IPv6 Node Requirements
RFC 8504
| Document | Type |
RFC - Best Current Practice
(January 2019; No errata)
Obsoletes RFC 6434
Also known as BCP 220
|
|
|---|---|---|---|
| Last updated | 2019-01-30 | ||
| Replaces | draft-clw-rfc6434-bis | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Bob Hinden | ||
| Shepherd write-up | Show (last changed 2018-03-21) | ||
| IESG | IESG state | RFC 8504 (Best Current Practice) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Suresh Krishnan | ||
| Send notices to | Robert Hinden <bob.hinden@gmail.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) T. Chown
Request for Comments: 8504 Jisc
BCP: 220 J. Loughney
Obsoletes: 6434 Intel
Category: Best Current Practice T. Winters
ISSN: 2070-1721 UNH-IOL
January 2019
IPv6 Node Requirements
Abstract
This document defines requirements for IPv6 nodes. It is expected
that IPv6 will be deployed in a wide range of devices and situations.
Specifying the requirements for IPv6 nodes allows IPv6 to function
well and interoperate in a large number of situations and
deployments.
This document obsoletes RFC 6434, and in turn RFC 4294.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8504.
Chown, et al. Best Current Practice [Page 1]
RFC 8504 IPv6 Node Requirements January 2019
Copyright Notice
Copyright (c) 2019 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
(https://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. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Scope of This Document . . . . . . . . . . . . . . . . . 4
1.2. Description of IPv6 Nodes . . . . . . . . . . . . . . . . 5
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5
3. Abbreviations Used in This Document . . . . . . . . . . . . . 5
4. Sub-IP Layer . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IP Layer . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Internet Protocol Version 6 - RFC 8200 . . . . . . . . . 6
5.2. Support for IPv6 Extension Headers . . . . . . . . . . . 7
5.3. Protecting a Node from Excessive Extension Header Options 8
5.4. Neighbor Discovery for IPv6 - RFC 4861 . . . . . . . . . 9
5.5. SEcure Neighbor Discovery (SEND) - RFC 3971 . . . . . . . 11
5.6. IPv6 Router Advertisement Flags Option - RFC 5175 . . . . 11
5.7. Path MTU Discovery and Packet Size . . . . . . . . . . . 11
5.7.1. Path MTU Discovery - RFC 8201 . . . . . . . . . . . . 11
5.7.2. Minimum MTU Considerations . . . . . . . . . . . . . 12
5.8. ICMP for the Internet Protocol Version 6 (IPv6) -
RFC 4443 . . . . . . . . . . . . . . . . . . . . . . . . 12
5.9. Default Router Preferences and More-Specific Routes -
RFC 4191 . . . . . . . . . . . . . . . . . . . . . . . . 12
5.10. First-Hop Router Selection - RFC 8028 . . . . . . . . . . 12
5.11. Multicast Listener Discovery (MLD) for IPv6 - RFC 3810 . 13
5.12. Explicit Congestion Notification (ECN) - RFC 3168 . . . . 13
6. Addressing and Address Configuration . . . . . . . . . . . . 13
6.1. IP Version 6 Addressing Architecture - RFC 4291 . . . . . 13
6.2. Host Address Availability Recommendations . . . . . . . . 13
6.3. IPv6 Stateless Address Autoconfiguration - RFC 4862 . . . 14
6.4. Privacy Extensions for Address Configuration in IPv6 -
RFC 4941 . . . . . . . . . . . . . . . . . . . . . . . . 15
Chown, et al. Best Current Practice [Page 2]
RFC 8504 IPv6 Node Requirements January 2019
6.5. Stateful Address Autoconfiguration (DHCPv6) - RFC 3315 . 16
6.6. Default Address Selection for IPv6 - RFC 6724 . . . . . . 16
7. DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8. Configuring Non-address Information . . . . . . . . . . . . . 17
8.1. DHCP for Other Configuration Information . . . . . . . . 17
8.2. Router Advertisements and Default Gateway . . . . . . . . 17
Show full document text