[IPsec] Re: IPR disclosures for the draft-ietf-ipsecme-g-ikev2

2024-11-06 Thread Brian Weis
Hi Tero, I am also not aware of any IPR related to this draft. Thanks, Brian > On Nov 6, 2024, at 9:00 AM, Valery Smyslov wrote: > > Hi Tero, > > I'm not aware of any IPR related to this draft. > > Regards, > Valery. > >> I want to have confirmation from the authors whether there is any IPR

[IPsec] Re: draft-hu-ipsecme-pqt-hybrid-auth

2024-11-06 Thread Valery Smyslov
Hi, I do not have strong opinion regarding type-1 (composite signatures) vs type-2 (non-composite signatures). But as it was already mentioned, if we support non-composite signatures, then we in fact support both. And if we support type-2 (non-composite), then I believe that RFC 4739 appr

[IPsec] Re: [EXT] Re: draft-hu-ipsecme-pqt-hybrid-auth

2024-11-06 Thread tirumal reddy
Type-2 cannot be used with other protocols like TLS without protocol changes, assuming a network function uses both TLS and IPSec protocols, it will have to support both Type-1 and Type-2. Hence, the preference for Type-1. On Tue, 5 Nov 2024 at 22:51, Daniel Van Geest < daniel.vange...@cryptonext-

[IPsec] Re: Comments regarding draft-wang-hybrid-kem-ikev2-frodo-02

2024-11-06 Thread Wang Guilin
Dear Valery, Thanks for your questions on our draft IKEv2 with FrodoKEM. You mentioned to better use TCP, but IPsec seems mainly used in the scenarios with UDP. You also mentioned something is "wrong", but I did not get the point. Could you please explain this further? Thanks a lot, Guilin

[IPsec] Re: New Version Notification for draft-antony-ipsecme-iekv2-beet-mode-03.txt

2024-11-06 Thread Antony Antony
Hi, Here is a the latest version, draft-antony-ipsecme-ikev2-beet-mode-03. This document is a straightforward I.D. that seeks a code point for IKEv2 negotiation. Since IETF 120, the primary updates in this version focus on enhancing readability. Please note, this ID does not address packet form

[IPsec] Re: New Version Notification for draft-antony-ipsecme-iekv2-beet-mode-03.txt

2024-11-06 Thread Tuomo Soini
On Wed, 6 Nov 2024 14:26:53 +0100 Antony Antony wrote: > Hi, > Here is a the latest version, > draft-antony-ipsecme-ikev2-beet-mode-03. This document is a > straightforward I.D. that seeks a code point for IKEv2 negotiation. > Since IETF 120, the primary updates in this version focus on > enhanci

[IPsec] Re: [EXT] Re: draft-hu-ipsecme-pqt-hybrid-auth

2024-11-06 Thread Panwei (William)
I agree with Daniel that type-1 and type-2 are not in confliction that we could only choose one. Both choices have pros and cons. Either one has their assumptions of the suitable scenarios. I also in favor of type-2. Because I think the hybridization is temporary and pure PQ is the future, and

[IPsec] [CFRG] [IPsec]: FrodoKEM and its usage in IKemEv2

2024-11-06 Thread Wang Guilin
Dear Patrick, As disccussed during your talk about FrodoKEM in the CFRG meeting, here is the info about our draft. Post-quantum Hybrid Key Exchange in the IKEv2 with FrodoKEM draft-wang-hybrid-kem-ikev2-frodo-02 https://datatracker.ietf.org/doc/draft-wang-hybrid-kem-ikev2-frodo/ Cheers, Guilin

[IPsec] Re: New Version Notification for draft-antony-ipsecme-iekv2-beet-mode-03.txt

2024-11-06 Thread Paul Wouters
On Nov 6, 2024, at 13:27, Antony Antony wrote: > > As such, this document can progress independently. > > I would like to request the working group’s adoption of > draft-antony-ipsecme-ikev2-beet-mode-03. It is ready. I am supportive of this work continuing here. Paul

[IPsec] Re: New Version Notification for draft-antony-ipsecme-encrypted-esp-ping-05.txt

2024-11-06 Thread Antony Antony
Hi, Here’s the latest version, -05, of draft-antony-ipsecme-encrypted-esp-ping. This update, since IETF 120, includes readability improvements and fixes to the IP-TFS subtype, as well as the addition of an IKEv2 notification. There’s been interest in this work, as reflected in feedback from recen

[IPsec] Re: IPR disclosures for the draft-ietf-ipsecme-g-ikev2

2024-11-06 Thread Valery Smyslov
Hi Tero, I'm not aware of any IPR related to this draft. Regards, Valery. > I want to have confirmation from the authors whether there is any IPRs known > that has not yet been disclosed. Please respond to this email to confirm this. > > Also if anybody else knows any IPRs that has not been alr

[IPsec] Re: [CFRG] [IPsec]: FrodoKEM and its usage in IKemEv2

2024-11-06 Thread Patrick Longa
Thanks, Guilin! I'll take a look as soon as I get a chance. Best, -Patrick From: Wang Guilin Sent: Wednesday, November 6, 2024 6:20 AM To: Patrick Longa Cc: ipsec ; cfrg ; Wang Guilin Subject: [CFRG] [IPsec]: FrodoKEM and its usage in IKemEv2 Dear Patrick, As disccussed during your talk abo

[IPsec] Re: Comments regarding draft-wang-hybrid-kem-ikev2-frodo-02

2024-11-06 Thread Valery Smyslov
Hi Guilin, Dear Valery, Thanks for your questions on our draft IKEv2 with FrodoKEM. You mentioned to better use TCP, but IPsec seems mainly used in the scenarios with UDP. RFC 9329 defines how to use TCP as a transport for IKE and ESP. This RFC was developed to

[IPsec] Re: New Version Notification for draft-antony-ipsecme-iekv2-beet-mode-03.txt

2024-11-06 Thread Robert Moskowitz
I support this work in IPsec. Aside:  I will work in parallel on a 7402-bis; not here. On 11/6/24 08:26, Antony Antony wrote: Hi, Here is a the latest version, draft-antony-ipsecme-ikev2-beet-mode-03. This document is a straightforward I.D. that seeks a code point for IKEv2 negotiation. Since

[IPsec] Re: Comments regarding draft-wang-hybrid-kem-ikev2-frodo-02

2024-11-06 Thread Bruckert, Leonie
Hi Guilin, Thank you for your offer. I am looking forward to working together on this draft. Cheers, Leonie Von: Wang Guilin Gesendet: Dienstag, 5. November 2024 15:06 An: Bruckert, Leonie ; ipsec Cc: Wang Guilin Betreff: RE: [IPsec] Comments regarding draft-wang-hybrid-kem-ikev2-frodo-02