Hi IESG, This new version addresses the remaining open DISCUSS items, namely:
- An IP protocol number has been early allocated and the text updated to indicate this allocation and use, as requested. - The text on ECN has been updated as requested. - The text on ICMP message handling has been expanded and made more explicit, as requested. I believe this clears all open DISCUSS, and if so would ask the owners of those DISCUSS items to clear them. Given this, I believe the document is now ready to progress. Thanks, Chris. internet-dra...@ietf.org writes:
A new version of I-D, draft-ietf-ipsecme-iptfs-19.txt has been successfully submitted by Christian Hopps and posted to the IETF repository. Name: draft-ietf-ipsecme-iptfs Revision: 19 Title: IP-TFS: Aggregation and Fragmentation Mode for ESP and its Use for IP Traffic Flow Security Document date: 2022-09-04 Group: ipsecme Pages: 37 URL: https://www.ietf.org/archive/id/draft-ietf-ipsecme-iptfs-19.txt Status: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-iptfs/ Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-ipsecme-iptfs Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-ipsecme-iptfs-19 Abstract: This document describes a mechanism for aggregation and fragmentation of IP packets when they are being encapsulated in ESP payloads. This new payload type can be used for various purposes such as decreasing encapsulation overhead for small IP packets; however, the focus in this document is to enhance IPsec traffic flow security (IP-TFS) by adding Traffic Flow Confidentiality (TFC) to encrypted IP encapsulated traffic. TFC is provided by obscuring the size and frequency of IP traffic using a fixed-sized, constant-send-rate IPsec tunnel. The solution allows for congestion control as well as non- constant send-rate usage. The IETF Secretariat
_______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
