One document matched: draft-fairhurst-ipdvb-ule-iana-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc category="std" docName="draft-fairhurst-ipdvb-ule-iana-00"
     ipr="trust200902" obsoletes="" updates="4326">
  <!-- Updates SDP -->

  <?rfc toc="yes"?>

  <!-- generate a table of contents -->

  <?rfc symrefs="yes"?>

  <!-- use anchors instead of numbers for references -->

  <?rfc sortrefs="yes" ?>

  <!-- alphabetize the references -->

  <?rfc compact="yes" ?>

  <!-- conserve vertical whitespace -->

  <?rfc subcompact="no" ?>

  <!-- but keep a blank line between list items -->

  <front>
    <title abbrev="IANA ULE guidelines">IANA Guidance for Managing the ULE
    Registry</title>

    <author fullname="Godred Fairhurst" initials="G." surname="Fairhurst">
      <organization>University of Aberdeen</organization>

      <address>
        <postal>
          <street>School of Engineering</street>

          <street>Fraser Noble Building</street>

          <city>Aberdeen</city>

          <region>Scotland</region>

          <code>AB24 3UE</code>

          <country>UK</country>
        </postal>

        <email>gorry@erg.abdn.ac.uk</email>

        <uri>http://www.erg.abdn.ac.uk</uri>
      </address>
    </author>

    <date day="14" month="February" year="2013" />

    <area>Transport</area>

    <workgroup>IPDVB Working Group</workgroup>

    <keyword>ULE</keyword>

    <keyword>IANA</keyword>

    <abstract>
      <t>This document proposes an update to RFC 4326 to clarify and update
      the allocation rules for the Unidirectional Lightweight Encapsulation
      (ULE) next header registry. This registry is used by ULE and Generic
      Stream Encapsulation (GSE) to record the codepoints of extension headers
      and protocols supported by these encapsulation protocols.</t>
    </abstract>
  </front>

  <middle>
    <!-- text starts here -->

    <section title="Introduction" toc="include">
      <t>The Unidirectional Lightweight Encapsulation (ULE) <xref
      target="RFC4326"></xref> specifies an encapsulation for links that
      employ the MPEG-2 Transport Stream, with support over a wide variety of
      physical-layer bearers <xref target="RFC4259"></xref>. The encapsulation
      header includes a Type field that identifies payload types and extension
      headers (e.g.<xref target="RFC5163"> </xref>). The ULE specification
      requested IANA to maintain the ULE next header registries to record the
      allocation of the values used to construct this Type field.</t>

      <t>The Digital Video Broadcast (DVB) Project has published an
      encapsulation for second-generation DVB physical layers. This specifies
      the Generic Stream Encapsulation <xref target="GSE"></xref>. This
      encapsulation shares many of the network properties of ULE and uses a
      common format for the Type field <xref target="RFC5163"></xref>. The ULE
      Next Header registries are therefore also applicable to this
      encapsulation.</t>

      <section title="The ULE Next Header Registries">
        <t>The Mandatory Extension Headers registry allocates values in the
        range 0-255. These values are used to identify mandatory extension
        headers. The registered value corresponds to the 16-bit Type value for
        the mandatory extension header or the specified protocol.</t>

        <t>The Optional Extension Headers registry allocates values in the
        range 256-512. These values are used to identify optional extension
        headers. The registered value corresponds to the 16-bit Type value
        that would be used for an optional extension header with a length
        (H-LEN) of 1.</t>
      </section>
    </section>

    <section title="Terminology" toc="include">
      <t>This document assumes familiarity with the terminology of ULE <xref
      target="RFC4326"></xref> and <xref target="RFC5163"></xref>.</t>

      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119"></xref>.</t>
    </section>

    <section title="Updated IANA guidance on allocation in the ULE Next Header Registry"
             toc="include">
      <t>The rules for allocation are defined in section 11 of RFC 4326.
      Requirements for the request of a registry entry are provided in RFC
      4326. This document updates these rules in the following way:</t>

      <t>Allocations in the ULE Next Header Registry are to be assigned by
      IANA using the "Expert Review" policy defined in <xref
      target="RFC5226"></xref>. Applications for registration are expected to
      include a reference to a published specification of the extension in a
      standards document (e.g. such a reference to an RFC). The requirements
      for specification of the two types of extension header are in section 11
      of RFC 4326.</t>

      <t>XXX An alternate approach to writing this section could be to include
      a complete replacement text, based on RFC 4326 IANA considerations.
      XXX</t>

      <section title="Reservation of port values">
        <t>This document reserves the range decimal 144-159 (0x80-0x8F). These
        reserved values are presently not available for general assignment,
        and will not be allocated until the registry is exhausted.</t>
      </section>
    </section>

    <section title="Update to registry information" toc="default">
      <t>This section requests IANA to record additional explanatory note in
      the registry:</t>

      <t>"The Mandatory Extension Headers registry allocates values in the
      range 0-255. These values are used to identify mandatory extension
      headers. The registered value corresponds to the 16-bit Type value for
      the mandatory extension header or the specified protocol.</t>

      <t>The Optional Extension Headers registry allocates values in the range
      256-512. These values are used to identify optional extension headers.
      The registered value corresponds to the 16-bit Type value that would be
      used for an optional extension header with a length (H-LEN) of 1."</t>
    </section>

    <section title="Security Considerations" toc="include">
      <t>This document does not present new security considerations.</t>
    </section>

    <section title="IANA Considerations" toc="include">
      <t>Section 3 specifies updated IANA allocation rules</t>

      <t>Section 4 requests IANA to update the registry information.</t>
    </section>

    <section title="Acknowledgments">
      <t>The author acknowledges feedback from IANA, Alexander Adolf and
      Hans-Peter Lexow on usage of this registry.</t>

      <t><!----></t>
    </section>

    <section title="Revision notes">
      <t>RFC-Editor: Please remove this section prior to publication</t>

      <t>Draft 00</t>

      <t><list style="symbols">
          <t>This contains the first draft for comment.</t>
        </list></t>
    </section>
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- -->

    <references title="Normative References">
      <?rfc sortrefs="yes"?>

      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>

      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4326.xml"?>

      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5163.xml"
?>

      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml"?>

      <reference anchor="GSE">
        <front>
          <title>Digital Video Broadcasting (DVB); Generic Stream
          Encapsulation (GSE) Protocol</title>

          <author fullname="TS 102 606">
            <organization>European Telecommunication Standards, Institute
            (ETSI)</organization>
          </author>

          <date year="2007" />
        </front>
      </reference>
    </references>

    <references title="Informative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4259.xml"?>
    </references>
  </back>
</rfc>