Dear WG Chairs, This is a friendly nudge for your response, as the re-chartering process seems to have progressed.
Could you please let us know the next steps? Would the WG Chairs consider issuing a call for WG adoption of this document? The draft is ready to proceed, and there has been support for its adoption on the mailing list. On a related note, drafts draft-antony-ipsecme-encrypted-esp-ping and very likely draft-colitti-ipsecme-esp-ping are also awaiting a response from the WG Chairs. If there is anything I need to do to facilitate this process, please let me know. regards, -antony On Wed, Nov 06, 2024 at 02:26:53PM +0100, Antony Antony wrote: > Hi, > Here is a the latest version, draft-antony-ipsecme-ikev2-beet-mode-03. This > document is a straightforward I.D. that seeks a code point for IKEv2 > negotiation. Since IETF 120, the primary updates in this version focus on > enhancing readability. > > Please note, this ID does not address packet format, as that is covered in > RFC 7402 Appendix B, RFC since 2015. It is likely be stand alone or a bis > document in the future. As such, this document can progress independently. > > I would like to request the working group’s adoption of > draft-antony-ipsecme-ikev2-beet-mode-03. It is ready. > > regards, > -antony > > > On Wed, Nov 06, 2024 at 02:27:13 -0800, internet-dra...@ietf.org wrote: > > A new version of Internet-Draft draft-antony-ipsecme-iekv2-beet-mode-03.txt > > has been successfully submitted by Antony Antony and posted to the > > IETF repository. > > > > Name: draft-antony-ipsecme-iekv2-beet-mode > > Revision: 03 > > Title: IKEv2 negotiation for Bound End-to-End Tunnel (BEET) mode ESP > > Date: 2024-11-06 > > Group: Individual Submission > > Pages: 8 > > URL: > > https://www.ietf.org/archive/id/draft-antony-ipsecme-iekv2-beet-mode-03.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-03.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-03 > > > > 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 -- ipsec@ietf.org > To unsubscribe send an email to ipsec-le...@ietf.org _______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
