<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-lspping-norao" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-lspping-norao-08">
   <front>
      <title>Deprecating the Use of Router Alert in LSP Ping</title>
      <author initials="K." surname="Kompella" fullname="Kireeti Kompella">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="R. P." surname="Bonica" fullname="Ron Bonica">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="G." surname="Mirsky" fullname="Greg Mirsky">
         <organization>Ericsson</organization>
      </author>
      <date month="March" day="1" year="2024" />
      <abstract>
	 <t>   The MPLS echo request and MPLS echo response messages, defined in RFC
   8029 &quot;Detecting Multiprotocol Label Switched (MPLS) Data-Plane
   Failures&quot; (usually referred to as LSP ping messages), are
   encapsulated in IP whose headers 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, the use of an IPv6 loopback address (::1/128) as the IPv6
   destination address for an MPLS echo request message is RECOMMENDED.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-lspping-norao-08" />
   
</reference>
