draft-ietf-ippm-initial-registry-08.txt   draft-ietf-ippm-initial-registry-09.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: April 25, 2019 UC3M Expires: June 10, 2019 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
October 22, 2018 December 7, 2018
Initial Performance Metric Registry Entries Initial Performance Metric Registry Entries
draft-ietf-ippm-initial-registry-08 draft-ietf-ippm-initial-registry-09
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:
* resolved open items on UDP one-way measurements. * removed sections which only contained examples, or a blank outine
for new metric entries.
* resolved questions on DNS measurement method(s) * removed remaining comments (did not require action).
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14[RFC2119] [RFC8174] when, and only when, they appear in all 14[RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
skipping to change at page 1, line 48 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2019. This Internet-Draft will expire on June 10, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Registry Categories and Columns . . . . . . . . . . . . . . . 8 3. Registry Categories and Columns . . . . . . . . . . . . . . . 7
4. UDP Round-trip Latency and Loss Registry Entries . . . . . . 9 4. UDP Round-trip Latency and Loss Registry Entries . . . . . . 8
4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 10 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9
4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 10 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9
4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 10 4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 9
4.1.6. Version (of Registry Format) . . . . . . . . . . . . 10 4.1.6. Version (of Registry Format) . . . . . . . . . . . . 9
4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 11 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9
4.2.1. Reference Definition . . . . . . . . . . . . . . . . 11 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 10
4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 12 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10
4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 12 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11
4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 13 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11
4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 14 4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 12
4.3.3. Traffic Filtering (observation) Details . . . . . . . 14 4.3.3. Traffic Filtering (observation) Details . . . . . . . 13
4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 15 4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 13
4.3.5. Run-time Parameters and Data Format . . . . . . . . . 15 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 13
4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2. Reference Definition . . . . . . . . . . . . . . . . 16 4.4.2. Reference Definition . . . . . . . . . . . . . . . . 14
4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 17 4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 15
4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 17 4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 15
4.5. Administrative items . . . . . . . . . . . . . . . . . . 18 4.5. Administrative items . . . . . . . . . . . . . . . . . . 16
4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 18 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 18 4.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 16
4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 18 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16
4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 18 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16
4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 18 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16
5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 18 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16
5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 18 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16
5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 18 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 19 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 19 5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 17
5.1.6. Version (of Registry Format) . . . . . . . . . . . . 19 5.1.6. Version (of Registry Format) . . . . . . . . . . . . 17
5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 19 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17
5.2.1. Reference Definition . . . . . . . . . . . . . . . . 19 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 20 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 21 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 19
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 21 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19
5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 22 5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19
5.3.3. Traffic Filtering (observation) Details . . . . . . . 22 5.3.3. Traffic Filtering (observation) Details . . . . . . . 20
5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 23 5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 20
5.3.5. Run-time Parameters and Data Format . . . . . . . . . 23 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 20
5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 23 5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 24 5.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.2. Reference Definition . . . . . . . . . . . . . . . . 24 5.4.2. Reference Definition . . . . . . . . . . . . . . . . 21
5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 24 5.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 22
5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 25 5.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 22
5.5. Administrative items . . . . . . . . . . . . . . . . . . 25 5.5. Administrative items . . . . . . . . . . . . . . . . . . 23
5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 25 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 26 5.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 23
5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 26 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 23
5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 26 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 23
5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 26 5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 23
6. DNS Response Latency and Loss Registry Entries . . . . . . . 26 6. DNS Response Latency and Loss Registry Entries . . . . . . . 23
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 27 6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 24
6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 27 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 27 6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 24
6.1.5. Change Controller . . . . . . . . . . . . . . . . . . 27 6.1.5. Change Controller . . . . . . . . . . . . . . . . . . 24
6.1.6. Version (of Registry Format) . . . . . . . . . . . . 27 6.1.6. Version (of Registry Format) . . . . . . . . . . . . 24
6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 27 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 24
6.2.1. Reference Definition . . . . . . . . . . . . . . . . 28 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 25
6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 28 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 25
6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 30 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 27
6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 30 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 27
6.3.2. Packet Stream Generation . . . . . . . . . . . . . . 32 6.3.2. Packet Stream Generation . . . . . . . . . . . . . . 28
6.3.3. Traffic Filtering (observation) Details . . . . . . . 32 6.3.3. Traffic Filtering (observation) Details . . . . . . . 29
6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 32 6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 29
6.3.5. Run-time Parameters and Data Format . . . . . . . . . 33 6.3.5. Run-time Parameters and Data Format . . . . . . . . . 29
6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 34 6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4.2. Reference Definition . . . . . . . . . . . . . . . . 34 6.4.2. Reference Definition . . . . . . . . . . . . . . . . 31
6.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 35 6.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 31
6.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 35 6.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 31
6.5. Administrative items . . . . . . . . . . . . . . . . . . 35 6.5. Administrative items . . . . . . . . . . . . . . . . . . 32
6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 35 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 32
6.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 36 6.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 32
6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 36 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 32
6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 36 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 32
6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 36 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 32
7. UDP Poisson One-way Delay and Loss Registry Entries . . . . . 36 7. UDP Poisson One-way Delay and Loss Registry Entries . . . . . 32
7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 36 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 36 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 33
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 37 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 33
7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 37 7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 33
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 37 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 33
7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 38 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 34
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 38 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 34
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 39 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 35
7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 40 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 36
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 40 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 36
7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 41 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 36
7.3.3. Traffic Filtering (observation) Details . . . . . . . 41 7.3.3. Traffic Filtering (observation) Details . . . . . . . 37
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 42 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 37
7.3.5. Run-time Parameters and Data Format . . . . . . . . . 42 7.3.5. Run-time Parameters and Data Format . . . . . . . . . 37
7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 42 7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 38
7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 42 7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 43 7.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 38
7.4.2. Reference Definition . . . . . . . . . . . . . . . . 43 7.4.2. Reference Definition . . . . . . . . . . . . . . . . 38
7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 46 7.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 41
7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 46 7.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 41
7.5. Administrative items . . . . . . . . . . . . . . . . . . 47 7.5. Administrative items . . . . . . . . . . . . . . . . . . 42
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 47 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 42
7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 47 7.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 42
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 47 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 42
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 47 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 42
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 47 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 42
8. UDP Periodic One-way Delay and Loss Registry Entries . . . . 47 8. UDP Periodic One-way Delay and Loss Registry Entries . . . . 43
8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 47 8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 47 8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 43
8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 48 8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 48 8.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 44
8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 48 8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 44
8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 49 8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 44
8.2.1. Reference Definition . . . . . . . . . . . . . . . . 49 8.2.1. Reference Definition . . . . . . . . . . . . . . . . 44
8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 50 8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 45
8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 51 8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 46
8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 51 8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 46
8.3.2. Packet Stream Generation . . . . . . . . . . . . . . 52 8.3.2. Packet Stream Generation . . . . . . . . . . . . . . 47
8.3.3. Traffic Filtering (observation) Details . . . . . . . 52 8.3.3. Traffic Filtering (observation) Details . . . . . . . 48
8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 53 8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 48
8.3.5. Run-time Parameters and Data Format . . . . . . . . . 53 8.3.5. Run-time Parameters and Data Format . . . . . . . . . 48
8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 53 8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 48
8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 53 8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 54 8.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 49
8.4.2. Reference Definition . . . . . . . . . . . . . . . . 54 8.4.2. Reference Definition . . . . . . . . . . . . . . . . 49
8.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 57 8.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 51
8.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 57 8.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 52
8.5. Administrative items . . . . . . . . . . . . . . . . . . 58 8.5. Administrative items . . . . . . . . . . . . . . . . . . 53
8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 58 8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 53
8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 58 8.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 53
8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 58 8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 53
8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 58 8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 53
8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 58 8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 53
9. ICMP Round-trip Latency and Loss Registry Entries . . . . . . 58 9. ICMP Round-trip Latency and Loss Registry Entries . . . . . . 53
9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 59 9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 59 9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 53
9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 59 9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 59 9.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 59 9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 54
9.1.5. Change Controller . . . . . . . . . . . . . . . . . . 60 9.1.5. Change Controller . . . . . . . . . . . . . . . . . . 54
9.1.6. Version (of Registry Format) . . . . . . . . . . . . 60 9.1.6. Version (of Registry Format) . . . . . . . . . . . . 54
9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 60 9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 55
9.2.1. Reference Definition . . . . . . . . . . . . . . . . 60 9.2.1. Reference Definition . . . . . . . . . . . . . . . . 55
9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 61 9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 55
9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 62 9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 56
9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 62 9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 56
9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 63 9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 57
9.3.3. Traffic Filtering (observation) Details . . . . . . . 64 9.3.3. Traffic Filtering (observation) Details . . . . . . . 58
9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 64 9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 58
9.3.5. Run-time Parameters and Data Format . . . . . . . . . 64 9.3.5. Run-time Parameters and Data Format . . . . . . . . . 58
9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 65 9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 59
9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 65 9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 65 9.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 59
9.4.2. Reference Definition . . . . . . . . . . . . . . . . 65 9.4.2. Reference Definition . . . . . . . . . . . . . . . . 59
9.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 67 9.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 61
9.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 67 9.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 61
9.5. Administrative items . . . . . . . . . . . . . . . . . . 68 9.5. Administrative items . . . . . . . . . . . . . . . . . . 62
9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 68 9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 62
9.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 68 9.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 62
9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 68 9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 62
9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 68 9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 62
9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 68 9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 62
10. TCP Round-Trip Delay and Loss Registry Entries . . . . . . . 68 10. TCP Round-Trip Delay and Loss Registry Entries . . . . . . . 62
10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 68 10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 63
10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 69 10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 63
10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 69 10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 63
10.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 69 10.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 63
10.1.4. Description . . . . . . . . . . . . . . . . . . . . 69 10.1.4. Description . . . . . . . . . . . . . . . . . . . . 63
10.1.5. Change Controller . . . . . . . . . . . . . . . . . 70 10.1.5. Change Controller . . . . . . . . . . . . . . . . . 64
10.1.6. Version (of Registry Format) . . . . . . . . . . . . 70 10.1.6. Version (of Registry Format) . . . . . . . . . . . . 64
10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 70 10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 64
10.2.1. Reference Definitions . . . . . . . . . . . . . . . 70 10.2.1. Reference Definitions . . . . . . . . . . . . . . . 64
10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 72 10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 66
10.3. Method of Measurement . . . . . . . . . . . . . . . . . 73 10.3. Method of Measurement . . . . . . . . . . . . . . . . . 67
10.3.1. Reference Methods . . . . . . . . . . . . . . . . . 73 10.3.1. Reference Methods . . . . . . . . . . . . . . . . . 67
10.3.2. Packet Stream Generation . . . . . . . . . . . . . . 75 10.3.2. Packet Stream Generation . . . . . . . . . . . . . . 69
10.3.3. Traffic Filtering (observation) Details . . . . . . 75 10.3.3. Traffic Filtering (observation) Details . . . . . . 69
10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 75 10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 69
10.3.5. Run-time Parameters and Data Format . . . . . . . . 75 10.3.5. Run-time Parameters and Data Format . . . . . . . . 69
10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 76 10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 70
10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 76 10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 70
10.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 76 10.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 70
10.4.2. Reference Definition . . . . . . . . . . . . . . . . 77 10.4.2. Reference Definition . . . . . . . . . . . . . . . . 70
10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 79 10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 72
10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 79 10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 73
10.5. Administrative items . . . . . . . . . . . . . . . . . . 79 10.5. Administrative items . . . . . . . . . . . . . . . . . . 73
10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 79 10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 73
10.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . 79 10.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . 73
10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 79 10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 73
10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 79 10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 73
10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 79 10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 73
11. ver08 BLANK Registry Entry . . . . . . . . . . . . . . . . . 80 11. Security Considerations . . . . . . . . . . . . . . . . . . . 73
11.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 80 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 73
11.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 80 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 73
11.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 80 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 74
11.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 80 14.1. Normative References . . . . . . . . . . . . . . . . . . 74
11.1.4. Description . . . . . . . . . . . . . . . . . . . . 80 14.2. Informative References . . . . . . . . . . . . . . . . . 76
11.1.5. Reference . . . . . . . . . . . . . . . . . . . . . 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78
11.1.6. Change Controller . . . . . . . . . . . . . . . . . 80
11.1.7. Version (of Registry Format) . . . . . . . . . . . . 80
11.2. Metric Definition . . . . . . . . . . . . . . . . . . . 80
11.2.1. Reference Definition . . . . . . . . . . . . . . . . 81
11.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 81
11.3. Method of Measurement . . . . . . . . . . . . . . . . . 81
11.3.1. Reference Method . . . . . . . . . . . . . . . . . . 81
11.3.2. Packet Stream Generation . . . . . . . . . . . . . . 81
11.3.3. Traffic Filtering (observation) Details . . . . . . 81
11.3.4. Sampling Distribution . . . . . . . . . . . . . . . 81
11.3.5. Run-time Parameters and Data Format . . . . . . . . 81
11.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 81
11.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 82
11.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 82
11.4.2. Reference Definition . . . . . . . . . . . . . . . . 82
11.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 82
11.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 82
11.5. Administrative items . . . . . . . . . . . . . . . . . . 82
11.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 82
11.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . 82
11.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 82
11.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 82
11.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 82
12. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 83
12.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 83
12.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 83
12.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 83
12.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 83
12.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 83
12.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 83
12.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 83
12.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 83
12.1.8. Description . . . . . . . . . . . . . . . . . . . . 83
12.1.9. Reference Specification(s) . . . . . . . . . . . . . 84
12.2. Metric Definition . . . . . . . . . . . . . . . . . . . 84
12.2.1. Reference Definition . . . . . . . . . . . . . . . . 84
12.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 84
12.3. Method of Measurement . . . . . . . . . . . . . . . . . 85
12.3.1. Reference Method . . . . . . . . . . . . . . . . . . 85
12.3.2. Stream Type and Stream Parameters . . . . . . . . . 85
12.3.3. Output Type and Data Format . . . . . . . . . . . . 85
12.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 85
12.3.5. Run-time Parameters and Data Format . . . . . . . . 86
12.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 87
13. Revision History . . . . . . . . . . . . . . . . . . . . . . 87
14. Security Considerations . . . . . . . . . . . . . . . . . . . 88
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 88
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 89
17.1. Normative References . . . . . . . . . . . . . . . . . . 89
17.2. Informative References . . . . . . . . . . . . . . . . . 91
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 93
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]. literature, primarily [RFC2330].
skipping to change at page 10, line 12 skipping to change at page 9, line 12
two closely-related registry entries. As a result, IANA is also two closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric. 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>
IANA is asked to assign different numeric identifiers to each of the IANA is asked to assign different numeric identifiers to each of the
two Named Metrics. two Named Metrics.
4.1.2. Name 4.1.2. Name
<insert name according to metric naming convention>
RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile
RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio RTLoss_Active_IP-UDP-Periodic_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>
skipping to change at page 11, line 13 skipping to change at page 10, line 7
1.0 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.>
Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay
Metric for IPPM", RFC 2681, September 1999. Metric for IPPM", RFC 2681, September 1999.
[RFC2681] [RFC2681]
<specific section reference and additional clarifications, if needed>
Section 2.4 of [RFC2681] provides the reference definition of the Section 2.4 of [RFC2681] provides the reference definition of the
singleton (single value) Round-trip delay metric. Section 3.4 of singleton (single value) Round-trip delay metric. Section 3.4 of
[RFC2681] provides the reference definition expanded to cover a [RFC2681] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330]. are defined in Section 11 of [RFC2330].
Note that although the [RFC2681] definition of "Round-trip-Delay Note that although the [RFC2681] definition of "Round-trip-Delay
between Src and Dst" is directionally ambiguous in the text, this between Src and Dst" is directionally ambiguous in the text, this
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
skipping to change at page 12, line 7 skipping to change at page 10, line 41
[RFC6673] [RFC6673]
Both delay and loss metrics employ a maximum waiting time for Both delay and loss metrics employ a maximum waiting time for
received packets, so the count of lost packets to total packets sent 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 is the basis for the loss ratio calculation as per Section 6.1 of
[RFC6673]. [RFC6673].
4.2.2. Fixed Parameters 4.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when
needed>
Type-P as defined in Section 13 of [RFC2330]: Type-P as defined in Section 13 of [RFC2330]:
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL: set to 255 * TTL: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
skipping to change at page 13, line 7 skipping to change at page 11, line 38
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.
4.3.1. Reference Method 4.3.1. Reference Method
<for metric, insert relevant section references and supplemental
info>
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. However, the Periodic stream will be generated Fixed Parameters. However, the Periodic stream will be generated
according to [RFC3432]. according to [RFC3432].
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
skipping to change at page 14, line 7 skipping to change at page 12, line 32
the packet payload. the packet payload.
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 MUST be included in [RFC6673] presents additional requirements which MUST be included in
the method of measurement for this metric. the method of measurement for this metric.
4.3.2. Packet Stream Generation 4.3.2. Packet Stream Generation
<list of generation parameters and section/spec references if needed>
This section gives the details of the packet traffic which is the This section gives the details of the packet traffic which is the
basis for measurement. In IPPM metrics, this is called the Stream, basis for measurement. In IPPM metrics, this is called the Stream,
and can easily be described by providing the list of stream and can easily be described by providing the list of stream
parameters. parameters.
Section 3 of [RFC3432] prescribes the method for generating Periodic Section 3 of [RFC3432] prescribes the method for generating Periodic
streams using associated parameters. streams using associated parameters.
incT the nominal duration of inter-packet interval, first bit to incT the nominal duration of inter-packet interval, first bit to
first bit, with value 0.0200, expressed in units of seconds, as a first bit, with value 0.0200, expressed in units of seconds, as a
skipping to change at page 14, line 47 skipping to change at page 13, line 24
The T0 parameter will be reported as a measured parameter. The T0 parameter will be reported as a measured parameter.
Parameters incT and dT are Fixed Parameters. Parameters incT and dT are Fixed Parameters.
4.3.3. Traffic Filtering (observation) Details 4.3.3. Traffic Filtering (observation) Details
The measured results based on a filtered version of the packets The measured results based on a filtered version of the packets
observed, and this section provides the filter details (when observed, and this section provides the filter details (when
present). present).
<section reference>.
NA NA
4.3.4. Sampling Distribution 4.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
NA NA
4.3.5. Run-time Parameters and Data Format 4.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 15, line 37 skipping to change at page 14, line 4
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" 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 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of
[RFC2330]. When T0 is "all-zeros", a start time is unspecified [RFC2330]. When T0 is "all-zeros", a start time is unspecified
and Tf is to be interpreted as the Duration of the measurement and Tf is to be interpreted as the Duration of the measurement
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.
4.3.6. Roles 4.3.6. Roles
<lists the names of the different roles from the measurement method>
Src launches each packet and waits for return transmissions from Src launches each packet and waits for return transmissions from
Dst. Dst.
Dst waits for each packet from Src and sends a return packet to Src. Dst waits for each packet from Src and sends a return packet to Src.
4.4. Output 4.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.
4.4.1. Type 4.4.1. Type
<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, "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 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]. 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>
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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [RFC2330].
TotalPkts the count of packets sent by the Src to Dst during the TotalPkts the count of packets sent by the Src to Dst during the
measurement interval. measurement interval.
For For
RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile: RTDelay_Active_IP-UDP-Periodic_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 the 64-bit NTP timestamp as
For For
skipping to change at page 17, line 23 skipping to change at page 15, line 32
RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio: RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio:
Percentile The numeric value of the result is expressed in units of Percentile The numeric value of the result is expressed in units of
lost packets to total packets times 100%, as a positive value of lost packets to total packets times 100%, as a positive value of
type decimal64 with fraction digits = 9 (see section 9.3 of type decimal64 with fraction digits = 9 (see section 9.3 of
[RFC6020]) with resolution of 0.0000000001. [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
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 The Round-trip Loss Ratio is expressed as a percentage of lost
packets to total packets sent. 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
skipping to change at page 18, line 9 skipping to change at page 16, line 15
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
4.5. Administrative items 4.5. Administrative items
4.5.1. Status 4.5.1. Status
<current or deprecated> Current
4.5.2. Requestor (keep?) 4.5.2. Requestor
name or RFC, etc. This RFC numner
4.5.3. Revision 4.5.3. Revision
1.0 1.0
4.5.4. Revision Date 4.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
4.6. Comments and Remarks 4.6. Comments and Remarks
Additional (Informational) details for this entry None.
5. Packet Delay Variation Registry Entry 5. Packet Delay Variation Registry Entry
This section gives an initial registry entry for a Packet Delay This section gives an initial registry entry for a Packet Delay
Variation metric. Variation metric.
Note: If each Registry entry should only produce a "raw" output or a Note: If each Registry entry should only produce a "raw" output or a
statistical summary, then the "Output" Category can be split and this statistical summary, then the "Output" Category can be split and this
section can become two closely-related metrics. section can become two closely-related metrics.
5.1. Summary 5.1. Summary
This category includes multiple indexes to the registry entries, the This category includes multiple indexes to the registry entries, the
element ID and metric name. element ID and metric name.
<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>
OWPDV_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile OWPDV_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile
5.1.3. URIs 5.1.3. URIs
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>
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 periodic stream, and the Output is expressed as delay observed on the periodic stream, and the Output is expressed as
the 95th percentile of the packet delay variation distribution. the 95th percentile of the packet delay variation distribution.
5.1.5. Change Controller 5.1.5. Change Controller
<org or person >
IETF IETF
5.1.6. Version (of Registry Format) 5.1.6. Version (of Registry Format)
1.0 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.>
Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP
Performance Metrics", RFC 2330, May 1998. [RFC2330] Performance Metrics", RFC 2330, May 1998. [RFC2330]
Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric
for IP Performance Metrics (IPPM)", RFC 3393, November 2002. for IP Performance Metrics (IPPM)", RFC 3393, November 2002.
[RFC3393] [RFC3393]
Morton, A. and B. Claise, "Packet Delay Variation Applicability Morton, A. and B. Claise, "Packet Delay Variation Applicability
Statement", RFC 5481, March 2009. [RFC5481] Statement", RFC 5481, March 2009. [RFC5481]
Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time
Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, Protocol Version 4: Protocol and Algorithms Specification", RFC 5905,
June 2010.[RFC5905] June 2010.[RFC5905]
<specific section reference and additional clarifications, if needed>
See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences
measured are referred to by the variable name "ddT" (applicable to measured are referred to by the variable name "ddT" (applicable to
all forms of delay variation). However, this metric entry specifies all forms of delay variation). However, this metric entry specifies
the PDV form defined in section 4.2 of [RFC5481], where the singleton the PDV form defined in section 4.2 of [RFC5481], where the singleton
PDV for packet i is referred to by the variable name "PDV(i)". PDV for packet i is referred to by the variable name "PDV(i)".
5.2.2. Fixed Parameters 5.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when
needed>
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL: set to 255 * TTL: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
o IPv6 header values: o IPv6 header values:
skipping to change at page 21, line 16 skipping to change at page 19, line 13
Parameters. Parameters.
5.3. Method of Measurement 5.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.
5.3.1. Reference Method 5.3.1. Reference Method
<for metric, insert relevant section references and supplemental
info>
See section 2.6 and 3.6 of [RFC3393] for general singleton element See section 2.6 and 3.6 of [RFC3393] for general singleton element
calculations. This metric entry requires implementation of the PDV calculations. This metric entry requires implementation of the PDV
form defined in section 4.2 of [RFC5481]. Also see measurement form defined in section 4.2 of [RFC5481]. Also see measurement
considerations in section 8 of [RFC5481]. considerations in section 8 of [RFC5481].
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.
skipping to change at page 22, line 7 skipping to change at page 19, line 49
If a standard measurement protocol is employed, then the measurement If a standard measurement protocol is employed, then the measurement
process will determine the sequence numbers or timestamps applied to process will determine the sequence numbers or timestamps applied to
test packets after the Fixed and Runtime parameters are passed to test packets after the Fixed and Runtime parameters are passed to
that process. The chosen measurement protocol will dictate the that process. The chosen measurement protocol will dictate the
format of sequence numbers and time-stamps, if they are conveyed in format of sequence numbers and time-stamps, if they are conveyed in
the packet payload. the packet payload.
5.3.2. Packet Stream Generation 5.3.2. Packet Stream Generation
<list of generation parameters and section/spec references if needed>
This section gives the details of the packet traffic which is the This section gives the details of the packet traffic which is the
basis for measurement. In IPPM metrics, this is called the Stream, basis for measurement. In IPPM metrics, this is called the Stream,
and can easily be described by providing the list of stream and can easily be described by providing the list of stream
parameters. parameters.
Section 3 of [RFC3432] prescribes the method for generating Periodic Section 3 of [RFC3432] prescribes the method for generating Periodic
streams using associated parameters. streams using associated parameters.
incT the nominal duration of inter-packet interval, first bit to incT the nominal duration of inter-packet interval, first bit to
first bit, with value 0.0200, expressed in units of seconds, as a first bit, with value 0.0200, expressed in units of seconds, as a
skipping to change at page 22, line 43 skipping to change at page 20, line 34
resulting in unpredictable start times (within a time interval) may resulting in unpredictable start times (within a time interval) may
be sufficient to avoid synchronization of periodic streams, and be sufficient to avoid synchronization of periodic streams, and
therefore a valid replacement for selecting a start time at random therefore a valid replacement for selecting a start time at random
from a fixed interval. from a fixed interval.
The T0 parameter will be reported as a measured parameter. The T0 parameter will be reported as a measured parameter.
Parameters incT and dT are Fixed Parameters. Parameters incT and dT are Fixed Parameters.
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
packets observed, and this section provides the filter details (when
present), and section reference>.
NA NA
5.3.4. Sampling Distribution 5.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
NA NA
5.3.5. Run-time Parameters and Data Format 5.3.5. Run-time Parameters and Data Format
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 23, line 39 skipping to change at page 21, line 17
interval. The start time is controlled through other means. interval. The start time is controlled through other means.
Tf a time, the end of a measurement interval, (format "date-and-time" Tf a time, the end of a measurement interval, (format "date-and-time"
as specified in Section 5.6 of [RFC3339], see also Section 3 of as specified in Section 5.6 of [RFC3339], see also Section 3 of
[RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of
[RFC2330]. When T0 is "all-zeros", a end time date is ignored and [RFC2330]. When T0 is "all-zeros", a end time date is ignored and
Tf is interpreted as the Duration of the measurement interval. Tf is interpreted as the Duration of the measurement interval.
5.3.6. Roles 5.3.6. Roles
<lists the names of the different roles from the measurement method>
Src launches each packet to Dst.
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>
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, "95Percentile", 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(95Percentile) >= 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. Reference Definition 5.4.2. Reference Definition
<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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [RFC2330].
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 per section 6 of RFC [RFC5905] the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]
5.4.3. Metric Units 5.4.3. Metric Units
<insert units for the measured results, and the reference
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 5.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.
skipping to change at page 25, line 48 skipping to change at page 23, line 9
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
5.5. Administrative items 5.5. Administrative items
5.5.1. Status 5.5.1. Status
<current or deprecated> Current
5.5.2. Requestor (keep?) 5.5.2. Requestor
<name of individual or RFC, etc.> This RFC number
5.5.3. Revision 5.5.3. Revision
1.0 1.0
5.5.4. Revision Date 5.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
5.6. Comments and Remarks 5.6. Comments and Remarks
<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 and Loss Registry Entries 6. DNS Response Latency and Loss Registry Entries
@@@@ comment from Brian: there is an interesting method for DNS
measurement by encoding information in the query itself. It is a
question of what exactly we are trying to measure: specific RR, or
the infrastructure itself. (at this time we measure a specific RR).
This section gives initial registry entries for DNS Response Latency This section gives initial registry entries for DNS Response Latency
and Loss from a network user's perspective, for a specific named and Loss from a network user's perspective, for a specific named
resource. The metric can be measured repeatedly using different resource. The metric can be measured repeatedly using different
names. RFC 2681 [RFC2681] defines a Round-trip delay metric. We names. 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 two metrics for measuring DNS latency and loss. precisely define two metrics for measuring DNS latency and loss.
Note to IANA: Each Registry "Name" below specifies a single registry Note to IANA: Each Registry "Name" below specifies a single registry
entry, whose output format varies in accordance with the name. entry, whose output format varies in accordance with the name.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
two closely-related registry entries. As a result, IANA is also two closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric. 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>
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 IANA is asked to assign different numeric identifiers to each of the
two Named Metrics. two Named Metrics.
6.1.2. Name 6.1.2. Name
<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 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>
skipping to change at page 28, line 7 skipping to change at page 25, line 7
1.0 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.>
Mockapetris, P., "Domain names - implementation and specification", Mockapetris, P., "Domain names - implementation and specification",
STD 13, RFC 1035, November 1987. (and updates) STD 13, RFC 1035, November 1987. (and updates)
[RFC1035] [RFC1035]
Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay
Metric for IPPM", RFC 2681, September 1999. Metric for IPPM", RFC 2681, September 1999.
[RFC2681] [RFC2681]
<specific section reference and additional clarifications, if needed>
Section 2.4 of [RFC2681] provides the reference definition of the Section 2.4 of [RFC2681] provides the reference definition of the
singleton (single value) Round-trip delay metric. Section 3.4 of singleton (single value) Round-trip delay metric. Section 3.4 of
[RFC2681] provides the reference definition expanded to cover a [RFC2681] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330]. are defined in Section 11 of [RFC2330].
For DNS Response Latency, the entities in [RFC1035] must be mapped to For DNS Response Latency, the entities in [RFC1035] must be mapped to
[RFC2681]. The Local Host with its User Program and Resolver take [RFC2681]. The Local Host with its User Program and Resolver take
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".
skipping to change at page 28, line 50 skipping to change at page 25, line 46
[RFC6673] [RFC6673]
Both response time and loss metrics employ a maximum waiting time for Both response time and loss metrics employ a maximum waiting time for
received responses, so the count of lost packets to total packets 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 sent is the basis for the loss determination as per Section 4.3 of
[RFC6673]. [RFC6673].
6.2.2. Fixed Parameters 6.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when
needed>
Type-P as defined in Section 13 of [RFC2330]: Type-P as defined in Section 13 of [RFC2330]:
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL set to 255 * TTL set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
o IPv6 header values: o IPv6 header values:
* DSCP: set to 0 * DSCP: set to 0
* Hop Count: set to 255 * Hop Count: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
skipping to change at page 30, line 46 skipping to change at page 27, line 39
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
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.
6.3.1. Reference Method 6.3.1. Reference Method
<for metric, insert relevant section references and supplemental
info>
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
response packet lost. Lost packets SHALL be designated as having response packet lost. Lost packets SHALL be designated as having
undefined delay and counted for the RLDNS metric. undefined delay and counted for the RLDNS metric.
skipping to change at page 32, line 14 skipping to change at page 28, line 50
subsequent reporting as a measured result, along with the Round-Trip subsequent reporting as a measured result, along with the Round-Trip
Delay. Delay.
6.3.2. Packet Stream Generation 6.3.2. Packet Stream Generation
This section gives the details of the packet traffic which is the This section gives the details of the packet traffic which is the
basis for measurement. In IPPM metrics, this is called the Stream, basis for measurement. In IPPM metrics, this is called the Stream,
and can easily be described by providing the list of stream and can easily be described by providing the list of stream
parameters. parameters.
<list of generation parameters and section/spec references if needed>
Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to
generate Poisson sampling intervals. The reciprocal of lambda is the generate Poisson sampling intervals. The reciprocal of lambda is the
average packet rate, thus the Run-time Parameter is Reciprocal_lambda average packet rate, thus the Run-time Parameter is Reciprocal_lambda
= 1/lambda, in seconds. = 1/lambda, in seconds.
Method 3 is used, where given a start time (Run-time Parameter), the Method 3 is used, where given a start time (Run-time Parameter), the
subsequent send times are all computed prior to measurement by subsequent send times are all computed prior to measurement by
computing the pseudo-random distribution of inter-packet send times, computing the pseudo-random distribution of inter-packet send times,
(truncating the distribution as specified in the Run-time (truncating the distribution as specified in the Run-time
Parameters), and the Src sends each packet at the computed times. Parameters), and the Src sends each packet at the computed times.
skipping to change at page 32, line 37 skipping to change at page 29, line 23
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
to Trunc instead. to Trunc instead.
6.3.3. Traffic Filtering (observation) Details 6.3.3. Traffic Filtering (observation) Details
The measured results based on a filtered version of the packets The measured results based on a filtered version of the packets
observed, and this section provides the filter details (when observed, and this section provides the filter details (when
present). present).
<section reference>.
NA NA
6.3.4. Sampling Distribution 6.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
NA NA
6.3.5. Run-time Parameters and Data Format 6.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 34, line 16 skipping to change at page 30, line 39
QNAME The domain name of the Query, formatted as specified in QNAME The domain name of the Query, formatted as specified in
section 4 of [RFC6991]. section 4 of [RFC6991].
QTYPE The Query Type, which will correspond to the IP address family QTYPE The Query Type, which will correspond to the IP address family
of the query (decimal 1 for IPv4 or 28 for IPv6, formatted as a of the query (decimal 1 for IPv4 or 28 for IPv6, formatted as a
uint16, as per section 9.2 of [RFC6020]. uint16, as per section 9.2 of [RFC6020].
6.3.6. Roles 6.3.6. Roles
<lists the names of the different roles from the measurement method>
Src launches each packet and waits for return transmissions from Src launches each packet and waits for return transmissions from
Dst. Dst.
Dst waits for each packet from Src and sends a return packet to Src. Dst waits for each packet from Src and sends a return packet to Src.
6.4. Output 6.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.
6.4.1. Type 6.4.1. Type
<insert name of the output type, raw or a selected summary statistic>
Raw -- for each DNS Query packet sent, sets of values as defined in Raw -- for each DNS Query packet sent, sets of values as defined in
the next column, including the status of the response, only assigning the next column, including the status of the response, only assigning
delay values to successful query-response pairs. delay values to successful query-response pairs.
6.4.2. Reference Definition 6.4.2. Reference Definition
<describe the data format for each type of result>
For all outputs: For all outputs:
T the time the DNS Query was sent during the measurement interval, T the time the DNS Query was sent during the measurement interval,
(format "date-and-time" as specified in Section 5.6 of [RFC3339], (format "date-and-time" as specified in Section 5.6 of [RFC3339],
see also Section 3 of [RFC6991]). The UTC Time Zone is required see also Section 3 of [RFC6991]). The UTC Time Zone is required
by Section 6.1 of [RFC2330]. by Section 6.1 of [RFC2330].
dT The time value of the round-trip delay to receive the DNS dT The time value of the round-trip delay to receive the DNS
response, expressed in units of seconds, as a positive value of response, expressed in units of seconds, as a positive value of
type decimal64 with fraction digits = 9 (see section 9.3 of type decimal64 with fraction digits = 9 (see section 9.3 of
skipping to change at page 35, line 15 skipping to change at page 31, line 36
response packet is not received at Src within waiting time Tmax response packet is not received at Src within waiting time Tmax
seconds. seconds.
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
specification>.
RTDNS: 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. 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,
skipping to change at page 35, line 48 skipping to change at page 32, line 17
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
6.5. Administrative items 6.5. Administrative items
6.5.1. Status 6.5.1. Status
<current or deprecated> Current
6.5.2. Requestor 6.5.2. Requestor
name or RFC, etc. This RFC number
6.5.3. Revision 6.5.3. Revision
1.0 1.0
6.5.4. Revision Date 6.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
6.6. Comments and Remarks 6.6. Comments and Remarks
skipping to change at page 36, line 43 skipping to change at page 33, line 12
six closely-related registry entries. As a result, IANA is also six closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric. 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
name below>
IANA is asked to assign different numeric identifiers to each of the IANA is asked to assign different numeric identifiers to each of the
six Metrics. six Metrics.
7.1.2. Name 7.1.2. Name
<insert name according to metric naming convention>
OWDelay_Active_IP-UDP-Poisson- OWDelay_Active_IP-UDP-Poisson-
Payload250B_RFCXXXXsecY_Seconds_<statistic> Payload250B_RFCXXXXsecY_Seconds_<statistic>
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
skipping to change at page 38, line 17 skipping to change at page 34, line 23
received packets expressed as a percentage. 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.>
For Delay: 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.
[RFC6049] [RFC6049]
<specific section reference and additional clarifications, if needed>
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: For loss:
skipping to change at page 39, line 13 skipping to change at page 35, line 13
rfc7680>. rfc7680>.
Section 2.4 of [RFC7680] provides the reference definition of the Section 2.4 of [RFC7680] provides the reference definition of the
singleton (single value) one-way loss metric. Section 3.4 of singleton (single value) one-way loss metric. Section 3.4 of
[RFC7680] provides the reference definition expanded to cover a [RFC7680] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330]. 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
determined and embedded in the measurement system for use when
needed>
Type-P: Type-P:
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL: set to 255 * TTL: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
skipping to change at page 40, line 18 skipping to change at page 36, line 13
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
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
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, and counted for the OWLoss metric. delay, and counted for the OWLoss metric.
skipping to change at page 41, line 14 skipping to change at page 37, line 5
of sequence numbers and time-stamps conveyed in the TWAMP-Test packet of sequence numbers and time-stamps conveyed in the TWAMP-Test packet
payload. payload.
7.3.2. Packet Stream Generation 7.3.2. Packet Stream Generation
This section gives the details of the packet traffic which is the This section gives the details of the packet traffic which is the
basis for measurement. In IPPM metrics, this is called the Stream, basis for measurement. In IPPM metrics, this is called the Stream,
and can easily be described by providing the list of stream and can easily be described by providing the list of stream
parameters. parameters.
<list of generation parameters and section/spec references if needed>
Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to
generate Poisson sampling intervals. The reciprocal of lambda is the generate Poisson sampling intervals. The reciprocal of lambda is the
average packet spacing, thus the Run-time Parameter is average packet spacing, thus the Run-time Parameter is
Reciprocal_lambda = 1/lambda, in seconds. Reciprocal_lambda = 1/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
skipping to change at page 42, line 15 skipping to change at page 37, line 50
7.3.4. Sampling Distribution 7.3.4. Sampling Distribution
NA NA
7.3.5. Run-time Parameters and Data Format 7.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 43, line 7 skipping to change at page 38, line 39
Dst waits for each packet from Src and sends a return packet to Src. Dst waits for each packet from Src and sends a return packet to Src.
This is the TWAMP Session-Reflector. This is the TWAMP Session-Reflector.
7.4. Output 7.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.
7.4.1. Type 7.4.1. Type
<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. Reference Definition 7.4.2. Reference Definition
<describe the data format for each type of result>
For all output types --- For all output types ---
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [RFC2330].
For LossRatio -- the count of lost packets to total packets sent is 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 the basis for the loss ratio calculation as per Section 4.1 of
[RFC7680]. [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
skipping to change at page 46, line 7 skipping to change at page 41, line 29
the classic calculation for standard deviation of a population. the classic calculation for standard deviation of a population.
Std_Dev The time value of the result is expressed in units of Std_Dev 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]
7.4.3. Metric Units 7.4.3. Metric Units
<insert units for the measured results, and the reference
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 The One-way Loss Ratio is expressed as a percentage of lost packets
to total packets sent. 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
skipping to change at page 47, line 9 skipping to change at page 42, line 30
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
7.5. Administrative items 7.5. Administrative items
7.5.1. Status 7.5.1. Status
<current or deprecated> Current
7.5.2. Requestor (keep?) 7.5.2. Requestor
name or RFC, etc. This REFC number
7.5.3. Revision 7.5.3. Revision
1.0 1.0
7.5.4. Revision Date 7.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
7.6. Comments and Remarks 7.6. Comments and Remarks
skipping to change at page 47, line 49 skipping to change at page 43, line 27
six closely-related registry entries. As a result, IANA is also six closely-related registry entries. As a result, IANA is also
asked to assign corresponding URNs and URLs to each Named Metric. 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
name below>
IANA is asked to assign a different numeric identifiers to each of IANA is asked to assign a different numeric identifiers to each of
the six Metrics. the six Metrics.
8.1.2. Name 8.1.2. Name
<insert name according to metric naming convention>
OWDelay_Active_IP-UDP-Periodic20m- OWDelay_Active_IP-UDP-Periodic20m-
Payload142B_RFCXXXXsecY_Seconds_<statistic> Payload142B_RFCXXXXsecY_Seconds_<statistic>
where <statistic> is one of: where <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
skipping to change at page 49, line 19 skipping to change at page 44, line 43
received packets expressed as a percentage. 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.>
For Delay: 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.
[RFC6049] [RFC6049]
<specific section reference and additional clarifications, if needed>
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: For loss:
skipping to change at page 50, line 13 skipping to change at page 45, line 33
rfc7680>. rfc7680>.
Section 2.4 of [RFC7680] provides the reference definition of the Section 2.4 of [RFC7680] provides the reference definition of the
singleton (single value) one-way loss metric. Section 3.4 of singleton (single value) one-way loss metric. Section 3.4 of
[RFC7680] provides the reference definition expanded to cover a [RFC7680] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330]. 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
determined and embedded in the measurement system for use when
needed>
Type-P: Type-P:
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL: set to 255 * TTL: set to 255
* Protocol: Set to 17 (UDP) * Protocol: Set to 17 (UDP)
skipping to change at page 51, line 18 skipping to change at page 46, line 34
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
unambiguous methods for implementations. unambiguous methods for implementations.
8.3.1. Reference Method 8.3.1. Reference Method
<for metric, insert relevant section references and supplemental
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.
However, a Periodic stream is used, as defined in [RFC3432]. However, a Periodic stream is used, as defined in [RFC3432].
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, and counted for the OWLoss metric. delay, and counted for the OWLoss metric.
skipping to change at page 52, line 9 skipping to change at page 47, line 21
Since a standard measurement protocol is employed [RFC5357], then the Since a standard measurement protocol is employed [RFC5357], then the
measurement process will determine the sequence numbers or timestamps measurement process will determine the sequence numbers or timestamps
applied to test packets after the Fixed and Runtime parameters are applied to test packets after the Fixed and Runtime parameters are
passed to that process. The measurement protocol dictates the format passed to that process. The measurement protocol dictates the format
of sequence numbers and time-stamps conveyed in the TWAMP-Test packet of sequence numbers and time-stamps conveyed in the TWAMP-Test packet
payload. payload.
8.3.2. Packet Stream Generation 8.3.2. Packet Stream Generation
<list of generation parameters and section/spec references if needed>
This section gives the details of the packet traffic which is the This section gives the details of the packet traffic which is the
basis for measurement. In IPPM metrics, this is called the Stream, basis for measurement. In IPPM metrics, this is called the Stream,
and can easily be described by providing the list of stream and can easily be described by providing the list of stream
parameters. parameters.
Section 3 of [RFC3432] prescribes the method for generating Periodic Section 3 of [RFC3432] prescribes the method for generating Periodic
streams using associated parameters. streams using associated parameters.
incT the nominal duration of inter-packet interval, first bit to incT the nominal duration of inter-packet interval, first bit to
first bit, with value 0.0200 expressed in units of seconds, as a first bit, with value 0.0200 expressed in units of seconds, as a
skipping to change at page 53, line 15 skipping to change at page 48, line 19
8.3.4. Sampling Distribution 8.3.4. Sampling Distribution
NA NA
8.3.5. Run-time Parameters and Data Format 8.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 53, line 40 skipping to change at page 48, line 42
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.
8.3.6. Roles 8.3.6. Roles
<lists the names of the different roles from the measurement method>
Src launches each packet and waits for return transmissions from Src launches each packet and waits for return transmissions from
Dst. This is the TWAMP Session-Sender. Dst. This is the TWAMP Session-Sender.
Dst waits for each packet from Src and sends a return packet to Src. Dst waits for each packet from Src and sends a return packet to Src.
This is the TWAMP Session-Reflector. This is the TWAMP Session-Reflector.
8.4. Output 8.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.
8.4.1. Type 8.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>
See subsection titles in Reference Definition for Latency Types. See subsection titles in Reference Definition for Latency Types.
8.4.2. Reference Definition 8.4.2. Reference Definition
<describe the data format for each type of result>
For all output types --- For all output types ---
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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
skipping to change at page 57, line 7 skipping to change at page 51, line 46
the classic calculation for standard deviation of a population. the classic calculation for standard deviation of a population.
Std_Dev The time value of the result is expressed in units of Std_Dev 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]
8.4.3. Metric Units 8.4.3. Metric Units
<insert units for the measured results, and the reference
specification>.
The <statistic> of One-way Delay is expressed in seconds, where The <statistic> of One-way Delay is expressed in seconds, where
<statistic> is one of: <statistic> is one of:
o 95Percentile o 95Percentile
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
The One-way Loss Ratio is expressed as a percentage of lost packets The One-way Loss Ratio is expressed as a percentage of lost packets
to total packets sent. to total packets sent.
8.4.4. Calibration 8.4.4. Calibration
skipping to change at page 58, line 22 skipping to change at page 53, line 9
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
8.5. Administrative items 8.5. Administrative items
8.5.1. Status 8.5.1. Status
<current or deprecated> Current
8.5.2. Requestor (keep?) 8.5.2. Requestor
name or RFC, etc. This RFC number
8.5.3. Revision 8.5.3. Revision
1.0 1.0
8.5.4. Revision Date 8.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
8.6. Comments and Remarks 8.6. Comments and Remarks
Additional (Informational) details for this entry
9. ICMP Round-trip Latency and Loss Registry Entries 9. ICMP Round-trip Latency and Loss Registry Entries
This section specifies three initial registry entries for the ICMP This section specifies three initial registry entries for the ICMP
Round-trip Latency, and another entry for ICMP Round-trip Loss Ratio. Round-trip Latency, and another entry for ICMP Round-trip Loss Ratio.
This section specifies four Registry entries with many common This section specifies four Registry entries with many common
columns. columns.
All column entries beside the ID, Name, Description, and Output All column entries beside the ID, Name, Description, and Output
Reference Method categories are the same, thus this section proposes Reference Method categories are the same, thus this section proposes
skipping to change at page 59, line 12 skipping to change at page 53, line 46
asked to assign four corresponding URNs and URLs to each Named asked to assign four corresponding URNs and URLs to each Named
Metric. Metric.
9.1. Summary 9.1. Summary
This category includes multiple indexes to the registry entry: the This category includes multiple indexes to the registry entry: the
element ID and metric name. element ID and metric name.
9.1.1. ID (Identifier) 9.1.1. ID (Identifier)
<insert a numeric identifier, an integer, TBD>
IANA is asked to assign different numeric identifiers to each of the IANA is asked to assign different numeric identifiers to each of the
four Named Metrics. four Named Metrics.
9.1.2. Name 9.1.2. Name
<insert name according to metric naming convention>
RTDelay_Active_IP-ICMP-SendOnRcv_RFCXXXXsecY_Seconds_<statistic> RTDelay_Active_IP-ICMP-SendOnRcv_RFCXXXXsecY_Seconds_<statistic>
where <statistic> is one of: where <statistic> is one of:
o Mean o Mean
o Min o Min
o Max o Max
skipping to change at page 60, line 25 skipping to change at page 55, line 13
1.0 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.>
Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay
Metric for IPPM", RFC 2681, September 1999. Metric for IPPM", RFC 2681, September 1999.
[RFC2681] [RFC2681]
<specific section reference and additional clarifications, if needed>
Section 2.4 of [RFC2681] provides the reference definition of the Section 2.4 of [RFC2681] provides the reference definition of the
singleton (single value) Round-trip delay metric. Section 3.4 of singleton (single value) Round-trip delay metric. Section 3.4 of
[RFC2681] provides the reference definition expanded to cover a [RFC2681] provides the reference definition expanded to cover a
multi-singleton sample. Note that terms such as singleton and sample multi-singleton sample. Note that terms such as singleton and sample
are defined in Section 11 of [RFC2330]. are defined in Section 11 of [RFC2330].
Note that although the [RFC2681] definition of "Round-trip-Delay Note that although the [RFC2681] definition of "Round-trip-Delay
between Src and Dst" is directionally ambiguous in the text, this between Src and Dst" is directionally ambiguous in the text, this
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
skipping to change at page 61, line 16 skipping to change at page 55, line 47
[RFC6673] [RFC6673]
Both delay and loss metrics employ a maximum waiting time for Both delay and loss metrics employ a maximum waiting time for
received packets, so the count of lost packets to total packets sent 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 is the basis for the loss ratio calculation as per Section 6.1 of
[RFC6673]. [RFC6673].
9.2.2. Fixed Parameters 9.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when
needed>
Type-P as defined in Section 13 of [RFC2330]: Type-P as defined in Section 13 of [RFC2330]:
o IPv4 header values: o IPv4 header values:
* DSCP: set to 0 * DSCP: set to 0
* TTL: set to 255 * TTL: set to 255
* Protocol: Set to 01 (ICMP) * Protocol: Set to 01 (ICMP)
o IPv6 header values: o IPv6 header values:
* DSCP: set to 0 * DSCP: set to 0
* Hop Limit: set to 255 * Hop Limit: set to 255
skipping to change at page 62, line 23 skipping to change at page 56, line 49
section 6 of [RFC5905]. section 6 of [RFC5905].
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
info>
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, and counted for the RTLoss metric. delay, and counted for the RTLoss metric.
skipping to change at page 64, line 11 skipping to change at page 58, line 33
interval for the next sending time is nominally Tmax. interval for the next sending time is nominally Tmax.
If an immediate send on reply arrival is desired, then set incT=0. If an immediate send on reply arrival is desired, then set incT=0.
9.3.3. Traffic Filtering (observation) Details 9.3.3. Traffic Filtering (observation) Details
The measured results based on a filtered version of the packets The measured results based on a filtered version of the packets
observed, and this section provides the filter details (when observed, and this section provides the filter details (when
present). present).
<section reference>.
NA NA
9.3.4. Sampling Distribution 9.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
NA NA
9.3.5. Run-time Parameters and Data Format 9.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the Src Role (format ipv4-address- Src the IP address of the host in the Src Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see Section 4 of [RFC6991]) see Section 4 of [RFC6991])
Dst the IP address of the host in the Dst Role (format ipv4-address- Dst the IP address of the host in the Dst Role (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 65, line 7 skipping to change at page 59, line 20
interval. The start time is controlled through other means. interval. The start time is controlled through other means.
Count The total count of ICMP Echo Requests to send, formatted as a Count The total count of ICMP Echo Requests to send, formatted as a
uint16, as per section 9.2 of [RFC6020]. uint16, as per section 9.2 of [RFC6020].
(see the Packet Stream Generation section for additional Run-time (see the Packet Stream Generation section for additional Run-time
parameters) parameters)
9.3.6. Roles 9.3.6. Roles
<lists the names of the different roles from the measurement method>
Src launches each packet and waits for return transmissions from Src launches each packet and waits for return transmissions from
Dst. Dst.
Dst waits for each packet from Src and sends a return packet to Src. Dst waits for each packet from Src and sends a return packet to Src.
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>
See subsection titles in Reference Definition for Latency Types. See subsection titles in Reference Definition for Latency Types.
LossRatio -- the count of lost packets to total packets sent is the 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]. basis for the loss ratio calculation as per Section 6.1 of [RFC6673].
9.4.2. Reference Definition 9.4.2. Reference Definition
<describe the data format for each type of result>
For all output types --- For all output types ---
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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
skipping to change at page 67, line 22 skipping to change at page 61, line 32
FiniteDelay[j] >= FiniteDelay[n] for all n FiniteDelay[j] >= FiniteDelay[n] for all n
Max The time value of the result is expressed in units of seconds, Max The time value of the result is expressed in units of seconds,
as a positive value of type decimal64 with fraction digits = 9 as a positive value of type decimal64 with fraction digits = 9
(see section 9.3 of [RFC6020]) with resolution of 0.000000001 (see section 9.3 of [RFC6020]) with resolution of 0.000000001
seconds (1.0 ns), and with lossless conversion to/from the 64-bit seconds (1.0 ns), and with lossless conversion to/from the 64-bit
NTP timestamp as per section 6 of RFC [RFC5905] NTP timestamp as per section 6 of RFC [RFC5905]
9.4.3. Metric Units 9.4.3. Metric Units
<insert units for the measured results, and the reference
specification>.
The <statistic> of Round-trip Delay is expressed in seconds, where The <statistic> of Round-trip Delay is expressed in seconds, where
<statistic> is one of: <statistic> is one of:
o Mean o Mean
o Min o Min
o Max o Max
The Round-trip Loss Ratio is expressed as a percentage of lost The Round-trip Loss Ratio is expressed as a percentage of lost
skipping to change at page 68, line 15 skipping to change at page 62, line 22
Both internal loopback calibration and clock synchronization can be Both internal loopback calibration and clock synchronization can be
used to estimate the *available accuracy* of the Output Metric Units. used to estimate the *available accuracy* of the Output Metric Units.
For example, repeated loopback delay measurements will reveal the For example, repeated loopback delay measurements will reveal the
portion of the Output result resolution which is the result of system portion of the Output result resolution which is the result of system
noise, and thus inaccurate. noise, and thus inaccurate.
9.5. Administrative items 9.5. Administrative items
9.5.1. Status 9.5.1. Status
<current or deprecated> Current
9.5.2. Requestor (keep?) 9.5.2. Requestor
name or RFC, etc. This RFC number
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
9.6. Comments and Remarks 9.6. Comments and Remarks
Additional (Informational) details for this entry None
10. TCP Round-Trip Delay and Loss Registry Entries 10. TCP Round-Trip Delay and Loss Registry Entries
This section specifies three initial registry entries for the Passive This section specifies three initial registry entries for the Passive
assessment of TCP Round-Trip Delay (RTD) and another entry for TCP assessment of TCP Round-Trip Delay (RTD) and another entry for TCP
Round-trip Loss Count. Round-trip Loss Count.
This section specifies four Registry entries with many common This section specifies four Registry entries with many common
columns. columns.
skipping to change at page 69, line 7 skipping to change at page 63, line 14
asked to assign four corresponding URNs and URLs to each Named asked to assign four corresponding URNs and URLs to each Named
Metric. Metric.
10.1. Summary 10.1. Summary
This category includes multiple indexes to the registry entry: the This category includes multiple indexes to the registry entry: the
element ID and metric name. element ID and metric name.
10.1.1. ID (Identifier) 10.1.1. ID (Identifier)
<insert a numeric identifier, an integer, TBD>
IANA is asked to assign different numeric identifiers to each of the IANA is asked to assign different numeric identifiers to each of the
four Named Metrics. four Named Metrics.
10.1.2. Name 10.1.2. Name
<insert name according to metric naming convention>
RTDelay_Passive_IP-TCP_RFCXXXXsecY_Seconds_<statistic> RTDelay_Passive_IP-TCP_RFCXXXXsecY_Seconds_<statistic>
where <statistic> is one of: where <statistic> is one of:
o Mean o Mean
o Min o Min
o Max o Max
skipping to change at page 70, line 28 skipping to change at page 64, line 33
1.0 1.0
10.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. and values of input factors, called fixed parameters.
10.2.1. Reference Definitions 10.2.1. Reference Definitions
<Full bibliographic reference to an immutable doc.>
Although there is no RFC that describes passive measurement of Round- Although there is no RFC that describes passive measurement of Round-
Trip Delay, the parallel definition for Active measurement is: Trip Delay, the parallel definition for Active measurement is:
Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay
Metric for IPPM", RFC 2681, September 1999. Metric for IPPM", RFC 2681, September 1999.
[RFC2681] [RFC2681]
<specific section reference and additional clarifications, if needed>
This metric definition uses the terms singleton and sample as defined This metric definition uses the terms singleton and sample as defined
in Section 11 of [RFC2330]. (Section 2.4 of [RFC2681] provides the in Section 11 of [RFC2330]. (Section 2.4 of [RFC2681] provides the
reference definition of the singleton (single value) Round-trip delay reference definition of the singleton (single value) Round-trip delay
metric. Section 3.4 of [RFC2681] provides the reference definition metric. Section 3.4 of [RFC2681] provides the reference definition
expanded to cover a multi-singleton sample.) expanded to cover a multi-singleton sample.)
With the Observation Point [RFC7011] (OP) typically located between With the Observation Point [RFC7011] (OP) typically located between
the hosts participating in the TCP connection, the Round-trip Delay the hosts participating in the TCP connection, the Round-trip Delay
metric requires two individual measurements between the OP and each metric requires two individual measurements between the OP and each
host, such that the Spatial Composition [RFC6049]of the measurements host, such that the Spatial Composition [RFC6049]of the measurements
skipping to change at page 73, line 35 skipping to change at page 67, line 35
o o
10.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. unambiguous methods for implementations.
10.3.1. Reference Methods 10.3.1. Reference Methods
<for metric, insert relevant section references and supplemental
info>
The foundation methodology for this metric is defined in Section 4 of The foundation methodology for this metric is defined in Section 4 of
[RFC7323] using the Timestamp Option with modifications that allow [RFC7323] using the Timestamp Option with modifications that allow
application at a mid-path Observation Point (OP) [RFC7011]. Further application at a mid-path Observation Point (OP) [RFC7011]. Further
details and applicable heuristics were derived from [Strowes] and details and applicable heuristics were derived from [Strowes] and
[Trammell-14]. [Trammell-14].
The Traffic Filter at the OP is configured to observe a single TCP The Traffic Filter at the OP is configured to observe a single TCP
connection. When the SYN, SYN-ACK, ACK handshake occurs, it offers connection. When the SYN, SYN-ACK, ACK handshake occurs, it offers
the first opportunity to measure both RTD_fwd (on the SYN to SYN-ACK the first opportunity to measure both RTD_fwd (on the SYN to SYN-ACK
pair) and RTD_rev (on the SYN-ACK to ACK pair). Label this singleton pair) and RTD_rev (on the SYN-ACK to ACK pair). Label this singleton
skipping to change at page 74, line 32 skipping to change at page 68, line 29
measurement using a packet unless it makes progress in the transfer measurement using a packet unless it makes progress in the transfer
(advances the left edge of the send window, consistent (advances the left edge of the send window, consistent
with[Strowes]). with[Strowes]).
A different heuristic from [Trammell-14] is to exclude any RTD_rev A different heuristic from [Trammell-14] is to exclude any RTD_rev
that is larger than previously observed values. This would tend to that is larger than previously observed values. This would tend to
exclude Reverse measurements taken when the Application has no data exclude Reverse measurements taken when the Application has no data
ready to send, because considerable time could be added to RTD_rev ready to send, because considerable time could be added to RTD_rev
from this source of error. from this source of error.
@@@@ Note that the above Heuristic assumes that host A is sending Note that the above Heuristic assumes that host A is sending data.
data. Host A expecting a download would mean that this heuristic Host A expecting a download would mean that this heuristic should be
should be applied to RTD_fwd. applied to RTD_fwd.
The statistic calculations to summarize the delay (RTDelay) SHALL be The statistic calculations to summarize the delay (RTDelay) SHALL be
performed on the conditional distribution, conditioned on successful performed on the conditional distribution, conditioned on successful
Forward and Reverse measurements which follow the Heuristics. Forward and Reverse measurements which follow the Heuristics.
Method for Inferring Loss: Method for Inferring Loss:
The OP tracks sequence numbers and stores gaps for each direction of The OP tracks sequence numbers and stores gaps for each direction of
transmission, as well as the next-expected sequence number as in transmission, as well as the next-expected sequence number as in
[Trammell-14] and [RFC4737]. Loss is inferred from Out-of-order [Trammell-14] and [RFC4737]. Loss is inferred from Out-of-order
skipping to change at page 75, line 41 skipping to change at page 69, line 39
The measured results based on a filtered version of the packets The measured results based on a filtered version of the packets
observed, and this section provides the filter details (when observed, and this section provides the filter details (when
present). present).
The Fixed Parameters above give a portion of the Traffic Filter. The Fixed Parameters above give a portion of the Traffic Filter.
Other aspects will be supplied as Run-time Parameters (below). Other aspects will be supplied as Run-time Parameters (below).
10.3.4. Sampling Distribution 10.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
This metric requires a complete sample of all packets that qualify This metric requires a complete sample of all packets that qualify
according to the Traffic Filter criteria. according to the Traffic Filter criteria.
10.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. for the context to be complete.
<list of run-time parameters, and their data formats>
Src the IP address of the host in the host A Role (format ipv4- Src the IP address of the host in the host A Role (format ipv4-
address-no-zone value for IPv4, or ipv6-address-no-zone value for address-no-zone value for IPv4, or ipv6-address-no-zone value for
IPv6, see Section 4 of [RFC6991]) IPv6, see Section 4 of [RFC6991])
Dst the IP address of the host in the host B (format ipv4-address- Dst the IP address of the host in the host B (format ipv4-address-
no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
see section 4 of [RFC6991]) see section 4 of [RFC6991])
T0 a time, the start of a measurement interval, (format "date-and- T0 a time, the start of a measurement interval, (format "date-and-
time" as specified in Section 5.6 of [RFC3339], see also Section 3 time" as specified in Section 5.6 of [RFC3339], see also Section 3
skipping to change at page 76, line 34 skipping to change at page 70, line 28
of [RFC6991]), or the duration (see T0). The UTC Time Zone is of [RFC6991]), or the duration (see T0). The UTC Time Zone is
required by Section 6.1 of [RFC2330]. Alternatively, the end of required by Section 6.1 of [RFC2330]. Alternatively, the end of
the measurement interval MAY be controlled by the measured the measurement interval MAY be controlled by the measured
connection, where the second pair of FIN and ACK packets exchanged connection, where the second pair of FIN and ACK packets exchanged
between host A and B effectively ends the interval. between host A and B effectively ends the interval.
TTL or Hop Limit Set at desired value. TTL or Hop Limit Set at desired value.
10.3.6. Roles 10.3.6. Roles
<lists the names of the different roles from the measurement method>
host A launches the SYN packet to open the connection, and host A launches the SYN packet to open the connection, and
synonymous with an IP address. synonymous with an IP address.
host B replies with the SYN-ACK packet to open the connection, and host B replies with the SYN-ACK packet to open the connection, and
synonymous with an IP address. synonymous with an IP address.
10.4. Output 10.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.
10.4.1. Type 10.4.1. Type
<insert name of the output type, raw or a selected summary statistic>
See subsection titles in Reference Definition for RTDelay Types. See subsection titles in Reference Definition for RTDelay Types.
For RTLoss -- the count of lost packets. For RTLoss -- the count of lost packets.
10.4.2. Reference Definition 10.4.2. Reference Definition
<describe the data format for each type of result>
For all output types --- For all output types ---
T0 the start of a measurement interval, (format "date-and-time" as T0 the start of a measurement interval, (format "date-and-time" as
specified in Section 5.6 of [RFC3339], see also Section 3 of 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]. [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
specified in Section 5.6 of [RFC3339], see also Section 3 of 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
skipping to change at page 79, line 7 skipping to change at page 72, line 38
FiniteDelay[j] >= FiniteDelay[n] for all n FiniteDelay[j] >= FiniteDelay[n] for all n
Max The time value of the result is expressed in units of seconds, Max The time value of the result is expressed in units of seconds,
as a positive value of type decimal64 with fraction digits = 9 as a positive value of type decimal64 with fraction digits = 9
(see section 9.3 of [RFC6020]) with resolution of 0.000000001 (see section 9.3 of [RFC6020]) with resolution of 0.000000001
seconds (1.0 ns), and with lossless conversion to/from the 64-bit seconds (1.0 ns), and with lossless conversion to/from the 64-bit
NTP timestamp as per section 6 of RFC [RFC5905] NTP timestamp as per section 6 of RFC [RFC5905]
10.4.3. Metric Units 10.4.3. Metric Units
<insert units for the measured results, and the reference
specification>.
The <statistic> of Round-trip Delay is expressed in seconds, where The <statistic> of Round-trip Delay is expressed in seconds, where
<statistic> is one of: <statistic> is one of:
o Mean o Mean
o Min o Min
o Max o Max
The Round-trip Delay of the Hand Shake is expressed in seconds. The Round-trip Delay of the Hand Shake is expressed in seconds.
skipping to change at page 79, line 33 skipping to change at page 73, line 15
10.4.4. Calibration 10.4.4. Calibration
Passive measurements at an OP could be calibrated against an active Passive measurements at an OP could be calibrated against an active
measurement (with loss emulation) at host A or B, where the active measurement (with loss emulation) at host A or B, where the active
measurement represents the ground-truth. measurement represents the ground-truth.
10.5. Administrative items 10.5. Administrative items
10.5.1. Status 10.5.1. Status
<current or deprecated> Current
10.5.2. Requestor (keep?) 10.5.2. Requestor
name or RFC, etc. This RFC
10.5.3. Revision 10.5.3. Revision
1.0 1.0
10.5.4. Revision Date 10.5.4. Revision Date
YYYY-MM-DD YYYY-MM-DD
10.6. Comments and Remarks 10.6. Comments and Remarks
Additional (Informational) details for this entry None.
11. ver08 BLANK Registry Entry
This section gives an initial registry entry for ....
11.1. Summary
This category includes multiple indexes to the registry entries, the
element ID and metric name.
11.1.1. ID (Identifier)
<insert numeric identifier, an integer>
11.1.2. Name
<insert name according to metric naming convention>
11.1.3. URIs
URI: Prefix urn:ietf:metrics:perf:<name>
URL:
11.1.4. Description
TBD.
11.1.5. Reference
<reference to the RFC of spec where the registry entry is defined>
11.1.6. Change Controller
<org or person >
11.1.7. Version (of Registry Format)
<currently 1.0>
11.2. Metric Definition
This category includes columns to prompt the entry of all necessary
details related to the metric definition, including the RFC reference
and values of input factors, called fixed parameters.
11.2.1. Reference Definition
<Full bibliographic reference to an immutable doc.>
<specific section reference and additional clarifications, if needed>
11.2.2. Fixed Parameters
<list and specify Fixed Parameters, input factors that must be
determined and embedded in the measurement system for use when
needed>
11.3. Method of Measurement
This category includes columns for references to relevant sections of
the RFC(s) and any supplemental information needed to ensure an
unambiguous methods for implementations.
11.3.1. Reference Method
<for metric, insert relevant section references and supplemental
info>
11.3.2. Packet Stream Generation
<list of generation parameters and section/spec references if needed>
11.3.3. Traffic Filtering (observation) Details
<insert the measured results based on a filtered version of the
packets observed, and this section provides the filter details (when
present), and section reference>.
11.3.4. Sampling Distribution
<insert time distribution details, or how this is diff from the
filter>
11.3.5. Run-time Parameters and Data Format
<list of run-time parameters, and any reference(s)>.
11.3.6. Roles
<lists the names of the different roles from the measurement method>
11.4. Output
This category specifies all details of the Output of measurements
using the metric.
11.4.1. Type
<insert name of the output type, raw or a selected summary statistic>
11.4.2. Reference Definition
<pointer to section/spec where output type/format is defined>
11.4.3. Metric Units
<insert units for the measured results, and the reference
specification>.
11.4.4. Calibration
<describe the error calibration, a way to indicate that the results
were collected in a calibration mode of operation, and a way to
report internal status metrics related to calibration, such as time
offset>
11.5. Administrative items
11.5.1. Status
<current or deprecated>
11.5.2. Requestor
<name of individual or Internet Draft, etc.>
11.5.3. Revision
1.0
11.5.4. Revision Date
YYYY-MM-DD
11.6. Comments and Remarks
Additional (Informational) details for this entry
12. Example RTCP-XR Registry Entry
This section is MAY BE DELETED or adapted before submission.
This section gives an example registry entry for the end-point metric
described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric
reporting.
12.1. Registry Indexes
This category includes multiple indexes to the registry entries, the
element ID and metric name.
12.1.1. Identifier
An integer having enough digits to uniquely identify each entry in
the Registry.
12.1.2. Name
A metric naming convention is TBD.
12.1.3. URI
Prefix urn:ietf:metrics:param:<name>
12.1.4. Status
current
12.1.5. Requestor
Alcelip Mornuley
12.1.6. Revision
1.0
12.1.7. Revision Date
2014-07-04
12.1.8. Description
TBD.
12.1.9. Reference Specification(s)
[RFC3611][RFC4566][RFC6776][RFC6792][RFC7003]
12.2. Metric Definition
This category includes columns to prompt the entry of all necessary
details related to the metric definition, including the RFC reference
and values of input factors, called fixed parameters. Section 3.2 of
[RFC7003] provides the reference information for this category.
12.2.1. Reference Definition
Packets Discarded in Bursts:
The total number of packets discarded during discard bursts. The
measured value is unsigned value. If the measured value exceeds
0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over-
range measurement. If the measurement is unavailable, the value
0xFFFFFF MUST be reported.
12.2.2. Fixed Parameters
Fixed Parameters are input factors that must be determined and
embedded in the measurement system for use when needed. The values
of these parameters is specified in the Registry.
Threshold: 8 bits, set to value = 3 packets.
The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of
successive packets that must not be discarded prior to and following
a discard packet in order for this discarded packet to be regarded as
part of a gap. Note that the Threshold is set in accordance with the
Gmin calculation defined in Section 4.7.2 of [RFC3611].
Interval Metric flag: 2 bits, set to value 11=Cumulative Duration
This field is used to indicate whether the burst/gap discard metrics
are Sampled, Interval, or Cumulative metrics [RFC6792]:
I=10: Interval Duration - the reported value applies to the most
recent measurement interval duration between successive metrics
reports.
I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements.
Senders MUST NOT use the values I=00 or I=01.
12.3. Method of Measurement
This category includes columns for references to relevant sections of
the RFC(s) and any supplemental information needed to ensure an
unambiguous methods for implementations. For the Burst/Gap Discard
Metric, it appears that the only guidance on methods of measurement
is in Section 3.0 of [RFC7003] and its supporting references.
Relevant information is repeated below, although there appears to be
no section titled "Method of Measurement" in [RFC7003].
12.3.1. Reference Method
Metrics in this block report on burst/gap discard in the stream
arriving at the RTP system. Measurements of these metrics are made
at the receiving end of the RTP stream. Instances of this metrics
block use the synchronization source (SSRC) to refer to the separate
auxiliary Measurement Information Block [RFC6776], which describes
measurement periods in use (see [RFC6776], Section 4.2).
This metrics block relies on the measurement period in the
Measurement Information Block indicating the span of the report.
Senders MUST send this block in the same compound RTCP packet as the
Measurement Information Block. Receivers MUST verify that the
measurement period is received in the same compound RTCP packet as
this metrics block. If not, this metrics block MUST be discarded.
12.3.2. Stream Type and Stream Parameters
Since RTCP-XR Measurements are conducted on live RTP traffic, the
complete description of the stream is contained in SDP messages that
proceed the establishment of a compatible stream between two or more
communicating hosts. See Run-time Parameters, below.
12.3.3. Output Type and Data Format
The output type defines the type of result that the metric produces.
o Value: Packets Discarded in Bursts
o Data Format: 24 bits
o Reference: Section 3.2 of [RFC7003]
12.3.4. Metric Units
The measured results are apparently expressed in packets, although
there is no section of [RFC7003] titled "Metric Units".
12.3.5. Run-time Parameters and Data Format
Run-Time Parameters are input factors that must be determined,
configured into the measurement system, and reported with the results
for the context to be complete. However, the values of these
parameters is not specified in the Registry, rather these parameters
are listed as an aid to the measurement system implementor or user
(they must be left as variables, and supplied on execution).
The Data Format of each Run-time Parameter SHALL be specified in this
column, to simplify the control and implementation of measurement
devices.
SSRC of Source: 32 bits As defined in Section 4.1 of [RFC3611].
SDP Parameters: As defined in [RFC4566]
Session description v= (protocol version number, currently only 0)
o= (originator and session identifier : username, id, version number,
network address)
s= (session name : mandatory with at least one UTF-8-encoded
character)
i=* (session title or short information) u=* (URI of description)
e=* (zero or more email address with optional name of contacts)
p=* (zero or more phone number with optional name of contacts)
c=* (connection information--not required if included in all media)
b=* (zero or more bandwidth information lines) One or more Time
descriptions ("t=" and "r=" lines; see below)
z=* (time zone adjustments)
k=* (encryption key)
a=* (zero or more session attribute lines)
Zero or more Media descriptions (each one starting by an "m=" line;
see below)
m= (media name and transport address)
i=* (media title or information field)
c=* (connection information -- optional if included at session level)
b=* (zero or more bandwidth information lines)
k=* (encryption key)
a=* (zero or more media attribute lines -- overriding the Session
attribute lines)
An example Run-time SDP description follows:
v=0
o=jdoe 2890844526 2890842807 IN IP4 192.0.2.5
s=SDP Seminar i=A Seminar on the session description protocol
u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane
Doe)
c=IN IP4 233.252.0.12/127
t=2873397496 2873404696
a=recvonly
m=audio 49170 RTP/AVP 0
m=video 51372 RTP/AVP 99
a=rtpmap:99 h263-1998/90000
12.4. Comments and Remarks
TBD.
13. Revision History
This section may be removed for publication. It contains overview
information on updates.
This draft replaced draft-mornuley-ippm-initial-registry.
In version 02, Section 4 has been edited to reflect recent discussion
on the ippm-list: * Removed the combination or "Raw" and left 95th
percentile. * Hanging Indent on Run-time parameters (Fixed parameters
use bullet lists and other indenting formats. * Payload format for
measurement has been removed. * Explanation of Conditional delay
distribution.
Version 03 addressed Phil Eardley's comments and suggestions in
sections 1-4. and resolved the definition of Percentiles.
Version 04 * All section 4 parameters reference YANG types for
alternate data formats. * Discussion has concluded that usecase(s)
for machine parse-able registry columns are not needed.
Version 05 * Revised several Poisson streams to Periodic, sections 4
& 5. * Addition of ICMP (ping) metrics in section 9. * First
implementation of Passive TCP RTT metrics in section 10.
14. Security Considerations 11. Security Considerations
These registry entries represent no known security implications for These registry entries represent no known implications for Internet
Internet Security. Each referenced Metric contains a Security Security. Each referenced Metric contains a Security Considerations
Considerations section. section.
15. IANA Considerations 12. 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.
See the IANA Considerations section of See the IANA Considerations section of
[I-D.ietf-ippm-metric-registry] for additional requests and [I-D.ietf-ippm-metric-registry] for additional requests and
considerations. considerations.
16. Acknowledgements 13. Acknowledgements
The authors thank Brian Trammell for suggesting the term "Run-time The authors thank Brian Trammell for suggesting the term "Run-time
Parameters", which led to the distinction between run-time and fixed Parameters", which led to the distinction between run-time and fixed
parameters implemented in this memo, for identifying the IPFIX metric parameters implemented in this memo, for identifying the IPFIX metric
with Flow Key as an example, for suggesting the Passive TCP RTD with Flow Key as an example, for suggesting the Passive TCP RTD
metric and supporting references, and for many other productive metric and supporting references, and for many other productive
suggestions. Thanks to Peter Koch, who provided several useful suggestions. Thanks to Peter Koch, who provided several useful
suggestions for disambiguating successive DNS Queries in the DNS suggestions for disambiguating successive DNS Queries in the DNS
Response time metric. Response time metric.
The authors also acknowledge the constructive reviews and helpful The authors also acknowledge the constructive reviews and helpful
suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey, and suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey,
participants in the LMAP working group. Thanks to Michelle Cotton Yaakov Stein, and participants in the LMAP working group. Thanks to
for her early IANA review, and to Amanda Barber for answering Michelle Cotton for her early IANA review, and to Amanda Barber for
questions related to the presentation of the registry and answering questions related to the presentation of the registry and
accessibility of the complete template via URL. accessibility of the complete template via URL.
17. References 14. References
17.1. Normative References 14.1. Normative References
[I-D.ietf-ippm-metric-registry] [I-D.ietf-ippm-metric-registry]
Bagnulo, M., Claise, B., Eardley, P., and A. Morton, Bagnulo, M., Claise, B., Eardley, P., and A. Morton,
"Registry for Performance Metrics", Internet Draft (work "Registry for Performance Metrics", Internet Draft (work
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, <https://www.rfc-editor.org/info/rfc1035>. November 1987, <https://www.rfc-editor.org/info/rfc1035>.
skipping to change at page 91, line 24 skipping to change at page 76, line 34
[RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, [RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Loss Metric for IP Performance Metrics Ed., "A One-Way Loss Metric for IP Performance Metrics
(IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January (IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January
2016, <https://www.rfc-editor.org/info/rfc7680>. 2016, <https://www.rfc-editor.org/info/rfc7680>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
17.2. Informative References 14.2. Informative References
[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, <https://www.rfc-editor.org/info/rfc1242>. July 1991, <https://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)",
RFC 3611, DOI 10.17487/RFC3611, November 2003, RFC 3611, DOI 10.17487/RFC3611, November 2003,
<https://www.rfc-editor.org/info/rfc3611>. <https://www.rfc-editor.org/info/rfc3611>.
 End of changes. 141 change blocks. 
923 lines changed or deleted 259 lines changed or added

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