< draft-ietf-ippm-metric-registry-14.txt		draft-ietf-ippm-metric-registry-15.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: September 5, 2018 Cisco Systems, Inc.		Expires: January 1, 2019 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
	March 4, 2018		June 30, 2018
	Registry for Performance Metrics		Registry for Performance Metrics
	draft-ietf-ippm-metric-registry-14		draft-ietf-ippm-metric-registry-15
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 September 5, 2018.		This Internet-Draft will expire on January 1, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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
	skipping to change at page 2, line 23 ¶		skipping to change at page 2, line 23 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6		3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. Motivation for a Performance Metrics Registry . . . . . . . . 7		4. Motivation for a Performance Metrics Registry . . . . . . . . 7
	4.1. Interoperability . . . . . . . . . . . . . . . . . . . . 7		4.1. Interoperability . . . . . . . . . . . . . . . . . . . . 7
	4.2. Single point of reference for Performance Metrics . . . . 8		4.2. Single point of reference for Performance Metrics . . . . 8
	4.3. Side benefits . . . . . . . . . . . . . . . . . . . . . . 8		4.3. Side benefits . . . . . . . . . . . . . . . . . . . . . . 8
	5. Criteria for Performance Metrics Registration . . . . . . . . 9		5. Criteria for Performance Metrics Registration . . . . . . . . 9
	6. Performance Metric Registry: Prior attempt . . . . . . . . . 9		6. Performance Metric Registry: Prior attempt . . . . . . . . . 9
	6.1. Why this Attempt Will Succeed . . . . . . . . . . . . . . 10		6.1. Why this Attempt Will Succeed . . . . . . . . . . . . . . 10
	7. Definition of the Performance Metric Registry . . . . . . . . 10		7. Definition of the Performance Metric Registry . . . . . . . . 11
	7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 12		7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 12
	7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12		7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12
	7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13		7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13
	7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16		7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16
	7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17		7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
	7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 17		7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 17
	7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 17		7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 17
	7.1.7. Version (of Registry Format) . . . . . . . . . . . . 17		7.1.7. Version (of Registry Format) . . . . . . . . . . . . 17
	7.2. Metric Definition Category . . . . . . . . . . . . . . . 17		7.2. Metric Definition Category . . . . . . . . . . . . . . . 17
	7.2.1. Reference Definition . . . . . . . . . . . . . . . . 17		7.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
	skipping to change at page 4, line 42 ¶		skipping to change at page 4, line 42 ¶
	guarantee of the format's applicability to any possible set of		guarantee of the format's applicability to any possible set of
	Performance Metrics envisaged by other organizations, but encourage		Performance Metrics envisaged by other organizations, but encourage
	others to apply it. In the remainder of this document, unless we		others to apply it. In the remainder of this document, unless we
	explicitly say so, we will refer to the IANA-maintained Performance		explicitly say so, we will refer to the IANA-maintained Performance
	Metrics Registry as simply the Performance Metrics Registry.		Metrics Registry as simply the Performance Metrics Registry.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in BCP
	[RFC2119].		14[RFC2119] [RFC8174] when, and only when, they appear in all
			capitals, as shown here.
	Performance Metric: A Performance Metric is a quantitative measure		Performance Metric: A Performance Metric is a quantitative measure
	of performance, targeted to an IETF-specified protocol or targeted		of performance, targeted to an IETF-specified protocol or targeted
	to an application transported over an IETF-specified protocol.		to an application transported over an IETF-specified protocol.
	Examples of Performance Metrics are the FTP response time for a		Examples of Performance Metrics are the FTP response time for a
	complete file download, the DNS response time to resolve the IP		complete file download, the DNS response time to resolve the IP
	address, a database logging time, etc. This definition is		address, a database logging time, etc. This definition is
	consistent with the definition of metric in [RFC2330] and broader		consistent with the definition of metric in [RFC2330] and broader
	than the definition of performance metric in [RFC6390].		than the definition of performance metric in [RFC6390].
	skipping to change at page 31, line 15 ¶		skipping to change at page 31, line 15 ¶
	[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New		[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
	Performance Metric Development", BCP 170, RFC 6390,		Performance Metric Development", BCP 170, RFC 6390,
	DOI 10.17487/RFC6390, October 2011,		DOI 10.17487/RFC6390, October 2011,
	<https://www.rfc-editor.org/info/rfc6390>.		<https://www.rfc-editor.org/info/rfc6390>.
	[RFC6576] Geib, R., Ed., Morton, A., Fardid, R., and A. Steinmitz,		[RFC6576] Geib, R., Ed., Morton, A., Fardid, R., and A. Steinmitz,
	"IP Performance Metrics (IPPM) Standard Advancement		"IP Performance Metrics (IPPM) Standard Advancement
	Testing", BCP 176, RFC 6576, DOI 10.17487/RFC6576, March		Testing", BCP 176, RFC 6576, DOI 10.17487/RFC6576, March
	2012, <https://www.rfc-editor.org/info/rfc6576>.		2012, <https://www.rfc-editor.org/info/rfc6576>.
			[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
			2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
			May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	12.2. Informative References		12.2. Informative References
	[I-D.ietf-ippm-initial-registry]		[I-D.ietf-ippm-initial-registry]
	Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,		Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,
	"Initial Performance Metric Registry Entries", draft-ietf-		"Initial Performance Metric Registry Entries", draft-ietf-
	ippm-initial-registry-05 (work in progress), October 2017.		ippm-initial-registry-06 (work in progress), March 2018.
	[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way		[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
	Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,		Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,
	September 1999, <https://www.rfc-editor.org/info/rfc2679>.		September 1999, <https://www.rfc-editor.org/info/rfc2679>.
	[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip		[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
	Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,		Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
	September 1999, <https://www.rfc-editor.org/info/rfc2681>.		September 1999, <https://www.rfc-editor.org/info/rfc2681>.
	[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation		[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
End of changes. 8 change blocks.
	8 lines changed or deleted		13 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/