idnits 2.17.1 draft-ietf-6man-ndpioiana-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4861, updated by this document, for RFC5378 checks: 2004-07-16) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 29, 2018) is 2182 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group O. Troan 3 Internet-Draft Cisco Systems 4 Updates: 4861 (if approved) April 29, 2018 5 Intended status: Standards Track 6 Expires: October 31, 2018 8 IANA Considerations for IPv6 Neighbor Discovery Prefix Information 9 Option Flags 10 draft-ietf-6man-ndpioiana-03 12 Abstract 14 The Prefix Information Option in the IPv6 Neighbor Discovery Router 15 Advertisement message defines an 8-bit flag field with two flags 16 defined and the remaining 6 bits reserved (Reserved1). RFC 6275 has 17 defined a new flag from this field without creating a IANA registry 18 or updating RFC 4861. The purpose of this document is to request a 19 new IANA registry for the PIO flags. This document updates RFC 4861. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on October 31, 2018. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery 56 Router Advertisement defines an 8-bit flag field with two flags 57 defined and the remaining 6 bits reserved (Reserved1). RFC 6275 has 58 defined a new flag from this field without creating a IANA registry 59 or updating RFC 4861. The purpose of this document is to to create a 60 new registry for the PIO flags. 62 2. Current Prefix Information Option flags 64 Currently, the Neighbor Discovery Protocol Prefix Information Option 65 [RFC4861] contains the following one-bit flags defined in published 66 RFCs: 68 0 1 2 3 4 5 6 7 69 +-+-+-+-+-+-+-+-+ 70 |L|A|R|Reserved1| 71 +-+-+-+-+-+-+-+-+ 73 Figure 1 75 L - On-link Flag [RFC4861] 77 A - Autonomous Address Configuration Flag [RFC4861] 79 R - Router Address Agent Flag [RFC6275] 81 Reserved1 - Reserved 83 3. Updates to RFC4861 85 This document updates Section 4.6.2 "Prefix Information" of [RFC4861] 86 to point to the new IANA registry that is created in this document. 88 Specifically: The current list of flags in the Prefix Information 89 Option can be found in IANA-TBD. 91 4. IANA Considerations 93 The IANA is requested to create a new registry for IPv6 Neighbor 94 Discovery Prefix Information Option flags. This should include the 95 current flags in the PIO option. The format for the registry is: 97 +---------------+---------------------------------+-----------+ 98 | RA Option Bit | Description | Reference | 99 +---------------+---------------------------------+-----------+ 100 | 0 | L - On-link Flag | [RFC4861] | 101 | 1 | A - Autonomous Address | [RFC4861] | 102 | | Configuration Flag | | 103 | 2 | R - Router Address Flag | [RFC6275] | 104 | 3-7 | Reserved | | 105 +---------------+---------------------------------+-----------+ 107 Figure 2 109 The assignment of new flags in the PIO option header require 110 Standards Action. 112 The registry for these flags should be added to: 113 http://www.iana.org/assignments/icmpv6-parameters 115 5. Security Considerations 117 This document has no security considerations. 119 6. Normative References 121 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 122 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 123 DOI 10.17487/RFC4861, September 2007, 124 . 126 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 127 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 128 2011, . 130 Author's Address 132 Ole Troan 133 Cisco Systems 134 Philip Pedersens vei 1 135 Lysaker 1366 136 Norway 138 Email: ot@cisco.com