GENWiki

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

Abstract

 This document records the transfer of responsibility for the
 Ethernet-related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB,
 POWER-ETHERNET-MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB,
 ETHER-WIS, and MAU-MIB from the IETF to the IEEE 802.3 Working Group
 (WG).  This document also describes the procedures associated with
 the transfer in a similar way to how RFC 4663 records the transfer of
 the IETF Bridge MIB work to the IEEE 802.1 WG.

Status of This Memo

 This document is not an Internet Standards Track specification; it is
 published for informational purposes.

 This document is a product of the Internet Engineering Task Force
 (IETF).  It represents the consensus of the IETF community.  It has
 received public review and has been approved for publication by the
 Internet Engineering Steering Group (IESG).  Not all documents
 approved by the IESG are a candidate for any level of Internet
 Standard; see Section 2 of RFC 5741.

 Information about the current status of this document, any errata,
 and how to provide feedback on it may be obtained at
 http://www.rfc-editor.org/info/rfc7448.

Taylor & Romascanu Informational [Page 1] RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015

Copyright Notice

 Copyright (c) 2015 IETF Trust and the persons identified as the
 document authors.  All rights reserved.

 This document is subject to BCP 78 and the IETF Trust's Legal
 Provisions Relating to IETF Documents
 (http://trustee.ietf.org/license-info) in effect on the date of
 publication of this document.  Please review these documents
 carefully, as they describe your rights and restrictions with respect
 to this document.  Code Components extracted from this document must
 include Simplified BSD License text as described in Section 4.e of
 the Trust Legal Provisions and are provided without warranty as
 described in the Simplified BSD License.

Table of Contents

 1. Introduction ....................................................2
 2. IETF and Corresponding IEEE 802.3 MIB Modules ...................3
 3. Procedural Aspects of the Transfer ..............................4
    3.1. IEEE MIB Modules in ASCII Format ...........................4
    3.2. OID Registration for New MIB Modules .......................5
    3.3. Mailing List Discussions ...................................5
    3.4. IETF MIB Doctor Reviews ....................................5
 4. Security Considerations .........................................5
 5. Informative References ..........................................5
 Acknowledgements ...................................................7
 Authors' Addresses .................................................7

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.

 The IEEE version of this second lot of transferred MIB modules was
 published as 802.3.1-2011 in February 2011.  The IEEE 802.3.1
 specification was subsequently updated.  The latest version, IEEE
 802.3.1-2013 [IEEE802.3.1-2013], is the basis for this document.

Taylor & Romascanu Informational [Page 2] RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015

2. IETF and Corresponding IEEE 802.3 MIB Modules

 This 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.

 IETF MIB Name: DOT3-OAM-MIB
 IETF Reference: Definitions and Managed Objects for Operations,
 Administration, and Maintenance (OAM) Functions on Ethernet-Like
 Interfaces [RFC4878]
 IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB
 IEEE 802.3.1-2013 Description: Clause 6, Ethernet operations,
 administration, and maintenance (OAM) MIB module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C6mib.txt

 IETF MIB Name: SNMP-REPEATER-MIB
 IETF Reference: Definitions of Managed Objects for IEEE 802.3
 Repeater Devices using SMIv2 [RFC2108]
 IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB
 IEEE 802.3.1-2013 Description: Clause 7, Ethernet repeater device MIB
 module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C7mib.txt

 IETF MIB Name: POWER-ETHERNET-MIB
 IETF Reference: Power Ethernet MIB [RFC3621]
 IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB
 IEEE 802.3.1-2013 Description: Clause 8, Ethernet data terminal
 equipment (DTE) power via medium dependent interface (MDI) MIB module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C8mib.txt

 IETF MIB Name: DOT3-EPON-MIB
 IETF Reference: Managed Objects of Ethernet Passive Optical Networks
 (EPON) [RFC4837]
 IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB
 IEEE 802.3.1-2013 Description: Clause 9, Ethernet passive optical
 networks (EPON) MIB module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C9mib.txt

Taylor & Romascanu Informational [Page 3] RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015

 IETF MIB Name: EtherLike-MIB
 IETF Reference: Definitions of Managed Objects for the Ethernet-like
 Interface Types [RFC3635]
 IEEE 802.3 MIB Name: IEEE8023-Etherlike-MIB
 IEEE 802.3.1-2013 Description: Clause 10, Ethernet-like interface MIB
 module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C10mib.txt

 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.txt

 IETF MIB Name: ETHER-WIS
 IETF Reference: Definitions of Managed Objects for the Ethernet WAN
 Interface Sublayer [RFC3637]
 IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB
 IEEE 802.3.1-2013 Description: Clause 12, Ethernet wide area network
 (WAN) interface sublayer (WIS) MIB module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C12mib.txt

 IETF MIB Name: MAU-MIB
 IETF Reference: Definitions of Managed Objects for IEEE 802.3 Medium
 Attachment Units (MAUs) [RFC4836]
 IEEE 802.3 MIB Name: IEEE8023-MAU-MIB
 IEEE 802.3.1-2013 Description: Clause 13, Ethernet medium attachment
 units (MAUs) MIB module
 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
 802dot3dot1C13mib.txt

3. Procedural Aspects of the Transfer

3.1. IEEE MIB Modules in ASCII Format

 The 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 Modules

 The 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.

 To see general information about 802.3, including how they work and
 how to participate, go to <http://www.ieee802.org/3/>.

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]
            IEEE Computer Society, "IEEE Standard for Management
            Information Base (MIB) Definitions for Ethernet", June
            2013.

 [RFC2108]  de Graaf, K., Romascanu, D., McMaster, D., and K.
            McCloghrie, "Definitions of Managed Objects for IEEE 802.3
            Repeater Devices using SMIv2", RFC 2108, February 1997,
            <http://www.rfc-editor.org/info/rfc2108>.

 [RFC3621]  Berger, A. and D. Romascanu, "Power Ethernet MIB", RFC
            3621, December 2003,
            <http://www.rfc-editor.org/info/rfc3621>.

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
            Ethernet-like Interface Types", RFC 3635, September 2003,
            <http://www.rfc-editor.org/info/rfc3635>.

 [RFC3637]  Heard, C., "Definitions of Managed Objects for the
            Ethernet WAN Interface Sublayer", RFC 3637, September
            2003, <http:///www.rfc-editor.org/info/rfc3637>.

 [RFC4663]  Harrington, D., "Transferring MIB Work from IETF Bridge
            MIB WG to IEEE 802.1 WG", RFC 4663, September 2006,
            <http://www.rfc-editor.org/info/rfc4663>.

 [RFC4836]  Beili, E., "Definitions of Managed Objects for
            IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836,
            April 2007, <http:///www.rfc-editor.org/info/rfc4836>.

 [RFC4837]  Khermosh, L., "Managed Objects of Ethernet Passive Optical
            Networks (EPON)", RFC 4837, July 2007,
            <http://www.rfc-editor.org/info/rfc4837>.

 [RFC4878]  Squire, M., "Definitions and Managed Objects for
            Operations, Administration, and Maintenance (OAM)
            Functions on Ethernet-Like Interfaces", RFC 4878, June
            2007, <http://www.rfc-editor.org/info/rfc4878>.

 [RFC5066]  Beili, E., "Ethernet in the First Mile Copper (EFMCu)
            Interfaces MIB", RFC 5066, November 2007,
            <http://www.rfc-editor.org/info/rfc5066>.

Taylor & Romascanu Informational [Page 6] RFC 7448 Transferring MIB Modules to IEEE 802.3 February 2015

Acknowledgements

 Thanks to Juergen Schoenwaelder and Howard Frazier for their reviews
 and comments on both the initial and the present versions of this
 document.  During WG Last Call, Warren Kumari caught a nit, and
 Thomas Petch raised the point of ownership versus responsibility that
 resulted in some wording changes in the Abstract and Introduction.

Authors' Addresses

 Tom Taylor (editor)
 PT Taylor Consulting
 Ottawa
 Canada

 EMail: tom.taylor.stds@gmail.com

 Dan Romascanu
 Avaya
 Park Atidim, Bldg. #3
 Tel Aviv  61581
 Israel

 Phone: +972-3-6458414
 EMail: dromasca@avaya.com

Taylor & Romascanu Informational [Page 7]