rfc9304xml2.original.xml   rfc9304.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc [
<!ENTITY % RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R <!ENTITY nbsp "&#160;">
FC.2119.xml"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]> ]>
<?rfc rfcedstyle="yes" ?>
<?rfc symrefs="yes" ?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-lisp-rfc8113
<?rfc compact="yes" ?> bis-03" number="9304" ipr="trust200902" obsoletes="8113" updates="" submissionTy
<?rfc sortrefs="yes" ?> pe="IETF" category="std" consensus="true" xml:lang="en" symRefs="true" sortRefs=
<?rfc toc="yes" ?> "true" tocInclude="true" version="3">
<?rfc tocompact="yes"?>
<rfc category="std" docName="draft-ietf-lisp-rfc8113bis-03" ipr="trust200902" <!-- xml2rfc v2v3 conversion 3.2.1 -->
obsoletes="8113">
<front> <front>
<title abbrev="LISP Packet Type Allocations">Locator/ID Separation <title abbrev="LISP Packet Type Allocations">Locator/ID Separation
Protocol (LISP): Shared Extension Message &amp; IANA Registry for Packet Protocol (LISP): Shared Extension Message and IANA Registry for Packet
Type Allocations</title> Type Allocations</title>
<seriesInfo name="RFC" value="9304"/>
<author fullname="Mohamed Boucadair" initials="M." surname="Boucadair"> <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Rennes</city> <city>Rennes</city>
<code>35000</code> <code>35000</code>
<country>France</country> <country>France</country>
</postal> </postal>
<email>mohamed.boucadair@orange.com</email> <email>mohamed.boucadair@orange.com</email>
</address> </address>
</author> </author>
<author fullname="Christian Jacquenet" initials="C." surname="Jacquenet"> <author fullname="Christian Jacquenet" initials="C." surname="Jacquenet">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<street></street> <street/>
<city>Rennes</city> <city>Rennes</city>
<code>35000</code> <code>35000</code>
<country>France</country> <country>France</country>
</postal> </postal>
<email>christian.jacquenet@orange.com</email> <email>christian.jacquenet@orange.com</email>
</address> </address>
</author> </author>
<date month="October" year="2022"/>
<date day="25" month="January" year="2019" /> <area>RTG</area>
<area>Internet</area>
<workgroup>LISP</workgroup> <workgroup>LISP</workgroup>
<keyword>Shared Experiment Code</keyword> <keyword>Shared Experiment Code</keyword>
<keyword>LISP codepoints</keyword> <keyword>LISP codepoints</keyword>
<keyword>Experiment Identifier</keyword> <keyword>Experiment Identifier</keyword>
<keyword>Experiment ID</keyword> <keyword>Experiment ID</keyword>
<keyword>LISP Experimental Registry</keyword> <keyword>LISP Experimental Registry</keyword>
<keyword>LISP Extension</keyword> <keyword>LISP Extension</keyword>
<keyword>Extending LISP</keyword> <keyword>Extending LISP</keyword>
<keyword>Exhausted LISP types</keyword>
<keyword>Exhauted LISP types</keyword>
<keyword>LISP IANA</keyword> <keyword>LISP IANA</keyword>
<keyword>IANA</keyword> <keyword>IANA</keyword>
<abstract> <abstract>
<t>This document specifies a Locator/ID Separation Protocol (LISP) <t>This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting shared message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each experiments without consuming a LISP Packet Type codepoint for each
extension.</t> extension.</t>
<t>This document obsoletes RFC 8113.</t> <t>This document obsoletes RFC 8113.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<t>The Locator/ID Separation Protocol (LISP) base specification, <xref <name>Introduction</name>
target="I-D.ietf-lisp-rfc6833bis"></xref>, defines a set of primitives <t>The Locator/ID Separation Protocol (LISP) base specification, <xref tar
get="RFC9301" format="default"/>, defines a set of primitives
that are identified with a packet type code. Several extensions have that are identified with a packet type code. Several extensions have
been proposed to add more LISP functionalities. It is expected that been proposed to add more LISP functionalities. It is expected that
additional LISP extensions will be proposed in the future.</t> additional LISP extensions will be proposed in the future.</t>
<t>The "LISP Packet Types" IANA registry (see <xref target="iana" format="
<t>The "LISP Packet Types" IANA registry (see <xref default"/>) is used to ease the tracking of LISP message
target="iana"></xref>) is used to ease the tracking of LISP message
types.</t> types.</t>
<t>Because of the limited type space <xref target="RFC9301" format="defaul
<t>Because of the limited type space <xref t"/> and the need to conduct
target="I-D.ietf-lisp-rfc6833bis"></xref> and the need to conduct
experiments to assess new LISP extensions, this document specifies a experiments to assess new LISP extensions, this document specifies a
shared LISP extension message type and describes a procedure for shared LISP extension message type and describes a procedure for
registering LISP shared extension sub-types (see <xref registering LISP shared extension sub-types (see <xref target="exp" format
target="exp"></xref>). Concretely, one single LISP message type code is ="default"/>). Concretely, one single LISP message type code is
dedicated to future LISP extensions; sub-types are used to uniquely dedicated to future LISP extensions; sub-types are used to uniquely
identify a given LISP extension making use of the shared LISP extension identify a given LISP extension making use of the shared LISP extension
message type. These identifiers are selected by the author(s) of the message type. These identifiers are selected by the author(s) of the
corresponding LISP specification that introduces a new LISP extension corresponding LISP specification that introduces a new LISP extension
message type.</t> message type.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Requirements Language"> <name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
"OPTIONAL" in this document are to be interpreted as described in BCP 14 "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
<xref target="RFC2119"></xref><xref target="RFC8174"></xref> when, and ",
only when, they appear in all capitals, as shown here.</t> "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be
interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/> <xref
target="RFC8174"/> when, and only when, they appear in all capitals, as
shown here.
</t>
</section> </section>
<section anchor="exp" numbered="true" toc="default">
<section anchor="exp" title="LISP Shared Extension Message Type "> <name>LISP Shared Extension Message Type</name>
<t><xref target="expf"></xref> depicts the common format of the LISP <t><xref target="expf" format="default"/> depicts the common format of the
shared extension message. The type field MUST be set to 15 (see <xref LISP
target="iana"></xref>).</t> shared extension message. The type field <bcp14>MUST</bcp14> be set to 15
(see <xref target="iana" format="default"/>).</t>
<t><figure anchor="expf" title="LISP Shared Extension Message Type"> <figure anchor="expf">
<artwork><![CDATA[ 0 1 2 <name>LISP Shared Extension Message Type</name>
3 <artwork name="" type="" align="center" alt=""><![CDATA[
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 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| Sub-type | extension-specific | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Type=15| Sub-type | extension-specific |
// extension-specific // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // extension-specific //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></art // //
work> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</figure>The "Sub-type" field conveys a unique identifier that MUST be ]]></artwork>
registered with IANA (see <xref target="id"></xref>).</t> </figure>
<t>The 'Sub-type' field conveys a unique identifier that <bcp14>MUST</bcp1
4> be
registered with IANA (see <xref target="id" format="default"/>).</t>
<t>The exact structure of the 'extension-specific' portion of the <t>The exact structure of the 'extension-specific' portion of the
message is specified in the corresponding specification document.</t> message is specified in the corresponding specification document.</t>
</section> </section>
<section numbered="true" toc="default">
<section title="Security Considerations"> <name>Security Considerations</name>
<t>This document does not introduce any additional security issues other <t>This document does not introduce any additional security issues other
than those discussed in <xref than those discussed in <xref target="RFC9301" format="default"/>.</t>
target="I-D.ietf-lisp-rfc6833bis"></xref>.</t>
</section> </section>
<section anchor="iana" numbered="true" toc="default">
<section anchor="iana" title="IANA Considerations"> <name>IANA Considerations</name>
<section anchor="ptype" title="LISP Packet Types"> <section anchor="ptype" numbered="true" toc="default">
<t>IANA has created a protocol registry for LISP Packet Types, <name>LISP Packet Types</name>
<t>IANA has created a registry titled "LISP Packet Types",
numbered 0-15.</t> numbered 0-15.</t>
<t>Values can be assigned via Standards Action <xref target="RFC8126" fo
<t>Values can be assigned via Standards Action <xref rmat="default"/>. Documents that request for a new LISP Packet
target="RFC8126"></xref>. Documents that request for a new LISP packet Type may indicate a preferred value in the corresponding IANA
type may indicate a preferred value in the corresponding IANA
sections.</t> sections.</t>
<t>IANA has replaced the reference to RFC 8113 with the RFC
number of this document.</t>
<t>Also, IANA has updated the table as follows:</t>
<t>OLD:</t>
<table align="left">
<thead>
<tr>
<th>Message</th>
<th>Code</th>
<th>Reference</th>
</tr>
</thead>
<tbody>
<tr>
<t>IANA is requested to replace the reference to RFC8113 with the RFC <td>LISP Shared Extension Message</td>
number to be assigned to this document.</t> <td>15</td>
<td>[RFC8113]</td>
<t>Also, IANA is requested to update the table as follows:</t> </tr>
</tbody>
</table>
<t><figure> <t>NEW:</t>
<artwork><![CDATA[OLD: <table align="left">
<thead>
<tr>
<th>Message</th>
<th>Code</th>
<th>Reference</th>
</tr>
</thead>
<tbody>
<tr>
<td>LISP Shared Extension Message</td>
<td>15</td>
<td>RFC 9304</td>
</tr>
</tbody>
Message Code Reference </table>
================================= ==== ===============
LISP Shared Extension Message 15 [RFC8113]
NEW: </section>
Message Code Reference
================================= ==== ===============
LISP Shared Extension Message 15 [ThisDocument]]]></artwork>
</figure></t>
</section>
<section anchor="id" title="Sub-Types"> <section anchor="id" numbered="true" toc="default">
<name>Sub-Types</name>
<t>IANA has created the "LISP Shared Extension Message Type Sub-types" <t>IANA has created the "LISP Shared Extension Message Type Sub-types"
registry. IANA is requested to update that registry by replacing the registry. IANA has updated that registry by replacing the
reference to RFC8113 with the RFC number to be assigned to this reference to RFC 8113 with the RFC number of this
document.</t> document.</t>
<t>The values in the range 0-1023 are assigned via Standards Action. <t>The values in the range 0-1023 are assigned via Standards Action.
This range is provisioned to anticipate, in particular, the exhaustion This range is provisioned to anticipate, in particular, the exhaustion
of the LISP Packet types.</t> of the LISP Packet Types.</t>
<t>The values in the range 1024-4095 are assigned on a First Come, <t>The values in the range 1024-4095 are assigned on a First Come,
First Served (FCFS) basis. The registration procedure should provide First Served (FCFS) basis. The registration procedure is to provide
IANA with the desired codepoint and a point of contact; providing a IANA with the desired codepoint and a point of contact; providing a
short description (together with an acronym, if relevant) of the short description (together with an acronym, if relevant) of the
foreseen usage of the extension message is also encouraged.</t> foreseen usage of the extension message is also encouraged.</t>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="Changes from RFC 8113"> <name>Changes from RFC 8113</name>
<t>The following changes were made from RFC 8113:<list style="symbols"> <t>The following changes were made from RFC 8113:</t>
<t>Change the status from Experimental to Standard track.</t> <ul spacing="normal">
<li>Changed the status from Experimental to Standards Track.</li>
<t>Indicate explicitly that the shared extension is used for two <li>Indicated explicitly that the shared extension is used for two
purposes: extend the type space and conduct experiments to assess purposes: extend the type space and conduct experiments to assess
new LISP extensions.</t> new LISP extensions.</li>
<li>Deleted pointers to some examples illustrating how the shared
<t>Delete pointers to some examples illustrating how the shared extension message is used to extend the LISP protocol.</li>
extension message is used to extend the LISP protocol.</t> <li>IANA has updated the "IANA LISP Packet Types" and "LISP
<t>Request IANA to update the "IANA LISP Packet Types" and "LISP
Shared Extension Message Type Sub-types" registries to point to this Shared Extension Message Type Sub-types" registries to point to this
document instead of RFC8113.</t> document instead of RFC 8113.</li>
</list></t> </ul>
</section>
<section title="Acknowledgments">
<t>This work is partly funded by ANR LISP-Lab project
#ANR-13-INFR-009-X.</t>
<t>Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for
the review.</t>
<t>Thanks to Geoff Huston, Brian Carpenter, Barry Leiba, and Suresh
Krishnan for the review.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<?rfc include='reference.RFC.2119'?>
<?rfc include='reference.RFC.8174'?> <name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.211
9.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817
4.xml"/>
<?rfc include='reference.I-D.ietf-lisp-rfc6833bis'?> <reference anchor='RFC9301' target="https://www.rfc-editor.org/info/rfc9301">
<front>
<title>Locator/ID Separation Protocol (LISP) Control Plane</title>
<author initials='D' surname='Farinacci' fullname='Dino Farinacci'>
<organization />
</author>
<author initials='F' surname='Maino' fullname='Fabio Maino'>
<organization />
</author>
<author initials='V' surname='Fuller' fullname='Vince Fuller'>
<organization />
</author>
<author initials='A' surname='Cabellos' fullname='Albert Cabellos' role='editor'
>
<organization />
</author>
<date month='October' year='2022' />
</front>
<seriesInfo name="RFC" value="9301"/>
<seriesInfo name="DOI" value="10.17487/RFC9301"/>
</reference>
<?rfc include='reference.RFC.8126'?> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.812 6.xml"/>
</references> </references>
<section numbered="false" toc="default">
<name>Acknowledgments</name>
<t>This work is partly funded by ANR LISP-Lab project
#ANR-13-INFR-009-X.</t>
<t>Many thanks to <contact fullname="Luigi Iannone"/>, <contact fullname="
Dino Farinacci"/>, and <contact fullname="Alvaro Retana"/> for
the review.</t>
<t>Thanks to <contact fullname="Geoff Huston"/>, <contact fullname="Brian
Carpenter"/>, <contact fullname="Barry Leiba"/>, and <contact fullname="Suresh
Krishnan"/> for the review.</t>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 58 change blocks. 
150 lines changed or deleted 174 lines changed or added

This html diff was produced by rfcdiff 1.48.