idnits 2.17.1 draft-ietf-ospf-ospfv3-iid-registry-update-01.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 -- The document date (January 22, 2013) is 4084 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 (==), 1 comment (--). 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 Intended status: Standards Track D. Cheng 5 Expires: July 26, 2013 Huawei Technologies 6 January 22, 2013 8 OSPFv3 Instance ID Registry Update 9 draft-ietf-ospf-ospfv3-iid-registry-update-01 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 July 26, 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 62 1. Introduction 64 [RFC5838] defined the "OSPFv3 Instance ID Address Family Values" 65 registry for the purpose of mapping OSPFv3 Instance IDs to different 66 address families. The following table lists the value ranges as 67 currently allocated. 69 +---------------------------+-------------------+-------------------+ 70 | Instance ID Range | Description | Assignment Policy | 71 +---------------------------+-------------------+-------------------+ 72 | Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned | 73 | Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned | 74 | Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned | 75 | Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned | 76 | Instance ID # 128 - # 255 | Unassigned | Standards Action | 77 +---------------------------+-------------------+-------------------+ 79 In some networks additional OSPFv3 instances may be required to 80 operationally identify specific applications. 82 2. OSPFv3 Instance ID Address Family Values Registry Update 84 The IANA "OSPFv3 Instance ID Address Family Values" registry must be 85 updated as follows: 87 +---------------------------+-------------+-----------------------+ 88 | Instance ID Range | Description | Assignment Policy | 89 +---------------------------+-------------+-----------------------+ 90 | Instance ID # 128 - # 191 | Unassigned | Standards Action | 91 | Instance ID # 192 - # 255 | Unassigned | Private Use [RFC5226] | 92 +---------------------------+-------------+-----------------------+ 94 3. IANA Considerations 96 This document requests the modification of the "OSPFv3 Instance ID 97 Address Family Values" registry as described in Section 2. 99 4. Security Considerations 101 This document modifies the assignment policy of an IANA registry 102 defined in [RFC5838]. It does not introduce any new security issues. 104 5. Acknowledgements 106 Many thanks to Acee Lindem, Stewart Bryant and Nevil Brownlee for 107 their review and input. 109 6. References 111 6.1. Normative References 113 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 114 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 115 May 2008. 117 6.2. Informative References 119 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 120 Aggarwal, "Support of Address Families in OSPFv3", 121 RFC 5838, April 2010. 123 Appendix A. Change Log 125 A.1. Changes between the -00 and -01 versions. 127 o Eliminated rfc2119 keywords, section about Requirements Language 128 and corrsponding reference. 130 o Updated acks. 132 Authors' Addresses 134 Alvaro Retana 135 Cisco Systems, Inc. 136 7025 Kit Creek Rd. 137 Research Triangle Park, NC 27709 138 USA 140 Email: aretana@cisco.com 141 Dean Cheng 142 Huawei Technologies 143 2330 Central Expressway 144 Santa Clara, California 95050 145 USA 147 Email: dean.cheng@huawei.com