Hi, The BEET mode work started around IETF 118. Since IETF 118, I have narrowed the scope of the BEET mode ID to IKEv2 only, to obtain an IKEv2 Code Point allocation. BEET mode itself is specified in the Appendix of RFC 7402.
However, if there is interest among the authors of RFC 7402, I would propose writing a bis(revision) just for that Appendix. This ID is simple now and could potentially proceed quickly. On Mon, Jul 08, 2024 at 02:00:27 -0700, internet-dra...@ietf.org wrote: > A new version of Internet-Draft draft-antony-ipsecme-iekv2-beet-mode-02.txt > has been successfully submitted by Antony Antony and posted to the > IETF repository. > > Name: draft-antony-ipsecme-iekv2-beet-mode > Revision: 02 > Title: IKEv2 negotiation for Bound End-to-End Tunnel (BEET) mode ESP > Date: 2024-07-08 > Group: Individual Submission > Pages: 8 > URL: > https://www.ietf.org/archive/id/draft-antony-ipsecme-iekv2-beet-mode-02.txt > Status: > https://datatracker.ietf.org/doc/draft-antony-ipsecme-iekv2-beet-mode/ > HTML: > https://www.ietf.org/archive/id/draft-antony-ipsecme-iekv2-beet-mode-02.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-antony-ipsecme-iekv2-beet-mode > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-antony-ipsecme-iekv2-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 > > regards, -antony _______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
