draft-ietf-hubmib-etherif-mib-00.txt		draft-ietf-hubmib-etherif-mib-01.txt
	Hub MIB Working Group J. Johnson		Hub MIB Working Group J. Johnson
	INTERNET DRAFT cisco Systems, Inc.		INTERNET DRAFT cisco Systems, Inc.
	June 1996		November 1996
	Definitions of Managed Objects for		Definitions of Managed Objects for
	the Ethernet-like Interface Types		the Ethernet-like Interface Types
	<draft-ietf-hubmib-etherif-mib-00.txt>		<draft-ietf-hubmib-etherif-mib-01.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas, and		documents of the Internet Engineering Task Force (IETF), its areas, and
	its working groups. Note that other groups may also distribute working		its working groups. Note that other groups may also distribute working
	documents as Internet-Drafts.		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
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	skipping to change at page 2, line 47		skipping to change at page 2, line 47
	3. Change Log		3. Change Log
	This section enumerates changes made to RFC 1650 to produce this		This section enumerates changes made to RFC 1650 to produce this
	document.		document.
	(1) The MODULE-IDENTITY has been updated to reflect the changes		(1) The MODULE-IDENTITY has been updated to reflect the changes
	in the MIB.		in the MIB.
	(2) A new object, dot3StatsSymbolErrors, has been added.		(2) A new object, dot3StatsSymbolErrors, has been added.
	(3) The description of the object dot3StatsSQETestErrors has		(3) The definition of the object dot3StatsIndex has been
	been updated to reflect the fact that this object is not
	applicable to 100Base-T interfaces.
	(4) The definition of the object dot3StatsIndex has been
	converted to use the SMIv2 OBJECT-TYPE macro.		converted to use the SMIv2 OBJECT-TYPE macro.
	(5) A new conformance group, etherStats100MbsGroup, has been		(4) A new conformance group, etherStats100MbsGroup, has been
	added.		added.
	(6) A new compliance statement, ether100MbsCompliance, has		(5) A new compliance statement, ether100MbsCompliance, has
	been added.		been added.
	(7) The Acknowledgements were extended to provide a more		(6) The Acknowledgements were extended to provide a more
	complete history of the origin of this document.		complete history of the origin of this document.
	4. Overview		4. Overview
	Instances of these object types represent attributes of an interface to		Instances of these object types represent attributes of an interface to
	an ethernet-like communications medium. At present, ethernet-like media		an ethernet-like communications medium. At present, ethernet-like media
	are identified by the following values of the ifType object in the		are identified by the following values of the ifType object in the
	Interfaces MIB [12]:		Interfaces MIB [12]:
	ethernet-csmacd(6)		ethernet-csmacd(6)
	skipping to change at page 4, line 38		skipping to change at page 4, line 35
	MIB must clarify. Each of these areas is addressed in a following		MIB must clarify. Each of these areas is addressed in a following
	subsection. The implementor is referred to RFC 1573 in order to		subsection. The implementor is referred to RFC 1573 in order to
	understand the general intent of these areas.		understand the general intent of these areas.
	4.2.1. Layering Model		4.2.1. Layering Model
	This MIB does not provide for layering. There are no sublayers.		This MIB does not provide for layering. There are no sublayers.
	EDITOR'S NOTE:		EDITOR'S NOTE:
	One could forsee the development of an 802.2 and enet-transceiver MIB.		One could foresee the development of an 802.2 and enet-transceiver MIB.
	They could be higher and lower sublayers, respectively. All that THIS		They could be higher and lower sublayers, respectively. All that THIS
	document should do is allude to the possibilities and urge the		document should do is allude to the possibilities and urge the
	implementor to be aware of the possibility and that they may have		implementor to be aware of the possibility and that they may have
	requirements which supersede the requirements in this document.		requirements which supersede the requirements in this document.
	4.2.2. Virtual Circuits		4.2.2. Virtual Circuits
	This medium does not support virtual circuits and this area is not		This medium does not support virtual circuits and this area is not
	applicable to this MIB.		applicable to this MIB.
	4.2.3. ifTestTable		4.2.3. ifTestTable
	This MIB defines two tests for media which are instumented with this		This MIB defines two tests for media which are instrumented with this
	MIB; TDR and Loopback. Implementation of these tests is not required.		MIB; TDR and Loopback. Implementation of these tests is not required.
	Many common interface chips do not support one or both of these tests.		Many common interface chips do not support one or both of these tests.
	These two tests are provided as a convenience, allowing a common method		These two tests are provided as a convenience, allowing a common method
	to invoke the test.		to invoke the test.
	Standard MIBs do not include objects in which to return the results of		Standard MIBs do not include objects in which to return the results of
	the TDR test. Any needed objects MUST be provided in the vendor		the TDR test. Any needed objects MUST be provided in the vendor
	specific MIB.		specific MIB.
	skipping to change at page 6, line 22		skipping to change at page 6, line 19
	ethernet-csmacd(6)		ethernet-csmacd(6)
	iso88023-csmacd(7)		iso88023-csmacd(7)
	starLan(11)		starLan(11)
	fastEther(62)		fastEther(62)
	fastEtherFX(69)		fastEtherFX(69)
	Interfaces with any of the first three ifType values map to the		Interfaces with any of the first three ifType values map to the
	EtherLike-MIB in the same manner. The EtherLike-MIB etherCompliance		EtherLike-MIB in the same manner. The EtherLike-MIB etherCompliance
	compliance statement applies equally to all three types; there are no		compliance statement applies equally to all three types; there are no
	implementation differences. Similiarly, interfaces with either of the		implementation differences. Similarly, interfaces with either of the
	last two ifType values map to the EtherLike-MIB in the same manner. The		last two ifType values map to the EtherLike-MIB in the same manner. The
	EtherLike-MIB ether100MbsCompliance compliance statement applies equally		EtherLike-MIB ether100MbsCompliance compliance statement applies equally
	to both types; there are no implementation differences.		to both types; there are no implementation differences.
	5. Definitions		5. Definitions
	EtherLike-MIB DEFINITIONS ::= BEGIN		EtherLike-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, Counter32, mib-2 FROM SNMPv2-SMI		MODULE-IDENTITY, OBJECT-TYPE, Counter32, mib-2 FROM SNMPv2-SMI
	skipping to change at page 10, line 40		skipping to change at page 10, line 40
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A count of times that the SQE TEST ERROR		"A count of times that the SQE TEST ERROR
	message is generated by the PLS sublayer for a		message is generated by the PLS sublayer for a
	particular interface. The SQE TEST ERROR		particular interface. The SQE TEST ERROR
	message is defined in section 7.2.2.2.4 of		message is defined in section 7.2.2.2.4 of
	ANSI/IEEE 802.3-1985 and its generation is		ANSI/IEEE 802.3-1985 and its generation is
	described in section 7.2.4.6 of the same		described in section 7.2.4.6 of the same
	document.		document."
	The SQE test function is not a part of 100 Mb/sec
	operation, so an instance of this object need not
	be present for 100 Mb/sec interfaces."
	REFERENCE		REFERENCE
	"ANSI/IEEE Std 802.3-1985 Carrier Sense		"ANSI/IEEE Std 802.3-1985 Carrier Sense
	Multiple Access with Collision Detection Access		Multiple Access with Collision Detection Access
	Method and Physical Layer Specifications"		Method and Physical Layer Specifications"
	::= { dot3StatsEntry 6 }		::= { dot3StatsEntry 6 }
	dot3StatsDeferredTransmissions OBJECT-TYPE		dot3StatsDeferredTransmissions OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A count of frames for which the first		"A count of frames for which the first
	transmission attempt on a particular interface		transmission attempt on a particular interface
	is delayed because the medium is busy.		is delayed because the medium is busy.
	The count represented by an instance of this		The count represented by an instance of this
	skipping to change at page 20, line 41		skipping to change at page 20, line 39
	SNMPv2 SMI, RFC 1650 [11], both of which were edited by Frank Kastenholz		SNMPv2 SMI, RFC 1650 [11], both of which were edited by Frank Kastenholz
	of FTP Software and produced by the Ethernet MIB Working Group. This		of FTP Software and produced by the Ethernet MIB Working Group. This
	document extends those documents by providing support for 100 Mb/sec		document extends those documents by providing support for 100 Mb/sec
	ethernet interfaces as outlined in [6].		ethernet interfaces as outlined in [6].
	RFC 1623 and RFC 1650, in turn, are based on the Draft Standard Ethernet		RFC 1623 and RFC 1650, in turn, are based on the Draft Standard Ethernet
	MIB, RFC 1398 [9], also edited by Frank Kastenholz and produced by the		MIB, RFC 1398 [9], also edited by Frank Kastenholz and produced by the
	Ethernet MIB Working Group.		Ethernet MIB Working Group.
	RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, RFC		RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, RFC
	1284 [8], which was editted by John Cook of Chipcom and produced by the		1284 [8], which was edited by John Cook of Chipcom and produced by the
	Transmission MIB Working Group. The Ethernet MIB Working Group gathered		Transmission MIB Working Group. The Ethernet MIB Working Group gathered
	implementation experience of the variables specified in RFC 1284 and		implementation experience of the variables specified in RFC 1284 and
	used that information to develop this revised MIB.		used that information to develop this revised MIB.
	RFC 1284, in turn, is based on a document written by Frank Kastenholz,		RFC 1284, in turn, is based on a document written by Frank Kastenholz,
	then of Interlan, entitled IEEE 802.3 Layer Management Draft M		then of Interlan, entitled IEEE 802.3 Layer Management Draft M
	compatible MIB for TCP/IP Networks [7]. This document has been modestly		compatible MIB for TCP/IP Networks [7]. This document has been modestly
	reworked, initially by the SNMP Working Group, and then by the		reworked, initially by the SNMP Working Group, and then by the
	Transmission Working Group, to reflect the current conventions for		Transmission Working Group, to reflect the current conventions for
	defining objects for MIB interfaces. James Davin, of the MIT Laboratory		defining objects for MIB interfaces. James Davin, of the MIT Laboratory
	for Computer Science, and Keith McCloghrie of Hughes LAN Systems,		for Computer Science, and Keith McCloghrie of Hughes LAN Systems,
	contributed to later drafts of this memo. Marshall Rose of Performance		contributed to later drafts of this memo. Marshall Rose of Performance
	Systems International, Inc. converted the document into its current		Systems International, Inc. converted the document into its current
	concise format. Anil Rijsinghani of DEC contributed text that more		concise format. Anil Rijsinghani of DEC contributed text that more
	adequately describes the TDR test. Thanks to Frank Kastenholz of		adequately describes the TDR test. Thanks to Frank Kastenholz of
	Interlan and Louis Steinberg of IBM for their experimentation.		Interlan and Louis Steinberg of IBM for their experimentation.
	7. References		7. References
	[1] Information processing systems - Open Systems Interconnection -		[1] Information processing systems - Open Systems Interconnection -
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/