| 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 8856: Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams</title> |
| 8 |
<meta content="Gonzalo Camarillo" name="author"> |
| 9 |
<meta content="Tom Kristensen" name="author"> |
| 10 |
<meta content="Christer Holmberg" name="author"> |
| 11 |
<meta content=" |
| 12 |
This document defines the Session Description Protocol (SDP) |
| 13 |
offer/answer procedures for negotiating and establishing Binary Floor |
| 14 |
Control Protocol (BFCP) streams. |
| 15 |
This document obsoletes RFC 4583. |
| 16 |
" name="description"> |
| 17 |
<meta content="xml2rfc 3.5.0" name="generator"> |
| 18 |
<meta content="floor control" name="keyword"> |
| 19 |
<meta content="BFCP" name="keyword"> |
| 20 |
<meta content="SDP" name="keyword"> |
| 21 |
<meta content="8856" 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="rfc8856.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/rfc8856" rel="alternate"> |
| 1173 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1174 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4583bis-27" 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 8856</td> |
| 1181 |
<td class="center">SDP Format for BFCP Streams</td> |
| 1182 |
<td class="right">January 2021</td> |
| 1183 |
</tr></thead> |
| 1184 |
<tfoot><tr> |
| 1185 |
<td class="left">Camarillo, 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/rfc8856" class="eref">8856</a></dd> |
| 1197 |
<dt class="label-obsoletes">Obsoletes:</dt> |
| 1198 |
<dd class="obsoletes"> |
| 1199 |
<a href="https://www.rfc-editor.org/rfc/rfc4583" class="eref">4583</a> </dd> |
| 1200 |
<dt class="label-category">Category:</dt> |
| 1201 |
<dd class="category">Standards Track</dd> |
| 1202 |
<dt class="label-published">Published:</dt> |
| 1203 |
<dd class="published"> |
| 1204 |
<time datetime="2021-01" class="published">January 2021</time> |
| 1205 |
</dd> |
| 1206 |
<dt class="label-issn">ISSN:</dt> |
| 1207 |
<dd class="issn">2070-1721</dd> |
| 1208 |
<dt class="label-authors">Authors:</dt> |
| 1209 |
<dd class="authors"> |
| 1210 |
<div class="author"> |
| 1211 |
<div class="author-name">G. Camarillo</div> |
| 1212 |
<div class="org">Ericsson</div> |
| 1213 |
</div> |
| 1214 |
<div class="author"> |
| 1215 |
<div class="author-name">T. Kristensen</div> |
| 1216 |
<div class="org">Jotron</div> |
| 1217 |
</div> |
| 1218 |
<div class="author"> |
| 1219 |
<div class="author-name">C. Holmberg</div> |
| 1220 |
<div class="org">Ericsson</div> |
| 1221 |
</div> |
| 1222 |
</dd> |
| 1223 |
</dl> |
| 1224 |
</div> |
| 1225 |
<h1 id="rfcnum">RFC 8856</h1> |
| 1226 |
<h1 id="title">Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams</h1> |
| 1227 |
<section id="section-abstract"> |
| 1228 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1229 |
<p id="section-abstract-1">This document defines the Session Description Protocol (SDP) |
| 1230 |
offer/answer procedures for negotiating and establishing Binary Floor |
| 1231 |
Control Protocol (BFCP) streams.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1232 |
<p id="section-abstract-2">This document obsoletes RFC 4583.<a href="#section-abstract-2" 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/rfc8856">https://www.rfc-editor.org/info/rfc8856</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="ulEmpty toc compact"> |
| 1280 |
<li class="ulEmpty toc 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="ulEmpty toc 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="ulEmpty toc compact" id="section-toc.1-1.3"> |
| 1287 |
<p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>. <a href="#name-floor-control-roles" class="xref">Floor Control Roles</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1288 |
</li> |
| 1289 |
<li class="ulEmpty toc compact" id="section-toc.1-1.4"> |
| 1290 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-fields-in-the-m-line" class="xref">Fields in the "m=" Line</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1291 |
</li> |
| 1292 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5"> |
| 1293 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-sdp-attributes" class="xref">SDP Attributes</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1294 |
<ul class="ulEmpty toc compact"> |
| 1295 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.1"> |
| 1296 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>. <a href="#name-sdp-floorctrl-attribute" class="xref">SDP 'floorctrl' Attribute</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p> |
| 1297 |
</li> |
| 1298 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.2"> |
| 1299 |
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>. <a href="#name-sdp-confid-attribute" class="xref">SDP 'confid' Attribute</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p> |
| 1300 |
</li> |
| 1301 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.3"> |
| 1302 |
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>. <a href="#name-sdp-userid-attribute" class="xref">SDP 'userid' Attribute</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p> |
| 1303 |
</li> |
| 1304 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.4"> |
| 1305 |
<p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>. <a href="#name-sdp-floorid-attribute" class="xref">SDP 'floorid' Attribute</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p> |
| 1306 |
</li> |
| 1307 |
<li class="ulEmpty toc compact" id="section-toc.1-1.5.2.5"> |
| 1308 |
<p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>. <a href="#name-sdp-bfcpver-attribute" class="xref">SDP 'bfcpver' Attribute</a><a href="#section-toc.1-1.5.2.5.1" class="pilcrow">¶</a></p> |
| 1309 |
</li> |
| 1310 |
</ul> |
| 1311 |
</li> |
| 1312 |
<li class="ulEmpty toc compact" id="section-toc.1-1.6"> |
| 1313 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-multiplexing-considerations" class="xref">Multiplexing Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1314 |
</li> |
| 1315 |
<li class="ulEmpty toc compact" id="section-toc.1-1.7"> |
| 1316 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-bfcp-connection-management" class="xref">BFCP Connection Management</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1317 |
<ul class="ulEmpty toc compact"> |
| 1318 |
<li class="ulEmpty toc compact" id="section-toc.1-1.7.2.1"> |
| 1319 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-tcp-connection-management" class="xref">TCP Connection Management</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p> |
| 1320 |
</li> |
| 1321 |
</ul> |
| 1322 |
</li> |
| 1323 |
<li class="ulEmpty toc compact" id="section-toc.1-1.8"> |
| 1324 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-tls-dtls-considerations" class="xref">TLS/DTLS Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1325 |
</li> |
| 1326 |
<li class="ulEmpty toc compact" id="section-toc.1-1.9"> |
| 1327 |
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>. <a href="#name-ice-considerations" class="xref">ICE Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1328 |
</li> |
| 1329 |
<li class="ulEmpty toc compact" id="section-toc.1-1.10"> |
| 1330 |
<p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-sdp-offer-answer-procedures" class="xref">SDP Offer/Answer Procedures</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1331 |
<ul class="ulEmpty toc compact"> |
| 1332 |
<li class="ulEmpty toc compact" id="section-toc.1-1.10.2.1"> |
| 1333 |
<p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>. <a href="#name-generating-the-initial-sdp-" class="xref">Generating the Initial SDP Offer</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p> |
| 1334 |
</li> |
| 1335 |
<li class="ulEmpty toc compact" id="section-toc.1-1.10.2.2"> |
| 1336 |
<p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>. <a href="#name-generating-the-sdp-answer" class="xref">Generating the SDP Answer</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p> |
| 1337 |
</li> |
| 1338 |
<li class="ulEmpty toc compact" id="section-toc.1-1.10.2.3"> |
| 1339 |
<p id="section-toc.1-1.10.2.3.1"><a href="#section-10.3" class="xref">10.3</a>. <a href="#name-offerer-processing-of-the-s" class="xref">Offerer Processing of the SDP Answer</a><a href="#section-toc.1-1.10.2.3.1" class="pilcrow">¶</a></p> |
| 1340 |
</li> |
| 1341 |
<li class="ulEmpty toc compact" id="section-toc.1-1.10.2.4"> |
| 1342 |
<p id="section-toc.1-1.10.2.4.1"><a href="#section-10.4" class="xref">10.4</a>. <a href="#name-modifying-the-session" class="xref">Modifying the Session</a><a href="#section-toc.1-1.10.2.4.1" class="pilcrow">¶</a></p> |
| 1343 |
</li> |
| 1344 |
</ul> |
| 1345 |
</li> |
| 1346 |
<li class="ulEmpty toc compact" id="section-toc.1-1.11"> |
| 1347 |
<p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-examples" class="xref">Examples</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p> |
| 1348 |
</li> |
| 1349 |
<li class="ulEmpty toc compact" id="section-toc.1-1.12"> |
| 1350 |
<p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p> |
| 1351 |
</li> |
| 1352 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13"> |
| 1353 |
<p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p> |
| 1354 |
<ul class="ulEmpty toc compact"> |
| 1355 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.1"> |
| 1356 |
<p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="xref">13.1</a>. <a href="#name-registration-of-sdp-proto-v" class="xref">Registration of SDP 'proto' Values</a><a href="#section-toc.1-1.13.2.1.1" class="pilcrow">¶</a></p> |
| 1357 |
</li> |
| 1358 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.2"> |
| 1359 |
<p id="section-toc.1-1.13.2.2.1"><a href="#section-13.2" class="xref">13.2</a>. <a href="#name-registration-of-the-sdp-flo" class="xref">Registration of the SDP 'floorctrl' Attribute</a><a href="#section-toc.1-1.13.2.2.1" class="pilcrow">¶</a></p> |
| 1360 |
</li> |
| 1361 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.3"> |
| 1362 |
<p id="section-toc.1-1.13.2.3.1"><a href="#section-13.3" class="xref">13.3</a>. <a href="#name-registration-of-the-sdp-con" class="xref">Registration of the SDP 'confid' Attribute</a><a href="#section-toc.1-1.13.2.3.1" class="pilcrow">¶</a></p> |
| 1363 |
</li> |
| 1364 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.4"> |
| 1365 |
<p id="section-toc.1-1.13.2.4.1"><a href="#section-13.4" class="xref">13.4</a>. <a href="#name-registration-of-the-sdp-use" class="xref">Registration of the SDP 'userid' Attribute</a><a href="#section-toc.1-1.13.2.4.1" class="pilcrow">¶</a></p> |
| 1366 |
</li> |
| 1367 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.5"> |
| 1368 |
<p id="section-toc.1-1.13.2.5.1"><a href="#section-13.5" class="xref">13.5</a>. <a href="#name-registration-of-the-sdp-floo" class="xref">Registration of the SDP 'floorid' Attribute</a><a href="#section-toc.1-1.13.2.5.1" class="pilcrow">¶</a></p> |
| 1369 |
</li> |
| 1370 |
<li class="ulEmpty toc compact" id="section-toc.1-1.13.2.6"> |
| 1371 |
<p id="section-toc.1-1.13.2.6.1"><a href="#section-13.6" class="xref">13.6</a>. <a href="#name-registration-of-the-sdp-bfc" class="xref">Registration of the SDP 'bfcpver' Attribute</a><a href="#section-toc.1-1.13.2.6.1" class="pilcrow">¶</a></p> |
| 1372 |
</li> |
| 1373 |
</ul> |
| 1374 |
</li> |
| 1375 |
<li class="ulEmpty toc compact" id="section-toc.1-1.14"> |
| 1376 |
<p id="section-toc.1-1.14.1"><a href="#section-14" class="xref">14</a>. <a href="#name-changes-from-rfc-4583" class="xref">Changes from RFC 4583</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p> |
| 1377 |
</li> |
| 1378 |
<li class="ulEmpty toc compact" id="section-toc.1-1.15"> |
| 1379 |
<p id="section-toc.1-1.15.1"><a href="#section-15" class="xref">15</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p> |
| 1380 |
<ul class="ulEmpty toc compact"> |
| 1381 |
<li class="ulEmpty toc compact" id="section-toc.1-1.15.2.1"> |
| 1382 |
<p id="section-toc.1-1.15.2.1.1"><a href="#section-15.1" class="xref">15.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.15.2.1.1" class="pilcrow">¶</a></p> |
| 1383 |
</li> |
| 1384 |
<li class="ulEmpty toc compact" id="section-toc.1-1.15.2.2"> |
| 1385 |
<p id="section-toc.1-1.15.2.2.1"><a href="#section-15.2" class="xref">15.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.15.2.2.1" class="pilcrow">¶</a></p> |
| 1386 |
</li> |
| 1387 |
</ul> |
| 1388 |
</li> |
| 1389 |
<li class="ulEmpty toc compact" id="section-toc.1-1.16"> |
| 1390 |
<p id="section-toc.1-1.16.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p> |
| 1391 |
</li> |
| 1392 |
<li class="ulEmpty toc compact" id="section-toc.1-1.17"> |
| 1393 |
<p id="section-toc.1-1.17.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.17.1" class="pilcrow">¶</a></p> |
| 1394 |
</li> |
| 1395 |
</ul> |
| 1396 |
</nav> |
| 1397 |
</section> |
| 1398 |
</div> |
| 1399 |
<section id="section-1"> |
| 1400 |
<h2 id="name-introduction"> |
| 1401 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1402 |
</h2> |
| 1403 |
<p id="section-1-1">As discussed in the BFCP (Binary Floor Control Protocol) specification <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>, a |
| 1404 |
given BFCP client needs a set of data in order to establish a BFCP connection to a floor control server. This data includes |
| 1405 |
the transport address of the server, the conference identifier, and the user identifier.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1406 |
<p id="section-1-2">One way for clients to obtain this information is to use a Session |
| 1407 |
Description Protocol (SDP) offer/answer exchange <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>. |
| 1408 |
This document specifies how to encode this information in the SDP session descriptions that are part of such an offer/answer |
| 1409 |
exchange.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1410 |
<p id="section-1-3">User agents typically use the offer/answer model to establish a number of media streams of different types. |
| 1411 |
Following this model, a BFCP connection is described as any other media stream by using an SDP "m=" line, possibly |
| 1412 |
followed by a number of SDP lines that also apply to the BFCP connection.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1413 |
<p id="section-1-4"><a href="#sec_m-line" class="xref">Section 4</a> defines how the field |
| 1414 |
values in an "m=" line representing a BFCP connection are set.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1415 |
<p id="section-1-5"><a href="#sec_attributes" class="xref">Section 5</a> defines SDP attributes that are used when negotiating a BFCP connection.<a href="#section-1-5" class="pilcrow">¶</a></p> |
| 1416 |
<p id="section-1-6"><a href="#sec_mux-cons" class="xref">Section 6</a> defines multiplexing considerations for a BFCP connection.<a href="#section-1-6" class="pilcrow">¶</a></p> |
| 1417 |
<p id="section-1-7"><a href="#sec_bfcp-connection" class="xref">Section 7</a> defines procedures for managing a BFCP connection.<a href="#section-1-7" class="pilcrow">¶</a></p> |
| 1418 |
<p id="section-1-8"><a href="#sec_authentication" class="xref">Section 8</a> defines TLS and DTLS considerations when negotiating a BFCP connection.<a href="#section-1-8" class="pilcrow">¶</a></p> |
| 1419 |
<p id="section-1-9"><a href="#sec_ice-considerations" class="xref">Section 9</a> defines |
| 1420 |
considerations regarding Interactive Connectivity Establishment (ICE) |
| 1421 |
<span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> when negotiating a BFCP connection.<a href="#section-1-9" class="pilcrow">¶</a></p> |
| 1422 |
<p id="section-1-10"><a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a> defines |
| 1423 |
the SDP offer/answer procedures for negotiating a BFCP connection.<a href="#section-1-10" class="pilcrow">¶</a></p> |
| 1424 |
<p id="section-1-11">This document obsoletes RFC 4583 <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span>. <a href="#sec_changes" class="xref">Section 14</a> summarizes the changes |
| 1425 |
from RFC 4583.<a href="#section-1-11" class="pilcrow">¶</a></p> |
| 1426 |
</section> |
| 1427 |
<section id="section-2"> |
| 1428 |
<h2 id="name-conventions"> |
| 1429 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions" class="section-name selfRef">Conventions</a> |
| 1430 |
</h2> |
| 1431 |
<p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", |
| 1432 |
"<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", |
| 1433 |
"<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", |
| 1434 |
"<span class="bcp14">SHOULD NOT</span>", |
| 1435 |
"<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", |
| 1436 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are |
| 1437 |
to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> |
| 1438 |
<span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, |
| 1439 |
as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1440 |
</section> |
| 1441 |
<div id="sec_server-determination"> |
| 1442 |
<section id="section-3"> |
| 1443 |
<h2 id="name-floor-control-roles"> |
| 1444 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-floor-control-roles" class="section-name selfRef">Floor Control Roles</a> |
| 1445 |
</h2> |
| 1446 |
<p id="section-3-1"> |
| 1447 |
When two endpoints establish a BFCP stream, they need to determine which of them acts as a floor control client and which acts as a floor control server.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1448 |
<p id="section-3-2"> |
| 1449 |
Once the roles have been determined, the roles will apply to all BFCP-controlled streams associated with the BFCP stream.<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1450 |
</section> |
| 1451 |
</div> |
| 1452 |
<div id="sec_m-line"> |
| 1453 |
<section id="section-4"> |
| 1454 |
<h2 id="name-fields-in-the-m-line"> |
| 1455 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-fields-in-the-m-line" class="section-name selfRef">Fields in the "m=" Line</a> |
| 1456 |
</h2> |
| 1457 |
<p id="section-4-1">According to the SDP specification <span>[<a href="#RFC8866" class="xref">RFC8866</a>]</span>, the "m=" line format is as follows:<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 1458 |
<div id="section-4-2"> |
| 1459 |
<pre class="sourcecode lang-sdp"> |
| 1460 |
m=<media> <port> <proto> <fmt> ...</pre><a href="#section-4-2" class="pilcrow">¶</a> |
| 1461 |
</div> |
| 1462 |
<p id="section-4-3">This section describes how to generate an "m=" line of an SDP Media Description ("m=" section) describing a BFCP stream.<a href="#section-4-3" class="pilcrow">¶</a></p> |
| 1463 |
<p id="section-4-4">The media field <span class="bcp14">MUST</span> have a value of "application".<a href="#section-4-4" class="pilcrow">¶</a></p> |
| 1464 |
<p id="section-4-5">Depending on the value of the proto field, the port field is set as explained below. A port field value of zero has the standard SDP meaning (i.e., rejection of the media stream), regardless of the proto field.<a href="#section-4-5" class="pilcrow">¶</a></p> |
| 1465 |
<ul class="normal"> |
| 1466 |
<li class="normal" id="section-4-6.1">When TCP is used as the transport, the port field is set following |
| 1467 |
the rules in <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>. Depending on |
| 1468 |
the value of the 'setup' attribute (defined in <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span> and discussed in <a href="#sec_tcp-connection" class="xref">Section 7.1</a>), the port field contains the port to which the remote endpoint will direct BFCP messages, or in the case where the endpoint will initiate the connection towards the remote endpoint, should be set to a value of 9.<a href="#section-4-6.1" class="pilcrow">¶</a> |
| 1469 |
</li> |
| 1470 |
<li class="normal" id="section-4-6.2">When UDP is used as the transport, the port field contains the port to which the remote endpoint will direct BFCP messages, regardless of the value of the 'setup' attribute.<a href="#section-4-6.2" class="pilcrow">¶</a> |
| 1471 |
</li> |
| 1472 |
</ul> |
| 1473 |
<p id="section-4-7">This document defines five values for the proto field: 'TCP/BFCP', 'TCP/DTLS/BFCP', 'TCP/TLS/BFCP', 'UDP/BFCP', and 'UDP/TLS/BFCP'.<a href="#section-4-7" class="pilcrow">¶</a></p> |
| 1474 |
<p id="section-4-8">The proto values are used as described below:<a href="#section-4-8" class="pilcrow">¶</a></p> |
| 1475 |
<ul class="normal"> |
| 1476 |
<li class="normal" id="section-4-9.1">'TCP/BFCP' is used for TCP transport of BFCP without TLS |
| 1477 |
encryption and is backward compatible with endpoints that are compliant with RFC 4583.<a href="#section-4-9.1" class="pilcrow">¶</a> |
| 1478 |
</li> |
| 1479 |
<li class="normal" id="section-4-9.2">'TCP/TLS/BFCP' is used for TCP transport of BFCP with TLS |
| 1480 |
encryption and is backward compatible with endpoints that are |
| 1481 |
compliant with RFC 4583 and support TLS.<a href="#section-4-9.2" class="pilcrow">¶</a> |
| 1482 |
</li> |
| 1483 |
<li class="normal" id="section-4-9.3">'UDP/BFCP' is used for UDP transport of BFCP without DTLS encryption <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>.<a href="#section-4-9.3" class="pilcrow">¶</a> |
| 1484 |
</li> |
| 1485 |
<li class="normal" id="section-4-9.4">'UDP/TLS/BFCP' is used for UDP transport of BFCP with DTLS |
| 1486 |
encryption. This is one of the options when ICE is used (<a href="#sec_ice-considerations" class="xref">Section 9</a>). It can also be used without ICE |
| 1487 |
when backward compatibility with endpoints compliant with RFC 4583 is not required.<a href="#section-4-9.4" class="pilcrow">¶</a> |
| 1488 |
</li> |
| 1489 |
<li class="normal" id="section-4-9.5">'TCP/DTLS/BFCP' is used for TCP transport of BFCP with DTLS encryption, running on top of TCP using the framing method defined in <span>[<a href="#RFC4571" class="xref">RFC4571</a>]</span>, with DTLS packets being |
| 1490 |
sent and received instead of RTP / RTP Control Protocol (RTCP) |
| 1491 |
packets, such that the LENGTH field defined in RFC 4571 precedes |
| 1492 |
each DTLS message. This is one of the options when |
| 1493 |
ICE is used (<a href="#sec_ice-considerations" class="xref">Section 9</a>). It can also be used without ICE when backward |
| 1494 |
compatibility with endpoints compliant with RFC 4583 is not required.<a href="#section-4-9.5" class="pilcrow">¶</a> |
| 1495 |
</li> |
| 1496 |
</ul> |
| 1497 |
<p id="section-4-10">The fmt (format) list is not applicable to BFCP. The fmt list of "m=" lines in the case of any proto field value related to BFCP <span class="bcp14">MUST</span> contain a single "*" character. If the fmt list contains any other value, it <span class="bcp14">MUST</span> be ignored.<a href="#section-4-10" class="pilcrow">¶</a></p> |
| 1498 |
<p id="section-4-11">The following is an example of an "m=" line for a BFCP connection:<a href="#section-4-11" class="pilcrow">¶</a></p> |
| 1499 |
<div id="section-4-12"> |
| 1500 |
<pre class="sourcecode lang-sdp"> |
| 1501 |
m=application 50000 TCP/TLS/BFCP *</pre><a href="#section-4-12" class="pilcrow">¶</a> |
| 1502 |
</div> |
| 1503 |
</section> |
| 1504 |
</div> |
| 1505 |
<div id="sec_attributes"> |
| 1506 |
<section id="section-5"> |
| 1507 |
<h2 id="name-sdp-attributes"> |
| 1508 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-sdp-attributes" class="section-name selfRef">SDP Attributes</a> |
| 1509 |
</h2> |
| 1510 |
<div id="sec_floorctrl-attr"> |
| 1511 |
<section id="section-5.1"> |
| 1512 |
<h3 id="name-sdp-floorctrl-attribute"> |
| 1513 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-sdp-floorctrl-attribute" class="section-name selfRef">SDP 'floorctrl' Attribute</a> |
| 1514 |
</h3> |
| 1515 |
<p id="section-5.1-1"> |
| 1516 |
This section defines the SDP 'floorctrl' media-level attribute. The attribute is used to determine the floor control roles (client and server) for the endpoints associated with |
| 1517 |
the BFCP stream.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 1518 |
<ul class="normal ulEmpty"> |
| 1519 |
<li class="normal ulEmpty" id="section-5.1-2.1"> |
| 1520 |
<span class="break"></span><dl class="dlParallel" id="section-5.1-2.1.1"> |
| 1521 |
<dt id="section-5.1-2.1.1.1">Attribute Name:</dt> |
| 1522 |
<dd style="margin-left: 1.5em" id="section-5.1-2.1.1.2">floorctrl<a href="#section-5.1-2.1.1.2" class="pilcrow">¶</a> |
| 1523 |
</dd> |
| 1524 |
<dd class="break"></dd> |
| 1525 |
<dt id="section-5.1-2.1.1.3">Attribute Value:</dt> |
| 1526 |
<dd style="margin-left: 1.5em" id="section-5.1-2.1.1.4">floor-control<a href="#section-5.1-2.1.1.4" class="pilcrow">¶</a> |
| 1527 |
</dd> |
| 1528 |
<dd class="break"></dd> |
| 1529 |
<dt id="section-5.1-2.1.1.5">Usage Level:</dt> |
| 1530 |
<dd style="margin-left: 1.5em" id="section-5.1-2.1.1.6">media<a href="#section-5.1-2.1.1.6" class="pilcrow">¶</a> |
| 1531 |
</dd> |
| 1532 |
<dd class="break"></dd> |
| 1533 |
<dt id="section-5.1-2.1.1.7">Charset Dependent:</dt> |
| 1534 |
<dd style="margin-left: 1.5em" id="section-5.1-2.1.1.8">No<a href="#section-5.1-2.1.1.8" class="pilcrow">¶</a> |
| 1535 |
</dd> |
| 1536 |
<dd class="break"></dd> |
| 1537 |
<dt id="section-5.1-2.1.1.9">Mux Category:</dt> |
| 1538 |
<dd style="margin-left: 1.5em" id="section-5.1-2.1.1.10">TBD<a href="#section-5.1-2.1.1.10" class="pilcrow">¶</a> |
| 1539 |
</dd> |
| 1540 |
<dd class="break"></dd> |
| 1541 |
</dl> |
| 1542 |
</li> |
| 1543 |
</ul> |
| 1544 |
<p id="section-5.1-3">The Augmented BNF syntax <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> for the attribute is:<a href="#section-5.1-3" class="pilcrow">¶</a></p> |
| 1545 |
<div id="section-5.1-4"> |
| 1546 |
<pre class="sourcecode lang-abnf"> |
| 1547 |
floor-control = role *(SP role) |
| 1548 |
role = "c-only" / "s-only" / "c-s"</pre><a href="#section-5.1-4" class="pilcrow">¶</a> |
| 1549 |
</div> |
| 1550 |
<p id="section-5.1-5">An endpoint includes the attribute to indicate the role(s) it would be willing to perform for the BFCP-controlled media streams:<a href="#section-5.1-5" class="pilcrow">¶</a></p> |
| 1551 |
<ul class="normal ulEmpty"> |
| 1552 |
<li class="normal ulEmpty" id="section-5.1-6.1"> |
| 1553 |
<span class="break"></span><dl class="dlParallel" id="section-5.1-6.1.1"> |
| 1554 |
<dt id="section-5.1-6.1.1.1">c-only:</dt> |
| 1555 |
<dd style="margin-left: 1.5em" id="section-5.1-6.1.1.2">The endpoint is willing to act as a floor control client.<a href="#section-5.1-6.1.1.2" class="pilcrow">¶</a> |
| 1556 |
</dd> |
| 1557 |
<dd class="break"></dd> |
| 1558 |
<dt id="section-5.1-6.1.1.3">s-only:</dt> |
| 1559 |
<dd style="margin-left: 1.5em" id="section-5.1-6.1.1.4">The endpoint is willing to act as a floor control server only.<a href="#section-5.1-6.1.1.4" class="pilcrow">¶</a> |
| 1560 |
</dd> |
| 1561 |
<dd class="break"></dd> |
| 1562 |
</dl> |
| 1563 |
</li> |
| 1564 |
</ul> |
| 1565 |
<p id="section-5.1-7"> |
| 1566 |
When inserted in an offer, the offerer <span class="bcp14">MAY</span> indicate multiple attribute values ("c-only" and "s-only"). When inserted in an answer, the answerer <span class="bcp14">MUST</span> |
| 1567 |
indicate only one attribute value: "c-only" or "s-only". The answerer indicates the role taken by the answerer. The offerer will then take the |
| 1568 |
opposite role.<a href="#section-5.1-7" class="pilcrow">¶</a></p> |
| 1569 |
<p id="section-5.1-8"> |
| 1570 |
In <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span>, there was a third |
| 1571 |
attribute specified, "c-s", which meant that an endpoint was willing |
| 1572 |
to act as both a floor control client and a |
| 1573 |
floor control server at the same time for the BFCP stream, taking different roles for different BFCP-controlled media streams. The feature was underspecified |
| 1574 |
and implemented in different ways; in particular, many implementations |
| 1575 |
interpreted "c-s" to mean that the endpoint is willing to act as |
| 1576 |
either a client or a server |
| 1577 |
(equivalent to "c-only s-only"). An implementation compliant with this specification <span class="bcp14">MUST NOT</span> include the "c-s" 'floorctrl' attribute value in an offer or in an answer |
| 1578 |
but <span class="bcp14">MUST</span> accept the attribute value in an offer and |
| 1579 |
process it as equivalent to "c-only s-only" (or "s-only c-only"). Also, as an implementation compliant with |
| 1580 |
this specification is only allowed to include one role -- either |
| 1581 |
"c-only" or "s-only" -- in an answer, each endpoint will only take one role, and as a result |
| 1582 |
the endpoint will take the same role for each BFCP-controlled media stream associated with the BFCP stream.<a href="#section-5.1-8" class="pilcrow">¶</a></p> |
| 1583 |
<p id="section-5.1-9"> |
| 1584 |
<a href="#tab-roles" class="xref">Table 1</a> shows the roles that the answerer is allowed to take, based on what roles the offerer has |
| 1585 |
indicated that it is willing to take.<a href="#section-5.1-9" class="pilcrow">¶</a></p> |
| 1586 |
<span id="name-roles"></span><div id="tab-roles"> |
| 1587 |
<table class="center" id="table-1"> |
| 1588 |
<caption> |
| 1589 |
<a href="#table-1" class="selfRef">Table 1</a>: |
| 1590 |
<a href="#name-roles" class="selfRef">Roles</a> |
| 1591 |
</caption> |
| 1592 |
<thead> |
| 1593 |
<tr> |
| 1594 |
<th class="text-center" rowspan="1" colspan="1">Offerer</th> |
| 1595 |
<th class="text-center" rowspan="1" colspan="1">Answerer</th> |
| 1596 |
</tr> |
| 1597 |
</thead> |
| 1598 |
<tbody> |
| 1599 |
<tr> |
| 1600 |
<td class="text-center" rowspan="1" colspan="1">c-only</td> |
| 1601 |
<td class="text-center" rowspan="1" colspan="1">s-only</td> |
| 1602 |
</tr> |
| 1603 |
<tr> |
| 1604 |
<td class="text-center" rowspan="1" colspan="1">s-only</td> |
| 1605 |
<td class="text-center" rowspan="1" colspan="1">c-only</td> |
| 1606 |
</tr> |
| 1607 |
<tr> |
| 1608 |
<td class="text-center" rowspan="1" colspan="1">c-s</td> |
| 1609 |
<td class="text-center" rowspan="1" colspan="1">c-only</td> |
| 1610 |
</tr> |
| 1611 |
<tr> |
| 1612 |
<td class="text-center" rowspan="1" colspan="1">c-s</td> |
| 1613 |
<td class="text-center" rowspan="1" colspan="1">s-only</td> |
| 1614 |
</tr> |
| 1615 |
</tbody> |
| 1616 |
</table> |
| 1617 |
</div> |
| 1618 |
<p id="section-5.1-11"> |
| 1619 |
Endpoints compliant with <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> might not include the 'floorctrl' attribute in offers and answers. |
| 1620 |
If the 'floorctrl' attribute is not present, in order to be |
| 1621 |
interoperable with such endpoints, the offerer will act as a floor control client |
| 1622 |
and the answerer will act as a floor control server.<a href="#section-5.1-11" class="pilcrow">¶</a></p> |
| 1623 |
<p id="section-5.1-12"> |
| 1624 |
The SDP Offer/Answer procedures for the 'floorctrl' attribute are defined in <a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a>.<a href="#section-5.1-12" class="pilcrow">¶</a></p> |
| 1625 |
<p id="section-5.1-13">The following is an example of a 'floorctrl' attribute in an offer:<a href="#section-5.1-13" class="pilcrow">¶</a></p> |
| 1626 |
<div id="section-5.1-14"> |
| 1627 |
<pre class="sourcecode lang-sdp"> |
| 1628 |
a=floorctrl:c-only s-only</pre><a href="#section-5.1-14" class="pilcrow">¶</a> |
| 1629 |
</div> |
| 1630 |
</section> |
| 1631 |
</div> |
| 1632 |
<div id="sec_confid-attr"> |
| 1633 |
<section id="section-5.2"> |
| 1634 |
<h3 id="name-sdp-confid-attribute"> |
| 1635 |
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-sdp-confid-attribute" class="section-name selfRef">SDP 'confid' Attribute</a> |
| 1636 |
</h3> |
| 1637 |
<p id="section-5.2-1"> |
| 1638 |
This section defines the SDP 'confid' media-level attribute. The attribute is used by a floor control server |
| 1639 |
to convey the conference ID value to the floor control client, using decimal integer representation.<a href="#section-5.2-1" class="pilcrow">¶</a></p> |
| 1640 |
<ul class="normal ulEmpty"> |
| 1641 |
<li class="normal ulEmpty" id="section-5.2-2.1"> |
| 1642 |
<span class="break"></span><dl class="dlParallel" id="section-5.2-2.1.1"> |
| 1643 |
<dt id="section-5.2-2.1.1.1">Attribute Name:</dt> |
| 1644 |
<dd style="margin-left: 1.5em" id="section-5.2-2.1.1.2">confid<a href="#section-5.2-2.1.1.2" class="pilcrow">¶</a> |
| 1645 |
</dd> |
| 1646 |
<dd class="break"></dd> |
| 1647 |
<dt id="section-5.2-2.1.1.3">Attribute Value:</dt> |
| 1648 |
<dd style="margin-left: 1.5em" id="section-5.2-2.1.1.4">conference-id<a href="#section-5.2-2.1.1.4" class="pilcrow">¶</a> |
| 1649 |
</dd> |
| 1650 |
<dd class="break"></dd> |
| 1651 |
<dt id="section-5.2-2.1.1.5">Usage Level:</dt> |
| 1652 |
<dd style="margin-left: 1.5em" id="section-5.2-2.1.1.6">media<a href="#section-5.2-2.1.1.6" class="pilcrow">¶</a> |
| 1653 |
</dd> |
| 1654 |
<dd class="break"></dd> |
| 1655 |
<dt id="section-5.2-2.1.1.7">Charset Dependent:</dt> |
| 1656 |
<dd style="margin-left: 1.5em" id="section-5.2-2.1.1.8">No<a href="#section-5.2-2.1.1.8" class="pilcrow">¶</a> |
| 1657 |
</dd> |
| 1658 |
<dd class="break"></dd> |
| 1659 |
<dt id="section-5.2-2.1.1.9">Mux Category:</dt> |
| 1660 |
<dd style="margin-left: 1.5em" id="section-5.2-2.1.1.10">TBD<a href="#section-5.2-2.1.1.10" class="pilcrow">¶</a> |
| 1661 |
</dd> |
| 1662 |
<dd class="break"></dd> |
| 1663 |
</dl> |
| 1664 |
</li> |
| 1665 |
</ul> |
| 1666 |
<p id="section-5.2-3">The Augmented BNF syntax <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> for the attribute is:<a href="#section-5.2-3" class="pilcrow">¶</a></p> |
| 1667 |
<div id="section-5.2-4"> |
| 1668 |
<pre class="sourcecode lang-abnf"> |
| 1669 |
conference-id = 1*DIGIT |
| 1670 |
|
| 1671 |
DIGIT = <DIGIT as defined in [RFC5234]></pre><a href="#section-5.2-4" class="pilcrow">¶</a> |
| 1672 |
</div> |
| 1673 |
<p id="section-5.2-5">The maximum value of the attribute is determined by the |
| 1674 |
COMMON-HEADER format <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>.<a href="#section-5.2-5" class="pilcrow">¶</a></p> |
| 1675 |
<p id="section-5.2-6"> |
| 1676 |
The SDP Offer/Answer procedures for the 'confid' attribute are defined in <a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a>.<a href="#section-5.2-6" class="pilcrow">¶</a></p> |
| 1677 |
</section> |
| 1678 |
</div> |
| 1679 |
<div id="sec_userid-attr"> |
| 1680 |
<section id="section-5.3"> |
| 1681 |
<h3 id="name-sdp-userid-attribute"> |
| 1682 |
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-sdp-userid-attribute" class="section-name selfRef">SDP 'userid' Attribute</a> |
| 1683 |
</h3> |
| 1684 |
<p id="section-5.3-1"> |
| 1685 |
This section defines the SDP 'userid' media-level attribute. The attribute is used by a floor control server |
| 1686 |
to convey the user ID value to the floor control client, using decimal integer representation.<a href="#section-5.3-1" class="pilcrow">¶</a></p> |
| 1687 |
<ul class="normal ulEmpty"> |
| 1688 |
<li class="normal ulEmpty" id="section-5.3-2.1"> |
| 1689 |
<span class="break"></span><dl class="dlParallel" id="section-5.3-2.1.1"> |
| 1690 |
<dt id="section-5.3-2.1.1.1">Attribute Name:</dt> |
| 1691 |
<dd style="margin-left: 1.5em" id="section-5.3-2.1.1.2">userid<a href="#section-5.3-2.1.1.2" class="pilcrow">¶</a> |
| 1692 |
</dd> |
| 1693 |
<dd class="break"></dd> |
| 1694 |
<dt id="section-5.3-2.1.1.3">Attribute Value:</dt> |
| 1695 |
<dd style="margin-left: 1.5em" id="section-5.3-2.1.1.4">user-id<a href="#section-5.3-2.1.1.4" class="pilcrow">¶</a> |
| 1696 |
</dd> |
| 1697 |
<dd class="break"></dd> |
| 1698 |
<dt id="section-5.3-2.1.1.5">Usage Level:</dt> |
| 1699 |
<dd style="margin-left: 1.5em" id="section-5.3-2.1.1.6">media<a href="#section-5.3-2.1.1.6" class="pilcrow">¶</a> |
| 1700 |
</dd> |
| 1701 |
<dd class="break"></dd> |
| 1702 |
<dt id="section-5.3-2.1.1.7">Charset Dependent:</dt> |
| 1703 |
<dd style="margin-left: 1.5em" id="section-5.3-2.1.1.8">No<a href="#section-5.3-2.1.1.8" class="pilcrow">¶</a> |
| 1704 |
</dd> |
| 1705 |
<dd class="break"></dd> |
| 1706 |
<dt id="section-5.3-2.1.1.9">Mux Category:</dt> |
| 1707 |
<dd style="margin-left: 1.5em" id="section-5.3-2.1.1.10">TBD<a href="#section-5.3-2.1.1.10" class="pilcrow">¶</a> |
| 1708 |
</dd> |
| 1709 |
<dd class="break"></dd> |
| 1710 |
</dl> |
| 1711 |
</li> |
| 1712 |
</ul> |
| 1713 |
<p id="section-5.3-3">The Augmented BNF syntax <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> for the attribute is:<a href="#section-5.3-3" class="pilcrow">¶</a></p> |
| 1714 |
<div id="section-5.3-4"> |
| 1715 |
<pre class="sourcecode lang-abnf"> |
| 1716 |
user-id = 1*DIGIT |
| 1717 |
|
| 1718 |
DIGIT = <DIGIT as defined in [RFC5234]></pre><a href="#section-5.3-4" class="pilcrow">¶</a> |
| 1719 |
</div> |
| 1720 |
<p id="section-5.3-5">The maximum value of the attribute is determined by the |
| 1721 |
COMMON-HEADER format <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>.<a href="#section-5.3-5" class="pilcrow">¶</a></p> |
| 1722 |
<p id="section-5.3-6"> |
| 1723 |
The SDP Offer/Answer procedures for the 'userid' attribute are defined in <a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a>.<a href="#section-5.3-6" class="pilcrow">¶</a></p> |
| 1724 |
</section> |
| 1725 |
</div> |
| 1726 |
<div id="sec_floorid-attr"> |
| 1727 |
<section id="section-5.4"> |
| 1728 |
<h3 id="name-sdp-floorid-attribute"> |
| 1729 |
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-sdp-floorid-attribute" class="section-name selfRef">SDP 'floorid' Attribute</a> |
| 1730 |
</h3> |
| 1731 |
<p id="section-5.4-1"> |
| 1732 |
This section defines the SDP 'floorid' media-level attribute. The |
| 1733 |
attribute is used to convey a floor identifier, using decimal integer |
| 1734 |
representation, and, optionally, pointers to one or more BFCP-controlled |
| 1735 |
media streams.<a href="#section-5.4-1" class="pilcrow">¶</a></p> |
| 1736 |
<ul class="normal ulEmpty"> |
| 1737 |
<li class="normal ulEmpty" id="section-5.4-2.1"> |
| 1738 |
<span class="break"></span><dl class="dlParallel" id="section-5.4-2.1.1"> |
| 1739 |
<dt id="section-5.4-2.1.1.1">Attribute Name:</dt> |
| 1740 |
<dd style="margin-left: 1.5em" id="section-5.4-2.1.1.2">floorid<a href="#section-5.4-2.1.1.2" class="pilcrow">¶</a> |
| 1741 |
</dd> |
| 1742 |
<dd class="break"></dd> |
| 1743 |
<dt id="section-5.4-2.1.1.3">Attribute Value:</dt> |
| 1744 |
<dd style="margin-left: 1.5em" id="section-5.4-2.1.1.4">floor-id<a href="#section-5.4-2.1.1.4" class="pilcrow">¶</a> |
| 1745 |
</dd> |
| 1746 |
<dd class="break"></dd> |
| 1747 |
<dt id="section-5.4-2.1.1.5">Usage Level:</dt> |
| 1748 |
<dd style="margin-left: 1.5em" id="section-5.4-2.1.1.6">media<a href="#section-5.4-2.1.1.6" class="pilcrow">¶</a> |
| 1749 |
</dd> |
| 1750 |
<dd class="break"></dd> |
| 1751 |
<dt id="section-5.4-2.1.1.7">Charset Dependent:</dt> |
| 1752 |
<dd style="margin-left: 1.5em" id="section-5.4-2.1.1.8">No<a href="#section-5.4-2.1.1.8" class="pilcrow">¶</a> |
| 1753 |
</dd> |
| 1754 |
<dd class="break"></dd> |
| 1755 |
<dt id="section-5.4-2.1.1.9">Mux Category:</dt> |
| 1756 |
<dd style="margin-left: 1.5em" id="section-5.4-2.1.1.10">TBD<a href="#section-5.4-2.1.1.10" class="pilcrow">¶</a> |
| 1757 |
</dd> |
| 1758 |
<dd class="break"></dd> |
| 1759 |
</dl> |
| 1760 |
</li> |
| 1761 |
</ul> |
| 1762 |
<p id="section-5.4-3">The Augmented BNF syntax <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> for the attribute is:<a href="#section-5.4-3" class="pilcrow">¶</a></p> |
| 1763 |
<div id="section-5.4-4"> |
| 1764 |
<pre class="sourcecode lang-abnf"> |
| 1765 |
floor-id = 1*DIGIT SP "mstrm:" token *(SP token) |
| 1766 |
|
| 1767 |
DIGIT = <DIGIT as defined in [RFC5234]> |
| 1768 |
token = <token as defined in [RFC8866]></pre><a href="#section-5.4-4" class="pilcrow">¶</a> |
| 1769 |
</div> |
| 1770 |
<p id="section-5.4-5">The maximum value of the attribute is determined by the |
| 1771 |
FLOOR-ID format <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>.<a href="#section-5.4-5" class="pilcrow">¶</a></p> |
| 1772 |
<p id="section-5.4-6">The floor identifier value is the integer representation of the |
| 1773 |
Floor ID field value <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> to be used in BFCP. Each media stream |
| 1774 |
pointer value is associated with an SDP 'label' attribute <span>[<a href="#RFC4574" class="xref">RFC4574</a>]</span> of a media stream.<a href="#section-5.4-6" class="pilcrow">¶</a></p> |
| 1775 |
<p id="section-5.4-7"> |
| 1776 |
The SDP Offer/Answer procedures for the 'floorid' attribute are defined in <a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a>.<a href="#section-5.4-7" class="pilcrow">¶</a></p> |
| 1777 |
<aside id="section-5.4-8"> |
| 1778 |
<p id="section-5.4-8.1">Note: In the first SDP example in |
| 1779 |
<span><a href="https://www.rfc-editor.org/rfc/rfc4583#section-9" class="relref">Section 9</a> of [<a href="#RFC4583" class="xref">RFC4583</a>]</span>, 'm-stream' |
| 1780 |
was erroneously listed. Although the example was non‑normative, it is |
| 1781 |
implemented by some vendors and occurs in cases where the endpoint is willing to act as a server. Therefore, it is <span class="bcp14">RECOMMENDED</span> to support parsing and |
| 1782 |
interpreting 'm-stream' the same way as 'mstrm' when receiving.<a href="#section-5.4-8.1" class="pilcrow">¶</a></p> |
| 1783 |
</aside> |
| 1784 |
</section> |
| 1785 |
</div> |
| 1786 |
<div id="sec_bfcp-version-attr"> |
| 1787 |
<section id="section-5.5"> |
| 1788 |
<h3 id="name-sdp-bfcpver-attribute"> |
| 1789 |
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-sdp-bfcpver-attribute" class="section-name selfRef">SDP 'bfcpver' Attribute</a> |
| 1790 |
</h3> |
| 1791 |
<p id="section-5.5-1"> |
| 1792 |
This section defines the SDP 'bfcpver' media-level attribute. The |
| 1793 |
attribute is used to negotiate the BFCP version, using decimal integer |
| 1794 |
representation.<a href="#section-5.5-1" class="pilcrow">¶</a></p> |
| 1795 |
<ul class="normal ulEmpty"> |
| 1796 |
<li class="normal ulEmpty" id="section-5.5-2.1"> |
| 1797 |
<span class="break"></span><dl class="dlParallel" id="section-5.5-2.1.1"> |
| 1798 |
<dt id="section-5.5-2.1.1.1">Attribute Name:</dt> |
| 1799 |
<dd style="margin-left: 1.5em" id="section-5.5-2.1.1.2">bfcpver<a href="#section-5.5-2.1.1.2" class="pilcrow">¶</a> |
| 1800 |
</dd> |
| 1801 |
<dd class="break"></dd> |
| 1802 |
<dt id="section-5.5-2.1.1.3">Attribute Value:</dt> |
| 1803 |
<dd style="margin-left: 1.5em" id="section-5.5-2.1.1.4">bfcp-version<a href="#section-5.5-2.1.1.4" class="pilcrow">¶</a> |
| 1804 |
</dd> |
| 1805 |
<dd class="break"></dd> |
| 1806 |
<dt id="section-5.5-2.1.1.5">Usage Level:</dt> |
| 1807 |
<dd style="margin-left: 1.5em" id="section-5.5-2.1.1.6">media<a href="#section-5.5-2.1.1.6" class="pilcrow">¶</a> |
| 1808 |
</dd> |
| 1809 |
<dd class="break"></dd> |
| 1810 |
<dt id="section-5.5-2.1.1.7">Charset Dependent:</dt> |
| 1811 |
<dd style="margin-left: 1.5em" id="section-5.5-2.1.1.8">No<a href="#section-5.5-2.1.1.8" class="pilcrow">¶</a> |
| 1812 |
</dd> |
| 1813 |
<dd class="break"></dd> |
| 1814 |
<dt id="section-5.5-2.1.1.9">Mux Category:</dt> |
| 1815 |
<dd style="margin-left: 1.5em" id="section-5.5-2.1.1.10">TBD<a href="#section-5.5-2.1.1.10" class="pilcrow">¶</a> |
| 1816 |
</dd> |
| 1817 |
<dd class="break"></dd> |
| 1818 |
</dl> |
| 1819 |
</li> |
| 1820 |
</ul> |
| 1821 |
<p id="section-5.5-3">The Augmented BNF syntax <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> for the attribute is:<a href="#section-5.5-3" class="pilcrow">¶</a></p> |
| 1822 |
<div id="section-5.5-4"> |
| 1823 |
<pre class="sourcecode lang-abnf"> |
| 1824 |
bfcp-version = version *(SP version) |
| 1825 |
version = 1*DIGIT |
| 1826 |
|
| 1827 |
DIGIT = <DIGIT as defined in [RFC5234]></pre><a href="#section-5.5-4" class="pilcrow">¶</a> |
| 1828 |
</div> |
| 1829 |
<p id="section-5.5-5">The maximum value of the attribute is determined by the |
| 1830 |
COMMON-HEADER format <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>.<a href="#section-5.5-5" class="pilcrow">¶</a></p> |
| 1831 |
<p id="section-5.5-6"> |
| 1832 |
An endpoint uses the 'bfcpver' attribute to convey the version(s) of BFCP supported by the endpoint, using integer values. For a given version, the attribute |
| 1833 |
value representing the version <span class="bcp14">MUST</span> match the version ("Ver") field that would be presented in the BFCP COMMON‑HEADER <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>. |
| 1834 |
The BFCP version that will eventually be used will be conveyed with a BFCP-level Hello/HelloAck.<a href="#section-5.5-6" class="pilcrow">¶</a></p> |
| 1835 |
<p id="section-5.5-7"> |
| 1836 |
Endpoints compliant with <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> might not always include the 'bfcpver' |
| 1837 |
attribute in offers and answers. The attribute value, if present, <span class="bcp14">MUST</span> be in accordance with |
| 1838 |
the definition of the version ("Ver") field in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>. If the |
| 1839 |
attribute is not present, endpoints <span class="bcp14">MUST</span> assume a default value in accordance with |
| 1840 |
<span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>: when used over a reliable transport, the default |
| 1841 |
attribute value is "1", and when used over an unreliable transport, the default attribute value |
| 1842 |
is "2". The value is inferred from the transport specified in the "m=" line (<a href="#sec_m-line" class="xref">Section 4</a>) |
| 1843 |
of the "m=" section associated with the stream.<a href="#section-5.5-7" class="pilcrow">¶</a></p> |
| 1844 |
<p id="section-5.5-8"> |
| 1845 |
The SDP Offer/Answer procedures for the 'bfcpver' attribute are defined in <a href="#sec_oa-offer-answer-proc" class="xref">Section 10</a>.<a href="#section-5.5-8" class="pilcrow">¶</a></p> |
| 1846 |
</section> |
| 1847 |
</div> |
| 1848 |
</section> |
| 1849 |
</div> |
| 1850 |
<div id="sec_mux-cons"> |
| 1851 |
<section id="section-6"> |
| 1852 |
<h2 id="name-multiplexing-considerations"> |
| 1853 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-multiplexing-considerations" class="section-name selfRef">Multiplexing Considerations</a> |
| 1854 |
</h2> |
| 1855 |
<p id="section-6-1"> |
| 1856 |
<span>[<a href="#RFC8843" class="xref">RFC8843</a>]</span> defines how multiplexing of multiple media streams can be negotiated. This specification does not define |
| 1857 |
how BFCP streams can be multiplexed with other media streams. Therefore, a BFCP stream <span class="bcp14">MUST NOT</span> be associated with a BUNDLE group <span>[<a href="#RFC8843" class="xref">RFC8843</a>]</span>. |
| 1858 |
Note that BFCP-controlled media streams might be multiplexed with other media streams.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 1859 |
<p id="section-6-2"> |
| 1860 |
<span>[<a href="#RFC8859" class="xref">RFC8859</a>]</span> defines the mux categories for the SDP |
| 1861 |
attributes defined in this specification, except for the 'bfcpver' attribute. <a href="#tab_mux-tbd" class="xref">Table 2</a> defines the mux category |
| 1862 |
for the 'bfcpver' attribute:<a href="#section-6-2" class="pilcrow">¶</a></p> |
| 1863 |
<span id="name-multiplexing-attribute-anal"></span><div id="tab_mux-tbd"> |
| 1864 |
<table class="center" id="table-2"> |
| 1865 |
<caption> |
| 1866 |
<a href="#table-2" class="selfRef">Table 2</a>: |
| 1867 |
<a href="#name-multiplexing-attribute-anal" class="selfRef">Multiplexing Attribute Analysis</a> |
| 1868 |
</caption> |
| 1869 |
<thead> |
| 1870 |
<tr> |
| 1871 |
<th class="text-left" rowspan="1" colspan="1">Name</th> |
| 1872 |
<th class="text-left" rowspan="1" colspan="1">Notes</th> |
| 1873 |
<th class="text-left" rowspan="1" colspan="1">Level</th> |
| 1874 |
<th class="text-left" rowspan="1" colspan="1">Mux Category</th> |
| 1875 |
</tr> |
| 1876 |
</thead> |
| 1877 |
<tbody> |
| 1878 |
<tr> |
| 1879 |
<td class="text-left" rowspan="1" colspan="1">bfcpver</td> |
| 1880 |
<td class="text-left" rowspan="1" colspan="1">Needs further analysis in a separate specification</td> |
| 1881 |
<td class="text-left" rowspan="1" colspan="1">M</td> |
| 1882 |
<td class="text-left" rowspan="1" colspan="1">TBD</td> |
| 1883 |
</tr> |
| 1884 |
</tbody> |
| 1885 |
</table> |
| 1886 |
</div> |
| 1887 |
</section> |
| 1888 |
</div> |
| 1889 |
<div id="sec_bfcp-connection"> |
| 1890 |
<section id="section-7"> |
| 1891 |
<h2 id="name-bfcp-connection-management"> |
| 1892 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-bfcp-connection-management" class="section-name selfRef">BFCP Connection Management</a> |
| 1893 |
</h2> |
| 1894 |
<p id="section-7-1"> |
| 1895 |
BFCP streams can use TCP or UDP as the underlying transport. Endpoints exchanging BFCP messages over UDP send the BFCP messages towards the peer |
| 1896 |
using the connection address and port provided in the SDP "c=" and "m=" lines. TCP connection management is more complicated and is described in |
| 1897 |
the following section.<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 1898 |
<aside id="section-7-2"> |
| 1899 |
<p id="section-7-2.1">Note: When using Interactive Connectivity Establishment |
| 1900 |
(ICE) <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, TCP/DTLS/BFCP, or |
| 1901 |
UDP/TLS/BFCP, the straightforward procedures for connection management |
| 1902 |
via UDP/BFCP, as described above, apply. |
| 1903 |
TCP/TLS/BFCP follows the same procedures as TCP/BFCP and is described below.<a href="#section-7-2.1" class="pilcrow">¶</a></p> |
| 1904 |
</aside> |
| 1905 |
<div id="sec_tcp-connection"> |
| 1906 |
<section id="section-7.1"> |
| 1907 |
<h3 id="name-tcp-connection-management"> |
| 1908 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-tcp-connection-management" class="section-name selfRef">TCP Connection Management</a> |
| 1909 |
</h3> |
| 1910 |
<p id="section-7.1-1"> |
| 1911 |
The management of the TCP connection used to transport BFCP messages is performed using the SDP 'setup' and 'connection' attributes <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>. |
| 1912 |
The 'setup' attribute indicates which of the endpoints initiates the TCP connection. The 'connection' attribute handles TCP connection re-establishment.<a href="#section-7.1-1" class="pilcrow">¶</a></p> |
| 1913 |
<p id="section-7.1-2"> |
| 1914 |
The BFCP specification <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> describes a number of situations when the TCP connection between a floor control client |
| 1915 |
and the floor control server needs to be re-established. However, |
| 1916 |
<span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> does not describe the re-establishment |
| 1917 |
process, because this process |
| 1918 |
depends on how the connection was established in the first |
| 1919 |
place. Endpoints using the offer/answer mechanism follow the following |
| 1920 |
rules.<a href="#section-7.1-2" class="pilcrow">¶</a></p> |
| 1921 |
<p id="section-7.1-3"> |
| 1922 |
When the existing TCP connection is closed and re-established following the rules in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>, the floor control client |
| 1923 |
<span class="bcp14">MUST</span> send an offer towards the floor control server in order to re-establish the connection. If a TCP connection cannot deliver a BFCP message and times out, |
| 1924 |
the endpoint that attempted to send the message (i.e., the one that detected the TCP timeout) <span class="bcp14">MUST</span> send an offer in order to re-establish the TCP connection.<a href="#section-7.1-3" class="pilcrow">¶</a></p> |
| 1925 |
<p id="section-7.1-4"> |
| 1926 |
Endpoints that use the offer/answer mechanism to negotiate TCP connections <span class="bcp14">MUST</span> support the 'setup' and 'connection' attributes.<a href="#section-7.1-4" class="pilcrow">¶</a></p> |
| 1927 |
</section> |
| 1928 |
</div> |
| 1929 |
</section> |
| 1930 |
</div> |
| 1931 |
<div id="sec_authentication"> |
| 1932 |
<section id="section-8"> |
| 1933 |
<h2 id="name-tls-dtls-considerations"> |
| 1934 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-tls-dtls-considerations" class="section-name selfRef">TLS/DTLS Considerations</a> |
| 1935 |
</h2> |
| 1936 |
<p id="section-8-1"> |
| 1937 |
When DTLS is used with UDP, the generic procedures defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8842#section-5" class="relref">Section 5</a> of [<a href="#RFC8842" class="xref">RFC8842</a>]</span> |
| 1938 |
<span class="bcp14">MUST</span> be followed.<a href="#section-8-1" class="pilcrow">¶</a></p> |
| 1939 |
<p id="section-8-2"> |
| 1940 |
When TLS is used with TCP, once the underlying connection is established, the answerer always acts as the TLS server. |
| 1941 |
If the TCP connection is lost, the active endpoint <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> is responsible for re-establishing the TCP connection. Unless a new |
| 1942 |
TLS connection is negotiated, subsequent SDP offers and answers will not impact the previously negotiated TLS roles.<a href="#section-8-2" class="pilcrow">¶</a></p> |
| 1943 |
<aside id="section-8-3"> |
| 1944 |
<p id="section-8-3.1">Note: For TLS, it was decided to keep the original procedures in <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> to determine which endpoint |
| 1945 |
acts as the TLS server, in order to retain backward compatibility.<a href="#section-8-3.1" class="pilcrow">¶</a></p> |
| 1946 |
</aside> |
| 1947 |
</section> |
| 1948 |
</div> |
| 1949 |
<div id="sec_ice-considerations"> |
| 1950 |
<section id="section-9"> |
| 1951 |
<h2 id="name-ice-considerations"> |
| 1952 |
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-ice-considerations" class="section-name selfRef">ICE Considerations</a> |
| 1953 |
</h2> |
| 1954 |
<p id="section-9-1"> |
| 1955 |
Generic SDP offer/answer procedures for ICE are defined in <span>[<a href="#RFC8839" class="xref">RFC8839</a>]</span>.<a href="#section-9-1" class="pilcrow">¶</a></p> |
| 1956 |
<p id="section-9-2"> |
| 1957 |
When BFCP is used with UDP-based ICE candidates <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, the procedures for UDP/TLS/BFCP are used.<a href="#section-9-2" class="pilcrow">¶</a></p> |
| 1958 |
<p id="section-9-3"> |
| 1959 |
When BFCP is used with TCP-based ICE candidates <span>[<a href="#RFC6544" class="xref">RFC6544</a>]</span>, the procedures for TCP/DTLS/BFCP are used.<a href="#section-9-3" class="pilcrow">¶</a></p> |
| 1960 |
<p id="section-9-4"> |
| 1961 |
Based on the procedures defined in <span>[<a href="#RFC8842" class="xref">RFC8842</a>]</span>, endpoints treat all ICE candidate pairs associated with a BFCP stream on top of a DTLS association |
| 1962 |
as part of the same DTLS association. Thus, there will only be one BFCP handshake and one DTLS handshake |
| 1963 |
even if there are multiple valid candidate pairs, and even if BFCP media |
| 1964 |
is shifted between candidate pairs (including switching between UDP |
| 1965 |
candidate pairs and TCP candidate pairs) prior to nomination. If new |
| 1966 |
candidates are added, they will also be part of the same DTLS association.<a href="#section-9-4" class="pilcrow">¶</a></p> |
| 1967 |
<p id="section-9-5"> |
| 1968 |
In order to maximize the likelihood of interoperability between the endpoints, all ICE-enabled BFCP-over-DTLS endpoints <span class="bcp14">SHOULD</span> |
| 1969 |
implement support for UDP/TLS/BFCP.<a href="#section-9-5" class="pilcrow">¶</a></p> |
| 1970 |
<p id="section-9-6"> |
| 1971 |
When an SDP offer or answer conveys multiple ICE candidates for a BFCP stream, UDP-based candidates <span class="bcp14">SHOULD</span> be included and |
| 1972 |
the default candidate <span class="bcp14">SHOULD</span> be chosen from one of those UDP candidates. If UDP transport is used for the default candidate, |
| 1973 |
then the "m=" line proto value <span class="bcp14">MUST</span> be 'UDP/TLS/BFCP'. If TCP transport is used for the default candidate, the "m=" line proto |
| 1974 |
value <span class="bcp14">MUST</span> be 'TCP/DTLS/BFCP'.<a href="#section-9-6" class="pilcrow">¶</a></p> |
| 1975 |
<aside id="section-9-7"> |
| 1976 |
<p id="section-9-7.1">Note: Usage of ICE with protocols other than UDP/TLS/BFCP and TCP/DTLS/BFCP is out of scope for this specification.<a href="#section-9-7.1" class="pilcrow">¶</a></p> |
| 1977 |
</aside> |
| 1978 |
</section> |
| 1979 |
</div> |
| 1980 |
<div id="sec_oa-offer-answer-proc"> |
| 1981 |
<section id="section-10"> |
| 1982 |
<h2 id="name-sdp-offer-answer-procedures"> |
| 1983 |
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-sdp-offer-answer-procedures" class="section-name selfRef">SDP Offer/Answer Procedures</a> |
| 1984 |
</h2> |
| 1985 |
<p id="section-10-1"> |
| 1986 |
This section defines the SDP offer/answer <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> procedures for negotiating and establishing a BFCP stream. |
| 1987 |
Generic procedures for DTLS are defined in <span>[<a href="#RFC8842" class="xref">RFC8842</a>]</span>. Generic procedures for TLS are defined |
| 1988 |
in <span>[<a href="#RFC8122" class="xref">RFC8122</a>]</span>.<a href="#section-10-1" class="pilcrow">¶</a></p> |
| 1989 |
<p id="section-10-2"> |
| 1990 |
This section only defines the BFCP-specific procedures. Unless explicitly stated otherwise, the procedures apply to an "m=" section describing a BFCP stream. |
| 1991 |
If an offer or answer contains multiple "m=" sections describing BFCP streams, the procedures are applied independently to each stream.<a href="#section-10-2" class="pilcrow">¶</a></p> |
| 1992 |
<p id="section-10-3"> |
| 1993 |
Within this document, 'initial offer' refers to the first offer within |
| 1994 |
an SDP session (e.g., a Session Initiation Protocol (SIP) |
| 1995 |
dialog when SIP <span>[<a href="#RFC3261" class="xref">RFC3261</a>]</span> is used to carry SDP) in which the offerer |
| 1996 |
indicates that it wants to negotiate the establishment of a BFCP stream.<a href="#section-10-3" class="pilcrow">¶</a></p> |
| 1997 |
<p id="section-10-4"> |
| 1998 |
If the "m=" line 'proto' value is 'TCP/TLS/BFCP', 'TCP/DTLS/BFCP', or 'UDP/TLS/BFCP', the offerer and answerer follow the generic procedures |
| 1999 |
defined in <span>[<a href="#RFC8122" class="xref">RFC8122</a>]</span>.<a href="#section-10-4" class="pilcrow">¶</a></p> |
| 2000 |
<p id="section-10-5"> |
| 2001 |
If the "m=" line proto value is 'TCP/BFCP', 'TCP/TLS/BFCP', 'TCP/DTLS/TCP', or 'UDP/TLS/BFCP', the offerer and answerer |
| 2002 |
use the SDP 'setup' attribute according to the procedures in <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>.<a href="#section-10-5" class="pilcrow">¶</a></p> |
| 2003 |
<p id="section-10-6"> |
| 2004 |
If the "m=" line proto value is 'TCP/BFCP', 'TCP/TLS/BFCP', or 'TCP/DTLS/BFCP', the offerer and answerer use |
| 2005 |
the SDP 'connection' attribute according to the procedures in <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>.<a href="#section-10-6" class="pilcrow">¶</a></p> |
| 2006 |
<aside id="section-10-7"> |
| 2007 |
<p id="section-10-7.1">Note: The use of source-specific SDP parameters <span>[<a href="#RFC5576" class="xref">RFC5576</a>]</span> is not defined for BFCP streams.<a href="#section-10-7.1" class="pilcrow">¶</a></p> |
| 2008 |
</aside> |
| 2009 |
<div id="oa-gen-initial-offer"> |
| 2010 |
<section id="section-10.1"> |
| 2011 |
<h3 id="name-generating-the-initial-sdp-"> |
| 2012 |
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-generating-the-initial-sdp-" class="section-name selfRef">Generating the Initial SDP Offer</a> |
| 2013 |
</h3> |
| 2014 |
<p id="section-10.1-1"> |
| 2015 |
When the offerer creates an initial offer, the offerer <span class="bcp14">MUST</span> include an SDP 'floorctrl' attribute (<a href="#sec_floorctrl-attr" class="xref">Section 5.1</a>) |
| 2016 |
and an SDP 'bfcpver' attribute (<a href="#sec_bfcp-version-attr" class="xref">Section 5.5</a>) in the "m=" section.<a href="#section-10.1-1" class="pilcrow">¶</a></p> |
| 2017 |
<p id="section-10.1-2"> |
| 2018 |
In addition, if the offerer includes an SDP 'floorctrl' attribute with "s-only" or "c-s" attribute values in the offer, the offerer<a href="#section-10.1-2" class="pilcrow">¶</a></p> |
| 2019 |
<ul class="normal"> |
| 2020 |
<li class="normal" id="section-10.1-3.1"> |
| 2021 |
<span class="bcp14">MUST</span> include an SDP 'confid' attribute (<a href="#sec_confid-attr" class="xref">Section 5.2</a>) in the "m=" section,<a href="#section-10.1-3.1" class="pilcrow">¶</a> |
| 2022 |
</li> |
| 2023 |
<li class="normal" id="section-10.1-3.2"> |
| 2024 |
<span class="bcp14">MUST</span> include an SDP 'userid' attribute (<a href="#sec_userid-attr" class="xref">Section 5.3</a>) in the "m=" section,<a href="#section-10.1-3.2" class="pilcrow">¶</a> |
| 2025 |
</li> |
| 2026 |
<li class="normal" id="section-10.1-3.3"> |
| 2027 |
<span class="bcp14">MUST</span> include an SDP 'floorid' attribute (<a href="#sec_floorid-attr" class="xref">Section 5.4</a>) in the "m=" section, and<a href="#section-10.1-3.3" class="pilcrow">¶</a> |
| 2028 |
</li> |
| 2029 |
<li class="normal" id="section-10.1-3.4"> |
| 2030 |
<span class="bcp14">MUST</span> include an SDP 'label' attribute <span>[<a href="#RFC4574" class="xref">RFC4574</a>]</span> with the "m=" section of each BFCP-controlled media stream.<a href="#section-10.1-3.4" class="pilcrow">¶</a> |
| 2031 |
</li> |
| 2032 |
</ul> |
| 2033 |
<aside id="section-10.1-4"> |
| 2034 |
<p id="section-10.1-4.1">Note: If the offerer includes an SDP 'floorctrl' attribute with a "c-s" attribute value, or both a "c-only" and an "s-only" attribute value in the offer, |
| 2035 |
the attribute values above will only be used if it is determined |
| 2036 |
(<a href="#sec_floorctrl-attr" class="xref">Section 5.1</a>) that the |
| 2037 |
offerer will act as a floor control server.<a href="#section-10.1-4.1" class="pilcrow">¶</a></p> |
| 2038 |
</aside> |
| 2039 |
</section> |
| 2040 |
</div> |
| 2041 |
<div id="oa-gen-answer"> |
| 2042 |
<section id="section-10.2"> |
| 2043 |
<h3 id="name-generating-the-sdp-answer"> |
| 2044 |
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-generating-the-sdp-answer" class="section-name selfRef">Generating the SDP Answer</a> |
| 2045 |
</h3> |
| 2046 |
<p id="section-10.2-1"> |
| 2047 |
When the answerer receives an offer that contains an "m=" section describing a BFCP stream, the answerer <span class="bcp14">MUST</span> check whether it supports |
| 2048 |
one or more of the BFCP versions supported by the offerer (<a href="#sec_bfcp-version-attr" class="xref">Section 5.5</a>). If the answerer does not support |
| 2049 |
any of the BFCP versions, it <span class="bcp14">MUST NOT</span> accept the "m=" |
| 2050 |
section. Otherwise, if the answerer accepts the "m=" section, the answerer<a href="#section-10.2-1" class="pilcrow">¶</a></p> |
| 2051 |
<ul class="normal"> |
| 2052 |
<li class="normal" id="section-10.2-2.1"> |
| 2053 |
<span class="bcp14">MUST</span> insert a corresponding "m=" section in the |
| 2054 |
answer, with an identical "m=" line proto value <span>[<a href="#RFC8866" class="xref">RFC8866</a>]</span>,<a href="#section-10.2-2.1" class="pilcrow">¶</a> |
| 2055 |
</li> |
| 2056 |
<li class="normal" id="section-10.2-2.2"> |
| 2057 |
<span class="bcp14">MUST</span> include a 'bfcpver' attribute in the "m=" section; the versions indicated by the answer <span class="bcp14">MUST</span> be the same or a subset of the versions indicated by the offerer in the corresponding offer, and<a href="#section-10.2-2.2" class="pilcrow">¶</a> |
| 2058 |
</li> |
| 2059 |
<li class="normal" id="section-10.2-2.3"> |
| 2060 |
<span class="bcp14">MUST</span>, if the offer contained an SDP 'floorctrl' attribute, include a 'floorctrl' attribute in the "m=" section.<a href="#section-10.2-2.3" class="pilcrow">¶</a> |
| 2061 |
</li> |
| 2062 |
</ul> |
| 2063 |
<p id="section-10.2-3"> |
| 2064 |
In addition, if the answerer includes an SDP 'floorctrl' attribute with an "s-only" attribute value in the answer, the answerer<a href="#section-10.2-3" class="pilcrow">¶</a></p> |
| 2065 |
<ul class="normal"> |
| 2066 |
<li class="normal" id="section-10.2-4.1"> |
| 2067 |
<span class="bcp14">MUST</span> include an SDP 'confid' attribute in the "m=" section,<a href="#section-10.2-4.1" class="pilcrow">¶</a> |
| 2068 |
</li> |
| 2069 |
<li class="normal" id="section-10.2-4.2"> |
| 2070 |
<span class="bcp14">MUST</span> include an SDP 'userid' attribute in the "m=" section,<a href="#section-10.2-4.2" class="pilcrow">¶</a> |
| 2071 |
</li> |
| 2072 |
<li class="normal" id="section-10.2-4.3"> |
| 2073 |
<span class="bcp14">MUST</span> include an SDP 'floorid' attribute in the "m=" section, and<a href="#section-10.2-4.3" class="pilcrow">¶</a> |
| 2074 |
</li> |
| 2075 |
<li class="normal" id="section-10.2-4.4"> |
| 2076 |
<span class="bcp14">MUST</span> include an SDP 'label' attribute in the "m=" section of each BFCP-controlled media stream.<a href="#section-10.2-4.4" class="pilcrow">¶</a> |
| 2077 |
</li> |
| 2078 |
</ul> |
| 2079 |
<aside id="section-10.2-5"> |
| 2080 |
<p id="section-10.2-5.1">Note: An offerer compliant with <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> might not include 'floorctrl' and 'bfcpver' attributes in offers, in which case |
| 2081 |
the default values apply.<a href="#section-10.2-5.1" class="pilcrow">¶</a></p> |
| 2082 |
</aside> |
| 2083 |
<p id="section-10.2-6"> |
| 2084 |
Once the answerer has sent the answer, the answerer<a href="#section-10.2-6" class="pilcrow">¶</a></p> |
| 2085 |
<ul class="normal"> |
| 2086 |
<li class="normal" id="section-10.2-7.1"> |
| 2087 |
<span class="bcp14">MUST</span>, if the answerer is the active endpoint and if a TCP connection associated with the "m=" section is to be established (or re-established), |
| 2088 |
initiate the establishment of the TCP connection, and<a href="#section-10.2-7.1" class="pilcrow">¶</a> |
| 2089 |
</li> |
| 2090 |
<li class="normal" id="section-10.2-7.2"> |
| 2091 |
<span class="bcp14">MUST</span>, if the answerer is the active endpoint and if a TLS/DTLS connection associated with the "m=" section is to be established (or re-established), |
| 2092 |
initiate the establishment of the TLS/DTLS connection (by sending a ClientHello message).<a href="#section-10.2-7.2" class="pilcrow">¶</a> |
| 2093 |
</li> |
| 2094 |
</ul> |
| 2095 |
<p id="section-10.2-8"> |
| 2096 |
If the answerer does not accept the "m=" section in the offer, it <span class="bcp14">MUST</span> assign a zero port value to the "m=" line of the corresponding "m=" section in the answer. |
| 2097 |
In addition, the answerer <span class="bcp14">MUST NOT</span> establish a TCP connection or a TLS/DTLS connection associated with the "m=" section.<a href="#section-10.2-8" class="pilcrow">¶</a></p> |
| 2098 |
</section> |
| 2099 |
</div> |
| 2100 |
<div id="oa-offerer-processing-answer"> |
| 2101 |
<section id="section-10.3"> |
| 2102 |
<h3 id="name-offerer-processing-of-the-s"> |
| 2103 |
<a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-offerer-processing-of-the-s" class="section-name selfRef">Offerer Processing of the SDP Answer</a> |
| 2104 |
</h3> |
| 2105 |
<p id="section-10.3-1"> |
| 2106 |
When the offerer receives an answer that contains an "m=" section |
| 2107 |
describing a BFCP stream and with a non-zero port value in the |
| 2108 |
"m=" line, the offerer<a href="#section-10.3-1" class="pilcrow">¶</a></p> |
| 2109 |
<ul class="normal"> |
| 2110 |
<li class="normal" id="section-10.3-2.1"> |
| 2111 |
<span class="bcp14">MUST</span>, if the offerer is the active endpoint and if a TCP connection associated with the "m=" section is to be established (or re-established), |
| 2112 |
initiate the establishment of the TCP connection, and<a href="#section-10.3-2.1" class="pilcrow">¶</a> |
| 2113 |
</li> |
| 2114 |
<li class="normal" id="section-10.3-2.2"> |
| 2115 |
<span class="bcp14">MUST</span>, if the offerer is the active endpoint and if a TLS/DTLS connection associated with the "m=" section is to be established (or re-established), |
| 2116 |
initiate the establishment of the TLS/DTLS connection (by sending a ClientHello message).<a href="#section-10.3-2.2" class="pilcrow">¶</a> |
| 2117 |
</li> |
| 2118 |
</ul> |
| 2119 |
<aside id="section-10.3-3"> |
| 2120 |
<p id="section-10.3-3.1">Note: An answerer compliant with <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> might not include 'floorctrl' and 'bfcpver' attributes in answers, |
| 2121 |
in which case the default values apply.<a href="#section-10.3-3.1" class="pilcrow">¶</a></p> |
| 2122 |
</aside> |
| 2123 |
<p id="section-10.3-4"> |
| 2124 |
If the "m=" line in the answer contains a zero port value or if the offerer for some other reason does not accept the answer (e.g., if the answerer only |
| 2125 |
indicates support of BFCP versions not supported by the offerer), the offerer <span class="bcp14">MUST NOT</span> establish a TCP connection or a TLS/DTLS connection associated with the "m=" section.<a href="#section-10.3-4" class="pilcrow">¶</a></p> |
| 2126 |
</section> |
| 2127 |
</div> |
| 2128 |
<div id="oa-mod-session"> |
| 2129 |
<section id="section-10.4"> |
| 2130 |
<h3 id="name-modifying-the-session"> |
| 2131 |
<a href="#section-10.4" class="section-number selfRef">10.4. </a><a href="#name-modifying-the-session" class="section-name selfRef">Modifying the Session</a> |
| 2132 |
</h3> |
| 2133 |
<p id="section-10.4-1"> |
| 2134 |
When an offerer sends an updated offer, in order to modify a previously established BFCP stream, it follows the procedures |
| 2135 |
in <a href="#oa-gen-initial-offer" class="xref">Section 10.1</a>, with the following exceptions:<a href="#section-10.4-1" class="pilcrow">¶</a></p> |
| 2136 |
<ul class="normal"> |
| 2137 |
<li class="normal" id="section-10.4-2.1">If the BFCP stream is carried on top of TCP and if the offerer |
| 2138 |
does not want to re-establish an existing TCP connection, the |
| 2139 |
offerer <span class="bcp14">MUST</span> include in the "m=" section |
| 2140 |
an SDP 'connection' attribute with a value of "existing", and<a href="#section-10.4-2.1" class="pilcrow">¶</a> |
| 2141 |
</li> |
| 2142 |
<li class="normal" id="section-10.4-2.2">If the offerer wants to disable a previously established BFCP stream, it <span class="bcp14">MUST</span> assign a zero port value to the "m=" line associated with the |
| 2143 |
BFCP connection, following the procedures in <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>.<a href="#section-10.4-2.2" class="pilcrow">¶</a> |
| 2144 |
</li> |
| 2145 |
</ul> |
| 2146 |
</section> |
| 2147 |
</div> |
| 2148 |
</section> |
| 2149 |
</div> |
| 2150 |
<div id="sec_example"> |
| 2151 |
<section id="section-11"> |
| 2152 |
<h2 id="name-examples"> |
| 2153 |
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-examples" class="section-name selfRef">Examples</a> |
| 2154 |
</h2> |
| 2155 |
<p id="section-11-1">For the purpose of brevity, the main portion of the session description is omitted in the examples, which only show "m=" sections and their "m=" lines and attributes.<a href="#section-11-1" class="pilcrow">¶</a></p> |
| 2156 |
<p id="section-11-2">The following is an example of an offer sent by a conference server to a client.<a href="#section-11-2" class="pilcrow">¶</a></p> |
| 2157 |
<div id="section-11-3"> |
| 2158 |
<pre class="sourcecode lang-sdp"> |
| 2159 |
m=application 50000 TCP/TLS/BFCP * |
| 2160 |
a=setup:actpass |
| 2161 |
a=connection:new |
| 2162 |
a=fingerprint:sha-256 \ |
| 2163 |
19:E2:1C:3B:4B:9F:81:E6:B8:5C:F4:A5:A8:D8:73:04: \ |
| 2164 |
BB:05:2F:70:9F:04:A9:0E:05:E9:26:33:E8:70:88:A2 |
| 2165 |
a=floorctrl:c-only s-only |
| 2166 |
a=confid:4321 |
| 2167 |
a=userid:1234 |
| 2168 |
a=floorid:1 mstrm:10 |
| 2169 |
a=floorid:2 mstrm:11 |
| 2170 |
a=bfcpver:1 2 |
| 2171 |
m=audio 50002 RTP/AVP 0 |
| 2172 |
a=label:10 |
| 2173 |
m=video 50004 RTP/AVP 31 |
| 2174 |
a=label:11</pre><a href="#section-11-3" class="pilcrow">¶</a> |
| 2175 |
</div> |
| 2176 |
<p id="section-11-4">Note that due to RFC formatting conventions, this document splits the |
| 2177 |
SDP entries across lines whose content would exceed the maximum line |
| 2178 |
length. A backslash character ("\") marks where this line folding has taken place. This backslash and its trailing CRLF and whitespace would not appear in actual SDP content.<a href="#section-11-4" class="pilcrow">¶</a></p> |
| 2179 |
<p id="section-11-5">The following is the answer returned by the client.<a href="#section-11-5" class="pilcrow">¶</a></p> |
| 2180 |
<div id="section-11-6"> |
| 2181 |
<pre class="sourcecode lang-sdp"> |
| 2182 |
m=application 9 TCP/TLS/BFCP * |
| 2183 |
a=setup:active |
| 2184 |
a=connection:new |
| 2185 |
a=fingerprint:sha-256 \ |
| 2186 |
6B:8B:F0:65:5F:78:E2:51:3B:AC:6F:F3:3F:46:1B:35: \ |
| 2187 |
DC:B8:5F:64:1A:24:C2:43:F0:A1:58:D0:A1:2C:19:08 |
| 2188 |
a=floorctrl:c-only |
| 2189 |
a=bfcpver:1 |
| 2190 |
m=audio 55000 RTP/AVP 0 |
| 2191 |
m=video 55002 RTP/AVP 31</pre><a href="#section-11-6" class="pilcrow">¶</a> |
| 2192 |
</div> |
| 2193 |
<p id="section-11-7">A similar example using an unreliable transport and DTLS is shown below, where the offer is sent from a client.<a href="#section-11-7" class="pilcrow">¶</a></p> |
| 2194 |
<div id="section-11-8"> |
| 2195 |
<pre class="sourcecode lang-sdp"> |
| 2196 |
m=application 50000 UDP/TLS/BFCP * |
| 2197 |
a=setup:actpass |
| 2198 |
a=dtls-id:abc3dl |
| 2199 |
a=fingerprint:sha-256 \ |
| 2200 |
19:E2:1C:3B:4B:9F:81:E6:B8:5C:F4:A5:A8:D8:73:04: \ |
| 2201 |
BB:05:2F:70:9F:04:A9:0E:05:E9:26:33:E8:70:88:A2 |
| 2202 |
a=floorctrl:c-only s-only |
| 2203 |
a=confid:4321 |
| 2204 |
a=userid:1234 |
| 2205 |
a=floorid:1 mstrm:10 |
| 2206 |
a=floorid:2 mstrm:11 |
| 2207 |
a=bfcpver:1 2 |
| 2208 |
m=audio 50002 RTP/AVP 0 |
| 2209 |
a=label:10 |
| 2210 |
m=video 50004 RTP/AVP 31 |
| 2211 |
a=label:11</pre><a href="#section-11-8" class="pilcrow">¶</a> |
| 2212 |
</div> |
| 2213 |
<p id="section-11-9">The following is the answer returned by the server.<a href="#section-11-9" class="pilcrow">¶</a></p> |
| 2214 |
<div id="section-11-10"> |
| 2215 |
<pre class="sourcecode lang-sdp"> |
| 2216 |
m=application 55000 UDP/TLS/BFCP * |
| 2217 |
a=setup:active |
| 2218 |
a=dtls-id:abc3dl |
| 2219 |
a=fingerprint:sha-256 \ |
| 2220 |
6B:8B:F0:65:5F:78:E2:51:3B:AC:6F:F3:3F:46:1B:35: \ |
| 2221 |
DC:B8:5F:64:1A:24:C2:43:F0:A1:58:D0:A1:2C:19:08 |
| 2222 |
a=floorctrl:s-only |
| 2223 |
a=confid:4321 |
| 2224 |
a=userid:1234 |
| 2225 |
a=floorid:1 mstrm:10 |
| 2226 |
a=floorid:2 mstrm:11 |
| 2227 |
a=bfcpver:2 |
| 2228 |
m=audio 55002 RTP/AVP 0 |
| 2229 |
m=video 55004 RTP/AVP 31</pre><a href="#section-11-10" class="pilcrow">¶</a> |
| 2230 |
</div> |
| 2231 |
</section> |
| 2232 |
</div> |
| 2233 |
<div id="sec_security"> |
| 2234 |
<section id="section-12"> |
| 2235 |
<h2 id="name-security-considerations"> |
| 2236 |
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2237 |
</h2> |
| 2238 |
<p id="section-12-1">The BFCP specification <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>, SDP |
| 2239 |
specification <span>[<a href="#RFC8866" class="xref">RFC8866</a>]</span>, and |
| 2240 |
offer/answer specification <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> discuss security issues related to BFCP, SDP, and offer/answer, respectively. In addition, <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span> |
| 2241 |
and <span>[<a href="#RFC8122" class="xref">RFC8122</a>]</span> discuss security issues related to the establishment of TCP and TLS connections using an offer/answer |
| 2242 |
model. Furthermore, when using DTLS over UDP, the generic offer/answer considerations defined in |
| 2243 |
<span>[<a href="#RFC8842" class="xref">RFC8842</a>]</span> <span class="bcp14">MUST</span> be followed.<a href="#section-12-1" class="pilcrow">¶</a></p> |
| 2244 |
<p id="section-12-2">The usage of certain proto values in the SDP offer/answer negotiation will result in a BFCP stream that is not protected by |
| 2245 |
TLS or DTLS. Operators will need to provide integrity protection and confidentiality protection of the BFCP stream using other means.<a href="#section-12-2" class="pilcrow">¶</a></p> |
| 2246 |
<p id="section-12-3">The generic security considerations associated with SDP attributes are defined in <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>. While the attributes |
| 2247 |
defined in this specification do not reveal information about the content of individual BFCP-controlled media streams, they do reveal |
| 2248 |
which media streams will be BFCP controlled.<a href="#section-12-3" class="pilcrow">¶</a></p> |
| 2249 |
</section> |
| 2250 |
</div> |
| 2251 |
<div id="sec_iana"> |
| 2252 |
<section id="section-13"> |
| 2253 |
<h2 id="name-iana-considerations"> |
| 2254 |
<a href="#section-13" class="section-number selfRef">13. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2255 |
</h2> |
| 2256 |
<p id="section-13-1">This document registers three new values in the "proto" |
| 2257 |
subregistry within the "Session Description Protocol (SDP) |
| 2258 |
Parameters" registry: 'TCP/DTLS/BFCP', 'UDP/BFCP', and 'UDP/TLS/BFCP' (see <a href="#sec_proto-reg" class="xref">Section 13.1</a>).<a href="#section-13-1" class="pilcrow">¶</a></p> |
| 2259 |
<p id="section-13-2">This document also registers a new SDP attribute in the |
| 2260 |
'attribute-name (formerly "att-field")' |
| 2261 |
subregistry within the "Session Description Protocol (SDP) Parameters" |
| 2262 |
registry: 'bfcpver' (see <a href="#sec_bfcp-version-attr" class="xref">Section 5.5</a>).<a href="#section-13-2" class="pilcrow">¶</a></p> |
| 2263 |
<p id="section-13-3">The remaining values are unchanged from <span>[<a href="#RFC4582" class="xref">RFC4582</a>]</span>, except |
| 2264 |
that the references have been updated to refer to this document.<a href="#section-13-3" class="pilcrow">¶</a></p> |
| 2265 |
<div id="sec_proto-reg"> |
| 2266 |
<section id="section-13.1"> |
| 2267 |
<h3 id="name-registration-of-sdp-proto-v"> |
| 2268 |
<a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-registration-of-sdp-proto-v" class="section-name selfRef">Registration of SDP 'proto' Values</a> |
| 2269 |
</h3> |
| 2270 |
<p id="section-13.1-1">The IANA has registered three new values in the SDP |
| 2271 |
'proto' field under the "Session Description Protocol (SDP) |
| 2272 |
Parameters" registry.<a href="#section-13.1-1" class="pilcrow">¶</a></p> |
| 2273 |
<span id="name-values-for-the-sdp-proto-fi"></span><div id="tab_proto-iana"> |
| 2274 |
<table class="center" id="table-3"> |
| 2275 |
<caption> |
| 2276 |
<a href="#table-3" class="selfRef">Table 3</a>: |
| 2277 |
<a href="#name-values-for-the-sdp-proto-fi" class="selfRef">Values for the SDP 'proto' Field</a> |
| 2278 |
</caption> |
| 2279 |
<thead> |
| 2280 |
<tr> |
| 2281 |
<th class="text-left" rowspan="1" colspan="1">Value</th> |
| 2282 |
<th class="text-center" rowspan="1" colspan="1">Reference</th> |
| 2283 |
</tr> |
| 2284 |
</thead> |
| 2285 |
<tbody> |
| 2286 |
<tr> |
| 2287 |
<td class="text-left" rowspan="1" colspan="1">TCP/BFCP</td> |
| 2288 |
<td class="text-center" rowspan="1" colspan="1">RFC 8856</td> |
| 2289 |
</tr> |
| 2290 |
<tr> |
| 2291 |
<td class="text-left" rowspan="1" colspan="1">TCP/DTLS/BFCP</td> |
| 2292 |
<td class="text-center" rowspan="1" colspan="1">RFC 8856</td> |
| 2293 |
</tr> |
| 2294 |
<tr> |
| 2295 |
<td class="text-left" rowspan="1" colspan="1">TCP/TLS/BFCP</td> |
| 2296 |
<td class="text-center" rowspan="1" colspan="1">RFC 8856</td> |
| 2297 |
</tr> |
| 2298 |
<tr> |
| 2299 |
<td class="text-left" rowspan="1" colspan="1">UDP/BFCP</td> |
| 2300 |
<td class="text-center" rowspan="1" colspan="1">RFC 8856</td> |
| 2301 |
</tr> |
| 2302 |
<tr> |
| 2303 |
<td class="text-left" rowspan="1" colspan="1">UDP/TLS/BFCP</td> |
| 2304 |
<td class="text-center" rowspan="1" colspan="1">RFC 8856</td> |
| 2305 |
</tr> |
| 2306 |
</tbody> |
| 2307 |
</table> |
| 2308 |
</div> |
| 2309 |
</section> |
| 2310 |
</div> |
| 2311 |
<section id="section-13.2"> |
| 2312 |
<h3 id="name-registration-of-the-sdp-flo"> |
| 2313 |
<a href="#section-13.2" class="section-number selfRef">13.2. </a><a href="#name-registration-of-the-sdp-flo" class="section-name selfRef">Registration of the SDP 'floorctrl' Attribute</a> |
| 2314 |
</h3> |
| 2315 |
<p id="section-13.2-1"> |
| 2316 |
This document defines the SDP 'floorctrl' attribute. |
| 2317 |
Details regarding this attribute are provided in <a href="#sec_floorctrl-attr" class="xref">Section 5.1</a>.<a href="#section-13.2-1" class="pilcrow">¶</a></p> |
| 2318 |
</section> |
| 2319 |
<section id="section-13.3"> |
| 2320 |
<h3 id="name-registration-of-the-sdp-con"> |
| 2321 |
<a href="#section-13.3" class="section-number selfRef">13.3. </a><a href="#name-registration-of-the-sdp-con" class="section-name selfRef">Registration of the SDP 'confid' Attribute</a> |
| 2322 |
</h3> |
| 2323 |
<p id="section-13.3-1"> |
| 2324 |
This document defines the SDP 'confid' attribute. |
| 2325 |
Details regarding this attribute are provided in <a href="#sec_confid-attr" class="xref">Section 5.2</a>.<a href="#section-13.3-1" class="pilcrow">¶</a></p> |
| 2326 |
</section> |
| 2327 |
<section id="section-13.4"> |
| 2328 |
<h3 id="name-registration-of-the-sdp-use"> |
| 2329 |
<a href="#section-13.4" class="section-number selfRef">13.4. </a><a href="#name-registration-of-the-sdp-use" class="section-name selfRef">Registration of the SDP 'userid' Attribute</a> |
| 2330 |
</h3> |
| 2331 |
<p id="section-13.4-1"> |
| 2332 |
This document defines the SDP 'userid' attribute. |
| 2333 |
Details regarding this attribute are provided in <a href="#sec_userid-attr" class="xref">Section 5.3</a>.<a href="#section-13.4-1" class="pilcrow">¶</a></p> |
| 2334 |
</section> |
| 2335 |
<section id="section-13.5"> |
| 2336 |
<h3 id="name-registration-of-the-sdp-floo"> |
| 2337 |
<a href="#section-13.5" class="section-number selfRef">13.5. </a><a href="#name-registration-of-the-sdp-floo" class="section-name selfRef">Registration of the SDP 'floorid' Attribute</a> |
| 2338 |
</h3> |
| 2339 |
<p id="section-13.5-1"> |
| 2340 |
This document defines the SDP 'floorid' attribute. |
| 2341 |
Details regarding this attribute are provided in <a href="#sec_floorid-attr" class="xref">Section 5.4</a>.<a href="#section-13.5-1" class="pilcrow">¶</a></p> |
| 2342 |
</section> |
| 2343 |
<section id="section-13.6"> |
| 2344 |
<h3 id="name-registration-of-the-sdp-bfc"> |
| 2345 |
<a href="#section-13.6" class="section-number selfRef">13.6. </a><a href="#name-registration-of-the-sdp-bfc" class="section-name selfRef">Registration of the SDP 'bfcpver' Attribute</a> |
| 2346 |
</h3> |
| 2347 |
<p id="section-13.6-1"> |
| 2348 |
This document defines the SDP 'bfcpver' attribute. |
| 2349 |
Details regarding this attribute are provided in <a href="#sec_bfcp-version-attr" class="xref">Section 5.5</a>.<a href="#section-13.6-1" class="pilcrow">¶</a></p> |
| 2350 |
</section> |
| 2351 |
</section> |
| 2352 |
</div> |
| 2353 |
<div id="sec_changes"> |
| 2354 |
<section id="section-14"> |
| 2355 |
<h2 id="name-changes-from-rfc-4583"> |
| 2356 |
<a href="#section-14" class="section-number selfRef">14. </a><a href="#name-changes-from-rfc-4583" class="section-name selfRef">Changes from RFC 4583</a> |
| 2357 |
</h2> |
| 2358 |
<p id="section-14-1">The technical changes and other fixes from <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span> are listed below.<a href="#section-14-1" class="pilcrow">¶</a></p> |
| 2359 |
<p id="section-14-2">The main purpose of this work was to add signaling support necessary |
| 2360 |
to support BFCP over an unreliable transport, as described in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>, resulting in the following changes:<a href="#section-14-2" class="pilcrow">¶</a></p> |
| 2361 |
<ul class="normal"> |
| 2362 |
<li class="normal" id="section-14-3.1"> |
| 2363 |
<p id="section-14-3.1.1">Fields in the "m=" Line (<a href="#sec_m-line" class="xref">Section 4</a>):<a href="#section-14-3.1.1" class="pilcrow">¶</a></p> |
| 2364 |
<p id="section-14-3.1.2">This section has been rewritten to remove reference to the exclusivity |
| 2365 |
of TCP as a transport for BFCP streams. The proto field values |
| 2366 |
'TCP/DTLS/BFCP', 'UDP/BFCP', and 'UDP/TLS/BFCP' have been added.<a href="#section-14-3.1.2" class="pilcrow">¶</a></p> |
| 2367 |
</li> |
| 2368 |
<li class="normal" id="section-14-3.2"> |
| 2369 |
<p id="section-14-3.2.1">Security Considerations (<a href="#sec_security" class="xref">Section 12</a>):<a href="#section-14-3.2.1" class="pilcrow">¶</a></p> |
| 2370 |
<p id="section-14-3.2.2">For the DTLS-over-UDP case, we direct the reader to existing considerations |
| 2371 |
and requirements for the offer/answer exchange as provided in <span>[<a href="#RFC8842" class="xref">RFC8842</a>]</span>.<a href="#section-14-3.2.2" class="pilcrow">¶</a></p> |
| 2372 |
</li> |
| 2373 |
<li class="normal" id="section-14-3.3"> |
| 2374 |
<p id="section-14-3.3.1">Registration of SDP 'proto' Values (<a href="#sec_proto-reg" class="xref">Section 13.1</a>):<a href="#section-14-3.3.1" class="pilcrow">¶</a></p> |
| 2375 |
<p id="section-14-3.3.2">This document registers the three new values 'TCP/DTLS/BFCP', 'UDP/BFCP', and |
| 2376 |
'UDP/TLS/BFCP' in the "Session Description Protocol (SDP) Parameters" registry.<a href="#section-14-3.3.2" class="pilcrow">¶</a></p> |
| 2377 |
</li> |
| 2378 |
<li class="normal" id="section-14-3.4"> |
| 2379 |
<p id="section-14-3.4.1">SDP 'bfcpver' Attribute (<a href="#sec_bfcp-version-attr" class="xref">Section 5.5</a>):<a href="#section-14-3.4.1" class="pilcrow">¶</a></p> |
| 2380 |
<p id="section-14-3.4.2">A new 'bfcpver' SDP media-level attribute has been added, in order to |
| 2381 |
signal the supported version number.<a href="#section-14-3.4.2" class="pilcrow">¶</a></p> |
| 2382 |
</li> |
| 2383 |
</ul> |
| 2384 |
<p id="section-14-4">In addition to the changes associated with support of BFCP over an |
| 2385 |
unreliable transport, the possibility that an endpoint can act as both a |
| 2386 |
floor control client and a floor control server at the same time has |
| 2387 |
been removed. An endpoint will now take the same role for all BFCP-controlled streams associated with the BFCP stream.<a href="#section-14-4" class="pilcrow">¶</a></p> |
| 2388 |
<p id="section-14-5">Clarifications and bug fixes:<a href="#section-14-5" class="pilcrow">¶</a></p> |
| 2389 |
<ul class="normal"> |
| 2390 |
<li class="normal" id="section-14-6.1"> |
| 2391 |
<p id="section-14-6.1.1">Erratum ID 712 (Sections <a href="https://www.rfc-editor.org/rfc/rfc4583#section-3" class="relref">3</a> and <a href="https://www.rfc-editor.org/rfc/rfc4583#section-10" class="relref">10</a> of <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span>; see <span>[<a href="#Err712" class="xref">Err712</a>]</span> for details):<a href="#section-14-6.1.1" class="pilcrow">¶</a></p> |
| 2392 |
<p id="section-14-6.1.2">Do not use language such as 'used in an "m=" line' when discussing an SDP attribute; instead, make clear that the attribute is a |
| 2393 |
media-level attribute.<a href="#section-14-6.1.2" class="pilcrow">¶</a></p> |
| 2394 |
</li> |
| 2395 |
<li class="normal" id="section-14-6.2"> |
| 2396 |
<p id="section-14-6.2.1">Spelling corrected in the first SDP example in <span><a href="https://www.rfc-editor.org/rfc/rfc4583#section-9" class="relref">Section 9</a> of [<a href="#RFC4583" class="xref">RFC4583</a>]</span>:<a href="#section-14-6.2.1" class="pilcrow">¶</a></p> |
| 2397 |
<p id="section-14-6.2.2">Do not use 'm-stream' as listed in the first SDP example in <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span>; instead, use the correct 'mstrm' |
| 2398 |
as specified in <a href="#sec_example" class="xref">Section 11</a> of this |
| 2399 |
document. However, we recommend continuing to interpret 'm-stream', if received, |
| 2400 |
because it is still present in some implementations.<a href="#section-14-6.2.2" class="pilcrow">¶</a></p> |
| 2401 |
</li> |
| 2402 |
<li class="normal" id="section-14-6.3"> |
| 2403 |
<p id="section-14-6.3.1">Assorted clarifications (throughout the document):<a href="#section-14-6.3.1" class="pilcrow">¶</a></p> |
| 2404 |
<p id="section-14-6.3.2">Language clarifications were made as a result of reviews. Also, |
| 2405 |
normative language was "tightened" where appropriate, i.e., changed |
| 2406 |
from "<span class="bcp14">SHOULD</span>" strength to "<span class="bcp14">MUST</span>" in a |
| 2407 |
number of places.<a href="#section-14-6.3.2" class="pilcrow">¶</a></p> |
| 2408 |
</li> |
| 2409 |
</ul> |
| 2410 |
</section> |
| 2411 |
</div> |
| 2412 |
<section id="section-15"> |
| 2413 |
<h2 id="name-references"> |
| 2414 |
<a href="#section-15" class="section-number selfRef">15. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 2415 |
</h2> |
| 2416 |
<section id="section-15.1"> |
| 2417 |
<h3 id="name-normative-references"> |
| 2418 |
<a href="#section-15.1" class="section-number selfRef">15.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 2419 |
</h3> |
| 2420 |
<dl class="references"> |
| 2421 |
<dt id="RFC2119">[RFC2119]</dt> |
| 2422 |
<dd> |
| 2423 |
<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><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd> |
| 2424 |
<dd class="break"></dd> |
| 2425 |
<dt id="RFC3261">[RFC3261]</dt> |
| 2426 |
<dd> |
| 2427 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Schulzrinne, H.</span><span class="refAuthor">, Camarillo, G.</span><span class="refAuthor">, Johnston, A.</span><span class="refAuthor">, Peterson, J.</span><span class="refAuthor">, Sparks, R.</span><span class="refAuthor">, Handley, M.</span><span class="refAuthor">, and E. Schooler</span>, <span class="refTitle">"SIP: Session Initiation Protocol"</span>, <span class="seriesInfo">RFC 3261</span>, <span class="seriesInfo">DOI 10.17487/RFC3261</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3261">https://www.rfc-editor.org/info/rfc3261</a>></span>. </dd> |
| 2428 |
<dd class="break"></dd> |
| 2429 |
<dt id="RFC3264">[RFC3264]</dt> |
| 2430 |
<dd> |
| 2431 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor"> and H. Schulzrinne</span>, <span class="refTitle">"An Offer/Answer Model with Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 3264</span>, <span class="seriesInfo">DOI 10.17487/RFC3264</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3264">https://www.rfc-editor.org/info/rfc3264</a>></span>. </dd> |
| 2432 |
<dd class="break"></dd> |
| 2433 |
<dt id="RFC4145">[RFC4145]</dt> |
| 2434 |
<dd> |
| 2435 |
<span class="refAuthor">Yon, D.</span><span class="refAuthor"> and G. Camarillo</span>, <span class="refTitle">"TCP-Based Media Transport in the Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 4145</span>, <span class="seriesInfo">DOI 10.17487/RFC4145</span>, <time datetime="2005-09" class="refDate">September 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4145">https://www.rfc-editor.org/info/rfc4145</a>></span>. </dd> |
| 2436 |
<dd class="break"></dd> |
| 2437 |
<dt id="RFC4571">[RFC4571]</dt> |
| 2438 |
<dd> |
| 2439 |
<span class="refAuthor">Lazzaro, J.</span>, <span class="refTitle">"Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport"</span>, <span class="seriesInfo">RFC 4571</span>, <span class="seriesInfo">DOI 10.17487/RFC4571</span>, <time datetime="2006-07" class="refDate">July 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4571">https://www.rfc-editor.org/info/rfc4571</a>></span>. </dd> |
| 2440 |
<dd class="break"></dd> |
| 2441 |
<dt id="RFC4574">[RFC4574]</dt> |
| 2442 |
<dd> |
| 2443 |
<span class="refAuthor">Levin, O.</span><span class="refAuthor"> and G. Camarillo</span>, <span class="refTitle">"The Session Description Protocol (SDP) Label Attribute"</span>, <span class="seriesInfo">RFC 4574</span>, <span class="seriesInfo">DOI 10.17487/RFC4574</span>, <time datetime="2006-08" class="refDate">August 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4574">https://www.rfc-editor.org/info/rfc4574</a>></span>. </dd> |
| 2444 |
<dd class="break"></dd> |
| 2445 |
<dt id="RFC4582">[RFC4582]</dt> |
| 2446 |
<dd> |
| 2447 |
<span class="refAuthor">Camarillo, G.</span><span class="refAuthor">, Ott, J.</span><span class="refAuthor">, and K. Drage</span>, <span class="refTitle">"The Binary Floor Control Protocol (BFCP)"</span>, <span class="seriesInfo">RFC 4582</span>, <span class="seriesInfo">DOI 10.17487/RFC4582</span>, <time datetime="2006-11" class="refDate">November 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4582">https://www.rfc-editor.org/info/rfc4582</a>></span>. </dd> |
| 2448 |
<dd class="break"></dd> |
| 2449 |
<dt id="RFC4583">[RFC4583]</dt> |
| 2450 |
<dd> |
| 2451 |
<span class="refAuthor">Camarillo, G.</span>, <span class="refTitle">"Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams"</span>, <span class="seriesInfo">RFC 4583</span>, <span class="seriesInfo">DOI 10.17487/RFC4583</span>, <time datetime="2006-11" class="refDate">November 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4583">https://www.rfc-editor.org/info/rfc4583</a>></span>. </dd> |
| 2452 |
<dd class="break"></dd> |
| 2453 |
<dt id="RFC5234">[RFC5234]</dt> |
| 2454 |
<dd> |
| 2455 |
<span class="refAuthor">Crocker, D., Ed.</span><span class="refAuthor"> and P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>></span>. </dd> |
| 2456 |
<dd class="break"></dd> |
| 2457 |
<dt id="RFC6347">[RFC6347]</dt> |
| 2458 |
<dd> |
| 2459 |
<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><<a href="https://www.rfc-editor.org/info/rfc6347">https://www.rfc-editor.org/info/rfc6347</a>></span>. </dd> |
| 2460 |
<dd class="break"></dd> |
| 2461 |
<dt id="RFC6544">[RFC6544]</dt> |
| 2462 |
<dd> |
| 2463 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Keranen, A.</span><span class="refAuthor">, Lowekamp, B. B.</span><span class="refAuthor">, and A. B. Roach</span>, <span class="refTitle">"TCP Candidates with Interactive Connectivity Establishment (ICE)"</span>, <span class="seriesInfo">RFC 6544</span>, <span class="seriesInfo">DOI 10.17487/RFC6544</span>, <time datetime="2012-03" class="refDate">March 2012</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6544">https://www.rfc-editor.org/info/rfc6544</a>></span>. </dd> |
| 2464 |
<dd class="break"></dd> |
| 2465 |
<dt id="RFC8122">[RFC8122]</dt> |
| 2466 |
<dd> |
| 2467 |
<span class="refAuthor">Lennox, J.</span><span class="refAuthor"> and C. Holmberg</span>, <span class="refTitle">"Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 8122</span>, <span class="seriesInfo">DOI 10.17487/RFC8122</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8122">https://www.rfc-editor.org/info/rfc8122</a>></span>. </dd> |
| 2468 |
<dd class="break"></dd> |
| 2469 |
<dt id="RFC8174">[RFC8174]</dt> |
| 2470 |
<dd> |
| 2471 |
<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><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 2472 |
<dd class="break"></dd> |
| 2473 |
<dt id="RFC8445">[RFC8445]</dt> |
| 2474 |
<dd> |
| 2475 |
<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><<a href="https://www.rfc-editor.org/info/rfc8445">https://www.rfc-editor.org/info/rfc8445</a>></span>. </dd> |
| 2476 |
<dd class="break"></dd> |
| 2477 |
<dt id="RFC8839">[RFC8839]</dt> |
| 2478 |
<dd> |
| 2479 |
<span class="refAuthor">Petit-Huguenin, M.</span><span class="refAuthor">, Nandakumar, S.</span><span class="refAuthor">, Holmberg, C.</span><span class="refAuthor">, Keränen, A.</span><span class="refAuthor">, and R. Shpount</span>, <span class="refTitle">"Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)"</span>, <span class="seriesInfo">RFC 8839</span>, <span class="seriesInfo">DOI 10.17487/RFC8839</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8839">https://www.rfc-editor.org/info/rfc8839</a>></span>. </dd> |
| 2480 |
<dd class="break"></dd> |
| 2481 |
<dt id="RFC8842">[RFC8842]</dt> |
| 2482 |
<dd> |
| 2483 |
<span class="refAuthor">Holmberg, C.</span><span class="refAuthor"> and R. Shpount</span>, <span class="refTitle">"Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)"</span>, <span class="seriesInfo">RFC 8842</span>, <span class="seriesInfo">DOI 10.17487/RFC8842</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8842">https://www.rfc-editor.org/info/rfc8842</a>></span>. </dd> |
| 2484 |
<dd class="break"></dd> |
| 2485 |
<dt id="RFC8855">[RFC8855]</dt> |
| 2486 |
<dd> |
| 2487 |
<span class="refAuthor">Camarillo, G.</span><span class="refAuthor">, Drage, K.</span><span class="refAuthor">, Kristensen, T.</span><span class="refAuthor">, Ott, J.</span><span class="refAuthor">, and C. Eckel</span>, <span class="refTitle">"The Binary Floor Control Protocol (BFCP)"</span>, <span class="seriesInfo">RFC 8855</span>, <span class="seriesInfo">DOI 10.17487/RFC8855</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8855">https://www.rfc-editor.org/info/rfc8855</a>></span>. </dd> |
| 2488 |
<dd class="break"></dd> |
| 2489 |
<dt id="RFC8859">[RFC8859]</dt> |
| 2490 |
<dd> |
| 2491 |
<span class="refAuthor">Nandakumar, S.</span>, <span class="refTitle">"A Framework for Session Description Protocol (SDP) Attributes When Multiplexing"</span>, <span class="seriesInfo">RFC 8859</span>, <span class="seriesInfo">DOI 10.17487/RFC8859</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8859">https://www.rfc-editor.org/info/rfc8859</a>></span>. </dd> |
| 2492 |
<dd class="break"></dd> |
| 2493 |
<dt id="RFC8866">[RFC8866]</dt> |
| 2494 |
<dd> |
| 2495 |
<span class="refAuthor">Begen, A.</span><span class="refAuthor">, Kyzivat, P.</span><span class="refAuthor">, Perkins, C.</span><span class="refAuthor">, and M. Handley</span>, <span class="refTitle">"SDP: Session Description Protocol"</span>, <span class="seriesInfo">RFC 8866</span>, <span class="seriesInfo">DOI 10.17487/RFC8866</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8866">https://www.rfc-editor.org/info/rfc8866</a>></span>. </dd> |
| 2496 |
<dd class="break"></dd> |
| 2497 |
</dl> |
| 2498 |
</section> |
| 2499 |
<section id="section-15.2"> |
| 2500 |
<h3 id="name-informative-references"> |
| 2501 |
<a href="#section-15.2" class="section-number selfRef">15.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2502 |
</h3> |
| 2503 |
<dl class="references"> |
| 2504 |
<dt id="Err712">[Err712]</dt> |
| 2505 |
<dd> |
| 2506 |
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 712</span>, <span class="refContent">RFC 4583</span>, <span><<a href="https://www.rfc-editor.org/errata/eid712">https://www.rfc-editor.org/errata/eid712</a>></span>. </dd> |
| 2507 |
<dd class="break"></dd> |
| 2508 |
<dt id="RFC5576">[RFC5576]</dt> |
| 2509 |
<dd> |
| 2510 |
<span class="refAuthor">Lennox, J.</span><span class="refAuthor">, Ott, J.</span><span class="refAuthor">, and T. Schierl</span>, <span class="refTitle">"Source-Specific Media Attributes in the Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 5576</span>, <span class="seriesInfo">DOI 10.17487/RFC5576</span>, <time datetime="2009-06" class="refDate">June 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5576">https://www.rfc-editor.org/info/rfc5576</a>></span>. </dd> |
| 2511 |
<dd class="break"></dd> |
| 2512 |
<dt id="RFC8843">[RFC8843]</dt> |
| 2513 |
<dd> |
| 2514 |
<span class="refAuthor">Holmberg, C.</span><span class="refAuthor">, Alvestrand, H.</span><span class="refAuthor">, and C. Jennings</span>, <span class="refTitle">"Negotiating Media Multiplexing Using the Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 8843</span>, <span class="seriesInfo">DOI 10.17487/RFC8843</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8843">https://www.rfc-editor.org/info/rfc8843</a>></span>. </dd> |
| 2515 |
<dd class="break"></dd> |
| 2516 |
</dl> |
| 2517 |
</section> |
| 2518 |
</section> |
| 2519 |
<div id="sec_acks"> |
| 2520 |
<section id="section-appendix.a"> |
| 2521 |
<h2 id="name-acknowledgements"> |
| 2522 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 2523 |
</h2> |
| 2524 |
<p id="section-appendix.a-1"><span class="contact-name">Jörg Ott</span>, <span class="contact-name">Keith Drage</span>, |
| 2525 |
<span class="contact-name">Alan Johnston</span>, <span class="contact-name">Eric Rescorla</span>, <span class="contact-name">Roni Even</span>, and <span class="contact-name">Oscar Novo</span> provided useful ideas for the original <span>[<a href="#RFC4583" class="xref">RFC4583</a>]</span>. The authors also acknowledge |
| 2526 |
contributions to the revision of BFCP for use over an unreliable |
| 2527 |
transport from <span class="contact-name">Geir Arne Sandbakken</span>, <span class="contact-name">Charles Eckel</span>, <span class="contact-name">Alan Ford</span>, <span class="contact-name">Eoin McLeod</span>, and <span class="contact-name">Mark Thompson</span>. Useful |
| 2528 |
and important final reviews were done by <span class="contact-name">Ali C. Begen</span>, <span class="contact-name">Mary Barnes</span>, and <span class="contact-name">Charles Eckel</span>. In the final stages, <span class="contact-name">Roman Shpount</span> made a considerable effort in adding proper ICE support and considerations.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p> |
| 2529 |
</section> |
| 2530 |
</div> |
| 2531 |
<div id="authors-addresses"> |
| 2532 |
<section id="section-appendix.b"> |
| 2533 |
<h2 id="name-authors-addresses"> |
| 2534 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2535 |
</h2> |
| 2536 |
<address class="vcard"> |
| 2537 |
<div dir="auto" class="left"><span class="fn nameRole">Gonzalo Camarillo</span></div> |
| 2538 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 2539 |
<div dir="auto" class="left"><span class="street-address">Hirsalantie 11</span></div> |
| 2540 |
<div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span> |
| 2541 |
</div> |
| 2542 |
<div dir="auto" class="left"><span class="country-name">Finland</span></div> |
| 2543 |
<div class="email"> |
| 2544 |
<span>Email:</span> |
| 2545 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2546 |
</div> |
| 2547 |
</address> |
| 2548 |
<address class="vcard"> |
| 2549 |
<div dir="auto" class="left"><span class="fn nameRole">Tom Kristensen</span></div> |
| 2550 |
<div dir="auto" class="left"><span class="org">Jotron AS</span></div> |
| 2551 |
<div dir="auto" class="left"><span class="street-address">Ringdalskogen 8</span></div> |
| 2552 |
<div dir="auto" class="left"> |
| 2553 |
<span class="postal-code">3270</span> <span class="locality">Larvik</span> |
| 2554 |
</div> |
| 2555 |
<div dir="auto" class="left"><span class="country-name">Norway</span></div> |
| 2556 |
<div class="email"> |
| 2557 |
<span>Email:</span> |
| 2558 |
<a href="mailto:[email protected],%[email protected]" class="email">[email protected], [email protected]</a> |
| 2559 |
</div> |
| 2560 |
</address> |
| 2561 |
<address class="vcard"> |
| 2562 |
<div dir="auto" class="left"><span class="fn nameRole">Christer Holmberg</span></div> |
| 2563 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 2564 |
<div dir="auto" class="left"><span class="street-address">Hirsalantie 11</span></div> |
| 2565 |
<div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span> |
| 2566 |
</div> |
| 2567 |
<div dir="auto" class="left"><span class="country-name">Finland</span></div> |
| 2568 |
<div class="email"> |
| 2569 |
<span>Email:</span> |
| 2570 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2571 |
</div> |
| 2572 |
</address> |
| 2573 |
</section> |
| 2574 |
</div> |
| 2575 |
<script>const toc = document.getElementById("toc"); |
| 2576 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2577 |
toc.classList.toggle("active"); |
| 2578 |
}); |
| 2579 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2580 |
toc.classList.remove("active"); |
| 2581 |
}); |
| 2582 |
</script> |
| 2583 |
</body> |
| 2584 |
</html> |