I support adoption of the document. I think today I prefer it to be EESP
than ESPv4.but we can leave that for further discussion.
Yours,
Daniel

On Fri, Apr 11, 2025 at 4:59 AM Wang Guilin <Wang.Guilin=
[email protected]> wrote:

> Also support adoption. The current ESP protocol do need to be updated,  I
> think.
>
> Guilin
>
> -----Original Message-----
> From: Valery Smyslov <[email protected]>
> Sent: Monday, 7 April 2025 8:10 pm
> To: 'Tero Kivinen' <[email protected]>; [email protected]
> Subject: [IPsec] Re: WG Adoption call of draft draft-klassert-ipsecme-eesp
>
> Hi,
>
> I support adoption of this document as a starting point.
>
> Regards,
> Valery.
>
> > As our charter is now updated, this document is working on the
> > following charter
> > item:
> >
> >       The ESPv3 protocol was defined in 2005 and there may be a need
> >       to make enhancements to it. The working group will analyze the
> >       possible problems and work on solving them. This may include
> >       updating ESP, AH, and/or Wrapped ESP (WESP) standards, or
> >       result in a new security protocol.
> >
> > This email will start three week working group adoption call for
> > draft-klassert- ipsecme-eesp document. If you are in favor of adopting
> > this document, reply this email. And especially if you have any
> > objections adopting this document as base document, reply this email by
> explaining your objections.
> > --
> > [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]
> _______________________________________________
> IPsec mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>


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

Reply via email to