RFC 8029changechanged the registration procedures for TLV and sub-TLV registries for LSP Ping. IANA has created a new "Sub-TLVs for TLV Type 6" subregistry under the "TLVs" registry of the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry [IANA-MPLS-LSP-PING]. This registry conforms with RFC 8029. The registration procedures for this sub-TLV registryare.are: Range Registration Procedure Note ----- ---------------------- ----- 0-16383 Standards Action This range is for mandatory TLVs or for optional TLVs that require an error message if not recognized. 16384-31743 RFC Required This range is for mandatory TLVs or for optional TLVs that require an error message if not recognized. 31744-32767 Private Use Not to beallocatedassigned 32768-49161 Standards Action This range is for optional TLVs that can be silently dropped if not recognized. 49162-64511 RFC Required This range is for optional TLVs that can be silently dropped if not recognized. 64512-65535 Private Use Not to beallocatedassigned Thein intialinitial allocations for this registryis:are: Sub-Type Sub-TLV Name Reference Comment -------- ------------ --------- ------- 0 Reserved RFC 8611 1 Incoming Label Stack RFC 8611 2 Incoming Interface Index RFC 8611 3-31743 Unassigned 31744-32767 RFC 8611 Reserved for Private Use 32768-64511 Unassigned 64511-65535 RFC 8611 Reserved for Private Use Note: IETF does notprescribedprescribe how the PrivateUSEUse sub-TLVs arehandled, howeverhandled; however, if a sub-TLV fromthea Private Useever would berange is receivedbutby an LSR that does not recognizeitit, an error message MAY be returned if it isformfrom the range 31744-32767, and it SHOULD be silently dropped if it is from the range64511-6553564511-65535.