Ethernet Interfaces and Hub MIB (hubmib) Last Modified: 2007-08-15Additional information is available at tools.ietf.org/wg/hubmib Chair(s):Operations and Management Area Director(s):Operations and Management Area Advisor:Mailing Lists:General Discussion: hubmib@ietf.orgTo Subscribe: hubmib-request@ietf.org In Body: subscribe your_email_address Archive: http://www.ietf.org/mail-archive/web/hubmib/index.html Description of Working Group:The Ethernet Interfaces and Hub MIB WG is Chartered to definea set of managed objects that instrument devices, MAUs and interfaces that conform to the IEEE 802.3 standard for Ethernet. This set of objects should be largely compliant with, and even draw from IEEE 802.3, although there is no requirement that any specific object be present or absent. Close coordination with hardware standards development in IEEE 802.3 will be followed. The WG chair will support the communication with IEEE 802.3. When objects are added that require hardware support, IEEE 802.3 shall be informed, so that they consider to add them to their draft/standard. The MIB object definitions produced will be for use by SNMP and will be adequately consistent with other SNMP objects, standards and conventions. The working group will work on the following MIB modules for the IEEE 802.3ah (Ethernet First Mile) interfaces and devices: - Ethernet First Mile (EFM) MIB common attributes, OAM operations and statistics - Copper EFM MIB - Ethernet Passive Optical Networks (EPON) MIB The base for the definition of the managed objects in these MIB modules will be the management-related clauses in IEEE 802.3ah specification. The working group will also take into consideration management objects defined by other Working Groups in the IETF (ADSL MIB for example), or other standard bodies (G.983.2), will avoid work duplication, and describe the relationship with these specifications. The working group will also work on a revision of the MAU MIB so that it refers a IANA maintained TC for MAU types. This will allow to add new MAU types in the future as the Ethernet evolution requires without re-opening the MAU MIB RFC each time. Goals and Milestones:
Internet-Drafts:Ethernet in the First Mile Copper (EFMCu) Interfaces MIB (193153 bytes)Request For Comments:Definitions of Managed Objects for IEEE 802.3 Repeater Devices (RFC 1368) (83905 bytes) obsoleted by RFC 1516Definitions of Managed Objects for IEEE 802.3 Repeater Devices (RFC 1516) (82918 bytes) obsoletes RFC 1368/ obsoleted by RFC 2108 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (RFC 1515) (52828 bytes) obsoleted by RFC 3636 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 (RFC 2108) (166336 bytes) obsoletes RFC 1516 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 (RFC 2239) (80651 bytes) obsoleted by RFC 2668 Definitions of Managed Objects for the Ethernet-like Interface Types (RFC 2358) (87891 bytes) obsoleted by RFC 2665 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 (RFC 2668) (121843 bytes) obsoletes RFC 2239/ obsoleted by RFC 3636 Definitions of Object Identifiers for Identifying Ethernet Chip Sets (RFC 2666) (37699 bytes) Definitions of Managed Objects for the Ethernet-like Interface Types (RFC 2665) (110038 bytes) obsoletes RFC 2358/ obsoleted by RFC 3635 Definitions of Managed Objects for the Ethernet-like Interface Types (RFC 3635) (154476 bytes) obsoletes RFC 2665 Definition of Managed Objects for the Ethernet WAN Interface Sublayer (RFC 3637) (78785 bytes) Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (RFC 3636) (139990 bytes) obsoletes RFC 2668,RFC 1515/ obsoleted by RFC 4836 Applicability Statement for Reclassification of RFC 1643 to Historic Status (RFC 3638) (8676 bytes) obsoletes RFC 1643 Power Ethernet MIB (RFC 3621) (37294 bytes) Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (RFC 4836) (151012 bytes) obsoletes RFC 3636 Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces (RFC 4878) (130067 bytes) Managed Objects of Ethernet Passive Optical Networks (EPON) (RFC 4837) (206726 bytes) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||