< draft-iana-special-ipv4-registry-01.txt   draft-iana-special-ipv4-registry-02.txt >
Network Working Group G. Huston Network Working Group G. Huston
Internet-Draft APNIC Internet-Draft APNIC
Intended status: Informational M. Cotton Intended status: Informational M. Cotton
Expires: August 31, 2009 L. Vegoda Expires: February 12, 2010 L. Vegoda
ICANN ICANN
February 27, 2009 August 11, 2009
IANA IPv4 Special Purpose Address Registry IANA IPv4 Special Purpose Address Registry
draft-iana-special-ipv4-registry-01 draft-iana-special-ipv4-registry-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 31, 2009. This Internet-Draft will expire on February 12, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 7 skipping to change at page 3, line 7
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IANA IPv4 Special Purpose Address Block . . . . . . . . . . . . 3 2. IANA IPv4 Special Purpose Address Block . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
6. Informative References . . . . . . . . . . . . . . . . . . . . 5 6. Informative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
This is a direction to IANA concerning the creation and management of This is a direction to [IANA] concerning the creation and management
the IANA IPv4 Special Purpose Address Registry. The registry will be of the IANA IPv4 Special Purpose Address Registry. The registry will
used for recording IETF protocol assignments from 192.0.0.0/24 and be used for recording IETF protocol assignments from 192.0.0.0/24 and
any other address prefixes allocated to the registry in the future, any other address prefixes allocated to the registry in the future,
as described in section 3. as described in section 3.
2. IANA IPv4 Special Purpose Address Block 2. IANA IPv4 Special Purpose Address Block
[rfc3330bis] records the assignment of an IPv4 address prefix to IANA [I-D.iana-rfc3330bis] records the assignment of an IPv4 address
for IETF protocol assignments. prefix to IANA for IETF protocol assignments.
"192.0.0.0/24 - This block is reserved for IETF protocol "192.0.0.0/24 - This block is reserved for IETF protocol
assignments." assignments."
This address allocation to IANA is intended to support IETF protocol This address allocation to IANA is intended to support IETF protocol
assignments. A more general view of the roles of IANA with respect assignments. A more general view of the roles of IANA with respect
to address allocation functions is documented in [RFC2860]: to address allocation functions is documented in [RFC2860]:
"4.3. [...] Note that [...] (b) assignments of specialised address "4.3. [...] Note that [...] (b) assignments of specialised address
blocks (such as multicast or anycast blocks), and (c) experimental blocks (such as multicast or anycast blocks), and (c) experimental
skipping to change at page 4, line 12 skipping to change at page 4, line 12
cases, as documented in IESG-reviewed published RFCs, according to cases, as documented in IESG-reviewed published RFCs, according to
the provisions described in section 4.1 of [RFC2860]. the provisions described in section 4.1 of [RFC2860].
3. IANA Considerations 3. IANA Considerations
IANA maintains an "IANA IPv4 Special Purpose Address Registry". The IANA maintains an "IANA IPv4 Special Purpose Address Registry". The
registry records current IANA address designations from the IANA- registry records current IANA address designations from the IANA-
managed IPv4 Special Purpose address pool. managed IPv4 Special Purpose address pool.
This recommendation concerns the management of the address pool used This recommendation concerns the management of the address pool used
for IETF protocol assignments as documented in [rfc3330bis] in for IETF protocol assignments as documented in [rfc3330bis], namely
[date], namely 192.0.0.0/24. Following the policies outlined in 192.0.0.0/24. Following the policies outlined in [RFC5226], further
[RFC5226], further assignments of address space to IANA for assignments of address space to IANA for subsequent designation of
subsequent designation of address prefixes for the purposes listed address prefixes for the purposes listed here shall be undertaken
here shall be undertaken only through an IETF Review action. only through an IETF Review action.
IANA may make Special Purpose address designations to support testing IANA may make Special Purpose address designations to support testing
or experimental usage activities initiated by IETF, or for or experimental usage activities initiated by IETF, or for
specialised use of a designated address block in a context (e.g. specialised use of a designated address block in a context (e.g.
anycast) associated with an Internet Standards track protocol. All anycast) associated with an Internet Standards track protocol. All
such address designations must be documented in the "IANA such address designations must be documented in the "IANA
Considerations" section of an IESG-reviewed RFC. Considerations" section of an IESG-reviewed RFC.
The IANA IPv4 Special Purpose Address Registry records, for all The IANA IPv4 Special Purpose Address Registry records, for all
current address designations undertaken by IANA: current address designations undertaken by IANA:
skipping to change at page 5, line 42 skipping to change at page 5, line 42
5. Acknowledgements 5. Acknowledgements
This document is based on [RFC4773], which was prepared with the This document is based on [RFC4773], which was prepared with the
assistance of Leslie Daigle, Brian Haberman, Bob Hinden, David assistance of Leslie Daigle, Brian Haberman, Bob Hinden, David
Kessens, Kurt Lindqvist, Thomas Narten, and Paul Wilson. While all Kessens, Kurt Lindqvist, Thomas Narten, and Paul Wilson. While all
these individuals were not explicitly consulted in the preparation of these individuals were not explicitly consulted in the preparation of
this document, their original contribution is acknowledged here. this document, their original contribution is acknowledged here.
6. Informative References 6. Informative References
[I-D.iana-rfc3330bis]
Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
draft-iana-rfc3330bis-07 (work in progress), June 2009.
[IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/ [IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/
Registration Procedures", Registration Procedures",
<http://www.iana.org/numbers.html>. <http://www.iana.org/numbers.html>.
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority", RFC 2860, June 2000. Internet Assigned Numbers Authority", RFC 2860, June 2000.
[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 [RFC4773] Huston, G., "Administration of the IANA Special Purpose
IPv6 Address Block", RFC 4773, December 2006. IPv6 Address Block", RFC 4773, December 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
Authors' Addresses Authors' Addresses
Geoff Huston Geoff Huston
 End of changes. 9 change blocks. 
17 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/