A new Request for Comments is now available in online RFC libraries.

        
        RFC 9570

        Title:      Deprecating the Use of Router Alert
                    in LSP Ping 
        Author:     K. Kompella,
                    R. Bonica,
                    G. Mirsky, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2024
        Mailbox:    kireeti.i...@gmail.com,
                    rbon...@juniper.net,
                    gregimir...@gmail.com
        Pages:      9
        Updates:    RFC 8029

        I-D Tag:    draft-ietf-mpls-lspping-norao-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9570

        DOI:        10.17487/RFC9570

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.

This document is a product of the Multiprotocol Label Switching Working Group 
of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org

Reply via email to