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

2023-12-12 Thread hannes . tschofenig=40gmx . net
Migault Cc: ipsec@ietf.org; s...@ietf.org Subject: Re: [Schc] [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet-esp and draft-mglt-ipsecme-ikev2-diet-esp-extension Let me reply to Hannes’ statement: “Integrating the functionality into SCHC alone is not enough.” I consider SCHC

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

2023-12-12 Thread Eric Vyncke (evyncke)
COAP. Regards -éric From: Schc on behalf of Hannes Tschofenig Date: Monday, 11 December 2023 at 18:03 To: Daniel Migault , Hannes Tschofenig Cc: Carsten Bormann , Tero Kivinen , ipsec@ietf.org , s...@ietf.org Subject: Re: [Schc] [IPsec] WG Adoption calls for draft-mglt-ipsecme-diet

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.