Skip to main content

IP Payload Compression excluding transport layer
draft-ls-6man-ipcomp-exclude-transport-layer-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Cheng Li , Hang Shi , Meng Zhang , Xiaobo Ding
Last updated 2023-04-22 (Latest revision 2022-10-19)
Replaced by draft-ls-ipsecme-ipcomp-exclude-transport-layer
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

IP Payload Compression Protocol (IPComp) is used for compressing the IP payload in transmission to increase the communication performance. The IPComp is applied to payload of the IP datagram, starting with the first octet immediately after the IP header in IPv4, and starting with 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.

Authors

Cheng Li
Hang Shi
Meng Zhang
Xiaobo Ding

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)