idnits 2.17.1 draft-andersson-mpls-lsp-ping-registries-update-00.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 7, 2019) is 1754 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 8, 2020 July 7, 2019 8 Updating the LSP Ping IANA registries 9 draft-andersson-mpls-lsp-ping-registries-update-00 11 Abstract 13 This document updates some registries in the LSP Ping IANA name 14 space. The updates are mostly for clarification and to align this 15 registry with recent developments. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on January 8, 2020. 34 Copyright Notice 36 Copyright (c) 2019 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Requirement Language . . . . . . . . . . . . . . . . . . 3 53 2. Updating the Message Types, Reply Mode and Return Codes 54 Registries . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Updating the TLV and sub-TLV registries . . . . . . . . . . . 4 56 3.1. General principles the LSP Ping TLV and sub-TLV 57 registries . . . . . . . . . . . . . . . . . . . . . . . 5 58 3.2. Changes to the LSP Ping registries . . . . . . . . . . . 5 59 3.2.1. Common changes to the TLV and sub-TLV registries . . 6 60 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 61 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 62 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 63 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 65 7.2. Informative References . . . . . . . . . . . . . . . . . 8 66 Appendix A. New Message Type, Reply Mode and Return Codes 67 registries . . . . . . . . . . . . . . . . . . . . . 9 68 Appendix B. Common Registration Procedures for TLVs and sub-TLVs 9 69 Appendix C. IANA assignments for TLVs and sub-TLVs . . . . . . . 10 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 72 1. Introduction 74 When RFC 8029 [RFC8029] where published it contained among other 75 things updates to the "Multiprotocol Label Switching (MPLS) Label 76 Switched Paths (LSPs) Ping Parameters" IANA name space 77 [IANA-LSP-PING]. 79 The LSP Ping IANA registries were partly updated to match RFC 8029, 80 but the there were some ambiguity in the RFC, that were reflected in 81 the registries. 83 This document updates two groups of registries. 85 First the registries for Message Types [MessTypes], Reply Modes 86 [re-Mode] and Return Codes [return-codes]. The changes to these 87 registries are minor. 89 Second, this document updates the TLV and sub-TLV registries. 91 o TLVs [tlv-reg] 93 o Sub-TLVs for TLVs 1, 16 and 21 [sub-1-16-21] 95 o Sub-TLVs for TLV 6 [sub-6] 96 o Sub-TLVs for TLV 11 [sub-11] 98 o Sub-TLVs for TLV 20 [sub-20] 100 o Sub-TLVs for TLV 23 [sub-23] 102 o Sub-TLVs for TLV 27 [sub-27] 104 The registry for sub-TLVs for TLV 9 [sub-9] is not updated. 106 1.1. Requirement Language 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 110 "OPTIONAL" in this document are to be interpreted as described in BCP 111 14 [RFC2119] [RFC8174] when, and only when, they appear in all 112 capitals, as shown here. 114 2. Updating the Message Types, Reply Mode and Return Codes Registries 116 The following changes are made to the Message Types, Reply Modes and 117 Return Codes [MessTypes] registries. 119 o a small set of code points (4 code points) for experimental use is 120 added, actually they are take from the range for "Private Use". 122 o the registration procedure "Specification Required" is changed to 123 "RFC Required" and the note "Experimental RFC needed" is removed 125 o In the listing of assignments the term "Vendor Specific Use" is 126 changed to "Private use" 128 o the registration procedures "Private Use" and "Experimental Use" 129 are added to the table of registration procedures 131 o A note "Not to be assigned" is added for the registration 132 procedures "Private Use" and "Experimental Use" 134 o In the list that capture nment status, the fields that are 135 reserved, i.e. 0, Private Use and Experimental Use are clearly 136 marked. 138 * In the Return Codes [return-codes] registry the code point "0" 139 already been assigned. This assignment is not changed and this 140 registry will not havethe "0" value "Reserved". 142 The new Registration Procedures layout and the new assignments for 143 these registries will be found in Appendix A. 145 3. Updating the TLV and sub-TLV registries 147 When a new LSP Ping sub-TLV registry were created by RFC 8611 148 [RFC8611] this registry "Sub-TLVs for TLV Type 6" [sub-6] was set up 149 following the intentions of RFC 8029. 151 The registry for "Sub-TLVs for TLV Type 6" will serve as a model to 152 change/update the rest of the TLV and sub-TLV registries in this name 153 space. 155 The registration procedures in the current registry for "Sub-TLVs for 156 TLV Type 6" looks like this (2019-06-20). This will be used as a 157 base-line and some additions/changes will be made as captured in the 158 Appendixes: 160 +-------------+-------------------+---------------------------------+ 161 | Range | Registration | Note | 162 | | Procedures | | 163 +-------------+-------------------+---------------------------------+ 164 | 0-16383 | Standards Action | This range is for mandatory | 165 | | | TLVs or for optional TLVs that | 166 | | | require an error message if not | 167 | | | recognized. | 168 | 16384-31743 | RFC Required | This range is for mandatory | 169 | | | TLVs or for optional TLVs that | 170 | | | require an error message if not | 171 | | | recognized. | 172 | 31744-32767 | Private Use | Not to be assigned | 173 | 32768-49161 | Standards Action | This range is for optional TLVs | 174 | | | that can be silently dropped if | 175 | | | not recognized. | 176 | 49162-64511 | RFC Required | This range is for optional TLVs | 177 | | | that can be silently dropped if | 178 | | | not recognized. | 179 | 64512-65535 | Private Use | Not to be assigned | 180 +-------------+-------------------+---------------------------------+ 182 Sub-TLVs for TLV Type 6 Registration Procedures 184 This document adds small ranges of code points for Experimental Use 185 to this registry and to registries listed in Appendix B. 187 All registries will be changed to reflect the same model. 189 3.1. General principles the LSP Ping TLV and sub-TLV registries 191 The following principles are valid for all the LSP Ping TLV and sub- 192 TLV IANA registries 194 o all mandatory TLVs and sub-TLVs requires a response if the are not 195 recognized 197 o some optional TLVs and sub-TLVs requires a response if the are not 198 recognized 200 o some optional TLVs and sub-TLVs may be silently dropped if the are 201 not recognized 203 The range of each TLV and sub-TLV registry is divided into to blocks, 204 one with a range from 0 to 49161 for TLVs and sub-TLVs that require a 205 response if not recognized. Another block in the range from 49161 to 206 65535, this block is for TLVs and sub-TLVs that may be silently 207 dropped if not recognized. 209 Each of the blocks have code point spaces with the following 210 registration procedures: 212 o Standards Action 214 o RFC Required 216 o Experimental Use 218 o Private Use 220 The exact defintion of registration procedures for IANA registries 221 are found in [RFC8126] 223 IETF does not prescribe how the Experimental Use and Private Use sub- 224 TLVs are handled; however, if a packet containing a sub-TLV from the 225 Experimental Use or Private Use ranges is received by an LSR that 226 does not recognize the sub-TLV, an error message MAY be returned if 227 the sub-TLV is from the range 31744-32767, and the packet SHOULD be 228 silently dropped if it is from the range 64512-65535. 230 3.2. Changes to the LSP Ping registries 232 This section lists the changes to each LSP Ping Registry, in 233 appendixes it is shown what the IANA registry version of the 234 registration procedures and assignments would look like. 236 3.2.1. Common changes to the TLV and sub-TLV registries 238 The following changes are made to the TLV and sub-TLV registries. 240 o two small set of code points (2 times 4 code points) for 241 experimental use is added, actually they are take from the range 242 for "Private Use". 244 o the registration procedure "Specification Required" is changed to 245 "RFC Required" and the note "Experimental RFC needed" is removed 247 o In the listing of assignements the term "Vendor Specific Use" is 248 changed to "Private use" 250 o In the listing of assignments the range for "Experimental Use" is 251 added 253 o the registration procedures "Private Use" and "Experimental Use" 254 are added to the table of registration procedures 256 o A note "Not to be assigned" is added for the registration 257 procedures "Experimental Use" and "Private Use" 259 o In the list that capture assignment status, the fields that are 260 reserved, i.e. 0, Experimental Use and Private Use are clearly 261 marked. 263 The new Registration Procedures description and the new assignments 264 for these registries will be found in Appendix B and Appendix C. 266 4. Security Considerations 268 TBA 270 5. IANA Considerations 272 There are no requests for IANA actions in this document. 274 This is obviously not true, the entire document is an IANA 275 Consideration section,but we need some help how to write the IANA 276 section in this type of document. 278 Maybe we could just say, IANA is requested to update the LSP Ping 279 name space as described in this document. 281 6. Acknowledgements 283 TBA 285 7. References 287 7.1. Normative References 289 [IANA-LSP-PING] 290 "Multiprotocol Label Switching (MPLS) Label Switched Paths 291 (LSPs) Ping Parameters", 292 . 295 [MessTypes] 296 "Message Types", . 300 [re-Mode] "Message Types", . 304 [return-codes] 305 "Return Codes", . 309 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 310 Requirement Levels", BCP 14, RFC 2119, 311 DOI 10.17487/RFC2119, March 1997, 312 . 314 [RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N., 315 Aldrin, S., and M. Chen, "Detecting Multiprotocol Label 316 Switched (MPLS) Data-Plane Failures", RFC 8029, 317 DOI 10.17487/RFC8029, March 2017, 318 . 320 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 321 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 322 May 2017, . 324 [RFC8611] Akiya, N., Swallow, G., Litkowski, S., Decraene, B., 325 Drake, J., and M. Chen, "Label Switched Path (LSP) Ping 326 and Traceroute Multipath Support for Link Aggregation 327 Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611, 328 June 2019, . 330 [sub-1-16-21] 331 "Sub-TLVs for TLV Types 1, 16, and 21", 332 . 336 [sub-11] "Sub-TLVs for TLV Type 11", 337 . 341 [sub-20] "Sub-TLVs for TLV Type 20", 342 . 346 [sub-23] "Sub-TLVs for TLV Type 23", 347 . 351 [sub-27] "Sub-TLVs for TLV Type 27", 352 . 356 [sub-6] "Sub-TLVs for TLV Type 6", 357 . 361 [tlv-reg] "TLVs", . 364 7.2. Informative References 366 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 367 Writing an IANA Considerations Section in RFCs", BCP 26, 368 RFC 8126, DOI 10.17487/RFC8126, June 2017, 369 . 371 [sub-9] "Sub-TLVs for TLV Type 9", 372 . 376 Appendix A. New Message Type, Reply Mode and Return Codes registries 378 This appendix defines the updated registration procedures for Message 379 Type, Reply Mode and Return Codes registries. 381 +---------+--------------------+------------------------------------+ 382 | Range | Registration | Note | 383 | | Procedures | | 384 +---------+--------------------+------------------------------------+ 385 | 0-191 | Standards Action | | 386 | 192-247 | RFC Required | | 387 | 248-251 | Experimental Use | Not to be assigned | 388 | 252-255 | Private Use | Not to be assigned | 389 +---------+--------------------+------------------------------------+ 391 New common registration procedures 393 +---------+---------------------------------+-----------------------+ 394 | Value | Meaning | Reference | 395 +---------+---------------------------------+-----------------------+ 396 | 0 | Reserved | This document | 397 | 1-247 | No changes to the existing | | 398 | | assignments | | 399 | 248-251 | Reserved for Experimental Use | This document | 400 | 252-255 | Reserved for Private Use | [RFC8029] | 401 +---------+---------------------------------+-----------------------+ 403 Common Assignments for the Message Types, Reply Mode and Return Code 404 registries 406 Note that for the Return Code registry the assignment for code point 407 zero has been previously assigned, it is not changed but will remain: 409 +-------+----------------------------------+------------------------+ 410 | Value | Meaning | Reference | 411 +-------+----------------------------------+------------------------+ 412 | 0 | No return code | [RFC8029] | 413 +-------+----------------------------------+------------------------+ 415 Assignment for code point 0 in the Return Code registry 417 Appendix B. Common Registration Procedures for TLVs and sub-TLVs 419 This appendix describes the new registration procedures for the TLV 420 and sub-TLV registries. The registry for sub-TLV 9 ([sub-9] is not 421 changed. 423 +-------------+-------------------+---------------------------------+ 424 | Range | Registration | Note | 425 | | Procedures | | 426 +-------------+-------------------+---------------------------------+ 427 | 0-16383 | Standards Action | This range is for mandatory | 428 | | | TLVs or for optional TLVs that | 429 | | | require an error message if not | 430 | | | recognized. | 431 | 16384-31743 | RFC Required | This range is for mandatory | 432 | | | TLVs or for optional TLVs that | 433 | | | require an error message if not | 434 | | | recognized. | 435 | 37144-37147 | Experimental Use | Not to be assigned | 436 | 31748-32767 | Private Use | Not to be assigned | 437 | 32768-49161 | Standards Action | This range is for optional TLVs | 438 | | | that can be silently dropped if | 439 | | | not recognized. | 440 | 49162-64511 | RFC Required | This range is for optional TLVs | 441 | | | that can be silently dropped if | 442 | | | not recognized. | 443 | 64512-64515 | Experimental Use | Not to be assigned | 444 | 64515-65535 | Private Use | Not to be assigned | 445 +-------------+-------------------+---------------------------------+ 447 TLV and sub-TLV Registration Procedures 449 Appendix C. IANA assignments for TLVs and sub-TLVs 451 The two tables in this appendix describes the updated IANA 452 assignments for the TLV and sub-TLV registries. The registry for 453 sub-TLV 9 ([sub-9] is not changed. 455 +-------------+-------------------+------------------+--------------+ 456 | Type | TLV name | Reference | sub-TLV | 457 | | | | registry | 458 +-------------+-------------------+------------------+--------------+ 459 | 0 | Reserved | This document | | 460 | 1-31743 | [any] | No changes to | [any] | 461 | | | the current | | 462 | | | registry | | 463 | 37144-37147 | Reserved for | This document | NA | 464 | | Experimental Use | | | 465 | 31748-32767 | Reserved for | This document | NA | 466 | | Private Use | | | 467 | 32768-64511 | [any] | No changes to | [any] | 468 | | | the current | | 469 | | | registry. | | 470 | 64512-64515 | Reserved for | This document | NA | 471 | | Experimental Use | | | 472 | 64515-65535 | Reserved for | This document | NA | 473 | | Private Use | | | 474 +-------------+-------------------+------------------+--------------+ 476 TLV Assignments 478 Updated Sub-TLV assignments 480 +-------------+-------------------------------+---------------------+ 481 | Type | TLV name | Reference | 482 +-------------+-------------------------------+---------------------+ 483 | 0 | Reserved | This document | 484 | 1-31743 | [any] | No changes to the | 485 | | | current registry | 486 | 37144-37147 | Reserved for Experimental Use | This document | 487 | 31748-32767 | Reserved for Private Use | This document | 488 | 32768-64511 | [any] | No changes to the | 489 | | | current registry. | 490 | 64512-64515 | Reserved for Experimental Use | This document | 491 | 64515-65535 | Reserved for Private Use | This document | 492 +-------------+-------------------------------+---------------------+ 494 Sub-TLV Assignments 496 Authors' Addresses 498 Loa Andersson 499 Bronze Dragon Consulting 501 Email: loa@pi.nu 502 Tarek Saad 503 Juniper Networks 505 Email: tsaad.net@gmail.com