RFC 4164: RObust Header Compression (ROHC): Context Replication for ROHC Profiles
In plain English — editorial summary, not part of the RFC
This document defines context replication, a complement to the context initialization procedure found in Robust Header Compression (ROHC), as specified in RFC 3095. Profiles defining support for context replication may use the mechanism described herein to establish a new context based on another already existing context. Context replication is introduced to reduce the overhead of the context establishment procedure. It may be especially useful for the compression of multiple short-lived flows that may be occurring simultaneously or near-simultaneously, such as short-lived TCP flows. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4164
- Published
- September 2005
- Authors
- G. Pelletier
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9154Extensible Provisioning Protocol (EPP) Secure Authorization Information for TransferCurrent
December 2021
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4171Internet Storage Name Service (iSNS)Current
September 2005
- RFC 4172iFCP - A Protocol for Internet Fibre Channel Storage NetworkingUpdated
September 2005
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4224RObust Header Compression (ROHC): ROHC over Channels That Can Reorder PacketsCurrent
January 2006
- RFC 4230RSVP Security PropertiesCurrent
December 2005
- RFC 4097Middlebox Communications (MIDCOM) Protocol EvaluationUpdated
June 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?