draft-ietf-ippm-metric-registry-23.txt   draft-ietf-ippm-metric-registry-24.txt 
Network Working Group M. Bagnulo Network Working Group M. Bagnulo
Internet-Draft UC3M Internet-Draft UC3M
Intended status: Standards Track B. Claise Intended status: Standards Track B. Claise
Expires: June 13, 2020 Cisco Systems, Inc. Expires: September 10, 2020 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
December 11, 2019 March 9, 2020
Registry for Performance Metrics Registry for Performance Metrics
draft-ietf-ippm-metric-registry-23 draft-ietf-ippm-metric-registry-24
Abstract Abstract
This document defines the format for the IANA Performance Metrics This document defines the format for the IANA Performance Metrics
Registry. This document also gives a set of guidelines for Registry. This document also gives a set of guidelines for
Registered Performance Metric requesters and reviewers. 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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 13, 2020. This Internet-Draft will expire on September 10, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 26 skipping to change at page 2, line 26
4.1. Interoperability . . . . . . . . . . . . . . . . . . . . 8 4.1. Interoperability . . . . . . . . . . . . . . . . . . . . 8
4.2. Single point of reference for Performance Metrics . . . . 9 4.2. Single point of reference for Performance Metrics . . . . 9
4.3. Side benefits . . . . . . . . . . . . . . . . . . . . . . 9 4.3. Side benefits . . . . . . . . . . . . . . . . . . . . . . 9
5. Criteria for Performance Metrics Registration . . . . . . . . 9 5. Criteria for Performance Metrics Registration . . . . . . . . 9
6. Performance Metric Registry: Prior attempt . . . . . . . . . 10 6. Performance Metric Registry: Prior attempt . . . . . . . . . 10
6.1. Why this Attempt Should Succeed . . . . . . . . . . . . . 11 6.1. Why this Attempt Should Succeed . . . . . . . . . . . . . 11
7. Definition of the Performance Metric Registry . . . . . . . . 11 7. Definition of the Performance Metric Registry . . . . . . . . 11
7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 13 7.1. Summary Category . . . . . . . . . . . . . . . . . . . . 13
7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 13 7.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 13
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 17 7.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 17 7.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 17
7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 17 7.1.6. Change Controller . . . . . . . . . . . . . . . . . . 17
7.1.7. Version (of Registry Format) . . . . . . . . . . . . 18 7.1.7. Version (of Registry Format) . . . . . . . . . . . . 18
7.2. Metric Definition Category . . . . . . . . . . . . . . . 18 7.2. Metric Definition Category . . . . . . . . . . . . . . . 18
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 18 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 18
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18
7.3. Method of Measurement Category . . . . . . . . . . . . . 19 7.3. Method of Measurement Category . . . . . . . . . . . . . 19
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19
7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19
skipping to change at page 3, line 9 skipping to change at page 3, line 9
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 24 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 24
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 24 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 24
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 24 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 24
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 24 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 24
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 24 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 24
8. Processes for Managing the Performance Metric Registry Group 24 8. Processes for Managing the Performance Metric Registry Group 24
8.1. Adding new Performance Metrics to the Performance Metrics 8.1. Adding new Performance Metrics to the Performance Metrics
Registry . . . . . . . . . . . . . . . . . . . . . . . . 25 Registry . . . . . . . . . . . . . . . . . . . . . . . . 25
8.2. Revising Registered Performance Metrics . . . . . . . . . 26 8.2. Revising Registered Performance Metrics . . . . . . . . . 26
8.3. Deprecating Registered Performance Metrics . . . . . . . 27 8.3. Deprecating Registered Performance Metrics . . . . . . . 28
9. Security considerations . . . . . . . . . . . . . . . . . . . 28 9. Security considerations . . . . . . . . . . . . . . . . . . . 28
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
10.1. Registry Group . . . . . . . . . . . . . . . . . . . . . 29 10.1. Registry Group . . . . . . . . . . . . . . . . . . . . . 29
10.2. Performance Metric Name Elements . . . . . . . . . . . . 29 10.2. Performance Metric Name Elements . . . . . . . . . . . . 29
10.3. New Performance Metrics Registry . . . . . . . . . . . . 30 10.3. New Performance Metrics Registry . . . . . . . . . . . . 30
11. Blank Registry Template . . . . . . . . . . . . . . . . . . . 31 11. Blank Registry Template . . . . . . . . . . . . . . . . . . . 32
11.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 32 11.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 32
11.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 32 11.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 32
11.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 32 11.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 32
11.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 32 11.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 32
11.1.4. Description . . . . . . . . . . . . . . . . . . . . 32 11.1.4. Description . . . . . . . . . . . . . . . . . . . . 32
11.1.5. Change Controller . . . . . . . . . . . . . . . . . 32 11.1.5. Change Controller . . . . . . . . . . . . . . . . . 32
11.1.6. Version (of Registry Format) . . . . . . . . . . . . 32 11.1.6. Version (of Registry Format) . . . . . . . . . . . . 32
11.2. Metric Definition . . . . . . . . . . . . . . . . . . . 32 11.2. Metric Definition . . . . . . . . . . . . . . . . . . . 32
11.2.1. Reference Definition . . . . . . . . . . . . . . . . 32 11.2.1. Reference Definition . . . . . . . . . . . . . . . . 32
11.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 32 11.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 32
11.3. Method of Measurement . . . . . . . . . . . . . . . . . 33 11.3. Method of Measurement . . . . . . . . . . . . . . . . . 33
11.3.1. Reference Method . . . . . . . . . . . . . . . . . . 33 11.3.1. Reference Method . . . . . . . . . . . . . . . . . . 33
11.3.2. Packet Stream Generation . . . . . . . . . . . . . . 33 11.3.2. Packet Stream Generation . . . . . . . . . . . . . . 33
11.3.3. Traffic Filtering (observation) Details . . . . . . 33 11.3.3. Traffic Filtering (observation) Details . . . . . . 33
skipping to change at page 8, line 31 skipping to change at page 8, line 31
the particular case of the Performance Metrics Registry, there are the particular case of the Performance Metrics Registry, there are
two types of protocols that will use the Performance Metrics in the two 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 protocol used to allow one entity o Control protocol: This type of protocol used to allow one entity
to request another entity to perform a measurement using a 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 [RFC7594]. Using the particular example is the LMAP framework [RFC7594]. Using the
LMAP terminology, the Performance Metrics Registry is used in the LMAP terminology, the Performance Metrics Registry is used in the
LMAP Control protocol to allow a Controller to request a LMAP Control protocol to allow a Controller to schedule a
measurement task to one or more Measurement Agents. In order to measurement task for one or more Measurement Agents. In order to
enable this use case, the entries of the Performance Metrics enable this use case, the entries of the Performance Metrics
Registry must be sufficiently defined to allow a Measurement Agent Registry must be sufficiently defined to allow a Measurement Agent
implementation to trigger a specific measurement task upon the implementation to trigger a specific measurement task upon the
reception of a control protocol message. This requirement heavily reception of a control protocol message. This requirement heavily
constrains the type of entries that are acceptable for the constrains the type of entries that are acceptable for the
Performance Metrics Registry. Performance Metrics Registry.
o Report protocol: This type of protocol is used to allow an entity o Report protocol: This type of protocol 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 Metrics Registry, it is possible to to a specific Performance Metrics Registry, it is possible to
skipping to change at page 11, line 28 skipping to change at page 11, line 28
too generic to be useful. This document specifies stricter criteria too generic to be useful. This document specifies stricter criteria
for performance metric registration (see section 5), and imposes a for performance metric registration (see section 5), and imposes a
group of Performance Metrics Experts that will provide guidelines to group of Performance Metrics Experts that will provide guidelines to
assess if a Performance Metric is properly specified. assess if a Performance Metric is properly specified.
Another key difference between this attempt and the previous one is Another key difference between this attempt and the previous one is
that in this case there is at least one clear user for the that in this case there is at least one clear user for the
Performance Metrics Registry: the LMAP framework and protocol. Performance Metrics Registry: the LMAP framework and protocol.
Because the LMAP protocol will use the Performance Metrics Registry Because the LMAP protocol will use the Performance Metrics Registry
values in its operation, this actually helps to determine if a metric values in its operation, this actually helps to determine if a metric
is properly defined. is properly defined. In particular, since we expect that the LMAP
control protocol will enable a controller to request a measurement
In particular, since we expect that the LMAP control protocol will agent to perform a measurement using a given metric by embedding the
enable a controller to request a measurement agent to perform a Performance Metrics Registry identifier in the protocol. Such a
measurement using a given metric by embedding the Performance Metrics metric and method are properly specified if they are defined well-
Registry identifier in the protocol. Such a metric and method are enough so that it is possible (and practical) to implement them in
properly specified if they are defined well-enough so that it is the measurement agent. This was the failure of the previous attempt:
possible (and practical) to implement them in the measurement agent. a registry entry with an undefined Type-P (section 13 of RFC 2330
This was the failure of the previous attempt: a registry entry with [RFC2330]) allows implementation to be ambiguous.
an undefined Type-P (section 13 of RFC 2330 [RFC2330]) allows
implementation to be ambiguous.
7. Definition of the Performance Metric Registry 7. Definition of the Performance Metric Registry
This Performance Metrics Registry is applicable to Performance This Performance Metrics Registry is applicable to Performance
Metrics used for Active Measurement, Passive Measurement, and any Metrics used for Active Measurement, Passive Measurement, and any
other form of Performance Measurement. Each category of measurement other form of Performance Measurement. Each category of measurement
has unique properties, so some of the columns defined below are not has unique properties, so some of the columns defined below are not
applicable for a given metric category. In this case, the column(s) applicable for a given metric category. In this case, the column(s)
SHOULD be populated with the "NA" value (Non Applicable). However, SHOULD be populated with the "NA" value (Non Applicable). However,
the "NA" value MUST NOT be used by any metric in the following the "NA" value MUST NOT be used by any metric in the following
columns: Identifier, Name, URI, Status, Requester, Revision, Revision columns: Identifier, Name, URI, Status, Requester, Revision, Revision
Date, Description. In the future, a new category of metrics could Date, Description. In the future, a new category of metrics could
require additional columns, and adding new columns is a recognized require additional columns, and adding new columns is a recognized
form of registry extension. The specification defining the new form of registry extension. The specification defining the new
column(s) MUST give guidelines to populate the new column(s) for column(s) MUST give general guidelines for populating the new
existing entries (in general). column(s) for existing entries.
The columns of the Performance Metrics Registry are defined below. The columns of the Performance Metrics 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.
======================================================================= =======================================================================
Legend: Legend:
Registry Categories and Columns are shown below as: Registry Categories and Columns are shown below as:
Category Category
------------------... ------------------...
Column | Column |... Column | Column |...
======================================================================= =======================================================================
Summary Summary
------------------------------------------------------------------------ ------------------------------------------------------------------------
Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver | Identifier | Name | URI | 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 |
skipping to change at page 13, line 4 skipping to change at page 12, line 48
----------------------------------------- -----------------------------------------
Type | Reference | Units | Calibration | Type | Reference | Units | Calibration |
| Definition | | | | Definition | | |
Administrative Information Administrative Information
------------------------------------ ------------------------------------
Status |Requester | Rev | Rev.Date | Status |Requester | Rev | Rev.Date |
Comments and Remarks Comments and Remarks
-------------------- --------------------
There is a blank template of the Registry template provided in
Section 11 of this memo.
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 Metrics Registry. identifier MUST be unique within the Performance Metrics Registry.
The Registered Performance Metric unique identifier is an unbounded The Registered Performance Metric unique identifier is an unbounded
integer (range 0 to infinity). integer (range 0 to infinity).
skipping to change at page 15, line 28 skipping to change at page 15, line 28
of octets in the Payload)) of octets in the Payload))
SustainedBurst (Capacity test, worst case) SustainedBurst (Capacity test, worst case)
StandingQueue (test of bottleneck queue behavior) StandingQueue (test of bottleneck queue behavior)
SubTypeMethod values are separated by a hyphen "-" character, SubTypeMethod values are separated by a hyphen "-" character,
which indicates that they belong to this element, and that their which indicates that they belong to this element, and that their
order is unimportant when considering name uniqueness. order is unimportant when considering name uniqueness.
o Spec: an immutable document, for RFCs, the RFC number and major o Spec: An immutable document identifier combined with a document
section number that specifies this Registry entry in the form section identifier. For RFCs, this consists of the RFC number and
RFCXXXXsecY, such as RFC7799sec3. Note: the RFC number is not the major section number that specifies this Registry entry in the
Primary Reference specification for the metric definition, such as form RFCXXXXsecY, such as RFC7799sec3. Note: the RFC number is
[RFC7679] for One-way Delay; it will contain the placeholder not the Primary Reference specification for the metric definition,
"RFCXXXXsecY" until the RFC number is assigned to the specifying such as [RFC7679] for One-way Delay; it will contain the
document, and would remain blank in private registry entries placeholder "RFCXXXXsecY" until the RFC number is assigned to the
without a corresponding RFC. Anticipating the "RFC10K" problem, specifying document, and would remain blank in private registry
the number of the RFC continues to replace RFCXXXX regardless of entries without a corresponding RFC. Anticipating the "RFC10K"
the number of digits in the RFC number. Anticipating Registry problem, the number of the RFC continues to replace RFCXXXX
Entries from other standards bodies, the form of this Name Element regardless of the number of digits in the RFC number.
MUST be proposed and reviewed for consistency and uniqueness by Anticipating Registry Entries from other standards bodies, the
the Expert Reviewer. form of this Name Element MUST be proposed and reviewed for
consistency and uniqueness by the Expert Reviewer.
o Units: The units of measurement for the output, such as and not o Units: The units of measurement for the output, such as and not
limited to: limited to:
Seconds Seconds
Ratio (unitless) Ratio (unitless)
Percent (value multiplied by 100%)
Percent (value multiplied by 100)
Logical (1 or 0) Logical (1 or 0)
Packets Packets
BPS (Bits per Second) BPS (Bits per Second)
PPS (Packets per Second) PPS (Packets per Second)
EventTotal (for unit-less counts) EventTotal (for unit-less counts)
skipping to change at page 17, line 15 skipping to change at page 17, line 17
RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile
as described in section 4 of [I-D.ietf-ippm-initial-registry]. as described in section 4 of [I-D.ietf-ippm-initial-registry].
Note that private registries following the format described here Note that private registries following the format described here
SHOULD use the prefix "Priv_" on any name to avoid unintended SHOULD use the prefix "Priv_" on any name to avoid unintended
conflicts (further considerations are described in section 10). conflicts (further considerations are described in section 10).
Private registry entries usually have no specifying RFC, thus the Private registry entries usually have no specifying RFC, thus the
Spec: element has no clear interpretation. Spec: element has no clear interpretation.
7.1.3. URIs 7.1.3. URI
The URIs column MUST contain a URL [RFC3986] that uniquely identifies The URIs column MUST contain a URL [RFC3986] that uniquely identifies
and locates the metric entry so it is accessible through the and locates the metric entry so it is accessible through the
Internet. The URL points to a file containing all the human-readable Internet. The URL points to a file containing all the human-readable
information for one registry entry. The URL SHALL reference a target information for one registry entry. The URL SHALL reference a target
file that is HTML-formatted and contains URLs to referenced sections file that is preferably HTML-formatted and contains URLs to
of HTML-ized RFCs, or other reference specifications. These target referenced sections of HTML-ized RFCs, or other reference
files for different entries can be more easily edited and re-used specifications. These target files for different entries can be more
when preparing new entries. The exact form of the URL for each easily edited and re-used when preparing new entries. The exact form
target file will be determined by IANA and reside on "iana.org". The of the URL for each target file, and the target file itself, will be
major sections of [I-D.ietf-ippm-initial-registry] provide an example determined by IANA and reside on "iana.org". The major sections of
of a target file in HTML form (sections 4 and higher). [I-D.ietf-ippm-initial-registry] provide an example of a target file
in HTML form (sections 4 and higher).
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.1.5. Reference 7.1.5. Reference
skipping to change at page 21, line 48 skipping to change at page 21, line 48
do not appear in the Reference Method Specification MUST 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. IPv6 addresses and explicitly defined for each Run-time parameter. IPv6 addresses and
options MUST be accommodated, allowing Registered Metrics to be used options MUST be accommodated, allowing Registered Metrics to be used
in either address family. in that address family. Other address families are permissable.
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 methods of measurement, there may be several roles defined, In some methods of measurement, there may be several roles defined,
e.g., for a one-way packet delay active measurement there is one e.g., for a one-way packet delay active measurement there is one
measurement agent that generates the packets and another agent that measurement agent that generates the packets and another agent that
skipping to change at page 25, line 16 skipping to change at page 25, line 16
Requests to add Registered Performance Metrics in the Performance Requests to add Registered Performance Metrics in the Performance
Metrics Registry SHALL be submitted to IANA, which forwards the Metrics Registry SHALL be submitted to IANA, which forwards the
request to a designated group of experts (Performance Metric Experts) request to a designated group of experts (Performance Metric Experts)
appointed by the IESG; these are the reviewers called for by the appointed by the IESG; these are the reviewers called for by the
Specification Required [RFC8126] policy defined for the Performance Specification Required [RFC8126] policy defined for the Performance
Metrics Registry. The Performance Metric Experts review the request Metrics Registry. The Performance Metric Experts review the request
for such things as compliance with this document, compliance with for such things as compliance with this document, compliance with
other applicable Performance Metric-related RFCs, and consistency other applicable Performance Metric-related RFCs, and consistency
with the currently defined set of Registered Performance Metrics. with the currently defined set of Registered Performance Metrics.
The most efficient path for submission begins with preparation of an
Internet Draft containing the proposed Performance Metrics Registry
entry using the template in Section 11, so that the submission
formatting will benefit from the normal IETF Internet Draft
submission processing (including HTML-ization).
Submission to IANA may be during IESG review (leading to IETF Submission to IANA may be during IESG review (leading to IETF
Standards Action), where an Internet Draft proposes one or more Standards Action), where an Internet Draft proposes one or more
Registered Performance Metrics to be added to the Performance Metrics Registered Performance Metrics to be added to the Performance Metrics
Registry, including the text of the proposed Registered Performance Registry, including the text of the proposed Registered Performance
Metric(s). Metric(s).
If an RFC-to-be includes a Performance Metric and a proposed If an RFC-to-be includes a Performance Metric and a proposed
Performance Metrics Registry entry, but the IANA and Performance Performance Metrics Registry entry, but the Performance Metric Expert
Metric Expert review determines that one or more of the Section 5 review determines that one or more of the Section 5 criteria have not
criteria have not been met, then the proposed Performance Metrics been met, then the proposed Performance Metrics Registry entry MUST
Registry entry MUST be removed from the text. When the RFC-to-be be removed from the text. Once evidence exists that the Performance
authors are ready to show evidence of meeting the criteria in section Metric meets the criteria in section 5, the proposed Performance
5, they SHOULD re-submit the proposed Performance Metrics Registry Metrics Registry entry SHOULD be submitted to IANA to be evaluated in
entry to IANA to be evaluated in consultation with the Performance consultation with the Performance Metric Experts for registration at
Metric Experts for registration at that time. that time.
Authors of proposed Registered Performance Metrics SHOULD review Authors of proposed Registered Performance Metrics SHOULD review
compliance with the specifications in this document to check their compliance with the specifications in this document to check their
submissions before sending them to IANA. submissions before sending them to IANA.
At least one Performance Metric Expert should endeavor to complete At least one Performance Metric Expert should endeavor to complete
referred reviews in a timely manner. If the request is acceptable, referred reviews in a timely manner. If the request is acceptable,
the Performance Metric Experts signify their approval to IANA, and the Performance Metric Experts signify their approval to IANA, and
IANA updates the Performance Metrics Registry. If the request is not IANA updates the Performance Metrics Registry. If the request is not
acceptable, the Performance Metric Experts MAY coordinate with the acceptable, the Performance Metric Experts MAY coordinate with the
skipping to change at page 30, line 34 skipping to change at page 30, line 37
This document specifies the procedure for Performance Metrics This document specifies the procedure for Performance Metrics
Registry setup. IANA is requested to create a new registry for Registry setup. IANA is requested to create a new registry for
Performance Metrics called "Performance Metrics Registry". This Performance Metrics called "Performance Metrics Registry". This
Registry will contain the following Summary columns: Registry will contain the following Summary columns:
Identifier: Identifier:
Name: Name:
URIs: URI:
Description: Description:
Reference: Reference:
Change Controller: Change Controller:
Version: Version:
Descriptions of these columns and additional information found in the Descriptions of these columns and additional information found in the
skipping to change at page 31, line 16 skipping to change at page 31, line 18
available identifier to the new Registered Performance Metric. If a available identifier to the new Registered Performance Metric. If a
Performance Metrics Expert providing review determines that there is Performance Metrics Expert providing review determines that there is
a reason to assign a specific numeric identifier, possibly leaving a a reason to assign a specific numeric identifier, possibly leaving a
temporary gap in the numbering, then the Performance Expert SHALL temporary gap in the numbering, then the Performance Expert SHALL
inform IANA of this decision. inform IANA of this decision.
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 "URIs" column will have a URL to the full template of each The "URI" column will have a URL to the full template of each
registry entry. The Registry Entry text SHALL be HTML-ized to aid registry entry. The Registry Entry text SHALL be HTML-ized to aid
the reader, with links to reference RFCs (similar to the way that the reader, with links to reference RFCs (similar to the way that
Internet Drafts are HTML-ized, the same tool can perform the Internet Drafts are HTML-ized, the same tool can perform the
function) or immutable document. function) or immutable document.
The "Reference" column will include an RFC number, an approved The "Reference" column will include an RFC number, an approved
specification designator from another standards body, or other specification designator from another standards body, or other
immutable document. immutable document.
New assignments for Performance Metrics Registry will be administered New assignments for Performance Metrics Registry will be administered
skipping to change at page 32, line 18 skipping to change at page 32, line 23
element ID and metric name. element ID and metric name.
11.1.1. ID (Identifier) 11.1.1. ID (Identifier)
<insert a numeric identifier, an integer, TBD> <insert a numeric identifier, an integer, TBD>
11.1.2. Name 11.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
11.1.3. URIs 11.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
11.1.4. Description 11.1.4. Description
<provide a description> <provide a description>
11.1.5. Change Controller 11.1.5. Change Controller
11.1.6. Version (of Registry Format) 11.1.6. Version (of Registry Format)
skipping to change at page 36, line 10 skipping to change at page 36, line 10
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-ippm-initial-registry] [I-D.ietf-ippm-initial-registry]
Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza, Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,
"Initial Performance Metrics Registry Entries", draft- "Initial Performance Metrics Registry Entries", draft-
ietf-ippm-initial-registry-14 (work in progress), November ietf-ippm-initial-registry-15 (work in progress), December
2019. 2019.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681, Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
September 1999, <https://www.rfc-editor.org/info/rfc2681>. September 1999, <https://www.rfc-editor.org/info/rfc2681>.
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
performance measurement with periodic streams", RFC 3432, performance measurement with periodic streams", RFC 3432,
DOI 10.17487/RFC3432, November 2002, DOI 10.17487/RFC3432, November 2002,
<https://www.rfc-editor.org/info/rfc3432>. <https://www.rfc-editor.org/info/rfc3432>.
skipping to change at page 38, line 5 skipping to change at page 38, line 5
Ed., "A One-Way Delay Metric for IP Performance Metrics Ed., "A One-Way Delay Metric for IP Performance Metrics
(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January (IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January
2016, <https://www.rfc-editor.org/info/rfc7679>. 2016, <https://www.rfc-editor.org/info/rfc7679>.
[RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for [RFC8194] Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for
LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194, LMAP Measurement Agents", RFC 8194, DOI 10.17487/RFC8194,
August 2017, <https://www.rfc-editor.org/info/rfc8194>. August 2017, <https://www.rfc-editor.org/info/rfc8194>.
Authors' Addresses Authors' Addresses
Marcelo Bagnulo Marcelo Bagnulo
Universidad Carlos III de Universidad Carlos III de Madrid
Madrid
Av. Universidad 30 Av. Universidad 30
Leganes, Madrid 28911 Leganes, Madrid 28911
SPAIN SPAIN
Phone: 34 91 6249500 Phone: 34 91 6249500
Email: marcelo@it.uc3m.es Email: marcelo@it.uc3m.es
URI: http://www.it.uc3m.es URI: http://www.it.uc3m.es
Benoit Claise Benoit Claise
Cisco Systems, Cisco Systems, Inc.
Inc.
De Kleetlaan 6a b1 De Kleetlaan 6a b1
1831 Diegem 1831 Diegem
Belgium Belgium
Email: bclaise@cisco.com Email: bclaise@cisco.com
Philip Eardley Philip Eardley
BT BT
Adastral Park, Martlesham Heath Adastral Park, Martlesham Heath
Ipswich Ipswich
 End of changes. 28 change blocks. 
64 lines changed or deleted 71 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/