Internet Engineering Task Force (IETF) T. Taylor, Ed.
Request for Comments: 7448 PT Taylor Consulting
Category: Informational D. Romascanu
ISSN: 2070-1721 Avaya
February 2015
MIB Transfer from the IETF to the IEEE 802.3 WG
Taylor & Romascanu Informational [Page 1]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015
Copyright Notice
1. Introduction
[RFC4663], published in September 2006, described a plan for transferring responsibility for four MIB modules related to bridges from the IETF to IEEE 802.1. Some years later, responsibility for eight more MIB modules was transferred from the IETF Ethernet Interfaces and Hub MIB (hubmib) WG to the IEEE 802.3 WG. The MIB modules concerned are tabulated below (Section 2). [RFC4663] clearly enunciates the motivation for both transfers and also provides an introduction to IEEE standardization procedures. The discussions of those topics will not be repeated here.
Taylor & Romascanu Informational [Page 2]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015 2. IETF and Corresponding IEEE 802.3 MIB ModulesThis section tabulates the MIB modules that were transferred to IEEE 802.3, identifying the IETF source document, the corresponding clause of [IEEE802.3.1-2013], and the location of the MIB itself in ASCII format.
Taylor & Romascanu Informational [Page 3]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015
IETF MIB Name: EFM-CU-MIB IETF Reference: Ethernet in the First Mile Copper (EFMCu) Interfaces MIB [RFC5066] IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB IEEE 802.3.1-2013 Description: Clause 11, Ethernet in the First Mile copper (EFMCu) interfaces MIB module MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 802dot3dot1C11mib.txt3. Procedural Aspects of the Transfer 3.1. IEEE MIB Modules in ASCII FormatThe content of Section 2.2 of [RFC4663] is also accurate for this document.
Taylor & Romascanu Informational [Page 4]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015 3.2. OID Registration for New MIB ModulesThe IEEE 802.3 WG adopted the approach recommended in Section 2.3 of [RFC4663] of developing an IEEE MIB module and defining new compliance clauses under the IEEE OID branch. Information about the IEEE 802.3 Management Registration Arcs can be found at <http://www.ieee802.org/3/arcs/index.html>.
3.3. Mailing List Discussions
The Ethernet Interfaces and Hub MIB WG has completed its documents, and the WG was closed in September 2007. The mailing list stayed open for a while and was closed a few years later. The appropriate mailing list for IEEE 802.3 MIB modules discussion is STDS-802-3-MIB@LISTSERV.IEEE.ORG.
3.4. IETF MIB Doctor Reviews
The content of Section 5 of [RFC4663] is also accurate for this document, noting that from the point of view of the present document, 802.3 should replace 802.1 wherever it occurs in the text.
4. Security Considerations
This document records the transfer of ownership of Ethernet-related MIB modules to IEEE 802.3.1 several years ago. The transfer has no security implications.
5. Informative References
[IEEE802.3.1-2013]
Taylor & Romascanu Informational [Page 5]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Taylor & Romascanu Informational [Page 6]
RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015
Acknowledgements