RFC 4837: Managed Objects of Ethernet Passive Optical Networks (EPON)
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 interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4837
- Published
- July 2007
- Authors
- L. Khermosh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 91
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 4875Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)Updated
May 2007
- RFC 4461Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)Current
April 2006
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
- RFC 6425Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP PingCurrent
November 2011
- RFC 6456Multi-Segment Pseudowires in Passive Optical NetworksCurrent
November 2011
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?