< draft-ietf-ippm-metric-registry-08.txt   draft-ietf-ippm-metric-registry-09.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: April 13, 2017 Cisco Systems, Inc. Expires: May 3, 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
October 10, 2016 October 30, 2016
Registry for Performance Metrics Registry for Performance Metrics
draft-ietf-ippm-metric-registry-08 draft-ietf-ippm-metric-registry-09
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 April 13, 2017. This Internet-Draft will expire on May 3, 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 27 skipping to change at page 2, line 27
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 . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . 15 7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 15 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 16
7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 15 7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 16
7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 15 7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 16
7.2. Metric Definition Category . . . . . . . . . . . . . . . 16 7.1.7. Version (of Registry Format) . . . . . . . . . . . . 16
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 16 7.2. Metric Definition Category . . . . . . . . . . . . . . . 17
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 16 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
7.3. Method of Measurement Category . . . . . . . . . . . . . 17 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 17 7.3. Method of Measurement Category . . . . . . . . . . . . . 18
7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 17 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18
7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 18 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 18
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 18 7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 19
7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 19 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 19
7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 19 7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 20
7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 20 7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 20
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 20 7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 21
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 20 7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 20 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 21
7.5. Administrative information . . . . . . . . . . . . . . . 20 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 21
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 20 7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 21
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 21 7.5. Administrative information . . . . . . . . . . . . . . . 22
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 21 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 21 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 22
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 21 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 22
8. The Life-Cycle of Registered Performance Metrics . . . . . . 21 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 22
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . 21 Registry . . . . . . . . . . . . . . . . . . . . . . . . 23
8.2. Revising Registered Performance Metrics . . . . . . . . . 22 8.2. Revising Registered Performance Metrics . . . . . . . . . 24
8.3. Deprecating Registered Performance Metrics . . . . . . . 24 8.3. Deprecating Registered Performance Metrics . . . . . . . 25
9. Security considerations . . . . . . . . . . . . . . . . . . . 24 9. Security considerations . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.1. Normative References . . . . . . . . . . . . . . . . . . 26 12.1. Normative References . . . . . . . . . . . . . . . . . . 28
12.2. Informative References . . . . . . . . . . . . . . . . . 27 12.2. Informative References . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
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 12, line 5 skipping to change at page 12, line 5
The columns of the Performance Metric Registry are defined below. The columns of the Performance Metric Registry are defined below.
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 7.x heading level, and the registry. Categories are described at the 7.x heading level, and
columns are at the 7.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 | Reference | Change Controller Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver |
Metric Definition Metric Definition
----------------------------------------- -----------------------------------------
Reference Definition | Fixed Parameters | Reference Definition | Fixed Parameters |
Method of Measurement Method of Measurement
--------------------------------------------------------------------- ---------------------------------------------------------------------
Reference | Packet | Traffic | Sampling | Run-time | Role | Reference | Packet | Traffic | Sampling | Run-time | Role |
Method | Stream | Filter | Distribution | Parameters | | Method | Stream | Filter | Distribution | Parameters | |
| Generation | | Generation |
Output Output
----------------------------- -----------------------------------------
| Type | Reference | Units | Type | Reference | Units | Calibration |
| | Definition | | | Definition | | |
Administrative Information Administrative Information
---------------------------------- ----------------------------------
Status |Request | Rev | Rev.Date | Status |Request | Rev | Rev.Date |
Comments and Remarks Comments and Remarks
-------------------- --------------------
-------------------
7.1. Summary Category 7.1. Summary Category
7.1.1. Identifier 7.1.1. Identifier
A numeric identifier for the Registered Performance Metric. This A numeric identifier for the Registered Performance Metric. This
identifier MUST be unique within the Performance Metric Registry. identifier MUST be unique within the Performance Metric Registry.
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). integer (range 0 to 65535).
skipping to change at page 13, line 25 skipping to change at page 13, line 25
Names are composed of the following elements, separated by an Names are composed of the following elements, separated by an
underscore character "_": underscore character "_":
MetricType_Method_SubTypeMethod_... Spec_Units_Output MetricType_Method_SubTypeMethod_... Spec_Units_Output
o MetricType: a combination of the directional properties and the o MetricType: a combination of the directional properties and the
metric measured, such as: metric measured, such as:
RTDelay RTDelay
RTDNS
OWDelay OWDelay
RTLoss RTLoss
OWLoss OWLoss
OWPDV OWPDV
OWIPDV OWIPDV
OWReorder OWReorder
OWDuplic OWDuplic
OWBTC
OWMBM
SPMonitor (Single Point Monitor)
MPMonitor (Multi-Point Monitor)
o Method: One of the methods defined in [RFC7799], such as: o Method: One of the methods defined in [RFC7799], such as:
Active Active
Passive Passive
HybridType1 HybridType1
HybridType2 HybridType2
Spatial Spatial
o SubTypeMethod: One or more sub-types to further describe the o SubTypeMethod: One or more sub-types to further describe the
features of the entry, such as: features of the entry, such as:
ICMP ICMP
IP IP
DSCPxx (where xx is replaced by a decimal code point)
UDP UDP
TCP
Poisson Poisson
Periodic Periodic
o <optionally, other SubTypeMethods> PayloadxxxxB (where xxxx is replaced by an integer)
SustainedBurst
StandingQueue
@@@@<add others from MBM draft?>
SubTypeMethod values are separated by a hyphen "-" character,
which indicates that they belong to this element, and that their
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; it will be blank until the RFC
number is assigned, and would remain blank in private registry number is assigned, and would remain blank in private registry
entries without an RFC. entries without an 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 RatioPercent (value multiplied by 100)
BPS (Bits per Second)
EventTotal (for unit-less counts) EventTotal (for unit-less counts)
Multiple
Enumerated
Unit-less
o Output: The type of output resulting from measurement, such as: o Output: The type of output resulting from measurement, such as:
Singleton Singleton (sometimes called raw data)
Minimum Minimum
Maximum Maximum
Median Median
Mean Mean
95percentile 95Percentile
99percentile 99Percentile
StdDev
PFI (Pass, Fail, Inconclusive)
FlowRecords
An example is: An example is:
RTDelay_Active_UDP_Poisson_RFCXXXXsecY_Seconds_95th%tile 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 urn:ietf:params:ippm:metric: to generated by prepending the prefix
the metric name. The resulting URI is globally unique.
urn:ietf:metric:
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
skipping to change at page 16, line 5 skipping to change at page 16, line 47
This entry gives the specification containing the candidate registry This entry gives the specification containing the candidate registry
entry which was reviewed and agreed, if such an RFC or other entry which was reviewed and agreed, if such an RFC or other
specification exists. specification exists.
7.1.6. Change Controller 7.1.6. Change Controller
This entry names the entity responsible for approving revsions to the This entry names the entity responsible for approving revsions to the
regsitry entry, and provides contact information. regsitry entry, and provides contact information.
7.1.7. Version (of Registry Format)
This entry gives the version number for the registry format used.
Formats complying with this memo MUST use 1.0.
7.2. Metric Definition Category 7.2. Metric Definition Category
This category includes columns to prompt all necessary details This category includes columns to prompt all necessary details
related to the metric definition, including the RFC reference and related to the metric definition, including the RFC reference and
values of input factors, called fixed parameters, which are left open values of input factors, called fixed parameters, which are left open
in the RFC but have a particular value defined by the performance in the RFC but have a particular value defined by the performance
metric. metric.
7.2.1. Reference Definition 7.2.1. Reference Definition
skipping to change at page 20, line 28 skipping to change at page 21, line 28
This column contains the name of the output type. The output type This column contains the name of the output type. The output type
defines a single type of result that the metric produces. It can be defines a single type of result that the metric produces. It can be
the raw results (packet send times and singleton metrics), or it can the raw results (packet send times and singleton metrics), or it can
be a summary statistic. The specification of the output type MUST be a summary statistic. The specification of the output type MUST
define the format of the output. In some systems, format define the format of the output. In some systems, format
specifications will simplify both measurement implementation and specifications will simplify both measurement implementation and
collection/storage tasks. Note that if two different statistics are collection/storage tasks. Note that if two different statistics are
required from a single measurement (for example, both "Xth percentile required from a single measurement (for example, both "Xth percentile
mean" and "Raw"), then a new output type must be defined ("Xth mean" and "Raw"), then a new output type must be defined ("Xth
percentile mean AND Raw"). percentile mean AND Raw"). See the Naming section above for a list
of Output Types.
7.4.2. Reference Definition 7.4.2. Reference Definition
This column contains a pointer to the specification where the output This column contains a pointer to the specification(s) where the
type is defined output type and format are defined.
7.4.3. Metric Units 7.4.3. Metric Units
The measured results must be expressed using some standard dimension The measured results must be expressed using some standard dimension
or units of measure. This column provides the units. or units of measure. This column provides the units.
When a sample of singletons (see [RFC2330] for definitions of these When a sample of singletons (see Section 11 of[RFC2330] for
terms) is collected, this entry will specify the units for each definitions of these terms) is collected, this entry will specify the
measured value. units for each measured value.
7.4.4. Calibration
Some specifications for Methods of Measurement include the
possibility to perform an error calibration. Section 3.7.3 of
[RFC7679] is one example. In the registry entry, this field will
identify a method of calibration for the metric, and when available,
the measurement system SHOULD perform the calibration when requested
and produce the output with an indication that it is the restult of a
calbration method. In-situ calibration could be enabled with an
internal loopback that includes as much of the measurement system as
possible, performs address manipulation as needed, and provides some
form of isolation (e.g., deterministic delay) to avoid send-receive
interface contention. Some portion of the random and systematic
error can be characterized this way.
For one-way delay measurements, the error calibration must include an
assessment of the internal clock synchronization with its external
reference (this internal clock is supplying timestamps for
measurement). In practice, the time offsets of clocks at both the
source and destination are needed to estimate the systematic error
due to imperfect clock synchronization (the time offsets are
smoothed, thus the random variation is not usually represented in the
results).
Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system
noise, and thus inaccurate.
7.5. Administrative information 7.5. Administrative information
7.5.1. Status 7.5.1. Status
The status of the specification of this Registered Performance The status of the specification of this Registered Performance
Metric. Allowed values are 'current' and 'deprecated'. All newly Metric. Allowed values are 'current' and 'deprecated'. All newly
defined Information Elements have 'current' status. defined Information Elements have 'current' status.
7.5.2. Requester 7.5.2. Requester
skipping to change at page 25, line 17 skipping to change at page 26, line 52
Name: Name:
URIs: URIs:
Description: Description:
Reference: Reference:
Change Controller: Change Controller:
Version:
Descriptions of these columns and additional information found in the Descriptions of these columns and additional information found in the
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 "Name" (or "URIs" ??) column will have a link to the full The "URIs" column will have a link to the full template.
template.
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 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.
>>> ok to here, pending the use of "Name" or URIs column question.
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:metric: for the purpose of generating URIs for Registered
Registered Performance Metrics. Note: an alternate proposal which Performance Metrics.
avoids the "params" namspace for protocols is urn:ietf:metric: .
Extensions of the Registry require IETF Standards Action. Two forms Extensions of the Registry require IETF Standards Action. Two forms
of registry extension are envisaged: of registry extension are 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.
Note: this form of extension may be well-served by adding a
format version number column now, then existing entries (without
the extended column) can be left as-is, if desired.
2. Additional values for the various elements used in the Metric 2. Additional values for the various elements used in the Metric
"Name" column. A candidate Metric Entry RFC would propose one or "Name" column. A candidate Metric Entry RFC would propose one or
more new element values required to describe the entry. more new element values required to describe the entry.
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 29, line 30 skipping to change at page 31, line 11
[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, <http://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>. <http://www.rfc-editor.org/info/rfc7594>.
[I-D.ietf-ippm-active-passive]
Morton, A., "Active and Passive Metrics and Methods (and
everything in-between, or Hybrid)", draft-ietf-ippm-
active-passive-06 (work in progress), January 2016.
[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, <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-01 (work in progress), July 2016. ippm-initial-registry-01 (work in progress), July 2016.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
 End of changes. 37 change blocks. 
94 lines changed or deleted 161 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/