[rfc-dist] RFC 3895 on Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Sep 24 09:23:00 PDT 2004

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

        RFC 3895

        Title:      Definitions of Managed Objects
                    for the DS1, E1, DS2, and E2 Interface Types
        Author(s):  O. Nicklass, Ed.
        Status:     Standards Track
        Date:       September 2004
        Mailbox:    orly_n at rad.com
        Pages:      84
        Characters: 163841
        Obsoletes:  2495

        I-D Tag:    draft-ietf-atommib-rfc2495bis-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3895.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 objects used for managing DS1, E1, DS2 
and E2 interfaces.  This document is a companion to the documents
that define Managed Objects for the DS0, DS3/E3 and Synchronous
Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
Types.  This document obsoletes RFC 2495.

This document is a product of the AToM 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

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.

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