< draft-ietf-ippm-metric-registry-12.txt		draft-ietf-ippm-metric-registry-13.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: January 1, 2018 Cisco Systems, Inc.		Expires: May 2, 2018 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
	June 30, 2017		October 29, 2017
	Registry for Performance Metrics		Registry for Performance Metrics
	draft-ietf-ippm-metric-registry-12		draft-ietf-ippm-metric-registry-13
	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
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 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 January 1, 2018.		This Internet-Draft will expire on May 2, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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		(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
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 2, line 28 ¶		skipping to change at page 2, line 28 ¶
	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 . . . . . . . . 10
	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 . . . . . . . . . . . . . . . . . . . . . 16		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
	7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17		7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17
	7.3. Method of Measurement Category . . . . . . . . . . . . . 18		7.3. Method of Measurement Category . . . . . . . . . . . . . 18
	7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18		7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18
	7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 18		7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 18
	7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 19		7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 19
	7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 19		7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 20
	7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 20		7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 20
	7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 21		7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 21
	7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 21		7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 21
	7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21		7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21
	7.4.2. Reference Definition . . . . . . . . . . . . . . . . 21		7.4.2. Reference Definition . . . . . . . . . . . . . . . . 22
	7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 22		7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 22
	7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22		7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22
	7.5. Administrative information . . . . . . . . . . . . . . . 22		7.5. Administrative information . . . . . . . . . . . . . . . 23
	7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22		7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 23
	7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 23		7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 23
	7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 23		7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 23
	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 . . . . . . . . . . . . . . . . . . . . . . . . 24
	8.2. Revising Registered Performance Metrics . . . . . . . . . 24		8.2. Revising Registered Performance Metrics . . . . . . . . . 24
	8.3. Deprecating Registered Performance Metrics . . . . . . . 26		8.3. Deprecating Registered Performance Metrics . . . . . . . 26
	9. Security considerations . . . . . . . . . . . . . . . . . . . 26		9. Security considerations . . . . . . . . . . . . . . . . . . . 27
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
	10.1. New Namespace Assignments . . . . . . . . . . . . . . . 27		10.1. New Namespace Assignments . . . . . . . . . . . . . . . 27
	10.2. Performance Metric Name Elements . . . . . . . . . . . . 27		10.2. Performance Metric Name Elements . . . . . . . . . . . . 27
	10.3. New Performance Metrics Registry . . . . . . . . . . . . 28		10.3. New Performance Metrics Registry . . . . . . . . . . . . 28
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 29		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
	12.1. Normative References . . . . . . . . . . . . . . . . . . 29		12.1. Normative References . . . . . . . . . . . . . . . . . . 30
	12.2. Informative References . . . . . . . . . . . . . . . . . 30		12.2. Informative References . . . . . . . . . . . . . . . . . 31
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
	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
	skipping to change at page 14, line 36 ¶		skipping to change at page 14, line 36 ¶
	DSCPxx (where xx is replaced by a Diffserv code point)		DSCPxx (where xx is replaced by a Diffserv code point)
	UDP (User Datagram Protocol)		UDP (User Datagram Protocol)
	TCP (Transport Control Protocol)		TCP (Transport Control Protocol)
	Poisson (Packet generation using Poisson distribution)		Poisson (Packet generation using Poisson distribution)
	Periodic (Periodic packet generation)		Periodic (Periodic packet generation)
			SendOnRcv (Sender keeps one packet in-transit by sending when
			previous packet arrives)
	PayloadxxxxB (where xxxx is replaced by an integer, the number		PayloadxxxxB (where xxxx is replaced by an integer, the number
	of octets in the Payload))		of octets in the Payload))
	SustainedBurst (Capacity test, worst case)		SustainedBurst (Capacity test, worst case)
	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,
	skipping to change at page 15, line 17 ¶		skipping to change at page 15, line 22 ¶
	o Units: The units of measurement for the output, such as:		o Units: The units of measurement for the output, such as:
	Seconds		Seconds
	Ratio (unitless)		Ratio (unitless)
	Percent (value multiplied by 100)		Percent (value multiplied by 100)
	Logical (1 or 0)		Logical (1 or 0)
			Packets
	BPS (Bits per Second)		BPS (Bits per Second)
			PPS (Packets 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)
	Unitless		Unitless
	o Output: The type of output resulting from measurement, such as:		o Output: The type of output resulting from measurement, such as:
	Singleton		Singleton
	Raw (multiple Singletons)		Raw (multiple Singletons)
			Count
	Minimum		Minimum
	Maximum		Maximum
	Median		Median
	Mean		Mean
	95Percentile (95th Percentile)		95Percentile (95th Percentile)
	99Percentile (99th Percentile)		99Percentile (99th Percentile)
	StdDev (Standard Deviation)		StdDev (Standard Deviation)
	Variance		Variance
	PFI (Pass, Fail, Inconclusive)		PFI (Pass, Fail, Inconclusive)
	FlowRecords (descriptions of flows observed)		FlowRecords (descriptions of flows observed)
	LossRatio (lost packets to total packets, <=1)		LossRatio (lost packets to total packets, <=1)
	An example is:		An example is:
	RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95percentile		RTDelay_Active_IP-UDP-Periodic_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
	skipping to change at page 29, line 38 ¶		skipping to change at page 30, line 4 ¶
	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.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[RFC2026] Bradner, S., "The Internet Standards Process -- Revision		[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
	3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,		3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
	<http://www.rfc-editor.org/info/rfc2026>.		<https://www.rfc-editor.org/info/rfc2026>.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,		[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
	May 1997, <http://www.rfc-editor.org/info/rfc2141>.		May 1997, <https://www.rfc-editor.org/info/rfc2141>.
	[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,		[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
	"Framework for IP Performance Metrics", RFC 2330,		"Framework for IP Performance Metrics", RFC 2330,
	DOI 10.17487/RFC2330, May 1998,		DOI 10.17487/RFC2330, May 1998,
	<http://www.rfc-editor.org/info/rfc2330>.		<https://www.rfc-editor.org/info/rfc2330>.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66,		Resource Identifier (URI): Generic Syntax", STD 66,
	RFC 3986, DOI 10.17487/RFC3986, January 2005,		RFC 3986, DOI 10.17487/RFC3986, January 2005,
	<http://www.rfc-editor.org/info/rfc3986>.		<https://www.rfc-editor.org/info/rfc3986>.
	[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics		[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics
	Registry", BCP 108, RFC 4148, DOI 10.17487/RFC4148, August		Registry", BCP 108, RFC 4148, DOI 10.17487/RFC4148, August
	2005, <http://www.rfc-editor.org/info/rfc4148>.		2005, <https://www.rfc-editor.org/info/rfc4148>.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", RFC 5226,		IANA Considerations Section in RFCs", RFC 5226,
	DOI 10.17487/RFC5226, May 2008,		DOI 10.17487/RFC5226, May 2008,
	<http://www.rfc-editor.org/info/rfc5226>.		<https://www.rfc-editor.org/info/rfc5226>.
	[RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics		[RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics
	(IPPM) Registry of Metrics Are Obsolete", RFC 6248,		(IPPM) Registry of Metrics Are Obsolete", RFC 6248,
	DOI 10.17487/RFC6248, April 2011,		DOI 10.17487/RFC6248, April 2011,
	<http://www.rfc-editor.org/info/rfc6248>.		<https://www.rfc-editor.org/info/rfc6248>.
	[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,
	<http://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, <http://www.rfc-editor.org/info/rfc6576>.		2012, <https://www.rfc-editor.org/info/rfc6576>.
	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-03 (work in progress), March 2017.		ippm-initial-registry-04 (work in progress), June 2017.
	[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, <http://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, <http://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
	Metric for IP Performance Metrics (IPPM)", RFC 3393,		Metric for IP Performance Metrics (IPPM)", RFC 3393,
	DOI 10.17487/RFC3393, November 2002,		DOI 10.17487/RFC3393, November 2002,
	<http://www.rfc-editor.org/info/rfc3393>.		<https://www.rfc-editor.org/info/rfc3393>.
	[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network		[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
	performance measurement with periodic streams", RFC 3432,		performance measurement with periodic streams", RFC 3432,
	DOI 10.17487/RFC3432, November 2002,		DOI 10.17487/RFC3432, November 2002,
	<http://www.rfc-editor.org/info/rfc3432>.		<https://www.rfc-editor.org/info/rfc3432>.
	[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.		[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
	Jacobson, "RTP: A Transport Protocol for Real-Time		Jacobson, "RTP: A Transport Protocol for Real-Time
	Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,		Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
	July 2003, <http://www.rfc-editor.org/info/rfc3550>.		July 2003, <https://www.rfc-editor.org/info/rfc3550>.
	[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,		[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
	"RTP Control Protocol Extended Reports (RTCP XR)",		"RTP Control Protocol Extended Reports (RTCP XR)",
	RFC 3611, DOI 10.17487/RFC3611, November 2003,		RFC 3611, DOI 10.17487/RFC3611, November 2003,
	<http://www.rfc-editor.org/info/rfc3611>.		<https://www.rfc-editor.org/info/rfc3611>.
	[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session		[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
	Description Protocol", RFC 4566, DOI 10.17487/RFC4566,		Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
	July 2006, <http://www.rfc-editor.org/info/rfc4566>.		July 2006, <https://www.rfc-editor.org/info/rfc4566>.
	[RFC5474] Duffield, N., Ed., Chiou, D., Claise, B., Greenberg, A.,		[RFC5474] Duffield, N., Ed., Chiou, D., Claise, B., Greenberg, A.,
	Grossglauser, M., and J. Rexford, "A Framework for Packet		Grossglauser, M., and J. Rexford, "A Framework for Packet
	Selection and Reporting", RFC 5474, DOI 10.17487/RFC5474,		Selection and Reporting", RFC 5474, DOI 10.17487/RFC5474,
	March 2009, <http://www.rfc-editor.org/info/rfc5474>.		March 2009, <https://www.rfc-editor.org/info/rfc5474>.
	[RFC5475] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.		[RFC5475] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
	Raspall, "Sampling and Filtering Techniques for IP Packet		Raspall, "Sampling and Filtering Techniques for IP Packet
	Selection", RFC 5475, DOI 10.17487/RFC5475, March 2009,		Selection", RFC 5475, DOI 10.17487/RFC5475, March 2009,
	<http://www.rfc-editor.org/info/rfc5475>.		<https://www.rfc-editor.org/info/rfc5475>.
	[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G.		[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G.
	Carle, "Information Model for Packet Sampling Exports",		Carle, "Information Model for Packet Sampling Exports",
	RFC 5477, DOI 10.17487/RFC5477, March 2009,		RFC 5477, DOI 10.17487/RFC5477, March 2009,
	<http://www.rfc-editor.org/info/rfc5477>.		<https://www.rfc-editor.org/info/rfc5477>.
	[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation		[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
	Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,		Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
	March 2009, <http://www.rfc-editor.org/info/rfc5481>.		March 2009, <https://www.rfc-editor.org/info/rfc5481>.
	[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,		[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
	"Network Time Protocol Version 4: Protocol and Algorithms		"Network Time Protocol Version 4: Protocol and Algorithms
	Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,		Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
	<http://www.rfc-editor.org/info/rfc5905>.		<https://www.rfc-editor.org/info/rfc5905>.
	[RFC6035] Pendleton, A., Clark, A., Johnston, A., and H. Sinnreich,		[RFC6035] Pendleton, A., Clark, A., Johnston, A., and H. Sinnreich,
	"Session Initiation Protocol Event Package for Voice		"Session Initiation Protocol Event Package for Voice
	Quality Reporting", RFC 6035, DOI 10.17487/RFC6035,		Quality Reporting", RFC 6035, DOI 10.17487/RFC6035,
	November 2010, <http://www.rfc-editor.org/info/rfc6035>.		November 2010, <https://www.rfc-editor.org/info/rfc6035>.
	[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information		[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
	Reporting Using a Source Description (SDES) Item and an		Reporting Using a Source Description (SDES) Item and an
	RTCP Extended Report (XR) Block", RFC 6776,		RTCP Extended Report (XR) Block", RFC 6776,
	DOI 10.17487/RFC6776, October 2012,		DOI 10.17487/RFC6776, October 2012,
	<http://www.rfc-editor.org/info/rfc6776>.		<https://www.rfc-editor.org/info/rfc6776>.
	[RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use		[RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use
	of the RTP Monitoring Framework", RFC 6792,		of the RTP Monitoring Framework", RFC 6792,
	DOI 10.17487/RFC6792, November 2012,		DOI 10.17487/RFC6792, November 2012,
	<http://www.rfc-editor.org/info/rfc6792>.		<https://www.rfc-editor.org/info/rfc6792>.
	[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",		[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
	RFC 6991, DOI 10.17487/RFC6991, July 2013,		RFC 6991, DOI 10.17487/RFC6991, July 2013,
	<http://www.rfc-editor.org/info/rfc6991>.		<https://www.rfc-editor.org/info/rfc6991>.
	[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control		[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
	Protocol (RTCP) Extended Report (XR) Block for Burst/Gap		Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
	Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003,		Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003,
	September 2013, <http://www.rfc-editor.org/info/rfc7003>.		September 2013, <https://www.rfc-editor.org/info/rfc7003>.
	[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model		[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
	for IP Flow Information Export (IPFIX)", RFC 7012,		for IP Flow Information Export (IPFIX)", RFC 7012,
	DOI 10.17487/RFC7012, September 2013,		DOI 10.17487/RFC7012, September 2013,
	<http://www.rfc-editor.org/info/rfc7012>.		<https://www.rfc-editor.org/info/rfc7012>.
	[RFC7014] D'Antonio, S., Zseby, T., Henke, C., and L. Peluso, "Flow		[RFC7014] D'Antonio, S., Zseby, T., Henke, C., and L. Peluso, "Flow
	Selection Techniques", RFC 7014, DOI 10.17487/RFC7014,		Selection Techniques", RFC 7014, DOI 10.17487/RFC7014,
	September 2013, <http://www.rfc-editor.org/info/rfc7014>.		September 2013, <https://www.rfc-editor.org/info/rfc7014>.
	[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,		[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
	Aitken, P., and A. Akhter, "A Framework for Large-Scale		Aitken, P., and A. Akhter, "A Framework for Large-Scale
	Measurement of Broadband Performance (LMAP)", RFC 7594,		Measurement of Broadband Performance (LMAP)", RFC 7594,
	DOI 10.17487/RFC7594, September 2015,		DOI 10.17487/RFC7594, September 2015,
	<http://www.rfc-editor.org/info/rfc7594>.		<https://www.rfc-editor.org/info/rfc7594>.
	[RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,		[RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
	Ed., "A One-Way Delay Metric for IP Performance Metrics		Ed., "A One-Way Delay Metric for IP Performance Metrics
	(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January		(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January
	2016, <http://www.rfc-editor.org/info/rfc7679>.		2016, <https://www.rfc-editor.org/info/rfc7679>.
	[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with		[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
	Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,		Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
	May 2016, <http://www.rfc-editor.org/info/rfc7799>.		May 2016, <https://www.rfc-editor.org/info/rfc7799>.
	Authors' Addresses		Authors' Addresses
	Marcelo Bagnulo		Marcelo Bagnulo
	Universidad Carlos III de Madrid		Universidad Carlos III de Madrid
	Av. Universidad 30		Av. Universidad 30
	Leganes, Madrid 28911		Leganes, Madrid 28911
	SPAIN		SPAIN
	Phone: 34 91 6249500		Phone: 34 91 6249500
End of changes. 54 change blocks.
	52 lines changed or deleted		60 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/