draft-ietf-ipv6-2461bis-06.txt   draft-ietf-ipv6-2461bis-07.txt 
INTERNET-DRAFT T. Narten, INTERNET-DRAFT T. Narten,
Expires: September 2006 IBM Expires: November 2006 IBM
E. Nordmark, E. Nordmark,
Sun Microsystems Sun Microsystems
W. Simpson, W. Simpson,
Daydreamer Daydreamer
H. Soliman, H. Soliman,
Flarion Flarion
March, 2006 May, 2006
Neighbor Discovery for IP version 6 (IPv6) Neighbor Discovery for IP version 6 (IPv6)
<draft-ietf-ipv6-2461bis-06.txt> <draft-ietf-ipv6-2461bis-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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 13 skipping to change at page 2, line 13
about the paths to active neighbors. about the paths to active neighbors.
Table of Contents Table of Contents
1. INTRODUCTION....................................................4 1. INTRODUCTION....................................................4
2. TERMINOLOGY.....................................................4 2. TERMINOLOGY.....................................................4
2.1. General...................................................4 2.1. General...................................................4
2.2. Link Types................................................8 2.2. Link Types................................................8
2.3. Addresses.................................................9 2.3. Addresses.................................................9
2.4. Requirements..............................................9 2.4. Requirements.............................................10
3. PROTOCOL OVERVIEW..............................................10 3. PROTOCOL OVERVIEW..............................................10
3.1. Comparison with IPv4.....................................13 3.1. Comparison with IPv4.....................................13
3.2. Supported Link Types.....................................15 3.2. Supported Link Types.....................................15
3.3. Securing Neighbor Discovery messages......................17 3.3. Securing Neighbor Discovery messages......................17
4. MESSAGE FORMATS................................................17 4. MESSAGE FORMATS................................................17
4.1. Router Solicitation Message Format.......................17 4.1. Router Solicitation Message Format.......................17
4.2. Router Advertisement Message Format......................18 4.2. Router Advertisement Message Format......................18
4.3. Neighbor Solicitation Message Format.....................20 4.3. Neighbor Solicitation Message Format.....................20
skipping to change at page 2, line 39 skipping to change at page 2, line 39
4.6.4. MTU................................................30 4.6.4. MTU................................................30
5. CONCEPTUAL MODEL OF A HOST.....................................31 5. CONCEPTUAL MODEL OF A HOST.....................................31
5.1. Conceptual Data Structures...............................31 5.1. Conceptual Data Structures...............................31
5.2. Conceptual Sending Algorithm.............................33 5.2. Conceptual Sending Algorithm.............................33
5.3. Garbage Collection and Timeout Requirements..............35 5.3. Garbage Collection and Timeout Requirements..............35
6. ROUTER AND PREFIX DISCOVERY....................................35 6. ROUTER AND PREFIX DISCOVERY....................................35
6.1. Message Validation.......................................36 6.1. Message Validation.......................................36
6.1.1. Validation of Router Solicitation Messages.........36 6.1.1. Validation of Router Solicitation Messages.........36
6.1.2. Validation of Router Advertisement Messages........36 6.1.2. Validation of Router Advertisement Messages........37
6.2. Router Specification.....................................37 6.2. Router Specification.....................................37
6.2.1. Router Configuration Variables....................37 6.2.1. Router Configuration Variables....................37
6.2.2. Becoming An Advertising Interface.................41 6.2.2. Becoming An Advertising Interface.................41
6.2.3. Router Advertisement Message Content..............42 6.2.3. Router Advertisement Message Content..............42
6.2.4. Sending Unsolicited Router Advertisements.........43 6.2.4. Sending Unsolicited Router Advertisements.........43
6.2.5. Ceasing To Be An Advertising Interface............44 6.2.5. Ceasing To Be An Advertising Interface............44
6.2.6. Processing Router Solicitations...................44 6.2.6. Processing Router Solicitations...................44
6.2.7. Router Advertisement Consistency..................45 6.2.7. Router Advertisement Consistency..................46
6.2.8. Link-local Address Change.........................46 6.2.8. Link-local Address Change.........................46
6.3. Host Specification.......................................47 6.3. Host Specification.......................................47
6.3.1. Host Configuration Variables......................47 6.3.1. Host Configuration Variables......................47
6.3.2. Host Variables....................................47 6.3.2. Host Variables....................................47
6.3.3. Interface Initialization..........................48 6.3.3. Interface Initialization..........................48
6.3.4. Processing Received Router Advertisements.........48 6.3.4. Processing Received Router Advertisements.........48
6.3.5. Timing out Prefixes and Default Routers...........51 6.3.5. Timing out Prefixes and Default Routers...........51
6.3.6. Default Router Selection..........................51 6.3.6. Default Router Selection..........................51
6.3.7. Sending Router Solicitations......................52 6.3.7. Sending Router Solicitations......................52
skipping to change at page 3, line 41 skipping to change at page 3, line 41
10. PROTOCOL CONSTANTS............................................72 10. PROTOCOL CONSTANTS............................................72
11. SECURITY CONSIDERATIONS.......................................73 11. SECURITY CONSIDERATIONS.......................................73
11.1 Threat analysis...........................................73 11.1 Threat analysis...........................................73
11.2 Securing Neighbor Discovery messages......................74 11.2 Securing Neighbor Discovery messages......................74
12. RENUMBERING CONSIDERATIONS....................................75 12. RENUMBERING CONSIDERATIONS....................................75
REFERENCES.........................................................76 REFERENCES.........................................................76
Authors' Addresses.................................................79 Authors' Addresses.................................................80
APPENDIX A: MULTIHOMED HOSTS.......................................80 APPENDIX A: MULTIHOMED HOSTS.......................................80
APPENDIX B: FUTURE EXTENSIONS......................................81 APPENDIX B: FUTURE EXTENSIONS......................................81
APPENDIX C: STATE MACHINE FOR THE REACHABILITY STATE...............82 APPENDIX C: STATE MACHINE FOR THE REACHABILITY STATE...............82
APPENDIX D: SUMMARY OF ISROUTER RULES..............................84 APPENDIX D: SUMMARY OF ISROUTER RULES..............................84
APPENDIX E: IMPLEMENTATION ISSUES..................................85 APPENDIX E: IMPLEMENTATION ISSUES..................................85
Appendix E.1: Reachability confirmations...........................85 Appendix E.1: Reachability confirmations...........................85
APPENDIX F: CHANGES FROM RFC 2461..................................86 APPENDIX F: CHANGES FROM RFC 2461..................................86
1. INTRODUCTION 1. INTRODUCTION
skipping to change at page 19, line 17 skipping to change at page 19, line 18
Code 0 Code 0
Checksum The ICMP checksum. See [ICMPv6]. Checksum The ICMP checksum. See [ICMPv6].
Cur Hop Limit 8-bit unsigned integer. The default value that Cur Hop Limit 8-bit unsigned integer. The default value that
should be placed in the Hop Count field of the IP should be placed in the Hop Count field of the IP
header for outgoing IP packets. A value of zero header for outgoing IP packets. A value of zero
means unspecified (by this router). means unspecified (by this router).
M 1-bit "Managed address configuration" flag. When M 1-bit "Managed address configuration" flag. When
set, it indicates that Dynamic Host Configuration set, it indicates that addresses are available via
Protocol [DHCPv6] is available for address Dynamic Host Configuration Protocol [DHCPv6].
configuration in addition to any addresses
autoconfigured using stateless address If the M flag is set, the O flag is redundant and
autoconfiguration. can be ignored because DHCPv6 will return all
available configuration information.
O 1-bit "Other configuration" flag. When O 1-bit "Other configuration" flag. When
set, it indicates that [DHCPv6lite] is available set, it indicates that other configuration
for autoconfiguration of other (non-address) information is available via DHCPv6.
information. Examples of such information are DNS- Examples of such information are DNS-related
related information or information on other servers information or information on other servers within
within the network. the network.
Note: If neither M nor O flags are set this indicates that no
information is available via DHCPv6.
Reserved A 6-bit unused field. It MUST be initialized to Reserved A 6-bit unused field. It MUST be initialized to
zero by the sender and MUST be ignored by the zero by the sender and MUST be ignored by the
receiver. receiver.
Router Lifetime Router Lifetime
16-bit unsigned integer. The lifetime associated 16-bit unsigned integer. The lifetime associated
with the default router in units of seconds. with the default router in units of seconds.
The field can contain values up to 65535 and The field can contain values up to 65535 and
receivers should handle any value, while the receivers should handle any value, while the
skipping to change at page 78, line 5 skipping to change at page 78, line 8
[IPv6-SA] Kent, S. and R. Atkinson, "Security Architecture for the [IPv6-SA] Kent, S. and R. Atkinson, "Security Architecture for the
Internet Protocol", RFC 2401, November 1998. Internet Protocol", RFC 2401, November 1998.
[IPv6-AUTH] Kent, S. and R. Atkinson, "IP Authentication Header", [IPv6-AUTH] Kent, S. and R. Atkinson, "IP Authentication Header",
RFC 2402, November 1998. RFC 2402, November 1998.
[IPv6-ESP] Kent, S. and R. Atkinson, "IP Encapsulating Security [IPv6-ESP] Kent, S. and R. Atkinson, "IP Encapsulating Security
Payload (ESP)", RFC 2406, November 1998. Payload (ESP)", RFC 2406, November 1998.
[LD-SHRE] Hinden, R. and D. Thaler, "IPv6 Host-to-Router Load
Sharing", RFC 4311, November 2005.
[MIPv6] D. Johnson, C. Perkins and J. Arkko, "Mobility Support [MIPv6] D. Johnson, C. Perkins and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[MLD] Deering, S., Fenner, W, and B. Haberman, "Multicast [MLD] Deering, S., Fenner, W, and B. Haberman, "Multicast
Listener Discovery for IPv6", RFC 2710, October 1999. Listener Discovery for IPv6", RFC 2710, October 1999.
[MLDv2] Vida, R. and L. Costa, "Multicast Listener Discovery [MLDv2] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[NDMAN] Arkko, J., "Manual Configuration of Security [NDMAN] Arkko, J., "Manual Configuration of Security
skipping to change at page 86, line 50 skipping to change at page 87, line 4
Note that an implementation can not use negative upper-layer advise Note that an implementation can not use negative upper-layer advise
as a replacement for the Neighbor Unreachability Detection algorithm. as a replacement for the Neighbor Unreachability Detection algorithm.
Negative advise (e.g. from TCP when there are excessive Negative advise (e.g. from TCP when there are excessive
retransmissions) could serve as a hint that the forward path from the retransmissions) could serve as a hint that the forward path from the
sender of the data might not be working. But it would fail to detect sender of the data might not be working. But it would fail to detect
when the path from the receiver of the data is not functioning when the path from the receiver of the data is not functioning
causing, none of the acknowledgement packets to reach the sender. causing, none of the acknowledgement packets to reach the sender.
APPENDIX F: CHANGES FROM RFC 2461 APPENDIX F: CHANGES FROM RFC 2461
o Removed references to IPsec AH and ESP for securing messages
o Removed all references to IPsec AH and ESP for securing messages
or as part of validating the received message. or as part of validating the received message.
o Added section 3.3. o Added section 3.3.
o Updated section 11 to include more detailed discussion on threats, o Updated section 11 to include more detailed discussion on threats,
IPsec limitations, and use of SeND. IPsec limitations, and use of SeND.
o Removed the on-link assumption in section 5.2 based on o Removed the on-link assumption in section 5.2 based on
draft-ietf-v6ops-onlinkassumption draft-ietf-v6ops-onlinkassumption
skipping to change at page 88, line 37 skipping to change at page 88, line 42
Disclaimer of Validity Disclaimer of Validity
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 AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 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.
This Internet-Draft expires January, 2006. This Internet-Draft expires November, 2006.
 End of changes. 12 change blocks. 
19 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.31. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/