Debian Codegraph @

rfc8831.html

raw
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 8831: WebRTC Data Channels</title>
8 <meta content="Randell Jesup" name="author">
9 <meta content="Salvatore Loreto" name="author">
10 <meta content="Michael Tüxen" name="author">
11 <meta content="
12 The WebRTC framework specifies protocol support for direct, interactive,
13 rich communication using audio, video, and data between two peers' web browsers.
14 This document specifies the non-media data transport aspects of the WebRTC
15 framework. It provides an architectural overview of how the Stream Control
16 Transmission Protocol (SCTP) is used in the WebRTC context as a generic
17 transport service that allows web browsers to exchange generic data from peer to
18 peer.
19 " name="description">
20 <meta content="xml2rfc 3.5.0" name="generator">
21 <meta content="8831" name="rfc.number">
22 <!-- Generator version information:
23 xml2rfc 3.5.0
24 Python 3.6.10
25 appdirs 1.4.4
26 ConfigArgParse 1.2.3
27 google-i18n-address 2.3.5
28 html5lib 1.0.1
29 intervaltree 3.0.2
30 Jinja2 2.11.2
31 kitchen 1.2.6
32 lxml 4.4.2
33 pycairo 1.19.0
34 pycountry 19.8.18
35 pyflakes 2.1.1
36 PyYAML 5.3.1
37 requests 2.22.0
38 setuptools 40.6.2
39 six 1.14.0
40 WeasyPrint 51
41 -->
42 <link href="rfc8831.xml" rel="alternate" type="application/rfc+xml">
43 <link href="#copyright" rel="license">
44 <style type="text/css">/*
45
46 NOTE: Changes at the bottom of this file overrides some earlier settings.
47
48 Once the style has stabilized and has been adopted as an official RFC style,
49 this can be consolidated so that style settings occur only in one place, but
50 for now the contents of this file consists first of the initial CSS work as
51 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
52 commented changes found necssary during the development of the v3
53 formatters.
54
55 */
56
57 /* fonts */
58 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
59 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
60 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
61
62 @viewport {
63 zoom: 1.0;
64 width: extend-to-zoom;
65 }
66 @-ms-viewport {
67 width: extend-to-zoom;
68 zoom: 1.0;
69 }
70 /* general and mobile first */
71 html {
72 }
73 body {
74 max-width: 90%;
75 margin: 1.5em auto;
76 color: #222;
77 background-color: #fff;
78 font-size: 14px;
79 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
80 line-height: 1.6;
81 scroll-behavior: smooth;
82 }
83 .ears {
84 display: none;
85 }
86
87 /* headings */
88 #title, h1, h2, h3, h4, h5, h6 {
89 margin: 1em 0 0.5em;
90 font-weight: bold;
91 line-height: 1.3;
92 }
93 #title {
94 clear: both;
95 border-bottom: 1px solid #ddd;
96 margin: 0 0 0.5em 0;
97 padding: 1em 0 0.5em;
98 }
99 .author {
100 padding-bottom: 4px;
101 }
102 h1 {
103 font-size: 26px;
104 margin: 1em 0;
105 }
106 h2 {
107 font-size: 22px;
108 margin-top: -20px; /* provide offset for in-page anchors */
109 padding-top: 33px;
110 }
111 h3 {
112 font-size: 18px;
113 margin-top: -36px; /* provide offset for in-page anchors */
114 padding-top: 42px;
115 }
116 h4 {
117 font-size: 16px;
118 margin-top: -36px; /* provide offset for in-page anchors */
119 padding-top: 42px;
120 }
121 h5, h6 {
122 font-size: 14px;
123 }
124 #n-copyright-notice {
125 border-bottom: 1px solid #ddd;
126 padding-bottom: 1em;
127 margin-bottom: 1em;
128 }
129 /* general structure */
130 p {
131 padding: 0;
132 margin: 0 0 1em 0;
133 text-align: left;
134 }
135 div, span {
136 position: relative;
137 }
138 div {
139 margin: 0;
140 }
141 .alignRight.art-text {
142 background-color: #f9f9f9;
143 border: 1px solid #eee;
144 border-radius: 3px;
145 padding: 1em 1em 0;
146 margin-bottom: 1.5em;
147 }
148 .alignRight.art-text pre {
149 padding: 0;
150 }
151 .alignRight {
152 margin: 1em 0;
153 }
154 .alignRight > *:first-child {
155 border: none;
156 margin: 0;
157 float: right;
158 clear: both;
159 }
160 .alignRight > *:nth-child(2) {
161 clear: both;
162 display: block;
163 border: none;
164 }
165 svg {
166 display: block;
167 }
168 .alignCenter.art-text {
169 background-color: #f9f9f9;
170 border: 1px solid #eee;
171 border-radius: 3px;
172 padding: 1em 1em 0;
173 margin-bottom: 1.5em;
174 }
175 .alignCenter.art-text pre {
176 padding: 0;
177 }
178 .alignCenter {
179 margin: 1em 0;
180 }
181 .alignCenter > *:first-child {
182 border: none;
183 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
184 support flexbox yet.
185 */
186 display: table;
187 margin: 0 auto;
188 }
189
190 /* lists */
191 ol, ul {
192 padding: 0;
193 margin: 0 0 1em 2em;
194 }
195 ol ol, ul ul, ol ul, ul ol {
196 margin-left: 1em;
197 }
198 li {
199 margin: 0 0 0.25em 0;
200 }
201 .ulCompact li {
202 margin: 0;
203 }
204 ul.empty, .ulEmpty {
205 list-style-type: none;
206 }
207 ul.empty li, .ulEmpty li {
208 margin-top: 0.5em;
209 }
210 ul.compact, .ulCompact,
211 ol.compact, .olCompact {
212 line-height: 100%;
213 margin: 0 0 0 2em;
214 }
215
216 /* definition lists */
217 dl {
218 }
219 dl > dt {
220 float: left;
221 margin-right: 1em;
222 }
223 /*
224 dl.nohang > dt {
225 float: none;
226 }
227 */
228 dl > dd {
229 margin-bottom: .8em;
230 min-height: 1.3em;
231 }
232 dl.compact > dd, .dlCompact > dd {
233 margin-bottom: 0em;
234 }
235 dl > dd > dl {
236 margin-top: 0.5em;
237 margin-bottom: 0em;
238 }
239
240 /* links */
241 a {
242 text-decoration: none;
243 }
244 a[href] {
245 color: #22e; /* Arlen: WCAG 2019 */
246 }
247 a[href]:hover {
248 background-color: #f2f2f2;
249 }
250 figcaption a[href],
251 a[href].selfRef {
252 color: #222;
253 }
254 /* XXX probably not this:
255 a.selfRef:hover {
256 background-color: transparent;
257 cursor: default;
258 } */
259
260 /* Figures */
261 tt, code, pre, code {
262 background-color: #f9f9f9;
263 font-family: 'Roboto Mono', monospace;
264 }
265 pre {
266 border: 1px solid #eee;
267 margin: 0;
268 padding: 1em;
269 }
270 img {
271 max-width: 100%;
272 }
273 figure {
274 margin: 0;
275 }
276 figure blockquote {
277 margin: 0.8em 0.4em 0.4em;
278 }
279 figcaption {
280 font-style: italic;
281 margin: 0 0 1em 0;
282 }
283 @media screen {
284 pre {
285 overflow-x: auto;
286 max-width: 100%;
287 max-width: calc(100% - 22px);
288 }
289 }
290
291 /* aside, blockquote */
292 aside, blockquote {
293 margin-left: 0;
294 padding: 1.2em 2em;
295 }
296 blockquote {
297 background-color: #f9f9f9;
298 color: #111; /* Arlen: WCAG 2019 */
299 border: 1px solid #ddd;
300 border-radius: 3px;
301 margin: 1em 0;
302 }
303 cite {
304 display: block;
305 text-align: right;
306 font-style: italic;
307 }
308
309 /* tables */
310 table {
311 width: 100%;
312 margin: 0 0 1em;
313 border-collapse: collapse;
314 border: 1px solid #eee;
315 }
316 th, td {
317 text-align: left;
318 vertical-align: top;
319 padding: 0.5em 0.75em;
320 }
321 th {
322 text-align: left;
323 background-color: #e9e9e9;
324 }
325 tr:nth-child(2n+1) > td {
326 background-color: #f5f5f5;
327 }
328 table caption {
329 font-style: italic;
330 margin: 0;
331 padding: 0;
332 text-align: left;
333 }
334 table p {
335 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
336 be allowed within tables more generally, it would be far better to select on a class. */
337 margin: 0;
338 }
339
340 /* pilcrow */
341 a.pilcrow {
342 color: #666; /* Arlen: AHDJ 2019 */
343 text-decoration: none;
344 visibility: hidden;
345 user-select: none;
346 -ms-user-select: none;
347 -o-user-select:none;
348 -moz-user-select: none;
349 -khtml-user-select: none;
350 -webkit-user-select: none;
351 -webkit-touch-callout: none;
352 }
353 @media screen {
354 aside:hover > a.pilcrow,
355 p:hover > a.pilcrow,
356 blockquote:hover > a.pilcrow,
357 div:hover > a.pilcrow,
358 li:hover > a.pilcrow,
359 pre:hover > a.pilcrow {
360 visibility: visible;
361 }
362 a.pilcrow:hover {
363 background-color: transparent;
364 }
365 }
366
367 /* misc */
368 hr {
369 border: 0;
370 border-top: 1px solid #eee;
371 }
372 .bcp14 {
373 font-variant: small-caps;
374 }
375
376 .role {
377 font-variant: all-small-caps;
378 }
379
380 /* info block */
381 #identifiers {
382 margin: 0;
383 font-size: 0.9em;
384 }
385 #identifiers dt {
386 width: 3em;
387 clear: left;
388 }
389 #identifiers dd {
390 float: left;
391 margin-bottom: 0;
392 }
393 #identifiers .authors .author {
394 display: inline-block;
395 margin-right: 1.5em;
396 }
397 #identifiers .authors .org {
398 font-style: italic;
399 }
400
401 /* The prepared/rendered info at the very bottom of the page */
402 .docInfo {
403 color: #666; /* Arlen: WCAG 2019 */
404 font-size: 0.9em;
405 font-style: italic;
406 margin-top: 2em;
407 }
408 .docInfo .prepared {
409 float: left;
410 }
411 .docInfo .prepared {
412 float: right;
413 }
414
415 /* table of contents */
416 #toc {
417 padding: 0.75em 0 2em 0;
418 margin-bottom: 1em;
419 }
420 nav.toc ul {
421 margin: 0 0.5em 0 0;
422 padding: 0;
423 list-style: none;
424 }
425 nav.toc li {
426 line-height: 1.3em;
427 margin: 0.75em 0;
428 padding-left: 1.2em;
429 text-indent: -1.2em;
430 }
431 /* references */
432 .references dt {
433 text-align: right;
434 font-weight: bold;
435 min-width: 7em;
436 }
437 .references dd {
438 margin-left: 8em;
439 overflow: auto;
440 }
441
442 .refInstance {
443 margin-bottom: 1.25em;
444 }
445
446 .references .ascii {
447 margin-bottom: 0.25em;
448 }
449
450 /* index */
451 .index ul {
452 margin: 0 0 0 1em;
453 padding: 0;
454 list-style: none;
455 }
456 .index ul ul {
457 margin: 0;
458 }
459 .index li {
460 margin: 0;
461 text-indent: -2em;
462 padding-left: 2em;
463 padding-bottom: 5px;
464 }
465 .indexIndex {
466 margin: 0.5em 0 1em;
467 }
468 .index a {
469 font-weight: 700;
470 }
471 /* make the index two-column on all but the smallest screens */
472 @media (min-width: 600px) {
473 .index ul {
474 -moz-column-count: 2;
475 -moz-column-gap: 20px;
476 }
477 .index ul ul {
478 -moz-column-count: 1;
479 -moz-column-gap: 0;
480 }
481 }
482
483 /* authors */
484 address.vcard {
485 font-style: normal;
486 margin: 1em 0;
487 }
488
489 address.vcard .nameRole {
490 font-weight: 700;
491 margin-left: 0;
492 }
493 address.vcard .label {
494 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
495 margin: 0.5em 0;
496 }
497 address.vcard .type {
498 display: none;
499 }
500 .alternative-contact {
501 margin: 1.5em 0 1em;
502 }
503 hr.addr {
504 border-top: 1px dashed;
505 margin: 0;
506 color: #ddd;
507 max-width: calc(100% - 16px);
508 }
509
510 /* temporary notes */
511 .rfcEditorRemove::before {
512 position: absolute;
513 top: 0.2em;
514 right: 0.2em;
515 padding: 0.2em;
516 content: "The RFC Editor will remove this note";
517 color: #9e2a00; /* Arlen: WCAG 2019 */
518 background-color: #ffd; /* Arlen: WCAG 2019 */
519 }
520 .rfcEditorRemove {
521 position: relative;
522 padding-top: 1.8em;
523 background-color: #ffd; /* Arlen: WCAG 2019 */
524 border-radius: 3px;
525 }
526 .cref {
527 background-color: #ffd; /* Arlen: WCAG 2019 */
528 padding: 2px 4px;
529 }
530 .crefSource {
531 font-style: italic;
532 }
533 /* alternative layout for smaller screens */
534 @media screen and (max-width: 1023px) {
535 body {
536 padding-top: 2em;
537 }
538 #title {
539 padding: 1em 0;
540 }
541 h1 {
542 font-size: 24px;
543 }
544 h2 {
545 font-size: 20px;
546 margin-top: -18px; /* provide offset for in-page anchors */
547 padding-top: 38px;
548 }
549 #identifiers dd {
550 max-width: 60%;
551 }
552 #toc {
553 position: fixed;
554 z-index: 2;
555 top: 0;
556 right: 0;
557 padding: 0;
558 margin: 0;
559 background-color: inherit;
560 border-bottom: 1px solid #ccc;
561 }
562 #toc h2 {
563 margin: -1px 0 0 0;
564 padding: 4px 0 4px 6px;
565 padding-right: 1em;
566 min-width: 190px;
567 font-size: 1.1em;
568 text-align: right;
569 background-color: #444;
570 color: white;
571 cursor: pointer;
572 }
573 #toc h2::before { /* css hamburger */
574 float: right;
575 position: relative;
576 width: 1em;
577 height: 1px;
578 left: -164px;
579 margin: 6px 0 0 0;
580 background: white none repeat scroll 0 0;
581 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
582 content: "";
583 }
584 #toc nav {
585 display: none;
586 padding: 0.5em 1em 1em;
587 overflow: auto;
588 height: calc(100vh - 48px);
589 border-left: 1px solid #ddd;
590 }
591 }
592
593 /* alternative layout for wide screens */
594 @media screen and (min-width: 1024px) {
595 body {
596 max-width: 724px;
597 margin: 42px auto;
598 padding-left: 1.5em;
599 padding-right: 29em;
600 }
601 #toc {
602 position: fixed;
603 top: 42px;
604 right: 42px;
605 width: 25%;
606 margin: 0;
607 padding: 0 1em;
608 z-index: 1;
609 }
610 #toc h2 {
611 border-top: none;
612 border-bottom: 1px solid #ddd;
613 font-size: 1em;
614 font-weight: normal;
615 margin: 0;
616 padding: 0.25em 1em 1em 0;
617 }
618 #toc nav {
619 display: block;
620 height: calc(90vh - 84px);
621 bottom: 0;
622 padding: 0.5em 0 0;
623 overflow: auto;
624 }
625 img { /* future proofing */
626 max-width: 100%;
627 height: auto;
628 }
629 }
630
631 /* pagination */
632 @media print {
633 body {
634
635 width: 100%;
636 }
637 p {
638 orphans: 3;
639 widows: 3;
640 }
641 #n-copyright-notice {
642 border-bottom: none;
643 }
644 #toc, #n-introduction {
645 page-break-before: always;
646 }
647 #toc {
648 border-top: none;
649 padding-top: 0;
650 }
651 figure, pre {
652 page-break-inside: avoid;
653 }
654 figure {
655 overflow: scroll;
656 }
657 h1, h2, h3, h4, h5, h6 {
658 page-break-after: avoid;
659 }
660 h2+*, h3+*, h4+*, h5+*, h6+* {
661 page-break-before: avoid;
662 }
663 pre {
664 white-space: pre-wrap;
665 word-wrap: break-word;
666 font-size: 10pt;
667 }
668 table {
669 border: 1px solid #ddd;
670 }
671 td {
672 border-top: 1px solid #ddd;
673 }
674 }
675
676 /* This is commented out here, as the string-set: doesn't
677 pass W3C validation currently */
678 /*
679 .ears thead .left {
680 string-set: ears-top-left content();
681 }
682
683 .ears thead .center {
684 string-set: ears-top-center content();
685 }
686
687 .ears thead .right {
688 string-set: ears-top-right content();
689 }
690
691 .ears tfoot .left {
692 string-set: ears-bottom-left content();
693 }
694
695 .ears tfoot .center {
696 string-set: ears-bottom-center content();
697 }
698
699 .ears tfoot .right {
700 string-set: ears-bottom-right content();
701 }
702 */
703
704 @page :first {
705 padding-top: 0;
706 @top-left {
707 content: normal;
708 border: none;
709 }
710 @top-center {
711 content: normal;
712 border: none;
713 }
714 @top-right {
715 content: normal;
716 border: none;
717 }
718 }
719
720 @page {
721 size: A4;
722 margin-bottom: 45mm;
723 padding-top: 20px;
724 /* The follwing is commented out here, but set appropriately by in code, as
725 the content depends on the document */
726 /*
727 @top-left {
728 content: 'Internet-Draft';
729 vertical-align: bottom;
730 border-bottom: solid 1px #ccc;
731 }
732 @top-left {
733 content: string(ears-top-left);
734 vertical-align: bottom;
735 border-bottom: solid 1px #ccc;
736 }
737 @top-center {
738 content: string(ears-top-center);
739 vertical-align: bottom;
740 border-bottom: solid 1px #ccc;
741 }
742 @top-right {
743 content: string(ears-top-right);
744 vertical-align: bottom;
745 border-bottom: solid 1px #ccc;
746 }
747 @bottom-left {
748 content: string(ears-bottom-left);
749 vertical-align: top;
750 border-top: solid 1px #ccc;
751 }
752 @bottom-center {
753 content: string(ears-bottom-center);
754 vertical-align: top;
755 border-top: solid 1px #ccc;
756 }
757 @bottom-right {
758 content: '[Page ' counter(page) ']';
759 vertical-align: top;
760 border-top: solid 1px #ccc;
761 }
762 */
763
764 }
765
766 /* Changes introduced to fix issues found during implementation */
767 /* Make sure links are clickable even if overlapped by following H* */
768 a {
769 z-index: 2;
770 }
771 /* Separate body from document info even without intervening H1 */
772 section {
773 clear: both;
774 }
775
776
777 /* Top align author divs, to avoid names without organization dropping level with org names */
778 .author {
779 vertical-align: top;
780 }
781
782 /* Leave room in document info to show Internet-Draft on one line */
783 #identifiers dt {
784 width: 8em;
785 }
786
787 /* Don't waste quite as much whitespace between label and value in doc info */
788 #identifiers dd {
789 margin-left: 1em;
790 }
791
792 /* Give floating toc a background color (needed when it's a div inside section */
793 #toc {
794 background-color: white;
795 }
796
797 /* Make the collapsed ToC header render white on gray also when it's a link */
798 @media screen and (max-width: 1023px) {
799 #toc h2 a,
800 #toc h2 a:link,
801 #toc h2 a:focus,
802 #toc h2 a:hover,
803 #toc a.toplink,
804 #toc a.toplink:hover {
805 color: white;
806 background-color: #444;
807 text-decoration: none;
808 }
809 }
810
811 /* Give the bottom of the ToC some whitespace */
812 @media screen and (min-width: 1024px) {
813 #toc {
814 padding: 0 0 1em 1em;
815 }
816 }
817
818 /* Style section numbers with more space between number and title */
819 .section-number {
820 padding-right: 0.5em;
821 }
822
823 /* prevent monospace from becoming overly large */
824 tt, code, pre, code {
825 font-size: 95%;
826 }
827
828 /* Fix the height/width aspect for ascii art*/
829 pre.sourcecode,
830 .art-text pre {
831 line-height: 1.12;
832 }
833
834
835 /* Add styling for a link in the ToC that points to the top of the document */
836 a.toplink {
837 float: right;
838 margin-right: 0.5em;
839 }
840
841 /* Fix the dl styling to match the RFC 7992 attributes */
842 dl > dt,
843 dl.dlParallel > dt {
844 float: left;
845 margin-right: 1em;
846 }
847 dl.dlNewline > dt {
848 float: none;
849 }
850
851 /* Provide styling for table cell text alignment */
852 table td.text-left,
853 table th.text-left {
854 text-align: left;
855 }
856 table td.text-center,
857 table th.text-center {
858 text-align: center;
859 }
860 table td.text-right,
861 table th.text-right {
862 text-align: right;
863 }
864
865 /* Make the alternative author contact informatio look less like just another
866 author, and group it closer with the primary author contact information */
867 .alternative-contact {
868 margin: 0.5em 0 0.25em 0;
869 }
870 address .non-ascii {
871 margin: 0 0 0 2em;
872 }
873
874 /* With it being possible to set tables with alignment
875 left, center, and right, { width: 100%; } does not make sense */
876 table {
877 width: auto;
878 }
879
880 /* Avoid reference text that sits in a block with very wide left margin,
881 because of a long floating dt label.*/
882 .references dd {
883 overflow: visible;
884 }
885
886 /* Control caption placement */
887 caption {
888 caption-side: bottom;
889 }
890
891 /* Limit the width of the author address vcard, so names in right-to-left
892 script don't end up on the other side of the page. */
893
894 address.vcard {
895 max-width: 30em;
896 margin-right: auto;
897 }
898
899 /* For address alignment dependent on LTR or RTL scripts */
900 address div.left {
901 text-align: left;
902 }
903 address div.right {
904 text-align: right;
905 }
906
907 /* Provide table alignment support. We can't use the alignX classes above
908 since they do unwanted things with caption and other styling. */
909 table.right {
910 margin-left: auto;
911 margin-right: 0;
912 }
913 table.center {
914 margin-left: auto;
915 margin-right: auto;
916 }
917 table.left {
918 margin-left: 0;
919 margin-right: auto;
920 }
921
922 /* Give the table caption label the same styling as the figcaption */
923 caption a[href] {
924 color: #222;
925 }
926
927 @media print {
928 .toplink {
929 display: none;
930 }
931
932 /* avoid overwriting the top border line with the ToC header */
933 #toc {
934 padding-top: 1px;
935 }
936
937 /* Avoid page breaks inside dl and author address entries */
938 .vcard {
939 page-break-inside: avoid;
940 }
941
942 }
943 /* Tweak the bcp14 keyword presentation */
944 .bcp14 {
945 font-variant: small-caps;
946 font-weight: bold;
947 font-size: 0.9em;
948 }
949 /* Tweak the invisible space above H* in order not to overlay links in text above */
950 h2 {
951 margin-top: -18px; /* provide offset for in-page anchors */
952 padding-top: 31px;
953 }
954 h3 {
955 margin-top: -18px; /* provide offset for in-page anchors */
956 padding-top: 24px;
957 }
958 h4 {
959 margin-top: -18px; /* provide offset for in-page anchors */
960 padding-top: 24px;
961 }
962 /* Float artwork pilcrow to the right */
963 @media screen {
964 .artwork a.pilcrow {
965 display: block;
966 line-height: 0.7;
967 margin-top: 0.15em;
968 }
969 }
970 /* Make pilcrows on dd visible */
971 @media screen {
972 dd:hover > a.pilcrow {
973 visibility: visible;
974 }
975 }
976 /* Make the placement of figcaption match that of a table's caption
977 by removing the figure's added bottom margin */
978 .alignLeft.art-text,
979 .alignCenter.art-text,
980 .alignRight.art-text {
981 margin-bottom: 0;
982 }
983 .alignLeft,
984 .alignCenter,
985 .alignRight {
986 margin: 1em 0 0 0;
987 }
988 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
989 possibly even requiring a new line */
990 @media print {
991 a.pilcrow {
992 display: none;
993 }
994 }
995 /* Styling for the external metadata */
996 div#external-metadata {
997 background-color: #eee;
998 padding: 0.5em;
999 margin-bottom: 0.5em;
1000 display: none;
1001 }
1002 div#internal-metadata {
1003 padding: 0.5em; /* to match the external-metadata padding */
1004 }
1005 /* Styling for title RFC Number */
1006 h1#rfcnum {
1007 clear: both;
1008 margin: 0 0 -1em;
1009 padding: 1em 0 0 0;
1010 }
1011 /* Make .olPercent look the same as <ol><li> */
1012 dl.olPercent > dd {
1013 margin-bottom: 0.25em;
1014 min-height: initial;
1015 }
1016 /* Give aside some styling to set it apart */
1017 aside {
1018 border-left: 1px solid #ddd;
1019 margin: 1em 0 1em 2em;
1020 padding: 0.2em 2em;
1021 }
1022 aside > dl,
1023 aside > ol,
1024 aside > ul,
1025 aside > table,
1026 aside > p {
1027 margin-bottom: 0.5em;
1028 }
1029 /* Additional page break settings */
1030 @media print {
1031 figcaption, table caption {
1032 page-break-before: avoid;
1033 }
1034 }
1035 /* Font size adjustments for print */
1036 @media print {
1037 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1038 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1039 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1040 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1041 h4 { font-size: 1em; padding-top: 1.5em; }
1042 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1043 }
1044 /* Sourcecode margin in print, when there's no pilcrow */
1045 @media print {
1046 .artwork,
1047 .sourcecode {
1048 margin-bottom: 1em;
1049 }
1050 }
1051 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1052 table {
1053 min-width: 20em;
1054 }
1055 /* ol type a */
1056 ol.type-a { list-style-type: lower-alpha; }
1057 ol.type-A { list-style-type: upper-alpha; }
1058 ol.type-i { list-style-type: lower-roman; }
1059 ol.type-I { list-style-type: lower-roman; }
1060 /* Apply the print table and row borders in general, on request from the RPC,
1061 and increase the contrast between border and odd row background sligthtly */
1062 table {
1063 border: 1px solid #ddd;
1064 }
1065 td {
1066 border-top: 1px solid #ddd;
1067 }
1068 tr:nth-child(2n+1) > td {
1069 background-color: #f8f8f8;
1070 }
1071 /* Use style rules to govern display of the TOC. */
1072 @media screen and (max-width: 1023px) {
1073 #toc nav { display: none; }
1074 #toc.active nav { display: block; }
1075 }
1076 /* Add support for keepWithNext */
1077 .keepWithNext {
1078 break-after: avoid-page;
1079 break-after: avoid-page;
1080 }
1081 /* Add support for keepWithPrevious */
1082 .keepWithPrevious {
1083 break-before: avoid-page;
1084 }
1085 /* Change the approach to avoiding breaks inside artwork etc. */
1086 figure, pre, table, .artwork, .sourcecode {
1087 break-before: avoid-page;
1088 break-after: auto;
1089 }
1090 /* Avoid breaks between <dt> and <dd> */
1091 dl {
1092 break-before: auto;
1093 break-inside: auto;
1094 }
1095 dt {
1096 break-before: auto;
1097 break-after: avoid-page;
1098 }
1099 dd {
1100 break-before: avoid-page;
1101 break-after: auto;
1102 orphans: 3;
1103 widows: 3
1104 }
1105 span.break, dd.break {
1106 margin-bottom: 0;
1107 min-height: 0;
1108 break-before: auto;
1109 break-inside: auto;
1110 break-after: auto;
1111 }
1112 /* Undo break-before ToC */
1113 @media print {
1114 #toc {
1115 break-before: auto;
1116 }
1117 }
1118 /* Text in compact lists should not get extra bottim margin space,
1119 since that would makes the list not compact */
1120 ul.compact p, .ulCompact p,
1121 ol.compact p, .olCompact p {
1122 margin: 0;
1123 }
1124 /* But the list as a whole needs the extra space at the end */
1125 section ul.compact,
1126 section .ulCompact,
1127 section ol.compact,
1128 section .olCompact {
1129 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1130 }
1131 /* The tt and code background above interferes with for instance table cell
1132 backgrounds. Changed to something a bit more selective. */
1133 tt, code {
1134 background-color: transparent;
1135 }
1136 p tt, p code, li tt, li code {
1137 background-color: #f8f8f8;
1138 }
1139 /* Tweak the pre margin -- 0px doesn't come out well */
1140 pre {
1141 margin-top: 0.5px;
1142 }
1143 /* Tweak the comact list text */
1144 ul.compact, .ulCompact,
1145 ol.compact, .olCompact,
1146 dl.compact, .dlCompact {
1147 line-height: normal;
1148 }
1149 /* Don't add top margin for nested lists */
1150 li > ul, li > ol, li > dl,
1151 dd > ul, dd > ol, dd > dl,
1152 dl > dd > dl {
1153 margin-top: initial;
1154 }
1155 /* Elements that should not be rendered on the same line as a <dt> */
1156 /* This should match the element list in writer.text.TextWriter.render_dl() */
1157 dd > div.artwork:first-child,
1158 dd > aside:first-child,
1159 dd > figure:first-child,
1160 dd > ol:first-child,
1161 dd > div:first-child > pre.sourcecode,
1162 dd > table:first-child,
1163 dd > ul:first-child {
1164 clear: left;
1165 }
1166 /* fix for weird browser behaviour when <dd/> is empty */
1167 dt+dd:empty::before{
1168 content: "\00a0";
1169 }
1170 </style>
1171 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1172 <link href="https://dx.doi.org/10.17487/rfc8831" rel="alternate">
1173 <link href="urn:issn:2070-1721" rel="alternate">
1174 <link href="https://datatracker.ietf.org/doc/draft-ietf-rtcweb-data-channel-13" rel="prev">
1175 </head>
1176 <body>
1177 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1178 <table class="ears">
1179 <thead><tr>
1180 <td class="left">RFC 8831</td>
1181 <td class="center">WebRTC Data Channels</td>
1182 <td class="right">January 2021</td>
1183 </tr></thead>
1184 <tfoot><tr>
1185 <td class="left">Jesup, et al.</td>
1186 <td class="center">Standards Track</td>
1187 <td class="right">[Page]</td>
1188 </tr></tfoot>
1189 </table>
1190 <div id="external-metadata" class="document-information"></div>
1191 <div id="internal-metadata" class="document-information">
1192 <dl id="identifiers">
1193 <dt class="label-stream">Stream:</dt>
1194 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1195 <dt class="label-rfc">RFC:</dt>
1196 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8831" class="eref">8831</a></dd>
1197 <dt class="label-category">Category:</dt>
1198 <dd class="category">Standards Track</dd>
1199 <dt class="label-published">Published:</dt>
1200 <dd class="published">
1201 <time datetime="2021-01" class="published">January 2021</time>
1202 </dd>
1203 <dt class="label-issn">ISSN:</dt>
1204 <dd class="issn">2070-1721</dd>
1205 <dt class="label-authors">Authors:</dt>
1206 <dd class="authors">
1207 <div class="author">
1208 <div class="author-name">R. Jesup</div>
1209 <div class="org">Mozilla</div>
1210 </div>
1211 <div class="author">
1212 <div class="author-name">S. Loreto</div>
1213 <div class="org">Ericsson</div>
1214 </div>
1215 <div class="author">
1216 <div class="author-name">M. Tüxen</div>
1217 <div class="org">Münster Univ. of Appl. Sciences</div>
1218 </div>
1219 </dd>
1220 </dl>
1221 </div>
1222 <h1 id="rfcnum">RFC 8831</h1>
1223 <h1 id="title">WebRTC Data Channels</h1>
1224 <section id="section-abstract">
1225 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1226 <p id="section-abstract-1">The WebRTC framework specifies protocol support for direct, interactive,
1227 rich communication using audio, video, and data between two peers' web browsers.
1228 This document specifies the non-media data transport aspects of the WebRTC
1229 framework. It provides an architectural overview of how the Stream Control
1230 Transmission Protocol (SCTP) is used in the WebRTC context as a generic
1231 transport service that allows web browsers to exchange generic data from peer to
1232 peer.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1233 </section>
1234 <div id="status-of-memo">
1235 <section id="section-boilerplate.1">
1236 <h2 id="name-status-of-this-memo">
1237 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1238 </h2>
1239 <p id="section-boilerplate.1-1">
1240 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1241 <p id="section-boilerplate.1-2">
1242 This document is a product of the Internet Engineering Task Force
1243 (IETF). It represents the consensus of the IETF community. It has
1244 received public review and has been approved for publication by
1245 the Internet Engineering Steering Group (IESG). Further
1246 information on Internet Standards is available in Section 2 of
1247 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1248 <p id="section-boilerplate.1-3">
1249 Information about the current status of this document, any
1250 errata, and how to provide feedback on it may be obtained at
1251 <span><a href="https://www.rfc-editor.org/info/rfc8831">https://www.rfc-editor.org/info/rfc8831</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1252 </section>
1253 </div>
1254 <div id="copyright">
1255 <section id="section-boilerplate.2">
1256 <h2 id="name-copyright-notice">
1257 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1258 </h2>
1259 <p id="section-boilerplate.2-1">
1260 Copyright (c) 2021 IETF Trust and the persons identified as the
1261 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1262 <p id="section-boilerplate.2-2">
1263 This document is subject to BCP 78 and the IETF Trust's Legal
1264 Provisions Relating to IETF Documents
1265 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1266 publication of this document. Please review these documents
1267 carefully, as they describe your rights and restrictions with
1268 respect to this document. Code Components extracted from this
1269 document must include Simplified BSD License text as described in
1270 Section 4.e of the Trust Legal Provisions and are provided without
1271 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1272 </section>
1273 </div>
1274 <div id="toc">
1275 <section id="section-toc.1">
1276 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1277 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1278 </h2>
1279 <nav class="toc"><ul class="toc ulEmpty compact">
1280 <li class="toc ulEmpty compact" id="section-toc.1-1.1">
1281 <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>
1282 </li>
1283 <li class="toc ulEmpty compact" id="section-toc.1-1.2">
1284 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-conventions" class="xref">Conventions</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1285 </li>
1286 <li class="toc ulEmpty compact" id="section-toc.1-1.3">
1287 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-use-cases" class="xref">Use Cases</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1288 <ul class="toc ulEmpty compact">
1289 <li class="toc ulEmpty compact" id="section-toc.1-1.3.2.1">
1290 <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-use-cases-for-unreliable-da" class="xref">Use Cases for Unreliable Data Channels</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
1291 </li>
1292 <li class="toc ulEmpty compact" id="section-toc.1-1.3.2.2">
1293 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-use-cases-for-reliable-data" class="xref">Use Cases for Reliable Data Channels</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
1294 </li>
1295 </ul>
1296 </li>
1297 <li class="toc ulEmpty compact" id="section-toc.1-1.4">
1298 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-requirements" class="xref">Requirements</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1299 </li>
1300 <li class="toc ulEmpty compact" id="section-toc.1-1.5">
1301 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-sctp-over-dtls-over-udp-con" class="xref">SCTP over DTLS over UDP Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1302 </li>
1303 <li class="toc ulEmpty compact" id="section-toc.1-1.6">
1304 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-the-usage-of-sctp-for-data-" class="xref">The Usage of SCTP for Data Channels</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1305 <ul class="toc ulEmpty compact">
1306 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.1">
1307 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-sctp-protocol-consideration" class="xref">SCTP Protocol Considerations</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
1308 </li>
1309 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.2">
1310 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-sctp-association-management" class="xref">SCTP Association Management</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p>
1311 </li>
1312 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.3">
1313 <p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>.  <a href="#name-sctp-streams" class="xref">SCTP Streams</a><a href="#section-toc.1-1.6.2.3.1" class="pilcrow">¶</a></p>
1314 </li>
1315 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.4">
1316 <p id="section-toc.1-1.6.2.4.1"><a href="#section-6.4" class="xref">6.4</a>.  <a href="#name-data-channel-definition" class="xref">Data Channel Definition</a><a href="#section-toc.1-1.6.2.4.1" class="pilcrow">¶</a></p>
1317 </li>
1318 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.5">
1319 <p id="section-toc.1-1.6.2.5.1"><a href="#section-6.5" class="xref">6.5</a>.  <a href="#name-opening-a-data-channel" class="xref">Opening a Data Channel</a><a href="#section-toc.1-1.6.2.5.1" class="pilcrow">¶</a></p>
1320 </li>
1321 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.6">
1322 <p id="section-toc.1-1.6.2.6.1"><a href="#section-6.6" class="xref">6.6</a>.  <a href="#name-transferring-user-data-on-a" class="xref">Transferring User Data on a Data Channel</a><a href="#section-toc.1-1.6.2.6.1" class="pilcrow">¶</a></p>
1323 </li>
1324 <li class="toc ulEmpty compact" id="section-toc.1-1.6.2.7">
1325 <p id="section-toc.1-1.6.2.7.1"><a href="#section-6.7" class="xref">6.7</a>.  <a href="#name-closing-a-data-channel" class="xref">Closing a Data Channel</a><a href="#section-toc.1-1.6.2.7.1" class="pilcrow">¶</a></p>
1326 </li>
1327 </ul>
1328 </li>
1329 <li class="toc ulEmpty compact" id="section-toc.1-1.7">
1330 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1331 </li>
1332 <li class="toc ulEmpty compact" id="section-toc.1-1.8">
1333 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1334 </li>
1335 <li class="toc ulEmpty compact" id="section-toc.1-1.9">
1336 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
1337 <ul class="toc ulEmpty compact">
1338 <li class="toc ulEmpty compact" id="section-toc.1-1.9.2.1">
1339 <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p>
1340 </li>
1341 <li class="toc ulEmpty compact" id="section-toc.1-1.9.2.2">
1342 <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p>
1343 </li>
1344 </ul>
1345 </li>
1346 <li class="toc ulEmpty compact" id="section-toc.1-1.10">
1347 <p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
1348 </li>
1349 <li class="toc ulEmpty compact" id="section-toc.1-1.11">
1350 <p id="section-toc.1-1.11.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
1351 </li>
1352 </ul>
1353 </nav>
1354 </section>
1355 </div>
1356 <section id="section-1">
1357 <h2 id="name-introduction">
1358 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1359 </h2>
1360 <p id="section-1-1">In the WebRTC framework, communication between the parties consists of media
1361 (for example, audio and video) and non-media data.
1362 Media is sent using the Secure Real-time Transport Protocol (SRTP)
1363 and is not specified further here.
1364 Non-media data is handled by using the Stream Control Transmission Protocol (SCTP) <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span> encapsulated
1365 in DTLS. DTLS 1.0 is defined in <span>[<a href="#RFC4347" class="xref">RFC4347</a>]</span>; the present
1366 latest version, DTLS 1.2, is defined in <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>; and
1367 an upcoming version, DTLS 1.3, is defined in <span>[<a href="#I-D.ietf-tls-dtls13" class="xref">TLS-DTLS13</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p>
1368 <span id="name-basic-stack-diagram"></span><div id="fig-stack">
1369 <figure id="figure-1">
1370 <div class="artwork art-text alignCenter" id="section-1-2.1">
1371 <pre>
1372 +----------+
1373 | SCTP |
1374 +----------+
1375 | DTLS |
1376 +----------+
1377 | ICE/UDP |
1378 +----------+</pre>
1379 </div>
1380 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1381 <a href="#name-basic-stack-diagram" class="selfRef">Basic Stack Diagram</a>
1382 </figcaption></figure>
1383 </div>
1384 <p id="section-1-3">The encapsulation of SCTP over DTLS
1385 (see <span>[<a href="#RFC8261" class="xref">RFC8261</a>]</span>) over ICE/UDP
1386 (see <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>) provides a NAT traversal
1387 solution together with confidentiality, source authentication, and
1388 integrity-protected transfers.
1389 This data transport service operates in parallel to the SRTP media transports,
1390 and all of them can eventually share a single UDP port number.<a href="#section-1-3" class="pilcrow">¶</a></p>
1391 <p id="section-1-4">SCTP, as specified in <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span> with the partial reliability
1392 extension (PR-SCTP) defined in <span>[<a href="#RFC3758" class="xref">RFC3758</a>]</span> and the additional policies
1393 defined in <span>[<a href="#RFC7496" class="xref">RFC7496</a>]</span>,
1394 provides multiple streams natively with reliable, and the relevant
1395 partially reliable, delivery modes for user messages.
1396 Using the reconfiguration extension defined in <span>[<a href="#RFC6525" class="xref">RFC6525</a>]</span>
1397 allows an increase in the number of streams during the lifetime of an SCTP
1398 association and allows individual SCTP streams to be reset.
1399 Using <span>[<a href="#RFC8260" class="xref">RFC8260</a>]</span> allows the interleave of large messages to
1400 avoid monopolization and adds support for
1401 prioritizing SCTP streams.<a href="#section-1-4" class="pilcrow">¶</a></p>
1402 <p id="section-1-5">The remainder of this document is organized as follows:
1403 Sections <a href="#sec-use-cases" class="xref">3</a> and <a href="#sec-req" class="xref">4</a> provide use cases
1404 and requirements for both unreliable and reliable peer-to-peer data channels;
1405 <a href="#sec-p-a-2" class="xref">Section 5</a> discusses SCTP over DTLS over UDP; and
1406 <a href="#sec-sctp-usage" class="xref">Section 6</a> specifies how SCTP should be
1407 used by the WebRTC protocol framework for transporting non-media data
1408 between web browsers.<a href="#section-1-5" class="pilcrow">¶</a></p>
1409 </section>
1410 <section id="section-2">
1411 <h2 id="name-conventions">
1412 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions" class="section-name selfRef">Conventions</a>
1413 </h2>
1414 <p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
1415 "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>",
1416 "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>",
1417 "<span class="bcp14">SHOULD NOT</span>",
1418 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1419 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document
1420 are to be interpreted as described in BCP 14
1421 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only
1422 when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1423 </section>
1424 <div id="sec-use-cases">
1425 <section id="section-3">
1426 <h2 id="name-use-cases">
1427 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-use-cases" class="section-name selfRef">Use Cases</a>
1428 </h2>
1429 <p id="section-3-1">This section defines use cases specific to data channels.
1430 Please note that this section is informational only.<a href="#section-3-1" class="pilcrow">¶</a></p>
1431 <div id="sec-use-cases-unreliable">
1432 <section id="section-3.1">
1433 <h3 id="name-use-cases-for-unreliable-da">
1434 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-use-cases-for-unreliable-da" class="section-name selfRef">Use Cases for Unreliable Data Channels</a>
1435 </h3>
1436 <span class="break"></span><dl class="olPercent" id="section-3.1-1">
1437 <dt>U-C 1:</dt>
1438 <dd style="margin-left: 4.0em" id="section-3.1-1.1">A real-time game where position and object state information are
1439 sent via one or more unreliable data channels.
1440 Note that at any time, there may not be any SRTP media channels or all SRTP media
1441 channels may be inactive, and there may also be reliable data channels
1442 in use.<a href="#section-3.1-1.1" class="pilcrow">¶</a>
1443 </dd>
1444 <dd class="break"></dd>
1445 <dt>U-C 2:</dt>
1446 <dd style="margin-left: 4.0em" id="section-3.1-1.2">Providing non-critical information to a user about the reason for a state
1447 update in a video chat or conference, such as mute state.<a href="#section-3.1-1.2" class="pilcrow">¶</a>
1448 </dd>
1449 <dd class="break"></dd>
1450 </dl>
1451 </section>
1452 </div>
1453 <div id="sec-use-cases-reliable">
1454 <section id="section-3.2">
1455 <h3 id="name-use-cases-for-reliable-data">
1456 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-use-cases-for-reliable-data" class="section-name selfRef">Use Cases for Reliable Data Channels</a>
1457 </h3>
1458 <span class="break"></span><dl class="olPercent" id="section-3.2-1">
1459 <dt>U-C 3:</dt>
1460 <dd style="margin-left: 4.0em" id="section-3.2-1.1"> A real-time game where critical state information needs to be
1461 transferred, such as control information.
1462 Such a game may have no SRTP media channels, or they may be inactive at any
1463 given time or may only be added due to in-game actions.<a href="#section-3.2-1.1" class="pilcrow">¶</a>
1464 </dd>
1465 <dd class="break"></dd>
1466 <dt>U-C 4:</dt>
1467 <dd style="margin-left: 4.0em" id="section-3.2-1.2">Non-real-time file transfers between people chatting.
1468 Note that this may involve a large number of files to transfer sequentially
1469 or in parallel, such as when sharing a folder of images or a directory of files.<a href="#section-3.2-1.2" class="pilcrow">¶</a>
1470 </dd>
1471 <dd class="break"></dd>
1472 <dt>U-C 5:</dt>
1473 <dd style="margin-left: 4.0em" id="section-3.2-1.3">Real-time text chat during an audio and/or video call with an individual
1474 or with multiple people in a conference.<a href="#section-3.2-1.3" class="pilcrow">¶</a>
1475 </dd>
1476 <dd class="break"></dd>
1477 <dt>U-C 6:</dt>
1478 <dd style="margin-left: 4.0em" id="section-3.2-1.4">Renegotiation of the configuration of the PeerConnection.<a href="#section-3.2-1.4" class="pilcrow">¶</a>
1479 </dd>
1480 <dd class="break"></dd>
1481 <dt>U-C 7:</dt>
1482 <dd style="margin-left: 4.0em" id="section-3.2-1.5">Proxy browsing, where a browser uses data channels of a PeerConnection
1483 to send and receive HTTP/HTTPS requests and data, for example, to avoid local
1484 Internet filtering or monitoring.<a href="#section-3.2-1.5" class="pilcrow">¶</a>
1485 </dd>
1486 <dd class="break"></dd>
1487 </dl>
1488 </section>
1489 </div>
1490 </section>
1491 </div>
1492 <div id="sec-req">
1493 <section id="section-4">
1494 <h2 id="name-requirements">
1495 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-requirements" class="section-name selfRef">Requirements</a>
1496 </h2>
1497 <p id="section-4-1">This section lists the requirements for Peer-to-Peer (P2P) data channels between
1498 two browsers.
1499 Please note that this section is informational only.<a href="#section-4-1" class="pilcrow">¶</a></p>
1500 <span class="break"></span><dl class="olPercent" id="section-4-2">
1501 <dt>Req. 1:</dt>
1502 <dd style="margin-left: 5.0em" id="section-4-2.1">Multiple simultaneous data channels must be supported.
1503 Note that there may be zero or more SRTP media streams in parallel with the data
1504 channels in the same PeerConnection, and the number and state (active/inactive)
1505 of these SRTP media streams may change at any time.<a href="#section-4-2.1" class="pilcrow">¶</a>
1506 </dd>
1507 <dd class="break"></dd>
1508 <dt>Req. 2:</dt>
1509 <dd style="margin-left: 5.0em" id="section-4-2.2">Both reliable and unreliable data channels must be supported.<a href="#section-4-2.2" class="pilcrow">¶</a>
1510 </dd>
1511 <dd class="break"></dd>
1512 <dt>Req. 3:</dt>
1513 <dd style="margin-left: 5.0em" id="section-4-2.3">Data channels of a PeerConnection must be congestion controlled
1514 either individually, as a class, or in conjunction with the SRTP media streams
1515 of the PeerConnection. This ensures that data channels don't cause congestion
1516 problems for these SRTP media streams, and that the WebRTC PeerConnection does
1517 not cause excessive problems when run in parallel with TCP connections.<a href="#section-4-2.3" class="pilcrow">¶</a>
1518 </dd>
1519 <dd class="break"></dd>
1520 <dt>Req. 4:</dt>
1521 <dd style="margin-left: 5.0em" id="section-4-2.4">The application should be able to provide guidance as to the
1522 relative priority of each data channel relative to each other
1523 and relative to the SRTP media streams.
1524 This will interact with the congestion control algorithms.<a href="#section-4-2.4" class="pilcrow">¶</a>
1525 </dd>
1526 <dd class="break"></dd>
1527 <dt>Req. 5:</dt>
1528 <dd style="margin-left: 5.0em" id="section-4-2.5">Data channels must be secured, which allows for confidentiality,
1529 integrity, and source authentication.
1530 See <span>[<a href="#RFC8826" class="xref">RFC8826</a>]</span> and
1531 <span>[<a href="#RFC8827" class="xref">RFC8827</a>]</span> for detailed information.<a href="#section-4-2.5" class="pilcrow">¶</a>
1532 </dd>
1533 <dd class="break"></dd>
1534 <dt>Req. 6:</dt>
1535 <dd style="margin-left: 5.0em" id="section-4-2.6">Data channels must provide message fragmentation support such that
1536 IP-layer fragmentation can be avoided no matter how large a message the
1537 JavaScript application passes to be sent. It also must ensure that large
1538 data channel transfers don't unduly delay traffic on other data
1539 channels.<a href="#section-4-2.6" class="pilcrow">¶</a>
1540 </dd>
1541 <dd class="break"></dd>
1542 <dt>Req. 7:</dt>
1543 <dd style="margin-left: 5.0em" id="section-4-2.7">The data channel transport protocol must not encode local IP addresses
1544 inside its protocol fields; doing so reveals potentially private information
1545 and leads to failure if the address is depended upon.<a href="#section-4-2.7" class="pilcrow">¶</a>
1546 </dd>
1547 <dd class="break"></dd>
1548 <dt>Req. 8:</dt>
1549 <dd style="margin-left: 5.0em" id="section-4-2.8">The data channel transport protocol should support unbounded-length "messages"
1550 (i.e., a virtual socket stream) at the application layer for such things as
1551 image-file-transfer; implementations might enforce a reasonable message size
1552 limit.<a href="#section-4-2.8" class="pilcrow">¶</a>
1553 </dd>
1554 <dd class="break"></dd>
1555 <dt>Req. 9:</dt>
1556 <dd style="margin-left: 5.0em" id="section-4-2.9">The data channel transport protocol should avoid IP fragmentation. It
1557 must support Path MTU (PMTU) discovery and must not rely on ICMP or ICMPv6
1558 being generated or being passed back, especially for PMTU discovery.<a href="#section-4-2.9" class="pilcrow">¶</a>
1559 </dd>
1560 <dd class="break"></dd>
1561 <dt>Req. 10:</dt>
1562 <dd style="margin-left: 5.0em" id="section-4-2.10">It must be possible to implement the protocol stack in the user application space.<a href="#section-4-2.10" class="pilcrow">¶</a>
1563 </dd>
1564 <dd class="break"></dd>
1565 </dl>
1566 </section>
1567 </div>
1568 <div id="sec-p-a-2">
1569 <section id="section-5">
1570 <h2 id="name-sctp-over-dtls-over-udp-con">
1571 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-sctp-over-dtls-over-udp-con" class="section-name selfRef">SCTP over DTLS over UDP Considerations</a>
1572 </h2>
1573 <p id="section-5-1">The important features of SCTP in the WebRTC context are the following:<a href="#section-5-1" class="pilcrow">¶</a></p>
1574 <ul class="normal">
1575 <li class="normal" id="section-5-2.1">Usage of TCP-friendly congestion control.<a href="#section-5-2.1" class="pilcrow">¶</a>
1576 </li>
1577 <li class="normal" id="section-5-2.2">modifiable congestion control for integration with the
1578 SRTP media stream congestion control.<a href="#section-5-2.2" class="pilcrow">¶</a>
1579 </li>
1580 <li class="normal" id="section-5-2.3">Support of multiple unidirectional streams, each providing its own
1581 notion of ordered message delivery.<a href="#section-5-2.3" class="pilcrow">¶</a>
1582 </li>
1583 <li class="normal" id="section-5-2.4">Support of ordered and out-of-order message delivery.<a href="#section-5-2.4" class="pilcrow">¶</a>
1584 </li>
1585 <li class="normal" id="section-5-2.5">Support of arbitrarily large user messages by providing fragmentation
1586 and reassembly.<a href="#section-5-2.5" class="pilcrow">¶</a>
1587 </li>
1588 <li class="normal" id="section-5-2.6">Support of PMTU discovery.<a href="#section-5-2.6" class="pilcrow">¶</a>
1589 </li>
1590 <li class="normal" id="section-5-2.7">Support of reliable or partially reliable message transport.<a href="#section-5-2.7" class="pilcrow">¶</a>
1591 </li>
1592 </ul>
1593 <p id="section-5-3">The WebRTC data channel mechanism does not support SCTP multihoming.
1594 The SCTP layer will simply act as if it were running on a single-homed host,
1595 since that is the abstraction that the DTLS layer (a connection-oriented,
1596 unreliable datagram service) exposes.<a href="#section-5-3" class="pilcrow">¶</a></p>
1597 <p id="section-5-4">The encapsulation of SCTP over DTLS defined in
1598 <span>[<a href="#RFC8261" class="xref">RFC8261</a>]</span> provides confidentiality,
1599 source authentication, and integrity-protected transfers.
1600 Using DTLS over UDP in combination with Interactive Connectivity Establishment
1601 (ICE) <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> enables middlebox traversal
1602 in IPv4- and IPv6-based networks.
1603 SCTP as specified in <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span> <span class="bcp14">MUST</span> be used in
1604 combination with the extension defined in <span>[<a href="#RFC3758" class="xref">RFC3758</a>]</span> and
1605 provides the following features for transporting non-media data between
1606 browsers:<a href="#section-5-4" class="pilcrow">¶</a></p>
1607 <ul class="normal">
1608 <li class="normal" id="section-5-5.1">Support of multiple unidirectional streams.<a href="#section-5-5.1" class="pilcrow">¶</a>
1609 </li>
1610 <li class="normal" id="section-5-5.2">Ordered and unordered delivery of user messages.<a href="#section-5-5.2" class="pilcrow">¶</a>
1611 </li>
1612 <li class="normal" id="section-5-5.3">Reliable and partially reliable transport of user messages.<a href="#section-5-5.3" class="pilcrow">¶</a>
1613 </li>
1614 </ul>
1615 <p id="section-5-6">Each SCTP user message contains a Payload Protocol Identifier (PPID)
1616 that is passed to SCTP by its upper layer on the sending side and
1617 provided to its upper layer on the receiving side.
1618 The PPID can be used to multiplex/demultiplex multiple upper layers over
1619 a single SCTP association.
1620 In the WebRTC context, the PPID is used to distinguish between
1621 UTF-8 encoded user data,
1622 binary-encoded user data, and
1623 the Data Channel Establishment Protocol (DCEP) defined in
1624 <span>[<a href="#RFC8832" class="xref">RFC8832</a>]</span>.
1625 Please note that the PPID is not accessible via the JavaScript API.<a href="#section-5-6" class="pilcrow">¶</a></p>
1626 <p id="section-5-7">The encapsulation of SCTP over DTLS, together with the SCTP features listed
1627 above, satisfies all the requirements listed in <a href="#sec-req" class="xref">Section 4</a>.<a href="#section-5-7" class="pilcrow">¶</a></p>
1628 <p id="section-5-8">The layering of protocols for WebRTC is shown in <a href="#fig-sctp-layering" class="xref">Figure 2</a>.<a href="#section-5-8" class="pilcrow">¶</a></p>
1629 <span id="name-webrtc-protocol-layers"></span><div id="fig-sctp-layering">
1630 <figure id="figure-2">
1631 <div class="artwork art-text alignCenter" id="section-5-9.1">
1632 <pre>
1633 +------+------+------+
1634 | DCEP | UTF-8|Binary|
1635 | | Data | Data |
1636 +------+------+------+
1637 | SCTP |
1638 +----------------------------------+
1639 | STUN | SRTP | DTLS |
1640 +----------------------------------+
1641 | ICE |
1642 +----------------------------------+
1643 | UDP1 | UDP2 | UDP3 | ... |
1644 +----------------------------------+</pre>
1645 </div>
1646 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1647 <a href="#name-webrtc-protocol-layers" class="selfRef">WebRTC Protocol Layers</a>
1648 </figcaption></figure>
1649 </div>
1650 <p id="section-5-10">This stack (especially in contrast to DTLS over SCTP <span>[<a href="#RFC6083" class="xref">RFC6083</a>]</span> and
1651 in combination with SCTP over UDP <span>[<a href="#RFC6951" class="xref">RFC6951</a>]</span>)
1652 has been chosen for the following reasons:<a href="#section-5-10" class="pilcrow">¶</a></p>
1653 <ul class="normal">
1654 <li class="normal" id="section-5-11.1">supports the transmission of arbitrarily large user messages;<a href="#section-5-11.1" class="pilcrow">¶</a>
1655 </li>
1656 <li class="normal" id="section-5-11.2">shares the DTLS connection with the SRTP media channels of the
1657 PeerConnection; and<a href="#section-5-11.2" class="pilcrow">¶</a>
1658 </li>
1659 <li class="normal" id="section-5-11.3">provides privacy for the SCTP control information.<a href="#section-5-11.3" class="pilcrow">¶</a>
1660 </li>
1661 </ul>
1662 <p id="section-5-12">Referring to the protocol stack shown in <a href="#fig-sctp-layering" class="xref">Figure 2</a>:<a href="#section-5-12" class="pilcrow">¶</a></p>
1663 <ul class="normal">
1664 <li class="normal" id="section-5-13.1">the usage of DTLS 1.0 over UDP is specified in <span>[<a href="#RFC4347" class="xref">RFC4347</a>]</span>;<a href="#section-5-13.1" class="pilcrow">¶</a>
1665 </li>
1666 <li class="normal" id="section-5-13.2">the usage of DTLS 1.2 over UDP in specified in <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>;<a href="#section-5-13.2" class="pilcrow">¶</a>
1667 </li>
1668 <li class="normal" id="section-5-13.3">the usage of DTLS 1.3 over UDP is specified in an upcoming document
1669 <span>[<a href="#I-D.ietf-tls-dtls13" class="xref">TLS-DTLS13</a>]</span>; and<a href="#section-5-13.3" class="pilcrow">¶</a>
1670 </li>
1671 <li class="normal" id="section-5-13.4">the usage of SCTP on top of DTLS is specified in
1672 <span>[<a href="#RFC8261" class="xref">RFC8261</a>]</span>.<a href="#section-5-13.4" class="pilcrow">¶</a>
1673 </li>
1674 </ul>
1675 <p id="section-5-14">Please note that the demultiplexing Session Traversal Utilities for NAT (STUN)
1676 <span>[<a href="#RFC5389" class="xref">RFC5389</a>]</span> vs. SRTP vs. DTLS is done
1677 as described in <span><a href="https://www.rfc-editor.org/rfc/rfc5764#section-5.1.2" class="relref">Section 5.1.2</a> of [<a href="#RFC5764" class="xref">RFC5764</a>]</span>, and SCTP
1678 is the only payload of DTLS.<a href="#section-5-14" class="pilcrow">¶</a></p>
1679 <p id="section-5-15">Since DTLS is typically implemented in user application space, the SCTP
1680 stack also needs to be a user application space stack.<a href="#section-5-15" class="pilcrow">¶</a></p>
1681 <p id="section-5-16">The ICE/UDP layer can handle IP address changes during a session without
1682 needing interaction with the DTLS and SCTP layers.
1683 However, SCTP <span class="bcp14">SHOULD</span> be notified when an address change has happened.
1684 In this case, SCTP <span class="bcp14">SHOULD</span> retest the Path MTU and reset the congestion
1685 state to the initial state.
1686 In the case of window-based congestion control like the one specified in
1687 <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span>, this means setting the congestion window and
1688 slow-start threshold to its initial values.<a href="#section-5-16" class="pilcrow">¶</a></p>
1689 <p id="section-5-17">Incoming ICMP or ICMPv6 messages can't be processed by
1690 the SCTP layer, since there is no way to identify the corresponding
1691 association. Therefore, SCTP <span class="bcp14">MUST</span> support performing Path MTU discovery
1692 without relying on ICMP or ICMPv6 as specified in <span>[<a href="#RFC4821" class="xref">RFC4821</a>]</span>
1693 by using probing messages specified in <span>[<a href="#RFC4820" class="xref">RFC4820</a>]</span>.
1694 The initial Path MTU at the IP layer <span class="bcp14">SHOULD NOT</span> exceed 1200 bytes for IPv4
1695 and 1280 bytes for IPv6.<a href="#section-5-17" class="pilcrow">¶</a></p>
1696 <p id="section-5-18">In general, the lower-layer interface of an SCTP implementation should be
1697 adapted to address the differences between IPv4 and IPv6 (being connectionless)
1698 or DTLS (being connection oriented).<a href="#section-5-18" class="pilcrow">¶</a></p>
1699 <p id="section-5-19">When the protocol stack shown in <a href="#fig-sctp-layering" class="xref">Figure 2</a> is used, DTLS
1700 protects the complete SCTP packet, so it provides confidentiality, integrity, and
1701 source authentication of the complete SCTP packet.<a href="#section-5-19" class="pilcrow">¶</a></p>
1702 <p id="section-5-20">SCTP provides congestion control on a per-association basis. This means
1703 that all SCTP streams within a single SCTP association share the same
1704 congestion window. Traffic not being sent over SCTP is not covered by
1705 SCTP congestion control.
1706 Using a congestion control different from the standard one might improve
1707 the impact on the parallel SRTP media streams.<a href="#section-5-20" class="pilcrow">¶</a></p>
1708 <p id="section-5-21">SCTP uses the same port number concept as TCP and UDP.
1709 Therefore, an SCTP association uses two port numbers, one at each SCTP
1710 endpoint.<a href="#section-5-21" class="pilcrow">¶</a></p>
1711 </section>
1712 </div>
1713 <div id="sec-sctp-usage">
1714 <section id="section-6">
1715 <h2 id="name-the-usage-of-sctp-for-data-">
1716 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-the-usage-of-sctp-for-data-" class="section-name selfRef">The Usage of SCTP for Data Channels</a>
1717 </h2>
1718 <section id="section-6.1">
1719 <h3 id="name-sctp-protocol-consideration">
1720 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-sctp-protocol-consideration" class="section-name selfRef">SCTP Protocol Considerations</a>
1721 </h3>
1722 <p id="section-6.1-1">The DTLS encapsulation of SCTP packets as described in
1723 <span>[<a href="#RFC8261" class="xref">RFC8261</a>]</span> <span class="bcp14">MUST</span> be used.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
1724 <p id="section-6.1-2">This SCTP stack and its upper layer <span class="bcp14">MUST</span> support the usage of multiple
1725 SCTP streams.
1726 A user message can be sent ordered or unordered and with partial or full
1727 reliability.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
1728 <p id="section-6.1-3">The following SCTP protocol extensions are required:<a href="#section-6.1-3" class="pilcrow">¶</a></p>
1729 <ul class="normal">
1730 <li class="normal" id="section-6.1-4.1">The stream reconfiguration extension defined in <span>[<a href="#RFC6525" class="xref">RFC6525</a>]</span>
1731 <span class="bcp14">MUST</span> be supported. It is used for closing channels.<a href="#section-6.1-4.1" class="pilcrow">¶</a>
1732 </li>
1733 <li class="normal" id="section-6.1-4.2">The dynamic address reconfiguration extension defined in
1734 <span>[<a href="#RFC5061" class="xref">RFC5061</a>]</span> <span class="bcp14">MUST</span> be used to signal the support of the
1735 stream reset extension defined in <span>[<a href="#RFC6525" class="xref">RFC6525</a>]</span>.
1736 Other features of <span>[<a href="#RFC5061" class="xref">RFC5061</a>]</span> are <span class="bcp14">OPTIONAL</span>.<a href="#section-6.1-4.2" class="pilcrow">¶</a>
1737 </li>
1738 <li class="normal" id="section-6.1-4.3">The partial reliability extension defined in <span>[<a href="#RFC3758" class="xref">RFC3758</a>]</span> <span class="bcp14">MUST</span>
1739 be supported. In addition to the timed reliability PR-SCTP policy defined
1740 in <span>[<a href="#RFC3758" class="xref">RFC3758</a>]</span>, the limited retransmission policy defined in
1741 <span>[<a href="#RFC7496" class="xref">RFC7496</a>]</span> <span class="bcp14">MUST</span> be supported.
1742 Limiting the number of retransmissions to zero, combined with unordered
1743 delivery, provides a UDP-like service where each user message is sent
1744 exactly once and delivered in the order received.<a href="#section-6.1-4.3" class="pilcrow">¶</a>
1745 </li>
1746 </ul>
1747 <p id="section-6.1-5">The support for message interleaving as defined in
1748 <span>[<a href="#RFC8260" class="xref">RFC8260</a>]</span> <span class="bcp14">SHOULD</span> be used.<a href="#section-6.1-5" class="pilcrow">¶</a></p>
1749 </section>
1750 <div id="sec-sctp-management">
1751 <section id="section-6.2">
1752 <h3 id="name-sctp-association-management">
1753 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-sctp-association-management" class="section-name selfRef">SCTP Association Management</a>
1754 </h3>
1755 <p id="section-6.2-1">In the WebRTC context, the SCTP association will be set up when the
1756 two endpoints of the WebRTC PeerConnection agree on opening it, as negotiated
1757 by the JavaScript Session Establishment Protocol (JSEP), which is typically an
1758 exchange of the Session Description Protocol (SDP) <span>[<a href="#RFC8829" class="xref">RFC8829</a>]</span>.
1759 It will use the DTLS connection selected via ICE, and typically this will be
1760 shared via BUNDLE or equivalent with DTLS connections used to key the
1761 SRTP media streams.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
1762 <p id="section-6.2-2">The number of streams negotiated during SCTP association setup <span class="bcp14">SHOULD</span>
1763 be 65535, which is the maximum number of streams that can be negotiated during
1764 the association setup.<a href="#section-6.2-2" class="pilcrow">¶</a></p>
1765 <p id="section-6.2-3">SCTP supports two ways of terminating an SCTP association.
1766 The first method is a graceful one, where a procedure that ensures no messages
1767 are lost during the shutdown of the association is used.
1768 The second method is a non-graceful one, where one side can just abort the
1769 association.<a href="#section-6.2-3" class="pilcrow">¶</a></p>
1770 <p id="section-6.2-4">Each SCTP endpoint continuously supervises the reachability of its peer by
1771 monitoring the number of retransmissions of user messages and test messages.
1772 In case of excessive retransmissions, the association is terminated in a
1773 non-graceful way.<a href="#section-6.2-4" class="pilcrow">¶</a></p>
1774 <p id="section-6.2-5">If an SCTP association is closed in a graceful way, all of its data channels
1775 are closed.
1776 In case of a non-graceful teardown, all data channels are also closed,
1777 but an error indication <span class="bcp14">SHOULD</span> be provided if possible.<a href="#section-6.2-5" class="pilcrow">¶</a></p>
1778 </section>
1779 </div>
1780 <section id="section-6.3">
1781 <h3 id="name-sctp-streams">
1782 <a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-sctp-streams" class="section-name selfRef">SCTP Streams</a>
1783 </h3>
1784 <p id="section-6.3-1">SCTP defines a stream as a unidirectional logical channel existing within
1785 an SCTP association to another SCTP endpoint. The streams are used to
1786 provide the notion of in-sequence delivery and for multiplexing.
1787 Each user message is sent on a particular stream, either ordered or unordered.
1788 Ordering is preserved only for ordered messages sent on the same stream.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
1789 </section>
1790 <section id="section-6.4">
1791 <h3 id="name-data-channel-definition">
1792 <a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-data-channel-definition" class="section-name selfRef">Data Channel Definition</a>
1793 </h3>
1794 <p id="section-6.4-1">Data channels are defined such that their accompanying application-level API
1795 can closely mirror the API for WebSockets, which implies bidirectional streams
1796 of data and a textual field called 'label' used to identify the meaning of the
1797 data channel.<a href="#section-6.4-1" class="pilcrow">¶</a></p>
1798 <p id="section-6.4-2">The realization of a data channel is a pair of one incoming stream and
1799 one outgoing SCTP stream having the same SCTP stream identifier.
1800 How these SCTP stream identifiers are selected is protocol and implementation
1801 dependent. This allows a bidirectional communication.<a href="#section-6.4-2" class="pilcrow">¶</a></p>
1802 <p id="section-6.4-3">Additionally, each data channel has the following properties in each
1803 direction:<a href="#section-6.4-3" class="pilcrow">¶</a></p>
1804 <ul class="normal">
1805 <li class="normal" id="section-6.4-4.1">reliable or unreliable message transmission:
1806 In case of unreliable transmissions, the same level of unreliability is used.
1807 Note that, in SCTP, this is a property of an SCTP user message and not
1808 of an SCTP stream.<a href="#section-6.4-4.1" class="pilcrow">¶</a>
1809 </li>
1810 <li class="normal" id="section-6.4-4.2">in-order or out-of-order message delivery for message sent:
1811 Note that, in SCTP, this is a property of an SCTP user message and not
1812 of an SCTP stream.<a href="#section-6.4-4.2" class="pilcrow">¶</a>
1813 </li>
1814 <li class="normal" id="section-6.4-4.3">a priority, which is a 2-byte unsigned integer:
1815 These priorities <span class="bcp14">MUST</span> be interpreted as weighted-fair-queuing scheduling
1816 priorities per the definition of the corresponding stream scheduler
1817 supporting interleaving in <span>[<a href="#RFC8260" class="xref">RFC8260</a>]</span>.
1818 For use in WebRTC, the values used <span class="bcp14">SHOULD</span> be one of 128 ("below normal"),
1819 256 ("normal"), 512 ("high"), or 1024 ("extra high").<a href="#section-6.4-4.3" class="pilcrow">¶</a>
1820 </li>
1821 <li class="normal" id="section-6.4-4.4">an optional label.<a href="#section-6.4-4.4" class="pilcrow">¶</a>
1822 </li>
1823 <li class="normal" id="section-6.4-4.5">an optional protocol.<a href="#section-6.4-4.5" class="pilcrow">¶</a>
1824 </li>
1825 </ul>
1826 <p id="section-6.4-5">Note that for a data channel being negotiated with the protocol
1827 specified in <span>[<a href="#RFC8832" class="xref">RFC8832</a>]</span>, all of the above
1828 properties are the same in both directions.<a href="#section-6.4-5" class="pilcrow">¶</a></p>
1829 </section>
1830 <section id="section-6.5">
1831 <h3 id="name-opening-a-data-channel">
1832 <a href="#section-6.5" class="section-number selfRef">6.5. </a><a href="#name-opening-a-data-channel" class="section-name selfRef">Opening a Data Channel</a>
1833 </h3>
1834 <p id="section-6.5-1">Data channels can be opened by using negotiation within the SCTP association
1835 (called in-band negotiation) or out-of-band negotiation.
1836 Out-of-band negotiation is defined as any method that results in an agreement
1837 as to the parameters of a channel and the creation thereof.
1838 The details are out of scope of this document. Applications using data
1839 channels need to use the negotiation methods consistently on both endpoints.<a href="#section-6.5-1" class="pilcrow">¶</a></p>
1840 <p id="section-6.5-2">A simple protocol for in-band negotiation is specified in
1841 <span>[<a href="#RFC8832" class="xref">RFC8832</a>]</span>.<a href="#section-6.5-2" class="pilcrow">¶</a></p>
1842 <p id="section-6.5-3">When one side wants to open a channel using out-of-band negotiation, it
1843 picks a stream.
1844 Unless otherwise defined or negotiated, the streams are picked based on
1845 the DTLS role (the client picks even stream identifiers, and
1846 the server picks odd stream identifiers).
1847 However, the application is responsible for avoiding collisions with
1848 existing streams.
1849 If it attempts to reuse a stream that is part of an existing data channel,
1850 the addition <span class="bcp14">MUST</span> fail.
1851 In addition to choosing a stream, the application <span class="bcp14">SHOULD</span> also determine
1852 the options to be used for sending messages.
1853 The application <span class="bcp14">MUST</span> ensure in an application-specific manner that
1854 the application at the peer will also know the selected stream to
1855 be used, as well as the options for sending data from that side.<a href="#section-6.5-3" class="pilcrow">¶</a></p>
1856 </section>
1857 <section id="section-6.6">
1858 <h3 id="name-transferring-user-data-on-a">
1859 <a href="#section-6.6" class="section-number selfRef">6.6. </a><a href="#name-transferring-user-data-on-a" class="section-name selfRef">Transferring User Data on a Data Channel</a>
1860 </h3>
1861 <p id="section-6.6-1">All data sent on a data channel in both directions <span class="bcp14">MUST</span> be sent over the
1862 underlying stream using the reliability defined when the data channel was
1863 opened, unless the options are changed or per-message options are specified
1864 by a higher level.<a href="#section-6.6-1" class="pilcrow">¶</a></p>
1865 <p id="section-6.6-2">The message orientation of SCTP is used to preserve the message boundaries
1866 of user messages. Therefore, senders <span class="bcp14">MUST NOT</span> put more than one application
1867 message into an SCTP user message. Unless the deprecated PPID-based
1868 fragmentation and reassembly is used, the sender <span class="bcp14">MUST</span> include exactly one
1869 application message in each SCTP user message.<a href="#section-6.6-2" class="pilcrow">¶</a></p>
1870 <p id="section-6.6-3">The SCTP Payload Protocol Identifiers (PPIDs) are used to signal the
1871 interpretation of the "payload data". The following PPIDs <span class="bcp14">MUST</span> be used
1872 (see <a href="#sec-IANA" class="xref">Section 8</a>):<a href="#section-6.6-3" class="pilcrow">¶</a></p>
1873 <span class="break"></span><dl class="dlParallel" id="section-6.6-4">
1874 <dt id="section-6.6-4.1">WebRTC String:</dt>
1875 <dd style="margin-left: 1.5em" id="section-6.6-4.2">
1876 to identify a non-empty JavaScript string encoded in UTF-8.<a href="#section-6.6-4.2" class="pilcrow">¶</a>
1877 </dd>
1878 <dd class="break"></dd>
1879 <dt id="section-6.6-4.3">WebRTC String Empty:</dt>
1880 <dd style="margin-left: 1.5em" id="section-6.6-4.4">
1881 to identify an empty JavaScript string encoded in UTF-8.<a href="#section-6.6-4.4" class="pilcrow">¶</a>
1882 </dd>
1883 <dd class="break"></dd>
1884 <dt id="section-6.6-4.5">WebRTC Binary:</dt>
1885 <dd style="margin-left: 1.5em" id="section-6.6-4.6">
1886 to identify non-empty JavaScript binary data
1887 (ArrayBuffer, ArrayBufferView, or Blob).<a href="#section-6.6-4.6" class="pilcrow">¶</a>
1888 </dd>
1889 <dd class="break"></dd>
1890 <dt id="section-6.6-4.7">WebRTC Binary Empty:</dt>
1891 <dd style="margin-left: 1.5em" id="section-6.6-4.8">
1892 to identify empty JavaScript binary data
1893 (ArrayBuffer, ArrayBufferView, or Blob).<a href="#section-6.6-4.8" class="pilcrow">¶</a>
1894 </dd>
1895 <dd class="break"></dd>
1896 </dl>
1897 <p id="section-6.6-5">SCTP does not support the sending of empty user messages. Therefore, if an
1898 empty message has to be sent, the appropriate PPID (WebRTC String Empty or
1899 WebRTC Binary Empty) is used, and the SCTP user message of one zero byte is
1900 sent. When receiving an SCTP user message with one of these PPIDs, the receiver
1901 <span class="bcp14">MUST</span> ignore the SCTP user message and process it as an empty message.<a href="#section-6.6-5" class="pilcrow">¶</a></p>
1902 <p id="section-6.6-6">The usage of the PPIDs "WebRTC String Partial" and "WebRTC Binary Partial"
1903 is deprecated. They were used for a PPID-based fragmentation and reassembly
1904 of user messages belonging to reliable and ordered data channels.<a href="#section-6.6-6" class="pilcrow">¶</a></p>
1905 <p id="section-6.6-7">If a message with an unsupported PPID is received or some error condition
1906 related to the received message is detected by the receiver
1907 (for example, illegal ordering), the receiver <span class="bcp14">SHOULD</span> close the corresponding
1908 data channel. This implies in particular that extensions using additional
1909 PPIDs can't be used without prior negotiation.<a href="#section-6.6-7" class="pilcrow">¶</a></p>
1910 <p id="section-6.6-8">The SCTP base protocol specified in <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span> does not
1911 support the interleaving of user messages. Therefore, sending a large user
1912 message can monopolize the SCTP association.
1913 To overcome this limitation, <span>[<a href="#RFC8260" class="xref">RFC8260</a>]</span>
1914 defines an extension to support message interleaving, which <span class="bcp14">SHOULD</span> be used.
1915 As long as message interleaving is not supported, the sender
1916 <span class="bcp14">SHOULD</span> limit the maximum message size to 16 KB to avoid monopolization.<a href="#section-6.6-8" class="pilcrow">¶</a></p>
1917 <p id="section-6.6-9">It is recommended that the message size be kept within certain size bounds,
1918 as applications will not be able to support arbitrarily large single
1919 messages. This limit has to be negotiated, for example, by using
1920 <span>[<a href="#RFC8841" class="xref">RFC8841</a>]</span>.<a href="#section-6.6-9" class="pilcrow">¶</a></p>
1921 <p id="section-6.6-10">The sender <span class="bcp14">SHOULD</span> disable the Nagle algorithm (see <span>[<a href="#RFC1122" class="xref">RFC1122</a>]</span>)
1922 to minimize the latency.<a href="#section-6.6-10" class="pilcrow">¶</a></p>
1923 </section>
1924 <section id="section-6.7">
1925 <h3 id="name-closing-a-data-channel">
1926 <a href="#section-6.7" class="section-number selfRef">6.7. </a><a href="#name-closing-a-data-channel" class="section-name selfRef">Closing a Data Channel</a>
1927 </h3>
1928 <p id="section-6.7-1">Closing of a data channel <span class="bcp14">MUST</span> be signaled by resetting the corresponding
1929 outgoing streams <span>[<a href="#RFC6525" class="xref">RFC6525</a>]</span>. This means that if one side
1930 decides to close the data channel, it resets the corresponding outgoing stream.
1931 When the peer sees that an incoming stream was reset, it also resets its
1932 corresponding outgoing stream. Once this is completed, the data channel is closed.
1933 Resetting a stream sets the Stream Sequence Numbers (SSNs) of the stream back to
1934 'zero' with a corresponding notification to the application layer
1935 that the reset has been performed. Streams are available for reuse after a reset
1936 has been performed.<a href="#section-6.7-1" class="pilcrow">¶</a></p>
1937 <p id="section-6.7-2"><span>[<a href="#RFC6525" class="xref">RFC6525</a>]</span> also guarantees that all the messages are delivered
1938 (or abandoned) before the stream is reset.<a href="#section-6.7-2" class="pilcrow">¶</a></p>
1939 </section>
1940 </section>
1941 </div>
1942 <div id="sec-security">
1943 <section id="section-7">
1944 <h2 id="name-security-considerations">
1945 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1946 </h2>
1947 <p id="section-7-1">This document does not add any additional considerations to the ones given in
1948 <span>[<a href="#RFC8826" class="xref">RFC8826</a>]</span> and
1949 <span>[<a href="#RFC8827" class="xref">RFC8827</a>]</span>.<a href="#section-7-1" class="pilcrow">¶</a></p>
1950 <p id="section-7-2">It should be noted that a receiver must be prepared for a sender that tries
1951 to send arbitrarily large messages.<a href="#section-7-2" class="pilcrow">¶</a></p>
1952 </section>
1953 </div>
1954 <div id="sec-IANA">
1955 <section id="section-8">
1956 <h2 id="name-iana-considerations">
1957 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1958 </h2>
1959 <p id="section-8-1">This document uses six already registered SCTP Payload Protocol
1960 Identifiers (PPIDs):
1961 "DOMString Last",
1962 "Binary Data Partial",
1963 "Binary Data Last",
1964 "DOMString Partial",
1965 "WebRTC String Empty", and
1966 "WebRTC Binary Empty".
1967 <span>[<a href="#RFC4960" class="xref">RFC4960</a>]</span> creates the "SCTP Payload Protocol Identifiers" registry
1968 from which these identifiers were assigned.
1969 IANA has updated the reference of these six assignments to point
1970 to this document and changed the names of the first four PPIDs.
1971 The corresponding dates remain unchanged.<a href="#section-8-1" class="pilcrow">¶</a></p>
1972 <p id="section-8-2">The six assignments have been updated to read:<a href="#section-8-2" class="pilcrow">¶</a></p>
1973 <table class="center" id="table-1">
1974 <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
1975 <thead>
1976 <tr>
1977 <th class="text-left" rowspan="1" colspan="1">Value</th>
1978 <th class="text-left" rowspan="1" colspan="1">SCTP PPID</th>
1979 <th class="text-left" rowspan="1" colspan="1">Reference</th>
1980 <th class="text-left" rowspan="1" colspan="1">Date</th>
1981 </tr>
1982 </thead>
1983 <tbody>
1984 <tr>
1985 <td class="text-left" rowspan="1" colspan="1">WebRTC String</td>
1986 <td class="text-left" rowspan="1" colspan="1">51</td>
1987 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
1988 <td class="text-left" rowspan="1" colspan="1">2013-09-20</td>
1989 </tr>
1990 <tr>
1991 <td class="text-left" rowspan="1" colspan="1">WebRTC Binary Partial (deprecated)</td>
1992 <td class="text-left" rowspan="1" colspan="1">52</td>
1993 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
1994 <td class="text-left" rowspan="1" colspan="1">2013-09-20</td>
1995 </tr>
1996 <tr>
1997 <td class="text-left" rowspan="1" colspan="1">WebRTC Binary</td>
1998 <td class="text-left" rowspan="1" colspan="1">53</td>
1999 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
2000 <td class="text-left" rowspan="1" colspan="1">2013-09-20</td>
2001 </tr>
2002 <tr>
2003 <td class="text-left" rowspan="1" colspan="1">WebRTC String Partial (deprecated)</td>
2004 <td class="text-left" rowspan="1" colspan="1">54</td>
2005 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
2006 <td class="text-left" rowspan="1" colspan="1">2013-09-20</td>
2007 </tr>
2008 <tr>
2009 <td class="text-left" rowspan="1" colspan="1">WebRTC String Empty</td>
2010 <td class="text-left" rowspan="1" colspan="1">56</td>
2011 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
2012 <td class="text-left" rowspan="1" colspan="1">2014-08-22</td>
2013 </tr>
2014 <tr>
2015 <td class="text-left" rowspan="1" colspan="1">WebRTC Binary Empty</td>
2016 <td class="text-left" rowspan="1" colspan="1">57</td>
2017 <td class="text-left" rowspan="1" colspan="1">RFC 8831</td>
2018 <td class="text-left" rowspan="1" colspan="1">2014-08-22</td>
2019 </tr>
2020 </tbody>
2021 </table>
2022 </section>
2023 </div>
2024 <section id="section-9">
2025 <h2 id="name-references">
2026 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
2027 </h2>
2028 <section id="section-9.1">
2029 <h3 id="name-normative-references">
2030 <a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2031 </h3>
2032 <dl class="references">
2033 <dt id="RFC2119">[RFC2119]</dt>
2034 <dd>
2035 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
2036 <dd class="break"></dd>
2037 <dt id="RFC3758">[RFC3758]</dt>
2038 <dd>
2039 <span class="refAuthor">Stewart, R.</span><span class="refAuthor">, Ramalho, M.</span><span class="refAuthor">, Xie, Q.</span><span class="refAuthor">, Tuexen, M.</span><span class="refAuthor">, and P. Conrad</span>, <span class="refTitle">"Stream Control Transmission Protocol (SCTP) Partial Reliability Extension"</span>, <span class="seriesInfo">RFC 3758</span>, <span class="seriesInfo">DOI 10.17487/RFC3758</span>, <time datetime="2004-05" class="refDate">May 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3758">https://www.rfc-editor.org/info/rfc3758</a>&gt;</span>. </dd>
2040 <dd class="break"></dd>
2041 <dt id="RFC4820">[RFC4820]</dt>
2042 <dd>
2043 <span class="refAuthor">Tuexen, M.</span><span class="refAuthor">, Stewart, R.</span><span class="refAuthor">, and P. Lei</span>, <span class="refTitle">"Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)"</span>, <span class="seriesInfo">RFC 4820</span>, <span class="seriesInfo">DOI 10.17487/RFC4820</span>, <time datetime="2007-03" class="refDate">March 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4820">https://www.rfc-editor.org/info/rfc4820</a>&gt;</span>. </dd>
2044 <dd class="break"></dd>
2045 <dt id="RFC4821">[RFC4821]</dt>
2046 <dd>
2047 <span class="refAuthor">Mathis, M.</span><span class="refAuthor"> and J. Heffner</span>, <span class="refTitle">"Packetization Layer Path MTU Discovery"</span>, <span class="seriesInfo">RFC 4821</span>, <span class="seriesInfo">DOI 10.17487/RFC4821</span>, <time datetime="2007-03" class="refDate">March 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4821">https://www.rfc-editor.org/info/rfc4821</a>&gt;</span>. </dd>
2048 <dd class="break"></dd>
2049 <dt id="RFC4960">[RFC4960]</dt>
2050 <dd>
2051 <span class="refAuthor">Stewart, R., Ed.</span>, <span class="refTitle">"Stream Control Transmission Protocol"</span>, <span class="seriesInfo">RFC 4960</span>, <span class="seriesInfo">DOI 10.17487/RFC4960</span>, <time datetime="2007-09" class="refDate">September 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4960">https://www.rfc-editor.org/info/rfc4960</a>&gt;</span>. </dd>
2052 <dd class="break"></dd>
2053 <dt id="RFC5061">[RFC5061]</dt>
2054 <dd>
2055 <span class="refAuthor">Stewart, R.</span><span class="refAuthor">, Xie, Q.</span><span class="refAuthor">, Tuexen, M.</span><span class="refAuthor">, Maruyama, S.</span><span class="refAuthor">, and M. Kozuka</span>, <span class="refTitle">"Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration"</span>, <span class="seriesInfo">RFC 5061</span>, <span class="seriesInfo">DOI 10.17487/RFC5061</span>, <time datetime="2007-09" class="refDate">September 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5061">https://www.rfc-editor.org/info/rfc5061</a>&gt;</span>. </dd>
2056 <dd class="break"></dd>
2057 <dt id="RFC6525">[RFC6525]</dt>
2058 <dd>
2059 <span class="refAuthor">Stewart, R.</span><span class="refAuthor">, Tuexen, M.</span><span class="refAuthor">, and P. Lei</span>, <span class="refTitle">"Stream Control Transmission Protocol (SCTP) Stream Reconfiguration"</span>, <span class="seriesInfo">RFC 6525</span>, <span class="seriesInfo">DOI 10.17487/RFC6525</span>, <time datetime="2012-02" class="refDate">February 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6525">https://www.rfc-editor.org/info/rfc6525</a>&gt;</span>. </dd>
2060 <dd class="break"></dd>
2061 <dt id="RFC7496">[RFC7496]</dt>
2062 <dd>
2063 <span class="refAuthor">Tuexen, M.</span><span class="refAuthor">, Seggelmann, R.</span><span class="refAuthor">, Stewart, R.</span><span class="refAuthor">, and S. Loreto</span>, <span class="refTitle">"Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension"</span>, <span class="seriesInfo">RFC 7496</span>, <span class="seriesInfo">DOI 10.17487/RFC7496</span>, <time datetime="2015-04" class="refDate">April 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7496">https://www.rfc-editor.org/info/rfc7496</a>&gt;</span>. </dd>
2064 <dd class="break"></dd>
2065 <dt id="RFC8174">[RFC8174]</dt>
2066 <dd>
2067 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
2068 <dd class="break"></dd>
2069 <dt id="RFC8260">[RFC8260]</dt>
2070 <dd>
2071 <span class="refAuthor">Stewart, R.</span><span class="refAuthor">, Tuexen, M.</span><span class="refAuthor">, Loreto, S.</span><span class="refAuthor">, and R. Seggelmann</span>, <span class="refTitle">"Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol"</span>, <span class="seriesInfo">RFC 8260</span>, <span class="seriesInfo">DOI 10.17487/RFC8260</span>, <time datetime="2017-11" class="refDate">November 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8260">https://www.rfc-editor.org/info/rfc8260</a>&gt;</span>. </dd>
2072 <dd class="break"></dd>
2073 <dt id="RFC8261">[RFC8261]</dt>
2074 <dd>
2075 <span class="refAuthor">Tuexen, M.</span><span class="refAuthor">, Stewart, R.</span><span class="refAuthor">, Jesup, R.</span><span class="refAuthor">, and S. Loreto</span>, <span class="refTitle">"Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets"</span>, <span class="seriesInfo">RFC 8261</span>, <span class="seriesInfo">DOI 10.17487/RFC8261</span>, <time datetime="2017-11" class="refDate">November 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8261">https://www.rfc-editor.org/info/rfc8261</a>&gt;</span>. </dd>
2076 <dd class="break"></dd>
2077 <dt id="RFC8445">[RFC8445]</dt>
2078 <dd>
2079 <span class="refAuthor">Keranen, A.</span><span class="refAuthor">, Holmberg, C.</span><span class="refAuthor">, and J. Rosenberg</span>, <span class="refTitle">"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal"</span>, <span class="seriesInfo">RFC 8445</span>, <span class="seriesInfo">DOI 10.17487/RFC8445</span>, <time datetime="2018-07" class="refDate">July 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8445">https://www.rfc-editor.org/info/rfc8445</a>&gt;</span>. </dd>
2080 <dd class="break"></dd>
2081 <dt id="RFC8826">[RFC8826]</dt>
2082 <dd>
2083 <span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"Security Considerations for WebRTC"</span>, <span class="seriesInfo">RFC 8826</span>, <span class="seriesInfo">DOI 10.17487/RFC8826</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8826">https://www.rfc-editor.org/info/rfc8826</a>&gt;</span>. </dd>
2084 <dd class="break"></dd>
2085 <dt id="RFC8827">[RFC8827]</dt>
2086 <dd>
2087 <span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"WebRTC Security Architecture"</span>, <span class="seriesInfo">RFC 8827</span>, <span class="seriesInfo">DOI 10.17487/RFC8827</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8827">https://www.rfc-editor.org/info/rfc8827</a>&gt;</span>. </dd>
2088 <dd class="break"></dd>
2089 <dt id="RFC8829">[RFC8829]</dt>
2090 <dd>
2091 <span class="refAuthor">Uberti, J.</span><span class="refAuthor">, Jennings, C.</span><span class="refAuthor">, and E. Rescorla, Ed.</span>, <span class="refTitle">"JavaScript Session Establishment Protocol (JSEP)"</span>, <span class="seriesInfo">RFC 8829</span>, <span class="seriesInfo">DOI 10.17487/RFC8829</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8829">https://www.rfc-editor.org/info/rfc8829</a>&gt;</span>. </dd>
2092 <dd class="break"></dd>
2093 <dt id="RFC8832">[RFC8832]</dt>
2094 <dd>
2095 <span class="refAuthor">Jesup, R.</span><span class="refAuthor">, Loreto, S.</span><span class="refAuthor">, and M. Tüxen</span>, <span class="refTitle">"WebRTC Data Channel Establishment Protocol"</span>, <span class="seriesInfo">RFC 8832</span>, <span class="seriesInfo">DOI 10.17487/RFC8832</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8832">https://www.rfc-editor.org/info/rfc8832</a>&gt;</span>. </dd>
2096 <dd class="break"></dd>
2097 <dt id="RFC8841">[RFC8841]</dt>
2098 <dd>
2099 <span class="refAuthor">Holmberg, C.</span><span class="refAuthor">, Shpount, R.</span><span class="refAuthor">, Loreto, S.</span><span class="refAuthor">, and G. Camarillo</span>, <span class="refTitle">"Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport"</span>, <span class="seriesInfo">RFC 8841</span>, <span class="seriesInfo">DOI 10.17487/RFC8841</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8841">https://www.rfc-editor.org/info/rfc8841</a>&gt;</span>. </dd>
2100 <dd class="break"></dd>
2101 </dl>
2102 </section>
2103 <section id="section-9.2">
2104 <h3 id="name-informative-references">
2105 <a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2106 </h3>
2107 <dl class="references">
2108 <dt id="RFC1122">[RFC1122]</dt>
2109 <dd>
2110 <span class="refAuthor">Braden, R., Ed.</span>, <span class="refTitle">"Requirements for Internet Hosts - Communication Layers"</span>, <span class="seriesInfo">STD 3</span>, <span class="seriesInfo">RFC 1122</span>, <span class="seriesInfo">DOI 10.17487/RFC1122</span>, <time datetime="1989-10" class="refDate">October 1989</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc1122">https://www.rfc-editor.org/info/rfc1122</a>&gt;</span>. </dd>
2111 <dd class="break"></dd>
2112 <dt id="RFC4347">[RFC4347]</dt>
2113 <dd>
2114 <span class="refAuthor">Rescorla, E.</span><span class="refAuthor"> and N. Modadugu</span>, <span class="refTitle">"Datagram Transport Layer Security"</span>, <span class="seriesInfo">RFC 4347</span>, <span class="seriesInfo">DOI 10.17487/RFC4347</span>, <time datetime="2006-04" class="refDate">April 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4347">https://www.rfc-editor.org/info/rfc4347</a>&gt;</span>. </dd>
2115 <dd class="break"></dd>
2116 <dt id="RFC5389">[RFC5389]</dt>
2117 <dd>
2118 <span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Mahy, R.</span><span class="refAuthor">, Matthews, P.</span><span class="refAuthor">, and D. Wing</span>, <span class="refTitle">"Session Traversal Utilities for NAT (STUN)"</span>, <span class="seriesInfo">RFC 5389</span>, <span class="seriesInfo">DOI 10.17487/RFC5389</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5389">https://www.rfc-editor.org/info/rfc5389</a>&gt;</span>. </dd>
2119 <dd class="break"></dd>
2120 <dt id="RFC5764">[RFC5764]</dt>
2121 <dd>
2122 <span class="refAuthor">McGrew, D.</span><span class="refAuthor"> and E. Rescorla</span>, <span class="refTitle">"Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)"</span>, <span class="seriesInfo">RFC 5764</span>, <span class="seriesInfo">DOI 10.17487/RFC5764</span>, <time datetime="2010-05" class="refDate">May 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5764">https://www.rfc-editor.org/info/rfc5764</a>&gt;</span>. </dd>
2123 <dd class="break"></dd>
2124 <dt id="RFC6083">[RFC6083]</dt>
2125 <dd>
2126 <span class="refAuthor">Tuexen, M.</span><span class="refAuthor">, Seggelmann, R.</span><span class="refAuthor">, and E. Rescorla</span>, <span class="refTitle">"Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)"</span>, <span class="seriesInfo">RFC 6083</span>, <span class="seriesInfo">DOI 10.17487/RFC6083</span>, <time datetime="2011-01" class="refDate">January 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6083">https://www.rfc-editor.org/info/rfc6083</a>&gt;</span>. </dd>
2127 <dd class="break"></dd>
2128 <dt id="RFC6347">[RFC6347]</dt>
2129 <dd>
2130 <span class="refAuthor">Rescorla, E.</span><span class="refAuthor"> and N. Modadugu</span>, <span class="refTitle">"Datagram Transport Layer Security Version 1.2"</span>, <span class="seriesInfo">RFC 6347</span>, <span class="seriesInfo">DOI 10.17487/RFC6347</span>, <time datetime="2012-01" class="refDate">January 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6347">https://www.rfc-editor.org/info/rfc6347</a>&gt;</span>. </dd>
2131 <dd class="break"></dd>
2132 <dt id="RFC6951">[RFC6951]</dt>
2133 <dd>
2134 <span class="refAuthor">Tuexen, M.</span><span class="refAuthor"> and R. Stewart</span>, <span class="refTitle">"UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication"</span>, <span class="seriesInfo">RFC 6951</span>, <span class="seriesInfo">DOI 10.17487/RFC6951</span>, <time datetime="2013-05" class="refDate">May 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6951">https://www.rfc-editor.org/info/rfc6951</a>&gt;</span>. </dd>
2135 <dd class="break"></dd>
2136 <dt id="I-D.ietf-tls-dtls13">[TLS-DTLS13]</dt>
2137 <dd>
2138 <span class="refAuthor">Rescorla, E.</span><span class="refAuthor">, Tschofenig, H.</span><span class="refAuthor">, and N. Modadugu</span>, <span class="refTitle">"The Datagram Transport Layer Security (DTLS) Protocol Version 1.3"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-tls-dtls13-39</span>, <time datetime="2020-11-02" class="refDate">2 November 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-tls-dtls13-39">https://tools.ietf.org/html/draft-ietf-tls-dtls13-39</a>&gt;</span>. </dd>
2139 <dd class="break"></dd>
2140 </dl>
2141 </section>
2142 </section>
2143 <section id="section-appendix.a">
2144 <h2 id="name-acknowledgements">
2145 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
2146 </h2>
2147 <p id="section-appendix.a-1">Many thanks for comments, ideas, and text from <span class="contact-name">Harald Alvestrand</span>, <span class="contact-name">Richard Barnes</span>,
2148 <span class="contact-name">Adam Bergkvist</span>, <span class="contact-name">Alissa Cooper</span>,
2149 <span class="contact-name">Benoit Claise</span>, <span class="contact-name">Spencer Dawkins</span>, <span class="contact-name">Gunnar Hellström</span>, <span class="contact-name">Christer Holmberg</span>, <span class="contact-name">Cullen Jennings</span>,
2150 <span class="contact-name">Paul Kyzivat</span>, <span class="contact-name">Eric Rescorla</span>,
2151 <span class="contact-name">Adam Roach</span>, <span class="contact-name">Irene Rüngeler</span>,
2152 <span class="contact-name">Randall Stewart</span>, <span class="contact-name">Martin Stiemerling</span>, <span class="contact-name">Justin Uberti</span>, and <span class="contact-name">Magnus Westerlund</span>.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
2153 </section>
2154 <div id="authors-addresses">
2155 <section id="section-appendix.b">
2156 <h2 id="name-authors-addresses">
2157 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2158 </h2>
2159 <address class="vcard">
2160 <div dir="auto" class="left"><span class="fn nameRole">Randell Jesup</span></div>
2161 <div dir="auto" class="left"><span class="org">Mozilla</span></div>
2162 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2163 <div class="email">
2164 <span>Email:</span>
2165 <a href="mailto:[email protected]" class="email">[email protected]</a>
2166 </div>
2167 </address>
2168 <address class="vcard">
2169 <div dir="auto" class="left"><span class="fn nameRole">Salvatore Loreto</span></div>
2170 <div dir="auto" class="left"><span class="org">Ericsson</span></div>
2171 <div dir="auto" class="left"><span class="street-address">Hirsalantie 11</span></div>
2172 <div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span>
2173 </div>
2174 <div dir="auto" class="left"><span class="country-name">Finland</span></div>
2175 <div class="email">
2176 <span>Email:</span>
2177 <a href="mailto:[email protected]" class="email">[email protected]</a>
2178 </div>
2179 </address>
2180 <address class="vcard">
2181 <div dir="auto" class="left"><span class="fn nameRole">Michael Tüxen</span></div>
2182 <div dir="auto" class="left"><span class="org">Münster University of Applied Sciences</span></div>
2183 <div dir="auto" class="left"><span class="street-address">Stegerwaldstrasse 39</span></div>
2184 <div dir="auto" class="left">
2185 <span class="postal-code">48565</span> <span class="locality"> Steinfurt</span>
2186 </div>
2187 <div dir="auto" class="left"><span class="country-name">Germany</span></div>
2188 <div class="email">
2189 <span>Email:</span>
2190 <a href="mailto:[email protected]" class="email">[email protected]</a>
2191 </div>
2192 </address>
2193 </section>
2194 </div>
2195 <script>const toc = document.getElementById("toc");
2196 toc.querySelector("h2").addEventListener("click", e => {
2197 toc.classList.toggle("active");
2198 });
2199 toc.querySelector("nav").addEventListener("click", e => {
2200 toc.classList.remove("active");
2201 });
2202 </script>
2203 </body>
2204 </html>