Definitions of Managed Objects for the Ethernet WAN Interface Sublayer

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (hubmib WG)
Author C. Heard 
Last updated 2015-10-14 (latest revision 2003-03-21)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 3637 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Bert Wijnen
IESG note Requested to go on IESG agenda on June 12th
Responsible: bwijnen/iesg
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3637

        Title:      Definitions of Managed Objects
                    for the Ethernet WAN Interface Sublayer
        Author(s):  C.M. Heard, Ed.
        Status:     Standards Track
        Date:       September 2003
        Pages:      37
        Characters: 78785
        Updates/Obsoletes/SeeAlso:    None

        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@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@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.