draft-ietf-ippm-initial-registry-03.txt   draft-ietf-ippm-initial-registry-04.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: UC3M Expires: January 1, 2018 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
, 2017 June 30, 2017
Initial Performance Metric Registry Entries Initial Performance Metric Registry Entries
draft-ietf-ippm-initial-registry-0 draft-ietf-ippm-initial-registry-04
Abstract Abstract
This memo defines the Initial Entries for the Performance Metrics This memo defines the Initial Entries for the Performance Metrics
Registry. This version includes: Registry. This version includes:
* Addition of Loss Ratio metric in various sections (multiple metrics
per section).
* All section 4, 5, 6, 7, and 8 parameters reference YANG types for * All section 4, 5, 6, 7, and 8 parameters reference YANG types for
alternate data formats. alternate data formats.
* implementation of standard naming format for parameters. * implementation of standard naming format for parameters.
* implementation of many IANA early-review comments. * implementation of many IANA early-review comments.
Still need: Add MBM metric entry. Still need: Add MBM metric entry.
Requirements Language Requirements Language
skipping to change at page 2, line 4 skipping to change at page 2, line 9
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
This Internet-Draft will expire on January 1, 2018.
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
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 26 skipping to change at page 2, line 32
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.
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Registry Categories and Columns . . . . . . . . . . . . . . . 7 3. Registry Categories and Columns . . . . . . . . . . . . . . . 7
4. UDP Round-trip Latency Registry . . . . . . 8 4. UDP Round-trip Latency and Loss Registry Entries . . . . . . 8
4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9
4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9
4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 9 4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 9
4.1.6. Version (of Registry Format) . . . . . . . . . . . . 9 4.1.6. Version (of Registry Format) . . . . . . . . . . . . 9
4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 10
4.2.1. Reference Definition . . . . . . . . . . . . . . . . 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 10
4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 11
4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11
4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 12
4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 13
4.3.3. Traffic Filtering (observation) Details . . . . . . . 13 4.3.3. Traffic Filtering (observation) Details . . . . . . . 13
4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 13 4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 13
4.3.5. Run-time Parameters and Data Format . . . . . . . . . 13 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 13
4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4.2. Reference Definition . . . . . . . . . . . . . . . . 15 4.4.2. Reference Definition . . . . . . . . . . . . . . . . 15
4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 16
4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 16
4.5. Administrative items . . . . . . . . . . . . . . . . . . 4.5. Administrative items . . . . . . . . . . . . . . . . . . 17
4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 17
4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 17
4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 17
4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 17
4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 17
5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 17
5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 17 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 17
5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 18
5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 18
5.1.6. Version (of Registry Format) . . . . . . . . . . . . 5.1.6. Version (of Registry Format) . . . . . . . . . . . . 18
5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 18
5.2.1. Reference Definition . . . . . . . . . . . . . . . . 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 18
5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 19
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 20
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 20
5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 21
5.3.3. Traffic Filtering (observation) Details . . . . . . . 21 5.3.3. Traffic Filtering (observation) Details . . . . . . . 21
5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 22
5.3.5. Run-time Parameters and Data Format . . . . . . . . . 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 22
5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4.2. Reference Definition . . . . . . . . . . . . . . . . 5.4.2. Reference Definition . . . . . . . . . . . . . . . . 23
5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 23 5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 23
5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 2 5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 24
5.5. Administrative items . . . . . . . . . . . . . . . . . . 24 5.5. Administrative items . . . . . . . . . . . . . . . . . . 24
5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 24 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 25
5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 25
5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 25
5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 25
6. DNS Response Latency Registry . . . . . . . 6. DNS Response Latency and Loss Registry Entries . . . . . . . 25
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 25
6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 26
6.1.5. Change Controller . . . . . . . . . . . . . . . . . . 6.1.5. Change Controller . . . . . . . . . . . . . . . . . . 26
6.1.6. Version (of Registry Format) . . . . . . . . . . . . 6.1.6. Version (of Registry Format) . . . . . . . . . . . . 26
6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 26
6.2.1. Reference Definition . . . . . . . . . . . . . . . . 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 26
6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 27
9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 29
10. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 29
10.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 6.3.2. Packet Stream Generation . . . . . . . . . . . . . . 30
10.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 6.3.3. Traffic Filtering (observation) Details . . . . . . . 31
10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 31
10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 6.3.5. Run-time Parameters and Data Format . . . . . . . . . 31
10.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 32
10.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 6.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 6.4.2. Reference Definition . . . . . . . . . . . . . . . . 33
10.1.8. Description . . . . . . . . . . . . . . . . . . . . 6.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 33
10.1.9. Reference Specification(s) . . . . . . . . . . . . . 6.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 34
10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 6.5. Administrative items . . . . . . . . . . . . . . . . . . 34
10.2.1. Reference Definition . . . . . . . . . . . . . . . . 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 34
10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 6.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 34
10.3. Method of Measurement . . . . . . . . . . . . . . . . . 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 34
10.3.1. Reference Method . . . . . . . . . . . . . . . . . . 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 34
10.3.2. Stream Type and Stream Parameters . . . . . . . . . 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 34
10.3.3. Output Type and Data Format . . . . . . . . . . . . 7. UDP Poisson One-way Delay and Loss Registry Entries . . . . . 35
10.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 35
10.3.5. Run-time Parameters and Data Format . . . . . . . . 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 35
10.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 35
11. Revision History . . . . . . . . . . . . . . . . . . . . . . 7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 36
12. Security Considerations . . . . . . . . . . . . . . . . . . . 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 36
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 36
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 36
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 37
15.1. Normative References . . . . . . . . . . . . . . . . . . 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 38
15.2. Informative References . . . . . . . . . . . . . . . . . 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 39
7.3.3. Traffic Filtering (observation) Details . . . . . . . 40
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 40
7.3.5. Run-time Parameters and Data Format . . . . . . . . . 40
7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 41
7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 41
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 41
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 44
7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 44
7.5. Administrative items . . . . . . . . . . . . . . . . . . 45
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 45
7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 45
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 45
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 45
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 45
8. UDP Periodic One-way Delay and Loss Registry Entries . . . . 46
8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 46
8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 46
8.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 47
8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 47
8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 47
8.2.1. Reference Definition . . . . . . . . . . . . . . . . 47
8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 48
8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 49
8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 49
8.3.2. Packet Stream Generation . . . . . . . . . . . . . . 50
8.3.3. Traffic Filtering (observation) Details . . . . . . . 51
8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 51
8.3.5. Run-time Parameters and Data Format . . . . . . . . . 51
8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 52
8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 52
8.4.2. Reference Definition . . . . . . . . . . . . . . . . 52
8.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 55
8.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 55
8.5. Administrative items . . . . . . . . . . . . . . . . . . 56
8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 56
8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 56
8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 56
8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 56
8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 56
9. ver08 BLANK Registry Entry . . . . . . . . . . . . . . . . . 56
9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 56
9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 56
9.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 57
9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 57
9.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 57
9.1.6. Change Controller . . . . . . . . . . . . . . . . . . 57
9.1.7. Version (of Registry Format) . . . . . . . . . . . . 57
9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 57
9.2.1. Reference Definition . . . . . . . . . . . . . . . . 57
9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 57
9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 57
9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 58
9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 58
9.3.3. Traffic Filtering (observation) Details . . . . . . . 58
9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 58
9.3.5. Run-time Parameters and Data Format . . . . . . . . . 58
9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 58
9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 58
9.4.2. Reference Definition . . . . . . . . . . . . . . . . 58
9.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 58
9.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 59
9.5. Administrative items . . . . . . . . . . . . . . . . . . 59
9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 59
9.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 59
9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 59
9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 59
9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 59
10. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 59
10.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 59
10.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 59
10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 60
10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 60
10.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 60
10.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 60
10.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 60
10.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 60
10.1.8. Description . . . . . . . . . . . . . . . . . . . . 60
10.1.9. Reference Specification(s) . . . . . . . . . . . . . 60
10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 60
10.2.1. Reference Definition . . . . . . . . . . . . . . . . 60
10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 61
10.3. Method of Measurement . . . . . . . . . . . . . . . . . 61
10.3.1. Reference Method . . . . . . . . . . . . . . . . . . 61
10.3.2. Stream Type and Stream Parameters . . . . . . . . . 62
10.3.3. Output Type and Data Format . . . . . . . . . . . . 62
10.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 62
10.3.5. Run-time Parameters and Data Format . . . . . . . . 62
10.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 64
11. Revision History . . . . . . . . . . . . . . . . . . . . . . 64
12. Security Considerations . . . . . . . . . . . . . . . . . . . 64
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 65
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 65
15.1. Normative References . . . . . . . . . . . . . . . . . . 65
15.2. Informative References . . . . . . . . . . . . . . . . . 67
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69
1. Introduction 1. Introduction
Note: Efforts to synchronize structure and terminology with Note: Efforts to synchronize structure and terminology with
[I-D.ietf-ippm-metric-registry] will likely be incomplete until both [I-D.ietf-ippm-metric-registry] will likely be incomplete until both
drafts are stable. 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 Metric Registry. It uses terms and definitions from the IPPM
literature, primarily [RFC2330]. Proponents of Passive Performance literature, primarily [RFC2330]. Proponents of Passive Performance
skipping to change at page 8, line 35 skipping to change at page 8, line 35
Type | Reference | Units | Calibration | Type | Reference | Units | Calibration |
| Definition | | | | Definition | | |
---------------------------------- ----------------------------------
Status |Request | Rev | Rev.Date | Status |Request | Rev | Rev.Date |
-------------------- --------------------
4. UDP Round-trip Latency 4. UDP Round-trip Latency and Loss Registry Entries
This section an initial registry entry for the UDP Round-trip This section specifies an initial registry entry for the UDP Round-
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
statistical summary. To describe both "raw" and one or more statistical summary. To describe both "raw" and one or more
statistics efficiently, the Identifier, Name, and Output Categories statistics efficiently, the Identifier, Name, and Output Categories
can be split and a single section can specify two or more closely- can be split and a single section can specify two or more closely-
related metrics. See Section 7 for an example specifying multiple related metrics. This section specifies two Registry entries with
Registry entries with many common columns. many common columns. See Section 7 for an example specifying
multiple Registry entries with many common columns.
All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes
two closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric.
4.1. Summary 4.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.
4.1.1. ID (Identifier) 4.1.1. ID (Identifier)
<insert a numeric identifier, an integer, TBD> <insert a numeric identifier, an integer, TBD>
IANA is asked to assign different numeric identifiers to each of the
two Named Metrics.
4.1.2. Name 4.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile
RTLoss_Active_IP-UDP-Poisson_RFCXXXXsecY_Percent_LossRatio
4.1.3. URIs 4.1.3. URIs
URN: Prefix urn:ietf:metrics:perf:<name> URN: Prefix urn:ietf:metrics:perf:<name>
URL: http://<TBD by IANA>/<name> URL: http://<TBD by IANA>/<name>
4.1.4. Description 4.1.4. Description
This metric assesses the delay of a stream of packets exchanged RTDelay: This metric assesses the delay of a stream of packets
between two hosts (which are the two measurement points), and the exchanged between two hosts (which are the two measurement points),
Output is the Round-trip delay for all successfully exchanged packets and the Output is the Round-trip delay for all successfully exchanged
expressed as the 95th percentile of their conditional delay packets expressed as the 95th percentile of their conditional delay
distribution. distribution.
RTLoss: This metric assesses the loss ratio of a stream of packets
exchanged between two hosts (which are the two measurement points),
and the Output is the Round-trip loss ratio for all successfully
exchanged packets expressed as a percentage.
4.1.5. Change Controller 4.1.5. Change Controller
IETF IETF
4.1.6. Version (of Registry Format) 4.1.6. Version (of Registry Format)
1.0 1.0
4.2. Metric Definition 4.2. Metric Definition
skipping to change at page 10, line 22 skipping to change at page 10, line 40
metric tightens the definition further to recognize that the host in metric tightens the definition further to recognize that the host in
the "Src" role will send the first packet to "Dst", and ultimately the "Src" role will send the first packet to "Dst", and ultimately
receive the corresponding return packet from "Dst" (when neither are receive the corresponding return packet from "Dst" (when neither are
lost). lost).
Finally, note that the variable "dT" is used in [RFC2681] to refer to Finally, note that the variable "dT" is used in [RFC2681] to refer to
the value of Round-trip delay in metric definitions and methods. The the value of Round-trip delay in metric definitions and methods. The
variable "dT" has been re-used in other IPPM literature to refer to variable "dT" has been re-used in other IPPM literature to refer to
different quantities, and cannot be used as a global variable name. different quantities, and cannot be used as a global variable name.
Morton, A., "Round-trip Packet Loss Metrics", RFC 6673, August 2012.
[RFC6673]
Both delay and loss metrics employ a maximum waiting time for
received packets, so the count of lost packets to total packets sent
is the basis for the loss ratio calculation as per Section 6.1 of
[RFC6673].
4.2.2. Fixed Parameters 4.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be <list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when determined and embedded in the measurement system for use when
needed> needed>
Type-P as defined in Section 13 of [RFC2330]: Type-P as defined in Section 13 of [RFC2330]:
skipping to change at page 11, line 4 skipping to change at page 11, line 35
* Hop Count: set to 255 * Hop Count: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
* Checksum: the checksum MUST be calculated and included in the * Checksum: the checksum MUST be calculated and included in the
* total of 9 bytes * total of 9 bytes
Other measurement parameters: Other measurement parameters:
o Tmax: a loss threshold waiting time o Tmax: a loss threshold waiting time
* 3.0, expressed in units of seconds, as a positive value of type * 3.0, expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of decimal64 with fraction digits = 4 (see section 9.3 of
[RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with [RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with
lossless conversion to/from the 32-bit NTP timestamp as per lossless conversion to/from the 32-bit NTP timestamp as per
section 6 of [RFC5905]. section 6 of [RFC5905].
4.3. Method of Measurement 4.3. Method of Measurement
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 methods for implementations. unambiguous methods for implementations.
skipping to change at page 11, line 36 skipping to change at page 12, line 19
The methodology for this metric is defined as Type-P-Round-trip- The methodology for this metric is defined as Type-P-Round-trip-
Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section
3.6 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under 3.6 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under
Fixed Parameters. Fixed Parameters.
The reference method distinguishes between long-delayed packets and The reference method distinguishes between long-delayed packets and
lost packets by implementing a maximum waiting time for packet lost packets by implementing a maximum waiting time for packet
arrival. Tmax is the waiting time used as the threshold to declare a arrival. Tmax is the waiting time used as the threshold to declare a
packet lost. Lost packets SHALL be designated as having undefined packet lost. Lost packets SHALL be designated as having undefined
delay. delay, and counted for the RTLoss metric.
The calculations on the delay (RTT) SHALL be performed on the The calculations on the delay (RTT) SHALL be performed on the
conditional distribution, conditioned on successful packet arrival conditional distribution, conditioned on successful packet arrival
within Tmax. Also, when all packet delays are stored, the process within Tmax. Also, when all packet delays are stored, the process
which calculates the RTT value MAY enforce the Tmax threshold on which calculates the RTT value MAY enforce the Tmax threshold on
stored values before calculations. See section 4.1 of [RFC3393] for stored values before calculations. See section 4.1 of [RFC3393] for
details on the conditional distribution to exclude undefined values details on the conditional distribution to exclude undefined values
of delay, and Section 5 of [RFC6703] for background on this analysis of delay, and Section 5 of [RFC6703] for background on this analysis
choice. choice.
skipping to change at page 12, line 35 skipping to change at page 13, line 20
parameters. parameters.
<section/specification references, and description of any new <section/specification references, and description of any new
generation parameters, if needed> generation parameters, if needed>
Section 11.1.3 of [RFC2330] provides three methods to generate Section 11.1.3 of [RFC2330] provides three methods to generate
Poisson sampling intervals. the reciprocal of lambda is the average Poisson sampling intervals. the reciprocal of lambda is the average
packet spacing, thus the Run-time Parameter is Reciprocal_lambda = 1/ packet spacing, thus the Run-time Parameter is Reciprocal_lambda = 1/
lambda, in seconds. lambda, in seconds.
Method 3 SHALL be used, where given a start time (Run-time Method 3 SHALL be used, where given a start time (Run-time
Parameter), the subsequent send times are all computed prior to Parameter), the subsequent send times are all computed prior to
measurement by computing the pseudo-random distribution of inter- measurement by computing the pseudo-random distribution of inter-
packet send times, (truncating the distribution as specified in the packet send times, (truncating the distribution as specified in the
Run-time Parameter, Trunc), and the Src sends each packet at the Run-time Parameter, Trunc), and the Src sends each packet at the
computed times. computed times.
Note that Trunc is the upper limit on inter-packet times in the Note that Trunc is the upper limit on inter-packet times in the
Poisson distribution. A random value greater than Trunc is set equal Poisson distribution. A random value greater than Trunc is set equal
skipping to change at page 14, line 4 skipping to change at page 14, line 30
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.
Reciprocal_lambda average packet interval for Poisson Streams Reciprocal_lambda average packet interval for Poisson Streams
expressed in units of seconds, as a positive value of type expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of [RFC6020]) decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020])
with resolution of 0.0001 seconds (0.1 ms), and with lossless with resolution of 0.0001 seconds (0.1 ms), and with lossless
conversion to/from the 32-bit NTP timestamp as per section 6 of conversion to/from the 32-bit NTP timestamp as per section 6 of
[RFC5905]. [RFC5905].
Trunc Upper limit on Poisson distribution expressed in units of Trunc Upper limit on Poisson distribution expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = (see section 9.3 of [RFC6020]) with resolution of digits = 4 (see section 9.3 of [RFC6020]) with resolution of
0.0001 seconds (0.1 ms), and with lossless conversion to/from the 0.0001 seconds (0.1 ms), and with lossless conversion to/from the
32-bit NTP timestamp as per section 6 of [RFC5905] (values above 32-bit NTP timestamp as per section 6 of [RFC5905] (values above
this limit will be clipped and set to the limit value). (if fixed, this limit will be clipped and set to the limit value). (if fixed,
Trunc = 30.0000 seconds.) Trunc = 30.0000 seconds.)
>>> should Poisson run-time params be fixed instead? probably yes if >>> should Poisson run-time params be fixed instead? probably yes if
modeling a specific version of MBA tests. modeling a specific version of MBA tests.
4.3.6. Roles 4.3.6. Roles
skipping to change at page 15, line 5 skipping to change at page 15, line 31
distribution to exclude undefined values of delay, and Section 5 of distribution to exclude undefined values of delay, and Section 5 of
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
The percentile = 95, meaning that the reported delay, "95Percentile", The percentile = 95, meaning that the reported delay, "95Percentile",
is the smallest value of Round-trip delay for which the Empirical is the smallest value of Round-trip delay for which the Empirical
Distribution Function (EDF), F(95Percentile) >= 95% of the singleton Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
Round-trip delay values in the conditional distribution. See section Round-trip delay values in the conditional distribution. See section
11.3 of [RFC2330] for the definition of the percentile statistic 11.3 of [RFC2330] for the definition of the percentile statistic
using the EDF. using the EDF.
LossRatio -- the count of lost packets to total packets sent is the
basis for the loss ratio calculation as per Section 6.1 of [RFC6673].
4.4.2. Reference Definition 4.4.2. Reference Definition
<describe the reference data format for each type of result> <describe the reference data format for each type of result>
For all outputs --- For all outputs ---
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
Tf the end of a measurement interval, (format "date-and-time" as Tf the end of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
TotalPkts the count of packets sent by the Src to Dst during the
measurement interval.
For For
RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile:
95Percentile The time value of the result is expressed in units of 95Percentile The time value of the result is expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = 9 (see section 9.3 of [RFC6020]) with resolution of digits = 9 (see section 9.3 of [RFC6020]) with resolution of
0.000000001 seconds (1.0 ns), and with lossless conversion to/from 0.000000001 seconds (1.0 ns), and with lossless conversion to/from
the 64-bit NTP timestamp as section of the 64-bit NTP timestamp as
For
RTLoss_Active_IP-UDP-Poisson_RFCXXXXsecY_Percent_LossRatio:
Percentile The numeric value of the result is expressed in units of
lost packets to total packets times 100%, as a positive value of
type decimal64 with fraction digits = 9 (see section 9.3 of
[RFC6020]) with resolution of 0.0000000001.
4.4.3. Metric Units 4.4.3. Metric Units
<insert units for the measured results, and the reference <insert units for the measured results, and the reference
specification>. specification>.
The 95th Percentile of Round-trip Delay is expressed in seconds. The 95th Percentile of Round-trip Delay is expressed in seconds.
The Round-trip Loss Ratio is expressed as a percentage of lost
packets to total packets sent.
4.4.4. Calibration 4.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback at the Source calibration could be enabled with an internal loopback at the Source
host that includes as much of the measurement system as possible, host that includes as much of the measurement system as possible,
performs address manipulation as needed, and provides some form of performs address manipulation as needed, and provides some form of
isolation (e.g., deterministic delay) to avoid send-receive interface isolation (e.g., deterministic delay) to avoid send-receive interface
contention. Some portion of the random and systematic error can be contention. Some portion of the random and systematic error can be
characterized this way. characterized this way.
skipping to change at page 19, line 7 skipping to change at page 19, line 51
* total of 200 bytes * total of 200 bytes
Other measurement parameters: Other measurement parameters:
Tmax: a loss threshold waiting time with value 3.0, expressed in Tmax: a loss threshold waiting time with value 3.0, expressed in
units of seconds, as a positive value of type decimal64 with units of seconds, as a positive value of type decimal64 with
fraction digits = (see section 9.3 of [RFC6020]) and with fraction digits = 4 (see section 9.3 of [RFC6020]) and with
resolution of 0.0001 seconds (0.1 ms), with lossless conversion resolution of 0.0001 seconds (0.1 ms), with lossless conversion
to/from the 32-bit NTP timestamp as per section 6 of [RFC5905]. to/from the 32-bit NTP timestamp as per section 6 of [RFC5905].
F a selection function unambiguously defining the packets from the F a selection function unambiguously defining the packets from the
stream selected for the metric. See section 4.2 of [RFC5481] for stream selected for the metric. See section 4.2 of [RFC5481] for
the PDV form. the PDV form.
See the Packet Stream generation category for two additional Fixed See the Packet Stream generation category for two additional Fixed
Parameters. Parameters.
skipping to change at page 20, line 23 skipping to change at page 21, line 21
5.3.2. Packet Stream Generation 5.3.2. Packet Stream Generation
<list of generation parameters and section/spec references if needed> <list of generation parameters and section/spec references if needed>
Section 11.1.3 of [RFC2330] provides three methods to generate Section 11.1.3 of [RFC2330] provides three methods to generate
Poisson sampling intervals. the reciprocal of lambda is the average Poisson sampling intervals. the reciprocal of lambda is the average
packet spacing, thus the Run-time Parameter is Reciprocal_lambda = 1/ packet spacing, thus the Run-time Parameter is Reciprocal_lambda = 1/
lambda, in seconds. lambda, in seconds.
Method 3 SHALL be used, where given a start time (Run-time Method 3 SHALL be used, where given a start time (Run-time
Parameter), the subsequent send times are all computed prior to Parameter), the subsequent send times are all computed prior to
measurement by computing the pseudo-random distribution of inter- measurement by computing the pseudo-random distribution of inter-
packet send times, (truncating the distribution as specified in the packet send times, (truncating the distribution as specified in the
Parameter Trunc), and the Src sends each packet at the computed Parameter Trunc), and the Src sends each packet at the computed
times. times.
Note that Trunc is the upper limit on inter-packet times in the Note that Trunc is the upper limit on inter-packet times in the
Poisson distribution. A random value greater than Trunc is set equal Poisson distribution. A random value greater than Trunc is set equal
Reciprocal_lambda average packet interval for Poisson Streams Reciprocal_lambda average packet interval for Poisson Streams
expressed in units of seconds, as a positive value of type expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of [RFC6020]) decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020])
with resolution of 0.0001 seconds (0.1 ms), and with lossless with resolution of 0.0001 seconds (0.1 ms), and with lossless
conversion to/from the 32-bit NTP timestamp as per section 6 of conversion to/from the 32-bit NTP timestamp as per section 6 of
[RFC5905]. Reciprocal_lambda = 1 packet per second. [RFC5905]. Reciprocal_lambda = 1 packet per second.
Trunc Upper limit on Poisson distribution expressed in units of Trunc Upper limit on Poisson distribution expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = (see section 9.3 of [RFC6020]) with resolution of digits = 4 (see section 9.3 of [RFC6020]) with resolution of
0.0001 seconds (0.1 ms), and with lossless conversion to/from the 0.0001 seconds (0.1 ms), and with lossless conversion to/from the
32-bit NTP timestamp as per section 6 of [RFC5905] (values above 32-bit NTP timestamp as per section 6 of [RFC5905] (values above
this limit will be clipped and set to the limit value). Trunc = this limit will be clipped and set to the limit value). Trunc =
30.0000 seconds. 30.0000 seconds.
5.3.3. Traffic Filtering (observation) Details 5.3.3. Traffic Filtering (observation) Details
<insert the measured results based on a filtered version of the <insert the measured results based on a filtered version of the
packets observed, and this section provides the filter details (when packets observed, and this section provides the filter details (when
present), and section reference>. present), and section reference>.
skipping to change at page 24, line 32 skipping to change at page 25, line 26
<Additional (Informational) details for this entry> <Additional (Informational) details for this entry>
Lost packets represent a challenge for delay variation metrics. See Lost packets represent a challenge for delay variation metrics. See
section 4.1 of [RFC3393] and the delay variation applicability section 4.1 of [RFC3393] and the delay variation applicability
statement[RFC5481] for extensive analysis and comparison of PDV and statement[RFC5481] for extensive analysis and comparison of PDV and
an alternate metric, IPDV. an alternate metric, IPDV.
6. DNS Response Latency 6. DNS Response Latency and Loss Registry Entries
This section gives initial registry for DNS Response This section gives initial registry entries for DNS Response Latency
RFC 2681 [RFC2681] defines a Round-trip delay metric. We and Loss. RFC 2681 [RFC2681] defines a Round-trip delay metric. We
build on that metric by specifying several of the input parameters to build on that metric by specifying several of the input parameters to
precisely define for measuring DNS precisely define two metrics for measuring DNS latency and loss.
Note to IANA: Each Registry "Name" below specifies a single registry
entry, whose output format varies in accordance with the name.
All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes
two closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric.
6.1. Summary 6.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.
<skipping some admin columns for now> <skipping some admin columns for now>
6.1.1. ID (Identifier) 6.1.1. ID (Identifier)
<insert numeric identifier, an integer> <insert numeric identifier, an integer>
IANA is asked to assign different numeric identifiers to each of the
two Named Metrics.
6.1.2. Name 6.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_Raw RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_Raw
RLDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Logical_Raw
6.1.3. URI 6.1.3. URI
URI: Prefix urn:ietf:metrics:perf:<name> URI: Prefix urn:ietf:metrics:perf:<name>
URL: http://<TBD by IANA>/<name> URL: http://<TBD by IANA>/<name>
6.1.4. Description 6.1.4. Description
This metric assesses the response time, the interval from the query RTDNS: This metric assesses the response time, the interval from the
transmission to the response. query transmission to the response.
RLDNS: This metric indicates that the respnse was deemed lost. In
other words, the response time exceeded the maximum waiting time.
6.1.5. Change Controller 6.1.5. Change Controller
IETF IETF
6.1.6. Version (of Registry Format) 6.1.6. Version (of Registry Format)
1.0 1.0
6.2. Metric Definition 6.2. Metric Definition
skipping to change at page 26, line 22 skipping to change at page 27, line 29
the role of "Src", and the Foreign Name Server takes the role of the role of "Src", and the Foreign Name Server takes the role of
"Dst". "Dst".
Note that although the [RFC2681] definition of "Round-trip-Delay Note that although the [RFC2681] definition of "Round-trip-Delay
between Src and Dst at T" is directionally ambiguous in the text, between Src and Dst at T" is directionally ambiguous in the text,
this metric tightens the definition further to recognize that the this metric tightens the definition further to recognize that the
host in the "Src" role will send the first packet to "Dst", and host in the "Src" role will send the first packet to "Dst", and
ultimately receive the corresponding return packet from "Dst" (when ultimately receive the corresponding return packet from "Dst" (when
neither are lost). neither are lost).
Morton, A., "Round-trip Packet Loss Metrics", RFC 6673, August 2012.
[RFC6673]
Both response time and loss metrics employ a maximum waiting time for
received responses, so the count of lost packets to total packets
sent is the basis for the loss determination as per Section 4.3 of
[RFC6673].
6.2.2. Fixed Parameters 6.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be <list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when determined and embedded in the measurement system for use when
needed> needed>
Type-P as defined in Section 13 of [RFC2330]: Type-P as defined in Section 13 of [RFC2330]:
skipping to change at page 28, line 4 skipping to change at page 29, line 21
the Run-time column the Run-time column
+ QCLASS: set to 1 for IN + QCLASS: set to 1 for IN
* The other sections do not contain any Resource Records. * The other sections do not contain any Resource Records.
Other measurement parameters: Other measurement parameters:
o Tmax: a loss threshold waiting time (and to help disambiguate o Tmax: a loss threshold waiting time (and to help disambiguate
queries) queries)
* 5.0, expressed in units of seconds, as a positive value of type * 5.0, expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of decimal64 with fraction digits = 4 (see section 9.3 of
[RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with [RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with
lossless conversion to/from the 32-bit NTP timestamp as per lossless conversion to/from the 32-bit NTP timestamp as per
section 6 of [RFC5905]. section 6 of [RFC5905].
Observation: reply packets will contain a DNS response and may Observation: reply packets will contain a DNS response and may
contain RRs. contain RRs.
6.3. Method of Measurement 6.3. Method of Measurement
This category includes columns for references to relevant sections of This category includes columns for references to relevant sections of
skipping to change at page 28, line 33 skipping to change at page 29, line 51
The methodology for this metric is defined as Type-P-Round-trip- The methodology for this metric is defined as Type-P-Round-trip-
Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section
3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under 3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under
Fixed Parameters. Fixed Parameters.
The reference method distinguishes between long-delayed packets and The reference method distinguishes between long-delayed packets and
lost packets by implementing a maximum waiting time for packet lost packets by implementing a maximum waiting time for packet
arrival. Tmax is the waiting time used as the threshold to declare a arrival. Tmax is the waiting time used as the threshold to declare a
packet lost. Lost packets SHALL be designated as having undefined packet lost. Lost packets SHALL be designated as having undefined
delay. delay, and counted for the RLDNS metric.
The calculations on the delay (RTT) SHALL be performed on the The calculations on the delay (RTT) SHALL be performed on the
conditional distribution, conditioned on successful packet arrival conditional distribution, conditioned on successful packet arrival
within Tmax. Also, when all packet delays are stored, the process within Tmax. Also, when all packet delays are stored, the process
which calculates the RTT value MAY enforce the Tmax threshold on which calculates the RTT value MAY enforce the Tmax threshold on
stored values before calculations. See section 4.1 of [RFC3393] for stored values before calculations. See section 4.1 of [RFC3393] for
details on the conditional distribution to exclude undefined values details on the conditional distribution to exclude undefined values
of delay, and Section 5 of [RFC6703] for background on this analysis of delay, and Section 5 of [RFC6703] for background on this analysis
choice. choice.
skipping to change at page 29, line 9 skipping to change at page 30, line 26
sending times and receiving times for each successfully-arriving sending times and receiving times for each successfully-arriving
reply. Therefore, sequence numbers or other send-order reply. Therefore, sequence numbers or other send-order
identification MUST be retained at the Src or included with each identification MUST be retained at the Src or included with each
packet to dis-ambiguate packet reordering if it occurs. Sequence packet to dis-ambiguate packet reordering if it occurs. Sequence
number is part of the payload described under Fixed Parameters. number is part of the payload described under Fixed Parameters.
DNS Messages bearing Queries provide for random ID Numbers in the DNS Messages bearing Queries provide for random ID Numbers in the
Identification header field, so more than one query may be launched Identification header field, so more than one query may be launched
while a previous request is outstanding when the ID Number is used. while a previous request is outstanding when the ID Number is used.
IF a DNS response does not arrive within Tmax, the is IF a DNS response does not arrive within Tmax, the response time is
The Message ID SHALL be used to disambiguate the undefined, and RTDNS = 1. The Message ID SHALL be used to
successive queries. disambiguate the successive queries.
This would require support of ID generation and population in the @@@@ This would require support of ID generation and population in
Message. An alternative would be to use a random Source port on the the Message. An alternative would be to use a random Source port on
Query Message, but we would choose ONE before proceding. the Query Message, but we would choose ONE before proceding.
Refer to Section 4.4 of [RFC6673] for expanded discussion of the Refer to Section 4.4 of [RFC6673] for expanded discussion of the
instruction to "send a Type-P packet back to the Src as quickly as instruction to "send a Type-P packet back to the Src as quickly as
possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of
[RFC6673] presents additional requirements which shall be included in [RFC6673] presents additional requirements which shall be included in
the method of measurement for this metric. the method of measurement for this metric.
In addition to operations described in [RFC2681], the Src MUST parse In addition to operations described in [RFC2681], the Src MUST parse
subsequent reporting as a measured result, along with the Round-Trip subsequent reporting as a measured result, along with the Round-Trip
skipping to change at page 31, line 4 skipping to change at page 32, line 20
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.
Reciprocal_lambda average packet interval for Poisson Streams Reciprocal_lambda average packet interval for Poisson Streams
expressed in units of seconds, as a positive value of type expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of [RFC6020]) decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020])
with resolution of 0.0001 seconds (0.1 ms), and with lossless with resolution of 0.0001 seconds (0.1 ms), and with lossless
conversion to/from the 32-bit NTP timestamp as per section 6 of conversion to/from the 32-bit NTP timestamp as per section 6 of
[RFC5905]. [RFC5905].
Trunc Upper limit on Poisson distribution expressed in units of Trunc Upper limit on Poisson distribution expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = (see section 9.3 of [RFC6020]) with resolution of digits = 4 (see section 9.3 of [RFC6020]) with resolution of
0.0001 seconds (0.1 ms), and with lossless conversion to/from the 0.0001 seconds (0.1 ms), and with lossless conversion to/from the
32-bit NTP timestamp as per section 6 of [RFC5905] (values above 32-bit NTP timestamp as per section 6 of [RFC5905] (values above
this limit will be clipped and set to the limit value). (if fixed, this limit will be clipped and set to the limit value). (if fixed,
Trunc = 30.0000 seconds.) Trunc = 30.0000 seconds.)
ID The 16-bit identifier assigned by the program that generates the ID The 16-bit identifier assigned by the program that generates the
query, and which must vary in successive queries, see query, and which must vary in successive queries, see
Section 4.1.1 of [RFC1035]. This identifier is copied into the Section 4.1.1 of [RFC1035]. This identifier is copied into the
corresponding reply and can be used by the requester (Src) to corresponding reply and can be used by the requester (Src) to
match-up replies to outstanding queries. match-up replies to outstanding queries.
skipping to change at page 32, line 35 skipping to change at page 33, line 50
Rcode The value of the Rcode field in the DNS response header, Rcode The value of the Rcode field in the DNS response header,
expressed as a uint64 as specified in section 9.2 of [RFC6020]. expressed as a uint64 as specified in section 9.2 of [RFC6020].
Non-zero values convey errors in the response, and such replies Non-zero values convey errors in the response, and such replies
must be analyzed separately from successful requests. must be analyzed separately from successful requests.
6.4.3. Metric Units 6.4.3. Metric Units
<insert units for the measured results, and the reference <insert units for the measured results, and the reference
specification>. specification>.
Round-trip Delay, dT, is expressed in seconds. RTDNS: Round-trip Delay, dT, is expressed in seconds.
RTLDNS: the Logical value, where 1 = Lost and 0 = Received.
6.4.4. Calibration 6.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback at the Source calibration could be enabled with an internal loopback at the Source
host that includes as much of the measurement system as possible, host that includes as much of the measurement system as possible,
some form of isolation (e.g., deterministic delay) to avoid send- some form of isolation (e.g., deterministic delay) to avoid send-
receive interface contention. Some portion of the random and receive interface contention. Some portion of the random and
skipping to change at page 33, line 33 skipping to change at page 35, line 5
1.0 1.0
6.5.4. Revision Date 6.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
Additional (Informational) details for this entry Additional (Informational) details for this entry
7. UDP Poisson One-way Delay 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. Poisson One-way Delay, and one for UDP Poisson One-way Loss.
Registry "Name" below specifies a single registry entry, IANA Note: Registry "Name" below specifies a single registry entry,
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. 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, Reference Method categories are the same, thus this section proposes
Description, and Output Reference Method categories are the same, six closely-related registry entries. As a result, IANA is also
thus this section proposes closely-related registry entries. As asked to assign corresponding URNs and URLs to each Named Metric.
a result, IANA is also asked to assign corresponding URNs and URLs to
each Named Metric.
7.1. Summary 7.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.
7.1.1. ID (Identifier) 7.1.1. ID (Identifier)
<insert numeric identifier, an integer, one corresponding to each <insert numeric identifier, an integer, one corresponding to each
name below> name below>
IANA is asked to assign different numeric identifiers to each of the
six Metrics.
7.1.2. Name 7.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
OWDelay_Active_IP-UDP-Poisson- OWDelay_Active_IP-UDP-Poisson-
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss_Active_IP-UDP-Poisson-
7.1.3. URI and URL 7.1.3. URI and URL
URI: Prefix urn:ietf:metrics:perf:<name> URI: Prefix urn:ietf:metrics:perf:<name>
URL: http:\\www.iana.org\ ... <name> URL: http:\\www.iana.org\ ... <name>
7.1.4. Description 7.1.4. Description
This metric assesses the delay of a stream of packets exchanged OWDelay: This metric assesses the delay of a stream of packets
between two hosts (or measurement points), and reports the exchanged between two hosts (or measurement points), and reports the
<statistic> One-way delay for all successfully exchanged packets <statistic> One-way delay for all successfully exchanged packets
based on their conditional delay distribution. based on their conditional delay distribution.
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss: This metric assesses the loss ratio of a stream of packets
exchanged between two hosts (which are the two measurement points),
and the Output is the One-way loss ratio for all successfully
received packets expressed as a percentage.
7.2. Metric Definition 7.2. Metric Definition
This category includes columns to prompt the entry of all necessary This category includes columns to prompt the entry of all necessary
details related to the metric definition, including the RFC reference details related to the metric definition, including the RFC reference
and values of input factors, called fixed parameters. and values of input factors, called fixed parameters.
7.2.1. Reference Definition 7.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
For Delay:
Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One- Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-
Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC
7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc- 7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
editor.org/info/rfc7679>. editor.org/info/rfc7679>.
[RFC7679] [RFC7679]
Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC
6049, January 2011. 6049, January 2011.
skipping to change at page 35, line 43 skipping to change at page 37, line 25
Section 3.4 of [RFC7679] provides the reference definition of the Section 3.4 of [RFC7679] provides the reference definition of the
singleton (single value) One-way delay metric. Section 4.4 of singleton (single value) One-way delay metric. Section 4.4 of
[RFC7679] provides the reference definition expanded to cover a [RFC7679] provides the reference definition expanded to cover a
multi-value sample. Note that terms such as singleton and sample are multi-value sample. Note that terms such as singleton and sample are
defined in Section 11 of [RFC2330]. defined in Section 11 of [RFC2330].
Only successful packet transfers with finite delay are included in Only successful packet transfers with finite delay are included in
the sample, as prescribed in section 4.1.2 of [RFC6049]. the sample, as prescribed in section 4.1.2 of [RFC6049].
For loss:
Almes, G., Kalidini, S., Zekauskas, M., and A. Morton, Ed., "A One-
Way Loss Metric for IP Performance Metrics (IPPM)", RFC 7680, DOI
10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
rfc7680>.
Section 2.4 of [RFC7680] provides the reference definition of the
singleton (single value) one-way loss metric. Section 3.4 of
[RFC7680] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330].
7.2.2. Fixed Parameters 7.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be <list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when determined and embedded in the measurement system for use when
needed> needed>
Type-P: Type-P:
skipping to change at page 36, line 35 skipping to change at page 38, line 30
* Security features in use influence the number of Padding * Security features in use influence the number of Padding
octets. octets.
* 250 octets total, including the TWAMP format * 250 octets total, including the TWAMP format
Other measurement parameters: Other measurement parameters:
Tmax: a loss threshold waiting time with value 3.0, expressed in Tmax: a loss threshold waiting time with value 3.0, expressed in
units of seconds, as a positive value of type decimal64 with units of seconds, as a positive value of type decimal64 with
fraction digits = (see section 9.3 of [RFC6020]) and with fraction digits = 4 (see section 9.3 of [RFC6020]) and with
resolution of 0.0001 seconds (0.1 ms), with lossless conversion resolution of 0.0001 seconds (0.1 ms), with lossless conversion
to/from the 32-bit NTP timestamp as per section 6 of [RFC5905]. to/from the 32-bit NTP timestamp as per section 6 of [RFC5905].
See the Packet Stream generation category for two additional Fixed See the Packet Stream generation category for two additional Fixed
Parameters. Parameters.
7.3. Method of Measurement 7.3. Method of Measurement
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
skipping to change at page 37, line 4 skipping to change at page 38, line 47
7.3. Method of Measurement 7.3. Method of Measurement
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 methods for implementations. unambiguous methods for implementations.
7.3.1. Reference Method 7.3.1. Reference Method
<for metric, insert relevant section references and supplemental <for metric, insert relevant section references and supplemental
info> info>
The methodology for this metric is defined as Type-P-One-way-Delay- The methodology for this metric is defined as Type-P-One-way-Delay-
Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of
[RFC7679] using the Type-P and Tmax defined under Fixed Parameters. [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
The reference method distinguishes between long-delayed packets and The reference method distinguishes between long-delayed packets and
lost packets by implementing a maximum waiting time for packet lost packets by implementing a maximum waiting time for packet
arrival. Tmax is the waiting time used as the threshold to declare a arrival. Tmax is the waiting time used as the threshold to declare a
packet lost. Lost packets SHALL be designated as having undefined packet lost. Lost packets SHALL be designated as having undefined
delay. delay, and counted for the OWLoss metric.
The calculations on the one-way delay SHALL be performed on the The calculations on the one-way delay SHALL be performed on the
conditional distribution, conditioned on successful packet arrival conditional distribution, conditioned on successful packet arrival
within Tmax. Also, when all packet delays are stored, the process within Tmax. Also, when all packet delays are stored, the process
which calculates the one-way delay value MAY enforce the Tmax which calculates the one-way delay value MAY enforce the Tmax
threshold on stored values before calculations. See section 4.1 of threshold on stored values before calculations. See section 4.1 of
[RFC3393] for details on the conditional distribution to exclude [RFC3393] for details on the conditional distribution to exclude
undefined values of delay, and Section 5 of [RFC6703] for background undefined values of delay, and Section 5 of [RFC6703] for background
on this analysis choice. on this analysis choice.
skipping to change at page 38, line 18 skipping to change at page 40, line 13
packet send times, (truncating the distribution as specified in the packet send times, (truncating the distribution as specified in the
Parameter Trunc), and the Src sends each packet at the computed Parameter Trunc), and the Src sends each packet at the computed
times. times.
Note that Trunc is the upper limit on inter-packet times in the Note that Trunc is the upper limit on inter-packet times in the
Poisson distribution. A random value greater than Trunc is set equal Poisson distribution. A random value greater than Trunc is set equal
Reciprocal_lambda average packet interval for Poisson Streams Reciprocal_lambda average packet interval for Poisson Streams
expressed in units of seconds, as a positive value of type expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = (see section 9.3 of [RFC6020]) decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020])
with resolution of 0.0001 seconds (0.1 ms), and with lossless with resolution of 0.0001 seconds (0.1 ms), and with lossless
conversion to/from the 32-bit NTP timestamp as per section 6 of conversion to/from the 32-bit NTP timestamp as per section 6 of
[RFC5905]. Reciprocal_lambda = 1 packet per second. [RFC5905]. Reciprocal_lambda = 1 packet per second.
Trunc Upper limit on Poisson distribution expressed in units of Trunc Upper limit on Poisson distribution expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = (see section 9.3 of [RFC6020]) with resolution of digits = 4 (see section 9.3 of [RFC6020]) with resolution of
0.0001 seconds (0.1 ms), and with lossless conversion to/from the 0.0001 seconds (0.1 ms), and with lossless conversion to/from the
32-bit NTP timestamp as per section 6 of [RFC5905] (values above 32-bit NTP timestamp as per section 6 of [RFC5905] (values above
this limit will be clipped and set to the limit value). Trunc = this limit will be clipped and set to the limit value). Trunc =
30.0000 seconds. 30.0000 seconds.
7.3.3. Traffic Filtering (observation) Details 7.3.3. Traffic Filtering (observation) Details
NA NA
7.3.4. Sampling Distribution 7.3.4. Sampling Distribution
skipping to change at page 40, line 10 skipping to change at page 42, line 5
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
Tf the end of a measurement interval, (format "date-and-time" as Tf the end of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
For LossRatio -- the count of lost packets to total packets sent is
the basis for the loss ratio calculation as per Section 4.1 of
[RFC7680].
For each <statistic>, one of the following sub-sections apply: For each <statistic>, one of the following sub-sections apply:
7.4.2.1. Percentile95 7.4.2.1. Percentile95
The 95th percentile SHALL be calculated using the conditional The 95th percentile SHALL be calculated using the conditional
distribution of all packets with a finite value of One-way delay distribution of all packets with a finite value of One-way delay
(undefined delays are excluded), a single value as follows: (undefined delays are excluded), a single value as follows:
See section 4.1 of [RFC3393] for details on the conditional See section 4.1 of [RFC3393] for details on the conditional
distribution to exclude undefined values of delay, and Section 5 of distribution to exclude undefined values of delay, and Section 5 of
skipping to change at page 42, line 32 skipping to change at page 44, line 32
0.000000001 seconds (1.0 ns), and with lossless conversion to/from 0.000000001 seconds (1.0 ns), and with lossless conversion to/from
the 64-bit NTP timestamp as per section 6 of RFC [RFC5905] the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]
7.4.3. Metric Units 7.4.3. Metric Units
<insert units for the measured results, and the reference <insert units for the measured results, and the reference
specification>. specification>.
The <statistic> of One-way Delay is expressed in seconds. The <statistic> of One-way Delay is expressed in seconds.
The One-way Loss Ratio is expressed as a percentage of lost packets
to total packets sent.
7.4.4. Calibration 7.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback that includes calibration could be enabled with an internal loopback that includes
as much of the measurement system as possible, performs address as much of the measurement system as possible, performs address
manipulation as needed, and provides some form of isolation (e.g., manipulation as needed, and provides some form of isolation (e.g.,
deterministic delay) to avoid send-receive interface contention. deterministic delay) to avoid send-receive interface contention.
Some portion of the random and systematic error can be characterized Some portion of the random and systematic error can be characterized
this way. this way.
skipping to change at page 43, line 46 skipping to change at page 46, line 5
1.0 1.0
7.5.4. Revision Date 7.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
Additional (Informational) details for this entry Additional (Informational) details for this entry
8. UDP Periodic One-way Delay 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. Periodic One-way Delay, and one for UDP Periodic One-way Loss.
Registry "Name" below specifies a single registry entry, IANA Note: Registry "Name" below specifies a single registry entry,
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. 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, Reference Method categories are the same, thus this section proposes
Description, and Output Reference Method categories are the same, six closely-related registry entries. As a result, IANA is also
thus this section proposes closely-related registry entries. As asked to assign corresponding URNs and URLs to each Named Metric.
a result, IANA is also asked to assign corresponding URNs and URLs to
each Named Metric.
8.1. Summary 8.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.
8.1.1. ID (Identifier) 8.1.1. ID (Identifier)
<insert numeric identifier, an integer, one corresponding to each <insert numeric identifier, an integer, one corresponding to each
name below> name below>
IANA is asked to assign a different numeric identifiers to each of
the six Metrics.
8.1.2. Name 8.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
OWDelay_Active_IP-UDP-Periodic- OWDelay_Active_IP-UDP-Periodic-
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss_Active_IP-UDP-Periodic-
8.1.3. URIs 8.1.3. URIs
URI: Prefix urn:ietf:metrics:perf:<name> URI: Prefix urn:ietf:metrics:perf:<name>
URL: http:\\www.iana.org\ ... <name> URL: http:\\www.iana.org\ ... <name>
8.1.4. Description 8.1.4. Description
This metric assesses the delay of a stream of packets exchanged OWDelay: This metric assesses the delay of a stream of packets
between two hosts (or measurement points), and reports the exchanged between two hosts (or measurement points), and reports the
<statistic> One-way delay for all successfully exchanged packets <statistic> One-way delay for all successfully exchanged packets
based on their conditional delay distribution. based on their conditional delay distribution.
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss: This metric assesses the loss ratio of a stream of packets
exchanged between two hosts (which are the two measurement points),
and the Output is the One-way loss ratio for all successfully
received packets expressed as a percentage.
8.2. Metric Definition 8.2. Metric Definition
This category includes columns to prompt the entry of all necessary This category includes columns to prompt the entry of all necessary
details related to the metric definition, including the RFC reference details related to the metric definition, including the RFC reference
and values of input factors, called fixed parameters. and values of input factors, called fixed parameters.
8.2.1. Reference Definition 8.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
For Delay:
Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One- Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-
Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC
7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc- 7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
editor.org/info/rfc7679>. editor.org/info/rfc7679>.
[RFC7679] [RFC7679]
Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC
6049, January 2011. 6049, January 2011.
skipping to change at page 46, line 8 skipping to change at page 48, line 25
Section 3.4 of [RFC7679] provides the reference definition of the Section 3.4 of [RFC7679] provides the reference definition of the
singleton (single value) One-way delay metric. Section 4.4 of singleton (single value) One-way delay metric. Section 4.4 of
[RFC7679] provides the reference definition expanded to cover a [RFC7679] provides the reference definition expanded to cover a
multi-value sample. Note that terms such as singleton and sample are multi-value sample. Note that terms such as singleton and sample are
defined in Section 11 of [RFC2330]. defined in Section 11 of [RFC2330].
Only successful packet transfers with finite delay are included in Only successful packet transfers with finite delay are included in
the sample, as prescribed in section 4.1.2 of [RFC6049]. the sample, as prescribed in section 4.1.2 of [RFC6049].
For loss:
Almes, G., Kalidini, S., Zekauskas, M., and A. Morton, Ed., "A One-
Way Loss Metric for IP Performance Metrics (IPPM)", RFC 7680, DOI
10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
rfc7680>.
Section 2.4 of [RFC7680] provides the reference definition of the
singleton (single value) one-way loss metric. Section 3.4 of
[RFC7680] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330].
8.2.2. Fixed Parameters 8.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be <list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when determined and embedded in the measurement system for use when
needed> needed>
Type-P: Type-P:
skipping to change at page 46, line 48 skipping to change at page 49, line 30
* Security features in use influence the number of Padding * Security features in use influence the number of Padding
octets. octets.
* 142 octets total, including the TWAMP format * 142 octets total, including the TWAMP format
Other measurement parameters: Other measurement parameters:
Tmax: a loss threshold waiting time with value 3.0, expressed in Tmax: a loss threshold waiting time with value 3.0, expressed in
units of seconds, as a positive value of type decimal64 with units of seconds, as a positive value of type decimal64 with
fraction digits = (see section 9.3 of [RFC6020]) and with fraction digits = 4 (see section 9.3 of [RFC6020]) and with
resolution of 0.0001 seconds (0.1 ms), with lossless conversion resolution of 0.0001 seconds (0.1 ms), with lossless conversion
to/from the 32-bit NTP timestamp as per section 6 of [RFC5905]. to/from the 32-bit NTP timestamp as per section 6 of [RFC5905].
See the Packet Stream generation category for two additional Fixed See the Packet Stream generation category for two additional Fixed
Parameters. Parameters.
8.3. Method of Measurement 8.3. Method of Measurement
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
skipping to change at page 47, line 27 skipping to change at page 50, line 9
info> info>
The methodology for this metric is defined as Type-P-One-way-Delay- The methodology for this metric is defined as Type-P-One-way-Delay-
Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of
[RFC7679] using the Type-P and Tmax defined under Fixed Parameters. [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
The reference method distinguishes between long-delayed packets and The reference method distinguishes between long-delayed packets and
lost packets by implementing a maximum waiting time for packet lost packets by implementing a maximum waiting time for packet
arrival. Tmax is the waiting time used as the threshold to declare a arrival. Tmax is the waiting time used as the threshold to declare a
packet lost. Lost packets SHALL be designated as having undefined packet lost. Lost packets SHALL be designated as having undefined
delay. delay, and counted for the OWLoss metric.
The calculations on the one-way delay SHALL be performed on the The calculations on the one-way delay SHALL be performed on the
conditional distribution, conditioned on successful packet arrival conditional distribution, conditioned on successful packet arrival
within Tmax. Also, when all packet delays are stored, the process within Tmax. Also, when all packet delays are stored, the process
which calculates the one-way delay value MAY enforce the Tmax which calculates the one-way delay value MAY enforce the Tmax
threshold on stored values before calculations. See section 4.1 of threshold on stored values before calculations. See section 4.1 of
[RFC3393] for details on the conditional distribution to exclude [RFC3393] for details on the conditional distribution to exclude
undefined values of delay, and Section 5 of [RFC6703] for background undefined values of delay, and Section 5 of [RFC6703] for background
on this analysis choice. on this analysis choice.
skipping to change at page 50, line 14 skipping to change at page 52, line 42
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
Tf the end of a measurement interval, (format "date-and-time" as Tf the end of a measurement interval, (format "date-and-time" as
[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]. [RFC2330].
For LossRatio -- the count of lost packets to total packets sent is
the basis for the loss ratio calculation as per Section 4.1 of
[RFC7680].
For each <statistic>, one of the following sub-sections apply: For each <statistic>, one of the following sub-sections apply:
8.4.2.1. Percentile95 8.4.2.1. Percentile95
The 95th percentile SHALL be calculated using the conditional The 95th percentile SHALL be calculated using the conditional
distribution of all packets with a finite value of One-way delay distribution of all packets with a finite value of One-way delay
(undefined delays are excluded), a single value as follows: (undefined delays are excluded), a single value as follows:
See section 4.1 of [RFC3393] for details on the conditional See section 4.1 of [RFC3393] for details on the conditional
distribution to exclude undefined values of delay, and Section 5 of distribution to exclude undefined values of delay, and Section 5 of
skipping to change at page 52, line 38 skipping to change at page 55, line 18
0.000000001 seconds (1.0 ns), and with lossless conversion to/from 0.000000001 seconds (1.0 ns), and with lossless conversion to/from
the 64-bit NTP timestamp as per section 6 of RFC [RFC5905] the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]
8.4.3. Metric Units 8.4.3. Metric Units
<insert units for the measured results, and the reference <insert units for the measured results, and the reference
specification>. specification>.
The <statistic> of One-way Delay is expressed in seconds. The <statistic> of One-way Delay is expressed in seconds.
The One-way Loss Ratio is expressed as a percentage of lost packets
to total packets sent.
8.4.4. Calibration 8.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback that includes calibration could be enabled with an internal loopback that includes
as much of the measurement system as possible, performs address as much of the measurement system as possible, performs address
manipulation as needed, and provides some form of isolation (e.g., manipulation as needed, and provides some form of isolation (e.g.,
deterministic delay) to avoid send-receive interface contention. deterministic delay) to avoid send-receive interface contention.
Some portion of the random and systematic error can be characterized Some portion of the random and systematic error can be characterized
this way. this way.
End of changes. 88 change blocks.
256 lines changed or deleted 392 lines changed or added

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