One document matched: draft-bonica-special-purpose-02.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="bcp" docName="draft-bonica-special-purpose-02"
ipr="trust200902" obsoletes="5156, 5735" updates="4773,5736">
<front>
<title abbrev="Special-Purpose Address Registries">Special-Purpose Address
Registries</title>
<author fullname="Michelle Cotton" initials="M" surname="Cotton">
<organization>Internet Corporation for Assigned Names and
Numbers</organization>
<address>
<postal>
<street>12025 Waterfront Drive, Suite 300</street>
<city>Los Angeles</city>
<region>CA</region>
<code>90094-2536</code>
<country>USA</country>
</postal>
<phone>+310-823-9358</phone>
<facsimile/>
<email>michelle.cotton@icann.org</email>
<uri>http://www.icann.org/</uri>
</address>
</author>
<author fullname="Leo Vegoda" initials="L" surname="Vegoda">
<organization>Internet Corporation for Assigned Names and
Numbers</organization>
<address>
<postal>
<street>12025 Waterfront Drive, Suite 300</street>
<city>LosAngeles</city>
<region>CA</region>
<code>90094-2536</code>
<country>USA</country>
</postal>
<phone>+310-823-9358</phone>
<facsimile/>
<email>leo.vegoda@icann.org</email>
<uri>http://www.icann.org/</uri>
</address>
</author>
<author fullname="Ronald P Bonica" initials="R." role="editor"
surname="Bonica">
<organization>Juniper Networks</organization>
<address>
<postal>
<street>2251 Corporate Park Drive</street>
<city>Herndon</city>
<code>20171</code>
<region>Virginia</region>
<country>USA</country>
</postal>
<email>rbonica@juniper.net</email>
</address>
</author>
<author fullname="Brian Haberman" initials="B." surname="Haberman">
<organization>Johns Hopkins University Applied Physics
Lab</organization>
<address>
<postal>
<street>11100 Johns Hopkins Road</street>
<city>Laurel</city>
<code>20723-6099</code>
<region>Maryland</region>
<country>USA</country>
</postal>
<email>brian@innovationslab.net</email>
</address>
</author>
<date day="28" month="September" year="2012"/>
<abstract>
<t>This memo instructs IANA to restructure its IPv4 and IPv6
Special-Purpose Address Registries. Upon restructuring, the
aforementioned registries will record all special-purpose address
blocks, maintaining a common set of information regarding each address
block.</t>
<t>This memo updates RFC 5736 and RFC 4773, which define the current
structure of the IPv4 and IPv6 Special-Purpose Address Registries. It
also obsoletes RFC 5735 and RFC 5156 which document special-purpose
address blocks that are not currently, but will in the future, be
recorded in the IPv4 and IPv6 Special-Purpose Address Registries.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>In order to support new protocols and practices, the IETF
occasionally reserves an address block a for special purpose. For
example, <xref target="RFC1122"/> reserves an IPv4 address block
(0.0.0.0/8) to represent the local (i.e., "this") network. Likewise,
<xref target="RFC4291"/> reserves an IPv6 address block (fe80::/10) to
represent link-scoped unicast addresses.</t>
<t>Periodically, the IETF publishes an RFC that catalogs special-purpose
address blocks. Currently, <xref target="RFC5735"/> catalogs all IPv4
special-purpose address blocks and <xref target="RFC5156"/> catalogs all
IPv6 special-purpose address blocks.</t>
<t><xref target="RFC5736"/> assigns an IPv4 address block (192.0.0.0/24)
to IANA and instructs IANA to allocate special-purpose address blocks
from this space. <xref target="RFC5736"/> also instructs IANA to create
an IPv4 Special-Purpose Address Registry that records allocations from
this address space. However, <xref target="RFC5736"/> does not instruct
IANA to record special-purpose address block reservations from outside
of the aforementioned space in the IPv4 Special-Purpose Address
Registry.</t>
<t>Likewise, <xref target="RFC2928"/> assigns an IPv6 address block
(2001:0000::/23) to IANA and instructs IANA to allocate special-purpose
address blocks from this space. <xref target="RFC4773"/> instructs IANA
to create an IPv6 Special-Purpose Address Registry that records
allocations from this address space. However, <xref target="RFC4773"/>
does not instruct IANA to record special-purpose address block
reservations from outside of the aforementioned space in the IPv6
Special-Purpose Address Registry.</t>
<t>This memo instructs IANA to restructure its IPv4 and IPv6
Special-Purpose Address Registries. Therefore, this document updates
<xref target="RFC5736"/> and <xref target="RFC4773"/> which define the
current structure of the aforementioned registries.</t>
<t>Specifically, this memo instructs IANA to record all special-purpose
address blocks in the aforementioned registries. These include, but are
not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6 allocations
from 2001:0000::/23. When the aforementioned registries include all
special-purpose address blocks, <xref target="RFC5735"/> and <xref
target="RFC5156"/> will become redundant with the registries. Therefore,
this memo obsoletes <xref target="RFC5735"/> and <xref
target="RFC5156"/>.</t>
<t>Furthermore, this memo defines:</t>
<t><list style="symbols">
<t>a common set of information that the registries will maintain
regarding each special-purpose address block</t>
<t>a common set of requirements for future entries</t>
</list></t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>IANA will restructure the following registries:</t>
<t><list style="symbols">
<t>IPv4 Special-Purpose Address Registry</t>
<t>IPv6 Special-Purpose Address Registry</t>
</list>The IPv4 Special-Purpose Address Registry will record all IPv4
special-purpose address blocks. These reservations will include, but not
be limited to, allocations from the 192.0.0.0/24 address block.
Likewise, the IPv6 Special-Purpose Address Registry will record all IPv6
special-purpose address blocks. These reservations will include, but not
be limited to, allocations from the 2001:0000::/23 address block.</t>
<t><xref target="InfoReqs"/> of this document describes information that
both registries will maintain for each entry. Initially, IANA will
populate the IPv4 Special-Purpose Address Registry with information
taken from <xref target="IPv4Entries"/> of this document. Likewise, IANA
will populate the IPv6 Special-Purpose Address Registry with information
taken from <xref target="IPv6Entries"/> of this document.</t>
<t>IANA will update the aforementioned registries as requested in the
"IANA Considerations" section of an IESG-reviewed document. The " IANA
Considerations" section must include all of the information specified in
<xref target="InfoReqs"/> of this document.</t>
<section anchor="InfoReqs" title="Information Requirements">
<t>The IPv4 and IPv6 Special-Purpose Address Registries will maintain
the following information regarding each entry:</t>
<t><list style="symbols">
<t>Prefix - An IPv4 or IPv6 prefix that identifies the
special-purpose address block</t>
<t>Name - A descriptive name for the special-purpose address
block</t>
<t>RFC - The RFC though which the special-purpose address block
was requested</t>
<t>Allocation Date - The date upon which the special purpose
address block was allocated</t>
<t>Termination Date - The date upon which the allocation is to be
terminated. This field is applicable for limited-use allocations
only.</t>
<t>Source - A boolean value indicated whether an address from the
allocated special-purpose address block is valid when used as the
source address of an IP datagram that transits two devices</t>
<t>Destination - A boolean value indicated whether an address from
the allocated special-purpose address block is valid when used as
the destination address of an IP datagram that transits two
devices</t>
<t>Routable - A boolean value indicating whether a IP datagram
whose destination address is drawn from the allocated
special-purpose address block is routable (i.e., may traverse more
than a single IP interface)</t>
<t>Global - A boolean value indicating whether a IP datagram whose
destination address is drawn from the allocated special-purpose
address block is routable beyond a specified administrative
domain.</t>
</list>If the value of "Destination" is FALSE, the values of
"Routable" and "Global" must also be false.</t>
</section>
<section anchor="IPv4Entries"
title="IPv4 Special-Purpose Address Registry Entries">
<t><xref target="IPv4T1"/> though <xref target="IPv4Tg"/>, below,
represent entries with which the IANA will initially populate the IPv4
Special-Purpose Address Registry.</t>
<texttable anchor="IPv4T1" style="full"
title=""This" Network">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>0.0.0.0/8</c>
<c>Name</c>
<c>"This" Network</c>
<c>RFC</c>
<c><xref target="RFC1122"/> Section 3.2.1.3</c>
<c>Allocation Date</c>
<c>September, 1981</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T2" title="Private-Use Networks">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>10.0.0.0/8</c>
<c>Name</c>
<c>Private-Use</c>
<c>RFC</c>
<c><xref target="RFC1918"/></c>
<c>Allocation Date</c>
<c>February 1996</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4Tz" title="Shared Address Space">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>100.64.0.0/10</c>
<c>Name</c>
<c>Shared Address Space</c>
<c>RFC</c>
<c><xref target="RFC6598"/></c>
<c>Allocation Date</c>
<c>April 2012</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T3" title="Loopback">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>127.0.0.0/8</c>
<c>Name</c>
<c>Loopback</c>
<c>RFC</c>
<c><xref target="RFC1122"/> Section 3.2.1.3</c>
<c>Allocation Date</c>
<c>September 1981</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T4" title="Link Local">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>169.254.0.0/16</c>
<c>Name</c>
<c>Link Local</c>
<c>RFC</c>
<c><xref target="RFC3927"/></c>
<c>Allocation Date</c>
<c>May 2005</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T5" title="Private-Use Networks">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>172.16.0.0/12</c>
<c>Name</c>
<c>Private-Use</c>
<c>RFC</c>
<c><xref target="RFC1122"/></c>
<c>Allocation Date</c>
<c>February 1996</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T6" title="IETF Protocol Assignments">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>192.0.0.0/24 [1]</c>
<c>Name</c>
<c>IETF Protocol Assignments</c>
<c>RFC</c>
<c><xref target="RFC5736"/></c>
<c>Allocation Date</c>
<c>January 2010</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<t>[1] Not useable unless by virtue of a more specific
reservation.</t>
<texttable anchor="IPv4T7" title="DS-Lite">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>192.0.0.0/29</c>
<c>Name</c>
<c>DS-Lite</c>
<c>RFC</c>
<c><xref target="RFC6333"/></c>
<c>Allocation Date</c>
<c>June 2011</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T8" title="TEST-NET-1">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>192.0.2.0/24</c>
<c>Name</c>
<c>Documentation (TEST-NET-1)</c>
<c>RFC</c>
<c><xref target="RFC5737"/></c>
<c>Allocation Date</c>
<c>January 2010</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4T9" title="6to4 Relay Anycast">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>192.88.99.0/24</c>
<c>Name</c>
<c>6to4 Relay Anycast</c>
<c>RFC</c>
<c><xref target="RFC3068"/></c>
<c>Allocation Date</c>
<c>June 2001</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>True</c>
</texttable>
<texttable anchor="IPv4Ta" title="Private-Use Networks">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>192.168.0.0/16</c>
<c>Name</c>
<c>Private-Use</c>
<c>RFC</c>
<c><xref target="RFC1918"/></c>
<c>Allocation Date</c>
<c>February 196</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>Flase</c>
</texttable>
<texttable anchor="IPv4Tb"
title="Network Interconnect Device Benchmark Testing">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>198.18.0.0/15</c>
<c>Name</c>
<c>Benchmarking</c>
<c>RFC</c>
<c><xref target="RFC2544"/></c>
<c>Allocation Date</c>
<c>March 1999</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4Tc" title="TEST-NET-2">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>198.51.100.0/24</c>
<c>Name</c>
<c>Documentation (TEST-NET-2)</c>
<c>RFC</c>
<c><xref target="RFC5737"/></c>
<c>Allocation Date</c>
<c>January 2010</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4Td" title="TEST-NET-3">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>203.0.113.0/24</c>
<c>Name</c>
<c>Documentation (TEST-NET-3)</c>
<c>RFC</c>
<c><xref target="RFC5737"/></c>
<c>Allocation Date</c>
<c>January 2010</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4Te" title="Multicast">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>224.0.0.0/4</c>
<c>Name</c>
<c>Multicast</c>
<c>RFC</c>
<c><xref target="RFC5771"/></c>
<c>Allocation Date</c>
<c>March 2010</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>N/A [2]</c>
</texttable>
<t>[2] See <xref target="RFC5771"/> for details.</t>
<texttable anchor="IPv4Tf" title="Reserved for Future Use">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>240.0.0.0/4</c>
<c>Name</c>
<c>Reserved</c>
<c>RFC</c>
<c><xref target="RFC1112"/> Section 4</c>
<c>Allocation Date</c>
<c>August 1989</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv4Tg" title="Limited Broadcast">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>255.255.255.255/32</c>
<c>Name</c>
<c>Limited Broadcast</c>
<c>RFC</c>
<c><xref target="RFC0919"/> Section 7</c>
<c>Allocation Date</c>
<c>October 1984</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
</section>
<section anchor="IPv6Entries"
title="IPv6 Special-Purpose Address Registry Entries">
<t><xref target="IPv6T1"/> through <xref target="IPv6Td"/>, below,
represent entries with which the IANA will initially populate the IPv6
Special-Purpose Address Registry.</t>
<texttable anchor="IPv6T1" title="Loopback Address">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>::1/128</c>
<c>Name</c>
<c>Loopback Address</c>
<c>RFC</c>
<c><xref target="RFC4291"/></c>
<c>Allocation Date</c>
<c>February 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T2" title="Unspecified Address">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>::/128</c>
<c>Name</c>
<c>Unspecified Address</c>
<c>RFC</c>
<c><xref target="RFC4291"/></c>
<c>Allocation Date</c>
<c>February 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T3" title="IPv4-mapped Address">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>::FFFF:0:0/96</c>
<c>Name</c>
<c>IPv4-mapped Address</c>
<c>RFC</c>
<c><xref target="RFC4291"/></c>
<c>Allocation Date</c>
<c>February 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T4" title="Discard-Only Prefix">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>0100::/64</c>
<c>Name</c>
<c>Discard-Only Prefix</c>
<c>RFC</c>
<c><xref target="RFC6666"/></c>
<c>Allocation Date</c>
<c>June 2012</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T5" title="IETF Protocol Assignments">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2001:0000::/23</c>
<c>Name</c>
<c>IETF Protocol Assignments</c>
<c>RFC</c>
<c><xref target="RFC2928"/></c>
<c>Allocation Date</c>
<c>September 2000</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False[3]</c>
<c>Destination</c>
<c>False[3]</c>
<c>Routable</c>
<c>False[3]</c>
<c>Global</c>
<c>False[3]</c>
</texttable>
<t>[3] Unless allowed by a more specific allocation</t>
<texttable anchor="IPv6T6" title="TEREDO">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2001:0000::/32</c>
<c>Name</c>
<c>TEREDO</c>
<c>RFC</c>
<c><xref target="RFC4380"/></c>
<c>Allocation Date</c>
<c>January 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T7" title="Benchmarking">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2001:0002::/48</c>
<c>Name</c>
<c>Benchmarking</c>
<c>RFC</c>
<c><xref target="RFC5180"/></c>
<c>Allocation Date</c>
<c>April 2008</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T8" title="Documentation">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2001:db8::/32</c>
<c>Name</c>
<c>Documentation</c>
<c>RFC</c>
<c><xref target="RFC3849"/></c>
<c>Allocation Date</c>
<c>July 2004</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6T9" title="ORCHID">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2001:10::/28</c>
<c>Name</c>
<c>ORCHID</c>
<c>RFC</c>
<c><xref target="RFC4843"/></c>
<c>Allocation Date</c>
<c>March 2007</c>
<c>Termination Date</c>
<c>March 2014</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>False</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6Ta" title="6to4">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>2002::/16 [4]</c>
<c>Name</c>
<c>6to4</c>
<c>RFC</c>
<c><xref target="RFC3056"/></c>
<c>Allocation Date</c>
<c>February 2001</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>N/A[4]</c>
</texttable>
<t>[4] See <xref target="RFC3056"/> for details.</t>
<texttable anchor="IPv6Tb" title="Unique-Local">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>FC00::/7</c>
<c>Name</c>
<c>Unique-Local</c>
<c>RFC</c>
<c><xref target="RFC4193"/></c>
<c>Allocation Date</c>
<c>October 2005</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6Tc" title="Linked-Scoped Unicast">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>FE80::/10</c>
<c>Name</c>
<c>Linked-Scoped Unicast</c>
<c>RFC</c>
<c><xref target="RFC4291"/></c>
<c>Allocation Date</c>
<c>February 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>True</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>False</c>
<c>Global</c>
<c>False</c>
</texttable>
<texttable anchor="IPv6Td" title="Multicast">
<ttcol>Attribute</ttcol>
<ttcol>Value</ttcol>
<c>Prefix</c>
<c>FF00::/8 [5]</c>
<c>Name</c>
<c>Multicast</c>
<c>RFC</c>
<c><xref target="RFC4291"/></c>
<c>Allocation Date</c>
<c>February 2006</c>
<c>Termination Date</c>
<c>N/A</c>
<c>Source</c>
<c>False</c>
<c>Destination</c>
<c>True</c>
<c>Routable</c>
<c>True</c>
<c>Global</c>
<c>N/A</c>
</texttable>
<t>[5] See <xref target="RFC4007"/> for global scoping details</t>
</section>
</section>
<section anchor="Security" 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
purpose address blocks that are designated from the IANA-administered
Special Purpose 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 anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to acknowledge an anonymous donor, without
whom this document would not have been written.</t>
</section>
</middle>
<back>
<references title="Informative References">
<?rfc ?>
<?rfc include="reference.RFC.5156" ?>
<?rfc include="reference.RFC.5735"?>
<?rfc include="reference.RFC.5736" ?>
<?rfc include="reference.RFC.4773"?>
<?rfc include="reference.RFC.1122"?>
<?rfc include="reference.RFC.2928" ?>
<?rfc include="reference.RFC.4291"?>
<?rfc include="reference.RFC.6666"?>
<?rfc include="reference.RFC.4380"?>
<?rfc include="reference.RFC.5180"?>
<?rfc include="reference.RFC.3849"?>
<?rfc include="reference.RFC.4843"?>
<?rfc include="reference.RFC.3056"?>
<?rfc include="reference.RFC.4193"?>
<?rfc include="reference.RFC.6598"?>
<?rfc include="reference.RFC.1918"?>
<?rfc include="reference.RFC.3927"?>
<?rfc include="reference.RFC.5737"?>
<?rfc include="reference.RFC.6333"?>
<?rfc include="reference.RFC.2544"?>
<?rfc include="reference.RFC.5771"?>
<?rfc include="reference.RFC.1112"?>
<?rfc include="reference.RFC.0919"?>
<?rfc include="reference.RFC.4007"?>
<?rfc include="reference.RFC.3068"?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-22 13:00:56 |