Skip to main content

Management Information Base for the PINT Services Architecture
draft-ietf-pint-mib-05

The information below is for an old version of the document that is already published as an RFC.
Document Type This is an older version of an Internet-Draft that was ultimately published as an RFC.
Authors Murali Krishnaswamy , Dan Romascanu
Last updated 2013-03-02 (Latest revision 2000-11-16)
Stream Internet Engineering Task Force (IETF)
Formats
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3055 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-pint-mib-05
A new Request for Comments is now available in online RFC libraries.

        RFC 3055

        Title:      Management Information Base for the PINT Services
                    Architecture 
        Author(s):  M. Krishnaswamy, D. Romascanu
        Status:     Standards Track
        Date:       February 2001
        Mailbox:    murali@lucent.com, dromasca@avaya.com
        Pages:      21
        Characters: 39315
        Updates/Obsoletes/SeeAlso:    None        

        I-D Tag:    draft-ietf-pint-mib-05.txt

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

This memo describes a proposed Management Information Base (MIB) for
the PSTN/Internet Interworking (PINT) Services Architecture.

This document is a product of the PSTN and Internet Internetworking
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.echo 
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.