Network Working Group                                          A. Morton
Internet-Draft                                                 AT&T Labs
Intended status: Standards Track                              M. Bagnulo
Expires: April 25, June 10, 2019                                              UC3M
                                                              P. Eardley
                                                                      BT
                                                              K. D'Souza
                                                               AT&T Labs
                                                        October 22,
                                                        December 7, 2018

              Initial Performance Metric Registry Entries
                  draft-ietf-ippm-initial-registry-08
                  draft-ietf-ippm-initial-registry-09

Abstract

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

   * resolved open items on UDP one-way measurements. removed sections which only contained examples, or a blank outine
   for new metric entries.

   * resolved questions on DNS measurement method(s) removed remaining comments (did not require action).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14[RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 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 April 25, June 10, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   7   6
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   8   7
   3.  Registry Categories and Columns . . . . . . . . . . . . . . .   8   7
   4.  UDP Round-trip Latency and Loss Registry Entries  . . . . . .   9   8
     4.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  10   9
       4.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  10   9
       4.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  10   9
       4.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  10   9
       4.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  10   9
       4.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  10   9
       4.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  10   9
     4.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  11   9
       4.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  11  10
       4.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  12  10
     4.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  12  11
       4.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  13  11
       4.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  14  12
       4.3.3.  Traffic Filtering (observation) Details . . . . . . .  14  13
       4.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  15  13
       4.3.5.  Run-time Parameters and Data Format . . . . . . . . .  15  13
       4.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  15  14
     4.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  16  14
       4.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  16  14
       4.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  16  14
       4.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  17  15
       4.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  17  15
     4.5.  Administrative items  . . . . . . . . . . . . . . . . . .  18  16
       4.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  18  16
       4.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  18 . . . .  16
       4.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  18  16
       4.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  18  16

     4.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  18  16
   5.  Packet Delay Variation Registry Entry . . . . . . . . . . . .  18  16
     5.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  18  16
       5.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  18  16
       5.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  18  17
       5.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  19  17
       5.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  19  17
       5.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  19  17
       5.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  19  17
     5.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  19  17
       5.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  19  17
       5.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  20  18
     5.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  21  19
       5.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  21  19
       5.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  22  19
       5.3.3.  Traffic Filtering (observation) Details . . . . . . .  22  20
       5.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  23  20
       5.3.5.  Run-time Parameters and Data Format . . . . . . . . .  23  20
       5.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  23  21
     5.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  23  21
       5.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  24  21
       5.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  24  21
       5.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  24  22
       5.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  25  22
     5.5.  Administrative items  . . . . . . . . . . . . . . . . . .  25  23
       5.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  25  23
       5.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  26 . . . .  23
       5.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  26  23
       5.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  26  23
     5.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  26  23
   6.  DNS Response Latency and Loss Registry Entries  . . . . . . .  26  23
     6.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  26  23
       6.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  27  24
       6.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  27  24
       6.1.3.  URI . . . . . . . . . . . . . . . . . . . . . . . . .  27  24
       6.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  27  24
       6.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  27  24
       6.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  27  24
     6.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  27  24
       6.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  28  25
       6.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  28  25
     6.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  30  27
       6.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  30  27
       6.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  32  28
       6.3.3.  Traffic Filtering (observation) Details . . . . . . .  32  29
       6.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  32  29
       6.3.5.  Run-time Parameters and Data Format . . . . . . . . .  33  29
       6.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  34  30

     6.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  34  30
       6.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  34  31
       6.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  34  31
       6.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  35  31
       6.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  35  31
     6.5.  Administrative items  . . . . . . . . . . . . . . . . . .  35  32
       6.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  35  32
       6.5.2.  Requestor . . . . . . . . . . . . . . . . . . . . . .  36  32
       6.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  36  32
       6.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  36  32
     6.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  36  32
   7.  UDP Poisson One-way Delay and Loss Registry Entries . . . . .  36  32
     7.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  36  33
       7.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  36  33
       7.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  37  33
       7.1.3.  URI and URL . . . . . . . . . . . . . . . . . . . . .  37  33
       7.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  37  33
     7.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  38  34
       7.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  38  34
       7.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  39  35
     7.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  40  36
       7.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  40  36
       7.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  41  36
       7.3.3.  Traffic Filtering (observation) Details . . . . . . .  41  37
       7.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  42  37
       7.3.5.  Run-time Parameters and Data Format . . . . . . . . .  42  37
       7.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  42  38
     7.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  42  38
       7.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  43  38
       7.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  43  38
       7.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  46  41
       7.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  46  41
     7.5.  Administrative items  . . . . . . . . . . . . . . . . . .  47  42
       7.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  47  42
       7.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  47 . . . .  42
       7.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  47  42
       7.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  47  42
     7.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  47  42
   8.  UDP Periodic One-way Delay and Loss Registry Entries  . . . .  47  43
     8.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  47  43
       8.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  47  43
       8.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  48  43
       8.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  48  44
       8.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  48  44
     8.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  49  44
       8.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  49  44
       8.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  50  45
     8.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  51  46
       8.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  51  46
       8.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  52  47
       8.3.3.  Traffic Filtering (observation) Details . . . . . . .  52  48
       8.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  53  48
       8.3.5.  Run-time Parameters and Data Format . . . . . . . . .  53  48
       8.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  53  48
     8.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  53  48
       8.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  54  49
       8.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  54  49
       8.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  57  51
       8.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  57  52
     8.5.  Administrative items  . . . . . . . . . . . . . . . . . .  58  53
       8.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  58  53
       8.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  58 . . . .  53
       8.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  58  53
       8.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  58  53
     8.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  58  53
   9.  ICMP Round-trip Latency and Loss Registry Entries . . . . . .  58  53
     9.1.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  59  53
       9.1.1.  ID (Identifier) . . . . . . . . . . . . . . . . . . .  59  53
       9.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .  59  54
       9.1.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . .  59  54
       9.1.4.  Description . . . . . . . . . . . . . . . . . . . . .  59  54
       9.1.5.  Change Controller . . . . . . . . . . . . . . . . . .  60  54
       9.1.6.  Version (of Registry Format)  . . . . . . . . . . . .  60  54
     9.2.  Metric Definition . . . . . . . . . . . . . . . . . . . .  60  55
       9.2.1.  Reference Definition  . . . . . . . . . . . . . . . .  60  55
       9.2.2.  Fixed Parameters  . . . . . . . . . . . . . . . . . .  61  55
     9.3.  Method of Measurement . . . . . . . . . . . . . . . . . .  62  56
       9.3.1.  Reference Method  . . . . . . . . . . . . . . . . . .  62  56
       9.3.2.  Packet Stream Generation  . . . . . . . . . . . . . .  63  57
       9.3.3.  Traffic Filtering (observation) Details . . . . . . .  64  58
       9.3.4.  Sampling Distribution . . . . . . . . . . . . . . . .  64  58
       9.3.5.  Run-time Parameters and Data Format . . . . . . . . .  64  58
       9.3.6.  Roles . . . . . . . . . . . . . . . . . . . . . . . .  65  59
     9.4.  Output  . . . . . . . . . . . . . . . . . . . . . . . . .  65  59
       9.4.1.  Type  . . . . . . . . . . . . . . . . . . . . . . . .  65  59
       9.4.2.  Reference Definition  . . . . . . . . . . . . . . . .  65  59
       9.4.3.  Metric Units  . . . . . . . . . . . . . . . . . . . .  67  61
       9.4.4.  Calibration . . . . . . . . . . . . . . . . . . . . .  67  61
     9.5.  Administrative items  . . . . . . . . . . . . . . . . . .  68  62
       9.5.1.  Status  . . . . . . . . . . . . . . . . . . . . . . .  68  62
       9.5.2.  Requestor (keep?) . . . . . . . . . . . . . . . . . .  68 . . . .  62
       9.5.3.  Revision  . . . . . . . . . . . . . . . . . . . . . .  68  62
       9.5.4.  Revision Date . . . . . . . . . . . . . . . . . . . .  68  62
     9.6.  Comments and Remarks  . . . . . . . . . . . . . . . . . .  68  62
   10. TCP Round-Trip Delay and Loss Registry Entries  . . . . . . .  68  62
     10.1.  Summary  . . . . . . . . . . . . . . . . . . . . . . . .  68  63
       10.1.1.  ID (Identifier)  . . . . . . . . . . . . . . . . . .  69  63
       10.1.2.  Name . . . . . . . . . . . . . . . . . . . . . . . .  69  63
       10.1.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . .  69  63
       10.1.4.  Description  . . . . . . . . . . . . . . . . . . . .  69  63
       10.1.5.  Change Controller  . . . . . . . . . . . . . . . . .  70  64
       10.1.6.  Version (of Registry Format) . . . . . . . . . . . .  70  64
     10.2.  Metric Definition  . . . . . . . . . . . . . . . . . . .  70  64
       10.2.1.  Reference Definitions  . . . . . . . . . . . . . . .  70  64
       10.2.2.  Fixed Parameters . . . . . . . . . . . . . . . . . .  72  66
     10.3.  Method of Measurement  . . . . . . . . . . . . . . . . .  73  67
       10.3.1.  Reference Methods  . . . . . . . . . . . . . . . . .  73  67
       10.3.2.  Packet Stream Generation . . . . . . . . . . . . . .  75  69
       10.3.3.  Traffic Filtering (observation) Details  . . . . . .  75  69
       10.3.4.  Sampling Distribution  . . . . . . . . . . . . . . .  75  69
       10.3.5.  Run-time Parameters and Data Format  . . . . . . . .  75  69
       10.3.6.  Roles  . . . . . . . . . . . . . . . . . . . . . . .  76  70
     10.4.  Output . . . . . . . . . . . . . . . . . . . . . . . . .  76  70
       10.4.1.  Type . . . . . . . . . . . . . . . . . . . . . . . .  76  70
       10.4.2.  Reference Definition . . . . . . . . . . . . . . . .  77  70
       10.4.3.  Metric Units . . . . . . . . . . . . . . . . . . . .  79  72
       10.4.4.  Calibration  . . . . . . . . . . . . . . . . . . . .  79  73
     10.5.  Administrative items . . . . . . . . . . . . . . . . . .  79  73
       10.5.1.  Status . . . . . . . . . . . . . . . . . . . . . . .  79  73
       10.5.2.  Requestor (keep?)  . . . . . . . . . . . . . . . . .  79 . . . .  73
       10.5.3.  Revision . . . . . . . . . . . . . . . . . . . . . .  79  73
       10.5.4.  Revision Date  . . . . . . . . . . . . . . . . . . .  79  73
     10.6.  Comments and Remarks . . . . . . . . . . . . . . . . . .  79  73
   11. ver08 BLANK Registry Entry  . . . . . . . . . . . . . . . . .  80
     11.1.  Summary  . . . . . . . . . . . . . . . Security Considerations . . . . . . . . .  80
       11.1.1.  ID (Identifier) . . . . . . . . . .  73
   12. IANA Considerations . . . . . . . .  80
       11.1.2.  Name . . . . . . . . . . . . .  73
   13. Acknowledgements  . . . . . . . . . . .  80
       11.1.3.  URIs . . . . . . . . . . .  73
   14. References  . . . . . . . . . . . . .  80
       11.1.4.  Description . . . . . . . . . . . .  74
     14.1.  Normative References . . . . . . . .  80
       11.1.5.  Reference . . . . . . . . . .  74
     14.2.  Informative References . . . . . . . . . . .  80
       11.1.6.  Change Controller . . . . . .  76
   Authors' Addresses  . . . . . . . . . . .  80
       11.1.7.  Version (of Registry Format) . . . . . . . . . . . .  80
     11.2.  78

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 Definition  . . . . . . . . . . . . . . . . . . .  80
       11.2.1.  Reference Definition . . . . . . . . . . . . . . . .  81
       11.2.2.  Fixed Parameters . . . . . . . . . . . . . . . . . .  81
     11.3.  Method of Measurement  . . . . . . . . . . . . . . . . .  81
       11.3.1.  Reference Method . . . . . . . . . . . . . . . . . .  81
       11.3.2.  Packet Stream Generation . . . . . . . . . . . . . .  81
       11.3.3.  Traffic Filtering (observation) Details  . . . . . .  81
       11.3.4.  Sampling Distribution  . . . . . . . . . . . . . . .  81
       11.3.5.  Run-time Parameters and Data Format  . . . . . . . .  81
       11.3.6.  Roles  . . . . . . . . . . . . . . . . . . . . . . .  81
     11.4.  Output . . . . . . . . . . . . . . . . . . . . . . . . .  82
       11.4.1.  Type . . . . . . . . . . . . . . . . . . . . . . . .  82
       11.4.2.  Reference Definition . . . . . . . . . . . . . . . .  82
       11.4.3.  Metric Units . . . . . . . . . . . . . . . . . . . .  82
       11.4.4.  Calibration  . . . . . . . . . . . . . . . . . . . .  82
     11.5.  Administrative items . . . . . . . . . . . . . . . . . .  82
       11.5.1.  Status . . . . . . . . . . . . . . . . . . . . . . .  82
       11.5.2.  Requestor  . . . . . . . . . . . . . . . . . . . . .  82
       11.5.3.  Revision . . . . . . . . . . . . . . . . . . . . . .  82
       11.5.4.  Revision Date  . . . . . . . . . . . . . . . . . . .  82
     11.6.  Comments and Remarks . . . . . . . . . . . . . . . . . .  82
   12. Example RTCP-XR Registry Entry  . . . . . . . . . . . . . . .  83
     12.1.  Registry Indexes . . . . . . . . . . . . . . . . . . . .  83
       12.1.1.  Identifier . . . . . . . . . . . . . . . . . . . . .  83
       12.1.2.  Name . . . . . . . . . . . . . . . . . . . . . . . .  83
       12.1.3.  URI  . . . . . . . . . . . . . . . . . . . . . . . .  83
       12.1.4.  Status . . . . . . . . . . . . . . . . . . . . . . .  83
       12.1.5.  Requestor  . . . . . . . . . . . . . . . . . . . . .  83
       12.1.6.  Revision . . . . . . . . . . . . . . . . . . . . . .  83
       12.1.7.  Revision Date  . . . . . . . . . . . . . . . . . . .  83
       12.1.8.  Description  . . . . . . . . . . . . . . . . . . . .  83
       12.1.9.  Reference Specification(s) . . . . . . . . . . . . .  84
     12.2.  Metric Definition  . . . . . . . . . . . . . . . . . . .  84
       12.2.1.  Reference Definition . . . . . . . . . . . . . . . .  84
       12.2.2.  Fixed Parameters . . . . . . . . . . . . . . . . . .  84
     12.3.  Method of Measurement  . . . . . . . . . . . . . . . . .  85
       12.3.1.  Reference Method . . . . . . . . . . . . . . . . . .  85
       12.3.2.  Stream Type and Stream Parameters  . . . . . . . . .  85
       12.3.3.  Output Type and Data Format  . . . . . . . . . . . .  85
       12.3.4.  Metric Units . . . . . . . . . . . . . . . . . . . .  85
       12.3.5.  Run-time Parameters and Data Format  . . . . . . . .  86
     12.4.  Comments and Remarks . . . . . . . . . . . . . . . . . .  87
   13. Revision History  . . . . . . . . . . . . . . . . . . . . . .  87
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  88
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  88
   16. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  88
   17. References  . . . . . . . . . . . . . . . . . . . . . . . . .  89
     17.1.  Normative References . . . . . . . . . . . . . . . . . .  89
     17.2.  Informative References . . . . . . . . . . . . . . . . .  91
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  93

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 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 examining 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 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 for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
   Round-trip delay values in the conditional distribution.  See section
   11.3 of [RFC2330] for the definition of the percentile statistic
   using the EDF.

   LossRatio -- 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.4.2.  Reference Definition

   <describe the reference data format for 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 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].

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

   For

   RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio:

   Percentile  The numeric value of the result is expressed in units of
      lost packets to total packets times 100%, as a positive value of
      type decimal64 with fraction digits = 9 (see section 9.3 of
      [RFC6020]) with resolution of 0.0000000001.

4.4.3.  Metric Units

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

   The 95th Percentile of 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
   systematic and random errors of a 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 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 applied and the result is output in the same format as a
   normal measurement with additional indication that it is a
   calibration result.

   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.

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 and Remarks

   Additional (Informational) details for this entry

5.  Packet Delay Variation Registry Entry

   This section gives an initial registry entry for a Packet Delay
   Variation metric.

   Note: If each Registry entry should only produce a "raw" output or a
   statistical summary, then the "Output" Category can be split and this
   section can become two 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 reference and additional clarifications, if needed>
   See sections 2.4 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, this metric entry specifies
   the PDV form defined in section 4.2 of [RFC5481], where the singleton
   PDV for packet i is referred to by the variable name "PDV(i)".

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

   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 200 bytes

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value 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].

   F  a selection function unambiguously defining the packets from the
      stream selected for the metric.  See section 4.2 of [RFC5481] for
      the PDV form.

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

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

5.3.1.  Reference Method

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

   See section 2.6 and 3.6 of [RFC3393] for general singleton element
   calculations.  This metric entry requires implementation of the PDV
   form defined in section 4.2 of [RFC5481].  Also see measurement
   considerations in section 8 of [RFC5481].

   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.

   The calculations on the one-way delay 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 one-way delay 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.

5.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]) Registry.  It uses terms and with resolution of 0.0001 seconds
      (0.1 ms).

   dT the duration of definitions from the interval IPPM
   literature, primarily [RFC2330].

   Although there are several standard templates for allowed sample start times, with
      value 1.0, expressed in units of seconds, as a positive value organizing
   specifications of
      type decimal64 with fraction digits = 4 performance metrics (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: [RFC2679] for an initiation process with a number of control exchanges
   resulting in unpredictable start times (within a time interval) may
   be sufficient to avoid synchronization example
   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.

5.3.3.  Traffic Filtering (observation) Details

   <insert the measured results traditional IPPM template, based to large extent on a filtered version of the
   packets observed, and this section provides the filter details (when
   present), and section reference>.

   NA

5.3.4.  Sampling Distribution

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

   NA

5.3.5.  Run-time Parameters and Data Format

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

   Src  the IP address of the host
   Benchmarking Methodology Working Group's traditional template in the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
   [RFC1242], and see Section 4 [RFC6390] for a similar template), none of [RFC6991])

   Dst these
   templates were intended to become the IP address basis for the columns of an
   IETF-wide registry of metrics.  While examining aspects of metric
   specifications which need to be registered, it became clear that none
   of the host in existing metric templates fully satisfies the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see section 4 particular needs
   of [RFC6991])

   T0 a time, registry.

   Therefore, [I-D.ietf-ippm-metric-registry] defines the start of overall format
   for a measurement interval, (format "date-and-
      time" as specified in Performance Metric Registry.  Section 5.6 5 of [RFC3339], see
   [I-D.ietf-ippm-metric-registry] also Section 3 gives guidelines for those
   requesting registration of [RFC6991]).  The UTC Time Zone a Metric, that is required by Section 6.1 the creation of
      [RFC2330].  When T0 is "all-zeros", entry(s)
   in the Performance Metric Registry: "In essence, there needs to be
   evidence that a start time is unspecified candidate Registered Performance Metric has
   significant industry interest, or has seen deployment, and Tf there is to be interpreted as
   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 Duration IPPM working group of the measurement
      interval.  The start time is controlled through other means.

   Tf a time,
   IETF, according to their framework [RFC2330] and its updates.

3.  Registry Categories and Columns

   This section provides the end categories and columns of the registry, for
   easy reference.  An entry (row) therefore gives 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 complete
   description of
      [RFC2330].  When T0 is "all-zeros", a end time date is ignored Registered Metric.

 Registry Categories and
      Tf is interpreted Columns, shown as the Duration of the measurement interval.

5.3.6.  Roles

   <lists the names
                                            Category
                                            ------------------
                                            Column |  Column |

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

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

Method of the different roles from the measurement method>

   Src  launches each packet to Dst.

   Dst  waits for each packet from Src.

5.4. 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 category section specifies all details of the Output of measurements
   using the metric.

5.4.1.  Type

   <insert name of 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 type, raw or a selected summary statistic>

   Percentile -- for
   statistical summary.  To describe both "raw" and one or more
   statistics efficiently, the conditional distribution of all packets with a
   valid value of one-way delay (undefined delays are excluded), Identifier, Name, and Output Categories
   can be split and a single value corresponding to the 95th percentile, as follows:

   See section 4.1 of [RFC3393] can specify two or more closely-
   related metrics.  This section specifies two Registry entries with
   many common columns.  See Section 7 for details on an example specifying
   multiple Registry entries with many common columns.

   All column entries beside the conditional
   distribution to exclude undefined values of delay, ID, Name, Description, and Section 5 of
   [RFC6703] for background on this analysis choice.

   The percentile = 95, meaning that Output
   Reference Method categories are the reported delay, "95Percentile", 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 smallest value of one-way PDV for which registry entry: the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95%
   element ID and metric name.

4.1.1.  ID (Identifier)

   IANA is asked to assign different numeric identifiers to each of the singleton
   one-way PDV values in
   two Named Metrics.

4.1.2.  Name

   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 conditional distribution.  See section 11.3 delay of [RFC2330] for a stream of packets
   exchanged between two hosts (which are the definition of two measurement points),
   and the percentile statistic using Output is the
   EDF.

5.4.2.  Reference Definition

   <the output type and data format Round-trip delay for each type all successfully exchanged
   packets expressed as the 95th percentile of result>

   T0 their conditional delay
   distribution.

   RTLoss: This metric assesses the start loss ratio 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 stream of
      [RFC2330].

   Tf packets
   exchanged between two hosts (which are the end of a two 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].

   95Percentile  The time value of points),
   and the result Output is the Round-trip loss ratio for all successfully
   exchanged packets 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 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 64-bit NTP timestamp as per section 6 entry of all necessary
   details related to the metric definition, including the RFC [RFC5905]

5.4.3. reference
   and values of input factors, called fixed parameters.

4.2.1.  Reference Definition

   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay
   Metric Units

   <insert units for IPPM", RFC 2681, September 1999.

   [RFC2681]

   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 measured results, 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 reference
   specification>.

   The 95th Percentile [RFC2681] definition of one-way PDV "Round-trip-Delay
   between Src and Dst" is expressed directionally ambiguous in seconds.

5.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means the text, this
   metric tightens the definition further to quantify recognize that the
   systematic host in
   the "Src" role will send the first packet to "Dst", and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback ultimately
   receive the corresponding return packet from "Dst" (when neither are
   lost).

   Finally, note 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) variable "dT" is used in [RFC2681] to refer to avoid send-receive interface contention.
   Some portion of
   the random value of Round-trip delay in metric definitions and systematic error can methods.  The
   variable "dT" has been re-used in other IPPM literature to refer to
   different quantities, and cannot be characterized
   this way.

   For one-way used as a global variable name.

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

   [RFC6673]

   Both delay measurements, and loss metrics employ a maximum waiting time for
   received packets, so the error calibration must include an
   assessment count of the internal clock synchronization with its external
   reference (this internal clock lost packets to total packets sent
   is supplying timestamps the basis for
   measurement).  In practice, the time offsets loss ratio calculation as per Section 6.1 of
   [RFC6673].

4.2.2.  Fixed Parameters

   Type-P as defined in Section 13 of clocks at both the
   source and destination are needed [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to estimate the systematic error
   due 0

      *  TTL: set to imperfect clock synchronization (the time offsets are
   smoothed, thus 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 variation is not usually represented checksum MUST be calculated and included in the
   results).

   time_offset  The time value
         header

   o  UDP Payload

      *  total of the result is 100 bytes

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time

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

4.3.  Method of Measurement

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

4.3.1.  Reference Method

   The methodology for this metric is output 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 same format as 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
   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 the 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 RTLoss metric.

   The calculations on the Output Metric Units.
   For example, repeated loopback delay measurements will reveal (RTT) 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 RTT value MAY enforce the Tmax threshold on
   stored values before calculations.  See section 4.1 of system
   noise, and thus inaccurate.

5.5.  Administrative items

5.5.1.  Status

   <current or deprecated>

5.5.2.  Requestor (keep?)

   <name [RFC3393] for
   details on the conditional distribution to exclude undefined values
   of individual or RFC, etc.>

5.5.3.  Revision

   1.0

5.5.4.  Revision Date

   YYYY-MM-DD

5.6.  Comments delay, and Remarks

   <Additional (Informational) details Section 5 of [RFC6703] for background on this entry>

   Lost analysis
   choice.

   The reference method requires some way to distinguish between
   different packets represent in a challenge stream to establish correspondence between
   sending times and receiving times for delay variation metrics.  See
   section 4.1 of [RFC3393] 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 delay variation applicability
   statement[RFC5481] for extensive analysis
   format of sequence numbers and comparison time-stamps, if they are conveyed in
   the packet payload.

   Refer to Section 4.4 of PDV and
   an alternate metric, IPDV.

6.  DNS Response Latency and Loss Registry Entries

   @@@@ comment from Brian: there is an interesting method [RFC6673] for DNS
   measurement by encoding information in expanded discussion of the query itself.  It is
   instruction to "send a
   question of what exactly we are trying Type-P packet back to measure: specific RR, or the infrastructure itself. (at 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 time we measure a specific RR). metric.

4.3.2.  Packet Stream Generation

   This section gives initial registry entries the details of the packet traffic which is the
   basis for DNS Response Latency measurement.  In IPPM metrics, this is called the Stream,
   and Loss from a network user's perspective, for a specific named
   resource.  The metric can easily be measured repeatedly using different
   names.  RFC 2681 [RFC2681] defines a Round-trip delay metric.  We
   build on that metric described by specifying several providing the list of stream
   parameters.

   Section 3 of [RFC3432] prescribes the input parameters to
   precisely define two metrics method for measuring DNS latency and loss.

   Note generating Periodic
   streams using associated parameters.

   incT  the nominal duration of inter-packet interval, first bit to IANA: Each Registry "Name" below specifies a single registry
   entry, whose output format varies
      first bit, with value 0.0200, expressed in accordance units of seconds, as a
      positive value of type decimal64 with the name.

   All column entries beside the ID, Name, Description, fraction digits = 4 (see
      section 9.3 of [RFC6020]) and Output
   Reference Method categories are with resolution of 0.0001 seconds
      (0.1 ms).

   dT the same, thus this section proposes
   two closely-related registry entries.  As duration of the interval for allowed sample start times, with
      value 1.0, expressed in units of seconds, as a result, IANA is also
   asked to assign corresponding URNs positive value of
      type decimal64 with fraction digits = 4 (see section 9.3 of
      [RFC6020]) and URLs to each Named Metric.

6.1.  Summary

   This category includes multiple indexes to with resolution of 0.0001 seconds (0.1 ms).

   T0 the registry entries, actual start time of the
   element ID and metric name.

   <skipping some admin columns>

6.1.1.  ID (Identifier)

   <insert numeric identifier, periodic stream, (format "date-and-
      time" as specified in Section 5.6 of [RFC3339], see also Section 3
      of [RFC6991]).

   NOTE: an integer>

   IANA is asked to assign different numeric identifiers to each initiation process with a number of the
   two Named Metrics.

6.1.2.  Name

   <insert name according control exchanges
   resulting in unpredictable start times (within a time interval) may
   be sufficient 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 IANA>/<name>

6.1.4.  Description

   This is avoid synchronization of periodic streams, and
   therefore a metric valid replacement for DNS Response performance from selecting a network user's
   perspective, for start time at random
   from a specific named resource. fixed interval.

   The metric can T0 parameter will be reported as a measured repeatedly using different resource names.

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

   NA

4.3.4.  Sampling Distribution

   NA

4.3.5.  Run-time Parameters and Data Format

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

   Src  the response.

   RLDNS: This metric indicates that the response was deemed lost.  In
   other words, IP address of the response time exceeded host 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 to prompt 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 entry IP address of all necessary
   details related to the metric definition, including host in the RFC reference
   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
   Metric Dst Role (format ipv4-address-
      no-zone value for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific IPv4, or ipv6-address-no-zone value for IPv6,
      see section reference and additional clarifications, if needed>

   Section 2.4 4 of [RFC2681] provides [RFC6991])

   T0 a time, the reference definition start of the
   singleton (single value) Round-trip delay metric. a measurement interval, (format "date-and-
      time" as specified in Section 3.4 5.6 of
   [RFC2681] provides the reference definition expanded [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 cover be interpreted as the Duration of the measurement
      interval.  The start time is controlled through other means.

   Tf a
   multi-singleton sample.  Note that terms such time, the end of a 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 and Resolver take
   the role UTC Time Zone is required by Section 6.1 of "Src",
      [RFC2330].  When T0 is "all-zeros", a end time date is ignored and
      Tf is interpreted as the Foreign Name Server takes the role Duration of
   "Dst".

   Note that although the [RFC2681] definition of "Round-trip-Delay
   between measurement interval.

4.3.6.  Roles

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

   Dst at T" is directionally ambiguous in  waits for each packet from Src and sends a return packet to Src.

4.4.  Output

   This category specifies all details of the text,
   this metric tightens Output of measurements
   using the definition further to recognize that metric.

4.4.1.  Type

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

   See section 4.1 of [RFC3393] for details on the first packet conditional
   distribution to "Dst", exclude undefined values of delay, and
   ultimately receive Section 5 of
   [RFC6703] for background on this analysis choice.

   The percentile = 95, meaning that the 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 reported delay, "95Percentile",
   is the smallest value of Round-trip delay for
   received responses, so which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
   Round-trip delay values in the conditional distribution.  See section
   11.3 of [RFC2330] for the definition of the percentile statistic
   using the EDF.

   LossRatio -- the count of lost packets to total packets sent is the
   basis for the loss determination ratio calculation as per Section 4.3 6.1 of [RFC6673].

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

      *  Source port: 53

      *  Destination port: 53

      *  Checksum: the checksum must be calculated and 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 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 Fully Qualified Domain Name (FQDN) provided as
            input for

4.4.2.  Reference Definition

   For all outputs ---

   T0 the test, 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 Run-time column

         +  QTYPE: the query type provided end of a measurement interval, (format "date-and-time" as input for the test,
      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  the Run-time column

         +  QCLASS: set count of packets sent by the Src to 1 for IN

      *  The other sections do not contain any Resource Records.

   Other Dst during the
      measurement parameters:

   o  Tmax: a loss threshold waiting interval.

   For

   RTDelay_Active_IP-UDP-Periodic_RFCXXXXsecY_Seconds_95Percentile:

   95Percentile  The 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), with
         lossless conversion to/from the 32-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 (1.0 ns), and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is with lossless conversion to/from
      the waiting time used 64-bit NTP timestamp as

   For

   RTLoss_Active_IP-UDP-Periodic_RFCXXXXsecY_Percent_LossRatio:

   Percentile  The numeric value of the threshold result is expressed in units of
      lost packets to declare a
   response packet lost.  Lost total packets SHALL be designated times 100%, as having
   undefined delay and counted for the RLDNS 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 a positive value MAY enforce the Tmax threshold on
   stored values before calculations.  See of
      type decimal64 with fraction digits = 9 (see section 4.1 9.3 of [RFC3393] for
   details on the conditional distribution to exclude undefined values
      [RFC6020]) with resolution of delay, and Section 5 0.0000000001.

4.4.3.  Metric Units

   The 95th Percentile of [RFC6703] for background on this analysis
   choice. Round-trip Delay is expressed in seconds.

   The reference method requires some way Round-trip Loss Ratio is expressed as a percentage of lost
   packets to distinguish between
   different total packets in sent.

4.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a stream means to establish correspondence between
   sending times quantify the
   systematic and receiving times for each successfully-arriving
   reply.

   DNS Messages bearing Queries provide for random ID Numbers in errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback at the
   Identification header field, so more than one query may Source
   host 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 launched
   while
   characterized this way.

   When a previous request is outstanding when measurement controller requests a calibration measurement, the ID Number
   loopback is used.
   Therefore, applied and the ID Number MUST be retained at result is output in the Src or included same format as a
   normal measurement with
   each response packet to disambiguate packet reordering if additional indication that it occurs.

   IF a DNS response does not arrive within Tmax, the response time
   RTDNS is undefined, a
   calibration result.

   Both internal loopback calibration and RLDNS = 1.  The Message ID SHALL clock synchronization can be
   used to
   disambiguate estimate the successive queries that are otherwise identical.

   Since *available accuracy* of the ID Number filed is only 16 bits in length, it places a
   limit on Output Metric Units.
   For example, repeated loopback delay measurements will reveal the number of simultaneous outstanding DNS queries during a
   stress test from a single Src address.

   Refer to Section 4.4 of [RFC6673] for expanded discussion
   portion of the
   instruction to "send a Type-P packet back to Output result resolution which is the Src as quickly as
   possible" in Section 2.6 result of system
   noise, and thus inaccurate.

4.5.  Administrative items

4.5.1.  Status

   Current

4.5.2.  Requestor

   This RFC 2681 [RFC2681].  However, the DNS
   Server is expected to perform all required functions to prepare numner

4.5.3.  Revision

   1.0

4.5.4.  Revision Date

   YYYY-MM-DD

4.6.  Comments and
   send Remarks

   None.

5.  Packet Delay Variation Registry Entry

   This section gives an initial registry entry for a response, so the response time will include processing time
   and network delay.  Section 8 of [RFC6673] presents additional
   requirements which SHALL be included in Packet Delay
   Variation metric.

   Note: If each Registry entry should only produce a "raw" output or a
   statistical summary, then the method of measurement for "Output" Category can be split and this metric.

   In addition
   section can become two closely-related metrics.

5.1.  Summary

   This category includes multiple indexes to operations described in [RFC2681], the Src MUST parse registry entries, the DNS headers
   element ID and metric name.

5.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>

5.1.2.  Name

   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 reply minimum
   delay observed on the periodic stream, and prepare the information for
   subsequent reporting Output is expressed as a measured result, along with the Round-Trip
   Delay.

6.3.2.  Packet Stream Generation

   This section gives
   the details 95th percentile of the packet traffic which is delay variation distribution.

5.1.5.  Change Controller

   IETF

5.1.6.  Version (of Registry Format)

   1.0

5.2.  Metric Definition

   This category includes columns to prompt the
   basis for measurement.  In IPPM metrics, this is called entry of all necessary
   details related to the Stream,
   and can easily be described by providing metric definition, including the list RFC reference
   and values of stream input factors, called fixed parameters.

   <list of generation parameters

5.2.1.  Reference Definition

   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 section/spec references if needed>

   Section 11.1.3 of Algorithms Specification", RFC 2681 [RFC2330] provides three methods to
   generate Poisson sampling intervals.  The reciprocal 5905,
   June 2010.[RFC5905]

   See sections 2.4 and 3.4 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 start time (Run-time Parameter), the
   subsequent send times [RFC3393].  Singleton delay differences
   measured are all computed prior referred to measurement by
   computing the pseudo-random distribution variable name "ddT" (applicable to
   all forms of inter-packet send times,
   (truncating delay variation).  However, this metric entry specifies
   the distribution as specified PDV form defined in section 4.2 of [RFC5481], where the Run-time
   Parameters), and the Src sends each singleton
   PDV for packet at the computed times.

   Note that Trunc i is referred to by the upper limit on inter-packet times variable name "PDV(i)".

5.2.2.  Fixed Parameters

   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
   Poisson distribution.  A random
         header

   o  UDP Payload

      *  total of 200 bytes

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value greater than Trunc is set equal
   to Trunc instead.

6.3.3.  Traffic Filtering (observation) Details

   The measured results based on 3.0, expressed in
      units of seconds, as a filtered version 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 packets
   observed, and this 32-bit NTP timestamp as per section provides 6 of [RFC5905].

   F  a selection function unambiguously defining the filter details (when
   present).

   <section reference>.

   NA

6.3.4.  Sampling Distribution

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

   NA

6.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
      stream selected for the results metric.  See section 4.2 of [RFC5481] for
      the context PDV form.

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

5.3.  Method of Measurement

   This category includes columns for references to be complete.

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

   Src
   the IP address RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations.

5.3.1.  Reference Method

   See section 2.6 and 3.6 of [RFC3393] for general singleton element
   calculations.  This metric entry requires implementation of the host PDV
   form defined in the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6, section 4.2 of [RFC5481].  Also see Section 4 measurement
   considerations in section 8 of [RFC6991])

   Dst [RFC5481].

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

   The calculations on the one-way delay 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 Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone one-way delay value for IPv6,
      see MAY enforce the Tmax
   threshold on stored values before calculations.  See section 4 4.1 of [RFC6991])

   T0 a time,
   [RFC3393] for details on the start of a measurement interval, (format "date-and-
      time" as specified in Section 5.6 conditional distribution to exclude
   undefined values of [RFC3339], see also delay, and Section 3 5 of [RFC6991]). [RFC6703] for background
   on this analysis choice.

   The UTC Time Zone is required by Section 6.1 of
      [RFC2330].  When T0 is "all-zeros", reference method requires some way to distinguish between
   different packets in a start time is unspecified
      and Tf is stream to establish correspondence between
   sending times and receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be interpreted as
   retained at the Duration of Src or included with each packet to disambiguate
   packet reordering if it occurs.

   If a standard measurement protocol is employed, then the measurement
      interval.
   process will determine the sequence numbers or timestamps applied to
   test packets after the Fixed and Runtime parameters are passed to
   that process.  The start time is controlled through other means.

   Tf a time, chosen measurement protocol will dictate the end
   format of a measurement interval, (format "date-and-time"
      as specified sequence numbers and time-stamps, if they are conveyed in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1
   the packet payload.

5.3.2.  Packet Stream Generation

   This section gives the details of
      [RFC2330].  When T0 the packet traffic which is "all-zeros", a end time date the
   basis for measurement.  In IPPM metrics, this is ignored called the Stream,
   and
      Tf is interpreted as can easily be described by providing the Duration list of stream
   parameters.

   Section 3 of [RFC3432] prescribes the measurement interval.

   Reciprocal_lambda  average packet interval method for Poisson Streams 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), and with lossless
      conversion to/from ms).

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

   Trunc  Upper limit on Poisson distribution 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), and with lossless conversion to/from ms).

   T0 the
      32-bit NTP timestamp as per section 6 actual start time 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 periodic stream, (format "date-and-
      time" as specified in successive queries, Section 5.6 of [RFC3339], see also Section 4.1.1 3
      of [RFC1035].  This identifier is copied into the
      corresponding reply and can [RFC6991]).

   NOTE: an initiation process with a number of control exchanges
   resulting in unpredictable start times (within a time interval) may
   be used by the requester (Src) to
      match-up replies sufficient to outstanding queries.

   QNAME avoid synchronization of periodic streams, and
   therefore a valid replacement for selecting a start time at random
   from a fixed interval.

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

5.3.3.  Traffic Filtering (observation) Details

   NA

5.3.4.  Sampling Distribution

   NA

5.3.5.  Run-time Parameters and Data Format

   Src  the IP address of the Query, formatted as specified host in
      section the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see Section 4 of [RFC6991].

   QTYPE  The Query Type, which will correspond to [RFC6991])

   Dst  the IP address family of the query (decimal 1 host in the Dst Role (format ipv4-address-
      no-zone value for IPv4 IPv4, or 28 ipv6-address-no-zone value for IPv6, formatted as
      see section 4 of [RFC6991])

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

6.3.6.  Roles

   <lists [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 names Duration of the different roles from measurement
      interval.  The start time is controlled through other means.

   Tf a time, the end of a measurement method>

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

   Dst  waits for each packet from Src and sends 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 return packet to Src.

6.4. end time date is ignored and
      Tf is interpreted as the Duration of the measurement interval.

5.3.6.  Roles

5.4.  Output

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

5.4.1.  Type

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

   See section 4.1 of [RFC3393] for details on the conditional
   distribution to exclude undefined values of measurements
   using the metric.

6.4.1.  Type

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

   The percentile = 95, meaning that the output type, raw or a selected summary statistic>

   Raw -- reported delay, "95Percentile",
   is the smallest value of one-way PDV for each DNS Query packet sent, sets which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
   one-way PDV values as defined in the next column, including conditional distribution.  See section 11.3
   of [RFC2330] for the status definition of the response, only assigning
   delay values to successful query-response pairs.

6.4.2. percentile statistic using the
   EDF.

5.4.2.  Reference Definition

   <describe

   T0 the data format for each type start of result>

   For all outputs:

   T  the time the DNS Query was sent during a measurement interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 of
      [RFC2330].

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

   dT

   95Percentile  The time value of the round-trip delay to receive the DNS
      response, 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].  This value is 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, ns), and with lossless conversion to/from
      the reference
   specification>.

   RTDNS: Round-trip Delay, dT, 64-bit NTP timestamp as per section 6 of RFC [RFC5905]

5.4.3.  Metric Units

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

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

6.4.4.

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

   When a measurement controller requests a calibration measurement, the
   loopback is applied and the result is output in 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 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.

6.5.

5.5.  Administrative items

6.5.1.

5.5.1.  Status

   <current or deprecated>

6.5.2.

   Current

5.5.2.  Requestor

   name or RFC, etc.

6.5.3.

   This RFC number

5.5.3.  Revision

   1.0

6.5.4.

5.5.4.  Revision Date

   YYYY-MM-DD

6.6.

5.6.  Comments and Remarks

   Additional (Informational) details

   Lost packets represent a challenge for this entry

7.  UDP Poisson One-way Delay delay variation metrics.  See
   section 4.1 of [RFC3393] and the delay variation applicability
   statement[RFC5481] for extensive analysis and comparison of PDV and
   an alternate metric, IPDV.

6.  DNS Response Latency and Loss Registry Entries

   This section specifies five gives initial registry entries for the UDP
   Poisson One-way Delay, DNS Response Latency
   and one Loss from a network user's perspective, for UDP Poisson One-way Loss.

   IANA Note: a specific named
   resource.  The metric can be measured repeatedly using different
   names.  RFC 2681 [RFC2681] defines a Round-trip delay metric.  We
   build on that metric by specifying several of the 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 according to the <statistic> element of
   the name that specifies one form of statistical summary.  There is an
   additional metric name for in accordance with the Loss metric. name.

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

7.1.

6.1.  Summary

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

7.1.1.

6.1.1.  ID (Identifier)

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

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

7.1.2.

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

   RTDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Seconds_Raw

   RLDNS_Active_IP-UDP-Poisson_RFCXXXXsecY_Logical_Raw

6.1.3.  URI and URL

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

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

7.1.4. http://<TBD by IANA>/<name>

6.1.4.  Description

   OWDelay:

   This is a metric assesses the delay of for DNS Response performance from a stream of packets
   exchanged between two hosts (or measurement points), and reports the
   <statistic> One-way delay network user's
   perspective, 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: a specific named resource.  The metric can be
   measured repeatedly using different resource names.

   RTDNS: This metric assesses the loss ratio of a stream of packets
   exchanged between two hosts (which are response time, the interval from the
   query transmission to the response.

   RLDNS: This metric indicates that the two measurement points),
   and response was deemed lost.  In
   other words, the Output is response time exceeded the One-way loss ratio for all successfully
   received packets expressed as a percentage.

7.2. 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 prompt the entry of all necessary
   details related to the metric definition, including the RFC reference
   and values of input factors, called fixed parameters.

7.2.1.

6.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   For Delay:

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

   [RFC1035]

   Almes, G., Kalidindi, S., Zekauskas, M., and A.  Morton, Ed., M.  Zekauskas, "A One-
   Way Round-trip Delay
   Metric 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 of Metrics", IPPM", RFC
   6049, January 2011.

   [RFC6049]

   <specific section reference and additional clarifications, if needed> 2681, September 1999.

   [RFC2681]

   Section 3.4 2.4 of [RFC7679] [RFC2681] provides the reference definition of the
   singleton (single value) One-way Round-trip delay metric.  Section 4.4 3.4 of
   [RFC7679]
   [RFC2681] provides the reference definition expanded to cover a
   multi-value
   multi-singleton sample.  Note that terms such as singleton and sample
   are defined in Section 11 of [RFC2330].

   Only successful packet transfers

   For DNS Response Latency, the entities in [RFC1035] must be mapped to
   [RFC2681].  The Local Host with finite delay are included its User Program and Resolver take
   the role of "Src", and the Foreign Name Server takes the role of
   "Dst".

   Note that although the [RFC2681] definition of "Round-trip-Delay
   between Src and Dst at T" is directionally ambiguous in the sample, as prescribed text,
   this metric tightens the definition further to recognize that the
   host in section 4.1.2 of [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., the "Src" role will send the first packet to "Dst", and A.
   ultimately receive the corresponding return packet from "Dst" (when
   neither are lost).

   Morton, Ed., "A One-
   Way Loss Metric for IP Performance Metrics (IPPM)", A., "Round-trip Packet Loss Metrics", RFC 7680, DOI
   10.17487/RFC7680, January 2016, <http://www.rfc-editor.org/info/
   rfc7680>.

   Section 2.4 of [RFC7680] provides 6673, August 2012.

   [RFC6673]

   Both response time and loss metrics employ a maximum waiting time for
   received responses, so the reference definition count of lost packets to total packets
   sent is the basis for the
   singleton (single value) one-way loss metric. determination as per Section 3.4 4.3 of
   [RFC7680] provides the reference definition expanded to cover a
   multi-singleton sample.  Note that terms such
   [RFC6673].

6.2.2.  Fixed Parameters

   Type-P as singleton and sample
   are defined in Section 11 13 of [RFC2330].

7.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: [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to 0

      *  TTL:  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 must be calculated and included in the
         header

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

      *  Security features The payload contains a DNS message as defined in use influence RFC 1035
      [RFC1035] with the number of Padding
         octets. following values:

      *  250 octets total, including  The DNS header section 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 Fully Qualified Domain Name (FQDN) provided as
            input for the test, see the Run-time column

         +  QTYPE: the query type provided as input for the TWAMP format test, see
            the Run-time column

         +  QCLASS: set to 1 for IN

      *  The other sections do not contain any Resource Records.

   Other measurement parameters:

   o  Tmax: a loss threshold waiting time with value 3.0, (and to help disambiguate
      queries)

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

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

7.3.

   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.

7.3.1.

6.3.1.  Reference Method

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

   The methodology for this metric is defined as Type-P-One-way-Delay-
   Poisson-Stream Type-P-Round-trip-
   Delay-Poisson-Stream in section 3.6 2.6 of [RFC7679] RFC 2681 [RFC2681] and section 4.6
   3.6 of
   [RFC7679] RFC 2681 [RFC2681] using the Type-P and Tmax 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
   response packet lost.  Lost packets SHALL be designated as having
   undefined
   delay, delay and counted for the OWLoss RLDNS metric.

   The calculations on the one-way 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 one-way delay 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
   reply.

   DNS Messages bearing Queries provide 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.
   Therefore, the ID Number MUST be retained at the Src or included with
   each response packet to disambiguate packet reordering if it occurs.

   IF a DNS response does not arrive within Tmax, the response time
   RTDNS is undefined, and RLDNS = 1.  The Message ID SHALL be used to
   disambiguate the successive queries that are otherwise identical.

   Since the ID Number filed is only 16 bits in length, it places a
   limit on the number of simultaneous outstanding DNS queries during a
   stress test from a single Src address.

   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].  However, the DNS
   Server is expected to perform all required functions to disambiguate
   packet reordering if it occurs.

   Since prepare and
   send a standard measurement protocol is employed [RFC5357], then response, so the
   measurement process response time will determine include processing time
   and network delay.  Section 8 of [RFC6673] presents additional
   requirements which SHALL be included in the sequence numbers or timestamps
   applied method of measurement for
   this metric.

   In addition to test packets after operations described in [RFC2681], the Fixed and Runtime parameters are
   passed to that process.  The measurement protocol dictates Src MUST parse
   the format DNS headers of sequence numbers the reply and time-stamps conveyed in prepare the TWAMP-Test packet
   payload.

7.3.2. information for
   subsequent reporting as a measured result, along with the Round-Trip
   Delay.

6.3.2.  Packet Stream Generation

   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.

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

   Section 11.1.3 of RFC 2681 [RFC2330] provides three methods to
   generate Poisson sampling intervals.  The reciprocal of lambda is the
   average packet spacing, rate, thus the Run-time Parameter is Reciprocal_lambda
   = 1/lambda, in seconds.

   Method 3 SHALL be is used, where given a start time (Run-time Parameter), the
   subsequent send times are all computed prior to measurement by
   computing the pseudo-random distribution of inter-
   packet inter-packet send times,
   (truncating the distribution as specified in the
   Parameter Trunc), and the Src sends each packet at the computed
   times.

   Note that Trunc is the upper limit on inter-packet times in the
   Poisson distribution.  A random value greater than Trunc 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 (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), Run-time
   Parameters), and with lossless conversion to/from the
      32-bit NTP timestamp as per section 6 of [RFC5905] (values above
      this Src sends each packet at the computed times.

   Note that Trunc is the upper limit will be clipped and on inter-packet times in the
   Poisson distribution.  A random value greater than Trunc is set equal
   to the limit value). Trunc =
      30.0000 seconds.

7.3.3. instead.

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

   NA

7.3.4.

6.3.4.  Sampling Distribution

   NA

7.3.5.

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

7.3.6.  Roles

   <lists the names 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].

   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 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 Query, formatted as specified in
      section 4 of [RFC6991].

   QTYPE  The Query Type, which will correspond to the different roles from IP address family
      of the measurement method> query (decimal 1 for IPv4 or 28 for IPv6, formatted as a
      uint16, as per section 9.2 of [RFC6020].

6.3.6.  Roles

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

   Dst  waits for each packet from Src and sends a return packet to Src.
      This is the TWAMP Session-Reflector.

7.4.

6.4.  Output

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

7.4.1.

6.4.1.  Type

   <insert name

   Raw -- for each DNS Query packet sent, sets of values as defined in
   the output type, raw or a selected summary statistic>

   See subsection titles below for Types.

7.4.2. next column, including the status of the response, only assigning
   delay values to successful query-response pairs.

6.4.2.  Reference Definition

   <describe

   For all outputs:

   T  the data format for each time the DNS Query was sent during the 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].

   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 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].  This value is 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 measurement interval, (format "date-and-time" uint64 as specified in Section 5.6 of [RFC3339], see also Section 3 section 9.2 of
      [RFC6991]).  The UTC Time Zone [RFC6020].
      Non-zero values convey errors in the response, and such replies
      must be analyzed separately from successful requests.

6.4.3.  Metric Units

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

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

6.4.4.  Calibration

   Section 6.1 3.7.3 of
      [RFC2330].

   Tf [RFC7679] provides a means to quantify the end
   systematic and random errors of a measurement interval, (format "date-and-time" time measurement.  In-situ
   calibration could be enabled with an internal loopback at the Source
   host that includes as
      specified in Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is required by Section 6.1 much of
      [RFC2330].

   For LossRatio -- the count measurement system as possible,
   performs address and payload manipulation as needed, and provides
   some form of lost packets isolation (e.g., deterministic delay) to total packets sent 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 applied and the basis for result is output in the loss ratio calculation same format as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one a
   normal measurement with additional indication that it is a
   calibration result.

   Both internal loopback calibration and clock synchronization can be
   used to estimate the *available accuracy* of the following sub-sections apply:

7.4.2.1.  Percentile95

   The 95th percentile SHALL be calculated using Output Metric Units.
   For example, repeated loopback delay measurements will reveal the conditional
   distribution
   portion of all packets with a finite value the Output result resolution which is the result of system
   noise, and thus inaccurate.

6.5.  Administrative items

6.5.1.  Status

   Current

6.5.2.  Requestor

   This RFC number

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
   (undefined delays are excluded), a single value as follows:

   See Delay and Loss Registry Entries

   This section 4.1 of [RFC3393] specifies five initial registry entries for details on the conditional
   distribution 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 exclude undefined values the <statistic> element of delay, and Section 5
   the name that specifies one form of
   [RFC6703] statistical summary.  There is an
   additional metric name for background on the Loss metric.

   All column entries beside the ID, Name, Description, and Output
   Reference Method categories are the same, thus this analysis choice.

   See section 4.3 of [RFC3393] for details on 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 percentile statistic
   (where Round-trip delay should be substituted for "ipdv").

   The percentile = 95, meaning that registry entries, the reported delay, "95Percentile",
   element ID and metric name.

7.1.1.  ID (Identifier)

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

7.1.2.  Name

   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 smallest value of one-way delay for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of a stream of packets
   exchanged between two hosts (or measurement points), and reports the singleton
   one-way
   <statistic> One-way delay values in the for all successfully exchanged packets
   based on their conditional delay distribution.  See section
   11.3 of [RFC2330] for

   where <statistic> is one of:

   o  95Percentile

   o  Mean
   o  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses the definition loss ratio of the percentile statistic
   using the EDF.

   95Percentile  The time value a stream of packets
   exchanged between two hosts (which are the result two measurement points),
   and the Output is the One-way loss ratio for all successfully
   received packets expressed in units of
      seconds, as a positive value of type decimal64 with fraction
      digits = 9 (see section 9.3 of [RFC6020]) with resolution percentage.

7.2.  Metric Definition

   This category includes columns to prompt the entry of
      0.000000001 seconds (1.0 ns), and with lossless conversion to/from all necessary
   details related to the 64-bit NTP timestamp as per section 6 metric definition, including the RFC reference
   and values of input factors, called fixed parameters.

7.2.1.  Reference Definition

   For Delay:

   Almes, G., Kalidindi, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC [RFC5905]

7.4.2.2.  Mean

   The mean SHALL be calculated using the conditional distribution
   7679, DOI 10.17487/RFC7679, January 2016, <http://www.rfc-
   editor.org/info/rfc7679>.

   [RFC7679]

   Morton, A., and Stephan, E., "Spatial Composition of
   all packets with a finite value Metrics", RFC
   6049, January 2011.

   [RFC6049]

   Section 3.4 of [RFC7679] provides the reference definition of the
   singleton (single value) One-way delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 metric.  Section 4.4 of [RFC3393] for details on
   [RFC7679] provides the conditional
   distribution reference definition expanded to exclude undefined values of delay, cover a
   multi-value sample.  Note that terms such as singleton and sample are
   defined in Section 5 11 of
   [RFC6703] for background on this analysis choice.

   See [RFC2330].

   Only successful packet transfers with finite delay are included in
   the sample, as prescribed in section 4.2.2 of [RFC6049] for details on calculating this
   statistic, and 4.2.3 4.1.2 of [RFC6049].

   Mean  The time value

   For loss:

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

   Section 2.4 of [RFC7680] provides the result is expressed in units of seconds,
      as a positive value of type decimal64 with fraction digits = 9
      (see section 9.3 reference definition of [RFC6020]) with resolution the
   singleton (single value) one-way loss metric.  Section 3.4 of 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from
   [RFC7680] provides the 64-bit
      NTP timestamp reference definition expanded to cover a
   multi-singleton sample.  Note that terms such as per section 6 singleton and sample
   are defined in Section 11 of RFC [RFC5905]

7.4.2.3.  Min

   The minimum SHALL [RFC2330].

7.2.2.  Fixed Parameters

   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 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 included in the
         header

   o  UDP Payload: TWAMP Test Packet Formats, Section 5 of
   [RFC6703] for background on this analysis choice.

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

      *  Security features in use influence the number of [RFC6049].

   Min  The Padding
         octets.

      *  250 octets total, including the TWAMP format

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with 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 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 follows: [RFC5905].

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

   See section 4.3.2 two additional Fixed
   Parameters.

7.3.  Method of [RFC6049] for a closely related method Measurement

   This category includes columns for
   calculating this statistic, and 4.3.3 references to relevant sections of [RFC6049].  The formula is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n]
   the RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for all n

   Max implementations.

7.3.1.  Reference Method

   The time value of the result methodology for this metric is expressed in units of seconds, defined as a positive value of type decimal64 with fraction digits = 9
      (see Type-P-One-way-Delay-
   Poisson-Stream in section 9.3 3.6 of [RFC6020]) with resolution [RFC7679] and section 4.6 of 0.000000001
      seconds (1.0 ns),
   [RFC7679] using the Type-P and with lossless conversion to/from Tmax 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 64-bit
      NTP timestamp waiting time used as per section 6 of RFC [RFC5905]

7.4.2.5.  Std_Dev the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and counted for the OWLoss metric.

   The Std_Dev calculations on the one-way delay SHALL be calculated using 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 one-way delay 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 of [RFC6049] for a closely related

   The reference method for
   calculating this statistic, requires some way to distinguish between
   different packets in a stream to establish correspondence between
   sending times and 4.3.3 of [RFC6049].  The formula 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.

   Since a standard measurement protocol is employed [RFC5357], then the
   measurement process will determine the classic calculation for standard deviation of a population.

   Std_Dev sequence numbers or timestamps
   applied to test packets after the Fixed and Runtime parameters are
   passed to that process.  The time value of measurement protocol dictates 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 format
   of
      0.000000001 seconds (1.0 ns), sequence numbers and with lossless conversion to/from time-stamps conveyed in the 64-bit NTP timestamp as per TWAMP-Test packet
   payload.

7.3.2.  Packet Stream Generation

   This section 6 gives the details of RFC [RFC5905]

7.4.3.  Metric Units

   <insert units the packet traffic which is the
   basis for measurement.  In IPPM metrics, this is called the measured results, Stream,
   and can easily be described by providing the reference
   specification>.

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

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

7.4.4.  Calibration stream
   parameters.

   Section 3.7.3 11.1.3 of [RFC7679] RFC 2681 [RFC2330] provides a means three methods 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
   generate Poisson sampling intervals.  The reciprocal of lambda is 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
   average packet spacing, thus the random and systematic error can Run-time Parameter is
   Reciprocal_lambda = 1/lambda, in seconds.

   Method 3 SHALL be characterized
   this way.

   For one-way delay measurements, used, where given a start time (Run-time
   Parameter), the error calibration must include an
   assessment subsequent send times are all computed prior to
   measurement by computing the pseudo-random distribution of inter-
   packet send times, (truncating the internal clock synchronization with its external
   reference (this internal clock is supplying timestamps for
   measurement).  In practice, distribution as specified in the time offsets of clocks
   Parameter Trunc), and the Src sends each packet at both the
   source and destination are needed to estimate computed
   times.

   Note that Trunc is the systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus upper limit on inter-packet times in the
   Poisson distribution.  A random variation value greater than Trunc is not usually represented set equal
   to Trunc instead.

   Reciprocal_lambda  average packet interval for Poisson Streams
      expressed in the
   results).

   time_offset  The time 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 result is 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 signed positive value of type decimal64 with fraction
      digits = 9 4 (see section 9.3 of [RFC6020]) with resolution of 0.000000001
      0.0001 seconds (1.0 ns), (0.1 ms), and 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, the
   loopback is applied (values above
      this limit will be clipped and set to the result is output in the same format as a
   normal measurement with additional indication 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 it is a
   calibration result.  In any measurement, must be determined,
   configured into the measurement function
   SHOULD report its current estimate of time offset as an indicator of
   the degree of synchronization.

   Both internal loopback calibration system, and clock synchronization can be
   used reported with the results
   for the context to estimate be complete.

   Src  the *available accuracy* IP address of the Output Metric Units.
   For example, repeated loopback delay measurements will reveal host in the
   portion 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 Output result resolution which is the result IP address of system
   noise, and thus inaccurate.

7.5.  Administrative items

7.5.1.  Status

   <current or deprecated>

7.5.2.  Requestor (keep?)

   name the host in the Dst Role (format ipv4-address-
      no-zone value for IPv4, 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 ipv6-address-no-zone value for this entry

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

   This IPv6,
      see 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 4 of [RFC6991])

   T0 a single registry entry,
   whose output format varies according to time, the <statistic> element start of
   the name that specifies one form a measurement interval, (format "date-and-
      time" as specified in Section 5.6 of statistical summary.  There [RFC3339], see also Section 3
      of [RFC6991]).  The UTC Time Zone is an
   additional metric name for the Loss metric.

   All column entries beside the ID, Name, Description, and Output
   Reference Method categories are the same, thus this section proposes
   six closely-related registry entries.  As required by Section 6.1 of
      [RFC2330].  When T0 is "all-zeros", a result, IANA start time is also
   asked to assign corresponding URNs and URLs to each Named Metric.

8.1.  Summary

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

8.1.1.  ID (Identifier)

   <insert numeric identifier, an integer, one corresponding to each
   name below>
   IANA Tf is asked to assign a different numeric identifiers to each be interpreted as the Duration of the six Metrics.

8.1.2.  Name

   <insert name according to metric naming convention>

   OWDelay_Active_IP-UDP-Periodic20m-
   Payload142B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> measurement
      interval.  The start time 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 controlled through other means.

   Tf a time, the delay end of a stream of packets
   exchanged between two hosts (or measurement points), 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 reports the
   <statistic> One-way delay for all successfully exchanged packets
   based on their conditional delay distribution.

   where <statistic>
      Tf is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max
   o  StdDev

   OWLoss: This metric assesses interpreted as the loss ratio Duration of a stream the measurement interval.

7.3.6.  Roles

   <lists the names of packets
   exchanged between two hosts (which are the two different roles from the measurement points), method>

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

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

8.2.  Metric Definition TWAMP Session-Reflector.

7.4.  Output

   This category includes columns to prompt the entry of specifies all necessary details related to the metric definition, including of the RFC reference
   and values Output of input factors, called fixed parameters.

8.2.1. measurements
   using the metric.

7.4.1.  Type

   See subsection titles below for Types.

7.4.2.  Reference Definition

   <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 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 all output types ---

   T0 the start of Metrics", RFC
   6049, January 2011.

   [RFC6049]

   <specific section reference and additional clarifications, if needed> a measurement interval, (format "date-and-time" as
      specified in Section 3.4 5.6 of [RFC7679] provides the reference definition [RFC3339], see also Section 3 of the
   singleton (single value) One-way delay metric.
      [RFC6991]).  The UTC Time Zone is required by Section 4.4 6.1 of
   [RFC7679] provides
      [RFC2330].

   Tf the reference definition expanded to cover end of a
   multi-value sample.  Note that terms such measurement interval, (format "date-and-time" as singleton and sample are
   defined
      specified in Section 11 5.6 of [RFC3339], see also Section 3 of

      [RFC6991]).  The UTC Time Zone is required by Section 6.1 of
      [RFC2330].

   Only successful packet transfers

   For LossRatio -- the count of lost packets to total packets sent is
   the basis for the loss ratio calculation as per Section 4.1 of
   [RFC7680].

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

7.4.2.1.  Percentile95

   The 95th percentile SHALL be calculated using the conditional
   distribution of all packets with a finite value of One-way delay
   (undefined delays are included in
   the sample, excluded), a single value as prescribed in follows:

   See section 4.1.2 4.1 of [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Loss Metric [RFC3393] 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 reference definition of the
   singleton (single value) one-way loss metric.  Section 3.4 of
   [RFC7680] provides details on the reference definition expanded conditional
   distribution to cover a
   multi-singleton sample.  Note that terms such as singleton exclude undefined values of delay, and sample
   are defined in Section 11 5 of [RFC2330].

8.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded in the measurement system
   [RFC6703] 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: background on this analysis choice.

   See section 4.3 of [RFC3393] for details on the checksum MUST percentile statistic
   (where Round-trip delay should be calculated and included in substituted for "ipdv").

   The percentile = 95, meaning that the
         header

   o  UDP Payload: TWAMP Test Packet Formats, Section 4.1.2 reported delay, "95Percentile",
   is the smallest value of [RFC5357]

      *  Security features one-way delay for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of the singleton
   one-way delay values in use influence the number conditional distribution.  See section
   11.3 of [RFC2330] for the definition of Padding
         octets.

      *  142 octets total, including the TWAMP format (if used)

   Other measurement parameters:

   Tmax:  a loss threshold waiting percentile statistic
   using the EDF.

   95Percentile  The time with value 3.0, 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].

   See RFC [RFC5905]

7.4.2.2.  Mean

   The mean SHALL be calculated using the Packet Stream generation category for two additional Fixed
   Parameters.

8.3.  Method conditional distribution of Measurement

   This category includes columns for references to relevant sections
   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 RFC(s) and any supplemental information needed conditional
   distribution to ensure an
   unambiguous methods for implementations.

8.3.1.  Reference Method

   <for metric, insert relevant section references exclude undefined values of delay, and supplemental
   info>

   The methodology Section 5 of
   [RFC6703] for background on this metric is defined as Type-P-One-way-Delay-
   Poisson-Stream in analysis choice.

   See section 3.6 4.2.2 of [RFC7679] [RFC6049] for details on calculating this
   statistic, and section 4.6 4.2.3 of
   [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
   However, a Periodic stream is used, as defined in [RFC3432]. [RFC6049].

   Mean  The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is value of the waiting time used result is expressed in units of seconds,
      as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, 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 counted for with lossless conversion to/from the OWLoss metric. 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

7.4.2.3.  Min

   The calculations on the one-way delay minimum 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 one-way delay 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
   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 Runtime parameters are
   passed to that process.  The measurement protocol dictates the format
   of sequence numbers and 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>

   This

   See section gives the details 4.3.2 of the packet traffic which is the
   basis [RFC6049] for measurement.  In IPPM metrics, details on calculating 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
   statistic, and 4.3.3 of [RFC6049].

   Min  The time value 0.0200 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].

   dT RFC [RFC5905]

7.4.2.4.  Max

   The maximum SHALL be calculated using the duration 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 interval conditional
   distribution to exclude undefined values of delay, and Section 5 of
   [RFC6703] for allowed sample start times, with 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 1.0000, 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].

   T0 the actual start time of the periodic stream, determined from T0
      and dT.

   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.

   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 and Data Format

   Run-time Parameters are input factors that must 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 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 5 of the host in the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value
   [RFC6703] for IPv6,
      see background on this analysis choice.

   See section 4 of [RFC6991])

   T0 a time, the start 4.3.2 of [RFC6049] for a measurement interval, (format "date-and-
      time" as specified in Section 5.6 of [RFC3339], see also Section 3 closely related method for
   calculating this statistic, and 4.3.3 of [RFC6991]). [RFC6049].  The UTC Time Zone formula is required by Section 6.1
   the classic calculation for standard deviation of
      [RFC2330].  When T0 is "all-zeros", a start population.

   Std_Dev  The time is unspecified
      and Tf is to be interpreted as the Duration value of the measurement
      interval.  The start time result is controlled through other means.

   Tf a time, the end expressed in units of
      seconds, as a measurement interval, (format "date-and-time" 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 specified in Section 5.6 per section 6 of [RFC3339], see also Section 3 RFC [RFC5905]

7.4.3.  Metric Units

   The <statistic> of
      [RFC6991]). One-way Delay is expressed in seconds.

   The UTC Time Zone One-way Loss Ratio is required by expressed as a percentage of lost packets
   to total packets sent.

7.4.4.  Calibration

   Section 6.1 3.7.3 of
      [RFC2330].  When T0 is "all-zeros", [RFC7679] provides a end time date is ignored and
      Tf is interpreted as means to quantify the Duration
   systematic and random errors of the measurement interval.

8.3.6.  Roles

   <lists the names a time measurement.  In-situ
   calibration could be enabled with an internal loopback that includes
   as much of the different roles from the measurement method>

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

   Dst  waits for each packet from Src system as possible, performs address
   manipulation as needed, and sends a return packet provides some form of isolation (e.g.,
   deterministic delay) to Src.
      This is the TWAMP Session-Reflector.

8.4.  Output

   This category specifies all details avoid send-receive interface contention.
   Some portion of the Output of measurements
   using random and systematic error can be characterized
   this way.

   For one-way delay measurements, the metric.

8.4.1.  Type

   <insert name error calibration must include an
   assessment of the output type, raw or a selected summary statistic>

   See subsection titles in Reference Definition internal clock synchronization with its external
   reference (this internal clock is supplying timestamps for Latency Types.

8.4.2.  Reference Definition

   <describe
   measurement).  In practice, the data format for each type time offsets of result>

   For all output types ---

   T0 clocks at both the start of a measurement interval, (format "date-and-time" as
      specified
   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 Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]). the
   results).

   time_offset  The UTC Time Zone is required by Section 6.1 time value of
      [RFC2330].

   Tf the end result is expressed in units of a measurement interval, (format "date-and-time"
      seconds, as
      specified in Section 5.6 a signed 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].

   For LossRatio -- 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from the count 64-bit
      NTP timestamp as per section 6 of lost packets to total packets sent RFC [RFC5905]

   When a measurement controller requests a calibration measurement, the
   loopback is applied and the basis for result is output in the loss ratio calculation same format as per Section 4.1 a
   normal measurement with additional indication that it is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate of
   [RFC7680].

   For each <statistic>, one time offset as an indicator of
   the following sub-sections apply:

8.4.2.1.  Percentile95

   The 95th percentile SHALL degree of synchronization.

   Both internal loopback calibration and clock synchronization can be calculated using
   used to estimate the conditional
   distribution of all packets with a finite value *available accuracy* of One-way the Output Metric Units.
   For example, repeated loopback delay
   (undefined delays are excluded), a single value as follows:

   See section 4.1 measurements will reveal the
   portion of [RFC3393] for details on the conditional
   distribution to exclude undefined values Output result resolution which is the result of delay, system
   noise, and thus inaccurate.

7.5.  Administrative items

7.5.1.  Status

   Current

7.5.2.  Requestor

   This REFC number

7.5.3.  Revision

   1.0

7.5.4.  Revision Date

   YYYY-MM-DD

7.6.  Comments and Section 5 of
   [RFC6703] Remarks

   Additional (Informational) details for background on this analysis choice.

   See entry

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

   This section 4.3 of [RFC3393] specifies five initial registry entries for details on the percentile statistic
   (where Round-trip delay should be substituted UDP
   Periodic One-way Delay, and one for "ipdv").

   The percentile = 95, meaning that UDP Periodic One-way Loss.

   IANA Note: Registry "Name" below specifies a single registry entry,
   whose output format varies according to the reported delay, "95Percentile",
   is <statistic> element of
   the smallest value name that specifies one form of one-way delay statistical summary.  There is an
   additional metric name for which the Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of Loss metric.

   All column entries beside the singleton
   one-way delay values in ID, Name, Description, and Output
   Reference Method categories are the conditional distribution.  See same, thus this section
   11.3 of [RFC2330] for the definition of the percentile statistic
   using 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 to the EDF.

   95Percentile  The time value of registry entries, the result
   element ID and metric name.

8.1.1.  ID (Identifier)

   IANA is expressed in units of
      seconds, as asked to assign a positive value of type decimal64 with fraction
      digits = 9 (see section 9.3 of [RFC6020]) with resolution different numeric identifiers to each 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.2.2. six Metrics.

8.1.2.  Name

   OWDelay_Active_IP-UDP-Periodic20m-
   Payload142B_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   The mean SHALL be calculated using

   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 conditional distribution delay of
   all packets with a finite value stream of packets
   exchanged between two hosts (or measurement points), and reports the
   <statistic> One-way delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details all successfully exchanged packets
   based on the their conditional
   distribution to exclude undefined values of delay, and Section 5 delay distribution.

   where <statistic> is one of:

   o  95Percentile

   o  Mean

   o  Min

   o  Max

   o  StdDev

   OWLoss: This metric assesses the loss ratio of
   [RFC6703] for background on this analysis choice.

   See section 4.2.2 a stream of [RFC6049] for details on calculating this
   statistic, packets
   exchanged between two hosts (which are the two measurement points),
   and 4.2.3 of [RFC6049].

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

8.2.  Metric Definition

   This category includes columns to prompt the entry of type decimal64 with fraction digits = 9
      (see section 9.3 all necessary
   details related to the metric definition, including the RFC reference
   and values of input factors, called fixed parameters.

8.2.1.  Reference Definition

   For Delay:

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

   [RFC7679]
   Morton, A., and Stephan, E., "Spatial Composition of [RFC6020]) with resolution Metrics", RFC
   6049, January 2011.

   [RFC6049]

   Section 3.4 of 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from [RFC7679] provides the 64-bit
      NTP timestamp as per section 6 reference definition of RFC [RFC5905]

8.4.2.3.  Min

   The minimum SHALL be calculated using the conditional distribution
   singleton (single value) One-way delay metric.  Section 4.4 of
   all packets with
   [RFC7679] provides the reference definition expanded to cover a finite value
   multi-value sample.  Note that terms such as singleton and sample are
   defined in Section 11 of One-way [RFC2330].

   Only successful packet transfers with finite delay (undefined delays are excluded), a single value included in
   the sample, as follows:

   See prescribed in section 4.1 4.1.2 of [RFC3393] [RFC6049].

   For loss:

   Almes, G., Kalidini, S., Zekauskas, M., and A.  Morton, Ed., "A One-
   Way Loss Metric for details on 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 conditional
   distribution to exclude undefined values reference definition of delay, and the
   singleton (single value) one-way loss metric.  Section 5 3.4 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2
   [RFC7680] provides the reference definition expanded to cover a
   multi-singleton sample.  Note that terms such as singleton and sample
   are defined in Section 11 of [RFC6049] for details on calculating this
   statistic, [RFC2330].

8.2.2.  Fixed Parameters

   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 be calculated and 4.3.3 included in the
         header

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

   Min  The time value [RFC5357]

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

      *  142 octets total, including the result is TWAMP format (if used)

   Other measurement parameters:

   Tmax:  a loss threshold waiting time with value 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 RFC [RFC5905]

8.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 follows: [RFC5905].

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

8.3.  Method of [RFC3393] Measurement

   This category includes columns for details on the conditional
   distribution references to exclude undefined values relevant sections of delay,
   the RFC(s) and Section 5 of
   [RFC6703] any supplemental information needed to ensure an
   unambiguous methods for implementations.

8.3.1.  Reference Method

   The methodology for background on this analysis choice.

   See metric is defined as Type-P-One-way-Delay-
   Poisson-Stream in section 4.3.2 3.6 of [RFC6049] for a closely related method for
   calculating this statistic, [RFC7679] and 4.3.3 section 4.6 of [RFC6049].  The formula
   [RFC7679] using the Type-P and Tmax defined under Fixed Parameters.
   However, a Periodic stream is used, as follows:

            Max = (FiniteDelay [j])

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

   Max defined in [RFC3432].

   The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time value of the result for packet
   arrival.  Tmax is expressed in units of seconds, the waiting time used as the threshold to declare 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),
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, and with lossless conversion to/from counted for the 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

8.4.2.5.  Std_Dev OWLoss metric.

   The Std_Dev calculations on the one-way delay SHALL be calculated using 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 one-way delay 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 of [RFC6049]

   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.

   Since a closely related method 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 Runtime parameters are
   passed to that process.  The measurement protocol dictates the format
   of sequence numbers and time-stamps conveyed in the TWAMP-Test packet
   payload.

8.3.2.  Packet Stream Generation

   This section gives the details of the packet traffic which is the
   basis for
   calculating measurement.  In IPPM metrics, this statistic, is called the Stream,
   and 4.3.3 can easily be described by providing the list of [RFC6049].  The formula is stream
   parameters.

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

   incT  the nominal duration of a population.

   Std_Dev  The time inter-packet interval, first bit to
      first bit, with value of the result is 0.0200 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 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
   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 32-bit NTP
      timestamp as per section 6 of [RFC5905].

   dT the result is duration of the interval for allowed sample start times, with
      value 1.0000, 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, the
   loopback is applied and [RFC5905].

   T0 the result is output in actual start time of the same format as a
   normal measurement periodic stream, determined from T0
      and dT.

   NOTE: an initiation process with additional indication that it is a
   calibration result.  In any measurement, the measurement function
   SHOULD report its current estimate number of control exchanges
   resulting in unpredictable start times (within a time offset as an indicator of
   the degree of synchronization.

   Both internal loopback calibration and clock synchronization can interval) may
   be
   used sufficient 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 avoid synchronization 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 periodic streams, and Remarks

   Additional (Informational) details
   therefore a valid replacement for this entry

9.  ICMP Round-trip Latency selecting a start time at random
   from 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 and Loss Registry Entries

   This section specifies three initial registry entries for Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the ICMP
   Round-trip Latency, measurement system, and another entry for ICMP Round-trip Loss Ratio.

   This section specifies four Registry entries reported with many common
   columns.

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

9.1.  Summary

   This category includes multiple indexes context to be complete.

   Src  the registry entry: IP address of 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 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
   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 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 IP address of the delay 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 stream of ICMP packets
   exchanged between two hosts (which are time, the two start of a measurement points), 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 the Output Tf is the Round-trip delay for all successfully exchanged
   packets expressed to be interpreted as the <statistic> Duration of their conditional delay
   distribution, where <statistic> the measurement
      interval.  The start time is one of:

   o  Mean

   o  Min

   o  Max
   RTLoss: This metric assesses controlled through other means.

   Tf a time, the loss ratio end of a stream 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 ICMP
   packets exchanged between two hosts (which are the two measurement
   points), interval.

8.3.6.  Roles

   Src  launches each packet and the Output waits for return transmissions from
      Dst. This is the Round-trip loss ratio TWAMP Session-Sender.

   Dst  waits for all
   successfully exchanged packets expressed as each packet from Src and sends 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 return packet to prompt Src.
      This is the entry of TWAMP Session-Reflector.

8.4.  Output

   This category specifies all necessary details related to of the metric definition, including Output of measurements
   using the RFC reference
   and values metric.

8.4.1.  Type

   <insert name of input factors, called fixed parameters.

9.2.1. the output type, raw or a selected summary statistic>

   See subsection titles in 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> Latency Types.

8.4.2.  Reference Definition

   For all output types ---

   T0 the start of a measurement interval, (format "date-and-time" as
      specified in Section 2.4 5.6 of [RFC2681] provides the reference definition [RFC3339], see also Section 3 of the
   singleton (single value) Round-trip delay metric.
      [RFC6991]).  The UTC Time Zone is required by Section 3.4 6.1 of
   [RFC2681] provides
      [RFC2330].

   Tf the reference definition expanded to cover end 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].

   Note that although the [RFC2681] definition [RFC3339], see also Section 3 of "Round-trip-Delay
   between Src and Dst"
      [RFC6991]).  The UTC Time Zone is directionally ambiguous in the text, this
   metric tightens required by Section 6.1 of
      [RFC2330].

   For LossRatio -- the definition further count of lost packets to recognize that the host in
   the "Src" role will send total packets sent is
   the first packet to "Dst", and ultimately
   receive basis for the corresponding return packet from "Dst" (when neither are
   lost).

   Finally, note that loss ratio calculation as per Section 4.1 of
   [RFC7680].

   For each <statistic>, one of the variable "dT" is used in [RFC2681] to refer to following sub-sections apply:

8.4.2.1.  Percentile95

   The 95th percentile SHALL be calculated using the conditional
   distribution of all packets with a finite value of Round-trip One-way delay in metric definitions and methods.  The
   variable "dT" has been re-used in other IPPM literature to refer
   (undefined delays are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details on the conditional
   distribution to
   different quantities, exclude undefined values of delay, and cannot be used as a global variable name.

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

   [RFC6673]

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

   See section 4.3 of [RFC3393] for details on the percentile statistic
   (where Round-trip delay and loss metrics employ a maximum waiting time should be substituted for
   received packets, so "ipdv").

   The percentile = 95, meaning that the count of lost packets to total packets sent reported delay, "95Percentile",
   is the basis smallest value of one-way delay for which the loss ratio calculation as per Section 6.1 Empirical
   Distribution Function (EDF), F(95Percentile) >= 95% of
   [RFC6673].

9.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be
   determined and embedded the singleton
   one-way delay values in the measurement system conditional distribution.  See section
   11.3 of [RFC2330] for use when
   needed>

   Type-P as defined the definition of the percentile statistic
   using the EDF.

   95Percentile  The time value of the result is expressed in Section 13 units of [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:
      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 checksum MUST 64-bit NTP timestamp as per section 6 of RFC [RFC5905]

8.4.2.2.  Mean

   The mean SHALL be calculated and included in using the
         header

      *  (Identifier 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 Sequence Number set at Run-Time)

   o  ICMP Payload

      *  total Section 5 of 32 bytes
   [RFC6703] for background on this analysis choice.

   See section 4.2.2 of random info

   Other measurement parameters:

   o  Tmax: a loss threshold waiting [RFC6049] for details on calculating this
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time

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

9.3.  Method RFC [RFC5905]

8.4.2.3.  Min

   The minimum SHALL be calculated using the conditional distribution of Measurement

   This category includes columns for references to relevant sections
   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 RFC(s) and any supplemental information needed conditional
   distribution to ensure an
   unambiguous methods for implementations.

9.3.1.  Reference Method

   <for metric, insert relevant section references exclude undefined values of delay, and supplemental
   info>

   The methodology Section 5 of
   [RFC6703] for background on this metric is defined as Type-P-Round-trip-
   Delay-Poisson-Stream in analysis choice.

   See section 2.6 4.3.2 of RFC 2681 [RFC2681] [RFC6049] for details on calculating this
   statistic, and section
   3.6 4.3.3 of RFC 2681 [RFC2681] using the Type-P and Tmax defined under
   Fixed Parameters. [RFC6049].

   Min  The reference method distinguishes between long-delayed packets and
   lost packets by implementing a maximum waiting time for packet
   arrival.  Tmax is value of the waiting time used result is expressed in units of seconds,
      as the threshold to declare a
   packet lost.  Lost packets SHALL be designated as having undefined
   delay, 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 counted for with lossless conversion to/from the RTLoss metric. 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

8.4.2.4.  Max

   The calculations on the delay (RTD) maximum 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 RTD 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

   See section 4.3.2 of [RFC6049] for a closely related method requires for
   calculating this statistic, and 4.3.3 of [RFC6049].  The formula is
   as follows:

            Max = (FiniteDelay [j])

                  such that for some way to distinguish between
   different packets index, j, where 1 <= j <= N
                  FiniteDelay[j] >= FiniteDelay[n] for all n

   Max  The time value of the result is expressed in units of seconds,
      as a stream to establish correspondence between
   sending times 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 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 lossless conversion to/from the Fixed and Runtime parameters are passed to
   that process. 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

8.4.2.5.  Std_Dev

   The ICMP measurement process and protocol will dictate Std_Dev SHALL be calculated using the format conditional distribution of sequence numbers and other identifiers.

   Refer to Section 4.4
   all packets with a finite value of [RFC6673] for expanded discussion One-way delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details on the
   instruction to "send a Type-P packet back conditional
   distribution to the Src as quickly as
   possible" in Section 2.6 exclude undefined values of RFC 2681 [RFC2681]. delay, and Section 8 of
   [RFC6673] presents additional requirements which MUST be included in
   the method 5 of measurement
   [RFC6703] for background on this metric.

9.3.2.  Packet Stream Generation

   This analysis choice.

   See section gives the details 4.3.2 of the packet traffic which is the
   basis [RFC6049] for measurement.  In IPPM metrics, a closely related method for
   calculating this is called the Stream, statistic, and can easily be described by providing the list 4.3.3 of stream
   parameters. [RFC6049].  The ICMP metrics use a sending discipline called "SendOnRcv" or Send
   On Receive.  This formula is a modification of Section 3 of [RFC3432], which
   prescribes
   the method classic calculation for generating Periodic streams using
   associated parameters:

   incT  the nominal duration of inter-packet interval, first bit to
      first bit

   dT the duration standard deviation of the interval for allowed sample start times

   T0 the actual start a population.

   Std_Dev  The time value of the periodic stream

   The incT and T0 stream parameters will be specified as Run-time
   parameters, dT result is not used expressed in SendOnRcv.

   A SendOnRcv sender behaves exactly like units of
      seconds, as a Periodic stream generator
   while all reply packets arrive positive value of type decimal64 with RTD < incT, fraction
      digits = 9 (see section 9.3 of [RFC6020]) with resolution of
      0.000000001 seconds (1.0 ns), and the inter-packet
   interval will be constant.

   If a reply packet arrives with RTD >= incT, then the inter-packet
   interval for lossless conversion to/from
      the next sending time 64-bit NTP timestamp as per section 6 of RFC [RFC5905]

8.4.3.  Metric Units

   The <statistic> of One-way Delay is nominally RTD.

   If 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 reply packet fails percentage of lost packets
   to arrive within Tmax, then the inter-packet
   interval for total packets sent.

8.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a means to quantify the next sending
   systematic and random errors of a time is nominally Tmax.

   If measurement.  In-situ
   calibration could be enabled with an 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 internal loopback that includes
   as much of the packets
   observed, measurement system as possible, performs address
   manipulation as needed, and this section provides some form of isolation (e.g.,
   deterministic delay) to avoid send-receive interface contention.
   Some portion of the filter details (when
   present).

   <section reference>.

   NA

9.3.4.  Sampling Distribution

   <insert time distribution details, or how random and systematic error can be characterized
   this is diff from way.

   For one-way delay measurements, the
   filter>

   NA

9.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are input factors that error calibration must be determined,
   configured into include an
   assessment of the measurement system, and reported internal clock synchronization with the results its external
   reference (this internal clock is supplying timestamps for the context to be complete.

   <list
   measurement).  In practice, the time offsets of run-time parameters, clocks at both the
   source and their data formats>

   Src destination are needed to estimate the IP address of systematic error
   due to imperfect clock synchronization (the time offsets are
   smoothed, thus the host random variation is not usually represented in the Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone
   results).

   time_offset  The time value for IPv6,
      see Section 4 of [RFC6991])

   Dst  the IP address of the host result is expressed in the Dst Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see section 4 units of [RFC6991])

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

   When T0 is "all-zeros", a start time measurement controller requests a calibration measurement, the
   loopback is unspecified applied and Tf is to be interpreted as the Duration of the measurement
      interval.  The start time result is controlled through other means.

   Count  The total count of ICMP Echo Requests to send, formatted output in the same format as a
      uint16, as per section 9.2 of [RFC6020].

   (see the Packet Stream Generation section for
   normal measurement with additional Run-time
   parameters)

9.3.6.  Roles

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

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

9.4.1.  Type

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

   See subsection titles in Reference Definition for Latency Types.

   LossRatio -- Output result resolution which is the count result of lost packets to total packets sent is system
   noise, and thus inaccurate.

8.5.  Administrative items

8.5.1.  Status

   Current

8.5.2.  Requestor

   This RFC number

8.5.3.  Revision

   1.0

8.5.4.  Revision Date

   YYYY-MM-DD

8.6.  Comments and Remarks

9.  ICMP Round-trip Latency and Loss Registry Entries

   This section specifies three initial registry entries for the
   basis ICMP
   Round-trip Latency, and another entry for ICMP Round-trip Loss Ratio.

   This section specifies four Registry entries with many common
   columns.

   All column entries beside the loss ratio calculation as per Section 6.1 of [RFC6673].

9.4.2. ID, Name, Description, and Output
   Reference Definition

   <describe the data format for each type of result>

   For all output types ---

   T0 Method categories are the start of same, thus this section proposes
   two closely-related registry entries.  As a measurement interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC3339], see result, IANA is also Section 3 of
      [RFC6991]).  The UTC Time Zone
   asked to assign four corresponding URNs and 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)

   IANA is required by Section 6.1 asked to assign different numeric identifiers to each 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
   four Named Metrics.

9.1.2.  Name

   RTDelay_Active_IP-ICMP-SendOnRcv_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is required 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 Section 6.1 of
      [RFC2330].

   TotalCount IANA>/<name>

9.1.4.  Description

   RTDelay: This metric assesses the count delay of a stream of ICMP packets actually sent by the Src to Dst
      during
   exchanged between two hosts (which are the two measurement interval.

   For LossRatio -- points),
   and the count of lost packets to total packets sent Output is the basis Round-trip delay for the loss ratio calculation all successfully exchanged
   packets expressed as per Section 4.1 the <statistic> of
   [RFC7680].

   For each <statistic>, their conditional delay
   distribution, where <statistic> is one of the following sub-sections apply:

9.4.2.1. of:

   o  Mean

   The mean SHALL be calculated using

   o  Min

   o  Max

   RTLoss: This metric assesses the conditional distribution loss ratio of
   all packets with a finite value stream of Round-trip delay (undefined delays ICMP
   packets exchanged between two hosts (which 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, two measurement
   points), and 4.2.3 of [RFC6049].

   Mean  The time value of the result Output is the Round-trip loss ratio for all
   successfully exchanged packets expressed in units of seconds, as a positive value of type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC6020]) with resolution 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 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from all necessary
   details related to the 64-bit
      NTP timestamp as per section 6 metric definition, including the RFC reference
   and values of input factors, called fixed parameters.

9.2.1.  Reference Definition

   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay
   Metric for IPPM", RFC [RFC5905]

9.4.2.2.  Min

   The minimum SHALL be calculated using the conditional distribution 2681, September 1999.

   [RFC2681]

   Section 2.4 of
   all packets with a finite value [RFC2681] provides the reference definition of the
   singleton (single value) Round-trip delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 metric.  Section 3.4 of [RFC3393] for details on
   [RFC2681] provides the conditional
   distribution reference definition expanded to exclude undefined values of delay, cover a
   multi-singleton sample.  Note that terms such as singleton and sample
   are defined in Section 5 11 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 [RFC2330].

   Note that although the [RFC2681] definition of [RFC6049] for details on calculating "Round-trip-Delay
   between Src and Dst" is directionally ambiguous in the text, this
   statistic,
   metric tightens the definition further to recognize that the host in
   the "Src" role will send the first packet to "Dst", and 4.3.3 of [RFC6049].

   Min  The time value of 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]

9.4.2.3.  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 to total packets sent
   is the basis for the loss ratio calculation as per Section 6.1 of Round-trip delay (undefined delays
   are excluded), a single value
   [RFC6673].

9.2.2.  Fixed Parameters

   Type-P as follows:

   See section 4.1 defined in Section 13 of [RFC3393] for details on the conditional
   distribution [RFC2330]:

   o  IPv4 header values:

      *  DSCP: set to exclude undefined values of delay, 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 Section 5 included in the
         header

      *  (Identifier and 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 RFC [RFC5905]

9.4.3.  Metric Units

   <insert units [RFC5905].

9.3.  Method of Measurement

   This category includes columns for references to relevant sections of
   the measured results, RFC(s) and the reference
   specification>. any supplemental information needed to ensure an
   unambiguous methods for implementations.

9.3.1.  Reference Method

   The <statistic> of Round-trip Delay methodology for this metric is expressed defined as Type-P-Round-trip-
   Delay-Poisson-Stream in seconds, where
   <statistic> is one of:

   o  Mean

   o  Min

   o  Max 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.

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

   The calculations on the delay (RTD) 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 RTD value MAY enforce the Tmax threshold on
   stored values before calculations.  See section 4.1 of [RFC3393] for
   details on the conditional distribution to total packets sent.

9.4.4.  Calibration exclude undefined values
   of delay, and Section 3.7.3 5 of [RFC7679] provides [RFC6703] for background on this analysis
   choice.

   The reference method requires some way to distinguish between
   different packets in a means stream to quantify the
   systematic establish correspondence between
   sending times and random errors of a time measurement.  In-situ
   calibration could receiving times for each successfully-arriving
   packet.  Sequence numbers or other send-order identification MUST be enabled with an internal loopback
   retained at the Source
   host that includes as much of the Src or included with each packet to disambiguate
   packet reordering if it occurs.

   The measurement system as possible,
   performs address manipulation as needed, and provides some form of
   isolation (e.g., deterministic delay) process will determine the sequence numbers applied
   to avoid send-receive interface
   contention.  Some portion of test packets after the random Fixed and systematic error can be
   characterized this way.

   When a Runtime parameters are passed to
   that process.  The ICMP measurement controller requests a calibration measurement, the
   loopback is applied process and protocol will dictate
   the result is output in the same format as a
   normal measurement with additional indication that it is a
   calibration result.

   Both internal loopback calibration of sequence numbers and clock synchronization can be
   used other identifiers.

   Refer to estimate the *available accuracy* Section 4.4 of [RFC6673] for expanded discussion of the Output Metric Units.
   For example, repeated loopback delay measurements will reveal
   instruction to "send a Type-P packet back to the
   portion Src as quickly as
   possible" in Section 2.6 of the Output result resolution RFC 2681 [RFC2681].  Section 8 of
   [RFC6673] presents additional requirements which is MUST be included in
   the result method of 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 measurement for this entry

10.  TCP Round-Trip Delay and Loss Registry Entries metric.

9.3.2.  Packet Stream Generation

   This section specifies three initial registry entries for gives the Passive
   assessment details of TCP Round-Trip Delay (RTD) and another entry for 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 categories are packet traffic which is the same, thus
   basis for measurement.  In IPPM metrics, 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 multiple indexes to the registry entry: called the
   element ID Stream,
   and metric name.

10.1.1.  ID (Identifier)

   <insert a numeric identifier, an integer, TBD>

   IANA is asked to assign different numeric identifiers to each of can easily be described by providing the
   four Named Metrics.

10.1.2.  Name

   <insert name according to metric naming convention>

   RTDelay_Passive_IP-TCP_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   RTDelay_Passive_IP-TCP-HS_RFCXXXXsecY_Seconds_Singleton

   Note that list of stream
   parameters.

   The ICMP metrics use a mid-point observer only has the opportuinty to compose sending discipline called "SendOnRcv" or Send
   On Receive.  This is a
   single RTDelay on modification of Section 3 of [RFC3432], which
   prescribes the TCP Hand Shake.

   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 method for generating Periodic streams using
   associated parameters:

   incT  the round-trip delay nominal duration of TCP packets
   constituting a single connection, exchanged between two hosts.  We
   consider inter-packet interval, first bit to
      first bit

   dT the measurement duration of round-trip delay based on a single
   Observation Point [RFC7011] somewhere in the network. interval for allowed sample start times

   T0 the actual start time of the periodic stream

   The Output incT and T0 stream parameters will be specified as Run-time
   parameters, dT is
   the Round-trip delay for not used in SendOnRcv.

   A SendOnRcv sender behaves exactly like a Periodic stream generator
   while all successfully exchanged reply packets expressed
   as arrive with RTD < incT, and the <statistic> of their conditional delay distribution, where
   <statistic> is one of:

   o  Mean

   o  Min
   o  Max

   RTLoss: This metric assesses inter-packet
   interval will be constant.

   If a reply packet arrives with RTD >= incT, then the estimated loss count inter-packet
   interval for TCP packets
   constituting the next sending time is nominally RTD.

   If a single connection, exchanged between two hosts.  We
   consider reply packet fails to arrive within Tmax, then the measurement of round-trip delay inter-packet
   interval for the next sending time is nominally Tmax.

   If an immediate send on reply arrival is desired, then set incT=0.

9.3.3.  Traffic Filtering (observation) Details

   The measured results based on a single
   Observation Point [RFC7011] somewhere in filtered version of the network.  The Output is packets
   observed, and this section provides the estimated Loss Count filter details (when
   present).

   NA

9.3.4.  Sampling Distribution

   NA

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

10.1.5.  Change Controller

   IETF

10.1.6.  Version (of Registry Format)

   1.0

10.2.  Metric Definition

   This category includes columns context to prompt be complete.

   Src  the entry IP address of all necessary
   details related to the metric definition, including host in the RFC reference
   and values Src Role (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see Section 4 of input factors, called fixed parameters.

10.2.1.  Reference Definitions

   <Full bibliographic reference to an immutable doc.>

   Although there is no RFC that describes passive measurement [RFC6991])

   Dst  the IP address of Round-
   Trip Delay, the parallel definition host in the Dst Role (format ipv4-address-
      no-zone value for Active measurement is:

   Almes, G., Kalidindi, S., and M.  Zekauskas, "A Round-trip Delay
   Metric IPv4, or ipv6-address-no-zone value for IPPM", RFC 2681, September 1999.

   [RFC2681]

   <specific IPv6,
      see section reference and additional clarifications, if needed>

   This metric definition uses 4 of [RFC6991])

   T0 a time, the terms singleton and sample start of a measurement interval, (format "date-and-
      time" as defined specified in Section 11 of [RFC2330].  (Section 2.4 5.6 of [RFC2681] provides the
   reference definition [RFC3339], see also Section 3
      of the singleton (single value) Round-trip delay
   metric. [RFC6991]).  The UTC Time Zone is required by Section 3.4 6.1 of [RFC2681] provides the reference definition
   expanded to cover
      [RFC2330].  When T0 is "all-zeros", a multi-singleton sample.)

   With the Observation Point [RFC7011] (OP) typically located between
   the hosts participating in the TCP connection, the Round-trip Delay
   metric requires two individual measurements between the OP start time is unspecified
      and each
   host, such that the Spatial Composition [RFC6049]of the measurements
   yields a Round-trip Delay singleton (we are extending Tf is to be interpreted as the composition Duration of one-way subpath delays to subpath round-trip delay).

   Using the direction measurement
      interval.  The start time is controlled through other means.

   Count  The total count of TCP SYN transmission ICMP Echo Requests to anchor send, formatted as a
      uint16, as per section 9.2 of [RFC6020].

   (see the
   nomenclature, host A Packet Stream Generation section for additional Run-time
   parameters)

9.3.6.  Roles

   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.

9.4.  Output

   This category specifies all details of the SYN and host B replies with SYN-ACK
   during connection establishment.  The direction Output of SYN transfer is
   considered measurements
   using the Forward direction metric.

9.4.1.  Type

   See subsection titles in Reference Definition for Latency Types.

   LossRatio -- the count of transmission, from A through OP lost packets to B (Reverse total packets sent is B through OP to A).

   Traffic filters reduce the packet stream at
   basis for the OP to a Qualified
   bidirectional flow packets.

   In loss ratio calculation as per Section 6.1 of [RFC6673].

9.4.2.  Reference Definition

   For all output types ---

   T0 the definitions below, Corresponding Packets are transferred in
   different directions and convey a common value in start of a TCP header field
   that establishes correspondence (to the extent possible).  Examples
   may be found 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 TCP timestamp fields.

   For end of a real number, RTD_fwd, >> the Round-trip Delay measurement interval, (format "date-and-time" as
      specified in the Forward
   direction from OP to host B at time T' Section 5.6 of [RFC3339], see also Section 3 of
      [RFC6991]).  The UTC Time Zone is RTD_fwd << REQUIRES that OP
   observed a Qualified Packet to host B at wire-time T', that host B
   received that packet and required by Section 6.1 of
      [RFC2330].

   TotalCount  the count of packets actually sent a Corresponding Packet back by the Src to host A,
   and OP observed Dst
      during the Corresponding Packet at wire-time T' + RTD_fwd. measurement interval.

   For a real number, RTD_rev, >> the Round-trip Delay in LossRatio -- the Reverse
   direction from OP to host A at time T'' is RTD_rev << REQUIRES that
   OP observed a Qualified Packet count of lost packets to host A at wire-time T'', that host
   A received that packet and total packets sent a Corresponding Packet back to host
   B, and that OP observed is
   the Corresponding Packet at wire-time T'' +
   RTD_rev.

   Ideally, basis for the packet sent from host B to host A in both definitions
   above SHOULD loss ratio calculation as per Section 4.1 of
   [RFC7680].

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

9.4.2.1.  Mean

   The mean SHALL be calculated using the same packet (or, when measuring RTD_rev first, 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 packet from host A conditional
   distribution to host B in both definitions should be the
   same).

   The REQUIRED Composition Function exclude undefined values of delay, and Section 5 of
   [RFC6703] for a singleton background on this analysis choice.

   See section 4.2.2 of Round-trip Delay
   at [RFC6049] for details on calculating this
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time T (where T is value of the earliest result is expressed in units of T' and T'' above) is:

   RTDelay seconds,
      as a positive value of type decimal64 with fraction digits = RTD_fwd + RTD_rev

   Note that when OP is located at host A or host B, one 9
      (see section 9.3 of [RFC6020]) with resolution of 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from the terms
   composing RTDelay will 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

9.4.2.2.  Min

   The minimum SHALL be zero or negligible.

   When calculated using the Qualified and Corresponding Packets are a TCP-SYN and conditional distribution of
   all packets with a TCP-
   SYN-ACK, then RTD_fwd == RTD_HS_fwd.

   When the Qualified and Corresponding Packets finite value of Round-trip delay (undefined delays
   are excluded), a TCP-SYN-ACK and a
   TCP-ACK, then RTD_rev == RTD_HS_rev.

   The REQUIRED Composition Function for a singleton single value as follows:

   See section 4.1 of Round-trip Delay [RFC3393] for details on the connection Hand Shake:

   RTDelay_HS = RTD_HS_fwd + RTD_HS_rev

   The definition conditional
   distribution to exclude undefined values of Round-trip Loss Count uses the nomenclature
   developed above, based delay, and Section 5 of
   [RFC6703] for background on observation this analysis choice.

   See section 4.3.2 of the TCP header sequence
   numbers [RFC6049] for details on calculating this
   statistic, and storing 4.3.3 of [RFC6049].

   Min  The time value of the sequence number gaps observed.  Packet Losses
   can be inferred from:

   o  Out-of-order segments: TCP segments are transmitted result is expressed in units of seconds,
      as a positive value of type decimal64 with
      monotonically increasing sequence numbers, but these segments may
      be received out fraction digits = 9
      (see section 9.3 of order.  Section 3 [RFC6020]) with resolution of [RFC4737] describes 0.000000001
      seconds (1.0 ns), and with lossless conversion to/from the
      notion 64-bit
      NTP timestamp as per section 6 of "next expected" sequence numbers which can RFC [RFC5905]

9.4.2.3.  Max

   The maximum SHALL be adapted to
      TCP segments (for calculated using the purpose conditional distribution of detecting reordered packets).
      Observation
   all packets with a finite value of out-of-order segments indicates loss Round-trip delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of [RFC3393] for details on the path
      prior conditional
   distribution to the OP, exclude undefined values of delay, and creates a gap.

   o  Duplicate segments: Section 2 5 of [RFC5560] defines identical
      packets
   [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 suitable
   as follows:

            Max = (FiniteDelay [j])

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

   Max  The time value of TCP packets to detect
      duplication.  Observation the result is expressed in units of duplicate segments *without seconds,
      as a
      corresponding gap* indicates loss on the path following the OP
      (because they overlap part positive value of the delivered sequence numbers
      already observed at OP).

   Each observation type decimal64 with fraction digits = 9
      (see section 9.3 of an out-of-order or duplicate infers a singleton [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 loss, but composition RFC [RFC5905]

9.4.3.  Metric Units

   The <statistic> of Round-trip Loss Counts will be conducted
   over a measurement interval which Delay is synonymous with a single TCP
   connection.

   With the above observations expressed in the Forward direction over a
   measurement interval, the count of out-of-order and duplicate
   segments seconds, where
   <statistic> is defined as RTL_fwd.  Comparable observations in the
   Reverse direction are defined one of:

   o  Mean

   o  Min

   o  Max

   The Round-trip Loss Ratio is expressed as RTL_rev.

   For a measurement interval (corresponding percentage of lost
   packets to total packets sent.

9.4.4.  Calibration

   Section 3.7.3 of [RFC7679] provides a single TCP
   connection), T0 means to Tf, quantify the REQUIRED Composition Function for
   systematic and random errors of a time measurement.  In-situ
   calibration could be enabled with an internal loopback at the
   two single-direction counts of inferred loss is:

   RTLoss = RTL_fwd + RTL_rev

10.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors Source
   host that must be
   determined and embedded in includes as much of the 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, FIN, @@@@@ others??

      *  Timestamp Option (TSopt): Set

         +  Kind: 8

         +  Length: 10 bytes

   o

10.3.  Method as possible,
   performs address manipulation as needed, and provides some form of Measurement

   This category includes columns for references
   isolation (e.g., deterministic delay) to relevant sections avoid send-receive interface
   contention.  Some portion of the RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations.

10.3.1.  Reference Methods

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

   The foundation methodology for systematic error can be
   characterized this metric way.

   When a measurement controller requests a calibration measurement, the
   loopback is defined applied and the result is output in Section 4 of
   [RFC7323] using the Timestamp Option same format as a
   normal measurement with modifications additional indication that allow
   application at it is a mid-path Observation Point (OP) [RFC7011].  Further
   details and applicable heuristics were derived from [Strowes]
   calibration result.

   Both internal loopback calibration and
   [Trammell-14].

   The Traffic Filter at the OP is configured clock synchronization can be
   used to observe a single TCP
   connection.  When the SYN, SYN-ACK, ACK handshake occurs, it offers estimate the first opportunity to measure both RTD_fwd (on *available accuracy* of the SYN to SYN-ACK
   pair) and RTD_rev (on Output Metric Units.
   For example, repeated loopback delay measurements will reveal the SYN-ACK to ACK pair).  Label this singleton
   portion of RTDelay as RTDelay_HS (composed using the forward Output result resolution which is the result of system
   noise, and reverse
   measurement pair).  RTDelay_HS SHALL be treated separately from other
   RTDelays on data-bearing packets thus inaccurate.

9.5.  Administrative items

9.5.1.  Status

   Current

9.5.2.  Requestor

   This RFC number

9.5.3.  Revision

   1.0

9.5.4.  Revision Date

   YYYY-MM-DD

9.6.  Comments and their ACKs.  The RTDelay_HS
   value MAY be used as a sanity check on other Composed values of
   RTDelay.

   For payload bearing packets, the OP measures the time interval
   between observation Remarks

   None

10.  TCP Round-Trip Delay and Loss Registry Entries

   This section specifies three initial registry entries for the Passive
   assessment of a packet with Sequence Number s, TCP Round-Trip Delay (RTD) and the
   corresponding ACK another entry for TCP
   Round-trip Loss Count.

   This section specifies four Registry entries 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 common
   columns.

   All column entries beside the ID, Name, Description, and Output
   Reference Method categories are unidirectional (say, in the Forward
   direction from host A to host B), it same, thus this section proposes
   four closely-related registry entries.  As a result, IANA is necessary also
   asked to use pure ACK
   packets with Timestamp (TSval) assign four corresponding URNs and their Timestamp value echo URLs to
   perform a RTD_rev measurement.  The time interval between observation
   of the ACK from B each Named
   Metric.

10.1.  Summary

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

10.1.1.  ID (Identifier)

   IANA is asked to assign different numeric identifiers to each of the corresponding packet with Timestamp
   echo (TSecr)
   four Named Metrics.

10.1.2.  Name

   RTDelay_Passive_IP-TCP_RFCXXXXsecY_Seconds_<statistic>

   where <statistic> is one of:

   o  Mean

   o  Min

   o  Max

   RTDelay_Passive_IP-TCP-HS_RFCXXXXsecY_Seconds_Singleton

   Note that a mid-point observer only has the RTD_rev.

   Delay Measurement Filtering Heuristics:

   If Data payloads were transferred in both Forward and Reverse
   directions, then opportuinty to compose a
   single RTDelay on the Round-Trip Time Measurement Rule in Section 4.1
   of [RFC7323] could be applied. TCP Hand Shake.

   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 rule essentially excludes any metric assesses the round-trip delay of TCP packets
   constituting a single connection, exchanged between two hosts.  We
   consider the measurement using of round-trip delay based on a packet unless it makes progress single
   Observation Point [RFC7011] somewhere in the transfer
   (advances network.  The Output is
   the left edge of Round-trip delay for all successfully exchanged packets expressed
   as the send window, consistent
   with[Strowes]).

   A different heuristic from [Trammell-14] is to exclude any RTD_rev
   that <statistic> of their conditional delay distribution, where
   <statistic> is larger than previously observed values. one of:

   o  Mean

   o  Min

   o  Max

   RTLoss: This would tend to
   exclude Reverse measurements taken when metric assesses the Application has no data
   ready to send, because considerable time could be added to RTD_rev
   from this source estimated loss count for TCP packets
   constituting a single connection, exchanged between two hosts.  We
   consider the measurement of error.

   @@@@ Note that round-trip delay based on a single
   Observation Point [RFC7011] somewhere in the above Heuristic assumes that host A network.  The Output is sending
   data.  Host A expecting a download would mean that this heuristic
   should be applied
   the estimated Loss Count for the measurement 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 RTD_fwd.

   The statistic calculations prompt the entry of all necessary
   details related to summarize the delay (RTDelay) SHALL be
   performed on metric definition, including the conditional distribution, conditioned on successful
   Forward RFC reference
   and Reverse measurements which follow values of input factors, called fixed parameters.

10.2.1.  Reference Definitions

   Although there is no RFC that describes passive measurement of Round-
   Trip Delay, the Heuristics.

   Method parallel definition for Inferring Loss:

   The OP tracks sequence numbers Active measurement is:

   Almes, G., Kalidindi, S., and stores gaps M.  Zekauskas, "A Round-trip Delay
   Metric for each direction of
   transmission, as well as IPPM", RFC 2681, September 1999.

   [RFC2681]

   This metric definition uses the next-expected sequence number terms singleton and sample as defined
   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 Section 11 of evaluation based on the RTDelay.

   Distinguish Re-ordered from OOO due to loss, because sequence number
   gap is filled during the same RTDelay window.  Segments detected as
   re-ordered according to [RFC4737] MUST reduce [RFC2330].  (Section 2.4 of [RFC2681] provides the Loss Count inferred
   from Out-of-order segments.

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

   Sources
   reference definition of Error:

   The principal source the singleton (single value) Round-trip delay
   metric.  Section 3.4 of RTDelay error is [RFC2681] provides the host processing time reference definition
   expanded to
   return cover a packet multi-singleton sample.)

   With the Observation Point [RFC7011] (OP) typically located between
   the hosts participating in the TCP connection, the Round-trip Delay
   metric requires two individual measurements between the OP and each
   host, such that defines the termination of a time interval.  The
   heuristics above intend to mitigate these errors by excluding Spatial Composition [RFC6049]of the measurements where host processing time is
   yields a significant part Round-trip Delay singleton (we are extending the composition
   of
   RTD_fwd or RTD_rev. one-way subpath delays to subpath round-trip delay).

   Using the direction of TCP SYN transmission to anchor the
   nomenclature, host A key source sends the SYN and host B replies with SYN-ACK
   during connection establishment.  The direction of RTLoss error SYN transfer is observation loss, described in
   section 3 of [Trammell-14].

10.3.2.  Packet Stream Generation

   This section gives
   considered the details Forward direction of transmission, from A through OP
   to B (Reverse is B through OP to A).

   Traffic filters reduce the packet traffic which is stream at the
   basis for measurement. OP to a Qualified
   bidirectional flow packets.

   In IPPM metrics, this is called the Stream, definitions below, Corresponding Packets are transferred in
   different directions and can easily be described by providing the list of stream
   parameters.

   NA

10.3.3.  Traffic Filtering (observation) Details

   The measured results based on convey a filtered version of common value in a TCP header field
   that establishes correspondence (to the packets
   observed, and this section provides extent possible).  Examples
   may be found in the filter details (when
   present).

   The Fixed Parameters above give TCP timestamp fields.

   For a portion of real number, RTD_fwd, >> the Traffic Filter.
   Other aspects will be supplied as Run-time Parameters (below).

10.3.4.  Sampling Distribution

   <insert Round-trip Delay in the Forward
   direction from OP to host B at time distribution details, or how this T' is diff from the
   filter>

   This metric requires RTD_fwd << REQUIRES that OP
   observed a complete sample of all packets Qualified Packet to host B at wire-time T', that qualify
   according host B
   received that packet and sent a Corresponding Packet back to the Traffic Filter criteria.

10.3.5.  Run-time Parameters host A,
   and Data Format

   Run-time Parameters are input factors OP observed the Corresponding Packet at wire-time T' + RTD_fwd.

   For a real number, RTD_rev, >> the Round-trip Delay in the Reverse
   direction from OP to host A at time T'' is RTD_rev << REQUIRES that must be determined,
   configured into the measurement system,
   OP observed a Qualified Packet to host A at wire-time T'', that host
   A received that packet and reported with the results
   for the context sent a Corresponding Packet back to be complete.

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

   Src that OP observed the IP address of Corresponding Packet at wire-time T'' +
   RTD_rev.

   Ideally, the packet sent from host in the B to host A Role (format ipv4-
      address-no-zone value for IPv4, or ipv6-address-no-zone value for
      IPv6, see Section 4 of [RFC6991])

   Dst in both definitions
   above SHOULD be the IP address of same packet (or, when measuring RTD_rev first,
   the packet from host in the A to host B (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 Td is to both definitions should be interpreted as the Duration of the measurement
      interval.
   same).

   The start time is controlled through other means.

   Td Optionally, the end of REQUIRED Composition Function for a measurement interval, (format "date-and-
      time" as specified in Section 5.6 of [RFC3339], see also Section 3 singleton of [RFC6991]), or the duration (see T0).  The UTC Time Zone Round-trip Delay
   at time T (where T is
      required by Section 6.1 of [RFC2330].  Alternatively, the end earliest of 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 measurement interval MAY terms
   composing RTDelay will be controlled by zero or negligible.

   When the measured
      connection, where Qualified and Corresponding Packets are a TCP-SYN and a TCP-
   SYN-ACK, then RTD_fwd == RTD_HS_fwd.

   When the second pair of FIN Qualified and ACK packets exchanged
      between host A Corresponding Packets are a TCP-SYN-ACK and B effectively ends a
   TCP-ACK, then RTD_rev == RTD_HS_rev.

   The REQUIRED Composition Function for a singleton of Round-trip Delay
   for the interval.

   TTL or Hop Limit  Set at desired value.

10.3.6.  Roles

   <lists connection Hand Shake:

   RTDelay_HS = RTD_HS_fwd + RTD_HS_rev

   The definition of Round-trip Loss Count uses the names nomenclature
   developed above, based on observation of the different roles from TCP header sequence
   numbers and storing the measurement method>

   host A  launches sequence number gaps observed.  Packet Losses
   can be inferred from:

   o  Out-of-order segments: TCP segments are transmitted with
      monotonically increasing sequence numbers, but these segments may
      be received out of order.  Section 3 of [RFC4737] describes the SYN packet
      notion of "next expected" sequence numbers which can be adapted to open
      TCP segments (for the connection, and
      synonymous with an IP address.

   host B  replies with purpose of detecting reordered packets).
      Observation of out-of-order segments indicates loss on the SYN-ACK packet path
      prior to open the connection, OP, and
      synonymous with an IP address.

10.4.  Output

   This category specifies all details creates a gap.

   o  Duplicate segments: Section 2 of the Output [RFC5560] defines identical
      packets and is suitable for evaluation of measurements
   using the metric.

10.4.1.  Type

   <insert name TCP packets to detect
      duplication.  Observation of the output type, raw or duplicate segments *without a selected summary statistic>

   See subsection titles in Reference Definition for RTDelay Types.

   For RTLoss --
      corresponding gap* indicates loss on the count of lost packets.

10.4.2.  Reference Definition

   <describe path following the data format for each type OP
      (because they overlap part of result>

   For all output types ---

   T0 the start delivered sequence numbers
      already observed at OP).

   Each observation of an out-of-order or duplicate infers a measurement interval, (format "date-and-time" as
      specified in Section 5.6 singleton
   of [RFC3339], see also Section 3 loss, but composition of
      [RFC6991]).  The UTC Time Zone Round-trip Loss Counts will be conducted
   over a measurement interval which is required by Section 6.1 of
      [RFC2330].

   Tf synonymous with a 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 the count of
      [RFC6991]).  The UTC Time Zone out-of-order and duplicate
   segments is required by Section 6.1 of
      [RFC2330].  The end of defined as RTL_fwd.  Comparable observations in the
   Reverse direction are defined as RTL_rev.

   For a 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 (corresponding to a single TCP
   connection), T0 to Tf, the
      interval.

   ...  ...

   For RTDelay_HS -- REQUIRED Composition Function for a the Round trip delay
   two single-direction counts of the Handshake.

   For inferred loss is:

   RTLoss -- the count of lost packets.

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

10.4.2.1.  Mean

   The mean SHALL = RTL_fwd + RTL_rev

10.2.2.  Fixed Parameters

   <list and specify Fixed Parameters, input factors that must be calculated using
   determined and embedded in 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 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, FIN, @@@@@ others??

      *  Timestamp Option (TSopt): Set

         +  Kind: 8

         +  Length: 10 bytes

   o

10.3.  Method of [RFC3393] Measurement

   This category includes columns for details on the conditional
   distribution references to exclude undefined values relevant sections of delay,
   the RFC(s) and Section 5 of
   [RFC6703] any supplemental information needed to ensure an
   unambiguous methods for background on this analysis choice.

   See section 4.2.2 of [RFC6049] implementations.

10.3.1.  Reference Methods

   The foundation methodology for details on calculating this
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time value of the result metric is expressed defined 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 Section 4 of RFC [RFC5905]

10.4.2.2.  Min

   The minimum SHALL be calculated
   [RFC7323] using the conditional distribution of
   all packets Timestamp Option with modifications that allow
   application at a finite value of Round-trip delay (undefined delays
   are excluded), mid-path Observation Point (OP) [RFC7011].  Further
   details and applicable heuristics were derived from [Strowes] and
   [Trammell-14].

   The Traffic Filter at the OP is configured to observe a single value as follows:

   See section 4.1 of [RFC3393] for details on TCP
   connection.  When the conditional
   distribution SYN, SYN-ACK, ACK handshake occurs, it offers
   the first opportunity to exclude undefined values of delay, measure both RTD_fwd (on the SYN to SYN-ACK
   pair) and Section 5 of
   [RFC6703] for background on RTD_rev (on the SYN-ACK to ACK pair).  Label this analysis choice.

   See section 4.3.2 singleton
   of [RFC6049] for details RTDelay as RTDelay_HS (composed using the forward and reverse
   measurement pair).  RTDelay_HS SHALL be treated separately from other
   RTDelays on calculating this
   statistic, data-bearing packets and 4.3.3 of [RFC6049].

   Min their ACKs.  The time RTDelay_HS
   value of the result is expressed in units of seconds, MAY be used as a positive value sanity check on other Composed values of type decimal64 with fraction digits = 9
      (see section 9.3
   RTDelay.

   For payload bearing packets, the OP measures the time interval
   between observation of [RFC6020]) a packet with resolution of 0.000000001
      seconds (1.0 ns), Sequence Number s, and the
   corresponding ACK with lossless conversion to/from same Sequence number.  When the 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

10.4.2.3.  Max

   The maximum SHALL be calculated using payload is
   transferred from host A to host B, the conditional distribution of
   all observed interval is RTD_fwd.

   Because many data transfers are unidirectional (say, in the Forward
   direction from host A to host B), it is necessary to use pure ACK
   packets with a finite value of Round-trip delay (undefined delays
   are excluded), a single Timestamp (TSval) and their Timestamp value as follows:

   See section 4.1 echo to
   perform a RTD_rev measurement.  The time interval between observation
   of [RFC3393] for details on the conditional
   distribution ACK from B to exclude undefined values of delay, A, and the corresponding packet with Timestamp
   echo (TSecr) is the RTD_rev.

   Delay Measurement Filtering Heuristics:

   If Data payloads were transferred in both Forward and Reverse
   directions, then the Round-Trip Time Measurement Rule in Section 5 of
   [RFC6703] for background on this analysis choice.

   See section 4.3.2 4.1
   of [RFC6049] for [RFC7323] could be applied.  This rule essentially excludes any
   measurement using a closely related method for
   calculating this statistic, and 4.3.3 packet unless it makes progress in the transfer
   (advances the left edge of [RFC6049].  The formula the send window, consistent
   with[Strowes]).

   A different heuristic from [Trammell-14] is
   as follows:

            Max = (FiniteDelay [j])

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

   Max  The is larger than previously observed values.  This would tend to
   exclude Reverse measurements taken when the Application has no data
   ready to send, because considerable time value could be added to RTD_rev
   from this source of error.

   Note that the result above Heuristic assumes that host A is expressed in units of seconds,
      as sending data.
   Host A expecting 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]

10.4.3.  Metric Units

   <insert units for download would mean that this heuristic should be
   applied to RTD_fwd.

   The statistic calculations to summarize the measured results, delay (RTDelay) SHALL be
   performed on the conditional distribution, conditioned on successful
   Forward and Reverse measurements which follow the reference
   specification>.

   The <statistic> of Round-trip Delay is expressed in seconds, where
   <statistic> is one of:

   o  Mean

   o  Min

   o  Max Heuristics.

   Method for Inferring Loss:

   The Round-trip Delay OP tracks sequence numbers and stores gaps for each direction of
   transmission, as well as the Hand Shake is expressed next-expected sequence number as in seconds.

   The Round-trip
   [Trammell-14] and [RFC4737].  Loss Count is expressed as inferred from Out-of-order
   segments and Duplicate segments.

   Loss Measurement Filtering Heuristics:

   [Trammell-14] adds a number window of 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 evaluation based on the ground-truth.

10.5.  Administrative items

10.5.1.  Status

   <current or deprecated>

10.5.2.  Requestor (keep?)

   name or RFC, etc.

10.5.3.  Revision

   1.0

10.5.4.  Revision Date

   YYYY-MM-DD

10.6.  Comments and Remarks

   Additional (Informational) details for this entry

11.  ver08 BLANK Registry Entry

   This section gives an initial registry entry for ....

11.1.  Summary

   This category includes multiple indexes RTDelay.

   Distinguish Re-ordered from OOO due to loss, because sequence number
   gap is filled during the registry entries, the
   element ID and metric name.

11.1.1.  ID (Identifier)

   <insert numeric identifier, an integer>

11.1.2.  Name

   <insert name same RTDelay window.  Segments detected as
   re-ordered according to metric naming convention>

11.1.3.  URIs

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

   URL:

11.1.4.  Description

   TBD.

11.1.5.  Reference

   <reference [RFC4737] MUST reduce the Loss Count inferred
   from Out-of-order segments.

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

   Sources of Error:

   The principal source of RTDelay error is the host processing time to
   return a packet that defines the RFC termination of spec a time interval.  The
   heuristics above intend to mitigate these errors by excluding
   measurements where the registry entry host processing time is defined>

11.1.6.  Change Controller

   <org a significant part of
   RTD_fwd or person >

11.1.7.  Version (of Registry Format)

   <currently 1.0>

11.2.  Metric Definition RTD_rev.

   A key source of RTLoss error is observation loss, described in
   section 3 of [Trammell-14].

10.3.2.  Packet Stream Generation

   This category includes columns to prompt section gives the entry of all necessary details related to of the metric definition, including packet traffic which is the RFC reference
   and values of input factors,
   basis for measurement.  In IPPM metrics, this is called fixed parameters.

11.2.1.  Reference Definition

   <Full bibliographic reference to an immutable doc.>

   <specific section reference and additional clarifications, if needed>

11.2.2.  Fixed Parameters

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

11.3.  Method of Measurement

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

11.3.1.  Reference Method

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

11.3.2.  Packet Stream Generation

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

11.3.3. stream
   parameters.

   NA

10.3.3.  Traffic Filtering (observation) Details

   <insert the

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

11.3.4.
   present).

   The Fixed Parameters above give a portion of the 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

   This metric requires a complete sample of all packets that qualify
   according to the Traffic Filter criteria.

10.3.5.  Run-time Parameters and Data Format

   Run-time Parameters are input factors that must be determined,
   configured into the
   filter>

11.3.5.  Run-time Parameters and Data Format

   <list of run-time parameters, measurement system, and any reference(s)>.

11.3.6.  Roles

   <lists the names of reported with the different roles from results
   for the measurement method>

11.4.  Output

   This category specifies all details of context to be complete.

   Src  the Output IP address of measurements
   using the metric.

11.4.1.  Type

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

11.4.2.  Reference Definition

   <pointer to section/spec where output type/format is defined>

11.4.3.  Metric Units

   <insert units ipv6-address-no-zone value for
      IPv6, see Section 4 of [RFC6991])

   Dst  the measured results, and IP address of the reference
   specification>.

11.4.4.  Calibration

   <describe host in the error calibration, host B (format ipv4-address-
      no-zone value for IPv4, or ipv6-address-no-zone value for IPv6,
      see section 4 of [RFC6991])

   T0 a way to indicate that time, the results
   were collected in a calibration mode start of operation, and a way to
   report internal status metrics related to calibration, such measurement interval, (format "date-and-
      time" as time
   offset>

11.5.  Administrative items

11.5.1.  Status

   <current or deprecated>

11.5.2.  Requestor

   <name of individual or Internet Draft, etc.>

11.5.3.  Revision

   1.0

11.5.4.  Revision Date

   YYYY-MM-DD

11.6.  Comments and Remarks

   Additional (Informational) details for this entry

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.

12.1.  Registry Indexes

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

12.1.1.  Identifier

   An integer having enough digits to uniquely identify each entry specified in
   the Registry.

12.1.2.  Name

   A metric naming convention 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 Td is TBD.

12.1.3.  URI

   Prefix urn:ietf:metrics:param:<name>

12.1.4.  Status

   current

12.1.5.  Requestor

   Alcelip Mornuley

12.1.6.  Revision

   1.0

12.1.7.  Revision Date

   2014-07-04

12.1.8.  Description

   TBD.

12.1.9.  Reference Specification(s)

   [RFC3611][RFC4566][RFC6776][RFC6792][RFC7003]

12.2.  Metric Definition

   This category includes columns to prompt be interpreted as the entry Duration of all necessary
   details related to the metric definition, including measurement
      interval.  The start time is controlled through other means.

   Td Optionally, the RFC reference
   and values end of input factors, called fixed parameters. a measurement interval, (format "date-and-
      time" as specified in Section 3.2 5.6 of
   [RFC7003] provides the reference information for this category.

12.2.1.  Reference Definition

   Packets Discarded in Bursts:

   The total number [RFC3339], see also Section 3
      of packets discarded during discard bursts. [RFC6991]), or the duration (see T0).  The
   measured value UTC Time Zone is unsigned value.  If
      required by Section 6.1 of [RFC2330].  Alternatively, the measured value exceeds
   0xFFFFFD, end of
      the value 0xFFFFFE MUST measurement interval MAY be reported controlled by the measured
      connection, where the second pair of FIN and ACK packets exchanged
      between host A and B effectively ends the interval.

   TTL or Hop Limit  Set at desired value.

10.3.6.  Roles

   host A  launches the SYN packet to indicate open the connection, and
      synonymous with an over-
   range measurement.  If IP address.

   host B  replies with the measurement is unavailable, SYN-ACK packet to open the value
   0xFFFFFF MUST be reported.

12.2.2.  Fixed Parameters

   Fixed Parameters are input factors that must be determined connection, and
   embedded in
      synonymous with an IP address.

10.4.  Output

   This category specifies all details of the measurement system for use when needed.  The values Output of these parameters is specified measurements
   using the metric.

10.4.1.  Type

   See subsection titles in Reference Definition for RTDelay Types.

   For RTLoss -- the Registry.

   Threshold: 8 bits, set to value = count of lost packets.

10.4.2.  Reference Definition

   For all output types ---

   T0 the start of a measurement interval, (format "date-and-time" as
      specified in Section 5.6 of [RFC3339], see also Section 3 packets. of
      [RFC6991]).  The Threshold UTC Time Zone is equivalent to Gmin in [RFC3611], i.e., required by Section 6.1 of
      [RFC2330].

   Tf the number end of
   successive packets that must not be discarded prior to and following a discard packet in order for this discarded packet to be regarded measurement interval, (format "date-and-time" as
   part of a gap.  Note that the Threshold is set in accordance with the
   Gmin calculation defined
      specified in Section 4.7.2 5.6 of [RFC3339], see also Section 3 of [RFC3611].

   Interval Metric flag: 2 bits, set to value 11=Cumulative Duration

   This field
      [RFC6991]).  The UTC Time Zone 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 required by Section 6.1 of
      [RFC2330].  The end of the most
   recent measurement interval duration between successive metrics
   reports.

   I=11: Cumulative Duration - MAY be controlled
      by the reported value applies to measured connection, where the
   accumulation period characteristic second pair of cumulative measurements.

   Senders MUST NOT use FIN and ACK
      packets exchanged between host A and B effectively ends the values I=00 or I=01.

12.3.  Method of Measurement

   This category includes columns for references to relevant sections
      interval.

   ...  ...

   For RTDelay_HS -- the Round trip delay of the RFC(s) and any supplemental information needed to ensure an
   unambiguous methods for implementations. Handshake.

   For RTLoss -- the Burst/Gap Discard
   Metric, it appears that the only guidance on methods of measurement
   is in Section 3.0 count of [RFC7003] and its supporting references.
   Relevant information is repeated below, although there appears to be
   no section titled "Method lost packets.

   For each <statistic>, one of Measurement" in [RFC7003].

12.3.1.  Reference Method

   Metrics in this block report on burst/gap discard in the stream
   arriving at following sub-sections apply:

10.4.2.1.  Mean

   The mean SHALL be calculated using the RTP system.  Measurements conditional distribution of these metrics are made
   at the receiving end
   all packets with a finite value of the RTP stream.  Instances Round-trip delay (undefined delays
   are excluded), a single value as follows:

   See section 4.1 of this metrics
   block use [RFC3393] for details on the synchronization source (SSRC) to refer conditional
   distribution to the separate
   auxiliary Measurement Information Block [RFC6776], which describes
   measurement periods in use (see [RFC6776], exclude undefined values of delay, and Section 4.2).

   This metrics block relies 5 of
   [RFC6703] for background on the measurement period in the
   Measurement Information Block indicating the span this analysis choice.

   See section 4.2.2 of the report.
   Senders MUST send [RFC6049] for details on calculating this block in the same compound RTCP packet as the
   Measurement Information Block.  Receivers MUST verify that
   statistic, and 4.2.3 of [RFC6049].

   Mean  The time value of the
   measurement period result is received expressed in the same compound RTCP packet units of seconds,
      as
   this metrics block.  If not, this metrics block MUST be discarded.

12.3.2.  Stream Type 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 Stream Parameters

   Since RTCP-XR Measurements are conducted on live RTP traffic, with lossless conversion to/from the
   complete description 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

10.4.2.2.  Min

   The minimum SHALL be calculated using the stream is contained in SDP messages that
   proceed the establishment conditional distribution of
   all packets with a compatible stream between two or more
   communicating hosts. finite value of Round-trip delay (undefined delays
   are excluded), a single value as follows:

   See Run-time Parameters, below.

12.3.3.  Output Type and Data Format

   The output type defines the type section 4.1 of result that [RFC3393] for details on the metric produces.

   o  Value: Packets Discarded in Bursts

   o  Data Format: 24 bits

   o  Reference: conditional
   distribution to exclude undefined values of delay, and Section 3.2 5 of [RFC7003]

12.3.4.  Metric Units
   [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 measured results are apparently time value of the result is expressed in packets, although
   there is no units of seconds,
      as a positive value of type decimal64 with fraction digits = 9
      (see section 9.3 of [RFC7003] titled "Metric Units".

12.3.5.  Run-time Parameters and Data Format

   Run-Time Parameters are input factors that must be determined,
   configured into the measurement system, [RFC6020]) with resolution of 0.000000001
      seconds (1.0 ns), and reported with lossless conversion to/from the results
   for the context to 64-bit
      NTP timestamp as per section 6 of RFC [RFC5905]

10.4.2.3.  Max

   The maximum SHALL be complete.  However, calculated using the values conditional distribution of these
   parameters is not specified in the Registry, rather these parameters
   all packets with a finite value of Round-trip delay (undefined delays
   are listed excluded), a single value as an aid to follows:

   See section 4.1 of [RFC3393] for details on the measurement system implementor or user
   (they must be left as variables, conditional
   distribution to exclude undefined values of delay, and supplied Section 5 of
   [RFC6703] for background on execution).

   The Data Format this analysis choice.

   See section 4.3.2 of each Run-time Parameter SHALL be specified in [RFC6049] for a closely related method for
   calculating this
   column, to simplify the control statistic, and implementation 4.3.3 of measurement
   devices.

   SSRC [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 Source: 32 bits As defined the result is expressed in Section 4.1 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]

10.4.3.  Metric Units

   The <statistic> of [RFC3611].

   SDP Parameters: As defined Round-trip Delay is expressed 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 seconds, where
   <statistic> is 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:

   o  Mean

   o  Min

   o  Max

   The Round-trip Delay of contacts)

   p=* (zero or more phone the Hand Shake is expressed in seconds.

   The Round-trip Loss Count is expressed as a 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 packets.

10.4.4.  Calibration

   Passive measurements at an "m=" line;
   see below)

   m= (media name and transport address)

   i=* (media title or information field)
   c=* (connection information -- optional if included OP could be calibrated against an active
   measurement (with loss emulation) at session level)

   b=* (zero or more bandwidth information lines)

   k=* (encryption key)

   a=* (zero host A or more media attribute lines -- overriding B, where 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 active
   measurement represents 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

12.4. ground-truth.

10.5.  Administrative items

10.5.1.  Status

   Current

10.5.2.  Requestor

   This RFC

10.5.3.  Revision

   1.0

10.5.4.  Revision Date

   YYYY-MM-DD

10.6.  Comments and Remarks

   TBD.

13.  Revision History

   This section may be removed for publication.  It contains overview
   information on 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.

   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.

   None.

11.  Security Considerations

   These registry entries represent no known security implications for Internet
   Security.  Each referenced Metric contains a Security Considerations
   section.

15.

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

16.

13.  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,
   Yaakov Stein, 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.

17.

14.  References

17.1.

14.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, <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,
              <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,
              <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, <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,
              <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, <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,
              <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,
              <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,
              <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,
              <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,
              <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,
              <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,
              <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,
              <https://www.rfc-editor.org/info/rfc6049>.

   [RFC6673]  Morton, A., "Round-Trip Packet Loss Metrics", RFC 6673,
              DOI 10.17487/RFC6673, August 2012,
              <https://www.rfc-editor.org/info/rfc6673>.

   [RFC6991]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              RFC 6991, DOI 10.17487/RFC6991, July 2013,
              <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, <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, <https://www.rfc-editor.org/info/rfc7680>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

17.2.

14.2.  Informative References

   [RFC1242]  Bradner, S., "Benchmarking Terminology for Network
              Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242,
              July 1991, <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,
              <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, <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, <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,
              <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,
              <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, <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,
              <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,
              <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,
              <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,
              <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,
              <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, <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,
              <https://www.rfc-editor.org/info/rfc7594>.

   [Strowes]  Strowes, S., "Passively Measuring TCP Round Trip Times,
              Communications of the ACM, Vol. 56 No. 10, Pages 57-64",
              September 2013.

   [Trammell-14]
              Trammell, B., "Inline Data Integrity Signals for Passive
              Measurement, TMA 2014
              https://trammell.ch/pdf/qof-tma14.pdf", 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