RFC 4836: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
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 the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This document obsoletes RFC 3636. It amends that specification by moving MAU type OBJECT-IDENTITY definitions and relevant textual conventions into a separate Internet Assigned Number Authority (IANA) maintained MIB module. In addition, management information is added to enable support for Ethernet in the First Mile (EFM) and 10GBASE-CX4 MAUs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4836
- Published
- April 2007
- Authors
- E. Beili
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 67
- Also known as
- —
- Obsoletes:
- RFC 3636
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 1515 (1993)
- RFC 2239 (1997)
- RFC 2668 (1999)
- RFC 3636 (2003)
- RFC 4836 (2007)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4747The Virtual Fabrics MIBCurrent
November 2006
- RFC 4935Fibre Channel Fabric Configuration Server MIBCurrent
August 2007
- RFC 4936Fibre Channel Zone Server MIBCurrent
August 2007
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4711Real-time Application Quality-of-Service Monitoring (RAQMON) MIBCurrent
October 2006
- RFC 4706Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)Current
November 2006
- RFC 4983Fibre Channel Registered State Change Notification (RSCN) MIBCurrent
August 2007
- RFC 4626MIB for Fibre Channel's Fabric Shortest Path First (FSPF) ProtocolCurrent
September 2006
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?