RFC 3637 on Definitions of Managed Objects for the Ethernet WAN Interface Sublayer
<rfc-editor <at> rfc-editor.org>
2003-10-01 18:35:27 GMT
A new Request for Comments is now available in online RFC libraries.
Title: Definitions of Managed Objects
for the Ethernet WAN Interface Sublayer
Author(s): C.M. Heard, Ed.
Status: Standards Track
Date: September 2003
Mailbox: heard <at> pobox.com
I-D Tag: draft-ietf-hubmib-wis-mib-07.txt
This document 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
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).
The MIB module defined in this memo is an extension of the Synchronous
Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
MIB and is implemented in conjunction with it and with the
Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the
Interfaces Group MIB, and the Inverted Stack Table MIB.
This document is a product of the Ethernet Interfaces and Hub 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
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.
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
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
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.