RFC 3816: Definitions of Managed Objects for RObust Header Compression (ROHC)
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow monitoring of running instances of RObust Header Compression (ROHC). The managed objects defined in this memo are grouped into three MIB modules. The ROHC-MIB module defines managed objects shared by all ROHC profiles, the ROHC-UNCOMPRESSED-MIB module defines managed objects specific to the ROHC uncompressed profile, the ROHC-RTP-MIB module defines managed objects specific to the ROHC RTP (Real-Time Transport Protocol) profile, the ROHC UDP (User Datagram Protocol) profile, the ROHC ESP (Encapsulating Security Payload) profile, and the ROHC LLA (Link Layer Assisted) profile. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3816
- Published
- June 2004
- Authors
- J. Quittek; M. Stiemerling; H. Hartenstein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 53
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3843RObust Header Compression (ROHC): A Compression Profile for IPUpdated
June 2004
- RFC 4008Definitions of Managed Objects for Network Address Translators (NAT)Obsoleted
March 2005
- RFC 3559Multicast Address Allocation MIBCurrent
June 2003
- RFC 3408Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) ProfileCurrent
December 2002
- RFC 3289Management Information Base for the Differentiated Services ArchitectureCurrent
June 2002
- RFC 4369Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)Obsoleted
January 2006
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3241Robust Header Compression (ROHC) over PPPUpdated
May 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?