<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- ?rfc toc="yes"? -->
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<rfc category="bcp" docName="draft-huston-ipv6-iana-specials-01.txt" ipr="full3978" >
  <front>
    <title abbrev="IANA IPv6 Registry">Administration of the IANA Special Purpose Address Block</title>

    <author fullname="Geoff Huston" initials="G." surname="Huston">
      <organization abbrev="APNIC">Asia Pacific Network Information Centre</organization>

      <address>
        <postal></postal>
        <email>gih@apnic.net</email>
        <uri>http://www.apnic.net</uri>
      </address>
    </author>

    <date year="2005" />

    <area>Individual Submission</area>

    <workgroup>Individual Submission</workgroup>
    <abstract>
      <t>

      This is a direction to IANA concerning the management of
      the IANA Special Purpose IPv6 address assignment registry.

      </t>
    </abstract>

  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>

      This is a direction to IANA concerning the management of
      the IANA Special Purpose IPv6 address assignment registry.

      </t>
    </section>

    <section title="IANA IPv6 Special Purpose Address Block">
      <t>

      <xref target="RFC2928"/> specified the assignment of the IPv6 address prefix to
      IANA.  The rationale for this allocation is:

       <list>
      <t>

      "The block of Sub-TLA IDs assigned to the IANA (i.e.,
      2001:0000::/29 - 2001:01F8::/29) is for assignment for testing
      and experimental usage to support activities such as the 6bone,
      and for new approaches like exchanges."

      </t><t>
      <xref target="RFC2928"/>
      </t>
      </list>
      </t>
      <t>

      This address allocation to IANA was intended to support testing
      and experimental activities.  A more general view of the roles
      of IANA with respect to address allocation functions is
      documented in <xref target="RFC2860"/>:

      <list>
      <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.)"

      </t><t>
      <xref target="RFC2860"/>
      </t>
      </list>
      </t>
      <t>

      The reference to section 4 here is to the general technical work
      for the IANA:

      <list>
      <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."      

      </t><t>
      <xref target="RFC2860"/>
      </t>
      </list>
      </t>
      <t>
   
      This document directs IANA to undertake designation of special
      purpose address blocks within the purview of direct assignments
      by the IANA under the terms of the assignment criteria specified
      in RFC 2928.

      </t>
      <t>

      This document directs IANA to open a Special Purpose IPv6 address
      registry for the management of these IANA-designated address
      blocks. Special Purpose registrations to be made from this registry
      include addresses for experimental purposes, as described in
      <xref target="RFC2928"/>, 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 is directed to maintain an "IANA IPv6 Address Special
      Purpose Registry". The registry is to record current IANA
      address designations from the IANA-managed Special Purpose IPv6
      address pool.

      </t>
      <t>

      This recommendation concerns the management of the address pool
      assigned by the IETF to the IANA in July 1999 by <xref
      target="RFC2928"/>, namely 2001:0000::/23. Further assignments
      of address space to IANA for subsequent designation of address
      prefixes for the purposes listed here shall be undertaken only
      in response to direction to IANA provided by the IETF in a
      IESG-reviewed RFC document.  Such directions for assignments of
      address space to augment the IANA-managed special purpose
      address pool should, in the general course of events, be
      consistent with prevailing IANA IPv6 address management policies
      <xref target="IPv6-Policies" />.

      </t>
      <t>

      The IANA may undertake IPv6 address designations in support of
      special purposes as requested in "IANA Considerations" sections
      in IESG-reviewed RFCs, where a unicast 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 within an anycast
      use context associated with an Internet Standards track
      protocol.

      </t>
      <t>

      The IANA IPv6 Special Purpose Address Registry shall record for
      all current address designations undertaken by IANA:

      <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 (unicast
      experiment or protocol service anycast).

      </t>
      <t>

      If the purpose is an experimental unicast application, as
      distinct from an anycast service address, then 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>
      </list>
      </t>
      <t>
     
      The IANA registry shall note as a general comment that address
      prefixes listed in the 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 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>

      The proposed registry is intended to provide an authoritative
      source of information regarding the currency and intended
      purpose of special use IPv6 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 IANA
      registry publication formats that are machine parseable, and
      also 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>

      The document was prepared with the assistance of Leslie Daigle,
      Brian Haberman, Bob Hinden, David Kessens, Kurt Lindqvist,
      Thomas Narten and Paul Wilson.

      </t>
     </section>
  </middle>

  <back>
    <references title="Informative References">
      <?rfc include='./rfcs/bibxml/reference.RFC.2860.xml'?>
      <?rfc include='./rfcs/bibxml/reference.RFC.2928.xml'?>

<reference anchor="IPv6-Policies">
<front>
<title>IPv6 Allocation and Assignment Policy</title>
<author surname="IANA" fullname="IANA"><organization /> </author>
<date month="June" day="26" year="2005" />
</front>
<format type="TXT" target="http://www.iana.org/ipaddress/ipv6-allocation-policy-26jun02"/>
</reference>
    </references>
  </back>
</rfc>