draft-ietf-6man-ndpioiana-04.txt | rfc8425.txt | |||
---|---|---|---|---|
Network Working Group O. Troan | Internet Engineering Task Force (IETF) O. Troan | |||
Internet-Draft Cisco Systems | Request for Comments: 8425 Cisco Systems | |||
Updates: 4861 (if approved) April 30, 2018 | Updates: 4861 July 2018 | |||
Intended status: Standards Track | Category: Standards Track | |||
Expires: November 1, 2018 | ISSN: 2070-1721 | |||
IANA Considerations for IPv6 Neighbor Discovery Prefix Information | IANA Considerations for IPv6 Neighbor Discovery | |||
Option Flags | Prefix Information Option Flags | |||
draft-ietf-6man-ndpioiana-04 | ||||
Abstract | Abstract | |||
The Prefix Information Option in the IPv6 Neighbor Discovery Router | The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery | |||
Advertisement message defines an 8-bit flag field with two flags | Router Advertisement message defines an 8-bit flag field; this field | |||
defined and the remaining 6 bits reserved (Reserved1). RFC 6275 has | has two flags defined, and the remaining 6 bits are reserved | |||
defined a new flag from this field without creating a IANA registry | (Reserved1). RFC 6275 defines a flag from this field without | |||
or updating RFC 4861. The purpose of this document is to request a | creating an IANA registry or updating RFC 4861. The purpose of this | |||
new IANA registry for the PIO flags. This document updates RFC 4861. | document is to create an IANA registry for the PIO flags. This | |||
document updates RFC 4861. | ||||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This is an Internet Standards Track document. | |||
provisions of BCP 78 and BCP 79. | ||||
Internet-Drafts are working documents of the Internet Engineering | ||||
Task Force (IETF). Note that other groups may also distribute | ||||
working documents as Internet-Drafts. The list of current Internet- | ||||
Drafts is at https://datatracker.ietf.org/drafts/current/. | ||||
Internet-Drafts are draft documents valid for a maximum of six months | This document is a product of the Internet Engineering Task Force | |||
and may be updated, replaced, or obsoleted by other documents at any | (IETF). It represents the consensus of the IETF community. It has | |||
time. It is inappropriate to use Internet-Drafts as reference | received public review and has been approved for publication by the | |||
material or to cite them other than as "work in progress." | Internet Engineering Steering Group (IESG). Further information on | |||
Internet Standards is available in Section 2 of RFC 7841. | ||||
This Internet-Draft will expire on November 1, 2018. | 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/rfc8425. | ||||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | ||||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | ||||
2. Current Prefix Information Option Flags . . . . . . . . . . . 2 | ||||
3. Updates to RFC 4861 . . . . . . . . . . . . . . . . . . . . . 3 | ||||
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 | ||||
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 | ||||
6. Normative References . . . . . . . . . . . . . . . . . . . . 4 | ||||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 | ||||
1. Introduction | 1. Introduction | |||
The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery | The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery | |||
Router Advertisement defines an 8-bit flag field with two flags | Router Advertisement message defines an 8-bit flag field; this field | |||
defined and the remaining 6 bits reserved (Reserved1). RFC 6275 has | has two flags defined and the remaining 6 bits are reserved | |||
defined a new flag from this field without creating a IANA registry | (Reserved1). RFC 6275 defines a flag from this field without | |||
or updating RFC 4861. The purpose of this document is to to create a | creating an IANA registry or updating RFC 4861. The purpose of this | |||
new registry for the PIO flags. | document is to create a new registry for the PIO flags. | |||
2. Current Prefix Information Option flags | 2. Current Prefix Information Option Flags | |||
Currently, the Neighbor Discovery Protocol Prefix Information Option | Currently, the Neighbor Discovery Protocol Prefix Information Option | |||
[RFC4861] contains the following one-bit flags defined in published | [RFC4861] contains the following one-bit flags defined in published | |||
RFCs: | RFCs: | |||
0 1 2 3 4 5 6 7 | 0 1 2 3 4 5 6 7 | |||
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ | |||
|L|A|R|Reserved1| | |L|A|R|Reserved1| | |||
+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+ | |||
Figure 1 | Figure 1: PIO Flags | |||
L - On-link Flag [RFC4861] | L - On-link Flag [RFC4861] | |||
A - Autonomous Address Configuration Flag [RFC4861] | A - Autonomous Address Configuration Flag [RFC4861] | |||
R - Router Address Agent Flag [RFC6275] | R - Router Address Flag [RFC6275] | |||
Reserved1 - Reserved | Reserved1 - Reserved | |||
3. Updates to RFC4861 | 3. Updates to RFC 4861 | |||
This document updates Section 4.6.2 "Prefix Information" of [RFC4861] | This document updates Section 4.6.2 "Prefix Information" of [RFC4861] | |||
to point to the new IANA registry that is created in this document. | to point to the IANA registry that is created in this document (see | |||
Section 4). | ||||
Specifically: The current list of flags in the Prefix Information | Specifically, the current list of flags in the Prefix Information | |||
Option can be found in IANA-TBD. | Option can be found in the "IPv6 Neighbor Discovery Prefix | |||
Information Option Flags" registry. | ||||
4. IANA Considerations | 4. IANA Considerations | |||
The IANA is requested to create a new registry for IPv6 Neighbor | IANA has created a new registry for IPv6 Neighbor Discovery Prefix | |||
Discovery Prefix Information Option flags. This should include the | Information Option flags. This registry includes the current flags | |||
current flags in the PIO option. The format for the registry is: | in the PIO. The initial contents of the registry are as follows: | |||
+---------------+---------------------------------+-----------+ | +----------------+---------------------------------+-----------+ | |||
| RA Option Bit | Description | Reference | | | PIO Option Bit | Description | Reference | | |||
+---------------+---------------------------------+-----------+ | +----------------+---------------------------------+-----------+ | |||
| 0 | L - On-link Flag | [RFC4861] | | | 0 | L - On-link Flag | [RFC4861] | | |||
| 1 | A - Autonomous Address | [RFC4861] | | | 1 | A - Autonomous Address | [RFC4861] | | |||
| | Configuration Flag | | | | | Configuration Flag | | | |||
| 2 | R - Router Address Flag | [RFC6275] | | | 2 | R - Router Address Flag | [RFC6275] | | |||
| 3-7 | Reserved | | | | 3-7 | Reserved | | | |||
+---------------+---------------------------------+-----------+ | +----------------+---------------------------------+-----------+ | |||
Figure 2 | Figure 2: IPv6 Neighbor Discovery Prefix Information Option Flags | |||
The assignment of new flags in the PIO option header require | The assignment of new flags in the PIO option header requires | |||
Standards Action [RFC8126]. | Standards Action [RFC8126]. | |||
The registry for these flags should be added to: | The registry for these flags is available at | |||
http://www.iana.org/assignments/icmpv6-parameters | <http://www.iana.org/assignments/icmpv6-parameters>. | |||
5. Security Considerations | 5. Security Considerations | |||
This document has no security considerations. | This document has no security considerations. | |||
6. Normative References | 6. Normative References | |||
[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, | |||
DOI 10.17487/RFC4861, September 2007, | DOI 10.17487/RFC4861, September 2007, | |||
End of changes. 19 change blocks. | ||||
54 lines changed or deleted | 63 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |