idnits 2.17.1 draft-morton-ippm-initial-registry-00.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 -- The document date (July 6, 2015) is 3207 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 2664, but no explicit reference was found in the text == Unused Reference: 'RFC4737' is defined on line 2678, but no explicit reference was found in the text == Unused Reference: 'Brow00' is defined on line 2698, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-lmap-framework' is defined on line 2701, but no explicit reference was found in the text == Unused Reference: 'RFC4148' is defined on line 2714, but no explicit reference was found in the text == Unused Reference: 'RFC5472' is defined on line 2720, but no explicit reference was found in the text == Unused Reference: 'RFC5477' is defined on line 2724, but no explicit reference was found in the text == Unused Reference: 'RFC6248' is defined on line 2731, 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 (~~), 9 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: January 7, 2016 UC3M 6 P. Eardley 7 BT 8 K. D'Souza 9 AT&T Labs 10 July 6, 2015 12 Initial Performance Metric Registry Entries 13 draft-morton-ippm-initial-registry-00 15 Abstract 17 This memo defines the Initial Entries for the Performance Metrics 18 Registry. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on January 7, 2016. 43 Copyright Notice 45 Copyright (c) 2015 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 61 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 3. Registry Categories and Columns . . . . . . . . . . . . . . . 8 63 4. UDP Round-trip Latency Registry Entry . . . . . . . . . . . . 9 64 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 9 65 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 9 66 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 9 67 4.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 9 68 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 9 69 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 9 70 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 9 71 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 10 72 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 11 73 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 11 74 4.3.2. Packet Generation Stream . . . . . . . . . . . . . . 11 75 4.3.3. Traffic Filtering (observation) Details . . . . . . . 12 76 4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 12 77 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 12 78 4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 13 79 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 13 80 4.4.1. Type/Value (two diff terms used) . . . . . . . . . . 13 81 4.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 13 82 4.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 14 83 4.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 14 84 4.5. Administrative items . . . . . . . . . . . . . . . . . . 15 85 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 15 86 4.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 15 87 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 15 88 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 15 89 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 15 90 5. Packet Delay Variation Registry Entry . . . . . . . . . . . . 15 91 5.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 15 92 5.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 15 93 5.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 15 94 5.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 16 95 5.1.4. Description . . . . . . . . . . . . . . . . . . . . . 16 97 5.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 16 98 5.2.1. Reference Definition . . . . . . . . . . . . . . . . 16 99 5.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 16 100 5.3. Method of Measurement . . . . . . . . . . . . . . . . . . 17 101 5.3.1. Reference Method . . . . . . . . . . . . . . . . . . 17 102 5.3.2. Packet Generation Stream . . . . . . . . . . . . . . 17 103 5.3.3. Traffic Filtering (observation) Details . . . . . . . 17 104 5.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 18 105 5.3.5. Run-time Parameters and Data Format . . . . . . . . . 18 106 5.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 18 107 5.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 18 108 5.4.1. Type/Value (two diff terms used) . . . . . . . . . . 18 109 5.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 19 110 5.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 20 111 5.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 20 112 5.5. Administrative items . . . . . . . . . . . . . . . . . . 20 113 5.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 20 114 5.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 20 115 5.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 20 116 5.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 20 117 5.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 21 118 6. DNS Response Latency Registry Entry . . . . . . . . . . . . . 21 119 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 21 120 6.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 21 121 6.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 21 122 6.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 21 123 6.1.4. Description . . . . . . . . . . . . . . . . . . . . . 21 124 6.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 21 125 6.2.1. Reference Definition . . . . . . . . . . . . . . . . 22 126 6.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 22 127 6.3. Method of Measurement . . . . . . . . . . . . . . . . . . 24 128 6.3.1. Reference Method . . . . . . . . . . . . . . . . . . 24 129 6.3.2. Packet Generation Stream . . . . . . . . . . . . . . 25 130 6.3.3. Traffic Filtering (observation) Details . . . . . . . 25 131 6.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 25 132 6.3.5. Run-time Parameters and Data Format . . . . . . . . . 25 133 6.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 26 134 6.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 26 135 6.4.1. Type/Value (two diff terms used) . . . . . . . . . . 27 136 6.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 27 137 6.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 28 138 6.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 28 139 6.5. Administrative items . . . . . . . . . . . . . . . . . . 28 140 6.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 28 141 6.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 28 142 6.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 28 143 6.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 28 144 6.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 28 146 7. UDP Poisson One-way Delay Registry Entries . . . . . . . . . 29 147 7.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 29 148 7.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 29 149 7.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 29 150 7.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 29 151 7.1.4. Description . . . . . . . . . . . . . . . . . . . . . 30 152 7.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 30 153 7.2.1. Reference Definition . . . . . . . . . . . . . . . . 30 154 7.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 30 155 7.3. Method of Measurement . . . . . . . . . . . . . . . . . . 31 156 7.3.1. Reference Method . . . . . . . . . . . . . . . . . . 31 157 7.3.2. Packet Generation Stream . . . . . . . . . . . . . . 31 158 7.3.3. Traffic Filtering (observation) Details . . . . . . . 32 159 7.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 32 160 7.3.5. Run-time Parameters and Data Format . . . . . . . . . 32 161 7.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 33 162 7.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 33 163 7.4.1. Type/Value (two diff terms used) . . . . . . . . . . 33 164 7.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 33 165 7.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 35 166 7.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 35 167 7.5. Administrative items . . . . . . . . . . . . . . . . . . 36 168 7.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 36 169 7.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 36 170 7.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 36 171 7.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 36 172 7.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 36 173 8. UDP Periodic One-way Delay Registry Entries . . . . . . . . . 36 174 8.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 36 175 8.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 36 176 8.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 37 177 8.1.3. URI and URL . . . . . . . . . . . . . . . . . . . . . 37 178 8.1.4. Description . . . . . . . . . . . . . . . . . . . . . 37 179 8.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 37 180 8.2.1. Reference Definition . . . . . . . . . . . . . . . . 37 181 8.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 38 182 8.3. Method of Measurement . . . . . . . . . . . . . . . . . . 39 183 8.3.1. Reference Method . . . . . . . . . . . . . . . . . . 39 184 8.3.2. Packet Generation Stream . . . . . . . . . . . . . . 39 185 8.3.3. Traffic Filtering (observation) Details . . . . . . . 40 186 8.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 40 187 8.3.5. Run-time Parameters and Data Format . . . . . . . . . 40 188 8.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 41 189 8.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 41 190 8.4.1. Type/Value (two diff terms used) . . . . . . . . . . 41 191 8.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 41 192 8.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 43 193 8.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 43 195 8.5. Administrative items . . . . . . . . . . . . . . . . . . 43 196 8.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 43 197 8.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 43 198 8.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 43 199 8.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 44 200 8.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 44 201 9. partly BLANK Registry Entry . . . . . . . . . . . . . . . . . 44 202 9.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 44 203 9.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 44 204 9.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 44 205 9.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . . 44 206 9.1.4. Description . . . . . . . . . . . . . . . . . . . . . 44 207 9.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 44 208 9.2.1. Reference Definition . . . . . . . . . . . . . . . . 44 209 9.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 45 210 9.3. Method of Measurement . . . . . . . . . . . . . . . . . . 46 211 9.3.1. Reference Method . . . . . . . . . . . . . . . . . . 46 212 9.3.2. Packet Generation Stream . . . . . . . . . . . . . . 46 213 9.3.3. Traffic Filtering (observation) Details . . . . . . . 46 214 9.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 46 215 9.3.5. Run-time Parameters and Data Format . . . . . . . . . 46 216 9.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 47 217 9.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 47 218 9.4.1. Type/Value (two diff terms used) . . . . . . . . . . 47 219 9.4.2. Data Format . . . . . . . . . . . . . . . . . . . . . 47 220 9.4.3. Reference . . . . . . . . . . . . . . . . . . . . . . 47 221 9.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 47 222 9.5. Administrative items . . . . . . . . . . . . . . . . . . 47 223 9.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 47 224 9.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . . 47 225 9.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 48 226 9.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 48 227 9.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 48 228 10. BLANK Registry Entry . . . . . . . . . . . . . . . . . . . . 48 229 10.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . 48 230 10.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . 48 231 10.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 48 232 10.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 48 233 10.1.4. Description . . . . . . . . . . . . . . . . . . . . 48 234 10.2. Metric Definition . . . . . . . . . . . . . . . . . . . 48 235 10.2.1. Reference Definition . . . . . . . . . . . . . . . . 49 236 10.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 49 237 10.3. Method of Measurement . . . . . . . . . . . . . . . . . 49 238 10.3.1. Reference Method . . . . . . . . . . . . . . . . . . 49 239 10.3.2. Packet Generation Stream . . . . . . . . . . . . . . 49 240 10.3.3. Traffic Filtering (observation) Details . . . . . . 49 241 10.3.4. Sampling Distribution . . . . . . . . . . . . . . . 49 242 10.3.5. Run-time Parameters and Data Format . . . . . . . . 49 243 10.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . 49 244 10.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 50 245 10.4.1. Type/Value (two diff terms used) . . . . . . . . . . 50 246 10.4.2. Data Format . . . . . . . . . . . . . . . . . . . . 50 247 10.4.3. Reference . . . . . . . . . . . . . . . . . . . . . 50 248 10.4.4. Metric Units . . . . . . . . . . . . . . . . . . . . 50 249 10.5. Administrative items . . . . . . . . . . . . . . . . . . 50 250 10.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 50 251 10.5.2. Requestor (keep?) . . . . . . . . . . . . . . . . . 50 252 10.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 50 253 10.5.4. Revision Date . . . . . . . . . . . . . . . . . . . 50 254 10.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 50 255 11. Example RTCP-XR Registry Entry . . . . . . . . . . . . . . . 51 256 11.1. Registry Indexes . . . . . . . . . . . . . . . . . . . . 51 257 11.1.1. Identifier . . . . . . . . . . . . . . . . . . . . . 51 258 11.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 51 259 11.1.3. URI . . . . . . . . . . . . . . . . . . . . . . . . 51 260 11.1.4. Status . . . . . . . . . . . . . . . . . . . . . . . 51 261 11.1.5. Requestor . . . . . . . . . . . . . . . . . . . . . 51 262 11.1.6. Revision . . . . . . . . . . . . . . . . . . . . . . 51 263 11.1.7. Revision Date . . . . . . . . . . . . . . . . . . . 51 264 11.1.8. Description . . . . . . . . . . . . . . . . . . . . 51 265 11.1.9. Reference Specification(s) . . . . . . . . . . . . . 52 266 11.2. Metric Definition . . . . . . . . . . . . . . . . . . . 52 267 11.2.1. Reference Definition . . . . . . . . . . . . . . . . 52 268 11.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 52 269 11.3. Method of Measurement . . . . . . . . . . . . . . . . . 53 270 11.3.1. Reference Method . . . . . . . . . . . . . . . . . . 53 271 11.3.2. Stream Type and Stream Parameters . . . . . . . . . 53 272 11.3.3. Output Type and Data Format . . . . . . . . . . . . 53 273 11.3.4. Metric Units . . . . . . . . . . . . . . . . . . . . 53 274 11.3.5. Run-time Parameters and Data Format . . . . . . . . 54 275 11.4. Comments and Remarks . . . . . . . . . . . . . . . . . . 55 276 12. Security Considerations . . . . . . . . . . . . . . . . . . . 55 277 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 278 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 279 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 280 15.1. Normative References . . . . . . . . . . . . . . . . . . 57 281 15.2. Informative References . . . . . . . . . . . . . . . . . 58 282 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 284 1. Introduction 286 Note: Efforts to synchronize structure and terminology with 287 [I-D.ietf-ippm-metric-registry] will likely be incomplete until both 288 drafts are stable. 290 This memo defines the Initial set of entries for the Performance 291 Metric Registry. The registry will contain Active Performance 292 Metrics, especially those defined in RFCs prepared in the IP 293 Performance Metrics (IPPM) Working Group of the IETF, according to 294 their framework [RFC2330]. Three aspects make IPPM metric 295 registration difficult: (1) Use of the Type-P notion to allow users 296 to specify their own packet types. (2) Use of Flexible input 297 variables, called Parameters in IPPM definitions, some which 298 determine the quantity measured and others which should not be 299 specified until execution of the measurement. (3) Allowing 300 flexibility in choice of statistics to summarize the results on a 301 stream of measurement packets. This memo uses terms and definitions 302 from the IPPM literature, primarily [RFC2330], and the reader is 303 assumed familiar with them or may refer questions there as necessary. 305 Although there are several standard templates for organizing 306 specifications of performance metrics (see [RFC2679] for an example 307 of the traditional IPPM template, based to large extent on the 308 Benchmarking Methodology Working Group's traditional template in 309 [RFC1242], and see [RFC6390] for a similar template), none of these 310 templates were intended to become the basis for the columns of an 311 IETF-wide registry of metrics. While examinating aspects of metric 312 specifications which need to be registered, it was clear that none of 313 the existing metric templates fully satisfies the particular needs of 314 a registry. 316 2. Scope 318 [I-D.ietf-ippm-metric-registry] defines the overall structure for a 319 Performance Metric Registry and provides guidance for the process to 320 examine proposed metrics and maitain Registered Metrics. 322 This document defines the initial set of Performance Metrics Registry 323 entries; all are active metrics, or those where the packets measured 324 have been specially generated for the purpose. 326 A row in the registry corresponds to one Registered Performance 327 Metric, with entries in the various columns specifying the metric. 329 As discussed in [I-D.ietf-ippm-metric-registry], each entry (row) 330 must be tightly defined; the definition must leave open only a few 331 parameters that do not change the fundamental nature of the 332 measurement (such as source and destination addresses), and so 333 promotes comparable results across independent implementations. 334 Also, each registered entry must be based on existing reference RFCs 335 (or other standards) for performance metrics, and must be 336 operationally useful and have significant industry interest. This is 337 ensured by expert review for every entry before IANA action. 339 3. Registry Categories and Columns 341 This section defines the categories and columns of the registry. 342 Below, categories are described at the 3.x heading level, and columns 343 are at the 3.x.y heading level. The Figure below illustrates this 344 organization. An entry (row) therefore gives a complete description 345 of a Registered Metric. 347 Each column serves as a check-list item and helps to avoid omissions 348 during registration and expert review. In some cases an entry (row) 349 may have some columns without specific entries, marked Not Applicable 350 (NA). 352 Registry Categories and Columns, shown as 353 Category 354 ------------------ 355 Column | Column | 357 Summary 358 -------------------------------- 359 ID | Name | URIs | Description | 361 Metric Definition 362 ----------------------------------------- 363 Reference Definition | Fixed Parameters | 365 Method of Measurement 366 --------------------------------------------------------------- 367 Reference | Packet | Traffic | Sampling | Run-time | Role | 368 Method | Generation | Filter | dist. | Param | | 369 | Stream | 370 Output 371 ...----------------------------- 372 | Type | Reference | Units | 373 | | Definition | | 375 Administrative information 376 ---------------------------------- 377 Status |Request | Rev | Rev.Date | 379 Comments and Remarks 380 -------------------- 382 4. UDP Round-trip Latency Registry Entry 384 This section gives an initial registry entry for the UDP Round-trip 385 Latency. 387 Note: If each Registry entry should only produce a "raw" output or a 388 statistical summary, then the "Output" Category can be split and this 389 section can become two closely-related metrics. 391 4.1. Summary 393 This category includes multiple indexes to the registry entries, the 394 element ID and metric name. 396 4.1.1. ID (Identifier) 398 400 4.1.2. Name 402 404 Act_IP_UDP_Round-trip_Delay_Raw_95th-percentile_Poisson 406 URL: ?? 408 4.1.3. URI 410 URI: Prefix urn:ietf:params:performance:metric... 412 4.1.4. Description 414 This metric assesses the delay of a stream of packets exchanged 415 between two hosts (or measurement points), and reports the Round-trip 416 delay for all successfully exchanged packets and the 95th percentile 417 of their conditional delay distribution. 419 4.2. Metric Definition 421 This category includes columns to prompt the entry of all necessary 422 details related to the metric definition, including the RFC reference 423 and values of input factors, called fixed parameters. 425 4.2.1. Reference Definition 427 428 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 429 Metric for IPPM", RFC 2681, September 1999. 431 [RFC2681] 433 435 Section 2.4 of [RFC2681] provides the reference definition of the 436 singleton (single value) Round-trip delay metric. Section 3.4 of 437 [RFC2681] provides the reference definition expanded to cover a 438 multi-value sample. Note that terms such as singleton and sample are 439 defined in Section 11 of [RFC2330]. 441 Note that although the definition of "Round-trip-Delay between Src 442 and Dst at T" is directionally ambiguous in the text, this metric 443 tightens the definition further to recognize that the host in the 444 "Src" role will send the first packet to "Dst", and ultimately 445 receive the corresponding return packet from "Dst" (when neither are 446 lost). 448 4.2.2. Fixed Parameters 450 454 Type-P: 456 o IPv4 header values: 458 * DSCP: set to 0 460 * TTL set to 255 462 * Protocol: Set to 17 (UDP) 464 o UDP header values: 466 * Checksum: the checksum must be calculated 468 o Payload 470 * Sequence number: 8-byte integer 472 * Timestamp: 8 byte integer. Expressed as 64-bit NTP timestamp 473 as per section 6 of RFC 5905 [RFC5905] 475 * No padding (total of 9 bytes) 477 Timeout, Tmax: 3 seconds 479 4.3. Method of Measurement 481 This category includes columns for references to relevant sections of 482 the RFC(s) and any supplemental information needed to ensure an 483 unambiguous methods for implementations. 485 4.3.1. Reference Method 487 490 The methodology for this metric is defined as Type-P-Round-trip- 491 Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section 492 3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under 493 Fixed Parameters. 495 The method requires sequence numbers or other send-order information 496 to be retained at the Src or included with each packet to dis- 497 ambiguate packet reordering if it occurs. Sequence number is part of 498 the payload described under Fixed Parameters. 500 Refer to Section 4.4 of [RFC6673] for expanded discussion of the 501 instruction to "send a Type-P packet back to the Src as quickly as 502 possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of 503 [RFC6673] presents additional requirements which shall be included in 504 the method of measurement for this metric. 506 4.3.2. Packet Generation Stream 508 This section gives the details of the packet traffic which is the 509 basis for measurement. In IPPM metrics, this is called the Stream, 510 and can easily be dscribed by providing the list of stream 511 parameters. 513 515 Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to 516 generate Poisson sampling intervals. the reciprocal of lambda is the 517 average packet rate, thus the Run-time Parameter is 1/lambda. 519 >>> Check with Sam, most likely it is this... 521 Method 3 is used, where given a start time (Run-time Parameter), the 522 subsequent send times are all computed prior to measurement by 523 computing the pseudo-random distribution of inter-packet send times, 524 (truncating the distribution as specified in the Run-time 525 Parameters), and the Src sends each packet at the computed times. 527 4.3.3. Traffic Filtering (observation) Details 529 The measured results based on a filtered version of the packets 530 observed, and this section provides the filter details (when 531 present). 533
. 535 NA 537 4.3.4. Sampling Distribution 539 542 NA 544 4.3.5. Run-time Parameters and Data Format 546 Run-time Parameters are input factors that must be determined, 547 configured into the measurement system, and reported with the results 548 for the context to be complete. 550 552 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 553 value for IPv6) 555 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 556 value for IPv6) 558 o T0, a time (start of measurement interval, 128-bit NTP Date 559 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 560 start time is unspecified and Tf is to be interpreted as the 561 Duration of the measurement interval. 563 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 564 see section 6 of [RFC5905]), interpreted as the Duration of the 565 measurement interval. 567 o 1/lambda, average packet rate (for Poisson Streams). (1/lambda = 568 1 packet per second, if fixed) 570 o Upper limit on Poisson distribution (values above this limit will 571 be clipped and set to the limit value). (if fixed, Upper limit = 572 30 seconds.) 574 The format for 1/lambda and Upper limit of Poisson Dist. are the 575 short format in [RFC5905] (32 bits) and is as follows: the first 16 576 bits represent the integer number of seconds; the next 16 bits 577 represent the fractional part of a second. 579 >>> should Poisson run-time params be fixed instead? probably yes if 580 modeling a specific version of MBA tests. 582 4.3.6. Roles 584 586 Src - launches each packet and waits for return transmissions from 587 Dst. 589 Dst - waits for each packet from Src and sends a return packet to 590 Src. 592 4.4. Output 594 This category specifies all details of the Output of measurements 595 using the metric. 597 4.4.1. Type/Value (two diff terms used) 599 601 Raw -- for each packet sent, pairs of values. 603 Percentile -- for the conditional distribution of all packets with a 604 valid value of Round-trip delay (undefined delays are excluded), a 605 single value corresponding to the 95th percentile. 607 4.4.2. Data Format 609 611 For all outputs --- 613 o T0, a time (start of measurement interval, 128-bit NTP Date 614 Format, see section 6 of [RFC5905]) 616 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 617 see section 6 of [RFC5905]) 619 Raw -- for each packet sent, pairs of values as follows: 621 o T, the time when the packet was sent from Src, 128-bit NTP Date 622 Format, see section 6 of [RFC5905]) 624 o dT, a value of Round-trip delay, format is *similar to* the 32-bit 625 short NTP Time format in Section 6 of [RFC5905] and is as follows: 626 the first 16 bits represent the *signed* integer number of 627 seconds; the next 16 bits represent the fractional part of a 628 second. 630 o dT is undefined when the packet is not received at Src in waiting 631 time Tmxax seconds (need undefined code) 633 Percentile -- for the conditional distribution of all packets with a 634 valid value of Round-trip delay (undefined delays are excluded), a 635 single value as follows: 637 See section 4.1 of [RFC3393] for details on the conditional 638 distribution to exclude undefined values of delay, and Section 5 of 639 [RFC6703] for background on this analysis choice. 641 See section 4.3 of [RFC3393] for details on the percentile statistic 642 (where Round-trip delay should be substituted for "ipdv"). 644 The percentile = 95. 646 Data format is a 32-bit signed value, *similar to* the 32-bit short 647 NTP Time format in Section 6 of [RFC5905] and is as follows: the 648 first 16 bits represent the *signed* integer number of seconds; the 649 next 16 bits represent the fractional part of a second. 651 4.4.3. Reference 653 655 See the Data Format column for references. 657 4.4.4. Metric Units 659 . 662 Round-trip Delay, dT, is expressed in seconds. 664 The 95th Percentile of Round-trip Delay is expressed in seconds. 666 4.5. Administrative items 668 4.5.1. Status 670 672 4.5.2. Requestor (keep?) 674 name or RFC, etc. 676 4.5.3. Revision 678 1.0 680 4.5.4. Revision Date 682 YYYY-MM-DD 684 4.6. Comments and Remarks 686 Additional (Informational) details for this entry 688 5. Packet Delay Variation Registry Entry 690 This section gives an initial registry entry for a Packet Delay 691 Variation metric. 693 Note: If each Registry entry should only produce a "raw" output or a 694 statistical summary, then the "Output" Category can be split and this 695 section can become two closely-related metrics. 697 5.1. Summary 699 This category includes multiple indexes to the registry entries, the 700 element ID and metric name. 702 704 5.1.1. ID (Identifier) 706 708 5.1.2. Name 710 712 Act_IP-UDP-One-way-pdv-95th-percentile-Poisson 713 URL: ?? 715 5.1.3. URI 717 URI: Prefix urn:ietf:params:performance:metric 719 5.1.4. Description 721 An assessment of packet delay variation with respect to the minimum 722 delay observed on the stream. 724 5.2. Metric Definition 726 This category includes columns to prompt the entry of all necessary 727 details related to the metric definition, including the RFC reference 728 and values of input factors, called fixed parameters. 730 5.2.1. Reference Definition 732 734 Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP 735 Performance Metrics", RFC 2330, May 1998. [RFC2330] 737 Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric 738 for IP Performance Metrics (IPPM)", RFC 3393, November 2002. 739 [RFC3393] 741 Morton, A. and B. Claise, "Packet Delay Variation Applicability 742 Statement", RFC 5481, March 2009. [RFC5481] 744 Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time 745 Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, 746 June 2010.[RFC5905] 748 750 See sections 2.4 and 3.4 of [RFC3393]. Singleton delay differences 751 measured are referred to by the variable name "ddT". 753 5.2.2. Fixed Parameters 755 758 o F, a selection function defining unambiguously the packets from 759 the stream selected for the metric. See section 4.2 of [RFC5481] 760 for the PDV form. 762 o L, a packet length in bits. L = 200 bits. 764 o Tmax, a maximum waiting time for packets to arrive at Dst, set 765 sufficiently long to disambiguate packets with long delays from 766 packets that are discarded (lost). Tmax = 3 seconds. 768 o Type-P, as defined in [RFC2330], which includes any field that may 769 affect a packet's treatment as it traverses the network. The 770 packets are IP/UDP, with DSCP = 0 (BE). 772 5.3. Method of Measurement 774 This category includes columns for references to relevant sections of 775 the RFC(s) and any supplemental information needed to ensure an 776 unambiguous methods for implementations. 778 5.3.1. Reference Method 780 783 See section 2.6 and 3.6 of [RFC3393] for singleton elements. 785 5.3.2. Packet Generation Stream 787 789 Poisson distributed as described in [RFC2330], with the following 790 Parameters. 792 o lambda, a rate in reciprocal seconds (for Poisson Streams). 793 lambda = 1 packet per second 795 o Upper limit on Poisson distribution (values above this limit will 796 be clipped and set to the limit value). Upper limit = 30 seconds. 798 5.3.3. Traffic Filtering (observation) Details 800 . 804 NA 806 5.3.4. Sampling Distribution 808 811 NA 813 5.3.5. Run-time Parameters and Data Format 815 . 817 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 818 value for IPv6) 820 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 821 value for IPv6) 823 o T, a time (start of measurement interval, 128-bit NTP Date Format, 824 see section 6 of [RFC5905]). When T0 is "all-zeros", a start time 825 is unspecified and Tf is to be interpreted as the Duration of the 826 measurement interval. 828 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 829 see section 6 of [RFC5905]), interpreted as the Duration of the 830 measurement interval. 832 5.3.6. Roles 834 836 Src - the host that sends the stream of packets. 838 Dst - the host that receives the stream of packets. 840 5.4. Output 842 This category specifies all details of the Output of measurements 843 using the metric. 845 5.4.1. Type/Value (two diff terms used) 847 849 Raw -- for each packet sent, pairs of values. 851 Percentile -- for the conditional distribution of all packets with a 852 valid value of one-way delay (undefined delays are excluded), a 853 single value corresponding to the 95th percentile of the singletons, 854 ddT. 856 5.4.2. Data Format 858 860 For all Output types 862 o T, a time (start of measurement interval, 128-bit NTP Date Format, 863 see section 6 of [RFC5905]) 865 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 866 see section 6 of [RFC5905]) 868 Raw - 870 o T1, the wire time of the first packet in a pair, measured at 871 MP(Src) as it leaves for Dst (64-bit NTP Timestamp Format, see 872 section 6 of [RFC5905]). 874 o T2, the wire time of the second packet in a pair, measured at 875 MP(Src) as it leaves for Dst (64-bit NTP Timestamp Format, see 876 section 6 of [RFC5905]). 878 o I(i),I(i+1), i >=0, pairs of times which mark the beginning and 879 ending of the intervals in which the packet stream from which the 880 measurement is taken occurs. Here, I(0) = T0 and assuming that n 881 is the largest index, I(n) = Tf (pairs of 64-bit NTP Timestamp 882 Format, see section 6 of [RFC5905]). 884 o When the one-way delay of a packet in the calculation pair for ddT 885 is undefined, then ddT is undefined for that pair. 887 Percentile -- for the conditional distribution of all packets with a 888 valid value of one-way delay (undefined delays are excluded), a 889 single value as follows: 891 See section 4.1 of [RFC3393] for details on the conditional 892 distribution to exclude undefined values of delay, and Section 5 of 893 [RFC6703] for background on this analysis choice. 895 See section 4.3 of [RFC3393] for details on the percentile statistic 896 (where pdv should be substituted for "ipdv"). 898 The percentile = 95. 900 Data format is a 32-bit signed floating point value, *similar to* the 901 32-bit short NTP Time format in Section 6 of [RFC5905] and is as 902 follows: the first 16 bits represent the *signed* integer number of 903 seconds; the next 16 bits represent the fractional part of a second. 905 5.4.3. Reference 907 909 see Data Format column. 911 5.4.4. Metric Units 913 . 916 See section 3.3 of [RFC3393] for singleton elements, ddT. The units 917 are seconds, and the same units are used for 95th percentile. 919 [RFC2330] recommends that when a time is given, it will be expressed 920 in UTC. 922 The timestamp format (for T, Tf, etc.) is the same as in [RFC5905] 923 (64 bits) and is as follows: the first 32 bits represent the unsigned 924 integer number of seconds elapsed since 0h on 1 January 1900; the 925 next 32 bits represent the fractional part of a second that has 926 elapsed since then. 928 5.5. Administrative items 930 5.5.1. Status 932 934 5.5.2. Requestor (keep?) 936 938 5.5.3. Revision 940 1.0 942 5.5.4. Revision Date 944 YYYY-MM-DD 946 5.6. Comments and Remarks 948 950 Lost packets represent a challenge for delay variation metrics. See 951 section 4.1 of [RFC3393] and the delay variation applicability 952 statement[RFC5481] for extensive analysis and comparison of PDV and 953 an alternate metric, IPDV. 955 6. DNS Response Latency Registry Entry 957 This section gives an initial registry entry for DNS Response 958 Latency. RFC 2681 [RFC2681] defines a Round-trip delay metric. We 959 build on that metric by specifying several of the input parameters to 960 precisely define a metric for measuring DNS latency. 962 6.1. Summary 964 This category includes multiple indexes to the registry entries, the 965 element ID and metric name. 967 969 6.1.1. ID (Identifier) 971 973 6.1.2. Name 975 977 URL: ?? 979 6.1.3. URI 981 URI: Prefix urn:ietf:params:performance:metric 983 6.1.4. Description 985 This metric assesses the response time, the interval from the query 986 transmission to the response. 988 6.2. Metric Definition 990 This category includes columns to prompt the entry of all necessary 991 details related to the metric definition, including the RFC reference 992 and values of input factors, called fixed parameters. 994 6.2.1. Reference Definition 996 998 Mockapetris, P., "Domain names - implementation and specification", 999 STD 13, RFC 1035, November 1987. (and updates) 1001 [RFC1035] 1003 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 1004 Metric for IPPM", RFC 2681, September 1999. 1006 [RFC2681] 1008 1010 Section 2.4 of [RFC2681] provides the reference definition of the 1011 singleton (single value) Round-trip delay metric. Section 3.4 of 1012 [RFC2681] provides the reference definition expanded to cover a 1013 multi-value sample. Note that terms such as singleton and sample are 1014 defined in Section 11 of [RFC2330]. 1016 For DNS Response Latency, the entities in [RFC1035] must be mapped to 1017 [RFC2681]. The Local Host with its User Program and Resolver take 1018 the role of "Src", and the Foreign Name Server takes the role of 1019 "Dst". 1021 Note that although the definition of "Round-trip-Delay between Src 1022 and Dst at T" is directionally ambiguous in the text, this metric 1023 tightens the definition further to recognize that the host in the 1024 "Src" role will send the first packet to "Dst", and ultimately 1025 receive the corresponding return packet from "Dst" (when neither are 1026 lost). 1028 6.2.2. Fixed Parameters 1030 1034 Type-P: 1036 o IPv4 header values: 1038 * DSCP: set to 0 1040 * TTL set to 255 1041 * Protocol: Set to 17 (UDP) 1043 o UDP header values: 1045 * Source port: 53 1047 * Destination port: 53 1049 * Checksum: the checksum must be calculated 1051 o Payload: The payload contains a DNS message as defined in RFC 1035 1052 [RFC1035] with the following values: 1054 * The DNS header section contains: 1056 + QR: set to 0 (Query) 1058 + OPCODE: set to 0 (standard query) 1060 + AA: not set 1062 + TC: not set 1064 + RD: set to one (recursion desired) 1066 + RA: not set 1068 + RCODE: not set 1070 + QDCOUNT: set to one (only one entry) 1072 + ANCOUNT: not set 1074 + NSCOUNT: not set 1076 + ARCOUNT: not set 1078 * The Question section contains: 1080 + QNAME: the FQDN provided as input for the test 1082 + QTYPE: the query type provided as input for the test 1084 + QCLASS: set to IN 1086 * The other sections do not contain any Resource Records. 1088 Observation: reply packets will contain a DNS response and may 1089 contain RRs. 1091 Timeout: Tmax = 5 seconds (to help disambiguate queries) 1093 6.3. Method of Measurement 1095 This category includes columns for references to relevant sections of 1096 the RFC(s) and any supplemental information needed to ensure an 1097 unambiguous methods for implementations. 1099 6.3.1. Reference Method 1101 1104 The methodology for this metric is defined as Type-P-Round-trip- 1105 Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section 1106 3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under 1107 Fixed Parameters. 1109 The method requires sequence numbers or other send-order information 1110 to be retained at the Src or included with each packet to dis- 1111 ambiguate packet reordering if it occurs. Sequence number is part of 1112 the payload described under Fixed Parameters. 1114 DNS Messages bearing Queries provide for random ID Numbers, so more 1115 than one query may be launched while a previous request is 1116 outstanding when the ID Number is used. 1118 IF a DNS response does not arrive within Tmax, the result is 1119 undefined. The Message ID SHALL be used to disambiguate the 1120 successive queries. 1122 >>> This would require support of ID generation and population in the 1123 Message. An alternative would be to use a random Source port on the 1124 Query Message, but we would choose ONE before proceding. 1126 Refer to Section 4.4 of [RFC6673] for expanded discussion of the 1127 instruction to "send a Type-P packet back to the Src as quickly as 1128 possible" in Section 2.6 of RFC 2681 [RFC2681]. Section 8 of 1129 [RFC6673] presents additional requirements which shall be included in 1130 the method of measurement for this metric. 1132 6.3.2. Packet Generation Stream 1134 This section gives the details of the packet traffic which is the 1135 basis for measurement. In IPPM metrics, this is called the Stream, 1136 and can easily be dscribed by providing the list of stream 1137 parameters. 1139 1141 Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to 1142 generate Poisson sampling intervals. the reciprocal of lambda is the 1143 average packet rate, thus the Run-time Parameter is 1/lambda. 1145 >>> Check with Sam, most likely it is this... 1147 Method 3 is used, where given a start time (Run-time Parameter), the 1148 subsequent send times are all computed prior to measurement by 1149 computing the pseudo-random distribution of inter-packet send times, 1150 (truncating the distribution as specified in the Run-time 1151 Parameters), and the Src sends each packet at the computed times. 1153 6.3.3. Traffic Filtering (observation) Details 1155 The measured results based on a filtered version of the packets 1156 observed, and this section provides the filter details (when 1157 present). 1159
. 1161 NA 1163 6.3.4. Sampling Distribution 1165 1168 NA 1170 6.3.5. Run-time Parameters and Data Format 1172 Run-time Parameters are input factors that must be determined, 1173 configured into the measurement system, and reported with the results 1174 for the context to be complete. 1176 1178 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1179 value for IPv6) 1181 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1182 value for IPv6) 1184 o T0, a time (start of measurement interval, 128-bit NTP Date 1185 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1186 start time is unspecified and Tf is to be interpreted as the 1187 Duration of the measurement interval. 1189 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1190 see section 6 of [RFC5905]), interpreted as the Duration of the 1191 measurement interval. 1193 o 1/lambda, average packet rate (for Poisson Streams). (1/lambda = 1194 0.1 packet per second, if fixed) 1196 o Upper limit on Poisson distribution (values above this limit will 1197 be clipped and set to the limit value). (if fixed, Upper limit = 1198 300 seconds.) 1200 o ID, the 16-bit identifier assigned by the program that generates 1201 the query, and which must vary in successive queries, see 1202 Section 4.1.1 of [RFC1035]. This identifier is copied into the 1203 corresponding reply and can be used by the requester to match-up 1204 replies to outstanding queries. 1206 The format for 1/lambda and Upper limit of Poisson Dist. are the 1207 short format in [RFC5905] (32 bits) and is as follows: the first 16 1208 bits represent the integer number of seconds; the next 16 bits 1209 represent the fractional part of a second. 1211 >>> should Poisson run-time params be fixed instead? probably yes if 1212 modeling a specific version of MBA tests. 1214 6.3.6. Roles 1216 1218 Src - launches each packet and waits for return transmissions from 1219 Dst. 1221 Dst - waits for each packet from Src and sends a return packet to 1222 Src. 1224 6.4. Output 1226 This category specifies all details of the Output of measurements 1227 using the metric. 1229 6.4.1. Type/Value (two diff terms used) 1231 1233 For all output types: 1235 o T0, a time (start of measurement interval, 128-bit NTP Date 1236 Format, see section 6 of [RFC5905]) 1238 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1239 see section 6 of [RFC5905]) 1241 Raw -- for each packet sent, pairs of values. 1243 >>> and the status of the response, only assigning values to 1244 successful query-response pairs. 1246 Percentile -- for the conditional distribution of all packets with a 1247 valid value of Round-trip delay (undefined delays are excluded), a 1248 single value corresponding to the 95th percentile. 1250 6.4.2. Data Format 1252 1254 Raw -- for each packet sent, pairs of values as follows: 1256 o T, the time when the packet was sent from Src, 128-bit NTP Date 1257 Format, see section 6 of [RFC5905]) 1259 o dT, a value of Round-trip delay, format is *similar to* the 32-bit 1260 short NTP Time format in Section 6 of [RFC5905] and is as follows: 1261 the first 16 bits represent the *signed* integer number of 1262 seconds; the next 16 bits represent the fractional part of a 1263 second. 1265 o dT is undefined when the packet is not received at Src in waiting 1266 time Tmxax seconds (need undefined code for no-response or un- 1267 successful response) 1269 Percentile -- for the conditional distribution of all packets with a 1270 valid value of Round-trip delay (undefined delays are excluded), a 1271 single value as follows: 1273 See section 4.1 of [RFC3393] for details on the conditional 1274 distribution to exclude undefined values of delay, and Section 5 of 1275 [RFC6703] for background on this analysis choice. 1277 See section 4.3 of [RFC3393] for details on the percentile statistic 1278 (where Round-trip delay should be substituted for "ipdv"). 1280 The percentile = 95. 1282 Data format is a 32-bit signed floating point value, *similar to* the 1283 32-bit short NTP Time format in Section 6 of [RFC5905] and is as 1284 follows: the first 16 bits represent the *signed* integer number of 1285 seconds; the next 16 bits represent the fractional part of a second. 1287 6.4.3. Reference 1289 1291 See the Data Format column for references. 1293 6.4.4. Metric Units 1295 . 1298 Round-trip Delay, dT, is expressed in seconds. 1300 The 95th Percentile of Round-trip Delay is expressed in seconds. 1302 6.5. Administrative items 1304 6.5.1. Status 1306 1308 6.5.2. Requestor (keep?) 1310 name or RFC, etc. 1312 6.5.3. Revision 1314 1.0 1316 6.5.4. Revision Date 1318 YYYY-MM-DD 1320 6.6. Comments and Remarks 1322 Additional (Informational) details for this entry 1324 7. UDP Poisson One-way Delay Registry Entries 1326 This section gives an initial registry entry for the UDP Poisson One- 1327 way Delay. 1329 Note: Each Registry "Name" below specifies a single registry entry, 1330 whose output format varies according to a component of the name that 1331 specifies one form of statistical summary. 1333 IANA is asked to assign a different numeric identifiers to each Name. 1334 All other column entries are the same, thus this section is proposes 1335 five closely-related registry entries. As a result, IANA is also 1336 asked to assign corresponding URIs and URLs. 1338 7.1. Summary 1340 This category includes multiple indexes to the registry entries, the 1341 element ID and metric name. 1343 7.1.1. ID (Identifier) 1345 1348 7.1.2. Name 1350 1352 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_ 1354 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Percentile95 1356 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Mean 1358 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Min 1360 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Max 1362 Act_IP_UDP_Poisson_UDP-Payload-250_One-way_Delay_Std_Dev 1364 7.1.3. URI and URL 1366 URI: Prefix urn:ietf:params:performance:metric... 1368 URL: http:\\www.iana.org\ ... 1370 7.1.4. Description 1372 This metric assesses the delay of a stream of packets exchanged 1373 between two hosts (or measurement points), and reports the 1374 One-way delay for all successfully exchanged packets 1375 based on their conditional delay distribution. 1377 7.2. Metric Definition 1379 This category includes columns to prompt the entry of all necessary 1380 details related to the metric definition, including the RFC reference 1381 and values of input factors, called fixed parameters. 1383 7.2.1. Reference Definition 1385 1387 Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric 1388 for IPPM", RFC 2679, September 1999. 1390 [RFC2679] 1392 Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC 1393 6049, January 2011. 1395 [RFC6049] 1397 1399 Section 3.4 of [RFC2679] provides the reference definition of the 1400 singleton (single value) One-way delay metric. Section 4.4 of 1401 [RFC2679] provides the reference definition expanded to cover a 1402 multi-value sample. Note that terms such as singleton and sample are 1403 defined in Section 11 of [RFC2330]. 1405 Only successful packet transfers with finite delay are included in 1406 the sample, as prescribed in section 4.1.2 of [RFC6049]. 1408 NOTE: RFC2679 will be replaced by 2679-bis on approval, see draft- 1409 ietf-ippm-2679-bis-01. 1411 7.2.2. Fixed Parameters 1413 1417 Type-P: 1419 o IPv4 header values: 1421 * DSCP: set to 0 1423 * TTL set to 255 1425 * Protocol: Set to 17 (UDP) 1427 o UDP header values: 1429 * Checksum: the checksum must be calculated 1431 o UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357] 1433 * Security features in use influence the number of Padding 1434 octets. 1436 * 250 octets total, including the TWAMP format 1438 Timeout, Tmax: 3 seconds 1440 7.3. Method of Measurement 1442 This category includes columns for references to relevant sections of 1443 the RFC(s) and any supplemental information needed to ensure an 1444 unambiguous methods for implementations. 1446 7.3.1. Reference Method 1448 1451 The methodology for this metric is defined as Type-P-One-way-Delay- 1452 Poisson-Stream in section 3.6 of [RFC2679] and section 4.6 of 1453 [RFC2679] using the Type-P and Timeout defined under Fixed 1454 Parameters. 1456 The method requires sequence numbers or other send-order information 1457 to be retained at the Src or included with each packet to dis- 1458 ambiguate packet reordering if it occurs. Sequence number is part of 1459 the TWAMP payload described under Fixed Parameters. 1461 7.3.2. Packet Generation Stream 1463 This section gives the details of the packet traffic which is the 1464 basis for measurement. In IPPM metrics, this is called the Stream, 1465 and can easily be dscribed by providing the list of stream 1466 parameters. 1468 1470 Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to 1471 generate Poisson sampling intervals. The reciprocal of lambda is the 1472 average packet rate, thus the Run-time Parameter is 1/lambda. 1474 Method 3 or equivalent SHALL used, where given a start time (Run-time 1475 Parameter), the subsequent send times are all computed prior to 1476 measurement by computing the pseudo-random distribution of inter- 1477 packet send times, (truncating the distribution as specified in the 1478 Run-time Parameters), and the Src sends each packet at the computed 1479 times. 1481 7.3.3. Traffic Filtering (observation) Details 1483 NA 1485 7.3.4. Sampling Distribution 1487 NA 1489 7.3.5. Run-time Parameters and Data Format 1491 Run-time Parameters are input factors that must be determined, 1492 configured into the measurement system, and reported with the results 1493 for the context to be complete. 1495 1497 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1498 value for IPv6) 1500 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1501 value for IPv6) 1503 o T0, a time (start of measurement interval, 128-bit NTP Date 1504 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1505 start time is unspecified and Tf is to be interpreted as the 1506 Duration of the measurement interval. 1508 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1509 see section 6 of [RFC5905]), interpreted as the Duration of the 1510 measurement interval. 1512 o 1/lambda, average packet rate (for Poisson Streams). (1/lambda = 1513 1 packet per second, if fixed) 1515 o Upper limit on Poisson distribution (values above this limit will 1516 be clipped and set to the limit value). (if fixed, Upper limit = 1517 30 seconds.) 1519 The format for 1/lambda and Upper limit of Poisson Dist. are the 1520 short format in [RFC5905] (32 bits) and is as follows: the first 16 1521 bits represent the integer number of seconds; the next 16 bits 1522 represent the fractional part of a second. 1524 >>> should Poisson run-time params be fixed instead? probably yes if 1525 modeling a specific version of tests. Note in the NAME, i.e. 1526 Poisson3.3 1528 7.3.6. Roles 1530 1532 Src - launches each packet and waits for return transmissions from 1533 Dst. This is the TWAMP Session-Sender. 1535 Dst - waits for each packet from Src and sends a return packet to 1536 Src. This is the TWAMP Session-Reflector. 1538 7.4. Output 1540 This category specifies all details of the Output of measurements 1541 using the metric. 1543 7.4.1. Type/Value (two diff terms used) 1545 1547 See subsection titles below for Types. 1549 7.4.2. Data Format 1551 1553 For all output types --- 1555 o T0, a time (start of measurement interval, 128-bit NTP Date 1556 Format, see section 6 of [RFC5905]) 1558 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1559 see section 6 of [RFC5905]) 1561 7.4.2.1. Percentile95 1563 The 95th percentile SHALL be calculated using the conditional 1564 distribution of all packets with a finite value of One-way delay 1565 (undefined delays are excluded), a single value as follows: 1567 See section 4.1 of [RFC3393] for details on the conditional 1568 distribution to exclude undefined values of delay, and Section 5 of 1569 [RFC6703] for background on this analysis choice. 1571 See section 4.3 of [RFC3393] for details on the percentile statistic 1572 (where Round-trip delay should be substituted for "ipdv"). 1574 The percentile = 95. 1576 Data format is a 32-bit signed value, *similar to* the 32-bit short 1577 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1578 first 16 bits represent the *signed* integer number of seconds; the 1579 next 16 bits represent the fractional part of a second. 1581 7.4.2.2. Mean 1583 The mean SHALL be calculated using the conditional distribution of 1584 all packets with a finite value of One-way delay (undefined delays 1585 are excluded), a single value as follows: 1587 See section 4.1 of [RFC3393] for details on the conditional 1588 distribution to exclude undefined values of delay, and Section 5 of 1589 [RFC6703] for background on this analysis choice. 1591 See section 4.2.2 of [RFC6049] for details on calculating this 1592 statistic, and 4.2.3 of [RFC6049]. 1594 Data format is a 32-bit signed value, *similar to* the 32-bit short 1595 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1596 first 16 bits represent the *signed* integer number of seconds; the 1597 next 16 bits represent the fractional part of a second. 1599 7.4.2.3. Min 1601 The minimum SHALL be calculated using the conditional distribution of 1602 all packets with a finite value of One-way delay (undefined delays 1603 are excluded), a single value as follows: 1605 See section 4.1 of [RFC3393] for details on the conditional 1606 distribution to exclude undefined values of delay, and Section 5 of 1607 [RFC6703] for background on this analysis choice. 1609 See section 4.3.2 of [RFC6049] for details on calculating this 1610 statistic, and 4.3.3 of [RFC6049]. 1612 Data format is a 32-bit signed value, *similar to* the 32-bit short 1613 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1614 first 16 bits represent the *signed* integer number of seconds; the 1615 next 16 bits represent the fractional part of a second. 1617 7.4.2.4. Max 1619 The maximum SHALL be calculated using the conditional distribution of 1620 all packets with a finite value of One-way delay (undefined delays 1621 are excluded), a single value as follows: 1623 See section 4.1 of [RFC3393] for details on the conditional 1624 distribution to exclude undefined values of delay, and Section 5 of 1625 [RFC6703] for background on this analysis choice. 1627 See section 4.3.2 of [RFC6049] for a closely related method for 1628 calculating this statistic, and 4.3.3 of [RFC6049]. The formula is 1629 as follows: 1631 Max = (FiniteDelay [j]) 1633 such that for some index, j, where 1 <= j <= N 1634 FiniteDelay[j] >= FiniteDelay[n] for all n 1636 Data format is a 32-bit signed value, *similar to* the 32-bit short 1637 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1638 first 16 bits represent the *signed* integer number of seconds; the 1639 next 16 bits represent the fractional part of a second. 1641 7.4.2.5. Std_Dev 1643 7.4.3. Reference 1645 1647 See the Data Format column for references. 1649 7.4.4. Metric Units 1651 . 1654 The of One-way Delay is expressed in seconds. 1656 The 95th Percentile of One-way Delay is expressed in seconds. 1658 7.5. Administrative items 1660 7.5.1. Status 1662 1664 7.5.2. Requestor (keep?) 1666 name or RFC, etc. 1668 7.5.3. Revision 1670 1.0 1672 7.5.4. Revision Date 1674 YYYY-MM-DD 1676 7.6. Comments and Remarks 1678 Additional (Informational) details for this entry 1680 8. UDP Periodic One-way Delay Registry Entries 1682 This section gives an initial registry entry for the UDP Periodic 1683 One-way Delay. 1685 Note: Each Registry "Name" below specifies a single registry entry, 1686 whose output format varies according to a component of the name that 1687 specifies one form of statistical summary. 1689 IANA is asked to assign a different numeric identifiers to each Name. 1690 All other column entries are the same, thus this section is proposes 1691 five closely-related registry entries. As a result, IANA is also 1692 asked to assign corresponding URIs and URLs. 1694 8.1. Summary 1696 This category includes multiple indexes to the registry entries, the 1697 element ID and metric name. 1699 8.1.1. ID (Identifier) 1701 1704 8.1.2. Name 1706 1708 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_ 1710 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Percentile95 1712 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Mean 1714 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Min 1716 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Max 1718 Act_IP_UDP_Periodic-var_UDP-Payload-142_One-way_Delay_Std_Dev 1720 8.1.3. URI and URL 1722 URI: Prefix urn:ietf:params:performance:metric... 1724 URL: http:\\www.iana.org\ ... 1726 8.1.4. Description 1728 This metric assesses the delay of a stream of packets exchanged 1729 between two hosts (or measurement points), and reports the 1730 One-way delay for all successfully exchanged packets 1731 based on their conditional delay distribution. 1733 8.2. Metric Definition 1735 This category includes columns to prompt the entry of all necessary 1736 details related to the metric definition, including the RFC reference 1737 and values of input factors, called fixed parameters. 1739 8.2.1. Reference Definition 1741 1743 Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric 1744 for IPPM", RFC 2679, September 1999. 1746 [RFC2679] 1748 Morton, A., and Stephan, E., "Spatial Composition of Metrics", RFC 1749 6049, January 2011. 1751 [RFC6049] 1752 1754 Section 3.4 of [RFC2679] provides the reference definition of the 1755 singleton (single value) One-way delay metric. Section 4.4 of 1756 [RFC2679] provides the reference definition expanded to cover a 1757 multi-value sample. Note that terms such as singleton and sample are 1758 defined in Section 11 of [RFC2330]. 1760 Only successful packet transfers with finite delay are included in 1761 the sample, as prescribed in section 4.1.2 of [RFC6049]. 1763 NOTE: RFC2679 will be replaced by 2679-bis on approval, see draft- 1764 ietf-ippm-2679-bis-01. 1766 ANY other conditions, ... 1768 8.2.2. Fixed Parameters 1770 1774 Type-P: 1776 o IPv4 header values: 1778 * DSCP: set to 0 1780 * TTL set to 255 1782 * Protocol: Set to 17 (UDP) 1784 o UDP header values: 1786 * Checksum: the checksum must be calculated 1788 o UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357] 1790 * Security features in use influence the number of Padding 1791 octets. 1793 * 142 octets total, including the TWAMP format 1795 Timeout, Tmax: 3 seconds 1797 8.3. Method of Measurement 1799 This category includes columns for references to relevant sections of 1800 the RFC(s) and any supplemental information needed to ensure an 1801 unambiguous methods for implementations. 1803 8.3.1. Reference Method 1805 1808 The methodology for this metric is defined as Type-P-One-way-Delay- 1809 Poisson-Stream in section 3.6 of [RFC2679] and section 4.6 of 1810 [RFC2679] using the Type-P and Timeout defined under Fixed 1811 Parameters. 1813 The method requires sequence numbers or other send-order information 1814 to be retained at the Src or included with each packet to dis- 1815 ambiguate packet reordering if it occurs. Sequence number is part of 1816 the TWAMP payload described under Fixed Parameters. 1818 8.3.2. Packet Generation Stream 1820 This section gives the details of the packet traffic which is the 1821 basis for measurement. In IPPM metrics, this is called the Stream, 1822 and can easily be dscribed by providing the list of stream 1823 parameters. 1825 1827 Section 3 of [RFC3432] prescribes the method for generating Periodic 1828 streams using associated parameters. 1830 o incT, the nominal duration of inter-packet interval, first bit to 1831 first bit 1833 o dT, the duration of the interval for allowed sample start times 1835 o T0, the actual start time 1837 NOTE: an initiation process with a number of control exchanges 1838 resulting in unpredictable start times (within a time interval) may 1839 be sufficient to avoid synchronization of periodic streams, and 1840 therefore a valid replacement for selecting a start time at random 1841 from a fixed interval. 1843 These stream parameters will be specified as Run-time parameters. 1845 8.3.3. Traffic Filtering (observation) Details 1847 NA 1849 8.3.4. Sampling Distribution 1851 NA 1853 8.3.5. Run-time Parameters and Data Format 1855 Run-time Parameters are input factors that must be determined, 1856 configured into the measurement system, and reported with the results 1857 for the context to be complete. 1859 1861 o Src, the IP address of a host (32-bit value for IPv4, 128-bit 1862 value for IPv6) 1864 o Dst, the IP address of a host (32-bit value for IPv4, 128-bit 1865 value for IPv6) 1867 o T0, a time (start of measurement interval, 128-bit NTP Date 1868 Format, see section 6 of [RFC5905]). When T0 is "all-zeros", a 1869 start time is unspecified and Tf is to be interpreted as the 1870 Duration of the measurement interval. 1872 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1873 see section 6 of [RFC5905]), interpreted as the Duration of the 1874 measurement interval. 1876 o incT, the nominal duration of inter-packet interval, first bit to 1877 first bit 1879 o dT, the duration of the interval for allowed sample start times 1881 The format for incT and dT are the short format in [RFC5905] (32 1882 bits) and is as follows: the first 16 bits represent the integer 1883 number of seconds; the next 16 bits represent the fractional part of 1884 a second. 1886 >>> should Periodic run-time params be fixed instead? probably yes if 1887 modeling a specific version of tests. Note in the NAME, i.e. 1888 Poisson3.3 1890 8.3.6. Roles 1892 1894 Src - launches each packet and waits for return transmissions from 1895 Dst. This is the TWAMP Session-Sender. 1897 Dst - waits for each packet from Src and sends a return packet to 1898 Src. This is the TWAMP Session-Reflector. 1900 8.4. Output 1902 This category specifies all details of the Output of measurements 1903 using the metric. 1905 8.4.1. Type/Value (two diff terms used) 1907 1909 See subsection titles in Data Format for Types. 1911 8.4.2. Data Format 1913 1915 For all output types --- 1917 o T0, a time (start of measurement interval, 128-bit NTP Date 1918 Format, see section 6 of [RFC5905]) 1920 o Tf, a time (end of measurement interval, 128-bit NTP Date Format, 1921 see section 6 of [RFC5905]) 1923 8.4.2.1. Percentile95 1925 The 95th percentile SHALL be calculated using the conditional 1926 distribution of all packets with a finite value of One-way delay 1927 (undefined delays are excluded), a single value as follows: 1929 See section 4.1 of [RFC3393] for details on the conditional 1930 distribution to exclude undefined values of delay, and Section 5 of 1931 [RFC6703] for background on this analysis choice. 1933 See section 4.3 of [RFC3393] for details on the percentile statistic 1934 (where Round-trip delay should be substituted for "ipdv"). 1936 The percentile = 95. 1938 Data format is a 32-bit signed value, *similar to* the 32-bit short 1939 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1940 first 16 bits represent the *signed* integer number of seconds; the 1941 next 16 bits represent the fractional part of a second. 1943 8.4.2.2. Mean 1945 The mean SHALL be calculated using the conditional distribution of 1946 all packets with a finite value of One-way delay (undefined delays 1947 are excluded), a single value as follows: 1949 See section 4.1 of [RFC3393] for details on the conditional 1950 distribution to exclude undefined values of delay, and Section 5 of 1951 [RFC6703] for background on this analysis choice. 1953 See section 4.2.2 of [RFC6049] for details on calculating this 1954 statistic, and 4.2.3 of [RFC6049]. 1956 Data format is a 32-bit signed value, *similar to* the 32-bit short 1957 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1958 first 16 bits represent the *signed* integer number of seconds; the 1959 next 16 bits represent the fractional part of a second. 1961 8.4.2.3. Min 1963 The minimum SHALL be calculated using the conditional distribution of 1964 all packets with a finite value of One-way delay (undefined delays 1965 are excluded), a single value as follows: 1967 See section 4.1 of [RFC3393] for details on the conditional 1968 distribution to exclude undefined values of delay, and Section 5 of 1969 [RFC6703] for background on this analysis choice. 1971 See section 4.3.2 of [RFC6049] for details on calculating this 1972 statistic, and 4.3.3 of [RFC6049]. 1974 Data format is a 32-bit signed value, *similar to* the 32-bit short 1975 NTP Time format in Section 6 of [RFC5905] and is as follows: the 1976 first 16 bits represent the *signed* integer number of seconds; the 1977 next 16 bits represent the fractional part of a second. 1979 8.4.2.4. Max 1981 The maximum SHALL be calculated using the conditional distribution of 1982 all packets with a finite value of One-way delay (undefined delays 1983 are excluded), a single value as follows: 1985 See section 4.1 of [RFC3393] for details on the conditional 1986 distribution to exclude undefined values of delay, and Section 5 of 1987 [RFC6703] for background on this analysis choice. 1989 See section 4.3.2 of [RFC6049] for a closely related method for 1990 calculating this statistic, and 4.3.3 of [RFC6049]. The formula is 1991 as follows: 1993 Max = (FiniteDelay [j]) 1995 such that for some index, j, where 1 <= j <= N 1996 FiniteDelay[j] >= FiniteDelay[n] for all n 1998 Data format is a 32-bit signed value, *similar to* the 32-bit short 1999 NTP Time format in Section 6 of [RFC5905] and is as follows: the 2000 first 16 bits represent the *signed* integer number of seconds; the 2001 next 16 bits represent the fractional part of a second. 2003 8.4.2.5. Std_Dev 2005 8.4.3. Reference 2007 2009 See the Data Format column for references. 2011 8.4.4. Metric Units 2013 . 2016 The of One-way Delay is expressed in seconds. 2018 8.5. Administrative items 2020 8.5.1. Status 2022 2024 8.5.2. Requestor (keep?) 2026 name or RFC, etc. 2028 8.5.3. Revision 2030 1.0 2032 8.5.4. Revision Date 2034 YYYY-MM-DD 2036 8.6. Comments and Remarks 2038 Additional (Informational) details for this entry 2040 9. partly BLANK Registry Entry 2042 This section gives an initial registry entry for .... 2044 9.1. Summary 2046 This category includes multiple indexes to the registry entries, the 2047 element ID and metric name. 2049 2051 9.1.1. ID (Identifier) 2053 2055 9.1.2. Name 2057 2059 URL: ?? 2061 9.1.3. URI 2063 URI: Prefix urn:ietf:params:performance:metric 2065 9.1.4. Description 2067 TBD. 2069 9.2. Metric Definition 2071 This category includes columns to prompt the entry of all necessary 2072 details related to the metric definition, including the RFC reference 2073 and values of input factors, called fixed parameters. 2075 9.2.1. Reference Definition 2077 2078 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 2079 Metric for IPPM", RFC 2681, September 1999. 2081 2083 Section 2.4 of [RFC2681] provides the reference definition of the 2084 singleton (single value) Round-trip delay metric. Section 3.4 of 2085 [RFC2681] provides the reference definition expanded to cover a 2086 multi-value sample. Note that terms such as singleton and sample are 2087 defined in Section 11 of [RFC2330]. 2089 Note that although the definition of "Round-trip-Delay between Src 2090 and Dst at T" is directionally ambiguous in the text, this metric 2091 tightens the definition further to recognize that the host in the 2092 "Src" role will send the first packet to "Dst", and ultimately 2093 receive the corresponding return packet from "Dst" (when neither are 2094 lost). 2096 <<< Check how the Methodology also makes this clear (or not) >>> 2098 9.2.2. Fixed Parameters 2100 2104 Type-P: 2106 o IPv4 header values: 2108 * DSCP: set to 0 2110 * TTL set to 255 2112 * Protocol: Set to 17 (UDP) 2114 o UDP header values: 2116 * Checksum: the checksum must be calculated 2118 o Payload 2120 * Sequence number: 8-byte integer 2122 * Timestamp: 8 byte integer. Expressed as 64-bit NTP timestamp 2123 as per section 6 of RFC 5905 [RFC5905] 2125 * No padding (total of 9 bytes) 2127 Timeout: 3 seconds 2129 9.3. Method of Measurement 2131 This category includes columns for references to relevant sections of 2132 the RFC(s) and any supplemental information needed to ensure an 2133 unambiguous methods for implementations. 2135 9.3.1. Reference Method 2137 2140 9.3.2. Packet Generation Stream 2142 This section gives the details of the packet traffic which is the 2143 basis for measurement. In IPPM metrics, this is called the Stream, 2144 and can easily be dscribed by providing the list of stream 2145 parameters. 2147 2149 9.3.3. Traffic Filtering (observation) Details 2151 The measured results based on a filtered version of the packets 2152 observed, and this section provides the filter details (when 2153 present). 2155
. 2157 9.3.4. Sampling Distribution 2159 2162 9.3.5. Run-time Parameters and Data Format 2164 Run-time Parameters are input factors that must be determined, 2165 configured into the measurement system, and reported with the results 2166 for the context to be complete. 2168 2170 . 2172 9.3.6. Roles 2174 2176 9.4. Output 2178 This category specifies all details of the Output of measurements 2179 using the metric. 2181 9.4.1. Type/Value (two diff terms used) 2183 2185 9.4.2. Data Format 2187 2189 o Value: 2191 o Data Format: (There may be some precedent to follow here, but 2192 otherwise use 64-bit NTP Timestamp Format, see section 6 of 2193 [RFC5905]). 2195 o Reference:
2197 9.4.3. Reference 2199 2201 9.4.4. Metric Units 2203 . 2206 9.5. Administrative items 2208 9.5.1. Status 2210 2212 9.5.2. Requestor (keep?) 2214 name or RFC, etc. 2216 9.5.3. Revision 2218 1.0 2220 9.5.4. Revision Date 2222 YYYY-MM-DD 2224 9.6. Comments and Remarks 2226 Additional (Informational) details for this entry 2228 10. BLANK Registry Entry 2230 This section gives an initial registry entry for .... 2232 10.1. Summary 2234 This category includes multiple indexes to the registry entries, the 2235 element ID and metric name. 2237 2239 10.1.1. ID (Identifier) 2241 2243 10.1.2. Name 2245 2247 URL: ?? 2249 10.1.3. URI 2251 URI: Prefix urn:ietf:params:performance:metric 2253 10.1.4. Description 2255 TBD. 2257 10.2. Metric Definition 2259 This category includes columns to prompt the entry of all necessary 2260 details related to the metric definition, including the RFC reference 2261 and values of input factors, called fixed parameters. 2263 10.2.1. Reference Definition 2265 2267 2269 10.2.2. Fixed Parameters 2271 2275 10.3. Method of Measurement 2277 This category includes columns for references to relevant sections of 2278 the RFC(s) and any supplemental information needed to ensure an 2279 unambiguous methods for implementations. 2281 10.3.1. Reference Method 2283 2286 10.3.2. Packet Generation Stream 2288 2290 10.3.3. Traffic Filtering (observation) Details 2292 . 2296 10.3.4. Sampling Distribution 2298 2301 10.3.5. Run-time Parameters and Data Format 2303 . 2305 10.3.6. Roles 2307 2309 10.4. Output 2311 This category specifies all details of the Output of measurements 2312 using the metric. 2314 10.4.1. Type/Value (two diff terms used) 2316 2318 10.4.2. Data Format 2320 2322 10.4.3. Reference 2324 2326 10.4.4. Metric Units 2328 . 2331 10.5. Administrative items 2333 10.5.1. Status 2335 2337 10.5.2. Requestor (keep?) 2339 2341 10.5.3. Revision 2343 1.0 2345 10.5.4. Revision Date 2347 YYYY-MM-DD 2349 10.6. Comments and Remarks 2351 Additional (Informational) details for this entry 2353 11. Example RTCP-XR Registry Entry 2355 This section is MAY BE DELETED or adapted before submission. 2357 This section gives an example registry entry for the end-point metric 2358 described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric 2359 reporting. 2361 11.1. Registry Indexes 2363 This category includes multiple indexes to the registry entries, the 2364 element ID and metric name. 2366 11.1.1. Identifier 2368 An integer having enough digits to uniquely identify each entry in 2369 the Registry. 2371 11.1.2. Name 2373 A metric naming convention is TBD. 2375 11.1.3. URI 2377 Prefix urn:ietf:params:performance:metric 2379 11.1.4. Status 2381 current 2383 11.1.5. Requestor 2385 Alcelip Mornuley 2387 11.1.6. Revision 2389 1.0 2391 11.1.7. Revision Date 2393 2014-07-04 2395 11.1.8. Description 2397 TBD. 2399 11.1.9. Reference Specification(s) 2401 [RFC3611][RFC4566][RFC6776][RFC6792][RFC7003] 2403 11.2. Metric Definition 2405 This category includes columns to prompt the entry of all necessary 2406 details related to the metric definition, including the RFC reference 2407 and values of input factors, called fixed parameters. Section 3.2 of 2408 [RFC7003] provides the reference information for this category. 2410 11.2.1. Reference Definition 2412 Packets Discarded in Bursts: 2414 The total number of packets discarded during discard bursts. The 2415 measured value is unsigned value. If the measured value exceeds 2416 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over- 2417 range measurement. If the measurement is unavailable, the value 2418 0xFFFFFF MUST be reported. 2420 11.2.2. Fixed Parameters 2422 Fixed Parameters are input factors that must be determined and 2423 embedded in the measurement system for use when needed. The values 2424 of these parameters is specified in the Registry. 2426 Threshold: 8 bits, set to value = 3 packets. 2428 The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of 2429 successive packets that must not be discarded prior to and following 2430 a discard packet in order for this discarded packet to be regarded as 2431 part of a gap. Note that the Threshold is set in accordance with the 2432 Gmin calculation defined in Section 4.7.2 of [RFC3611]. 2434 Interval Metric flag: 2 bits, set to value 11=Cumulative Duration 2436 This field is used to indicate whether the burst/gap discard metrics 2437 are Sampled, Interval, or Cumulative metrics [RFC6792]: 2439 I=10: Interval Duration - the reported value applies to the most 2440 recent measurement interval duration between successive metrics 2441 reports. 2443 I=11: Cumulative Duration - the reported value applies to the 2444 accumulation period characteristic of cumulative measurements. 2446 Senders MUST NOT use the values I=00 or I=01. 2448 11.3. Method of Measurement 2450 This category includes columns for references to relevant sections of 2451 the RFC(s) and any supplemental information needed to ensure an 2452 unambiguous methods for implementations. For the Burst/Gap Discard 2453 Metric, it appears that the only guidance on methods of measurement 2454 is in Section 3.0 of [RFC7003] and its supporting references. 2455 Relevant information is repeated below, although there appears to be 2456 no section titled "Method of Measurement" in [RFC7003]. 2458 11.3.1. Reference Method 2460 Metrics in this block report on burst/gap discard in the stream 2461 arriving at the RTP system. Measurements of these metrics are made 2462 at the receiving end of the RTP stream. Instances of this metrics 2463 block use the synchronization source (SSRC) to refer to the separate 2464 auxiliary Measurement Information Block [RFC6776], which describes 2465 measurement periods in use (see [RFC6776], Section 4.2). 2467 This metrics block relies on the measurement period in the 2468 Measurement Information Block indicating the span of the report. 2469 Senders MUST send this block in the same compound RTCP packet as the 2470 Measurement Information Block. Receivers MUST verify that the 2471 measurement period is received in the same compound RTCP packet as 2472 this metrics block. If not, this metrics block MUST be discarded. 2474 11.3.2. Stream Type and Stream Parameters 2476 Since RTCP-XR Measurements are conducted on live RTP traffic, the 2477 complete description of the stream is contained in SDP messages that 2478 proceed the establishment of a compatible stream between two or more 2479 communicating hosts. See Run-time Parameters, below. 2481 11.3.3. Output Type and Data Format 2483 The output type defines the type of result that the metric produces. 2485 o Value: Packets Discarded in Bursts 2487 o Data Format: 24 bits 2489 o Reference: Section 3.2 of [RFC7003] 2491 11.3.4. Metric Units 2493 The measured results are apparently expressed in packets, although 2494 there is no section of [RFC7003] titled "Metric Units". 2496 11.3.5. Run-time Parameters and Data Format 2498 Run-Time Parameters are input factors that must be determined, 2499 configured into the measurement system, and reported with the results 2500 for the context to be complete. However, the values of these 2501 parameters is not specified in the Registry, rather these parameters 2502 are listed as an aid to the measurement system implementor or user 2503 (they must be left as variables, and supplied on execution). 2505 The Data Format of each Run-time Parameter SHALL be specified in this 2506 column, to simplify the control and implementation of measurement 2507 devices. 2509 SSRC of Source: 32 bits As defined in Section 4.1 of [RFC3611]. 2511 SDP Parameters: As defined in [RFC4566] 2513 Session description v= (protocol version number, currently only 0) 2515 o= (originator and session identifier : username, id, version number, 2516 network address) 2518 s= (session name : mandatory with at least one UTF-8-encoded 2519 character) 2521 i=* (session title or short information) u=* (URI of description) 2523 e=* (zero or more email address with optional name of contacts) 2525 p=* (zero or more phone number with optional name of contacts) 2527 c=* (connection information--not required if included in all media) 2529 b=* (zero or more bandwidth information lines) One or more Time 2530 descriptions ("t=" and "r=" lines; see below) 2532 z=* (time zone adjustments) 2534 k=* (encryption key) 2536 a=* (zero or more session attribute lines) 2538 Zero or more Media descriptions (each one starting by an "m=" line; 2539 see below) 2541 m= (media name and transport address) 2543 i=* (media title or information field) 2544 c=* (connection information -- optional if included at session level) 2546 b=* (zero or more bandwidth information lines) 2548 k=* (encryption key) 2550 a=* (zero or more media attribute lines -- overriding the Session 2551 attribute lines) 2553 An example Run-time SDP description follows: 2555 v=0 2557 o=jdoe 2890844526 2890842807 IN IP4 192.0.2.5 2559 s=SDP Seminar i=A Seminar on the session description protocol 2561 u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane 2562 Doe) 2564 c=IN IP4 233.252.0.12/127 2566 t=2873397496 2873404696 2568 a=recvonly 2570 m=audio 49170 RTP/AVP 0 2572 m=video 51372 RTP/AVP 99 2574 a=rtpmap:99 h263-1998/90000 2576 11.4. Comments and Remarks 2578 TBD. 2580 12. Security Considerations 2582 These registry entries represent no known security implications for 2583 Internet Security. Each referenced Metric contains a Security 2584 Considerations section. 2586 13. IANA Considerations 2588 IANA is requested to create The Active Performance Metric Sub- 2589 registry within the Performance Metric Registry defined in 2590 [I-D.ietf-ippm-metric-registry]. The Sub-registry will contain the 2591 following categories and (bullet) columns, (as defined in section 3 2592 above): 2594 Common Registry Indexes and Info 2596 o Identifier 2598 o Name 2600 o Status 2602 o Requester 2604 o Revision 2606 o Revision Date 2608 o Description 2610 o Reference Specification(s) 2612 Metric Definition 2614 o Reference Definition 2616 o Fixed Parameters 2618 Method of Measurement 2620 o Reference Method 2622 o Stream Type and Parameters 2624 o Output type and Data format 2626 o Metric Units 2628 o Run-time Parameters 2630 Comments and Remarks 2632 14. Acknowledgements 2634 The authors thank Brian Trammell for suggesting the term "Run-time 2635 Parameters", which led to the distinction between run-time and fixed 2636 parameters implemented in this memo, for raising the IPFIX metric 2637 with Flow Key as an example, and for many other productive 2638 suggestions.Thanks to Peter Koch, who provided several useful 2639 suggestions for disambiguating successive DNS Queries in the DNS 2640 Response time metric. 2642 15. References 2644 15.1. Normative References 2646 [I-D.ietf-ippm-metric-registry] 2647 Bagnulo, M., Claise, B., Eardley, P., and A. Morton, 2648 "Registry for Performance Metrics", Internet Draft (work 2649 in progress) draft-ietf-ippm-metric-registry, 2014. 2651 [RFC1035] Mockapetris, P., "Domain names - implementation and 2652 specification", STD 13, RFC 1035, November 1987. 2654 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2655 Requirement Levels", BCP 14, RFC 2119, March 1997. 2657 [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, 2658 "Framework for IP Performance Metrics", RFC 2330, May 2659 1998. 2661 [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way 2662 Delay Metric for IPPM", RFC 2679, September 1999. 2664 [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way 2665 Packet Loss Metric for IPPM", RFC 2680, September 1999. 2667 [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip 2668 Delay Metric for IPPM", RFC 2681, September 1999. 2670 [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation 2671 Metric for IP Performance Metrics (IPPM)", RFC 3393, 2672 November 2002. 2674 [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network 2675 performance measurement with periodic streams", RFC 3432, 2676 November 2002. 2678 [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, 2679 S., and J. Perser, "Packet Reordering Metrics", RFC 4737, 2680 November 2006. 2682 [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. 2683 Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", 2684 RFC 5357, October 2008. 2686 [RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network 2687 Time Protocol Version 4: Protocol and Algorithms 2688 Specification", RFC 5905, June 2010. 2690 [RFC6049] Morton, A. and E. Stephan, "Spatial Composition of 2691 Metrics", RFC 6049, January 2011. 2693 [RFC6673] Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673, 2694 August 2012. 2696 15.2. Informative References 2698 [Brow00] Brownlee, N., "Packet Matching for NeTraMet 2699 Distributions", March 2000. 2701 [I-D.ietf-lmap-framework] 2702 Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., 2703 Aitken, P., and A. Akhter, "A framework for Large-Scale 2704 Measurement of Broadband Performance (LMAP)", draft-ietf- 2705 lmap-framework-14 (work in progress), April 2015. 2707 [RFC1242] Bradner, S., "Benchmarking terminology for network 2708 interconnection devices", RFC 1242, July 1991. 2710 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 2711 Protocol Extended Reports (RTCP XR)", RFC 3611, November 2712 2003. 2714 [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics 2715 Registry", BCP 108, RFC 4148, August 2005. 2717 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 2718 Description Protocol", RFC 4566, July 2006. 2720 [RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP 2721 Flow Information Export (IPFIX) Applicability", RFC 5472, 2722 March 2009. 2724 [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. 2725 Carle, "Information Model for Packet Sampling Exports", 2726 RFC 5477, March 2009. 2728 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 2729 Applicability Statement", RFC 5481, March 2009. 2731 [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics 2732 (IPPM) Registry of Metrics Are Obsolete", RFC 6248, April 2733 2011. 2735 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 2736 Performance Metric Development", BCP 170, RFC 6390, 2737 October 2011. 2739 [RFC6703] Morton, A., Ramachandran, G., and G. Maguluri, "Reporting 2740 IP Network Performance Metrics: Different Points of View", 2741 RFC 6703, August 2012. 2743 [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information 2744 Reporting Using a Source Description (SDES) Item and an 2745 RTCP Extended Report (XR) Block", RFC 6776, October 2012. 2747 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 2748 RTP Monitoring Framework", RFC 6792, November 2012. 2750 [RFC7003] Clark, A., Huang, R., and Q. Wu, "RTP Control Protocol 2751 (RTCP) Extended Report (XR) Block for Burst/Gap Discard 2752 Metric Reporting", RFC 7003, September 2013. 2754 Authors' Addresses 2756 Al Morton 2757 AT&T Labs 2758 200 Laurel Avenue South 2759 Middletown,, NJ 07748 2760 USA 2762 Phone: +1 732 420 1571 2763 Fax: +1 732 368 1192 2764 Email: acmorton@att.com 2765 URI: http://home.comcast.net/~acmacm/ 2767 Marcelo Bagnulo 2768 Universidad Carlos III de Madrid 2769 Av. Universidad 30 2770 Leganes, Madrid 28911 2771 SPAIN 2773 Phone: 34 91 6249500 2774 Email: marcelo@it.uc3m.es 2775 URI: http://www.it.uc3m.es 2776 Philip Eardley 2777 BT 2778 Adastral Park, Martlesham Heath 2779 Ipswich 2780 ENGLAND 2782 Email: philip.eardley@bt.com 2784 Kevin D'Souza 2785 AT&T Labs 2786 200 Laurel Avenue South 2787 Middletown,, NJ 07748 2788 USA 2790 Phone: +1 732 420 xxxx 2791 Email: kevin.dsouza@att.com