8425
PROPOSED STANDARD

IANA Considerations for IPv6 Neighbor Discovery Prefix Information Option Flags

Authors: O. Troan
Date: July 2018
Area: int
Working Group: 6man
Stream: IETF
Updates: RFC 4861
View on RFC Editor (HTML) Download PDF DOI

Abstract

The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery Router Advertisement message defines an 8-bit flag field; this field has two flags defined, and the remaining 6 bits are reserved (Reserved1). RFC 6275 defines a flag from this field without creating an IANA registry or updating RFC 4861. The purpose of this document is to create an IANA registry for the PIO flags. This document updates RFC 4861.

RFC 8425
Download TXTDownload PDF
RFC 8425: IANA Considerations for IPv6 Neighbor Discovery Prefix Information Option Flags [RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]

PROPOSED STANDARD
Internet Engineering Task Force (IETF)                          O. Troan
Request for Comments: 8425                                 Cisco Systems
Updates: <a href="./rfc4861">4861</a>                                                  July 2018
Category: Standards Track
ISSN: 2070-1721


            <span class="h1">IANA Considerations for IPv6 Neighbor Discovery</span>
                    <span class="h1">Prefix Information Option Flags</span>

Abstract

   The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery
   Router Advertisement message defines an 8-bit flag field; this field
   has two flags defined, and the remaining 6 bits are reserved
   (Reserved1).  <a href="./rfc6275">RFC 6275</a> defines a flag from this field without
   creating an IANA registry or updating <a href="./rfc4861">RFC 4861</a>.  The purpose of this
   document is to create an IANA registry for the PIO flags.  This
   document updates <a href="./rfc4861">RFC 4861</a>.

Status of This Memo

   This is an Internet Standards Track document.

   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
   Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc8425">https://www.rfc-editor.org/info/rfc8425</a>.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) 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.



<span class="grey">Troan                        Standards Track                    [Page 1]</span>
<span id="page-2" ></span>
<span class="grey"><a href="./rfc8425">RFC 8425</a>            IANA Considerations for PIO Flags          July 2018</span>


Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  Current Prefix Information Option Flags . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-3">3</a>.  Updates to <a href="./rfc4861">RFC 4861</a> . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-4">4</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-5">5</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-6">6</a>.  Normative References  . . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery
   Router Advertisement message defines an 8-bit flag field; this field
   has two flags defined and the remaining 6 bits are reserved
   (Reserved1).  <a href="./rfc6275">RFC 6275</a> defines a flag from this field without
   creating an IANA registry or updating <a href="./rfc4861">RFC 4861</a>.  The purpose of this
   document is to create a new registry for the PIO flags.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Current Prefix Information Option Flags</span>

   Currently, the Neighbor Discovery Protocol Prefix Information Option
   [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] contains the following one-bit flags defined in published
   RFCs:

                               0 1 2 3 4 5 6 7
                              +-+-+-+-+-+-+-+-+
                              |L|A|R|Reserved1|
                              +-+-+-+-+-+-+-+-+

                            Figure 1: PIO Flags

      L - On-link Flag [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]

      A - Autonomous Address Configuration Flag [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]

      R - Router Address Flag [<a href="./rfc6275" title=""Mobility Support in IPv6"">RFC6275</a>]

      Reserved1 - Reserved












<span class="grey">Troan                        Standards Track                    [Page 2]</span>
<span id="page-3" ></span>
<span class="grey"><a href="./rfc8425">RFC 8425</a>            IANA Considerations for PIO Flags          July 2018</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Updates to <a href="./rfc4861">RFC 4861</a></span>

   This document updates <a href="#section-4.6.2">Section 4.6.2</a> "Prefix Information" of [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]
   to point to the IANA registry that is created in this document (see
   <a href="#section-4">Section 4</a>).

   Specifically, the current list of flags in the Prefix Information
   Option can be found in the "IPv6 Neighbor Discovery Prefix
   Information Option Flags" registry.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   IANA has created a new registry for IPv6 Neighbor Discovery Prefix
   Information Option flags.  This registry includes the current flags
   in the PIO.  The initial contents of the registry are as follows:

       +----------------+---------------------------------+-----------+
       | PIO Option Bit | Description                     | Reference |
       +----------------+---------------------------------+-----------+
       | 0              | L - On-link Flag                | [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] |
       | 1              | A - Autonomous Address          | [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] |
       |                |     Configuration Flag          |           |
       | 2              | R - Router Address Flag         | [<a href="./rfc6275" title=""Mobility Support in IPv6"">RFC6275</a>] |
       | 3-7            | Reserved                        |           |
       +----------------+---------------------------------+-----------+

     Figure 2: IPv6 Neighbor Discovery Prefix Information Option Flags

   The assignment of new flags in the PIO option header requires
   Standards Action [<a href="./rfc8126" title="">RFC8126</a>].

   The registry for these flags is available at
   <<a href="http://www.iana.org/assignments/icmpv6-parameters">http://www.iana.org/assignments/icmpv6-parameters</a>>.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   This document has no security considerations.














<span class="grey">Troan                        Standards Track                    [Page 3]</span>
<span id="page-4" ></span>
<span class="grey"><a href="./rfc8425">RFC 8425</a>            IANA Considerations for PIO Flags          July 2018</span>


<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Normative References</span>

   [<a id="ref-RFC4861">RFC4861</a>]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
              "Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>,
              DOI 10.17487/RFC4861, September 2007,
              <<a href="https://www.rfc-editor.org/info/rfc4861">https://www.rfc-editor.org/info/rfc4861</a>>.

   [<a id="ref-RFC6275">RFC6275</a>]  Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
              Support in IPv6", <a href="./rfc6275">RFC 6275</a>, DOI 10.17487/RFC6275, July
              2011, <<a href="https://www.rfc-editor.org/info/rfc6275">https://www.rfc-editor.org/info/rfc6275</a>>.

   [<a id="ref-RFC8126">RFC8126</a>]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
              <a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
              <<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>.

Author's Address

   Ole Troan
   Cisco Systems
   Philip Pedersens vei 1
   Lysaker  1366
   Norway

   Email: [email protected]


























Troan                        Standards Track                    [Page 4]

Additional Resources