RFC 9214: OSPFv3 Code Point for MPLS LSP Ping
In plain English — editorial summary, not part of the RFC
IANA has created "Protocol in the Segment ID Sub-TLV" and "Protocol in Label Stack Sub-TLV of Downstream Detailed Mapping TLV" registries under the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry. RFC 8287 defines the code points for Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS) protocols. 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 updates RFC 8287 by clarifying that the existing "OSPF" code point is to be used only to indicate OSPFv2 and by defining the behavior when the Segment ID sub-TLV indicates the use of IPv6.
Document record
- Document ID
- RFC9214
- Published
- April 2022
- Authors
- N. Nainar; C. Pignataro; M. Aissaoui
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 8287
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 9070YANG Data Model for MPLS LDPCurrent
March 2022
- RFC 9020YANG Data Model for Segment RoutingCurrent
May 2021
- RFC 9017Special-Purpose Label TerminologyCurrent
April 2021
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 8957Synonymous Flow Label FrameworkCurrent
January 2021
- RFC 9658Multipoint LDP Extensions for Multi-Topology RoutingCurrent
October 2024
- RFC 8690Clarification of Segment ID Sub-TLV Length for RFC 8287Current
December 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?