<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="peformandce-metrics.xsl"?>
<?xml-model href="performance-metrics.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="performance-metrics">
  <title>Performance Metrics</title>
  <created>2020-03-19</created>
  <updated>2026-04-02</updated>
    
  <registry id="performance-metrics-registry">
  <title>Performance Metrics Registry</title>
  <xref type="rfc" data="rfc8911"/>
  <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
  <note>Summary category shown. Complete registry entries available in the URIs of each row.</note>
    <record date="2020-03-19" updated="2021-11-17">
      <id>0</id>
      <name>Reserved</name>
      <file type="template"/>
      <description/>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version/>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>1</id>
      <name>RTDelay_Active_IP-UDP-Periodic_RFC8912sec4_Seconds_95Percentile</name>
      <file type="template">RTDelay_Active_IP-UDP-Periodic_RFC8912sec4_Seconds_95Percentile</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (which are the two measurement points).
        The output is the round-trip delay for all successfully exchanged
        packets expressed as the 95th percentile of their conditional delay
        distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2022-01-27">
      <id>2</id>
      <name>RTLoss_Active_IP-UDP-Periodic_RFC8912sec4_Percent_LossRatio</name>
      <file type="template">RTLoss_Active_IP-UDP-Periodic_RFC8912sec4_Percent_LossRatio</file>
      <description>This metric assesses the loss ratio of a stream of packets
        exchanged between two hosts (which are the two measurement points).
        The output is the round-trip loss ratio for all successfully
        exchanged packets expressed as a percentage.</description>
      <xref type="rfc" data="rfc8912"/>
      <xref type="rfc-errata" data="6758"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>3</id>
      <name>OWPDV_Active_IP-UDP-Periodic_RFC8912sec5_Seconds_95Percentile</name>
      <file type="template">OWPDV_Active_IP-UDP-Periodic_RFC8912sec5_Seconds_95Percentile</file>
      <description>This metric assesses packet delay variation with respect to the minimum
        delay observed on the periodic stream. The output is expressed as
        the 95th percentile of the packet delay variation distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>4</id>
      <name>RTDNS_Active_IP-UDP-Poisson_RFC8912sec6_Seconds_Raw</name>
      <file type="template">RTDNS_Active_IP-UDP-Poisson_RFC8912sec6_Seconds_Raw</file>
      <description>This is a metric for DNS Response performance from a network user's
        perspective, for a specific named resource.  The metric can be
        measured repeatedly using different resource names.  This metric assesses the response time, the interval from the
        query transmission to the response.</description>
        <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
    <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>5</id>
      <name>RLDNS_Active_IP-UDP-Poisson_RFC8912sec6_Logical_Raw</name>
      <file type="template">RLDNS_Active_IP-UDP-Poisson_RFC8912sec6_Logical_Raw</file>
      <description>This is a metric for DNS Response performance from a network user's
        perspective, for a specific named resource.  The metric can be
        measured repeatedly using different resource names. This metric indicates that the response was deemed lost.  In
        other words, the response time exceeded the maximum waiting time.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>6</id>
      <name>OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_95Percentile</name>
      <file type="template">OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_95Percentile</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        95Percentile of one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>7</id>
      <name>OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Mean</name>
      <file type="template">OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Mean</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Mean of one-way delay for all successfully exchanged packets
        based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>8</id>
      <name>OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Min</name>
      <file type="template">OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Min</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Min of one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>9</id>
      <name>OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Max</name>
      <file type="template">OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_Max</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Max of one-way delay for all successfully exchanged packets
        based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>10</id>
      <name>OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_StdDev</name>
      <file type="template">OWDelay_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Seconds_StdDev</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        StdDev of one-way delay for all successfully exchanged packets
        based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2022-01-27">
      <id>11</id>
      <name>OWLoss_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Percent_LossRatio</name>
      <file type="template">OWLoss_Active_IP-UDP-Poisson-Payload250B_RFC8912sec7_Percent_LossRatio</file>
      <description>This metric assesses the loss ratio of a stream of packets
        exchanged between two hosts (which are the two measurement points).
        The output is the one-way loss ratio for all transmitted
        packets expressed as a percentage.</description>
      <xref type="rfc" data="rfc8912"/>
      <xref type="rfc-errata" data="6758"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>12</id>
      <name>OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_95Percentile</name>
      <file type="template">OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_95Percentile</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        95Percentile one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>13</id>
      <name>OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Mean</name>
      <file type="template">OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Mean</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Mean one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>14</id>
      <name>OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Min</name>
      <file type="template">OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Min</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Min one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>15</id>
      <name>OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Max</name>
      <file type="template">OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_Max</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        Max one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>16</id>
      <name>OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_StdDev</name>
      <file type="template">OWDelay_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Seconds_StdDev</file>
      <description>This metric assesses the delay of a stream of packets
        exchanged between two hosts (or measurement points) and reports the
        StdDev one-way delay for all successfully exchanged packets
          based on their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2022-01-27">
      <id>17</id>
      <name>OWLoss_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Percent_LossRatio</name>
      <file type="template">OWLoss_Active_IP-UDP-Periodic20m-Payload142B_RFC8912sec8_Percent_LossRatio</file>
      <description>This metric assesses the loss ratio of a stream of packets
        exchanged between two hosts (which are the two measurement points).
        The output is the one-way loss ratio for all transmitted
        packets expressed as a percentage.</description>
      <xref type="rfc" data="rfc8912"/>
      <xref type="rfc-errata" data="6758"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>18</id>
      <name>RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Mean</name>
      <file type="template">RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Mean</file>
      <description>This metric assesses the delay of a stream of ICMP packets 
        exchanged between two hosts (which are the two measurement points). 
        The output is the round-trip delay for all successfully exchanged packets 
        expressed as the Mean of their conditional delay distribution.
      </description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>19</id>
      <name>RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Min</name>
      <file type="template">RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Min</file>
      <description>This metric assesses the delay of a stream of ICMP packets 
        exchanged between two hosts (which are the two measurement points). 
        The output is the round-trip delay for all successfully exchanged packets 
        expressed as the Min of their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2021-11-17">
      <id>20</id>
      <name>RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Max</name>
      <file type="template">RTDelay_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Seconds_Max</file>
      <description>This metric assesses the delay of a stream of ICMP packets 
        exchanged between two hosts (which are the two measurement points). 
        The output is the round-trip delay for all successfully exchanged packets 
        expressed as the Max of their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2020-03-19" updated="2022-01-27">
      <id>21</id>
      <name>RTLoss_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Percent_LossRatio</name>
      <file type="template">RTLoss_Active_IP-ICMP-SendOnRcv_RFC8912sec9_Percent_LossRatio</file>
      <description>This metric assesses the loss ratio of a stream of ICMP
        packets exchanged between two hosts (which are the two measurement
        points). The output is the round-trip loss ratio for all
        transmitted packets expressed as a percentage.</description>
      <xref type="rfc" data="rfc8912"/>
      <xref type="rfc-errata" data="6758"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>   
    <record date="2020-03-19" updated="2021-11-17">
      <id>22</id>
      <name>RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Mean</name>
      <file type="template">RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Mean</file>
      <description>This metric assesses the round-trip delay of TCP packets 
        constituting a single connection, exchanged between two hosts. We consider 
        the measurement of round-trip delay based on a single Observation Point (OP) 
        [RFC7011] somewhere in the network. The output is the round-trip delay for 
        all successfully exchanged packets expressed as the Mean of their conditional 
        delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record> 
    <record date="2020-03-19" updated="2021-11-17">
      <id>23</id>
      <name>RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Min</name>
      <file type="template">RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Min</file>
      <description>This metric assesses the round-trip delay of TCP packets
        constituting a single connection, exchanged between two hosts.  We
        consider the measurement of round-trip delay based on a single
        Observation Point (OP) [RFC7011] somewhere in the network.  The output is
        the round-trip delay for all successfully exchanged packets expressed
        as the Min of their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record> 
    <record date="2020-03-19" updated="2021-11-17">
      <id>24</id>
      <name>RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Max</name>
      <file type="template">RTDelay_Passive_IP-TCP_RFC8912sec10_Seconds_Max</file>
      <description>This metric assesses the round-trip delay of TCP packets
        constituting a single connection, exchanged between two hosts.  We
        consider the measurement of round-trip delay based on a single
        Observation Point (OP) [RFC7011] somewhere in the network.  The output is
        the round-trip delay for all successfully exchanged packets expressed
        as the Max of their conditional delay distribution.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record> 
    <record date="2020-03-19" updated="2021-11-17">
      <id>25</id>
      <name>RTDelay_Passive_IP-TCP-HS_RFC8912sec10_Seconds_Singleton</name>
      <file type="template">RTDelay_Passive_IP-TCP-HS_RFC8912sec10_Seconds_Singleton</file>
      <description> RTDelay Singleton: This metric assesses the round-trip delay 
        of TCP packets initiating a single connection (or 3-way handshake), 
        exchanged between two hosts.  We consider the measurement of round-trip 
        delay based on a single Observation Point (OP) [RFC7011] somewhere in the 
        network.  The output is a single measurement of Round-trip delay, or Singleton.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record> 
    <record date="2020-03-19" updated="2021-11-17">
      <id>26</id>
      <name>RTLoss_Passive_IP-TCP_RFC8912sec10_Packet_Count</name>
      <file type="template">RTLoss_Passive_IP-TCP_RFC8912sec10_Packet_Count</file>
      <description>This metric assesses the estimated loss count for TCP packets
        constituting a single connection, exchanged between two hosts.  We
        consider the measurement of round-trip delay based on a single
        Observation Point (OP) [RFC7011] somewhere in the network.  The output is
        the estimated loss count for the measurement interval.</description>
      <xref type="rfc" data="rfc8912"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2026-04-02">
      <id>27</id>
      <name>OWDelay_HybridType1_IP_RFC9951_Seconds_Mean</name>
      <file type="template">OWDelay_HybridType1_IP_RFC9951_Seconds_Mean</file>
      <description>This metric assesses the mean of one-way delays of all 
        successfully forwarded IP packets constituting a single Flow. The 
        measurement of one-sway delay is based on a single Observation Point 
        <xref type="rfc" data="rfc7011"/> somewhere in the network.</description>
      <xref type="draft" data="RFC-ietf-opsawg-ipfix-on-path-telemetry-23"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2026-04-02">
      <id>28</id>
      <name>OWDelay_HybridType1_IP_RFC9951_Seconds_Min</name>
      <file type="template">OWDelay_HybridType1_IP_RFC9951_Seconds_Min</file>
      <description>This metric assesses the minimum of one-way delays of all
      successfully forwarded IP packets constituting a single Flow.  The
      measurement of one-way delay is based on a single Observation
      Point <xref type="rfc" data="rfc7011"/> somewhere in the network.</description>
      <xref type="draft" data="RFC-ietf-opsawg-ipfix-on-path-telemetry-23"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2026-04-02">
      <id>29</id>
      <name>OWDelay_HybridType1_IP_RFC9951_Seconds_Max</name>
      <file type="template">OWDelay_HybridType1_IP_RFC9951_Seconds_Max</file>
      <description>This metric assesses the maximum of one-way delays of all
      successfully forwarded IP packets constituting a single Flow.  The
      measurement of one-way delay is based on a single Observation
      Point <xref type="rfc" data="rfc7011"/> somewhere in the network.</description>
      <xref type="draft" data="RFC-ietf-opsawg-ipfix-on-path-telemetry-23"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>
    <record date="2026-04-02">
      <id>30</id>
      <name>OWDelay_HybridType1_IP_RFC9951_Seconds_Sum</name>
      <file type="template">OWDelay_HybridType1_IP_RFC9951_Seconds_Sum</file>
      <description>This metric assesses the maximum of one-way delays of all
      successfully forwarded IP packets constituting a single Flow.  The
      measurement of one-way delay is based on a single Observation
      Point <xref type="rfc" data="rfc7011"/> somewhere in the network.</description>
      <xref type="draft" data="RFC-ietf-opsawg-ipfix-on-path-telemetry-23"/>
      <controller>IETF</controller>
      <version>1.0</version>
    </record>    
  </registry>
  
  <registry id="performance-metrics-metric-type">
    <title>Performance Metric Name Elements -  Metric Type</title>
    <xref type="rfc" data="rfc8911"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
   <record date="2020-03-19">
    <id>MetricType</id>
    <name>RTDelay</name>
    <description>Round-Trip Delay</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
   </record>
   <record date="2020-03-19">
    <id>MetricType</id>
    <name>RTDNS</name>
    <description>Response Time Domain Name Service</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
   </record>
   <record date="2020-03-19">
    <id>MetricType</id>
    <name>RLDNS</name>
    <description>Response Loss Domain Name Service</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
   </record>
   <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWDelay</name>
    <description>One-Way Delay</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
   </record>
   <record date="2020-03-19">
    <id>MetricType</id>
    <name>RTLoss</name>
    <description>Round-Trip Loss</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWLoss</name>
    <description>One-Way Loss</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
  <record date="2020-03-19" updated="2025-01-14">
    <id>MetricType</id>
    <name>OWPDV</name>
    <description>One-Way Packet Delay Variation</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWIPDV</name>
    <description>One-Way Inter-Packet Delay Variation</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWReorder</name>
    <description>One-Way Packet Reordering</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWDuplic</name>
    <description>One-Way Packet Duplication</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWBTC</name>
    <description>One-Way Bulk Transport Capacity</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>OWMBM</name>
    <description>One-Way Model-Based Metric</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>SPMonitor</name>
    <description>Single-Point Monitor</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>MetricType</id>
    <name>MPMonitor</name>
    <description>Multi-Point Monitor</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
</registry>

  <registry id="performance-metrics-method">
    <title>Performance Metric Name Elements -  Method</title>
    <xref type="rfc" data="rfc8911"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
    <record date="2020-03-19">
    <id>Method</id>
    <name>Active</name>
    <description>depends on a dedicated measurement packet stream and
      observations of the stream as described in [RFC7799]
    </description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Method</id>
    <name>Passive</name>
    <description>depends *solely* on observation of one or more
      existing packet streams as described in [RFC7799]
    </description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Method</id>
    <name>Hybrid Type 1</name>
    <description>Hybrid Type I obervations on one stream that combine both Active
     Methods and Passive Methods as described in [RFC7799]
    </description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Method</id>
    <name>Hybrid Type 2</name>
      <description>Hybrid Type II obervations on two or more streams that combine
        both Active Methods and Passive Methods as described in [RFC7799]
      </description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Method</id>
    <name>Spatial</name>
      <description>spatial metric as described in [RFC5644]</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
</registry> 

  <registry id="performance-metrics-subtypemethod">
    <title>Performance Metric Name Elements - SubTypeMethod</title>
    <xref type="rfc" data="rfc8911"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>ICMP</name>
      <description>Internet Control Message Protocol</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>IP</name>
      <description>Internet Protocol</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>  
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>DSCPxx</name>
      <description>where xx is replaced by a Diffserv code point</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>UDP</name>
      <description>User Datagram Protocol</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>TCP</name>
      <description>Transport Control Protocol</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>QUIC</name>
      <description>QUIC transport protocol</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>HS</name>
      <description>Hand-Shake, such as TCP's 3-way HS</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>Poisson</name>
      <description>packet generation using Poisson distribution</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>Periodic</name>
      <description>periodic packet generation</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>SendOnRcv</name>
      <description>Sender keeps one packet in transit by sending when
        previous packet arrives</description>
        <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>  
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>PayloadxxxxB</name>
      <description>where xxxx is replaced by an integer, the number
        of octets or 8-bit Bytes in the Payload</description>
        <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>SustaninedBurst</name>
      <description>capacity test, worst case</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>SubTypeMethod</id>
    <name>StandingQueue</name>
      <description>test of bottleneck queue behavior</description>
      <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
</registry>

  <registry id="performance-metrics-spec">
    <title>Performance Metric Name Elements - Spec</title>
    <xref type="rfc" data="rfc8911"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
    <note>Spec contains an immutable document identifier combined with a document section identifier for the specifying document.
     See Section 7.1.2 of [RFC8911].</note>
    <record date="2020-03-19">
      <id>Spec</id>
      <xref type="rfc" data="rfc8911"/>
    </record>
  </registry>  

  <registry id="performance-metrics-units">
    <title>Performance Metric Name Elements - Units</title>
    <xref type="rfc" data="rfc8911"/>
    <registration_rule>Specification Required</registration_rule>
    <expert>Greg Mirsky, Michael Scharf</expert>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Seconds</name>
    <description/>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Ratio</name>
    <description>unitless</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Percent</name>
    <description>value multiplied by 100%</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Logical</name>
    <description>1 or 0</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Packets</name>
    <description/>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>BPS</name>
    <description>bits per second</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>PPS</name>
    <description>packets per second</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>EventTotal</name>
    <description>for unitless counts</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Multiple</name>
    <description>more than one type of unit</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Enumerated</name>
    <description>a list of outcomes</description>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
    <record date="2020-03-19">
    <id>Units</id>
    <name>Unitless</name>
    <description/>
    <xref type="rfc" data="rfc8911"/>
    <controller>IETF</controller>
  </record>
</registry>

  <registry id="performance-metrics-output">
  <title>Performance Metric Name Elements - Output </title>
  <xref type="rfc" data="rfc8911"/>
  <registration_rule>Specification Required</registration_rule>
  <expert>Greg Mirsky, Michael Scharf</expert>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Singleton</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Raw</name>
  <description>multiple singletons</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Count</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Minimum</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Maximum</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Median</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Mean</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>95Percentile</name>
  <description>95th Percentile</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>99Percentile</name>
  <description>99th Percentile</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>StdDev</name>
  <description>standard deviation</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>Variance</name>
  <description/>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>PFI</name>
  <description>pass, fail, inconclusive</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>FlowRecords</name>
  <description>descriptions of flows observed</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  <record date="2020-03-19">
  <id>Output</id>
  <name>LossRatio</name>
  <description>lost packets to total packets, &lt;=1</description>
  <xref type="rfc" data="rfc8911"/>
  <controller>IETF</controller>
  </record>
  </registry>
  
  <people/>
</registry>
