idnits 2.17.1 draft-ietf-opsawg-mibs-to-ieee80231-01.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 (October 14, 2014) is 3474 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: April 17, 2015 Avaya 6 October 14, 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-01 12 Abstract 14 This document records the transfer of responsibility for the 15 Ethernet-related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB, POWER- 16 ETHERNET-MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB, ETHER-WIS and 17 MAU-MIB from the IETF to the IEEE 802.3 Working Group. This document 18 also describes the procedures associated with the transfer, in a 19 similar way as RFC 4663 which records the transfer of the IETF Bridge 20 MIB work to the IEEE 802.1 Working Group. 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 April 17, 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 responsibility for four MIB modules related to bridges 74 from the IETF to IEEE 802.1. Some years later, responsibility for 75 eight more MIB modules was transferred from the IETF Ethernet 76 Interfaces and Hub MIB (hubmib) Working Group to the IEEE 802.3 77 Working Group. The MIB modules concerned are tabulated below 78 (Section 2). [RFC4663] clearly enunciates the motivation for both 79 transfers and also provides an introduction to IEEE standardization 80 procedures. The discussions of those topics will not be repeated 81 here. 83 The IEEE version of this second lot of transferred MIB modules was 84 published as 802.3.1-2011 in February, 2011. The IEEE 802.3.1 85 specification was subsequently updated. The latest version, IEEE 86 802.3.1-2013 [IEEE802.3.1-2013], is the basis for this document. 88 2. IETF and Corresponding IEEE 802.3 MIB modules 90 This section tabulates the MIB modules that were transferred to IEEE 91 802.3, identifying the IETF source document, the corresponding clause 92 of [IEEE802.3.1-2013], and the location of the MIB itself in ASCII 93 format. 95 IETF MIB Name: DOT3-OAM-MIB 96 IETF Reference: Definitions and Managed Objects for Operations, 97 Administration, and Maintenance (OAM) Functions on Ethernet-Like 98 Interfaces [RFC4878] 99 IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB 100 IEEE 802.3.1-2013 description: Clause 6, Ethernet operations, 101 administration, and maintenance (OAM) MIB module 102 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 103 802dot3dot1C6mib.txt 105 IETF MIB Name: SNMP-REPEATER-MIB 106 IETF Reference: Definitions of Managed Objects for IEEE 802.3 107 Repeater Devices using SMIv2 [RFC2108] 108 IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB 109 IEEE 802.3.1-2013 description: Clause 7, Ethernet repeater device MIB 110 module 111 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 112 802dot3dot1C7mib.txt 114 IETF MIB Name: POWER-ETHERNET-MIB 115 IETF Reference: Power Ethernet MIB [RFC3621] 116 IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB 117 IEEE 802.3.1-2013 description: Clause 8, Ethernet data terminal 118 equipment (DTE) power via medium dependent interface (MDI) MIB module 119 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 120 802dot3dot1C8mib.txt 122 IETF MIB Name: DOT3-EPON-MIB 123 IETF Reference: Managed Objects of Ethernet Passive Optical Networks 124 (EPON) [RFC4837] 125 IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB 126 IEEE 802.3.1-2013 description: Clause 9, Ethernet passive optical 127 networks (EPON) MIB module 128 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 129 802dot3dot1C9mib.txt 131 IETF MIB Name: EtherLike-MIB 132 IETF Reference: Definitions of Managed Objects for the Ethernet-like 133 Interface Types [RFC3635] 134 IEEE 802.3 MIB Name: ieee8023etherMIB 135 IEEE 802.3.1-2013 description: Clause 10, Ethernet-like interface MIB 136 module 137 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 138 802dot3dot1C10mib.txt 140 IETF MIB Name: EFM-CU-MIB 141 IETF Reference: Ethernet in the First Mile Copper (EFMCu) Interfaces 142 MIB [RFC5066] 143 IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB 144 IEEE 802.3.1-2013 description: Clause 11, Ethernet in the First Mile 145 copper (EFMCu) interfaces MIB module 146 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 147 802dot3dot1C11mib.txt 149 IETF MIB Name: ETHER-WIS 150 IETF Reference: Definitions of Managed Objects for the Ethernet WAN 151 Interface Sublayer [RFC3637] 152 IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB 153 IEEE 802.3.1-2013 description: Clause 12, Ethernet wide area network 154 (WAN) interface sublayer (WIS) MIB module 155 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 156 802dot3dot1C12mib.txt 158 IETF MIB Name: MAU-MIB 159 IETF Reference: Definitions of Managed Objects for IEEE 802.3 Medium 160 Attachment Units (MAUs) [RFC4836] 161 IEEE 802.3 MIB Name: IEEE8023-MAU-MIB 162 IEEE 802.3.1-2013 description: Clause 13, Ethernet medium attachment 163 units (MAUs) MIB module 164 MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/ 165 802dot3dot1C13mib.txt 167 3. Procedural Aspects Of the Transfer 169 3.1. IEEE MIB Modules in ASCII Format 171 The content of Section 2.2 of [RFC4663] is accurate also for this 172 document. 174 3.2. OID Registration for New MIB Modules 176 The IEEE 802.3 WG adopted the approach recommended in [RFC4663], 177 Section 2.3 of developing an IEEE MIB module and defining new 178 compliance clauses under the IEEE OID branch. Information about the 179 IEEE 802.3 Management Registration Arcs can be found at 180 http://www.ieee802.org/3/arcs/index.html. 182 3.3. Mailing List Discussions 184 The Ethernet Interfaces and Hub MIB WG has completed its documents, 185 and the WG was closed in September 2007. The mailing list stayed 186 open for a while, and was closed a few years later. The appropriate 187 mailing list for IEEE 802.3 MIB modules discussion is STDS-802-3- 188 MIB@LISTSERV.IEEE.ORG. 190 To see general information about 802.3, including how they work and 191 how to participate, go to http://www.ieee802.org/3/. 193 3.4. IETF MIB Doctor Reviews 195 The content of Section 5 of [RFC4663] is accurate also for this 196 document, noting that from the point of view of the present document, 197 802.3 should replace 802.1 wherever it occurs in the text. 199 4. Security Considerations 201 This document records the transfer of ownership of Ethernet-related 202 MIB modules to IEEE 802.3.1 several years ago. The transfer has no 203 security implications. 205 5. IANA Considerations 207 This document requires no actions by IANA. 209 6. IPR Considerations 211 See Section 9 of [RFC4663]. 213 7. Acknowledgements 215 Thanks to Juergen Schoenwaelder and Howard Frazier for their reviews 216 and comments on both the initial and the present versions of this 217 document. During Working Group Last Call, Warren Kumari caught a 218 nit, and Thomas Petch raised the point of ownership versus 219 responsibility that resulted in some wording changes in the Abstract 220 and Introduction. 222 8. Informative References 224 [IEEE802.3.1-2013] 225 IEEE Computer Society, "IEEE Standard for Management 226 Information Base (MIB) Definitions for Ethernet", June 227 2013. 229 [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. 230 McCloghrie, "Definitions of Managed Objects for IEEE 802.3 231 Repeater Devices using SMIv2", RFC 2108, February 1997. 233 [RFC3621] Berger, A. and D. Romascanu, "Power Ethernet MIB", RFC 234 3621, December 2003. 236 [RFC3635] Flick, J., "Definitions of Managed Objects for the 237 Ethernet-like Interface Types", RFC 3635, September 2003. 239 [RFC3637] Heard, C., "Definitions of Managed Objects for the 240 Ethernet WAN Interface Sublayer", RFC 3637, September 241 2003. 243 [RFC4663] Harrington, D., "Transferring MIB Work from IETF Bridge 244 MIB WG to IEEE 802.1 WG", RFC 4663, September 2006. 246 [RFC4836] Beili, E., "Definitions of Managed Objects for 247 IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836, 248 April 2007. 250 [RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical 251 Networks (EPON)", RFC 4837, July 2007. 253 [RFC4878] Squire, M., "Definitions and Managed Objects for 254 Operations, Administration, and Maintenance (OAM) 255 Functions on Ethernet-Like Interfaces", RFC 4878, June 256 2007. 258 [RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu) 259 Interfaces MIB", RFC 5066, November 2007. 261 Authors' Addresses 263 Tom Taylor (editor) 264 PT Taylor Consulting 265 Ottawa 266 Canada 268 Email: tom.taylor.stds@gmail.com 270 Dan Romascanu 271 Avaya 272 Park Atidim, Bldg. #3 273 Tel Aviv 61581 274 Israel 276 Phone: +972-3-6458414 277 Email: dromasca@avaya.com