Network Working Group G. Huston
Internet-Draft APNIC
Intended status: Informational M. Cotton
Expires: August 28, 2009 L. Vegoda
ICANN
February 24, 2009
IANA IPv4 Special Purpose Address Registry
draft-iana-special-ipv4-registry-00
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/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 28, 2009.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This is a direction to IANA concerning the management of the IANA
Huston, et al. Expires August 28, 2009 [Page 1]
Internet-Draft IPv4 Special Registry February 2009
Special Purpose IPv4 address assignment registry.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IANA IPv4 Special Purpose Address Block . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
6. Informative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Huston, et al. Expires August 28, 2009 [Page 2]
Internet-Draft IPv4 Special Registry February 2009
1. Introduction
This is a direction to IANA concerning the management of the IANA
Special Purpose IPv4 address assignment registry.
2. IANA IPv4 Special Purpose Address Block
[rfc3330bis] records the assignment of an IPv4 address prefix to IANA
for IETF protocol assignments.
"192.0.0.0/24 - This block is reserved for IETF protocol
assignments."
This address allocation to IANA is intended to support IETF protocol
assignments. A more general view of the roles of IANA with respect
to address allocation functions is documented in [RFC2860]:
"4.3. [...] Note that [...] (b) assignments of specialised address
blocks (such as multicast or anycast blocks), and (c) experimental
assignments are not considered to be policy issues, and shall remain
subject to the provisions of this Section 4. (For purposes of this
MOU, the term "assignments" includes allocations.)" [RFC2860]
The reference to section 4 here is to the general technical work for
the IANA:
"4.1. The IANA will assign and register Internet protocol parameters
only as directed by the criteria and procedures specified in RFCs,
including Proposed, Draft, and full Internet Standards and Best
Current Practice documents, and any other RFC that calls for IANA
assignment." [RFC2860]
This document directs IANA to undertake designation of special
purpose address blocks within the purview of direct assignments by
the IANA.
This document directs IANA to open a Special Purpose IPv4 address
registry for the management of these IANA-designated address blocks.
Special Purpose registrations to be made from this registry include
addresses for IETF protocol assignments and other special purpose
cases, as documented in IESG-reviewed published RFCs, according to
the provisions described in section 4.1 of [RFC2860].
3. IANA Considerations
IANA maintains an "IANA IPv4 Address Special Purpose Registry". The
Huston, et al. Expires August 28, 2009 [Page 3]
Internet-Draft IPv4 Special Registry February 2009
registry records current IANA address designations from the IANA-
managed Special Purpose IPv4 address pool.
This recommendation concerns the management of the address pool used
for IETF protocol assignments as documented in [rfc3330bis] in
[date], namely 192.0.0.0/24. Following the policies outlined in
[RFC5226], further assignments of address space to IANA for
subsequent designation of address prefixes for the purposes listed
here shall be undertaken only through an IETF Review action.
IANA may undertake IPv4 address designations in support of special
purposes as requested in "IANA Considerations" sections in IESG-
reviewed RFCs, where an address is requested with an intended use of
the designated address block for the purpose of testing or
experimental usage activities initiated by IETF, or for specialised
use of the address block in a context (e.g., anycast) associated with
an Internet Standards track protocol.
The IANA IPv4 Special Purpose Address Registry records, for all
current address designations undertaken by IANA:
1. The designated address prefix.
2. The RFC that called for the IANA address designation.
3. The date the designation was made.
4. The date the use designation is to be terminated (if specified as
a limited-use designation).
5. The nature of the purpose of the designated address (e.g.,
unicast experiment or protocol service anycast).
6. For experimental unicast applications and otherwise as
appropriate, the registry will also identify the entity and
related contact details to whom the address designation has been
made.
7. The registry will also note, for each designation, the intended
routing scope of the address, indicating whether the address is
intended to be routable only in scoped, local, or private
contexts, or whether the address prefix is intended to be routed
globally.
8. The date in the IANA registry is the date of the IANA action,
i.e., the day IANA records the allocation.
The IANA registry notes, as a general comment, that address prefixes
Huston, et al. Expires August 28, 2009 [Page 4]
Internet-Draft IPv4 Special Registry February 2009
listed in the Special Purpose Address Registry are not guaranteed
routability in any particular local or global context.
IANA will not maintain further sub-registries for any special purpose
address block designated according to this direction.
4. Security Considerations
Security of the Internet's routing system relies on the ability to
authenticate an assertion of unique control of an address block.
Measures to authenticate such assertions rely on validation that the
address block forms part of an existing allocated address block, and
that there is a trustable and unique reference in the IANA address
registries.
The proposed registry is intended to provide an authoritative source
of information regarding the currency and intended purpose of special
use IPv4 address blocks that are designated from the IANA-
administered Special Use registry. This is a small step towards the
creation of a comprehensive registry framework that can be used as a
trust point for commencing a chain of address validation.
Consideration should be given to the use of file signatures and
associated certificate mechanisms to allow applications to confirm
that the registry contents are current, and that they have been
published by the IANA.
5. Acknowledgements
This document is based on [RFC4773], which was prepared with the
assistance of Leslie Daigle, Brian Haberman, Bob Hinden, David
Kessens, Kurt Lindqvist, Thomas Narten, and Paul Wilson. While all
these individuals were not explicitly consulted in the preparation of
this document, their original original contribution is acknowledged
here.
6. Informative References
[IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/
Registration Procedures",
<http://www.iana.org/numbers.html>.
[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.
Huston, et al. Expires August 28, 2009 [Page 5]
Internet-Draft IPv4 Special Registry February 2009
[RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial
IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000.
[RFC4773] Huston, G., "Administration of the IANA Special Purpose
IPv6 Address Block", RFC 4773, December 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
Authors' Addresses
Geoff Huston
Asia Pacific Network Information Centre
PO Box 2131
Milton, QLD 4064
Australia
Phone: +61-7-3858-3100
Email: gih@apnic.net
URI: http://www.apnic.net/
Michelle Cotton
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
USA
Phone: ++1-310-823-9358
Email: michelle.cotton@icann.org
URI: http://www.iana.org/
Leo Vegoda
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
USA
Phone: ++1-310-823-9358
Email: leo.vegoda@icann.org
URI: http://www.iana.org/
Huston, et al. Expires August 28, 2009 [Page 6]
