draft-ietf-mpls-lsp-ping-registries-update-04.txt   draft-ietf-mpls-lsp-ping-registries-update-05.txt 
MPLS Working Group L. Andersson MPLS Working Group L. Andersson
Internet-Draft Bronze Dragon Consulting Internet-Draft Bronze Dragon Consulting
Updates: 8029, 8611 (if approved) M. Chen Updates: 8029, 8611 (if approved) M. Chen
Intended status: Standards Track Huawei Techologies Intended status: Standards Track Huawei Techologies
Expires: March 28, 2021 C. Pignataro Expires: April 26, 2021 C. Pignataro
Cisco Systems Cisco Systems
T. Saad T. Saad
Juniper Networks Juniper Networks
September 24, 2020 October 23, 2020
Updating the IANA MPLS LSP Ping Parameters Updating the IANA MPLS LSP Ping Parameters
draft-ietf-mpls-lsp-ping-registries-update-04 draft-ietf-mpls-lsp-ping-registries-update-05
Abstract Abstract
This document updates RFC 8029 and RFC 8611 that both define IANA This document updates RFC 8029 and RFC 8611 that both define IANA
registries for MPLS LSP Ping. It also updates the description of the registries for MPLS LSP Ping. It also updates the description of the
procedures for the responses sent when an unknown or erroneous code procedures for the responses sent when an unknown or erroneous code
point is found. The updates are to clarify and align this name space point is found. The updates are to clarify and align this name space
with recent developments. with recent developments.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 28, 2021. This Internet-Draft will expire on April 26, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirement Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirement Language . . . . . . . . . . . . . . . . . . 4
1.2. Terminology Used in this Document . . . . . . . . . . . . 4 1.2. Terminology Used in this Document . . . . . . . . . . . . 4
2. Updating the Message Types, Reply Mode and Return Codes 2. Updating the Message Types, Reply Mode and Return Codes
Registries . . . . . . . . . . . . . . . . . . . . . . . . . 4 Registries . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Updating the TLV and Sub-TLV Registries . . . . . . . . . . . 5 3. Updating the TLV and Sub-TLV Registries . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . . . . . . . . 5 registries . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs . . . 6 3.1.1. Unrecognized Experimental Use TLVs and Sub-TLVs . . . 6
3.2. Common Registration Procedures for TLVs and sub-TLVs . . 6 3.2. Common Registration Procedures for TLVs and sub-TLVs . . 6
3.3. Changes to the LSP Ping Registries . . . . . . . . . . . 7 3.3. Changes to the LSP Ping Registries . . . . . . . . . . . 7
3.3.1. Common Changes to the TLV and Sub-TLV Registries . . 7 3.3.1. Common Changes to the TLV and Sub-TLV Registries . . 7
4. Updates to Related RFCs . . . . . . . . . . . . . . . . . . . 8 4. Updates to Related RFCs . . . . . . . . . . . . . . . . . . . 8
4.1. Updates to RFC 8029 . . . . . . . . . . . . . . . . . . . 8 4.1. Updates to RFC 8029 . . . . . . . . . . . . . . . . . . . 8
4.2. Updates to RFC 8611 . . . . . . . . . . . . . . . . . . . 9 4.2. Updates to RFC 8611 . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6.1. Updates to the Message Type, Reply Mode and Return Codes 6.1. Updates to the Message Type, Reply Mode and Return Codes
Registries . . . . . . . . . . . . . . . . . . . . . . . 11 Registries . . . . . . . . . . . . . . . . . . . . . . . 11
6.1.1. Updates to the Mesage Type registry . . . . . . . . . 11 6.1.1. Updates to the Message Type registry . . . . . . . . 11
6.1.2. Updates to the Reply Modes registry . . . . . . . . . 12 6.1.2. Updates to the Reply Modes registry . . . . . . . . . 12
6.1.3. Updates to the Return Codes registry . . . . . . . . 13 6.1.3. Updates to the Return Codes registry . . . . . . . . 13
6.2. Updates to the TLV and sub-TLV registries . . . . . . . . 16 6.2. Updates to the TLV and Sub-TLV registries . . . . . . . . 16
6.2.1. Updates to the TLVs registry . . . . . . . . . . . . 16 6.2.1. Updates to the TLVs registry . . . . . . . . . . . . 16
6.2.2. Updates to the registry for SubTLVs for TLVs 1, 16 6.2.2. Updates to the registry for SubTLVs for TLVs 1, 16
and 21 . . . . . . . . . . . . . . . . . . . . . . . 18 and 21 . . . . . . . . . . . . . . . . . . . . . . . 18
6.2.3. Updates to the registry for SubTLVs for TLV 6 . . . . 20 6.2.3. Updates to the registry for SubTLVs for TLV 6 . . . . 20
6.2.4. Updates to the registry for SubTLVs for TLV 11 . . . 22 6.2.4. Updates to the registry for SubTLVs for TLV 11 . . . 22
6.2.5. Updates to the registry for SubTLVs for TLV 20 . . . 24 6.2.5. Updates to the registry for Sub-TLVs for TLV 20 . . . 24
6.2.6. Updates to the registry for SubTLVs for TLV 23 . . . 26 6.2.6. Updates to the registry for SubTLVs for TLV 23 . . . 26
6.2.7. Updates to the registry for SubTLVs for TLV 27 . . . 28 6.2.7. Updates to the registry for SubTLVs for TLV 27 . . . 28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.1. Normative References . . . . . . . . . . . . . . . . . . 30 8.1. Normative References . . . . . . . . . . . . . . . . . . 30
8.2. Informative References . . . . . . . . . . . . . . . . . 32 8.2. Informative References . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
There were a few reasons to start the work that have led to this
document, e.g.:
o When the LSP Ping registry was created it was incorrectly assumed
that code points allocated by Experimental RFCs would be
'experimental' code points; a code point made available in a
public IANA registry is not limited by the type of RDFC that made
the allocation but is available for any document.
o The number of 'experimental' code points was also too large, as
compared to what we normally allocated for "Experimental Use".
o RFC 8029 uses the words "mandatory" and "optional" differently
from what others RFC does. RFC 8029 for example talks about
mandatory TLVs to indicate that it is mandatory to take a certain
action if the TLV is found in a message but not recognized, other
RFCs uses "mandatory TLV" to indicate a TLV that must be present
in a message.
Over time there has been attempts administratively update some of the
registries, but it was soon decided the an RFC was needed. We also
found other, often minor, potential updates, e.g. reserving the value
0 (zero) in registries there that is possible.
When RFC 8029 [RFC8029] was published it contained updates to the When RFC 8029 [RFC8029] was published it contained updates to the
"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
Ping Parameters" IANA name space [IANA-LSP-PING]. Ping Parameters" IANA name space [IANA-LSP-PING].
RFC 8611 [RFC8611] updated the LSP Ping IANA registries to match RFC RFC 8611 [RFC8611] updated the LSP Ping IANA registries to match RFC
8029. This document further clarifies the entries in those 8029. This document further clarifies the entries in those
registries and makes the definitions more precise. registries and makes the definitions more precise.
This document updates RFC 8029 [[RFC8029] and RFC 8611 [RFC8611] by This document updates RFC 8029 [[RFC8029] and RFC 8611 [RFC8611] by
updating two groups of registries as follows: updating two groups of registries as follows:
skipping to change at page 4, line 9 skipping to change at page 4, line 33
1.1. Requirement Language 1.1. Requirement 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 BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1.2. Terminology Used in this Document 1.2. Terminology Used in this Document
This docuemtment uses some terms that relates to IANA registries in This document uses some terms that relates to IANA registries in this
this way: way:
IANA Name Space, IANA Name Space,
a name space is a top level registry. An exasmple could be a name space 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 name space is most often a Ping Parameters" [IANA-LSP-PING]. A name space is most often a
contaimer for regiistries that hold code points that share some container for registries that hold code points that share some
affinity. affinity.
IANA Registry, IANA Registry,
an IANA registry holds code points, and lists the registration an IANA registry holds code points, and lists the registration
procedures and allocation of code points these code points. One procedures and allocation of code points these code points. One
example would be the "TLVs" registry [IANA-TLV-reg]. example would be the "TLVs" registry [IANA-TLV-reg].
IANA Sub-registry, IANA Sub-registry,
a sub-registry is used when a code point allocated in a registry a sub-registry is used when a code point, or a set of code points
need code points scoped by that or a set of code points. An allocated in a single registry, needs "sub-code points" scoped by
example of a sunregistry thast holds code points for more than one the code point or the set of code points. An example of a sub-
TLV is "Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21] registry that holds code points for more than one TLV is
"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21]
2. Updating the Message Types, Reply Mode and Return Codes Registries 2. Updating the Message Types, Reply Mode and Return Codes Registries
The following changes are made to the Message Types, Reply Modes and The following changes are made to the Message Types, Reply Modes and
Return Codes [IANA-MT] registries. Return Codes [IANA-MT] registries.
o In the listing of assiged code points the term "Vendor Private o In the listing of assigned code points the term "Vendor Private
Use" is changed to "Private Use". Use" is changed to "Private Use".
o The registration procedure "Specification Required" is changed to o The registration procedure "Specification Required" is changed to
"RFC Required" and the note "Experimental RFC needed" is removed. "RFC Required" and the note "Experimental RFC needed" is removed.
o A small set of code points (4 code points) for Experimental Use is o A small set of code points (4 code points) for Experimental Use is
added by reducing the range for "RFC Required" range. added by reducing the "RFC Required" range.
o The registration procedures "Private Use" and "Experimental Use" o The registration procedures "Private Use" and "Experimental Use"
are added to the table of registration procedures. are added to the table of registration procedures.
o A note "Not to be assigned" is added for the registration o A note "Not to be assigned" is added for the registration
procedures "Private Use" and "Experimental Use". procedures "Private Use" and "Experimental Use".
o In the lists that capture the assignment status, the fields that o 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 are
clearly marked as such. clearly marked as such.
* Note that in the Return Codes registry [IANA-RC] registry the * Note that in the Return Codes registry [IANA-RC] the code point
code point "0" has already been assigned. This assignment is "0" has already been assigned. This assignment is not changed
not changed and in this registry the code point "0" continues and in this registry the code point "0" continues to be
to be assigned as "No Return Code". 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 TLV and sub-TLV 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 o 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 o All TLVs and sub-TLVs in the range 32768-65535 may be silently
dropped, stepped over or an error message sennt if they are not dropped, stepped over or an error message sent if they are not
recognized. recognized.
The range of each TLV and sub-TLV registry is divided into two
blocks, one with a range from 0 to 32767 for TLVs and sub-TLVs that
require a response if not recognized. The other block has the range
from 32768 to 65535 for TLVs and sub-TLVs that may be silently
dropped, stepped over or an error message sent, if not recognized.
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. o Standards Action.
o RFC Required. o RFC Required.
o Experimental Use. o Experimental Use.
o First come, first served (FCFS). o First Come First Served (FCFS).
The exact defintions 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 Experimetal 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 o If the unrecognized TLV or sub-TLV is from the Experimental Use
range (37140-37143) or from the FCFS range (31744-32767) a the range (37140-31743) or from the FCFS range (31744-32767) a Return
Return Code of 2 ("One or more of the TLVs was not understood") Code of 2 ("One or more of the TLVs was not understood") will be
will be sent in the echo response. sent in the echo response.
o If the unrecognized TLV or sub-TLV is from the Experimental Use o If the unrecognized TLV or sub-TLV is from the Experimental Use
range (64508-64511). or from the FCFS range (64512-65535) the range (64508-64511)or from the FCFS range (64512-65535) the TLVs
TLVs may be silently ignored, stepped over or an error message may be silently ignored, stepped over or an error message sent.
sent.
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 experiment or the private network. The statement above describes the experiment or the private network. The statement above describes
how standards compliant implementations will treat the unrecognized how standards compliant implementations will treat the unrecognized
TLVs and sub- TLVs from these ranges. 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 Action | This range is for TLVs and sub- |
| | | TLVs that require an error | | | | TLVs that require an error |
| | | message if not recognized. | | | | message if not recognized. |
| 16384-31739 | RFC Required | This range is for TLVs an sub- | | | | [This document, section 3.1] |
| 16384-31739 | RFC Required | This range is for TLVs and sub- |
| | | TLVs that require an error | | | | TLVs that require an error |
| | | message if not recognized. | | | | message if not recognized. |
| 37140-37143 | Experimental Use | Reserved, not to be assigned | | | | [This document, section 3.1] |
| 31744-32767 | FCFS | This range is for TLVs anf sub- | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for TLVs and sub- |
| | | TLVs that require an error | | | | TLVs that require an error |
| | | message if not recognized. | | | | message if not recognized. |
| | | [This document, section 3.1] |
| 32768-49161 | Standards Action | This range is for TLVs and sub- | | 32768-49161 | Standards Action | This range is for TLVs and sub- |
| | | TLVs that can be silently | | | | TLVs that can be silently |
| | | dropped if not recognized. | | | | dropped if not recognized. |
| 49162-64507 | RFC Required | This range is for TLVs and sub- | | 49162-64507 | RFC Required | This range is for TLVs and sub- |
| | | TLVs that can be silently | | | | TLVs that can be silently |
| | | dropped if not recognized. | | | | dropped if not recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for TLVs and sub- | | 64512-65535 | FCFS | This range is for TLVs and sub- |
| | | TLVs that can be silently | | | | TLVs that can be silently |
| | | dropped if not recognized. | | | | dropped if not recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
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, see section 6.2.1 to 6.2.7 describe how the new versions of Registry, see section 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 Procedures description 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. Common Changes 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 Frst Served (FCFS)" and o The registration procedures "First Come First Served (FCFS)" and
"Experimental Use" are added to the table of registration "Experimental Use" are added to the table of registration
procedures. procedures.
o Two small sets of code points (4 code points each) for o Two small sets of code points (4 code points each) for
Experiemental Use, are created. The first set are for the range Experimental Use, are created. The first set is for the range
that requires a response if the TLV or sub-TLV is not recognised; that requires a response if the TLV or sub-TLV is not recognized;
the second set are for the range there the TLV or sub-TLV that may the second set is for the range there the TLV or sub-TLV that may
be silently dropped if not recognized. The code points for be silently dropped if not recognized. The code points for
experimental use are actually taken from the two ranges now called experimental use are actually taken from the two ranges now called
"RFC Required". "RFC Required".
o The registration procedure "Specification Required" is changed to o The registration procedure "Specification Required" is changed to
"RFC Required" and the note "Experimental RFC needed" is removed. "RFC Required" and the note "Experimental RFC needed" is removed.
o In the listing of assignments the term "Vendor Private Use" is o In the listing of assignments the term "Vendor Private Use" is
changed to "First Come First Served (FCFS)". changed to "First Come First Served (FCFS)".
o In the listing of assignments the range for "Experimental Use" is o In the listing of assignments the range for "Experimental Use" is
added. added.
o A note saying "Not to be assigned" is added for the registration o A note saying "Not to be assigned" is added for the registration
procedures "Experimental Use". procedures "Experimental Use".
o In the list that captures assignment status, the fields that are o 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 are 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-16383 sub-TLVs" to indicate that, if a TLV or sub-TLV of the range 0-32767
or 16384-31743 in a message is not understood, an error message needs in a message is not understood, an error message needs to be sent in
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 requires an error message in response if not understood. The that requires 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 14 and 15 in needed if a TLV or sub-TLV is not understood on pages 14 and 15 in
Section 3 of RFC 8029. Section 3 of RFC 8029.
The text in those two paragraphs are 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 the 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 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
skipping to change at page 10, line 11 skipping to change at page 10, line 14
The "Sub-TLVs for TLV Type 6" sub-registry is now updated to align The "Sub-TLVs for TLV Type 6" sub-registry 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 Action | This range is for sub-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sub-TLVs that | | 16384-31739 | RFC Required | This range is for sub-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 31740-31743 | Experimental Use | Reserved not to be assigned | | 31740-31743 | Experimental Use | Reserved not to be assigned |
| 31744-32767 | FCFS | This range is for sub-TLVs that | | 31744-32767 | FCFS | This range is for sub-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sub-TLVs that | | 32768-49161 | Standards Action | This range is for sub-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | 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. |
| 64508-64511 | Experimental Use | Reserved not to be assigned | | 64508-64511 | Experimental Use | Reserved not to be assigned |
| 64512-65535 | FCFS | This range is for sub-TLVs that | | 64512-65535 | FCFS | This range is for sub-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 1: 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
skipping to change at page 11, line 29 skipping to change at page 11, line 38
"Sub-TLVs for TLV Type 23" [IANA-Sub-23] "Sub-TLVs for TLV Type 23" [IANA-Sub-23]
"Sub-TLVs for TLV Type 27" [IANA-Sub-27] "Sub-TLVs for TLV Type 27" [IANA-Sub-27]
6.1. Updates to the Message Type, Reply Mode and Return Codes 6.1. Updates to the Message Type, Reply Mode and Return Codes
Registries 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 "Message Type", "Reply Mode" and "Return Codes"
registries. registries.
6.1.1. Updates to the Mesage Type registry 6.1.1. Updates to the Message Type registry
This is the changes to the "Message Type" registry specified in this This is the changes to the "Message Type" registry specified in this
document: document:
o Code Point 0 (zero) is marked Resereved. o Code Point 0 (zero) is marked Reserved.
o The registration procedure "Specification Required" is changed to o The registration procedure "Specification Required" is changed to
"RFC Required" and the comment "Experimental RFC needed" is "RFC Required" and the comment "Experimental RFC needed" is
removed. removed.
o Four code point has been taken from what was earlier o Four code point have been taken from what was earlier
"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 for the "Message Type"
registry are shown in the table below: registry are shown in the table below:
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | 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 | | 248-251 | Experimental Use | Reserved, not to be assigned |
| 252-255 | Private Use | Reserved, not to be assigned | | 252-255 | Private Use | Reserved, not to be assigned |
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
Table 2: Message Type registration procedures Table 3: Message Type registration procedures
The updated assignments for the "Message Types" registry will look The updated assignments for the "Message Types" registry will look
like this: like this:
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
| Value | Meaning | Reference | | Value | Meaning | Reference |
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1 | MPLS Echo Request | [RFC8029] | | 1 | MPLS Echo Request | [RFC8029] |
| 2 | MPLS Echo Reply | [RFC8029] | | 2 | MPLS Echo Reply | [RFC8029] |
| 3 | MPLS Proxy Ping Request | [RFC7555] | | 3 | MPLS Proxy Ping Request | [RFC7555] |
| 4 | MPLS Proxy Ping Reply | [RFC7555] | | 4 | MPLS Proxy Ping Reply | [RFC7555] |
| 5 | MPLS Relayed Echo Reply | [RFC7743] | | 5 | MPLS Relayed Echo Reply | [RFC7743] |
| 6-247 | Unassigned | | | 6-247 | Unassigned | |
| 248-251 | Reserved for Experimental Use | This document | | 248-251 | Reserved for Experimental Use | This document |
| 252-255 | Reserved for Private Use | [RFC8029] | | 252-255 | Reserved for Private Use | [RFC8029] |
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
Table 3: 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 This is the changes to the "Reply Modes" registry specified in this
document: document:
o Code Point 0 (zero) is marked Resereved. o Code Point 0 (zero) is marked Reserved.
o The registration procedure "Specification Required" is changed to o The registration procedure "Specification Required" is changed to
"RFC Required" and the comment "Experimental RFC needed" is "RFC Required" and the comment "Experimental RFC needed" is
removed. removed.
o Four code point has been taken from what was earlier o Four code point have been taken from what was earlier
"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 show in the table below:
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | 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 | | 248-251 | Experimental Use | Reserved, not to be assigned |
| 252-255 | Private Use | Reserved, not to be assigned | | 252-255 | Private Use | Reserved, not to be assigned |
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
Table 4: 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 will look like
this: this:
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
| Value | Meaning | Reference | | Value | Meaning | Reference |
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1 | Do not reply | [RFC8029] | | 1 | Do not reply | [RFC8029] |
| 2 | Reply via an IPv4/IPv6 UDP | [RFC8029] | | 2 | Reply via an IPv4/IPv6 UDP | [RFC8029] |
skipping to change at page 13, line 37 skipping to change at page 13, line 40
| 3 | Reply via an IPv4/IPv6 UDP | [RFC8029] | | 3 | Reply via an IPv4/IPv6 UDP | [RFC8029] |
| | packet with Router Alert | | | | packet with Router Alert | |
| 4 | Reply via application-level | [RFC8029] | | 4 | Reply via application-level | [RFC8029] |
| | control channel | | | | control channel | |
| 5 | Reply via Specified Path | [RFC7110] | | 5 | Reply via Specified Path | [RFC7110] |
| 6-247 | Unassigned | | | 6-247 | Unassigned | |
| 248-251 | Reserved for Experimental Use | This document | | 248-251 | Reserved for Experimental Use | This document |
| 252-255 | Reserved for Private Use | [RFC8029] | | 252-255 | Reserved for Private Use | [RFC8029] |
+---------+---------------------------------+-----------------------+ +---------+---------------------------------+-----------------------+
Table 5: 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
This is the changes to the "Return Codes" registry specified in this This is the changes to the "Return Codes" registry specified in this
document: document:
o The registration procedure "Specification Required" is changed to o The registration procedure "Specification Required" is changed to
"RFC Required" and the comment "Experimental RFC needed" is "RFC Required" and the comment "Experimental RFC needed" is
removed. removed.
o Four code point has been taken from what was earlier o Four code point have been taken from what was earlier
"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 show in the table below:
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | 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 | | 248-251 | Experimental Use | Reserved, not to be assigned |
| 252-255 | Private Use | Reserved, not to be assigned | | 252-255 | Private Use | Reserved, not to be assigned |
+---------+--------------------+------------------------------------+ +---------+--------------------+------------------------------------+
Table 6: 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 will look
like this: like this:
+---------+----------------------------------+----------------------+ +---------+----------------------------------+----------------------+
| Value | Meaning | Reference | | Value | Meaning | Reference |
+---------+----------------------------------+----------------------+ +---------+----------------------------------+----------------------+
| 0 | No Return Code | This document | | 0 | No Return Code | This document |
| 1 | Malformed echo request received | [RFC8029] | | 1 | Malformed echo request received | [RFC8029] |
| 2 | One or more of the TLVs was not | [RFC8029] | | 2 | One or more of the TLVs was not | [RFC8029] |
skipping to change at page 16, line 4 skipping to change at page 16, line 8
| | fault management association | | | | fault management association | |
| 34 | OAM Problem/PM Configuration | [RFC7759] | | 34 | OAM Problem/PM Configuration | [RFC7759] |
| | Error | | | | Error | |
| 35 | Mapping for this FEC is not | [RFC8287] sec 7.4 | | 35 | Mapping for this FEC is not | [RFC8287] sec 7.4 |
| | associated with the incoming | | | | associated with the incoming | |
| | interface | | | | interface | |
| 36-247 | Unassigned | [RFC7759] | | 36-247 | Unassigned | [RFC7759] |
| 248-251 | Reserved for Experimental Use | This document | | 248-251 | Reserved for Experimental Use | This document |
| 252-255 | Reserved for Private Use | [RFC8029] | | 252-255 | Reserved for Private Use | [RFC8029] |
+---------+----------------------------------+----------------------+ +---------+----------------------------------+----------------------+
Table 7: Assignments for the Return Codes registry
6.2. Updates to the TLV and sub-TLV registries Table 8: Assignments for the Return Codes registry
Notes [1] and [2] for code point 5,6 and 14 points to footnotes in
the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
Ping Parameters" name space. The footnoes are not changed by this
document.
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] has not been same, however the Sub-TLVs for TLV Type 9 [IANA-Sub-9] has not been
updated. updated.
Note that when a field in an assigment table sayds "EQ", it means Note that when a field in an assignment table says "EQ", it means
that the field should not be changed as compared to the corresponding that the field should not be changed as compared to the corresponding
field in the "Multiprotocol Label Switching (MPLS) Label Switched field in the "Multiprotocol Label Switching (MPLS) Label Switched
Paths (LSPs) Ping Parameters" name space [IANA-LSP-PING] Paths (LSPs) Ping Parameters" name space [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] based on the new
registration procedures. registration procedures.
skipping to change at page 16, line 34 skipping to change at page 16, line 44
the "TLVs" registry. the "TLVs" registry.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required or not if a TLV is not to reflect when a response is required or not 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: will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for TLVs that | | 0-16383 | Standards Action | This range is for TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 16384-31739 | RFC Required | This range is for TLVs that | | 16384-31739 | RFC Required | This range is for TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 31740-31743 | Experimental Use | Reserved, not to be assigned | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for TLVs that | | 31744-32767 | FCFS | This range is for TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| | | section 3.1] |
| 32768-49161 | Standards Action | This range is for TLVs that can | | 32768-49161 | Standards Action | This range is for TLVs that can |
| | | be silently dropped if not | | | | be 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 silently dropped if not | | | | be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for TLVs that can | | 64512-65535 | FCFS | This range is for TLVs that can |
| | | be silently dropped if not | | | | be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 8: TLV Registration Procedures Table 9: TLV Registration Procedures
The TLV Assignments will now look like this. The TLV Assignments will now look like this.
Note that when a field in this table does say "EQ", it means that if Note that when a field in this table does say "EQ", it means that it
should be the same as the registry being updtated. should be the same as the registry being updated.
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Sub-TLV Registry | | Type | TLV Name | Reference | Sub-TLV Registry |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | This document | | | 0 | Reserved | This document | |
| 1-7 | EQ | EQ | EQ | | 1-7 | EQ | EQ | EQ |
| 8 | Unassigned | | | | 8 | Unassigned | | |
| 9-16 | EQ | EQ | EQ | | 9-16 | EQ | EQ | EQ |
| 17-19 | unassigned | | | | 17-19 | unassigned | | |
| 20-27 | EQ | EQ | EQ | | 20-27 | EQ | EQ | EQ |
| 28-31739 | Unassigned | | | | 28-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-32767 | Unassigned | | | | 31744-32767 | Unassigned | | |
| 32768-32770 | EQ | EQ | EQ | | 32768-32770 | EQ | EQ | EQ |
| 32771-64507 | EQ | EQ | EQ | | 32771-64507 | EQ | EQ | EQ |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 9: TLV Assignments Table 10: TLV Assignments
6.2.2. Updates to the registry for SubTLVs for TLVs 1, 16 and 21 6.2.2. Updates to the registry for SubTLVs for TLVs 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] sub-registry based on the new registration
procedures. procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
The registration procedures for the The registration procedures for the
"Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21] sub- "Sub-TLVs for TLV Types 1, 16, and 21" [IANA-Sub-1-16-21] sub-
registry will now look like this: registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. [This document, |
| | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 32768-49161 | Standards Action | This range is for TLVs that can | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. |
| 49162-64507 | RFC Required | This range is for TLVs that can |
| | | be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for TLVs that can | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 10: Registration Procedures for Sub-TLVs for TLVs 1, 16 and 21 Table 11: Registration Procedures for Sub-TLVs for TLVs 1, 16 and 21
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+-----------------+-------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+-----------------+-------------------+
| 0 | Reserved | This document | | | 0 | Reserved | This document | |
| 1-4 | EQ | EQ | EQ | | 1-4 | EQ | EQ | EQ |
| 5 | Unassigned | | | | 5 | Unassigned | | |
| 6-8 | EQ | EQ | EQ | | 6-8 | EQ | EQ | EQ |
| 9 | EQ | EQ | DEPRECATED | | 9 | EQ | EQ | DEPRECATED |
| 9-20 | EQ | EQ | EQ | | 10-20 | EQ | EQ | EQ |
| 21 | unassigned | | | | 21 | unassigned | | |
| 22-37 | EQ | EQ | EQ | | 22-37 | EQ | EQ | EQ |
| 38-31739 | Unassigned | | | | 38-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+-----------------+-------------------+
Table 11: Sub-TLV for TLV 1, 16 and 21 Assignments Table 12: Sub-TLV for TLV 1, 16 and 21 Assignments
6.2.3. Updates to the registry for SubTLVs for TLV 6 6.2.3. Updates to the registry for SubTLVs for TLV 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] sub-
registry based on the new registration procedures. registry based on the new registration procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
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] sub-registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for Sub-TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for Sub-TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for Sub-TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 32768-49161 | Standards Action | This range is for Sub-TLVs that | | | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | This range is for Sub-TLVs that | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for Sub-TLVs that | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 12: Registration Procedures for Sub-TLVs for TLVs 6 Table 13: Registration Procedures for Sub-TLVs for TLVs 6
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | This document | | | 0 | Reserved | This document | |
| 1-2 | EQ | EQ | EQ | | 1-2 | EQ | EQ | EQ |
| 3-31739 | Unassigned | | | | 3-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 13: Sub-TLVs for TLV 6 Assignments Table 14: Sub-TLVs for TLV 6 Assignments
6.2.4. Updates to the registry for SubTLVs for TLV 11 6.2.4. Updates to the registry for SubTLVs for TLV 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] sub-
registry based on the new registration procedures. registry based on the new registration procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
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] sub-registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for Sub-TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for Sub-TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for Sub-TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 32768-49161 | Standards Action | This range is for Sub-TLVs that | | | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | This range is for Sub-TLVs that | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for Sub-TLVs that | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 14: Registration Procedures for Sub-TLVs for TLVs 11 Table 15: Registration Procedures for Sub-TLVs for TLVs 11
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | This document | | | 0 | Reserved | This document | |
| 1-4 | EQ | EQ | EQ | | 1-4 | EQ | EQ | EQ |
| 5-31739 | Unassigned | | | | 5-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 15: Sub-TLVs for TLV 11 Assignments Table 16: Sub-TLVs for TLV 11 Assignments
6.2.5. Updates to the registry for SubTLVs for TLV 20 6.2.5. Updates to the registry for Sub-TLVs for TLV 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] sub-
registry based on the new registration procedures. registry based on the new registration procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code ve been created for Experimental Use.
Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
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] sub-registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for Sub-TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for Sub-TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for Sub-TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 32768-49161 | Standards Action | This range is for Sub-TLVs that | | | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | This range is for Sub-TLVs that | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for Sub-TLVs that | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 16: Registration Procedures for Sub-TLVs for TLVs 20 Table 17: Registration Procedures for Sub-TLVs for TLVs 20
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | This document | | | 0 | Reserved | This document | |
| 1-5 | EQ | EQ | EQ | | 1-5 | EQ | EQ | EQ |
| 6-31739 | Unassigned | | | | 6-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 17: Sub-TLVs for TLV 20 Assignments Table 18: Sub-TLVs for TLV 20 Assignments
6.2.6. Updates to the registry for SubTLVs for TLV 23 6.2.6. Updates to the registry for SubTLVs for TLV 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] sub-
registry based on the new registration procedures. registry based on the new registration procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
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] sub-registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for Sub-TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for Sub-TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for Sub-TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 32768-49161 | Standards Action | This range is for Sub-TLVs that | | | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | This range is for Sub-TLVs that | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for Sub-TLVs that | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 18: Registration Procedures for Sub-TLVs for TLVs 23 Table 19: Registration Procedures for Sub-TLVs for TLVs 23
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | [RFC7555] | | | 0 | Reserved | [RFC7555] | |
| 1 | EQ | EQ | EQ | | 1 | EQ | EQ | EQ |
| 2-31739 | Unassigned | | | | 2-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 19: Sub-TLVs for TLV 23 Assignments Table 20: Sub-TLVs for TLV 23 Assignments
6.2.7. Updates to the registry for SubTLVs for TLV 27 6.2.7. Updates to the registry for SubTLVs for TLV 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] sub-
registry based on the new registration procedures. registry based on the new registration procedures.
o The "Specification Required" registration procedure has been o The "Specification Required" registration procedure has been
changed to "RFC Required", the comment "Experimental RFC Required" changed to "RFC Required", the comment "Experimental RFC Required"
has been removed. has been removed.
o The code points registration procedure "Vendor Private Use" has o 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, has been created for o Two small sets, 4 code points each, have been created for
Experimental Use. Experimental Use.
o Code points that are reserved are clearly marked as such. o Code points that are reserved are clearly marked as such.
o The assignments have been updated to match the new registration o The assignments have been updated to match the new registration
procedures. procedures.
o The notes related to the registration procedures have been changed o The notes related to the registration procedures have been changed
to reflect when a response is required if a sub-TLV is not to reflect when a response is required if a sub-TLV is not
recognized or not. recognized or not.
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] sub-registry will now look like this:
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| Range | Registration | Note | | Range | Registration | Note |
| | Procedures | | | | Procedures | |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
| 0-16383 | Standards Action | This range is for Sub-TLVs that | | 0-16383 | Standards Action | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 16384-31739 | RFC Required | This range is for Sub-TLVs that | | | | section 3.1] |
| 16384-31739 | RFC Required | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 37140-37144 | Experimental Use | Reserved, not to be assigned | | | | section 3.1] |
| 31748-32767 | FCFS | This range is for Sub-TLVs that | | 31740-31743 | Experimental Use | Reserved, not to be assigned |
| 31744-32767 | FCFS | This range is for sun-TLVs that |
| | | require an error message if not | | | | require an error message if not |
| | | recognized. | | | | recognized. [This document, |
| 32768-49161 | Standards Action | This range is for Sub-TLVs that | | | | section 3.1] |
| 32768-49161 | Standards Action | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 49162-64507 | RFC Required | This range is for Sub-TLVs that | | 49162-64507 | RFC Required | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
| 64508-64511 | Experimental Use | Reserved, not to be assigned | | 64508-64511 | Experimental Use | Reserved, not to be assigned |
| 64512-65535 | FCFS | This range is for Sub-TLVs that | | 64512-65535 | FCFS | This range is for sun-TLVs that |
| | | can be silently dropped if not | | | | can be silently dropped if not |
| | | recognized. | | | | recognized. |
+-------------+-------------------+---------------------------------+ +-------------+-------------------+---------------------------------+
Table 20: Registration Procedures for Sub-TLVs for TLV 27 Table 21: Registration Procedures for Sub-TLVs for TLV 27
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| Type | TLV Name | Reference | Comment | | Type | TLV Name | Reference | Comment |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
| 0 | Reserved | [RFC7555] | | | 0 | Reserved | [RFC7555] | |
| 1 | EQ | EQ | EQ | | 1 | EQ | EQ | EQ |
| 2-31739 | Unassigned | | | | 2-31739 | Unassigned | | |
| 31740-31743 | Experimental | This Document | Reserved, not to | | 31740-31743 | Experimental | This Document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 31744-64507 | Unassigned | | | | 31744-64507 | Unassigned | | |
| 64508-64511 | Experimental | This document | Resereved, not to | | 64508-64511 | Experimental | This document | Reserved, not to |
| | Use | | be assigned | | | Use | | be assigned |
| 64512-65535 | Unassigned | | | | 64512-65535 | Unassigned | | |
+-------------+---------------+-----------------+-------------------+ +-------------+---------------+------------------+------------------+
Table 21: Sub-TLVs for TLV 27 Assignments Table 22: Sub-TLVs for TLV 27 Assignments
7. Acknowledgements 7. Acknowledgements
The authors wish to thank Adrian Farrel, who both made very useful The authors wish to thank Adrian Farrel, who both made very useful
comments and agreed to serve as the document shepherd. comments and agreed to serve as the document shepherd.
The authors also wish to thank Micelle Cotton who very patiently The authors also wish to thank Micelle Cotton who very patiently
worked with us to determine how our registries could and should be worked with us to determine how our registries could and should be
updated. updated.
 End of changes. 124 change blocks. 
250 lines changed or deleted 300 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/