RFC 2393: IP Payload Compression Protocol (IPComp)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3173.
Current version: RFC 3173 — IP Payload Compression Protocol (IPComp)
In plain English — editorial summary, not part of the RFC
This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2393
- Published
- December 1998
- Authors
- A. Shacham; R. Monsour; R. Pereira; M. Thomas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 3173
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2395IP Payload Compression Using LZSCurrent
December 1998
- RFC 2394IP Payload Compression Using DEFLATECurrent
December 1998
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 2391Load Sharing using IP Network Address Translation (LSNAT)Current
August 1998
- RFC 2375IPv6 Multicast Address AssignmentsCurrent
July 1998
- RFC 2373IP Version 6 Addressing ArchitectureObsoleted
July 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?