idnits 2.17.1 draft-housley-number-registries-04.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 (7 February 2014) is 3730 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 3513 (Obsoleted by RFC 4291) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft R. Housley 3 Intended Status: Informational Vigil Security 4 Expires: 7 August 2014 7 February 2014 6 Internet Numbers Registries 7 9 Abstract 11 RFC 7020 provides information about the Internet Numbers Registry 12 System and how it is used in the distribution of autonomous system 13 (AS) numbers and globally unique unicast Internet Protocol (IP) 14 address space. 16 This companion document identifies the IANA registries that are part 17 of the Internet Numbers Registry System at this time. 19 Status of this Memo 21 This Internet-Draft is submitted to IETF in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as 27 Internet-Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/1id-abstracts.html 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html 40 Copyright and License Notice 42 Copyright (c) 2014 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 Internet Numbers Registries February 2014 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 1. Introduction 59 In accordance with the IETF-IANA Memorandum of Understanding 60 [RFC2860], RFC 7020 [RFC7020] provides information about the Internet 61 Numbers Registry System and how it is used in the distribution of 62 autonomous system (AS) numbers and globally unique unicast Internet 63 Protocol (IP) address space. 65 This companion document identifies the IANA registries that are part 66 of the Internet Numbers Registry System at this time. 68 2. Internet Numbers Registries 70 Three IANA registries are associated with the Internet Numbers 71 Registry System: AS Numbers, unicast IPv4 Addresses, and unicast IPv6 72 Addresses. However, in each case, there are special-purpose values, 73 and those special-purpose values are outside the Internet Numbers 74 Registry System. 76 2.1. Autonomous System Numbers 78 For historical reasons, there are 16-bit AS numbers and 32-bit AS 79 numbers. However, the 16-bit AS numbers are really just zero through 80 65535 of the 32-bit AS number space. 82 The allocation and registration functions for all non-reserved AS 83 numbers are handled by the Internet Numbers Registry System in 84 accordance with policies developed by the Regional Internet 85 Registries (RIRs) public policy development processes. 87 Some special-purpose AS numbers have been reserved. Section 3 of 88 this document establishes an IANA registry for special-purpose AS 89 Numbers that have already been reserved. Future additions to this 90 registry can be made through "IETF Review" as defined in [RFC5226]. 91 Once a future reservation is approved, it is recorded in the special- 92 purpose AS numbers registry with a reference to the IESG-approved RFC 93 that documents the reservation. 95 Internet Numbers Registries February 2014 97 2.2. IPv4 Addresses 99 The allocation and registration functions for all non-reserved 100 globally unique unicast IPv4 addresses are handled by the Internet 101 Numbers Registry System in accordance with policies developed by the 102 Regional Internet Registries (RIRs) public policy development 103 processes. 105 Reservations of special-purpose IPv4 addresses can be found in the 106 IANA registry [IANA-IPv4-Reg]. Future additions to this registry can 107 be made through "IETF Review" as defined in [RFC5226]. Once a future 108 reservation is approved, it is recorded in the special-purpose IPv4 109 address registry with a reference to the IESG-approved RFC that 110 documents the reservation. 112 2.3. IPv6 Addresses 114 The vast bulk of the IPv6 address space (approximately 7/8ths of the 115 whole address space) is reserved by the IETF [RFC3513], with the 116 expectation that further assignment of globally unique unicast 117 address space will be made from this reserved space in accordance 118 with future needs. 120 The allocation and registration functions for all non-reserved 121 globally unique unicast IPv6 addresses are handled by the Internet 122 Numbers Registry System in accordance with policies developed by the 123 Regional Internet Registries (RIRs) public policy development 124 processes. 126 Reservations of special-purpose IPv6 addresses can be found in the 127 IANA registry [IANA-IPv6-Reg]. Future additions to this registry can 128 be made through "IETF Review" as defined in [RFC5226]. Once a future 129 reservation is approved, it is recorded in the special-purpose IPv6 130 address registry with a reference to the IESG-approved RFC that 131 documents the reservation. 133 3. IANA Considerations 135 Please establish an IANA registry for special-purpose AS numbers. 136 Future additions to this registry can be made through "IETF Review" 137 as defined in [RFC5226]. At this time, the special-purpose AS 138 numbers are: 140 Internet Numbers Registries February 2014 142 AS Numbers Reason for Reservation 143 --------------------- ------------------------------------------- 144 0 Reserved by [draft-ietf-idr-as0] 145 23456 AS_TRANS; reserved by [RFC6793] 146 64496-64511 For documentation and sample code; reserved 147 by [RFC5398] 148 64512-65534 For private use; reserved by [RFC6996] 149 65535 Reserved by [RFC1930] 150 65536-65551 For documentation and sample code; reserved 151 by [RFC5398] 152 4200000000-4294967294 For private use; reserved by [RFC6996] 153 4294967295 Reserved by 154 [draft-ietf-idr-last-as-reservation] 156 4. Security Considerations 158 This document identifies the IANA registries that are part of the 159 Internet Numbers Registry System at this time. It does not change 160 the security posture of the Internet in any way. 162 Network operators should take care that special-purpose numbers and 163 addresses are used on the public Internet in a manner that is 164 consistent with their reserved purpose. 166 5. References 168 5.1. Normative References 170 [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of 171 Understanding Concerning the Technical Work of the Internet 172 Assigned Numbers Authority", RFC 2860, June 2000. 174 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 175 IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 176 2008. 178 [RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The 179 Internet Numbers Registry System", RFC 7020, August 2013. 181 5.2. Informative References 183 [draft-ietf-idr-as0] Kumari, W., R. Bush, H. Schiller, and K. Patel, 184 "Codification of AS 0 processing", work-in-progress, August 185 2012. 187 [draft-ietf-idr-last-as-reservation] Haas, J., and J. Mitchell, 188 "Reservation of Last Autonomous System (AS) Numbers", work- 189 in-progress, October 2013. 191 Internet Numbers Registries February 2014 193 [IANA-IPv4-Reg] http://www.iana.org/assignments/iana-ipv4-special- 194 registry/iana-ipv4-special-registry.xml 196 [IANA-IPv6-Reg] http://www.iana.org/assignments/iana-ipv6-special- 197 registry/iana-ipv6-special-registry.xml 199 [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, 200 selection, and registration of an Autonomous System (AS)", 201 BCP 6, RFC 1930, March 1996. 203 [RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 204 (IPv6) Addressing Architecture", RFC 3513, April 2003. 206 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 207 Documentation Use", RFC 5398, December 2008. 209 [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet 210 Autonomous System (AS) Number Space", RFC 6793, December 211 2012. 213 [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for 214 Private Use", BCP 6, RFC 6996, July 2013. 216 Acknowledgements 218 Many thanks to Jari Arkko, Scott Bradner, Brian Carpenter, David 219 Conrad, John Curran, David Farmer, Adrian Farrel, Stephen Farrell, 220 Brian Haberman, Geoff Huston, George Michaelson, S. Moonesamy, and 221 Thomas Narten for their insightful review and comment. 223 Author's Addresses 225 Russell Housley 226 Vigil Security, LLC 227 918 Spring Knoll Drive 228 Herndon, VA 20170 229 USA 230 EMail: housley@vigilsec.com