<?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-03">
   <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="September" day="22" year="2023" />
      <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 headers that include a Router Alert Option (RAO).
   The rationale for using an RAO as the exception mechanism is
   questionable.  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 OAM, and recommends against its use outside of controlled
   environments.

   Therefore, this document removes the RAO from LSP ping message
   encapsulations.  It updates RFCs 7506 and 8029.

   This document also recommends the use of an IPv6 loopback address
   (::1/128) and discourages the use of an IPv4 loopback address mapped
   to IPv6.

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