idnits 2.17.1 draft-ietf-ospf-ospfv3-iid-registry-update-02.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5838, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5838, updated by this document, for RFC5378 checks: 2004-04-06) -- 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 (February 11, 2013) is 4091 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) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Retana 3 Internet-Draft Cisco Systems, Inc. 4 Updates: 5838 (if approved) D. Cheng 5 Intended status: Standards Track Huawei Technologies 6 Expires: August 15, 2013 February 11, 2013 8 OSPFv3 Instance ID Registry Update 9 draft-ietf-ospf-ospfv3-iid-registry-update-02 11 Abstract 13 This document modifies the "Unassigned" number space in the IANA 14 "OSPFv3 Instance ID Address Family Values" registry. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on August 15, 2013. 33 Copyright Notice 35 Copyright (c) 2013 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. OSPFv3 Instance ID Address Family Values Registry Update . . . 3 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 55 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 57 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 58 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 4 59 A.1. Changes between the -00 and -01 versions. . . . . . . . . . 4 60 A.2. Changes between the -01 and -02 versions. . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 [RFC5838] defined the "OSPFv3 Instance ID Address Family Values" 66 registry for the purpose of mapping OSPFv3 Instance IDs to different 67 address families. The following table lists the value ranges as 68 currently allocated. 70 +---------------------------+-------------------+-------------------+ 71 | Instance ID Range | Description | Assignment Policy | 72 +---------------------------+-------------------+-------------------+ 73 | Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned | 74 | Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned | 75 | Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned | 76 | Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned | 77 | Instance ID # 128 - # 255 | Unassigned | Standards Action | 78 +---------------------------+-------------------+-------------------+ 80 In some networks additional OSPFv3 instances may be required to 81 operationally identify specific applications. 83 2. OSPFv3 Instance ID Address Family Values Registry Update 85 The IANA "OSPFv3 Instance ID Address Family Values" registry must be 86 updated as follows: 88 +---------------------------+-------------+-----------------------+ 89 | Instance ID Range | Description | Assignment Policy | 90 +---------------------------+-------------+-----------------------+ 91 | Instance ID # 128 - # 191 | Unassigned | Standards Action | 92 | Instance ID # 192 - # 255 | Reserved | Private Use [RFC5226] | 93 +---------------------------+-------------+-----------------------+ 95 3. IANA Considerations 97 This document requests the modification of the "OSPFv3 Instance ID 98 Address Family Values" registry as described in Section 2. The 99 reference to [RFC5838] should be removed from the registry for the 100 modified ranges. 102 4. Security Considerations 104 This document modifies the assignment policy of an IANA registry 105 defined in [RFC5838]. It does not introduce any new security issues. 107 5. Acknowledgements 109 Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee and Pearl 110 Liang for their review and input. 112 6. References 114 6.1. Normative References 116 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 117 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 118 May 2008. 120 6.2. Informative References 122 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 123 Aggarwal, "Support of Address Families in OSPFv3", 124 RFC 5838, April 2010. 126 Appendix A. Change Log 128 A.1. Changes between the -00 and -01 versions. 130 o Eliminated rfc2119 keywords, section about Requirements Language 131 and corresponding reference. 133 o Updated acks. 135 A.2. Changes between the -01 and -02 versions. 137 o Added indicated that this draft updates rfc5838. 139 o Clarified the description of the 'Private Use' range to 140 'Reserved'. 142 o Added the need to remove the reference to rfc5838 from the updated 143 registry fields. 145 o Updated acks. 147 Authors' Addresses 149 Alvaro Retana 150 Cisco Systems, Inc. 151 7025 Kit Creek Rd. 152 Research Triangle Park, NC 27709 153 USA 155 Email: aretana@cisco.com 157 Dean Cheng 158 Huawei Technologies 159 2330 Central Expressway 160 Santa Clara, California 95050 161 USA 163 Email: dean.cheng@huawei.com