Internet Engineering Task Force (IETF) R. Housley Request for Comments: 7020 Vigil Security Obsoletes: 2050 J. Curran Category: Informational ARIN ISSN: 2070-1721 G. Huston APNIC D. Conrad Virtualized, LLC August 2013 The Internet Numbers Registry System
AbstractThis document provides information about the current Internet Numbers Registry System used in the distribution of globally unique Internet Protocol (IP) address space and autonomous system (AS) numbers. This document also provides information about the processes for further evolution of the Internet Numbers Registry System. This document replaces RFC 2050. This document does not propose any changes to the current Internet Numbers Registry System. Rather, it documents the Internet Numbers Registry System as it works today. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7020.
Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Internet Numbers Registry System Structure . . . . . . . . . . 3 4. Internet Numbers Registry Technical Considerations . . . . . . 5 5. Internet Numbers Registry Evolution . . . . . . . . . . . . . . 5 6. Summary of Changes since RFC 2050 . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 8 RFC 2050. Since the publication of RFC 2050, the Internet Numbers Registry System has changed significantly. This document describes the present Internet Numbers Registry System.
IETF The IETF specifies the underlying technical facilities and constraints of Internet numbers administered by the Internet Numbers Registry System. These specifications are aimed at enabling and protecting the long-term viability of the Internet, and adjustments to those specifications are made over time as circumstances warrant. The IETF has also reserved portions of the Internet number spaces and identifiers for future needs. IANA The Internet Assigned Numbers Authority (IANA) is a role, not an organization. For the Internet Numbers Registry System, the IANA role manages the top of the IP address and AS number allocation hierarchies. The Internet Corporation for Assigned Names and Numbers (ICANN) currently fulfills the IANA role in accordance with the IETF-ICANN "Memorandum of Understanding Concerning Technical Work of the Internet Assigned Numbers Authority", which was signed and ratified in March 2000 [RFC2860]. In addition, ICANN performs the IANA services related to the IP address space and AS numbers according to global number resource policies that have been developed by the community and formalized under a Memorandum of Understanding between ICANN and the Regional Internet Registries [ASOMOU] and documented in [ICANNv4], [ICANNv6], and [ICANNASN]. Regional IRs In order to promote distribution of the Internet number resource registration function, RFC 1366 proposed delegating responsibility to regional bodies. (Note: RFC 1366 was replaced by RFC 1466, which was replaced by RFC 2050.) These bodies became known as the Regional Internet Registries (RIRs). The RIRs operate in continent-sized geopolitical regions. Currently, there are five RIRs: AfriNIC serving Africa, APNIC serving parts of Asia and the Pacific region, ARIN serving North America and parts of the Caribbean, LACNIC serving Latin America and parts of the Caribbean, and RIPE NCC serving Europe, parts of Asia and the Middle East. The RIRs were established in a bottom-up fashion via a global policy process that has been documented as the ICANN "Internet Consensus Policy 2" [ICP-2], which details the principles and criteria for establishment of Regional Internet Registries. The RIRs also conduct regional number policy development used in the administration of the number resources for which they are responsible.
Local IRs Local Internet Registries (LIRs) are established through a relationship with the body from which they received their addresses, typically the RIR that serves the region in which they operate, a parent LIR, or other number-allocating entity. In cases where LIRs span multiple regions, those LIRs have established relationships with multiple RIRs. LIRs perform IP address allocation services for their customers, typically ISPs, end users, or child LIRs (also known as "sub-LIRs"). RFC5855]. 2) Public WHOIS: The policies and practices of the Internet Numbers Registry System have included consideration of the technical and operational requirements for supporting WHOIS services [RFC3013] [RFC3912]. As the Internet and the Internet Numbers Registry System continue to evolve, it may be necessary for the Internet community to examine these and related technical and operational considerations and how best to meet them. This evolution is discussed in the next section. RFC2860], discussions regarding the evolution of the Internet Numbers Registry System structure, policy, and processes are to take place within the ICANN framework and will respect ICANN's core values [ICANNBL]. These core
values encourage broad, informed participation reflecting the functional, geographic, and cultural diversity of the Internet at all levels of policy development and decision making, as well as the delegation of coordination functions and recognition of the policy roles of other responsible entities that reflect the interests of affected parties. The discussions regarding Internet Numbers Registry evolution must also continue to consider the overall Internet address architecture and technical goals referenced in this document. The foregoing does not alter the IETF's continued responsibility for the non-policy aspects of Internet addressing such as the architectural definition of IP address and AS number spaces and specification of associated technical goals and constraints in their application, assignment of specialized address blocks, and experimental technical assignments as documented in RFC 2860. In addition, in the cases where the IETF sets technical recommendations for protocols, practices, or services that are directly related to IP address space or AS numbers, such recommendations must be taken into consideration in Internet Numbers Registry System policy discussions regardless of venue. RFC 2050 was published, the Internet and the Internet Numbers Registry System have undergone significant change. This document describes the Internet Numbers Registry System as it presently exists and omits policy and operational procedures that have been superseded by ICANN and RIR policy since the publication of RFC 2050. One particular change of note is that RFC 2050 defined an appeal process and included: If necessary, after exhausting all other avenues, the appeal may be forwarded to IANA for a final decision. Each registry must, as part of their policy, document and specify how to appeal a registry assignment decision. The RIRs have developed consensus-based policies for appeals, and over time, they have become accepted by the respective RIR communities. As a result, the ability to further appeal to IANA is no longer appropriate.
RFC 1466 and RFC 2050 for their earlier contributions in this area. [ASOMOU] Published by ICANN, "ICANN Address Supporting Organization (ASO) MoU", October 2004, <http://archive.icann.org/en/aso/aso-mou-29oct04.htm>. [ICANNASN] Ratified by ICANN, "Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks to Regional Internet Registries", September 2010, <http://www.icann.org/en/resources/policy/global- addressing/global-policy-asn-blocks-21sep10-en.htm>. [ICANNBL] ICANN, "Bylaws for Internet Corporation for Assigned Names and Numbers", December 2012, <http://www.icann.org/en/about/governance/bylaws>. [ICANNv4] Ratified by ICANN, "Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA", May 2012, <http://www.icann.org/en/resources/policy/ global-addressing/allocation-ipv4-post-exhaustion>. [ICANNv6] Ratified by ICANN, "Internet Assigned Numbers Authority (IANA) Policy For Allocation of IPv6 Blocks to Regional Internet Registries", September 2006, <http://www.icann.org/en/resources/policy/ global-addressing/allocation-ipv6-rirs>. [ICP-2] ICANN, "ICP-2: Criteria for Establishment of New Regional Internet Registries", July 2001, <http://www.icann.org/icp/icp-2.htm>. [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, June 2000.
[RFC3013] Killalea, T., "Recommended Internet Service Provider Security Services and Procedures", BCP 46, RFC 3013, November 2000. [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, September 2004. [RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6 Reverse Zones", BCP 155, RFC 5855, May 2010.