draft-ietf-ippm-initial-registry-01.txt   draft-ietf-ippm-initial-registry-02.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: May 2, 2017 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
, 2016 October 29, 2016
Initial Performance Metric Registry Entries Initial Performance Metric Registry Entries
draft-ietf-ippm-initial-registry-0 draft-ietf-ippm-initial-registry-02
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:
* All section 4 and 5 parameters reference YANG types for alternate * All section 4 and 5 parameters reference YANG types for alternate
data formats. data formats.
* implementation of standard naming format for parameters. * implementation of standard naming format for parameters.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 , 2017. This Internet-Draft will expire on May 2, 2017.
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Registry Categories and Columns . . . . . . . . . . . . . . . 3. Registry Categories and Columns . . . . . . . . . . . . . . . 7
4. UDP Round-trip Latency Registry Entry . . . . . . . . . . . . 8 4. UDP Round-trip Latency Registry Entry . . . . . . . . . . . . 8
4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 8
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.6. Version (of Registry Format) . . . . . . . . . . . . 9
4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9
4.2.1. Reference Definition . . . . . . . . . . . . . . . . 9 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 9
4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10
4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11
4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11
4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 12 4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 12
4.3.3. Traffic Filtering (observation) Details . . . . . . . 1 4.3.3. Traffic Filtering (observation) Details . . . . . . . 12
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 . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 14 4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2. . . . . . . . . . . . . . . . . 4.4.2. Reference Definition . . . . . . . . . . . . . . . . 14
4.4.3. . . . . . . . . . . . . . . . . . . . . 15 4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 15
4.4.4. . . . . . . . . . . . . . . . . . . . . 15 4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 15
4.5. Administrative items . . . . . . . . . . . . . . . . . . 4.5. Administrative items . . . . . . . . . . . . . . . . . . 16
4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 16 4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 18
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 1 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 19
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19
5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.2. . . . . . . . . . . . . . . . . 22 5.4.2. Reference Definition . . . . . . . . . . . . . . . . 22
5.4.3. . . . . . . . . . . . . . . . . . . . . 5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 23
5.4.4. . . . . . . . . . . . . . . . . . . . . 5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 23
5.5. Administrative items . . . . . . . . . . . . . . . . . . 5.5. Administrative items . . . . . . . . . . . . . . . . . . 24
5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 24
5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 24
5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 24
5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 24
6. DNS Response Latency Registry Entry . . . . . . . . . . . . . 6. DNS Response Latency Registry Entry . . . . . . . . . . . . . 24
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 24
6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 25
6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 6.1.5. Change Controller . . . . . . . . . . . . . . . . . . 25
6.2.1. Reference Definition . . . . . . . . . . . . . . . . 6.1.6. Version (of Registry Format) . . . . . . . . . . . . 25
6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 25
6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 25
6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 26
6.3.2. Packet Generation Stream . . . . . . . . . . . . . . 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 27
6.3.3. Traffic Filtering (observation) Details . . . . . . . 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 27
6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 6.3.2. Packet Generation Stream . . . . . . . . . . . . . . 28
6.3.5. Run-time Parameters and Data Format . . . . . . . . . 6.3.3. Traffic Filtering (observation) Details . . . . . . . 29
6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 29
6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.5. Run-time Parameters and Data Format . . . . . . . . . 29
6.4.1. Type/Value (two diff terms used) . . . . . . . . . . 6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4.2. . . . . . . . . . . . . . . . . 6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4.3. . . . . . . . . . . . . . . . . . . . . 6.4.1. Type/Value (two diff terms used) . . . . . . . . . . 30
6.4.4. . . . . . . . . . . . . . . . . . . . . 6.4.2. Reference Definition . . . . . . . . . . . . . . . . 31
6.5. Administrative items . . . . . . . . . . . . . . . . . . 6.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 31
6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 6.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 32
6.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 6.5. Administrative items . . . . . . . . . . . . . . . . . . 32
6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 32
6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 6.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 32
6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 32
7. UDP Poisson One-way Delay Registry Entries . . . . . . . . . 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 32
7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 32
7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 7. UDP Poisson One-way Delay Registry Entries . . . . . . . . . 32
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 33
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 33
7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 33
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 33
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 33
7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 33
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 34
7.3.2. Packet Generation Stream . . . . . . . . . . . . . . 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 35
7.3.3. Traffic Filtering (observation) Details . . . . . . . 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 35
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 7.3.2. Packet Generation Stream . . . . . . . . . . . . . . 35
7.3.5. Run-time Parameters and Data Format . . . . . . . . . 7.3.3. Traffic Filtering (observation) Details . . . . . . . 36
7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 36
7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.5. Run-time Parameters and Data Format . . . . . . . . . 36
7.4.1. Type/Value (two diff terms used) . . . . . . . . . . 7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 37
7.4.2. . . . . . . . . . . . . . . . . 7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.4.3. . . . . . . . . . . . . . . . . . . . . 7.4.1. Type/Value (two diff terms used) . . . . . . . . . . 37
7.4.4. . . . . . . . . . . . . . . . . . . . . 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 37
7.5. Administrative items . . . . . . . . . . . . . . . . . . 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 39
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 39
7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 7.5. Administrative items . . . . . . . . . . . . . . . . . . 39
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 39
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 40
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 40
8. UDP Periodic One-way Delay Registry Entries . . . . . . . . . 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 40
8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 40
8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 8. UDP Periodic One-way Delay Registry Entries . . . . . . . . . 40
8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 40
8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 40
8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 8.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 41
8.2.1. Reference Definition . . . . . . . . . . . . . . . . 8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 41
8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 41
8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 8.2.1. Reference Definition . . . . . . . . . . . . . . . . 41
8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 42
8.3.2. Packet Generation Stream . . . . . . . . . . . . . . 8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 42
8.3.3. Traffic Filtering (observation) Details . . . . . . . 8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 43
8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 8.3.2. Packet Generation Stream . . . . . . . . . . . . . . 43
8.3.5. Run-time Parameters and Data Format . . . . . . . . . 8.3.3. Traffic Filtering (observation) Details . . . . . . . 43
8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 44
8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.5. Run-time Parameters and Data Format . . . . . . . . . 44
8.4.1. Type/Value (two diff terms used) . . . . . . . . . . 8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 44
8.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.4.3. . . . . . . . . . . . . . . . . . . . . 8.4.1. Type/Value (two diff terms used) . . . . . . . . . . 45
8.4.4. . . . . . . . . . . . . . . . . . . . . 8.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 45
8.5. Administrative items . . . . . . . . . . . . . . . . . . 8.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 47
8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 8.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 47
8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 8.5. Administrative items . . . . . . . . . . . . . . . . . . 47
8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 47
8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 47
8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 47
9. BLANK Registry Entry . . . . . . . . . . . . . . . . . 8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 48
9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 48
9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9. ver08 BLANK Registry Entry . . . . . . . . . . . . . . . . . 48
9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.1.3. . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 48
9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 48
9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 48
9.2.1. Reference Definition . . . . . . . . . . . . . . . . 9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 48
9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 9.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 48
9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 9.1.6. Change Controller . . . . . . . . . . . . . . . . . . 48
9.1.7. Version (of Registry Format) . . . . . . . . . . . . 48
9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 49
9.2.1. Reference Definition . . . . . . . . . . . . . . . . 49
9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 49
9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 49
9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 49 9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 49
9.3.2. Packet . . . . . . . . . . . . . . 49 9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 49
9.3.3. Traffic Filtering (observation) Details . . . . . . . 49 9.3.3. Traffic Filtering (observation) Details . . . . . . . 49
9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 49 9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 49
9.3.5. Run-time Parameters and Data Format . . . . . . . . . 9.3.5. Run-time Parameters and Data Format . . . . . . . . . 50
9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 50
9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.4.1. . . . . . . . . . . 9.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 50
. . . . . . . . . . . . . . . . . . . . . 9.4.2. Reference Definition . . . . . . . . . . . . . . . . 50
. . . . . . . . . . . . . . . . . . . . . . 50 9.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 50
9.4.4. . . . . . . . . . . . . . . . . . . . . 50 9.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 50
9.5. Administrative items . . . . . . . . . . . . . . . . . . 50 9.5. Administrative items . . . . . . . . . . . . . . . . . . 50
9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 50 9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 50
9.5.2. Requestor . . . . . . . . . . . . . . . . . . 50 9.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 50
9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 50 9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 50
9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 51
9.6. Comments and Remarks . . . . . . . . . . . . . . . . . .
10. Registry Entry . . . . . . . . . . . . . . . 51 9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 51
10.1. . . . . . . . . . . . . . . . . . . . . . . . 10. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 51
. . . . . . . . . . . . . . . . . . 51 10.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 51
10.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 51
10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 51 10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 51
10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 51 10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 51
10.1.4. 10.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 51
10.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 51
10.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 51
10.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 52
10.1.8. Description . . . . . . . . . . . . . . . . . . . . 52
10.1.9. Reference Specification(s) . . . . . . . . . . . . . 52
10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 52
10.2.1. Reference Definition . . . . . . . . . . . . . . . . 52
10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 52
10.3. Method of Measurement . . . . . . . . . . . . . . . . . 53
10.3.1. Reference Method . . . . . . . . . . . . . . . . . . 53
10.3.2. Stream Type and Stream Parameters . . . . . . . . . 53
10.3.3. Output Type and Data Format . . . . . . . . . . . . 53
10.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 54
10.3.5. Run-time Parameters and Data Format . . . . . . . . 54
10.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 55
11. Revision History . . . . . . . . . . . . . . . . . . . . . . 56
12. Security Considerations . . . . . . . . . . . . . . . . . . . 56
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
15.1. Normative References . . . . . . . . . . . . . . . . . . 57
15.2. Informative References . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60
Status . . . . . . . . . . . . . . . . . . . . . . .
Requestor . . . . . . . . . . . . . . . . . . . . .
Revision . . . . . . . . . . . . . . . . . . . . . .
Revision Date . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . .
Reference Specification(s) . . . . . . . . . . . . .
Metric Definition . . . . . . . . . . . . . . . . . . .
Reference Definition . . . . . . . . . . . . . . . .
Fixed Parameters . . . . . . . . . . . . . . . . . .
Method of Measurement . . . . . . . . . . . . . . . . .
Reference Method . . . . . . . . . . . . . . . . . .
Stream Type and Stream Parameters . . . . . . . . .
Output Type and Data Format . . . . . . . . . . . .
Metric Units . . . . . . . . . . . . . . . . . . . .
Run-time Parameters and Data Format . . . . . . . .
Comments and Remarks . . . . . . . . . . . . . . . . . .
Revision History . . . . . . . . . . . . . . . . . . . . . .
Security Considerations . . . . . . . . . . . . . . . . . . .
IANA Considerations . . . . . . . . . . . . . . . . . . . . .
Acknowledgements . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . .
Normative References . . . . . . . . . . . . . . . . . .
Informative References . . . . . . . . . . . . . . . . .
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .
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 11 skipping to change at page 8, line 5
requirement for Expert Review. Note that all are Active Performance requirement for Expert Review. Note that all are Active Performance
Metrics, which are based on RFCs prepared in the IPPM working group Metrics, which are based on RFCs prepared in the IPPM working group
of the IETF, according to their framework [RFC2330] and its updates. of the IETF, according to their framework [RFC2330] and its updates.
3. Registry Categories and Columns 3. Registry Categories and Columns
This section provides the categories and columns of the registry, for This section provides the categories and columns of the registry, for
easy reference. An entry (row) therefore gives a complete easy reference. An entry (row) therefore gives a complete
description of a Registered Metric. description of a Registered Metric.
Registry Categories and Columns, shown as Registry Categories and Columns, shown as
Category Category
------------------ ------------------
Column | Column | Column | Column |
Summary
------------------------------------------------------------------------
Reference | | Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver |
Metric Definition
-----------------------------------------
Reference | Reference Definition | Fixed Parameters |
|
Output Method of Measurement
---------------------------------------------------------------------
Type | Reference | Units | Reference | Packet | Traffic | Sampling | Run-time | Role |
| Definition | | Method | Stream | Filter | Distribution | Parameters | |
| Generation |
Output
-----------------------------------------
Type | Reference | Units | Calibration |
| Definition | | |
---------------------------------- ----------------------------------
Status |Request | Rev | Rev.Date | Status |Request | Rev | Rev.Date |
-------------------- --------------------
4. UDP Round-trip Latency Registry Entry 4. UDP Round-trip Latency Registry Entry
This section gives an initial registry entry for the UDP Round-trip This section gives an initial registry entry for the UDP Round-trip
Latency. Latency.
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 this section can become two or more closely-related can be split and this section can become two or more closely-related
skipping to change at page 9, line 25 skipping to change at page 9, line 13
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>
4.1.2. Name 4.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
RTDelay_Active_tile RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile
4.1.3. URIs 4.1.3. URIs
URN: Prefix urn:ietf:params:performance:metric:<name> URN: Prefix urn:ietf:params:performance:metric:<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 This metric assesses the delay of a stream of packets exchanged
between two hosts (which are the two measurement points), and the between two hosts (which are the two measurement points), and the
Output is the Round-trip delay for all successfully exchanged packets Output is the Round-trip delay for all successfully exchanged packets
expressed as the 95th percentile of their conditional delay expressed as the 95th percentile of their conditional delay
distribution. distribution.
4.1.5. Change Controller
IETF
4.1.6. Version (of Registry Format)
1.0
4.2. Metric Definition 4.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.
4.2.1. Reference Definition 4.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
skipping to change at page 14, line 46 skipping to change at page 14, line 38
<insert name of the output type, raw or a selected summary statistic> <insert name of the output type, raw or a selected summary statistic>
Percentile -- for the conditional distribution of all packets with a Percentile -- for the conditional distribution of all packets with a
valid value of Round-trip delay (undefined delays are excluded), a valid value of Round-trip delay (undefined delays are excluded), a
single value corresponding to the 95th percentile, as follows: single value corresponding to the 95th percentile, 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
The percentile = 95, meaning that the reported delay, "", 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() >= 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.
4.4.2. 4.4.2. Reference Definition
<describe the 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 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].
Raw -- REMOVED IN VERSION 01 Raw -- REMOVED IN VERSION 01
For Act_IP_UDP_Round-trip_Delay_Poisson_95th-percentile: For Act_IP_UDP_Round-trip_Delay_Poisson_95th-percentile:
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 per section 6 of RFC [RFC5905] the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]
4.4.3. 4.4.3. Metric Units
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.
4.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback that includes
as much of the measurement system as possible, performs address
manipulation as needed, and provides some form of isolation (e.g.,
deterministic delay) to avoid send-receive interface contention.
Some portion of the random and systematic error can be characterized
this way.
When a measurement controller requests a calibration measurement, the
loopback is applied and the result is output in the same format as a
normal measurement with additional indication that it is a
calibration result.
Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system
noise, and thus inaccurate.
4.5.1. Status 4.5.1. Status
<current or deprecated> <current or deprecated>
4.5.2. Requestor (keep?) 4.5.2. Requestor (keep?)
name or RFC, etc. name or RFC, etc.
skipping to change at page 16, line 45 skipping to change at page 16, line 51
<skipping some Summary columns for now> <skipping some Summary columns for now>
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
<insert name according to metric naming convention> <insert name according to metric naming convention>
OWPDV_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile
5.1.3. URIs 5.1.3. URIs
URI: Prefix urn:ietf:metric:<name> URI: Prefix urn:ietf:metric:<name>
URL: http://<TBD by IANA>/<name> URL: http://<TBD by IANA>/<name>
5.1.4. Description 5.1.4. Description
An assessment of packet delay variation with respect to the minimum An assessment of packet delay variation with respect to the minimum
delay observed on the stream, and the Output is expressed as the 95th delay observed on the stream, and the Output is expressed as the 95th
percentile of the packet delay variation distribution. percentile of the packet delay variation distribution.
5.1.5. Change Controller
<org or person >
5.1.6. Version (of Registry Format)
1.0
5.2. Metric Definition 5.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.
5.2.1. Reference Definition 5.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
skipping to change at page 22, line 4 skipping to change at page 22, line 13
Dst waits for each packet from Src. Dst waits for each packet from 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
<insert name of the output type, raw or a selected summary statistic> <insert name of the output type, raw or a selected summary statistic>
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:
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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
The percentile = 95, meaning that the reported delay, "", The percentile = 95, meaning that the reported delay, "95Percentile",
is the smallest value of one-way PDV for which the Empirical is the smallest value of one-way PDV for which the Empirical
Distribution Function (EDF), F() >= 95% of the singleton Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
one-way PDV values in the conditional distribution. See section 11.3 one-way PDV values in the conditional distribution. See section 11.3
of [RFC2330] for the definition of the percentile statistic using the of [RFC2330] for the definition of the percentile statistic using the
EDF. EDF.
5.4.2. 5.4.2. Reference Definition
< data format for each type of result> <the output type and data format for each type of result>
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 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].
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 per section 6 of RFC [RFC5905] the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]
5.4.3. 5.4.3. Metric Units
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 one-way PDV is expressed in seconds. The 95th Percentile of one-way PDV is expressed in seconds.
5.4.4. Calibration
Section 3.7.3 of [RFC7679] provides a means to quantify the
systematic and random errors of a time measurement. In-situ
calibration could be enabled with an internal loopback that includes
as much of the measurement system as possible, performs address
manipulation as needed, and provides some form of isolation (e.g.,
deterministic delay) to avoid send-receive interface contention.
Some portion of the random and systematic error can be characterized
this way.
For one-way delay measurements, the error calibration must include an
assessment of the internal clock synchronization with its external
reference (this internal clock is supplying timestamps for
measurement). In practice, the time offsets of clocks at both the
source and destination are needed to estimate the systematic error
due to imperfect clock synchronization (the time offsets are
smoothed, thus the random variation is not usually represented in the
results).
time_offset The time value of the result is expressed in units of
seconds, as a signed value of type decimal64 with fraction digits
= 9 (see section 9.3 of [RFC6020]) with resolution of 0.000000001
seconds (1.0 ns), and with lossless conversion to/from the 64-bit
NTP timestamp as per section 6 of RFC [RFC5905]
When a measurement controller requests a calibration measurement, the
loopback is applied and the result is output in the same format as a
normal measurement with additional indication that it is a
calibration result. In any measurement, the measurement function
SHOULD report its current estimate of time offset as an indicator of
the degree of synchronization.
Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system
noise, and thus inaccurate.
5.5.1. Status 5.5.1. Status
<current or depricated> <current or depricated>
5.5.2. Requestor (keep?) 5.5.2. Requestor (keep?)
<name of individual or RFC, etc.> <name of individual or RFC, etc.>
skipping to change at page 24, line 9 skipping to change at page 25, line 9
<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>
6.1.2. Name 6.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
RTDNS_Active_tile RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile
6.1.3. URI 6.1.3. URI
URI: Prefix urn:ietf: URI: Prefix urn:ietf:metric:<name>
URL: 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 This metric assesses the response time, the interval from the query
transmission to the response. transmission to the response.
6.1.5. Change Controller
IETF
6.1.6. Version (of Registry Format)
1.0
6.2. Metric Definition 6.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.
6.2.1. Reference Definition 6.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
skipping to change at page 29, line 44 skipping to change at page 31, line 9
Raw -- for each packet sent, pairs of values. Raw -- for each packet sent, pairs of values.
>>> and the status of the response, only assigning values to >>> and the status of the response, only assigning values to
successful query-response pairs. successful query-response pairs.
Percentile -- for the conditional distribution of all packets with a Percentile -- for the conditional distribution of all packets with a
valid value of Round-trip delay (undefined delays are excluded), a valid value of Round-trip delay (undefined delays are excluded), a
single value corresponding to the 95th percentile. single value corresponding to the 95th percentile.
6.4.2. 6.4.2. Reference Definition
<describe the data format for each type of result> <describe the data format for each type of result>
Raw -- for each packet sent, pairs of values as follows: Raw -- for each packet sent, pairs of values as follows:
o T, the time when the packet was sent from Src, 128-bit NTP Date o T, the time when the packet was sent from Src, 128-bit NTP Date
Format, see section 6 of [RFC5905]) Format, see section 6 of [RFC5905])
o dT, a value of Round-trip delay, format is *similar to* the 32-bit o dT, a value of Round-trip delay, format is *similar to* the 32-bit
short NTP Time format in Section 6 of [RFC5905] and is as follows: short NTP Time format in Section 6 of [RFC5905] and is as follows:
skipping to change at page 30, line 33 skipping to change at page 31, line 46
See section 4.3 of [RFC3393] for details on the percentile statistic See section 4.3 of [RFC3393] for details on the percentile statistic
(where Round-trip delay should be substituted for "ipdv"). (where Round-trip delay should be substituted for "ipdv").
The percentile = 95. The percentile = 95.
Data format is a 32-bit signed floating point value, *similar to* the Data format is a 32-bit signed floating point value, *similar to* the
32-bit short NTP Time format in Section 6 of [RFC5905] and is as 32-bit short NTP Time format in Section 6 of [RFC5905] and is as
follows: the first 16 bits represent the *signed* integer number of follows: the first 16 bits represent the *signed* integer number of
seconds; the next 16 bits represent the fractional part of a second. seconds; the next 16 bits represent the fractional part of a second.
6.4.3. 6.4.3. Metric Units
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. Round-trip Delay, dT, is expressed in seconds.
The 95th Percentile of Round-trip Delay is expressed in seconds. The 95th Percentile of Round-trip Delay is expressed in seconds.
6.4.4. Calibration
<pointer to >
6.5.1. Status 6.5.1. Status
<current or depricated> <current or depricated>
6.5.2. Requestor (keep?) 6.5.2. Requestor (keep?)
name or RFC, etc. name or RFC, etc.
6.5.3. Revision 6.5.3. Revision
skipping to change at page 32, line 9 skipping to change at page 33, line 14
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>
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-
7.1.3. URI and URL 7.1.3. URI and URL
URI: Prefix urn:ietf:params:performance:metric...<name> URI: Prefix urn:ietf:params:performance:metric...<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 This metric assesses the delay of a stream of packets exchanged
skipping to change at page 32, line 47 skipping to change at page 33, line 51
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.>
Almes, G., Kalidindi, S., Zekauskas, "A Delay Metric Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-
for RFC Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC
7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
editor.org/info/rfc7679>.
[RFC2679] [RFC2679]
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.
[RFC6049] [RFC6049]
<specific section reference and additional clarifications, if needed> <specific section reference and additional clarifications, if needed>
Section 3.4 of [RFC2679] provides the reference definition of the Section 3.4 of [RFC2679] 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
[RFC2679] provides the reference definition expanded to cover a [RFC2679] provides the reference definition expanded to cover a
skipping to change at page 36, line 21 skipping to change at page 37, line 26
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.
7.4.1. Type/Value (two diff terms used) 7.4.1. Type/Value (two diff terms used)
<insert name of the output type, raw or a selected summary statistic> <insert name of the output type, raw or a selected summary statistic>
See subsection titles below for Types. See subsection titles below for Types.
7.4.2. 7.4.2. Reference Definition
<describe the data format for each type of result> <describe the data format for each type of result>
For all output types --- For all output types ---
o T0, a time (start of measurement interval, 128-bit NTP Date o T0, a time (start of measurement interval, 128-bit NTP Date
Format, see section 6 of [RFC5905]) Format, see section 6 of [RFC5905])
o Tf, a time (end of measurement interval, 128-bit NTP Date Format, o Tf, a time (end of measurement interval, 128-bit NTP Date Format,
see section 6 of [RFC5905]) see section 6 of [RFC5905])
skipping to change at page 36, line 48 skipping to change at page 38, line 5
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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3 of [RFC3393] for details on the percentile statistic See section 4.3 of [RFC3393] for details on the percentile statistic
(where Round-trip delay should be substituted for "ipdv"). (where Round-trip delay should be substituted for "ipdv").
The percentile = 95. The percentile = 95.
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
7.4.2.2. Mean 7.4.2.2. Mean
The mean SHALL be calculated using the conditional distribution of The mean SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.2.2 of [RFC6049] for details on calculating this See section 4.2.2 of [RFC6049] for details on calculating this
statistic, and 4.2.3 of [RFC6049]. statistic, and 4.2.3 of [RFC6049].
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
7.4.2.3. Min 7.4.2.3. Min
The minimum SHALL be calculated using the conditional distribution of The minimum SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3.2 of [RFC6049] for details on calculating this See section 4.3.2 of [RFC6049] for details on calculating this
statistic, and 4.3.3 of [RFC6049]. statistic, and 4.3.3 of [RFC6049].
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
7.4.2.4. Max 7.4.2.4. Max
The maximum SHALL be calculated using the conditional distribution of The maximum SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3.2 of [RFC6049] for a closely related method for See section 4.3.2 of [RFC6049] for a closely related method for
calculating this statistic, and 4.3.3 of [RFC6049]. The formula is calculating this statistic, and 4.3.3 of [RFC6049]. The formula is
as follows: as follows:
Max = (FiniteDelay [j]) Max = (FiniteDelay [j])
such that for some index, j, where 1 <= j <= N such that for some index, j, where 1 <= j <= N
FiniteDelay[j] >= FiniteDelay[n] for all n FiniteDelay[j] >= FiniteDelay[n] for all n
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
7.4.2.5. Std_Dev 7.4.2.5. Std_Dev
7.4.3. 7.4.3. Metric Units
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 95th Percentile of One-way Delay is expressed in seconds. The 95th Percentile of One-way Delay is expressed in seconds.
7.4.4. Calibration
<pointer to >
7.5.1. Status 7.5.1. Status
<current or depricated> <current or depricated>
7.5.2. Requestor (keep?) 7.5.2. Requestor (keep?)
name or RFC, etc. name or RFC, etc.
skipping to change at page 39, line 41 skipping to change at page 40, line 49
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>
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-
8.1.3. URI and URL 8.1.3. URI and URL
URI: Prefix urn:ietf:metric...<name> URI: Prefix urn:ietf:metric...<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 This metric assesses the delay of a stream of packets exchanged
between two hosts (or measurement points), and reports the 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.
skipping to change at page 44, line 23 skipping to change at page 45, line 31
<describe the data format for each type of result> <describe the data format for each type of result>
For all output types --- For all output types ---
o T0, a time (start of measurement interval, 128-bit NTP Date o T0, a time (start of measurement interval, 128-bit NTP Date
Format, see section 6 of [RFC5905]) Format, see section 6 of [RFC5905])
o Tf, a time (end of measurement interval, 128-bit NTP Date Format, o Tf, a time (end of measurement interval, 128-bit NTP Date Format,
see section 6 of [RFC5905]) see section 6 of [RFC5905])
8.4.2.1. 8.4.2.1. 95Percentile
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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3 of [RFC3393] for details on the percentile statistic See section 4.3 of [RFC3393] for details on the percentile statistic
(where Round-trip delay should be substituted for "ipdv"). (where Round-trip delay should be substituted for "ipdv").
The percentile = 95. The percentile = 95.
Data format is a 32-bit signed value, *similar to* the 32-bit short Data format is a 32-bit signed value, *similar to* the 32-bit short
NTP Time format in Section 6 of [RFC5905] and is as follows: the NTP Time format in Section 6 of [RFC5905] and is as follows: the
first 16 bits represent the *signed* integer number of seconds; the first 16 bits represent the *signed* integer number of seconds; the
next 16 bits represent the fractional part of a second. next 16 bits represent the fractional part of a second.
The time value of the result is expressed in units of seconds, as a
positive value of type decimal64 with fraction digits = 9 (see
section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
8.4.2.2. Mean 8.4.2.2. Mean
The mean SHALL be calculated using the conditional distribution of The mean SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.2.2 of [RFC6049] for details on calculating this See section 4.2.2 of [RFC6049] for details on calculating this
statistic, and 4.2.3 of [RFC6049]. statistic, and 4.2.3 of [RFC6049].
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
8.4.2.3. Min 8.4.2.3. Min
The minimum SHALL be calculated using the conditional distribution of The minimum SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3.2 of [RFC6049] for details on calculating this See section 4.3.2 of [RFC6049] for details on calculating this
statistic, and 4.3.3 of [RFC6049]. statistic, and 4.3.3 of [RFC6049].
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
8.4.2.4. Max 8.4.2.4. Max
The maximum SHALL be calculated using the conditional distribution of The maximum SHALL be calculated using the conditional distribution of
all packets with a finite value of One-way delay (undefined delays all packets with a finite value of One-way delay (undefined delays
are excluded), a single value as follows: 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
[RFC6703] for background on this analysis choice. [RFC6703] for background on this analysis choice.
See section 4.3.2 of [RFC6049] for a closely related method for See section 4.3.2 of [RFC6049] for a closely related method for
calculating this statistic, and 4.3.3 of [RFC6049]. The formula is calculating this statistic, and 4.3.3 of [RFC6049]. The formula is
as follows: as follows:
Max = (FiniteDelay [j]) Max = (FiniteDelay [j])
such that for some index, j, where 1 <= j <= N such that for some index, j, where 1 <= j <= N
FiniteDelay[j] >= FiniteDelay[n] for all n FiniteDelay[j] >= FiniteDelay[n] for all n
the The time value of the result is expressed in units of seconds, as a
in of as positive value of type decimal64 with fraction digits = 9 (see
of section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0
the of ns), and with lossless conversion to/from the 64-bit NTP timestamp as
per section 6 of RFC [RFC5905].
8.4.2.5. Std_Dev 8.4.2.5. Std_Dev
8.4.3. 8.4.3. Metric Units
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.
8.4.4. Calibration
<pointer to >
8.5.1. Status 8.5.1. Status
<current or depricated> <current or depricated>
8.5.2. Requestor (keep?) 8.5.2. Requestor (keep?)
name or RFC, etc. name or RFC, etc.
skipping to change at page 46, line 44 skipping to change at page 48, line 13
1.0 1.0
8.5.4. Revision Date 8.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
Additional (Informational) details for this entry Additional (Informational) details for this entry
9. BLANK Registry Entry 9. ver08 BLANK Registry Entry
This section gives an initial registry entry for .... This section gives an initial registry entry for ....
9.1. Summary 9.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.
9.1.1. ID (Identifier) 9.1.1. ID (Identifier)
<insert numeric identifier, an integer> <insert numeric identifier, an integer>
9.1.2. Name 9.1.2. Name
<insert name according to metric naming convention> <insert name according to metric naming convention>
9.1.3. URIs
9.1.3.
URI: Prefix urn:ietf:params:performance:metric URI: Prefix urn:ietf:params:performance:metric
URL:
9.1.4. Description 9.1.4. Description
TBD. TBD.
9.1.5. Reference
<reference to the RFC of spec where the registry entry is defined>
9.1.6. Change Controller
<org or person >
9.1.7. Version (of Registry Format)
<currently 1.0>
9.2. Metric Definition 9.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.
9.2.1. Reference Definition 9.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.> <Full bibliographic reference to an immutable doc.>
<specific section reference and additional clarifications, if needed> <specific section reference and additional clarifications, if needed>
9.2.2. Fixed Parameters 9.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>
9.3. Method of Measurement 9.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.
9.3.1. Reference Method 9.3.1. Reference Method
<for metric, insert relevant section references and supplemental <for metric, insert relevant section references and supplemental
info> info>
9.3.2. Packet Stream 9.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>
9.3.3. Traffic Filtering (observation) Details 9.3.3. Traffic Filtering (observation) Details
measured results based on a filtered version of the packets <insert the measured results based on a filtered version of the
observed, and this section provides the filter details (when packets observed, and this section provides the filter details (when
present), and section reference>.
reference>.
9.3.4. Sampling Distribution 9.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the <insert time distribution details, or how this is diff from the
filter> filter>
9.3.5. Run-time Parameters and Data Format 9.3.5. Run-time Parameters and Data Format
<list of run-time parameters, and any reference(s)>.
<list of run-time
9.3.6. Roles 9.3.6. Roles
<lists the names of the different roles from the measurement method> <lists the names of the different roles from the measurement method>
9.4. Output 9.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.
9.4.1. Type 9.4.1. Type
<insert name of the output type, raw or a selected summary statistic> <insert name of the output type, raw or a selected summary statistic>
9.4.2. 9.4.2. Reference Definition
Reference
<pointer to section/spec where output type/format is defined> <pointer to section/spec where output type/format is defined>
9.4.. Metric Units 9.4.3. Metric Units
<insert units for the measured results, and the reference <insert units for the measured results, and the reference
specification>. specification>.
9.4.4. Calibration
<describe the error calibration, a way to indicate that the results
were collected in a calbration mode of operation, and a way to report
internal status metrics related to calibration, such as time offset>
9.5.1. Status 9.5.1. Status
<current or depricated> <current or depricated>
9.5.2. Requestor 9.5.2. Requestor
<name of individual or Internet Draft, etc.>
9.5.3. Revision 9.5.3. Revision
1.0 1.0
9.5.4. Revision Date 9.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
Additional (Informational) details for this entry Additional (Informational) details for this entry
10. 10. Example RTCP-XR Registry Entry
Example RTCP-XR Registry Entry
This section is MAY BE DELETED or adapted before submission. This section is MAY BE DELETED or adapted before submission.
This section gives an example registry entry for the end-point metric This section gives an example registry entry for the end-point metric
described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric
reporting. reporting.
1.1. Registry Indexes 10.1. Registry Indexes
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.
1.1.1. Identifier 10.1.1. Identifier
An integer having enough digits to uniquely identify each entry in An integer having enough digits to uniquely identify each entry in
the Registry. the Registry.
1.1.2. Name 10.1.2. Name
A metric naming convention is TBD. A metric naming convention is TBD.
1.1.3. URI 10.1.3. URI
Prefix urn:ietf:params:performance:metric Prefix urn:ietf:params:performance:metric
1.1.4. Status 10.1.4. Status
current current
1.1.5. Requestor 10.1.5. Requestor
Alcelip Mornuley Alcelip Mornuley
1.1.6. Revision 10.1.6. Revision
1.0 1.0
1.1.7. Revision Date 10.1.7. Revision Date
2014-07-04 2014-07-04
1.1.8. Description 10.1.8. Description
TBD. TBD.
1.1.9. Reference Specification(s) 10.1.9. Reference Specification(s)
[RFC3611][RFC4566][RFC6776][RFC6792][RFC7003] [RFC3611][RFC4566][RFC6776][RFC6792][RFC7003]
1.2. Metric Definition 10.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. Section 3.2 of and values of input factors, called fixed parameters. Section 3.2 of
[RFC7003] provides the reference information for this category. [RFC7003] provides the reference information for this category.
1.2.1. Reference Definition 10.2.1. Reference Definition
measured value is unsigned value. If the measured value exceeds measured value is unsigned value. If the measured value exceeds
0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over- 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over-
range measurement. If the measurement is unavailable, the value range measurement. If the measurement is unavailable, the value
0xFFFFFF MUST be reported. 0xFFFFFF MUST be reported.
1.2.2. Fixed Parameters 10.2.2. Fixed Parameters
Fixed Parameters are input factors that must be determined and Fixed Parameters are input factors that must be determined and
embedded in the measurement system for use when needed. The values embedded in the measurement system for use when needed. The values
of these parameters is specified in the Registry. of these parameters is specified in the Registry.
Threshold: 8 bits, set to value = 3 packets. Threshold: 8 bits, set to value = 3 packets.
The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of
successive packets that must not be discarded prior to and following successive packets that must not be discarded prior to and following
a discard packet in order for this discarded packet to be regarded as a discard packet in order for this discarded packet to be regarded as
skipping to change at page 55, line 43 skipping to change at page 53, line 14
I=10: Interval Duration - the reported value applies to the most I=10: Interval Duration - the reported value applies to the most
recent measurement interval duration between successive metrics recent measurement interval duration between successive metrics
reports. reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
Senders MUST NOT use the values I=00 or I=01. Senders MUST NOT use the values I=00 or I=01.
1.3. Method of Measurement 10.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. For the Burst/Gap Discard unambiguous methods for implementations. For the Burst/Gap Discard
Metric, it appears that the only guidance on methods of measurement Metric, it appears that the only guidance on methods of measurement
is in Section 3.0 of [RFC7003] and its supporting references. is in Section 3.0 of [RFC7003] and its supporting references.
Relevant information is repeated below, although there appears to be Relevant information is repeated below, although there appears to be
no section titled "Method of Measurement" in [RFC7003]. no section titled "Method of Measurement" in [RFC7003].
1.3.1. Reference Method 10.3.1. Reference Method
Metrics in this block report on burst/gap discard in the stream Metrics in this block report on burst/gap discard in the stream
arriving at the RTP system. Measurements of these metrics are made arriving at the RTP system. Measurements of these metrics are made
at the receiving end of the RTP stream. Instances of this metrics at the receiving end of the RTP stream. Instances of this metrics
block use the synchronization source (SSRC) to refer to the separate block use the synchronization source (SSRC) to refer to the separate
auxiliary Measurement Information Block [RFC6776], which describes auxiliary Measurement Information Block [RFC6776], which describes
measurement periods in use (see [RFC6776], Section 4.2). measurement periods in use (see [RFC6776], Section 4.2).
This metrics block relies on the measurement period in the This metrics block relies on the measurement period in the
Measurement Information Block indicating the span of the report. Measurement Information Block indicating the span of the report.
Senders MUST send this block in the same compound RTCP packet as the Senders MUST send this block in the same compound RTCP packet as the
Measurement Information Block. Receivers MUST verify that the Measurement Information Block. Receivers MUST verify that the
measurement period is received in the same compound RTCP packet as measurement period is received in the same compound RTCP packet as
this metrics block. If not, this metrics block MUST be discarded. this metrics block. If not, this metrics block MUST be discarded.
1.3.2. Stream Type and Stream Parameters 10.3.2. Stream Type and Stream Parameters
Since RTCP-XR Measurements are conducted on live RTP traffic, the Since RTCP-XR Measurements are conducted on live RTP traffic, the
complete description of the stream is contained in SDP messages that complete description of the stream is contained in SDP messages that
proceed the establishment of a compatible stream between two or more proceed the establishment of a compatible stream between two or more
communicating hosts. See Run-time Parameters, below. communicating hosts. See Run-time Parameters, below.
1.3.3. Output Type and Data Format 10.3.3. Output Type and Data Format
The output type defines the type of result that the metric produces. The output type defines the type of result that the metric produces.
o Value: Packets Discarded in Bursts o Value: Packets Discarded in Bursts
o Data Format: 24 bits o Data Format: 24 bits
o Reference: Section 3.2 of [RFC7003] o Reference: Section 3.2 of [RFC7003]
1.3.4. Metric Units 10.3.4. Metric Units
The measured results are apparently expressed in packets, although The measured results are apparently expressed in packets, although
there is no section of [RFC7003] titled "Metric Units". there is no section of [RFC7003] titled "Metric Units".
1.3.5. Run-time Parameters and Data Format 10.3.5. Run-time Parameters and Data Format
Run-Time Parameters are input factors that must be determined, Run-Time Parameters are input factors that must be determined,
configured into the measurement system, and reported with the results configured into the measurement system, and reported with the results
for the context to be complete. However, the values of these for the context to be complete. However, the values of these
parameters is not specified in the Registry, rather these parameters parameters is not specified in the Registry, rather these parameters
are listed as an aid to the measurement system implementor or user are listed as an aid to the measurement system implementor or user
(they must be left as variables, and supplied on execution). (they must be left as variables, and supplied on execution).
The Data Format of each Run-time Parameter SHALL be specified in this The Data Format of each Run-time Parameter SHALL be specified in this
column, to simplify the control and implementation of measurement column, to simplify the control and implementation of measurement
skipping to change at page 58, line 27 skipping to change at page 55, line 45
t=2873397496 2873404696 t=2873397496 2873404696
a=recvonly a=recvonly
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
m=video 51372 RTP/AVP 99 m=video 51372 RTP/AVP 99
a=rtpmap:99 h263-1998/90000 a=rtpmap:99 h263-1998/90000
TBD. TBD.
1. Revision History 11. Revision History
This section may be removed for publication. It contains partial This section may be removed for publication. It contains partial
information on updtes. information on updtes.
This draft replaced draft-mornuley-ippm-initial-registry. This draft replaced draft-mornuley-ippm-initial-registry.
In version 02, Section 4 has been edited to reflect recent discussion In version 02, Section 4 has been edited to reflect recent discussion
on the ippm-list: * Removed the combination or "Raw" and left 95th on the ippm-list: * Removed the combination or "Raw" and left 95th
percentile. * Hanging Indent on Run-time parameters (Fixed parameters percentile. * Hanging Indent on Run-time parameters (Fixed parameters
use bullet lists and other indenting formats. * Payload format for use bullet lists and other indenting formats. * Payload format for
skipping to change at page 59, line 10 skipping to change at page 56, line 31
Version 04 * All section 4 parameters reference YANG types for Version 04 * All section 4 parameters reference YANG types for
alternate data formats. * Discussion has concluded that usecase(s) alternate data formats. * Discussion has concluded that usecase(s)
for machine parse-able registry columns are not needed. for machine parse-able registry columns are not needed.
Still need: * suggestion of standard naming format for parameters. Still need: * suggestion of standard naming format for parameters.
Note: lambda parameter description is correct in section 4, elsewhere Note: lambda parameter description is correct in section 4, elsewhere
needs fix. needs fix.
1. Security Considerations 12. Security Considerations
These registry entries represent no known security implications for These registry entries represent no known security implications for
Internet Security. Each referenced Metric contains a Security Internet Security. Each referenced Metric contains a Security
Considerations section. Considerations section.
1. IANA Considerations 13. IANA Considerations
IANA is requested to populate The Performance Metric Registry defined IANA is requested to populate The Performance Metric Registry defined
in [I-D.ietf-ippm-metric-registry] with the values defined above. in [I-D.ietf-ippm-metric-registry] with the values defined above.
<more is needed here> <more is needed here>
1. Acknowledgements 14. Acknowledgements
The authors thank Brian Trammell for suggesting the term "Run-time The authors thank Brian Trammell for suggesting the term "Run-time
Parameters", which led to the distinction between run-time and fixed Parameters", which led to the distinction between run-time and fixed
parameters implemented in this memo, for identifying the IPFIX metric parameters implemented in this memo, for identifying the IPFIX metric
with Flow Key as an example, and for many other productive with Flow Key as an example, 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, and suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey, and
participants in the LMAP working group. participants in the LMAP working group.
1. References 15. References
1.1. Normative References 15.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
in progress) draft-ietf-ippm-metric-registry, 2014. in progress) draft-ietf-ippm-metric-registry, 2014.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>. November 1987, <http://www.rfc-editor.org/info/rfc1035>.
skipping to change at page 61, line 27 skipping to change at page 58, line 42
<http://www.rfc-editor.org/info/rfc6049>. <http://www.rfc-editor.org/info/rfc6049>.
[RFC6673] Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673, [RFC6673] Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673,
DOI 10.17487/RFC6673, August 2012, DOI 10.17487/RFC6673, August 2012,
<http://www.rfc-editor.org/info/rfc6673>. <http://www.rfc-editor.org/info/rfc6673>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
Informative References [RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Delay Metric for IP Performance Metrics
(IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January
2016, <http://www.rfc-editor.org/info/rfc7679>.
[RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Loss Metric for IP Performance Metrics
(IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January
2016, <http://www.rfc-editor.org/info/rfc7680>.
15.2. Informative References
[Brow00] Brownlee, N., "Packet Matching for NeTraMet [Brow00] Brownlee, N., "Packet Matching for NeTraMet
Distributions", March 2000. Distributions", March 2000.
[RFC1242] Bradner, S., "Benchmarking Terminology for Network [RFC1242] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242,
July 1991, <http://www.rfc-editor.org/info/rfc1242>. July 1991, <http://www.rfc-editor.org/info/rfc1242>.
[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed., [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
"RTP Control Protocol Extended Reports (RTCP XR)", "RTP Control Protocol Extended Reports (RTCP XR)",
End of changes. 132 change blocks.
555 lines changed or deleted 447 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/