idnits 2.17.1 draft-andersson-mpls-lsp-ping-registries-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC8029, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC8611, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 23, 2019) is 1733 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group L. Andersson 3 Internet-Draft Bronze Dragon Consulting 4 Updates: 8029, 8611 (if approved) T. Saad 5 Intended status: Informational Juniper Networks 6 Expires: January 24, 2020 M. Chen 7 Huawei Techologies 8 July 23, 2019 10 Updating the LSP Ping IANA registries 11 draft-andersson-mpls-lsp-ping-registries-update-01 13 Abstract 15 This document updates some registries in the LSP Ping IANA name 16 space. The updates are mostly for clarification and to align this 17 registry with recent developments. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 24, 2020. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirement Language . . . . . . . . . . . . . . . . . . 3 55 2. Updating the Message Types, Reply Mode and Return Codes 56 Registries . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Updating the TLV and sub-TLV registries . . . . . . . . . . . 4 58 3.1. General principles the LSP Ping TLV and sub-TLV 59 registries . . . . . . . . . . . . . . . . . . . . . . . 5 60 3.2. Changes to the LSP Ping registries . . . . . . . . . . . 5 61 3.2.1. Common changes to the TLV and sub-TLV registries . . 6 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 67 7.2. Informative References . . . . . . . . . . . . . . . . . 8 68 Appendix A. New Message Type, Reply Mode and Return Codes 69 registries . . . . . . . . . . . . . . . . . . . . . 8 70 Appendix B. Common Registration Procedures for TLVs and sub-TLVs 9 71 Appendix C. IANA assignments for TLVs and sub-TLVs . . . . . . . 10 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 74 1. Introduction 76 When RFC 8029 [RFC8029] where published it contained among other 77 things updates to the "Multiprotocol Label Switching (MPLS) Label 78 Switched Paths (LSPs) Ping Parameters" IANA name space 79 [IANA-LSP-PING]. 81 The LSP Ping IANA registries were partly updated to match RFC 8029, 82 but the there were some ambiguity in the RFC, that were reflected in 83 the registries. 85 This document updates two groups of registries. 87 First the registries for Message Types [MessTypes], Reply Modes 88 [re-Mode] and Return Codes [return-codes]. The changes to these 89 registries are minor. 91 Second, this document updates the TLV and sub-TLV registries. 93 o TLVs [tlv-reg] 95 o Sub-TLVs for TLVs 1, 16 and 21 [sub-1-16-21] 96 o Sub-TLVs for TLV 6 [sub-6] 98 o Sub-TLVs for TLV 11 [sub-11] 100 o Sub-TLVs for TLV 20 [sub-20] 102 o Sub-TLVs for TLV 23 [sub-23] 104 o Sub-TLVs for TLV 27 [sub-27] 106 The registry for sub-TLVs for TLV 9 [sub-9] is not updated. 108 1.1. Requirement Language 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 112 "OPTIONAL" in this document are to be interpreted as described in BCP 113 14 [RFC2119] [RFC8174] when, and only when, they appear in all 114 capitals, as shown here. 116 2. Updating the Message Types, Reply Mode and Return Codes Registries 118 The following changes are made to the Message Types, Reply Modes and 119 Return Codes [MessTypes] registries. 121 o a small set of code points (4 code points) for experimental use is 122 added, actually they are take from the range for "Private Use". 124 o the registration procedure "Specification Required" is changed to 125 "RFC Required" and the note "Experimental RFC needed" is removed 127 o In the listing of assignments the term "Vendor Private Use" is 128 changed to "Private Use" 130 o the registration procedures "Private Use" and "Experimental Use" 131 are added to the table of registration procedures 133 o A note "Not to be assigned" is added for the registration 134 procedures "Private Use" and "Experimental Use" 136 o In the list that capture the assignment status, the fields that 137 are reserved, i.e. 0, Private Use and Experimental Use are 138 clearly marked. 140 * In the Return Codes [return-codes] registry the code point "0" 141 already been assigned. This assignment is not changed and this 142 registry will not have the "0" value "Reserved". 144 The new Registration Procedures layout and the new assignments for 145 these registries will be found in Appendix A. 147 3. Updating the TLV and sub-TLV registries 149 When a new LSP Ping sub-TLV registry were created by RFC 8611 150 [RFC8611] this registry "Sub-TLVs for TLV Type 6" [sub-6] was set up 151 following the intentions of RFC 8029. 153 The registry for "Sub-TLVs for TLV Type 6" will serve as a model to 154 change/update the rest of the TLV and sub-TLV registries in this name 155 space. 157 The registration procedures in the current registry for "Sub-TLVs for 158 TLV Type 6" looks like this (2019-06-20). This will be used as a 159 base-line and some additions/changes will be made as captured in the 160 Appendixes: 162 +-------------+-------------------+---------------------------------+ 163 | Range | Registration | Note | 164 | | Procedures | | 165 +-------------+-------------------+---------------------------------+ 166 | 0-16383 | Standards Action | This range is for mandatory | 167 | | | TLVs or for optional TLVs that | 168 | | | require an error message if not | 169 | | | recognized. | 170 | 16384-31743 | RFC Required | This range is for mandatory | 171 | | | TLVs or for optional TLVs that | 172 | | | require an error message if not | 173 | | | recognized. | 174 | 31744-32767 | Private Use | Not to be assigned | 175 | 32768-49161 | Standards Action | This range is for optional TLVs | 176 | | | that can be silently dropped if | 177 | | | not recognized. | 178 | 49162-64511 | RFC Required | This range is for optional TLVs | 179 | | | that can be silently dropped if | 180 | | | not recognized. | 181 | 64512-65535 | Private Use | Not to be assigned | 182 +-------------+-------------------+---------------------------------+ 184 Sub-TLVs for TLV Type 6 Registration Procedures 186 This document adds small ranges of code points for Experimental Use 187 to this registry and to registries listed in Appendix B. 189 All registries will be changed to reflect the same model. 191 3.1. General principles the LSP Ping TLV and sub-TLV registries 193 The following principles are valid for all the LSP Ping TLV and sub- 194 TLV IANA registries 196 o all mandatory TLVs and sub-TLVs requires a response if the are not 197 recognized 199 o some optional TLVs and sub-TLVs requires a response if the are not 200 recognized 202 o some optional TLVs and sub-TLVs may be silently dropped if the are 203 not recognized 205 The range of each TLV and sub-TLV registry is divided into to blocks, 206 one with a range from 0 to 49161 for TLVs and sub-TLVs that require a 207 response if not recognized. Another block in the range from 49161 to 208 65535, this block is for TLVs and sub-TLVs that may be silently 209 dropped if not recognized. 211 Each of the blocks have code point spaces with the following 212 registration procedures: 214 o Standards Action 216 o RFC Required 218 o Experimental Use 220 o Private Use 222 The exact defintion of registration procedures for IANA registries 223 are found in [RFC8126] 225 IETF does not prescribe how the Experimental Use and Private Use sub- 226 TLVs are handled; however, if a packet containing a sub-TLV from the 227 Experimental Use or Private Use ranges is received by an LSR that 228 does not recognize the sub-TLV, an error message MAY be returned if 229 the sub-TLV is from the range 31744-32767, and the packet SHOULD be 230 silently dropped if it is from the range 64512-65535. 232 3.2. Changes to the LSP Ping registries 234 This section lists the changes to each LSP Ping Registry, in 235 appendixes it is shown what the IANA registry version of the 236 registration procedures and assignments would look like. 238 3.2.1. Common changes to the TLV and sub-TLV registries 240 The following changes are made to the TLV and sub-TLV registries. 242 o two small set of code points (2 times 4 code points) for 243 experimental use is added, actually they are take from the range 244 for "Private Use". 246 o the registration procedure "Specification Required" is changed to 247 "RFC Required" and the note "Experimental RFC needed" is removed 249 o In the listing of assignements the term "Vendor Private Use" is 250 changed to "Private Use" 252 o In the listing of assignments the range for "Experimental Use" is 253 added 255 o the registration procedures "Private Use" and "Experimental Use" 256 are added to the table of registration procedures 258 o A note "Not to be assigned" is added for the registration 259 procedures "Experimental Use" and "Private Use" 261 o In the list that capture assignment status, the fields that are 262 reserved, i.e. 0, Experimental Use and Private Use are clearly 263 marked. 265 The new Registration Procedures description and the new assignments 266 for these registries will be found in Appendix B and Appendix C. 268 4. Security Considerations 270 TBA 272 5. IANA Considerations 274 IANA is requested to update the LSP Ping name space as described in 275 this document and documented in the Appendixies. 277 6. Acknowledgements 279 TBA 281 7. References 282 7.1. Normative References 284 [IANA-LSP-PING] 285 "Multiprotocol Label Switching (MPLS) Label Switched Paths 286 (LSPs) Ping Parameters", 287 . 290 [MessTypes] 291 "Message Types", . 295 [re-Mode] "Message Types", . 299 [return-codes] 300 "Return Codes", . 304 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 305 Requirement Levels", BCP 14, RFC 2119, 306 DOI 10.17487/RFC2119, March 1997, 307 . 309 [RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N., 310 Aldrin, S., and M. Chen, "Detecting Multiprotocol Label 311 Switched (MPLS) Data-Plane Failures", RFC 8029, 312 DOI 10.17487/RFC8029, March 2017, 313 . 315 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 316 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 317 May 2017, . 319 [RFC8611] Akiya, N., Swallow, G., Litkowski, S., Decraene, B., 320 Drake, J., and M. Chen, "Label Switched Path (LSP) Ping 321 and Traceroute Multipath Support for Link Aggregation 322 Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611, 323 June 2019, . 325 [sub-1-16-21] 326 "Sub-TLVs for TLV Types 1, 16, and 21", 327 . 331 [sub-11] "Sub-TLVs for TLV Type 11", 332 . 336 [sub-20] "Sub-TLVs for TLV Type 20", 337 . 341 [sub-23] "Sub-TLVs for TLV Type 23", 342 . 346 [sub-27] "Sub-TLVs for TLV Type 27", 347 . 351 [sub-6] "Sub-TLVs for TLV Type 6", 352 . 356 [tlv-reg] "TLVs", . 359 7.2. Informative References 361 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 362 Writing an IANA Considerations Section in RFCs", BCP 26, 363 RFC 8126, DOI 10.17487/RFC8126, June 2017, 364 . 366 [sub-9] "Sub-TLVs for TLV Type 9", 367 . 371 Appendix A. New Message Type, Reply Mode and Return Codes registries 373 This appendix defines the updated registration procedures for Message 374 Type, Reply Mode and Return Codes registries. 376 +---------+--------------------+------------------------------------+ 377 | Range | Registration | Note | 378 | | Procedures | | 379 +---------+--------------------+------------------------------------+ 380 | 0-191 | Standards Action | | 381 | 192-247 | RFC Required | | 382 | 248-251 | Experimental Use | Not to be assigned | 383 | 252-255 | Private Use | Not to be assigned | 384 +---------+--------------------+------------------------------------+ 386 New common registration procedures 388 +---------+---------------------------------+-----------------------+ 389 | Value | Meaning | Reference | 390 +---------+---------------------------------+-----------------------+ 391 | 0 | Reserved | This document | 392 | 1-247 | No changes to the existing | | 393 | | assignments | | 394 | 248-251 | Reserved for Experimental Use | This document | 395 | 252-255 | Reserved for Private Use | [RFC8029] | 396 +---------+---------------------------------+-----------------------+ 398 Common Assignments for the Message Types, Reply Mode and Return Code 399 registries 401 Note that for the Return Code registry the assignment for code point 402 zero has been previously assigned, it is not changed but will remain: 404 +-------+----------------------------------+------------------------+ 405 | Value | Meaning | Reference | 406 +-------+----------------------------------+------------------------+ 407 | 0 | No return code | [RFC8029] | 408 +-------+----------------------------------+------------------------+ 410 Assignment for code point 0 in the Return Code registry 412 Appendix B. Common Registration Procedures for TLVs and sub-TLVs 414 This appendix describes the new registration procedures for the TLV 415 and sub-TLV registries. The registry for sub-TLV 9 ([sub-9] is not 416 changed. 418 +-------------+-------------------+---------------------------------+ 419 | Range | Registration | Note | 420 | | Procedures | | 421 +-------------+-------------------+---------------------------------+ 422 | 0-16383 | Standards Action | This range is for mandatory | 423 | | | TLVs or for optional TLVs that | 424 | | | require an error message if not | 425 | | | recognized. | 426 | 16384-31743 | RFC Required | This range is for mandatory | 427 | | | TLVs or for optional TLVs that | 428 | | | require an error message if not | 429 | | | recognized. | 430 | 37144-37147 | Experimental Use | Not to be assigned | 431 | 31748-32767 | Private Use | Not to be assigned | 432 | 32768-49161 | Standards Action | This range is for optional TLVs | 433 | | | that can be silently dropped if | 434 | | | not recognized. | 435 | 49162-64511 | RFC Required | This range is for optional TLVs | 436 | | | that can be silently dropped if | 437 | | | not recognized. | 438 | 64512-64515 | Experimental Use | Not to be assigned | 439 | 64515-65535 | Private Use | Not to be assigned | 440 +-------------+-------------------+---------------------------------+ 442 TLV and sub-TLV Registration Procedures 444 Appendix C. IANA assignments for TLVs and sub-TLVs 446 The two tables in this appendix describes the updated IANA 447 assignments for the TLV and sub-TLV registries. The registry for 448 sub-TLV 9 ([sub-9] is not changed. 450 +-------------+-------------------+------------------+--------------+ 451 | Type | TLV name | Reference | sub-TLV | 452 | | | | registry | 453 +-------------+-------------------+------------------+--------------+ 454 | 0 | Reserved | This document | | 455 | 1-31743 | [any] | No changes to | [any] | 456 | | | the current | | 457 | | | registry | | 458 | 37144-37147 | Reserved for | This document | NA | 459 | | Experimental Use | | | 460 | 31748-32767 | Reserved for | This document | NA | 461 | | Private Use | | | 462 | 32768-64511 | [any] | No changes to | [any] | 463 | | | the current | | 464 | | | registry. | | 465 | 64512-64515 | Reserved for | This document | NA | 466 | | Experimental Use | | | 467 | 64515-65535 | Reserved for | This document | NA | 468 | | Private Use | | | 469 +-------------+-------------------+------------------+--------------+ 471 TLV Assignments 473 Updated Sub-TLV assignments 475 +-------------+-------------------------------+---------------------+ 476 | Type | TLV name | Reference | 477 +-------------+-------------------------------+---------------------+ 478 | 0 | Reserved | This document | 479 | 1-31743 | [any] | No changes to the | 480 | | | current registry | 481 | 37144-37147 | Reserved for Experimental Use | This document | 482 | 31748-32767 | Reserved for Private Use | This document | 483 | 32768-64511 | [any] | No changes to the | 484 | | | current registry. | 485 | 64512-64515 | Reserved for Experimental Use | This document | 486 | 64515-65535 | Reserved for Private Use | This document | 487 +-------------+-------------------------------+---------------------+ 489 Sub-TLV Assignments 491 Authors' Addresses 493 Loa Andersson 494 Bronze Dragon Consulting 496 Email: loa@pi.nu 497 Tarek Saad 498 Juniper Networks 500 Email: tsaad.net@gmail.com 502 Mach Chen 503 Huawei Techologies 505 Email: mach.chen@huawei.com