File: rfc9037.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 (2010 lines) | stat: -rw-r--r-- 74,494 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 9037: Deterministic Networking (DetNet) Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN)</title>
<meta content="Balázs Varga" name="author">
<meta content="János Farkas" name="author">
<meta content="Andrew G. Malis" name="author">
<meta content="Stewart Bryant" name="author">
<meta content="
       
     This document specifies the Deterministic Networking (DetNet) MPLS data plane
     when operating over an IEEE 802.1 Time-Sensitive Networking (TSN) 
  sub-network. This document does not define 
  new procedures or processes.  Whenever this document makes  
  statements or recommendations, they are taken from normative text in the 
  referenced RFCs.
       
    " name="description">
<meta content="xml2rfc 3.8.0" name="generator">
<meta content="9037" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.8.0
    Python 3.6.10
    appdirs 1.4.4
    ConfigArgParse 1.2.3
    google-i18n-address 2.3.5
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.2
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.19.0
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.3.1
    requests 2.22.0
    setuptools 40.6.2
    six 1.14.0
    WeasyPrint 51
-->
<link href="rfc9037.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.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;
}
#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: avoid-page;
  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/rfc9037" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-over-tsn-07" 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 9037</td>
<td class="center">DetNet MPLS over TSN</td>
<td class="right">June 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Varga, et al.</td>
<td class="center">Informational</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/rfc9037" class="eref">9037</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-06" class="published">June 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">B. Varga, <span class="editor">Ed.</span>
</div>
<div class="org">Ericsson</div>
</div>
<div class="author">
      <div class="author-name">J. Farkas</div>
<div class="org">Ericsson</div>
</div>
<div class="author">
      <div class="author-name">A. Malis</div>
<div class="org">Malis Consulting</div>
</div>
<div class="author">
      <div class="author-name">S. Bryant</div>
<div class="org">Futurewei Technologies</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9037</h1>
<h1 id="title">Deterministic Networking (DetNet) Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN)</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
     This document specifies the Deterministic Networking (DetNet) MPLS data plane
     when operating over an IEEE 802.1 Time-Sensitive Networking (TSN) 
  sub-network. This document does not define 
  new procedures or processes.  Whenever this document makes  
  statements or recommendations, they are taken from normative text in the 
  referenced RFCs.<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 document is not an Internet Standards Track specification; it is
            published for informational purposes.<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).  Not all documents
            approved by the IESG are candidates for any level of Internet
            Standard; see 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/rfc9037">https://www.rfc-editor.org/info/rfc9037</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 Simplified BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Simplified BSD License.<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 ulEmpty toc">
<li class="compact ulEmpty toc" 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 ulEmpty toc" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
<ul class="compact ulEmpty toc">
<li class="compact ulEmpty toc" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1" class="keepWithNext"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-terms-used-in-this-document" class="xref">Terms Used in This Document</a></p>
</li>
              <li class="compact ulEmpty toc" id="section-toc.1-1.2.2.2">
                <p id="section-toc.1-1.2.2.2.1" class="keepWithNext"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-abbreviations" class="xref">Abbreviations</a></p>
</li>
            </ul>
</li>
          <li class="compact ulEmpty toc" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-detnet-mpls-data-plane-over" class="xref">DetNet MPLS Data Plane Overview</a></p>
</li>
          <li class="compact ulEmpty toc" 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-detnet-mpls-operation-over-" class="xref">DetNet MPLS Operation over IEEE 802.1 TSN Sub-networks</a></p>
<ul class="compact ulEmpty toc">
<li class="compact ulEmpty toc" 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-functions-for-detnet-flow-t" class="xref">Functions for DetNet Flow to TSN Stream Mapping</a></p>
</li>
              <li class="compact ulEmpty toc" 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-tsn-requirements-of-mpls-de" class="xref">TSN Requirements of MPLS DetNet Nodes</a></p>
</li>
              <li class="compact ulEmpty toc" 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-service-protection-within-t" class="xref">Service Protection within the TSN Sub-network</a></p>
</li>
              <li class="compact ulEmpty toc" id="section-toc.1-1.4.2.4">
                <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-aggregation-during-detnet-f" class="xref">Aggregation during DetNet Flow to TSN Stream Mapping</a></p>
</li>
            </ul>
</li>
          <li class="compact ulEmpty toc" 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-management-and-control-impl" class="xref">Management and Control Implications</a></p>
</li>
          <li class="compact ulEmpty toc" 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-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact ulEmpty toc" 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-iana-considerations" class="xref">IANA Considerations</a></p>
</li>
          <li class="compact ulEmpty toc" 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-references" class="xref">References</a></p>
<ul class="compact ulEmpty toc">
<li class="compact ulEmpty toc" 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-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="compact ulEmpty toc" 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-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact ulEmpty toc" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
</li>
          <li class="compact ulEmpty toc" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="sec_intro">
<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">
    Deterministic Networking (DetNet) is a service that can be offered by a
    network to DetNet flows.  DetNet provides these flows with low packet loss
    rate and assured maximum end-to-end delivery latency.  General background
    and concepts of DetNet can be found in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">
    The DetNet architecture decomposes DetNet-related data plane
    functions into two sub-layers: a service sub-layer and a forwarding sub-layer.
    The service sub-layer is used to provide DetNet service protection and
    reordering. The forwarding sub-layer is used to provide congestion
    protection (low loss, assured latency, and limited reordering)
    leveraging MPLS Traffic Engineering mechanisms.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">
 <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span> specifies the DetNet data plane 
 operation for an MPLS-based PSN.  MPLS-encapsulated 
 DetNet flows can be carried over network technologies that can provide the 
 DetNet-required level of service. This document focuses on the scenario 
 where MPLS (DetNet) nodes are interconnected by an IEEE 802.1 TSN sub-network.
 There is close cooperation between the IETF DetNet Working Group and the IEEE 802.1 Time-Sensitive Networking Task Group (TSN TG).<a href="#section-1-3" class="pilcrow">¶</a></p>
</section>
</div>
<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>
<section id="section-2.1">
        <h3 id="name-terms-used-in-this-document">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-terms-used-in-this-document" class="section-name selfRef">Terms Used in This Document</a>
        </h3>
<p id="section-2.1-1">
   This document uses the terminology established in the DetNet architecture
   <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>
          <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>.  TSN-specific terms are defined in the TSN TG
 of the IEEE 802.1 Working Group.  The reader is assumed
   to be familiar with these documents and their terminology.<a href="#section-2.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-2.2">
        <h3 id="name-abbreviations">
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-abbreviations" class="section-name selfRef">Abbreviations</a>
        </h3>
<p id="section-2.2-1">
   The following abbreviations are used in this document:<a href="#section-2.2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-2.2-2">
          <dt id="section-2.2-2.1">A-Label</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.2">Aggregation label; a special case of an S-Label.<a href="#section-2.2-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.3">d-CW</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.4">DetNet Control Word<a href="#section-2.2-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.5">DetNet</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.6">Deterministic Networking<a href="#section-2.2-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.7">F-Label</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.8">Forwarding label that identifies the LSP used by a 
 DetNet flow.<a href="#section-2.2-2.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.9">FRER</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.10">Frame Replication and Elimination for Redundancy 
 (TSN function)<a href="#section-2.2-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.11">L2</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.12">Layer 2<a href="#section-2.2-2.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.13">L3</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.14">Layer 3<a href="#section-2.2-2.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.15">LSP</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.16">Label Switched Path<a href="#section-2.2-2.16" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.17">MPLS</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.18">Multiprotocol Label Switching<a href="#section-2.2-2.18" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.19">PREOF</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.20">Packet Replication, Elimination, and Ordering Functions<a href="#section-2.2-2.20" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.21">PSN</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.22">Packet Switched Network<a href="#section-2.2-2.22" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.23">PW</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.24">Pseudowire<a href="#section-2.2-2.24" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.25">RSVP-TE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.26">Resource Reservation Protocol - Traffic Engineering<a href="#section-2.2-2.26" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.27">S-Label</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.28">Service label<a href="#section-2.2-2.28" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.29">TSN</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.30">Time-Sensitive Networking<a href="#section-2.2-2.30" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</section>
<div id="sec_dt_dp">
<section id="section-3">
      <h2 id="name-detnet-mpls-data-plane-over">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-detnet-mpls-data-plane-over" class="section-name selfRef">DetNet MPLS Data Plane Overview</a>
      </h2>
<p id="section-3-1">
 The basic approach defined in <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>
 supports the DetNet service sub-layer based on existing PW 
 encapsulations and mechanisms and supports the DetNet forwarding 
 sub-layer based on existing MPLS Traffic Engineering encapsulations 
 and mechanisms.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">
  A node operates on a DetNet flow in the DetNet service sub-layer, i.e., 
  a node processing a DetNet packet that has the service label (S-Label) as the top of stack uses 
  the local context associated with that S-Label, for example, a received 
  forwarding label (F-Label), to determine what local DetNet operation(s) is applied to that 
  packet. An S-Label may be unique when taken from the platform
  label space <span>[<a href="#RFC3031" class="xref">RFC3031</a>]</span>, which would enable correct DetNet flow
  identification regardless of which input interface or LSP the packet arrives 
  on. The service sub-layer functions (i.e., PREOF) use a d-CW.<a href="#section-3-2" class="pilcrow">¶</a></p>
<p id="section-3-3">
    The DetNet MPLS data plane builds on MPLS Traffic Engineering
    encapsulations and mechanisms to provide a forwarding sub-layer that
    is responsible for providing resource allocation and explicit
    routes.  The forwarding sub-layer is supported by one or more
    F-Labels.<a href="#section-3-3" class="pilcrow">¶</a></p>
<p id="section-3-4">
        DetNet edge/relay nodes are DetNet service sub-layer-aware,
        understand the particular needs of DetNet flows, and
        provide both DetNet service and forwarding sub-layer functions.
        They add, remove, and process d-CWs, S-Labels, and F-Labels as
        needed.  MPLS DetNet nodes and transit nodes include
        DetNet forwarding sub-layer functions, notable support for 
        explicit routes, and resource allocation to eliminate (or
        reduce) congestion loss and jitter. Unlike other DetNet node types, 
 transit nodes provide no service sub-layer processing.<a href="#section-3-4" class="pilcrow">¶</a></p>
<p id="section-3-5">
 MPLS (DetNet) nodes and transit nodes interconnected by a TSN 
 sub-network are the primary focus of this document. 
 The mapping of DetNet MPLS flows to TSN Streams and TSN protection 
 mechanisms are covered in <a href="#mpls-over-tsn" class="xref">Section 4</a>.<a href="#section-3-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="mpls-over-tsn">
<section id="section-4">
      <h2 id="name-detnet-mpls-operation-over-">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-detnet-mpls-operation-over-" class="section-name selfRef">DetNet MPLS Operation over IEEE 802.1 TSN Sub-networks</a>
      </h2>
<p id="section-4-1">
 The DetNet WG collaborates with IEEE 802.1 TSN in order to define a 
 common architecture for both Layer 2 and Layer 3 that maintains 
 consistency across diverse networks. Both DetNet MPLS and TSN use
 the same techniques to provide their deterministic service:<a href="#section-4-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4-2.1">
 Service protection<a href="#section-4-2.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.2">
 Resource allocation<a href="#section-4-2.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.3">
 Explicit routes<a href="#section-4-2.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-4-3">
 As described in the DetNet architecture 
 <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>, from the MPLS perspective, a sub-network provides 
         a single-hop connection between MPLS (DetNet) nodes. 
 Functions used for resource allocation and explicit routes 
 are treated as domain internal functions and do not require function
 interworking across the DetNet MPLS network and the TSN sub-network.<a href="#section-4-3" class="pilcrow">¶</a></p>
<p id="section-4-4">
 In the case of the service protection function, due to the similarities of 
 the DetNet PREOF and TSN FRER functions, some level of interworking is 
 possible. However, such interworking is out of scope of this document 
 and left for further study.<a href="#section-4-4" class="pilcrow">¶</a></p>
<p id="section-4-5">
      <a href="#fig_mpls_detnet_to_tsn" class="xref">Figure 1</a> illustrates a scenario where 
   two MPLS (DetNet) nodes are interconnected by a TSN sub-network. Node-1 
   is single-homed, and Node-2 is dual-homed to the TSN sub-network.<a href="#section-4-5" class="pilcrow">¶</a></p>
<span id="name-detnet-enabled-mpls-network"></span><div id="fig_mpls_detnet_to_tsn">
<figure id="figure-1">
        <div class="artwork art-text alignLeft" id="section-4-6.1">
<pre>
   MPLS (DetNet)                 MPLS (DetNet)
      Node-1                        Node-2

   +----------+                  +----------+
&lt;--| Service* |-- DetNet flow ---| Service* |--&gt;
   +----------+                  +----------+
   |Forwarding|                  |Forwarding|
   +--------.-+    &lt;-TSN Str-&gt;   +-.-----.--+
             \      ,-------.     /     /
              +----[ TSN Sub-]---+     /
                   [ network ]--------+
                    `-------'
&lt;---------------- DetNet MPLS ---------------&gt;

Note: * no service sub-layer required for transit nodes
</pre>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
<a href="#name-detnet-enabled-mpls-network" class="selfRef">DetNet-Enabled MPLS Network over a TSN Sub-network</a>
        </figcaption></figure>
</div>
<p id="section-4-7">
 At the time of this writing,
 the TSN TG of the IEEE 802.1 
 Working Group have defined (and are defining) a number of amendments 
 to <span>[<a href="#IEEE8021Q" class="xref">IEEE8021Q</a>]</span> that provide zero 
 congestion loss and bounded latency in bridged networks. Furthermore,
 <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> defines frame replication
 and elimination functions for reliability that should prove both 
 compatible with and useful to DetNet networks. All these functions 
 have to identify flows that require TSN treatment (i.e., applying TSN 
 functions during forwarding).<a href="#section-4-7" class="pilcrow">¶</a></p>
<p id="section-4-8">
        TSN capabilities of the TSN sub-network are made available for MPLS
        (DetNet) flows via the protocol interworking function defined in Annex C.5 of 
        <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span>. For example,
        when applied on the TSN edge port, it can convert an ingress unicast 
 MPLS (DetNet) flow to use a specific Layer 2 multicast destination 
 Media Access Control (MAC) address and a VLAN, in order to direct the packet through a 
 specific path inside the bridged network. 
 A similar interworking function pair at the 
 other end of the TSN sub-network would restore the packet to its 
 original Layer 2 destination MAC address and VLAN.<a href="#section-4-8" class="pilcrow">¶</a></p>
<p id="section-4-9">
        The placement of TSN functions depends on the TSN capabilities of the
        nodes along the path. MPLS (DetNet) nodes may or may not support TSN functions. For
        a given TSN Stream (i.e., DetNet flow), an MPLS (DetNet) node is
        treated as a Talker or a Listener inside the TSN sub-network.<a href="#section-4-9" class="pilcrow">¶</a></p>
<section id="section-4.1">
        <h3 id="name-functions-for-detnet-flow-t">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-functions-for-detnet-flow-t" class="section-name selfRef">Functions for DetNet Flow to TSN Stream Mapping</a>
        </h3>
<p id="section-4.1-1">
              Mapping of a DetNet MPLS flow to a TSN Stream is provided via 
   the combination of a passive and an active Stream identification 
   function that operate at the frame level. The passive Stream
   identification function is used to catch the MPLS label(s) of a 
   DetNet MPLS flow, and the active Stream identification function 
   is used to modify the Ethernet header according to the ID of the 
   mapped TSN Stream.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2">
   Clause 6.8 of <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span> defines a
   Mask-and-Match Stream identification function that can be used 
   as a passive function for MPLS DetNet flows.<a href="#section-4.1-2" class="pilcrow">¶</a></p>
<p id="section-4.1-3">
       Clause 6.6 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> defines an
              Active Destination MAC and a VLAN Stream identification function
              that can replace some Ethernet header fields, namely (1) the
              destination MAC address, (2) the VLAN-ID, and (3) priority
              parameters with alternate values. Replacement is provided for
              the frame that is passed either down the stack from the upper layers or up the
              stack from the lower layers.<a href="#section-4.1-3" class="pilcrow">¶</a></p>
<p id="section-4.1-4">
              Active Destination MAC and VLAN Stream identification can be
              used within a Talker to set flow identity or a Listener to
              recover the original addressing information. It can also be used
              in a TSN bridge that is providing translation as a proxy service
              for an end system.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
</section>
<section id="section-4.2">
        <h3 id="name-tsn-requirements-of-mpls-de">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-tsn-requirements-of-mpls-de" class="section-name selfRef">TSN Requirements of MPLS DetNet Nodes</a>
        </h3>
<p id="section-4.2-1">
              This section covers required behavior of a TSN-aware MPLS (DetNet)
   node using a TSN sub-network. The implementation of TSN packet-processing 
   functions must be compliant with the relevant IEEE 802.1 
   standards.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<p id="section-4.2-2">
              From the TSN sub-network perspective, MPLS (DetNet) nodes are treated 
   as a Talker or Listener, which may be (1) TSN-unaware or 
   (2) TSN-aware.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
<p id="section-4.2-3">
              In cases of TSN-unaware MPLS DetNet nodes, the TSN relay nodes 
   within the TSN sub-network must modify the Ethernet encapsulation 
   of the DetNet MPLS flow (e.g., MAC translation, VLAN-ID setting, 
   sequence number addition, etc.) to allow proper TSN-specific 
   handling inside the sub-network.  There are no requirements 
   defined for TSN-unaware MPLS DetNet nodes in this document.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
<p id="section-4.2-4">
              MPLS (DetNet) nodes that are TSN-aware can be treated as a
              combination of a TSN-unaware Talker/Listener and a TSN-Relay, as
              shown in <a href="#fig_mpls_with_tsn" class="xref">Figure 2</a>.  In such cases, the 
   MPLS (DetNet) node must provide the TSN sub-network-specific 
   Ethernet encapsulation over the link(s) towards the sub-network.<a href="#section-4.2-4" class="pilcrow">¶</a></p>
<span id="name-mpls-detnet-node-with-tsn-f"></span><div id="fig_mpls_with_tsn">
<figure id="figure-2">
          <div class="artwork art-text alignLeft" id="section-4.2-5.1">
<pre>
              MPLS (DetNet)
                  Node
   &lt;----------------------------------&gt;

   +----------+
&lt;--| Service* |-- DetNet flow ------------------
   +----------+
   |Forwarding|
   +----------+    +---------------+
   |    L2    |    | L2 Relay with |&lt;--- TSN ---
   |          |    | TSN function  |    Stream
   +-----.----+    +--.------.---.-+
          \__________/        \   \______
                               \_________
    TSN-unaware
     Talker /          TSN-Bridge
     Listener             Relay
                                       &lt;----- TSN Sub-network -----
   &lt;------- TSN-aware Tlk/Lstn -------&gt;

Note: * no service sub-layer required for transit nodes
</pre>
</div>
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
<a href="#name-mpls-detnet-node-with-tsn-f" class="selfRef">MPLS (DetNet) Node with TSN Functions</a>
          </figcaption></figure>
</div>
<p id="section-4.2-6">
   A TSN-aware MPLS (DetNet) node implementation must support the 
   Stream identification TSN component for recognizing flows.<a href="#section-4.2-6" class="pilcrow">¶</a></p>
<p id="section-4.2-7">
              A Stream identification component must be able to instantiate
              the following functions: (1) Active Destination MAC and VLAN
              Stream identification function, 
   (2) Mask-and-Match Stream identification function, and 
   (3) the related managed objects in Clause 9 of
              <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and 
   <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>.<a href="#section-4.2-7" class="pilcrow">¶</a></p>
<p id="section-4.2-8">
   A TSN-aware MPLS (DetNet) node implementation must support the 
   Sequencing function and the Sequence encode/decode function as 
   defined in Clauses 7.4 and 7.6 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> 
   in order for FRER to be used inside the TSN sub-network.<a href="#section-4.2-8" class="pilcrow">¶</a></p>
<p id="section-4.2-9">
              The Sequence encode/decode function must support the Redundancy
              tag (R-TAG) format as per Clause 7.8 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span>.<a href="#section-4.2-9" class="pilcrow">¶</a></p>
<p id="section-4.2-10">
   A TSN-aware MPLS (DetNet) node implementation must support the 
   Stream splitting 
   function and the Individual recovery function as defined in 
   Clauses 7.5 and 7.7 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> 
   in order for that node to be a replication or elimination 
   point for FRER.<a href="#section-4.2-10" class="pilcrow">¶</a></p>
</section>
<section id="section-4.3">
        <h3 id="name-service-protection-within-t">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-service-protection-within-t" class="section-name selfRef">Service Protection within the TSN Sub-network</a>
        </h3>
<p id="section-4.3-1">
              TSN Streams supporting DetNet flows may use FRER as defined in Clause 8 of
   <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> based on the
              loss service requirements of the TSN Stream, which is derived
              from the DetNet service requirements of the DetNet mapped flow.
              The specific operation of FRER is not modified by the use of
              DetNet and follows <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span>.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
<p id="section-4.3-2">
              FRER function and the provided service recovery is available
              only within the TSN sub-network as the TSN Stream-ID and the TSN
              sequence number are not valid outside the sub-network.  An MPLS
              (DetNet) node represents an L3 border, and as such, it terminates
              all related information elements encoded in the L2 frames.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
<p id="section-4.3-3">
   As the Stream-ID and the TSN sequence number are paired with 
   similar MPLS flow parameters, FRER can be combined with PREOF 
   functions. Such service protection interworking scenarios may 
   require moving sequence number fields among TSN (L2) and PW 
   (MPLS) encapsulations, and they are left for further study.<a href="#section-4.3-3" class="pilcrow">¶</a></p>
</section>
<section id="section-4.4">
        <h3 id="name-aggregation-during-detnet-f">
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-aggregation-during-detnet-f" class="section-name selfRef">Aggregation during DetNet Flow to TSN Stream Mapping</a>
        </h3>
<p id="section-4.4-1">
 Implementation of this document shall use management and
 control information to map a DetNet flow to a TSN
 Stream. N:1 mapping (aggregating DetNet flows in a single
 TSN Stream) shall be supported. The management or control
 function that provisions flow mapping shall ensure that
 adequate resources are allocated and configured to provide
 proper service requirements of the mapped flows.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<section id="section-5">
      <h2 id="name-management-and-control-impl">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-management-and-control-impl" class="section-name selfRef">Management and Control Implications</a>
      </h2>
<p id="section-5-1">
 Information related to DetNet flow and TSN Stream mapping is
 required only for TSN-aware MPLS (DetNet) nodes. From the
 data plane perspective, there is no practical difference
 based on the origin of flow-mapping-related information
 (management plane or control plane).<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">
            The following summarizes the set of information that is needed to
            configure DetNet MPLS over TSN:<a href="#section-5-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5-3.1">DetNet MPLS-related configuration information according to the 
      DetNet role of the DetNet MPLS node, as per 
      <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>.<a href="#section-5-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-3.2">TSN-related configuration information according to the 
      TSN role of the DetNet MPLS node, as per 
  <span>[<a href="#IEEE8021Q" class="xref">IEEE8021Q</a>]</span>, <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span>, and
      <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>.<a href="#section-5-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-3.3">Mapping between a DetNet MPLS flow(s) (label information: 
   A-Labels, S-Labels, and F-Labels as defined in 
   <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>) and a TSN 
   Stream(s) (as Stream identification information defined in 
   <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>).
   Note that managed objects for TSN Stream identification can be 
   found in <span>[<a href="#IEEEP8021CBcv" class="xref">IEEEP8021CBcv</a>]</span>.<a href="#section-5-3.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-5-4">
            This information must be provisioned per DetNet flow.<a href="#section-5-4" class="pilcrow">¶</a></p>
<p id="section-5-5">
 Mappings between DetNet and TSN management and control planes are 
 out of scope of this document. Some of the challenges are 
 highlighted below.<a href="#section-5-5" class="pilcrow">¶</a></p>
<p id="section-5-6">
 TSN-aware MPLS DetNet nodes are members of both the DetNet
 domain and the TSN sub-network.  Within the TSN
 sub-network, the TSN-aware MPLS (DetNet) node has a TSN-aware
 Talker/Listener role, so TSN-specific management and
 control plane functionalities must be implemented.  There
 are many similarities in the management plane techniques
 used in DetNet and TSN, but that is not the case for the
 control plane protocols. For example, RSVP-TE and the
 Multiple Stream Registration Protocol (MSRP)
 behave differently. Therefore, management and control plane
 design are important aspects of scenarios where
 mapping between DetNet and TSN is required.<a href="#section-5-6" class="pilcrow">¶</a></p>
<p id="section-5-7">
       In order to use a TSN sub-network between DetNet nodes,
       DetNet-specific information must be converted to information specific to the TSN
       sub-network. DetNet flow ID and flow-related
       parameters/requirements must be converted to a TSN Stream
       ID and stream-related parameters/requirements.

       Note that,
       as the TSN sub-network is just a portion of the end-to-end
       DetNet path (i.e., a single hop from the MPLS perspective), some
       parameters (e.g., delay) may differ significantly. Other
       parameters (like bandwidth) also may have to be tuned due
       to the L2 encapsulation used within the TSN sub-network.<a href="#section-5-7" class="pilcrow">¶</a></p>
<p id="section-5-8">
       In some cases, it may be challenging to determine some TSN-Stream-related
       information. For example, on a TSN-aware MPLS
       (DetNet) node that acts as a Talker, it is quite obvious
       which DetNet node is the Listener of the mapped TSN Stream
       (i.e., the MPLS next hop). However, it may be not trivial to
       locate the point/interface where that Listener is
       connected to the TSN sub-network. Such attributes may
       require interaction between control and management plane
       functions and between DetNet and TSN domains.<a href="#section-5-8" class="pilcrow">¶</a></p>
<p id="section-5-9">
       Mapping between DetNet flow identifiers and TSN Stream
       identifiers, if not provided explicitly, can be done by a
       TSN-aware MPLS (DetNet) node locally based on information
       provided for configuration of the TSN Stream
       identification functions (Mask-and-Match Stream identification 
   and active Stream identification).<a href="#section-5-9" class="pilcrow">¶</a></p>
<p id="section-5-10">
       Triggering the setup/modification of a TSN Stream in the
       TSN sub-network is an example where management and/or
       control plane interactions are required between the DetNet
       and TSN sub-network. TSN-unaware MPLS (DetNet) nodes make
       such a triggering even more complicated as they are fully
       unaware of the sub-network and run independently.<a href="#section-5-10" class="pilcrow">¶</a></p>
<p id="section-5-11">
       Configuration of TSN-specific functions (e.g., FRER)
       inside the TSN sub-network is a TSN-domain-specific decision 
   and may not be visible in the DetNet domain. Service protection
   interworking scenarios are left for further study.<a href="#section-5-11" class="pilcrow">¶</a></p>
</section>
<section id="section-6">
      <h2 id="name-security-considerations">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-6-1">
   Security considerations for DetNet are described in detail in
   <span>[<a href="#I-D.ietf-detnet-security" class="xref">DETNET-SECURITY</a>]</span>. General security considerations
      are described in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>. 
   Considerations specific to the DetNet MPLS data plane are summarized in 
   <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>. 
   This section considers exclusively security considerations that are 
   specific to the DetNet MPLS over TSN sub-network scenario.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">
   The sub-network between DetNet nodes needs to be subject to appropriate 
   confidentiality. Additionally, knowledge of what DetNet/TSN services are 
   provided by a sub-network may supply information that can be used in a 
   variety of security attacks. The ability to modify information exchanges 
   between connected DetNet nodes may result in bogus operations. Therefore, 
   it is important that the interface between DetNet nodes and the TSN 
   sub-network are subject to authorization, authentication, and encryption.<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">
   The TSN sub-network operates at Layer 2, so various security mechanisms 
   defined by IEEE can be used to secure the connection between the DetNet 
   nodes (e.g., encryption may be provided using MACsec 
   <span>[<a href="#IEEE802.1AE-2018" class="xref">IEEE802.1AE-2018</a>]</span>).<a href="#section-6-3" class="pilcrow">¶</a></p>
</section>
<div id="iana">
<section id="section-7">
      <h2 id="name-iana-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-7-1">
      This document has no IANA actions.<a href="#section-7-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-8">
      <h2 id="name-references">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-8.1">
        <h3 id="name-normative-references">
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="IEEE8021CB">[IEEE8021CB]</dt>
        <dd>
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and metropolitan area networks -- Frame Replication and Elimination for Reliability"</span>, <span class="refContent">IEEE Std 802.1CB-2017</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2017.8091139</span>, <time datetime="2017-10" class="refDate">October 2017</time>, <span>&lt;<a href="https://ieeexplore.ieee.org/document/8091139">https://ieeexplore.ieee.org/document/8091139</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IEEEP8021CBdb">[IEEEP8021CBdb]</dt>
        <dd>
<span class="refAuthor">IEEE</span>, <span class="refTitle">"Draft Standard for Local and metropolitan area networks -- Frame Replication and Elimination for Reliability -- Amendment: Extended Stream Identification Functions"</span>, <span class="refContent">IEEE P802.1CBdb / D1.3</span>, <time datetime="2021-04" class="refDate">April 2021</time>, <span>&lt;<a href="https://1.ieee802.org/tsn/802-1cbdb/">https://1.ieee802.org/tsn/802-1cbdb/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3031">[RFC3031]</dt>
        <dd>
<span class="refAuthor">Rosen, E.</span>, <span class="refAuthor">Viswanathan, A.</span>, and <span class="refAuthor">R. Callon</span>, <span class="refTitle">"Multiprotocol Label Switching Architecture"</span>, <span class="seriesInfo">RFC 3031</span>, <span class="seriesInfo">DOI 10.17487/RFC3031</span>, <time datetime="2001-01" class="refDate">January 2001</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3031">https://www.rfc-editor.org/info/rfc3031</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8655">[RFC8655]</dt>
        <dd>
<span class="refAuthor">Finn, N.</span>, <span class="refAuthor">Thubert, P.</span>, <span class="refAuthor">Varga, B.</span>, and <span class="refAuthor">J. Farkas</span>, <span class="refTitle">"Deterministic Networking Architecture"</span>, <span class="seriesInfo">RFC 8655</span>, <span class="seriesInfo">DOI 10.17487/RFC8655</span>, <time datetime="2019-10" class="refDate">October 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8655">https://www.rfc-editor.org/info/rfc8655</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8964">[RFC8964]</dt>
      <dd>
<span class="refAuthor">Varga, B., Ed.</span>, <span class="refAuthor">Farkas, J.</span>, <span class="refAuthor">Berger, L.</span>, <span class="refAuthor">Malis, A.</span>, <span class="refAuthor">Bryant, S.</span>, and <span class="refAuthor">J. Korhonen</span>, <span class="refTitle">"Deterministic Networking (DetNet) Data Plane: MPLS"</span>, <span class="seriesInfo">RFC 8964</span>, <span class="seriesInfo">DOI 10.17487/RFC8964</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8964">https://www.rfc-editor.org/info/rfc8964</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-8.2">
        <h3 id="name-informative-references">
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="I-D.ietf-detnet-security">[DETNET-SECURITY]</dt>
        <dd>
<span class="refAuthor">Grossman, E., Ed.</span>, <span class="refAuthor">Mizrahi, T.</span>, and <span class="refAuthor">A. Hacker</span>, <span class="refTitle">"Deterministic Networking (DetNet) Security Considerations"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-detnet-security-16</span>, <time datetime="2021-03-02" class="refDate">2 March 2021</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-detnet-security-16">https://tools.ietf.org/html/draft-ietf-detnet-security-16</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IEEE802.1AE-2018">[IEEE802.1AE-2018]</dt>
        <dd>
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and metropolitan area networks-Media Access Control (MAC) Security"</span>, <span class="refContent">IEEE Std 802.1AE-2018</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2018.8585421</span>, <time datetime="2018-12" class="refDate">December 2018</time>, <span>&lt;<a href="https://ieeexplore.ieee.org/document/8585421">https://ieeexplore.ieee.org/document/8585421</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IEEE8021Q">[IEEE8021Q]</dt>
        <dd>
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and metropolitan area networks -- Bridges and Bridged Networks"</span>, <span class="refContent">IEEE Std 802.1Q-2018</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2018.8403927</span>, <time datetime="2018-07" class="refDate">July 2018</time>, <span>&lt;<a href="https://ieeexplore.ieee.org/document/8403927/">https://ieeexplore.ieee.org/document/8403927/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IEEEP8021CBcv">[IEEEP8021CBcv]</dt>
      <dd>
<span class="refAuthor">IEEE 802.1</span>, <span class="refTitle">"Draft Standard for Local and metropolitan area networks -- Frame Replication and Elimination for Reliability -- Amendment: Information Model, YANG Data Model and Management Information Base Module"</span>, <span class="refContent">IEEE P802.1CBcv, Draft 1.1</span>, <time datetime="2021-02" class="refDate">February 2021</time>, <span>&lt;<a href="https://1.ieee802.org/tsn/802-1cbcv/">https://1.ieee802.org/tsn/802-1cbcv/</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="acks">
<section id="section-appendix.a">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="section-appendix.a-1">
 The authors wish to thank <span class="contact-name">Norman Finn</span>,  <span class="contact-name">Lou Berger</span>,  <span class="contact-name">Craig Gunther</span>,
  <span class="contact-name">Christophe Mangin</span>, and  <span class="contact-name">Jouni Korhonen</span> for their various contributions 
 to this work.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="section-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">Balázs Varga (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Ericsson</span></div>
<div dir="auto" class="left"><span class="locality">Budapest</span></div>
<div dir="auto" class="left"><span class="street-address">Magyar Tudosok krt. 11.</span></div>
<div dir="auto" class="left"><span class="postal-code">1117</span></div>
<div dir="auto" class="left"><span class="country-name">Hungary</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:balazs.a.varga@ericsson.com" class="email">balazs.a.varga@ericsson.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">János Farkas</span></div>
<div dir="auto" class="left"><span class="org">Ericsson</span></div>
<div dir="auto" class="left"><span class="locality">Budapest</span></div>
<div dir="auto" class="left"><span class="street-address">Magyar Tudosok krt. 11.</span></div>
<div dir="auto" class="left"><span class="postal-code">1117</span></div>
<div dir="auto" class="left"><span class="country-name">Hungary</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:janos.farkas@ericsson.com" class="email">janos.farkas@ericsson.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Andrew G. Malis</span></div>
<div dir="auto" class="left"><span class="org">Malis Consulting</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:agmalis@gmail.com" class="email">agmalis@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Stewart Bryant</span></div>
<div dir="auto" class="left"><span class="org">Futurewei Technologies</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:sb@stewartbryant.com" class="email">sb@stewartbryant.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>