Re: [IPsec] WG adoptation call for draft-smyslov-ipsecme-ikev2-aux-02

2019-03-14 Thread Panos Kampanakis (pkampana)
+1 on adopting this draft. -Original Message- From: IPsec On Behalf Of Valery Smyslov Sent: Thursday, March 14, 2019 4:38 AM To: 'Tero Kivinen' ; ipsec@ietf.org Subject: Re: [IPsec] WG adoptation call for draft-smyslov-ipsecme-ikev2-aux-02 Hi, as author of the document I (obviously)

Re: [IPsec] I-D Action: draft-hopps-ipsecme-iptfs-00.txt

2019-03-14 Thread Christian Hopps
Valery Smyslov writes: If there really is no way to work around this, I suppose we just require retransmissions of CC info reports until they are ACKd or things are torn down b/c of drops (i.e., normal INFO exchange). It does feel like we are adding fragility here that isn’t really needed

Re: [IPsec] WG adoptation call for draft-smyslov-ipsecme-ikev2-aux-02

2019-03-14 Thread Valery Smyslov
Hi, as author of the document I (obviously) support its adoption. It's a building block for QSKE solution (at least how the WG sees it now) so I think we should adopt it. Regards, Valery. > This document has been stable for some time, and I think it is ready > to go forward. Because of that I

Re: [IPsec] I-D Action: draft-hopps-ipsecme-iptfs-00.txt

2019-03-14 Thread Valery Smyslov
> > No, all retransmissions of IKE message with the same Message ID must be > > binary identical. > > Perhaps we could relax this requirement for this particular message though. > This seems like a simple tightly- > focused semantic change which gets us past the roadblock. No, we cannot.