RFC 3637: Definitions of Managed Objects for the Ethernet WAN Interface Sublayer
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3637
- Published
- October 2003
- Authors
- C.M. Heard
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3635Definitions of Managed Objects for the Ethernet-like Interface TypesCurrent
October 2003
- RFC 3621Power Ethernet MIBCurrent
December 2003
- RFC 3606Definitions of Supplemental Managed Objects for ATM InterfaceCurrent
November 2003
- RFC 3595Textual Conventions for IPv6 Flow LabelCurrent
September 2003
- RFC 3593Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
September 2003
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 3705High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
February 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?