idnits 2.17.1 draft-ietf-mpls-lsp-ping-ospfv3-codepoint-04.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 27, 2021) is 1182 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-MPLS-LSP-PING' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Work group N. Nainar 3 Internet-Draft C. Pignataro 4 Updates: 8287 (if approved) Cisco Systems, Inc. 5 Intended status: Standards Track M. Aissaoui 6 Expires: July 31, 2021 Nokia 7 January 27, 2021 9 OSPFv3 CodePoint for MPLS LSP Ping 10 draft-ietf-mpls-lsp-ping-ospfv3-codepoint-04 12 Abstract 14 IANA has created "Protocol in the Segment IS Sub-TLV" and "Protocol 15 in the Label Stack Sub-TLV of the Downstream Detailed Mapping TLV" 16 registries under the "Multi-Protocol Label Switching (MPLS) Label 17 Switched Paths (LSPs) Ping Parameters" registry. RFC8287 defines the 18 code points for OSPF and IS-IS. 20 This document proposes the code point to be used in the Segment ID 21 Sub-TLV and Downstream Detailed Mapping TLV when the IGP is OSPFv3. 22 This document also updates RFC8287 by clarifying that the existing 23 "OSPF" code point is to be used only to indicate OSPFv2, and by 24 defining the behavior when the Segment ID SUb-TLV indicates the use 25 of IPv6. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on July 31, 2021. 44 Copyright Notice 46 Copyright (c) 2021 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 64 4. OSPFv3 protocol in Segment ID Sub-TLVs . . . . . . . . . . . 3 65 5. OSPFv3 protocol in Downstream Detailed Mapping TLV . . . . . 3 66 6. OSPFv2 Protocol in Segment ID and DDMAP Sub-TLVs . . . . . . 3 67 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 68 7.1. Protocol in the Segment ID sub-TLV . . . . . . . . . . . 4 69 7.2. Protocol in Label Stack Sub-TLV of Downstream Detailed 70 Mapping TLV . . . . . . . . . . . . . . . . . . . . . . . 4 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . 4 72 9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 4 73 10. Normative References . . . . . . . . . . . . . . . . . . . . 4 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 76 1. Introduction 78 IANA has created the "Protocol in the Segment IS Sub-TLV" registry 79 and "Protocol in the Label Stack Sub-TLV of the Downstream Detailed 80 Mapping TLV" registries under the "Multi-Protocol Label Switching 81 (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry 82 [IANA-MPLS-LSP-PING]. [RFC8287] defines the code points for OSPF and 83 IS-IS. 85 [RFC5340] describes OSPF version 3 (OSPFv3) to support IPv6. 86 [RFC5838] describes the mechanism to support multiple address 87 families (AFs) in OSPFv3. Accordingly, OSPFv3 may be used to 88 advertise IPv6 and IPv4 prefixes. 90 This document proposes the code point to be used in the Segment ID 91 Sub-TLV (Type 34, 35 and 36) and in the Downstream Detailed Mapping 92 (DDMAP) TLV when the IGP is OSPFv3. 94 This document also updates [RFC8287] by clarifying that the existing 95 "OSPF" code point is to be used only to indicate OSPFv2, and by 96 defining the behavior when the Segment ID Sub-TLV indicates the use 97 of IPv6. 99 2. Terminology 101 This document uses the terminology defined in [RFC8402], [RFC8029], 102 [RFC8287] and so the readers are expected to be familiar with the 103 same. 105 3. Requirements Notation 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 109 "OPTIONAL" in this document are to be interpreted as described in BCP 110 14 [RFC2119] [RFC8174] when, and only when, they appear in all 111 capitals, as shown here. 113 4. OSPFv3 protocol in Segment ID Sub-TLVs 115 When the protocol field of the Segment ID Sub-TLV of Type 34, 35 and 116 36 is set to 3, the responder MUST perform the FEC validation using 117 OSPFv3 as the IGP. 119 The initiator MUST NOT set the protocol field of the Segment ID Sub- 120 TLV Type 35 as OSPF (value 1) as OSPFv2 is not compatible with the 121 use of IPv6 addresses indicated by this Sub-TLV. 123 When the protocol field in the received Segment ID Sub-TLV Type 35 is 124 OSPF (value 1), the responder MAY treat the protocol value as "Any 125 IGP Protocol" (value 0) according to step 4a of Section 7.4 of 126 [RFC8287]. This allows the responder to support legacy 127 implementations that use value 1 to indicate OSPFv3. 129 5. OSPFv3 protocol in Downstream Detailed Mapping TLV 131 The protocol field of the Downstream Detailed Mapping (DDMAP) TLV in 132 an echo reply is set to 7 when OSPFv3 is used to distribute the label 133 carried in the Downstream Label field. 135 6. OSPFv2 Protocol in Segment ID and DDMAP Sub-TLVs 137 Section 5 of [RFC8287] defines the code point for OSPF to be used in 138 the Protocol field of the Segment ID Sub-TLV. Section 6 of [RFC8287] 139 defines the code point for OSPF to be used in the Protocol field of 140 the DDMAP TLV. 142 This document specifies that the above code points will be used only 143 for OSPFv2. 145 7. IANA Considerations 147 7.1. Protocol in the Segment ID sub-TLV 149 IANA is requested to assign a new code point from the "Protocol in 150 the Segment ID sub-TLV" registry under the "Multi-Protocol Label 151 Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" 152 registry as follows: 154 Value Meaning Reference 155 ---------- ------- ------------ 156 3 OSPFv3 This document 158 IANA is also requested to add a note for the existing entry for code 159 point 1 (OSPF) to read: - "To be used for OSPFv2 only". 161 7.2. Protocol in Label Stack Sub-TLV of Downstream Detailed Mapping TLV 163 IANA is requested to assign a new code point for OSPFv3 from 164 "Protocol in Label Stack Sub-TLV of Downstream Detailed Mapping TLV" 165 registry under the "Multi-Protocol Label Switching (MPLS) Label 166 Switched Paths (LSPs) Ping Parameters" registry as follows: 168 Value Meaning Reference 169 ---------- --------- ------------ 170 7 OSPFv3 This document 172 IANA is also requested to add a note for the existing codepoint 5 173 (OSPF) to read - "To be used for OSPFv2 only". 175 8. Security Considerations 177 This document updates [RFC8287] and does not introduce any additional 178 security considerations. 180 9. Acknowledgement 182 The authors would like to thank Les Ginsberg, Zafar Ali, Loa 183 Andersson, Andrew Molotchko, Deborah Brungard, Acee Lindem and Adrian 184 Farrel for their review and suggestions. 186 10. Normative References 188 [IANA-MPLS-LSP-PING] 189 IANA, "Multi-Protocol Label Switching (MPLS) Label 190 Switched Paths (LSPs) Ping Parameters", 191 . 194 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 195 Requirement Levels", BCP 14, RFC 2119, 196 DOI 10.17487/RFC2119, March 1997, 197 . 199 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 200 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 201 . 203 [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and 204 R. Aggarwal, "Support of Address Families in OSPFv3", 205 RFC 5838, DOI 10.17487/RFC5838, April 2010, 206 . 208 [RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N., 209 Aldrin, S., and M. Chen, "Detecting Multiprotocol Label 210 Switched (MPLS) Data-Plane Failures", RFC 8029, 211 DOI 10.17487/RFC8029, March 2017, 212 . 214 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 215 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 216 May 2017, . 218 [RFC8287] Kumar, N., Ed., Pignataro, C., Ed., Swallow, G., Akiya, 219 N., Kini, S., and M. Chen, "Label Switched Path (LSP) 220 Ping/Traceroute for Segment Routing (SR) IGP-Prefix and 221 IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data 222 Planes", RFC 8287, DOI 10.17487/RFC8287, December 2017, 223 . 225 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 226 Decraene, B., Litkowski, S., and R. Shakir, "Segment 227 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 228 July 2018, . 230 Authors' Addresses 232 Nagendra Kumar Nainar 233 Cisco Systems, Inc. 234 7200-12 Kit Creek Road 235 Research Triangle Park, NC 27709 236 US 238 Email: naikumar@cisco.com 239 Carlos Pignataro 240 Cisco Systems, Inc. 241 7200-11 Kit Creek Road 242 Research Triangle Park, NC 27709 243 US 245 Email: cpignata@cisco.com 247 Mustapha Aissaoui 248 Nokia 249 Canada 251 Email: mustapha.aissaoui@nokia.com