Thanks to the authors and the reviewers!

I suspect that there may be some nits and changes that will be made,  but
I'm going to issue the ballot for this now for the 6 Feb telechat (there
are some pretty full telechats between 19 Dec and 6 Feb).  So there is
ample time to make sure the IANA registry work and terminology is all
perfect before then.

It also gives the working group a little bit of breathing room for the
newly adopted draft-ietf-ipsecme-ikev2-rename-esn and still allow it to
catch up to this draft.

Deb Cooley
Sec AD

On Thu, Dec 12, 2024 at 1:44 AM Valery Smyslov <smyslov.i...@gmail.com>
wrote:

> Hi,
>
> this version addresses concerns expressed during IETF LC and in
> directorate reviews.
> It is also aligned with draft-ietf-ipsecme-ikev2-rename-esn. In addition,
> we completely
> avoided any renaming of IKEv2 registries (including Reserved
> Authentication Method) by defining
> a new transform IDs registry for GCKS authentication methods.
> As a result - the draft does not update RFC 7296 anymore.
>
> This version also contains numerous clarifications made as a result of
> discussions
> during IETF LC. It also addresses the questions made by IANA in initial
> IANA review.
>
> Regards,
> Brian & Valery.
>
> > Internet-Draft draft-ietf-ipsecme-g-ikev2-18.txt is now available. It is
> a work item of
> > the IP Security Maintenance and Extensions (IPSECME) WG of the IETF.
> >
> >    Title:   Group Key Management using IKEv2
> >    Authors: Valery Smyslov
> >             Brian Weis
> >    Name:    draft-ietf-ipsecme-g-ikev2-18.txt
> >    Pages:   74
> >    Dates:   2024-12-11
> >
> > Abstract:
> >
> >    This document presents an extension to the Internet Key Exchange
> >    version 2 (IKEv2) protocol for the purpose of a group key management.
> >    The protocol is in conformance with the Multicast Security (MSEC) key
> >    management architecture, which contains two components: member
> >    registration and group rekeying.  Both components are required for a
> >    GCKS (Group Controller/Key Server) to provide authorized Group
> >    Members (GMs) with IPsec group security associations.  The group
> >    members then exchange IP multicast or other group traffic as IPsec
> >    packets.
> >
> >    This document obsoletes RFC 6407.
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-ipsecme-g-ikev2/
> >
> > There is also an HTMLized version available at:
> > https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-g-ikev2-18
> >
> > A diff from the previous version is available at:
> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-ipsecme-g-ikev2-18
> >
> > Internet-Drafts are also available by rsync at:
> > rsync.ietf.org::internet-drafts
> >
> >
> > _______________________________________________
> > 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
>
_______________________________________________
IPsec mailing list -- ipsec@ietf.org
To unsubscribe send an email to ipsec-le...@ietf.org

Reply via email to