< draft-ietf-ippm-metric-registry-05.txt   draft-ietf-ippm-metric-registry-06.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 20, 2016 Cisco Systems, Inc. Expires: September 22, 2016 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 18, 2015 March 21, 2016
Registry for Performance Metrics Registry for Performance Metrics
draft-ietf-ippm-metric-registry-05 draft-ietf-ippm-metric-registry-06
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 20, 2016. This Internet-Draft will expire on September 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 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 . . . . . . . . 8 5. Criteria for Performance Metrics Registration . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . . 11
7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 11 7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 11
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 12 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 13 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 13
7.2. Metric Definition Category . . . . . . . . . . . . . . . 13 7.2. Metric Definition Category . . . . . . . . . . . . . . . 13
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 13 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 13
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 13 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 14
7.3. Method of Measurement Category . . . . . . . . . . . . . 14 7.3. Method of Measurement Category . . . . . . . . . . . . . 14
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 14 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 14
7.3.2. Packet Generation Stream . . . . . . . . . . . . . . 14 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 15
7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 15 7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 15
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 16 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 16
7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 16 7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 16
7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 17 7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 17
7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 17 7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 17
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 17 7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 18
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 17 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 18
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 18 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 18
7.5. Administrative information . . . . . . . . . . . . . . . 18 7.5. Administrative information . . . . . . . . . . . . . . . 18
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 18 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 18
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 18 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 18
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 18 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 18
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 18 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 19
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 18 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 19
8. The Life-Cycle of Registered Performance Metrics . . . . . . 18 8. The Life-Cycle of Registered Performance Metrics . . . . . . 19
8.1. Adding new Performance Metrics to the Performance Metrics 8.1. Adding new Performance Metrics to the Performance Metrics
Registry . . . . . . . . . . . . . . . . . . . . . . . . 19 Registry . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2. Revising Registered Performance Metrics . . . . . . . . . 19 8.2. Revising Registered Performance Metrics . . . . . . . . . 20
8.3. Deprecating Registered Performance Metrics . . . . . . . 21 8.3. Deprecating Registered Performance Metrics . . . . . . . 21
9. Security considerations . . . . . . . . . . . . . . . . . . . 22 9. Security considerations . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
12.1. Normative References . . . . . . . . . . . . . . . . . . 22 12.1. Normative References . . . . . . . . . . . . . . . . . . 23
12.2. Informative References . . . . . . . . . . . . . . . . . 23 12.2. Informative References . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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 4, line 23 skipping to change at page 4, line 23
addressed by creating a registry of performance metrics. The usual addressed by creating a registry of performance metrics. The usual
way in which IETF organizes namespaces is with Internet Assigned way in which IETF organizes namespaces is with Internet Assigned
Numbers Authority (IANA) registries, and there is currently no Numbers Authority (IANA) registries, and there is currently no
Performance Metrics Registry maintained by the IANA. Performance Metrics Registry maintained by the IANA.
This document therefore requests that IANA create and maintain a This document therefore requests that IANA create and maintain a
Performance Metrics Registry, according to the maintenance procedures Performance Metrics Registry, according to the maintenance procedures
and the Performance Metrics Registry format defined in this memo. and the Performance Metrics Registry format defined in this memo.
Although the Registry format is primarily for use by IANA, any other Although the Registry format is primarily for use by IANA, any other
organization that wishes to create a Performance Metrics Registry MAY organization that wishes to create a Performance Metrics Registry MAY
use the format for its purposes. The authors make no guarantee of use the same format for their purposes. The authors make no
the format's applicability to any possible set of Performance Metrics guarantee of the format's applicability to any possible set of
envisaged by other organizations. In the rest of this document, Performance Metrics envisaged by other organizations, but encourage
unless we explicitly say so, we will refer to the IANA-maintained others to apply it. In the remainder of this document, unless we
Performance Metrics Registry as simply the Performance Metrics explicitly say so, we will refer to the IANA-maintained Performance
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
[RFC2119]. [RFC2119].
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
skipping to change at page 6, line 4 skipping to change at page 6, line 4
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. A detailed definition of Active Measurement
Method is provided in [I-D.ietf-ippm-active-passive]. Examples of Method is provided in [RFC7799][I-D.ietf-ippm-active-passive].
Active Measurement Methods are the measurement methods for the One Examples of Active Measurement Methods are the measurement methods
way delay metric defined in [RFC2679] and the one for round trip for the One way delay metric defined in [RFC2679] and the one for
delay defined in [RFC2681]. round trip delay 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. One characteristic of
Passive Measurement Methods is that sensitive information may be Passive Measurement Methods is that sensitive information may be
observed, and as a consequence, stored in the measurement system. observed, and as a consequence, stored in the measurement system.
A detailed definition of Passive Measurement Method is provided in A detailed definition of Passive Measurement Method is provided in
[I-D.ietf-ippm-active-passive]. [RFC7799] [I-D.ietf-ippm-active-passive].
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 11, line 27 skipping to change at page 11, line 27
------------------------------- -------------------------------
Identifier | Name | URIs | Description | Identifier | Name | URIs | Description |
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 | Generation | Filter | Distribution | Parameters | | Method | Stream | Filter | Distribution | Parameters | |
| Stream | | Generation |
Output Output
----------------------------- -----------------------------
| Type | Reference | Units | | Type | Reference | Units |
| | Definition | | | | Definition | |
Administrative Information Administrative Information
---------------------------------- ----------------------------------
Status |Request | Rev | Rev.Date | Status |Request | Rev | Rev.Date |
Comments and Remarks Comments and Remarks
skipping to change at page 12, line 40 skipping to change at page 12, line 40
Performance Metric. Performance Metric.
6. MUST start with prefix Pas_ for passive monitoring Registered 6. MUST start with prefix Pas_ for passive monitoring Registered
Performance Metric. Performance Metric.
7. Other types of Performance Metric should define a proper prefix 7. Other types of Performance Metric should define a proper prefix
for identifying the type. for identifying the type.
8. The remaining rules for naming are left for the Performance 8. The remaining rules for naming are left for the Performance
Metric Experts to determine as they gather experience, so this is Metric Experts to determine as they gather experience, so this is
an area of planned update by a future RFC an area of planned update by a future RFC.
An example is "Act_UDP_Latency_Poisson_mean" for a active monitoring An example is "Act_UDP_Latency_Poisson_mean" for an active
UDP latency metric using a Poisson stream of packets and producing measurement of a UDP latency metric using a Poisson stream of packets
the mean as output. and producing the mean as output.
Some examples of names of passive metrics might be: Pas_L3_L4_Octets Some examples of names of passive metrics might be: Pas_L3_L4_Octets
(Layer 3 and 4 level accounting of bytes observed), Pas_DNS_RTT (Layer 3 and 4 level accounting of bytes observed), Pas_DNS_RTT
(Round Trip Time of in DNS query response of observed traffic), and (Round Trip Time of in DNS query response of observed traffic), and
Pas_L3_TCP_RTT (Passively observed round trip time in TCP handshake Pas_L3_TCP_RTT (Passively observed round trip time in TCP handshake
organized with L3 addresses) organized with L3 addresses)
7.1.3. URI 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
accessible through the Internet. The URL points to a file containing accessible through the Internet. The URL points to a file containing
the information of exactly one registry entry. The separate files the human-readable information of exactly one registry entry.
for different entries can be more easily edited and re-used when Ideally, the file will be HTML-formated and contain URLs to
referenced sections of HTML-ized RFCs. The separate files for
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, but there will be some overlap with the URN be determined by IANA, but there will be some overlap with the URN
described above. described above. The major sections of
[I-D.ietf-ippm-initial-registry] provide an example in HTML form
(sections 4 and above).
7.1.4. Description 7.1.4. Description
A Registered Performance Metric description is a written A Registered Performance Metric description is a written
representation of a particular Performance Metrics Registry entry. representation of a particular Performance Metrics Registry entry.
It supplements the Registered Performance Metric name to help It supplements the Registered Performance Metric name to help
Performance Metrics Registry users select relevant Registered Performance Metrics Registry users select relevant Registered
Performance Metrics. Performance Metrics.
7.2. Metric Definition Category 7.2. Metric Definition Category
skipping to change at page 14, line 15 skipping to change at page 14, line 21
Where referenced metrics supply a list of Parameters as part of their Where referenced metrics supply a list of Parameters as part of their
descriptive template, a sub-set of the Parameters will be designated descriptive template, a sub-set of the Parameters will be designated
as Fixed Parameters. For example, for active metrics, Fixed as Fixed Parameters. For example, for active metrics, Fixed
Parameters determine most or all of the IPPM Framework convention Parameters determine most or all of the IPPM Framework convention
"packets of Type-P" as described in [RFC2330], such as transport "packets of Type-P" as described in [RFC2330], such as transport
protocol, payload length, TTL, etc. An example for passive metrics protocol, payload length, TTL, etc. An example for passive metrics
is for RTP packet loss calculation that relies on the validation of a is for RTP packet loss calculation that relies on the validation of a
packet as RTP which is a multi-packet validation controlled by packet as RTP which is a multi-packet validation controlled by
MIN_SEQUENTIAL as defined by [RFC3550]. Varying MIN_SEQUENTIAL MIN_SEQUENTIAL as defined by [RFC3550]. Varying MIN_SEQUENTIAL
values can alter the loss report and this value could be set as a values can alter the loss report and this value could be set as a
Fixed Parameter Fixed Parameter.
In any case, Parameters MUST have well defined names. For Human Parameters MUST have well defined names. For human readers, the
readers, the hanging indent style will work, and the names and hanging indent style is preferred, and the names and definitions that
definitions that do not appear in the Reference Method Specification do not appear in the Reference Method Specification MUST appear in
should appear in this column this column.
Parameters MUST have a well-specified data format.
A Parameter which is a Fixed Parameter for one Performance Metrics A Parameter which is a Fixed Parameter for one Performance Metrics
Registry entry may be designated as a Run-time Parameter for another Registry entry may be designated as a Run-time Parameter for another
Performance Metrics Registry entry. Performance Metrics Registry entry.
7.3. Method of Measurement Category 7.3. Method of Measurement Category
This category includes columns for references to relevant sections of This category includes columns for references to relevant sections of
the RFC(s) and any supplemental information needed to ensure an the RFC(s) and any supplemental information needed to ensure an
unambiguous method for implementations. unambiguous method for implementations.
skipping to change at page 14, line 42 skipping to change at page 15, line 5
7.3.1. Reference Method 7.3.1. Reference Method
This entry provides references to relevant sections of the RFC(s) This entry provides references to relevant sections of the RFC(s)
describing the method of measurement, as well as any supplemental describing the method of measurement, as well as any supplemental
information needed to ensure unambiguous interpretation for information needed to ensure unambiguous interpretation for
implementations referring to the RFC text. implementations referring to the RFC text.
Specifically, this section should include pointers to pseudocode or Specifically, this section should include pointers to pseudocode or
actual code that could be used for an unambigious implementation. actual code that could be used for an unambigious implementation.
7.3.2. Packet Generation Stream 7.3.2. Packet Stream Generation
This column applies to Performance Metrics that generate traffic for This column applies to Performance Metrics that generate traffic for
a part of their Measurement Method purposes including but not a part of their Measurement Method purposes including but not
necessarily limited to Active metrics. The generated traffic is necessarily limited to Active metrics. The generated traffic is
referred as stream and this columns describe its characteristics. referred as stream and this columns describe its characteristics.
Each entry for this column contains the following information: Each entry for this column contains the following information:
o Value: The name of the packet stream scheduling discipline o Value: The name of the packet stream scheduling discipline
o Reference: the specification where the stream is defined o Reference: the specification where the stream is defined
The packet generation stream may require parameters such as the the The packet generation stream may require parameters such as the the
average packet rate and distribution truncation value for streams average packet rate and distribution truncation value for streams
with Poisson-distributed inter-packet sending times. In case such with Poisson-distributed inter-packet sending times. In case such
parameters are needed, they should be included either in the Fixed parameters are needed, they should be included either in the Fixed
parameter column or in the run time parameter column, depending on parameter column or in the run time parameter column, depending on
wether they will be fixed or will be an input for the metric. wether they will be fixed or will be an input for the metric.
The simplest example of stream specification is Singleton scheduling The simplest example of stream specification is Singleton scheduling
skipping to change at page 16, line 44 skipping to change at page 17, line 9
for the context to be complete. However, the values of these for the context to be complete. However, the values of these
parameters is not specified in the Performance Metrics Registry (like parameters is not specified in the Performance Metrics Registry (like
the Fixed Parameters), rather these parameters are listed as an aid the Fixed Parameters), rather these parameters are listed as an aid
to the measurement system implementer or user (they must be left as to the measurement system implementer or user (they must be left as
variables, and supplied on execution). variables, and supplied on execution).
Where metrics supply a list of Parameters as part of their Where metrics supply a list of Parameters as part of their
descriptive template, a sub-set of the Parameters will be designated descriptive template, a sub-set of the Parameters will be designated
as Run-Time Parameters. as Run-Time Parameters.
Parameters MUST have well defined names. For Human readers, the Parameters MUST have well defined names. For human readers, the
hanging indent style will work, and the names and definitions that do hanging indent style is preferred, and the names and definitions that
not appear in the Reference Method Specification should appear in do not appear in the Reference Method Specification MUST appear in
this column. this column.
A Data Format for each Run-time Parameter MUST be specified in this A Data Format for each Run-time Parameter MUST be specified in this
column, to simplify the control and implementation of measurement column, to simplify the control and implementation of measurement
devices. For example, parameters that include an IPv4 address can be devices. For example, parameters that include an IPv4 address can be
encoded as a 32 bit integer (i.e. binary base64 encoded value) or ip- encoded as a 32 bit integer (i.e. binary base64 encoded value) or ip-
address as defined in [RFC6991]. The actual encoding(s) used must be address as defined in [RFC6991]. The actual encoding(s) used must be
explicitly defined for each Run-time parameter. explicitly defined for each Run-time parameter. IPv6 addresses and
options MUST be accomodated, allowing Registered Metrics to be used
in either address family.
Examples of Run-time Parameters include IP addresses, measurement Examples of Run-time Parameters include IP addresses, measurement
point designations, start times and end times for measurement, and point designations, start times and end times for measurement, and
other information essential to the method of measurement. other information essential to the method of measurement.
7.3.6. Role 7.3.6. Role
In some method of measurements, there may be several roles defined In some method of measurements, there may be several roles defined
e.g. on a one-way packet delay active measurement, there is one e.g. on a one-way packet delay active measurement, there is one
measurement agent that generates the packets and the other one that measurement agent that generates the packets and the other one that
skipping to change at page 17, line 35 skipping to change at page 18, line 7
For entries which involve a stream and many singleton measurements, a For entries which involve a stream and many singleton measurements, a
statistic may be specified in this column to summarize the results to statistic may be specified in this column to summarize the results to
a single value. If the complete set of measured singletons is a single value. If the complete set of measured singletons is
output, this will be specified here. output, this will be specified here.
Some metrics embed one specific statistic in the reference metric Some metrics embed one specific statistic in the reference metric
definition, while others allow several output types or statistics. definition, while others allow several output types or statistics.
7.4.1. Type 7.4.1. Type
This column contain the name of the output type. The output type This column contains the name of the output type. The output type
defines the type of result that the metric produces. It can be the defines a single type of result that the metric produces. It can be
raw results or it can be some form of statistic. The specification the raw results (packet send times and singleton metrics), or it can
of the output type must define the format of the output. In some be a summary statistic. The specification of the output type MUST
systems, format specifications will simplify both measurement define the format of the output. In some systems, format
implementation and collection/storage tasks. Note that if two specifications will simplify both measurement implementation and
different statistics are required from a single measurement (for collection/storage tasks. Note that if two different statistics are
example, both "Xth percentile mean" and "Raw"), then a new output required from a single measurement (for example, both "Xth percentile
type must be defined ("Xth percentile mean AND Raw"). mean" and "Raw"), then a new output type must be defined ("Xth
percentile mean AND Raw").
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 where the output
type is defined type is 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.
skipping to change at page 25, line 49 skipping to change at page 26, line 23
[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] [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-01 (work in progress), September 2015. active-passive-06 (work in progress), January 2016.
[I-D.ietf-ippm-initial-registry]
Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,
"Initial Performance Metric Registry Entries", draft-ietf-
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
Marcelo Bagnulo Marcelo Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad 30 Av. Universidad 30
 End of changes. 29 change blocks. 
59 lines changed or deleted 74 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/