Hi, Please find the document describing Diet-ESP. The compression mechanism is not being described using SCHC. We initially thought of updating the document with SCHC and so wait for SCHC to be published. On the other hand this is not mandatory and we would like to understand if the WG has an opinion.
In any case, i believe the document is sufficiently advanced to get adopted. Yours, Daniel ________________________________________ From: internet-dra...@ietf.org <internet-dra...@ietf.org> Sent: Friday, May 13, 2022 12:29 PM To: Carsten Bormann; Daniel Migault; David Schinazi; Tobias Guggemos Subject: New Version Notification for draft-mglt-ipsecme-diet-esp-08.txt A new version of I-D, draft-mglt-ipsecme-diet-esp-08.txt has been successfully submitted by Daniel Migault and posted to the IETF repository. Name: draft-mglt-ipsecme-diet-esp Revision: 08 Title: ESP Header Compression and Diet-ESP Document date: 2022-05-13 Group: Individual Submission Pages: 53 URL: https://www.ietf.org/archive/id/draft-mglt-ipsecme-diet-esp-08.txt Status: https://datatracker.ietf.org/doc/draft-mglt-ipsecme-diet-esp/ Htmlized: https://datatracker.ietf.org/doc/html/draft-mglt-ipsecme-diet-esp Diff: https://www.ietf.org/rfcdiff?url2=draft-mglt-ipsecme-diet-esp-08 Abstract: With the use of encrypted ESP for secure IP communication, the compression of IP payload is only possible with complex frameworks, such as RObust Header Compression (ROHC). Such frameworks are too complex for numerous use cases and especially for IoT scenarios, which makes IPsec not being used here, although it offers architectural benefits. ESP Header Compression (EHC) defines a flexible framework to compress communications protected with IPsec/ESP. Compression and decompression is defined by EHC Rules orchestrated by EHC Strategies. The necessary state is hold within the IPsec Security Association and can be negotiated during key agreement, e.g. with IKEv2. The document specifies the necessary parameters of the EHC Context to allow compression of ESP and the most common included protocols, such as IPv4, IPv6, UDP and TCP and the corresponding EHC Rules. It also defines the Diet-ESP EHC Strategy which compresses up to 32 bytes per packet for traditional IPv6 VPN and up to 66 bytes for IPv6 VPN sent over a single TCP or UDP session. The IETF Secretariat _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
