One document matched: draft-boucadair-lisp-type-iana-01.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY % RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<?rfc rfcedstyle="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc toc="yes" ?>
<?rfc tocompact="yes"?>
<rfc category="std" docName="draft-boucadair-lisp-type-iana-01"
     ipr="trust200902">
  <front>
    <title abbrev="LISP Packet Type Allocations">IANA Registry for LISP Packet
    Type Allocations</title>

    <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
      <organization>Orange</organization>

      <address>
        <postal>
          <street></street>

          <city>Rennes</city>

          <code>35000</code>

          <country>France</country>
        </postal>

        <email>mohamed.boucadair@orange.com</email>
      </address>
    </author>

    <author fullname="Christian Jacquenet" initials="C." surname="Jacquenet">
      <organization>Orange</organization>

      <address>
        <postal>
          <street></street>

          <city>Rennes</city>

          <code>35000</code>

          <country>France</country>
        </postal>

        <email>christian.jacquenet@orange.com</email>
      </address>
    </author>

    <date day="" month="" year="" />

    <area>Internet</area>

    <keyword>IPv4 service continuity</keyword>

    <keyword>IPv4 address exhaustion</keyword>

    <keyword>Service Availability</keyword>

    <keyword>Address sharing</keyword>

    <keyword>IPv6</keyword>

    <keyword>Reliability</keyword>

    <keyword>IPv4 over IPv6</keyword>

    <abstract>
      <t>This document defines a registry for LISP Packet Type allocations. It
      also specifies a shared LISP message type for experimentation
      purposes.</t>
    </abstract>

    <note title="Requirements Language">
      <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">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>The Locator/ID Separation Protocol (LISP, <xref
      target="RFC6830"></xref> ) base specification defines a set of
      primitives that are identified with a packet type code. Several
      extensions have been proposed to add more LISP functionalities. For
      example, new message types are proposed in <xref
      target="I-D.ietf-lisp-ddt"></xref>, <xref
      target="I-D.zhao-lisp-mn-extension"></xref>, <xref
      target="I-D.boucadair-lisp-bulk"></xref>, <xref
      target="I-D.boucadair-lisp-subscribe"></xref>, or <xref
      target="I-D.boucadair-lisp-ms-assisted-forwarding"></xref>. It is
      expected that additional LISP extensions will be proposed in the
      future.</t>

      <t>In order to ease the tracking of LISP message types, this document
      proposes to create a "LISP Packet Types" IANA registry (see <xref
      target="iana"></xref>).</t>

      <t>Because of the limited type space <xref target="RFC6830"></xref>,
      this document specifies a shared LISP message type for experimentation
      purposes and proposes a procedure for registering LISP experiment
      identifiers (see <xref target="exp"></xref>) that make use of additional
      LISP capabilities associated with this message type. Concretely, one
      single LISP message type code is dedicated to experiments; experiment
      identifiers are used to uniquely identify a given LISP experimental
      message. These identifiers are selected by the author(s) of the
      corresponding LISP specification that introduces a new experimental
      message type.</t>
    </section>

    <section anchor="exp" title="LISP Message Type for Experimentations">
      <t><xref target="expf"></xref> depicts a common LISP experimental
      message type. The type field MUST be set to 15 (see <xref
      target="iana"></xref>).</t>

      <t><figure anchor="expf" title="Common LISP Experimental Message Type">
          <artwork><![CDATA[        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |Type=15|     Experiment ID     |  experiment-specific          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       //                   experiment-specific                       //
       //                                                             //
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure>The "Experiment ID" field conveys a unique identifier that is
      assigned on a First Come, First Served (FCFS) basis <xref
      target="RFC5226"></xref>. These identifiers are registered with IANA
      (see <xref target="id"></xref>).</t>

      <t>The exact structure of the 'experiment-specific' portion of the
      message is specified in the corresponding specification document.</t>
    </section>

    <section title="Security Considerations">
      <t>This document does not introduce any additional security issues other
      than those discussed in <xref target="RFC6830"></xref>.</t>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <section title="LISP Packet Types">
        <t>IANA is requested to create a new protocol registry for LISP Packet
        Types, numbered 0-15. The registry must be initially populated with
        the following values:</t>

        <t><figure>
            <artwork><![CDATA[Message                           Code Reference
================================= ==== ========
Reserved                           0   [RFC6830]
LISP Map-Request                   1   [RFC6830]
LISP Map-Reply                     2   [RFC6830]
LISP Map-Register                  3   [RFC6830]
LISP Map-Notify                    4   [RFC6830]
LISP Encapsulated Control Message  8   [RFC6830]
LISP Experimental Message         15   [This document]]]></artwork>
          </figure></t>

        <t>The values in the ranges 5-7 and 9-14 can be assigned via Standards
        Action <xref target="RFC5226"></xref>.</t>

        <t>The value 15 is reserved for Experimental Use <xref
        target="RFC5226"></xref>.</t>
      </section>

      <section anchor="id" title="Experiment IDs">
        <t>IANA is requested to create a "LISP Experimental Message Experiment
        Identifiers" registry.</t>

        <t>Entries are assigned on a FCFS basis.</t>

        <t>The registration procedure should provide IANA with the desired
        codepoint and a point of contact. Providing a short description
        (together with an acronym, if relevant) of the foreseen usage of the
        experimental message is also encouraged. </t>
      </section>
    </section>

    <section title="Acknowledgments">
      <t>This work is partly funded by ANR LISP-Lab project
      #ANR-13-INFR-009-X.</t>

      <t>The shared experiment ID is inspired by <xref
      target="RFC6994"></xref>.</t>

      <t>Many thanks to Luigi Iannone for the review.</t>
    </section>
  </middle>

  <back>
    <references title="Normative references">
      <?rfc include='reference.RFC.2119'?>

      <?rfc include='reference.RFC.6830'?>

      <?rfc include='reference.RFC.5226'?>
    </references>

    <references title="Informative References">
      <?rfc include='reference.I-D.boucadair-lisp-bulk'?>

      <?rfc include='reference.I-D.boucadair-lisp-subscribe'?>

      <?rfc include='reference.I-D.ietf-lisp-ddt'?>

      <?rfc include='reference.I-D.boucadair-lisp-ms-assisted-forwarding'?>

      <?rfc include='reference.I-D.zhao-lisp-mn-extension'?>

      <?rfc include='reference.RFC.6994'?>
    </references>
  </back>
</rfc>