< draft-ietf-atommib-rfc2496bis-05.txt		draft-ietf-atommib-rfc2496bis-06.txt >
	INTERNET-DRAFT DS3/E3 MIB October 2003		INTERNET-DRAFT DS3/E3 MIB April 2004
	Definitions of Managed Objects		Definitions of Managed Objects
	for the DS3/E3 Interface Type		for the DS3/E3 Interface Type
	Sun October 19 11:52:50 EDT 2003		Sun April 4 11:52:50 EDT 2004
	draft-ietf-atommib-rfc2496bis-05.txt		draft-ietf-atommib-rfc2496bis-06.txt
	Orly Nicklass (editor)		Orly Nicklass (editor)
	RAD Data Communications, Ltd.		RAD Data Communications, Ltd.
	Orly_n@rad.com		Orly_n@rad.com
	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,
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 (2003). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	In particular, it describes objects used for managing DS3 and E3		In particular, it describes objects used for managing DS3 and E3
	interfaces. This document is a companion to the documents that		interfaces. This document is a companion to the documents that
	define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous		define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous
	Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface		Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
	Types.		Types.
	This document entirely replaces RFC 2496.		This document obsoletes RFC 2496.
	1. The Internet Standard Management Framework		1. 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 3410 [RFC3410].		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].
	1.1. Changes from RFC2496		1.1. Changes from RFC2496
	This MIB obsoletes RFC2496. The changes from RFC2496 are the		The changes from RFC2496 are the following:
	following:
	(1) The dsx3FracIfIndex SYNTAX matches the description range.		(1) The dsx3FracIfIndex SYNTAX matches the description range.
	(2) Reference was added to Circuit Identifier object.		(2) Reference was added to Circuit Identifier object.
	(3) Usage of ifStackTable section was updated.		(3) Usage of ifStackTable section was updated.
	(4) Align the DESCRIPTION clauses of few statistic objects with		(4) Align the DESCRIPTION clauses of few statistic objects with
	thenear end definition, the far end definition and with		thenear end definition, the far end definition and with
	RFC3593.		RFC3593.
	(5) Add new value, dsx3M13, to dsx3LineType.		(5) Add new value, dsx3M13, to dsx3LineType.
			1.2. Changes from RFC1407
			The changes from RFC1407 are the following:
			(1) The Fractional Table has been deprecated.
			(2) This document uses SMIv2.
			(3) Values are given for ifTable and ifXTable.
			(4) Example usage of ifStackTable is included.
			(5) dsx3IfIndex has been deprecated.
			(6) The definition of valid intervals has been clarified
			for the case where the agent proxied for other devices. In
			particular, the treatment of missing intervals has been
			clarified.
			(7) An inward loopback has been added.
			(8) Additional lineStatus bits have been added for Near End
			in Unavailable Signal State, Carrier Equipment Out of
			Service.
			(9) A read-write line Length object has been added.
			(10) Added a lineStatus last change, trap and enabler.
			(11) Textual Conventions for statistics objects have
			been used.
			(12) A new object, dsx3LoopbackStatus, has been introduced to
			reflect the loopbacks established on a DS3/E3 interface and
			the source to the requests. dsx3LoopbackConfig continues
			to be the desired loopback state while dsx3LoopbackStatus
			reflects the actual state.
			(13) A dual loopback has been added to allow the setting of an
			inward loopback and a line loopback at the same time.
			(14) An object has been added to indicated whether or not this
			is a channelized DS3/E3.
			(15) A new object has been added to indicate which DS1 is to set
			for remote loopback.
	2. Overview		2. Overview
	These objects are used when the particular media being used to		These objects are used when the particular media being used to
	realize an interface is a DS3/E3 interface. At present, this applies		realize an interface is a DS3/E3 interface. At present, this applies
	to these values of the ifType variable in the Internet-standard MIB:		to these values of the ifType variable in the Internet-standard MIB:
	ds3 (30)		ds3 (30)
	The DS3 definitions contained herein are based on the DS3		The DS3 definitions contained herein are based on the DS3
	specifications in ANSI T1.102-1987 [ANSI-T1.102], ANSI T1.107-1988		specifications in ANSI T1.102-1987 [ANSI-T1.102], ANSI T1.107-1988
	skipping to change at page 16, line 20 ¶		skipping to change at page 17, line 20 ¶
	MODULE-IDENTITY, OBJECT-TYPE,		MODULE-IDENTITY, OBJECT-TYPE,
	NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI		NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI
	DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC		DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC
	MODULE-COMPLIANCE, OBJECT-GROUP,		MODULE-COMPLIANCE, OBJECT-GROUP,
	NOTIFICATION-GROUP FROM SNMPv2-CONF		NOTIFICATION-GROUP FROM SNMPv2-CONF
	InterfaceIndex FROM IF-MIB		InterfaceIndex FROM IF-MIB
	PerfCurrentCount, PerfIntervalCount,		PerfCurrentCount, PerfIntervalCount,
	PerfTotalCount FROM PerfHist-TC-MIB;		PerfTotalCount FROM PerfHist-TC-MIB;
	ds3 MODULE-IDENTITY		ds3 MODULE-IDENTITY
	LAST-UPDATED "200310190000Z"		LAST-UPDATED "200404040000Z"
	ORGANIZATION "IETF AToM MIB Working Group"		ORGANIZATION "IETF AToM MIB Working Group"
	CONTACT-INFO		CONTACT-INFO
	"WG charter:		"WG charter:
	http://www.ietf.org/html.charters/atommib-charter.html		http://www.ietf.org/html.charters/atommib-charter.html
	Mailing Lists:		Mailing Lists:
	General Discussion: atommib@research.telcordia.com		General Discussion: atommib@research.telcordia.com
	To Subscribe: atommib-request@research.telcordia.com		To Subscribe: atommib-request@research.telcordia.com
	Editor: Orly Nicklass		Editor: Orly Nicklass
	skipping to change at page 16, line 48 ¶		skipping to change at page 17, line 48 ¶
	DESCRIPTION		DESCRIPTION
	"The is the MIB module that describes		"The is the MIB module that describes
	DS3 and E3 interfaces objects.		DS3 and E3 interfaces objects.
	Copyright (c) The Internet Society (2003). This		Copyright (c) The Internet Society (2003). This
	version of this MIB module is part of RFC yyyy;		version of this MIB module is part of RFC yyyy;
	see the RFC itself for full legal notices."		see the RFC 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 "200308170000Z"		REVISION "200404040000Z"
	DESCRIPTION		DESCRIPTION
	"The RFC yyyy version of this MIB module."		"The RFC yyyy version of this MIB module.
	-- RFC Ed.: replace yyyy with actual RFC number & remove this notice		-- RFC Ed.: replace yyyy with actual RFC number & remove this notice
			The key changes made to this MIB module
			since its publication in RFC 2496 are as follows:
			(1) The dsx3FracIfIndex SYNTAX matches the description range.
			(2) Reference was added to Circuit Identifier object.
			(3) Usage of ifStackTable section was updated.
			(4) Align the DESCRIPTION clauses of few statistic objects with
			thenear end definition, the far end definition and with
			RFC3593.
			(5) Add new value, dsx3M13, to dsx3LineType."
	REVISION "199808012130Z"		REVISION "199808012130Z"
	DESCRIPTION		DESCRIPTION
	"The RFC 2496 version of this MIB module."		"The RFC 2496 version of this MIB module.
			The key changes made to this MIB module
			since its publication in RFC 1407 are as follows:
			(1) The Fractional Table has been deprecated.
			(2) This document uses SMIv2.
			(3) Values are given for ifTable and ifXTable.
			(4) Example usage of ifStackTable is included.
			(5) dsx3IfIndex has been deprecated.
			(6) The definition of valid intervals has been clarified
			for the case where the agent proxied for other devices. In
			particular, the treatment of missing intervals has been
			clarified.
			(7) An inward loopback has been added.
			(8) Additional lineStatus bits have been added for Near End
			in Unavailable Signal State, Carrier Equipment Out of
			Service.
			(9) A read-write line Length object has been added.
			(10) Added a lineStatus last change, trap and enabler.
			(11) Textual Conventions for statistics objects have
			been used.
			(12) A new object, dsx3LoopbackStatus, has been introduced to
			reflect the loopbacks established on a DS3/E3 interface and
			the source to the requests. dsx3LoopbackConfig continues
			to be the desired loopback state while dsx3LoopbackStatus
			reflects the actual state.
			(13) A dual loopback has been added to allow the setting of an
			inward loopback and a line loopback at the same time.
			(14) An object has been added to indicated whether or not this
			is a channelized DS3/E3.
			(15) A new object has been added to indicate which DS1 is to set
			for remote loopback."
	REVISION "199301252028Z"		REVISION "199301252028Z"
	DESCRIPTION		DESCRIPTION
	"Initial version, published as RFC 1407."		"Initial version, published as RFC 1407."
	::= { transmission 30 }		::= { transmission 30 }
	-- The DS3/E3 Near End Group		-- The DS3/E3 Near End Group
	-- The DS3/E3 Near End Group consists of four tables:		-- The DS3/E3 Near End Group consists of four tables:
	skipping to change at page 51, line 4 ¶		skipping to change at page 53, line 4 ¶
	dsx3FracIfIndex.2. 7 = 4 dsx3FracIfIndex.2.21 = 6		dsx3FracIfIndex.2. 7 = 4 dsx3FracIfIndex.2.21 = 6
	dsx3FracIfIndex.2. 8 = 4 dsx3FracIfIndex.2.22 = 6		dsx3FracIfIndex.2. 8 = 4 dsx3FracIfIndex.2.22 = 6
	dsx3FracIfIndex.2. 9 = 4 dsx3FracIfIndex.2.23 = 6		dsx3FracIfIndex.2. 9 = 4 dsx3FracIfIndex.2.23 = 6
	dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.24 = 6		dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.24 = 6
	dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.25 = 6		dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.25 = 6
	dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.26 = 6		dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.26 = 6
	dsx3FracIfIndex.2.13 = 5 dsx3FracIfIndex.2.27 = 6		dsx3FracIfIndex.2.13 = 5 dsx3FracIfIndex.2.27 = 6
	dsx3FracIfIndex.2.14 = 5 dsx3FracIfIndex.2.28 = 6		dsx3FracIfIndex.2.14 = 5 dsx3FracIfIndex.2.28 = 6
	For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and		For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and
	dsx3ClearChannel there are 28 legal channels,		dsx3ClearChannel there are 28 legal channels,
	numbered 1 throug h 28.		numbered 1 through 28.
	For e3Framed there are 16 legal channels, numbered		For e3Framed there are 16 legal channels, numbered
	1 through 16. The channels (1..16) correspond		1 through 16. The channels (1..16) correspond
	directly to the equivalently numbered time-slots."		directly to the equivalently numbered time-slots."
	::= { ds3 13 }		::= { ds3 13 }
	dsx3FracEntry OBJECT-TYPE		dsx3FracEntry OBJECT-TYPE
	SYNTAX Dsx3FracEntry		SYNTAX Dsx3FracEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS deprecated		STATUS deprecated
	skipping to change at page 53, line 20 ¶		skipping to change at page 55, line 20 ¶
	OBJECTS { dsx3LineStatus,		OBJECTS { dsx3LineStatus,
	dsx3LineStatusLastChange }		dsx3LineStatusLastChange }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A dsx3LineStatusChange trap is sent when the		"A dsx3LineStatusChange trap is sent when the
	value of an instance of dsx3LineStatus changes. It		value of an instance of dsx3LineStatus changes. It
	can be utilized by an NMS to trigger polls. When		can be utilized by an NMS to trigger polls. When
	the line status change results in a lower level		the line status change results in a lower level
	line status change (i.e. ds1), then no traps for		line status change (i.e. ds1), then no traps for
	the lower level are sent."		the lower level are sent."
	::= { ds3Traps 0 1 }		::= { ds3Traps 0 1 }
	-- conformance information
	ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 }		-- conformance information
			ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 }
	ds3Groups OBJECT IDENTIFIER ::= {		ds3Groups OBJECT IDENTIFIER ::= { ds3Conformance 1 }
	ds3Conformance 1 } ds3Compliances OBJECT		ds3Compliances OBJECT IDENTIFIER ::= { ds3Conformance 2 }
	IDENTIFIER ::= { ds3Conformance 2 }
	-- compliance statements		-- compliance statements
	ds3Compliance MODULE-COMPLIANCE		ds3Compliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The compliance statement for DS3/E3		"The compliance statement for DS3/E3 interfaces."
	interfaces."
	MODULE -- this module		MODULE -- this module
	MANDATORY-GROUPS { ds3NearEndConfigGroup,		MANDATORY-GROUPS { ds3NearEndConfigGroup,
	ds3NearEndStatisticsGroup }		ds3NearEndStatisticsGroup }
	GROUP ds3FarEndGroup		GROUP ds3FarEndGroup
	DESCRIPTION		DESCRIPTION
	"Implementation of this group is optional for all		"Implementation of this group is optional for all
	systems that attach to a DS3 Interface. However,		systems that attach to a DS3 Interface. However,
	only C-bit Parity and SYNTRAN DS3 applications		only C-bit Parity and SYNTRAN DS3 applications
	have the capability (option) of providing this		have the capability (option) of providing this
	information."		information."
			GROUP ds3NearEndOptionalTrapGroup
			DESCRIPTION
			"Implementation of this group is optional for all
			systems that attach to a DS3 Interface. If it is
			implemented then ds3NearEndOptionalConfigGroup
			should also be implemented."
	GROUP ds3NearEndOptionalConfigGroup		GROUP ds3NearEndOptionalConfigGroup
	DESCRIPTION		DESCRIPTION
	"Implementation of this group is optional for all		"Implementation of this group is optional for all
	systems that attach to a DS3 interface."		systems that attach to a DS3 interface."
	OBJECT dsx3LineType		OBJECT dsx3LineType
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access for the line type is not required."		"Write access for the line type is not required."
	skipping to change at page 63, line 21 ¶		skipping to change at page 66, line 7 ¶
	This document and the information contained herein is provided on an		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	8. Acknowledgments		8. Acknowledgments
	This document was produced by the AToM MIB Working Group.		This document was produced by the AToM MIB Working Group. The Editor
			would like to dedicate a special thanks to C. Mike Heard for
			providing a top notch doctor review and many helpful suggestions, and
			to acknowledge D. Fowler, Editor of RFC 2496, T. Cox and K. Tesink
			Editors of RFC 1407.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC2578]		[RFC2578]
	McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,		McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
	and S. Waldbusser, "Structure of Management Information Version 2		and S. Waldbusser, "Structure of Management Information Version 2
	(SMIv2)", STD 58 RFC 2578, April 1999.		(SMIv2)", STD 58 RFC 2578, April 1999.
	skipping to change at page 65, line 36 ¶		skipping to change at page 68, line 36 ¶
	[RFC1407]		[RFC1407]
	T. Cox, K. Tesink, "Definitions of Managed Objects for the DS3/E3		T. Cox, K. Tesink, "Definitions of Managed Objects for the DS3/E3
	Interface Types", RFC 1406, January 1993.		Interface Types", RFC 1406, January 1993.
	[RFC2495]		[RFC2495]
	Fowler D., "Definitions of Managed Objects for the DS1, E1, DS2 and		Fowler D., "Definitions of Managed Objects for the DS1, E1, DS2 and
	and E2 Interface Types", RFC 2495, january 1999.		and E2 Interface Types", RFC 2495, january 1999.
	***********************************************************		***********************************************************
	* NOTE TO RFC Editor (to be removed prior to publication):*		* NOTE TO RFC Editor (to be removed prior to publication):*
	* If <draft-ietf-atommib-rfc2495bis-05.txt> (or its *		* If <draft-ietf-atommib-rfc2495bis-06.txt> (or its *
	* successor) is to be published as an RFC concurrently *		* successor) is to be published as an RFC concurrently *
	* with this document, please update this reference to *		* with this document, please update this reference to *
	* point to that RFC, instead of RFC 2495, and change *		* point to that RFC, instead of RFC 2495, and change *
	* the reference tag [RFC2495] to match. *		* the reference tag [RFC2495] to match. *
	***********************************************************		***********************************************************
	[RFC3592]		[RFC3592]
	Brown, T., and Tesink, K., "Definitions of Managed Objects for the		Brown, T., and Tesink, K., "Definitions of Managed Objects for the
	SONET/SDH Interface Type", RFC 3592, September 2003.		SONET/SDH Interface Type", RFC 3592, September 2003.
	skipping to change at page 69, line 9 ¶		skipping to change at page 72, line 9 ¶
	Tel Aviv, Israel, 69719		Tel Aviv, Israel, 69719
	Phone: 9723-765-9969		Phone: 9723-765-9969
	e-Mail: orly_n@rad.com		e-Mail: orly_n@rad.com
	Table of Contents		Table of Contents
	1 The Internet Standard Management Framework ................... 2		1 The Internet Standard Management Framework ................... 2
	1.1 Changes from RFC2496 ....................................... 2		1.1 Changes from RFC2496 ....................................... 2
	2 Overview ..................................................... 3		1.2 Changes from RFC1407 ....................................... 2
	2.1 Use of ifTable for DS3 Layer ............................... 3		2 Overview ..................................................... 4
	2.2 Usage Guidelines ........................................... 4		2.1 Use of ifTable for DS3 Layer ............................... 4
	2.2.1 Usage of ifStackTable .................................... 4		2.2 Usage Guidelines ........................................... 5
	2.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 6		2.2.1 Usage of ifStackTable .................................... 5
	2.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 7		2.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 7
	2.2.4 Usage of Loopbacks ....................................... 8		2.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 8
	2.3 Objectives of this MIB Module .............................. 9		2.2.4 Usage of Loopbacks ....................................... 9
	2.4 DS3/E3 Terminology ......................................... 9		2.3 Objectives of this MIB Module .............................. 10
	2.4.1 Error Events ............................................. 9		2.4 DS3/E3 Terminology ......................................... 10
	2.4.2 Performance Parameters ................................... 10		2.4.1 Error Events ............................................. 10
	2.4.3 Performance Defects ...................................... 13		2.4.2 Performance Parameters ................................... 11
	2.4.4 Other Terms .............................................. 15		2.4.3 Performance Defects ...................................... 14
	3 Object Definitions ........................................... 16		2.4.4 Other Terms .............................................. 16
	4.1 The DS3/E3 Near End Group .................................. 18		3 Object Definitions ........................................... 17
	4.1.1 The DS3/E3 Configuration Table ........................... 18		4.1 The DS3/E3 Near End Group .................................. 20
	4.1.2 The DS3/E3 Current Table ................................. 28		4.1.1 The DS3/E3 Configuration Table ........................... 20
	4.1.3 The DS3/E3 Interval Table ................................ 32		4.1.2 The DS3/E3 Current Table ................................. 30
	4.1.4 The DS3/E3 Total ......................................... 36		4.1.3 The DS3/E3 Interval Table ................................ 34
	4.2 The DS3 Far End Group ...................................... 40		4.1.4 The DS3/E3 Total ......................................... 38
	4.2.1 The DS3 Far End Configuration ............................ 40		4.2 The DS3 Far End Group ...................................... 42
	4.2.2 The DS3 Far End Current .................................. 42		4.2.1 The DS3 Far End Configuration ............................ 42
	4.2.3 The DS3 Far End Interval Table ........................... 45		4.2.2 The DS3 Far End Current .................................. 44
	4.2.4 The DS3 Far End Total .................................... 47		4.2.3 The DS3 Far End Interval Table ........................... 47
	4.3 The DS3/E3 Fractional Table ................................ 50		4.2.4 The DS3 Far End Total .................................... 49
	4.4 The DS3 Trap Group ......................................... 53		4.3 The DS3/E3 Fractional Table ................................ 52
	4.5 Conformance Groups ......................................... 53		4.4 The DS3 Trap Group ......................................... 55
	4 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 58		4.5 Conformance Groups ......................................... 56
	5 Appendix B - The delay approach to Unavialable Seconds. ..... 60		4 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 60
	6 Intellectual Property ........................................ 62		5 Appendix B - The delay approach to Unavialable Seconds. ..... 63
	7 Full Copyright Statement ..................................... 62		6 Intellectual Property ........................................ 64
	8 Acknowledgments .............................................. 63		7 Full Copyright Statement ..................................... 65
	9 References ................................................... 64		8 Acknowledgments .............................................. 66
	9.1 Normative References ....................................... 64		9 References ................................................... 67
	9.2 Informative References ..................................... 65		9.1 Normative References ....................................... 67
	10 Security Considerations ..................................... 67		9.2 Informative References ..................................... 68
	11 Author's Address ............................................ 68		10 Security Considerations ..................................... 70
			11 Author's Address ............................................ 71
End of changes. 22 change blocks.
	27 lines changed or deleted		139 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/