RFC 3055 on PINT MIB

RFC Editor <rfc-ed@ISI.EDU> Sat, 10 February 2001 01:29 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05767; Fri, 9 Feb 2001 20:29:11 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA26972 for ietf-123-outbound.10@ietf.org; Fri, 9 Feb 2001 20:15:00 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA26943 for <all-ietf@loki.ietf.org>; Fri, 9 Feb 2001 20:07:57 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05486 for <all-ietf@ietf.org>; Fri, 9 Feb 2001 20:07:54 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA05410; Fri, 9 Feb 2001 17:07:49 -0800 (PST)
Message-Id: <200102100107.RAA05410@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3055 on PINT MIB
Cc: rfc-ed@ISI.EDU, pint@lists.bell-labs.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 09 Feb 2001 17:07:49 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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.


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.
ftp://ftp.isi.edu/in-notes/rfc3055.txt"><ftp://ftp.isi.edu/in-notes/rfc3055.txt>