draft-ietf-opsawg-mibs-to-ieee80231-01.txt		rfc7448.txt
	OPSAWG T. Taylor, Ed.		Internet Engineering Task Force (IETF) T. Taylor, Ed.
	Internet-Draft PT Taylor Consulting		Request for Comments: 7448 PT Taylor Consulting
	Intended status: Informational D. Romascanu		Category: Informational D. Romascanu
	Expires: April 17, 2015 Avaya		ISSN: 2070-1721 Avaya
	October 14, 2014		February 2015
	Transferring MIB Work from IETF Ethernet Interfaces and Hub MIB WG to		MIB Transfer from the IETF to the IEEE 802.3 WG
	IEEE 802.3 WG
	draft-ietf-opsawg-mibs-to-ieee80231-01
	Abstract		Abstract
	This document records the transfer of responsibility for the		This document records the transfer of responsibility for the
	Ethernet-related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB, POWER-		Ethernet-related MIB modules DOT3-OAM-MIB, SNMP-REPEATER-MIB,
	ETHERNET-MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB, ETHER-WIS and		POWER-ETHERNET-MIB, DOT3-EPON-MIB, EtherLike-MIB, EFM-CU-MIB,
	MAU-MIB from the IETF to the IEEE 802.3 Working Group. This document		ETHER-WIS, and MAU-MIB from the IETF to the IEEE 802.3 Working Group
	also describes the procedures associated with the transfer, in a		(WG). This document also describes the procedures associated with
	similar way as RFC 4663 which records the transfer of the IETF Bridge		the transfer in a similar way to how RFC 4663 records the transfer of
	MIB work to the IEEE 802.1 Working Group.		the IETF Bridge MIB work to the IEEE 802.1 WG.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This document is not an Internet Standards Track specification; it is
	provisions of BCP 78 and BCP 79.		published for informational purposes.
	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		This document is a product of the Internet Engineering Task Force
	and may be updated, replaced, or obsoleted by other documents at any		(IETF). It represents the consensus of the IETF community. It has
	time. It is inappropriate to use Internet-Drafts as reference		received public review and has been approved for publication by the
	material or to cite them other than as "work in progress."		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.
	This Internet-Draft will expire on April 17, 2015.		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.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction ....................................................2
	2. IETF and Corresponding IEEE 802.3 MIB modules . . . . . . . . 2		2. IETF and Corresponding IEEE 802.3 MIB Modules ...................3
	3. Procedural Aspects Of the Transfer . . . . . . . . . . . . . 4		3. Procedural Aspects of the Transfer ..............................4
	3.1. IEEE MIB Modules in ASCII Format . . . . . . . . . . . . 4		3.1. IEEE MIB Modules in ASCII Format ...........................4
	3.2. OID Registration for New MIB Modules . . . . . . . . . . 4		3.2. OID Registration for New MIB Modules .......................5
	3.3. Mailing List Discussions . . . . . . . . . . . . . . . . 4		3.3. Mailing List Discussions ...................................5
	3.4. IETF MIB Doctor Reviews . . . . . . . . . . . . . . . . . 5		3.4. IETF MIB Doctor Reviews ....................................5
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 5		4. Security Considerations .........................................5
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		5. Informative References ..........................................5
	6. IPR Considerations . . . . . . . . . . . . . . . . . . . . . 5		Acknowledgements ...................................................7
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses .................................................7
	8. Informative References . . . . . . . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	[RFC4663], published in September, 2006, described a plan for		[RFC4663], published in September 2006, described a plan for
	transferring responsibility for four MIB modules related to bridges		transferring responsibility for four MIB modules related to bridges
	from the IETF to IEEE 802.1. Some years later, responsibility for		from the IETF to IEEE 802.1. Some years later, responsibility for
	eight more MIB modules was transferred from the IETF Ethernet		eight more MIB modules was transferred from the IETF Ethernet
	Interfaces and Hub MIB (hubmib) Working Group to the IEEE 802.3		Interfaces and Hub MIB (hubmib) WG to the IEEE 802.3 WG. The MIB
	Working Group. The MIB modules concerned are tabulated below		modules concerned are tabulated below (Section 2). [RFC4663] clearly
	(Section 2). [RFC4663] clearly enunciates the motivation for both		enunciates the motivation for both transfers and also provides an
	transfers and also provides an introduction to IEEE standardization		introduction to IEEE standardization procedures. The discussions of
	procedures. The discussions of those topics will not be repeated		those topics will not be repeated here.
	here.
	The IEEE version of this second lot of transferred MIB modules was		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		published as 802.3.1-2011 in February 2011. The IEEE 802.3.1
	specification was subsequently updated. The latest version, IEEE		specification was subsequently updated. The latest version, IEEE
	802.3.1-2013 [IEEE802.3.1-2013], is the basis for this document.		802.3.1-2013 [IEEE802.3.1-2013], is the basis for this document.
	2. IETF and Corresponding IEEE 802.3 MIB modules		2. IETF and Corresponding IEEE 802.3 MIB Modules
	This section tabulates the MIB modules that were transferred to IEEE		This section tabulates the MIB modules that were transferred to IEEE
	802.3, identifying the IETF source document, the corresponding clause		802.3, identifying the IETF source document, the corresponding clause
	of [IEEE802.3.1-2013], and the location of the MIB itself in ASCII		of [IEEE802.3.1-2013], and the location of the MIB itself in ASCII
	format.		format.
	IETF MIB Name: DOT3-OAM-MIB		IETF MIB Name: DOT3-OAM-MIB
	IETF Reference: Definitions and Managed Objects for Operations,		IETF Reference: Definitions and Managed Objects for Operations,
	Administration, and Maintenance (OAM) Functions on Ethernet-Like		Administration, and Maintenance (OAM) Functions on Ethernet-Like
	Interfaces [RFC4878]		Interfaces [RFC4878]
	IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB		IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB
	IEEE 802.3.1-2013 description: Clause 6, Ethernet operations,		IEEE 802.3.1-2013 Description: Clause 6, Ethernet operations,
	administration, and maintenance (OAM) MIB module		administration, and maintenance (OAM) MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C6mib.txt		802dot3dot1C6mib.txt
	IETF MIB Name: SNMP-REPEATER-MIB		IETF MIB Name: SNMP-REPEATER-MIB
	IETF Reference: Definitions of Managed Objects for IEEE 802.3		IETF Reference: Definitions of Managed Objects for IEEE 802.3
	Repeater Devices using SMIv2 [RFC2108]		Repeater Devices using SMIv2 [RFC2108]
	IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB		IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB
	IEEE 802.3.1-2013 description: Clause 7, Ethernet repeater device MIB		IEEE 802.3.1-2013 Description: Clause 7, Ethernet repeater device MIB
	module		module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C7mib.txt		802dot3dot1C7mib.txt
	IETF MIB Name: POWER-ETHERNET-MIB		IETF MIB Name: POWER-ETHERNET-MIB
	IETF Reference: Power Ethernet MIB [RFC3621]		IETF Reference: Power Ethernet MIB [RFC3621]
	IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB		IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB
	IEEE 802.3.1-2013 description: Clause 8, Ethernet data terminal		IEEE 802.3.1-2013 Description: Clause 8, Ethernet data terminal
	equipment (DTE) power via medium dependent interface (MDI) MIB module		equipment (DTE) power via medium dependent interface (MDI) MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C8mib.txt		802dot3dot1C8mib.txt
	IETF MIB Name: DOT3-EPON-MIB		IETF MIB Name: DOT3-EPON-MIB
	IETF Reference: Managed Objects of Ethernet Passive Optical Networks		IETF Reference: Managed Objects of Ethernet Passive Optical Networks
	(EPON) [RFC4837]		(EPON) [RFC4837]
	IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB		IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB
	IEEE 802.3.1-2013 description: Clause 9, Ethernet passive optical		IEEE 802.3.1-2013 Description: Clause 9, Ethernet passive optical
	networks (EPON) MIB module		networks (EPON) MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C9mib.txt		802dot3dot1C9mib.txt
	IETF MIB Name: EtherLike-MIB		IETF MIB Name: EtherLike-MIB
	IETF Reference: Definitions of Managed Objects for the Ethernet-like		IETF Reference: Definitions of Managed Objects for the Ethernet-like
	Interface Types [RFC3635]		Interface Types [RFC3635]
	IEEE 802.3 MIB Name: ieee8023etherMIB		IEEE 802.3 MIB Name: IEEE8023-Etherlike-MIB
	IEEE 802.3.1-2013 description: Clause 10, Ethernet-like interface MIB		IEEE 802.3.1-2013 Description: Clause 10, Ethernet-like interface MIB
	module		module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C10mib.txt		802dot3dot1C10mib.txt
	IETF MIB Name: EFM-CU-MIB		IETF MIB Name: EFM-CU-MIB
	IETF Reference: Ethernet in the First Mile Copper (EFMCu) Interfaces		IETF Reference: Ethernet in the First Mile Copper (EFMCu) Interfaces
	MIB [RFC5066]		MIB [RFC5066]
	IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB		IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB
	IEEE 802.3.1-2013 description: Clause 11, Ethernet in the First Mile		IEEE 802.3.1-2013 Description: Clause 11, Ethernet in the First Mile
	copper (EFMCu) interfaces MIB module		copper (EFMCu) interfaces MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C11mib.txt		802dot3dot1C11mib.txt
	IETF MIB Name: ETHER-WIS		IETF MIB Name: ETHER-WIS
	IETF Reference: Definitions of Managed Objects for the Ethernet WAN		IETF Reference: Definitions of Managed Objects for the Ethernet WAN
	Interface Sublayer [RFC3637]		Interface Sublayer [RFC3637]
	IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB		IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB
	IEEE 802.3.1-2013 description: Clause 12, Ethernet wide area network		IEEE 802.3.1-2013 Description: Clause 12, Ethernet wide area network
	(WAN) interface sublayer (WIS) MIB module		(WAN) interface sublayer (WIS) MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C12mib.txt		802dot3dot1C12mib.txt
	IETF MIB Name: MAU-MIB		IETF MIB Name: MAU-MIB
	IETF Reference: Definitions of Managed Objects for IEEE 802.3 Medium		IETF Reference: Definitions of Managed Objects for IEEE 802.3 Medium
	Attachment Units (MAUs) [RFC4836]		Attachment Units (MAUs) [RFC4836]
	IEEE 802.3 MIB Name: IEEE8023-MAU-MIB		IEEE 802.3 MIB Name: IEEE8023-MAU-MIB
	IEEE 802.3.1-2013 description: Clause 13, Ethernet medium attachment		IEEE 802.3.1-2013 Description: Clause 13, Ethernet medium attachment
	units (MAUs) MIB module		units (MAUs) MIB module
	MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/		MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
	802dot3dot1C13mib.txt		802dot3dot1C13mib.txt
	3. Procedural Aspects Of the Transfer		3. Procedural Aspects of the Transfer
	3.1. IEEE MIB Modules in ASCII Format		3.1. IEEE MIB Modules in ASCII Format
	The content of Section 2.2 of [RFC4663] is accurate also for this		The content of Section 2.2 of [RFC4663] is also accurate for this
	document.		document.
	3.2. OID Registration for New MIB Modules		3.2. OID Registration for New MIB Modules
	The IEEE 802.3 WG adopted the approach recommended in [RFC4663],		The IEEE 802.3 WG adopted the approach recommended in Section 2.3 of
	Section 2.3 of developing an IEEE MIB module and defining new		[RFC4663] of developing an IEEE MIB module and defining new
	compliance clauses under the IEEE OID branch. Information about the		compliance clauses under the IEEE OID branch. Information about the
	IEEE 802.3 Management Registration Arcs can be found at		IEEE 802.3 Management Registration Arcs can be found at
	http://www.ieee802.org/3/arcs/index.html.		<http://www.ieee802.org/3/arcs/index.html>.
	3.3. Mailing List Discussions		3.3. Mailing List Discussions
	The Ethernet Interfaces and Hub MIB WG has completed its documents,		The Ethernet Interfaces and Hub MIB WG has completed its documents,
	and the WG was closed in September 2007. The mailing list stayed		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		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-		mailing list for IEEE 802.3 MIB modules discussion is
	MIB@LISTSERV.IEEE.ORG.		STDS-802-3-MIB@LISTSERV.IEEE.ORG.
	To see general information about 802.3, including how they work and		To see general information about 802.3, including how they work and
	how to participate, go to http://www.ieee802.org/3/.		how to participate, go to <http://www.ieee802.org/3/>.
	3.4. IETF MIB Doctor Reviews		3.4. IETF MIB Doctor Reviews
	The content of Section 5 of [RFC4663] is accurate also for this		The content of Section 5 of [RFC4663] is also accurate for this
	document, noting that from the point of view of the present document,		document, noting that from the point of view of the present document,
	802.3 should replace 802.1 wherever it occurs in the text.		802.3 should replace 802.1 wherever it occurs in the text.
	4. Security Considerations		4. Security Considerations
	This document records the transfer of ownership of Ethernet-related		This document records the transfer of ownership of Ethernet-related
	MIB modules to IEEE 802.3.1 several years ago. The transfer has no		MIB modules to IEEE 802.3.1 several years ago. The transfer has no
	security implications.		security implications.
	5. IANA Considerations		5. Informative References
	This document requires no actions by IANA.
	6. IPR Considerations
	See Section 9 of [RFC4663].
	7. 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 Working Group 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.
	8. Informative References
	[IEEE802.3.1-2013]		[IEEE802.3.1-2013]
	IEEE Computer Society, "IEEE Standard for Management		IEEE Computer Society, "IEEE Standard for Management
	Information Base (MIB) Definitions for Ethernet", June		Information Base (MIB) Definitions for Ethernet", June
	2013.		2013.
	[RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K.		[RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K.
	McCloghrie, "Definitions of Managed Objects for IEEE 802.3		McCloghrie, "Definitions of Managed Objects for IEEE 802.3
	Repeater Devices using SMIv2", RFC 2108, February 1997.		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		[RFC3621] Berger, A. and D. Romascanu, "Power Ethernet MIB", RFC
	3621, December 2003.		3621, December 2003,
			<http://www.rfc-editor.org/info/rfc3621>.
	[RFC3635] Flick, J., "Definitions of Managed Objects for the		[RFC3635] Flick, J., "Definitions of Managed Objects for the
	Ethernet-like Interface Types", RFC 3635, September 2003.		Ethernet-like Interface Types", RFC 3635, September 2003,
			<http://www.rfc-editor.org/info/rfc3635>.
	[RFC3637] Heard, C., "Definitions of Managed Objects for the		[RFC3637] Heard, C., "Definitions of Managed Objects for the
	Ethernet WAN Interface Sublayer", RFC 3637, September		Ethernet WAN Interface Sublayer", RFC 3637, September
	2003.		2003, <http:///www.rfc-editor.org/info/rfc3637>.
	[RFC4663] Harrington, D., "Transferring MIB Work from IETF Bridge		[RFC4663] Harrington, D., "Transferring MIB Work from IETF Bridge
	MIB WG to IEEE 802.1 WG", RFC 4663, September 2006.		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		[RFC4836] Beili, E., "Definitions of Managed Objects for
	IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836,		IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836,
	April 2007.		April 2007, <http:///www.rfc-editor.org/info/rfc4836>.
	[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical		[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical
	Networks (EPON)", RFC 4837, July 2007.		Networks (EPON)", RFC 4837, July 2007,
			<http://www.rfc-editor.org/info/rfc4837>.
	[RFC4878] Squire, M., "Definitions and Managed Objects for		[RFC4878] Squire, M., "Definitions and Managed Objects for
	Operations, Administration, and Maintenance (OAM)		Operations, Administration, and Maintenance (OAM)
	Functions on Ethernet-Like Interfaces", RFC 4878, June		Functions on Ethernet-Like Interfaces", RFC 4878, June
	2007.		2007, <http://www.rfc-editor.org/info/rfc4878>.
	[RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu)		[RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu)
	Interfaces MIB", RFC 5066, November 2007.		Interfaces MIB", RFC 5066, November 2007,
			<http://www.rfc-editor.org/info/rfc5066>.
			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		Authors' Addresses
	Tom Taylor (editor)		Tom Taylor (editor)
	PT Taylor Consulting		PT Taylor Consulting
	Ottawa		Ottawa
	Canada		Canada
	Email: tom.taylor.stds@gmail.com		EMail: tom.taylor.stds@gmail.com
	Dan Romascanu		Dan Romascanu
	Avaya		Avaya
	Park Atidim, Bldg. #3		Park Atidim, Bldg. #3
	Tel Aviv 61581		Tel Aviv 61581
	Israel		Israel
	Phone: +972-3-6458414		Phone: +972-3-6458414
	Email: dromasca@avaya.com		EMail: dromasca@avaya.com
End of changes. 47 change blocks.
	105 lines changed or deleted		95 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/