One document matched: draft-iana-special-ipv4-registry-01.xml
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc strict="yes"?>
<?rfc tocompact="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc tocdepth="2"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes" ?>
<!--<?rfc rfcedstyle="yes"?>-->
<?rfc sortrefs="yes" ?>
<!-- noModification3978 -->
<rfc category="info" ipr="trust200811" docName="draft-iana-special-ipv4-registry-01">
<front>
<title abbrev="IPv4 Special Registry">
IANA IPv4 Special Purpose Address Registry
</title>
<author initials="G." surname="Huston" fullname="Geoff Huston">
<organization abbrev="APNIC">
Asia Pacific Network Information Centre
</organization>
<address>
<postal>
<street>PO Box 2131</street>
<code>4064</code> <city>Milton, QLD</city>
<country>Australia</country>
</postal>
<phone>+61-7-3858-3100</phone>
<email>gih@apnic.net</email>
<uri>
http://www.apnic.net/
</uri>
</address>
</author>
<author initials="M." surname="Cotton" fullname="Michelle Cotton">
<organization abbrev="ICANN">
Internet Corporation for Assigned Names and Numbers
</organization>
<address>
<postal>
<street>4676 Admiralty Way, Suite 330</street>
<code>90292-6601</code> <city>Marina del Rey, CA</city>
<country>USA</country>
</postal>
<phone>++1-310-823-9358</phone>
<email>michelle.cotton@icann.org</email>
<uri>
http://www.iana.org/
</uri>
</address>
</author>
<author initials="L." surname="Vegoda" fullname="Leo Vegoda">
<organization abbrev="ICANN">
Internet Corporation for Assigned Names and Numbers
</organization>
<address>
<postal>
<street>4676 Admiralty Way, Suite 330</street>
<code>90292-6601</code> <city>Marina del Rey, CA</city>
<country>USA</country>
</postal>
<phone>++1-310-823-9358</phone>
<email>leo.vegoda@icann.org</email>
<uri>
http://www.iana.org/
</uri>
</address>
</author>
<date month="February" year="2009"/>
<keyword>IPv4</keyword>
<keyword>Special</keyword>
<keyword>Registry</keyword>
<keyword>IANA</keyword>
<abstract>
<t>
This is a direction to IANA concerning the creation and management of
the IANA IPv4 Special Purpose Address Registry.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
This is a direction to IANA concerning the creation and management of
the IANA IPv4 Special Purpose Address Registry. The registry will 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, as
described in section 3.
</t>
</section>
<section title="IANA IPv4 Special Purpose Address Block">
<t>
[rfc3330bis] records the assignment of an IPv4 address prefix to
IANA for IETF protocol assignments.
</t>
<t>
"192.0.0.0/24 - This block is reserved for IETF protocol
assignments."
</t>
<t>
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
<xref target="RFC2860"/>:
</t>
<t>
"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.)" <xref target="RFC2860"/>
</t>
<t>
The reference to section 4 here is to the general technical work for
the IANA:
</t>
<t>
"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." <xref target="RFC2860"/>
</t>
<t>
This document directs IANA to designate special purpose address blocks
in compliance with [RFC2860].
</t>
<t>
This document directs IANA to open an IPv4 Special Purpose 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 <xref target="RFC2860"/>.
</t>
</section>
<section title="IANA Considerations">
<t>
IANA maintains an "IANA IPv4 Special Purpose Address Registry". The
registry records current IANA address designations from the IANA-
managed IPv4 Special Purpose address pool.
</t>
<t>
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
<xref target="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.
</t>
<t>
IANA may make Special Purpose address designations to support testing or
experimental usage activities initiated by IETF, or for specialised use
of a designated address block in a context (e.g. anycast) associated
with an Internet Standards track protocol. All such address designations
must be documented in the "IANA Considerations" section of an
IESG-reviewed RFC.
</t>
<t>
The IANA IPv4 Special Purpose Address Registry records, for all
current address designations undertaken by IANA:
</t>
<t>
<list style="numbers">
<t>The designated address prefix.</t>
<t>The RFC that called for the IANA address designation.</t>
<t>The date the designation was made.</t>
<t>The date the use designation is to be terminated (if specified as
a limited-use designation).</t>
<t>The nature of the purpose of the designated address (e.g.
unicast experiment or protocol service anycast).</t>
<t>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.</t>
<t>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.</t>
<t>The date in the IANA registry is the date of the IANA action,
i.e. the day IANA records the allocation.</t>
</list>
</t>
<t>
The IANA registry notes, as a general comment, that address prefixes
listed in the IPv4 Special Purpose Address Registry are not guaranteed
routability in any particular local or global context.
</t>
<t>
IANA will not maintain further sub-registries for any IPv4 Special Purpose
address block designated according to this direction.
</t>
</section>
<section title="Security Considerations">
<t>
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.
</t>
<t>
This registry is intended to provide an authoritative source
of information regarding the currency and intended purpose of
IPv4 Special Purpose address blocks that are designated from the IANA-
administered IPv4 Special Purpose address pool. 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.
</t>
</section>
<section title="Acknowledgements">
<t>
This document is based on <xref target="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
contribution is acknowledged here.
</t>
</section>
</middle>
<!-- REFERENCE TEMPLATE
<reference anchor="reference.XXX">
<front>
<title>XXX</title>
<author initials="X." surname="XXX" fullname="XXX">
<organization abbrev="XXX">XXX</organization>
<address>
<postal>
<street>XXX</street>
<city>XXX</city>
<region>XXX</region>
<code>XXX</code>
<country>XXX</country>
</postal>
<phone>XXX</phone>
<facsimile>XXX</facsimile>
<email>XXX</email>
<uri>XXX</uri>
</address>
</author>
<date month="XXX" year="XXX"/>
</front>
<seriesInfo name="XXX" value="XXX"/>
<format type="XXX" target="XXX"/>
</reference>
-->
<back>
<references title='Informative References'>
<reference anchor="IANA" target="http://www.iana.org/numbers.html">
<front>
<title>IANA Matrix for Protocol Parameter Assignment/Registration Procedures</title>
<author fullname="IANA"><organization>IANA</organization></author>
</front>
</reference>
<?rfc include="reference.RFC.2860" ?>
<?rfc include="reference.RFC.2928" ?>
<?rfc include="reference.RFC.4773" ?>
<?rfc include="reference.RFC.5226" ?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 23:25:10 |