draft-ietf-hubmib-wis-mib-05.txt		draft-ietf-hubmib-wis-mib-06.txt
	Ethernet Interfaces and Hub MIB Working Group Mike Ayers		Ethernet Interfaces and Hub MIB Working Group C. M. Heard, Editor
	INTERNET DRAFT Consultant		INTERNET DRAFT Consultant
	John Flick		January 4, 2003
	Hewlett-Packard Company
	C. M. Heard
	Consultant
	Kam Lam
	Lucent Technologies
	Kerry McDonald
	CSU San Bernardino
	K. C. Norseth
	Consultant
	Kaj Tesink
	Telcordia Technologies
	December 13, 2002
	Definitions of Managed Objects		Definitions of Managed Objects
	for the Ethernet WAN Interface Sublayer		for the Ethernet WAN Interface Sublayer
	<draft-ietf-hubmib-wis-mib-05.txt>		<draft-ietf-hubmib-wis-mib-06.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	skipping to change at page 1, line 44		skipping to change at page 1, line 32
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2003). All Rights Reserved.
	Abstract		Abstract
	This document defines a portion of the Management Information Base		This document defines a portion of the Management Information Base
	(MIB) for use with network management protocols in TCP/IP based		(MIB) for use with network management protocols in TCP/IP based
	internets. In particular, it defines objects for managing the		internets. In particular, it defines objects for managing the
	Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).		Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).
	The MIB module defined in this memo is an extension of the SONET/SDH		The MIB module defined in this memo is an extension of the SONET/SDH
	Interface MIB and is implemented in conjunction with it and with the		Interface MIB and is implemented in conjunction with it and with the
	skipping to change at page 2, line 43		skipping to change at page 2, line 31
	3.5 SONET/SDH Terminology ................................... 6		3.5 SONET/SDH Terminology ................................... 6
	3.6 Mapping of IEEE 802.3 Managed Objects ................... 7		3.6 Mapping of IEEE 802.3 Managed Objects ................... 7
	3.7 Mapping of SNMP Objects to WIS Station Management		3.7 Mapping of SNMP Objects to WIS Station Management
	Registers .............................................. 12		Registers .............................................. 12
	3.8 Structure of the MIB Module ............................. 14		3.8 Structure of the MIB Module ............................. 14
	3.8.1 etherWisDeviceTable ................................... 14		3.8.1 etherWisDeviceTable ................................... 14
	3.8.2 etherWisSectionCurrentTable ........................... 15		3.8.2 etherWisSectionCurrentTable ........................... 15
	3.8.3 etherWisPathCurrentTable .............................. 15		3.8.3 etherWisPathCurrentTable .............................. 15
	3.8.4 etherWisFarEndPathCurrentTable ........................ 15		3.8.4 etherWisFarEndPathCurrentTable ........................ 15
	4 Object Definitions ........................................ 16		4 Object Definitions ........................................ 16
	5 Acknowledgments ........................................... 30		5 Intellectual Property ..................................... 30
	6 Security Considerations ................................... 31		6 Acknowledgments ........................................... 30
	7 References ................................................ 32		7 Security Considerations ................................... 31
	7.1 Normative References .................................... 32		8 References ................................................ 32
	7.2 Informative References .................................. 33		8.1 Normative References .................................... 32
	8 Authors' Addresses ........................................ 33		8.2 Informative References .................................. 33
	9 Intellectual Property ..................................... 34		9 Contributors .............................................. 33
			10 Editor's Address ......................................... 34
	Appendix A: Collection of Performance Data Using WIS		Appendix A: Collection of Performance Data Using WIS
	MDIO Registers ......................................... 35		MDIO Registers ......................................... 35
	Full Copyright Statement ................................... 36		Full Copyright Statement ................................... 36
	1. Conventions		1. Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL", when they appear in this document, are to be interpreted		"OPTIONAL", when they appear in this document, are to be interpreted
	as described in RFC 2119 [RFC2119].		as described in RFC 2119 [RFC2119].
	2. The Internet-Standard Management Framework		2. The Internet-Standard Management Framework
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of		Internet-Standard Management Framework, please refer to section 7 of
	RFC 2570bis [RFC2570bis].		RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	Structure of Management Information (SMI). This memo specifies a MIB		Structure of Management Information (SMI). This memo specifies a MIB
	module that is compliant to the SMIv2, which is described in STD 58,		module that is compliant to the SMIv2, which is described in STD 58,
	RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580		RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
	[RFC2580].		[RFC2580].
	skipping to change at page 16, line 27		skipping to change at page 16, line 27
	sonetMediumStuff2, sonetSectionStuff2,		sonetMediumStuff2, sonetSectionStuff2,
	sonetLineStuff2, sonetFarEndLineStuff2,		sonetLineStuff2, sonetFarEndLineStuff2,
	sonetPathStuff2, sonetFarEndPathStuff2,		sonetPathStuff2, sonetFarEndPathStuff2,
	sonetMediumType, sonetMediumLineCoding,		sonetMediumType, sonetMediumLineCoding,
	sonetMediumLineType, sonetMediumCircuitIdentifier,		sonetMediumLineType, sonetMediumCircuitIdentifier,
	sonetMediumLoopbackConfig, sonetSESthresholdSet,		sonetMediumLoopbackConfig, sonetSESthresholdSet,
	sonetPathCurrentWidth		sonetPathCurrentWidth
	FROM SONET-MIB;		FROM SONET-MIB;
	etherWisMIB MODULE-IDENTITY		etherWisMIB MODULE-IDENTITY
	LAST-UPDATED "200212132358Z" -- December 13, 2002		LAST-UPDATED "200301042136Z" -- January 4, 2003
	ORGANIZATION "IETF Ethernet Interfaces and Hub MIB		ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
	Working Group"		Working Group"
	CONTACT-INFO		CONTACT-INFO
	"WG charter:		"WG charter:
	http://www.ietf.org/html.charters/hubmib-charter.html		http://www.ietf.org/html.charters/hubmib-charter.html
			Mailing Lists:
			General Discussion: hubmib@ietf.org
			To Subscribe: hubmib-request@ietf.org
			In Body: subscribe your_email_address
	Chair: Dan Romascanu		Chair: Dan Romascanu
	Postal: Avaya Inc.		Postal: Avaya Inc.
	Atidim Technology Park, Bldg. 3		Atidim Technology Park, Bldg. 3
	Tel Aviv 61131		Tel Aviv 61131
	Israel		Israel
	Tel: +972 3 645 8414		Tel: +972 3 645 8414
	E-mail: dromasca@avaya.com		E-mail: dromasca@avaya.com
	Editor: C. M. Heard		Editor: C. M. Heard
	Postal: 600 Rainbow Dr. #141		Postal: 600 Rainbow Dr. #141
	skipping to change at page 17, line 27		skipping to change at page 17, line 31
	Physical Layer Specifications - Media Access Control		Physical Layer Specifications - Media Access Control
	(MAC) Parameters, Physical Layer and Management		(MAC) Parameters, Physical Layer and Management
	Parameters for 10 Gb/s Operation', 30 August 2002.		Parameters for 10 Gb/s Operation', 30 August 2002.
	Of particular interest are Clause 50, 'WAN Interface		Of particular interest are Clause 50, 'WAN Interface
	Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s,		Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s,
	100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link		100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link
	Aggregation Management', and Clause 45, 'Management		Aggregation Management', and Clause 45, 'Management
	Data Input/Output (MDIO) Interface'.		Data Input/Output (MDIO) Interface'.
	Copyright (C) The Internet Society (2002). This version		Copyright (C) The Internet Society (2003). This version
	of this MIB module is part of RFC yyyy; see the RFC		of this MIB module is part of RFC yyyy; see the RFC
	itself for full legal notices."		itself for full legal notices."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this notice		-- RFC Ed.: replace yyyy with actual RFC number & remove this notice
	REVISION "200212132358Z" -- December 13, 2002		REVISION "200301042136Z" -- January 4, 2003
	DESCRIPTION "Initial version, published as RFC yyyy."		DESCRIPTION "Initial version, published as RFC yyyy."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this notice		-- RFC Ed.: replace yyyy with actual RFC number & remove this notice
	::= { transmission XXX }		::= { transmission XXX }
	-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice		-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice
	-- The main sections of the module		-- The main sections of the module
	etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 }		etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 }
	etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 }		etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 }
	skipping to change at page 30, line 23		skipping to change at page 30, line 23
	}		}
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access is not required, nor is support		"Write access is not required, nor is support
	for any value other than sts192cSTM64(6)."		for any value other than sts192cSTM64(6)."
	::= { etherWisCompliances 1 }		::= { etherWisCompliances 1 }
	END		END
	5. Acknowledgments		5. Intellectual Property
	This document is a product of the IETF Hubmib and AToMMIB Working		The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			pertain to the implementation or use of the technology described in
			this document or the extent to which any license under such rights
			might or might not be available; neither does it represent that it
			has made any effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in BCP-11. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			6. Acknowledgments
			This document is a product of the IETF Hub MIB and AToM MIB Working
	Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit		Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit
	Ethernet Task Force.		Ethernet Task Force.
	6. Security Considerations		7. Security Considerations
	There are five managed objects defined in this MIB module that have a		There are five managed objects defined in this MIB module that have a
	MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode,		MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode,
	etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors,		etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors,
	etherWisSectionCurrentJ0Transmitted, and		etherWisSectionCurrentJ0Transmitted, and
	etherWisPathCurrentJ1Transmitted. Writing to these objects can have		etherWisPathCurrentJ1Transmitted. Writing to these objects can have
	the following potentially disruptive effects on network operation:		the following potentially disruptive effects on network operation:
	o changing the transmit or receive test pattern mode or modifying		o changing the transmit or receive test pattern mode or modifying
	the accumulated error count from a PRBS31 pattern test on an		the accumulated error count from a PRBS31 pattern test on an
	skipping to change at page 31, line 27		skipping to change at page 31, line 27
	interfere with an in-progress pattern test;		interfere with an in-progress pattern test;
	o modifying the transmitted section trace and/or path trace		o modifying the transmitted section trace and/or path trace
	message on an operational 10GBASE-W interface, which can cause		message on an operational 10GBASE-W interface, which can cause
	connectivity alarms to be raised at the remote of the link.		connectivity alarms to be raised at the remote of the link.
	The user of this MIB module must therefore be aware that support for		The user of this MIB module must therefore be aware that support for
	SET operations in a non-secure environment without proper protection		SET operations in a non-secure environment without proper protection
	can have a negative effect on network operations.		can have a negative effect on network operations.
	All other managed objects in this MIB module have a MAX-ACCESS clause		The readable objects in this MIB module (i.e., those with MAX-ACCESS
	of read-only. The information contained in those objects may be		other than not-accessible) may be considered sensitive in some
	considered sensitive in some network environments. In such		environments since, collectively, they provide information about the
	environments it is important to control even GET access to those		performance of network interfaces and can reveal some aspects of
	objects and possibly to even encrypt the values of these objects when		their configuration. In such environments it is important to control
	sending them over the network via SNMP.		even GET and NOTIFY access to these objects and possibly even to
			encrypt their values when sending them over the network via SNMP.
	SNMP versions prior to SNMPv3 did not include adequate security.		SNMP versions prior to SNMPv3 did not include adequate security.
	Even if the network itself is secure (for example by using IPSec),		Even if the network itself is secure (for example by using IPSec),
	even then, there is no control as to who on the secure network is		even then, there is no control as to who on the secure network is
	allowed to access and GET/SET (read/change/create/delete) the objects		allowed to access and GET/SET (read/change/create/delete) the objects
	in this MIB module.		in this MIB module.
	It is RECOMMENDED that implementers consider the security features as		It is RECOMMENDED that implementers consider the security features as
	provided by the SNMPv3 framework (see [RFC2570bis], section 8),		provided by the SNMPv3 framework (see [RFC3410], section 8),
	inluding full support for the SNMPv3 cryptographic mechanisms (for		including full support for the SNMPv3 cryptographic mechanisms (for
	authentication and privacy).		authentication and privacy).
	Further, deployment of SNMP versions prior to SNMPv3 is NOT		Further, deployment of SNMP versions prior to SNMPv3 is NOT
	RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to		RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
	enable cryptographic security. It is a customer/operator		enable cryptographic security. It is then a customer/operator
	responsibility to ensure that the SNMP entity giving access to an		responsibility to ensure that the SNMP entity giving access to an
	instance of this MIB module, is properly configured to give access to		instance of this MIB module is properly configured to give access to
	the objects only to those principals (users) that have legitimate		the objects only to those principals (users) that have legitimate
	rights to indeed GET or SET (change/create/delete) them.		rights to indeed GET or SET (change/create/delete) them.
	7. References		8. References
	7.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirements Levels", BCP 14, RFC 2119, March 1997.		Requirements Levels", BCP 14, RFC 2119, March 1997.
	[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,		[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Structure of Management		Rose, M. and S. Waldbusser, "Structure of Management
	Information Version 2 (SMIv2)", STD 58, RFC 2578, April		Information Version 2 (SMIv2)", STD 58, RFC 2578, April
	1999.		1999.
	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,		[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Textual Conventions for		Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2",
	SMIv2", STD 58, RFC 2579, April 1999.		STD 58, RFC 2579, April 1999.
	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,		[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Conformance Statements for		Rose, M. and S. Waldbusser, "Conformance Statements for
	SMIv2", STD 58, RFC 2580, April 1999.		SMIv2", STD 58, RFC 2580, April 1999.
	[RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group		[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
	MIB", RFC 2863, June 2000.		MIB", RFC 2863, June 2000.
	[RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table		[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
	Extension to the Interfaces Group MIB", RFC 2864, June 2000.		Extension to the Interfaces Group MIB", RFC 2864, June 2000.
	[SONETng] Tesink, K., "Definitions of Managed Objects for the		[SONETng] Tesink, K., "Definitions of Managed Objects for the
	SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-		SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-
	00.txt>, work in progress.		01.txt>, work in progress.
	[T1.231] American National Standard for Telecommunications - Digital		[T1.231] American National Standard for Telecommunications - Digital
	Hierarchy - Layer 1 In-Service Digital Transmission		Hierarchy - Layer 1 In-Service Digital Transmission
	Performance Monitoring, ANSI T1.231-1997, September 1997.		Performance Monitoring, ANSI T1.231-1997, September 1997.
	[ETHERIF] Flick, J., "Definitions of Managed Objects for the		[ETHERIF] Flick, J., "Definitions of Managed Objects for the
	Ethernet-like Interface Types", <draft-ietf-hubmib-etherif-		Ethernet-like Interface Types", <draft-ietf-hubmib-etherif-
	mib-v3-01.txt>, work in progress.		mib-v3-02.txt>, work in progress.
	[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3		[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3
	Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau-		Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau-
	mib-v3-01.txt>, work in progress.		mib-v3-02.txt>, work in progress.
	[802.3ae] Institute of Electrical and Electronic Engineers, IEEE Std		[802.3ae] Institute of Electrical and Electronic Engineers, IEEE Std
	802.3ae-2002, "IEEE Standard for Carrier Sense Multiple		802.3ae-2002, "IEEE Standard for Carrier Sense Multiple
	Access with Collision Detection (CSMA/CD) Access Method and		Access with Collision Detection (CSMA/CD) Access Method and
	Physical Layer Specifications - Media Access Control (MAC)		Physical Layer Specifications - Media Access Control (MAC)
	Parameters, Physical Layer and Management Parameters for 10		Parameters, Physical Layer and Management Parameters for 10
	Gb/s Operation", August 2002.		Gb/s Operation", August 2002.
	7.2. Informative References		8.2. Informative References
	[RFC2570bis]		[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
	Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction and Applicability Statements for Internet-		"Introduction and Applicability Statements for Internet-
	Standard Management Framework", <draft-ietf-snmpv3-		Standard Management Framework", RFC 3410, December 2002.
	rfc2570bis-03.txt>, work in progress.
	8. Authors' Addresses		9. Contributors
	Mike Ayers		Mike Ayers
	1204 Knox Ave.		1204 Knox Ave.
	San Jose, CA 95122		San Jose, CA 95122
	USA		USA
	Phone: +1 408 857 6810		Phone: +1 408 857 6810
	EMail: mike.ayers@earthling.net		EMail: mike.ayers@earthling.net
	John Flick		John Flick
	Hewlett-Packard Company		Hewlett-Packard Company
	8000 Foothills Blvd. M/S 5557		8000 Foothills Blvd. M/S 5557
	Roseville, CA 95747-5557		Roseville, CA 95747-5557
	USA		USA
	Phone: +1 916 785 4018		Phone: +1 916 785 4018
	Fax: +1 916 785 1199		Fax: +1 916 785 1199
	EMail: johnf@rose.hp.com		EMail: johnf@rose.hp.com
	C. M. Heard
	600 Rainbow Dr. #141
	Mountain View, CA 94041-2542
	USA
	Phone: +1 650 964 8391
	EMail: heard@pobox.com
	Kam Lam		Kam Lam
	Lucent Technologies		Lucent Technologies
	101 Crawfords Corner Road, Room 4C-616A		101 Crawfords Corner Road, Room 4C-616A
	Holmdel, NJ 07733		Holmdel, NJ 07733
	USA		USA
	Phone: +1 732 949 8338		Phone: +1 732 949 8338
	EMail: hklam@lucent.com		EMail: hklam@lucent.com
	Kerry McDonald		Kerry McDonald
	Institute for Applied Supercomputing		Institute for Applied Supercomputing
	California State University San Bernardino		California State University San Bernardino
	EMail: kerry_mcd@hotmail.com		EMail: kerry_mcd@hotmail.com
	kmcdonal@csci.csusb.edu		kmcdonal@csci.csusb.edu
	K. C. Norseth		K. C. Norseth
	934 S. Palos Verdes Dr.		L-3 Communications
	Kaysville, Utah 84037		640 N. 2200 West.
			Salt Lake City, Utah 84116-0850
	USA		USA
	Phone: +1 801 546 3316		Phone: +1 801 594 2809
	EMail: kcn@norseth.com		EMail: kenyon.c.norseth@L-3com.com
			kcn@norseth.com
	Kaj Tesink		Kaj Tesink
	Telcordia Technologies		Telcordia Technologies
	331 Newman Springs Road		331 Newman Springs Road
	P.O. Box 7020		P.O. Box 7020
	Red Bank, NJ 07701-7020		Red Bank, NJ 07701-7020
	USA		USA
	Phone: +1 732 758 5254		Phone: +1 732 758 5254
	EMail: kaj@research.telcordia.com		EMail: kaj@research.telcordia.com
	9. Intellectual Property		10. Editor's Address
	The IETF takes no position regarding the validity or scope of any		C. M. Heard
	intellectual property or other rights that might be claimed to		600 Rainbow Dr. #141
	pertain to the implementation or use of the technology described in		Mountain View, CA 94041-2542
	this document or the extent to which any license under such rights		USA
	might or might not be available; neither does it represent that it
	has made any effort to identify any such rights. Information on the
	IETF's procedures with respect to rights in standards-track and
	standards-related documentation can be found in BCP-11. Copies of
	claims of rights made available for publication and any assurances of
	licenses to be made available, or the result of an attempt made to
	obtain a general license or permission for the use of such
	proprietary rights by implementors or users of this specification can
	be obtained from the IETF Secretariat.
	The IETF invites any interested party to bring to its attention any		Phone: +1 650 964 8391
	copyrights, patents or patent applications, or other proprietary		EMail: heard@pobox.com
	rights which may cover technology that may be required to practice
	this standard. Please address the information to the IETF Executive
	Director.
	Appendix A: Collection of Performance Data Using WIS MDIO Registers		Appendix A: Collection of Performance Data Using WIS MDIO Registers
	The purpose of this appendix is to illustrate how the WIS MDIO		The purpose of this appendix is to illustrate how the WIS MDIO
	registers specified in [802.3ae] subclause 45.2.2 (and more		registers specified in [802.3ae] subclause 45.2.2 (and more
	specifically the subset required by [802.3ae] subclause 50.3.11) can		specifically the subset required by [802.3ae] subclause 50.3.11) can
	be used to collect performance data either according to the		be used to collect performance data either according to the
	conventions adopted by this document or according to the conventions		conventions adopted by this document or according to the conventions
	specified in [802.3ae] Clause 30.		specified in [802.3ae] Clause 30.
	skipping to change at page 36, line 7		skipping to change at page 36, line 7
	start by polling the 10G WIS status 3 register and the various error		start by polling the 10G WIS status 3 register and the various error
	count registers to find the defects and error counts for the previous		count registers to find the defects and error counts for the previous
	second, and it could determine the number of errors and whether the		second, and it could determine the number of errors and whether the
	second was an errored second, a severely errored second, or a		second was an errored second, a severely errored second, or a
	severely errored frame second in the same manner as above. The rest		severely errored frame second in the same manner as above. The rest
	of the process would simply be to increment the generalized non-		of the process would simply be to increment the generalized non-
	resetable counters without consideration of any inhibiting rules.		resetable counters without consideration of any inhibiting rules.
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2003). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
	skipping to change at page 40, line 9		skipping to change at page 40, line 9
	unnecessary verbiage.		unnecessary verbiage.
	12.) The MDIO register name spellings in Section 3.7, Section 4,		12.) The MDIO register name spellings in Section 3.7, Section 4,
	and Appendix A were updated to match those in P802.3ae/D4.2		and Appendix A were updated to match those in P802.3ae/D4.2
	subclause 45.2.2.		subclause 45.2.2.
	13.) A missing comma was added to the		13.) A missing comma was added to the
	etherWisDeviceRxTestPatternErrors REFERENCE clause.		etherWisDeviceRxTestPatternErrors REFERENCE clause.
	14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted		14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted
	and etherWisPathCurrentJ1Transmitted were updates to state that		and etherWisPathCurrentJ1Transmitted were updated to state that
	the default value should be '89'h followed by 16 octets of '00'h,		the default value should be '89'h followed by 16 octets of '00'h,
	rather than 16 octets of '00'h followed by '89'h (this matches the		rather than 16 octets of '00'h followed by '89'h (this matches the
	resolution in P802.3ae/D4.2 of a byte ordering inconsistency).		resolution in P802.3ae/D4.2 of a byte ordering inconsistency).
	15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and		15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and
	etherWisPathCurrentStatus were changed from 'read-write' to		etherWisPathCurrentStatus were changed from 'read-write' to
	16.) In Section 6, "Security Considerations", all read-write		16.) In Section 6, "Security Considerations", all read-write
	objects have been explicitly listed and mention of read-create		objects have been explicitly listed and mention of read-create
	objects has been removed.		objects has been removed.
	skipping to change at page 42, line 5		skipping to change at page 42, line 5
	13.) The DESCRIPTION clause of the MODULE-IDENTITY invocation was		13.) The DESCRIPTION clause of the MODULE-IDENTITY invocation was
	updated to include the required copyright statement.		updated to include the required copyright statement.
	14.) The dates in the LAST-UPDATED and REVISION clauses of the		14.) The dates in the LAST-UPDATED and REVISION clauses of the
	MODULE-IDENTITY invocation were changed to the current date.		MODULE-IDENTITY invocation were changed to the current date.
	15.) The document pagination was changed to match that expected		15.) The document pagination was changed to match that expected
	upon publication as an RFC.		upon publication as an RFC.
	To-Do List		The following changes were made to <draft-ietf-hubmib-wis-mib-05.txt>
			to produce <draft-ietf-hubmib-wis-mib-06.txt>:
	NOTE TO RFC Editor: prior to publishing this document please take		1.) Names of WIS MIB design team members other than the editor
	care of any open items listed below and then remove this section.		were removed from author list on front page. They now appear in
			the Contributors section with (updated) contact information.
	1.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must		2.) Reference tag [2570bis] was replaced with [RFC3410], and the
	be updated to point to the appropriate RFCs when the respective		corresponding informative reference was updated to point to RFC
	Internet Drafts are published, and all occurrences of the		3410.
	reference tags must be changed to [RFCnnnn] where nnnn is the
	assigned RFC number.
	2.) Informative reference [2570bis] should be updated to point to		3.) Working group mailing list information was added to the
	the appropriate RFC when the corresponding Internet Draft is		CONTACT-INFO clause of the MODULE-IDENTITY invocation.
	published, and the reference tag should be changed to match.
	3.) It must be determined whether members of WIS MIB design team		4.) The dates in the LAST-UPDATED and REVISION clauses of the
	other than editor C. M. Heard will continue to be listed in the		MODULE-IDENTITY invocation were changed to the current date.
	front page as co-authors or whether they will be listed in a
	Contributors section with contact information, in a Contributors		5.) The Intellectual Property section was relocated.
	section without contact information, or in the Acknowledgments
			6.) The working group names in the Acknowlegments section were
			corrected.
			7.) The part of the Security Considerations section dealing with
			read-only objects was wordsmithed, and some typos in the last part
			were fixed.
			8.) References [SONETng], [ETHERIF], and [MAU-MIB] were updated to
			point to <draft-ietf-atommib-rfc2558bis-01.txt>, <draft-ietf-
			hubmib-etherif-mib-v3-02.txt>, and <draft-ietf-hubmib-mau-mib-v3-
			02.txt>, respectively.
			9.) All references to multi-author RFCs were updated to conform to
			the style used in recently published RFCs.
			10.) The "To-Do List" was replaced with a "NOTES TO RFC Editor"
	section.		section.
			************************************************************
			* NOTES TO RFC Editor (to be removed prior to publication) *
			* *
			* 1.) The normative references [SONETng], [ETHERIF], and *
			* [MAU-MIB] must be updated to point to the appropriate *
			* RFCs when the respective Internet Drafts are published, *
			* and all occurrences of the reference tags must be *
			* changed to [RFCnnnn] where nnnn is the assigned RFC *
			* number. *
			* *
			* 2.) Please replace all occurrences of "yyyy" in the *
			* DESCRIPTION clause of the MODULE-IDENTITY invocation *
			* in Section 4 with the RFC number assigned to this *
			* specification and remove the accompanying notes. *
			* *
			* 3.) Please replace "XXX" in the MODULE-IDENTITY value *
			* with an IANA-assigned value under the 'transmission' *
			* subtree and remove the accompanying note. *
			* *
			* 4.) Please remove the "Revision History" section. *
			* *
			************************************************************
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/