draft-ietf-ippm-metrics-registry-03.txt		draft-ietf-ippm-metrics-registry-04.txt
	Network Working Group E. Stephan		Network Working Group E. Stephan
	Internet Draft France Telecom R&D		Internet Draft France Telecom R&D
	Document: draft-ietf-ippm-metrics-registry-03.txt April 2003		Document: draft-ietf-ippm-metrics-registry-04.txt April 2003
	Category: Standards Track		Category: Standards Track
	IPPM metrics registry		IPPM metrics registry
	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 RFC 2026 [RFC2026].		all provisions of Section 10 of RFC 2026 [RFC2026].
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	Abstract		Abstract
	This memo defines a registry of the IPPM working group metrics. It		This memo defines a registry of the IPPM working group metrics. It
	assigns an OBJECT IDENTIFIER to each metric currently standardized by		assigns an OBJECT IDENTIFIER to each metric currently standardized by
	the IPPM WG. It defines the rules for the identification of the		the IPPM WG. It defines the rules for the identification of the
	metrics standardized in the future.		metrics standardized in the future.
	Table of Contents		Table of Contents
	1. The Internet-Standard Management Framework..................2		1. The Internet-Standard Management Framework...................2
	2. Terms.......................................................2		2. Terms........................................................2
	3. Overview....................................................2		3. Overview.....................................................2
	4. The IPPM Framework..........................................2		4. The IPPM Framework...........................................2
	5. Overview....................................................3		5. Overview.....................................................3
	6. IPPM metrics Registry framework.............................3		6. IPPM metrics Registry framework..............................3
	6.1. Metrics registry template...................................4		6.1. Metrics registry template....................................4
	6.2. Initial IPPM metrics registry creation......................5		6.2. Initial IPPM metrics registry creation.......................5
	6.3. Future IPPM metrics registration............................6		6.3. Future IPPM metrics registration.............................6
	6.4. Metric defined in cooperation with other bodies.............6		6.4. Metric defined in cooperation with other bodies..............6
	7. Initial IPPM registry definition............................6		7. Initial IPPM registry definition.............................6
	8. Intellectual Property......................................13		8. Intellectual Property.......................................13
	9. Acknowledgments............................................13		9. Acknowledgments.............................................13
	10. Normative References.......................................13		10. Normative References........................................13
	11. Informative References.....................................14		11. Informative References......................................14
	12. Security Considerations....................................14		12. Security Considerations.....................................14
	13. Author's Addresses.........................................15		13. Author's Addresses..........................................15
	14. Full Copyright Statement...................................15		14. Full Copyright Statement....................................15
	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]. Managed objects are accessed via a virtual		RFC 3410 [RFC3410]. Managed objects are accessed via a virtual
	information store, termed the Management Information Base or MIB.		information store, termed the Management Information Base or MIB.
	MIB objects are generally accessed through the Simple Network		MIB objects are generally accessed through the Simple Network
	Management Protocol (SNMP). Objects in the MIB are defined using the		Management Protocol (SNMP). Objects in the MIB are defined using the
	mechanisms defined in the Structure of Management Information (SMI).		mechanisms defined in the Structure of Management Information (SMI).
	skipping to change at page 2, line 42		skipping to change at page 2, line 42
	This memo defines a registry of the IPPM working group metrics. It		This memo defines a registry of the IPPM working group metrics. It
	assigns an OBJECT IDENTIFIER to each metric currently standardized by		assigns an OBJECT IDENTIFIER to each metric currently standardized by
	the IPPM WG. It defines the rules for the identification of the		the IPPM WG. It defines the rules for the identification of the
	metrics standardized in the future.		metrics standardized in the future.
	4. The IPPM Framework		4. The IPPM Framework
	The IPPM Framework consists in four major components:		The IPPM Framework consists in four major components:
	+ A general framework for defining performance metrics,		+ A general framework for defining performance metrics
	described in the Framework for IP Performance Metrics RFC2330		described in the Framework for IP Performance Metrics RFC2330
	[RFC 2330];		[RFC 2330];
	+ A set of standardized metrics, which conform to this		+ A set of standardized metrics, which conform to this
	framework.		framework.
	+ Emerging metrics which are being specified in respect of this		+ Emerging metrics which are being specified in respect of this
	framework;		framework;
	+ The IPPM-REPORTING-MIB for reporting the results of the		+ The IPPM-REPORTING-MIB for reporting the results of the
	measures and for interfacing heterogeneous measurement systems		measures and for interfacing heterogeneous measurement systems
	with management entities.		with management entities.
	5. Overview		5. Overview
	This memo defines a registry of the current metrics and a framework		This memo defines a registry of the current metrics and a framework
	for the integration of future metrics for the following reasons:		for the integration of future metrics for the following reasons:
	+ to permit metrics to be clearly referenced by MIBs or other		+ to permit metrics to be clearly referenced by MIBs or other data
	data models;		models;
	+ Metrics identifiers are needed to allow measurement		+ Metrics identifiers are needed to allow measurement
	interoperability;		interoperability;
	+ As specification of new metrics is a continuous process,		+ As specification of new metrics is a continuous process, special
	special care must be taken for the integration of future		care must be taken for the integration of future standardized
	standardized metrics;		metrics;
	+ As the intent of the IPPM WG is to cooperate with other		+ As the intent of the IPPM WG is to cooperate with other
	appropriate standards bodies and other areas of IETF to promote		appropriate standards bodies and other areas of IETF to promote
	consistent metrics, there is a need to permit registration of		consistent metrics, there is a need to permit registration of
	such metrics.		such metrics.
	6. IPPM metrics Registry framework		6. IPPM metrics Registry framework
	MIBs need OBJECT INDENTIFIERs to refer precisely to the standardized		MIBs need OBJECT INDENTIFIERs to refer precisely to the standardized
	metrics. The registry associates an OBJECT IDENTIFIER with each		metrics. The registry associates an OBJECT IDENTIFIER with each
	skipping to change at page 5, line 11		skipping to change at page 5, line 11
	Tel:		Tel:
	E-mail:		E-mail:
	Postal:		Postal:
	Send comments to <ippm@ietf.org>		Send comments to <ippm@ietf.org>
	Mailing list subscription info:		Mailing list subscription info:
	https://www1.ietf.org/mailman/listinfo/ippm "		https://www1.ietf.org/mailman/listinfo/ippm "
	DESCRIPTION		DESCRIPTION
	" This memo defines the registry for IPPM Packet Speed metrics.		" This memo defines the registry for IPPM Packet Speed metrics.
	Copyright (C) The Internet Society (2002).		Copyright (C) The Internet Society (2003).
	This version of this MIB module is part of RFC yyyy; see the		This version of this MIB module is part of RFC yyyy; see the
	RFC itself for full legal notices."		RFC itself for full legal notices."
	REVISION "YYYYMMDD0000Z"		REVISION "YYYYMMDD0000Z"
	DESCRIPTION		DESCRIPTION
	"Initial version of the module of the registry for IPPM Packet		"Initial version of the module of the registry for IPPM Packet
	Speed metrics.		Speed metrics.
	This version published as RFC yyyy."		This version published as RFC yyyy."
	::= { mib-2 N }		::= { mib-2 N }
	skipping to change at page 6, line 25		skipping to change at page 6, line 25
	+ IPPM Metrics for periodic streams, RFC 3432 [RFC3432];		+ IPPM Metrics for periodic streams, RFC 3432 [RFC3432];
	They are registered in the node rfc(1). They are numbered using the RFC		They are registered in the node rfc(1). They are numbered using the RFC
	order and the metrics definitions order in each memo. The node assigned		order and the metrics definitions order in each memo. The node assigned
	to a metric is definitive and cannot be reused.		to a metric is definitive and cannot be reused.
	6.3. Future IPPM metrics registration		6.3. Future IPPM metrics registration
	When the IPPM WG draft is considered mature enough:		When the IPPM WG draft is considered mature enough:
	+ The chair of the IPPM WG, or someone proposed by the directors of		+ The chair of the IPPM WG, or someone proposed by the directors
	the Transport Area, assigns to each metric a sub node chosen in the		of the Transport Area, assigns to each metric a sub node chosen
	tree rfc(1) of the IPPM-METRICS-REGISTRY;		in the tree rfc(1) of the IPPM-METRICS-REGISTRY;
	+ Authors insert a registry template in their document. Then they		+ Authors insert a registry template in their document. Then they
	create an OBJECT-IDENTITY instance per metric and complete the		create an OBJECT-IDENTITY instance per metric and complete the
	instance with the assigned sub nodes.		instance with the assigned sub nodes.
	That helps to prepare the final version of the draft. Moreover it		That helps to prepare the final version of the draft. Moreover it
	facilitates software integration and interoperability measurement		facilitates software integration and interoperability measurement
	during the specification process.		during the specification process.
	6.4. Metric defined in cooperation with other bodies		6.4. Metric defined in cooperation with other bodies
	skipping to change at page 6, line 53		skipping to change at page 6, line 53
	7. Initial IPPM registry definition		7. Initial IPPM registry definition
	IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN		IPPM-METRICS-REGISTRY DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	OBJECT-IDENTITY, MODULE-IDENTITY, mib-2		OBJECT-IDENTITY, MODULE-IDENTITY, mib-2
	FROM SNMPv2-SMI;		FROM SNMPv2-SMI;
	ippmMetricsRegistry MODULE-IDENTITY		ippmMetricsRegistry MODULE-IDENTITY
	LAST-UPDATED "200304160000Z" -- April 16th, 2003		LAST-UPDATED "200304170000Z" -- April 17th, 2003
	ORGANIZATION "IETF IPPM working Group"		ORGANIZATION "IETF IPPM working Group"
	CONTACT-INFO "		CONTACT-INFO "
	Emile STEPHAN		Emile STEPHAN
	France Telecom R & D		France Telecom R & D
	Tel: +1 33 2 96 05 36 10		Tel: +1 33 2 96 05 36 10
	E-mail: emile.stephan@francetelecom.com		E-mail: emile.stephan@francetelecom.com
	Postal: 2, avenue Pierre Marzin		Postal: 2, avenue Pierre Marzin
	Lannion, FRANCE 22307		Lannion, FRANCE 22307
	Send comments to <ippm@ietf.org>		Send comments to <ippm@ietf.org>
	Mailing list subscription info:		Mailing list subscription info:
	https://www1.ietf.org/mailman/listinfo/ippm "		https://www1.ietf.org/mailman/listinfo/ippm "
	DESCRIPTION		DESCRIPTION
	"This memo defines a registry of the IPPM working group		"This memo defines a registry of the IPPM working group
	metrics.		metrics.
	Copyright (C) The Internet Society (2002). This version of this		Copyright (C) The Internet Society (2003). This version of this
	MIB module is part of RFC yyyy; see the RFC itself for full		MIB module is part of RFC yyyy; see the RFC itself for full
	legal notices."		legal notices."
	REVISION "200304160000Z" -- April 16th, 2003		REVISION "200304170000Z" -- April 17th, 2003
	DESCRIPTION		DESCRIPTION
	"Initial version of the IPPM metrics registry module.		"Initial version of the IPPM metrics registry module.
	This version published as RFC yyyy."		This version published as RFC yyyy."
	::= { mib-2 XXX }		::= { mib-2 XXX }
	rfc OBJECT IDENTIFIER ::= { ippmMetricsRegistry 1 }		rfc OBJECT IDENTIFIER ::= { ippmMetricsRegistry 1 }
	otherBodies OBJECT IDENTIFIER ::= { ippmMetricsRegistry 2 }		otherBodies OBJECT IDENTIFIER ::= { ippmMetricsRegistry 2 }
	--		--
	-- Registry of the metrics of the IPPM WG RFCs		-- Registry of the metrics of the IPPM WG RFCs
	skipping to change at page 12, line 5		skipping to change at page 12, line 5
	oneWayInterLossPeriodLengths OBJECT-IDENTITY		oneWayInterLossPeriodLengths OBJECT-IDENTITY
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The identifier for the Type-P-One-Way-Inter-Loss-Period-		"The identifier for the Type-P-One-Way-Inter-Loss-Period-
	Lengths metric."		Lengths metric."
	REFERENCE " RFC3357, section 6.4."		REFERENCE " RFC3357, section 6.4."
	::= { rfc 26 }		::= { rfc 26 }
	--		--
			-- RFC3393:
			-- "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)"
	oneWayIpdv OBJECT-IDENTITY		oneWayIpdv OBJECT-IDENTITY
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The identifier for the Type-P-One-way-ipdv metric."		"The identifier for the Type-P-One-way-ipdv metric."
	REFERENCE " RFC3393, section 2."		REFERENCE " RFC3393, section 2."
	::= { rfc 27 }		::= { rfc 27 }
	oneWayIpdvPoissonStream OBJECT-IDENTITY		oneWayIpdvPoissonStream OBJECT-IDENTITY
	STATUS current		STATUS current
	skipping to change at page 15, line 18		skipping to change at page 15, line 18
	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 then 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.
	13. Author's Addresses		13. Author's Address
	Emile STEPHAN		Emile STEPHAN
	France Telecom R & D		France Telecom R & D
	2, avenue Pierre Marzin		2, avenue Pierre Marzin
	F-22307 Lannion cedex		F-22307 Lannion cedex
	Phone: (+ 33) 2 96 05 36 10		Phone: (+ 33) 2 96 05 36 10
	Email: emile.stephan@francetelecom.com		Email: emile.stephan@francetelecom.com
	14. Full Copyright Statement		14. Full Copyright Statement
	"Copyright (C) The Internet Society (2003). 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 its implementation may be prepared, copied, published and		or assist its implementation may be prepared, copied, published and
	distributed, in whole or in part, without restriction of any kind,		distributed, in whole or in part, without restriction of any kind,
	provided that the above copyright notice and this paragraph are		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
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/