One document matched: draft-ietf-6man-iana-routing-header-00.xml

<?xml version="1.0" encoding="iso-8859-1" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<rfc ipr="trust200902"
     docName="draft-ietf-6man-iana-routing-header-00"
     category="std"
     updates="2460">

<?rfc toc="no"?> <?rfc symrefs="yes"?> <?rfc autobreaks="yes"?>
<?rfc tocindent="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?>

<front>

<title abbrev="IPv6 RH IANA Rules">IANA Allocation Guidelines for the IPv6 Routing Header</title>

<author initials="J" surname="Arkko" fullname="Jari Arkko">
<organization>Ericsson</organization>
<address>
<postal>
<street/>
<city>Jorvas</city> <code>02420</code>
<country>Finland</country>
</postal>
<email>jari.arkko@piuha.net</email>
</address>
</author>

<author initials='S.' surname='Bradner' fullname='Scott Bradner'>
<organization>Harvard University</organization>
<address>
<postal>
<street />
<city>Cambridge</city>
<region>MA</region>
<code>02138</code>
<country>US</country></postal>
<phone>+1 617 495 3864</phone>
<email>sob@harvard.edu</email></address></author>

<date month="October" year="2009" />

<keyword>IANA rules</keyword>
<keyword>IPv6</keyword>
<keyword>Routing Header</keyword>

<abstract>

<t>This document specifies the IANA guidelines for allocating new
values for the Routing Type field in the IPv6 Routing Header.</t>

</abstract>

</front>
<middle>

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

<t>This document specifies the IANA guidelines
<xref target='RFC5226'/> for allocating new values for the Routing
Type field in the IPv6 Routing Header <xref target="RFC2460"/>.
Previously, no IANA guidance existed for
such allocations.</t>

</section>

<section anchor="ianarules" title="IANA Considerations">

<t>New Routing Type values are allocated through IETF Review or
IESG Approval <xref target="RFC5226"/>.</t>

<t>Note that two experimental values (253 and 254) are already
available for use <xref target="RFC4727"/>.</t>

</section>

<section title='Security Considerations'>

<t>This specification does not change the security properties of the
Routing Header. However, past experience shows that it is easy to
design routing headers that have significant problems
<xref target="RFC5095"/>.</t>

</section>

</middle>
<back>

<references title="Normative References">
      <?rfc include="reference.RFC.2460.xml"?>
      <?rfc include="reference.RFC.5226.xml"?>
</references>

<references title="Informative References">
      <?rfc include="reference.RFC.4727.xml"?>
      <?rfc include="reference.RFC.5095.xml"?>
</references>

<section title="Changes from RFC 2460">

<t>This document specifies only the IANA rules associated with the
Routing Type field.</t>

</section>

</back>
</rfc>