Detecting Network Attachment in IPv6 Networks (DNAv6) draft-ietf-dna-protocol-03.txt

1. Detecting Network Attachment in IPv6 Networks (DNAv6)draft-ietf-dna-protocol-03.txt S. Narayanan, Ed. J. Kempf, E. Nordmark, B. Pentland, JH. Choi, G. Daley, N. Montavont, N. Moore.

2. Outline • Overview of the merge • Overview of DNA • Open Issues (AFAIK) • Proposed schedule

3. Overview of the merge • Overview section (section 2) • Expands to include • Complete Prefix List • Erroneous Prefix List • Tentative Option (TO) • New TLV format for TO • No changes in DNA Router operation • DNA Host operation • DNA Steps from draft-ietf-dna-hosts • Processing router advertisement • Modified to include CPL for no link-change. • Or wait for further RAs if the prefix list not complete.

4. Overview of the merge (Contd.) • Just dropped in at the end • Tentative option • Initiation of DNA Procedures (from dna-host) • Complication to DNA (from dna-host) • Edited the document to • Remove redundancy (Candidate Objects and DNAHostPrefixList) • Improve flow • RA processing logic

5. DNA Steps • Try making use of prior information stored related to the links the host visited in the past (see Section 5.2.4). • If the prior information implies no link change, the host MAY conduct reachability detection (see Section 5.2.7.4) to one of the default routers it is using, otherwise no action is needed. • If the prior information implies that there is a link change or there is no useful prior information available, follow the procedure below. • Mark all the IPv6 addresses in use as optimistic. • Set all Neighbor Cache entries for routers on its Default Router List to STALE. • Send router solicitation. (See Section 5.2.6). • Receive router advertisement (s). • Mark that router's Neighbor Cache Entry [3] as REACHABLE, or add a Neighbor Cache Entry in the REACHABLE state if one does not currently exist. • Process received router advertisement. (See Section 5.2.7). • If the link has changed Change the IP configuration parameters of the host (see Section 5.2.8). • If the link has NOT changed Restore the address configuration state of all the IPv6 addresses known to be on the link. • Update default routers list and their reachability information (see Section 5.2.7.4).

6. Processing RA

7. Open Issues • WiMAX is trying to increase the MaxRtrAdvInterval into hours or days. Should we change 1.5 hours to 3 * MaxRtrAdvInterval? • What happens if no prefixes are advertised in a link? Is such a scenario possible? Proposal is to mandate the AR to advertise the linkID prefix. • Do we need Landmark Y/N bit? • We never use the ‘N’ bit, because if the host has changed link, the draft recommends sending a completeRA. It doesn’t make sense to send a Landmark with N bit because it wastes space in the RA. • ‘Y’ functionality can be achieved by just including the Landmark prefix in the RA. But, the host will not know whether this RA is in response to its request or not? • Should variables NumRSRAComplete, MinRAWait, MaxCacheTime be kept as variables or should they be constants?

8. Open Issues (Contd.) • DNA Terminology – Do we need any more terms defined? • MaxCacheTime – Do we want to keep this variable and its associated functionality? • Do we have to say something about storing old LinkID list as prior information for future use? • There is some text w.r.t. old prefix list, I think? We have to make this consistent.

9. Open Issues (Contd.) • Do we need a section on “DNA without link UP notification”? • Current section with that title is text from CPL. If we want to keep this, we need to make it applicable for the whole scheme. • Do we want to keep “Initiation of DNA procedures”? • Anything else?

10. Proposed schedule • Next revision by ~ Dec 15 • Need substantial comments by Nov 30. • Another revision by ~ Feb 15. • Need substantial comments by Jan 31.