Internet-Draft R. Housley Intended Status: Informational Vigil Security Expires: 12 June 2014 12 December 2013 Internet Numbers Registries Abstract RFC 7020 provides information about the Internet Numbers Registry System and how it is used in the distribution of autonomous system (AS) numbers and globally unique unicast Internet Protocol (IP) address space. This companion document identifies the IANA registries that are part of the Internet Numbers Registry System at this time. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. Housley [Page 1] Internet Numbers Registries December 2013 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Introduction RFC 7020 [RFC7020] provides information about the Internet Numbers Registry System and how it is used in the distribution of autonomous system (AS) numbers and globally unique unicast Internet Protocol (IP) address space. This companion document identifies the IANA registries that are part of the Internet Numbers Registry System at this time. 2. Internet Numbers Registries Portions of three IANA registries are associated with the Internet Numbers Registry System: AS Numbers, IPv4 Addresses, and IPv6 Addresses. 2.1. Autonomous System Numbers For historical reasons, there are 16-bit AS numbers and 32-bit AS numbers. However, the 16-bit AS numbers are really just zero through 65535 of the 32-bit AS number space. The allocation and registration functions for all non-reserved AS numbers are handled by the Internet Numbers Registry System in accordance with policies developed by the Regional Internet Registries (RIRs). Reservations of special-purpose AS Numbers are made through Internet Standards actions. Housley [Page 2] Internet Numbers Registries December 2013 At this time, the special-purpose AS numbers are: AS Numbers Reason for Reservation --------------------- ------------------------------------------- 0 Reserved by [draft-ietf-idr-as0] 23456 AS_TRANS; reserved by [RFC6793] 64496-64511 For documentation and sample code; reserved by [RFC5398] 64512-65534 For private use; reserved by [RFC6996] 65535 Reserved by [RFC1930] 65536-65551 For documentation and sample code; reserved by [RFC5398] 4200000000-4294967294 For private use; reserved by [RFC6996] 4294967295 Reserved 2.2. IPv4 Addresses The allocation and registration functions for all non-reserved globally unique unicast IPv4 unicast addresses are handled by the Internet Numbers Registry System in accordance with policies developed by the Regional Internet Registries (RIRs). Reservation of special-purpose IPv4 addresses are made through Internet Standards actions. Reserved IPv4 unicast addresses are registered in the Special Purpose IP address registries [RFC6890]. At this time, the special-purpose IPv4 unicast addresses are: IPv4 Addresses Reason for Reservation --------------- ----------------------------------------------- 0/8 For self-identification; reserved by [RFC1122] 10/8 For private use; reserved by [RFC1918] 100.64/10 For shared address space; reserved by [RFC6598] 127/8 For loopback; reserved by [RFC1122] 169.254/16 For link local; reserved by [RFC3927] 172.16/12 For private use; reserved by [RFC1918] 192.0.0/24 For IETF protocol assignments; reserved by [RFC6890] 192.0.2/24 For documentation (TEST-NET-1); reserved by [RFC5737] 192.88.99/24 For 6to4 relay anycast; reserved by [RFC3068] 192.168/16 For private use; reserved by [RFC1918] 198.18/15 For benchmarking; reserved by [RFC2544] 198.51.100/24 For documentation (TEST-NET-2); reserved by [RFC5737] 203.0.113/24 For documentation (TEST-NET-3); reserved by [RFC5737] 240/4 Reserved by [RFC1112] Housley [Page 3] Internet Numbers Registries December 2013 2.3. IPv6 Addresses The vast bulk of the IPv6 address space (approximately 7/8ths of the whole address space) is reserved by the IETF, with the expectation that further assignment of globally unique unicast address space will be made from this reserved space in accordance with future needs. The allocation and registration functions for all non-reserved globally unique unicast IPv6 unicast addresses are handled by the Internet Numbers Registry System in accordance with policies developed by the Regional Internet Registries (RIRs). Reservation of special-purpose IPv6 addresses are made through Internet Standards actions. Reserved IPv6 unicast addresses are registered in the Special Purpose IP address Registries [RFC6890]. At this time, the special-purpose IPv6 addresses are: IPv6 Addresses Reason for Reservation -------------- ---------------------------------------------------- 0::/8 For unspecified, loopback, IPv4-compatible, IPv4- mapped, link-local, site-local, and addresses assigned by the IETF; reserved by [RFC4291] 100::/64 For discard-only addresses; reserved by [RFC6666] 2001:0::/23 For IETF protocol assignments; reserved by [RFC2928] 2001:db8::/32 For documentation; reserved by [RFC3849] 2002::/16 For 6to4; reserved by [RFC3056] 3. IANA Considerations "IETF Review" as defined in [RFC5226] is required to reserve special- purpose AS numbers or IPv4 addresses or IPv6 addresses. These reservations are recorded in the relevant IANA registry with a Special Purpose designation, referencing the IESG-approved RFC that documents the reservation. IANA may designate special-purpose AS numbers or IPv4 addresses or IPv6 addresses to support testing, IETF experimental activities, or other special uses (e.g., anycast) associated with a standards-track protocol. 4. Security Considerations This document identifies the IANA registries that are part of the Internet Numbers Registry System at this time. It does not change the security posture of the Internet in any way. Housley [Page 4] Internet Numbers Registries December 2013 5. References 5.1. Normative References [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 5.2. Informative References [draft-ietf-idr-as0] Kumari, W., R. Bush, H. Schiller, and K. Patel, "Codification of AS 0 processing", work-in-progress, August 2012. [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989. [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996. [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, selection, and registration of an Autonomous System (AS)", BCP 6, RFC 1930, March 1996. [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, March 1999. [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001. [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", RFC 3068, June 2001. [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004. [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic Configuration of IPv4 Link-Local Addresses", RFC 3927, May 2005. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for Housley [Page 5] Internet Numbers Registries December 2013 Documentation Use", RFC 5398, December 2008. [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks Reserved for Documentation", RFC 5737, January 2010. [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address Space", BCP 153, RFC 6598, April 2012. [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", RFC 6666, August 2012. [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet Autonomous System (AS) Number Space", RFC 6793, December 2012. [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, "Special-Purpose IP Address Registries", BCP 153, RFC 6890, April 2013. [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for Private Use", BCP 6, RFC 6996, July 2013. Acknowledgements Many thanks to Jari Arkko, John Curran and Geoff Huston for their insightful review and comment. Author's Addresses Russell Housley Vigil Security, LLC 918 Spring Knoll Drive Herndon, VA 20170 USA EMail: housley@vigilsec.com Housley [Page 6]