Thanks for adding the use cases section, it's useful to me.
In section 5, after adding the third scenario of not receiving the ESP Echo
Reply packet, there are two points in the following paragraph that also need
adjustments.
1. s/the sender can not distibguish those two scenarios/the sender can not
distinguish those three scenarios.
2. The following sentence isn't correct as there are 3 possible situations.
Therefore
the sender SHOULD NOT treat lack of response as an indicator of end-
to-end connectivity issues until an explicit confirmation of ESP Echo
support by the peer is received.
Maybe change it to "Therefore the sender SHOULD NOT treat lack of response as
an indicator of end-to-end connectivity issues" or "Therefore the sender SHOULD
NOT treat lack of response as an indicator of end-to-end connectivity issues
until it receives explicit confirmation that the peer supports and the
intermediate nodes allow ESP Echo".
Regards & Thanks！
Wei PAN (潘伟)
> -----Original Message-----
> From: IPsec <[email protected]> On Behalf Of Jen Linkova
> Sent: Friday, April 5, 2024 6:59 AM
> To: [email protected]; Michael Richardson <[email protected]>;
> Lorenzo Colitti <[email protected]>
> Subject: [IPsec] Fwd: New Version Notification for
> draft-colitti-ipsecme-esp-ping-02.txt
>
> We've just submitted -02 which should address comments raised during
> the IPSECME session at IETF119.
>
> Comments/suggestions?
>
>
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Fri, Apr 5, 2024 at 9:43 AM
> Subject: New Version Notification for
> draft-colitti-ipsecme-esp-ping-02.txt
> To: Jen Linkova <[email protected]>, Lorenzo Colitti
> <[email protected]>, Michael Richardson
> <[email protected]>
>
>
> A new version of Internet-Draft draft-colitti-ipsecme-esp-ping-02.txt
> has been successfully submitted by Jen Linkova and posted to the IETF
> repository.
>
> Name: draft-colitti-ipsecme-esp-ping
> Revision: 02
> Title: ESP Echo Protocol
> Date: 2024-04-04
> Group: Individual Submission
> Pages: 8
> URL:
> https://www.ietf.org/archive/id/draft-colitti-ipsecme-esp-ping-02.txt
> Status:
> https://datatracker.ietf.org/doc/draft-colitti-ipsecme-esp-ping/
> HTML:
> https://www.ietf.org/archive/id/draft-colitti-ipsecme-esp-ping-02.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-colitti-ipsecme-esp-ping
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-colitti-ipsecme-esp-ping-
> 02
>
> Abstract:
>
> This document defines an ESP echo function which can be used to
> detect whether a given network path supports ESP packets.
>
>
>
> The IETF Secretariat
>
>
>
>
> --
> Cheers, Jen Linkova
>
> _______________________________________________
> IPsec mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipsec
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
