File: rfc8911.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (3704 lines) | stat: -rw-r--r-- 203,604 bytes
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8911: Registry for Performance Metrics</title>
<meta content="Marcelo Bagnulo" name="author">
<meta content="Benoit Claise" name="author">
<meta content="Philip Eardley" name="author">
<meta content="Al Morton" name="author">
<meta content="Aamer Akhter" name="author">
<meta content="
       This document defines the format for the IANA Registry of Performance Metrics.
      This document also gives a set of guidelines for Registered
      Performance Metric requesters and reviewers. 
    " name="description">
<meta content="xml2rfc 3.11.1" name="generator">
<meta content="IPPM" name="keyword">
<meta content="Loss" name="keyword">
<meta content="Delay" name="keyword">
<meta content="8911" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.11.1
    Python 3.6.13
    appdirs 1.4.4
    ConfigArgParse 1.4.1
    google-i18n-address 2.4.0
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.3
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.15.1
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.4.1
    requests 2.24.0
    setuptools 40.5.0
    six 1.14.0
    WeasyPrint 52.5
-->
<link href="rfc8911.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.ulBare, li.ulBare {
  margin-left: 0em !important;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
/* Fix PDF info block run off issue */
@media print {
  #identifiers dd {
    float: none;
  }
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: auto;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8911" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-ippm-metric-registry-24" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 8911</td>
<td class="center">Registry for Performance Metrics</td>
<td class="right">November 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Bagnulo, et al.</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8911" class="eref">8911</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-11" class="published">November 2021</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">M. Bagnulo</div>
<div class="org">UC3M</div>
</div>
<div class="author">
      <div class="author-name">B. Claise</div>
<div class="org">Huawei</div>
</div>
<div class="author">
      <div class="author-name">P. Eardley</div>
<div class="org">BT</div>
</div>
<div class="author">
      <div class="author-name">A. Morton</div>
<div class="org">AT&amp;T Labs</div>
</div>
<div class="author">
      <div class="author-name">A. Akhter</div>
<div class="org">Consultant</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8911</h1>
<h1 id="title">Registry for Performance Metrics</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document defines the format for the IANA Registry of Performance Metrics.
      This document also gives a set of guidelines for Registered
      Performance Metric requesters and reviewers.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc8911">https://www.rfc-editor.org/info/rfc8911</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-scope" class="xref">Scope</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-motivations-for-the-perform" class="xref">Motivations for the Performance Metrics Registry</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-interoperability" class="xref">Interoperability</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-single-point-of-reference-f" class="xref">Single Point of Reference for Performance Metrics</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
                <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-side-benefits" class="xref">Side Benefits</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-criteria-for-performance-me" class="xref">Criteria for Performance Metrics Registration</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-performance-metrics-registr" class="xref">Performance Metrics Registry: Prior Attempt</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
                <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-why-this-attempt-should-suc" class="xref">Why This Attempt Should Succeed</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-definition-of-the-performan" class="xref">Definition of the Performance Metrics Registry</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-summary-category" class="xref">Summary Category</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.1">
                    <p id="section-toc.1-1.7.2.1.2.1.1"><a href="#section-7.1.1" class="xref">7.1.1</a>.  <a href="#name-identifier" class="xref">Identifier</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.2">
                    <p id="section-toc.1-1.7.2.1.2.2.1"><a href="#section-7.1.2" class="xref">7.1.2</a>.  <a href="#name-name" class="xref">Name</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.3">
                    <p id="section-toc.1-1.7.2.1.2.3.1"><a href="#section-7.1.3" class="xref">7.1.3</a>.  <a href="#name-uri" class="xref">URI</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.4">
                    <p id="section-toc.1-1.7.2.1.2.4.1"><a href="#section-7.1.4" class="xref">7.1.4</a>.  <a href="#name-description" class="xref">Description</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.5">
                    <p id="section-toc.1-1.7.2.1.2.5.1"><a href="#section-7.1.5" class="xref">7.1.5</a>.  <a href="#name-reference" class="xref">Reference</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.6">
                    <p id="section-toc.1-1.7.2.1.2.6.1"><a href="#section-7.1.6" class="xref">7.1.6</a>.  <a href="#name-change-controller" class="xref">Change Controller</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.7">
                    <p id="section-toc.1-1.7.2.1.2.7.1"><a href="#section-7.1.7" class="xref">7.1.7</a>.  <a href="#name-version-of-registry-format" class="xref">Version (of Registry Format)</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-metric-definition-category" class="xref">Metric Definition Category</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.1">
                    <p id="section-toc.1-1.7.2.2.2.1.1"><a href="#section-7.2.1" class="xref">7.2.1</a>.  <a href="#name-reference-definition" class="xref">Reference Definition</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.2">
                    <p id="section-toc.1-1.7.2.2.2.2.1"><a href="#section-7.2.2" class="xref">7.2.2</a>.  <a href="#name-fixed-parameters" class="xref">Fixed Parameters</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3">
                <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-method-of-measurement-categ" class="xref">Method of Measurement Category</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.1">
                    <p id="section-toc.1-1.7.2.3.2.1.1"><a href="#section-7.3.1" class="xref">7.3.1</a>.  <a href="#name-reference-method" class="xref">Reference Method</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.2">
                    <p id="section-toc.1-1.7.2.3.2.2.1"><a href="#section-7.3.2" class="xref">7.3.2</a>.  <a href="#name-packet-stream-generation" class="xref">Packet Stream Generation</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.3">
                    <p id="section-toc.1-1.7.2.3.2.3.1"><a href="#section-7.3.3" class="xref">7.3.3</a>.  <a href="#name-traffic-filter" class="xref">Traffic Filter</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.4">
                    <p id="section-toc.1-1.7.2.3.2.4.1"><a href="#section-7.3.4" class="xref">7.3.4</a>.  <a href="#name-sampling-distribution" class="xref">Sampling Distribution</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.5">
                    <p id="section-toc.1-1.7.2.3.2.5.1"><a href="#section-7.3.5" class="xref">7.3.5</a>.  <a href="#name-runtime-parameters" class="xref">Runtime Parameters</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3.2.6">
                    <p id="section-toc.1-1.7.2.3.2.6.1"><a href="#section-7.3.6" class="xref">7.3.6</a>.  <a href="#name-role" class="xref">Role</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4">
                <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-output-category" class="xref">Output Category</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4.2.1">
                    <p id="section-toc.1-1.7.2.4.2.1.1"><a href="#section-7.4.1" class="xref">7.4.1</a>.  <a href="#name-type" class="xref">Type</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4.2.2">
                    <p id="section-toc.1-1.7.2.4.2.2.1"><a href="#section-7.4.2" class="xref">7.4.2</a>.  <a href="#name-reference-definition-2" class="xref">Reference Definition</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4.2.3">
                    <p id="section-toc.1-1.7.2.4.2.3.1"><a href="#section-7.4.3" class="xref">7.4.3</a>.  <a href="#name-metric-units" class="xref">Metric Units</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4.2.4">
                    <p id="section-toc.1-1.7.2.4.2.4.1"><a href="#section-7.4.4" class="xref">7.4.4</a>.  <a href="#name-calibration" class="xref">Calibration</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5">
                <p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>.  <a href="#name-administrative-information" class="xref">Administrative Information</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5.2.1">
                    <p id="section-toc.1-1.7.2.5.2.1.1"><a href="#section-7.5.1" class="xref">7.5.1</a>.  <a href="#name-status" class="xref">Status</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5.2.2">
                    <p id="section-toc.1-1.7.2.5.2.2.1"><a href="#section-7.5.2" class="xref">7.5.2</a>.  <a href="#name-requester" class="xref">Requester</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5.2.3">
                    <p id="section-toc.1-1.7.2.5.2.3.1"><a href="#section-7.5.3" class="xref">7.5.3</a>.  <a href="#name-revision" class="xref">Revision</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5.2.4">
                    <p id="section-toc.1-1.7.2.5.2.4.1"><a href="#section-7.5.4" class="xref">7.5.4</a>.  <a href="#name-revision-date" class="xref">Revision Date</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.6">
                <p id="section-toc.1-1.7.2.6.1"><a href="#section-7.6" class="xref">7.6</a>.  <a href="#name-comments-and-remarks" class="xref">Comments and Remarks</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-processes-for-managing-the-" class="xref">Processes for Managing the Performance Metrics Registry Group</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1">
                <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-adding-new-performance-metr" class="xref">Adding New Performance Metrics to the Performance Metrics Registry</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2">
                <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-backward-compatible-revisio" class="xref">Backward-Compatible Revision of Registered Performance Metrics</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3">
                <p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>.  <a href="#name-non-backward-compatible-dep" class="xref">Non-Backward-Compatible Deprecation of Registered Performance Metrics</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4">
                <p id="section-toc.1-1.8.2.4.1"><a href="#section-8.4" class="xref">8.4</a>.  <a href="#name-obsolete-registry-entries" class="xref">Obsolete Registry Entries</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.5">
                <p id="section-toc.1-1.8.2.5.1"><a href="#section-8.5" class="xref">8.5</a>.  <a href="#name-registry-format-version-and" class="xref">Registry Format Version and Future Changes/Extensions</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1">
                <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-registry-group" class="xref">Registry Group</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.2">
                <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-performance-metrics-name-el" class="xref">Performance Metrics Name Elements</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.3">
                <p id="section-toc.1-1.10.2.3.1"><a href="#section-10.3" class="xref">10.3</a>.  <a href="#name-new-performance-metrics-reg" class="xref">New Performance Metrics Registry</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-blank-registry-template" class="xref">Blank Registry Template</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1">
                <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-summary" class="xref">Summary</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.1">
                    <p id="section-toc.1-1.11.2.1.2.1.1"><a href="#section-11.1.1" class="xref">11.1.1</a>.  <a href="#name-id-identifier" class="xref">ID (Identifier)</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.2">
                    <p id="section-toc.1-1.11.2.1.2.2.1"><a href="#section-11.1.2" class="xref">11.1.2</a>.  <a href="#name-name-2" class="xref">Name</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.3">
                    <p id="section-toc.1-1.11.2.1.2.3.1"><a href="#section-11.1.3" class="xref">11.1.3</a>.  <a href="#name-uri-2" class="xref">URI</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.4">
                    <p id="section-toc.1-1.11.2.1.2.4.1"><a href="#section-11.1.4" class="xref">11.1.4</a>.  <a href="#name-description-2" class="xref">Description</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.5">
                    <p id="section-toc.1-1.11.2.1.2.5.1"><a href="#section-11.1.5" class="xref">11.1.5</a>.  <a href="#name-reference-2" class="xref">Reference</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.6">
                    <p id="section-toc.1-1.11.2.1.2.6.1"><a href="#section-11.1.6" class="xref">11.1.6</a>.  <a href="#name-change-controller-2" class="xref">Change Controller</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.1.2.7">
                    <p id="section-toc.1-1.11.2.1.2.7.1"><a href="#section-11.1.7" class="xref">11.1.7</a>.  <a href="#name-version-of-registry-format-2" class="xref">Version (of Registry Format)</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.2">
                <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-metric-definition" class="xref">Metric Definition</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.2.2.1">
                    <p id="section-toc.1-1.11.2.2.2.1.1"><a href="#section-11.2.1" class="xref">11.2.1</a>.  <a href="#name-reference-definition-3" class="xref">Reference Definition</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.2.2.2">
                    <p id="section-toc.1-1.11.2.2.2.2.1"><a href="#section-11.2.2" class="xref">11.2.2</a>.  <a href="#name-fixed-parameters-2" class="xref">Fixed Parameters</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3">
                <p id="section-toc.1-1.11.2.3.1"><a href="#section-11.3" class="xref">11.3</a>.  <a href="#name-method-of-measurement" class="xref">Method of Measurement</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.1">
                    <p id="section-toc.1-1.11.2.3.2.1.1"><a href="#section-11.3.1" class="xref">11.3.1</a>.  <a href="#name-reference-method-2" class="xref">Reference Method</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.2">
                    <p id="section-toc.1-1.11.2.3.2.2.1"><a href="#section-11.3.2" class="xref">11.3.2</a>.  <a href="#name-packet-stream-generation-2" class="xref">Packet Stream Generation</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.3">
                    <p id="section-toc.1-1.11.2.3.2.3.1"><a href="#section-11.3.3" class="xref">11.3.3</a>.  <a href="#name-traffic-filtering-observati" class="xref">Traffic Filtering (Observation) Details</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.4">
                    <p id="section-toc.1-1.11.2.3.2.4.1"><a href="#section-11.3.4" class="xref">11.3.4</a>.  <a href="#name-sampling-distribution-2" class="xref">Sampling Distribution</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.5">
                    <p id="section-toc.1-1.11.2.3.2.5.1"><a href="#section-11.3.5" class="xref">11.3.5</a>.  <a href="#name-runtime-parameters-and-data" class="xref">Runtime Parameters and Data Format</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.3.2.6">
                    <p id="section-toc.1-1.11.2.3.2.6.1"><a href="#section-11.3.6" class="xref">11.3.6</a>.  <a href="#name-roles" class="xref">Roles</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.4">
                <p id="section-toc.1-1.11.2.4.1"><a href="#section-11.4" class="xref">11.4</a>.  <a href="#name-output" class="xref">Output</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.4.2.1">
                    <p id="section-toc.1-1.11.2.4.2.1.1"><a href="#section-11.4.1" class="xref">11.4.1</a>.  <a href="#name-type-2" class="xref">Type</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.4.2.2">
                    <p id="section-toc.1-1.11.2.4.2.2.1"><a href="#section-11.4.2" class="xref">11.4.2</a>.  <a href="#name-reference-definition-4" class="xref">Reference Definition</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.4.2.3">
                    <p id="section-toc.1-1.11.2.4.2.3.1"><a href="#section-11.4.3" class="xref">11.4.3</a>.  <a href="#name-metric-units-2" class="xref">Metric Units</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.4.2.4">
                    <p id="section-toc.1-1.11.2.4.2.4.1"><a href="#section-11.4.4" class="xref">11.4.4</a>.  <a href="#name-calibration-2" class="xref">Calibration</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.5">
                <p id="section-toc.1-1.11.2.5.1"><a href="#section-11.5" class="xref">11.5</a>.  <a href="#name-administrative-items" class="xref">Administrative Items</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.5.2.1">
                    <p id="section-toc.1-1.11.2.5.2.1.1"><a href="#section-11.5.1" class="xref">11.5.1</a>.  <a href="#name-status-2" class="xref">Status</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.5.2.2">
                    <p id="section-toc.1-1.11.2.5.2.2.1"><a href="#section-11.5.2" class="xref">11.5.2</a>.  <a href="#name-requester-2" class="xref">Requester</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.5.2.3">
                    <p id="section-toc.1-1.11.2.5.2.3.1"><a href="#section-11.5.3" class="xref">11.5.3</a>.  <a href="#name-revision-2" class="xref">Revision</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.5.2.4">
                    <p id="section-toc.1-1.11.2.5.2.4.1"><a href="#section-11.5.4" class="xref">11.5.4</a>.  <a href="#name-revision-date-2" class="xref">Revision Date</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11.2.6">
                <p id="section-toc.1-1.11.2.6.1"><a href="#section-11.6" class="xref">11.6</a>.  <a href="#name-comments-and-remarks-2" class="xref">Comments and Remarks</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-references" class="xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.1">
                <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.2">
                <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
            <p id="section-toc.1-1.14.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">The IETF specifies and uses Performance Metrics of protocols and
      applications transported over its protocols. Performance Metrics are
      an important part of network operations using IETF protocols, and <span>[<a href="#RFC6390" class="xref">RFC6390</a>]</span> specifies guidelines for their development.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">The definition and use of Performance Metrics in the IETF have been
      fostered in various working groups (WGs). Most notably:<a href="#section-1-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1-3.1">The "IP Performance Metrics" (IPPM) WG is the WG primarily
          focusing on Performance Metrics definition at the IETF.<a href="#section-1-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-1-3.2">The "Benchmarking Methodology" WG (BMWG) defines many Performance
          Metrics for use in laboratory benchmarking of internetworking
          technologies.<a href="#section-1-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-1-3.3">The "Metric Blocks for use with RTCP's Extended Report Framework"
          (XRBLOCK) WG (concluded) specified many Performance Metrics related
          to "RTP Control Protocol Extended Reports (RTCP XR)" <span>[<a href="#RFC3611" class="xref">RFC3611</a>]</span>, which establishes a framework to allow new
          information to be conveyed in RTCP, supplementing the original
          report blocks defined in "RTP: A Transport Protocol for Real-Time
          Applications" <span>[<a href="#RFC3550" class="xref">RFC3550</a>]</span>.<a href="#section-1-3.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-1-3.4">The "IP Flow Information eXport" (IPFIX) WG (concluded) specified
          an Internet Assigned Numbers Authority (IANA) process for new
          Information Elements. Some Information Elements related to Performance
          Metrics are proposed on a regular basis.<a href="#section-1-3.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-1-3.5">The "Performance Metrics for Other Layers" (PMOL) WG (concluded)
          defined some Performance Metrics related to Session Initiation
          Protocol (SIP) voice quality <span>[<a href="#RFC6035" class="xref">RFC6035</a>]</span>.<a href="#section-1-3.5" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-1-4">It is expected that more Performance Metrics will be defined in the
      future -- not only IP-based metrics but also metrics that are
      protocol specific and application specific.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">Despite the importance of Performance Metrics, there are two related
      problems for the industry:<a href="#section-1-5" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1-6.1">First, ensuring that when one party requests that
      another party measure (or report or in some way act on) a particular
      Performance Metric, both parties have exactly the same
      understanding of what Performance Metric is being referred to.<a href="#section-1-6.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-1-6.2">Second,
      discovering which Performance Metrics have been specified, to avoid
      developing a new Performance Metric that is very similar but not quite
      interoperable.<a href="#section-1-6.2" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-1-7">These problems can be addressed by creating a Registry
      for Performance Metrics with the Internet Assigned Numbers Authority
      (IANA).   As such, this document defines the new IANA Registry for Performance
      Metrics.<a href="#section-1-7" class="pilcrow">¶</a></p>
<p id="section-1-8">Per this document, IANA has created and now maintains the Performance
      Metrics Registry, according to the maintenance procedures and the
      format defined in the sections below. The resulting
      Performance Metrics Registry is for use by the IETF and others. Although
      the Registry formatting specifications herein are primarily for Registry
      creation by IANA, any other organization that wishes to create a
      Performance Metrics Registry may use the same formatting specifications
      for their purposes. The authors make no guarantee of the Registry
      format's applicability to any possible set of Performance Metrics
      envisaged by other organizations, but we encourage others to apply it. In
      the remainder of this document, unless we explicitly say otherwise, we
      will refer to the IANA-maintained Performance Metrics Registry as simply
      the Performance Metrics Registry.<a href="#section-1-8" class="pilcrow">¶</a></p>
</section>
<section id="section-2">
      <h2 id="name-terminology">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
      </h2>
<p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
       "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>",
       "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>",
       "<span class="bcp14">SHOULD NOT</span>",
       "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
       "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document
       are to be interpreted as described in BCP 14
       <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only
       when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-2-2">
        <dt id="section-2-2.1">Performance Metric:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.2">A quantitative measure of performance, targeted to an IETF-specified
          protocol or targeted to an application transported over an
          IETF-specified protocol. Examples of Performance Metrics are the FTP
          response time for a complete file download, the DNS Response time to
          resolve the IP address(es), a database logging time, etc. This
          definition is consistent with the definition of a metric in <span>[<a href="#RFC2330" class="xref">RFC2330</a>]</span> and broader than the definition
          of a Performance Metric in <span>[<a href="#RFC6390" class="xref">RFC6390</a>]</span>.<a href="#section-2-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.3">Registered Performance Metric:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.4">A Performance Metric expressed as an entry in
          the Performance Metrics Registry, administered by IANA. Such a
          Performance Metric has met all of the Registry review criteria defined
          in this document in order to be included in the Registry.<a href="#section-2-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.5">Performance Metrics Registry:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.6">The IANA Registry
          containing Registered Performance Metrics.<a href="#section-2-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.7">Proprietary Registry:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.8">A set of metrics that are
          registered in a proprietary Registry, as opposed to the Performance
          Metrics Registry.<a href="#section-2-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.9">Performance Metrics Experts:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.10">A group of designated experts <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>
          selected by the IESG to validate the Performance Metrics before
          updating the Performance Metrics Registry. The Performance Metrics
          Experts work closely with IANA.<a href="#section-2-2.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.11">Parameter:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.12">An input factor defined as a
          variable in the definition of a Performance Metric. A Parameter is a
          numerical or other specified factor forming one of a set that
          defines a metric or sets the conditions of its operation. All
          Parameters must be known in order to make a measurement using a
          metric and interpret the results. There are two types of Parameters:
          Fixed and Runtime. For the Fixed Parameters, the value
          of the variable is specified in the Performance Metrics Registry
          Entry and different Fixed Parameter values results in different
          Registered Performance Metrics. For the Runtime Parameters, the
          value of the variable is defined when the Metric Measurement Method
          is executed and a given Registered Performance Metric supports
          multiple values for the Parameter. Although Runtime Parameters do
          not change the fundamental nature of the Performance Metric's
          definition, some have substantial influence on the network property
          being assessed and interpretation of the results.<a href="#section-2-2.12" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<aside id="section-2-3">
        <p id="section-2-3.1">Note: Consider the case of packet loss in the following two
              Active Measurement Method cases. The first case is packet loss
              as background loss where the Runtime Parameter set includes a
              very sparse Poisson stream and only characterizes the times
              when packets were lost. Actual user streams likely see much
              higher loss at these times, due to tail drop or radio errors.
              The second case is packet loss ratio as the complimentary
              probability of delivery ratio where
              the Runtime Parameter set includes a very dense, bursty stream,
              and characterizes the loss experienced by a stream that
              approximates a user stream. These are both "Loss metrics", but
              the difference in interpretation of the results is highly
              dependent on the Runtime Parameters (at least), to the extreme
              where we are actually using loss ratio to infer its complimentary
              probability: delivery ratio.<a href="#section-2-3.1" class="pilcrow">¶</a></p>
</aside>
<span class="break"></span><dl class="dlParallel" id="section-2-4">
        <dt id="section-2-4.1">Active Measurement Methods:</dt>
        <dd style="margin-left: 1.5em" id="section-2-4.2">Methods of Measurement
          conducted on traffic that serves only the purpose of measurement
          and is generated for that reason alone, and whose traffic
          characteristics are known a priori. The complete definition of
          Active Methods is specified in <span><a href="https://www.rfc-editor.org/rfc/rfc7799#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC7799" class="xref">RFC7799</a>]</span>. Examples of Active Measurement Methods are the
          Measurement Methods for the one-way delay metric defined in <span>[<a href="#RFC7679" class="xref">RFC7679</a>]</span> and the round-trip delay metric defined in <span>[<a href="#RFC2681" class="xref">RFC2681</a>]</span>.<a href="#section-2-4.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-4.3">Passive Measurement Methods:</dt>
        <dd style="margin-left: 1.5em" id="section-2-4.4">Methods of Measurement
          conducted on network traffic, generated by either (1) the end
          users or (2) network elements that would exist regardless of whether the
          measurement was being conducted or not. The complete definition of
          Passive Methods is specified in <span><a href="https://www.rfc-editor.org/rfc/rfc7799#section-3.6" class="relref">Section 3.6</a> of [<a href="#RFC7799" class="xref">RFC7799</a>]</span>. One characteristic of Passive Measurement
          Methods is that sensitive information may be observed and, as a
          consequence, stored in the measurement system.<a href="#section-2-4.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-4.5">Hybrid Measurement Methods:</dt>
        <dd style="margin-left: 1.5em" id="section-2-4.6">Methods of Measurement that use a combination of Active Methods and Passive
          Methods, to assess Active Metrics, Passive Metrics, or new metrics
          derived from the a priori knowledge and observations of the stream
          of interest. The complete definition of Hybrid Methods is specified
          in <span><a href="https://www.rfc-editor.org/rfc/rfc7799#section-3.8" class="relref">Section 3.8</a> of [<a href="#RFC7799" class="xref">RFC7799</a>]</span>.<a href="#section-2-4.6" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
<section id="section-3">
      <h2 id="name-scope">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-scope" class="section-name selfRef">Scope</a>
      </h2>
<p id="section-3-1">This document is intended for two different audiences:<a href="#section-3-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3-2">
        <li id="section-3-2.1">For those preparing a candidate Performance Metric, it provides
        criteria that the proposal <span class="bcp14">SHOULD</span> meet (see <a href="#metrics-criteria" class="xref">Section 5</a>). It also provides instructions for
        writing the text for each column of the candidate Performance Metric
        and the references required for the new Performance Metrics Registry
        Entry (up to and including the publication of one or more immutable
        documents such as an RFC) (see <a href="#columns" class="xref">Section 7</a>).<a href="#section-3-2.1" class="pilcrow">¶</a>
</li>
        <li id="section-3-2.2">For the appointed Performance Metrics Experts and for IANA
        personnel administering the new IANA Performance Metrics Registry, it
        defines a set of acceptance criteria against which a candidate
        Registered Performance Metric should be evaluated, and requirements
        for the composition of a candidate Performance Metric Registry Entry.<a href="#section-3-2.2" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-3-3">Other organizations that standardize performance metrics are
      encouraged to use the process defined in this memo to propose a
      candidate Registered Performance Metric.  In addition, this document may
      be useful for other organizations who are defining a Performance Metrics
      Registry of their own and may reuse the features of the Performance
      Metrics Registry defined in this document.<a href="#section-3-3" class="pilcrow">¶</a></p>
<p id="section-3-4">This Performance Metrics Registry is applicable to Performance
      Metrics derived from Active Measurement, Passive Measurement, and any
      other form of Performance Metric. This Registry is designed to encompass
      Performance Metrics developed throughout the IETF and especially for the
      technologies specified in the following working groups: IPPM, XRBLOCK,
      IPFIX, and BMWG. This document analyzes a prior attempt to set up a
      Performance Metrics Registry and the reasons why this design was
      inadequate <span>[<a href="#RFC6248" class="xref">RFC6248</a>]</span>.<a href="#section-3-4" class="pilcrow">¶</a></p>
<p id="section-3-5"><span>[<a href="#RFC8912" class="xref">RFC8912</a>]</span> populates the new Registry
      with the initial set of entries.<a href="#section-3-5" class="pilcrow">¶</a></p>
</section>
<section id="section-4">
      <h2 id="name-motivations-for-the-perform">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-motivations-for-the-perform" class="section-name selfRef">Motivations for the Performance Metrics Registry</a>
      </h2>
<p id="section-4-1">In this section, we detail several motivations for the Performance
      Metrics Registry.<a href="#section-4-1" class="pilcrow">¶</a></p>
<section id="section-4.1">
        <h3 id="name-interoperability">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-interoperability" class="section-name selfRef">Interoperability</a>
        </h3>
<p id="section-4.1-1">As with any IETF Registry, the primary intention is to manage the
        registration of Identifiers for use within one or more protocols. In
        the particular case of the Performance Metrics Registry, there are two
        types of protocols that will use the Performance Metrics in the
        Performance Metrics Registry during their operation (by referring to
        the index values):<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-4.1-2">
          <dt id="section-4.1-2.1">Control Protocol:</dt>
          <dd style="margin-left: 1.5em" id="section-4.1-2.2">This type of protocol is used to allow one
            entity to request that another entity perform a measurement using a
            specific metric defined by the Performance Metrics Registry. One
            particular example is the Large-scale Measurement of Broadband
            Performance (LMAP) framework <span>[<a href="#RFC7594" class="xref">RFC7594</a>]</span>.
            Using the LMAP terminology, the Performance Metrics Registry is
            used in the LMAP Control Protocol to allow a Controller to
            schedule a Measurement Task for one or more Measurement Agents. In
            order to enable this use case, the entries in the Performance
            Metrics Registry must be sufficiently defined to allow a
            Measurement Agent implementation to trigger a specific Measurement
            Task upon the reception of a Control Protocol message. This
            requirement heavily constrains the types of entries that are
            acceptable for the Performance Metrics Registry.<a href="#section-4.1-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-4.1-2.3">Report Protocol:</dt>
          <dd style="margin-left: 1.5em" id="section-4.1-2.4">This type of protocol is used to allow an entity to report Measurement Results to another entity.  By referencing to a specific Registered Performance Metric, it is
            possible to properly characterize the Measurement Result data
            being reported. Using the LMAP terminology, the Performance
            Metrics Registry is used in the LMAP Report Protocol to allow a
            Measurement Agent to report Measurement Results to a
            Collector.<a href="#section-4.1-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
<p id="section-4.1-3"> It should be noted that the LMAP framework explicitly allows
        for using not only the IANA-maintained Performance Metrics Registry
        but also other registries containing Performance Metrics, i.e.,
        either (1) registries defined by other organizations or (2) private registries. However, others who
        are creating registries to be used in the context of an LMAP framework
        are encouraged to use the Registry format defined in this document,
        because this makes it easier for developers of LMAP Measurement Agents
        to programmatically use information found in those other
        registries' entries.<a href="#section-4.1-3" class="pilcrow">¶</a></p>
</section>
<section id="section-4.2">
        <h3 id="name-single-point-of-reference-f">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-single-point-of-reference-f" class="section-name selfRef">Single Point of Reference for Performance Metrics</a>
        </h3>
<p id="section-4.2-1">A Performance Metrics Registry serves as a single point of
        reference for Performance Metrics defined in different working groups
        in the IETF. As we mentioned earlier, there are several working groups that
        define Performance Metrics in the IETF, and it is hard to keep track of
        all of them. This results in multiple definitions of similar Performance
        Metrics that attempt to measure the same phenomena but in slightly
        different (and incompatible) ways. Having a Registry would allow the
        IETF community and others to have a single list of relevant
        Performance Metrics defined by the IETF (and others, where
        appropriate). The single list is also an essential aspect of
        communication about Performance Metrics, where different entities that
        request measurements, execute measurements, and report the results can
        benefit from a common understanding of the referenced Performance
        Metric.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.3">
        <h3 id="name-side-benefits">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-side-benefits" class="section-name selfRef">Side Benefits</a>
        </h3>
<p id="section-4.3-1">There are a couple of side benefits of having such a Registry.
        First, the Performance Metrics Registry could serve as an inventory of
        useful and used Performance Metrics that are normally supported by
        different implementations of Measurement Agents. Second, the results
        of measurements using the Performance Metrics should be comparable
        even if they are performed by different implementations and in
        different networks, as the Performance Metric is properly defined.
        BCP 176 <span>[<a href="#RFC6576" class="xref">RFC6576</a>]</span> examines whether the
        results produced by independent implementations are equivalent in the
        context of evaluating the completeness and clarity of metric
        specifications. <span>[<a href="#RFC6576" class="xref">RFC6576</a>]</span> is a BCP <span>[<a href="#RFC2026" class="xref">RFC2026</a>]</span> that defines the Standards Track advancement
        testing for (Active) IPPM Metrics, and the same process will likely
        suffice to determine whether Registered Performance Metrics are
        sufficiently well specified to result in comparable (or equivalent)
        results. If a Registered Performance Metric has undergone such
        testing, this <span class="bcp14">SHOULD</span> be noted in "Comments and Remarks"
        (see <a href="#remarks" class="xref">Section 7.6</a>), with a reference to the test
        results.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
</section>
</section>
<div id="metrics-criteria">
<section id="section-5">
      <h2 id="name-criteria-for-performance-me">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-criteria-for-performance-me" class="section-name selfRef">Criteria for Performance Metrics Registration</a>
      </h2>
<p id="section-5-1">It is neither possible nor desirable to populate the Performance
      Metrics Registry with all combinations of Parameters of all Performance
      Metrics. A Registered Performance Metric <span class="bcp14">SHOULD</span> be:<a href="#section-5-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-5-2">
        <li id="section-5-2.1">Interpretable by the human user.<a href="#section-5-2.1" class="pilcrow">¶</a>
</li>
        <li id="section-5-2.2">Implementable by the software or hardware designer.<a href="#section-5-2.2" class="pilcrow">¶</a>
</li>
        <li id="section-5-2.3">Deployable by network operators.<a href="#section-5-2.3" class="pilcrow">¶</a>
</li>
        <li id="section-5-2.4">Accurate in terms of producing equivalent results, and for
          interoperability and deployment across vendors.<a href="#section-5-2.4" class="pilcrow">¶</a>
</li>
        <li id="section-5-2.5">Operationally useful, so that it has significant industry
          interest and/or has seen deployment.<a href="#section-5-2.5" class="pilcrow">¶</a>
</li>
        <li id="section-5-2.6">Sufficiently tightly defined, so that different values for the
          Runtime Parameters do not change the fundamental nature of the
          measurement or change the practicality of its implementation.<a href="#section-5-2.6" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-5-3">In essence, there needs to be evidence that (1) a candidate
      Registered Performance Metric has significant industry interest or has
      seen deployment and (2) there is agreement that the candidate Registered
      Performance Metric serves its intended purpose.<a href="#section-5-3" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-6">
      <h2 id="name-performance-metrics-registr">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-performance-metrics-registr" class="section-name selfRef">Performance Metrics Registry: Prior Attempt</a>
      </h2>
<p id="section-6-1">There was a previous attempt to define a Metrics Registry <span>[<a href="#RFC4148" class="xref">RFC4148</a>]</span>. However, it was
      obsoleted by <span>[<a href="#RFC6248" class="xref">RFC6248</a>]</span>
      because it was 

"found to be
      insufficiently detailed to uniquely identify IPPM metrics... [there was
      too much] variability possible when characterizing a metric exactly",

      which led to the IPPM Metrics Registry defined in <span>[<a href="#RFC4148" class="xref">RFC4148</a>]</span> having
 "very few users, if any."<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">Three interesting additional quotes from <span>[<a href="#RFC6248" class="xref">RFC6248</a>]</span> might help to understand the issues
      related to that registry.<a href="#section-6-2" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-6-3">
        <li id="section-6-3.1">"It is not believed to be feasible or even useful to register
          every possible combination of Type P, metric parameters, and Stream
          parameters using the current structure of the IPPM Metrics
          Registry."<a href="#section-6-3.1" class="pilcrow">¶</a>
</li>
        <li id="section-6-3.2">"The current registry structure has been found to be insufficiently
          detailed to uniquely identify IPPM metrics."<a href="#section-6-3.2" class="pilcrow">¶</a>
</li>
        <li id="section-6-3.3">"Despite apparent efforts to find current or even future users,
          no one responded to the call for interest in the RFC 4148 registry
          during the second half of 2010."<a href="#section-6-3.3" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-6-4">The current approach learns from this by tightly defining each
      Registered Performance Metric with only a few variable (Runtime)
      Parameters to be specified by the measurement designer, if any. The idea
      is that entries in the Performance Metrics Registry stem from different
      Measurement Methods that require input (Runtime) Parameters to set
      factors like Source and Destination addresses (which do not change the
      fundamental nature of the measurement). The downside of this approach is
      that it could result in a large number of entries in the Performance
      Metrics Registry. There is agreement that less is more in this context --
      it is better to have a reduced set of useful metrics rather than a large
      set of metrics, some with questionable usefulness.<a href="#section-6-4" class="pilcrow">¶</a></p>
<section id="section-6.1">
        <h3 id="name-why-this-attempt-should-suc">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-why-this-attempt-should-suc" class="section-name selfRef">Why This Attempt Should Succeed</a>
        </h3>
<p id="section-6.1-1">As mentioned in the previous section, one of the main issues with
        the previous Registry was that the metrics contained in the Registry
        were too generic to be useful. This document specifies stricter
        criteria for Performance Metric registration (see <a href="#metrics-criteria" class="xref">Section 5</a>) and
        imposes a group of Performance Metrics Experts that will provide
        guidelines to assess if a Performance Metric is properly
        specified.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
<p id="section-6.1-2">Another key difference between this attempt and the previous one is
        that in this case there is at least one clear user for the Performance
        Metrics Registry: the LMAP framework and protocol. Because the LMAP
        protocol will use the Performance Metrics Registry values in its
        operation, this actually helps to determine if a metric is properly
        defined -- in particular, since we expect that the LMAP Control Protocol will enable
        a Controller to request that a Measurement Agent perform a measurement
        using a given metric by embedding the Performance Metrics Registry
        Identifier in the protocol. Such a metric and method are properly
        specified if they are defined well enough so that it is possible (and
        practical) to implement them in the Measurement Agent. This was the failure of the previous attempt: a Registry Entry with an undefined Type-P (<span><a href="https://www.rfc-editor.org/rfc/rfc2330#section-13" class="relref">Section 13</a> of [<a href="#RFC2330" class="xref">RFC2330</a>]</span>) allows measurement results to vary significantly.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
</section>
</section>
<div id="columns">
<section id="section-7">
      <h2 id="name-definition-of-the-performan">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-definition-of-the-performan" class="section-name selfRef">Definition of the Performance Metrics Registry</a>
      </h2>
<p id="section-7-1">This Performance Metrics Registry is applicable to Performance
      Metrics used for Active Measurement, Passive Measurement, and any other
      form of Performance Measurement. Each category of measurement has unique
      properties, so some of the columns defined below are not applicable for
      a given metric category. In this case, the column(s) <span class="bcp14">SHOULD</span> be populated
      with the "N/A" value (Not Applicable). However, the "N/A" value <span class="bcp14">MUST NOT</span>
      be used by any metric in the following columns: Identifier, Name, URI,
      Status, Requester, Revision, Revision Date, Description. In the future,
      a new category of metrics could require additional columns, and adding
      new columns is a recognized form of Registry extension. The
      specification defining the new column(s) <span class="bcp14">MUST</span> give general guidelines
      for populating the new column(s) for existing entries.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">The columns of the Performance Metrics Registry are defined below.
      The columns are grouped into "Categories" to facilitate the use of the
      Registry. Categories are described at the "Section 7.x" heading level, and columns
      are described at the "Section 7.x.y" heading level. The figure below illustrates this
      organization. An entry (row) therefore gives a complete description of a
      Registered Performance Metric.<a href="#section-7-2" class="pilcrow">¶</a></p>
<p id="section-7-3">Each column serves as a checklist item and helps to avoid omissions
      during registration and Expert Review <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-7-3" class="pilcrow">¶</a></p>
<p id="section-7-4">Registry Categories and Columns are shown below in this format:<a href="#section-7-4" class="pilcrow">¶</a></p>
<div class="alignLeft art-text artwork" id="section-7-5">
<pre>
    Category
    ------------------...
    Column |  Column |...
</pre><a href="#section-7-5" class="pilcrow">¶</a>
</div>
<div class="alignLeft art-text artwork" id="section-7-6">
<pre>
Summary
----------------------------------------------------------------
Identifier | Name | URI | Desc. | Reference | Change     | Ver |
           |      |     |       |           | Controller |

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

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

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

Comments and Remarks
--------------------</pre><a href="#section-7-6" class="pilcrow">¶</a>
</div>
<p id="section-7-7">There is a blank template of the Registry template provided in
      <a href="#blank-reg-template" class="xref">Section 11</a> of this memo.<a href="#section-7-7" class="pilcrow">¶</a></p>
<section id="section-7.1">
        <h3 id="name-summary-category">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-summary-category" class="section-name selfRef">Summary Category</a>
        </h3>
<section id="section-7.1.1">
          <h4 id="name-identifier">
<a href="#section-7.1.1" class="section-number selfRef">7.1.1. </a><a href="#name-identifier" class="section-name selfRef">Identifier</a>
          </h4>
<p id="section-7.1.1-1">This column provides a numeric Identifier for the Registered Performance Metric. The Identifier of each Registered Performance Metric <span class="bcp14">MUST</span> be unique. Note that revising a Metric according to the process in <a href="#revise-reg-perf-metrics" class="xref">Section 8.2</a> creates a new entry in the Performance Metrics Registry with the same identifier.<a href="#section-7.1.1-1" class="pilcrow">¶</a></p>
<p id="section-7.1.1-2">The Registered Performance Metric unique Identifier is an
          unbounded integer (range 0 to infinity).<a href="#section-7.1.1-2" class="pilcrow">¶</a></p>
<p id="section-7.1.1-3">The Identifier 0 should be Reserved. The Identifier values from
          64512 to 65535 are reserved for private or experimental use, and the
          user may encounter overlapping uses.<a href="#section-7.1.1-3" class="pilcrow">¶</a></p>
<p id="section-7.1.1-4">When adding new Registered Performance Metrics to the
          Performance Metrics Registry, IANA <span class="bcp14">SHOULD</span> assign the lowest
          available Identifier to the new Registered Performance Metric.<a href="#section-7.1.1-4" class="pilcrow">¶</a></p>
<p id="section-7.1.1-5">If a Performance Metrics Expert providing review determines that
          there is a reason to assign a specific numeric Identifier, possibly
          leaving a temporary gap in the numbering, then the Performance Metrics
          Expert <span class="bcp14">SHALL</span> inform IANA of this decision.<a href="#section-7.1.1-5" class="pilcrow">¶</a></p>
</section>
<div id="name-sec7-1-2">
<section id="section-7.1.2">
          <h4 id="name-name">
<a href="#section-7.1.2" class="section-number selfRef">7.1.2. </a><a href="#name-name" class="section-name selfRef">Name</a>
          </h4>
<p id="section-7.1.2-1">As the Name of a Registered Performance Metric is the first thing
          a potential human implementer will use when determining whether it
          is suitable for their measurement study, it is important to be as
          precise and descriptive as possible. In the future, users will review
          the Names to determine if the metric they want to measure has
          already been registered, or if a similar entry is available, as a
          basis for creating a new entry.<a href="#section-7.1.2-1" class="pilcrow">¶</a></p>
<p id="section-7.1.2-2">Names are composed of the following elements, separated by an
          underscore character "_":<a href="#section-7.1.2-2" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.1.2-3.1">MetricType_Method_SubTypeMethod_... Spec_Units_Output<a href="#section-7.1.2-3.1" class="pilcrow">¶</a>
</li>
          </ul>
<span class="break"></span><dl class="dlParallel" id="section-7.1.2-4">
            <dt id="section-7.1.2-4.1">MetricType:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-4.2">A combination of the directional properties and
              the metric measured, such as and not limited to:<a href="#section-7.1.2-4.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<div id="metric-type">
<table class="center" id="table-1">
            <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
<tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">RTDelay</td>
                <td class="text-left" rowspan="1" colspan="1">Round-Trip Delay</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">RTDNS</td>
                <td class="text-left" rowspan="1" colspan="1">Response Time Domain Name Service</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">RLDNS</td>
                <td class="text-left" rowspan="1" colspan="1">Response Loss Domain Name Service</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWDelay</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Delay</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">RTLoss</td>
                <td class="text-left" rowspan="1" colspan="1">Round-Trip Loss</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWLoss</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Loss</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWPDV</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Packet Delay Variation</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWIPDV</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Inter-Packet Delay Variation</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWReorder</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Packet Reordering</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWDuplic</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Packet Duplication</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWBTC</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Bulk Transport Capacity</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">OWMBM</td>
                <td class="text-left" rowspan="1" colspan="1">One-Way Model-Based Metric</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">SPMonitor</td>
                <td class="text-left" rowspan="1" colspan="1">Single-Point Monitor</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">MPMonitor</td>
                <td class="text-left" rowspan="1" colspan="1">Multi-Point Monitor</td>
              </tr>
            </tbody>
          </table>
</div>
<span class="break"></span><dl class="dlParallel" id="section-7.1.2-6">
            <dt id="section-7.1.2-6.1">Method:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-6.2">One of the methods defined in <span>[<a href="#RFC7799" class="xref">RFC7799</a>]</span>, such as and not limited
              to:<a href="#section-7.1.2-6.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<div id="methods">
<table class="center" id="table-2">
            <caption><a href="#table-2" class="selfRef">Table 2</a></caption>
<tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Active</td>
                <td class="text-left" rowspan="1" colspan="1">depends on a dedicated measurement packet stream and observations of
      the stream as described in <span>[<a href="#RFC7799" class="xref">RFC7799</a>]</span>
</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Passive</td>
                <td class="text-left" rowspan="1" colspan="1">depends *solely* on observation of one or more existing packet streams as described in <span>[<a href="#RFC7799" class="xref">RFC7799</a>]</span>
</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">HybridType1</td>
                <td class="text-left" rowspan="1" colspan="1">Hybrid Type I observations on one stream that combine both Active
      Methods and Passive Methods as described in <span>[<a href="#RFC7799" class="xref">RFC7799</a>]</span>
</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">HybridType2</td>
                <td class="text-left" rowspan="1" colspan="1">Hybrid Type II observations on two or more streams that combine both
      Active Methods and Passive Methods as described in <span>[<a href="#RFC7799" class="xref">RFC7799</a>]</span>
</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Spatial</td>
                <td class="text-left" rowspan="1" colspan="1">spatial metric as described in <span>[<a href="#RFC5644" class="xref">RFC5644</a>]</span>
</td>
              </tr>
            </tbody>
          </table>
</div>
<span class="break"></span><dl class="dlParallel" id="section-7.1.2-8">
            <dt id="section-7.1.2-8.1">SubTypeMethod:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-8.2">One or more subtypes to further describe the
              features of the entry, such as and not limited to:<a href="#section-7.1.2-8.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<div id="SubTypeMethod">
<table class="center" id="table-3">
            <caption><a href="#table-3" class="selfRef">Table 3</a></caption>
<tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">ICMP</td>
                <td class="text-left" rowspan="1" colspan="1">Internet Control Message Protocol</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">IP</td>
                <td class="text-left" rowspan="1" colspan="1">Internet Protocol</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">DSCPxx</td>
                <td class="text-left" rowspan="1" colspan="1">where xx is replaced by a Diffserv code point</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">UDP</td>
                <td class="text-left" rowspan="1" colspan="1">User Datagram Protocol</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">TCP</td>
                <td class="text-left" rowspan="1" colspan="1">Transport Control Protocol</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">QUIC</td>
                <td class="text-left" rowspan="1" colspan="1">QUIC transport protocol</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">HS</td>
                <td class="text-left" rowspan="1" colspan="1">Hand-Shake, such as TCP's 3-way HS</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Poisson</td>
                <td class="text-left" rowspan="1" colspan="1">packet generation using Poisson distribution</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Periodic</td>
                <td class="text-left" rowspan="1" colspan="1">periodic packet generation</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">SendOnRcv</td>
                <td class="text-left" rowspan="1" colspan="1">sender keeps one packet in transit by sending when previous packet arrives</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">PayloadxxxxB</td>
                <td class="text-left" rowspan="1" colspan="1">where xxxx is replaced by an integer, the number of octets or 8-bit
      Bytes in the Payload</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">SustainedBurst</td>
                <td class="text-left" rowspan="1" colspan="1">capacity test, worst case</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">StandingQueue</td>
                <td class="text-left" rowspan="1" colspan="1">test of bottleneck queue behavior</td>
              </tr>
            </tbody>
          </table>
</div>
<p style="margin-left: 1.5em" id="section-7.1.2-10">SubTypeMethod values are separated by a hyphen "-"
              character, which indicates that they belong to this element and
              that their order is unimportant when considering Name
              uniqueness.<a href="#section-7.1.2-10" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.1.2-11">
            <dt id="section-7.1.2-11.1">Spec:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-11.2">An immutable document Identifier combined with a
              document section Identifier. For RFCs, this consists of the RFC
              number and major section number that specifies this Registry
              Entry in the form "RFCXXXXsecY", e.g., RFC7799sec3. Note: The
              RFC number is not the primary reference specification for the
              metric definition (e.g., <span>[<a href="#RFC7679" class="xref">RFC7679</a>]</span> as the primary reference specification for
              one-way delay metrics); it will contain the placeholder
              "RFCXXXXsecY" until the
              RFC number is assigned to the specifying document and would
              remain blank in Private Registry Entries without a corresponding
              RFC. Anticipating the "RFC10K" problem, the number of the RFC
              continues to replace "RFCXXXX", regardless of the number of digits
              in the RFC number. Anticipating Registry Entries from other
              standards bodies, the form of this Name Element <span class="bcp14">MUST</span> be proposed
              and reviewed for consistency and uniqueness by the Expert
              Reviewer.<a href="#section-7.1.2-11.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-7.1.2-11.3">Units:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-11.4">
              <p id="section-7.1.2-11.4.1">The units of measurement for the output, such as and
              not limited to:<a href="#section-7.1.2-11.4.1" class="pilcrow">¶</a></p>
</dd>
          <dd class="break"></dd>
</dl>
<div id="units">
<table class="center" id="table-4">
            <caption><a href="#table-4" class="selfRef">Table 4</a></caption>
<tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Seconds</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Ratio</td>
                <td class="text-left" rowspan="1" colspan="1">unitless</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Percent</td>
                <td class="text-left" rowspan="1" colspan="1">value multiplied by 100%</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Logical</td>
                <td class="text-left" rowspan="1" colspan="1">1 or 0</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Packets</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">BPS</td>
                <td class="text-left" rowspan="1" colspan="1">bits per second</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">PPS</td>
                <td class="text-left" rowspan="1" colspan="1">packets per second</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">EventTotal</td>
                <td class="text-left" rowspan="1" colspan="1">for unitless counts</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Multiple</td>
                <td class="text-left" rowspan="1" colspan="1">more than one type of unit</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Enumerated</td>
                <td class="text-left" rowspan="1" colspan="1">a list of outcomes</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Unitless</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
            </tbody>
          </table>
</div>
<span class="break"></span><dl class="dlParallel" id="section-7.1.2-13">
            <dt id="section-7.1.2-13.1">Output:</dt>
            <dd style="margin-left: 1.5em" id="section-7.1.2-13.2">The type of output resulting from measurement, such
              as and not limited to:<a href="#section-7.1.2-13.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<div id="output">
<table class="center" id="table-5">
            <caption><a href="#table-5" class="selfRef">Table 5</a></caption>
<tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Singleton</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Raw</td>
                <td class="text-left" rowspan="1" colspan="1">multiple singletons</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Count</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Minimum</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Maximum</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Median</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Mean</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">95Percentile</td>
                <td class="text-left" rowspan="1" colspan="1">95th percentile</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">99Percentile</td>
                <td class="text-left" rowspan="1" colspan="1">99th percentile</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">StdDev</td>
                <td class="text-left" rowspan="1" colspan="1">standard deviation</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">Variance</td>
                <td class="text-left" rowspan="1" colspan="1"></td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">PFI</td>
                <td class="text-left" rowspan="1" colspan="1">pass, fail, inconclusive</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">FlowRecords</td>
                <td class="text-left" rowspan="1" colspan="1">descriptions of flows observed</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">LossRatio</td>
                <td class="text-left" rowspan="1" colspan="1">lost packets to total packets, &lt;=1</td>
              </tr>
            </tbody>
          </table>
</div>
<p id="section-7.1.2-15">An example, as described in <span><a href="https://www.rfc-editor.org/rfc/rfc8912#section-4" class="relref">Section 4</a> of [<a href="#RFC8912" class="xref">RFC8912</a>]</span>, is<a href="#section-7.1.2-15" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.1.2-16.1">RTDelay_Active_IP-UDP-Periodic_RFC8912sec4_Seconds_95Percentile<a href="#section-7.1.2-16.1" class="pilcrow">¶</a>
</li>
          </ul>
<p id="section-7.1.2-17">Note that private registries following the format described here
          <span class="bcp14">SHOULD</span> use the prefix "Priv_" on any Name to avoid unintended
          conflicts (further considerations are described in <a href="#iana-cons" class="xref">Section 10</a>).
          Private Registry Entries usually have no specifying RFC; thus, the
          Spec: element has no clear interpretation.<a href="#section-7.1.2-17" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-7.1.3">
          <h4 id="name-uri">
<a href="#section-7.1.3" class="section-number selfRef">7.1.3. </a><a href="#name-uri" class="section-name selfRef">URI</a>
          </h4>
<p id="section-7.1.3-1">The URI column <span class="bcp14">MUST</span> contain a URL <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> that
          uniquely identifies and locates the Metric Entry so it is accessible
          through the Internet. The URL points to a file containing all of the
          human-readable information for one Registry Entry. The URL <span class="bcp14">SHALL</span>
          reference a target file that is preferably HTML-formatted and
          contains URLs to referenced sections of HTMLized RFCs, or other
          reference specifications. These target files for different entries
          can be more easily edited and reused when preparing new entries.
          The exact form of the URL for each target file, and the target file
          itself, will be determined by IANA and reside on
          <span>&lt;<a href="https://www.iana.org/">https://www.iana.org/</a>&gt;</span>.
          <span><a href="https://www.rfc-editor.org/rfc/rfc8912#section-4" class="relref">Section 4</a> of [<a href="#RFC8912" class="xref">RFC8912</a>]</span>, as well as
          subsequent major sections of that document, provide an example of a target file in HTML form.<a href="#section-7.1.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.1.4">
          <h4 id="name-description">
<a href="#section-7.1.4" class="section-number selfRef">7.1.4. </a><a href="#name-description" class="section-name selfRef">Description</a>
          </h4>
<p id="section-7.1.4-1">A Registered Performance Metric description is a written
          representation of a particular Performance Metrics Registry Entry.
          It supplements the Registered Performance Metric Name to help
          Performance Metrics Registry users select relevant Registered
          Performance Metrics.<a href="#section-7.1.4-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.1.5">
          <h4 id="name-reference">
<a href="#section-7.1.5" class="section-number selfRef">7.1.5. </a><a href="#name-reference" class="section-name selfRef">Reference</a>
          </h4>
<p id="section-7.1.5-1">This entry gives the specification containing the candidate
          Registry Entry that was reviewed and agreed upon, if such an RFC or
          other specification exists.<a href="#section-7.1.5-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.1.6">
          <h4 id="name-change-controller">
<a href="#section-7.1.6" class="section-number selfRef">7.1.6. </a><a href="#name-change-controller" class="section-name selfRef">Change Controller</a>
          </h4>
<p id="section-7.1.6-1">This entry names the entity responsible for approving revisions
          to the Registry Entry and <span class="bcp14">SHALL</span> provide contact information (for an
          individual, where appropriate).<a href="#section-7.1.6-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.1.7">
          <h4 id="name-version-of-registry-format">
<a href="#section-7.1.7" class="section-number selfRef">7.1.7. </a><a href="#name-version-of-registry-format" class="section-name selfRef">Version (of Registry Format)</a>
          </h4>
<p id="section-7.1.7-1">This column gives the version number for the Registry format used, at the time the Performance Metric is registered. The format complying with this memo <span class="bcp14">MUST</span> use 1.0. A new RFC that changes the Registry format will designate a new version number corresponding to that format. The version number of Registry Entries <span class="bcp14">SHALL NOT</span> change unless the Registry Entry is updated to reflect the Registry format (following the procedures in <a href="#managing-perf-metric-grp" class="xref">Section 8</a>).<a href="#section-7.1.7-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-7.2">
        <h3 id="name-metric-definition-category">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-metric-definition-category" class="section-name selfRef">Metric Definition Category</a>
        </h3>
<p id="section-7.2-1">This category includes columns to prompt all necessary details
        related to the metric definition, including the immutable document
        reference and values of input factors, called "Fixed Parameters", which
        are left open in the immutable document but have a particular value
        defined by the Performance Metric.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
<section id="section-7.2.1">
          <h4 id="name-reference-definition">
<a href="#section-7.2.1" class="section-number selfRef">7.2.1. </a><a href="#name-reference-definition" class="section-name selfRef">Reference Definition</a>
          </h4>
<p id="section-7.2.1-1">This entry provides a reference (or references) to the relevant
          sections of the document or documents that define the metric, as well as any
          supplemental information needed to ensure an unambiguous definition
          for implementations. A given reference needs to be an immutable
          document, such as an RFC; for other standards bodies, it is likely
          to be necessary to reference a specific, dated version of a
          specification.<a href="#section-7.2.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.2.2">
          <h4 id="name-fixed-parameters">
<a href="#section-7.2.2" class="section-number selfRef">7.2.2. </a><a href="#name-fixed-parameters" class="section-name selfRef">Fixed Parameters</a>
          </h4>
<p id="section-7.2.2-1">Fixed Parameters are Parameters whose values must be specified in
          the Performance Metrics Registry. The measurement system uses these
          values.<a href="#section-7.2.2-1" class="pilcrow">¶</a></p>
<p id="section-7.2.2-2">Where referenced metrics supply a list of Parameters as part of
          their descriptive template, a subset of the Parameters will be
          designated as Fixed Parameters. As an example for Active Metrics,
          Fixed Parameters determine most or all of the IPPM framework
          convention "packets of Type-P" as described in <span>[<a href="#RFC2330" class="xref">RFC2330</a>]</span>, such as transport protocol,
          payload length, TTL, etc. An example for Passive Metrics is for an RTP packet loss
          calculation that relies on the validation of a packet as RTP, which
          is a multi-packet validation controlled by the MIN_SEQUENTIAL variable as defined
          by <span>[<a href="#RFC3550" class="xref">RFC3550</a>]</span>. Varying MIN_SEQUENTIAL values can alter
          the loss report, and this variable could be set as a Fixed
          Parameter.<a href="#section-7.2.2-2" class="pilcrow">¶</a></p>
<p id="section-7.2.2-3">Parameters <span class="bcp14">MUST</span> have well-defined names. For human readers, the
          hanging-indent style is preferred, and any Parameter names and
          definitions that do not appear in the Reference Method Specification
          <span class="bcp14">MUST</span> appear in this column (or the Runtime Parameters column).<a href="#section-7.2.2-3" class="pilcrow">¶</a></p>
<p id="section-7.2.2-4">Parameters <span class="bcp14">MUST</span> have a well-specified data format.<a href="#section-7.2.2-4" class="pilcrow">¶</a></p>
<p id="section-7.2.2-5">A Parameter that is a Fixed Parameter for one Performance
          Metrics Registry Entry may be designated as a Runtime Parameter for
          another Performance Metrics Registry Entry.<a href="#section-7.2.2-5" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-7.3">
        <h3 id="name-method-of-measurement-categ">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-method-of-measurement-categ" class="section-name selfRef">Method of Measurement Category</a>
        </h3>
<p id="section-7.3-1">This category includes columns for references to relevant sections
        of the immutable document(s) and any supplemental information needed
        to ensure an unambiguous method for implementations.<a href="#section-7.3-1" class="pilcrow">¶</a></p>
<section id="section-7.3.1">
          <h4 id="name-reference-method">
<a href="#section-7.3.1" class="section-number selfRef">7.3.1. </a><a href="#name-reference-method" class="section-name selfRef">Reference Method</a>
          </h4>
<p id="section-7.3.1-1">This entry provides references to relevant sections of immutable
          documents, such as RFC(s) (for other standards bodies, it is likely
          to be necessary to reference a specific, dated version of a
          specification) describing the Method of Measurement, as well as any
          supplemental information needed to ensure unambiguous interpretation
          for implementations referring to the immutable document text.<a href="#section-7.3.1-1" class="pilcrow">¶</a></p>
<p id="section-7.3.1-2">Specifically, this section should include pointers to pseudocode
          or actual code that could be used for an unambiguous
          implementation.<a href="#section-7.3.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.2">
          <h4 id="name-packet-stream-generation">
<a href="#section-7.3.2" class="section-number selfRef">7.3.2. </a><a href="#name-packet-stream-generation" class="section-name selfRef">Packet Stream Generation</a>
          </h4>
<p id="section-7.3.2-1">This column applies to Performance Metrics that generate traffic
          as part of their Measurement Method, including, but not necessarily
          limited to, Active Metrics. The generated traffic is referred to as a
          "stream", and this column describes its characteristics.<a href="#section-7.3.2-1" class="pilcrow">¶</a></p>
<p id="section-7.3.2-2">Each entry for this column contains the following information:<a href="#section-7.3.2-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.2-3">
            <dt id="section-7.3.2-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.2-3.2">The name of the packet stream scheduling
              discipline<a href="#section-7.3.2-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-7.3.2-3.3">Reference:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.2-3.4">The specification where the Parameters of the
              stream are defined<a href="#section-7.3.2-3.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<p id="section-7.3.2-4">The packet generation stream may require Parameters such as the
          average packet rate and distribution truncation value for streams
          with Poisson-distributed inter-packet sending times. If such
          Parameters are needed, they should be included in either the Fixed
          Parameters column or the Runtime Parameters column, depending on
          whether they will be fixed or will be an input for the metric.<a href="#section-7.3.2-4" class="pilcrow">¶</a></p>
<p id="section-7.3.2-5">The simplest example of stream specification is singleton
          scheduling (see <span>[<a href="#RFC2330" class="xref">RFC2330</a>]</span>), where a
          single atomic measurement is conducted. Each atomic measurement
          could consist of sending a single packet (such as a DNS request) or
          sending several packets (for example, to request a web page). Other
          streams support a series of atomic measurements using pairs of
          packets, where the packet stream follows a schedule defining the
          timing between transmitted packets, and an atomic measurement
          assesses the reception time between successive packets (e.g., a
          measurement of Inter-Packet Delay Variation). More complex streams
          and measurement relationships are possible. Principally, two
          different streams are used in IPPM Metrics: (1) Poisson,
          distributed as described in <span>[<a href="#RFC2330" class="xref">RFC2330</a>]</span> and (2) periodic, as described in <span>[<a href="#RFC3432" class="xref">RFC3432</a>]</span>. Both Poisson and periodic have
          their own unique Parameters, and the relevant set of Parameter names
          and values should be included in either the Fixed Parameters column
          or the Runtime Parameters column.<a href="#section-7.3.2-5" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.3">
          <h4 id="name-traffic-filter">
<a href="#section-7.3.3" class="section-number selfRef">7.3.3. </a><a href="#name-traffic-filter" class="section-name selfRef">Traffic Filter</a>
          </h4>
<p id="section-7.3.3-1">This column applies to Performance Metrics that observe packets
          flowing through (the device with) the Measurement Agent, i.e.,
          packets that are not necessarily addressed to the Measurement Agent.
          This includes, but is not limited to, Passive Metrics. The filter
          specifies the traffic that is measured. This includes protocol field
          values/ranges, such as address ranges, and flow or session
          Identifiers.<a href="#section-7.3.3-1" class="pilcrow">¶</a></p>
<p id="section-7.3.3-2">The Traffic Filter itself depends on the needs of the metric itself
          and a balance of an operator's measurement needs and a user's need
          for privacy. Mechanics for conveying the filter criteria might be
          the BPF (Berkeley Packet Filter) or PSAMP (Packet Sampling) <span>[<a href="#RFC5475" class="xref">RFC5475</a>]</span>
          Property Match Filtering, which reuses IPFIX <span>[<a href="#RFC7012" class="xref">RFC7012</a>]</span>. An example BPF string for matching TCP/80
          traffic to remote Destination net 192.0.2.0/24 would be "dst net
          192.0.2.0/24 and tcp dst port 80". More complex filter engines may allow for matching using Deep Packet Inspection (DPI) technology.<a href="#section-7.3.3-2" class="pilcrow">¶</a></p>
<p id="section-7.3.3-3">The Traffic Filter includes the following information:<a href="#section-7.3.3-3" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.3-4">
            <dt id="section-7.3.3-4.1">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.3-4.2">The type of Traffic Filter used, e.g., BPF, PSAMP,
              OpenFlow rule, etc., as defined by a normative reference<a href="#section-7.3.3-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-7.3.3-4.3">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.3-4.4">The actual set of rules expressed<a href="#section-7.3.3-4.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
<section id="section-7.3.4">
          <h4 id="name-sampling-distribution">
<a href="#section-7.3.4" class="section-number selfRef">7.3.4. </a><a href="#name-sampling-distribution" class="section-name selfRef">Sampling Distribution</a>
          </h4>
<p id="section-7.3.4-1">The sampling distribution defines, out of all of the packets that
          match the Traffic Filter, which one or more of those packets are
          actually used for the measurement.  One possibility is "all", which
          implies that all packets matching the Traffic Filter are considered,
          but there may be other sampling strategies. It includes the following information:<a href="#section-7.3.4-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7.3.4-2">
            <dt id="section-7.3.4-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.4-2.2">The name of the sampling distribution<a href="#section-7.3.4-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-7.3.4-2.3">Reference definition:</dt>
            <dd style="margin-left: 1.5em" id="section-7.3.4-2.4">Pointer to the specification where the
              sampling distribution is properly defined<a href="#section-7.3.4-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<p id="section-7.3.4-3">The sampling distribution may require Parameters. If such
          Parameters are needed, they should be included in either the Fixed
          Parameters column or the Runtime Parameters column, depending on
          whether they will be fixed or will be an input for the metric.<a href="#section-7.3.4-3" class="pilcrow">¶</a></p>
<p id="section-7.3.4-4">PSAMP is documented in "Sampling and Filtering Techniques for IP Packet Selection" <span>[<a href="#RFC5475" class="xref">RFC5475</a>]</span>,
          while "A Framework for Packet Selection and Reporting" <span>[<a href="#RFC5474" class="xref">RFC5474</a>]</span> provides more background information. The
          sampling distribution Parameters might be expressed in terms of
          the model described in "Information Model for Packet Sampling
          Exports" <span>[<a href="#RFC5477" class="xref">RFC5477</a>]</span> and the process
          provided in "Flow Selection Techniques" <span>[<a href="#RFC7014" class="xref">RFC7014</a>]</span>.<a href="#section-7.3.4-4" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.5">
          <h4 id="name-runtime-parameters">
<a href="#section-7.3.5" class="section-number selfRef">7.3.5. </a><a href="#name-runtime-parameters" class="section-name selfRef">Runtime Parameters</a>
          </h4>
<p id="section-7.3.5-1">In contrast to the Fixed Parameters, Runtime Parameters are Parameters that do not change the fundamental nature of the measurement and their values are not specified in the Performance Metrics Registry. They are left as variables in the Registry, as an aid to the measurement system implementer or user. Their values are supplied on execution, configured into the measurement system, and reported with the Measurement Results (so that the context is complete).<a href="#section-7.3.5-1" class="pilcrow">¶</a></p>
<p id="section-7.3.5-2">Where metrics supply a list of Parameters as part of their
          descriptive template, a subset of the Parameters will be designated
          as Runtime Parameters.<a href="#section-7.3.5-2" class="pilcrow">¶</a></p>
<p id="section-7.3.5-3">Parameters <span class="bcp14">MUST</span> have well-defined names. For human readers, the
          hanging-indent style is preferred, and the names and definitions
          that do not appear in the Reference Method Specification <span class="bcp14">MUST</span> appear
          in this column.<a href="#section-7.3.5-3" class="pilcrow">¶</a></p>
<p id="section-7.3.5-4">A data format for each Runtime Parameter <span class="bcp14">MUST</span> be specified in
          this column, to simplify the control and implementation of
          measurement devices. For example, Parameters that include an IPv4
          address can be encoded as a 32-bit integer (i.e., a binary
          base64-encoded value) or "ip‑address" as defined in <span>[<a href="#RFC6991" class="xref">RFC6991</a>]</span>.
          The actual encoding(s) used must be explicitly defined for each
          Runtime Parameter. IPv6 addresses and options <span class="bcp14">MUST</span> be accommodated,
          allowing Registered Performance Metrics to be used in that address family. Other
          address families are permissible.<a href="#section-7.3.5-4" class="pilcrow">¶</a></p>
<p id="section-7.3.5-5">Examples of Runtime Parameters include IP addresses, measurement
          point designations, start times and end times for measurement, and
          other information essential to the Method of Measurement.<a href="#section-7.3.5-5" class="pilcrow">¶</a></p>
</section>
<section id="section-7.3.6">
          <h4 id="name-role">
<a href="#section-7.3.6" class="section-number selfRef">7.3.6. </a><a href="#name-role" class="section-name selfRef">Role</a>
          </h4>
<p id="section-7.3.6-1">In some Methods of Measurement, there may be several Roles
          defined, e.g., for a one-way packet delay Active Measurement, there
          is one Measurement Agent that generates the packets and another
          Agent that receives the packets. This column contains the name of
          the Role(s) for this particular entry. In the one-way delay example
          above, there should be two entries in the Registry's Role column, one
          for each Role (Source and Destination). When a Measurement Agent is
          instructed to perform the "Source" Role for the one-way delay metric,
          the Agent knows that it is required to generate packets. The values
          for this field are defined in the Reference Method of Measurement
          (and this frequently results in abbreviated Role names such as
          "Src").<a href="#section-7.3.6-1" class="pilcrow">¶</a></p>
<p id="section-7.3.6-2">When the Role column of a Registry Entry defines more than one
          Role, the Role <span class="bcp14">SHALL</span> be treated as a Runtime Parameter and
          supplied for execution. It should be noted that the LMAP framework
          <span>[<a href="#RFC7594" class="xref">RFC7594</a>]</span> distinguishes the Role from other Runtime
          Parameters.<a href="#section-7.3.6-2" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-7.4">
        <h3 id="name-output-category">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-output-category" class="section-name selfRef">Output Category</a>
        </h3>
<p id="section-7.4-1">For entries that involve a stream and many singleton measurements,
        a statistic may be specified in this column to summarize the results
        to a single value. If the complete set of measured singletons is
        output, this will be specified here.<a href="#section-7.4-1" class="pilcrow">¶</a></p>
<p id="section-7.4-2">Some metrics embed one specific statistic in the reference metric
        definition, while others allow several output types or statistics.<a href="#section-7.4-2" class="pilcrow">¶</a></p>
<section id="section-7.4.1">
          <h4 id="name-type">
<a href="#section-7.4.1" class="section-number selfRef">7.4.1. </a><a href="#name-type" class="section-name selfRef">Type</a>
          </h4>
<p id="section-7.4.1-1">This column contains the name of the output type. The output type
          defines a single type of result that the metric produces. It can be
          the raw results (packet send times and singleton metrics), or it can
          be a summary statistic. The specification of the output type <span class="bcp14">MUST</span>
          define the format of the output. In some systems, format
          specifications will simplify both measurement implementation and
          collection/storage tasks. Note that if two different statistics are
          required from a single measurement (for example, both "Xth
          percentile mean" and "Raw"), then a new output type must be defined
          ("Xth percentile mean AND Raw"). See <a href="#name-sec7-1-2" class="xref">Section 7.1.2</a>
          above for a list of output types.<a href="#section-7.4.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.4.2">
          <h4 id="name-reference-definition-2">
<a href="#section-7.4.2" class="section-number selfRef">7.4.2. </a><a href="#name-reference-definition-2" class="section-name selfRef">Reference Definition</a>
          </h4>
<p id="section-7.4.2-1">This column contains a pointer to the specification(s) where the
          output type and format are defined.<a href="#section-7.4.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.4.3">
          <h4 id="name-metric-units">
<a href="#section-7.4.3" class="section-number selfRef">7.4.3. </a><a href="#name-metric-units" class="section-name selfRef">Metric Units</a>
          </h4>
<p id="section-7.4.3-1">The measured results must be expressed using some standard
          dimension or units of measure. This column provides the units.<a href="#section-7.4.3-1" class="pilcrow">¶</a></p>
<p id="section-7.4.3-2">When a sample of singletons (see <span><a href="https://www.rfc-editor.org/rfc/rfc2330#section-11" class="relref">Section 11</a> of [<a href="#RFC2330" class="xref">RFC2330</a>]</span> for definitions of these terms) is collected,
          this entry will specify the units for each measured value.<a href="#section-7.4.3-2" class="pilcrow">¶</a></p>
</section>
<section id="section-7.4.4">
          <h4 id="name-calibration">
<a href="#section-7.4.4" class="section-number selfRef">7.4.4. </a><a href="#name-calibration" class="section-name selfRef">Calibration</a>
          </h4>
<p id="section-7.4.4-1">Some specifications for Methods of Measurement include the
          ability to perform an error calibration. <span><a href="https://www.rfc-editor.org/rfc/rfc7679#section-3.7.3" class="relref">Section 3.7.3</a> of [<a href="#RFC7679" class="xref">RFC7679</a>]</span> is one example. In the Registry Entry, this field
          will identify a method of calibration for the metric, and, when
          available, the measurement system <span class="bcp14">SHOULD</span> perform the calibration
          when requested and produce the output with an indication that it is
          the result of a calibration method. 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 in this way.<a href="#section-7.4.4-1" class="pilcrow">¶</a></p>
<p id="section-7.4.4-2">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).<a href="#section-7.4.4-2" class="pilcrow">¶</a></p>
<p id="section-7.4.4-3">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 that is the result of
          system noise and is thus inaccurate.<a href="#section-7.4.4-3" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-7.5">
        <h3 id="name-administrative-information">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-administrative-information" class="section-name selfRef">Administrative Information</a>
        </h3>
<section id="section-7.5.1">
          <h4 id="name-status">
<a href="#section-7.5.1" class="section-number selfRef">7.5.1. </a><a href="#name-status" class="section-name selfRef">Status</a>
          </h4>
<p id="section-7.5.1-1">This entry indicates the status of the specification of this
          Registered Performance Metric.  Allowed values are 'Current',
          'Deprecated', and 'Obsolete'.  All newly defined Registered
          Performance Metrics have 'Current' Status.<a href="#section-7.5.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.5.2">
          <h4 id="name-requester">
<a href="#section-7.5.2" class="section-number selfRef">7.5.2. </a><a href="#name-requester" class="section-name selfRef">Requester</a>
          </h4>
<p id="section-7.5.2-1">This entry indicates the requester for the Registered Performance Metric. The
          requester <span class="bcp14">MAY</span> be a document (such as an RFC) or a person.<a href="#section-7.5.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.5.3">
          <h4 id="name-revision">
<a href="#section-7.5.3" class="section-number selfRef">7.5.3. </a><a href="#name-revision" class="section-name selfRef">Revision</a>
          </h4>
<p id="section-7.5.3-1">This entry indicates the revision number of a Registered Performance Metric, starting at 0 for Registered Performance Metrics at the time of definition and incremented by one for each revision. However, in the case of a non-backward-compatible revision, see <a href="#deprecating-metrics" class="xref">Section 8.3</a>.<a href="#section-7.5.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-7.5.4">
          <h4 id="name-revision-date">
<a href="#section-7.5.4" class="section-number selfRef">7.5.4. </a><a href="#name-revision-date" class="section-name selfRef">Revision Date</a>
          </h4>
<p id="section-7.5.4-1">This entry indicates the date of acceptance of the most recent revision for the
          Registered Performance Metric. The date <span class="bcp14">SHALL</span> be determined by IANA
          and the reviewing Performance Metrics Expert.<a href="#section-7.5.4-1" class="pilcrow">¶</a></p>
</section>
</section>
<div id="remarks">
<section id="section-7.6">
        <h3 id="name-comments-and-remarks">
<a href="#section-7.6" class="section-number selfRef">7.6. </a><a href="#name-comments-and-remarks" class="section-name selfRef">Comments and Remarks</a>
        </h3>
<p id="section-7.6-1">Besides providing additional details that do not appear in other
        categories, this open category (single column) allows unforeseen
        issues to be addressed by simply updating this informational
        entry.<a href="#section-7.6-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="managing-perf-metric-grp">
<section id="section-8">
      <h2 id="name-processes-for-managing-the-">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-processes-for-managing-the-" class="section-name selfRef">Processes for Managing the Performance Metrics Registry Group</a>
      </h2>
<p id="section-8-1">Once a Performance Metric or set of Performance Metrics has been
      identified for a given application, candidate Performance Metrics
      Registry Entry specifications prepared in accordance with <a href="#columns" class="xref">Section 7</a> should be submitted to IANA to follow the process for
      review by the Performance Metrics Experts, as defined below. This process
      is also used for other changes to a Performance Metrics Registry Entry, such
      as deprecation or revision, as described later in this section.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">It is desirable that the author(s) of a candidate Performance Metrics
      Registry Entry seek review in the relevant IETF working group or offer
      the opportunity for review on the working group mailing list.<a href="#section-8-2" class="pilcrow">¶</a></p>
<div id="add-new-perf-metrics">
<section id="section-8.1">
        <h3 id="name-adding-new-performance-metr">
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-adding-new-performance-metr" class="section-name selfRef">Adding New Performance Metrics to the Performance Metrics Registry</a>
        </h3>
<p id="section-8.1-1">Requests to add Registered Performance Metrics in the Performance
        Metrics Registry <span class="bcp14">SHALL</span> be submitted to IANA, which forwards the
        request to a designated group of experts (Performance Metrics Experts)
        appointed by the IESG; these are the reviewers called for by the
        Specification Required policy <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span> defined for the
        Performance Metrics Registry. The Performance Metrics Experts review
        the request for such things as compliance with this document,
        compliance with other applicable Performance Metrics-related RFCs, and
        consistency with the currently defined set of Registered Performance
        Metrics. The most efficient path for submission begins with
        preparation of an Internet-Draft containing the proposed Performance
        Metrics Registry Entry using the template in <a href="#blank-reg-template" class="xref">Section 11</a>, so that the
        submission formatting will benefit from the normal IETF Internet-Draft
        submission processing (including HTMLization).<a href="#section-8.1-1" class="pilcrow">¶</a></p>
<p id="section-8.1-2">Submission to IANA may be during IESG review (leading to IETF
        Standards Action), where an Internet-Draft proposes one or more
        Registered Performance Metrics to be added to the Performance Metrics
        Registry, including the text of the proposed Registered Performance
        Metric⁠(s).<a href="#section-8.1-2" class="pilcrow">¶</a></p>
<p id="section-8.1-3">If an RFC-to-be includes a Performance Metric and a proposed
        Performance Metrics Registry Entry but the Performance Metrics Expert's
        review determines that one or more of the criteria listed in <a href="#metrics-criteria" class="xref">Section 5</a> have not
        been met, then the proposed Performance Metrics Registry Entry <span class="bcp14">MUST</span> be
        removed from the text. Once evidence exists that the Performance
        Metric meets the criteria in <a href="#metrics-criteria" class="xref">Section 5</a>, the proposed Performance
        Metrics Registry Entry <span class="bcp14">SHOULD</span> be submitted to IANA to be evaluated in
        consultation with the Performance Metrics Experts for registration at
        that time.<a href="#section-8.1-3" class="pilcrow">¶</a></p>
<p id="section-8.1-4">Authors of proposed Registered Performance Metrics <span class="bcp14">SHOULD</span> review
        compliance with the specifications in this document to check their
        submissions before sending them to IANA.<a href="#section-8.1-4" class="pilcrow">¶</a></p>
<p id="section-8.1-5">At least one Performance Metrics Expert should endeavor to complete
        referred reviews in a timely manner. If the request is acceptable, the
        Performance Metrics Experts signify their approval to IANA, and IANA
        updates the Performance Metrics Registry. If the request is not
        acceptable, the Performance Metrics Experts <span class="bcp14">MAY</span>
        coordinate with the requester to change the request so that it is
        compliant; otherwise, IANA <span class="bcp14">SHALL</span> coordinate resolution
        of issues on behalf of the expert. The Performance Metrics Experts
        <span class="bcp14">MAY</span> choose to reject clearly frivolous or inappropriate
        change requests outright, but such exceptional circumstances should be
        rare.<a href="#section-8.1-5" class="pilcrow">¶</a></p>
<p id="section-8.1-6">If the proposed Metric is unique in a significant way, in order to
 properly describe the Metric, it may be necessary to propose a new Name
 Element Registry, or (more likely) a new Entry in an existing Name
 Element Registry. This proposal is part of the request for the new
 Metric, so that it undergoes the same IANA review and approval
 process.<a href="#section-8.1-6" class="pilcrow">¶</a></p>
<p id="section-8.1-7">Decisions by the Performance Metrics Experts may be appealed per
        <span><a href="https://www.rfc-editor.org/rfc/rfc8126#section-10" class="relref">Section 10</a> of [<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-8.1-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="revise-reg-perf-metrics">
<section id="section-8.2">
        <h3 id="name-backward-compatible-revisio">
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-backward-compatible-revisio" class="section-name selfRef">Backward-Compatible Revision of Registered Performance Metrics</a>
        </h3>
<p id="section-8.2-1">A request for revision is only permitted when the requested changes
        maintain backward compatibility with implementations of the prior
        Performance Metrics Registry Entry describing a Registered Performance
        Metric (entries with lower revision numbers but having the same Identifier
        and Name).<a href="#section-8.2-1" class="pilcrow">¶</a></p>
<p id="section-8.2-2">The purpose of the Status field in the Performance Metrics Registry is to indicate whether the entry for a Registered Performance Metric is 'Current', 'Deprecated', or 'Obsolete'. The term 'deprecated' is used when an entry is replaced, either with a backwards-compatible revision (this sub-section) or with a non-backwards-compatible revision (in <a href="#deprecating-metrics" class="xref">Section 8.3</a>).<a href="#section-8.2-2" class="pilcrow">¶</a></p>
<p id="section-8.2-3">In addition, no policy is defined for revising the Performance
        Metric Entries in the IANA Registry or addressing errors therein. To
        be clear, changes and deprecations within the Performance Metrics
        Registry are not encouraged and should be avoided to the extent
        possible. However, in recognition that change is inevitable, the
        provisions of this section address the need for revisions.<a href="#section-8.2-3" class="pilcrow">¶</a></p>
<p id="section-8.2-4">Revisions are initiated by sending a candidate Registered
        Performance Metric definition to IANA, per <a href="#add-new-perf-metrics" class="xref">Section 8.1</a>, identifying
        the existing Performance Metrics Registry Entry, and explaining how
        and why the existing entry should be revised.<a href="#section-8.2-4" class="pilcrow">¶</a></p>
<p id="section-8.2-5">The primary requirement in the definition of procedures for
        managing changes to existing Registered Performance Metrics is
        avoidance of measurement interoperability problems; the Performance
        Metrics Experts must work to maintain interoperability above all else.
        Changes to Registered Performance Metrics may only be done in an
        interoperable way; necessary changes that cannot be done in a way that
        allows interoperability with unchanged implementations <span class="bcp14">MUST</span> result in
        the creation of a new Registered Performance Metric (with a new Name,
        replacing the RFCXXXXsecY portion of the Name) and possibly the
        deprecation of the earlier metric.<a href="#section-8.2-5" class="pilcrow">¶</a></p>
<p id="section-8.2-6">A change to a Registered Performance Metric <span class="bcp14">SHALL</span> be determined to
        be backward compatible when:<a href="#section-8.2-6" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-8.2-7">
          <li id="section-8.2-7.1">it involves the correction of an error that is obviously only
            editorial, or<a href="#section-8.2-7.1" class="pilcrow">¶</a>
</li>
          <li id="section-8.2-7.2">it corrects an ambiguity in the Registered Performance Metric's
            definition, which itself leads to issues severe enough to prevent
            the Registered Performance Metric's usage as originally defined,
            or<a href="#section-8.2-7.2" class="pilcrow">¶</a>
</li>
          <li id="section-8.2-7.3">it corrects missing information in the metric definition
            without changing its meaning (e.g., the explicit definition of
            'quantity' semantics for numeric fields without a Data Type
            Semantics value), or<a href="#section-8.2-7.3" class="pilcrow">¶</a>
</li>
          <li id="section-8.2-7.4">it harmonizes with an external reference that was itself
            corrected, or<a href="#section-8.2-7.4" class="pilcrow">¶</a>
</li>
          <li id="section-8.2-7.5">if the current Registry format has been revised by adding a new
          column that is not relevant to an existing Registered Performance
          Metric (i.e., the new column can be safely filled in with "Not
          Applicable").<a href="#section-8.2-7.5" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-8.2-8">If a Performance Metric revision is deemed permissible and
        backward compatible by the Performance Metrics Experts, according to
        the rules in this document, IANA <span class="bcp14">SHOULD</span> execute the change(s) in the
        Performance Metrics Registry. The requester of the change is appended
        to the original requester in the Performance Metrics Registry. The
        Name of the revised Registered Performance Metric, including the
        RFCXXXXsecY portion of the Name, <span class="bcp14">SHALL</span> remain unchanged even when the
        change is the result of IETF Standards Action. The revised Registry
        Entry <span class="bcp14">SHOULD</span> reference the new immutable document, such as an RFC. For other standards bodies, it is likely to be necessary to reference
        a specific, dated version of a specification, in an appropriate
        category and column.<a href="#section-8.2-8" class="pilcrow">¶</a></p>
<p id="section-8.2-9">Each Registered Performance Metric in the Performance Metrics
        Registry has a revision number, starting at zero. Each change to a
        Registered Performance Metric following this process increments the
        revision number by one.<a href="#section-8.2-9" class="pilcrow">¶</a></p>
<p id="section-8.2-10">When a revised Registered Performance Metric is accepted into the
        Performance Metrics Registry, the date of acceptance of the most
        recent revision is placed into the Revision Date column of the
        Registry for that Registered Performance Metric.<a href="#section-8.2-10" class="pilcrow">¶</a></p>
<p id="section-8.2-11">Where applicable, additions to Registered Performance Metrics in
        the form of text in the Comments or Remarks column should include the date, but such
        additions may not constitute a revision according to this process.<a href="#section-8.2-11" class="pilcrow">¶</a></p>
<p id="section-8.2-12">Older versions of the updated Metric Entries are kept in the
        Registry for archival purposes. The older entries are kept with all
        fields unmodified (including Revision Date) except for the Status field,
        which <span class="bcp14">SHALL</span> be changed to 'Deprecated'.<a href="#section-8.2-12" class="pilcrow">¶</a></p>
<p id="section-8.2-13">This process should not in any way be construed as allowing the
   Performance Metrics Experts to overrule IETF consensus.
   Specifically, any Registered Performance Metrics that were added to
   the Performance Metrics Registry with IETF consensus require IETF
   consensus for revision or deprecation.<a href="#section-8.2-13" class="pilcrow">¶</a></p>
</section>
</div>
<div id="deprecating-metrics">
<section id="section-8.3">
        <h3 id="name-non-backward-compatible-dep">
<a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-non-backward-compatible-dep" class="section-name selfRef">Non-Backward-Compatible Deprecation of Registered Performance Metrics</a>
        </h3>
<p id="section-8.3-1">This section describes how to make a non-backward-compatible update
        to a Registered Performance Metric. A Registered Performance Metric
        <span class="bcp14">MAY</span> be deprecated and replaced when:<a href="#section-8.3-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-8.3-2">
          <li id="section-8.3-2.1">the Registered Performance Metric definition has an error or
            shortcoming that cannot be permissibly changed per <a href="#revise-reg-perf-metrics" class="xref">Section 8.2</a>
            ("Revising Registered Performance Metrics"), or<a href="#section-8.3-2.1" class="pilcrow">¶</a>
</li>
          <li id="section-8.3-2.2">the deprecation harmonizes with an external reference that was
            itself deprecated through that reference's accepted deprecation
            method.<a href="#section-8.3-2.2" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-8.3-3">A request for deprecation is sent to IANA, which passes it to the
        Performance Metrics Experts for review. When deprecating a Performance
        Metric, the Performance Metric Description in the Performance Metrics
        Registry <span class="bcp14">MUST</span> be updated to explain the deprecation, as well as to
        refer to the new Performance Metric created to replace the deprecated
        Performance Metric.<a href="#section-8.3-3" class="pilcrow">¶</a></p>
<p id="section-8.3-4">When a new, non-backward-compatible Performance Metric replaces a
        (now) deprecated metric, the revision number of the new Registered
        Performance Metric is incremented over the value in the deprecated
        version, and the current date is entered as the Revision Date of the
        new Registered Performance Metric.<a href="#section-8.3-4" class="pilcrow">¶</a></p>
<p id="section-8.3-5">The intentional use of deprecated Registered Performance Metrics
        should result in a log entry or human-readable warning by the
        respective application.<a href="#section-8.3-5" class="pilcrow">¶</a></p>
<p id="section-8.3-6">Names and Metric IDs of deprecated Registered Performance Metrics
        must not be reused.<a href="#section-8.3-6" class="pilcrow">¶</a></p>
<p id="section-8.3-7">The deprecated entries are kept with all Administrative columns
        unmodified, except the Status field (which is changed to
        'Deprecated').<a href="#section-8.3-7" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-8.4">
        <h3 id="name-obsolete-registry-entries">
<a href="#section-8.4" class="section-number selfRef">8.4. </a><a href="#name-obsolete-registry-entries" class="section-name selfRef">Obsolete Registry Entries</a>
        </h3>
<p id="section-8.4-1">Existing Registry Entries may become obsolete over time due to:<a href="#section-8.4-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-8.4-2">
         <li id="section-8.4-2.1">the Registered Performance Metric is found to contain considerable
       errors (and no one sees the value in the effort to fix it), or<a href="#section-8.4-2.1" class="pilcrow">¶</a>
</li>
          <li id="section-8.4-2.2">one or more critical References (or sections thereof) have been
        designated obsolete by the SDO, or<a href="#section-8.4-2.2" class="pilcrow">¶</a>
</li>
          <li id="section-8.4-2.3">other reasons brought to the attention of IANA and the Registry
       Experts.<a href="#section-8.4-2.3" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-8.4-3">When a Performance Metric Registry Entry is declared obsolete, the
 Performance Metric Description in the Performance Metrics Registry is
 updated to explain the reasons the Entry is now obsolete and has not
 been replaced (Deprecation always involves replacement).<a href="#section-8.4-3" class="pilcrow">¶</a></p>
<p id="section-8.4-4"> Obsolete entries are kept with all Administrative columns
        unmodified, except the Status field (which is changed to
        'Obsolete').<a href="#section-8.4-4" class="pilcrow">¶</a></p>
</section>
<section id="section-8.5">
        <h3 id="name-registry-format-version-and">
<a href="#section-8.5" class="section-number selfRef">8.5. </a><a href="#name-registry-format-version-and" class="section-name selfRef">Registry Format Version and Future Changes/Extensions</a>
        </h3>
<p id="section-8.5-1">The Registry Format Version defined in this memo is 1.0, and candidate
   Registry Entries complying with this memo <span class="bcp14">MUST</span> use 1.0.<a href="#section-8.5-1" class="pilcrow">¶</a></p>
<p id="section-8.5-2">The Registry Format can only be updated by publishing a new RFC with
   the new format (Standards Action).<a href="#section-8.5-2" class="pilcrow">¶</a></p>
<p id="section-8.5-3">When a Registered Performance Metric is created or revised, then it
   uses the most recent Registry Format Version.<a href="#section-8.5-3" class="pilcrow">¶</a></p>
<p id="section-8.5-4">Only one form of Registry extension is envisaged:<a href="#section-8.5-4" class="pilcrow">¶</a></p>
<p style="margin-left: 1.5em" id="section-8.5-5">Adding columns, or both categories and columns, to accommodate
   unanticipated aspects of new measurements and metric categories.<a href="#section-8.5-5" class="pilcrow">¶</a></p>
<p id="section-8.5-6">If the Performance Metrics Registry is extended in this way, the
   version number of future entries complying with the extension <span class="bcp14">SHALL</span>
   be incremented (in either the unit or the tenths digit, depending
   on the degree of extension).<a href="#section-8.5-6" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<section id="section-9">
      <h2 id="name-security-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-9-1">This document defines a Registry structure and does not itself
      introduce any new security considerations for the Internet. The
      definition of Performance Metrics for this Registry may introduce some
      security concerns, but the mandatory references should have their own
      considerations for security, and such definitions should be reviewed
      with security in mind if the security considerations are not covered by
      one or more reference standards.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2">The aggregated results of the Performance Metrics described in this
      Registry might reveal network topology information that may be
      considered sensitive. If such cases are found, then access control
      mechanisms should be applied.<a href="#section-9-2" class="pilcrow">¶</a></p>
</section>
<div id="iana-cons">
<section id="section-10">
      <h2 id="name-iana-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-10-1">With the background and processes described in earlier sections, IANA 
      has taken the actions described below.<a href="#section-10-1" class="pilcrow">¶</a></p>
<section id="section-10.1">
        <h3 id="name-registry-group">
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-registry-group" class="section-name selfRef">Registry Group</a>
        </h3>
<p id="section-10.1-1">The new Registry group is named Performance Metrics. This document
        refers to it as the "Performance Metrics Group" or "Registry Group",
        meaning all registrations appearing on <a href="https://www.iana.org/assignments/performance-metrics">&lt;https://www.iana.org/assignments/performance-metrics&gt;</a>.<a href="#section-10.1-1" class="pilcrow">¶</a></p>
<p id="section-10.1-2">For clarity, note that this document and <span>[<a href="#RFC8912" class="xref">RFC8912</a>]</span>
 use the following conventions to refer to the various IANA registries
 related to Performance Metrics.<a href="#section-10.1-2" class="pilcrow">¶</a></p>
<div id="IANAterms-map">
<table class="center" id="table-6">
          <caption><a href="#table-6" class="selfRef">Table 6</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1"></th>
              <th class="text-left" rowspan="1" colspan="1">RFC 8911 and RFC 8912</th>
              <th class="text-left" rowspan="1" colspan="1">IANA Web page</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">Page Title</td>
              <td class="text-left" rowspan="1" colspan="1">Performance Metrics Group</td>
              <td class="text-left" rowspan="1" colspan="1">Performance Metrics</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">Main Registry</td>
              <td class="text-left" rowspan="1" colspan="1">Performance Metrics Registry</td>
              <td class="text-left" rowspan="1" colspan="1">Performance Metrics Registry</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">Registry Row</td>
              <td class="text-left" rowspan="1" colspan="1">Performance Metrics Registry Entry</td>
              <td class="text-left" rowspan="1" colspan="1">registration (also template)</td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-10.1-4">Registration Procedure: Specification Required<a href="#section-10.1-4" class="pilcrow">¶</a></p>
<p id="section-10.1-5">Reference: RFC 8911<a href="#section-10.1-5" class="pilcrow">¶</a></p>
<p id="section-10.1-6">Experts: Performance Metrics Experts<a href="#section-10.1-6" class="pilcrow">¶</a></p>
</section>
<section id="section-10.2">
        <h3 id="name-performance-metrics-name-el">
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-performance-metrics-name-el" class="section-name selfRef">Performance Metrics Name Elements</a>
        </h3>
<p id="section-10.2-1">This memo specifies and populates the Registries for the
        Performance Metric Name Elements.  The Name assigned to a Performance
        Metric Registry Entry consists of multiple Elements separated by an
        "_" (underscore), in the order defined in <a href="#name-sec7-1-2" class="xref">Section 7.1.2</a>.  IANA has created the following registries,
        which contain the current set of possibilities for each Element in the
        Performance Metric Name.<a href="#section-10.2-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-10.2-2.1">MetricType<a href="#section-10.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.2-2.2">Method<a href="#section-10.2-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.2-2.3">SubTypeMethod<a href="#section-10.2-2.3" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.2-2.4">Spec<a href="#section-10.2-2.4" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.2-2.5">Units<a href="#section-10.2-2.5" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.2-2.6">Output<a href="#section-10.2-2.6" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-10.2-3">At creation, IANA has populated the Registered Performance Metrics Name Elements 
        using the lists of values for each Name
        Element listed in <a href="#name-sec7-1-2" class="xref">Section 7.1.2</a>. The Name Elements in each Registry
        are case sensitive.<a href="#section-10.2-3" class="pilcrow">¶</a></p>
<p id="section-10.2-4">When preparing a Metric Entry for registration, the developer
        <span class="bcp14">SHOULD</span> choose Name Elements from among the registered elements.
        However, if the proposed metric is unique in a significant way, it may
        be necessary to propose a new Name Element to properly describe the
        metric, as described below.<a href="#section-10.2-4" class="pilcrow">¶</a></p>
<p id="section-10.2-5">A candidate Metric Entry proposes a set of values for its Name
        Elements. These are reviewed by IANA and an Expert Reviewer. It is
        possible that a candidate Metric Entry proposes a new value for a Name
        Element (that is, one that is not in the existing list of
        possibilities), or even that it proposes a new Name Element. Such new
        assignments are administered by IANA through the Specification
        Required policy <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>, which includes Expert Review (i.e., review
        by one of a group of Performance Metrics Experts, who are appointed by
        the IESG upon recommendation of the Transport Area Directors).<a href="#section-10.2-5" class="pilcrow">¶</a></p>
</section>
<section id="section-10.3">
        <h3 id="name-new-performance-metrics-reg">
<a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-new-performance-metrics-reg" class="section-name selfRef">New Performance Metrics Registry</a>
        </h3>
<p id="section-10.3-1">This document specifies the Performance Metrics Registry. 
        The Registry contains the following columns in the Summary category:<a href="#section-10.3-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-10.3-2.1">Identifier<a href="#section-10.3-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.2">Name<a href="#section-10.3-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.3">URI<a href="#section-10.3-2.3" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.4">Description<a href="#section-10.3-2.4" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.5">Reference<a href="#section-10.3-2.5" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.6">Change Controller<a href="#section-10.3-2.6" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-10.3-2.7">Version<a href="#section-10.3-2.7" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-10.3-3">Descriptions of these columns and additional information
        found in the template for Registry Entries (categories and columns)
        are further defined in <a href="#columns" class="xref">Section 7</a>.<a href="#section-10.3-3" class="pilcrow">¶</a></p>
<p id="section-10.3-4">The Identifier 0 should be Reserved. The Registered Performance
        Metric unique Identifier is an unbounded integer (range 0 to
        infinity). The Identifier values from 64512 to 65535 are reserved for
        private or experimental use, and the user may encounter overlapping
        uses. When adding new Registered Performance Metrics to the
        Performance Metrics Registry, IANA <span class="bcp14">SHOULD</span> assign the lowest available
        Identifier to the new Registered Performance Metric. If a Performance
        Metrics Expert providing review determines that there is a reason to
        assign a specific numeric Identifier, possibly leaving a temporary gap
        in the numbering, then the Performance Metrics Expert <span class="bcp14">SHALL</span> inform IANA of
        this decision.<a href="#section-10.3-4" class="pilcrow">¶</a></p>
<p id="section-10.3-5">Names starting with the prefix "Priv_" are reserved for private use
        and are not considered for registration. The Name column entries are
        further defined in <a href="#columns" class="xref">Section 7</a>.<a href="#section-10.3-5" class="pilcrow">¶</a></p>
<p id="section-10.3-6">The URI column will have a URL to each completed
        Registry Entry. The Registry Entry text <span class="bcp14">SHALL</span> be HTMLized to aid the
        reader (similar to the way that Internet-Drafts are HTMLized, the same tool can perform the function), with links to referenced section(s) of an RFC or another
        immutable document.<a href="#section-10.3-6" class="pilcrow">¶</a></p>
<p id="section-10.3-7">The Reference column will include an RFC number, an approved
        specification designator from another standards body, or some other
        immutable document.<a href="#section-10.3-7" class="pilcrow">¶</a></p>
<p id="section-10.3-8">New assignments for the Performance Metrics Registry will be
   administered by IANA through the Specification Required policy
   <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span> (which includes Expert Review, i.e., review by one of a
   group of experts -- in the case of this document, the Performance
   Metrics Experts, who are appointed by the IESG upon recommendation of
   the Transport Area Directors) or by Standards Action.  The experts can be initially drawn
        from the Working Group Chairs, document editors, and members of the
        Performance Metrics Directorate, among other sources of experts.<a href="#section-10.3-8" class="pilcrow">¶</a></p>
<p id="section-10.3-9">Extensions to the Performance Metrics Registry require IETF
        Standards Action. Only one form of Registry extension is
        envisaged:<a href="#section-10.3-9" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-10.3-10.1">Adding columns, or both categories and columns, to accommodate
            unanticipated aspects of new measurements and metric
            categories.<a href="#section-10.3-10.1" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-10.3-11">If the Performance Metrics Registry is extended in this way,
        the version number of future entries complying with the extension
        <span class="bcp14">SHALL</span> be incremented (in either the unit or the tenths digit, depending on
        the degree of extension).<a href="#section-10.3-11" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="blank-reg-template">
<section id="section-11">
      <h2 id="name-blank-registry-template">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-blank-registry-template" class="section-name selfRef">Blank Registry Template</a>
      </h2>
<p id="section-11-1">This section provides a blank template to help IANA and Registry
      Entry writers.<a href="#section-11-1" class="pilcrow">¶</a></p>
<section id="section-11.1">
        <h3 id="name-summary">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-summary" class="section-name selfRef">Summary</a>
        </h3>
<p id="section-11.1-1">This category includes multiple indexes to the Registry Entry: the
        element ID and Metric Name.<a href="#section-11.1-1" class="pilcrow">¶</a></p>
<section id="section-11.1.1">
          <h4 id="name-id-identifier">
<a href="#section-11.1.1" class="section-number selfRef">11.1.1. </a><a href="#name-id-identifier" class="section-name selfRef">ID (Identifier)</a>
          </h4>
<p id="section-11.1.1-1">&lt;insert a numeric Identifier, an integer, TBD&gt;<a href="#section-11.1.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.2">
          <h4 id="name-name-2">
<a href="#section-11.1.2" class="section-number selfRef">11.1.2. </a><a href="#name-name-2" class="section-name selfRef">Name</a>
          </h4>
<p id="section-11.1.2-1">&lt;insert the Name, according to the metric naming convention&gt;<a href="#section-11.1.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.3">
          <h4 id="name-uri-2">
<a href="#section-11.1.3" class="section-number selfRef">11.1.3. </a><a href="#name-uri-2" class="section-name selfRef">URI</a>
          </h4>
<p id="section-11.1.3-1">URL: <span><a href="https://www.iana.org/assignments/performance-metrics/">https://www.iana.org/assignments/performance-metrics/</a></span>
          ... &lt;Name&gt;<a href="#section-11.1.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.4">
          <h4 id="name-description-2">
<a href="#section-11.1.4" class="section-number selfRef">11.1.4. </a><a href="#name-description-2" class="section-name selfRef">Description</a>
          </h4>
<p id="section-11.1.4-1">&lt;provide a description&gt;<a href="#section-11.1.4-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.5">
          <h4 id="name-reference-2">
<a href="#section-11.1.5" class="section-number selfRef">11.1.5. </a><a href="#name-reference-2" class="section-name selfRef">Reference</a>
          </h4>
<p id="section-11.1.5-1">&lt;provide the RFC or other specification
          that contains the approved candidate Registry Entry&gt;<a href="#section-11.1.5-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.6">
          <h4 id="name-change-controller-2">
<a href="#section-11.1.6" class="section-number selfRef">11.1.6. </a><a href="#name-change-controller-2" class="section-name selfRef">Change Controller</a>
          </h4>
<p id="section-11.1.6-1">&lt;provide information regarding the entity responsible for
          approving revisions to the Registry Entry (including contact information for an individual, where appropriate)&gt;<a href="#section-11.1.6-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.1.7">
          <h4 id="name-version-of-registry-format-2">
<a href="#section-11.1.7" class="section-number selfRef">11.1.7. </a><a href="#name-version-of-registry-format-2" class="section-name selfRef">Version (of Registry Format)</a>
        </h4>
</section>
</section>
<section id="section-11.2">
        <h3 id="name-metric-definition">
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-metric-definition" class="section-name selfRef">Metric Definition</a>
        </h3>
<p id="section-11.2-1">This category includes columns to prompt the entry of all necessary
        details related to the metric definition, including the immutable
        document reference and values of input factors, called "Fixed
        Parameters".<a href="#section-11.2-1" class="pilcrow">¶</a></p>
<section id="section-11.2.1">
          <h4 id="name-reference-definition-3">
<a href="#section-11.2.1" class="section-number selfRef">11.2.1. </a><a href="#name-reference-definition-3" class="section-name selfRef">Reference Definition</a>
          </h4>
<p id="section-11.2.1-1">&lt;provide a full bibliographic reference to an immutable document&gt;<a href="#section-11.2.1-1" class="pilcrow">¶</a></p>
<p id="section-11.2.1-2">&lt;provide a specific section reference and additional clarifications, if
          needed&gt;<a href="#section-11.2.1-2" class="pilcrow">¶</a></p>
</section>
<section id="section-11.2.2">
          <h4 id="name-fixed-parameters-2">
<a href="#section-11.2.2" class="section-number selfRef">11.2.2. </a><a href="#name-fixed-parameters-2" class="section-name selfRef">Fixed Parameters</a>
          </h4>
<p id="section-11.2.2-1">&lt;list and specify Fixed Parameters, input factors that must be
          determined and embedded in the measurement system for use when
          needed&gt;<a href="#section-11.2.2-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-11.3">
        <h3 id="name-method-of-measurement">
<a href="#section-11.3" class="section-number selfRef">11.3. </a><a href="#name-method-of-measurement" class="section-name selfRef">Method of Measurement</a>
        </h3>
<p id="section-11.3-1">This category includes columns for references to relevant sections
        of the immutable document⁠(s) and any supplemental information needed
        to ensure an unambiguous method for implementations.<a href="#section-11.3-1" class="pilcrow">¶</a></p>
<section id="section-11.3.1">
          <h4 id="name-reference-method-2">
<a href="#section-11.3.1" class="section-number selfRef">11.3.1. </a><a href="#name-reference-method-2" class="section-name selfRef">Reference Method</a>
          </h4>
<p id="section-11.3.1-1">&lt;for the metric, insert relevant section references and
          supplemental info&gt;<a href="#section-11.3.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.3.2">
          <h4 id="name-packet-stream-generation-2">
<a href="#section-11.3.2" class="section-number selfRef">11.3.2. </a><a href="#name-packet-stream-generation-2" class="section-name selfRef">Packet Stream Generation</a>
          </h4>
<p id="section-11.3.2-1">&lt;provide a list of generation Parameters and section/spec references if
          needed&gt;<a href="#section-11.3.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.3.3">
          <h4 id="name-traffic-filtering-observati">
<a href="#section-11.3.3" class="section-number selfRef">11.3.3. </a><a href="#name-traffic-filtering-observati" class="section-name selfRef">Traffic Filtering (Observation) Details</a>
          </h4>
<p id="section-11.3.3-1">This category provides the filter details (when present), which
          qualify the set of packets that contribute to the measured results
          from among all packets observed.<a href="#section-11.3.3-1" class="pilcrow">¶</a></p>
<p id="section-11.3.3-2">&lt;provide a section reference&gt;<a href="#section-11.3.3-2" class="pilcrow">¶</a></p>
</section>
<section id="section-11.3.4">
          <h4 id="name-sampling-distribution-2">
<a href="#section-11.3.4" class="section-number selfRef">11.3.4. </a><a href="#name-sampling-distribution-2" class="section-name selfRef">Sampling Distribution</a>
          </h4>
<p id="section-11.3.4-1">&lt;insert time distribution details, or how this is different from
          the filter&gt;<a href="#section-11.3.4-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.3.5">
          <h4 id="name-runtime-parameters-and-data">
<a href="#section-11.3.5" class="section-number selfRef">11.3.5. </a><a href="#name-runtime-parameters-and-data" class="section-name selfRef">Runtime Parameters and Data Format</a>
          </h4>
<p id="section-11.3.5-1">Runtime Parameters are input factors that must be determined,
          configured into the measurement system, and reported with the
          results for the context to be complete.<a href="#section-11.3.5-1" class="pilcrow">¶</a></p>
<p id="section-11.3.5-2">&lt;provide a list of Runtime Parameters and their data formats&gt;<a href="#section-11.3.5-2" class="pilcrow">¶</a></p>
</section>
<section id="section-11.3.6">
          <h4 id="name-roles">
<a href="#section-11.3.6" class="section-number selfRef">11.3.6. </a><a href="#name-roles" class="section-name selfRef">Roles</a>
          </h4>
<p id="section-11.3.6-1">&lt;list the names of the different Roles from the Measurement
          Method&gt;<a href="#section-11.3.6-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-11.4">
        <h3 id="name-output">
<a href="#section-11.4" class="section-number selfRef">11.4. </a><a href="#name-output" class="section-name selfRef">Output</a>
        </h3>
<p id="section-11.4-1">This category specifies all details of the output of measurements
        using the metric.<a href="#section-11.4-1" class="pilcrow">¶</a></p>
<section id="section-11.4.1">
          <h4 id="name-type-2">
<a href="#section-11.4.1" class="section-number selfRef">11.4.1. </a><a href="#name-type-2" class="section-name selfRef">Type</a>
          </h4>
<p id="section-11.4.1-1">&lt;insert the name of the output type -- raw results or a selected summary
          statistic&gt;<a href="#section-11.4.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.4.2">
          <h4 id="name-reference-definition-4">
<a href="#section-11.4.2" class="section-number selfRef">11.4.2. </a><a href="#name-reference-definition-4" class="section-name selfRef">Reference Definition</a>
          </h4>
<p id="section-11.4.2-1">&lt;describe the reference data format for each type of
          result&gt;<a href="#section-11.4.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.4.3">
          <h4 id="name-metric-units-2">
<a href="#section-11.4.3" class="section-number selfRef">11.4.3. </a><a href="#name-metric-units-2" class="section-name selfRef">Metric Units</a>
          </h4>
<p id="section-11.4.3-1">&lt;insert units for the measured results, and provide the reference
          specification&gt;<a href="#section-11.4.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.4.4">
          <h4 id="name-calibration-2">
<a href="#section-11.4.4" class="section-number selfRef">11.4.4. </a><a href="#name-calibration-2" class="section-name selfRef">Calibration</a>
          </h4>
<p id="section-11.4.4-1">&lt;insert information on calibration&gt;<a href="#section-11.4.4-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-11.5">
        <h3 id="name-administrative-items">
<a href="#section-11.5" class="section-number selfRef">11.5. </a><a href="#name-administrative-items" class="section-name selfRef">Administrative Items</a>
        </h3>
<p id="section-11.5-1">This category provides administrative information.<a href="#section-11.5-1" class="pilcrow">¶</a></p>
<section id="section-11.5.1">
          <h4 id="name-status-2">
<a href="#section-11.5.1" class="section-number selfRef">11.5.1. </a><a href="#name-status-2" class="section-name selfRef">Status</a>
          </h4>
<p id="section-11.5.1-1">&lt;provide status: 'Current' or 'Deprecated'&gt;<a href="#section-11.5.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.5.2">
          <h4 id="name-requester-2">
<a href="#section-11.5.2" class="section-number selfRef">11.5.2. </a><a href="#name-requester-2" class="section-name selfRef">Requester</a>
          </h4>
<p id="section-11.5.2-1">&lt;provide a person's name, an RFC number, etc.&gt;<a href="#section-11.5.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.5.3">
          <h4 id="name-revision-2">
<a href="#section-11.5.3" class="section-number selfRef">11.5.3. </a><a href="#name-revision-2" class="section-name selfRef">Revision</a>
          </h4>
<p id="section-11.5.3-1">&lt;provide the revision number: starts at 0&gt;<a href="#section-11.5.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11.5.4">
          <h4 id="name-revision-date-2">
<a href="#section-11.5.4" class="section-number selfRef">11.5.4. </a><a href="#name-revision-date-2" class="section-name selfRef">Revision Date</a>
          </h4>
<p id="section-11.5.4-1">&lt;provide the date, in YYYY-MM-DD format&gt;<a href="#section-11.5.4-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-11.6">
        <h3 id="name-comments-and-remarks-2">
<a href="#section-11.6" class="section-number selfRef">11.6. </a><a href="#name-comments-and-remarks-2" class="section-name selfRef">Comments and Remarks</a>
        </h3>
<p id="section-11.6-1">&lt;list any additional (informational) details for this entry&gt;<a href="#section-11.6-1" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<section id="section-12">
      <h2 id="name-references">
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-12.1">
        <h3 id="name-normative-references">
<a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="RFC2026">[RFC2026]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"The Internet Standards Process -- Revision 3"</span>, <span class="seriesInfo">BCP 9</span>, <span class="seriesInfo">RFC 2026</span>, <span class="seriesInfo">DOI 10.17487/RFC2026</span>, <time datetime="1996-10" class="refDate">October 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2026">https://www.rfc-editor.org/info/rfc2026</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2330">[RFC2330]</dt>
        <dd>
<span class="refAuthor">Paxson, V.</span>, <span class="refAuthor">Almes, G.</span>, <span class="refAuthor">Mahdavi, J.</span>, and <span class="refAuthor">M. Mathis</span>, <span class="refTitle">"Framework for IP Performance Metrics"</span>, <span class="seriesInfo">RFC 2330</span>, <span class="seriesInfo">DOI 10.17487/RFC2330</span>, <time datetime="1998-05" class="refDate">May 1998</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2330">https://www.rfc-editor.org/info/rfc2330</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3986">[RFC3986]</dt>
        <dd>
<span class="refAuthor">Berners-Lee, T.</span>, <span class="refAuthor">Fielding, R.</span>, and <span class="refAuthor">L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5644">[RFC5644]</dt>
        <dd>
<span class="refAuthor">Stephan, E.</span>, <span class="refAuthor">Liang, L.</span>, and <span class="refAuthor">A. Morton</span>, <span class="refTitle">"IP Performance Metrics (IPPM): Spatial and Multicast"</span>, <span class="seriesInfo">RFC 5644</span>, <span class="seriesInfo">DOI 10.17487/RFC5644</span>, <time datetime="2009-10" class="refDate">October 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5644">https://www.rfc-editor.org/info/rfc5644</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6390">[RFC6390]</dt>
        <dd>
<span class="refAuthor">Clark, A.</span> and <span class="refAuthor">B. Claise</span>, <span class="refTitle">"Guidelines for Considering New Performance Metric Development"</span>, <span class="seriesInfo">BCP 170</span>, <span class="seriesInfo">RFC 6390</span>, <span class="seriesInfo">DOI 10.17487/RFC6390</span>, <time datetime="2011-10" class="refDate">October 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6390">https://www.rfc-editor.org/info/rfc6390</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6576">[RFC6576]</dt>
        <dd>
<span class="refAuthor">Geib, R., Ed.</span>, <span class="refAuthor">Morton, A.</span>, <span class="refAuthor">Fardid, R.</span>, and <span class="refAuthor">A. Steinmitz</span>, <span class="refTitle">"IP Performance Metrics (IPPM) Standard Advancement Testing"</span>, <span class="seriesInfo">BCP 176</span>, <span class="seriesInfo">RFC 6576</span>, <span class="seriesInfo">DOI 10.17487/RFC6576</span>, <time datetime="2012-03" class="refDate">March 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6576">https://www.rfc-editor.org/info/rfc6576</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7799">[RFC7799]</dt>
        <dd>
<span class="refAuthor">Morton, A.</span>, <span class="refTitle">"Active and Passive Metrics and Methods (with Hybrid Types In-Between)"</span>, <span class="seriesInfo">RFC 7799</span>, <span class="seriesInfo">DOI 10.17487/RFC7799</span>, <time datetime="2016-05" class="refDate">May 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7799">https://www.rfc-editor.org/info/rfc7799</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8126">[RFC8126]</dt>
        <dd>
<span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
      <dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-12.2">
        <h3 id="name-informative-references">
<a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="RFC2681">[RFC2681]</dt>
        <dd>
<span class="refAuthor">Almes, G.</span>, <span class="refAuthor">Kalidindi, S.</span>, and <span class="refAuthor">M. Zekauskas</span>, <span class="refTitle">"A Round-trip Delay Metric for IPPM"</span>, <span class="seriesInfo">RFC 2681</span>, <span class="seriesInfo">DOI 10.17487/RFC2681</span>, <time datetime="1999-09" class="refDate">September 1999</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2681">https://www.rfc-editor.org/info/rfc2681</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3432">[RFC3432]</dt>
        <dd>
<span class="refAuthor">Raisanen, V.</span>, <span class="refAuthor">Grotefeld, G.</span>, and <span class="refAuthor">A. Morton</span>, <span class="refTitle">"Network performance measurement with periodic streams"</span>, <span class="seriesInfo">RFC 3432</span>, <span class="seriesInfo">DOI 10.17487/RFC3432</span>, <time datetime="2002-11" class="refDate">November 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3432">https://www.rfc-editor.org/info/rfc3432</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3550">[RFC3550]</dt>
        <dd>
<span class="refAuthor">Schulzrinne, H.</span>, <span class="refAuthor">Casner, S.</span>, <span class="refAuthor">Frederick, R.</span>, and <span class="refAuthor">V. Jacobson</span>, <span class="refTitle">"RTP: A Transport Protocol for Real-Time Applications"</span>, <span class="seriesInfo">STD 64</span>, <span class="seriesInfo">RFC 3550</span>, <span class="seriesInfo">DOI 10.17487/RFC3550</span>, <time datetime="2003-07" class="refDate">July 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3550">https://www.rfc-editor.org/info/rfc3550</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3611">[RFC3611]</dt>
        <dd>
<span class="refAuthor">Friedman, T., Ed.</span>, <span class="refAuthor">Caceres, R., Ed.</span>, and <span class="refAuthor">A. Clark, Ed.</span>, <span class="refTitle">"RTP Control Protocol Extended Reports (RTCP XR)"</span>, <span class="seriesInfo">RFC 3611</span>, <span class="seriesInfo">DOI 10.17487/RFC3611</span>, <time datetime="2003-11" class="refDate">November 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3611">https://www.rfc-editor.org/info/rfc3611</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4148">[RFC4148]</dt>
        <dd>
<span class="refAuthor">Stephan, E.</span>, <span class="refTitle">"IP Performance Metrics (IPPM) Metrics Registry"</span>, <span class="seriesInfo">BCP 108</span>, <span class="seriesInfo">RFC 4148</span>, <span class="seriesInfo">DOI 10.17487/RFC4148</span>, <time datetime="2005-08" class="refDate">August 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4148">https://www.rfc-editor.org/info/rfc4148</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5474">[RFC5474]</dt>
        <dd>
<span class="refAuthor">Duffield, N., Ed.</span>, <span class="refAuthor">Chiou, D.</span>, <span class="refAuthor">Claise, B.</span>, <span class="refAuthor">Greenberg, A.</span>, <span class="refAuthor">Grossglauser, M.</span>, and <span class="refAuthor">J. Rexford</span>, <span class="refTitle">"A Framework for Packet Selection and Reporting"</span>, <span class="seriesInfo">RFC 5474</span>, <span class="seriesInfo">DOI 10.17487/RFC5474</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5474">https://www.rfc-editor.org/info/rfc5474</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5475">[RFC5475]</dt>
        <dd>
<span class="refAuthor">Zseby, T.</span>, <span class="refAuthor">Molina, M.</span>, <span class="refAuthor">Duffield, N.</span>, <span class="refAuthor">Niccolini, S.</span>, and <span class="refAuthor">F. Raspall</span>, <span class="refTitle">"Sampling and Filtering Techniques for IP Packet Selection"</span>, <span class="seriesInfo">RFC 5475</span>, <span class="seriesInfo">DOI 10.17487/RFC5475</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5475">https://www.rfc-editor.org/info/rfc5475</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5477">[RFC5477]</dt>
        <dd>
<span class="refAuthor">Dietz, T.</span>, <span class="refAuthor">Claise, B.</span>, <span class="refAuthor">Aitken, P.</span>, <span class="refAuthor">Dressler, F.</span>, and <span class="refAuthor">G. Carle</span>, <span class="refTitle">"Information Model for Packet Sampling Exports"</span>, <span class="seriesInfo">RFC 5477</span>, <span class="seriesInfo">DOI 10.17487/RFC5477</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5477">https://www.rfc-editor.org/info/rfc5477</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6035">[RFC6035]</dt>
        <dd>
<span class="refAuthor">Pendleton, A.</span>, <span class="refAuthor">Clark, A.</span>, <span class="refAuthor">Johnston, A.</span>, and <span class="refAuthor">H. Sinnreich</span>, <span class="refTitle">"Session Initiation Protocol Event Package for Voice Quality Reporting"</span>, <span class="seriesInfo">RFC 6035</span>, <span class="seriesInfo">DOI 10.17487/RFC6035</span>, <time datetime="2010-11" class="refDate">November 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6035">https://www.rfc-editor.org/info/rfc6035</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6248">[RFC6248]</dt>
        <dd>
<span class="refAuthor">Morton, A.</span>, <span class="refTitle">"RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are Obsolete"</span>, <span class="seriesInfo">RFC 6248</span>, <span class="seriesInfo">DOI 10.17487/RFC6248</span>, <time datetime="2011-04" class="refDate">April 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6248">https://www.rfc-editor.org/info/rfc6248</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6991">[RFC6991]</dt>
        <dd>
<span class="refAuthor">Schoenwaelder, J., Ed.</span>, <span class="refTitle">"Common YANG Data Types"</span>, <span class="seriesInfo">RFC 6991</span>, <span class="seriesInfo">DOI 10.17487/RFC6991</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6991">https://www.rfc-editor.org/info/rfc6991</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7012">[RFC7012]</dt>
        <dd>
<span class="refAuthor">Claise, B., Ed.</span> and <span class="refAuthor">B. Trammell, Ed.</span>, <span class="refTitle">"Information Model for IP Flow Information Export (IPFIX)"</span>, <span class="seriesInfo">RFC 7012</span>, <span class="seriesInfo">DOI 10.17487/RFC7012</span>, <time datetime="2013-09" class="refDate">September 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7012">https://www.rfc-editor.org/info/rfc7012</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7014">[RFC7014]</dt>
        <dd>
<span class="refAuthor">D'Antonio, S.</span>, <span class="refAuthor">Zseby, T.</span>, <span class="refAuthor">Henke, C.</span>, and <span class="refAuthor">L. Peluso</span>, <span class="refTitle">"Flow Selection Techniques"</span>, <span class="seriesInfo">RFC 7014</span>, <span class="seriesInfo">DOI 10.17487/RFC7014</span>, <time datetime="2013-09" class="refDate">September 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7014">https://www.rfc-editor.org/info/rfc7014</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7594">[RFC7594]</dt>
        <dd>
<span class="refAuthor">Eardley, P.</span>, <span class="refAuthor">Morton, A.</span>, <span class="refAuthor">Bagnulo, M.</span>, <span class="refAuthor">Burbridge, T.</span>, <span class="refAuthor">Aitken, P.</span>, and <span class="refAuthor">A. Akhter</span>, <span class="refTitle">"A Framework for Large-Scale Measurement of Broadband Performance (LMAP)"</span>, <span class="seriesInfo">RFC 7594</span>, <span class="seriesInfo">DOI 10.17487/RFC7594</span>, <time datetime="2015-09" class="refDate">September 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7594">https://www.rfc-editor.org/info/rfc7594</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7679">[RFC7679]</dt>
        <dd>
<span class="refAuthor">Almes, G.</span>, <span class="refAuthor">Kalidindi, S.</span>, <span class="refAuthor">Zekauskas, M.</span>, and <span class="refAuthor">A. Morton, Ed.</span>, <span class="refTitle">"A One-Way Delay Metric for IP Performance Metrics (IPPM)"</span>, <span class="seriesInfo">STD 81</span>, <span class="seriesInfo">RFC 7679</span>, <span class="seriesInfo">DOI 10.17487/RFC7679</span>, <time datetime="2016-01" class="refDate">January 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7679">https://www.rfc-editor.org/info/rfc7679</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8912">[RFC8912]</dt>
      <dd>
<span class="refAuthor">Morton, A.</span>, <span class="refAuthor">Bagnulo, M.</span>, <span class="refAuthor">Eardley, P.</span>, and <span class="refAuthor">K. D'Souza</span>, <span class="refTitle">"Initial Performance Metrics Registry Entries"</span>, <span class="seriesInfo">RFC 8912</span>, <span class="seriesInfo">DOI 10.17487/RFC8912</span>, <time datetime="2021-11" class="refDate">November 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8912">https://www.rfc-editor.org/info/rfc8912</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<section id="appendix-A">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="appendix-A-1">Thanks to <span class="contact-name">Brian Trammell</span> and <span class="contact-name">Bill Cerveny</span>, IPPM co-chairs during the development of this
      memo, for leading several brainstorming sessions on this topic. Thanks
      to <span class="contact-name">Barbara Stark</span> and <span class="contact-name">Juergen       Schoenwaelder</span> for the detailed feedback and suggestions. Thanks to
      <span class="contact-name">Andrew McGregor</span> for suggestions on metric
      naming. Thanks to <span class="contact-name">Michelle Cotton</span> for her early
      IANA review, and to <span class="contact-name">Amanda Baber</span> for answering
      questions related to the presentation of the Registry and accessibility
      of the complete template via URL. Thanks to <span class="contact-name">Roni       Even</span> for his review and suggestions to generalize the
      procedures. Thanks to all of the Area Directors for their reviews.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
</section>
<div id="authors-addresses">
<section id="appendix-B">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Marcelo Bagnulo</span></div>
<div dir="auto" class="left"><span class="org">Universidad Carlos III de Madrid</span></div>
<div dir="auto" class="left"><span class="street-address">Av. Universidad 30</span></div>
<div dir="auto" class="left">
<span class="postal-code">28911</span> <span class="locality">Leganes</span> <span class="region">Madrid</span>
</div>
<div dir="auto" class="left"><span class="country-name">Spain</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:34%2091%206249500" class="tel">34 91 6249500</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:marcelo@it.uc3m.es" class="email">marcelo@it.uc3m.es</a>
</div>
<div class="url">
<span>URI:</span>
<a href="http://www.it.uc3m.es" class="url">http://www.it.uc3m.es</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Benoit Claise</span></div>
<div dir="auto" class="left"><span class="org">Huawei</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:benoit.claise@huawei.com" class="email">benoit.claise@huawei.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Philip Eardley</span></div>
<div dir="auto" class="left"><span class="org">BT</span></div>
<div dir="auto" class="left"><span class="street-address">Adastral Park, Martlesham Heath</span></div>
<div dir="auto" class="left"><span class="locality">Ipswich</span></div>
<div dir="auto" class="left"><span class="country-name">United Kingdom</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:philip.eardley@bt.com" class="email">philip.eardley@bt.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Al Morton</span></div>
<div dir="auto" class="left"><span class="org">AT&amp;T Labs</span></div>
<div dir="auto" class="left"><span class="street-address">200 Laurel Avenue South</span></div>
<div dir="auto" class="left">
<span class="locality">Middletown</span>, <span class="region">NJ</span> <span class="postal-code">07748</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:acmorton@att.com" class="email">acmorton@att.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Aamer Akhter</span></div>
<div dir="auto" class="left"><span class="org">Consultant</span></div>
<div dir="auto" class="left"><span class="street-address">118 Timber Hitch</span></div>
<div dir="auto" class="left">
<span class="locality">Cary</span>, <span class="region">NC</span> </div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:aakhter@gmail.com" class="email">aakhter@gmail.com</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>