RFC 7448

MIB Transfer from the IETF to the IEEE 802.3 WG

📅 published February 2015, from ietf

RFC 7448: MIB Transfer from the IETF to the IEEE 802.3 WG 🎀

okay bestie, this one's a transfer doc, so it's all about who owns which MIB modules now 📋✨

  • Editor: Tom Taylor (Ed.), PT Taylor Consulting, Ottawa, Canada 💅
  • Co-author: Dan Romascanu, Avaya 🫶
  • Category: Informational (it is not a Standards Track spec, just published for info) 🌸
  • ISSN: 2070-1721
  • Date: February 2015 🦋
  • Obsoletes / Updates: the header doesn't list anything it obsoletes or updates 🙈

Abstract

okay so this doc records the handoff of 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 over to the IEEE 802.3 Working Group (WG) 🔥. It also explains the procedures for the transfer, and it does that the same way RFC 4663 recorded the IETF Bridge MIB work moving to the IEEE 802.1 WG. the vibes are very "passing the baton, but make it organized" 🏃‍♀️💨

Status of This Memo

this is NOT an Internet Standards Track spec, it's just here for info 🧚

this is a product of the Internet Engineering Task Force (IETF) 🌈. it reflects the consensus of the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). not every IESG-approved doc is a candidate for any level of Internet Standard though, so see Section 2 of RFC 5741 for that 🙃.

for the latest on this doc's status, errata, or how to send feedback, check http://www.rfc-editor.org/info/rfc7448 💜

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

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date. read those carefully, bestie, they spell out your rights and restrictions 📜. any Code Components pulled out of this doc have to include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as the Simplified BSD License says ⚠️.

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 ✨

so, [RFC4663] came out in September 2006 and planned the handoff of four bridge-related MIB modules from the IETF to IEEE 802.1 🌉. a few years later, eight more MIB modules got transferred from the IETF Ethernet Interfaces and Hub MIB (hubmib) WG to the IEEE 802.3 WG 🧁. those are tabulated in Section 2 below. [RFC4663] explains the motivation for both transfers and gives an intro to IEEE standardization procedures, so we're not going to redo that here 💅.

the IEEE version of this second batch was published as 802.3.1-2011 in February 2011. the IEEE 802.3.1 spec got updated after that, and the latest version, IEEE 802.3.1-2013 [IEEE802.3.1-2013], is what this doc is based on 🦋.

2. IETF and Corresponding IEEE 802.3 MIB Modules 📋

this section is the big list of which MIB modules moved over 🍓. for each one, it shows the IETF source doc, the matching clause in [IEEE802.3.1-2013], and where to find the MIB 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
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 stuff in Section 2.2 of [RFC4663] is also accurate for this doc 🫶.

3.2. OID Registration for New MIB Modules 🔢

the IEEE 802.3 WG went with the approach from Section 2.3 of [RFC4663]: build an IEEE MIB module and define new compliance clauses under the IEEE OID branch 🌟. you can find info about the IEEE 802.3 Management Registration Arcs at <http://www.ieee802.org/3/arcs/index.html> 🗺️.

3.3. Mailing List Discussions 💌

the Ethernet Interfaces and Hub MIB WG finished its docs and closed in September 2007 🥀. the mailing list stayed open for a bit, then closed a few years later. the right list for IEEE 802.3 MIB module talk is STDS-802-3-MIB@LISTSERV.IEEE.ORG 📨.

if you want general info on 802.3, like how they work and how to join in, go to <http://www.ieee802.org/3/> 🎀.

3.4. IETF MIB Doctor Reviews 🩺

the stuff in Section 5 of [RFC4663] is also accurate for this doc, with one tweak: for this doc, 802.3 should replace 802.1 wherever it shows up in the text 🔁.

4. Security Considerations 🔐

this doc 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 📚

Acknowledgements 🫶

huge thanks to Juergen Schoenwaelder and Howard Frazier for reviewing both the initial and current versions 🙌. during WG Last Call, Warren Kumari caught a nit 🐛, and Thomas Petch brought up ownership vs. responsibility, which led to 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

the end, bestie! 🌈✨ the MIBs are officially over at 802.3 now 👑

📦 where this page comes from