| 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 8857: The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)</title> |
| 8 |
<meta content="Victor Pascual" name="author"> |
| 9 |
<meta content="Antón Román" name="author"> |
| 10 |
<meta content="Stéphane Cazeaux" name="author"> |
| 11 |
<meta content="Gonzalo Salgueiro" name="author"> |
| 12 |
<meta content="Ram Mohan Ravindranath" name="author"> |
| 13 |
<meta content=" |
| 14 |
The WebSocket protocol enables two-way real-time communication |
| 15 |
between clients and servers. This document specifies the use of Binary Floor |
| 16 |
Control Protocol (BFCP) as a new WebSocket subprotocol enabling a reliable |
| 17 |
transport mechanism between BFCP entities in new scenarios. |
| 18 |
" name="description"> |
| 19 |
<meta content="xml2rfc 3.5.0" name="generator"> |
| 20 |
<meta content="BFCP" name="keyword"> |
| 21 |
<meta content="WebSocket" name="keyword"> |
| 22 |
<meta content="8857" name="rfc.number"> |
| 23 |
<!-- Generator version information: |
| 24 |
xml2rfc 3.5.0 |
| 25 |
Python 3.6.10 |
| 26 |
appdirs 1.4.4 |
| 27 |
ConfigArgParse 1.2.3 |
| 28 |
google-i18n-address 2.3.5 |
| 29 |
html5lib 1.0.1 |
| 30 |
intervaltree 3.0.2 |
| 31 |
Jinja2 2.11.2 |
| 32 |
kitchen 1.2.6 |
| 33 |
lxml 4.4.2 |
| 34 |
pycairo 1.19.0 |
| 35 |
pycountry 19.8.18 |
| 36 |
pyflakes 2.1.1 |
| 37 |
PyYAML 5.3.1 |
| 38 |
requests 2.22.0 |
| 39 |
setuptools 40.6.2 |
| 40 |
six 1.14.0 |
| 41 |
WeasyPrint 51 |
| 42 |
--> |
| 43 |
<link href="rfc8857.xml" rel="alternate" type="application/rfc+xml"> |
| 44 |
<link href="#copyright" rel="license"> |
| 45 |
<style type="text/css">/* |
| 46 |
|
| 47 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 48 |
|
| 49 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 50 |
this can be consolidated so that style settings occur only in one place, but |
| 51 |
for now the contents of this file consists first of the initial CSS work as |
| 52 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 53 |
commented changes found necssary during the development of the v3 |
| 54 |
formatters. |
| 55 |
|
| 56 |
*/ |
| 57 |
|
| 58 |
/* fonts */ |
| 59 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 60 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 61 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 62 |
|
| 63 |
@viewport { |
| 64 |
zoom: 1.0; |
| 65 |
width: extend-to-zoom; |
| 66 |
} |
| 67 |
@-ms-viewport { |
| 68 |
width: extend-to-zoom; |
| 69 |
zoom: 1.0; |
| 70 |
} |
| 71 |
/* general and mobile first */ |
| 72 |
html { |
| 73 |
} |
| 74 |
body { |
| 75 |
max-width: 90%; |
| 76 |
margin: 1.5em auto; |
| 77 |
color: #222; |
| 78 |
background-color: #fff; |
| 79 |
font-size: 14px; |
| 80 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 81 |
line-height: 1.6; |
| 82 |
scroll-behavior: smooth; |
| 83 |
} |
| 84 |
.ears { |
| 85 |
display: none; |
| 86 |
} |
| 87 |
|
| 88 |
/* headings */ |
| 89 |
#title, h1, h2, h3, h4, h5, h6 { |
| 90 |
margin: 1em 0 0.5em; |
| 91 |
font-weight: bold; |
| 92 |
line-height: 1.3; |
| 93 |
} |
| 94 |
#title { |
| 95 |
clear: both; |
| 96 |
border-bottom: 1px solid #ddd; |
| 97 |
margin: 0 0 0.5em 0; |
| 98 |
padding: 1em 0 0.5em; |
| 99 |
} |
| 100 |
.author { |
| 101 |
padding-bottom: 4px; |
| 102 |
} |
| 103 |
h1 { |
| 104 |
font-size: 26px; |
| 105 |
margin: 1em 0; |
| 106 |
} |
| 107 |
h2 { |
| 108 |
font-size: 22px; |
| 109 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 110 |
padding-top: 33px; |
| 111 |
} |
| 112 |
h3 { |
| 113 |
font-size: 18px; |
| 114 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 115 |
padding-top: 42px; |
| 116 |
} |
| 117 |
h4 { |
| 118 |
font-size: 16px; |
| 119 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 120 |
padding-top: 42px; |
| 121 |
} |
| 122 |
h5, h6 { |
| 123 |
font-size: 14px; |
| 124 |
} |
| 125 |
#n-copyright-notice { |
| 126 |
border-bottom: 1px solid #ddd; |
| 127 |
padding-bottom: 1em; |
| 128 |
margin-bottom: 1em; |
| 129 |
} |
| 130 |
/* general structure */ |
| 131 |
p { |
| 132 |
padding: 0; |
| 133 |
margin: 0 0 1em 0; |
| 134 |
text-align: left; |
| 135 |
} |
| 136 |
div, span { |
| 137 |
position: relative; |
| 138 |
} |
| 139 |
div { |
| 140 |
margin: 0; |
| 141 |
} |
| 142 |
.alignRight.art-text { |
| 143 |
background-color: #f9f9f9; |
| 144 |
border: 1px solid #eee; |
| 145 |
border-radius: 3px; |
| 146 |
padding: 1em 1em 0; |
| 147 |
margin-bottom: 1.5em; |
| 148 |
} |
| 149 |
.alignRight.art-text pre { |
| 150 |
padding: 0; |
| 151 |
} |
| 152 |
.alignRight { |
| 153 |
margin: 1em 0; |
| 154 |
} |
| 155 |
.alignRight > *:first-child { |
| 156 |
border: none; |
| 157 |
margin: 0; |
| 158 |
float: right; |
| 159 |
clear: both; |
| 160 |
} |
| 161 |
.alignRight > *:nth-child(2) { |
| 162 |
clear: both; |
| 163 |
display: block; |
| 164 |
border: none; |
| 165 |
} |
| 166 |
svg { |
| 167 |
display: block; |
| 168 |
} |
| 169 |
.alignCenter.art-text { |
| 170 |
background-color: #f9f9f9; |
| 171 |
border: 1px solid #eee; |
| 172 |
border-radius: 3px; |
| 173 |
padding: 1em 1em 0; |
| 174 |
margin-bottom: 1.5em; |
| 175 |
} |
| 176 |
.alignCenter.art-text pre { |
| 177 |
padding: 0; |
| 178 |
} |
| 179 |
.alignCenter { |
| 180 |
margin: 1em 0; |
| 181 |
} |
| 182 |
.alignCenter > *:first-child { |
| 183 |
border: none; |
| 184 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 185 |
support flexbox yet. |
| 186 |
*/ |
| 187 |
display: table; |
| 188 |
margin: 0 auto; |
| 189 |
} |
| 190 |
|
| 191 |
/* lists */ |
| 192 |
ol, ul { |
| 193 |
padding: 0; |
| 194 |
margin: 0 0 1em 2em; |
| 195 |
} |
| 196 |
ol ol, ul ul, ol ul, ul ol { |
| 197 |
margin-left: 1em; |
| 198 |
} |
| 199 |
li { |
| 200 |
margin: 0 0 0.25em 0; |
| 201 |
} |
| 202 |
.ulCompact li { |
| 203 |
margin: 0; |
| 204 |
} |
| 205 |
ul.empty, .ulEmpty { |
| 206 |
list-style-type: none; |
| 207 |
} |
| 208 |
ul.empty li, .ulEmpty li { |
| 209 |
margin-top: 0.5em; |
| 210 |
} |
| 211 |
ul.compact, .ulCompact, |
| 212 |
ol.compact, .olCompact { |
| 213 |
line-height: 100%; |
| 214 |
margin: 0 0 0 2em; |
| 215 |
} |
| 216 |
|
| 217 |
/* definition lists */ |
| 218 |
dl { |
| 219 |
} |
| 220 |
dl > dt { |
| 221 |
float: left; |
| 222 |
margin-right: 1em; |
| 223 |
} |
| 224 |
/* |
| 225 |
dl.nohang > dt { |
| 226 |
float: none; |
| 227 |
} |
| 228 |
*/ |
| 229 |
dl > dd { |
| 230 |
margin-bottom: .8em; |
| 231 |
min-height: 1.3em; |
| 232 |
} |
| 233 |
dl.compact > dd, .dlCompact > dd { |
| 234 |
margin-bottom: 0em; |
| 235 |
} |
| 236 |
dl > dd > dl { |
| 237 |
margin-top: 0.5em; |
| 238 |
margin-bottom: 0em; |
| 239 |
} |
| 240 |
|
| 241 |
/* links */ |
| 242 |
a { |
| 243 |
text-decoration: none; |
| 244 |
} |
| 245 |
a[href] { |
| 246 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 247 |
} |
| 248 |
a[href]:hover { |
| 249 |
background-color: #f2f2f2; |
| 250 |
} |
| 251 |
figcaption a[href], |
| 252 |
a[href].selfRef { |
| 253 |
color: #222; |
| 254 |
} |
| 255 |
/* XXX probably not this: |
| 256 |
a.selfRef:hover { |
| 257 |
background-color: transparent; |
| 258 |
cursor: default; |
| 259 |
} */ |
| 260 |
|
| 261 |
/* Figures */ |
| 262 |
tt, code, pre, code { |
| 263 |
background-color: #f9f9f9; |
| 264 |
font-family: 'Roboto Mono', monospace; |
| 265 |
} |
| 266 |
pre { |
| 267 |
border: 1px solid #eee; |
| 268 |
margin: 0; |
| 269 |
padding: 1em; |
| 270 |
} |
| 271 |
img { |
| 272 |
max-width: 100%; |
| 273 |
} |
| 274 |
figure { |
| 275 |
margin: 0; |
| 276 |
} |
| 277 |
figure blockquote { |
| 278 |
margin: 0.8em 0.4em 0.4em; |
| 279 |
} |
| 280 |
figcaption { |
| 281 |
font-style: italic; |
| 282 |
margin: 0 0 1em 0; |
| 283 |
} |
| 284 |
@media screen { |
| 285 |
pre { |
| 286 |
overflow-x: auto; |
| 287 |
max-width: 100%; |
| 288 |
max-width: calc(100% - 22px); |
| 289 |
} |
| 290 |
} |
| 291 |
|
| 292 |
/* aside, blockquote */ |
| 293 |
aside, blockquote { |
| 294 |
margin-left: 0; |
| 295 |
padding: 1.2em 2em; |
| 296 |
} |
| 297 |
blockquote { |
| 298 |
background-color: #f9f9f9; |
| 299 |
color: #111; /* Arlen: WCAG 2019 */ |
| 300 |
border: 1px solid #ddd; |
| 301 |
border-radius: 3px; |
| 302 |
margin: 1em 0; |
| 303 |
} |
| 304 |
cite { |
| 305 |
display: block; |
| 306 |
text-align: right; |
| 307 |
font-style: italic; |
| 308 |
} |
| 309 |
|
| 310 |
/* tables */ |
| 311 |
table { |
| 312 |
width: 100%; |
| 313 |
margin: 0 0 1em; |
| 314 |
border-collapse: collapse; |
| 315 |
border: 1px solid #eee; |
| 316 |
} |
| 317 |
th, td { |
| 318 |
text-align: left; |
| 319 |
vertical-align: top; |
| 320 |
padding: 0.5em 0.75em; |
| 321 |
} |
| 322 |
th { |
| 323 |
text-align: left; |
| 324 |
background-color: #e9e9e9; |
| 325 |
} |
| 326 |
tr:nth-child(2n+1) > td { |
| 327 |
background-color: #f5f5f5; |
| 328 |
} |
| 329 |
table caption { |
| 330 |
font-style: italic; |
| 331 |
margin: 0; |
| 332 |
padding: 0; |
| 333 |
text-align: left; |
| 334 |
} |
| 335 |
table p { |
| 336 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 337 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 338 |
margin: 0; |
| 339 |
} |
| 340 |
|
| 341 |
/* pilcrow */ |
| 342 |
a.pilcrow { |
| 343 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 344 |
text-decoration: none; |
| 345 |
visibility: hidden; |
| 346 |
user-select: none; |
| 347 |
-ms-user-select: none; |
| 348 |
-o-user-select:none; |
| 349 |
-moz-user-select: none; |
| 350 |
-khtml-user-select: none; |
| 351 |
-webkit-user-select: none; |
| 352 |
-webkit-touch-callout: none; |
| 353 |
} |
| 354 |
@media screen { |
| 355 |
aside:hover > a.pilcrow, |
| 356 |
p:hover > a.pilcrow, |
| 357 |
blockquote:hover > a.pilcrow, |
| 358 |
div:hover > a.pilcrow, |
| 359 |
li:hover > a.pilcrow, |
| 360 |
pre:hover > a.pilcrow { |
| 361 |
visibility: visible; |
| 362 |
} |
| 363 |
a.pilcrow:hover { |
| 364 |
background-color: transparent; |
| 365 |
} |
| 366 |
} |
| 367 |
|
| 368 |
/* misc */ |
| 369 |
hr { |
| 370 |
border: 0; |
| 371 |
border-top: 1px solid #eee; |
| 372 |
} |
| 373 |
.bcp14 { |
| 374 |
font-variant: small-caps; |
| 375 |
} |
| 376 |
|
| 377 |
.role { |
| 378 |
font-variant: all-small-caps; |
| 379 |
} |
| 380 |
|
| 381 |
/* info block */ |
| 382 |
#identifiers { |
| 383 |
margin: 0; |
| 384 |
font-size: 0.9em; |
| 385 |
} |
| 386 |
#identifiers dt { |
| 387 |
width: 3em; |
| 388 |
clear: left; |
| 389 |
} |
| 390 |
#identifiers dd { |
| 391 |
float: left; |
| 392 |
margin-bottom: 0; |
| 393 |
} |
| 394 |
#identifiers .authors .author { |
| 395 |
display: inline-block; |
| 396 |
margin-right: 1.5em; |
| 397 |
} |
| 398 |
#identifiers .authors .org { |
| 399 |
font-style: italic; |
| 400 |
} |
| 401 |
|
| 402 |
/* The prepared/rendered info at the very bottom of the page */ |
| 403 |
.docInfo { |
| 404 |
color: #666; /* Arlen: WCAG 2019 */ |
| 405 |
font-size: 0.9em; |
| 406 |
font-style: italic; |
| 407 |
margin-top: 2em; |
| 408 |
} |
| 409 |
.docInfo .prepared { |
| 410 |
float: left; |
| 411 |
} |
| 412 |
.docInfo .prepared { |
| 413 |
float: right; |
| 414 |
} |
| 415 |
|
| 416 |
/* table of contents */ |
| 417 |
#toc { |
| 418 |
padding: 0.75em 0 2em 0; |
| 419 |
margin-bottom: 1em; |
| 420 |
} |
| 421 |
nav.toc ul { |
| 422 |
margin: 0 0.5em 0 0; |
| 423 |
padding: 0; |
| 424 |
list-style: none; |
| 425 |
} |
| 426 |
nav.toc li { |
| 427 |
line-height: 1.3em; |
| 428 |
margin: 0.75em 0; |
| 429 |
padding-left: 1.2em; |
| 430 |
text-indent: -1.2em; |
| 431 |
} |
| 432 |
/* references */ |
| 433 |
.references dt { |
| 434 |
text-align: right; |
| 435 |
font-weight: bold; |
| 436 |
min-width: 7em; |
| 437 |
} |
| 438 |
.references dd { |
| 439 |
margin-left: 8em; |
| 440 |
overflow: auto; |
| 441 |
} |
| 442 |
|
| 443 |
.refInstance { |
| 444 |
margin-bottom: 1.25em; |
| 445 |
} |
| 446 |
|
| 447 |
.references .ascii { |
| 448 |
margin-bottom: 0.25em; |
| 449 |
} |
| 450 |
|
| 451 |
/* index */ |
| 452 |
.index ul { |
| 453 |
margin: 0 0 0 1em; |
| 454 |
padding: 0; |
| 455 |
list-style: none; |
| 456 |
} |
| 457 |
.index ul ul { |
| 458 |
margin: 0; |
| 459 |
} |
| 460 |
.index li { |
| 461 |
margin: 0; |
| 462 |
text-indent: -2em; |
| 463 |
padding-left: 2em; |
| 464 |
padding-bottom: 5px; |
| 465 |
} |
| 466 |
.indexIndex { |
| 467 |
margin: 0.5em 0 1em; |
| 468 |
} |
| 469 |
.index a { |
| 470 |
font-weight: 700; |
| 471 |
} |
| 472 |
/* make the index two-column on all but the smallest screens */ |
| 473 |
@media (min-width: 600px) { |
| 474 |
.index ul { |
| 475 |
-moz-column-count: 2; |
| 476 |
-moz-column-gap: 20px; |
| 477 |
} |
| 478 |
.index ul ul { |
| 479 |
-moz-column-count: 1; |
| 480 |
-moz-column-gap: 0; |
| 481 |
} |
| 482 |
} |
| 483 |
|
| 484 |
/* authors */ |
| 485 |
address.vcard { |
| 486 |
font-style: normal; |
| 487 |
margin: 1em 0; |
| 488 |
} |
| 489 |
|
| 490 |
address.vcard .nameRole { |
| 491 |
font-weight: 700; |
| 492 |
margin-left: 0; |
| 493 |
} |
| 494 |
address.vcard .label { |
| 495 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 496 |
margin: 0.5em 0; |
| 497 |
} |
| 498 |
address.vcard .type { |
| 499 |
display: none; |
| 500 |
} |
| 501 |
.alternative-contact { |
| 502 |
margin: 1.5em 0 1em; |
| 503 |
} |
| 504 |
hr.addr { |
| 505 |
border-top: 1px dashed; |
| 506 |
margin: 0; |
| 507 |
color: #ddd; |
| 508 |
max-width: calc(100% - 16px); |
| 509 |
} |
| 510 |
|
| 511 |
/* temporary notes */ |
| 512 |
.rfcEditorRemove::before { |
| 513 |
position: absolute; |
| 514 |
top: 0.2em; |
| 515 |
right: 0.2em; |
| 516 |
padding: 0.2em; |
| 517 |
content: "The RFC Editor will remove this note"; |
| 518 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 519 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 520 |
} |
| 521 |
.rfcEditorRemove { |
| 522 |
position: relative; |
| 523 |
padding-top: 1.8em; |
| 524 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 525 |
border-radius: 3px; |
| 526 |
} |
| 527 |
.cref { |
| 528 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 529 |
padding: 2px 4px; |
| 530 |
} |
| 531 |
.crefSource { |
| 532 |
font-style: italic; |
| 533 |
} |
| 534 |
/* alternative layout for smaller screens */ |
| 535 |
@media screen and (max-width: 1023px) { |
| 536 |
body { |
| 537 |
padding-top: 2em; |
| 538 |
} |
| 539 |
#title { |
| 540 |
padding: 1em 0; |
| 541 |
} |
| 542 |
h1 { |
| 543 |
font-size: 24px; |
| 544 |
} |
| 545 |
h2 { |
| 546 |
font-size: 20px; |
| 547 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 548 |
padding-top: 38px; |
| 549 |
} |
| 550 |
#identifiers dd { |
| 551 |
max-width: 60%; |
| 552 |
} |
| 553 |
#toc { |
| 554 |
position: fixed; |
| 555 |
z-index: 2; |
| 556 |
top: 0; |
| 557 |
right: 0; |
| 558 |
padding: 0; |
| 559 |
margin: 0; |
| 560 |
background-color: inherit; |
| 561 |
border-bottom: 1px solid #ccc; |
| 562 |
} |
| 563 |
#toc h2 { |
| 564 |
margin: -1px 0 0 0; |
| 565 |
padding: 4px 0 4px 6px; |
| 566 |
padding-right: 1em; |
| 567 |
min-width: 190px; |
| 568 |
font-size: 1.1em; |
| 569 |
text-align: right; |
| 570 |
background-color: #444; |
| 571 |
color: white; |
| 572 |
cursor: pointer; |
| 573 |
} |
| 574 |
#toc h2::before { /* css hamburger */ |
| 575 |
float: right; |
| 576 |
position: relative; |
| 577 |
width: 1em; |
| 578 |
height: 1px; |
| 579 |
left: -164px; |
| 580 |
margin: 6px 0 0 0; |
| 581 |
background: white none repeat scroll 0 0; |
| 582 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 583 |
content: ""; |
| 584 |
} |
| 585 |
#toc nav { |
| 586 |
display: none; |
| 587 |
padding: 0.5em 1em 1em; |
| 588 |
overflow: auto; |
| 589 |
height: calc(100vh - 48px); |
| 590 |
border-left: 1px solid #ddd; |
| 591 |
} |
| 592 |
} |
| 593 |
|
| 594 |
/* alternative layout for wide screens */ |
| 595 |
@media screen and (min-width: 1024px) { |
| 596 |
body { |
| 597 |
max-width: 724px; |
| 598 |
margin: 42px auto; |
| 599 |
padding-left: 1.5em; |
| 600 |
padding-right: 29em; |
| 601 |
} |
| 602 |
#toc { |
| 603 |
position: fixed; |
| 604 |
top: 42px; |
| 605 |
right: 42px; |
| 606 |
width: 25%; |
| 607 |
margin: 0; |
| 608 |
padding: 0 1em; |
| 609 |
z-index: 1; |
| 610 |
} |
| 611 |
#toc h2 { |
| 612 |
border-top: none; |
| 613 |
border-bottom: 1px solid #ddd; |
| 614 |
font-size: 1em; |
| 615 |
font-weight: normal; |
| 616 |
margin: 0; |
| 617 |
padding: 0.25em 1em 1em 0; |
| 618 |
} |
| 619 |
#toc nav { |
| 620 |
display: block; |
| 621 |
height: calc(90vh - 84px); |
| 622 |
bottom: 0; |
| 623 |
padding: 0.5em 0 0; |
| 624 |
overflow: auto; |
| 625 |
} |
| 626 |
img { /* future proofing */ |
| 627 |
max-width: 100%; |
| 628 |
height: auto; |
| 629 |
} |
| 630 |
} |
| 631 |
|
| 632 |
/* pagination */ |
| 633 |
@media print { |
| 634 |
body { |
| 635 |
|
| 636 |
width: 100%; |
| 637 |
} |
| 638 |
p { |
| 639 |
orphans: 3; |
| 640 |
widows: 3; |
| 641 |
} |
| 642 |
#n-copyright-notice { |
| 643 |
border-bottom: none; |
| 644 |
} |
| 645 |
#toc, #n-introduction { |
| 646 |
page-break-before: always; |
| 647 |
} |
| 648 |
#toc { |
| 649 |
border-top: none; |
| 650 |
padding-top: 0; |
| 651 |
} |
| 652 |
figure, pre { |
| 653 |
page-break-inside: avoid; |
| 654 |
} |
| 655 |
figure { |
| 656 |
overflow: scroll; |
| 657 |
} |
| 658 |
h1, h2, h3, h4, h5, h6 { |
| 659 |
page-break-after: avoid; |
| 660 |
} |
| 661 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 662 |
page-break-before: avoid; |
| 663 |
} |
| 664 |
pre { |
| 665 |
white-space: pre-wrap; |
| 666 |
word-wrap: break-word; |
| 667 |
font-size: 10pt; |
| 668 |
} |
| 669 |
table { |
| 670 |
border: 1px solid #ddd; |
| 671 |
} |
| 672 |
td { |
| 673 |
border-top: 1px solid #ddd; |
| 674 |
} |
| 675 |
} |
| 676 |
|
| 677 |
/* This is commented out here, as the string-set: doesn't |
| 678 |
pass W3C validation currently */ |
| 679 |
/* |
| 680 |
.ears thead .left { |
| 681 |
string-set: ears-top-left content(); |
| 682 |
} |
| 683 |
|
| 684 |
.ears thead .center { |
| 685 |
string-set: ears-top-center content(); |
| 686 |
} |
| 687 |
|
| 688 |
.ears thead .right { |
| 689 |
string-set: ears-top-right content(); |
| 690 |
} |
| 691 |
|
| 692 |
.ears tfoot .left { |
| 693 |
string-set: ears-bottom-left content(); |
| 694 |
} |
| 695 |
|
| 696 |
.ears tfoot .center { |
| 697 |
string-set: ears-bottom-center content(); |
| 698 |
} |
| 699 |
|
| 700 |
.ears tfoot .right { |
| 701 |
string-set: ears-bottom-right content(); |
| 702 |
} |
| 703 |
*/ |
| 704 |
|
| 705 |
@page :first { |
| 706 |
padding-top: 0; |
| 707 |
@top-left { |
| 708 |
content: normal; |
| 709 |
border: none; |
| 710 |
} |
| 711 |
@top-center { |
| 712 |
content: normal; |
| 713 |
border: none; |
| 714 |
} |
| 715 |
@top-right { |
| 716 |
content: normal; |
| 717 |
border: none; |
| 718 |
} |
| 719 |
} |
| 720 |
|
| 721 |
@page { |
| 722 |
size: A4; |
| 723 |
margin-bottom: 45mm; |
| 724 |
padding-top: 20px; |
| 725 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 726 |
the content depends on the document */ |
| 727 |
/* |
| 728 |
@top-left { |
| 729 |
content: 'Internet-Draft'; |
| 730 |
vertical-align: bottom; |
| 731 |
border-bottom: solid 1px #ccc; |
| 732 |
} |
| 733 |
@top-left { |
| 734 |
content: string(ears-top-left); |
| 735 |
vertical-align: bottom; |
| 736 |
border-bottom: solid 1px #ccc; |
| 737 |
} |
| 738 |
@top-center { |
| 739 |
content: string(ears-top-center); |
| 740 |
vertical-align: bottom; |
| 741 |
border-bottom: solid 1px #ccc; |
| 742 |
} |
| 743 |
@top-right { |
| 744 |
content: string(ears-top-right); |
| 745 |
vertical-align: bottom; |
| 746 |
border-bottom: solid 1px #ccc; |
| 747 |
} |
| 748 |
@bottom-left { |
| 749 |
content: string(ears-bottom-left); |
| 750 |
vertical-align: top; |
| 751 |
border-top: solid 1px #ccc; |
| 752 |
} |
| 753 |
@bottom-center { |
| 754 |
content: string(ears-bottom-center); |
| 755 |
vertical-align: top; |
| 756 |
border-top: solid 1px #ccc; |
| 757 |
} |
| 758 |
@bottom-right { |
| 759 |
content: '[Page ' counter(page) ']'; |
| 760 |
vertical-align: top; |
| 761 |
border-top: solid 1px #ccc; |
| 762 |
} |
| 763 |
*/ |
| 764 |
|
| 765 |
} |
| 766 |
|
| 767 |
/* Changes introduced to fix issues found during implementation */ |
| 768 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 769 |
a { |
| 770 |
z-index: 2; |
| 771 |
} |
| 772 |
/* Separate body from document info even without intervening H1 */ |
| 773 |
section { |
| 774 |
clear: both; |
| 775 |
} |
| 776 |
|
| 777 |
|
| 778 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 779 |
.author { |
| 780 |
vertical-align: top; |
| 781 |
} |
| 782 |
|
| 783 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 784 |
#identifiers dt { |
| 785 |
width: 8em; |
| 786 |
} |
| 787 |
|
| 788 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 789 |
#identifiers dd { |
| 790 |
margin-left: 1em; |
| 791 |
} |
| 792 |
|
| 793 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 794 |
#toc { |
| 795 |
background-color: white; |
| 796 |
} |
| 797 |
|
| 798 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 799 |
@media screen and (max-width: 1023px) { |
| 800 |
#toc h2 a, |
| 801 |
#toc h2 a:link, |
| 802 |
#toc h2 a:focus, |
| 803 |
#toc h2 a:hover, |
| 804 |
#toc a.toplink, |
| 805 |
#toc a.toplink:hover { |
| 806 |
color: white; |
| 807 |
background-color: #444; |
| 808 |
text-decoration: none; |
| 809 |
} |
| 810 |
} |
| 811 |
|
| 812 |
/* Give the bottom of the ToC some whitespace */ |
| 813 |
@media screen and (min-width: 1024px) { |
| 814 |
#toc { |
| 815 |
padding: 0 0 1em 1em; |
| 816 |
} |
| 817 |
} |
| 818 |
|
| 819 |
/* Style section numbers with more space between number and title */ |
| 820 |
.section-number { |
| 821 |
padding-right: 0.5em; |
| 822 |
} |
| 823 |
|
| 824 |
/* prevent monospace from becoming overly large */ |
| 825 |
tt, code, pre, code { |
| 826 |
font-size: 95%; |
| 827 |
} |
| 828 |
|
| 829 |
/* Fix the height/width aspect for ascii art*/ |
| 830 |
pre.sourcecode, |
| 831 |
.art-text pre { |
| 832 |
line-height: 1.12; |
| 833 |
} |
| 834 |
|
| 835 |
|
| 836 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 837 |
a.toplink { |
| 838 |
float: right; |
| 839 |
margin-right: 0.5em; |
| 840 |
} |
| 841 |
|
| 842 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 843 |
dl > dt, |
| 844 |
dl.dlParallel > dt { |
| 845 |
float: left; |
| 846 |
margin-right: 1em; |
| 847 |
} |
| 848 |
dl.dlNewline > dt { |
| 849 |
float: none; |
| 850 |
} |
| 851 |
|
| 852 |
/* Provide styling for table cell text alignment */ |
| 853 |
table td.text-left, |
| 854 |
table th.text-left { |
| 855 |
text-align: left; |
| 856 |
} |
| 857 |
table td.text-center, |
| 858 |
table th.text-center { |
| 859 |
text-align: center; |
| 860 |
} |
| 861 |
table td.text-right, |
| 862 |
table th.text-right { |
| 863 |
text-align: right; |
| 864 |
} |
| 865 |
|
| 866 |
/* Make the alternative author contact informatio look less like just another |
| 867 |
author, and group it closer with the primary author contact information */ |
| 868 |
.alternative-contact { |
| 869 |
margin: 0.5em 0 0.25em 0; |
| 870 |
} |
| 871 |
address .non-ascii { |
| 872 |
margin: 0 0 0 2em; |
| 873 |
} |
| 874 |
|
| 875 |
/* With it being possible to set tables with alignment |
| 876 |
left, center, and right, { width: 100%; } does not make sense */ |
| 877 |
table { |
| 878 |
width: auto; |
| 879 |
} |
| 880 |
|
| 881 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 882 |
because of a long floating dt label.*/ |
| 883 |
.references dd { |
| 884 |
overflow: visible; |
| 885 |
} |
| 886 |
|
| 887 |
/* Control caption placement */ |
| 888 |
caption { |
| 889 |
caption-side: bottom; |
| 890 |
} |
| 891 |
|
| 892 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 893 |
script don't end up on the other side of the page. */ |
| 894 |
|
| 895 |
address.vcard { |
| 896 |
max-width: 30em; |
| 897 |
margin-right: auto; |
| 898 |
} |
| 899 |
|
| 900 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 901 |
address div.left { |
| 902 |
text-align: left; |
| 903 |
} |
| 904 |
address div.right { |
| 905 |
text-align: right; |
| 906 |
} |
| 907 |
|
| 908 |
/* Provide table alignment support. We can't use the alignX classes above |
| 909 |
since they do unwanted things with caption and other styling. */ |
| 910 |
table.right { |
| 911 |
margin-left: auto; |
| 912 |
margin-right: 0; |
| 913 |
} |
| 914 |
table.center { |
| 915 |
margin-left: auto; |
| 916 |
margin-right: auto; |
| 917 |
} |
| 918 |
table.left { |
| 919 |
margin-left: 0; |
| 920 |
margin-right: auto; |
| 921 |
} |
| 922 |
|
| 923 |
/* Give the table caption label the same styling as the figcaption */ |
| 924 |
caption a[href] { |
| 925 |
color: #222; |
| 926 |
} |
| 927 |
|
| 928 |
@media print { |
| 929 |
.toplink { |
| 930 |
display: none; |
| 931 |
} |
| 932 |
|
| 933 |
/* avoid overwriting the top border line with the ToC header */ |
| 934 |
#toc { |
| 935 |
padding-top: 1px; |
| 936 |
} |
| 937 |
|
| 938 |
/* Avoid page breaks inside dl and author address entries */ |
| 939 |
.vcard { |
| 940 |
page-break-inside: avoid; |
| 941 |
} |
| 942 |
|
| 943 |
} |
| 944 |
/* Tweak the bcp14 keyword presentation */ |
| 945 |
.bcp14 { |
| 946 |
font-variant: small-caps; |
| 947 |
font-weight: bold; |
| 948 |
font-size: 0.9em; |
| 949 |
} |
| 950 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 951 |
h2 { |
| 952 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 953 |
padding-top: 31px; |
| 954 |
} |
| 955 |
h3 { |
| 956 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 957 |
padding-top: 24px; |
| 958 |
} |
| 959 |
h4 { |
| 960 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 961 |
padding-top: 24px; |
| 962 |
} |
| 963 |
/* Float artwork pilcrow to the right */ |
| 964 |
@media screen { |
| 965 |
.artwork a.pilcrow { |
| 966 |
display: block; |
| 967 |
line-height: 0.7; |
| 968 |
margin-top: 0.15em; |
| 969 |
} |
| 970 |
} |
| 971 |
/* Make pilcrows on dd visible */ |
| 972 |
@media screen { |
| 973 |
dd:hover > a.pilcrow { |
| 974 |
visibility: visible; |
| 975 |
} |
| 976 |
} |
| 977 |
/* Make the placement of figcaption match that of a table's caption |
| 978 |
by removing the figure's added bottom margin */ |
| 979 |
.alignLeft.art-text, |
| 980 |
.alignCenter.art-text, |
| 981 |
.alignRight.art-text { |
| 982 |
margin-bottom: 0; |
| 983 |
} |
| 984 |
.alignLeft, |
| 985 |
.alignCenter, |
| 986 |
.alignRight { |
| 987 |
margin: 1em 0 0 0; |
| 988 |
} |
| 989 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 990 |
possibly even requiring a new line */ |
| 991 |
@media print { |
| 992 |
a.pilcrow { |
| 993 |
display: none; |
| 994 |
} |
| 995 |
} |
| 996 |
/* Styling for the external metadata */ |
| 997 |
div#external-metadata { |
| 998 |
background-color: #eee; |
| 999 |
padding: 0.5em; |
| 1000 |
margin-bottom: 0.5em; |
| 1001 |
display: none; |
| 1002 |
} |
| 1003 |
div#internal-metadata { |
| 1004 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1005 |
} |
| 1006 |
/* Styling for title RFC Number */ |
| 1007 |
h1#rfcnum { |
| 1008 |
clear: both; |
| 1009 |
margin: 0 0 -1em; |
| 1010 |
padding: 1em 0 0 0; |
| 1011 |
} |
| 1012 |
/* Make .olPercent look the same as <ol><li> */ |
| 1013 |
dl.olPercent > dd { |
| 1014 |
margin-bottom: 0.25em; |
| 1015 |
min-height: initial; |
| 1016 |
} |
| 1017 |
/* Give aside some styling to set it apart */ |
| 1018 |
aside { |
| 1019 |
border-left: 1px solid #ddd; |
| 1020 |
margin: 1em 0 1em 2em; |
| 1021 |
padding: 0.2em 2em; |
| 1022 |
} |
| 1023 |
aside > dl, |
| 1024 |
aside > ol, |
| 1025 |
aside > ul, |
| 1026 |
aside > table, |
| 1027 |
aside > p { |
| 1028 |
margin-bottom: 0.5em; |
| 1029 |
} |
| 1030 |
/* Additional page break settings */ |
| 1031 |
@media print { |
| 1032 |
figcaption, table caption { |
| 1033 |
page-break-before: avoid; |
| 1034 |
} |
| 1035 |
} |
| 1036 |
/* Font size adjustments for print */ |
| 1037 |
@media print { |
| 1038 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1039 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1040 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1041 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1042 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1043 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1044 |
} |
| 1045 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1046 |
@media print { |
| 1047 |
.artwork, |
| 1048 |
.sourcecode { |
| 1049 |
margin-bottom: 1em; |
| 1050 |
} |
| 1051 |
} |
| 1052 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1053 |
table { |
| 1054 |
min-width: 20em; |
| 1055 |
} |
| 1056 |
/* ol type a */ |
| 1057 |
ol.type-a { list-style-type: lower-alpha; } |
| 1058 |
ol.type-A { list-style-type: upper-alpha; } |
| 1059 |
ol.type-i { list-style-type: lower-roman; } |
| 1060 |
ol.type-I { list-style-type: lower-roman; } |
| 1061 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1062 |
and increase the contrast between border and odd row background sligthtly */ |
| 1063 |
table { |
| 1064 |
border: 1px solid #ddd; |
| 1065 |
} |
| 1066 |
td { |
| 1067 |
border-top: 1px solid #ddd; |
| 1068 |
} |
| 1069 |
tr:nth-child(2n+1) > td { |
| 1070 |
background-color: #f8f8f8; |
| 1071 |
} |
| 1072 |
/* Use style rules to govern display of the TOC. */ |
| 1073 |
@media screen and (max-width: 1023px) { |
| 1074 |
#toc nav { display: none; } |
| 1075 |
#toc.active nav { display: block; } |
| 1076 |
} |
| 1077 |
/* Add support for keepWithNext */ |
| 1078 |
.keepWithNext { |
| 1079 |
break-after: avoid-page; |
| 1080 |
break-after: avoid-page; |
| 1081 |
} |
| 1082 |
/* Add support for keepWithPrevious */ |
| 1083 |
.keepWithPrevious { |
| 1084 |
break-before: avoid-page; |
| 1085 |
} |
| 1086 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1087 |
figure, pre, table, .artwork, .sourcecode { |
| 1088 |
break-before: avoid-page; |
| 1089 |
break-after: auto; |
| 1090 |
} |
| 1091 |
/* Avoid breaks between <dt> and <dd> */ |
| 1092 |
dl { |
| 1093 |
break-before: auto; |
| 1094 |
break-inside: auto; |
| 1095 |
} |
| 1096 |
dt { |
| 1097 |
break-before: auto; |
| 1098 |
break-after: avoid-page; |
| 1099 |
} |
| 1100 |
dd { |
| 1101 |
break-before: avoid-page; |
| 1102 |
break-after: auto; |
| 1103 |
orphans: 3; |
| 1104 |
widows: 3 |
| 1105 |
} |
| 1106 |
span.break, dd.break { |
| 1107 |
margin-bottom: 0; |
| 1108 |
min-height: 0; |
| 1109 |
break-before: auto; |
| 1110 |
break-inside: auto; |
| 1111 |
break-after: auto; |
| 1112 |
} |
| 1113 |
/* Undo break-before ToC */ |
| 1114 |
@media print { |
| 1115 |
#toc { |
| 1116 |
break-before: auto; |
| 1117 |
} |
| 1118 |
} |
| 1119 |
/* Text in compact lists should not get extra bottim margin space, |
| 1120 |
since that would makes the list not compact */ |
| 1121 |
ul.compact p, .ulCompact p, |
| 1122 |
ol.compact p, .olCompact p { |
| 1123 |
margin: 0; |
| 1124 |
} |
| 1125 |
/* But the list as a whole needs the extra space at the end */ |
| 1126 |
section ul.compact, |
| 1127 |
section .ulCompact, |
| 1128 |
section ol.compact, |
| 1129 |
section .olCompact { |
| 1130 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1131 |
} |
| 1132 |
/* The tt and code background above interferes with for instance table cell |
| 1133 |
backgrounds. Changed to something a bit more selective. */ |
| 1134 |
tt, code { |
| 1135 |
background-color: transparent; |
| 1136 |
} |
| 1137 |
p tt, p code, li tt, li code { |
| 1138 |
background-color: #f8f8f8; |
| 1139 |
} |
| 1140 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1141 |
pre { |
| 1142 |
margin-top: 0.5px; |
| 1143 |
} |
| 1144 |
/* Tweak the comact list text */ |
| 1145 |
ul.compact, .ulCompact, |
| 1146 |
ol.compact, .olCompact, |
| 1147 |
dl.compact, .dlCompact { |
| 1148 |
line-height: normal; |
| 1149 |
} |
| 1150 |
/* Don't add top margin for nested lists */ |
| 1151 |
li > ul, li > ol, li > dl, |
| 1152 |
dd > ul, dd > ol, dd > dl, |
| 1153 |
dl > dd > dl { |
| 1154 |
margin-top: initial; |
| 1155 |
} |
| 1156 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1157 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1158 |
dd > div.artwork:first-child, |
| 1159 |
dd > aside:first-child, |
| 1160 |
dd > figure:first-child, |
| 1161 |
dd > ol:first-child, |
| 1162 |
dd > div:first-child > pre.sourcecode, |
| 1163 |
dd > table:first-child, |
| 1164 |
dd > ul:first-child { |
| 1165 |
clear: left; |
| 1166 |
} |
| 1167 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1168 |
dt+dd:empty::before{ |
| 1169 |
content: "\00a0"; |
| 1170 |
} |
| 1171 |
</style> |
| 1172 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1173 |
<link href="https://dx.doi.org/10.17487/rfc8857" rel="alternate"> |
| 1174 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1175 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-bfcp-websocket-15" rel="prev"> |
| 1176 |
</head> |
| 1177 |
<body> |
| 1178 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1179 |
<table class="ears"> |
| 1180 |
<thead><tr> |
| 1181 |
<td class="left">RFC 8857</td> |
| 1182 |
<td class="center">WebSocket as a Transport for BFCP</td> |
| 1183 |
<td class="right">January 2021</td> |
| 1184 |
</tr></thead> |
| 1185 |
<tfoot><tr> |
| 1186 |
<td class="left">Pascual, et al.</td> |
| 1187 |
<td class="center">Standards Track</td> |
| 1188 |
<td class="right">[Page]</td> |
| 1189 |
</tr></tfoot> |
| 1190 |
</table> |
| 1191 |
<div id="external-metadata" class="document-information"></div> |
| 1192 |
<div id="internal-metadata" class="document-information"> |
| 1193 |
<dl id="identifiers"> |
| 1194 |
<dt class="label-stream">Stream:</dt> |
| 1195 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1196 |
<dt class="label-rfc">RFC:</dt> |
| 1197 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8857" class="eref">8857</a></dd> |
| 1198 |
<dt class="label-category">Category:</dt> |
| 1199 |
<dd class="category">Standards Track</dd> |
| 1200 |
<dt class="label-published">Published:</dt> |
| 1201 |
<dd class="published"> |
| 1202 |
<time datetime="2021-01" class="published">January 2021</time> |
| 1203 |
</dd> |
| 1204 |
<dt class="label-issn">ISSN:</dt> |
| 1205 |
<dd class="issn">2070-1721</dd> |
| 1206 |
<dt class="label-authors">Authors:</dt> |
| 1207 |
<dd class="authors"> |
| 1208 |
<div class="author"> |
| 1209 |
<div class="author-name">V. Pascual</div> |
| 1210 |
<div class="org">Nokia</div> |
| 1211 |
</div> |
| 1212 |
<div class="author"> |
| 1213 |
<div class="author-name">A. Román</div> |
| 1214 |
<div class="org">Quobis</div> |
| 1215 |
</div> |
| 1216 |
<div class="author"> |
| 1217 |
<div class="author-name">S. Cazeaux</div> |
| 1218 |
<div class="org">Orange</div> |
| 1219 |
</div> |
| 1220 |
<div class="author"> |
| 1221 |
<div class="author-name">G. Salgueiro</div> |
| 1222 |
<div class="org">Cisco</div> |
| 1223 |
</div> |
| 1224 |
<div class="author"> |
| 1225 |
<div class="author-name">R. Ravindranath</div> |
| 1226 |
<div class="org">Cisco</div> |
| 1227 |
</div> |
| 1228 |
</dd> |
| 1229 |
</dl> |
| 1230 |
</div> |
| 1231 |
<h1 id="rfcnum">RFC 8857</h1> |
| 1232 |
<h1 id="title">The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)</h1> |
| 1233 |
<section id="section-abstract"> |
| 1234 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1235 |
<p id="section-abstract-1"> The WebSocket protocol enables two-way real-time communication |
| 1236 |
between clients and servers. This document specifies the use of Binary Floor |
| 1237 |
Control Protocol (BFCP) as a new WebSocket subprotocol enabling a reliable |
| 1238 |
transport mechanism between BFCP entities in new scenarios.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1239 |
</section> |
| 1240 |
<div id="status-of-memo"> |
| 1241 |
<section id="section-boilerplate.1"> |
| 1242 |
<h2 id="name-status-of-this-memo"> |
| 1243 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1244 |
</h2> |
| 1245 |
<p id="section-boilerplate.1-1"> |
| 1246 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1247 |
<p id="section-boilerplate.1-2"> |
| 1248 |
This document is a product of the Internet Engineering Task Force |
| 1249 |
(IETF). It represents the consensus of the IETF community. It has |
| 1250 |
received public review and has been approved for publication by |
| 1251 |
the Internet Engineering Steering Group (IESG). Further |
| 1252 |
information on Internet Standards is available in Section 2 of |
| 1253 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1254 |
<p id="section-boilerplate.1-3"> |
| 1255 |
Information about the current status of this document, any |
| 1256 |
errata, and how to provide feedback on it may be obtained at |
| 1257 |
<span><a href="https://www.rfc-editor.org/info/rfc8857">https://www.rfc-editor.org/info/rfc8857</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1258 |
</section> |
| 1259 |
</div> |
| 1260 |
<div id="copyright"> |
| 1261 |
<section id="section-boilerplate.2"> |
| 1262 |
<h2 id="name-copyright-notice"> |
| 1263 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1264 |
</h2> |
| 1265 |
<p id="section-boilerplate.2-1"> |
| 1266 |
Copyright (c) 2021 IETF Trust and the persons identified as the |
| 1267 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1268 |
<p id="section-boilerplate.2-2"> |
| 1269 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1270 |
Provisions Relating to IETF Documents |
| 1271 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1272 |
publication of this document. Please review these documents |
| 1273 |
carefully, as they describe your rights and restrictions with |
| 1274 |
respect to this document. Code Components extracted from this |
| 1275 |
document must include Simplified BSD License text as described in |
| 1276 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1277 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1278 |
</section> |
| 1279 |
</div> |
| 1280 |
<div id="toc"> |
| 1281 |
<section id="section-toc.1"> |
| 1282 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1283 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1284 |
</h2> |
| 1285 |
<nav class="toc"><ul class="ulEmpty compact toc"> |
| 1286 |
<li class="ulEmpty compact toc" id="section-toc.1-1.1"> |
| 1287 |
<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> |
| 1288 |
</li> |
| 1289 |
<li class="ulEmpty compact toc" id="section-toc.1-1.2"> |
| 1290 |
<p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>. <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1291 |
<ul class="ulEmpty compact toc"> |
| 1292 |
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.1"> |
| 1293 |
<p id="section-toc.1-1.2.2.1.1" class="keepWithNext"><a href="#section-2.1" class="xref">2.1</a>. <a href="#name-definitions" class="xref">Definitions</a><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p> |
| 1294 |
</li> |
| 1295 |
</ul> |
| 1296 |
</li> |
| 1297 |
<li class="ulEmpty compact toc" id="section-toc.1-1.3"> |
| 1298 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-the-websocket-protocol" class="xref">The WebSocket Protocol</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1299 |
</li> |
| 1300 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4"> |
| 1301 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-the-websocket-bfcp-subproto" class="xref">The WebSocket BFCP Subprotocol</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1302 |
<ul class="ulEmpty compact toc"> |
| 1303 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.1"> |
| 1304 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-handshake" class="xref">Handshake</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1305 |
</li> |
| 1306 |
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2"> |
| 1307 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-bfcp-encoding" class="xref">BFCP Encoding</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1308 |
</li> |
| 1309 |
</ul> |
| 1310 |
</li> |
| 1311 |
<li class="ulEmpty compact toc" id="section-toc.1-1.5"> |
| 1312 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-transport-reliability" class="xref">Transport Reliability</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1313 |
</li> |
| 1314 |
<li class="ulEmpty compact toc" id="section-toc.1-1.6"> |
| 1315 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-sdp-considerations" class="xref">SDP Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1316 |
<ul class="ulEmpty compact toc"> |
| 1317 |
<li class="ulEmpty compact toc" id="section-toc.1-1.6.2.1"> |
| 1318 |
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>. <a href="#name-transport-negotiation" class="xref">Transport Negotiation</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p> |
| 1319 |
</li> |
| 1320 |
<li class="ulEmpty compact toc" id="section-toc.1-1.6.2.2"> |
| 1321 |
<p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>. <a href="#name-sdp-media-attributes" class="xref">SDP Media Attributes</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p> |
| 1322 |
</li> |
| 1323 |
</ul> |
| 1324 |
</li> |
| 1325 |
<li class="ulEmpty compact toc" id="section-toc.1-1.7"> |
| 1326 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-sdp-offer-answer-procedures" class="xref">SDP Offer/Answer Procedures</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1327 |
<ul class="ulEmpty compact toc"> |
| 1328 |
<li class="ulEmpty compact toc" id="section-toc.1-1.7.2.1"> |
| 1329 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-general" class="xref">General</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p> |
| 1330 |
</li> |
| 1331 |
<li class="ulEmpty compact toc" id="section-toc.1-1.7.2.2"> |
| 1332 |
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-example-usage-of-websocket-" class="xref">Example Usage of 'websocket-uri' SDP Attribute</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p> |
| 1333 |
</li> |
| 1334 |
</ul> |
| 1335 |
</li> |
| 1336 |
<li class="ulEmpty compact toc" id="section-toc.1-1.8"> |
| 1337 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-authentication" class="xref">Authentication</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1338 |
</li> |
| 1339 |
<li class="ulEmpty compact toc" id="section-toc.1-1.9"> |
| 1340 |
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1341 |
</li> |
| 1342 |
<li class="ulEmpty compact toc" id="section-toc.1-1.10"> |
| 1343 |
<p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1344 |
<ul class="ulEmpty compact toc"> |
| 1345 |
<li class="ulEmpty compact toc" id="section-toc.1-1.10.2.1"> |
| 1346 |
<p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>. <a href="#name-registration-of-the-websock" class="xref">Registration of the WebSocket BFCP Subprotocol</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p> |
| 1347 |
</li> |
| 1348 |
<li class="ulEmpty compact toc" id="section-toc.1-1.10.2.2"> |
| 1349 |
<p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>. <a href="#name-registration-of-the-tcp-ws-" class="xref">Registration of the 'TCP/WS/BFCP' and 'TCP/WSS/BFCP' SDP "proto" Values</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p> |
| 1350 |
</li> |
| 1351 |
</ul> |
| 1352 |
</li> |
| 1353 |
<li class="ulEmpty compact toc" id="section-toc.1-1.11"> |
| 1354 |
<p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p> |
| 1355 |
<ul class="ulEmpty compact toc"> |
| 1356 |
<li class="ulEmpty compact toc" id="section-toc.1-1.11.2.1"> |
| 1357 |
<p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.11.2.1.1" class="pilcrow">¶</a></p> |
| 1358 |
</li> |
| 1359 |
<li class="ulEmpty compact toc" id="section-toc.1-1.11.2.2"> |
| 1360 |
<p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.11.2.2.1" class="pilcrow">¶</a></p> |
| 1361 |
</li> |
| 1362 |
</ul> |
| 1363 |
</li> |
| 1364 |
<li class="ulEmpty compact toc" id="section-toc.1-1.12"> |
| 1365 |
<p id="section-toc.1-1.12.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p> |
| 1366 |
</li> |
| 1367 |
<li class="ulEmpty compact toc" id="section-toc.1-1.13"> |
| 1368 |
<p id="section-toc.1-1.13.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.13.1" class="pilcrow">¶</a></p> |
| 1369 |
</li> |
| 1370 |
</ul> |
| 1371 |
</nav> |
| 1372 |
</section> |
| 1373 |
</div> |
| 1374 |
<div id="introduction"> |
| 1375 |
<section id="section-1"> |
| 1376 |
<h2 id="name-introduction"> |
| 1377 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1378 |
</h2> |
| 1379 |
<p id="section-1-1">The WebSocket (WS) protocol <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span> enables |
| 1380 |
two-way message exchange between clients and servers on top of a |
| 1381 |
persistent TCP connection, optionally secured with Transport Layer Security (TLS) |
| 1382 |
<span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>. The initial protocol handshake makes use of |
| 1383 |
Hypertext Transfer Protocol (HTTP) <span>[<a href="#RFC7230" class="xref">RFC7230</a>]</span> semantics, allowing the WebSocket |
| 1384 |
protocol to reuse existing HTTP infrastructure.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1385 |
<p id="section-1-2">The Binary Floor Control Protocol (BFCP) is a protocol to |
| 1386 |
coordinate access to shared resources in a conference. It is |
| 1387 |
defined in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> and is |
| 1388 |
used between floor participants and floor control servers, and |
| 1389 |
between floor chairs (i.e., moderators) and floor control |
| 1390 |
servers.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1391 |
<p id="section-1-3">Modern web browsers include a WebSocket client stack |
| 1392 |
complying with the WebSocket API <span>[<a href="#WS-API" class="xref">WS-API</a>]</span> as |
| 1393 |
specified by the W3C. It is expected that other client |
| 1394 |
applications (those running in personal computers and devices |
| 1395 |
such as smartphones) will also make a WebSocket client stack |
| 1396 |
available. This document extends the applicability of |
| 1397 |
<span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> and |
| 1398 |
<span>[<a href="#RFC8856" class="xref">RFC8856</a>]</span> to enable the |
| 1399 |
usage of BFCP in these scenarios.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1400 |
<p id="section-1-4">The transport over which BFCP entities exchange messages |
| 1401 |
depends on how the clients obtain information to contact the |
| 1402 |
floor control server (e.g., using a Session Description Protocol (SDP) |
| 1403 |
offer/answer exchange per <span>[<a href="#RFC8856" class="xref">RFC8856</a>]</span> or the |
| 1404 |
procedure described in RFC 5018 <span>[<a href="#RFC5018" class="xref">RFC5018</a>]</span>). |
| 1405 |
<span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> defines two transports |
| 1406 |
for BFCP: TCP and UDP. This specification defines a new |
| 1407 |
WebSocket subprotocol (as defined in |
| 1408 |
<span><a href="https://www.rfc-editor.org/rfc/rfc6455#section-1.9" class="relref">Section 1.9</a> of [<a href="#RFC6455" class="xref">RFC6455</a>]</span>) for transporting BFCP messages between a |
| 1409 |
WebSocket client and server. This subprotocol provides a reliable and |
| 1410 |
boundary-preserving transport for BFCP when run on top of TCP. Since WebSocket provides |
| 1411 |
a reliable transport, the extensions defined in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> for sending BFCP over unreliable |
| 1412 |
transports are not applicable.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1413 |
</section> |
| 1414 |
</div> |
| 1415 |
<div id="terminology"> |
| 1416 |
<section id="section-2"> |
| 1417 |
<h2 id="name-terminology"> |
| 1418 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1419 |
</h2> |
| 1420 |
<p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", |
| 1421 |
"<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", |
| 1422 |
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", |
| 1423 |
"<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" |
| 1424 |
in this document are to be interpreted as described in BCP 14 |
| 1425 |
<span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, |
| 1426 |
they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1427 |
<div id="definitions"> |
| 1428 |
<section id="section-2.1"> |
| 1429 |
<h3 id="name-definitions"> |
| 1430 |
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-definitions" class="section-name selfRef">Definitions</a> |
| 1431 |
</h3> |
| 1432 |
<span class="break"></span><dl class="dlParallel" id="section-2.1-1"> |
| 1433 |
<dt id="section-2.1-1.1">BFCP WebSocket Client:</dt> |
| 1434 |
<dd style="margin-left: 3.0em" id="section-2.1-1.2">Any BFCP entity capable |
| 1435 |
of opening outbound connections to WebSocket servers and |
| 1436 |
communicating using the WebSocket BFCP subprotocol as |
| 1437 |
defined by this document.<a href="#section-2.1-1.2" class="pilcrow">¶</a> |
| 1438 |
</dd> |
| 1439 |
<dd class="break"></dd> |
| 1440 |
<dt id="section-2.1-1.3">BFCP WebSocket Server:</dt> |
| 1441 |
<dd style="margin-left: 3.0em" id="section-2.1-1.4">Any BFCP entity capable |
| 1442 |
of listening for inbound connections from WebSocket |
| 1443 |
clients and communicating using the WebSocket BFCP |
| 1444 |
subprotocol as defined by this document.<a href="#section-2.1-1.4" class="pilcrow">¶</a> |
| 1445 |
</dd> |
| 1446 |
<dd class="break"></dd> |
| 1447 |
</dl> |
| 1448 |
</section> |
| 1449 |
</div> |
| 1450 |
</section> |
| 1451 |
</div> |
| 1452 |
<div id="the_websocket_protocol"> |
| 1453 |
<section id="section-3"> |
| 1454 |
<h2 id="name-the-websocket-protocol"> |
| 1455 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-the-websocket-protocol" class="section-name selfRef">The WebSocket Protocol</a> |
| 1456 |
</h2> |
| 1457 |
<p id="section-3-1">The WebSocket protocol <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span> is a |
| 1458 |
transport layer on top of TCP (optionally secured with |
| 1459 |
TLS <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>) in which both client and server exchange |
| 1460 |
message units in both directions. The protocol defines a |
| 1461 |
connection handshake, WebSocket subprotocol and extensions |
| 1462 |
negotiation, a frame format for sending application and control |
| 1463 |
data, a masking mechanism, and status codes for indicating |
| 1464 |
disconnection causes.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1465 |
<p id="section-3-2">The WebSocket connection handshake is based on |
| 1466 |
HTTP <span>[<a href="#RFC7230" class="xref">RFC7230</a>]</span> and utilizes the HTTP GET method with an |
| 1467 |
Upgrade header field. This is sent by the client and then answered |
| 1468 |
by the server (if the negotiation succeeded) with an HTTP 101 |
| 1469 |
status code. Once the handshake is completed, the connection |
| 1470 |
upgrades from HTTP to the WebSocket protocol. This handshake |
| 1471 |
procedure is designed to reuse the existing HTTP infrastructure. |
| 1472 |
During the connection handshake, the client and server agree on the |
| 1473 |
application protocol to use on top of the WebSocket transport. |
| 1474 |
Such an application protocol (also known as a "WebSocket |
| 1475 |
subprotocol") defines the format and semantics of the messages |
| 1476 |
exchanged by the endpoints. This could be a custom protocol or a |
| 1477 |
standardized one (as the WebSocket BFCP subprotocol defined in |
| 1478 |
this document). Once the HTTP 101 response is processed, both |
| 1479 |
the client and server reuse the underlying TCP connection for |
| 1480 |
sending WebSocket messages and control frames to each other. |
| 1481 |
Unlike plain HTTP, this connection is persistent and can be used |
| 1482 |
for multiple message exchanges.<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1483 |
<p id="section-3-3">The WebSocket protocol defines message units to be used by |
| 1484 |
applications for the exchange of data, so it provides a message |
| 1485 |
boundary-preserving transport layer.<a href="#section-3-3" class="pilcrow">¶</a></p> |
| 1486 |
</section> |
| 1487 |
</div> |
| 1488 |
<div id="the_websocket_bfcp_subprotocol"> |
| 1489 |
<section id="section-4"> |
| 1490 |
<h2 id="name-the-websocket-bfcp-subproto"> |
| 1491 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-the-websocket-bfcp-subproto" class="section-name selfRef">The WebSocket BFCP Subprotocol</a> |
| 1492 |
</h2> |
| 1493 |
<p id="section-4-1">The term WebSocket subprotocol refers to an |
| 1494 |
application-level protocol layered on top of a WebSocket |
| 1495 |
connection. This document specifies the WebSocket BFCP |
| 1496 |
subprotocol for carrying BFCP messages over a WebSocket |
| 1497 |
connection.<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 1498 |
<div id="handshake"> |
| 1499 |
<section id="section-4.1"> |
| 1500 |
<h3 id="name-handshake"> |
| 1501 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-handshake" class="section-name selfRef">Handshake</a> |
| 1502 |
</h3> |
| 1503 |
<p id="section-4.1-1">The BFCP WebSocket client and BFCP WebSocket server |
| 1504 |
negotiate usage of the WebSocket BFCP subprotocol during the |
| 1505 |
WebSocket handshake procedure as defined in |
| 1506 |
<span><a href="https://www.rfc-editor.org/rfc/rfc6455#section-1.3" class="relref">Section 1.3</a> of [<a href="#RFC6455" class="xref">RFC6455</a>]</span>. |
| 1507 |
The client <span class="bcp14">MUST</span> include the value |
| 1508 |
"bfcp" in the Sec-WebSocket-Protocol header field in its handshake |
| 1509 |
request. The 101 reply from the server <span class="bcp14">MUST</span> contain "bfcp" in |
| 1510 |
its corresponding Sec-WebSocket-Protocol header field.<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 1511 |
<p id="section-4.1-2">Below is an example of a WebSocket handshake in which the |
| 1512 |
client requests the WebSocket BFCP subprotocol support from |
| 1513 |
the server:<a href="#section-4.1-2" class="pilcrow">¶</a></p> |
| 1514 |
<div class="artwork art-text alignLeft" id="section-4.1-3"> |
| 1515 |
<pre> |
| 1516 |
GET / HTTP/1.1 |
| 1517 |
Host: bfcp-ws.example.com |
| 1518 |
Upgrade: websocket |
| 1519 |
Connection: Upgrade |
| 1520 |
Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ== |
| 1521 |
Origin: http://www.example.com |
| 1522 |
Sec-WebSocket-Protocol: bfcp |
| 1523 |
Sec-WebSocket-Version: 13 |
| 1524 |
</pre><a href="#section-4.1-3" class="pilcrow">¶</a> |
| 1525 |
</div> |
| 1526 |
<p id="section-4.1-4">The handshake response from the server accepting the |
| 1527 |
WebSocket BFCP subprotocol would look as follows:<a href="#section-4.1-4" class="pilcrow">¶</a></p> |
| 1528 |
<div class="artwork art-text alignLeft" id="section-4.1-5"> |
| 1529 |
<pre> |
| 1530 |
HTTP/1.1 101 Switching Protocols |
| 1531 |
Upgrade: websocket |
| 1532 |
Connection: Upgrade |
| 1533 |
Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo= |
| 1534 |
Sec-WebSocket-Protocol: bfcp |
| 1535 |
</pre><a href="#section-4.1-5" class="pilcrow">¶</a> |
| 1536 |
</div> |
| 1537 |
<p id="section-4.1-6">Once the negotiation has been completed, the WebSocket |
| 1538 |
connection is established and can be used for the transport of |
| 1539 |
BFCP messages.<a href="#section-4.1-6" class="pilcrow">¶</a></p> |
| 1540 |
</section> |
| 1541 |
</div> |
| 1542 |
<div id="bfcp_encoding"> |
| 1543 |
<section id="section-4.2"> |
| 1544 |
<h3 id="name-bfcp-encoding"> |
| 1545 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-bfcp-encoding" class="section-name selfRef">BFCP Encoding</a> |
| 1546 |
</h3> |
| 1547 |
<p id="section-4.2-1">BFCP messages use a TLV (Type-Length-Value) binary |
| 1548 |
encoding, therefore BFCP WebSocket clients and BFCP WebSocket |
| 1549 |
servers <span class="bcp14">MUST</span> be transported in unfragmented binary WebSocket |
| 1550 |
frames (FIN: 1, opcode: %x2) to exchange BFCP messages. The |
| 1551 |
WebSocket frame data <span class="bcp14">MUST</span> be a valid BFCP message, so the |
| 1552 |
length of the payload of the WebSocket frame <span class="bcp14">MUST</span> be lower |
| 1553 |
than the maximum size allowed (2<sup>16</sup> +12 bytes) for a BFCP |
| 1554 |
message as described in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>. In addition, the |
| 1555 |
encoding rules for reliable protocols defined in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> |
| 1556 |
<span class="bcp14">MUST</span> be followed.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 1557 |
<p id="section-4.2-2">While this specification assumes that BFCP encoding is only TLV binary, |
| 1558 |
future documents may define other mechanisms, like JSON serialization. |
| 1559 |
If encoding changes, a new subprotocol identifier would need to be selected.<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 1560 |
<p id="section-4.2-3">Each BFCP message <span class="bcp14">MUST</span> be carried within a single WebSocket |
| 1561 |
message, and a WebSocket message <span class="bcp14">MUST NOT</span> contain more than one |
| 1562 |
BFCP message.<a href="#section-4.2-3" class="pilcrow">¶</a></p> |
| 1563 |
</section> |
| 1564 |
</div> |
| 1565 |
</section> |
| 1566 |
</div> |
| 1567 |
<div id="bfcp_websocket_transport"> |
| 1568 |
<section id="section-5"> |
| 1569 |
<h2 id="name-transport-reliability"> |
| 1570 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-transport-reliability" class="section-name selfRef">Transport Reliability</a> |
| 1571 |
</h2> |
| 1572 |
<p id="section-5-1">The WebSocket protocol <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span> provides a reliable transport, and |
| 1573 |
therefore the BFCP WebSocket subprotocol defined by this |
| 1574 |
document also provides reliable BFCP transport. Thus, client and server |
| 1575 |
transactions using the WebSocket protocol for transport <span class="bcp14">MUST</span> follow the |
| 1576 |
procedures for reliable transports as defined in <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> |
| 1577 |
and <span>[<a href="#RFC8856" class="xref">RFC8856</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 1578 |
<p id="section-5-2">BFCP WebSocket clients cannot receive incoming WebSocket |
| 1579 |
connections initiated by any other peer. This means that a BFCP |
| 1580 |
WebSocket client <span class="bcp14">MUST</span> actively initiate a connection towards a |
| 1581 |
BFCP WebSocket server. The BFCP server will have a globally routable address |
| 1582 |
and thus does not require ICE, as clients always initiate connections to it.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 1583 |
</section> |
| 1584 |
</div> |
| 1585 |
<div id="sdp_con"> |
| 1586 |
<section id="section-6"> |
| 1587 |
<h2 id="name-sdp-considerations"> |
| 1588 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-sdp-considerations" class="section-name selfRef">SDP Considerations</a> |
| 1589 |
</h2> |
| 1590 |
<div id="updates_to_rfc_4583bis"> |
| 1591 |
<section id="section-6.1"> |
| 1592 |
<h3 id="name-transport-negotiation"> |
| 1593 |
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-transport-negotiation" class="section-name selfRef">Transport Negotiation</a> |
| 1594 |
</h3> |
| 1595 |
<p id="section-6.1-1">Rules to generate an "m=" line for a BFCP stream are described |
| 1596 |
in <span>[<a href="#RFC8856" class="xref">RFC8856</a>], <a href="https://www.rfc-editor.org/rfc/rfc8856#section-4" class="relref">Section 4</a></span>.<a href="#section-6.1-1" class="pilcrow">¶</a></p> |
| 1597 |
<p id="section-6.1-2">New values are defined for the SDP "proto" field: 'TCP/WS/BFCP' |
| 1598 |
and 'TCP/WSS/BFCP'.<a href="#section-6.1-2" class="pilcrow">¶</a></p> |
| 1599 |
<ul class="ulEmpty normal"> |
| 1600 |
<li class="ulEmpty normal" id="section-6.1-3.1">'TCP/WS/BFCP' is used when BFCP runs on top of WS, which in |
| 1601 |
turn runs on top of TCP.<a href="#section-6.1-3.1" class="pilcrow">¶</a> |
| 1602 |
</li> |
| 1603 |
<li class="ulEmpty normal" id="section-6.1-3.2">'TCP/WSS/BFCP' is used when BFCP runs on top of secure WebSocket (WSS), which |
| 1604 |
in turn runs on top of TLS and TCP.<a href="#section-6.1-3.2" class="pilcrow">¶</a> |
| 1605 |
</li> |
| 1606 |
</ul> |
| 1607 |
<p id="section-6.1-4">The "port" field is set following the rules in Section |
| 1608 |
<a href="https://www.rfc-editor.org/rfc/rfc8856#section-4" class="relref">4</a> and Section |
| 1609 |
<a href="https://www.rfc-editor.org/rfc/rfc8856#section-7.1" class="relref">7.1</a> |
| 1610 |
of <span>[<a href="#RFC8856" class="xref">RFC8856</a>]</span>. Depending on the value |
| 1611 |
of the SDP 'setup' attribute defined in <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>, |
| 1612 |
the "port" field contains the port to which the remote endpoint will |
| 1613 |
direct BFCP messages, or it is irrelevant (i.e., the endpoint will initiate the connection |
| 1614 |
towards the remote endpoint) and should be set to a value of '9', |
| 1615 |
which is the discard port. The 'connection' attribute and port <span class="bcp14">MUST</span> |
| 1616 |
follow the rules of <span>[<a href="#RFC4145" class="xref">RFC4145</a>]</span>.<a href="#section-6.1-4" class="pilcrow">¶</a></p> |
| 1617 |
<p id="section-6.1-5">While this document recommends the use of secure WebSocket (i.e., TCP/WSS) |
| 1618 |
for security reasons, TCP/WS is also permitted so as to achieve maximum |
| 1619 |
compatibility among clients.<a href="#section-6.1-5" class="pilcrow">¶</a></p> |
| 1620 |
</section> |
| 1621 |
</div> |
| 1622 |
<div id="attribute"> |
| 1623 |
<section id="section-6.2"> |
| 1624 |
<h3 id="name-sdp-media-attributes"> |
| 1625 |
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-sdp-media-attributes" class="section-name selfRef">SDP Media Attributes</a> |
| 1626 |
</h3> |
| 1627 |
<p id="section-6.2-1"><span>[<a href="#RFC8124" class="xref">RFC8124</a>]</span> defines a new SDP attribute |
| 1628 |
to indicate the connection Uniform Resource Identifier (URI) for the WebSocket client. |
| 1629 |
The SDP attribute 'websocket-uri' defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8124#section-3" class="relref">Section 3</a> of [<a href="#RFC8124" class="xref">RFC8124</a>]</span> |
| 1630 |
<span class="bcp14">MUST</span> be used when BFCP runs on top of WS or WSS. |
| 1631 |
When the 'websocket-uri' attribute is present in the media section of the SDP, |
| 1632 |
the procedures mentioned in <span><a href="https://www.rfc-editor.org/rfc/rfc8124#section-4" class="relref">Section 4</a> of [<a href="#RFC8124" class="xref">RFC8124</a>]</span> |
| 1633 |
<span class="bcp14">MUST</span> be followed.<a href="#section-6.2-1" class="pilcrow">¶</a></p> |
| 1634 |
</section> |
| 1635 |
</div> |
| 1636 |
</section> |
| 1637 |
</div> |
| 1638 |
<section id="section-7"> |
| 1639 |
<h2 id="name-sdp-offer-answer-procedures"> |
| 1640 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-sdp-offer-answer-procedures" class="section-name selfRef">SDP Offer/Answer Procedures</a> |
| 1641 |
</h2> |
| 1642 |
<div id="general"> |
| 1643 |
<section id="section-7.1"> |
| 1644 |
<h3 id="name-general"> |
| 1645 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-general" class="section-name selfRef">General</a> |
| 1646 |
</h3> |
| 1647 |
<p id="section-7.1-1"> An endpoint (i.e., both the offerer and the answerer) <span class="bcp14">MUST</span> create an SDP media description ("m=" line) |
| 1648 |
for each BFCP-over-WebSocket media stream and <span class="bcp14">MUST</span> assign either a 'TCP/WSS/BFCP' or 'TCP/WS/BFCP' value to the |
| 1649 |
"proto" field of the "m=" line depending on whether the endpoint wishes to use secure WebSocket or WebSocket. |
| 1650 |
Furthermore, the server side, which could be either the offerer or answerer, <span class="bcp14">MUST</span> add a 'websocket-uri' |
| 1651 |
attribute in the media section depending on whether it wishes to use WebSocket or secure WebSocket. This new |
| 1652 |
attribute <span class="bcp14">MUST</span> follow the syntax defined in <span>[<a href="#RFC8124" class="xref">RFC8124</a>]</span>. Additionally, |
| 1653 |
the SDP offer/answer procedures defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8124#section-4" class="relref">Section 4</a> of [<a href="#RFC8124" class="xref">RFC8124</a>]</span> <span class="bcp14">MUST</span> |
| 1654 |
be followed for the "m=" line associated with a BFCP-over-WebSocket media stream.<a href="#section-7.1-1" class="pilcrow">¶</a></p> |
| 1655 |
</section> |
| 1656 |
</div> |
| 1657 |
<div id="example"> |
| 1658 |
<section id="section-7.2"> |
| 1659 |
<h3 id="name-example-usage-of-websocket-"> |
| 1660 |
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-example-usage-of-websocket-" class="section-name selfRef">Example Usage of 'websocket-uri' SDP Attribute</a> |
| 1661 |
</h3> |
| 1662 |
<p id="section-7.2-1">The following is an example of an "m=" line for a BFCP connection. |
| 1663 |
In this example, the offerer sends the SDP with the "proto" field having a |
| 1664 |
value of 'TCP/WSS/BFCP', indicating that the offerer wishes to use secure |
| 1665 |
WebSocket as a transport for the media stream, and the "fmt" field having |
| 1666 |
a value of '*' (for details on the "fmt" field, see |
| 1667 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8856#section-4" class="relref">Section 4</a> of [<a href="#RFC8856" class="xref">RFC8856</a>]</span>).<a href="#section-7.2-1" class="pilcrow">¶</a></p> |
| 1668 |
<div id="section-7.2-2"> |
| 1669 |
<pre class="sourcecode lang-sdp"> |
| 1670 |
Offer (browser): |
| 1671 |
m=application 9 TCP/WSS/BFCP * |
| 1672 |
a=setup:active |
| 1673 |
a=connection:new |
| 1674 |
a=floorctrl:c-only |
| 1675 |
m=audio 55000 RTP/AVP 0 |
| 1676 |
m=video 55002 RTP/AVP 31 |
| 1677 |
|
| 1678 |
Answer (server): |
| 1679 |
m=application 50000 TCP/WSS/BFCP * |
| 1680 |
a=setup:passive |
| 1681 |
a=connection:new |
| 1682 |
a=websocket-uri:wss://bfcp-ws.example.com?token=3170449312 |
| 1683 |
a=floorctrl:s-only |
| 1684 |
a=confid:4321 |
| 1685 |
a=userid:1234 |
| 1686 |
a=floorid:1 m-stream:10 |
| 1687 |
a=floorid:2 m-stream:11 |
| 1688 |
m=audio 50002 RTP/AVP 0 |
| 1689 |
a=label:10 |
| 1690 |
m=video 50004 RTP/AVP 31 |
| 1691 |
a=label:11 |
| 1692 |
</pre><a href="#section-7.2-2" class="pilcrow">¶</a> |
| 1693 |
</div> |
| 1694 |
<p id="section-7.2-3"> |
| 1695 |
It is possible that an endpoint (e.g., a browser) sends an offerless INVITE to the server. |
| 1696 |
In such cases, the server will act as SDP offerer. The server <span class="bcp14">MUST</span> assign the SDP 'setup' |
| 1697 |
attribute with a value of 'passive'. The server <span class="bcp14">MUST</span> have a 'websocket-uri' attribute |
| 1698 |
with a 'ws-URI' or 'wss-URI' value depending on whether the server wishes to use WebSocket or secure WebSocket. |
| 1699 |
This attribute <span class="bcp14">MUST</span> follow the syntax defined in |
| 1700 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8124#section-3" class="relref">Section 3</a> of [<a href="#RFC8124" class="xref">RFC8124</a>]</span>. |
| 1701 |
For BFCP application, the "proto" value in the "m=" line <span class="bcp14">MUST</span> be 'TCP/WSS/BFCP' if WebSocket is over TLS, |
| 1702 |
else it <span class="bcp14">MUST</span> be 'TCP/WS/BFCP'.<a href="#section-7.2-3" class="pilcrow">¶</a></p> |
| 1703 |
</section> |
| 1704 |
</div> |
| 1705 |
</section> |
| 1706 |
<div id="authentication"> |
| 1707 |
<section id="section-8"> |
| 1708 |
<h2 id="name-authentication"> |
| 1709 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-authentication" class="section-name selfRef">Authentication</a> |
| 1710 |
</h2> |
| 1711 |
<p id="section-8-1"><span><a href="https://www.rfc-editor.org/rfc/rfc8855#section-9" class="relref">Section 9</a> of [<a href="#RFC8855" class="xref">RFC8855</a>]</span> |
| 1712 |
states that BFCP clients and floor control servers <span class="bcp14">SHOULD</span> |
| 1713 |
authenticate each other prior to accepting messages, and |
| 1714 |
RECOMMENDS that mutual TLS/DTLS authentication be used. However, |
| 1715 |
browser-based WebSocket clients have no control over the use of |
| 1716 |
TLS in the WebSocket API <span>[<a href="#WS-API" class="xref">WS-API</a>]</span>, so it is |
| 1717 |
<span class="bcp14">RECOMMENDED</span> that standard web-based methods for client and |
| 1718 |
server authentication are used, as follows.<a href="#section-8-1" class="pilcrow">¶</a></p> |
| 1719 |
<p id="section-8-2">When a BFCP WebSocket client connects to a BFCP WebSocket |
| 1720 |
server, it <span class="bcp14">SHOULD</span> use TCP/WSS as its transport. If the signaling |
| 1721 |
or control protocol traffic used to set up the conference is authenticated |
| 1722 |
and confidentiality and integrity protected, secure WebSocket (WSS) <span class="bcp14">MUST</span> be used, |
| 1723 |
and the floor control server <span class="bcp14">MUST</span> authenticate the client. The WebSocket client |
| 1724 |
<span class="bcp14">MUST</span> follow the procedures in <span>[<a href="#RFC7525" class="xref">RFC7525</a>]</span> while setting up TLS |
| 1725 |
connection with the WebSocket server. |
| 1726 |
The BFCP client validates the server by means of verifying the server certificate. |
| 1727 |
This means the 'websocket-uri' value <span class="bcp14">MUST</span> contain a hostname. |
| 1728 |
The verification process does not use "a=fingerprint".<a href="#section-8-2" class="pilcrow">¶</a></p> |
| 1729 |
<p id="section-8-3">A floor control server that receives a message over TCP/WS |
| 1730 |
can mandate the use of TCP/WSS by generating an Error message, |
| 1731 |
as described in <span><a href="https://www.rfc-editor.org/rfc/rfc8855#section-13.8" class="relref">Section 13.8</a> of [<a href="#RFC8855" class="xref">RFC8855</a>]</span>, |
| 1732 |
with an error code with a value of 9 (Use TLS).<a href="#section-8-3" class="pilcrow">¶</a></p> |
| 1733 |
<p id="section-8-4">Prior to sending BFCP requests, a BFCP WebSocket client |
| 1734 |
connects to a BFCP WebSocket server and performs the connection |
| 1735 |
handshake. As described in <a href="#handshake" class="xref">Section 4.1</a>, the handshake procedure |
| 1736 |
involves an HTTP GET method request from the client and a |
| 1737 |
response from the server including an HTTP 101 status code.<a href="#section-8-4" class="pilcrow">¶</a></p> |
| 1738 |
<p id="section-8-5">In order to authorize the WebSocket connection, the BFCP |
| 1739 |
WebSocket server <span class="bcp14">SHOULD</span> inspect any cookie header fields |
| 1740 |
<span>[<a href="#RFC6265" class="xref">RFC6265</a>]</span> present in the HTTP GET request. For many web |
| 1741 |
applications, the value of such a cookie is provided by the web |
| 1742 |
server once the user has authenticated themselves to the web |
| 1743 |
server, which could be done by many existing mechanisms. As an |
| 1744 |
alternative method, the BFCP WebSocket server could request HTTP |
| 1745 |
authentication by replying to the client's GET method request |
| 1746 |
with an HTTP 401 status code. The WebSocket protocol <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span> |
| 1747 |
covers this usage in Section <a href="https://www.rfc-editor.org/rfc/rfc6455#section-4.1" class="relref">4.1</a>:<a href="#section-8-5" class="pilcrow">¶</a></p> |
| 1748 |
<ul class="ulEmpty normal"> |
| 1749 |
<li class="ulEmpty normal" id="section-8-6.1">If the status code received from the server is not 101, |
| 1750 |
the WebSocket client stack handles the response per HTTP |
| 1751 |
<span>[<a href="#RFC7230" class="xref">RFC7230</a>]</span> procedures; in particular, the |
| 1752 |
client might perform authentication if it receives an 401 |
| 1753 |
status code. The WebSocket clients are vulnerable to the attacks |
| 1754 |
of basic authentication (mentioned in <span><a href="https://www.rfc-editor.org/rfc/rfc7617#section-4" class="relref">Section 4</a> of [<a href="#RFC7617" class="xref">RFC7617</a>]</span>) and |
| 1755 |
digest authentication (mentioned in <span><a href="https://www.rfc-editor.org/rfc/rfc7616#section-5" class="relref">Section 5</a> of [<a href="#RFC7616" class="xref">RFC7616</a>]</span>). To overcome |
| 1756 |
some of these weaknesses, WebSocket clients can use the |
| 1757 |
HTTP Origin-Bound Authentication (HOBA) mechanism mentioned in |
| 1758 |
<span>[<a href="#RFC7486" class="xref">RFC7486</a>]</span>, for example.<a href="#section-8-6.1" class="pilcrow">¶</a> |
| 1759 |
</li> |
| 1760 |
</ul> |
| 1761 |
</section> |
| 1762 |
</div> |
| 1763 |
<div id="security_considerations"> |
| 1764 |
<section id="section-9"> |
| 1765 |
<h2 id="name-security-considerations"> |
| 1766 |
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 1767 |
</h2> |
| 1768 |
<p id="section-9-1">Considerations from <span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span>, |
| 1769 |
<span>[<a href="#RFC8856" class="xref">RFC8856</a>]</span>, and <span>[<a href="#RFC5018" class="xref">RFC5018</a>]</span> apply.<a href="#section-9-1" class="pilcrow">¶</a></p> |
| 1770 |
<p id="section-9-2">BFCP relies on lower-layer security mechanisms to provide |
| 1771 |
replay and integrity protection and confidentiality. It is |
| 1772 |
<span class="bcp14">RECOMMENDED</span> that the BFCP traffic transported over WebSocket |
| 1773 |
be protected by using a Secure WebSocket |
| 1774 |
connection (using TLS <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span> over TCP). The security |
| 1775 |
considerations in <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span> apply for BFCP over WebSocket as well. |
| 1776 |
The security model here is a typical webserver-client model |
| 1777 |
where the client validates the server certificate and then connects to the server. |
| 1778 |
<a href="#authentication" class="xref">Section 8</a> describes the authentication procedures between client |
| 1779 |
and server.<a href="#section-9-2" class="pilcrow">¶</a></p> |
| 1780 |
<p id="section-9-3">When using BFCP over WebSocket, the security mechanisms defined in |
| 1781 |
<span>[<a href="#RFC8855" class="xref">RFC8855</a>]</span> are not used. Instead, the |
| 1782 |
application is required to build and rely on the security mechanisms in <span>[<a href="#RFC6455" class="xref">RFC6455</a>]</span>.<a href="#section-9-3" class="pilcrow">¶</a></p> |
| 1783 |
<p id="section-9-4">The rest of this section analyses the threats described in |
| 1784 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8855#section-14" class="relref">Section 14</a> of [<a href="#RFC8855" class="xref">RFC8855</a>]</span> when WebSocket is used as a transport |
| 1785 |
protocol for BFCP.<a href="#section-9-4" class="pilcrow">¶</a></p> |
| 1786 |
<p id="section-9-5">An attacker attempting to impersonate a floor control server is |
| 1787 |
avoided by having servers accept BFCP messages over WSS |
| 1788 |
only. As with any other web connection, the clients will verify the server's |
| 1789 |
certificate. The BFCP WebSocket client <span class="bcp14">MUST</span> follow the |
| 1790 |
procedures in <span>[<a href="#RFC7525" class="xref">RFC7525</a>]</span> (including hostname verification as per |
| 1791 |
<span><a href="https://www.rfc-editor.org/rfc/rfc7525#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC7525" class="xref">RFC7525</a>]</span>) while setting up a TLS connection with floor |
| 1792 |
control WebSocket server.<a href="#section-9-5" class="pilcrow">¶</a></p> |
| 1793 |
<p id="section-9-6">An attacker attempting to impersonate a floor control client is avoided by |
| 1794 |
having servers accept BFCP messages over WSS only. As described in |
| 1795 |
<span><a href="https://www.rfc-editor.org/rfc/rfc6455#section-10.5" class="relref">Section 10.5</a> of [<a href="#RFC6455" class="xref">RFC6455</a>]</span> the floor control server can use |
| 1796 |
any client authentication mechanism and follow the steps in <a href="#authentication" class="xref">Section 8</a> |
| 1797 |
of this document.<a href="#section-9-6" class="pilcrow">¶</a></p> |
| 1798 |
<p id="section-9-7">Attackers may attempt to modify messages exchanged by a client and a |
| 1799 |
floor control server. This can be prevented by having WSS between client and server.<a href="#section-9-7" class="pilcrow">¶</a></p> |
| 1800 |
<p id="section-9-8">An attacker trying to replay the messages is prevented by |
| 1801 |
having floor control servers check that messages arriving over a |
| 1802 |
given WSS connection use an authorized user ID.<a href="#section-9-8" class="pilcrow">¶</a></p> |
| 1803 |
<p id="section-9-9">Attackers may eavesdrop on the network to get access |
| 1804 |
to confidential information between the floor control server and a |
| 1805 |
client (e.g., why a floor request was denied). In order to ensure that |
| 1806 |
BFCP users are getting the level of protection that they would get using |
| 1807 |
BFCP directly, applications need to have a way to |
| 1808 |
control the WebSocket libraries to use encryption algorithms specified in |
| 1809 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8855#section-7" class="relref">Section 7</a> of [<a href="#RFC8855" class="xref">RFC8855</a>]</span>. Since the |
| 1810 |
WebSocket API <span>[<a href="#WS-API" class="xref">WS-API</a>]</span> does not have a way to allow an |
| 1811 |
application to select the encryption algorithm to be used, the protection level |
| 1812 |
provided when WSS is used is limited to the underlying TLS algorithm used by |
| 1813 |
the WebSocket library.<a href="#section-9-9" class="pilcrow">¶</a></p> |
| 1814 |
</section> |
| 1815 |
</div> |
| 1816 |
<div id="iana_considerations"> |
| 1817 |
<section id="section-10"> |
| 1818 |
<h2 id="name-iana-considerations"> |
| 1819 |
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 1820 |
</h2> |
| 1821 |
<section id="section-10.1"> |
| 1822 |
<h3 id="name-registration-of-the-websock"> |
| 1823 |
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-registration-of-the-websock" class="section-name selfRef">Registration of the WebSocket BFCP Subprotocol</a> |
| 1824 |
</h3> |
| 1825 |
<p id="section-10.1-1">IANA has registered the WebSocket |
| 1826 |
BFCP subprotocol under the "WebSocket Subprotocol Name Registry" |
| 1827 |
as follows:<a href="#section-10.1-1" class="pilcrow">¶</a></p> |
| 1828 |
<span class="break"></span><dl class="dlParallel" id="section-10.1-2"> |
| 1829 |
<dt id="section-10.1-2.1">Subprotocol Identifier:</dt> |
| 1830 |
<dd style="margin-left: 1.5em" id="section-10.1-2.2">bfcp<a href="#section-10.1-2.2" class="pilcrow">¶</a> |
| 1831 |
</dd> |
| 1832 |
<dd class="break"></dd> |
| 1833 |
<dt id="section-10.1-2.3">Subprotocol Common Name:</dt> |
| 1834 |
<dd style="margin-left: 1.5em" id="section-10.1-2.4">WebSocket Transport |
| 1835 |
for BFCP (Binary Floor Control Protocol)<a href="#section-10.1-2.4" class="pilcrow">¶</a> |
| 1836 |
</dd> |
| 1837 |
<dd class="break"></dd> |
| 1838 |
<dt id="section-10.1-2.5">Subprotocol Definition:</dt> |
| 1839 |
<dd style="margin-left: 1.5em" id="section-10.1-2.6">RFC 8857<a href="#section-10.1-2.6" class="pilcrow">¶</a> |
| 1840 |
</dd> |
| 1841 |
<dd class="break"></dd> |
| 1842 |
</dl> |
| 1843 |
</section> |
| 1844 |
<section id="section-10.2"> |
| 1845 |
<h3 id="name-registration-of-the-tcp-ws-"> |
| 1846 |
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-registration-of-the-tcp-ws-" class="section-name selfRef">Registration of the 'TCP/WS/BFCP' and 'TCP/WSS/BFCP' SDP "proto" Values</a> |
| 1847 |
</h3> |
| 1848 |
<p id="section-10.2-1">This document defines two new values for the SDP "proto" |
| 1849 |
subregistry within the "Session Description Protocol (SDP) Parameters" |
| 1850 |
registry. The resulting entries are shown in <a href="#IANA_SDP_proto" class="xref">Table 1</a>:<a href="#section-10.2-1" class="pilcrow">¶</a></p> |
| 1851 |
<span id="name-values-for-the-sdp-proto-fi"></span><div id="IANA_SDP_proto"> |
| 1852 |
<table class="center" id="table-1"> |
| 1853 |
<caption> |
| 1854 |
<a href="#table-1" class="selfRef">Table 1</a>: |
| 1855 |
<a href="#name-values-for-the-sdp-proto-fi" class="selfRef">Values for the SDP "proto" Field</a> |
| 1856 |
</caption> |
| 1857 |
<thead> |
| 1858 |
<tr> |
| 1859 |
<th class="text-left" rowspan="1" colspan="1">Value</th> |
| 1860 |
<th class="text-left" rowspan="1" colspan="1">Reference</th> |
| 1861 |
</tr> |
| 1862 |
</thead> |
| 1863 |
<tbody> |
| 1864 |
<tr> |
| 1865 |
<td class="text-left" rowspan="1" colspan="1">TCP/WS/BFCP</td> |
| 1866 |
<td class="text-left" rowspan="1" colspan="1">RFC 8857</td> |
| 1867 |
</tr> |
| 1868 |
<tr> |
| 1869 |
<td class="text-left" rowspan="1" colspan="1">TCP/WSS/BFCP</td> |
| 1870 |
<td class="text-left" rowspan="1" colspan="1">RFC 8857</td> |
| 1871 |
</tr> |
| 1872 |
</tbody> |
| 1873 |
</table> |
| 1874 |
</div> |
| 1875 |
</section> |
| 1876 |
</section> |
| 1877 |
</div> |
| 1878 |
<section id="section-11"> |
| 1879 |
<h2 id="name-references"> |
| 1880 |
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 1881 |
</h2> |
| 1882 |
<section id="section-11.1"> |
| 1883 |
<h3 id="name-normative-references"> |
| 1884 |
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 1885 |
</h3> |
| 1886 |
<dl class="references"> |
| 1887 |
<dt id="RFC2119">[RFC2119]</dt> |
| 1888 |
<dd> |
| 1889 |
<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> |
| 1890 |
<dd class="break"></dd> |
| 1891 |
<dt id="RFC4145">[RFC4145]</dt> |
| 1892 |
<dd> |
| 1893 |
<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> |
| 1894 |
<dd class="break"></dd> |
| 1895 |
<dt id="RFC5018">[RFC5018]</dt> |
| 1896 |
<dd> |
| 1897 |
<span class="refAuthor">Camarillo, G.</span>, <span class="refTitle">"Connection Establishment in the Binary Floor Control Protocol (BFCP)"</span>, <span class="seriesInfo">RFC 5018</span>, <span class="seriesInfo">DOI 10.17487/RFC5018</span>, <time datetime="2007-09" class="refDate">September 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5018">https://www.rfc-editor.org/info/rfc5018</a>></span>. </dd> |
| 1898 |
<dd class="break"></dd> |
| 1899 |
<dt id="RFC6455">[RFC6455]</dt> |
| 1900 |
<dd> |
| 1901 |
<span class="refAuthor">Fette, I.</span><span class="refAuthor"> and A. Melnikov</span>, <span class="refTitle">"The WebSocket Protocol"</span>, <span class="seriesInfo">RFC 6455</span>, <span class="seriesInfo">DOI 10.17487/RFC6455</span>, <time datetime="2011-12" class="refDate">December 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6455">https://www.rfc-editor.org/info/rfc6455</a>></span>. </dd> |
| 1902 |
<dd class="break"></dd> |
| 1903 |
<dt id="RFC7525">[RFC7525]</dt> |
| 1904 |
<dd> |
| 1905 |
<span class="refAuthor">Sheffer, Y.</span><span class="refAuthor">, Holz, R.</span><span class="refAuthor">, and P. Saint-Andre</span>, <span class="refTitle">"Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">BCP 195</span>, <span class="seriesInfo">RFC 7525</span>, <span class="seriesInfo">DOI 10.17487/RFC7525</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7525">https://www.rfc-editor.org/info/rfc7525</a>></span>. </dd> |
| 1906 |
<dd class="break"></dd> |
| 1907 |
<dt id="RFC8124">[RFC8124]</dt> |
| 1908 |
<dd> |
| 1909 |
<span class="refAuthor">Ravindranath, R.</span><span class="refAuthor"> and G. Salgueiro</span>, <span class="refTitle">"The Session Description Protocol (SDP) WebSocket Connection URI Attribute"</span>, <span class="seriesInfo">RFC 8124</span>, <span class="seriesInfo">DOI 10.17487/RFC8124</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8124">https://www.rfc-editor.org/info/rfc8124</a>></span>. </dd> |
| 1910 |
<dd class="break"></dd> |
| 1911 |
<dt id="RFC8174">[RFC8174]</dt> |
| 1912 |
<dd> |
| 1913 |
<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> |
| 1914 |
<dd class="break"></dd> |
| 1915 |
<dt id="RFC8855">[RFC8855]</dt> |
| 1916 |
<dd> |
| 1917 |
<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> |
| 1918 |
<dd class="break"></dd> |
| 1919 |
<dt id="RFC8856">[RFC8856]</dt> |
| 1920 |
<dd> |
| 1921 |
<span class="refAuthor">Camarillo, G.</span><span class="refAuthor">, Kristensen, T.</span><span class="refAuthor">, and C. Holmberg</span>, <span class="refTitle">"Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams"</span>, <span class="seriesInfo">RFC 8856</span>, <span class="seriesInfo">DOI 10.17487/RFC8856</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8856">https://www.rfc-editor.org/info/rfc8856</a>></span>. </dd> |
| 1922 |
<dd class="break"></dd> |
| 1923 |
</dl> |
| 1924 |
</section> |
| 1925 |
<section id="section-11.2"> |
| 1926 |
<h3 id="name-informative-references"> |
| 1927 |
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 1928 |
</h3> |
| 1929 |
<dl class="references"> |
| 1930 |
<dt id="RFC6265">[RFC6265]</dt> |
| 1931 |
<dd> |
| 1932 |
<span class="refAuthor">Barth, A.</span>, <span class="refTitle">"HTTP State Management Mechanism"</span>, <span class="seriesInfo">RFC 6265</span>, <span class="seriesInfo">DOI 10.17487/RFC6265</span>, <time datetime="2011-04" class="refDate">April 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6265">https://www.rfc-editor.org/info/rfc6265</a>></span>. </dd> |
| 1933 |
<dd class="break"></dd> |
| 1934 |
<dt id="RFC7230">[RFC7230]</dt> |
| 1935 |
<dd> |
| 1936 |
<span class="refAuthor">Fielding, R., Ed.</span><span class="refAuthor"> and J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</span>, <span class="seriesInfo">RFC 7230</span>, <span class="seriesInfo">DOI 10.17487/RFC7230</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>></span>. </dd> |
| 1937 |
<dd class="break"></dd> |
| 1938 |
<dt id="RFC7486">[RFC7486]</dt> |
| 1939 |
<dd> |
| 1940 |
<span class="refAuthor">Farrell, S.</span><span class="refAuthor">, Hoffman, P.</span><span class="refAuthor">, and M. Thomas</span>, <span class="refTitle">"HTTP Origin-Bound Authentication (HOBA)"</span>, <span class="seriesInfo">RFC 7486</span>, <span class="seriesInfo">DOI 10.17487/RFC7486</span>, <time datetime="2015-03" class="refDate">March 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7486">https://www.rfc-editor.org/info/rfc7486</a>></span>. </dd> |
| 1941 |
<dd class="break"></dd> |
| 1942 |
<dt id="RFC7616">[RFC7616]</dt> |
| 1943 |
<dd> |
| 1944 |
<span class="refAuthor">Shekh-Yusef, R., Ed.</span><span class="refAuthor">, Ahrens, D.</span><span class="refAuthor">, and S. Bremer</span>, <span class="refTitle">"HTTP Digest Access Authentication"</span>, <span class="seriesInfo">RFC 7616</span>, <span class="seriesInfo">DOI 10.17487/RFC7616</span>, <time datetime="2015-09" class="refDate">September 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7616">https://www.rfc-editor.org/info/rfc7616</a>></span>. </dd> |
| 1945 |
<dd class="break"></dd> |
| 1946 |
<dt id="RFC7617">[RFC7617]</dt> |
| 1947 |
<dd> |
| 1948 |
<span class="refAuthor">Reschke, J.</span>, <span class="refTitle">"The 'Basic' HTTP Authentication Scheme"</span>, <span class="seriesInfo">RFC 7617</span>, <span class="seriesInfo">DOI 10.17487/RFC7617</span>, <time datetime="2015-09" class="refDate">September 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7617">https://www.rfc-editor.org/info/rfc7617</a>></span>. </dd> |
| 1949 |
<dd class="break"></dd> |
| 1950 |
<dt id="RFC8446">[RFC8446]</dt> |
| 1951 |
<dd> |
| 1952 |
<span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>></span>. </dd> |
| 1953 |
<dd class="break"></dd> |
| 1954 |
<dt id="WS-API">[WS-API]</dt> |
| 1955 |
<dd> |
| 1956 |
<span class="refAuthor">Hickson, I., Ed.</span>, <span class="refTitle">"The WebSocket API"</span>, <span class="refContent">W3C Candidate Recommendation, September 2012</span>, <span><<a href="https://www.w3.org/TR/2012/CR-websockets-20120920/">https://www.w3.org/TR/2012/CR-websockets-20120920/</a>></span>. </dd> |
| 1957 |
<dd class="break"></dd> |
| 1958 |
</dl> |
| 1959 |
</section> |
| 1960 |
</section> |
| 1961 |
<div id="acknowledgements"> |
| 1962 |
<section id="section-appendix.a"> |
| 1963 |
<h2 id="name-acknowledgements"> |
| 1964 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 1965 |
</h2> |
| 1966 |
<p id="section-appendix.a-1">The authors want to thank <span class="contact-name">Robert Welbourn</span> from Acme Packet and |
| 1967 |
<span class="contact-name">Sergio Garcia Murillo</span>, |
| 1968 |
who made significant contributions to the first draft version of |
| 1969 |
this document. This work benefited from the thorough review |
| 1970 |
and constructive comments of <span class="contact-name">Charles Eckel</span>, <span class="contact-name">Christer Holmberg</span>, |
| 1971 |
<span class="contact-name">Paul Kyzivat</span>, <span class="contact-name">Dan Wing</span>, and <span class="contact-name">Alissa Cooper</span>. |
| 1972 |
Thanks to <span class="contact-name">Bert Wijnen</span>, <span class="contact-name">Robert Sparks</span>, and <span class="contact-name">Mirja Kühlewind</span> |
| 1973 |
for their reviews and comments on this document.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p> |
| 1974 |
<p id="section-appendix.a-2"> Thanks to <span class="contact-name">Spencer Dawkins</span>, <span class="contact-name">Ben Campbell</span>, |
| 1975 |
<span class="contact-name">Kathleen Moriarty</span>, <span class="contact-name">Alexey Melnikov</span>, <span class="contact-name">Jari Arkko</span>, |
| 1976 |
and <span class="contact-name">Stephen Farrell</span> for |
| 1977 |
their feedback and comments during IESG reviews.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p> |
| 1978 |
</section> |
| 1979 |
</div> |
| 1980 |
<div id="authors-addresses"> |
| 1981 |
<section id="section-appendix.b"> |
| 1982 |
<h2 id="name-authors-addresses"> |
| 1983 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 1984 |
</h2> |
| 1985 |
<address class="vcard"> |
| 1986 |
<div dir="auto" class="left"><span class="fn nameRole">Victor Pascual</span></div> |
| 1987 |
<div dir="auto" class="left"><span class="org">Nokia</span></div> |
| 1988 |
<div dir="auto" class="left"> |
| 1989 |
<span class="locality">Barcelona</span> </div> |
| 1990 |
<div dir="auto" class="left"><span class="country-name">Spain</span></div> |
| 1991 |
<div class="email"> |
| 1992 |
<span>Email:</span> |
| 1993 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 1994 |
</div> |
| 1995 |
</address> |
| 1996 |
<address class="vcard"> |
| 1997 |
<div dir="auto" class="left"><span class="fn nameRole">Antón Román</span></div> |
| 1998 |
<div dir="auto" class="left"><span class="org">Quobis</span></div> |
| 1999 |
<div dir="auto" class="left"><span class="extended-address">Pol. Ind. A Granxa, Casa de Pedra</span></div> |
| 2000 |
<div dir="auto" class="left"> |
| 2001 |
<span class="postal-code">36475</span> <span class="locality">O Porriño</span> </div> |
| 2002 |
<div dir="auto" class="left"><span class="country-name">Spain</span></div> |
| 2003 |
<div class="email"> |
| 2004 |
<span>Email:</span> |
| 2005 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2006 |
</div> |
| 2007 |
</address> |
| 2008 |
<address class="vcard"> |
| 2009 |
<div dir="auto" class="left"><span class="fn nameRole">Stéphane Cazeaux</span></div> |
| 2010 |
<div dir="auto" class="left"><span class="org">Orange</span></div> |
| 2011 |
<div dir="auto" class="left"><span class="street-address">42 rue des Coutures</span></div> |
| 2012 |
<div dir="auto" class="left"> |
| 2013 |
<span class="postal-code">14000</span> <span class="locality">Caen</span> |
| 2014 |
</div> |
| 2015 |
<div dir="auto" class="left"><span class="country-name">France</span></div> |
| 2016 |
<div class="email"> |
| 2017 |
<span>Email:</span> |
| 2018 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2019 |
</div> |
| 2020 |
</address> |
| 2021 |
<address class="vcard"> |
| 2022 |
<div dir="auto" class="left"><span class="fn nameRole">Gonzalo Salgueiro</span></div> |
| 2023 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2024 |
<div dir="auto" class="left"><span class="street-address">7200-12 Kit Creek Road</span></div> |
| 2025 |
<div dir="auto" class="left"> |
| 2026 |
<span class="locality">Research Triangle Park</span>, <span class="region">NC</span> <span class="postal-code">27709</span> |
| 2027 |
</div> |
| 2028 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2029 |
<div class="email"> |
| 2030 |
<span>Email:</span> |
| 2031 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2032 |
</div> |
| 2033 |
</address> |
| 2034 |
<address class="vcard"> |
| 2035 |
<div dir="auto" class="left"><span class="fn nameRole">Ram Mohan Ravindranath</span></div> |
| 2036 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2037 |
<div dir="auto" class="left"><span class="extended-address">Cessna Business Park<br>Kadabeesanahalli Village, Varthur Hobli,</span></div> |
| 2038 |
<div dir="auto" class="left"><span class="street-address">Sarjapur-Marathahalli Outer Ring Road</span></div> |
| 2039 |
<div dir="auto" class="left"> |
| 2040 |
<span class="locality">Bangalore</span> <span class="postal-code">560103</span> |
| 2041 |
</div> |
| 2042 |
<div dir="auto" class="left"><span class="region">Karnataka</span></div> |
| 2043 |
<div dir="auto" class="left"><span class="country-name">India</span></div> |
| 2044 |
<div class="email"> |
| 2045 |
<span>Email:</span> |
| 2046 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2047 |
</div> |
| 2048 |
</address> |
| 2049 |
</section> |
| 2050 |
</div> |
| 2051 |
<script>const toc = document.getElementById("toc"); |
| 2052 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2053 |
toc.classList.toggle("active"); |
| 2054 |
}); |
| 2055 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2056 |
toc.classList.remove("active"); |
| 2057 |
}); |
| 2058 |
</script> |
| 2059 |
</body> |
| 2060 |
</html> |