draft-ietf-ippm-initial-registry-15.txt   draft-ietf-ippm-initial-registry-16.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Standards Track M. Bagnulo Intended status: Standards Track M. Bagnulo
Expires: June 13, 2020 UC3M Expires: September 10, 2020 UC3M
P. Eardley P. Eardley
BT BT
K. D'Souza K. D'Souza
AT&T Labs AT&T Labs
December 11, 2019 March 9, 2020
Initial Performance Metrics Registry Entries Initial Performance Metrics Registry Entries
draft-ietf-ippm-initial-registry-15 draft-ietf-ippm-initial-registry-16
Abstract Abstract
This memo defines the set of Initial Entries for the IANA Performance This memo defines the set of Initial Entries for the IANA Performance
Metrics Registry. The set includes: UDP Round-trip Latency and Loss, Metrics Registry. The set includes: UDP Round-trip Latency and Loss,
Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson Packet Delay Variation, DNS Response Latency and Loss, UDP Poisson
One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP One-way Delay and Loss, UDP Periodic One-way Delay and Loss, ICMP
Round-trip Latency and Loss, and TCP round-trip Latency and Loss. Round-trip Latency and Loss, and TCP round-trip Latency and Loss.
Requirements Language Requirements Language
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 13, 2020. This Internet-Draft will expire on September 10, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Registry Categories and Columns . . . . . . . . . . . . . . . 7 3. Registry Categories and Columns . . . . . . . . . . . . . . . 7
4. UDP Round-trip Latency and Loss Registry Entries . . . . . . 8 4. UDP Round-trip Latency and Loss Registry Entries . . . . . . 8
4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9
4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9
4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 9 4.1.5. Change Controller . . . . . . . . . . . . . . . . . . 9
4.1.6. Version (of Registry Format) . . . . . . . . . . . . 9 4.1.6. Version (of Registry Format) . . . . . . . . . . . . 9
4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 10 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 10
4.2.1. Reference Definition . . . . . . . . . . . . . . . . 10 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 10
4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10
4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11
4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11
4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 12 4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 12
4.3.3. Traffic Filtering (observation) Details . . . . . . . 13 4.3.3. Traffic Filtering (observation) Details . . . . . . . 13
skipping to change at page 3, line 10 skipping to change at page 3, line 10
4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 16 4.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 16
4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16
4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16
4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16
5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16
5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16
5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17
5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 17 5.1.5. Change Controller . . . . . . . . . . . . . . . . . . 17
5.1.6. Version (of Registry Format) . . . . . . . . . . . . 17 5.1.6. Version (of Registry Format) . . . . . . . . . . . . 17
5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17
5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17
5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 18
5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 19 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 19
5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 19
5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19 5.3.2. Packet Stream Generation . . . . . . . . . . . . . . 19
5.3.3. Traffic Filtering (observation) Details . . . . . . . 20 5.3.3. Traffic Filtering (observation) Details . . . . . . . 20
skipping to change at page 4, line 20 skipping to change at page 4, line 20
6.5. Administrative items . . . . . . . . . . . . . . . . . . 32 6.5. Administrative items . . . . . . . . . . . . . . . . . . 32
6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 32 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 32
6.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 32 6.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 32
6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 32 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 32
6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 32 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 32
6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 32 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 32
7. UDP Poisson One-way Delay and Loss Registry Entries . . . . . 32 7. UDP Poisson One-way Delay and Loss Registry Entries . . . . . 32
7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 33 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 33
7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 33 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 33
7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 33 7.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 33 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 33
7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 34 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 34
7.2.1. Reference Definition . . . . . . . . . . . . . . . . 34 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 34
7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 35 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 35
7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 36 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 36
7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 36 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 36
7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 36 7.3.2. Packet Stream Generation . . . . . . . . . . . . . . 36
7.3.3. Traffic Filtering (observation) Details . . . . . . . 37 7.3.3. Traffic Filtering (observation) Details . . . . . . . 37
7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 37 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 37
7.3.5. Run-time Parameters and Data Format . . . . . . . . . 37 7.3.5. Run-time Parameters and Data Format . . . . . . . . . 37
skipping to change at page 4, line 47 skipping to change at page 4, line 47
7.5. Administrative items . . . . . . . . . . . . . . . . . . 42 7.5. Administrative items . . . . . . . . . . . . . . . . . . 42
7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 42 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 42
7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 42 7.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 42
7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 42 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 42
7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 43 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 43
7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 43 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 43
8. UDP Periodic One-way Delay and Loss Registry Entries . . . . 43 8. UDP Periodic One-way Delay and Loss Registry Entries . . . . 43
8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 43 8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 43 8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 43
8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 43 8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 44 8.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 44 8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 44
8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 44 8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 44
8.2.1. Reference Definition . . . . . . . . . . . . . . . . 44 8.2.1. Reference Definition . . . . . . . . . . . . . . . . 44
8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 45 8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 45
8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 46 8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 46
8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 46 8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 46
8.3.2. Packet Stream Generation . . . . . . . . . . . . . . 47 8.3.2. Packet Stream Generation . . . . . . . . . . . . . . 47
8.3.3. Traffic Filtering (observation) Details . . . . . . . 48 8.3.3. Traffic Filtering (observation) Details . . . . . . . 48
8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 48 8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 48
8.3.5. Run-time Parameters and Data Format . . . . . . . . . 48 8.3.5. Run-time Parameters and Data Format . . . . . . . . . 48
skipping to change at page 5, line 25 skipping to change at page 5, line 25
8.5. Administrative items . . . . . . . . . . . . . . . . . . 53 8.5. Administrative items . . . . . . . . . . . . . . . . . . 53
8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 53 8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 53
8.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 53 8.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 53
8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 53 8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 53
8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 53 8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 53
8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 54 8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 54
9. ICMP Round-trip Latency and Loss Registry Entries . . . . . . 54 9. ICMP Round-trip Latency and Loss Registry Entries . . . . . . 54
9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 54 9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 54 9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 54
9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 54 9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 54 9.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 54
9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 55 9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 55
9.1.5. Change Controller . . . . . . . . . . . . . . . . . . 55 9.1.5. Change Controller . . . . . . . . . . . . . . . . . . 55
9.1.6. Version (of Registry Format) . . . . . . . . . . . . 55 9.1.6. Version (of Registry Format) . . . . . . . . . . . . 55
9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 55 9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 55
9.2.1. Reference Definition . . . . . . . . . . . . . . . . 55 9.2.1. Reference Definition . . . . . . . . . . . . . . . . 55
9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 56 9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 56
9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 57 9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 57
9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 57 9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 57
9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 58 9.3.2. Packet Stream Generation . . . . . . . . . . . . . . 58
9.3.3. Traffic Filtering (observation) Details . . . . . . . 59 9.3.3. Traffic Filtering (observation) Details . . . . . . . 59
skipping to change at page 6, line 6 skipping to change at page 6, line 6
9.5. Administrative items . . . . . . . . . . . . . . . . . . 62 9.5. Administrative items . . . . . . . . . . . . . . . . . . 62
9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 62 9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 62
9.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 63 9.5.2. Requester . . . . . . . . . . . . . . . . . . . . . . 63
9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 63 9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 63
9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 63 9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 63
9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 63 9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 63
10. TCP Round-Trip Delay and Loss Registry Entries . . . . . . . 63 10. TCP Round-Trip Delay and Loss Registry Entries . . . . . . . 63
10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 63 10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 63
10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 63 10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 63
10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 63 10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 63
10.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 64 10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 64
10.1.4. Description . . . . . . . . . . . . . . . . . . . . 64 10.1.4. Description . . . . . . . . . . . . . . . . . . . . 64
10.1.5. Change Controller . . . . . . . . . . . . . . . . . 64 10.1.5. Change Controller . . . . . . . . . . . . . . . . . 64
10.1.6. Version (of Registry Format) . . . . . . . . . . . . 64 10.1.6. Version (of Registry Format) . . . . . . . . . . . . 64
10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 65 10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 65
10.2.1. Reference Definitions . . . . . . . . . . . . . . . 65 10.2.1. Reference Definitions . . . . . . . . . . . . . . . 65
10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 67 10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 67
10.3. Method of Measurement . . . . . . . . . . . . . . . . . 68 10.3. Method of Measurement . . . . . . . . . . . . . . . . . 68
10.3.1. Reference Methods . . . . . . . . . . . . . . . . . 68 10.3.1. Reference Methods . . . . . . . . . . . . . . . . . 68
10.3.2. Packet Stream Generation . . . . . . . . . . . . . . 69 10.3.2. Packet Stream Generation . . . . . . . . . . . . . . 70
10.3.3. Traffic Filtering (observation) Details . . . . . . 70 10.3.3. Traffic Filtering (observation) Details . . . . . . 70
10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 70 10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 70
10.3.5. Run-time Parameters and Data Format . . . . . . . . 70 10.3.5. Run-time Parameters and Data Format . . . . . . . . 70
10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 70 10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 71
10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 71 10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 71 10.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 71
10.4.2. Reference Definition . . . . . . . . . . . . . . . . 71 10.4.2. Reference Definition . . . . . . . . . . . . . . . . 71
10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 73 10.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 73
10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 73 10.4.4. Calibration . . . . . . . . . . . . . . . . . . . . 73
10.5. Administrative items . . . . . . . . . . . . . . . . . . 73 10.5. Administrative items . . . . . . . . . . . . . . . . . . 73
10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 73 10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 73
10.5.2. Requester . . . . . . . . . . . . . . . . . . . . . 73 10.5.2. Requester . . . . . . . . . . . . . . . . . . . . . 73
10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 73 10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 74
10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 73 10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 74
10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 73 10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 74
11. Security Considerations . . . . . . . . . . . . . . . . . . . 74 11. Security Considerations . . . . . . . . . . . . . . . . . . . 74
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 74 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 74
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 75
14.1. Normative References . . . . . . . . . . . . . . . . . . 74 14.1. Normative References . . . . . . . . . . . . . . . . . . 75
14.2. Informative References . . . . . . . . . . . . . . . . . 77 14.2. Informative References . . . . . . . . . . . . . . . . . 77
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78
1. Introduction 1. Introduction
This memo proposes an initial set of entries for the Performance This memo proposes an initial set of entries for the Performance
Metrics Registry. It uses terms and definitions from the IPPM Metrics Registry. It uses terms and definitions from the IPPM
literature, primarily [RFC2330]. literature, primarily [RFC2330].
Although there are several standard templates for organizing Although there are several standard templates for organizing
specifications of performance metrics (see [RFC7679] for an example specifications of performance metrics (see [RFC7679] for an example
of the traditional IPPM template, based to large extent on the of the traditional IPPM template, based to large extent on the
skipping to change at page 7, line 18 skipping to change at page 7, line 18
Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format
for a Performance Metrics Registry. Section 5 of for a Performance Metrics Registry. Section 5 of
[I-D.ietf-ippm-metric-registry] also gives guidelines for those [I-D.ietf-ippm-metric-registry] also gives guidelines for those
requesting registration of a Metric, that is the creation of entry(s) requesting registration of a Metric, that is the creation of entry(s)
in the Performance Metrics Registry: "In essence, there needs to be in the Performance Metrics Registry: "In essence, there needs to be
evidence that a candidate Registered Performance Metric has evidence that a candidate Registered Performance Metric has
significant industry interest, or has seen deployment, and there is significant industry interest, or has seen deployment, and there is
agreement that the candidate Registered Performance Metric serves its agreement that the candidate Registered Performance Metric serves its
intended purpose." The process in [I-D.ietf-ippm-metric-registry] intended purpose." The process in [I-D.ietf-ippm-metric-registry]
also requires that new entries are administered by IANA through also requires that new entries are administered by IANA through
Specification Required policy, which includes Expert Review, which Specification Required policy, which will ensure that the metrics are
will ensure that the metrics are tightly defined. tightly defined.
2. Scope 2. Scope
This document defines a set of initial Performance Metrics Registry This document defines a set of initial Performance Metrics Registry
entries. Most are Active Performance Metrics, which are based on entries. Most are Active Performance Metrics, which are based on
RFCs prepared in the IPPM working group of the IETF, according to RFCs prepared in the IPPM working group of the IETF, according to
their framework [RFC2330] and its updates. their framework [RFC2330] and its updates.
3. Registry Categories and Columns 3. Registry Categories and Columns
skipping to change at page 8, line 13 skipping to change at page 8, line 13
description of a Registered Metric. description of a Registered Metric.
Legend: Legend:
Registry Categories and Columns, shown as Registry Categories and Columns, shown as
Category Category
------------------ ------------------
Column | Column | Column | Column |
Summary Summary
------------------------------------------------------------------------ ------------------------------------------------------------------------
Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver | Identifier | Name | URI | Desc. | Reference | Change Controller | Ver |
Metric Definition Metric Definition
----------------------------------------- -----------------------------------------
Reference Definition | Fixed Parameters | Reference Definition | Fixed Parameters |
Method of Measurement Method of Measurement
--------------------------------------------------------------------- ---------------------------------------------------------------------
Reference | Packet | Traffic | Sampling | Run-time | Role | Reference | Packet | Traffic | Sampling | Run-time | Role |
Method | Stream | Filter | Distribution | Parameters | | Method | Stream | Filter | Distribution | Parameters | |
| Generation | | Generation |
skipping to change at page 8, line 45 skipping to change at page 8, line 45
4. UDP Round-trip Latency and Loss Registry Entries 4. UDP Round-trip Latency and Loss Registry Entries
This section specifies an initial registry entry for the UDP Round- This section specifies an initial registry entry for the UDP Round-
trip Latency, and another entry for UDP Round-trip Loss Ratio. trip Latency, and another entry for UDP Round-trip Loss Ratio.
Note: Each Registry entry only produces a "raw" output or a Note: Each Registry entry only produces a "raw" output or a
statistical summary. To describe both "raw" and one or more statistical summary. To describe both "raw" and one or more
statistics efficiently, the Identifier, Name, and Output Categories statistics efficiently, the Identifier, Name, and Output Categories
can be split and a single section can specify two or more closely- can be split and a single section can specify two or more closely-
related metrics. This section specifies two Registry entries with related metrics. For example, this section specifies two Registry
many common columns. See Section 7 for an example specifying entries with many common columns. See Section 7 for an example
multiple Registry entries with many common columns. specifying multiple Registry entries with many common 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
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 a corresponding URL to each Named Metric. asked to assign a corresponding URL 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.
skipping to change at page 9, line 23 skipping to change at page 9, line 23
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
RTDelay_Active_IP-UDP-Periodic_RFCXXXXsec4_Seconds_95Percentile RTDelay_Active_IP-UDP-Periodic_RFCXXXXsec4_Seconds_95Percentile
RTLoss_Active_IP-UDP-Periodic_RFCXXXXsec4_Percent_LossRatio RTLoss_Active_IP-UDP-Periodic_RFCXXXXsec4_Percent_LossRatio
4.1.3. URIs 4.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
4.1.4. Description 4.1.4. Description
RTDelay: This metric assesses the delay of a stream of packets RTDelay: This metric assesses the delay of a stream of packets
exchanged between two hosts (which are the two measurement points), exchanged between two hosts (which are the two measurement points),
and the Output is the Round-trip delay for all successfully exchanged and the Output is the Round-trip delay for all successfully exchanged
packets expressed as the 95th percentile of their conditional delay packets expressed as the 95th percentile of their conditional delay
distribution. distribution.
skipping to change at page 17, line 5 skipping to change at page 17, line 5
element ID and metric name. element ID and metric name.
5.1.1. ID (Identifier) 5.1.1. ID (Identifier)
<insert numeric identifier, an integer> <insert numeric identifier, an integer>
5.1.2. Name 5.1.2. Name
OWPDV_Active_IP-UDP-Periodic_RFCXXXXsec5_Seconds_95Percentile OWPDV_Active_IP-UDP-Periodic_RFCXXXXsec5_Seconds_95Percentile
5.1.3. URIs 5.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <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
skipping to change at page 29, line 7 skipping to change at page 29, line 7
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.
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 spacing, thus the Run-time Parameter is
= 1/lambda, in packets per second. Reciprocal_lambda = 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.
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.
skipping to change at page 33, line 30 skipping to change at page 33, line 30
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss_Active_IP-UDP-Poisson- OWLoss_Active_IP-UDP-Poisson-
Payload250B_RFCXXXXsec7_Percent_LossRatio Payload250B_RFCXXXXsec7_Percent_LossRatio
7.1.3. URI and URL 7.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
7.1.4. Description 7.1.4. Description
OWDelay: This metric assesses the delay of a stream of packets OWDelay: This metric assesses the delay of a stream of packets
exchanged between two hosts (or measurement points), and reports the exchanged between two hosts (or measurement points), and reports the
<statistic> One-way delay for all successfully exchanged packets <statistic> One-way delay for all successfully exchanged packets
based on their conditional delay distribution. based on their conditional delay distribution.
skipping to change at page 37, line 4 skipping to change at page 37, line 4
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.
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 spacing, thus the Run-time Parameter is
= 1/lambda, in packets per second. 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
times. times.
Note that Trunc is the upper limit on inter-packet times in the Note that Trunc is the upper limit on inter-packet times in the
Poisson distribution. A random value greater than Trunc is set equal Poisson distribution. A random value greater than Trunc is set equal
to Trunc instead. to Trunc instead.
Reciprocal_lambda average packet interval for Poisson Streams Reciprocal_lambda average packet interval for Poisson Streams
expressed in units of seconds, as a positive value of type expressed in units of seconds, as a positive value of type
decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020]) decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020])
with resolution of 0.0001 seconds (0.1 ms), and with lossless with resolution of 0.0001 seconds (0.1 ms), and with lossless
conversion to/from the 32-bit NTP timestamp as per section 6 of conversion to/from the 32-bit NTP timestamp as per section 6 of
[RFC5905]. Reciprocal_lambda = 1 packet per second. [RFC5905]. Reciprocal_lambda = 1 second.
Trunc Upper limit on Poisson distribution expressed in units of Trunc Upper limit on Poisson distribution expressed in units of
seconds, as a positive value of type decimal64 with fraction seconds, as a positive value of type decimal64 with fraction
digits = 4 (see section 9.3 of [RFC6020]) with resolution of digits = 4 (see section 9.3 of [RFC6020]) with resolution of
0.0001 seconds (0.1 ms), and with lossless conversion to/from the 0.0001 seconds (0.1 ms), and with lossless conversion to/from the
32-bit NTP timestamp as per section 6 of [RFC5905] (values above 32-bit NTP timestamp as per section 6 of [RFC5905] (values above
this limit will be clipped and set to the limit value). Trunc = this limit will be clipped and set to the limit value). Trunc =
30.0000 seconds. 30.0000 seconds.
7.3.3. Traffic Filtering (observation) Details 7.3.3. Traffic Filtering (observation) Details
skipping to change at page 44, line 9 skipping to change at page 44, line 9
o Mean o Mean
o Min o Min
o Max o Max
o StdDev o StdDev
OWLoss_Active_IP-UDP-Periodic- OWLoss_Active_IP-UDP-Periodic-
Payload142B_RFCXXXXsec8_Percent_LossRatio Payload142B_RFCXXXXsec8_Percent_LossRatio
8.1.3. URIs 8.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
8.1.4. Description 8.1.4. Description
OWDelay: This metric assesses the delay of a stream of packets OWDelay: This metric assesses the delay of a stream of packets
exchanged between two hosts (or measurement points), and reports the exchanged between two hosts (or measurement points), and reports the
<statistic> One-way delay for all successfully exchanged packets <statistic> One-way delay for all successfully exchanged packets
based on their conditional delay distribution. based on their conditional delay distribution.
skipping to change at page 54, line 48 skipping to change at page 54, line 48
where <statistic> is one of: where <statistic> is one of:
o Mean o Mean
o Min o Min
o Max o Max
RTLoss_Active_IP-ICMP-SendOnRcv_RFCXXXXsec9_Percent_LossRatio RTLoss_Active_IP-ICMP-SendOnRcv_RFCXXXXsec9_Percent_LossRatio
9.1.3. URIs 9.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
9.1.4. Description 9.1.4. Description
RTDelay: This metric assesses the delay of a stream of ICMP packets RTDelay: This metric assesses the delay of a stream of ICMP packets
exchanged between two hosts (which are the two measurement points), exchanged between two hosts (which are the two measurement points),
and the Output is the Round-trip delay for all successfully exchanged and the Output is the Round-trip delay for all successfully exchanged
packets expressed as the <statistic> of their conditional delay packets expressed as the <statistic> of their conditional delay
distribution, where <statistic> is one of: distribution, where <statistic> is one of:
skipping to change at page 64, line 18 skipping to change at page 64, line 18
o Max o Max
RTDelay_Passive_IP-TCP-HS_RFCXXXXsec10_Seconds_Singleton RTDelay_Passive_IP-TCP-HS_RFCXXXXsec10_Seconds_Singleton
Note that a mid-point observer only has the opportunity to compose a Note that a mid-point observer only has the opportunity to compose a
single RTDelay on the TCP Hand Shake. single RTDelay on the TCP Hand Shake.
RTLoss_Passive_IP-TCP_RFCXXXXsec10_Packet_Count RTLoss_Passive_IP-TCP_RFCXXXXsec10_Packet_Count
10.1.3. URIs 10.1.3. URI
URL: https://www.iana.org/ ... <name> URL: https://www.iana.org/ ... <name>
10.1.4. Description 10.1.4. Description
RTDelay: This metric assesses the round-trip delay of TCP packets RTDelay: This metric assesses the round-trip delay of TCP packets
constituting a single connection, exchanged between two hosts. We constituting a single connection, exchanged between two hosts. We
consider the measurement of round-trip delay based on a single consider the measurement of round-trip delay based on a single
Observation Point [RFC7011] somewhere in the network. The Output is Observation Point [RFC7011] somewhere in the network. The Output is
the Round-trip delay for all successfully exchanged packets expressed the Round-trip delay for all successfully exchanged packets expressed
skipping to change at page 65, line 49 skipping to change at page 65, line 49
Traffic filters reduce the packet stream at the OP to a Qualified Traffic filters reduce the packet stream at the OP to a Qualified
bidirectional flow of packets. bidirectional flow of packets.
In the definitions below, Corresponding Packets are transferred in In the definitions below, Corresponding Packets are transferred in
different directions and convey a common value in a TCP header field different directions and convey a common value in a TCP header field
that establishes correspondence (to the extent possible). Examples that establishes correspondence (to the extent possible). Examples
may be found in the TCP timestamp fields. may be found in the TCP timestamp fields.
For a real number, RTD_fwd, >> the Round-trip Delay in the Forward For a real number, RTD_fwd, >> the Round-trip Delay in the Forward
direction from OP to host B at time T' is RTD_fwd << REQUIRES that OP direction from OP to host B at time T' is RTD_fwd << it is REQUIRED
observed a Qualified Packet to host B at wire-time T', that host B that OP observed a Qualified Packet to host B at wire-time T', that
received that packet and sent a Corresponding Packet back to host A, host B received that packet and sent a Corresponding Packet back to
and OP observed the Corresponding Packet at wire-time T' + RTD_fwd. host A, and OP observed the Corresponding Packet at wire-time T' +
RTD_fwd.
For a real number, RTD_rev, >> the Round-trip Delay in the Reverse For a real number, RTD_rev, >> the Round-trip Delay in the Reverse
direction from OP to host A at time T'' is RTD_rev << REQUIRES that direction from OP to host A at time T'' is RTD_rev << it is REQUIRED
OP observed a Qualified Packet to host A at wire-time T'', that host that OP observed a Qualified Packet to host A at wire-time T'', that
A received that packet and sent a Corresponding Packet back to host host A received that packet and sent a Corresponding Packet back to
B, and that OP observed the Corresponding Packet at wire-time T'' + host B, and that OP observed the Corresponding Packet at wire-time
RTD_rev. T'' + RTD_rev.
Ideally, the packet sent from host B to host A in both definitions Ideally, the packet sent from host B to host A in both definitions
above SHOULD be the same packet (or, when measuring RTD_rev first, above SHOULD be the same packet (or, when measuring RTD_rev first,
the packet from host A to host B in both definitions should be the the packet from host A to host B in both definitions should be the
same). same).
The REQUIRED Composition Function for a singleton of Round-trip Delay The REQUIRED Composition Function for a singleton of Round-trip Delay
at time T (where T is the earliest of T' and T'' above) is: at time T (where T is the earliest of T' and T'' above) is:
RTDelay = RTD_fwd + RTD_rev RTDelay = RTD_fwd + RTD_rev
skipping to change at page 74, line 8 skipping to change at page 74, line 20
YYYY-MM-DD YYYY-MM-DD
10.6. Comments and Remarks 10.6. Comments and Remarks
None. None.
11. Security Considerations 11. Security Considerations
These registry entries represent no known implications for Internet These registry entries represent no known implications for Internet
Security. Each IETF Metric definition referenced above contains a Security. Each RFC referenced above contains a Security
Security Considerations section. Further, the LMAP Framework Considerations section. Further, the LMAP Framework [RFC7594]
[RFC7594] provides both security and privacy considerations for provides both security and privacy considerations for measurements.
measurements.
There are potential privacy considerations for observed traffic, There are potential privacy considerations for observed traffic,
particularly for passive metrics in section 10. An attacker that particularly for passive metrics in section 10. An attacker that
knows that its TCP connection is being measured can modify its knows that its TCP connection is being measured can modify its
behavior to skew the measurement results. behavior to skew the measurement results.
12. IANA Considerations 12. IANA Considerations
IANA is requested to populate The Performance Metrics Registry IANA is requested to populate The Performance Metrics Registry
defined in [I-D.ietf-ippm-metric-registry] with the values defined in defined in [I-D.ietf-ippm-metric-registry] with the values defined in
skipping to change at page 76, line 5 skipping to change at page 76, line 15
[RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,
S., and J. Perser, "Packet Reordering Metrics", RFC 4737, S., and J. Perser, "Packet Reordering Metrics", RFC 4737,
DOI 10.17487/RFC4737, November 2006, DOI 10.17487/RFC4737, November 2006,
<https://www.rfc-editor.org/info/rfc4737>. <https://www.rfc-editor.org/info/rfc4737>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008, RFC 5357, DOI 10.17487/RFC5357, October 2008,
<https://www.rfc-editor.org/info/rfc5357>. <https://www.rfc-editor.org/info/rfc5357>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
March 2009, <https://www.rfc-editor.org/info/rfc5481>.
[RFC5560] Uijterwaal, H., "A One-Way Packet Duplication Metric", [RFC5560] Uijterwaal, H., "A One-Way Packet Duplication Metric",
RFC 5560, DOI 10.17487/RFC5560, May 2009, RFC 5560, DOI 10.17487/RFC5560, May 2009,
<https://www.rfc-editor.org/info/rfc5560>. <https://www.rfc-editor.org/info/rfc5560>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<https://www.rfc-editor.org/info/rfc5905>. <https://www.rfc-editor.org/info/rfc5905>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
skipping to change at page 77, line 27 skipping to change at page 77, line 42
in Computer Science, vol 8406. Springer, Berlin, in Computer Science, vol 8406. Springer, Berlin,
Heidelberg https://link.springer.com/ Heidelberg https://link.springer.com/
chapter/10.1007/978-3-642-54999-1_2", March 2014. chapter/10.1007/978-3-642-54999-1_2", March 2014.
14.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>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
March 2009, <https://www.rfc-editor.org/info/rfc5481>.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390, Performance Metric Development", BCP 170, RFC 6390,
DOI 10.17487/RFC6390, October 2011, DOI 10.17487/RFC6390, October 2011,
<https://www.rfc-editor.org/info/rfc6390>. <https://www.rfc-editor.org/info/rfc6390>.
[RFC6703] Morton, A., Ramachandran, G., and G. Maguluri, "Reporting [RFC6703] Morton, A., Ramachandran, G., and G. Maguluri, "Reporting
IP Network Performance Metrics: Different Points of View", IP Network Performance Metrics: Different Points of View",
RFC 6703, DOI 10.17487/RFC6703, August 2012, RFC 6703, DOI 10.17487/RFC6703, August 2012,
<https://www.rfc-editor.org/info/rfc6703>. <https://www.rfc-editor.org/info/rfc6703>.
 End of changes. 33 change blocks. 
53 lines changed or deleted 53 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/