| 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 8817: RTP Payload Format for Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Codec</title> |
| 8 |
<meta content="Victor Demjanenko, Ph.D." name="author"> |
| 9 |
<meta content="John Punaro" name="author"> |
| 10 |
<meta content="David Satterlee" name="author"> |
| 11 |
<meta content=" |
| 12 |
|
| 13 |
This document describes the RTP payload format for the Tactical |
| 14 |
Secure Voice Cryptographic Interoperability Specification (TSVCIS) |
| 15 |
speech coder. TSVCIS is a scalable narrowband voice coder supporting |
| 16 |
varying encoder data rates and fallbacks. It is implemented as an |
| 17 |
augmentation to the Mixed Excitation Linear Prediction Enhanced |
| 18 |
(MELPe) speech coder by conveying additional speech coder parameters |
| 19 |
to enhance voice quality. TSVCIS augmented speech data is |
| 20 |
processed in conjunction with its temporally matched Mixed Excitation Linear |
| 21 |
Prediction (MELP) 2400 speech data. The RTP packetization of TSVCIS and |
| 22 |
MELPe speech coder data is described in detail. |
| 23 |
" name="description"> |
| 24 |
<meta content="xml2rfc 2.47.0" name="generator"> |
| 25 |
<meta content="MELP" name="keyword"> |
| 26 |
<meta content="MELPe" name="keyword"> |
| 27 |
<meta content="TSVCIS" name="keyword"> |
| 28 |
<meta content="NRLVDR" name="keyword"> |
| 29 |
<meta content="Naval Research Laboratory" name="keyword"> |
| 30 |
<meta content="NRL" name="keyword"> |
| 31 |
<meta content="NATO" name="keyword"> |
| 32 |
<meta content="TSVWG" name="keyword"> |
| 33 |
<meta content="Department of Defense" name="keyword"> |
| 34 |
<meta content="DoD" name="keyword"> |
| 35 |
<meta content="NSA" name="keyword"> |
| 36 |
<meta content="MIL-STD" name="keyword"> |
| 37 |
<meta content="8817" name="rfc.number"> |
| 38 |
<link href="rfc8817.xml" rel="alternate" type="application/rfc+xml"> |
| 39 |
<link href="#copyright" rel="license"> |
| 40 |
<style type="text/css">/* |
| 41 |
|
| 42 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 43 |
|
| 44 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 45 |
this can be consolidated so that style settings occur only in one place, but |
| 46 |
for now the contents of this file consists first of the initial CSS work as |
| 47 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 48 |
commented changes found necssary during the development of the v3 |
| 49 |
formatters. |
| 50 |
|
| 51 |
*/ |
| 52 |
|
| 53 |
/* fonts */ |
| 54 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 55 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 56 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 57 |
|
| 58 |
@viewport { |
| 59 |
zoom: 1.0; |
| 60 |
width: extend-to-zoom; |
| 61 |
} |
| 62 |
@-ms-viewport { |
| 63 |
width: extend-to-zoom; |
| 64 |
zoom: 1.0; |
| 65 |
} |
| 66 |
/* general and mobile first */ |
| 67 |
html { |
| 68 |
} |
| 69 |
body { |
| 70 |
max-width: 90%; |
| 71 |
margin: 1.5em auto; |
| 72 |
color: #222; |
| 73 |
background-color: #fff; |
| 74 |
font-size: 14px; |
| 75 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 76 |
line-height: 1.6; |
| 77 |
scroll-behavior: smooth; |
| 78 |
} |
| 79 |
.ears { |
| 80 |
display: none; |
| 81 |
} |
| 82 |
|
| 83 |
/* headings */ |
| 84 |
#title, h1, h2, h3, h4, h5, h6 { |
| 85 |
margin: 1em 0 0.5em; |
| 86 |
font-weight: bold; |
| 87 |
line-height: 1.3; |
| 88 |
} |
| 89 |
#title { |
| 90 |
clear: both; |
| 91 |
border-bottom: 1px solid #ddd; |
| 92 |
margin: 0 0 0.5em 0; |
| 93 |
padding: 1em 0 0.5em; |
| 94 |
} |
| 95 |
.author { |
| 96 |
padding-bottom: 4px; |
| 97 |
} |
| 98 |
h1 { |
| 99 |
font-size: 26px; |
| 100 |
margin: 1em 0; |
| 101 |
} |
| 102 |
h2 { |
| 103 |
font-size: 22px; |
| 104 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 105 |
padding-top: 33px; |
| 106 |
} |
| 107 |
h3 { |
| 108 |
font-size: 18px; |
| 109 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 110 |
padding-top: 42px; |
| 111 |
} |
| 112 |
h4 { |
| 113 |
font-size: 16px; |
| 114 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 115 |
padding-top: 42px; |
| 116 |
} |
| 117 |
h5, h6 { |
| 118 |
font-size: 14px; |
| 119 |
} |
| 120 |
#n-copyright-notice { |
| 121 |
border-bottom: 1px solid #ddd; |
| 122 |
padding-bottom: 1em; |
| 123 |
margin-bottom: 1em; |
| 124 |
} |
| 125 |
/* general structure */ |
| 126 |
p { |
| 127 |
padding: 0; |
| 128 |
margin: 0 0 1em 0; |
| 129 |
text-align: left; |
| 130 |
} |
| 131 |
div, span { |
| 132 |
position: relative; |
| 133 |
} |
| 134 |
div { |
| 135 |
margin: 0; |
| 136 |
} |
| 137 |
.alignRight.art-text { |
| 138 |
background-color: #f9f9f9; |
| 139 |
border: 1px solid #eee; |
| 140 |
border-radius: 3px; |
| 141 |
padding: 1em 1em 0; |
| 142 |
margin-bottom: 1.5em; |
| 143 |
} |
| 144 |
.alignRight.art-text pre { |
| 145 |
padding: 0; |
| 146 |
} |
| 147 |
.alignRight { |
| 148 |
margin: 1em 0; |
| 149 |
} |
| 150 |
.alignRight > *:first-child { |
| 151 |
border: none; |
| 152 |
margin: 0; |
| 153 |
float: right; |
| 154 |
clear: both; |
| 155 |
} |
| 156 |
.alignRight > *:nth-child(2) { |
| 157 |
clear: both; |
| 158 |
display: block; |
| 159 |
border: none; |
| 160 |
} |
| 161 |
svg { |
| 162 |
display: block; |
| 163 |
} |
| 164 |
.alignCenter.art-text { |
| 165 |
background-color: #f9f9f9; |
| 166 |
border: 1px solid #eee; |
| 167 |
border-radius: 3px; |
| 168 |
padding: 1em 1em 0; |
| 169 |
margin-bottom: 1.5em; |
| 170 |
} |
| 171 |
.alignCenter.art-text pre { |
| 172 |
padding: 0; |
| 173 |
} |
| 174 |
.alignCenter { |
| 175 |
margin: 1em 0; |
| 176 |
} |
| 177 |
.alignCenter > *:first-child { |
| 178 |
border: none; |
| 179 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 180 |
support flexbox yet. |
| 181 |
*/ |
| 182 |
display: table; |
| 183 |
margin: 0 auto; |
| 184 |
} |
| 185 |
|
| 186 |
/* lists */ |
| 187 |
ol, ul { |
| 188 |
padding: 0; |
| 189 |
margin: 0 0 1em 2em; |
| 190 |
} |
| 191 |
ol ol, ul ul, ol ul, ul ol { |
| 192 |
margin-left: 1em; |
| 193 |
} |
| 194 |
li { |
| 195 |
margin: 0 0 0.25em 0; |
| 196 |
} |
| 197 |
.ulCompact li { |
| 198 |
margin: 0; |
| 199 |
} |
| 200 |
ul.empty, .ulEmpty { |
| 201 |
list-style-type: none; |
| 202 |
} |
| 203 |
ul.empty li, .ulEmpty li { |
| 204 |
margin-top: 0.5em; |
| 205 |
} |
| 206 |
ul.compact, .ulCompact, |
| 207 |
ol.compact, .olCompact { |
| 208 |
line-height: 100%; |
| 209 |
margin: 0 0 0 2em; |
| 210 |
} |
| 211 |
|
| 212 |
/* definition lists */ |
| 213 |
dl { |
| 214 |
} |
| 215 |
dl > dt { |
| 216 |
float: left; |
| 217 |
margin-right: 1em; |
| 218 |
} |
| 219 |
/* |
| 220 |
dl.nohang > dt { |
| 221 |
float: none; |
| 222 |
} |
| 223 |
*/ |
| 224 |
dl > dd { |
| 225 |
margin-bottom: .8em; |
| 226 |
min-height: 1.3em; |
| 227 |
} |
| 228 |
dl.compact > dd, .dlCompact > dd { |
| 229 |
margin-bottom: 0em; |
| 230 |
} |
| 231 |
dl > dd > dl { |
| 232 |
margin-top: 0.5em; |
| 233 |
margin-bottom: 0em; |
| 234 |
} |
| 235 |
|
| 236 |
/* links */ |
| 237 |
a { |
| 238 |
text-decoration: none; |
| 239 |
} |
| 240 |
a[href] { |
| 241 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 242 |
} |
| 243 |
a[href]:hover { |
| 244 |
background-color: #f2f2f2; |
| 245 |
} |
| 246 |
figcaption a[href], |
| 247 |
a[href].selfRef { |
| 248 |
color: #222; |
| 249 |
} |
| 250 |
/* XXX probably not this: |
| 251 |
a.selfRef:hover { |
| 252 |
background-color: transparent; |
| 253 |
cursor: default; |
| 254 |
} */ |
| 255 |
|
| 256 |
/* Figures */ |
| 257 |
tt, code, pre, code { |
| 258 |
background-color: #f9f9f9; |
| 259 |
font-family: 'Roboto Mono', monospace; |
| 260 |
} |
| 261 |
pre { |
| 262 |
border: 1px solid #eee; |
| 263 |
margin: 0; |
| 264 |
padding: 1em; |
| 265 |
} |
| 266 |
img { |
| 267 |
max-width: 100%; |
| 268 |
} |
| 269 |
figure { |
| 270 |
margin: 0; |
| 271 |
} |
| 272 |
figure blockquote { |
| 273 |
margin: 0.8em 0.4em 0.4em; |
| 274 |
} |
| 275 |
figcaption { |
| 276 |
font-style: italic; |
| 277 |
margin: 0 0 1em 0; |
| 278 |
} |
| 279 |
@media screen { |
| 280 |
pre { |
| 281 |
overflow-x: auto; |
| 282 |
max-width: 100%; |
| 283 |
max-width: calc(100% - 22px); |
| 284 |
} |
| 285 |
} |
| 286 |
|
| 287 |
/* aside, blockquote */ |
| 288 |
aside, blockquote { |
| 289 |
margin-left: 0; |
| 290 |
padding: 1.2em 2em; |
| 291 |
} |
| 292 |
blockquote { |
| 293 |
background-color: #f9f9f9; |
| 294 |
color: #111; /* Arlen: WCAG 2019 */ |
| 295 |
border: 1px solid #ddd; |
| 296 |
border-radius: 3px; |
| 297 |
margin: 1em 0; |
| 298 |
} |
| 299 |
cite { |
| 300 |
display: block; |
| 301 |
text-align: right; |
| 302 |
font-style: italic; |
| 303 |
} |
| 304 |
|
| 305 |
/* tables */ |
| 306 |
table { |
| 307 |
width: 100%; |
| 308 |
margin: 0 0 1em; |
| 309 |
border-collapse: collapse; |
| 310 |
border: 1px solid #eee; |
| 311 |
} |
| 312 |
th, td { |
| 313 |
text-align: left; |
| 314 |
vertical-align: top; |
| 315 |
padding: 0.5em 0.75em; |
| 316 |
} |
| 317 |
th { |
| 318 |
text-align: left; |
| 319 |
background-color: #e9e9e9; |
| 320 |
} |
| 321 |
tr:nth-child(2n+1) > td { |
| 322 |
background-color: #f5f5f5; |
| 323 |
} |
| 324 |
table caption { |
| 325 |
font-style: italic; |
| 326 |
margin: 0; |
| 327 |
padding: 0; |
| 328 |
text-align: left; |
| 329 |
} |
| 330 |
table p { |
| 331 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 332 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 333 |
margin: 0; |
| 334 |
} |
| 335 |
|
| 336 |
/* pilcrow */ |
| 337 |
a.pilcrow { |
| 338 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 339 |
text-decoration: none; |
| 340 |
visibility: hidden; |
| 341 |
user-select: none; |
| 342 |
-ms-user-select: none; |
| 343 |
-o-user-select:none; |
| 344 |
-moz-user-select: none; |
| 345 |
-khtml-user-select: none; |
| 346 |
-webkit-user-select: none; |
| 347 |
-webkit-touch-callout: none; |
| 348 |
} |
| 349 |
@media screen { |
| 350 |
aside:hover > a.pilcrow, |
| 351 |
p:hover > a.pilcrow, |
| 352 |
blockquote:hover > a.pilcrow, |
| 353 |
div:hover > a.pilcrow, |
| 354 |
li:hover > a.pilcrow, |
| 355 |
pre:hover > a.pilcrow { |
| 356 |
visibility: visible; |
| 357 |
} |
| 358 |
a.pilcrow:hover { |
| 359 |
background-color: transparent; |
| 360 |
} |
| 361 |
} |
| 362 |
|
| 363 |
/* misc */ |
| 364 |
hr { |
| 365 |
border: 0; |
| 366 |
border-top: 1px solid #eee; |
| 367 |
} |
| 368 |
.bcp14 { |
| 369 |
font-variant: small-caps; |
| 370 |
} |
| 371 |
|
| 372 |
.role { |
| 373 |
font-variant: all-small-caps; |
| 374 |
} |
| 375 |
|
| 376 |
/* info block */ |
| 377 |
#identifiers { |
| 378 |
margin: 0; |
| 379 |
font-size: 0.9em; |
| 380 |
} |
| 381 |
#identifiers dt { |
| 382 |
width: 3em; |
| 383 |
clear: left; |
| 384 |
} |
| 385 |
#identifiers dd { |
| 386 |
float: left; |
| 387 |
margin-bottom: 0; |
| 388 |
} |
| 389 |
#identifiers .authors .author { |
| 390 |
display: inline-block; |
| 391 |
margin-right: 1.5em; |
| 392 |
} |
| 393 |
#identifiers .authors .org { |
| 394 |
font-style: italic; |
| 395 |
} |
| 396 |
|
| 397 |
/* The prepared/rendered info at the very bottom of the page */ |
| 398 |
.docInfo { |
| 399 |
color: #666; /* Arlen: WCAG 2019 */ |
| 400 |
font-size: 0.9em; |
| 401 |
font-style: italic; |
| 402 |
margin-top: 2em; |
| 403 |
} |
| 404 |
.docInfo .prepared { |
| 405 |
float: left; |
| 406 |
} |
| 407 |
.docInfo .prepared { |
| 408 |
float: right; |
| 409 |
} |
| 410 |
|
| 411 |
/* table of contents */ |
| 412 |
#toc { |
| 413 |
padding: 0.75em 0 2em 0; |
| 414 |
margin-bottom: 1em; |
| 415 |
} |
| 416 |
nav.toc ul { |
| 417 |
margin: 0 0.5em 0 0; |
| 418 |
padding: 0; |
| 419 |
list-style: none; |
| 420 |
} |
| 421 |
nav.toc li { |
| 422 |
line-height: 1.3em; |
| 423 |
margin: 0.75em 0; |
| 424 |
padding-left: 1.2em; |
| 425 |
text-indent: -1.2em; |
| 426 |
} |
| 427 |
/* references */ |
| 428 |
.references dt { |
| 429 |
text-align: right; |
| 430 |
font-weight: bold; |
| 431 |
min-width: 7em; |
| 432 |
} |
| 433 |
.references dd { |
| 434 |
margin-left: 8em; |
| 435 |
overflow: auto; |
| 436 |
} |
| 437 |
|
| 438 |
.refInstance { |
| 439 |
margin-bottom: 1.25em; |
| 440 |
} |
| 441 |
|
| 442 |
.references .ascii { |
| 443 |
margin-bottom: 0.25em; |
| 444 |
} |
| 445 |
|
| 446 |
/* index */ |
| 447 |
.index ul { |
| 448 |
margin: 0 0 0 1em; |
| 449 |
padding: 0; |
| 450 |
list-style: none; |
| 451 |
} |
| 452 |
.index ul ul { |
| 453 |
margin: 0; |
| 454 |
} |
| 455 |
.index li { |
| 456 |
margin: 0; |
| 457 |
text-indent: -2em; |
| 458 |
padding-left: 2em; |
| 459 |
padding-bottom: 5px; |
| 460 |
} |
| 461 |
.indexIndex { |
| 462 |
margin: 0.5em 0 1em; |
| 463 |
} |
| 464 |
.index a { |
| 465 |
font-weight: 700; |
| 466 |
} |
| 467 |
/* make the index two-column on all but the smallest screens */ |
| 468 |
@media (min-width: 600px) { |
| 469 |
.index ul { |
| 470 |
-moz-column-count: 2; |
| 471 |
-moz-column-gap: 20px; |
| 472 |
} |
| 473 |
.index ul ul { |
| 474 |
-moz-column-count: 1; |
| 475 |
-moz-column-gap: 0; |
| 476 |
} |
| 477 |
} |
| 478 |
|
| 479 |
/* authors */ |
| 480 |
address.vcard { |
| 481 |
font-style: normal; |
| 482 |
margin: 1em 0; |
| 483 |
} |
| 484 |
|
| 485 |
address.vcard .nameRole { |
| 486 |
font-weight: 700; |
| 487 |
margin-left: 0; |
| 488 |
} |
| 489 |
address.vcard .label { |
| 490 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 491 |
margin: 0.5em 0; |
| 492 |
} |
| 493 |
address.vcard .type { |
| 494 |
display: none; |
| 495 |
} |
| 496 |
.alternative-contact { |
| 497 |
margin: 1.5em 0 1em; |
| 498 |
} |
| 499 |
hr.addr { |
| 500 |
border-top: 1px dashed; |
| 501 |
margin: 0; |
| 502 |
color: #ddd; |
| 503 |
max-width: calc(100% - 16px); |
| 504 |
} |
| 505 |
|
| 506 |
/* temporary notes */ |
| 507 |
.rfcEditorRemove::before { |
| 508 |
position: absolute; |
| 509 |
top: 0.2em; |
| 510 |
right: 0.2em; |
| 511 |
padding: 0.2em; |
| 512 |
content: "The RFC Editor will remove this note"; |
| 513 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 514 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 515 |
} |
| 516 |
.rfcEditorRemove { |
| 517 |
position: relative; |
| 518 |
padding-top: 1.8em; |
| 519 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 520 |
border-radius: 3px; |
| 521 |
} |
| 522 |
.cref { |
| 523 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 524 |
padding: 2px 4px; |
| 525 |
} |
| 526 |
.crefSource { |
| 527 |
font-style: italic; |
| 528 |
} |
| 529 |
/* alternative layout for smaller screens */ |
| 530 |
@media screen and (max-width: 1023px) { |
| 531 |
body { |
| 532 |
padding-top: 2em; |
| 533 |
} |
| 534 |
#title { |
| 535 |
padding: 1em 0; |
| 536 |
} |
| 537 |
h1 { |
| 538 |
font-size: 24px; |
| 539 |
} |
| 540 |
h2 { |
| 541 |
font-size: 20px; |
| 542 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 543 |
padding-top: 38px; |
| 544 |
} |
| 545 |
#identifiers dd { |
| 546 |
max-width: 60%; |
| 547 |
} |
| 548 |
#toc { |
| 549 |
position: fixed; |
| 550 |
z-index: 2; |
| 551 |
top: 0; |
| 552 |
right: 0; |
| 553 |
padding: 0; |
| 554 |
margin: 0; |
| 555 |
background-color: inherit; |
| 556 |
border-bottom: 1px solid #ccc; |
| 557 |
} |
| 558 |
#toc h2 { |
| 559 |
margin: -1px 0 0 0; |
| 560 |
padding: 4px 0 4px 6px; |
| 561 |
padding-right: 1em; |
| 562 |
min-width: 190px; |
| 563 |
font-size: 1.1em; |
| 564 |
text-align: right; |
| 565 |
background-color: #444; |
| 566 |
color: white; |
| 567 |
cursor: pointer; |
| 568 |
} |
| 569 |
#toc h2::before { /* css hamburger */ |
| 570 |
float: right; |
| 571 |
position: relative; |
| 572 |
width: 1em; |
| 573 |
height: 1px; |
| 574 |
left: -164px; |
| 575 |
margin: 6px 0 0 0; |
| 576 |
background: white none repeat scroll 0 0; |
| 577 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 578 |
content: ""; |
| 579 |
} |
| 580 |
#toc nav { |
| 581 |
display: none; |
| 582 |
padding: 0.5em 1em 1em; |
| 583 |
overflow: auto; |
| 584 |
height: calc(100vh - 48px); |
| 585 |
border-left: 1px solid #ddd; |
| 586 |
} |
| 587 |
} |
| 588 |
|
| 589 |
/* alternative layout for wide screens */ |
| 590 |
@media screen and (min-width: 1024px) { |
| 591 |
body { |
| 592 |
max-width: 724px; |
| 593 |
margin: 42px auto; |
| 594 |
padding-left: 1.5em; |
| 595 |
padding-right: 29em; |
| 596 |
} |
| 597 |
#toc { |
| 598 |
position: fixed; |
| 599 |
top: 42px; |
| 600 |
right: 42px; |
| 601 |
width: 25%; |
| 602 |
margin: 0; |
| 603 |
padding: 0 1em; |
| 604 |
z-index: 1; |
| 605 |
} |
| 606 |
#toc h2 { |
| 607 |
border-top: none; |
| 608 |
border-bottom: 1px solid #ddd; |
| 609 |
font-size: 1em; |
| 610 |
font-weight: normal; |
| 611 |
margin: 0; |
| 612 |
padding: 0.25em 1em 1em 0; |
| 613 |
} |
| 614 |
#toc nav { |
| 615 |
display: block; |
| 616 |
height: calc(90vh - 84px); |
| 617 |
bottom: 0; |
| 618 |
padding: 0.5em 0 0; |
| 619 |
overflow: auto; |
| 620 |
} |
| 621 |
img { /* future proofing */ |
| 622 |
max-width: 100%; |
| 623 |
height: auto; |
| 624 |
} |
| 625 |
} |
| 626 |
|
| 627 |
/* pagination */ |
| 628 |
@media print { |
| 629 |
body { |
| 630 |
|
| 631 |
width: 100%; |
| 632 |
} |
| 633 |
p { |
| 634 |
orphans: 3; |
| 635 |
widows: 3; |
| 636 |
} |
| 637 |
#n-copyright-notice { |
| 638 |
border-bottom: none; |
| 639 |
} |
| 640 |
#toc, #n-introduction { |
| 641 |
page-break-before: always; |
| 642 |
} |
| 643 |
#toc { |
| 644 |
border-top: none; |
| 645 |
padding-top: 0; |
| 646 |
} |
| 647 |
figure, pre { |
| 648 |
page-break-inside: avoid; |
| 649 |
} |
| 650 |
figure { |
| 651 |
overflow: scroll; |
| 652 |
} |
| 653 |
h1, h2, h3, h4, h5, h6 { |
| 654 |
page-break-after: avoid; |
| 655 |
} |
| 656 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 657 |
page-break-before: avoid; |
| 658 |
} |
| 659 |
pre { |
| 660 |
white-space: pre-wrap; |
| 661 |
word-wrap: break-word; |
| 662 |
font-size: 10pt; |
| 663 |
} |
| 664 |
table { |
| 665 |
border: 1px solid #ddd; |
| 666 |
} |
| 667 |
td { |
| 668 |
border-top: 1px solid #ddd; |
| 669 |
} |
| 670 |
} |
| 671 |
|
| 672 |
/* This is commented out here, as the string-set: doesn't |
| 673 |
pass W3C validation currently */ |
| 674 |
/* |
| 675 |
.ears thead .left { |
| 676 |
string-set: ears-top-left content(); |
| 677 |
} |
| 678 |
|
| 679 |
.ears thead .center { |
| 680 |
string-set: ears-top-center content(); |
| 681 |
} |
| 682 |
|
| 683 |
.ears thead .right { |
| 684 |
string-set: ears-top-right content(); |
| 685 |
} |
| 686 |
|
| 687 |
.ears tfoot .left { |
| 688 |
string-set: ears-bottom-left content(); |
| 689 |
} |
| 690 |
|
| 691 |
.ears tfoot .center { |
| 692 |
string-set: ears-bottom-center content(); |
| 693 |
} |
| 694 |
|
| 695 |
.ears tfoot .right { |
| 696 |
string-set: ears-bottom-right content(); |
| 697 |
} |
| 698 |
*/ |
| 699 |
|
| 700 |
@page :first { |
| 701 |
padding-top: 0; |
| 702 |
@top-left { |
| 703 |
content: normal; |
| 704 |
border: none; |
| 705 |
} |
| 706 |
@top-center { |
| 707 |
content: normal; |
| 708 |
border: none; |
| 709 |
} |
| 710 |
@top-right { |
| 711 |
content: normal; |
| 712 |
border: none; |
| 713 |
} |
| 714 |
} |
| 715 |
|
| 716 |
@page { |
| 717 |
size: A4; |
| 718 |
margin-bottom: 45mm; |
| 719 |
padding-top: 20px; |
| 720 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 721 |
the content depends on the document */ |
| 722 |
/* |
| 723 |
@top-left { |
| 724 |
content: 'Internet-Draft'; |
| 725 |
vertical-align: bottom; |
| 726 |
border-bottom: solid 1px #ccc; |
| 727 |
} |
| 728 |
@top-left { |
| 729 |
content: string(ears-top-left); |
| 730 |
vertical-align: bottom; |
| 731 |
border-bottom: solid 1px #ccc; |
| 732 |
} |
| 733 |
@top-center { |
| 734 |
content: string(ears-top-center); |
| 735 |
vertical-align: bottom; |
| 736 |
border-bottom: solid 1px #ccc; |
| 737 |
} |
| 738 |
@top-right { |
| 739 |
content: string(ears-top-right); |
| 740 |
vertical-align: bottom; |
| 741 |
border-bottom: solid 1px #ccc; |
| 742 |
} |
| 743 |
@bottom-left { |
| 744 |
content: string(ears-bottom-left); |
| 745 |
vertical-align: top; |
| 746 |
border-top: solid 1px #ccc; |
| 747 |
} |
| 748 |
@bottom-center { |
| 749 |
content: string(ears-bottom-center); |
| 750 |
vertical-align: top; |
| 751 |
border-top: solid 1px #ccc; |
| 752 |
} |
| 753 |
@bottom-right { |
| 754 |
content: '[Page ' counter(page) ']'; |
| 755 |
vertical-align: top; |
| 756 |
border-top: solid 1px #ccc; |
| 757 |
} |
| 758 |
*/ |
| 759 |
|
| 760 |
} |
| 761 |
|
| 762 |
/* Changes introduced to fix issues found during implementation */ |
| 763 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 764 |
a { |
| 765 |
z-index: 2; |
| 766 |
} |
| 767 |
/* Separate body from document info even without intervening H1 */ |
| 768 |
section { |
| 769 |
clear: both; |
| 770 |
} |
| 771 |
|
| 772 |
|
| 773 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 774 |
.author { |
| 775 |
vertical-align: top; |
| 776 |
} |
| 777 |
|
| 778 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 779 |
#identifiers dt { |
| 780 |
width: 8em; |
| 781 |
} |
| 782 |
|
| 783 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 784 |
#identifiers dd { |
| 785 |
margin-left: 1em; |
| 786 |
} |
| 787 |
|
| 788 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 789 |
#toc { |
| 790 |
background-color: white; |
| 791 |
} |
| 792 |
|
| 793 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 794 |
@media screen and (max-width: 1023px) { |
| 795 |
#toc h2 a, |
| 796 |
#toc h2 a:link, |
| 797 |
#toc h2 a:focus, |
| 798 |
#toc h2 a:hover, |
| 799 |
#toc a.toplink, |
| 800 |
#toc a.toplink:hover { |
| 801 |
color: white; |
| 802 |
background-color: #444; |
| 803 |
text-decoration: none; |
| 804 |
} |
| 805 |
} |
| 806 |
|
| 807 |
/* Give the bottom of the ToC some whitespace */ |
| 808 |
@media screen and (min-width: 1024px) { |
| 809 |
#toc { |
| 810 |
padding: 0 0 1em 1em; |
| 811 |
} |
| 812 |
} |
| 813 |
|
| 814 |
/* Style section numbers with more space between number and title */ |
| 815 |
.section-number { |
| 816 |
padding-right: 0.5em; |
| 817 |
} |
| 818 |
|
| 819 |
/* prevent monospace from becoming overly large */ |
| 820 |
tt, code, pre, code { |
| 821 |
font-size: 95%; |
| 822 |
} |
| 823 |
|
| 824 |
/* Fix the height/width aspect for ascii art*/ |
| 825 |
pre.sourcecode, |
| 826 |
.art-text pre { |
| 827 |
line-height: 1.12; |
| 828 |
} |
| 829 |
|
| 830 |
|
| 831 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 832 |
a.toplink { |
| 833 |
float: right; |
| 834 |
margin-right: 0.5em; |
| 835 |
} |
| 836 |
|
| 837 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 838 |
dl > dt, |
| 839 |
dl.dlParallel > dt { |
| 840 |
float: left; |
| 841 |
margin-right: 1em; |
| 842 |
} |
| 843 |
dl.dlNewline > dt { |
| 844 |
float: none; |
| 845 |
} |
| 846 |
|
| 847 |
/* Provide styling for table cell text alignment */ |
| 848 |
table td.text-left, |
| 849 |
table th.text-left { |
| 850 |
text-align: left; |
| 851 |
} |
| 852 |
table td.text-center, |
| 853 |
table th.text-center { |
| 854 |
text-align: center; |
| 855 |
} |
| 856 |
table td.text-right, |
| 857 |
table th.text-right { |
| 858 |
text-align: right; |
| 859 |
} |
| 860 |
|
| 861 |
/* Make the alternative author contact informatio look less like just another |
| 862 |
author, and group it closer with the primary author contact information */ |
| 863 |
.alternative-contact { |
| 864 |
margin: 0.5em 0 0.25em 0; |
| 865 |
} |
| 866 |
address .non-ascii { |
| 867 |
margin: 0 0 0 2em; |
| 868 |
} |
| 869 |
|
| 870 |
/* With it being possible to set tables with alignment |
| 871 |
left, center, and right, { width: 100%; } does not make sense */ |
| 872 |
table { |
| 873 |
width: auto; |
| 874 |
} |
| 875 |
|
| 876 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 877 |
because of a long floating dt label.*/ |
| 878 |
.references dd { |
| 879 |
overflow: visible; |
| 880 |
} |
| 881 |
|
| 882 |
/* Control caption placement */ |
| 883 |
caption { |
| 884 |
caption-side: bottom; |
| 885 |
} |
| 886 |
|
| 887 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 888 |
script don't end up on the other side of the page. */ |
| 889 |
|
| 890 |
address.vcard { |
| 891 |
max-width: 30em; |
| 892 |
margin-right: auto; |
| 893 |
} |
| 894 |
|
| 895 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 896 |
address div.left { |
| 897 |
text-align: left; |
| 898 |
} |
| 899 |
address div.right { |
| 900 |
text-align: right; |
| 901 |
} |
| 902 |
|
| 903 |
/* Provide table alignment support. We can't use the alignX classes above |
| 904 |
since they do unwanted things with caption and other styling. */ |
| 905 |
table.right { |
| 906 |
margin-left: auto; |
| 907 |
margin-right: 0; |
| 908 |
} |
| 909 |
table.center { |
| 910 |
margin-left: auto; |
| 911 |
margin-right: auto; |
| 912 |
} |
| 913 |
table.left { |
| 914 |
margin-left: 0; |
| 915 |
margin-right: auto; |
| 916 |
} |
| 917 |
|
| 918 |
/* Give the table caption label the same styling as the figcaption */ |
| 919 |
caption a[href] { |
| 920 |
color: #222; |
| 921 |
} |
| 922 |
|
| 923 |
@media print { |
| 924 |
.toplink { |
| 925 |
display: none; |
| 926 |
} |
| 927 |
|
| 928 |
/* avoid overwriting the top border line with the ToC header */ |
| 929 |
#toc { |
| 930 |
padding-top: 1px; |
| 931 |
} |
| 932 |
|
| 933 |
/* Avoid page breaks inside dl and author address entries */ |
| 934 |
.vcard { |
| 935 |
page-break-inside: avoid; |
| 936 |
} |
| 937 |
|
| 938 |
} |
| 939 |
/* Tweak the bcp14 keyword presentation */ |
| 940 |
.bcp14 { |
| 941 |
font-variant: small-caps; |
| 942 |
font-weight: bold; |
| 943 |
font-size: 0.9em; |
| 944 |
} |
| 945 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 946 |
h2 { |
| 947 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 948 |
padding-top: 31px; |
| 949 |
} |
| 950 |
h3 { |
| 951 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 952 |
padding-top: 24px; |
| 953 |
} |
| 954 |
h4 { |
| 955 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 956 |
padding-top: 24px; |
| 957 |
} |
| 958 |
/* Float artwork pilcrow to the right */ |
| 959 |
@media screen { |
| 960 |
.artwork a.pilcrow { |
| 961 |
display: block; |
| 962 |
line-height: 0.7; |
| 963 |
margin-top: 0.15em; |
| 964 |
} |
| 965 |
} |
| 966 |
/* Make pilcrows on dd visible */ |
| 967 |
@media screen { |
| 968 |
dd:hover > a.pilcrow { |
| 969 |
visibility: visible; |
| 970 |
} |
| 971 |
} |
| 972 |
/* Make the placement of figcaption match that of a table's caption |
| 973 |
by removing the figure's added bottom margin */ |
| 974 |
.alignLeft.art-text, |
| 975 |
.alignCenter.art-text, |
| 976 |
.alignRight.art-text { |
| 977 |
margin-bottom: 0; |
| 978 |
} |
| 979 |
.alignLeft, |
| 980 |
.alignCenter, |
| 981 |
.alignRight { |
| 982 |
margin: 1em 0 0 0; |
| 983 |
} |
| 984 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 985 |
possibly even requiring a new line */ |
| 986 |
@media print { |
| 987 |
a.pilcrow { |
| 988 |
display: none; |
| 989 |
} |
| 990 |
} |
| 991 |
/* Styling for the external metadata */ |
| 992 |
div#external-metadata { |
| 993 |
background-color: #eee; |
| 994 |
padding: 0.5em; |
| 995 |
margin-bottom: 0.5em; |
| 996 |
display: none; |
| 997 |
} |
| 998 |
div#internal-metadata { |
| 999 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1000 |
} |
| 1001 |
/* Styling for title RFC Number */ |
| 1002 |
h1#rfcnum { |
| 1003 |
clear: both; |
| 1004 |
margin: 0 0 -1em; |
| 1005 |
padding: 1em 0 0 0; |
| 1006 |
} |
| 1007 |
/* Make .olPercent look the same as <ol><li> */ |
| 1008 |
dl.olPercent > dd { |
| 1009 |
margin-bottom: 0.25em; |
| 1010 |
min-height: initial; |
| 1011 |
} |
| 1012 |
/* Give aside some styling to set it apart */ |
| 1013 |
aside { |
| 1014 |
border-left: 1px solid #ddd; |
| 1015 |
margin: 1em 0 1em 2em; |
| 1016 |
padding: 0.2em 2em; |
| 1017 |
} |
| 1018 |
aside > dl, |
| 1019 |
aside > ol, |
| 1020 |
aside > ul, |
| 1021 |
aside > table, |
| 1022 |
aside > p { |
| 1023 |
margin-bottom: 0.5em; |
| 1024 |
} |
| 1025 |
/* Additional page break settings */ |
| 1026 |
@media print { |
| 1027 |
figcaption, table caption { |
| 1028 |
page-break-before: avoid; |
| 1029 |
} |
| 1030 |
} |
| 1031 |
/* Font size adjustments for print */ |
| 1032 |
@media print { |
| 1033 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1034 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1035 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1036 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1037 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1038 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1039 |
} |
| 1040 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1041 |
@media print { |
| 1042 |
.artwork, |
| 1043 |
.sourcecode { |
| 1044 |
margin-bottom: 1em; |
| 1045 |
} |
| 1046 |
} |
| 1047 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1048 |
table { |
| 1049 |
min-width: 20em; |
| 1050 |
} |
| 1051 |
/* ol type a */ |
| 1052 |
ol.type-a { list-style-type: lower-alpha; } |
| 1053 |
ol.type-A { list-style-type: upper-alpha; } |
| 1054 |
ol.type-i { list-style-type: lower-roman; } |
| 1055 |
ol.type-I { list-style-type: lower-roman; } |
| 1056 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1057 |
and increase the contrast between border and odd row background sligthtly */ |
| 1058 |
table { |
| 1059 |
border: 1px solid #ddd; |
| 1060 |
} |
| 1061 |
td { |
| 1062 |
border-top: 1px solid #ddd; |
| 1063 |
} |
| 1064 |
tr:nth-child(2n+1) > td { |
| 1065 |
background-color: #f8f8f8; |
| 1066 |
} |
| 1067 |
/* Use style rules to govern display of the TOC. */ |
| 1068 |
@media screen and (max-width: 1023px) { |
| 1069 |
#toc nav { display: none; } |
| 1070 |
#toc.active nav { display: block; } |
| 1071 |
} |
| 1072 |
/* Add support for keepWithNext */ |
| 1073 |
.keepWithNext { |
| 1074 |
break-after: avoid-page; |
| 1075 |
break-after: avoid-page; |
| 1076 |
} |
| 1077 |
/* Add support for keepWithPrevious */ |
| 1078 |
.keepWithPrevious { |
| 1079 |
break-before: avoid-page; |
| 1080 |
} |
| 1081 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1082 |
figure, pre, table, .artwork, .sourcecode { |
| 1083 |
break-before: avoid-page; |
| 1084 |
break-after: auto; |
| 1085 |
} |
| 1086 |
/* Avoid breaks between <dt> and <dd> */ |
| 1087 |
dl { |
| 1088 |
break-before: auto; |
| 1089 |
break-inside: auto; |
| 1090 |
} |
| 1091 |
dt { |
| 1092 |
break-before: auto; |
| 1093 |
break-after: avoid-page; |
| 1094 |
} |
| 1095 |
dd { |
| 1096 |
break-before: avoid-page; |
| 1097 |
break-after: auto; |
| 1098 |
orphans: 3; |
| 1099 |
widows: 3 |
| 1100 |
} |
| 1101 |
span.break, dd.break { |
| 1102 |
margin-bottom: 0; |
| 1103 |
min-height: 0; |
| 1104 |
break-before: auto; |
| 1105 |
break-inside: auto; |
| 1106 |
break-after: auto; |
| 1107 |
} |
| 1108 |
/* Undo break-before ToC */ |
| 1109 |
@media print { |
| 1110 |
#toc { |
| 1111 |
break-before: auto; |
| 1112 |
} |
| 1113 |
} |
| 1114 |
/* Text in compact lists should not get extra bottim margin space, |
| 1115 |
since that would makes the list not compact */ |
| 1116 |
ul.compact p, .ulCompact p, |
| 1117 |
ol.compact p, .olCompact p { |
| 1118 |
margin: 0; |
| 1119 |
} |
| 1120 |
/* But the list as a whole needs the extra space at the end */ |
| 1121 |
section ul.compact, |
| 1122 |
section .ulCompact, |
| 1123 |
section ol.compact, |
| 1124 |
section .olCompact { |
| 1125 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1126 |
} |
| 1127 |
/* The tt and code background above interferes with for instance table cell |
| 1128 |
backgrounds. Changed to something a bit more selective. */ |
| 1129 |
tt, code { |
| 1130 |
background-color: transparent; |
| 1131 |
} |
| 1132 |
p tt, p code, li tt, li code { |
| 1133 |
background-color: #f8f8f8; |
| 1134 |
} |
| 1135 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1136 |
pre { |
| 1137 |
margin-top: 0.5px; |
| 1138 |
} |
| 1139 |
/* Tweak the comact list text */ |
| 1140 |
ul.compact, .ulCompact, |
| 1141 |
ol.compact, .olCompact { |
| 1142 |
line-height: normal; |
| 1143 |
} |
| 1144 |
/* Don't add top margin for nested lists */ |
| 1145 |
li > ul, li > ol, li > dl, |
| 1146 |
dd > ul, dd > ol, dd > dl, |
| 1147 |
dl > dd > dl { |
| 1148 |
margin-top: initial; |
| 1149 |
}</style> |
| 1150 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1151 |
<link href="https://dx.doi.org/10.17487/rfc8817" rel="alternate"> |
| 1152 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1153 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-payload-tsvcis-05" rel="prev"> |
| 1154 |
</head> |
| 1155 |
<body> |
| 1156 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1157 |
<table class="ears"> |
| 1158 |
<thead><tr> |
| 1159 |
<td class="left">RFC 8817</td> |
| 1160 |
<td class="center">RTP Payload Format for TSVCIS Codec</td> |
| 1161 |
<td class="right">August 2020</td> |
| 1162 |
</tr></thead> |
| 1163 |
<tfoot><tr> |
| 1164 |
<td class="left">Demjanenko, et al.</td> |
| 1165 |
<td class="center">Standards Track</td> |
| 1166 |
<td class="right">[Page]</td> |
| 1167 |
</tr></tfoot> |
| 1168 |
</table> |
| 1169 |
<div id="external-metadata" class="document-information"></div> |
| 1170 |
<div id="internal-metadata" class="document-information"> |
| 1171 |
<dl id="identifiers"> |
| 1172 |
<dt class="label-stream">Stream:</dt> |
| 1173 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1174 |
<dt class="label-rfc">RFC:</dt> |
| 1175 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8817" class="eref">8817</a></dd> |
| 1176 |
<dt class="label-category">Category:</dt> |
| 1177 |
<dd class="category">Standards Track</dd> |
| 1178 |
<dt class="label-published">Published:</dt> |
| 1179 |
<dd class="published"> |
| 1180 |
<time datetime="2020-08" class="published">August 2020</time> |
| 1181 |
</dd> |
| 1182 |
<dt class="label-issn">ISSN:</dt> |
| 1183 |
<dd class="issn">2070-1721</dd> |
| 1184 |
<dt class="label-authors">Authors:</dt> |
| 1185 |
<dd class="authors"> |
| 1186 |
<div class="author"> |
| 1187 |
<div class="author-name">V. Demjanenko</div> |
| 1188 |
<div class="org">VOCAL Technologies, Ltd.</div> |
| 1189 |
</div> |
| 1190 |
<div class="author"> |
| 1191 |
<div class="author-name">J. Punaro</div> |
| 1192 |
<div class="org">VOCAL Technologies, Ltd.</div> |
| 1193 |
</div> |
| 1194 |
<div class="author"> |
| 1195 |
<div class="author-name">D. Satterlee</div> |
| 1196 |
<div class="org">VOCAL Technologies, Ltd.</div> |
| 1197 |
</div> |
| 1198 |
</dd> |
| 1199 |
</dl> |
| 1200 |
</div> |
| 1201 |
<h1 id="rfcnum">RFC 8817</h1> |
| 1202 |
<h1 id="title">RTP Payload Format for Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Codec</h1> |
| 1203 |
<section id="section-abstract"> |
| 1204 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1205 |
<p id="section-abstract-1"> |
| 1206 |
This document describes the RTP payload format for the Tactical |
| 1207 |
Secure Voice Cryptographic Interoperability Specification (TSVCIS) |
| 1208 |
speech coder. TSVCIS is a scalable narrowband voice coder supporting |
| 1209 |
varying encoder data rates and fallbacks. It is implemented as an |
| 1210 |
augmentation to the Mixed Excitation Linear Prediction Enhanced |
| 1211 |
(MELPe) speech coder by conveying additional speech coder parameters |
| 1212 |
to enhance voice quality. TSVCIS augmented speech data is |
| 1213 |
processed in conjunction with its temporally matched Mixed Excitation Linear |
| 1214 |
Prediction (MELP) 2400 speech data. The RTP packetization of TSVCIS and |
| 1215 |
MELPe speech coder data is described in detail.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1216 |
</section> |
| 1217 |
<div id="status-of-memo"> |
| 1218 |
<section id="section-boilerplate.1"> |
| 1219 |
<h2 id="name-status-of-this-memo"> |
| 1220 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1221 |
</h2> |
| 1222 |
<p id="section-boilerplate.1-1"> |
| 1223 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1224 |
<p id="section-boilerplate.1-2"> |
| 1225 |
This document is a product of the Internet Engineering Task Force |
| 1226 |
(IETF). It represents the consensus of the IETF community. It has |
| 1227 |
received public review and has been approved for publication by |
| 1228 |
the Internet Engineering Steering Group (IESG). Further |
| 1229 |
information on Internet Standards is available in Section 2 of |
| 1230 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1231 |
<p id="section-boilerplate.1-3"> |
| 1232 |
Information about the current status of this document, any |
| 1233 |
errata, and how to provide feedback on it may be obtained at |
| 1234 |
<span><a href="https://www.rfc-editor.org/info/rfc8817">https://www.rfc-editor.org/info/rfc8817</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1235 |
</section> |
| 1236 |
</div> |
| 1237 |
<div id="copyright"> |
| 1238 |
<section id="section-boilerplate.2"> |
| 1239 |
<h2 id="name-copyright-notice"> |
| 1240 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1241 |
</h2> |
| 1242 |
<p id="section-boilerplate.2-1"> |
| 1243 |
Copyright (c) 2020 IETF Trust and the persons identified as the |
| 1244 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1245 |
<p id="section-boilerplate.2-2"> |
| 1246 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1247 |
Provisions Relating to IETF Documents |
| 1248 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1249 |
publication of this document. Please review these documents |
| 1250 |
carefully, as they describe your rights and restrictions with |
| 1251 |
respect to this document. Code Components extracted from this |
| 1252 |
document must include Simplified BSD License text as described in |
| 1253 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1254 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1255 |
</section> |
| 1256 |
</div> |
| 1257 |
<div id="toc"> |
| 1258 |
<section id="section-toc.1"> |
| 1259 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1260 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1261 |
</h2> |
| 1262 |
<nav class="toc"><ul class="compact ulEmpty toc"> |
| 1263 |
<li class="compact ulEmpty toc" id="section-toc.1-1.1"> |
| 1264 |
<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> |
| 1265 |
<ul class="toc ulEmpty compact"> |
| 1266 |
<li class="toc ulEmpty compact" id="section-toc.1-1.1.2.1"> |
| 1267 |
<p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>. <a href="#name-conventions" class="xref">Conventions</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p> |
| 1268 |
</li> |
| 1269 |
<li class="toc ulEmpty compact" id="section-toc.1-1.1.2.2"> |
| 1270 |
<p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>. <a href="#name-abbreviations" class="xref">Abbreviations</a><a href="#section-toc.1-1.1.2.2.1" class="pilcrow">¶</a></p> |
| 1271 |
</li> |
| 1272 |
</ul> |
| 1273 |
</li> |
| 1274 |
<li class="compact ulEmpty toc" id="section-toc.1-1.2"> |
| 1275 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-background" class="xref">Background</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1276 |
</li> |
| 1277 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3"> |
| 1278 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-payload-format" class="xref">Payload Format</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1279 |
<ul class="toc ulEmpty compact"> |
| 1280 |
<li class="toc ulEmpty compact" id="section-toc.1-1.3.2.1"> |
| 1281 |
<p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-melpe-bitstream-definitions" class="xref">MELPe Bitstream Definitions</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p> |
| 1282 |
<ul class="compact ulEmpty toc"> |
| 1283 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3.2.1.2.1"> |
| 1284 |
<p id="section-toc.1-1.3.2.1.2.1.1"><a href="#section-3.1.1" class="xref">3.1.1</a>. <a href="#name-2400-bps-bitstream-structur" class="xref">2400 bps Bitstream Structure</a><a href="#section-toc.1-1.3.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1285 |
</li> |
| 1286 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3.2.1.2.2"> |
| 1287 |
<p id="section-toc.1-1.3.2.1.2.2.1"><a href="#section-3.1.2" class="xref">3.1.2</a>. <a href="#name-1200-bps-bitstream-structur" class="xref">1200 bps Bitstream Structure</a><a href="#section-toc.1-1.3.2.1.2.2.1" class="pilcrow">¶</a></p> |
| 1288 |
</li> |
| 1289 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3.2.1.2.3"> |
| 1290 |
<p id="section-toc.1-1.3.2.1.2.3.1"><a href="#section-3.1.3" class="xref">3.1.3</a>. <a href="#name-600-bps-bitstream-structure" class="xref">600 bps Bitstream Structure</a><a href="#section-toc.1-1.3.2.1.2.3.1" class="pilcrow">¶</a></p> |
| 1291 |
</li> |
| 1292 |
<li class="compact ulEmpty toc" id="section-toc.1-1.3.2.1.2.4"> |
| 1293 |
<p id="section-toc.1-1.3.2.1.2.4.1"><a href="#section-3.1.4" class="xref">3.1.4</a>. <a href="#name-comfort-noise-bitstream-def" class="xref">Comfort Noise Bitstream Definition</a><a href="#section-toc.1-1.3.2.1.2.4.1" class="pilcrow">¶</a></p> |
| 1294 |
</li> |
| 1295 |
</ul> |
| 1296 |
</li> |
| 1297 |
<li class="toc ulEmpty compact" id="section-toc.1-1.3.2.2"> |
| 1298 |
<p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>. <a href="#name-tsvcis-bitstream-definition" class="xref">TSVCIS Bitstream Definition</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p> |
| 1299 |
</li> |
| 1300 |
<li class="toc ulEmpty compact" id="section-toc.1-1.3.2.3"> |
| 1301 |
<p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>. <a href="#name-multiple-tsvcis-frames-in-a" class="xref">Multiple TSVCIS Frames in an RTP Packet</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p> |
| 1302 |
</li> |
| 1303 |
<li class="toc ulEmpty compact" id="section-toc.1-1.3.2.4"> |
| 1304 |
<p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>. <a href="#name-congestion-control-consider" class="xref">Congestion Control Considerations</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p> |
| 1305 |
</li> |
| 1306 |
</ul> |
| 1307 |
</li> |
| 1308 |
<li class="compact ulEmpty toc" id="section-toc.1-1.4"> |
| 1309 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-payload-format-parameters" class="xref">Payload Format Parameters</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1310 |
<ul class="toc ulEmpty compact"> |
| 1311 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.1"> |
| 1312 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-media-type-definitions" class="xref">Media Type Definitions</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1313 |
</li> |
| 1314 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.2"> |
| 1315 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-mapping-to-sdp" class="xref">Mapping to SDP</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1316 |
</li> |
| 1317 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.3"> |
| 1318 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-declarative-sdp-considerati" class="xref">Declarative SDP Considerations</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p> |
| 1319 |
</li> |
| 1320 |
<li class="toc ulEmpty compact" id="section-toc.1-1.4.2.4"> |
| 1321 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>. <a href="#name-offer-answer-sdp-considerat" class="xref">Offer/Answer SDP Considerations</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p> |
| 1322 |
</li> |
| 1323 |
</ul> |
| 1324 |
</li> |
| 1325 |
<li class="compact ulEmpty toc" id="section-toc.1-1.5"> |
| 1326 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-discontinuous-transmissions" class="xref">Discontinuous Transmissions</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1327 |
</li> |
| 1328 |
<li class="compact ulEmpty toc" id="section-toc.1-1.6"> |
| 1329 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-packet-loss-concealment" class="xref">Packet Loss Concealment</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1330 |
</li> |
| 1331 |
<li class="compact ulEmpty toc" id="section-toc.1-1.7"> |
| 1332 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1333 |
</li> |
| 1334 |
<li class="compact ulEmpty toc" id="section-toc.1-1.8"> |
| 1335 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1336 |
</li> |
| 1337 |
<li class="compact ulEmpty toc" id="section-toc.1-1.9"> |
| 1338 |
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1339 |
<ul class="toc ulEmpty compact"> |
| 1340 |
<li class="toc ulEmpty compact" id="section-toc.1-1.9.2.1"> |
| 1341 |
<p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p> |
| 1342 |
</li> |
| 1343 |
<li class="toc ulEmpty compact" id="section-toc.1-1.9.2.2"> |
| 1344 |
<p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p> |
| 1345 |
</li> |
| 1346 |
</ul> |
| 1347 |
</li> |
| 1348 |
<li class="compact ulEmpty toc" id="section-toc.1-1.10"> |
| 1349 |
<p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1350 |
</li> |
| 1351 |
</ul> |
| 1352 |
</nav> |
| 1353 |
</section> |
| 1354 |
</div> |
| 1355 |
<div id="sect-1"> |
| 1356 |
<section id="section-1"> |
| 1357 |
<h2 id="name-introduction"> |
| 1358 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1359 |
</h2> |
| 1360 |
<p id="section-1-1"> |
| 1361 |
This document describes how compressed Tactical Secure Voice |
| 1362 |
Cryptographic Interoperability Specification (TSVCIS) speech as |
| 1363 |
produced by the TSVCIS codec <span>[<a href="#TSVCIS" class="xref">TSVCIS</a>]</span> <span>[<a href="#NRLVDR" class="xref">NRLVDR</a>]</span> may be formatted for |
| 1364 |
use as an RTP payload. The TSVCIS speech coder (or TSVCIS speech-aware communications equipment on any intervening transport link) may |
| 1365 |
adjust to restricted bandwidth conditions by reducing the amount of |
| 1366 |
augmented speech data and relying on the underlying MELPe speech |
| 1367 |
coder for the most constrained bandwidth links.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1368 |
<p id="section-1-2"> |
| 1369 |
Details are provided for packetizing the TSVCIS augmented speech data |
| 1370 |
along with MELPe 2400 bps speech parameters in an RTP packet. The |
| 1371 |
sender may send one or more codec data frames per packet, depending |
| 1372 |
on the application scenario or based on transport network conditions, |
| 1373 |
bandwidth restrictions, delay requirements, and packet loss |
| 1374 |
tolerance.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1375 |
<div id="sect-1.1"> |
| 1376 |
<section id="section-1.1"> |
| 1377 |
<h3 id="name-conventions"> |
| 1378 |
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-conventions" class="section-name selfRef">Conventions</a> |
| 1379 |
</h3> |
| 1380 |
<p id="section-1.1-1"> |
| 1381 |
The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", |
| 1382 |
"<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", |
| 1383 |
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", |
| 1384 |
"<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", |
| 1385 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as |
| 1386 |
described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> |
| 1387 |
when, and only when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p> |
| 1388 |
<p id="section-1.1-2"> |
| 1389 |
Best current practices for writing an RTP payload format |
| 1390 |
specification were followed <span>[<a href="#RFC2736" class="xref">RFC2736</a>]</span> <span>[<a href="#RFC8088" class="xref">RFC8088</a>]</span>.<a href="#section-1.1-2" class="pilcrow">¶</a></p> |
| 1391 |
</section> |
| 1392 |
</div> |
| 1393 |
<div id="sect-1.2"> |
| 1394 |
<section id="section-1.2"> |
| 1395 |
<h3 id="name-abbreviations"> |
| 1396 |
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-abbreviations" class="section-name selfRef">Abbreviations</a> |
| 1397 |
</h3> |
| 1398 |
<p id="section-1.2-1">The following abbreviations are used in this document.<a href="#section-1.2-1" class="pilcrow">¶</a></p> |
| 1399 |
<span class="break"></span><dl class="dlParallel" id="section-1.2-2"> |
| 1400 |
<dt id="section-1.2-2.1">AVP:</dt> |
| 1401 |
<dd style="margin-left: 5.0em" id="section-1.2-2.2">Audio/Video Profile<a href="#section-1.2-2.2" class="pilcrow">¶</a> |
| 1402 |
</dd> |
| 1403 |
<dd class="break"></dd> |
| 1404 |
<dt id="section-1.2-2.3">AVPF:</dt> |
| 1405 |
<dd style="margin-left: 5.0em" id="section-1.2-2.4">Audio/Video Profile Feedback<a href="#section-1.2-2.4" class="pilcrow">¶</a> |
| 1406 |
</dd> |
| 1407 |
<dd class="break"></dd> |
| 1408 |
<dt id="section-1.2-2.5">CELP:</dt> |
| 1409 |
<dd style="margin-left: 5.0em" id="section-1.2-2.6">Code-Excited Linear Prediction<a href="#section-1.2-2.6" class="pilcrow">¶</a> |
| 1410 |
</dd> |
| 1411 |
<dd class="break"></dd> |
| 1412 |
<dt id="section-1.2-2.7">FEC:</dt> |
| 1413 |
<dd style="margin-left: 5.0em" id="section-1.2-2.8">Forward Error Correction<a href="#section-1.2-2.8" class="pilcrow">¶</a> |
| 1414 |
</dd> |
| 1415 |
<dd class="break"></dd> |
| 1416 |
<dt id="section-1.2-2.9">LPC:</dt> |
| 1417 |
<dd style="margin-left: 5.0em" id="section-1.2-2.10">Linear-Predictive Coding<a href="#section-1.2-2.10" class="pilcrow">¶</a> |
| 1418 |
</dd> |
| 1419 |
<dd class="break"></dd> |
| 1420 |
<dt id="section-1.2-2.11">LSB:</dt> |
| 1421 |
<dd style="margin-left: 5.0em" id="section-1.2-2.12">Least Significant Bit<a href="#section-1.2-2.12" class="pilcrow">¶</a> |
| 1422 |
</dd> |
| 1423 |
<dd class="break"></dd> |
| 1424 |
<dt id="section-1.2-2.13">MELP:</dt> |
| 1425 |
<dd style="margin-left: 5.0em" id="section-1.2-2.14">Mixed Excitation Linear Prediction<a href="#section-1.2-2.14" class="pilcrow">¶</a> |
| 1426 |
</dd> |
| 1427 |
<dd class="break"></dd> |
| 1428 |
<dt id="section-1.2-2.15">MELPe:</dt> |
| 1429 |
<dd style="margin-left: 5.0em" id="section-1.2-2.16">Mixed Excitation Linear Prediction Enhanced<a href="#section-1.2-2.16" class="pilcrow">¶</a> |
| 1430 |
</dd> |
| 1431 |
<dd class="break"></dd> |
| 1432 |
<dt id="section-1.2-2.17">MSB:</dt> |
| 1433 |
<dd style="margin-left: 5.0em" id="section-1.2-2.18">Most Significant Bit<a href="#section-1.2-2.18" class="pilcrow">¶</a> |
| 1434 |
</dd> |
| 1435 |
<dd class="break"></dd> |
| 1436 |
<dt id="section-1.2-2.19">MTC:</dt> |
| 1437 |
<dd style="margin-left: 5.0em" id="section-1.2-2.20">Modified Count<a href="#section-1.2-2.20" class="pilcrow">¶</a> |
| 1438 |
</dd> |
| 1439 |
<dd class="break"></dd> |
| 1440 |
<dt id="section-1.2-2.21">NATO:</dt> |
| 1441 |
<dd style="margin-left: 5.0em" id="section-1.2-2.22">North American Treaty Organization<a href="#section-1.2-2.22" class="pilcrow">¶</a> |
| 1442 |
</dd> |
| 1443 |
<dd class="break"></dd> |
| 1444 |
<dt id="section-1.2-2.23">NRL:</dt> |
| 1445 |
<dd style="margin-left: 5.0em" id="section-1.2-2.24">Naval Research Lab<a href="#section-1.2-2.24" class="pilcrow">¶</a> |
| 1446 |
</dd> |
| 1447 |
<dd class="break"></dd> |
| 1448 |
<dt id="section-1.2-2.25">PLC:</dt> |
| 1449 |
<dd style="margin-left: 5.0em" id="section-1.2-2.26">Packet Loss Concealment<a href="#section-1.2-2.26" class="pilcrow">¶</a> |
| 1450 |
</dd> |
| 1451 |
<dd class="break"></dd> |
| 1452 |
<dt id="section-1.2-2.27">SAVP:</dt> |
| 1453 |
<dd style="margin-left: 5.0em" id="section-1.2-2.28">Secure Audio/Video Profile<a href="#section-1.2-2.28" class="pilcrow">¶</a> |
| 1454 |
</dd> |
| 1455 |
<dd class="break"></dd> |
| 1456 |
<dt id="section-1.2-2.29">SAVPF:</dt> |
| 1457 |
<dd style="margin-left: 5.0em" id="section-1.2-2.30">Secure Audio/Video Profile Feedback<a href="#section-1.2-2.30" class="pilcrow">¶</a> |
| 1458 |
</dd> |
| 1459 |
<dd class="break"></dd> |
| 1460 |
<dt id="section-1.2-2.31">SDP:</dt> |
| 1461 |
<dd style="margin-left: 5.0em" id="section-1.2-2.32">Session Description Protocol<a href="#section-1.2-2.32" class="pilcrow">¶</a> |
| 1462 |
</dd> |
| 1463 |
<dd class="break"></dd> |
| 1464 |
<dt id="section-1.2-2.33">SSRC:</dt> |
| 1465 |
<dd style="margin-left: 5.0em" id="section-1.2-2.34">Synchronization Source<a href="#section-1.2-2.34" class="pilcrow">¶</a> |
| 1466 |
</dd> |
| 1467 |
<dd class="break"></dd> |
| 1468 |
<dt id="section-1.2-2.35">SRTP:</dt> |
| 1469 |
<dd style="margin-left: 5.0em" id="section-1.2-2.36">Secure Real-Time Transport Protocol<a href="#section-1.2-2.36" class="pilcrow">¶</a> |
| 1470 |
</dd> |
| 1471 |
<dd class="break"></dd> |
| 1472 |
<dt id="section-1.2-2.37">TSVCIS:</dt> |
| 1473 |
<dd style="margin-left: 5.0em" id="section-1.2-2.38">Tactical Secure Voice Cryptographic Interoperability Specification<a href="#section-1.2-2.38" class="pilcrow">¶</a> |
| 1474 |
</dd> |
| 1475 |
<dd class="break"></dd> |
| 1476 |
<dt id="section-1.2-2.39">VAD:</dt> |
| 1477 |
<dd style="margin-left: 5.0em" id="section-1.2-2.40">Voice Activity Detect<a href="#section-1.2-2.40" class="pilcrow">¶</a> |
| 1478 |
</dd> |
| 1479 |
<dd class="break"></dd> |
| 1480 |
<dt id="section-1.2-2.41">VDR:</dt> |
| 1481 |
<dd style="margin-left: 5.0em" id="section-1.2-2.42">Variable Date Rate<a href="#section-1.2-2.42" class="pilcrow">¶</a> |
| 1482 |
</dd> |
| 1483 |
<dd class="break"></dd> |
| 1484 |
</dl> |
| 1485 |
</section> |
| 1486 |
</div> |
| 1487 |
</section> |
| 1488 |
</div> |
| 1489 |
<div id="sect-2"> |
| 1490 |
<section id="section-2"> |
| 1491 |
<h2 id="name-background"> |
| 1492 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-background" class="section-name selfRef">Background</a> |
| 1493 |
</h2> |
| 1494 |
<p id="section-2-1"> |
| 1495 |
The MELP speech coder was developed by the US military as an upgrade |
| 1496 |
from the LPC-based CELP standard vocoder for low-bitrate |
| 1497 |
communications <span>[<a href="#MELP" class="xref">MELP</a>]</span>. ("LPC" stands for "Linear-Predictive Coding", |
| 1498 |
and "CELP" stands for "Code-Excited Linear Prediction".) MELP was |
| 1499 |
further enhanced and subsequently adopted by NATO as "MELPe" for use by |
| 1500 |
its members and Partnership for Peace countries for military and |
| 1501 |
other governmental communications as international NATO Standard |
| 1502 |
STANAG 4591 <span>[<a href="#MELPE" class="xref">MELPE</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1503 |
<p id="section-2-2"> |
| 1504 |
The Tactical Secure Voice Cryptographic Interoperability |
| 1505 |
Specification (TSVCIS) is a specification written by the Tactical |
| 1506 |
Secure Voice Working Group (TSVWG) to enable all modern tactical |
| 1507 |
secure voice devices to be interoperable across the US Department of |
| 1508 |
Defense <span>[<a href="#TSVCIS" class="xref">TSVCIS</a>]</span>. One of the most important aspects is that the |
| 1509 |
voice modes defined in TSVCIS are based on specific fixed rates of the Naval Research Lab's (NRL's) Variable Date Rate (VDR) Vocoder, which |
| 1510 |
uses the MELPe standard as its base <span>[<a href="#NRLVDR" class="xref">NRLVDR</a>]</span>. A complete TSVCIS |
| 1511 |
speech frame consists of MELPe speech parameters and corresponding |
| 1512 |
TSVCIS augmented speech data.<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1513 |
<p id="section-2-3"> |
| 1514 |
In addition to the augmented speech data, the TSVCIS specification |
| 1515 |
identifies which speech coder and framing bits are to be encrypted |
| 1516 |
and how they are protected by forward error correction (FEC) |
| 1517 |
techniques (using block codes). At the RTP transport layer, only the |
| 1518 |
speech coder-related bits need to be considered and are conveyed in |
| 1519 |
unencrypted form. In most IP-based network deployments, standard |
| 1520 |
link encryption methods (Secure Real-Time Transport Protocol (SRTP), VPNs, FIPS 140 link encryptors, or Type |
| 1521 |
1 Ethernet encryptors) would be used to secure the RTP speech |
| 1522 |
contents.<a href="#section-2-3" class="pilcrow">¶</a></p> |
| 1523 |
<p id="section-2-4"> |
| 1524 |
TSVCIS augmented speech data is derived from the signal processing |
| 1525 |
and data generated by the MELPe speech coder. For the |
| 1526 |
purposes of this specification, only the general parameter nature of |
| 1527 |
TSVCIS will be characterized. Depending on the bandwidth available |
| 1528 |
(and FEC requirements), a varying number of TSVCIS-specific speech |
| 1529 |
coder parameters need to be transported. These are first byte-packed |
| 1530 |
and then conveyed from encoder to decoder.<a href="#section-2-4" class="pilcrow">¶</a></p> |
| 1531 |
<p id="section-2-5"> |
| 1532 |
Byte packing of TSVCIS speech data into packed parameters is |
| 1533 |
processed as per the following example, where<a href="#section-2-5" class="pilcrow">¶</a></p> |
| 1534 |
<span class="break"></span><dl class="dlParallel" id="section-2-6"> |
| 1535 |
<dt id="section-2-6.1">Three-bit field:</dt> |
| 1536 |
<dd id="section-2-6.2">Bits A, B, and C (A is MSB; C is LSB)<a href="#section-2-6.2" class="pilcrow">¶</a> |
| 1537 |
</dd> |
| 1538 |
<dd class="break"></dd> |
| 1539 |
<dt id="section-2-6.3">Five-bit field:</dt> |
| 1540 |
<dd id="section-2-6.4">Bits D, E, F, G, and H (D is MSB; H is LSB)<a href="#section-2-6.4" class="pilcrow">¶</a> |
| 1541 |
</dd> |
| 1542 |
<dd class="break"></dd> |
| 1543 |
</dl> |
| 1544 |
<div class="artwork art-text alignLeft" id="section-2-7"> |
| 1545 |
<pre> |
| 1546 |
MSB LSB |
| 1547 |
0 1 2 3 4 5 6 7 |
| 1548 |
+------+------+------+------+------+------+------+------+ |
| 1549 |
| H | G | F | E | D | C | B | A | |
| 1550 |
+------+------+------+------+------+------+------+------+ |
| 1551 |
</pre><a href="#section-2-7" class="pilcrow">¶</a> |
| 1552 |
</div> |
| 1553 |
<p id="section-2-8"> |
| 1554 |
This packing method places the three-bit field "first" in the lowest |
| 1555 |
bits followed by the next five-bit field. Parameters may be split |
| 1556 |
between octets with the most significant bits in the earlier octet. |
| 1557 |
Any unfilled bits in the last octet <span class="bcp14">MUST</span> be filled with |
| 1558 |
zero.<a href="#section-2-8" class="pilcrow">¶</a></p> |
| 1559 |
<p id="section-2-9"> |
| 1560 |
In order to accommodate a varying amount of TSVCIS augmented speech |
| 1561 |
data, an octet count specifies the number of octets representing |
| 1562 |
the TSVCIS packed parameters. The encoding to do so is presented in |
| 1563 |
<a href="#sect-3.2" class="xref">Section 3.2</a>. TSVCIS specifically uses the NRL VDR in two |
| 1564 |
configurations with a fixed set of 15 and 35 packed octet |
| 1565 |
parameters in a standardized order <span>[<a href="#TSVCIS" class="xref">TSVCIS</a>]</span>.<a href="#section-2-9" class="pilcrow">¶</a></p> |
| 1566 |
</section> |
| 1567 |
</div> |
| 1568 |
<div id="sect-3"> |
| 1569 |
<section id="section-3"> |
| 1570 |
<h2 id="name-payload-format"> |
| 1571 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-payload-format" class="section-name selfRef">Payload Format</a> |
| 1572 |
</h2> |
| 1573 |
<p id="section-3-1"> |
| 1574 |
The TSVCIS codec augments the standard MELP 2400, 1200, and 600 |
| 1575 |
bitrates and hence uses 22.5, 67.5, or 90 ms frames with a sampling |
| 1576 |
rate clock of 8 kHz, so the RTP timestamp <span class="bcp14">MUST</span> be in units of 1/8000 |
| 1577 |
of a second.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1578 |
<p id="section-3-2"> |
| 1579 |
The RTP payload for TSVCIS has the format shown in <a href="#fig-1" class="xref">Figure 1</a>. No |
| 1580 |
additional header specific to this payload format is needed. This |
| 1581 |
format is intended for situations where the sender and the receiver |
| 1582 |
send one or more codec data frames per packet.<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1583 |
<span id="name-packet-format-diagram"></span><div id="fig-1"> |
| 1584 |
<figure id="figure-1"> |
| 1585 |
<div class="artwork art-text alignLeft" id="section-3-3.1"> |
| 1586 |
<pre> |
| 1587 |
0 1 2 3 |
| 1588 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1589 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1590 |
| RTP Header | |
| 1591 |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ |
| 1592 |
| | |
| 1593 |
+ one or more frames of TSVCIS | |
| 1594 |
| | |
| 1595 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1596 |
</pre> |
| 1597 |
</div> |
| 1598 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 1599 |
<a href="#name-packet-format-diagram" class="selfRef">Packet Format Diagram</a> |
| 1600 |
</figcaption></figure> |
| 1601 |
</div> |
| 1602 |
<p id="section-3-4"> |
| 1603 |
The RTP header of the packetized encoded TSVCIS speech has the |
| 1604 |
expected values as described in <span>[<a href="#RFC3550" class="xref">RFC3550</a>]</span>. The usage of the M bit |
| 1605 |
<span class="bcp14">SHOULD</span> be as specified in the applicable RTP profile -- for example, |
| 1606 |
<span>[<a href="#RFC3551" class="xref">RFC3551</a>]</span> specifies that if the sender does not |
| 1607 |
suppress silence (i.e., sends a frame on every frame interval), the |
| 1608 |
M bit will always be zero. When more than one codec data frame is |
| 1609 |
present in a single RTP packet, the timestamp specified is that of |
| 1610 |
the oldest data frame represented in the RTP packet.<a href="#section-3-4" class="pilcrow">¶</a></p> |
| 1611 |
<p id="section-3-5"> |
| 1612 |
The assignment of an RTP payload type for this new packet format is |
| 1613 |
outside the scope of this document and will not be specified here. It |
| 1614 |
is expected that the RTP profile for a particular class of |
| 1615 |
applications will assign a payload type for this encoding; if that |
| 1616 |
is not done, then a payload type in the dynamic range shall be chosen |
| 1617 |
by the sender.<a href="#section-3-5" class="pilcrow">¶</a></p> |
| 1618 |
<div id="sect-3.1"> |
| 1619 |
<section id="section-3.1"> |
| 1620 |
<h3 id="name-melpe-bitstream-definitions"> |
| 1621 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-melpe-bitstream-definitions" class="section-name selfRef">MELPe Bitstream Definitions</a> |
| 1622 |
</h3> |
| 1623 |
<p id="section-3.1-1"> |
| 1624 |
The TSVCIS speech coder includes all three MELPe coder rates used as |
| 1625 |
base speech parameters or as speech coders for bandwidth-restricted |
| 1626 |
links. RTP packetization of MELPe follows <span>[<a href="#RFC8130" class="xref">RFC8130</a>]</span> and is repeated |
| 1627 |
here for all three MELPe rates <span>[<a href="#RFC8130" class="xref">RFC8130</a>]</span>, with its recommendations now |
| 1628 |
regarded as requirements. The bits previously labeled as RSVA, RSVB, |
| 1629 |
and RSVC in <span>[<a href="#RFC8130" class="xref">RFC8130</a>]</span> <span class="bcp14">SHOULD</span> be filled with |
| 1630 |
rate code bits CODA, CODB, |
| 1631 |
and CODC, as shown in <a href="#tab-1" class="xref">Table 1</a> (compatible with Table 7 in <span><a href="https://www.rfc-editor.org/rfc/rfc8130#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8130" class="xref">RFC8130</a>]</span>).<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1632 |
<span id="name-tsvcis-melpe-frame-bitrate-"></span><div id="tab-1"> |
| 1633 |
<table class="center" id="table-1"> |
| 1634 |
<caption> |
| 1635 |
<a href="#table-1" class="selfRef">Table 1</a>: |
| 1636 |
<a href="#name-tsvcis-melpe-frame-bitrate-" class="selfRef">TSVCIS/MELPe Frame Bitrate Indicators and Frame Length</a> |
| 1637 |
</caption> |
| 1638 |
<thead> |
| 1639 |
<tr> |
| 1640 |
<th class="text-left" rowspan="1" colspan="1">Coder Bitrate</th> |
| 1641 |
<th class="text-left" rowspan="1" colspan="1">CODA</th> |
| 1642 |
<th class="text-left" rowspan="1" colspan="1">CODB</th> |
| 1643 |
<th class="text-left" rowspan="1" colspan="1">CODC</th> |
| 1644 |
<th class="text-left" rowspan="1" colspan="1">Length</th> |
| 1645 |
</tr> |
| 1646 |
</thead> |
| 1647 |
<tbody> |
| 1648 |
<tr> |
| 1649 |
<td class="text-left" rowspan="1" colspan="1">2400 bps</td> |
| 1650 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1651 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1652 |
<td class="text-left" rowspan="1" colspan="1">N/A</td> |
| 1653 |
<td class="text-left" rowspan="1" colspan="1">7</td> |
| 1654 |
</tr> |
| 1655 |
<tr> |
| 1656 |
<td class="text-left" rowspan="1" colspan="1">1200 bps</td> |
| 1657 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1658 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1659 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1660 |
<td class="text-left" rowspan="1" colspan="1">11</td> |
| 1661 |
</tr> |
| 1662 |
<tr> |
| 1663 |
<td class="text-left" rowspan="1" colspan="1">600 bps</td> |
| 1664 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1665 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1666 |
<td class="text-left" rowspan="1" colspan="1">N/A</td> |
| 1667 |
<td class="text-left" rowspan="1" colspan="1">7</td> |
| 1668 |
</tr> |
| 1669 |
<tr> |
| 1670 |
<td class="text-left" rowspan="1" colspan="1">Comfort Noise</td> |
| 1671 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1672 |
<td class="text-left" rowspan="1" colspan="1">0</td> |
| 1673 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1674 |
<td class="text-left" rowspan="1" colspan="1">2</td> |
| 1675 |
</tr> |
| 1676 |
<tr> |
| 1677 |
<td class="text-left" rowspan="1" colspan="1">TSVCIS Data</td> |
| 1678 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1679 |
<td class="text-left" rowspan="1" colspan="1">1</td> |
| 1680 |
<td class="text-left" rowspan="1" colspan="1">N/A</td> |
| 1681 |
<td class="text-left" rowspan="1" colspan="1">var.</td> |
| 1682 |
</tr> |
| 1683 |
</tbody> |
| 1684 |
</table> |
| 1685 |
</div> |
| 1686 |
<p id="section-3.1-3"> |
| 1687 |
The total number of bits used to describe one MELPe frame of 2400 bps |
| 1688 |
speech is 54, which fits in 7 octets (with two rate code bits). For |
| 1689 |
MELPe 1200 bps speech, the total number of bits used is 81, which |
| 1690 |
fits in 11 octets (with three rate code bits and four unused bits). |
| 1691 |
For MELPe 600 bps speech, the total number of bits used is 54, which |
| 1692 |
fits in 7 octets (with two rate code bits). The comfort noise frame |
| 1693 |
consists of 13 bits, which fits in 2 octets (with three rate code |
| 1694 |
bits). TSVCIS packed parameters will use the last code combination |
| 1695 |
in a trailing byte as discussed in <a href="#sect-3.2" class="xref">Section 3.2</a>.<a href="#section-3.1-3" class="pilcrow">¶</a></p> |
| 1696 |
<p id="section-3.1-4"> |
| 1697 |
It should be noted that CODB for MELPe 600 bps mode <span class="bcp14">MAY</span> deviate from |
| 1698 |
the value in <a href="#tab-1" class="xref">Table 1</a> when bit 55 is used as an alternating 1/0 |
| 1699 |
end-to-end framing bit. Frame decoding would remain distinct as CODA |
| 1700 |
being zero on its own would indicate a 7-byte frame for either a 2400 |
| 1701 |
or 600 bps rate, and the use of 600 bps speech coding could be deduced |
| 1702 |
from the RTP timestamp (and anticipated by the Session Description Protocol |
| 1703 |
(SDP) negotiations).<a href="#section-3.1-4" class="pilcrow">¶</a></p> |
| 1704 |
<div id="sect-3.1.1"> |
| 1705 |
<section id="section-3.1.1"> |
| 1706 |
<h4 id="name-2400-bps-bitstream-structur"> |
| 1707 |
<a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-2400-bps-bitstream-structur" class="section-name selfRef">2400 bps Bitstream Structure</a> |
| 1708 |
</h4> |
| 1709 |
<p id="section-3.1.1-1"> |
| 1710 |
The 2400 bps MELPe RTP payload is constructed as per <a href="#fig-2" class="xref">Figure 2</a>. Note |
| 1711 |
that CODA <span class="bcp14">MUST</span> be filled with 0 and CODB <span class="bcp14">SHOULD</span> be filled with 0 as |
| 1712 |
per <a href="#sect-3.1" class="xref">Section 3.1</a>. CODB <span class="bcp14">MAY</span> contain an end-to-end framing bit if |
| 1713 |
required by the endpoints.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p> |
| 1714 |
<span id="name-packed-melpe-2400-bps-paylo"></span><div id="fig-2"> |
| 1715 |
<figure id="figure-2"> |
| 1716 |
<div class="artwork art-text alignLeft" id="section-3.1.1-2.1"> |
| 1717 |
<pre> |
| 1718 |
MSB LSB |
| 1719 |
0 1 2 3 4 5 6 7 |
| 1720 |
+------+------+------+------+------+------+------+------+ |
| 1721 |
| B_08 | B_07 | B_06 | B_05 | B_04 | B_03 | B_02 | B_01 | |
| 1722 |
+------+------+------+------+------+------+------+------+ |
| 1723 |
| B_16 | B_15 | B_14 | B_13 | B_12 | B_11 | B_10 | B_09 | |
| 1724 |
+------+------+------+------+------+------+------+------+ |
| 1725 |
| B_24 | B_23 | B_22 | B_21 | B_20 | B_19 | B_18 | B_17 | |
| 1726 |
+------+------+------+------+------+------+------+------+ |
| 1727 |
| B_32 | B_31 | B_30 | B_29 | B_28 | B_27 | B_26 | B_25 | |
| 1728 |
+------+------+------+------+------+------+------+------+ |
| 1729 |
| B_40 | B_39 | B_38 | B_37 | B_36 | B_35 | B_34 | B_33 | |
| 1730 |
+------+------+------+------+------+------+------+------+ |
| 1731 |
| B_48 | B_47 | B_46 | B_45 | B_44 | B_43 | B_42 | B_41 | |
| 1732 |
+------+------+------+------+------+------+------+------+ |
| 1733 |
| CODA | CODB | B_54 | B_53 | B_52 | B_51 | B_50 | B_49 | |
| 1734 |
+------+------+------+------+------+------+------+------+ |
| 1735 |
</pre> |
| 1736 |
</div> |
| 1737 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 1738 |
<a href="#name-packed-melpe-2400-bps-paylo" class="selfRef">Packed MELPe 2400 bps Payload Octets</a> |
| 1739 |
</figcaption></figure> |
| 1740 |
</div> |
| 1741 |
</section> |
| 1742 |
</div> |
| 1743 |
<div id="sect-3.1.2"> |
| 1744 |
<section id="section-3.1.2"> |
| 1745 |
<h4 id="name-1200-bps-bitstream-structur"> |
| 1746 |
<a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-1200-bps-bitstream-structur" class="section-name selfRef">1200 bps Bitstream Structure</a> |
| 1747 |
</h4> |
| 1748 |
<p id="section-3.1.2-1"> |
| 1749 |
The 1200 bps MELPe RTP payload is constructed as per <a href="#fig-3" class="xref">Figure 3</a>. Note |
| 1750 |
that CODA, CODB, and CODC <span class="bcp14">MUST</span> be filled with 1, 0, and 0, |
| 1751 |
respectively, as per <a href="#sect-3.1" class="xref">Section 3.1</a>. RSV0 <span class="bcp14">MUST</span> be coded as 0.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p> |
| 1752 |
<span id="name-packed-melpe-1200-bps-paylo"></span><div id="fig-3"> |
| 1753 |
<figure id="figure-3"> |
| 1754 |
<div class="artwork art-text alignLeft" id="section-3.1.2-2.1"> |
| 1755 |
<pre> |
| 1756 |
MSB LSB |
| 1757 |
0 1 2 3 4 5 6 7 |
| 1758 |
+------+------+------+------+------+------+------+------+ |
| 1759 |
| B_08 | B_07 | B_06 | B_05 | B_04 | B_03 | B_02 | B_01 | |
| 1760 |
+------+------+------+------+------+------+------+------+ |
| 1761 |
| B_16 | B_15 | B_14 | B_13 | B_12 | B_11 | B_10 | B_09 | |
| 1762 |
+------+------+------+------+------+------+------+------+ |
| 1763 |
| B_24 | B_23 | B_22 | B_21 | B_20 | B_19 | B_18 | B_17 | |
| 1764 |
+------+------+------+------+------+------+------+------+ |
| 1765 |
| B_32 | B_31 | B_30 | B_29 | B_28 | B_27 | B_26 | B_25 | |
| 1766 |
+------+------+------+------+------+------+------+------+ |
| 1767 |
| B_40 | B_39 | B_38 | B_37 | B_36 | B_35 | B_34 | B_33 | |
| 1768 |
+------+------+------+------+------+------+------+------+ |
| 1769 |
| B_48 | B_47 | B_46 | B_45 | B_44 | B_43 | B_42 | B_41 | |
| 1770 |
+------+------+------+------+------+------+------+------+ |
| 1771 |
| B_56 | B_55 | B_54 | B_53 | B_52 | B_51 | B_50 | B_49 | |
| 1772 |
+------+------+------+------+------+------+------+------+ |
| 1773 |
| B_64 | B_63 | B_62 | B_61 | B_60 | B_59 | B_58 | B_57 | |
| 1774 |
+------+------+------+------+------+------+------+------+ |
| 1775 |
| B_72 | B_71 | B_70 | B_69 | B_68 | B_67 | B_66 | B_65 | |
| 1776 |
+------+------+------+------+------+------+------+------+ |
| 1777 |
| B_80 | B_79 | B_78 | B_77 | B_76 | B_75 | B_74 | B_73 | |
| 1778 |
+------+------+------+------+------+------+------+------+ |
| 1779 |
| CODA | CODB | CODC | RSV0 | RSV0 | RSV0 | RSV0 | B_81 | |
| 1780 |
+------+------+------+------+------+------+------+------+ |
| 1781 |
</pre> |
| 1782 |
</div> |
| 1783 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 1784 |
<a href="#name-packed-melpe-1200-bps-paylo" class="selfRef">Packed MELPe 1200 bps Payload Octets</a> |
| 1785 |
</figcaption></figure> |
| 1786 |
</div> |
| 1787 |
</section> |
| 1788 |
</div> |
| 1789 |
<div id="sect-3.1.3"> |
| 1790 |
<section id="section-3.1.3"> |
| 1791 |
<h4 id="name-600-bps-bitstream-structure"> |
| 1792 |
<a href="#section-3.1.3" class="section-number selfRef">3.1.3. </a><a href="#name-600-bps-bitstream-structure" class="section-name selfRef">600 bps Bitstream Structure</a> |
| 1793 |
</h4> |
| 1794 |
<p id="section-3.1.3-1"> |
| 1795 |
The 600 bps MELPe RTP payload is constructed as per <a href="#fig-4" class="xref">Figure 4</a>. Note |
| 1796 |
CODA <span class="bcp14">MUST</span> be filled with 0 and CODB <span class="bcp14">SHOULD</span> be filled with 1 as per |
| 1797 |
<a href="#sect-3.1" class="xref">Section 3.1</a>. CODB <span class="bcp14">MAY</span> contain an end-to-end framing bit if required |
| 1798 |
by the endpoints.<a href="#section-3.1.3-1" class="pilcrow">¶</a></p> |
| 1799 |
<span id="name-packed-melpe-600-bps-payloa"></span><div id="fig-4"> |
| 1800 |
<figure id="figure-4"> |
| 1801 |
<div class="artwork art-text alignLeft" id="section-3.1.3-2.1"> |
| 1802 |
<pre> |
| 1803 |
MSB LSB |
| 1804 |
0 1 2 3 4 5 6 7 |
| 1805 |
+------+------+------+------+------+------+------+------+ |
| 1806 |
| B_08 | B_07 | B_06 | B_05 | B_04 | B_03 | B_02 | B_01 | |
| 1807 |
+------+------+------+------+------+------+------+------+ |
| 1808 |
| B_16 | B_15 | B_14 | B_13 | B_12 | B_11 | B_10 | B_09 | |
| 1809 |
+------+------+------+------+------+------+------+------+ |
| 1810 |
| B_24 | B_23 | B_22 | B_21 | B_20 | B_19 | B_18 | B_17 | |
| 1811 |
+------+------+------+------+------+------+------+------+ |
| 1812 |
| B_32 | B_31 | B_30 | B_29 | B_28 | B_27 | B_26 | B_25 | |
| 1813 |
+------+------+------+------+------+------+------+------+ |
| 1814 |
| B_40 | B_39 | B_38 | B_37 | B_36 | B_35 | B_34 | B_33 | |
| 1815 |
+------+------+------+------+------+------+------+------+ |
| 1816 |
| B_48 | B_47 | B_46 | B_45 | B_44 | B_43 | B_42 | B_41 | |
| 1817 |
+------+------+------+------+------+------+------+------+ |
| 1818 |
| CODA | CODB | B_54 | B_53 | B_52 | B_51 | B_50 | B_49 | |
| 1819 |
+------+------+------+------+------+------+------+------+ |
| 1820 |
</pre> |
| 1821 |
</div> |
| 1822 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 1823 |
<a href="#name-packed-melpe-600-bps-payloa" class="selfRef">Packed MELPe 600 bps Payload Octets</a> |
| 1824 |
</figcaption></figure> |
| 1825 |
</div> |
| 1826 |
</section> |
| 1827 |
</div> |
| 1828 |
<div id="sect-3.1.4"> |
| 1829 |
<section id="section-3.1.4"> |
| 1830 |
<h4 id="name-comfort-noise-bitstream-def"> |
| 1831 |
<a href="#section-3.1.4" class="section-number selfRef">3.1.4. </a><a href="#name-comfort-noise-bitstream-def" class="section-name selfRef">Comfort Noise Bitstream Definition</a> |
| 1832 |
</h4> |
| 1833 |
<p id="section-3.1.4-1"> |
| 1834 |
The comfort noise MELPe RTP payload is constructed as per <a href="#fig-5" class="xref">Figure 5</a>. |
| 1835 |
Note that CODA, CODB, and CODC <span class="bcp14">MUST</span> be filled with 1, 0, and 1, |
| 1836 |
respectively, as per <a href="#sect-3.1" class="xref">Section 3.1</a>.<a href="#section-3.1.4-1" class="pilcrow">¶</a></p> |
| 1837 |
<span id="name-packed-melpe-comfort-noise-"></span><div id="fig-5"> |
| 1838 |
<figure id="figure-5"> |
| 1839 |
<div class="artwork art-text alignLeft" id="section-3.1.4-2.1"> |
| 1840 |
<pre> |
| 1841 |
MSB LSB |
| 1842 |
0 1 2 3 4 5 6 7 |
| 1843 |
+------+------+------+------+------+------+------+------+ |
| 1844 |
| B_08 | B_07 | B_06 | B_05 | B_04 | B_03 | B_02 | B_01 | |
| 1845 |
+------+------+------+------+------+------+------+------+ |
| 1846 |
| CODA | CODB | CODC | B_13 | B_12 | B_11 | B_10 | B_09 | |
| 1847 |
+------+------+------+------+------+------+------+------+ |
| 1848 |
</pre> |
| 1849 |
</div> |
| 1850 |
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>: |
| 1851 |
<a href="#name-packed-melpe-comfort-noise-" class="selfRef">Packed MELPe Comfort Noise Payload Octets</a> |
| 1852 |
</figcaption></figure> |
| 1853 |
</div> |
| 1854 |
</section> |
| 1855 |
</div> |
| 1856 |
</section> |
| 1857 |
</div> |
| 1858 |
<div id="sect-3.2"> |
| 1859 |
<section id="section-3.2"> |
| 1860 |
<h3 id="name-tsvcis-bitstream-definition"> |
| 1861 |
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-tsvcis-bitstream-definition" class="section-name selfRef">TSVCIS Bitstream Definition</a> |
| 1862 |
</h3> |
| 1863 |
<p id="section-3.2-1"> |
| 1864 |
The TSVCIS augmented speech data as packed parameters <span class="bcp14">MUST</span> be placed |
| 1865 |
immediately after a corresponding MELPe 2400 bps payload in the same |
| 1866 |
RTP packet. The packed parameters are counted in octets (TC). The |
| 1867 |
preferred placement <span class="bcp14">SHOULD</span> be used for TSVCIS payloads with TC less |
| 1868 |
than or equal to 77 octets; this is shown in <a href="#fig-6" class="xref">Figure 6</a>. In the |
| 1869 |
preferred placement, a single trailing octet <span class="bcp14">SHALL</span> be appended to |
| 1870 |
include a two-bit rate code, CODA and CODB (both bits set to one), |
| 1871 |
and a six-bit modified count (MTC). The special modified count value |
| 1872 |
of all ones (representing an MTC value of 63) <span class="bcp14">SHALL NOT</span> be used for |
| 1873 |
this format as it is used as the indicator for the alternate packing |
| 1874 |
format shown next. In a standard implementation, the TSVCIS speech |
| 1875 |
coder uses a minimum of 15 octets for parameters in octet packed |
| 1876 |
form. The modified count (MTC) <span class="bcp14">MUST</span> be reduced by 15 from the full |
| 1877 |
octet count (TC). Computed MTC = TC-15. This accommodates a maximum |
| 1878 |
of 77 parameter octets (the maximum value of MTC is 62; 77 is the sum of |
| 1879 |
62+15).<a href="#section-3.2-1" class="pilcrow">¶</a></p> |
| 1880 |
<span id="name-preferred-packed-tsvcis-pay"></span><div id="fig-6"> |
| 1881 |
<figure id="figure-6"> |
| 1882 |
<div class="artwork art-text alignLeft" id="section-3.2-2.1"> |
| 1883 |
<pre> |
| 1884 |
MSB LSB |
| 1885 |
0 1 2 3 4 5 6 7 |
| 1886 |
+------+------+------+------+------+------+------+------+ |
| 1887 |
1 | T008 | T007 | T006 | T005 | T004 | T003 | T002 | T001 | |
| 1888 |
+------+------+------+------+------+------+------+------+ |
| 1889 |
2 | T016 | T015 | T014 | T013 | T012 | T011 | T010 | T009 | |
| 1890 |
+------+------+------+------+------+------+------+------+ |
| 1891 |
3 | T024 | T023 | T022 | T021 | T020 | T019 | T018 | T017 | |
| 1892 |
+------+------+------+------+------+------+------+------+ |
| 1893 |
4 | T032 | T031 | T030 | T029 | T028 | T027 | T026 | T025 | |
| 1894 |
+------+------+------+------+------+------+------+------+ |
| 1895 |
5 | T040 | T039 | T038 | T037 | T036 | T035 | T034 | T033 | |
| 1896 |
+------+------+------+------+------+------+------+------+ |
| 1897 |
6 | T048 | T047 | T046 | T045 | T044 | T043 | T042 | T041 | |
| 1898 |
+------+------+------+------+------+------+------+------+ |
| 1899 |
7 | TO56 | TO55 | T054 | T053 | T052 | T051 | T050 | T049 | |
| 1900 |
+------+------+------+------+------+------+------+------+ |
| 1901 |
8 | T064 | T063 | T062 | T061 | T060 | T059 | T058 | T057 | |
| 1902 |
+------+------+------+------+------+------+------+------+ |
| 1903 |
9 | T072 | T071 | T070 | T069 | T068 | T067 | T066 | T065 | |
| 1904 |
+------+------+------+------+------+------+------+------+ |
| 1905 |
10 | T080 | T079 | T078 | T077 | T076 | T075 | T074 | T073 | |
| 1906 |
+------+------+------+------+------+------+------+------+ |
| 1907 |
11 | T088 | T087 | T086 | T085 | T084 | T083 | T082 | T081 | |
| 1908 |
+------+------+------+------+------+------+------+------+ |
| 1909 |
12 | TO96 | TO95 | T094 | T093 | T092 | T091 | T090 | T089 | |
| 1910 |
+------+------+------+------+------+------+------+------+ |
| 1911 |
13 | T104 | T103 | T102 | T101 | T100 | T099 | T098 | T097 | |
| 1912 |
+------+------+------+------+------+------+------+------+ |
| 1913 |
14 | T112 | T111 | T110 | T109 | T108 | T107 | T106 | T105 | |
| 1914 |
+------+------+------+------+------+------+------+------+ |
| 1915 |
15 | T120 | T119 | T118 | T117 | T116 | T115 | T114 | T113 | |
| 1916 |
+------+------+------+------+------+------+------+------+ |
| 1917 |
| . . . . | |
| 1918 |
+------+------+------+------+------+------+------+------+ |
| 1919 |
TC+1 | CODA | CODB | modified octet count | |
| 1920 |
+------+------+------+------+------+------+------+------+ |
| 1921 |
</pre> |
| 1922 |
</div> |
| 1923 |
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a>: |
| 1924 |
<a href="#name-preferred-packed-tsvcis-pay" class="selfRef">Preferred Packed TSVCIS Payload Octets</a> |
| 1925 |
</figcaption></figure> |
| 1926 |
</div> |
| 1927 |
<p id="section-3.2-3"> |
| 1928 |
In order to accommodate all other NRL VDR configurations, an |
| 1929 |
alternate parameter placement <span class="bcp14">MUST</span> use two trailing bytes as shown in |
| 1930 |
<a href="#fig-7" class="xref">Figure 7</a>. The last trailing byte <span class="bcp14">MUST</span> be filled with a two-bit rate |
| 1931 |
code, CODA and CODB (both bits set to one), and its six-bit count |
| 1932 |
field <span class="bcp14">MUST</span> be filled with ones. The second to last trailing byte |
| 1933 |
<span class="bcp14">MUST</span> contain the parameter count (TC) in octets (a value from 1 and |
| 1934 |
255, inclusive). The value of zero <span class="bcp14">SHALL</span> be considered as reserved.<a href="#section-3.2-3" class="pilcrow">¶</a></p> |
| 1935 |
<span id="name-length-unrestricted-packed-"></span><div id="fig-7"> |
| 1936 |
<figure id="figure-7"> |
| 1937 |
<div class="artwork art-text alignLeft" id="section-3.2-4.1"> |
| 1938 |
<pre> |
| 1939 |
MSB LSB |
| 1940 |
0 1 2 3 4 5 6 7 |
| 1941 |
+------+------+------+------+------+------+------+------+ |
| 1942 |
1 | T008 | T007 | T006 | T005 | T004 | T003 | T002 | T001 | |
| 1943 |
+------+------+------+------+------+------+------+------+ |
| 1944 |
2 | T016 | T015 | T014 | T013 | T012 | T011 | T010 | T009 | |
| 1945 |
+------+------+------+------+------+------+------+------+ |
| 1946 |
| . . . . | |
| 1947 |
+------+------+------+------+------+------+------+------+ |
| 1948 |
TC+1 | octet count | |
| 1949 |
+------+------+------+------+------+------+------+------+ |
| 1950 |
TC+2 | CODA | CODB | 1 | 1 | 1 | 1 | 1 | 1 | |
| 1951 |
+------+------+------+------+------+------+------+------+ |
| 1952 |
</pre> |
| 1953 |
</div> |
| 1954 |
<figcaption><a href="#figure-7" class="selfRef">Figure 7</a>: |
| 1955 |
<a href="#name-length-unrestricted-packed-" class="selfRef">Length Unrestricted Packed TSVCIS Payload Octets</a> |
| 1956 |
</figcaption></figure> |
| 1957 |
</div> |
| 1958 |
</section> |
| 1959 |
</div> |
| 1960 |
<div id="sect-3.3"> |
| 1961 |
<section id="section-3.3"> |
| 1962 |
<h3 id="name-multiple-tsvcis-frames-in-a"> |
| 1963 |
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-multiple-tsvcis-frames-in-a" class="section-name selfRef">Multiple TSVCIS Frames in an RTP Packet</a> |
| 1964 |
</h3> |
| 1965 |
<p id="section-3.3-1"> |
| 1966 |
A TSVCIS RTP packet payload consists of zero or more consecutive |
| 1967 |
TSVCIS coder frames (each consisting of MELPe 2400 and TSVCIS coder |
| 1968 |
data), with the oldest frame first, followed by zero or one MELPe |
| 1969 |
comfort noise frame. The presence of a comfort noise frame can be |
| 1970 |
determined by its rate code bits in its last octet.<a href="#section-3.3-1" class="pilcrow">¶</a></p> |
| 1971 |
<p id="section-3.3-2"> |
| 1972 |
The default packetization interval is one coder frame (22.5, 67.5, or |
| 1973 |
90 ms) according to the coder bitrate (2400, 1200, or 600 bps). For |
| 1974 |
some applications, a longer packetization interval is used to reduce |
| 1975 |
the packet rate.<a href="#section-3.3-2" class="pilcrow">¶</a></p> |
| 1976 |
<p id="section-3.3-3"> |
| 1977 |
A TSVCIS RTP packet without coder and comfort noise frames <span class="bcp14">MAY</span> be |
| 1978 |
used periodically by an endpoint to indicate connectivity by an |
| 1979 |
otherwise idle receiver.<a href="#section-3.3-3" class="pilcrow">¶</a></p> |
| 1980 |
<p id="section-3.3-4"> |
| 1981 |
TSVCIS coder frames in a single RTP packet <span class="bcp14">MAY</span> have varying TSVCIS |
| 1982 |
parameter octet counts. Its packed parameter octet count (length) is |
| 1983 |
indicated in the trailing byte(s). All MELPe frames in a single RTP |
| 1984 |
packet <span class="bcp14">MUST</span> be of the same coder bitrate. For all MELPe coder |
| 1985 |
frames, the coder rate bits in the trailing byte identify the |
| 1986 |
contents and length as per <a href="#tab-1" class="xref">Table 1</a>.<a href="#section-3.3-4" class="pilcrow">¶</a></p> |
| 1987 |
<p id="section-3.3-5"> |
| 1988 |
It is important to observe that senders have the following additional |
| 1989 |
restrictions:<a href="#section-3.3-5" class="pilcrow">¶</a></p> |
| 1990 |
<ul class="normal"> |
| 1991 |
<li class="normal" id="section-3.3-6.1">Senders <span class="bcp14">SHOULD NOT</span> include more TSVCIS or MELPe frames in a single |
| 1992 |
RTP packet than will fit in the MTU of the RTP transport protocol.<a href="#section-3.3-6.1" class="pilcrow">¶</a> |
| 1993 |
</li> |
| 1994 |
<li class="normal" id="section-3.3-6.2"> |
| 1995 |
Frames <span class="bcp14">MUST NOT</span> be split between RTP packets.<a href="#section-3.3-6.2" class="pilcrow">¶</a> |
| 1996 |
</li> |
| 1997 |
</ul> |
| 1998 |
<p id="section-3.3-7"> |
| 1999 |
It is <span class="bcp14">RECOMMENDED</span> that the number of frames contained within an RTP packet |
| 2000 |
be consistent with the application. For example, in telephony and other |
| 2001 |
real-time applications where delay is important, the fewer frames per |
| 2002 |
packet, the lower the delay. However, for bandwidth-constrained links or |
| 2003 |
delay-insensitive streaming messaging applications, more than one frame per |
| 2004 |
packet or many frames per packet would be acceptable.<a href="#section-3.3-7" class="pilcrow">¶</a></p> |
| 2005 |
<p id="section-3.3-8"> |
| 2006 |
Information describing the number of frames contained in an RTP |
| 2007 |
packet is not transmitted as part of the RTP payload. The way to |
| 2008 |
determine the number of TSVCIS/MELPe frames is to identify each frame |
| 2009 |
type and length, thereby counting the total number of octets within |
| 2010 |
the RTP packet.<a href="#section-3.3-8" class="pilcrow">¶</a></p> |
| 2011 |
</section> |
| 2012 |
</div> |
| 2013 |
<div id="sect-3.4"> |
| 2014 |
<section id="section-3.4"> |
| 2015 |
<h3 id="name-congestion-control-consider"> |
| 2016 |
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-congestion-control-consider" class="section-name selfRef">Congestion Control Considerations</a> |
| 2017 |
</h3> |
| 2018 |
<p id="section-3.4-1"> |
| 2019 |
The target bitrate of TSVCIS can be adjusted at any point in time, |
| 2020 |
thus allowing congestion management. Furthermore, the amount of |
| 2021 |
encoded speech or audio data encoded in a single packet can be used |
| 2022 |
for congestion control, since the packet rate is inversely |
| 2023 |
proportional to the packet duration. A lower packet transmission |
| 2024 |
rate reduces the amount of header overhead but at the same time |
| 2025 |
increases latency and loss sensitivity, so it ought to be used |
| 2026 |
with care.<a href="#section-3.4-1" class="pilcrow">¶</a></p> |
| 2027 |
<p id="section-3.4-2"> |
| 2028 |
Since UDP does not provide congestion control, applications that use |
| 2029 |
RTP over UDP <span class="bcp14">SHOULD</span> implement their own congestion control above the |
| 2030 |
UDP layer <span>[<a href="#RFC8085" class="xref">RFC8085</a>]</span> and <span class="bcp14">MAY</span> also implement a transport circuit |
| 2031 |
breaker <span>[<a href="#RFC8083" class="xref">RFC8083</a>]</span>. Work in the RMCAT Working Group <span>[<a href="#RMCAT" class="xref">RMCAT</a>]</span> describes |
| 2032 |
the interactions and conceptual interfaces necessary between the |
| 2033 |
application components that relate to congestion control, including |
| 2034 |
the RTP layer, the higher-level media codec control layer, and the |
| 2035 |
lower-level transport interface, as well as components dedicated to |
| 2036 |
congestion control functions.<a href="#section-3.4-2" class="pilcrow">¶</a></p> |
| 2037 |
</section> |
| 2038 |
</div> |
| 2039 |
</section> |
| 2040 |
</div> |
| 2041 |
<div id="sect-4"> |
| 2042 |
<section id="section-4"> |
| 2043 |
<h2 id="name-payload-format-parameters"> |
| 2044 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-payload-format-parameters" class="section-name selfRef">Payload Format Parameters</a> |
| 2045 |
</h2> |
| 2046 |
<p id="section-4-1"> |
| 2047 |
This RTP payload format is identified using the TSVCIS media subtype, |
| 2048 |
which is registered in accordance with <span>[<a href="#RFC4855" class="xref">RFC4855</a>]</span> and per the |
| 2049 |
media type registration template from <span>[<a href="#RFC6838" class="xref">RFC6838</a>]</span>.<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 2050 |
<div id="sect-4.1"> |
| 2051 |
<section id="section-4.1"> |
| 2052 |
<h3 id="name-media-type-definitions"> |
| 2053 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-media-type-definitions" class="section-name selfRef">Media Type Definitions</a> |
| 2054 |
</h3> |
| 2055 |
<span class="break"></span><dl class="dlParallel" id="section-4.1-1"> |
| 2056 |
<dt id="section-4.1-1.1">Type name:</dt> |
| 2057 |
<dd id="section-4.1-1.2"> audio<a href="#section-4.1-1.2" class="pilcrow">¶</a> |
| 2058 |
</dd> |
| 2059 |
<dd class="break"></dd> |
| 2060 |
<dt id="section-4.1-1.3">Subtype name:</dt> |
| 2061 |
<dd id="section-4.1-1.4"> TSVCIS<a href="#section-4.1-1.4" class="pilcrow">¶</a> |
| 2062 |
</dd> |
| 2063 |
<dd class="break"></dd> |
| 2064 |
<dt id="section-4.1-1.5">Required parameters:</dt> |
| 2065 |
<dd id="section-4.1-1.6">Clock Rate (Hz): 8000<a href="#section-4.1-1.6" class="pilcrow">¶</a> |
| 2066 |
</dd> |
| 2067 |
<dd class="break"></dd> |
| 2068 |
</dl> |
| 2069 |
<span class="break"></span><dl class="dlNewline" id="section-4.1-2"> |
| 2070 |
<dt id="section-4.1-2.1">Optional parameters:</dt> |
| 2071 |
<dd id="section-4.1-2.2"> |
| 2072 |
<span class="break"></span><dl class="dlNewline" id="section-4.1-2.2.1"> |
| 2073 |
<dt id="section-4.1-2.2.1.1">ptime:</dt> |
| 2074 |
<dd id="section-4.1-2.2.1.2"> the recommended length of time (in milliseconds) |
| 2075 |
represented by the media in a packet. It <span class="bcp14">SHALL</span> |
| 2076 |
use the nearest rounded-up ms integer packet duration. For |
| 2077 |
TSVCIS, this corresponds to the following values: 23, 45, 68, |
| 2078 |
90, 112, 135, 156, and 180. Larger values can be used as long |
| 2079 |
as they are properly rounded. See <span><a href="https://www.rfc-editor.org/rfc/rfc4566#section-6" class="relref">Section 6</a> of [<a href="#RFC4566" class="xref">RFC4566</a>]</span>.<a href="#section-4.1-2.2.1.2" class="pilcrow">¶</a> |
| 2080 |
</dd> |
| 2081 |
<dd class="break"></dd> |
| 2082 |
<dt id="section-4.1-2.2.1.3">maxptime:</dt> |
| 2083 |
<dd id="section-4.1-2.2.1.4"> the maximum length of time (in milliseconds) that can be |
| 2084 |
encapsulated in a packet. It <span class="bcp14">SHALL</span> use the |
| 2085 |
nearest rounded-up ms integer packet duration. For TSVCIS, this |
| 2086 |
corresponds to the following values: 23, 45, 68, 90, 112, 135, |
| 2087 |
156, and 180. Larger values can be used as long as they are |
| 2088 |
properly rounded. See <span><a href="https://www.rfc-editor.org/rfc/rfc4566#section-6" class="relref">Section 6</a> of [<a href="#RFC4566" class="xref">RFC4566</a>]</span>.<a href="#section-4.1-2.2.1.4" class="pilcrow">¶</a> |
| 2089 |
</dd> |
| 2090 |
<dd class="break"></dd> |
| 2091 |
<dt id="section-4.1-2.2.1.5">bitrate:</dt> |
| 2092 |
<dd id="section-4.1-2.2.1.6"> specifies the MELPe coder bitrates supported. Possible |
| 2093 |
values are a comma-separated list of rates from the following |
| 2094 |
set: 2400, 1200, 600. The modes are listed in order of |
| 2095 |
preference; the first is preferred. If "bitrate" is not |
| 2096 |
present, the fixed coder bitrate of 2400 <span class="bcp14">MUST</span> be |
| 2097 |
used.<a href="#section-4.1-2.2.1.6" class="pilcrow">¶</a> |
| 2098 |
</dd> |
| 2099 |
<dd class="break"></dd> |
| 2100 |
<dt id="section-4.1-2.2.1.7">tcmax:</dt> |
| 2101 |
<dd id="section-4.1-2.2.1.8"> specifies the TSVCIS maximum value for the TC supported or |
| 2102 |
desired, ranging from 1 to 255. If "tcmax" is not present, a |
| 2103 |
default value of 35 is used.<a href="#section-4.1-2.2.1.8" class="pilcrow">¶</a> |
| 2104 |
</dd> |
| 2105 |
<dd class="break"></dd> |
| 2106 |
<dt id="section-4.1-2.2.1.9">Channels:</dt> |
| 2107 |
<dd id="section-4.1-2.2.1.10">1<a href="#section-4.1-2.2.1.10" class="pilcrow">¶</a> |
| 2108 |
</dd> |
| 2109 |
<dd class="break"></dd> |
| 2110 |
</dl> |
| 2111 |
</dd> |
| 2112 |
<dd class="break"></dd> |
| 2113 |
</dl> |
| 2114 |
<span class="break"></span><dl class="dlParallel" id="section-4.1-3"> |
| 2115 |
<dt id="section-4.1-3.1">Encoding considerations:</dt> |
| 2116 |
<dd id="section-4.1-3.2"> This media subtype is framed and binary; see <span><a href="https://www.rfc-editor.org/rfc/rfc6838#section-4.8" class="relref">Section 4.8</a> of [<a href="#RFC6838" class="xref">RFC6838</a>]</span>.<a href="#section-4.1-3.2" class="pilcrow">¶</a> |
| 2117 |
</dd> |
| 2118 |
<dd class="break"></dd> |
| 2119 |
<dt id="section-4.1-3.3">Security considerations:</dt> |
| 2120 |
<dd id="section-4.1-3.4"> Please see <a href="#sect-8" class="xref">Section 8</a> of RFC 8817.<a href="#section-4.1-3.4" class="pilcrow">¶</a> |
| 2121 |
</dd> |
| 2122 |
<dd class="break"></dd> |
| 2123 |
<dt id="section-4.1-3.5">Interoperability considerations:</dt> |
| 2124 |
<dd id="section-4.1-3.6">N/A<a href="#section-4.1-3.6" class="pilcrow">¶</a> |
| 2125 |
</dd> |
| 2126 |
<dd class="break"></dd> |
| 2127 |
<dt id="section-4.1-3.7">Published specification:</dt> |
| 2128 |
<dd id="section-4.1-3.8"> |
| 2129 |
<span>[<a href="#TSVCIS" class="xref">TSVCIS</a>]</span><a href="#section-4.1-3.8" class="pilcrow">¶</a> |
| 2130 |
</dd> |
| 2131 |
<dd class="break"></dd> |
| 2132 |
<dt id="section-4.1-3.9">Applications that use this media type:</dt> |
| 2133 |
<dd id="section-4.1-3.10">N/A<a href="#section-4.1-3.10" class="pilcrow">¶</a> |
| 2134 |
</dd> |
| 2135 |
<dd class="break"></dd> |
| 2136 |
<dt id="section-4.1-3.11">Fragment identifier considerations:</dt> |
| 2137 |
<dd id="section-4.1-3.12">N/A<a href="#section-4.1-3.12" class="pilcrow">¶</a> |
| 2138 |
</dd> |
| 2139 |
<dd class="break"></dd> |
| 2140 |
<dt id="section-4.1-3.13">Additional information:</dt> |
| 2141 |
<dd id="section-4.1-3.14"> |
| 2142 |
<p id="section-4.1-3.14.1"><br></p> |
| 2143 |
<span class="break"></span><dl class="dlParallel dlCompact" id="section-4.1-3.14.2"> |
| 2144 |
<dt id="section-4.1-3.14.2.1">Deprecated alias names for this type:</dt> |
| 2145 |
<dd id="section-4.1-3.14.2.2">N/A<a href="#section-4.1-3.14.2.2" class="pilcrow">¶</a> |
| 2146 |
</dd> |
| 2147 |
<dd class="break"></dd> |
| 2148 |
<dt id="section-4.1-3.14.2.3">Magic number(s):</dt> |
| 2149 |
<dd id="section-4.1-3.14.2.4">N/A<a href="#section-4.1-3.14.2.4" class="pilcrow">¶</a> |
| 2150 |
</dd> |
| 2151 |
<dd class="break"></dd> |
| 2152 |
<dt id="section-4.1-3.14.2.5">File extension(s):</dt> |
| 2153 |
<dd id="section-4.1-3.14.2.6">N/A<a href="#section-4.1-3.14.2.6" class="pilcrow">¶</a> |
| 2154 |
</dd> |
| 2155 |
<dd class="break"></dd> |
| 2156 |
<dt id="section-4.1-3.14.2.7">Macintosh file type code(s):</dt> |
| 2157 |
<dd id="section-4.1-3.14.2.8">N/A<a href="#section-4.1-3.14.2.8" class="pilcrow">¶</a> |
| 2158 |
</dd> |
| 2159 |
<dd class="break"></dd> |
| 2160 |
</dl> |
| 2161 |
</dd> |
| 2162 |
<dd class="break"></dd> |
| 2163 |
<dt id="section-4.1-3.15">Person & email address to contact for further information:</dt> |
| 2164 |
<dd id="section-4.1-3.16"> |
| 2165 |
<p id="section-4.1-3.16.1"><br><span class="contact-name">Victor Demjanenko, Ph.D.</span> |
| 2166 |
<[email protected]><a href="#section-4.1-3.16.1" class="pilcrow">¶</a></p> |
| 2167 |
</dd> |
| 2168 |
<dd class="break"></dd> |
| 2169 |
<dt id="section-4.1-3.17">Intended usage:</dt> |
| 2170 |
<dd id="section-4.1-3.18">COMMON<a href="#section-4.1-3.18" class="pilcrow">¶</a> |
| 2171 |
</dd> |
| 2172 |
<dd class="break"></dd> |
| 2173 |
<dt id="section-4.1-3.19">Restrictions on usage:</dt> |
| 2174 |
<dd id="section-4.1-3.20"> The media subtype depends on RTP |
| 2175 |
framing and hence is only defined for transfer via RTP <span>[<a href="#RFC3550" class="xref">RFC3550</a>]</span>. Transport within other framing protocols is not |
| 2176 |
defined at this time.<a href="#section-4.1-3.20" class="pilcrow">¶</a> |
| 2177 |
</dd> |
| 2178 |
<dd class="break"></dd> |
| 2179 |
<dt id="section-4.1-3.21">Author:</dt> |
| 2180 |
<dd id="section-4.1-3.22"> |
| 2181 |
<p id="section-4.1-3.22.1"><span class="contact-name">Victor Demjanenko, Ph.D.</span><a href="#section-4.1-3.22.1" class="pilcrow">¶</a></p> |
| 2182 |
</dd> |
| 2183 |
<dd class="break"></dd> |
| 2184 |
<dt id="section-4.1-3.23">Change controller:</dt> |
| 2185 |
<dd id="section-4.1-3.24"> IETF; contact <[email protected]><a href="#section-4.1-3.24" class="pilcrow">¶</a> |
| 2186 |
</dd> |
| 2187 |
<dd class="break"></dd> |
| 2188 |
<dt id="section-4.1-3.25">Provisional registration? (standards tree only):</dt> |
| 2189 |
<dd id="section-4.1-3.26"> No<a href="#section-4.1-3.26" class="pilcrow">¶</a> |
| 2190 |
</dd> |
| 2191 |
<dd class="break"></dd> |
| 2192 |
</dl> |
| 2193 |
</section> |
| 2194 |
</div> |
| 2195 |
<div id="sect-4.2"> |
| 2196 |
<section id="section-4.2"> |
| 2197 |
<h3 id="name-mapping-to-sdp"> |
| 2198 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-mapping-to-sdp" class="section-name selfRef">Mapping to SDP</a> |
| 2199 |
</h3> |
| 2200 |
<p id="section-4.2-1"> |
| 2201 |
The mapping of the above-defined payload format media subtype and its |
| 2202 |
parameters <span class="bcp14">SHALL</span> be done according to <span><a href="https://www.rfc-editor.org/rfc/rfc4855#section-3" class="relref">Section 3</a> of [<a href="#RFC4855" class="xref">RFC4855</a>]</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 2203 |
<p id="section-4.2-2"> |
| 2204 |
The information carried in the media type specification has a |
| 2205 |
specific mapping to fields in the Session Description Protocol (SDP) |
| 2206 |
<span>[<a href="#RFC4566" class="xref">RFC4566</a>]</span>, which is commonly used to describe RTP sessions. When SDP |
| 2207 |
is used to specify sessions employing the TSVCIS codec, the mapping |
| 2208 |
is as follows:<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 2209 |
<ul class="normal"> |
| 2210 |
<li class="normal" id="section-4.2-3.1">The media type ("audio") goes in SDP "m=" as the media name.<a href="#section-4.2-3.1" class="pilcrow">¶</a> |
| 2211 |
</li> |
| 2212 |
<li class="normal" id="section-4.2-3.2">The media subtype (payload format name) goes in SDP "a=rtpmap" as |
| 2213 |
the encoding name.<a href="#section-4.2-3.2" class="pilcrow">¶</a> |
| 2214 |
</li> |
| 2215 |
<li class="normal" id="section-4.2-3.3">The parameter "bitrate" goes in the SDP "a=fmtp" attribute by |
| 2216 |
copying it as a "bitrate=<value>" string.<a href="#section-4.2-3.3" class="pilcrow">¶</a> |
| 2217 |
</li> |
| 2218 |
<li class="normal" id="section-4.2-3.4">The parameter "tcmax" goes in the SDP "a=fmtp" attribute by |
| 2219 |
copying it as a "tcmax=<value>" string.<a href="#section-4.2-3.4" class="pilcrow">¶</a> |
| 2220 |
</li> |
| 2221 |
<li class="normal" id="section-4.2-3.5">The parameters "ptime" and "maxptime" go in the SDP "a=ptime" and |
| 2222 |
"a=maxptime" attributes, respectively.<a href="#section-4.2-3.5" class="pilcrow">¶</a> |
| 2223 |
</li> |
| 2224 |
</ul> |
| 2225 |
<p id="section-4.2-4"> |
| 2226 |
When conveying information via SDP, the encoding name <span class="bcp14">SHALL</span> be |
| 2227 |
"TSVCIS" (the same as the media subtype).<a href="#section-4.2-4" class="pilcrow">¶</a></p> |
| 2228 |
<p id="section-4.2-5"> |
| 2229 |
An example of the media representation in SDP for describing TSVCIS |
| 2230 |
might be:<a href="#section-4.2-5" class="pilcrow">¶</a></p> |
| 2231 |
<div id="section-4.2-6"> |
| 2232 |
<pre class="sourcecode lang-sdp"> |
| 2233 |
m=audio 49120 RTP/AVP 96 |
| 2234 |
a=rtpmap:96 TSVCIS/8000 |
| 2235 |
</pre><a href="#section-4.2-6" class="pilcrow">¶</a> |
| 2236 |
</div> |
| 2237 |
<p id="section-4.2-7"> |
| 2238 |
The optional media type parameter "bitrate", when present, <span class="bcp14">MUST</span> be |
| 2239 |
included in the "a=fmtp" attribute in the SDP, expressed as a media |
| 2240 |
type string in the form of a semicolon-separated list of |
| 2241 |
parameter=value pairs. The string "value" can be one or more of |
| 2242 |
2400, 1200, and 600, separated by commas (where each bitrate value |
| 2243 |
indicates the corresponding MELPe coder). An example of the media |
| 2244 |
representation in SDP for describing TSVCIS when all three coder |
| 2245 |
bitrates are supported might be:<a href="#section-4.2-7" class="pilcrow">¶</a></p> |
| 2246 |
<div id="section-4.2-8"> |
| 2247 |
<pre class="sourcecode lang-sdp"> |
| 2248 |
m=audio 49120 RTP/AVP 96 |
| 2249 |
a=rtpmap:96 TSVCIS/8000 |
| 2250 |
a=fmtp:96 bitrate=2400,600,1200 |
| 2251 |
</pre><a href="#section-4.2-8" class="pilcrow">¶</a> |
| 2252 |
</div> |
| 2253 |
<p id="section-4.2-9"> |
| 2254 |
The optional media type parameter "tcmax", when present, <span class="bcp14">MUST</span> be |
| 2255 |
included in the "a=fmtp" attribute in the SDP, expressed as a media |
| 2256 |
type string in the form of a semicolon-separated list of |
| 2257 |
parameter=value pairs. The string "value" is an integer number in |
| 2258 |
the range of 1 to 255 representing the maximum number of TSVCIS |
| 2259 |
parameter octets supported. An example of the media representation |
| 2260 |
in SDP for describing TSVCIS with a maximum of 101 octets supported |
| 2261 |
is as follows:<a href="#section-4.2-9" class="pilcrow">¶</a></p> |
| 2262 |
<div id="section-4.2-10"> |
| 2263 |
<pre class="sourcecode lang-sdp"> |
| 2264 |
m=audio 49120 RTP/AVP 96 |
| 2265 |
a=rtpmap:96 TSVCIS/8000 |
| 2266 |
a=fmtp:96 tcmax=101 |
| 2267 |
</pre><a href="#section-4.2-10" class="pilcrow">¶</a> |
| 2268 |
</div> |
| 2269 |
<p id="section-4.2-11"> |
| 2270 |
The parameter "ptime" cannot be used for the purpose of specifying |
| 2271 |
the TSVCIS operating mode due to the fact that, for certain values, it |
| 2272 |
will be impossible to distinguish which mode is about to be used |
| 2273 |
(e.g., when ptime=68, it would be impossible to distinguish whether the |
| 2274 |
packet is carrying one frame of 67.5 ms or three frames of 22.5 ms).<a href="#section-4.2-11" class="pilcrow">¶</a></p> |
| 2275 |
<p id="section-4.2-12"> |
| 2276 |
Note that the payload format (encoding) names are commonly shown in |
| 2277 |
upper case. Media subtypes are commonly shown in lower case. These |
| 2278 |
names are case insensitive in both places. Similarly, parameter |
| 2279 |
names are case insensitive in both the media subtype name and the |
| 2280 |
default mapping to the SDP a=fmtp attribute.<a href="#section-4.2-12" class="pilcrow">¶</a></p> |
| 2281 |
</section> |
| 2282 |
</div> |
| 2283 |
<div id="sect-4.3"> |
| 2284 |
<section id="section-4.3"> |
| 2285 |
<h3 id="name-declarative-sdp-considerati"> |
| 2286 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-declarative-sdp-considerati" class="section-name selfRef">Declarative SDP Considerations</a> |
| 2287 |
</h3> |
| 2288 |
<p id="section-4.3-1"> |
| 2289 |
For declarative media, the "bitrate" parameter specifies the possible |
| 2290 |
bitrates used by the sender. Multiple TSVCIS rtpmap values (such as |
| 2291 |
97, 98, and 99, as used below) <span class="bcp14">MAY</span> be used to convey TSVCIS-coded |
| 2292 |
voice at different bitrates. The receiver can then select an |
| 2293 |
appropriate TSVCIS codec by using 97, 98, or 99.<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 2294 |
<div id="section-4.3-2"> |
| 2295 |
<pre class="sourcecode lang-sdp"> |
| 2296 |
m=audio 49120 RTP/AVP 97 98 99 |
| 2297 |
a=rtpmap:97 TSVCIS/8000 |
| 2298 |
a=fmtp:97 bitrate=2400 |
| 2299 |
a=rtpmap:98 TSVCIS/8000 |
| 2300 |
a=fmtp:98 bitrate=1200 |
| 2301 |
a=rtpmap:99 TSVCIS/8000 |
| 2302 |
a=fmtp:99 bitrate=600 |
| 2303 |
</pre><a href="#section-4.3-2" class="pilcrow">¶</a> |
| 2304 |
</div> |
| 2305 |
<p id="section-4.3-3"> |
| 2306 |
For declarative media, the "tcmax" parameter specifies the maximum |
| 2307 |
number of octets of TSVCIS packed parameters used by the sender or the |
| 2308 |
sender's communications channel.<a href="#section-4.3-3" class="pilcrow">¶</a></p> |
| 2309 |
</section> |
| 2310 |
</div> |
| 2311 |
<div id="sect-4.4"> |
| 2312 |
<section id="section-4.4"> |
| 2313 |
<h3 id="name-offer-answer-sdp-considerat"> |
| 2314 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-offer-answer-sdp-considerat" class="section-name selfRef">Offer/Answer SDP Considerations</a> |
| 2315 |
</h3> |
| 2316 |
<p id="section-4.4-1"> |
| 2317 |
In the Offer/Answer model <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>, "bitrate" is a bidirectional |
| 2318 |
parameter. Both sides <span class="bcp14">MUST</span> use a common "bitrate" value or values. |
| 2319 |
The offer contains the bitrates supported by the offerer, listed in |
| 2320 |
its preferred order. The answerer <span class="bcp14">MAY</span> agree to any bitrate by |
| 2321 |
listing the bitrate first in the answerer response. Additionally, |
| 2322 |
the answerer <span class="bcp14">MAY</span> indicate any secondary bitrate or bitrates that it |
| 2323 |
supports. The initial bitrate used by both parties <span class="bcp14">SHALL</span> be the |
| 2324 |
first bitrate specified in the answerer response.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 2325 |
<p id="section-4.4-2"> |
| 2326 |
For example, if offerer bitrates are "2400,600" and answerer bitrates |
| 2327 |
are "600,2400", the initial bitrate is 600. If other bitrates are |
| 2328 |
provided by the answerer, any common bitrate between the offer and |
| 2329 |
answer <span class="bcp14">MAY</span> be used at any time in the future. Activation of these |
| 2330 |
other common bitrates is beyond the scope of this document.<a href="#section-4.4-2" class="pilcrow">¶</a></p> |
| 2331 |
<p id="section-4.4-3"> |
| 2332 |
The use of a lower bitrate is often important for a case such as when |
| 2333 |
one endpoint utilizes a bandwidth-constrained link (e.g., 1200 bps |
| 2334 |
radio link or slower), where only the lower coder bitrate will work.<a href="#section-4.4-3" class="pilcrow">¶</a></p> |
| 2335 |
<p id="section-4.4-4"> |
| 2336 |
In the Offer/Answer model <span>[<a href="#RFC3264" class="xref">RFC3264</a>]</span>, "tcmax" is a bidirectional |
| 2337 |
parameter. Both sides <span class="bcp14">SHOULD</span> use a common "tcmax" value. The offer |
| 2338 |
contains the tcmax supported by the offerer. The answerer <span class="bcp14">MAY</span> agree |
| 2339 |
to any tcmax equal to or less than this value by stating the desired |
| 2340 |
tcmax in the answerer response. The answerer alternatively <span class="bcp14">MAY</span> |
| 2341 |
identify its own tcmax and rely on TSVCIS ignoring any augmented data |
| 2342 |
it cannot use.<a href="#section-4.4-4" class="pilcrow">¶</a></p> |
| 2343 |
</section> |
| 2344 |
</div> |
| 2345 |
</section> |
| 2346 |
</div> |
| 2347 |
<div id="sect-5"> |
| 2348 |
<section id="section-5"> |
| 2349 |
<h2 id="name-discontinuous-transmissions"> |
| 2350 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-discontinuous-transmissions" class="section-name selfRef">Discontinuous Transmissions</a> |
| 2351 |
</h2> |
| 2352 |
<p id="section-5-1"> |
| 2353 |
A primary application of TSVCIS is for radio communications of voice |
| 2354 |
conversations, and discontinuous transmissions are normal. When |
| 2355 |
TSVCIS is used in an IP network, TSVCIS RTP packet transmissions may |
| 2356 |
cease and resume frequently. RTP synchronization source (SSRC) |
| 2357 |
sequence number gaps indicate lost packets to be filled by Packet |
| 2358 |
Loss Concealment (PLC), while abrupt loss of RTP packets indicates |
| 2359 |
intended discontinuous transmissions. Resumption of voice |
| 2360 |
transmission <span class="bcp14">SHOULD</span> be indicated by the RTP marker bit (M) set to 1.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 2361 |
<p id="section-5-2">If a TSVCIS coder so desires, it may send a MELPe comfort noise frame as |
| 2362 |
per Appendix B of <span>[<a href="#SCIP210" class="xref">SCIP210</a>]</span> prior to ceasing transmission. A |
| 2363 |
receiver may optionally use comfort noise during its silence periods. No |
| 2364 |
SDP negotiations are required.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 2365 |
</section> |
| 2366 |
</div> |
| 2367 |
<div id="sect-6"> |
| 2368 |
<section id="section-6"> |
| 2369 |
<h2 id="name-packet-loss-concealment"> |
| 2370 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-packet-loss-concealment" class="section-name selfRef">Packet Loss Concealment</a> |
| 2371 |
</h2> |
| 2372 |
<p id="section-6-1"> |
| 2373 |
TSVCIS packet loss concealment (PLC) uses the special properties and |
| 2374 |
coding for the pitch/voicing parameter of the MELPe 2400 bps coder. |
| 2375 |
The PLC erasure indication utilizes any of the errored encodings of a |
| 2376 |
non-voiced frame as identified in Table 1 of <span>[<a href="#MELPE" class="xref">MELPE</a>]</span>. For the sake of |
| 2377 |
simplicity, it is preferred that a code value of 3 for the |
| 2378 |
pitch/voicing parameter be used. Hence, set bits P0 and P1 to one |
| 2379 |
and bits P2, P3, P4, P5, and P6 to zero.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 2380 |
<p id="section-6-2"> |
| 2381 |
When using PLC in 1200 bps or 600 bps mode, the MELPe 2400 bps |
| 2382 |
decoder is called three or four times, respectively, to cover the |
| 2383 |
loss of a low bitrate MELPe frame.<a href="#section-6-2" class="pilcrow">¶</a></p> |
| 2384 |
</section> |
| 2385 |
</div> |
| 2386 |
<div id="sect-7"> |
| 2387 |
<section id="section-7"> |
| 2388 |
<h2 id="name-iana-considerations"> |
| 2389 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2390 |
</h2> |
| 2391 |
<p id="section-7-1"> |
| 2392 |
IANA has registered TSVCIS as specified in <a href="#sect-4.1" class="xref">Section 4.1</a>. The media type has been added to the IANA |
| 2393 |
registry for "RTP Payload Format Media Types" |
| 2394 |
(<span><a href="https://www.iana.org/assignments/rtp-parameters">https://www.iana.org/assignments/rtp-parameters</a></span>).<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 2395 |
</section> |
| 2396 |
</div> |
| 2397 |
<div id="sect-8"> |
| 2398 |
<section id="section-8"> |
| 2399 |
<h2 id="name-security-considerations"> |
| 2400 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2401 |
</h2> |
| 2402 |
<p id="section-8-1"> |
| 2403 |
RTP packets using the payload format defined in this specification |
| 2404 |
are subject to the security considerations discussed in the RTP |
| 2405 |
specification <span>[<a href="#RFC3550" class="xref">RFC3550</a>]</span> and in any applicable RTP profile such as |
| 2406 |
RTP/AVP <span>[<a href="#RFC3551" class="xref">RFC3551</a>]</span>, RTP/AVPF <span>[<a href="#RFC4585" class="xref">RFC4585</a>]</span>, RTP/SAVP <span>[<a href="#RFC3711" class="xref">RFC3711</a>]</span>, or |
| 2407 |
RTP/SAVPF <span>[<a href="#RFC5124" class="xref">RFC5124</a>]</span>. However, as discussed in <span>[<a href="#RFC7202" class="xref">RFC7202</a>]</span>, it is not |
| 2408 |
an RTP payload format's responsibility to discuss or mandate what |
| 2409 |
solutions are used to meet such basic security goals as |
| 2410 |
confidentiality, integrity, and source authenticity for RTP in |
| 2411 |
general. This responsibility lies with anyone using RTP in an |
| 2412 |
application. They can find guidance on available security mechanisms |
| 2413 |
and important considerations in <span>[<a href="#RFC7201" class="xref">RFC7201</a>]</span>. Applications <span class="bcp14">SHOULD</span> use |
| 2414 |
one or more appropriate strong security mechanisms. The rest of this |
| 2415 |
section discusses the security-impacting properties of the payload |
| 2416 |
format itself.<a href="#section-8-1" class="pilcrow">¶</a></p> |
| 2417 |
<p id="section-8-2"> |
| 2418 |
This RTP payload format and the TSVCIS decoder, to the best of our |
| 2419 |
knowledge, do not exhibit any significant non-uniformity in the |
| 2420 |
receiver-side computational complexity for packet processing and thus |
| 2421 |
are unlikely to pose a denial-of-service threat due to the receipt of |
| 2422 |
pathological data. Additionally, the RTP payload format does not |
| 2423 |
contain any active content.<a href="#section-8-2" class="pilcrow">¶</a></p> |
| 2424 |
<p id="section-8-3"> |
| 2425 |
Please see the security considerations discussed in <span>[<a href="#RFC6562" class="xref">RFC6562</a>]</span> |
| 2426 |
regarding Voice Activity Detect (VAD) and its effect on bitrates.<a href="#section-8-3" class="pilcrow">¶</a></p> |
| 2427 |
</section> |
| 2428 |
</div> |
| 2429 |
<section id="section-9"> |
| 2430 |
<h2 id="name-references"> |
| 2431 |
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 2432 |
</h2> |
| 2433 |
<section id="section-9.1"> |
| 2434 |
<h3 id="name-normative-references"> |
| 2435 |
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 2436 |
</h3> |
| 2437 |
<dl class="references"> |
| 2438 |
<dt id="MELP">[MELP]</dt> |
| 2439 |
<dd> |
| 2440 |
<span class="refAuthor">Department of Defense</span>, <span class="refTitle">"Analog-to-Digital Conversion of Voice by 2,400 Bit/Second Mixed Excitation Linear Prediction (MELP)"</span>, <span class="seriesInfo">Department of Defense Telecommunications Standard MIL-STD-3005</span>, <time datetime="1999-12" class="refDate">December 1999</time>. </dd> |
| 2441 |
<dd class="break"></dd> |
| 2442 |
<dt id="MELPE">[MELPE]</dt> |
| 2443 |
<dd> |
| 2444 |
<span class="refAuthor">North Atlantic Treaty Organization (NATO)</span>, <span class="refTitle">"The 600 Bit/S, 1200 Bit/S and 2400 Bit/S NATO Interoperable Narrow Band Voice Coder"</span>, <span class="seriesInfo">STANAG No. 4591</span>, <time datetime="2008-10" class="refDate">October 2008</time>. </dd> |
| 2445 |
<dd class="break"></dd> |
| 2446 |
<dt id="NRLVDR">[NRLVDR]</dt> |
| 2447 |
<dd> |
| 2448 |
<span class="refAuthor">Heide, D.</span><span class="refAuthor">, Cohen, A.</span><span class="refAuthor">, Lee, Y.</span><span class="refAuthor">, and T. Moran</span>, <span class="refTitle">"Universal Vocoder Using Variable Data Rate Vocoding"</span>, <span class="seriesInfo">DOI 10.21236/ada588068</span>, <span class="seriesInfo">Naval Research Lab NRL/FR/5555--13-10, 239</span>, <time datetime="2013-06" class="refDate">June 2013</time>, <span><<a href="https://doi.org/10.21236/ada588068">https://doi.org/10.21236/ada588068</a>></span>. </dd> |
| 2449 |
<dd class="break"></dd> |
| 2450 |
<dt id="RFC2119">[RFC2119]</dt> |
| 2451 |
<dd> |
| 2452 |
<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> |
| 2453 |
<dd class="break"></dd> |
| 2454 |
<dt id="RFC2736">[RFC2736]</dt> |
| 2455 |
<dd> |
| 2456 |
<span class="refAuthor">Handley, M.</span><span class="refAuthor"> and C. Perkins</span>, <span class="refTitle">"Guidelines for Writers of RTP Payload Format Specifications"</span>, <span class="seriesInfo">BCP 36</span>, <span class="seriesInfo">RFC 2736</span>, <span class="seriesInfo">DOI 10.17487/RFC2736</span>, <time datetime="1999-12" class="refDate">December 1999</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2736">https://www.rfc-editor.org/info/rfc2736</a>></span>. </dd> |
| 2457 |
<dd class="break"></dd> |
| 2458 |
<dt id="RFC3264">[RFC3264]</dt> |
| 2459 |
<dd> |
| 2460 |
<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> |
| 2461 |
<dd class="break"></dd> |
| 2462 |
<dt id="RFC3550">[RFC3550]</dt> |
| 2463 |
<dd> |
| 2464 |
<span class="refAuthor">Schulzrinne, H.</span><span class="refAuthor">, Casner, S.</span><span class="refAuthor">, Frederick, R.</span><span class="refAuthor">, and V. Jacobson</span>, <span class="refTitle">"RTP: A Transport Protocol for Real-Time Applications"</span>, <span class="seriesInfo">STD 64</span>, <span class="seriesInfo">RFC 3550</span>, <span class="seriesInfo">DOI 10.17487/RFC3550</span>, <time datetime="2003-07" class="refDate">July 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3550">https://www.rfc-editor.org/info/rfc3550</a>></span>. </dd> |
| 2465 |
<dd class="break"></dd> |
| 2466 |
<dt id="RFC3551">[RFC3551]</dt> |
| 2467 |
<dd> |
| 2468 |
<span class="refAuthor">Schulzrinne, H.</span><span class="refAuthor"> and S. Casner</span>, <span class="refTitle">"RTP Profile for Audio and Video Conferences with Minimal Control"</span>, <span class="seriesInfo">STD 65</span>, <span class="seriesInfo">RFC 3551</span>, <span class="seriesInfo">DOI 10.17487/RFC3551</span>, <time datetime="2003-07" class="refDate">July 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3551">https://www.rfc-editor.org/info/rfc3551</a>></span>. </dd> |
| 2469 |
<dd class="break"></dd> |
| 2470 |
<dt id="RFC3711">[RFC3711]</dt> |
| 2471 |
<dd> |
| 2472 |
<span class="refAuthor">Baugher, M.</span><span class="refAuthor">, McGrew, D.</span><span class="refAuthor">, Naslund, M.</span><span class="refAuthor">, Carrara, E.</span><span class="refAuthor">, and K. Norrman</span>, <span class="refTitle">"The Secure Real-time Transport Protocol (SRTP)"</span>, <span class="seriesInfo">RFC 3711</span>, <span class="seriesInfo">DOI 10.17487/RFC3711</span>, <time datetime="2004-03" class="refDate">March 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3711">https://www.rfc-editor.org/info/rfc3711</a>></span>. </dd> |
| 2473 |
<dd class="break"></dd> |
| 2474 |
<dt id="RFC4566">[RFC4566]</dt> |
| 2475 |
<dd> |
| 2476 |
<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> |
| 2477 |
<dd class="break"></dd> |
| 2478 |
<dt id="RFC4855">[RFC4855]</dt> |
| 2479 |
<dd> |
| 2480 |
<span class="refAuthor">Casner, S.</span>, <span class="refTitle">"Media Type Registration of RTP Payload Formats"</span>, <span class="seriesInfo">RFC 4855</span>, <span class="seriesInfo">DOI 10.17487/RFC4855</span>, <time datetime="2007-02" class="refDate">February 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4855">https://www.rfc-editor.org/info/rfc4855</a>></span>. </dd> |
| 2481 |
<dd class="break"></dd> |
| 2482 |
<dt id="RFC5124">[RFC5124]</dt> |
| 2483 |
<dd> |
| 2484 |
<span class="refAuthor">Ott, J.</span><span class="refAuthor"> and E. Carrara</span>, <span class="refTitle">"Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)"</span>, <span class="seriesInfo">RFC 5124</span>, <span class="seriesInfo">DOI 10.17487/RFC5124</span>, <time datetime="2008-02" class="refDate">February 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5124">https://www.rfc-editor.org/info/rfc5124</a>></span>. </dd> |
| 2485 |
<dd class="break"></dd> |
| 2486 |
<dt id="RFC6562">[RFC6562]</dt> |
| 2487 |
<dd> |
| 2488 |
<span class="refAuthor">Perkins, C.</span><span class="refAuthor"> and JM. Valin</span>, <span class="refTitle">"Guidelines for the Use of Variable Bit Rate Audio with Secure RTP"</span>, <span class="seriesInfo">RFC 6562</span>, <span class="seriesInfo">DOI 10.17487/RFC6562</span>, <time datetime="2012-03" class="refDate">March 2012</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6562">https://www.rfc-editor.org/info/rfc6562</a>></span>. </dd> |
| 2489 |
<dd class="break"></dd> |
| 2490 |
<dt id="RFC6838">[RFC6838]</dt> |
| 2491 |
<dd> |
| 2492 |
<span class="refAuthor">Freed, N.</span><span class="refAuthor">, Klensin, J.</span><span class="refAuthor">, and T. Hansen</span>, <span class="refTitle">"Media Type Specifications and Registration Procedures"</span>, <span class="seriesInfo">BCP 13</span>, <span class="seriesInfo">RFC 6838</span>, <span class="seriesInfo">DOI 10.17487/RFC6838</span>, <time datetime="2013-01" class="refDate">January 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6838">https://www.rfc-editor.org/info/rfc6838</a>></span>. </dd> |
| 2493 |
<dd class="break"></dd> |
| 2494 |
<dt id="RFC8083">[RFC8083]</dt> |
| 2495 |
<dd> |
| 2496 |
<span class="refAuthor">Perkins, C.</span><span class="refAuthor"> and V. Singh</span>, <span class="refTitle">"Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions"</span>, <span class="seriesInfo">RFC 8083</span>, <span class="seriesInfo">DOI 10.17487/RFC8083</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8083">https://www.rfc-editor.org/info/rfc8083</a>></span>. </dd> |
| 2497 |
<dd class="break"></dd> |
| 2498 |
<dt id="RFC8085">[RFC8085]</dt> |
| 2499 |
<dd> |
| 2500 |
<span class="refAuthor">Eggert, L.</span><span class="refAuthor">, Fairhurst, G.</span><span class="refAuthor">, and G. Shepherd</span>, <span class="refTitle">"UDP Usage Guidelines"</span>, <span class="seriesInfo">BCP 145</span>, <span class="seriesInfo">RFC 8085</span>, <span class="seriesInfo">DOI 10.17487/RFC8085</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8085">https://www.rfc-editor.org/info/rfc8085</a>></span>. </dd> |
| 2501 |
<dd class="break"></dd> |
| 2502 |
<dt id="RFC8088">[RFC8088]</dt> |
| 2503 |
<dd> |
| 2504 |
<span class="refAuthor">Westerlund, M.</span>, <span class="refTitle">"How to Write an RTP Payload Format"</span>, <span class="seriesInfo">RFC 8088</span>, <span class="seriesInfo">DOI 10.17487/RFC8088</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8088">https://www.rfc-editor.org/info/rfc8088</a>></span>. </dd> |
| 2505 |
<dd class="break"></dd> |
| 2506 |
<dt id="RFC8130">[RFC8130]</dt> |
| 2507 |
<dd> |
| 2508 |
<span class="refAuthor">Demjanenko, V.</span><span class="refAuthor"> and D. Satterlee</span>, <span class="refTitle">"RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) Codec"</span>, <span class="seriesInfo">RFC 8130</span>, <span class="seriesInfo">DOI 10.17487/RFC8130</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8130">https://www.rfc-editor.org/info/rfc8130</a>></span>. </dd> |
| 2509 |
<dd class="break"></dd> |
| 2510 |
<dt id="RFC8174">[RFC8174]</dt> |
| 2511 |
<dd> |
| 2512 |
<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> |
| 2513 |
<dd class="break"></dd> |
| 2514 |
<dt id="SCIP210">[SCIP210]</dt> |
| 2515 |
<dd> |
| 2516 |
<span class="refAuthor">National Security Agency</span>, <span class="refTitle">"SCIP Signaling Plan"</span>, <span class="refContent">SCIP-210</span>, <time datetime="2013-01" class="refDate">January 2013</time>. </dd> |
| 2517 |
<dd class="break"></dd> |
| 2518 |
</dl> |
| 2519 |
</section> |
| 2520 |
<section id="section-9.2"> |
| 2521 |
<h3 id="name-informative-references"> |
| 2522 |
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2523 |
</h3> |
| 2524 |
<dl class="references"> |
| 2525 |
<dt id="RFC4585">[RFC4585]</dt> |
| 2526 |
<dd> |
| 2527 |
<span class="refAuthor">Ott, J.</span><span class="refAuthor">, Wenger, S.</span><span class="refAuthor">, Sato, N.</span><span class="refAuthor">, Burmeister, C.</span><span class="refAuthor">, and J. Rey</span>, <span class="refTitle">"Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)"</span>, <span class="seriesInfo">RFC 4585</span>, <span class="seriesInfo">DOI 10.17487/RFC4585</span>, <time datetime="2006-07" class="refDate">July 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4585">https://www.rfc-editor.org/info/rfc4585</a>></span>. </dd> |
| 2528 |
<dd class="break"></dd> |
| 2529 |
<dt id="RFC7201">[RFC7201]</dt> |
| 2530 |
<dd> |
| 2531 |
<span class="refAuthor">Westerlund, M.</span><span class="refAuthor"> and C. Perkins</span>, <span class="refTitle">"Options for Securing RTP Sessions"</span>, <span class="seriesInfo">RFC 7201</span>, <span class="seriesInfo">DOI 10.17487/RFC7201</span>, <time datetime="2014-04" class="refDate">April 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7201">https://www.rfc-editor.org/info/rfc7201</a>></span>. </dd> |
| 2532 |
<dd class="break"></dd> |
| 2533 |
<dt id="RFC7202">[RFC7202]</dt> |
| 2534 |
<dd> |
| 2535 |
<span class="refAuthor">Perkins, C.</span><span class="refAuthor"> and M. Westerlund</span>, <span class="refTitle">"Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution"</span>, <span class="seriesInfo">RFC 7202</span>, <span class="seriesInfo">DOI 10.17487/RFC7202</span>, <time datetime="2014-04" class="refDate">April 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7202">https://www.rfc-editor.org/info/rfc7202</a>></span>. </dd> |
| 2536 |
<dd class="break"></dd> |
| 2537 |
<dt id="RMCAT">[RMCAT]</dt> |
| 2538 |
<dd> |
| 2539 |
<span class="refAuthor">IETF</span>, <span class="refTitle">"RTP Media Congestion Avoidance Techniques (rmcat) Working Group"</span>, <span><<a href="https://datatracker.ietf.org/wg/rmcat/about/">https://datatracker.ietf.org/wg/rmcat/about/</a>></span>. </dd> |
| 2540 |
<dd class="break"></dd> |
| 2541 |
<dt id="TSVCIS">[TSVCIS]</dt> |
| 2542 |
<dd> |
| 2543 |
<span class="refAuthor">National Security Agency</span>, <span class="refTitle">"Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Version 3.1"</span>, <span class="seriesInfo">NSA 09-01A</span>, <time datetime="2019-03" class="refDate">March 2019</time>. </dd> |
| 2544 |
<dd class="break"></dd> |
| 2545 |
</dl> |
| 2546 |
</section> |
| 2547 |
</section> |
| 2548 |
<div id="authors-addresses"> |
| 2549 |
<section id="section-appendix.a"> |
| 2550 |
<h2 id="name-authors-addresses"> |
| 2551 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2552 |
</h2> |
| 2553 |
<address class="vcard"> |
| 2554 |
<div dir="auto" class="left"><span class="fn nameRole">Victor Demjanenko, Ph.D.</span></div> |
| 2555 |
<div dir="auto" class="left"><span class="org">VOCAL Technologies, Ltd.</span></div> |
| 2556 |
<div dir="auto" class="left"><span class="street-address">520 Lee Entrance, Suite 202</span></div> |
| 2557 |
<div dir="auto" class="left"> |
| 2558 |
<span class="locality">Buffalo</span>, <span class="region">NY</span> <span class="postal-code">14228</span> |
| 2559 |
</div> |
| 2560 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2561 |
<div class="tel"> |
| 2562 |
<span>Phone:</span> |
| 2563 |
<a href="tel:+1%20716%20688%204675" class="tel">+1 716 688 4675</a> |
| 2564 |
</div> |
| 2565 |
<div class="email"> |
| 2566 |
<span>Email:</span> |
| 2567 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2568 |
</div> |
| 2569 |
</address> |
| 2570 |
<address class="vcard"> |
| 2571 |
<div dir="auto" class="left"><span class="fn nameRole">John Punaro</span></div> |
| 2572 |
<div dir="auto" class="left"><span class="org">VOCAL Technologies, Ltd.</span></div> |
| 2573 |
<div dir="auto" class="left"><span class="street-address">520 Lee Entrance, Suite 202</span></div> |
| 2574 |
<div dir="auto" class="left"> |
| 2575 |
<span class="locality">Buffalo</span>, <span class="region">NY</span> <span class="postal-code">14228</span> |
| 2576 |
</div> |
| 2577 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2578 |
<div class="tel"> |
| 2579 |
<span>Phone:</span> |
| 2580 |
<a href="tel:+1%20716%20688%204675" class="tel">+1 716 688 4675</a> |
| 2581 |
</div> |
| 2582 |
<div class="email"> |
| 2583 |
<span>Email:</span> |
| 2584 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2585 |
</div> |
| 2586 |
</address> |
| 2587 |
<address class="vcard"> |
| 2588 |
<div dir="auto" class="left"><span class="fn nameRole">David Satterlee</span></div> |
| 2589 |
<div dir="auto" class="left"><span class="org">VOCAL Technologies, Ltd.</span></div> |
| 2590 |
<div dir="auto" class="left"><span class="street-address">520 Lee Entrance, Suite 202</span></div> |
| 2591 |
<div dir="auto" class="left"> |
| 2592 |
<span class="locality">Buffalo</span>, <span class="region">NY</span> <span class="postal-code">14228</span> |
| 2593 |
</div> |
| 2594 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2595 |
<div class="tel"> |
| 2596 |
<span>Phone:</span> |
| 2597 |
<a href="tel:+1%20716%20688%204675" class="tel">+1 716 688 4675</a> |
| 2598 |
</div> |
| 2599 |
<div class="email"> |
| 2600 |
<span>Email:</span> |
| 2601 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2602 |
</div> |
| 2603 |
</address> |
| 2604 |
</section> |
| 2605 |
</div> |
| 2606 |
<script>const toc = document.getElementById("toc"); |
| 2607 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2608 |
toc.classList.toggle("active"); |
| 2609 |
}); |
| 2610 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2611 |
toc.classList.remove("active"); |
| 2612 |
}); |
| 2613 |
</script> |
| 2614 |
</body> |
| 2615 |
</html> |