idnits 2.17.1 draft-housley-number-registries-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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (15 December 2013) is 3782 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC7020' is mentioned on line 59, but not defined == Missing Reference: 'RFC1112' is mentioned on line 136, but not defined ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 3068 (Obsoleted by RFC 7526) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 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: 15 June 2014 15 December 2013 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) 2013 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 Internet Numbers Registries December 2013 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 RFC 7020 [RFC7020] provides information about the Internet Numbers 60 Registry System and how it is used in the distribution of autonomous 61 system (AS) numbers and globally unique unicast Internet Protocol 62 (IP) address space. 64 This companion document identifies the IANA registries that are part 65 of the Internet Numbers Registry System at this time. 67 2. Internet Numbers Registries 69 Portions of three IANA registries are associated with the Internet 70 Numbers Registry System: AS Numbers, IPv4 Addresses, and IPv6 71 Addresses. 73 2.1. Autonomous System Numbers 75 For historical reasons, there are 16-bit AS numbers and 32-bit AS 76 numbers. However, the 16-bit AS numbers are really just zero through 77 65535 of the 32-bit AS number space. 79 The allocation and registration functions for all non-reserved AS 80 numbers are handled by the Internet Numbers Registry System in 81 accordance with policies developed by the Regional Internet 82 Registries (RIRs). 84 Reservations of special-purpose AS Numbers are made through Internet 85 Standards actions. 87 Internet Numbers Registries December 2013 89 At this time, the special-purpose AS numbers are: 91 AS Numbers Reason for Reservation 92 --------------------- ------------------------------------------- 93 0 Reserved by [draft-ietf-idr-as0] 94 23456 AS_TRANS; reserved by [RFC6793] 95 64496-64511 For documentation and sample code; reserved 96 by [RFC5398] 97 64512-65534 For private use; reserved by [RFC6996] 98 65535 Reserved by [RFC1930] 99 65536-65551 For documentation and sample code; reserved 100 by [RFC5398] 101 4200000000-4294967294 For private use; reserved by [RFC6996] 102 4294967295 Reserved 104 2.2. IPv4 Addresses 106 The allocation and registration functions for all non-reserved 107 globally unique unicast IPv4 unicast addresses are handled by the 108 Internet Numbers Registry System in accordance with policies 109 developed by the Regional Internet Registries (RIRs). 111 Reservation of special-purpose IPv4 addresses are made through 112 Internet Standards actions. Reserved IPv4 unicast addresses are 113 registered in the Special Purpose IP address registries [RFC6890]. 115 At this time, the special-purpose IPv4 unicast addresses are: 117 IPv4 Addresses Reason for Reservation 118 --------------- ----------------------------------------------- 119 0/8 For self-identification; reserved by [RFC1122] 120 10/8 For private use; reserved by [RFC1918] 121 100.64/10 For shared address space; reserved by [RFC6598] 122 127/8 For loopback; reserved by [RFC1122] 123 169.254/16 For link local; reserved by [RFC3927] 124 172.16/12 For private use; reserved by [RFC1918] 125 192.0.0/24 For IETF protocol assignments; reserved 126 by [RFC6890] 127 192.0.2/24 For documentation (TEST-NET-1); reserved 128 by [RFC5737] 129 192.88.99/24 For 6to4 relay anycast; reserved by [RFC3068] 130 192.168/16 For private use; reserved by [RFC1918] 131 198.18/15 For benchmarking; reserved by [RFC2544] 132 198.51.100/24 For documentation (TEST-NET-2); reserved 133 by [RFC5737] 134 203.0.113/24 For documentation (TEST-NET-3); reserved 135 by [RFC5737] 136 240/4 Reserved by [RFC1112] 138 Internet Numbers Registries December 2013 140 2.3. IPv6 Addresses 142 The vast bulk of the IPv6 address space (approximately 7/8ths of the 143 whole address space) is reserved by the IETF, with the expectation 144 that further assignment of globally unique unicast address space will 145 be made from this reserved space in accordance with future needs. 147 The allocation and registration functions for all non-reserved 148 globally unique unicast IPv6 unicast addresses are handled by the 149 Internet Numbers Registry System in accordance with policies 150 developed by the Regional Internet Registries (RIRs). 152 Reservation of special-purpose IPv6 addresses are made through 153 Internet Standards actions. Reserved IPv6 unicast addresses are 154 registered in the Special Purpose IP address Registries [RFC6890]. 156 At this time, the special-purpose IPv6 addresses are: 158 IPv6 Addresses Reason for Reservation 159 -------------- ---------------------------------------------------- 160 0::/8 For unspecified, loopback, IPv4-compatible, IPv4- 161 mapped, link-local, site-local, and addresses 162 assigned by the IETF; reserved by [RFC4291] 163 100::/64 For discard-only addresses; reserved by [RFC6666] 164 2001:0::/23 For IETF protocol assignments; reserved by [RFC2928] 165 2001:db8::/32 For documentation; reserved by [RFC3849] 166 2002::/16 For 6to4; reserved by [RFC3056] 168 3. IANA Considerations 170 "IETF Review" as defined in [RFC5226] is required to reserve special- 171 purpose AS numbers, IPv4 addresses, or IPv6 addresses. Reserved AS 172 numbers, IPv4 addresses, or IPv6 addresses may be designated to 173 support testing, IETF experimental activities, or other special uses 174 (e.g., anycast). These reservations are recorded in the relevant 175 IANA registry with a Special Purpose designation, referencing the 176 IESG-approved RFC that documents the reservation. 178 4. Security Considerations 180 This document identifies the IANA registries that are part of the 181 Internet Numbers Registry System at this time. It does not change 182 the security posture of the Internet in any way. 184 Internet Numbers Registries December 2013 186 5. References 188 5.1. Normative References 190 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 191 IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 192 2008. 194 5.2. Informative References 196 [draft-ietf-idr-as0] Kumari, W., R. Bush, H. Schiller, and K. Patel, 197 "Codification of AS 0 processing", work-in-progress, August 198 2012. 200 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 201 Communication Layers", STD 3, RFC 1122, October 1989. 203 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 204 and E. Lear, "Address Allocation for Private Internets", 205 BCP 5, RFC 1918, February 1996. 207 [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, 208 selection, and registration of an Autonomous System (AS)", 209 BCP 6, RFC 1930, March 1996. 211 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 212 Network Interconnect Devices", RFC 2544, March 1999. 214 [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial 215 IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. 217 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via 218 IPv4 Clouds", RFC 3056, February 2001. 220 [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", 221 RFC 3068, June 2001. 223 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 224 Reserved for Documentation", RFC 3849, July 2004. 226 [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic 227 Configuration of IPv4 Link-Local Addresses", RFC 3927, May 228 2005. 230 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 231 Architecture", RFC 4291, February 2006. 233 Internet Numbers Registries December 2013 235 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 236 Documentation Use", RFC 5398, December 2008. 238 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 239 Reserved for Documentation", RFC 5737, January 2010. 241 [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and 242 M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address 243 Space", BCP 153, RFC 6598, April 2012. 245 [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", 246 RFC 6666, August 2012. 248 [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet 249 Autonomous System (AS) Number Space", RFC 6793, December 250 2012. 252 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 253 "Special-Purpose IP Address Registries", BCP 153, RFC 6890, 254 April 2013. 256 [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for 257 Private Use", BCP 6, RFC 6996, July 2013. 259 Acknowledgements 261 Many thanks to Jari Arkko, John Curran and Geoff Huston for their 262 insightful review and comment. 264 Author's Addresses 266 Russell Housley 267 Vigil Security, LLC 268 918 Spring Knoll Drive 269 Herndon, VA 20170 270 USA 271 EMail: housley@vigilsec.com