[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DNA] DNA Protocol vs. Protocol 2
Over all the TOC is okay, what I was mentioning is about the content
of the sections.
>
> I'm open to suggestions. What sort of reorganization would help?
>
> As it stands, section 3 is an overview and it clearly breaks the problem
> down into separate sections:
>
> 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
> 3.1 What Identifies a Link? . . . . . . . . . . . . . . . . . 6
> 3.2 Link Identification . . . . . . . . . . . . . . . . . . . 6
> 3.3 Fast Router Advertisment . . . . . . . . . . . . . . . . . 7
Can we describe these 2 completely in this sections? Meaning, can we
for example, just replace the Link Identification method with some other
approach?
>
> Section 5 goes into the details of what each device has to do to solve
> both problems:
>
> 5. DNA Operation . . . . . . . . . . . . . . . . . . . . . . . . 11
> 5.1 DNA Router Operation . . . . . . . . . . . . . . . . . . . 11
> 5.1.1 Data Structures . . . . . . . . . . . . . . . . . . . 11
> 5.1.2 Router Configuration Variables . . . . . . . . . . . . 12
> 5.1.3 Bootstrapping DNA Data Structures . . . . . . . . . . 13
> 5.1.4 Processing Router Advertisements . . . . . . . . . . . 13
> 5.1.5 Processing Router Solicitations . . . . . . . . . . . 13
> 5.1.6 Complete Router Advertisements . . . . . . . . . . . . 15
> 5.1.7 Scheduling Fast Router Advertisements . . . . . . . . 15
> 5.1.8 Scheduling Unsolicited Router Advertisements . . . . . 16
> 5.2 DNA Host Operation . . . . . . . . . . . . . . . . . . . . 16
> 5.2.1 Data Structures . . . . . . . . . . . . . . . . . . . 16
> 5.2.2 Selection of a Landmark Prefix . . . . . . . . . . . . 17
> 5.2.3 Sending Router Solicitations . . . . . . . . . . . . . 17
> 5.2.4 Processing Router Advertisements . . . . . . . . . . . 17
>
> Is this general structure ok (just needing some reorganization within
> sections)?
>
> Brett.
>
>