<?xml version="1.0"encoding="US-ASCII"?>encoding="UTF-8"?> <!DOCTYPE rfcSYSTEM "rfc2629.dtd"> <?rfc toc="yes"?> <?rfc tocompact="yes"?> <?rfc tocdepth="3"?> <?rfc tocindent="yes"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes"?> <?rfc comments="yes"?> <?rfc inline="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?>[ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]> <rfccategory='std' ipr='trust200902' docName='draft-ietf-mpls-lsp-ping-ospfv3-codepoint-06' updates="8287">xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-mpls-lsp-ping-ospfv3-codepoint-06" number="9214" updates="8287" obsoletes="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.12.0 --> <front><title abbrev="OSPFv3<title>OSPFv3 Code Point for MPLS LSPPing">OSPFv3 CodePoint for MPLS LSPPing</title> <seriesInfo name="RFC" value="9214"/> <author initials="N." surname="Nainar" fullname="Nagendra Kumar Nainar"> <organization>Cisco Systems, Inc.</organization> <address> <postal> <street>7200-12 Kit Creek Road</street> <city>Research Triangle Park</city> <region>NC</region> <code>27709</code><country>US</country><country>United States of America</country> </postal> <email>naikumar@cisco.com</email> </address> </author> <author initials="C." surname="Pignataro" fullname="Carlos Pignataro"> <organization>Cisco Systems, Inc.</organization> <address> <postal> <street>7200-11 Kit Creek Road</street> <city>Research Triangle Park</city> <region>NC</region> <code>27709</code><country>US</country><country>United States of America</country> </postal> <email>cpignata@cisco.com</email> </address> </author> <author initials="M." surname="Aissaoui" fullname="Mustapha Aissaoui"> <organization>Nokia</organization> <address> <postal><street></street> <city></city> <region></region> <code></code><street/> <city/> <region/> <code/> <country>Canada</country> </postal> <email>mustapha.aissaoui@nokia.com</email> </address> </author> <date month="March" year="2022" /> <area>Internet</area><workgroup>Network Work group</workgroup> <keyword>mpls</keyword> <abstract><t>IANA<workgroup>MPLS</workgroup> <keyword>MPLS</keyword> <abstract> <!-- [rfced] FYI, we have capitalized "sub-TLV" in the title of the "Protocol in the Segment ID Sub-TLV" registry, and we will ask IANA to update the registry accordingly unless there are any objections. on iana.org: Protocol in the Segment ID sub-TLV Suggested: Protocol in the Segment ID Sub-TLV --> <t>IANA has created "Protocol in the Segment ID Sub-TLV" and "Protocol intheLabel Stack Sub-TLV oftheDownstream Detailed Mapping TLV" registries under the"Multi-Protocol"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry.RFC8287RFC 8287 defines the code points for Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS) protocols. </t> <t>This document specifies the code point to be used in the Segment ID sub-TLV and Downstream Detailed Mapping (DDMAP) TLV when the Interior Gateway Protocol (IGP) is OSPFv3. This document also updatesRFC8287RFC 8287 by clarifying that the existing "OSPF" code point is to be used only to indicateOSPFv2,OSPFv2 and by defining the behavior when the Segment ID sub-TLV indicates the use of IPv6.</t> </abstract> </front> <middle> <sectiontitle="Introduction">numbered="true" toc="default"> <name>Introduction</name> <t>IANA has created the "Protocol in the Segment ID Sub-TLV" registry and "Protocol intheLabel Stack Sub-TLV oftheDownstream Detailed Mapping TLV" registries under the"Multi-Protocol"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry <xreftarget="IANA-MPLS-LSP-PING"/>.target="IANA-MPLS-LSP-PING" format="default"/>. <xref target="RFC8287"/>format="default"/> defines the code points for OSPF and IS-IS. </t> <t>"OSPF for IPv6" <xref target="RFC5340"/>format="default"/> describes OSPF version 3 (OSPFv3) to support IPv6. "Support of Address Families in OSPFv3" <xref target="RFC5838"/>format="default"/> describes the mechanism to support multiple address families (AFs) in OSPFv3. Accordingly, OSPFv3 may be used to advertise IPv6 and IPv4 prefixes. </t> <t>This document specifies the code point to be used in the Segment ID sub-TLV(Type(Types 34,3535, and 36) and in the Downstream Detailed Mapping (DDMAP) TLV when the IGP is OSPFv3. </t> <t>This document also updates "Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes" <xref target="RFC8287"/>format="default"/> by clarifying that the existing "OSPF" code point is to be used only to indicateOSPFv2,OSPFv2 and by defining the behavior when the Segment ID sub-TLV indicates the use of IPv6. </t> </section> <sectiontitle="Terminology">numbered="true" toc="default"> <name>Requirements Notation</name> <t> The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t> </section> <section numbered="true" toc="default"> <name>Terminology</name> <t>This document uses the terminology defined in "Segment Routing Architecture" <xref target="RFC8402"/>,format="default"/>, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" <xref target="RFC8029"/>,format="default"/>, and "Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes" <xref target="RFC8287"/>format="default"/>, and so the readers are expected to be familiar with the same. </t> </section> <sectiontitle="Requirements Notation"> <t> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. </t> </section> <section title="OSPFv3 protocolnumbered="true" toc="default"> <name>OSPFv3 Protocol in Segment IDsub-TLVs">Sub-TLVs</name> <t>When the protocol field of the Segment ID sub-TLV of Type 34 (IPv4 IGP-Prefix Segment ID), Type 35 (IPv6 IGP-Prefix SegmentID)ID), and Type 36 (IGP-Adjacency Segment ID) is set to 3, the responderMUST<bcp14>MUST</bcp14> perform the Forwarding Equivalence Class (FEC) validation using OSPFv3 as the IGP. </t> <t>The initiatorMUST NOT<bcp14>MUST NOT</bcp14> set the protocol field of the Segment ID sub-TLV Type 35 and Type 36 as OSPF (value 1) as OSPFv2 is not compatible with the use of IPv6 addresses indicated by this sub-TLV. </t> <t>When the protocol field in the received Segment ID sub-TLV Type 35 and Type 36 is OSPF (value 1), the responderMAY<bcp14>MAY</bcp14> treat the protocol value as "Any IGP Protocol" (value 0) according to step 4a ofSection 7.4 of<xref target="RFC8287" sectionFormat="of" section="7.4" />. This allows the responder to support legacy implementations that use value 1 to indicate OSPFv3. </t> </section> <sectiontitle="OSPFv3 protocolnumbered="true" toc="default"> <name>OSPFv3 Protocol in Downstream Detailed MappingTLV">TLV</name> <t>The protocol field of theDownstream Detailed Mapping (DDMAP)DDMAP TLV in an echo reply is set to 7 when OSPFv3 is used to distribute the label carried in the Downstream Label field. </t> </section> <sectiontitle="Updatenumbered="true" toc="default"> <name>Update toRFC8287RFC 8287 - OSPFv2 Protocol in Segment ID and DDMAPsub-TLVs"> <t>Section 5 of <xrefSub-TLVs</name> <t><xref target="RFC8287"/>sectionFormat="of" section="5"/> defines the code point for OSPF to be used in the Protocol field of the Segment ID sub-TLV.Section 6 of<xref target="RFC8287"/>sectionFormat="of" section="6"/> defines the code point for OSPF to be used in the Protocol field of the DDMAP TLV. </t> <t>This document updates <xref target="RFC8287"/>,format="default"/> by specifying that the "OSPF" code pointsSHOULD<bcp14>SHOULD</bcp14> be used only for OSPFv2. </t> </section> <sectiontitle="IANA Considerations">numbered="true" toc="default"> <name>IANA Considerations</name> <section anchor="proto"title="Protocolnumbered="true" toc="default"> <name>Protocol in the Segment IDsub-TLV">Sub-TLV</name> <t> IANAis requested to assignhas assigned a new code point from the "Protocol in the Segment IDsub-TLV"Sub-TLV" registry under the"Multi-Protocol"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry as follows: </t><figure> <artwork><![CDATA[ Value Meaning Reference ---------- ------- ------------ 3 OSPFv3 This document ]]></artwork> </figure><table anchor="table1"> <name></name> <thead> <tr> <th>Value</th> <th>Meaning</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td>3</td> <td>OSPFv3</td> <td>RFC 9214</td> </tr> </tbody> </table> <t>IANAis also requested to addhas added a note for the existing entry for code point 1(OSPF) to read: -(OSPF): "To be used for OSPFv2 only". </t> </section> <section anchor="ds"title="Protocolnumbered="true" toc="default"> <name>Protocol in Label Stacksub-TLVSub-TLV of Downstream Detailed MappingTLV">TLV</name> <t>IANAis requested to assignhas assigned a new code point for OSPFv3 from "Protocol in Label Stack Sub-TLV of Downstream Detailed Mapping TLV" registry under the"Multi-Protocol"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry as follows: </t><figure> <artwork><![CDATA[ Value Meaning Reference ---------- --------- ------------ 7 OSPFv3 This document ]]></artwork> </figure><table anchor="table2"> <name></name> <thead> <tr> <th>Value</th> <th>Meaning</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td>7</td> <td>OSPFv3</td> <td>RFC 9214</td> </tr> </tbody> </table> <t>IANAis also requested to addhas added a note for the existing codepoint 5(OSPF) to read -(OSPF): "To be used for OSPFv2 only". </t> </section> </section> <sectiontitle="Security Considerations">numbered="true" toc="default"> <name>Security Considerations</name> <t>This document updates <xref target="RFC8287"/>format="default"/> and does not introduce any additional security considerations. See <xref target="RFC8029"/>format="default"/> to see generic security considerations about the MPLS LSP Ping. </t> </section> </middle> <back> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5340.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8402.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5838.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8029.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8287.xml"/> <reference anchor="IANA-MPLS-LSP-PING" target="https://www.iana.org/assignments/mpls-lsp-ping-parameters"> <front> <title>Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters</title> <author> <organization>IANA</organization> </author> <date/> </front> </reference> </references> <sectiontitle="Acknowledgement">numbered="false" toc="default"> <name>Acknowledgements</name> <t>The authors would like to thankLes Ginsberg, Zafar Ali, Loa Andersson, Andrew Molotchko, Deborah Brungard, Acee Lindem and Adrian Farrel<contact fullname="Les Ginsberg"/>, <contact fullname="Zafar Ali"/>, <contact fullname="Loa Andersson"/>, <contact fullname="Andrew Molotchko"/>, <contact fullname="Deborah Brungard"/>, <contact fullname="Acee Lindem"/>, and <contact fullname="Adrian Farrel"/> for their review and suggestions.</t> <t>The authors also would like to thankChrister Holmberg, Tero Kivinen, Matthew Bocci, Tom Petch and Martin Vigoureux<contact fullname="Christer Holmberg"/>, <contact fullname="Tero Kivinen"/>, <contact fullname="Matthew Bocci"/>, <contact fullname="Tom Petch"/>, and <contact fullname="Martin Vigoureux"/> for their review comments. </t> </section></middle> <back> <references title="Normative References"> <?rfc include="reference.RFC.2119"?> <?rfc include="reference.RFC.8174"?> <?rfc include="reference.RFC.5340"?> <?rfc include="reference.RFC.8402"?> <?rfc include="reference.RFC.5838"?> <?rfc include="reference.RFC.8029"?> <?rfc include="reference.RFC.8287"?> <reference anchor="IANA-MPLS-LSP-PING" target="http://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml"> <front> <title>Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters</title> <author><organization>IANA</organization></author> <date/> </front> </reference> </references></back> </rfc>