[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 RFC 7249

Internet-Draft                                                R. Housley
Intended Status: Informational                            Vigil Security
Expires: 7 August 2014                                   7 February 2014


                        Internet Numbers Registries
                 <draft-housley-number-registries-04.txt>

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) 2014 IETF Trust and the persons identified as the
   document authors. All rights reserved.








Housley                                                         [Page 1]

Internet Numbers Registries                                February 2014


   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

   In accordance with the IETF-IANA Memorandum of Understanding
   [RFC2860], 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

   Three IANA registries are associated with the Internet Numbers
   Registry System: AS Numbers, unicast IPv4 Addresses, and unicast IPv6
   Addresses.  However, in each case, there are special-purpose values,
   and those special-purpose values are outside the Internet Numbers
   Registry System.

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) public policy development processes.

   Some special-purpose AS numbers have been reserved.  Section 3 of
   this document establishes an IANA registry for special-purpose AS
   Numbers that have already been reserved.  Future additions to this
   registry can be made through "IETF Review" as defined in [RFC5226].
   Once a future reservation is approved, it is recorded in the special-
   purpose AS numbers registry with a reference to the IESG-approved RFC
   that documents the reservation.




Housley                                                         [Page 2]

Internet Numbers Registries                                February 2014


2.2.  IPv4 Addresses

   The allocation and registration functions for all non-reserved
   globally unique unicast IPv4 addresses are handled by the Internet
   Numbers Registry System in accordance with policies developed by the
   Regional Internet Registries (RIRs) public policy development
   processes.

   Reservations of special-purpose IPv4 addresses can be found in the
   IANA registry [IANA-IPv4-Reg].  Future additions to this registry can
   be made through "IETF Review" as defined in [RFC5226].  Once a future
   reservation is approved, it is recorded in the special-purpose IPv4
   address registry with a reference to the IESG-approved RFC that
   documents the reservation.

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 [RFC3513], 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 addresses are handled by the Internet
   Numbers Registry System in accordance with policies developed by the
   Regional Internet Registries (RIRs) public policy development
   processes.

   Reservations of special-purpose IPv6 addresses can be found in the
   IANA registry [IANA-IPv6-Reg].  Future additions to this registry can
   be made through "IETF Review" as defined in [RFC5226].  Once a future
   reservation is approved, it is recorded in the special-purpose IPv6
   address registry with a reference to the IESG-approved RFC that
   documents the reservation.

3.  IANA Considerations

   Please establish an IANA registry for special-purpose AS numbers.
   Future additions to this registry can be made through "IETF Review"
   as defined in [RFC5226].  At this time, the special-purpose AS
   numbers are:









Housley                                                         [Page 3]

Internet Numbers Registries                                February 2014


   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 by
                            [draft-ietf-idr-last-as-reservation]

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.

   Network operators should take care that special-purpose numbers and
   addresses are used on the public Internet in a manner that is
   consistent with their reserved purpose.

5.  References

5.1.  Normative References

   [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.

   [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
             IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
             2008.

   [RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The
             Internet Numbers Registry System", RFC 7020, August 2013.

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.

   [draft-ietf-idr-last-as-reservation]  Haas, J., and J. Mitchell,
             "Reservation of Last Autonomous System (AS) Numbers", work-
             in-progress, October 2013.



Housley                                                         [Page 4]

Internet Numbers Registries                                February 2014


   [IANA-IPv4-Reg]  http://www.iana.org/assignments/iana-ipv4-special-
             registry/iana-ipv4-special-registry.xml

   [IANA-IPv6-Reg]  http://www.iana.org/assignments/iana-ipv6-special-
             registry/iana-ipv6-special-registry.xml

   [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,
             selection, and registration of an Autonomous System (AS)",
             BCP 6, RFC 1930, March 1996.

   [RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6
             (IPv6) Addressing Architecture", RFC 3513, April 2003.

   [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for
             Documentation Use", RFC 5398, December 2008.

   [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
             Autonomous System (AS) Number Space", RFC 6793, December
             2012.

   [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for
             Private Use", BCP 6, RFC 6996, July 2013.

Acknowledgements

   Many thanks to Jari Arkko, Scott Bradner, Brian Carpenter, David
   Conrad, John Curran, David Farmer, Adrian Farrel, Stephen Farrell,
   Brian Haberman, Geoff Huston, George Michaelson, S. Moonesamy, and
   Thomas Narten 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 5]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/