Deprecating the Use of Router Alert in LSP Ping
RFC 9570
Revision differences
Document history
Date | By | Action |
---|---|---|
2024-05-22
|
(System) | Received changes through RFC Editor sync (created document RFC 9570, created became rfc relationship between draft-ietf-mpls-lspping-norao and RFC 9570, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9570, created became rfc relationship between draft-ietf-mpls-lspping-norao and RFC 9570, set abstract to 'The MPLS echo request and MPLS echo response messages, defined in RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" (usually referred to as LSP ping), are encapsulated in IP packets with headers that include a Router Alert Option (RAO). In actual deployments, the RAO was neither required nor used. Furthermore, RFC 6398 identifies security vulnerabilities associated with the RAO in non-controlled environments, e.g., the case of using the MPLS echo request/reply as inter-area Operations, Administration, and Maintenance (OAM), and recommends against its use outside of controlled environments. Therefore, this document retires the RAO for MPLS OAM and updates RFC 8029 to remove the RAO from LSP ping message encapsulations. Furthermore, this document explains why RFC 7506 has been reclassified as Historic. Also, this document recommends the use of an IPv6 loopback address (::1/128) as the IPv6 destination address for an MPLS echo request message.', set pages to 9, set standardization level to Proposed Standard, added RFC published event at 2024-05-22, created updates relation between RFC 9570 and RFC 8029) |
2024-05-22
|
(System) | RFC published |