Hi, We are proposing Encrypted ESP Ping, which will compliment/co-exist with draft-colitti-ipsecme-esp-ping. We welcome feedback on this proposal. Both authors will be present at the upcoming Vancouver IETF and would love to chat about this ID and our implementation plans. Also, we are planning a short presentation at IPsecME session there.
regards, -antony On Thu, Jul 04, 2024 at 04:59:57 -0700, internet-dra...@ietf.org wrote: > A new version of Internet-Draft draft-antony-ipsecme-encrypted-esp-ping-01.txt > has been successfully submitted by Antony Antony and posted to the > IETF repository. > > Name: draft-antony-ipsecme-encrypted-esp-ping > Revision: 01 > Title: Encrypted ESP Echo Protocol > Date: 2024-07-04 > Group: Individual Submission > Pages: 9 > URL: > https://www.ietf.org/archive/id/draft-antony-ipsecme-encrypted-esp-ping-01.txt > Status: > https://datatracker.ietf.org/doc/draft-antony-ipsecme-encrypted-esp-ping/ > HTML: > https://www.ietf.org/archive/id/draft-antony-ipsecme-encrypted-esp-ping-01.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-antony-ipsecme-encrypted-esp-ping > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-antony-ipsecme-encrypted-esp-ping-01 > > Abstract: > > This document defines an Encrypted ESP Echo Function, a novel > mechanism designed to assess the reachability of an IP Security > (IPsec) network path using Encapsulating Security Payload (ESP) > packets. The primary objective of this function is to facilitate the > detection of end-to-end path status dynamically in a reliable and > efficient manner, only using encrypted ESP packets between the IPsec > peers. The Encrypted Echo message can use existing congestion > control payloads from RFC9347 or the message format specified here, > with an optional preferred return path > > > > The IETF Secretariat > > _______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
