idnits 2.17.1 draft-retana-ospf-ospfv3-iid-registry-update-00.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 (September 26, 2012) is 4228 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: March 30, 2013 Huawei Technologies 6 September 26, 2012 8 OSPFv3 Instance ID Registry Update 9 draft-retana-ospf-ospfv3-iid-registry-update-00 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 March 30, 2013. 33 Copyright Notice 35 Copyright (c) 2012 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. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 52 3. OSPFv3 Instance ID Address Family Values Registry Update . . . 3 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 55 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 56 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 58 7.2. Informative References . . . . . . . . . . . . . . . . . . 4 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 61 1. Introduction 63 [RFC5838] defined the "OSPFv3 Instance ID Address Family Values" 64 registry for the purpose of mapping OSPFv3 Instance IDs to different 65 address families. The following table lists the value ranges as 66 currently allocated. 68 +---------------------------+-------------------+-------------------+ 69 | Instance ID Range | Description | Assignment Policy | 70 +---------------------------+-------------------+-------------------+ 71 | Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned | 72 | Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned | 73 | Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned | 74 | Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned | 75 | Instance ID # 128 - # 255 | Unassigned | Standards Action | 76 +---------------------------+-------------------+-------------------+ 78 In some networks additional OSPFv3 instances may be required to 79 operationally identify specific applications. 81 2. Requirements Language 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in [RFC2119]. 87 3. OSPFv3 Instance ID Address Family Values Registry Update 89 The IANA "OSPFv3 Instance ID Address Family Values" registry MUST be 90 updated as follows: 92 +---------------------------+-------------+-----------------------+ 93 | Instance ID Range | Description | Assignment Policy | 94 +---------------------------+-------------+-----------------------+ 95 | Instance ID # 128 - # 191 | Unassigned | Standards Action | 96 | Instance ID # 192 - # 255 | Unassigned | Private Use [RFC5226] | 97 +---------------------------+-------------+-----------------------+ 99 4. IANA Considerations 101 This document requests the modification of the "OSPFv3 Instance ID 102 Address Family Values" registry as described in Section 3. 104 5. Security Considerations 106 This document modifies the assignment policy of an IANA registry 107 defined in [RFC5838]. It does not introduce any new security issues. 109 6. Acknowledgements 111 Many thanks to Acee Lindem and Stewart Bryant for their input. 113 7. References 115 7.1. Normative References 117 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 118 Requirement Levels", BCP 14, RFC 2119, March 1997. 120 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 121 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 122 May 2008. 124 7.2. Informative References 126 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 127 Aggarwal, "Support of Address Families in OSPFv3", 128 RFC 5838, April 2010. 130 Authors' Addresses 132 Alvaro Retana 133 Cisco Systems, Inc. 134 7025 Kit Creek Rd. 135 Research Triangle Park, NC 27709 136 USA 138 Email: aretana@cisco.com 140 Dean Cheng 141 Huawei Technologies 142 2330 Central Expressway 143 Santa Clara, California 95050 144 USA 146 Email: dean.cheng@huawei.com