| 1 |
<!DOCTYPE html> |
| 2 |
<html lang="en" class="RFC"> |
| 3 |
<head> |
| 4 |
<meta charset="utf-8"> |
| 5 |
<meta content="Common,Latin" name="scripts"> |
| 6 |
<meta content="initial-scale=1.0" name="viewport"> |
| 7 |
<title>RFC 8938: Deterministic Networking (DetNet) Data Plane Framework</title> |
| 8 |
<meta content="Balázs Varga" name="author"> |
| 9 |
<meta content="János Farkas" name="author"> |
| 10 |
<meta content="Lou Berger" name="author"> |
| 11 |
<meta content="Andrew G. Malis" name="author"> |
| 12 |
<meta content="Stewart Bryant" name="author"> |
| 13 |
<meta content=" |
| 14 |
|
| 15 |
This document provides an overall framework for the Deterministic |
| 16 |
Networking (DetNet) |
| 17 |
data plane. It covers concepts and considerations that |
| 18 |
are generally common to any DetNet data plane |
| 19 |
specification. It describes related Controller Plane |
| 20 |
considerations as well. |
| 21 |
|
| 22 |
" name="description"> |
| 23 |
<meta content="xml2rfc 3.5.0" name="generator"> |
| 24 |
<meta content="8938" name="rfc.number"> |
| 25 |
<!-- Generator version information: |
| 26 |
xml2rfc 3.5.0 |
| 27 |
Python 3.6.10 |
| 28 |
appdirs 1.4.4 |
| 29 |
ConfigArgParse 1.2.3 |
| 30 |
google-i18n-address 2.3.5 |
| 31 |
html5lib 1.0.1 |
| 32 |
intervaltree 3.0.2 |
| 33 |
Jinja2 2.11.2 |
| 34 |
kitchen 1.2.6 |
| 35 |
lxml 4.4.2 |
| 36 |
pycairo 1.19.0 |
| 37 |
pycountry 19.8.18 |
| 38 |
pyflakes 2.1.1 |
| 39 |
PyYAML 5.3.1 |
| 40 |
requests 2.22.0 |
| 41 |
setuptools 40.6.2 |
| 42 |
six 1.14.0 |
| 43 |
WeasyPrint 51 |
| 44 |
--> |
| 45 |
<link href="rfc8938.xml" rel="alternate" type="application/rfc+xml"> |
| 46 |
<link href="#copyright" rel="license"> |
| 47 |
<style type="text/css">/* |
| 48 |
|
| 49 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 50 |
|
| 51 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 52 |
this can be consolidated so that style settings occur only in one place, but |
| 53 |
for now the contents of this file consists first of the initial CSS work as |
| 54 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 55 |
commented changes found necssary during the development of the v3 |
| 56 |
formatters. |
| 57 |
|
| 58 |
*/ |
| 59 |
|
| 60 |
/* fonts */ |
| 61 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 62 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 63 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 64 |
|
| 65 |
@viewport { |
| 66 |
zoom: 1.0; |
| 67 |
width: extend-to-zoom; |
| 68 |
} |
| 69 |
@-ms-viewport { |
| 70 |
width: extend-to-zoom; |
| 71 |
zoom: 1.0; |
| 72 |
} |
| 73 |
/* general and mobile first */ |
| 74 |
html { |
| 75 |
} |
| 76 |
body { |
| 77 |
max-width: 90%; |
| 78 |
margin: 1.5em auto; |
| 79 |
color: #222; |
| 80 |
background-color: #fff; |
| 81 |
font-size: 14px; |
| 82 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 83 |
line-height: 1.6; |
| 84 |
scroll-behavior: smooth; |
| 85 |
} |
| 86 |
.ears { |
| 87 |
display: none; |
| 88 |
} |
| 89 |
|
| 90 |
/* headings */ |
| 91 |
#title, h1, h2, h3, h4, h5, h6 { |
| 92 |
margin: 1em 0 0.5em; |
| 93 |
font-weight: bold; |
| 94 |
line-height: 1.3; |
| 95 |
} |
| 96 |
#title { |
| 97 |
clear: both; |
| 98 |
border-bottom: 1px solid #ddd; |
| 99 |
margin: 0 0 0.5em 0; |
| 100 |
padding: 1em 0 0.5em; |
| 101 |
} |
| 102 |
.author { |
| 103 |
padding-bottom: 4px; |
| 104 |
} |
| 105 |
h1 { |
| 106 |
font-size: 26px; |
| 107 |
margin: 1em 0; |
| 108 |
} |
| 109 |
h2 { |
| 110 |
font-size: 22px; |
| 111 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 112 |
padding-top: 33px; |
| 113 |
} |
| 114 |
h3 { |
| 115 |
font-size: 18px; |
| 116 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 117 |
padding-top: 42px; |
| 118 |
} |
| 119 |
h4 { |
| 120 |
font-size: 16px; |
| 121 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 122 |
padding-top: 42px; |
| 123 |
} |
| 124 |
h5, h6 { |
| 125 |
font-size: 14px; |
| 126 |
} |
| 127 |
#n-copyright-notice { |
| 128 |
border-bottom: 1px solid #ddd; |
| 129 |
padding-bottom: 1em; |
| 130 |
margin-bottom: 1em; |
| 131 |
} |
| 132 |
/* general structure */ |
| 133 |
p { |
| 134 |
padding: 0; |
| 135 |
margin: 0 0 1em 0; |
| 136 |
text-align: left; |
| 137 |
} |
| 138 |
div, span { |
| 139 |
position: relative; |
| 140 |
} |
| 141 |
div { |
| 142 |
margin: 0; |
| 143 |
} |
| 144 |
.alignRight.art-text { |
| 145 |
background-color: #f9f9f9; |
| 146 |
border: 1px solid #eee; |
| 147 |
border-radius: 3px; |
| 148 |
padding: 1em 1em 0; |
| 149 |
margin-bottom: 1.5em; |
| 150 |
} |
| 151 |
.alignRight.art-text pre { |
| 152 |
padding: 0; |
| 153 |
} |
| 154 |
.alignRight { |
| 155 |
margin: 1em 0; |
| 156 |
} |
| 157 |
.alignRight > *:first-child { |
| 158 |
border: none; |
| 159 |
margin: 0; |
| 160 |
float: right; |
| 161 |
clear: both; |
| 162 |
} |
| 163 |
.alignRight > *:nth-child(2) { |
| 164 |
clear: both; |
| 165 |
display: block; |
| 166 |
border: none; |
| 167 |
} |
| 168 |
svg { |
| 169 |
display: block; |
| 170 |
} |
| 171 |
.alignCenter.art-text { |
| 172 |
background-color: #f9f9f9; |
| 173 |
border: 1px solid #eee; |
| 174 |
border-radius: 3px; |
| 175 |
padding: 1em 1em 0; |
| 176 |
margin-bottom: 1.5em; |
| 177 |
} |
| 178 |
.alignCenter.art-text pre { |
| 179 |
padding: 0; |
| 180 |
} |
| 181 |
.alignCenter { |
| 182 |
margin: 1em 0; |
| 183 |
} |
| 184 |
.alignCenter > *:first-child { |
| 185 |
border: none; |
| 186 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 187 |
support flexbox yet. |
| 188 |
*/ |
| 189 |
display: table; |
| 190 |
margin: 0 auto; |
| 191 |
} |
| 192 |
|
| 193 |
/* lists */ |
| 194 |
ol, ul { |
| 195 |
padding: 0; |
| 196 |
margin: 0 0 1em 2em; |
| 197 |
} |
| 198 |
ol ol, ul ul, ol ul, ul ol { |
| 199 |
margin-left: 1em; |
| 200 |
} |
| 201 |
li { |
| 202 |
margin: 0 0 0.25em 0; |
| 203 |
} |
| 204 |
.ulCompact li { |
| 205 |
margin: 0; |
| 206 |
} |
| 207 |
ul.empty, .ulEmpty { |
| 208 |
list-style-type: none; |
| 209 |
} |
| 210 |
ul.empty li, .ulEmpty li { |
| 211 |
margin-top: 0.5em; |
| 212 |
} |
| 213 |
ul.compact, .ulCompact, |
| 214 |
ol.compact, .olCompact { |
| 215 |
line-height: 100%; |
| 216 |
margin: 0 0 0 2em; |
| 217 |
} |
| 218 |
|
| 219 |
/* definition lists */ |
| 220 |
dl { |
| 221 |
} |
| 222 |
dl > dt { |
| 223 |
float: left; |
| 224 |
margin-right: 1em; |
| 225 |
} |
| 226 |
/* |
| 227 |
dl.nohang > dt { |
| 228 |
float: none; |
| 229 |
} |
| 230 |
*/ |
| 231 |
dl > dd { |
| 232 |
margin-bottom: .8em; |
| 233 |
min-height: 1.3em; |
| 234 |
} |
| 235 |
dl.compact > dd, .dlCompact > dd { |
| 236 |
margin-bottom: 0em; |
| 237 |
} |
| 238 |
dl > dd > dl { |
| 239 |
margin-top: 0.5em; |
| 240 |
margin-bottom: 0em; |
| 241 |
} |
| 242 |
|
| 243 |
/* links */ |
| 244 |
a { |
| 245 |
text-decoration: none; |
| 246 |
} |
| 247 |
a[href] { |
| 248 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 249 |
} |
| 250 |
a[href]:hover { |
| 251 |
background-color: #f2f2f2; |
| 252 |
} |
| 253 |
figcaption a[href], |
| 254 |
a[href].selfRef { |
| 255 |
color: #222; |
| 256 |
} |
| 257 |
/* XXX probably not this: |
| 258 |
a.selfRef:hover { |
| 259 |
background-color: transparent; |
| 260 |
cursor: default; |
| 261 |
} */ |
| 262 |
|
| 263 |
/* Figures */ |
| 264 |
tt, code, pre, code { |
| 265 |
background-color: #f9f9f9; |
| 266 |
font-family: 'Roboto Mono', monospace; |
| 267 |
} |
| 268 |
pre { |
| 269 |
border: 1px solid #eee; |
| 270 |
margin: 0; |
| 271 |
padding: 1em; |
| 272 |
} |
| 273 |
img { |
| 274 |
max-width: 100%; |
| 275 |
} |
| 276 |
figure { |
| 277 |
margin: 0; |
| 278 |
} |
| 279 |
figure blockquote { |
| 280 |
margin: 0.8em 0.4em 0.4em; |
| 281 |
} |
| 282 |
figcaption { |
| 283 |
font-style: italic; |
| 284 |
margin: 0 0 1em 0; |
| 285 |
} |
| 286 |
@media screen { |
| 287 |
pre { |
| 288 |
overflow-x: auto; |
| 289 |
max-width: 100%; |
| 290 |
max-width: calc(100% - 22px); |
| 291 |
} |
| 292 |
} |
| 293 |
|
| 294 |
/* aside, blockquote */ |
| 295 |
aside, blockquote { |
| 296 |
margin-left: 0; |
| 297 |
padding: 1.2em 2em; |
| 298 |
} |
| 299 |
blockquote { |
| 300 |
background-color: #f9f9f9; |
| 301 |
color: #111; /* Arlen: WCAG 2019 */ |
| 302 |
border: 1px solid #ddd; |
| 303 |
border-radius: 3px; |
| 304 |
margin: 1em 0; |
| 305 |
} |
| 306 |
cite { |
| 307 |
display: block; |
| 308 |
text-align: right; |
| 309 |
font-style: italic; |
| 310 |
} |
| 311 |
|
| 312 |
/* tables */ |
| 313 |
table { |
| 314 |
width: 100%; |
| 315 |
margin: 0 0 1em; |
| 316 |
border-collapse: collapse; |
| 317 |
border: 1px solid #eee; |
| 318 |
} |
| 319 |
th, td { |
| 320 |
text-align: left; |
| 321 |
vertical-align: top; |
| 322 |
padding: 0.5em 0.75em; |
| 323 |
} |
| 324 |
th { |
| 325 |
text-align: left; |
| 326 |
background-color: #e9e9e9; |
| 327 |
} |
| 328 |
tr:nth-child(2n+1) > td { |
| 329 |
background-color: #f5f5f5; |
| 330 |
} |
| 331 |
table caption { |
| 332 |
font-style: italic; |
| 333 |
margin: 0; |
| 334 |
padding: 0; |
| 335 |
text-align: left; |
| 336 |
} |
| 337 |
table p { |
| 338 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 339 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 340 |
margin: 0; |
| 341 |
} |
| 342 |
|
| 343 |
/* pilcrow */ |
| 344 |
a.pilcrow { |
| 345 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 346 |
text-decoration: none; |
| 347 |
visibility: hidden; |
| 348 |
user-select: none; |
| 349 |
-ms-user-select: none; |
| 350 |
-o-user-select:none; |
| 351 |
-moz-user-select: none; |
| 352 |
-khtml-user-select: none; |
| 353 |
-webkit-user-select: none; |
| 354 |
-webkit-touch-callout: none; |
| 355 |
} |
| 356 |
@media screen { |
| 357 |
aside:hover > a.pilcrow, |
| 358 |
p:hover > a.pilcrow, |
| 359 |
blockquote:hover > a.pilcrow, |
| 360 |
div:hover > a.pilcrow, |
| 361 |
li:hover > a.pilcrow, |
| 362 |
pre:hover > a.pilcrow { |
| 363 |
visibility: visible; |
| 364 |
} |
| 365 |
a.pilcrow:hover { |
| 366 |
background-color: transparent; |
| 367 |
} |
| 368 |
} |
| 369 |
|
| 370 |
/* misc */ |
| 371 |
hr { |
| 372 |
border: 0; |
| 373 |
border-top: 1px solid #eee; |
| 374 |
} |
| 375 |
.bcp14 { |
| 376 |
font-variant: small-caps; |
| 377 |
} |
| 378 |
|
| 379 |
.role { |
| 380 |
font-variant: all-small-caps; |
| 381 |
} |
| 382 |
|
| 383 |
/* info block */ |
| 384 |
#identifiers { |
| 385 |
margin: 0; |
| 386 |
font-size: 0.9em; |
| 387 |
} |
| 388 |
#identifiers dt { |
| 389 |
width: 3em; |
| 390 |
clear: left; |
| 391 |
} |
| 392 |
#identifiers dd { |
| 393 |
float: left; |
| 394 |
margin-bottom: 0; |
| 395 |
} |
| 396 |
#identifiers .authors .author { |
| 397 |
display: inline-block; |
| 398 |
margin-right: 1.5em; |
| 399 |
} |
| 400 |
#identifiers .authors .org { |
| 401 |
font-style: italic; |
| 402 |
} |
| 403 |
|
| 404 |
/* The prepared/rendered info at the very bottom of the page */ |
| 405 |
.docInfo { |
| 406 |
color: #666; /* Arlen: WCAG 2019 */ |
| 407 |
font-size: 0.9em; |
| 408 |
font-style: italic; |
| 409 |
margin-top: 2em; |
| 410 |
} |
| 411 |
.docInfo .prepared { |
| 412 |
float: left; |
| 413 |
} |
| 414 |
.docInfo .prepared { |
| 415 |
float: right; |
| 416 |
} |
| 417 |
|
| 418 |
/* table of contents */ |
| 419 |
#toc { |
| 420 |
padding: 0.75em 0 2em 0; |
| 421 |
margin-bottom: 1em; |
| 422 |
} |
| 423 |
nav.toc ul { |
| 424 |
margin: 0 0.5em 0 0; |
| 425 |
padding: 0; |
| 426 |
list-style: none; |
| 427 |
} |
| 428 |
nav.toc li { |
| 429 |
line-height: 1.3em; |
| 430 |
margin: 0.75em 0; |
| 431 |
padding-left: 1.2em; |
| 432 |
text-indent: -1.2em; |
| 433 |
} |
| 434 |
/* references */ |
| 435 |
.references dt { |
| 436 |
text-align: right; |
| 437 |
font-weight: bold; |
| 438 |
min-width: 7em; |
| 439 |
} |
| 440 |
.references dd { |
| 441 |
margin-left: 8em; |
| 442 |
overflow: auto; |
| 443 |
} |
| 444 |
|
| 445 |
.refInstance { |
| 446 |
margin-bottom: 1.25em; |
| 447 |
} |
| 448 |
|
| 449 |
.references .ascii { |
| 450 |
margin-bottom: 0.25em; |
| 451 |
} |
| 452 |
|
| 453 |
/* index */ |
| 454 |
.index ul { |
| 455 |
margin: 0 0 0 1em; |
| 456 |
padding: 0; |
| 457 |
list-style: none; |
| 458 |
} |
| 459 |
.index ul ul { |
| 460 |
margin: 0; |
| 461 |
} |
| 462 |
.index li { |
| 463 |
margin: 0; |
| 464 |
text-indent: -2em; |
| 465 |
padding-left: 2em; |
| 466 |
padding-bottom: 5px; |
| 467 |
} |
| 468 |
.indexIndex { |
| 469 |
margin: 0.5em 0 1em; |
| 470 |
} |
| 471 |
.index a { |
| 472 |
font-weight: 700; |
| 473 |
} |
| 474 |
/* make the index two-column on all but the smallest screens */ |
| 475 |
@media (min-width: 600px) { |
| 476 |
.index ul { |
| 477 |
-moz-column-count: 2; |
| 478 |
-moz-column-gap: 20px; |
| 479 |
} |
| 480 |
.index ul ul { |
| 481 |
-moz-column-count: 1; |
| 482 |
-moz-column-gap: 0; |
| 483 |
} |
| 484 |
} |
| 485 |
|
| 486 |
/* authors */ |
| 487 |
address.vcard { |
| 488 |
font-style: normal; |
| 489 |
margin: 1em 0; |
| 490 |
} |
| 491 |
|
| 492 |
address.vcard .nameRole { |
| 493 |
font-weight: 700; |
| 494 |
margin-left: 0; |
| 495 |
} |
| 496 |
address.vcard .label { |
| 497 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 498 |
margin: 0.5em 0; |
| 499 |
} |
| 500 |
address.vcard .type { |
| 501 |
display: none; |
| 502 |
} |
| 503 |
.alternative-contact { |
| 504 |
margin: 1.5em 0 1em; |
| 505 |
} |
| 506 |
hr.addr { |
| 507 |
border-top: 1px dashed; |
| 508 |
margin: 0; |
| 509 |
color: #ddd; |
| 510 |
max-width: calc(100% - 16px); |
| 511 |
} |
| 512 |
|
| 513 |
/* temporary notes */ |
| 514 |
.rfcEditorRemove::before { |
| 515 |
position: absolute; |
| 516 |
top: 0.2em; |
| 517 |
right: 0.2em; |
| 518 |
padding: 0.2em; |
| 519 |
content: "The RFC Editor will remove this note"; |
| 520 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 521 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 522 |
} |
| 523 |
.rfcEditorRemove { |
| 524 |
position: relative; |
| 525 |
padding-top: 1.8em; |
| 526 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 527 |
border-radius: 3px; |
| 528 |
} |
| 529 |
.cref { |
| 530 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 531 |
padding: 2px 4px; |
| 532 |
} |
| 533 |
.crefSource { |
| 534 |
font-style: italic; |
| 535 |
} |
| 536 |
/* alternative layout for smaller screens */ |
| 537 |
@media screen and (max-width: 1023px) { |
| 538 |
body { |
| 539 |
padding-top: 2em; |
| 540 |
} |
| 541 |
#title { |
| 542 |
padding: 1em 0; |
| 543 |
} |
| 544 |
h1 { |
| 545 |
font-size: 24px; |
| 546 |
} |
| 547 |
h2 { |
| 548 |
font-size: 20px; |
| 549 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 550 |
padding-top: 38px; |
| 551 |
} |
| 552 |
#identifiers dd { |
| 553 |
max-width: 60%; |
| 554 |
} |
| 555 |
#toc { |
| 556 |
position: fixed; |
| 557 |
z-index: 2; |
| 558 |
top: 0; |
| 559 |
right: 0; |
| 560 |
padding: 0; |
| 561 |
margin: 0; |
| 562 |
background-color: inherit; |
| 563 |
border-bottom: 1px solid #ccc; |
| 564 |
} |
| 565 |
#toc h2 { |
| 566 |
margin: -1px 0 0 0; |
| 567 |
padding: 4px 0 4px 6px; |
| 568 |
padding-right: 1em; |
| 569 |
min-width: 190px; |
| 570 |
font-size: 1.1em; |
| 571 |
text-align: right; |
| 572 |
background-color: #444; |
| 573 |
color: white; |
| 574 |
cursor: pointer; |
| 575 |
} |
| 576 |
#toc h2::before { /* css hamburger */ |
| 577 |
float: right; |
| 578 |
position: relative; |
| 579 |
width: 1em; |
| 580 |
height: 1px; |
| 581 |
left: -164px; |
| 582 |
margin: 6px 0 0 0; |
| 583 |
background: white none repeat scroll 0 0; |
| 584 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 585 |
content: ""; |
| 586 |
} |
| 587 |
#toc nav { |
| 588 |
display: none; |
| 589 |
padding: 0.5em 1em 1em; |
| 590 |
overflow: auto; |
| 591 |
height: calc(100vh - 48px); |
| 592 |
border-left: 1px solid #ddd; |
| 593 |
} |
| 594 |
} |
| 595 |
|
| 596 |
/* alternative layout for wide screens */ |
| 597 |
@media screen and (min-width: 1024px) { |
| 598 |
body { |
| 599 |
max-width: 724px; |
| 600 |
margin: 42px auto; |
| 601 |
padding-left: 1.5em; |
| 602 |
padding-right: 29em; |
| 603 |
} |
| 604 |
#toc { |
| 605 |
position: fixed; |
| 606 |
top: 42px; |
| 607 |
right: 42px; |
| 608 |
width: 25%; |
| 609 |
margin: 0; |
| 610 |
padding: 0 1em; |
| 611 |
z-index: 1; |
| 612 |
} |
| 613 |
#toc h2 { |
| 614 |
border-top: none; |
| 615 |
border-bottom: 1px solid #ddd; |
| 616 |
font-size: 1em; |
| 617 |
font-weight: normal; |
| 618 |
margin: 0; |
| 619 |
padding: 0.25em 1em 1em 0; |
| 620 |
} |
| 621 |
#toc nav { |
| 622 |
display: block; |
| 623 |
height: calc(90vh - 84px); |
| 624 |
bottom: 0; |
| 625 |
padding: 0.5em 0 0; |
| 626 |
overflow: auto; |
| 627 |
} |
| 628 |
img { /* future proofing */ |
| 629 |
max-width: 100%; |
| 630 |
height: auto; |
| 631 |
} |
| 632 |
} |
| 633 |
|
| 634 |
/* pagination */ |
| 635 |
@media print { |
| 636 |
body { |
| 637 |
|
| 638 |
width: 100%; |
| 639 |
} |
| 640 |
p { |
| 641 |
orphans: 3; |
| 642 |
widows: 3; |
| 643 |
} |
| 644 |
#n-copyright-notice { |
| 645 |
border-bottom: none; |
| 646 |
} |
| 647 |
#toc, #n-introduction { |
| 648 |
page-break-before: always; |
| 649 |
} |
| 650 |
#toc { |
| 651 |
border-top: none; |
| 652 |
padding-top: 0; |
| 653 |
} |
| 654 |
figure, pre { |
| 655 |
page-break-inside: avoid; |
| 656 |
} |
| 657 |
figure { |
| 658 |
overflow: scroll; |
| 659 |
} |
| 660 |
h1, h2, h3, h4, h5, h6 { |
| 661 |
page-break-after: avoid; |
| 662 |
} |
| 663 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 664 |
page-break-before: avoid; |
| 665 |
} |
| 666 |
pre { |
| 667 |
white-space: pre-wrap; |
| 668 |
word-wrap: break-word; |
| 669 |
font-size: 10pt; |
| 670 |
} |
| 671 |
table { |
| 672 |
border: 1px solid #ddd; |
| 673 |
} |
| 674 |
td { |
| 675 |
border-top: 1px solid #ddd; |
| 676 |
} |
| 677 |
} |
| 678 |
|
| 679 |
/* This is commented out here, as the string-set: doesn't |
| 680 |
pass W3C validation currently */ |
| 681 |
/* |
| 682 |
.ears thead .left { |
| 683 |
string-set: ears-top-left content(); |
| 684 |
} |
| 685 |
|
| 686 |
.ears thead .center { |
| 687 |
string-set: ears-top-center content(); |
| 688 |
} |
| 689 |
|
| 690 |
.ears thead .right { |
| 691 |
string-set: ears-top-right content(); |
| 692 |
} |
| 693 |
|
| 694 |
.ears tfoot .left { |
| 695 |
string-set: ears-bottom-left content(); |
| 696 |
} |
| 697 |
|
| 698 |
.ears tfoot .center { |
| 699 |
string-set: ears-bottom-center content(); |
| 700 |
} |
| 701 |
|
| 702 |
.ears tfoot .right { |
| 703 |
string-set: ears-bottom-right content(); |
| 704 |
} |
| 705 |
*/ |
| 706 |
|
| 707 |
@page :first { |
| 708 |
padding-top: 0; |
| 709 |
@top-left { |
| 710 |
content: normal; |
| 711 |
border: none; |
| 712 |
} |
| 713 |
@top-center { |
| 714 |
content: normal; |
| 715 |
border: none; |
| 716 |
} |
| 717 |
@top-right { |
| 718 |
content: normal; |
| 719 |
border: none; |
| 720 |
} |
| 721 |
} |
| 722 |
|
| 723 |
@page { |
| 724 |
size: A4; |
| 725 |
margin-bottom: 45mm; |
| 726 |
padding-top: 20px; |
| 727 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 728 |
the content depends on the document */ |
| 729 |
/* |
| 730 |
@top-left { |
| 731 |
content: 'Internet-Draft'; |
| 732 |
vertical-align: bottom; |
| 733 |
border-bottom: solid 1px #ccc; |
| 734 |
} |
| 735 |
@top-left { |
| 736 |
content: string(ears-top-left); |
| 737 |
vertical-align: bottom; |
| 738 |
border-bottom: solid 1px #ccc; |
| 739 |
} |
| 740 |
@top-center { |
| 741 |
content: string(ears-top-center); |
| 742 |
vertical-align: bottom; |
| 743 |
border-bottom: solid 1px #ccc; |
| 744 |
} |
| 745 |
@top-right { |
| 746 |
content: string(ears-top-right); |
| 747 |
vertical-align: bottom; |
| 748 |
border-bottom: solid 1px #ccc; |
| 749 |
} |
| 750 |
@bottom-left { |
| 751 |
content: string(ears-bottom-left); |
| 752 |
vertical-align: top; |
| 753 |
border-top: solid 1px #ccc; |
| 754 |
} |
| 755 |
@bottom-center { |
| 756 |
content: string(ears-bottom-center); |
| 757 |
vertical-align: top; |
| 758 |
border-top: solid 1px #ccc; |
| 759 |
} |
| 760 |
@bottom-right { |
| 761 |
content: '[Page ' counter(page) ']'; |
| 762 |
vertical-align: top; |
| 763 |
border-top: solid 1px #ccc; |
| 764 |
} |
| 765 |
*/ |
| 766 |
|
| 767 |
} |
| 768 |
|
| 769 |
/* Changes introduced to fix issues found during implementation */ |
| 770 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 771 |
a { |
| 772 |
z-index: 2; |
| 773 |
} |
| 774 |
/* Separate body from document info even without intervening H1 */ |
| 775 |
section { |
| 776 |
clear: both; |
| 777 |
} |
| 778 |
|
| 779 |
|
| 780 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 781 |
.author { |
| 782 |
vertical-align: top; |
| 783 |
} |
| 784 |
|
| 785 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 786 |
#identifiers dt { |
| 787 |
width: 8em; |
| 788 |
} |
| 789 |
|
| 790 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 791 |
#identifiers dd { |
| 792 |
margin-left: 1em; |
| 793 |
} |
| 794 |
|
| 795 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 796 |
#toc { |
| 797 |
background-color: white; |
| 798 |
} |
| 799 |
|
| 800 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 801 |
@media screen and (max-width: 1023px) { |
| 802 |
#toc h2 a, |
| 803 |
#toc h2 a:link, |
| 804 |
#toc h2 a:focus, |
| 805 |
#toc h2 a:hover, |
| 806 |
#toc a.toplink, |
| 807 |
#toc a.toplink:hover { |
| 808 |
color: white; |
| 809 |
background-color: #444; |
| 810 |
text-decoration: none; |
| 811 |
} |
| 812 |
} |
| 813 |
|
| 814 |
/* Give the bottom of the ToC some whitespace */ |
| 815 |
@media screen and (min-width: 1024px) { |
| 816 |
#toc { |
| 817 |
padding: 0 0 1em 1em; |
| 818 |
} |
| 819 |
} |
| 820 |
|
| 821 |
/* Style section numbers with more space between number and title */ |
| 822 |
.section-number { |
| 823 |
padding-right: 0.5em; |
| 824 |
} |
| 825 |
|
| 826 |
/* prevent monospace from becoming overly large */ |
| 827 |
tt, code, pre, code { |
| 828 |
font-size: 95%; |
| 829 |
} |
| 830 |
|
| 831 |
/* Fix the height/width aspect for ascii art*/ |
| 832 |
pre.sourcecode, |
| 833 |
.art-text pre { |
| 834 |
line-height: 1.12; |
| 835 |
} |
| 836 |
|
| 837 |
|
| 838 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 839 |
a.toplink { |
| 840 |
float: right; |
| 841 |
margin-right: 0.5em; |
| 842 |
} |
| 843 |
|
| 844 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 845 |
dl > dt, |
| 846 |
dl.dlParallel > dt { |
| 847 |
float: left; |
| 848 |
margin-right: 1em; |
| 849 |
} |
| 850 |
dl.dlNewline > dt { |
| 851 |
float: none; |
| 852 |
} |
| 853 |
|
| 854 |
/* Provide styling for table cell text alignment */ |
| 855 |
table td.text-left, |
| 856 |
table th.text-left { |
| 857 |
text-align: left; |
| 858 |
} |
| 859 |
table td.text-center, |
| 860 |
table th.text-center { |
| 861 |
text-align: center; |
| 862 |
} |
| 863 |
table td.text-right, |
| 864 |
table th.text-right { |
| 865 |
text-align: right; |
| 866 |
} |
| 867 |
|
| 868 |
/* Make the alternative author contact informatio look less like just another |
| 869 |
author, and group it closer with the primary author contact information */ |
| 870 |
.alternative-contact { |
| 871 |
margin: 0.5em 0 0.25em 0; |
| 872 |
} |
| 873 |
address .non-ascii { |
| 874 |
margin: 0 0 0 2em; |
| 875 |
} |
| 876 |
|
| 877 |
/* With it being possible to set tables with alignment |
| 878 |
left, center, and right, { width: 100%; } does not make sense */ |
| 879 |
table { |
| 880 |
width: auto; |
| 881 |
} |
| 882 |
|
| 883 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 884 |
because of a long floating dt label.*/ |
| 885 |
.references dd { |
| 886 |
overflow: visible; |
| 887 |
} |
| 888 |
|
| 889 |
/* Control caption placement */ |
| 890 |
caption { |
| 891 |
caption-side: bottom; |
| 892 |
} |
| 893 |
|
| 894 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 895 |
script don't end up on the other side of the page. */ |
| 896 |
|
| 897 |
address.vcard { |
| 898 |
max-width: 30em; |
| 899 |
margin-right: auto; |
| 900 |
} |
| 901 |
|
| 902 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 903 |
address div.left { |
| 904 |
text-align: left; |
| 905 |
} |
| 906 |
address div.right { |
| 907 |
text-align: right; |
| 908 |
} |
| 909 |
|
| 910 |
/* Provide table alignment support. We can't use the alignX classes above |
| 911 |
since they do unwanted things with caption and other styling. */ |
| 912 |
table.right { |
| 913 |
margin-left: auto; |
| 914 |
margin-right: 0; |
| 915 |
} |
| 916 |
table.center { |
| 917 |
margin-left: auto; |
| 918 |
margin-right: auto; |
| 919 |
} |
| 920 |
table.left { |
| 921 |
margin-left: 0; |
| 922 |
margin-right: auto; |
| 923 |
} |
| 924 |
|
| 925 |
/* Give the table caption label the same styling as the figcaption */ |
| 926 |
caption a[href] { |
| 927 |
color: #222; |
| 928 |
} |
| 929 |
|
| 930 |
@media print { |
| 931 |
.toplink { |
| 932 |
display: none; |
| 933 |
} |
| 934 |
|
| 935 |
/* avoid overwriting the top border line with the ToC header */ |
| 936 |
#toc { |
| 937 |
padding-top: 1px; |
| 938 |
} |
| 939 |
|
| 940 |
/* Avoid page breaks inside dl and author address entries */ |
| 941 |
.vcard { |
| 942 |
page-break-inside: avoid; |
| 943 |
} |
| 944 |
|
| 945 |
} |
| 946 |
/* Tweak the bcp14 keyword presentation */ |
| 947 |
.bcp14 { |
| 948 |
font-variant: small-caps; |
| 949 |
font-weight: bold; |
| 950 |
font-size: 0.9em; |
| 951 |
} |
| 952 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 953 |
h2 { |
| 954 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 955 |
padding-top: 31px; |
| 956 |
} |
| 957 |
h3 { |
| 958 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 959 |
padding-top: 24px; |
| 960 |
} |
| 961 |
h4 { |
| 962 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 963 |
padding-top: 24px; |
| 964 |
} |
| 965 |
/* Float artwork pilcrow to the right */ |
| 966 |
@media screen { |
| 967 |
.artwork a.pilcrow { |
| 968 |
display: block; |
| 969 |
line-height: 0.7; |
| 970 |
margin-top: 0.15em; |
| 971 |
} |
| 972 |
} |
| 973 |
/* Make pilcrows on dd visible */ |
| 974 |
@media screen { |
| 975 |
dd:hover > a.pilcrow { |
| 976 |
visibility: visible; |
| 977 |
} |
| 978 |
} |
| 979 |
/* Make the placement of figcaption match that of a table's caption |
| 980 |
by removing the figure's added bottom margin */ |
| 981 |
.alignLeft.art-text, |
| 982 |
.alignCenter.art-text, |
| 983 |
.alignRight.art-text { |
| 984 |
margin-bottom: 0; |
| 985 |
} |
| 986 |
.alignLeft, |
| 987 |
.alignCenter, |
| 988 |
.alignRight { |
| 989 |
margin: 1em 0 0 0; |
| 990 |
} |
| 991 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 992 |
possibly even requiring a new line */ |
| 993 |
@media print { |
| 994 |
a.pilcrow { |
| 995 |
display: none; |
| 996 |
} |
| 997 |
} |
| 998 |
/* Styling for the external metadata */ |
| 999 |
div#external-metadata { |
| 1000 |
background-color: #eee; |
| 1001 |
padding: 0.5em; |
| 1002 |
margin-bottom: 0.5em; |
| 1003 |
display: none; |
| 1004 |
} |
| 1005 |
div#internal-metadata { |
| 1006 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1007 |
} |
| 1008 |
/* Styling for title RFC Number */ |
| 1009 |
h1#rfcnum { |
| 1010 |
clear: both; |
| 1011 |
margin: 0 0 -1em; |
| 1012 |
padding: 1em 0 0 0; |
| 1013 |
} |
| 1014 |
/* Make .olPercent look the same as <ol><li> */ |
| 1015 |
dl.olPercent > dd { |
| 1016 |
margin-bottom: 0.25em; |
| 1017 |
min-height: initial; |
| 1018 |
} |
| 1019 |
/* Give aside some styling to set it apart */ |
| 1020 |
aside { |
| 1021 |
border-left: 1px solid #ddd; |
| 1022 |
margin: 1em 0 1em 2em; |
| 1023 |
padding: 0.2em 2em; |
| 1024 |
} |
| 1025 |
aside > dl, |
| 1026 |
aside > ol, |
| 1027 |
aside > ul, |
| 1028 |
aside > table, |
| 1029 |
aside > p { |
| 1030 |
margin-bottom: 0.5em; |
| 1031 |
} |
| 1032 |
/* Additional page break settings */ |
| 1033 |
@media print { |
| 1034 |
figcaption, table caption { |
| 1035 |
page-break-before: avoid; |
| 1036 |
} |
| 1037 |
} |
| 1038 |
/* Font size adjustments for print */ |
| 1039 |
@media print { |
| 1040 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1041 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1042 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1043 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1044 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1045 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1046 |
} |
| 1047 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1048 |
@media print { |
| 1049 |
.artwork, |
| 1050 |
.sourcecode { |
| 1051 |
margin-bottom: 1em; |
| 1052 |
} |
| 1053 |
} |
| 1054 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1055 |
table { |
| 1056 |
min-width: 20em; |
| 1057 |
} |
| 1058 |
/* ol type a */ |
| 1059 |
ol.type-a { list-style-type: lower-alpha; } |
| 1060 |
ol.type-A { list-style-type: upper-alpha; } |
| 1061 |
ol.type-i { list-style-type: lower-roman; } |
| 1062 |
ol.type-I { list-style-type: lower-roman; } |
| 1063 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1064 |
and increase the contrast between border and odd row background sligthtly */ |
| 1065 |
table { |
| 1066 |
border: 1px solid #ddd; |
| 1067 |
} |
| 1068 |
td { |
| 1069 |
border-top: 1px solid #ddd; |
| 1070 |
} |
| 1071 |
tr:nth-child(2n+1) > td { |
| 1072 |
background-color: #f8f8f8; |
| 1073 |
} |
| 1074 |
/* Use style rules to govern display of the TOC. */ |
| 1075 |
@media screen and (max-width: 1023px) { |
| 1076 |
#toc nav { display: none; } |
| 1077 |
#toc.active nav { display: block; } |
| 1078 |
} |
| 1079 |
/* Add support for keepWithNext */ |
| 1080 |
.keepWithNext { |
| 1081 |
break-after: avoid-page; |
| 1082 |
break-after: avoid-page; |
| 1083 |
} |
| 1084 |
/* Add support for keepWithPrevious */ |
| 1085 |
.keepWithPrevious { |
| 1086 |
break-before: avoid-page; |
| 1087 |
} |
| 1088 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1089 |
figure, pre, table, .artwork, .sourcecode { |
| 1090 |
break-before: avoid-page; |
| 1091 |
break-after: auto; |
| 1092 |
} |
| 1093 |
/* Avoid breaks between <dt> and <dd> */ |
| 1094 |
dl { |
| 1095 |
break-before: auto; |
| 1096 |
break-inside: auto; |
| 1097 |
} |
| 1098 |
dt { |
| 1099 |
break-before: auto; |
| 1100 |
break-after: avoid-page; |
| 1101 |
} |
| 1102 |
dd { |
| 1103 |
break-before: avoid-page; |
| 1104 |
break-after: auto; |
| 1105 |
orphans: 3; |
| 1106 |
widows: 3 |
| 1107 |
} |
| 1108 |
span.break, dd.break { |
| 1109 |
margin-bottom: 0; |
| 1110 |
min-height: 0; |
| 1111 |
break-before: auto; |
| 1112 |
break-inside: auto; |
| 1113 |
break-after: auto; |
| 1114 |
} |
| 1115 |
/* Undo break-before ToC */ |
| 1116 |
@media print { |
| 1117 |
#toc { |
| 1118 |
break-before: auto; |
| 1119 |
} |
| 1120 |
} |
| 1121 |
/* Text in compact lists should not get extra bottim margin space, |
| 1122 |
since that would makes the list not compact */ |
| 1123 |
ul.compact p, .ulCompact p, |
| 1124 |
ol.compact p, .olCompact p { |
| 1125 |
margin: 0; |
| 1126 |
} |
| 1127 |
/* But the list as a whole needs the extra space at the end */ |
| 1128 |
section ul.compact, |
| 1129 |
section .ulCompact, |
| 1130 |
section ol.compact, |
| 1131 |
section .olCompact { |
| 1132 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1133 |
} |
| 1134 |
/* The tt and code background above interferes with for instance table cell |
| 1135 |
backgrounds. Changed to something a bit more selective. */ |
| 1136 |
tt, code { |
| 1137 |
background-color: transparent; |
| 1138 |
} |
| 1139 |
p tt, p code, li tt, li code { |
| 1140 |
background-color: #f8f8f8; |
| 1141 |
} |
| 1142 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1143 |
pre { |
| 1144 |
margin-top: 0.5px; |
| 1145 |
} |
| 1146 |
/* Tweak the comact list text */ |
| 1147 |
ul.compact, .ulCompact, |
| 1148 |
ol.compact, .olCompact, |
| 1149 |
dl.compact, .dlCompact { |
| 1150 |
line-height: normal; |
| 1151 |
} |
| 1152 |
/* Don't add top margin for nested lists */ |
| 1153 |
li > ul, li > ol, li > dl, |
| 1154 |
dd > ul, dd > ol, dd > dl, |
| 1155 |
dl > dd > dl { |
| 1156 |
margin-top: initial; |
| 1157 |
} |
| 1158 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1159 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1160 |
dd > div.artwork:first-child, |
| 1161 |
dd > aside:first-child, |
| 1162 |
dd > figure:first-child, |
| 1163 |
dd > ol:first-child, |
| 1164 |
dd > div:first-child > pre.sourcecode, |
| 1165 |
dd > table:first-child, |
| 1166 |
dd > ul:first-child { |
| 1167 |
clear: left; |
| 1168 |
} |
| 1169 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1170 |
dt+dd:empty::before{ |
| 1171 |
content: "\00a0"; |
| 1172 |
} |
| 1173 |
</style> |
| 1174 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1175 |
<link href="https://dx.doi.org/10.17487/rfc8938" rel="alternate"> |
| 1176 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1177 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-detnet-data-plane-framework-06" rel="prev"> |
| 1178 |
</head> |
| 1179 |
<body> |
| 1180 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1181 |
<table class="ears"> |
| 1182 |
<thead><tr> |
| 1183 |
<td class="left">RFC 8938</td> |
| 1184 |
<td class="center">DetNet Data Plane Framework</td> |
| 1185 |
<td class="right">November 2020</td> |
| 1186 |
</tr></thead> |
| 1187 |
<tfoot><tr> |
| 1188 |
<td class="left">Varga, et al.</td> |
| 1189 |
<td class="center">Informational</td> |
| 1190 |
<td class="right">[Page]</td> |
| 1191 |
</tr></tfoot> |
| 1192 |
</table> |
| 1193 |
<div id="external-metadata" class="document-information"></div> |
| 1194 |
<div id="internal-metadata" class="document-information"> |
| 1195 |
<dl id="identifiers"> |
| 1196 |
<dt class="label-stream">Stream:</dt> |
| 1197 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1198 |
<dt class="label-rfc">RFC:</dt> |
| 1199 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8938" class="eref">8938</a></dd> |
| 1200 |
<dt class="label-category">Category:</dt> |
| 1201 |
<dd class="category">Informational</dd> |
| 1202 |
<dt class="label-published">Published:</dt> |
| 1203 |
<dd class="published"> |
| 1204 |
<time datetime="2020-11" class="published">November 2020</time> |
| 1205 |
</dd> |
| 1206 |
<dt class="label-issn">ISSN:</dt> |
| 1207 |
<dd class="issn">2070-1721</dd> |
| 1208 |
<dt class="label-authors">Authors:</dt> |
| 1209 |
<dd class="authors"> |
| 1210 |
<div class="author"> |
| 1211 |
<div class="author-name">B. Varga, <span class="editor">Ed.</span> |
| 1212 |
</div> |
| 1213 |
<div class="org">Ericsson</div> |
| 1214 |
</div> |
| 1215 |
<div class="author"> |
| 1216 |
<div class="author-name">J. Farkas</div> |
| 1217 |
<div class="org">Ericsson</div> |
| 1218 |
</div> |
| 1219 |
<div class="author"> |
| 1220 |
<div class="author-name">L. Berger</div> |
| 1221 |
<div class="org">LabN Consulting, L.L.C.</div> |
| 1222 |
</div> |
| 1223 |
<div class="author"> |
| 1224 |
<div class="author-name">A. Malis</div> |
| 1225 |
<div class="org">Malis Consulting</div> |
| 1226 |
</div> |
| 1227 |
<div class="author"> |
| 1228 |
<div class="author-name">S. Bryant</div> |
| 1229 |
<div class="org">Futurewei Technologies</div> |
| 1230 |
</div> |
| 1231 |
</dd> |
| 1232 |
</dl> |
| 1233 |
</div> |
| 1234 |
<h1 id="rfcnum">RFC 8938</h1> |
| 1235 |
<h1 id="title">Deterministic Networking (DetNet) Data Plane Framework</h1> |
| 1236 |
<section id="section-abstract"> |
| 1237 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1238 |
<p id="section-abstract-1"> |
| 1239 |
This document provides an overall framework for the Deterministic |
| 1240 |
Networking (DetNet) |
| 1241 |
data plane. It covers concepts and considerations that |
| 1242 |
are generally common to any DetNet data plane |
| 1243 |
specification. It describes related Controller Plane |
| 1244 |
considerations as well.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1245 |
</section> |
| 1246 |
<div id="status-of-memo"> |
| 1247 |
<section id="section-boilerplate.1"> |
| 1248 |
<h2 id="name-status-of-this-memo"> |
| 1249 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1250 |
</h2> |
| 1251 |
<p id="section-boilerplate.1-1"> |
| 1252 |
This document is not an Internet Standards Track specification; it is |
| 1253 |
published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1254 |
<p id="section-boilerplate.1-2"> |
| 1255 |
This document is a product of the Internet Engineering Task Force |
| 1256 |
(IETF). It represents the consensus of the IETF community. It has |
| 1257 |
received public review and has been approved for publication by the |
| 1258 |
Internet Engineering Steering Group (IESG). Not all documents |
| 1259 |
approved by the IESG are candidates for any level of Internet |
| 1260 |
Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1261 |
<p id="section-boilerplate.1-3"> |
| 1262 |
Information about the current status of this document, any |
| 1263 |
errata, and how to provide feedback on it may be obtained at |
| 1264 |
<span><a href="https://www.rfc-editor.org/info/rfc8938">https://www.rfc-editor.org/info/rfc8938</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1265 |
</section> |
| 1266 |
</div> |
| 1267 |
<div id="copyright"> |
| 1268 |
<section id="section-boilerplate.2"> |
| 1269 |
<h2 id="name-copyright-notice"> |
| 1270 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1271 |
</h2> |
| 1272 |
<p id="section-boilerplate.2-1"> |
| 1273 |
Copyright (c) 2020 IETF Trust and the persons identified as the |
| 1274 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1275 |
<p id="section-boilerplate.2-2"> |
| 1276 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1277 |
Provisions Relating to IETF Documents |
| 1278 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1279 |
publication of this document. Please review these documents |
| 1280 |
carefully, as they describe your rights and restrictions with |
| 1281 |
respect to this document. Code Components extracted from this |
| 1282 |
document must include Simplified BSD License text as described in |
| 1283 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1284 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1285 |
</section> |
| 1286 |
</div> |
| 1287 |
<div id="toc"> |
| 1288 |
<section id="section-toc.1"> |
| 1289 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1290 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1291 |
</h2> |
| 1292 |
<nav class="toc"><ul class="compact ulEmpty toc"> |
| 1293 |
<li class="compact ulEmpty toc" id="section-toc.1-1.1"> |
| 1294 |
<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><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p> |
| 1295 |
</li> |
| 1296 |
<li class="compact ulEmpty toc" id="section-toc.1-1.2"> |
| 1297 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1298 |
<ul class="ulEmpty compact toc"> |
| 1299 |
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.1"> |
| 1300 |
<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><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p> |
| 1301 |
</li> |
| 1302 |
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.2"> |
| 1303 |
<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><a href="#section-toc.1-1.2.2.2.1" class="pilcrow">¶</a></p> |
| 1304 |
</li> |
| 1305 |
</ul> |
| 1306 |
</li> |
| 1307 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3"> |
| 1308 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-overview-of-the-detnet-data" class="xref">Overview of the DetNet Data Plane</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1309 |
<ul class="ulEmpty compact toc"> |
| 1310 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.1"> |
| 1311 |
<p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-data-plane-characteristics" class="xref">Data Plane Characteristics</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p> |
| 1312 |
<ul class="ulEmpty compact toc"> |
| 1313 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.1.2.1"> |
| 1314 |
<p id="section-toc.1-1.3.2.1.2.1.1"><a href="#section-3.1.1" class="xref">3.1.1</a>. <a href="#name-data-plane-technology" class="xref">Data Plane Technology</a><a href="#section-toc.1-1.3.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1315 |
</li> |
| 1316 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.1.2.2"> |
| 1317 |
<p id="section-toc.1-1.3.2.1.2.2.1"><a href="#section-3.1.2" class="xref">3.1.2</a>. <a href="#name-encapsulation" class="xref">Encapsulation</a><a href="#section-toc.1-1.3.2.1.2.2.1" class="pilcrow">¶</a></p> |
| 1318 |
</li> |
| 1319 |
</ul> |
| 1320 |
</li> |
| 1321 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.2"> |
| 1322 |
<p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>. <a href="#name-detnet-specific-metadata" class="xref">DetNet-Specific Metadata</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p> |
| 1323 |
</li> |
| 1324 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.3"> |
| 1325 |
<p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>. <a href="#name-detnet-ip-data-plane" class="xref">DetNet IP Data Plane</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p> |
| 1326 |
</li> |
| 1327 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.4"> |
| 1328 |
<p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>. <a href="#name-detnet-mpls-data-plane" class="xref">DetNet MPLS Data Plane</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p> |
| 1329 |
</li> |
| 1330 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5"> |
| 1331 |
<p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>. <a href="#name-further-detnet-data-plane-c" class="xref">Further DetNet Data Plane Considerations</a><a href="#section-toc.1-1.3.2.5.1" class="pilcrow">¶</a></p> |
| 1332 |
<ul class="ulEmpty compact toc"> |
| 1333 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5.2.1"> |
| 1334 |
<p id="section-toc.1-1.3.2.5.2.1.1"><a href="#section-3.5.1" class="xref">3.5.1</a>. <a href="#name-functions-provided-on-a-per" class="xref">Functions Provided on a Per-Flow Basis</a><a href="#section-toc.1-1.3.2.5.2.1.1" class="pilcrow">¶</a></p> |
| 1335 |
</li> |
| 1336 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5.2.2"> |
| 1337 |
<p id="section-toc.1-1.3.2.5.2.2.1"><a href="#section-3.5.2" class="xref">3.5.2</a>. <a href="#name-service-protection-2" class="xref">Service Protection</a><a href="#section-toc.1-1.3.2.5.2.2.1" class="pilcrow">¶</a></p> |
| 1338 |
</li> |
| 1339 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5.2.3"> |
| 1340 |
<p id="section-toc.1-1.3.2.5.2.3.1"><a href="#section-3.5.3" class="xref">3.5.3</a>. <a href="#name-aggregation-considerations" class="xref">Aggregation Considerations</a><a href="#section-toc.1-1.3.2.5.2.3.1" class="pilcrow">¶</a></p> |
| 1341 |
</li> |
| 1342 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5.2.4"> |
| 1343 |
<p id="section-toc.1-1.3.2.5.2.4.1"><a href="#section-3.5.4" class="xref">3.5.4</a>. <a href="#name-end-system-specific-conside" class="xref">End-System-Specific Considerations</a><a href="#section-toc.1-1.3.2.5.2.4.1" class="pilcrow">¶</a></p> |
| 1344 |
</li> |
| 1345 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3.2.5.2.5"> |
| 1346 |
<p id="section-toc.1-1.3.2.5.2.5.1"><a href="#section-3.5.5" class="xref">3.5.5</a>. <a href="#name-sub-network-considerations" class="xref">Sub-network Considerations</a><a href="#section-toc.1-1.3.2.5.2.5.1" class="pilcrow">¶</a></p> |
| 1347 |
</li> |
| 1348 |
</ul> |
| 1349 |
</li> |
| 1350 |
</ul> |
| 1351 |
</li> |
| 1352 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4"> |
| 1353 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-controller-plane-management" class="xref">Controller Plane (Management and Control) Considerations</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1354 |
<ul class="ulEmpty compact toc"> |
| 1355 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.1"> |
| 1356 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-detnet-controller-plane-req" class="xref">DetNet Controller Plane Requirements</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1357 |
</li> |
| 1358 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2"> |
| 1359 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-generic-controller-plane-co" class="xref">Generic Controller Plane Considerations</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1360 |
<ul class="ulEmpty compact toc"> |
| 1361 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2.2.1"> |
| 1362 |
<p id="section-toc.1-1.4.2.2.2.1.1"><a href="#section-4.2.1" class="xref">4.2.1</a>. <a href="#name-flow-aggregation-control" class="xref">Flow Aggregation Control</a><a href="#section-toc.1-1.4.2.2.2.1.1" class="pilcrow">¶</a></p> |
| 1363 |
</li> |
| 1364 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2.2.2"> |
| 1365 |
<p id="section-toc.1-1.4.2.2.2.2.1"><a href="#section-4.2.2" class="xref">4.2.2</a>. <a href="#name-explicit-routes-2" class="xref">Explicit Routes</a><a href="#section-toc.1-1.4.2.2.2.2.1" class="pilcrow">¶</a></p> |
| 1366 |
</li> |
| 1367 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2.2.3"> |
| 1368 |
<p id="section-toc.1-1.4.2.2.2.3.1"><a href="#section-4.2.3" class="xref">4.2.3</a>. <a href="#name-contention-loss-and-jitter-" class="xref">Contention Loss and Jitter Reduction</a><a href="#section-toc.1-1.4.2.2.2.3.1" class="pilcrow">¶</a></p> |
| 1369 |
</li> |
| 1370 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2.2.4"> |
| 1371 |
<p id="section-toc.1-1.4.2.2.2.4.1"><a href="#section-4.2.4" class="xref">4.2.4</a>. <a href="#name-bidirectional-traffic" class="xref">Bidirectional Traffic</a><a href="#section-toc.1-1.4.2.2.2.4.1" class="pilcrow">¶</a></p> |
| 1372 |
</li> |
| 1373 |
</ul> |
| 1374 |
</li> |
| 1375 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.3"> |
| 1376 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-packet-replication-eliminat" class="xref">Packet Replication, Elimination, and Ordering Functions (PREOF)</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p> |
| 1377 |
</li> |
| 1378 |
</ul> |
| 1379 |
</li> |
| 1380 |
<li class="compact ulEmpty toc" id="section-toc.1-1.5"> |
| 1381 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1382 |
</li> |
| 1383 |
<li class="compact ulEmpty toc" id="section-toc.1-1.6"> |
| 1384 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1385 |
</li> |
| 1386 |
<li class="compact ulEmpty toc" id="section-toc.1-1.7"> |
| 1387 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1388 |
<ul class="ulEmpty compact toc"> |
| 1389 |
<li class="ulEmpty compact toc" id="section-toc.1-1.7.2.1"> |
| 1390 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p> |
| 1391 |
</li> |
| 1392 |
<li class="ulEmpty compact toc" id="section-toc.1-1.7.2.2"> |
| 1393 |
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p> |
| 1394 |
</li> |
| 1395 |
</ul> |
| 1396 |
</li> |
| 1397 |
<li class="compact ulEmpty toc" id="section-toc.1-1.8"> |
| 1398 |
<p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1399 |
</li> |
| 1400 |
<li class="compact ulEmpty toc" id="section-toc.1-1.9"> |
| 1401 |
<p id="section-toc.1-1.9.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1402 |
</li> |
| 1403 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10"> |
| 1404 |
<p id="section-toc.1-1.10.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1405 |
</li> |
| 1406 |
</ul> |
| 1407 |
</nav> |
| 1408 |
</section> |
| 1409 |
</div> |
| 1410 |
<div id="sec_intro"> |
| 1411 |
<section id="section-1"> |
| 1412 |
<h2 id="name-introduction"> |
| 1413 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1414 |
</h2> |
| 1415 |
<p id="section-1-1"> |
| 1416 |
DetNet (Deterministic Networking) provides the ability to carry |
| 1417 |
specified unicast or multicast data flows for real-time applications |
| 1418 |
with extremely low packet loss rates and assured maximum end-to-end |
| 1419 |
delivery latency. A description of the general background and concepts |
| 1420 |
of DetNet can be found in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1421 |
<p id="section-1-2"> |
| 1422 |
This document describes the concepts needed by any DetNet data plane |
| 1423 |
specification (i.e., the DetNet-specific use of packet header fields) |
| 1424 |
and provides considerations for any corresponding |
| 1425 |
implementation. It covers the building blocks that provide the DetNet |
| 1426 |
service, the DetNet service sub‑layer, and the DetNet forwarding |
| 1427 |
sub‑layer functions as described in the DetNet architecture |
| 1428 |
<span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1429 |
<p id="section-1-3"> |
| 1430 |
The DetNet architecture models the DetNet-related data plane functions |
| 1431 |
as being decomposed into two sub‑layers: a service sub‑layer and a forwarding |
| 1432 |
sub‑layer. The service sub‑layer is used to provide DetNet service |
| 1433 |
protection and reordering. The forwarding sub‑layer leverages traffic |
| 1434 |
engineering mechanisms and provides congestion protection (low loss, |
| 1435 |
assured latency, and limited out-of-order delivery). A particular |
| 1436 |
forwarding sub‑layer may have capabilities that are not available on |
| 1437 |
other forwarding sub‑layers. DetNet makes use of the existing |
| 1438 |
forwarding sub‑layers with their respective capabilities and does not |
| 1439 |
require 1:1 equivalence between different forwarding sub‑layer |
| 1440 |
capabilities.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1441 |
<p id="section-1-4"> |
| 1442 |
As part of the service sub‑layer functions, this document describes |
| 1443 |
typical DetNet node data plane operation. It describes the functionality |
| 1444 |
and operation of the Packet Replication Function (PRF), the Packet |
| 1445 |
Elimination Function (PEF), and the Packet Ordering Function (POF) within the service |
| 1446 |
sub‑layer. Furthermore, it describes the forwarding sub‑layer.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1447 |
<p id="section-1-5"> |
| 1448 |
As defined in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>, |
| 1449 |
DetNet flows may be carried over network technologies that can provide |
| 1450 |
service characteristics required by DetNet. For example, DetNet MPLS flows can be carried over IEEE 802.1 Time-Sensitive |
| 1451 |
Networking (TSN) sub-networks <span>[<a href="#IEEE802.1TSNTG" class="xref">IEEE802.1TSNTG</a>]</span>. However, IEEE 802.1 TSN support is not required in |
| 1452 |
DetNet. TSN frame preemption is an example of a forwarding layer capability |
| 1453 |
that is typically not replicated in other forwarding technologies. Most of |
| 1454 |
DetNet's benefits can be gained by running over a data-link layer that has |
| 1455 |
not been specifically enhanced to support all TSN capabilities, but for such |
| 1456 |
networks and traffic mixes, delay and jitter performance may vary due to the |
| 1457 |
forwarding sub‑layer's intrinsic properties.<a href="#section-1-5" class="pilcrow">¶</a></p> |
| 1458 |
<p id="section-1-6"> |
| 1459 |
Different application flows, such as Ethernet or IP, can be mapped |
| 1460 |
on top of DetNet. DetNet can optionally reuse header information |
| 1461 |
provided by, or shared with, applications. An example of shared header |
| 1462 |
fields can be found in <span>[<a href="#RFC8939" class="xref">RFC8939</a>]</span>.<a href="#section-1-6" class="pilcrow">¶</a></p> |
| 1463 |
<p id="section-1-7"> |
| 1464 |
This document also covers |
| 1465 |
basic concepts related to the Controller Plane and Operations, |
| 1466 |
Administration, and Maintenance (OAM). |
| 1467 |
Data plane OAM specifics are out of scope for this document.<a href="#section-1-7" class="pilcrow">¶</a></p> |
| 1468 |
</section> |
| 1469 |
</div> |
| 1470 |
<section id="section-2"> |
| 1471 |
<h2 id="name-terminology"> |
| 1472 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1473 |
</h2> |
| 1474 |
<section id="section-2.1"> |
| 1475 |
<h3 id="name-terms-used-in-this-document"> |
| 1476 |
<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> |
| 1477 |
</h3> |
| 1478 |
<p id="section-2.1-1"> |
| 1479 |
This document uses the terminology established in the DetNet |
| 1480 |
architecture <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>, and |
| 1481 |
it is assumed that the reader is familiar with that document |
| 1482 |
and its terminology.<a href="#section-2.1-1" class="pilcrow">¶</a></p> |
| 1483 |
</section> |
| 1484 |
<section id="section-2.2"> |
| 1485 |
<h3 id="name-abbreviations"> |
| 1486 |
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-abbreviations" class="section-name selfRef">Abbreviations</a> |
| 1487 |
</h3> |
| 1488 |
<p id="section-2.2-1"> |
| 1489 |
The following abbreviations are used in this document:<a href="#section-2.2-1" class="pilcrow">¶</a></p> |
| 1490 |
<span class="break"></span><dl class="dlParallel" id="section-2.2-2"> |
| 1491 |
<dt id="section-2.2-2.1">BGP</dt> |
| 1492 |
<dd style="margin-left: 6.0em" id="section-2.2-2.2">Border Gateway Protocol<a href="#section-2.2-2.2" class="pilcrow">¶</a> |
| 1493 |
</dd> |
| 1494 |
<dd class="break"></dd> |
| 1495 |
<dt id="section-2.2-2.3">CoS</dt> |
| 1496 |
<dd style="margin-left: 6.0em" id="section-2.2-2.4">Class of Service<a href="#section-2.2-2.4" class="pilcrow">¶</a> |
| 1497 |
</dd> |
| 1498 |
<dd class="break"></dd> |
| 1499 |
<dt id="section-2.2-2.5">d-CW</dt> |
| 1500 |
<dd style="margin-left: 6.0em" id="section-2.2-2.6">DetNet Control Word<a href="#section-2.2-2.6" class="pilcrow">¶</a> |
| 1501 |
</dd> |
| 1502 |
<dd class="break"></dd> |
| 1503 |
<dt id="section-2.2-2.7">DetNet</dt> |
| 1504 |
<dd style="margin-left: 6.0em" id="section-2.2-2.8">Deterministic Networking<a href="#section-2.2-2.8" class="pilcrow">¶</a> |
| 1505 |
</dd> |
| 1506 |
<dd class="break"></dd> |
| 1507 |
<dt id="section-2.2-2.9">DN</dt> |
| 1508 |
<dd style="margin-left: 6.0em" id="section-2.2-2.10">DetNet<a href="#section-2.2-2.10" class="pilcrow">¶</a> |
| 1509 |
</dd> |
| 1510 |
<dd class="break"></dd> |
| 1511 |
<dt id="section-2.2-2.11">GMPLS</dt> |
| 1512 |
<dd style="margin-left: 6.0em" id="section-2.2-2.12">Generalized Multiprotocol Label Switching<a href="#section-2.2-2.12" class="pilcrow">¶</a> |
| 1513 |
</dd> |
| 1514 |
<dd class="break"></dd> |
| 1515 |
<dt id="section-2.2-2.13">GRE</dt> |
| 1516 |
<dd style="margin-left: 6.0em" id="section-2.2-2.14">Generic Routing Encapsulation<a href="#section-2.2-2.14" class="pilcrow">¶</a> |
| 1517 |
</dd> |
| 1518 |
<dd class="break"></dd> |
| 1519 |
<dt id="section-2.2-2.15">IPsec</dt> |
| 1520 |
<dd style="margin-left: 6.0em" id="section-2.2-2.16">IP Security<a href="#section-2.2-2.16" class="pilcrow">¶</a> |
| 1521 |
</dd> |
| 1522 |
<dd class="break"></dd> |
| 1523 |
<dt id="section-2.2-2.17">L2</dt> |
| 1524 |
<dd style="margin-left: 6.0em" id="section-2.2-2.18">Layer 2<a href="#section-2.2-2.18" class="pilcrow">¶</a> |
| 1525 |
</dd> |
| 1526 |
<dd class="break"></dd> |
| 1527 |
<dt id="section-2.2-2.19">LSP</dt> |
| 1528 |
<dd style="margin-left: 6.0em" id="section-2.2-2.20">Label Switched Path<a href="#section-2.2-2.20" class="pilcrow">¶</a> |
| 1529 |
</dd> |
| 1530 |
<dd class="break"></dd> |
| 1531 |
<dt id="section-2.2-2.21">MPLS</dt> |
| 1532 |
<dd style="margin-left: 6.0em" id="section-2.2-2.22">Multiprotocol Label Switching<a href="#section-2.2-2.22" class="pilcrow">¶</a> |
| 1533 |
</dd> |
| 1534 |
<dd class="break"></dd> |
| 1535 |
<dt id="section-2.2-2.23">OAM</dt> |
| 1536 |
<dd style="margin-left: 6.0em" id="section-2.2-2.24">Operations, Administration, and Maintenance<a href="#section-2.2-2.24" class="pilcrow">¶</a> |
| 1537 |
</dd> |
| 1538 |
<dd class="break"></dd> |
| 1539 |
<dt id="section-2.2-2.25">PCEP</dt> |
| 1540 |
<dd style="margin-left: 6.0em" id="section-2.2-2.26">Path Computation Element Communication Protocol<a href="#section-2.2-2.26" class="pilcrow">¶</a> |
| 1541 |
</dd> |
| 1542 |
<dd class="break"></dd> |
| 1543 |
<dt id="section-2.2-2.27">PEF</dt> |
| 1544 |
<dd style="margin-left: 6.0em" id="section-2.2-2.28">Packet Elimination Function<a href="#section-2.2-2.28" class="pilcrow">¶</a> |
| 1545 |
</dd> |
| 1546 |
<dd class="break"></dd> |
| 1547 |
<dt id="section-2.2-2.29">POF</dt> |
| 1548 |
<dd style="margin-left: 6.0em" id="section-2.2-2.30">Packet Ordering Function<a href="#section-2.2-2.30" class="pilcrow">¶</a> |
| 1549 |
</dd> |
| 1550 |
<dd class="break"></dd> |
| 1551 |
<dt id="section-2.2-2.31">PREOF</dt> |
| 1552 |
<dd style="margin-left: 6.0em" id="section-2.2-2.32">Packet Replication, Elimination, and Ordering Functions<a href="#section-2.2-2.32" class="pilcrow">¶</a> |
| 1553 |
</dd> |
| 1554 |
<dd class="break"></dd> |
| 1555 |
<dt id="section-2.2-2.33">PRF</dt> |
| 1556 |
<dd style="margin-left: 6.0em" id="section-2.2-2.34">Packet Replication Function<a href="#section-2.2-2.34" class="pilcrow">¶</a> |
| 1557 |
</dd> |
| 1558 |
<dd class="break"></dd> |
| 1559 |
<dt id="section-2.2-2.35">PSN</dt> |
| 1560 |
<dd style="margin-left: 6.0em" id="section-2.2-2.36">Packet Switched Network<a href="#section-2.2-2.36" class="pilcrow">¶</a> |
| 1561 |
</dd> |
| 1562 |
<dd class="break"></dd> |
| 1563 |
<dt id="section-2.2-2.37">QoS</dt> |
| 1564 |
<dd style="margin-left: 6.0em" id="section-2.2-2.38">Quality of Service<a href="#section-2.2-2.38" class="pilcrow">¶</a> |
| 1565 |
</dd> |
| 1566 |
<dd class="break"></dd> |
| 1567 |
<dt id="section-2.2-2.39">S-Label</dt> |
| 1568 |
<dd style="margin-left: 6.0em" id="section-2.2-2.40">DetNet "service" label<a href="#section-2.2-2.40" class="pilcrow">¶</a> |
| 1569 |
</dd> |
| 1570 |
<dd class="break"></dd> |
| 1571 |
<dt id="section-2.2-2.41">TDM</dt> |
| 1572 |
<dd style="margin-left: 6.0em" id="section-2.2-2.42">Time-Division Multiplexing<a href="#section-2.2-2.42" class="pilcrow">¶</a> |
| 1573 |
</dd> |
| 1574 |
<dd class="break"></dd> |
| 1575 |
<dt id="section-2.2-2.43">TSN</dt> |
| 1576 |
<dd style="margin-left: 6.0em" id="section-2.2-2.44">Time-Sensitive Networking<a href="#section-2.2-2.44" class="pilcrow">¶</a> |
| 1577 |
</dd> |
| 1578 |
<dd class="break"></dd> |
| 1579 |
<dt id="section-2.2-2.45">YANG</dt> |
| 1580 |
<dd style="margin-left: 6.0em" id="section-2.2-2.46">Yet Another Next Generation<a href="#section-2.2-2.46" class="pilcrow">¶</a> |
| 1581 |
</dd> |
| 1582 |
<dd class="break"></dd> |
| 1583 |
</dl> |
| 1584 |
</section> |
| 1585 |
</section> |
| 1586 |
<div id="sec_dt_dp"> |
| 1587 |
<section id="section-3"> |
| 1588 |
<h2 id="name-overview-of-the-detnet-data"> |
| 1589 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-overview-of-the-detnet-data" class="section-name selfRef">Overview of the DetNet Data Plane</a> |
| 1590 |
</h2> |
| 1591 |
<p id="section-3-1"> |
| 1592 |
This document describes how application flows, or App-flows <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>, are |
| 1593 |
carried over DetNet networks. The DetNet architecture <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span> models the DetNet-related |
| 1594 |
data plane functions as decomposed into two sub‑layers: a service |
| 1595 |
sub‑layer and a forwarding sub‑layer.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1596 |
<p id="section-3-2"> |
| 1597 |
<a href="#ProtStack1" class="xref">Figure 1</a>, reproduced from <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>, |
| 1598 |
shows a logical DetNet service with the two sub‑layers.<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1599 |
<span id="name-detnet-data-plane-protocol-"></span><div id="ProtStack1"> |
| 1600 |
<figure id="figure-1"> |
| 1601 |
<div class="artwork art-text alignCenter" id="section-3-3.1"> |
| 1602 |
<pre> |
| 1603 |
| packets going | ^ packets coming ^ |
| 1604 |
v down the stack v | up the stack | |
| 1605 |
+-----------------------+ +-----------------------+ |
| 1606 |
| Source | | Destination | |
| 1607 |
+-----------------------+ +-----------------------+ |
| 1608 |
| Service sub-layer: | | Service sub-layer: | |
| 1609 |
| Packet sequencing | | Duplicate elimination | |
| 1610 |
| Flow replication | | Flow merging | |
| 1611 |
| Packet encoding | | Packet decoding | |
| 1612 |
+-----------------------+ +-----------------------+ |
| 1613 |
| Forwarding sub-layer: | | Forwarding sub-layer: | |
| 1614 |
| Resource allocation | | Resource allocation | |
| 1615 |
| Explicit routes | | Explicit routes | |
| 1616 |
+-----------------------+ +-----------------------+ |
| 1617 |
| Lower layers | | Lower layers | |
| 1618 |
+-----------------------+ +-----------------------+ |
| 1619 |
v ^ |
| 1620 |
\_________________________/</pre> |
| 1621 |
</div> |
| 1622 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 1623 |
<a href="#name-detnet-data-plane-protocol-" class="selfRef">DetNet Data Plane Protocol Stack</a> |
| 1624 |
</figcaption></figure> |
| 1625 |
</div> |
| 1626 |
<p id="section-3-4"> |
| 1627 |
The DetNet forwarding sub‑layer may be directly provided by the DetNet |
| 1628 |
service sub‑layer -- for example, by IP tunnels or MPLS. |
| 1629 |
Alternatively, an overlay approach |
| 1630 |
may be used in which the packet is natively carried between key nodes |
| 1631 |
within the DetNet network (say, between PREOF nodes), and a sub‑layer is |
| 1632 |
used to provide the information needed to reach the next hop in the |
| 1633 |
overlay.<a href="#section-3-4" class="pilcrow">¶</a></p> |
| 1634 |
<p id="section-3-5"> |
| 1635 |
The forwarding sub‑layer provides the QoS-related functions needed by |
| 1636 |
the DetNet flow. It may do this directly through the use of queuing |
| 1637 |
techniques and traffic engineering methods, or it may do this through |
| 1638 |
the assistance of its underlying connectivity. For example, it may call |
| 1639 |
upon Ethernet TSN capabilities defined in IEEE 802.1 TSN <span>[<a href="#IEEE802.1TSNTG" class="xref">IEEE802.1TSNTG</a>]</span>. The forwarding sub‑layer uses |
| 1640 |
buffer resources for packet queuing, as well as reservation and |
| 1641 |
allocation of bandwidth capacity resources.<a href="#section-3-5" class="pilcrow">¶</a></p> |
| 1642 |
<p id="section-3-6"> |
| 1643 |
The service sub‑layer provides additional support beyond the |
| 1644 |
connectivity function of the forwarding sub‑layer. See |
| 1645 |
<a href="#PREOF" class="xref">Section 4.3</a> regarding PREOF. The POF uses sequence numbers |
| 1646 |
added to packets, enabling a range of packet order protection from |
| 1647 |
simple ordering and dropping out-of-order packets to more complex |
| 1648 |
reordering of a fixed number of out-of-order, minimally delayed |
| 1649 |
packets. Reordering requires buffer resources and has an impact on the |
| 1650 |
delay and jitter of packets in the DetNet flow.<a href="#section-3-6" class="pilcrow">¶</a></p> |
| 1651 |
<p id="section-3-7"> |
| 1652 |
The method of instantiating each of the layers is specific to the |
| 1653 |
particular DetNet data plane method, and more than one approach may |
| 1654 |
be applicable to a given network type.<a href="#section-3-7" class="pilcrow">¶</a></p> |
| 1655 |
<div id="sec_dp_char"> |
| 1656 |
<section id="section-3.1"> |
| 1657 |
<h3 id="name-data-plane-characteristics"> |
| 1658 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-data-plane-characteristics" class="section-name selfRef">Data Plane Characteristics</a> |
| 1659 |
</h3> |
| 1660 |
<p id="section-3.1-1"> |
| 1661 |
The data plane has two major characteristics: the technology and |
| 1662 |
the encapsulation, as discussed below.<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1663 |
<div id="sec_dp_tech"> |
| 1664 |
<section id="section-3.1.1"> |
| 1665 |
<h4 id="name-data-plane-technology"> |
| 1666 |
<a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-data-plane-technology" class="section-name selfRef">Data Plane Technology</a> |
| 1667 |
</h4> |
| 1668 |
<p id="section-3.1.1-1"> |
| 1669 |
The DetNet data plane is provided by the DetNet service and forwarding sub‑layers. |
| 1670 |
The DetNet service sub‑layer |
| 1671 |
generally provides its functions for the DetNet application flows by using or applying |
| 1672 |
existing standardized headers and/or encapsulations. The DetNet |
| 1673 |
forwarding sub‑layer may provide capabilities leveraging that same |
| 1674 |
header or encapsulation technology (e.g., DN IP or DN MPLS), or it |
| 1675 |
may be achieved via other technologies, as shown in <a href="#dn_svc_encaps" class="xref">Figure 2</a> below. |
| 1676 |
DetNet is currently defined for operation over packet-switched (IP) |
| 1677 |
networks or label-switched (MPLS) networks.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p> |
| 1678 |
</section> |
| 1679 |
</div> |
| 1680 |
<div id="sec_dp_encap"> |
| 1681 |
<section id="section-3.1.2"> |
| 1682 |
<h4 id="name-encapsulation"> |
| 1683 |
<a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-encapsulation" class="section-name selfRef">Encapsulation</a> |
| 1684 |
</h4> |
| 1685 |
<p id="section-3.1.2-1"> |
| 1686 |
DetNet encodes specific flow attributes |
| 1687 |
(flow identity and sequence number) in packets. |
| 1688 |
For example, in DetNet IP, |
| 1689 |
zero encapsulation is used, and no sequence number |
| 1690 |
is available; in DetNet MPLS, DetNet-specific information may be added |
| 1691 |
explicitly to the packets in the form of an S-Label and a d-CW |
| 1692 |
<span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span>.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p> |
| 1693 |
<p id="section-3.1.2-2"> |
| 1694 |
The encapsulation of a DetNet flow allows it to be sent over a |
| 1695 |
data plane technology other than its native type. |
| 1696 |
DetNet uses header information to perform traffic classification, |
| 1697 |
i.e., identify DetNet flows, and provide DetNet service and |
| 1698 |
forwarding functions. As mentioned above, DetNet may add headers, |
| 1699 |
as is the case for DN MPLS, or may use headers that are already |
| 1700 |
present, as is the case for DN IP. |
| 1701 |
<a href="#dn_svc_encaps" class="xref">Figure 2</a> illustrates some relationships |
| 1702 |
between the components.<a href="#section-3.1.2-2" class="pilcrow">¶</a></p> |
| 1703 |
<span id="name-detnet-service-examples"></span><div id="dn_svc_encaps"> |
| 1704 |
<figure id="figure-2"> |
| 1705 |
<div class="artwork art-text alignCenter" id="section-3.1.2-3.1"> |
| 1706 |
<pre> |
| 1707 |
+-----+ |
| 1708 |
| TSN | |
| 1709 |
+-------+ +-+-----+-+ |
| 1710 |
| DN IP | | DN MPLS | |
| 1711 |
+--+--+----+----+ +-+---+-----+-+ |
| 1712 |
| TSN | DN MPLS | | TSN | DN IP | |
| 1713 |
+-----+---------+ +-----+-------+</pre> |
| 1714 |
</div> |
| 1715 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 1716 |
<a href="#name-detnet-service-examples" class="selfRef">DetNet Service Examples</a> |
| 1717 |
</figcaption></figure> |
| 1718 |
</div> |
| 1719 |
<p id="section-3.1.2-4"> |
| 1720 |
The use of encapsulation is also required if additional information |
| 1721 |
(metadata) is needed by the DetNet data plane and either (1) there is |
| 1722 |
no ability to include it in the client data packet or (2) the |
| 1723 |
specification of the client data plane does not permit the |
| 1724 |
modification of the packet to include additional data. An example of |
| 1725 |
such metadata is the inclusion of a sequence number required by |
| 1726 |
PREOF.<a href="#section-3.1.2-4" class="pilcrow">¶</a></p> |
| 1727 |
<p id="section-3.1.2-5"> |
| 1728 |
Encapsulation may also be used to carry or aggregate flows for equipment with limited |
| 1729 |
DetNet capability.<a href="#section-3.1.2-5" class="pilcrow">¶</a></p> |
| 1730 |
</section> |
| 1731 |
</div> |
| 1732 |
</section> |
| 1733 |
</div> |
| 1734 |
<div id="sec_dp_metadata"> |
| 1735 |
<section id="section-3.2"> |
| 1736 |
<h3 id="name-detnet-specific-metadata"> |
| 1737 |
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-detnet-specific-metadata" class="section-name selfRef">DetNet-Specific Metadata</a> |
| 1738 |
</h3> |
| 1739 |
<p id="section-3.2-1"> |
| 1740 |
The DetNet data plane can provide or carry the following metadata:<a href="#section-3.2-1" class="pilcrow">¶</a></p> |
| 1741 |
<ol start="1" type="1" class="normal type-1" id="section-3.2-2"> |
| 1742 |
<li id="section-3.2-2.1"> |
| 1743 |
Flow-ID<a href="#section-3.2-2.1" class="pilcrow">¶</a> |
| 1744 |
</li> |
| 1745 |
<li id="section-3.2-2.2"> |
| 1746 |
Sequence number<a href="#section-3.2-2.2" class="pilcrow">¶</a> |
| 1747 |
</li> |
| 1748 |
</ol> |
| 1749 |
<p id="section-3.2-3"> |
| 1750 |
The DetNet data plane framework supports a Flow-ID (for identification of the |
| 1751 |
flow or aggregate flow) and/or a sequence number (for PREOF) for each |
| 1752 |
DetNet flow. The Flow-ID is used by both the service and forwarding sub‑layers, |
| 1753 |
but the sequence number is only used by the service layer. Metadata can also be |
| 1754 |
used for OAM indications and instrumentation of DetNet data plane |
| 1755 |
operation.<a href="#section-3.2-3" class="pilcrow">¶</a></p> |
| 1756 |
<p id="section-3.2-4"> |
| 1757 |
Metadata inclusion can be implicit or explicit. Explicit inclusions |
| 1758 |
involve a dedicated header field that is used to include metadata |
| 1759 |
in a DetNet packet. In the implicit method, part of an already-existing |
| 1760 |
header field is used to encode the metadata.<a href="#section-3.2-4" class="pilcrow">¶</a></p> |
| 1761 |
<p id="section-3.2-5"> |
| 1762 |
Explicit inclusion of metadata is possible through the use of |
| 1763 |
IP options or IP extension headers. New IP options are almost impossible |
| 1764 |
to get standardized or to deploy in an operational network and will |
| 1765 |
not be discussed further in this text. IPv6 extension headers are |
| 1766 |
finding popularity in current IPv6 development work, particularly |
| 1767 |
in connection with Segment Routing of IPv6 (SRv6) and IP OAM. The design |
| 1768 |
of a new IPv6 extension header or the modification of an existing one is |
| 1769 |
a technique available in the toolbox of the DetNet IP data plane designer.<a href="#section-3.2-5" class="pilcrow">¶</a></p> |
| 1770 |
<p id="section-3.2-6"> |
| 1771 |
Explicit inclusion of metadata in an IP packet is also possible |
| 1772 |
through the inclusion of an MPLS label stack and the MPLS d-CW, |
| 1773 |
using one of the methods for carrying MPLS over IP <span>[<a href="#DetNet-MPLS-over-UDP-IP" class="xref">DetNet-MPLS-over-UDP-IP</a>]</span>. This is described in more |
| 1774 |
detail in <a href="#subnet_considerations" class="xref">Section 3.5.5</a>.<a href="#section-3.2-6" class="pilcrow">¶</a></p> |
| 1775 |
<p id="section-3.2-7"> |
| 1776 |
Implicit metadata in IP can be included through the use of the network |
| 1777 |
programming paradigm <span>[<a href="#SRv6-Network-Prog" class="xref">SRv6-Network-Prog</a>]</span>, in which the |
| 1778 |
suffix of an IPv6 address is used to encode additional information |
| 1779 |
for use by the network of the receiving host.<a href="#section-3.2-7" class="pilcrow">¶</a></p> |
| 1780 |
<p id="section-3.2-8"> |
| 1781 |
An MPLS example of explicit metadata is the sequence number |
| 1782 |
used by PREOF, or even the case where all the |
| 1783 |
essential information is included in the DetNet-over-MPLS |
| 1784 |
label stack (the d-CW and the DetNet S-Label).<a href="#section-3.2-8" class="pilcrow">¶</a></p> |
| 1785 |
</section> |
| 1786 |
</div> |
| 1787 |
<div id="sec_dt_ip_dp"> |
| 1788 |
<section id="section-3.3"> |
| 1789 |
<h3 id="name-detnet-ip-data-plane"> |
| 1790 |
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-detnet-ip-data-plane" class="section-name selfRef">DetNet IP Data Plane</a> |
| 1791 |
</h3> |
| 1792 |
<p id="section-3.3-1"> |
| 1793 |
An IP data plane may operate natively or through the use of an |
| 1794 |
encapsulation. |
| 1795 |
Many types of IP encapsulation can satisfy DetNet requirements, |
| 1796 |
and it is anticipated that more than one encapsulation |
| 1797 |
may be deployed -- for example, GRE, IPsec.<a href="#section-3.3-1" class="pilcrow">¶</a></p> |
| 1798 |
<p id="section-3.3-2"> |
| 1799 |
One method of operating an IP DetNet data plane without encapsulation |
| 1800 |
is to use 6-tuple-based flow identification, where "6-tuple" refers |
| 1801 |
to information carried in IP-layer and higher-layer protocol headers. |
| 1802 |
General background on the use of IP headers and 6-tuples to |
| 1803 |
identify flows and support QoS can be found in |
| 1804 |
<span>[<a href="#RFC3670" class="xref">RFC3670</a>]</span>. The extra field in the |
| 1805 |
6-tuple is the DSCP field in the packet. <span>[<a href="#RFC7657" class="xref">RFC7657</a>]</span> provides |
| 1806 |
useful background on differentiated services (Diffserv) |
| 1807 |
and tuple-based flow identification. DetNet flow aggregation may |
| 1808 |
be enabled via the use of wildcards, masks, prefixes, and ranges. The |
| 1809 |
operation of this method is described in detail in <span>[<a href="#RFC8939" class="xref">RFC8939</a>]</span>.<a href="#section-3.3-2" class="pilcrow">¶</a></p> |
| 1810 |
<p id="section-3.3-3"> |
| 1811 |
The DetNet forwarding plane may use explicit route capabilities and |
| 1812 |
traffic engineering capabilities to provide a forwarding sub‑layer |
| 1813 |
that is responsible for providing resource allocation and explicit |
| 1814 |
routes. It is possible to include such information in a native IP |
| 1815 |
packet either explicitly or implicitly.<a href="#section-3.3-3" class="pilcrow">¶</a></p> |
| 1816 |
</section> |
| 1817 |
</div> |
| 1818 |
<div id="sec_dt_mpls_dp"> |
| 1819 |
<section id="section-3.4"> |
| 1820 |
<h3 id="name-detnet-mpls-data-plane"> |
| 1821 |
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-detnet-mpls-data-plane" class="section-name selfRef">DetNet MPLS Data Plane</a> |
| 1822 |
</h3> |
| 1823 |
<p id="section-3.4-1"> |
| 1824 |
MPLS provides a forwarding sub‑layer for traffic over implicit |
| 1825 |
and explicit paths to the point in the network where the next |
| 1826 |
DetNet service sub‑layer action needs to take place. It does this |
| 1827 |
through the use of a stack of one or more labels with various |
| 1828 |
forwarding semantics.<a href="#section-3.4-1" class="pilcrow">¶</a></p> |
| 1829 |
<p id="section-3.4-2"> |
| 1830 |
MPLS also provides the ability to identify a service instance |
| 1831 |
that is used to process the packet through the use of a label that |
| 1832 |
maps the packet to a service instance.<a href="#section-3.4-2" class="pilcrow">¶</a></p> |
| 1833 |
<p id="section-3.4-3"> |
| 1834 |
In cases where metadata is needed to process an MPLS-encapsulated |
| 1835 |
packet at the service sub‑layer, the d-CW <span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span> can be used. Although such d-CWs |
| 1836 |
are frequently 32 bits long, there is no architectural constraint on |
| 1837 |
the size of this structure -- only the requirement that it be fully |
| 1838 |
understood by all parties operating on it in the DetNet service |
| 1839 |
sub‑layer. The operation of this method is described in detail in |
| 1840 |
<span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span>.<a href="#section-3.4-3" class="pilcrow">¶</a></p> |
| 1841 |
</section> |
| 1842 |
</div> |
| 1843 |
<div id="further_dn_dp_consid"> |
| 1844 |
<section id="section-3.5"> |
| 1845 |
<h3 id="name-further-detnet-data-plane-c"> |
| 1846 |
<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-further-detnet-data-plane-c" class="section-name selfRef">Further DetNet Data Plane Considerations</a> |
| 1847 |
</h3> |
| 1848 |
<p id="section-3.5-1"> |
| 1849 |
This section provides informative considerations related to |
| 1850 |
providing DetNet service to flows that are identified |
| 1851 |
based on their header information.<a href="#section-3.5-1" class="pilcrow">¶</a></p> |
| 1852 |
<div id="further_dn_dp_pf"> |
| 1853 |
<section id="section-3.5.1"> |
| 1854 |
<h4 id="name-functions-provided-on-a-per"> |
| 1855 |
<a href="#section-3.5.1" class="section-number selfRef">3.5.1. </a><a href="#name-functions-provided-on-a-per" class="section-name selfRef">Functions Provided on a Per-Flow Basis</a> |
| 1856 |
</h4> |
| 1857 |
<p id="section-3.5.1-1"> |
| 1858 |
At a high level, the following functions are provided on a per-flow basis.<a href="#section-3.5.1-1" class="pilcrow">¶</a></p> |
| 1859 |
<section id="section-3.5.1.1"> |
| 1860 |
<h5 id="name-reservation-and-allocation-"> |
| 1861 |
<a href="#section-3.5.1.1" class="section-number selfRef">3.5.1.1. </a><a href="#name-reservation-and-allocation-" class="section-name selfRef">Reservation and Allocation of Resources</a> |
| 1862 |
</h5> |
| 1863 |
<p id="section-3.5.1.1-1"> |
| 1864 |
Resources might be reserved in order to make them available for allocation to specific DetNet |
| 1865 |
flows. This can eliminate packet contention and packet loss for DetNet |
| 1866 |
traffic. This also can reduce jitter for DetNet traffic. Resources |
| 1867 |
allocated to a DetNet flow protect it from other traffic flows. On the |
| 1868 |
other hand, it is assumed that DetNet flows behave in accordance with the |
| 1869 |
reserved traffic profile. It must be possible to detect misbehaving DetNet flows |
| 1870 |
and to ensure that they do not compromise QoS of other flows. |
| 1871 |
Queuing, policing, and shaping policies can be used to ensure |
| 1872 |
that the allocation of resources reserved for DetNet is met.<a href="#section-3.5.1.1-1" class="pilcrow">¶</a></p> |
| 1873 |
</section> |
| 1874 |
<section id="section-3.5.1.2"> |
| 1875 |
<h5 id="name-explicit-routes"> |
| 1876 |
<a href="#section-3.5.1.2" class="section-number selfRef">3.5.1.2. </a><a href="#name-explicit-routes" class="section-name selfRef">Explicit Routes</a> |
| 1877 |
</h5> |
| 1878 |
<p id="section-3.5.1.2-1"> |
| 1879 |
A flow can be routed over a specific, precomputed path. This allows control of network |
| 1880 |
delay by steering the packet with the ability to influence the physical |
| 1881 |
path. Explicit routes complement reservation by ensuring that a |
| 1882 |
consistent path can be associated with its resources for the duration |
| 1883 |
of that path. Coupled with the traffic mechanism, this limits |
| 1884 |
misordering and bounds latency. Explicit route computation can |
| 1885 |
encompass a wide set of constraints and can optimize the path for a certain |
| 1886 |
characteristic, e.g., highest bandwidth or lowest jitter. In these cases, |
| 1887 |
the "best" path for any set of characteristics may not be a shortest |
| 1888 |
path. The selection of the path can take into account multiple network |
| 1889 |
metrics. Some of these metrics are measured and distributed by the |
| 1890 |
routing system as traffic engineering metrics.<a href="#section-3.5.1.2-1" class="pilcrow">¶</a></p> |
| 1891 |
</section> |
| 1892 |
<section id="section-3.5.1.3"> |
| 1893 |
<h5 id="name-service-protection"> |
| 1894 |
<a href="#section-3.5.1.3" class="section-number selfRef">3.5.1.3. </a><a href="#name-service-protection" class="section-name selfRef">Service Protection</a> |
| 1895 |
</h5> |
| 1896 |
<p id="section-3.5.1.3-1"> |
| 1897 |
Service protection involves the use of multiple packet streams using |
| 1898 |
multiple paths -- for example, 1+1 or |
| 1899 |
1:1 linear protection. For DetNet, this primarily relates to packet |
| 1900 |
replication and elimination capabilities. |
| 1901 |
MPLS offers a number of protection schemes. |
| 1902 |
MPLS hitless protection can be used to switch traffic to an already-established path |
| 1903 |
in order to restore delivery rapidly after a failure. |
| 1904 |
Path changes, even in the case of failure recovery, can lead to the out-of-order delivery of data requiring POFs either |
| 1905 |
within the DetNet service or at a high layer in the application |
| 1906 |
traffic. Establishment of new paths after a failure is out of scope |
| 1907 |
for DetNet services.<a href="#section-3.5.1.3-1" class="pilcrow">¶</a></p> |
| 1908 |
</section> |
| 1909 |
<section id="section-3.5.1.4"> |
| 1910 |
<h5 id="name-network-coding"> |
| 1911 |
<a href="#section-3.5.1.4" class="section-number selfRef">3.5.1.4. </a><a href="#name-network-coding" class="section-name selfRef">Network Coding</a> |
| 1912 |
</h5> |
| 1913 |
<p id="section-3.5.1.4-1"> |
| 1914 |
Network Coding <span>[<a href="#nwcrg" class="xref">nwcrg</a>]</span>, |
| 1915 |
not to be confused with network programming, |
| 1916 |
comprises |
| 1917 |
several techniques where multiple data flows are encoded. These |
| 1918 |
resulting flows can then be sent on different paths. The encoding |
| 1919 |
operation can combine flows and error recovery information. When the |
| 1920 |
encoded flows are decoded and recombined, the original flows can be |
| 1921 |
recovered. Note that Network Coding uses an alternative to |
| 1922 |
packet-by-packet PREOF. Therefore, for certain network topologies and traffic |
| 1923 |
loads, Network Coding can be used to improve a network's throughput, |
| 1924 |
efficiency, latency, and scalability, as well as resilience to |
| 1925 |
partition, attacks, and eavesdropping, as compared to traditional |
| 1926 |
methods. DetNet could use Network Coding as an alternative to |
| 1927 |
other means of protection. Network Coding is often applied in wireless |
| 1928 |
networks and is being explored for other network types.<a href="#section-3.5.1.4-1" class="pilcrow">¶</a></p> |
| 1929 |
</section> |
| 1930 |
<section id="section-3.5.1.5"> |
| 1931 |
<h5 id="name-load-sharing"> |
| 1932 |
<a href="#section-3.5.1.5" class="section-number selfRef">3.5.1.5. </a><a href="#name-load-sharing" class="section-name selfRef">Load-Sharing</a> |
| 1933 |
</h5> |
| 1934 |
<p id="section-3.5.1.5-1"> |
| 1935 |
The use of packet-by-packet load-sharing of the same DetNet flow over |
| 1936 |
multiple paths is not recommended, except for the cases listed above |
| 1937 |
where PREOF are utilized to improve protection of traffic and maintain order. |
| 1938 |
Packet-by-packet load-sharing, e.g., via Equal-Cost Multipath (ECMP) |
| 1939 |
or Unequal-Cost Multipath (UCMP), impacts ordering and, |
| 1940 |
possibly, jitter.<a href="#section-3.5.1.5-1" class="pilcrow">¶</a></p> |
| 1941 |
</section> |
| 1942 |
<section id="section-3.5.1.6"> |
| 1943 |
<h5 id="name-troubleshooting"> |
| 1944 |
<a href="#section-3.5.1.6" class="section-number selfRef">3.5.1.6. </a><a href="#name-troubleshooting" class="section-name selfRef">Troubleshooting</a> |
| 1945 |
</h5> |
| 1946 |
<p id="section-3.5.1.6-1"> |
| 1947 |
DetNet leverages many different forwarding sub‑layers, each of which |
| 1948 |
supports various tools to troubleshoot connectivity -- for example, |
| 1949 |
identification of misbehaving flows. The DetNet service layer can |
| 1950 |
leverage existing mechanisms to troubleshoot or monitor flows, such as |
| 1951 |
those in use by IP and MPLS networks. At the Application layer, a client |
| 1952 |
of a DetNet service can use existing techniques to detect and monitor |
| 1953 |
delay and loss.<a href="#section-3.5.1.6-1" class="pilcrow">¶</a></p> |
| 1954 |
</section> |
| 1955 |
<section id="section-3.5.1.7"> |
| 1956 |
<h5 id="name-flow-recognition-for-analyt"> |
| 1957 |
<a href="#section-3.5.1.7" class="section-number selfRef">3.5.1.7. </a><a href="#name-flow-recognition-for-analyt" class="section-name selfRef">Flow Recognition for Analytics</a> |
| 1958 |
</h5> |
| 1959 |
<p id="section-3.5.1.7-1"> |
| 1960 |
Network analytics can be inherited from the technologies of the service |
| 1961 |
and forwarding sub‑layers. At the DetNet service edge, packet and bit |
| 1962 |
counters (e.g., sent, received, dropped, out of sequence) can be |
| 1963 |
maintained.<a href="#section-3.5.1.7-1" class="pilcrow">¶</a></p> |
| 1964 |
</section> |
| 1965 |
<section id="section-3.5.1.8"> |
| 1966 |
<h5 id="name-correlation-of-events-with-"> |
| 1967 |
<a href="#section-3.5.1.8" class="section-number selfRef">3.5.1.8. </a><a href="#name-correlation-of-events-with-" class="section-name selfRef">Correlation of Events with Flows</a> |
| 1968 |
</h5> |
| 1969 |
<p id="section-3.5.1.8-1"> |
| 1970 |
The provider of a DetNet service may provide other capabilities to |
| 1971 |
monitor flows, such as more detailed loss statistics and timestamping |
| 1972 |
of events. Details regarding these capabilities are out of scope |
| 1973 |
for this document.<a href="#section-3.5.1.8-1" class="pilcrow">¶</a></p> |
| 1974 |
</section> |
| 1975 |
</section> |
| 1976 |
</div> |
| 1977 |
<section id="section-3.5.2"> |
| 1978 |
<h4 id="name-service-protection-2"> |
| 1979 |
<a href="#section-3.5.2" class="section-number selfRef">3.5.2. </a><a href="#name-service-protection-2" class="section-name selfRef">Service Protection</a> |
| 1980 |
</h4> |
| 1981 |
<p id="section-3.5.2-1"> |
| 1982 |
Service protection allows DetNet services to increase reliability and |
| 1983 |
maintain a desired level of service assurance in the case of network |
| 1984 |
congestion or network failure. DetNet relies on the underlying technology capabilities |
| 1985 |
for various protection schemes. Protection schemes enable partial or |
| 1986 |
complete coverage of the network paths and active protection with |
| 1987 |
combinations of the PRF, PEF, and POF.<a href="#section-3.5.2-1" class="pilcrow">¶</a></p> |
| 1988 |
<section id="section-3.5.2.1"> |
| 1989 |
<h5 id="name-linear-service-protection"> |
| 1990 |
<a href="#section-3.5.2.1" class="section-number selfRef">3.5.2.1. </a><a href="#name-linear-service-protection" class="section-name selfRef">Linear Service Protection</a> |
| 1991 |
</h5> |
| 1992 |
<p id="section-3.5.2.1-1"> |
| 1993 |
An example DetNet MPLS network fragment and its packet flow are illustrated in |
| 1994 |
<a href="#dn_protection_flow" class="xref">Figure 3</a>.<a href="#section-3.5.2.1-1" class="pilcrow">¶</a></p> |
| 1995 |
<span id="name-example-of-packet-flow-prot"></span><div id="dn_protection_flow"> |
| 1996 |
<figure id="figure-3"> |
| 1997 |
<div class="artwork art-text alignCenter" id="section-3.5.2.1-2.1"> |
| 1998 |
<pre> |
| 1999 |
1 1.1 1.1 1.2.1 1.2.1 1.2.2 |
| 2000 |
CE1----EN1--------R1-------R2-------R3--------EN2-----CE2 |
| 2001 |
\ 1.2.1 / / |
| 2002 |
\1.2 /------+ / |
| 2003 |
+------R4------------------------+ |
| 2004 |
1.2.2</pre> |
| 2005 |
</div> |
| 2006 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 2007 |
<a href="#name-example-of-packet-flow-prot" class="selfRef">Example of Packet Flow Protected by DetNet</a> |
| 2008 |
</figcaption></figure> |
| 2009 |
</div> |
| 2010 |
<p id="section-3.5.2.1-3"> |
| 2011 |
In <a href="#dn_protection_flow" class="xref">Figure 3</a>, the numbers are used to identify the |
| 2012 |
instance of a packet. Packet 1 is the original packet. Packets 1.1 and |
| 2013 |
1.2 are two first-generation copies of packet 1, packet 1.2.1 is a |
| 2014 |
second-generation copy of packet 1.2, and so on. Note that these numbers never appear in |
| 2015 |
the packet and are not to be confused with sequence numbers, labels, or any |
| 2016 |
other identifiers that appear in the packet. They simply indicate the |
| 2017 |
generation number of the original packet so that its passage through the |
| 2018 |
network fragment can be identified for the reader.<a href="#section-3.5.2.1-3" class="pilcrow">¶</a></p> |
| 2019 |
<p id="section-3.5.2.1-4"> |
| 2020 |
Customer Equipment device CE1 sends a packet into the DetNet-enabled network. This |
| 2021 |
is packet 1. Edge Node EN1 encapsulates the packet as a DetNet packet and |
| 2022 |
sends it to Relay Node R1 (packet 1.1). EN1 makes a copy of the packet |
| 2023 |
(1.2), encapsulates it, and sends this copy to Relay Node R4.<a href="#section-3.5.2.1-4" class="pilcrow">¶</a></p> |
| 2024 |
<p id="section-3.5.2.1-5"> |
| 2025 |
Note that R1 may be directly attached to EN1, or there may be one or more |
| 2026 |
nodes on the path that, for clarity, are not shown in <a href="#dn_protection_flow" class="xref">Figure 3</a>. The same |
| 2027 |
holds true for any other path between two DetNet entities as shown in |
| 2028 |
the figure.<a href="#section-3.5.2.1-5" class="pilcrow">¶</a></p> |
| 2029 |
<p id="section-3.5.2.1-6"> |
| 2030 |
Relay Node R4 has been configured to send one copy of the packet to Relay |
| 2031 |
Node R2 (packet 1.2.1) and one copy to Edge Node EN2 (packet 1.2.2).<a href="#section-3.5.2.1-6" class="pilcrow">¶</a></p> |
| 2032 |
<p id="section-3.5.2.1-7"> |
| 2033 |
R2 receives packet copy 1.2.1 before packet copy 1.1 arrives and, having |
| 2034 |
been configured to perform packet elimination on this DetNet flow, forwards |
| 2035 |
packet 1.2.1 to Relay Node R3. Packet copy 1.1 is of no further use and so |
| 2036 |
is discarded by R2.<a href="#section-3.5.2.1-7" class="pilcrow">¶</a></p> |
| 2037 |
<p id="section-3.5.2.1-8"> |
| 2038 |
Edge Node EN2 receives packet copy 1.2.2 from R4 before it receives packet |
| 2039 |
copy 1.2.1 from R2 via Relay Node R3. EN2 therefore strips any DetNet |
| 2040 |
encapsulation from packet copy 1.2.2 and forwards the packet to CE2. When |
| 2041 |
EN2 receives packet copy 1.2.1 later on, the copy is discarded.<a href="#section-3.5.2.1-8" class="pilcrow">¶</a></p> |
| 2042 |
<p id="section-3.5.2.1-9"> |
| 2043 |
The above is of course illustrative of many network scenarios that can be |
| 2044 |
configured.<a href="#section-3.5.2.1-9" class="pilcrow">¶</a></p> |
| 2045 |
<p id="section-3.5.2.1-10"> |
| 2046 |
This example also illustrates a 1:1 protection scheme, meaning there is |
| 2047 |
traffic over each segment of the end-to-end path. Local DetNet |
| 2048 |
relay nodes determine which packets are eliminated and which packets are |
| 2049 |
forwarded. A 1+1 scheme where only one path is used for traffic at a |
| 2050 |
time could use the same topology. In this case, there is no PRF, |
| 2051 |
and traffic is switched upon detection of failure. An OAM scheme that |
| 2052 |
monitors the paths to detect the loss of a path or traffic is required to |
| 2053 |
initiate the switch. A POF may still be used in this case to |
| 2054 |
prevent misordering of packets. In both cases, the protection paths are |
| 2055 |
established and maintained for the duration of the DetNet service.<a href="#section-3.5.2.1-10" class="pilcrow">¶</a></p> |
| 2056 |
</section> |
| 2057 |
<section id="section-3.5.2.2"> |
| 2058 |
<h5 id="name-path-differential-delay"> |
| 2059 |
<a href="#section-3.5.2.2" class="section-number selfRef">3.5.2.2. </a><a href="#name-path-differential-delay" class="section-name selfRef">Path Differential Delay</a> |
| 2060 |
</h5> |
| 2061 |
<p id="section-3.5.2.2-1"> |
| 2062 |
In the preceding example, proper operation of duplicate |
| 2063 |
elimination and the reordering of packets are dependent |
| 2064 |
on the number of out-of-order packets that can be |
| 2065 |
buffered and the difference in delay of the arriving packets. |
| 2066 |
DetNet uses flow-specific requirements (e.g., maximum |
| 2067 |
number of out-of-order packets, maximum latency |
| 2068 |
of the flow) for configuration of POF-related buffers. |
| 2069 |
If the differential delay between paths is excessively large |
| 2070 |
or there is excessive misordering of the packets, then packets may |
| 2071 |
be dropped instead of being reordered. |
| 2072 |
Likewise, the PEF |
| 2073 |
uses the sequence number to identify duplicate packets, and large |
| 2074 |
differential delays combined with high numbers of packets may exceed |
| 2075 |
the PEF's ability to work properly.<a href="#section-3.5.2.2-1" class="pilcrow">¶</a></p> |
| 2076 |
</section> |
| 2077 |
<section id="section-3.5.2.3"> |
| 2078 |
<h5 id="name-ring-service-protection"> |
| 2079 |
<a href="#section-3.5.2.3" class="section-number selfRef">3.5.2.3. </a><a href="#name-ring-service-protection" class="section-name selfRef">Ring Service Protection</a> |
| 2080 |
</h5> |
| 2081 |
<p id="section-3.5.2.3-1"> |
| 2082 |
Ring protection may also be supported if the underlying technology |
| 2083 |
supports it. Many of the same concepts apply; however, rings are normally |
| 2084 |
1+1 protection for data efficiency reasons. <span>[<a href="#RFC8227" class="xref">RFC8227</a>]</span> provides an example of an MPLS Transport Profile (MPLS-TP) data plane that supports ring protection.<a href="#section-3.5.2.3-1" class="pilcrow">¶</a></p> |
| 2085 |
</section> |
| 2086 |
</section> |
| 2087 |
<div id="aggregation"> |
| 2088 |
<section id="section-3.5.3"> |
| 2089 |
<h4 id="name-aggregation-considerations"> |
| 2090 |
<a href="#section-3.5.3" class="section-number selfRef">3.5.3. </a><a href="#name-aggregation-considerations" class="section-name selfRef">Aggregation Considerations</a> |
| 2091 |
</h4> |
| 2092 |
<p id="section-3.5.3-1"> |
| 2093 |
The DetNet data plane also allows for the aggregation of DetNet flows, which |
| 2094 |
can improve scalability by reducing the per-hop state. How this is accomplished is data |
| 2095 |
plane or control plane dependent. When DetNet flows are aggregated, transit |
| 2096 |
nodes provide service to the aggregate and not on a per-DetNet-flow basis. |
| 2097 |
When aggregating DetNet flows, the flows should be compatible, i.e., the same or |
| 2098 |
very similar QoS and CoS characteristics. In this case, nodes performing |
| 2099 |
aggregation will ensure that per-flow service requirements are achieved.<a href="#section-3.5.3-1" class="pilcrow">¶</a></p> |
| 2100 |
<p id="section-3.5.3-2"> |
| 2101 |
If bandwidth reservations are used, the reservation should be the |
| 2102 |
sum of all the individual reservations; in other words, the reservations |
| 2103 |
should not add up to an oversubscription of bandwidth reservation. If |
| 2104 |
maximum delay bounds are used, the system should ensure that the aggregate |
| 2105 |
does not exceed the delay bounds of the individual flows.<a href="#section-3.5.3-2" class="pilcrow">¶</a></p> |
| 2106 |
<p id="section-3.5.3-3"> |
| 2107 |
When |
| 2108 |
an encapsulation is used, the choice of reserving a maximum resource level and |
| 2109 |
then tracking the services in the aggregated service or adjusting the |
| 2110 |
aggregated resources as the services are added is implementation and |
| 2111 |
technology specific.<a href="#section-3.5.3-3" class="pilcrow">¶</a></p> |
| 2112 |
<p id="section-3.5.3-4"> |
| 2113 |
DetNet flows at edges must be able to handle rejection to an aggregation |
| 2114 |
group due to lack of resources as well as conditions where |
| 2115 |
requirements are not satisfied.<a href="#section-3.5.3-4" class="pilcrow">¶</a></p> |
| 2116 |
<div id="ip-agg"> |
| 2117 |
<section id="section-3.5.3.1"> |
| 2118 |
<h5 id="name-ip-aggregation"> |
| 2119 |
<a href="#section-3.5.3.1" class="section-number selfRef">3.5.3.1. </a><a href="#name-ip-aggregation" class="section-name selfRef">IP Aggregation</a> |
| 2120 |
</h5> |
| 2121 |
<p id="section-3.5.3.1-1"> |
| 2122 |
IP aggregation has both data plane and Controller Plane aspects. For the |
| 2123 |
data plane, flows may be aggregated for treatment based on shared |
| 2124 |
characteristics such as 6-tuple <span>[<a href="#RFC8939" class="xref">RFC8939</a>]</span>. |
| 2125 |
Alternatively, an IP encapsulation may be |
| 2126 |
used to tunnel an aggregate number of DetNet flows between relay nodes.<a href="#section-3.5.3.1-1" class="pilcrow">¶</a></p> |
| 2127 |
</section> |
| 2128 |
</div> |
| 2129 |
<div id="mpls-agg"> |
| 2130 |
<section id="section-3.5.3.2"> |
| 2131 |
<h5 id="name-mpls-aggregation"> |
| 2132 |
<a href="#section-3.5.3.2" class="section-number selfRef">3.5.3.2. </a><a href="#name-mpls-aggregation" class="section-name selfRef">MPLS Aggregation</a> |
| 2133 |
</h5> |
| 2134 |
<p id="section-3.5.3.2-1"> |
| 2135 |
MPLS aggregation also has data plane and Controller Plane aspects. MPLS |
| 2136 |
flows are often tunneled in a forwarding sub‑layer, under the reservation |
| 2137 |
associated with that MPLS tunnel.<a href="#section-3.5.3.2-1" class="pilcrow">¶</a></p> |
| 2138 |
</section> |
| 2139 |
</div> |
| 2140 |
</section> |
| 2141 |
</div> |
| 2142 |
<section id="section-3.5.4"> |
| 2143 |
<h4 id="name-end-system-specific-conside"> |
| 2144 |
<a href="#section-3.5.4" class="section-number selfRef">3.5.4. </a><a href="#name-end-system-specific-conside" class="section-name selfRef">End-System-Specific Considerations</a> |
| 2145 |
</h4> |
| 2146 |
<p id="section-3.5.4-1"> |
| 2147 |
Data flows requiring DetNet service are generated and terminated on |
| 2148 |
end systems. Encapsulation depends on the application and its |
| 2149 |
preferences. For example, in a DetNet MPLS domain, the sub‑layer functions use the d-CWs, |
| 2150 |
S-Labels, and F-Labels <span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span> to provide DetNet services. However, an |
| 2151 |
application may exchange further flow-related parameters (e.g., |
| 2152 |
timestamps) that are not provided by DetNet functions.<a href="#section-3.5.4-1" class="pilcrow">¶</a></p> |
| 2153 |
<p id="section-3.5.4-2"> |
| 2154 |
As a general rule, DetNet domains are capable of forwarding any |
| 2155 |
DetNet flows, and the DetNet domain does not mandate the |
| 2156 |
encapsulation format for end systems or edge nodes. Unless |
| 2157 |
some form of proxy is present, end systems peer with similar end systems |
| 2158 |
using the same application encapsulation format. For example, as |
| 2159 |
shown in <a href="#fig_es_connect" class="xref">Figure 4</a>, IP applications peer with |
| 2160 |
IP applications, and Ethernet applications peer with Ethernet |
| 2161 |
applications.<a href="#section-3.5.4-2" class="pilcrow">¶</a></p> |
| 2162 |
<span id="name-end-systems-and-the-detnet-"></span><div id="fig_es_connect"> |
| 2163 |
<figure id="figure-4"> |
| 2164 |
<div class="artwork art-text alignCenter" id="section-3.5.4-3.1"> |
| 2165 |
<pre> |
| 2166 |
+-----+ |
| 2167 |
| X | +-----+ |
| 2168 |
+-----+ | X | |
| 2169 |
| Eth | ________ +-----+ |
| 2170 |
+-----+ _____ / \ | Eth | |
| 2171 |
\ / \__/ \___ +-----+ |
| 2172 |
\ / \ / |
| 2173 |
0======== tunnel-1 ========0_ |
| 2174 |
| \ |
| 2175 |
\ | |
| 2176 |
0========= tunnel-2 =========0 |
| 2177 |
/ \ __/ \ |
| 2178 |
+-----+ \__ DetNet MPLS domain / \ |
| 2179 |
| X | \ __ / +-----+ |
| 2180 |
+-----+ \_______/ \_____/ | X | |
| 2181 |
| IP | +-----+ |
| 2182 |
+-----+ | IP | |
| 2183 |
+-----+</pre> |
| 2184 |
</div> |
| 2185 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 2186 |
<a href="#name-end-systems-and-the-detnet-" class="selfRef">End Systems and the DetNet MPLS Domain</a> |
| 2187 |
</figcaption></figure> |
| 2188 |
</div> |
| 2189 |
</section> |
| 2190 |
<div id="subnet_considerations"> |
| 2191 |
<section id="section-3.5.5"> |
| 2192 |
<h4 id="name-sub-network-considerations"> |
| 2193 |
<a href="#section-3.5.5" class="section-number selfRef">3.5.5. </a><a href="#name-sub-network-considerations" class="section-name selfRef">Sub-network Considerations</a> |
| 2194 |
</h4> |
| 2195 |
<p id="section-3.5.5-1"> |
| 2196 |
Any of the DetNet service types may be transported by another |
| 2197 |
DetNet service. MPLS nodes may be interconnected by different sub-network |
| 2198 |
technologies, which may include point-to-point links. Each of these |
| 2199 |
sub-network technologies needs to provide appropriate service to DetNet |
| 2200 |
flows. In some cases, e.g., on dedicated point-to-point links or TDM |
| 2201 |
technologies, all that is required is for a DetNet node to appropriately |
| 2202 |
queue its output traffic. In other cases, DetNet nodes will need to map |
| 2203 |
DetNet flows to the flow semantics (i.e., identifiers) and mechanisms used |
| 2204 |
by an underlying sub-network technology. <a href="#fig_dn_mpls_sn_ex" class="xref">Figure 5</a> shows several examples of |
| 2205 |
sub-network encapsulations that can be used to carry DetNet MPLS flows over different |
| 2206 |
sub-network technologies. L2 represents a generic Layer 2 encapsulation |
| 2207 |
that might be used on a point-to-point link. TSN represents the |
| 2208 |
encapsulation used on an IEEE 802.1 TSN network, as described in <span>[<a href="#DetNet-MPLS-over-TSN" class="xref">DetNet-MPLS-over-TSN</a>]</span>. UDP/IP represents the encapsulation |
| 2209 |
used on a DetNet IP PSN, as described in <span>[<a href="#DetNet-MPLS-over-UDP-IP" class="xref">DetNet-MPLS-over-UDP-IP</a>]</span>.<a href="#section-3.5.5-1" class="pilcrow">¶</a></p> |
| 2210 |
<span id="name-example-detnet-mpls-encapsu"></span><div id="fig_dn_mpls_sn_ex"> |
| 2211 |
<figure id="figure-5"> |
| 2212 |
<div class="artwork art-text alignCenter" id="section-3.5.5-2.1"> |
| 2213 |
<pre> |
| 2214 |
+------+ +------+ +------+ |
| 2215 |
App-flow | X | | X | | X | |
| 2216 |
+-----+======+--+======+--+======+-----+ |
| 2217 |
DetNet-MPLS | d-CW | | d-CW | | d-CW | |
| 2218 |
+------+ +------+ +------+ |
| 2219 |
|Labels| |Labels| |Labels| |
| 2220 |
+-----+======+--+======+--+======+-----+ |
| 2221 |
Sub-network | L2 | | TSN | | UDP | |
| 2222 |
+------+ +------+ +------+ |
| 2223 |
| IP | |
| 2224 |
+------+ |
| 2225 |
| L2 | |
| 2226 |
+------+</pre> |
| 2227 |
</div> |
| 2228 |
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>: |
| 2229 |
<a href="#name-example-detnet-mpls-encapsu" class="selfRef">Example DetNet MPLS Encapsulations in Sub-networks</a> |
| 2230 |
</figcaption></figure> |
| 2231 |
</div> |
| 2232 |
</section> |
| 2233 |
</div> |
| 2234 |
</section> |
| 2235 |
</div> |
| 2236 |
</section> |
| 2237 |
</div> |
| 2238 |
<div id="cp_considerations"> |
| 2239 |
<section id="section-4"> |
| 2240 |
<h2 id="name-controller-plane-management"> |
| 2241 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-controller-plane-management" class="section-name selfRef">Controller Plane (Management and Control) Considerations</a> |
| 2242 |
</h2> |
| 2243 |
<div id="control-management-requirements"> |
| 2244 |
<section id="section-4.1"> |
| 2245 |
<h3 id="name-detnet-controller-plane-req"> |
| 2246 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-detnet-controller-plane-req" class="section-name selfRef">DetNet Controller Plane Requirements</a> |
| 2247 |
</h3> |
| 2248 |
<p id="section-4.1-1"> |
| 2249 |
The Controller Plane corresponds to the aggregation of the Control and |
| 2250 |
Management Planes discussed in <span>[<a href="#RFC7426" class="xref">RFC7426</a>]</span> and |
| 2251 |
<span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>. While more details regarding any DetNet Controller |
| 2252 |
Plane are out of scope for this document, there are particular |
| 2253 |
considerations and requirements for the Controller Plane that result from the unique |
| 2254 |
characteristics of the DetNet architecture and |
| 2255 |
data plane as defined herein.<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 2256 |
<p id="section-4.1-2"> |
| 2257 |
The primary requirements of the DetNet Controller Plane are |
| 2258 |
that it must be able to:<a href="#section-4.1-2" class="pilcrow">¶</a></p> |
| 2259 |
<ul class="normal"> |
| 2260 |
<li class="normal" id="section-4.1-3.1"> |
| 2261 |
Instantiate DetNet flows in a DetNet domain (which may, for example, |
| 2262 |
include some or all of the following: explicit path determination, link |
| 2263 |
bandwidth reservations, restricting flows to IEEE 802.1 TSN |
| 2264 |
links, node buffer and other resource reservations, |
| 2265 |
specification of required queuing disciplines along the |
| 2266 |
path, ability to manage bidirectional flows, etc.) as needed |
| 2267 |
for a flow.<a href="#section-4.1-3.1" class="pilcrow">¶</a> |
| 2268 |
</li> |
| 2269 |
<li class="normal" id="section-4.1-3.2"> |
| 2270 |
In the case of MPLS, manage DetNet S-Label and F-Label allocation |
| 2271 |
and distribution. In cases where the DetNet MPLS encapsulation is |
| 2272 |
being used, see <span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span>.<a href="#section-4.1-3.2" class="pilcrow">¶</a> |
| 2273 |
</li> |
| 2274 |
<li class="normal" id="section-4.1-3.3"> |
| 2275 |
Support DetNet flow aggregation.<a href="#section-4.1-3.3" class="pilcrow">¶</a> |
| 2276 |
</li> |
| 2277 |
<li class="normal" id="section-4.1-3.4"> |
| 2278 |
Advertise static and dynamic node and link resources such |
| 2279 |
as capabilities and adjacencies to other network nodes (for |
| 2280 |
dynamic signaling approaches) or to network controllers (for |
| 2281 |
centralized approaches).<a href="#section-4.1-3.4" class="pilcrow">¶</a> |
| 2282 |
</li> |
| 2283 |
<li class="normal" id="section-4.1-3.5"> |
| 2284 |
Scale to handle the number of DetNet flows expected in a |
| 2285 |
domain (which may require per-flow signaling or |
| 2286 |
provisioning).<a href="#section-4.1-3.5" class="pilcrow">¶</a> |
| 2287 |
</li> |
| 2288 |
<li class="normal" id="section-4.1-3.6"> |
| 2289 |
Provision flow identification information at each of the nodes |
| 2290 |
along the path. Flow identification may differ, depending on the |
| 2291 |
location in the network and the DetNet functionality (e.g., transit |
| 2292 |
node vs. relay node).<a href="#section-4.1-3.6" class="pilcrow">¶</a> |
| 2293 |
</li> |
| 2294 |
</ul> |
| 2295 |
<p id="section-4.1-4"> |
| 2296 |
These requirements, as stated earlier, could be satisfied using |
| 2297 |
distributed control protocol signaling (such as RSVP-TE), |
| 2298 |
centralized network management provisioning mechanisms (BGP, PCEP, YANG, <span>[<a href="#I-D.ietf-detnet-flow-information-model" class="xref">DetNet-Flow-Info</a>]</span>, etc.), or hybrid |
| 2299 |
combinations of the two, and could also make use of MPLS-based |
| 2300 |
segment routing.<a href="#section-4.1-4" class="pilcrow">¶</a></p> |
| 2301 |
<p id="section-4.1-5"> |
| 2302 |
In the abstract, the results of either distributed signaling |
| 2303 |
or centralized provisioning are equivalent from a DetNet data plane |
| 2304 |
perspective -- flows are instantiated, explicit routes |
| 2305 |
are determined, resources are reserved, and packets are |
| 2306 |
forwarded through the domain using the DetNet data plane.<a href="#section-4.1-5" class="pilcrow">¶</a></p> |
| 2307 |
<p id="section-4.1-6"> |
| 2308 |
However, from a practical and implementation standpoint, Controller Plane alternatives are not |
| 2309 |
equivalent at all. Some approaches are more scalable than others in |
| 2310 |
terms of signaling load on the network. Some alternatives can take advantage of |
| 2311 |
global tracking of resources in the DetNet domain for better overall |
| 2312 |
network resource optimization. Some solutions are more resilient than others if |
| 2313 |
link, node, or management equipment failures occur. While a detailed |
| 2314 |
analysis of the control plane alternatives is out of scope for this |
| 2315 |
document, the requirements from this document can be used as the basis |
| 2316 |
of a future analysis of the alternatives.<a href="#section-4.1-6" class="pilcrow">¶</a></p> |
| 2317 |
</section> |
| 2318 |
</div> |
| 2319 |
<div id="gen_cp_considerations"> |
| 2320 |
<section id="section-4.2"> |
| 2321 |
<h3 id="name-generic-controller-plane-co"> |
| 2322 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-generic-controller-plane-co" class="section-name selfRef">Generic Controller Plane Considerations</a> |
| 2323 |
</h3> |
| 2324 |
<p id="section-4.2-1"> |
| 2325 |
This section covers control plane considerations that are |
| 2326 |
independent of the data plane technology used for DetNet service |
| 2327 |
delivery.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 2328 |
<p id="section-4.2-2"> |
| 2329 |
While the management plane and the control plane are traditionally |
| 2330 |
considered separately, from a data plane perspective, there is no |
| 2331 |
practical difference based on the origin of flow-provisioning |
| 2332 |
information, and the DetNet architecture <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span> refers to these collectively |
| 2333 |
as the "Controller Plane". This document therefore does not |
| 2334 |
distinguish between information provided by distributed control plane protocols (e.g., RSVP-TE <span>[<a href="#RFC3209" class="xref">RFC3209</a>]</span> <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>) or centralized network management mechanisms |
| 2335 |
(e.g., RESTCONF <span>[<a href="#RFC8040" class="xref">RFC8040</a>]</span>, YANG <span>[<a href="#RFC7950" class="xref">RFC7950</a>]</span>, PCEP <span>[<a href="#I-D.ietf-pce-pcep-extension-for-pce-controller" class="xref">PCECC</a>]</span>), or any |
| 2336 |
combination thereof. Specific considerations and requirements for |
| 2337 |
the DetNet Controller Plane are discussed in <a href="#control-management-requirements" class="xref">Section 4.1</a>.<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 2338 |
<p id="section-4.2-3"> |
| 2339 |
Each respective data plane document also covers the control plane considerations |
| 2340 |
for that technology. For example, <span>[<a href="#RFC8939" class="xref">RFC8939</a>]</span> also covers IP |
| 2341 |
control plane normative considerations, and <span>[<a href="#DetNet-MPLS" class="xref">DetNet-MPLS</a>]</span> also covers MPLS control plane |
| 2342 |
normative considerations.<a href="#section-4.2-3" class="pilcrow">¶</a></p> |
| 2343 |
<section id="section-4.2.1"> |
| 2344 |
<h4 id="name-flow-aggregation-control"> |
| 2345 |
<a href="#section-4.2.1" class="section-number selfRef">4.2.1. </a><a href="#name-flow-aggregation-control" class="section-name selfRef">Flow Aggregation Control</a> |
| 2346 |
</h4> |
| 2347 |
<p id="section-4.2.1-1"> |
| 2348 |
Flow aggregation means that multiple App-flows are served by a single new DetNet |
| 2349 |
flow. There are many techniques to achieve aggregation. For example, |
| 2350 |
in the case of IP, IP flows that share 6-tuple attributes or flow |
| 2351 |
identifiers at the DetNet sub‑layer can be grouped. |
| 2352 |
Another example includes aggregation accomplished through the use of |
| 2353 |
hierarchical LSPs in MPLS and tunnels.<a href="#section-4.2.1-1" class="pilcrow">¶</a></p> |
| 2354 |
<p id="section-4.2.1-2"> |
| 2355 |
Control of aggregation involves a set of procedures listed here. |
| 2356 |
Aggregation may use some or all of these capabilities, and the order may vary:<a href="#section-4.2.1-2" class="pilcrow">¶</a></p> |
| 2357 |
<span class="break"></span><dl class="dlNewline" id="section-4.2.1-3"> |
| 2358 |
<dt id="section-4.2.1-3.1">Traffic engineering resource collection and distribution:</dt> |
| 2359 |
<dd style="margin-left: 1.5em" id="section-4.2.1-3.2">Available resources are tracked through control plane or |
| 2360 |
management plane databases and distributed amongst controllers |
| 2361 |
or nodes that can manage resources.<a href="#section-4.2.1-3.2" class="pilcrow">¶</a> |
| 2362 |
</dd> |
| 2363 |
<dd class="break"></dd> |
| 2364 |
<dt id="section-4.2.1-3.3">Path computation and resource allocation:</dt> |
| 2365 |
<dd style="margin-left: 1.5em" id="section-4.2.1-3.4">When DetNet services are provisioned or requested, one or more |
| 2366 |
paths meeting the requirements are selected and the resources |
| 2367 |
verified and recorded.<a href="#section-4.2.1-3.4" class="pilcrow">¶</a> |
| 2368 |
</dd> |
| 2369 |
<dd class="break"></dd> |
| 2370 |
<dt id="section-4.2.1-3.5">Resource assignment and data plane coordination:</dt> |
| 2371 |
<dd style="margin-left: 1.5em" id="section-4.2.1-3.6">The assignment of resources along the path depends on the technology and |
| 2372 |
includes assignment of specific links, coordination of |
| 2373 |
queuing, and other traffic management capabilities such as policing and shaping.<a href="#section-4.2.1-3.6" class="pilcrow">¶</a> |
| 2374 |
</dd> |
| 2375 |
<dd class="break"></dd> |
| 2376 |
<dt id="section-4.2.1-3.7">Assigned resource recording and updating:</dt> |
| 2377 |
<dd style="margin-left: 1.5em" id="section-4.2.1-3.8">Depending on the specific technology, the assigned resources are |
| 2378 |
updated and distributed in the databases, preventing oversubscription.<a href="#section-4.2.1-3.8" class="pilcrow">¶</a> |
| 2379 |
</dd> |
| 2380 |
<dd class="break"></dd> |
| 2381 |
</dl> |
| 2382 |
</section> |
| 2383 |
<section id="section-4.2.2"> |
| 2384 |
<h4 id="name-explicit-routes-2"> |
| 2385 |
<a href="#section-4.2.2" class="section-number selfRef">4.2.2. </a><a href="#name-explicit-routes-2" class="section-name selfRef">Explicit Routes</a> |
| 2386 |
</h4> |
| 2387 |
<p id="section-4.2.2-1"> |
| 2388 |
Explicit routes are used to ensure that packets are routed through the |
| 2389 |
resources that have been reserved for them and hence provide the |
| 2390 |
DetNet application with the required service. A requirement for the |
| 2391 |
DetNet Controller Plane will be the ability to assign a particular |
| 2392 |
identified DetNet IP flow to a path through the DetNet domain that has |
| 2393 |
been assigned the required per-node resources. This provides the |
| 2394 |
appropriate traffic treatment for the flow and also includes particular |
| 2395 |
links as a part of the path that are able to support the DetNet flow. |
| 2396 |
For example, by using IEEE 802.1 TSN links (as discussed in |
| 2397 |
<span>[<a href="#DetNet-MPLS-over-TSN" class="xref">DetNet-MPLS-over-TSN</a>]</span>), DetNet parameters can be maintained. |
| 2398 |
Further considerations and requirements for the DetNet Controller Plane |
| 2399 |
are discussed in <a href="#control-management-requirements" class="xref">Section 4.1</a>.<a href="#section-4.2.2-1" class="pilcrow">¶</a></p> |
| 2400 |
<p id="section-4.2.2-2"> |
| 2401 |
Whether configuring, calculating, and instantiating these |
| 2402 |
routes is a single-stage or multi-stage process, or is performed in a |
| 2403 |
centralized or distributed manner, is out of scope for this |
| 2404 |
document.<a href="#section-4.2.2-2" class="pilcrow">¶</a></p> |
| 2405 |
<p id="section-4.2.2-3"> |
| 2406 |
There are several approaches that could be used to provide |
| 2407 |
explicit routes and resource allocation in the DetNet |
| 2408 |
forwarding sub‑layer. For example:<a href="#section-4.2.2-3" class="pilcrow">¶</a></p> |
| 2409 |
<ul class="normal"> |
| 2410 |
<li class="normal" id="section-4.2.2-4.1"> |
| 2411 |
The path could be explicitly set up by a controller that |
| 2412 |
calculates the path and explicitly configures each node along that |
| 2413 |
path with the appropriate forwarding and resource allocation |
| 2414 |
information.<a href="#section-4.2.2-4.1" class="pilcrow">¶</a> |
| 2415 |
</li> |
| 2416 |
<li class="normal" id="section-4.2.2-4.2"> |
| 2417 |
The path could use a distributed control plane such as |
| 2418 |
<span><a href="#RFC2205" class="xref">RSVP</a> [<a href="#RFC2205" class="xref">RFC2205</a>]</span> or RSVP-TE <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span> extended to support DetNet IP flows.<a href="#section-4.2.2-4.2" class="pilcrow">¶</a> |
| 2419 |
</li> |
| 2420 |
<li class="normal" id="section-4.2.2-4.3"> |
| 2421 |
The path could be implemented using IPv6-based segment |
| 2422 |
routing when extended to support resource allocation.<a href="#section-4.2.2-4.3" class="pilcrow">¶</a> |
| 2423 |
</li> |
| 2424 |
</ul> |
| 2425 |
<p id="section-4.2.2-5"> |
| 2426 |
See <a href="#control-management-requirements" class="xref">Section 4.1</a> for |
| 2427 |
further discussion of these alternatives. In addition, |
| 2428 |
<span>[<a href="#RFC2386" class="xref">RFC2386</a>]</span> contains useful background information |
| 2429 |
on QoS-based routing, and <span>[<a href="#RFC5575" class="xref">RFC5575</a>]</span> |
| 2430 |
(which will be |
| 2431 |
updated by <span>[<a href="#I-D.ietf-idr-rfc5575bis" class="xref">Flow-Spec-Rules</a>]</span>) discusses |
| 2432 |
a specific mechanism used by BGP for traffic flow specification |
| 2433 |
and policy-based routing.<a href="#section-4.2.2-5" class="pilcrow">¶</a></p> |
| 2434 |
</section> |
| 2435 |
<section id="section-4.2.3"> |
| 2436 |
<h4 id="name-contention-loss-and-jitter-"> |
| 2437 |
<a href="#section-4.2.3" class="section-number selfRef">4.2.3. </a><a href="#name-contention-loss-and-jitter-" class="section-name selfRef">Contention Loss and Jitter Reduction</a> |
| 2438 |
</h4> |
| 2439 |
<p id="section-4.2.3-1"> |
| 2440 |
This document does |
| 2441 |
not specify the mechanisms needed to eliminate packet contention or packet loss |
| 2442 |
or to reduce jitter for DetNet flows at the DetNet forwarding |
| 2443 |
sub‑layer. The ability to manage node and link resources to |
| 2444 |
be able to provide these functions is a necessary part of |
| 2445 |
the DetNet Controller Plane. It is also necessary to be |
| 2446 |
able to control the required queuing mechanisms used to |
| 2447 |
provide these functions along a flow's path through the |
| 2448 |
network. See <span>[<a href="#RFC8939" class="xref">RFC8939</a>]</span> and <a href="#control-management-requirements" class="xref">Section 4.1</a> for further |
| 2449 |
discussion of these requirements. Some forms of protection |
| 2450 |
may minimize packet loss or change |
| 2451 |
jitter characteristics in the cases where packets are reordered when out-of-order packets are received at the service sub‑layer.<a href="#section-4.2.3-1" class="pilcrow">¶</a></p> |
| 2452 |
</section> |
| 2453 |
<section id="section-4.2.4"> |
| 2454 |
<h4 id="name-bidirectional-traffic"> |
| 2455 |
<a href="#section-4.2.4" class="section-number selfRef">4.2.4. </a><a href="#name-bidirectional-traffic" class="section-name selfRef">Bidirectional Traffic</a> |
| 2456 |
</h4> |
| 2457 |
<p id="section-4.2.4-1"> |
| 2458 |
In many cases, DetNet flows can be considered unidirectional and |
| 2459 |
independent. However, there are cases where the DetNet service requires |
| 2460 |
bidirectional traffic from a DetNet application service perspective. IP and |
| 2461 |
MPLS typically treat each direction separately and do not force |
| 2462 |
interdependence of each direction. The IETF MPLS Working Group has |
| 2463 |
studied bidirectional traffic requirements. The definitions provided in <span>[<a href="#RFC5654" class="xref">RFC5654</a>]</span> are useful to illustrate terms such as |
| 2464 |
associated bidirectional flows and co-routed bidirectional flows. |
| 2465 |
MPLS |
| 2466 |
defines a point-to-point associated bidirectional LSP as consisting of |
| 2467 |
two unidirectional point-to-point LSPs, one from A to B and the other |
| 2468 |
from B to A, which are regarded as providing a single logical |
| 2469 |
bidirectional forwarding path. This is analogous to standard IP |
| 2470 |
routing. MPLS defines a point-to-point co-routed bidirectional LSP as |
| 2471 |
an associated bidirectional LSP that satisfies the additional |
| 2472 |
constraint that its two unidirectional component LSPs follow the same |
| 2473 |
path (in terms of both nodes and links) in both directions. An |
| 2474 |
important property of co-routed bidirectional LSPs is that their |
| 2475 |
unidirectional component LSPs share fate. In both types of |
| 2476 |
bidirectional LSPs, resource reservations may differ in each direction. |
| 2477 |
The concepts of associated bidirectional flows and co‑routed |
| 2478 |
bidirectional flows can also be applied to DetNet IP flows.<a href="#section-4.2.4-1" class="pilcrow">¶</a></p> |
| 2479 |
<p id="section-4.2.4-2"> |
| 2480 |
While the DetNet IP data plane must support bidirectional |
| 2481 |
DetNet flows, there are no special bidirectional features with |
| 2482 |
respect to the data plane other than the need for the two |
| 2483 |
directions of a co‑routed bidirectional flow to take the same |
| 2484 |
path. That is to say, bidirectional DetNet flows are |
| 2485 |
solely represented at the management plane and control plane levels, |
| 2486 |
without specific support or knowledge within the DetNet data |
| 2487 |
plane. Fate-sharing and associated or co‑routed |
| 2488 |
bidirectional flows can be managed at the control level.<a href="#section-4.2.4-2" class="pilcrow">¶</a></p> |
| 2489 |
<p id="section-4.2.4-3"> |
| 2490 |
DetNet's use of PREOF may increase the complexity of using co‑routing |
| 2491 |
bidirectional flows, because if PREOF are used, the replication points |
| 2492 |
in one direction would have to match the elimination points in the |
| 2493 |
other direction, and vice versa. In such cases, the optimal points for |
| 2494 |
these functions in one direction may not match the optimal points in |
| 2495 |
the other, due to network and traffic constraints. |
| 2496 |
Furthermore, due to the per-packet service protection nature, |
| 2497 |
bidirectional forwarding may not be ensured. |
| 2498 |
The first packet of received member flows is selected by the |
| 2499 |
elimination function independently of which path it has taken |
| 2500 |
through the network.<a href="#section-4.2.4-3" class="pilcrow">¶</a></p> |
| 2501 |
<p id="section-4.2.4-4"> |
| 2502 |
Control and management mechanisms need to support bidirectional flows, |
| 2503 |
but the specification of such mechanisms is out of scope for this |
| 2504 |
document. Example control plane solutions for MPLS can be found in <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>, <span>[<a href="#RFC6387" class="xref">RFC6387</a>]</span>, and <span>[<a href="#RFC7551" class="xref">RFC7551</a>]</span>. These requirements are included in <a href="#control-management-requirements" class="xref">Section 4.1</a>.<a href="#section-4.2.4-4" class="pilcrow">¶</a></p> |
| 2505 |
</section> |
| 2506 |
</section> |
| 2507 |
</div> |
| 2508 |
<div id="PREOF"> |
| 2509 |
<section id="section-4.3"> |
| 2510 |
<h3 id="name-packet-replication-eliminat"> |
| 2511 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-packet-replication-eliminat" class="section-name selfRef">Packet Replication, Elimination, and Ordering Functions (PREOF)</a> |
| 2512 |
</h3> |
| 2513 |
<p id="section-4.3-1"> |
| 2514 |
The Controller Plane protocol solution required for managing the |
| 2515 |
processing of PREOF is outside the scope of this document. That |
| 2516 |
said, it should be noted that the ability to determine, for a |
| 2517 |
particular flow, optimal packet replication and elimination |
| 2518 |
points in the DetNet domain requires explicit support. There may |
| 2519 |
be existing capabilities that can be used or extended -- for example, GMPLS |
| 2520 |
end-to-end recovery <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span> and GMPLS segment |
| 2521 |
recovery <span>[<a href="#RFC4873" class="xref">RFC4873</a>]</span>.<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 2522 |
</section> |
| 2523 |
</div> |
| 2524 |
</section> |
| 2525 |
</div> |
| 2526 |
<section id="section-5"> |
| 2527 |
<h2 id="name-security-considerations"> |
| 2528 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2529 |
</h2> |
| 2530 |
<p id="section-5-1"> |
| 2531 |
Security considerations for DetNet are described in detail in |
| 2532 |
<span>[<a href="#DetNet-Security" class="xref">DetNet-Security</a>]</span>. General security considerations |
| 2533 |
for the DetNet architecture are described in <span>[<a href="#RFC8655" class="xref">RFC8655</a>]</span>. This section |
| 2534 |
considers architecture-level DetNet security considerations applicable to all data planes.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 2535 |
<p id="section-5-2"> |
| 2536 |
Part of what makes DetNet unique is its ability to provide specific and |
| 2537 |
reliable QoS (delivering data flows with extremely low |
| 2538 |
packet loss rates and bounded end-to-end delivery latency), and the |
| 2539 |
security-related aspects of protecting that QoS are |
| 2540 |
similarly unique.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 2541 |
<p id="section-5-3"> |
| 2542 |
As for all communications protocols, |
| 2543 |
the primary consideration for the data plane is to maintain |
| 2544 |
integrity of data and delivery of the associated DetNet service traversing |
| 2545 |
the DetNet network. |
| 2546 |
Application flows can be protected through whatever means is |
| 2547 |
provided by the underlying technology. For example, encryption may be |
| 2548 |
used, such as that provided by IPsec <span>[<a href="#RFC4301" class="xref">RFC4301</a>]</span> for IP |
| 2549 |
flows and/or by an underlying sub-network using MACsec |
| 2550 |
<span>[<a href="#IEEE802.1AE-2018" class="xref">IEEE802.1AE-2018</a>]</span> for Ethernet (Layer 2) flows.<a href="#section-5-3" class="pilcrow">¶</a></p> |
| 2551 |
<p id="section-5-4"> |
| 2552 |
At the management and control levels, DetNet flows are identified on a |
| 2553 |
per-flow basis, which may provide Controller Plane |
| 2554 |
attackers with additional information about the data flows (when |
| 2555 |
compared to Controller Planes that do not include per-flow identification). |
| 2556 |
This is an inherent property of DetNet that has security |
| 2557 |
implications that should be considered when determining if DetNet is |
| 2558 |
a suitable technology for any given use case.<a href="#section-5-4" class="pilcrow">¶</a></p> |
| 2559 |
<p id="section-5-5"> |
| 2560 |
To provide uninterrupted availability of the DetNet |
| 2561 |
service, provisions can be made against DoS attacks and delay |
| 2562 |
attacks. To protect against DoS attacks, excess traffic due to |
| 2563 |
malicious or malfunctioning devices can be prevented or mitigated -- |
| 2564 |
for example, through the use of existing mechanisms such as policing and shaping applied at |
| 2565 |
the input of a DetNet domain. To prevent DetNet packets from |
| 2566 |
being delayed by an entity external to a DetNet domain, DetNet |
| 2567 |
technology definitions can allow for the mitigation of |
| 2568 |
man-in-the-middle attacks -- for example, through the use of |
| 2569 |
authentication and authorization of devices within the DetNet domain.<a href="#section-5-5" class="pilcrow">¶</a></p> |
| 2570 |
<p id="section-5-6"> |
| 2571 |
In order to prevent or mitigate DetNet attacks on other networks via |
| 2572 |
flow escape, edge devices can, for example, use existing mechanisms such |
| 2573 |
as policing and shaping applied at the output of a DetNet domain.<a href="#section-5-6" class="pilcrow">¶</a></p> |
| 2574 |
</section> |
| 2575 |
<div id="iana"> |
| 2576 |
<section id="section-6"> |
| 2577 |
<h2 id="name-iana-considerations"> |
| 2578 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2579 |
</h2> |
| 2580 |
<p id="section-6-1"> |
| 2581 |
This document has no IANA actions.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 2582 |
</section> |
| 2583 |
</div> |
| 2584 |
<section id="section-7"> |
| 2585 |
<h2 id="name-references"> |
| 2586 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 2587 |
</h2> |
| 2588 |
<section id="section-7.1"> |
| 2589 |
<h3 id="name-normative-references"> |
| 2590 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 2591 |
</h3> |
| 2592 |
<dl class="references"> |
| 2593 |
<dt id="RFC8655">[RFC8655]</dt> |
| 2594 |
<dd> |
| 2595 |
<span class="refAuthor">Finn, N.</span><span class="refAuthor">, Thubert, P.</span><span class="refAuthor">, Varga, B.</span><span class="refAuthor">, and 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><<a href="https://www.rfc-editor.org/info/rfc8655">https://www.rfc-editor.org/info/rfc8655</a>></span>. </dd> |
| 2596 |
<dd class="break"></dd> |
| 2597 |
</dl> |
| 2598 |
</section> |
| 2599 |
<section id="section-7.2"> |
| 2600 |
<h3 id="name-informative-references"> |
| 2601 |
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2602 |
</h3> |
| 2603 |
<dl class="references"> |
| 2604 |
<dt id="I-D.ietf-detnet-flow-information-model">[DetNet-Flow-Info]</dt> |
| 2605 |
<dd> |
| 2606 |
<span class="refAuthor">Varga, B.</span><span class="refAuthor">, Farkas, J.</span><span class="refAuthor">, Cummings, R.</span><span class="refAuthor">, Jiang, Y.</span><span class="refAuthor">, and D. Fedyk</span>, <span class="refTitle">"DetNet Flow Information Model"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-detnet-flow-information-model-11</span>, <time datetime="2020-10-21" class="refDate">21 October 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-detnet-flow-information-model-11">https://tools.ietf.org/html/draft-ietf-detnet-flow-information-model-11</a>></span>. </dd> |
| 2607 |
<dd class="break"></dd> |
| 2608 |
<dt id="DetNet-MPLS">[DetNet-MPLS]</dt> |
| 2609 |
<dd> |
| 2610 |
<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><span class="refAuthor">, and J. Korhonen</span>, <span class="refTitle">"DetNet Data Plane: MPLS"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-detnet-mpls-13</span>, <time datetime="2020-10-11" class="refDate">11 October 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-detnet-mpls-13">https://tools.ietf.org/html/draft-ietf-detnet-mpls-13</a>></span>. </dd> |
| 2611 |
<dd class="break"></dd> |
| 2612 |
<dt id="DetNet-MPLS-over-TSN">[DetNet-MPLS-over-TSN]</dt> |
| 2613 |
<dd> |
| 2614 |
<span class="refAuthor">Varga, B., Ed.</span><span class="refAuthor">, Farkas, J.</span><span class="refAuthor">, Malis, A.</span><span class="refAuthor">, and S. Bryant</span>, <span class="refTitle">"DetNet Data Plane: MPLS over IEEE 802.1 Time Sensitive Networking (TSN)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-detnet-mpls-over-tsn-04</span>, <time datetime="2020-11-02" class="refDate">2 November 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-detnet-mpls-over-tsn-04">https://tools.ietf.org/html/draft-ietf-detnet-mpls-over-tsn-04</a>></span>. </dd> |
| 2615 |
<dd class="break"></dd> |
| 2616 |
<dt id="DetNet-MPLS-over-UDP-IP">[DetNet-MPLS-over-UDP-IP]</dt> |
| 2617 |
<dd> |
| 2618 |
<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">, and S. Bryant</span>, <span class="refTitle">"DetNet Data Plane: MPLS over UDP/IP"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-detnet-mpls-over-udp-ip-07</span>, <time datetime="2020-10-11" class="refDate">11 October 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-detnet-mpls-over-udp-ip-07">https://tools.ietf.org/html/draft-ietf-detnet-mpls-over-udp-ip-07</a>></span>. </dd> |
| 2619 |
<dd class="break"></dd> |
| 2620 |
<dt id="DetNet-Security">[DetNet-Security]</dt> |
| 2621 |
<dd> |
| 2622 |
<span class="refAuthor">Grossman, E., Ed.</span><span class="refAuthor">, Mizrahi, T.</span><span class="refAuthor">, and 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-12</span>, <time datetime="2020-10-02" class="refDate">2 October 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-detnet-security-12">https://tools.ietf.org/html/draft-ietf-detnet-security-12</a>></span>. </dd> |
| 2623 |
<dd class="break"></dd> |
| 2624 |
<dt id="I-D.ietf-idr-rfc5575bis">[Flow-Spec-Rules]</dt> |
| 2625 |
<dd> |
| 2626 |
<span class="refAuthor">Loibl, C.</span><span class="refAuthor">, Hares, S.</span><span class="refAuthor">, Raszuk, R.</span><span class="refAuthor">, McPherson, D.</span><span class="refAuthor">, and M. Bacher</span>, <span class="refTitle">"Dissemination of Flow Specification Rules"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-idr-rfc5575bis-27</span>, <time datetime="2020-10-15" class="refDate">15 October 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-27">https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-27</a>></span>. </dd> |
| 2627 |
<dd class="break"></dd> |
| 2628 |
<dt id="IEEE802.1AE-2018">[IEEE802.1AE-2018]</dt> |
| 2629 |
<dd> |
| 2630 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and metropolitan area networks-Media Access Control (MAC) Security"</span>, <span class="seriesInfo">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><<a href="https://ieeexplore.ieee.org/document/8585421">https://ieeexplore.ieee.org/document/8585421</a>></span>. </dd> |
| 2631 |
<dd class="break"></dd> |
| 2632 |
<dt id="IEEE802.1TSNTG">[IEEE802.1TSNTG]</dt> |
| 2633 |
<dd> |
| 2634 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"Time-Sensitive Networking (TSN) Task Group"</span>, <span><<a href="https://1.ieee802.org/tsn/">https://1.ieee802.org/tsn/</a>></span>. </dd> |
| 2635 |
<dd class="break"></dd> |
| 2636 |
<dt id="nwcrg">[nwcrg]</dt> |
| 2637 |
<dd> |
| 2638 |
<span class="refAuthor">IRTF</span>, <span class="refTitle">"Coding for efficient NetWork Communications Research Group (nwcrg)"</span>, <span><<a href="https://datatracker.ietf.org/rg/nwcrg/about">https://datatracker.ietf.org/rg/nwcrg/about</a>></span>. </dd> |
| 2639 |
<dd class="break"></dd> |
| 2640 |
<dt id="I-D.ietf-pce-pcep-extension-for-pce-controller">[PCECC]</dt> |
| 2641 |
<dd> |
| 2642 |
<span class="refAuthor">Li, Z.</span><span class="refAuthor">, Peng, S.</span><span class="refAuthor">, Negi, M. S.</span><span class="refAuthor">, Zhao, Q.</span><span class="refAuthor">, and C. Zhou</span>, <span class="refTitle">"PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-pce-pcep-extension-for-pce-controller-08</span>, <time datetime="2020-11-01" class="refDate">1 November 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controller-08">https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controller-08</a>></span>. </dd> |
| 2643 |
<dd class="break"></dd> |
| 2644 |
<dt id="RFC2205">[RFC2205]</dt> |
| 2645 |
<dd> |
| 2646 |
<span class="refAuthor">Braden, R., Ed.</span><span class="refAuthor">, Zhang, L.</span><span class="refAuthor">, Berson, S.</span><span class="refAuthor">, Herzog, S.</span><span class="refAuthor">, and S. Jamin</span>, <span class="refTitle">"Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"</span>, <span class="seriesInfo">RFC 2205</span>, <span class="seriesInfo">DOI 10.17487/RFC2205</span>, <time datetime="1997-09" class="refDate">September 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2205">https://www.rfc-editor.org/info/rfc2205</a>></span>. </dd> |
| 2647 |
<dd class="break"></dd> |
| 2648 |
<dt id="RFC2386">[RFC2386]</dt> |
| 2649 |
<dd> |
| 2650 |
<span class="refAuthor">Crawley, E.</span><span class="refAuthor">, Nair, R.</span><span class="refAuthor">, Rajagopalan, B.</span><span class="refAuthor">, and H. Sandick</span>, <span class="refTitle">"A Framework for QoS-based Routing in the Internet"</span>, <span class="seriesInfo">RFC 2386</span>, <span class="seriesInfo">DOI 10.17487/RFC2386</span>, <time datetime="1998-08" class="refDate">August 1998</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2386">https://www.rfc-editor.org/info/rfc2386</a>></span>. </dd> |
| 2651 |
<dd class="break"></dd> |
| 2652 |
<dt id="RFC3209">[RFC3209]</dt> |
| 2653 |
<dd> |
| 2654 |
<span class="refAuthor">Awduche, D.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Gan, D.</span><span class="refAuthor">, Li, T.</span><span class="refAuthor">, Srinivasan, V.</span><span class="refAuthor">, and G. Swallow</span>, <span class="refTitle">"RSVP-TE: Extensions to RSVP for LSP Tunnels"</span>, <span class="seriesInfo">RFC 3209</span>, <span class="seriesInfo">DOI 10.17487/RFC3209</span>, <time datetime="2001-12" class="refDate">December 2001</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3209">https://www.rfc-editor.org/info/rfc3209</a>></span>. </dd> |
| 2655 |
<dd class="break"></dd> |
| 2656 |
<dt id="RFC3473">[RFC3473]</dt> |
| 2657 |
<dd> |
| 2658 |
<span class="refAuthor">Berger, L., Ed.</span>, <span class="refTitle">"Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"</span>, <span class="seriesInfo">RFC 3473</span>, <span class="seriesInfo">DOI 10.17487/RFC3473</span>, <time datetime="2003-01" class="refDate">January 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3473">https://www.rfc-editor.org/info/rfc3473</a>></span>. </dd> |
| 2659 |
<dd class="break"></dd> |
| 2660 |
<dt id="RFC3670">[RFC3670]</dt> |
| 2661 |
<dd> |
| 2662 |
<span class="refAuthor">Moore, B.</span><span class="refAuthor">, Durham, D.</span><span class="refAuthor">, Strassner, J.</span><span class="refAuthor">, Westerinen, A.</span><span class="refAuthor">, and W. Weiss</span>, <span class="refTitle">"Information Model for Describing Network Device QoS Datapath Mechanisms"</span>, <span class="seriesInfo">RFC 3670</span>, <span class="seriesInfo">DOI 10.17487/RFC3670</span>, <time datetime="2004-01" class="refDate">January 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3670">https://www.rfc-editor.org/info/rfc3670</a>></span>. </dd> |
| 2663 |
<dd class="break"></dd> |
| 2664 |
<dt id="RFC4301">[RFC4301]</dt> |
| 2665 |
<dd> |
| 2666 |
<span class="refAuthor">Kent, S.</span><span class="refAuthor"> and K. Seo</span>, <span class="refTitle">"Security Architecture for the Internet Protocol"</span>, <span class="seriesInfo">RFC 4301</span>, <span class="seriesInfo">DOI 10.17487/RFC4301</span>, <time datetime="2005-12" class="refDate">December 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4301">https://www.rfc-editor.org/info/rfc4301</a>></span>. </dd> |
| 2667 |
<dd class="break"></dd> |
| 2668 |
<dt id="RFC4872">[RFC4872]</dt> |
| 2669 |
<dd> |
| 2670 |
<span class="refAuthor">Lang, J.P., Ed.</span><span class="refAuthor">, Rekhter, Y., Ed.</span><span class="refAuthor">, and D. Papadimitriou, Ed.</span>, <span class="refTitle">"RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"</span>, <span class="seriesInfo">RFC 4872</span>, <span class="seriesInfo">DOI 10.17487/RFC4872</span>, <time datetime="2007-05" class="refDate">May 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4872">https://www.rfc-editor.org/info/rfc4872</a>></span>. </dd> |
| 2671 |
<dd class="break"></dd> |
| 2672 |
<dt id="RFC4873">[RFC4873]</dt> |
| 2673 |
<dd> |
| 2674 |
<span class="refAuthor">Berger, L.</span><span class="refAuthor">, Bryskin, I.</span><span class="refAuthor">, Papadimitriou, D.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"GMPLS Segment Recovery"</span>, <span class="seriesInfo">RFC 4873</span>, <span class="seriesInfo">DOI 10.17487/RFC4873</span>, <time datetime="2007-05" class="refDate">May 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4873">https://www.rfc-editor.org/info/rfc4873</a>></span>. </dd> |
| 2675 |
<dd class="break"></dd> |
| 2676 |
<dt id="RFC5575">[RFC5575]</dt> |
| 2677 |
<dd> |
| 2678 |
<span class="refAuthor">Marques, P.</span><span class="refAuthor">, Sheth, N.</span><span class="refAuthor">, Raszuk, R.</span><span class="refAuthor">, Greene, B.</span><span class="refAuthor">, Mauch, J.</span><span class="refAuthor">, and D. McPherson</span>, <span class="refTitle">"Dissemination of Flow Specification Rules"</span>, <span class="seriesInfo">RFC 5575</span>, <span class="seriesInfo">DOI 10.17487/RFC5575</span>, <time datetime="2009-08" class="refDate">August 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5575">https://www.rfc-editor.org/info/rfc5575</a>></span>. </dd> |
| 2679 |
<dd class="break"></dd> |
| 2680 |
<dt id="RFC5654">[RFC5654]</dt> |
| 2681 |
<dd> |
| 2682 |
<span class="refAuthor">Niven-Jenkins, B., Ed.</span><span class="refAuthor">, Brungard, D., Ed.</span><span class="refAuthor">, Betts, M., Ed.</span><span class="refAuthor">, Sprecher, N.</span><span class="refAuthor">, and S. Ueno</span>, <span class="refTitle">"Requirements of an MPLS Transport Profile"</span>, <span class="seriesInfo">RFC 5654</span>, <span class="seriesInfo">DOI 10.17487/RFC5654</span>, <time datetime="2009-09" class="refDate">September 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5654">https://www.rfc-editor.org/info/rfc5654</a>></span>. </dd> |
| 2683 |
<dd class="break"></dd> |
| 2684 |
<dt id="RFC6387">[RFC6387]</dt> |
| 2685 |
<dd> |
| 2686 |
<span class="refAuthor">Takacs, A.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Caviglia, D.</span><span class="refAuthor">, Fedyk, D.</span><span class="refAuthor">, and J. Meuric</span>, <span class="refTitle">"GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"</span>, <span class="seriesInfo">RFC 6387</span>, <span class="seriesInfo">DOI 10.17487/RFC6387</span>, <time datetime="2011-09" class="refDate">September 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6387">https://www.rfc-editor.org/info/rfc6387</a>></span>. </dd> |
| 2687 |
<dd class="break"></dd> |
| 2688 |
<dt id="RFC7426">[RFC7426]</dt> |
| 2689 |
<dd> |
| 2690 |
<span class="refAuthor">Haleplidis, E., Ed.</span><span class="refAuthor">, Pentikousis, K., Ed.</span><span class="refAuthor">, Denazis, S.</span><span class="refAuthor">, Hadi Salim, J.</span><span class="refAuthor">, Meyer, D.</span><span class="refAuthor">, and O. Koufopavlou</span>, <span class="refTitle">"Software-Defined Networking (SDN): Layers and Architecture Terminology"</span>, <span class="seriesInfo">RFC 7426</span>, <span class="seriesInfo">DOI 10.17487/RFC7426</span>, <time datetime="2015-01" class="refDate">January 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7426">https://www.rfc-editor.org/info/rfc7426</a>></span>. </dd> |
| 2691 |
<dd class="break"></dd> |
| 2692 |
<dt id="RFC7551">[RFC7551]</dt> |
| 2693 |
<dd> |
| 2694 |
<span class="refAuthor">Zhang, F., Ed.</span><span class="refAuthor">, Jing, R.</span><span class="refAuthor">, and R. Gandhi, Ed.</span>, <span class="refTitle">"RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs)"</span>, <span class="seriesInfo">RFC 7551</span>, <span class="seriesInfo">DOI 10.17487/RFC7551</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7551">https://www.rfc-editor.org/info/rfc7551</a>></span>. </dd> |
| 2695 |
<dd class="break"></dd> |
| 2696 |
<dt id="RFC7657">[RFC7657]</dt> |
| 2697 |
<dd> |
| 2698 |
<span class="refAuthor">Black, D., Ed.</span><span class="refAuthor"> and P. Jones</span>, <span class="refTitle">"Differentiated Services (Diffserv) and Real-Time Communication"</span>, <span class="seriesInfo">RFC 7657</span>, <span class="seriesInfo">DOI 10.17487/RFC7657</span>, <time datetime="2015-11" class="refDate">November 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7657">https://www.rfc-editor.org/info/rfc7657</a>></span>. </dd> |
| 2699 |
<dd class="break"></dd> |
| 2700 |
<dt id="RFC7950">[RFC7950]</dt> |
| 2701 |
<dd> |
| 2702 |
<span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"The YANG 1.1 Data Modeling Language"</span>, <span class="seriesInfo">RFC 7950</span>, <span class="seriesInfo">DOI 10.17487/RFC7950</span>, <time datetime="2016-08" class="refDate">August 2016</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7950">https://www.rfc-editor.org/info/rfc7950</a>></span>. </dd> |
| 2703 |
<dd class="break"></dd> |
| 2704 |
<dt id="RFC8040">[RFC8040]</dt> |
| 2705 |
<dd> |
| 2706 |
<span class="refAuthor">Bierman, A.</span><span class="refAuthor">, Bjorklund, M.</span><span class="refAuthor">, and K. Watsen</span>, <span class="refTitle">"RESTCONF Protocol"</span>, <span class="seriesInfo">RFC 8040</span>, <span class="seriesInfo">DOI 10.17487/RFC8040</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8040">https://www.rfc-editor.org/info/rfc8040</a>></span>. </dd> |
| 2707 |
<dd class="break"></dd> |
| 2708 |
<dt id="RFC8227">[RFC8227]</dt> |
| 2709 |
<dd> |
| 2710 |
<span class="refAuthor">Cheng, W.</span><span class="refAuthor">, Wang, L.</span><span class="refAuthor">, Li, H.</span><span class="refAuthor">, van Helvoort, H.</span><span class="refAuthor">, and J. Dong</span>, <span class="refTitle">"MPLS-TP Shared-Ring Protection (MSRP) Mechanism for Ring Topology"</span>, <span class="seriesInfo">RFC 8227</span>, <span class="seriesInfo">DOI 10.17487/RFC8227</span>, <time datetime="2017-08" class="refDate">August 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8227">https://www.rfc-editor.org/info/rfc8227</a>></span>. </dd> |
| 2711 |
<dd class="break"></dd> |
| 2712 |
<dt id="RFC8939">[RFC8939]</dt> |
| 2713 |
<dd> |
| 2714 |
<span class="refAuthor">Varga, B., Ed.</span><span class="refAuthor">, Farkas, J.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Fedyk, D.</span><span class="refAuthor">, and S. Bryant</span>, <span class="refTitle">"Deterministic Networking (DetNet) Data Plane: IP"</span>, <span class="seriesInfo">RFC 8939</span>, <span class="seriesInfo">DOI 10.17487/RFC8939</span>, <time datetime="2020-11" class="refDate">November 2020</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8939">https://www.rfc-editor.org/info/rfc8939</a>></span>. </dd> |
| 2715 |
<dd class="break"></dd> |
| 2716 |
<dt id="SRv6-Network-Prog">[SRv6-Network-Prog]</dt> |
| 2717 |
<dd> |
| 2718 |
<span class="refAuthor">Filsfils, C., Ed.</span><span class="refAuthor">, Camarillo, P., Ed.</span><span class="refAuthor">, Leddy, J.</span><span class="refAuthor">, Voyer, D.</span><span class="refAuthor">, Matsushima, S.</span><span class="refAuthor">, and Z. Li</span>, <span class="refTitle">"SRv6 Network Programming"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-spring-srv6-network-programming-26</span>, <time datetime="2020-11-26" class="refDate">26 November 2020</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-26">https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-26</a>></span>. </dd> |
| 2719 |
<dd class="break"></dd> |
| 2720 |
</dl> |
| 2721 |
</section> |
| 2722 |
</section> |
| 2723 |
<div id="acks"> |
| 2724 |
<section id="section-appendix.a"> |
| 2725 |
<h2 id="name-acknowledgements"> |
| 2726 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 2727 |
</h2> |
| 2728 |
<p id="section-appendix.a-1"> |
| 2729 |
The authors wish to thank <span class="contact-name">Pat Thaler</span>, <span class="contact-name">Norman Finn</span>, <span class="contact-name">Loa Andersson</span>, <span class="contact-name">David Black</span>, <span class="contact-name">Rodney Cummings</span>, <span class="contact-name">Ethan Grossman</span>, <span class="contact-name">Tal Mizrahi</span>, <span class="contact-name">David Mozes</span>, <span class="contact-name">Craig Gunther</span>, <span class="contact-name">George Swallow</span>, <span class="contact-name">Yuanlong Jiang</span>, and |
| 2730 |
<span class="contact-name">Carlos J. Bernardos</span> for their various contributions |
| 2731 |
to this work.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p> |
| 2732 |
</section> |
| 2733 |
</div> |
| 2734 |
<div id="contrib"> |
| 2735 |
<section id="section-appendix.b"> |
| 2736 |
<h2 id="name-contributors"> |
| 2737 |
<a href="#name-contributors" class="section-name selfRef">Contributors</a> |
| 2738 |
</h2> |
| 2739 |
<p id="section-appendix.b-1"> |
| 2740 |
The following people contributed substantially to the content of this |
| 2741 |
document:<a href="#section-appendix.b-1" class="pilcrow">¶</a></p> |
| 2742 |
<ul class="ulEmpty compact"> |
| 2743 |
<li class="ulEmpty compact" id="section-appendix.b-2.1"> |
| 2744 |
<p id="section-appendix.b-2.1.1"><span class="contact-name">Don Fedyk</span><a href="#section-appendix.b-2.1.1" class="pilcrow">¶</a></p> |
| 2745 |
</li> |
| 2746 |
<li class="ulEmpty compact" id="section-appendix.b-2.2"> |
| 2747 |
<p id="section-appendix.b-2.2.1"><span class="contact-name">Jouni Korhonen</span><a href="#section-appendix.b-2.2.1" class="pilcrow">¶</a></p> |
| 2748 |
</li> |
| 2749 |
</ul> |
| 2750 |
</section> |
| 2751 |
</div> |
| 2752 |
<div id="authors-addresses"> |
| 2753 |
<section id="section-appendix.c"> |
| 2754 |
<h2 id="name-authors-addresses"> |
| 2755 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2756 |
</h2> |
| 2757 |
<address class="vcard"> |
| 2758 |
<div dir="auto" class="left"><span class="fn nameRole">Balázs Varga (<span class="role">editor</span>)</span></div> |
| 2759 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 2760 |
<div dir="auto" class="left"><span class="locality">Budapest</span></div> |
| 2761 |
<div dir="auto" class="left"><span class="street-address">Magyar Tudosok krt. 11.</span></div> |
| 2762 |
<div dir="auto" class="left"><span class="postal-code">1117</span></div> |
| 2763 |
<div dir="auto" class="left"><span class="country-name">Hungary</span></div> |
| 2764 |
<div class="email"> |
| 2765 |
<span>Email:</span> |
| 2766 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2767 |
</div> |
| 2768 |
</address> |
| 2769 |
<address class="vcard"> |
| 2770 |
<div dir="auto" class="left"><span class="fn nameRole">János Farkas</span></div> |
| 2771 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 2772 |
<div dir="auto" class="left"><span class="locality">Budapest</span></div> |
| 2773 |
<div dir="auto" class="left"><span class="street-address">Magyar Tudosok krt. 11.</span></div> |
| 2774 |
<div dir="auto" class="left"><span class="postal-code">1117</span></div> |
| 2775 |
<div dir="auto" class="left"><span class="country-name">Hungary</span></div> |
| 2776 |
<div class="email"> |
| 2777 |
<span>Email:</span> |
| 2778 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2779 |
</div> |
| 2780 |
</address> |
| 2781 |
<address class="vcard"> |
| 2782 |
<div dir="auto" class="left"><span class="fn nameRole">Lou Berger</span></div> |
| 2783 |
<div dir="auto" class="left"><span class="org">LabN Consulting, L.L.C.</span></div> |
| 2784 |
<div class="email"> |
| 2785 |
<span>Email:</span> |
| 2786 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2787 |
</div> |
| 2788 |
</address> |
| 2789 |
<address class="vcard"> |
| 2790 |
<div dir="auto" class="left"><span class="fn nameRole">Andrew G. Malis</span></div> |
| 2791 |
<div dir="auto" class="left"><span class="org">Malis Consulting</span></div> |
| 2792 |
<div class="email"> |
| 2793 |
<span>Email:</span> |
| 2794 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2795 |
</div> |
| 2796 |
</address> |
| 2797 |
<address class="vcard"> |
| 2798 |
<div dir="auto" class="left"><span class="fn nameRole">Stewart Bryant</span></div> |
| 2799 |
<div dir="auto" class="left"><span class="org">Futurewei Technologies</span></div> |
| 2800 |
<div class="email"> |
| 2801 |
<span>Email:</span> |
| 2802 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2803 |
</div> |
| 2804 |
</address> |
| 2805 |
</section> |
| 2806 |
</div> |
| 2807 |
<script>const toc = document.getElementById("toc"); |
| 2808 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2809 |
toc.classList.toggle("active"); |
| 2810 |
}); |
| 2811 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2812 |
toc.classList.remove("active"); |
| 2813 |
}); |
| 2814 |
</script> |
| 2815 |
</body> |
| 2816 |
</html> |