Network Working Group                                          A. Morton
Internet-Draft                                                 AT&T Labs
Intended status: Standards Track                              M. Bagnulo
Expires: January 1, May 2, 2018                                                UC3M
                                                              P. Eardley
                                                                      BT
                                                              K. D'Souza
                                                               AT&T Labs
                                                           June 30,
                                                        October 29, 2017

              Initial Performance Metric Registry Entries
                  draft-ietf-ippm-initial-registry-04
                  draft-ietf-ippm-initial-registry-05

Abstract

   This memo defines the Initial Entries for the Performance Metrics
   Registry.  This version includes:

   * Revised several Poisson streams to Periodic, sections 4 & 5.

   * Addition of Loss Ratio metric in various sections (multiple ICMP (ping) metrics
   per section).

   * All in section 4, 5, 6, 7, and 8 parameters reference YANG types for
   alternate data formats.

   * implementation of standard naming format for parameters. 9.

   * First implementation of many IANA early-review comments. Passive TCP RTT metrics in section 10.

   Still need: Add MBM metric entry.

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/. https://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 January 1, May 2, 2018.

Copyright Notice

   Copyright (c) 2017 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)
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   6   7
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   7   8
   3.  Registry Categories and Columns . . . . . . . . . . . . . . .   7   8
   4.  UDP Round-trip Latency and Loss Registry Entries  . . . . . .   8   9
     4.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .   9  10
       4.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .   9  10
       4.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .   9  10
       4.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .   9  10
       4.1.4.  Description . . . . . . . . . . . . . . . . . . . . .   9  10
       4.1.5.  Change Controller . . . . . . . . . . . . . . . . . .   9  10
       4.1.6.  Version (of Registry Format)  . . . . . . . . . . . .   9  10
     4.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  10  11
       4.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  10  11
       4.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  11  12
     4.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  11  12
       4.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  12  13
       4.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  13  14
       4.3.3.  Traffic Filtering (observation) Details . . . . . . .  13  14
       4.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  13  15
       4.3.5.  Run-time Parameters and Data Format . . . . . . . . .  13  15
       4.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  14  15
     4.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  15  16
       4.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  15  16
       4.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  15  16
       4.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  16  17
       4.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  16  17
     4.5.  Administrative items  . . . . . . . . . . . . . . . . . .  17  18
       4.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  17  18
       4.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  17  18
       4.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  17  18
       4.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  17  18
     4.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  17  18
   5.  Packet Delay Variation Registry Entry . . . . . . . . . . . .  17  18
     5.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  17  18
       5.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  17  18
       5.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  18
       5.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  18  19
       5.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  18  19
       5.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  18  19
       5.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  18  19
     5.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  18  19
       5.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  18  19
       5.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  19  20
     5.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  20  21
       5.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  20  21
       5.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  21  22
       5.3.3.  Traffic Filtering (observation) Details . . . . . . .  21  22
       5.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  22  23
       5.3.5.  Run-time Parameters and Data Format . . . . . . . . .  22  23
       5.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  22  23
     5.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  22  23
       5.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  23  24
       5.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  23  24
       5.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  23  24
       5.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  24  25
     5.5.  Administrative items  . . . . . . . . . . . . . . . . . .  24  25
       5.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  24  25
       5.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  25  26
       5.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  25  26
       5.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  25  26
     5.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  25  26
   6.  DNS Response Latency and Loss Registry Entries  . . . . . . .  25  26
     6.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  25  26
       6.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  25  26
       6.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  26  27
       6.1.3.  URI . . . . . . . . . . . . . . . . . . . . . . . . .  26  27
       6.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  26  27
       6.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  26  27
       6.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  26  27
     6.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  26  27
       6.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  26  27
       6.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  27  28
     6.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  29  30
       6.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  29  30
       6.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  30  31
       6.3.3.  Traffic Filtering (observation) Details . . . . . . .  31  32
       6.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  31  32
       6.3.5.  Run-time Parameters and Data Format . . . . . . . . .  31  32
       6.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  32  33
     6.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  33  34
       6.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  33  34
       6.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  33  34
       6.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  33  34
       6.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  34  35
     6.5.  Administrative items  . . . . . . . . . . . . . . . . . .  34  35
       6.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  34  35
       6.5.2.  Requestor . . . . . . . . . . . . . . . . . . . . . .  34  35
       6.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  34  35
       6.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  34  35
     6.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  34  35
   7.  UDP Poisson One-way Delay and Loss Registry Entries . . . . .  35  36
     7.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  35  36
       7.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  35  36
       7.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  35  36
       7.1.3.  URI and URL . . . . . . . . . . . . . . . . . . . . .  36  37
       7.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  36  37
     7.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  36  37
       7.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  36  37
       7.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  37  38
     7.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  38  39
       7.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  38  39
       7.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  39  40
       7.3.3.  Traffic Filtering (observation) Details . . . . . . .  40  41
       7.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  40  41
       7.3.5.  Run-time Parameters and Data Format . . . . . . . . .  40  41
       7.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  41  42
     7.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  41  42
       7.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  41  42
       7.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  41  42
       7.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  44  45
       7.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  44  45
     7.5.  Administrative items  . . . . . . . . . . . . . . . . . .  45  46
       7.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  45  46
       7.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  45  46
       7.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  45  46
       7.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  45  46
     7.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  45  46
   8.  UDP Periodic One-way Delay and Loss Registry Entries  . . . .  46  47
     8.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  46  47
       8.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  46  47
       8.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  46  47
       8.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  47  48
       8.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  47  48
     8.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  47  48
       8.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  47  48
       8.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  48  49
     8.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  49  50
       8.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  49  50
       8.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  50  51
       8.3.3.  Traffic Filtering (observation) Details . . . . . . .  51  52
       8.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  51  52
       8.3.5.  Run-time Parameters and Data Format . . . . . . . . .  51  52
       8.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  52  53
     8.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  52  53
       8.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  52  53
       8.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  52  53
       8.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  55  56
       8.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  55  56
     8.5.  Administrative items  . . . . . . . . . . . . . . . . . .  56  57
       8.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  56  57
       8.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  56  57
       8.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  56  57
       8.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  56  57
     8.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  56  57
   9.  ver08 BLANK  ICMP Round-trip Latency and Loss Registry Entry  . . . . . . . . . . . Entries . . . . . .  56  57
     9.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  56  58
       9.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  56  58
       9.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  56  58
       9.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  57  58
       9.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  57  58
       9.1.5.  Reference . . . . . . . . . . . . . . . . . . . . . .  57
       9.1.6.  Change Controller . . . . . . . . . . . . . . . . . .  57
       9.1.7.  59
       9.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  57  59
     9.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  57  59
       9.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  57  59
       9.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  57  60
     9.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  57  61
       9.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  58  61
       9.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  58  62
       9.3.3.  Traffic Filtering (observation) Details . . . . . . .  58  63
       9.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  58  63
       9.3.5.  Run-time Parameters and Data Format . . . . . . . . .  58  63
       9.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  58  64
     9.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  58  64
       9.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  58  64
       9.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  58  64
       9.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  58  66
       9.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  59  66
     9.5.  Administrative items  . . . . . . . . . . . . . . . . . .  59  67
       9.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  59  67
       9.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . . . . . .  59  67
       9.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  59  67
       9.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  59  67
     9.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  59  67

   10. Example RTCP-XR TCP Round-Trip Delay and Loss Registry Entry  . . . . Entries  . . . . . . .  67
     10.1.  Summary  . . . .  59
     10.1.  Registry Indexes . . . . . . . . . . . . . . . . . . . .  59  67
       10.1.1.  Identifier . . .  ID (Identifier)  . . . . . . . . . . . . . . . . . .  59  68
       10.1.2.  Name . . . . . . . . . . . . . . . . . . . . . . . .  60  68
       10.1.3.  URI  URIs . . . . . . . . . . . . . . . . . . . . . . . .  60  68
       10.1.4.  Status  Description  . . . . . . . . . . . . . . . . . . . .  68
       10.1.5.  Change Controller  . . .  60
       10.1.5.  Requestor . . . . . . . . . . . . . .  69
       10.1.6.  Version (of Registry Format) . . . . . . .  60
       10.1.6.  Revision . . . . .  69
     10.2.  Metric Definition  . . . . . . . . . . . . . . . . .  60
       10.1.7.  Revision Date . .  69
       10.2.1.  Reference Definitions  . . . . . . . . . . . . . . .  69
       10.2.2.  Fixed Parameters . .  60
       10.1.8.  Description . . . . . . . . . . . . . . . .  71
     10.3.  Method of Measurement  . . . .  60
       10.1.9.  Reference Specification(s) . . . . . . . . . . . . .  60
     10.2.  Metric Definition  72
       10.3.1.  Reference Methods  . . . . . . . . . . . . . . . . .  72
       10.3.2.  Packet Stream Generation . . .  60
       10.2.1.  Reference Definition . . . . . . . . . . .  74
       10.3.3.  Traffic Filtering (observation) Details  . . . . . .  60
       10.2.2.  Fixed  74
       10.3.4.  Sampling Distribution  . . . . . . . . . . . . . . .  74
       10.3.5.  Run-time Parameters and Data Format  . . . . . . . .  74
       10.3.6.  Roles  . . . . . . . . . .  61
     10.3.  Method of Measurement . . . . . . . . . . . . .  75
     10.4.  Output . . . .  61
       10.3.1.  Reference Method . . . . . . . . . . . . . . . . . .  61
       10.3.2.  Stream . . .  75
       10.4.1.  Type and Stream Parameters . . . . . . . . .  62
       10.3.3.  Output Type and Data Format . . . . . . . . . . . .  62
       10.3.4. . . .  75
       10.4.2.  Reference Definition . . . . . . . . . . . . . . . .  76
       10.4.3.  Metric Units . . . . . . . . . . . . . . . . . . . .  62
       10.3.5.  Run-time Parameters and Data Format  78
       10.4.4.  Calibration  . . . . . . . . . . .  62
     10.4.  Comments and Remarks . . . . . . . . .  78
     10.5.  Administrative items . . . . . . . . .  64
   11. . . . . . . . . .  78
       10.5.1.  Status . . . . . . . . . . . . . . . . . . . . . . .  78
       10.5.2.  Requestor (keep?)  . . . . . . . . . . . . . . . . .  78
       10.5.3.  Revision History . . . . . . . . . . . . . . . . . . . . . .  64
   12. Security Considerations  78
       10.5.4.  Revision Date  . . . . . . . . . . . . . . . . . . .  64
   13. IANA Considerations  78
     10.6.  Comments and Remarks . . . . . . . . . . . . . . . . . .  78
   11. ver08 BLANK Registry Entry  . . .  65
   14. Acknowledgements . . . . . . . . . . . . . .  79
     11.1.  Summary  . . . . . . . .  65
   15. References . . . . . . . . . . . . . . . .  79
       11.1.1.  ID (Identifier)  . . . . . . . . .  65
     15.1.  Normative References . . . . . . . . .  79
       11.1.2.  Name . . . . . . . . .  65
     15.2.  Informative References . . . . . . . . . . . . . . .  79
       11.1.3.  URIs . .  67
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .  79
       11.1.4.  Description  .  69

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 an initial set of entries for the Performance
   Metric Registry.  It uses terms and definitions from the IPPM
   literature, primarily [RFC2330].  Proponents of Passive Performance
   Metrics are encouraged to develop a similar document. . . . . . . . . . . . . . . . . . . .  79
       11.1.5.  Reference  . . . . . . . . . . . . . . . . . . . . .  79
       11.1.6.  Change Controller  . . . . . . . . . . . . . . . . .  79
       11.1.7.  Version (of Registry Format) . . . . . . . . . . . .  79
     11.2.  Metric Definition  . . . . . . . . . . . . . . . . . . .  79
       11.2.1.  Reference Definition . . . . . . . . . . . . . . . .  80
       11.2.2.  Fixed Parameters . . . . . . . . . . . . . . . . . .  80
     11.3.  Method of Measurement  . . . . . . . . . . . . . . . . .  80
       11.3.1.  Reference Method . . . . . . . . . . . . . . . . . .  80
       11.3.2.  Packet Stream Generation . . . . . . . . . . . . . .  80
       11.3.3.  Traffic Filtering (observation) Details  . . . . . .  80
       11.3.4.  Sampling Distribution  . . . . . . . . . . . . . . .  80
       11.3.5.  Run-time Parameters and Data Format  . . . . . . . .  80
       11.3.6.  Roles  . . . . . . . . . . . . . . . . . . . . . . .  80

     11.4.  Output . . . . . . . . . . . . . . . . . . . . . . . . .  81
       11.4.1.  Type . . . . . . . . . . . . . . . . . . . . . . . .  81
       11.4.2.  Reference Definition . . . . . . . . . . . . . . . .  81
       11.4.3.  Metric Units . . . . . . . . . . . . . . . . . . . .  81
       11.4.4.  Calibration  . . . . . . . . . . . . . . . . . . . .  81
     11.5.  Administrative items . . . . . . . . . . . . . . . . . .  81
       11.5.1.  Status . . . . . . . . . . . . . . . . . . . . . . .  81
       11.5.2.  Requestor  . . . . . . . . . . . . . . . . . . . . .  81
       11.5.3.  Revision . . . . . . . . . . . . . . . . . . . . . .  81
       11.5.4.  Revision Date  . . . . . . . . . . . . . . . . . . .  81
     11.6.  Comments and Remarks . . . . . . . . . . . . . . . . . .  81
   12. Example RTCP-XR Registry Entry  . . . . . . . . . . . . . . .  82
     12.1.  Registry Indexes . . . . . . . . . . . . . . . . . . . .  82
       12.1.1.  Identifier . . . . . . . . . . . . . . . . . . . . .  82
       12.1.2.  Name . . . . . . . . . . . . . . . . . . . . . . . .  82
       12.1.3.  URI  . . . . . . . . . . . . . . . . . . . . . . . .  82
       12.1.4.  Status . . . . . . . . . . . . . . . . . . . . . . .  82
       12.1.5.  Requestor  . . . . . . . . . . . . . . . . . . . . .  82
       12.1.6.  Revision . . . . . . . . . . . . . . . . . . . . . .  82
       12.1.7.  Revision Date  . . . . . . . . . . . . . . . . . . .  82
       12.1.8.  Description  . . . . . . . . . . . . . . . . . . . .  82
       12.1.9.  Reference Specification(s) . . . . . . . . . . . . .  83
     12.2.  Metric Definition  . . . . . . . . . . . . . . . . . . .  83
       12.2.1.  Reference Definition . . . . . . . . . . . . . . . .  83
       12.2.2.  Fixed Parameters . . . . . . . . . . . . . . . . . .  83
     12.3.  Method of Measurement  . . . . . . . . . . . . . . . . .  84
       12.3.1.  Reference Method . . . . . . . . . . . . . . . . . .  84
       12.3.2.  Stream Type and Stream Parameters  . . . . . . . . .  84
       12.3.3.  Output Type and Data Format  . . . . . . . . . . . .  84
       12.3.4.  Metric Units . . . . . . . . . . . . . . . . . . . .  84
       12.3.5.  Run-time Parameters and Data Format  . . . . . . . .  85
     12.4.  Comments and Remarks . . . . . . . . . . . . . . . . . .  86
   13. Revision History  . . . . . . . . . . . . . . . . . . . . . .  86
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  87
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  87
   16. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  87
   17. References  . . . . . . . . . . . . . . . . . . . . . . . . .  88
     17.1.  Normative References . . . . . . . . . . . . . . . . . .  88
     17.2.  Informative References . . . . . . . . . . . . . . . . .  90
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  92

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 an initial set of entries for the Performance
   Metric Registry.  It uses terms and definitions from the IPPM
   literature, primarily [RFC2330].

   Although there are several standard templates several standard templates for organizing
   specifications of performance metrics (see [RFC2679] for an example
   of the traditional IPPM template, based to large extent on the
   Benchmarking Methodology Working Group's traditional template in
   [RFC1242], and see [RFC6390] for a similar template), none of these
   templates were intended to become the basis for the columns of an
   IETF-wide registry of metrics.  While examinating aspects of metric
   specifications which need to be registered, it became clear that none
   of the existing metric templates fully satisfies the particular needs
   of a registry.

   Therefore, [I-D.ietf-ippm-metric-registry] defines the overall format
   for a Performance Metric Registry.  Section 5 of
   [I-D.ietf-ippm-metric-registry] also gives guidelines for those
   requesting registration of a Metric, that is the creation of entry(s)
   in the Performance Metric Registry: "In essence, there needs to be
   evidence that a candidate Registered Performance Metric has
   significant industry interest, or has seen deployment, and there is
   agreement that the candidate Registered Performance Metric serves its
   intended purpose."  The process in [I-D.ietf-ippm-metric-registry]
   also requires that new entries are administered by IANA through
   Expert Review, which will ensure that the metrics are tightly
   defined.

2.  Scope

   This document defines 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.  Most 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.  Registry Categories and Columns

   This section provides the categories and columns of the registry, for
   easy reference.  An entry (row) therefore gives a complete
   description of a Registered Metric.

 Registry Categories and Columns, shown as
                                            Category
                                            ------------------
                                            Column |  Column |

Summary
------------------------------------------------------------------------
Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver |

Metric Definition
-----------------------------------------
Reference Definition | Fixed Parameters |

Method of Measurement
---------------------------------------------------------------------
Reference | Packet     | Traffic | Sampling     | Run-time   | Role |
Method    | Stream     | Filter  | Distribution | Parameters |      |
          | Generation |
Output
-----------------------------------------
Type | Reference  | Units | Calibration |
     | Definition |       |             |

Administrative Information
----------------------------------
Status |Request | Rev | Rev.Date |

Comments and Remarks
--------------------

4.  UDP Round-trip Latency and Loss Registry Entries

   This section specifies an initial registry entry for the UDP Round-
   trip Latency, and another entry for UDP Round-trip Loss Ratio.

   Note: Each Registry entry only produces a "raw" output or a
   statistical summary.  To describe both "raw" and one or more
   statistics efficiently, the Identifier, Name, and Output Categories
   can be split and a single section can specify two or more closely-
   related metrics.  This section specifies two Registry entries with
   many common columns.  See Section 7 for an example specifying
   multiple Registry entries with many common columns.

   All column entries beside the ID, Name, Description, and Output
   Reference Method categories are the same, thus this section proposes
   two closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to each Named Metric.

4.1.  Summary

   This category includes multiple indexes to the registry entry: the
   element ID and metric name.

4.1.1.  ID (Identifier)

   <insert a numeric identifier, an integer, TBD>

   IANA is asked to assign different numeric identifiers to each of the
   two Named Metrics.

4.1.2.  Name

   <insert name according to metric naming convention>

   RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile

   RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio

4.1.3.  URIs

   URN: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

4.1.4.  Description

   RTDelay: This metric assesses the delay of a stream of packets
   exchanged between two hosts (which are the two measurement points),
   and the Output is the Round-trip delay for all successfully exchanged
   packets expressed as the 95th percentile of their conditional delay
   distribution.

   RTLoss: This metric assesses the loss ratio of a stream of packets
   exchanged between two hosts (which are the two measurement points),
   and the Output is the Round-trip loss ratio for all successfully
   exchanged packets expressed as a percentage.

4.1.5.  Change Controller

   IETF

4.1.6.  Version (of Registry Format)

   1.0

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

   <Full bibliographic reference to an immutable doc.>

   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay
   Metric for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <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 [RFC2681] 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.

   Morton, A., "Round-trip Packet Loss Metrics", RFC 6673, August 2012.

   [RFC6673]

   Both delay and loss metrics employ a maximum waiting time for
   received packets, so the count of lost packets to total packets sent
   is the basis for the loss ratio calculation as per Section 6.1 of
   [RFC6673].

4.2.2.  Fixed Parameters

   <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]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255

      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: the checksum MUST be calculated and included in the
         header

   o  UDP Payload

      *  total of 100 bytes

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time

      *  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].

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

   <for metric, insert relevant section references and supplemental
   info>

   The methodology for this metric is defined as Type-P-Round-trip-
   Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section
   3.6 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under
   Fixed Parameters.  However, the Periodic stream will be generated
   according to [RFC3432].

   The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is the waiting time used as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for the RTLoss metric.

   The calculations on the delay (RTT) SHALL be performed on the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packet delays are stored, the process
   which calculates the RTT value MAY enforce the Tmax threshold on
   stored values before calculations.  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.

   The reference method requires some way to distinguish between
   different packets in a stream to establish correspondence between
   sending times and receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the Src or included with each packet to disambiguate
   packet reordering if it occurs.

   If a standard measurement protocol is employed, then the measurement
   process will determine the sequence numbers or timestamps applied to
   test packets after the Fixed and Runtime parameters are passed to
   that process.  The chosen measurement protocol will dictate the
   format of sequence numbers and time-stamps, if they are conveyed in
   the packet payload.

   Refer to Section 4.4 of [RFC6673] for expanded discussion of the
   instruction to "send a Type-P packet back to the Src as quickly as
   possible" in Section 2.6 of RFC 2681 [RFC2681].  Section 8 of
   [RFC6673] presents additional requirements which MUST be included in
   the method of measurement for this metric.

4.3.2.  Packet Stream Generation

   <list of generation parameters and section/spec references if needed>

   This section gives the details of the packet traffic which is the
   basis for measurement.  In IPPM metrics, this is called the Stream,
   and can easily be described by providing the list of stream
   parameters.

   Section 3 of [RFC3432] prescribes the method for generating Periodic
   streams using associated parameters.

   incT  the nominal duration of inter-packet interval, first bit to
      first bit, with value 0.0200, 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).

   dT the duration of the interval for allowed sample start times, with
      value 1.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).

   T0 the actual start time of the periodic stream, (format "date-and-
      time" as specified in Section 5.6 of [RFC3339], see also Section 3
      of [RFC6991]).

   NOTE: an initiation process with a number of control exchanges
   resulting in unpredictable start times (within a time interval) may
   be sufficient to avoid synchronization of periodic streams, and
   therefore a valid replacement for selecting a start time at random
   from a fixed interval.

   The T0 parameter will be reported as a measured parameter.
   Parameters incT and dT are Fixed Parameters.

4.3.3.  Traffic Filtering (observation) Details

   The measured results based on a filtered version of the packets
   observed, and this section provides the filter details (when
   present).

   <section reference>.

   NA

4.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from the
   filter>

   NA

4.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the measurement system, and reported with the results
   for the context to be complete.

   <list of run-time parameters, and their data formats>

   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])

   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.

4.3.6.  Roles

   <lists the names of the different roles from the measurement method>

   Src  launches each packet and waits for return transmissions from
      Dst.

   Dst  waits for each packet from Src and sends a return packet to Src.

4.4.  Output

   This category specifies all details of the Output of measurements
   using the metric.

4.4.1.  Type

   <insert name of the output type, raw or a selected summary statistic>

   Percentile -- for the conditional distribution of all packets with a
   valid value of Round-trip delay (undefined delays are excluded), a
   single value corresponding to the 95th percentile, as follows:

   See section 4.1 of [RFC3393] for organizing
   specifications details on the conditional
   distribution to exclude undefined values of performance metrics (see [RFC2679] delay, and Section 5 of
   [RFC6703] for an example background on this analysis choice.

   The percentile = 95, meaning that the reported delay, "95Percentile",
   is the smallest value of Round-trip delay for which the traditional IPPM template, based to large extent on Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the
   Benchmarking Methodology Working Group's traditional template singleton
   Round-trip delay values in
   [RFC1242], and see [RFC6390] the conditional distribution.  See section
   11.3 of [RFC2330] for a similar template), none the definition of these
   templates were intended the percentile statistic
   using the EDF.

   LossRatio -- the count of lost packets to become total packets sent is the
   basis for the columns of an
   IETF-wide registry of metrics.  While examinating aspects of metric
   specifications which need to be registered, it became clear that none loss ratio calculation as per Section 6.1 of [RFC6673].

4.4.2.  Reference Definition

   <describe the existing metric templates fully satisfies reference data format for each type of result>

   For all outputs ---

   T0 the particular needs start of a registry.

   Therefore, [I-D.ietf-ippm-metric-registry] defines 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 overall format
   for end of a Performance Metric Registry. measurement interval, (format "date-and-time" as
      specified in Section 5 5.6 of
   [I-D.ietf-ippm-metric-registry] [RFC3339], see also gives guidelines for those
   requesting registration Section 3 of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 of
      [RFC2330].

   TotalPkts  the count of packets sent by the Src to Dst during the
      measurement interval.

   For
   RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile:

   95Percentile  The time value of the result is expressed in units of
      seconds, as a Metric, that is 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 creation 64-bit NTP timestamp as

   For

   RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio:

   Percentile  The numeric value of entry(s)
   in the Performance Metric Registry: "In essence, there needs result is expressed in units of
      lost packets to be
   evidence that total packets times 100%, as a candidate Registered Performance positive value of
      type decimal64 with fraction digits = 9 (see section 9.3 of
      [RFC6020]) with resolution of 0.0000000001.

4.4.3.  Metric has
   significant industry interest, or has seen deployment, Units

   <insert units for the measured results, and there is
   agreement that the candidate Registered Performance Metric serves its
   intended purpose." reference
   specification>.

   The process in [I-D.ietf-ippm-metric-registry]
   also requires that new entries are administered by IANA through
   Expert Review, which will ensure that the metrics are tightly
   defined.

2.  Scope

   This document defines the initial set 95th Percentile of Performance Metrics Registry
   entries, for which IETF approval (following development Round-trip Delay is expressed in seconds.

   The Round-trip Loss Ratio is expressed as a percentage of lost
   packets to total packets sent.

4.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means to quantify the IP
   Performance Metrics (IPPM) Working Group) will satisfy
   systematic and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback at the
   requirement for Expert Review.  Note Source
   host that all are Active Performance
   Metrics, which are based on RFCs prepared in includes as much of the IPPM working group measurement system as possible,
   performs address manipulation as needed, and provides some form of the IETF, according
   isolation (e.g., deterministic delay) to their framework [RFC2330] and its updates.

3.  Registry Categories avoid send-receive interface
   contention.  Some portion of the random and Columns

   This section provides systematic error can be
   characterized this way.

   When a measurement controller requests a calibration measurement, the categories
   loopback is applied and columns of the registry, for
   easy reference.  An entry (row) therefore gives result is output in the same format as a complete
   description of
   normal measurement with additional indication that it is a Registered Metric.

 Registry Categories
   calibration result.

   Both internal loopback calibration and Columns, shown as
                                            Category
                                            ------------------
                                            Column |  Column |

Summary
------------------------------------------------------------------------
Identifier | Name | URIs | Desc. | Reference | Change Controller | Ver | clock synchronization can be
   used to estimate the *available accuracy* of the Output Metric Definition
-----------------------------------------
Reference Definition | Fixed Parameters |

Method Units.
   For example, repeated loopback delay measurements will reveal the
   portion of Measurement
---------------------------------------------------------------------
Reference | Packet     | Traffic | Sampling     | Run-time   | Role |
Method    | Stream     | Filter  | Distribution | Parameters |      |
          | Generation | the Output
-----------------------------------------
Type | Reference  | Units | Calibration |
     | Definition |       |             | result resolution which is the result of system
   noise, and thus inaccurate.

4.5.  Administrative Information
---------------------------------- items

4.5.1.  Status |Request | Rev | Rev.Date |

   <current or deprecated>

4.5.2.  Requestor (keep?)

   name or RFC, etc.

4.5.3.  Revision

   1.0

4.5.4.  Revision Date

   YYYY-MM-DD

4.6.  Comments and Remarks
--------------------

4.  UDP Round-trip Latency and Loss

   Additional (Informational) details for this entry

5.  Packet Delay Variation Registry Entries Entry

   This section specifies gives an initial registry entry for the UDP Round-
   trip Latency, and another entry for UDP Round-trip Loss Ratio. a Packet Delay
   Variation metric.

   Note: Each If each Registry entry should only produces produce a "raw" output or a
   statistical summary.  To describe both "raw" and one or more
   statistics efficiently, summary, then the Identifier, Name, and Output Categories "Output" Category can be split and a single this
   section can specify become two or more closely-
   related closely-related metrics.

5.1.  Summary

   This category includes multiple indexes to the registry entries, the
   element ID and metric name.

   <skipping some Summary columns for now>

5.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>

5.1.2.  Name

   <insert name according to metric naming convention>

   OWPDV_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile

5.1.3.  URIs

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

5.1.4.  Description

   An assessment of packet delay variation with respect to the minimum
   delay observed on the periodic stream, and the Output is expressed as
   the 95th percentile of the packet delay variation distribution.

5.1.5.  Change Controller

   <org or person >

   IETF

5.1.6.  Version (of Registry Format)

   1.0

5.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.

5.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   Paxson, V., Almes, G., Mahdavi, J., and M.  Mathis, "Framework for IP
   Performance Metrics", RFC 2330, May 1998.  [RFC2330]

   Demichelis, C. and P.  Chimento, "IP Packet Delay Variation Metric
   for IP Performance Metrics (IPPM)", RFC 3393, November 2002.
   [RFC3393]

   Morton, A. and B.  Claise, "Packet Delay Variation Applicability
   Statement", RFC 5481, March 2009.  [RFC5481]

   Mills, D., Martin, J., Burbank, J., and W.  Kasch, "Network Time
   Protocol Version 4: Protocol and Algorithms Specification", RFC 5905,
   June 2010.[RFC5905]

   <specific section specifies two Registry entries with
   many common columns. reference and additional clarifications, if needed>
   See Section 7 for an example specifying
   multiple Registry entries with many common columns.

   All column entries beside the ID, Name, Description, sections 2.4 and Output
   Reference Method categories 3.4 of [RFC3393].  Singleton delay differences
   measured are referred to by the same, thus variable name "ddT" (applicable to
   all forms of delay variation).  However, this metric entry specifies
   the PDV form defined in section proposes
   two closely-related registry entries.  As a result, IANA 4.2 of [RFC5481], where the singleton
   PDV for packet i is also
   asked referred to assign corresponding URNs by the variable name "PDV(i)".

5.2.2.  Fixed Parameters

   <list and URLs specify Fixed Parameters, input factors that must be
   determined and embedded in the measurement system for use when
   needed>

   o  IPv4 header values:

      *  DSCP: set to each Named Metric.

4.1.  Summary

   This category includes multiple indexes 0

      *  TTL: set to the registry entry: the
   element ID and metric name.

4.1.1.  ID (Identifier)

   <insert a numeric identifier, an integer, TBD>

   IANA is asked 255

      *  Protocol: Set to assign different numeric identifiers 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to each of the
   two Named Metrics.

4.1.2.  Name

   <insert name according 0

      *  Hop Count: set to metric naming convention>

   RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile

   RTLoss_Active_IP-UDP-Poisson_RFCXXXXsecY_Percent_LossRatio

4.1.3.  URIs

   URN: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

4.1.4.  Description

   RTDelay: This metric assesses 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: the checksum MUST be calculated and included in the delay
         header

   o  UDP Payload

      *  total of 200 bytes

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value 3.0, expressed in
      units of seconds, as a stream 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].

   F  a selection function unambiguously defining the packets
   exchanged between two hosts (which are from the two measurement points),
   and
      stream selected for the Output is metric.  See section 4.2 of [RFC5481] for
      the Round-trip delay PDV form.

   See the Packet Stream generation category for all successfully exchanged
   packets expressed as two additional Fixed
   Parameters.

5.3.  Method of Measurement

   This category includes columns for references to relevant sections of
   the 95th percentile RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations.

5.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   See section 2.6 and 3.6 of their conditional delay
   distribution.

   RTLoss: [RFC3393] for general singleton element
   calculations.  This metric assesses entry requires implementation of the loss ratio PDV
   form defined in section 4.2 of a stream [RFC5481].  Also see measurement
   considerations in section 8 of packets
   exchanged [RFC5481].

   The reference method distinguishes between two hosts (which are the two measurement points), long-delayed packets and the Output is the Round-trip loss ratio for all successfully
   exchanged
   lost packets expressed as by implementing a percentage.

4.1.5.  Change Controller

   IETF

4.1.6.  Version (of Registry Format)

   1.0

4.2.  Metric Definition

   This category includes columns maximum waiting time for packet
   arrival.  Tmax is the waiting time used as the threshold to prompt declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay.

   The calculations on the entry of one-way delay SHALL be performed on the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all necessary
   details related to packet delays are stored, the metric definition, including process
   which calculates the RFC reference
   and one-way delay value MAY enforce the Tmax
   threshold on stored values of input factors, called fixed parameters.

4.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay
   Metric for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific before calculations.  See section reference and additional clarifications, if needed>

   Section 2.4 4.1 of [RFC2681] provides
   [RFC3393] for details on the reference definition conditional distribution to exclude
   undefined values of the
   singleton (single value) Round-trip delay metric. delay, and Section 3.4 5 of
   [RFC2681] provides the [RFC6703] for background
   on this analysis choice.

   The reference definition expanded method requires some way to cover a
   multi-singleton sample.  Note that terms such as singleton and sample
   are defined distinguish between
   different packets in Section 11 of [RFC2330].

   Note that although the [RFC2681] definition of "Round-trip-Delay a stream to establish correspondence between Src
   sending times and Dst" is directionally ambiguous in the text, this
   metric tightens receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the definition further Src or included with each packet to recognize that the host in disambiguate
   packet reordering if it occurs.

   If a standard measurement protocol is employed, then the "Src" role measurement
   process will send determine the first packet sequence numbers or timestamps applied to "Dst", and ultimately
   receive
   test packets after the corresponding return packet from "Dst" (when neither Fixed and Runtime parameters are
   lost).

   Finally, note that the variable "dT" is used in [RFC2681] to refer passed to
   that process.  The chosen measurement protocol will dictate the value
   format of Round-trip delay in metric definitions sequence numbers and methods.  The
   variable "dT" has been re-used time-stamps, if they are conveyed in other IPPM literature to refer to
   different quantities, and cannot be used as a global variable name.

   Morton, A., "Round-trip
   the packet payload.

5.3.2.  Packet Loss Metrics", RFC 6673, August 2012.

   [RFC6673]

   Both delay Stream Generation

   <list of generation parameters and loss metrics employ a maximum waiting time for
   received packets, so section/spec references if needed>

   This section gives the count details of lost packets to total packets sent the packet traffic which is the
   basis for measurement.  In IPPM metrics, this is called the loss ratio calculation as per Section 6.1 of
   [RFC6673].

4.2.2.  Fixed Parameters

   <list Stream,
   and specify Fixed Parameters, input factors that must can easily be
   determined and embedded in described by providing the measurement system for use when
   needed>

   Type-P as defined in list of stream
   parameters.

   Section 13 3 of [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255

      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: [RFC3432] prescribes the checksum MUST be calculated and included in method for generating Periodic
   streams using associated parameters.

   incT  the
         header

   o  UDP Payload

      *  total nominal duration of 9 bytes

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time

      *  3.0, inter-packet interval, first bit to
      first bit, with value 0.0200, 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 ms).

   dT the 32-bit NTP timestamp as per
         section 6 of [RFC5905].

4.3.  Method of Measurement

   This category includes columns for references to relevant sections duration of the RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations.

4.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   The methodology interval for this metric is defined as Type-P-Round-trip-
   Delay-Poisson-Stream allowed sample start times, with
      value 1.0, expressed in section 2.6 units of RFC 2681 [RFC2681] and seconds, as a positive value of
      type decimal64 with fraction digits = 4 (see section
   3.6 9.3 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under
   Fixed Parameters.

   The reference method distinguishes between long-delayed packets
      [RFC6020]) and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is with resolution of 0.0001 seconds (0.1 ms).

   T0 the waiting actual start time used as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for the RTLoss metric.

   The calculations on the delay (RTT) SHALL be performed on the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packet delays are stored, the process
   which calculates the RTT value MAY enforce the Tmax threshold on
   stored values before calculations.  See section 4.1 of [RFC3393] for
   details on the conditional distribution to exclude undefined values periodic stream, (format "date-and-
      time" as specified in Section 5.6 of delay, and [RFC3339], see also Section 5 3
      of [RFC6703] for background on this analysis
   choice.

   The reference method requires some way to distinguish between
   different packets [RFC6991]).

   NOTE: an initiation process with a number of control exchanges
   resulting in unpredictable start times (within a stream time interval) may
   be sufficient to establish correspondence between
   sending times avoid synchronization of periodic streams, and receiving times
   therefore a valid replacement for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained selecting a start time at the Src or included with each packet to dis-ambiguate
   packet reordering if it occurs.

   If random
   from a standard measurement protocol is employed, then the measurement
   process fixed interval.

   The T0 parameter will determine be reported as a measured parameter.
   Parameters incT and dT are Fixed Parameters.

5.3.3.  Traffic Filtering (observation) Details

   <insert the measured results based on a filtered version of the sequence numbers or timestamps applied to
   test
   packets after observed, and this section provides the Fixed filter details (when
   present), and Runtime parameters are passed to
   that process.  The chosen measurement protocol will dictate section reference>.

   NA

5.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from the
   format
   filter>

   NA

5.3.5.  Run-time Parameters and Data Format

   <list of sequence numbers run-time parameters, and time-stamps, if they are conveyed their data formats>

   Src  the IP address of the host in the packet payload.

   Refer to Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see Section 4.4 4 of [RFC6673] [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 expanded discussion IPv6,
      see section 4 of the
   instruction to "send [RFC6991])

   T0 a Type-P packet back to time, the Src as quickly start of a measurement interval, (format "date-and-
      time" as
   possible" specified in Section 2.6 5.6 of RFC 2681 [RFC2681]. [RFC3339], see also Section 8 of
   [RFC6673] presents additional requirements which MUST be included in
   the method 3
      of measurement for this metric.

4.3.2.  Packet Stream Generation

   This section gives the details [RFC6991]).  The UTC Time Zone is required by Section 6.1 of the packet traffic which
      [RFC2330].  When T0 is the
   basis for measurement.  In IPPM metrics, this "all-zeros", a start time is called the Stream, unspecified
      and can easily Tf is to be described by providing interpreted as the list Duration of stream
   parameters.

   <section/specification references, and description the measurement
      interval.  The start time is controlled through other means.

   Tf a time, the end of any new
   generation parameters, if needed> a measurement interval, (format "date-and-time"
      as specified in Section 11.1.3 5.6 of [RFC2330] provides three methods to generate
   Poisson sampling intervals. the reciprocal [RFC3339], see also Section 3 of lambda
      [RFC6991]).  The UTC Time Zone is the average
   packet spacing, thus the Run-time Parameter required by Section 6.1 of
      [RFC2330].  When T0 is Reciprocal_lambda = 1/
   lambda, in seconds.

   Method 3 SHALL be used, where given "all-zeros", a start end time (Run-time
   Parameter), date is ignored and
      Tf is interpreted as the Duration of the subsequent send times are all computed prior to measurement by computing interval.

5.3.6.  Roles

   <lists the pseudo-random distribution names of inter-
   packet send times, (truncating the distribution as specified in the
   Run-time Parameter, Trunc), and different roles from the measurement method>

   Src sends  launches each packet to Dst.

   Dst  waits for each packet at from Src.

5.4.  Output

   This category specifies all details of the
   computed times.

   Note that Trunc is Output of measurements
   using the upper limit on inter-packet times in metric.

5.4.1.  Type

   <insert name of the
   Poisson distribution.  A random value greater than Trunc is set equal
   to Trunc instead.

4.3.3.  Traffic Filtering (observation) Details

   The measured results based on output type, raw or a filtered version of selected summary statistic>

   Percentile -- for the conditional distribution of all packets
   observed, and this section provides with a
   valid value of one-way delay (undefined delays are excluded), a
   single value corresponding to the filter 95th percentile, as follows:

   See section 4.1 of [RFC3393] for details (when
   present).

   <section reference>.

   NA

4.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from on the
   filter>

   NA

4.3.5.  Run-time Parameters conditional
   distribution to exclude undefined values of delay, and Data Format

   Run-time Parameters are input factors Section 5 of
   [RFC6703] for background on this analysis choice.

   The percentile = 95, meaning that must be determined,
   configured into the measurement system, and reported with the results
   for delay, "95Percentile",
   is the context to be complete.

   <list smallest value of run-time parameters, and their data formats>

   Src one-way PDV for which the IP address Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the host singleton
   one-way PDV values in the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see Section 4 conditional distribution.  See section 11.3
   of [RFC6991])

   Dst [RFC2330] for the IP address definition of the host in percentile statistic using the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value
   EDF.

5.4.2.  Reference Definition

   <the output type and data format for IPv6,
      see section 4 each type of [RFC6991]) result>

   T0 a time, the start of a measurement interval, (format "date-and-
      time" "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

   95Percentile  The time date is ignored and
      Tf is interpreted as the Duration value of the measurement interval.

   Reciprocal_lambda  average packet interval for Poisson Streams result is expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 4 9 (see section 9.3 of [RFC6020]) with resolution of 0.0001
      0.000000001 seconds (0.1 ms), (1.0 ns), and with lossless conversion to/from
      the 32-bit 64-bit NTP timestamp as per section 6 of
      [RFC5905].

   Trunc  Upper limit on Poisson distribution RFC [RFC5905]

5.4.3.  Metric Units

   <insert units for the measured results, and the reference
   specification>.

   The 95th Percentile of one-way PDV is expressed in seconds.

5.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means to quantify the
   systematic and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback that includes
   as much of the measurement system as possible, performs address
   manipulation as needed, and provides some form of isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of the random and systematic error can be characterized
   this way.

   For one-way delay measurements, the error calibration must include an
   assessment of the internal clock synchronization with its external
   reference (this internal clock is supplying timestamps for
   measurement).  In practice, the time offsets of clocks at both the
   source and destination are needed to estimate the systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus the random variation is not usually represented in the
   results).

   time_offset  The time value of the result is expressed in units of
      seconds, as a positive signed value of type decimal64 with fraction digits
      = 4 9 (see section 9.3 of [RFC6020]) with resolution of
      0.0001 0.000000001
      seconds (0.1 ms), (1.0 ns), and with lossless conversion to/from the
      32-bit 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905] (values above
      this limit will be clipped

   When a measurement controller requests a calibration measurement, the
   loopback is applied and set to the limit value). (if fixed,
      Trunc = 30.0000 seconds.)

   >>> should Poisson run-time params be fixed instead? probably yes if
   modeling result is output in the same format as a specific version of MBA tests.

4.3.6.  Roles

   <lists
   normal measurement with additional indication that it is a
   calibration result.  In any measurement, the names measurement function
   SHOULD report its current estimate of time offset as an indicator of
   the different roles from the measurement method>

   Src  launches each packet and waits for return transmissions from
      Dst.

   Dst  waits for each packet from Src degree of synchronization.

   Both internal loopback calibration and sends a return packet clock synchronization can be
   used to Src.

4.4.  Output

   This category specifies all details estimate the *available accuracy* of the Output of Metric Units.
   For example, repeated loopback delay measurements
   using will reveal the metric.

4.4.1.  Type

   <insert name
   portion of the output type, raw or a selected summary statistic>

   Percentile -- for Output result resolution which is the conditional distribution result of all packets with a
   valid value system
   noise, and thus inaccurate.

5.5.  Administrative items

5.5.1.  Status

   <current or deprecated>

5.5.2.  Requestor (keep?)

   <name of Round-trip delay (undefined delays are excluded), a
   single value corresponding to the 95th percentile, as follows: individual or RFC, etc.>

5.5.3.  Revision

   1.0

5.5.4.  Revision Date

   YYYY-MM-DD

5.6.  Comments and Remarks

   <Additional (Informational) details for this entry>

   Lost packets represent a challenge for delay variation metrics.  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.

   The percentile = 95, meaning that the reported delay, "95Percentile",
   is the smallest value of Round-trip delay variation applicability
   statement[RFC5481] for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% extensive analysis and comparison of the singleton PDV and
   an alternate metric, IPDV.

6.  DNS Response Latency and Loss Registry Entries

   This section gives initial registry entries for DNS Response Latency
   and Loss.  RFC 2681 [RFC2681] defines a Round-trip delay values in the conditional distribution.  See section
   11.3 metric.  We
   build on that metric by specifying several of [RFC2330] for the definition of input parameters to
   precisely define two metrics for measuring DNS latency and loss.

   Note to IANA: Each Registry "Name" below specifies a single registry
   entry, whose output format varies in accordance with the percentile statistic
   using name.

   All column entries beside the EDF.

   LossRatio -- ID, Name, Description, and Output
   Reference Method categories are the count of lost packets to total packets sent same, thus this section proposes
   two closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to each Named Metric.

6.1.  Summary

   This category includes multiple indexes to the
   basis for the loss ratio calculation as per Section 6.1 of [RFC6673].

4.4.2.  Reference Definition

   <describe registry entries, the reference data format
   element ID and metric name.

   <skipping some admin columns for now>

6.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>
   IANA is asked to assign different numeric identifiers to each type of result>

   For all outputs ---

   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
   two Named Metrics.

6.1.2.  Name

   <insert name according to metric naming convention>

   RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_Raw

   RLDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Logical_Raw

6.1.3.  URI

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by Section 6.1 of
      [RFC2330].

   Tf IANA>/<name>

6.1.4.  Description

   RTDNS: This metric assesses 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].

   TotalPkts response time, the count of packets sent by interval from the Src
   query transmission to Dst during the
      measurement interval.

   For

   RTDelay_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile:

   95Percentile  The time value of response.

   RLDNS: This metric indicates that 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 response was deemed lost.  In
   other words, the 64-bit NTP timestamp as

   For

   RTLoss_Active_IP-UDP-Poisson_RFCXXXXsecY_Percent_LossRatio:

   Percentile  The numeric value of response time exceeded the result is expressed in units of
      lost packets maximum waiting time.

6.1.5.  Change Controller

   IETF

6.1.6.  Version (of Registry Format)

   1.0

6.2.  Metric Definition

   This category includes columns to total packets times 100%, as a positive value of
      type decimal64 with fraction digits = 9 (see section 9.3 of
      [RFC6020]) with resolution prompt the entry of 0.0000000001.

4.4.3.  Metric Units

   <insert units for all necessary
   details related to the measured results, and metric definition, including the RFC reference
   specification>.

   The 95th Percentile
   and values of input factors, called fixed parameters.

6.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   Mockapetris, P., "Domain names - implementation and specification",
   STD 13, RFC 1035, November 1987. (and updates)

   [RFC1035]
   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay is expressed in seconds.

   The Round-trip Loss Ratio is expressed as a percentage of lost
   packets to total packets sent.

4.4.4.  Calibration
   Metric for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific section reference and additional clarifications, if needed>

   Section 3.7.3 2.4 of [RFC7679] [RFC2681] provides a means to quantify the
   systematic and random errors reference definition of a time measurement.  In-situ
   calibration could be enabled with an internal loopback at the Source
   host that includes as much
   singleton (single value) Round-trip delay metric.  Section 3.4 of
   [RFC2681] provides the measurement system as possible,
   performs address manipulation reference definition expanded to cover a
   multi-singleton sample.  Note that terms such as needed, singleton and provides some form of
   isolation (e.g., deterministic delay) to avoid send-receive interface
   contention.  Some portion sample
   are defined in Section 11 of [RFC2330].

   For DNS Response Latency, the random and systematic error can entities in [RFC1035] must be
   characterized this way.

   When a measurement controller requests a calibration measurement, mapped to
   [RFC2681].  The Local Host with its User Program and Resolver take
   the
   loopback is applied role of "Src", and the result is output in Foreign Name Server takes the same format as a
   normal measurement with additional indication role of
   "Dst".

   Note that it is a
   calibration result.

   Both internal loopback calibration and clock synchronization can be
   used although the [RFC2681] definition of "Round-trip-Delay
   between Src and Dst at T" is directionally ambiguous in the text,
   this metric tightens the definition further to estimate recognize that the *available accuracy* of
   host in the Output Metric Units.
   For example, repeated loopback delay measurements "Src" role will reveal send the
   portion of first packet to "Dst", and
   ultimately receive the Output result resolution which corresponding return packet from "Dst" (when
   neither are lost).

   Morton, A., "Round-trip Packet Loss Metrics", RFC 6673, August 2012.

   [RFC6673]

   Both response time and loss metrics employ a maximum waiting time for
   received responses, so the count of lost packets to total packets
   sent is the result basis for the loss determination as per Section 4.3 of system
   noise,
   [RFC6673].

6.2.2.  Fixed Parameters

   <list and thus inaccurate.

4.5.  Administrative items

4.5.1.  Status

   <current or deprecated>

4.5.2.  Requestor (keep?)

   name or RFC, etc.

4.5.3.  Revision

   1.0

4.5.4.  Revision Date

   YYYY-MM-DD

4.6.  Comments specify Fixed Parameters, input factors that must be
   determined and Remarks

   Additional (Informational) details for this entry

5.  Packet Delay Variation Registry Entry

   This section gives an initial registry entry embedded in the measurement system for a Packet Delay
   Variation metric.

   Note: If each Registry entry should only produce a "raw" output or a
   statistical summary, then use when
   needed>

   Type-P as defined in Section 13 of [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Source port: 53

      *  Destination port: 53

      *  Checksum: the "Output" Category can checksum must be split calculated and this included in the
         header

   o  Payload: The payload contains a DNS message as defined in RFC 1035
      [RFC1035] with the following values:

      *  The DNS header section can become two closely-related metrics.

5.1.  Summary

   This category includes multiple indexes contains:

         +  Identification (see the Run-time column)

         +  QR: set to 0 (Query)

         +  OPCODE: set to 0 (standard query)

         +  AA: not set

         +  TC: not set

         +  RD: set to one (recursion desired)

         +  RA: not set

         +  RCODE: not set

         +  QDCOUNT: set to one (only one entry)

         +  ANCOUNT: not set

         +  NSCOUNT: not set

         +  ARCOUNT: not set

      *  The Question section contains:

         +  QNAME: the registry entries, Fully Qualified Domain Name (FQDN) provided as
            input for the
   element ID and metric name.

   <skipping some Summary columns test, see the Run-time column

         +  QTYPE: the query type provided as input for now>

5.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>

5.1.2.  Name

   <insert name according the test, see
            the Run-time column

         +  QCLASS: set to metric naming convention>

   OWPDV_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_95Percentile

5.1.3.  URIs

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

5.1.4.  Description

   An assessment 1 for IN

      *  The other sections do not contain any Resource Records.

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time (and to help disambiguate
      queries)

      *  5.0, expressed in units of packet delay variation seconds, as a positive value of type
         decimal64 with respect to the minimum
   delay observed on the stream, 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 Output is expressed 32-bit NTP timestamp as the 95th
   percentile per
         section 6 of the packet delay variation distribution.

5.1.5.  Change Controller

   <org or person >

   IETF

5.1.6.  Version (of Registry Format)

   1.0

5.2.  Metric Definition [RFC5905].

   Observation: reply packets will contain a DNS response and may
   contain RRs.

6.3.  Method of Measurement

   This category includes columns for references to prompt the entry relevant sections of all necessary
   details related to
   the metric definition, including the RFC reference RFC(s) and values of input factors, called fixed parameters.

5.2.1.  Reference Definition

   <Full bibliographic reference any supplemental information needed to ensure an immutable doc.>

   Paxson, V., Almes, G., Mahdavi, J., and M.  Mathis, "Framework for IP
   Performance Metrics", RFC 2330, May 1998.  [RFC2330]

   Demichelis, C. and P.  Chimento, "IP Packet Delay Variation Metric
   unambiguous methods for IP Performance Metrics (IPPM)", RFC 3393, November 2002.
   [RFC3393]

   Morton, A. and B.  Claise, "Packet Delay Variation Applicability
   Statement", RFC 5481, March 2009.  [RFC5481]
   Mills, D., Martin, J., Burbank, J., and W.  Kasch, "Network Time
   Protocol Version 4: Protocol and Algorithms Specification", RFC 5905,
   June 2010.[RFC5905]

   <specific implementations.

6.3.1.  Reference Method

   <for metric, insert relevant section reference and additional clarifications, if needed>

   See sections 2.4 references and 3.4 of [RFC3393].  Singleton delay differences
   measured are referred to by the variable name "ddT" (applicable to
   all forms of delay variation).  However, supplemental
   info>

   The methodology for this metric entry specifies
   the PDV form is defined as Type-P-Round-trip-
   Delay-Poisson-Stream in section 4.2 2.6 of [RFC5481], where RFC 2681 [RFC2681] and section
   3.6 of RFC 2681 [RFC2681] using the singleton
   PDV Type-P and Timeout defined under
   Fixed Parameters.

   The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet i
   arrival.  Tmax is referred to by the variable name "PDV(i)".

5.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must waiting time used as the threshold to declare a
   packet lost.  Lost packets SHALL be
   determined designated as having undefined
   delay, and embedded in the measurement system counted for use when
   needed>

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255

      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: the checksum MUST RLDNS metric.

   The calculations on the delay (RTT) SHALL be calculated and included in performed on the
         header

   o  UDP Payload

      *  total of 200 bytes

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packet delays are stored, the process
   which calculates the RTT value 3.0, expressed in
      units MAY enforce the Tmax threshold on
   stored values before calculations.  See section 4.1 of seconds, as a positive value [RFC3393] for
   details on the conditional distribution to exclude undefined values
   of type decimal64 with
      fraction digits = 4 (see section 9.3 delay, and Section 5 of [RFC6020]) [RFC6703] for background on this analysis
   choice.

   The reference method requires some way to distinguish between
   different packets in a stream to establish correspondence between
   sending times and receiving times for each successfully-arriving
   reply.  Therefore, sequence numbers or other send-order
   identification MUST be retained at the Src or included with
      resolution each
   packet to disambiguate packet reordering if it occurs.  Sequence
   number is part of 0.0001 seconds (0.1 ms), with lossless conversion
      to/from the 32-bit NTP timestamp as per section 6 of [RFC5905].

   F payload described under Fixed Parameters.

   DNS Messages bearing Queries provide for random ID Numbers in the
   Identification header field, so more than one query may be launched
   while a selection function unambiguously defining previous request is outstanding when the packets from ID Number is used.

   IF a DNS response does not arrive within Tmax, the
      stream selected for response time is
   undefined, and RTDNS = 1.  The Message ID SHALL be used to
   disambiguate the metric.  See section 4.2 successive queries.

   @@@@ This would require support of [RFC5481] for ID generation and population in
   the PDV form.

   See Message.  An alternative would be to use a random Source port on
   the Packet Stream generation category for two additional Fixed
   Parameters.

5.3.  Method Query Message, but we would choose ONE before proceeding.

   Refer to Section 4.4 of Measurement

   This category includes columns [RFC6673] for references to relevant sections expanded discussion of the RFC(s) and any supplemental information needed
   instruction to ensure an
   unambiguous methods for implementations.

5.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   See section "send a Type-P packet back to the Src as quickly as
   possible" in Section 2.6 and 3.6 of [RFC3393] for general singleton element
   calculations.  This metric entry requires implementation RFC 2681 [RFC2681].  Section 8 of the PDV
   form defined
   [RFC6673] presents additional requirements which shall be included in section 4.2
   the method of [RFC5481].  Also see measurement
   considerations for this metric.

   In addition to operations described in section 8 [RFC2681], the Src MUST parse
   the DNS headers of [RFC5481].

   The reference method distinguishes between long-delayed packets the reply and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is prepare the waiting time used information for
   subsequent reporting as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay.

   The calculations on measured result, along with the one-way delay SHALL be performed on Round-Trip
   Delay.

6.3.2.  Packet Stream Generation

   This section gives the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packet delays are stored, details of the process packet traffic which calculates the one-way delay value MAY enforce is the Tmax
   threshold on stored values before calculations.  See section 4.1 of
   [RFC3393]
   basis for details on measurement.  In IPPM metrics, this is called the conditional distribution to exclude
   undefined values Stream,
   and can easily be described by providing the list of delay, stream
   parameters.

   <list of generation parameters and section/spec references if needed>
   Section 5 11.1.3 of [RFC6703] for background
   on this analysis choice.

   The reference method requires some way RFC 2681 [RFC2330] provides three methods to distinguish between
   different packets
   generate Poisson sampling intervals.  The reciprocal of lambda is the
   average packet rate, thus the Run-time Parameter is Reciprocal_lambda
   = 1/lambda, in seconds.

   Method 3 is used, where given a stream to establish correspondence between
   sending start time (Run-time Parameter), the
   subsequent send times are all computed prior to measurement by
   computing the pseudo-random distribution of inter-packet send times,
   (truncating the distribution as specified in the Run-time
   Parameters), and receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the Src or included with sends each packet to dis-ambiguate
   packet reordering if it occurs.

   If a standard measurement protocol at the computed times.

   Note that Trunc is employed, then the measurement
   process will determine upper limit on inter-packet times in the sequence numbers or timestamps applied
   Poisson distribution.  A random value greater than Trunc is set equal
   to
   test Trunc instead.

6.3.3.  Traffic Filtering (observation) Details

   The measured results based on a filtered version of the packets after
   observed, and this section provides the Fixed filter details (when
   present).

   <section reference>.

   NA

6.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from the
   filter>

   NA

6.3.5.  Run-time Parameters and Runtime parameters Data Format

   Run-time Parameters are passed to input factors that process.  The chosen measurement protocol will dictate must be determined,
   configured into the
   format of sequence numbers measurement system, and time-stamps, if they are conveyed in reported with the packet payload.

5.3.2.  Packet Stream Generation results
   for the context to be complete.

   <list of generation parameters run-time parameters, and section/spec references if needed> their data formats>

   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 11.1.3 4 of [RFC2330] provides three methods to generate
   Poisson sampling intervals. [RFC6991])

   Dst  the reciprocal 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])

   T0 a time, the start of a measurement interval, (format "date-and-
      time" as specified in Section 5.6 of lambda [RFC3339], see also Section 3
      of [RFC6991]).  The UTC Time Zone is the average
   packet spacing, thus the Run-time Parameter required by Section 6.1 of
      [RFC2330].  When T0 is Reciprocal_lambda = 1/
   lambda, in seconds.

   Method 3 SHALL be used, where given "all-zeros", a start time (Run-time
   Parameter), the subsequent send times are all computed prior is unspecified
      and Tf is to
   measurement by computing be interpreted as the pseudo-random distribution Duration of inter-
   packet send times, (truncating the distribution 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 the
   Parameter Trunc), 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 the Src sends each packet at the computed
   times.

   Note that Trunc
      Tf is interpreted as the upper limit on inter-packet times in Duration of the
   Poisson distribution.  A random value greater than Trunc is set equal
   to Trunc instead. measurement interval.

   Reciprocal_lambda  average packet interval for Poisson Streams
      expressed in units of seconds, 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), and with lossless
      conversion to/from the 32-bit NTP timestamp as per section 6 of
      [RFC5905].  Reciprocal_lambda = 1 packet per second.

   Trunc  Upper limit on Poisson distribution expressed in units of
      seconds, 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), and with lossless conversion to/from
      0.0001 seconds (0.1 ms), and with lossless conversion to/from the
      32-bit NTP timestamp as per section 6 of [RFC5905] (values above
      this limit will be clipped and set to the limit value). (if fixed,
      Trunc = 30.0000 seconds.)

   ID The 16-bit identifier assigned by the program that generates the
      query, and which must vary in successive queries, see
      Section 4.1.1 of [RFC1035].  This identifier is copied into the
      corresponding reply and can be used by the requester (Src) to
      match-up replies to outstanding queries.

   QNAME  The domain name of the
      32-bit NTP timestamp Query, formatted as per specified in
      section 6 4 of [RFC5905] (values above
      this limit [RFC6991].

   QTYPE  The Query Type, which will be clipped and set correspond to the limit value).  Trunc =
      30.0000 seconds.

5.3.3.  Traffic Filtering (observation) Details

   <insert IP address family
      of the measured results based on query (decimal 1 for IPv4 or 28 for IPv6, formatted as a filtered version
      uint16, as per section 9.2 of [RFC6020].

6.3.6.  Roles

   <lists the
   packets observed, and this section provides names of the filter details (when
   present), and section reference>.

   NA

5.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff different roles from the
   filter>

   NA

5.3.5.  Run-time Parameters and Data Format

   <list of run-time parameters, measurement method>

   Src  launches each packet and their data formats> waits for return transmissions from
      Dst.

   Dst  waits for each packet from Src and sends a return packet to Src.

6.4.  Output

   This category specifies all details of the IP address Output of measurements
   using the host in metric.

6.4.1.  Type

   <insert name of the Src Role (format ipv4-address-
      no-zone value for IPv4, output type, raw or ipv6-address-no-zone value a selected summary statistic>

   Raw -- for IPv6,
      see Section 4 each DNS Query packet sent, sets of [RFC6991])

   Dst values as defined in
   the IP address next column, including the status of the host in response, only assigning
   delay values to successful query-response pairs.

6.4.2.  Reference Definition

   <describe the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value data format for IPv6,
      see section 4 of [RFC6991])

   T0 a time, the start each type of a result>

   For all outputs:

   T  the time the DNS Query was sent during the measurement interval,
      (format "date-and-
      time" "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

   dT The time value of the round-trip delay to receive the DNS
      response, 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].  This value is "all-zeros", undefined when the
      response packet is not received at Src within waiting time Tmax
      seconds.

   Rcode  The value of the Rcode field in the DNS response header,
      expressed as a uint64 as specified in section 9.2 of [RFC6020].
      Non-zero values convey errors in the response, and such replies
      must be analyzed separately from successful requests.

6.4.3.  Metric Units

   <insert units for the measured results, and the reference
   specification>.

   RTDNS: Round-trip Delay, dT, is expressed in seconds.

   RTLDNS: the Logical value, where 1 = Lost and 0 = Received.

6.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means to quantify the
   systematic and random errors of a start time measurement.  In-situ
   calibration could be enabled with an internal loopback at the Source
   host that includes as much of the measurement system as possible,
   performs address and payload manipulation as needed, and provides
   some form of isolation (e.g., deterministic delay) to avoid send-
   receive interface contention.  Some portion of the random and
   systematic error can be characterized this way.

   When a measurement controller requests a calibration measurement, the
   loopback is unspecified applied and Tf is to be interpreted as the Duration of result is output in the same format as a
   normal measurement
      interval.  The start time with additional indication that it is controlled through other means.

   Tf a time,
   calibration result.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the end of a measurement interval, (format "date-and-time"
      as specified in Section 5.6 *available accuracy* of [RFC3339], see also Section 3 the Output Metric Units.
   For example, repeated loopback delay measurements will reveal the
   portion of
      [RFC6991]).  The UTC Time Zone the Output result resolution which is required by Section 6.1 the result of
      [RFC2330].  When T0 is "all-zeros", a end time date is ignored system
   noise, and
      Tf is interpreted as thus inaccurate.

6.5.  Administrative items

6.5.1.  Status

   <current or deprecated>

6.5.2.  Requestor

   name or RFC, etc.

6.5.3.  Revision

   1.0

6.5.4.  Revision Date

   YYYY-MM-DD

6.6.  Comments and Remarks

   Additional (Informational) details for this entry

7.  UDP Poisson One-way Delay and Loss Registry Entries

   This section specifies five initial registry entries for the Duration of UDP
   Poisson One-way Delay, and one for UDP Poisson One-way Loss.

   IANA Note: Registry "Name" below specifies a single registry entry,
   whose output format varies according to the measurement interval.

5.3.6.  Roles

   <lists <statistic> element of
   the names name that specifies one form of statistical summary.  There is an
   additional metric name for the different roles from Loss metric.

   All column entries beside the measurement method>

   Src  launches each packet ID, Name, Description, and Output
   Reference Method categories are the same, thus this section proposes
   six closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to Dst.

   Dst  waits for each packet from Src.

5.4.  Output Named Metric.

7.1.  Summary

   This category specifies all details of includes multiple indexes to the Output of measurements
   using registry entries, the metric.

5.4.1.  Type
   element ID and metric name.

7.1.1.  ID (Identifier)

   <insert numeric identifier, an integer, one corresponding to each
   name below>

   IANA is asked to assign different numeric identifiers to each of the output type, raw or a selected summary statistic>

   Percentile -- for
   six Metrics.

7.1.2.  Name

   <insert name according to metric naming convention>

   OWDelay_Active_IP-UDP-Poisson-
   Payload250B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev
   OWLoss_Active_IP-UDP-Poisson-
   Payload250B_RFCXXXXsecY_Percent_LossRatio

7.1.3.  URI and URL

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http:\\www.iana.org\ ... <name>

7.1.4.  Description

   OWDelay: This metric assesses the conditional distribution delay of all packets with a
   valid value stream of one-way delay (undefined delays are excluded), a
   single value corresponding to packets
   exchanged between two hosts (or measurement points), and reports the 95th percentile, as follows:

   See section 4.1 of [RFC3393]
   <statistic> One-way delay for details all successfully exchanged packets
   based on the their conditional
   distribution to exclude undefined values of delay, and Section 5 of
   [RFC6703] for background on this analysis choice.

   The percentile = 95, meaning that the reported delay, "95Percentile", delay distribution.

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses the smallest value loss ratio of one-way PDV for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% a stream of packets
   exchanged between two hosts (which are the singleton
   one-way PDV values in two measurement points),
   and the Output is the conditional distribution.  See section 11.3
   of [RFC2330] One-way loss ratio for all successfully
   received packets expressed as a percentage.

7.2.  Metric Definition

   This category includes columns to prompt the definition entry of all necessary
   details related to the percentile statistic using metric definition, including the
   EDF.

5.4.2. RFC reference
   and values of input factors, called fixed parameters.

7.2.1.  Reference Definition

   <the output type

   <Full bibliographic reference to an immutable doc.>

   For Delay:

   Almes, G., Kalidindi, S., Zekauskas, M., and data format A.  Morton, Ed., "A One-
   Way Delay Metric for each type of result>

   T0 the start IP Performance Metrics (IPPM)", STD 81, RFC
   7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
   editor.org/info/rfc7679>.

   [RFC7679]

   Morton, A., and Stephan, E., "Spatial Composition of a measurement interval, (format "date-and-time" as
      specified in Metrics", RFC
   6049, January 2011.

   [RFC6049]

   <specific section reference and additional clarifications, if needed>

   Section 5.6 3.4 of [RFC3339], see also Section 3 [RFC7679] provides the reference definition of
      [RFC6991]).  The UTC Time Zone is required by the
   singleton (single value) One-way delay metric.  Section 6.1 4.4 of
      [RFC2330].

   Tf
   [RFC7679] provides the end of reference definition expanded to cover a measurement interval, (format "date-and-time"
   multi-value sample.  Note that terms such as
      specified singleton and sample are
   defined in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 11 of [RFC2330].

   95Percentile  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

   Only successful packet transfers with lossless conversion to/from finite delay are included in
   the 64-bit NTP timestamp sample, as per prescribed in section 6 4.1.2 of RFC [RFC5905]

5.4.3. [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Loss Metric Units

   <insert units for the measured results, and IP Performance Metrics (IPPM)", RFC 7680, DOI
   10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
   rfc7680>.

   Section 2.4 of [RFC7680] provides the reference
   specification>.

   The 95th Percentile definition of the
   singleton (single value) one-way PDV is expressed in seconds.

5.4.4.  Calibration loss metric.  Section 3.7.3 3.4 of [RFC7679]
   [RFC7680] provides a means to quantify the
   systematic and random errors of reference definition expanded to cover a time measurement.  In-situ
   calibration could be enabled with an internal loopback
   multi-singleton sample.  Note that includes
   as much of the measurement system as possible, performs address
   manipulation terms such as needed, singleton and provides some form of isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion sample
   are defined in Section 11 of the random [RFC2330].

7.2.2.  Fixed Parameters

   <list and systematic error can be characterized
   this way.

   For one-way delay measurements, the error calibration specify Fixed Parameters, input factors that must include an
   assessment of be
   determined and embedded in the internal clock synchronization with its external
   reference (this internal clock is supplying timestamps measurement system for
   measurement).  In practice, the time offsets of clocks at both the
   source and destination are needed use when
   needed>

   Type-P:

   o  IPv4 header values:

      *  DSCP: set to estimate the systematic error
   due 0

      *  TTL: set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to imperfect clock synchronization (the time offsets are
   smoothed, thus 17 (UDP)

   o  UDP header values:

      *  Checksum: the random variation is not usually represented checksum MUST be calculated and included in the
   results).

   time_offset  The time value
         header

   o  UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357]

      *  Security features in use influence the number of Padding
         octets.

      *  250 octets total, including the result is TWAMP format

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value 3.0, expressed in
      units of seconds, as a signed positive value of type decimal64 with
      fraction digits = 9 4 (see section 9.3 of [RFC6020]) and with
      resolution of 0.000000001 0.0001 seconds (1.0 ns), and (0.1 ms), with lossless conversion
      to/from the 64-bit 32-bit NTP timestamp as per section 6 of RFC [RFC5905]

   When a measurement controller requests a calibration measurement, [RFC5905].

   See the
   loopback is applied and Packet Stream generation category for two additional Fixed
   Parameters.

7.3.  Method of Measurement

   This category includes columns for references to relevant sections of
   the result RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations.

7.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   The methodology for this metric is output defined as Type-P-One-way-Delay-
   Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of
   [RFC7679] using the same format as Type-P and Tmax defined under Fixed Parameters.

   The reference method distinguishes between long-delayed packets and
   lost packets by implementing a
   normal measurement with additional indication that it maximum waiting time for packet
   arrival.  Tmax is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate of waiting time offset used as an indicator of the degree of synchronization.

   Both internal loopback calibration and clock synchronization can be
   used threshold to estimate declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for the *available accuracy* of OWLoss metric.

   The calculations on the Output Metric Units.
   For example, repeated loopback one-way delay measurements will reveal SHALL be performed on the
   portion of
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packet delays are stored, the Output result resolution process
   which is calculates the result of system
   noise, and thus inaccurate.

5.5.  Administrative items

5.5.1.  Status

   <current or depricated>

5.5.2.  Requestor (keep?)

   <name of individual or RFC, etc.>

5.5.3.  Revision

   1.0

5.5.4.  Revision Date

   YYYY-MM-DD

5.6.  Comments and Remarks

   <Additional (Informational) details for this entry>

   Lost packets represent a challenge for one-way delay variation metrics. value MAY enforce the Tmax
   threshold on stored values before calculations.  See section 4.1 of
   [RFC3393] and the delay variation applicability
   statement[RFC5481] for extensive analysis and comparison details on the conditional distribution to exclude
   undefined values of PDV and
   an alternate metric, IPDV.

6.  DNS Response Latency delay, and Loss Registry Entries

   This section gives initial registry entries Section 5 of [RFC6703] for DNS Response Latency
   and Loss.  RFC 2681 [RFC2681] defines a Round-trip delay metric.  We
   build background
   on that metric by specifying several of the input parameters this analysis choice.

   The reference method requires some way to
   precisely define two metrics distinguish between
   different packets in a stream to establish correspondence between
   sending times and receiving times for measuring DNS latency each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the Src or included with each packet to disambiguate
   packet reordering if it occurs.

   Since a standard measurement protocol is employed [RFC5357], then the
   measurement process will determine the sequence numbers or timestamps
   applied to test packets after the Fixed and loss.

   Note Runtime parameters are
   passed to IANA: Each Registry "Name" below specifies a single registry
   entry, whose output that process.  The measurement protocol dictates the format varies
   of sequence numbers and time-stamps conveyed in accordance with the name.

   All column entries beside TWAMP-Test packet
   payload.

7.3.2.  Packet Stream Generation

   This section gives the ID, Name, Description, and Output
   Reference Method categories are details of the same, thus packet traffic which is the
   basis for measurement.  In IPPM metrics, this section proposes
   two closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to each Named Metric.

6.1.  Summary

   This category includes multiple indexes to called the registry entries, Stream,
   and can easily be described by providing the
   element ID list of stream
   parameters.

   <list of generation parameters and metric name.

   <skipping some admin columns for now>

6.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>
   IANA is asked to assign different numeric identifiers section/spec references if needed>

   Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to each
   generate Poisson sampling intervals.  The reciprocal of lambda is the
   two Named Metrics.

6.1.2.  Name

   <insert name according
   average packet spacing, thus the Run-time Parameter is
   Reciprocal_lambda = 1/lambda, in seconds.

   Method 3 SHALL be used, where given a start time (Run-time
   Parameter), the subsequent send times are all computed prior to metric naming convention>

   RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_Raw

   RLDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Logical_Raw

6.1.3.  URI

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD
   measurement by IANA>/<name>

6.1.4.  Description

   RTDNS: This metric assesses computing the response time, pseudo-random distribution of inter-
   packet send times, (truncating the distribution as specified in the interval from
   Parameter Trunc), and the
   query transmission to Src sends each packet at the response.

   RLDNS: This metric indicates computed
   times.

   Note that Trunc is the respnse was deemed lost.  In
   other words, the response time exceeded upper limit on inter-packet times in the maximum waiting time.

6.1.5.  Change Controller

   IETF

6.1.6.  Version (of Registry Format)

   1.0

6.2.  Metric Definition

   This category includes columns
   Poisson distribution.  A random value greater than Trunc is set equal
   to prompt the entry Trunc instead.

   Reciprocal_lambda  average packet interval for Poisson Streams
      expressed in units of all necessary
   details related to the metric definition, including seconds, 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), and with lossless
      conversion to/from the RFC reference 32-bit NTP timestamp as per section 6 of
      [RFC5905].  Reciprocal_lambda = 1 packet per second.

   Trunc  Upper limit on Poisson distribution expressed in units of
      seconds, 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), and values with lossless conversion to/from the
      32-bit NTP timestamp as per section 6 of input factors, called fixed parameters.

6.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   Mockapetris, P., "Domain names - implementation [RFC5905] (values above
      this limit will be clipped and specification",
   STD 13, RFC 1035, November 1987. (and updates)

   [RFC1035]
   Almes, G., Kalidindi, S., set to the limit value).  Trunc =
      30.0000 seconds.

7.3.3.  Traffic Filtering (observation) Details

   NA

7.3.4.  Sampling Distribution

   NA

7.3.5.  Run-time Parameters and M.  Zekauskas, "A Round-trip Delay
   Metric Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the measurement system, and reported with the results
   for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific section reference the context to be complete.

   <list of run-time parameters, and additional clarifications, if needed> their data formats>

   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 2.4 4 of [RFC2681] provides [RFC6991])

   Dst  the reference definition IP address of the
   singleton (single value) Round-trip delay metric.  Section 3.4 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
   [RFC2681] provides [RFC6991])

   T0 a time, the reference definition expanded to cover start of a
   multi-singleton sample.  Note that terms such measurement interval, (format "date-and-
      time" as singleton and sample
   are defined specified in Section 11 5.6 of [RFC2330].

   For DNS Response Latency, the entities in [RFC1035] must be mapped to
   [RFC2681]. [RFC3339], see also Section 3
      of [RFC6991]).  The Local Host with its User Program UTC Time Zone is required by Section 6.1 of
      [RFC2330].  When T0 is "all-zeros", a start time is unspecified
      and Resolver take Tf is to be interpreted as the role Duration of "Src", and the Foreign Name Server takes measurement
      interval.  The start time is controlled through other means.

   Tf a time, the role end of
   "Dst".

   Note that although the [RFC2681] definition a measurement interval, (format "date-and-time"
      as specified in Section 5.6 of "Round-trip-Delay
   between Src [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 Dst at T"
      Tf is directionally ambiguous in interpreted as the text,
   this metric tightens Duration of the definition further to recognize that measurement interval.

7.3.6.  Roles

   <lists the
   host in names of the "Src" role will send different roles from the first measurement method>

   Src  launches each packet to "Dst", and
   ultimately receive the corresponding waits for return transmissions from
      Dst. This is the TWAMP Session-Sender.

   Dst  waits for each packet from "Dst" (when
   neither are lost).

   Morton, A., "Round-trip Packet Loss Metrics", RFC 6673, August 2012.

   [RFC6673]

   Both response time Src and loss metrics employ sends a maximum waiting time for
   received responses, so the count of lost packets return packet to total packets
   sent Src.
      This is the basis TWAMP Session-Reflector.

7.4.  Output

   This category specifies all details of the Output of measurements
   using the metric.

7.4.1.  Type

   <insert name of the output type, raw or a selected summary statistic>

   See subsection titles below for Types.

7.4.2.  Reference Definition

   <describe the loss determination data format for each type of result>

   For all output types ---

   T0 the start of a measurement interval, (format "date-and-time" as per
      specified in Section 4.3 5.6 of
   [RFC6673].

6.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded [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].

   For LossRatio -- the measurement system count of lost packets to total packets sent is
   the basis for use when
   needed>

   Type-P the loss ratio calculation as defined in per Section 13 4.1 of
   [RFC7680].

   For each <statistic>, one of [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Source port: 53

      *  Destination port: 53

      *  Checksum: the checksum must following sub-sections apply:

7.4.2.1.  Percentile95

   The 95th percentile SHALL be calculated and included in using the
         header

   o  Payload: The payload contains conditional
   distribution of all packets with a DNS message finite value of One-way delay
   (undefined delays are excluded), a single value as defined in RFC 1035
      [RFC1035] with the following values:

      *  The DNS header follows:

   See section contains:

         +  Identification (see 4.1 of [RFC3393] for details on the Run-time column)

         +  QR: set to 0 (Query)

         +  OPCODE: set to 0 (standard query)

         +  AA: not set

         +  TC: not set

         +  RD: set to one (recursion desired)

         +  RA: not set

         +  RCODE: not set

         +  QDCOUNT: set conditional
   distribution to one (only one entry)

         +  ANCOUNT: not set

         +  NSCOUNT: not set

         +  ARCOUNT: not set

      *  The Question exclude undefined values of delay, and Section 5 of
   [RFC6703] for background on this analysis choice.

   See section contains:

         +  QNAME: 4.3 of [RFC3393] for details on the percentile statistic
   (where Round-trip delay should be substituted for "ipdv").

   The percentile = 95, meaning that the Fully Qualified Domain Name (FQDN) provided as
            input reported delay, "95Percentile",
   is the smallest value of one-way delay for which the test, see Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the Run-time column

         +  QTYPE: singleton
   one-way delay values in the query type provided as input conditional distribution.  See section
   11.3 of [RFC2330] for the test, see definition of the Run-time column

         +  QCLASS: set to 1 for IN

      * percentile statistic
   using the EDF.

   95Percentile  The other sections do not contain any Resource Records.

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time (and to help disambiguate
      queries)

      *  5.0, value of the result is expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 4 9 (see section 9.3 of [RFC6020]) and with resolution of 0.0001
      0.000000001 seconds (0.1 ms), (1.0 ns), and with lossless conversion to/from
      the 32-bit 64-bit NTP timestamp as per section 6 of [RFC5905].

   Observation: reply packets will contain a DNS response and may
   contain RRs.

6.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.

6.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   The methodology for this metric is defined as Type-P-Round-trip-
   Delay-Poisson-Stream in section 2.6 of RFC 2681 [RFC2681] and section
   3.6 of RFC 2681 [RFC2681] using the Type-P and Timeout defined under
   Fixed Parameters.

   The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is the waiting time used as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for the RLDNS metric.

   The calculations on the delay (RTT) [RFC5905]

7.4.2.2.  Mean

   The mean SHALL be performed on calculated using the conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when distribution of
   all packet packets with a finite value of One-way delay (undefined delays
   are stored, the process
   which calculates the RTT excluded), a single value MAY enforce the Tmax threshold on
   stored values before calculations. 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.

   The reference method requires some way to distinguish between
   different packets in a stream to establish correspondence between
   sending times and receiving times for each successfully-arriving
   reply.  Therefore, sequence numbers or other send-order
   identification MUST be retained at the Src or included with each
   packet to dis-ambiguate packet reordering if it occurs.  Sequence
   number is part

   See section 4.2.2 of the payload described under Fixed Parameters.

   DNS Messages bearing Queries provide [RFC6049] for random ID Numbers in the
   Identification header field, so more than one query may be launched
   while a previous request is outstanding when the ID Number is used.

   IF a DNS response does not arrive within Tmax, the response time is
   undefined, details on calculating this
   statistic, and RTDNS = 1. 4.2.3 of [RFC6049].

   Mean  The Message ID SHALL be used to
   disambiguate the successive queries.

   @@@@ This would require support time value of ID generation and population in the Message.  An alternative would be to use result is expressed in units of seconds,
      as a random Source port on
   the Query Message, but we would choose ONE before proceding.

   Refer to Section 4.4 positive value of [RFC6673] for expanded discussion 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
   instruction to "send a Type-P packet back to the Src as quickly 64-bit
      NTP timestamp as
   possible" in Section 2.6 per section 6 of RFC 2681 [RFC2681].  Section 8 of
   [RFC6673] presents additional requirements which shall [RFC5905]

7.4.2.3.  Min

   The minimum SHALL be included in calculated using the method conditional distribution of measurement for this metric.

   In addition to operations described in [RFC2681], the Src MUST parse
   the DNS headers
   all packets with a finite value of the reply and prepare the information for
   subsequent reporting as One-way delay (undefined delays
   are excluded), a measured result, along with the Round-Trip
   Delay.

6.3.2.  Packet Stream Generation

   This single value as follows:

   See section gives the details 4.1 of the packet traffic which is the
   basis [RFC3393] for measurement.  In IPPM metrics, this is called details on the Stream, conditional
   distribution to exclude undefined values of delay, and can easily be dscribed by providing the list Section 5 of stream
   parameters.

   <list
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of generation parameters [RFC6049] for details on calculating this
   statistic, and section/spec references if needed>
   Section 11.1.3 4.3.3 of RFC 2681 [RFC2330] provides three methods to
   generate Poisson sampling intervals. [RFC6049].

   Min  The reciprocal time value of lambda is the
   average packet rate, thus the Run-time Parameter result is Reciprocal_lambda
   = 1/lambda, expressed in seconds.

   Method 3 is used, where given units of seconds,
      as a start time (Run-time Parameter), the
   subsequent send times are all computed prior to measurement by
   computing 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 pseudo-random distribution 64-bit
      NTP timestamp as per section 6 of inter-packet send times,
   (truncating RFC [RFC5905]

7.4.2.4.  Max

   The maximum SHALL be calculated using the conditional distribution of
   all packets with a finite value of One-way delay (undefined delays
   are excluded), a single value as specified in the Run-time
   Parameters), and the Src sends each packet at the computed times.

   Note that Trunc is the upper limit follows:

   See section 4.1 of [RFC3393] for details on inter-packet times in the
   Poisson distribution.  A random value greater than Trunc is set equal conditional
   distribution to Trunc instead.

6.3.3.  Traffic Filtering (observation) Details

   The measured results based on a filtered version exclude undefined values of the packets
   observed, delay, and Section 5 of
   [RFC6703] for background on this analysis choice.

   See section provides the filter details (when
   present).

   <section reference>.

   NA

6.3.4.  Sampling Distribution

   <insert time distribution details, or how 4.3.2 of [RFC6049] for a closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is diff from
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value of the
   filter>

   NA

6.3.5.  Run-time Parameters 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 Data Format

   Run-time Parameters are input factors that must with lossless conversion to/from the 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

7.4.2.5.  Std_Dev

   The Std_Dev SHALL be determined,
   configured into calculated using the measurement system, and reported conditional distribution of
   all packets with the results a finite value of One-way delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details on the context conditional
   distribution to be complete.

   <list exclude undefined values of run-time parameters, delay, and their data formats>

   Src  the IP address Section 5 of the host in the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value
   [RFC6703] for IPv6,
      see Section 4 background on this analysis choice.

   See section 4.3.2 of [RFC6991])

   Dst  the IP address [RFC6049] for a closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   the host in the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value classic calculation for IPv6,
      see section 4 standard deviation of [RFC6991])

   T0 a time, population.

   Std_Dev  The time value of the start result is expressed in units of a measurement interval, (format "date-and-
      time"
      seconds, as specified in Section 5.6 a positive value of [RFC3339], see also Section 3 type decimal64 with fraction
      digits = 9 (see section 9.3 of [RFC6991]).  The UTC Time Zone is required by Section 6.1 [RFC6020]) with resolution of
      [RFC2330].  When T0 is "all-zeros", a start time is unspecified
      0.000000001 seconds (1.0 ns), and Tf is to be interpreted as with lossless conversion to/from
      the Duration 64-bit NTP timestamp as per section 6 of RFC [RFC5905]

7.4.3.  Metric Units

   <insert units for the measurement
      interval. measured results, and the reference
   specification>.

   The start time <statistic> of One-way Delay is controlled through other means.

   Tf expressed in seconds.

   The One-way Loss Ratio is expressed as a percentage of lost packets
   to total packets sent.

7.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a time, means to quantify the end
   systematic and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback that includes
   as much of the measurement interval, (format "date-and-time" system as specified in Section 5.6 possible, performs address
   manipulation as needed, and provides some form of [RFC3339], see also Section 3 isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 the random and systematic error can be characterized
   this way.

   For one-way delay measurements, the error calibration must include an
   assessment of
      [RFC2330].  When T0 the internal clock synchronization with its external
   reference (this internal clock is "all-zeros", a end supplying timestamps for
   measurement).  In practice, the time date is ignored offsets of clocks at both the
   source and
      Tf destination are needed to estimate the systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus the random variation is interpreted as not usually represented in the Duration
   results).

   time_offset  The time value of the measurement interval.

   Reciprocal_lambda  average packet interval for Poisson Streams result is expressed in units of
      seconds, as a positive signed value of type decimal64 with fraction digits
      = 4 9 (see section 9.3 of [RFC6020]) with resolution of 0.0001 0.000000001
      seconds (0.1 ms), (1.0 ns), and with lossless conversion to/from the 32-bit 64-bit
      NTP timestamp as per section 6 of
      [RFC5905].

   Trunc  Upper limit on Poisson distribution expressed RFC [RFC5905]

   When a measurement controller requests a calibration measurement, the
   loopback is applied and the result is output in units the same format as a
   normal measurement with additional indication that it is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate of time offset as an indicator of
   the degree of
      seconds, as a positive value synchronization.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the *available accuracy* of type decimal64 with fraction
      digits = 4 (see section 9.3 the Output Metric Units.
   For example, repeated loopback delay measurements will reveal the
   portion of [RFC6020]) with the Output result resolution of
      0.0001 seconds (0.1 ms), and with lossless conversion to/from which is the
      32-bit NTP timestamp as per section 6 result of [RFC5905] (values above system
   noise, and thus inaccurate.

7.5.  Administrative items

7.5.1.  Status

   <current or deprecated>

7.5.2.  Requestor (keep?)

   name or RFC, etc.

7.5.3.  Revision

   1.0

7.5.4.  Revision Date

   YYYY-MM-DD

7.6.  Comments and Remarks

   Additional (Informational) details for this limit will be clipped entry

8.  UDP Periodic One-way Delay and set Loss Registry Entries

   This section specifies five initial registry entries for the UDP
   Periodic One-way Delay, and one for UDP Periodic One-way Loss.

   IANA Note: Registry "Name" below specifies a single registry entry,
   whose output format varies according to the limit value). (if fixed,
      Trunc = 30.0000 seconds.)

   ID The 16-bit identifier assigned by <statistic> element of
   the program name that generates specifies one form of statistical summary.  There is an
   additional metric name for the
      query, Loss metric.

   All column entries beside the ID, Name, Description, and which must vary in successive queries, see
      Section 4.1.1 of [RFC1035].  This identifier Output
   Reference Method categories are the same, thus this section proposes
   six closely-related registry entries.  As a result, IANA is copied into also
   asked to assign corresponding URNs and URLs to each Named Metric.

8.1.  Summary

   This category includes multiple indexes to the
      corresponding reply and can be used by registry entries, the requester (Src) to
      match-up replies
   element ID and metric name.

8.1.1.  ID (Identifier)

   <insert numeric identifier, an integer, one corresponding to outstanding queries.

   QNAME  The domain each
   name below>

   IANA is asked to assign a different numeric identifiers to each of
   the Query, formatted as specified in
      section 4 of [RFC6991].

   QTYPE  The Query Type, which will correspond six Metrics.

8.1.2.  Name

   <insert name according to metric naming convention>

   OWDelay_Active_IP-UDP-Periodic-
   Payload142B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev
   OWLoss_Active_IP-UDP-Periodic-
   Payload142B_RFCXXXXsecY_Percent_LossRatio

8.1.3.  URIs

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http:\\www.iana.org\ ... <name>

8.1.4.  Description

   OWDelay: This metric assesses the IP address family delay of the query (decimal 1 for IPv4 or 28 for IPv6, formatted as a
      uint16, as per section 9.2 stream of [RFC6020].

6.3.6.  Roles

   <lists packets
   exchanged between two hosts (or measurement points), and reports the names of
   <statistic> One-way delay for all successfully exchanged packets
   based on their conditional delay distribution.

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses the different roles from loss ratio of a stream of packets
   exchanged between two hosts (which are the two measurement method>

   Src  launches each packet points),
   and waits for return transmissions from
      Dst.

   Dst  waits the Output is the One-way loss ratio for each packet from Src and sends all successfully
   received packets expressed as a return packet to Src.

6.4.  Output percentage.

8.2.  Metric Definition

   This category specifies all details of the Output of measurements
   using the metric.

6.4.1.  Type

   <insert name of includes columns to prompt the output type, raw or a selected summary statistic>

   Raw -- for each DNS Query packet sent, sets entry of values as defined in all necessary
   details related to the next column, metric definition, including the status of the response, only assigning
   delay RFC reference
   and values to successful query-response pairs.

6.4.2. of input factors, called fixed parameters.

8.2.1.  Reference Definition

   <describe the data format

   <Full bibliographic reference to an immutable doc.>

   For Delay:

   Almes, G., Kalidindi, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Delay Metric for each type IP Performance Metrics (IPPM)", STD 81, RFC
   7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
   editor.org/info/rfc7679>.

   [RFC7679]

   Morton, A., and Stephan, E., "Spatial Composition of result>

   For all outputs:

   T  the time the DNS Query was sent during the measurement interval,
      (format "date-and-time" as specified in Metrics", RFC
   6049, January 2011.

   [RFC6049]

   <specific section reference and additional clarifications, if needed>

   Section 5.6 3.4 of [RFC3339],
      see also Section 3 [RFC7679] provides the reference definition of [RFC6991]).  The UTC Time Zone is required
      by the
   singleton (single value) One-way delay metric.  Section 6.1 of [RFC2330].

   dT The time value 4.4 of
   [RFC7679] provides the round-trip delay reference definition expanded to receive the DNS
      response, expressed in units of seconds, as cover 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].  This value is undefined when the
      response packet is not received at Src within waiting time Tmxax
      seconds.

   Rcode  The value
   multi-value sample.  Note that terms such as singleton and sample are
   defined in Section 11 of the Rcode field [RFC2330].

   Only successful packet transfers with finite delay are included in
   the DNS response header,
      expressed as a uint64 sample, as specified prescribed in section 9.2 4.1.2 of [RFC6020].
      Non-zero values convey errors in the response, [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and such replies
      must be analyzed separately from successful requests.

6.4.3. A.  Morton, Ed., "A One-
   Way Loss Metric Units

   <insert units for the measured results, and IP Performance Metrics (IPPM)", RFC 7680, DOI
   10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
   rfc7680>.

   Section 2.4 of [RFC7680] provides the reference
   specification>.

   RTDNS: Round-trip Delay, dT, is expressed in seconds.

   RTLDNS: definition of the Logical value, where 1 = Lost and 0 = Received.

6.4.4.  Calibration
   singleton (single value) one-way loss metric.  Section 3.7.3 3.4 of [RFC7679]
   [RFC7680] provides a means to quantify the
   systematic and random errors of reference definition expanded to cover a time measurement.  In-situ
   calibration could be enabled with an internal loopback at the Source
   host
   multi-singleton sample.  Note that includes terms such as much singleton and sample
   are defined in Section 11 of [RFC2330].

8.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the measurement system as possible,
   performs address and payload manipulation as needed, and provides
   some form of isolation (e.g., deterministic delay) for use when
   needed>

   Type-P:

   o  IPv4 header values:

      *  DSCP: set to avoid send-
   receive interface contention.  Some portion of 0

      *  TTL: set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: the random and
   systematic error can checksum MUST be characterized this way.

   When a measurement controller requests a calibration measurement, the
   loopback is applied calculated and included in the result is output
         header

   o  UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357]

      *  Security features in use influence the same number of Padding
         octets.

      *  142 octets total, including the TWAMP format as a
   normal

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with additional indication that it is value 3.0, expressed in
      units of seconds, as a
   calibration result.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the *available accuracy* positive value of the Output Metric Units.
   For example, repeated loopback delay measurements will reveal the
   portion type decimal64 with
      fraction digits = 4 (see section 9.3 of the Output result [RFC6020]) and with
      resolution which is of 0.0001 seconds (0.1 ms), with lossless conversion
      to/from the result 32-bit NTP timestamp as per section 6 of system
   noise, and thus inaccurate.

6.5.  Administrative items

6.5.1.  Status

   <current or depricated>

6.5.2.  Requestor

   name or RFC, etc.

6.5.3.  Revision

   1.0

6.5.4.  Revision Date

   YYYY-MM-DD

6.6.  Comments and Remarks

   Additional (Informational) details [RFC5905].

   See the Packet Stream generation category for this entry

7.  UDP Poisson One-way Delay and Loss Registry Entries two additional Fixed
   Parameters.

8.3.  Method of Measurement

   This section specifies five initial registry entries for the UDP
   Poisson One-way Delay, and one category includes columns for UDP Poisson One-way Loss.

   IANA Note: Registry "Name" below specifies a single registry entry,
   whose output format varies according references to the <statistic> element relevant sections of
   the name that specifies one form of statistical summary.  There is RFC(s) and any supplemental information needed to ensure an
   additional metric name
   unambiguous methods for the Loss metric.

   All column entries beside the ID, Name, Description, and Output implementations.

8.3.1.  Reference Method categories are the same, thus this

   <for metric, insert relevant section proposes
   six closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to each Named Metric.

7.1.  Summary

   This category includes multiple indexes to the registry entries, the
   element ID references and supplemental
   info>

   The methodology for this metric name.

7.1.1.  ID (Identifier)

   <insert numeric identifier, an integer, one corresponding to each
   name below>

   IANA is asked to assign different numeric identifiers to each defined as Type-P-One-way-Delay-
   Poisson-Stream in section 3.6 of the
   six Metrics.

7.1.2.  Name

   <insert name according to metric naming convention>

   OWDelay_Active_IP-UDP-Poisson-
   Payload250B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev
   OWLoss_Active_IP-UDP-Poisson-
   Payload250B_RFCXXXXsecY_Percent_LossRatio

7.1.3.  URI [RFC7679] and URL

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http:\\www.iana.org\ ... <name>

7.1.4.  Description

   OWDelay: This metric assesses the delay section 4.6 of
   [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
   However, a Periodic stream of packets
   exchanged is used, as defined in [RFC3432].

   The reference method distinguishes between two hosts (or measurement points), long-delayed packets and reports the
   <statistic> One-way delay for all successfully exchanged
   lost packets
   based on their conditional delay distribution.

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses by implementing a maximum waiting time for packet
   arrival.  Tmax is the loss ratio of waiting time used as the threshold to declare a stream of
   packet lost.  Lost packets
   exchanged between two hosts (which are the two measurement points), SHALL be designated as having undefined
   delay, and counted for the Output is OWLoss metric.

   The calculations on the One-way loss ratio for one-way delay SHALL be performed on the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all successfully
   received packets expressed as a percentage.

7.2.  Metric Definition

   This category includes columns to prompt packet delays are stored, the entry process
   which calculates the one-way delay value MAY enforce the Tmax
   threshold on stored values before calculations.  See section 4.1 of all necessary
   [RFC3393] for details related to the metric definition, including on the RFC reference
   and conditional distribution to exclude
   undefined values of input factors, called fixed parameters.

7.2.1.  Reference Definition

   <Full bibliographic delay, and Section 5 of [RFC6703] for background
   on this analysis choice.

   The reference method requires some way to an immutable doc.>

   For Delay:

   Almes, G., Kalidindi, S., Zekauskas, M., distinguish between
   different packets in a stream to establish correspondence between
   sending times and A.  Morton, Ed., "A One-
   Way Delay Metric receiving times for IP Performance Metrics (IPPM)", STD 81, RFC
   7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
   editor.org/info/rfc7679>.

   [RFC7679]

   Morton, A., each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the Src or included with each packet to disambiguate
   packet reordering if it occurs.

   Since a standard measurement protocol is employed [RFC5357], then the
   measurement process will determine the sequence numbers or timestamps
   applied to test packets after the Fixed and Stephan, E., "Spatial Composition Runtime parameters are
   passed to that process.  The measurement protocol dictates the format
   of Metrics", RFC
   6049, January 2011.

   [RFC6049]

   <specific section reference sequence numbers and additional clarifications, time-stamps conveyed in the TWAMP-Test packet
   payload.

8.3.2.  Packet Stream Generation

   <list of generation parameters and section/spec references if needed>

   Section 3.4 of [RFC7679] provides

   This section gives the reference definition details of the
   singleton (single value) One-way delay metric.  Section 4.4 of
   [RFC7679] provides packet traffic which is the reference definition expanded to cover a
   multi-value sample.  Note that terms such as singleton
   basis for measurement.  In IPPM metrics, this is called the Stream,
   and sample are
   defined in can easily be described by providing the list of stream
   parameters.

   Section 11 3 of [RFC2330].

   Only successful packet transfers with finite delay are included in [RFC3432] prescribes the sample, as prescribed in section 4.1.2 of [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Loss Metric method for IP Performance Metrics (IPPM)", RFC 7680, DOI
   10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
   rfc7680>.

   Section 2.4 generating Periodic
   streams using associated parameters.

   incT  the nominal duration of [RFC7680] provides inter-packet interval, first bit to
      first bit

   dT the reference definition duration of the
   singleton (single value) one-way loss metric.  Section 3.4 interval for allowed sample start times

   T0 the actual start time of
   [RFC7680] provides the reference definition expanded periodic stream
   NOTE: an initiation process with a number of control exchanges
   resulting in unpredictable start times (within a time interval) may
   be sufficient to cover avoid synchronization of periodic streams, and
   therefore a valid replacement for selecting a start time at random
   from a
   multi-singleton sample.  Note that terms such fixed interval.

   These stream parameters will be specified as singleton and sample
   are defined in Section 11 of [RFC2330].

7.2.2.  Fixed Run-time parameters.

8.3.3.  Traffic Filtering (observation) Details

   NA

8.3.4.  Sampling Distribution

   NA

8.3.5.  Run-time Parameters

   <list and specify Fixed Parameters, Data Format

   Run-time Parameters are input factors that must be
   determined and embedded in determined,
   configured into the measurement system system, and reported with the results
   for use when
   needed>

   Type-P:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set to 17 (UDP)

   o  UDP header values:

      *  Checksum: the checksum MUST context to be calculated complete.

   <list of run-time parameters, and included their data formats>

   Src  the IP address of the host in the
         header

   o  UDP Payload: TWAMP Test Packet Formats, Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see Section 4.1.2 4 of [RFC5357]

      *  Security features in use influence [RFC6991])

   Dst  the number IP address of Padding
         octets.

      *  250 octets total, including the TWAMP format

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value 3.0, expressed host in
      units of seconds, as a positive the Dst Role (format ipv4-address-
      no-zone value of type decimal64 with
      fraction digits = 4 (see for IPv4, or ipv6-address-no-zone value for IPv6,
      see section 9.3 of [RFC6020]) and with
      resolution 4 of 0.0001 seconds (0.1 ms), with lossless conversion
      to/from [RFC6991])

   T0 a time, the 32-bit NTP timestamp start of a measurement interval, (format "date-and-
      time" as per section 6 specified in Section 5.6 of [RFC5905].

   See the Packet Stream generation category for two additional Fixed
   Parameters.

7.3.  Method [RFC3339], see also Section 3
      of Measurement

   This category includes columns for references to relevant sections [RFC6991]).  The UTC Time Zone is required by Section 6.1 of
   the RFC(s)
      [RFC2330].  When T0 is "all-zeros", a start time is unspecified
      and any supplemental information needed Tf is to ensure an
   unambiguous methods for implementations.

7.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info> be interpreted as the Duration of the measurement
      interval.  The methodology for this metric start time is defined controlled through other means.

   Tf a time, the end of a measurement interval, (format "date-and-time"
      as Type-P-One-way-Delay-
   Poisson-Stream specified in section 3.6 Section 5.6 of [RFC7679] and section 4.6 [RFC3339], see also Section 3 of
   [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
      [RFC6991]).  The reference method distinguishes between long-delayed packets and
   lost packets UTC Time Zone is required by implementing Section 6.1 of
      [RFC2330].  When T0 is "all-zeros", a maximum waiting end time for packet
   arrival.  Tmax date is the waiting time used ignored and
      Tf is interpreted as the threshold to declare Duration of the measurement interval.

   @@@@ should Periodic run-time params be fixed instead?  Probably yes
   if modeling a specific version of tests.  Note in the NAME, i.e.
   Poisson3.3

8.3.6.  Roles

   <lists the names of the different roles from the measurement method>

   Src  launches each packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted waits for return transmissions from
      Dst. This is the OWLoss metric.

   The calculations on the one-way delay SHALL be performed on the
   conditional distribution, conditioned on successful TWAMP Session-Sender.

   Dst  waits for each packet arrival
   within Tmax.  Also, when all from Src and sends a return packet delays are stored, the process
   which calculates the one-way delay value MAY enforce to Src.
      This is the Tmax
   threshold on stored values before calculations.  See section 4.1 of
   [RFC3393] for TWAMP Session-Reflector.

8.4.  Output

   This category specifies all details on of the conditional distribution to exclude
   undefined values Output of delay, and Section 5 measurements
   using the metric.

8.4.1.  Type

   <insert name of [RFC6703] for background
   on this analysis choice.

   The reference method requires some way to distinguish between
   different packets in the output type, raw or a stream to establish correspondence between
   sending times and receiving times selected summary statistic>

   See subsection titles in Reference Definition for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at Latency Types.

8.4.2.  Reference Definition

   <describe the Src or included with data format for each packet to dis-ambiguate
   packet reordering if it occurs.

   Since type of result>

   For all output types ---

   T0 the start of a standard measurement protocol interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is employed [RFC5357], then required by Section 6.1 of
      [RFC2330].

   Tf the end of a measurement process will determine the sequence numbers or timestamps
   applied to test packets after the Fixed and Runtime parameters are
   passed to that process. interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The measurement protocol dictates the format UTC Time Zone is required by Section 6.1 of sequence numbers and time-stamps conveyed in the TWAMP-Test packet
   payload.

7.3.2.  Packet Stream Generation

   This section gives
      [RFC2330].

   For LossRatio -- the details count of the packet traffic which lost packets to total packets sent is
   the basis for measurement.  In IPPM metrics, this is called the Stream,
   and can easily loss ratio calculation as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one of the following sub-sections apply:

8.4.2.1.  Percentile95

   The 95th percentile SHALL be dscribed by providing calculated using the list conditional
   distribution of stream
   parameters.

   <list all packets with a finite value of generation parameters One-way 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/spec references if needed> Section 11.1.3 5 of RFC 2681 [RFC2330] provides three methods to
   generate Poisson sampling intervals. the reciprocal
   [RFC6703] for background on this analysis choice.

   See section 4.3 of lambda is [RFC3393] for details on the
   average packet spacing, thus percentile statistic
   (where Round-trip delay should be substituted for "ipdv").

   The percentile = 95, meaning that the Run-time Parameter reported delay, "95Percentile",
   is
   Reciprocal_lambda = 1/lambda, in seconds.

   Method 3 SHALL be used, where given a start time (Run-time
   Parameter), the subsequent send times are all computed prior to
   measurement by computing smallest value of one-way delay for which the pseudo-random distribution Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of inter-
   packet send times, (truncating the distribution as specified singleton
   one-way delay values in the
   Parameter Trunc), and the Src sends each packet at the computed
   times.

   Note that Trunc is conditional distribution.  See section
   11.3 of [RFC2330] for the upper limit on inter-packet times in definition of the
   Poisson distribution.  A random percentile statistic
   using the EDF.

   95Percentile  The time value greater than Trunc of the result is set equal
   to Trunc instead.

   Reciprocal_lambda  average packet interval for Poisson Streams expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 4 9 (see section 9.3 of [RFC6020]) with resolution of 0.0001
      0.000000001 seconds (0.1 ms), (1.0 ns), and with lossless conversion to/from
      the 32-bit 64-bit NTP timestamp as per section 6 of
      [RFC5905].  Reciprocal_lambda = 1 packet per second.

   Trunc  Upper limit on Poisson RFC [RFC5905]

8.4.2.2.  Mean

   The mean SHALL be calculated using the conditional distribution expressed in units of
      seconds, as
   all packets with a positive finite value of type decimal64 with fraction
      digits = 4 (see section 9.3 of [RFC6020]) with resolution of
      0.0001 seconds (0.1 ms), and with lossless conversion to/from the
      32-bit NTP timestamp One-way delay (undefined delays
   are excluded), a single value as per follows:

   See section 6 4.1 of [RFC5905] (values above
      this limit will be clipped and set to the limit value).  Trunc =
      30.0000 seconds.

7.3.3.  Traffic Filtering (observation) Details

   NA

7.3.4.  Sampling Distribution

   NA

7.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the measurement system, and reported with the results [RFC3393] for details on the context conditional
   distribution to be complete.

   <list exclude undefined values of run-time parameters, delay, and their data formats>

   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 5 of [RFC6991])

   Dst  the IP address
   [RFC6703] for background on this analysis choice.

   See section 4.2.2 of the host in the Dst Role (format ipv4-address-
      no-zone value [RFC6049] for IPv4, or ipv6-address-no-zone details on calculating this
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time value for IPv6,
      see section 4 of [RFC6991])

   T0 a time, the start result is expressed in units of a measurement interval, (format "date-and-
      time" seconds,
      as specified in Section 5.6 a positive value of [RFC3339], see also Section 3 type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC6991]).  The UTC Time Zone is required by Section 6.1 [RFC6020]) with resolution of
      [RFC2330].  When T0 is "all-zeros", a start time is unspecified 0.000000001
      seconds (1.0 ns), and Tf is to be interpreted as with lossless conversion to/from the Duration 64-bit
      NTP timestamp as per section 6 of the measurement
      interval. RFC [RFC5905]

8.4.2.3.  Min

   The start time is controlled through other means.

   Tf a time, minimum SHALL be calculated using the end conditional distribution of
   all packets with 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 finite value of
      [RFC2330].  When T0 is "all-zeros", One-way delay (undefined delays
   are excluded), a end time date is ignored and
      Tf is interpreted single value as the Duration follows:

   See section 4.1 of [RFC3393] for details on the measurement interval.

7.3.6.  Roles

   <lists the names conditional
   distribution to exclude undefined values of the different roles from the measurement method>

   Src  launches each packet delay, and waits for return transmissions from
      Dst. This is the TWAMP Session-Sender.

   Dst  waits Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of [RFC6049] for each packet from Src and sends a return packet to Src.
      This is the TWAMP Session-Reflector.

7.4.  Output

   This category specifies all details on calculating this
   statistic, and 4.3.3 of the Output [RFC6049].

   Min  The time value of measurements
   using the metric.

7.4.1.  Type

   <insert name result is expressed in units of the output type, raw or seconds,
      as a selected summary statistic>

   See subsection titles below for Types.

7.4.2.  Reference Definition

   <describe the data format for each positive value of type decimal64 with fraction digits = 9
      (see section 9.3 of result>

   For all output types ---

   T0 [RFC6020]) with resolution of 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from the start 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

8.4.2.4.  Max

   The maximum SHALL be calculated using the conditional distribution of
   all packets with a measurement interval, (format "date-and-time" finite value of One-way delay (undefined delays
   are excluded), a single value as
      specified in Section 5.6 follows:

   See section 4.1 of [RFC3339], see also Section 3 [RFC3393] for details on the conditional
   distribution to exclude undefined values of
      [RFC6991]).  The UTC Time Zone is required by delay, and Section 6.1 5 of
      [RFC2330].

   Tf the end
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of [RFC6049] for a measurement interval, (format "date-and-time" closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   as
      specified follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value of the result is expressed in Section 5.6 units of [RFC3339], see also Section 3 seconds,
      as a positive value of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 type decimal64 with fraction digits = 9
      (see section 9.3 of
      [RFC2330].

   For LossRatio -- the count [RFC6020]) with resolution of lost packets to total packets sent is
   the basis for 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from the loss ratio calculation 64-bit
      NTP timestamp as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one section 6 of the following sub-sections apply:

7.4.2.1.  Percentile95 RFC [RFC5905]

8.4.2.5.  Std_Dev

   The 95th percentile Std_Dev SHALL be calculated using the conditional distribution of
   all packets with a finite value of One-way 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.3 4.3.2 of [RFC3393] [RFC6049] for details on a closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   the percentile statistic
   (where Round-trip delay should be substituted classic calculation for "ipdv"). standard deviation of a population.

   Std_Dev  The percentile time value of the result is expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 95, meaning that 9 (see section 9.3 of [RFC6020]) with resolution of
      0.000000001 seconds (1.0 ns), and with lossless conversion to/from
      the reported delay, "95Percentile", 64-bit NTP timestamp as per section 6 of RFC [RFC5905]

8.4.3.  Metric Units

   <insert units for the measured results, and the reference
   specification>.

   The <statistic> of One-way Delay is expressed in seconds, where
   <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev

   The One-way Loss Ratio is expressed as a percentage of lost packets
   to total packets sent.

8.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means to quantify the smallest value
   systematic and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback that includes
   as much of the measurement system as possible, performs address
   manipulation as needed, and provides some form of one-way delay for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of the singleton random and systematic error can be characterized
   this way.

   For one-way delay values in measurements, the conditional distribution.  See section
   11.3 error calibration must include an
   assessment of [RFC2330] the internal clock synchronization with its external
   reference (this internal clock is supplying timestamps for
   measurement).  In practice, the definition time offsets of clocks at both the percentile statistic
   using
   source and destination are needed to estimate the EDF.

   95Percentile systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus the random variation is not usually represented in the
   results).

   time_offset  The time value of the result is expressed in units of
      seconds, as a positive signed 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]

7.4.2.2.  Mean

   The mean SHALL be calculated using

   When a measurement controller requests a calibration measurement, the conditional distribution of
   all packets
   loopback is applied and the result is output in the same format as a
   normal measurement with additional indication that it is a finite value
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate of One-way delay (undefined delays
   are excluded), a single value time offset as follows:

   See an indicator of
   the degree of synchronization.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the *available accuracy* of the Output Metric Units.
   For example, repeated loopback delay measurements will reveal the
   portion of the Output result resolution which is the result of system
   noise, and thus inaccurate.

8.5.  Administrative items

8.5.1.  Status

   <current or deprecated>

8.5.2.  Requestor (keep?)

   name or RFC, etc.

8.5.3.  Revision

   1.0

8.5.4.  Revision Date

   YYYY-MM-DD

8.6.  Comments and Remarks

   Additional (Informational) details for this entry

9.  ICMP Round-trip Latency and Loss Registry Entries

   This section 4.1 of [RFC3393] specifies three initial registry entries for details on the conditional
   distribution to exclude undefined values of delay, ICMP
   Round-trip Latency, and Section 5 of
   [RFC6703] another entry for background on this analysis choice.

   See ICMP Round-trip Loss Ratio.

   This section 4.2.2 of [RFC6049] for details on calculating specifies four Registry entries with many common
   columns.

   All column entries beside the ID, Name, Description, and Output
   Reference Method categories are the same, thus this
   statistic, section proposes
   two closely-related registry entries.  As a result, IANA is also
   asked to assign four corresponding URNs and 4.2.3 of [RFC6049].

   Mean  The time value URLs to each Named
   Metric.

9.1.  Summary

   This category includes multiple indexes to the registry entry: the
   element ID and metric name.

9.1.1.  ID (Identifier)

   <insert a numeric identifier, an integer, TBD>

   IANA is asked to assign different numeric identifiers to each of the result
   four Named Metrics.

9.1.2.  Name

   <insert name according to metric naming convention>

   RTDelay_Active_IP-ICMP-SendOnRcv_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is expressed in units one of:

   o  Mean

   o  Min

   o  Max

   RTLoss_Active_IP-ICMP-SendOnRcv_RFCXXXXsecY_Percent_LossRatio

9.1.3.  URIs

   URN: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

9.1.4.  Description

   RTDelay: This metric assesses the delay of seconds,
      as a positive value of type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC6020]) with resolution stream of 0.000000001
      seconds (1.0 ns), ICMP packets
   exchanged between two hosts (which are the two measurement points),
   and with lossless conversion to/from the 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

7.4.2.3.  Min

   The minimum SHALL be calculated using Output is the Round-trip delay for all successfully exchanged
   packets expressed as the <statistic> of their conditional distribution delay
   distribution, where <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   RTLoss: This metric assesses the loss ratio of
   all packets with a finite value stream of One-way delay (undefined delays ICMP
   packets exchanged between two hosts (which are excluded), a single value the two measurement
   points), and the Output is the Round-trip loss ratio for all
   successfully exchanged packets expressed as follows:

   See section 4.1 a percentage.

9.1.5.  Change Controller

   IETF

9.1.6.  Version (of Registry Format)

   1.0

9.2.  Metric Definition

   This category includes columns to prompt the entry of [RFC3393] for all necessary
   details on the conditional
   distribution related to exclude undefined the metric definition, including the RFC reference
   and values of delay, input factors, called fixed parameters.

9.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   Almes, G., Kalidindi, S., and Section 5 of
   [RFC6703] M.  Zekauskas, "A Round-trip Delay
   Metric for background on this analysis choice.

   See IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific section 4.3.2 reference and additional clarifications, if needed>

   Section 2.4 of [RFC6049] for details on calculating this
   statistic, [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 4.3.3 sample
   are defined in Section 11 of [RFC6049].

   Min  The time value [RFC2330].

   Note that although the [RFC2681] 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 result corresponding return packet from "Dst" (when neither are
   lost).

   Finally, note that the variable "dT" is expressed used in units of seconds,
      as a positive [RFC2681] to refer to
   the value of type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC6020]) with resolution of 0.000000001
      seconds (1.0 ns), Round-trip delay in metric definitions and with lossless conversion to/from the 64-bit
      NTP timestamp methods.  The
   variable "dT" has been re-used in other IPPM literature to refer to
   different quantities, and cannot be used as per section 6 of a global variable name.

   Morton, A., "Round-trip Packet Loss Metrics", RFC [RFC5905]

7.4.2.4.  Max

   The 6673, August 2012.

   [RFC6673]

   Both delay and loss metrics employ a maximum SHALL be calculated using waiting time for
   received packets, so the conditional distribution count of
   all lost packets with a finite value of One-way delay (undefined delays
   are excluded), a single value to total packets sent
   is the basis for the loss ratio calculation as follows:

   See section 4.1 per Section 6.1 of [RFC3393] for details on
   [RFC6673].

9.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the conditional
   distribution to exclude undefined values measurement system for use when
   needed>

   Type-P as defined in Section 13 of delay, [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255

      *  Protocol: Set to 01 (ICMP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Limit: set to 255

      *  Protocol: Set to 01 (ICMP)

   o  ICMP header values:

      *  Type: 8 (Echo Request)

      *  Code: 0

      *  Checksum: the checksum MUST be calculated and included in the
         header

      *  (Identifier and Section 5 Sequence Number set at Run-Time)

   o  ICMP Payload

      *  total of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 32 bytes of [RFC6049] for random info

   Other measurement parameters:

   o  Tmax: a closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The loss threshold waiting time value of the result is

      *  3.0, expressed in units of seconds, as a positive value of type
         decimal64 with fraction digits = 9 4 (see section 9.3 of
         [RFC6020]) and with resolution of 0.000000001 0.0001 seconds (1.0 ns), and (0.1 ms), with
         lossless conversion to/from the 64-bit 32-bit NTP timestamp as per
         section 6 of [RFC5905].

9.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.

9.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   The methodology for this metric is defined as Type-P-Round-trip-
   Delay-Poisson-Stream in section 2.6 of RFC [RFC5905]

7.4.2.5.  Std_Dev 2681 [RFC2681] and section
   3.6 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under
   Fixed Parameters.

   The Std_Dev reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is the waiting time used as the threshold to declare a
   packet lost.  Lost packets SHALL be calculated using designated as having undefined
   delay, and counted for the RTLoss metric.

   The calculations on the delay (RTD) SHALL be performed on the
   conditional distribution of distribution, conditioned on successful packet arrival
   within Tmax.  Also, when all packets with a finite value of One-way delay (undefined packet delays are excluded), a single stored, the process
   which calculates the RTD value as follows: MAY enforce the Tmax threshold on
   stored values before calculations.  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.3.2

   The reference method requires some way to distinguish between
   different packets in a stream to establish correspondence between
   sending times and receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be
   retained at the Src or included with each packet to disambiguate
   packet reordering if it occurs.

   The measurement process will determine the sequence numbers applied
   to test packets after the Fixed and Runtime parameters are passed to
   that process.  The ICMP measurement process and protocol will dictate
   the format of [RFC6049] sequence numbers and other identifiers.

   Refer to Section 4.4 of [RFC6673] for expanded discussion of the
   instruction to "send a closely related Type-P packet back to the Src as quickly as
   possible" in Section 2.6 of RFC 2681 [RFC2681].  Section 8 of
   [RFC6673] presents additional requirements which MUST be included in
   the method of measurement for
   calculating this statistic, and 4.3.3 metric.

9.3.2.  Packet Stream Generation

   This section gives the details of [RFC6049].  The formula the packet traffic which is the classic calculation
   basis for standard deviation measurement.  In IPPM metrics, this is called the Stream,
   and can easily be described by providing the list of a population.

   Std_Dev stream
   parameters.

   The time value of the result ICMP metrics use a sending discipline called "SendOnRcv" or Send
   On Receive.  This is expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 9 (see section 9.3 modification of [RFC6020]) with resolution Section 3 of
      0.000000001 seconds (1.0 ns), and with lossless conversion to/from [RFC3432], which
   prescribes the method for generating Periodic streams using
   associated parameters:

   incT  the 64-bit NTP timestamp as per section 6 nominal duration of RFC [RFC5905]

7.4.3.  Metric Units

   <insert units inter-packet interval, first bit to
      first bit

   dT the duration of the interval for allowed sample start times

   T0 the measured results, and actual start time of the reference
   specification>. periodic stream

   The <statistic> of One-way Delay incT and T0 stream parameters will be specified as Run-time
   parameters, dT is expressed not used in seconds.

   The One-way Loss Ratio is expressed as SendOnRcv.

   A SendOnRcv sender behaves exactly like a percentage of lost packets
   to total Periodic stream generator
   while all reply packets sent.

7.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides arrive with RTD < incT, and the inter-packet
   interval will be constant.

   If a means to quantify reply packet arrives with RTD >= incT, then the
   systematic and random errors of inter-packet
   interval for the next sending time is nominally RTD.

   If a reply packet fails to arrive within Tmax, then the inter-packet
   interval for the next sending time measurement.  In-situ
   calibration could be enabled with is nominally Tmax.

   If an internal loopback that includes
   as much immediate send on reply arrival is desired, then set incT=0.

9.3.3.  Traffic Filtering (observation) Details

   The measured results based on a filtered version of the measurement system as possible, performs address
   manipulation as needed, packets
   observed, and this section provides some form of isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of the random and systematic error can be characterized filter details (when
   present).

   <section reference>.

   NA

9.3.4.  Sampling Distribution

   <insert time distribution details, or how this way.

   For one-way delay measurements, is diff from the error calibration must include an
   assessment of
   filter>

   NA

9.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the internal clock synchronization measurement system, and reported with its external
   reference (this internal clock is supplying timestamps the results
   for
   measurement).  In practice, the time offsets context to be complete.

   <list of clocks at both the
   source run-time parameters, and destination are needed to estimate their data formats>

   Src  the systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus IP address of the random variation is not usually represented host in the
   results).

   time_offset  The time 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 result is expressed in units IP address of
      seconds, as a signed the host in the Dst Role (format ipv4-address-
      no-zone value of type decimal64 with fraction digits
      = 9 (see for IPv4, or ipv6-address-no-zone value for IPv6,
      see section 9.3 of [RFC6020]) with resolution 4 of 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from [RFC6991])

   T0 a time, the 64-bit
      NTP timestamp as per section 6 start of RFC [RFC5905]

   When a measurement controller requests 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 calibration measurement, the
   loopback start time is applied unspecified
      and the result Tf is output in the same format to be interpreted as a
   normal measurement with additional indication that it is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate Duration of the measurement
      interval.  The start time offset is controlled through other means.

   Count  The total count of ICMP Echo Requests to send, formatted as a
      uint16, as an indicator per section 9.2 of [RFC6020].

   (see the degree Packet Stream Generation section for additional Run-time
   parameters)

9.3.6.  Roles

   <lists the names of synchronization.

   Both internal loopback calibration the different roles from the measurement method>

   Src  launches each packet and clock synchronization can be
   used waits for return transmissions from
      Dst.

   Dst  waits for each packet from Src and sends a return packet to estimate the *available accuracy* Src.

9.4.  Output

   This category specifies all details of the Output Metric Units.
   For example, repeated loopback delay of measurements will reveal
   using the
   portion metric.

9.4.1.  Type

   <insert name of the Output result resolution which is the result of system
   noise, and thus inaccurate.

7.5.  Administrative items

7.5.1.  Status

   <current or depricated>

7.5.2.  Requestor (keep?)

   name output type, raw or RFC, etc.

7.5.3.  Revision

   1.0

7.5.4.  Revision Date

   YYYY-MM-DD

7.6.  Comments and Remarks

   Additional (Informational) details a selected summary statistic>

   See subsection titles in Reference Definition for this entry

8.  UDP Periodic One-way Delay and Loss Registry Entries

   This section specifies five initial registry entries Latency Types.

   LossRatio -- the count of lost packets to total packets sent is the
   basis for the UDP
   Periodic One-way Delay, and one loss ratio calculation as per Section 6.1 of [RFC6673].

9.4.2.  Reference Definition

   <describe the data format for UDP Periodic One-way Loss.

   IANA Note: Registry "Name" below specifies a single registry entry,
   whose each type of result>

   For all output format varies according to types ---

   T0 the <statistic> element 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 name that specifies one form end of statistical summary.  There 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 an
   additional metric name for the Loss metric.

   All column entries beside required by Section 6.1 of
      [RFC2330].

   TotalCount  the ID, Name, Description, and Output
   Reference Method categories are count of packets actually sent by the same, thus this section proposes
   six closely-related registry entries.  As a result, IANA is also
   asked to assign corresponding URNs and URLs to each Named Metric.

8.1.  Summary

   This category includes multiple indexes Src to Dst
      during the registry entries, measurement interval.

   For LossRatio -- the
   element ID and metric name.

8.1.1.  ID (Identifier)

   <insert numeric identifier, an integer, one corresponding count of lost packets to each
   name below>

   IANA total packets sent is asked to assign a different numeric identifiers to
   the basis for the loss ratio calculation as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one of the six Metrics.

8.1.2.  Name

   <insert name according to metric naming convention>

   OWDelay_Active_IP-UDP-Periodic-
   Payload142B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  95Percentile

   o following sub-sections apply:

9.4.2.1.  Mean

   o  Min

   o  Max

   o  StdDev
   OWLoss_Active_IP-UDP-Periodic-
   Payload142B_RFCXXXXsecY_Percent_LossRatio

8.1.3.  URIs

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL: http:\\www.iana.org\ ... <name>

8.1.4.  Description

   OWDelay: This metric assesses

   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].

   Mean  The time value of the delay result is expressed in units of seconds,
      as a stream positive value of packets
   exchanged between two hosts (or measurement points), type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC6020]) with resolution of 0.000000001
      seconds (1.0 ns), and reports with lossless conversion to/from the
   <statistic> One-way delay for all successfully exchanged packets
   based on their conditional delay distribution.

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

9.4.2.2.  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses

   The minimum SHALL be calculated using the loss ratio conditional distribution of
   all packets with a stream finite value of packets
   exchanged between two hosts (which Round-trip delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details on the two measurement points), conditional
   distribution to exclude undefined values of delay, and Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of [RFC6049] for details on calculating this
   statistic, and 4.3.3 of [RFC6049].

   Min  The time value of the Output result is the One-way loss ratio for all successfully
   received packets expressed in units of seconds,
      as a percentage.

8.2.  Metric Definition

   This category includes columns to prompt 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]

9.4.2.3.  Max

   The maximum SHALL be calculated using the entry conditional distribution of
   all necessary 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 related to the metric definition, including on the RFC reference
   and conditional
   distribution to exclude undefined values of input factors, called fixed parameters.

8.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   For Delay:

   Almes, G., Kalidindi, S., Zekauskas, M., delay, and A.  Morton, Ed., "A One-
   Way Delay Metric Section 5 of
   [RFC6703] for IP Performance Metrics (IPPM)", STD 81, RFC
   7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
   editor.org/info/rfc7679>.

   [RFC7679]

   Morton, A., and Stephan, E., "Spatial Composition background on this analysis choice.

   See section 4.3.2 of Metrics", RFC
   6049, January 2011. [RFC6049]

   <specific section reference for a closely related method for
   calculating this statistic, and additional clarifications, if needed>

   Section 3.4 4.3.3 of [RFC7679] provides the reference definition [RFC6049].  The formula is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value of the
   singleton (single value) One-way delay metric.  Section 4.4 result is expressed in units of
   [RFC7679] provides the reference definition expanded to cover a
   multi-value sample.  Note that terms such seconds,
      as singleton and sample are
   defined in Section 11 a positive value of [RFC2330].

   Only successful packet transfers type decimal64 with finite delay are included in 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 sample, 64-bit
      NTP timestamp as prescribed in per section 4.1.2 6 of [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Loss RFC [RFC5905]

9.4.3.  Metric Units

   <insert units for IP Performance Metrics (IPPM)", RFC 7680, DOI
   10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
   rfc7680>.

   Section 2.4 of [RFC7680] provides the measured results, and the reference definition
   specification>.

   The <statistic> of the
   singleton (single value) one-way loss metric. Round-trip Delay is expressed in seconds, where
   <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   The Round-trip Loss Ratio is expressed as a percentage of lost
   packets to total packets sent.

9.4.4.  Calibration

   Section 3.4 3.7.3 of
   [RFC7680] [RFC7679] provides the reference definition expanded a means to cover quantify the
   systematic and random errors of a
   multi-singleton sample.  Note time measurement.  In-situ
   calibration could be enabled with an internal loopback at the Source
   host that terms such includes as singleton and sample
   are defined in Section 11 much of [RFC2330].

8.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the measurement system for use when
   needed>

   Type-P:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL: set to 255
      *  Protocol: Set to 17 (UDP)

   o  IPv6 header values:

      *  DSCP: set to 0

      *  Hop Count: set to 255

      *  Protocol: Set as possible,
   performs address manipulation as needed, and provides some form of
   isolation (e.g., deterministic delay) to 17 (UDP)

   o  UDP header values:

      *  Checksum: avoid send-receive interface
   contention.  Some portion of the checksum MUST random and systematic error can be calculated
   characterized this way.

   When a measurement controller requests a calibration measurement, the
   loopback is applied and included in the
         header

   o  UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 of [RFC5357]

      *  Security features result is output in use influence the number of Padding
         octets.

      *  142 octets total, including the TWAMP same format

   Other measurement parameters:

   Tmax: as a loss threshold waiting time
   normal measurement with value 3.0, expressed in
      units of seconds, as additional indication that it is a positive value
   calibration result.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the *available accuracy* of type decimal64 with
      fraction digits = 4 (see section 9.3 the Output Metric Units.
   For example, repeated loopback delay measurements will reveal the
   portion of [RFC6020]) and with the Output result resolution of 0.0001 seconds (0.1 ms), with lossless conversion
      to/from which is the 32-bit NTP timestamp as per section 6 result of [RFC5905].

   See system
   noise, and thus inaccurate.

9.5.  Administrative items

9.5.1.  Status

   <current or deprecated>

9.5.2.  Requestor (keep?)

   name or RFC, etc.

9.5.3.  Revision

   1.0

9.5.4.  Revision Date

   YYYY-MM-DD

9.6.  Comments and Remarks

   Additional (Informational) details for this entry

10.  TCP Round-Trip Delay and Loss Registry Entries

   This section specifies three initial registry entries for the Packet Stream generation category Passive
   assessment of TCP Round-Trip Delay (RTD) and another entry for two additional Fixed
   Parameters.

8.3. TCP
   Round-trip Loss Count.

   This section specifies four Registry entries with many common
   columns.

   All column entries beside the ID, Name, Description, and Output
   Reference Method of Measurement categories are the same, thus this section proposes
   four closely-related registry entries.  As a result, IANA is also
   asked to assign four corresponding URNs and URLs to each Named
   Metric.

10.1.  Summary

   This category includes columns for references multiple indexes to the registry entry: the
   element ID and metric name.

10.1.1.  ID (Identifier)

   <insert a numeric identifier, an integer, TBD>

   IANA is asked to relevant sections assign different numeric identifiers to each of the RFC(s) and any supplemental information needed
   four Named Metrics.

10.1.2.  Name

   <insert name according to ensure an
   unambiguous methods for implementations.

8.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

   The methodology for this metric naming convention>

   RTDelay_Passive_IP-TCP_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is defined as Type-P-One-way-Delay-
   Poisson-Stream in section 3.6 of [RFC7679] and section 4.6 of
   [RFC7679] using one of:

   o  Mean

   o  Min

   o  Max

   RTLoss_Passive_IP-TCP_RFCXXXXsecY_Packet_Count

10.1.3.  URIs

   URN: Prefix urn:ietf:metrics:perf:<name>

   URL: http://<TBD by IANA>/<name>

10.1.4.  Description

   RTDelay: This metric assesses the Type-P and Tmax defined under Fixed Parameters.

   The reference method distinguishes between long-delayed packets and
   lost round-trip delay of TCP packets by implementing
   constituting a maximum waiting time for packet
   arrival.  Tmax single connection, exchanged between two hosts.  The
   Observation Point [RFC7011] is the waiting time used as the threshold assumed to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for in the OWLoss metric. network at a
   remote point from the end hosts.  The calculations on Output is the one-way Round-trip delay SHALL be performed on the
   conditional distribution, conditioned on successful packet arrival
   within Tmax.  Also, when
   for all packet delays are stored, the process
   which calculates the one-way delay value MAY enforce successfully exchanged packets expressed as the Tmax
   threshold on stored values before calculations.  See section 4.1 <statistic>
   of
   [RFC3393] for details on the their conditional distribution to exclude
   undefined values of delay, and Section 5 of [RFC6703] delay distribution, where <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   RTLoss: This metric assesses the estimated loss count for background
   on this analysis choice.

   The reference method requires some way to distinguish between
   different TCP packets in
   constituting a stream to establish correspondence single connection, exchanged between
   sending times and receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST two hosts.  The
   Observation Point [RFC7011] is assumed to be
   retained at in the Src or included with each packet to dis-ambiguate
   packet reordering if it occurs.

   Since network at a standard measurement protocol
   remote point from the end hosts.  The Output is employed [RFC5357], then the estimated Loss
   Count for the measurement process will determine interval.

10.1.5.  Change Controller

   IETF

10.1.6.  Version (of Registry Format)

   1.0

10.2.  Metric Definition

   This category includes columns to prompt the sequence numbers or timestamps
   applied entry of all necessary
   details related to test packets after the Fixed metric definition, including the RFC reference
   and Runtime parameters are
   passed values of input factors, called fixed parameters.

10.2.1.  Reference Definitions

   <Full bibliographic reference to an immutable doc.>

   Although there is no RFC that process.  The describes passive measurement protocol dictates the format of sequence numbers and time-stamps conveyed in Round-
   Trip Delay,

   @@@@ is this true??? Searches seem to say so.

   the TWAMP-Test packet
   payload.

8.3.2.  Packet Stream Generation

   <list of generation parameters parallel definition for Active measurement is:

   Almes, G., Kalidindi, S., and section/spec references M.  Zekauskas, "A Round-trip Delay
   Metric for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific section reference and additional clarifications, if needed>

   This section gives metric definition uses the details terms singleton and sample as defined
   in Section 11 of [RFC2330].  (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.)

   With the Observation Point [RFC7011] (OP) located between the packet traffic which is hosts
   participating in the
   basis for measurement.  In IPPM metrics, this is called TCP connection, the Stream, Round-trip Delay metric
   requires two individual measurements between the OP and can easily be described by providing each host,
   such that the list of stream
   parameters.

   Section 3 of [RFC3432] prescribes Spatial Composition [RFC6049]of the method for generating Periodic
   streams using associated parameters.

   incT measurements yields
   a Round-trip Delay singleton.

   Using the nominal duration direction of inter-packet interval, first bit TCP SYN transmission to
      first bit

   dT anchor the duration of
   nomenclature, host A sends the interval for allowed sample start times

   T0 SYN and host B replies with SYN-ACK
   during connection establishment.  The direction of SYN transfer is
   the actual start time Forward direction of transmission, from A through OP to B
   (Reverse is B through OP to A).

   Traffic filters reduce the periodic packet stream
   NOTE: an initiation process with at the OP to a number of control exchanges
   resulting Qualified
   bidirectional flow packets.

   In the definitions below, Corresponding Packets are transferred in unpredictable start times (within
   different directions and convey a time interval) common value in a TCP header field
   that establishes correspondence (to the extent possible).  Examples
   may be sufficient found in the TCP timestamp fields.

   @@@@ Note the first-bit last bit questions in the definitions below.

   For a real number, RTD_fwd, >> the Round-trip Delay in the Forward
   direction from OP to avoid synchronization host B at time T' is RTD_fwd << REQUIRES that OP
   observed (the first bit of periodic streams, and
   therefore a valid replacement for selecting ?) a start time Qualified packet to host B at random
   from wire-
   time T', that host B received that packet and sent a fixed interval.

   These stream parameters will be specified as Run-time parameters.

8.3.3.  Traffic Filtering (observation) Details

   NA

8.3.4.  Sampling Distribution

   NA

8.3.5.  Run-time Parameters Corresponding
   Packet back to host A, and Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the measurement system, and reported with OP observed (the last bit of ?) that
   packet at wire-time T' + RTD_fwd.

   For a real number, RTD_rev, >> the results
   for Round-trip Delay in the context Reverse
   direction from OP to be complete.

   <list host A at time T'' is RTD_rev << REQUIRES that
   OP observed (the first bit of run-time parameters, ?) a Qualified packet to host A at
   wire-time T'', that host A received that packet and their data formats>

   Src  the IP address sent a
   Corresponding Packet back to host B, and that OP observed (the last
   bit of ?) that packet at wire-time T'' + RTD_rev.

   Ideally, the packet sent from host B to host A in both definitions
   above SHOULD be 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 same packet (or, when measuring RTD_rev first,
   the packet from host A to host B in both definitions should be the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value
   same).

   The REQUIRED Composition Function for IPv6,
      see section 4 of [RFC6991])

   T0 a time, singleton of Round-trip Delay
   at time T (where T is the start earliest of a measurement interval, (format "date-and-
      time" as specified T' and T'' above) is:

   RTDelay = RTD_fwd + RTD_rev

   Note that when OP is located at host A or host B, one of the terms in Section 5.6
   RTDelay will be zero or negligible.

   The definition of [RFC3339], see also Round-trip Loss Count uses the nomenclature
   developed above, based on observation of the TCP header sequence
   numbers and storing the sequence number gaps observed.  Packet Losses
   can be inferred from:

   o  Out-of-order segments: TCP segments are normally monotonically
      increasing.  Section 3 of [RFC6991]).  The UTC Time Zone is required by Section 6.1 [RFC4737] describes the notion of
      [RFC2330].  When T0 is "all-zeros", "next
      expected" sequence numbers which can be adapted to TCP segments
      (for the purpose of detecting reordered packets).  Observation of
      out-of-order segments indicates loss on the path prior to the OP,
      and creates a start time is unspecified gap.

   o  Duplicate segments: Section 2 of [RFC5560] defines identical
      packets and Tf is suitable for evaluation of TCP packets to be interpreted as detect
      duplication.  Observation of duplicate segments *without a
      corresponding gap* indicates loss on the Duration path following the OP
      (because they overlap part of the delivered sequence numbers
      already observed at OP).

   Each observation of the an out-of-order or duplicate infers a singleton
   of loss, but composition of Round-trip Loss Counts will be conducted
   over a measurement
      interval.  The start time interval which is controlled through other means.

   Tf synonymous with a time, single TCP
   connection.

   With the end of above observations in the Forward direction over 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 the count of
      [RFC2330].  When T0 is "all-zeros", a end time date is ignored out-of-order and
      Tf duplicate
   segments is interpreted defined as RTL_fwd.  Comparable observations in the Duration of the
   Reverse direction are defined as RTL_rev.

   For a measurement interval.

   >>> should Periodic run-time params be fixed instead? probably yes if
   modeling interval (corresponding to a specific version single TCP
   connection), T0 to Tf, the REQUIRED Composition Function for a the
   two single-direction counts of tests.  Note inferred loss is:

   RTLoss = RTL_fwd + RTL_rev

10.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the NAME, i.e.
   Poisson3.3

8.3.6.  Roles

   <lists measurement system for use when
   needed>

   Traffic Filters:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  Protocol: Set to 06 (TCP)

   o  IPv6 header values:

      *  DSCP: set to 0
      *  Protocol: Set to 06 (TCP)

   o  TCP header values:

      *  Flags: ACK, SYN, others??

      *  Checksum: the names of checksum MUST be calculated and included in the different roles from
         header

      *  Timestamp Option (TSopt): Set

         +  Kind: 8

         +  Length: 10 bytes

   o

10.3.  Method of Measurement

   This category includes columns for references to relevant sections of
   the measurement method>

   Src  launches each packet RFC(s) and waits any supplemental information needed to ensure an
   unambiguous methods for return transmissions from
      Dst. This implementations.

10.3.1.  Reference Methods

   <for metric, insert relevant section references and supplemental
   info>

   The foundation methodology for this metric is defined in Section 4 of
   [RFC7323] using the TWAMP Session-Sender.

   Dst  waits for each packet Timestamp Option with modifications that allow
   application at a mid-path Observation Point (OP) [RFC7011].  Further
   details and applicable heuristics were derived from Src [Strowes] and sends
   [Trammell-14].

   The Traffic Filter at the OP is configured to observe a return packet single TCP
   connection.  When the SYN, SYN-ACK, ACK handshake occurs, it offers
   the first opportunity to Src.
      This is measure both RTD_fwd (on the TWAMP Session-Reflector.

8.4.  Output

   This category specifies all details of SYN to SYN-ACK
   pair) and RTD_rev (on the Output SYN-ACK to ACK pair).  Label this singleton
   of measurements RTDelay as RTDelay-SA (SYN-ACK = SA, composed using the metric.

8.4.1.  Type

   <insert name forward
   and reverse measurement pair).  RTDelay-SA SHOULD be treated
   separately from other RTDelays on data-bearing packets and their
   ACKs.  The RTDelay-SA value MAY be used as a sanity check on other
   Composed values of the output type, raw or RTDelay.

   @@@@ Should we add a selected summary statistic>

   See subsection titles in Data Format for Types.

8.4.2.  Reference Definition

   <describe the data format separate singleton metric for each type of result> RTDelay-SA ??
   (seems reasonable and useful, but no loss metric however)
   For all output types ---

   T0 payload bearing packets, the start OP measures the time interval
   between observation of a measurement interval, (format "date-and-time" as
      specified packet with Sequence Number s, and the
   corresponding ACK with same Sequence number.  When the payload is
   transferred from host A to host B, the observed interval is RTD_fwd.

   Because many data transfers are unidirectional (say, in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone the Forward
   direction from host A to host B), it is required by Section 6.1 necessary to use pure ACK
   packets with Timestamp (TSval) and their Timestamp value echo to
   perform a RTD_rev measurement.  The time interval between observation
   of
      [RFC2330].

   Tf the end of a measurement interval, (format "date-and-time" as
      specified ACK from B to A, and the corresponding packet with Timestamp
   echo (TSecr) is the RTD_rev.

   Delay Measurement Filtering Heuristics:

   If Data payloads were transferred in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC both Forward and Reverse
   directions, then the Round-Trip Time Zone is required by Measurement Rule in Section 6.1 4.1
   of
      [RFC2330].

   For LossRatio -- [RFC7323] could be applied.  This rule essentially excludes any
   measurement using a packet unless it makes progress in the count transfer
   (advances the left edge of lost packets the send window, consistent
   with[Strowes]).

   A different heuristic from [Trammell-14] is to total packets sent exclude any RTD_rev
   that is larger than previously observed values.  This would tend to
   exclude Reverse measurements taken when the basis for the loss ratio calculation as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one Application has no data
   ready to send, because considerable time could be added to RTD_rev
   from this source of the following sub-sections apply:

8.4.2.1.  Percentile95 error.

   The 95th percentile statistic calculations to summarize the delay (RTDelay) SHALL be calculated using
   performed on the conditional
   distribution of all packets with a finite value of One-way delay
   (undefined delays are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details distribution, conditioned on successful
   Forward and Reverse measurements which follow the conditional
   distribution to exclude undefined values of delay, Heuristics.

   Method for Inferring Loss:

   The OP tracks sequence numbers and Section 5 of
   [RFC6703] stores gaps for background on this analysis choice.

   See section 4.3 each direction of [RFC3393] for details
   transmission, as well as the next-expected sequence number as in
   [Trammell-14] and [RFC4737].  Loss is inferred from Out-of-order
   segments and Duplicate segments.

   Loss Measurement Filtering Heuristics:

   [Trammell-14] adds a window of evaluation based on the percentile statistic
   (where Round-trip delay should RTDelay.

   Spurious (unneeded) retransmissions (observed as duplicates) can also
   be substituted for "ipdv"). reduced this way, as described in [Trammell-14].

   Sources of Error:

   The percentile = 95, meaning principal source of RTDelay error is the host processing time to
   return a packet that defines the reported delay, "95Percentile", termination of a time interval.  The
   heuristics above intend to mitigate these errors by excluding
   measurements where host processing time is the smallest value a significant part of one-way delay for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95%
   RTD_fwd or RTD_rev.

   A key source of the singleton
   one-way delay values RTLoss error is observation loss, described in the conditional distribution.  See
   section
   11.3 of [RFC2330] for 3 of [Trammell-14].

10.3.2.  Packet Stream Generation

   This section gives the definition details of the percentile statistic
   using the EDF.

   95Percentile  The time value of packet traffic which is the result
   basis for measurement.  In IPPM metrics, this is expressed in units called the Stream,
   and can easily be described by providing the list of
      seconds, as stream
   parameters.

   NA

10.3.3.  Traffic Filtering (observation) Details

   The measured results based on a positive value of type decimal64 with fraction
      digits = 9 (see section 9.3 of [RFC6020]) with resolution filtered version of
      0.000000001 seconds (1.0 ns), and with lossless conversion to/from the 64-bit NTP timestamp as per packets
   observed, and this section 6 of RFC [RFC5905]

8.4.2.2.  Mean provides the filter details (when
   present).

   The mean SHALL be calculated using Fixed Parameters above give a portion of the conditional Traffic Filter.
   Other aspects will be supplied as Run-time Parameters (below).

10.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from the
   filter>

   This metric requires a complete sample of all packets with a finite value of One-way delay (undefined delays that qualify
   according to the Traffic Filter criteria.

10.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are excluded), a single value as follows:

   See section 4.1 of [RFC3393] input factors that must be determined,
   configured into the measurement system, and reported with the results
   for details on the conditional
   distribution context to exclude undefined values be complete.

   <list of delay, run-time parameters, and Section 5 their data formats>

   Src  the IP address of
   [RFC6703] the host in the host A Role (format ipv4-
      address-no-zone value for background on this analysis choice.

   See section 4.2.2 IPv4, or ipv6-address-no-zone value for
      IPv6, see Section 4 of [RFC6991])

   Dst  the IP address of [RFC6049] the host in the host B (format ipv4-address-
      no-zone value for details on calculating this
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time IPv4, or ipv6-address-no-zone value for IPv6,
      see section 4 of [RFC6991])

   T0 a time, the result is expressed in units start of seconds,
      as a positive value measurement interval, (format "date-and-
      time" as specified in Section 5.6 of type decimal64 with fraction digits = 9
      (see section 9.3 [RFC3339], see also Section 3
      of [RFC6020]) with resolution [RFC6991]).  The UTC Time Zone is required by Section 6.1 of 0.000000001
      seconds (1.0 ns),
      [RFC2330].  When T0 is "all-zeros", a start time is unspecified
      and with lossless conversion to/from the 64-bit
      NTP timestamp Td is to be interpreted as per section 6 the Duration of RFC [RFC5905]

8.4.2.3.  Min the measurement
      interval.  The minimum SHALL be calculated using start time is controlled through other means.

   Td Optionally, the conditional distribution of
   all packets with a finite value end of One-way delay (undefined delays
   are excluded), a single value measurement interval, (format "date-and-
      time" as follows:

   See section 4.1 of [RFC3393] for details on the conditional
   distribution to exclude undefined values of delay, and specified in Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 5.6 of [RFC6049] for details on calculating this
   statistic, and 4.3.3 [RFC3339], see also Section 3
      of [RFC6049].

   Min [RFC6991]), or the duration (see T0).  The time value UTC Time Zone is
      required by Section 6.1 of [RFC2330].  Alternatively, the result is expressed in units end of seconds,
      as a positive value
      the measurement interval MAY be controlled by the measured
      connection, where the second pair of FIN and ACK packets exchanged
      between host A and B effectively ends the interval.

   ...  ...

10.3.6.  Roles

   <lists the names of type decimal64 the different roles from the measurement method>

   host A  launches the SYN packet to open the connection, and
      synonymous with fraction digits = 9
      (see section 9.3 of [RFC6020]) an IP address.

   host B  replies with resolution of 0.000000001
      seconds (1.0 ns), the SYN-ACK packet to open the connection, and
      synonymous with lossless conversion to/from an IP address.

10.4.  Output

   This category specifies all details of the 64-bit
      NTP timestamp as per section 6 Output of RFC [RFC5905]

8.4.2.4.  Max

   The maximum SHALL be calculated measurements
   using the conditional distribution of
   all packets with a finite value metric.

10.4.1.  Type

   <insert name of One-way delay (undefined delays
   are excluded), the output type, raw or a single value as follows: selected summary statistic>

   See section 4.1 of [RFC3393] subsection titles in Reference Definition for details on RTDelay Types.

   For RTLoss -- the conditional
   distribution to exclude undefined values of delay, and Section 5 count of
   [RFC6703] lost packets.

10.4.2.  Reference Definition

   <describe the data format for background on this analysis choice.

   See section 4.3.2 each type of result>

   For all output types ---

   T0 the start of [RFC6049] for a closely related method for
   calculating this statistic, and 4.3.3 measurement interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC6049]. [RFC3339], see also Section 3 of
      [RFC6991]).  The formula UTC Time Zone is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value required by Section 6.1 of
      [RFC2330].

   Tf the result is expressed in units end of seconds,
      as a positive value 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 type decimal64 with fraction digits = 9
      (see section 9.3
      [RFC2330].  The end of [RFC6020]) with resolution the measurement interval MAY be controlled
      by the measured connection, where the second pair of 0.000000001
      seconds (1.0 ns), FIN and with lossless conversion to/from ACK
      packets exchanged between host A and B effectively ends the 64-bit
      NTP timestamp as per section 6
      interval.

   ...  ...

   For RTLoss -- the count of RFC [RFC5905]

8.4.2.5.  Std_Dev lost packets.

   For each <statistic>, one of the following sub-sections apply:

10.4.2.1.  Mean

   The Std_Dev mean SHALL be calculated using the conditional distribution of
   all packets with a finite value of One-way 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.3.2 4.2.2 of [RFC6049] for a closely related method for details on calculating this
   statistic, and 4.3.3 4.2.3 of [RFC6049].  The formula is
   the classic calculation for standard deviation of a population.

   Std_Dev

   Mean  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]

8.4.3.  Metric Units

   <insert units for the measured results, and the reference
   specification>.

   The <statistic> of One-way Delay is expressed in seconds.

10.4.2.2.  Min

   The One-way Loss Ratio is expressed as a percentage minimum SHALL be calculated using the conditional distribution of lost packets
   to total
   all packets sent.

8.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides with a means to quantify the
   systematic and random errors finite value of Round-trip delay (undefined delays
   are excluded), a time measurement.  In-situ
   calibration could be enabled with an internal loopback that includes
   as much of the measurement system as possible, performs address
   manipulation single value as needed, and provides some form of isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of the random and systematic error can be characterized
   this way.

   For one-way delay measurements, the error calibration must include an
   assessment of the internal clock synchronization with its external
   reference (this internal clock is supplying timestamps follows:

   See section 4.1 of [RFC3393] for
   measurement).  In practice, details on the time offsets conditional
   distribution to exclude undefined values of clocks at both the
   source delay, and destination are needed to estimate the systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus the random variation is not usually represented in the
   results).

   time_offset Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of [RFC6049] for details on calculating this
   statistic, and 4.3.3 of [RFC6049].

   Min  The time value of the result is expressed in units of seconds,
      as a signed 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]

   When

10.4.2.3.  Max

   The maximum SHALL be calculated using the conditional distribution of
   all packets with a measurement controller requests finite value of Round-trip delay (undefined delays
   are excluded), a calibration measurement, single value as follows:

   See section 4.1 of [RFC3393] for details on the
   loopback is applied conditional
   distribution to exclude undefined values of delay, and Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 of [RFC6049] for a closely related method for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value of the result is output expressed in the same format units of seconds,
      as a
   normal measurement with additional indication that it is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate positive value of time offset as an indicator type decimal64 with fraction digits = 9
      (see section 9.3 of
   the degree [RFC6020]) with resolution of synchronization.

   Both internal loopback calibration 0.000000001
      seconds (1.0 ns), and clock synchronization can be
   used to estimate with lossless conversion to/from the *available accuracy* 64-bit
      NTP timestamp as per section 6 of the Output RFC [RFC5905]

10.4.3.  Metric Units.
   For example, repeated loopback delay measurements will reveal Units

   <insert units for the
   portion of measured results, and the Output result resolution which reference
   specification>.

   The <statistic> of Round-trip Delay is the result expressed in seconds, where
   <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   The Round-trip Loss Count is expressed as a number of system
   noise, and thus inaccurate.

8.5. packets.

10.4.4.  Calibration

   Passive measurements at an OP could be calibrated against an active
   measurement (with loss emulation) at host A or B, where the active
   measurement represents the ground-truth.

10.5.  Administrative items

8.5.1.

10.5.1.  Status

   <current or depricated>

8.5.2. deprecated>

10.5.2.  Requestor (keep?)

   name or RFC, etc.

8.5.3.

10.5.3.  Revision

   1.0

8.5.4.

10.5.4.  Revision Date

   YYYY-MM-DD

8.6.

10.6.  Comments and Remarks

   Additional (Informational) details for this entry

9.

11.  ver08 BLANK Registry Entry

   This section gives an initial registry entry for ....

9.1.

11.1.  Summary

   This category includes multiple indexes to the registry entries, the
   element ID and metric name.

9.1.1.

11.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>

9.1.2.

11.1.2.  Name

   <insert name according to metric naming convention>

9.1.3.

11.1.3.  URIs

   URI: Prefix urn:ietf:metrics:perf:<name>

   URL:

9.1.4.

11.1.4.  Description

   TBD.

9.1.5.

11.1.5.  Reference

   <reference to the RFC of spec where the registry entry is defined>

9.1.6.

11.1.6.  Change Controller

   <org or person >

9.1.7.

11.1.7.  Version (of Registry Format)

   <currently 1.0>

9.2.

11.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.

9.2.1.

11.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   <specific section reference and additional clarifications, if needed>

9.2.2.

11.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the measurement system for use when
   needed>

9.3.

11.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.

9.3.1.

11.3.1.  Reference Method

   <for metric, insert relevant section references and supplemental
   info>

9.3.2.

11.3.2.  Packet Stream Generation

   <list of generation parameters and section/spec references if needed>

9.3.3.

11.3.3.  Traffic Filtering (observation) Details

   <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>.

9.3.4.

11.3.4.  Sampling Distribution

   <insert time distribution details, or how this is diff from the
   filter>

9.3.5.

11.3.5.  Run-time Parameters and Data Format

   <list of run-time parameters, and any reference(s)>.

9.3.6.

11.3.6.  Roles

   <lists the names of the different roles from the measurement method>

9.4.

11.4.  Output

   This category specifies all details of the Output of measurements
   using the metric.

9.4.1.

11.4.1.  Type

   <insert name of the output type, raw or a selected summary statistic>

9.4.2.

11.4.2.  Reference Definition

   <pointer to section/spec where output type/format is defined>

9.4.3.

11.4.3.  Metric Units

   <insert units for the measured results, and the reference
   specification>.

9.4.4.

11.4.4.  Calibration

   <describe the error calibration, a way to indicate that the results
   were collected in a calbration calibration mode of operation, and a way to
   report internal status metrics related to calibration, such as time
   offset>

9.5.

11.5.  Administrative items

9.5.1.

11.5.1.  Status

   <current or depricated>

9.5.2. deprecated>

11.5.2.  Requestor

   <name of individual or Internet Draft, etc.>

9.5.3.

11.5.3.  Revision

   1.0

9.5.4.

11.5.4.  Revision Date

   YYYY-MM-DD

9.6.

11.6.  Comments and Remarks

   Additional (Informational) details for this entry

10.

12.  Example RTCP-XR Registry Entry

   This section is MAY BE DELETED or adapted before submission.

   This section gives an example registry entry for the end-point metric
   described in RFC 7003 [RFC7003], for RTCP-XR Burst/Gap Discard Metric
   reporting.

10.1.

12.1.  Registry Indexes

   This category includes multiple indexes to the registry entries, the
   element ID and metric name.

10.1.1.

12.1.1.  Identifier

   An integer having enough digits to uniquely identify each entry in
   the Registry.

10.1.2.

12.1.2.  Name

   A metric naming convention is TBD.

10.1.3.

12.1.3.  URI

   Prefix urn:ietf:metrics:param:<name>

10.1.4.

12.1.4.  Status

   current

10.1.5.

12.1.5.  Requestor

   Alcelip Mornuley

10.1.6.

12.1.6.  Revision

   1.0

10.1.7.

12.1.7.  Revision Date

   2014-07-04

10.1.8.

12.1.8.  Description

   TBD.

10.1.9.

12.1.9.  Reference Specification(s)

   [RFC3611][RFC4566][RFC6776][RFC6792][RFC7003]

10.2.

12.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.  Section 3.2 of
   [RFC7003] provides the reference information for this category.

10.2.1.

12.2.1.  Reference Definition

   Packets Discarded in Bursts:

   The total number of packets discarded during discard bursts.  The
   measured value is unsigned value.  If the measured value exceeds
   0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over-
   range measurement.  If the measurement is unavailable, the value
   0xFFFFFF MUST be reported.

10.2.2.

12.2.2.  Fixed Parameters

   Fixed Parameters are input factors that must be determined and
   embedded in the measurement system for use when needed.  The values
   of these parameters is specified in the Registry.

   Threshold: 8 bits, set to value = 3 packets.

   The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of
   successive packets that must not be discarded prior to and following
   a discard packet in order for this discarded packet to be regarded as
   part of a gap.  Note that the Threshold is set in accordance with the
   Gmin calculation defined in Section 4.7.2 of [RFC3611].

   Interval Metric flag: 2 bits, set to value 11=Cumulative Duration

   This field is used to indicate whether the burst/gap discard metrics
   are Sampled, Interval, or Cumulative metrics [RFC6792]:

   I=10: Interval Duration - the reported value applies to the most
   recent measurement interval duration between successive metrics
   reports.

   I=11: Cumulative Duration - the reported value applies to the
   accumulation period characteristic of cumulative measurements.

   Senders MUST NOT use the values I=00 or I=01.

10.3.

12.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.  For the Burst/Gap Discard
   Metric, it appears that the only guidance on methods of measurement
   is in Section 3.0 of [RFC7003] and its supporting references.
   Relevant information is repeated below, although there appears to be
   no section titled "Method of Measurement" in [RFC7003].

10.3.1.

12.3.1.  Reference Method

   Metrics in this block report on burst/gap discard in the stream
   arriving at the RTP system.  Measurements of these metrics are made
   at the receiving end of the RTP stream.  Instances of this metrics
   block use the synchronization source (SSRC) to refer to the separate
   auxiliary Measurement Information Block [RFC6776], which describes
   measurement periods in use (see [RFC6776], Section 4.2).

   This metrics block relies on the measurement period in the
   Measurement Information Block indicating the span of the report.
   Senders MUST send this block in the same compound RTCP packet as the
   Measurement Information Block.  Receivers MUST verify that the
   measurement period is received in the same compound RTCP packet as
   this metrics block.  If not, this metrics block MUST be discarded.

10.3.2.

12.3.2.  Stream Type and Stream Parameters

   Since RTCP-XR Measurements are conducted on live RTP traffic, the
   complete description of the stream is contained in SDP messages that
   proceed the establishment of a compatible stream between two or more
   communicating hosts.  See Run-time Parameters, below.

10.3.3.

12.3.3.  Output Type and Data Format

   The output type defines the type of result that the metric produces.

   o  Value: Packets Discarded in Bursts

   o  Data Format: 24 bits

   o  Reference: Section 3.2 of [RFC7003]

10.3.4.

12.3.4.  Metric Units

   The measured results are apparently expressed in packets, although
   there is no section of [RFC7003] titled "Metric Units".

10.3.5.

12.3.5.  Run-time Parameters and Data Format

   Run-Time Parameters are input factors that must be determined,
   configured into the measurement system, and reported with the results
   for the context to be complete.  However, the values of these
   parameters is not specified in the Registry, rather these parameters
   are listed as an aid to the measurement system implementor or user
   (they must be left as variables, and supplied on execution).

   The Data Format of each Run-time Parameter SHALL be specified in this
   column, to simplify the control and implementation of measurement
   devices.

   SSRC of Source: 32 bits As defined in Section 4.1 of [RFC3611].

   SDP Parameters: As defined in [RFC4566]

   Session description v= (protocol version number, currently only 0)

   o= (originator and session identifier : username, id, version number,
   network address)

   s= (session name : mandatory with at least one UTF-8-encoded
   character)

   i=* (session title or short information) u=* (URI of description)

   e=* (zero or more email address with optional name of contacts)

   p=* (zero or more phone number with optional name of contacts)

   c=* (connection information--not required if included in all media)

   b=* (zero or more bandwidth information lines) One or more Time
   descriptions ("t=" and "r=" lines; see below)

   z=* (time zone adjustments)

   k=* (encryption key)

   a=* (zero or more session attribute lines)

   Zero or more Media descriptions (each one starting by an "m=" line;
   see below)

   m= (media name and transport address)

   i=* (media title or information field)
   c=* (connection information -- optional if included at session level)

   b=* (zero or more bandwidth information lines)

   k=* (encryption key)

   a=* (zero or more media attribute lines -- overriding the Session
   attribute lines)

   An example Run-time SDP description follows:

   v=0

   o=jdoe 2890844526 2890842807 IN IP4 192.0.2.5

   s=SDP Seminar i=A Seminar on the session description protocol

   u=http://www.example.com/seminars/sdp.pdf e=j.doe@example.com (Jane
   Doe)

   c=IN IP4 233.252.0.12/127

   t=2873397496 2873404696

   a=recvonly

   m=audio 49170 RTP/AVP 0

   m=video 51372 RTP/AVP 99

   a=rtpmap:99 h263-1998/90000

10.4.

12.4.  Comments and Remarks

   TBD.

11.

13.  Revision History

   This section may be removed for publication.  It contains partial overview
   information on updtes. updates.

   This draft replaced draft-mornuley-ippm-initial-registry.

   In version 02, Section 4 has been edited to reflect recent discussion
   on the ippm-list: * Removed the combination or "Raw" and left 95th
   percentile. * Hanging Indent on Run-time parameters (Fixed parameters
   use bullet lists and other indenting formats. * Payload format for
   measurement has been removed. * Explanation of Conditional delay
   distribution.

   Version 03 addressed Phil Eardley's comments and suggestions in
   sections 1-4. and resolved the definition of Percentiles.

   Version 04 * All section 4 parameters reference YANG types for
   alternate data formats. * Discussion has concluded that usecase(s)
   for machine parse-able registry columns are not needed.

12.

   Version 05 * Revised several Poisson streams to Periodic, sections 4
   & 5. * Addition of ICMP (ping) metrics in section 9. * First
   implementation of Passive TCP RTT metrics in section 10.

14.  Security Considerations

   These registry entries represent no known security implications for
   Internet Security.  Each referenced Metric contains a Security
   Considerations section.

13.

15.  IANA Considerations

   IANA is requested to populate The Performance Metric Registry defined
   in [I-D.ietf-ippm-metric-registry] with the values defined above.

   See the IANA Considerations section of
   [I-D.ietf-ippm-metric-registry] for additional requests and
   considerations.

14.

16.  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, for suggesting the Passive TCP RTD
   metric and supporting references, 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.  Thanks to Michelle Cotton
   for her early IANA review, and to Amanda Barber for answering
   questions related to the presentation of the registry and
   accessibility of the complete template via URL.

15.

17.  References

15.1.

17.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.

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
              November 1987, <http://www.rfc-editor.org/info/rfc1035>. <https://www.rfc-editor.org/info/rfc1035>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC2330]  Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
              "Framework for IP Performance Metrics", RFC 2330,
              DOI 10.17487/RFC2330, May 1998,
              <http://www.rfc-editor.org/info/rfc2330>.
              <https://www.rfc-editor.org/info/rfc2330>.

   [RFC2679]  Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
              Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,
              September 1999, <http://www.rfc-editor.org/info/rfc2679>. <https://www.rfc-editor.org/info/rfc2679>.

   [RFC2680]  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>.
              <https://www.rfc-editor.org/info/rfc2680>.

   [RFC2681]  Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
              Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
              September 1999, <http://www.rfc-editor.org/info/rfc2681>. <https://www.rfc-editor.org/info/rfc2681>.

   [RFC3339]  Klyne, G. and C. Newman, "Date and Time on the Internet:
              Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
              <http://www.rfc-editor.org/info/rfc3339>.
              <https://www.rfc-editor.org/info/rfc3339>.

   [RFC3393]  Demichelis, C. and P. Chimento, "IP Packet Delay Variation
              Metric for IP Performance Metrics (IPPM)", RFC 3393,
              DOI 10.17487/RFC3393, November 2002,
              <http://www.rfc-editor.org/info/rfc3393>.
              <https://www.rfc-editor.org/info/rfc3393>.

   [RFC3432]  Raisanen, V., Grotefeld, G., and A. Morton, "Network
              performance measurement with periodic streams", RFC 3432,
              DOI 10.17487/RFC3432, November 2002,
              <http://www.rfc-editor.org/info/rfc3432>.
              <https://www.rfc-editor.org/info/rfc3432>.

   [RFC4737]  Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,
              S., and J. Perser, "Packet Reordering Metrics", RFC 4737,
              DOI 10.17487/RFC4737, November 2006,
              <http://www.rfc-editor.org/info/rfc4737>.
              <https://www.rfc-editor.org/info/rfc4737>.

   [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,
              <http://www.rfc-editor.org/info/rfc5357>.
              <https://www.rfc-editor.org/info/rfc5357>.

   [RFC5560]  Uijterwaal, H., "A One-Way Packet Duplication Metric",
              RFC 5560, DOI 10.17487/RFC5560, May 2009,
              <https://www.rfc-editor.org/info/rfc5560>.

   [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,
              <http://www.rfc-editor.org/info/rfc5905>.
              <https://www.rfc-editor.org/info/rfc5905>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <http://www.rfc-editor.org/info/rfc6020>.
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6049]  Morton, A. and E. Stephan, "Spatial Composition of
              Metrics", RFC 6049, DOI 10.17487/RFC6049, January 2011,
              <http://www.rfc-editor.org/info/rfc6049>.
              <https://www.rfc-editor.org/info/rfc6049>.

   [RFC6673]  Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673,
              DOI 10.17487/RFC6673, August 2012,
              <http://www.rfc-editor.org/info/rfc6673>.
              <https://www.rfc-editor.org/info/rfc6673>.

   [RFC6991]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              RFC 6991, DOI 10.17487/RFC6991, July 2013,
              <http://www.rfc-editor.org/info/rfc6991>.
              <https://www.rfc-editor.org/info/rfc6991>.

   [RFC7011]  Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
              "Specification of the IP Flow Information Export (IPFIX)
              Protocol for the Exchange of Flow Information", STD 77,
              RFC 7011, DOI 10.17487/RFC7011, September 2013,
              <https://www.rfc-editor.org/info/rfc7011>.

   [RFC7323]  Borman, D., Braden, B., Jacobson, V., and R.
              Scheffenegger, Ed., "TCP Extensions for High Performance",
              RFC 7323, DOI 10.17487/RFC7323, September 2014,
              <https://www.rfc-editor.org/info/rfc7323>.

   [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, <http://www.rfc-editor.org/info/rfc7679>. <https://www.rfc-editor.org/info/rfc7679>.

   [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, <http://www.rfc-editor.org/info/rfc7680>.

15.2. <https://www.rfc-editor.org/info/rfc7680>.

17.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, <http://www.rfc-editor.org/info/rfc1242>. <https://www.rfc-editor.org/info/rfc1242>.

   [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,
              <http://www.rfc-editor.org/info/rfc3611>.
              <https://www.rfc-editor.org/info/rfc3611>.

   [RFC4148]  Stephan, E., "IP Performance Metrics (IPPM) Metrics
              Registry", BCP 108, RFC 4148, DOI 10.17487/RFC4148, August
              2005, <http://www.rfc-editor.org/info/rfc4148>. <https://www.rfc-editor.org/info/rfc4148>.

   [RFC4566]  Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
              Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
              July 2006, <http://www.rfc-editor.org/info/rfc4566>. <https://www.rfc-editor.org/info/rfc4566>.

   [RFC5472]  Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP
              Flow Information Export (IPFIX) Applicability", RFC 5472,
              DOI 10.17487/RFC5472, March 2009,
              <http://www.rfc-editor.org/info/rfc5472>.
              <https://www.rfc-editor.org/info/rfc5472>.

   [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,
              <http://www.rfc-editor.org/info/rfc5477>.
              <https://www.rfc-editor.org/info/rfc5477>.

   [RFC5481]  Morton, A. and B. Claise, "Packet Delay Variation
              Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
              March 2009, <http://www.rfc-editor.org/info/rfc5481>. <https://www.rfc-editor.org/info/rfc5481>.

   [RFC6248]  Morton, A., "RFC 4148 and the IP Performance Metrics
              (IPPM) Registry of Metrics Are Obsolete", RFC 6248,
              DOI 10.17487/RFC6248, April 2011,
              <http://www.rfc-editor.org/info/rfc6248>.
              <https://www.rfc-editor.org/info/rfc6248>.

   [RFC6390]  Clark, A. and B. Claise, "Guidelines for Considering New
              Performance Metric Development", BCP 170, RFC 6390,
              DOI 10.17487/RFC6390, October 2011,
              <http://www.rfc-editor.org/info/rfc6390>.
              <https://www.rfc-editor.org/info/rfc6390>.

   [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,
              <http://www.rfc-editor.org/info/rfc6703>.
              <https://www.rfc-editor.org/info/rfc6703>.

   [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,
              <http://www.rfc-editor.org/info/rfc6776>.
              <https://www.rfc-editor.org/info/rfc6776>.

   [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,
              <http://www.rfc-editor.org/info/rfc6792>.
              <https://www.rfc-editor.org/info/rfc6792>.

   [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, <http://www.rfc-editor.org/info/rfc7003>. <https://www.rfc-editor.org/info/rfc7003>.

   [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,
              <http://www.rfc-editor.org/info/rfc7594>.
              <https://www.rfc-editor.org/info/rfc7594>.

   [Strowes]  Strowes, S., "Passively Measuring TCP Round Trip Times",
              September 2013.

   [Trammell-14]
              Trammell, B., "Inline Data Integrity Signals for Passive
              Measurement", March 2014.

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/

   Marcelo Bagnulo
   Universidad Carlos III de Madrid
   Av. Universidad 30
   Leganes, Madrid  28911
   SPAIN

   Phone: 34 91 6249500
   Email: marcelo@it.uc3m.es
   URI:   http://www.it.uc3m.es

   Philip Eardley
   BT
   Adastral Park, Martlesham Heath
   Ipswich
   ENGLAND

   Email: philip.eardley@bt.com

   Kevin D'Souza
   AT&T Labs
   200 Laurel Avenue South
   Middletown,, NJ  07748
   USA

   Phone: +1 732 420 xxxx
   Email: kld@att.com