| 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 8839: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)</title> |
| 8 |
<meta content="Marc Petit-Huguenin" name="author"> |
| 9 |
<meta content="Suhas Nandakumar" name="author"> |
| 10 |
<meta content="Christer Holmberg" name="author"> |
| 11 |
<meta content="Ari Keränen" name="author"> |
| 12 |
<meta content="Roman Shpount" name="author"> |
| 13 |
<meta content=" |
| 14 |
|
| 15 |
This document describes Session Description Protocol (SDP) Offer/Answer |
| 16 |
procedures for carrying out Interactive Connectivity Establishment (ICE) |
| 17 |
between the agents. |
| 18 |
|
| 19 |
|
| 20 |
This document obsoletes RFCs 5245 and 6336. |
| 21 |
|
| 22 |
" name="description"> |
| 23 |
<meta content="xml2rfc 3.5.0" name="generator"> |
| 24 |
<meta content="SIP" name="keyword"> |
| 25 |
<meta content="Session Initial Protocol" name="keyword"> |
| 26 |
<meta content="8839" name="rfc.number"> |
| 27 |
<!-- Generator version information: |
| 28 |
xml2rfc 3.5.0 |
| 29 |
Python 3.6.10 |
| 30 |
appdirs 1.4.4 |
| 31 |
ConfigArgParse 1.2.3 |
| 32 |
google-i18n-address 2.3.5 |
| 33 |
html5lib 1.0.1 |
| 34 |
intervaltree 3.0.2 |
| 35 |
Jinja2 2.11.2 |
| 36 |
kitchen 1.2.6 |
| 37 |
lxml 4.4.2 |
| 38 |
pycairo 1.19.0 |
| 39 |
pycountry 19.8.18 |
| 40 |
pyflakes 2.1.1 |
| 41 |
PyYAML 5.3.1 |
| 42 |
requests 2.22.0 |
| 43 |
setuptools 40.6.2 |
| 44 |
six 1.14.0 |
| 45 |
WeasyPrint 51 |
| 46 |
--> |
| 47 |
<link href="rfc8839.xml" rel="alternate" type="application/rfc+xml"> |
| 48 |
<link href="#copyright" rel="license"> |
| 49 |
<style type="text/css">/* |
| 50 |
|
| 51 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 52 |
|
| 53 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 54 |
this can be consolidated so that style settings occur only in one place, but |
| 55 |
for now the contents of this file consists first of the initial CSS work as |
| 56 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 57 |
commented changes found necssary during the development of the v3 |
| 58 |
formatters. |
| 59 |
|
| 60 |
*/ |
| 61 |
|
| 62 |
/* fonts */ |
| 63 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 64 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 65 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 66 |
|
| 67 |
@viewport { |
| 68 |
zoom: 1.0; |
| 69 |
width: extend-to-zoom; |
| 70 |
} |
| 71 |
@-ms-viewport { |
| 72 |
width: extend-to-zoom; |
| 73 |
zoom: 1.0; |
| 74 |
} |
| 75 |
/* general and mobile first */ |
| 76 |
html { |
| 77 |
} |
| 78 |
body { |
| 79 |
max-width: 90%; |
| 80 |
margin: 1.5em auto; |
| 81 |
color: #222; |
| 82 |
background-color: #fff; |
| 83 |
font-size: 14px; |
| 84 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 85 |
line-height: 1.6; |
| 86 |
scroll-behavior: smooth; |
| 87 |
} |
| 88 |
.ears { |
| 89 |
display: none; |
| 90 |
} |
| 91 |
|
| 92 |
/* headings */ |
| 93 |
#title, h1, h2, h3, h4, h5, h6 { |
| 94 |
margin: 1em 0 0.5em; |
| 95 |
font-weight: bold; |
| 96 |
line-height: 1.3; |
| 97 |
} |
| 98 |
#title { |
| 99 |
clear: both; |
| 100 |
border-bottom: 1px solid #ddd; |
| 101 |
margin: 0 0 0.5em 0; |
| 102 |
padding: 1em 0 0.5em; |
| 103 |
} |
| 104 |
.author { |
| 105 |
padding-bottom: 4px; |
| 106 |
} |
| 107 |
h1 { |
| 108 |
font-size: 26px; |
| 109 |
margin: 1em 0; |
| 110 |
} |
| 111 |
h2 { |
| 112 |
font-size: 22px; |
| 113 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 114 |
padding-top: 33px; |
| 115 |
} |
| 116 |
h3 { |
| 117 |
font-size: 18px; |
| 118 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 119 |
padding-top: 42px; |
| 120 |
} |
| 121 |
h4 { |
| 122 |
font-size: 16px; |
| 123 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 124 |
padding-top: 42px; |
| 125 |
} |
| 126 |
h5, h6 { |
| 127 |
font-size: 14px; |
| 128 |
} |
| 129 |
#n-copyright-notice { |
| 130 |
border-bottom: 1px solid #ddd; |
| 131 |
padding-bottom: 1em; |
| 132 |
margin-bottom: 1em; |
| 133 |
} |
| 134 |
/* general structure */ |
| 135 |
p { |
| 136 |
padding: 0; |
| 137 |
margin: 0 0 1em 0; |
| 138 |
text-align: left; |
| 139 |
} |
| 140 |
div, span { |
| 141 |
position: relative; |
| 142 |
} |
| 143 |
div { |
| 144 |
margin: 0; |
| 145 |
} |
| 146 |
.alignRight.art-text { |
| 147 |
background-color: #f9f9f9; |
| 148 |
border: 1px solid #eee; |
| 149 |
border-radius: 3px; |
| 150 |
padding: 1em 1em 0; |
| 151 |
margin-bottom: 1.5em; |
| 152 |
} |
| 153 |
.alignRight.art-text pre { |
| 154 |
padding: 0; |
| 155 |
} |
| 156 |
.alignRight { |
| 157 |
margin: 1em 0; |
| 158 |
} |
| 159 |
.alignRight > *:first-child { |
| 160 |
border: none; |
| 161 |
margin: 0; |
| 162 |
float: right; |
| 163 |
clear: both; |
| 164 |
} |
| 165 |
.alignRight > *:nth-child(2) { |
| 166 |
clear: both; |
| 167 |
display: block; |
| 168 |
border: none; |
| 169 |
} |
| 170 |
svg { |
| 171 |
display: block; |
| 172 |
} |
| 173 |
.alignCenter.art-text { |
| 174 |
background-color: #f9f9f9; |
| 175 |
border: 1px solid #eee; |
| 176 |
border-radius: 3px; |
| 177 |
padding: 1em 1em 0; |
| 178 |
margin-bottom: 1.5em; |
| 179 |
} |
| 180 |
.alignCenter.art-text pre { |
| 181 |
padding: 0; |
| 182 |
} |
| 183 |
.alignCenter { |
| 184 |
margin: 1em 0; |
| 185 |
} |
| 186 |
.alignCenter > *:first-child { |
| 187 |
border: none; |
| 188 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 189 |
support flexbox yet. |
| 190 |
*/ |
| 191 |
display: table; |
| 192 |
margin: 0 auto; |
| 193 |
} |
| 194 |
|
| 195 |
/* lists */ |
| 196 |
ol, ul { |
| 197 |
padding: 0; |
| 198 |
margin: 0 0 1em 2em; |
| 199 |
} |
| 200 |
ol ol, ul ul, ol ul, ul ol { |
| 201 |
margin-left: 1em; |
| 202 |
} |
| 203 |
li { |
| 204 |
margin: 0 0 0.25em 0; |
| 205 |
} |
| 206 |
.ulCompact li { |
| 207 |
margin: 0; |
| 208 |
} |
| 209 |
ul.empty, .ulEmpty { |
| 210 |
list-style-type: none; |
| 211 |
} |
| 212 |
ul.empty li, .ulEmpty li { |
| 213 |
margin-top: 0.5em; |
| 214 |
} |
| 215 |
ul.compact, .ulCompact, |
| 216 |
ol.compact, .olCompact { |
| 217 |
line-height: 100%; |
| 218 |
margin: 0 0 0 2em; |
| 219 |
} |
| 220 |
|
| 221 |
/* definition lists */ |
| 222 |
dl { |
| 223 |
} |
| 224 |
dl > dt { |
| 225 |
float: left; |
| 226 |
margin-right: 1em; |
| 227 |
} |
| 228 |
/* |
| 229 |
dl.nohang > dt { |
| 230 |
float: none; |
| 231 |
} |
| 232 |
*/ |
| 233 |
dl > dd { |
| 234 |
margin-bottom: .8em; |
| 235 |
min-height: 1.3em; |
| 236 |
} |
| 237 |
dl.compact > dd, .dlCompact > dd { |
| 238 |
margin-bottom: 0em; |
| 239 |
} |
| 240 |
dl > dd > dl { |
| 241 |
margin-top: 0.5em; |
| 242 |
margin-bottom: 0em; |
| 243 |
} |
| 244 |
|
| 245 |
/* links */ |
| 246 |
a { |
| 247 |
text-decoration: none; |
| 248 |
} |
| 249 |
a[href] { |
| 250 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 251 |
} |
| 252 |
a[href]:hover { |
| 253 |
background-color: #f2f2f2; |
| 254 |
} |
| 255 |
figcaption a[href], |
| 256 |
a[href].selfRef { |
| 257 |
color: #222; |
| 258 |
} |
| 259 |
/* XXX probably not this: |
| 260 |
a.selfRef:hover { |
| 261 |
background-color: transparent; |
| 262 |
cursor: default; |
| 263 |
} */ |
| 264 |
|
| 265 |
/* Figures */ |
| 266 |
tt, code, pre, code { |
| 267 |
background-color: #f9f9f9; |
| 268 |
font-family: 'Roboto Mono', monospace; |
| 269 |
} |
| 270 |
pre { |
| 271 |
border: 1px solid #eee; |
| 272 |
margin: 0; |
| 273 |
padding: 1em; |
| 274 |
} |
| 275 |
img { |
| 276 |
max-width: 100%; |
| 277 |
} |
| 278 |
figure { |
| 279 |
margin: 0; |
| 280 |
} |
| 281 |
figure blockquote { |
| 282 |
margin: 0.8em 0.4em 0.4em; |
| 283 |
} |
| 284 |
figcaption { |
| 285 |
font-style: italic; |
| 286 |
margin: 0 0 1em 0; |
| 287 |
} |
| 288 |
@media screen { |
| 289 |
pre { |
| 290 |
overflow-x: auto; |
| 291 |
max-width: 100%; |
| 292 |
max-width: calc(100% - 22px); |
| 293 |
} |
| 294 |
} |
| 295 |
|
| 296 |
/* aside, blockquote */ |
| 297 |
aside, blockquote { |
| 298 |
margin-left: 0; |
| 299 |
padding: 1.2em 2em; |
| 300 |
} |
| 301 |
blockquote { |
| 302 |
background-color: #f9f9f9; |
| 303 |
color: #111; /* Arlen: WCAG 2019 */ |
| 304 |
border: 1px solid #ddd; |
| 305 |
border-radius: 3px; |
| 306 |
margin: 1em 0; |
| 307 |
} |
| 308 |
cite { |
| 309 |
display: block; |
| 310 |
text-align: right; |
| 311 |
font-style: italic; |
| 312 |
} |
| 313 |
|
| 314 |
/* tables */ |
| 315 |
table { |
| 316 |
width: 100%; |
| 317 |
margin: 0 0 1em; |
| 318 |
border-collapse: collapse; |
| 319 |
border: 1px solid #eee; |
| 320 |
} |
| 321 |
th, td { |
| 322 |
text-align: left; |
| 323 |
vertical-align: top; |
| 324 |
padding: 0.5em 0.75em; |
| 325 |
} |
| 326 |
th { |
| 327 |
text-align: left; |
| 328 |
background-color: #e9e9e9; |
| 329 |
} |
| 330 |
tr:nth-child(2n+1) > td { |
| 331 |
background-color: #f5f5f5; |
| 332 |
} |
| 333 |
table caption { |
| 334 |
font-style: italic; |
| 335 |
margin: 0; |
| 336 |
padding: 0; |
| 337 |
text-align: left; |
| 338 |
} |
| 339 |
table p { |
| 340 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 341 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 342 |
margin: 0; |
| 343 |
} |
| 344 |
|
| 345 |
/* pilcrow */ |
| 346 |
a.pilcrow { |
| 347 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 348 |
text-decoration: none; |
| 349 |
visibility: hidden; |
| 350 |
user-select: none; |
| 351 |
-ms-user-select: none; |
| 352 |
-o-user-select:none; |
| 353 |
-moz-user-select: none; |
| 354 |
-khtml-user-select: none; |
| 355 |
-webkit-user-select: none; |
| 356 |
-webkit-touch-callout: none; |
| 357 |
} |
| 358 |
@media screen { |
| 359 |
aside:hover > a.pilcrow, |
| 360 |
p:hover > a.pilcrow, |
| 361 |
blockquote:hover > a.pilcrow, |
| 362 |
div:hover > a.pilcrow, |
| 363 |
li:hover > a.pilcrow, |
| 364 |
pre:hover > a.pilcrow { |
| 365 |
visibility: visible; |
| 366 |
} |
| 367 |
a.pilcrow:hover { |
| 368 |
background-color: transparent; |
| 369 |
} |
| 370 |
} |
| 371 |
|
| 372 |
/* misc */ |
| 373 |
hr { |
| 374 |
border: 0; |
| 375 |
border-top: 1px solid #eee; |
| 376 |
} |
| 377 |
.bcp14 { |
| 378 |
font-variant: small-caps; |
| 379 |
} |
| 380 |
|
| 381 |
.role { |
| 382 |
font-variant: all-small-caps; |
| 383 |
} |
| 384 |
|
| 385 |
/* info block */ |
| 386 |
#identifiers { |
| 387 |
margin: 0; |
| 388 |
font-size: 0.9em; |
| 389 |
} |
| 390 |
#identifiers dt { |
| 391 |
width: 3em; |
| 392 |
clear: left; |
| 393 |
} |
| 394 |
#identifiers dd { |
| 395 |
float: left; |
| 396 |
margin-bottom: 0; |
| 397 |
} |
| 398 |
#identifiers .authors .author { |
| 399 |
display: inline-block; |
| 400 |
margin-right: 1.5em; |
| 401 |
} |
| 402 |
#identifiers .authors .org { |
| 403 |
font-style: italic; |
| 404 |
} |
| 405 |
|
| 406 |
/* The prepared/rendered info at the very bottom of the page */ |
| 407 |
.docInfo { |
| 408 |
color: #666; /* Arlen: WCAG 2019 */ |
| 409 |
font-size: 0.9em; |
| 410 |
font-style: italic; |
| 411 |
margin-top: 2em; |
| 412 |
} |
| 413 |
.docInfo .prepared { |
| 414 |
float: left; |
| 415 |
} |
| 416 |
.docInfo .prepared { |
| 417 |
float: right; |
| 418 |
} |
| 419 |
|
| 420 |
/* table of contents */ |
| 421 |
#toc { |
| 422 |
padding: 0.75em 0 2em 0; |
| 423 |
margin-bottom: 1em; |
| 424 |
} |
| 425 |
nav.toc ul { |
| 426 |
margin: 0 0.5em 0 0; |
| 427 |
padding: 0; |
| 428 |
list-style: none; |
| 429 |
} |
| 430 |
nav.toc li { |
| 431 |
line-height: 1.3em; |
| 432 |
margin: 0.75em 0; |
| 433 |
padding-left: 1.2em; |
| 434 |
text-indent: -1.2em; |
| 435 |
} |
| 436 |
/* references */ |
| 437 |
.references dt { |
| 438 |
text-align: right; |
| 439 |
font-weight: bold; |
| 440 |
min-width: 7em; |
| 441 |
} |
| 442 |
.references dd { |
| 443 |
margin-left: 8em; |
| 444 |
overflow: auto; |
| 445 |
} |
| 446 |
|
| 447 |
.refInstance { |
| 448 |
margin-bottom: 1.25em; |
| 449 |
} |
| 450 |
|
| 451 |
.references .ascii { |
| 452 |
margin-bottom: 0.25em; |
| 453 |
} |
| 454 |
|
| 455 |
/* index */ |
| 456 |
.index ul { |
| 457 |
margin: 0 0 0 1em; |
| 458 |
padding: 0; |
| 459 |
list-style: none; |
| 460 |
} |
| 461 |
.index ul ul { |
| 462 |
margin: 0; |
| 463 |
} |
| 464 |
.index li { |
| 465 |
margin: 0; |
| 466 |
text-indent: -2em; |
| 467 |
padding-left: 2em; |
| 468 |
padding-bottom: 5px; |
| 469 |
} |
| 470 |
.indexIndex { |
| 471 |
margin: 0.5em 0 1em; |
| 472 |
} |
| 473 |
.index a { |
| 474 |
font-weight: 700; |
| 475 |
} |
| 476 |
/* make the index two-column on all but the smallest screens */ |
| 477 |
@media (min-width: 600px) { |
| 478 |
.index ul { |
| 479 |
-moz-column-count: 2; |
| 480 |
-moz-column-gap: 20px; |
| 481 |
} |
| 482 |
.index ul ul { |
| 483 |
-moz-column-count: 1; |
| 484 |
-moz-column-gap: 0; |
| 485 |
} |
| 486 |
} |
| 487 |
|
| 488 |
/* authors */ |
| 489 |
address.vcard { |
| 490 |
font-style: normal; |
| 491 |
margin: 1em 0; |
| 492 |
} |
| 493 |
|
| 494 |
address.vcard .nameRole { |
| 495 |
font-weight: 700; |
| 496 |
margin-left: 0; |
| 497 |
} |
| 498 |
address.vcard .label { |
| 499 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 500 |
margin: 0.5em 0; |
| 501 |
} |
| 502 |
address.vcard .type { |
| 503 |
display: none; |
| 504 |
} |
| 505 |
.alternative-contact { |
| 506 |
margin: 1.5em 0 1em; |
| 507 |
} |
| 508 |
hr.addr { |
| 509 |
border-top: 1px dashed; |
| 510 |
margin: 0; |
| 511 |
color: #ddd; |
| 512 |
max-width: calc(100% - 16px); |
| 513 |
} |
| 514 |
|
| 515 |
/* temporary notes */ |
| 516 |
.rfcEditorRemove::before { |
| 517 |
position: absolute; |
| 518 |
top: 0.2em; |
| 519 |
right: 0.2em; |
| 520 |
padding: 0.2em; |
| 521 |
content: "The RFC Editor will remove this note"; |
| 522 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 523 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 524 |
} |
| 525 |
.rfcEditorRemove { |
| 526 |
position: relative; |
| 527 |
padding-top: 1.8em; |
| 528 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 529 |
border-radius: 3px; |
| 530 |
} |
| 531 |
.cref { |
| 532 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 533 |
padding: 2px 4px; |
| 534 |
} |
| 535 |
.crefSource { |
| 536 |
font-style: italic; |
| 537 |
} |
| 538 |
/* alternative layout for smaller screens */ |
| 539 |
@media screen and (max-width: 1023px) { |
| 540 |
body { |
| 541 |
padding-top: 2em; |
| 542 |
} |
| 543 |
#title { |
| 544 |
padding: 1em 0; |
| 545 |
} |
| 546 |
h1 { |
| 547 |
font-size: 24px; |
| 548 |
} |
| 549 |
h2 { |
| 550 |
font-size: 20px; |
| 551 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 552 |
padding-top: 38px; |
| 553 |
} |
| 554 |
#identifiers dd { |
| 555 |
max-width: 60%; |
| 556 |
} |
| 557 |
#toc { |
| 558 |
position: fixed; |
| 559 |
z-index: 2; |
| 560 |
top: 0; |
| 561 |
right: 0; |
| 562 |
padding: 0; |
| 563 |
margin: 0; |
| 564 |
background-color: inherit; |
| 565 |
border-bottom: 1px solid #ccc; |
| 566 |
} |
| 567 |
#toc h2 { |
| 568 |
margin: -1px 0 0 0; |
| 569 |
padding: 4px 0 4px 6px; |
| 570 |
padding-right: 1em; |
| 571 |
min-width: 190px; |
| 572 |
font-size: 1.1em; |
| 573 |
text-align: right; |
| 574 |
background-color: #444; |
| 575 |
color: white; |
| 576 |
cursor: pointer; |
| 577 |
} |
| 578 |
#toc h2::before { /* css hamburger */ |
| 579 |
float: right; |
| 580 |
position: relative; |
| 581 |
width: 1em; |
| 582 |
height: 1px; |
| 583 |
left: -164px; |
| 584 |
margin: 6px 0 0 0; |
| 585 |
background: white none repeat scroll 0 0; |
| 586 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 587 |
content: ""; |
| 588 |
} |
| 589 |
#toc nav { |
| 590 |
display: none; |
| 591 |
padding: 0.5em 1em 1em; |
| 592 |
overflow: auto; |
| 593 |
height: calc(100vh - 48px); |
| 594 |
border-left: 1px solid #ddd; |
| 595 |
} |
| 596 |
} |
| 597 |
|
| 598 |
/* alternative layout for wide screens */ |
| 599 |
@media screen and (min-width: 1024px) { |
| 600 |
body { |
| 601 |
max-width: 724px; |
| 602 |
margin: 42px auto; |
| 603 |
padding-left: 1.5em; |
| 604 |
padding-right: 29em; |
| 605 |
} |
| 606 |
#toc { |
| 607 |
position: fixed; |
| 608 |
top: 42px; |
| 609 |
right: 42px; |
| 610 |
width: 25%; |
| 611 |
margin: 0; |
| 612 |
padding: 0 1em; |
| 613 |
z-index: 1; |
| 614 |
} |
| 615 |
#toc h2 { |
| 616 |
border-top: none; |
| 617 |
border-bottom: 1px solid #ddd; |
| 618 |
font-size: 1em; |
| 619 |
font-weight: normal; |
| 620 |
margin: 0; |
| 621 |
padding: 0.25em 1em 1em 0; |
| 622 |
} |
| 623 |
#toc nav { |
| 624 |
display: block; |
| 625 |
height: calc(90vh - 84px); |
| 626 |
bottom: 0; |
| 627 |
padding: 0.5em 0 0; |
| 628 |
overflow: auto; |
| 629 |
} |
| 630 |
img { /* future proofing */ |
| 631 |
max-width: 100%; |
| 632 |
height: auto; |
| 633 |
} |
| 634 |
} |
| 635 |
|
| 636 |
/* pagination */ |
| 637 |
@media print { |
| 638 |
body { |
| 639 |
|
| 640 |
width: 100%; |
| 641 |
} |
| 642 |
p { |
| 643 |
orphans: 3; |
| 644 |
widows: 3; |
| 645 |
} |
| 646 |
#n-copyright-notice { |
| 647 |
border-bottom: none; |
| 648 |
} |
| 649 |
#toc, #n-introduction { |
| 650 |
page-break-before: always; |
| 651 |
} |
| 652 |
#toc { |
| 653 |
border-top: none; |
| 654 |
padding-top: 0; |
| 655 |
} |
| 656 |
figure, pre { |
| 657 |
page-break-inside: avoid; |
| 658 |
} |
| 659 |
figure { |
| 660 |
overflow: scroll; |
| 661 |
} |
| 662 |
h1, h2, h3, h4, h5, h6 { |
| 663 |
page-break-after: avoid; |
| 664 |
} |
| 665 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 666 |
page-break-before: avoid; |
| 667 |
} |
| 668 |
pre { |
| 669 |
white-space: pre-wrap; |
| 670 |
word-wrap: break-word; |
| 671 |
font-size: 10pt; |
| 672 |
} |
| 673 |
table { |
| 674 |
border: 1px solid #ddd; |
| 675 |
} |
| 676 |
td { |
| 677 |
border-top: 1px solid #ddd; |
| 678 |
} |
| 679 |
} |
| 680 |
|
| 681 |
/* This is commented out here, as the string-set: doesn't |
| 682 |
pass W3C validation currently */ |
| 683 |
/* |
| 684 |
.ears thead .left { |
| 685 |
string-set: ears-top-left content(); |
| 686 |
} |
| 687 |
|
| 688 |
.ears thead .center { |
| 689 |
string-set: ears-top-center content(); |
| 690 |
} |
| 691 |
|
| 692 |
.ears thead .right { |
| 693 |
string-set: ears-top-right content(); |
| 694 |
} |
| 695 |
|
| 696 |
.ears tfoot .left { |
| 697 |
string-set: ears-bottom-left content(); |
| 698 |
} |
| 699 |
|
| 700 |
.ears tfoot .center { |
| 701 |
string-set: ears-bottom-center content(); |
| 702 |
} |
| 703 |
|
| 704 |
.ears tfoot .right { |
| 705 |
string-set: ears-bottom-right content(); |
| 706 |
} |
| 707 |
*/ |
| 708 |
|
| 709 |
@page :first { |
| 710 |
padding-top: 0; |
| 711 |
@top-left { |
| 712 |
content: normal; |
| 713 |
border: none; |
| 714 |
} |
| 715 |
@top-center { |
| 716 |
content: normal; |
| 717 |
border: none; |
| 718 |
} |
| 719 |
@top-right { |
| 720 |
content: normal; |
| 721 |
border: none; |
| 722 |
} |
| 723 |
} |
| 724 |
|
| 725 |
@page { |
| 726 |
size: A4; |
| 727 |
margin-bottom: 45mm; |
| 728 |
padding-top: 20px; |
| 729 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 730 |
the content depends on the document */ |
| 731 |
/* |
| 732 |
@top-left { |
| 733 |
content: 'Internet-Draft'; |
| 734 |
vertical-align: bottom; |
| 735 |
border-bottom: solid 1px #ccc; |
| 736 |
} |
| 737 |
@top-left { |
| 738 |
content: string(ears-top-left); |
| 739 |
vertical-align: bottom; |
| 740 |
border-bottom: solid 1px #ccc; |
| 741 |
} |
| 742 |
@top-center { |
| 743 |
content: string(ears-top-center); |
| 744 |
vertical-align: bottom; |
| 745 |
border-bottom: solid 1px #ccc; |
| 746 |
} |
| 747 |
@top-right { |
| 748 |
content: string(ears-top-right); |
| 749 |
vertical-align: bottom; |
| 750 |
border-bottom: solid 1px #ccc; |
| 751 |
} |
| 752 |
@bottom-left { |
| 753 |
content: string(ears-bottom-left); |
| 754 |
vertical-align: top; |
| 755 |
border-top: solid 1px #ccc; |
| 756 |
} |
| 757 |
@bottom-center { |
| 758 |
content: string(ears-bottom-center); |
| 759 |
vertical-align: top; |
| 760 |
border-top: solid 1px #ccc; |
| 761 |
} |
| 762 |
@bottom-right { |
| 763 |
content: '[Page ' counter(page) ']'; |
| 764 |
vertical-align: top; |
| 765 |
border-top: solid 1px #ccc; |
| 766 |
} |
| 767 |
*/ |
| 768 |
|
| 769 |
} |
| 770 |
|
| 771 |
/* Changes introduced to fix issues found during implementation */ |
| 772 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 773 |
a { |
| 774 |
z-index: 2; |
| 775 |
} |
| 776 |
/* Separate body from document info even without intervening H1 */ |
| 777 |
section { |
| 778 |
clear: both; |
| 779 |
} |
| 780 |
|
| 781 |
|
| 782 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 783 |
.author { |
| 784 |
vertical-align: top; |
| 785 |
} |
| 786 |
|
| 787 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 788 |
#identifiers dt { |
| 789 |
width: 8em; |
| 790 |
} |
| 791 |
|
| 792 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 793 |
#identifiers dd { |
| 794 |
margin-left: 1em; |
| 795 |
} |
| 796 |
|
| 797 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 798 |
#toc { |
| 799 |
background-color: white; |
| 800 |
} |
| 801 |
|
| 802 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 803 |
@media screen and (max-width: 1023px) { |
| 804 |
#toc h2 a, |
| 805 |
#toc h2 a:link, |
| 806 |
#toc h2 a:focus, |
| 807 |
#toc h2 a:hover, |
| 808 |
#toc a.toplink, |
| 809 |
#toc a.toplink:hover { |
| 810 |
color: white; |
| 811 |
background-color: #444; |
| 812 |
text-decoration: none; |
| 813 |
} |
| 814 |
} |
| 815 |
|
| 816 |
/* Give the bottom of the ToC some whitespace */ |
| 817 |
@media screen and (min-width: 1024px) { |
| 818 |
#toc { |
| 819 |
padding: 0 0 1em 1em; |
| 820 |
} |
| 821 |
} |
| 822 |
|
| 823 |
/* Style section numbers with more space between number and title */ |
| 824 |
.section-number { |
| 825 |
padding-right: 0.5em; |
| 826 |
} |
| 827 |
|
| 828 |
/* prevent monospace from becoming overly large */ |
| 829 |
tt, code, pre, code { |
| 830 |
font-size: 95%; |
| 831 |
} |
| 832 |
|
| 833 |
/* Fix the height/width aspect for ascii art*/ |
| 834 |
pre.sourcecode, |
| 835 |
.art-text pre { |
| 836 |
line-height: 1.12; |
| 837 |
} |
| 838 |
|
| 839 |
|
| 840 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 841 |
a.toplink { |
| 842 |
float: right; |
| 843 |
margin-right: 0.5em; |
| 844 |
} |
| 845 |
|
| 846 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 847 |
dl > dt, |
| 848 |
dl.dlParallel > dt { |
| 849 |
float: left; |
| 850 |
margin-right: 1em; |
| 851 |
} |
| 852 |
dl.dlNewline > dt { |
| 853 |
float: none; |
| 854 |
} |
| 855 |
|
| 856 |
/* Provide styling for table cell text alignment */ |
| 857 |
table td.text-left, |
| 858 |
table th.text-left { |
| 859 |
text-align: left; |
| 860 |
} |
| 861 |
table td.text-center, |
| 862 |
table th.text-center { |
| 863 |
text-align: center; |
| 864 |
} |
| 865 |
table td.text-right, |
| 866 |
table th.text-right { |
| 867 |
text-align: right; |
| 868 |
} |
| 869 |
|
| 870 |
/* Make the alternative author contact informatio look less like just another |
| 871 |
author, and group it closer with the primary author contact information */ |
| 872 |
.alternative-contact { |
| 873 |
margin: 0.5em 0 0.25em 0; |
| 874 |
} |
| 875 |
address .non-ascii { |
| 876 |
margin: 0 0 0 2em; |
| 877 |
} |
| 878 |
|
| 879 |
/* With it being possible to set tables with alignment |
| 880 |
left, center, and right, { width: 100%; } does not make sense */ |
| 881 |
table { |
| 882 |
width: auto; |
| 883 |
} |
| 884 |
|
| 885 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 886 |
because of a long floating dt label.*/ |
| 887 |
.references dd { |
| 888 |
overflow: visible; |
| 889 |
} |
| 890 |
|
| 891 |
/* Control caption placement */ |
| 892 |
caption { |
| 893 |
caption-side: bottom; |
| 894 |
} |
| 895 |
|
| 896 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 897 |
script don't end up on the other side of the page. */ |
| 898 |
|
| 899 |
address.vcard { |
| 900 |
max-width: 30em; |
| 901 |
margin-right: auto; |
| 902 |
} |
| 903 |
|
| 904 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 905 |
address div.left { |
| 906 |
text-align: left; |
| 907 |
} |
| 908 |
address div.right { |
| 909 |
text-align: right; |
| 910 |
} |
| 911 |
|
| 912 |
/* Provide table alignment support. We can't use the alignX classes above |
| 913 |
since they do unwanted things with caption and other styling. */ |
| 914 |
table.right { |
| 915 |
margin-left: auto; |
| 916 |
margin-right: 0; |
| 917 |
} |
| 918 |
table.center { |
| 919 |
margin-left: auto; |
| 920 |
margin-right: auto; |
| 921 |
} |
| 922 |
table.left { |
| 923 |
margin-left: 0; |
| 924 |
margin-right: auto; |
| 925 |
} |
| 926 |
|
| 927 |
/* Give the table caption label the same styling as the figcaption */ |
| 928 |
caption a[href] { |
| 929 |
color: #222; |
| 930 |
} |
| 931 |
|
| 932 |
@media print { |
| 933 |
.toplink { |
| 934 |
display: none; |
| 935 |
} |
| 936 |
|
| 937 |
/* avoid overwriting the top border line with the ToC header */ |
| 938 |
#toc { |
| 939 |
padding-top: 1px; |
| 940 |
} |
| 941 |
|
| 942 |
/* Avoid page breaks inside dl and author address entries */ |
| 943 |
.vcard { |
| 944 |
page-break-inside: avoid; |
| 945 |
} |
| 946 |
|
| 947 |
} |
| 948 |
/* Tweak the bcp14 keyword presentation */ |
| 949 |
.bcp14 { |
| 950 |
font-variant: small-caps; |
| 951 |
font-weight: bold; |
| 952 |
font-size: 0.9em; |
| 953 |
} |
| 954 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 955 |
h2 { |
| 956 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 957 |
padding-top: 31px; |
| 958 |
} |
| 959 |
h3 { |
| 960 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 961 |
padding-top: 24px; |
| 962 |
} |
| 963 |
h4 { |
| 964 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 965 |
padding-top: 24px; |
| 966 |
} |
| 967 |
/* Float artwork pilcrow to the right */ |
| 968 |
@media screen { |
| 969 |
.artwork a.pilcrow { |
| 970 |
display: block; |
| 971 |
line-height: 0.7; |
| 972 |
margin-top: 0.15em; |
| 973 |
} |
| 974 |
} |
| 975 |
/* Make pilcrows on dd visible */ |
| 976 |
@media screen { |
| 977 |
dd:hover > a.pilcrow { |
| 978 |
visibility: visible; |
| 979 |
} |
| 980 |
} |
| 981 |
/* Make the placement of figcaption match that of a table's caption |
| 982 |
by removing the figure's added bottom margin */ |
| 983 |
.alignLeft.art-text, |
| 984 |
.alignCenter.art-text, |
| 985 |
.alignRight.art-text { |
| 986 |
margin-bottom: 0; |
| 987 |
} |
| 988 |
.alignLeft, |
| 989 |
.alignCenter, |
| 990 |
.alignRight { |
| 991 |
margin: 1em 0 0 0; |
| 992 |
} |
| 993 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 994 |
possibly even requiring a new line */ |
| 995 |
@media print { |
| 996 |
a.pilcrow { |
| 997 |
display: none; |
| 998 |
} |
| 999 |
} |
| 1000 |
/* Styling for the external metadata */ |
| 1001 |
div#external-metadata { |
| 1002 |
background-color: #eee; |
| 1003 |
padding: 0.5em; |
| 1004 |
margin-bottom: 0.5em; |
| 1005 |
display: none; |
| 1006 |
} |
| 1007 |
div#internal-metadata { |
| 1008 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1009 |
} |
| 1010 |
/* Styling for title RFC Number */ |
| 1011 |
h1#rfcnum { |
| 1012 |
clear: both; |
| 1013 |
margin: 0 0 -1em; |
| 1014 |
padding: 1em 0 0 0; |
| 1015 |
} |
| 1016 |
/* Make .olPercent look the same as <ol><li> */ |
| 1017 |
dl.olPercent > dd { |
| 1018 |
margin-bottom: 0.25em; |
| 1019 |
min-height: initial; |
| 1020 |
} |
| 1021 |
/* Give aside some styling to set it apart */ |
| 1022 |
aside { |
| 1023 |
border-left: 1px solid #ddd; |
| 1024 |
margin: 1em 0 1em 2em; |
| 1025 |
padding: 0.2em 2em; |
| 1026 |
} |
| 1027 |
aside > dl, |
| 1028 |
aside > ol, |
| 1029 |
aside > ul, |
| 1030 |
aside > table, |
| 1031 |
aside > p { |
| 1032 |
margin-bottom: 0.5em; |
| 1033 |
} |
| 1034 |
/* Additional page break settings */ |
| 1035 |
@media print { |
| 1036 |
figcaption, table caption { |
| 1037 |
page-break-before: avoid; |
| 1038 |
} |
| 1039 |
} |
| 1040 |
/* Font size adjustments for print */ |
| 1041 |
@media print { |
| 1042 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1043 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1044 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1045 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1046 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1047 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1048 |
} |
| 1049 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1050 |
@media print { |
| 1051 |
.artwork, |
| 1052 |
.sourcecode { |
| 1053 |
margin-bottom: 1em; |
| 1054 |
} |
| 1055 |
} |
| 1056 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1057 |
table { |
| 1058 |
min-width: 20em; |
| 1059 |
} |
| 1060 |
/* ol type a */ |
| 1061 |
ol.type-a { list-style-type: lower-alpha; } |
| 1062 |
ol.type-A { list-style-type: upper-alpha; } |
| 1063 |
ol.type-i { list-style-type: lower-roman; } |
| 1064 |
ol.type-I { list-style-type: lower-roman; } |
| 1065 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1066 |
and increase the contrast between border and odd row background sligthtly */ |
| 1067 |
table { |
| 1068 |
border: 1px solid #ddd; |
| 1069 |
} |
| 1070 |
td { |
| 1071 |
border-top: 1px solid #ddd; |
| 1072 |
} |
| 1073 |
tr:nth-child(2n+1) > td { |
| 1074 |
background-color: #f8f8f8; |
| 1075 |
} |
| 1076 |
/* Use style rules to govern display of the TOC. */ |
| 1077 |
@media screen and (max-width: 1023px) { |
| 1078 |
#toc nav { display: none; } |
| 1079 |
#toc.active nav { display: block; } |
| 1080 |
} |
| 1081 |
/* Add support for keepWithNext */ |
| 1082 |
.keepWithNext { |
| 1083 |
break-after: avoid-page; |
| 1084 |
break-after: avoid-page; |
| 1085 |
} |
| 1086 |
/* Add support for keepWithPrevious */ |
| 1087 |
.keepWithPrevious { |
| 1088 |
break-before: avoid-page; |
| 1089 |
} |
| 1090 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1091 |
figure, pre, table, .artwork, .sourcecode { |
| 1092 |
break-before: avoid-page; |
| 1093 |
break-after: auto; |
| 1094 |
} |
| 1095 |
/* Avoid breaks between <dt> and <dd> */ |
| 1096 |
dl { |
| 1097 |
break-before: auto; |
| 1098 |
break-inside: auto; |
| 1099 |
} |
| 1100 |
dt { |
| 1101 |
break-before: auto; |
| 1102 |
break-after: avoid-page; |
| 1103 |
} |
| 1104 |
dd { |
| 1105 |
break-before: avoid-page; |
| 1106 |
break-after: auto; |
| 1107 |
orphans: 3; |
| 1108 |
widows: 3 |
| 1109 |
} |
| 1110 |
span.break, dd.break { |
| 1111 |
margin-bottom: 0; |
| 1112 |
min-height: 0; |
| 1113 |
break-before: auto; |
| 1114 |
break-inside: auto; |
| 1115 |
break-after: auto; |
| 1116 |
} |
| 1117 |
/* Undo break-before ToC */ |
| 1118 |
@media print { |
| 1119 |
#toc { |
| 1120 |
break-before: auto; |
| 1121 |
} |
| 1122 |
} |
| 1123 |
/* Text in compact lists should not get extra bottim margin space, |
| 1124 |
since that would makes the list not compact */ |
| 1125 |
ul.compact p, .ulCompact p, |
| 1126 |
ol.compact p, .olCompact p { |
| 1127 |
margin: 0; |
| 1128 |
} |
| 1129 |
/* But the list as a whole needs the extra space at the end */ |
| 1130 |
section ul.compact, |
| 1131 |
section .ulCompact, |
| 1132 |
section ol.compact, |
| 1133 |
section .olCompact { |
| 1134 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1135 |
} |
| 1136 |
/* The tt and code background above interferes with for instance table cell |
| 1137 |
backgrounds. Changed to something a bit more selective. */ |
| 1138 |
tt, code { |
| 1139 |
background-color: transparent; |
| 1140 |
} |
| 1141 |
p tt, p code, li tt, li code { |
| 1142 |
background-color: #f8f8f8; |
| 1143 |
} |
| 1144 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1145 |
pre { |
| 1146 |
margin-top: 0.5px; |
| 1147 |
} |
| 1148 |
/* Tweak the comact list text */ |
| 1149 |
ul.compact, .ulCompact, |
| 1150 |
ol.compact, .olCompact, |
| 1151 |
dl.compact, .dlCompact { |
| 1152 |
line-height: normal; |
| 1153 |
} |
| 1154 |
/* Don't add top margin for nested lists */ |
| 1155 |
li > ul, li > ol, li > dl, |
| 1156 |
dd > ul, dd > ol, dd > dl, |
| 1157 |
dl > dd > dl { |
| 1158 |
margin-top: initial; |
| 1159 |
} |
| 1160 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1161 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1162 |
dd > div.artwork:first-child, |
| 1163 |
dd > aside:first-child, |
| 1164 |
dd > figure:first-child, |
| 1165 |
dd > ol:first-child, |
| 1166 |
dd > div:first-child > pre.sourcecode, |
| 1167 |
dd > table:first-child, |
| 1168 |
dd > ul:first-child { |
| 1169 |
clear: left; |
| 1170 |
} |
| 1171 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1172 |
dt+dd:empty::before{ |
| 1173 |
content: "\00a0"; |
| 1174 |
} |
| 1175 |
</style> |
| 1176 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1177 |
<link href="https://dx.doi.org/10.17487/rfc8839" rel="alternate"> |
| 1178 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1179 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp-39" rel="prev"> |
| 1180 |
</head> |
| 1181 |
<body> |
| 1182 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1183 |
<table class="ears"> |
| 1184 |
<thead><tr> |
| 1185 |
<td class="left">RFC 8839</td> |
| 1186 |
<td class="center">ICE SDP Usage</td> |
| 1187 |
<td class="right">January 2021</td> |
| 1188 |
</tr></thead> |
| 1189 |
<tfoot><tr> |
| 1190 |
<td class="left">Petit-Huguenin, et al.</td> |
| 1191 |
<td class="center">Standards Track</td> |
| 1192 |
<td class="right">[Page]</td> |
| 1193 |
</tr></tfoot> |
| 1194 |
</table> |
| 1195 |
<div id="external-metadata" class="document-information"></div> |
| 1196 |
<div id="internal-metadata" class="document-information"> |
| 1197 |
<dl id="identifiers"> |
| 1198 |
<dt class="label-stream">Stream:</dt> |
| 1199 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1200 |
<dt class="label-rfc">RFC:</dt> |
| 1201 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8839" class="eref">8839</a></dd> |
| 1202 |
<dt class="label-obsoletes">Obsoletes:</dt> |
| 1203 |
<dd class="obsoletes"> |
| 1204 |
<a href="https://www.rfc-editor.org/rfc/rfc5245" class="eref">5245</a>, <a href="https://www.rfc-editor.org/rfc/rfc6336" class="eref">6336</a> </dd> |
| 1205 |
<dt class="label-category">Category:</dt> |
| 1206 |
<dd class="category">Standards Track</dd> |
| 1207 |
<dt class="label-published">Published:</dt> |
| 1208 |
<dd class="published"> |
| 1209 |
<time datetime="2021-01" class="published">January 2021</time> |
| 1210 |
</dd> |
| 1211 |
<dt class="label-issn">ISSN:</dt> |
| 1212 |
<dd class="issn">2070-1721</dd> |
| 1213 |
<dt class="label-authors">Authors:</dt> |
| 1214 |
<dd class="authors"> |
| 1215 |
<div class="author"> |
| 1216 |
<div class="author-name">M. Petit-Huguenin</div> |
| 1217 |
<div class="org">Impedance Mismatch</div> |
| 1218 |
</div> |
| 1219 |
<div class="author"> |
| 1220 |
<div class="author-name">S. Nandakumar</div> |
| 1221 |
<div class="org">Cisco Systems</div> |
| 1222 |
</div> |
| 1223 |
<div class="author"> |
| 1224 |
<div class="author-name">C. Holmberg</div> |
| 1225 |
<div class="org">Ericsson</div> |
| 1226 |
</div> |
| 1227 |
<div class="author"> |
| 1228 |
<div class="author-name">A. Keränen</div> |
| 1229 |
<div class="org">Ericsson</div> |
| 1230 |
</div> |
| 1231 |
<div class="author"> |
| 1232 |
<div class="author-name">R. Shpount</div> |
| 1233 |
<div class="org">TurboBridge</div> |
| 1234 |
</div> |
| 1235 |
</dd> |
| 1236 |
</dl> |
| 1237 |
</div> |
| 1238 |
<h1 id="rfcnum">RFC 8839</h1> |
| 1239 |
<h1 id="title">Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)</h1> |
| 1240 |
<section id="section-abstract"> |
| 1241 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1242 |
<p id="section-abstract-1"> |
| 1243 |
This document describes Session Description Protocol (SDP) Offer/Answer |
| 1244 |
procedures for carrying out Interactive Connectivity Establishment (ICE) |
| 1245 |
between the agents.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1246 |
<p id="section-abstract-2"> |
| 1247 |
This document obsoletes RFCs 5245 and 6336.<a href="#section-abstract-2" class="pilcrow">¶</a></p> |
| 1248 |
</section> |
| 1249 |
<div id="status-of-memo"> |
| 1250 |
<section id="section-boilerplate.1"> |
| 1251 |
<h2 id="name-status-of-this-memo"> |
| 1252 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1253 |
</h2> |
| 1254 |
<p id="section-boilerplate.1-1"> |
| 1255 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1256 |
<p id="section-boilerplate.1-2"> |
| 1257 |
This document is a product of the Internet Engineering Task Force |
| 1258 |
(IETF). It represents the consensus of the IETF community. It has |
| 1259 |
received public review and has been approved for publication by |
| 1260 |
the Internet Engineering Steering Group (IESG). Further |
| 1261 |
information on Internet Standards is available in Section 2 of |
| 1262 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1263 |
<p id="section-boilerplate.1-3"> |
| 1264 |
Information about the current status of this document, any |
| 1265 |
errata, and how to provide feedback on it may be obtained at |
| 1266 |
<span><a href="https://www.rfc-editor.org/info/rfc8839">https://www.rfc-editor.org/info/rfc8839</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1267 |
</section> |
| 1268 |
</div> |
| 1269 |
<div id="copyright"> |
| 1270 |
<section id="section-boilerplate.2"> |
| 1271 |
<h2 id="name-copyright-notice"> |
| 1272 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1273 |
</h2> |
| 1274 |
<p id="section-boilerplate.2-1"> |
| 1275 |
Copyright (c) 2021 IETF Trust and the persons identified as the |
| 1276 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1277 |
<p id="section-boilerplate.2-2"> |
| 1278 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1279 |
Provisions Relating to IETF Documents |
| 1280 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1281 |
publication of this document. Please review these documents |
| 1282 |
carefully, as they describe your rights and restrictions with |
| 1283 |
respect to this document. Code Components extracted from this |
| 1284 |
document must include Simplified BSD License text as described in |
| 1285 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1286 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1287 |
<p id="section-boilerplate.2-3"> |
| 1288 |
This document may contain material from IETF Documents or IETF |
| 1289 |
Contributions published or made publicly available before November |
| 1290 |
10, 2008. The person(s) controlling the copyright in some of this |
| 1291 |
material may not have granted the IETF Trust the right to allow |
| 1292 |
modifications of such material outside the IETF Standards Process. |
| 1293 |
Without obtaining an adequate license from the person(s) |
| 1294 |
controlling the copyright in such materials, this document may not |
| 1295 |
be modified outside the IETF Standards Process, and derivative |
| 1296 |
works of it may not be created outside the IETF Standards Process, |
| 1297 |
except to format it for publication as an RFC or to translate it |
| 1298 |
into languages other than English.<a href="#section-boilerplate.2-3" class="pilcrow">¶</a></p> |
| 1299 |
</section> |
| 1300 |
</div> |
| 1301 |
<div id="toc"> |
| 1302 |
<section id="section-toc.1"> |
| 1303 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1304 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1305 |
</h2> |
| 1306 |
<nav class="toc"><ul class="compact ulEmpty toc"> |
| 1307 |
<li class="compact ulEmpty toc" id="section-toc.1-1.1"> |
| 1308 |
<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> |
| 1309 |
</li> |
| 1310 |
<li class="compact ulEmpty toc" id="section-toc.1-1.2"> |
| 1311 |
<p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>. <a href="#name-conventions" class="xref">Conventions</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1312 |
</li> |
| 1313 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3"> |
| 1314 |
<p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>. <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1315 |
</li> |
| 1316 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4"> |
| 1317 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-sdp-offer-answer-procedures" class="xref">SDP Offer/Answer Procedures</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1318 |
<ul class="toc ulEmpty compact"> |
| 1319 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.1"> |
| 1320 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-introduction-2" class="xref">Introduction</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1321 |
</li> |
| 1322 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.2"> |
| 1323 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-generic-procedures" class="xref">Generic Procedures</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1324 |
<ul class="compact ulEmpty toc"> |
| 1325 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.1"> |
| 1326 |
<p id="section-toc.1-1.4.2.2.2.1.1"><a href="#section-4.2.1" class="xref">4.2.1</a>. <a href="#name-encoding" class="xref">Encoding</a><a href="#section-toc.1-1.4.2.2.2.1.1" class="pilcrow">¶</a></p> |
| 1327 |
</li> |
| 1328 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.2"> |
| 1329 |
<p id="section-toc.1-1.4.2.2.2.2.1"><a href="#section-4.2.2" class="xref">4.2.2</a>. <a href="#name-rtp-rtcp-considerations" class="xref">RTP/RTCP Considerations</a><a href="#section-toc.1-1.4.2.2.2.2.1" class="pilcrow">¶</a></p> |
| 1330 |
</li> |
| 1331 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.3"> |
| 1332 |
<p id="section-toc.1-1.4.2.2.2.3.1"><a href="#section-4.2.3" class="xref">4.2.3</a>. <a href="#name-determining-role" class="xref">Determining Role</a><a href="#section-toc.1-1.4.2.2.2.3.1" class="pilcrow">¶</a></p> |
| 1333 |
</li> |
| 1334 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.4"> |
| 1335 |
<p id="section-toc.1-1.4.2.2.2.4.1"><a href="#section-4.2.4" class="xref">4.2.4</a>. <a href="#name-stun-considerations" class="xref">STUN Considerations</a><a href="#section-toc.1-1.4.2.2.2.4.1" class="pilcrow">¶</a></p> |
| 1336 |
</li> |
| 1337 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.5"> |
| 1338 |
<p id="section-toc.1-1.4.2.2.2.5.1"><a href="#section-4.2.5" class="xref">4.2.5</a>. <a href="#name-verifying-ice-support-proce" class="xref">Verifying ICE Support Procedures</a><a href="#section-toc.1-1.4.2.2.2.5.1" class="pilcrow">¶</a></p> |
| 1339 |
</li> |
| 1340 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.2.2.6"> |
| 1341 |
<p id="section-toc.1-1.4.2.2.2.6.1"><a href="#section-4.2.6" class="xref">4.2.6</a>. <a href="#name-sdp-example" class="xref">SDP Example</a><a href="#section-toc.1-1.4.2.2.2.6.1" class="pilcrow">¶</a></p> |
| 1342 |
</li> |
| 1343 |
</ul> |
| 1344 |
</li> |
| 1345 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.3"> |
| 1346 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-initial-offer-answer-exchan" class="xref">Initial Offer/Answer Exchange</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p> |
| 1347 |
<ul class="compact ulEmpty toc"> |
| 1348 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.3.2.1"> |
| 1349 |
<p id="section-toc.1-1.4.2.3.2.1.1"><a href="#section-4.3.1" class="xref">4.3.1</a>. <a href="#name-sending-the-initial-offer" class="xref">Sending the Initial Offer</a><a href="#section-toc.1-1.4.2.3.2.1.1" class="pilcrow">¶</a></p> |
| 1350 |
</li> |
| 1351 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.3.2.2"> |
| 1352 |
<p id="section-toc.1-1.4.2.3.2.2.1"><a href="#section-4.3.2" class="xref">4.3.2</a>. <a href="#name-sending-the-initial-answer" class="xref">Sending the Initial Answer</a><a href="#section-toc.1-1.4.2.3.2.2.1" class="pilcrow">¶</a></p> |
| 1353 |
</li> |
| 1354 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.3.2.3"> |
| 1355 |
<p id="section-toc.1-1.4.2.3.2.3.1"><a href="#section-4.3.3" class="xref">4.3.3</a>. <a href="#name-receiving-the-initial-answe" class="xref">Receiving the Initial Answer</a><a href="#section-toc.1-1.4.2.3.2.3.1" class="pilcrow">¶</a></p> |
| 1356 |
</li> |
| 1357 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.3.2.4"> |
| 1358 |
<p id="section-toc.1-1.4.2.3.2.4.1"><a href="#section-4.3.4" class="xref">4.3.4</a>. <a href="#name-concluding-ice" class="xref">Concluding ICE</a><a href="#section-toc.1-1.4.2.3.2.4.1" class="pilcrow">¶</a></p> |
| 1359 |
</li> |
| 1360 |
</ul> |
| 1361 |
</li> |
| 1362 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.4"> |
| 1363 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>. <a href="#name-subsequent-offer-answer-exc" class="xref">Subsequent Offer/Answer Exchanges</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p> |
| 1364 |
<ul class="compact ulEmpty toc"> |
| 1365 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.4.2.1"> |
| 1366 |
<p id="section-toc.1-1.4.2.4.2.1.1"><a href="#section-4.4.1" class="xref">4.4.1</a>. <a href="#name-sending-subsequent-offer" class="xref">Sending Subsequent Offer</a><a href="#section-toc.1-1.4.2.4.2.1.1" class="pilcrow">¶</a></p> |
| 1367 |
</li> |
| 1368 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.4.2.2"> |
| 1369 |
<p id="section-toc.1-1.4.2.4.2.2.1"><a href="#section-4.4.2" class="xref">4.4.2</a>. <a href="#name-sending-subsequent-answer" class="xref">Sending Subsequent Answer</a><a href="#section-toc.1-1.4.2.4.2.2.1" class="pilcrow">¶</a></p> |
| 1370 |
</li> |
| 1371 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4.2.4.2.3"> |
| 1372 |
<p id="section-toc.1-1.4.2.4.2.3.1"><a href="#section-4.4.3" class="xref">4.4.3</a>. <a href="#name-receiving-answer-for-a-subs" class="xref">Receiving Answer for a Subsequent Offer</a><a href="#section-toc.1-1.4.2.4.2.3.1" class="pilcrow">¶</a></p> |
| 1373 |
</li> |
| 1374 |
</ul> |
| 1375 |
</li> |
| 1376 |
</ul> |
| 1377 |
</li> |
| 1378 |
<li class="compact ulEmpty toc" id="section-toc.1-1.5"> |
| 1379 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-grammar" class="xref">Grammar</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1380 |
<ul class="toc ulEmpty compact"> |
| 1381 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.1"> |
| 1382 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>. <a href="#name-candidate-attribute" class="xref">"candidate" Attribute</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p> |
| 1383 |
</li> |
| 1384 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.2"> |
| 1385 |
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>. <a href="#name-remote-candidates-attribute" class="xref">"remote-candidates" Attribute</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p> |
| 1386 |
</li> |
| 1387 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.3"> |
| 1388 |
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>. <a href="#name-ice-lite-and-ice-mismatch-a" class="xref">"ice-lite" and "ice-mismatch" Attributes</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p> |
| 1389 |
</li> |
| 1390 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.4"> |
| 1391 |
<p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>. <a href="#name-ice-ufrag-and-ice-pwd-attri" class="xref">"ice-ufrag" and "ice-pwd" Attributes</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p> |
| 1392 |
</li> |
| 1393 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.5"> |
| 1394 |
<p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>. <a href="#name-ice-pacing-attribute" class="xref">"ice-pacing" Attribute</a><a href="#section-toc.1-1.5.2.5.1" class="pilcrow">¶</a></p> |
| 1395 |
</li> |
| 1396 |
<li class="toc ulEmpty compact" id="section-toc.1-1.5.2.6"> |
| 1397 |
<p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>. <a href="#name-ice-options-attribute" class="xref">"ice-options" Attribute</a><a href="#section-toc.1-1.5.2.6.1" class="pilcrow">¶</a></p> |
| 1398 |
</li> |
| 1399 |
</ul> |
| 1400 |
</li> |
| 1401 |
<li class="compact ulEmpty toc" id="section-toc.1-1.6"> |
| 1402 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-keepalives" class="xref">Keepalives</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1403 |
</li> |
| 1404 |
<li class="compact ulEmpty toc" id="section-toc.1-1.7"> |
| 1405 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-sip-considerations" class="xref">SIP Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1406 |
<ul class="toc ulEmpty compact"> |
| 1407 |
<li class="toc ulEmpty compact" id="section-toc.1-1.7.2.1"> |
| 1408 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-latency-guidelines" class="xref">Latency Guidelines</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p> |
| 1409 |
<ul class="compact ulEmpty toc"> |
| 1410 |
<li class="compact ulEmpty toc" id="section-toc.1-1.7.2.1.2.1"> |
| 1411 |
<p id="section-toc.1-1.7.2.1.2.1.1"><a href="#section-7.1.1" class="xref">7.1.1</a>. <a href="#name-offer-in-invite" class="xref">Offer in INVITE</a><a href="#section-toc.1-1.7.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1412 |
</li> |
| 1413 |
<li class="compact ulEmpty toc" id="section-toc.1-1.7.2.1.2.2"> |
| 1414 |
<p id="section-toc.1-1.7.2.1.2.2.1"><a href="#section-7.1.2" class="xref">7.1.2</a>. <a href="#name-offer-in-response" class="xref">Offer in Response</a><a href="#section-toc.1-1.7.2.1.2.2.1" class="pilcrow">¶</a></p> |
| 1415 |
</li> |
| 1416 |
</ul> |
| 1417 |
</li> |
| 1418 |
<li class="toc ulEmpty compact" id="section-toc.1-1.7.2.2"> |
| 1419 |
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-sip-option-tags-and-media-f" class="xref">SIP Option Tags and Media Feature Tags</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p> |
| 1420 |
</li> |
| 1421 |
<li class="toc ulEmpty compact" id="section-toc.1-1.7.2.3"> |
| 1422 |
<p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>. <a href="#name-interactions-with-forking" class="xref">Interactions with Forking</a><a href="#section-toc.1-1.7.2.3.1" class="pilcrow">¶</a></p> |
| 1423 |
</li> |
| 1424 |
<li class="toc ulEmpty compact" id="section-toc.1-1.7.2.4"> |
| 1425 |
<p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>. <a href="#name-interactions-with-precondit" class="xref">Interactions with Preconditions</a><a href="#section-toc.1-1.7.2.4.1" class="pilcrow">¶</a></p> |
| 1426 |
</li> |
| 1427 |
<li class="toc ulEmpty compact" id="section-toc.1-1.7.2.5"> |
| 1428 |
<p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>. <a href="#name-interactions-with-third-par" class="xref">Interactions with Third Party Call Control</a><a href="#section-toc.1-1.7.2.5.1" class="pilcrow">¶</a></p> |
| 1429 |
</li> |
| 1430 |
</ul> |
| 1431 |
</li> |
| 1432 |
<li class="compact ulEmpty toc" id="section-toc.1-1.8"> |
| 1433 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-interactions-with-applicati" class="xref">Interactions with Application Layer Gateways and SIP</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1434 |
</li> |
| 1435 |
<li class="compact ulEmpty toc" id="section-toc.1-1.9"> |
| 1436 |
<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> |
| 1437 |
<ul class="toc ulEmpty compact"> |
| 1438 |
<li class="toc ulEmpty compact" id="section-toc.1-1.9.2.1"> |
| 1439 |
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>. <a href="#name-ip-address-privacy" class="xref">IP Address Privacy</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p> |
| 1440 |
</li> |
| 1441 |
<li class="toc ulEmpty compact" id="section-toc.1-1.9.2.2"> |
| 1442 |
<p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>. <a href="#name-attacks-on-the-offer-answer" class="xref">Attacks on the Offer/Answer Exchanges</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p> |
| 1443 |
</li> |
| 1444 |
<li class="toc ulEmpty compact" id="section-toc.1-1.9.2.3"> |
| 1445 |
<p id="section-toc.1-1.9.2.3.1"><a href="#section-9.3" class="xref">9.3</a>. <a href="#name-the-voice-hammer-attack" class="xref">The Voice Hammer Attack</a><a href="#section-toc.1-1.9.2.3.1" class="pilcrow">¶</a></p> |
| 1446 |
</li> |
| 1447 |
</ul> |
| 1448 |
</li> |
| 1449 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10"> |
| 1450 |
<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> |
| 1451 |
<ul class="toc ulEmpty compact"> |
| 1452 |
<li class="toc ulEmpty compact" id="section-toc.1-1.10.2.1"> |
| 1453 |
<p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>. <a href="#name-sdp-attributes" class="xref">SDP Attributes</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p> |
| 1454 |
<ul class="compact ulEmpty toc"> |
| 1455 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.1"> |
| 1456 |
<p id="section-toc.1-1.10.2.1.2.1.1"><a href="#section-10.1.1" class="xref">10.1.1</a>. <a href="#name-candidate-attribute-2" class="xref">"candidate" Attribute</a><a href="#section-toc.1-1.10.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1457 |
</li> |
| 1458 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.2"> |
| 1459 |
<p id="section-toc.1-1.10.2.1.2.2.1"><a href="#section-10.1.2" class="xref">10.1.2</a>. <a href="#name-remote-candidates-attribute-2" class="xref">"remote-candidates" Attribute</a><a href="#section-toc.1-1.10.2.1.2.2.1" class="pilcrow">¶</a></p> |
| 1460 |
</li> |
| 1461 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.3"> |
| 1462 |
<p id="section-toc.1-1.10.2.1.2.3.1"><a href="#section-10.1.3" class="xref">10.1.3</a>. <a href="#name-ice-lite-attribute" class="xref">"ice-lite" Attribute</a><a href="#section-toc.1-1.10.2.1.2.3.1" class="pilcrow">¶</a></p> |
| 1463 |
</li> |
| 1464 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.4"> |
| 1465 |
<p id="section-toc.1-1.10.2.1.2.4.1"><a href="#section-10.1.4" class="xref">10.1.4</a>. <a href="#name-ice-mismatch-attribute" class="xref">"ice-mismatch" Attribute</a><a href="#section-toc.1-1.10.2.1.2.4.1" class="pilcrow">¶</a></p> |
| 1466 |
</li> |
| 1467 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.5"> |
| 1468 |
<p id="section-toc.1-1.10.2.1.2.5.1"><a href="#section-10.1.5" class="xref">10.1.5</a>. <a href="#name-ice-pwd-attribute" class="xref">"ice-pwd" Attribute</a><a href="#section-toc.1-1.10.2.1.2.5.1" class="pilcrow">¶</a></p> |
| 1469 |
</li> |
| 1470 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.6"> |
| 1471 |
<p id="section-toc.1-1.10.2.1.2.6.1"><a href="#section-10.1.6" class="xref">10.1.6</a>. <a href="#name-ice-ufrag-attribute" class="xref">"ice-ufrag" Attribute</a><a href="#section-toc.1-1.10.2.1.2.6.1" class="pilcrow">¶</a></p> |
| 1472 |
</li> |
| 1473 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.7"> |
| 1474 |
<p id="section-toc.1-1.10.2.1.2.7.1"><a href="#section-10.1.7" class="xref">10.1.7</a>. <a href="#name-ice-options-attribute-2" class="xref">"ice-options" Attribute</a><a href="#section-toc.1-1.10.2.1.2.7.1" class="pilcrow">¶</a></p> |
| 1475 |
</li> |
| 1476 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10.2.1.2.8"> |
| 1477 |
<p id="section-toc.1-1.10.2.1.2.8.1"><a href="#section-10.1.8" class="xref">10.1.8</a>. <a href="#name-ice-pacing-attribute-2" class="xref">"ice-pacing" Attribute</a><a href="#section-toc.1-1.10.2.1.2.8.1" class="pilcrow">¶</a></p> |
| 1478 |
</li> |
| 1479 |
</ul> |
| 1480 |
</li> |
| 1481 |
<li class="toc ulEmpty compact" id="section-toc.1-1.10.2.2"> |
| 1482 |
<p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>. <a href="#name-interactive-connectivity-es" class="xref">Interactive Connectivity Establishment (ICE) Options Registry</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p> |
| 1483 |
</li> |
| 1484 |
<li class="toc ulEmpty compact" id="section-toc.1-1.10.2.3"> |
| 1485 |
<p id="section-toc.1-1.10.2.3.1"><a href="#section-10.3" class="xref">10.3</a>. <a href="#name-candidate-attribute-extensi" class="xref">Candidate Attribute Extension Subregistry Establishment</a><a href="#section-toc.1-1.10.2.3.1" class="pilcrow">¶</a></p> |
| 1486 |
</li> |
| 1487 |
</ul> |
| 1488 |
</li> |
| 1489 |
<li class="compact ulEmpty toc" id="section-toc.1-1.11"> |
| 1490 |
<p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-changes-from-rfc-5245" class="xref">Changes from RFC 5245</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p> |
| 1491 |
</li> |
| 1492 |
<li class="compact ulEmpty toc" id="section-toc.1-1.12"> |
| 1493 |
<p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p> |
| 1494 |
<ul class="toc ulEmpty compact"> |
| 1495 |
<li class="toc ulEmpty compact" id="section-toc.1-1.12.2.1"> |
| 1496 |
<p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.12.2.1.1" class="pilcrow">¶</a></p> |
| 1497 |
</li> |
| 1498 |
<li class="toc ulEmpty compact" id="section-toc.1-1.12.2.2"> |
| 1499 |
<p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.12.2.2.1" class="pilcrow">¶</a></p> |
| 1500 |
</li> |
| 1501 |
</ul> |
| 1502 |
</li> |
| 1503 |
<li class="compact ulEmpty toc" id="section-toc.1-1.13"> |
| 1504 |
<p id="section-toc.1-1.13.1"><a href="#section-appendix.a" class="xref">Appendix A</a>. <a href="#name-examples" class="xref">Examples</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p> |
| 1505 |
</li> |
| 1506 |
<li class="compact ulEmpty toc" id="section-toc.1-1.14"> |
| 1507 |
<p id="section-toc.1-1.14.1"><a href="#section-appendix.b" class="xref">Appendix B</a>. <a href="#name-the-remote-candidates-attri" class="xref">The "remote-candidates" Attribute</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p> |
| 1508 |
</li> |
| 1509 |
<li class="compact ulEmpty toc" id="section-toc.1-1.15"> |
| 1510 |
<p id="section-toc.1-1.15.1"><a href="#section-appendix.c" class="xref">Appendix C</a>. <a href="#name-why-is-the-conflict-resolut" class="xref">Why Is the Conflict Resolution Mechanism Needed?</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p> |
| 1511 |
</li> |
| 1512 |
<li class="compact ulEmpty toc" id="section-toc.1-1.16"> |
| 1513 |
<p id="section-toc.1-1.16.1"><a href="#section-appendix.d" class="xref">Appendix D</a>. <a href="#name-why-send-an-updated-offer" class="xref">Why Send an Updated Offer?</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p> |
| 1514 |
</li> |
| 1515 |
<li class="compact ulEmpty toc" id="section-toc.1-1.17"> |
| 1516 |
<p id="section-toc.1-1.17.1"><a href="#section-appendix.e" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.17.1" class="pilcrow">¶</a></p> |
| 1517 |
</li> |
| 1518 |
<li class="compact ulEmpty toc" id="section-toc.1-1.18"> |
| 1519 |
<p id="section-toc.1-1.18.1"><a href="#section-appendix.f" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.18.1" class="pilcrow">¶</a></p> |
| 1520 |
</li> |
| 1521 |
<li class="compact ulEmpty toc" id="section-toc.1-1.19"> |
| 1522 |
<p id="section-toc.1-1.19.1"><a href="#section-appendix.g" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.19.1" class="pilcrow">¶</a></p> |
| 1523 |
</li> |
| 1524 |
</ul> |
| 1525 |
</nav> |
| 1526 |
</section> |
| 1527 |
</div> |
| 1528 |
<div id="intro"> |
| 1529 |
<section id="section-1"> |
| 1530 |
<h2 id="name-introduction"> |
| 1531 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1532 |
</h2> |
| 1533 |
<p id="section-1-1"> |
| 1534 |
This document describes how Interactive Connectivity Establishment (ICE) is |
| 1535 |
used with Session Description Protocol (SDP) offer/answer <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>. The ICE specification <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> describes procedures that are common to |
| 1536 |
all usages of ICE, and this document gives the additional details needed to |
| 1537 |
use ICE with SDP offer/answer.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1538 |
<p id="section-1-2">This document obsoletes RFCs 5245 and 6336.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1539 |
<p id="section-1-3"> |
| 1540 |
NOTE: Previously both the common ICE procedures, and the SDP offer/answer |
| 1541 |
specific details, were described in <span>[<a href="#RFC5245" class="xref">RFC5245</a>]</span>. <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> obsoleted <span>[<a href="#RFC5245" class="xref">RFC5245</a>]</span>, and the SDP offer/answer-specific details |
| 1542 |
were removed from the document. <a href="#sec.5245" class="xref">Section 11</a> |
| 1543 |
describes the changes to the SDP offer/answer-specific details specified in |
| 1544 |
this document.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1545 |
</section> |
| 1546 |
</div> |
| 1547 |
<section id="section-2"> |
| 1548 |
<h2 id="name-conventions"> |
| 1549 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions" class="section-name selfRef">Conventions</a> |
| 1550 |
</h2> |
| 1551 |
<p id="section-2-1"> |
| 1552 |
The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", |
| 1553 |
"<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", |
| 1554 |
"<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", |
| 1555 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are |
| 1556 |
to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> |
| 1557 |
<span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, |
| 1558 |
as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1559 |
</section> |
| 1560 |
<section id="section-3"> |
| 1561 |
<h2 id="name-terminology"> |
| 1562 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1563 |
</h2> |
| 1564 |
<p id="section-3-1"> |
| 1565 |
Readers should be familiar with the terminology defined in <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>, in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, and the following:<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1566 |
<span class="break"></span><dl class="dlParallel" id="section-3-2"> |
| 1567 |
<dt id="section-3-2.1">Default Destination/Candidate:</dt> |
| 1568 |
<dd style="margin-left: 1.5em" id="section-3-2.2"> |
| 1569 |
The default destination for a component of a data stream is the transport |
| 1570 |
address that would be used by an agent that is not ICE aware. A default |
| 1571 |
candidate for a component is one whose transport address matches the default |
| 1572 |
destination for that component. For the RTP component, the default connection |
| 1573 |
address is in the "c=" line of the SDP, and the port and transport protocol |
| 1574 |
are in the "m=" line. For the RTP Control Protocol (RTCP) component, the |
| 1575 |
address and port are indicated using the "rtcp" attribute defined in <span>[<a href="#RFC3605" class="xref">RFC3605</a>]</span>, if present; otherwise, the RTCP component |
| 1576 |
address is the same as the address of the RTP component, and its port is one |
| 1577 |
greater than the port of the RTP component.<a href="#section-3-2.2" class="pilcrow">¶</a> |
| 1578 |
</dd> |
| 1579 |
<dd class="break"></dd> |
| 1580 |
</dl> |
| 1581 |
</section> |
| 1582 |
<section id="section-4"> |
| 1583 |
<h2 id="name-sdp-offer-answer-procedures"> |
| 1584 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-sdp-offer-answer-procedures" class="section-name selfRef">SDP Offer/Answer Procedures</a> |
| 1585 |
</h2> |
| 1586 |
<section id="section-4.1"> |
| 1587 |
<h3 id="name-introduction-2"> |
| 1588 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-introduction-2" class="section-name selfRef">Introduction</a> |
| 1589 |
</h3> |
| 1590 |
<p id="section-4.1-1"><span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> defines ICE candidate |
| 1591 |
exchange as the process for ICE agents (initiator and responder) to |
| 1592 |
exchange their candidate information required for ICE processing at |
| 1593 |
the agents. For the purposes of this specification, the candidate |
| 1594 |
exchange process corresponds to the Offer/Answer protocol <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>, and the terms "offerer" and |
| 1595 |
"answerer" correspond to the initiator and responder roles from <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> respectively.<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 1596 |
<p id="section-4.1-2"> |
| 1597 |
Once the initiating agent has gathered, pruned, and prioritized its set of |
| 1598 |
candidates <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, the candidate exchange |
| 1599 |
with the peer agent begins.<a href="#section-4.1-2" class="pilcrow">¶</a></p> |
| 1600 |
</section> |
| 1601 |
<section id="section-4.2"> |
| 1602 |
<h3 id="name-generic-procedures"> |
| 1603 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-generic-procedures" class="section-name selfRef">Generic Procedures</a> |
| 1604 |
</h3> |
| 1605 |
<div id="sec-encoding"> |
| 1606 |
<section id="section-4.2.1"> |
| 1607 |
<h4 id="name-encoding"> |
| 1608 |
<a href="#section-4.2.1" class="section-number selfRef">4.2.1. </a><a href="#name-encoding" class="section-name selfRef">Encoding</a> |
| 1609 |
</h4> |
| 1610 |
<p id="section-4.2.1-1"><a href="#sec-grammar" class="xref">Section 5</a> provides detailed |
| 1611 |
rules for constructing various SDP attributes defined in this |
| 1612 |
specification.<a href="#section-4.2.1-1" class="pilcrow">¶</a></p> |
| 1613 |
<section id="section-4.2.1.1"> |
| 1614 |
<h5 id="name-data-streams"> |
| 1615 |
<a href="#section-4.2.1.1" class="section-number selfRef">4.2.1.1. </a><a href="#name-data-streams" class="section-name selfRef">Data Streams</a> |
| 1616 |
</h5> |
| 1617 |
<p id="section-4.2.1.1-1"> |
| 1618 |
Each data stream <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> is represented by |
| 1619 |
an SDP media description ("m=" section).<a href="#section-4.2.1.1-1" class="pilcrow">¶</a></p> |
| 1620 |
</section> |
| 1621 |
<section id="section-4.2.1.2"> |
| 1622 |
<h5 id="name-candidates"> |
| 1623 |
<a href="#section-4.2.1.2" class="section-number selfRef">4.2.1.2. </a><a href="#name-candidates" class="section-name selfRef">Candidates</a> |
| 1624 |
</h5> |
| 1625 |
<p id="section-4.2.1.2-1"> |
| 1626 |
Within an "m=" section, each candidate (including the default candidate) associated |
| 1627 |
with the data stream is represented by an SDP "candidate" attribute.<a href="#section-4.2.1.2-1" class="pilcrow">¶</a></p> |
| 1628 |
<p id="section-4.2.1.2-2"> |
| 1629 |
Prior to nomination, the "c=" line associated with an "m=" section contains |
| 1630 |
the connection address of the default candidate, while the "m=" line contains the port |
| 1631 |
and transport protocol of the default candidate for that "m=" section.<a href="#section-4.2.1.2-2" class="pilcrow">¶</a></p> |
| 1632 |
<p id="section-4.2.1.2-3"> |
| 1633 |
After nomination, the "c=" line for a given "m=" section contains the |
| 1634 |
connection address of the nominated candidate (the local candidate of the |
| 1635 |
nominated candidate pair), and the "m=" line contains the port and |
| 1636 |
transport protocol corresponding to the nominated candidate for that |
| 1637 |
"m=" section.<a href="#section-4.2.1.2-3" class="pilcrow">¶</a></p> |
| 1638 |
</section> |
| 1639 |
<section id="section-4.2.1.3"> |
| 1640 |
<h5 id="name-username-and-password"> |
| 1641 |
<a href="#section-4.2.1.3" class="section-number selfRef">4.2.1.3. </a><a href="#name-username-and-password" class="section-name selfRef">Username and Password</a> |
| 1642 |
</h5> |
| 1643 |
<p id="section-4.2.1.3-1"> |
| 1644 |
The ICE username is represented by an SDP "ice-ufrag" attribute, and the ICE |
| 1645 |
password is represented by an SDP "ice-pwd" attribute.<a href="#section-4.2.1.3-1" class="pilcrow">¶</a></p> |
| 1646 |
</section> |
| 1647 |
<section id="section-4.2.1.4"> |
| 1648 |
<h5 id="name-lite-implementations"> |
| 1649 |
<a href="#section-4.2.1.4" class="section-number selfRef">4.2.1.4. </a><a href="#name-lite-implementations" class="section-name selfRef">Lite Implementations</a> |
| 1650 |
</h5> |
| 1651 |
<p id="section-4.2.1.4-1"> |
| 1652 |
An ICE-lite implementation <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> <span class="bcp14">MUST</span> include an SDP "ice-lite" attribute. |
| 1653 |
A full implementation <span class="bcp14">MUST NOT</span> include that attribute.<a href="#section-4.2.1.4-1" class="pilcrow">¶</a></p> |
| 1654 |
</section> |
| 1655 |
<section id="section-4.2.1.5"> |
| 1656 |
<h5 id="name-ice-extensions"> |
| 1657 |
<a href="#section-4.2.1.5" class="section-number selfRef">4.2.1.5. </a><a href="#name-ice-extensions" class="section-name selfRef">ICE Extensions</a> |
| 1658 |
</h5> |
| 1659 |
<p id="section-4.2.1.5-1"> |
| 1660 |
An agent uses the SDP "ice-options" attribute to indicate support of ICE |
| 1661 |
extensions.<a href="#section-4.2.1.5-1" class="pilcrow">¶</a></p> |
| 1662 |
<p id="section-4.2.1.5-2"> |
| 1663 |
An agent compliant with this specification <span class="bcp14">MUST</span> include an SDP "ice-options" |
| 1664 |
attribute with an "ice2" attribute value <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>. If an agent receives an SDP offer |
| 1665 |
or answer that indicates ICE support, but that does not contain an SDP "ice-options" attribute with an "ice2" attribute value, |
| 1666 |
the agent can assume that the peer is compliant to <span>[<a href="#RFC5245" class="xref">RFC5245</a>]</span>.<a href="#section-4.2.1.5-2" class="pilcrow">¶</a></p> |
| 1667 |
</section> |
| 1668 |
<section id="section-4.2.1.6"> |
| 1669 |
<h5 id="name-inactive-and-disabled-data-"> |
| 1670 |
<a href="#section-4.2.1.6" class="section-number selfRef">4.2.1.6. </a><a href="#name-inactive-and-disabled-data-" class="section-name selfRef">Inactive and Disabled Data Streams</a> |
| 1671 |
</h5> |
| 1672 |
<p id="section-4.2.1.6-1"> |
| 1673 |
If an "m=" section is marked as inactive <span>[<a href="#RFC4566" class="xref">RFC4566</a>]</span>, or has a bandwidth |
| 1674 |
value of zero <span>[<a href="#RFC4566" class="xref">RFC4566</a>]</span>, the agent <span class="bcp14">MUST</span> still include ICE-related SDP |
| 1675 |
attributes.<a href="#section-4.2.1.6-1" class="pilcrow">¶</a></p> |
| 1676 |
<p id="section-4.2.1.6-2"> |
| 1677 |
If the port value associated with an "m=" section is set to zero (implying a |
| 1678 |
disabled stream) as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc3264#section-8.2" class="relref">Section 8.2</a> of [<a href="#RFC3264" class="xref">RFC3264</a>]</span>, the agent <span class="bcp14">SHOULD NOT</span> |
| 1679 |
include ICE-related SDP "candidate" attributes in that "m=" section, unless an |
| 1680 |
SDP extension specifying otherwise is used.<a href="#section-4.2.1.6-2" class="pilcrow">¶</a></p> |
| 1681 |
</section> |
| 1682 |
</section> |
| 1683 |
</div> |
| 1684 |
<section id="section-4.2.2"> |
| 1685 |
<h4 id="name-rtp-rtcp-considerations"> |
| 1686 |
<a href="#section-4.2.2" class="section-number selfRef">4.2.2. </a><a href="#name-rtp-rtcp-considerations" class="section-name selfRef">RTP/RTCP Considerations</a> |
| 1687 |
</h4> |
| 1688 |
<p id="section-4.2.2-1"> |
| 1689 |
If an agent utilizes both RTP and RTCP, and separate ports |
| 1690 |
are used for RTP and RTCP, the agent <span class="bcp14">MUST</span> include SDP "candidate" |
| 1691 |
attributes for both the RTP and RTCP components.<a href="#section-4.2.2-1" class="pilcrow">¶</a></p> |
| 1692 |
<p id="section-4.2.2-2"> |
| 1693 |
The agent includes an SDP "rtcp" attribute following the procedures |
| 1694 |
in <span>[<a href="#RFC3605" class="xref">RFC3605</a>]</span>. Hence, in the cases where the RTCP |
| 1695 |
port value is one higher than the RTP port value and the RTCP component |
| 1696 |
address the same as the address of the RTP component, the SDP "rtcp" attribute |
| 1697 |
might be omitted.<a href="#section-4.2.2-2" class="pilcrow">¶</a></p> |
| 1698 |
<p id="section-4.2.2-3"> |
| 1699 |
NOTE: <span>[<a href="#RFC5245" class="xref">RFC5245</a>]</span> required that an agent always includes the |
| 1700 |
SDP "rtcp" attribute, even if the RTCP port value was one higher than the |
| 1701 |
RTP port value. This specification aligns the "rtcp" attribute procedures |
| 1702 |
with <span>[<a href="#RFC3605" class="xref">RFC3605</a>]</span>.<a href="#section-4.2.2-3" class="pilcrow">¶</a></p> |
| 1703 |
<p id="section-4.2.2-4"> |
| 1704 |
If the agent does not utilize RTCP, it indicates that by including "RS:0" |
| 1705 |
and "RR:0" SDP attributes as described in <span>[<a href="#RFC3556" class="xref">RFC3556</a>]</span>.<a href="#section-4.2.2-4" class="pilcrow">¶</a></p> |
| 1706 |
</section> |
| 1707 |
<section id="section-4.2.3"> |
| 1708 |
<h4 id="name-determining-role"> |
| 1709 |
<a href="#section-4.2.3" class="section-number selfRef">4.2.3. </a><a href="#name-determining-role" class="section-name selfRef">Determining Role</a> |
| 1710 |
</h4> |
| 1711 |
<p id="section-4.2.3-1"> |
| 1712 |
The offerer acts as the initiating agent. The answerer acts as the |
| 1713 |
responding agent. The ICE roles (controlling and controlled) are determined |
| 1714 |
using the procedures in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-4.2.3-1" class="pilcrow">¶</a></p> |
| 1715 |
</section> |
| 1716 |
<section id="section-4.2.4"> |
| 1717 |
<h4 id="name-stun-considerations"> |
| 1718 |
<a href="#section-4.2.4" class="section-number selfRef">4.2.4. </a><a href="#name-stun-considerations" class="section-name selfRef">STUN Considerations</a> |
| 1719 |
</h4> |
| 1720 |
<p id="section-4.2.4-1"> |
| 1721 |
Once an agent has provided its local candidates to its peer in an SDP |
| 1722 |
offer or answer, the agent <span class="bcp14">MUST</span> be prepared to receive STUN |
| 1723 |
(Session Traversal Utilities for NAT, <span>[<a href="#RFC5389" class="xref">RFC5389</a>]</span>) connectivity |
| 1724 |
check Binding requests on those candidates.<a href="#section-4.2.4-1" class="pilcrow">¶</a></p> |
| 1725 |
</section> |
| 1726 |
<div id="sec-ice-mismatch"> |
| 1727 |
<section id="section-4.2.5"> |
| 1728 |
<h4 id="name-verifying-ice-support-proce"> |
| 1729 |
<a href="#section-4.2.5" class="section-number selfRef">4.2.5. </a><a href="#name-verifying-ice-support-proce" class="section-name selfRef">Verifying ICE Support Procedures</a> |
| 1730 |
</h4> |
| 1731 |
<p id="section-4.2.5-1"> |
| 1732 |
An ICE agent indicates support of ICE by including |
| 1733 |
at least the SDP "ice-pwd" and "ice-ufrag" attributes in an offer or answer. |
| 1734 |
An ICE agent compliant with this specification <span class="bcp14">MUST</span> also include an |
| 1735 |
SDP "ice-options" attribute with an "ice2" attribute value.<a href="#section-4.2.5-1" class="pilcrow">¶</a></p> |
| 1736 |
<p id="section-4.2.5-2"> |
| 1737 |
The agents will proceed with the ICE procedures defined in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> and |
| 1738 |
this specification if, for each data stream in the SDP it received, the |
| 1739 |
default destination for each component of that data stream appears in |
| 1740 |
a "candidate" attribute. For example, in the case of RTP, the |
| 1741 |
connection address, port, and transport protocol in the |
| 1742 |
"c=" and "m=" lines, respectively, appear in a "candidate" |
| 1743 |
attribute, and the value in the "rtcp" attribute appears in a "candidate" |
| 1744 |
attribute.<a href="#section-4.2.5-2" class="pilcrow">¶</a></p> |
| 1745 |
<p id="section-4.2.5-3"> |
| 1746 |
This specification provides no guidance on how an agent should proceed |
| 1747 |
in the cases where the above condition is not met with the few |
| 1748 |
exceptions noted below:<a href="#section-4.2.5-3" class="pilcrow">¶</a></p> |
| 1749 |
<ol start="1" type="1" class="normal type-1" id="section-4.2.5-4"> |
| 1750 |
<li id="section-4.2.5-4.1"> |
| 1751 |
The presence of certain Application Layer Gateways might modify |
| 1752 |
the transport address information as described in <a href="#sec-alg-sip" class="xref">Section 8</a>. |
| 1753 |
The behavior of the responding agent in such a situation is |
| 1754 |
implementation dependent. Informally, the responding agent might |
| 1755 |
consider the mismatched transport address information as a |
| 1756 |
plausible new candidate learned from the peer and continue its |
| 1757 |
ICE processing with that transport address included. |
| 1758 |
Alternatively, the responding agent <span class="bcp14">MAY</span> include an "ice-mismatch" |
| 1759 |
attribute in its answer for such data streams. If an agent chooses to |
| 1760 |
include an "ice-mismatch" attribute in its answer for a data stream, |
| 1761 |
then it <span class="bcp14">MUST</span> also omit "candidate" attributes, <span class="bcp14">MUST</span> terminate |
| 1762 |
the usage of ICE procedures, and <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> |
| 1763 |
procedures <span class="bcp14">MUST</span> be used instead for this data stream.<a href="#section-4.2.5-4.1" class="pilcrow">¶</a> |
| 1764 |
</li> |
| 1765 |
<li id="section-4.2.5-4.2"> |
| 1766 |
The transport address from the peer for the default destination |
| 1767 |
is set to IPv4/IPv6 address values "0.0.0.0"/"::" and port value of "9". |
| 1768 |
This <span class="bcp14">MUST NOT</span> be considered as an ICE failure by the peer agent, and |
| 1769 |
the ICE processing <span class="bcp14">MUST</span> continue as usual.<a href="#section-4.2.5-4.2" class="pilcrow">¶</a> |
| 1770 |
</li> |
| 1771 |
<li id="section-4.2.5-4.3"> |
| 1772 |
In some cases, the controlling/initiator agent may receive an SDP answer |
| 1773 |
that may omit "candidate" attributes for the data stream, and instead |
| 1774 |
include a media-level "ice-mismatch" attribute. This signals to the |
| 1775 |
offerer that the answerer supports ICE, but that ICE processing was not |
| 1776 |
used for this data stream. In this case, ICE processing <span class="bcp14">MUST</span> be terminated |
| 1777 |
for this data stream, and <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> procedures <span class="bcp14">MUST</span> be followed instead.<a href="#section-4.2.5-4.3" class="pilcrow">¶</a> |
| 1778 |
</li> |
| 1779 |
<li id="section-4.2.5-4.4"> |
| 1780 |
The transport address from the peer for the default destination is |
| 1781 |
an FQDN. Regardless of the procedures used to resolve FQDN or the |
| 1782 |
resolution result, this <span class="bcp14">MUST NOT</span> be considered as an ICE failure by |
| 1783 |
the peer agent, and the ICE processing <span class="bcp14">MUST</span> continue as usual.<a href="#section-4.2.5-4.4" class="pilcrow">¶</a> |
| 1784 |
</li> |
| 1785 |
</ol> |
| 1786 |
</section> |
| 1787 |
</div> |
| 1788 |
<section id="section-4.2.6"> |
| 1789 |
<h4 id="name-sdp-example"> |
| 1790 |
<a href="#section-4.2.6" class="section-number selfRef">4.2.6. </a><a href="#name-sdp-example" class="section-name selfRef">SDP Example</a> |
| 1791 |
</h4> |
| 1792 |
<p id="section-4.2.6-1"> |
| 1793 |
The following is an example SDP message that includes ICE attributes |
| 1794 |
(lines folded for readability):<a href="#section-4.2.6-1" class="pilcrow">¶</a></p> |
| 1795 |
<div id="section-4.2.6-2"> |
| 1796 |
<pre class="sourcecode lang-sdp"> |
| 1797 |
v=0 |
| 1798 |
o=jdoe 2890844526 2890842807 IN IP4 203.0.113.141 |
| 1799 |
s= |
| 1800 |
c=IN IP4 192.0.2.3 |
| 1801 |
t=0 0 |
| 1802 |
a=ice-options:ice2 |
| 1803 |
a=ice-pacing:50 |
| 1804 |
a=ice-pwd:asd88fgpdd777uzjYhagZg |
| 1805 |
a=ice-ufrag:8hhY |
| 1806 |
m=audio 45664 RTP/AVP 0 |
| 1807 |
b=RS:0 |
| 1808 |
b=RR:0 |
| 1809 |
a=rtpmap:0 PCMU/8000 |
| 1810 |
a=candidate:1 1 UDP 2130706431 203.0.113.141 8998 typ host |
| 1811 |
a=candidate:2 1 UDP 1694498815 192.0.2.3 45664 typ srflx raddr |
| 1812 |
203.0.113.141 rport 8998 |
| 1813 |
</pre><a href="#section-4.2.6-2" class="pilcrow">¶</a> |
| 1814 |
</div> |
| 1815 |
</section> |
| 1816 |
</section> |
| 1817 |
<section id="section-4.3"> |
| 1818 |
<h3 id="name-initial-offer-answer-exchan"> |
| 1819 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-initial-offer-answer-exchan" class="section-name selfRef">Initial Offer/Answer Exchange</a> |
| 1820 |
</h3> |
| 1821 |
<section id="section-4.3.1"> |
| 1822 |
<h4 id="name-sending-the-initial-offer"> |
| 1823 |
<a href="#section-4.3.1" class="section-number selfRef">4.3.1. </a><a href="#name-sending-the-initial-offer" class="section-name selfRef">Sending the Initial Offer</a> |
| 1824 |
</h4> |
| 1825 |
<p id="section-4.3.1-1"> |
| 1826 |
When an offerer generates the initial offer, in each "m=" section it <span class="bcp14">MUST</span> |
| 1827 |
include SDP "candidate" attributes for each available candidate associated |
| 1828 |
with the "m=" section. In addition, the offerer <span class="bcp14">MUST</span> include an SDP "ice-ufrag" |
| 1829 |
attribute, an SDP "ice-pwd" attribute, and an SDP "ice-options" attribute with |
| 1830 |
an "ice2" attribute value in the offer. If the offerer is a full ICE implementation, |
| 1831 |
it <span class="bcp14">SHOULD</span> include an "ice-pacing" attribute in the offer (if not included, the |
| 1832 |
default value will apply). A lite ICE implementation <span class="bcp14">MUST NOT</span> include the "ice-pacing" |
| 1833 |
attribute in the offer (as it will not perform connectivity checks).<a href="#section-4.3.1-1" class="pilcrow">¶</a></p> |
| 1834 |
<p id="section-4.3.1-2"> |
| 1835 |
It is valid for an offer "m=" line to include no SDP "candidate" attributes |
| 1836 |
and have the default destination set to the IP address values |
| 1837 |
"0.0.0.0"/"::" and the port value to "9". |
| 1838 |
This implies that the offering agent is only going to use peer-reflexive |
| 1839 |
candidates or will provide additional candidates in subsequent signaling |
| 1840 |
messages.<a href="#section-4.3.1-2" class="pilcrow">¶</a></p> |
| 1841 |
<span class="break"></span><dl class="dlParallel" id="section-4.3.1-3"> |
| 1842 |
<dt id="section-4.3.1-3.1">Note:</dt> |
| 1843 |
<dd style="margin-left: 1.5em" id="section-4.3.1-3.2"> |
| 1844 |
Within the scope of this document, "initial offer" refers to the first |
| 1845 |
SDP offer that is sent in order to negotiate usage of ICE. It might, or |
| 1846 |
might not, be the initial SDP offer of the SDP session.<a href="#section-4.3.1-3.2" class="pilcrow">¶</a> |
| 1847 |
</dd> |
| 1848 |
<dd class="break"></dd> |
| 1849 |
</dl> |
| 1850 |
<span class="break"></span><dl class="dlParallel" id="section-4.3.1-4"> |
| 1851 |
<dt id="section-4.3.1-4.1">Note:</dt> |
| 1852 |
<dd style="margin-left: 1.5em" id="section-4.3.1-4.2"> |
| 1853 |
The procedures in this document only consider "m=" sections associated |
| 1854 |
with data streams where ICE is used.<a href="#section-4.3.1-4.2" class="pilcrow">¶</a> |
| 1855 |
</dd> |
| 1856 |
<dd class="break"></dd> |
| 1857 |
</dl> |
| 1858 |
</section> |
| 1859 |
<section id="section-4.3.2"> |
| 1860 |
<h4 id="name-sending-the-initial-answer"> |
| 1861 |
<a href="#section-4.3.2" class="section-number selfRef">4.3.2. </a><a href="#name-sending-the-initial-answer" class="section-name selfRef">Sending the Initial Answer</a> |
| 1862 |
</h4> |
| 1863 |
<p id="section-4.3.2-1"> |
| 1864 |
When an answerer receives an initial offer indicating |
| 1865 |
that the offerer supports ICE, and if the answerer accepts |
| 1866 |
the offer and the usage of ICE, the answerer <span class="bcp14">MUST</span> include |
| 1867 |
in each "m=" section within the answer the SDP "candidate" |
| 1868 |
attributes for each available candidate associated with |
| 1869 |
the "m=" section. |
| 1870 |
In addition, the answerer <span class="bcp14">MUST</span> include an SDP "ice-ufrag" |
| 1871 |
attribute, an SDP "ice-pwd" attribute, and an SDP "ice-options" |
| 1872 |
attribute with an "ice2" attribute value in the answer. If the |
| 1873 |
answerer is a full ICE implementation, it <span class="bcp14">SHOULD</span> include an |
| 1874 |
"ice-pacing" attribute in the answer (if not included, the |
| 1875 |
default value will apply). A lite ICE implementation <span class="bcp14">MUST NOT</span> |
| 1876 |
include the "ice-pacing" attribute in the answer (as it will |
| 1877 |
not perform connectivity checks).<a href="#section-4.3.2-1" class="pilcrow">¶</a></p> |
| 1878 |
<p id="section-4.3.2-2"> |
| 1879 |
In each "m=" line, the answerer <span class="bcp14">MUST</span> use the same transport |
| 1880 |
protocol as was used in the offer "m=" line. If none of |
| 1881 |
the candidates in the "m=" line in the answer uses the same |
| 1882 |
transport protocol as indicated in the offer "m=" line, |
| 1883 |
then, in order to avoid ICE mismatch, the default destination |
| 1884 |
<span class="bcp14">MUST</span> be set to IP address values "0.0.0.0"/"::" and |
| 1885 |
port value of "9".<a href="#section-4.3.2-2" class="pilcrow">¶</a></p> |
| 1886 |
<p id="section-4.3.2-3"> |
| 1887 |
It is also valid for an answer "m=" line to include no SDP |
| 1888 |
"candidate" attributes and have the default destination set |
| 1889 |
to the IP address values "0.0.0.0"/"::" and the port value to "9". |
| 1890 |
This implies that the answering agent is only going to use |
| 1891 |
peer-reflexive candidates or that additional candidates would be |
| 1892 |
provided in subsequent signaling messages.<a href="#section-4.3.2-3" class="pilcrow">¶</a></p> |
| 1893 |
<p id="section-4.3.2-4"> |
| 1894 |
Once the answerer has sent the answer, it can start performing |
| 1895 |
connectivity checks towards the peer candidates that were provided |
| 1896 |
in the offer.<a href="#section-4.3.2-4" class="pilcrow">¶</a></p> |
| 1897 |
<p id="section-4.3.2-5"> |
| 1898 |
If the offer does not indicate support of ICE (<a href="#sec-ice-mismatch" class="xref">Section 4.2.5</a>), the answerer |
| 1899 |
<span class="bcp14">MUST NOT</span> accept the usage of ICE. If the answerer still accepts |
| 1900 |
the offer, the answerer <span class="bcp14">MUST NOT</span> include any ICE-related SDP |
| 1901 |
attributes in the answer. Instead, the answerer will generate |
| 1902 |
the answer according to normal offer/answer procedures <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>.<a href="#section-4.3.2-5" class="pilcrow">¶</a></p> |
| 1903 |
<p id="section-4.3.2-6"> |
| 1904 |
If the answerer detects a possibility of an ICE mismatch, |
| 1905 |
procedures described in <a href="#sec-ice-mismatch" class="xref">Section 4.2.5</a> are followed.<a href="#section-4.3.2-6" class="pilcrow">¶</a></p> |
| 1906 |
</section> |
| 1907 |
<section id="section-4.3.3"> |
| 1908 |
<h4 id="name-receiving-the-initial-answe"> |
| 1909 |
<a href="#section-4.3.3" class="section-number selfRef">4.3.3. </a><a href="#name-receiving-the-initial-answe" class="section-name selfRef">Receiving the Initial Answer</a> |
| 1910 |
</h4> |
| 1911 |
<p id="section-4.3.3-1"> |
| 1912 |
When an offerer receives an initial answer that indicates |
| 1913 |
that the answerer supports ICE, it can start performing |
| 1914 |
connectivity checks towards the peer candidates that were |
| 1915 |
provided in the answer.<a href="#section-4.3.3-1" class="pilcrow">¶</a></p> |
| 1916 |
<p id="section-4.3.3-2"> |
| 1917 |
If the answer does not indicate that the answerer supports ICE, or if the |
| 1918 |
answerer included "ice-mismatch" attributes for all the active data streams |
| 1919 |
in the answer, the offerer <span class="bcp14">MUST</span> terminate the usage of ICE for |
| 1920 |
the entire session, and <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> procedures |
| 1921 |
<span class="bcp14">MUST</span> be followed instead.<a href="#section-4.3.3-2" class="pilcrow">¶</a></p> |
| 1922 |
<p id="section-4.3.3-3"> |
| 1923 |
On the other hand, if the answer indicates support for |
| 1924 |
ICE but includes "ice-mismatch" in certain active data |
| 1925 |
streams, then the offerer <span class="bcp14">MUST</span> terminate the usage of ICE |
| 1926 |
procedures, and <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> procedures |
| 1927 |
<span class="bcp14">MUST</span> be used instead for only these data streams. Also, ICE |
| 1928 |
procedures <span class="bcp14">MUST</span> be used for data streams where an "ice-mismatch" |
| 1929 |
attribute was not included.<a href="#section-4.3.3-3" class="pilcrow">¶</a></p> |
| 1930 |
<p id="section-4.3.3-4"> |
| 1931 |
If the offerer detects an ICE mismatch for one or more data streams in the |
| 1932 |
answer, as described in <a href="#sec-ice-mismatch" class="xref">Section 4.2.5</a>, |
| 1933 |
the offerer <span class="bcp14">MUST</span> terminate the usage of ICE for the entire |
| 1934 |
session. The subsequent actions taken by the offerer are implementation |
| 1935 |
dependent and are out of the scope of this specification.<a href="#section-4.3.3-4" class="pilcrow">¶</a></p> |
| 1936 |
</section> |
| 1937 |
<section id="section-4.3.4"> |
| 1938 |
<h4 id="name-concluding-ice"> |
| 1939 |
<a href="#section-4.3.4" class="section-number selfRef">4.3.4. </a><a href="#name-concluding-ice" class="section-name selfRef">Concluding ICE</a> |
| 1940 |
</h4> |
| 1941 |
<p id="section-4.3.4-1"> |
| 1942 |
Once the agent has successfully nominated a pair <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, the state of the checklist associated with the pair is set |
| 1943 |
to Completed. Once the state of each checklist is set to either Completed or |
| 1944 |
Failed, for each Completed checklist, the agent checks whether the nominated |
| 1945 |
pair matches the default candidate pair. If there are one or more pairs that |
| 1946 |
do not match, and the peer did not indicate support for the 'ice2' ice-option, |
| 1947 |
the controlling agent <span class="bcp14">MUST</span> generate a subsequent offer in which |
| 1948 |
the connection address, port, and transport protocol in the "c=" and "m=" |
| 1949 |
lines associated with each data stream match the corresponding local |
| 1950 |
information of the nominated pair for that data stream (<a href="#sec-send-subsequent-offer-after-nom" class="xref">Section 4.4.1.2.2</a>). If the peer |
| 1951 |
did indicate support for the 'ice2' ice-option, the controlling agent does not |
| 1952 |
immediately need to generate an updated offer in order to align a connection |
| 1953 |
address, port, and protocol with a nominated pair. However, later in the |
| 1954 |
session, whenever the controlling agent does send a subsequent offer, it |
| 1955 |
<span class="bcp14">MUST</span> do the alignment as described above.<a href="#section-4.3.4-1" class="pilcrow">¶</a></p> |
| 1956 |
<p id="section-4.3.4-2"> |
| 1957 |
If there are one or more checklists with the state set to Failed, the |
| 1958 |
controlling agent <span class="bcp14">MUST</span> generate a subsequent offer in order to |
| 1959 |
remove the associated data streams by setting the port value of the data |
| 1960 |
streams to zero (<a href="#sec-send-subsequent-offer-remove" class="xref">Section 4.4.1.1.2</a>), even if the peer did indicate support for the 'ice2' |
| 1961 |
ice-option. If needed, such offer is used to align the connection address, |
| 1962 |
port, and transport protocol, as described above.<a href="#section-4.3.4-2" class="pilcrow">¶</a></p> |
| 1963 |
<p id="section-4.3.4-3"> |
| 1964 |
As described in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, once the controlling agent has nominated |
| 1965 |
a candidate pair for a checklist, the agent <span class="bcp14">MUST NOT</span> nominate another pair |
| 1966 |
for that checklist during the lifetime of the ICE session (i.e., until |
| 1967 |
ICE is restarted).<a href="#section-4.3.4-3" class="pilcrow">¶</a></p> |
| 1968 |
<p id="section-4.3.4-4"> |
| 1969 |
<span>[<a href="#RFC8863" class="xref">RFC8863</a>]</span> provides a mechanism for |
| 1970 |
allowing the ICE process to run long enough in order to find working candidate pairs, |
| 1971 |
by waiting for potential peer-reflexive candidates, even though no candidate pairs were |
| 1972 |
received from the peer or all current candidate pairs associated with a checklist have |
| 1973 |
either failed or been discarded.<a href="#section-4.3.4-4" class="pilcrow">¶</a></p> |
| 1974 |
</section> |
| 1975 |
</section> |
| 1976 |
<section id="section-4.4"> |
| 1977 |
<h3 id="name-subsequent-offer-answer-exc"> |
| 1978 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-subsequent-offer-answer-exc" class="section-name selfRef">Subsequent Offer/Answer Exchanges</a> |
| 1979 |
</h3> |
| 1980 |
<p id="section-4.4-1"> |
| 1981 |
Either agent <span class="bcp14">MAY</span> generate a subsequent offer at any time allowed by |
| 1982 |
<span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>. This section defines rules for construction of subsequent |
| 1983 |
offers and answers.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 1984 |
<p id="section-4.4-2"> |
| 1985 |
Should a subsequent offer fail, ICE processing continues as if the |
| 1986 |
subsequent offer had never been made.<a href="#section-4.4-2" class="pilcrow">¶</a></p> |
| 1987 |
<div id="sec-send-subsequent-offer"> |
| 1988 |
<section id="section-4.4.1"> |
| 1989 |
<h4 id="name-sending-subsequent-offer"> |
| 1990 |
<a href="#section-4.4.1" class="section-number selfRef">4.4.1. </a><a href="#name-sending-subsequent-offer" class="section-name selfRef">Sending Subsequent Offer</a> |
| 1991 |
</h4> |
| 1992 |
<section id="section-4.4.1.1"> |
| 1993 |
<h5 id="name-procedures-for-all-implemen"> |
| 1994 |
<a href="#section-4.4.1.1" class="section-number selfRef">4.4.1.1. </a><a href="#name-procedures-for-all-implemen" class="section-name selfRef">Procedures for All Implementations</a> |
| 1995 |
</h5> |
| 1996 |
<div id="sec-suboffer-restarts"> |
| 1997 |
<section id="section-4.4.1.1.1"> |
| 1998 |
<h6 id="name-ice-restart"> |
| 1999 |
<a href="#section-4.4.1.1.1" class="section-number selfRef">4.4.1.1.1. </a><a href="#name-ice-restart" class="section-name selfRef">ICE Restart</a> |
| 2000 |
</h6> |
| 2001 |
<p id="section-4.4.1.1.1-1"> |
| 2002 |
An agent <span class="bcp14">MAY</span> restart ICE processing for an existing data stream <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-4.4.1.1.1-1" class="pilcrow">¶</a></p> |
| 2003 |
<p id="section-4.4.1.1.1-2"> |
| 2004 |
The rules governing the ICE restart imply that setting the connection address |
| 2005 |
in the "c=" line to "0.0.0.0" (for IPv4)/ "::" (for IPv6) will cause an ICE restart. |
| 2006 |
Consequently, ICE implementations <span class="bcp14">MUST NOT</span> utilize this mechanism for call hold, |
| 2007 |
and instead <span class="bcp14">MUST</span> use "inactive" and "sendonly" as described in |
| 2008 |
<span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>.<a href="#section-4.4.1.1.1-2" class="pilcrow">¶</a></p> |
| 2009 |
<p id="section-4.4.1.1.1-3"> |
| 2010 |
To restart ICE, an agent <span class="bcp14">MUST</span> change both the "ice-pwd" and the "ice-ufrag" for |
| 2011 |
the data stream in an offer. However, it is permissible to use a session-level |
| 2012 |
attribute in one offer, but to provide the same "ice-pwd" or "ice-ufrag" as a |
| 2013 |
media-level attribute in a subsequent offer. This <span class="bcp14">MUST NOT</span> be considered |
| 2014 |
as ICE restart.<a href="#section-4.4.1.1.1-3" class="pilcrow">¶</a></p> |
| 2015 |
<p id="section-4.4.1.1.1-4"> |
| 2016 |
An agent sets the rest of the ICE-related fields in the SDP for this data stream as it |
| 2017 |
would in an initial offer of this data stream (<a href="#sec-encoding" class="xref">Section 4.2.1</a>). |
| 2018 |
Consequently, the set of candidates <span class="bcp14">MAY</span> include some, none, or all of the |
| 2019 |
previous candidates for that data stream and <span class="bcp14">MAY</span> include a totally new set of |
| 2020 |
candidates. The agent <span class="bcp14">MAY</span> modify the attribute values of the SDP "ice-options" and |
| 2021 |
SDP "ice-pacing" attributes, and it <span class="bcp14">MAY</span> change its role using the SDP "ice-lite" attribute. |
| 2022 |
The agent <span class="bcp14">MUST NOT</span> modify the SDP "ice-options", "ice-pacing", and "ice-lite" attributes in a |
| 2023 |
subsequent offer unless the offer is sent in order to request an ICE restart.<a href="#section-4.4.1.1.1-4" class="pilcrow">¶</a></p> |
| 2024 |
</section> |
| 2025 |
</div> |
| 2026 |
<div id="sec-send-subsequent-offer-remove"> |
| 2027 |
<section id="section-4.4.1.1.2"> |
| 2028 |
<h6 id="name-removing-a-data-stream"> |
| 2029 |
<a href="#section-4.4.1.1.2" class="section-number selfRef">4.4.1.1.2. </a><a href="#name-removing-a-data-stream" class="section-name selfRef">Removing a Data Stream</a> |
| 2030 |
</h6> |
| 2031 |
<p id="section-4.4.1.1.2-1"> |
| 2032 |
If an agent removes a data stream by setting its port to zero, it <span class="bcp14">MUST NOT</span> |
| 2033 |
include any "candidate" attributes for that data stream and <span class="bcp14">SHOULD NOT</span> include |
| 2034 |
any other ICE-related attributes defined in <a href="#sec-grammar" class="xref">Section 5</a> for that data stream.<a href="#section-4.4.1.1.2-1" class="pilcrow">¶</a></p> |
| 2035 |
</section> |
| 2036 |
</div> |
| 2037 |
<section id="section-4.4.1.1.3"> |
| 2038 |
<h6 id="name-adding-a-data-stream"> |
| 2039 |
<a href="#section-4.4.1.1.3" class="section-number selfRef">4.4.1.1.3. </a><a href="#name-adding-a-data-stream" class="section-name selfRef">Adding a Data Stream</a> |
| 2040 |
</h6> |
| 2041 |
<p id="section-4.4.1.1.3-1"> |
| 2042 |
If an agent wishes to add a new data stream, it sets the fields in the SDP for |
| 2043 |
this data stream as if this were an initial offer for that data stream |
| 2044 |
(<a href="#sec-encoding" class="xref">Section 4.2.1</a>). This will cause ICE processing to begin for this data stream.<a href="#section-4.4.1.1.3-1" class="pilcrow">¶</a></p> |
| 2045 |
</section> |
| 2046 |
</section> |
| 2047 |
<section id="section-4.4.1.2"> |
| 2048 |
<h5 id="name-procedures-for-full-impleme"> |
| 2049 |
<a href="#section-4.4.1.2" class="section-number selfRef">4.4.1.2. </a><a href="#name-procedures-for-full-impleme" class="section-name selfRef">Procedures for Full Implementations</a> |
| 2050 |
</h5> |
| 2051 |
<p id="section-4.4.1.2-1"> |
| 2052 |
This section describes additional procedures for full implementations, |
| 2053 |
covering existing data streams.<a href="#section-4.4.1.2-1" class="pilcrow">¶</a></p> |
| 2054 |
<section id="section-4.4.1.2.1"> |
| 2055 |
<h6 id="name-before-nomination"> |
| 2056 |
<a href="#section-4.4.1.2.1" class="section-number selfRef">4.4.1.2.1. </a><a href="#name-before-nomination" class="section-name selfRef">Before Nomination</a> |
| 2057 |
</h6> |
| 2058 |
<p id="section-4.4.1.2.1-1"> |
| 2059 |
When an offerer sends a subsequent offer; in each "m=" section for which a |
| 2060 |
candidate pair has not yet been nominated, the offer <span class="bcp14">MUST</span> include the |
| 2061 |
same set of ICE-related information that the offerer included in the |
| 2062 |
previous offer or answer. The agent <span class="bcp14">MAY</span> include additional candidates |
| 2063 |
it did not offer previously, but which it has gathered since the last |
| 2064 |
offer/answer exchange, including peer-reflexive candidates.<a href="#section-4.4.1.2.1-1" class="pilcrow">¶</a></p> |
| 2065 |
<p id="section-4.4.1.2.1-2"> |
| 2066 |
The agent <span class="bcp14">MAY</span> change the default destination for media. As with initial |
| 2067 |
offers, there <span class="bcp14">MUST</span> be a set of "candidate" attributes in the offer matching |
| 2068 |
this default destination.<a href="#section-4.4.1.2.1-2" class="pilcrow">¶</a></p> |
| 2069 |
</section> |
| 2070 |
<div id="sec-send-subsequent-offer-after-nom"> |
| 2071 |
<section id="section-4.4.1.2.2"> |
| 2072 |
<h6 id="name-after-nomination"> |
| 2073 |
<a href="#section-4.4.1.2.2" class="section-number selfRef">4.4.1.2.2. </a><a href="#name-after-nomination" class="section-name selfRef">After Nomination</a> |
| 2074 |
</h6> |
| 2075 |
<p id="section-4.4.1.2.2-1"> |
| 2076 |
Once a candidate pair has been nominated for a data stream, the connection address, |
| 2077 |
port, and transport protocol in each "c=" and "m=" line associated with that data |
| 2078 |
stream <span class="bcp14">MUST</span> match the data associated with the nominated pair for that |
| 2079 |
data stream. In addition, the offerer only includes SDP "candidate" attributes |
| 2080 |
(one per component) representing the local candidates of the nominated candidate pair. |
| 2081 |
The offerer <span class="bcp14">MUST NOT</span> include any other SDP "candidate" attributes in the |
| 2082 |
subsequent offer.<a href="#section-4.4.1.2.2-1" class="pilcrow">¶</a></p> |
| 2083 |
<p id="section-4.4.1.2.2-2"> |
| 2084 |
In addition, if the agent is controlling, it <span class="bcp14">MUST</span> include the |
| 2085 |
"remote-candidates" attribute for each data stream whose checklist |
| 2086 |
is in the Completed state. The attribute contains the remote candidates |
| 2087 |
corresponding to the nominated pair in the valid list for each |
| 2088 |
component of that data stream. It is needed to avoid a race condition |
| 2089 |
whereby the controlling agent chooses its pairs, but the updated offer |
| 2090 |
beats the connectivity checks to the controlled agent, which doesn't |
| 2091 |
even know these pairs are valid, let alone selected. See <a href="#sec-why-remote" class="xref">Appendix B</a> |
| 2092 |
for elaboration on this race condition.<a href="#section-4.4.1.2.2-2" class="pilcrow">¶</a></p> |
| 2093 |
</section> |
| 2094 |
</div> |
| 2095 |
</section> |
| 2096 |
<section id="section-4.4.1.3"> |
| 2097 |
<h5 id="name-procedures-for-lite-impleme"> |
| 2098 |
<a href="#section-4.4.1.3" class="section-number selfRef">4.4.1.3. </a><a href="#name-procedures-for-lite-impleme" class="section-name selfRef">Procedures for Lite Implementations</a> |
| 2099 |
</h5> |
| 2100 |
<p id="section-4.4.1.3-1"> |
| 2101 |
If the ICE state is Running, a lite implementation <span class="bcp14">MUST</span> include all of |
| 2102 |
its candidates for each component of each data stream in "candidate" |
| 2103 |
attributes in any subsequent offer. The candidates are formed identically |
| 2104 |
to the procedures for initial offers.<a href="#section-4.4.1.3-1" class="pilcrow">¶</a></p> |
| 2105 |
<p id="section-4.4.1.3-2"> |
| 2106 |
A lite implementation <span class="bcp14">MUST NOT</span> add additional host candidates in a |
| 2107 |
subsequent offer, and <span class="bcp14">MUST NOT</span> modify the username fragments and |
| 2108 |
passwords. If an agent needs to offer additional candidates, or |
| 2109 |
to modify the username fragments and passwords, it <span class="bcp14">MUST</span> request an |
| 2110 |
ICE restart (<a href="#sec-suboffer-restarts" class="xref">Section 4.4.1.1.1</a>) for that data stream.<a href="#section-4.4.1.3-2" class="pilcrow">¶</a></p> |
| 2111 |
<p id="section-4.4.1.3-3"> |
| 2112 |
If ICE has completed for a data stream, and if the agent is controlled, |
| 2113 |
the default destination for that data stream <span class="bcp14">MUST</span> be set to the |
| 2114 |
remote candidate of the candidate pair for that component in the valid list. |
| 2115 |
For a lite implementation, there is always just a single candidate pair in |
| 2116 |
the valid list for each component of a data stream. Additionally, the agent |
| 2117 |
<span class="bcp14">MUST</span> include a "candidate" attribute for each default destination.<a href="#section-4.4.1.3-3" class="pilcrow">¶</a></p> |
| 2118 |
<p id="section-4.4.1.3-4"> |
| 2119 |
If the ICE state is Completed, and if the agent is controlling (which only |
| 2120 |
happens when both agents are lite), the agent <span class="bcp14">MUST</span> include the |
| 2121 |
"remote-candidates" attribute for each data stream. The attribute |
| 2122 |
contains the remote candidates from the candidate pairs in the |
| 2123 |
valid list (one pair for each component of each data stream).<a href="#section-4.4.1.3-4" class="pilcrow">¶</a></p> |
| 2124 |
</section> |
| 2125 |
</section> |
| 2126 |
</div> |
| 2127 |
<div id="sec-subsequent-answer"> |
| 2128 |
<section id="section-4.4.2"> |
| 2129 |
<h4 id="name-sending-subsequent-answer"> |
| 2130 |
<a href="#section-4.4.2" class="section-number selfRef">4.4.2. </a><a href="#name-sending-subsequent-answer" class="section-name selfRef">Sending Subsequent Answer</a> |
| 2131 |
</h4> |
| 2132 |
<p id="section-4.4.2-1"> |
| 2133 |
If ICE is Completed for a data stream, and the offer for that data |
| 2134 |
stream lacked the "remote-candidates" attribute, the rules for |
| 2135 |
construction of the answer are identical to those for the offerer, |
| 2136 |
except that the answerer <span class="bcp14">MUST NOT</span> include the "remote-candidates" |
| 2137 |
attribute in the answer.<a href="#section-4.4.2-1" class="pilcrow">¶</a></p> |
| 2138 |
<p id="section-4.4.2-2"> |
| 2139 |
A controlled agent will receive an offer with the "remote-candidates" |
| 2140 |
attribute for a data stream when its peer has concluded ICE processing |
| 2141 |
for that data stream. This attribute is present in the |
| 2142 |
offer to deal with a race condition between the receipt of the offer, |
| 2143 |
and the receipt of the Binding response that tells the answerer the |
| 2144 |
candidate that will be selected by ICE. See <a href="#sec-why-remote" class="xref">Appendix B</a> for an |
| 2145 |
explanation of this race condition. Consequently, processing of an |
| 2146 |
offer with this attribute depends on the winner of the race.<a href="#section-4.4.2-2" class="pilcrow">¶</a></p> |
| 2147 |
<p id="section-4.4.2-3"> |
| 2148 |
The agent forms a candidate pair for each component of the data stream by:<a href="#section-4.4.2-3" class="pilcrow">¶</a></p> |
| 2149 |
<ul class="normal"> |
| 2150 |
<li class="normal" id="section-4.4.2-4.1"> |
| 2151 |
Setting the remote candidate equal to the offerer's default |
| 2152 |
destination for that component (i.e., the contents of the "m=" and |
| 2153 |
"c=" lines for RTP, and the "rtcp" attribute for RTCP)<a href="#section-4.4.2-4.1" class="pilcrow">¶</a> |
| 2154 |
</li> |
| 2155 |
<li class="normal" id="section-4.4.2-4.2"> |
| 2156 |
Setting the local candidate equal to the transport address for |
| 2157 |
that same component in the "remote-candidates" attribute in the |
| 2158 |
offer.<a href="#section-4.4.2-4.2" class="pilcrow">¶</a> |
| 2159 |
</li> |
| 2160 |
</ul> |
| 2161 |
<p id="section-4.4.2-5"> |
| 2162 |
The agent then sees if each of these candidate pairs is present |
| 2163 |
in the valid list. If a particular pair is not in the valid list, |
| 2164 |
the check has "lost" the race. Call such a pair a "losing pair".<a href="#section-4.4.2-5" class="pilcrow">¶</a></p> |
| 2165 |
<p id="section-4.4.2-6"> |
| 2166 |
The agent finds all the pairs in the checklist whose remote |
| 2167 |
candidates equal the remote candidate in the losing pair:<a href="#section-4.4.2-6" class="pilcrow">¶</a></p> |
| 2168 |
<ul class="normal"> |
| 2169 |
<li class="normal" id="section-4.4.2-7.1"> |
| 2170 |
If none of the pairs is In-Progress, and at least one is Failed, |
| 2171 |
it is most likely that a network failure, such as a network |
| 2172 |
partition or serious packet loss, has occurred. The agent <span class="bcp14">SHOULD</span> |
| 2173 |
generate an answer for this data stream as if the "remote- |
| 2174 |
candidates" attribute had not been present, and then restart ICE |
| 2175 |
for this stream.<a href="#section-4.4.2-7.1" class="pilcrow">¶</a> |
| 2176 |
</li> |
| 2177 |
<li class="normal" id="section-4.4.2-7.2"> |
| 2178 |
If at least one of the pairs is In-Progress, the agent <span class="bcp14">SHOULD</span> wait |
| 2179 |
for those checks to complete, and as each completes, redo the |
| 2180 |
processing in this section until there are no losing pairs.<a href="#section-4.4.2-7.2" class="pilcrow">¶</a> |
| 2181 |
</li> |
| 2182 |
</ul> |
| 2183 |
<p id="section-4.4.2-8"> |
| 2184 |
Once there are no losing pairs, the agent can generate the answer. |
| 2185 |
It <span class="bcp14">MUST</span> set the default destination for media to the candidates in |
| 2186 |
the "remote-candidates" attribute from the offer (each of which will |
| 2187 |
now be the local candidate of a candidate pair in the valid list). |
| 2188 |
It <span class="bcp14">MUST</span> include a "candidate" attribute in the answer for each |
| 2189 |
candidate in the "remote-candidates" attribute in the offer.<a href="#section-4.4.2-8" class="pilcrow">¶</a></p> |
| 2190 |
<section id="section-4.4.2.1"> |
| 2191 |
<h5 id="name-ice-restart-2"> |
| 2192 |
<a href="#section-4.4.2.1" class="section-number selfRef">4.4.2.1. </a><a href="#name-ice-restart-2" class="section-name selfRef">ICE Restart</a> |
| 2193 |
</h5> |
| 2194 |
<p id="section-4.4.2.1-1"> |
| 2195 |
If the offerer in a subsequent offer requested an ICE restart (<a href="#sec-suboffer-restarts" class="xref">Section 4.4.1.1.1</a>) |
| 2196 |
for a data stream, and if the answerer accepts the offer, the |
| 2197 |
answerer follows the procedures for generating an initial answer.<a href="#section-4.4.2.1-1" class="pilcrow">¶</a></p> |
| 2198 |
<p id="section-4.4.2.1-2"> |
| 2199 |
For a given data stream, the answerer <span class="bcp14">MAY</span> include the same |
| 2200 |
candidates that were used in the previous ICE session, but |
| 2201 |
it <span class="bcp14">MUST</span> change the SDP "ice-pwd" and "ice-ufrag" attribute |
| 2202 |
values.<a href="#section-4.4.2.1-2" class="pilcrow">¶</a></p> |
| 2203 |
<p id="section-4.4.2.1-3"> |
| 2204 |
The answerer <span class="bcp14">MAY</span> modify the attribute values of the SDP "ice-options" and |
| 2205 |
SDP "ice-pacing" attributes, and it <span class="bcp14">MAY</span> change its role using the SDP "ice-lite" attribute. |
| 2206 |
The answerer <span class="bcp14">MUST NOT</span> modify the SDP "ice-options", "ice-pacing", and "ice-lite" attributes in a |
| 2207 |
subsequent answer unless the answer is sent for an offer that was used to request an ICE restart |
| 2208 |
(<a href="#sec-suboffer-restarts" class="xref">Section 4.4.1.1.1</a>). If any of the SDP attributes have been modified in |
| 2209 |
a subsequent offer that is not used to request an ICE restart, the answerer <span class="bcp14">MUST</span> reject the |
| 2210 |
offer.<a href="#section-4.4.2.1-3" class="pilcrow">¶</a></p> |
| 2211 |
</section> |
| 2212 |
<section id="section-4.4.2.2"> |
| 2213 |
<h5 id="name-lite-implementation-specifi"> |
| 2214 |
<a href="#section-4.4.2.2" class="section-number selfRef">4.4.2.2. </a><a href="#name-lite-implementation-specifi" class="section-name selfRef">Lite Implementation Specific Procedures</a> |
| 2215 |
</h5> |
| 2216 |
<p id="section-4.4.2.2-1"> |
| 2217 |
If the received offer contains the "remote-candidates" attribute for a |
| 2218 |
data stream, the agent forms a candidate pair for each component of the |
| 2219 |
data stream by:<a href="#section-4.4.2.2-1" class="pilcrow">¶</a></p> |
| 2220 |
<ul class="normal"> |
| 2221 |
<li class="normal" id="section-4.4.2.2-2.1"> |
| 2222 |
Setting the remote candidate equal to the offerer's default destination |
| 2223 |
for that component (i.e., the contents of the "m=" and "c=" lines for RTP, |
| 2224 |
and the "rtcp" attribute for RTCP).<a href="#section-4.4.2.2-2.1" class="pilcrow">¶</a> |
| 2225 |
</li> |
| 2226 |
<li class="normal" id="section-4.4.2.2-2.2"> |
| 2227 |
Setting the local candidate equal to the transport address for that same |
| 2228 |
component in the "remote-candidates" attribute in the offer.<a href="#section-4.4.2.2-2.2" class="pilcrow">¶</a> |
| 2229 |
</li> |
| 2230 |
</ul> |
| 2231 |
<p id="section-4.4.2.2-3"> |
| 2232 |
The state of the checklist associated with that data stream is set to Completed.<a href="#section-4.4.2.2-3" class="pilcrow">¶</a></p> |
| 2233 |
<p id="section-4.4.2.2-4"> |
| 2234 |
Furthermore, if the agent believed it was controlling, but the offer contained |
| 2235 |
the "remote-candidates" attribute, both agents believe they are controlling. |
| 2236 |
In this case, both would have sent updated offers around the same time.<a href="#section-4.4.2.2-4" class="pilcrow">¶</a></p> |
| 2237 |
<p id="section-4.4.2.2-5"> |
| 2238 |
However, the signaling protocol carrying the offer/answer exchanges |
| 2239 |
will have resolved this glare condition, so that one agent is always |
| 2240 |
the 'winner' by having its offer received before its peer has sent |
| 2241 |
an offer. The winner takes the role of controlling, so that the |
| 2242 |
loser (the answerer under consideration in this section) <span class="bcp14">MUST</span> |
| 2243 |
change its role to controlled.<a href="#section-4.4.2.2-5" class="pilcrow">¶</a></p> |
| 2244 |
<p id="section-4.4.2.2-6"> |
| 2245 |
Consequently, if the agent was controlling based on the rules |
| 2246 |
in <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-8.2" class="relref">Section 8.2</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span> |
| 2247 |
and was going to send an updated offer, it no longer needs to.<a href="#section-4.4.2.2-6" class="pilcrow">¶</a></p> |
| 2248 |
<p id="section-4.4.2.2-7"> |
| 2249 |
Besides the potential role change, change in the valid list, and |
| 2250 |
state changes, the construction of the answer is performed identically |
| 2251 |
to the construction of an offer.<a href="#section-4.4.2.2-7" class="pilcrow">¶</a></p> |
| 2252 |
</section> |
| 2253 |
</section> |
| 2254 |
</div> |
| 2255 |
<section id="section-4.4.3"> |
| 2256 |
<h4 id="name-receiving-answer-for-a-subs"> |
| 2257 |
<a href="#section-4.4.3" class="section-number selfRef">4.4.3. </a><a href="#name-receiving-answer-for-a-subs" class="section-name selfRef">Receiving Answer for a Subsequent Offer</a> |
| 2258 |
</h4> |
| 2259 |
<section id="section-4.4.3.1"> |
| 2260 |
<h5 id="name-procedures-for-full-implemen"> |
| 2261 |
<a href="#section-4.4.3.1" class="section-number selfRef">4.4.3.1. </a><a href="#name-procedures-for-full-implemen" class="section-name selfRef">Procedures for Full Implementations</a> |
| 2262 |
</h5> |
| 2263 |
<p id="section-4.4.3.1-1"> |
| 2264 |
There may be certain situations where the offerer receives |
| 2265 |
an SDP answer that lacks ICE candidates although the initial answer |
| 2266 |
included them. One example of such an "unexpected" answer might |
| 2267 |
happen when an ICE-unaware Back-to-Back User Agent (B2BUA) |
| 2268 |
introduces a media server during call hold using third party |
| 2269 |
call control procedures <span>[<a href="#RFC3725" class="xref">RFC3725</a>]</span>. |
| 2270 |
Omitting further details on how this is done, this could |
| 2271 |
result in an answer that was constructed by the B2BUA |
| 2272 |
being received at the holding UA. With the B2BUA being |
| 2273 |
ICE-unaware, that answer would not include ICE candidates.<a href="#section-4.4.3.1-1" class="pilcrow">¶</a></p> |
| 2274 |
<p id="section-4.4.3.1-2"> |
| 2275 |
Receiving an answer without ICE attributes in this situation might be |
| 2276 |
unexpected, but would not necessarily impair the user experience.<a href="#section-4.4.3.1-2" class="pilcrow">¶</a></p> |
| 2277 |
<p id="section-4.4.3.1-3"> |
| 2278 |
When the offerer receives an answer indicating support for ICE, the |
| 2279 |
offer performs one of the following actions:<a href="#section-4.4.3.1-3" class="pilcrow">¶</a></p> |
| 2280 |
<ul class="normal"> |
| 2281 |
<li class="normal" id="section-4.4.3.1-4.1"> |
| 2282 |
If the offer was a restart, the agent <span class="bcp14">MUST</span> perform ICE restart |
| 2283 |
procedures as specified in <a href="#sec-restart-subsequent" class="xref">Section 4.4.3.1.1</a>.<a href="#section-4.4.3.1-4.1" class="pilcrow">¶</a> |
| 2284 |
</li> |
| 2285 |
<li class="normal" id="section-4.4.3.1-4.2"> |
| 2286 |
If the offer/answer exchange removed a data stream, or an |
| 2287 |
answer rejected an offered data stream, an agent <span class="bcp14">MUST</span> flush the |
| 2288 |
valid list for that data stream. It <span class="bcp14">MUST</span> also terminate any |
| 2289 |
STUN transactions in progress for that data stream.<a href="#section-4.4.3.1-4.2" class="pilcrow">¶</a> |
| 2290 |
</li> |
| 2291 |
<li class="normal" id="section-4.4.3.1-4.3"> |
| 2292 |
If the offer/answer exchange added a new data stream, the agent |
| 2293 |
<span class="bcp14">MUST</span> create a new checklist for it (and an empty valid list to |
| 2294 |
start of course), which in turn triggers the candidate |
| 2295 |
processing procedures <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-4.4.3.1-4.3" class="pilcrow">¶</a> |
| 2296 |
</li> |
| 2297 |
<li class="normal" id="section-4.4.3.1-4.4"> |
| 2298 |
If the checklist state associated with a data stream is Running, the agent |
| 2299 |
recomputes the checklist. If a pair on the new checklist was |
| 2300 |
also on the previous checklist, its candidate pair state is copied over. |
| 2301 |
Otherwise, its candidate pair state is set to Frozen. If none of the checklists |
| 2302 |
are active (meaning that the candidate pair states in each checklist |
| 2303 |
are Frozen), appropriate procedures in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> |
| 2304 |
are performed to move candidate pair(s) to the Waiting state to |
| 2305 |
further continue ICE processing.<a href="#section-4.4.3.1-4.4" class="pilcrow">¶</a> |
| 2306 |
</li> |
| 2307 |
<li class="normal" id="section-4.4.3.1-4.5"> |
| 2308 |
If the ICE state is Completed, and the SDP answer conforms to |
| 2309 |
<a href="#sec-subsequent-answer" class="xref">Section 4.4.2</a>, the agent <span class="bcp14">MUST</span> remain in the |
| 2310 |
Completed ICE state.<a href="#section-4.4.3.1-4.5" class="pilcrow">¶</a> |
| 2311 |
</li> |
| 2312 |
</ul> |
| 2313 |
<p id="section-4.4.3.1-5"> |
| 2314 |
However, if the ICE support is no longer indicated in the SDP answer, |
| 2315 |
the agent <span class="bcp14">MUST</span> fall back to <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> |
| 2316 |
procedures and <span class="bcp14">SHOULD NOT</span> drop the dialog because of the |
| 2317 |
missing ICE support or unexpected answer. |
| 2318 |
When the agent sends a new offer, it <span class="bcp14">MUST</span> perform an ICE restart.<a href="#section-4.4.3.1-5" class="pilcrow">¶</a></p> |
| 2319 |
<div id="sec-restart-subsequent"> |
| 2320 |
<section id="section-4.4.3.1.1"> |
| 2321 |
<h6 id="name-ice-restarts"> |
| 2322 |
<a href="#section-4.4.3.1.1" class="section-number selfRef">4.4.3.1.1. </a><a href="#name-ice-restarts" class="section-name selfRef">ICE Restarts</a> |
| 2323 |
</h6> |
| 2324 |
<p id="section-4.4.3.1.1-1"> |
| 2325 |
The agent <span class="bcp14">MUST</span> remember the nominated pair in the valid list for each |
| 2326 |
component of the data stream, called the "previous selected pair", prior |
| 2327 |
to the restart. The agent will continue to send media using this pair, |
| 2328 |
as described in <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-12" class="relref">Section 12</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span>. Once these destinations are |
| 2329 |
noted, the agent <span class="bcp14">MUST</span> flush the valid lists and checklists, and then recompute |
| 2330 |
the checklist and its states, thus triggering the candidate processing |
| 2331 |
procedures <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-4.4.3.1.1-1" class="pilcrow">¶</a></p> |
| 2332 |
</section> |
| 2333 |
</div> |
| 2334 |
</section> |
| 2335 |
<section id="section-4.4.3.2"> |
| 2336 |
<h5 id="name-procedures-for-lite-implemen"> |
| 2337 |
<a href="#section-4.4.3.2" class="section-number selfRef">4.4.3.2. </a><a href="#name-procedures-for-lite-implemen" class="section-name selfRef">Procedures for Lite Implementations</a> |
| 2338 |
</h5> |
| 2339 |
<p id="section-4.4.3.2-1"> |
| 2340 |
If ICE is restarting for a data stream, the agent <span class="bcp14">MUST</span> create a new |
| 2341 |
valid list for that data stream. It <span class="bcp14">MUST</span> remember the nominated pair in the |
| 2342 |
previous valid list for each component of the data stream, called |
| 2343 |
the "previous selected pairs", and continue to send media there as |
| 2344 |
described in <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-12" class="relref">Section 12</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span>. The state of each |
| 2345 |
checklist for each data stream <span class="bcp14">MUST</span> change to Running, and the ICE state |
| 2346 |
<span class="bcp14">MUST</span> be set to Running.<a href="#section-4.4.3.2-1" class="pilcrow">¶</a></p> |
| 2347 |
</section> |
| 2348 |
</section> |
| 2349 |
</section> |
| 2350 |
</section> |
| 2351 |
<div id="sec-grammar"> |
| 2352 |
<section id="section-5"> |
| 2353 |
<h2 id="name-grammar"> |
| 2354 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-grammar" class="section-name selfRef">Grammar</a> |
| 2355 |
</h2> |
| 2356 |
<p id="section-5-1"> |
| 2357 |
This specification defines eight new SDP attributes -- the "candidate", |
| 2358 |
"remote-candidates", "ice-lite", "ice-mismatch", "ice-ufrag", "ice-pwd", "ice-pacing", |
| 2359 |
and "ice-options" attributes.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 2360 |
<p id="section-5-2"> |
| 2361 |
This section also provides non-normative examples of the attributes defined.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 2362 |
<p id="section-5-3"> |
| 2363 |
The syntax for the attributes follow Augmented BNF as defined in <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span>.<a href="#section-5-3" class="pilcrow">¶</a></p> |
| 2364 |
<section id="section-5.1"> |
| 2365 |
<h3 id="name-candidate-attribute"> |
| 2366 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-candidate-attribute" class="section-name selfRef">"candidate" Attribute</a> |
| 2367 |
</h3> |
| 2368 |
<p id="section-5.1-1"> |
| 2369 |
The "candidate" attribute is a media-level attribute only. |
| 2370 |
It contains a transport address for a candidate that can be used for connectivity checks.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 2371 |
<div id="section-5.1-2"> |
| 2372 |
<pre class="sourcecode lang-abnf"> |
| 2373 |
candidate-attribute = "candidate" ":" foundation SP component-id SP |
| 2374 |
transport SP |
| 2375 |
priority SP |
| 2376 |
connection-address SP ;from RFC 4566 |
| 2377 |
port ;port from RFC 4566 |
| 2378 |
SP cand-type |
| 2379 |
[SP rel-addr] |
| 2380 |
[SP rel-port] |
| 2381 |
*(SP cand-extension) |
| 2382 |
|
| 2383 |
foundation = 1*32ice-char |
| 2384 |
component-id = 1*3DIGIT |
| 2385 |
transport = "UDP" / transport-extension |
| 2386 |
transport-extension = token ; from RFC 3261 |
| 2387 |
priority = 1*10DIGIT |
| 2388 |
cand-type = "typ" SP candidate-types |
| 2389 |
candidate-types = "host" / "srflx" / "prflx" / "relay" / token |
| 2390 |
rel-addr = "raddr" SP connection-address |
| 2391 |
rel-port = "rport" SP port |
| 2392 |
cand-extension = extension-att-name SP extension-att-value |
| 2393 |
extension-att-name = token |
| 2394 |
extension-att-value = *VCHAR |
| 2395 |
ice-char = ALPHA / DIGIT / "+" / "/" |
| 2396 |
</pre><a href="#section-5.1-2" class="pilcrow">¶</a> |
| 2397 |
</div> |
| 2398 |
<p id="section-5.1-3"> |
| 2399 |
This grammar encodes the primary information about a candidate: its IP address, |
| 2400 |
port and transport protocol, and its properties: the foundation, component ID, priority, |
| 2401 |
type, and related transport address:<a href="#section-5.1-3" class="pilcrow">¶</a></p> |
| 2402 |
<span class="break"></span><dl class="dlParallel" id="section-5.1-4"> |
| 2403 |
<dt id="section-5.1-4.1"><connection-address>:</dt> |
| 2404 |
<dd style="margin-left: 1.5em" id="section-5.1-4.2"> |
| 2405 |
is taken from RFC 4566 <span>[<a href="#RFC4566" class="xref">RFC4566</a>]</span>. |
| 2406 |
It is the IP address of the candidate, allowing for |
| 2407 |
IPv4 addresses, IPv6 addresses, and fully qualified domain names (FQDNs). |
| 2408 |
When parsing this field, an agent can differentiate an IPv4 address |
| 2409 |
and an IPv6 address by presence of a colon in its value - |
| 2410 |
the presence of a colon indicates IPv6. An agent generating |
| 2411 |
local candidates <span class="bcp14">MUST NOT</span> use FQDN addresses. An agent processing remote |
| 2412 |
candidates <span class="bcp14">MUST</span> ignore "candidate" lines that include candidates with |
| 2413 |
FQDNs or IP address versions that are not supported or recognized. |
| 2414 |
The procedures for generation and handling of FQDN candidates, as well as, |
| 2415 |
how agents indicate support for such procedures, need to be specified in an |
| 2416 |
extension specification.<a href="#section-5.1-4.2" class="pilcrow">¶</a> |
| 2417 |
</dd> |
| 2418 |
<dd class="break"></dd> |
| 2419 |
<dt id="section-5.1-4.3"><port>:</dt> |
| 2420 |
<dd style="margin-left: 1.5em" id="section-5.1-4.4"> |
| 2421 |
is also taken from RFC 4566 <span>[<a href="#RFC4566" class="xref">RFC4566</a>]</span>. |
| 2422 |
It is the port of the candidate.<a href="#section-5.1-4.4" class="pilcrow">¶</a> |
| 2423 |
</dd> |
| 2424 |
<dd class="break"></dd> |
| 2425 |
<dt id="section-5.1-4.5"><transport>:</dt> |
| 2426 |
<dd style="margin-left: 1.5em" id="section-5.1-4.6"> |
| 2427 |
indicates the transport protocol for the candidate. |
| 2428 |
This specification only defines UDP. However, extensibility is provided to allow for |
| 2429 |
future transport protocols to be used with ICE by extending the subregistry |
| 2430 |
"ICE Transport Protocols" under the "Interactive Connectivity Establishment (ICE)" registry.<a href="#section-5.1-4.6" class="pilcrow">¶</a> |
| 2431 |
</dd> |
| 2432 |
<dd class="break"></dd> |
| 2433 |
<dt id="section-5.1-4.7"><foundation>:</dt> |
| 2434 |
<dd style="margin-left: 1.5em" id="section-5.1-4.8"> |
| 2435 |
is composed of 1 to 32 <ice-char>s. |
| 2436 |
It is an identifier that is equivalent for two candidates that are of the same type, |
| 2437 |
share the same base, and come from the same STUN server. |
| 2438 |
The foundation is used to optimize ICE performance in the Frozen algorithm as |
| 2439 |
described in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-5.1-4.8" class="pilcrow">¶</a> |
| 2440 |
</dd> |
| 2441 |
<dd class="break"></dd> |
| 2442 |
<dt id="section-5.1-4.9"><component-id>:</dt> |
| 2443 |
<dd style="margin-left: 1.5em" id="section-5.1-4.10"> |
| 2444 |
is a positive integer between 1 and 256 (inclusive) that |
| 2445 |
identifies the specific component of the data stream for which this is a candidate. |
| 2446 |
It <span class="bcp14">MUST</span> start at 1 and <span class="bcp14">MUST</span> increment by 1 for each component of a particular candidate. |
| 2447 |
For data streams based on RTP, candidates for the actual RTP media <span class="bcp14">MUST</span> have a component |
| 2448 |
ID of 1, and candidates for RTCP <span class="bcp14">MUST</span> have a component ID of 2. |
| 2449 |
See <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-13" class="relref">Section 13</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span> for additional discussion on extending ICE to new data streams.<a href="#section-5.1-4.10" class="pilcrow">¶</a> |
| 2450 |
</dd> |
| 2451 |
<dd class="break"></dd> |
| 2452 |
<dt id="section-5.1-4.11"><priority>:</dt> |
| 2453 |
<dd style="margin-left: 1.5em" id="section-5.1-4.12"> |
| 2454 |
is a positive integer between 1 and (2**31 - 1) inclusive. The procedures |
| 2455 |
for computing a candidate's priority are described in <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-5.1.2" class="relref">Section 5.1.2</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-5.1-4.12" class="pilcrow">¶</a> |
| 2456 |
</dd> |
| 2457 |
<dd class="break"></dd> |
| 2458 |
<dt id="section-5.1-4.13"><cand-type>:</dt> |
| 2459 |
<dd style="margin-left: 1.5em" id="section-5.1-4.14"> |
| 2460 |
encodes the type of candidate. |
| 2461 |
This specification defines the values "host", "srflx", "prflx", and "relay" for host, |
| 2462 |
server-reflexive, peer-reflexive, and relayed candidates, respectively. |
| 2463 |
Specifications for new candidate types <span class="bcp14">MUST</span> define how, if at all, various steps in the ICE |
| 2464 |
processing differ from the ones defined by this specification.<a href="#section-5.1-4.14" class="pilcrow">¶</a> |
| 2465 |
</dd> |
| 2466 |
<dd class="break"></dd> |
| 2467 |
<dt id="section-5.1-4.15"><rel-addr> and <rel-port>:</dt> |
| 2468 |
<dd style="margin-left: 1.5em" id="section-5.1-4.16"> |
| 2469 |
convey transport addresses related to the candidate, useful for diagnostics |
| 2470 |
and other purposes. <rel-addr> and <rel-port> <span class="bcp14">MUST</span> be present for |
| 2471 |
server-reflexive, peer-reflexive, and relayed candidates. |
| 2472 |
If a candidate is server-reflexive or peer-reflexive, <rel-addr> and <rel-port> |
| 2473 |
are equal to the base for that server-reflexive or peer-reflexive candidate. |
| 2474 |
If the candidate is relayed, <rel-addr> and <rel-port> are equal to |
| 2475 |
the mapped address in the Allocate response that provided the client with |
| 2476 |
that relayed candidate (see <span><a href="https://www.rfc-editor.org/rfc/rfc5766#section-6.3" class="relref">Section 6.3</a> of [<a href="#RFC5766" class="xref">RFC5766</a>]</span>). |
| 2477 |
If the candidate is a host candidate, <rel-addr> and <rel-port> MUST be omitted.<a href="#section-5.1-4.16" class="pilcrow">¶</a> |
| 2478 |
</dd> |
| 2479 |
<dd class="break"></dd> |
| 2480 |
<dt id="section-5.1-4.17"></dt> |
| 2481 |
<dd style="margin-left: 1.5em" id="section-5.1-4.18"> |
| 2482 |
In some cases, e.g., for privacy reasons, an agent may not want to reveal the related |
| 2483 |
address and port. In this case the address <span class="bcp14">MUST</span> be set to "0.0.0.0" (for IPv4 candidates) |
| 2484 |
or "::" (for IPv6 candidates) and the port to "9".<a href="#section-5.1-4.18" class="pilcrow">¶</a> |
| 2485 |
</dd> |
| 2486 |
<dd class="break"></dd> |
| 2487 |
</dl> |
| 2488 |
<p id="section-5.1-5"> |
| 2489 |
The "candidate" attribute can itself be extended. The grammar allows for new name/value pairs |
| 2490 |
to be added at the end of the attribute. Such extensions <span class="bcp14">MUST</span> be made through IETF Review or |
| 2491 |
IESG Approval <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>, and the assignments <span class="bcp14">MUST</span> contain the specific extension and a |
| 2492 |
reference to the document defining the usage of the extension.<a href="#section-5.1-5" class="pilcrow">¶</a></p> |
| 2493 |
<p id="section-5.1-6"> |
| 2494 |
An implementation <span class="bcp14">MUST</span> ignore any name/value pairs it doesn't understand.<a href="#section-5.1-6" class="pilcrow">¶</a></p> |
| 2495 |
<p id="section-5.1-7"> |
| 2496 |
The following is an example SDP line for a UDP server-reflexive "candidate" attribute for |
| 2497 |
the RTP component:<a href="#section-5.1-7" class="pilcrow">¶</a></p> |
| 2498 |
<div id="section-5.1-8"> |
| 2499 |
<pre class="sourcecode lang-sdp"> |
| 2500 |
a=candidate:2 1 UDP 1694498815 192.0.2.3 45664 typ srflx raddr |
| 2501 |
203.0.113.141 rport 8998 |
| 2502 |
</pre><a href="#section-5.1-8" class="pilcrow">¶</a> |
| 2503 |
</div> |
| 2504 |
</section> |
| 2505 |
<section id="section-5.2"> |
| 2506 |
<h3 id="name-remote-candidates-attribute"> |
| 2507 |
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-remote-candidates-attribute" class="section-name selfRef">"remote-candidates" Attribute</a> |
| 2508 |
</h3> |
| 2509 |
<p id="section-5.2-1"> |
| 2510 |
The syntax of the "remote-candidates" attribute is defined using Augmented BNF |
| 2511 |
as defined in <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span>. |
| 2512 |
The "remote-candidates" attribute is a media-level attribute only.<a href="#section-5.2-1" class="pilcrow">¶</a></p> |
| 2513 |
<div id="section-5.2-2"> |
| 2514 |
<pre class="sourcecode lang-abnf"> |
| 2515 |
remote-candidate-att = "remote-candidates:" remote-candidate |
| 2516 |
0*(SP remote-candidate) |
| 2517 |
remote-candidate = component-id SP connection-address SP port |
| 2518 |
</pre><a href="#section-5.2-2" class="pilcrow">¶</a> |
| 2519 |
</div> |
| 2520 |
<p id="section-5.2-3"> |
| 2521 |
The attribute contains a connection-address and port for each component. The ordering |
| 2522 |
of components is irrelevant. However, a value <span class="bcp14">MUST</span> be present for each component of a |
| 2523 |
data stream. This attribute <span class="bcp14">MUST</span> be included in an offer by a controlling agent for |
| 2524 |
a data stream that is Completed, and <span class="bcp14">MUST NOT</span> be included in any other case.<a href="#section-5.2-3" class="pilcrow">¶</a></p> |
| 2525 |
<p id="section-5.2-4"> |
| 2526 |
The following is an example of "remote-candidates" SDP lines for the RTP and RTCP components:<a href="#section-5.2-4" class="pilcrow">¶</a></p> |
| 2527 |
<div id="section-5.2-5"> |
| 2528 |
<pre class="sourcecode lang-sdp"> |
| 2529 |
a=remote-candidates:1 192.0.2.3 45664 |
| 2530 |
a=remote-candidates:2 192.0.2.3 45665 |
| 2531 |
</pre><a href="#section-5.2-5" class="pilcrow">¶</a> |
| 2532 |
</div> |
| 2533 |
</section> |
| 2534 |
<section id="section-5.3"> |
| 2535 |
<h3 id="name-ice-lite-and-ice-mismatch-a"> |
| 2536 |
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-ice-lite-and-ice-mismatch-a" class="section-name selfRef">"ice-lite" and "ice-mismatch" Attributes</a> |
| 2537 |
</h3> |
| 2538 |
<p id="section-5.3-1"> |
| 2539 |
The syntax of the "ice-lite" and "ice-mismatch" attributes, both of which are flags, is:<a href="#section-5.3-1" class="pilcrow">¶</a></p> |
| 2540 |
<div id="section-5.3-2"> |
| 2541 |
<pre class="sourcecode lang-abnf"> |
| 2542 |
ice-lite = "ice-lite" |
| 2543 |
ice-mismatch = "ice-mismatch" |
| 2544 |
</pre><a href="#section-5.3-2" class="pilcrow">¶</a> |
| 2545 |
</div> |
| 2546 |
<p id="section-5.3-3"> |
| 2547 |
"ice-lite" is a session-level attribute only, and indicates that an agent is a |
| 2548 |
lite implementation. "ice-mismatch" is a media-level attribute and only |
| 2549 |
reported in the answer. It indicates that the offer arrived with a default |
| 2550 |
destination for a media component that didn't have a corresponding "candidate" |
| 2551 |
attribute. Inclusion of "ice-mismatch" attribute for a given data stream implies |
| 2552 |
that even though both agents support ICE, ICE procedures <span class="bcp14">MUST NOT</span> be used for this data |
| 2553 |
stream, and <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> procedures <span class="bcp14">MUST</span> be used instead.<a href="#section-5.3-3" class="pilcrow">¶</a></p> |
| 2554 |
</section> |
| 2555 |
<section id="section-5.4"> |
| 2556 |
<h3 id="name-ice-ufrag-and-ice-pwd-attri"> |
| 2557 |
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-ice-ufrag-and-ice-pwd-attri" class="section-name selfRef">"ice-ufrag" and "ice-pwd" Attributes</a> |
| 2558 |
</h3> |
| 2559 |
<p id="section-5.4-1"> |
| 2560 |
The "ice-ufrag" and "ice-pwd" attributes convey the username fragment and password used by ICE for message integrity. |
| 2561 |
Their syntax is:<a href="#section-5.4-1" class="pilcrow">¶</a></p> |
| 2562 |
<div id="section-5.4-2"> |
| 2563 |
<pre class="sourcecode lang-abnf"> |
| 2564 |
ice-pwd-att = "ice-pwd:" password |
| 2565 |
ice-ufrag-att = "ice-ufrag:" ufrag |
| 2566 |
password = 22*256ice-char |
| 2567 |
ufrag = 4*256ice-char |
| 2568 |
</pre><a href="#section-5.4-2" class="pilcrow">¶</a> |
| 2569 |
</div> |
| 2570 |
<p id="section-5.4-3"> |
| 2571 |
The "ice-pwd" and "ice-ufrag" attributes can appear at either the session-level |
| 2572 |
or media-level. When present in both, the value in the media-level takes precedence. |
| 2573 |
Thus, the value at the session-level is effectively a default that applies to all |
| 2574 |
data streams, unless overridden by a media-level value. Whether present at the session |
| 2575 |
or media-level, there <span class="bcp14">MUST</span> be an "ice-pwd" and "ice-ufrag" attribute for each data stream. |
| 2576 |
If two data streams have identical "ice-ufrag"s, they <span class="bcp14">MUST</span> have identical "ice-pwd"s.<a href="#section-5.4-3" class="pilcrow">¶</a></p> |
| 2577 |
<p id="section-5.4-4"> |
| 2578 |
The "ice-ufrag" and "ice-pwd" attributes <span class="bcp14">MUST</span> be chosen randomly at the beginning of |
| 2579 |
a session (the same applies when ICE is restarting for an agent).<a href="#section-5.4-4" class="pilcrow">¶</a></p> |
| 2580 |
<p id="section-5.4-5"><span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> requires the "ice-ufrag" attribute to contain at least 24 bits of |
| 2581 |
randomness, and the "ice-pwd" attribute to contain at least 128 bits of |
| 2582 |
randomness. This means that the "ice-ufrag" |
| 2583 |
attribute will be at least 4 characters long, and the "ice-pwd" at least 22 characters long, |
| 2584 |
since the grammar for these attributes allows for 6 bits of information per character. |
| 2585 |
The attributes <span class="bcp14">MAY</span> be longer than 4 and 22 characters, respectively, of course, up to |
| 2586 |
256 characters. The upper limit allows for buffer sizing in implementations. |
| 2587 |
Its large upper limit allows for increased amounts of randomness to be added over time. |
| 2588 |
For compatibility with the 512-character limitation for the STUN username attribute value |
| 2589 |
and for bandwidth conservation considerations, the "ice-ufrag" attribute <span class="bcp14">MUST NOT</span> be longer |
| 2590 |
than 32 characters when sending, but an implementation <span class="bcp14">MUST</span> accept up to 256 characters |
| 2591 |
when receiving.<a href="#section-5.4-5" class="pilcrow">¶</a></p> |
| 2592 |
<p id="section-5.4-6"> |
| 2593 |
The following example shows sample "ice-ufrag" and "ice-pwd" SDP lines:<a href="#section-5.4-6" class="pilcrow">¶</a></p> |
| 2594 |
<div id="section-5.4-7"> |
| 2595 |
<pre class="sourcecode lang-sdp"> |
| 2596 |
a=ice-pwd:asd88fgpdd777uzjYhagZg |
| 2597 |
a=ice-ufrag:8hhY |
| 2598 |
</pre><a href="#section-5.4-7" class="pilcrow">¶</a> |
| 2599 |
</div> |
| 2600 |
</section> |
| 2601 |
<section id="section-5.5"> |
| 2602 |
<h3 id="name-ice-pacing-attribute"> |
| 2603 |
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-ice-pacing-attribute" class="section-name selfRef">"ice-pacing" Attribute</a> |
| 2604 |
</h3> |
| 2605 |
<p id="section-5.5-1"> |
| 2606 |
The "ice-pacing" is a session-level attribute that indicates the desired connectivity-check pacing (Ta interval), in milliseconds, that the sender wishes to use. See |
| 2607 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-14.2" class="relref">Section 14.2</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span> for more information regarding selecting a pacing value. |
| 2608 |
The syntax is:<a href="#section-5.5-1" class="pilcrow">¶</a></p> |
| 2609 |
<div id="section-5.5-2"> |
| 2610 |
<pre class="sourcecode lang-abnf"> |
| 2611 |
ice-pacing-att = "ice-pacing:" pacing-value |
| 2612 |
pacing-value = 1*10DIGIT |
| 2613 |
</pre><a href="#section-5.5-2" class="pilcrow">¶</a> |
| 2614 |
</div> |
| 2615 |
<p id="section-5.5-3"> |
| 2616 |
If absent in an offer or answer, the default value of the attribute is 50 ms, |
| 2617 |
which is the recommended value specified in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>.<a href="#section-5.5-3" class="pilcrow">¶</a></p> |
| 2618 |
<p id="section-5.5-4"> |
| 2619 |
As defined in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, regardless of the Ta value |
| 2620 |
chosen for each agent, the combination of all transactions from all agents (if a given |
| 2621 |
implementation runs several concurrent agents) will not be sent more often than |
| 2622 |
once every 5 ms.<a href="#section-5.5-4" class="pilcrow">¶</a></p> |
| 2623 |
<p id="section-5.5-5"> |
| 2624 |
As defined in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, once both agents have |
| 2625 |
indicated the pacing value they want to use, both agents will use the larger of the |
| 2626 |
indicated values.<a href="#section-5.5-5" class="pilcrow">¶</a></p> |
| 2627 |
<p id="section-5.5-6"> |
| 2628 |
The following example shows an "ice-pacing" SDP line with value '50':<a href="#section-5.5-6" class="pilcrow">¶</a></p> |
| 2629 |
<div id="section-5.5-7"> |
| 2630 |
<pre class="sourcecode lang-sdp"> |
| 2631 |
a=ice-pacing:50 |
| 2632 |
</pre><a href="#section-5.5-7" class="pilcrow">¶</a> |
| 2633 |
</div> |
| 2634 |
</section> |
| 2635 |
<div id="sec-ice-options"> |
| 2636 |
<section id="section-5.6"> |
| 2637 |
<h3 id="name-ice-options-attribute"> |
| 2638 |
<a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-ice-options-attribute" class="section-name selfRef">"ice-options" Attribute</a> |
| 2639 |
</h3> |
| 2640 |
<p id="section-5.6-1"> |
| 2641 |
The "ice-options" attribute is a session-level and media-level attribute. |
| 2642 |
It contains a series of tokens that identify the options supported by the agent. |
| 2643 |
Its grammar is:<a href="#section-5.6-1" class="pilcrow">¶</a></p> |
| 2644 |
<div id="section-5.6-2"> |
| 2645 |
<pre class="sourcecode lang-abnf"> |
| 2646 |
ice-options = "ice-options:" ice-option-tag |
| 2647 |
*(SP ice-option-tag) |
| 2648 |
ice-option-tag = 1*ice-char |
| 2649 |
</pre><a href="#section-5.6-2" class="pilcrow">¶</a> |
| 2650 |
</div> |
| 2651 |
<p id="section-5.6-3"> |
| 2652 |
The existence of an "ice-options" in an offer indicates that a certain extension |
| 2653 |
is supported by the agent, and it is willing to use it if the peer agent also includes |
| 2654 |
the same extension in the answer. There might be further extension-specific |
| 2655 |
negotiation needed between the agents that determine how the extension gets used |
| 2656 |
in a given session. The details of the negotiation procedures, if present, <span class="bcp14">MUST</span> be |
| 2657 |
defined by the specification defining the extension (<a href="#sec-iana-ice-options" class="xref">Section 10.2</a>).<a href="#section-5.6-3" class="pilcrow">¶</a></p> |
| 2658 |
<p id="section-5.6-4">The following example shows an "ice-options" SDP line with 'ice2' and |
| 2659 |
'rtp+ecn' <span>[<a href="#RFC6679" class="xref">RFC6679</a>]</span> values.<a href="#section-5.6-4" class="pilcrow">¶</a></p> |
| 2660 |
<div id="section-5.6-5"> |
| 2661 |
<pre class="sourcecode lang-sdp"> |
| 2662 |
a=ice-options:ice2 rtp+ecn |
| 2663 |
</pre><a href="#section-5.6-5" class="pilcrow">¶</a> |
| 2664 |
</div> |
| 2665 |
</section> |
| 2666 |
</div> |
| 2667 |
</section> |
| 2668 |
</div> |
| 2669 |
<div id="sec-keepalive"> |
| 2670 |
<section id="section-6"> |
| 2671 |
<h2 id="name-keepalives"> |
| 2672 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-keepalives" class="section-name selfRef">Keepalives</a> |
| 2673 |
</h2> |
| 2674 |
<p id="section-6-1"> |
| 2675 |
All the ICE agents <span class="bcp14">MUST</span> follow the procedures defined in |
| 2676 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-11" class="relref">Section 11</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span> |
| 2677 |
for sending keepalives. As defined in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, |
| 2678 |
the keepalives will be sent regardless of whether the data stream is currently |
| 2679 |
inactive, sendonly, recvonly, or sendrecv, and regardless |
| 2680 |
of the presence or value of the bandwidth attribute. An agent can determine that its |
| 2681 |
peer supports ICE by the presence of "candidate" attributes for each media session.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 2682 |
</section> |
| 2683 |
</div> |
| 2684 |
<section id="section-7"> |
| 2685 |
<h2 id="name-sip-considerations"> |
| 2686 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-sip-considerations" class="section-name selfRef">SIP Considerations</a> |
| 2687 |
</h2> |
| 2688 |
<p id="section-7-1"> |
| 2689 |
Note that ICE is not intended for NAT traversal for SIP signaling, which is assumed to be |
| 2690 |
provided via another mechanism <span>[<a href="#RFC5626" class="xref">RFC5626</a>]</span>.<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 2691 |
<p id="section-7-2"> |
| 2692 |
When ICE is used with SIP, forking may result in a single offer generating a |
| 2693 |
multiplicity of answers. In that case, ICE proceeds completely in parallel and |
| 2694 |
independently for each answer, treating the combination of its offer and |
| 2695 |
each answer as an independent offer/answer exchange, with its own set of local |
| 2696 |
candidates, pairs, checklists, states, and so on.<a href="#section-7-2" class="pilcrow">¶</a></p> |
| 2697 |
<div id="sec-latency"> |
| 2698 |
<section id="section-7.1"> |
| 2699 |
<h3 id="name-latency-guidelines"> |
| 2700 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-latency-guidelines" class="section-name selfRef">Latency Guidelines</a> |
| 2701 |
</h3> |
| 2702 |
<p id="section-7.1-1"> |
| 2703 |
ICE requires a series of STUN-based connectivity checks to take place between |
| 2704 |
endpoints. These checks start from the answerer on generation of its answer, |
| 2705 |
and start from the offerer when it receives the answer. |
| 2706 |
These checks can take time to complete, and as such, the selection of |
| 2707 |
messages to use with offers and answers can affect perceived user latency. |
| 2708 |
Two latency figures are of particular interest. These are the post-pickup delay |
| 2709 |
and the post-dial delay. The post-pickup delay refers to the time between when |
| 2710 |
a user "answers the phone" and when any speech they utter can be delivered to |
| 2711 |
the caller. The post-dial delay refers to the time between when a user enters |
| 2712 |
the destination address for the user and ringback begins as a consequence of |
| 2713 |
having successfully started alerting the called user agent.<a href="#section-7.1-1" class="pilcrow">¶</a></p> |
| 2714 |
<p id="section-7.1-2"> |
| 2715 |
Two cases can be considered -- one where the offer is present in the initial |
| 2716 |
INVITE and one where it is in a response.<a href="#section-7.1-2" class="pilcrow">¶</a></p> |
| 2717 |
<section id="section-7.1.1"> |
| 2718 |
<h4 id="name-offer-in-invite"> |
| 2719 |
<a href="#section-7.1.1" class="section-number selfRef">7.1.1. </a><a href="#name-offer-in-invite" class="section-name selfRef">Offer in INVITE</a> |
| 2720 |
</h4> |
| 2721 |
<p id="section-7.1.1-1"> |
| 2722 |
To reduce post-dial delays, it is <span class="bcp14">RECOMMENDED</span> that the caller begin gathering |
| 2723 |
candidates prior to actually sending its initial INVITE, so that the candidates |
| 2724 |
can be provided in the INVITE. This can be started upon |
| 2725 |
user interface cues that a call is pending, such as activity on a keypad or |
| 2726 |
the phone going off-hook.<a href="#section-7.1.1-1" class="pilcrow">¶</a></p> |
| 2727 |
<p id="section-7.1.1-2"> |
| 2728 |
On the receipt of the offer, the answerer <span class="bcp14">SHOULD</span> generate an answer in a |
| 2729 |
provisional response as soon as it has completed gathering |
| 2730 |
the candidates. ICE requires that a provisional response with an SDP be |
| 2731 |
transmitted reliably. This can be done through the existing |
| 2732 |
Provisional Response Acknowledgment (PRACK) |
| 2733 |
mechanism <span>[<a href="#RFC3262" class="xref">RFC3262</a>]</span> or through an ICE-specific optimization, wherein, |
| 2734 |
the agent retransmits the provisional response with the exponential backoff |
| 2735 |
timers described in <span>[<a href="#RFC3262" class="xref">RFC3262</a>]</span>. Such retransmissions <span class="bcp14">MUST</span> cease on receipt |
| 2736 |
of a STUN Binding request with the transport address matching the candidate address |
| 2737 |
for one of the data streams signaled in that SDP or on transmission of the answer |
| 2738 |
in a 2xx response. If no Binding request is received prior to the last retransmit, |
| 2739 |
the agent does not consider the session terminated. For the ICE-lite peers, the |
| 2740 |
agent <span class="bcp14">MUST</span> cease retransmitting the 18x response after |
| 2741 |
sending it four times since there will be no Binding request sent, and |
| 2742 |
the number four is arbitrarily chosen to limit the number of 18x retransmits.<a href="#section-7.1.1-2" class="pilcrow">¶</a></p> |
| 2743 |
<p id="section-7.1.1-3"> |
| 2744 |
Once the answer has been sent, the agent <span class="bcp14">SHOULD</span> begin its connectivity checks. |
| 2745 |
Once candidate pairs for each component of a data stream enter the valid list, |
| 2746 |
the answerer can begin sending media on that data stream.<a href="#section-7.1.1-3" class="pilcrow">¶</a></p> |
| 2747 |
<p id="section-7.1.1-4"> |
| 2748 |
However, prior to this point, any media that needs to be sent towards the |
| 2749 |
caller (such as SIP early media <span>[<a href="#RFC3960" class="xref">RFC3960</a>]</span>) <span class="bcp14">MUST NOT</span> be transmitted. For this |
| 2750 |
reason, implementations <span class="bcp14">SHOULD</span> delay alerting the called party until candidates |
| 2751 |
for each component of each data stream have entered the valid list. |
| 2752 |
In the case of a PSTN gateway, this would mean that the setup message into the |
| 2753 |
PSTN is delayed until this point. Doing this increases the post-dial delay, but |
| 2754 |
has the effect of eliminating 'ghost rings'. |
| 2755 |
Ghost rings are cases where the called party hears the phone ring, picks up, but |
| 2756 |
hears nothing and cannot be heard. This technique works without requiring support |
| 2757 |
for, or usage of, preconditions <span>[<a href="#RFC3312" class="xref">RFC3312</a>]</span>. It also has the benefit of guaranteeing |
| 2758 |
that not a single packet of media will get clipped, so that post-pickup delay is zero. |
| 2759 |
If an agent chooses to delay local alerting in this way, it <span class="bcp14">SHOULD</span> generate a 180 |
| 2760 |
response once alerting begins.<a href="#section-7.1.1-4" class="pilcrow">¶</a></p> |
| 2761 |
</section> |
| 2762 |
<section id="section-7.1.2"> |
| 2763 |
<h4 id="name-offer-in-response"> |
| 2764 |
<a href="#section-7.1.2" class="section-number selfRef">7.1.2. </a><a href="#name-offer-in-response" class="section-name selfRef">Offer in Response</a> |
| 2765 |
</h4> |
| 2766 |
<p id="section-7.1.2-1"> |
| 2767 |
In addition to uses where the offer is in an INVITE, and the answer is in the |
| 2768 |
provisional and/or 200 OK response, ICE works with cases where the offer appears |
| 2769 |
in the response. |
| 2770 |
In such cases, which are common in third party call control <span>[<a href="#RFC3725" class="xref">RFC3725</a>]</span>, ICE |
| 2771 |
agents <span class="bcp14">SHOULD</span> generate their offers in a reliable provisional response |
| 2772 |
(which <span class="bcp14">MUST</span> utilize <span>[<a href="#RFC3262" class="xref">RFC3262</a>]</span>), and not alert the user on receipt of the INVITE. |
| 2773 |
The answer will arrive in a PRACK. |
| 2774 |
This allows for ICE processing to take place prior to alerting, so that there is no |
| 2775 |
post-pickup delay, at the expense of increased call setup delays. |
| 2776 |
Once ICE completes, the callee can alert the user and then generate a 200 OK |
| 2777 |
when they answer. |
| 2778 |
The 200 OK would contain no SDP, since the offer/answer exchange has completed.<a href="#section-7.1.2-1" class="pilcrow">¶</a></p> |
| 2779 |
<p id="section-7.1.2-2"> |
| 2780 |
Alternatively, agents <span class="bcp14">MAY</span> place the offer in a 2xx instead (in which case the |
| 2781 |
answer comes in the ACK). |
| 2782 |
When this happens, the callee will alert the user on receipt of the INVITE, |
| 2783 |
and the ICE exchanges will take place only after the user answers. |
| 2784 |
This has the effect of reducing call-setup delay, but can cause substantial |
| 2785 |
post-pickup delays and media clipping.<a href="#section-7.1.2-2" class="pilcrow">¶</a></p> |
| 2786 |
</section> |
| 2787 |
</section> |
| 2788 |
</div> |
| 2789 |
<section id="section-7.2"> |
| 2790 |
<h3 id="name-sip-option-tags-and-media-f"> |
| 2791 |
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-sip-option-tags-and-media-f" class="section-name selfRef">SIP Option Tags and Media Feature Tags</a> |
| 2792 |
</h3> |
| 2793 |
<p id="section-7.2-1"><span>[<a href="#RFC5768" class="xref">RFC5768</a>]</span> specifies a SIP option tag and media feature tag for usage with ICE. |
| 2794 |
ICE implementations using SIP <span class="bcp14">SHOULD</span> support this specification, which uses a |
| 2795 |
feature tag in registrations to facilitate interoperability through signaling |
| 2796 |
intermediaries.<a href="#section-7.2-1" class="pilcrow">¶</a></p> |
| 2797 |
</section> |
| 2798 |
<section id="section-7.3"> |
| 2799 |
<h3 id="name-interactions-with-forking"> |
| 2800 |
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-interactions-with-forking" class="section-name selfRef">Interactions with Forking</a> |
| 2801 |
</h3> |
| 2802 |
<p id="section-7.3-1"> |
| 2803 |
ICE interacts very well with forking. |
| 2804 |
Indeed, ICE fixes some of the problems associated with forking. |
| 2805 |
Without ICE, when a call forks and the caller receives multiple incoming |
| 2806 |
data streams, it cannot determine which data stream corresponds to |
| 2807 |
which callee.<a href="#section-7.3-1" class="pilcrow">¶</a></p> |
| 2808 |
<p id="section-7.3-2"> |
| 2809 |
With ICE, this problem is resolved. |
| 2810 |
The connectivity checks which occur prior to transmission of media carry |
| 2811 |
username fragments which in turn are correlated to a specific callee. |
| 2812 |
Subsequent media packets that arrive on the same candidate pair as the |
| 2813 |
connectivity check will be associated with that same callee. |
| 2814 |
Thus, the caller can perform this correlation as long as it has received an answer.<a href="#section-7.3-2" class="pilcrow">¶</a></p> |
| 2815 |
</section> |
| 2816 |
<section id="section-7.4"> |
| 2817 |
<h3 id="name-interactions-with-precondit"> |
| 2818 |
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-interactions-with-precondit" class="section-name selfRef">Interactions with Preconditions</a> |
| 2819 |
</h3> |
| 2820 |
<p id="section-7.4-1"> |
| 2821 |
Quality of Service (QoS) preconditions, which are defined in <span>[<a href="#RFC3312" class="xref">RFC3312</a>]</span> |
| 2822 |
and <span>[<a href="#RFC4032" class="xref">RFC4032</a>]</span>, apply only to the transport addresses listed as the default |
| 2823 |
targets for media in an offer/answer. |
| 2824 |
If ICE changes the transport address where media is received, this change |
| 2825 |
is reflected in an updated offer that changes the default destination for |
| 2826 |
media to match ICE's selection. As such, it appears like any other re-INVITE would, |
| 2827 |
and is fully treated in RFCs 3312 and 4032, which apply without regard to the fact |
| 2828 |
that the destination for media is changing due to ICE negotiations occurring |
| 2829 |
"in the background".<a href="#section-7.4-1" class="pilcrow">¶</a></p> |
| 2830 |
<p id="section-7.4-2"> |
| 2831 |
Indeed, an agent <span class="bcp14">SHOULD NOT</span> indicate that QoS preconditions have been met |
| 2832 |
until the checks have completed and selected the candidate pairs to be used for media.<a href="#section-7.4-2" class="pilcrow">¶</a></p> |
| 2833 |
<p id="section-7.4-3"> |
| 2834 |
ICE also has interactions with connectivity preconditions <span>[<a href="#RFC5898" class="xref">RFC5898</a>]</span>. |
| 2835 |
Those interactions are described there. |
| 2836 |
Note that the procedures described in <a href="#sec-latency" class="xref">Section 7.1</a> describe their own type of "preconditions", albeit with less functionality than those provided by the explicit preconditions in <span>[<a href="#RFC5898" class="xref">RFC5898</a>]</span>.<a href="#section-7.4-3" class="pilcrow">¶</a></p> |
| 2837 |
</section> |
| 2838 |
<section id="section-7.5"> |
| 2839 |
<h3 id="name-interactions-with-third-par"> |
| 2840 |
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-interactions-with-third-par" class="section-name selfRef">Interactions with Third Party Call Control</a> |
| 2841 |
</h3> |
| 2842 |
<p id="section-7.5-1"> |
| 2843 |
ICE works with Flows I, III, and IV as described in <span>[<a href="#RFC3725" class="xref">RFC3725</a>]</span>. |
| 2844 |
Flow I works without the controller supporting or being aware of ICE. |
| 2845 |
Flow IV will work as long as the controller passes along the ICE attributes without alteration. |
| 2846 |
Flow II is fundamentally incompatible with ICE; each agent will believe itself to be the answerer and thus never generate a re-INVITE.<a href="#section-7.5-1" class="pilcrow">¶</a></p> |
| 2847 |
<p id="section-7.5-2"> |
| 2848 |
The flows for continued operation, as described in <span><a href="https://www.rfc-editor.org/rfc/rfc3725#section-7" class="relref">Section 7</a> of [<a href="#RFC3725" class="xref">RFC3725</a>]</span>, |
| 2849 |
require additional behavior of ICE implementations to support. |
| 2850 |
In particular, if an agent receives a mid-dialog re-INVITE that contains no offer, it <span class="bcp14">MUST</span> restart ICE for each data stream and go through the process of gathering new candidates. |
| 2851 |
Furthermore, that list of candidates <span class="bcp14">SHOULD</span> include the ones currently being used for media.<a href="#section-7.5-2" class="pilcrow">¶</a></p> |
| 2852 |
</section> |
| 2853 |
</section> |
| 2854 |
<div id="sec-alg-sip"> |
| 2855 |
<section id="section-8"> |
| 2856 |
<h2 id="name-interactions-with-applicati"> |
| 2857 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-interactions-with-applicati" class="section-name selfRef">Interactions with Application Layer Gateways and SIP</a> |
| 2858 |
</h2> |
| 2859 |
<p id="section-8-1"> |
| 2860 |
Application Layer Gateways (ALGs) are functions present in a Network Address Translation (NAT) |
| 2861 |
device that inspect the contents of packets and modify them, in order to facilitate NAT traversal |
| 2862 |
for application protocols. Session Border Controllers (SBCs) are close cousins of ALGs, but are |
| 2863 |
less transparent since they actually exist as application-layer SIP intermediaries. ICE has |
| 2864 |
interactions with SBCs and ALGs.<a href="#section-8-1" class="pilcrow">¶</a></p> |
| 2865 |
<p id="section-8-2"> |
| 2866 |
If an ALG is SIP aware but not ICE aware, ICE will work through it as long as the ALG correctly |
| 2867 |
modifies the SDP. A correct ALG implementation behaves as follows:<a href="#section-8-2" class="pilcrow">¶</a></p> |
| 2868 |
<ul class="normal"> |
| 2869 |
<li class="normal" id="section-8-3.1"> |
| 2870 |
The ALG does not modify the "m=" and "c=" lines or the "rtcp" attribute if they contain |
| 2871 |
external addresses.<a href="#section-8-3.1" class="pilcrow">¶</a> |
| 2872 |
</li> |
| 2873 |
<li class="normal" id="section-8-3.2"> |
| 2874 |
<p id="section-8-3.2.1"> |
| 2875 |
If the "m=" and "c=" lines contain internal addresses, the modification depends on the state of the ALG:<a href="#section-8-3.2.1" class="pilcrow">¶</a></p> |
| 2876 |
<ul class="normal"> |
| 2877 |
<li class="normal" id="section-8-3.2.2.1"> |
| 2878 |
If the ALG already has a binding established that maps an external port to an internal connection |
| 2879 |
address and port matching the values in the "m=" and "c=" lines or "rtcp" attribute, the ALG uses that |
| 2880 |
binding instead of creating a new one.<a href="#section-8-3.2.2.1" class="pilcrow">¶</a> |
| 2881 |
</li> |
| 2882 |
<li class="normal" id="section-8-3.2.2.2"> |
| 2883 |
If the ALG does not already have a binding, it creates a new one and modifies the SDP, rewriting |
| 2884 |
the "m=" and "c=" lines and "rtcp" attribute.<a href="#section-8-3.2.2.2" class="pilcrow">¶</a> |
| 2885 |
</li> |
| 2886 |
</ul> |
| 2887 |
</li> |
| 2888 |
</ul> |
| 2889 |
<p id="section-8-4"> |
| 2890 |
Unfortunately, many ALGs are known to work poorly in these corner cases. |
| 2891 |
ICE does not try to work around broken ALGs, as this is outside the scope of its functionality. |
| 2892 |
ICE can help diagnose these conditions, which often show up as a mismatch between the set of candidates and |
| 2893 |
the "m=" and "c=" lines and "rtcp" attributes. The "ice-mismatch" attribute is used for this purpose.<a href="#section-8-4" class="pilcrow">¶</a></p> |
| 2894 |
<p id="section-8-5"> |
| 2895 |
ICE works best through ALGs when the signaling is run over TLS. |
| 2896 |
This prevents the ALG from manipulating the SDP messages and interfering with ICE operation. |
| 2897 |
Implementations that are expected to be deployed behind ALGs <span class="bcp14">SHOULD</span> provide for TLS transport of the SDP.<a href="#section-8-5" class="pilcrow">¶</a></p> |
| 2898 |
<p id="section-8-6"> |
| 2899 |
If an SBC is SIP aware but not ICE aware, the result depends on the behavior of the SBC. |
| 2900 |
If it is acting as a proper Back-to-Back User Agent (B2BUA), the SBC will remove any SDP attributes |
| 2901 |
it doesn't understand, including the ICE attributes. Consequently, the call will appear to both |
| 2902 |
endpoints as if the other side doesn't support ICE. This will result in ICE being disabled, and |
| 2903 |
media flowing through the SBC, if the SBC has requested it. If, however, the SBC passes the ICE attributes |
| 2904 |
without modification, yet modifies the default destination for media (contained in the "m=" and "c=" lines |
| 2905 |
and "rtcp" attribute), this will be detected as an ICE mismatch, and ICE processing is aborted for the call. |
| 2906 |
It is outside of the scope of ICE for it to act as a tool for "working around" SBCs. |
| 2907 |
If one is present, ICE will not be used and the SBC techniques take precedence.<a href="#section-8-6" class="pilcrow">¶</a></p> |
| 2908 |
</section> |
| 2909 |
</div> |
| 2910 |
<section id="section-9"> |
| 2911 |
<h2 id="name-security-considerations"> |
| 2912 |
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2913 |
</h2> |
| 2914 |
<p id="section-9-1"> |
| 2915 |
The generic ICE security considerations are defined in <span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span>, and the |
| 2916 |
generic SDP offer/answer security considerations are defined in <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>. These |
| 2917 |
security considerations also apply to implementations of this document.<a href="#section-9-1" class="pilcrow">¶</a></p> |
| 2918 |
<section id="section-9.1"> |
| 2919 |
<h3 id="name-ip-address-privacy"> |
| 2920 |
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-ip-address-privacy" class="section-name selfRef">IP Address Privacy</a> |
| 2921 |
</h3> |
| 2922 |
<p id="section-9.1-1"> |
| 2923 |
In some cases, e.g., for privacy reasons, an agent may not want to reveal the related |
| 2924 |
address and port. In this case the address <span class="bcp14">MUST</span> be set to "0.0.0.0" (for IPv4 candidates) |
| 2925 |
or "::" (for IPv6 candidates) and the port to '9'.<a href="#section-9.1-1" class="pilcrow">¶</a></p> |
| 2926 |
</section> |
| 2927 |
<section id="section-9.2"> |
| 2928 |
<h3 id="name-attacks-on-the-offer-answer"> |
| 2929 |
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-attacks-on-the-offer-answer" class="section-name selfRef">Attacks on the Offer/Answer Exchanges</a> |
| 2930 |
</h3> |
| 2931 |
<p id="section-9.2-1"> |
| 2932 |
An attacker that can modify or disrupt the offer/answer exchanges themselves can readily |
| 2933 |
launch a variety of attacks with ICE. They could direct media to a target of a DoS attack, |
| 2934 |
they could insert themselves into the data stream, and so on. These are similar to the general |
| 2935 |
security considerations for offer/answer exchanges, and the security considerations in |
| 2936 |
<span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span> apply. These require techniques for message integrity and encryption |
| 2937 |
for offers and answers, which are satisfied by the TLS mechanism <span>[<a href="#RFC3261" class="xref">RFC3261</a>]</span> when |
| 2938 |
SIP is used. As such, the usage of TLS with ICE is <span class="bcp14">RECOMMENDED</span>.<a href="#section-9.2-1" class="pilcrow">¶</a></p> |
| 2939 |
</section> |
| 2940 |
<div id="sec-voice-hammer"> |
| 2941 |
<section id="section-9.3"> |
| 2942 |
<h3 id="name-the-voice-hammer-attack"> |
| 2943 |
<a href="#section-9.3" class="section-number selfRef">9.3. </a><a href="#name-the-voice-hammer-attack" class="section-name selfRef">The Voice Hammer Attack</a> |
| 2944 |
</h3> |
| 2945 |
<p id="section-9.3-1"> |
| 2946 |
The voice hammer attack is an amplification attack, and can be triggered even if the attacker |
| 2947 |
is an authenticated and valid participant in a session. |
| 2948 |
In this attack, the attacker initiates sessions to other agents, and maliciously includes |
| 2949 |
the connection address and port of a DoS target as the destination for media traffic |
| 2950 |
signaled in the SDP. This causes substantial amplification; a single offer/answer exchange |
| 2951 |
can create a continuing flood of media packets, possibly at high rates (consider video sources). |
| 2952 |
The use of ICE can help to prevent against this attack.<a href="#section-9.3-1" class="pilcrow">¶</a></p> |
| 2953 |
<p id="section-9.3-2"> |
| 2954 |
Specifically, if ICE is used, the agent receiving the malicious SDP will first perform connectivity |
| 2955 |
checks to the target of media before sending media there. If this target is a third-party host, the |
| 2956 |
checks will not succeed, and media is never sent. The ICE extension defined in <span>[<a href="#RFC7675" class="xref">RFC7675</a>]</span> |
| 2957 |
can be used to further protect against voice hammer attacks.<a href="#section-9.3-2" class="pilcrow">¶</a></p> |
| 2958 |
<p id="section-9.3-3"> |
| 2959 |
Unfortunately, ICE doesn't help if it's not used, in which case an attacker could simply |
| 2960 |
send the offer without the ICE parameters. However, in environments where the set of clients is known, |
| 2961 |
and is limited to ones that support ICE, the server can reject any offers or answers that don't |
| 2962 |
indicate ICE support.<a href="#section-9.3-3" class="pilcrow">¶</a></p> |
| 2963 |
<p id="section-9.3-4"> |
| 2964 |
SIP user agents (UA) <span>[<a href="#RFC3261" class="xref">RFC3261</a>]</span> that are not willing to receive non-ICE answers <span class="bcp14">MUST</span> include |
| 2965 |
an "ice" option tag <span>[<a href="#RFC5768" class="xref">RFC5768</a>]</span> in the SIP Require header field in their offer. UAs that |
| 2966 |
reject non-ICE offers will generally use a 421 response code, together with an option tag "ice" in the |
| 2967 |
Require header field in the response.<a href="#section-9.3-4" class="pilcrow">¶</a></p> |
| 2968 |
</section> |
| 2969 |
</div> |
| 2970 |
</section> |
| 2971 |
<div id="iana"> |
| 2972 |
<section id="section-10"> |
| 2973 |
<h2 id="name-iana-considerations"> |
| 2974 |
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2975 |
</h2> |
| 2976 |
<section id="section-10.1"> |
| 2977 |
<h3 id="name-sdp-attributes"> |
| 2978 |
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-sdp-attributes" class="section-name selfRef">SDP Attributes</a> |
| 2979 |
</h3> |
| 2980 |
<p id="section-10.1-1"> |
| 2981 |
The original ICE specification defined seven new SDP attributes per the procedures of |
| 2982 |
<span><a href="https://www.rfc-editor.org/rfc/rfc4566#section-8.2.4" class="relref">Section 8.2.4</a> of [<a href="#RFC4566" class="xref">RFC4566</a>]</span>. |
| 2983 |
The registration information from the original specification |
| 2984 |
is included here with modifications to include Mux Category <span>[<a href="#RFC8859" class="xref">RFC8859</a>]</span> |
| 2985 |
and also defines a new SDP attribute "ice-pacing".<a href="#section-10.1-1" class="pilcrow">¶</a></p> |
| 2986 |
<section id="section-10.1.1"> |
| 2987 |
<h4 id="name-candidate-attribute-2"> |
| 2988 |
<a href="#section-10.1.1" class="section-number selfRef">10.1.1. </a><a href="#name-candidate-attribute-2" class="section-name selfRef">"candidate" Attribute</a> |
| 2989 |
</h4> |
| 2990 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.1-1"> |
| 2991 |
<dt id="section-10.1.1-1.1">Attribute Name:</dt> |
| 2992 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.2"> |
| 2993 |
candidate<a href="#section-10.1.1-1.2" class="pilcrow">¶</a> |
| 2994 |
</dd> |
| 2995 |
<dd class="break"></dd> |
| 2996 |
<dt id="section-10.1.1-1.3">Type of Attribute:</dt> |
| 2997 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.4"> |
| 2998 |
media-level<a href="#section-10.1.1-1.4" class="pilcrow">¶</a> |
| 2999 |
</dd> |
| 3000 |
<dd class="break"></dd> |
| 3001 |
<dt id="section-10.1.1-1.5">Subject to charset:</dt> |
| 3002 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.6"> |
| 3003 |
No<a href="#section-10.1.1-1.6" class="pilcrow">¶</a> |
| 3004 |
</dd> |
| 3005 |
<dd class="break"></dd> |
| 3006 |
<dt id="section-10.1.1-1.7">Purpose:</dt> |
| 3007 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.8"> |
| 3008 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3009 |
and provides one of many possible candidate addresses for communication. |
| 3010 |
These addresses are validated with an end-to-end connectivity check using Session |
| 3011 |
Traversal Utilities for NAT (STUN).<a href="#section-10.1.1-1.8" class="pilcrow">¶</a> |
| 3012 |
</dd> |
| 3013 |
<dd class="break"></dd> |
| 3014 |
<dt id="section-10.1.1-1.9">Appropriate Values:</dt> |
| 3015 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.10"> |
| 3016 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.1-1.10" class="pilcrow">¶</a> |
| 3017 |
</dd> |
| 3018 |
<dd class="break"></dd> |
| 3019 |
<dt id="section-10.1.1-1.11">Contact Name:</dt> |
| 3020 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.12"> |
| 3021 |
IESG<a href="#section-10.1.1-1.12" class="pilcrow">¶</a> |
| 3022 |
</dd> |
| 3023 |
<dd class="break"></dd> |
| 3024 |
<dt id="section-10.1.1-1.13">Contact Email:</dt> |
| 3025 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.14"> |
| 3026 |
[email protected]<a href="#section-10.1.1-1.14" class="pilcrow">¶</a> |
| 3027 |
</dd> |
| 3028 |
<dd class="break"></dd> |
| 3029 |
<dt id="section-10.1.1-1.15">Reference:</dt> |
| 3030 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.16"> |
| 3031 |
RFC 8839<a href="#section-10.1.1-1.16" class="pilcrow">¶</a> |
| 3032 |
</dd> |
| 3033 |
<dd class="break"></dd> |
| 3034 |
<dt id="section-10.1.1-1.17">Mux Category:</dt> |
| 3035 |
<dd style="margin-left: 1.5em" id="section-10.1.1-1.18"> |
| 3036 |
TRANSPORT<a href="#section-10.1.1-1.18" class="pilcrow">¶</a> |
| 3037 |
</dd> |
| 3038 |
<dd class="break"></dd> |
| 3039 |
</dl> |
| 3040 |
</section> |
| 3041 |
<section id="section-10.1.2"> |
| 3042 |
<h4 id="name-remote-candidates-attribute-2"> |
| 3043 |
<a href="#section-10.1.2" class="section-number selfRef">10.1.2. </a><a href="#name-remote-candidates-attribute-2" class="section-name selfRef">"remote-candidates" Attribute</a> |
| 3044 |
</h4> |
| 3045 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.2-1"> |
| 3046 |
<dt id="section-10.1.2-1.1">Attribute Name:</dt> |
| 3047 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.2"> |
| 3048 |
remote-candidates<a href="#section-10.1.2-1.2" class="pilcrow">¶</a> |
| 3049 |
</dd> |
| 3050 |
<dd class="break"></dd> |
| 3051 |
<dt id="section-10.1.2-1.3">Type of Attribute:</dt> |
| 3052 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.4"> |
| 3053 |
media-level<a href="#section-10.1.2-1.4" class="pilcrow">¶</a> |
| 3054 |
</dd> |
| 3055 |
<dd class="break"></dd> |
| 3056 |
<dt id="section-10.1.2-1.5">Subject to charset:</dt> |
| 3057 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.6"> |
| 3058 |
No<a href="#section-10.1.2-1.6" class="pilcrow">¶</a> |
| 3059 |
</dd> |
| 3060 |
<dd class="break"></dd> |
| 3061 |
<dt id="section-10.1.2-1.7">Purpose:</dt> |
| 3062 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.8"> |
| 3063 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3064 |
and provides the identity of the remote candidates that the offerer wishes the answerer |
| 3065 |
to use in its answer.<a href="#section-10.1.2-1.8" class="pilcrow">¶</a> |
| 3066 |
</dd> |
| 3067 |
<dd class="break"></dd> |
| 3068 |
<dt id="section-10.1.2-1.9">Appropriate Values:</dt> |
| 3069 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.10"> |
| 3070 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.2-1.10" class="pilcrow">¶</a> |
| 3071 |
</dd> |
| 3072 |
<dd class="break"></dd> |
| 3073 |
<dt id="section-10.1.2-1.11">Contact Name:</dt> |
| 3074 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.12"> |
| 3075 |
IESG<a href="#section-10.1.2-1.12" class="pilcrow">¶</a> |
| 3076 |
</dd> |
| 3077 |
<dd class="break"></dd> |
| 3078 |
<dt id="section-10.1.2-1.13">Contact Email:</dt> |
| 3079 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.14"> |
| 3080 |
[email protected]<a href="#section-10.1.2-1.14" class="pilcrow">¶</a> |
| 3081 |
</dd> |
| 3082 |
<dd class="break"></dd> |
| 3083 |
<dt id="section-10.1.2-1.15">Reference:</dt> |
| 3084 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.16"> |
| 3085 |
RFC 8839<a href="#section-10.1.2-1.16" class="pilcrow">¶</a> |
| 3086 |
</dd> |
| 3087 |
<dd class="break"></dd> |
| 3088 |
<dt id="section-10.1.2-1.17">Mux Category:</dt> |
| 3089 |
<dd style="margin-left: 1.5em" id="section-10.1.2-1.18"> |
| 3090 |
TRANSPORT<a href="#section-10.1.2-1.18" class="pilcrow">¶</a> |
| 3091 |
</dd> |
| 3092 |
<dd class="break"></dd> |
| 3093 |
</dl> |
| 3094 |
</section> |
| 3095 |
<section id="section-10.1.3"> |
| 3096 |
<h4 id="name-ice-lite-attribute"> |
| 3097 |
<a href="#section-10.1.3" class="section-number selfRef">10.1.3. </a><a href="#name-ice-lite-attribute" class="section-name selfRef">"ice-lite" Attribute</a> |
| 3098 |
</h4> |
| 3099 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.3-1"> |
| 3100 |
<dt id="section-10.1.3-1.1">Attribute Name:</dt> |
| 3101 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.2"> |
| 3102 |
ice-lite<a href="#section-10.1.3-1.2" class="pilcrow">¶</a> |
| 3103 |
</dd> |
| 3104 |
<dd class="break"></dd> |
| 3105 |
<dt id="section-10.1.3-1.3">Type of Attribute:</dt> |
| 3106 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.4"> |
| 3107 |
session-level<a href="#section-10.1.3-1.4" class="pilcrow">¶</a> |
| 3108 |
</dd> |
| 3109 |
<dd class="break"></dd> |
| 3110 |
<dt id="section-10.1.3-1.5">Subject to charset:</dt> |
| 3111 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.6"> |
| 3112 |
No<a href="#section-10.1.3-1.6" class="pilcrow">¶</a> |
| 3113 |
</dd> |
| 3114 |
<dd class="break"></dd> |
| 3115 |
<dt id="section-10.1.3-1.7">Purpose:</dt> |
| 3116 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.8"> |
| 3117 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3118 |
and indicates that an agent has the minimum functionality required to support ICE |
| 3119 |
inter-operation with a peer that has a full implementation.<a href="#section-10.1.3-1.8" class="pilcrow">¶</a> |
| 3120 |
</dd> |
| 3121 |
<dd class="break"></dd> |
| 3122 |
<dt id="section-10.1.3-1.9">Appropriate Values:</dt> |
| 3123 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.10"> |
| 3124 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.3-1.10" class="pilcrow">¶</a> |
| 3125 |
</dd> |
| 3126 |
<dd class="break"></dd> |
| 3127 |
<dt id="section-10.1.3-1.11">Contact Name:</dt> |
| 3128 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.12"> |
| 3129 |
IESG<a href="#section-10.1.3-1.12" class="pilcrow">¶</a> |
| 3130 |
</dd> |
| 3131 |
<dd class="break"></dd> |
| 3132 |
<dt id="section-10.1.3-1.13">Contact Email:</dt> |
| 3133 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.14"> |
| 3134 |
[email protected]<a href="#section-10.1.3-1.14" class="pilcrow">¶</a> |
| 3135 |
</dd> |
| 3136 |
<dd class="break"></dd> |
| 3137 |
<dt id="section-10.1.3-1.15">Reference:</dt> |
| 3138 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.16"> |
| 3139 |
RFC 8839<a href="#section-10.1.3-1.16" class="pilcrow">¶</a> |
| 3140 |
</dd> |
| 3141 |
<dd class="break"></dd> |
| 3142 |
<dt id="section-10.1.3-1.17">Mux Category:</dt> |
| 3143 |
<dd style="margin-left: 1.5em" id="section-10.1.3-1.18"> |
| 3144 |
NORMAL<a href="#section-10.1.3-1.18" class="pilcrow">¶</a> |
| 3145 |
</dd> |
| 3146 |
<dd class="break"></dd> |
| 3147 |
</dl> |
| 3148 |
</section> |
| 3149 |
<section id="section-10.1.4"> |
| 3150 |
<h4 id="name-ice-mismatch-attribute"> |
| 3151 |
<a href="#section-10.1.4" class="section-number selfRef">10.1.4. </a><a href="#name-ice-mismatch-attribute" class="section-name selfRef">"ice-mismatch" Attribute</a> |
| 3152 |
</h4> |
| 3153 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.4-1"> |
| 3154 |
<dt id="section-10.1.4-1.1">Attribute Name:</dt> |
| 3155 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.2"> |
| 3156 |
ice-mismatch<a href="#section-10.1.4-1.2" class="pilcrow">¶</a> |
| 3157 |
</dd> |
| 3158 |
<dd class="break"></dd> |
| 3159 |
<dt id="section-10.1.4-1.3">Type of Attribute:</dt> |
| 3160 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.4"> |
| 3161 |
media-level<a href="#section-10.1.4-1.4" class="pilcrow">¶</a> |
| 3162 |
</dd> |
| 3163 |
<dd class="break"></dd> |
| 3164 |
<dt id="section-10.1.4-1.5">Subject to charset:</dt> |
| 3165 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.6"> |
| 3166 |
No<a href="#section-10.1.4-1.6" class="pilcrow">¶</a> |
| 3167 |
</dd> |
| 3168 |
<dd class="break"></dd> |
| 3169 |
<dt id="section-10.1.4-1.7">Purpose:</dt> |
| 3170 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.8"> |
| 3171 |
This attribute is used with Interactive Connectivity Establishment (ICE), and indicates that an agent is ICE capable, but did not proceed with ICE due to a mismatch of candidates with the default destination for media signaled in the SDP.<a href="#section-10.1.4-1.8" class="pilcrow">¶</a> |
| 3172 |
</dd> |
| 3173 |
<dd class="break"></dd> |
| 3174 |
<dt id="section-10.1.4-1.9">Appropriate Values:</dt> |
| 3175 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.10"> |
| 3176 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.4-1.10" class="pilcrow">¶</a> |
| 3177 |
</dd> |
| 3178 |
<dd class="break"></dd> |
| 3179 |
<dt id="section-10.1.4-1.11">Contact Name:</dt> |
| 3180 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.12"> |
| 3181 |
IESG<a href="#section-10.1.4-1.12" class="pilcrow">¶</a> |
| 3182 |
</dd> |
| 3183 |
<dd class="break"></dd> |
| 3184 |
<dt id="section-10.1.4-1.13">Contact e-mail:</dt> |
| 3185 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.14"> |
| 3186 |
[email protected]<a href="#section-10.1.4-1.14" class="pilcrow">¶</a> |
| 3187 |
</dd> |
| 3188 |
<dd class="break"></dd> |
| 3189 |
<dt id="section-10.1.4-1.15">Reference:</dt> |
| 3190 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.16"> |
| 3191 |
RFC 8839<a href="#section-10.1.4-1.16" class="pilcrow">¶</a> |
| 3192 |
</dd> |
| 3193 |
<dd class="break"></dd> |
| 3194 |
<dt id="section-10.1.4-1.17">Mux Category:</dt> |
| 3195 |
<dd style="margin-left: 1.5em" id="section-10.1.4-1.18"> |
| 3196 |
NORMAL<a href="#section-10.1.4-1.18" class="pilcrow">¶</a> |
| 3197 |
</dd> |
| 3198 |
<dd class="break"></dd> |
| 3199 |
</dl> |
| 3200 |
</section> |
| 3201 |
<section id="section-10.1.5"> |
| 3202 |
<h4 id="name-ice-pwd-attribute"> |
| 3203 |
<a href="#section-10.1.5" class="section-number selfRef">10.1.5. </a><a href="#name-ice-pwd-attribute" class="section-name selfRef">"ice-pwd" Attribute</a> |
| 3204 |
</h4> |
| 3205 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.5-1"> |
| 3206 |
<dt id="section-10.1.5-1.1">Attribute Name:</dt> |
| 3207 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.2"> |
| 3208 |
ice-pwd<a href="#section-10.1.5-1.2" class="pilcrow">¶</a> |
| 3209 |
</dd> |
| 3210 |
<dd class="break"></dd> |
| 3211 |
<dt id="section-10.1.5-1.3">Type of Attribute:</dt> |
| 3212 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.4"> |
| 3213 |
session- or media-level<a href="#section-10.1.5-1.4" class="pilcrow">¶</a> |
| 3214 |
</dd> |
| 3215 |
<dd class="break"></dd> |
| 3216 |
<dt id="section-10.1.5-1.5">Subject to charset:</dt> |
| 3217 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.6"> |
| 3218 |
No<a href="#section-10.1.5-1.6" class="pilcrow">¶</a> |
| 3219 |
</dd> |
| 3220 |
<dd class="break"></dd> |
| 3221 |
<dt id="section-10.1.5-1.7">Purpose:</dt> |
| 3222 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.8"> |
| 3223 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3224 |
and provides the password used to protect STUN connectivity checks.<a href="#section-10.1.5-1.8" class="pilcrow">¶</a> |
| 3225 |
</dd> |
| 3226 |
<dd class="break"></dd> |
| 3227 |
<dt id="section-10.1.5-1.9">Appropriate Values:</dt> |
| 3228 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.10"> |
| 3229 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.5-1.10" class="pilcrow">¶</a> |
| 3230 |
</dd> |
| 3231 |
<dd class="break"></dd> |
| 3232 |
<dt id="section-10.1.5-1.11">Contact Name:</dt> |
| 3233 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.12"> |
| 3234 |
IESG<a href="#section-10.1.5-1.12" class="pilcrow">¶</a> |
| 3235 |
</dd> |
| 3236 |
<dd class="break"></dd> |
| 3237 |
<dt id="section-10.1.5-1.13">Contact e-mail:</dt> |
| 3238 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.14"> |
| 3239 |
[email protected]<a href="#section-10.1.5-1.14" class="pilcrow">¶</a> |
| 3240 |
</dd> |
| 3241 |
<dd class="break"></dd> |
| 3242 |
<dt id="section-10.1.5-1.15">Reference:</dt> |
| 3243 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.16"> |
| 3244 |
RFC 8839<a href="#section-10.1.5-1.16" class="pilcrow">¶</a> |
| 3245 |
</dd> |
| 3246 |
<dd class="break"></dd> |
| 3247 |
<dt id="section-10.1.5-1.17">Mux Category:</dt> |
| 3248 |
<dd style="margin-left: 1.5em" id="section-10.1.5-1.18"> |
| 3249 |
TRANSPORT<a href="#section-10.1.5-1.18" class="pilcrow">¶</a> |
| 3250 |
</dd> |
| 3251 |
<dd class="break"></dd> |
| 3252 |
</dl> |
| 3253 |
</section> |
| 3254 |
<section id="section-10.1.6"> |
| 3255 |
<h4 id="name-ice-ufrag-attribute"> |
| 3256 |
<a href="#section-10.1.6" class="section-number selfRef">10.1.6. </a><a href="#name-ice-ufrag-attribute" class="section-name selfRef">"ice-ufrag" Attribute</a> |
| 3257 |
</h4> |
| 3258 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.6-1"> |
| 3259 |
<dt id="section-10.1.6-1.1">Attribute Name:</dt> |
| 3260 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.2"> |
| 3261 |
ice-ufrag<a href="#section-10.1.6-1.2" class="pilcrow">¶</a> |
| 3262 |
</dd> |
| 3263 |
<dd class="break"></dd> |
| 3264 |
<dt id="section-10.1.6-1.3">Type of Attribute:</dt> |
| 3265 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.4"> |
| 3266 |
session- or media-level<a href="#section-10.1.6-1.4" class="pilcrow">¶</a> |
| 3267 |
</dd> |
| 3268 |
<dd class="break"></dd> |
| 3269 |
<dt id="section-10.1.6-1.5">Subject to charset:</dt> |
| 3270 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.6"> |
| 3271 |
No<a href="#section-10.1.6-1.6" class="pilcrow">¶</a> |
| 3272 |
</dd> |
| 3273 |
<dd class="break"></dd> |
| 3274 |
<dt id="section-10.1.6-1.7">Purpose:</dt> |
| 3275 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.8"> |
| 3276 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3277 |
and provides the fragments used to construct the username in STUN connectivity checks.<a href="#section-10.1.6-1.8" class="pilcrow">¶</a> |
| 3278 |
</dd> |
| 3279 |
<dd class="break"></dd> |
| 3280 |
<dt id="section-10.1.6-1.9">Appropriate Values:</dt> |
| 3281 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.10"> |
| 3282 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.6-1.10" class="pilcrow">¶</a> |
| 3283 |
</dd> |
| 3284 |
<dd class="break"></dd> |
| 3285 |
<dt id="section-10.1.6-1.11">Contact Name:</dt> |
| 3286 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.12"> |
| 3287 |
IESG<a href="#section-10.1.6-1.12" class="pilcrow">¶</a> |
| 3288 |
</dd> |
| 3289 |
<dd class="break"></dd> |
| 3290 |
<dt id="section-10.1.6-1.13">Contact e-mail:</dt> |
| 3291 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.14"> |
| 3292 |
[email protected]<a href="#section-10.1.6-1.14" class="pilcrow">¶</a> |
| 3293 |
</dd> |
| 3294 |
<dd class="break"></dd> |
| 3295 |
<dt id="section-10.1.6-1.15">Reference:</dt> |
| 3296 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.16"> |
| 3297 |
RFC 8839<a href="#section-10.1.6-1.16" class="pilcrow">¶</a> |
| 3298 |
</dd> |
| 3299 |
<dd class="break"></dd> |
| 3300 |
<dt id="section-10.1.6-1.17">Mux Category:</dt> |
| 3301 |
<dd style="margin-left: 1.5em" id="section-10.1.6-1.18"> |
| 3302 |
TRANSPORT<a href="#section-10.1.6-1.18" class="pilcrow">¶</a> |
| 3303 |
</dd> |
| 3304 |
<dd class="break"></dd> |
| 3305 |
</dl> |
| 3306 |
</section> |
| 3307 |
<section id="section-10.1.7"> |
| 3308 |
<h4 id="name-ice-options-attribute-2"> |
| 3309 |
<a href="#section-10.1.7" class="section-number selfRef">10.1.7. </a><a href="#name-ice-options-attribute-2" class="section-name selfRef">"ice-options" Attribute</a> |
| 3310 |
</h4> |
| 3311 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.7-1"> |
| 3312 |
<dt id="section-10.1.7-1.1">Attribute Name:</dt> |
| 3313 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.2"> |
| 3314 |
ice-options<a href="#section-10.1.7-1.2" class="pilcrow">¶</a> |
| 3315 |
</dd> |
| 3316 |
<dd class="break"></dd> |
| 3317 |
<dt id="section-10.1.7-1.3">Long Form:</dt> |
| 3318 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.4"> |
| 3319 |
ice-options<a href="#section-10.1.7-1.4" class="pilcrow">¶</a> |
| 3320 |
</dd> |
| 3321 |
<dd class="break"></dd> |
| 3322 |
<dt id="section-10.1.7-1.5">Type of Attribute:</dt> |
| 3323 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.6"> |
| 3324 |
session-level<a href="#section-10.1.7-1.6" class="pilcrow">¶</a> |
| 3325 |
</dd> |
| 3326 |
<dd class="break"></dd> |
| 3327 |
<dt id="section-10.1.7-1.7">Subject to charset:</dt> |
| 3328 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.8"> |
| 3329 |
No<a href="#section-10.1.7-1.8" class="pilcrow">¶</a> |
| 3330 |
</dd> |
| 3331 |
<dd class="break"></dd> |
| 3332 |
<dt id="section-10.1.7-1.9">Purpose:</dt> |
| 3333 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.10"> |
| 3334 |
This attribute is used with Interactive Connectivity Establishment (ICE), |
| 3335 |
and indicates the ICE options or extensions used by the agent.<a href="#section-10.1.7-1.10" class="pilcrow">¶</a> |
| 3336 |
</dd> |
| 3337 |
<dd class="break"></dd> |
| 3338 |
<dt id="section-10.1.7-1.11">Appropriate Values:</dt> |
| 3339 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.12"> |
| 3340 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.7-1.12" class="pilcrow">¶</a> |
| 3341 |
</dd> |
| 3342 |
<dd class="break"></dd> |
| 3343 |
<dt id="section-10.1.7-1.13">Contact Name:</dt> |
| 3344 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.14"> |
| 3345 |
IESG<a href="#section-10.1.7-1.14" class="pilcrow">¶</a> |
| 3346 |
</dd> |
| 3347 |
<dd class="break"></dd> |
| 3348 |
<dt id="section-10.1.7-1.15">Contact e-mail:</dt> |
| 3349 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.16"> |
| 3350 |
[email protected]<a href="#section-10.1.7-1.16" class="pilcrow">¶</a> |
| 3351 |
</dd> |
| 3352 |
<dd class="break"></dd> |
| 3353 |
<dt id="section-10.1.7-1.17">Reference:</dt> |
| 3354 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.18"> |
| 3355 |
RFC 8839<a href="#section-10.1.7-1.18" class="pilcrow">¶</a> |
| 3356 |
</dd> |
| 3357 |
<dd class="break"></dd> |
| 3358 |
<dt id="section-10.1.7-1.19">Mux Category:</dt> |
| 3359 |
<dd style="margin-left: 1.5em" id="section-10.1.7-1.20"> |
| 3360 |
NORMAL<a href="#section-10.1.7-1.20" class="pilcrow">¶</a> |
| 3361 |
</dd> |
| 3362 |
<dd class="break"></dd> |
| 3363 |
</dl> |
| 3364 |
</section> |
| 3365 |
<section id="section-10.1.8"> |
| 3366 |
<h4 id="name-ice-pacing-attribute-2"> |
| 3367 |
<a href="#section-10.1.8" class="section-number selfRef">10.1.8. </a><a href="#name-ice-pacing-attribute-2" class="section-name selfRef">"ice-pacing" Attribute</a> |
| 3368 |
</h4> |
| 3369 |
<p id="section-10.1.8-1"> |
| 3370 |
This specification also defines a new SDP attribute, "ice-pacing", according |
| 3371 |
to the following data:<a href="#section-10.1.8-1" class="pilcrow">¶</a></p> |
| 3372 |
<span class="break"></span><dl class="dlParallel" id="section-10.1.8-2"> |
| 3373 |
<dt id="section-10.1.8-2.1">Attribute Name:</dt> |
| 3374 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.2"> |
| 3375 |
ice-pacing<a href="#section-10.1.8-2.2" class="pilcrow">¶</a> |
| 3376 |
</dd> |
| 3377 |
<dd class="break"></dd> |
| 3378 |
<dt id="section-10.1.8-2.3">Type of Attribute:</dt> |
| 3379 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.4"> |
| 3380 |
session-level<a href="#section-10.1.8-2.4" class="pilcrow">¶</a> |
| 3381 |
</dd> |
| 3382 |
<dd class="break"></dd> |
| 3383 |
<dt id="section-10.1.8-2.5">Subject to charset:</dt> |
| 3384 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.6"> |
| 3385 |
No<a href="#section-10.1.8-2.6" class="pilcrow">¶</a> |
| 3386 |
</dd> |
| 3387 |
<dd class="break"></dd> |
| 3388 |
<dt id="section-10.1.8-2.7">Purpose:</dt> |
| 3389 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.8"> |
| 3390 |
This attribute is used with Interactive Connectivity Establishment (ICE) |
| 3391 |
to indicate desired connectivity check pacing values.<a href="#section-10.1.8-2.8" class="pilcrow">¶</a> |
| 3392 |
</dd> |
| 3393 |
<dd class="break"></dd> |
| 3394 |
<dt id="section-10.1.8-2.9">Appropriate Values:</dt> |
| 3395 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.10"> |
| 3396 |
See <a href="#sec-grammar" class="xref">Section 5</a> of RFC 8839.<a href="#section-10.1.8-2.10" class="pilcrow">¶</a> |
| 3397 |
</dd> |
| 3398 |
<dd class="break"></dd> |
| 3399 |
<dt id="section-10.1.8-2.11">Contact Name:</dt> |
| 3400 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.12"> |
| 3401 |
IESG<a href="#section-10.1.8-2.12" class="pilcrow">¶</a> |
| 3402 |
</dd> |
| 3403 |
<dd class="break"></dd> |
| 3404 |
<dt id="section-10.1.8-2.13">Contact e-mail:</dt> |
| 3405 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.14"> |
| 3406 |
[email protected]<a href="#section-10.1.8-2.14" class="pilcrow">¶</a> |
| 3407 |
</dd> |
| 3408 |
<dd class="break"></dd> |
| 3409 |
<dt id="section-10.1.8-2.15">Reference:</dt> |
| 3410 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.16"> |
| 3411 |
RFC 8839<a href="#section-10.1.8-2.16" class="pilcrow">¶</a> |
| 3412 |
</dd> |
| 3413 |
<dd class="break"></dd> |
| 3414 |
<dt id="section-10.1.8-2.17">Mux Category:</dt> |
| 3415 |
<dd style="margin-left: 1.5em" id="section-10.1.8-2.18"> |
| 3416 |
NORMAL<a href="#section-10.1.8-2.18" class="pilcrow">¶</a> |
| 3417 |
</dd> |
| 3418 |
<dd class="break"></dd> |
| 3419 |
</dl> |
| 3420 |
</section> |
| 3421 |
</section> |
| 3422 |
<div id="sec-iana-ice-options"> |
| 3423 |
<section id="section-10.2"> |
| 3424 |
<h3 id="name-interactive-connectivity-es"> |
| 3425 |
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-interactive-connectivity-es" class="section-name selfRef">Interactive Connectivity Establishment (ICE) Options Registry</a> |
| 3426 |
</h3> |
| 3427 |
<p id="section-10.2-1"> |
| 3428 |
IANA maintains a registry for "ice-options" identifiers under the Specification |
| 3429 |
Required policy as defined in "Guidelines for Writing an IANA Considerations |
| 3430 |
Section in RFCs" <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-10.2-1" class="pilcrow">¶</a></p> |
| 3431 |
<p id="section-10.2-2"> |
| 3432 |
ICE options are of unlimited length according to the syntax in |
| 3433 |
<a href="#sec-ice-options" class="xref">Section 5.6</a>; however, they are <span class="bcp14">RECOMMENDED</span> to be no longer |
| 3434 |
than 20 characters. This is to reduce message sizes and allow for |
| 3435 |
efficient parsing. ICE options are defined at the session level.<a href="#section-10.2-2" class="pilcrow">¶</a></p> |
| 3436 |
<p id="section-10.2-3"> |
| 3437 |
A registration request <span class="bcp14">MUST</span> include the following information:<a href="#section-10.2-3" class="pilcrow">¶</a></p> |
| 3438 |
<ul class="normal"> |
| 3439 |
<li class="normal" id="section-10.2-4.1"> |
| 3440 |
The ICE option identifier to be registered<a href="#section-10.2-4.1" class="pilcrow">¶</a> |
| 3441 |
</li> |
| 3442 |
<li class="normal" id="section-10.2-4.2"> |
| 3443 |
Name and email address of organization or individuals having change control<a href="#section-10.2-4.2" class="pilcrow">¶</a> |
| 3444 |
</li> |
| 3445 |
<li class="normal" id="section-10.2-4.3"> |
| 3446 |
Short description of the ICE extension to which the option relates<a href="#section-10.2-4.3" class="pilcrow">¶</a> |
| 3447 |
</li> |
| 3448 |
<li class="normal" id="section-10.2-4.4"> |
| 3449 |
Reference(s) to the specification defining the ICE option and the related extensions<a href="#section-10.2-4.4" class="pilcrow">¶</a> |
| 3450 |
</li> |
| 3451 |
</ul> |
| 3452 |
</section> |
| 3453 |
</div> |
| 3454 |
<div id="sec-iana-cand-ext"> |
| 3455 |
<section id="section-10.3"> |
| 3456 |
<h3 id="name-candidate-attribute-extensi"> |
| 3457 |
<a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-candidate-attribute-extensi" class="section-name selfRef">Candidate Attribute Extension Subregistry Establishment</a> |
| 3458 |
</h3> |
| 3459 |
<p id="section-10.3-1"> |
| 3460 |
This section creates a new subregistry, "Candidate Attribute |
| 3461 |
Extensions", under the SDP Parameters |
| 3462 |
registry: <span><a href="http://www.iana.org/assignments/sdp-parameters">http://www.iana.org/assignments/sdp-parameters</a></span>.<a href="#section-10.3-1" class="pilcrow">¶</a></p> |
| 3463 |
<p id="section-10.3-2"> |
| 3464 |
The purpose of the subregistry is to register SDP "candidate" attribute extensions.<a href="#section-10.3-2" class="pilcrow">¶</a></p> |
| 3465 |
<p id="section-10.3-3"> |
| 3466 |
When a "candidate" extension is registered in the subregistry, it needs to meet the "Specification Required" |
| 3467 |
policies defined in <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-10.3-3" class="pilcrow">¶</a></p> |
| 3468 |
<p id="section-10.3-4"> |
| 3469 |
"candidate" attribute extensions <span class="bcp14">MUST</span> follow the 'cand-extension' syntax. The attribute extension |
| 3470 |
name <span class="bcp14">MUST</span> follow the 'extension-att-name' syntax, and the attribute extension value <span class="bcp14">MUST</span> follow the |
| 3471 |
'extension-att-value' syntax.<a href="#section-10.3-4" class="pilcrow">¶</a></p> |
| 3472 |
<p id="section-10.3-5"> |
| 3473 |
A registration request <span class="bcp14">MUST</span> include the following information:<a href="#section-10.3-5" class="pilcrow">¶</a></p> |
| 3474 |
<ul class="normal"> |
| 3475 |
<li class="normal" id="section-10.3-6.1"> |
| 3476 |
The name of the attribute extension.<a href="#section-10.3-6.1" class="pilcrow">¶</a> |
| 3477 |
</li> |
| 3478 |
<li class="normal" id="section-10.3-6.2"> |
| 3479 |
Name and email address of organization or individuals having change control<a href="#section-10.3-6.2" class="pilcrow">¶</a> |
| 3480 |
</li> |
| 3481 |
<li class="normal" id="section-10.3-6.3"> |
| 3482 |
A short description of the attribute extension.<a href="#section-10.3-6.3" class="pilcrow">¶</a> |
| 3483 |
</li> |
| 3484 |
<li class="normal" id="section-10.3-6.4"> |
| 3485 |
A reference to a specification that describes the semantics, usage and possible |
| 3486 |
values of the attribute extension.<a href="#section-10.3-6.4" class="pilcrow">¶</a> |
| 3487 |
</li> |
| 3488 |
</ul> |
| 3489 |
</section> |
| 3490 |
</div> |
| 3491 |
</section> |
| 3492 |
</div> |
| 3493 |
<div id="sec.5245"> |
| 3494 |
<section id="section-11"> |
| 3495 |
<h2 id="name-changes-from-rfc-5245"> |
| 3496 |
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-changes-from-rfc-5245" class="section-name selfRef">Changes from RFC 5245</a> |
| 3497 |
</h2> |
| 3498 |
<p id="section-11-1"> |
| 3499 |
<span>[<a href="#RFC8445" class="xref">RFC8445</a>]</span> describes the changes made to the |
| 3500 |
common SIP procedures, including removal of aggressive nomination, |
| 3501 |
modifying the procedures for calculating candidate pair states, |
| 3502 |
scheduling connectivity checks, and the calculation of timer values.<a href="#section-11-1" class="pilcrow">¶</a></p> |
| 3503 |
<p id="section-11-2"> |
| 3504 |
This document defines the following SDP offer/answer specific changes:<a href="#section-11-2" class="pilcrow">¶</a></p> |
| 3505 |
<ul class="normal"> |
| 3506 |
<li class="normal" id="section-11-3.1">SDP offer/answer realization and usage of 'ice2' option.<a href="#section-11-3.1" class="pilcrow">¶</a> |
| 3507 |
</li> |
| 3508 |
<li class="normal" id="section-11-3.2">Definition and usage of SDP "ice-pacing" attribute.<a href="#section-11-3.2" class="pilcrow">¶</a> |
| 3509 |
</li> |
| 3510 |
<li class="normal" id="section-11-3.3">Explicit text that an ICE agent must not generate candidates with FQDNs, and |
| 3511 |
must discard such candidates if received from the peer agent.<a href="#section-11-3.3" class="pilcrow">¶</a> |
| 3512 |
</li> |
| 3513 |
<li class="normal" id="section-11-3.4">Relax requirement to include SDP "rtcp" attribute.<a href="#section-11-3.4" class="pilcrow">¶</a> |
| 3514 |
</li> |
| 3515 |
<li class="normal" id="section-11-3.5">Generic clarifications of SDP offer/answer procedures.<a href="#section-11-3.5" class="pilcrow">¶</a> |
| 3516 |
</li> |
| 3517 |
<li class="normal" id="section-11-3.6">ICE mismatch is now optional, and an agent has an option to not |
| 3518 |
trigger mismatch and instead treat the default candidate as an |
| 3519 |
additional candidate.<a href="#section-11-3.6" class="pilcrow">¶</a> |
| 3520 |
</li> |
| 3521 |
<li class="normal" id="section-11-3.7">FQDNs and "0.0.0.0"/"::" IP addresses with port "9" default |
| 3522 |
candidates do not trigger ICE mismatch.<a href="#section-11-3.7" class="pilcrow">¶</a> |
| 3523 |
</li> |
| 3524 |
</ul> |
| 3525 |
</section> |
| 3526 |
</div> |
| 3527 |
<section id="section-12"> |
| 3528 |
<h2 id="name-references"> |
| 3529 |
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 3530 |
</h2> |
| 3531 |
<section id="section-12.1"> |
| 3532 |
<h3 id="name-normative-references"> |
| 3533 |
<a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 3534 |
</h3> |
| 3535 |
<dl class="references"> |
| 3536 |
<dt id="RFC2119">[RFC2119]</dt> |
| 3537 |
<dd> |
| 3538 |
<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> |
| 3539 |
<dd class="break"></dd> |
| 3540 |
<dt id="RFC3261">[RFC3261]</dt> |
| 3541 |
<dd> |
| 3542 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Schulzrinne, H.</span><span class="refAuthor">, Camarillo, G.</span><span class="refAuthor">, Johnston, A.</span><span class="refAuthor">, Peterson, J.</span><span class="refAuthor">, Sparks, R.</span><span class="refAuthor">, Handley, M.</span><span class="refAuthor">, and E. Schooler</span>, <span class="refTitle">"SIP: Session Initiation Protocol"</span>, <span class="seriesInfo">RFC 3261</span>, <span class="seriesInfo">DOI 10.17487/RFC3261</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3261">https://www.rfc-editor.org/info/rfc3261</a>></span>. </dd> |
| 3543 |
<dd class="break"></dd> |
| 3544 |
<dt id="RFC3262">[RFC3262]</dt> |
| 3545 |
<dd> |
| 3546 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor"> and H. Schulzrinne</span>, <span class="refTitle">"Reliability of Provisional Responses in Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 3262</span>, <span class="seriesInfo">DOI 10.17487/RFC3262</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3262">https://www.rfc-editor.org/info/rfc3262</a>></span>. </dd> |
| 3547 |
<dd class="break"></dd> |
| 3548 |
<dt id="RFC3264">[RFC3264]</dt> |
| 3549 |
<dd> |
| 3550 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor"> and H. Schulzrinne</span>, <span class="refTitle">"An Offer/Answer Model with Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 3264</span>, <span class="seriesInfo">DOI 10.17487/RFC3264</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3264">https://www.rfc-editor.org/info/rfc3264</a>></span>. </dd> |
| 3551 |
<dd class="break"></dd> |
| 3552 |
<dt id="RFC3312">[RFC3312]</dt> |
| 3553 |
<dd> |
| 3554 |
<span class="refAuthor">Camarillo, G., Ed.</span><span class="refAuthor">, Marshall, W., Ed.</span><span class="refAuthor">, and J. Rosenberg</span>, <span class="refTitle">"Integration of Resource Management and Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 3312</span>, <span class="seriesInfo">DOI 10.17487/RFC3312</span>, <time datetime="2002-10" class="refDate">October 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3312">https://www.rfc-editor.org/info/rfc3312</a>></span>. </dd> |
| 3555 |
<dd class="break"></dd> |
| 3556 |
<dt id="RFC3556">[RFC3556]</dt> |
| 3557 |
<dd> |
| 3558 |
<span class="refAuthor">Casner, S.</span>, <span class="refTitle">"Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth"</span>, <span class="seriesInfo">RFC 3556</span>, <span class="seriesInfo">DOI 10.17487/RFC3556</span>, <time datetime="2003-07" class="refDate">July 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3556">https://www.rfc-editor.org/info/rfc3556</a>></span>. </dd> |
| 3559 |
<dd class="break"></dd> |
| 3560 |
<dt id="RFC3605">[RFC3605]</dt> |
| 3561 |
<dd> |
| 3562 |
<span class="refAuthor">Huitema, C.</span>, <span class="refTitle">"Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)"</span>, <span class="seriesInfo">RFC 3605</span>, <span class="seriesInfo">DOI 10.17487/RFC3605</span>, <time datetime="2003-10" class="refDate">October 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3605">https://www.rfc-editor.org/info/rfc3605</a>></span>. </dd> |
| 3563 |
<dd class="break"></dd> |
| 3564 |
<dt id="RFC4032">[RFC4032]</dt> |
| 3565 |
<dd> |
| 3566 |
<span class="refAuthor">Camarillo, G.</span><span class="refAuthor"> and P. Kyzivat</span>, <span class="refTitle">"Update to the Session Initiation Protocol (SIP) Preconditions Framework"</span>, <span class="seriesInfo">RFC 4032</span>, <span class="seriesInfo">DOI 10.17487/RFC4032</span>, <time datetime="2005-03" class="refDate">March 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4032">https://www.rfc-editor.org/info/rfc4032</a>></span>. </dd> |
| 3567 |
<dd class="break"></dd> |
| 3568 |
<dt id="RFC4566">[RFC4566]</dt> |
| 3569 |
<dd> |
| 3570 |
<span class="refAuthor">Handley, M.</span><span class="refAuthor">, Jacobson, V.</span><span class="refAuthor">, and C. Perkins</span>, <span class="refTitle">"SDP: Session Description Protocol"</span>, <span class="seriesInfo">RFC 4566</span>, <span class="seriesInfo">DOI 10.17487/RFC4566</span>, <time datetime="2006-07" class="refDate">July 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4566">https://www.rfc-editor.org/info/rfc4566</a>></span>. </dd> |
| 3571 |
<dd class="break"></dd> |
| 3572 |
<dt id="RFC5234">[RFC5234]</dt> |
| 3573 |
<dd> |
| 3574 |
<span class="refAuthor">Crocker, D., Ed.</span><span class="refAuthor"> and P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>></span>. </dd> |
| 3575 |
<dd class="break"></dd> |
| 3576 |
<dt id="RFC5389">[RFC5389]</dt> |
| 3577 |
<dd> |
| 3578 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Mahy, R.</span><span class="refAuthor">, Matthews, P.</span><span class="refAuthor">, and D. Wing</span>, <span class="refTitle">"Session Traversal Utilities for NAT (STUN)"</span>, <span class="seriesInfo">RFC 5389</span>, <span class="seriesInfo">DOI 10.17487/RFC5389</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5389">https://www.rfc-editor.org/info/rfc5389</a>></span>. </dd> |
| 3579 |
<dd class="break"></dd> |
| 3580 |
<dt id="RFC5766">[RFC5766]</dt> |
| 3581 |
<dd> |
| 3582 |
<span class="refAuthor">Mahy, R.</span><span class="refAuthor">, Matthews, P.</span><span class="refAuthor">, and J. Rosenberg</span>, <span class="refTitle">"Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)"</span>, <span class="seriesInfo">RFC 5766</span>, <span class="seriesInfo">DOI 10.17487/RFC5766</span>, <time datetime="2010-04" class="refDate">April 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5766">https://www.rfc-editor.org/info/rfc5766</a>></span>. </dd> |
| 3583 |
<dd class="break"></dd> |
| 3584 |
<dt id="RFC5768">[RFC5768]</dt> |
| 3585 |
<dd> |
| 3586 |
<span class="refAuthor">Rosenberg, J.</span>, <span class="refTitle">"Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 5768</span>, <span class="seriesInfo">DOI 10.17487/RFC5768</span>, <time datetime="2010-04" class="refDate">April 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5768">https://www.rfc-editor.org/info/rfc5768</a>></span>. </dd> |
| 3587 |
<dd class="break"></dd> |
| 3588 |
<dt id="RFC6336">[RFC6336]</dt> |
| 3589 |
<dd> |
| 3590 |
<span class="refAuthor">Westerlund, M.</span><span class="refAuthor"> and C. Perkins</span>, <span class="refTitle">"IANA Registry for Interactive Connectivity Establishment (ICE) Options"</span>, <span class="seriesInfo">RFC 6336</span>, <span class="seriesInfo">DOI 10.17487/RFC6336</span>, <time datetime="2011-07" class="refDate">July 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6336">https://www.rfc-editor.org/info/rfc6336</a>></span>. </dd> |
| 3591 |
<dd class="break"></dd> |
| 3592 |
<dt id="RFC8174">[RFC8174]</dt> |
| 3593 |
<dd> |
| 3594 |
<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> |
| 3595 |
<dd class="break"></dd> |
| 3596 |
<dt id="RFC8445">[RFC8445]</dt> |
| 3597 |
<dd> |
| 3598 |
<span class="refAuthor">Keranen, A.</span><span class="refAuthor">, Holmberg, C.</span><span class="refAuthor">, and J. Rosenberg</span>, <span class="refTitle">"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal"</span>, <span class="seriesInfo">RFC 8445</span>, <span class="seriesInfo">DOI 10.17487/RFC8445</span>, <time datetime="2018-07" class="refDate">July 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8445">https://www.rfc-editor.org/info/rfc8445</a>></span>. </dd> |
| 3599 |
<dd class="break"></dd> |
| 3600 |
</dl> |
| 3601 |
</section> |
| 3602 |
<section id="section-12.2"> |
| 3603 |
<h3 id="name-informative-references"> |
| 3604 |
<a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 3605 |
</h3> |
| 3606 |
<dl class="references"> |
| 3607 |
<dt id="RFC3725">[RFC3725]</dt> |
| 3608 |
<dd> |
| 3609 |
<span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Peterson, J.</span><span class="refAuthor">, Schulzrinne, H.</span><span class="refAuthor">, and G. Camarillo</span>, <span class="refTitle">"Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">BCP 85</span>, <span class="seriesInfo">RFC 3725</span>, <span class="seriesInfo">DOI 10.17487/RFC3725</span>, <time datetime="2004-04" class="refDate">April 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3725">https://www.rfc-editor.org/info/rfc3725</a>></span>. </dd> |
| 3610 |
<dd class="break"></dd> |
| 3611 |
<dt id="RFC3960">[RFC3960]</dt> |
| 3612 |
<dd> |
| 3613 |
<span class="refAuthor">Camarillo, G.</span><span class="refAuthor"> and H. Schulzrinne</span>, <span class="refTitle">"Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 3960</span>, <span class="seriesInfo">DOI 10.17487/RFC3960</span>, <time datetime="2004-12" class="refDate">December 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3960">https://www.rfc-editor.org/info/rfc3960</a>></span>. </dd> |
| 3614 |
<dd class="break"></dd> |
| 3615 |
<dt id="RFC5245">[RFC5245]</dt> |
| 3616 |
<dd> |
| 3617 |
<span class="refAuthor">Rosenberg, J.</span>, <span class="refTitle">"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols"</span>, <span class="seriesInfo">RFC 5245</span>, <span class="seriesInfo">DOI 10.17487/RFC5245</span>, <time datetime="2010-04" class="refDate">April 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5245">https://www.rfc-editor.org/info/rfc5245</a>></span>. </dd> |
| 3618 |
<dd class="break"></dd> |
| 3619 |
<dt id="RFC5626">[RFC5626]</dt> |
| 3620 |
<dd> |
| 3621 |
<span class="refAuthor">Jennings, C., Ed.</span><span class="refAuthor">, Mahy, R., Ed.</span><span class="refAuthor">, and F. Audet, Ed.</span>, <span class="refTitle">"Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 5626</span>, <span class="seriesInfo">DOI 10.17487/RFC5626</span>, <time datetime="2009-10" class="refDate">October 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5626">https://www.rfc-editor.org/info/rfc5626</a>></span>. </dd> |
| 3622 |
<dd class="break"></dd> |
| 3623 |
<dt id="RFC5898">[RFC5898]</dt> |
| 3624 |
<dd> |
| 3625 |
<span class="refAuthor">Andreasen, F.</span><span class="refAuthor">, Camarillo, G.</span><span class="refAuthor">, Oran, D.</span><span class="refAuthor">, and D. Wing</span>, <span class="refTitle">"Connectivity Preconditions for Session Description Protocol (SDP) Media Streams"</span>, <span class="seriesInfo">RFC 5898</span>, <span class="seriesInfo">DOI 10.17487/RFC5898</span>, <time datetime="2010-07" class="refDate">July 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5898">https://www.rfc-editor.org/info/rfc5898</a>></span>. </dd> |
| 3626 |
<dd class="break"></dd> |
| 3627 |
<dt id="RFC6679">[RFC6679]</dt> |
| 3628 |
<dd> |
| 3629 |
<span class="refAuthor">Westerlund, M.</span><span class="refAuthor">, Johansson, I.</span><span class="refAuthor">, Perkins, C.</span><span class="refAuthor">, O'Hanlon, P.</span><span class="refAuthor">, and K. Carlberg</span>, <span class="refTitle">"Explicit Congestion Notification (ECN) for RTP over UDP"</span>, <span class="seriesInfo">RFC 6679</span>, <span class="seriesInfo">DOI 10.17487/RFC6679</span>, <time datetime="2012-08" class="refDate">August 2012</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6679">https://www.rfc-editor.org/info/rfc6679</a>></span>. </dd> |
| 3630 |
<dd class="break"></dd> |
| 3631 |
<dt id="RFC7675">[RFC7675]</dt> |
| 3632 |
<dd> |
| 3633 |
<span class="refAuthor">Perumal, M.</span><span class="refAuthor">, Wing, D.</span><span class="refAuthor">, Ravindranath, R.</span><span class="refAuthor">, Reddy, T.</span><span class="refAuthor">, and M. Thomson</span>, <span class="refTitle">"Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness"</span>, <span class="seriesInfo">RFC 7675</span>, <span class="seriesInfo">DOI 10.17487/RFC7675</span>, <time datetime="2015-10" class="refDate">October 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7675">https://www.rfc-editor.org/info/rfc7675</a>></span>. </dd> |
| 3634 |
<dd class="break"></dd> |
| 3635 |
<dt id="RFC8126">[RFC8126]</dt> |
| 3636 |
<dd> |
| 3637 |
<span class="refAuthor">Cotton, M.</span><span class="refAuthor">, Leiba, B.</span><span class="refAuthor">, and T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>></span>. </dd> |
| 3638 |
<dd class="break"></dd> |
| 3639 |
<dt id="RFC8859">[RFC8859]</dt> |
| 3640 |
<dd> |
| 3641 |
<span class="refAuthor">Nandakumar, S.</span>, <span class="refTitle">"A Framework for Session Description Protocol (SDP) Attributes When Multiplexing"</span>, <span class="seriesInfo">RFC 8859</span>, <span class="seriesInfo">DOI 10.17487/RFC8859</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8859">https://www.rfc-editor.org/info/rfc8859</a>></span>. </dd> |
| 3642 |
<dd class="break"></dd> |
| 3643 |
<dt id="RFC8863">[RFC8863]</dt> |
| 3644 |
<dd> |
| 3645 |
<span class="refAuthor">Holmberg, C.</span><span class="refAuthor"> and J. Uberti</span>, <span class="refTitle">"Interactive Connectivity Establishment Patiently Awaiting Connectivity (ICE PAC)"</span>, <span class="seriesInfo">RFC 8863</span>, <span class="seriesInfo">DOI 10.17487/RFC8863</span>, <time datetime="2021-01" class="refDate">January 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8863">https://www.rfc-editor.org/info/rfc8863</a>></span>. </dd> |
| 3646 |
<dd class="break"></dd> |
| 3647 |
</dl> |
| 3648 |
</section> |
| 3649 |
</section> |
| 3650 |
<div id="sec-example"> |
| 3651 |
<section id="section-appendix.a"> |
| 3652 |
<h2 id="name-examples"> |
| 3653 |
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-examples" class="section-name selfRef">Examples</a> |
| 3654 |
</h2> |
| 3655 |
<p id="section-appendix.a-1"> |
| 3656 |
For the example shown in <span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-15" class="relref">Section 15</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span>, |
| 3657 |
the resulting offer (message 5) encoded in SDP looks like (lines folded for clarity):<a href="#section-appendix.a-1" class="pilcrow">¶</a></p> |
| 3658 |
<div id="section-appendix.a-2"> |
| 3659 |
<pre class="sourcecode lang-sdp"> |
| 3660 |
v=0 |
| 3661 |
o=jdoe 2890844526 2890842807 IN IP6 $L-PRIV-1.IP |
| 3662 |
s= |
| 3663 |
c=IN IP6 $NAT-PUB-1.IP |
| 3664 |
t=0 0 |
| 3665 |
a=ice-options:ice2 |
| 3666 |
a=ice-pacing:50 |
| 3667 |
a=ice-pwd:asd88fgpdd777uzjYhagZg |
| 3668 |
a=ice-ufrag:8hhY |
| 3669 |
m=audio $NAT-PUB-1.PORT RTP/AVP 0 |
| 3670 |
b=RS:0 |
| 3671 |
b=RR:0 |
| 3672 |
a=rtpmap:0 PCMU/8000 |
| 3673 |
a=candidate:1 1 UDP 2130706431 $L-PRIV-1.IP $L-PRIV-1.PORT typ host |
| 3674 |
a=candidate:2 1 UDP 1694498815 $NAT-PUB-1.IP $NAT-PUB-1.PORT typ |
| 3675 |
srflx raddr $L-PRIV-1.IP rport $L-PRIV-1.PORT |
| 3676 |
</pre><a href="#section-appendix.a-2" class="pilcrow">¶</a> |
| 3677 |
</div> |
| 3678 |
<p id="section-appendix.a-3"> |
| 3679 |
The offer, with the variables replaced with their values, will look like (lines folded for clarity):<a href="#section-appendix.a-3" class="pilcrow">¶</a></p> |
| 3680 |
<div id="section-appendix.a-4"> |
| 3681 |
<pre class="sourcecode lang-sdp"> |
| 3682 |
v=0 |
| 3683 |
o=jdoe 2890844526 2890842807 IN IP6 fe80::6676:baff:fe9c:ee4a |
| 3684 |
s= |
| 3685 |
c=IN IP6 2001:db8:8101:3a55:4858:a2a9:22ff:99b9 |
| 3686 |
t=0 0 |
| 3687 |
a=ice-options:ice2 |
| 3688 |
a=ice-pacing:50 |
| 3689 |
a=ice-pwd:asd88fgpdd777uzjYhagZg |
| 3690 |
a=ice-ufrag:8hhY |
| 3691 |
m=audio 45664 RTP/AVP 0 |
| 3692 |
b=RS:0 |
| 3693 |
b=RR:0 |
| 3694 |
a=rtpmap:0 PCMU/8000 |
| 3695 |
a=candidate:1 1 UDP 2130706431 fe80::6676:baff:fe9c:ee4a 8998 |
| 3696 |
typ host |
| 3697 |
a=candidate:2 1 UDP 1694498815 2001:db8:8101:3a55:4858:a2a9:22ff:99b9 |
| 3698 |
45664 typ srflx raddr fe80::6676:baff:fe9c:ee4a rport 8998 |
| 3699 |
</pre><a href="#section-appendix.a-4" class="pilcrow">¶</a> |
| 3700 |
</div> |
| 3701 |
<p id="section-appendix.a-5"> |
| 3702 |
The resulting answer looks like:<a href="#section-appendix.a-5" class="pilcrow">¶</a></p> |
| 3703 |
<div id="section-appendix.a-6"> |
| 3704 |
<pre class="sourcecode lang-sdp"> |
| 3705 |
v=0 |
| 3706 |
o=bob 2808844564 2808844564 IN IP4 $R-PUB-1.IP |
| 3707 |
s= |
| 3708 |
c=IN IP4 $R-PUB-1.IP |
| 3709 |
t=0 0 |
| 3710 |
a=ice-options:ice2 |
| 3711 |
a=ice-pacing:50 |
| 3712 |
a=ice-pwd:YH75Fviy6338Vbrhrlp8Yh |
| 3713 |
a=ice-ufrag:9uB6 |
| 3714 |
m=audio $R-PUB-1.PORT RTP/AVP 0 |
| 3715 |
b=RS:0 |
| 3716 |
b=RR:0 |
| 3717 |
a=rtpmap:0 PCMU/8000 |
| 3718 |
a=candidate:1 1 UDP 2130706431 $R-PUB-1.IP $R-PUB-1.PORT typ host |
| 3719 |
</pre><a href="#section-appendix.a-6" class="pilcrow">¶</a> |
| 3720 |
</div> |
| 3721 |
<p id="section-appendix.a-7"> |
| 3722 |
With the variables filled in:<a href="#section-appendix.a-7" class="pilcrow">¶</a></p> |
| 3723 |
<div id="section-appendix.a-8"> |
| 3724 |
<pre class="sourcecode lang-sdp"> |
| 3725 |
v=0 |
| 3726 |
o=bob 2808844564 2808844564 IN IP4 192.0.2.1 |
| 3727 |
s= |
| 3728 |
c=IN IP4 192.0.2.1 |
| 3729 |
t=0 0 |
| 3730 |
a=ice-options:ice2 |
| 3731 |
a=ice-pacing:50 |
| 3732 |
a=ice-pwd:YH75Fviy6338Vbrhrlp8Yh |
| 3733 |
a=ice-ufrag:9uB6 |
| 3734 |
m=audio 3478 RTP/AVP 0 |
| 3735 |
b=RS:0 |
| 3736 |
b=RR:0 |
| 3737 |
a=rtpmap:0 PCMU/8000 |
| 3738 |
a=candidate:1 1 UDP 2130706431 192.0.2.1 3478 typ host |
| 3739 |
</pre><a href="#section-appendix.a-8" class="pilcrow">¶</a> |
| 3740 |
</div> |
| 3741 |
</section> |
| 3742 |
</div> |
| 3743 |
<div id="sec-why-remote"> |
| 3744 |
<section id="section-appendix.b"> |
| 3745 |
<h2 id="name-the-remote-candidates-attri"> |
| 3746 |
<a href="#section-appendix.b" class="section-number selfRef">Appendix B. </a><a href="#name-the-remote-candidates-attri" class="section-name selfRef">The "remote-candidates" Attribute</a> |
| 3747 |
</h2> |
| 3748 |
<p id="section-appendix.b-1"> |
| 3749 |
The "remote-candidates" attribute exists to eliminate a race condition between the updated offer and the response to the STUN Binding request that moved a candidate into the valid list. |
| 3750 |
This race condition is shown in <a href="#fig-race-flow" class="xref">Figure 1</a>. |
| 3751 |
On receipt of message 4, agent L adds a candidate pair to the valid list. |
| 3752 |
If there was only a single data stream with a single component, agent L could now send an updated offer. |
| 3753 |
However, the check from agent R has not yet |
| 3754 |
received a response, and agent R receives the updated offer |
| 3755 |
(message 7) before getting the response (message 9). |
| 3756 |
Thus, it does not yet know that this particular pair is valid. |
| 3757 |
To eliminate this condition, the actual candidates at R that were selected by the offerer (the remote candidates) are included in the offer itself, and the answerer delays its answer until those pairs validate.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p> |
| 3758 |
<span id="name-race-condition-flow"></span><div id="fig-race-flow"> |
| 3759 |
<figure id="figure-1"> |
| 3760 |
<div class="artwork art-text alignLeft" id="section-appendix.b-2.1"> |
| 3761 |
<pre> |
| 3762 |
Agent L Network Agent R |
| 3763 |
|(1) Offer | | |
| 3764 |
|------------------------------------------>| |
| 3765 |
|(2) Answer | | |
| 3766 |
|<------------------------------------------| |
| 3767 |
|(3) STUN Req. | | |
| 3768 |
|------------------------------------------>| |
| 3769 |
|(4) STUN Res. | | |
| 3770 |
|<------------------------------------------| |
| 3771 |
|(5) STUN Req. | | |
| 3772 |
|<------------------------------------------| |
| 3773 |
|(6) STUN Res. | | |
| 3774 |
|-------------------->| | |
| 3775 |
| |Lost | |
| 3776 |
|(7) Offer | | |
| 3777 |
|------------------------------------------>| |
| 3778 |
|(8) STUN Req. | | |
| 3779 |
|<------------------------------------------| |
| 3780 |
|(9) STUN Res. | | |
| 3781 |
|------------------------------------------>| |
| 3782 |
|(10) Answer | | |
| 3783 |
|<------------------------------------------| |
| 3784 |
</pre> |
| 3785 |
</div> |
| 3786 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 3787 |
<a href="#name-race-condition-flow" class="selfRef">Race Condition Flow</a> |
| 3788 |
</figcaption></figure> |
| 3789 |
</div> |
| 3790 |
</section> |
| 3791 |
</div> |
| 3792 |
<div id="sec-glare"> |
| 3793 |
<section id="section-appendix.c"> |
| 3794 |
<h2 id="name-why-is-the-conflict-resolut"> |
| 3795 |
<a href="#section-appendix.c" class="section-number selfRef">Appendix C. </a><a href="#name-why-is-the-conflict-resolut" class="section-name selfRef">Why Is the Conflict Resolution Mechanism Needed?</a> |
| 3796 |
</h2> |
| 3797 |
<p id="section-appendix.c-1"> |
| 3798 |
When ICE runs between two peers, one agent acts as controlled, and the other as controlling. |
| 3799 |
Rules are defined as a function of implementation type and offerer/answerer to determine who is controlling and who is controlled. |
| 3800 |
However, the specification mentions that, in some cases, both sides might believe they are controlling, or both sides might believe they are controlled. |
| 3801 |
How can this happen?<a href="#section-appendix.c-1" class="pilcrow">¶</a></p> |
| 3802 |
<p id="section-appendix.c-2"> |
| 3803 |
The condition when both agents believe they are controlled shows up in third party call control cases. |
| 3804 |
Consider the following flow:<a href="#section-appendix.c-2" class="pilcrow">¶</a></p> |
| 3805 |
<span id="name-role-conflict-flow"></span><div id="fig-conflict"> |
| 3806 |
<figure id="figure-2"> |
| 3807 |
<div class="artwork art-text alignLeft" id="section-appendix.c-3.1"> |
| 3808 |
<pre> |
| 3809 |
A Controller B |
| 3810 |
|(1) INV() | | |
| 3811 |
|<-------------| | |
| 3812 |
|(2) 200(SDP1) | | |
| 3813 |
|------------->| | |
| 3814 |
| |(3) INV() | |
| 3815 |
| |------------->| |
| 3816 |
| |(4) 200(SDP2) | |
| 3817 |
| |<-------------| |
| 3818 |
|(5) ACK(SDP2) | | |
| 3819 |
|<-------------| | |
| 3820 |
| |(6) ACK(SDP1) | |
| 3821 |
| |------------->| |
| 3822 |
</pre> |
| 3823 |
</div> |
| 3824 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 3825 |
<a href="#name-role-conflict-flow" class="selfRef">Role Conflict Flow</a> |
| 3826 |
</figcaption></figure> |
| 3827 |
</div> |
| 3828 |
<p id="section-appendix.c-4"> |
| 3829 |
This flow is a variation on flow III of RFC 3725 <span>[<a href="#RFC3725" class="xref">RFC3725</a>]</span>. |
| 3830 |
In fact, it works better than flow III since it produces fewer messages. |
| 3831 |
In this flow, the controller sends an offerless INVITE to agent A, which responds with its offer, SDP1. |
| 3832 |
The agent then sends an offerless INVITE to agent B, which it responds to with its offer, SDP2. |
| 3833 |
The controller then uses the offer from each agent to generate the answers. |
| 3834 |
When this flow is used, ICE will run between agents A and B, but both will believe they are in the controlling role. |
| 3835 |
With the role conflict resolution procedures, this flow will function properly when ICE is used.<a href="#section-appendix.c-4" class="pilcrow">¶</a></p> |
| 3836 |
<p id="section-appendix.c-5"> |
| 3837 |
At this time, there are no documented flows that can result in the case where both agents believe they are controlled. |
| 3838 |
However, the conflict resolution procedures allow for this case, should a flow arise that would fit into this category.<a href="#section-appendix.c-5" class="pilcrow">¶</a></p> |
| 3839 |
</section> |
| 3840 |
</div> |
| 3841 |
<section id="section-appendix.d"> |
| 3842 |
<h2 id="name-why-send-an-updated-offer"> |
| 3843 |
<a href="#section-appendix.d" class="section-number selfRef">Appendix D. </a><a href="#name-why-send-an-updated-offer" class="section-name selfRef">Why Send an Updated Offer?</a> |
| 3844 |
</h2> |
| 3845 |
<p id="section-appendix.d-1"> |
| 3846 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8445#section-12.1" class="relref">Section 12.1</a> of [<a href="#RFC8445" class="xref">RFC8445</a>]</span> |
| 3847 |
describes rules for sending media. |
| 3848 |
Both agents can send media once ICE checks complete, without waiting for an updated offer. |
| 3849 |
Indeed, the only purpose of the updated offer is to "correct" the SDP so that the default destination for media matches where media is being sent based on ICE procedures (which will be the highest-priority nominated candidate pair).<a href="#section-appendix.d-1" class="pilcrow">¶</a></p> |
| 3850 |
<p id="section-appendix.d-2"> |
| 3851 |
This raises the question -- why is the updated offer/answer exchange needed at all? |
| 3852 |
Indeed, in a pure offer/answer environment, it would not be. |
| 3853 |
The offerer and answerer will agree on the candidates to use through ICE, and then can begin using them. |
| 3854 |
As far as the agents themselves are concerned, the updated offer/answer provides no new information. |
| 3855 |
However, in practice, numerous components along the signaling path look at the SDP information. |
| 3856 |
These include entities performing off-path QoS reservations, NAT traversal components such as ALGs and Session Border Controllers (SBCs), and diagnostic tools that passively monitor the network. |
| 3857 |
For these tools to continue to function without change, the core property of SDP -- that the existing, pre-ICE definitions of the addresses used for media -- the "m=" and "c=" lines and the "rtcp" attribute -- must be retained. |
| 3858 |
For this reason, an updated offer must be sent.<a href="#section-appendix.d-2" class="pilcrow">¶</a></p> |
| 3859 |
</section> |
| 3860 |
<section id="section-appendix.e"> |
| 3861 |
<h2 id="name-acknowledgements"> |
| 3862 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 3863 |
</h2> |
| 3864 |
<p id="section-appendix.e-1"> |
| 3865 |
A large part of the text in this document was taken from <span>[<a href="#RFC5245" class="xref">RFC5245</a>]</span>, authored by <span class="contact-name">Jonathan Rosenberg</span>.<a href="#section-appendix.e-1" class="pilcrow">¶</a></p> |
| 3866 |
<p id="section-appendix.e-2"> |
| 3867 |
Some of the text in this document was taken from <span>[<a href="#RFC6336" class="xref">RFC6336</a>]</span>, |
| 3868 |
authored by <span class="contact-name">Magnus Westerlund</span> and <span class="contact-name">Colin Perkins</span>.<a href="#section-appendix.e-2" class="pilcrow">¶</a></p> |
| 3869 |
<p id="section-appendix.e-3"> |
| 3870 |
Many thanks to <span class="contact-name">Flemming Andreasen</span> for shepherd review feedback.<a href="#section-appendix.e-3" class="pilcrow">¶</a></p> |
| 3871 |
<p id="section-appendix.e-4"> |
| 3872 |
Thanks to following experts for their reviews and constructive feedback: |
| 3873 |
<span class="contact-name">Thomas Stach</span>, <span class="contact-name">Adam Roach</span>, |
| 3874 |
<span class="contact-name">Peter Saint-Andre</span>, <span class="contact-name">Roman Danyliw</span>, |
| 3875 |
<span class="contact-name">Alissa Cooper</span>, <span class="contact-name">Benjamin Kaduk</span>, |
| 3876 |
<span class="contact-name">Mirja Kühlewind</span>, <span class="contact-name">Alexey Melnikov</span>, and |
| 3877 |
<span class="contact-name">Éric Vyncke</span> for their detailed reviews.<a href="#section-appendix.e-4" class="pilcrow">¶</a></p> |
| 3878 |
</section> |
| 3879 |
<section id="section-appendix.f"> |
| 3880 |
<h2 id="name-contributors"> |
| 3881 |
<a href="#name-contributors" class="section-name selfRef">Contributors</a> |
| 3882 |
</h2> |
| 3883 |
<p id="section-appendix.f-1"> |
| 3884 |
The following experts have contributed textual and structural improvements for this work:<a href="#section-appendix.f-1" class="pilcrow">¶</a></p> |
| 3885 |
<address class="vcard"> |
| 3886 |
<div dir="auto" class="left"><span class="fn nameRole">Thomas Stach</span></div> |
| 3887 |
<div class="email"> |
| 3888 |
<span>Email:</span> |
| 3889 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3890 |
</div> |
| 3891 |
</address> |
| 3892 |
</section> |
| 3893 |
<div id="authors-addresses"> |
| 3894 |
<section id="section-appendix.g"> |
| 3895 |
<h2 id="name-authors-addresses"> |
| 3896 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 3897 |
</h2> |
| 3898 |
<address class="vcard"> |
| 3899 |
<div dir="auto" class="left"><span class="fn nameRole">Marc Petit-Huguenin</span></div> |
| 3900 |
<div dir="auto" class="left"><span class="org">Impedance Mismatch</span></div> |
| 3901 |
<div class="email"> |
| 3902 |
<span>Email:</span> |
| 3903 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3904 |
</div> |
| 3905 |
</address> |
| 3906 |
<address class="vcard"> |
| 3907 |
<div dir="auto" class="left"><span class="fn nameRole">Suhas Nandakumar</span></div> |
| 3908 |
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div> |
| 3909 |
<div dir="auto" class="left"><span class="street-address">707 Tasman Dr</span></div> |
| 3910 |
<div dir="auto" class="left"> |
| 3911 |
<span class="locality">Milpitas</span>, <span class="region">CA</span> <span class="postal-code">95035</span> |
| 3912 |
</div> |
| 3913 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 3914 |
<div class="email"> |
| 3915 |
<span>Email:</span> |
| 3916 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3917 |
</div> |
| 3918 |
</address> |
| 3919 |
<address class="vcard"> |
| 3920 |
<div dir="auto" class="left"><span class="fn nameRole">Christer Holmberg</span></div> |
| 3921 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 3922 |
<div dir="auto" class="left"><span class="street-address">Hirsalantie 11</span></div> |
| 3923 |
<div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span> |
| 3924 |
</div> |
| 3925 |
<div dir="auto" class="left"><span class="country-name">Finland</span></div> |
| 3926 |
<div class="email"> |
| 3927 |
<span>Email:</span> |
| 3928 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3929 |
</div> |
| 3930 |
</address> |
| 3931 |
<address class="vcard"> |
| 3932 |
<div dir="auto" class="left"><span class="fn nameRole">Ari Keränen</span></div> |
| 3933 |
<div dir="auto" class="left"><span class="org">Ericsson</span></div> |
| 3934 |
<div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span> |
| 3935 |
</div> |
| 3936 |
<div dir="auto" class="left"><span class="country-name">Finland</span></div> |
| 3937 |
<div class="email"> |
| 3938 |
<span>Email:</span> |
| 3939 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3940 |
</div> |
| 3941 |
</address> |
| 3942 |
<address class="vcard"> |
| 3943 |
<div dir="auto" class="left"><span class="fn nameRole">Roman Shpount</span></div> |
| 3944 |
<div dir="auto" class="left"><span class="org">TurboBridge</span></div> |
| 3945 |
<div dir="auto" class="left"><span class="street-address">4905 Del Ray Avenue, Suite 300</span></div> |
| 3946 |
<div dir="auto" class="left"> |
| 3947 |
<span class="locality">Bethesda</span>, <span class="region">MD</span> <span class="postal-code">20814</span> |
| 3948 |
</div> |
| 3949 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 3950 |
<div class="email"> |
| 3951 |
<span>Email:</span> |
| 3952 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 3953 |
</div> |
| 3954 |
</address> |
| 3955 |
</section> |
| 3956 |
</div> |
| 3957 |
<script>const toc = document.getElementById("toc"); |
| 3958 |
toc.querySelector("h2").addEventListener("click", e => { |
| 3959 |
toc.classList.toggle("active"); |
| 3960 |
}); |
| 3961 |
toc.querySelector("nav").addEventListener("click", e => { |
| 3962 |
toc.classList.remove("active"); |
| 3963 |
}); |
| 3964 |
</script> |
| 3965 |
</body> |
| 3966 |
</html> |