I plan on being in the session to answer any questions on my draft.

On 3/18/26 7:28 AM, Antony Antony wrote:
Hi IPsecME,

In the interest of saving time at tomorrow's packed session in
Shenzhen, here is a quick status update on this I-D,
draft-moskowitz-ipsecme-rfc7402-beet-update .

At IETF 124(Montréal), Deb raised a concern that the original, RFC7402,
was processed in the INT area. We reached out to them and the INT AD
has since given his blessing to move this document
- an update to Appendix B, BEET - into the IPsecME WG(under the SEC AD),
as the relevant expertise resides in IPsecME/SEC.

Given the issue Deb raised at IETF 124 is resolved, I would like to
formally request WG adoption of this document to IPsecME chairs.
At least change to WG Adoption Candidate state, if WG adoption
would take long due to other documents.

Note: this I-D is different from draft-ietf-ipsecme-ikev2-beet-mode ,
which is already a WG document and authors are waiting on this I-D
before it, ideally both, can proceed to WGLC.

Tomorrow, I will be participating remotely. Time permits, I plan to
raise this under AoB. Early feedback on the list is welcome.

regards,
-antony


On Thu, Oct 09, 2025 at 10:46:53 -0400, Robert Moskowitz wrote:
    This is the final draft from the authors.  It is ready for moving
    forward.
    Note it is primarily a clean up of Appendix B from rfc 7402 with
    additions from Antony for IPsec use.
    Thank you, Antony.
    Please include it in the IETF124 session.
    Thank you and see you all soon in Montreal.
    Bob

    -------- Forwarded Message --------
    Subject: New Version Notification for
    draft-moskowitz-ipsecme-rfc7402-beet-update-02.txt
    Date: Thu, 09 Oct 2025 07:40:45 -0700
    From: [1][email protected]
    To: Andrei Gurtov [2]<[email protected]>, Antony Antony
    [3]<[email protected]>, Jan Melen [4]<[email protected]>,
    Jan Melen [5]<[email protected]>, Petri Laari
    [6]<[email protected]>, Robert Moskowitz
    [7]<[email protected]>
    A new version of Internet-Draft
    draft-moskowitz-ipsecme-rfc7402-beet-update-02.txt has been
    successfully
    submitted by Robert Moskowitz and posted to the
    IETF repository.
    Name: draft-moskowitz-ipsecme-rfc7402-beet-update
    Revision: 02
    Title: A Bound End-to-End Tunnel (BEET) mode for ESP
    Date: 2025-10-09
    Group: Individual Submission
    Pages: 16
    URL:
    [8]https://www.ietf.org/archive/id/draft-moskowitz-ipsecme-rfc7402-beet
    -update-02.txt
    Status:
    [9]https://datatracker.ietf.org/doc/draft-moskowitz-ipsecme-rfc7402-bee
    t-update/
    HTML:
    [10]https://www.ietf.org/archive/id/draft-moskowitz-ipsecme-rfc7402-bee
    t-update-02.html
    HTMLized:
    [11]https://datatracker.ietf.org/doc/html/draft-moskowitz-ipsecme-rfc74
    02-beet-update
    Diff:
    [12]https://author-tools.ietf.org/iddiff?url2=draft-moskowitz-ipsecme-r
    fc7402-beet-update-02
    Abstract:
    This document is an update to the Bound End-to-End Tunnel (BEET) mode
    for ESP in as described in [RFC7402]. It brings the description in
    alignment with the addition of BEET mode for IKEv2 without any
    processing changes as described in [RFC7402]
    The IETF Secretariat

References

    1. mailto:[email protected]
    2. mailto:[email protected]
    3. mailto:[email protected]
    4. mailto:[email protected]
    5. mailto:[email protected]
    6. mailto:[email protected]
    7. mailto:[email protected]
    8. 
https://www.ietf.org/archive/id/draft-moskowitz-ipsecme-rfc7402-beet-update-02.txt
    9. 
https://datatracker.ietf.org/doc/draft-moskowitz-ipsecme-rfc7402-beet-update/
   10. 
https://www.ietf.org/archive/id/draft-moskowitz-ipsecme-rfc7402-beet-update-02.html
   11. 
https://datatracker.ietf.org/doc/html/draft-moskowitz-ipsecme-rfc7402-beet-update
   12. 
https://author-tools.ietf.org/iddiff?url2=draft-moskowitz-ipsecme-rfc7402-beet-update-02
_______________________________________________
IPsec mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
IPsec mailing list -- [email protected]
To unsubscribe send an email to [email protected]

_______________________________________________
IPsec mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to