1 / 10

draft-pentland-dna-protocol3-00.txt

draft-pentland-dna-protocol3-00.txt. Brett Pentland. Agenda. Document description Open Issues Consensus call. Background. Based on two prior proposals draft-pentland-dna-protocol-01.txt draft-jinchoi-dna-protocol2-01.txt Only one fast RA scheme Link Identification schemes merged.

kylan-hartman
Download Presentation

draft-pentland-dna-protocol3-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-pentland-dna-protocol3-00.txt Brett Pentland

  2. Agenda • Document description • Open Issues • Consensus call

  3. Background • Based on two prior proposals • draft-pentland-dna-protocol-01.txt • draft-jinchoi-dna-protocol2-01.txt • Only one fast RA scheme • Link Identification schemes merged

  4. Fast RA • Taken directly from draft-pentland-dna-protocol-01.txt Token = A Token = B Token = C Access Routers RS Token = S Host Say that: B XOR S < A XOR S < C XOR S • B sends an RA immediately • A sends an RA after 20 ms • C sends an RA after 40 ms

  5. Link Identification • Routers listen for all prefixes on a link • In general, all prefixes included in RAs • New option for learned prefixes • One noted as LinkID prefix • MUST be included in RAs • Hosts SHOULD include a landmark in RSs • If the landmark is on the link, routers may send an abbreviated RA containing only the landmark • If the landmark is not on the link or there’s no landmark routers send a Complete RA • Unsolicited RAs MAY carry a subset of prefixes but MUST include the LinkID prefix

  6. RA(A) RA(A,B) RA(C,D) RA(C) RA(A-Yes) RA(A-Yes) RA(A-No,C,D) RA(A-No,C,D) A,B A,B C,D A,B Link Identification A B B A C D D C ARs RA(C) RA(D) RS(A?) APs RS(A?) Host

  7. Open Issues • Identification based on non-prefix information • No supporting emails on mailing list • Explicit link identifiers • Some other discussion suggests there is interest • TSLLAO • Needed for unicast RS/RA w/o NS/NA • Where does this belong? • Delivery of MLD packets during DNA? • presentation to follow

  8. Open issues (cont) • Packet delivery to/from node during DNA i.e. between the RS and RA • What should hosts do with queued packets? • Do we need separate Y/N flags for the Landmark Option? • Probably not.

  9. Possible LPO format 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length |L|P| Reserved | Prefix Len 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | Prefix Len N | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + Prefix 1 + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + Prefix 2 + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + Prefix N + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Use a flag to mark the first prefix as the LinkID • Use a further flag to mark it as “not a prefix” • Need host processing rules

  10. Where to now? • Is this close enough to the mark to accept as a WG draft?

More Related