<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ipsecme-encrypted-esp-ping" target="https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-encrypted-esp-ping-02">
   <front>
      <title>Encrypted ESP Echo Protocol</title>
      <author initials="A." surname="Antony" fullname="Antony Antony">
         <organization>secunet Security Networks AG</organization>
      </author>
      <author initials="S." surname="Klassert" fullname="Steffen Klassert">
         <organization>secunet Security Networks AG</organization>
      </author>
      <date month="April" day="3" year="2026" />
      <abstract>
	 <t>   This document defines the Encrypted ESP Echo Function, a mechanism
   designed to assess the reachability of IP Security (IPsec) network
   paths using Encapsulating Security Payload (ESP) packets.  The
   primary objective is to reliably and efficiently detect the status of
   end-to-end paths by exchanging only encrypted ESP packets between
   IPsec peers.  The Encrypted Echo message can either use existing
   congestion control payloads from RFC9347 or a new message format
   defined here, with an option to specify a preferred return path when
   there is more than one pair of IPsec SAs between the same set of
   IPsec peers.

   A peer MAY announce the support using a new IKEv2 Status Notifcation
   ENCRYPTED_PING_SUPPORTED.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ipsecme-encrypted-esp-ping-02" />
   
</reference>
