Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

IP Payload Compression Protocol (IPComp) (RFC2393)

IP.com Disclosure Number: IPCOM000002966D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 8 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Shacham: AUTHOR [+4]

Abstract

This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group A. Shacham

Request for Comments: 2393 Cisco

Category: Standards Track R. Monsour

Hi/fn

R. Pereira

TimeStep

M. Thomas

AltaVista Internet

December 1998

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 Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

This document describes a protocol intended to provide lossless

compression for Internet Protocol datagrams in an Internet

environment.

1. Introduction

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

document are to be interpreted as described in RFC 2119 [RFC-2119].

2. Compression Process

The compression processing of IP datagrams has two phases:

compressing of outbound IP datagrams ("compression") and

decompressing of inbound datagrams ("decompression"). The

compression processing MUST be lossless, ensuring that the IP

datagram, after being c...