On Mon, Mar 02, 2026 at 07:59:48AM -0800, [email protected] wrote:
> Internet-Draft draft-ietf-ipsecme-eesp-ikev2-02.txt is now available. It is a
> work item of the IP Security Maintenance and Extensions (IPSECME) WG of the
> IETF.
> 
>    Title:   IKEv2 negotiation for Enhanced Encapsulating Security Payload 
> (EESP)
>    Authors: Steffen Klassert
>             Antony Antony
>             Tobias Brunner
>             Valery Smyslov
>    Name:    draft-ietf-ipsecme-eesp-ikev2-02.txt
>    Pages:   17
>    Dates:   2026-03-02
> 
> Abstract:
> 
>    This document specifies how to negotiate the use of the Enhanced
>    Encapsulating Security Payload (EESP) protocol using the Internet Key
>    Exchange protocol version 2 (IKEv2).  The EESP protocol, which is
>    defined in [I-D.ietf-ipsecme-eesp], provides the same security
>    services as Encapsulating Security Payload (ESP), but has richer
>    functionality and provides better performance in specific
>    circumstances.  This document specifies negotiation of version 0 of
>    EESP.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ipsecme-eesp-ikev2/

We don't present at the IETF 125 meeting about the EESP-IKev2 work,
so here is a changelog for the latest version. The changes basically
align the draft to the core EESP document.

Changelog:

- Reference migration to WG EESP draft:
  - references switched from I-D.klassert-ipsecme-eesp to I-D.ietf-ipsecme-eesp
  - placeholder section references like [XXX] replaced with concrete section 
names

- Introduction/feature wording refined:
  - text now emphasizes Session ID usage (e.g., CPU pinning/QoS based on inner 
flow)
  - terminology aligned with the current base EESP WG draft

- Security Considerations strengthened:
  - Crypt Offset text rewritten to describe controlled exposure and negotiated 
max offset

Steffen

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

Reply via email to