[rfc-dist] RFC 3816 on Definitions of Managed Objects for RObust Header Compression (ROHC)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Jun 9 17:05:03 PDT 2004


A new Request for Comments is now available in online RFC libraries.


        RFC 3816

        Title:      Definitions of Managed Objects for RObust Header
                    Compression (ROHC)
        Author(s):  J. Quittek, M. Stiemerling, H. Hartenstein
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    quittek at netlab.nec.de, stiemerling at netlab.nec.de,
                    hartenstein at rz.uni-karlsruhe.de
        Pages:      53
        Characters: 104947
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rohc-mib-rtp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3816.txt


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.

This document is a product of the Robust Header Compression Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list