RFC 5858: IPsec Extensions to Support Robust Header Compression over IPsec
In plain English — editorial summary, not part of the RFC
Integrating Robust Header Compression (ROHC) with IPsec (ROHCoIPsec) offers the combined benefits of IP security services and efficient bandwidth utilization. However, in order to integrate ROHC with IPsec, extensions to the Security Policy Database (SPD) and Security Association Database (SAD) are required. This document describes the IPsec extensions required to support ROHCoIPsec. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5858
- Published
- May 2010
- Authors
- E. Ertekin; C. Christou; C. Bormann
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5857IKEv2 Extensions to Support Robust Header Compression over IPsecCurrent
May 2010
- RFC 5856Integration of Robust Header Compression over IPsec Security AssociationsCurrent
May 2010
- RFC 5225RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-LiteCurrent
April 2008
- RFC 3843RObust Header Compression (ROHC): A Compression Profile for IPUpdated
June 2004
- RFC 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 3409Lower Layer Guidelines for Robust RTP/UDP/IP Header CompressionCurrent
December 2002
- RFC 3408Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) ProfileCurrent
December 2002
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
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?