idnits 2.17.1 draft-ietf-opsawg-mibs-to-ieee80231-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 24, 2014) is 3557 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 OPSAWG T. Taylor, Ed. 3 Internet-Draft PT Taylor Consulting 4 Intended status: Informational D. Romascanu 5 Expires: January 25, 2015 Avaya 6 July 24, 2014 8 Transferring MIB Work from IETF Ethernet Interfaces and Hub MIB WG to 9 IEEE 802.3 WG 10 draft-ietf-opsawg-mibs-to-ieee80231-00 12 Abstract 14 This document records the transfer of ownership of the Ethernet- 15 related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB, POWER-ETHERNET- 16 MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB, ETHER-WIS and MAU-MIB 17 from the IETF to the IEEE 802.3 Working Group. This document also 18 describes the procedures associated with the transfer, relying 19 heavily on RFC 4663 (which records an earlier transfer to the IEEE 20 802.1 Working Group) as the primary source. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 25, 2015. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. IETF and Corresponding IEEE 802.3 MIB modules . . . . . . . . 2 58 3. Procedural Aspects Of the Transfer . . . . . . . . . . . . . 4 59 3.1. IEEE MIB Modules in ASCII Format . . . . . . . . . . . . 4 60 3.2. OID Registration for New MIB Modules . . . . . . . . . . 4 61 3.3. Mailing List Discussions . . . . . . . . . . . . . . . . 4 62 3.4. IETF MIB Doctor Reviews . . . . . . . . . . . . . . . . . 5 63 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 65 6. IPR Considerations . . . . . . . . . . . . . . . . . . . . . 5 66 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 67 8. Informative References . . . . . . . . . . . . . . . . . . . 5 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 70 1. Introduction 72 [RFC4663], published in September, 2006, described a plan for 73 transferring four MIB modules related to bridges from IETF to IEEE 74 802.1 ownership. Some years later, ownership of eight more MIB 75 modules was transferred from the IETF Ethernet Interfaces and Hub MIB 76 (hubmib) Working Group to the IEEE 802.3 Working Group. The MIB 77 modules concerned are tabulated below (Section 2). [RFC4663] clearly 78 enunciates the motivation for both transfers and also provides an 79 introduction to IEEE standardization procedures. The discussions of 80 those topics will not be repeated here. 82 The IEEE version of this second lot of transferred MIB modules was 83 published as 802.3.1-2011 in February, 2011. The IEEE 802.3.1 84 specification was subsequently updated. The latest version, IEEE 85 802.3.1-2013 [IEEE802.3.1-2013], is the basis for this document. 87 2. IETF and Corresponding IEEE 802.3 MIB modules 89 This section tabulates the MIB modules that were transferred to IEEE 90 802.3, identifying the IETF source document, the corresponding clause 91 of [IEEE802.3.1-2013], and the location of the MIB itself in ASCII 92 format. 94 IETF MIB Name: DOT3-OAM-MIB 95 IETF Reference: Definitions and Managed Objects for Operations, 96 Administration, and Maintenance (OAM) Functions on Ethernet-Like 97 Interfaces [RFC4878] 98 IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB 99 IEEE 802.3.1-2013 description: Clause 6, Ethernet operations, 100 administration, and maintenance (OAM) MIB module 101 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 102 802dot3dot1C6mib.txt 104 IETF MIB Name: SNMP-REPEATER-MIB 105 IETF Reference: Definitions of Managed Objects for IEEE 802.3 106 Repeater Devices using SMIv2 [RFC2108] 107 IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB 108 IEEE 802.3.1-2013 description: Clause 7, Ethernet repeater device MIB 109 module 110 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 111 802dot3dot1C7mib.txt 113 IETF MIB Name: POWER-ETHERNET-MIB 114 IETF Reference: Power Ethernet MIB [RFC3621] 115 IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB 116 IEEE 802.3.1-2013 description: Clause 8, Ethernet data terminal 117 equipment (DTE) power via medium dependent interface (MDI) MIB module 118 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 119 802dot3dot1C8mib.txt 121 IETF MIB Name: DOT3-EPON-MIB 122 IETF Reference: Managed Objects of Ethernet Passive Optical Networks 123 (EPON) [RFC4837] 124 IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB 125 IEEE 802.3.1-2013 description: Clause 9, Ethernet passive optical 126 networks (EPON) MIB module 127 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 128 802dot3dot1C9mib.txt 130 IETF MIB Name: EtherLike-MIB 131 IETF Reference: Definitions of Managed Objects for the Ethernet-like 132 Interface Types [RFC3635] 133 IEEE 802.3 MIB Name: ieee8023etherMIB 134 IEEE 802.3.1-2013 description: Clause 10, Ethernet-like interface MIB 135 module 136 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 137 802dot3dot1C10mib.txt 139 IETF MIB Name: EFM-CU-MIB 140 IETF Reference: Ethernet in the First Mile Copper (EFMCu) Interfaces 141 MIB [RFC5066] 142 IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB 143 IEEE 802.3.1-2013 description: Clause 11, Ethernet in the First Mile 144 copper (EFMCu) interfaces MIB module 145 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 146 802dot3dot1C11mib.tx 148 IETF MIB Name: ETHER-WIS 149 IETF Reference: Definitions of Managed Objects for the Ethernet WAN 150 Interface Sublayer [RFC3637] 151 IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB 152 IEEE 802.3.1-2013 description: Clause 12, Ethernet wide area network 153 (WAN) interface sublayer (WIS) MIB module 154 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 155 802dot3dot1C12mib.txt 157 IETF MIB Name: MAU-MIB 158 IETF Reference: Definitions of Managed Objects for IEEE 802.3 Medium 159 Attachment Units (MAUs) [RFC4836] 160 IEEE 802.3 MIB Name: IEEE8023-MAU-MIB 161 IEEE 802.3.1-2013 description: Clause 13, Ethernet medium attachment 162 units (MAUs) MIB module 163 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 164 802dot3dot1C13mib.txt 166 3. Procedural Aspects Of the Transfer 168 3.1. IEEE MIB Modules in ASCII Format 170 The content of Section 2.2 of [RFC4663] is accurate also for this 171 document. 173 3.2. OID Registration for New MIB Modules 175 The IEEE 802.3 WG adopted the approach recommended in [RFC4663], 176 Section 2.3 of developing an IEEE MIB module and defining new 177 compliance clauses under the IEEE OID branch. Information about the 178 IEEE 802.3 Management Registration Arcs can be found at 179 http://www.ieee802.org/3/arcs/index.html. 181 3.3. Mailing List Discussions 183 The Ethernet Interfaces and Hub MIB WG has completed its documents, 184 and the WG was closed in September 2007. The mailing list stayed 185 open for a while, and was closed a few years later. The appropriate 186 mailing list for IEEE 802.3 MIB modules discussion is STDS-802-3- 187 MIB@LISTSERV.IEEE.ORG. 189 To see general information about 802.3, including how they work and 190 how to participate, go to http://www.ieee802.org/3/. 192 3.4. IETF MIB Doctor Reviews 194 The content of Section 5 of [RFC4663] is accurate also for this 195 document, noting that from the point of view of the present document, 196 802.3 should replace 802.1 wherever it occurs in the text. 198 4. Security Considerations 200 This document records the transfer of ownership of Ethernet-related 201 MIB modules to IEEE 802.3.1 several years ago. The transfer has no 202 security implications. 204 5. IANA Considerations 206 This document requires no actions by IANA. 208 6. IPR Considerations 210 See Section 9 of [RFC4663]. 212 7. Acknowledgements 214 Thanks to Juergen Schoenwaelder and Howard Frazier for their reviews 215 and comments on both the initial and the present versions of this 216 document. 218 8. Informative References 220 [IEEE802.3.1-2013] 221 IEEE Computer Society, "IEEE Standard for Management 222 Information Base (MIB) Definitions for Ethernet", June 223 2013. 225 [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. 226 McCloghrie, "Definitions of Managed Objects for IEEE 802.3 227 Repeater Devices using SMIv2", RFC 2108, February 1997. 229 [RFC3621] Berger, A. and D. Romascanu, "Power Ethernet MIB", RFC 230 3621, December 2003. 232 [RFC3635] Flick, J., "Definitions of Managed Objects for the 233 Ethernet-like Interface Types", RFC 3635, September 2003. 235 [RFC3637] Heard, C., "Definitions of Managed Objects for the 236 Ethernet WAN Interface Sublayer", RFC 3637, September 237 2003. 239 [RFC4663] Harrington, D., "Transferring MIB Work from IETF Bridge 240 MIB WG to IEEE 802.1 WG", RFC 4663, September 2006. 242 [RFC4836] Beili, E., "Definitions of Managed Objects for 243 IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836, 244 April 2007. 246 [RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical 247 Networks (EPON)", RFC 4837, July 2007. 249 [RFC4878] Squire, M., "Definitions and Managed Objects for 250 Operations, Administration, and Maintenance (OAM) 251 Functions on Ethernet-Like Interfaces", RFC 4878, June 252 2007. 254 [RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu) 255 Interfaces MIB", RFC 5066, November 2007. 257 Authors' Addresses 259 Tom Taylor (editor) 260 PT Taylor Consulting 261 Ottawa 262 Canada 264 Email: tom.taylor.stds@gmail.com 266 Dan Romascanu 267 Avaya 268 Park Atidim, Bldg. #3 269 Tel Aviv 61581 270 Israel 272 Phone: +972-3-6458414 273 Email: dromasca@avaya.com