< draft-ietf-ippm-metric-registry-04.txt   draft-ietf-ippm-metric-registry-05.txt >
Network Working Group M. Bagnulo Network Working Group M. Bagnulo
Internet-Draft UC3M Internet-Draft UC3M
Intended status: Best Current Practice B. Claise Intended status: Best Current Practice B. Claise
Expires: January 21, 2016 Cisco Systems, Inc. Expires: April 20, 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
July 20, 2015 October 18, 2015
Registry for Performance Metrics Registry for Performance Metrics
draft-ietf-ippm-metric-registry-04 draft-ietf-ippm-metric-registry-05
Abstract Abstract
This document defines the IANA Registry for Performance Metrics. This document defines the format for the Performance Metrics registry
This document also gives a set of guidelines for Registered and defines the IANA Registry for Performance Metrics. This document
Performance Metric requesters and reviewers. also gives a set of guidelines for Registered Performance Metric
requesters and reviewers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at 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 January 21, 2016. This Internet-Draft will expire on April 20, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 15 skipping to change at page 2, line 16
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Motivation for a Performance Metrics Registry . . . . . . . . 6 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 . . . . 7 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 . . . . . . . . . . . . . . 9 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. URI . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 13
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 Generation Stream . . . . . . . . . . . . . . 14
7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 15 7.3.3. Traffic Filter . . . . . . . . . . . . . . . . . . . 15
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 15 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 16
7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 16 7.3.5. Run-time Parameters . . . . . . . . . . . . . . . . . 16
7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 16 7.3.6. Role . . . . . . . . . . . . . . . . . . . . . . . . 17
7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 16 7.4. Output Category . . . . . . . . . . . . . . . . . . . . . 17
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 17 7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 17
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 17 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 17
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 17 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 18
7.5. Administrative information . . . . . . . . . . . . . . . 17 7.5. Administrative information . . . . . . . . . . . . . . . 18
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 17 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 18
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 17 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 18
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 17 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 18
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 18 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 18
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 18 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 18
8. The Life-Cycle of Registered Performance Metrics . . . . . . 18 8. The Life-Cycle of Registered Performance Metrics . . . . . . 18
8.1. Adding new Performance Metrics to the Performance Metrics 8.1. Adding new Performance Metrics to the Performance Metrics
Registry . . . . . . . . . . . . . . . . . . . . . . . . 18 Registry . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2. Revising Registered Performance Metrics . . . . . . . . . 19 8.2. Revising Registered Performance Metrics . . . . . . . . . 19
8.3. Deprecating Registered Performance Metrics . . . . . . . 20 8.3. Deprecating Registered Performance Metrics . . . . . . . 21
9. Security considerations . . . . . . . . . . . . . . . . . . . 21 9. Security considerations . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
12.1. Normative References . . . . . . . . . . . . . . . . . . 22 12.1. Normative References . . . . . . . . . . . . . . . . . . 22
12.2. Informative References . . . . . . . . . . . . . . . . . 23 12.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 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
various working groups (WG), most notably: various working groups (WG), most notably:
skipping to change at page 4, line 18 skipping to change at page 4, line 18
act on) a particular Performance Metric, then both parties have act on) a particular Performance Metric, then both parties have
exactly the same understanding of what Performance Metric is being exactly the same understanding of what Performance Metric is being
referred to. Second, how to discover which Performance Metrics have referred to. Second, how to discover which Performance Metrics have
been specified, so as to avoid developing new Performance Metric that been specified, so as to avoid developing new Performance Metric that
is very similar, but not quite inter-operable. The problems can be is very similar, but not quite inter-operable. The problems can be
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 creates an IANA-maintained Performance This document therefore requests that IANA create and maintain a
Metrics Registry. It also provides best practices on how to specify Performance Metrics Registry, according to the maintenance procedures
new entries or update ones in the Performance Metrics Registry. and the Performance Metrics Registry format defined in this memo.
Although the Registry format is primarily for use by IANA, any other
organization that wishes to create a Performance Metrics Registry MAY
use the format for its purposes. The authors make no guarantee of
the format's applicability to any possible set of Performance Metrics
envisaged by other organizations. In the rest of this document,
unless we explicitly say so, we will refer to the IANA-maintained
Performance 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 11 skipping to change at page 6, line 20
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]. [I-D.ietf-ippm-active-passive].
3. Scope 3. Scope
This document is meant 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
including the publication of one or more RFCs or I-Ds describing it). including the publication of one or more RFCs or I-Ds describing it).
For the appointed Performance Metrics Experts and for IANA personnel For the appointed Performance Metrics Experts and for IANA personnel
administering the new IANA Performance Metric Registry, it defines a administering the new IANA Performance Metric Registry, it defines a
set of acceptance criteria against which these proposed Registered set of acceptance criteria against which these proposed Registered
Performance Metrics should be evaluated. Performance Metrics should be evaluated. In addition, this document
may be useful for other organization who are defining a Performance
Metric registry of its own, who can rely on the Performance Metric
registry defined in this document.
This Performance Metric Registry is applicable to Performance Metrics This Performance Metric Registry is applicable to Performance Metrics
issued from Active Measurement, Passive Measurement, and any other issued from Active Measurement, Passive Measurement, and any other
form of Performance Metric. This registry is designed to encompass form of Performance Metric. This registry is designed to encompass
Performance Metrics developed throughout the IETF and especially for Performance Metrics developed throughout the IETF and especially for
the technologies specified in the following working groups: IPPM, the technologies specified in the following working groups: IPPM,
XRBLOCK, IPFIX, and BMWG. This document analyzes an prior attempt to XRBLOCK, IPFIX, and BMWG. This document analyzes an prior attempt to
set up a Performance Metric Registry, and the reasons why this design set up a Performance Metric Registry, and the reasons why this design
was inadequate [RFC6248]. Finally, this document gives a set of was inadequate [RFC6248]. Finally, this document gives a set of
guidelines for requesters and expert reviewers of candidate guidelines for requesters and expert reviewers of candidate
skipping to change at page 7, line 17 skipping to change at page 7, line 25
As any IETF registry, the primary use for a registry is to manage a As any IETF registry, the primary use for a registry is to manage a
namespace for its use within one or more protocols. In the namespace for its use within one or more protocols. In the
particular case of the Performance Metric Registry, there are two particular case of the Performance Metric Registry, there are two
types of protocols that will use the Performance Metrics in the types of protocols that will use the Performance Metrics in the
Performance Metrics Registry during their operation (by referring to Performance Metrics Registry during their operation (by referring to
the Index values): the Index values):
o Control protocol: this type of protocols is used to allow one o Control protocol: this type of protocols is used to allow one
entity to request another entity to perform a measurement using a entity to request another entity to perform a measurement using a
specific metric defined by the Performance Metrics Registry. One specific metric defined by the Performance Metrics Registry. One
particular example is the LMAP framework particular example is the LMAP framework [RFC7594]. Using the
[I-D.ietf-lmap-framework]. Using the LMAP terminology, the LMAP terminology, the Performance Metrics Registry is used in the
Performance Metrics Registry is used in the LMAP Control protocol LMAP Control protocol to allow a Controller to request a
to allow a Controller to request a measurement task to one or more measurement task to one or more Measurement Agents. In order to
Measurement Agents. In order to enable this use case, the entries enable this use case, the entries of the Performance Metric
of the Performance Metric Registry must be well enough defined to Registry must be well enough defined to allow a Measurement Agent
allow a Measurement Agent implementation to trigger a specific implementation to trigger a specific measurement task upon the
measurement task upon the reception of a control protocol message. reception of a control protocol message. This requirement heavily
This requirement heavily constrains the type of entries that are constrains the type of entries that are acceptable for the
acceptable for the Performance Metric Registry. Performance Metric Registry.
o Report protocol: This type of protocols is used to allow an entity o Report protocol: This type of protocols is used to allow an entity
to report measurement results to another entity. By referencing to report measurement results to another entity. By referencing
to a specific Performance Metric Registry, it is possible to to a specific Performance Metric Registry, it is possible to
properly characterize the measurement result data being reported. properly characterize the measurement result data being reported.
Using the LMAP terminology, the Performance Metrics Registry is Using the LMAP terminology, the Performance Metrics Registry is
used in the Report protocol to allow a Measurement Agent to report used in the Report protocol to allow a Measurement Agent to report
measurement results to a Collector. measurement results to a Collector.
It should be noted that the LMAP framework explicitly allows for
using not only the IANA-maintained Performance Metrics Registry but
also other registries containing Performance Metrics, either defined
by other organizations or private ones. However, others who are
creating Registries to be used in the context of an LMAP framework
are encouraged to use the Registry format defined in this document,
because this makes it easier for developers of LMAP Measurement
Agents (MAs) to programmatically use information found in those other
Registries' entries.
4.2. Single point of reference for Performance Metrics 4.2. Single point of reference for Performance Metrics
A Performance Metrics Registry serves as a single point of reference A Performance Metrics Registry serves as a single point of reference
for Performance Metrics defined in different working groups in the for Performance Metrics defined in different working groups in the
IETF. As we mentioned earlier, there are several WGs that define IETF. As we mentioned earlier, there are several WGs that define
Performance Metrics in the IETF and it is hard to keep track of all Performance Metrics in the IETF and it is hard to keep track of all
them. This results in multiple definitions of similar Performance them. This results in multiple definitions of similar Performance
Metrics that attempt to measure the same phenomena but in slightly Metrics that attempt to measure the same phenomena but in slightly
different (and incompatible) ways. Having a registry would allow different (and incompatible) ways. Having a registry would allow
both the IETF community and external people to have a single list of both the IETF community and external people to have a single list of
skipping to change at page 13, line 7 skipping to change at page 13, line 7
the mean as output. 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. URI
The URIs column MUST contain a URI [RFC 3986] that uniquely The URIs column MUST contain a URI [RFC3986] that uniquely identifies
identifies the metric. This URI is a URN [RFC 2141]. The URI is the metric. This URI is a URN [RFC2141]. The URI is automatically
automatically generated by prepending the prefix generated by prepending the prefix urn:ietf:params:ippm:metric: to
urn:ietf:params:ippm:metric: to the metric name. The resulting URI the metric name. The resulting URI is globally unique.
is globally unique.
The URIs column MUST contain a second URI which is a URL [RFC 3986] 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 exact composition of each accessible through the Internet. The URL points to a file containing
metric URL will be determined by IANA, but there will be some overlap the information of exactly one registry entry. The separate files
with the URN described above. for different entries can be more easily edited and re-used when
preparing new entries. The exact composition of each metric URL will
be determined by IANA, but there will be some overlap with the URN
described 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 13, line 47 skipping to change at page 13, line 49
This entry provides a reference (or references) to the relevant This entry provides a reference (or references) to the relevant
section(s) of the document(s) that define the metric, as well as any section(s) of the document(s) that define the metric, as well as any
supplemental information needed to ensure an unambiguous definition supplemental information needed to ensure an unambiguous definition
for implementations. The reference needs to be an immutable for implementations. The reference needs to be an immutable
document, such as an RFC; for other standards bodies, it is likely to document, such as an RFC; for other standards bodies, it is likely to
be necessary to reference a specific, dated version of a be necessary to reference a specific, dated version of a
specification. specification.
7.2.2. Fixed Parameters 7.2.2. Fixed Parameters
Fixed Parameters are Paremeters whose value must be specified in the Fixed Parameters are Parameters whose value must be specified in the
Performance Metrics Registry. The measurement system uses these Performance Metrics Registry. The measurement system uses these
values. values.
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
readers, the hanging indent style will work, and the names and
definitions that do not appear in the Reference Method Specification
should appear in this column
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 44 skipping to change at page 15, line 4
7.3.2. Packet Generation Stream 7.3.2. Packet Generation Stream
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 Stream Parameters: The values and formats of input factors for The packet generation stream may require parameters such as the the
each type of stream. For example, the average packet rate and average packet rate and distribution truncation value for streams
distribution truncation value for streams with Poisson-distributed with Poisson-distributed inter-packet sending times. In case such
inter-packet sending times. parameters are needed, they should be included either in the Fixed
parameter column or in the run time parameter column, depending on
wether they will be fixed or will be an input for the metric.
o Reference: the specification where the stream is defined
The simplest example of stream specification is Singleton scheduling The simplest example of stream specification is Singleton scheduling
(see [RFC2330]), where a single atomic measurement is conducted. (see [RFC2330]), where a single atomic measurement is conducted.
Each atomic measurement could consist of sending a single packet Each atomic measurement could consist of sending a single packet
(such as a DNS request) or sending several packets (for example, to (such as a DNS request) or sending several packets (for example, to
request a webpage). Other streams support a series of atomic request a webpage). Other streams support a series of atomic
measurements in a "sample", with a schedule defining the timing measurements in a "sample", with a schedule defining the timing
between each transmitted packet and subsequent measurement. between each transmitted packet and subsequent measurement.
Principally, two different streams are used in IPPM metrics, Poisson Principally, two different streams are used in IPPM metrics, Poisson
distributed as described in [RFC2330] and Periodic as described in distributed as described in [RFC2330] and Periodic as described in
[RFC3432]. Both Poisson and Periodic have their own unique [RFC3432]. Both Poisson and Periodic have their own unique
parameters, and the relevant set of values is specified in this parameters, and the relevant set of parameters names and values
column. should be included either in the Fixed Parameters column or in the
Run-time parameter column.
7.3.3. Traffic Filter 7.3.3. Traffic Filter
This column applies to Performance Metrics that observe packets This column applies to Performance Metrics that observe packets
flowing through (the device with) the measurement agent i.e. that is flowing through (the device with) the measurement agent i.e. that is
not necessarily addressed to the measurement agent. This includes not necessarily addressed to the measurement agent. This includes
but is not limited to Passive Metrics. The filter specifies the but is not limited to Passive Metrics. The filter specifies the
traffic that is measured. This includes protocol field values/ traffic that is measured. This includes protocol field values/
ranges, such as address ranges, and flow or session identifiers. ranges, such as address ranges, and flow or session identifiers.
skipping to change at page 16, line 4 skipping to change at page 16, line 14
7.3.4. Sampling Distribution 7.3.4. Sampling Distribution
The sampling distribution defines out of all the packets that match The sampling distribution defines out of all the packets that match
the traffic filter, which one of those are actually used for the the traffic filter, which one of those are actually used for the
measurement. One possibility is "all" which implies that all packets measurement. One possibility is "all" which implies that all packets
matching the Traffic filter are considered, but there may be other matching the Traffic filter are considered, but there may be other
sampling strategies. It includes the following information: sampling strategies. It includes the following information:
Value: the name of the sampling distribution Value: the name of the sampling distribution
Parameters: if any.
Reference definition: pointer to the specification where the Reference definition: pointer to the specification where the
sampling distribution is properly defined. sampling distribution is properly defined.
The sampling distribution may require parameters. In case such
parameters are needed, they should be included either in the Fixed
parameter column or in the run time parameter column, depending on
wether they will be fixed or will be an input for the metric.
Sampling and Filtering Techniques for IP Packet Selection are Sampling and Filtering Techniques for IP Packet Selection are
documented in the PSAMP (Packet Sampling) [RFC5475], while the documented in the PSAMP (Packet Sampling) [RFC5475], while the
Framework for Packet Selection and Reporting, [RFC5474] provides more Framework for Packet Selection and Reporting, [RFC5474] provides more
background information. The sampling distribution parameters might background information. The sampling distribution parameters might
be expressed in terms of the Information Model for Packet Sampling be expressed in terms of the Information Model for Packet Sampling
Exports, [RFC5477], and the Flow Selection Techniques, [RFC7014]. Exports, [RFC5477], and the Flow Selection Techniques, [RFC7014].
7.3.5. Run-time Parameters 7.3.5. Run-time Parameters
Run-Time Parameters are Parameters that must be determined, Run-Time Parameters are Parameters that must be determined,
skipping to change at page 16, line 30 skipping to change at page 16, line 44
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
hanging indent style will work, and the names and definitions that do
not appear in the Reference Method Specification should appear in
this column.
A Data Format for each Run-time Parameter MUST be specified in this
column, to simplify the control and implementation of measurement
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-
address as defined in [RFC6991]. The actual encoding(s) used must be
explicitly defined for each Run-time parameter.
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
receives the packets. This column contains the name of the role for receives the packets. This column contains the name of the role for
skipping to change at page 22, line 16 skipping to change at page 22, line 42
use. The name starting with the prefix Priv- are reserved for use. The name starting with the prefix Priv- are reserved for
private use. private use.
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. some brainstorming sessions on this topic. Thanks to Barbara Stark
and Juergen Schoenwaelder for the detailed feedback and suggestions.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<http://www.rfc-editor.org/info/rfc2026>. <http://www.rfc-editor.org/info/rfc2026>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 25, line 14 skipping to change at page 25, line 40
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012, for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013, DOI 10.17487/RFC7012, September 2013,
<http://www.rfc-editor.org/info/rfc7012>. <http://www.rfc-editor.org/info/rfc7012>.
[RFC7014] D'Antonio, S., Zseby, T., Henke, C., and L. Peluso, "Flow [RFC7014] D'Antonio, S., Zseby, T., Henke, C., and L. Peluso, "Flow
Selection Techniques", RFC 7014, DOI 10.17487/RFC7014, Selection Techniques", RFC 7014, DOI 10.17487/RFC7014,
September 2013, <http://www.rfc-editor.org/info/rfc7014>. September 2013, <http://www.rfc-editor.org/info/rfc7014>.
[I-D.ietf-lmap-framework] [RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
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)", draft-ietf- DOI 10.17487/RFC7594, September 2015,
lmap-framework-14 (work in progress), April 2015. <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-00 (work in progress), June 2015. active-passive-01 (work in progress), September 2015.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013,
<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
Leganes, Madrid 28911 Leganes, Madrid 28911
SPAIN SPAIN
Phone: 34 91 6249500 Phone: 34 91 6249500
 End of changes. 34 change blocks. 
63 lines changed or deleted 117 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/