Re: [IPsec] WG Adoption call for draft-smyslov-ipsecme-ikev2-qr-alt

2023-12-11 Thread Panwei (William)
Hi, I support the adoption of this draft. I've read the very early version and thought it was quite useful. I've read it again and still believe it's important and useful. I believe we're highly likely to implement this draft. Some quick comments below: 1) I feel the title "Alternate

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Paul Wouters
On Dec 11, 2023, at 12:03, Hannes Tschofenig wrote:I have, however, heard about uses of WireGuard on Linux-based IoT devices (these are non-constrained devices, obviously) with the argument that it is simple to use and efficient.It’s actually far less efficient because it only

Re: [IPsec] [Schc] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Carsten Bormann
On 2023-12-11, at 13:11, Hannes Tschofenig wrote: > > @Carsten: I have not been following the ROHC work after standardization > was completed. Was it actually used? Is it still used? Hi Hannes, last I looked, ROHC was in wide use in 3GPP environments, probably mostly in conjunction with IMS.

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Hannes Tschofenig
Hi Daniel, Hi all, don't get me wrong: I am trying to be helpful. Integrating the functionality into SCHC alone is not enough. You need to integrate it into an implementation of IKEv2/IPsec that is suitable to the mentioned constrained IoT use cases. I have not seen IPsec/IKEv2 being used in

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Daniel Migault
Hi Paul, Please find my comments inline. Yours, Daniel On Mon, Dec 11, 2023 at 9:59 AM Paul Wouters wrote: > > > > > On Dec 11, 2023, at 08:53, Daniel Migault wrote: > > > >  > > What is not completely clear to me now is how we will be able to > have/make public implementations for linux

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Paul Wouters
> > On Dec 11, 2023, at 08:53, Daniel Migault wrote: > >  > What is not completely clear to me now is how we will be able to have/make > public implementations for linux implementation and potentially *Swan > projects. It is a bit too early for now, but I am hoping to have a path in > the

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Daniel Migault
Hi Hannes, One draft is esp, the other is ikev2, I tend to think it would be better to have two separate documents. Validation of specification SCHC will be supported by implementations and I am aware of two ongoing implementations based on openschc. I am also aware of 2 implementations that do

Re: [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension

2023-12-11 Thread Hannes Tschofenig
Shouldn't the two drafts be merged? Who of the authors is going to implement the specs? Ciao Hannes @Carsten: I have not been following the ROHC work after standardization was completed. Was it actually used? Is it still used? Am 30.11.2023 um 14:09 schrieb Carsten Bormann: As a