RFC 3872 on Management Information Base for Telephony Routing over IP (TRIP)

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

        RFC 3872

        Title:      Management Information Base
                    for Telephony Routing over IP (TRIP)
        Author(s):  D. Zinman, D. Walker, J. Jiang
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    dzinman@rogers.com,
                    david.walker@sedna-wireless.com,
                    jjiang@syndesis.com
        Pages:      53
        Characters: 98614
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-iptel-trip-mib-10.txt

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

This memo defines a portion of the Management Information Base (MIB)
module for use with network management protocols in the Internet
community.  In particular, it describes a set of managed objects that
are used to manage Telephony Routing over IP (TRIP) devices.

This document is a product of the IP Telephony 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@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.