<?xml version="1.0"encoding="US-ASCII"?>encoding="UTF-8"?> <!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"?>"rfc2629-xhtml.ent"> <rfccategory="std"xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-mpls-lsp-ping-registries-update-11" number="9041" ipr="trust200902" updates="8029,8611">8611" obsoletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" version="3"> <front> <title abbrev="LSP Ping Registries">Updating theIANAMPLSLSPLabel Switched Paths (LSPs) PingParameters</title>Parameters IANA Registry</title> <seriesInfo name="RFC" value="9041"/> <author fullname="Loa Andersson" initials="L." surname="Andersson"> <organization>Bronze Dragon Consulting</organization> <address> <postal> <street/> <city/> <region/> <code/> <country/> </postal> <email>loa@pi.nu</email> </address> </author> <authorfullname="Machfullname="Mach(Guoyi) Chen" initials="M." surname="Chen"> <organization>Huawei Technologies</organization> <address> <postal> <street/> <city/> <region/> <code/> <country/> </postal> <email>mach.chen@huawei.com</email> </address> </author> <author fullname="Carlos Pignataro" initials="C." surname="Pignataro"> <organization>Cisco Systems</organization> <address> <postal> <street/> <city/> <region/> <code/> <country/> </postal> <email>cpignata@cisco.com</email> </address> </author> <author fullname="Tarek Saad" initials="T." surname="Saad"> <organization>Juniper Networks</organization> <address> <postal> <street/> <city/> <region/> <code/> <country/> </postal> <email>tsaad@juniper.net</email> </address> </author> <date year="2021" month="July" /> <workgroup>MPLS Working Group</workgroup> <abstract> <t> This document updatesRFCRFCs 8029 andRFC 8611 which8611, both of which define IANA registries for MPLS Label Switched Path (LSP)Ping, in particularPing. In particular, the registration procedure "Private Use"(esarlier know(previously known as "Vendor Private Use")ishas been changed to "FirstCome,Come First Served" for the TLV andSub-TLV Registries.sub-TLV registries. </t> <t> It also updates the description of the procedures for the responses sent when an unknown or erroneous code point is found. The updates are to clarify and align this namespace with recent developments,e.g.e.g., aligning terminology with RFC 8126 instead of theupdates to " Guidelinesnow obsoleted RFC 5226 (both titled "Guidelines for Writing an IANA Considerations Section inRFCs" (e.g. RFC 8126), instead of the terminology from the obsoleted RFC 5226.RFCs"). </t> </abstract> </front> <middle><!-- section 1 --><section anchor="intro"title="Introduction">numbered="true" toc="default"> <name>Introduction</name> <t> There were a number of reasons to start the work that has led to this document,e.g.: <list style="symbols"> <t>e.g., </t> <ul spacing="normal"> <li> When the LSP Ping registry wascreatedcreated, it was incorrectly assumed that code points allocated by Experimental RFCs would be'experimental'"experimental" code points; a code point made available in a public IANA registry is not limited by the type of RFC that made theallocation butallocation: it is available for use in any type of document.</t> <t></li> <li> The number of'experimental'"experimental" code points was also toolarge,large as compared to what is normally allocated for "Experimental Use".</t> <t> RFC 8029 uses the</li> <li> The words "mandatory" and "optional" are used differentlyto howin <xref target="RFC8029"/> than in otherRFC do. RFC 8029 for exampleRFCs. For example, <xref target="RFC8029"/> talks about mandatory TLVs to indicate that it is mandatory to take a certain action if the TLV is found in a message but is notrecognized, otherrecognized. Other RFCsusesuse "mandatory TLV" to indicate a TLV that must be present in a message.</t> </list></li> </ul> <t> Overtimetime, there have been attempts to administratively update some of the registries, but it was soon decided that an RFC was needed. Other, often minor, potential updates were found,e.g.e.g., reserving the value 0 (zero) in registries where that is possible. </t> <t>When RFC 8029<xreftarget="RFC8029"/> was published it containedtarget="RFC8029" format="default"/> contains updates to the"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters""<xref target="IANA-LSP-PING" format="title"/>" IANA namespace <xreftarget="IANA-LSP-PING"/>.target="IANA-LSP-PING" format="default"/>. </t> <t>RFC 8611<xreftarget="RFC8611"/>target="RFC8611" format="default"/> created LSP Ping IANA registries that matchRFC 8126.<xref target="RFC8126"/>. This document further clarifies the entries in those registries and makes the definitions more precise. </t> <t> This document updatesRFC 8029<xreftarget="RFC8029"/>target="RFC8029" format="default"/> andRFC 8611<xreftarget="RFC8611"/>target="RFC8611" format="default"/> by updating two groups of registries as follows: </t> <t>FirstFirst, theregistries for Message Types"Message Types" <xreftarget="IANA-MT"/>, Reply Modestarget="IANA-MT" format="default"/>, "Reply Modes" <xreftarget="IANA-RM"/>target="IANA-RM" format="default"/>, andReturn Codes"Return Codes" <xreftarget="IANA-RC"/>target="IANA-RC" format="default"/> registries are updated. The changes to these registries are minor. </t> <t> Second, this document updates the TLV and sub-TLVregistries. <list style="symbols"> <t> <xref target="IANA-TLV-reg" format="title"/> <xref target="IANA-TLV-reg"/>.registries listed below: </t><t> Sub-TLVs for TLVs 1, 16 and 21<ul spacing="normal"> <li> "<xref target="IANA-TLV-reg" format="title"/>", <xreftarget="IANA-Sub-1-16-21"/>. </t> <t>target="IANA-TLV-reg" format="default"/> </li> <li> "<xref target="IANA-Sub-1-16-21" format="title"/>", <xref target="IANA-Sub-1-16-21" format="default"/> </li> <li> "<xref target="IANA-Sub-6"format="title" />format="title"/>", <xreftarget="IANA-Sub-6"/>. </t> <t> Sub-TLVs for TLV 11target="IANA-Sub-6" format="default"/> </li> <li> "<xref target="IANA-Sub-11" format="title"/>", <xreftarget="IANA-Sub-11"/>. </t> <t> Sub-TLVs for TLV 20target="IANA-Sub-11" format="default"/> </li> <li> "<xref target="IANA-Sub-20" format="title"/>", <xreftarget="IANA-Sub-20"/>. </t> <t> Sub-TLVs for TLV 23target="IANA-Sub-20" format="default"/> </li> <li> "<xref target="IANA-Sub-23" format="title"/>", <xreftarget="IANA-Sub-23"/>. </t> <t> Sub-TLVs for TLV 27target="IANA-Sub-23" format="default"/> </li> <li> "<xref target="IANA-Sub-27" format="title"/>", <xreftarget="IANA-Sub-27"/>. </t> </list> </t>target="IANA-Sub-27" format="default"/> </li> </ul> <t> It should be noted thatRFC 8029<xref target="RFC8029"/> was published beforeRFC 8126<xref target="RFC8126"/> and usesoldoutdated terminology for some registration procedures, e.g., "Vendor Private Use".RFC 8611<xref target="RFC8611"/> was published afterRFC 8126<xref target="RFC8126"/> and usesnewerits recommended terminology, e.g., "Private Use".BothHowever, now both "Vendor Private Use" and "Private Use"hashave been removed and replaced with "Firstcome, first servedCome First Served" (FCFS) code points. </t> <t> One reason to change from codepointpoints allocated by Vendor Private Use or Private Use is that such code points are allowed in production networks. Theoretically, it is possible that two vendors might use the same code point value with different meanings. If such a code is ever deployed in the samenetworknetwork, this could cause protocol issues that would be hard to debug. </t> <t> With FCFS codepointspoints, this will not happen. Vendors that have existing code using Vendor Private Use or Private Use code points should register those code points asFSFCFCFS code points as soon as this document is published as an RFC. </t> <t> Theregistry for sub-TLVs for TLV 9 <xref target="IANA-Sub-9"/>"<xref target="IANA-Sub-9" format="title"/>" subregistry is not updated. </t> <t> Third, according toRFC 8029<xref target="RFC8029"/>, some code points (TLVs and sub-TLVs) are called "mandatory" or "optional". Contrary to how other RFCs use these words, indicating that it is mandatory or optional to include the code points in a message,RFC 8029<xref target="RFC8029"/> uses these words to indicate that an action might or might not be mandatory. This document updatesRFC 8029<xref target="RFC8029"/> to drop the words "mandatory" and "optional", and the text is changed to focus on what should be done. </t> <section anchor="lang"title="Requirement Language">numbered="true" toc="default"> <name>Requirements Language</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t> </section> <section anchor="terms"title="Terminology">numbered="true" toc="default"> <name>Terminology</name> <t> This sectionlistlists terms that are used when discussing the hierarchy of IANAregistersregistries (<xreftarget="local-terms"/>)target="local-terms" format="default"/>), and abbreviations used in IANA registriesupdateare updated in this document (<xreftarget="abbr"/>).target="abbr" format="default"/>). </t> <section anchor="local-terms"title="Terminologynumbered="true" toc="default"> <name>Terminology Used inthis Document"> <t>Thisdocument uses some terms that relatesDocument</name> <t> Terms related to IANA registries are used as follows in thisway: <list style="symbol"> <t> IANA Name Space, <vspace blankLines="0"/> adocument: </t> <dl newline="true"> <dt> Namespace</dt> <dd> A namespace is atop leveltop-level registry. An example could be "<xref target="lsp-ping-Namespace" format="title"/>" <xreftarget="IANA-LSP-PING"/>.target="IANA-LSP-PING" format="default"/>. A namespace is most often a container for registries that hold code points that share some affinity.</t> <t> IANA Registry, <vspace blankLines="0"/> an</dd> <dt> Registry</dt> <dd>An IANA registry holds codepoints,points and lists the registration procedures and allocation for these code points. One example would be the "<xref target="IANA-TLV-reg" format="title"/>" registry <xreftarget="IANA-TLV-reg"/>. </t> <t> IANA Sub-registry, <vspace blankLines="0"/> a sub-registrytarget="IANA-TLV-reg" format="default"/>. </dd> <dt> Subregistry</dt> <dd>A subregistry is used when a code point, or a set of code points allocated in a single registry, needs"sub-code points""sub-code-points" scoped by the code point or the set of code points. An example of asub-registrysubregistry that holds code points for more than one TLV is "<xref target="IANA-Sub-1-16-21" format="title"/>" <xreftarget="IANA-Sub-1-16-21"/> </t> </list> </t>target="IANA-Sub-1-16-21" format="default"/>. </dd> </dl> </section> <sectiontitle="Abbreviations" anchor="abbr">anchor="abbr" numbered="true" toc="default"> <name>Abbreviations</name> <t> This sectionlistlists abbreviations used in the unchanged part of the registries updated by this document. These abbreviations were originally expanded in the document defining the registries. They are listed here following the requirement to expand any abbreviation that is notwell-known.well known. All these abbreviations are from the<xref"<xref target="IANA-RC"format="title"/>format="title"/>" registry <xreftarget="IANA-RC"/>.target="IANA-RC" format="default"/>. </t><t> <list style="symbol"> <t> BFD - Bidirectional<dl indent="10"> <dt>BFD:</dt><dd>Bidirectional Forwarding Detection</t> <t> DDMAP - Downstream</dd> <dt> DDMAP:</dt><dd>Downstream Detailed Mapping</t> <t> FEC - Forwarding</dd> <dt> FEC:</dt><dd>Forwarding Equivalence Class</t> <t> OAM - Operation, Administration</dd> <dt> OAM:</dt><dd>Operation, Administration, and Maintenance</t> <t> PM - Performance</dd> <dt> PM:</dt><dd>Performance Monitoring</t> <t> RSC - Return</dd> <dt> RSC:</dt><dd>Return Subcode</t> </list> </t></dd> </dl> </section> </section> </section> <section anchor="codes"title="Updatingnumbered="true" toc="default"> <name>Updating the Message Types, ReplyModeModes, and Return CodesRegistries">Registries</name> <t> The following changesarehave been made to theMessage Types"<xref target="IANA-MT" format="title"/>" <xreftarget="IANA-MT"/>, Reply Modestarget="IANA-MT" format="default"/>, "<xref target="IANA-RM" format="title"/>" <xreftarget="IANA-RM"/>target="IANA-RM" format="default"/>, andReturn Codes"<xref target="IANA-RC" format="title"/>" <xreftarget="IANA-RC"/>target="IANA-RC" format="default"/> registries.<list style="symbols"> <t></t> <ul spacing="normal"> <li> In the listing of assigned codepointspoints, the term "Vendor Private Use" is changed to "PrivateUse". </t> <t>Use" for the 252-255 range. The registration procedures have been updated to reflect this. </li> <li> The registration procedure "Specification Required" is changed to "RFC Required" and the note "Experimental RFC needed" isremoved. </t> <t>removed for the 192-247 range. </li> <li> A small set of four code points(4 code points)(248-251) for Experimental Use is added by reducing the "RFC Required" range.</t> <t>The registration procedures"Private Use" and "Experimental Use" are addedhave been updated tothe table of registration procedures. </t> <t>reflect this. </li> <li> A note"Not"Reserved, not to be assigned"ishas been added for the registration procedures of the "Private Use" and "ExperimentalUse". </t>Use" ranges. </li> <li> <t> In the lists that capture the assignment status, the fields that are reserved, i.e., 0 (zero), PrivateUseUse, and ExperimentalUseUse, are clearly marked as such.<list style="symbols"> <t></t> <ul spacing="normal"> <li> Note that in theReturn Codes"<xref target="IANA-RC" format="title"/>" registry <xreftarget="IANA-RC"/>target="IANA-RC" format="default"/>, the code point "0" has already been assigned. This assignment is notchangedchanged, and in thisregistryregistry, the code point "0" continues to be assigned as "No Return Code".</t> </list> </t> <!-- Amandas comment left in for easy changeability <t> At the top of each registry listed in this section a reference to this document should be added making the header of the register look like this: <list style="empty"> <t> [Registry Name] <vspace blankLines="0"/> Expert(s) <vspace blankLines="0"/> Mach Chen and Carlos Pignataro <vspace blankLines="0"/> Reference <vspace blankLines="0"/> [RFC8029] [This document] <vspace blankLines="0"/> Available Formats <vspace blankLines="0"/> CSV </t> </list> </t> --> </list> </t></li> </ul> </li> </ul> <t> The newRegistration Procedures,registration procedures, the registrylayoutslayouts, and the new assignments for these registries are found in <xreftarget="app-messages"/>.target="app-messages" format="default"/>. </t> </section> <section anchor="upd-tlv"title="Updatingnumbered="true" toc="default"> <name>Updating the TLV and Sub-TLVRegistries">Registries</name> <section anchor="principles"title="Generalnumbered="true" toc="default"> <name>General Principles for the LSP Ping TLV and Sub-TLVregistries">Registries</name> <t> The following principles apply to the processing of any TLV from any of the LSP PingTLVsTLV andsub-TLVssub-TLV IANA registries.<list style="symbols"> <t></t> <ul spacing="normal"> <li> All TLVs and sub-TLVs with a type in the range 0-32767 require a response if they are not recognized.</t> <t></li> <li> All TLVs and sub-TLVs in the range 32768-65535maycan be silentlydropped, stepped over or an error message sentdropped if they are not recognized.</t> <!-- Amandas comment left in becasue easy changeability <t> AtAlternatively, thetop of each registry listed in this section a reference to this document should be added making the header ofreceiver may step over theregister look like this: <list style="empty"> <t> [Registry Name] <vspace blankLines="0"/> Expert(s) <vspace blankLines="0"/> Mach Chen and Carlos Pignataro <vspace blankLines="0"/> Reference <vspace blankLines="0"/> [Current Reference(s)] [This document] <vspace blankLines="0"/> Available Formats <vspace blankLines="0"/> CSV </t> </list> </t> --> </list> </t>unrecognized TLV or send an error message. </li> </ul> <t> Each of the blocks has code point spaces with the following registration procedures:<list style="symbols"> <t> Standards Action.</t><t> RFC Required. </t> <t><ul spacing="normal"> <li> Standards Action </li> <li> RFC Required </li> <li> ExperimentalUse. </t> <t>Use </li> <li> First Come First Served(FCFS). </t> </list> </t>(FCFS) </li> </ul> <t> The exact definitions of these procedures are found in <xreftarget="RFC8126"/>.target="RFC8126" format="default"/>. </t> <section anchor="unrecog"title="Unrecognizednumbered="true" toc="default"> <name>Unrecognized Experimental Use TLVs andSub-TLVs">Sub-TLVs</name> <t> Unrecognized TLVs and sub-TLVs in the ExperimentalUse,Use and FCFS ranges are handled as any other unrecognized TLV or sub-TLV.<list style="symbols"> <t></t> <ul spacing="normal"> <li> If the unrecognized TLV or sub-TLV is from the Experimental Use range (31740-31743) or from the FCFS range(31744-32767)(31744-32767), a Return Code of 2 ("One or more of the TLVs was not understood") must be sent in the echo response.</t> <t></li> <li> Ifthe unrecognizeda TLV or sub-TLVisfrom the Experimental Use range (64508-64511) or from the FCFS range (64512-65535) is unrecognized, then theTLVs may bereceiver can silentlyignored, steppeddrop the TLV. Alternatively, the receiver may step over the unrecognized TLV or send an errormessage sent. </t> </list> </t>message. </li> </ul> <t> The IETF does not prescribe how recognized or unrecognized Experimental Use and Private Use TLVs and sub-TLVs are handled in experimental or private networks; that is up to the agency running the experimental or the private network. The statement above describes howstandards compliantstandards-compliant implementations must treat the unrecognized TLVs and sub-TLVs from these ranges. </t> </section> </section> <section anchor="shared"title="Commonnumbered="true" toc="default"> <name>Common Registration Procedures for TLVs andsub-TLVs">Sub-TLVs</name> <t> This section describes the new registration procedures for the TLV and sub-TLV registries. </t><texttable title="TLV<table anchor="tlv-sub-tlv" align="center"> <name>TLV andsub-TLVSub-TLV RegistrationProcedures" anchor="tlv-sub-tlv"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisProcedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for TLVs and sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for TLVs and sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for TLVs and sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for TLVs and sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for TLVs and sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for TLVs and sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for TLVs and sub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for TLVs and sub-TLVs that can be silently dropped if notrecognized.</c> </texttable>recognized.</td> </tr> </tbody> </table> </section> <section anchor="general"title="Changesnumbered="true" toc="default"> <name>Changes to the LSP PingRegistries">Registries</name> <t> This section lists the changes to each MPLS LSP Ping TLV and sub-TLVRegistry. Sectionregistry. Sections <xref target="upds-tlv" format="counter"/> to <xref target="upds-sub-tlv-27" format="counter"/> describe how the new versions of the IANA registries should look, together with the registration procedures for each registry. </t> <t> The newRegistration Procedures descriptionregistration procedure descriptions and the new assignments for these registries are used to model the changed MPLS LSP Pingregistries,registries; see <xreftarget="IANA"/>.target="IANA" format="default"/>. </t> <section anchor="common-tlv"title="Common Changesnumbered="true" toc="default"> <name>Changes Common to the TLV and Sub-TLVRegistries">Registries</name> <t> The following changes are made to the TLV and sub-TLV registries.<list style="symbols"> <t></t> <ul spacing="normal"> <li> The registration procedures "First Come FirstServed (FCFS)"Served" (FCFS) and "Experimental Use"arehave been added to the table of registration procedures.</t> <t></li> <li> Two small sets of code points(4(four code points each) for ExperimentalUse, areUse have been created. The first set is for the range that requires a response if the TLV or sub-TLV is not recognized; the second set is for the range where the TLV or sub-TLVthatmay be silently dropped if not recognized. The code points forexperimental use areExperimental Use have been taken from the ranges previously(RFC 8029)called'Specification Required'"Specification Required" and(RFC 8611)"RFCRequired". </t> <t>Required" <xref target="RFC8029"/>. </li> <li> The registration procedure "Specification Required"ishas been changed to "RFCRequired"Required", and the note "Experimental RFC needed"ishas been removed.</t> <t></li> <li> In the listing ofassignmentsassignments, the term "Vendor Private Use"ishas been changed to "First Come FirstServed (FCFS)". </t> <t>Served" (FCFS). </li> <li> In the listing ofassignmentsassignments, the range for "Experimental Use"ishas been added.</t> <t></li> <li> A note saying "Not to be assigned"ishas been added for the registrationproceduresprocedure "Experimental Use".</t> <t></li> <li> In the list that captures assignment status, the fields that are reserved, i.e., 0 (zero) and ExperimentalUse areUse, have been clearly marked.</t> </list> </t></li> </ul> </section> </section> </section> <section anchor="text-updates"title="Updatesnumbered="true" toc="default"> <name>Updates to RelatedRFCs">RFCs</name> <t> Some referenced RFCs use the concept "mandatory TLVs" and "mandatory sub-TLVs" to indicate that, if a TLV or sub-TLV of the range 0-32767 in a message is not understood, an error message needs to be sent in response. </t> <t> The same RFCs use "optional TLVs" and "optional sub-TLVs" to mean TLVs or sub-TLVs that can be silently ignored if not recognized. </t> <t> Since other RFCs use "mandatory TLVs" and "mandatory sub-TLVs" to indicate TLVs and sub-TLVs that must be present in a message, we want to discontinue the use of "mandatory" to indicate TLVs and sub-TLVs that require an error message in response if not understood. The changes to the RFCs below align with this practice. </t> <section anchor="rfc8029"title="Updatesnumbered="true" toc="default"> <name>Updates to RFC8029">8029</name> <t>Mandatory"Mandatory" andoptional"optional" are used to indicate whether a response is needed if a TLV or sub-TLV is not understoodon pages 15 and 16in Section3<xref target="RFC8029" sectionFormat="bare" section="3"/> ofRFC 8029."<xref target="RFC8029" format="title"/>" <xref target="RFC8611" format="default"/>. </t> <t> The text in those two paragraphs is now updated to the following: </t><t> <list style="empty"> <t><blockquote><t> TLV and sub-TLVTypestypes less than 32768 (i.e., with the high-order bit equal to 0) are TLVs and sub-TLVs thatMUST<bcp14>MUST</bcp14> either be supported by an implementation or result inthea Return Code of 2 ("One or more of the TLVs was not understood") being sent in the echo response. </t> <t> An implementation that does not understand or support a received TLV or sub-TLV withTypea type greater than or equal to 32768 (i.e., with the high-order bit equal to 1)SHOULD<bcp14>SHOULD</bcp14> ignore and step over the TLV orsub-TLV, howeversub-TLV; however, an implementationMAY<bcp14>MAY</bcp14> send an echo response with a Return Code of 2 ("One or more of the TLVs was not understood") as it would have done if thehigh orderhigh-order bit had beenclear. </t> </list> </t>clear.</t> </blockquote> <t> InSection 3.8 of RFC 8029<xref target="RFC8029" section="3.8"/>, "mandatory" is used in the same way. The<!-- here -->first two paragraphs of this section are now updated to read as follows:<list style="empty"> <t></t> <blockquote><t> The following TLV is a TLV thatMAY<bcp14>MAY</bcp14> be included in an echo reply to inform the sender of an echo request that includesTLVsTLV orsub- TLVssub-TLV Types less than 32768 (i.e., with the high-order bit equal to 0) that are either not supported by the implementation or parsed and found to be inerror. </t>error.</t> <t> The Value fieldcontainsuses sub-TLVs to encode theTLVs, including sub-TLVs,received TLVs and sub-TLVs that were notunderstood, encoded as sub-TLVs. </t> </list>understood. </t> </blockquote> </section> <section anchor="rfc8611"title="Updatesnumbered="true" toc="default"> <name>Updates to RFC8611">8611</name> <t> Section13.4.1<xref target="RFC8611" sectionFormat="bare" section="13.4.1"/> of "<xref target="RFC8611"format="title"/>format="title"/>" <xreftarget="RFC8611"/>"target="RFC8611" format="default"/> defines "<xref target="IANA-Sub-6"format="title" />"format="title"/>" <xreftarget="IANA-Sub-6"/>.target="IANA-Sub-6" format="default"/>. </t> <t> The"Sub-TLVs for TLV Type 6""<xref target="IANA-Sub-6" format="title"/>" registryis nowhas been updated to align with changes defined in this document. </t> <t>Section 13.4.1 of RFC 8611<xref target="RFC8611" section="13.4.1"/> is now updated as follows: </t><t> Section<blockquote><t>Section 13.4.1 Sub-TLVs for TLV Type6 </t>6</t></blockquote> <t> IANA has created a newsub-registrysubregistry, "<xref target="IANA-Sub-6"format="title"/>"format="title"/>", <xreftarget="IANA-Sub-6"/>target="IANA-Sub-6" format="default"/> under the "<xref target="IANA-TLV-reg" format="title"/>" registry <xreftarget="IANA-TLV-reg"/>target="IANA-TLV-reg" format="default"/> of the "<xref target="lsp-ping-Namespace" format="title"/>" namespace <xreftarget="lsp-ping-Namespace"/>.target="lsp-ping-Namespace" format="default"/>. </t> <t> The "<xref target="IANA-Sub-6" format="title"/>"sub-registrysubregistry is now updated to align with changes defined in this document. </t><texttable title="Sub-TLVs<table anchor="sub-six-texttab" align="center"> <name>Sub-TLVs for TLV Type 6 RegistrationProcedures" anchor="sub-six-texttab"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisProcedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable>recognized.</td> </tr> </tbody> </table> </section> </section> <section anchor="security"title="Security Considerations">numbered="true" toc="default"> <name>Security Considerations</name> <t> This document updates IANA registries. It also updates terminology used to define, and clarifies the terminology related to, the code points in the registries. The document does not change how thecode-pointscode points in the registries are used. This should not create any new threats. </t> <t> However, the updated terminology and the clarifications improve security because it makes it more likely that implementations will be consistent and harder to attack. </t> </section> <section anchor="IANA"title="IANA Considerations">numbered="true" toc="default"> <name>IANA Considerations</name> <t> IANAis requested to updatehas updated the "<xref target="lsp-ping-Namespace" format="title"/>" namespace <xreftarget="IANA-LSP-PING"/>target="IANA-LSP-PING" format="default"/> as described in this document. </t> <t> See <xref target="local-terms"/>format="default"/> of "<xref target="local-terms" format="title"/>" to see how "namespace","registry""registry", and"sub-registry""subregistry" are used in this document. </t> <t> In other parts of thisdocumentdocument, thecommunalitycommonality of the changes to the LSP Ping registries has been the focus. For the IANAconsiderationsConsiderations, each changed registry has been described in its own right. </t> <t> The following registries andsub-registries are changed: <vspace blankLines="1"/> "<xrefsubregistries have been changed:</t> <ul empty="false"> <li>"<xref target="IANA-MT" format="title"/>", <xreftarget="IANA-MT"/>, <vspace blankLines="0"/> "<xreftarget="IANA-MT" format="default"/></li> <li>"<xref target="IANA-RM" format="title"/>", <xreftarget="IANA-RM"/> <vspace blankLines="0"/> "<xreftarget="IANA-RM" format="default"/></li> <li>"<xref target="IANA-RC"format="title"/>"format="title"/>", <xreftarget="IANA-RC"/> <vspace blankLines="0"/> "<xreftarget="IANA-RC" format="default"/></li> <li>"<xref target="IANA-TLV-reg"format="title"/>"format="title"/>", <xreftarget="IANA-TLV-reg"/> <vspace blankLines="0"/> "<xreftarget="IANA-TLV-reg" format="default"/></li> <li>"<xref target="IANA-Sub-1-16-21"format="title" />"format="title"/>", <xreftarget="IANA-Sub-1-16-21"/> <vspace blankLines="0"/> "<xreftarget="IANA-Sub-1-16-21" format="default"/></li> <li>"<xref target="IANA-Sub-6"format="title" />"format="title"/>", <xreftarget="IANA-Sub-6"/> <vspace blankLines="0"/> "<xreftarget="IANA-Sub-6" format="default"/></li> <li>"<xref target="IANA-Sub-11"format="title"/>"format="title"/>", <xreftarget="IANA-Sub-11"/> <vspace blankLines="0"/> "<xreftarget="IANA-Sub-11" format="default"/></li> <li>"<xref target="IANA-Sub-20"format="title" />"format="title"/>", <xreftarget="IANA-Sub-20"/> <vspace blankLines="0"/> "<xreftarget="IANA-Sub-20" format="default"/></li> <li>"<xref target="IANA-Sub-23"format="title"/>"format="title"/>", <xreftarget="IANA-Sub-23"/> <vspace blankLines="0"/> "<xreftarget="IANA-Sub-23" format="default"/></li> <li>"<xref target="IANA-Sub-27"format="title"/>"format="title"/>", <xreftarget="IANA-Sub-27"/> </t>target="IANA-Sub-27" format="default"/></li> </ul> <t> This documentwill behas been listed as an additional reference for each of the registries described in Sections6.1<xref target="app-messages" format="counter"/> and6.2.<xref target="upd-tls-sub-tlv" format="counter"/>. </t> <section anchor="app-messages"title="Updatesnumbered="true" toc="default"> <name>Updates by IANA to the MessageType,Types, ReplyModeModes, and Return CodesRegistries">Registries</name> <t> This section details the updated registration procedures and allocations for"Message Type", "Reply Mode"the "<xref target="IANA-MT" format="title"/>", "<xref target="IANA-RM" format="title"/>", and"Return Codes""<xref target="IANA-RC" format="title"/>" registries. </t> <section anchor="mt-upd"title="Updatesnumbered="true" toc="default"> <name>Updates to the MessageType registry">Types Registry</name> <t>This isThese are the changes to the"Message Type""<xref target="IANA-MT" format="title"/>" registry specified in this document:<list style="symbols"> <t></t> <ul spacing="normal"> <li> Code Point 0 (zero)ishas been marked Reserved.</t> <t></li> <li> The registration procedure "Specification Required"ishas been changed to "RFCRequired"Required", and the comment "Experimental RFC needed"ishas been removed.</t> <t></li> <li> Four codepointpoints have been taken from what wasearlierpreviously "Specification Required" to form a set of code points for "ExperimentalUse." </t> </list> </t>Use". </li> </ul> <t> The registration procedures after the changes listed above for the"Message Type""<xref target="IANA-MT" format="title"/>" registry are shown in the table below: </t><texttable title="Message Type registration procedures" anchor="mt-reg-proc-texttab"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-191</c> <c>Standards Action</c> <c></c> <c>192-247</c> <c>RFC Required</c> <c></c> <c>248-251</c> <c>Experimental Use</c> <c>Reserved,<table anchor="mt-reg-proc-texttab" align="center"> <name>Message Types Registration Procedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-191</td> <td align="left">Standards Action</td> <td align="left"/> </tr> <tr> <td align="left">192-247</td> <td align="left">RFC Required</td> <td align="left"/> </tr> <tr> <td align="left">248-251</td> <td align="left">Experimental Use</td> <td align="left">Reserved, not to beassigned</c> <c>252-255</c> <c>Private Use</c> <c>Reserved,assigned</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Private Use</td> <td align="left">Reserved, not to beassigned</c> </texttable>assigned</td> </tr> </tbody> </table> <t> The updated assignments for the"Message Types""<xref target="IANA-MT" format="title"/>" registrywill look like this:appear as follows: </t><texttable title="Assignments<table anchor="mt-texttab" align="center"> <name>Assignments for the Message Typesregistry" anchor="mt-texttab"> <ttcol align='left' width="8%">Value</ttcol> <ttcol align='left' width="62%">Meaning</ttcol> <ttcol align='left' width="40%">Reference</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c>1</c> <c>MPLSRegistry</name> <thead> <tr> <th align="left">Value</th> <th align="left">Meaning</th> <th align="left">Reference</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> </tr> <tr> <td align="left">1</td> <td align="left">MPLS EchoRequest</c> <c> <xref target="RFC8029"/> </c> <c>2</c> <c>MPLSRequest</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">2</td> <td align="left">MPLS EchoReply</c> <c> <xref target="RFC8029"/> </c> <c>3</c> <c>Reply</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">3</td> <td align="left"> MPLS Proxy PingRequest</c> <c> <xref target="RFC7555"/> </c> <c>4</c> <c>Request</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">4</td> <td align="left"> MPLS Proxy PingReply</c> <c> <xref target="RFC7555"/> </c> <c>5</c> <c>Reply</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">5</td> <td align="left"> MPLS Relayed EchoReply</c> <c> <xref target="RFC7743"/> </c> <c>6-247</c> <c>Unassigned</c> <c> </c> <c>248-251</c> <c>Reserved for Experimental Use</c> <c>This document</c> <c>252-255</c> <c>ReservedReply</td> <td align="left"> <xref target="RFC7743" format="default"/> </td> </tr> <tr> <td align="left">6-247</td> <td align="left">Unassigned</td> <td align="left"> </td> </tr> <tr> <td align="left">248-251</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Reserved for PrivateUse</c> <c><xref target="RFC8029"/></c> </texttable>Use</td> <td align="left"> <xref target="RFC8029" format="default"/></td> </tr> </tbody> </table> </section> <section anchor="rm-upd"title="Updatesnumbered="true" toc="default"> <name>Updates to the Reply Modesregistry">Registry</name> <t>This isThese are the changes to the"Reply Modes""<xref target="IANA-RM" format="title"/>" registry specified in this document:<list style="symbols"> <t></t> <ul spacing="normal"> <li> Code Point 0 (zero)ishas been marked Reserved.</t> <t></li> <li> The registration procedure "Specification Required"ishas been changed to "RFCRequired"Required", and the comment "Experimental RFC needed"ishas been removed.</t> <t></li> <li> Four codepointpoints have been taken from what wasearlierpreviously "Specification Required" to form a set of code points for "Experimental Use".</t> </list> </t></li> </ul> <t> The registration procedures after the changes for the"Reply Modes""<xref target="IANA-RM" format="title"/>" registry areshowshown in the table below: </t><texttable title="Reply<table anchor="rm-reg-prov-texttab" align="center"> <name>Reply Modesregistration procedures" anchor="rm-reg-prov-texttab"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-191</c> <c>Standards Action</c> <c></c> <c>192-247</c> <c>RFC Required</c> <c></c> <c>248-251</c> <c>Experimental Use</c> <c>Reserved,Registration Procedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-191</td> <td align="left">Standards Action</td> <td align="left"/> </tr> <tr> <td align="left">192-247</td> <td align="left">RFC Required</td> <td align="left"/> </tr> <tr> <td align="left">248-251</td> <td align="left">Experimental Use</td> <td align="left">Reserved, not to beassigned</c> <c>252-255</c> <c>Private Use</c> <c>Reserved,assigned</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Private Use</td> <td align="left">Reserved, not to beassigned</c> </texttable>assigned</td> </tr> </tbody> </table> <t> The updated assignments for the"Reply Modes""<xref target="IANA-RM" format="title"/>" registrywill look like this:are as follows: </t><texttable title="Assignments<table anchor="rm-texttab" align="center"> <name>Assignments for the Reply Modesregistry" anchor="rm-texttab"> <ttcol align='left' width="8%">Value</ttcol> <ttcol align='left' width="62%">Meaning</ttcol> <ttcol align='left' width="40%">Reference</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c>1</c> <c>Do not reply</c> <c> <xref target="RFC8029"/> </c> <c>2</c> <c>ReplyRegistry</name> <thead> <tr> <th align="left">Value</th> <th align="left">Meaning</th> <th align="left">Reference</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> </tr> <tr> <td align="left">1</td> <td align="left">Do not reply</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">2</td> <td align="left">Reply via an IPv4/IPv6 UDPpacket</c> <c> <xref target="RFC8029"/> </c> <c>3</c> <c>Replypacket</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">3</td> <td align="left">Reply via an IPv4/IPv6 UDP packet with RouterAlert</c> <c> <xref target="RFC8029"/> </c> <c>4</c> <c>Alert</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">4</td> <td align="left"> Reply via application-level controlchannel</c> <c> <xref target="RFC8029"/> </c> <c>5</c> <c>Replychannel</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">5</td> <td align="left">Reply via SpecifiedPath</c> <c> <xref target="RFC7110"/> </c> <c>6-247</c> <c>Unassigned</c> <c> </c> <c>248-251</c> <c>Reserved for Experimental Use</c> <c>This document</c> <c>252-255</c> <c>ReservedPath</td> <td align="left"> <xref target="RFC7110" format="default"/> </td> </tr> <tr> <td align="left">6-247</td> <td align="left">Unassigned</td> <td align="left"> </td> </tr> <tr> <td align="left">248-251</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Reserved for PrivateUse</c> <c><xref target="RFC8029"/></c> </texttable>Use</td> <td align="left"> <xref target="RFC8029" format="default"/></td> </tr> </tbody> </table> </section> <section anchor="rc-upd"title="Updatesnumbered="true" toc="default"> <name>Updates to the Return Codesregistry">Registry</name> <t> These are the changes to the"Return Codes""<xref target="IANA-RC" format="title"/>" registry specified in this document:<list style="symbols"> <t></t> <ul spacing="normal"> <li> The registration procedure "Specification Required"ishas been changed to "RFCRequired"Required", and the comment "Experimental RFC needed"ishas been removed.</t> <t></li> <li> Four codepointpoints have been taken from what wasearlierpreviously "Specification Required" to form a set of code points for "Experimental Use".</t> </list> </t></li> </ul> <t> The registration procedures after the changes for the"Return Codes""<xref target="IANA-RC" format="title"/>" registry areshowshown in the table below: </t><texttable title="Return<table anchor="rc-reg-proc-texttab" align="center"> <name>Return Codesregistration procedures" anchor="rc-reg-proc-texttab"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-191</c> <c>Standards Action</c> <c></c> <c>192-247</c> <c>RFC Required</c> <c></c> <c>248-251</c> <c>Experimental Use</c> <c>Reserved,Registration Procedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-191</td> <td align="left">Standards Action</td> <td align="left"/> </tr> <tr> <td align="left">192-247</td> <td align="left">RFC Required</td> <td align="left"/> </tr> <tr> <td align="left">248-251</td> <td align="left">Experimental Use</td> <td align="left">Reserved, not to beassigned</c> <c>252-255</c> <c>Private Use</c> <c>Reserved,assigned</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Private Use</td> <td align="left">Reserved, not to beassigned</c> </texttable>assigned</td> </tr> </tbody> </table> <t> The updated assignments for the"Return Codes""<xref target="IANA-RC" format="title"/>" registrywill look like this:are as follows: </t><texttable title="Assignments<table anchor="rc-texttab" align="center"> <name>Assignments for the Return Codesregistry" anchor="rc-texttab"> <ttcol align='left' width="8%">Value</ttcol> <ttcol align='left' width="62%">Meaning</ttcol> <ttcol align='left' width="40%">Reference</ttcol> <c>0</c> <c>NoRegistry</name> <thead> <tr> <th align="left">Value</th> <th align="left">Meaning</th> <th align="left">Reference</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">No ReturnCode</c> <c>This document</c> <c>1</c> <c>MalformedCode</td> <td align="left"><xref target="RFC8029" format="default"/></td> </tr> <tr> <td align="left">1</td> <td align="left">Malformed echo requestreceived</c> <c> <xref target="RFC8029"/> </c> <c>2</c> <c>Onereceived</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">2</td> <td align="left">One or more of the TLVs was notunderstood</c> <c> <xref target="RFC8029"/> </c> <c>3</c> <c>Replyingunderstood</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">3</td> <td align="left">Replying router is an egress for the FEC at stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>4</c> <c>Replying</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">4</td> <td align="left">Replying router has no mapping for the FEC at stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>5</c> <c>Downstream</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">5</td> <td align="left">Downstream Mapping Mismatch (See[1])</c> <c> <xref target="RFC8029"/> </c> <c>6</c> <c>Upstream[1])</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">6</td> <td align="left">Upstream Interface Index Unknown (See[1])</c> <c> <xref target="RFC8029"/> </c> <c>7</c> <c>Reserved</c> <c> <xref target="RFC8029"/> </c> <c>8</c> <c>Label[1])</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">7</td> <td align="left">Reserved</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">8</td> <td align="left">Label switched at stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>9</c> <c>Label</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">9</td> <td align="left">Label switched but no MPLS forwarding at stack-depth<RSC> </c> <c> <xref target="RFC8029"/> </c> <c>10</c> <c>Mapping<RSC> </td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">10</td> <td align="left">Mapping for this FEC is not the given label at stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>11</c> <c></td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">11</td> <td align="left"> No label entry at stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>12</c> <c>Protocol</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">12</td> <td align="left">Protocol not associated with interface at FEC stack-depth <RSC></c> <c> <xref target="RFC8029"/> </c> <c>13</c> <c>Premature</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">13</td> <td align="left">Premature termination of ping due to label stack shrinking to a singlelabel</c> <c> <xref target="RFC8029"/> </c> <c>14</c> <c>Seelabel</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">14</td> <td align="left">See DDMAP TLV for meaning of Return Code and Return Subcode (See[2])</c> <c> <xref target="RFC8029"/> </c> <c>15</c> <c>[2])</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">15</td> <td align="left"> Label switched with FECchange</c> <c> <xref target="RFC8029"/> </c> <c>16</c> <c>Proxychange</td> <td align="left"> <xref target="RFC8029" format="default"/> </td> </tr> <tr> <td align="left">16</td> <td align="left">Proxy Ping notauthorized</c> <c> <xref target="RFC7555"/> </c> <c>17</c> <c>Proxyauthorized</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">17</td> <td align="left">Proxy Ping parameters need to bemodified</c> <c> <xref target="RFC7555"/> </c> <c>18</c> <c>MPLSmodified</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">18</td> <td align="left">MPLS Echo Request could not besent</c> <c> <xref target="RFC7555"/> </c> <c>19</c> <c>Replyingsent</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">19</td> <td align="left">Replying router has FEC mapping for topmostFEC</c> <c> <xref target="RFC7555"/> </c> <c>20</c> <c>OneFEC</td> <td align="left"> <xref target="RFC7555" format="default"/> </td> </tr> <tr> <td align="left">20</td> <td align="left">One or more TLVs not returned due to MTUsize</c> <c> <xref target="RFC7743"/> </c> <c>21</c> <c>OAMsize</td> <td align="left"> <xref target="RFC7743" format="default"/> </td> </tr> <tr> <td align="left">21</td> <td align="left">OAM Problem/Unsupported BFDVersion</c> <c> <xref target="RFC7759"/> </c> <c>22</c> <c>Version</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">22</td> <td align="left"> OAM Problem/Unsupported BFD Encapsulationformat</c> <c> <xref target="RFC7759"/> </c> <c>23</c> <c>OAMformat</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">23</td> <td align="left">OAM Problem/Unsupported BFD AuthenticationType</c> <c> <xref target="RFC7759"/> </c> <c>24</c> <c>OAMType</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">24</td> <td align="left">OAM Problem/Mismatch of BFD Authentication KeyID</c> <c> <xref target="RFC7759"/> </c> <c>25</c> <c>OAMID</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">25</td> <td align="left">OAM Problem/Unsupported TimestampFormat</c> <c> <xref target="RFC7759"/> </c> <c>26</c> <c>OAMFormat</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">26</td> <td align="left">OAM Problem/Unsupported DelayMode</c> <c> <xref target="RFC7759"/> </c> <c>27</c> <c>OAMMode</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">27</td> <td align="left">OAM Problem/Unsupported LossMode</c> <c> <xref target="RFC7759"/> </c> <c>28</c> <c>OAMMode</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">28</td> <td align="left">OAM Problem/Delay variationunsupported</c> <c> <xref target="RFC7759"/> </c> <c>29</c> <c>OAMunsupported</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">29</td> <td align="left">OAM Problem/Dyadic modeunsupported</c> <c> <xref target="RFC7759"/> </c> <c>30</c> <c>OAMunsupported</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">30</td> <td align="left">OAM Problem/Loopback modeunsupported</c> <c> <xref target="RFC7759"/> </c> <c>31</c> <c>unsupported</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">31</td> <td align="left"> OAM Problem/Combined modeunsupported</c> <c> <xref target="RFC7759"/> </c> <c>32</c> <c>unsupported</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">32</td> <td align="left"> OAM Problem/Fault management signalingunsupported</c> <c> <xref target="RFC7759"/> </c> <c>33</c> <c>OAMunsupported</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">33</td> <td align="left">OAM Problem/Unable to create fault managementassociation</c> <c> <xref target="RFC7759"/> </c> <c>34</c> <c>association</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">34</td> <td align="left"> OAM Problem/PM ConfigurationError</c> <c> <xref target="RFC7759"/> </c> <c>35</c> <c>MappingError</td> <td align="left"> <xref target="RFC7759" format="default"/> </td> </tr> <tr> <td align="left">35</td> <td align="left">Mapping for this FEC is not associated with the incoming interface</c> <c> <xref target="RFC8287"/> sec 7.4</c> <c>36-247</c> <c>Unassigned</c> <c> </c> <c>248-251</c> <c>Reserved for Experimental Use</c> <c>This document</c> <c>252-255</c> <c>Reserved</td> <td align="left"> <xref target="RFC8287" sectionFormat="comma" section="7.4"/></td> </tr> <tr> <td align="left">36-247</td> <td align="left">Unassigned</td> <td align="left"> </td> </tr> <tr> <td align="left">248-251</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> </tr> <tr> <td align="left">252-255</td> <td align="left">Reserved for PrivateUse</c> <c><xref target="RFC8029"/></c> </texttable> <t>Use</td> <td align="left"> <xref target="RFC8029" format="default"/></td> </tr> </tbody> </table> <dl> <dt> Note1:1:</dt><dd> Notes [1] and [2] for code points 5,66, and 14 point to footnotes in the"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters""<xref target="IANA-LSP-PING" format="title"/>" namespace. The footnotes are not changed by this document.</t> <t></dd> <dt> Note2:2:</dt><dd> <RSC> stands for "Return Subcode" and is explained insection 3.1 of RFC 8029<xreftarget="RFC8029"/>. </t>target="RFC8029" sectionFormat="of" section="3.1"/>. </dd></dl> </section> </section> <section anchor="upd-tls-sub-tlv"title="Updatesnumbered="true" toc="default"> <name>Updates to the TLV and Sub-TLVregistries">Registries</name> <t> The updates to the TLV and the sub-TLV registries are mostly thesame, howeversame; however, the<xref"<xref target="IANA-Sub-9"format="title"/>format="title"/>" <xreftarget="IANA-Sub-9"/> havetarget="IANA-Sub-9" format="default"/> registry has not been updated. </t> <t> Note that when a field in an assignment table says "EQ", it means that there is no change from the existing field in the "<xref target="lsp-ping-Namespace" format="title"/>" namespace <xreftarget="IANA-LSP-PING"/>target="IANA-LSP-PING" format="default"/>. </t> <section anchor="upds-tlv"title="Updatesnumbered="true" toc="default"> <name>Updates to the TLVsregistry">Registry</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-TLV-reg" format="title"/>" registry <xreftarget="IANA-TLV-reg"/>target="IANA-TLV-reg" format="default"/> that are based onthe new registration procedures.them. </t> <t> The registration procedures have been changed, as follows, for the "<xref target="IANA-TLV-reg" format="title"/>" registry. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFCRequired", theRequired". The comment "Experimental RFC Required" has been removed. Note that when a field in an assignment table says "EQ", it means that there is no change from the existing field in the "<xref target="lsp-ping-Namespace" format="title"/>" namespace <xreftarget="IANA-LSP-PING"/>. </t> <t> RFC 8611target="IANA-LSP-PING" format="default"/>. </li> <li> <xref target="RFC8611"/> was published afterRFC 8126<xref target="RFC8126"/> and uses the new terminology,e.g.e.g., "Private Use". The code points registration procedure "Private Use" has been replaced by the "FirstCome,Come First Served" code point registrationproceedure. </t> <t>procedure. </li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-TLV-reg" format="title"/>" registry <xreftarget="IANA-TLV-reg"/> will now look like this:target="IANA-TLV-reg" format="default"/> after the changes listed above are shown in the table below: </t><texttable title="TLV<table anchor="tlv-reg-proc" align="center"> <name>TLVs RegistrationProcedures" anchor="tlv-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisProcedures</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forsub-TLVsTLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for TLVs that can be silently dropped if notrecognized.</c> </texttable>recognized.</td> </tr> </tbody> </table> <t> The<xref target="tlv-assign" format="title"/> will now look like this.updated assignments for this registry appear as follows: </t> <t> Note that when a field in an assignment table says "EQ", it means that thereiswas no change from the existing field in the "<xref target="lsp-ping-Namespace" format="title"/>" namespace <xreftarget="IANA-LSP-PING"/>target="IANA-LSP-PING" format="default"/>. </t><texttable title="TLV Assignments" anchor="tlv-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Sub-TLV Registry</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c></c> <c>1-7</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>8</c> <c>Unassigned</c> <c></c> <c></c> <c>9-16</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>17-19</c> <c>unassigned</c> <c></c> <c></c> <c>20-27</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>28-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, not<table anchor="tlv-assign" align="center"> <name>TLV Assignments</name> <thead> <tr> <th align="left">Type</th> <th align="left">TLV Name</th> <th align="left">Reference</th> <th align="left">Sub-TLV Registry</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> <td align="left"/> </tr> <tr> <td align="left">1-7</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">8</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">9-16</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">17-19</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">20-27</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">28-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forsub-TLVsTLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>Unassigned</c> <c></c> <c></c> <c>32768-32770</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>32771-64507</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>64508-64511</c> <c>Experimental Use.</c> <c>This document</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">32768-32770</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">32771-64507</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section> <section anchor="upds-sub-tlv-1-16-21"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs forTLVsTLV Types 1,1616, and21">21</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-1-16-21"format="title" />"format="title"/>" <xreftarget="IANA-Sub-1-16-21"/> sub-registrytarget="IANA-Sub-1-16-21" format="default"/> subregistry that are based onthe new registration procedures.them. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFC Required", and the comment "Experimental RFC Required" has been removed.</t> <t></li> <li> The code points registration procedure "Vendor Private Use" has been removed and replaced with "FirstCome,Come First Served"code points. </t> <t>procedure. </li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-1-16-21"format="title" />"format="title"/>" <xreftarget="IANA-Sub-1-16-21"/> sub-registry will now look like this:target="IANA-Sub-1-16-21" format="default"/> subregistry appear as follows after the changes listed above: </t><texttable title="Registration<table anchor="sub-tlv-1-16-21-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs forTLVsTLV Types 1,1616, and21" anchor="sub-tlv-1-16-21-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>This21</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-1-16-21-assign" align="center"> <name>Sub-TLV forTLVTLVs 1,1616, and 21Assignments" anchor="sub-tlv-1-16-21-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c></c> <c>1-4</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>5</c> <c>Unassigned</c> <c></c> <c></c> <c>6-8</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>9</c> <c>EQ</c> <c>EQ</c> <c>DEPRECATED</c> <c>10-20</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>21</c> <c>unassigned</c> <c></c> <c></c> <c>22-37</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>38-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> <td align="left"/> </tr> <tr> <td align="left">1-4</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">5</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">6-8</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">9</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">DEPRECATED</td> </tr> <tr> <td align="left">10-20</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">21</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">22-37</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">38</td> <td align="left">PeerAdj SID Sub-TLV</td> <td align="left">[draft-ietf-mpls-sr-epe-oam-03]</td> <td align="left">TEMPORARY - registered 2021-05-11, expires 2022-05-11</td> </tr> <tr> <td align="left">39</td> <td align="left">PeerNode SID Sub-TLV</td> <td align="left">[draft-ietf-mpls-sr-epe-oam-03]</td> <td align="left">TEMPORARY - registered 2021-05-11, expires 2022-05-11</td> </tr> <tr> <td align="left">40</td> <td align="left">PeerSet SID Sub-TLV</td> <td align="left">[draft-ietf-mpls-sr-epe-oam-03]</td> <td align="left">TEMPORARY - registered 2021-05-11, expires 2022-05-11</td> </tr> <tr> <td align="left">41-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use</c> <c>This document</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section><!-- section 6.3.3 --><section anchor="upds-sub-tlv-6"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs for TLV6">Type 6</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-6"format="title" />"format="title"/>" <xreftarget="IANA-Sub-6"/> sub-registry based on the new registration procedures.target="IANA-Sub-6" format="default"/> subregistry that are based on them. </t><t> <list style="symbols"> <t> RFC 8611<ul spacing="normal"> <li> <xref target="RFC8611"/> was published afterRFC 8126<xref target="RFC8126"/> and uses the new terminology,e.g.e.g., "Private Use". The code points registration procedure "Private Use" has been replaced by the "Firstcome,Come First Served" code point registrationproceedure. </t> <t>procedure. </li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-6"format="title" />"format="title"/>" <xreftarget="IANA-Sub-6"/> sub-registry will now look like this:target="IANA-Sub-6" format="default"/> subregistry after the changes listed above are shown in the table below: </t><texttable title="Registration<table anchor="sub-tlv-6-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs forTLVs 6" anchor="sub-tlv-6-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisTLV Type 6</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVsrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-6-assign" align="center"> <name>Sub-TLVs for TLV Type 6Assignments" anchor="sub-tlv-6-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c></c> <c>1-2</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>3-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document, <xref target="RFC8611"/></td> <td align="left"/> </tr> <tr> <td align="left">1-2</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">3-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use.</c> <c>This document</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section><!-- section 6.3.4 --><section anchor="upds-sub-tlv-11"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs for TLV11">Type 11</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-11"format="title" />"format="title"/>" <xreftarget="IANA-Sub-11"/> sub-registrytarget="IANA-Sub-11" format="default"/> subregistry that are based onthe new registration procedures.them. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFC Required", and the comment "Experimental RFC Required" has been removed.</t> <t></li> <li> The code points registration procedure "Vendor Private Use" has been removed and replaced with "FirstCome,Come First Served" code points.</t> <t></li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-11"format="title" />"format="title"/>" <xreftarget="IANA-Sub-11"/> sub-registry will now look like this:target="IANA-Sub-11" format="default"/> subregistry after the changes listed above are shown in the table below: </t><texttable title="Registration<table anchor="sub-tlv-11-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs forTLVs 11" anchor="sub-tlv-11-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisTLV Type 11</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/></td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVsrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-11-assign" align="center"> <name>Sub-TLVs for TLV Type 11Assignments" anchor="sub-tlv-11-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c></c> <c>1-4</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>5-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> <td align="left"/> </tr> <tr> <td align="left">1-4</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">5-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use</c> <c>This document</c> <c>Reserved, not<xref target="principles"/></td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section> <section anchor="upds-sub-tlv-20"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs for TLV20">Type 20</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-20"format="title" />"format="title"/>" <xreftarget="IANA-Sub-20"/> sub-registrytarget="IANA-Sub-20" format="default"/> subregistry that are based onthe new registration procedures.them. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFC Required", and the comment "Experimental RFC Required" has been removed.</t> <t></li> <li> The code points registration procedure "Vendor Private Use" has been removed and replaced with "FirstCome,Come First Served" code points.</t> <t></li> <li> Two small sets,4four codevepoints each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-20"format="title" />"format="title"/>" <xreftarget="IANA-Sub-20"/> sub-registry will now look like this:target="IANA-Sub-20" format="default"/> subregistry after the changes listed above are shown in the table below: </t><texttable title="Registration<table anchor="sub-tlv-20-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs forTLVs 20" anchor="sub-tlv-20-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisTLV Type 20</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVsrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-20-assign" align="center"> <name>Sub-TLVs for TLV Type 20Assignments" anchor="sub-tlv-20-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c>This document</c> <c></c> <c>1-5</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>6-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left">This document</td> <td align="left"/> </tr> <tr> <td align="left">1-5</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">6-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use</c> <c>This document</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section> <section anchor="upds-sub-tlv-23"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs for TLV23">Type 23</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-23"format="title" />"format="title"/>" <xreftarget="IANA-Sub-23"/> sub-registrytarget="IANA-Sub-23" format="default"/> subregistry that are based onthe new registration procedures.them. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFC Required", and the comment "Experimental RFC Required" has been removed.</t> <t></li> <li> The code points registration procedure "Vendor Private Use" has been removed and replaced with "FirstCome,Come First Served" code points.</t> <t></li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-23"format="title" />"format="title"/>" <xreftarget="IANA-Sub-23"/> sub-registry will now look like this:target="IANA-Sub-23" format="default"/> subregistry after the changes listed above are shown in the table below: </t><texttable title="Registration<table anchor="sub-tlv-23-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs forTLVs 23" anchor="sub-tlv-23-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisTLV Type 23</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved, notrecognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVsrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-23-assign" align="center"> <name>Sub-TLVs for TLV Type 23Assignments" anchor="sub-tlv-23-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c><xref target="RFC7555"/></c> <c></c> <c>1</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>2-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left"> <xref target="RFC7555" format="default"/></td> <td align="left"/> </tr> <tr> <td align="left">1</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">2-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use</c> <c>This document</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section> <section anchor="upds-sub-tlv-27"title="Updatesnumbered="true" toc="default"> <name>Updates to theregistryRegistry for Sub-TLVs for TLV27">Type 27</name> <t> This section describes the new registration procedures and the assignments for the "<xref target="IANA-Sub-27"format="title" />"format="title"/>" <xreftarget="IANA-Sub-27"/> sub-registrytarget="IANA-Sub-27" format="default"/> subregistry that are based onthe new registration procedures.them. </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> The "Specification Required" registration procedure has been changed to "RFC Required", and the comment "Experimental RFC Required" has been removed.</t> <t></li> <li> The code points registration procedure "Vendor Private Use" has been removed and replaced with "FirstCome,Come First Served" code points.</t> <t></li> <li> Two small sets,4four code points each, have been created for Experimental Use.</t> <t></li> <li> Code points that are reserved are clearly marked as such.</t> <t></li> <li> The assignments have been updated to match the new registration procedures.</t> <t></li> <li> The notes related to the registration procedures have been changed to reflect whether or not a response is requiredor notif a sub-TLV is not recognized.</t> </list> </t></li> </ul> <t> The registration procedures for the "<xref target="IANA-Sub-27"format="title" />"format="title"/>" <xreftarget="IANA-Sub-27"/> sub-registry will now look like this:target="IANA-Sub-27" format="default"/> subregistry after the changes listed above are shown in the table below: </t><texttable title="Registration<table anchor="sub-tlv-27-reg-proc" align="center"> <name>Registration Procedures for Sub-TLVs for TLV27" anchor="sub-tlv-27-reg-proc"> <ttcol align='left' width="8%">Range</ttcol> <ttcol align='left' width="33%">Registration Procedures</ttcol> <ttcol align='left' width="69%">Note</ttcol> <c>0-16383</c> <c>Standards Action</c> <c>ThisType 27</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <th align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-16383</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>16384-31739</c> <c>RFC Required</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">16384-31739</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31740-31743</c> <c>Experimental Use</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-32767</c> <c>FCFS</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-32767</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>32768-49161</c> <c>Standards Action</c> <c>This<xref target="principles"/>]</td> </tr> <tr> <td align="left">32768-49161</td> <td align="left">Standards Action</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>49162-64507</c> <c>RFC Required</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">49162-64507</td> <td align="left">RFC Required</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> <c>64508-64511</c> <c>Experimental Use</c> <c>Reserved,recognized.</td> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Experimental Use</td> <td align="left">Reserved, not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>FCFS</c> <c>Thisrecognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">FCFS</td> <td align="left">This range is for sub-TLVs that can be silently dropped if notrecognized.</c> </texttable> <texttable title="Sub-TLVsrecognized.</td> </tr> </tbody> </table> <table anchor="sub-tlv-27-assign" align="center"> <name>Sub-TLVs for TLV Type 27Assignments" anchor="sub-tlv-27-assign"> <ttcol align='left' width="8%">Type</ttcol> <ttcol align='left' width="33%">TLV Name</ttcol> <ttcol align='left' width="69%">Reference</ttcol> <ttcol align='left' width="69%">Comment</ttcol> <c>0</c> <c>Reserved</c> <c><xref target="RFC7759"/></c> <c></c> <c>1-99</c> <c>Unassigned</c> <c></c> <c></c> <c>100-104</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>105-199</c> <c>Unassigned</c> <c></c> <c></c> <c>200-202</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>203-299</c> <c>Unassigned</c> <c></c> <c></c> <c>300</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>301-399</c> <c>Unassigned</c> <c></c> <c></c> <c>400</c> <c>EQ</c> <c>EQ</c> <c>EQ</c> <c>401-31739</c> <c>Unassigned</c> <c></c> <c></c> <c>31740-31743</c> <c>Experimental Use</c> <c>This Document</c> <c>Reserved, notAssignments</name> <thead> <tr> <th align="left">Sub-Type</th> <th align="left">Sub-TLV Name</th> <th align="left">Reference</th> <th align="left">Comment</th> </tr> </thead> <tbody> <tr> <td align="left">0</td> <td align="left">Reserved</td> <td align="left"> <xref target="RFC7759" format="default"/></td> <td align="left"/> </tr> <tr> <td align="left">1-99</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">100-104</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">105-199</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">200-202</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">203-299</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">300</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">301-399</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">400</td> <td align="left">EQ</td> <td align="left">EQ</td> <td align="left">EQ</td> </tr> <tr> <td align="left">401-31739</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">31740-31743</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is for sub-TLVs that require an error message if not recognized.[ThisThis document,section 3.1]</c> <c>31744-64507</c> <c>Unassigned</c> <c></c> <c></c> <c>64508-64511</c> <c>Experimental Use</c> <c>This document</c> <c>Reserved, not<xref target="principles"/>]</td> </tr> <tr> <td align="left">31744-64507</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> <tr> <td align="left">64508-64511</td> <td align="left">Reserved for Experimental Use</td> <td align="left">This document</td> <td align="left">Not to be assigned. This range is forTLVssub-TLVs that can be silently dropped if notrecognized.</c> <c>64512-65535</c> <c>Unassigned</c> <c></c> <c></c> </texttable>recognized.</td> </tr> <tr> <td align="left">64512-65535</td> <td align="left">Unassigned</td> <td align="left"/> <td align="left"/> </tr> </tbody> </table> </section> </section> </section><section anchor="Acknowledgements" title="Acknowledgements"> <t> The authors wish to thank Adrian Farrel, who both made very useful comments and agreed to serve as the document shepherd. </t> <t> The authors also wish to thank Michelle Cotton and Amanda Baber who very patiently worked with us to determine how our registries could and should be updated. </t> <t> The authors thanks Donald Eastlake and Tom Petch for careful and detailed reviews. </t> </section></middle> <back><references title="Normative References"> <?rfc include="reference.RFC.2119"?> <?rfc include="reference.RFC.8029"?> <?rfc include="reference.RFC.8126"?> <?rfc include="reference.RFC.8174"?> <?rfc include="reference.RFC.8611"?><references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8029.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8611.xml"/> <reference anchor="IANA-LSP-PING"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml/">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters"> <front> <title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters</title> <author/> <date/> </front> </reference> <reference anchor="IANA-MT"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#message-types">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Message Types</title> <author/> <date/> </front> </reference> <reference anchor="IANA-RM"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/#reply-modes">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Reply Modes</title> <author/> <date/> </front> </reference> <reference anchor="IANA-RC"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/#return-codes">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Return Codes</title> <author/> <date/> </front> </reference> <reference anchor="IANA-TLV-reg"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#tlvs">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>TLVs</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-1-16-21"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-1-16-21">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Types 1, 16, and 21</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-6"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-6">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 6</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-11"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-11">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 11</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-20"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-20">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 20</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-23"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-23">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 23</title> <author/> <date/> </front> </reference> <reference anchor="IANA-Sub-27"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-27">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 27</title> <author/> <date/> </front> </reference> </references><references title="Informative References"> <!-- <?rfc include="reference.RFC.7759"?> --> <?rfc include="reference.RFC.7110"?> <?rfc include="reference.RFC.7555"?> <?rfc include="reference.RFC.7743"?> <?rfc include="reference.RFC.7759"?> <?rfc include="reference.RFC.8287"?><references> <name>Informative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7110.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7555.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7743.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7759.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8287.xml"/> <reference anchor="IANA-Sub-9"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-9">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Sub-TLVs for TLV Type 9</title> <author/> <date/> </front> </reference> <reference anchor="lsp-ping-Namespace"target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml">target="https://www.iana.org/assignments/mpls-lsp-ping-parameters/"> <front> <title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters</title> <author/> <date/> </front> </reference> </references> </references> <section anchor="Acknowledgements" numbered="false" toc="default"> <name>Acknowledgements</name> <t> The authors wish to thank <contact fullname="Adrian Farrel"/>, who both made very useful comments and agreed to serve as the Document Shepherd. </t> <t> The authors also wish to thank <contact fullname="Michelle Cotton"/> and <contact fullname="Amanda Baber"/>, who very patiently worked with us to determine how our registries could and should be updated. </t> <t> The authors thank <contact fullname="Donald Eastlake 3rd"/> and <contact fullname="Tom Petch"/> for their careful and detailed review. </t> </section> </back> </rfc>