Hi, This is just a version bump while wating for ESP packet format I.D WG adoption call. There is no content change.
A Bound End-to-End Tunnel (BEET) mode for ESP https://datatracker.ietf.org/doc/html/draft-moskowitz-ipsecme-rfc7402-beet-update-02 regards, -antony On Mon, Mar 23, 2026 at 06:59:26 -0700, [email protected] wrote: > A new version of Internet-Draft draft-ietf-ipsecme-ikev2-beet-mode-02.txt has > been successfully submitted by Antony Antony and posted to the > IETF repository. > > Name: draft-ietf-ipsecme-ikev2-beet-mode > Revision: 02 > Title: IKEv2 negotiation for Bound End-to-End Tunnel (BEET) mode ESP > Date: 2026-03-23 > Group: ipsecme > Pages: 8 > URL: > https://www.ietf.org/archive/id/draft-ietf-ipsecme-ikev2-beet-mode-02.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-beet-mode/ > HTML: > https://www.ietf.org/archive/id/draft-ietf-ipsecme-ikev2-beet-mode-02.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-ikev2-beet-mode > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-ipsecme-ikev2-beet-mode-02 > > Abstract: > > This document specifies a new Notify Message Type Payload for the > Internet Key Exchange Protocol Version 2 (IKEv2), to negotiate IPsec > ESP Bound End-to-End Tunnel (BEET) mode. BEET mode combines the > benefits of tunnel mode with reduced overhead, making it suitable for > applications requiring minimalistic end-to-end tunnels, mobility > support, and multi-address multi-homing capabilities. The > introduction of the USE_BEET_MODE Notify Message enables the > negotiation and establishment of BEET mode security associations. > > > > The IETF Secretariat > > _______________________________________________ IPsec mailing list -- [email protected] To unsubscribe send an email to [email protected]
