File: rfc9024.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 (2121 lines) | stat: -rw-r--r-- 83,871 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 9024: Deterministic Networking (DetNet) Data Plane: IEEE 802.1 Time-Sensitive Networking over MPLS</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="Don Fedyk" name="author">
<meta content="
       
     This document specifies the Deterministic Networking data plane
     when Time-Sensitive Networking (TSN) networks are interconnected over a DetNet MPLS network.
       
    " name="description">
<meta content="xml2rfc 3.8.0" name="generator">
<meta content="interconnecting TSN networks" name="keyword">
<meta content="9024" 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="rfc9024.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/rfc9024" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-detnet-tsn-vpn-over-mpls-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 9024</td>
<td class="center">TSN over DetNet MPLS</td>
<td class="right">June 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Varga, 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/rfc9024" class="eref">9024</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-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>
<div class="author">
      <div class="author-name">D. Fedyk</div>
<div class="org">LabN Consulting, L.L.C.</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9024</h1>
<h1 id="title">Deterministic Networking (DetNet) Data Plane: IEEE 802.1 Time-Sensitive Networking over MPLS</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 data plane
     when Time-Sensitive Networking (TSN) networks are interconnected over a DetNet MPLS network.<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/rfc9024">https://www.rfc-editor.org/info/rfc9024</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="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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="ulEmpty toc compact" 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="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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="ulEmpty toc compact" 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>
              <li class="ulEmpty toc compact" id="section-toc.1-1.2.2.3">
                <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-requirements-language" class="xref">Requirements Language</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-ieee-8021-tsn-over-detnet-m" class="xref">IEEE 802.1 TSN over DetNet MPLS Data Plane Scenario</a></p>
</li>
          <li class="ulEmpty toc compact" 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-data-plane" class="xref">DetNet MPLS Data Plane</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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-overview" class="xref">Overview</a></p>
</li>
              <li class="ulEmpty toc compact" 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-over-detnet-mpls-encaps" class="xref">TSN over DetNet MPLS Encapsulation</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-tsn-over-mpls-data-plane-pr" class="xref">TSN over MPLS Data Plane Procedures</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-edge-node-tsn-procedures" class="xref">Edge Node TSN Procedures</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-edge-node-detnet-service-pr" class="xref">Edge Node DetNet Service Proxy Procedures</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-edge-node-detnet-service-an" class="xref">Edge Node DetNet Service and Forwarding Sub-Layer Procedures</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-controller-plane-management" class="xref">Controller Plane (Management and Control) Considerations</a></p>
</li>
          <li class="ulEmpty toc compact" 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-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="ulEmpty toc compact" 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-iana-considerations" class="xref">IANA Considerations</a></p>
</li>
          <li class="ulEmpty toc compact" 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-references" class="xref">References</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.9.2.1">
                <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.9.2.2">
                <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.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">
        The Time-Sensitive Networking Task Group (TSN TG) within the IEEE 802.1 Working 
        Group deals with deterministic services through IEEE 802 networks. 
    Deterministic Networking (DetNet) defined by the IETF is a service that can be 
        offered by an L3 network to DetNet flows.  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">
        This document specifies the use of a DetNet MPLS network to interconnect TSN 
        nodes/network segments. The DetNet MPLS data plane is defined in 
           <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>.<a href="#section-1-2" 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 and concepts established in the DetNet 
        architecture <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>
          <span>[<a href="#RFC8938" class="xref">RFC8938</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">AC</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.2">Attachment Circuit<a href="#section-2.2-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.3">CE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.4">Customer Edge equipment<a href="#section-2.2-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.5">d-CW</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.6">DetNet Control Word<a href="#section-2.2-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.7">DetNet</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.8">Deterministic Networking<a href="#section-2.2-2.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.9">DF</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.10">DetNet Flow<a href="#section-2.2-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.11">FRER</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.12">Frame Replication and Elimination for Redundancy 
        (TSN function)<a href="#section-2.2-2.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.13">L2</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.14">Layer 2<a href="#section-2.2-2.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.15">L2VPN</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.16">Layer 2 Virtual Private Network<a href="#section-2.2-2.16" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.17">L3</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.18">Layer 3<a href="#section-2.2-2.18" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.19">LSP</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.20">Label Switched Path<a href="#section-2.2-2.20" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.21">LSR</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.22">Label Switching Router<a href="#section-2.2-2.22" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.23">MPLS</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.24">Multiprotocol Label Switching<a href="#section-2.2-2.24" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.25">MPLS-TE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.26">Multiprotocol Label Switching - Traffic Engineering<a href="#section-2.2-2.26" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.27">NSP</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.28">Native Service Processing<a href="#section-2.2-2.28" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.29">OAM</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.30">Operations, Administration, and Maintenance<a href="#section-2.2-2.30" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.31">PE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.32">Provider Edge<a href="#section-2.2-2.32" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.33">PREOF</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.34">Packet Replication, Elimination and Ordering Functions<a href="#section-2.2-2.34" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.35">PW</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.36">Pseudowire<a href="#section-2.2-2.36" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.37">S-PE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.38">Switching Provider Edge<a href="#section-2.2-2.38" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.39">T-PE</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.40">Terminating Provider Edge<a href="#section-2.2-2.40" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.2-2.41">TSN</dt>
          <dd style="margin-left: 7.0em" id="section-2.2-2.42">Time-Sensitive Network<a href="#section-2.2-2.42" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
<section id="section-2.3">
        <h3 id="name-requirements-language">
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
        </h3>
<p id="section-2.3-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.3-1" class="pilcrow">¶</a></p>
</section>
</section>
<div id="sec_tsn_mpls_dt_dp_scen">
<section id="section-3">
      <h2 id="name-ieee-8021-tsn-over-detnet-m">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-ieee-8021-tsn-over-detnet-m" class="section-name selfRef">IEEE 802.1 TSN over DetNet MPLS Data Plane Scenario</a>
      </h2>
<p id="section-3-1">
   <a href="#fig_tsn_mpls_detnet" class="xref">Figure 1</a> shows IEEE 802.1 TSN end
   stations operating over a TSN-aware DetNet service running over an MPLS
   network.  DetNet edge nodes sit at the boundary of a DetNet domain. They are
   responsible for mapping non-DetNet-aware L2 traffic to DetNet services.
   They also support the imposition and disposition of the required DetNet
   encapsulation.  These are functionally similar to PW
   T-PE nodes, which use MPLS-TE LSPs.  In this
   example, TSN Streams are simple applications over DetNet flows.  The specifics
   of this operation are discussed later in this document.<a href="#section-3-1" class="pilcrow">¶</a></p>
<span id="name-a-tsn-over-detnet-mpls-enab"></span><div id="fig_tsn_mpls_detnet">
<figure id="figure-1">
        <div class="artwork art-text alignCenter" id="section-3-2.1">
<pre>
   TSN           Edge          Transit         Edge          TSN
End System       Node           Node           Node       End System
                (T-PE)         (LSR)          (T-PE)

+----------+                                             +----------+
|   TSN    | &lt;-------- End-to-End TSN Service ---------&gt; |   TSN    |
|  Applic. |                                             |  Applic. |
+----------+  +.........+                   +.........+  +----------+
|          |  | \S-Proxy:                   :S-Proxy/ |  |          |
|   TSN    |  |   +.+---+&lt;-- DetNet flow --&gt;+---+ |   |  |   TSN    |
|          |  |TSN| |Svc|                   |Svc| |TSN|  |          |
+----------+  +---+ +---+    +----------+   +---+ +---+  +----------+
|   L2     |  | L2| |Fwd|    |Forwarding|   |Fwd| |L2 |  |   L2     |
+------.---+  +-.-+ +-.-+    +---.----.-+   +--.+ +-.-+  +---.------+
       :  Link  :     /  ,-----.  \   :  Link  :   /  ,-----. \
       +........+     +-[  Sub- ]-+   +........+   +-[  TSN  ]-+
                        [Network]                    [Network]
                         `-----'                      `-----'

                    |&lt;------ DetNet MPLS ------&gt;|
        |&lt;---------------------- TSN   ---------------------&gt;|

</pre>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
<a href="#name-a-tsn-over-detnet-mpls-enab" class="selfRef">A TSN over DetNet MPLS-Enabled Network</a>
        </figcaption></figure>
</div>
<p id="section-3-3">
        In this example, edge nodes provide a service proxy function that 
        "associates" the DetNet flows and native flows (i.e., TSN Streams) at
        the edge of the DetNet domain.  TSN Streams are treated as App-flows 
 for DetNet. The whole DetNet domain behaves as a TSN relay node for 
 the TSN Streams. The service proxy behaves as a port of that TSN 
 relay node.<a href="#section-3-3" class="pilcrow">¶</a></p>
<p id="section-3-4">

   <a href="#fig_8021_detnet" class="xref">Figure 2</a> illustrates how DetNet can provide services 
   for IEEE 802.1 TSN end systems, CE1 and CE2, over a DetNet-enabled MPLS 
   network.  Edge nodes E1 and E2 insert and remove the required DetNet data
   plane encapsulation.  The 'X' in the edge nodes and relay node, R1, 
   represent a potential DetNet compound flow packet replication and 
   elimination point.  This conceptually parallels L2VPN services and could
   leverage existing related solutions as discussed below.<a href="#section-3-4" class="pilcrow">¶</a></p>
<span id="name-ieee-8021tsn-over-detnet"></span><div id="fig_8021_detnet">
<figure id="figure-2">
        <div class="artwork art-text alignLeft" id="section-3-5.1">
<pre>
     TSN    |&lt;------- End-to-End DetNet Service ------&gt;|  TSN
    Service |         Transit          Transit         | Service
TSN  (AC)   |        |&lt;-Tnl-&gt;|        |&lt;-Tnl-&gt;|        |  (AC)  TSN
End    |    V        V    1  V        V   2   V        V   |    End
System |    +--------+       +--------+       +--------+   |  System
+---+  |    |   E1   |=======|   R1   |=======|   E2   |   |   +---+
|   |--|----|._X_....|..DF1..|.._ _...|..DF3..|...._X_.|---|---|   |
|CE1|  |    |    \   |       |   X    |       |   /    |   |   |CE2|
|   |       |     \_.|..DF2..|._/ \_..|..DF4..|._/     |       |   |
+---+       |        |=======|        |=======|        |       +---+
    ^       +--------+       +--------+       +--------+       ^
    |        Edge Node       Relay Node        Edge Node       |
    |          (T-PE)           (S-PE)          (T-PE)         |
    |                                                          |
    |&lt;- TSN -&gt; &lt;------- TSN over DetNet MPLS -------&gt; &lt;- TSN -&gt;|
    |                                                          |
    |&lt;-------- Time-Sensitive Networking (TSN) Service -------&gt;|

    X   = Service protection
    DFx = DetNet member flow x over a TE LSP
        AC  = Attachment Circuit
        Tnl = Tunnel
</pre>
</div>
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
<a href="#name-ieee-8021tsn-over-detnet" class="selfRef">IEEE 802.1TSN over DetNet</a>
        </figcaption></figure>
</div>
</section>
</div>
<div id="sec_dt_dp">
<section id="section-4">
      <h2 id="name-detnet-mpls-data-plane">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-detnet-mpls-data-plane" class="section-name selfRef">DetNet MPLS Data Plane</a>
      </h2>
<div id="sec_dt_dp_ov">
<section id="section-4.1">
        <h3 id="name-overview">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
        </h3>
<p id="section-4.1-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-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2">
        A node operating on a DetNet flow in the DetNet service sub-layer, i.e., a node processing a DetNet packet that has the S-Label as top of stack, 
        uses the local context associated with that S-Label. For example, a received 
        F-Label can be used 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 DetNet control word 
        (d-CW).<a href="#section-4.1-2" class="pilcrow">¶</a></p>
<p id="section-4.1-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
    forwarding labels (F-Labels).<a href="#section-4.1-3" class="pilcrow">¶</a></p>
<p id="section-4.1-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 -- notably, 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-4.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tom-encap">
<section id="section-4.2">
        <h3 id="name-tsn-over-detnet-mpls-encaps">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-tsn-over-detnet-mpls-encaps" class="section-name selfRef">TSN over DetNet MPLS Encapsulation</a>
        </h3>
<p id="section-4.2-1">
        The basic encapsulation approach is to treat a TSN Stream as an App-flow 
        from the DetNet MPLS perspective. The corresponding example is shown in 
        <a href="#fig_tsn_mpls_ex" class="xref">Figure 3</a>. Note that three example flows are 
 shown in the figure.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<span id="name-examples-of-tsn-over-mpls-e"></span><div id="fig_tsn_mpls_ex">
<figure id="figure-3">
          <div class="artwork art-text alignCenter" id="section-4.2-2.1">
<pre>

           /-&gt;     +------+  +------+  +------+   TSN      ^ ^
  MPLS     |       |  X   |  |  X   |  |  X   |&lt;- Appli    : :
App-Flow &lt;-+       +------+  +------+  +------+   cation   : :(1)
           |       |TSN-L2|  |TSN-L2|  |TSN-L2|            : v
           \-&gt; +---+======+--+======+--+======+-----+      :
                   | d-CW |  | d-CW |  | d-CW |            :
DetNet-MPLS        +------+  +------+  +------+            :(2)
                   |Labels|  |Labels|  |Labels|            v
               +---+======+--+======+--+======+-----+
Link/Sub-Network   |  L2  |  | TSN  |  | UDP  |
                   +------+  +------+  +------+
                                       |  IP  |
                                       +------+
                                       |  L2  |
                                       +------+
    (1) TSN Stream
    (2) DetNet MPLS Flow
</pre>
</div>
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
<a href="#name-examples-of-tsn-over-mpls-e" class="selfRef">Examples of TSN over MPLS Encapsulation Formats</a>
          </figcaption></figure>
</div>
<p id="section-4.2-3">
        In the figure, "Application" indicates the application payload carried by 
        the TSN network. "MPLS App-Flow" indicates that the TSN Stream is the 
        payload from the perspective of the DetNet MPLS data plane defined in 
        <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>. A single DetNet MPLS flow 
        can aggregate multiple TSN Streams.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
<aside id="section-4.2-4">
          <p id="section-4.2-4.1">
 Note: Network fragmentation for DetNet is not supported and MUST be avoided. The reason for this is that network fragmentation is not  consistent with the packet delivery times needed for DetNet. Therefore, when IP is used as the sub-network, IPv6 fragmentation MUST NOT be used, and IPv4 packets MUST be sent with the DF bit set. This means that the network operator MUST ensure that all the DetNet encapsulation overhead plus the maximum TSN App-flow frame size does not exceed the DetNet network's MTU.<a href="#section-4.2-4.1" class="pilcrow">¶</a></p>
</aside>
</section>
</div>
</section>
</div>
<div id="tom_proc">
<section id="section-5">
      <h2 id="name-tsn-over-mpls-data-plane-pr">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-tsn-over-mpls-data-plane-pr" class="section-name selfRef">TSN over MPLS Data Plane Procedures</a>
      </h2>
<p id="section-5-1">
        The description of edge node procedures and functions for TSN over DetNet MPLS
        scenarios follows the concepts from <span>[<a href="#RFC3985" class="xref">RFC3985</a>]</span> and covers the 
        edge node components shown in <a href="#fig_tsn_mpls_detnet" class="xref">Figure 1</a>. In 
        this section, the following procedures of DetNet edge nodes are described:<a href="#section-5-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5-2.1">
                        TSN related (<a href="#tom_tsn_proc" class="xref">Section 5.1</a>)<a href="#section-5-2.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.2">
                        DetNet Service Proxy (<a href="#tom_svc_prx_proc" class="xref">Section 5.2</a>)<a href="#section-5-2.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.3">
                        DetNet service and forwarding sub-layer (<a href="#tom_dn_sub_proc" class="xref">Section 5.3</a>)<a href="#section-5-2.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-5-3">  
 The subsections describe procedures for forwarding packets by DetNet 
 edge nodes, where such packets are received from either directly 
 connected CEs (TSN nodes) or some other DetNet edge nodes.<a href="#section-5-3" class="pilcrow">¶</a></p>
<div id="tom_tsn_proc">
<section id="section-5.1">
        <h3 id="name-edge-node-tsn-procedures">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-edge-node-tsn-procedures" class="section-name selfRef">Edge Node TSN Procedures</a>
        </h3>
<p id="section-5.1-1">
        The TSN TG of the IEEE 802.1 
                Working Group has defined (and is 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.
        <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> defines packet 
                replication and elimination functions for a TSN network.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2">
      The implementation of a TSN entity (i.e., TSN packet processing 
   functions) must be compliant with the relevant IEEE 802.1 
   standards.<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<p id="section-5.1-3">
                TSN-specific functions are executed on the data received by 
                the DetNet edge node from the connected CE before being forwarded to 
 connected CE(s) or presented to the DetNet service proxy function for 
                transmission across the DetNet domain. TSN-specific functions 
 are also executed on the data received from a DetNet PW by a PE 
 before the data is output on the AC(s).<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<p id="section-5.1-4">
                The TSN packet processing function(s) of edge nodes (T-PE) belongs to the 
                NSP <span>[<a href="#RFC3985" class="xref">RFC3985</a>]</span> 
                block. This is similar to other functionalities being defined by standards 
                bodies other than the IETF (for example, in the case of Ethernet, stripping, 
                overwriting, or adding VLAN tags, etc.). Depending on the TSN role of 
                the edge node in the end-to-end TSN service, selected TSN functions 
                are supported.<a href="#section-5.1-4" class="pilcrow">¶</a></p>
<p id="section-5.1-5"> 
 When a PE receives a packet from a CE on a given AC with DetNet service,
 it first checks via Stream identification 
 (see Clause 6 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and
            <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>) 
 whether the packet belongs 
 to a configured TSN Stream (i.e., App-flow from the DetNet perspective). 
 If no Stream ID is matched and no other (VPN) service is configured 
 for the AC, then the packet <span class="bcp14">MUST</span> be dropped. If there is a matching TSN 
 Stream, then the Stream-ID-specific TSN functions are executed 
 (e.g., ingress policing, header field manipulation in the case 
 of active Stream identification, FRER, etc.). Source Media Access Control (MAC) lookup 
 may also be used for local MAC address learning.<a href="#section-5.1-5" class="pilcrow">¶</a></p>
<p id="section-5.1-6"> 
 If the PE decides to forward the packet, the packet <span class="bcp14">MUST</span> be forwarded 
 according to the TSN-Stream-specific configuration to connected CE(s) 
 (in case of local bridging) and/or to the DetNet service proxy 
 (in case of forwarding to remote CE(s)). If there are no 
 TSN-Stream-specific forwarding configurations, the PE <span class="bcp14">MUST</span> flood 
 the packet to other locally attached CE(s) and to the DetNet service 
 proxy. If the administrative policy on the PE does not allow 
 flooding, the PE <span class="bcp14">MUST</span> drop the packet.<a href="#section-5.1-6" class="pilcrow">¶</a></p>
<p id="section-5.1-7"> 
 When a TSN entity of the PE receives a packet from the DetNet 
 service proxy, it first checks via Stream identification 
 (see Clause 6 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and
            <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>) whether 
 the packet belongs to a configured TSN Stream. If no Stream ID is 
 matched, then the packet is dropped. If there is a matching TSN 
 Stream, then the Stream-ID-specific TSN functions are executed 
 (e.g., header field manipulation in case of active Stream 
 identification, FRER, etc.). Source MAC lookup may also be used for 
 local MAC address learning.<a href="#section-5.1-7" class="pilcrow">¶</a></p>
<p id="section-5.1-8"> 
 If the PE decides to forward the packet, the packet is forwarded 
 according to the TSN-Stream-specific configuration to connected CE(s).
 If there are no TSN-Stream-specific forwarding configurations, the 
 PE floods the packet to locally attached CE(s). If the 
 administrative policy on the PE does not allow flooding, the PE  
 drops the packet.<a href="#section-5.1-8" class="pilcrow">¶</a></p>
<p id="section-5.1-9">
            Implementations of this document <span class="bcp14">SHALL</span> use management and
            control information to ensure TSN-specific functions of the edge node
            according to the expectations of the connected TSN network.<a href="#section-5.1-9" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tom_svc_prx_proc">
<section id="section-5.2">
        <h3 id="name-edge-node-detnet-service-pr">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-edge-node-detnet-service-pr" class="section-name selfRef">Edge Node DetNet Service Proxy Procedures</a>
        </h3>
<p id="section-5.2-1">
                The service proxy
                function maps between App-flows and DetNet flows.
 The DetNet edge node TSN entity <span class="bcp14">MUST</span> support the TSN Stream
                identification functions (as defined in Clause 6 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>) and the related managed objects (as
                defined in Clause 9 of <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>) to
                recognize the packets related to App-flow.  The service proxy
                presents TSN Streams as an App-flow to a DetNet flow.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2"> 
 When a DetNet service proxy receives a packet from the TSN entity,
 it <span class="bcp14">MUST</span> check whether such an App-flow is present in its mapping table.
 If present, it associates the internal DetNet flow ID to the packet and 
 <span class="bcp14">MUST</span> forward it to the DetNet service and forwarding sub-layers. If 
 no match is found, it <span class="bcp14">MUST</span> drop the packet.<a href="#section-5.2-2" class="pilcrow">¶</a></p>
<p id="section-5.2-3"> 
 When a DetNet service proxy receives a packet from the DetNet service 
 and forwarding sub-layers, it <span class="bcp14">MUST</span> be forwarded to the edge node 
 TSN entity.<a href="#section-5.2-3" class="pilcrow">¶</a></p>
<p id="section-5.2-4">
                Implementations of this document <span class="bcp14">SHALL</span> use management and
                control information to map a TSN Stream to a DetNet flow. 
                N:1 mapping (aggregating multiple TSN Streams in a single
                DetNet flow) <span class="bcp14">SHALL</span> be supported. The management or control
                function that provisions flow mapping <span class="bcp14">SHALL</span> ensure that
                adequate resources are allocated and configured to 
                fulfill the service requirements of the mapped flows.<a href="#section-5.2-4" class="pilcrow">¶</a></p>
<p id="section-5.2-5">
                Due to the (intentional) similarities of the DetNet PREOF and
                TSN FRER functions, service protection function interworking is
                possible between the TSN and the DetNet domains. Such service
                protection interworking scenarios might require copying of sequence
                number fields from TSN (L2) to PW (MPLS) encapsulation.
                However, such interworking is out of scope in this document and
                is left for further study.<a href="#section-5.2-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tom_dn_sub_proc">
<section id="section-5.3">
        <h3 id="name-edge-node-detnet-service-an">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-edge-node-detnet-service-an" class="section-name selfRef">Edge Node DetNet Service and Forwarding Sub-Layer Procedures</a>
        </h3>
<p id="section-5.3-1">
                In the design presented in <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>, an MPLS service 
                label (the S-Label), similar to a PW label 
                <span>[<a href="#RFC3985" class="xref">RFC3985</a>]</span>, is used to identify both the DetNet flow 
                identity and the MPLS payload type.  The DetNet sequence 
                number is carried in the d-CW, which carries the 
                Data/OAM discriminator as well. In 
                <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>, two sequence number sizes 
                are supported: a 16-bit sequence number and a 28-bit sequence number.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
<p id="section-5.3-2">
                PREOF functions and the provided service recovery are available
                only within the DetNet domain as the DetNet flow ID and the DetNet
                sequence number are not valid outside the DetNet network.  MPLS
                (DetNet) edge nodes terminate all related information elements 
                encoded in the MPLS labels.<a href="#section-5.3-2" class="pilcrow">¶</a></p>
<p id="section-5.3-3"> 
 When a PE receives a packet from the service proxy function, it <span class="bcp14">MUST</span> 
 handle the packet as defined in <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>.<a href="#section-5.3-3" class="pilcrow">¶</a></p>
<p id="section-5.3-4"> 
 When a PE receives an MPLS packet from a remote PE, then, after 
 processing the MPLS label stack, if the top MPLS label ends up being 
 a DetNet S-Label that was advertised by this node, then the PE 
 <span class="bcp14">MUST</span> forward the packet according to the configured DetNet service and 
 forwarding sub-layer rules to other PE nodes or via the DetNet service 
 proxy function towards locally connected CE(s).<a href="#section-5.3-4" class="pilcrow">¶</a></p>
<p id="section-5.3-5">
                For further details on DetNet service and forwarding sub-layers, 
 see <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>.<a href="#section-5.3-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="cp_considerations">
<section id="section-6">
      <h2 id="name-controller-plane-management">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-controller-plane-management" class="section-name selfRef">Controller Plane (Management and Control) Considerations</a>
      </h2>
<p id="section-6-1">
        Information related to TSN Stream(s) to DetNet flow mapping is
        required only for the service proxy function of MPLS (DetNet) edge 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-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">
            The following summarizes the set of information that is needed to
            configure TSN over DetNet MPLS:<a href="#section-6-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-6-3.1">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-6-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-6-3.2">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-6-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-6-3.3">App-flow identification information to map received TSN 
   Stream(s) to the DetNet flow. Parameters of TSN Stream 
   identification are defined in <span>[<a href="#IEEE8021CB" class="xref">IEEE8021CB</a>]</span> and 
   <span>[<a href="#IEEEP8021CBdb" class="xref">IEEEP8021CBdb</a>]</span>.<a href="#section-6-3.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-6-4">
            This information <span class="bcp14">MUST</span> be provisioned per DetNet flow.<a href="#section-6-4" class="pilcrow">¶</a></p>
<p id="section-6-5">
 Mappings between DetNet and TSN management and control planes are 
 out of scope of the document. Some of the challenges are 
 highlighted below.<a href="#section-6-5" class="pilcrow">¶</a></p>
<p id="section-6-6">
        MPLS DetNet edge nodes are a member of both the DetNet domain and the
        connected TSN network. From the TSN network perspective, the MPLS
        (DetNet) edge node has a "TSN relay node" 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 MSRP behave differently.  
 Therefore, management and control plane design is an important aspect 
 of scenarios where mapping between DetNet and TSN is required.<a href="#section-6-6" class="pilcrow">¶</a></p>
<p id="section-6-7">
        Note that as the DetNet network is just a portion of the end-to-end TSN
        path (i.e., single hop from the Ethernet perspective), some parameters
        (e.g., delay) may differ significantly.  Since there is no interworking
        function, the bandwidth of the DetNet network is assumed to be set large enough to
        handle all TSN flows it will support.  At the egress of the DetNet domain, the MPLS
        headers are stripped, and the TSN flow continues on as a normal TSN
        flow.<a href="#section-6-7" class="pilcrow">¶</a></p>
<p id="section-6-8">
        In order to use a DetNet network to interconnect TSN segments,
        TSN-specific information must be converted to DetNet-domain-specific information. TSN Stream ID(s) and stream-related
        parameters/requirements must be converted to a DetNet flow ID and 
        flow-related parameters/requirements.<a href="#section-6-8" class="pilcrow">¶</a></p>
<p id="section-6-9">
        In some cases, it may be challenging to determine some information related to the egress-node. For example, it may be not trivial to
        locate the egress point/interface of a TSN Stream with a 
        multicast destination MAC address. Such scenarios may
        require interaction between control and management plane
        functions and between DetNet and TSN domains.<a href="#section-6-9" class="pilcrow">¶</a></p>
<p id="section-6-10">
        Mapping between DetNet flow identifiers and TSN Stream
        identifiers, if not provided explicitly, can be done by the service
        proxy function of an MPLS (DetNet) edge node locally based on information
        provided for the configuration of the TSN Stream identification functions 
        (e.g., Mask-and-Match Stream identification).<a href="#section-6-10" class="pilcrow">¶</a></p>
<p id="section-6-11">
        Triggering the setup/modification of a DetNet flow in the
        DetNet network is an example where management and/or
        control plane interactions are required between the DetNet
        and the TSN network.<a href="#section-6-11" class="pilcrow">¶</a></p>
<p id="section-6-12">
        Configuration of TSN-specific functions (e.g., FRER)
        inside the TSN 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-6-12" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-7">
      <h2 id="name-security-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-7-1">
     Security considerations for DetNet are described in detail in <span>[<a href="#I-D.ietf-detnet-security" class="xref">DETNET-SEC</a>]</span>. General security
     considerations are described in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">     
     Considerations specific to the DetNet MPLS data plane are summarized and 
  described in <span>[<a href="#RFC8964" class="xref">RFC8964</a>]</span>, including any 
  application flow types. This document focuses on a scenario where TSN Streams are the application flows for DetNet, which is already covered 
  by those DetNet MPLS data plane security considerations.<a href="#section-7-2" class="pilcrow">¶</a></p>
</section>
<div id="iana">
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-8-1">
   This document has no IANA actions.<a href="#section-8-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-9">
      <h2 id="name-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-9.1">
        <h3 id="name-normative-references">
<a href="#section-9.1" class="section-number selfRef">9.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">"Standard for Local and metropolitan area networks -- Frame Replication and Elimination for Reliability"</span>, <span class="seriesInfo">IEEE 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="seriesInfo">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="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="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="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>
<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="RFC8938">[RFC8938]</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>, and <span class="refAuthor">S. Bryant</span>, <span class="refTitle">"Deterministic Networking (DetNet) Data Plane Framework"</span>, <span class="seriesInfo">RFC 8938</span>, <span class="seriesInfo">DOI 10.17487/RFC8938</span>, <time datetime="2020-11" class="refDate">November 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8938">https://www.rfc-editor.org/info/rfc8938</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-9.2">
        <h3 id="name-informative-references">
<a href="#section-9.2" class="section-number selfRef">9.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-SEC]</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="IEEE8021Q">[IEEE8021Q]</dt>
        <dd>
<span class="refAuthor">IEEE</span>, <span class="refTitle">"Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"</span>, <span class="seriesInfo">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="RFC3985">[RFC3985]</dt>
      <dd>
<span class="refAuthor">Bryant, S., Ed.</span> and <span class="refAuthor">P. Pate, Ed.</span>, <span class="refTitle">"Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"</span>, <span class="seriesInfo">RFC 3985</span>, <span class="seriesInfo">DOI 10.17487/RFC3985</span>, <time datetime="2005-03" class="refDate">March 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3985">https://www.rfc-editor.org/info/rfc3985</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>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Don Fedyk</span></div>
<div dir="auto" class="left"><span class="org">LabN Consulting, L.L.C.</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:dfedyk@labn.net" class="email">dfedyk@labn.net</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>