| Network Working Group | A. Morton |
| Internet-Draft | AT&T Labs |
| Intended status: Standards Track | M. Mathis |
| Expires: May 3, 2017 | |
| October 30, 2016 |
Initial Performance Metric Registry Entries Part 2: MBM
draft-morton-ippm-mbm-registry-00
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 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].
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 May 3, 2017.
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
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.
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].
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.
This section gives an initial registry entry for a Model-Based Metric (MBM) Sustained Burst Metric.
This category includes multiple indexes to the registry entries, the element ID and metric name.
<insert numeric identifier, an integer>
<insert name according to metric naming convention>
OWMBM_Active_IP-TCP-SustainedBurst_RFCXXXXsecY_Enumerated_PFI
URI: Prefix urn:ietf:metric
URL: http://<TBD by IANA>/<name>
TBD.
<reference to the RFC of spec where the registry entry is defined>
RFCXXXXsecY
<org or person >
<currently 1.0>
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.
<Full bibliographic reference to an immutable doc.>
<specific section reference and additional clarifications, if needed>
Mathis, M. and A. Morton, "Model Based Metrics for Bulk Transport Capacity", draft-ietf-ippm-model-based- metrics-08 (work in progress), July 2016.
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., Kalidindi, S., and M. Zekauskas, "A One-way Packet Loss Metric for IPPM", RFC 2680, DOI 10.17487/RFC2680, September 1999, <http://www.rfc-editor.org/info/rfc2680>.
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:
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, <http://www.rfc-editor.org/info/rfc7679>.
<specific section reference and additional clarifications, if needed>
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.
<list and specify Fixed Parameters, input factors that must be determined and embedded in the measurement system for use when needed>
Type-P as defined in Section 13 of [RFC2330]:
Other measurement parameters:
This category includes columns for references to relevant sections of the RFC(s) and any supplemental information needed to ensure an unambiguous methods for implementations.
<for metric, insert relevant section references and supplemental info>
The method of measurement is described in Section 8.1.5 of [I-D.ietf-ippm-model-based-metrics].
@@@@<more could be said here about loss and RTT methods>
<list of generation parameters and section/spec references if needed>
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.
<insert the measured results based on a filtered version of the packets observed, and this section provides the filter details (when present), and section reference>.
NA
<insert time distribution details, or how this is diff from the filter>
NA
<list of run-time parameters, and any reference(s)>.
The following parameters are described in [RFC2330]
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.
The following MBM-specific parameters are as defined in Section of 7.2 [I-D.ietf-ippm-model-based-metrics]:
Additional MBM-specific parameters may be calculated by the measurement system itself, or they may be supplied as additional Run-time parameters:
<lists the names of the different roles from the measurement method>
[I-D.ietf-ippm-model-based-metrics].
as described in Section 3 of
This category specifies all details of the Output of measurements using the metric.
<insert name of the output type, raw or a selected summary statistic>
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
<pointer to section/spec where output type/format is defined>
For all outputs ---
PFI:
@@@@<TBP>@@@@
Loss Ratio:
@@@@<TBP>@@@@
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:
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].
<insert units for the measured results, and the reference specification>.
PFI: Enumerated{Pass, Fail, Inconclusive}
Loss Ratio: RatioPercent
Mean Round-trip Time: Seconds
<describe the error calibration, a way to indicate that the results were collected in a calbration mode of operation, and a way to report internal status metrics related to calibration, such as time offset>
<current or depricated>
<name of individual or Internet Draft, etc.>
1.0
YYYY-MM-DD
Additional (Informational) details for this entry
This section gives an initial registry entry for ....
This category includes multiple indexes to the registry entries, the element ID and metric name.
<insert numeric identifier, an integer>
<insert name according to metric naming convention>
URI: Prefix urn:ietf:params:performance:metric
URL:
TBD.
<reference to the RFC of spec where the registry entry is defined>
<org or person >
<currently 1.0>
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.
<Full bibliographic reference to an immutable doc.>
<specific section reference and additional clarifications, if needed>
<list and specify Fixed Parameters, input factors that must be determined and embedded in the measurement system for use when needed>
This category includes columns for references to relevant sections of the RFC(s) and any supplemental information needed to ensure an unambiguous methods for implementations.
<for metric, insert relevant section references and supplemental info>
<list of generation parameters and section/spec references if needed>
<insert the measured results based on a filtered version of the packets observed, and this section provides the filter details (when present), and section reference>.
<insert time distribution details, or how this is diff from the filter>
<list of run-time parameters, and any reference(s)>.
<lists the names of the different roles from the measurement method>
This category specifies all details of the Output of measurements using the metric.
<insert name of the output type, raw or a selected summary statistic>
<pointer to section/spec where output type/format is defined>
<insert units for the measured results, and the reference specification>.
<describe the error calibration, a way to indicate that the results were collected in a calbration mode of operation, and a way to report internal status metrics related to calibration, such as time offset>
<current or depricated>
<name of individual or Internet Draft, etc.>
1.0
YYYY-MM-DD
Additional (Informational) details for this entry
These registry entries represent no known security implications for Internet Security. Each referenced Metric contains a Security Considerations section.
IANA is requested to populate The Performance Metric Registry defined in [I-D.ietf-ippm-metric-registry] with the values defined above.
<more is needed here>
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.