< draft-ietf-ippm-metric-registry-06.txt		draft-ietf-ippm-metric-registry-07.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 22, 2016 Cisco Systems, Inc.		Expires: January 9, 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
	March 21, 2016		July 8, 2016
	Registry for Performance Metrics		Registry for Performance Metrics
	draft-ietf-ippm-metric-registry-06		draft-ietf-ippm-metric-registry-07
	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 September 22, 2016.		This Internet-Draft will expire on January 9, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	Table of Contents		Table of Contents
	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 . . . . . . . . 8		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 . . . . . . . . . . . . . . . . . . . . 11		7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 12
	7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 11		7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 12
	7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 12		7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13
	7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 13		7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 14
	7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 13		7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 14
	7.2. Metric Definition Category . . . . . . . . . . . . . . . 13		7.2. Metric Definition Category . . . . . . . . . . . . . . . 14
	7.2.1. Reference Definition . . . . . . . . . . . . . . . . 13		7.2.1. Reference Definition . . . . . . . . . . . . . . . . 14
	7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 14		7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 15
	7.3. Method of Measurement Category . . . . . . . . . . . . . 14		7.3. Method of Measurement Category . . . . . . . . . . . . . 15
	7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 14		7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 15
	7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 15		7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 16
	7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 15		7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 16
	7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 16		7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 17
	7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 16		7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 17
	7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 17		7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 18
	7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 17		7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 18
	7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 18		7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 19
	7.4.2. Reference Definition . . . . . . . . . . . . . . . . 18		7.4.2. Reference Definition . . . . . . . . . . . . . . . . 19
	7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 18		7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 19
	7.5. Administrative information . . . . . . . . . . . . . . . 18		7.5. Administrative information . . . . . . . . . . . . . . . 19
	7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 18		7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 19
	7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 18		7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 19
	7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 18		7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 19
	7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 19		7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 20
	7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 19		7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 20
	8. The Life-Cycle of Registered Performance Metrics . . . . . . 19		8. The Life-Cycle of Registered Performance Metrics . . . . . . 20
	8.1. Adding new Performance Metrics to the Performance Metrics		8.1. Adding new Performance Metrics to the Performance Metrics
	Registry . . . . . . . . . . . . . . . . . . . . . . . . 19		Registry . . . . . . . . . . . . . . . . . . . . . . . . 20
	8.2. Revising Registered Performance Metrics . . . . . . . . . 20		8.2. Revising Registered Performance Metrics . . . . . . . . . 21
	8.3. Deprecating Registered Performance Metrics . . . . . . . 21		8.3. Deprecating Registered Performance Metrics . . . . . . . 22
	9. Security considerations . . . . . . . . . . . . . . . . . . . 22		9. Security considerations . . . . . . . . . . . . . . . . . . . 23
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
	12.1. Normative References . . . . . . . . . . . . . . . . . . 23		12.1. Normative References . . . . . . . . . . . . . . . . . . 24
	12.2. Informative References . . . . . . . . . . . . . . . . . 24		12.2. Informative References . . . . . . . . . . . . . . . . . 25
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
	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 5, line 52 ¶		skipping to change at page 5, line 52 ¶
	stream, and characterizes the loss experienced by a stream that		stream, and characterizes the loss experienced by a stream that
	approximates a user stream. These are both "loss metrics", but		approximates a user stream. These are both "loss metrics", but
	the difference in interpretation of the results is highly		the difference in interpretation of the results is highly
	dependent on the Run-time Parameters (at least), to the extreme		dependent on the Run-time Parameters (at least), to the extreme
	where we are actually using loss to infer its compliment:		where we are actually using loss to infer its compliment:
	delivered throughput.		delivered throughput.
	Active Measurement Method: Methods of Measurement conducted on		Active Measurement Method: Methods of Measurement conducted on
	traffic which serves only the purpose of measurement and is		traffic which serves only the purpose of measurement and is
	generated for that reason alone, and whose traffic characteristics		generated for that reason alone, and whose traffic characteristics
	are known a priori. A detailed definition of Active Measurement		are known a priori. The complete definition of Active Methods is
	Method is provided in [RFC7799][I-D.ietf-ippm-active-passive].		specified in section 3.4 of[RFC7799]. Examples of Active
	Examples of Active Measurement Methods are the measurement methods		Measurement Methods are the measurement methods for the One way
	for the One way delay metric defined in [RFC2679] and the one for		delay metric defined in [RFC7679] and the one for round trip delay
	round trip delay defined in [RFC2681].		defined in [RFC2681].
	Passive Measurement Method: Methods of Measurement conducted on		Passive Measurement Method: Methods of Measurement conducted on
	network traffic, generated either from the end users or from		network traffic, generated either from the end users or from
	network elements that would exist regardless whether the		network elements that would exist regardless whether the
	measurement was being conducted or not. One characteristic of		measurement was being conducted or not. The complete definition
	Passive Measurement Methods is that sensitive information may be		of Passive Methods is specified in section 3.6 of [RFC7799]. One
	observed, and as a consequence, stored in the measurement system.		characteristic of Passive Measurement Methods is that sensitive
	A detailed definition of Passive Measurement Method is provided in		information may be observed, and as a consequence, stored in the
	[RFC7799] [I-D.ietf-ippm-active-passive].		measurement system.
			Hybrid Measurement Method: Hybrid Methods are Methods of Measurement
			that use a combination of Active Methods and Passive Methods, to
			assess Active Metrics, Passive Metrics, or new metrics derived
			from the a priori knowledge and observations of the stream of
			interest. The complete definition of Hybrid Methods is specified
			in section 3.8 of [RFC7799].
	3. Scope		3. Scope
	This document is meant mainly for two different audiences. For those		This document is meant mainly for two different audiences. For those
	defining new Registered Performance Metrics, it provides		defining new Registered Performance Metrics, it provides
	specifications and best practices to be used in deciding which		specifications and best practices to be used in deciding which
	Registered Performance Metrics are useful for a measurement study,		Registered Performance Metrics are useful for a measurement study,
	instructions for writing the text for each column of the Registered		instructions for writing the text for each column of the Registered
	Performance Metrics, and information on the supporting documentation		Performance Metrics, and information on the supporting documentation
	required for the new Performance Metrics Registry entry (up to and		required for the new Performance Metrics Registry entry (up to and
	skipping to change at page 10, line 51 ¶		skipping to change at page 11, line 17 ¶
	following columns: Identifier, Name, URI, Status, Requester,		following columns: Identifier, Name, URI, Status, Requester,
	Revision, Revision Date, Description. In addition, it may be		Revision, Revision Date, Description. In addition, it may be
	possible that, in the future, a new type of metric requires		possible that, in the future, a new type of metric requires
	additional columns. Should that be the case, it is possible to add		additional columns. Should that be the case, it is possible to add
	new columns to the registry. The specification defining the new		new columns to the registry. The specification defining the new
	column(s) must define how to populate the new column(s) for existing		column(s) must define how to populate the new column(s) for existing
	entries.		entries.
	The columns of the Performance Metric Registry are defined next. The		The columns of the Performance Metric Registry are defined next. The
	columns are grouped into "Categories" to facilitate the use of the		columns are grouped into "Categories" to facilitate the use of the
	registry. Categories are described at the 8.x heading level, and		registry. Categories are described at the 7.x heading level, and
	columns are at the 8.x.y heading level. The Figure below illustrates		columns are at the 7.x.y heading level. The Figure below illustrates
	this organization. An entry (row) therefore gives a complete		this organization. An entry (row) therefore gives a complete
	description of a Registered Performance Metric.		description of a Registered Performance Metric.
	Each column serves as a check-list item and helps to avoid omissions		Each column serves as a check-list item and helps to avoid omissions
	during registration and expert review.		during registration and expert review.
	Registry Categories and Columns, shown as		Registry Categories and Columns, shown as
	Category		Category
	------------------		------------------
	Column | Column |		Column | Column |
	Summary		Summary
	-------------------------------		-------------------------------
	Identifier | Name | URIs | Description |		Identifier | Name | URIs | Description |
	Metric Definition		Metric Definition
	-----------------------------------------		-----------------------------------------
	skipping to change at page 12, line 10 ¶		skipping to change at page 13, line 8 ¶
	The Registered Performance Metric unique identifier is a 16-bit		The Registered Performance Metric unique identifier is a 16-bit
	integer (range 0 to 65535). When adding newly Registered Performance		integer (range 0 to 65535). When adding newly Registered Performance
	Metrics to the Performance Metric Registry, IANA should assign the		Metrics to the Performance Metric Registry, IANA should assign the
	lowest available identifier to the next Registered Performance		lowest available identifier to the next Registered Performance
	Metric.		Metric.
	7.1.2. Name		7.1.2. Name
	As the name of a Registered Performance Metric is the first thing a		As the name of a Registered Performance Metric is the first thing a
	potential implementor will use when determining whether it is		potential human implementor will use when determining whether it is
	suitable for a given application, it is important to be as precise		suitable for their measurement study, it is important to be as
	and descriptive as possible.		precise and descriptive as possible. In future, users will review
			the names to determine if the metric they want to measure has already
			been registered, or if a similar entry is available as a basis for
			creating a new entry.
	New names of Registered Performance Metrics:		Names are composed of the following elements, seperated by an
			underscore character "_":
	1. "MUST be chosen carefully to describe the Registered Performance		MetricType_MethodLayer_SubTypeMethod_... Spec_Units_Output
	Metric and the context in which it will be used."
	2. "MUST be unique within the Performance Metric Registry."		o MetricType: a combination of the directional properties and the
			metric measured, such as RTDelay, OWDelay,
	3. "MUST use capital letters for the first letter of each component.		o Method: One of the methods defined in [RFC7799], such as Active,
	All other letters MUST be lowercase, even for acronyms.		Passive, HybridType1,
	Exceptions are made for acronyms containing a mixture of
	lowercase and capital letters, such as 'IPv4' and 'IPv6'."
	4. MUST use '_' between each component of the Registered Performance		o SubTypeMethod: One or more sub-types to further describe the
	Metric name.		features of the entry, such as ICMP, IP, UDP, Poisson, Periodic,
	5. MUST start with prefix Act_ for active measurement Registered		o <optionally, other SubTypeMethods>
	Performance Metric.
	6. MUST start with prefix Pas_ for passive monitoring Registered		o Spec: RFC that specifies this entry in the form RFCXXXXsecY, such
	Performance Metric.		as RFC7799sec3. Note: this is not the Primary Reference
			specification for the metric; it will be blank until the RFC
			number is assigned.
	7. Other types of Performance Metric should define a proper prefix		o Units: The units of measurement for the output, such as Seconds,
	for identifying the type.		RatioPercent,
	8. The remaining rules for naming are left for the Performance		o Output: The type of resulting ouptut of measurement, such as
	Metric Experts to determine as they gather experience, so this is		Singleton, Minimum, Maximum, Median, 95%tile,
	an area of planned update by a future RFC.
	An example is "Act_UDP_Latency_Poisson_mean" for an active		An example is:
	measurement of a UDP latency metric using a Poisson stream of packets
	and producing the mean as output.
	Some examples of names of passive metrics might be: Pas_L3_L4_Octets		RTDelay_Active_UDP_Poisson_RFCXXXXsecY_Seconds_95th%tile
	(Layer 3 and 4 level accounting of bytes observed), Pas_DNS_RTT
	(Round Trip Time of in DNS query response of observed traffic), and		as described in section 4 of [I-D.ietf-ippm-initial-registry].
	Pas_L3_TCP_RTT (Passively observed round trip time in TCP handshake
	organized with L3 addresses)		Note that private registries following the format described here
			SHOULD use the prefix "Priv_" on any name to avoid unintended
			conflicts (further considerations are described in section 10).
			Private registry entries usually have no specifying RFC, thus the
			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 urn:ietf:params:ippm:metric: to		generated by prepending the prefix urn:ietf:params:ippm:metric: to
	the metric name. The resulting URI is globally unique.		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
	skipping to change at page 23, line 6 ¶		skipping to change at page 24, line 6 ¶
	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, appointed by the		group of experts, the Performance Metric Experts, appointed by the
	IESG upon recommendation of the Transport Area Directors. 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 and
	document editors of the Performance Metrics Directorate among other		document editors of the Performance Metrics Directorate among other
	sources of experts.		sources of experts.
	The Identifier values from 64512 to 65536 are reserved for private		The Identifier values from 64512 to 65536 are reserved for private
	use. The name starting with the prefix Priv- are reserved for		use. Names starting with the prefix Priv_ are reserved for private
	private use.		use, and are not considered for registration.
	This document requests the allocation of the URI prefix		This document requests the allocation of the URI prefix
	urn:ietf:params:ippm:metric for the purpose of generating URIs for		urn:ietf:params:ippm:metric for the purpose of generating URIs for
	Registered Performance Metrics.		Registered Performance Metrics.
	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.
	skipping to change at page 24, line 26 ¶		skipping to change at page 25, line 26 ¶
	"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, <http://www.rfc-editor.org/info/rfc6576>.
	12.2. Informative References		12.2. Informative References
	[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, <http://www.rfc-editor.org/info/rfc2679>.
			[RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
			Ed., "A One-Way Delay Metric for IP Performance Metrics
			(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January
			2016, <http://www.rfc-editor.org/info/rfc7679>.
	[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, <http://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>.		<http://www.rfc-editor.org/info/rfc3393>.
	[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network		[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
	skipping to change at page 26, line 25 ¶		skipping to change at page 27, line 30 ¶
	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>.		<http://www.rfc-editor.org/info/rfc7594>.
	[I-D.ietf-ippm-active-passive]		[I-D.ietf-ippm-active-passive]
	Morton, A., "Active and Passive Metrics and Methods (and		Morton, A., "Active and Passive Metrics and Methods (and
	everything in-between, or Hybrid)", draft-ietf-ippm-		everything in-between, or Hybrid)", draft-ietf-ippm-
	active-passive-06 (work in progress), January 2016.		active-passive-06 (work in progress), January 2016.
			[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
			Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
			May 2016, <http://www.rfc-editor.org/info/rfc7799>.
	[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-00 (work in progress), March 2016.		ippm-initial-registry-00 (work in progress), March 2016.
	[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>.		<http://www.rfc-editor.org/info/rfc6991>.
	Authors' Addresses		Authors' Addresses
End of changes. 27 change blocks.
	86 lines changed or deleted		106 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/