draft-ietf-dna-simple-05.txt   draft-ietf-dna-simple-06.txt 
Network Working Group S. Krishnan Network Working Group S. Krishnan
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 4861 (if approved) G. Daley Updates: 4861 (if approved) G. Daley
Intended status: Standards Track NetStar Networks Intended status: Standards Track NetStar Networks
Expires: May 7, 2009 November 3, 2008 Expires: August 28, 2009 February 24, 2009
Simple procedures for Detecting Network Attachment in IPv6 Simple procedures for Detecting Network Attachment in IPv6
draft-ietf-dna-simple-05 draft-ietf-dna-simple-06
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 May 7, 2009. This Internet-Draft will expire on August 28, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
Detecting Network Attachment allows hosts to assess if its existing Detecting Network Attachment allows hosts to assess if its existing
addressing or routing configuration is valid for a newly connected addressing or routing configuration is valid for a newly connected
network. network.
This document provides simple procedures for detecting network This document provides simple procedures for detecting network
attachment in IPv6 hosts, and procedures for routers to support such attachment in IPv6 hosts, and procedures for routers to support such
services. services.
skipping to change at page 2, line 31 skipping to change at page 2, line 37
4.5.1. Neighbor Solicitation messages . . . . . . . . . . . . 8 4.5.1. Neighbor Solicitation messages . . . . . . . . . . . . 8
4.5.2. Router Solicitation messages . . . . . . . . . . . . . 8 4.5.2. Router Solicitation messages . . . . . . . . . . . . . 8
4.6. Sending DHCPv6 probes . . . . . . . . . . . . . . . . . . 8 4.6. Sending DHCPv6 probes . . . . . . . . . . . . . . . . . . 8
4.7. Response Gathering . . . . . . . . . . . . . . . . . . . . 9 4.7. Response Gathering . . . . . . . . . . . . . . . . . . . . 9
4.8. Further Host Operations . . . . . . . . . . . . . . . . . 10 4.8. Further Host Operations . . . . . . . . . . . . . . . . . 10
4.9. Recommended retransmission behavior . . . . . . . . . . . 10 4.9. Recommended retransmission behavior . . . . . . . . . . . 10
5. Router Operations . . . . . . . . . . . . . . . . . . . . . . 11 5. Router Operations . . . . . . . . . . . . . . . . . . . . . . 11
5.1. DHCPv6 Router/Server Operations . . . . . . . . . . . . . 12 5.1. DHCPv6 Router/Server Operations . . . . . . . . . . . . . 12
6. Pseudocode for Simple DNA . . . . . . . . . . . . . . . . . . 12 6. Pseudocode for Simple DNA . . . . . . . . . . . . . . . . . . 12
7. Constants . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. Constants . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Relationship to DNAv4 . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 9. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 15
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
12.1. Normative References . . . . . . . . . . . . . . . . . . . 16 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
12.2. Informative References . . . . . . . . . . . . . . . . . . 17 13.1. Normative References . . . . . . . . . . . . . . . . . . . 16
13.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
Hosts require procedures to simply and reliably identify if they have Hosts require procedures to simply and reliably identify if they have
skipping to change at page 7, line 35 skipping to change at page 7, line 35
unicast Neighbor Solicitations to a test node corresponding to an unicast Neighbor Solicitations to a test node corresponding to an
IPv6 address that is no longer valid. IPv6 address that is no longer valid.
Please note that the Neighbour Solicitations SHOULD be sent in Please note that the Neighbour Solicitations SHOULD be sent in
parallel with the Router Solicitations. Since sending NSs is just an parallel with the Router Solicitations. Since sending NSs is just an
optimization, doing the NSs and RSs in parallel ensures that the optimization, doing the NSs and RSs in parallel ensures that the
procedure does not run slower than it would if it only used an RS. procedure does not run slower than it would if it only used an RS.
Be aware that each unicast solicitation which is not successful may Be aware that each unicast solicitation which is not successful may
cause packet flooding in bridged networks, if the networks are not cause packet flooding in bridged networks, if the networks are not
properly configured. This is further described in Section 8. Where properly configured. This is further described in Section 9. Where
flooding may cause performance issues within the LAN, host SHOULD flooding may cause performance issues within the LAN, host SHOULD
limit the number of unicast solicitations. limit the number of unicast solicitations.
4.5. Contents of the Neighbor Discovery messages 4.5. Contents of the Neighbor Discovery messages
4.5.1. Neighbor Solicitation messages 4.5.1. Neighbor Solicitation messages
This section describes the contents of the neighbor solicitation This section describes the contents of the neighbor solicitation
probe messages sent during the probing procedure. probe messages sent during the probing procedure.
skipping to change at page 8, line 25 skipping to change at page 8, line 25
Destination Address: The link-local address of the router being Destination Address: The link-local address of the router being
probed as learnt from the SDAT. probed as learnt from the SDAT.
Hop Limit: 255 Hop Limit: 255
ND Options: ND Options:
Target Address: The link-local address of the router being Target Address: The link-local address of the router being
probed as learnt from the SDAT. probed as learnt from the SDAT.
The probing node SHOULD NOT include a Source link-layer address The probing node SHOULD include a Source link-layer address option in
option if it has not performed duplicate address detection [RFC4862], the probe messages. If the node believes that the source address of
for the source address of the NS, on the newly attached link. the NS may not be unique on the newly attached link, it MAY omit the
Source link-layer address option in the probe messages.
4.5.2. Router Solicitation messages 4.5.2. Router Solicitation messages
This section describes the contents of the router solicitation probe This section describes the contents of the router solicitation probe
message sent during the probing procedure. message sent during the probing procedure.
Source Address: A link-local address assigned to the Source Address: A link-local address assigned to the
probing host. probing host.
Destination Address: The all-routers multicast address. Destination Address: The all-routers multicast address.
skipping to change at page 14, line 42 skipping to change at page 14, line 42
Value: 20 Value: 20
SEND_NA_GRACE_TIME SEND_NA_GRACE_TIME
Definition: An optional period to wait after Neighbour Definition: An optional period to wait after Neighbour
Solicitation before adopting a non-SEND RA's link change Solicitation before adopting a non-SEND RA's link change
information. information.
Value: 40 milliseconds Value: 40 milliseconds
8. Open Issues 8. Relationship to DNAv4
DNAv4 [RFC4436] specifies a set of steps that optimize the (common)
case of re-attachment to an IPv4 network that one has been connected
to previously by attempting to re-use a previous (but still valid)
configuration. This document shares the same goal as DNAv4 (that of
minimizing the handover latency in moving between points of
attachment) but differs in the steps it performs to achieve this
goal. Another difference is that this document also supports
stateless autoconfiguration of addresses in addition to addresses
configured using DHCPv6.
9. Open Issues
This section documents issues that are still outstanding within the This section documents issues that are still outstanding within the
document, and the simple DNA solution in general. document, and the simple DNA solution in general.
Rate limitation for solicitations. Rate limitation for solicitations.
Hosts MAY implement hysteresis mechanisms to pace solicitations Hosts MAY implement hysteresis mechanisms to pace solicitations
where necessary to prevent damage to a particular medium. where necessary to prevent damage to a particular medium.
Implementors should be aware that when such hysteresis is Implementors should be aware that when such hysteresis is
triggered, Detecting Network Attachment may be slowed, which may triggered, Detecting Network Attachment may be slowed, which may
affect application traffic. affect application traffic.
9. IANA Considerations 10. IANA Considerations
There are no changes to IANA registries required in this document. There are no changes to IANA registries required in this document.
10. Security Considerations 11. Security Considerations
When providing fast responses to router solicitations, it is possible When providing fast responses to router solicitations, it is possible
to cause collisions with other signaling packets on contention based to cause collisions with other signaling packets on contention based
media. This can cause repeated packet loss or delay when multiple media. This can cause repeated packet loss or delay when multiple
routers are present on the link. routers are present on the link.
As such the fast router advertisement system is NOT RECOMMENDED in As such the fast router advertisement system is NOT RECOMMENDED in
this form for media which are susceptible to collision loss. Such this form for media which are susceptible to collision loss. Such
environments may be better served using the procedures defined in environments may be better served using the procedures defined in
[I-D.ietf-dna-protocol]. [I-D.ietf-dna-protocol].
skipping to change at page 16, line 8 skipping to change at page 16, line 20
Even if SEND signatures on RAs are used, it may not be immediately Even if SEND signatures on RAs are used, it may not be immediately
clear if the router is authorized to make such advertisements. As clear if the router is authorized to make such advertisements. As
such, a host SHOULD NOT treat such devices as secure until and unless such, a host SHOULD NOT treat such devices as secure until and unless
authorization delegation discovery is successful. authorization delegation discovery is successful.
It is easy for hosts soliciting without SEND to deplete a SEND It is easy for hosts soliciting without SEND to deplete a SEND
router's fast advertisement token buckets, and consume additional router's fast advertisement token buckets, and consume additional
bandwidth. As such, a router MAY choose to preserve a portion of bandwidth. As such, a router MAY choose to preserve a portion of
their token bucket to serve solicitations with SEND signatures. their token bucket to serve solicitations with SEND signatures.
11. Acknowledgments 12. Acknowledgments
This document is the product of a discussion between the authors had This document is the product of a discussion between the authors had
with Bernard Aboba, Thomas Narten, Erik Nordmark and Dave Thaler at with Bernard Aboba, Thomas Narten, Erik Nordmark and Dave Thaler at
IETF 69. The authors would like to thank them for clearly detailing IETF 69. The authors would like to thank them for clearly detailing
the requirements of the solution and the goals it needed to meet and the requirements of the solution and the goals it needed to meet and
for helping to explore the solution space. The authors would like to for helping to explore the solution space. The authors would like to
thank the authors and editors of the complete DNA specification for thank the authors and editors of the complete DNA specification for
detailing the overall problem space and solutions. The authors would detailing the overall problem space and solutions. The authors would
like to thank Jari Arkko for driving the evolution of a simple and like to thank Jari Arkko for driving the evolution of a simple and
probabilistic DNA solution. The authors would like to thank Bernard probabilistic DNA solution. The authors would like to thank Bernard
Aboba, Thomas Narten, Sathya Narayan, Julien Laganier, Domagoj Aboba, Thomas Narten, Sathya Narayan, Julien Laganier, Domagoj
Premec, Jin Hyeock-Choi, Alfred Hoenes and Frederic Rossi for Premec, Jin Hyeock-Choi, Alfred Hoenes and Frederic Rossi for
performing reviews on the document and providing valuable comments to performing reviews on the document and providing valuable comments to
drive the document forward. drive the document forward.
12. References 13. References
12.1. Normative References 13.1. Normative References
[I-D.ietf-dna-tentative] [I-D.ietf-dna-tentative]
Daley, G., Nordmark, E., and N. Moore, "Tentative Options Daley, G., Nordmark, E., and N. Moore, "Tentative Options
for IPv6 Neighbour Discovery", draft-ietf-dna-tentative-01 for IPv6 Neighbour Discovery", draft-ietf-dna-tentative-01
(work in progress), July 2007. (work in progress), July 2007.
[I-D.ietf-dna-protocol] [I-D.ietf-dna-protocol]
Narayanan, S., "Detecting Network Attachment in IPv6 Narayanan, S., "Detecting Network Attachment in IPv6
Networks (DNAv6)", draft-ietf-dna-protocol (work in Networks (DNAv6)", draft-ietf-dna-protocol (work in
progress), June 2007. progress), June 2007.
skipping to change at page 17, line 9 skipping to change at page 17, line 22
[RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol
(DHCP) Service for IPv6", RFC 3736, April 2004. (DHCP) Service for IPv6", RFC 3736, April 2004.
[RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure [RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
Neighbor Discovery (SEND)", RFC 3971, March 2005. Neighbor Discovery (SEND)", RFC 3971, March 2005.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
12.2. Informative References 13.2. Informative References
[RFC4957] Krishnan, S., Montavont, N., Njedjou, E., Veerepalli, S., [RFC4957] Krishnan, S., Montavont, N., Njedjou, E., Veerepalli, S.,
and A. Yegin, "Link-Layer Event Notifications for and A. Yegin, "Link-Layer Event Notifications for
Detecting Network Attachments", RFC 4957, August 2007. Detecting Network Attachments", RFC 4957, August 2007.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[RFC4436] Aboba, B., Carlson, J., and S. Cheshire, "Detecting
Network Attachment in IPv4 (DNAv4)", RFC 4436, March 2006.
Authors' Addresses Authors' Addresses
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Decarie Blvd. 8400 Decarie Blvd.
Town of Mount Royal, QC Town of Mount Royal, QC
Canada Canada
Phone: +1 514 345 7900 x42871 Phone: +1 514 345 7900 x42871
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
skipping to change at page 17, line 28 skipping to change at page 18, line 4
Authors' Addresses Authors' Addresses
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Decarie Blvd. 8400 Decarie Blvd.
Town of Mount Royal, QC Town of Mount Royal, QC
Canada Canada
Phone: +1 514 345 7900 x42871 Phone: +1 514 345 7900 x42871
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
Greg Daley Greg Daley
NetStar Networks NetStar Networks
Level 9/636 St Kilda Rd Level 9/636 St Kilda Rd
Melbourne, Victoria 3004 Melbourne, Victoria 3004
Australia Australia
Phone: +61 3 8532 4042 Phone: +61 3 8532 4042
Email: gdaley@netstarnetworks.com Email: gdaley@netstarnetworks.com
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 18 change blocks. 
27 lines changed or deleted 52 lines changed or added

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