[IPsec] Re: I-D Action: draft-ietf-ipsecme-ikev2-qr-alt-05.txt

2024-11-21 Thread Valery Smyslov
Hi, this version addresses points raised in the tree recent reviews (from Panos, William and Scott). Regards, Valery. > Internet-Draft draft-ietf-ipsecme-ikev2-qr-alt-05.txt is now available. It is > a work > item of the IP Security Maintenance and Extensions (IPSECME) WG of the IETF. > >

[IPsec] Re: Comments on draft-ietf-ipsecme-ikev2-qr-alt

2024-11-21 Thread Valery Smyslov
Hi Scott, thank you for your comments. Please see inline. I just went through the ikev2-qr-alt draft, and have these comments: -The last paragraph of 3.1 worries about the case where the two sides agree on a PPK, but after authenticating, it turns out that they're not configurin

[IPsec] I-D Action: draft-ietf-ipsecme-ikev2-qr-alt-05.txt

2024-11-21 Thread internet-drafts
Internet-Draft draft-ietf-ipsecme-ikev2-qr-alt-05.txt is now available. It is a work item of the IP Security Maintenance and Extensions (IPSECME) WG of the IETF. Title: Mixing Preshared Keys in the IKE_INTERMEDIATE and in the CREATE_CHILD_SA Exchanges of IKEv2 for Post-quantum Security Au

[IPsec] I-D Action: draft-ietf-ipsecme-ikev2-diet-esp-extension-02.txt

2024-11-21 Thread internet-drafts
Internet-Draft draft-ietf-ipsecme-ikev2-diet-esp-extension-02.txt is now available. It is a work item of the IP Security Maintenance and Extensions (IPSECME) WG of the IETF. Title: Internet Key Exchange version 2 (IKEv2) extension for Header Compression Profile (HCP) Authors: Daniel Migau

[IPsec] Re: Rechartering IPsecME

2024-11-21 Thread Michael Richardson
Paul Wouters wrote: > I thought the world was moving towards ML-KEM and FrodoKEM? It would be That seems to be where CFRG/NIST/PQC is going. The whole world is not NIST though. I think that figuring out how to accomodate McElice, with what I understand are monstrous sizes is a good thing to

[IPsec] Re: Rechartering IPsecME

2024-11-21 Thread Michael Richardson
Hi, the charter text seems fine to me. In general, I think that it is overly detailed invokes too much IESG busy work, and much of the "current work items" could just be milestones (which still requires AD approval). If we went beyond what paragraph two says, "... continues the work..." then th