< draft-ietf-adslmib-hc-tc-06.txt		draft-ietf-adslmib-hc-tc-07.txt >
	Network Working Group B. Ray		Network Working Group B. Ray
	Category: Internet Draft PESA Switching Systems		Category: Internet Draft PESA Switching Systems
	R. Abbi		R. Abbi
	Alcatel		Alcatel
	September 2003		November 2003
	High Capacity Textual Conventions for MIB Modules Using		High Capacity Textual Conventions for MIB Modules Using
	Performance History Based on 15 Minute Intervals		Performance History Based on 15 Minute Intervals
	draft-ietf-adslmib-hc-tc-06.txt		draft-ietf-adslmib-hc-tc-07.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.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as		other groups may also distribute working documents as
	Internet-Drafts.		Internet-Drafts.
	skipping to change at page 3, line 6 ¶		skipping to change at page 3, line 6 ¶
	Telecommunications equipment often makes use of the latter strategy.		Telecommunications equipment often makes use of the latter strategy.
	For such equipment the standard practice is that history data is		For such equipment the standard practice is that history data is
	maintained by the agent in terms of 15-minute intervals [T1.231].		maintained by the agent in terms of 15-minute intervals [T1.231].
	MIB modules for collecting performance history based on 15-minute		MIB modules for collecting performance history based on 15-minute
	intervals have been defined for the DS1/E1 [RFC2495], DS3/E3		intervals have been defined for the DS1/E1 [RFC2495], DS3/E3
	[RFC2496], SONET/SDH [RFC3592], ADSL [RFC2662], HDLS2 and SHDSL		[RFC2496], SONET/SDH [RFC3592], ADSL [RFC2662], HDLS2 and SHDSL
	[RFC3276] interface types. These MIB modules use a common set of		[RFC3276] interface types. These MIB modules use a common set of
	textual conventions defined in [RFC3593]. Those textual		textual conventions defined in [RFC3593].
	conventions are based on the Gauge32 data type.
	A need has arisen to define 64-bit versions of the textual		A need has arisen to define 64-bit versions of the textual
	conventions in [RFC3593]. Ideally, these high-capacity textual		conventions in [RFC3593]. Ideally, these high-capacity textual
	conventions would be based on a Gauge64 or Unsigned64 data type, but		conventions would be based on a Gauge64 or Unsigned64 data type, but
	unfortunately no such types exist in SMIv2. The next best choice		unfortunately no such types exist in SMIv2. The next best choice
	would be to base them on the CounterBasedGauge64 textual convention		would be to base them on the CounterBasedGauge64 textual convention
	presented in [RFC2856], but that is not possible either since SMIv2		presented in [RFC2856], but that is not possible either since SMIv2
	allows only base types to be used in defining textual conventions.		allows only base types to be used in defining textual conventions.
	Therefore, the textual conventions presented in this memo are based		Therefore, the textual conventions presented in this memo are based
	directly on the Counter64 type, like those in [RFC2856]. They are		directly on the Counter64 type, like those in [RFC2856]. They are
	skipping to change at page 4, line 4 ¶		skipping to change at page 4, line 4 ¶
	history intervals, and the total aggregates.		history intervals, and the total aggregates.
	3. Definitions		3. Definitions
	HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN		HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY,		MODULE-IDENTITY,
	Counter64,		Counter64,
	Unsigned32,		Unsigned32,
	Gauge32,
	mib-2 FROM SNMPv2-SMI		mib-2 FROM SNMPv2-SMI
	TEXTUAL-CONVENTION FROM SNMPv2-TC;		TEXTUAL-CONVENTION FROM SNMPv2-TC;
	hcPerfHistTCMIB MODULE-IDENTITY		hcPerfHistTCMIB MODULE-IDENTITY
	LAST-UPDATED "200309240000Z" -- September 24, 2003		LAST-UPDATED "200311240000Z" -- November 24, 2003
	ORGANIZATION "ADSLMIB Working Group"		ORGANIZATION "ADSLMIB Working Group"
	CONTACT-INFO "WG-email: adslmib@ietf.org		CONTACT-INFO "WG-email: adslmib@ietf.org
	Info: https://www1.ietf.org/mailman/listinfo/adslmib		Info: https://www1.ietf.org/mailman/listinfo/adslmib
	Chair: Mike Sneed		Chair: Mike Sneed
	Sand Channel Systems		Sand Channel Systems
	Postal: P.O. Box 37324		Postal: P.O. Box 37324
	Raleigh NC 27627-7324		Raleigh NC 27627-7324
	USA		USA
	Email: sneedmike@hotmail.com		Email: sneedmike@hotmail.com
	skipping to change at page 4, line 47 ¶		skipping to change at page 4, line 46 ¶
	"		"
	DESCRIPTION		DESCRIPTION
	"This MIB Module provides Textual Conventions to be		"This MIB Module provides Textual Conventions to be
	used by systems supporting 15 minute based performance		used by systems supporting 15 minute based performance
	history counts that require high-capacity counts.		history counts that require high-capacity counts.
	Copyright (C) The Internet Society (2003). This version		Copyright (C) The Internet Society (2003). This version
	of this MIB module is part of RFC XXXX: see the RFC		of this MIB module is part of RFC XXXX: see the RFC
	itself for full legal notices."		itself for full legal notices."
	-- RFC Ed.: replace XXXX with assigned number & remove this note		-- RFC Ed.: replace XXXX with assigned number & remove this note
	REVISION "200309240000Z" -- September 24, 2003		REVISION "200311240000Z" -- November 24, 2003
	DESCRIPTION "Initial version, published as RFC XXXX."		DESCRIPTION "Initial version, published as RFC XXXX."
	-- RFC Ed.: replace XXXX with assigned number & remove this note		-- RFC Ed.: replace XXXX with assigned number & remove this note
	::= { mib-2 YYYY }		::= { mib-2 YYYY }
	-- RFC Ed.: replace YYYY with IANA-assigned number & remove this note		-- RFC Ed.: replace YYYY with IANA-assigned number & remove this note
	HCPerfValidIntervals ::= TEXTUAL-CONVENTION		HCPerfValidIntervals ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of near end intervals for which data was		"The number of near end intervals for which data was
	collected. The value of an object with an		collected. The value of an object with an
	HCPerfValidIntervals syntax will be 96 unless the		HCPerfValidIntervals syntax will be 96 unless the
	measurement was (re-)started within the last 1440 minutes,		measurement was (re-)started within the last 1440 minutes,
	in which case the value will be the number of complete 15		in which case the value will be the number of complete 15
	minute intervals for which the agent has at least some data.		minute intervals for which the agent has at least some data.
	In certain cases (e.g., in the case where the agent is a		In certain cases (e.g., in the case where the agent is a
	proxy) it is possible that some intervals are unavailable.		proxy) it is possible that some intervals are unavailable.
	In this case, this interval is the maximum interval number		In this case, this interval is the maximum interval number
	for which data is available."		for which data is available."
	SYNTAX Gauge32 (0..96)		SYNTAX Integer32 (0..96)
	HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION		HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of near end intervals for which no data is		"The number of near end intervals for which no data is
	available. The value of an object with an		available. The value of an object with an
	HCPerfInvalidIntervals syntax will typically be zero except		HCPerfInvalidIntervals syntax will typically be zero except
	in cases where the data for some intervals are not available		in cases where the data for some intervals are not available
	(e.g., in proxy situations)."		(e.g., in proxy situations)."
	SYNTAX Gauge32 (0..96)		SYNTAX Integer32 (0..96)
	HCPerfTimeElapsed ::= TEXTUAL-CONVENTION		HCPerfTimeElapsed ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of seconds that have elapsed since the beginning		"The number of seconds that have elapsed since the beginning
	of the current measurement period. If, for some reason,		of the current measurement period. If, for some reason,
	such as an adjustment in the system's time-of-day clock or		such as an adjustment in the system's time-of-day clock or
	the addition of a leap second, the duration of the current		the addition of a leap second, the duration of the current
	interval exceeds the maximum value, the agent will return		interval exceeds the maximum value, the agent will return
	the maximum value.		the maximum value.
	For 15 minute intervals, the range is limited to (0..899).		For 15 minute intervals, the range is limited to (0..899).
	For 24 hour intervals, the range is limited to (0..86399)."		For 24 hour intervals, the range is limited to (0..86399)."
	SYNTAX Gauge32 (0..86399)		SYNTAX Integer32 (0..86399)
	HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION		HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This convention defines a range of values that may be set		"This convention defines a range of values that may be set
	in a fault threshold alarm control. As the number of		in a fault threshold alarm control. As the number of
	seconds in a 15-minute interval numbers at most 900,		seconds in a 15-minute interval numbers at most 900,
	objects of this type may have a range of 0...900, where the		objects of this type may have a range of 0...900, where the
	value of 0 disables the alarm."		value of 0 disables the alarm."
	SYNTAX Unsigned32 (0..900)		SYNTAX Unsigned32 (0..900)
	skipping to change at page 9, line 18 ¶		skipping to change at page 9, line 18 ¶
	[RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1,		[RFC2495] Fowler, D., "Definitions of Managed Objects for the DS1,
	E1, DS2 and E2 Interface Types", RFC 2495, January 1999.		E1, DS2 and E2 Interface Types", RFC 2495, January 1999.
	[RFC2496] Fowler, D., "Definitions of Managed Objects for the		[RFC2496] Fowler, D., "Definitions of Managed Objects for the
	DS3/E3 Interface Type", RFC 2496, January 1999.		DS3/E3 Interface Type", RFC 2496, January 1999.
	[RFC3592] Tesink, K., "Definitions of Managed Objects for the		[RFC3592] Tesink, K., "Definitions of Managed Objects for the
	Synchronous Optical Network/Synchronous Digital		Synchronous Optical Network/Synchronous Digital
	Hierachy (SONET/SDH) Interface Type", RFC 3592,		Hierachy (SONET/SDH) Interface Type", RFC 3592,
	September 2003.		November 2003.
	[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects		[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
	for the ADSL Lines", RFC 2662, August 1999.		for the ADSL Lines", RFC 2662, August 1999.
	[RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual		[RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual
	Conventions for Additional High Capacity Data Types",		Conventions for Additional High Capacity Data Types",
	RFC2856, June 2000.		RFC2856, June 2000.
	[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects		[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects
	for High Bit-rate DSL - 2nd Generation (HDSL2) and		for High Bit-rate DSL - 2nd Generation (HDSL2) and
	Single-Pair High-Speed Digital Subscriber Line (SHDSL)		Single-Pair High-Speed Digital Subscriber Line (SHDSL)
	Lines", RFC3276, May 2002.		Lines", RFC3276, May 2002.
	[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using		[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
	Performance History Based on 15 Minute Intervals", RFC		Performance History Based on 15 Minute Intervals", RFC
	3593, September 2003.		3593, November 2003.
	7. Security Considerations		7. Security Considerations
	This module does not define any management objects. Instead, it		This module does not define any management objects. Instead, it
	defines a set of textual conventions which may be used by other		defines a set of textual conventions which may be used by other
	MIB modules to define management objects.		MIB modules to define management objects.
	Meaningful security considerations can only be written in the MIB		Meaningful security considerations can only be written in the MIB
	modules that define management objects. This document has		modules that define management objects. This document has
	therefore no impact on the security of the Internet.		therefore no impact on the security of the Internet.
End of changes. 12 change blocks.
	12 lines changed or deleted		11 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/