< draft-ietf-ippm-metric-registry-10.txt		draft-ietf-ippm-metric-registry-11.txt >
	Network Working Group M. Bagnulo		Network Working Group M. Bagnulo
	Internet-Draft UC3M		Internet-Draft UC3M
	Intended status: Best Current Practice B. Claise		Intended status: Best Current Practice B. Claise
	Expires: June 3, 2017 Cisco Systems, Inc.		Expires: September 10, 2017 Cisco Systems, Inc.
	P. Eardley		P. Eardley
	BT		BT
	A. Morton		A. Morton
	AT&T Labs		AT&T Labs
	A. Akhter		A. Akhter
	Consultant		Consultant
	November 30, 2016		March 9, 2017
	Registry for Performance Metrics		Registry for Performance Metrics
	draft-ietf-ippm-metric-registry-10		draft-ietf-ippm-metric-registry-11
	Abstract		Abstract
	This document defines the format for the Performance Metrics registry		This document defines the format for the Performance Metrics registry
	and defines the IANA Registry for Performance Metrics. This document		and defines the IANA Registry for Performance Metrics. This document
	also gives a set of guidelines for Registered Performance Metric		also gives a set of guidelines for Registered Performance Metric
	requesters and reviewers.		requesters and reviewers.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on June 3, 2017.		This Internet-Draft will expire on September 10, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 13 ¶		skipping to change at page 3, line 13 ¶
	7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23		7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23
	7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 23		7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 23
	8. The Life-Cycle of Registered Performance Metrics . . . . . . 23		8. The Life-Cycle of Registered Performance Metrics . . . . . . 23
	8.1. Adding new Performance Metrics to the Performance Metrics		8.1. Adding new Performance Metrics to the Performance Metrics
	Registry . . . . . . . . . . . . . . . . . . . . . . . . 23		Registry . . . . . . . . . . . . . . . . . . . . . . . . 23
	8.2. Revising Registered Performance Metrics . . . . . . . . . 24		8.2. Revising Registered Performance Metrics . . . . . . . . . 24
	8.3. Deprecating Registered Performance Metrics . . . . . . . 25		8.3. Deprecating Registered Performance Metrics . . . . . . . 25
	9. Security considerations . . . . . . . . . . . . . . . . . . . 26		9. Security considerations . . . . . . . . . . . . . . . . . . . 26
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28		10.1. New Namespace Assignments . . . . . . . . . . . . . . . 26
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28		10.2. Performance Metric Name Elements . . . . . . . . . . . . 27
	12.1. Normative References . . . . . . . . . . . . . . . . . . 28		10.3. New Performance Metrics Registry . . . . . . . . . . . . 28
	12.2. Informative References . . . . . . . . . . . . . . . . . 29		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
			12.1. Normative References . . . . . . . . . . . . . . . . . . 29
			12.2. Informative References . . . . . . . . . . . . . . . . . 30
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
	1. Introduction		1. Introduction
	The IETF specifies and uses Performance Metrics of protocols and		The IETF specifies and uses Performance Metrics of protocols and
	applications transported over its protocols. Performance metrics are		applications transported over its protocols. Performance metrics are
	such an important part of the operations of IETF protocols that		such an important part of the operations of IETF protocols that
	[RFC6390] specifies guidelines for their development.		[RFC6390] specifies guidelines for their development.
	The definition and use of Performance Metrics in the IETF happens in		The definition and use of Performance Metrics in the IETF happens in
	various working groups (WG), most notably:		various working groups (WG), most notably:
	skipping to change at page 14, line 47 ¶		skipping to change at page 14, line 47 ¶
	StandingQueue (test of bottleneck queue behavior)		StandingQueue (test of bottleneck queue behavior)
	@@@@<add others from MBM draft?>		@@@@<add others from MBM draft?>
	SubTypeMethod values are separated by a hyphen "-" character,		SubTypeMethod values are separated by a hyphen "-" character,
	which indicates that they belong to this element, and that their		which indicates that they belong to this element, and that their
	order is unimportant when considering name uniqueness.		order is unimportant when considering name uniqueness.
	o Spec: RFC that specifies this entry in the form RFCXXXXsecY, such		o Spec: RFC that specifies this entry in the form RFCXXXXsecY, such
	as RFC7799sec3. Note: this is not the Primary Reference		as RFC7799sec3. Note: this is not the Primary Reference
	specification for the metric; it will be blank until the RFC		specification for the metric definition; it will contain the
	number is assigned, and would remain blank in private registry		placeholder "RFCXXXXsecY" until the RFC number is assigned to the
	entries without an RFC.		specifying document, and would remain blank in private registry
			entries without a corresponding RFC.
	o Units: The units of measurement for the output, such as:		o Units: The units of measurement for the output, such as:
	Seconds		Seconds
	RatioPercent (value multiplied by 100)		RatioPercent (value multiplied by 100)
	BPS (Bits per Second)		BPS (Bits per Second)
	EventTotal (for unit-less counts)		EventTotal (for unit-less counts)
	Multiple (more than one type of unit)		Multiple (more than one type of unit)
	Enumerated (a list of outcomes)		Enumerated (a list of outcomes)
	Unit-less		Unitless
	o Output: The type of output resulting from measurement, such as:		o Output: The type of output resulting from measurement, such as:
	Singleton (sometimes called raw data)		Singleton (sometimes called raw data)
	Minimum		Minimum
	Maximum		Maximum
	Median		Median
	skipping to change at page 16, line 4 ¶		skipping to change at page 16, line 5 ¶
	An example is:		An example is:
	RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile		RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile
	as described in section 4 of [I-D.ietf-ippm-initial-registry].		as described in section 4 of [I-D.ietf-ippm-initial-registry].
	Note that private registries following the format described here		Note that private registries following the format described here
	SHOULD use the prefix "Priv_" on any name to avoid unintended		SHOULD use the prefix "Priv_" on any name to avoid unintended
	conflicts (further considerations are described in section 10).		conflicts (further considerations are described in section 10).
	Private registry entries usually have no specifying RFC, thus the		Private registry entries usually have no specifying RFC, thus the
	Spec: element has no clear interpretation.		Spec: element has no clear interpretation.
	7.1.3. URIs		7.1.3. URIs
	The URIs column MUST contain a URI [RFC3986] that uniquely identifies		The URIs column MUST contain a URI [RFC3986] that uniquely identifies
	the metric. This URI is a URN [RFC2141]. The URI is automatically		the metric. This URI is a URN [RFC2141]. The URI is automatically
	generated by prepending the prefix		generated by prepending the prefix
	urn:ietf:metric:perf:		urn:ietf:metrics:perf:
	to the metric name. The resulting URI is globally unique.		to the metric name. The resulting URI is globally unique.
	The URIs column MUST contain a second URI which is a URL [RFC3986]		The URIs column MUST contain a second URI which is a URL [RFC3986]
	and uniquely identifies and locates the metric entry so it is		and uniquely identifies and locates the metric entry so it is
	accessible through the Internet. The URL points to a file containing		accessible through the Internet. The URL points to a file containing
	the human-readable information of exactly one registry entry.		the human-readable information of exactly one registry entry.
	Ideally, the file will be HTML-formated and contain URLs to		Ideally, the file will be HTML-formated and contain URLs to
	referenced sections of HTML-ized RFCs. The separate files for		referenced sections of HTML-ized RFCs. The separate files for
	different entries can be more easily edited and re-used when		different entries can be more easily edited and re-used when
	preparing new entries. The exact composition of each metric URL will		preparing new entries. The exact composition of each metric URL will
	be determined by IANA and reside on "iana.org", but there will be		be determined by IANA and reside on "iana.org", but there will be
	some overlap with the URN described above. The major sections of		some overlap with the URN described above. The major sections of
	[I-D.ietf-ippm-initial-registry] provide an example in HTML form		[I-D.ietf-ippm-initial-registry] provide an example in HTML form
	(sections 4 and above).		(sections 4 and higher).
	7.1.4. Description		7.1.4. Description
	A Registered Performance Metric description is a written		A Registered Performance Metric description is a written
	representation of a particular Performance Metrics Registry entry.		representation of a particular Performance Metrics Registry entry.
	It supplements the Registered Performance Metric name to help		It supplements the Registered Performance Metric name to help
	Performance Metrics Registry users select relevant Registered		Performance Metrics Registry users select relevant Registered
	Performance Metrics.		Performance Metrics.
	7.1.5. Reference		7.1.5. Reference
	skipping to change at page 17, line 36 ¶		skipping to change at page 17, line 36 ¶
	specification.		specification.
	7.2.2. Fixed Parameters		7.2.2. Fixed Parameters
	Fixed Parameters are Parameters whose value must be specified in the		Fixed Parameters are Parameters whose value must be specified in the
	Performance Metrics Registry. The measurement system uses these		Performance Metrics Registry. The measurement system uses these
	values.		values.
	Where referenced metrics supply a list of Parameters as part of their		Where referenced metrics supply a list of Parameters as part of their
	descriptive template, a sub-set of the Parameters will be designated		descriptive template, a sub-set of the Parameters will be designated
	as Fixed Parameters. For example, for active metrics, Fixed		as Fixed Parameters. As an example for active metrics, Fixed
	Parameters determine most or all of the IPPM Framework convention		Parameters determine most or all of the IPPM Framework convention
	"packets of Type-P" as described in [RFC2330], such as transport		"packets of Type-P" as described in [RFC2330], such as transport
	protocol, payload length, TTL, etc. An example for passive metrics		protocol, payload length, TTL, etc. An example for passive metrics
	is for RTP packet loss calculation that relies on the validation of a		is for RTP packet loss calculation that relies on the validation of a
	packet as RTP which is a multi-packet validation controlled by		packet as RTP which is a multi-packet validation controlled by
	MIN_SEQUENTIAL as defined by [RFC3550]. Varying MIN_SEQUENTIAL		MIN_SEQUENTIAL as defined by [RFC3550]. Varying MIN_SEQUENTIAL
	values can alter the loss report and this value could be set as a		values can alter the loss report and this value could be set as a
	Fixed Parameter.		Fixed Parameter.
	Parameters MUST have well defined names. For human readers, the		Parameters MUST have well-defined names. For human readers, the
	hanging indent style is preferred, and the names and definitions that		hanging indent style is preferred, and any Parameter names and
	do not appear in the Reference Method Specification MUST appear in		definitions that do not appear in the Reference Method Specification
	this column.		MUST appear in this column (or Run-time Parameters column).
	Parameters MUST have a well-specified data format.		Parameters MUST have a well-specified data format.
	A Parameter which is a Fixed Parameter for one Performance Metrics		A Parameter which is a Fixed Parameter for one Performance Metrics
	Registry entry may be designated as a Run-time Parameter for another		Registry entry may be designated as a Run-time Parameter for another
	Performance Metrics Registry entry.		Performance Metrics Registry entry.
	7.3. Method of Measurement Category		7.3. Method of Measurement Category
	This category includes columns for references to relevant sections of		This category includes columns for references to relevant sections of
	skipping to change at page 26, line 39 ¶		skipping to change at page 26, line 39 ¶
	9. Security considerations		9. Security considerations
	This draft doesn't introduce any new security considerations for the		This draft doesn't introduce any new security considerations for the
	Internet. However, the definition of Performance Metrics may		Internet. However, the definition of Performance Metrics may
	introduce some security concerns, and should be reviewed with		introduce some security concerns, and should be reviewed with
	security in mind.		security in mind.
	10. IANA Considerations		10. IANA Considerations
			This document requests the following IANA Actions.
			10.1. New Namespace Assignments
			This document requests the allocation of the URI prefix
			urn:ietf:metrics for the purpose of generating URIs for metrics in
			general. The registration procedure for the new "metrics" URN sub-
			namespace is IETF Review.
			This document requests the allocation of the URI prefix
			urn:ietf:metrics:perf for the purpose of generating URIs for
			Registered Performance Metrics. The registration procedures for the
			new "perf" URN sub-namespace are Expert Review or IETF Standards
			Action, and coordinated with the entries added to the New Performance
			Metrics Registry (see below).
			10.2. Performance Metric Name Elements
			This document specifies the procedure for Performance Metrics Name
			Element Registry setup. IANA is requested to create a new set of
			registries for Performance Metric Name Elements called "IETF URN Sub-
			namespace for Registered Performance Metric Name Elements"
			(urn:ietf:metrics:perf). Each Registry, whose names are listed
			below:
			MetricType:
			Method:
			SubTypeMethod:
			Spec:
			Units:
			Output:
			will contain the current set of possibilities for Performance Metric
			Registry Entry Names.
			To populate the IETF URN Sub-namespace for Registered Performance
			Metric Name Elements at creation, the IANA is asked to use the lists
			of values for each name element listed in Section 7.1.2. The Name
			Elements in each registry are case-sensitive.
			When preparing a Metric entry for Registration, the developer SHOULD
			choose Name elements from among the registered elements. However, if
			the proposed metric is unique in a significant way, it may be
			necessary to propose a new Name element to properly describe the
			metric, as described below.
			A candidate Metric Entry RFC or document for Expert Review would
			propose one or more new element values required to describe the
			unique entry, and the new name element(s) would be reviewed along
			with the metric entry. New assignments for IETF URN Sub-namespace
			for Registered Performance Metric Name Elements will be administered
			by IANA through Expert Review [RFC5226], i.e., review by one of a
			group of experts, the Performance Metric Experts, who are appointed
			by the IESG upon recommendation of the Transport Area Directors.
			10.3. New Performance Metrics Registry
	This document specifies the procedure for Performance Metrics		This document specifies the procedure for Performance Metrics
	Registry setup. IANA is requested to create a new registry for		Registry setup. IANA is requested to create a new registry for
	Performance Metrics called "Registered Performance Metrics". This		Performance Metrics called "Registered Performance Metrics". This
	Registry will contain the following Summary columns:		Registry will contain the following Summary columns:
	Identifier:		Identifier:
	Name:		Name:
	URIs:		URIs:
	skipping to change at page 27, line 20 ¶		skipping to change at page 28, line 37 ¶
	template for registry entries (categories and columns) are further		template for registry entries (categories and columns) are further
	defined in section Section 7.		defined in section Section 7.
	The "Identifier" 0 should be Reserved. "The Identifier" values from		The "Identifier" 0 should be Reserved. "The Identifier" values from
	64512 to 65536 are reserved for private use.		64512 to 65536 are reserved for private use.
	Names starting with the prefix Priv_ are reserved for private use,		Names starting with the prefix Priv_ are reserved for private use,
	and are not considered for registration. The "Name" column entries		and are not considered for registration. The "Name" column entries
	are further defined in section Section 7.		are further defined in section Section 7.
	The "URIs" column will have a link to the full template.		The "URIs" column will have a URL to the full template of each
			registry entry, and the linked text may be the URN itself. The
			template shall be HTML-ized to aid the reader, with links to
			reference RFCs (similar to the way that Internet Drafts are HTML-
			ized, the same tool can perform the function).
	The "Reference" column will include an RFC, an approved specification		The "Reference" column will include an RFC, an approved specification
	from another standards body, or the contact person.		from another standards body, or the contact person.
	New assignments for Performance Metric Registry will be administered		New assignments for Performance Metric Registry will be administered
	by IANA through Expert Review [RFC5226], i.e., review by one of a		by IANA through Expert Review [RFC5226], i.e., review by one of a
	group of experts, the Performance Metric Experts, who are appointed		group of experts, the Performance Metric Experts, who are appointed
	by the IESG upon recommendation of the Transport Area Directors. The		by the IESG upon recommendation of the Transport Area Directors. The
	experts can be initially drawn from the Working Group Chairs and		experts can be initially drawn from the Working Group Chairs,
	document editors of the Performance Metrics Directorate among other		document editors, and members of the Performance Metrics Directorate,
	sources of experts.		among other sources of experts.
	This document requests the allocation of the URI prefix
	urn:ietf:metric: for the purpose of generating URIs for Registered
	Performance Metrics.
	Extensions of the Registry require IETF Standards Action. Two forms		Extensions of the Performance Metric Registry require IETF Standards
	of registry extension are envisaged:		Action. Only one form of registry extension is envisaged:
	1. Adding columns or both categories and columns, to accommodate		1. Adding columns, or both categories and columns, to accommodate
	unanticipated aspects of new measurements and metric categories.		unanticipated aspects of new measurements and metric categories.
	2. Additional values for the various elements used in the Metric		If the Performance Metrics Registry is extended in this way, the
	"Name" column. A candidate Metric Entry RFC would propose one or		Version number of future entries complying with the extension SHALL
	more new element values required to describe the entry, and the		be incremented (either in the unit or tenths digit, depending on the
	values would be reviewed along with the metric entry.		degree of extension.
	To address this second point above, the IANA is asked to take the
	sets of values for each name element in Section 7.1.2, and create a
	sub-registry with the following columns:
	MetricType:
	Method:
	SubTypeMethod:
	Spec:
	Units:
	Output:
	11. Acknowledgments		11. Acknowledgments
	Thanks to Brian Trammell and Bill Cerveny, IPPM chairs, for leading		Thanks to Brian Trammell and Bill Cerveny, IPPM chairs, for leading
	some brainstorming sessions on this topic. Thanks to Barbara Stark		some brainstorming sessions on this topic. Thanks to Barbara Stark
	and Juergen Schoenwaelder for the detailed feedback and suggestions.		and Juergen Schoenwaelder for the detailed feedback and suggestions.
	Thanks to Andrew McGregor for suggestions on metric naming. Thanks		Thanks to Andrew McGregor for suggestions on metric naming. Thanks
	to Michelle Cotton for her early IANA review, and to Amanda Barber		to Michelle Cotton for her early IANA review, and to Amanda Barber
	for answering questions related to the presentation of the registry		for answering questions related to the presentation of the registry
	and accessibility of the complete template via URL.		and accessibility of the complete template via URL.
End of changes. 19 change blocks.
	53 lines changed or deleted		102 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/