Presentation is loading. Please wait.

Presentation is loading. Please wait.

Slide title In CAPITALS 50 pt Slide subtitle 32 pt Simple DNA draft-ietf-dna-simple-03 Suresh Krishnan Greg Daley.

Similar presentations


Presentation on theme: "Slide title In CAPITALS 50 pt Slide subtitle 32 pt Simple DNA draft-ietf-dna-simple-03 Suresh Krishnan Greg Daley."— Presentation transcript:

1 Slide title In CAPITALS 50 pt Slide subtitle 32 pt Simple DNA draft-ietf-dna-simple-03 Suresh Krishnan Greg Daley

2 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-122 Status  Document adopted as WG item at IETF71  Received several reviews –Bernard Aboba, Julien Laganier, Domagoj Premec, Jin Hyeock Choi and Alfred Hoenes reviewed the document and provided comments (Thanks!)  Started using an issue tracker to make sure issues are recorded and resolved –http://tools.ietf.org/wg/dna/trac/report/9 lists all issues (both open and closed)http://tools.ietf.org/wg/dna/trac/report/9 –http://tools.ietf.org/wg/dna/trac/report/1 lists open issueshttp://tools.ietf.org/wg/dna/trac/report/1

3 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-123 Issue #1: To DAD or not to DAD  ISSUE: A simple DNA host should not perform DAD after re-attaching to a known link  SUBMITTER: Bernard Aboba  STATUS: Resolved  RESOLUTION: Added text to indicate that this should not be done. The exact text reads  “ If the host has determined that there has been no link change, it SHOULD NOT perform duplicate address detection on the addresses that have been confirmed to be operable. ”

4 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-124 Issue #2: Scope of SDAT  ISSUE: It is not clear whether the simple dna address table is maintained on a per-interface basis or on a per- host basis.  SUBMITTER: Alfred Hoenes  STATUS: Resolved  RESOLUTION: It has been clarified that the Simple DNA Address table is maintained on a per interface basis and not on a per host basis  The text reads “This data structure is maintained by the host on a per interface basis.” –Do we need stronger text? (Perhaps Normative)

5 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-125 Issue #4: When is DAD done  ISSUE: It was not clear from the document whether DAD is performed after receiving a link-layer indication or after performing the simple dna procedure.  SUBMITTER: Domagoj Premec  STATUS: Resolved  RESOLUTION: This issue is resolved by the following text that also addresses Issue #1  “If the host has determined that there has been no link change, it SHOULD NOT perform duplicate address detection on the addresses that have been confirmed to be operable.”

6 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-126 Issue #5: Default router selection  ISSUE: A Simple DNA capable host should not wait until communication fails to start seeking a new default router.  SUBMITTER: Julien Laganier  STATUS: Resolved  RESOLUTION: –The following text has been added in Section 4.3  It SHOULD also set all Neighbor Cache entries for the routers on its Default Router List to STALE. This is done to speed up the acquisition of a new default router when link change has occurred. –The following text is added to Section 4.5  When the host receives a Router Advertisement in reply to the Router Solicitation it sent, the host SHOULD look for a Neighbor Cache entry for the sending router and SHOULD mark that router's Neighbor Cache Entry as REACHABLE if one was found. The host SHOULD add a new Neighbor Cache Entry in the REACHABLE state for the sending router if one does not currently exist.

7 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-127 Issue #6: Source Address in RS  ISSUE: Which of the addresses on the host should be used as the source address of the RS?  SUBMITTER: Bernard Aboba, Julien Laganier  STATUS: Resolved  RESOLUTION: The following text has been added to describe the source address used to send the RS and the NS probes. This text uses a link-local as source address as suggested by the submitters.  “The Router Solicitation is sent to the All-routers multicast address using a link-local address as the source address [RFC4861]. Even if the host is in possession of more than one valid IPv6 address, it MUST send only one router solicitation using a valid link-local address as the source address. “

8 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-128 Issue #7: What is a “Valid Address”  ISSUE: The term “valid address” used in the document is ambiguous as it can mean one of two things –Case 1) An address which a host can use on the currently attached link –Case 2) Any address with valid lifetime.  SUBMITTER: Jin Hyeock Choi, Bernard Aboba  STATUS: Resolved  RESOLUTION: This has been fixed by using the term "operable address" for Case 1) mentioned above and using the term "valid address" for Case 2). The two terms have been defined in a new Terminology section.

9 Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt © Ericsson AB 2008Simple DNA2008-03-129 Way forward  Any more open/outstanding issues? –Not aware of any but feel free to raise them  Reviews –Do we need wider reviews of this document  Implementer feedback –Host/router vendors who have plans to implement this proposal  Progressing the document –Before the next IETF meeting if everything goes well  What do we do with the wg?


Download ppt "Slide title In CAPITALS 50 pt Slide subtitle 32 pt Simple DNA draft-ietf-dna-simple-03 Suresh Krishnan Greg Daley."

Similar presentations


Ads by Google