Internet DRAFT - draft-ietf-x25mib-lapbmib
A new Request for Comments is now available in online RFC libraries.
Title: SNMP MIB Extension for X.25 LAPB
Author: D. Throop, F. Baker
Mailbox: firstname.lastname@example.org, email@example.com
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 the Link Layer of X.25,
LAPB. The objects defined here, along with the objects in the "SNMP
MIB Extension for the Packet Layer of X.25" and the "Definitions of
Managed Objects for RS-232-like Hardware Devices", combine to allow
management of an X.25 protocol stack. This RFC was produced by the
X25mib Working Group of the 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@NRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
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:
Subject: getting 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
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
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retreive the ASCII version
of the RFCs.
Content-Type: Multipart/Alternative; Boundary="OtherAccess"