< draft-ietf-ippm-initial-registry-09.txt   draft-ietf-ippm-initial-registry-10.txt >
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Standards Track M. Bagnulo Intended status: Standards Track M. Bagnulo
Expires: June 10, 2019 UC3M Expires: September 12, 2019 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
December 7, 2018 March 11, 2019
Initial Performance Metric Registry Entries Initial Performance Metrics Registry Entries
draft-ietf-ippm-initial-registry-09 draft-ietf-ippm-initial-registry-10
Abstract Abstract
This memo defines the Initial Entries for the Performance Metrics This memo defines the set of Initial Entries for the IANA Performance
Registry. This version includes: Metrics Registry. The set includes, UDP Round-trip Latency and Loss,
Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson
* removed sections which only contained examples, or a blank outine One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP
for new metric entries. Round-trip Latency and Loss, and TCP round-trip Latency and Loss.
* removed remaining comments (did not require action).
Requirements Language Requirements Language
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 BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14[RFC2119] [RFC8174] when, and only when, they appear in all 14[RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
skipping to change at page 1, line 49 skipping to change at page 1, line 47
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 10, 2019. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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 6, line 33 skipping to change at page 6, line 33
10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 72 10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 72
10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 73 10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 73
10.5. Administrative items . . . . . . . . . . . . . . . . . . 73 10.5. Administrative items . . . . . . . . . . . . . . . . . . 73
10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 73 10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 73
10.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . 73 10.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . 73
10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 73 10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 73
10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 73 10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 73
10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 73 10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 73
11. Security Considerations . . . . . . . . . . . . . . . . . . . 73 11. Security Considerations . . . . . . . . . . . . . . . . . . . 73
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 73 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 73
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 73 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 74
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 74
14.1. Normative References . . . . . . . . . . . . . . . . . . 74 14.1. Normative References . . . . . . . . . . . . . . . . . . 74
14.2. Informative References . . . . . . . . . . . . . . . . . 76 14.2. Informative References . . . . . . . . . . . . . . . . . 76
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78
1. Introduction 1. Introduction
Note: Efforts to synchronize structure and terminology with
[I-D.ietf-ippm-metric-registry] will likely be incomplete until both
drafts are stable.
This memo proposes an initial set of entries for the Performance This memo proposes an initial set of entries for the Performance
Metric Registry. It uses terms and definitions from the IPPM Metrics Registry. It uses terms and definitions from the IPPM
literature, primarily [RFC2330]. literature, primarily [RFC2330].
Although there are several standard templates for organizing Although there are several standard templates for organizing
specifications of performance metrics (see [RFC2679] for an example specifications of performance metrics (see [RFC2679] for an example
of the traditional IPPM template, based to large extent on the of the traditional IPPM template, based to large extent on the
Benchmarking Methodology Working Group's traditional template in Benchmarking Methodology Working Group's traditional template in
[RFC1242], and see [RFC6390] for a similar template), none of these [RFC1242], and see [RFC6390] for a similar template), none of these
templates were intended to become the basis for the columns of an templates were intended to become the basis for the columns of an
IETF-wide registry of metrics. While examining aspects of metric IETF-wide registry of metrics. While examining aspects of metric
specifications which need to be registered, it became clear that none specifications which need to be registered, it became clear that none
of the existing metric templates fully satisfies the particular needs of the existing metric templates fully satisfies the particular needs
of a registry. of a registry.
Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format
for a Performance Metric Registry. Section 5 of for a Performance Metrics Registry. Section 5 of
[I-D.ietf-ippm-metric-registry] also gives guidelines for those [I-D.ietf-ippm-metric-registry] also gives guidelines for those
requesting registration of a Metric, that is the creation of entry(s) requesting registration of a Metric, that is the creation of entry(s)
in the Performance Metric Registry: "In essence, there needs to be in the Performance Metrics Registry: "In essence, there needs to be
evidence that a candidate Registered Performance Metric has evidence that a candidate Registered Performance Metric has
significant industry interest, or has seen deployment, and there is significant industry interest, or has seen deployment, and there is
agreement that the candidate Registered Performance Metric serves its agreement that the candidate Registered Performance Metric serves its
intended purpose." The process in [I-D.ietf-ippm-metric-registry] intended purpose." The process in [I-D.ietf-ippm-metric-registry]
also requires that new entries are administered by IANA through also requires that new entries are administered by IANA through
Expert Review, which will ensure that the metrics are tightly Expert Review or IETF Standards action, which will ensure that the
defined. metrics are tightly defined.
2. Scope 2. Scope
This document defines the initial set of Performance Metrics Registry This document defines the initial set of Performance Metrics Registry
entries, for which IETF approval (following development in the IP entries, for which IETF approval (following development in the IP
Performance Metrics (IPPM) Working Group) will satisfy the Performance Metrics (IPPM) Working Group) will satisfy the
requirement for Expert Review. Most are Active Performance Metrics, requirement for Expert Review. Most are Active Performance Metrics,
which are based on RFCs prepared in the IPPM working group of the which are based on RFCs prepared in the IPPM working group of the
IETF, according to their framework [RFC2330] and its updates. IETF, according to their framework [RFC2330] and its updates.
3. Registry Categories and Columns 3. Registry Categories and Columns
This memo uses the terminology defined in
[I-D.ietf-ippm-metric-registry].
This section provides the categories and columns of the registry, for This section provides the categories and columns of the registry, for
easy reference. An entry (row) therefore gives a complete easy reference. An entry (row) therefore gives a complete
description of a Registered Metric. description of a Registered Metric.
Registry Categories and Columns, shown as Registry Categories and Columns, shown as
Category Category
------------------ ------------------
Column | Column | Column | Column |
Summary Summary
skipping to change at page 73, line 41 skipping to change at page 73, line 41
None. None.
11. Security Considerations 11. Security Considerations
These registry entries represent no known implications for Internet These registry entries represent no known implications for Internet
Security. Each referenced Metric contains a Security Considerations Security. Each referenced Metric contains a Security Considerations
section. section.
12. IANA Considerations 12. IANA Considerations
IANA is requested to populate The Performance Metric Registry defined IANA is requested to populate The Performance Metrics Registry
in [I-D.ietf-ippm-metric-registry] with the values defined above. defined in [I-D.ietf-ippm-metric-registry] with the values defined
above.
See the IANA Considerations section of See the IANA Considerations section of
[I-D.ietf-ippm-metric-registry] for additional requests and [I-D.ietf-ippm-metric-registry] for additional requests and
considerations. considerations.
13. Acknowledgements 13. Acknowledgements
The authors thank Brian Trammell for suggesting the term "Run-time The authors thank Brian Trammell for suggesting the term "Run-time
Parameters", which led to the distinction between run-time and fixed Parameters", which led to the distinction between run-time and fixed
parameters implemented in this memo, for identifying the IPFIX metric parameters implemented in this memo, for identifying the IPFIX metric
 End of changes. 14 change blocks. 
25 lines changed or deleted 23 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/