Network Working Group A. Morton Internet-Draft AT&T Labs Intended status: Standards Track M. Mathis Expires: September 14, 2017 Google March 13, 2017 Initial Performance Metric Registry Entries Part 2: MBM draft-morton-ippm-mbm-registry-01 Abstract This memo defines a Registry Entry for the Performance Metrics Registry based on Model Based Metrics. This entry will be combined with the "initial-registry" draft after review. The string "@@@@" identifies some areas for further discussion to finalize the text. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 14, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. Morton & Mathis Expires September 14, 2017 [Page 1] Internet-Draft Initial Registry Part 2 March 2017 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MBM Registry Entry . . . . . . . . . . . . . . . . . . . . . 4 3.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 4 3.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1.4. Description . . . . . . . . . . . . . . . . . . . . . 4 3.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 4 3.1.6. Change Controller . . . . . . . . . . . . . . . . . . 5 3.1.7. Version (of Registry Format) . . . . . . . . . . . . 5 3.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 5 3.2.1. Reference Definition . . . . . . . . . . . . . . . . 5 3.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 6 3.3. Method of Measurement . . . . . . . . . . . . . . . . . . 7 3.3.1. Reference Method . . . . . . . . . . . . . . . . . . 7 3.3.2. Packet Stream Generation . . . . . . . . . . . . . . 8 3.3.3. Traffic Filtering (observation) Details . . . . . . . 9 3.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 9 3.3.5. Run-time Parameters and Data Format . . . . . . . . . 9 3.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 11 3.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 12 3.4.2. Reference Definition . . . . . . . . . . . . . . . . 12 3.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 13 3.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 13 3.5. Administrative items . . . . . . . . . . . . . . . . . . 13 3.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 13 3.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 13 3.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 13 3.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 14 3.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 14 4. ver08 BLANK Registry Entry . . . . . . . . . . . . . . . . . 14 4.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.1. ID (Identifier) . . . . . . . . . . . . . . . . . . . 14 4.1.2. Name . . . . . . . . . . . . . . . . . . . . . . . . 14 Morton & Mathis Expires September 14, 2017 [Page 2] Internet-Draft Initial Registry Part 2 March 2017 4.1.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . 14 4.1.4. Description . . . . . . . . . . . . . . . . . . . . . 14 4.1.5. Reference . . . . . . . . . . . . . . . . . . . . . . 14 4.1.6. Change Controller . . . . . . . . . . . . . . . . . . 14 4.1.7. Version (of Registry Format) . . . . . . . . . . . . 14 4.2. Metric Definition . . . . . . . . . . . . . . . . . . . . 15 4.2.1. Reference Definition . . . . . . . . . . . . . . . . 15 4.2.2. Fixed Parameters . . . . . . . . . . . . . . . . . . 15 4.3. Method of Measurement . . . . . . . . . . . . . . . . . . 15 4.3.1. Reference Method . . . . . . . . . . . . . . . . . . 15 4.3.2. Packet Stream Generation . . . . . . . . . . . . . . 15 4.3.3. Traffic Filtering (observation) Details . . . . . . . 15 4.3.4. Sampling Distribution . . . . . . . . . . . . . . . . 15 4.3.5. Run-time Parameters and Data Format . . . . . . . . . 16 4.3.6. Roles . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4. Output . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4.1. Type . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4.2. Reference Definition . . . . . . . . . . . . . . . . 16 4.4.3. Metric Units . . . . . . . . . . . . . . . . . . . . 16 4.4.4. Calibration . . . . . . . . . . . . . . . . . . . . . 16 4.5. Administrative items . . . . . . . . . . . . . . . . . . 16 4.5.1. Status . . . . . . . . . . . . . . . . . . . . . . . 16 4.5.2. Requestor . . . . . . . . . . . . . . . . . . . . . . 16 4.5.3. Revision . . . . . . . . . . . . . . . . . . . . . . 16 4.5.4. Revision Date . . . . . . . . . . . . . . . . . . . . 17 4.6. Comments and Remarks . . . . . . . . . . . . . . . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 17 8.2. Informative References . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 1. Introduction Note: Efforts to synchronize structure and terminology with [I-D.ietf-ippm-metric-registry] will likely be incomplete until both drafts are stable. This memo proposes a (set of) entry(ies) for the Performance Metric Registry, based on Model-Based Metrics (MBM). It uses terms and definitions from the IPPM literature, primarily [RFC2330]. Morton & Mathis Expires September 14, 2017 [Page 3] Internet-Draft Initial Registry Part 2 March 2017 2. Scope This document defines one of the initial set of Performance Metrics Registry entries, for which IETF approval (following development in the IP Performance Metrics (IPPM) Working Group) will satisfy the requirement for Expert Review. Note that all are Active Performance Metrics, which are based on RFCs prepared in the IPPM working group of the IETF, according to their framework [RFC2330] and its updates. 3. MBM Registry Entry This section gives an initial registry entry for a Model-Based Metric (MBM) Sustained Burst Metric. 3.1. Summary This category includes multiple indexes to the registry entries, the element ID and metric name. 3.1.1. ID (Identifier) 3.1.2. Name OWMBM_Active_IP-TCP-SustainedBurst_RFCXXXXsecY_Enumerated_PFI 3.1.3. URIs URI: Prefix urn:ietf:metrics:perf: URL: http:\\www.iana.org\ ... 3.1.4. Description TBD. 3.1.5. Reference RFCXXXXsecY Morton & Mathis Expires September 14, 2017 [Page 4] Internet-Draft Initial Registry Part 2 March 2017 3.1.6. Change Controller IETF 3.1.7. Version (of Registry Format) 1.0 3.2. Metric Definition This category includes columns to prompt the entry of all necessary details related to the metric definition, including the RFC reference and values of input factors, called fixed parameters. 3.2.1. Reference Definition Mathis, M. and A. Morton, "Model Based Metrics for Bulk Transport Capacity", draft-ietf-ippm-model-based- metrics-10 (work in progress), February 2017. The primary metrics of measurement are round-trip delay and one-way loss, measured under the conditions described in Section 8.5.1 of [I-D.ietf-ippm-model-based-metrics]. For loss: Almes, G., Kalidini, S., Zekauskas, M., and A. Morton, Ed., "A One- Way Loss Metric for IP Performance Metrics (IPPM)", RFC 7680, DOI 10.17487/RFC7680, January 2016, . Section 2.4 of [RFC7680] provides the reference definition of the singleton (single value) one-way loss metric. Section 3.4 of [RFC7680] provides the reference definition expanded to cover a multi-singleton sample. Note that terms such as singleton and sample are defined in Section 11 of [RFC2330]. For round-trip delay: Morton & Mathis Expires September 14, 2017 [Page 5] Internet-Draft Initial Registry Part 2 March 2017 Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Packet Loss Metric for IPPM", RFC 2680, September 1999. [RFC2681] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One- Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January 2016, . [RFC7679] Section 2.4 of [RFC2681] provides the reference definition of the singleton (single value) Round-trip delay metric. Section 3.4 of [RFC2681] provides the reference definition expanded to cover a multi-singleton sample. Note that terms such as singleton and sample are defined in Section 11 of [RFC2330]. Note that although the definition of "Round-trip-Delay between Src and Dst" is directionally ambiguous in the text, this metric tightens the definition further to recognize that the host in the "Src" role will send the first packet to "Dst", and ultimately receive the corresponding return packet from "Dst" (when neither are lost). Finally, note that the variable "dT" is used in [RFC2681] to refer to the value of Round-trip delay in metric definitions and methods. The variable "dT" has been re-used in other IPPM literature to refer to different quantities, and cannot be used as a global variable name here. 3.2.2. Fixed Parameters Type-P as defined in Section 13 of [RFC2330]: o IPv4 header values: * DSCP: set to 0 * TTL: set to 255 * Protocol: Set to 6 (TCP) Morton & Mathis Expires September 14, 2017 [Page 6] Internet-Draft Initial Registry Part 2 March 2017 o IPv6 header values: * DSCP: set to 0 * Hop Count: set to 255 * Protocol: Set to 6 (TCP) o TCP header values: * Checksum: the checksum MUST be calculated and included in the header o TCP Payload * see target_MTU in Run-time parameters. Other measurement parameters: o Tmax: a loss threshold waiting time @@@@ Should this be linked to TCP RTO, or target_RTT plus a factor ??? * 3.0, expressed in units of seconds, as a positive value of type decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020]) and with resolution of 0.0001 seconds (0.1 ms), with lossless conversion to/from the 32-bit NTP timestamp as per section 6 of [RFC5905]. 3.3. Method of Measurement This category includes columns for references to relevant sections of the RFC(s) and any supplemental information needed to ensure an unambiguous methods for implementations. 3.3.1. Reference Method The method of measurement is described in Section 8.5.1 of [I-D.ietf-ippm-model-based-metrics]. The example described in Section 9 of [I-D.ietf-ippm-model-based-metrics] may also help. @@@@ Morton & Mathis Expires September 14, 2017 [Page 7] Internet-Draft Initial Registry Part 2 March 2017 3.3.2. Packet Stream Generation The stream generation parameters are described in Section 3 of [I-D.ietf-ippm-model-based-metrics]. They are dependent on the target parameters described in the Run-time parameters section below. They are written here with underscores because they are used in formulas in this note. @@@@ I strongly suggest decimal64 fraction digits = 9 or 12 (i.e nanoseconds or picoseconds). I point out that the average headway for min sized packets on 100Gb/s is already down to 5.1 uS. In either case for decimal64 the max headway is way longer than ever needed (decades or months). --MM-- (@@@@ BTW I think your fraction digits are off --MM--). @@@@ This section has a general problem that it need to better prescribe generic concepts (headway, sizes, rates) and then define multiple distinct parameters needed to properly specify each pattern. packet_headway Time interval between packets, specified from the start of one to the start of the next, as a positive value of type decimal64 with fraction digits = 9 seconds, for a resolution of 1 nanosecond. (see section 9.3 of [RFC6020]). @@@@ We need a convention for "back to back" independent of clock accuracy.--MM-- burst_headway Time interval between bursts, specified from the start of the first packet one burst to the start of the first packet of the next burst, specified as a positive value of type decimal64 with fraction digits = 9 seconds, for a resolution of 1 nanosecond. (see section 9.3 of [RFC6020]). paced_single_packets Send individual packets at the specified packet headway, specified as a positive value of type decimal64 with fraction digits = 9 seconds, for a resolution of 1 nanosecond. (see section 9.3 of [RFC6020]). @@@@ NB: I dropped rate.--MM-- paced_bursts Send bursts on a timer. Specify any 3 of: average data rate, packet size, burst size (number of packets) and burst headway (burst start to start), specified as a positive value of type decimal64 with fraction digits = 9 seconds, for a resolution of 1 nanosecond. (see section 9.3 of [RFC6020]). slowstart_rate The average data rate necessary to mimic TCP slowstart by sending 4 packet paced bursts to mimic a two level burst pattern as described in Section 6.1 of [I-D.ietf-ippm-model-based-metrics]. This rate should be chosen Morton & Mathis Expires September 14, 2017 [Page 8] Internet-Draft Initial Registry Part 2 March 2017 to be twice the implied bottleneck IP capacity (but not more than the sender interface rate). The slowstart_rate is specified as a value of type uint32 (see section 9.2 of [RFC6020]) in units of IP-layer bytes per second. slowstart_burst Mimic one round of TCP slowstart by sending a specified number of packets in a two level burst pattern that resembles slowstart, specified as a number of type uint16 (see section 9.2 of [RFC6020]) in units of packets, and a rate specified as a value of type uint16 (see section 9.2 of [RFC6020]) in units of packets per second. repeated_slowstart_burst Repeat Slowstart bursts once per target_RTT. All Slowstart bursts are the same size in measurements (different from normal TCP sending behavior), specified as a value of type boolean (see section 9.5 of [RFC6020]). @@@@@ I would change this to [slowestart] burst headway, nominally an interval mimicking the RTT and long enough to permit all of the queues to drain between slowstart bursts. 3.3.3. Traffic Filtering (observation) Details . NA 3.3.4. Sampling Distribution NA 3.3.5. Run-time Parameters and Data Format . The following parameters are described in [RFC2330] Src the IP address of the host in the Src Role (format ipv4-address- no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, see Section 4 of [RFC6991]) Dst the IP address of the host in the Dst Role (format ipv4-address- no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, see section 4 of [RFC6991]) Morton & Mathis Expires September 14, 2017 [Page 9] Internet-Draft Initial Registry Part 2 March 2017 T0 a time, the start of a measurement interval, (format "date-and- time" as specified in Section 5.6 of [RFC3339], see also Section 3 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC2330]. When T0 is "all-zeros", a start time is unspecified and Tf is to be interpreted as the Duration of the measurement interval. The start time is controlled through other means. Tf a time, the end of a measurement interval, (format "date-and-time" as specified in Section 5.6 of [RFC3339], see also Section 3 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC2330]. When T0 is "all-zeros", a end time date is ignored and Tf is interpreted as the Duration of the measurement interval. The following MBM-specific parameters are as defined in Section 3 of [I-D.ietf-ippm-model-based-metrics], and subsequent sections of the memo. target_data_rate The specified application data rate required for an application's proper operation, specified as a value of type uint32 (see section 9.2 of [RFC6020]) in units of IP-layer bytes per second. target_RTT The specified baseline (minimum) RTT of the longest complete path over which the user expects to be able meet the target performance, specified as a positive value of type decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020]) with resolution of 0.0001 seconds (0.1 ms). target_MTU The specified maximum MTU supported by the complete path the over which the application expects to meet the target performancespecified as a value of type uint16 (see section 9.2 of [RFC6020]) in units of IP-layer bytes. target_window_size The average number of packets in flight (the window size) needed to meet the Target Data Rate, for the specified Target RTT, and MTU, specified as a value of type uint32 (see section 9.2 of [RFC6020]) in units of @@@@ packets @@@@ or IP-layer bytes @@@@@. It implies the scale of the bursts that the network might experience. subpath_??? @@@@@ Do we need a subpath-specific parameter? Such as subpath_RTT ??? derating The modeling framework permits some latitude in relaxing or "derating" some test parameters as described in Section 5.3 of [I-D.ietf-ippm-model-based-metrics], in exchange for a more stringent TIDS validation procedures as described in Section 10 of [I-D.ietf-ippm-model-based-metrics]. The use of derated Morton & Mathis Expires September 14, 2017 [Page 10] Internet-Draft Initial Registry Part 2 March 2017 parameters is specified as a value of type boolean (see section 9.5 of [RFC6020]). test_window The smallest window sufficient to meet or exceed the target_rate when operating with a pure self-clock over a test path, specified as a value of type uint32 (see section 9.2 of [RFC6020]) in units of @@@@ packets @@@@ or IP-layer bytes @@@@@. The following MBM-specific parameters are as defined in Section of 7.2 [I-D.ietf-ippm-model-based-metrics]: H0H1_ratio The value of the multiplier on the Null Hypothesis loss ratio used to calculate the Alternate Hypothesis loss ratio, specified as a value of type uint8 (see section 9.2 of [RFC6020]) and unit-less. alpha_TI_err Measurements support accepting H0 with the specified Type I error = alpha (= 0.05 for example), specified as a positive value of type decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020]) with resolution of 0.0001. beta_TII_err Measurements support accepting H1 with the specified Type II error = beta (= 0.05 for example), specified as a positive value of type decimal64 with fraction digits = 4 (see section 9.3 of [RFC6020]) with resolution of 0.0001. Additional MBM-specific parameters may be calculated by the measurement system itself, or they may be supplied as additional Run- time parameters: @@@@ Candidates ???? 3.3.6. Roles data_sender Host sending data and receiving ACKs. data_receiver Host receiving data and sending ACKs. as described in Section 3 of [I-D.ietf-ippm-model-based-metrics]. Morton & Mathis Expires September 14, 2017 [Page 11] Internet-Draft Initial Registry Part 2 March 2017 3.4. Output This category specifies all details of the Output of measurements using the metric. 3.4.1. Type The primary output type is PFI, or Pass, Fail, Inconclusive, referring to the conclusion of the test. Two secondary output types MAY be reported to support the primary output. Loss Ratio: Singleton Mean Round-trip Time: Singleton 3.4.2. Reference Definition T0 the start of a measurement interval, (format "date-and-time" as specified in Section 5.6 of [RFC3339], see also Section 3 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC2330]. Tf the end of a measurement interval, (format "date-and-time" as specified in Section 5.6 of [RFC3339], see also Section 3 of [RFC6991]). The UTC Time Zone is required by Section 6.1 of [RFC2330]. PFI the summarized result of the measurement representing the conclusion of whether or not the target values have been achieved, (format enum as specified in section 9.6 of [RFC6020]) with one of the following enumerations: Pass, Fail, Inconclusive. Loss_Ratio the result of lost (or ECN marked) packet measurement from data_sender to data_receiver, expressed as the ratio of lost packets to total packets sent from the data sender (units). See section 4 of [RFC7680] for details on this calculation. Mean_RTT Mean Round-trip Time: The mean SHALL be calculated using the conditional distribution of all packets with a finite value of round-trip delay (undefined delays are excluded), a single value as follows: Morton & Mathis Expires September 14, 2017 [Page 12] Internet-Draft Initial Registry Part 2 March 2017 * See section 4.1 of [RFC3393] for details on the conditional distribution to exclude undefined values of delay, and Section 5 of [RFC6703] for background on this analysis choice. * See section 4.2.2 of [RFC6049] for details on calculating this statistic, and 4.2.3 of [RFC6049]. * The time value of the result is expressed in units of seconds, as a positive value of type decimal64 with fraction digits = 9 (see section 9.3 of [RFC6020]) with resolution of 0.000000001 seconds (1.0 ns), and with lossless conversion to/from the 64-bit NTP timestamp as per section 6 of RFC [RFC5905]. 3.4.3. Metric Units . PFI: Enumerated{Pass, Fail, Inconclusive} Loss Ratio: RatioPercent Mean Round-trip Time: Seconds 3.4.4. Calibration 3.5. Administrative items 3.5.1. Status 3.5.2. Requestor 3.5.3. Revision 1.0 Morton & Mathis Expires September 14, 2017 [Page 13] Internet-Draft Initial Registry Part 2 March 2017 3.5.4. Revision Date YYYY-MM-DD 3.6. Comments and Remarks Additional (Informational) details for this entry 4. ver08 BLANK Registry Entry This section gives an initial registry entry for .... 4.1. Summary This category includes multiple indexes to the registry entries, the element ID and metric name. 4.1.1. ID (Identifier) 4.1.2. Name 4.1.3. URIs URI: Prefix urn:ietf:params:performance:metric URL: 4.1.4. Description TBD. 4.1.5. Reference 4.1.6. Change Controller 4.1.7. Version (of Registry Format) Morton & Mathis Expires September 14, 2017 [Page 14] Internet-Draft Initial Registry Part 2 March 2017 4.2. Metric Definition This category includes columns to prompt the entry of all necessary details related to the metric definition, including the RFC reference and values of input factors, called fixed parameters. 4.2.1. Reference Definition 4.2.2. Fixed Parameters 4.3. Method of Measurement This category includes columns for references to relevant sections of the RFC(s) and any supplemental information needed to ensure an unambiguous methods for implementations. 4.3.1. Reference Method 4.3.2. Packet Stream Generation 4.3.3. Traffic Filtering (observation) Details . 4.3.4. Sampling Distribution Morton & Mathis Expires September 14, 2017 [Page 15] Internet-Draft Initial Registry Part 2 March 2017 4.3.5. Run-time Parameters and Data Format . 4.3.6. Roles 4.4. Output This category specifies all details of the Output of measurements using the metric. 4.4.1. Type 4.4.2. Reference Definition 4.4.3. Metric Units . 4.4.4. Calibration 4.5. Administrative items 4.5.1. Status 4.5.2. Requestor 4.5.3. Revision 1.0 Morton & Mathis Expires September 14, 2017 [Page 16] Internet-Draft Initial Registry Part 2 March 2017 4.5.4. Revision Date YYYY-MM-DD 4.6. Comments and Remarks Additional (Informational) details for this entry 5. Security Considerations These registry entries represent no known security implications for Internet Security. Each referenced Metric contains a Security Considerations section. 6. IANA Considerations IANA is requested to populate The Performance Metric Registry defined in [I-D.ietf-ippm-metric-registry] with the values defined above. 7. Acknowledgements The authors thank Brian Trammell for suggesting the term "Run-time Parameters", which led to the distinction between run-time and fixed parameters implemented in this memo, for identifying the IPFIX metric with Flow Key as an example, and for many other productive suggestions. Thanks to Peter Koch, who provided several useful suggestions for disambiguating successive DNS Queries in the DNS Response time metric. The authors also acknowledge the constructive reviews and helpful suggestions from Barbara Stark, Juergen Schoenwaelder, Tim Carey, and participants in the LMAP working group. 8. References 8.1. Normative References [I-D.ietf-ippm-metric-registry] Bagnulo, M., Claise, B., Eardley, P., and A. Morton, "Registry for Performance Metrics", Internet Draft (work in progress) draft-ietf-ippm-metric-registry, 2014. [I-D.ietf-ippm-model-based-metrics] Mathis, M. and A. Morton, "Model Based Metrics for Bulk Transport Capacity", draft-ietf-ippm-model-based- metrics-10 (work in progress), February 2017. Morton & Mathis Expires September 14, 2017 [Page 17] Internet-Draft Initial Registry Part 2 March 2017 [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, November 1987, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP Performance Metrics", RFC 2330, DOI 10.17487/RFC2330, May 1998, . [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, September 1999, . [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way Packet Loss Metric for IPPM", RFC 2680, DOI 10.17487/RFC2680, September 1999, . [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681, September 1999, . [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)", RFC 3393, DOI 10.17487/RFC3393, November 2002, . [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network performance measurement with periodic streams", RFC 3432, DOI 10.17487/RFC3432, November 2002, . [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, S., and J. Perser, "Packet Reordering Metrics", RFC 4737, DOI 10.17487/RFC4737, November 2006, . Morton & Mathis Expires September 14, 2017 [Page 18] Internet-Draft Initial Registry Part 2 March 2017 [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", RFC 5357, DOI 10.17487/RFC5357, October 2008, . [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, "Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6049] Morton, A. and E. Stephan, "Spatial Composition of Metrics", RFC 6049, DOI 10.17487/RFC6049, January 2011, . [RFC6673] Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673, DOI 10.17487/RFC6673, August 2012, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . [RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January 2016, . [RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-Way Loss Metric for IP Performance Metrics (IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January 2016, . 8.2. Informative References [Brow00] Brownlee, N., "Packet Matching for NeTraMet Distributions", March 2000. [RFC1242] Bradner, S., "Benchmarking Terminology for Network Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, July 1991, . Morton & Mathis Expires September 14, 2017 [Page 19] Internet-Draft Initial Registry Part 2 March 2017 [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed., "RTP Control Protocol Extended Reports (RTCP XR)", RFC 3611, DOI 10.17487/RFC3611, November 2003, . [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics Registry", BCP 108, RFC 4148, DOI 10.17487/RFC4148, August 2005, . [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, DOI 10.17487/RFC4566, July 2006, . [RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP Flow Information Export (IPFIX) Applicability", RFC 5472, DOI 10.17487/RFC5472, March 2009, . [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. Carle, "Information Model for Packet Sampling Exports", RFC 5477, DOI 10.17487/RFC5477, March 2009, . [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, March 2009, . [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are Obsolete", RFC 6248, DOI 10.17487/RFC6248, April 2011, . [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New Performance Metric Development", BCP 170, RFC 6390, DOI 10.17487/RFC6390, October 2011, . [RFC6703] Morton, A., Ramachandran, G., and G. Maguluri, "Reporting IP Network Performance Metrics: Different Points of View", RFC 6703, DOI 10.17487/RFC6703, August 2012, . [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block", RFC 6776, DOI 10.17487/RFC6776, October 2012, . Morton & Mathis Expires September 14, 2017 [Page 20] Internet-Draft Initial Registry Part 2 March 2017 [RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use of the RTP Monitoring Framework", RFC 6792, DOI 10.17487/RFC6792, November 2012, . [RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003, September 2013, . [RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., Aitken, P., and A. Akhter, "A Framework for Large-Scale Measurement of Broadband Performance (LMAP)", RFC 7594, DOI 10.17487/RFC7594, September 2015, . Authors' Addresses Al Morton AT&T Labs 200 Laurel Avenue South Middletown,, NJ 07748 USA Phone: +1 732 420 1571 Fax: +1 732 368 1192 Email: acmorton@att.com URI: http://home.comcast.net/~acmacm/ Matt Mathis Google Email: mattmathis@google.com Morton & Mathis Expires September 14, 2017 [Page 21]