Ethernet Interfaces and Hub MIB (hubmib) ---------------------------------------- Charter Last Modified: 2007-01-30 Current Status: Active Working Group Chair(s): Bert Wijnen Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Mailing Lists: General Discussion:hubmib@ietf.org To 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 define a 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: Done Meet at the 41st IETF to discuss implementation experience of RFC 2108 and RFC 2239, and to consider future extensions for Full Duplex operation and 1 Gigabit Ethernet Speeds Done Gather implementation experience feedback concerning RFC 2108 and RFC 2239 Done Post Internet-Draft(s) for Full Duplex and 1 Gigabit Ethernet MIB extensions Done Meet at the 42nd IETF to discuss the Internet-Draft(s) and issue recomendations concerning advancement of RFC 2108 and RFC 2239 on the standards track Done Post revised Internet-Draft(s) Done Conduct WG Last Call on Internet-Draft(s) Done Submit final version of the Internet-Draft(s) to the IESG for consideration as Proposed Standards Done Submit revised version of the Internet-Drafts, following the Area Directorate review Done Submit final versions of the MAU MIB and Ethernet-like Interfaces MIB Internet-Draft(s) to the IESG for consideration as Proposed Standards Done Submit the Ethernet Chipsets document to IESG for consideration as an Informational RFC Done Begin identifying new work items for future work Done Issue WG Drafts for MIBs for P802.3ae & P802.3af Done Issue revised WG Drafts for MIBs for P802.3ae/P802.3af Done Gather implementation experience concerning WG documents already on the standards track Done WG Last Call All documents Done Issue revised WG drafts for existing stds track documents if so required by the implementation reports Done Forward Internet-Drafts to the AD/IESG Stds track considerations Done Power Ethernet MIB Last Call Done Submit Power Ethernet MIB to AD/IESG for Standards track consideration Done Individual submissions for the EFM MIB modules Done First round of WG Internet-Drafts for the EFM MIB modules Done Working Group Last Call Done Second Working Group Last Call for (3) EFM MIB documents Done Initial Draft for updated MAU MIB document Done Submit EFM-MIB for consideration as Proposed Standard Done Submit EFM-EPON-MIB for consideration as Proposed Standard Done WG Last Call for updated MAU MIB document Done Submit updated MAU MIB document to the IESG for consideration as a Proposed standard, replacing RFC 3636 Apr 2007 Submit EFM-CU-MIB for consideration as Proposed Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jan 2004 Feb 2007 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC1368 PS Oct 1992 Definitions of Managed Objects for IEEE 802.3 Repeater Devices RFC1516 DS Sep 1993 Definitions of Managed Objects for IEEE 802.3 Repeater Devices RFC1515 PS Sep 1993 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) RFC2108 PS Feb 1997 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 RFC2239 PS Nov 1997 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 RFC2358 PS Jun 1998 Definitions of Managed Objects for the Ethernet-like Interface Types RFC2668 PS Sep 1999 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 RFC2666 I Sep 1999 Definitions of Object Identifiers for Identifying Ethernet Chip Sets RFC2665 PS Sep 1999 Definitions of Managed Objects for the Ethernet-like Interface Types RFC3635 PS Oct 2003 Definitions of Managed Objects for the Ethernet-like Interface Types RFC3637 PS Oct 2003 Definition of Managed Objects for the Ethernet WAN Interface Sublayer RFC3636 PS Oct 2003 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) RFC3638 I Oct 2003 Applicability Statement for Reclassification of RFC 1643 to Historic Status RFC3621Standard Jan 2004 Power Ethernet MIB RFC4836 PS Apr 2007 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) RFC4878 PS Jun 2007 Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces RFC4837 PS Jul 2007 Managed Objects of Ethernet Passive Optical Networks (EPON)