Diff: rfc9041xml2.original.xml

	rfc9041xml2.original.xml	rfc9041.xml

	<?xml version="1.0" encoding="US-ASCII"?>	<?xml version="1.0" 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"?>
	<rfc category="std" docName="draft-ietf-mpls-lsp-ping-registries-update-11"
	ipr="trust200902" updates="8029, 8611">
	<front>


	<title abbrev="LSP Ping Registries">Updating the IANA MPLS LSP Ping Paramete rs</title>	<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">


		<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-mpls-lsp-pin
		g-registries-update-11" number="9041" ipr="trust200902" updates="8029, 8611" obs
		oletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" to
		cInclude="true" tocDepth="3" symRefs="true" sortRefs="true" version="3">

		<front>

		<title abbrev="LSP Ping Registries">Updating the MPLS Label Switched Paths (
		LSPs) Ping Parameters IANA Registry</title>
		<seriesInfo name="RFC" value="9041"/>
	<author fullname="Loa Andersson" initials="L." surname="Andersson">	<author fullname="Loa Andersson" initials="L." surname="Andersson">
	<organization>Bronze Dragon Consulting</organization>	<organization>Bronze Dragon Consulting</organization>


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


	<city/>	<city/>


	<region/>	<region/>


	<code/>	<code/>


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


	<email>loa@pi.nu</email>	<email>loa@pi.nu</email>
	</address>	</address>
	</author>	</author>

		<author fullname="Mach(Guoyi) Chen" initials="M." surname="Chen">
	<author fullname="Mach Chen" initials="M." surname="Chen">
	<organization>Huawei Technologies</organization>	<organization>Huawei Technologies</organization>


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


	<city/>	<city/>


	<region/>	<region/>


	<code/>	<code/>


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


	<email>mach.chen@huawei.com</email>	<email>mach.chen@huawei.com</email>
	</address>	</address>
	</author>	</author>

		<author fullname="Carlos Pignataro" initials="C." surname="Pignataro">
	<author fullname="Carlos Pignataro" initials="C." surname="Pignataro">
	<organization>Cisco Systems</organization>	<organization>Cisco Systems</organization>


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


	<city/>	<city/>


	<region/>	<region/>


	<code/>	<code/>


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


	<email>cpignata@cisco.com</email>	<email>cpignata@cisco.com</email>
	</address>	</address>
	</author>	</author>

		<author fullname="Tarek Saad" initials="T." surname="Saad">
	<author fullname="Tarek Saad" initials="T." surname="Saad">
	<organization>Juniper Networks</organization>	<organization>Juniper Networks</organization>


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


	<city/>	<city/>


	<region/>	<region/>


	<code/>	<code/>


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


	<email>tsaad@juniper.net</email>	<email>tsaad@juniper.net</email>
	</address>	</address>
	</author>	</author>

		<date year="2021" month="July" />
		<workgroup>MPLS Working Group</workgroup>


	<date />	<abstract>
	<workgroup>MPLS Working Group</workgroup>

	<abstract>

	<t>
	This document updates RFC 8029 and RFC 8611 which both define IANA
	registries for MPLS Label Switched Path (LSP) Ping, in particular the
	registration procedure "Private Use" (esarlier know as "Vendor Private Use")
	is changed to "First Come, First Served" the TLV and Sub-TLV Registries.
	</t>


	<t>	<t>
		This document updates RFCs 8029 and 8611, both of which define IANA
		registries for MPLS Label Switched Path (LSP) Ping. In particular, the
		registration procedure "Private Use" (previously known as "Vendor Private Use
		")
		has been changed to "First Come First Served" for the TLV and sub-TLV registr
		ies.
		</t>
		<t>
	It also updates the description of the procedures for the responses sent	It also updates the description of the procedures for the responses sent
	when an unknown or erroneous code point is found.	when an unknown or erroneous code point is found.
	The updates are to clarify and align this namespace with recent developments,	The updates are to clarify and align this namespace with recent developments,

	e.g. the updates to " Guidelines for Writing an IANA Considerations	e.g., aligning terminology with RFC 8126 instead of the now obsoleted RFC 522
	Section in RFCs" (e.g. RFC 8126), instead of the terminology from the	6 (both titled "Guidelines for Writing an IANA Considerations Section in RFCs").
	obsoleted RFC 5226.	</t>
	</t>	</abstract>
		</front>
	</abstract>	<middle>
		<section anchor="intro" numbered="true" toc="default">
	</front>	<name>Introduction</name>
		<t>
	<middle>
	<!-- section 1 -->
	<section anchor="intro" title="Introduction">

	<t>
	There were a number of reasons to start the work that has led to this	There were a number of reasons to start the work that has led to this

	document, e.g.:	document, e.g.,
	<list style="symbols">	</t>
	<t>	<ul spacing="normal">
	When the LSP Ping registry was created it was incorrectly assumed that code	<li>
	points allocated by Experimental RFCs would be 'experimental' code points;	When the LSP Ping registry was created, it was incorrectly assumed that code
		points allocated by Experimental RFCs would be "experimental" code points;
	a code point	a code point
	made available in a public IANA registry is not limited by the type of RFC	made available in a public IANA registry is not limited by the type of RFC

	that made the allocation but is available for any document.	that made the allocation: it is available for use in any type of document.
	</t>


	<t>	</li>
	The number of 'experimental' code points was also too large, as compared to	<li>
		The number of "experimental" code points was also too large as compared to
	what is normally	what is normally
	allocated for "Experimental Use".	allocated for "Experimental Use".

	</t>	</li>
		<li>
	<t>	The words "mandatory" and "optional" are used differently in <xref target="R
	RFC 8029 uses the words "mandatory" and "optional" differently to how other	FC8029"/> than in other
	RFC do. RFC 8029 for example talks about mandatory TLVs to	RFCs. For example, <xref target="RFC8029"/> talks about mandatory TLVs to
	indicate that it is	indicate that it is

	mandatory to take a certain action if the TLV is found in a message but	mandatory to take a certain action if the TLV is found in a message but is n
	not recognized, other RFCs uses "mandatory TLV" to indicate a TLV that	ot recognized. Other RFCs use "mandatory TLV" to indicate a TLV that
	must be present in a message.	must be present in a message.

	</t>	</li>
		</ul>
	</list>	<t>


	Over time there have been attempts to administratively update some of the	Over time, there have been attempts to administratively update some of the
	registries, but it was soon decided that an RFC was needed. Other, often	registries, but it was soon decided that an RFC was needed. Other, often

	minor, potential updates were found, e.g. reserving the	minor, potential updates were found, e.g., reserving the
	value 0 (zero) in registries where that is possible.	value 0 (zero) in registries where that is possible.

	</t>	</t>
		<t>
	<t>	<xref target="RFC8029" format="default"/> contains
	When RFC 8029 <xref target="RFC8029"/> was published it contained	updates to the "<xref target="IANA-LSP-PING" format="title"/>" IANA namespac
	updates to the "Multiprotocol Label Switching (MPLS) Label	e <xref target="IANA-LSP-PING" format="default"/>.
	Switched Paths (LSPs)	</t>
	Ping Parameters" IANA namespace <xref target="IANA-LSP-PING"/>.	<t>
	</t>	<xref target="RFC8611" format="default"/> created LSP Ping IANA registries
		that
	<t>	match <xref target="RFC8126"/>. This document further clarifies the entrie
	RFC 8611 <xref target="RFC8611"/> created LSP Ping IANA registries that	s in those
	match RFC 8126. This document further clarifies the entries in those
	registries and makes the definitions more precise.	registries and makes the definitions more precise.

	</t>	</t>
		<t>
	<t>	This document updates <xref target="RFC8029" format="default"/> and
	This document updates RFC 8029 <xref target="RFC8029"/> and RFC 8611	<xref target="RFC8611" format="default"/> by updating two groups of registri
	<xref target="RFC8611"/> by updating two groups of registries as follows:	es as follows:
	</t>	</t>
		<t>
	<t>	First, the "Message Types" <xref target="IANA-MT" format="default"/>,
	First the registries for Message Types <xref target="IANA-MT"/>,	"Reply Modes" <xref target="IANA-RM" format="default"/>, and "Return Codes"
	Reply Modes <xref target="IANA-RM"/> and Return Codes <xref target="IANA-RC"	<xref target="IANA-RC" format="default"/> registries
	/>
	are updated.	are updated.
	The changes to these registries are minor.	The changes to these registries are minor.

	</t>	</t>
		<t>
	<t>	Second, this document updates the TLV and sub-TLV registries listed below:
	Second, this document updates the TLV and sub-TLV registries.	</t>
	<list style="symbols">	<ul spacing="normal">
		<li>
	<t>	"<xref target="IANA-TLV-reg" format="title"/>", <xref target="IANA-TLV
	<xref target="IANA-TLV-reg" format="title"/> <xref target="IANA-TLV-reg"/>.	-reg" format="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-1-16-21" format="title"/>", <xref target="IANA-Sub-1
	Sub-TLVs for TLVs 1, 16 and 21 <xref target="IANA-Sub-1-16-21"/>.	-16-21" format="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-6" format="title"/>", <xref target="IANA-Sub-6
	<xref target="IANA-Sub-6" format="title" /> <xref target="IANA-Sub-6"/>.	" format="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-11" format="title"/>", <xref target="IANA-Sub-11" forma
	Sub-TLVs for TLV 11 <xref target="IANA-Sub-11"/>.	t="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-20" format="title"/>", <xref target="IANA-Sub-20" fo
	Sub-TLVs for TLV 20 <xref target="IANA-Sub-20"/>.	rmat="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-23" format="title"/>", <xref target="IANA-Sub-23" for
	Sub-TLVs for TLV 23 <xref target="IANA-Sub-23"/>.	mat="default"/>
	</t>	</li>
		<li>
	<t>	"<xref target="IANA-Sub-27" format="title"/>", <xref target="IANA-Sub-27" fo
	Sub-TLVs for TLV 27 <xref target="IANA-Sub-27"/>.	rmat="default"/>
	</t>	</li>
	</list>	</ul>
	</t>	<t>
		It should be noted that <xref target="RFC8029"/> was published before <xref t
	<t>	arget="RFC8126"/> and
	It should be noted that RFC 8029 was published before RFC 8126 and	uses outdated terminology for some registration procedures, e.g.,
	uses old terminology for some registration procedures, e.g.,	"Vendor Private Use". <xref target="RFC8611"/> was published after <xref tar
	"Vendor Private Use". RFC 8611 was published after RFC 8126 and uses	get="RFC8126"/> and uses
	newer terminology, e.g., "Private Use". Both "Vendor Private Use"	its recommended terminology, e.g., "Private Use". However, now both "Vendor
	and "Private Use" has been removed and replaced with	Private Use"
	"First come, first served (FCFS) code points.	and "Private Use" have been removed and replaced with
	</t>	"First Come First Served" (FCFS) code points.
		</t>
	<t>	<t>


	One reason to change from code point allocated by Vendor Private Use	One reason to change from code points allocated by Vendor Private Use
	or Private Use is that such code points are allowed in production	or Private Use is that such code points are allowed in production
	networks. Theoretically, it is possible that two vendors might use the	networks. Theoretically, it is possible that two vendors might use the

	same code point value with different meanings. If such code is ever	same code point value with different meanings. If such a code is ever
	deployed in the same network this could cause protocol issues that	deployed in the same network, this could cause protocol issues that
	would be hard to debug.	would be hard to debug.

	</t>	</t>


	<t>	<t>
	With FCFS code points this will not happen. Vendors that have existing	With FCFS code points, this will not happen. Vendors that have existing
	code using Vendor Private Use or Private Use code points should	code using Vendor Private Use or Private Use code points should

	register those code points as FSFC code points soon as this document is	register those code points as FCFS code points as soon as this document is
	published as an RFC.	published as an RFC.

	</t>	</t>
		<t>
	<t>	The "<xref target="IANA-Sub-9" format="title"/>" subregistry is not updated.
	The registry for sub-TLVs for TLV 9 <xref target="IANA-Sub-9"/> is not updat	</t>
	ed.	<t>
	</t>	Third, according to <xref target="RFC8029"/>, some code points (TLVs and su
		b-TLVs)
	<t>
	Third, according to RFC 8029 some code points (TLVs and sub-TLVs)
	are called "mandatory" or	are called "mandatory" or
	"optional". Contrary to how other RFCs use these words, indicating	"optional". Contrary to how other RFCs use these words, indicating
	that it is mandatory or optional to include the code points in a	that it is mandatory or optional to include the code points in a

	message, RFC 8029 uses these words to indicate that an action might or	message, <xref target="RFC8029"/> uses these words to indicate that an acti
	might not be mandatory. This document updates RFC 8029 to drop the words	on might or
		might not be mandatory. This document updates <xref target="RFC8029"/> to
		drop the words
	"mandatory" and "optional", and the text is changed to focus on what	"mandatory" and "optional", and the text is changed to focus on what
	should be done.	should be done.

	</t>	</t>
		<section anchor="lang" numbered="true" toc="default">
	<section anchor="lang" title="Requirement Language">	<name>Requirements Language</name>
	<t>	<t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",	The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and	IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
	"OPTIONAL" in this document are to be interpreted as described in BCP	NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
	14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when,	RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
	they appear in all capitals, as shown here.	"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
	</t>	be interpreted as
	</section>	described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/>
	<section anchor="terms" title="Terminology">	when, and only when, they appear in all capitals, as shown here.
	<t>	</t>
	This section list terms that are used when discussing the hierarchy of	</section>
	IANA registers (<xref target="local-terms"/>)	<section anchor="terms" numbered="true" toc="default">
	and abbreviations used in IANA registries update in this document (<xref tar	<name>Terminology</name>
	get="abbr"/>).	<t>
	</t>	This section lists terms that are used when discussing the hierarchy of
	<section anchor="local-terms" title="Terminology Used in this Document">	IANA registries (<xref target="local-terms" format="default"/>),
		and abbreviations used in IANA registries are updated in this document (<xre
	<t>	f target="abbr" format="default"/>).
	This document uses some terms that relates to IANA registries in this way:	</t>
	<list style="symbol">	<section anchor="local-terms" numbered="true" toc="default">
		<name>Terminology Used in This Document</name>


	<t>	<t>
	IANA Name Space, <vspace blankLines="0"/> a namespace is a top level registr	Terms related to IANA registries are used as follows in this document:
	y.	</t>
		<dl newline="true">
		<dt>
		Namespace</dt>
		<dd> A namespace is a top-level registry.
	An example could be	An example could be

	"<xref target="lsp-ping-Namespace" format="title"/>" <xref target="IANA-LSP- PING"/>.	"<xref target="lsp-ping-Namespace" format="title"/>" <xref target="IANA-LSP- PING" format="default"/>.
	A namespace is most often a container for registries that hold code points	A namespace is most often a container for registries that hold code points
	that share some affinity.	that share some affinity.

	</t>	</dd>
		<dt>
		Registry</dt>


	<t>	<dd>An IANA registry holds code points
	IANA Registry, <vspace blankLines="0"/> an IANA registry holds code points,
	and lists the registration	and lists the registration

	procedures and allocation these code points. One example	procedures and allocation for these code points. One example
	would be the	would be the
	"<xref target="IANA-TLV-reg" format="title"/>" registry	"<xref target="IANA-TLV-reg" format="title"/>" registry

	<xref target="IANA-TLV-reg"/>.	<xref target="IANA-TLV-reg" format="default"/>.
	</t>	</dd>
		<dt>


	<t>	Subregistry</dt>
	IANA Sub-registry, <vspace blankLines="0"/> a sub-registry is used when a	<dd>A subregistry is used when a
	code point, or a set of code points allocated in a single registry, needs	code point, or a set of code points allocated in a single registry, needs

	"sub-code points" scoped by the code point or the set of code points. An	"sub-code-points" scoped by the code point or the set of code points. An
	example of a sub-registry that holds code points for more than one TLV is	example of a subregistry that holds code points for more than one TLV is
	"<xref target="IANA-Sub-1-16-21" format="title"/>" <xref target="IANA-Sub-1-	"<xref target="IANA-Sub-1-16-21" format="title"/>" <xref target="IANA-Sub-1-
	16-21"/>	16-21" format="default"/>.
	</t>	</dd>

	</list>

	</t>

	</section>

	<section title="Abbreviations" anchor="abbr">


	<t>	</dl>
	This section list abbreviations used in the unchanged part of the registries	</section>
		<section anchor="abbr" numbered="true" toc="default">
		<name>Abbreviations</name>
		<t>
		This section lists abbreviations used in the unchanged part of the registrie
		s
	updated by this document. These abbreviations were originally expanded in	updated by this document. These abbreviations were originally expanded in
	the document defining the registries. They are listed here following the	the document defining the registries. They are listed here following the

	requirement to expand any abbreviation that is not well-known. All these	requirement to expand any abbreviation that is not well known. All these
	abbreviations are from the <xref target="IANA-RC" format="title"/>	abbreviations are from the "<xref target="IANA-RC" format="title"/>"
	registry <xref target="IANA-RC"/>.	registry <xref target="IANA-RC" format="default"/>.
	</t>	</t>
		<dl indent="10">
	<t>	<dt>BFD:</dt><dd>Bidirectional Forwarding Detection
	<list style="symbol">	</dd>
		<dt>
	<t>	DDMAP:</dt><dd>Downstream Detailed Mapping
	BFD - Bidirectional Forwarding Detection	</dd>
	</t>	<dt>
		FEC:</dt><dd>Forwarding Equivalence Class
	<t>	</dd>
	DDMAP - Downstream Detailed Mapping	<dt>
	</t>	OAM:</dt><dd>Operation, Administration, and Maintenance
		</dd>
	<t>	<dt>
	FEC - Forwarding Equivalence Class	PM:</dt><dd>Performance Monitoring
	</t>	</dd>
		<dt>
	<t>	RSC:</dt><dd>Return Subcode
	OAM - Operation, Administration and Maintenance	</dd>
	</t>

	<t>
	PM - Performance Monitoring
	</t>

	<t>
	RSC - Return Subcode
	</t>
	</list>
	</t>

	</section>

	</section>


		</dl>
		</section>
		</section>
	</section>	</section>

		<section anchor="codes" numbered="true" toc="default">
		<name>Updating the Message Types, Reply Modes, and Return Codes Registries
		</name>
		<t>
		The following changes have been made to the "<xref target="IANA-MT" format="titl
		e"/>" <xref target="IANA-MT" format="default"/>,
		"<xref target="IANA-RM" format="title"/>" <xref target="IANA-RM" format="def
		ault"/>, and "<xref target="IANA-RC" format="title"/>"
		<xref target="IANA-RC" format="default"/> registries.


	<section anchor="codes" title="Updating the Message Types, Reply Mode and Re
	turn Codes Registries">

	<t>
	The following changes are made to the Message Types <xref target="IANA-MT"/>,
	Reply Modes <xref target="IANA-RM"/> and Return Codes
	<xref target="IANA-RC"/> registries.

	<list style="symbols">

	<t>
	In the listing of assigned code points the term "Vendor Private Use" is chang
	ed to
	"Private Use".
	</t>	</t>

		<ul spacing="normal">
	<t>	<li>
		In the listing of assigned code points, the term "Vendor Private Use" is chan
		ged to
		"Private Use" for the 252-255 range. The registration procedures have been u
		pdated to reflect this.
		</li>
		<li>
	The registration procedure "Specification Required" is changed to "RFC	The registration procedure "Specification Required" is changed to "RFC

	Required" and the note "Experimental RFC needed" is removed.	Required" and the note "Experimental RFC needed" is removed for the 192-247 r
	</t>	ange.
		</li>
	<t>	<li>
	A small set of code points (4 code points) for Experimental Use is	A small set of four code points (248-251) for Experimental Use is
	added by reducing the "RFC Required" range.	added by reducing the "RFC Required" range. The registration procedures hav
	</t>	e been updated to reflect this.
		</li>
	<t>
	The registration procedures "Private Use" and "Experimental Use" are added to
	the table of registration procedures.
	</t>

	<t>
	A note "Not to be assigned" is added for the registration procedures
	"Private Use" and "Experimental Use".
	</t>


	<t>	<li>
		A note "Reserved, not to be assigned" has been added for the registration proced
		ures of the
		"Private Use" and "Experimental Use" ranges.
		</li>
		<li>
		<t>
	In the lists that capture the assignment status, the fields that are reserved, i .e.,	In the lists that capture the assignment status, the fields that are reserved, i .e.,

	0 (zero), Private Use and Experimental Use are clearly marked as such.	0 (zero), Private Use, and Experimental Use, are clearly marked as such.
	<list style="symbols">
	<t>
	Note that in the Return Codes registry
	<xref target="IANA-RC"/> the code point "0"
	has already been assigned. This assignment is not changed and in this
	registry 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>	</t>

		<ul spacing="normal">
		<li>
		Note that in the "<xref target="IANA-RC" format="title"/>" registry
		<xref target="IANA-RC" format="default"/>, the code point "0"
		has already been assigned. This assignment is not changed, and in this
		registry, the code point "0" continues to be assigned as "No Return Code".


	<t>	</li>
	The new Registration Procedures, the registry layouts and the new assignments	</ul>
		</li>
		</ul>
		<t>
		The new registration procedures, the registry layouts, and the new assignments
	for these	for these

	registries are found in <xref target="app-messages"/>.	registries are found in <xref target="app-messages" format="default"/>.
	</t>	</t>


	</section>	</section>

		<section anchor="upd-tlv" numbered="true" toc="default">
	<section anchor="upd-tlv" title="Updating the TLV and Sub-TLV Registries">	<name>Updating the TLV and Sub-TLV Registries</name>
		<section anchor="principles" numbered="true" toc="default">
	<section anchor="principles" title="General Principles for the LSP Ping TLV and	<name>General Principles for the LSP Ping TLV and Sub-TLV Registries</na
	Sub-TLV registries">	me>
		<t>
	<t>
	The following principles apply to the processing of any TLV from any	The following principles apply to the processing of any TLV from any

	of the LSP Ping TLVs and sub-TLVs IANA registries.	of the LSP Ping TLV and sub-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	All TLVs and sub-TLVs with a type in the range 0-32767 require a response
	if they are not recognized.	if they are not recognized.

	</t>	</li>
		<li>
	<t>	All TLVs and sub-TLVs in the range 32768-65535 can be silently dropped if they a
	All TLVs and sub-TLVs in the range 32768-65535 may be silently dropped, stepped	re not recognized. Alternatively, the receiver may step over the unrecognized TL
	over or an error message sent if they	V or send an error message.
	are not recognized.	</li>
	</t>	</ul>
		<t>
	<!-- Amandas comment left in becasue 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"/>
	[Current Reference(s)] [This document]
	<vspace blankLines="0"/>
	Available Formats
	<vspace blankLines="0"/>
	CSV
	</t>
	</list>
	</t>


	</list>

	</t>

	<t>
	Each of the blocks has code point spaces with the following registration	Each of the blocks has code point spaces with the following registration
	procedures:	procedures:

	<list style="symbols">
	<t>
	Standards Action.
	</t>

	<t>
	RFC Required.
	</t>

	<t>
	Experimental Use.
	</t>	</t>

		<ul spacing="normal">
	<t>	<li>
	First Come First Served (FCFS).	Standards Action
	</t>	</li>
		<li>
	</list>	RFC Required
	</t>	</li>
		<li>
	<t>	Experimental Use
		</li>
		<li>
		First Come First Served (FCFS)
		</li>
		</ul>
		<t>
	The exact definitions of these procedures are found	The exact definitions of these procedures are found

	in <xref target="RFC8126"/>.	in <xref target="RFC8126" format="default"/>.
	</t>	</t>

		<section anchor="unrecog" numbered="true" toc="default">
	<section anchor="unrecog" title="Unrecognized Experimental Use TLVs and Sub-TLVs	<name>Unrecognized Experimental Use TLVs and Sub-TLVs</name>
	">	<t>
	<t>	Unrecognized TLVs and sub-TLVs in the Experimental Use and FCFS ranges are
	Unrecognized TLVs and sub-TLVs in the Experimental Use, and FCFS ranges are
	handled as any other unrecognized TLV or sub-TLV.	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	If the unrecognized TLV or sub-TLV is from the Experimental Use range
	(31740-31743)	(31740-31743)

	or from the FCFS range (31744-32767) a Return Code of 2	or from the FCFS range (31744-32767), a Return Code of 2
	("One or more of the TLVs was not understood") must be sent in the echo response .	("One or more of the TLVs was not understood") must be sent in the echo response .

	</t>	</li>
	<t>	<li>
	If the unrecognized TLV or sub-TLV is from the Experimental Use range	If a TLV or sub-TLV from the Experimental Use range
	(64508-64511) or from the FCFS range (64512-65535) the TLVs may be silently	(64508-64511) or from the FCFS range (64512-65535) is unrecognized, then the rec
	ignored, stepped	eiver can silently drop the TLV. Alternatively, the receiver may step over the u
	over or an error message sent.	nrecognized TLV or send an error message.
	</t>	</li>
		</ul>
	</list>	<t>

	</t>

	<t>
	The IETF does not prescribe how recognized or unrecognized Experimental Use	The IETF does not prescribe how recognized or unrecognized Experimental Use
	and Private Use TLVs and sub-TLVs are	and Private Use TLVs and sub-TLVs are
	handled in experimental or private networks; that is up to the agency running	handled in experimental or private networks; that is up to the agency running
	the experimental or the private network. The statement above describes how	the experimental or the private network. The statement above describes how

	standards	standards-compliant implementations must treat the unrecognized TLVs and sub-
	compliant implementations must treat the unrecognized TLVs and sub-TLVs	TLVs
	from these ranges.	from these ranges.

	</t>	</t>

		</section>
	</section>	</section>
		<section anchor="shared" numbered="true" toc="default">
	</section>	<name>Common Registration Procedures for TLVs and Sub-TLVs</name>
	<section anchor="shared" title="Common Registration Procedures for TLVs and sub	<t>
	-TLVs">
	<t>
	This section describes the new registration procedures for the TLV and sub-TLV	This section describes the new registration procedures for the TLV and sub-TLV
	registries.	registries.

	</t>	</t>
		<table anchor="tlv-sub-tlv" align="center">
	<texttable title="TLV and sub-TLV Registration Procedures" anchor="tlv-sub-tl	<name>TLV and Sub-TLV Registration Procedures</name>
	v">	<thead>
	<ttcol align='left' width="8%">Range</ttcol>	<tr>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<th align="left">Range</th>
	<ttcol align='left' width="69%">Note</ttcol>	<th align="left">Registration Procedures</th>
		<th align="left">Note</th>
	<c>0-16383</c>	</tr>
	<c>Standards Action</c>	</thead>
	<c>This range is for TLVs and sub-TLVs that require an error message if not	<tbody>
	recognized. [This document, section 3.1]</c>	<tr>
		<td align="left">0-16383</td>
	<c>16384-31739</c>	<td align="left">Standards Action</td>
	<c>RFC Required</c>	<td align="left">This range is for TLVs and sub-TLVs that require
	<c>This range is for TLVs and sub-TLVs that require an error message if not	an error message if not recognized. This document, <xref target="principles"/></
	recognized. [This document, section 3.1]</c>	td>
		</tr>
	<c>31740-31743</c>	<tr>
	<c>Experimental Use</c>	<td align="left">16384-31739</td>
	<c>Reserved, not to be assigned. This range is for TLVs and sub-TLVs that re	<td align="left">RFC Required</td>
	quire an error message if not recognized. [This document, section 3.1]</c>	<td align="left">This range is for TLVs and sub-TLVs that require
		an error message if not recognized. This document, <xref target="principles"/></
	<c>31744-32767</c>	td>
	<c>FCFS</c>	</tr>
	<c>This range is for TLVs and sub-TLVs that require an error message if not	<tr>
	recognized. [This document, section 3.1]</c>	<td align="left">31740-31743</td>
		<td align="left">Reserved for Experimental Use</td>
	<c>32768-49161</c>	<td align="left">Not to be assigned. This range is for TLVs and su
	<c>Standards Action</c>	b-TLVs that require an error message if not recognized. This document, <xref tar
	<c>This range is for TLVs and sub-TLVs that can be silently dropped if not r	get="principles"/></td>
	ecognized.</c>	</tr>
		<tr>
	<c>49162-64507</c>	<td align="left">31744-32767</td>
	<c>RFC Required</c>	<td align="left">FCFS</td>
	<c>This range is for TLVs and sub-TLVs that can be silently dropped if not r	<td align="left">This range is for TLVs and sub-TLVs that require
	ecognized.</c>	an error message if not recognized. This document, <xref target="principles"/></
		td>
	<c>64508-64511</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved, not to be assigned. This range is for TLVs and sub-TLVs that ca	<td align="left">32768-49161</td>
	n be silently dropped if not recognized.</c>	<td align="left">Standards Action</td>
		<td align="left">This range is for TLVs and sub-TLVs that can be s
	<c>64512-65535</c>	ilently dropped if not recognized.</td>
	<c>FCFS</c>	</tr>
	<c>This range is for TLVs and sub-TLVs that can be silently dropped if not r	<tr>
	ecognized.</c>	<td align="left">49162-64507</td>
		<td align="left">RFC Required</td>
	</texttable>	<td align="left">This range is for TLVs and sub-TLVs that can be s
		ilently dropped if not recognized.</td>
	</section>	</tr>
		<tr>
	<section anchor="general" title="Changes to the LSP Ping Registries">	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	<t>	<td align="left">Not to be assigned. This range is for TLVs and su
	This section lists the changes to each MPLS LSP Ping TLV and sub-TLV Registry.	b-TLVs that can be silently dropped if not recognized.</td>
	Section	</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 s
		ilently dropped if not recognized.</td>
		</tr>
		</tbody>
		</table>
		</section>
		<section anchor="general" numbered="true" toc="default">
		<name>Changes to the LSP Ping Registries</name>
		<t>
		This section lists the changes to each MPLS LSP Ping TLV and sub-TLV registry.
		Sections
	<xref target="upds-tlv" format="counter"/> to <xref target="upds-sub-tlv-27" for mat="counter"/>	<xref target="upds-tlv" format="counter"/> to <xref target="upds-sub-tlv-27" for mat="counter"/>
	describe how the new	describe how the new
	versions of the IANA registries should look, together with the	versions of the IANA registries should look, together with the
	registration procedures for each registry.	registration procedures for each registry.
	</t>	</t>

		<t>
	<t>	The new registration procedure descriptions and the new assignments for these
	The new Registration Procedures description and the new assignments for these	registries are used to model the changed MPLS LSP Ping registries; see
	registries are used to model the changed MPLS LSP Ping registries, see	<xref target="IANA" format="default"/>.
	<xref target="IANA"/>.
	</t>	</t>

		<section anchor="common-tlv" numbered="true" toc="default">
	<section anchor="common-tlv" title="Common Changes to the TLV and Sub-TLV Regist	<name>Changes Common to the TLV and Sub-TLV Registries</name>
	ries">	<t>

	<t>
	The following changes are made to the TLV and sub-TLV registries.	The following changes are made to the TLV and sub-TLV registries.


	<list style="symbols">
	<t>
	The registration procedures "First Come First Served (FCFS)" and
	"Experimental Use" are added to
	the table of registration procedures.
	</t>	</t>

		<ul spacing="normal">
	<t>	<li>
	Two small sets of code points (4 code points each) for Experimental Use, are	The registration procedures "First Come First Served" (FCFS) and
		"Experimental Use" have been added to
		the table of registration procedures.
		</li>
		<li>
		Two small sets of code points (four code points each) for Experimental Use have
		been
	created. The first set is for the range that requires a response if the TLV or	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-TLV is not recognized; the second set is for the range where the TLV or

	sub-TLV that may be silently dropped if not recognized. The code points for	sub-TLV may be silently dropped if not recognized. The code points for
	experimental use are taken from the ranges previously (RFC 8029) called	Experimental Use have been taken from the ranges previously called
	'Specification Required' and (RFC 8611) "RFC Required".	"Specification Required" and "RFC Required" <xref target="RFC8029"/>.
	</t>	</li>
		<li>
	<t>	The registration procedure "Specification Required" has been changed to "RFC
	The registration procedure "Specification Required" is changed to "RFC	Required", and the note "Experimental RFC needed" has been removed.
	Required" and the note "Experimental RFC needed" is removed.	</li>
	</t>	<li>
		In the listing of assignments, the term "Vendor Private Use" has been changed to
	<t>	"First Come First Served" (FCFS).
	In the listing of assignments the term "Vendor Private Use" is changed to	</li>
	"First Come First Served (FCFS)".	<li>
	</t>	In the listing of assignments, the range for "Experimental Use" has been added.
		</li>
	<t>
	In the listing of assignments the range for "Experimental Use" is added.
	</t>


	<t>	<li>
	A note saying "Not to be assigned" is added for the registration procedures	A note saying "Not to be assigned" has been added for the registration procedure
	"Experimental Use".	"Experimental Use".

	</t>	</li>
		<li>
	<t>
	In the list that captures assignment status, the fields that are reserved, i.e.,	In the list that captures assignment status, the fields that are reserved, i.e.,

	0 (zero) and Experimental Use are clearly marked.	0 (zero) and Experimental Use, have been clearly marked.
	</t>	</li>
		</ul>
	</list>	</section>
		</section>
	</t>	</section>
		<section anchor="text-updates" numbered="true" toc="default">
	</section>	<name>Updates to Related RFCs</name>
		<t>
	</section>

	</section>

	<section anchor="text-updates" title="Updates to Related RFCs">
	<t>
	Some referenced RFCs use the concept "mandatory TLVs" and "mandatory	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	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	in a message is not understood, an error message needs to be sent in
	response.	response.

	</t>	</t>
		<t>
	<t>
	The same RFCs use "optional TLVs" and "optional sub-TLVs" to mean TLVs or	The same RFCs use "optional TLVs" and "optional sub-TLVs" to mean TLVs or
	sub-TLVs that can be silently ignored if not recognized.	sub-TLVs that can be silently ignored if not recognized.

	</t>	</t>
		<t>
	<t>
	Since other RFCs use "mandatory TLVs" and "mandatory sub-TLVs" to	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	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	discontinue the use of "mandatory" to indicate TLVs and sub-TLVs that
	require	require
	an error message in response if not understood. The changes	an error message in response if not understood. The changes
	to the RFCs below align with this practice.	to the RFCs below align with this practice.

	</t>	</t>
	<section anchor="rfc8029" title="Updates to RFC 8029">	<section anchor="rfc8029" numbered="true" toc="default">
	<t>	<name>Updates to RFC 8029</name>
	Mandatory and optional are used to indicate whether a response is
	needed if a TLV or sub-TLV is not understood on pages 15 and 16 in
	Section 3 of RFC 8029.
	</t>
	<t>
	The text in those two paragraphs is now updated to the following:
	</t>


	<t>	<t>
		"Mandatory" and "optional" are used to indicate whether a response is
		needed if a TLV or sub-TLV is not understood in Section <xref target="RFC802
		9" sectionFormat="bare" section="3"/> of "<xref target="RFC8029" format="title"/
		>" <xref target="RFC8611" format="default"/>.


	<list style="empty">	</t>
	<t>	<t>
	TLV and sub-TLV Types less than 32768 (i.e., with the high-order	The text in those two paragraphs is now updated to the following:
	bit equal to 0) are TLVs and sub-TLVs that MUST either be	</t>
	supported by an implementation or result in the Return Code of 2	<blockquote><t>
		TLV and sub-TLV types less than 32768 (i.e., with the high-order
		bit equal to 0) are TLVs and sub-TLVs that <bcp14>MUST</bcp14> either be
		supported by an implementation or result in a Return Code of 2
	("One or more of the TLVs was not understood") being sent in the	("One or more of the TLVs was not understood") being sent in the

	echo response.	echo response. </t>
	</t>	<t>
	<t>
	An implementation that does not understand or support a received	An implementation that does not understand or support a received

	TLV or sub-TLV with Type greater than or equal to 32768 (i.e., with	TLV or sub-TLV with a type greater than or equal to 32768 (i.e., with
	the high-order bit equal to 1) SHOULD ignore and step over the TLV	the high-order bit equal to 1) <bcp14>SHOULD</bcp14> ignore and step over
	or sub-TLV, however an implementation MAY send an echo response	the TLV
	with Return Code 2 ("One or more of the TLVs was not understood") as it	or sub-TLV; however, an implementation <bcp14>MAY</bcp14> send an echo re
	would have done if the high order bit had been clear.	sponse
	</t>	with a Return Code of 2 ("One or more of the TLVs was not understood") as
		it
	</list>	would have done if the high-order bit had been clear.</t> </blockquote>
	</t>


	<t>	<t>
	In Section 3.8 of RFC 8029 "mandatory" is used in the same way. The	In <xref target="RFC8029" section="3.8"/>, "mandatory" is used in the same w
	<!-- here -->	ay. The first two paragraphs of this section are now updated to read as follows:
	first two paragraphs of this section are now updated to read as follows:	</t>
	<list style="empty">	<blockquote><t>
	<t>	The following TLV is a TLV that <bcp14>MAY</bcp14> be included in an echo r
	The following TLV is a TLV that MAY be included in an echo reply	eply
	to inform the sender of an echo request that includes TLVs or sub-	to inform the sender of an echo request that includes TLV or sub-TLV Types
	TLVs Types less than 32768 (i.e., with the high-order bit equal to	less than 32768 (i.e., with the high-order bit equal to
	0) that are either not supported by the implementation or parsed and	0) that are either not supported by the implementation or parsed and

	found to be in error.	found to be in error.</t>
	</t>	<t>
		The Value field uses sub-TLVs to encode the received TLVs and sub-TLVs that
	<t>	were not
	The Value field contains the TLVs, including sub-TLVs, that were not	understood.
	understood, encoded as sub-TLVs.
	</t>
	</list>
	</t>	</t>

		</blockquote>
	</section>	</section>
		<section anchor="rfc8611" numbered="true" toc="default">
	<section anchor="rfc8611" title="Updates to RFC 8611">	<name>Updates to RFC 8611</name>
	<t>	<t>
	Section 13.4.1 of "<xref target="RFC8611" format="title"/> <xref target="RFC8	Section <xref target="RFC8611" sectionFormat="bare" section="13.4.1"/> of "<x
	611"/>"	ref target="RFC8611" format="title"/>" <xref target="RFC8611" format="default"/>
	defines "<xref target="IANA-Sub-6" format="title" />" <xref target="IANA-Sub-	defines "<xref target="IANA-Sub-6" format="title"/>" <xref target="IANA-Sub-6"
	6"/>.	format="default"/>.
	</t>	</t>
		<t>
	<t>	The "<xref target="IANA-Sub-6" format="title"/>"
	The "Sub-TLVs for TLV Type 6"	registry has been updated to align with changes defined in this document.
	registry is now updated to align with changes defined in this document.	</t>
	</t>	<t>
	<t>	<xref target="RFC8611" section="13.4.1"/> is now updated as follows:
	Section 13.4.1 of RFC 8611 is now updated as follows:	</t>
	</t>	<blockquote><t>Section 13.4.1 Sub-TLVs for TLV Type 6</t></blockquote>
		<t>
	<t>	IANA has created a new subregistry, "<xref target="IANA-Sub-6" format="title"
	Section 13.4.1 Sub-TLVs for TLV Type 6	/>", <xref target="IANA-Sub-6" format="default"/>
	</t>	under the "<xref target="IANA-TLV-reg" format="title"/>" registry <xref targ
		et="IANA-TLV-reg" format="default"/>
	<t>
	IANA has created a new sub-registry "<xref target="IANA-Sub-6" format="title"
	/>" <xref target="IANA-Sub-6"/>
	under the "<xref target="IANA-TLV-reg" format="title"/>" registry <xref targ
	et="IANA-TLV-reg"/>
	of the "<xref target="lsp-ping-Namespace" format="title"/>" namespace	of the "<xref target="lsp-ping-Namespace" format="title"/>" namespace

	<xref target="lsp-ping-Namespace"/>.	<xref target="lsp-ping-Namespace" format="default"/>.
	</t>	</t>
		<t>
	<t>
	The "<xref target="IANA-Sub-6" format="title"/>"	The "<xref target="IANA-Sub-6" format="title"/>"

	sub-registry is now updated to align with changes defined in this document.	subregistry is now updated to align with changes defined in this document.
	</t>	</t>
	<texttable title="Sub-TLVs for TLV Type 6 Registration Procedures" anchor="s	<table anchor="sub-six-texttab" align="center">
	ub-six-texttab">	<name>Sub-TLVs for TLV Type 6 Registration Procedures</name>
	<ttcol align='left' width="8%">Range</ttcol>	<thead>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<tr>
	<ttcol align='left' width="69%">Note</ttcol>	<th align="left">Range</th>
	<c>0-16383</c>	<th align="left">Registration Procedures</th>
	<c>Standards Action</c>	<th align="left">Note</th>
	<c>This range is for sub-TLVs that require an error message if not recognize	</tr>
	d. [This document, section 3.1]</c>	</thead>
		<tbody>
	<c>16384-31739</c>	<tr>
	<c>RFC Required</c>	<td align="left">0-16383</td>
	<c>This range is for sub-TLVs that require an error message if not recognized. [	<td align="left">Standards Action</td>
	This document, section 3.1]</c>	<td align="left">This range is for sub-TLVs that require an error
		message if not recognized. This document, <xref target="principles"/></td>
	<c>31740-31743</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved not to be assigned. This range is for sub-TLVs that require an e	<td align="left">16384-31739</td>
	rror message if not recognized. [This document, section 3.1]</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that require an error
	<c>31744-32767</c>	message if not recognized. This document, <xref target="principles"/></td>
	<c>FCFS</c>	</tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<tr>
	d. [This document, section 3.1]</c>	<td align="left">31740-31743</td>
	<c>32768-49161</c>	<td align="left">Reserved for Experimental Use</td>
	<c>Standards Action</c>	<td align="left">Not to be assigned. This range is for sub-TLVs th
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	at require an error message if not recognized. This document, <xref target="prin
	.</c>	ciples"/></td>
		</tr>
	<c>49162-64507</c>	<tr>
	<c>RFC Required</c>	<td align="left">31744-32767</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">FCFS</td>
	.</c>	<td align="left">This range is for sub-TLVs that require an error
		message if not recognized. This document, <xref target="principles"/></td>
	<c>64508-64511</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved not to be assigned. This range is for sub-TLVs that can be silen	<td align="left">32768-49161</td>
	tly dropped if not recognized.</c>	<td align="left">Standards Action</td>
		<td align="left">This range is for sub-TLVs that can be silently d
	<c>64512-65535</c>	ropped if not recognized.</td>
	<c>FCFS</c>	</tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<tr>
	.</c>	<td align="left">49162-64507</td>
	</texttable>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that can be silently d
	</section>	ropped if not recognized.</td>
	</section>	</tr>
		<tr>
	<section anchor="security" title="Security Considerations">	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	<t>	<td align="left">Not to be assigned. This range is for sub-TLVs th
		at can be silently dropped if not recognized.</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 d
		ropped if not recognized.</td>
		</tr>
		</tbody>
		</table>
		</section>
		</section>
		<section anchor="security" numbered="true" toc="default">
		<name>Security Considerations</name>
		<t>
	This document updates IANA registries. It also updates terminology	This document updates IANA registries. It also updates terminology
	used to define, and	used to define, and
	clarifies the terminology related to, the	clarifies the terminology related to, the
	code points in the registries. The document does not change how the	code points in the registries. The document does not change how the

	code-points in the	code points in the
	registries are used. This should not create any new threats.	registries are used. This should not create any new threats.

	</t>	</t>
		<t>
	<t>
	However, the updated terminology and the clarifications	However, the updated terminology and the clarifications
	improve security because it makes it more likely that implementations	improve security because it makes it more likely that implementations
	will be consistent and harder to attack.	will be consistent and harder to attack.

	</t>	</t>

	</section>	</section>

		<section anchor="IANA" numbered="true" toc="default">
	<section anchor="IANA" title="IANA Considerations">	<name>IANA Considerations</name>
		<t>
	<t>	IANA has updated the
	IANA is requested to update the
	"<xref target="lsp-ping-Namespace" format="title"/>" namespace	"<xref target="lsp-ping-Namespace" format="title"/>" namespace

	<xref target="IANA-LSP-PING"/> as described in this	<xref target="IANA-LSP-PING" format="default"/> as described in this
	document.	document.

	</t>	</t>
		<t>
	<t>	See <xref target="local-terms" format="default"/> of "<xref target="local-te
	See <xref target="local-terms" /> "<xref target="local-terms" format="title"	rms" format="title"/>"
	/>"
	to see	to see

	how "namespace", "registry" and "sub-registry" are used in this document.	how "namespace", "registry", and "subregistry" are used in this document.
	</t>	</t>
		<t>
	<t>	In other parts of this document, the commonality of the changes to the LSP
	In other parts of this document the communality of the changes to the LSP	Ping registries has been the focus. For the IANA Considerations, each
	Ping registries has been the focus. For the IANA considerations each
	changed registry has been described in its own right.	changed registry has been described in its own right.

	</t>	</t>
	<t>	<t>
	The following registries and sub-registries are changed:	The following registries and subregistries have been changed:</t>
	<vspace blankLines="1"/>	<ul empty="false">
	"<xref target="IANA-MT" format="title"/>", <xref target="IANA-MT"/>,	<li>"<xref target="IANA-MT" format="title"/>", <xref target="IANA-MT" format="de
	<vspace blankLines="0"/>	fault"/></li>
	"<xref target="IANA-RM" format="title"/>", <xref target="IANA-RM"/>	<li>"<xref target="IANA-RM" format="title"/>", <xref target="IANA-RM" format="de
	<vspace blankLines="0"/>	fault"/></li>
	"<xref target="IANA-RC" format="title"/>" <xref target="IANA-RC"/>	<li>"<xref target="IANA-RC" format="title"/>", <xref target="IANA-RC" format="de
	<vspace blankLines="0"/>	fault"/></li>
	"<xref target="IANA-TLV-reg" format="title"/>" <xref target="IANA-TLV-reg"/>	<li>"<xref target="IANA-TLV-reg" format="title"/>", <xref target="IANA-TLV-reg"
	<vspace blankLines="0"/>	format="default"/></li>
	"<xref target="IANA-Sub-1-16-21" format="title" />" <xref target="IANA-Sub-1	<li>"<xref target="IANA-Sub-1-16-21" format="title"/>", <xref target="IANA-Sub-1
	-16-21"/>	-16-21" format="default"/></li>
	<vspace blankLines="0"/>	<li>"<xref target="IANA-Sub-6" format="title"/>", <xref target="IANA-Sub-6" form
	"<xref target="IANA-Sub-6" format="title" />" <xref target="IANA-Sub-6"/>	at="default"/></li>
	<vspace blankLines="0"/>	<li>"<xref target="IANA-Sub-11" format="title"/>", <xref target="IANA-Sub-11" fo
	"<xref target="IANA-Sub-11" format="title"/>" <xref target="IANA-Sub-11"/>	rmat="default"/></li>
	<vspace blankLines="0"/>	<li>"<xref target="IANA-Sub-20" format="title"/>", <xref target="IANA-Sub-20" fo
	"<xref target="IANA-Sub-20" format="title" />" <xref target="IANA-Sub-20"/>	rmat="default"/></li>
	<vspace blankLines="0"/>	<li>"<xref target="IANA-Sub-23" format="title"/>", <xref target="IANA-Sub-23" fo
	"<xref target="IANA-Sub-23" format="title"/>" <xref target="IANA-Sub-23"/>	rmat="default"/></li>
	<vspace blankLines="0"/>	<li>"<xref target="IANA-Sub-27" format="title"/>", <xref target="IANA-Sub-27" fo
	"<xref target="IANA-Sub-27" format="title"/>" <xref target="IANA-Sub-27"/>	rmat="default"/></li>
	</t>	</ul>
		<t>
	<t>	This document has been listed as an additional reference for each of the
	This document will be listed as an additional reference for each of the	registries described in Sections <xref target="app-messages" format="counter"/>
	registries described in Sections 6.1 and 6.2.	and <xref target="upd-tls-sub-tlv" format="counter"/>.
	</t>	</t>

		<section anchor="app-messages" numbered="true" toc="default">
	<section anchor="app-messages" title="Updates to the Message Type, Reply Mod	<name>Updates by IANA to the Message Types, Reply Modes, and Return Code
	e and Return Codes Registries">	s Registries</name>
		<t>
	<t>
	This section details the updated registration procedures and allocations	This section details the updated registration procedures and allocations

	for "Message Type", "Reply Mode" and "Return Codes" registries.	for the "<xref target="IANA-MT" format="title"/>", "<xref target="IANA-RM" for
	</t>	mat="title"/>", and "<xref target="IANA-RC" format="title"/>" registries.
		</t>
	<section anchor="mt-upd" title="Updates to the Message Type registry">	<section anchor="mt-upd" numbered="true" toc="default">
	<t>	<name>Updates to the Message Types Registry</name>
	This is the changes to the "Message Type" registry specified in this document:	<t>
	<list style="symbols">	These are the changes to the "<xref target="IANA-MT" format="title"/>" registr
	<t>	y specified in this document:
	Code Point 0 (zero) is marked Reserved.	</t>
	</t>	<ul spacing="normal">
	<t>	<li>
	The registration procedure "Specification Required" is changed to "RFC Require	Code Point 0 (zero) has been marked Reserved.
	d"	</li>
	and the comment "Experimental RFC needed" is removed.	<li>
	</t>	The registration procedure "Specification Required" has been changed to "RFC R
		equired",
	<t>	and the comment "Experimental RFC needed" has been removed.
	Four code point have been taken from what was earlier "Specification Required"	</li>
	to form a set of code points for "Experimental Use."	<li>
	</t>	Four code points have been taken from what was previously "Specification Requi
	</list>	red"
	</t>	to form a set of code points for "Experimental Use".
	<t>	</li>
	The registration procedures after the changes for the "Message Type" registry	</ul>
		<t>
		The registration procedures after the changes listed above for the "<xref targ
		et="IANA-MT" format="title"/>" registry
	are shown in the table below:	are shown in the table below:

	</t>	</t>
	<texttable title="Message Type registration procedures" anchor="mt-reg-proc-	<table anchor="mt-reg-proc-texttab" align="center">
	texttab">	<name>Message Types Registration Procedures</name>
	<ttcol align='left' width="8%">Range</ttcol>	<thead>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<tr>
	<ttcol align='left' width="69%">Note</ttcol>	<th align="left">Range</th>
	<c>0-191</c>	<th align="left">Registration Procedures</th>
	<c>Standards Action</c>	<th align="left">Note</th>
	<c></c>	</tr>
	<c>192-247</c>	</thead>
	<c>RFC Required</c>	<tbody>
	<c></c>	<tr>
	<c>248-251</c>	<td align="left">0-191</td>
	<c>Experimental Use</c>	<td align="left">Standards Action</td>
	<c>Reserved, not to be assigned</c>	<td align="left"/>
	<c>252-255</c>	</tr>
	<c>Private Use</c>	<tr>
	<c>Reserved, not to be assigned</c>	<td align="left">192-247</td>
		<td align="left">RFC Required</td>
	</texttable>	<td align="left"/>
		</tr>
	<t>	<tr>
	The updated assignments for the "Message Types" registry will look like this:	<td align="left">248-251</td>
		<td align="left">Experimental Use</td>
		<td align="left">Reserved, not to be assigned</td>
		</tr>
		<tr>
		<td align="left">252-255</td>
		<td align="left">Private Use</td>
		<td align="left">Reserved, not to be assigned</td>
		</tr>
		</tbody>
		</table>
		<t>
		The updated assignments for the "<xref target="IANA-MT" format="title"/>" regist
		ry appear as follows:
	</t>	</t>

		<table anchor="mt-texttab" align="center">
	<texttable title="Assignments for the Message Types registry" anchor="mt-texttab	<name>Assignments for the Message Types Registry</name>
	">	<thead>
	<ttcol align='left' width="8%">Value</ttcol>	<tr>
	<ttcol align='left' width="62%">Meaning</ttcol>	<th align="left">Value</th>
	<ttcol align='left' width="40%">Reference</ttcol>	<th align="left">Meaning</th>
	<c>0</c>	<th align="left">Reference</th>
	<c>Reserved</c>	</tr>
	<c>This document</c>	</thead>
	<c>1</c>	<tbody>
	<c>MPLS Echo Request</c>	<tr>
	<c> <xref target="RFC8029"/> </c>	<td align="left">0</td>
	<c>2</c>	<td align="left">Reserved</td>
	<c>MPLS Echo Reply</c>	<td align="left">This document</td>
	<c> <xref target="RFC8029"/> </c>	</tr>
	<c>3</c>	<tr>
	<c> MPLS Proxy Ping Request</c>	<td align="left">1</td>
	<c> <xref target="RFC7555"/> </c>	<td align="left">MPLS Echo Request</td>
	<c>4</c>	<td align="left">
	<c> MPLS Proxy Ping Reply</c>	<xref target="RFC8029" format="default"/> </td>
	<c> <xref target="RFC7555"/> </c>	</tr>
	<c>5</c>	<tr>
	<c> MPLS Relayed Echo Reply</c>	<td align="left">2</td>
	<c> <xref target="RFC7743"/> </c>	<td align="left">MPLS Echo Reply</td>
	<c>6-247</c>	<td align="left">
	<c>Unassigned</c>	<xref target="RFC8029" format="default"/> </td>
	<c> </c>	</tr>
	<c>248-251</c>	<tr>
	<c>Reserved for Experimental Use</c>	<td align="left">3</td>
	<c>This document</c>	<td align="left"> MPLS Proxy Ping Request</td>
	<c>252-255</c>	<td align="left">
	<c>Reserved for Private Use</c>	<xref target="RFC7555" format="default"/> </td>
	<c><xref target="RFC8029"/></c>	</tr>
	</texttable>	<tr>
		<td align="left">4</td>
	</section>	<td align="left"> MPLS Proxy Ping Reply</td>
		<td align="left">
	<section anchor="rm-upd" title="Updates to the Reply Modes registry">	<xref target="RFC7555" format="default"/> </td>
	<t>	</tr>
	This is the changes to the "Reply Modes" registry specified in this document:	<tr>
	<list style="symbols">	<td align="left">5</td>
	<t>	<td align="left"> MPLS Relayed Echo Reply</td>
	Code Point 0 (zero) is marked Reserved.	<td align="left">
	</t>	<xref target="RFC7743" format="default"/> </td>
	<t>	</tr>
	The registration procedure "Specification Required" is changed to "RFC Require	<tr>
	d"	<td align="left">6-247</td>
	and the comment "Experimental RFC needed" is removed.	<td align="left">Unassigned</td>
	</t>	<td align="left"> </td>
		</tr>
	<t>	<tr>
	Four code point have been taken from what was earlier "Specification Required"	<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 Private Use</td>
		<td align="left">
		<xref target="RFC8029" format="default"/></td>
		</tr>
		</tbody>
		</table>
		</section>
		<section anchor="rm-upd" numbered="true" toc="default">
		<name>Updates to the Reply Modes Registry</name>
		<t>
		These are the changes to the "<xref target="IANA-RM" format="title"/>" registr
		y specified in this document:
		</t>
		<ul spacing="normal">
		<li>
		Code Point 0 (zero) has been marked Reserved.
		</li>
		<li>
		The registration procedure "Specification Required" has been changed to "RFC R
		equired",
		and the comment "Experimental RFC needed" has been removed.
		</li>
		<li>
		Four code points have been taken from what was previously "Specification Requi
		red"
	to form a set of code points for "Experimental Use".	to form a set of code points for "Experimental Use".

	</t>	</li>
	</list>	</ul>
	</t>	<t>
	<t>	The registration procedures after the changes for the "<xref target="IANA-RM"
	The registration procedures after the changes for the "Reply Modes" registry	format="title"/>" registry
	are show in the table below:	are shown in the table below:
	</t>	</t>
	<texttable title="Reply Modes registration procedures" anchor="rm-reg-prov-t	<table anchor="rm-reg-prov-texttab" align="center">
	exttab">	<name>Reply Modes Registration Procedures</name>
	<ttcol align='left' width="8%">Range</ttcol>	<thead>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<tr>
	<ttcol align='left' width="69%">Note</ttcol>	<th align="left">Range</th>
	<c>0-191</c>	<th align="left">Registration Procedures</th>
	<c>Standards Action</c>	<th align="left">Note</th>
	<c></c>	</tr>
	<c>192-247</c>	</thead>
	<c>RFC Required</c>	<tbody>
	<c></c>	<tr>
	<c>248-251</c>	<td align="left">0-191</td>
	<c>Experimental Use</c>	<td align="left">Standards Action</td>
	<c>Reserved, not to be assigned</c>	<td align="left"/>
	<c>252-255</c>	</tr>
	<c>Private Use</c>	<tr>
	<c>Reserved, not to be assigned</c>	<td align="left">192-247</td>
		<td align="left">RFC Required</td>
	</texttable>	<td align="left"/>
		</tr>
	<t>	<tr>
	The updated assignments for the "Reply Modes" registry will look like this:	<td align="left">248-251</td>
		<td align="left">Experimental Use</td>
		<td align="left">Reserved, not to be assigned</td>
		</tr>
		<tr>
		<td align="left">252-255</td>
		<td align="left">Private Use</td>
		<td align="left">Reserved, not to be assigned</td>
		</tr>
		</tbody>
		</table>
		<t>
		The updated assignments for the "<xref target="IANA-RM" format="title"/>" regist
		ry are as follows:
	</t>	</t>

		<table anchor="rm-texttab" align="center">
	<texttable title="Assignments for the Reply Modes registry" anchor="rm-texttab">	<name>Assignments for the Reply Modes Registry</name>
	<ttcol align='left' width="8%">Value</ttcol>	<thead>
	<ttcol align='left' width="62%">Meaning</ttcol>	<tr>
	<ttcol align='left' width="40%">Reference</ttcol>	<th align="left">Value</th>
	<c>0</c>	<th align="left">Meaning</th>
	<c>Reserved</c>	<th align="left">Reference</th>
	<c>This document</c>	</tr>
	<c>1</c>	</thead>
	<c>Do not reply</c>	<tbody>
	<c> <xref target="RFC8029"/> </c>	<tr>
	<c>2</c>	<td align="left">0</td>
	<c>Reply via an IPv4/IPv6 UDP packet</c>	<td align="left">Reserved</td>
	<c> <xref target="RFC8029"/> </c>	<td align="left">This document</td>
	<c>3</c>	</tr>
	<c>Reply via an IPv4/IPv6 UDP packet with Router Alert</c>	<tr>
	<c> <xref target="RFC8029"/> </c>	<td align="left">1</td>
	<c>4</c>	<td align="left">Do not reply</td>
	<c> Reply via application-level control channel</c>	<td align="left">
	<c> <xref target="RFC8029"/> </c>	<xref target="RFC8029" format="default"/> </td>
	<c>5</c>	</tr>
	<c>Reply via Specified Path</c>	<tr>
	<c> <xref target="RFC7110"/> </c>	<td align="left">2</td>
	<c>6-247</c>	<td align="left">Reply via an IPv4/IPv6 UDP packet</td>
	<c>Unassigned</c>	<td align="left">
	<c> </c>	<xref target="RFC8029" format="default"/> </td>
	<c>248-251</c>	</tr>
	<c>Reserved for Experimental Use</c>	<tr>
	<c>This document</c>	<td align="left">3</td>
	<c>252-255</c>	<td align="left">Reply via an IPv4/IPv6 UDP packet with Router A
	<c>Reserved for Private Use</c>	lert</td>
	<c><xref target="RFC8029"/></c>	<td align="left">
	</texttable>	<xref target="RFC8029" format="default"/> </td>
		</tr>
	</section>	<tr>
		<td align="left">4</td>
	<section anchor="rc-upd" title="Updates to the Return Codes registry">	<td align="left"> Reply via application-level control chann
	<t>	el</td>
	These are the changes to the "Return Codes" registry specified in this	<td align="left">
		<xref target="RFC8029" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">5</td>
		<td align="left">Reply via Specified Path</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 Private Use</td>
		<td align="left">
		<xref target="RFC8029" format="default"/></td>
		</tr>
		</tbody>
		</table>
		</section>
		<section anchor="rc-upd" numbered="true" toc="default">
		<name>Updates to the Return Codes Registry</name>
		<t>
		These are the changes to the "<xref target="IANA-RC" format="title"/>" registr
		y specified in this
	document:	document:

	<list style="symbols">	</t>
		<ul spacing="normal">
	<t>	<li>
	The registration procedure "Specification Required" is changed to "RFC Require	The registration procedure "Specification Required" has been changed to "RFC R
	d"	equired",
	and the comment "Experimental RFC needed" is removed.	and the comment "Experimental RFC needed" has been removed.
	</t>	</li>
		<li>
	<t>	Four code points have been taken from what was previously "Specification Requi
	Four code point have been taken from what was earlier "Specification Required"	red"
	to form a set of code points for "Experimental Use".	to form a set of code points for "Experimental Use".

	</t>	</li>
	</list>	</ul>
	</t>	<t>
	<t>	The registration procedures after the changes for the "<xref target="IANA-RC"
	The registration procedures after the changes for the "Return Codes" registry	format="title"/>" registry
	are show in the table below:	are shown in the table below:
	</t>	</t>
	<texttable title="Return Codes registration procedures" anchor="rc-reg-proc-	<table anchor="rc-reg-proc-texttab" align="center">
	texttab">	<name>Return Codes Registration Procedures</name>
	<ttcol align='left' width="8%">Range</ttcol>	<thead>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<tr>
	<ttcol align='left' width="69%">Note</ttcol>	<th align="left">Range</th>
	<c>0-191</c>	<th align="left">Registration Procedures</th>
	<c>Standards Action</c>	<th align="left">Note</th>
	<c></c>	</tr>
	<c>192-247</c>	</thead>
	<c>RFC Required</c>	<tbody>
	<c></c>	<tr>
	<c>248-251</c>	<td align="left">0-191</td>
	<c>Experimental Use</c>	<td align="left">Standards Action</td>
	<c>Reserved, not to be assigned</c>	<td align="left"/>
	<c>252-255</c>	</tr>
	<c>Private Use</c>	<tr>
	<c>Reserved, not to be assigned</c>	<td align="left">192-247</td>
		<td align="left">RFC Required</td>
	</texttable>	<td align="left"/>
		</tr>
	<t>	<tr>
	The updated assignments for the "Return Codes" registry will look like this:	<td align="left">248-251</td>
	</t>	<td align="left">Experimental Use</td>
		<td align="left">Reserved, not to be assigned</td>
	<texttable title="Assignments for the Return Codes registry" anchor="rc-texttab"	</tr>
	>	<tr>
	<ttcol align='left' width="8%">Value</ttcol>	<td align="left">252-255</td>
	<ttcol align='left' width="62%">Meaning</ttcol>	<td align="left">Private Use</td>
	<ttcol align='left' width="40%">Reference</ttcol>	<td align="left">Reserved, not to be assigned</td>
		</tr>
	<c>0</c>	</tbody>
	<c>No Return Code</c>	</table>
	<c>This document</c>	<t>
		The updated assignments for the "<xref target="IANA-RC" format="title"/>" regist
	<c>1</c>	ry are as follows:
	<c>Malformed echo request received</c>	</t>
	<c> <xref target="RFC8029"/> </c>

	<c>2</c>
	<c>One or more of the TLVs was not understood</c>
	<c> <xref target="RFC8029"/> </c>

	<c>3</c>
	<c>Replying router is an egress for the FEC at stack-depth <RSC> </c>
	<c> <xref target="RFC8029"/> </c>

	<c>4</c>
	<c>Replying router has no mapping for the FEC at stack-depth <RSC> </c
	>
	<c> <xref target="RFC8029"/> </c>

	<c>5</c>
	<c>Downstream Mapping Mismatch (See [1])</c>
	<c> <xref target="RFC8029"/> </c>

	<c>6</c>
	<c>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 switched at stack-depth <RSC> </c>
	<c> <xref target="RFC8029"/> </c>

	<c>9</c>
	<c>Label switched but no MPLS forwarding at stack-depth <RSC> </c>
	<c> <xref target="RFC8029"/> </c>

	<c>10</c>
	<c>Mapping for this FEC is not the given label at stack-depth <RSC> </
	c>
	<c> <xref target="RFC8029"/> </c>

	<c>11</c>
	<c> No label entry at stack-depth <RSC> </c>
	<c> <xref target="RFC8029"/> </c>

	<c>12</c>
	<c>Protocol not associated with interface at FEC stack-depth <RSC> </c
	>
	<c> <xref target="RFC8029"/> </c>

	<c>13</c>
	<c>Premature termination of ping due to label stack shrinking to a single la
	bel</c>
	<c> <xref target="RFC8029"/> </c>

	<c>14</c>
	<c>See DDMAP TLV for meaning of Return Code and Return Subcode (See [2])</c>
	<c> <xref target="RFC8029"/> </c>

	<c>15</c>
	<c> Label switched with FEC change</c>
	<c> <xref target="RFC8029"/> </c>

	<c>16</c>
	<c>Proxy Ping not authorized</c>
	<c> <xref target="RFC7555"/> </c>

	<c>17</c>
	<c>Proxy Ping parameters need to be modified</c>
	<c> <xref target="RFC7555"/> </c>

	<c>18</c>
	<c>MPLS Echo Request could not be sent</c>
	<c> <xref target="RFC7555"/> </c>

	<c>19</c>
	<c>Replying router has FEC mapping for topmost FEC</c>
	<c> <xref target="RFC7555"/> </c>

	<c>20</c>
	<c>One or more TLVs not returned due to MTU size</c>
	<c> <xref target="RFC7743"/> </c>

	<c>21</c>
	<c>OAM Problem/Unsupported BFD Version</c>
	<c> <xref target="RFC7759"/> </c>

	<c>22</c>
	<c> OAM Problem/Unsupported BFD Encapsulation format</c>
	<c> <xref target="RFC7759"/> </c>

	<c>23</c>
	<c>OAM Problem/Unsupported BFD Authentication Type</c>
	<c> <xref target="RFC7759"/> </c>

	<c>24</c>
	<c>OAM Problem/Mismatch of BFD Authentication Key ID</c>
	<c> <xref target="RFC7759"/> </c>

	<c>25</c>
	<c>OAM Problem/Unsupported Timestamp Format</c>
	<c> <xref target="RFC7759"/> </c>

	<c>26</c>
	<c>OAM Problem/Unsupported Delay Mode</c>
	<c> <xref target="RFC7759"/> </c>

	<c>27</c>
	<c>OAM Problem/Unsupported Loss Mode</c>
	<c> <xref target="RFC7759"/> </c>

	<c>28</c>
	<c>OAM Problem/Delay variation unsupported</c>
	<c> <xref target="RFC7759"/> </c>

	<c>29</c>
	<c>OAM Problem/Dyadic mode unsupported</c>
	<c> <xref target="RFC7759"/> </c>

	<c>30</c>
	<c>OAM Problem/Loopback mode unsupported</c>
	<c> <xref target="RFC7759"/> </c>

	<c>31</c>
	<c> OAM Problem/Combined mode unsupported</c>
	<c> <xref target="RFC7759"/> </c>

	<c>32</c>
	<c> OAM Problem/Fault management signaling unsupported</c>
	<c> <xref target="RFC7759"/> </c>

	<c>33</c>
	<c>OAM Problem/Unable to create fault management association</c>
	<c> <xref target="RFC7759"/> </c>

	<c>34</c>
	<c> OAM Problem/PM Configuration Error</c>
	<c> <xref target="RFC7759"/> </c>

	<c>35</c>
	<c>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 for Private Use</c>
	<c><xref target="RFC8029"/></c>
	</texttable>

	<t>
	Note 1: Notes [1] and [2] for code points 5, 6 and 14 point to footnotes in the
	"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping
	Parameters" namespace. The footnotes are not changed by this document.
	</t>

	<t>
	Note 2: <RSC> stands for "Return Subcode" and is explained in section 3.1
	of
	RFC 8029 <xref target="RFC8029"/>.
	</t>

	</section>

	</section>

	<section anchor="upd-tls-sub-tlv" title="Updates to the TLV and Sub-TLV regist
	ries">

	<t>
	The updates to the TLV and the sub-TLV registries are mostly the same, however
	the <xref target="IANA-Sub-9" format="title"/> <xref target="IANA-Sub-9"/>
	have not been updated.
	</t>


	<t>	<table anchor="rc-texttab" align="center">
		<name>Assignments for the Return Codes Registry</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 Return Code</td>
		<td align="left"><xref target="RFC8029" format="default"/></td>
		</tr>
		<tr>
		<td align="left">1</td>
		<td align="left">Malformed echo request received</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 not understood</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 sta
		ck-depth <RSC> </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 s
		tack-depth <RSC> </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])</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])</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> </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> </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> </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>
		</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 s
		tack-depth <RSC> </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 stac
		k shrinking to a single label</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 Re
		turn Subcode (See [2])</td>
		<td align="left">
		<xref target="RFC8029" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">15</td>
		<td align="left"> Label switched with FEC change</td>
		<td align="left">
		<xref target="RFC8029" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">16</td>
		<td align="left">Proxy Ping not authorized</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 be modified</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 be sent</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 topmost FEC
		</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 MTU size</
		td>
		<td align="left">
		<xref target="RFC7743" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">21</td>
		<td align="left">OAM Problem/Unsupported BFD 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 Encapsulation
		format</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">23</td>
		<td align="left">OAM Problem/Unsupported BFD Authentication Type
		</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 Key
		ID</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">25</td>
		<td align="left">OAM Problem/Unsupported Timestamp Format</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">26</td>
		<td align="left">OAM Problem/Unsupported Delay Mode</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">27</td>
		<td align="left">OAM Problem/Unsupported Loss Mode</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">28</td>
		<td align="left">OAM Problem/Delay variation unsupported</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">29</td>
		<td align="left">OAM Problem/Dyadic mode unsupported</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">30</td>
		<td align="left">OAM Problem/Loopback mode unsupported</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">31</td>
		<td align="left"> OAM Problem/Combined mode 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 signaling un
		supported</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 management a
		ssociation</td>
		<td align="left">
		<xref target="RFC7759" format="default"/> </td>
		</tr>
		<tr>
		<td align="left">34</td>
		<td align="left"> OAM Problem/PM Configuration Error</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 </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 Private Use</td>
		<td align="left">
		<xref target="RFC8029" format="default"/></td>
		</tr>
		</tbody>
		</table>
		<dl>
		<dt>
		Note 1:</dt><dd> Notes [1] and [2] for code points 5, 6, and 14 point to footnot
		es in the
		"<xref target="IANA-LSP-PING" format="title"/>" namespace. The footnotes are not
		changed by this document.
		</dd>
		<dt>
		Note 2:</dt><dd> <RSC> stands for "Return Subcode" and is explained in <xr
		ef target="RFC8029" sectionFormat="of" section="3.1"/>.
		</dd></dl>
		</section>
		</section>
		<section anchor="upd-tls-sub-tlv" numbered="true" toc="default">
		<name>Updates to the TLV and Sub-TLV Registries</name>
		<t>
		The updates to the TLV and the sub-TLV registries are mostly the same; however
		,
		the "<xref target="IANA-Sub-9" format="title"/>" <xref target="IANA-Sub-9" for
		mat="default"/> registry has not been updated.
		</t>
		<t>
	Note that when a field in an assignment table says "EQ", it means that	Note that when a field in an assignment table says "EQ", it means that
	there is no change from the existing field in the	there is no change from the existing field in the
	"<xref target="lsp-ping-Namespace" format="title"/>" namespace	"<xref target="lsp-ping-Namespace" format="title"/>" namespace

	<xref target="IANA-LSP-PING"/>	<xref target="IANA-LSP-PING" format="default"/>.
		</t>
	</t>	<section anchor="upds-tlv" numbered="true" toc="default">
		<name>Updates to the TLVs Registry</name>
	<section anchor="upds-tlv" title="Updates to the TLVs registry">	<t>
	<t>
	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments
	for the "<xref target="IANA-TLV-reg" format="title"/>" registry	for the "<xref target="IANA-TLV-reg" format="title"/>" registry

	<xref target="IANA-TLV-reg"/> based on the new registration procedures.	<xref target="IANA-TLV-reg" format="default"/> that are based on them.
	</t>	</t>
		<t>
	<t>
	The registration procedures have been changed, as follows, for the	The registration procedures have been changed, as follows, for the
	"<xref target="IANA-TLV-reg" format="title"/>" registry.	"<xref target="IANA-TLV-reg" format="title"/>" registry.

	</t>	</t>
		<ul spacing="normal">
	<t>	<li>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required". The comment "Experimental RFC Required" has been removed.
	Note that when a field in an assignment table says "EQ", it means that	Note that when a field in an assignment table says "EQ", it means that
	there is no change from the existing field in the	there is no change from the existing field in the
	"<xref target="lsp-ping-Namespace" format="title"/>" namespace	"<xref target="lsp-ping-Namespace" format="title"/>" namespace

	<xref target="IANA-LSP-PING"/>.	<xref target="IANA-LSP-PING" format="default"/>.

	</t>

	<t>
	RFC 8611 was published after RFC 8126 and uses the new terminology,
	e.g. "Private Use". The code points registration procedure "Private Use"
	has been replaced by the "First Come, First Served" code point registration
	proceedure.
	</t>

	<t>
	Two small sets, 4 code points each, have been created for Experimental Use.
	</t>


	<t>	</li>
		<li>
		<xref target="RFC8611"/> was published after <xref target="RFC8126"/> and u
		ses the new terminology,
		e.g., "Private Use". The code points registration procedure "Private Use"
		has been replaced by the "First Come First Served" code point registration
		procedure.
		</li>
		<li>
		Two small sets, four code points each, have been created for Experimental Use.
		</li>
		<li>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.

	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a TLV is not recognized.	whether or not a response is required if a TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>

	</t>

	<t>
	The registration procedures for the "<xref target="IANA-TLV-reg" format="title "/>"	The registration procedures for the "<xref target="IANA-TLV-reg" format="title "/>"

	registry <xref target="IANA-TLV-reg"/> will now look like this:	registry <xref target="IANA-TLV-reg" format="default"/> after the changes list
	</t>	ed above are shown in the table below:
		</t>
	<texttable title="TLV Registration Procedures" anchor="tlv-reg-proc">	<table anchor="tlv-reg-proc" align="center">
	<ttcol align='left' width="8%">Range</ttcol>	<name>TLVs Registration Procedures</name>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<thead>
	<ttcol align='left' width="69%">Note</ttcol>	<tr>
	<c>0-16383</c>	<th align="left">Range</th>
	<c>Standards Action</c>	<th align="left">Registration Procedures</th>
	<c>This range is for TLVs that require an error message if not recognized.	<th align="left">Note</th>
	[This document, section 3.1]</c>	</tr>
		</thead>
	<c>16384-31739</c>	<tbody>
	<c>RFC Required</c>	<tr>
	<c>This range is for TLVs that require an error message if not recognized.	<td align="left">0-16383</td>
	[This document, section 3.1]</c>	<td align="left">Standards Action</td>
		<td align="left">This range is for TLVs that require an error me
	<c>31740-31743</c>	ssage if not recognized.
	<c>Experimental Use</c>	This document, <xref target="principles"/></td>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	</tr>
	error message if not recognized. [This document, section 3.1]</c>	<tr>
		<td align="left">16384-31739</td>
	<c>31744-32767</c>	<td align="left">RFC Required</td>
	<c>FCFS</c>	<td align="left">This range is for TLVs that require an error me
	<c>This range is for TLVs that require an error message if not recognized. [	ssage if not recognized.
	This document, section 3.1]</c>	This document, <xref target="principles"/></td>
		</tr>
	<c>32768-49161</c>	<tr>
	<c>Standards Action</c>	<td align="left">31740-31743</td>
	<c>This range is for TLVs that can be silently dropped if not recognized.</c	<td align="left">Reserved for Experimental Use</td>
	>	<td align="left">Not to be assigned. This range is for TLVs that
		require an error message if not recognized. This document, <xref target="princi
	<c>49162-64507</c>	ples"/></td>
	<c>RFC Required</c>	</tr>
	<c>This range is for TLVs that can be silently dropped if not recognized.</c	<tr>
	>	<td align="left">31744-32767</td>
		<td align="left">FCFS</td>
	<c>64508-64511</c>	<td align="left">This range is for TLVs that require an error me
	<c>Experimental Use</c>	ssage if not recognized. This document, <xref target="principles"/></td>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	</tr>
	dropped if not recognized.</c>	<tr>
		<td align="left">32768-49161</td>
	<c>64512-65535</c>	<td align="left">Standards Action</td>
	<c>FCFS</c>	<td align="left">This range is for TLVs that can be silently dro
	<c>This range is for TLVs that can be silently dropped if not recognized.</c	pped if not recognized.</td>
	>	</tr>
		<tr>
	</texttable>	<td align="left">49162-64507</td>
		<td align="left">RFC Required</td>
	<t>	<td align="left">This range is for TLVs that can be silently dro
	The <xref target="tlv-assign" format="title"/> will now look like this.	pped if not recognized.</td>
	</t>	</tr>
		<tr>
	<t>	<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 not recognized.</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 dro
		pped if not recognized.</td>
		</tr>
		</tbody>
		</table>
		<t>
		The updated assignments for this registry appear as follows:
		</t>
		<t>
	Note that when a field in an assignment table says "EQ", it means that	Note that when a field in an assignment table says "EQ", it means that

	there is no change from the existing field in the	there was no change from the existing field in the
	"<xref target="lsp-ping-Namespace" format="title"/>" namespace	"<xref target="lsp-ping-Namespace" format="title"/>" namespace

	<xref target="IANA-LSP-PING"/>	<xref 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 to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This 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 to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>Unassigned</c>
	<c></c>
	<c></c>

	</texttable>

	</section>


	<section anchor="upds-sub-tlv-1-16-21" title="Updates to the registry for Sub-	</t>
	TLVs for TLVs 1, 16 and 21">	<table anchor="tlv-assign" align="center">
	<t>	<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 for TLVs that
		require an error message if not recognized. This document, <xref target="princi
		ples"/></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 not 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" numbered="true" toc="default">
		<name>Updates to the Registry for Sub-TLVs for TLV Types 1, 16, and 21
		</name>
		<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-1-16-21" format="title" />"	for the "<xref target="IANA-Sub-1-16-21" format="title"/>"
	<xref target="IANA-Sub-1-16-21"/> sub-registry based on the new registration	<xref target="IANA-Sub-1-16-21" format="default"/> subregistry that are based
	procedures.	on them.
	</t>	</t>
		<ul spacing="normal">
	<t>	<li>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required", and the comment "Experimental RFC Required" has been removed.
	</t>	</li>
		<li>


	<t>
	The code points registration procedure "Vendor Private Use" has been removed	The code points registration procedure "Vendor Private Use" has been removed
	and replaced with "First	and replaced with "First

	Come, First Served" code points.	Come First Served" procedure.
	</t>	</li>
		<li>
	<t>	Two small sets, four code points each, have been created for Experimental Use.
	Two small sets, 4 code points each, have been created for Experimental Use.	</li>
	</t>	<li>

	<t>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-1-16-21" format="t
	</t>	itle"/>"
		<xref target="IANA-Sub-1-16-21" format="default"/> subregistry appear as follo
	<t>	ws after the changes listed above:
	The registration procedures for the "<xref target="IANA-Sub-1-16-21" format="t	</t>
	itle" />"	<table anchor="sub-tlv-1-16-21-reg-proc" align="center">
	<xref target="IANA-Sub-1-16-21"/> sub-registry will now look like this:	<name>Registration Procedures for Sub-TLVs for TLV Types 1, 16, and
	</t>	21</name>
		<thead>
	<texttable title="Registration Procedures for Sub-TLVs for TLVs 1, 16 and 21"	<tr>
	anchor="sub-tlv-1-16-21-reg-proc">	<th align="left">Range</th>
	<ttcol align='left' width="8%">Range</ttcol>	<th align="left">Registration Procedures</th>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	<th align="left">Note</th>
	<ttcol align='left' width="69%">Note</ttcol>	</tr>
	<c>0-16383</c>	</thead>
	<c>Standards Action</c>	<tbody>
	<c>This range is for sub-TLVs that require an error message if not recognize	<tr>
	d. [This document, section 3.1]</c>	<td align="left">0-16383</td>
		<td align="left">Standards Action</td>
	<c>16384-31739</c>	<td align="left">This range is for sub-TLVs that require an erro
	<c>RFC Required</c>	r message if not recognized. This document, <xref target="principles"/></td>
	<c>This range is for sub-TLVs that require an error message if not recognize	</tr>
	d. [This document, section 3.1]</c>	<tr>
		<td align="left">16384-31739</td>
	<c>31740-31743</c>	<td align="left">RFC Required</td>
	<c>Experimental Use</c>	<td align="left">This range is for sub-TLVs that require an erro
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	r message if not recognized. This document, <xref target="principles"/></td>
	error message if not recognized. [This document, section 3.1]</c>	</tr>
		<tr>
	<c>31744-32767</c>	<td align="left">31740-31743</td>
	<c>FCFS</c>	<td align="left">Reserved for Experimental Use</td>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">Not to be assigned. This range is for sub-TLVs
	d. [This document, section 3.1]</c>	that require an error message if not recognized. This document, <xref target="pr
		inciples"/></td>
	<c>32768-49161</c>	</tr>
	<c>Standards Action</c>	<tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">31744-32767</td>
	.</c>	<td align="left">FCFS</td>
		<td align="left">This range is for sub-TLVs that require an erro
	<c>49162-64507</c>	r message if not recognized. This document, <xref target="principles"/></td>
	<c>RFC Required</c>	</tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<tr>
	.</c>	<td align="left">32768-49161</td>
		<td align="left">Standards Action</td>
	<c>64508-64511</c>	<td align="left">This range is for sub-TLVs that can be silently
	<c>Experimental Use</c>	dropped if not recognized.</td>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	</tr>
	dropped if not recognized.</c>	<tr>
		<td align="left">49162-64507</td>
	<c>64512-65535</c>	<td align="left">RFC Required</td>
	<c>FCFS</c>	<td align="left">This range is for sub-TLVs that can be silently
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	dropped if not recognized.</td>
	.</c>	</tr>
		<tr>
	</texttable>	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	<texttable title="Sub-TLV for TLV 1, 16 and 21 Assignments" anchor="sub-tlv-	<td align="left">Not to be assigned. This range is for sub-TLVs
	1-16-21-assign">	that can be silently dropped if not recognized.</td>
	<ttcol align='left' width="8%">Type</ttcol>	</tr>
	<ttcol align='left' width="33%">TLV Name</ttcol>	<tr>
	<ttcol align='left' width="69%">Reference</ttcol>	<td align="left">64512-65535</td>
	<ttcol align='left' width="69%">Comment</ttcol>	<td align="left">FCFS</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>0</c>	dropped if not recognized.</td>
	<c>Reserved</c>	</tr>
	<c>This document</c>	</tbody>
	<c></c>	</table>

	<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, not to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This 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 to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>Unassigned</c>
	<c></c>
	<c></c>

	</texttable>

	</section>


	<!-- section 6.3.3 -->	<table anchor="sub-tlv-1-16-21-assign" align="center">
		<name>Sub-TLV for TLVs 1, 16, and 21 Assignments</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. This document, <xref target="pr
		inciples"/></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 for sub-TLVs
		that can be silently dropped if not 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-6" title="Updates to the registry for Sub-TLVs f	<section anchor="upds-sub-tlv-6" numbered="true" toc="default">
	or TLV 6">	<name>Updates to the Registry for Sub-TLVs for TLV Type 6</name>
	<t>	<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-6" format="title" />" <xref target="IANA-Sub-6	for the "<xref target="IANA-Sub-6" format="title"/>" <xref target="IANA-Sub-6"
	"/>	format="default"/>
	sub-registry based on the new registration	subregistry that are based on them.
	procedures.	</t>
	</t>	<ul spacing="normal">
		<li>
	<t>	<xref target="RFC8611"/> was published after <xref target="RFC8126"/> and u
	<list style="symbols">	ses the new terminology,
		e.g., "Private Use". The code points registration procedure "Private Use"
	<t>	has been replaced by the "First Come First Served" code point registration
	RFC 8611 was published after RFC 8126 and uses the new terminology,	procedure.
	e.g. "Private Use". The code points registration procedure "Private Use"	</li>
	has been replaced by the "First come, First Served" code point registration	<li>
	proceedure.	Two small sets, four code points each, have been created for Experimental Use.
	</t>	</li>
		<li>
	<t>
	Two small sets, 4 code points each, have been created for Experimental Use.
	</t>

	<t>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-6" format="title"/
	</t>	>"
		<xref target="IANA-Sub-6" format="default"/> subregistry after the changes lis
	<t>	ted above are shown in the table below:
	The registration procedures for the "<xref target="IANA-Sub-6" format="title"	</t>
	/>"	<table anchor="sub-tlv-6-reg-proc" align="center">
	<xref target="IANA-Sub-6"/> sub-registry will now look like this:	<name>Registration Procedures for Sub-TLVs for TLV Type 6</name>
	</t>	<thead>
		<tr>
	<texttable title="Registration Procedures for Sub-TLVs for TLVs 6" anchor="su	<th align="left">Range</th>
	b-tlv-6-reg-proc">	<th align="left">Registration Procedures</th>
	<ttcol align='left' width="8%">Range</ttcol>	<th align="left">Note</th>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	</tr>
	<ttcol align='left' width="69%">Note</ttcol>	</thead>
	<c>0-16383</c>	<tbody>
	<c>Standards Action</c>	<tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">0-16383</td>
	d. [This document, section 3.1]</c>	<td align="left">Standards Action</td>
		<td align="left">This range is for sub-TLVs that require an erro
	<c>16384-31739</c>	r message if not recognized. This document, <xref target="principles"/></td>
	<c>RFC Required</c>	</tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<tr>
	d. [This document, section 3.1]</c>	<td align="left">16384-31739</td>
		<td align="left">RFC Required</td>
	<c>31740-31743</c>	<td align="left">This range is for sub-TLVs that require an erro
	<c>Experimental Use</c>	r message if not recognized. This document, <xref target="principles"/></td>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	</tr>
	error message if not recognized. [This document, section 3.1]</c>	<tr>
		<td align="left">31740-31743</td>
	<c>31744-32767</c>	<td align="left">Reserved for Experimental Use</td>
	<c>FCFS</c>	<td align="left">Not to be assigned. This range is for sub-TLVs
	<c>This range is for sub-TLVs that require an error message if not recognize	that require an error message if not recognized. This document, <xref target="pr
	d. [This document, section 3.1]</c>	inciples"/></td>
		</tr>
	<c>32768-49161</c>	<tr>
	<c>Standards Action</c>	<td align="left">31744-32767</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">FCFS</td>
	.</c>	<td align="left">This range is for sub-TLVs that require an erro
		r message if not recognized. This document, <xref target="principles"/></td>
	<c>49162-64507</c>	</tr>
	<c>RFC Required</c>	<tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">32768-49161</td>
	.</c>	<td align="left">Standards Action</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>64508-64511</c>	dropped if not recognized.</td>
	<c>Experimental Use</c>	</tr>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<tr>
	dropped if not recognized.</c>	<td align="left">49162-64507</td>
		<td align="left">RFC Required</td>
	<c>64512-65535</c>	<td align="left">This range is for sub-TLVs that can be silently
	<c>FCFS</c>	dropped if not recognized.</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	</tr>
	.</c>	<tr>
		<td align="left">64508-64511</td>
	</texttable>	<td align="left">Reserved for Experimental Use</td>
		<td align="left">Not to be assigned. This range is for sub-TLVs
	<texttable title="Sub-TLVs for TLV 6 Assignments" anchor="sub-tlv-6-assign">	that can be silently dropped if not recognized.</td>
	<ttcol align='left' width="8%">Type</ttcol>	</tr>
	<ttcol align='left' width="33%">TLV Name</ttcol>	<tr>
	<ttcol align='left' width="69%">Reference</ttcol>	<td align="left">64512-65535</td>
	<ttcol align='left' width="69%">Comment</ttcol>	<td align="left">FCFS</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>0</c>	dropped if not recognized.</td>
	<c>Reserved</c>	</tr>
	<c>This document</c>	</tbody>
	<c></c>	</table>

	<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, not to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This 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 to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>Unassigned</c>
	<c></c>
	<c></c>

	</texttable>

	</section>

	<!-- section 6.3.4 -->


	<section anchor="upds-sub-tlv-11" title="Updates to the registry for Sub-TLVs	<table anchor="sub-tlv-6-assign" align="center">
	for TLV 11">	<name>Sub-TLVs for TLV Type 6 Assignments</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. This document, <xref target="pr
		inciples"/></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 for sub-TLVs
		that can be silently dropped if not 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>


	<t>	<section anchor="upds-sub-tlv-11" numbered="true" toc="default">
		<name>Updates to the Registry for Sub-TLVs for TLV Type 11</name>
		<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-11" format="title" />" <xref target="IANA-Sub-	for the "<xref target="IANA-Sub-11" format="title"/>" <xref target="IANA-Sub-1
	11"/>	1" format="default"/>
	sub-registry based on the new registration	subregistry that are based on them.
	procedures.	</t>
	</t>	<ul spacing="normal">
		<li>
	<t>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required", and the comment "Experimental RFC Required" has been removed.
	</t>	</li>
		<li>
	<t>
	The code points registration procedure "Vendor Private Use" has been removed	The code points registration procedure "Vendor Private Use" has been removed
	and replaced with "First	and replaced with "First

	Come, First Served" code points.	Come First Served" code points.
	</t>	</li>
		<li>
	<t>	Two small sets, four code points each, have been created for Experimental Use.
	Two small sets, 4 code points each, have been created for Experimental Use.	</li>
	</t>	<li>

	<t>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-11" format="title"
	</t>	/>"
		<xref target="IANA-Sub-11" format="default"/> subregistry after the changes li
	<t>	sted above are shown in the table below:
	The registration procedures for the "<xref target="IANA-Sub-11" format="title"	</t>
	/>"	<table anchor="sub-tlv-11-reg-proc" align="center">
	<xref target="IANA-Sub-11"/> sub-registry will now look like this:	<name>Registration Procedures for Sub-TLVs for TLV Type 11</name>
	</t>	<thead>
		<tr>
	<texttable title="Registration Procedures for Sub-TLVs for TLVs 11" anchor="s	<th align="left">Range</th>
	ub-tlv-11-reg-proc">	<th align="left">Registration Procedures</th>
	<ttcol align='left' width="8%">Range</ttcol>	<th align="left">Note</th>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	</tr>
	<ttcol align='left' width="69%">Note</ttcol>	</thead>
		<tbody>
	<c>0-16383</c>	<tr>
	<c>Standards Action</c>	<td align="left">0-16383</td>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">Standards Action</td>
	d. [This document, section 3.1]</c>	<td align="left">This range is for sub-TLVs that require an erro
		r message if not recognized. This document, <xref target="principles"/></td>
	<c>16384-31739</c>	</tr>
	<c>RFC Required</c>	<tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">16384-31739</td>
	d. [This document, section 3.1]</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that require an erro
	<c>31740-31743</c>	r message if not recognized. This document, <xref target="principles"/></td>
	<c>Experimental Use</c>	</tr>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	<tr>
	error message if not recognized. [This document, section 3.1]</c>	<td align="left">31740-31743</td>
		<td align="left">Reserved for Experimental Use</td>
	<c>31744-32767</c>	<td align="left">Not to be assigned. This range is for sub-TLVs
	<c>FCFS</c>	that require an error message if not recognized. This document, <xref target="pr
	<c>This range is for sub-TLVs that require an error message if not recognize	inciples"/></td>
	d. [This document, section 3.1]</c>	</tr>
		<tr>
	<c>32768-49161</c>	<td align="left">31744-32767</td>
	<c>Standards Action</c>	<td align="left">FCFS</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">This range is for sub-TLVs that require an erro
	.</c>	r message if not recognized. This document, <xref target="principles"/></td>
		</tr>
	<c>49162-64507</c>	<tr>
	<c>RFC Required</c>	<td align="left">32768-49161</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">Standards Action</td>
	.</c>	<td align="left">This range is for sub-TLVs that can be silently
		dropped if not recognized.</td>
	<c>64508-64511</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<td align="left">49162-64507</td>
	dropped if not recognized.</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>64512-65535</c>	dropped if not recognized.</td>
	<c>FCFS</c>	</tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<tr>
	.</c>	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	</texttable>	<td align="left">Not to be assigned. This range is for sub-TLVs
		that can be silently dropped if not recognized.</td>
	<texttable title="Sub-TLVs for TLV 11 Assignments" anchor="sub-tlv-11-assign	</tr>
	">	<tr>
	<ttcol align='left' width="8%">Type</ttcol>	<td align="left">64512-65535</td>
	<ttcol align='left' width="33%">TLV Name</ttcol>	<td align="left">FCFS</td>
	<ttcol align='left' width="69%">Reference</ttcol>	<td align="left">This range is for sub-TLVs that can be silently
	<ttcol align='left' width="69%">Comment</ttcol>	dropped if not recognized.</td>
		</tr>
	<c>0</c>	</tbody>
	<c>Reserved</c>	</table>
	<c>This document</c>	<table anchor="sub-tlv-11-assign" align="center">
	<c></c>	<name>Sub-TLVs for TLV Type 11 Assignments</name>
		<thead>
	<c>1-4</c>	<tr>
	<c>EQ</c>	<th align="left">Sub-Type</th>
	<c>EQ</c>	<th align="left">Sub-TLV Name</th>
	<c>EQ</c>	<th align="left">Reference</th>
		<th align="left">Comment</th>
	<c>5-31739</c>	</tr>
	<c>Unassigned</c>	</thead>
	<c></c>	<tbody>
	<c></c>	<tr>
		<td align="left">0</td>
	<c>31740-31743</c>	<td align="left">Reserved</td>
	<c>Experimental Use</c>	<td align="left">This document</td>
	<c>This Document</c>	<td align="left"/>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	</tr>
	error message if not recognized. [This document, section 3.1]</c>	<tr>
		<td align="left">1-4</td>
	<c>31744-64507</c>	<td align="left">EQ</td>
	<c>Unassigned</c>	<td align="left">EQ</td>
	<c></c>	<td align="left">EQ</td>
	<c></c>	</tr>
		<tr>
	<c>64508-64511</c>	<td align="left">5-31739</td>
	<c>Experimental Use</c>	<td align="left">Unassigned</td>
	<c>This document</c>	<td align="left"/>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<td align="left"/>
	dropped if not recognized.</c>	</tr>
		<tr>
	<c>64512-65535</c>	<td align="left">31740-31743</td>
	<c>Unassigned</c>	<td align="left">Reserved for Experimental Use</td>
	<c></c>	<td align="left">This document</td>
	<c></c>	<td align="left">Not to be assigned. This range is for sub-TLVs
		that require an error message if not recognized. This document, <xref target="pr
	</texttable>	inciples"/></td>
	</section>	</tr>
		<tr>
	<section anchor="upds-sub-tlv-20" title="Updates to the registry for Sub-TLVs	<td align="left">31744-64507</td>
	for TLV 20">	<td align="left">Unassigned</td>
		<td align="left"/>
	<t>	<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 for sub-TLVs
		that can be silently dropped if not 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" numbered="true" toc="default">
		<name>Updates to the Registry for Sub-TLVs for TLV Type 20</name>
		<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-20" format="title" />" <xref target="IANA-Sub-	for the "<xref target="IANA-Sub-20" format="title"/>" <xref target="IANA-Sub-2
	20"/>	0" format="default"/>
	sub-registry based on the new registration	subregistry that are based on them.
	procedures.	</t>
	</t>	<ul spacing="normal">
		<li>
	<t>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required", and the comment "Experimental RFC Required" has been removed.
	</t>	</li>
		<li>
	<t>
	The code points registration procedure "Vendor Private Use" has been removed	The code points registration procedure "Vendor Private Use" has been removed
	and replaced with "First	and replaced with "First

	Come, First Served" code points.	Come First Served" code points.
	</t>	</li>

	<t>
	Two small sets, 4 code ve been created for Experimental Use.
	</t>


	<t>	<li>
		Two small sets, four code points each, have been created for Experimental Use.
		</li>
		<li>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-20" format="title"
	</t>	/>"
		<xref target="IANA-Sub-20" format="default"/> subregistry after the changes li
	<t>	sted above are shown in the table below:
	The registration procedures for the "<xref target="IANA-Sub-20" format="title"	</t>
	/>"	<table anchor="sub-tlv-20-reg-proc" align="center">
	<xref target="IANA-Sub-20"/> sub-registry will now look like this:	<name>Registration Procedures for Sub-TLVs for TLV Type 20</name>
	</t>	<thead>
		<tr>
	<texttable title="Registration Procedures for Sub-TLVs for TLVs 20" anchor="s	<th align="left">Range</th>
	ub-tlv-20-reg-proc">	<th align="left">Registration Procedures</th>
	<ttcol align='left' width="8%">Range</ttcol>	<th align="left">Note</th>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	</tr>
	<ttcol align='left' width="69%">Note</ttcol>	</thead>
		<tbody>
	<c>0-16383</c>	<tr>
	<c>Standards Action</c>	<td align="left">0-16383</td>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">Standards Action</td>
	d. [This document, section 3.1]</c>	<td align="left">This range is for sub-TLVs that require an erro
		r message if not recognized. This document, <xref target="principles"/>]</td>
	<c>16384-31739</c>	</tr>
	<c>RFC Required</c>	<tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">16384-31739</td>
	d. [This document, section 3.1]</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that require an erro
	<c>31740-31743</c>	r message if not recognized. This document, <xref target="principles"/>]</td>
	<c>Experimental Use</c>	</tr>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	<tr>
	error message if not recognized. [This document, section 3.1]</c>	<td align="left">31740-31743</td>
		<td align="left">Reserved for Experimental Use</td>
	<c>31744-32767</c>	<td align="left">Not to be assigned. This range is for sub-TLVs
	<c>FCFS</c>	that require an error message if not recognized. This document, <xref target="pr
	<c>This range is for sub-TLVs that require an error message if not recognize	inciples"/>]</td>
	d. [This document, section 3.1]</c>	</tr>
		<tr>
	<c>32768-49161</c>	<td align="left">31744-32767</td>
	<c>Standards Action</c>	<td align="left">FCFS</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">This range is for sub-TLVs that require an erro
	.</c>	r message if not recognized. This document, <xref target="principles"/>]</td>
		</tr>
	<c>49162-64507</c>	<tr>
	<c>RFC Required</c>	<td align="left">32768-49161</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">Standards Action</td>
	.</c>	<td align="left">This range is for sub-TLVs that can be silently
		dropped if not recognized.</td>
	<c>64508-64511</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<td align="left">49162-64507</td>
	dropped if not recognized.</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>64512-65535</c>	dropped if not recognized.</td>
	<c>FCFS</c>	</tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<tr>
	.</c>	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	</texttable>	<td align="left">Not to be assigned. This range is for sub-TLVs
		that can be silently dropped if not recognized.</td>
	<texttable title="Sub-TLVs for TLV 20 Assignments" anchor="sub-tlv-20-assign	</tr>
	">	<tr>
	<ttcol align='left' width="8%">Type</ttcol>	<td align="left">64512-65535</td>
	<ttcol align='left' width="33%">TLV Name</ttcol>	<td align="left">FCFS</td>
	<ttcol align='left' width="69%">Reference</ttcol>	<td align="left">This range is for sub-TLVs that can be silently
	<ttcol align='left' width="69%">Comment</ttcol>	dropped if not recognized.</td>
		</tr>
	<c>0</c>	</tbody>
	<c>Reserved</c>	</table>
	<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, not to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This 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 to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>Unassigned</c>
	<c></c>
	<c></c>

	</texttable>
	</section>

	<section anchor="upds-sub-tlv-23" title="Updates to the registry for Sub-TLVs
	for TLV 23">


	<t>	<table anchor="sub-tlv-20-assign" align="center">
		<name>Sub-TLVs for TLV Type 20 Assignments</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. This document, <xref target="pr
		inciples"/>]</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 for sub-TLVs
		that can be silently dropped if not 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" numbered="true" toc="default">
		<name>Updates to the Registry for Sub-TLVs for TLV Type 23</name>
		<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-23" format="title" />" <xref target="IANA-Sub-	for the "<xref target="IANA-Sub-23" format="title"/>" <xref target="IANA-Sub-2
	23"/>	3" format="default"/>
	sub-registry based on the new registration	subregistry that are based on them.
	procedures.	</t>
	</t>	<ul spacing="normal">
		<li>
	<t>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required", and the comment "Experimental RFC Required" has been removed.
	</t>	</li>
		<li>
	<t>
	The code points registration procedure "Vendor Private Use" has been removed	The code points registration procedure "Vendor Private Use" has been removed
	and replaced with "First	and replaced with "First

	Come, First Served" code points.	Come First Served" code points.
	</t>	</li>
		<li>
	<t>	Two small sets, four code points each, have been created for Experimental Use.
	Two small sets, 4 code points each, have been created for Experimental Use.	</li>
	</t>	<li>

	<t>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-23" format="title"
	</t>	/>"
		<xref target="IANA-Sub-23" format="default"/> subregistry after the changes li
	<t>	sted above are shown in the table below:
	The registration procedures for the "<xref target="IANA-Sub-23" format="title"	</t>
	/>"	<table anchor="sub-tlv-23-reg-proc" align="center">
	<xref target="IANA-Sub-23"/> sub-registry will now look like this:	<name>Registration Procedures for Sub-TLVs for TLV Type 23</name>
	</t>	<thead>
		<tr>
	<texttable title="Registration Procedures for Sub-TLVs for TLVs 23" anchor="s	<th align="left">Range</th>
	ub-tlv-23-reg-proc">	<th align="left">Registration Procedures</th>
	<ttcol align='left' width="8%">Range</ttcol>	<th align="left">Note</th>
	<ttcol align='left' width="33%">Registration Procedures</ttcol>	</tr>
	<ttcol align='left' width="69%">Note</ttcol>	</thead>
		<tbody>
	<c>0-16383</c>	<tr>
	<c>Standards Action</c>	<td align="left">0-16383</td>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">Standards Action</td>
	d. [This document, section 3.1]</c>	<td align="left">This range is for sub-TLVs that require an erro
		r message if not recognized. This document, <xref target="principles"/>]</td>
	<c>16384-31739</c>	</tr>
	<c>RFC Required</c>	<tr>
	<c>This range is for sub-TLVs that require an error message if not recognize	<td align="left">16384-31739</td>
	d. [This document, section 3.1]</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that require an erro
	<c>31740-31743</c>	r message if not recognized. This document, <xref target="principles"/>]</td>
	<c>Experimental Use</c>	</tr>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	<tr>
	error message if not recognized. [This document, section 3.1]</c>	<td align="left">31740-31743</td>
		<td align="left">Reserved for Experimental Use</td>
	<c>31744-32767</c>	<td align="left">Not to be assigned. This range is for sub-TLVs
	<c>FCFS</c>	that require an error message if not recognized. This document, <xref target="pr
	<c>This range is for sub-TLVs that require an error message if not recognize	inciples"/>]</td>
	d. [This document, section 3.1]</c>	</tr>
		<tr>
	<c>32768-49161</c>	<td align="left">31744-32767</td>
	<c>Standards Action</c>	<td align="left">FCFS</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">This range is for sub-TLVs that require an erro
	.</c>	r message if not recognized. This document, <xref target="principles"/>]</td>
		</tr>
	<c>49162-64507</c>	<tr>
	<c>RFC Required</c>	<td align="left">32768-49161</td>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<td align="left">Standards Action</td>
	.</c>	<td align="left">This range is for sub-TLVs that can be silently
		dropped if not recognized.</td>
	<c>64508-64511</c>	</tr>
	<c>Experimental Use</c>	<tr>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<td align="left">49162-64507</td>
	dropped if not recognized.</c>	<td align="left">RFC Required</td>
		<td align="left">This range is for sub-TLVs that can be silently
	<c>64512-65535</c>	dropped if not recognized.</td>
	<c>FCFS</c>	</tr>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized	<tr>
	.</c>	<td align="left">64508-64511</td>
		<td align="left">Reserved for Experimental Use</td>
	</texttable>	<td align="left">Not to be assigned. This range is for sub-TLVs
		that can be silently dropped if not recognized.</td>
	<texttable title="Sub-TLVs for TLV 23 Assignments" anchor="sub-tlv-23-assign	</tr>
	">	<tr>
	<ttcol align='left' width="8%">Type</ttcol>	<td align="left">64512-65535</td>
	<ttcol align='left' width="33%">TLV Name</ttcol>	<td align="left">FCFS</td>
	<ttcol align='left' width="69%">Reference</ttcol>	<td align="left">This range is for sub-TLVs that can be silently
	<ttcol align='left' width="69%">Comment</ttcol>	dropped if not recognized.</td>
		</tr>
	<c>0</c>	</tbody>
	<c>Reserved</c>	</table>
	<c><xref target="RFC7555"/></c>	<table anchor="sub-tlv-23-assign" align="center">
	<c></c>	<name>Sub-TLVs for TLV Type 23 Assignments</name>
		<thead>
	<c>1</c>	<tr>
	<c>EQ</c>	<th align="left">Sub-Type</th>
	<c>EQ</c>	<th align="left">Sub-TLV Name</th>
	<c>EQ</c>	<th align="left">Reference</th>
		<th align="left">Comment</th>
	<c>2-31739</c>	</tr>
	<c>Unassigned</c>	</thead>
	<c></c>	<tbody>
	<c></c>	<tr>
		<td align="left">0</td>
	<c>31740-31743</c>	<td align="left">Reserved</td>
	<c>Experimental Use</c>	<td align="left">
	<c>This Document</c>	<xref target="RFC7555" format="default"/></td>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an	<td align="left"/>
	error message if not recognized. [This document, section 3.1]</c>	</tr>
		<tr>
	<c>31744-64507</c>	<td align="left">1</td>
	<c>Unassigned</c>	<td align="left">EQ</td>
	<c></c>	<td align="left">EQ</td>
	<c></c>	<td align="left">EQ</td>
		</tr>
	<c>64508-64511</c>	<tr>
	<c>Experimental Use</c>	<td align="left">2-31739</td>
	<c>This document</c>	<td align="left">Unassigned</td>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently	<td align="left"/>
	dropped if not recognized.</c>	<td align="left"/>
		</tr>
	<c>64512-65535</c>	<tr>
	<c>Unassigned</c>	<td align="left">31740-31743</td>
	<c></c>	<td align="left">Reserved for Experimental Use</td>
	<c></c>	<td align="left">This document</td>
		<td align="left">Not to be assigned. This range is for sub-TLVs
	</texttable>	that require an error message if not recognized. This document, <xref target="pr
	</section>	inciples"/>]</td>
		</tr>
	<section anchor="upds-sub-tlv-27" title="Updates to the registry for Sub-TLVs	<tr>
	for TLV 27">	<td align="left">31744-64507</td>
		<td align="left">Unassigned</td>
	<t>	<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 for sub-TLVs
		that can be silently dropped if not 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" numbered="true" toc="default">
		<name>Updates to the Registry for Sub-TLVs for TLV Type 27</name>
		<t>

	This section describes the new registration procedures and the assignments	This section describes the new registration procedures and the assignments

	for the "<xref target="IANA-Sub-27" format="title" />" <xref target="IANA-Sub-	for the "<xref target="IANA-Sub-27" format="title"/>" <xref target="IANA-Sub-2
	27"/>	7" format="default"/>
	sub-registry based on the new registration	subregistry that are based on them.
	procedures.	</t>
	</t>	<ul spacing="normal">
		<li>
	<t>
	<list style="symbols">
	<t>
	The "Specification Required" registration procedure has been changed to "RFC	The "Specification Required" registration procedure has been changed to "RFC

	Required", the comment "Experimental RFC Required" has been removed.	Required", and the comment "Experimental RFC Required" has been removed.
	</t>	</li>
		<li>
	<t>
	The code points registration procedure "Vendor Private Use" has been removed	The code points registration procedure "Vendor Private Use" has been removed
	and replaced with "First	and replaced with "First

	Come, First Served" code points.	Come First Served" code points.
	</t>	</li>
		<li>
	<t>	Two small sets, four code points each, have been created for Experimental Use.
	Two small sets, 4 code points each, have been created for Experimental Use.	</li>
	</t>	<li>

	<t>
	Code points that are reserved are clearly marked as such.	Code points that are reserved are clearly marked as such.

	</t>	</li>
		<li>
	<t>
	The assignments have been updated to match the new registration procedures.	The assignments have been updated to match the new registration procedures.


	</t>	</li>
		<li>
	<t>
	The notes related to the registration procedures have been changed to reflect	The notes related to the registration procedures have been changed to reflect

	whether a response is required or not if a sub-TLV is not recognized.	whether or not a response is required if a sub-TLV is not recognized.
	</t>	</li>
		</ul>
	</list>	<t>
		The registration procedures for the "<xref target="IANA-Sub-27" format="title"
	</t>	/>"
		<xref target="IANA-Sub-27" format="default"/> subregistry after the changes li
	<t>	sted above are shown in the table below:
	The registration procedures for the "<xref target="IANA-Sub-27" format="title"
	/>"
	<xref target="IANA-Sub-27"/> sub-registry will now look like this:
	</t>

	<texttable title="Registration Procedures for Sub-TLVs for TLV 27" anchor="su
	b-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>This range is for sub-TLVs that require an error message if not recognize
	d. [This document, section 3.1]</c>

	<c>16384-31739</c>
	<c>RFC Required</c>
	<c>This range is for sub-TLVs that require an error message if not recognize
	d. [This document, section 3.1]</c>

	<c>31740-31743</c>
	<c>Experimental Use</c>
	<c>Reserved, not to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This document, section 3.1]</c>

	<c>31744-32767</c>
	<c>FCFS</c>
	<c>This range is for sub-TLVs that require an error message if not recognize
	d. [This document, section 3.1]</c>

	<c>32768-49161</c>
	<c>Standards Action</c>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized
	.</c>

	<c>49162-64507</c>
	<c>RFC Required</c>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized
	.</c>

	<c>64508-64511</c>
	<c>Experimental Use</c>
	<c>Reserved, not to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>FCFS</c>
	<c>This range is for sub-TLVs that can be silently dropped if not recognized
	.</c>

	</texttable>

	<texttable title="Sub-TLVs for TLV 27 Assignments" 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, not to be assigned. This range is for sub-TLVs that require an
	error message if not recognized. [This 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 to be assigned. This range is for TLVs that can be silently
	dropped if not recognized.</c>

	<c>64512-65535</c>
	<c>Unassigned</c>
	<c></c>
	<c></c>

	</texttable>
	</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>	</t>
	The authors thanks Donald Eastlake and Tom Petch for careful and detailed	<table anchor="sub-tlv-27-reg-proc" align="center">
	reviews.	<name>Registration Procedures for Sub-TLVs for TLV Type 27</name>
	</t>	<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 erro
		r message if not recognized. This document, <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 erro
		r message if not recognized. This document, <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. This document, <xref target="pr
		inciples"/>]</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 erro
		r message if not recognized. This document, <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 not recognized.</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 not 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 for
		sub-TLVs that can be silently dropped if not recognized.</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 not recognized.</td>
		</tr>
		</tbody>
		</table>


		<table anchor="sub-tlv-27-assign" align="center">
		<name>Sub-TLVs for TLV Type 27 Assignments</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. This document, <xref target="pr
		inciples"/>]</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 for sub-TLVs
		that can be silently dropped if not 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>


	</middle>	</middle>


	<back>	<back>

		<references>
		<name>References</name>
		<references>
		<name>Normative References</name>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.2119.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8029.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8126.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8174.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8611.xml"/>


	<references title="Normative References">	<reference anchor="IANA-LSP-PING" target="https://www.iana.org/assignmen
		ts/mpls-lsp-ping-parameters">
	<?rfc include="reference.RFC.2119"?>	<front>
	<?rfc include="reference.RFC.8029"?>	<title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LS
	<?rfc include="reference.RFC.8126"?>	Ps) Ping Parameters</title>
	<?rfc include="reference.RFC.8174"?>	<author/>
	<?rfc include="reference.RFC.8611"?>	<date/>
	<reference anchor="IANA-LSP-PING" target="https://www.iana.org/assignments	</front>
	/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml/">	</reference>
	<front>
	<title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Pi
	ng Parameters</title>
	<author/>
	<date/>
	</front>
	</reference>

	<reference anchor="IANA-MT" target="https://www.iana.org/assignments/mpls-l
	sp-ping-parameters/mpls-lsp-ping-parameters.xhtml#message-types">
	<front>
	<title>Message Types</title>
	<author/>
	<date/>
	</front>
	</reference>


	<reference anchor="IANA-RM" target="https://www.iana.org/assignments/mpls-l	<reference anchor="IANA-MT" target="https://www.iana.org/assignments/mpl
	sp-ping-parameters/#reply-modes">	s-lsp-ping-parameters/">
	<front>	<front>
	<title>Reply Modes</title>	<title>Message Types</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-RC" target="https://www.iana.org/assignments/mpls-	<reference anchor="IANA-RM" target="https://www.iana.org/assignments/mpl
	lsp-ping-parameters/#return-codes">	s-lsp-ping-parameters/">
	<front>	<front>
	<title>Return Codes</title>	<title>Reply Modes</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-TLV-reg" target="https://www.iana.org/assignments/	<reference anchor="IANA-RC" target="https://www.iana.org/assignments/mpl
	mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#tlvs">	s-lsp-ping-parameters/">
	<front>	<front>
	<title>TLVs</title>	<title>Return Codes</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-1-16-21" target="https://www.iana.org/assignme	<reference anchor="IANA-TLV-reg" target="https://www.iana.org/assignment
	nts/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-1-16-21">	s/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Types 1, 16, and 21</title>	<title>TLVs</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-6" target="https://www.iana.org/assignments/mp	<reference anchor="IANA-Sub-1-16-21" target="https://www.iana.org/assign
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-6">	ments/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Type 6</title>	<title>Sub-TLVs for TLV Types 1, 16, and 21</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-11" target="https://www.iana.org/assignments/mp	<reference anchor="IANA-Sub-6" target="https://www.iana.org/assignments/
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-11">	mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Type 11</title>	<title>Sub-TLVs for TLV Type 6</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-20" target="https://www.iana.org/assignments/mp	<reference anchor="IANA-Sub-11" target="https://www.iana.org/assignments
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-20">	/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Type 20</title>	<title>Sub-TLVs for TLV Type 11</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-23" target="https://www.iana.org/assignments/mp	<reference anchor="IANA-Sub-20" target="https://www.iana.org/assignments
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-23">	/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Type 23</title>	<title>Sub-TLVs for TLV Type 20</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


	<reference anchor="IANA-Sub-27" target="https://www.iana.org/assignments/mp	<reference anchor="IANA-Sub-23" target="https://www.iana.org/assignments
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-27">	/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Sub-TLVs for TLV Type 27</title>	<title>Sub-TLVs for TLV Type 23</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>


		<reference anchor="IANA-Sub-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>

		<references>
		<name>Informative References</name>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7110.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7555.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7743.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.7759.xml"/>
		<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
		FC.8287.xml"/>


	<references title="Informative References">	<reference anchor="IANA-Sub-9" target="https://www.iana.org/assignments/
	<!--	mpls-lsp-ping-parameters/">
	<?rfc include="reference.RFC.7759"?>	<front>
	-->	<title>Sub-TLVs for TLV Type 9</title>
	<?rfc include="reference.RFC.7110"?>	<author/>
	<?rfc include="reference.RFC.7555"?>	<date/>
	<?rfc include="reference.RFC.7743"?>	</front>
	<?rfc include="reference.RFC.7759"?>	</reference>
	<?rfc include="reference.RFC.8287"?>

	<reference anchor="IANA-Sub-9" target="https://www.iana.org/assignments/mp
	ls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-9">
	<front>
	<title>Sub-TLVs for TLV Type 9</title>
	<author/>
	<date/>
	</front>
	</reference>


	<reference anchor="lsp-ping-Namespace" target="https://www.iana.org/assign	<reference anchor="lsp-ping-Namespace" target="https://www.iana.org/assi
	ments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml">	gnments/mpls-lsp-ping-parameters/">
	<front>	<front>
	<title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Pi	<title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LS
	ng Parameters</title>	Ps) Ping Parameters</title>
	<author/>	<author/>
	<date/>	<date/>
	</front>	</front>
	</reference>	</reference>
		</references>
	</references>	</references>

		<section anchor="Acknowledgements" numbered="false" toc="default">
		<name>Acknowledgements</name>
		<t>
		The authors wish to thank <contact fullname="Adrian Farrel"/>, who both mad
		e very useful
		comments and agreed to serve as the Document Shepherd.
		</t>
		<t>
		The authors also wish to thank <contact fullname="Michelle Cotton"/> and <co
		ntact 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 ful
		lname="Tom Petch"/> for their careful and detailed
		review.
		</t>
		</section>
	</back>	</back>
	</rfc>	</rfc>

End of changes. 198 change blocks.
	2363 lines changed or deleted	2588 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/