draft-ietf-dna-protocol-06.txt   draft-ietf-dna-protocol-07.txt 
DNA Working Group S. Narayanan, Ed. DNA Working Group S. Narayanan, Ed.
Internet-Draft iTCD/CSUMB Internet-Draft iTCD/CSUMB
Expires: December 27, 2007 June 25, 2007 Expires: August 27, 2008 Feb 24, 2008
Detecting Network Attachment in IPv6 Networks (DNAv6) Detecting Network Attachment in IPv6 Networks (DNAv6)
draft-ietf-dna-protocol-06.txt draft-ietf-dna-protocol-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 27, 2007. This Internet-Draft will expire on August 27, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
Efficient detection of network attachment in IPv6 needs the following Efficient detection of network attachment in IPv6 needs the following
three components: a method for hosts to detect link change in the three components: a method for hosts to detect link change in the
presence of unmodified (non-DNAv6) routers, a method for the host to presence of unmodified (non-DNAv6) routers, a method for the host to
query routers on the link to identify the link (Link Identification) query routers on the link to identify the link (Link Identification)
and a method for the routers on the link to consistently respond to and a method for the routers on the link to consistently respond to
such a query with minimal delay (Fast RA). Solving the link such a query with minimal delay (Fast RA). Solving the link
identification based strictly on RFC 2461 is difficult because of the identification based strictly on RFC 2461 is difficult because of the
skipping to change at page 3, line 7 skipping to change at page 3, line 7
5.2.2 Host Configuration Variables . . . . . . . . . . . . . 22 5.2.2 Host Configuration Variables . . . . . . . . . . . . . 22
5.2.3 Detecting Network Attachment Steps . . . . . . . . . . 22 5.2.3 Detecting Network Attachment Steps . . . . . . . . . . 22
5.2.4 Selection of a Landmark Prefix . . . . . . . . . . . . 23 5.2.4 Selection of a Landmark Prefix . . . . . . . . . . . . 23
5.2.5 Sending Router Solicitations . . . . . . . . . . . . . 23 5.2.5 Sending Router Solicitations . . . . . . . . . . . . . 23
5.2.6 Processing Router Advertisements . . . . . . . . . . . 24 5.2.6 Processing Router Advertisements . . . . . . . . . . . 24
5.2.7 DNA and Address Configuration . . . . . . . . . . . . 29 5.2.7 DNA and Address Configuration . . . . . . . . . . . . 29
5.3 Tentative options for IPv6 ND . . . . . . . . . . . . . . 32 5.3 Tentative options for IPv6 ND . . . . . . . . . . . . . . 32
5.3.1 Sending solicitations containing Tentative Options . . 32 5.3.1 Sending solicitations containing Tentative Options . . 32
5.3.2 Receiving Tentative Options . . . . . . . . . . . . . 33 5.3.2 Receiving Tentative Options . . . . . . . . . . . . . 33
5.3.3 Sending directed advertisements without the 5.3.3 Sending directed advertisements without the
neighbour cache . . . . . . . . . . . . . . . . . . . 35 neighbour cache . . . . . . . . . . . . . . . . . . . 34
6. Security Considerations . . . . . . . . . . . . . . . . . . 36 6. Security Considerations . . . . . . . . . . . . . . . . . . 36
6.1 Attacks on the Token Bucket . . . . . . . . . . . . . . . 36 6.1 Attacks on the Token Bucket . . . . . . . . . . . . . . . 36
6.2 Attacks on DNA Hosts . . . . . . . . . . . . . . . . . . . 36 6.2 Attacks on DNA Hosts . . . . . . . . . . . . . . . . . . . 36
6.3 Tentative options . . . . . . . . . . . . . . . . . . . . 37 6.3 Tentative options . . . . . . . . . . . . . . . . . . . . 36
6.4 Authorization and Detecting Network Attachment . . . . . . 38 6.4 Authorization and Detecting Network Attachment . . . . . . 38
6.5 Addressing . . . . . . . . . . . . . . . . . . . . . . . . 38 6.5 Addressing . . . . . . . . . . . . . . . . . . . . . . . . 38
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 38 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 38
8. Constants . . . . . . . . . . . . . . . . . . . . . . . . . 39 8. Constants . . . . . . . . . . . . . . . . . . . . . . . . . 38
9. Changes since -05 . . . . . . . . . . . . . . . . . . . . . 40 9. Changes since -05 . . . . . . . . . . . . . . . . . . . . . 40
10. Changes since -04 . . . . . . . . . . . . . . . . . . . . . 41 10. Changes since -04 . . . . . . . . . . . . . . . . . . . . . 40
11. Changes since -03 . . . . . . . . . . . . . . . . . . . . . 41 11. Changes since -03 . . . . . . . . . . . . . . . . . . . . . 41
12. Changes since -02 . . . . . . . . . . . . . . . . . . . . . 41 12. Changes since -02 . . . . . . . . . . . . . . . . . . . . . 41
13. Open issues . . . . . . . . . . . . . . . . . . . . . . . . 42 13. Open issues . . . . . . . . . . . . . . . . . . . . . . . . 42
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 42 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 42
skipping to change at page 16, line 41 skipping to change at page 16, line 41
If a unicast response is not possible but there is a multicast RA If a unicast response is not possible but there is a multicast RA
already scheduled for transmission in the next MULTICAST_RA_DELAY, already scheduled for transmission in the next MULTICAST_RA_DELAY,
then the Router Solicitation MUST be silently discarded. then the Router Solicitation MUST be silently discarded.
All Router Advertisements sent by a DNA router MUST have the "D" flag All Router Advertisements sent by a DNA router MUST have the "D" flag
set so that hosts processing them know that they can interpret the set so that hosts processing them know that they can interpret the
messages according to this specification. messages according to this specification.
In order to understand the conditions leading to the different type In order to understand the conditions leading to the different type
of Router Advertisement messages (Abbreviated Vs CompleteRA, Unicast of Router Advertisement messages, please refer to the figure below,
Vs Multicast), please refer to the figure below,
+---------------+--+----+-----+-----+----+-----+----+-----+----+ +---------------+--+----+-----+-----+----+-----+----+-----+----+
| RA Message | Unicast | Multicast | | RA Message | Unicast | Multicast |
+---------------+--+----+-----+-----+----+-----+----+-----+----+ +---------------+--+----+-----+-----+----+-----+----+-----+----+
| Abbreviated RA| Landmark prefix present| Never | | Abbreviated RA| Landmark prefix present| Never |
| | on the link | | | | on the link | |
+---------------+--+----+-----+-----+----+-----+----+-----+----+ +---------------+--+----+-----+-----+----+-----+----+-----+----+
| Complete RA |No LO in RS or Landmark |No token available in| | Complete RA |No LO in RS or Landmark |No token available in|
| |prefix NOT present | the token bucket. | | |prefix NOT present | the token bucket. |
| | on the link. | | | | on the link. | |
skipping to change at page 44, line 48 skipping to change at page 44, line 46
Authors' Addresses Authors' Addresses
Sathya Narayanan (editor) Sathya Narayanan (editor)
School of Information Technology and Communications Design School of Information Technology and Communications Design
California State University, Monterey Bay California State University, Monterey Bay
3110, Inter-Garrison Road, Building 18, Room 150 3110, Inter-Garrison Road, Building 18, Room 150
Seaside, CA 93955 Seaside, CA 93955
USA USA
Phone: +1 (831) 582-3621 Phone: +1 (831) 582-33411
Email: sathya@njit.edu Email: sathya_narayanan@csumb.edu
James Kempf James Kempf
DoCoMo Communications Labs USA DoCoMo Communications Labs USA
USA USA
Phone: Phone:
Email: kempf@docomolabs-usa.com Email: kempf@docomolabs-usa.com
Erik Nordmark Erik Nordmark
Sun Microsystems, Inc. Sun Microsystems, Inc.
17 Network Circle 17 Network Circle
skipping to change at page 47, line 29 skipping to change at page 47, line 29
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR,THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR,THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY),THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY),THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 12 change blocks. 
19 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/