RFC 3096: Requirements for robust IP/UDP/RTP header compression
In plain English — editorial summary, not part of the RFC
This document contains requirements for robust IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) header compression to be developed by the ROHC (Robust Header Compression) WG. It is based on the ROHC charter, discussions in the WG, the 3GPP document "3GPP TR 23.922", version 1.0.0 of October 1999, as well as contributions from 3G.IP. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3096
- Published
- July 2001
- Authors
- M. Degermark
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 2395IP Payload Compression Using LZSCurrent
December 1998
- RFC 2394IP Payload Compression Using DEFLATECurrent
December 1998
- RFC 2393IP Payload Compression Protocol (IPComp)Obsoleted
December 1998
- RFC 2354Options for Repair of Streaming MediaCurrent
June 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?