Definitions of Managed Objects for RObust Header Compression (ROHC)
RFC 3816

Document Type RFC - Proposed Standard (June 2004; Errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3816 (Proposed Standard)
Telechat date
Responsible AD Allison Mankin
Send notices to <cabo@tzi.org>, <lars-erik.jonsson@ericsson.com>
Network Working Group                                         J. Quittek
Request for Comments: 3816                                M. Stiemerling
Category: Standards Track                                            NEC
                                                          H. Hartenstein
                                                 University of Karlsruhe
                                                               June 2004

  Definitions of Managed Objects for RObust Header Compression (ROHC)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   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.

Quittek, et al.             Standards Track                     [Page 1]
RFC 3816                        ROHC MIB                       June 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  The Internet-Standard Management Framework . . . . . . . . . .  2
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Structure of the MIB modules . . . . . . . . . . . . . . . . .  3
       4.1. The ROHC-MIB module . . . . . . . . . . . . . . . . . . .  4
            4.1.1. rohcChannelTable . . . . . . . . . . . . . . . . .  5
            4.1.2. rohcInstanceTable. . . . . . . . . . . . . . . . .  5
            4.1.3. rohcProfileTable . . . . . . . . . . . . . . . . .  6
            4.1.4. rohcContextTable . . . . . . . . . . . . . . . . .  7
       4.2. The ROHC-UNCOMPRESSED-MIB module. . . . . . . . . . . . .  8
            4.2.1. rohcUncmprContextTable . . . . . . . . . . . . . .  8
       4.3. The ROHC-RTP-MIB module . . . . . . . . . . . . . . . . .  8
            4.3.1. rohcRtpContextTable. . . . . . . . . . . . . . . .  8
            4.3.2. rohcPacketSizeTable. . . . . . . . . . . . . . . .  9
   5.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Security Considerations. . . . . . . . . . . . . . . . . . . . 50
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 51
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 51
       8.1. Normative References. . . . . . . . . . . . . . . . . . . 51
       8.2. Informative References. . . . . . . . . . . . . . . . . . 52
   9.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 52
   10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 53

1.  Introduction

   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.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14, RFC 2119 [RFC2119].

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB

Quittek, et al.             Standards Track                     [Page 2]
Show full document text