Re: [IPsec] Comments on draft-pwouters-multi-sa-performance

2021-11-10 Thread Antony Antony
Hi Paul, I think our draft is a better solution for the network multipath problem too, definitely for a few per Path SAs. Larger number of paths, say 32 or more paths, may cause scaling issues in SPD or/and SAD lookup; the data path lookup. However, data path lookup speed would depend on the i

Re: [IPsec] WG Adoption call for draft-btw-add-ipsecme-ike

2021-11-10 Thread tirumal reddy
I support adoption of the draft. -Tiru On Mon, 8 Nov 2021 at 19:58, wrote: > Hi Tero, all, > > I support adoption. > > FWIW, I'm not aware of any IPR related to this I-D. > > Cheers, > Med > > > -Message d'origine- > > De : IPsec De la part de Tero Kivinen > > Envoyé : lundi 8 novemb

Re: [IPsec] Cost-efficient quantum-resistant DoS protection

2021-11-10 Thread Michael Richardson
Yoav Nir wrote: >>> Tero Kivinen wrote: > Even without surpassing the 64KB limit, this must be a concern. > IKEv2's cookie mechanism and puzzles try to increase the cost of the > attacker per each connection. Now, an attacker must still accept > these costs bu

Re: [IPsec] WGLC for draft-ietf-ipsecme-rfc8229bis

2021-11-10 Thread Michael Richardson
Valery Smyslov wrote: >> I wonder about keeping more of the original authors on the new >> document, since it is substantively the same document. I can not >> judge what their contribution was to the original document, nor do I >> know if they were asked. If the design team has

Re: [IPsec] WG Adoption call for draft-btw-add-ipsecme-ike

2021-11-10 Thread Paul Wouters
On Wed, 10 Nov 2021, mohamed.boucad...@orange.com wrote: So the client sends FOO(x) and the server respones with FOO(y) x can be empty (eg the client has no previous notion or preference for FOO. Or if it has one, it can suggest it. The server takes that value only as a preference of the client

Re: [IPsec] WG Adoption call for draft-btw-add-ipsecme-ike

2021-11-10 Thread Michael Richardson
> This is the start of 2 week WG adoption call for this document, ending > 2021-11-22. Please send your reply about whether you support adopting > this document as WG document or not. I have browsed through the document. I don't know if the mechanism is correct or not. I think that P

Re: [IPsec] WGLC for draft-ietf-ipsecme-rfc8229bis

2021-11-10 Thread Valery Smyslov
Hi Michael, > > All three original authors were asked to co-author the draft. Tommy > > agreed, but no reply was received from Samy and Ravi. I cannot judge > > their contribution to the original rfc, but I think that it's a good > > idea to add them to acknowledgement section an

Re: [IPsec] WG adoption call for draft-smyslov-ipsecme-ikev2-auth-announce

2021-11-10 Thread Valery Smyslov
Hi, FWIW, as an author I (obviously) support adoption. Regards, Valery. > This is the start of 2 week WG adoption call for this document, ending > 2021-11-22. Please send your reply about whether you support adopting > this document as WG document or not. > -- > kivi...@iki.fi > > _

Re: [IPsec] WG Adoption call for draft-btw-add-ipsecme-ike

2021-11-10 Thread Valery Smyslov
HI, Just for the record: as a co-author I (obviously) support adoption or this document. Regards, Valery. > This is the start of 2 week WG adoption call for this document, ending > 2021-11-22. Please send your reply about whether you support adopting > this document as WG document or not. > --

[IPsec] Potential issue with draft-ietf-ipsecme-ikev2-intermediate

2021-11-10 Thread Valery Smyslov
Hi, I have had off the list discussion with Tobias Brunner and he has pointed out to one potential issue with draft-ietf-ipsecme-ikev2-intermediate. Currently the authentication of IKE_INTERMEDIATE exchanges is performed as follows: InitiatorSignedOctets = RealMsg1 | NonceRData | MACedIDFor