RFC 4224: RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets
In plain English — editorial summary, not part of the RFC
RObust Header Compression (ROHC), RFC 3095, defines a framework for header compression, along with a number of compression protocols (profiles). One operating assumption for the profiles defined in RFC 3095 is that the channel between compressor and decompressor is required to maintain packet ordering. This document discusses aspects of using ROHC over channels that can reorder packets. It provides guidelines on how to implement existing profiles over such channels, as well as suggestions for the design of new profiles. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4224
- Published
- January 2006
- Authors
- G. Pelletier; L-E. Jonsson; K. Sandlund
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 21
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4230RSVP Security PropertiesCurrent
December 2005
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4172iFCP - A Protocol for Internet Fibre Channel Storage NetworkingUpdated
September 2005
- RFC 4171Internet Storage Name Service (iSNS)Current
September 2005
- RFC 4164RObust Header Compression (ROHC): Context Replication for ROHC ProfilesCurrent
September 2005
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4296The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet ProtocolsCurrent
December 2005
- RFC 4297Remote Direct Memory Access (RDMA) over IP Problem StatementCurrent
December 2005
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?