draft-ietf-ippm-initial-registry-12.txt   draft-ietf-ippm-initial-registry-13.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: March 14, 2020 UC3M Expires: May 24, 2020 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
September 11, 2019 November 21, 2019
Initial Performance Metrics Registry Entries Initial Performance Metrics Registry Entries
draft-ietf-ippm-initial-registry-12 draft-ietf-ippm-initial-registry-13
Abstract Abstract
This memo defines the set of Initial Entries for the IANA Performance This memo defines the set of Initial Entries for the IANA Performance
Metrics Registry. The set includes, UDP Round-trip Latency and Loss, Metrics Registry. The set includes, UDP Round-trip Latency and Loss,
Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson
One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP
Round-trip Latency and Loss, and TCP round-trip Latency and Loss. Round-trip Latency and Loss, and TCP round-trip Latency and Loss.
Requirements Language Requirements Language
skipping to change at page 1, line 47 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 March 14, 2020. This Internet-Draft will expire on May 24, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 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
skipping to change at page 3, line 10 skipping to change at page 3, line 10
4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 16 4.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 16
4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16
4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16
4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16
5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16
5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16
5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 17 5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 17
5.1.6. Version (of Registry Format) . . . . . . . . . . . . 17 5.1.6. Version (of Registry Format) . . . . . . . . . . . . 17
5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17
5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 18 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 18
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18
5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19 5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19
5.3.3. Traffic Filtering (observation) Details . . . . . . . 20 5.3.3. Traffic Filtering (observation) Details . . . . . . . 20
5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 20 5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 20
5.3.5. Run-time Parameters and Data Format . . . . . . . . . 20 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 20
5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 21 5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21 5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.2. Reference Definition . . . . . . . . . . . . . . . . 21 5.4.2. Reference Definition . . . . . . . . . . . . . . . . 21
5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 21 5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 21
5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22 5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22
5.5. Administrative items . . . . . . . . . . . . . . . . . . 22 5.5. Administrative items . . . . . . . . . . . . . . . . . . 22
5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 22
5.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 23 5.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 23
5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 23 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 23
5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23
skipping to change at page 8, line 29 skipping to change at page 8, line 29
--------------------------------------------------------------------- ---------------------------------------------------------------------
Reference | Packet | Traffic | Sampling | Run-time | Role | Reference | Packet | Traffic | Sampling | Run-time | Role |
Method | Stream | Filter | Distribution | Parameters | | Method | Stream | Filter | Distribution | Parameters | |
| Generation | | Generation |
Output Output
----------------------------------------- -----------------------------------------
Type | Reference | Units | Calibration | Type | Reference | Units | Calibration |
| Definition | | | | Definition | | |
Administrative Information Administrative Information
Status |Request | Rev | Rev.Date | ------------------------------------
Status |Requester | Rev | Rev.Date |
Comments and Remarks Comments and Remarks
-------------------- --------------------
4. UDP Round-trip Latency and Loss Registry Entries 4. UDP Round-trip Latency and Loss Registry Entries
This section specifies an initial registry entry for the UDP Round- This section specifies an initial registry entry for the UDP Round-
trip Latency, and another entry for UDP Round-trip Loss Ratio. trip Latency, and another entry for UDP Round-trip Loss Ratio.
Note: Each Registry entry only produces a "raw" output or a Note: Each Registry entry only produces a "raw" output or a
skipping to change at page 16, line 32 skipping to change at page 16, line 32
4.6. Comments and Remarks 4.6. Comments and Remarks
None. None.
5. Packet Delay Variation Registry Entry 5. Packet Delay Variation Registry Entry
This section gives an initial registry entry for a Packet Delay This section gives an initial registry entry for a Packet Delay
Variation metric. Variation metric.
Note: If each Registry entry should only produce a "raw" output or a
statistical summary, then the "Output" Category can be split and this
section can become two closely-related metrics.
5.1. Summary 5.1. Summary
This category includes multiple indexes to the registry entries, the This category includes multiple indexes to the registry entries, the
element ID and metric name. element ID and metric name.
5.1.1. ID (Identifier) 5.1.1. ID (Identifier)
<insert numeric identifier, an integer> <insert numeric identifier, an integer>
5.1.2. Name 5.1.2. Name
skipping to change at page 17, line 43 skipping to change at page 17, line 39
Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric
for IP Performance Metrics (IPPM)", RFC 3393, November 2002. for IP Performance Metrics (IPPM)", RFC 3393, November 2002.
[RFC3393] [RFC3393]
Morton, A. and B. Claise, "Packet Delay Variation Applicability Morton, A. and B. Claise, "Packet Delay Variation Applicability
Statement", RFC 5481, March 2009. [RFC5481] Statement", RFC 5481, March 2009. [RFC5481]
Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time
Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, Protocol Version 4: Protocol and Algorithms Specification", RFC 5905,
June 2010.[RFC5905] June 2010. [RFC5905]
See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences
measured are referred to by the variable name "ddT" (applicable to measured are referred to by the variable name "ddT" (applicable to
all forms of delay variation). However, this metric entry specifies all forms of delay variation). However, this metric entry specifies
the PDV form defined in section 4.2 of [RFC5481], where the singleton the PDV form defined in section 4.2 of [RFC5481], where the singleton
PDV for packet i is referred to by the variable name "PDV(i)". PDV for packet i is referred to by the variable name "PDV(i)".
5.2.2. Fixed Parameters 5.2.2. Fixed Parameters
o IPv4 header values: o IPv4 header values:
skipping to change at page 21, line 7 skipping to change at page 20, line 49
interval. The start time is controlled through other means. interval. The start time is controlled through other means.
Tf a time, the end of a measurement interval, (format "date-and-time" Tf a time, the end of a measurement interval, (format "date-and-time"
as specified in Section 5.6 of [RFC3339], see also Section 3 of as specified in Section 5.6 of [RFC3339], see also Section 3 of
[RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of
[RFC2330]. When T0 is "all-zeros", a end time date is ignored and [RFC2330]. When T0 is "all-zeros", a end time date is ignored and
Tf is interpreted as the Duration of the measurement interval. Tf is interpreted as the Duration of the measurement interval.
5.3.6. Roles 5.3.6. Roles
Src launches each packet and waits for return transmissions from
Dst.
Dst waits for each packet from Src and sends a return packet to Src.
5.4. Output 5.4. Output
This category specifies all details of the Output of measurements This category specifies all details of the Output of measurements
using the metric. using the metric.
5.4.1. Type 5.4.1. Type
Percentile -- for the conditional distribution of all packets with a Percentile -- for the conditional distribution of all packets with a
valid value of one-way delay (undefined delays are excluded), a valid value of one-way delay (undefined delays are excluded), a
single value corresponding to the 95th percentile, as follows: single value corresponding to the 95th percentile, as follows:
skipping to change at page 32, line 25 skipping to change at page 32, line 25
6.5.3. Revision 6.5.3. Revision
1.0 1.0
6.5.4. Revision Date 6.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
6.6. Comments and Remarks 6.6. Comments and Remarks
Additional (Informational) details for this entry None
7. UDP Poisson One-way Delay and Loss Registry Entries 7. UDP Poisson One-way Delay and Loss Registry Entries
This section specifies five initial registry entries for the UDP This section specifies five initial registry entries for the UDP
Poisson One-way Delay, and one for UDP Poisson One-way Loss. Poisson One-way Delay, and one for UDP Poisson One-way Loss.
IANA Note: Registry "Name" below specifies a single registry entry, IANA Note: Registry "Name" below specifies multiple registry entries,
whose output format varies according to the <statistic> element of whose output format varies according to the <statistic> element of
the name that specifies one form of statistical summary. There is an the name that specifies one form of statistical summary. There is an
additional metric name for the Loss metric. additional metric name for the Loss metric.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
six closely-related registry entries. As a result, IANA is also six closely-related registry entries. As a result, IANA is also
asked to assign corresponding URLs to each Named Metric. asked to assign corresponding URLs to each Named Metric.
7.1. Summary 7.1. Summary
skipping to change at page 42, line 44 skipping to change at page 42, line 44
7.5.3. Revision 7.5.3. Revision
1.0 1.0
7.5.4. Revision Date 7.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
7.6. Comments and Remarks 7.6. Comments and Remarks
Additional (Informational) details for this entry None
8. UDP Periodic One-way Delay and Loss Registry Entries 8. UDP Periodic One-way Delay and Loss Registry Entries
This section specifies five initial registry entries for the UDP This section specifies five initial registry entries for the UDP
Periodic One-way Delay, and one for UDP Periodic One-way Loss. Periodic One-way Delay, and one for UDP Periodic One-way Loss.
IANA Note: Registry "Name" below specifies a single registry entry, IANA Note: Registry "Name" below specifies multiple registry entries,
whose output format varies according to the <statistic> element of whose output format varies according to the <statistic> element of
the name that specifies one form of statistical summary. There is an the name that specifies one form of statistical summary. There is an
additional metric name for the Loss metric. additional metric name for the Loss metric.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
six closely-related registry entries. As a result, IANA is also six closely-related registry entries. As a result, IANA is also
asked to assign corresponding URLs to each Named Metric. asked to assign corresponding URLs to each Named Metric.
8.1. Summary 8.1. Summary
skipping to change at page 53, line 32 skipping to change at page 53, line 32
8.6. Comments and Remarks 8.6. Comments and Remarks
None. None.
9. ICMP Round-trip Latency and Loss Registry Entries 9. ICMP Round-trip Latency and Loss Registry Entries
This section specifies three initial registry entries for the ICMP This section specifies three initial registry entries for the ICMP
Round-trip Latency, and another entry for ICMP Round-trip Loss Ratio. Round-trip Latency, and another entry for ICMP Round-trip Loss Ratio.
This section specifies four Registry entries with many common IANA Note: Registry "Name" below specifies multiple registry entries,
columns. whose output format varies according to the <statistic> element of
the name that specifies one form of statistical summary. There is an
additional metric name for the Loss metric.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
two closely-related registry entries. As a result, IANA is also two closely-related registry entries. As a result, IANA is also
asked to assign four corresponding URLs to each Named Metric. asked to assign four corresponding URLs to each Named Metric.
9.1. Summary 9.1. Summary
This category includes multiple indexes to the registry entry: the This category includes multiple indexes to the registry entry: the
element ID and metric name. element ID and metric name.
skipping to change at page 62, line 46 skipping to change at page 62, line 46
9.6. Comments and Remarks 9.6. Comments and Remarks
None None
10. TCP Round-Trip Delay and Loss Registry Entries 10. TCP Round-Trip Delay and Loss Registry Entries
This section specifies three initial registry entries for the Passive This section specifies three initial registry entries for the Passive
assessment of TCP Round-Trip Delay (RTD) and another entry for TCP assessment of TCP Round-Trip Delay (RTD) and another entry for TCP
Round-trip Loss Count. Round-trip Loss Count.
This section specifies four Registry entries with many common IANA Note: Registry "Name" below specifies multiple registry entries,
columns. whose output format varies according to the <statistic> element of
the name that specifies one form of statistical summary. There are
two additional metric names for Singleton RT Delay and Packet Count
metrics.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
four closely-related registry entries. As a result, IANA is also four closely-related registry entries. As a result, IANA is also
asked to assign four corresponding URLs to each Named Metric. asked to assign four corresponding URLs to each Named Metric.
10.1. Summary 10.1. Summary
This category includes multiple indexes to the registry entry: the This category includes multiple indexes to the registry entry: the
element ID and metric name. element ID and metric name.
skipping to change at page 74, line 8 skipping to change at page 74, line 8
parameters implemented in this memo, for identifying the IPFIX metric parameters implemented in this memo, for identifying the IPFIX metric
with Flow Key as an example, for suggesting the Passive TCP RTD with Flow Key as an example, for suggesting the Passive TCP RTD
metric and supporting references, and for many other productive metric and supporting references, and for many other productive
suggestions. Thanks to Peter Koch, who provided several useful suggestions. Thanks to Peter Koch, who provided several useful
suggestions for disambiguating successive DNS Queries in the DNS suggestions for disambiguating successive DNS Queries in the DNS
Response time metric. Response time metric.
The authors also acknowledge the constructive reviews and helpful The authors also acknowledge the constructive reviews and helpful
suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey, suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey,
Yaakov Stein, and participants in the LMAP working group. Thanks to Yaakov Stein, and participants in the LMAP working group. Thanks to
Michelle Cotton for her early IANA review, and to Amanda Barber for Michelle Cotton for her early IANA reviews, and to Amanda Barber for
answering questions related to the presentation of the registry and answering questions related to the presentation of the registry and
accessibility of the complete template via URL. accessibility of the complete template via URL.
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.ietf-ippm-metric-registry] [I-D.ietf-ippm-metric-registry]
Bagnulo, M., Claise, B., Eardley, P., and A. Morton, Bagnulo, M., Claise, B., Eardley, P., and A. Morton,
"Registry for Performance Metrics", Internet Draft (work "Registry for Performance Metrics", Internet Draft (work
skipping to change at page 77, line 18 skipping to change at page 77, line 18
AT&T Labs AT&T Labs
200 Laurel Avenue South 200 Laurel Avenue South
Middletown,, NJ 07748 Middletown,, NJ 07748
USA USA
Phone: +1 732 420 1571 Phone: +1 732 420 1571
Fax: +1 732 368 1192 Fax: +1 732 368 1192
Email: acmorton@att.com Email: acmorton@att.com
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
Email: marcelo@it.uc3m.es Email: marcelo@it.uc3m.es
URI: http://www.it.uc3m.es URI: http://www.it.uc3m.es
Philip Eardley Philip Eardley
BT BT
 End of changes. 20 change blocks. 
24 lines changed or deleted 32 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/