IP Payload Compression Protocol: Difference between revisions

Revision as of 08:37, 18 September 2007

Latest revision as of 00:19, 4 March 2022

(26 intermediate revisions by 19 users not shown)

Line 1:

{{Primary sources|date=November 2007}}

{{csb-pageincludes|1=http://www.faqs.org/rfcs/rfc3173.html}}

For [[Computer network|networking]], the [[Internet Protocol]] '''IP Payload Compression Protocol''', or IPComp, is a low level compression protocol for [[Internet Protocol|IP]] [[datagram]]s defined in RFC 3173.<ref>{{cite web| url=http://tools.ietf.org/html/rfc3173 | title=RFC 3173 IP Payload Compression Protocol (IPComp) |accessdate=2008-01-18}}</ref> The intent is to reduce the size of data transmitted over congested or slow network connections, thereby increasing the speed of such networks without losing data. According to the RFC requirements, compression must be done before [[IP fragmentation|fragmenting]] or [[encrypting]] the packet. It further states that each datagram must be compressed independently so it can be decompressed even if received out of order. This is important because it allows IPComp to work with both [[Transmission Control Protocol|TCP]] and [[User Datagram Protocol|UDP]] network communications.

==References==

The IP Payload Compression Protocol, or IPComp, is a protocol for compression of IP datagrams.

{{Reflist}}

It is described in RFC 2393.

[[Category:Internet Protocol]]

{{internet-stub}}