[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-troan-6man-ndpioiana) 00 01 02 03 04

Network Working Group                                           O. Troan
Internet-Draft                                             Cisco Systems
Updates: 4861 (if approved)                               April 30, 2018
Intended status: Standards Track
Expires: November 1, 2018


   IANA Considerations for IPv6 Neighbor Discovery Prefix Information
                              Option Flags
                      draft-ietf-6man-ndpioiana-04

Abstract

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

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   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
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 1, 2018.

Copyright Notice

   Copyright (c) 2018 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



Troan                   Expires November 1, 2018                [Page 1]


Internet-Draft                                                April 2018


   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.

1.  Introduction

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

2.  Current Prefix Information Option flags

   Currently, the Neighbor Discovery Protocol Prefix Information Option
   [RFC4861] contains the following one-bit flags defined in published
   RFCs:


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

                                 Figure 1

      L - On-link Flag [RFC4861]

      A - Autonomous Address Configuration Flag [RFC4861]

      R - Router Address Agent Flag [RFC6275]

      Reserved1 - Reserved

3.  Updates to 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.

   Specifically: The current list of flags in the Prefix Information
   Option can be found in IANA-TBD.

4.  IANA Considerations

   The IANA is requested to create a new registry for IPv6 Neighbor
   Discovery Prefix Information Option flags.  This should include the
   current flags in the PIO option.  The format for the registry is:



Troan                   Expires November 1, 2018                [Page 2]


Internet-Draft                                                April 2018


       +---------------+---------------------------------+-----------+
       | RA Option Bit | Description                     | Reference |
       +---------------+---------------------------------+-----------+
       | 0             | L - On-link Flag                | [RFC4861] |
       | 1             | A - Autonomous Address          | [RFC4861] |
       |               |     Configuration Flag          |           |
       | 2             | R - Router Address Flag         | [RFC6275] |
       | 3-7           | Reserved                        |           |
       +---------------+---------------------------------+-----------+


                                 Figure 2

   The assignment of new flags in the PIO option header require
   Standards Action [RFC8126].

   The registry for these flags should be added to:
   http://www.iana.org/assignments/icmpv6-parameters

5.  Security Considerations

   This document has no security considerations.

6.  Normative References

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

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

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

Author's Address

   Ole Troan
   Cisco Systems
   Philip Pedersens vei 1
   Lysaker  1366
   Norway

   Email: ot@cisco.com



Troan                   Expires November 1, 2018                [Page 3]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/