IP Payload Compression Protocol (IPComp) (RFC2393)
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
A. Shacham: AUTHOR [+4]
This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment.
Network Working Group A. Shacham
Request for Comments: 2393 Cisco
Category: Standards Track R. Monsour
IP Payload Compression Protocol (IPComp)
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document describes a protocol intended to provide lossless
compression for Internet Protocol datagrams in an Internet
IP payload compression is a protocol to reduce the size of IP
datagrams. This protocol will increase the overall communication
performance between a pair of communicating hosts/gateways ("nodes")
by compressing the datagrams, provided the nodes have sufficient
computation power, through either CPU capacity or a compression
coprocessor, and the communication is over slow or congested links.
IP payload compression is especially useful when encryption is
applied to IP datagrams. Encrypting the IP datagram causes the data
to be random in nature, rendering compression at lower protocol
layers (e.g., PPP Compression Control Protocol [RFC-1962])
ineffective. If both compression and encryption are required,
compression MUST be applied before encryption.
This document defines the IP payload compression protocol (IPComp),
the IPComp packet structure, the IPComp Association (IPCA), and
several methods to negotiate the IPCA.
Other documents shall specify how a specific compression algorithm
can be used with the IP payload compression protocol. Such
algorithms are beyond the scope of this document.
1.1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this