home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_q_t
/
draft-ietf-trunkmib-ds1e1mib-02.txt
< prev
next >
Wrap
Text File
|
1993-03-03
|
2KB
|
68 lines
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 1406:
Title: Definitions of Managed Objects for the DS1 and E1
Interface Types
Author: F. Baker & J. Watt, Editors
Mailbox: fbaker@acc.com, james@newbridge.com
Pages: 50
Characters: 97,559
Obsoletes: RFC 1232
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing DS1 Interfaces --
including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.
This document entirely replaces RFC 1232, which contains a fundamental
error: many objects are encoded as Counters that must be encoded as
INTEGERs or Gauges. The magnitude of the change required is
sufficient that virtually every object changed. Therefore, the MIB
documented in RFC 1232 should not be implemented. This document was
produced by the Trunk MIB Working Group of the Internet Engineering
Task Force (IETF).
This is now a Proposed Standard Protocol.
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" 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 NIC@NIC.DDN.MIL. 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 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute