idnits 2.17.1 draft-morton-ippm-initial-registry-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 592 has weird spacing: '... Src the IP...' == Line 596 has weird spacing: '... Dst the IP...' == Line 613 has weird spacing: '..._lambda avera...' == Line 635 has weird spacing: '... Src launch...' == Line 638 has weird spacing: '... Dst waits ...' -- The document date (February 21, 2016) is 2986 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2680' is defined on line 2699, but no explicit reference was found in the text == Unused Reference: 'RFC4737' is defined on line 2722, but no explicit reference was found in the text == Unused Reference: 'Brow00' is defined on line 2756, but no explicit reference was found in the text == Unused Reference: 'RFC4148' is defined on line 2768, but no explicit reference was found in the text == Unused Reference: 'RFC5472' is defined on line 2776, but no explicit reference was found in the text == Unused Reference: 'RFC5477' is defined on line 2781, but no explicit reference was found in the text == Unused Reference: 'RFC6248' is defined on line 2790, but no explicit reference was found in the text == Unused Reference: 'RFC7594' is defined on line 2821, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2330 ** Obsolete normative reference: RFC 2679 (Obsoleted by RFC 7679) ** Obsolete normative reference: RFC 2680 (Obsoleted by RFC 7680) -- Obsolete informational reference (is this intentional?): RFC 4148 (Obsoleted by RFC 6248) -- Obsolete informational reference (is this intentional?): RFC 4566 (Obsoleted by RFC 8866) Summary: 3 errors (**), 0 flaws (~~), 14 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Morton 3 Internet-Draft AT&T Labs 4 Intended status: Standards Track M. Bagnulo 5 Expires: August 24, 2016 UC3M 6 P. Eardley 7 BT 8 K. D'Souza 9 AT&T Labs 10 February 21, 2016 12 Initial Performance Metric Registry Entries 13 draft-morton-ippm-initial-registry-04 15 Abstract 17 This memo defines the Initial Entries for the Performance Metrics 18 Registry. 20 Version 04 * All section 4 parameters reference YANG types for 21 alternate data formats. * Discussion has concluded that usecase(s) 22 for machine parse-able registry columns are not needed. 24 Still need: * suggestion of standard naming format for parameters. * 25 revisions that follow section 4 changes in other proposed metrics. 27 Requirements Language 29 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 30 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 31 document are to be interpreted as described in RFC 2119 [RFC2119]. 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at http://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on August 24, 2016. 50 Copyright Notice 52 Copyright (c) 2016 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 7 68 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 69 3. Registry Categories and Columns . . . . . . . . . . . . . . . 8 70 4. UDP Round-trip Latency Registry Entry . . . . . . . . . . . . 8 71 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9 72 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9 73 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9 74 4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 9 75 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9 76 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9 77 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 9 78 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10 79 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11 80 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11 81 4.3.2. Packet Generation Stream . . . . . . . . . . . . . . 12 82 4.3.3. Traffic Filtering (observation) Details . . . . . . . 13 83 4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 13 84 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 13 85 4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 14 86 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 14 87 4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 14 88 4.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 15 89 4.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 15 90 4.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 15 91 4.5. Administrative items . . . . . . . . . . . . . . . . . . 15 92 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 15 93 4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 16 94 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16 95 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 16 96 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 16 97 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 16 98 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16 99 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 16 100 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 16 101 5.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 17 102 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 17 103 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 17 104 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 17 105 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 17 106 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 18 107 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 18 108 5.3.2. Packet Generation Stream . . . . . . . . . . . . . . 18 109 5.3.3. Traffic Filtering (observation) Details . . . . . . . 18 110 5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 19 111 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 19 112 5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 19 113 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 19 114 5.4.1. Type/Value (two diff terms used) . . . . . . . . . . 19 115 5.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 20 116 5.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 21 117 5.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 21 118 5.5. Administrative items . . . . . . . . . . . . . . . . . . 21 119 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 21 120 5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 21 121 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 21 122 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 21 123 5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 22 124 6. DNS Response Latency Registry Entry . . . . . . . . . . . . . 22 125 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 22 126 6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 22 127 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 22 128 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 22 129 6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 22 130 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 22 131 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 23 132 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 23 133 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 25 134 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 25 135 6.3.2. Packet Generation Stream . . . . . . . . . . . . . . 26 136 6.3.3. Traffic Filtering (observation) Details . . . . . . . 26 137 6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 26 138 6.3.5. Run-time Parameters and Data Format . . . . . . . . . 26 139 6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 27 140 6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 27 141 6.4.1. Type/Value (two diff terms used) . . . . . . . . . . 28 142 6.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 28 143 6.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 29 144 6.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 29 145 6.5. Administrative items . . . . . . . . . . . . . . . . . . 29 146 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 29 147 6.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 29 148 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 29 149 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 29 150 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 29 151 7. UDP Poisson One-way Delay Registry Entries . . . . . . . . . 30 152 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 30 153 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 30 154 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 30 155 7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 30 156 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 31 157 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 31 158 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 31 159 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 31 160 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 32 161 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 32 162 7.3.2. Packet Generation Stream . . . . . . . . . . . . . . 32 163 7.3.3. Traffic Filtering (observation) Details . . . . . . . 33 164 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 33 165 7.3.5. Run-time Parameters and Data Format . . . . . . . . . 33 166 7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 34 167 7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 34 168 7.4.1. Type/Value (two diff terms used) . . . . . . . . . . 34 169 7.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 34 170 7.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 36 171 7.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 36 172 7.5. Administrative items . . . . . . . . . . . . . . . . . . 37 173 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 37 174 7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 37 175 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 37 176 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 37 177 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 37 178 8. UDP Periodic One-way Delay Registry Entries . . . . . . . . . 37 179 8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 37 180 8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 37 181 8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 38 182 8.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 38 183 8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 38 184 8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 38 185 8.2.1. Reference Definition . . . . . . . . . . . . . . . . 38 186 8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 39 187 8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 40 188 8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 40 189 8.3.2. Packet Generation Stream . . . . . . . . . . . . . . 40 190 8.3.3. Traffic Filtering (observation) Details . . . . . . . 41 191 8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 41 192 8.3.5. Run-time Parameters and Data Format . . . . . . . . . 41 193 8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 42 195 8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 42 196 8.4.1. Type/Value (two diff terms used) . . . . . . . . . . 42 197 8.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 42 198 8.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 44 199 8.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 44 200 8.5. Administrative items . . . . . . . . . . . . . . . . . . 44 201 8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 44 202 8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 44 203 8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 44 204 8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 45 205 8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 45 206 9. partly BLANK Registry Entry . . . . . . . . . . . . . . . . . 45 207 9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 45 208 9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 45 209 9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 45 210 9.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 45 211 9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 45 212 9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 45 213 9.2.1. Reference Definition . . . . . . . . . . . . . . . . 45 214 9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 46 215 9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 47 216 9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 47 217 9.3.2. Packet Generation Stream . . . . . . . . . . . . . . 47 218 9.3.3. Traffic Filtering (observation) Details . . . . . . . 47 219 9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 47 220 9.3.5. Run-time Parameters and Data Format . . . . . . . . . 47 221 9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 48 222 9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 48 223 9.4.1. Type/Value (two diff terms used) . . . . . . . . . . 48 224 9.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 48 225 9.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 48 226 9.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 48 227 9.5. Administrative items . . . . . . . . . . . . . . . . . . 48 228 9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 48 229 9.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 48 230 9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 49 231 9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 49 232 9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 49 233 10. BLANK Registry Entry . . . . . . . . . . . . . . . . . . . . 49 234 10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 49 235 10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 49 236 10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 49 237 10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 49 238 10.1.4. Description . . . . . . . . . . . . . . . . . . . . 49 239 10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 49 240 10.2.1. Reference Definition . . . . . . . . . . . . . . . . 50 241 10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 50 242 10.3. Method of Measurement . . . . . . . . . . . . . . . . . 50 243 10.3.1. Reference Method . . . . . . . . . . . . . . . . . . 50 244 10.3.2. Packet Generation Stream . . . . . . . . . . . . . . 50 245 10.3.3. Traffic Filtering (observation) Details . . . . . . 50 246 10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 50 247 10.3.5. Run-time Parameters and Data Format . . . . . . . . 50 248 10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 50 249 10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 51 250 10.4.1. Type/Value (two diff terms used) . . . . . . . . . . 51 251 10.4.2. Data Format . . . . . . . . . . . . . . . . . . . . 51 252 10.4.3. Reference . . . . . . . . . . . . . . . . . . . . . 51 253 10.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 51 254 10.5. Administrative items . . . . . . . . . . . . . . . . . . 51 255 10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 51 256 10.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . 51 257 10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 51 258 10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 51 259 10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 51 260 11. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 52 261 11.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 52 262 11.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 52 263 11.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 52 264 11.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 52 265 11.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 52 266 11.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 52 267 11.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 52 268 11.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 52 269 11.1.8. Description . . . . . . . . . . . . . . . . . . . . 52 270 11.1.9. Reference Specification(s) . . . . . . . . . . . . . 53 271 11.2. Metric Definition . . . . . . . . . . . . . . . . . . . 53 272 11.2.1. Reference Definition . . . . . . . . . . . . . . . . 53 273 11.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 53 274 11.3. Method of Measurement . . . . . . . . . . . . . . . . . 54 275 11.3.1. Reference Method . . . . . . . . . . . . . . . . . . 54 276 11.3.2. Stream Type and Stream Parameters . . . . . . . . . 54 277 11.3.3. Output Type and Data Format . . . . . . . . . . . . 54 278 11.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 54 279 11.3.5. Run-time Parameters and Data Format . . . . . . . . 55 280 11.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 56 281 12. Revision History . . . . . . . . . . . . . . . . . . . . . . 56 282 13. Security Considerations . . . . . . . . . . . . . . . . . . . 57 283 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 284 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 285 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 286 16.1. Normative References . . . . . . . . . . . . . . . . . . 58 287 16.2. Informative References . . . . . . . . . . . . . . . . . 59 288 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61 290 1. Introduction 292 Note: Efforts to synchronize structure and terminology with 293 [I-D.ietf-ippm-metric-registry] will likely be incomplete until both 294 drafts are stable. 296 This memo proposes an initial set of entries for the Performance 297 Metric Registry. It uses terms and definitions from the IPPM 298 literature, primarily [RFC2330]. Proponents of Passive Performance 299 Metrics are encouraged to develop a similar document. 301 Although there are several standard templates for organizing 302 specifications of performance metrics (see [RFC2679] for an example 303 of the traditional IPPM template, based to large extent on the 304 Benchmarking Methodology Working Group's traditional template in 305 [RFC1242], and see [RFC6390] for a similar template), none of these 306 templates were intended to become the basis for the columns of an 307 IETF-wide registry of metrics. While examinating aspects of metric 308 specifications which need to be registered, it became clear that none 309 of the existing metric templates fully satisfies the particular needs 310 of a registry. 312 Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format 313 for a Performance Metric Registry. Section 5 of 314 [I-D.ietf-ippm-metric-registry] also gives guidelines for those 315 requesting registration of a Metric, that is the creation of entry(s) 316 in the Performance Metric Registry: "In essence, there needs to be 317 evidence that a candidate Registered Performance Metric has 318 significant industry interest, or has seen deployment, and there is 319 agreement that the candidate Registered Performance Metric serves its 320 intended purpose." The process in [I-D.ietf-ippm-metric-registry] 321 also requires that new entries are administered by IANA through 322 Expert Review, which will ensure that the metrics are tightly 323 defined. 325 2. Scope 327 This document defines the initial set of Performance Metrics Registry 328 entries, for which IETF approval (following development in the IP 329 Performance Metrics (IPPM) Working Group) will satisfy the 330 requirement for Expert Review. Note that all are Active Performance 331 Metrics, which are based on RFCs prepared in the IPPM working group 332 of the IETF, according to their framework [RFC2330] and its updates. 334 3. Registry Categories and Columns 336 This section provides the categories and columns of the registry, for 337 easy reference. An entry (row) therefore gives a complete 338 description of a Registered Metric. 340 Registry Categories and Columns, shown as 341 Category 342 ------------------ 343 Column | Column | 345 Summary 346 -------------------------------- 347 ID | Name | URIs | Description | 349 Metric Definition 350 ----------------------------------------- 351 Reference Definition | Fixed Parameters | 353 Method of Measurement 354 --------------------------------------------------------------- 355 Reference | Packet | Traffic | Sampling | Run-time | Role | 356 Method | Generation | Filter | dist. | Param | | 357 | Stream | 359 Output 360 ---------------------------- 361 Type | Reference | Units | 362 | Definition | | 364 Administrative information 365 ---------------------------------- 366 Status |Request | Rev | Rev.Date | 368 Comments and Remarks 369 -------------------- 371 4. UDP Round-trip Latency Registry Entry 373 This section gives an initial registry entry for the UDP Round-trip 374 Latency. 376 Note: Each Registry entry only produces a "raw" output or a 377 statistical summary. To describe both "raw" and one or more 378 statistics efficiently, the Identifier, Name, and Output Categories 379 can be split and this section can become two or more closely-related 380 metrics. See Section 7 for an example specifying multiple Registry 381 entries with many common columns. 383 4.1. Summary 385 This category includes multiple indexes to the registry entry: the 386 element ID and metric name. 388 4.1.1. ID (Identifier) 390 392 4.1.2. Name 394 396 Act_IP_UDP_Round-trip_Delay_Poisson_95th-percentile 398 4.1.3. URIs 400 URN: Prefix urn:ietf:params:performance:metric... 402 URL: http:/// 404 4.1.4. Description 406 This metric assesses the delay of a stream of packets exchanged 407 between two hosts (which are the two measurement points), and the 408 Output is the Round-trip delay for all successfully exchanged packets 409 expressed as the 95th percentile of their conditional delay 410 distribution. 412 4.2. Metric Definition 414 This category includes columns to prompt the entry of all necessary 415 details related to the metric definition, including the RFC reference 416 and values of input factors, called fixed parameters. 418 4.2.1. Reference Definition 420 422 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 423 Metric for IPPM", RFC 2681, September 1999. 425 [RFC2681] 427 429 Section 2.4 of [RFC2681] provides the reference definition of the 430 singleton (single value) Round-trip delay metric. Section 3.4 of 431 [RFC2681] provides the reference definition expanded to cover a 432 multi-value sample. Note that terms such as singleton and sample are 433 defined in Section 11 of [RFC2330]. 435 Note that although the definition of "Round-trip-Delay between Src 436 and Dst" is directionally ambiguous in the text, this metric tightens 437 the definition further to recognize that the host in the "Src" role 438 will send the first packet to "Dst", and ultimately receive the 439 corresponding return packet from "Dst" (when neither are lost). 441 Finally, note that the variable "dT" is used in [RFC2681] to refer to 442 the value of Round-trip delay in metric definitions and methods. The 443 variable "dT" has been re-used in other IPPM literature to refer to 444 different quantities, and cannot be used as a global variable name. 446 4.2.2. Fixed Parameters 448 452 Type-P: 454 o IPv4 header values: 456 * DSCP: set to 0 458 * TTL: set to 255 460 * Protocol: Set to 17 (UDP) 462 o IPv6 header values: 464 * DSCP: set to 0 466 * Hop Count: set to 255 468 * Protocol: Set to 17 (UDP) 470 o UDP header values: 472 * Checksum: the checksum MUST be calculated 474 o UDP Payload 476 * total of 9 bytes 478 Other measurement parameters: 480 o Tmax: a loss threshold waiting time 482 * 3.0, expressed in units of seconds, as a positive value of type 483 decimal64 with fraction digits = 5 (see section 9.3 of 484 [RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with 485 lossless conversion to/from the 32-bit NTP timestamp as per 486 section 6 of [RFC5905]. 488 4.3. Method of Measurement 490 This category includes columns for references to relevant sections of 491 the RFC(s) and any supplemental information needed to ensure an 492 unambiguous methods for implementations. 494 4.3.1. Reference Method 496 499 The methodology for this metric is defined as Type-P-Round-trip- 500 Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section 501 3.6 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under 502 Fixed Parameters. 504 The reference method distinguishes between long-delayed packets and 505 lost packets by implementing a maximum waiting time for packet 506 arrival. Tmax is the waiting time used as the threshold to declare a 507 packet lost. Lost packets SHALL be designated as having undefined 508 delay. 510 The calculations on the delay (RTT) SHALL be performed on the 511 conditional distribution, conditioned on successful packet arrival 512 within Tmax. Also, when all packet delays are stored, the process 513 which calculates the RTT value MAY enforce the Tmax threshold on 514 stored values before calculations. See section 4.1 of [RFC3393] for 515 details on the conditional distribution to exclude undefined values 516 of delay, and Section 5 of [RFC6703] for background on this analysis 517 choice. 519 The reference method requires some way to distinguish between 520 different packets in a stream to establish correspondence between 521 sending times and receiving times for each successfully-arriving 522 packet. Sequence numbers or other send-order identification MUST be 523 retained at the Src or included with each packet to dis-ambiguate 524 packet reordering if it occurs. 526 If a standard measurement protocol is employed, then the measurement 527 process will determine the sequence numbers or timestamps applied to 528 test packets after the Fixed and Runtime parameters are passed to 529 that process. The chosen measurement protocol will dictate the 530 format of sequence numbers and time-stamps, if they are conveyed in 531 the packet payload. 533 Refer to Section 4.4 of [RFC6673] for expanded discussion of the 534 instruction to "send a Type-P packet back to the Src as quickly as 535 possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of 536 [RFC6673] presents additional requirements which MUST be included in 537 the method of measurement for this metric. 539 4.3.2. Packet Generation Stream 541 This section gives the details of the packet traffic which is the 542 basis for measurement. In IPPM metrics, this is called the Stream, 543 and can easily be described by providing the list of stream 544 parameters. 546
549 Section 11.1.3 of [RFC2330] provides three methods to generate 550 Poisson sampling intervals. the reciprocal of lambda is the average 551 packet spacing, thus the Run-time Parameter is Reciprocal_lambda = 1/ 552 lambda, in seconds. 554 >>> Check with Sam, most likely it is this... 556 Method 3 SHALL be used, where given a start time (Run-time 557 Parameter), the subsequent send times are all computed prior to 558 measurement by computing the pseudo-random distribution of inter- 559 packet send times, (truncating the distribution as specified in the 560 Run-time Parameter, Trunc), and the Src sends each packet at the 561 computed times. 563 Note that Trunc is the upper limit on inter-packet times in the 564 Poisson distribution. A random value greater than Trunc is set equal 565 to Trunc instead. 567 4.3.3. Traffic Filtering (observation) Details 569 The measured results based on a filtered version of the packets 570 observed, and this section provides the filter details (when 571 present). 573
. 575 NA 577 4.3.4. Sampling Distribution 579 582 NA 584 4.3.5. Run-time Parameters and Data Format 586 Run-time Parameters are input factors that must be determined, 587 configured into the measurement system, and reported with the results 588 for the context to be complete. 590 592 Src the IP address of the host in the Src Role (format ipv4-address- 593 no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, 594 see Section 4 of [RFC6991]) 596 Dst the IP address of the host in the Dst Role (format ipv4-address- 597 no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, 598 see section 4 of [RFC6991]) 600 T0 a time, the start of a measurement interval, (format "date-and- 601 time" as specified in Section 5.6 of [RFC3339], see also Section 3 602 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of 603 [RFC2330]. When T0 is "all-zeros", a start time is unspecified 604 and Tf is to be interpreted as the Duration of the measurement 605 interval. The start time is controlled through other means. 607 Tf a time, the end of a measurement interval, (format "date-and-time" 608 as specified in Section 5.6 of [RFC3339], see also Section 3 of 609 [RFC6991]). The UTC Time Zone is required by Section 6.1 of 610 [RFC2330]. When T0 is "all-zeros", a end time date is ignored and 611 Tf is interpreted as the Duration of the measurement interval. 613 Reciprocal_lambda average packet interval for Poisson Streams 614 expressed in units of seconds, as a positive value of type 615 decimal64 with fraction digits = 5 (see section 9.3 of [RFC6020]) 616 with resolution of 0.0001 seconds (0.1 ms), and with lossless 617 conversion to/from the 32-bit NTP timestamp as per section 6 of 618 [RFC5905]. 620 Trunc Upper limit on Poisson distribution expressed in units of 621 seconds, as a positive value of type decimal64 with fraction 622 digits = 5 (see section 9.3 of [RFC6020]) with resolution of 623 0.0001 seconds (0.1 ms), and with lossless conversion to/from the 624 32-bit NTP timestamp as per section 6 of [RFC5905] (values above 625 this limit will be clipped and set to the limit value). (if fixed, 626 Trunc = 30.0000 seconds.) 628 >>> should Poisson run-time params be fixed instead? probably yes if 629 modeling a specific version of MBA tests. 631 4.3.6. Roles 633 635 Src launches each packet and waits for return transmissions from 636 Dst. 638 Dst waits for each packet from Src and sends a return packet to Src. 640 4.4. Output 642 This category specifies all details of the Output of measurements 643 using the metric. 645 4.4.1. Type 647 649 Percentile -- for the conditional distribution of all packets with a 650 valid value of Round-trip delay (undefined delays are excluded), a 651 single value corresponding to the 95th percentile, as follows: 653 See section 4.1 of [RFC3393] for details on the conditional 654 distribution to exclude undefined values of delay, and Section 5 of 655 [RFC6703] for background on this analysis choice. 657 The percentile = 95, meaning that the reported delay, "Percentile95", 658 is the smallest value of Round-trip delay for which the Empirical 659 Distribution Function (EDF), F(Percentile95) >= 95% of the singleton 660 Round-trip delay values in the conditional distribution. See section 661 11.3 of [RFC2330] for the definition of the percentile statistic 662 using the EDF. 664 4.4.2. Data Format 666 668 For all outputs --- 670 T0 the start of a measurement interval, (format "date-and-time" as 671 specified in Section 5.6 of [RFC3339], see also Section 3 of 672 [RFC6991]). The UTC Time Zone is required by Section 6.1 of 673 [RFC2330]. 675 Tf the start of a measurement interval, (format "date-and-time" as 676 specified in Section 5.6 of [RFC3339], see also Section 3 of 677 [RFC6991]). The UTC Time Zone is required by Section 6.1 of 678 [RFC2330]. 680 Raw -- REMOVED IN VERSION 01 682 For Act_IP_UDP_Round-trip_Delay_Poisson_95th-percentile: 684 Percentile95 The time value of the result is expressed in units of 685 seconds, as a positive value of type decimal64 with fraction 686 digits = 9 (see section 9.3 of [RFC6020]) with resolution of 687 0.000000001 seconds (1.0 ns), and with lossless conversion to/from 688 the 64-bit NTP timestamp as per section 6 of RFC [RFC5905] 690 4.4.3. Reference 692 694 See the Data Format column for references. 696 4.4.4. Metric Units 698 . 701 The 95th Percentile of Round-trip Delay is expressed in seconds. 703 4.5. Administrative items 705 4.5.1. Status 707 709 4.5.2. Requestor (keep?) 711 name or RFC, etc. 713 4.5.3. Revision 715 1.0 717 4.5.4. Revision Date 719 YYYY-MM-DD 721 4.6. Comments and Remarks 723 Additional (Informational) details for this entry 725 5. Packet Delay Variation Registry Entry 727 This section gives an initial registry entry for a Packet Delay 728 Variation metric. 730 Note: If each Registry entry should only produce a "raw" output or a 731 statistical summary, then the "Output" Category can be split and this 732 section can become two closely-related metrics. 734 5.1. Summary 736 This category includes multiple indexes to the registry entries, the 737 element ID and metric name. 739 741 5.1.1. ID (Identifier) 743 745 5.1.2. Name 747 749 Act_IP-UDP-One-way-pdv-95th-percentile-Poisson 751 URL: ?? 753 5.1.3. URI 755 URI: Prefix urn:ietf:params:performance:metric 757 5.1.4. Description 759 An assessment of packet delay variation with respect to the minimum 760 delay observed on the stream. 762 5.2. Metric Definition 764 This category includes columns to prompt the entry of all necessary 765 details related to the metric definition, including the RFC reference 766 and values of input factors, called fixed parameters. 768 5.2.1. Reference Definition 770 772 Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP 773 Performance Metrics", RFC 2330, May 1998. [RFC2330] 775 Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric 776 for IP Performance Metrics (IPPM)", RFC 3393, November 2002. 777 [RFC3393] 779 Morton, A. and B. Claise, "Packet Delay Variation Applicability 780 Statement", RFC 5481, March 2009. [RFC5481] 782 Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time 783 Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, 784 June 2010.[RFC5905] 786 788 See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences 789 measured are referred to by the variable name "ddT". 791 5.2.2. Fixed Parameters 793 797 o F, a selection function defining unambiguously the packets from 798 the stream selected for the metric. See section 4.2 of [RFC5481] 799 for the PDV form. 801 o L, a packet length in bits. L = 200 bits. 803 o Tmax, a maximum waiting time for packets to arrive at Dst, set 804 sufficiently long to disambiguate packets with long delays from 805 packets that are discarded (lost). Tmax = 3 seconds. 807 o Type-P, as defined in [RFC2330], which includes any field that may 808 affect a packet's treatment as it traverses the network. The 809 packets are IP/UDP, with DSCP = 0 (BE). 811 5.3. Method of Measurement 813 This category includes columns for references to relevant sections of 814 the RFC(s) and any supplemental information needed to ensure an 815 unambiguous methods for implementations. 817 5.3.1. Reference Method 819 822 See section 2.6 and 3.6 of [RFC3393] for singleton elements. 824 5.3.2. Packet Generation Stream 826 828 Poisson distributed as described in [RFC2330], with the following 829 Parameters. 831 o lambda, a rate in reciprocal seconds (for Poisson Streams). 832 lambda = 1 packet per second 834 o Upper limit on Poisson distribution (values above this limit will 835 be clipped and set to the limit value). Upper limit = 30 seconds. 837 5.3.3. Traffic Filtering (observation) Details 839 . 843 NA 845 5.3.4. Sampling Distribution 847 850 NA 852 5.3.5. Run-time Parameters and Data Format 854 . 856 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 857 value for IPv6) 859 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 860 value for IPv6) 862 o T, a time (start of measurement interval, 128-bit NTP Date Format, 863 see section 6 of [RFC5905]). When T0 is "all-zeros", a start time 864 is unspecified and Tf is to be interpreted as the Duration of the 865 measurement interval. 867 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 868 see section 6 of [RFC5905]), interpreted as the Duration of the 869 measurement interval. 871 5.3.6. Roles 873 875 Src - the host that sends the stream of packets. 877 Dst - the host that receives the stream of packets. 879 5.4. Output 881 This category specifies all details of the Output of measurements 882 using the metric. 884 5.4.1. Type/Value (two diff terms used) 886 888 Raw -- for each packet sent, pairs of values. 890 Percentile -- for the conditional distribution of all packets with a 891 valid value of one-way delay (undefined delays are excluded), a 892 single value corresponding to the 95th percentile of the singletons, 893 ddT. 895 5.4.2. Data Format 897 899 For all Output types 901 o T, a time (start of measurement interval, 128-bit NTP Date Format, 902 see section 6 of [RFC5905]) 904 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 905 see section 6 of [RFC5905]) 907 Raw - 909 o T1, the wire time of the first packet in a pair, measured at 910 MP(Src) as it leaves for Dst (64-bit NTP Timestamp Format, see 911 section 6 of [RFC5905]). 913 o T2, the wire time of the second packet in a pair, measured at 914 MP(Src) as it leaves for Dst (64-bit NTP Timestamp Format, see 915 section 6 of [RFC5905]). 917 o I(i),I(i+1), i >=0, pairs of times which mark the beginning and 918 ending of the intervals in which the packet stream from which the 919 measurement is taken occurs. Here, I(0) = T0 and assuming that n 920 is the largest index, I(n) = Tf (pairs of 64-bit NTP Timestamp 921 Format, see section 6 of [RFC5905]). 923 o When the one-way delay of a packet in the calculation pair for ddT 924 is undefined, then ddT is undefined for that pair. 926 Percentile -- for the conditional distribution of all packets with a 927 valid value of one-way delay (undefined delays are excluded), a 928 single value as follows: 930 See section 4.1 of [RFC3393] for details on the conditional 931 distribution to exclude undefined values of delay, and Section 5 of 932 [RFC6703] for background on this analysis choice. 934 See section 4.3 of [RFC3393] for details on the percentile statistic 935 (where pdv should be substituted for "ipdv"). 937 The percentile = 95. 939 Data format is a 32-bit signed floating point value, *similar to* the 940 32-bit short NTP Time format in Section 6 of [RFC5905] and is as 941 follows: the first 16 bits represent the *signed* integer number of 942 seconds; the next 16 bits represent the fractional part of a second. 944 5.4.3. Reference 946 948 see Data Format column. 950 5.4.4. Metric Units 952 . 955 See section 3.3 of [RFC3393] for singleton elements, ddT. The units 956 are seconds, and the same units are used for 95th percentile. 958 [RFC2330] recommends that when a time is given, it will be expressed 959 in UTC. 961 The timestamp format (for T, Tf, etc.) is the same as in [RFC5905] 962 (64 bits) and is as follows: the first 32 bits represent the unsigned 963 integer number of seconds elapsed since 0h on 1 January 1900; the 964 next 32 bits represent the fractional part of a second that has 965 elapsed since then. 967 5.5. Administrative items 969 5.5.1. Status 971 973 5.5.2. Requestor (keep?) 975 977 5.5.3. Revision 979 1.0 981 5.5.4. Revision Date 983 YYYY-MM-DD 985 5.6. Comments and Remarks 987 989 Lost packets represent a challenge for delay variation metrics. See 990 section 4.1 of [RFC3393] and the delay variation applicability 991 statement[RFC5481] for extensive analysis and comparison of PDV and 992 an alternate metric, IPDV. 994 6. DNS Response Latency Registry Entry 996 This section gives an initial registry entry for DNS Response 997 Latency. RFC 2681 [RFC2681] defines a Round-trip delay metric. We 998 build on that metric by specifying several of the input parameters to 999 precisely define a metric for measuring DNS latency. 1001 6.1. Summary 1003 This category includes multiple indexes to the registry entries, the 1004 element ID and metric name. 1006 1008 6.1.1. ID (Identifier) 1010 1012 6.1.2. Name 1014 1016 URL: ?? 1018 6.1.3. URI 1020 URI: Prefix urn:ietf:params:performance:metric 1022 6.1.4. Description 1024 This metric assesses the response time, the interval from the query 1025 transmission to the response. 1027 6.2. Metric Definition 1029 This category includes columns to prompt the entry of all necessary 1030 details related to the metric definition, including the RFC reference 1031 and values of input factors, called fixed parameters. 1033 6.2.1. Reference Definition 1035 1037 Mockapetris, P., "Domain names - implementation and specification", 1038 STD 13, RFC 1035, November 1987. (and updates) 1040 [RFC1035] 1042 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 1043 Metric for IPPM", RFC 2681, September 1999. 1045 [RFC2681] 1047 1049 Section 2.4 of [RFC2681] provides the reference definition of the 1050 singleton (single value) Round-trip delay metric. Section 3.4 of 1051 [RFC2681] provides the reference definition expanded to cover a 1052 multi-value sample. Note that terms such as singleton and sample are 1053 defined in Section 11 of [RFC2330]. 1055 For DNS Response Latency, the entities in [RFC1035] must be mapped to 1056 [RFC2681]. The Local Host with its User Program and Resolver take 1057 the role of "Src", and the Foreign Name Server takes the role of 1058 "Dst". 1060 Note that although the definition of "Round-trip-Delay between Src 1061 and Dst at T" is directionally ambiguous in the text, this metric 1062 tightens the definition further to recognize that the host in the 1063 "Src" role will send the first packet to "Dst", and ultimately 1064 receive the corresponding return packet from "Dst" (when neither are 1065 lost). 1067 6.2.2. Fixed Parameters 1069 1073 Type-P: 1075 o IPv4 header values: 1077 * DSCP: set to 0 1079 * TTL set to 255 1080 * Protocol: Set to 17 (UDP) 1082 o UDP header values: 1084 * Source port: 53 1086 * Destination port: 53 1088 * Checksum: the checksum must be calculated 1090 o Payload: The payload contains a DNS message as defined in RFC 1035 1091 [RFC1035] with the following values: 1093 * The DNS header section contains: 1095 + QR: set to 0 (Query) 1097 + OPCODE: set to 0 (standard query) 1099 + AA: not set 1101 + TC: not set 1103 + RD: set to one (recursion desired) 1105 + RA: not set 1107 + RCODE: not set 1109 + QDCOUNT: set to one (only one entry) 1111 + ANCOUNT: not set 1113 + NSCOUNT: not set 1115 + ARCOUNT: not set 1117 * The Question section contains: 1119 + QNAME: the FQDN provided as input for the test 1121 + QTYPE: the query type provided as input for the test 1123 + QCLASS: set to IN 1125 * The other sections do not contain any Resource Records. 1127 Observation: reply packets will contain a DNS response and may 1128 contain RRs. 1130 Timeout: Tmax = 5 seconds (to help disambiguate queries) 1132 6.3. Method of Measurement 1134 This category includes columns for references to relevant sections of 1135 the RFC(s) and any supplemental information needed to ensure an 1136 unambiguous methods for implementations. 1138 6.3.1. Reference Method 1140 1143 The methodology for this metric is defined as Type-P-Round-trip- 1144 Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section 1145 3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under 1146 Fixed Parameters. 1148 The method requires sequence numbers or other send-order information 1149 to be retained at the Src or included with each packet to dis- 1150 ambiguate packet reordering if it occurs. Sequence number is part of 1151 the payload described under Fixed Parameters. 1153 DNS Messages bearing Queries provide for random ID Numbers, so more 1154 than one query may be launched while a previous request is 1155 outstanding when the ID Number is used. 1157 IF a DNS response does not arrive within Tmax, the result is 1158 undefined. The Message ID SHALL be used to disambiguate the 1159 successive queries. 1161 >>> This would require support of ID generation and population in the 1162 Message. An alternative would be to use a random Source port on the 1163 Query Message, but we would choose ONE before proceding. 1165 Refer to Section 4.4 of [RFC6673] for expanded discussion of the 1166 instruction to "send a Type-P packet back to the Src as quickly as 1167 possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of 1168 [RFC6673] presents additional requirements which shall be included in 1169 the method of measurement for this metric. 1171 6.3.2. Packet Generation Stream 1173 This section gives the details of the packet traffic which is the 1174 basis for measurement. In IPPM metrics, this is called the Stream, 1175 and can easily be dscribed by providing the list of stream 1176 parameters. 1178 1180 Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to 1181 generate Poisson sampling intervals. the reciprocal of lambda is the 1182 average packet rate, thus the Run-time Parameter is 1/lambda. 1184 >>> Check with Sam, most likely it is this... 1186 Method 3 is used, where given a start time (Run-time Parameter), the 1187 subsequent send times are all computed prior to measurement by 1188 computing the pseudo-random distribution of inter-packet send times, 1189 (truncating the distribution as specified in the Run-time 1190 Parameters), and the Src sends each packet at the computed times. 1192 6.3.3. Traffic Filtering (observation) Details 1194 The measured results based on a filtered version of the packets 1195 observed, and this section provides the filter details (when 1196 present). 1198
. 1200 NA 1202 6.3.4. Sampling Distribution 1204 1207 NA 1209 6.3.5. Run-time Parameters and Data Format 1211 Run-time Parameters are input factors that must be determined, 1212 configured into the measurement system, and reported with the results 1213 for the context to be complete. 1215 1217 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1218 value for IPv6) 1220 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1221 value for IPv6) 1223 o T0, a time (start of measurement interval, 128-bit NTP Date 1224 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1225 start time is unspecified and Tf is to be interpreted as the 1226 Duration of the measurement interval. 1228 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1229 see section 6 of [RFC5905]), interpreted as the Duration of the 1230 measurement interval. 1232 o 1/lambda, average packet rate (for Poisson Streams). (1/lambda = 1233 0.1 packet per second, if fixed) 1235 o Upper limit on Poisson distribution (values above this limit will 1236 be clipped and set to the limit value). (if fixed, Upper limit = 1237 300 seconds.) 1239 o ID, the 16-bit identifier assigned by the program that generates 1240 the query, and which must vary in successive queries, see 1241 Section 4.1.1 of [RFC1035]. This identifier is copied into the 1242 corresponding reply and can be used by the requester to match-up 1243 replies to outstanding queries. 1245 The format for 1/lambda and Upper limit of Poisson Dist. are the 1246 short format in [RFC5905] (32 bits) and is as follows: the first 16 1247 bits represent the integer number of seconds; the next 16 bits 1248 represent the fractional part of a second. 1250 >>> should Poisson run-time params be fixed instead? probably yes if 1251 modeling a specific version of MBA tests. 1253 6.3.6. Roles 1255 1257 Src - launches each packet and waits for return transmissions from 1258 Dst. 1260 Dst - waits for each packet from Src and sends a return packet to 1261 Src. 1263 6.4. Output 1265 This category specifies all details of the Output of measurements 1266 using the metric. 1268 6.4.1. Type/Value (two diff terms used) 1270 1272 For all output types: 1274 o T0, a time (start of measurement interval, 128-bit NTP Date 1275 Format, see section 6 of [RFC5905]) 1277 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1278 see section 6 of [RFC5905]) 1280 Raw -- for each packet sent, pairs of values. 1282 >>> and the status of the response, only assigning values to 1283 successful query-response pairs. 1285 Percentile -- for the conditional distribution of all packets with a 1286 valid value of Round-trip delay (undefined delays are excluded), a 1287 single value corresponding to the 95th percentile. 1289 6.4.2. Data Format 1291 1293 Raw -- for each packet sent, pairs of values as follows: 1295 o T, the time when the packet was sent from Src, 128-bit NTP Date 1296 Format, see section 6 of [RFC5905]) 1298 o dT, a value of Round-trip delay, format is *similar to* the 32-bit 1299 short NTP Time format in Section 6 of [RFC5905] and is as follows: 1300 the first 16 bits represent the *signed* integer number of 1301 seconds; the next 16 bits represent the fractional part of a 1302 second. 1304 o dT is undefined when the packet is not received at Src in waiting 1305 time Tmxax seconds (need undefined code for no-response or un- 1306 successful response) 1308 Percentile -- for the conditional distribution of all packets with a 1309 valid value of Round-trip delay (undefined delays are excluded), a 1310 single value as follows: 1312 See section 4.1 of [RFC3393] for details on the conditional 1313 distribution to exclude undefined values of delay, and Section 5 of 1314 [RFC6703] for background on this analysis choice. 1316 See section 4.3 of [RFC3393] for details on the percentile statistic 1317 (where Round-trip delay should be substituted for "ipdv"). 1319 The percentile = 95. 1321 Data format is a 32-bit signed floating point value, *similar to* the 1322 32-bit short NTP Time format in Section 6 of [RFC5905] and is as 1323 follows: the first 16 bits represent the *signed* integer number of 1324 seconds; the next 16 bits represent the fractional part of a second. 1326 6.4.3. Reference 1328 1330 See the Data Format column for references. 1332 6.4.4. Metric Units 1334 . 1337 Round-trip Delay, dT, is expressed in seconds. 1339 The 95th Percentile of Round-trip Delay is expressed in seconds. 1341 6.5. Administrative items 1343 6.5.1. Status 1345 1347 6.5.2. Requestor (keep?) 1349 name or RFC, etc. 1351 6.5.3. Revision 1353 1.0 1355 6.5.4. Revision Date 1357 YYYY-MM-DD 1359 6.6. Comments and Remarks 1361 Additional (Informational) details for this entry 1363 7. UDP Poisson One-way Delay Registry Entries 1365 This section gives an initial registry entry for the UDP Poisson One- 1366 way Delay. 1368 Note: Each Registry "Name" below specifies a single registry entry, 1369 whose output format varies according to a component of the name that 1370 specifies one form of statistical summary. 1372 IANA is asked to assign a different numeric identifiers to each Name. 1373 All column entries beside the Summary and Output categories are the 1374 same, thus this section proposes five closely-related registry 1375 entries. As a result, IANA is also asked to assign corresponding 1376 URIs and URLs. 1378 7.1. Summary 1380 This category includes multiple indexes to the registry entries, the 1381 element ID and metric name. 1383 7.1.1. ID (Identifier) 1385 1388 7.1.2. Name 1390 1392 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_ 1394 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Percentile95 1396 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Mean 1398 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Min 1400 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Max 1402 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Std_Dev 1404 7.1.3. URI and URL 1406 URI: Prefix urn:ietf:params:performance:metric... 1408 URL: http:\\www.iana.org\ ... 1410 7.1.4. Description 1412 This metric assesses the delay of a stream of packets exchanged 1413 between two hosts (or measurement points), and reports the 1414 One-way delay for all successfully exchanged packets 1415 based on their conditional delay distribution. 1417 7.2. Metric Definition 1419 This category includes columns to prompt the entry of all necessary 1420 details related to the metric definition, including the RFC reference 1421 and values of input factors, called fixed parameters. 1423 7.2.1. Reference Definition 1425 1427 Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric 1428 for IPPM", RFC 2679, September 1999. 1430 [RFC2679] 1432 Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC 1433 6049, January 2011. 1435 [RFC6049] 1437 1439 Section 3.4 of [RFC2679] provides the reference definition of the 1440 singleton (single value) One-way delay metric. Section 4.4 of 1441 [RFC2679] provides the reference definition expanded to cover a 1442 multi-value sample. Note that terms such as singleton and sample are 1443 defined in Section 11 of [RFC2330]. 1445 Only successful packet transfers with finite delay are included in 1446 the sample, as prescribed in section 4.1.2 of [RFC6049]. 1448 NOTE: RFC2679 will be replaced by 2679-bis on approval, see draft- 1449 ietf-ippm-2679-bis-01. 1451 7.2.2. Fixed Parameters 1453 1457 Type-P: 1459 o IPv4 header values: 1461 * DSCP: set to 0 1463 * TTL set to 255 1465 * Protocol: Set to 17 (UDP) 1467 o UDP header values: 1469 * Checksum: the checksum must be calculated 1471 o UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357] 1473 * Security features in use influence the number of Padding 1474 octets. 1476 * 250 octets total, including the TWAMP format 1478 Timeout, Tmax: 3 seconds 1480 7.3. Method of Measurement 1482 This category includes columns for references to relevant sections of 1483 the RFC(s) and any supplemental information needed to ensure an 1484 unambiguous methods for implementations. 1486 7.3.1. Reference Method 1488 1491 The methodology for this metric is defined as Type-P-One-way-Delay- 1492 Poisson-Stream in section 3.6 of [RFC2679] and section 4.6 of 1493 [RFC2679] using the Type-P and Timeout defined under Fixed 1494 Parameters. 1496 The method requires sequence numbers or other send-order information 1497 to be retained at the Src or included with each packet to dis- 1498 ambiguate packet reordering if it occurs. Sequence number is part of 1499 the TWAMP payload described under Fixed Parameters. 1501 7.3.2. Packet Generation Stream 1503 This section gives the details of the packet traffic which is the 1504 basis for measurement. In IPPM metrics, this is called the Stream, 1505 and can easily be dscribed by providing the list of stream 1506 parameters. 1508 1510 Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to 1511 generate Poisson sampling intervals. The reciprocal of lambda is the 1512 average packet rate, thus the Run-time Parameter is 1/lambda. 1514 Method 3 or equivalent SHALL used, where given a start time (Run-time 1515 Parameter), the subsequent send times are all computed prior to 1516 measurement by computing the pseudo-random distribution of inter- 1517 packet send times, (truncating the distribution as specified in the 1518 Run-time Parameters), and the Src sends each packet at the computed 1519 times. 1521 7.3.3. Traffic Filtering (observation) Details 1523 NA 1525 7.3.4. Sampling Distribution 1527 NA 1529 7.3.5. Run-time Parameters and Data Format 1531 Run-time Parameters are input factors that must be determined, 1532 configured into the measurement system, and reported with the results 1533 for the context to be complete. 1535 1537 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1538 value for IPv6) 1540 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1541 value for IPv6) 1543 o T0, a time (start of measurement interval, 128-bit NTP Date 1544 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1545 start time is unspecified and Tf is to be interpreted as the 1546 Duration of the measurement interval. 1548 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1549 see section 6 of [RFC5905]), interpreted as the Duration of the 1550 measurement interval. 1552 o 1/lambda, average packet rate (for Poisson Streams). (1/lambda = 1553 1 packet per second, if fixed) 1555 o Upper limit on Poisson distribution (values above this limit will 1556 be clipped and set to the limit value). (if fixed, Upper limit = 1557 30 seconds.) 1559 The format for 1/lambda and Upper limit of Poisson Dist. are the 1560 short format in [RFC5905] (32 bits) and is as follows: the first 16 1561 bits represent the integer number of seconds; the next 16 bits 1562 represent the fractional part of a second. 1564 >>> should Poisson run-time params be fixed instead? probably yes if 1565 modeling a specific version of tests. Note in the NAME, i.e. 1566 Poisson3.3 1568 7.3.6. Roles 1570 1572 Src - launches each packet and waits for return transmissions from 1573 Dst. This is the TWAMP Session-Sender. 1575 Dst - waits for each packet from Src and sends a return packet to 1576 Src. This is the TWAMP Session-Reflector. 1578 7.4. Output 1580 This category specifies all details of the Output of measurements 1581 using the metric. 1583 7.4.1. Type/Value (two diff terms used) 1585 1587 See subsection titles below for Types. 1589 7.4.2. Data Format 1591 1593 For all output types --- 1595 o T0, a time (start of measurement interval, 128-bit NTP Date 1596 Format, see section 6 of [RFC5905]) 1598 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1599 see section 6 of [RFC5905]) 1601 7.4.2.1. Percentile95 1603 The 95th percentile SHALL be calculated using the conditional 1604 distribution of all packets with a finite value of One-way delay 1605 (undefined delays are excluded), a single value as follows: 1607 See section 4.1 of [RFC3393] for details on the conditional 1608 distribution to exclude undefined values of delay, and Section 5 of 1609 [RFC6703] for background on this analysis choice. 1611 See section 4.3 of [RFC3393] for details on the percentile statistic 1612 (where Round-trip delay should be substituted for "ipdv"). 1614 The percentile = 95. 1616 Data format is a 32-bit signed value, *similar to* the 32-bit short 1617 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1618 first 16 bits represent the *signed* integer number of seconds; the 1619 next 16 bits represent the fractional part of a second. 1621 7.4.2.2. Mean 1623 The mean SHALL be calculated using the conditional distribution of 1624 all packets with a finite value of One-way delay (undefined delays 1625 are excluded), a single value as follows: 1627 See section 4.1 of [RFC3393] for details on the conditional 1628 distribution to exclude undefined values of delay, and Section 5 of 1629 [RFC6703] for background on this analysis choice. 1631 See section 4.2.2 of [RFC6049] for details on calculating this 1632 statistic, and 4.2.3 of [RFC6049]. 1634 Data format is a 32-bit signed value, *similar to* the 32-bit short 1635 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1636 first 16 bits represent the *signed* integer number of seconds; the 1637 next 16 bits represent the fractional part of a second. 1639 7.4.2.3. Min 1641 The minimum SHALL be calculated using the conditional distribution of 1642 all packets with a finite value of One-way delay (undefined delays 1643 are excluded), a single value as follows: 1645 See section 4.1 of [RFC3393] for details on the conditional 1646 distribution to exclude undefined values of delay, and Section 5 of 1647 [RFC6703] for background on this analysis choice. 1649 See section 4.3.2 of [RFC6049] for details on calculating this 1650 statistic, and 4.3.3 of [RFC6049]. 1652 Data format is a 32-bit signed value, *similar to* the 32-bit short 1653 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1654 first 16 bits represent the *signed* integer number of seconds; the 1655 next 16 bits represent the fractional part of a second. 1657 7.4.2.4. Max 1659 The maximum SHALL be calculated using the conditional distribution of 1660 all packets with a finite value of One-way delay (undefined delays 1661 are excluded), a single value as follows: 1663 See section 4.1 of [RFC3393] for details on the conditional 1664 distribution to exclude undefined values of delay, and Section 5 of 1665 [RFC6703] for background on this analysis choice. 1667 See section 4.3.2 of [RFC6049] for a closely related method for 1668 calculating this statistic, and 4.3.3 of [RFC6049]. The formula is 1669 as follows: 1671 Max = (FiniteDelay [j]) 1673 such that for some index, j, where 1 <= j <= N 1674 FiniteDelay[j] >= FiniteDelay[n] for all n 1676 Data format is a 32-bit signed value, *similar to* the 32-bit short 1677 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1678 first 16 bits represent the *signed* integer number of seconds; the 1679 next 16 bits represent the fractional part of a second. 1681 7.4.2.5. Std_Dev 1683 7.4.3. Reference 1685 1687 See the Data Format column for references. 1689 7.4.4. Metric Units 1691 . 1694 The of One-way Delay is expressed in seconds. 1696 The 95th Percentile of One-way Delay is expressed in seconds. 1698 7.5. Administrative items 1700 7.5.1. Status 1702 1704 7.5.2. Requestor (keep?) 1706 name or RFC, etc. 1708 7.5.3. Revision 1710 1.0 1712 7.5.4. Revision Date 1714 YYYY-MM-DD 1716 7.6. Comments and Remarks 1718 Additional (Informational) details for this entry 1720 8. UDP Periodic One-way Delay Registry Entries 1722 This section gives an initial registry entry for the UDP Periodic 1723 One-way Delay. 1725 Note: Each Registry "Name" below specifies a single registry entry, 1726 whose output format varies according to a component of the name that 1727 specifies one form of statistical summary. 1729 IANA is asked to assign a different numeric identifiers to each Name. 1730 All other column entries are the same, thus this section is proposes 1731 five closely-related registry entries. As a result, IANA is also 1732 asked to assign corresponding URIs and URLs. 1734 8.1. Summary 1736 This category includes multiple indexes to the registry entries, the 1737 element ID and metric name. 1739 8.1.1. ID (Identifier) 1741 1744 8.1.2. Name 1746 1748 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_ 1750 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Percentile95 1752 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Mean 1754 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Min 1756 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Max 1758 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Std_Dev 1760 8.1.3. URI and URL 1762 URI: Prefix urn:ietf:params:performance:metric... 1764 URL: http:\\www.iana.org\ ... 1766 8.1.4. Description 1768 This metric assesses the delay of a stream of packets exchanged 1769 between two hosts (or measurement points), and reports the 1770 One-way delay for all successfully exchanged packets 1771 based on their conditional delay distribution. 1773 8.2. Metric Definition 1775 This category includes columns to prompt the entry of all necessary 1776 details related to the metric definition, including the RFC reference 1777 and values of input factors, called fixed parameters. 1779 8.2.1. Reference Definition 1781 1783 Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric 1784 for IPPM", RFC 2679, September 1999. 1786 [RFC2679] 1788 Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC 1789 6049, January 2011. 1791 [RFC6049] 1792 1794 Section 3.4 of [RFC2679] provides the reference definition of the 1795 singleton (single value) One-way delay metric. Section 4.4 of 1796 [RFC2679] provides the reference definition expanded to cover a 1797 multi-value sample. Note that terms such as singleton and sample are 1798 defined in Section 11 of [RFC2330]. 1800 Only successful packet transfers with finite delay are included in 1801 the sample, as prescribed in section 4.1.2 of [RFC6049]. 1803 NOTE: RFC2679 will be replaced by 2679-bis on approval, see draft- 1804 ietf-ippm-2679-bis-01. 1806 ANY other conditions, ... 1808 8.2.2. Fixed Parameters 1810 1814 Type-P: 1816 o IPv4 header values: 1818 * DSCP: set to 0 1820 * TTL set to 255 1822 * Protocol: Set to 17 (UDP) 1824 o UDP header values: 1826 * Checksum: the checksum must be calculated 1828 o UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357] 1830 * Security features in use influence the number of Padding 1831 octets. 1833 * 142 octets total, including the TWAMP format 1835 Timeout, Tmax: 3 seconds 1837 8.3. Method of Measurement 1839 This category includes columns for references to relevant sections of 1840 the RFC(s) and any supplemental information needed to ensure an 1841 unambiguous methods for implementations. 1843 8.3.1. Reference Method 1845 1848 The methodology for this metric is defined as Type-P-One-way-Delay- 1849 Poisson-Stream in section 3.6 of [RFC2679] and section 4.6 of 1850 [RFC2679] using the Type-P and Timeout defined under Fixed 1851 Parameters. 1853 The method requires sequence numbers or other send-order information 1854 to be retained at the Src or included with each packet to dis- 1855 ambiguate packet reordering if it occurs. Sequence number is part of 1856 the TWAMP payload described under Fixed Parameters. 1858 8.3.2. Packet Generation Stream 1860 This section gives the details of the packet traffic which is the 1861 basis for measurement. In IPPM metrics, this is called the Stream, 1862 and can easily be dscribed by providing the list of stream 1863 parameters. 1865 1867 Section 3 of [RFC3432] prescribes the method for generating Periodic 1868 streams using associated parameters. 1870 o incT, the nominal duration of inter-packet interval, first bit to 1871 first bit 1873 o dT, the duration of the interval for allowed sample start times 1875 o T0, the actual start time 1877 NOTE: an initiation process with a number of control exchanges 1878 resulting in unpredictable start times (within a time interval) may 1879 be sufficient to avoid synchronization of periodic streams, and 1880 therefore a valid replacement for selecting a start time at random 1881 from a fixed interval. 1883 These stream parameters will be specified as Run-time parameters. 1885 8.3.3. Traffic Filtering (observation) Details 1887 NA 1889 8.3.4. Sampling Distribution 1891 NA 1893 8.3.5. Run-time Parameters and Data Format 1895 Run-time Parameters are input factors that must be determined, 1896 configured into the measurement system, and reported with the results 1897 for the context to be complete. 1899 1901 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1902 value for IPv6) 1904 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1905 value for IPv6) 1907 o T0, a time (start of measurement interval, 128-bit NTP Date 1908 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1909 start time is unspecified and Tf is to be interpreted as the 1910 Duration of the measurement interval. 1912 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1913 see section 6 of [RFC5905]), interpreted as the Duration of the 1914 measurement interval. 1916 o incT, the nominal duration of inter-packet interval, first bit to 1917 first bit 1919 o dT, the duration of the interval for allowed sample start times 1921 The format for incT and dT are the short format in [RFC5905] (32 1922 bits) and is as follows: the first 16 bits represent the integer 1923 number of seconds; the next 16 bits represent the fractional part of 1924 a second. 1926 >>> should Periodic run-time params be fixed instead? probably yes if 1927 modeling a specific version of tests. Note in the NAME, i.e. 1928 Poisson3.3 1930 8.3.6. Roles 1932 1934 Src - launches each packet and waits for return transmissions from 1935 Dst. This is the TWAMP Session-Sender. 1937 Dst - waits for each packet from Src and sends a return packet to 1938 Src. This is the TWAMP Session-Reflector. 1940 8.4. Output 1942 This category specifies all details of the Output of measurements 1943 using the metric. 1945 8.4.1. Type/Value (two diff terms used) 1947 1949 See subsection titles in Data Format for Types. 1951 8.4.2. Data Format 1953 1955 For all output types --- 1957 o T0, a time (start of measurement interval, 128-bit NTP Date 1958 Format, see section 6 of [RFC5905]) 1960 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1961 see section 6 of [RFC5905]) 1963 8.4.2.1. Percentile95 1965 The 95th percentile SHALL be calculated using the conditional 1966 distribution of all packets with a finite value of One-way delay 1967 (undefined delays are excluded), a single value as follows: 1969 See section 4.1 of [RFC3393] for details on the conditional 1970 distribution to exclude undefined values of delay, and Section 5 of 1971 [RFC6703] for background on this analysis choice. 1973 See section 4.3 of [RFC3393] for details on the percentile statistic 1974 (where Round-trip delay should be substituted for "ipdv"). 1976 The percentile = 95. 1978 Data format is a 32-bit signed value, *similar to* the 32-bit short 1979 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1980 first 16 bits represent the *signed* integer number of seconds; the 1981 next 16 bits represent the fractional part of a second. 1983 8.4.2.2. Mean 1985 The mean SHALL be calculated using the conditional distribution of 1986 all packets with a finite value of One-way delay (undefined delays 1987 are excluded), a single value as follows: 1989 See section 4.1 of [RFC3393] for details on the conditional 1990 distribution to exclude undefined values of delay, and Section 5 of 1991 [RFC6703] for background on this analysis choice. 1993 See section 4.2.2 of [RFC6049] for details on calculating this 1994 statistic, and 4.2.3 of [RFC6049]. 1996 Data format is a 32-bit signed value, *similar to* the 32-bit short 1997 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1998 first 16 bits represent the *signed* integer number of seconds; the 1999 next 16 bits represent the fractional part of a second. 2001 8.4.2.3. Min 2003 The minimum SHALL be calculated using the conditional distribution of 2004 all packets with a finite value of One-way delay (undefined delays 2005 are excluded), a single value as follows: 2007 See section 4.1 of [RFC3393] for details on the conditional 2008 distribution to exclude undefined values of delay, and Section 5 of 2009 [RFC6703] for background on this analysis choice. 2011 See section 4.3.2 of [RFC6049] for details on calculating this 2012 statistic, and 4.3.3 of [RFC6049]. 2014 Data format is a 32-bit signed value, *similar to* the 32-bit short 2015 NTP Time format in Section 6 of [RFC5905] and is as follows: the 2016 first 16 bits represent the *signed* integer number of seconds; the 2017 next 16 bits represent the fractional part of a second. 2019 8.4.2.4. Max 2021 The maximum SHALL be calculated using the conditional distribution of 2022 all packets with a finite value of One-way delay (undefined delays 2023 are excluded), a single value as follows: 2025 See section 4.1 of [RFC3393] for details on the conditional 2026 distribution to exclude undefined values of delay, and Section 5 of 2027 [RFC6703] for background on this analysis choice. 2029 See section 4.3.2 of [RFC6049] for a closely related method for 2030 calculating this statistic, and 4.3.3 of [RFC6049]. The formula is 2031 as follows: 2033 Max = (FiniteDelay [j]) 2035 such that for some index, j, where 1 <= j <= N 2036 FiniteDelay[j] >= FiniteDelay[n] for all n 2038 Data format is a 32-bit signed value, *similar to* the 32-bit short 2039 NTP Time format in Section 6 of [RFC5905] and is as follows: the 2040 first 16 bits represent the *signed* integer number of seconds; the 2041 next 16 bits represent the fractional part of a second. 2043 8.4.2.5. Std_Dev 2045 8.4.3. Reference 2047 2049 See the Data Format column for references. 2051 8.4.4. Metric Units 2053 . 2056 The of One-way Delay is expressed in seconds. 2058 8.5. Administrative items 2060 8.5.1. Status 2062 2064 8.5.2. Requestor (keep?) 2066 name or RFC, etc. 2068 8.5.3. Revision 2070 1.0 2072 8.5.4. Revision Date 2074 YYYY-MM-DD 2076 8.6. Comments and Remarks 2078 Additional (Informational) details for this entry 2080 9. partly BLANK Registry Entry 2082 This section gives an initial registry entry for .... 2084 9.1. Summary 2086 This category includes multiple indexes to the registry entries, the 2087 element ID and metric name. 2089 2091 9.1.1. ID (Identifier) 2093 2095 9.1.2. Name 2097 2099 URL: ?? 2101 9.1.3. URI 2103 URI: Prefix urn:ietf:params:performance:metric 2105 9.1.4. Description 2107 TBD. 2109 9.2. Metric Definition 2111 This category includes columns to prompt the entry of all necessary 2112 details related to the metric definition, including the RFC reference 2113 and values of input factors, called fixed parameters. 2115 9.2.1. Reference Definition 2117 2118 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 2119 Metric for IPPM", RFC 2681, September 1999. 2121 2123 Section 2.4 of [RFC2681] provides the reference definition of the 2124 singleton (single value) Round-trip delay metric. Section 3.4 of 2125 [RFC2681] provides the reference definition expanded to cover a 2126 multi-value sample. Note that terms such as singleton and sample are 2127 defined in Section 11 of [RFC2330]. 2129 Note that although the definition of "Round-trip-Delay between Src 2130 and Dst at T" is directionally ambiguous in the text, this metric 2131 tightens the definition further to recognize that the host in the 2132 "Src" role will send the first packet to "Dst", and ultimately 2133 receive the corresponding return packet from "Dst" (when neither are 2134 lost). 2136 <<< Check how the Methodology also makes this clear (or not) >>> 2138 9.2.2. Fixed Parameters 2140 2144 Type-P: 2146 o IPv4 header values: 2148 * DSCP: set to 0 2150 * TTL set to 255 2152 * Protocol: Set to 17 (UDP) 2154 o UDP header values: 2156 * Checksum: the checksum must be calculated 2158 o Payload 2160 * Sequence number: 8-byte integer 2162 * Timestamp: 8 byte integer. Expressed as 64-bit NTP timestamp 2163 as per section 6 of RFC 5905 [RFC5905] 2165 * No padding (total of 9 bytes) 2167 Timeout: 3 seconds 2169 9.3. Method of Measurement 2171 This category includes columns for references to relevant sections of 2172 the RFC(s) and any supplemental information needed to ensure an 2173 unambiguous methods for implementations. 2175 9.3.1. Reference Method 2177 2180 9.3.2. Packet Generation Stream 2182 This section gives the details of the packet traffic which is the 2183 basis for measurement. In IPPM metrics, this is called the Stream, 2184 and can easily be dscribed by providing the list of stream 2185 parameters. 2187 2189 9.3.3. Traffic Filtering (observation) Details 2191 The measured results based on a filtered version of the packets 2192 observed, and this section provides the filter details (when 2193 present). 2195
. 2197 9.3.4. Sampling Distribution 2199 2202 9.3.5. Run-time Parameters and Data Format 2204 Run-time Parameters are input factors that must be determined, 2205 configured into the measurement system, and reported with the results 2206 for the context to be complete. 2208 2210 . 2212 9.3.6. Roles 2214 2216 9.4. Output 2218 This category specifies all details of the Output of measurements 2219 using the metric. 2221 9.4.1. Type/Value (two diff terms used) 2223 2225 9.4.2. Data Format 2227 2229 o Value: 2231 o Data Format: (There may be some precedent to follow here, but 2232 otherwise use 64-bit NTP Timestamp Format, see section 6 of 2233 [RFC5905]). 2235 o Reference:
2237 9.4.3. Reference 2239 2241 9.4.4. Metric Units 2243 . 2246 9.5. Administrative items 2248 9.5.1. Status 2250 2252 9.5.2. Requestor (keep?) 2254 name or RFC, etc. 2256 9.5.3. Revision 2258 1.0 2260 9.5.4. Revision Date 2262 YYYY-MM-DD 2264 9.6. Comments and Remarks 2266 Additional (Informational) details for this entry 2268 10. BLANK Registry Entry 2270 This section gives an initial registry entry for .... 2272 10.1. Summary 2274 This category includes multiple indexes to the registry entries, the 2275 element ID and metric name. 2277 2279 10.1.1. ID (Identifier) 2281 2283 10.1.2. Name 2285 2287 URL: ?? 2289 10.1.3. URI 2291 URI: Prefix urn:ietf:params:performance:metric 2293 10.1.4. Description 2295 TBD. 2297 10.2. Metric Definition 2299 This category includes columns to prompt the entry of all necessary 2300 details related to the metric definition, including the RFC reference 2301 and values of input factors, called fixed parameters. 2303 10.2.1. Reference Definition 2305 2307 2309 10.2.2. Fixed Parameters 2311 2315 10.3. Method of Measurement 2317 This category includes columns for references to relevant sections of 2318 the RFC(s) and any supplemental information needed to ensure an 2319 unambiguous methods for implementations. 2321 10.3.1. Reference Method 2323 2326 10.3.2. Packet Generation Stream 2328 2330 10.3.3. Traffic Filtering (observation) Details 2332 . 2336 10.3.4. Sampling Distribution 2338 2341 10.3.5. Run-time Parameters and Data Format 2343 . 2345 10.3.6. Roles 2347 2349 10.4. Output 2351 This category specifies all details of the Output of measurements 2352 using the metric. 2354 10.4.1. Type/Value (two diff terms used) 2356 2358 10.4.2. Data Format 2360 2362 10.4.3. Reference 2364 2366 10.4.4. Metric Units 2368 . 2371 10.5. Administrative items 2373 10.5.1. Status 2375 2377 10.5.2. Requestor (keep?) 2379 2381 10.5.3. Revision 2383 1.0 2385 10.5.4. Revision Date 2387 YYYY-MM-DD 2389 10.6. Comments and Remarks 2391 Additional (Informational) details for this entry 2393 11. Example RTCP-XR Registry Entry 2395 This section is MAY BE DELETED or adapted before submission. 2397 This section gives an example registry entry for the end-point metric 2398 described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric 2399 reporting. 2401 11.1. Registry Indexes 2403 This category includes multiple indexes to the registry entries, the 2404 element ID and metric name. 2406 11.1.1. Identifier 2408 An integer having enough digits to uniquely identify each entry in 2409 the Registry. 2411 11.1.2. Name 2413 A metric naming convention is TBD. 2415 11.1.3. URI 2417 Prefix urn:ietf:params:performance:metric 2419 11.1.4. Status 2421 current 2423 11.1.5. Requestor 2425 Alcelip Mornuley 2427 11.1.6. Revision 2429 1.0 2431 11.1.7. Revision Date 2433 2014-07-04 2435 11.1.8. Description 2437 TBD. 2439 11.1.9. Reference Specification(s) 2441 [RFC3611][RFC4566][RFC6776][RFC6792][RFC7003] 2443 11.2. Metric Definition 2445 This category includes columns to prompt the entry of all necessary 2446 details related to the metric definition, including the RFC reference 2447 and values of input factors, called fixed parameters. Section 3.2 of 2448 [RFC7003] provides the reference information for this category. 2450 11.2.1. Reference Definition 2452 Packets Discarded in Bursts: 2454 The total number of packets discarded during discard bursts. The 2455 measured value is unsigned value. If the measured value exceeds 2456 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over- 2457 range measurement. If the measurement is unavailable, the value 2458 0xFFFFFF MUST be reported. 2460 11.2.2. Fixed Parameters 2462 Fixed Parameters are input factors that must be determined and 2463 embedded in the measurement system for use when needed. The values 2464 of these parameters is specified in the Registry. 2466 Threshold: 8 bits, set to value = 3 packets. 2468 The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of 2469 successive packets that must not be discarded prior to and following 2470 a discard packet in order for this discarded packet to be regarded as 2471 part of a gap. Note that the Threshold is set in accordance with the 2472 Gmin calculation defined in Section 4.7.2 of [RFC3611]. 2474 Interval Metric flag: 2 bits, set to value 11=Cumulative Duration 2476 This field is used to indicate whether the burst/gap discard metrics 2477 are Sampled, Interval, or Cumulative metrics [RFC6792]: 2479 I=10: Interval Duration - the reported value applies to the most 2480 recent measurement interval duration between successive metrics 2481 reports. 2483 I=11: Cumulative Duration - the reported value applies to the 2484 accumulation period characteristic of cumulative measurements. 2486 Senders MUST NOT use the values I=00 or I=01. 2488 11.3. Method of Measurement 2490 This category includes columns for references to relevant sections of 2491 the RFC(s) and any supplemental information needed to ensure an 2492 unambiguous methods for implementations. For the Burst/Gap Discard 2493 Metric, it appears that the only guidance on methods of measurement 2494 is in Section 3.0 of [RFC7003] and its supporting references. 2495 Relevant information is repeated below, although there appears to be 2496 no section titled "Method of Measurement" in [RFC7003]. 2498 11.3.1. Reference Method 2500 Metrics in this block report on burst/gap discard in the stream 2501 arriving at the RTP system. Measurements of these metrics are made 2502 at the receiving end of the RTP stream. Instances of this metrics 2503 block use the synchronization source (SSRC) to refer to the separate 2504 auxiliary Measurement Information Block [RFC6776], which describes 2505 measurement periods in use (see [RFC6776], Section 4.2). 2507 This metrics block relies on the measurement period in the 2508 Measurement Information Block indicating the span of the report. 2509 Senders MUST send this block in the same compound RTCP packet as the 2510 Measurement Information Block. Receivers MUST verify that the 2511 measurement period is received in the same compound RTCP packet as 2512 this metrics block. If not, this metrics block MUST be discarded. 2514 11.3.2. Stream Type and Stream Parameters 2516 Since RTCP-XR Measurements are conducted on live RTP traffic, the 2517 complete description of the stream is contained in SDP messages that 2518 proceed the establishment of a compatible stream between two or more 2519 communicating hosts. See Run-time Parameters, below. 2521 11.3.3. Output Type and Data Format 2523 The output type defines the type of result that the metric produces. 2525 o Value: Packets Discarded in Bursts 2527 o Data Format: 24 bits 2529 o Reference: Section 3.2 of [RFC7003] 2531 11.3.4. Metric Units 2533 The measured results are apparently expressed in packets, although 2534 there is no section of [RFC7003] titled "Metric Units". 2536 11.3.5. Run-time Parameters and Data Format 2538 Run-Time Parameters are input factors that must be determined, 2539 configured into the measurement system, and reported with the results 2540 for the context to be complete. However, the values of these 2541 parameters is not specified in the Registry, rather these parameters 2542 are listed as an aid to the measurement system implementor or user 2543 (they must be left as variables, and supplied on execution). 2545 The Data Format of each Run-time Parameter SHALL be specified in this 2546 column, to simplify the control and implementation of measurement 2547 devices. 2549 SSRC of Source: 32 bits As defined in Section 4.1 of [RFC3611]. 2551 SDP Parameters: As defined in [RFC4566] 2553 Session description v= (protocol version number, currently only 0) 2555 o= (originator and session identifier : username, id, version number, 2556 network address) 2558 s= (session name : mandatory with at least one UTF-8-encoded 2559 character) 2561 i=* (session title or short information) u=* (URI of description) 2563 e=* (zero or more email address with optional name of contacts) 2565 p=* (zero or more phone number with optional name of contacts) 2567 c=* (connection information--not required if included in all media) 2569 b=* (zero or more bandwidth information lines) One or more Time 2570 descriptions ("t=" and "r=" lines; see below) 2572 z=* (time zone adjustments) 2574 k=* (encryption key) 2576 a=* (zero or more session attribute lines) 2578 Zero or more Media descriptions (each one starting by an "m=" line; 2579 see below) 2581 m= (media name and transport address) 2583 i=* (media title or information field) 2584 c=* (connection information -- optional if included at session level) 2586 b=* (zero or more bandwidth information lines) 2588 k=* (encryption key) 2590 a=* (zero or more media attribute lines -- overriding the Session 2591 attribute lines) 2593 An example Run-time SDP description follows: 2595 v=0 2597 o=jdoe 2890844526 2890842807 IN IP4 192.0.2.5 2599 s=SDP Seminar i=A Seminar on the session description protocol 2601 u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane 2602 Doe) 2604 c=IN IP4 233.252.0.12/127 2606 t=2873397496 2873404696 2608 a=recvonly 2610 m=audio 49170 RTP/AVP 0 2612 m=video 51372 RTP/AVP 99 2614 a=rtpmap:99 h263-1998/90000 2616 11.4. Comments and Remarks 2618 TBD. 2620 12. Revision History 2622 This section may be removed for publication. It contains partial 2623 information on updtes. 2625 This draft replaced draft-mornuley-ippm-initial-registry. 2627 In version 02, Section 4 has been edited to reflect recent discussion 2628 on the ippm-list: * Removed the combination or "Raw" and left 95th 2629 percentile. * Hanging Indent on Run-time parameters (Fixed parameters 2630 use bullet lists and other indenting formats. * Payload format for 2631 measurement has been removed. * Explanation of Conditional delay 2632 distribution. 2634 Version 03 addressed Phil Eardley's comments and suggestions in 2635 sections 1-4. and resolved the definition of Percentiles. 2637 Version 04 * All section 4 parameters reference YANG types for 2638 alternate data formats. * Discussion has concluded that usecase(s) 2639 for machine parse-able registry columns are not needed. 2641 Still need: * suggestion of standard naming format for parameters. 2643 Note: lambda parameter description is correct in section 4, elsewhere 2644 needs fix. 2646 13. Security Considerations 2648 These registry entries represent no known security implications for 2649 Internet Security. Each referenced Metric contains a Security 2650 Considerations section. 2652 14. IANA Considerations 2654 IANA is requested to populate The Performance Metric Registry defined 2655 in [I-D.ietf-ippm-metric-registry] with the values defined above. 2657 2659 15. Acknowledgements 2661 The authors thank Brian Trammell for suggesting the term "Run-time 2662 Parameters", which led to the distinction between run-time and fixed 2663 parameters implemented in this memo, for identifying the IPFIX metric 2664 with Flow Key as an example, and for many other productive 2665 suggestions. Thanks to Peter Koch, who provided several useful 2666 suggestions for disambiguating successive DNS Queries in the DNS 2667 Response time metric. 2669 The authors also acknowledge the constructive reviews and helpful 2670 suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey, and 2671 participants in the LMAP working group. 2673 16. References 2674 16.1. Normative References 2676 [I-D.ietf-ippm-metric-registry] 2677 Bagnulo, M., Claise, B., Eardley, P., and A. Morton, 2678 "Registry for Performance Metrics", Internet Draft (work 2679 in progress) draft-ietf-ippm-metric-registry, 2014. 2681 [RFC1035] Mockapetris, P., "Domain names - implementation and 2682 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 2683 November 1987, . 2685 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2686 Requirement Levels", BCP 14, RFC 2119, 2687 DOI 10.17487/RFC2119, March 1997, 2688 . 2690 [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, 2691 "Framework for IP Performance Metrics", RFC 2330, 2692 DOI 10.17487/RFC2330, May 1998, 2693 . 2695 [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way 2696 Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, 2697 September 1999, . 2699 [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way 2700 Packet Loss Metric for IPPM", RFC 2680, 2701 DOI 10.17487/RFC2680, September 1999, 2702 . 2704 [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip 2705 Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681, 2706 September 1999, . 2708 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 2709 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 2710 . 2712 [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation 2713 Metric for IP Performance Metrics (IPPM)", RFC 3393, 2714 DOI 10.17487/RFC3393, November 2002, 2715 . 2717 [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network 2718 performance measurement with periodic streams", RFC 3432, 2719 DOI 10.17487/RFC3432, November 2002, 2720 . 2722 [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, 2723 S., and J. Perser, "Packet Reordering Metrics", RFC 4737, 2724 DOI 10.17487/RFC4737, November 2006, 2725 . 2727 [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. 2728 Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", 2729 RFC 5357, DOI 10.17487/RFC5357, October 2008, 2730 . 2732 [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, 2733 "Network Time Protocol Version 4: Protocol and Algorithms 2734 Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, 2735 . 2737 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 2738 the Network Configuration Protocol (NETCONF)", RFC 6020, 2739 DOI 10.17487/RFC6020, October 2010, 2740 . 2742 [RFC6049] Morton, A. and E. Stephan, "Spatial Composition of 2743 Metrics", RFC 6049, DOI 10.17487/RFC6049, January 2011, 2744 . 2746 [RFC6673] Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673, 2747 DOI 10.17487/RFC6673, August 2012, 2748 . 2750 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 2751 RFC 6991, DOI 10.17487/RFC6991, July 2013, 2752 . 2754 16.2. Informative References 2756 [Brow00] Brownlee, N., "Packet Matching for NeTraMet 2757 Distributions", March 2000. 2759 [RFC1242] Bradner, S., "Benchmarking Terminology for Network 2760 Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, 2761 July 1991, . 2763 [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed., 2764 "RTP Control Protocol Extended Reports (RTCP XR)", 2765 RFC 3611, DOI 10.17487/RFC3611, November 2003, 2766 . 2768 [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics 2769 Registry", BCP 108, RFC 4148, DOI 10.17487/RFC4148, August 2770 2005, . 2772 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 2773 Description Protocol", RFC 4566, DOI 10.17487/RFC4566, 2774 July 2006, . 2776 [RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP 2777 Flow Information Export (IPFIX) Applicability", RFC 5472, 2778 DOI 10.17487/RFC5472, March 2009, 2779 . 2781 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 2782 Carle, "Information Model for Packet Sampling Exports", 2783 RFC 5477, DOI 10.17487/RFC5477, March 2009, 2784 . 2786 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 2787 Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, 2788 March 2009, . 2790 [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics 2791 (IPPM) Registry of Metrics Are Obsolete", RFC 6248, 2792 DOI 10.17487/RFC6248, April 2011, 2793 . 2795 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 2796 Performance Metric Development", BCP 170, RFC 6390, 2797 DOI 10.17487/RFC6390, October 2011, 2798 . 2800 [RFC6703] Morton, A., Ramachandran, G., and G. Maguluri, "Reporting 2801 IP Network Performance Metrics: Different Points of View", 2802 RFC 6703, DOI 10.17487/RFC6703, August 2012, 2803 . 2805 [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information 2806 Reporting Using a Source Description (SDES) Item and an 2807 RTCP Extended Report (XR) Block", RFC 6776, 2808 DOI 10.17487/RFC6776, October 2012, 2809 . 2811 [RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use 2812 of the RTP Monitoring Framework", RFC 6792, 2813 DOI 10.17487/RFC6792, November 2012, 2814 . 2816 [RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control 2817 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 2818 Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003, 2819 September 2013, . 2821 [RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., 2822 Aitken, P., and A. Akhter, "A Framework for Large-Scale 2823 Measurement of Broadband Performance (LMAP)", RFC 7594, 2824 DOI 10.17487/RFC7594, September 2015, 2825 . 2827 Authors' Addresses 2829 Al Morton 2830 AT&T Labs 2831 200 Laurel Avenue South 2832 Middletown,, NJ 07748 2833 USA 2835 Phone: +1 732 420 1571 2836 Fax: +1 732 368 1192 2837 Email: acmorton@att.com 2838 URI: http://home.comcast.net/~acmacm/ 2840 Marcelo Bagnulo 2841 Universidad Carlos III de Madrid 2842 Av. Universidad 30 2843 Leganes, Madrid 28911 2844 SPAIN 2846 Phone: 34 91 6249500 2847 Email: marcelo@it.uc3m.es 2848 URI: http://www.it.uc3m.es 2850 Philip Eardley 2851 BT 2852 Adastral Park, Martlesham Heath 2853 Ipswich 2854 ENGLAND 2856 Email: philip.eardley@bt.com 2857 Kevin D'Souza 2858 AT&T Labs 2859 200 Laurel Avenue South 2860 Middletown,, NJ 07748 2861 USA 2863 Phone: +1 732 420 xxxx 2864 Email: kld@att.com