Shihang(Vincent) writes: > Hi Tero, > We moved our draft of IPComp extension from 6man to IPSecMe because > people told me that IPComp IANA registry is in the IPSec. However > the extension itself is not related to encryption. I wonder if the > IPSecMe is the right place for the draft.
It is not, especially as if I remember reight the compressed payload is inside the encrypted payload, thus even if you do not compress the first four octets, they still will be encrypted, thus there is no visibility to them. Where are you trying to use this IPcomp if it is not inside IPsec? On the other hand I do not think current implemetatons of IPsec actually supprot IPcomp mostly because there are some security issues with it, as it may allow different traffic analysis methods to be used which are not available if packets are nott compressed. > I am on site at Brisbane. It would be much appreciated if you have > some time for a quick F2F discussion. > > Thanks, > Hang > > -----Original Message----- > From: I-D-Announce <i-d-announce-boun...@ietf.org> On Behalf Of > internet-dra...@ietf.org > Sent: 2024年2月28日 20:58 > To: i-d-annou...@ietf.org > Subject: I-D Action: draft-ls-ipsecme-ipcomp-exclude-transport-layer-00.txt > > Internet-Draft draft-ls-ipsecme-ipcomp-exclude-transport-layer-00.txt is now > available. > > Title: IP Payload Compression excluding transport layer > Authors: Cheng Li > Hang Shi > Meng Zhang > Xiaobo Ding > Name: draft-ls-ipsecme-ipcomp-exclude-transport-layer-00.txt > Pages: 8 > Dates: 2024-02-28 > > Abstract: > > IP Payload Compression Protocol (IPComp) is used for compressing the > IP payload in transmission to increase communication performance. > The IPComp is applied to the payload of the IP datagram, starting > with the first octet immediately after the IP header in IPv4, and the > first octet after the excluded IPv6 Extension headers. However, > transport layer information such as source port and destination port > are useful in many network functions in transmission. > > This document defines extensions of IP payload compression protocol > (IPComp) to support compressing the payload excluding the transport > layer information, to enable network functions using transport layer > information (e.g., ECMP) working together with the payload > compression. This document also defines an extension of IPComp to > indicate the payload is not compressed to solve the out-of-order > problems between the compressed and uncompressed packets. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ls-ipsecme-ipcomp-exclude-transport-layer/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ls-ipsecme-ipcomp-exclude-transport-layer-00.html > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > I-D-Announce mailing list > i-d-annou...@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > -- kivi...@iki.fi _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
