rfc9041.original		rfc9041.txt
	MPLS Working Group L. Andersson		Internet Engineering Task Force (IETF) L. Andersson
	Internet-Draft Bronze Dragon Consulting		Request for Comments: 9041 Bronze Dragon Consulting
	Updates: 8029, 8611 (if approved) M. Chen		Updates: 8029, 8611 M. Chen
	Intended status: Standards Track Huawei Technologies		Category: Standards Track Huawei Technologies
	Expires: September 1, 2021 C. Pignataro		ISSN: 2070-1721 C. Pignataro
	Cisco Systems		Cisco Systems
	T. Saad		T. Saad
	Juniper Networks		Juniper Networks
	February 28, 2021		July 2021
	Updating the IANA MPLS LSP Ping Parameters		Updating the MPLS Label Switched Paths (LSPs) Ping Parameters IANA
	draft-ietf-mpls-lsp-ping-registries-update-11		Registry
	Abstract		Abstract
	This document updates RFC 8029 and RFC 8611 which both define IANA		This document updates RFCs 8029 and 8611, both of which define IANA
	registries for MPLS Label Switched Path (LSP) Ping, in particular the		registries for MPLS Label Switched Path (LSP) Ping. In particular,
	registration procedure "Private Use" (esarlier know as "Vendor		the registration procedure "Private Use" (previously known as "Vendor
	Private Use") is changed to "First Come, First Served" the TLV and		Private Use") has been changed to "First Come First Served" for the
	Sub-TLV Registries.		TLV and sub-TLV registries.
	It also updates the description of the procedures for the responses		It also updates the description of the procedures for the responses
	sent when an unknown or erroneous code point is found. The updates		sent when an unknown or erroneous code point is found. The updates
	are to clarify and align this namespace with recent developments,		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
	Section in RFCs" (e.g. RFC 8126), instead of the terminology from		RFC 5226 (both titled "Guidelines for Writing an IANA Considerations
	the obsoleted RFC 5226.		Section in RFCs").
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This is an Internet Standards Track document.
	provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		This document is a product of the Internet Engineering Task Force
	and may be updated, replaced, or obsoleted by other documents at any		(IETF). It represents the consensus of the IETF community. It has
	time. It is inappropriate to use Internet-Drafts as reference		received public review and has been approved for publication by the
	material or to cite them other than as "work in progress."		Internet Engineering Steering Group (IESG). Further information on
			Internet Standards is available in Section 2 of RFC 7841.
	This Internet-Draft will expire on September 1, 2021.		Information about the current status of this document, any errata,
			and how to provide feedback on it may be obtained at
			https://www.rfc-editor.org/info/rfc9041.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction
	1.1. Requirement Language . . . . . . . . . . . . . . . . . . 5		1.1. Requirements Language
	1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5		1.2. Terminology
	1.2.1. Terminology Used in this Document . . . . . . . . . . 5		1.2.1. Terminology Used in This Document
	1.2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . 5		1.2.2. Abbreviations
	2. Updating the Message Types, Reply Mode and Return Codes		2. Updating the Message Types, Reply Modes, and Return Codes
	Registries . . . . . . . . . . . . . . . . . . . . . . . . . 6		Registries
	3. Updating the TLV and Sub-TLV Registries . . . . . . . . . . . 6		3. Updating the TLV and Sub-TLV Registries
	3.1. General Principles for the LSP Ping TLV and Sub-TLV		3.1. General Principles for the LSP Ping TLV and Sub-TLV
	registries . . . . . . . . . . . . . . . . . . . . . . . 7		Registries
	3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs . . . 7		3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs
	3.2. Common Registration Procedures for TLVs and sub-TLVs . . 8		3.2. Common Registration Procedures for TLVs and Sub-TLVs
	3.3. Changes to the LSP Ping Registries . . . . . . . . . . . 8		3.3. Changes to the LSP Ping Registries
	3.3.1. Common Changes to the TLV and Sub-TLV Registries . . 9		3.3.1. Changes Common to the TLV and Sub-TLV Registries
	4. Updates to Related RFCs . . . . . . . . . . . . . . . . . . . 9		4. Updates to Related RFCs
	4.1. Updates to RFC 8029 . . . . . . . . . . . . . . . . . . . 10		4.1. Updates to RFC 8029
	4.2. Updates to RFC 8611 . . . . . . . . . . . . . . . . . . . 10		4.2. Updates to RFC 8611
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 12		5. Security Considerations
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		6. IANA Considerations
	6.1. Updates to the Message Type, Reply Mode and Return Codes		6.1. Updates by IANA to the Message Types, Reply Modes, and
	Registries . . . . . . . . . . . . . . . . . . . . . . . 13		Return Codes Registries
	6.1.1. Updates to the Message Type registry . . . . . . . . 13		6.1.1. Updates to the Message Types Registry
	6.1.2. Updates to the Reply Modes registry . . . . . . . . . 14		6.1.2. Updates to the Reply Modes Registry
	6.1.3. Updates to the Return Codes registry . . . . . . . . 16		6.1.3. Updates to the Return Codes Registry
	6.2. Updates to the TLV and Sub-TLV registries . . . . . . . . 18		6.2. Updates to the TLV and Sub-TLV Registries
	6.2.1. Updates to the TLVs registry . . . . . . . . . . . . 18		6.2.1. Updates to the TLVs Registry
	6.2.2. Updates to the registry for Sub-TLVs for TLVs 1, 16		6.2.2. Updates to the Registry for Sub-TLVs for TLV Types 1,
	and 21 . . . . . . . . . . . . . . . . . . . . . . . 21		16, and 21
	6.2.3. Updates to the registry for Sub-TLVs for TLV 6 . . . 24		6.2.3. Updates to the Registry for Sub-TLVs for TLV Type 6
	6.2.4. Updates to the registry for Sub-TLVs for TLV 11 . . . 27		6.2.4. Updates to the Registry for Sub-TLVs for TLV Type 11
	6.2.5. Updates to the registry for Sub-TLVs for TLV 20 . . . 29		6.2.5. Updates to the Registry for Sub-TLVs for TLV Type 20
	6.2.6. Updates to the registry for Sub-TLVs for TLV 23 . . . 31		6.2.6. Updates to the Registry for Sub-TLVs for TLV Type 23
	6.2.7. Updates to the registry for Sub-TLVs for TLV 27 . . . 33		6.2.7. Updates to the Registry for Sub-TLVs for TLV Type 27
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35		7. References
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36		7.1. Normative References
	8.1. Normative References . . . . . . . . . . . . . . . . . . 36		7.2. Informative References
	8.2. Informative References . . . . . . . . . . . . . . . . . 37		Acknowledgements
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38		Authors' Addresses
	1. Introduction		1. Introduction
	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.,
	o When the LSP Ping registry was created it was incorrectly assumed		* When the LSP Ping registry was created, it was incorrectly assumed
	that code points allocated by Experimental RFCs would be		that code points allocated by Experimental RFCs would be
	'experimental' code points; a code point made available in a		"experimental" code points; a code point made available in a
	public IANA registry is not limited by the type of RFC that made		public IANA registry is not limited by the type of RFC that made
	the allocation but is available for any document.		the allocation: it is available for use in any type of document.
	o The number of 'experimental' code points was also too large, as		* The number of "experimental" code points was also too large as
	compared to what is normally allocated for "Experimental Use".		compared to what is normally allocated for "Experimental Use".
	o RFC 8029 uses the words "mandatory" and "optional" differently to		* The words "mandatory" and "optional" are used differently in
	how other RFC do. RFC 8029 for example talks about mandatory TLVs		[RFC8029] than in other RFCs. For example, [RFC8029] talks about
	to indicate that it is mandatory to take a certain action if the		mandatory TLVs to indicate that it is mandatory to take a certain
	TLV is found in a message but not recognized, other RFCs uses		action if the TLV is found in a message but is not recognized.
	"mandatory TLV" to indicate a TLV that must be present in a		Other RFCs use "mandatory TLV" to indicate a TLV that must be
	message.		present in a message.
	Over time there have been attempts to administratively update some of		Over time, there have been attempts to administratively update some
	the registries, but it was soon decided that an RFC was needed.		of the registries, but it was soon decided that an RFC was needed.
	Other, often minor, potential updates were found, e.g. reserving the		Other, often 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.
	When RFC 8029 [RFC8029] was published it contained updates to the		[RFC8029] contains updates to the "Multiprotocol Label Switching
	"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)		(MPLS) Label Switched Paths (LSPs) Ping Parameters" IANA namespace
	Ping Parameters" IANA namespace [IANA-LSP-PING].		[IANA-LSP-PING].
	RFC 8611 [RFC8611] created LSP Ping IANA registries that match RFC		[RFC8611] created LSP Ping IANA registries that match [RFC8126].
	8126. This document further clarifies the entries in those		This document further clarifies the entries in those registries and
	registries and makes the definitions more precise.		makes the definitions more precise.
	This document updates RFC 8029 [RFC8029] and RFC 8611 [RFC8611] by		This document updates [RFC8029] and [RFC8611] by updating two groups
	updating two groups of registries as follows:		of registries as follows:
	First the registries for Message Types [IANA-MT], Reply Modes		First, the "Message Types" [IANA-MT], "Reply Modes" [IANA-RM], and
	[IANA-RM] and Return Codes [IANA-RC] are updated. The changes to		"Return Codes" [IANA-RC] registries are updated. The changes to
	these registries are minor.		these registries are minor.
	Second, this document updates the TLV and sub-TLV registries.		Second, this document updates the TLV and sub-TLV registries listed
			below:
	o TLVs [IANA-TLV-reg].		* "TLVs", [IANA-TLV-reg]
	o Sub-TLVs for TLVs 1, 16 and 21 [IANA-Sub-1-16-21].		* "Sub-TLVs for TLV Types 1, 16, and 21", [IANA-Sub-1-16-21]
	o Sub-TLVs for TLV Type 6 [IANA-Sub-6].		* "Sub-TLVs for TLV Type 6", [IANA-Sub-6]
	o Sub-TLVs for TLV 11 [IANA-Sub-11].		* "Sub-TLVs for TLV Type 11", [IANA-Sub-11]
	o Sub-TLVs for TLV 20 [IANA-Sub-20].		* "Sub-TLVs for TLV Type 20", [IANA-Sub-20]
	o Sub-TLVs for TLV 23 [IANA-Sub-23].		* "Sub-TLVs for TLV Type 23", [IANA-Sub-23]
	o Sub-TLVs for TLV 27 [IANA-Sub-27].		* "Sub-TLVs for TLV Type 27", [IANA-Sub-27]
	It should be noted that RFC 8029 was published before RFC 8126 and		It should be noted that [RFC8029] was published before [RFC8126] and
	uses old terminology for some registration procedures, e.g., "Vendor		uses outdated terminology for some registration procedures, e.g.,
	Private Use". RFC 8611 was published after RFC 8126 and uses newer		"Vendor Private Use". [RFC8611] was published after [RFC8126] and
	terminology, e.g., "Private Use". Both "Vendor Private Use" and		uses its recommended terminology, e.g., "Private Use". However, now
	"Private Use" has been removed and replaced with "First come, first		both "Vendor Private Use" and "Private Use" have been removed and
	served (FCFS) code points.		replaced with "First Come First Served" (FCFS) code points.
	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		networks. Theoretically, it is possible that two vendors might use
	the same code point value with different meanings. If such code is		the same code point value with different meanings. If such a code is
	ever deployed in the same network this could cause protocol issues		ever deployed in the same network, this could cause protocol issues
	that would be hard to debug.		that would be hard to debug.
	With FCFS code points this will not happen. Vendors that have		With FCFS code points, this will not happen. Vendors that have
	existing code using Vendor Private Use or Private Use code points		existing code using Vendor Private Use or Private Use code points
	should register those code points as FSFC code points soon as this		should register those code points as FCFS code points as soon as this
	document is published as an RFC.		document is published as an RFC.
	The registry for sub-TLVs for TLV 9 [IANA-Sub-9] is not updated.		The "Sub-TLVs for TLV Type 9" subregistry is not updated.
	Third, according to RFC 8029 some code points (TLVs and sub-TLVs) are		Third, according to [RFC8029], some code points (TLVs and sub-TLVs)
	called "mandatory" or "optional". Contrary to how other RFCs use		are called "mandatory" or "optional". Contrary to how other RFCs use
	these words, indicating that it is mandatory or optional to include		these words, indicating that it is mandatory or optional to include
	the code points in a message, RFC 8029 uses these words to indicate		the code points in a message, [RFC8029] uses these words to indicate
	that an action might or might not be mandatory. This document		that an action might or might not be mandatory. This document
	updates RFC 8029 to drop the words "mandatory" and "optional", and		updates [RFC8029] to drop the words "mandatory" and "optional", and
	the text is changed to focus on what should be done.		the text is changed to focus on what should be done.
	1.1. Requirement Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	1.2. Terminology		1.2. Terminology
	This section list terms that are used when discussing the hierarchy		This section lists terms that are used when discussing the hierarchy
	of IANA registers (Section 1.2.1) and abbreviations used in IANA		of IANA registries (Section 1.2.1), and abbreviations used in IANA
	registries update in this document (Section 1.2.2).		registries are updated in this document (Section 1.2.2).
	1.2.1. Terminology Used in this Document		1.2.1. Terminology Used in This Document
	This document uses some terms that relates to IANA registries in this		Terms related to IANA registries are used as follows in this
	way:		document:
	IANA Name Space,		Namespace
	a namespace is a top level registry. An example could be		A namespace is a top-level registry. An example could be
	"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)		"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
	Ping Parameters" [IANA-LSP-PING]. A namespace is most often a		Ping Parameters" [IANA-LSP-PING]. A namespace is most often a
	container for registries that hold code points that share some		container for registries that hold code points that share some
	affinity.		affinity.
	IANA Registry,		Registry
	an IANA registry holds code points, and lists the registration		An IANA registry holds code points and lists the registration
	procedures and allocation these code points. One example would be		procedures and allocation for these code points. One example
	the "TLVs" registry [IANA-TLV-reg].		would be the "TLVs" registry [IANA-TLV-reg].
	IANA Sub-registry,		Subregistry
	a sub-registry is used when a code point, or a set of code points		A subregistry is used when a code point, or a set of code points
	allocated in a single registry, needs "sub-code points" scoped by		allocated in a single registry, needs "sub-code-points" scoped by
	the code point or the set of code points. An example of a sub-		the code point or the set of code points. An example of a
	registry that holds code points for more than one TLV is		subregistry that holds code points for more than one TLV is
	"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21]		"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21].
	1.2.2. Abbreviations		1.2.2. Abbreviations
	This section list abbreviations used in the unchanged part of the		This section lists abbreviations used in the unchanged part of the
	registries updated by this document. These abbreviations were		registries updated by this document. These abbreviations were
	originally expanded in the document defining the registries. They		originally expanded in the document defining the registries. They
	are listed here following the requirement to expand any abbreviation		are listed here following the requirement to expand any abbreviation
	that is not well-known. All these abbreviations are from the		that is not well known. All these abbreviations are from the "Return
	Return Codes registry [IANA-RC].		Codes" registry [IANA-RC].
	BFD - Bidirectional Forwarding Detection		BFD: Bidirectional Forwarding Detection
	DDMAP - Downstream Detailed Mapping
	FEC - Forwarding Equivalence Class		DDMAP: Downstream Detailed Mapping
	OAM - Operation, Administration and Maintenance		FEC: Forwarding Equivalence Class
	PM - Performance Monitoring		OAM: Operation, Administration, and Maintenance
	RSC - Return Subcode		PM: Performance Monitoring
	2. Updating the Message Types, Reply Mode and Return Codes Registries		RSC: Return Subcode
	The following changes are made to the Message Types [IANA-MT], Reply		2. Updating the Message Types, Reply Modes, and Return Codes Registries
	Modes [IANA-RM] and Return Codes [IANA-RC] registries.
	o In the listing of assigned code points the term "Vendor Private		The following changes have been made to the "Message Types"
	Use" is changed to "Private Use".		[IANA-MT], "Reply Modes" [IANA-RM], and "Return Codes" [IANA-RC]
			registries.
	o The registration procedure "Specification Required" is changed to		* In the listing of assigned code points, the term "Vendor Private
	"RFC Required" and the note "Experimental RFC needed" is removed.		Use" is changed to "Private Use" for the 252-255 range. The
			registration procedures have been updated to reflect this.
	o A small set of code points (4 code points) for Experimental Use is		* The registration procedure "Specification Required" is changed to
	added by reducing the "RFC Required" range.		"RFC Required" and the note "Experimental RFC needed" is removed
			for the 192-247 range.
	o The registration procedures "Private Use" and "Experimental Use"		* A small set of four code points (248-251) for Experimental Use is
	are added to the table of registration procedures.		added by reducing the "RFC Required" range. The registration
			procedures have been updated to reflect this.
	o A note "Not to be assigned" is added for the registration		* A note "Reserved, not to be assigned" has been added for the
	procedures "Private Use" and "Experimental Use".		registration procedures of the "Private Use" and "Experimental
			Use" ranges.
	o In the lists that capture the assignment status, the fields that		* In the lists that capture the assignment status, the fields that
	are reserved, i.e., 0 (zero), Private Use and Experimental Use are		are reserved, i.e., 0 (zero), Private Use, and Experimental Use,
	clearly marked as such.		are clearly marked as such.
	* Note that in the Return Codes registry [IANA-RC] the code point		- Note that in the "Return Codes" registry [IANA-RC], the code
	"0" has already been assigned. This assignment is not changed		point "0" has already been assigned. This assignment is not
	and in this registry the code point "0" continues to be		changed, and in this registry, the code point "0" continues to
	assigned as "No Return Code".		be assigned as "No Return Code".
	The new Registration Procedures, the registry layouts and the new		The new registration procedures, the registry layouts, and the new
	assignments for these registries are found in Section 6.1.		assignments for these registries are found in Section 6.1.
	3. Updating the TLV and Sub-TLV Registries		3. Updating the TLV and Sub-TLV Registries
	3.1. General Principles for the LSP Ping TLV and Sub-TLV registries
			3.1. General Principles for the LSP Ping TLV and Sub-TLV Registries
	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.
	o All TLVs and sub-TLVs with a type in the range 0-32767 require a		* All TLVs and sub-TLVs with a type in the range 0-32767 require a
	response if they are not recognized.		response if they are not recognized.
	o All TLVs and sub-TLVs in the range 32768-65535 may be silently		* All TLVs and sub-TLVs in the range 32768-65535 can be silently
	dropped, stepped over or an error message sent if they are not		dropped if they are not recognized. Alternatively, the receiver
	recognized.		may step over the unrecognized TLV or send an error message.
	Each of the blocks has code point spaces with the following		Each of the blocks has code point spaces with the following
	registration procedures:		registration procedures:
	o Standards Action.		* Standards Action
	o RFC Required.		* RFC Required
	o Experimental Use.		* Experimental Use
	o First Come First Served (FCFS).		* First Come First Served (FCFS)
	The exact definitions of these procedures are found in [RFC8126].		The exact definitions of these procedures are found in [RFC8126].
	3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs		3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs
	Unrecognized TLVs and sub-TLVs in the Experimental Use, and FCFS		Unrecognized TLVs and sub-TLVs in the Experimental Use and FCFS
	ranges are handled as any other unrecognized TLV or sub-TLV.		ranges are handled as any other unrecognized TLV or sub-TLV.
	o If the unrecognized TLV or sub-TLV is from the Experimental Use		* If the unrecognized TLV or sub-TLV is from the Experimental Use
	range (31740-31743) or from the FCFS range (31744-32767) a Return		range (31740-31743) or from the FCFS range (31744-32767), a Return
	Code of 2 ("One or more of the TLVs was not understood") must be		Code of 2 ("One or more of the TLVs was not understood") must be
	sent in the echo response.		sent in the echo response.
	o If the unrecognized TLV or sub-TLV is from the Experimental Use		* If a TLV or sub-TLV from the Experimental Use range (64508-64511)
	range (64508-64511) or from the FCFS range (64512-65535) the TLVs		or from the FCFS range (64512-65535) is unrecognized, then the
	may be silently ignored, stepped over or an error message sent.		receiver can silently drop the TLV. Alternatively, the receiver
			may step over the unrecognized TLV or send an error message.
	The IETF does not prescribe how recognized or unrecognized		The IETF does not prescribe how recognized or unrecognized
	Experimental Use and Private Use TLVs and sub-TLVs are handled in		Experimental Use and Private Use TLVs and sub-TLVs are handled in
	experimental or private networks; that is up to the agency running		experimental or private networks; that is up to the agency running
	the experimental or the private network. The statement above		the experimental or the private network. The statement above
	describes how standards compliant implementations must treat the		describes how standards-compliant implementations must treat the
	unrecognized TLVs and sub-TLVs from these ranges.		unrecognized TLVs and sub-TLVs from these ranges.
	3.2. Common Registration Procedures for TLVs and sub-TLVs		3.2. Common Registration Procedures for TLVs and Sub-TLVs
	This section describes the new registration procedures for the TLV		This section describes the new registration procedures for the TLV
	and sub-TLV registries.		and sub-TLV registries.
	+-------------+-------------------+---------------------------------+		+=============+==============+=====================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+=====================================+
	| 0-16383 | Standards Action | This range is for TLVs and sub- |		| 0-16383 | Standards | This range is for TLVs and sub-TLVs |
	| | | TLVs that require an error |		| | Action | that require an error message if |
	| | | message if not recognized. |		| | | not recognized. This document, |
	| | | [This document, section 3.1] |		| | | Section 3.1 |
	| 16384-31739 | RFC Required | This range is for TLVs and sub- |		+-------------+--------------+-------------------------------------+
	| | | TLVs that require an error |		| 16384-31739 | RFC Required | This range is for TLVs and sub-TLVs |
	| | | message if not recognized. |		| | | that require an error message if |
	| | | [This document, section 3.1] |		| | | not recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1 |
	| | | This range is for TLVs and sub- |		+-------------+--------------+-------------------------------------+
	| | | TLVs that require an error |		| 31740-31743 | Reserved for | Not to be assigned. This range is |
	| | | message if not recognized. |		| | Experimental | for TLVs and sub-TLVs that require |
	| | | [This document, section 3.1] |		| | Use | an error message if not recognized. |
	| 31744-32767 | FCFS | This range is for TLVs and sub- |		| | | This document, Section 3.1 |
	| | | TLVs that require an error |		+-------------+--------------+-------------------------------------+
	| | | message if not recognized. |		| 31744-32767 | FCFS | This range is for TLVs and sub-TLVs |
	| | | [This document, section 3.1] |		| | | that require an error message if |
	| 32768-49161 | Standards Action | This range is for TLVs and sub- |		| | | not recognized. This document, |
	| | | TLVs that can be silently |		| | | Section 3.1 |
	| | | dropped if not recognized. |		+-------------+--------------+-------------------------------------+
	| 49162-64507 | RFC Required | This range is for TLVs and sub- |		| 32768-49161 | Standards | This range is for TLVs and sub-TLVs |
	| | | TLVs that can be silently |		| | Action | that can be silently dropped if not |
	| | | dropped if not recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+-------------------------------------+
	| | | This range is for TLVs and sub- |		| 49162-64507 | RFC Required | This range is for TLVs and sub-TLVs |
	| | | TLVs that can be silently |		| | | that can be silently dropped if not |
	| | | dropped if not recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for TLVs and sub- |		+-------------+--------------+-------------------------------------+
	| | | TLVs that can be silently |		| 64508-64511 | Reserved for | Not to be assigned. This range is |
	| | | dropped if not recognized. |		| | Experimental | for TLVs and sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not recognized. |
			+-------------+--------------+-------------------------------------+
			| 64512-65535 | FCFS | This range is for TLVs and sub-TLVs |
			| | | that can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+-------------------------------------+
	Table 1: TLV and sub-TLV Registration Procedures		Table 1: TLV and Sub-TLV Registration Procedures
	3.3. Changes to the LSP Ping Registries		3.3. Changes to the LSP Ping Registries
	This section lists the changes to each MPLS LSP Ping TLV and sub-TLV		This section lists the changes to each MPLS LSP Ping TLV and sub-TLV
	Registry. Section 6.2.1 to 6.2.7 describe how the new versions of		registry. Sections 6.2.1 to 6.2.7 describe how the new versions of
	the IANA registries should look, together with the registration		the IANA registries should look, together with the registration
	procedures for each registry.		procedures for each registry.
	The new Registration Procedures description and the new assignments		The new registration procedure descriptions and the new assignments
	for these registries are used to model the changed MPLS LSP Ping		for these registries are used to model the changed MPLS LSP Ping
	registries, see Section 6.		registries; see Section 6.
	3.3.1. Common Changes to the TLV and Sub-TLV Registries		3.3.1. Changes Common to the TLV and Sub-TLV Registries
	The following changes are made to the TLV and sub-TLV registries.		The following changes are made to the TLV and sub-TLV registries.
	o The registration procedures "First Come First Served (FCFS)" and		* The registration procedures "First Come First Served" (FCFS) and
	"Experimental Use" are added to the table of registration		"Experimental Use" have been added to the table of registration
	procedures.		procedures.
	o Two small sets of code points (4 code points each) for		* Two small sets of code points (four code points each) for
	Experimental Use, are created. The first set is for the range		Experimental Use have been created. The first set is for the
	that requires a response if the TLV or sub-TLV is not recognized;		range that requires a response if the TLV or sub-TLV is not
	the second set is for the range where the TLV or sub-TLV that may		recognized; the second set is for the range where the TLV or sub-
	be silently dropped if not recognized. The code points for		TLV may be silently dropped if not recognized. The code points
	experimental use are taken from the ranges previously (RFC 8029)		for Experimental Use have been taken from the ranges previously
	called 'Specification Required' and (RFC 8611) "RFC Required".		called "Specification Required" and "RFC Required" [RFC8029].
	o The registration procedure "Specification Required" is changed to		* The registration procedure "Specification Required" has been
	"RFC Required" and the note "Experimental RFC needed" is removed.		changed to "RFC Required", and the note "Experimental RFC needed"
			has been removed.
	o In the listing of assignments the term "Vendor Private Use" is		* In the listing of assignments, the term "Vendor Private Use" has
	changed to "First Come First Served (FCFS)".		been changed to "First Come First Served" (FCFS).
	o In the listing of assignments the range for "Experimental Use" is		* In the listing of assignments, the range for "Experimental Use"
	added.		has been added.
	o A note saying "Not to be assigned" is added for the registration		* A note saying "Not to be assigned" has been added for the
	procedures "Experimental Use".		registration procedure "Experimental Use".
	o In the list that captures assignment status, the fields that are		* In the list that captures assignment status, the fields that are
	reserved, i.e., 0 (zero) and Experimental Use are clearly marked.		reserved, i.e., 0 (zero) and Experimental Use, have been clearly
			marked.
	4. Updates to Related RFCs		4. Updates to Related RFCs
	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.
	The same RFCs use "optional TLVs" and "optional sub-TLVs" to mean		The same RFCs use "optional TLVs" and "optional sub-TLVs" to mean
	TLVs or sub-TLVs that can be silently ignored if not recognized.		TLVs or sub-TLVs that can be silently ignored if not recognized.
	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		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		to discontinue the use of "mandatory" to indicate TLVs and sub-TLVs
	that require an error message in response if not understood. The		that require an error message in response if not understood. The
	changes to the RFCs below align with this practice.		changes to the RFCs below align with this practice.
	4.1. Updates to RFC 8029		4.1. Updates to RFC 8029
	Mandatory and optional are used to indicate whether a response is		"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		needed if a TLV or sub-TLV is not understood in Section 3 of
	Section 3 of RFC 8029.		"Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures"
			[RFC8611].
	The text in those two paragraphs is now updated to the following:		The text in those two paragraphs is now updated to the following:
	TLV and sub-TLV Types less than 32768 (i.e., with the high-order		| TLV and sub-TLV types less than 32768 (i.e., with the high-order
	bit equal to 0) are TLVs and sub-TLVs that MUST either be		| bit equal to 0) are TLVs and sub-TLVs that MUST either be
	supported by an implementation or result in the Return Code of 2		| 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.
			|
	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.,		| 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		| with the high-order bit equal to 1) SHOULD ignore and step over
	the TLV or sub-TLV, however an implementation MAY send an echo		| the TLV or sub-TLV; however, an implementation MAY send an echo
	response with Return Code 2 ("One or more of the TLVs was not		| response with a Return Code of 2 ("One or more of the TLVs was not
	understood") as it would have done if the high order bit had been		| understood") as it would have done if the high-order bit had been
	clear.		| clear.
	In Section 3.8 of RFC 8029 "mandatory" is used in the same way. The		In Section 3.8 of [RFC8029], "mandatory" is used in the same way.
	first two paragraphs of this section are now updated to read as		The first two paragraphs of this section are now updated to read as
	follows:		follows:
	The following TLV is a TLV that MAY be included in an echo reply		| The following TLV is a TLV that MAY be included in an echo reply
	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-
	TLVs Types less than 32768 (i.e., with the high-order bit equal to		| TLV Types less than 32768 (i.e., with the high-order bit equal to
	0) that are either not supported by the implementation or parsed		| 0) that are either not supported by the implementation or parsed
	and found to be in error.		| and found to be in error.
			|
	The Value field contains the TLVs, including sub-TLVs, that were		| The Value field uses sub-TLVs to encode the received TLVs and sub-
	not understood, encoded as sub-TLVs.		| TLVs that were not understood.
	4.2. Updates to RFC 8611		4.2. Updates to RFC 8611
	Section 13.4.1 of "Label Switched Path (LSP) Ping and Traceroute		Section 13.4.1 of "Label Switched Path (LSP) Ping and Traceroute
	Multipath Support for Link Aggregation Group (LAG) Interfaces		Multipath Support for Link Aggregation Group (LAG) Interfaces"
	[RFC8611]" defines "Sub-TLVs for TLV Type 6" [IANA-Sub-6].		[RFC8611] defines "Sub-TLVs for TLV Type 6" [IANA-Sub-6].
	The "Sub-TLVs for TLV Type 6" registry is now updated to align with		The "Sub-TLVs for TLV Type 6" registry has been updated to align with
	changes defined in this document.		changes defined in this document.
	Section 13.4.1 of RFC 8611 is now updated as follows:		Section 13.4.1 of [RFC8611] is now updated as follows:
	Section 13.4.1 Sub-TLVs for TLV Type 6		| Section 13.4.1 Sub-TLVs for TLV Type 6
	IANA has created a new sub-registry "Sub-TLVs for TLV Type 6"		IANA has created a new subregistry, "Sub-TLVs for TLV Type 6",
	[IANA-Sub-6] under the "TLVs" registry [IANA-TLV-reg] of the		[IANA-Sub-6] under the "TLVs" registry [IANA-TLV-reg] of the
	"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)		"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
	Ping Parameters" namespace [lsp-ping-Namespace].		Ping Parameters" namespace [lsp-ping-Namespace].
	The "Sub-TLVs for TLV Type 6" sub-registry is now updated to align		The "Sub-TLVs for TLV Type 6" subregistry is now updated to align
	with changes defined in this document.		with changes defined in this document.
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1 |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved not to be assigned. |		| | | Section 3.1 |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1 |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1 |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for sub-TLVs that |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 2: Sub-TLVs for TLV Type 6 Registration Procedures		Table 2: Sub-TLVs for TLV Type 6 Registration Procedures
	5. Security Considerations		5. Security Considerations
	This document updates IANA registries. It also updates terminology		This document updates IANA registries. It also updates terminology
	used to define, and clarifies the terminology related to, the code		used to define, and 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 registries are used. This should not create any new		points in the registries are used. This should not create any new
	threats.		threats.
	However, the updated terminology and the clarifications improve		However, the updated terminology and the clarifications improve
	security because it makes it more likely that implementations will be		security because it makes it more likely that implementations will be
	consistent and harder to attack.		consistent and harder to attack.
	6. IANA Considerations		6. IANA Considerations
	IANA is requested to update the "Multiprotocol Label Switching (MPLS)		IANA has updated the "Multiprotocol Label Switching (MPLS) Label
	Label Switched Paths (LSPs) Ping Parameters" namespace		Switched Paths (LSPs) Ping Parameters" namespace [IANA-LSP-PING] as
	[IANA-LSP-PING] as described in this document.		described in this document.
	See Section 1.2.1 "Terminology Used in this Document" to see how		See Section 1.2.1 of "Terminology Used in This Document" to see how
	"namespace", "registry" and "sub-registry" are used in this document.		"namespace", "registry", and "subregistry" are used in this document.
	In other parts of this document the communality of the changes to the		In other parts of this document, the commonality of the changes to
	LSP Ping registries has been the focus. For the IANA considerations		the LSP Ping registries has been the focus. For the IANA
	each changed registry has been described in its own right.		Considerations, each changed registry has been described in its own
			right.
	The following registries and sub-registries are changed:		The following registries and subregistries have been changed:
	"Message Types", [IANA-MT],		* "Message Types", [IANA-MT]
	"Reply Modes", [IANA-RM]
	"Return Codes" [IANA-RC]
	"TLVs" [IANA-TLV-reg]
	"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21]
	"Sub-TLVs for TLV Type 6" [IANA-Sub-6]
	"Sub-TLVs for TLV Type 11" [IANA-Sub-11]
	"Sub-TLVs for TLV Type 20" [IANA-Sub-20]
	"Sub-TLVs for TLV Type 23" [IANA-Sub-23]
	"Sub-TLVs for TLV Type 27" [IANA-Sub-27]
	This document will be listed as an additional reference for each of		* "Reply Modes", [IANA-RM]
			* "Return Codes", [IANA-RC]
			* "TLVs", [IANA-TLV-reg]
			* "Sub-TLVs for TLV Types 1, 16, and 21", [IANA-Sub-1-16-21]
			* "Sub-TLVs for TLV Type 6", [IANA-Sub-6]
			* "Sub-TLVs for TLV Type 11", [IANA-Sub-11]
			* "Sub-TLVs for TLV Type 20", [IANA-Sub-20]
			* "Sub-TLVs for TLV Type 23", [IANA-Sub-23]
			* "Sub-TLVs for TLV Type 27", [IANA-Sub-27]
			This document has been listed as an additional reference for each of
	the registries described in Sections 6.1 and 6.2.		the registries described in Sections 6.1 and 6.2.
	6.1. Updates to the Message Type, Reply Mode and Return Codes		6.1. Updates by IANA to the Message Types, Reply Modes, and Return
	Registries		Codes Registries
	This section details the updated registration procedures and		This section details the updated registration procedures and
	allocations for "Message Type", "Reply Mode" and "Return Codes"		allocations for the "Message Types", "Reply Modes", and "Return
	registries.		Codes" registries.
	6.1.1. Updates to the Message Type registry		6.1.1. Updates to the Message Types Registry
	This is the changes to the "Message Type" registry specified in this		These are the changes to the "Message Types" registry specified in
	document:		this document:
	o Code Point 0 (zero) is marked Reserved.		* Code Point 0 (zero) has been marked Reserved.
	o The registration procedure "Specification Required" is changed to		* The registration procedure "Specification Required" has been
	"RFC Required" and the comment "Experimental RFC needed" is		changed to "RFC Required", and the comment "Experimental RFC
	removed.		needed" has been removed.
	o Four code point have been taken from what was earlier		* Four code points have been taken from what was previously
	"Specification Required" to form a set of code points for		"Specification Required" to form a set of code points for
	"Experimental Use."		"Experimental Use".
	The registration procedures after the changes for the "Message Type"		The registration procedures after the changes listed above for the
	registry are shown in the table below:		"Message Types" registry are shown in the table below:
	+---------+--------------------+------------------------------------+		+=========+=========================+==============================+
	| Range | Registration | Note |		| Range | Registration Procedures | Note |
	| | Procedures | |		+=========+=========================+==============================+
	+---------+--------------------+------------------------------------+		| 0-191 | Standards Action | |
	| 0-191 | Standards Action | |		+---------+-------------------------+------------------------------+
	| 192-247 | RFC Required | |		| 192-247 | RFC Required | |
	| 248-251 | Experimental Use | Reserved, not to be assigned |		+---------+-------------------------+------------------------------+
	| 252-255 | Private Use | Reserved, not to be assigned |		| 248-251 | Experimental Use | Reserved, not to be assigned |
	+---------+--------------------+------------------------------------+		+---------+-------------------------+------------------------------+
			| 252-255 | Private Use | Reserved, not to be assigned |
			+---------+-------------------------+------------------------------+
	Table 3: Message Type registration procedures		Table 3: Message Types Registration Procedures
	The updated assignments for the "Message Types" registry will look		The updated assignments for the "Message Types" registry appear as
	like this:		follows:
	+---------+---------------------------------+-----------------------+		+=========+===============================+===============+
	| Value | Meaning | Reference |		| Value | Meaning | Reference |
	+---------+---------------------------------+-----------------------+		+=========+===============================+===============+
	| 0 | Reserved | This document |		| 0 | Reserved | This document |
	| 1 | MPLS Echo Request | [RFC8029] |		+---------+-------------------------------+---------------+
	| 2 | MPLS Echo Reply | [RFC8029] |		| 1 | MPLS Echo Request | [RFC8029] |
	| 3 | MPLS Proxy Ping Request | [RFC7555] |		+---------+-------------------------------+---------------+
	| 4 | MPLS Proxy Ping Reply | [RFC7555] |		| 2 | MPLS Echo Reply | [RFC8029] |
	| 5 | MPLS Relayed Echo Reply | [RFC7743] |		+---------+-------------------------------+---------------+
	| 6-247 | Unassigned | |		| 3 | MPLS Proxy Ping Request | [RFC7555] |
	| 248-251 | Reserved for Experimental Use | This document |		+---------+-------------------------------+---------------+
	| 252-255 | Reserved for Private Use | [RFC8029] |		| 4 | MPLS Proxy Ping Reply | [RFC7555] |
	+---------+---------------------------------+-----------------------+		+---------+-------------------------------+---------------+
			| 5 | MPLS Relayed Echo Reply | [RFC7743] |
			+---------+-------------------------------+---------------+
			| 6-247 | Unassigned | |
			+---------+-------------------------------+---------------+
			| 248-251 | Reserved for Experimental Use | This document |
			+---------+-------------------------------+---------------+
			| 252-255 | Reserved for Private Use | [RFC8029] |
			+---------+-------------------------------+---------------+
	Table 4: Assignments for the Message Types registry		Table 4: Assignments for the Message Types Registry
	6.1.2. Updates to the Reply Modes registry		6.1.2. Updates to the Reply Modes Registry
	This is the changes to the "Reply Modes" registry specified in this		These are the changes to the "Reply Modes" registry specified in this
	document:		document:
	o Code Point 0 (zero) is marked Reserved.		* Code Point 0 (zero) has been marked Reserved.
	o The registration procedure "Specification Required" is changed to		* The registration procedure "Specification Required" has been
	"RFC Required" and the comment "Experimental RFC needed" is		changed to "RFC Required", and the comment "Experimental RFC
	removed.		needed" has been removed.
	o Four code point have been taken from what was earlier		* Four code points have been taken from what was previously
	"Specification Required" to form a set of code points for		"Specification Required" to form a set of code points for
	"Experimental Use".		"Experimental Use".
	The registration procedures after the changes for the "Reply Modes"		The registration procedures after the changes for the "Reply Modes"
	registry are show in the table below:		registry are shown in the table below:
	+---------+--------------------+------------------------------------+		+=========+=========================+==============================+
	| Range | Registration | Note |		| Range | Registration Procedures | Note |
	| | Procedures | |		+=========+=========================+==============================+
	+---------+--------------------+------------------------------------+		| 0-191 | Standards Action | |
	| 0-191 | Standards Action | |		+---------+-------------------------+------------------------------+
	| 192-247 | RFC Required | |		| 192-247 | RFC Required | |
	| 248-251 | Experimental Use | Reserved, not to be assigned |		+---------+-------------------------+------------------------------+
	| 252-255 | Private Use | Reserved, not to be assigned |		| 248-251 | Experimental Use | Reserved, not to be assigned |
	+---------+--------------------+------------------------------------+		+---------+-------------------------+------------------------------+
			| 252-255 | Private Use | Reserved, not to be assigned |
			+---------+-------------------------+------------------------------+
	Table 5: Reply Modes registration procedures		Table 5: Reply Modes Registration Procedures
	The updated assignments for the "Reply Modes" registry will look like		The updated assignments for the "Reply Modes" registry are as
	this:		follows:
	+---------+---------------------------------+-----------------------+		+=========+===================================+===============+
	| Value | Meaning | Reference |		| Value | Meaning | Reference |
	+---------+---------------------------------+-----------------------+		+=========+===================================+===============+
	| 0 | Reserved | This document |		| 0 | Reserved | This document |
	| 1 | Do not reply | [RFC8029] |		+---------+-----------------------------------+---------------+
	| 2 | Reply via an IPv4/IPv6 UDP | [RFC8029] |		| 1 | Do not reply | [RFC8029] |
	| | packet | |		+---------+-----------------------------------+---------------+
	| 3 | Reply via an IPv4/IPv6 UDP | [RFC8029] |		| 2 | Reply via an IPv4/IPv6 UDP packet | [RFC8029] |
	| | packet with Router Alert | |		+---------+-----------------------------------+---------------+
	| 4 | Reply via application-level | [RFC8029] |		| 3 | Reply via an IPv4/IPv6 UDP packet | [RFC8029] |
	| | control channel | |		| | with Router Alert | |
	| 5 | Reply via Specified Path | [RFC7110] |		+---------+-----------------------------------+---------------+
	| 6-247 | Unassigned | |		| 4 | Reply via application-level | [RFC8029] |
	| 248-251 | Reserved for Experimental Use | This document |		| | control channel | |
	| 252-255 | Reserved for Private Use | [RFC8029] |		+---------+-----------------------------------+---------------+
	+---------+---------------------------------+-----------------------+		| 5 | Reply via Specified Path | [RFC7110] |
			+---------+-----------------------------------+---------------+
			| 6-247 | Unassigned | |
			+---------+-----------------------------------+---------------+
			| 248-251 | Reserved for Experimental Use | This document |
			+---------+-----------------------------------+---------------+
			| 252-255 | Reserved for Private Use | [RFC8029] |
			+---------+-----------------------------------+---------------+
	Table 6: Assignments for the Reply Modes registry		Table 6: Assignments for the Reply Modes Registry
	6.1.3. Updates to the Return Codes registry		6.1.3. Updates to the Return Codes Registry
	These are the changes to the "Return Codes" registry specified in		These are the changes to the "Return Codes" registry specified in
	this document:		this document:
	o The registration procedure "Specification Required" is changed to		* The registration procedure "Specification Required" has been
	"RFC Required" and the comment "Experimental RFC needed" is		changed to "RFC Required", and the comment "Experimental RFC
	removed.		needed" has been removed.
	o Four code point have been taken from what was earlier		* Four code points have been taken from what was previously
	"Specification Required" to form a set of code points for		"Specification Required" to form a set of code points for
	"Experimental Use".		"Experimental Use".
	The registration procedures after the changes for the "Return Codes"		The registration procedures after the changes for the "Return Codes"
	registry are show in the table below:		registry are shown in the table below:
	+---------+--------------------+------------------------------------+		+=========+=========================+==============================+
	| Range | Registration | Note |		| Range | Registration Procedures | Note |
	| | Procedures | |		+=========+=========================+==============================+
	+---------+--------------------+------------------------------------+		| 0-191 | Standards Action | |
	| 0-191 | Standards Action | |		+---------+-------------------------+------------------------------+
	| 192-247 | RFC Required | |		| 192-247 | RFC Required | |
	| 248-251 | Experimental Use | Reserved, not to be assigned |		+---------+-------------------------+------------------------------+
	| 252-255 | Private Use | Reserved, not to be assigned |		| 248-251 | Experimental Use | Reserved, not to be assigned |
	+---------+--------------------+------------------------------------+		+---------+-------------------------+------------------------------+
			| 252-255 | Private Use | Reserved, not to be assigned |
			+---------+-------------------------+------------------------------+
	Table 7: Return Codes registration procedures		Table 7: Return Codes Registration Procedures
	The updated assignments for the "Return Codes" registry will look		The updated assignments for the "Return Codes" registry are as
	like this:		follows:
	+---------+----------------------------------+----------------------+		+=========+=========================================+=============+
	| Value | Meaning | Reference |		| Value | Meaning | Reference |
	+---------+----------------------------------+----------------------+		+=========+=========================================+=============+
	| 0 | No Return Code | This document |		| 0 | No Return Code | [RFC8029] |
	| 1 | Malformed echo request received | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| 2 | One or more of the TLVs was not | [RFC8029] |		| 1 | Malformed echo request received | [RFC8029] |
	| | understood | |		+---------+-----------------------------------------+-------------+
	| 3 | Replying router is an egress for | [RFC8029] |		| 2 | One or more of the TLVs was not | [RFC8029] |
	| | the FEC at stack-depth <RSC> | |		| | understood | |
	| 4 | Replying router has no mapping | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | for the FEC at stack-depth <RSC> | |		| 3 | Replying router is an egress for the | [RFC8029] |
	| 5 | Downstream Mapping Mismatch (See | [RFC8029] |		| | FEC at stack-depth <RSC> | |
	| | [1]) | |		+---------+-----------------------------------------+-------------+
	| 6 | Upstream Interface Index Unknown | [RFC8029] |		| 4 | Replying router has no mapping for the | [RFC8029] |
	| | (See [1]) | |		| | FEC at stack-depth <RSC> | |
	| 7 | Reserved | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| 8 | Label switched at stack-depth | [RFC8029] |		| 5 | Downstream Mapping Mismatch (See [1]) | [RFC8029] |
	| | <RSC> | |		+---------+-----------------------------------------+-------------+
	| 9 | Label switched but no MPLS | [RFC8029] |		| 6 | Upstream Interface Index Unknown (See | [RFC8029] |
	| | forwarding at stack-depth <RSC> | |		| | [1]) | |
	| 10 | Mapping for this FEC is not the | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | given label at stack-depth <RSC> | |		| 7 | Reserved | [RFC8029] |
	| 11 | No label entry at stack-depth | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | <RSC> | |		| 8 | Label switched at stack-depth <RSC> | [RFC8029] |
	| 12 | Protocol not associated with | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | interface at FEC stack-depth | |		| 9 | Label switched but no MPLS forwarding | [RFC8029] |
	| | <RSC> | |		| | at stack-depth <RSC> | |
	| 13 | Premature termination of ping | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | due to label stack shrinking to | |		| 10 | Mapping for this FEC is not the given | [RFC8029] |
	| | a single label | |		| | label at stack-depth <RSC> | |
	| 14 | See DDMAP TLV for meaning of | [RFC8029] |		+---------+-----------------------------------------+-------------+
	| | Return Code and Return Subcode | |		| 11 | No label entry at stack-depth <RSC> | [RFC8029] |
	| | (See [2]) | |		+---------+-----------------------------------------+-------------+
	| 15 | Label switched with FEC change | [RFC8029] |		| 12 | Protocol not associated with interface | [RFC8029] |
	| 16 | Proxy Ping not authorized | [RFC7555] |		| | at FEC stack-depth <RSC> | |
	| 17 | Proxy Ping parameters need to be | [RFC7555] |		+---------+-----------------------------------------+-------------+
	| | modified | |		| 13 | Premature termination of ping due to | [RFC8029] |
	| 18 | MPLS Echo Request could not be | [RFC7555] |		| | label stack shrinking to a single label | |
	| | sent | |		+---------+-----------------------------------------+-------------+
	| 19 | Replying router has FEC mapping | [RFC7555] |		| 14 | See DDMAP TLV for meaning of Return | [RFC8029] |
	| | for topmost FEC | |		| | Code and Return Subcode (See [2]) | |
	| 20 | One or more TLVs not returned | [RFC7743] |		+---------+-----------------------------------------+-------------+
	| | due to MTU size | |		| 15 | Label switched with FEC change | [RFC8029] |
	| 21 | OAM Problem/Unsupported BFD | [RFC7759] |		+---------+-----------------------------------------+-------------+
	| | Version | |		| 16 | Proxy Ping not authorized | [RFC7555] |
	| 22 | OAM Problem/Unsupported BFD | [RFC7759] |		+---------+-----------------------------------------+-------------+
	| | Encapsulation format | |		| 17 | Proxy Ping parameters need to be | [RFC7555] |
	| 23 | OAM Problem/Unsupported BFD | [RFC7759] |		| | modified | |
	| | Authentication Type | |		+---------+-----------------------------------------+-------------+
	| 24 | OAM Problem/Mismatch of BFD | [RFC7759] |		| 18 | MPLS Echo Request could not be sent | [RFC7555] |
	| | Authentication Key ID | |		+---------+-----------------------------------------+-------------+
	| 25 | OAM Problem/Unsupported | [RFC7759] |		| 19 | Replying router has FEC mapping for | [RFC7555] |
	| | Timestamp Format | |		| | topmost FEC | |
	| 26 | OAM Problem/Unsupported Delay | [RFC7759] |		+---------+-----------------------------------------+-------------+
	| | Mode | |		| 20 | One or more TLVs not returned due to | [RFC7743] |
	| 27 | OAM Problem/Unsupported Loss | [RFC7759] |		| | MTU size | |
	| | Mode | |		+---------+-----------------------------------------+-------------+
	| 28 | OAM Problem/Delay variation | [RFC7759] |		| 21 | OAM Problem/Unsupported BFD Version | [RFC7759] |
	| | unsupported | |		+---------+-----------------------------------------+-------------+
	| 29 | OAM Problem/Dyadic mode | [RFC7759] |		| 22 | OAM Problem/Unsupported BFD | [RFC7759] |
	| | unsupported | |		| | Encapsulation format | |
	| 30 | OAM Problem/Loopback mode | [RFC7759] |		+---------+-----------------------------------------+-------------+
	| | unsupported | |		| 23 | OAM Problem/Unsupported BFD | [RFC7759] |
	| 31 | OAM Problem/Combined mode | [RFC7759] |		| | Authentication Type | |
	| | unsupported | |		+---------+-----------------------------------------+-------------+
	| 32 | OAM Problem/Fault management | [RFC7759] |		| 24 | OAM Problem/Mismatch of BFD | [RFC7759] |
	| | signaling unsupported | |		| | Authentication Key ID | |
	| 33 | OAM Problem/Unable to create | [RFC7759] |		+---------+-----------------------------------------+-------------+
	| | fault management association | |		| 25 | OAM Problem/Unsupported Timestamp | [RFC7759] |
	| 34 | OAM Problem/PM Configuration | [RFC7759] |		| | Format | |
	| | Error | |		+---------+-----------------------------------------+-------------+
	| 35 | Mapping for this FEC is not | [RFC8287] sec 7.4 |		| 26 | OAM Problem/Unsupported Delay Mode | [RFC7759] |
	| | associated with the incoming | |		+---------+-----------------------------------------+-------------+
	| | interface | |		| 27 | OAM Problem/Unsupported Loss Mode | [RFC7759] |
	| 36-247 | Unassigned | |		+---------+-----------------------------------------+-------------+
	| 248-251 | Reserved for Experimental Use | This document |		| 28 | OAM Problem/Delay variation unsupported | [RFC7759] |
	| 252-255 | Reserved for Private Use | [RFC8029] |		+---------+-----------------------------------------+-------------+
	+---------+----------------------------------+----------------------+		| 29 | OAM Problem/Dyadic mode unsupported | [RFC7759] |
			+---------+-----------------------------------------+-------------+
			| 30 | OAM Problem/Loopback mode unsupported | [RFC7759] |
			+---------+-----------------------------------------+-------------+
			| 31 | OAM Problem/Combined mode unsupported | [RFC7759] |
			+---------+-----------------------------------------+-------------+
			| 32 | OAM Problem/Fault management signaling | [RFC7759] |
			| | unsupported | |
			+---------+-----------------------------------------+-------------+
			| 33 | OAM Problem/Unable to create fault | [RFC7759] |
			| | management association | |
			+---------+-----------------------------------------+-------------+
			| 34 | OAM Problem/PM Configuration Error | [RFC7759] |
			+---------+-----------------------------------------+-------------+
			| 35 | Mapping for this FEC is not associated | [RFC8287], |
			| | with the incoming interface | Section 7.4 |
			+---------+-----------------------------------------+-------------+
			| 36-247 | Unassigned | |
			+---------+-----------------------------------------+-------------+
			| 248-251 | Reserved for Experimental Use | This |
			| | | document |
			+---------+-----------------------------------------+-------------+
			| 252-255 | Reserved for Private Use | [RFC8029] |
			+---------+-----------------------------------------+-------------+
	Table 8: Assignments for the Return Codes registry		Table 8: Assignments for the Return Codes Registry
	Note 1: Notes [1] and [2] for code points 5, 6 and 14 point to		Note 1: Notes [1] and [2] for code points 5, 6, and 14 point to
	footnotes in the "Multiprotocol Label Switching (MPLS) Label Switched		footnotes in the "Multiprotocol Label Switching (MPLS) Label
	Paths (LSPs) Ping Parameters" namespace. The footnotes are not		Switched Paths (LSPs) Ping Parameters" namespace. The footnotes
	changed by this document.		are not changed by this document.
	Note 2: <RSC> stands for "Return Subcode" and is explained in section		Note 2: <RSC> stands for "Return Subcode" and is explained in
	3.1 of RFC 8029 [RFC8029].		Section 3.1 of [RFC8029].
	6.2. Updates to the TLV and Sub-TLV registries		6.2. Updates to the TLV and Sub-TLV Registries
	The updates to the TLV and the sub-TLV registries are mostly the		The updates to the TLV and the sub-TLV registries are mostly the
	same, however the Sub-TLVs for TLV Type 9 [IANA-Sub-9] have not been		same; however, the "Sub-TLVs for TLV Type 9" [IANA-Sub-9] registry
	updated.		has not been updated.
	Note that when a field in an assignment table says "EQ", it means		Note that when a field in an assignment table says "EQ", it means
	that there is no change from the existing field in the "Multiprotocol		that there is no change from the existing field in the "Multiprotocol
	Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters"		Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters"
	namespace [IANA-LSP-PING]		namespace [IANA-LSP-PING].
	6.2.1. Updates to the TLVs registry		6.2.1. Updates to the TLVs Registry
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "TLVs" registry [IANA-TLV-reg] based on the new		assignments for the "TLVs" registry [IANA-TLV-reg] that are based on
	registration procedures.		them.
	The registration procedures have been changed, as follows, for the		The registration procedures have been changed, as follows, for the
	"TLVs" registry.		"TLVs" registry.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required". The comment "Experimental RFC
	has been removed. Note that when a field in an assignment table		Required" has been removed. Note that when a field in an
	says "EQ", it means that there is no change from the existing		assignment table says "EQ", it means that there is no change from
	field in the "Multiprotocol Label Switching (MPLS) Label Switched		the existing field in the "Multiprotocol Label Switching (MPLS)
	Paths (LSPs) Ping Parameters" namespace [IANA-LSP-PING].		Label Switched Paths (LSPs) Ping Parameters" namespace
			[IANA-LSP-PING].
	o RFC 8611 was published after RFC 8126 and uses the new		* [RFC8611] was published after [RFC8126] and uses the new
	terminology, e.g. "Private Use". The code points registration		terminology, e.g., "Private Use". The code points registration
	procedure "Private Use" has been replaced by the "First Come,		procedure "Private Use" has been replaced by the "First Come First
	First Served" code point registration proceedure.		Served" code point registration procedure.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a TLV is not		to reflect whether or not a response is required if a TLV is not
	recognized.		recognized.
	The registration procedures for the "TLVs" registry [IANA-TLV-reg]		The registration procedures for the "TLVs" registry [IANA-TLV-reg]
	will now look like this:		after the changes listed above are shown in the table below:
	+-------------+-------------------+---------------------------------+		+=============+==============+=====================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+=====================================+
	| 0-16383 | Standards Action | This range is for TLVs that |		| 0-16383 | Standards | This range is for TLVs that require |
	| | | require an error message if not |		| | Action | an error message if not recognized. |
	| | | recognized. [This document, |		| | | This document, Section 3.1 |
	| | | section 3.1] |		+-------------+--------------+-------------------------------------+
	| 16384-31739 | RFC Required | This range is for TLVs that |		| 16384-31739 | RFC Required | This range is for TLVs that require |
	| | | require an error message if not |		| | | an error message if not recognized. |
	| | | recognized. [This document, |		| | | This document, Section 3.1 |
	| | | section 3.1] |		+-------------+--------------+-------------------------------------+
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| 31740-31743 | Reserved for | Not to be assigned. This range is |
	| | | This range is for sub-TLVs that |		| | Experimental | for TLVs that require an error |
	| | | require an error message if not |		| | Use | message if not recognized. This |
	| | | recognized. [This document, |		| | | document, Section 3.1 |
	| | | section 3.1] |		+-------------+--------------+-------------------------------------+
	| 31744-32767 | FCFS | This range is for TLVs that |		| 31744-32767 | FCFS | This range is for TLVs that require |
	| | | require an error message if not |		| | | an error message if not recognized. |
	| | | recognized. [This document, |		| | | This document, Section 3.1 |
	| | | section 3.1] |		+-------------+--------------+-------------------------------------+
	| 32768-49161 | Standards Action | This range is for TLVs that can |		| 32768-49161 | Standards | This range is for TLVs that can be |
	| | | be silently dropped if not |		| | Action | silently dropped if not recognized. |
	| | | recognized. |		+-------------+--------------+-------------------------------------+
	| 49162-64507 | RFC Required | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for TLVs that can be |
	| | | be silently dropped if not |		| | | silently dropped if not recognized. |
	| | | recognized. |		+-------------+--------------+-------------------------------------+
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		| 64508-64511 | Reserved for | Not to be assigned. This range is |
	| | | This range is for TLVs that can |		| | Experimental | for TLVs that can be silently |
	| | | be silently dropped if not |		| | Use | dropped if not recognized. |
	| | | recognized. |		+-------------+--------------+-------------------------------------+
	| 64512-65535 | FCFS | This range is for TLVs that can |		| 64512-65535 | FCFS | This range is for TLVs that can be |
	| | | be silently dropped if not |		| | | silently dropped if not recognized. |
	| | | recognized. |		+-------------+--------------+-------------------------------------+
	+-------------+-------------------+---------------------------------+
	Table 9: TLV Registration Procedures		Table 9: TLVs Registration Procedures
	The TLV Assignments will now look like this.		The updated assignments for this registry appear as follows:
	Note that when a field in an assignment table says "EQ", it means		Note that when a field in an assignment table says "EQ", it means
	that there is no change from the existing field in the "Multiprotocol		that there was no change from the existing field in the
	Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters"		"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
	namespace [IANA-LSP-PING]		Ping Parameters" namespace [IANA-LSP-PING].
	+-------------+---------------+-----------------+-------------------+
	| Type | TLV Name | Reference | Sub-TLV Registry |
	+-------------+---------------+-----------------+-------------------+
	| 0 | Reserved | This document | |
	| 1-7 | EQ | EQ | EQ |
	| 8 | Unassigned | | |
	| 9-16 | EQ | EQ | EQ |
	| 17-19 | unassigned | | |
	| 20-27 | EQ | EQ | EQ |
	| 28-31739 | Unassigned | | |
	| 31740-31743 | Experimental | This Document | Reserved, not to |
	| | Use | | be assigned. This |
	| | | | range is for sub- |
	| | | | TLVs that require |
	| | | | an error message |
	| | | | if not |
	| | | | recognized. [This |
	| | | | document, section |
	| | | | 3.1] |
	| 31744-32767 | Unassigned | | |
	| 32768-32770 | EQ | EQ | EQ |
	| 32771-64507 | EQ | EQ | EQ |
	| 64508-64511 | Experimental | This document | Reserved, not to |
	| | Use. | | be assigned. This |
	| | | | range is for TLVs |
	| | | | that can be |
	| | | | silently dropped |
	| | | | if not |
	| | | | recognized. |
	| 64512-65535 | Unassigned | | |
	+-------------+---------------+-----------------+-------------------+
	Table 10: TLV Assignments		+=============+==============+===========+=======================+
			| Type | TLV Name | Reference | Sub-TLV Registry |
			+=============+==============+===========+=======================+
			| 0 | Reserved | This | |
			| | | document | |
			+-------------+--------------+-----------+-----------------------+
			| 1-7 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 8 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 9-16 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 17-19 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 20-27 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 28-31739 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 31740-31743 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for |
			| | Use | | TLVs that require an |
			| | | | error message if not |
			| | | | recognized. This |
			| | | | document, Section 3.1 |
			+-------------+--------------+-----------+-----------------------+
			| 31744-32767 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 32768-32770 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 32771-64507 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 64508-64511 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for |
			| | Use | | TLVs that can be |
			| | | | silently dropped if |
			| | | | not recognized. |
			+-------------+--------------+-----------+-----------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
	6.2.2. Updates to the registry for Sub-TLVs for TLVs 1, 16 and 21		Table 10: TLV Assignments
			6.2.2. Updates to the Registry for Sub-TLVs for TLV Types 1, 16, and 21
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Types 1, 16, and 21"		assignments for the "Sub-TLVs for TLV Types 1, 16, and 21"
	[IANA-Sub-1-16-21] sub-registry based on the new registration		[IANA-Sub-1-16-21] subregistry that are based on them.
	procedures.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required", and the comment "Experimental RFC
	has been removed.		Required" has been removed.
	o The code points registration procedure "Vendor Private Use" has		* The code points registration procedure "Vendor Private Use" has
	been removed and replaced with "First Come, First Served" code		been removed and replaced with "First Come First Served"
	points.		procedure.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the		The registration procedures for the "Sub-TLVs for TLV Types 1, 16,
	"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21] sub-		and 21" [IANA-Sub-1-16-21] subregistry appear as follows after the
	registry will now look like this:		changes listed above:
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1 |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1 |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1 |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1 |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 11: Registration Procedures for Sub-TLVs for TLVs 1, 16 and 21		Table 11: Registration Procedures for Sub-TLVs for TLV Types
	+-------------+---------------+-----------------+-------------------+		1, 16, and 21
	| Type | TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+
	| 0 | Reserved | This document | |
	| 1-4 | EQ | EQ | EQ |
	| 5 | Unassigned | | |
	| 6-8 | EQ | EQ | EQ |
	| 9 | EQ | EQ | DEPRECATED |
	| 10-20 | EQ | EQ | EQ |
	| 21 | unassigned | | |
	| 22-37 | EQ | EQ | EQ |
	| 38-31739 | Unassigned | | |
	| 31740-31743 | Experimental | This Document | Reserved, not to |
	| | Use | | be assigned. This |
	| | | | range is for sub- |
	| | | | TLVs that require |
	| | | | an error message |
	| | | | if not |
	| | | | recognized. [This |
	| | | | document, section |
	| | | | 3.1] |
	| 31744-64507 | Unassigned | | |
	| 64508-64511 | Experimental | This document | Reserved, not to |
	| | Use | | be assigned. This |
	| | | | range is for TLVs |
	| | | | that can be |
	| | | | silently dropped |
	| | | | if not |
	| | | | recognized. |
	| 64512-65535 | Unassigned | | |
	+-------------+---------------+-----------------+-------------------+
	Table 12: Sub-TLV for TLV 1, 16 and 21 Assignments		+=============+==============+===========+=======================+
			| Sub-Type | Sub-TLV Name | Reference | Comment |
			+=============+==============+===========+=======================+
			| 0 | Reserved | This | |
			| | | document | |
			+-------------+--------------+-----------+-----------------------+
			| 1-4 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 5 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 6-8 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 9 | EQ | EQ | DEPRECATED |
			+-------------+--------------+-----------+-----------------------+
			| 10-20 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 21 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 22-37 | EQ | EQ | EQ |
			+-------------+--------------+-----------+-----------------------+
			| 38 | PeerAdj SID | [draft- | TEMPORARY - |
			| | Sub-TLV | ietf- | registered |
			| | | mpls-sr- | 2021-05-11, expires |
			| | | epe-oam- | 2022-05-11 |
			| | | 03] | |
			+-------------+--------------+-----------+-----------------------+
			| 39 | PeerNode SID | [draft- | TEMPORARY - |
			| | Sub-TLV | ietf- | registered |
			| | | mpls-sr- | 2021-05-11, expires |
			| | | epe-oam- | 2022-05-11 |
			| | | 03] | |
			+-------------+--------------+-----------+-----------------------+
			| 40 | PeerSet SID | [draft- | TEMPORARY - |
			| | Sub-TLV | ietf- | registered |
			| | | mpls-sr- | 2021-05-11, expires |
			| | | epe-oam- | 2022-05-11 |
			| | | 03] | |
			+-------------+--------------+-----------+-----------------------+
			| 41-31739 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 31740-31743 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for |
			| | Use | | sub-TLVs that require |
			| | | | an error message if |
			| | | | not recognized. This |
			| | | | document, Section 3.1 |
			+-------------+--------------+-----------+-----------------------+
			| 31744-64507 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
			| 64508-64511 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for |
			| | Use | | sub-TLVs that can be |
			| | | | silently dropped if |
			| | | | not recognized. |
			+-------------+--------------+-----------+-----------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
	6.2.3. Updates to the registry for Sub-TLVs for TLV 6		Table 12: Sub-TLV for TLVs 1, 16, and 21 Assignments
			6.2.3. Updates to the Registry for Sub-TLVs for TLV Type 6
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Type 6" [IANA-Sub-6] sub-		assignments for the "Sub-TLVs for TLV Type 6" [IANA-Sub-6]
	registry based on the new registration procedures.		subregistry that are based on them.
	o RFC 8611 was published after RFC 8126 and uses the new		* [RFC8611] was published after [RFC8126] and uses the new
	terminology, e.g. "Private Use". The code points registration		terminology, e.g., "Private Use". The code points registration
	procedure "Private Use" has been replaced by the "First come,		procedure "Private Use" has been replaced by the "First Come First
	First Served" code point registration proceedure.		Served" code point registration procedure.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the "Sub-TLVs for TLV Type 6"		The registration procedures for the "Sub-TLVs for TLV Type 6"
	[IANA-Sub-6] sub-registry will now look like this:		[IANA-Sub-6] subregistry after the changes listed above are shown in
			the table below:
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1 |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1 |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1 |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1 |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 13: Registration Procedures for Sub-TLVs for TLVs 6		Table 13: Registration Procedures for Sub-TLVs for TLV Type 6
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+=======================+
	| Type | TLV Name | Reference | Comment |		| Sub-Type | Sub-TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+=======================+
	| 0 | Reserved | This document | |		| 0 | Reserved | This | |
	| 1-2 | EQ | EQ | EQ |		| | | document, | |
	| 3-31739 | Unassigned | | |		| | | [RFC8611] | |
	| 31740-31743 | Experimental | This Document | Reserved, not to |		+-------------+--------------+-----------+-----------------------+
	| | Use | | be assigned. This |		| 1-2 | EQ | EQ | EQ |
	| | | | range is for sub- |		+-------------+--------------+-----------+-----------------------+
	| | | | TLVs that require |		| 3-31739 | Unassigned | | |
	| | | | an error message |		+-------------+--------------+-----------+-----------------------+
	| | | | if not |		| 31740-31743 | Reserved for | This | Not to be assigned. |
	| | | | recognized. [This |		| | Experimental | document | This range is for |
	| | | | document, section |		| | Use | | sub-TLVs that require |
	| | | | 3.1] |		| | | | an error message if |
	| 31744-64507 | Unassigned | | |		| | | | not recognized. This |
	| 64508-64511 | Experimental | This document | Reserved, not to |		| | | | document, Section 3.1 |
	| | Use. | | be assigned. This |		+-------------+--------------+-----------+-----------------------+
	| | | | range is for TLVs |		| 31744-64507 | Unassigned | | |
	| | | | that can be |		+-------------+--------------+-----------+-----------------------+
	| | | | silently dropped |		| 64508-64511 | Reserved for | This | Not to be assigned. |
	| | | | if not |		| | Experimental | document | This range is for |
	| | | | recognized. |		| | Use | | sub-TLVs that can be |
	| 64512-65535 | Unassigned | | |		| | | | silently dropped if |
	+-------------+---------------+-----------------+-------------------+		| | | | not recognized. |
			+-------------+--------------+-----------+-----------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
	Table 14: Sub-TLVs for TLV 6 Assignments		Table 14: Sub-TLVs for TLV Type 6 Assignments
	6.2.4. Updates to the registry for Sub-TLVs for TLV 11		6.2.4. Updates to the Registry for Sub-TLVs for TLV Type 11
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Type 11" [IANA-Sub-11] sub-		assignments for the "Sub-TLVs for TLV Type 11" [IANA-Sub-11]
	registry based on the new registration procedures.		subregistry that are based on them.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required", and the comment "Experimental RFC
	has been removed.		Required" has been removed.
	o The code points registration procedure "Vendor Private Use" has		* The code points registration procedure "Vendor Private Use" has
	been removed and replaced with "First Come, First Served" code		been removed and replaced with "First Come First Served" code
	points.		points.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the "Sub-TLVs for TLV Type 11"		The registration procedures for the "Sub-TLVs for TLV Type 11"
	[IANA-Sub-11] sub-registry will now look like this:		[IANA-Sub-11] subregistry after the changes listed above are shown in
			the table below:
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1 |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1 |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1 |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1 |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 15: Registration Procedures for Sub-TLVs for TLVs 11		Table 15: Registration Procedures for Sub-TLVs for TLV Type 11
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+=======================+
	| Type | TLV Name | Reference | Comment |		| Sub-Type | Sub-TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+=======================+
	| 0 | Reserved | This document | |		| 0 | Reserved | This | |
	| 1-4 | EQ | EQ | EQ |		| | | document | |
	| 5-31739 | Unassigned | | |		+-------------+--------------+-----------+-----------------------+
	| 31740-31743 | Experimental | This Document | Reserved, not to |		| 1-4 | EQ | EQ | EQ |
	| | Use | | be assigned. This |		+-------------+--------------+-----------+-----------------------+
	| | | | range is for sub- |		| 5-31739 | Unassigned | | |
	| | | | TLVs that require |		+-------------+--------------+-----------+-----------------------+
	| | | | an error message |		| 31740-31743 | Reserved for | This | Not to be assigned. |
	| | | | if not |		| | Experimental | document | This range is for |
	| | | | recognized. [This |		| | Use | | sub-TLVs that require |
	| | | | document, section |		| | | | an error message if |
	| | | | 3.1] |		| | | | not recognized. This |
	| 31744-64507 | Unassigned | | |		| | | | document, Section 3.1 |
	| 64508-64511 | Experimental | This document | Reserved, not to |		+-------------+--------------+-----------+-----------------------+
	| | Use | | be assigned. This |		| 31744-64507 | Unassigned | | |
	| | | | range is for TLVs |		+-------------+--------------+-----------+-----------------------+
	| | | | that can be |		| 64508-64511 | Reserved for | This | Not to be assigned. |
	| | | | silently dropped |		| | Experimental | document | This range is for |
	| | | | if not |		| | Use | | sub-TLVs that can be |
	| | | | recognized. |		| | | | silently dropped if |
	| 64512-65535 | Unassigned | | |		| | | | not recognized. |
	+-------------+---------------+-----------------+-------------------+		+-------------+--------------+-----------+-----------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+-----------------------+
	Table 16: Sub-TLVs for TLV 11 Assignments		Table 16: Sub-TLVs for TLV Type 11 Assignments
	6.2.5. Updates to the registry for Sub-TLVs for TLV 20		6.2.5. Updates to the Registry for Sub-TLVs for TLV Type 20
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Type 20" [IANA-Sub-20] sub-		assignments for the "Sub-TLVs for TLV Type 20" [IANA-Sub-20]
	registry based on the new registration procedures.		subregistry that are based on them.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required", and the comment "Experimental RFC
	has been removed.		Required" has been removed.
	o The code points registration procedure "Vendor Private Use" has		* The code points registration procedure "Vendor Private Use" has
	been removed and replaced with "First Come, First Served" code		been removed and replaced with "First Come First Served" code
	points.		points.
	o Two small sets, 4 code ve been created for Experimental Use.		* Two small sets, four code points each, have been created for
			Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the "Sub-TLVs for TLV Type 20"		The registration procedures for the "Sub-TLVs for TLV Type 20"
	[IANA-Sub-20] sub-registry will now look like this:		[IANA-Sub-20] subregistry after the changes listed above are shown in
			the table below:
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1] |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1] |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1] |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1] |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 17: Registration Procedures for Sub-TLVs for TLVs 20		Table 17: Registration Procedures for Sub-TLVs for TLV Type 20
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+========================+
	| Type | TLV Name | Reference | Comment |		| Sub-Type | Sub-TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+========================+
	| 0 | Reserved | This document | |		| 0 | Reserved | This | |
	| 1-5 | EQ | EQ | EQ |		| | | document | |
	| 6-31739 | Unassigned | | |		+-------------+--------------+-----------+------------------------+
	| 31740-31743 | Experimental | This Document | Reserved, not to |		| 1-5 | EQ | EQ | EQ |
	| | Use | | be assigned. This |		+-------------+--------------+-----------+------------------------+
	| | | | range is for sub- |		| 6-31739 | Unassigned | | |
	| | | | TLVs that require |		+-------------+--------------+-----------+------------------------+
	| | | | an error message |		| 31740-31743 | Reserved for | This | Not to be assigned. |
	| | | | if not |		| | Experimental | document | This range is for sub- |
	| | | | recognized. [This |		| | Use | | TLVs that require an |
	| | | | document, section |		| | | | error message if not |
	| | | | 3.1] |		| | | | recognized. This |
	| 31744-64507 | Unassigned | | |		| | | | document, Section 3.1] |
	| 64508-64511 | Experimental | This document | Reserved, not to |		+-------------+--------------+-----------+------------------------+
	| | Use | | be assigned. This |		| 31744-64507 | Unassigned | | |
	| | | | range is for TLVs |		+-------------+--------------+-----------+------------------------+
	| | | | that can be |		| 64508-64511 | Reserved for | This | Not to be assigned. |
	| | | | silently dropped |		| | Experimental | document | This range is for sub- |
	| | | | if not |		| | Use | | TLVs that can be |
	| | | | recognized. |		| | | | silently dropped if |
	| 64512-65535 | Unassigned | | |		| | | | not recognized. |
	+-------------+---------------+-----------------+-------------------+		+-------------+--------------+-----------+------------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
	Table 18: Sub-TLVs for TLV 20 Assignments		Table 18: Sub-TLVs for TLV Type 20 Assignments
	6.2.6. Updates to the registry for Sub-TLVs for TLV 23		6.2.6. Updates to the Registry for Sub-TLVs for TLV Type 23
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Type 23" [IANA-Sub-23] sub-		assignments for the "Sub-TLVs for TLV Type 23" [IANA-Sub-23]
	registry based on the new registration procedures.		subregistry that are based on them.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required", and the comment "Experimental RFC
	has been removed.		Required" has been removed.
	o The code points registration procedure "Vendor Private Use" has		* The code points registration procedure "Vendor Private Use" has
	been removed and replaced with "First Come, First Served" code		been removed and replaced with "First Come First Served" code
	points.		points.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the "Sub-TLVs for TLV Type 23"		The registration procedures for the "Sub-TLVs for TLV Type 23"
	[IANA-Sub-23] sub-registry will now look like this:		[IANA-Sub-23] subregistry after the changes listed above are shown in
			the table below:
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| Range | Registration | Note |		| Range | Registration | Note |
	| | Procedures | |		| | Procedures | |
	+-------------+-------------------+---------------------------------+		+=============+==============+==================================+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |		| 0-16383 | Standards | This range is for sub-TLVs that |
	| | | require an error message if not |		| | Action | require an error message if not |
	| | | recognized. [This document, |		| | | recognized. This document, |
	| | | section 3.1] |		| | | Section 3.1] |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | recognized. [This document, |		| | | require an error message if not |
	| | | section 3.1] |		| | | recognized. This document, |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |		| | | Section 3.1] |
	| | | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | require an error message if not |		| 31740-31743 | Reserved for | Not to be assigned. This range |
	| | | recognized. [This document, |		| | Experimental | is for sub-TLVs that require an |
	| | | section 3.1] |		| | Use | error message if not recognized. |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |		| | | This document, Section 3.1] |
	| | | require an error message if not |		+-------------+--------------+----------------------------------+
	| | | recognized. [This document, |		| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | section 3.1] |		| | | require an error message if not |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |		| | | recognized. This document, |
	| | | can be silently dropped if not |		| | | Section 3.1] |
	| | | recognized. |		+-------------+--------------+----------------------------------+
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |		| 32768-49161 | Standards | This range is for sub-TLVs that |
	| | | can be silently dropped if not |		| | Action | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |		+-------------+--------------+----------------------------------+
	| | | This range is for TLVs that can |		| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | be silently dropped if not |		| | | can be silently dropped if not |
	| | | recognized. |		| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |		+-------------+--------------+----------------------------------+
	| | | can be silently dropped if not |		| 64508-64511 | Reserved for | Not to be assigned. This range |
	| | | recognized. |		| | Experimental | is for sub-TLVs that can be |
	+-------------+-------------------+---------------------------------+		| | Use | silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	Table 19: Registration Procedures for Sub-TLVs for TLVs 23		Table 19: Registration Procedures for Sub-TLVs for TLV Type 23
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+========================+
	| Type | TLV Name | Reference | Comment |		| Sub-Type | Sub-TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+		+=============+==============+===========+========================+
	| 0 | Reserved | [RFC7555] | |		| 0 | Reserved | [RFC7555] | |
	| 1 | EQ | EQ | EQ |		+-------------+--------------+-----------+------------------------+
	| 2-31739 | Unassigned | | |		| 1 | EQ | EQ | EQ |
	| 31740-31743 | Experimental | This Document | Reserved, not to |		+-------------+--------------+-----------+------------------------+
	| | Use | | be assigned. This |		| 2-31739 | Unassigned | | |
	| | | | range is for sub- |		+-------------+--------------+-----------+------------------------+
	| | | | TLVs that require |		| 31740-31743 | Reserved for | This | Not to be assigned. |
	| | | | an error message |		| | Experimental | document | This range is for sub- |
	| | | | if not |		| | Use | | TLVs that require an |
	| | | | recognized. [This |		| | | | error message if not |
	| | | | document, section |		| | | | recognized. This |
	| | | | 3.1] |		| | | | document, Section 3.1] |
	| 31744-64507 | Unassigned | | |		+-------------+--------------+-----------+------------------------+
	| 64508-64511 | Experimental | This document | Reserved, not to |		| 31744-64507 | Unassigned | | |
	| | Use | | be assigned. This |		+-------------+--------------+-----------+------------------------+
	| | | | range is for TLVs |		| 64508-64511 | Reserved for | This | Not to be assigned. |
	| | | | that can be |		| | Experimental | document | This range is for sub- |
	| | | | silently dropped |		| | Use | | TLVs that can be |
	| | | | if not |		| | | | silently dropped if |
	| | | | recognized. |		| | | | not recognized. |
	| 64512-65535 | Unassigned | | |		+-------------+--------------+-----------+------------------------+
	+-------------+---------------+-----------------+-------------------+		| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
	Table 20: Sub-TLVs for TLV 23 Assignments		Table 20: Sub-TLVs for TLV Type 23 Assignments
	6.2.7. Updates to the registry for Sub-TLVs for TLV 27		6.2.7. Updates to the Registry for Sub-TLVs for TLV Type 27
	This section describes the new registration procedures and the		This section describes the new registration procedures and the
	assignments for the "Sub-TLVs for TLV Type 27" [IANA-Sub-27] sub-		assignments for the "Sub-TLVs for TLV Type 27" [IANA-Sub-27]
	registry based on the new registration procedures.		subregistry that are based on them.
	o The "Specification Required" registration procedure has been		* The "Specification Required" registration procedure has been
	changed to "RFC Required", the comment "Experimental RFC Required"		changed to "RFC Required", and the comment "Experimental RFC
	has been removed.		Required" has been removed.
	o The code points registration procedure "Vendor Private Use" has		* The code points registration procedure "Vendor Private Use" has
	been removed and replaced with "First Come, First Served" code		been removed and replaced with "First Come First Served" code
	points.		points.
	o Two small sets, 4 code points each, have been created for		* Two small sets, four code points each, have been created for
	Experimental Use.		Experimental Use.
	o Code points that are reserved are clearly marked as such.		* Code points that are reserved are clearly marked as such.
	o The assignments have been updated to match the new registration		* The assignments have been updated to match the new registration
	procedures.		procedures.
	o The notes related to the registration procedures have been changed		* The notes related to the registration procedures have been changed
	to reflect whether a response is required or not if a sub-TLV is		to reflect whether or not a response is required if a sub-TLV is
	not recognized.		not recognized.
	The registration procedures for the "Sub-TLVs for TLV Type 27"		The registration procedures for the "Sub-TLVs for TLV Type 27"
	[IANA-Sub-27] sub-registry will now look like this:		[IANA-Sub-27] subregistry after the changes listed above are shown in
			the table below:
	+-------------+-------------------+---------------------------------+
	| Range | Registration | Note |
	| | Procedures | |
	+-------------+-------------------+---------------------------------+
	| 0-16383 | Standards Action | This range is for sub-TLVs that |
	| | | require an error message if not |
	| | | recognized. [This document, |
	| | | section 3.1] |
	| 16384-31739 | RFC Required | This range is for sub-TLVs that |
	| | | require an error message if not |
	| | | recognized. [This document, |
	| | | section 3.1] |
	| 31740-31743 | Experimental Use | Reserved, not to be assigned. |
	| | | This range is for sub-TLVs that |
	| | | require an error message if not |
	| | | recognized. [This document, |
	| | | section 3.1] |
	| 31744-32767 | FCFS | This range is for sub-TLVs that |
	| | | require an error message if not |
	| | | recognized. [This document, |
	| | | section 3.1] |
	| 32768-49161 | Standards Action | This range is for sub-TLVs that |
	| | | can be silently dropped if not |
	| | | recognized. |
	| 49162-64507 | RFC Required | This range is for sub-TLVs that |
	| | | can be silently dropped if not |
	| | | recognized. |
	| 64508-64511 | Experimental Use | Reserved, not to be assigned. |
	| | | This range is for TLVs that can |
	| | | be silently dropped if not |
	| | | recognized. |
	| 64512-65535 | FCFS | This range is for sub-TLVs that |
	| | | can be silently dropped if not |
	| | | recognized. |
	+-------------+-------------------+---------------------------------+
	Table 21: Registration Procedures for Sub-TLVs for TLV 27
	+-------------+---------------+-----------------+-------------------+
	| Type | TLV Name | Reference | Comment |
	+-------------+---------------+-----------------+-------------------+
	| 0 | Reserved | [RFC7759] | |
	| 1-99 | Unassigned | | |
	| 100-104 | EQ | EQ | EQ |
	| 105-199 | Unassigned | | |
	| 200-202 | EQ | EQ | EQ |
	| 203-299 | Unassigned | | |
	| 300 | EQ | EQ | EQ |
	| 301-399 | Unassigned | | |
	| 400 | EQ | EQ | EQ |
	| 401-31739 | Unassigned | | |
	| 31740-31743 | Experimental | This Document | Reserved, not to |
	| | Use | | be assigned. This |
	| | | | range is for sub- |
	| | | | TLVs that require |
	| | | | an error message |
	| | | | if not |
	| | | | recognized. [This |
	| | | | document, section |
	| | | | 3.1] |
	| 31744-64507 | Unassigned | | |
	| 64508-64511 | Experimental | This document | Reserved, not to |
	| | Use | | be assigned. This |
	| | | | range is for TLVs |
	| | | | that can be |
	| | | | silently dropped |
	| | | | if not |
	| | | | recognized. |
	| 64512-65535 | Unassigned | | |
	+-------------+---------------+-----------------+-------------------+
	Table 22: Sub-TLVs for TLV 27 Assignments
	7. Acknowledgements		+=============+==============+==================================+
			| Range | Registration | Note |
			| | Procedures | |
			+=============+==============+==================================+
			| 0-16383 | Standards | This range is for sub-TLVs that |
			| | Action | require an error message if not |
			| | | recognized. This document, |
			| | | Section 3.1] |
			+-------------+--------------+----------------------------------+
			| 16384-31739 | RFC Required | This range is for sub-TLVs that |
			| | | require an error message if not |
			| | | recognized. This document, |
			| | | Section 3.1] |
			+-------------+--------------+----------------------------------+
			| 31740-31743 | Reserved for | Not to be assigned. This range |
			| | Experimental | is for sub-TLVs that require an |
			| | Use | error message if not recognized. |
			| | | This document, Section 3.1] |
			+-------------+--------------+----------------------------------+
			| 31744-32767 | FCFS | This range is for sub-TLVs that |
			| | | require an error message if not |
			| | | recognized. This document, |
			| | | Section 3.1] |
			+-------------+--------------+----------------------------------+
			| 32768-49161 | Standards | This range is for sub-TLVs that |
			| | Action | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 49162-64507 | RFC Required | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64508-64511 | Experimental | Reserved, not to be assigned. |
			| | Use | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
			| 64512-65535 | FCFS | This range is for sub-TLVs that |
			| | | can be silently dropped if not |
			| | | recognized. |
			+-------------+--------------+----------------------------------+
	The authors wish to thank Adrian Farrel, who both made very useful		Table 21: Registration Procedures for Sub-TLVs for TLV Type 27
	comments and agreed to serve as the document shepherd.
	The authors also wish to thank Michelle Cotton and Amanda Baber who		+=============+==============+===========+========================+
	very patiently worked with us to determine how our registries could		| Sub-Type | Sub-TLV Name | Reference | Comment |
	and should be updated.		+=============+==============+===========+========================+
			| 0 | Reserved | [RFC7759] | |
			+-------------+--------------+-----------+------------------------+
			| 1-99 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 100-104 | EQ | EQ | EQ |
			+-------------+--------------+-----------+------------------------+
			| 105-199 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 200-202 | EQ | EQ | EQ |
			+-------------+--------------+-----------+------------------------+
			| 203-299 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 300 | EQ | EQ | EQ |
			+-------------+--------------+-----------+------------------------+
			| 301-399 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 400 | EQ | EQ | EQ |
			+-------------+--------------+-----------+------------------------+
			| 401-31739 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 31740-31743 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for sub- |
			| | Use | | TLVs that require an |
			| | | | error message if not |
			| | | | recognized. This |
			| | | | document, Section 3.1] |
			+-------------+--------------+-----------+------------------------+
			| 31744-64507 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
			| 64508-64511 | Reserved for | This | Not to be assigned. |
			| | Experimental | document | This range is for sub- |
			| | Use | | TLVs that can be |
			| | | | silently dropped if |
			| | | | not recognized. |
			+-------------+--------------+-----------+------------------------+
			| 64512-65535 | Unassigned | | |
			+-------------+--------------+-----------+------------------------+
	The authors thanks Donald Eastlake and Tom Petch for careful and		Table 22: Sub-TLVs for TLV Type 27 Assignments
	detailed reviews.
	8. References		7. References
	8.1. Normative References		7.1. Normative References
	[IANA-LSP-PING]		[IANA-LSP-PING]
	"Multiprotocol Label Switching (MPLS) Label Switched Paths		"Multiprotocol Label Switching (MPLS) Label Switched Paths
	(LSPs) Ping Parameters",		(LSPs) Ping Parameters",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml/>.		parameters>.
	[IANA-MT] "Message Types", <https://www.iana.org/assignments/mpls-		[IANA-MT] "Message Types", <https://www.iana.org/assignments/mpls-
	lsp-ping-parameters/mpls-lsp-ping-		lsp-ping-parameters/>.
	parameters.xhtml#message-types>.
	[IANA-RC] "Return Codes", <https://www.iana.org/assignments/mpls-		[IANA-RC] "Return Codes", <https://www.iana.org/assignments/mpls-
	lsp-ping-parameters/#return-codes>.		lsp-ping-parameters/>.
	[IANA-RM] "Reply Modes", <https://www.iana.org/assignments/mpls-lsp-		[IANA-RM] "Reply Modes", <https://www.iana.org/assignments/mpls-lsp-
	ping-parameters/#reply-modes>.		ping-parameters/>.
	[IANA-Sub-1-16-21]		[IANA-Sub-1-16-21]
	"Sub-TLVs for TLV Types 1, 16, and 21",		"Sub-TLVs for TLV Types 1, 16, and 21",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-		parameters/>.
	1-16-21>.
	[IANA-Sub-11]		[IANA-Sub-11]
	"Sub-TLVs for TLV Type 11",		"Sub-TLVs for TLV Type 11",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-11>.		parameters/>.
	[IANA-Sub-20]		[IANA-Sub-20]
	"Sub-TLVs for TLV Type 20",		"Sub-TLVs for TLV Type 20",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-20>.		parameters/>.
	[IANA-Sub-23]		[IANA-Sub-23]
	"Sub-TLVs for TLV Type 23",		"Sub-TLVs for TLV Type 23",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-23>.		parameters/>.
	[IANA-Sub-27]		[IANA-Sub-27]
	"Sub-TLVs for TLV Type 27",		"Sub-TLVs for TLV Type 27",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-27>.		parameters/>.
	[IANA-Sub-6]		[IANA-Sub-6]
	"Sub-TLVs for TLV Type 6",		"Sub-TLVs for TLV Type 6",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-6>.		parameters/>.
	[IANA-TLV-reg]		[IANA-TLV-reg]
	"TLVs", <https://www.iana.org/assignments/mpls-lsp-ping-		"TLVs", <https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#tlvs>.		parameters/>.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N.,		[RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N.,
	Aldrin, S., and M. Chen, "Detecting Multiprotocol Label		Aldrin, S., and M. Chen, "Detecting Multiprotocol Label
	Switched (MPLS) Data-Plane Failures", RFC 8029,		Switched (MPLS) Data-Plane Failures", RFC 8029,
	DOI 10.17487/RFC8029, March 2017,		DOI 10.17487/RFC8029, March 2017,
	skipping to change at page 37, line 40 ¶		skipping to change at line 1739 ¶
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8611] Akiya, N., Swallow, G., Litkowski, S., Decraene, B.,		[RFC8611] Akiya, N., Swallow, G., Litkowski, S., Decraene, B.,
	Drake, J., and M. Chen, "Label Switched Path (LSP) Ping		Drake, J., and M. Chen, "Label Switched Path (LSP) Ping
	and Traceroute Multipath Support for Link Aggregation		and Traceroute Multipath Support for Link Aggregation
	Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611,		Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611,
	June 2019, <https://www.rfc-editor.org/info/rfc8611>.		June 2019, <https://www.rfc-editor.org/info/rfc8611>.
	8.2. Informative References		7.2. Informative References
	[IANA-Sub-9]		[IANA-Sub-9]
	"Sub-TLVs for TLV Type 9",		"Sub-TLVs for TLV Type 9",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml#sub-tlv-9>.		parameters/>.
	[lsp-ping-Namespace]		[lsp-ping-Namespace]
	"Multiprotocol Label Switching (MPLS) Label Switched Paths		"Multiprotocol Label Switching (MPLS) Label Switched Paths
	(LSPs) Ping Parameters",		(LSPs) Ping Parameters",
	<https://www.iana.org/assignments/mpls-lsp-ping-		<https://www.iana.org/assignments/mpls-lsp-ping-
	parameters/mpls-lsp-ping-parameters.xhtml>.		parameters/>.
	[RFC7110] Chen, M., Cao, W., Ning, S., Jounay, F., and S. Delord,		[RFC7110] Chen, M., Cao, W., Ning, S., Jounay, F., and S. Delord,
	"Return Path Specified Label Switched Path (LSP) Ping",		"Return Path Specified Label Switched Path (LSP) Ping",
	RFC 7110, DOI 10.17487/RFC7110, January 2014,		RFC 7110, DOI 10.17487/RFC7110, January 2014,
	<https://www.rfc-editor.org/info/rfc7110>.		<https://www.rfc-editor.org/info/rfc7110>.
	[RFC7555] Swallow, G., Lim, V., and S. Aldrin, "Proxy MPLS Echo		[RFC7555] Swallow, G., Lim, V., and S. Aldrin, "Proxy MPLS Echo
	Request", RFC 7555, DOI 10.17487/RFC7555, June 2015,		Request", RFC 7555, DOI 10.17487/RFC7555, June 2015,
	<https://www.rfc-editor.org/info/rfc7555>.		<https://www.rfc-editor.org/info/rfc7555>.
	skipping to change at page 38, line 33 ¶		skipping to change at line 1780 ¶
	Switched Path (LSP) Ping", RFC 7759, DOI 10.17487/RFC7759,		Switched Path (LSP) Ping", RFC 7759, DOI 10.17487/RFC7759,
	February 2016, <https://www.rfc-editor.org/info/rfc7759>.		February 2016, <https://www.rfc-editor.org/info/rfc7759>.
	[RFC8287] Kumar, N., Ed., Pignataro, C., Ed., Swallow, G., Akiya,		[RFC8287] Kumar, N., Ed., Pignataro, C., Ed., Swallow, G., Akiya,
	N., Kini, S., and M. Chen, "Label Switched Path (LSP)		N., Kini, S., and M. Chen, "Label Switched Path (LSP)
	Ping/Traceroute for Segment Routing (SR) IGP-Prefix and		Ping/Traceroute for Segment Routing (SR) IGP-Prefix and
	IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data		IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data
	Planes", RFC 8287, DOI 10.17487/RFC8287, December 2017,		Planes", RFC 8287, DOI 10.17487/RFC8287, December 2017,
	<https://www.rfc-editor.org/info/rfc8287>.		<https://www.rfc-editor.org/info/rfc8287>.
			Acknowledgements
			The authors wish to thank Adrian Farrel, who both made very useful
			comments and agreed to serve as the Document Shepherd.
			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.
			The authors thank Donald Eastlake 3rd and Tom Petch for their careful
			and detailed review.
	Authors' Addresses		Authors' Addresses
	Loa Andersson		Loa Andersson
	Bronze Dragon Consulting		Bronze Dragon Consulting
	Email: loa@pi.nu		Email: loa@pi.nu
	Mach Chen		Mach(Guoyi) Chen
	Huawei Technologies		Huawei Technologies
	Email: mach.chen@huawei.com		Email: mach.chen@huawei.com
	Carlos Pignataro		Carlos Pignataro
	Cisco Systems		Cisco Systems
	Email: cpignata@cisco.com		Email: cpignata@cisco.com
	Tarek Saad		Tarek Saad
	Juniper Networks		Juniper Networks
	Email: tsaad@juniper.net		Email: tsaad@juniper.net
End of changes. 256 change blocks.
	1109 lines changed or deleted		1273 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/