RFC1604 on Frame Relay Service MIB

"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 25 March 1994 18:37 UTC

Message-Id: <199403251833.AA20741@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1604 on Frame Relay Service MIB
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 25 Mar 1994 10:33:06 -0800
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1604:

        Title:      Definitions of Managed Objects for Frame Relay
                    Service 
        Author:     T. Brown, Editor
        Mailbox:    tacox@mail.bellcore.com
        Pages:      46
        Characters: 88,770
        Obsoletes:  1596


This memo defines an extension to the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets.  In particular, it defines objects for managing the Frame
Relay Service.  This RFC is the product of the Frame Relay Service MIB
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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  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@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
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://ds.internic.net/rfc/rfc1604.txt"><ftp://ds.internic.net/rfc/rfc1604.txt>

RFC1604 on Frame Relay Service MIB Joyce K. Reynolds