| 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 9173: Default Security Contexts for Bundle Protocol Security (BPSec)</title> |
| 8 |
<meta content="Edward J. Birrane, III" name="author"> |
| 9 |
<meta content="Alex White" name="author"> |
| 10 |
<meta content="Sarah Heiner" name="author"> |
| 11 |
<meta content=" |
| 12 |
|
| 13 |
This document defines default integrity and confidentiality security |
| 14 |
contexts that can be used with Bundle Protocol Security |
| 15 |
(BPSec) implementations. These security contexts are intended to be |
| 16 |
used both for testing the interoperability of BPSec implementations and for providing |
| 17 |
basic security operations when no other security contexts are defined |
| 18 |
or otherwise required for a network. |
| 19 |
|
| 20 |
" name="description"> |
| 21 |
<meta content="xml2rfc 3.12.0" name="generator"> |
| 22 |
<meta content="security" name="keyword"> |
| 23 |
<meta content="bundle" name="keyword"> |
| 24 |
<meta content="integrity" name="keyword"> |
| 25 |
<meta content="confidentiality" name="keyword"> |
| 26 |
<meta content="9173" name="rfc.number"> |
| 27 |
<!-- Generator version information: |
| 28 |
xml2rfc 3.12.0 |
| 29 |
Python 3.6.15 |
| 30 |
appdirs 1.4.4 |
| 31 |
ConfigArgParse 1.4.1 |
| 32 |
google-i18n-address 2.4.0 |
| 33 |
html5lib 1.0.1 |
| 34 |
intervaltree 3.0.2 |
| 35 |
Jinja2 2.11.3 |
| 36 |
kitchen 1.2.6 |
| 37 |
lxml 4.4.2 |
| 38 |
pycairo 1.15.1 |
| 39 |
pycountry 19.8.18 |
| 40 |
pyflakes 2.1.1 |
| 41 |
PyYAML 5.4.1 |
| 42 |
requests 2.24.0 |
| 43 |
setuptools 40.5.0 |
| 44 |
six 1.14.0 |
| 45 |
WeasyPrint 52.5 |
| 46 |
--> |
| 47 |
<link href="rfc9173.xml" rel="alternate" type="application/rfc+xml"> |
| 48 |
<link href="#copyright" rel="license"> |
| 49 |
<style type="text/css">/* |
| 50 |
|
| 51 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 52 |
|
| 53 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 54 |
this can be consolidated so that style settings occur only in one place, but |
| 55 |
for now the contents of this file consists first of the initial CSS work as |
| 56 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 57 |
commented changes found necssary during the development of the v3 |
| 58 |
formatters. |
| 59 |
|
| 60 |
*/ |
| 61 |
|
| 62 |
/* fonts */ |
| 63 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 64 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 65 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 66 |
|
| 67 |
@viewport { |
| 68 |
zoom: 1.0; |
| 69 |
width: extend-to-zoom; |
| 70 |
} |
| 71 |
@-ms-viewport { |
| 72 |
width: extend-to-zoom; |
| 73 |
zoom: 1.0; |
| 74 |
} |
| 75 |
/* general and mobile first */ |
| 76 |
html { |
| 77 |
} |
| 78 |
body { |
| 79 |
max-width: 90%; |
| 80 |
margin: 1.5em auto; |
| 81 |
color: #222; |
| 82 |
background-color: #fff; |
| 83 |
font-size: 14px; |
| 84 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 85 |
line-height: 1.6; |
| 86 |
scroll-behavior: smooth; |
| 87 |
} |
| 88 |
.ears { |
| 89 |
display: none; |
| 90 |
} |
| 91 |
|
| 92 |
/* headings */ |
| 93 |
#title, h1, h2, h3, h4, h5, h6 { |
| 94 |
margin: 1em 0 0.5em; |
| 95 |
font-weight: bold; |
| 96 |
line-height: 1.3; |
| 97 |
} |
| 98 |
#title { |
| 99 |
clear: both; |
| 100 |
border-bottom: 1px solid #ddd; |
| 101 |
margin: 0 0 0.5em 0; |
| 102 |
padding: 1em 0 0.5em; |
| 103 |
} |
| 104 |
.author { |
| 105 |
padding-bottom: 4px; |
| 106 |
} |
| 107 |
h1 { |
| 108 |
font-size: 26px; |
| 109 |
margin: 1em 0; |
| 110 |
} |
| 111 |
h2 { |
| 112 |
font-size: 22px; |
| 113 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 114 |
padding-top: 33px; |
| 115 |
} |
| 116 |
h3 { |
| 117 |
font-size: 18px; |
| 118 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 119 |
padding-top: 42px; |
| 120 |
} |
| 121 |
h4 { |
| 122 |
font-size: 16px; |
| 123 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 124 |
padding-top: 42px; |
| 125 |
} |
| 126 |
h5, h6 { |
| 127 |
font-size: 14px; |
| 128 |
} |
| 129 |
#n-copyright-notice { |
| 130 |
border-bottom: 1px solid #ddd; |
| 131 |
padding-bottom: 1em; |
| 132 |
margin-bottom: 1em; |
| 133 |
} |
| 134 |
/* general structure */ |
| 135 |
p { |
| 136 |
padding: 0; |
| 137 |
margin: 0 0 1em 0; |
| 138 |
text-align: left; |
| 139 |
} |
| 140 |
div, span { |
| 141 |
position: relative; |
| 142 |
} |
| 143 |
div { |
| 144 |
margin: 0; |
| 145 |
} |
| 146 |
.alignRight.art-text { |
| 147 |
background-color: #f9f9f9; |
| 148 |
border: 1px solid #eee; |
| 149 |
border-radius: 3px; |
| 150 |
padding: 1em 1em 0; |
| 151 |
margin-bottom: 1.5em; |
| 152 |
} |
| 153 |
.alignRight.art-text pre { |
| 154 |
padding: 0; |
| 155 |
} |
| 156 |
.alignRight { |
| 157 |
margin: 1em 0; |
| 158 |
} |
| 159 |
.alignRight > *:first-child { |
| 160 |
border: none; |
| 161 |
margin: 0; |
| 162 |
float: right; |
| 163 |
clear: both; |
| 164 |
} |
| 165 |
.alignRight > *:nth-child(2) { |
| 166 |
clear: both; |
| 167 |
display: block; |
| 168 |
border: none; |
| 169 |
} |
| 170 |
svg { |
| 171 |
display: block; |
| 172 |
} |
| 173 |
.alignCenter.art-text { |
| 174 |
background-color: #f9f9f9; |
| 175 |
border: 1px solid #eee; |
| 176 |
border-radius: 3px; |
| 177 |
padding: 1em 1em 0; |
| 178 |
margin-bottom: 1.5em; |
| 179 |
} |
| 180 |
.alignCenter.art-text pre { |
| 181 |
padding: 0; |
| 182 |
} |
| 183 |
.alignCenter { |
| 184 |
margin: 1em 0; |
| 185 |
} |
| 186 |
.alignCenter > *:first-child { |
| 187 |
border: none; |
| 188 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 189 |
support flexbox yet. |
| 190 |
*/ |
| 191 |
display: table; |
| 192 |
margin: 0 auto; |
| 193 |
} |
| 194 |
|
| 195 |
/* lists */ |
| 196 |
ol, ul { |
| 197 |
padding: 0; |
| 198 |
margin: 0 0 1em 2em; |
| 199 |
} |
| 200 |
ol ol, ul ul, ol ul, ul ol { |
| 201 |
margin-left: 1em; |
| 202 |
} |
| 203 |
li { |
| 204 |
margin: 0 0 0.25em 0; |
| 205 |
} |
| 206 |
.ulCompact li { |
| 207 |
margin: 0; |
| 208 |
} |
| 209 |
ul.empty, .ulEmpty { |
| 210 |
list-style-type: none; |
| 211 |
} |
| 212 |
ul.empty li, .ulEmpty li { |
| 213 |
margin-top: 0.5em; |
| 214 |
} |
| 215 |
ul.ulBare, li.ulBare { |
| 216 |
margin-left: 0em !important; |
| 217 |
} |
| 218 |
ul.compact, .ulCompact, |
| 219 |
ol.compact, .olCompact { |
| 220 |
line-height: 100%; |
| 221 |
margin: 0 0 0 2em; |
| 222 |
} |
| 223 |
|
| 224 |
/* definition lists */ |
| 225 |
dl { |
| 226 |
} |
| 227 |
dl > dt { |
| 228 |
float: left; |
| 229 |
margin-right: 1em; |
| 230 |
} |
| 231 |
/* |
| 232 |
dl.nohang > dt { |
| 233 |
float: none; |
| 234 |
} |
| 235 |
*/ |
| 236 |
dl > dd { |
| 237 |
margin-bottom: .8em; |
| 238 |
min-height: 1.3em; |
| 239 |
} |
| 240 |
dl.compact > dd, .dlCompact > dd { |
| 241 |
margin-bottom: 0em; |
| 242 |
} |
| 243 |
dl > dd > dl { |
| 244 |
margin-top: 0.5em; |
| 245 |
margin-bottom: 0em; |
| 246 |
} |
| 247 |
|
| 248 |
/* links */ |
| 249 |
a { |
| 250 |
text-decoration: none; |
| 251 |
} |
| 252 |
a[href] { |
| 253 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 254 |
} |
| 255 |
a[href]:hover { |
| 256 |
background-color: #f2f2f2; |
| 257 |
} |
| 258 |
figcaption a[href], |
| 259 |
a[href].selfRef { |
| 260 |
color: #222; |
| 261 |
} |
| 262 |
/* XXX probably not this: |
| 263 |
a.selfRef:hover { |
| 264 |
background-color: transparent; |
| 265 |
cursor: default; |
| 266 |
} */ |
| 267 |
|
| 268 |
/* Figures */ |
| 269 |
tt, code, pre, code { |
| 270 |
background-color: #f9f9f9; |
| 271 |
font-family: 'Roboto Mono', monospace; |
| 272 |
} |
| 273 |
pre { |
| 274 |
border: 1px solid #eee; |
| 275 |
margin: 0; |
| 276 |
padding: 1em; |
| 277 |
} |
| 278 |
img { |
| 279 |
max-width: 100%; |
| 280 |
} |
| 281 |
figure { |
| 282 |
margin: 0; |
| 283 |
} |
| 284 |
figure blockquote { |
| 285 |
margin: 0.8em 0.4em 0.4em; |
| 286 |
} |
| 287 |
figcaption { |
| 288 |
font-style: italic; |
| 289 |
margin: 0 0 1em 0; |
| 290 |
} |
| 291 |
@media screen { |
| 292 |
pre { |
| 293 |
overflow-x: auto; |
| 294 |
max-width: 100%; |
| 295 |
max-width: calc(100% - 22px); |
| 296 |
} |
| 297 |
} |
| 298 |
|
| 299 |
/* aside, blockquote */ |
| 300 |
aside, blockquote { |
| 301 |
margin-left: 0; |
| 302 |
padding: 1.2em 2em; |
| 303 |
} |
| 304 |
blockquote { |
| 305 |
background-color: #f9f9f9; |
| 306 |
color: #111; /* Arlen: WCAG 2019 */ |
| 307 |
border: 1px solid #ddd; |
| 308 |
border-radius: 3px; |
| 309 |
margin: 1em 0; |
| 310 |
} |
| 311 |
cite { |
| 312 |
display: block; |
| 313 |
text-align: right; |
| 314 |
font-style: italic; |
| 315 |
} |
| 316 |
|
| 317 |
/* tables */ |
| 318 |
table { |
| 319 |
width: 100%; |
| 320 |
margin: 0 0 1em; |
| 321 |
border-collapse: collapse; |
| 322 |
border: 1px solid #eee; |
| 323 |
} |
| 324 |
th, td { |
| 325 |
text-align: left; |
| 326 |
vertical-align: top; |
| 327 |
padding: 0.5em 0.75em; |
| 328 |
} |
| 329 |
th { |
| 330 |
text-align: left; |
| 331 |
background-color: #e9e9e9; |
| 332 |
} |
| 333 |
tr:nth-child(2n+1) > td { |
| 334 |
background-color: #f5f5f5; |
| 335 |
} |
| 336 |
table caption { |
| 337 |
font-style: italic; |
| 338 |
margin: 0; |
| 339 |
padding: 0; |
| 340 |
text-align: left; |
| 341 |
} |
| 342 |
table p { |
| 343 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 344 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 345 |
margin: 0; |
| 346 |
} |
| 347 |
|
| 348 |
/* pilcrow */ |
| 349 |
a.pilcrow { |
| 350 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 351 |
text-decoration: none; |
| 352 |
visibility: hidden; |
| 353 |
user-select: none; |
| 354 |
-ms-user-select: none; |
| 355 |
-o-user-select:none; |
| 356 |
-moz-user-select: none; |
| 357 |
-khtml-user-select: none; |
| 358 |
-webkit-user-select: none; |
| 359 |
-webkit-touch-callout: none; |
| 360 |
} |
| 361 |
@media screen { |
| 362 |
aside:hover > a.pilcrow, |
| 363 |
p:hover > a.pilcrow, |
| 364 |
blockquote:hover > a.pilcrow, |
| 365 |
div:hover > a.pilcrow, |
| 366 |
li:hover > a.pilcrow, |
| 367 |
pre:hover > a.pilcrow { |
| 368 |
visibility: visible; |
| 369 |
} |
| 370 |
a.pilcrow:hover { |
| 371 |
background-color: transparent; |
| 372 |
} |
| 373 |
} |
| 374 |
|
| 375 |
/* misc */ |
| 376 |
hr { |
| 377 |
border: 0; |
| 378 |
border-top: 1px solid #eee; |
| 379 |
} |
| 380 |
.bcp14 { |
| 381 |
font-variant: small-caps; |
| 382 |
} |
| 383 |
|
| 384 |
.role { |
| 385 |
font-variant: all-small-caps; |
| 386 |
} |
| 387 |
|
| 388 |
/* info block */ |
| 389 |
#identifiers { |
| 390 |
margin: 0; |
| 391 |
font-size: 0.9em; |
| 392 |
} |
| 393 |
#identifiers dt { |
| 394 |
width: 3em; |
| 395 |
clear: left; |
| 396 |
} |
| 397 |
#identifiers dd { |
| 398 |
float: left; |
| 399 |
margin-bottom: 0; |
| 400 |
} |
| 401 |
/* Fix PDF info block run off issue */ |
| 402 |
@media print { |
| 403 |
#identifiers dd { |
| 404 |
float: none; |
| 405 |
} |
| 406 |
} |
| 407 |
#identifiers .authors .author { |
| 408 |
display: inline-block; |
| 409 |
margin-right: 1.5em; |
| 410 |
} |
| 411 |
#identifiers .authors .org { |
| 412 |
font-style: italic; |
| 413 |
} |
| 414 |
|
| 415 |
/* The prepared/rendered info at the very bottom of the page */ |
| 416 |
.docInfo { |
| 417 |
color: #666; /* Arlen: WCAG 2019 */ |
| 418 |
font-size: 0.9em; |
| 419 |
font-style: italic; |
| 420 |
margin-top: 2em; |
| 421 |
} |
| 422 |
.docInfo .prepared { |
| 423 |
float: left; |
| 424 |
} |
| 425 |
.docInfo .prepared { |
| 426 |
float: right; |
| 427 |
} |
| 428 |
|
| 429 |
/* table of contents */ |
| 430 |
#toc { |
| 431 |
padding: 0.75em 0 2em 0; |
| 432 |
margin-bottom: 1em; |
| 433 |
} |
| 434 |
nav.toc ul { |
| 435 |
margin: 0 0.5em 0 0; |
| 436 |
padding: 0; |
| 437 |
list-style: none; |
| 438 |
} |
| 439 |
nav.toc li { |
| 440 |
line-height: 1.3em; |
| 441 |
margin: 0.75em 0; |
| 442 |
padding-left: 1.2em; |
| 443 |
text-indent: -1.2em; |
| 444 |
} |
| 445 |
/* references */ |
| 446 |
.references dt { |
| 447 |
text-align: right; |
| 448 |
font-weight: bold; |
| 449 |
min-width: 7em; |
| 450 |
} |
| 451 |
.references dd { |
| 452 |
margin-left: 8em; |
| 453 |
overflow: auto; |
| 454 |
} |
| 455 |
|
| 456 |
.refInstance { |
| 457 |
margin-bottom: 1.25em; |
| 458 |
} |
| 459 |
|
| 460 |
.references .ascii { |
| 461 |
margin-bottom: 0.25em; |
| 462 |
} |
| 463 |
|
| 464 |
/* index */ |
| 465 |
.index ul { |
| 466 |
margin: 0 0 0 1em; |
| 467 |
padding: 0; |
| 468 |
list-style: none; |
| 469 |
} |
| 470 |
.index ul ul { |
| 471 |
margin: 0; |
| 472 |
} |
| 473 |
.index li { |
| 474 |
margin: 0; |
| 475 |
text-indent: -2em; |
| 476 |
padding-left: 2em; |
| 477 |
padding-bottom: 5px; |
| 478 |
} |
| 479 |
.indexIndex { |
| 480 |
margin: 0.5em 0 1em; |
| 481 |
} |
| 482 |
.index a { |
| 483 |
font-weight: 700; |
| 484 |
} |
| 485 |
/* make the index two-column on all but the smallest screens */ |
| 486 |
@media (min-width: 600px) { |
| 487 |
.index ul { |
| 488 |
-moz-column-count: 2; |
| 489 |
-moz-column-gap: 20px; |
| 490 |
} |
| 491 |
.index ul ul { |
| 492 |
-moz-column-count: 1; |
| 493 |
-moz-column-gap: 0; |
| 494 |
} |
| 495 |
} |
| 496 |
|
| 497 |
/* authors */ |
| 498 |
address.vcard { |
| 499 |
font-style: normal; |
| 500 |
margin: 1em 0; |
| 501 |
} |
| 502 |
|
| 503 |
address.vcard .nameRole { |
| 504 |
font-weight: 700; |
| 505 |
margin-left: 0; |
| 506 |
} |
| 507 |
address.vcard .label { |
| 508 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 509 |
margin: 0.5em 0; |
| 510 |
} |
| 511 |
address.vcard .type { |
| 512 |
display: none; |
| 513 |
} |
| 514 |
.alternative-contact { |
| 515 |
margin: 1.5em 0 1em; |
| 516 |
} |
| 517 |
hr.addr { |
| 518 |
border-top: 1px dashed; |
| 519 |
margin: 0; |
| 520 |
color: #ddd; |
| 521 |
max-width: calc(100% - 16px); |
| 522 |
} |
| 523 |
|
| 524 |
/* temporary notes */ |
| 525 |
.rfcEditorRemove::before { |
| 526 |
position: absolute; |
| 527 |
top: 0.2em; |
| 528 |
right: 0.2em; |
| 529 |
padding: 0.2em; |
| 530 |
content: "The RFC Editor will remove this note"; |
| 531 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 532 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 533 |
} |
| 534 |
.rfcEditorRemove { |
| 535 |
position: relative; |
| 536 |
padding-top: 1.8em; |
| 537 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 538 |
border-radius: 3px; |
| 539 |
} |
| 540 |
.cref { |
| 541 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 542 |
padding: 2px 4px; |
| 543 |
} |
| 544 |
.crefSource { |
| 545 |
font-style: italic; |
| 546 |
} |
| 547 |
/* alternative layout for smaller screens */ |
| 548 |
@media screen and (max-width: 1023px) { |
| 549 |
body { |
| 550 |
padding-top: 2em; |
| 551 |
} |
| 552 |
#title { |
| 553 |
padding: 1em 0; |
| 554 |
} |
| 555 |
h1 { |
| 556 |
font-size: 24px; |
| 557 |
} |
| 558 |
h2 { |
| 559 |
font-size: 20px; |
| 560 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 561 |
padding-top: 38px; |
| 562 |
} |
| 563 |
#identifiers dd { |
| 564 |
max-width: 60%; |
| 565 |
} |
| 566 |
#toc { |
| 567 |
position: fixed; |
| 568 |
z-index: 2; |
| 569 |
top: 0; |
| 570 |
right: 0; |
| 571 |
padding: 0; |
| 572 |
margin: 0; |
| 573 |
background-color: inherit; |
| 574 |
border-bottom: 1px solid #ccc; |
| 575 |
} |
| 576 |
#toc h2 { |
| 577 |
margin: -1px 0 0 0; |
| 578 |
padding: 4px 0 4px 6px; |
| 579 |
padding-right: 1em; |
| 580 |
min-width: 190px; |
| 581 |
font-size: 1.1em; |
| 582 |
text-align: right; |
| 583 |
background-color: #444; |
| 584 |
color: white; |
| 585 |
cursor: pointer; |
| 586 |
} |
| 587 |
#toc h2::before { /* css hamburger */ |
| 588 |
float: right; |
| 589 |
position: relative; |
| 590 |
width: 1em; |
| 591 |
height: 1px; |
| 592 |
left: -164px; |
| 593 |
margin: 6px 0 0 0; |
| 594 |
background: white none repeat scroll 0 0; |
| 595 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 596 |
content: ""; |
| 597 |
} |
| 598 |
#toc nav { |
| 599 |
display: none; |
| 600 |
padding: 0.5em 1em 1em; |
| 601 |
overflow: auto; |
| 602 |
height: calc(100vh - 48px); |
| 603 |
border-left: 1px solid #ddd; |
| 604 |
} |
| 605 |
} |
| 606 |
|
| 607 |
/* alternative layout for wide screens */ |
| 608 |
@media screen and (min-width: 1024px) { |
| 609 |
body { |
| 610 |
max-width: 724px; |
| 611 |
margin: 42px auto; |
| 612 |
padding-left: 1.5em; |
| 613 |
padding-right: 29em; |
| 614 |
} |
| 615 |
#toc { |
| 616 |
position: fixed; |
| 617 |
top: 42px; |
| 618 |
right: 42px; |
| 619 |
width: 25%; |
| 620 |
margin: 0; |
| 621 |
padding: 0 1em; |
| 622 |
z-index: 1; |
| 623 |
} |
| 624 |
#toc h2 { |
| 625 |
border-top: none; |
| 626 |
border-bottom: 1px solid #ddd; |
| 627 |
font-size: 1em; |
| 628 |
font-weight: normal; |
| 629 |
margin: 0; |
| 630 |
padding: 0.25em 1em 1em 0; |
| 631 |
} |
| 632 |
#toc nav { |
| 633 |
display: block; |
| 634 |
height: calc(90vh - 84px); |
| 635 |
bottom: 0; |
| 636 |
padding: 0.5em 0 0; |
| 637 |
overflow: auto; |
| 638 |
} |
| 639 |
img { /* future proofing */ |
| 640 |
max-width: 100%; |
| 641 |
height: auto; |
| 642 |
} |
| 643 |
} |
| 644 |
|
| 645 |
/* pagination */ |
| 646 |
@media print { |
| 647 |
body { |
| 648 |
|
| 649 |
width: 100%; |
| 650 |
} |
| 651 |
p { |
| 652 |
orphans: 3; |
| 653 |
widows: 3; |
| 654 |
} |
| 655 |
#n-copyright-notice { |
| 656 |
border-bottom: none; |
| 657 |
} |
| 658 |
#toc, #n-introduction { |
| 659 |
page-break-before: always; |
| 660 |
} |
| 661 |
#toc { |
| 662 |
border-top: none; |
| 663 |
padding-top: 0; |
| 664 |
} |
| 665 |
figure, pre { |
| 666 |
page-break-inside: avoid; |
| 667 |
} |
| 668 |
figure { |
| 669 |
overflow: scroll; |
| 670 |
} |
| 671 |
h1, h2, h3, h4, h5, h6 { |
| 672 |
page-break-after: avoid; |
| 673 |
} |
| 674 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 675 |
page-break-before: avoid; |
| 676 |
} |
| 677 |
pre { |
| 678 |
white-space: pre-wrap; |
| 679 |
word-wrap: break-word; |
| 680 |
font-size: 10pt; |
| 681 |
} |
| 682 |
table { |
| 683 |
border: 1px solid #ddd; |
| 684 |
} |
| 685 |
td { |
| 686 |
border-top: 1px solid #ddd; |
| 687 |
} |
| 688 |
} |
| 689 |
|
| 690 |
/* This is commented out here, as the string-set: doesn't |
| 691 |
pass W3C validation currently */ |
| 692 |
/* |
| 693 |
.ears thead .left { |
| 694 |
string-set: ears-top-left content(); |
| 695 |
} |
| 696 |
|
| 697 |
.ears thead .center { |
| 698 |
string-set: ears-top-center content(); |
| 699 |
} |
| 700 |
|
| 701 |
.ears thead .right { |
| 702 |
string-set: ears-top-right content(); |
| 703 |
} |
| 704 |
|
| 705 |
.ears tfoot .left { |
| 706 |
string-set: ears-bottom-left content(); |
| 707 |
} |
| 708 |
|
| 709 |
.ears tfoot .center { |
| 710 |
string-set: ears-bottom-center content(); |
| 711 |
} |
| 712 |
|
| 713 |
.ears tfoot .right { |
| 714 |
string-set: ears-bottom-right content(); |
| 715 |
} |
| 716 |
*/ |
| 717 |
|
| 718 |
@page :first { |
| 719 |
padding-top: 0; |
| 720 |
@top-left { |
| 721 |
content: normal; |
| 722 |
border: none; |
| 723 |
} |
| 724 |
@top-center { |
| 725 |
content: normal; |
| 726 |
border: none; |
| 727 |
} |
| 728 |
@top-right { |
| 729 |
content: normal; |
| 730 |
border: none; |
| 731 |
} |
| 732 |
} |
| 733 |
|
| 734 |
@page { |
| 735 |
size: A4; |
| 736 |
margin-bottom: 45mm; |
| 737 |
padding-top: 20px; |
| 738 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 739 |
the content depends on the document */ |
| 740 |
/* |
| 741 |
@top-left { |
| 742 |
content: 'Internet-Draft'; |
| 743 |
vertical-align: bottom; |
| 744 |
border-bottom: solid 1px #ccc; |
| 745 |
} |
| 746 |
@top-left { |
| 747 |
content: string(ears-top-left); |
| 748 |
vertical-align: bottom; |
| 749 |
border-bottom: solid 1px #ccc; |
| 750 |
} |
| 751 |
@top-center { |
| 752 |
content: string(ears-top-center); |
| 753 |
vertical-align: bottom; |
| 754 |
border-bottom: solid 1px #ccc; |
| 755 |
} |
| 756 |
@top-right { |
| 757 |
content: string(ears-top-right); |
| 758 |
vertical-align: bottom; |
| 759 |
border-bottom: solid 1px #ccc; |
| 760 |
} |
| 761 |
@bottom-left { |
| 762 |
content: string(ears-bottom-left); |
| 763 |
vertical-align: top; |
| 764 |
border-top: solid 1px #ccc; |
| 765 |
} |
| 766 |
@bottom-center { |
| 767 |
content: string(ears-bottom-center); |
| 768 |
vertical-align: top; |
| 769 |
border-top: solid 1px #ccc; |
| 770 |
} |
| 771 |
@bottom-right { |
| 772 |
content: '[Page ' counter(page) ']'; |
| 773 |
vertical-align: top; |
| 774 |
border-top: solid 1px #ccc; |
| 775 |
} |
| 776 |
*/ |
| 777 |
|
| 778 |
} |
| 779 |
|
| 780 |
/* Changes introduced to fix issues found during implementation */ |
| 781 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 782 |
a { |
| 783 |
z-index: 2; |
| 784 |
} |
| 785 |
/* Separate body from document info even without intervening H1 */ |
| 786 |
section { |
| 787 |
clear: both; |
| 788 |
} |
| 789 |
|
| 790 |
|
| 791 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 792 |
.author { |
| 793 |
vertical-align: top; |
| 794 |
} |
| 795 |
|
| 796 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 797 |
#identifiers dt { |
| 798 |
width: 8em; |
| 799 |
} |
| 800 |
|
| 801 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 802 |
#identifiers dd { |
| 803 |
margin-left: 1em; |
| 804 |
} |
| 805 |
|
| 806 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 807 |
#toc { |
| 808 |
background-color: white; |
| 809 |
} |
| 810 |
|
| 811 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 812 |
@media screen and (max-width: 1023px) { |
| 813 |
#toc h2 a, |
| 814 |
#toc h2 a:link, |
| 815 |
#toc h2 a:focus, |
| 816 |
#toc h2 a:hover, |
| 817 |
#toc a.toplink, |
| 818 |
#toc a.toplink:hover { |
| 819 |
color: white; |
| 820 |
background-color: #444; |
| 821 |
text-decoration: none; |
| 822 |
} |
| 823 |
} |
| 824 |
|
| 825 |
/* Give the bottom of the ToC some whitespace */ |
| 826 |
@media screen and (min-width: 1024px) { |
| 827 |
#toc { |
| 828 |
padding: 0 0 1em 1em; |
| 829 |
} |
| 830 |
} |
| 831 |
|
| 832 |
/* Style section numbers with more space between number and title */ |
| 833 |
.section-number { |
| 834 |
padding-right: 0.5em; |
| 835 |
} |
| 836 |
|
| 837 |
/* prevent monospace from becoming overly large */ |
| 838 |
tt, code, pre, code { |
| 839 |
font-size: 95%; |
| 840 |
} |
| 841 |
|
| 842 |
/* Fix the height/width aspect for ascii art*/ |
| 843 |
pre.sourcecode, |
| 844 |
.art-text pre { |
| 845 |
line-height: 1.12; |
| 846 |
} |
| 847 |
|
| 848 |
|
| 849 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 850 |
a.toplink { |
| 851 |
float: right; |
| 852 |
margin-right: 0.5em; |
| 853 |
} |
| 854 |
|
| 855 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 856 |
dl > dt, |
| 857 |
dl.dlParallel > dt { |
| 858 |
float: left; |
| 859 |
margin-right: 1em; |
| 860 |
} |
| 861 |
dl.dlNewline > dt { |
| 862 |
float: none; |
| 863 |
} |
| 864 |
|
| 865 |
/* Provide styling for table cell text alignment */ |
| 866 |
table td.text-left, |
| 867 |
table th.text-left { |
| 868 |
text-align: left; |
| 869 |
} |
| 870 |
table td.text-center, |
| 871 |
table th.text-center { |
| 872 |
text-align: center; |
| 873 |
} |
| 874 |
table td.text-right, |
| 875 |
table th.text-right { |
| 876 |
text-align: right; |
| 877 |
} |
| 878 |
|
| 879 |
/* Make the alternative author contact informatio look less like just another |
| 880 |
author, and group it closer with the primary author contact information */ |
| 881 |
.alternative-contact { |
| 882 |
margin: 0.5em 0 0.25em 0; |
| 883 |
} |
| 884 |
address .non-ascii { |
| 885 |
margin: 0 0 0 2em; |
| 886 |
} |
| 887 |
|
| 888 |
/* With it being possible to set tables with alignment |
| 889 |
left, center, and right, { width: 100%; } does not make sense */ |
| 890 |
table { |
| 891 |
width: auto; |
| 892 |
} |
| 893 |
|
| 894 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 895 |
because of a long floating dt label.*/ |
| 896 |
.references dd { |
| 897 |
overflow: visible; |
| 898 |
} |
| 899 |
|
| 900 |
/* Control caption placement */ |
| 901 |
caption { |
| 902 |
caption-side: bottom; |
| 903 |
} |
| 904 |
|
| 905 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 906 |
script don't end up on the other side of the page. */ |
| 907 |
|
| 908 |
address.vcard { |
| 909 |
max-width: 30em; |
| 910 |
margin-right: auto; |
| 911 |
} |
| 912 |
|
| 913 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 914 |
address div.left { |
| 915 |
text-align: left; |
| 916 |
} |
| 917 |
address div.right { |
| 918 |
text-align: right; |
| 919 |
} |
| 920 |
|
| 921 |
/* Provide table alignment support. We can't use the alignX classes above |
| 922 |
since they do unwanted things with caption and other styling. */ |
| 923 |
table.right { |
| 924 |
margin-left: auto; |
| 925 |
margin-right: 0; |
| 926 |
} |
| 927 |
table.center { |
| 928 |
margin-left: auto; |
| 929 |
margin-right: auto; |
| 930 |
} |
| 931 |
table.left { |
| 932 |
margin-left: 0; |
| 933 |
margin-right: auto; |
| 934 |
} |
| 935 |
|
| 936 |
/* Give the table caption label the same styling as the figcaption */ |
| 937 |
caption a[href] { |
| 938 |
color: #222; |
| 939 |
} |
| 940 |
|
| 941 |
@media print { |
| 942 |
.toplink { |
| 943 |
display: none; |
| 944 |
} |
| 945 |
|
| 946 |
/* avoid overwriting the top border line with the ToC header */ |
| 947 |
#toc { |
| 948 |
padding-top: 1px; |
| 949 |
} |
| 950 |
|
| 951 |
/* Avoid page breaks inside dl and author address entries */ |
| 952 |
.vcard { |
| 953 |
page-break-inside: avoid; |
| 954 |
} |
| 955 |
|
| 956 |
} |
| 957 |
/* Tweak the bcp14 keyword presentation */ |
| 958 |
.bcp14 { |
| 959 |
font-variant: small-caps; |
| 960 |
font-weight: bold; |
| 961 |
font-size: 0.9em; |
| 962 |
} |
| 963 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 964 |
h2 { |
| 965 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 966 |
padding-top: 31px; |
| 967 |
} |
| 968 |
h3 { |
| 969 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 970 |
padding-top: 24px; |
| 971 |
} |
| 972 |
h4 { |
| 973 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 974 |
padding-top: 24px; |
| 975 |
} |
| 976 |
/* Float artwork pilcrow to the right */ |
| 977 |
@media screen { |
| 978 |
.artwork a.pilcrow { |
| 979 |
display: block; |
| 980 |
line-height: 0.7; |
| 981 |
margin-top: 0.15em; |
| 982 |
} |
| 983 |
} |
| 984 |
/* Make pilcrows on dd visible */ |
| 985 |
@media screen { |
| 986 |
dd:hover > a.pilcrow { |
| 987 |
visibility: visible; |
| 988 |
} |
| 989 |
} |
| 990 |
/* Make the placement of figcaption match that of a table's caption |
| 991 |
by removing the figure's added bottom margin */ |
| 992 |
.alignLeft.art-text, |
| 993 |
.alignCenter.art-text, |
| 994 |
.alignRight.art-text { |
| 995 |
margin-bottom: 0; |
| 996 |
} |
| 997 |
.alignLeft, |
| 998 |
.alignCenter, |
| 999 |
.alignRight { |
| 1000 |
margin: 1em 0 0 0; |
| 1001 |
} |
| 1002 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 1003 |
possibly even requiring a new line */ |
| 1004 |
@media print { |
| 1005 |
a.pilcrow { |
| 1006 |
display: none; |
| 1007 |
} |
| 1008 |
} |
| 1009 |
/* Styling for the external metadata */ |
| 1010 |
div#external-metadata { |
| 1011 |
background-color: #eee; |
| 1012 |
padding: 0.5em; |
| 1013 |
margin-bottom: 0.5em; |
| 1014 |
display: none; |
| 1015 |
} |
| 1016 |
div#internal-metadata { |
| 1017 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1018 |
} |
| 1019 |
/* Styling for title RFC Number */ |
| 1020 |
h1#rfcnum { |
| 1021 |
clear: both; |
| 1022 |
margin: 0 0 -1em; |
| 1023 |
padding: 1em 0 0 0; |
| 1024 |
} |
| 1025 |
/* Make .olPercent look the same as <ol><li> */ |
| 1026 |
dl.olPercent > dd { |
| 1027 |
margin-bottom: 0.25em; |
| 1028 |
min-height: initial; |
| 1029 |
} |
| 1030 |
/* Give aside some styling to set it apart */ |
| 1031 |
aside { |
| 1032 |
border-left: 1px solid #ddd; |
| 1033 |
margin: 1em 0 1em 2em; |
| 1034 |
padding: 0.2em 2em; |
| 1035 |
} |
| 1036 |
aside > dl, |
| 1037 |
aside > ol, |
| 1038 |
aside > ul, |
| 1039 |
aside > table, |
| 1040 |
aside > p { |
| 1041 |
margin-bottom: 0.5em; |
| 1042 |
} |
| 1043 |
/* Additional page break settings */ |
| 1044 |
@media print { |
| 1045 |
figcaption, table caption { |
| 1046 |
page-break-before: avoid; |
| 1047 |
} |
| 1048 |
} |
| 1049 |
/* Font size adjustments for print */ |
| 1050 |
@media print { |
| 1051 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1052 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1053 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1054 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1055 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1056 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1057 |
} |
| 1058 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1059 |
@media print { |
| 1060 |
.artwork, |
| 1061 |
.sourcecode { |
| 1062 |
margin-bottom: 1em; |
| 1063 |
} |
| 1064 |
} |
| 1065 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1066 |
table { |
| 1067 |
min-width: 20em; |
| 1068 |
} |
| 1069 |
/* ol type a */ |
| 1070 |
ol.type-a { list-style-type: lower-alpha; } |
| 1071 |
ol.type-A { list-style-type: upper-alpha; } |
| 1072 |
ol.type-i { list-style-type: lower-roman; } |
| 1073 |
ol.type-I { list-style-type: lower-roman; } |
| 1074 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1075 |
and increase the contrast between border and odd row background sligthtly */ |
| 1076 |
table { |
| 1077 |
border: 1px solid #ddd; |
| 1078 |
} |
| 1079 |
td { |
| 1080 |
border-top: 1px solid #ddd; |
| 1081 |
} |
| 1082 |
tr:nth-child(2n+1) > td { |
| 1083 |
background-color: #f8f8f8; |
| 1084 |
} |
| 1085 |
/* Use style rules to govern display of the TOC. */ |
| 1086 |
@media screen and (max-width: 1023px) { |
| 1087 |
#toc nav { display: none; } |
| 1088 |
#toc.active nav { display: block; } |
| 1089 |
} |
| 1090 |
/* Add support for keepWithNext */ |
| 1091 |
.keepWithNext { |
| 1092 |
break-after: avoid-page; |
| 1093 |
break-after: avoid-page; |
| 1094 |
} |
| 1095 |
/* Add support for keepWithPrevious */ |
| 1096 |
.keepWithPrevious { |
| 1097 |
break-before: avoid-page; |
| 1098 |
} |
| 1099 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1100 |
figure, pre, table, .artwork, .sourcecode { |
| 1101 |
break-before: auto; |
| 1102 |
break-after: auto; |
| 1103 |
} |
| 1104 |
/* Avoid breaks between <dt> and <dd> */ |
| 1105 |
dl { |
| 1106 |
break-before: auto; |
| 1107 |
break-inside: auto; |
| 1108 |
} |
| 1109 |
dt { |
| 1110 |
break-before: auto; |
| 1111 |
break-after: avoid-page; |
| 1112 |
} |
| 1113 |
dd { |
| 1114 |
break-before: avoid-page; |
| 1115 |
break-after: auto; |
| 1116 |
orphans: 3; |
| 1117 |
widows: 3 |
| 1118 |
} |
| 1119 |
span.break, dd.break { |
| 1120 |
margin-bottom: 0; |
| 1121 |
min-height: 0; |
| 1122 |
break-before: auto; |
| 1123 |
break-inside: auto; |
| 1124 |
break-after: auto; |
| 1125 |
} |
| 1126 |
/* Undo break-before ToC */ |
| 1127 |
@media print { |
| 1128 |
#toc { |
| 1129 |
break-before: auto; |
| 1130 |
} |
| 1131 |
} |
| 1132 |
/* Text in compact lists should not get extra bottim margin space, |
| 1133 |
since that would makes the list not compact */ |
| 1134 |
ul.compact p, .ulCompact p, |
| 1135 |
ol.compact p, .olCompact p { |
| 1136 |
margin: 0; |
| 1137 |
} |
| 1138 |
/* But the list as a whole needs the extra space at the end */ |
| 1139 |
section ul.compact, |
| 1140 |
section .ulCompact, |
| 1141 |
section ol.compact, |
| 1142 |
section .olCompact { |
| 1143 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1144 |
} |
| 1145 |
/* The tt and code background above interferes with for instance table cell |
| 1146 |
backgrounds. Changed to something a bit more selective. */ |
| 1147 |
tt, code { |
| 1148 |
background-color: transparent; |
| 1149 |
} |
| 1150 |
p tt, p code, li tt, li code { |
| 1151 |
background-color: #f8f8f8; |
| 1152 |
} |
| 1153 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1154 |
pre { |
| 1155 |
margin-top: 0.5px; |
| 1156 |
} |
| 1157 |
/* Tweak the comact list text */ |
| 1158 |
ul.compact, .ulCompact, |
| 1159 |
ol.compact, .olCompact, |
| 1160 |
dl.compact, .dlCompact { |
| 1161 |
line-height: normal; |
| 1162 |
} |
| 1163 |
/* Don't add top margin for nested lists */ |
| 1164 |
li > ul, li > ol, li > dl, |
| 1165 |
dd > ul, dd > ol, dd > dl, |
| 1166 |
dl > dd > dl { |
| 1167 |
margin-top: initial; |
| 1168 |
} |
| 1169 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1170 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1171 |
dd > div.artwork:first-child, |
| 1172 |
dd > aside:first-child, |
| 1173 |
dd > figure:first-child, |
| 1174 |
dd > ol:first-child, |
| 1175 |
dd > div:first-child > pre.sourcecode, |
| 1176 |
dd > table:first-child, |
| 1177 |
dd > ul:first-child { |
| 1178 |
clear: left; |
| 1179 |
} |
| 1180 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1181 |
dt+dd:empty::before{ |
| 1182 |
content: "\00a0"; |
| 1183 |
} |
| 1184 |
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */ |
| 1185 |
li > p { |
| 1186 |
margin-bottom: 0.5em |
| 1187 |
} |
| 1188 |
/* Don't let p margin spill out from inside list items */ |
| 1189 |
li > p:last-of-type { |
| 1190 |
margin-bottom: 0; |
| 1191 |
} |
| 1192 |
</style> |
| 1193 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1194 |
<link href="https://dx.doi.org/10.17487/rfc9173" rel="alternate"> |
| 1195 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1196 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-dtn-bpsec-default-sc-11" rel="prev"> |
| 1197 |
</head> |
| 1198 |
<body> |
| 1199 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1200 |
<table class="ears"> |
| 1201 |
<thead><tr> |
| 1202 |
<td class="left">RFC 9173</td> |
| 1203 |
<td class="center">BPSec Default Security Contexts</td> |
| 1204 |
<td class="right">January 2022</td> |
| 1205 |
</tr></thead> |
| 1206 |
<tfoot><tr> |
| 1207 |
<td class="left">Birrane, III, et al.</td> |
| 1208 |
<td class="center">Standards Track</td> |
| 1209 |
<td class="right">[Page]</td> |
| 1210 |
</tr></tfoot> |
| 1211 |
</table> |
| 1212 |
<div id="external-metadata" class="document-information"></div> |
| 1213 |
<div id="internal-metadata" class="document-information"> |
| 1214 |
<dl id="identifiers"> |
| 1215 |
<dt class="label-stream">Stream:</dt> |
| 1216 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1217 |
<dt class="label-rfc">RFC:</dt> |
| 1218 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9173" class="eref">9173</a></dd> |
| 1219 |
<dt class="label-category">Category:</dt> |
| 1220 |
<dd class="category">Standards Track</dd> |
| 1221 |
<dt class="label-published">Published:</dt> |
| 1222 |
<dd class="published"> |
| 1223 |
<time datetime="2022-01" class="published">January 2022</time> |
| 1224 |
</dd> |
| 1225 |
<dt class="label-issn">ISSN:</dt> |
| 1226 |
<dd class="issn">2070-1721</dd> |
| 1227 |
<dt class="label-authors">Authors:</dt> |
| 1228 |
<dd class="authors"> |
| 1229 |
<div class="author"> |
| 1230 |
<div class="author-name">E. Birrane, III</div> |
| 1231 |
<div class="org">JHU/APL</div> |
| 1232 |
</div> |
| 1233 |
<div class="author"> |
| 1234 |
<div class="author-name">A. White</div> |
| 1235 |
<div class="org">JHU/APL</div> |
| 1236 |
</div> |
| 1237 |
<div class="author"> |
| 1238 |
<div class="author-name">S. Heiner</div> |
| 1239 |
<div class="org">JHU/APL</div> |
| 1240 |
</div> |
| 1241 |
</dd> |
| 1242 |
</dl> |
| 1243 |
</div> |
| 1244 |
<h1 id="rfcnum">RFC 9173</h1> |
| 1245 |
<h1 id="title">Default Security Contexts for Bundle Protocol Security (BPSec)</h1> |
| 1246 |
<section id="section-abstract"> |
| 1247 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1248 |
<p id="section-abstract-1"> |
| 1249 |
This document defines default integrity and confidentiality security |
| 1250 |
contexts that can be used with Bundle Protocol Security |
| 1251 |
(BPSec) implementations. These security contexts are intended to be |
| 1252 |
used both for testing the interoperability of BPSec implementations and for providing |
| 1253 |
basic security operations when no other security contexts are defined |
| 1254 |
or otherwise required for a network.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1255 |
</section> |
| 1256 |
<div id="status-of-memo"> |
| 1257 |
<section id="section-boilerplate.1"> |
| 1258 |
<h2 id="name-status-of-this-memo"> |
| 1259 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1260 |
</h2> |
| 1261 |
<p id="section-boilerplate.1-1"> |
| 1262 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1263 |
<p id="section-boilerplate.1-2"> |
| 1264 |
This document is a product of the Internet Engineering Task Force |
| 1265 |
(IETF). It represents the consensus of the IETF community. It has |
| 1266 |
received public review and has been approved for publication by |
| 1267 |
the Internet Engineering Steering Group (IESG). Further |
| 1268 |
information on Internet Standards is available in Section 2 of |
| 1269 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1270 |
<p id="section-boilerplate.1-3"> |
| 1271 |
Information about the current status of this document, any |
| 1272 |
errata, and how to provide feedback on it may be obtained at |
| 1273 |
<span><a href="https://www.rfc-editor.org/info/rfc9173">https://www.rfc-editor.org/info/rfc9173</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1274 |
</section> |
| 1275 |
</div> |
| 1276 |
<div id="copyright"> |
| 1277 |
<section id="section-boilerplate.2"> |
| 1278 |
<h2 id="name-copyright-notice"> |
| 1279 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1280 |
</h2> |
| 1281 |
<p id="section-boilerplate.2-1"> |
| 1282 |
Copyright (c) 2022 IETF Trust and the persons identified as the |
| 1283 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1284 |
<p id="section-boilerplate.2-2"> |
| 1285 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1286 |
Provisions Relating to IETF Documents |
| 1287 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1288 |
publication of this document. Please review these documents |
| 1289 |
carefully, as they describe your rights and restrictions with |
| 1290 |
respect to this document. Code Components extracted from this |
| 1291 |
document must include Revised BSD License text as described in |
| 1292 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1293 |
warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1294 |
</section> |
| 1295 |
</div> |
| 1296 |
<div id="toc"> |
| 1297 |
<section id="section-toc.1"> |
| 1298 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1299 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1300 |
</h2> |
| 1301 |
<nav class="toc"><ul class="compact toc ulBare ulEmpty"> |
| 1302 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1"> |
| 1303 |
<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></p> |
| 1304 |
</li> |
| 1305 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2"> |
| 1306 |
<p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>. <a href="#name-requirements-language" class="xref">Requirements Language</a></p> |
| 1307 |
</li> |
| 1308 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3"> |
| 1309 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-integrity-security-context-" class="xref">Integrity Security Context BIB-HMAC-SHA2</a></p> |
| 1310 |
<ul class="compact toc ulBare ulEmpty"> |
| 1311 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1"> |
| 1312 |
<p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-overview" class="xref">Overview</a></p> |
| 1313 |
</li> |
| 1314 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2"> |
| 1315 |
<p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>. <a href="#name-scope" class="xref">Scope</a></p> |
| 1316 |
</li> |
| 1317 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.3"> |
| 1318 |
<p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>. <a href="#name-parameters" class="xref">Parameters</a></p> |
| 1319 |
<ul class="compact toc ulBare ulEmpty"> |
| 1320 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.3.2.1"> |
| 1321 |
<p id="section-toc.1-1.3.2.3.2.1.1"><a href="#section-3.3.1" class="xref">3.3.1</a>. <a href="#name-sha-variant" class="xref">SHA Variant</a></p> |
| 1322 |
</li> |
| 1323 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.3.2.2"> |
| 1324 |
<p id="section-toc.1-1.3.2.3.2.2.1"><a href="#section-3.3.2" class="xref">3.3.2</a>. <a href="#name-wrapped-key" class="xref">Wrapped Key</a></p> |
| 1325 |
</li> |
| 1326 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.3.2.3"> |
| 1327 |
<p id="section-toc.1-1.3.2.3.2.3.1"><a href="#section-3.3.3" class="xref">3.3.3</a>. <a href="#name-integrity-scope-flags" class="xref">Integrity Scope Flags</a></p> |
| 1328 |
</li> |
| 1329 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.3.2.4"> |
| 1330 |
<p id="section-toc.1-1.3.2.3.2.4.1"><a href="#section-3.3.4" class="xref">3.3.4</a>. <a href="#name-enumerations" class="xref">Enumerations</a></p> |
| 1331 |
</li> |
| 1332 |
</ul> |
| 1333 |
</li> |
| 1334 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.4"> |
| 1335 |
<p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>. <a href="#name-results" class="xref">Results</a></p> |
| 1336 |
</li> |
| 1337 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.5"> |
| 1338 |
<p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>. <a href="#name-key-considerations" class="xref">Key Considerations</a></p> |
| 1339 |
</li> |
| 1340 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.6"> |
| 1341 |
<p id="section-toc.1-1.3.2.6.1"><a href="#section-3.6" class="xref">3.6</a>. <a href="#name-security-processing-conside" class="xref">Security Processing Considerations</a></p> |
| 1342 |
</li> |
| 1343 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.7"> |
| 1344 |
<p id="section-toc.1-1.3.2.7.1"><a href="#section-3.7" class="xref">3.7</a>. <a href="#name-canonicalization-algorithms" class="xref">Canonicalization Algorithms</a></p> |
| 1345 |
</li> |
| 1346 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.8"> |
| 1347 |
<p id="section-toc.1-1.3.2.8.1"><a href="#section-3.8" class="xref">3.8</a>. <a href="#name-processing" class="xref">Processing</a></p> |
| 1348 |
<ul class="compact toc ulBare ulEmpty"> |
| 1349 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.8.2.1"> |
| 1350 |
<p id="section-toc.1-1.3.2.8.2.1.1"><a href="#section-3.8.1" class="xref">3.8.1</a>. <a href="#name-keyed-hash-generation" class="xref">Keyed Hash Generation</a></p> |
| 1351 |
</li> |
| 1352 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.8.2.2"> |
| 1353 |
<p id="section-toc.1-1.3.2.8.2.2.1"><a href="#section-3.8.2" class="xref">3.8.2</a>. <a href="#name-keyed-hash-verification" class="xref">Keyed Hash Verification</a></p> |
| 1354 |
</li> |
| 1355 |
</ul> |
| 1356 |
</li> |
| 1357 |
</ul> |
| 1358 |
</li> |
| 1359 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> |
| 1360 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-security-context-bcb-aes-gc" class="xref">Security Context BCB-AES-GCM</a></p> |
| 1361 |
<ul class="compact toc ulBare ulEmpty"> |
| 1362 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1"> |
| 1363 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-overview-2" class="xref">Overview</a></p> |
| 1364 |
</li> |
| 1365 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2"> |
| 1366 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-scope-2" class="xref">Scope</a></p> |
| 1367 |
</li> |
| 1368 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3"> |
| 1369 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-parameters-2" class="xref">Parameters</a></p> |
| 1370 |
<ul class="compact toc ulBare ulEmpty"> |
| 1371 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.1"> |
| 1372 |
<p id="section-toc.1-1.4.2.3.2.1.1"><a href="#section-4.3.1" class="xref">4.3.1</a>. <a href="#name-initialization-vector-iv" class="xref">Initialization Vector (IV)</a></p> |
| 1373 |
</li> |
| 1374 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.2"> |
| 1375 |
<p id="section-toc.1-1.4.2.3.2.2.1"><a href="#section-4.3.2" class="xref">4.3.2</a>. <a href="#name-aes-variant" class="xref">AES Variant</a></p> |
| 1376 |
</li> |
| 1377 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.3"> |
| 1378 |
<p id="section-toc.1-1.4.2.3.2.3.1"><a href="#section-4.3.3" class="xref">4.3.3</a>. <a href="#name-wrapped-key-2" class="xref">Wrapped Key</a></p> |
| 1379 |
</li> |
| 1380 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.4"> |
| 1381 |
<p id="section-toc.1-1.4.2.3.2.4.1"><a href="#section-4.3.4" class="xref">4.3.4</a>. <a href="#name-aad-scope-flags" class="xref">AAD Scope Flags</a></p> |
| 1382 |
</li> |
| 1383 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.5"> |
| 1384 |
<p id="section-toc.1-1.4.2.3.2.5.1"><a href="#section-4.3.5" class="xref">4.3.5</a>. <a href="#name-enumerations-2" class="xref">Enumerations</a></p> |
| 1385 |
</li> |
| 1386 |
</ul> |
| 1387 |
</li> |
| 1388 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4"> |
| 1389 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>. <a href="#name-results-2" class="xref">Results</a></p> |
| 1390 |
<ul class="compact toc ulBare ulEmpty"> |
| 1391 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4.2.1"> |
| 1392 |
<p id="section-toc.1-1.4.2.4.2.1.1"><a href="#section-4.4.1" class="xref">4.4.1</a>. <a href="#name-authentication-tag" class="xref">Authentication Tag</a></p> |
| 1393 |
</li> |
| 1394 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4.2.2"> |
| 1395 |
<p id="section-toc.1-1.4.2.4.2.2.1"><a href="#section-4.4.2" class="xref">4.4.2</a>. <a href="#name-enumerations-3" class="xref">Enumerations</a></p> |
| 1396 |
</li> |
| 1397 |
</ul> |
| 1398 |
</li> |
| 1399 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.5"> |
| 1400 |
<p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>. <a href="#name-key-considerations-2" class="xref">Key Considerations</a></p> |
| 1401 |
</li> |
| 1402 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.6"> |
| 1403 |
<p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>. <a href="#name-gcm-considerations" class="xref">GCM Considerations</a></p> |
| 1404 |
</li> |
| 1405 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.7"> |
| 1406 |
<p id="section-toc.1-1.4.2.7.1"><a href="#section-4.7" class="xref">4.7</a>. <a href="#name-canonicalization-algorithms-2" class="xref">Canonicalization Algorithms</a></p> |
| 1407 |
<ul class="compact toc ulBare ulEmpty"> |
| 1408 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.7.2.1"> |
| 1409 |
<p id="section-toc.1-1.4.2.7.2.1.1"><a href="#section-4.7.1" class="xref">4.7.1</a>. <a href="#name-calculations-related-to-cip" class="xref">Calculations Related to Ciphertext</a></p> |
| 1410 |
</li> |
| 1411 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.7.2.2"> |
| 1412 |
<p id="section-toc.1-1.4.2.7.2.2.1"><a href="#section-4.7.2" class="xref">4.7.2</a>. <a href="#name-additional-authenticated-da" class="xref">Additional Authenticated Data</a></p> |
| 1413 |
</li> |
| 1414 |
</ul> |
| 1415 |
</li> |
| 1416 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.8"> |
| 1417 |
<p id="section-toc.1-1.4.2.8.1"><a href="#section-4.8" class="xref">4.8</a>. <a href="#name-processing-2" class="xref">Processing</a></p> |
| 1418 |
<ul class="compact toc ulBare ulEmpty"> |
| 1419 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.8.2.1"> |
| 1420 |
<p id="section-toc.1-1.4.2.8.2.1.1"><a href="#section-4.8.1" class="xref">4.8.1</a>. <a href="#name-encryption" class="xref">Encryption</a></p> |
| 1421 |
</li> |
| 1422 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.8.2.2"> |
| 1423 |
<p id="section-toc.1-1.4.2.8.2.2.1"><a href="#section-4.8.2" class="xref">4.8.2</a>. <a href="#name-decryption" class="xref">Decryption</a></p> |
| 1424 |
</li> |
| 1425 |
</ul> |
| 1426 |
</li> |
| 1427 |
</ul> |
| 1428 |
</li> |
| 1429 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> |
| 1430 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p> |
| 1431 |
<ul class="compact toc ulBare ulEmpty"> |
| 1432 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1"> |
| 1433 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>. <a href="#name-security-context-identifier" class="xref">Security Context Identifiers</a></p> |
| 1434 |
</li> |
| 1435 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2"> |
| 1436 |
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>. <a href="#name-integrity-scope-flags-2" class="xref">Integrity Scope Flags</a></p> |
| 1437 |
</li> |
| 1438 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.3"> |
| 1439 |
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>. <a href="#name-aad-scope-flags-2" class="xref">AAD Scope Flags</a></p> |
| 1440 |
</li> |
| 1441 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.4"> |
| 1442 |
<p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>. <a href="#name-guidance-for-designated-exp" class="xref">Guidance for Designated Experts</a></p> |
| 1443 |
</li> |
| 1444 |
</ul> |
| 1445 |
</li> |
| 1446 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> |
| 1447 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p> |
| 1448 |
<ul class="compact toc ulBare ulEmpty"> |
| 1449 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1"> |
| 1450 |
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>. <a href="#name-key-management" class="xref">Key Management</a></p> |
| 1451 |
</li> |
| 1452 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2"> |
| 1453 |
<p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>. <a href="#name-key-handling" class="xref">Key Handling</a></p> |
| 1454 |
</li> |
| 1455 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3"> |
| 1456 |
<p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>. <a href="#name-aes-gcm" class="xref">AES GCM</a></p> |
| 1457 |
</li> |
| 1458 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4"> |
| 1459 |
<p id="section-toc.1-1.6.2.4.1"><a href="#section-6.4" class="xref">6.4</a>. <a href="#name-aes-key-wrap" class="xref">AES Key Wrap</a></p> |
| 1460 |
</li> |
| 1461 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5"> |
| 1462 |
<p id="section-toc.1-1.6.2.5.1"><a href="#section-6.5" class="xref">6.5</a>. <a href="#name-bundle-fragmentation" class="xref">Bundle Fragmentation</a></p> |
| 1463 |
</li> |
| 1464 |
</ul> |
| 1465 |
</li> |
| 1466 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> |
| 1467 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-normative-references" class="xref">Normative References</a></p> |
| 1468 |
</li> |
| 1469 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> |
| 1470 |
<p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref">Appendix A</a>. <a href="#name-examples" class="xref">Examples</a></p> |
| 1471 |
<ul class="compact toc ulBare ulEmpty"> |
| 1472 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1"> |
| 1473 |
<p id="section-toc.1-1.8.2.1.1"><a href="#appendix-A.1" class="xref">A.1</a>. <a href="#name-example-1-simple-integrity" class="xref">Example 1 - Simple Integrity</a></p> |
| 1474 |
<ul class="compact toc ulBare ulEmpty"> |
| 1475 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.1"> |
| 1476 |
<p id="section-toc.1-1.8.2.1.2.1.1"><a href="#appendix-A.1.1" class="xref">A.1.1</a>. <a href="#name-original-bundle" class="xref">Original Bundle</a></p> |
| 1477 |
</li> |
| 1478 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.2"> |
| 1479 |
<p id="section-toc.1-1.8.2.1.2.2.1"><a href="#appendix-A.1.2" class="xref">A.1.2</a>. <a href="#name-security-operation-overview" class="xref">Security Operation Overview</a></p> |
| 1480 |
</li> |
| 1481 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.3"> |
| 1482 |
<p id="section-toc.1-1.8.2.1.2.3.1"><a href="#appendix-A.1.3" class="xref">A.1.3</a>. <a href="#name-block-integrity-block" class="xref">Block Integrity Block</a></p> |
| 1483 |
</li> |
| 1484 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.4"> |
| 1485 |
<p id="section-toc.1-1.8.2.1.2.4.1"><a href="#appendix-A.1.4" class="xref">A.1.4</a>. <a href="#name-final-bundle" class="xref">Final Bundle</a></p> |
| 1486 |
</li> |
| 1487 |
</ul> |
| 1488 |
</li> |
| 1489 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2"> |
| 1490 |
<p id="section-toc.1-1.8.2.2.1"><a href="#appendix-A.2" class="xref">A.2</a>. <a href="#name-example-2-simple-confidenti" class="xref">Example 2 - Simple Confidentiality with Key Wrap</a></p> |
| 1491 |
<ul class="compact toc ulBare ulEmpty"> |
| 1492 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2.2.1"> |
| 1493 |
<p id="section-toc.1-1.8.2.2.2.1.1"><a href="#appendix-A.2.1" class="xref">A.2.1</a>. <a href="#name-original-bundle-2" class="xref">Original Bundle</a></p> |
| 1494 |
</li> |
| 1495 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2.2.2"> |
| 1496 |
<p id="section-toc.1-1.8.2.2.2.2.1"><a href="#appendix-A.2.2" class="xref">A.2.2</a>. <a href="#name-security-operation-overview-2" class="xref">Security Operation Overview</a></p> |
| 1497 |
</li> |
| 1498 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2.2.3"> |
| 1499 |
<p id="section-toc.1-1.8.2.2.2.3.1"><a href="#appendix-A.2.3" class="xref">A.2.3</a>. <a href="#name-block-confidentiality-block" class="xref">Block Confidentiality Block</a></p> |
| 1500 |
</li> |
| 1501 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2.2.4"> |
| 1502 |
<p id="section-toc.1-1.8.2.2.2.4.1"><a href="#appendix-A.2.4" class="xref">A.2.4</a>. <a href="#name-final-bundle-2" class="xref">Final Bundle</a></p> |
| 1503 |
</li> |
| 1504 |
</ul> |
| 1505 |
</li> |
| 1506 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3"> |
| 1507 |
<p id="section-toc.1-1.8.2.3.1"><a href="#appendix-A.3" class="xref">A.3</a>. <a href="#name-example-3-security-blocks-f" class="xref">Example 3 - Security Blocks from Multiple Sources</a></p> |
| 1508 |
<ul class="compact toc ulBare ulEmpty"> |
| 1509 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3.2.1"> |
| 1510 |
<p id="section-toc.1-1.8.2.3.2.1.1"><a href="#appendix-A.3.1" class="xref">A.3.1</a>. <a href="#name-original-bundle-3" class="xref">Original Bundle</a></p> |
| 1511 |
</li> |
| 1512 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3.2.2"> |
| 1513 |
<p id="section-toc.1-1.8.2.3.2.2.1"><a href="#appendix-A.3.2" class="xref">A.3.2</a>. <a href="#name-security-operation-overview-3" class="xref">Security Operation Overview</a></p> |
| 1514 |
</li> |
| 1515 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3.2.3"> |
| 1516 |
<p id="section-toc.1-1.8.2.3.2.3.1"><a href="#appendix-A.3.3" class="xref">A.3.3</a>. <a href="#name-block-integrity-block-2" class="xref">Block Integrity Block</a></p> |
| 1517 |
</li> |
| 1518 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3.2.4"> |
| 1519 |
<p id="section-toc.1-1.8.2.3.2.4.1"><a href="#appendix-A.3.4" class="xref">A.3.4</a>. <a href="#name-block-confidentiality-block-2" class="xref">Block Confidentiality Block</a></p> |
| 1520 |
</li> |
| 1521 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3.2.5"> |
| 1522 |
<p id="section-toc.1-1.8.2.3.2.5.1"><a href="#appendix-A.3.5" class="xref">A.3.5</a>. <a href="#name-final-bundle-3" class="xref">Final Bundle</a></p> |
| 1523 |
</li> |
| 1524 |
</ul> |
| 1525 |
</li> |
| 1526 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4"> |
| 1527 |
<p id="section-toc.1-1.8.2.4.1"><a href="#appendix-A.4" class="xref">A.4</a>. <a href="#name-example-4-security-blocks-w" class="xref">Example 4 - Security Blocks with Full Scope</a></p> |
| 1528 |
<ul class="compact toc ulBare ulEmpty"> |
| 1529 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4.2.1"> |
| 1530 |
<p id="section-toc.1-1.8.2.4.2.1.1"><a href="#appendix-A.4.1" class="xref">A.4.1</a>. <a href="#name-original-bundle-4" class="xref">Original Bundle</a></p> |
| 1531 |
</li> |
| 1532 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4.2.2"> |
| 1533 |
<p id="section-toc.1-1.8.2.4.2.2.1"><a href="#appendix-A.4.2" class="xref">A.4.2</a>. <a href="#name-security-operation-overview-4" class="xref">Security Operation Overview</a></p> |
| 1534 |
</li> |
| 1535 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4.2.3"> |
| 1536 |
<p id="section-toc.1-1.8.2.4.2.3.1"><a href="#appendix-A.4.3" class="xref">A.4.3</a>. <a href="#name-block-integrity-block-3" class="xref">Block Integrity Block</a></p> |
| 1537 |
</li> |
| 1538 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4.2.4"> |
| 1539 |
<p id="section-toc.1-1.8.2.4.2.4.1"><a href="#appendix-A.4.4" class="xref">A.4.4</a>. <a href="#name-block-confidentiality-block-3" class="xref">Block Confidentiality Block</a></p> |
| 1540 |
</li> |
| 1541 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4.2.5"> |
| 1542 |
<p id="section-toc.1-1.8.2.4.2.5.1"><a href="#appendix-A.4.5" class="xref">A.4.5</a>. <a href="#name-final-bundle-4" class="xref">Final Bundle</a></p> |
| 1543 |
</li> |
| 1544 |
</ul> |
| 1545 |
</li> |
| 1546 |
</ul> |
| 1547 |
</li> |
| 1548 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> |
| 1549 |
<p id="section-toc.1-1.9.1"><a href="#appendix-B" class="xref">Appendix B</a>. <a href="#name-cddl-expression" class="xref">CDDL Expression</a></p> |
| 1550 |
</li> |
| 1551 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10"> |
| 1552 |
<p id="section-toc.1-1.10.1"><a href="#appendix-C" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p> |
| 1553 |
</li> |
| 1554 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11"> |
| 1555 |
<p id="section-toc.1-1.11.1"><a href="#appendix-D" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p> |
| 1556 |
</li> |
| 1557 |
</ul> |
| 1558 |
</nav> |
| 1559 |
</section> |
| 1560 |
</div> |
| 1561 |
<div id="intro"> |
| 1562 |
<section id="section-1"> |
| 1563 |
<h2 id="name-introduction"> |
| 1564 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1565 |
</h2> |
| 1566 |
<p id="section-1-1"> |
| 1567 |
The Bundle Protocol Security (BPSec) specification |
| 1568 |
<span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span> provides inter-bundle |
| 1569 |
integrity and confidentiality operations for networks deploying the |
| 1570 |
Bundle Protocol (BP) <span>[<a href="#RFC9171" class="xref">RFC9171</a>]</span>. BPSec defines |
| 1571 |
BP extension blocks to carry security information produced under the |
| 1572 |
auspices of some security context.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1573 |
<p id="section-1-2"> |
| 1574 |
This document defines two security contexts (one for an integrity |
| 1575 |
service and one for a confidentiality service) for populating |
| 1576 |
BPSec Block Integrity Blocks (BIBs) and Block Confidentiality Blocks |
| 1577 |
(BCBs). This document assumes familiarity with the concepts and |
| 1578 |
terminology associated with BP and BPSec, as these security |
| 1579 |
contexts are used with BPSec security blocks and other BP blocks |
| 1580 |
carried within BP bundles.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1581 |
<p id="section-1-3"> |
| 1582 |
These contexts generate information that <span class="bcp14">MUST</span> be encoded using |
| 1583 |
the Concise Binary Object Representation (CBOR) specification documented in <span>[<a href="#RFC8949" class="xref">RFC8949</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1584 |
</section> |
| 1585 |
</div> |
| 1586 |
<div id="term"> |
| 1587 |
<section id="section-2"> |
| 1588 |
<h2 id="name-requirements-language"> |
| 1589 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a> |
| 1590 |
</h2> |
| 1591 |
<p id="section-2-1"> |
| 1592 |
The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", |
| 1593 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as |
| 1594 |
described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> |
| 1595 |
when, and only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1596 |
</section> |
| 1597 |
</div> |
| 1598 |
<div id="first-context"> |
| 1599 |
<section id="section-3"> |
| 1600 |
<h2 id="name-integrity-security-context-"> |
| 1601 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-integrity-security-context-" class="section-name selfRef">Integrity Security Context BIB-HMAC-SHA2</a> |
| 1602 |
</h2> |
| 1603 |
<section id="section-3.1"> |
| 1604 |
<h3 id="name-overview"> |
| 1605 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-overview" class="section-name selfRef">Overview</a> |
| 1606 |
</h3> |
| 1607 |
<p id="section-3.1-1"> |
| 1608 |
The BIB-HMAC-SHA2 security context provides a keyed-hash |
| 1609 |
Message Authentication Code (MAC) over a |
| 1610 |
set of plaintext information. This context uses the Secure |
| 1611 |
Hash Algorithm 2 (SHA-2) discussed in <span>[<a href="#SHS" class="xref">SHS</a>]</span> combined |
| 1612 |
with the Hashed Message Authentication Code (HMAC) keyed hash discussed in <span>[<a href="#RFC2104" class="xref">RFC2104</a>]</span>. The combination |
| 1613 |
of HMAC and SHA-2 as the integrity mechanism for this security |
| 1614 |
context was selected for two reasons:<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1615 |
<ol start="1" type="1" class="normal type-1" id="section-3.1-2"> |
| 1616 |
<li id="section-3.1-2.1"> The use of symmetric keys allows this security context to |
| 1617 |
be used in places where an asymmetric-key infrastructure (such as a |
| 1618 |
public key infrastructure) might be impractical.<a href="#section-3.1-2.1" class="pilcrow">¶</a> |
| 1619 |
</li> |
| 1620 |
<li id="section-3.1-2.2"> |
| 1621 |
The combination HMAC-SHA2 represents a well-supported and well-understood |
| 1622 |
integrity mechanism with multiple implementations available.<a href="#section-3.1-2.2" class="pilcrow">¶</a> |
| 1623 |
</li> |
| 1624 |
</ol> |
| 1625 |
<p id="section-3.1-3"> |
| 1626 |
BIB-HMAC-SHA2 supports three variants of HMAC-SHA, based on |
| 1627 |
the supported length of the SHA-2 hash value. These variants |
| 1628 |
correspond to HMAC 256/256, HMAC 384/384, and HMAC 512/512 as |
| 1629 |
defined in Table 7 ("HMAC Algorithm Values") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span>. |
| 1630 |
The selection of which variant is used by this context is |
| 1631 |
provided as a security context parameter.<a href="#section-3.1-3" class="pilcrow">¶</a></p> |
| 1632 |
<p id="section-3.1-4"> |
| 1633 |
The output of the HMAC <span class="bcp14">MUST</span> be equal to the size of the SHA2 |
| 1634 |
hashing function: 256 bits for SHA-256, 384 bits for SHA-384, and |
| 1635 |
512 bits for SHA-512.<a href="#section-3.1-4" class="pilcrow">¶</a></p> |
| 1636 |
<p id="section-3.1-5"> |
| 1637 |
The BIB-HMAC-SHA2 security context <span class="bcp14">MUST</span> have the security context |
| 1638 |
identifier specified in <a href="#sc_ids" class="xref">Section 5.1</a>.<a href="#section-3.1-5" class="pilcrow">¶</a></p> |
| 1639 |
</section> |
| 1640 |
<section id="section-3.2"> |
| 1641 |
<h3 id="name-scope"> |
| 1642 |
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-scope" class="section-name selfRef">Scope</a> |
| 1643 |
</h3> |
| 1644 |
<p id="section-3.2-1"> |
| 1645 |
The scope of BIB-HMAC-SHA2 is the set of information used |
| 1646 |
to produce the plaintext over which a keyed hash is calculated. This |
| 1647 |
plaintext is termed the "Integrity-Protected Plaintext (IPPT)". The |
| 1648 |
content of the IPPT is constructed as the concatenation of information |
| 1649 |
whose integrity is being preserved from the BIB-HMAC-SHA2 security |
| 1650 |
source to its security acceptor. There are five types of information |
| 1651 |
that can be used in the generation of the IPPT, based on |
| 1652 |
how broadly the concept of integrity is being applied. These |
| 1653 |
five types of information, whether they are required, and why |
| 1654 |
they are important for integrity are discussed as follows.<a href="#section-3.2-1" class="pilcrow">¶</a></p> |
| 1655 |
<span class="break"></span><dl class="dlNewline" id="section-3.2-2"> |
| 1656 |
<dt id="section-3.2-2.1">Security target contents</dt> |
| 1657 |
<dd style="margin-left: 1.5em" id="section-3.2-2.2"> |
| 1658 |
The contents of the block-type-specific data field of the security |
| 1659 |
target <span class="bcp14">MUST</span> be included in the IPPT. Including this information protects |
| 1660 |
the security target data and is considered the minimal, required |
| 1661 |
set of information for an integrity service on the security |
| 1662 |
target.<a href="#section-3.2-2.2" class="pilcrow">¶</a> |
| 1663 |
</dd> |
| 1664 |
<dd class="break"></dd> |
| 1665 |
<dt id="section-3.2-2.3">IPPT scope</dt> |
| 1666 |
<dd style="margin-left: 1.5em" id="section-3.2-2.4"> |
| 1667 |
The determination of which optional types of information were |
| 1668 |
used when constructing the IPPT <span class="bcp14">MUST</span> always be included |
| 1669 |
in the IPPT. Including this information ensures that the scope |
| 1670 |
of the IPPT construction at a security source matches the scope of |
| 1671 |
the IPPT construction at security verifiers and security acceptors.<a href="#section-3.2-2.4" class="pilcrow">¶</a> |
| 1672 |
</dd> |
| 1673 |
<dd class="break"></dd> |
| 1674 |
<dt id="section-3.2-2.5">Primary block</dt> |
| 1675 |
<dd style="margin-left: 1.5em" id="section-3.2-2.6"> |
| 1676 |
<p id="section-3.2-2.6.1"> |
| 1677 |
The primary block identifies a bundle, and once |
| 1678 |
created, the contents of this block are immutable. Changes to |
| 1679 |
the primary block associated with the security target indicate |
| 1680 |
that the security target (and BIB) might no longer be in the |
| 1681 |
correct bundle.<a href="#section-3.2-2.6.1" class="pilcrow">¶</a></p> |
| 1682 |
<p id="section-3.2-2.6.2"> |
| 1683 |
For example, if a security target and associated BIB are copied |
| 1684 |
from one bundle to another bundle, the BIB might still contain a |
| 1685 |
verifiable signature for the security target unless information |
| 1686 |
associated with the bundle primary block is included in the |
| 1687 |
keyed hash carried by the BIB.<a href="#section-3.2-2.6.2" class="pilcrow">¶</a></p> |
| 1688 |
<p id="section-3.2-2.6.3"> |
| 1689 |
Including this information in the IPPT protects the integrity |
| 1690 |
of the association of the security target with a specific bundle.<a href="#section-3.2-2.6.3" class="pilcrow">¶</a></p> |
| 1691 |
</dd> |
| 1692 |
<dd class="break"></dd> |
| 1693 |
<dt id="section-3.2-2.7">Other fields of the security target</dt> |
| 1694 |
<dd style="margin-left: 1.5em" id="section-3.2-2.8"> |
| 1695 |
<p id="section-3.2-2.8.1"> |
| 1696 |
The other fields of the security target include block |
| 1697 |
identification and processing information. Changing this |
| 1698 |
information changes how the security target is treated by nodes |
| 1699 |
in the network even when the |
| 1700 |
"user data" of the security target are otherwise unchanged.<a href="#section-3.2-2.8.1" class="pilcrow">¶</a></p> |
| 1701 |
<p id="section-3.2-2.8.2"> |
| 1702 |
For example, if the block processing control flags of a security |
| 1703 |
target are different at a security verifier than they were |
| 1704 |
originally set at the security source, then the policy for |
| 1705 |
handling the security target has been modified.<a href="#section-3.2-2.8.2" class="pilcrow">¶</a></p> |
| 1706 |
<p id="section-3.2-2.8.3"> |
| 1707 |
Including this information in the IPPT protects the integrity |
| 1708 |
of the policy and identification of the security target data.<a href="#section-3.2-2.8.3" class="pilcrow">¶</a></p> |
| 1709 |
</dd> |
| 1710 |
<dd class="break"></dd> |
| 1711 |
<dt id="section-3.2-2.9">Other fields of the BIB</dt> |
| 1712 |
<dd style="margin-left: 1.5em" id="section-3.2-2.10"> |
| 1713 |
<p id="section-3.2-2.10.1"> |
| 1714 |
The other fields of the BIB include block identification |
| 1715 |
and processing information. |
| 1716 |
Changing this information changes how the BIB |
| 1717 |
is treated by nodes in the network, even when other aspects of the |
| 1718 |
BIB are unchanged.<a href="#section-3.2-2.10.1" class="pilcrow">¶</a></p> |
| 1719 |
<p id="section-3.2-2.10.2"> |
| 1720 |
For example, if the block processing control flags of the BIB are |
| 1721 |
different at a security verifier than they were |
| 1722 |
originally set at the security source, then the policy for |
| 1723 |
handling the BIB has been modified.<a href="#section-3.2-2.10.2" class="pilcrow">¶</a></p> |
| 1724 |
<p id="section-3.2-2.10.3"> |
| 1725 |
Including this information in the IPPT protects the integrity |
| 1726 |
of the policy and identification of the security service in the bundle.<a href="#section-3.2-2.10.3" class="pilcrow">¶</a></p> |
| 1727 |
<aside id="section-3.2-2.10.4"> |
| 1728 |
<p id="section-3.2-2.10.4.1"> |
| 1729 |
NOTE: The security context identifier and security context |
| 1730 |
parameters of the security block are not included in the IPPT |
| 1731 |
because these parameters, by definition, are required to verify or |
| 1732 |
accept the security service. Successful verification at security |
| 1733 |
verifiers and security acceptors implies that these parameters |
| 1734 |
were unchanged since being specified at the security source. |
| 1735 |
This is the case because keys cannot be reused across security |
| 1736 |
contexts and because the integrity scope flags used to define |
| 1737 |
the IPPT are included in the IPPT itself.<a href="#section-3.2-2.10.4.1" class="pilcrow">¶</a></p> |
| 1738 |
</aside> |
| 1739 |
</dd> |
| 1740 |
<dd class="break"></dd> |
| 1741 |
</dl> |
| 1742 |
<p id="section-3.2-3"> |
| 1743 |
The scope of the BIB-HMAC-SHA2 security context is configured using |
| 1744 |
an optional security context parameter.<a href="#section-3.2-3" class="pilcrow">¶</a></p> |
| 1745 |
</section> |
| 1746 |
<section id="section-3.3"> |
| 1747 |
<h3 id="name-parameters"> |
| 1748 |
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-parameters" class="section-name selfRef">Parameters</a> |
| 1749 |
</h3> |
| 1750 |
<p id="section-3.3-1"> |
| 1751 |
BIB-HMAC-SHA2 can be parameterized to select SHA-2 variants, |
| 1752 |
communicate key information, and define the scope of the IPPT.<a href="#section-3.3-1" class="pilcrow">¶</a></p> |
| 1753 |
<section id="section-3.3.1"> |
| 1754 |
<h4 id="name-sha-variant"> |
| 1755 |
<a href="#section-3.3.1" class="section-number selfRef">3.3.1. </a><a href="#name-sha-variant" class="section-name selfRef">SHA Variant</a> |
| 1756 |
</h4> |
| 1757 |
<p id="section-3.3.1-1"> |
| 1758 |
This optional parameter identifies which variant of the SHA-2 |
| 1759 |
algorithm is to be used in the generation of the authentication code.<a href="#section-3.3.1-1" class="pilcrow">¶</a></p> |
| 1760 |
<p id="section-3.3.1-2"> |
| 1761 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR unsigned integer.<a href="#section-3.3.1-2" class="pilcrow">¶</a></p> |
| 1762 |
<p id="section-3.3.1-3"> |
| 1763 |
Valid values for this parameter are as follows.<a href="#section-3.3.1-3" class="pilcrow">¶</a></p> |
| 1764 |
<span id="name-sha-variant-parameter-value"></span><div id="sha_var"> |
| 1765 |
<table class="center" id="table-1"> |
| 1766 |
<caption> |
| 1767 |
<a href="#table-1" class="selfRef">Table 1</a>: |
| 1768 |
<a href="#name-sha-variant-parameter-value" class="selfRef">SHA Variant Parameter Values</a> |
| 1769 |
</caption> |
| 1770 |
<thead> |
| 1771 |
<tr> |
| 1772 |
<th class="text-center" rowspan="1" colspan="1">Value</th> |
| 1773 |
<th class="text-center" rowspan="1" colspan="1">Description</th> |
| 1774 |
</tr> |
| 1775 |
</thead> |
| 1776 |
<tbody> |
| 1777 |
<tr> |
| 1778 |
<td class="text-center" rowspan="1" colspan="1">5</td> |
| 1779 |
<td class="text-left" rowspan="1" colspan="1">HMAC 256/256 as defined in Table 7 ("HMAC Algorithm Values") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span> |
| 1780 |
</td> |
| 1781 |
</tr> |
| 1782 |
<tr> |
| 1783 |
<td class="text-center" rowspan="1" colspan="1">6</td> |
| 1784 |
<td class="text-left" rowspan="1" colspan="1">HMAC 384/384 as defined in Table 7 ("HMAC Algorithm Values") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span> |
| 1785 |
</td> |
| 1786 |
</tr> |
| 1787 |
<tr> |
| 1788 |
<td class="text-center" rowspan="1" colspan="1">7</td> |
| 1789 |
<td class="text-left" rowspan="1" colspan="1">HMAC 512/512 as defined in Table 7 ("HMAC Algorithm Values") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span> |
| 1790 |
</td> |
| 1791 |
</tr> |
| 1792 |
</tbody> |
| 1793 |
</table> |
| 1794 |
</div> |
| 1795 |
<p id="section-3.3.1-5"> |
| 1796 |
When not provided, implementations <span class="bcp14">SHOULD</span> assume a value of 6 |
| 1797 |
(indicating use of HMAC 384/384), unless an alternate default is |
| 1798 |
established by local security policy at the security source, verifiers, |
| 1799 |
or acceptor of this integrity service.<a href="#section-3.3.1-5" class="pilcrow">¶</a></p> |
| 1800 |
</section> |
| 1801 |
<section id="section-3.3.2"> |
| 1802 |
<h4 id="name-wrapped-key"> |
| 1803 |
<a href="#section-3.3.2" class="section-number selfRef">3.3.2. </a><a href="#name-wrapped-key" class="section-name selfRef">Wrapped Key</a> |
| 1804 |
</h4> |
| 1805 |
<p id="section-3.3.2-1"> |
| 1806 |
This optional parameter contains the output of the AES key wrap function as defined in <span>[<a href="#RFC3394" class="xref">RFC3394</a>]</span>. Specifically, this parameter holds the ciphertext produced when running this key wrap algorithm with the |
| 1807 |
input string being the symmetric HMAC |
| 1808 |
key used to generate the security results present in the security block. |
| 1809 |
The value of this parameter is used as input to the AES key wrap authenticated |
| 1810 |
decryption function at security verifiers and security acceptors to determine |
| 1811 |
the symmetric HMAC key needed for the proper validation of the security results |
| 1812 |
in the security block.<a href="#section-3.3.2-1" class="pilcrow">¶</a></p> |
| 1813 |
<p id="section-3.3.2-2"> |
| 1814 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR byte string.<a href="#section-3.3.2-2" class="pilcrow">¶</a></p> |
| 1815 |
<p id="section-3.3.2-3"> |
| 1816 |
If this parameter is not present, then security verifiers |
| 1817 |
and acceptors <span class="bcp14">MUST</span> determine the proper key as a function of their local BPSec policy |
| 1818 |
and configuration.<a href="#section-3.3.2-3" class="pilcrow">¶</a></p> |
| 1819 |
</section> |
| 1820 |
<section id="section-3.3.3"> |
| 1821 |
<h4 id="name-integrity-scope-flags"> |
| 1822 |
<a href="#section-3.3.3" class="section-number selfRef">3.3.3. </a><a href="#name-integrity-scope-flags" class="section-name selfRef">Integrity Scope Flags</a> |
| 1823 |
</h4> |
| 1824 |
<p id="section-3.3.3-1"> |
| 1825 |
This optional parameter contains a series of flags that describe |
| 1826 |
what information is to be included with the block-type-specific data |
| 1827 |
when constructing the IPPT value.<a href="#section-3.3.3-1" class="pilcrow">¶</a></p> |
| 1828 |
<p id="section-3.3.3-2"> |
| 1829 |
This value <span class="bcp14">MUST</span> be represented as a CBOR unsigned |
| 1830 |
integer, the value of which <span class="bcp14">MUST</span> be processed as a 16-bit field. |
| 1831 |
The maximum value of this field, as a CBOR unsigned integer, <span class="bcp14">MUST</span> be |
| 1832 |
65535.<a href="#section-3.3.3-2" class="pilcrow">¶</a></p> |
| 1833 |
<p id="section-3.3.3-3">When not provided, implementations <span class="bcp14">SHOULD</span> assume a value of 7 (indicating all assigned fields), unless an alternate default is established by local security policy at the security source, verifier, or acceptor of this integrity service.<a href="#section-3.3.3-3" class="pilcrow">¶</a></p> |
| 1834 |
<p id="section-3.3.3-4"> |
| 1835 |
Implementations <span class="bcp14">MUST</span> set reserved and unassigned bits in this |
| 1836 |
field to 0 when constructing these flags at a security source. |
| 1837 |
Once set, the value of this field <span class="bcp14">MUST NOT</span> be altered until the |
| 1838 |
security service is completed at the security acceptor in the |
| 1839 |
network and removed from the bundle.<a href="#section-3.3.3-4" class="pilcrow">¶</a></p> |
| 1840 |
<p id="section-3.3.3-5"> |
| 1841 |
Bits in this field represent additional information to be included |
| 1842 |
when generating an integrity signature over the security target. |
| 1843 |
These bits are defined as follows.<a href="#section-3.3.3-5" class="pilcrow">¶</a></p> |
| 1844 |
<span class="break"></span><dl class="dlParallel" id="section-3.3.3-6"> |
| 1845 |
<dt id="section-3.3.3-6.1">Bit 0 (the low-order bit, 0x0001):</dt> |
| 1846 |
<dd style="margin-left: 1.5em" id="section-3.3.3-6.2">Include primary block flag<a href="#section-3.3.3-6.2" class="pilcrow">¶</a> |
| 1847 |
</dd> |
| 1848 |
<dd class="break"></dd> |
| 1849 |
<dt id="section-3.3.3-6.3">Bit 1 (0x0002):</dt> |
| 1850 |
<dd style="margin-left: 1.5em" id="section-3.3.3-6.4">Include target header flag<a href="#section-3.3.3-6.4" class="pilcrow">¶</a> |
| 1851 |
</dd> |
| 1852 |
<dd class="break"></dd> |
| 1853 |
<dt id="section-3.3.3-6.5">Bit 2 (0x0004):</dt> |
| 1854 |
<dd style="margin-left: 1.5em" id="section-3.3.3-6.6">Include security header flag<a href="#section-3.3.3-6.6" class="pilcrow">¶</a> |
| 1855 |
</dd> |
| 1856 |
<dd class="break"></dd> |
| 1857 |
<dt id="section-3.3.3-6.7">Bits 3-7:</dt> |
| 1858 |
<dd style="margin-left: 1.5em" id="section-3.3.3-6.8">Reserved<a href="#section-3.3.3-6.8" class="pilcrow">¶</a> |
| 1859 |
</dd> |
| 1860 |
<dd class="break"></dd> |
| 1861 |
<dt id="section-3.3.3-6.9">Bits 8-15:</dt> |
| 1862 |
<dd style="margin-left: 1.5em" id="section-3.3.3-6.10">Unassigned<a href="#section-3.3.3-6.10" class="pilcrow">¶</a> |
| 1863 |
</dd> |
| 1864 |
<dd class="break"></dd> |
| 1865 |
</dl> |
| 1866 |
</section> |
| 1867 |
<section id="section-3.3.4"> |
| 1868 |
<h4 id="name-enumerations"> |
| 1869 |
<a href="#section-3.3.4" class="section-number selfRef">3.3.4. </a><a href="#name-enumerations" class="section-name selfRef">Enumerations</a> |
| 1870 |
</h4> |
| 1871 |
<p id="section-3.3.4-1"> |
| 1872 |
The BIB-HMAC-SHA2 security context parameters are listed in |
| 1873 |
<a href="#bib_parm_table" class="xref">Table 2</a>. In this table, the "Parm Id" column |
| 1874 |
refers to the expected parameter identifier described in Section |
| 1875 |
<span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">3.10</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">"Parameter |
| 1876 |
and Result Identification"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#section-3.3.4-1" class="pilcrow">¶</a></p> |
| 1877 |
<p id="section-3.3.4-2"> |
| 1878 |
An empty "Default Value" column indicates that the |
| 1879 |
security context parameter does not have a default value.<a href="#section-3.3.4-2" class="pilcrow">¶</a></p> |
| 1880 |
<span id="name-bib-hmac-sha2-security-cont"></span><div id="bib_parm_table"> |
| 1881 |
<table class="center" id="table-2"> |
| 1882 |
<caption> |
| 1883 |
<a href="#table-2" class="selfRef">Table 2</a>: |
| 1884 |
<a href="#name-bib-hmac-sha2-security-cont" class="selfRef">BIB-HMAC-SHA2 Security Context Parameters</a> |
| 1885 |
</caption> |
| 1886 |
<thead> |
| 1887 |
<tr> |
| 1888 |
<th class="text-center" rowspan="1" colspan="1">Parm Id</th> |
| 1889 |
<th class="text-left" rowspan="1" colspan="1">Parm Name</th> |
| 1890 |
<th class="text-left" rowspan="1" colspan="1">CBOR Encoding Type</th> |
| 1891 |
<th class="text-left" rowspan="1" colspan="1">Default Value</th> |
| 1892 |
</tr> |
| 1893 |
</thead> |
| 1894 |
<tbody> |
| 1895 |
<tr> |
| 1896 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 1897 |
<td class="text-left" rowspan="1" colspan="1">SHA Variant</td> |
| 1898 |
<td class="text-left" rowspan="1" colspan="1">unsigned integer</td> |
| 1899 |
<td class="text-center" rowspan="1" colspan="1">6</td> |
| 1900 |
</tr> |
| 1901 |
<tr> |
| 1902 |
<td class="text-center" rowspan="1" colspan="1">2</td> |
| 1903 |
<td class="text-left" rowspan="1" colspan="1">Wrapped Key</td> |
| 1904 |
<td class="text-left" rowspan="1" colspan="1">byte string</td> |
| 1905 |
<td class="text-center" rowspan="1" colspan="1"></td> |
| 1906 |
</tr> |
| 1907 |
<tr> |
| 1908 |
<td class="text-center" rowspan="1" colspan="1">3</td> |
| 1909 |
<td class="text-left" rowspan="1" colspan="1">Integrity Scope Flags</td> |
| 1910 |
<td class="text-left" rowspan="1" colspan="1">unsigned integer</td> |
| 1911 |
<td class="text-center" rowspan="1" colspan="1">7</td> |
| 1912 |
</tr> |
| 1913 |
</tbody> |
| 1914 |
</table> |
| 1915 |
</div> |
| 1916 |
</section> |
| 1917 |
</section> |
| 1918 |
<div id="bib_results"> |
| 1919 |
<section id="section-3.4"> |
| 1920 |
<h3 id="name-results"> |
| 1921 |
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-results" class="section-name selfRef">Results</a> |
| 1922 |
</h3> |
| 1923 |
<p id="section-3.4-1"> |
| 1924 |
The BIB-HMAC-SHA2 security context results are listed in |
| 1925 |
<a href="#bib_res_table" class="xref">Table 3</a>. In this table, the "Result Id" column |
| 1926 |
refers to the expected result identifier described in Section |
| 1927 |
<span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">3.10</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">"Parameter |
| 1928 |
and Result Identification"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#section-3.4-1" class="pilcrow">¶</a></p> |
| 1929 |
<span id="name-bib-hmac-sha2-security-resu"></span><div id="bib_res_table"> |
| 1930 |
<table class="center" id="table-3"> |
| 1931 |
<caption> |
| 1932 |
<a href="#table-3" class="selfRef">Table 3</a>: |
| 1933 |
<a href="#name-bib-hmac-sha2-security-resu" class="selfRef">BIB-HMAC-SHA2 Security Results</a> |
| 1934 |
</caption> |
| 1935 |
<thead> |
| 1936 |
<tr> |
| 1937 |
<th class="text-center" rowspan="1" colspan="1">Result Id</th> |
| 1938 |
<th class="text-center" rowspan="1" colspan="1">Result Name</th> |
| 1939 |
<th class="text-center" rowspan="1" colspan="1">CBOR Encoding Type</th> |
| 1940 |
<th class="text-center" rowspan="1" colspan="1">Description</th> |
| 1941 |
</tr> |
| 1942 |
</thead> |
| 1943 |
<tbody> |
| 1944 |
<tr> |
| 1945 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 1946 |
<td class="text-center" rowspan="1" colspan="1">Expected HMAC</td> |
| 1947 |
<td class="text-center" rowspan="1" colspan="1">byte string</td> |
| 1948 |
<td class="text-left" rowspan="1" colspan="1">The output of the HMAC calculation at the security source.</td> |
| 1949 |
</tr> |
| 1950 |
</tbody> |
| 1951 |
</table> |
| 1952 |
</div> |
| 1953 |
</section> |
| 1954 |
</div> |
| 1955 |
<div id="bib_key_mgmt"> |
| 1956 |
<section id="section-3.5"> |
| 1957 |
<h3 id="name-key-considerations"> |
| 1958 |
<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-key-considerations" class="section-name selfRef">Key Considerations</a> |
| 1959 |
</h3> |
| 1960 |
<p id="section-3.5-1"> |
| 1961 |
HMAC keys used with this context <span class="bcp14">MUST</span> be symmetric and <span class="bcp14">MUST</span> have |
| 1962 |
a key length equal to the output of the HMAC. For this reason, HMAC |
| 1963 |
key lengths will be integers divisible by 8 bytes, and special padding-aware |
| 1964 |
AES key wrap algorithms are not needed.<a href="#section-3.5-1" class="pilcrow">¶</a></p> |
| 1965 |
<p id="section-3.5-2"> |
| 1966 |
It is assumed that any security verifier or security acceptor |
| 1967 |
performing an integrity verification can determine the proper HMAC |
| 1968 |
key to be used. Potential sources of the HMAC key include (but are |
| 1969 |
not limited to) the following:<a href="#section-3.5-2" class="pilcrow">¶</a></p> |
| 1970 |
<ul class="normal"> |
| 1971 |
<li class="normal" id="section-3.5-3.1"> Pre-placed keys selected based on local policy.<a href="#section-3.5-3.1" class="pilcrow">¶</a> |
| 1972 |
</li> |
| 1973 |
<li class="normal" id="section-3.5-3.2"> Keys extracted from material carried in the BIB.<a href="#section-3.5-3.2" class="pilcrow">¶</a> |
| 1974 |
</li> |
| 1975 |
<li class="normal" id="section-3.5-3.3"> Session keys negotiated via a mechanism external to the BIB.<a href="#section-3.5-3.3" class="pilcrow">¶</a> |
| 1976 |
</li> |
| 1977 |
</ul> |
| 1978 |
<p id="section-3.5-4"> |
| 1979 |
When an AES Key Wrap (AES-KW) <span>[<a href="#RFC3394" class="xref">RFC3394</a>]</span> wrapped key is present in a security block, it is |
| 1980 |
assumed that security verifiers and security acceptors can |
| 1981 |
independently determine the key encryption key (KEK) used in the |
| 1982 |
wrapping of the symmetric HMAC key.<a href="#section-3.5-4" class="pilcrow">¶</a></p> |
| 1983 |
<p id="section-3.5-5"> |
| 1984 |
As discussed in <a href="#SecCons" class="xref">Section 6</a> and emphasized here, it is |
| 1985 |
strongly recommended that keys be protected once generated, both |
| 1986 |
when they are stored and when they are transmitted.<a href="#section-3.5-5" class="pilcrow">¶</a></p> |
| 1987 |
</section> |
| 1988 |
</div> |
| 1989 |
<section id="section-3.6"> |
| 1990 |
<h3 id="name-security-processing-conside"> |
| 1991 |
<a href="#section-3.6" class="section-number selfRef">3.6. </a><a href="#name-security-processing-conside" class="section-name selfRef">Security Processing Considerations</a> |
| 1992 |
</h3> |
| 1993 |
<p id="section-3.6-1"> |
| 1994 |
An HMAC calculated over the same IPPT with the same key will always |
| 1995 |
have the same value. This regularity can lead to practical |
| 1996 |
side-channel attacks whereby an attacker could produce known |
| 1997 |
plaintext, guess at an HMAC tag, and observe the behavior of a |
| 1998 |
verifier. With a modest number of trials, a side-channel attack |
| 1999 |
could produce an HMAC tag for attacker-provided plaintext without |
| 2000 |
the attacker ever knowing the HMAC key.<a href="#section-3.6-1" class="pilcrow">¶</a></p> |
| 2001 |
<p id="section-3.6-2"> |
| 2002 |
A common method of observing the behavior of a verifier is precise |
| 2003 |
analysis of the timing associated with comparisons. Therefore, one |
| 2004 |
way to prevent behavior analysis of this type is to ensure that |
| 2005 |
any comparisons of the supplied and expected authentication tag occur |
| 2006 |
in constant time.<a href="#section-3.6-2" class="pilcrow">¶</a></p> |
| 2007 |
<p id="section-3.6-3"> |
| 2008 |
A constant-time comparison function <span class="bcp14">SHOULD</span> be used for the comparison |
| 2009 |
of authentication tags by any implementation of this security context. |
| 2010 |
In cases where such a function is difficult or impossible to use, |
| 2011 |
the impact of side-channel attacks (in general) and timing attacks (specifically) |
| 2012 |
need to be considered as part of the implementation.<a href="#section-3.6-3" class="pilcrow">¶</a></p> |
| 2013 |
</section> |
| 2014 |
<div id="bib_canon"> |
| 2015 |
<section id="section-3.7"> |
| 2016 |
<h3 id="name-canonicalization-algorithms"> |
| 2017 |
<a href="#section-3.7" class="section-number selfRef">3.7. </a><a href="#name-canonicalization-algorithms" class="section-name selfRef">Canonicalization Algorithms</a> |
| 2018 |
</h3> |
| 2019 |
<p id="section-3.7-1"> |
| 2020 |
This section defines the canonicalization algorithm used to prepare |
| 2021 |
the IPPT input to the BIB-HMAC-SHA2 integrity mechanism. The |
| 2022 |
construction of the IPPT depends on the settings of the |
| 2023 |
integrity scope flags that can be provided as part of customizing |
| 2024 |
the behavior of this security context.<a href="#section-3.7-1" class="pilcrow">¶</a></p> |
| 2025 |
<p id="section-3.7-2"> |
| 2026 |
In all cases, the canonical form of any portion of an extension block |
| 2027 |
<span class="bcp14">MUST</span> be created as described in <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>. |
| 2028 |
The canonicalization algorithms defined in <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span> |
| 2029 |
adhere to the canonical forms for extension blocks defined in |
| 2030 |
<span>[<a href="#RFC9171" class="xref">RFC9171</a>]</span> but resolve ambiguities related to |
| 2031 |
how values are represented in CBOR.<a href="#section-3.7-2" class="pilcrow">¶</a></p> |
| 2032 |
<p id="section-3.7-3"> |
| 2033 |
The IPPT is constructed using the following process. While integrity |
| 2034 |
scope flags might not be included in the BIB representing the |
| 2035 |
security operation, they <span class="bcp14">MUST</span> be included in the IPPT value itself.<a href="#section-3.7-3" class="pilcrow">¶</a></p> |
| 2036 |
<ol start="1" type="1" class="normal type-1" id="section-3.7-4"> |
| 2037 |
<li id="section-3.7-4.1"> |
| 2038 |
The canonical form of the IPPT starts as the CBOR encoding of the |
| 2039 |
integrity scope flags in which all unset flags, reserved bits, |
| 2040 |
and unassigned bits have been set to 0. For example, if the |
| 2041 |
primary block flag, target header flag, and security header flag are |
| 2042 |
each set, then the initial value of the canonical form of the |
| 2043 |
IPPT will be 0x07.<a href="#section-3.7-4.1" class="pilcrow">¶</a> |
| 2044 |
</li> |
| 2045 |
<li id="section-3.7-4.2"> |
| 2046 |
If the primary block flag of the integrity scope flags is set to 1 and the |
| 2047 |
security target is not the bundle's primary block, then a canonical form of |
| 2048 |
the bundle's primary block <span class="bcp14">MUST</span> be calculated and the result |
| 2049 |
appended to the IPPT.<a href="#section-3.7-4.2" class="pilcrow">¶</a> |
| 2050 |
</li> |
| 2051 |
<li id="section-3.7-4.3"> |
| 2052 |
If the target header flag of the integrity scope flags is set to 1 and the |
| 2053 |
security target is not the bundle's primary block, then the canonical form of |
| 2054 |
the block type code, block number, and block processing control flags |
| 2055 |
associated with the security target <span class="bcp14">MUST</span> be calculated and, in |
| 2056 |
that order, appended to the IPPT.<a href="#section-3.7-4.3" class="pilcrow">¶</a> |
| 2057 |
</li> |
| 2058 |
<li id="section-3.7-4.4"> |
| 2059 |
If the security header flag of the integrity scope flags is set |
| 2060 |
to 1, then the canonical form of the block type code, |
| 2061 |
block number, and block processing control flags associated with |
| 2062 |
the BIB <span class="bcp14">MUST</span> be calculated and, in that order, appended to the IPPT.<a href="#section-3.7-4.4" class="pilcrow">¶</a> |
| 2063 |
</li> |
| 2064 |
<li id="section-3.7-4.5"> |
| 2065 |
The canonical form of the security target <span class="bcp14">MUST</span> be calculated |
| 2066 |
and appended to the IPPT. If the security target is the primary block, this is |
| 2067 |
the canonical form of the primary block. Otherwise, this is the canonical form |
| 2068 |
of the block-type-specific data of the security target.<a href="#section-3.7-4.5" class="pilcrow">¶</a> |
| 2069 |
</li> |
| 2070 |
</ol> |
| 2071 |
<aside id="section-3.7-5"> |
| 2072 |
<p id="section-3.7-5.1">NOTE: When the security target is the bundle's primary block, the |
| 2073 |
canonicalization steps associated with the primary block flag and |
| 2074 |
the target header flag are skipped. Skipping primary block flag |
| 2075 |
processing, in this case, avoids adding the bundle's primary block |
| 2076 |
twice in the IPPT calculation. Skipping target header flag |
| 2077 |
processing, in this case, is necessary because the primary block of |
| 2078 |
a bundle does not have the expected elements of a block header such |
| 2079 |
as block number and block processing control flags.<a href="#section-3.7-5.1" class="pilcrow">¶</a></p> |
| 2080 |
</aside> |
| 2081 |
</section> |
| 2082 |
</div> |
| 2083 |
<section id="section-3.8"> |
| 2084 |
<h3 id="name-processing"> |
| 2085 |
<a href="#section-3.8" class="section-number selfRef">3.8. </a><a href="#name-processing" class="section-name selfRef">Processing</a> |
| 2086 |
</h3> |
| 2087 |
<section id="section-3.8.1"> |
| 2088 |
<h4 id="name-keyed-hash-generation"> |
| 2089 |
<a href="#section-3.8.1" class="section-number selfRef">3.8.1. </a><a href="#name-keyed-hash-generation" class="section-name selfRef">Keyed Hash Generation</a> |
| 2090 |
</h4> |
| 2091 |
<p id="section-3.8.1-1"> |
| 2092 |
During keyed hash generation, two inputs are prepared for |
| 2093 |
the appropriate HMAC/SHA2 algorithm: the HMAC key and the IPPT. |
| 2094 |
These data items <span class="bcp14">MUST</span> be generated as follows.<a href="#section-3.8.1-1" class="pilcrow">¶</a></p> |
| 2095 |
<ul class="normal"> |
| 2096 |
<li class="normal" id="section-3.8.1-2.1"> |
| 2097 |
The HMAC key <span class="bcp14">MUST</span> have the appropriate length |
| 2098 |
as required by local security policy. The key can be |
| 2099 |
generated specifically for this integrity service, given as |
| 2100 |
part of local security policy, or obtained through some other |
| 2101 |
key management mechanism as discussed in <a href="#bib_key_mgmt" class="xref">Section 3.5</a>.<a href="#section-3.8.1-2.1" class="pilcrow">¶</a> |
| 2102 |
</li> |
| 2103 |
<li class="normal" id="section-3.8.1-2.2"> |
| 2104 |
Prior to the generation of the IPPT, if a Cyclic Redundancy Check (CRC) value is present |
| 2105 |
for the target block of the BIB, then that CRC value <span class="bcp14">MUST</span> be |
| 2106 |
removed from the target block. This involves both removing the |
| 2107 |
CRC value from the target block and setting the CRC type field |
| 2108 |
of the target block to "no CRC is present."<a href="#section-3.8.1-2.2" class="pilcrow">¶</a> |
| 2109 |
</li> |
| 2110 |
<li class="normal" id="section-3.8.1-2.3"> |
| 2111 |
Once CRC information is removed, the IPPT <span class="bcp14">MUST</span> be generated as |
| 2112 |
discussed in <a href="#bib_canon" class="xref">Section 3.7</a>.<a href="#section-3.8.1-2.3" class="pilcrow">¶</a> |
| 2113 |
</li> |
| 2114 |
</ul> |
| 2115 |
<p id="section-3.8.1-3"> |
| 2116 |
Upon successful hash generation, the following action <span class="bcp14">MUST</span> occur.<a href="#section-3.8.1-3" class="pilcrow">¶</a></p> |
| 2117 |
<ul class="normal"> |
| 2118 |
<li class="normal" id="section-3.8.1-4.1"> |
| 2119 |
The keyed hash produced by the HMAC/SHA2 variant <span class="bcp14">MUST</span> be added |
| 2120 |
as a security result for the BIB representing the security |
| 2121 |
operation on this security target, as discussed |
| 2122 |
in <a href="#bib_results" class="xref">Section 3.4</a>.<a href="#section-3.8.1-4.1" class="pilcrow">¶</a> |
| 2123 |
</li> |
| 2124 |
</ul> |
| 2125 |
<p id="section-3.8.1-5"> |
| 2126 |
Finally, the BIB containing information about this security operation |
| 2127 |
<span class="bcp14">MUST</span> be updated as follows. These operations can occur in any order.<a href="#section-3.8.1-5" class="pilcrow">¶</a></p> |
| 2128 |
<ul class="normal"> |
| 2129 |
<li class="normal" id="section-3.8.1-6.1"> |
| 2130 |
The security context identifier for the BIB <span class="bcp14">MUST</span> be set to the context |
| 2131 |
identifier for BIB-HMAC-SHA2.<a href="#section-3.8.1-6.1" class="pilcrow">¶</a> |
| 2132 |
</li> |
| 2133 |
<li class="normal" id="section-3.8.1-6.2"> |
| 2134 |
Any local flags used to generate the IPPT <span class="bcp14">MUST</span> be placed in |
| 2135 |
the integrity scope flags security context parameter for the BIB unless |
| 2136 |
these flags are expected to be correctly configured at security |
| 2137 |
verifiers and acceptors in the network.<a href="#section-3.8.1-6.2" class="pilcrow">¶</a> |
| 2138 |
</li> |
| 2139 |
<li class="normal" id="section-3.8.1-6.3"> |
| 2140 |
The HMAC key <span class="bcp14">MAY</span> be included as a security context parameter, in which case |
| 2141 |
it <span class="bcp14">MUST</span> be wrapped using the AES key wrap function as defined in <span>[<a href="#RFC3394" class="xref">RFC3394</a>]</span> and |
| 2142 |
the results of the wrapping added as the wrapped key |
| 2143 |
security context parameter for the BIB.<a href="#section-3.8.1-6.3" class="pilcrow">¶</a> |
| 2144 |
</li> |
| 2145 |
<li class="normal" id="section-3.8.1-6.4"> |
| 2146 |
The SHA variant used by this security context <span class="bcp14">SHOULD</span> be added as |
| 2147 |
the SHA variant security context parameter for the BIB if it differs from |
| 2148 |
the default key length. Otherwise, this parameter <span class="bcp14">MAY</span> be |
| 2149 |
omitted if doing so provides a useful reduction in message sizes.<a href="#section-3.8.1-6.4" class="pilcrow">¶</a> |
| 2150 |
</li> |
| 2151 |
</ul> |
| 2152 |
<p id="section-3.8.1-7"> |
| 2153 |
Problems encountered in the keyed hash generation <span class="bcp14">MUST</span> be |
| 2154 |
processed in accordance with local BPSec security policy.<a href="#section-3.8.1-7" class="pilcrow">¶</a></p> |
| 2155 |
</section> |
| 2156 |
<section id="section-3.8.2"> |
| 2157 |
<h4 id="name-keyed-hash-verification"> |
| 2158 |
<a href="#section-3.8.2" class="section-number selfRef">3.8.2. </a><a href="#name-keyed-hash-verification" class="section-name selfRef">Keyed Hash Verification</a> |
| 2159 |
</h4> |
| 2160 |
<p id="section-3.8.2-1"> |
| 2161 |
During keyed hash verification, the input of the security target |
| 2162 |
and an HMAC key are provided to the appropriate HMAC/SHA2 algorithm.<a href="#section-3.8.2-1" class="pilcrow">¶</a></p> |
| 2163 |
<p id="section-3.8.2-2"> |
| 2164 |
During keyed hash verification, two inputs are prepared for |
| 2165 |
the appropriate HMAC/SHA2 algorithm: the HMAC key and the IPPT. |
| 2166 |
These data items <span class="bcp14">MUST</span> be generated as follows.<a href="#section-3.8.2-2" class="pilcrow">¶</a></p> |
| 2167 |
<ul class="normal"> |
| 2168 |
<li class="normal" id="section-3.8.2-3.1"> |
| 2169 |
The HMAC key <span class="bcp14">MUST</span> be derived using the wrapped key |
| 2170 |
security context parameter if such a parameter is included in the |
| 2171 |
security context parameters of the BIB. Otherwise, this key |
| 2172 |
<span class="bcp14">MUST</span> be derived in accordance with security policy at the |
| 2173 |
verifying node as discussed in <a href="#bib_key_mgmt" class="xref">Section 3.5</a>.<a href="#section-3.8.2-3.1" class="pilcrow">¶</a> |
| 2174 |
</li> |
| 2175 |
<li class="normal" id="section-3.8.2-3.2"> |
| 2176 |
The IPPT <span class="bcp14">MUST</span> be generated as discussed in <a href="#bib_canon" class="xref">Section 3.7</a> |
| 2177 |
with the value of integrity scope flags being taken from the |
| 2178 |
integrity scope flags security context parameter. If the |
| 2179 |
integrity scope flags parameter is not included in the |
| 2180 |
security context parameters, then these flags <span class="bcp14">MAY</span> be derived |
| 2181 |
from local security policy.<a href="#section-3.8.2-3.2" class="pilcrow">¶</a> |
| 2182 |
</li> |
| 2183 |
</ul> |
| 2184 |
<p id="section-3.8.2-4"> |
| 2185 |
The calculated HMAC output <span class="bcp14">MUST</span> be compared to the expected HMAC |
| 2186 |
output encoded in the security results of the BIB for the security |
| 2187 |
target. If the calculated HMAC and expected HMAC are |
| 2188 |
identical, the verification <span class="bcp14">MUST</span> be considered a success. Otherwise, |
| 2189 |
the verification <span class="bcp14">MUST</span> be considered a failure.<a href="#section-3.8.2-4" class="pilcrow">¶</a></p> |
| 2190 |
<p id="section-3.8.2-5"> |
| 2191 |
If the verification fails or otherwise experiences an error or if any |
| 2192 |
needed parameters are missing, then |
| 2193 |
the verification <span class="bcp14">MUST</span> be treated as failed and processed in accordance |
| 2194 |
with local security policy.<a href="#section-3.8.2-5" class="pilcrow">¶</a></p> |
| 2195 |
<p id="section-3.8.2-6"> |
| 2196 |
This security service is removed from the bundle at the |
| 2197 |
security acceptor as required by the BPSec specification <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>. If the |
| 2198 |
security acceptor is not the bundle destination and if no other |
| 2199 |
integrity service is being applied to the target block, then a |
| 2200 |
CRC <span class="bcp14">MUST</span> be included for the target block. The CRC type, as determined |
| 2201 |
by policy, is set in the target block's CRC type field, and the |
| 2202 |
corresponding CRC value is added as the CRC field for that block.<a href="#section-3.8.2-6" class="pilcrow">¶</a></p> |
| 2203 |
</section> |
| 2204 |
</section> |
| 2205 |
</section> |
| 2206 |
</div> |
| 2207 |
<div id="second-context"> |
| 2208 |
<section id="section-4"> |
| 2209 |
<h2 id="name-security-context-bcb-aes-gc"> |
| 2210 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-security-context-bcb-aes-gc" class="section-name selfRef">Security Context BCB-AES-GCM</a> |
| 2211 |
</h2> |
| 2212 |
<section id="section-4.1"> |
| 2213 |
<h3 id="name-overview-2"> |
| 2214 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-overview-2" class="section-name selfRef">Overview</a> |
| 2215 |
</h3> |
| 2216 |
<p id="section-4.1-1"> |
| 2217 |
The BCB-AES-GCM security context replaces the block-type-specific data |
| 2218 |
field of its security target with ciphertext generated using the |
| 2219 |
Advanced Encryption Standard (AES) cipher operating in Galois/Counter Mode |
| 2220 |
(GCM) <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>. The use of AES-GCM was selected |
| 2221 |
as the cipher suite for this confidentiality mechanism for several reasons:<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 2222 |
<ol start="1" type="1" class="normal type-1" id="section-4.1-2"> |
| 2223 |
<li id="section-4.1-2.1"> The selection of a symmetric-key cipher suite allows for relatively smaller |
| 2224 |
keys than asymmetric-key cipher suites.<a href="#section-4.1-2.1" class="pilcrow">¶</a> |
| 2225 |
</li> |
| 2226 |
<li id="section-4.1-2.2"> The selection of a symmetric-key cipher suite allows this security context to |
| 2227 |
be used in places where an asymmetric-key infrastructure (such as a public key |
| 2228 |
infrastructure) might be impractical.<a href="#section-4.1-2.2" class="pilcrow">¶</a> |
| 2229 |
</li> |
| 2230 |
<li id="section-4.1-2.3"> |
| 2231 |
The use of the Galois/Counter Mode produces ciphertext with the same size as |
| 2232 |
the plaintext making the replacement of target block information easier as |
| 2233 |
length fields do not need to be changed.<a href="#section-4.1-2.3" class="pilcrow">¶</a> |
| 2234 |
</li> |
| 2235 |
<li id="section-4.1-2.4"> |
| 2236 |
The AES-GCM cipher suite provides authenticated encryption, as required by the |
| 2237 |
BPSec protocol.<a href="#section-4.1-2.4" class="pilcrow">¶</a> |
| 2238 |
</li> |
| 2239 |
</ol> |
| 2240 |
<p id="section-4.1-3"> |
| 2241 |
Additionally, the BCB-AES-GCM security context generates an |
| 2242 |
authentication tag based on the plaintext value of the block-type-specific |
| 2243 |
data and other additional authenticated data (AAD) that might be specified |
| 2244 |
via parameters to this security context.<a href="#section-4.1-3" class="pilcrow">¶</a></p> |
| 2245 |
<p id="section-4.1-4"> |
| 2246 |
This security context supports two variants of AES-GCM, based on |
| 2247 |
the supported length of the symmetric key. These variants |
| 2248 |
correspond to A128GCM and A256GCM as |
| 2249 |
defined in Table 9 ("Algorithm Value for AES-GCM") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span>.<a href="#section-4.1-4" class="pilcrow">¶</a></p> |
| 2250 |
<p id="section-4.1-5"> |
| 2251 |
The BCB-AES-GCM security context <span class="bcp14">MUST</span> have the security context identifier |
| 2252 |
specified in <a href="#sc_ids" class="xref">Section 5.1</a>.<a href="#section-4.1-5" class="pilcrow">¶</a></p> |
| 2253 |
</section> |
| 2254 |
<section id="section-4.2"> |
| 2255 |
<h3 id="name-scope-2"> |
| 2256 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-scope-2" class="section-name selfRef">Scope</a> |
| 2257 |
</h3> |
| 2258 |
<p id="section-4.2-1"> |
| 2259 |
There are two scopes associated with BCB-AES-GCM: the scope of the |
| 2260 |
confidentiality service and the scope of the authentication |
| 2261 |
service. The first defines the set of information provided to the |
| 2262 |
AES-GCM cipher for the purpose of producing ciphertext. The second |
| 2263 |
defines the set of information used to generate an authentication tag.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 2264 |
<p id="section-4.2-2"> |
| 2265 |
The scope of the confidentiality service defines the set of information |
| 2266 |
provided to the AES-GCM cipher for the purpose of producing ciphertext. |
| 2267 |
This <span class="bcp14">MUST</span> be the full set of plaintext contained in the |
| 2268 |
block-type-specific data field of the security target.<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 2269 |
<p id="section-4.2-3"> |
| 2270 |
The scope of the authentication service defines the set of information |
| 2271 |
used to generate an authentication tag carried with the security |
| 2272 |
block. This information contains all data protected by the |
| 2273 |
confidentiality service and the scope flags used to identify other |
| 2274 |
optional information; it <span class="bcp14">MAY</span> include other information |
| 2275 |
(additional authenticated data), as follows.<a href="#section-4.2-3" class="pilcrow">¶</a></p> |
| 2276 |
<span class="break"></span><dl class="dlNewline" id="section-4.2-4"> |
| 2277 |
<dt id="section-4.2-4.1">Primary block</dt> |
| 2278 |
<dd style="margin-left: 1.5em" id="section-4.2-4.2"> |
| 2279 |
<p id="section-4.2-4.2.1"> |
| 2280 |
The primary block identifies a bundle, and once |
| 2281 |
created, the contents of this block are immutable. Changes to |
| 2282 |
the primary block associated with the security target indicate |
| 2283 |
that the security target (and BCB) might no longer be in the |
| 2284 |
correct bundle.<a href="#section-4.2-4.2.1" class="pilcrow">¶</a></p> |
| 2285 |
<p id="section-4.2-4.2.2"> |
| 2286 |
For example, if a security target and associated BCB are copied |
| 2287 |
from one bundle to another bundle, the BCB might still be able to |
| 2288 |
decrypt the security target even though these blocks were never |
| 2289 |
intended to exist in the copied-to bundle.<a href="#section-4.2-4.2.2" class="pilcrow">¶</a></p> |
| 2290 |
<p id="section-4.2-4.2.3"> |
| 2291 |
Including this information as part of additional authenticated data |
| 2292 |
ensures that the security target (and security block) appear in the |
| 2293 |
same bundle at the time of decryption as at the time of encryption.<a href="#section-4.2-4.2.3" class="pilcrow">¶</a></p> |
| 2294 |
</dd> |
| 2295 |
<dd class="break"></dd> |
| 2296 |
<dt id="section-4.2-4.3">Other fields of the security target</dt> |
| 2297 |
<dd style="margin-left: 1.5em" id="section-4.2-4.4"> |
| 2298 |
<p id="section-4.2-4.4.1"> |
| 2299 |
The other fields of the security target include block |
| 2300 |
identification and processing information. Changing this |
| 2301 |
information changes how the security target is treated by nodes |
| 2302 |
in the network even when the "user data" of the security target |
| 2303 |
are otherwise unchanged.<a href="#section-4.2-4.4.1" class="pilcrow">¶</a></p> |
| 2304 |
<p id="section-4.2-4.4.2"> |
| 2305 |
For example, if the block processing control flags of a security |
| 2306 |
target are different at a security verifier than they were |
| 2307 |
originally set at the security source, then the policy for |
| 2308 |
handling the security target has been modified.<a href="#section-4.2-4.4.2" class="pilcrow">¶</a></p> |
| 2309 |
<p id="section-4.2-4.4.3"> |
| 2310 |
Including this information as part of additional authenticated data |
| 2311 |
ensures that the ciphertext in the security target will not be used |
| 2312 |
with a different set of block policy than originally set at the |
| 2313 |
time of encryption.<a href="#section-4.2-4.4.3" class="pilcrow">¶</a></p> |
| 2314 |
</dd> |
| 2315 |
<dd class="break"></dd> |
| 2316 |
<dt id="section-4.2-4.5">Other fields of the BCB</dt> |
| 2317 |
<dd style="margin-left: 1.5em" id="section-4.2-4.6"> |
| 2318 |
<p id="section-4.2-4.6.1"> |
| 2319 |
The other fields of the BCB include block identification and |
| 2320 |
processing information. Changing this information changes how the BCB |
| 2321 |
is treated by nodes in the network, even when other aspects of the |
| 2322 |
BCB are unchanged.<a href="#section-4.2-4.6.1" class="pilcrow">¶</a></p> |
| 2323 |
<p id="section-4.2-4.6.2"> |
| 2324 |
For example, if the block processing control flags of the BCB are |
| 2325 |
different at a security acceptor than they were |
| 2326 |
originally set at the security source, then the policy for |
| 2327 |
handling the BCB has been modified.<a href="#section-4.2-4.6.2" class="pilcrow">¶</a></p> |
| 2328 |
<p id="section-4.2-4.6.3"> |
| 2329 |
Including this information as part of additional authenticated data |
| 2330 |
ensures that the policy and identification of the security service |
| 2331 |
in the bundle has not changed.<a href="#section-4.2-4.6.3" class="pilcrow">¶</a></p> |
| 2332 |
<aside id="section-4.2-4.6.4"> |
| 2333 |
<p id="section-4.2-4.6.4.1"> |
| 2334 |
NOTE: The security context identifier and security context |
| 2335 |
parameters of the security block are not included as additional |
| 2336 |
authenticated data because these parameters, by definition, are |
| 2337 |
those needed to verify or accept the security service. Therefore, |
| 2338 |
it is expected that changes to these values would result in failures |
| 2339 |
at security verifiers and security acceptors. This is the case |
| 2340 |
because keys cannot be reused across security |
| 2341 |
contexts and because the AAD scope flags used to identify |
| 2342 |
the AAD are included in the AAD.<a href="#section-4.2-4.6.4.1" class="pilcrow">¶</a></p> |
| 2343 |
</aside> |
| 2344 |
</dd> |
| 2345 |
<dd class="break"></dd> |
| 2346 |
</dl> |
| 2347 |
<p id="section-4.2-5"> |
| 2348 |
The scope of the BCB-AES-GCM security context is configured using |
| 2349 |
an optional security context parameter.<a href="#section-4.2-5" class="pilcrow">¶</a></p> |
| 2350 |
</section> |
| 2351 |
<section id="section-4.3"> |
| 2352 |
<h3 id="name-parameters-2"> |
| 2353 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-parameters-2" class="section-name selfRef">Parameters</a> |
| 2354 |
</h3> |
| 2355 |
<p id="section-4.3-1"> |
| 2356 |
BCB-AES-GCM can be parameterized to specify the AES variant, |
| 2357 |
initialization vector, key information, and identify additional |
| 2358 |
authenticated data.<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 2359 |
<section id="section-4.3.1"> |
| 2360 |
<h4 id="name-initialization-vector-iv"> |
| 2361 |
<a href="#section-4.3.1" class="section-number selfRef">4.3.1. </a><a href="#name-initialization-vector-iv" class="section-name selfRef">Initialization Vector (IV)</a> |
| 2362 |
</h4> |
| 2363 |
<p id="section-4.3.1-1"> |
| 2364 |
This optional parameter identifies the initialization vector (IV) |
| 2365 |
used to initialize the AES-GCM cipher.<a href="#section-4.3.1-1" class="pilcrow">¶</a></p> |
| 2366 |
<p id="section-4.3.1-2"> |
| 2367 |
The length of the initialization vector, prior to any CBOR encoding, |
| 2368 |
<span class="bcp14">MUST</span> be between 8-16 bytes. A value of 12 bytes <span class="bcp14">SHOULD</span> be used |
| 2369 |
unless local security policy requires a different length.<a href="#section-4.3.1-2" class="pilcrow">¶</a></p> |
| 2370 |
<p id="section-4.3.1-3"> |
| 2371 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR byte string.<a href="#section-4.3.1-3" class="pilcrow">¶</a></p> |
| 2372 |
<p id="section-4.3.1-4"> |
| 2373 |
The initialization vector can have any value, with the caveat that a |
| 2374 |
value <span class="bcp14">MUST NOT</span> be reused for multiple encryptions using the same |
| 2375 |
encryption key. This value <span class="bcp14">MAY</span> be reused when encrypting with different |
| 2376 |
keys. For example, if each encryption operation using BCB-AES-GCM |
| 2377 |
uses a newly generated key, then the same IV can be reused.<a href="#section-4.3.1-4" class="pilcrow">¶</a></p> |
| 2378 |
</section> |
| 2379 |
<section id="section-4.3.2"> |
| 2380 |
<h4 id="name-aes-variant"> |
| 2381 |
<a href="#section-4.3.2" class="section-number selfRef">4.3.2. </a><a href="#name-aes-variant" class="section-name selfRef">AES Variant</a> |
| 2382 |
</h4> |
| 2383 |
<p id="section-4.3.2-1"> |
| 2384 |
This optional parameter identifies the AES variant being used for |
| 2385 |
the AES-GCM encryption, where the variant is identified by the length |
| 2386 |
of key used.<a href="#section-4.3.2-1" class="pilcrow">¶</a></p> |
| 2387 |
<p id="section-4.3.2-2"> |
| 2388 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR unsigned integer.<a href="#section-4.3.2-2" class="pilcrow">¶</a></p> |
| 2389 |
<p id="section-4.3.2-3"> |
| 2390 |
Valid values for this parameter are as follows.<a href="#section-4.3.2-3" class="pilcrow">¶</a></p> |
| 2391 |
<span id="name-aes-variant-parameter-value"></span><table class="center" id="table-4"> |
| 2392 |
<caption> |
| 2393 |
<a href="#table-4" class="selfRef">Table 4</a>: |
| 2394 |
<a href="#name-aes-variant-parameter-value" class="selfRef">AES Variant Parameter Values</a> |
| 2395 |
</caption> |
| 2396 |
<thead> |
| 2397 |
<tr> |
| 2398 |
<th class="text-center" rowspan="1" colspan="1">Value</th> |
| 2399 |
<th class="text-center" rowspan="1" colspan="1">Description</th> |
| 2400 |
</tr> |
| 2401 |
</thead> |
| 2402 |
<tbody> |
| 2403 |
<tr> |
| 2404 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 2405 |
<td class="text-left" rowspan="1" colspan="1">A128GCM as defined in Table 9 ("Algorithm Value for AES-GCM") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span> |
| 2406 |
</td> |
| 2407 |
</tr> |
| 2408 |
<tr> |
| 2409 |
<td class="text-center" rowspan="1" colspan="1">3</td> |
| 2410 |
<td class="text-left" rowspan="1" colspan="1">A256GCM as defined in Table 9 ("Algorithm Value for AES-GCM") of <span>[<a href="#RFC8152" class="xref">RFC8152</a>]</span> |
| 2411 |
</td> |
| 2412 |
</tr> |
| 2413 |
</tbody> |
| 2414 |
</table> |
| 2415 |
<p id="section-4.3.2-5"> |
| 2416 |
When not provided, implementations <span class="bcp14">SHOULD</span> assume a value of 3 |
| 2417 |
(indicating use of A256GCM), unless an alternate default is |
| 2418 |
established by local security policy at the security source, verifier, |
| 2419 |
or acceptor of this integrity service.<a href="#section-4.3.2-5" class="pilcrow">¶</a></p> |
| 2420 |
<p id="section-4.3.2-6"> |
| 2421 |
Regardless of the variant, the generated authentication tag <span class="bcp14">MUST</span> |
| 2422 |
always be 128 bits.<a href="#section-4.3.2-6" class="pilcrow">¶</a></p> |
| 2423 |
</section> |
| 2424 |
<section id="section-4.3.3"> |
| 2425 |
<h4 id="name-wrapped-key-2"> |
| 2426 |
<a href="#section-4.3.3" class="section-number selfRef">4.3.3. </a><a href="#name-wrapped-key-2" class="section-name selfRef">Wrapped Key</a> |
| 2427 |
</h4> |
| 2428 |
<p id="section-4.3.3-1"> |
| 2429 |
This optional parameter contains the output of the AES key wrap function as defined in <span>[<a href="#RFC3394" class="xref">RFC3394</a>]</span>. Specifically, this parameter holds the ciphertext produced when running this key wrap algorithm with |
| 2430 |
the input string being the symmetric AES key used to generate the security results |
| 2431 |
present in the security block. |
| 2432 |
The value of this parameter is used as input to the AES key wrap authenticated |
| 2433 |
decryption function at security verifiers and security acceptors to determine |
| 2434 |
the symmetric AES key needed for the proper decryption of the security results |
| 2435 |
in the security block.<a href="#section-4.3.3-1" class="pilcrow">¶</a></p> |
| 2436 |
<p id="section-4.3.3-2"> |
| 2437 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR byte string.<a href="#section-4.3.3-2" class="pilcrow">¶</a></p> |
| 2438 |
<p id="section-4.3.3-3"> |
| 2439 |
If this parameter is not present, then security verifiers |
| 2440 |
and acceptors <span class="bcp14">MUST</span> determine the proper key as a function of their local BPSec policy |
| 2441 |
and configuration.<a href="#section-4.3.3-3" class="pilcrow">¶</a></p> |
| 2442 |
</section> |
| 2443 |
<section id="section-4.3.4"> |
| 2444 |
<h4 id="name-aad-scope-flags"> |
| 2445 |
<a href="#section-4.3.4" class="section-number selfRef">4.3.4. </a><a href="#name-aad-scope-flags" class="section-name selfRef">AAD Scope Flags</a> |
| 2446 |
</h4> |
| 2447 |
<p id="section-4.3.4-1"> |
| 2448 |
This optional parameter contains a series of flags that describe |
| 2449 |
what information is to be included with the |
| 2450 |
block-type-specific data of the security target as part of |
| 2451 |
additional authenticated data (AAD).<a href="#section-4.3.4-1" class="pilcrow">¶</a></p> |
| 2452 |
<p id="section-4.3.4-2"> |
| 2453 |
This value <span class="bcp14">MUST</span> be represented as a CBOR unsigned |
| 2454 |
integer, the value of which <span class="bcp14">MUST</span> be processed as a 16-bit field. |
| 2455 |
The maximum value of this field, as a CBOR unsigned integer, <span class="bcp14">MUST</span> be |
| 2456 |
65535.<a href="#section-4.3.4-2" class="pilcrow">¶</a></p> |
| 2457 |
<p id="section-4.3.4-3">When not provided, implementations <span class="bcp14">SHOULD</span> assume a value of 7 |
| 2458 |
(indicating all assigned fields), unless an alternate default is |
| 2459 |
established by local security policy at the security source, |
| 2460 |
verifier, or acceptor of this integrity service.<a href="#section-4.3.4-3" class="pilcrow">¶</a></p> |
| 2461 |
<p id="section-4.3.4-4"> |
| 2462 |
Implementations <span class="bcp14">MUST</span> set reserved and unassigned bits in this |
| 2463 |
field to 0 when constructing these flags at a security source. |
| 2464 |
Once set, the value of this field <span class="bcp14">MUST NOT</span> be altered until the |
| 2465 |
security service is completed at the security acceptor in the |
| 2466 |
network and removed from the bundle.<a href="#section-4.3.4-4" class="pilcrow">¶</a></p> |
| 2467 |
<p id="section-4.3.4-5"> |
| 2468 |
Bits in this field represent additional information to be included |
| 2469 |
when generating an integrity signature over the security target. |
| 2470 |
These bits are defined as follows.<a href="#section-4.3.4-5" class="pilcrow">¶</a></p> |
| 2471 |
<span class="break"></span><dl class="dlParallel" id="section-4.3.4-6"> |
| 2472 |
<dt id="section-4.3.4-6.1">Bit 0 (the low-order bit, 0x0001):</dt> |
| 2473 |
<dd style="margin-left: 1.5em" id="section-4.3.4-6.2">Include primary block flag<a href="#section-4.3.4-6.2" class="pilcrow">¶</a> |
| 2474 |
</dd> |
| 2475 |
<dd class="break"></dd> |
| 2476 |
<dt id="section-4.3.4-6.3">Bit 1 (0x0002):</dt> |
| 2477 |
<dd style="margin-left: 1.5em" id="section-4.3.4-6.4">Include target header flag<a href="#section-4.3.4-6.4" class="pilcrow">¶</a> |
| 2478 |
</dd> |
| 2479 |
<dd class="break"></dd> |
| 2480 |
<dt id="section-4.3.4-6.5">Bit 2 (0x0004):</dt> |
| 2481 |
<dd style="margin-left: 1.5em" id="section-4.3.4-6.6">Include security header flag<a href="#section-4.3.4-6.6" class="pilcrow">¶</a> |
| 2482 |
</dd> |
| 2483 |
<dd class="break"></dd> |
| 2484 |
<dt id="section-4.3.4-6.7">Bits 3-7:</dt> |
| 2485 |
<dd style="margin-left: 1.5em" id="section-4.3.4-6.8">Reserved<a href="#section-4.3.4-6.8" class="pilcrow">¶</a> |
| 2486 |
</dd> |
| 2487 |
<dd class="break"></dd> |
| 2488 |
<dt id="section-4.3.4-6.9">Bits 8-15:</dt> |
| 2489 |
<dd style="margin-left: 1.5em" id="section-4.3.4-6.10">Unassigned<a href="#section-4.3.4-6.10" class="pilcrow">¶</a> |
| 2490 |
</dd> |
| 2491 |
<dd class="break"></dd> |
| 2492 |
</dl> |
| 2493 |
</section> |
| 2494 |
<section id="section-4.3.5"> |
| 2495 |
<h4 id="name-enumerations-2"> |
| 2496 |
<a href="#section-4.3.5" class="section-number selfRef">4.3.5. </a><a href="#name-enumerations-2" class="section-name selfRef">Enumerations</a> |
| 2497 |
</h4> |
| 2498 |
<p id="section-4.3.5-1"> |
| 2499 |
The BCB-AES-GCM security context parameters are listed in |
| 2500 |
<a href="#bcb_parm_table" class="xref">Table 5</a>. In this table, the "Parm Id" column |
| 2501 |
refers to the expected parameter identifier described in Section |
| 2502 |
<span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">3.10</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">"Parameter |
| 2503 |
and Result Identification"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#section-4.3.5-1" class="pilcrow">¶</a></p> |
| 2504 |
<p id="section-4.3.5-2"> |
| 2505 |
An empty "Default Value" column indicates that the |
| 2506 |
security context parameter does not have a default value.<a href="#section-4.3.5-2" class="pilcrow">¶</a></p> |
| 2507 |
<span id="name-bcb-aes-gcm-security-contex"></span><div id="bcb_parm_table"> |
| 2508 |
<table class="center" id="table-5"> |
| 2509 |
<caption> |
| 2510 |
<a href="#table-5" class="selfRef">Table 5</a>: |
| 2511 |
<a href="#name-bcb-aes-gcm-security-contex" class="selfRef">BCB-AES-GCM Security Context Parameters</a> |
| 2512 |
</caption> |
| 2513 |
<thead> |
| 2514 |
<tr> |
| 2515 |
<th class="text-center" rowspan="1" colspan="1">Parm Id</th> |
| 2516 |
<th class="text-center" rowspan="1" colspan="1">Parm Name</th> |
| 2517 |
<th class="text-center" rowspan="1" colspan="1">CBOR Encoding Type</th> |
| 2518 |
<th class="text-center" rowspan="1" colspan="1">Default Value</th> |
| 2519 |
</tr> |
| 2520 |
</thead> |
| 2521 |
<tbody> |
| 2522 |
<tr> |
| 2523 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 2524 |
<td class="text-center" rowspan="1" colspan="1">Initialization Vector</td> |
| 2525 |
<td class="text-center" rowspan="1" colspan="1">byte string</td> |
| 2526 |
<td class="text-center" rowspan="1" colspan="1"></td> |
| 2527 |
</tr> |
| 2528 |
<tr> |
| 2529 |
<td class="text-center" rowspan="1" colspan="1">2</td> |
| 2530 |
<td class="text-center" rowspan="1" colspan="1">AES Variant</td> |
| 2531 |
<td class="text-center" rowspan="1" colspan="1">unsigned integer</td> |
| 2532 |
<td class="text-center" rowspan="1" colspan="1">3</td> |
| 2533 |
</tr> |
| 2534 |
<tr> |
| 2535 |
<td class="text-center" rowspan="1" colspan="1">3</td> |
| 2536 |
<td class="text-center" rowspan="1" colspan="1">Wrapped Key</td> |
| 2537 |
<td class="text-center" rowspan="1" colspan="1">byte string</td> |
| 2538 |
<td class="text-center" rowspan="1" colspan="1"></td> |
| 2539 |
</tr> |
| 2540 |
<tr> |
| 2541 |
<td class="text-center" rowspan="1" colspan="1">4</td> |
| 2542 |
<td class="text-center" rowspan="1" colspan="1">AAD Scope Flags</td> |
| 2543 |
<td class="text-center" rowspan="1" colspan="1">unsigned integer</td> |
| 2544 |
<td class="text-center" rowspan="1" colspan="1">7</td> |
| 2545 |
</tr> |
| 2546 |
</tbody> |
| 2547 |
</table> |
| 2548 |
</div> |
| 2549 |
</section> |
| 2550 |
</section> |
| 2551 |
<div id="bcb_results"> |
| 2552 |
<section id="section-4.4"> |
| 2553 |
<h3 id="name-results-2"> |
| 2554 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-results-2" class="section-name selfRef">Results</a> |
| 2555 |
</h3> |
| 2556 |
<p id="section-4.4-1"> |
| 2557 |
The BCB-AES-GCM security context produces a single security result |
| 2558 |
carried in the security block: the authentication tag.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 2559 |
<p id="section-4.4-2"> |
| 2560 |
NOTES:<a href="#section-4.4-2" class="pilcrow">¶</a></p> |
| 2561 |
<ul class="normal"> |
| 2562 |
<li class="normal" id="section-4.4-3.1"> |
| 2563 |
The ciphertext generated by the cipher suite is not considered a |
| 2564 |
security result as it is stored in the block-type-specific data field |
| 2565 |
of the security target block. When operating in GCM mode, AES produces |
| 2566 |
ciphertext of the same size as its plaintext; therefore, |
| 2567 |
no additional logic is required to handle padding or overflow caused |
| 2568 |
by the encryption in most cases.<a href="#section-4.4-3.1" class="pilcrow">¶</a> |
| 2569 |
</li> |
| 2570 |
<li class="normal" id="section-4.4-3.2"> |
| 2571 |
If the authentication tag can be separated from the ciphertext, then |
| 2572 |
the tag <span class="bcp14">MAY</span> be separated and stored in the authentication tag |
| 2573 |
security result field. Otherwise, the security target block <span class="bcp14">MUST</span> be |
| 2574 |
resized to accommodate the additional 128 bits of authentication |
| 2575 |
tag included with the generated ciphertext replacing the |
| 2576 |
block-type-specific data field of the security target block.<a href="#section-4.4-3.2" class="pilcrow">¶</a> |
| 2577 |
</li> |
| 2578 |
</ul> |
| 2579 |
<section id="section-4.4.1"> |
| 2580 |
<h4 id="name-authentication-tag"> |
| 2581 |
<a href="#section-4.4.1" class="section-number selfRef">4.4.1. </a><a href="#name-authentication-tag" class="section-name selfRef">Authentication Tag</a> |
| 2582 |
</h4> |
| 2583 |
<p id="section-4.4.1-1"> |
| 2584 |
The authentication tag is generated by the cipher suite over the |
| 2585 |
security target plaintext input to the cipher suite as combined with |
| 2586 |
any optional additional authenticated data. This tag is used to ensure |
| 2587 |
that the plaintext (and important information associated with the |
| 2588 |
plaintext) is authenticated prior to decryption.<a href="#section-4.4.1-1" class="pilcrow">¶</a></p> |
| 2589 |
<p id="section-4.4.1-2"> |
| 2590 |
If the authentication tag is included in the ciphertext placed |
| 2591 |
in the security target block-type-specific data field, then this |
| 2592 |
security result <span class="bcp14">MUST NOT</span> be included in the BCB for that security |
| 2593 |
target.<a href="#section-4.4.1-2" class="pilcrow">¶</a></p> |
| 2594 |
<p id="section-4.4.1-3"> |
| 2595 |
The length of the authentication tag, prior to any CBOR encoding, |
| 2596 |
<span class="bcp14">MUST</span> be 128 bits.<a href="#section-4.4.1-3" class="pilcrow">¶</a></p> |
| 2597 |
<p id="section-4.4.1-4"> |
| 2598 |
This value <span class="bcp14">MUST</span> be encoded as a CBOR byte string.<a href="#section-4.4.1-4" class="pilcrow">¶</a></p> |
| 2599 |
</section> |
| 2600 |
<section id="section-4.4.2"> |
| 2601 |
<h4 id="name-enumerations-3"> |
| 2602 |
<a href="#section-4.4.2" class="section-number selfRef">4.4.2. </a><a href="#name-enumerations-3" class="section-name selfRef">Enumerations</a> |
| 2603 |
</h4> |
| 2604 |
<p id="section-4.4.2-1"> |
| 2605 |
The BCB-AES-GCM security context results are listed in |
| 2606 |
<a href="#bcb_res_table" class="xref">Table 6</a>. In this table, the "Result Id" column |
| 2607 |
refers to the expected result identifier described in Section |
| 2608 |
<span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">3.10</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.10" class="relref">"Parameter |
| 2609 |
and Result Identification"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#section-4.4.2-1" class="pilcrow">¶</a></p> |
| 2610 |
<span id="name-bcb-aes-gcm-security-result"></span><div id="bcb_res_table"> |
| 2611 |
<table class="center" id="table-6"> |
| 2612 |
<caption> |
| 2613 |
<a href="#table-6" class="selfRef">Table 6</a>: |
| 2614 |
<a href="#name-bcb-aes-gcm-security-result" class="selfRef">BCB-AES-GCM Security Results</a> |
| 2615 |
</caption> |
| 2616 |
<thead> |
| 2617 |
<tr> |
| 2618 |
<th class="text-center" rowspan="1" colspan="1">Result Id</th> |
| 2619 |
<th class="text-center" rowspan="1" colspan="1">Result Name</th> |
| 2620 |
<th class="text-center" rowspan="1" colspan="1">CBOR Encoding Type</th> |
| 2621 |
</tr> |
| 2622 |
</thead> |
| 2623 |
<tbody> |
| 2624 |
<tr> |
| 2625 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 2626 |
<td class="text-center" rowspan="1" colspan="1">Authentication Tag</td> |
| 2627 |
<td class="text-center" rowspan="1" colspan="1">byte string</td> |
| 2628 |
</tr> |
| 2629 |
</tbody> |
| 2630 |
</table> |
| 2631 |
</div> |
| 2632 |
</section> |
| 2633 |
</section> |
| 2634 |
</div> |
| 2635 |
<div id="bcb_key_mgmt"> |
| 2636 |
<section id="section-4.5"> |
| 2637 |
<h3 id="name-key-considerations-2"> |
| 2638 |
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-key-considerations-2" class="section-name selfRef">Key Considerations</a> |
| 2639 |
</h3> |
| 2640 |
<p id="section-4.5-1"> |
| 2641 |
Keys used with this context <span class="bcp14">MUST</span> be symmetric and <span class="bcp14">MUST</span> have |
| 2642 |
a key length equal to the key length defined in the security |
| 2643 |
context parameters or as defined by local security policy at |
| 2644 |
security verifiers and acceptors. For this reason, content-encrypting |
| 2645 |
key lengths will be integers divisible by 8 bytes, and special padding-aware AES |
| 2646 |
key wrap algorithms are not needed.<a href="#section-4.5-1" class="pilcrow">¶</a></p> |
| 2647 |
<p id="section-4.5-2"> |
| 2648 |
It is assumed that any security verifier or security acceptor |
| 2649 |
can determine the proper key to be used. Potential sources of the key |
| 2650 |
include (but are not limited to) the following.<a href="#section-4.5-2" class="pilcrow">¶</a></p> |
| 2651 |
<ul class="normal"> |
| 2652 |
<li class="normal" id="section-4.5-3.1">Pre-placed keys selected based on local policy.<a href="#section-4.5-3.1" class="pilcrow">¶</a> |
| 2653 |
</li> |
| 2654 |
<li class="normal" id="section-4.5-3.2">Keys extracted from material carried in the BCB.<a href="#section-4.5-3.2" class="pilcrow">¶</a> |
| 2655 |
</li> |
| 2656 |
<li class="normal" id="section-4.5-3.3">Session keys negotiated via a mechanism external to the BCB.<a href="#section-4.5-3.3" class="pilcrow">¶</a> |
| 2657 |
</li> |
| 2658 |
</ul> |
| 2659 |
<p id="section-4.5-4"> |
| 2660 |
When an AES-KW wrapped key is present in a security block, it is assumed that |
| 2661 |
security verifiers and security acceptors can independently determine the |
| 2662 |
KEK used in the wrapping of the symmetric AES content-encrypting key.<a href="#section-4.5-4" class="pilcrow">¶</a></p> |
| 2663 |
<p id="section-4.5-5"> |
| 2664 |
The security provided by block ciphers is reduced as more data is |
| 2665 |
processed with the same key. The total number of AES blocks processed with |
| 2666 |
a single key for AES-GCM is recommended to be less than 2<sup>64</sup>, as |
| 2667 |
described in Appendix B of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>.<a href="#section-4.5-5" class="pilcrow">¶</a></p> |
| 2668 |
<p id="section-4.5-6"> |
| 2669 |
Additionally, there exist limits on the number of encryptions that |
| 2670 |
can be performed with the same key. The total number of invocations |
| 2671 |
of the authenticated encryption function with a single key for |
| 2672 |
AES-GCM is required to not exceed 2<sup>32</sup>, as described in Section |
| 2673 |
8.3 of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>.<a href="#section-4.5-6" class="pilcrow">¶</a></p> |
| 2674 |
<p id="section-4.5-7"> |
| 2675 |
As discussed in <a href="#SecCons" class="xref">Section 6</a> and emphasized here, it is |
| 2676 |
strongly recommended that keys be protected once generated, both |
| 2677 |
when they are stored and when they are transmitted.<a href="#section-4.5-7" class="pilcrow">¶</a></p> |
| 2678 |
</section> |
| 2679 |
</div> |
| 2680 |
<div id="GcmCons"> |
| 2681 |
<section id="section-4.6"> |
| 2682 |
<h3 id="name-gcm-considerations"> |
| 2683 |
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-gcm-considerations" class="section-name selfRef">GCM Considerations</a> |
| 2684 |
</h3> |
| 2685 |
<p id="section-4.6-1"> |
| 2686 |
The GCM cryptographic mode of AES has specific requirements that |
| 2687 |
<span class="bcp14">MUST</span> be followed by implementers for the secure function of the |
| 2688 |
BCB-AES-GCM security context. While these requirements are well |
| 2689 |
documented in <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>, some of them are |
| 2690 |
repeated here for emphasis.<a href="#section-4.6-1" class="pilcrow">¶</a></p> |
| 2691 |
<ul class="normal"> |
| 2692 |
<li class="normal" id="section-4.6-2.1"> |
| 2693 |
<p id="section-4.6-2.1.1"> |
| 2694 |
With the exception of the AES-KW function, the IVs |
| 2695 |
used by the BCB-AES-GCM security context are considered to |
| 2696 |
be per-invocation IVs. |
| 2697 |
The pairing of a per-invocation IV and a security key |
| 2698 |
<span class="bcp14">MUST</span> be unique. A per-invocation IV <span class="bcp14">MUST NOT</span> be used with a security |
| 2699 |
key more than one time. If a per-invocation IV and key pair are repeated, then the GCM implementation |
| 2700 |
is vulnerable to forgery attacks. Because the loss of integrity protection |
| 2701 |
occurs with even a single reuse, this situation is often considered to have |
| 2702 |
catastrophic security consequences. More information regarding |
| 2703 |
the importance of the uniqueness of the IV value can be found in |
| 2704 |
Appendix A of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>.<a href="#section-4.6-2.1.1" class="pilcrow">¶</a></p> |
| 2705 |
<p id="section-4.6-2.1.2"> |
| 2706 |
Methods of generating unique IV values are provided in Section 8 |
| 2707 |
of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>. For example, one method decomposes the |
| 2708 |
IV value into a fixed field and an invocation field. The fixed field |
| 2709 |
is a constant value associated with a device, and the invocation |
| 2710 |
field changes on each invocation (such as by incrementing an |
| 2711 |
integer counter). Implementers <span class="bcp14">SHOULD</span> carefully read |
| 2712 |
all relevant sections of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span> when generating |
| 2713 |
any mechanism to create unique IVs.<a href="#section-4.6-2.1.2" class="pilcrow">¶</a></p> |
| 2714 |
</li> |
| 2715 |
<li class="normal" id="section-4.6-2.2"> |
| 2716 |
The AES-KW function used to wrap keys for the security contexts in this document uses |
| 2717 |
a single, globally constant IV input to the AES cipher |
| 2718 |
operation and thus is distinct from the aforementioned |
| 2719 |
requirement related to per-invocation IVs.<a href="#section-4.6-2.2" class="pilcrow">¶</a> |
| 2720 |
</li> |
| 2721 |
<li class="normal" id="section-4.6-2.3"> |
| 2722 |
While any tag-based authentication mechanism has some likelihood |
| 2723 |
of being forged, this probability is increased when using AES-GCM. |
| 2724 |
In particular, short tag lengths combined with very long messages |
| 2725 |
<span class="bcp14">SHOULD</span> be avoided when using this mode. The BCB-AES-GCM security |
| 2726 |
context requires the use of 128-bit authentication tags at all |
| 2727 |
times. Concerns relating to the size of authentication tags is |
| 2728 |
discussed in Appendices B and C of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>.<a href="#section-4.6-2.3" class="pilcrow">¶</a> |
| 2729 |
</li> |
| 2730 |
<li class="normal" id="section-4.6-2.4"> |
| 2731 |
As discussed in Appendix B of <span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>, |
| 2732 |
implementations <span class="bcp14">SHOULD</span> limit the number of unsuccessful |
| 2733 |
verification attempts for each key to reduce the likelihood |
| 2734 |
of guessing tag values. This type of check has potential |
| 2735 |
state-keeping issues when AES-KW is used, since an attacker |
| 2736 |
could cause a large number of keys to be used at least |
| 2737 |
once.<a href="#section-4.6-2.4" class="pilcrow">¶</a> |
| 2738 |
</li> |
| 2739 |
<li class="normal" id="section-4.6-2.5"> |
| 2740 |
As discussed in Section |
| 2741 |
<span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-8" class="relref">8</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-8" class="relref">"Security Considerations"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>, delay-tolerant networks have a higher |
| 2742 |
occurrence of replay attacks due to the store-and-forward nature |
| 2743 |
of the network. Because GCM has no inherent replay attack |
| 2744 |
protection, implementors <span class="bcp14">SHOULD</span> attempt to detect replay attacks |
| 2745 |
by using mechanisms such as those described in Appendix D of |
| 2746 |
<span>[<a href="#AES-GCM" class="xref">AES-GCM</a>]</span>.<a href="#section-4.6-2.5" class="pilcrow">¶</a> |
| 2747 |
</li> |
| 2748 |
</ul> |
| 2749 |
</section> |
| 2750 |
</div> |
| 2751 |
<section id="section-4.7"> |
| 2752 |
<h3 id="name-canonicalization-algorithms-2"> |
| 2753 |
<a href="#section-4.7" class="section-number selfRef">4.7. </a><a href="#name-canonicalization-algorithms-2" class="section-name selfRef">Canonicalization Algorithms</a> |
| 2754 |
</h3> |
| 2755 |
<p id="section-4.7-1"> |
| 2756 |
This section defines the canonicalization algorithms used to prepare |
| 2757 |
the inputs used to generate both the ciphertext and the |
| 2758 |
authentication tag.<a href="#section-4.7-1" class="pilcrow">¶</a></p> |
| 2759 |
<p id="section-4.7-2"> |
| 2760 |
In all cases, the canonical form of any portion of an extension block |
| 2761 |
<span class="bcp14">MUST</span> be created as described in <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>. |
| 2762 |
The canonicalization algorithms defined in <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span> |
| 2763 |
adhere to the canonical forms for extension blocks defined in |
| 2764 |
<span>[<a href="#RFC9171" class="xref">RFC9171</a>]</span> but resolve ambiguities related to |
| 2765 |
how values are represented in CBOR.<a href="#section-4.7-2" class="pilcrow">¶</a></p> |
| 2766 |
<div id="bcb_canon_cipher"> |
| 2767 |
<section id="section-4.7.1"> |
| 2768 |
<h4 id="name-calculations-related-to-cip"> |
| 2769 |
<a href="#section-4.7.1" class="section-number selfRef">4.7.1. </a><a href="#name-calculations-related-to-cip" class="section-name selfRef">Calculations Related to Ciphertext</a> |
| 2770 |
</h4> |
| 2771 |
<p id="section-4.7.1-1"> |
| 2772 |
The BCB operates over the block-type-specific data of |
| 2773 |
a block, but the BP always encodes these data within a |
| 2774 |
single, definite-length CBOR byte string. Therefore, the plaintext |
| 2775 |
used during encryption <span class="bcp14">MUST</span> be calculated as the value of the |
| 2776 |
block-type-specific data field of the security target |
| 2777 |
excluding the BP CBOR encoding.<a href="#section-4.7.1-1" class="pilcrow">¶</a></p> |
| 2778 |
<p id="section-4.7.1-2"> |
| 2779 |
<a href="#enc_ex" class="xref">Table 7</a> shows two CBOR-encoded examples and the |
| 2780 |
plaintext that would be extracted from them. The first example |
| 2781 |
is an unsigned integer, while the second is a byte string.<a href="#section-4.7.1-2" class="pilcrow">¶</a></p> |
| 2782 |
<span id="name-cbor-plaintext-extraction-e"></span><div id="enc_ex"> |
| 2783 |
<table class="center" id="table-7"> |
| 2784 |
<caption> |
| 2785 |
<a href="#table-7" class="selfRef">Table 7</a>: |
| 2786 |
<a href="#name-cbor-plaintext-extraction-e" class="selfRef">CBOR Plaintext Extraction Examples</a> |
| 2787 |
</caption> |
| 2788 |
<thead> |
| 2789 |
<tr> |
| 2790 |
<th class="text-center" rowspan="1" colspan="1">CBOR Encoding (Hex)</th> |
| 2791 |
<th class="text-center" rowspan="1" colspan="1">CBOR Part (Hex)</th> |
| 2792 |
<th class="text-center" rowspan="1" colspan="1">Plaintext Part (Hex)</th> |
| 2793 |
</tr> |
| 2794 |
</thead> |
| 2795 |
<tbody> |
| 2796 |
<tr> |
| 2797 |
<td class="text-center" rowspan="1" colspan="1">18ED</td> |
| 2798 |
<td class="text-center" rowspan="1" colspan="1">18</td> |
| 2799 |
<td class="text-center" rowspan="1" colspan="1">ED</td> |
| 2800 |
</tr> |
| 2801 |
<tr> |
| 2802 |
<td class="text-center" rowspan="1" colspan="1">C24CDEADBEEFDEADBEEFDEADBEEF</td> |
| 2803 |
<td class="text-center" rowspan="1" colspan="1">C24C</td> |
| 2804 |
<td class="text-center" rowspan="1" colspan="1">DEADBEEFDEADBEEFDEADBEEF</td> |
| 2805 |
</tr> |
| 2806 |
</tbody> |
| 2807 |
</table> |
| 2808 |
</div> |
| 2809 |
<p id="section-4.7.1-4"> |
| 2810 |
The ciphertext used during decryption <span class="bcp14">MUST</span> be calculated |
| 2811 |
as the single, definite-length CBOR byte string representing the |
| 2812 |
block-type-specific data field excluding the CBOR byte string |
| 2813 |
identifying byte and optional CBOR byte string length field.<a href="#section-4.7.1-4" class="pilcrow">¶</a></p> |
| 2814 |
<p id="section-4.7.1-5"> |
| 2815 |
All other fields of the security target (such as the block type code, |
| 2816 |
block number, block processing control flags, or any CRC information) |
| 2817 |
<span class="bcp14">MUST NOT</span> be considered as part of encryption or decryption.<a href="#section-4.7.1-5" class="pilcrow">¶</a></p> |
| 2818 |
</section> |
| 2819 |
</div> |
| 2820 |
<div id="bcb_canon_aad"> |
| 2821 |
<section id="section-4.7.2"> |
| 2822 |
<h4 id="name-additional-authenticated-da"> |
| 2823 |
<a href="#section-4.7.2" class="section-number selfRef">4.7.2. </a><a href="#name-additional-authenticated-da" class="section-name selfRef">Additional Authenticated Data</a> |
| 2824 |
</h4> |
| 2825 |
<p id="section-4.7.2-1"> |
| 2826 |
The construction of additional authenticated data depends on the |
| 2827 |
AAD scope flags that can be provided as part of customizing the |
| 2828 |
behavior of this security context.<a href="#section-4.7.2-1" class="pilcrow">¶</a></p> |
| 2829 |
<p id="section-4.7.2-2"> |
| 2830 |
The canonical form of the AAD input to the BCB-AES-GCM mechanism is |
| 2831 |
constructed using the following process. While the AAD scope flags |
| 2832 |
might not be included in the BCB representing the security operation, |
| 2833 |
they <span class="bcp14">MUST</span> be included in the AAD value itself. This process <span class="bcp14">MUST</span> be |
| 2834 |
followed when generating AAD for either encryption or decryption.<a href="#section-4.7.2-2" class="pilcrow">¶</a></p> |
| 2835 |
<ol start="1" type="1" class="normal type-1" id="section-4.7.2-3"> |
| 2836 |
<li id="section-4.7.2-3.1"> |
| 2837 |
The canonical form of the AAD starts as the CBOR encoding |
| 2838 |
of the AAD scope flags in which all unset flags, reserved bits, |
| 2839 |
and unassigned bits have been set to 0. For example, if the |
| 2840 |
primary block flag, target header flag, and security header flag are |
| 2841 |
each set, then the initial value of the canonical form of the |
| 2842 |
AAD will be 0x07.<a href="#section-4.7.2-3.1" class="pilcrow">¶</a> |
| 2843 |
</li> |
| 2844 |
<li id="section-4.7.2-3.2"> |
| 2845 |
If the primary block flag of the AAD scope flags is set to |
| 2846 |
1, then a canonical form of the bundle's primary |
| 2847 |
block <span class="bcp14">MUST</span> be calculated and the result appended to the AAD.<a href="#section-4.7.2-3.2" class="pilcrow">¶</a> |
| 2848 |
</li> |
| 2849 |
<li id="section-4.7.2-3.3"> |
| 2850 |
If the target header flag of the AAD scope flags is set to |
| 2851 |
1, then the canonical form of the block type code, |
| 2852 |
block number, and block processing control flags associated with the |
| 2853 |
security target <span class="bcp14">MUST</span> be calculated and, in that order, appended |
| 2854 |
to the AAD.<a href="#section-4.7.2-3.3" class="pilcrow">¶</a> |
| 2855 |
</li> |
| 2856 |
<li id="section-4.7.2-3.4"> |
| 2857 |
If the security header flag of the AAD scope flags is set to 1, |
| 2858 |
then the canonical form of the block type code, |
| 2859 |
block number, and block processing control flags associated with |
| 2860 |
the BIB <span class="bcp14">MUST</span> be calculated and, in that order, appended to the AAD.<a href="#section-4.7.2-3.4" class="pilcrow">¶</a> |
| 2861 |
</li> |
| 2862 |
</ol> |
| 2863 |
</section> |
| 2864 |
</div> |
| 2865 |
</section> |
| 2866 |
<section id="section-4.8"> |
| 2867 |
<h3 id="name-processing-2"> |
| 2868 |
<a href="#section-4.8" class="section-number selfRef">4.8. </a><a href="#name-processing-2" class="section-name selfRef">Processing</a> |
| 2869 |
</h3> |
| 2870 |
<section id="section-4.8.1"> |
| 2871 |
<h4 id="name-encryption"> |
| 2872 |
<a href="#section-4.8.1" class="section-number selfRef">4.8.1. </a><a href="#name-encryption" class="section-name selfRef">Encryption</a> |
| 2873 |
</h4> |
| 2874 |
<p id="section-4.8.1-1"> |
| 2875 |
During encryption, four data elements are prepared for input to the |
| 2876 |
AES-GCM cipher: the encryption key, the IV, |
| 2877 |
the security target plaintext to be encrypted, and any |
| 2878 |
additional authenticated data. These data items <span class="bcp14">MUST</span> be generated |
| 2879 |
as follows.<a href="#section-4.8.1-1" class="pilcrow">¶</a></p> |
| 2880 |
<p id="section-4.8.1-2"> |
| 2881 |
Prior to encryption, if a CRC value is present for the target block, |
| 2882 |
then that CRC value <span class="bcp14">MUST</span> be removed. This requires removing the CRC |
| 2883 |
field from the target block and setting the CRC type field of the |
| 2884 |
target block to "no CRC is present."<a href="#section-4.8.1-2" class="pilcrow">¶</a></p> |
| 2885 |
<ul class="normal"> |
| 2886 |
<li class="normal" id="section-4.8.1-3.1"> |
| 2887 |
The encryption key <span class="bcp14">MUST</span> have the appropriate |
| 2888 |
length as required by local security policy. The key might be |
| 2889 |
generated specifically for this encryption, given as part of |
| 2890 |
local security policy, or obtained through some other key |
| 2891 |
management mechanism as discussed in <a href="#bcb_key_mgmt" class="xref">Section 4.5</a>.<a href="#section-4.8.1-3.1" class="pilcrow">¶</a> |
| 2892 |
</li> |
| 2893 |
<li class="normal" id="section-4.8.1-3.2"> |
| 2894 |
The IV selected <span class="bcp14">MUST</span> be of the appropriate |
| 2895 |
length. Because replaying an IV in counter mode voids the |
| 2896 |
confidentiality of all messages encrypted with said IV, this |
| 2897 |
context also requires a unique IV for every encryption performed |
| 2898 |
with the same key. This means the same key and IV combination <span class="bcp14">MUST NOT</span> be used more than once.<a href="#section-4.8.1-3.2" class="pilcrow">¶</a> |
| 2899 |
</li> |
| 2900 |
<li class="normal" id="section-4.8.1-3.3"> |
| 2901 |
The security target plaintext for encryption <span class="bcp14">MUST</span> be generated as |
| 2902 |
discussed in <a href="#bcb_canon_cipher" class="xref">Section 4.7.1</a>.<a href="#section-4.8.1-3.3" class="pilcrow">¶</a> |
| 2903 |
</li> |
| 2904 |
<li class="normal" id="section-4.8.1-3.4"> |
| 2905 |
Additional authenticated data <span class="bcp14">MUST</span> be generated as |
| 2906 |
discussed in <a href="#bcb_canon_aad" class="xref">Section 4.7.2</a>, with the value of |
| 2907 |
AAD scope flags being taken from local security policy.<a href="#section-4.8.1-3.4" class="pilcrow">¶</a> |
| 2908 |
</li> |
| 2909 |
</ul> |
| 2910 |
<p id="section-4.8.1-4"> |
| 2911 |
Upon successful encryption, the following actions <span class="bcp14">MUST</span> occur.<a href="#section-4.8.1-4" class="pilcrow">¶</a></p> |
| 2912 |
<ul class="normal"> |
| 2913 |
<li class="normal" id="section-4.8.1-5.1"> |
| 2914 |
The ciphertext produced by AES-GCM <span class="bcp14">MUST</span> replace the bytes used |
| 2915 |
to define the plaintext in the security target block's |
| 2916 |
block-type-specific data field. The block length of the security |
| 2917 |
target <span class="bcp14">MUST</span> be updated if the generated ciphertext is larger |
| 2918 |
than the plaintext (which can occur when the authentication |
| 2919 |
tag is included in the ciphertext calculation, as discussed |
| 2920 |
in <a href="#bcb_results" class="xref">Section 4.4</a>).<a href="#section-4.8.1-5.1" class="pilcrow">¶</a> |
| 2921 |
</li> |
| 2922 |
<li class="normal" id="section-4.8.1-5.2"> |
| 2923 |
The authentication tag calculated by the AES-GCM cipher <span class="bcp14">MAY</span> be |
| 2924 |
added as a security result for the security target in the BCB |
| 2925 |
holding results for this security operation, in which case it |
| 2926 |
<span class="bcp14">MUST</span> be processed as described in <a href="#bcb_results" class="xref">Section 4.4</a>.<a href="#section-4.8.1-5.2" class="pilcrow">¶</a> |
| 2927 |
</li> |
| 2928 |
<li class="normal" id="section-4.8.1-5.3"> |
| 2929 |
The authentication tag <span class="bcp14">MUST</span> be included either as a security |
| 2930 |
result in the BCB representing the security operation or |
| 2931 |
(with the ciphertext) in the security target block-type-specific |
| 2932 |
data field.<a href="#section-4.8.1-5.3" class="pilcrow">¶</a> |
| 2933 |
</li> |
| 2934 |
</ul> |
| 2935 |
<p id="section-4.8.1-6"> |
| 2936 |
Finally, the BCB containing information about this security operation |
| 2937 |
<span class="bcp14">MUST</span> be updated as follows. These operations can occur in any order.<a href="#section-4.8.1-6" class="pilcrow">¶</a></p> |
| 2938 |
<ul class="normal"> |
| 2939 |
<li class="normal" id="section-4.8.1-7.1"> |
| 2940 |
The security context identifier for the BCB <span class="bcp14">MUST</span> be set to the context |
| 2941 |
identifier for BCB-AES-GCM.<a href="#section-4.8.1-7.1" class="pilcrow">¶</a> |
| 2942 |
</li> |
| 2943 |
<li class="normal" id="section-4.8.1-7.2"> |
| 2944 |
The IV input to the cipher <span class="bcp14">MUST</span> be added as the |
| 2945 |
IV security context parameter for the BCB.<a href="#section-4.8.1-7.2" class="pilcrow">¶</a> |
| 2946 |
</li> |
| 2947 |
<li class="normal" id="section-4.8.1-7.3"> |
| 2948 |
Any local flags used to generate AAD for this cipher <span class="bcp14">MUST</span> be |
| 2949 |
placed in the AAD scope flags security context parameter for the BCB |
| 2950 |
unless these flags are expected to be correctly configured at |
| 2951 |
security verifiers and security acceptors in the network.<a href="#section-4.8.1-7.3" class="pilcrow">¶</a> |
| 2952 |
</li> |
| 2953 |
<li class="normal" id="section-4.8.1-7.4"> |
| 2954 |
The encryption key <span class="bcp14">MAY</span> be included as a security |
| 2955 |
context parameter, in which case it <span class="bcp14">MUST</span> be |
| 2956 |
wrapped using the AES key wrap function as defined in <span>[<a href="#RFC3394" class="xref">RFC3394</a>]</span> and the results of the |
| 2957 |
wrapping added as the wrapped key security context parameter for |
| 2958 |
the BCB.<a href="#section-4.8.1-7.4" class="pilcrow">¶</a> |
| 2959 |
</li> |
| 2960 |
<li class="normal" id="section-4.8.1-7.5"> |
| 2961 |
The AES variant used by this security context <span class="bcp14">SHOULD</span> be added as |
| 2962 |
the AES variant security context parameter for the BCB if it differs from |
| 2963 |
the default key length. Otherwise, this parameter <span class="bcp14">MAY</span> be |
| 2964 |
omitted if doing so provides a useful reduction in message sizes.<a href="#section-4.8.1-7.5" class="pilcrow">¶</a> |
| 2965 |
</li> |
| 2966 |
</ul> |
| 2967 |
<p id="section-4.8.1-8"> |
| 2968 |
Problems encountered in the encryption <span class="bcp14">MUST</span> be processed in accordance |
| 2969 |
with local security policy. This <span class="bcp14">MAY</span> include restoring a CRC value |
| 2970 |
removed from the target block prior to encryption, if the target block |
| 2971 |
is allowed to be transmitted after an encryption error.<a href="#section-4.8.1-8" class="pilcrow">¶</a></p> |
| 2972 |
</section> |
| 2973 |
<section id="section-4.8.2"> |
| 2974 |
<h4 id="name-decryption"> |
| 2975 |
<a href="#section-4.8.2" class="section-number selfRef">4.8.2. </a><a href="#name-decryption" class="section-name selfRef">Decryption</a> |
| 2976 |
</h4> |
| 2977 |
<p id="section-4.8.2-1"> |
| 2978 |
During decryption, five data elements are prepared for input to the |
| 2979 |
AES-GCM cipher: the decryption key, the IV, |
| 2980 |
the security target ciphertext to be decrypted, any additional |
| 2981 |
authenticated data, and the authentication tag generated from the |
| 2982 |
original encryption. These data items <span class="bcp14">MUST</span> be generated as follows.<a href="#section-4.8.2-1" class="pilcrow">¶</a></p> |
| 2983 |
<ul class="normal"> |
| 2984 |
<li class="normal" id="section-4.8.2-2.1"> |
| 2985 |
The decryption key <span class="bcp14">MUST</span> be derived using the wrapped key |
| 2986 |
security context parameter if such a parameter is included in the |
| 2987 |
security context parameters of the BCB. Otherwise, this key |
| 2988 |
<span class="bcp14">MUST</span> be derived in accordance with local security policy at the |
| 2989 |
decrypting node as discussed in <a href="#bcb_key_mgmt" class="xref">Section 4.5</a>.<a href="#section-4.8.2-2.1" class="pilcrow">¶</a> |
| 2990 |
</li> |
| 2991 |
<li class="normal" id="section-4.8.2-2.2"> |
| 2992 |
The IV <span class="bcp14">MUST</span> be set to the value of the |
| 2993 |
IV security context parameter included in the BCB. If the IV parameter |
| 2994 |
is not included as a security context parameter, an IV <span class="bcp14">MAY</span> be derived |
| 2995 |
as a function of local security policy and other BCB contents, or |
| 2996 |
a lack of an IV security context parameter in the BCB <span class="bcp14">MAY</span> be treated |
| 2997 |
as an error by the decrypting node.<a href="#section-4.8.2-2.2" class="pilcrow">¶</a> |
| 2998 |
</li> |
| 2999 |
<li class="normal" id="section-4.8.2-2.3"> |
| 3000 |
The security target ciphertext for decryption <span class="bcp14">MUST</span> be generated as |
| 3001 |
discussed in <a href="#bcb_canon_cipher" class="xref">Section 4.7.1</a>.<a href="#section-4.8.2-2.3" class="pilcrow">¶</a> |
| 3002 |
</li> |
| 3003 |
<li class="normal" id="section-4.8.2-2.4"> |
| 3004 |
Additional authenticated data <span class="bcp14">MUST</span> be generated as |
| 3005 |
discussed in <a href="#bcb_canon_aad" class="xref">Section 4.7.2</a> with the value of |
| 3006 |
AAD scope flags being taken from the AAD scope flags |
| 3007 |
security context parameter. If the AAD scope flags parameter is |
| 3008 |
not included in the security context parameters, then these flags |
| 3009 |
<span class="bcp14">MAY</span> be derived from local security policy in cases where the |
| 3010 |
set of such flags is determinable in the network.<a href="#section-4.8.2-2.4" class="pilcrow">¶</a> |
| 3011 |
</li> |
| 3012 |
<li class="normal" id="section-4.8.2-2.5"> |
| 3013 |
The authentication tag <span class="bcp14">MUST</span> be present either as a security |
| 3014 |
result in the BCB representing the security operation or |
| 3015 |
(with the ciphertext) in the security target block-type-specific |
| 3016 |
data field.<a href="#section-4.8.2-2.5" class="pilcrow">¶</a> |
| 3017 |
</li> |
| 3018 |
</ul> |
| 3019 |
<p id="section-4.8.2-3"> |
| 3020 |
Upon successful decryption, the following action <span class="bcp14">MUST</span> occur.<a href="#section-4.8.2-3" class="pilcrow">¶</a></p> |
| 3021 |
<ul class="normal"> |
| 3022 |
<li class="normal" id="section-4.8.2-4.1"> |
| 3023 |
The plaintext produced by AES-GCM <span class="bcp14">MUST</span> replace |
| 3024 |
the bytes used to define the ciphertext in the security target |
| 3025 |
block's block-type-specific data field. Any changes to the |
| 3026 |
security target block length field <span class="bcp14">MUST</span> be |
| 3027 |
corrected in cases where the plaintext has a different length |
| 3028 |
than the replaced ciphertext.<a href="#section-4.8.2-4.1" class="pilcrow">¶</a> |
| 3029 |
</li> |
| 3030 |
</ul> |
| 3031 |
<p id="section-4.8.2-5"> |
| 3032 |
If the security acceptor is not the bundle destination and if no other |
| 3033 |
integrity or confidentiality service is being applied to the target block, |
| 3034 |
then a CRC <span class="bcp14">MUST</span> be included for the target block. The CRC type, as determined |
| 3035 |
by policy, is set in the target block's CRC type field and the |
| 3036 |
corresponding CRC value is added as the CRC field for that block.<a href="#section-4.8.2-5" class="pilcrow">¶</a></p> |
| 3037 |
<p id="section-4.8.2-6"> |
| 3038 |
If the ciphertext fails to authenticate, if any needed parameters |
| 3039 |
are missing, or if there are other problems in the decryption, then |
| 3040 |
the decryption <span class="bcp14">MUST</span> be treated as failed and processed in accordance |
| 3041 |
with local security policy.<a href="#section-4.8.2-6" class="pilcrow">¶</a></p> |
| 3042 |
</section> |
| 3043 |
</section> |
| 3044 |
</section> |
| 3045 |
</div> |
| 3046 |
<div id="IANA"> |
| 3047 |
<section id="section-5"> |
| 3048 |
<h2 id="name-iana-considerations"> |
| 3049 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 3050 |
</h2> |
| 3051 |
<div id="sc_ids"> |
| 3052 |
<section id="section-5.1"> |
| 3053 |
<h3 id="name-security-context-identifier"> |
| 3054 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-security-context-identifier" class="section-name selfRef">Security Context Identifiers</a> |
| 3055 |
</h3> |
| 3056 |
<p id="section-5.1-1"> |
| 3057 |
This specification allocates two security context identifiers from the |
| 3058 |
"BPSec Security Context Identifiers" registry defined in |
| 3059 |
<span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 3060 |
<span id="name-additional-entries-for-the-"></span><div id="iana_table"> |
| 3061 |
<table class="center" id="table-8"> |
| 3062 |
<caption> |
| 3063 |
<a href="#table-8" class="selfRef">Table 8</a>: |
| 3064 |
<a href="#name-additional-entries-for-the-" class="selfRef">Additional Entries for the BPSec Security Context Identifiers Registry</a> |
| 3065 |
</caption> |
| 3066 |
<thead> |
| 3067 |
<tr> |
| 3068 |
<th class="text-center" rowspan="1" colspan="1">Value</th> |
| 3069 |
<th class="text-left" rowspan="1" colspan="1">Description</th> |
| 3070 |
<th class="text-left" rowspan="1" colspan="1">Reference</th> |
| 3071 |
</tr> |
| 3072 |
</thead> |
| 3073 |
<tbody> |
| 3074 |
<tr> |
| 3075 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 3076 |
<td class="text-left" rowspan="1" colspan="1">BIB-HMAC-SHA2</td> |
| 3077 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3078 |
</tr> |
| 3079 |
<tr> |
| 3080 |
<td class="text-center" rowspan="1" colspan="1">2</td> |
| 3081 |
<td class="text-left" rowspan="1" colspan="1">BCB-AES-GCM</td> |
| 3082 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3083 |
</tr> |
| 3084 |
</tbody> |
| 3085 |
</table> |
| 3086 |
</div> |
| 3087 |
</section> |
| 3088 |
</div> |
| 3089 |
<section id="section-5.2"> |
| 3090 |
<h3 id="name-integrity-scope-flags-2"> |
| 3091 |
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-integrity-scope-flags-2" class="section-name selfRef">Integrity Scope Flags</a> |
| 3092 |
</h3> |
| 3093 |
<p id="section-5.2-1"> |
| 3094 |
The BIB-HMAC-SHA2 security context has an Integrity Scope Flags field for |
| 3095 |
which IANA has created and now maintains a new registry named |
| 3096 |
"BPSec BIB-HMAC-SHA2 Integrity Scope Flags" on the "Bundle Protocol" registry page. |
| 3097 |
<a href="#bib_flags" class="xref">Table 9</a> shows the initial values for this registry.<a href="#section-5.2-1" class="pilcrow">¶</a></p> |
| 3098 |
<p id="section-5.2-2"> |
| 3099 |
The registration policy for this registry is Specification Required <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-5.2-2" class="pilcrow">¶</a></p> |
| 3100 |
<p id="section-5.2-3"> |
| 3101 |
The value range is unsigned 16-bit integer.<a href="#section-5.2-3" class="pilcrow">¶</a></p> |
| 3102 |
<span id="name-bpsec-bib-hmac-sha2-integri"></span><div id="bib_flags"> |
| 3103 |
<table class="center" id="table-9"> |
| 3104 |
<caption> |
| 3105 |
<a href="#table-9" class="selfRef">Table 9</a>: |
| 3106 |
<a href="#name-bpsec-bib-hmac-sha2-integri" class="selfRef">BPSec BIB-HMAC-SHA2 Integrity Scope Flags Registry</a> |
| 3107 |
</caption> |
| 3108 |
<thead> |
| 3109 |
<tr> |
| 3110 |
<th class="text-center" rowspan="1" colspan="1">Bit Position (right to left)</th> |
| 3111 |
<th class="text-left" rowspan="1" colspan="1">Description</th> |
| 3112 |
<th class="text-left" rowspan="1" colspan="1">Reference</th> |
| 3113 |
</tr> |
| 3114 |
</thead> |
| 3115 |
<tbody> |
| 3116 |
<tr> |
| 3117 |
<td class="text-center" rowspan="1" colspan="1">0</td> |
| 3118 |
<td class="text-left" rowspan="1" colspan="1">Include primary block flag</td> |
| 3119 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3120 |
</tr> |
| 3121 |
<tr> |
| 3122 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 3123 |
<td class="text-left" rowspan="1" colspan="1">Include target header flag</td> |
| 3124 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3125 |
</tr> |
| 3126 |
<tr> |
| 3127 |
<td class="text-center" rowspan="1" colspan="1">2</td> |
| 3128 |
<td class="text-left" rowspan="1" colspan="1">Include security header flag</td> |
| 3129 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3130 |
</tr> |
| 3131 |
<tr> |
| 3132 |
<td class="text-center" rowspan="1" colspan="1">3-7</td> |
| 3133 |
<td class="text-left" rowspan="1" colspan="1">Reserved</td> |
| 3134 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3135 |
</tr> |
| 3136 |
<tr> |
| 3137 |
<td class="text-center" rowspan="1" colspan="1">8-15</td> |
| 3138 |
<td class="text-left" rowspan="1" colspan="1">Unassigned</td> |
| 3139 |
<td class="text-left" rowspan="1" colspan="1"></td> |
| 3140 |
</tr> |
| 3141 |
</tbody> |
| 3142 |
</table> |
| 3143 |
</div> |
| 3144 |
</section> |
| 3145 |
<section id="section-5.3"> |
| 3146 |
<h3 id="name-aad-scope-flags-2"> |
| 3147 |
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-aad-scope-flags-2" class="section-name selfRef">AAD Scope Flags</a> |
| 3148 |
</h3> |
| 3149 |
<p id="section-5.3-1"> |
| 3150 |
The BCB-AES-GCM security context has an AAD Scope Flags field for |
| 3151 |
which IANA has created and now maintains a new registry named |
| 3152 |
"BPSec BCB-AES-GCM AAD Scope Flags" on the "Bundle Protocol" registry page. |
| 3153 |
<a href="#bcb_flags" class="xref">Table 10</a> shows the initial values for this registry.<a href="#section-5.3-1" class="pilcrow">¶</a></p> |
| 3154 |
<p id="section-5.3-2"> |
| 3155 |
The registration policy for this registry is Specification Required.<a href="#section-5.3-2" class="pilcrow">¶</a></p> |
| 3156 |
<p id="section-5.3-3"> |
| 3157 |
The value range is unsigned 16-bit integer.<a href="#section-5.3-3" class="pilcrow">¶</a></p> |
| 3158 |
<span id="name-bpsec-bcb-aes-gcm-aad-scope"></span><div id="bcb_flags"> |
| 3159 |
<table class="center" id="table-10"> |
| 3160 |
<caption> |
| 3161 |
<a href="#table-10" class="selfRef">Table 10</a>: |
| 3162 |
<a href="#name-bpsec-bcb-aes-gcm-aad-scope" class="selfRef">BPSec BCB-AES-GCM AAD Scope Flags Registry</a> |
| 3163 |
</caption> |
| 3164 |
<thead> |
| 3165 |
<tr> |
| 3166 |
<th class="text-center" rowspan="1" colspan="1">Bit Position (right to left)</th> |
| 3167 |
<th class="text-left" rowspan="1" colspan="1">Description</th> |
| 3168 |
<th class="text-left" rowspan="1" colspan="1">Reference</th> |
| 3169 |
</tr> |
| 3170 |
</thead> |
| 3171 |
<tbody> |
| 3172 |
<tr> |
| 3173 |
<td class="text-center" rowspan="1" colspan="1">0</td> |
| 3174 |
<td class="text-left" rowspan="1" colspan="1">Include primary block flag</td> |
| 3175 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3176 |
</tr> |
| 3177 |
<tr> |
| 3178 |
<td class="text-center" rowspan="1" colspan="1">1</td> |
| 3179 |
<td class="text-left" rowspan="1" colspan="1">Include target header flag</td> |
| 3180 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3181 |
</tr> |
| 3182 |
<tr> |
| 3183 |
<td class="text-center" rowspan="1" colspan="1">2</td> |
| 3184 |
<td class="text-left" rowspan="1" colspan="1">Include security header flag</td> |
| 3185 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3186 |
</tr> |
| 3187 |
<tr> |
| 3188 |
<td class="text-center" rowspan="1" colspan="1">3-7</td> |
| 3189 |
<td class="text-left" rowspan="1" colspan="1">Reserved</td> |
| 3190 |
<td class="text-left" rowspan="1" colspan="1">RFC 9173</td> |
| 3191 |
</tr> |
| 3192 |
<tr> |
| 3193 |
<td class="text-center" rowspan="1" colspan="1">8-15</td> |
| 3194 |
<td class="text-left" rowspan="1" colspan="1">Unassigned</td> |
| 3195 |
<td class="text-left" rowspan="1" colspan="1"></td> |
| 3196 |
</tr> |
| 3197 |
</tbody> |
| 3198 |
</table> |
| 3199 |
</div> |
| 3200 |
</section> |
| 3201 |
<section id="section-5.4"> |
| 3202 |
<h3 id="name-guidance-for-designated-exp"> |
| 3203 |
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-guidance-for-designated-exp" class="section-name selfRef">Guidance for Designated Experts</a> |
| 3204 |
</h3> |
| 3205 |
<p id="section-5.4-1"> |
| 3206 |
New assignments within the "BPSec BIB-HMAC-SHA2 |
| 3207 |
Integrity Scope Flags" and |
| 3208 |
"BPSec BCB-AES-GCM AAD Scope Flags" registries require |
| 3209 |
review by a Designated Expert (DE). This section |
| 3210 |
provides guidance to the DE when performing their |
| 3211 |
reviews. Specifically, a DE is expected to perform |
| 3212 |
the following activities.<a href="#section-5.4-1" class="pilcrow">¶</a></p> |
| 3213 |
<ul class="normal"> |
| 3214 |
<li class="normal" id="section-5.4-2.1"> |
| 3215 |
Ascertain the existence of suitable documentation |
| 3216 |
(a specification) as described in <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span> |
| 3217 |
and verify that the document is permanently and |
| 3218 |
publicly available.<a href="#section-5.4-2.1" class="pilcrow">¶</a> |
| 3219 |
</li> |
| 3220 |
<li class="normal" id="section-5.4-2.2"> |
| 3221 |
Ensure that any changes to the "BPSec BIB-HMAC-SHA2 Integrity Scope Flags" registry |
| 3222 |
clearly state how new assignments interact with existing |
| 3223 |
flags and how the inclusion of new assignments affects |
| 3224 |
the construction of the IPPT value.<a href="#section-5.4-2.2" class="pilcrow">¶</a> |
| 3225 |
</li> |
| 3226 |
<li class="normal" id="section-5.4-2.3"> |
| 3227 |
Ensure that any changes to the "BPSec BCB-AES-GCM AAD Scope Flags" registry clearly |
| 3228 |
state how new assignments interact with existing |
| 3229 |
flags and how the inclusion of new assignments affects |
| 3230 |
the construction of the AAD input to the BCB-AES-GCM mechanism.<a href="#section-5.4-2.3" class="pilcrow">¶</a> |
| 3231 |
</li> |
| 3232 |
<li class="normal" id="section-5.4-2.4"> |
| 3233 |
Ensure that any processing changes proposed with new assignments |
| 3234 |
do not alter any required behavior in this specification.<a href="#section-5.4-2.4" class="pilcrow">¶</a> |
| 3235 |
</li> |
| 3236 |
</ul> |
| 3237 |
</section> |
| 3238 |
</section> |
| 3239 |
</div> |
| 3240 |
<div id="SecCons"> |
| 3241 |
<section id="section-6"> |
| 3242 |
<h2 id="name-security-considerations"> |
| 3243 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 3244 |
</h2> |
| 3245 |
<p id="section-6-1"> |
| 3246 |
Security considerations specific to a single security context are |
| 3247 |
provided in the description of that context (see Sections <a href="#first-context" class="xref">3</a> and <a href="#second-context" class="xref">4</a>). This section discusses |
| 3248 |
security considerations that should be evaluated by implementers of any |
| 3249 |
security context described in this document. Considerations can also be |
| 3250 |
found in documents listed as normative references and should also be |
| 3251 |
reviewed by security context implementors.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 3252 |
<section id="section-6.1"> |
| 3253 |
<h3 id="name-key-management"> |
| 3254 |
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-key-management" class="section-name selfRef">Key Management</a> |
| 3255 |
</h3> |
| 3256 |
<p id="section-6.1-1"> |
| 3257 |
The delayed and disrupted nature of Delay-Tolerant |
| 3258 |
Networking (DTN) complicates the process of key management |
| 3259 |
because there might not be reliable, timely, round-trip exchange between security |
| 3260 |
sources, security verifiers, and security acceptors in the network. This is true when |
| 3261 |
there is a substantial signal propagation delay between nodes, when nodes are in a highly |
| 3262 |
challenged communications environment, and when nodes do not support bidirectional |
| 3263 |
communication.<a href="#section-6.1-1" class="pilcrow">¶</a></p> |
| 3264 |
<p id="section-6.1-2"> |
| 3265 |
In these environments, key establishment protocols that rely on round-trip information |
| 3266 |
exchange might not converge on a shared secret in a timely manner (or at all). Also, |
| 3267 |
key revocation or key verification mechanisms that rely on access to a centralized |
| 3268 |
authority (such as a certificate authority) might similarly fail in the stressing |
| 3269 |
conditions of DTN.<a href="#section-6.1-2" class="pilcrow">¶</a></p> |
| 3270 |
<p id="section-6.1-3"> |
| 3271 |
For these reasons, the default security contexts described in this document rely |
| 3272 |
on symmetric-key cryptographic mechanisms because asymmetric-key infrastructure (such |
| 3273 |
as a public key infrastructure) might be impractical in this environment.<a href="#section-6.1-3" class="pilcrow">¶</a></p> |
| 3274 |
<p id="section-6.1-4"> |
| 3275 |
BPSec assumes that "key management is handled as a separate part of network management" |
| 3276 |
<span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>. This assumption is also made |
| 3277 |
by the security contexts defined in this document, which do not define new protocols for |
| 3278 |
key derivation, exchange of KEKs, revocation of existing keys, |
| 3279 |
or the security configuration or policy used to select certain keys for certain |
| 3280 |
security operations.<a href="#section-6.1-4" class="pilcrow">¶</a></p> |
| 3281 |
<p id="section-6.1-5"> |
| 3282 |
Nodes using these security contexts need to perform the following kinds of |
| 3283 |
activities, independent of the construction, transmission, and processing of |
| 3284 |
BPSec security blocks.<a href="#section-6.1-5" class="pilcrow">¶</a></p> |
| 3285 |
<ul class="normal"> |
| 3286 |
<li class="normal" id="section-6.1-6.1"> |
| 3287 |
Establish shared KEKs with other nodes in the network using |
| 3288 |
an out-of-band mechanism. This might include pre-sharing of KEKs |
| 3289 |
or the use of older key establishment mechanisms prior to the |
| 3290 |
exchange of BPSec security blocks.<a href="#section-6.1-6.1" class="pilcrow">¶</a> |
| 3291 |
</li> |
| 3292 |
<li class="normal" id="section-6.1-6.2"> |
| 3293 |
Determine when a key is considered exhausted and no longer to be used in |
| 3294 |
the generation, verification, or acceptance of a security block.<a href="#section-6.1-6.2" class="pilcrow">¶</a> |
| 3295 |
</li> |
| 3296 |
<li class="normal" id="section-6.1-6.3"> |
| 3297 |
Determine when a key is considered invalid and no longer to be used in the |
| 3298 |
generation, verification, or acceptance of a security block. Such revocations |
| 3299 |
can be based on a variety of mechanisms, including local security policy, |
| 3300 |
time relative to the generation or use of the key, or other mechanisms |
| 3301 |
specified through network management.<a href="#section-6.1-6.3" class="pilcrow">¶</a> |
| 3302 |
</li> |
| 3303 |
<li class="normal" id="section-6.1-6.4"> |
| 3304 |
Determine, through an out-of-band mechanism such as local security policy, |
| 3305 |
what keys are to be used for what security blocks. This includes the selection |
| 3306 |
of which key should be used in the evaluation of a security block received by |
| 3307 |
a security verifier or a security acceptor.<a href="#section-6.1-6.4" class="pilcrow">¶</a> |
| 3308 |
</li> |
| 3309 |
</ul> |
| 3310 |
<p id="section-6.1-7"> |
| 3311 |
The failure to provide effective key management techniques appropriate |
| 3312 |
for the operational networking environment can result in the compromise of |
| 3313 |
those unmanaged keys and the loss of security services in the network.<a href="#section-6.1-7" class="pilcrow">¶</a></p> |
| 3314 |
</section> |
| 3315 |
<section id="section-6.2"> |
| 3316 |
<h3 id="name-key-handling"> |
| 3317 |
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-key-handling" class="section-name selfRef">Key Handling</a> |
| 3318 |
</h3> |
| 3319 |
<p id="section-6.2-1"> |
| 3320 |
Once generated, keys should be handled as follows.<a href="#section-6.2-1" class="pilcrow">¶</a></p> |
| 3321 |
<ul class="normal"> |
| 3322 |
<li class="normal" id="section-6.2-2.1"> |
| 3323 |
It is strongly <span class="bcp14">RECOMMENDED</span> that implementations protect keys both |
| 3324 |
when they are stored and when they are transmitted.<a href="#section-6.2-2.1" class="pilcrow">¶</a> |
| 3325 |
</li> |
| 3326 |
<li class="normal" id="section-6.2-2.2"> |
| 3327 |
In the event that a key is compromised, any security operations using |
| 3328 |
a security context associated with that key <span class="bcp14">SHOULD</span> also be |
| 3329 |
considered compromised. This means that the BIB-HMAC-SHA2 security context |
| 3330 |
<span class="bcp14">SHOULD NOT</span> be treated as providing integrity when used with a compromised key, and |
| 3331 |
BCB-AES-GCM <span class="bcp14">SHOULD NOT</span> be treated as providing confidentiality when used with a compromised key.<a href="#section-6.2-2.2" class="pilcrow">¶</a> |
| 3332 |
</li> |
| 3333 |
<li class="normal" id="section-6.2-2.3"> |
| 3334 |
The same key, whether a KEK or a wrapped key, <span class="bcp14">MUST NOT</span> |
| 3335 |
be used for different algorithms as doing so might leak information |
| 3336 |
about the key.<a href="#section-6.2-2.3" class="pilcrow">¶</a> |
| 3337 |
</li> |
| 3338 |
<li class="normal" id="section-6.2-2.4"> |
| 3339 |
A KEK <span class="bcp14">MUST NOT</span> be used to encrypt keys for different security |
| 3340 |
contexts. Any KEK used by a security context defined in this document <span class="bcp14">MUST</span> |
| 3341 |
only be used to wrap keys associated with security operations using |
| 3342 |
that security context. This means that a compliant security source |
| 3343 |
would not use the same KEK to wrap keys for both the BIB-HMAC-SHA2 and |
| 3344 |
BCB-AES-GCM security contexts. Similarly, any compliant security verifier |
| 3345 |
or security acceptor would not use the same KEK to unwrap keys |
| 3346 |
for different security contexts.<a href="#section-6.2-2.4" class="pilcrow">¶</a> |
| 3347 |
</li> |
| 3348 |
</ul> |
| 3349 |
</section> |
| 3350 |
<section id="section-6.3"> |
| 3351 |
<h3 id="name-aes-gcm"> |
| 3352 |
<a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-aes-gcm" class="section-name selfRef">AES GCM</a> |
| 3353 |
</h3> |
| 3354 |
<p id="section-6.3-1"> |
| 3355 |
There are a significant number of considerations related to the use of the |
| 3356 |
GCM mode of AES to provide a confidentiality service. These considerations |
| 3357 |
are provided in <a href="#GcmCons" class="xref">Section 4.6</a> as part of the documentation |
| 3358 |
of the BCB-AES-GCM security context.<a href="#section-6.3-1" class="pilcrow">¶</a></p> |
| 3359 |
<p id="section-6.3-2"> |
| 3360 |
The length of the ciphertext produced by the |
| 3361 |
GCM mode of AES will be equal to the length of the plaintext input |
| 3362 |
to the cipher suite. The authentication tag also produced by this |
| 3363 |
cipher suite is separate from the ciphertext. However, it should be |
| 3364 |
noted that implementations of the AES-GCM cipher suite might not separate |
| 3365 |
the concept of ciphertext and authentication tag in their Application |
| 3366 |
Programming Interface (API).<a href="#section-6.3-2" class="pilcrow">¶</a></p> |
| 3367 |
<p id="section-6.3-3"> |
| 3368 |
Implementations of the BCB-AES-GCM security context can either keep the length |
| 3369 |
of the target block unchanged by holding the authentication tag in a BCB |
| 3370 |
security result or alter the length of the target block by including the |
| 3371 |
authentication tag with the ciphertext replacing the block-type-specific data |
| 3372 |
field of the target block. Implementations <span class="bcp14">MAY</span> use the authentication tag |
| 3373 |
security result in cases where keeping target block length unchanged is an |
| 3374 |
important processing concern. In all cases, the ciphertext and authentication |
| 3375 |
tag <span class="bcp14">MUST</span> be processed in accordance with the API of the AES-GCM cipher suites |
| 3376 |
at the security source and security acceptor.<a href="#section-6.3-3" class="pilcrow">¶</a></p> |
| 3377 |
</section> |
| 3378 |
<section id="section-6.4"> |
| 3379 |
<h3 id="name-aes-key-wrap"> |
| 3380 |
<a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-aes-key-wrap" class="section-name selfRef">AES Key Wrap</a> |
| 3381 |
</h3> |
| 3382 |
<p id="section-6.4-1"> |
| 3383 |
The AES-KW algorithm used by the security contexts in this document |
| 3384 |
does not use a per-invocation initialization vector and does not require any key padding. Key padding is |
| 3385 |
not needed because wrapped keys used by these security contexts will always be multiples of 8 |
| 3386 |
bytes. The length of the wrapped key can be determined by inspecting the security |
| 3387 |
context parameters. Therefore, a key can be unwrapped using only the information present |
| 3388 |
in the security block and the KEK provided by local security policy at the security verifier |
| 3389 |
or security acceptor.<a href="#section-6.4-1" class="pilcrow">¶</a></p> |
| 3390 |
</section> |
| 3391 |
<section id="section-6.5"> |
| 3392 |
<h3 id="name-bundle-fragmentation"> |
| 3393 |
<a href="#section-6.5" class="section-number selfRef">6.5. </a><a href="#name-bundle-fragmentation" class="section-name selfRef">Bundle Fragmentation</a> |
| 3394 |
</h3> |
| 3395 |
<p id="section-6.5-1"> |
| 3396 |
Bundle fragmentation might prevent security services in a bundle from being |
| 3397 |
verified after a bundle is fragmented and before the bundle is |
| 3398 |
re-assembled. Examples of potential issues include the following.<a href="#section-6.5-1" class="pilcrow">¶</a></p> |
| 3399 |
<ul class="normal"> |
| 3400 |
<li class="normal" id="section-6.5-2.1"> |
| 3401 |
If a security block and its security target do not exist in the |
| 3402 |
same fragment, then the security block cannot be processed until the |
| 3403 |
bundle is re-assembled. If a fragment includes an encrypted |
| 3404 |
target block, but not its BCB, then a receiving Bundle Protocol |
| 3405 |
Agent (BPA) will not know that the target block has been encrypted.<a href="#section-6.5-2.1" class="pilcrow">¶</a> |
| 3406 |
</li> |
| 3407 |
<li class="normal" id="section-6.5-2.2"> |
| 3408 |
A security block can be cryptographically bound to a bundle by setting the |
| 3409 |
integrity scope flags (for BIB-HMAC-SHA2) or the AAD scope flags (for |
| 3410 |
BCB-AES-GCM) to include the bundle primary block. When a security |
| 3411 |
block is cryptographically bound to a bundle, it cannot be processed |
| 3412 |
even if the security block and target both coexist in the fragment. This |
| 3413 |
is because fragments have different primary blocks than the original bundle.<a href="#section-6.5-2.2" class="pilcrow">¶</a> |
| 3414 |
</li> |
| 3415 |
<li class="normal" id="section-6.5-2.3"> |
| 3416 |
If security blocks and their target blocks are repeated in |
| 3417 |
multiple fragments, policy needs to determine how to deal with issues |
| 3418 |
where a security operation verifies in one fragment but fails |
| 3419 |
in another fragment. This might happen, for example, if a BIB block |
| 3420 |
becomes corrupted in one fragment but not in another fragment.<a href="#section-6.5-2.3" class="pilcrow">¶</a> |
| 3421 |
</li> |
| 3422 |
</ul> |
| 3423 |
<p id="section-6.5-3"> |
| 3424 |
Implementors should consider how security blocks are processed when |
| 3425 |
a BPA fragments a received bundle. For example, security blocks and their targets |
| 3426 |
could be placed in the same fragment if the security block is not |
| 3427 |
otherwise cryptographically bound to the bundle being fragmented. |
| 3428 |
Alternatively, if security blocks are cryptographically bound to a |
| 3429 |
bundle, then a fragmenting BPA should consider encapsulating the bundle |
| 3430 |
first and then fragmenting the encapsulating bundle.<a href="#section-6.5-3" class="pilcrow">¶</a></p> |
| 3431 |
</section> |
| 3432 |
</section> |
| 3433 |
</div> |
| 3434 |
<section id="section-7"> |
| 3435 |
<h2 id="name-normative-references"> |
| 3436 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 3437 |
</h2> |
| 3438 |
<dl class="references"> |
| 3439 |
<dt id="AES-GCM">[AES-GCM]</dt> |
| 3440 |
<dd> |
| 3441 |
<span class="refAuthor">Dworkin, M.</span>, <span class="refTitle">"Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC"</span>, <span class="seriesInfo">NIST Special Publication 800-38D</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-38D</span>, <time datetime="2007-11" class="refDate">November 2007</time>, <span><<a href="https://doi.org/10.6028/NIST.SP.800-38D">https://doi.org/10.6028/NIST.SP.800-38D</a>></span>. </dd> |
| 3442 |
<dd class="break"></dd> |
| 3443 |
<dt id="RFC2104">[RFC2104]</dt> |
| 3444 |
<dd> |
| 3445 |
<span class="refAuthor">Krawczyk, H.</span>, <span class="refAuthor">Bellare, M.</span>, and <span class="refAuthor">R. Canetti</span>, <span class="refTitle">"HMAC: Keyed-Hashing for Message Authentication"</span>, <span class="seriesInfo">RFC 2104</span>, <span class="seriesInfo">DOI 10.17487/RFC2104</span>, <time datetime="1997-02" class="refDate">February 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2104">https://www.rfc-editor.org/info/rfc2104</a>></span>. </dd> |
| 3446 |
<dd class="break"></dd> |
| 3447 |
<dt id="RFC2119">[RFC2119]</dt> |
| 3448 |
<dd> |
| 3449 |
<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> |
| 3450 |
<dd class="break"></dd> |
| 3451 |
<dt id="RFC3394">[RFC3394]</dt> |
| 3452 |
<dd> |
| 3453 |
<span class="refAuthor">Schaad, J.</span> and <span class="refAuthor">R. Housley</span>, <span class="refTitle">"Advanced Encryption Standard (AES) Key Wrap Algorithm"</span>, <span class="seriesInfo">RFC 3394</span>, <span class="seriesInfo">DOI 10.17487/RFC3394</span>, <time datetime="2002-09" class="refDate">September 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3394">https://www.rfc-editor.org/info/rfc3394</a>></span>. </dd> |
| 3454 |
<dd class="break"></dd> |
| 3455 |
<dt id="RFC8126">[RFC8126]</dt> |
| 3456 |
<dd> |
| 3457 |
<span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>></span>. </dd> |
| 3458 |
<dd class="break"></dd> |
| 3459 |
<dt id="RFC8152">[RFC8152]</dt> |
| 3460 |
<dd> |
| 3461 |
<span class="refAuthor">Schaad, J.</span>, <span class="refTitle">"CBOR Object Signing and Encryption (COSE)"</span>, <span class="seriesInfo">RFC 8152</span>, <span class="seriesInfo">DOI 10.17487/RFC8152</span>, <time datetime="2017-07" class="refDate">July 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8152">https://www.rfc-editor.org/info/rfc8152</a>></span>. </dd> |
| 3462 |
<dd class="break"></dd> |
| 3463 |
<dt id="RFC8174">[RFC8174]</dt> |
| 3464 |
<dd> |
| 3465 |
<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> |
| 3466 |
<dd class="break"></dd> |
| 3467 |
<dt id="RFC8742">[RFC8742]</dt> |
| 3468 |
<dd> |
| 3469 |
<span class="refAuthor">Bormann, C.</span>, <span class="refTitle">"Concise Binary Object Representation (CBOR) Sequences"</span>, <span class="seriesInfo">RFC 8742</span>, <span class="seriesInfo">DOI 10.17487/RFC8742</span>, <time datetime="2020-02" class="refDate">February 2020</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8742">https://www.rfc-editor.org/info/rfc8742</a>></span>. </dd> |
| 3470 |
<dd class="break"></dd> |
| 3471 |
<dt id="RFC8949">[RFC8949]</dt> |
| 3472 |
<dd> |
| 3473 |
<span class="refAuthor">Bormann, C.</span> and <span class="refAuthor">P. Hoffman</span>, <span class="refTitle">"Concise Binary Object Representation (CBOR)"</span>, <span class="seriesInfo">STD 94</span>, <span class="seriesInfo">RFC 8949</span>, <span class="seriesInfo">DOI 10.17487/RFC8949</span>, <time datetime="2020-12" class="refDate">December 2020</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8949">https://www.rfc-editor.org/info/rfc8949</a>></span>. </dd> |
| 3474 |
<dd class="break"></dd> |
| 3475 |
<dt id="RFC9171">[RFC9171]</dt> |
| 3476 |
<dd> |
| 3477 |
<span class="refAuthor">Burleigh, S.</span>, <span class="refAuthor">Fall, K.</span>, and <span class="refAuthor">E. Birrane, III</span>, <span class="refTitle">"Bundle Protocol Version 7"</span>, <span class="seriesInfo">RFC 9171</span>, <span class="seriesInfo">DOI 10.17487/RFC9171</span>, <time datetime="2022-01" class="refDate">January 2022</time>, <span><<a href="https://www.rfc-editor.org/rfc/rfc9171">https://www.rfc-editor.org/rfc/rfc9171</a>></span>. </dd> |
| 3478 |
<dd class="break"></dd> |
| 3479 |
<dt id="RFC9172">[RFC9172]</dt> |
| 3480 |
<dd> |
| 3481 |
<span class="refAuthor">Birrane, III, E.</span> and <span class="refAuthor">K. McKeever</span>, <span class="refTitle">"Bundle Protocol Security (BPSec)"</span>, <span class="seriesInfo">RFC 9172</span>, <span class="seriesInfo">DOI 10.17487/RFC9172</span>, <time datetime="2022-01" class="refDate">January 2022</time>, <span><<a href="https://www.rfc-editor.org/rfc/rfc9172">https://www.rfc-editor.org/rfc/rfc9172</a>></span>. </dd> |
| 3482 |
<dd class="break"></dd> |
| 3483 |
<dt id="SHS">[SHS]</dt> |
| 3484 |
<dd> |
| 3485 |
<span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Secure Hash Standard (SHS)"</span>, <span class="seriesInfo">FIPS PUB 180-4</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.180-4</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span><<a href="https://csrc.nist.gov/publications/detail/fips/180/4/final">https://csrc.nist.gov/publications/detail/fips/180/4/final</a>></span>. </dd> |
| 3486 |
<dd class="break"></dd> |
| 3487 |
</dl> |
| 3488 |
</section> |
| 3489 |
<div id="vectors"> |
| 3490 |
<section id="appendix-A"> |
| 3491 |
<h2 id="name-examples"> |
| 3492 |
<a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-examples" class="section-name selfRef">Examples</a> |
| 3493 |
</h2> |
| 3494 |
<p id="appendix-A-1"> This appendix is informative.<a href="#appendix-A-1" class="pilcrow">¶</a></p> |
| 3495 |
<p id="appendix-A-2"> |
| 3496 |
This appendix presents a series of examples of constructing BPSec |
| 3497 |
security blocks (using the security contexts defined in this document) |
| 3498 |
and adding those blocks to a sample bundle.<a href="#appendix-A-2" class="pilcrow">¶</a></p> |
| 3499 |
<p id="appendix-A-3"> |
| 3500 |
The examples presented in this appendix represent valid constructions of |
| 3501 |
bundles, security blocks, and the encoding of security context parameters |
| 3502 |
and results. For this reason, they can inform unit test suites |
| 3503 |
for individual implementations as well as interoperability test suites |
| 3504 |
amongst implementations. However, these examples do not cover every |
| 3505 |
permutation of security context parameters, security results, or use of security |
| 3506 |
blocks in a bundle.<a href="#appendix-A-3" class="pilcrow">¶</a></p> |
| 3507 |
<p id="appendix-A-4"> |
| 3508 |
NOTES:<a href="#appendix-A-4" class="pilcrow">¶</a></p> |
| 3509 |
<ul class="normal"> |
| 3510 |
<li class="normal" id="appendix-A-5.1">The bundle diagrams in this appendix are patterned after the bundle |
| 3511 |
diagrams used in Section <span><a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.11" class="relref">3.11</a> (<a href="https://www.rfc-editor.org/rfc/rfc9172#section-3.11" class="relref">"BPSec Block Examples"</a>)</span> of <span>[<a href="#RFC9172" class="xref">RFC9172</a>]</span>.<a href="#appendix-A-5.1" class="pilcrow">¶</a> |
| 3512 |
</li> |
| 3513 |
<li class="normal" id="appendix-A-5.2"> |
| 3514 |
Figures in this appendix identified as "(CBOR Diagnostic Notation)" |
| 3515 |
are represented using the CBOR diagnostic notation defined in <span>[<a href="#RFC8949" class="xref">RFC8949</a>]</span>. |
| 3516 |
This notation is used to express CBOR data structures in a manner that enables |
| 3517 |
visual inspection. The bundles, security blocks, and security context contents |
| 3518 |
in these figures are represented using CBOR structures. In cases where BP blocks |
| 3519 |
(to include BPSec security blocks) are comprised of a sequence of |
| 3520 |
CBOR objects, these objects are represented as a CBOR sequence as defined in |
| 3521 |
<span>[<a href="#RFC8742" class="xref">RFC8742</a>]</span>.<a href="#appendix-A-5.2" class="pilcrow">¶</a> |
| 3522 |
</li> |
| 3523 |
<li class="normal" id="appendix-A-5.3"> |
| 3524 |
Examples in this appendix use the "ipn" URI scheme for endpoint ID |
| 3525 |
naming, as defined in <span>[<a href="#RFC9171" class="xref">RFC9171</a>]</span>.<a href="#appendix-A-5.3" class="pilcrow">¶</a> |
| 3526 |
</li> |
| 3527 |
<li class="normal" id="appendix-A-5.4"> |
| 3528 |
The bundle source is presumed to be the security source for all |
| 3529 |
security blocks in this appendix, unless otherwise noted.<a href="#appendix-A-5.4" class="pilcrow">¶</a> |
| 3530 |
</li> |
| 3531 |
</ul> |
| 3532 |
<section id="appendix-A.1"> |
| 3533 |
<h3 id="name-example-1-simple-integrity"> |
| 3534 |
<a href="#appendix-A.1" class="section-number selfRef">A.1. </a><a href="#name-example-1-simple-integrity" class="section-name selfRef">Example 1 - Simple Integrity</a> |
| 3535 |
</h3> |
| 3536 |
<p id="appendix-A.1-1"> |
| 3537 |
This example shows the addition of a BIB to a sample bundle |
| 3538 |
to provide integrity for the payload block.<a href="#appendix-A.1-1" class="pilcrow">¶</a></p> |
| 3539 |
<section id="appendix-A.1.1"> |
| 3540 |
<h4 id="name-original-bundle"> |
| 3541 |
<a href="#appendix-A.1.1" class="section-number selfRef">A.1.1. </a><a href="#name-original-bundle" class="section-name selfRef">Original Bundle</a> |
| 3542 |
</h4> |
| 3543 |
<p id="appendix-A.1.1-1"> |
| 3544 |
The following diagram shows the original bundle before the |
| 3545 |
BIB has been added.<a href="#appendix-A.1.1-1" class="pilcrow">¶</a></p> |
| 3546 |
<span id="name-example-1-original-bundle"></span><figure id="figure-1"> |
| 3547 |
<div class="alignCenter art-text artwork" id="appendix-A.1.1-2.1"> |
| 3548 |
<pre> |
| 3549 |
Block Block Block |
| 3550 |
in Bundle Type Number |
| 3551 |
+========================================+=======+========+ |
| 3552 |
| Primary Block | N/A | 0 | |
| 3553 |
+----------------------------------------+-------+--------+ |
| 3554 |
| Payload Block | 1 | 1 | |
| 3555 |
+----------------------------------------+-------+--------+ |
| 3556 |
</pre> |
| 3557 |
</div> |
| 3558 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 3559 |
<a href="#name-example-1-original-bundle" class="selfRef">Example 1 - Original Bundle</a> |
| 3560 |
</figcaption></figure> |
| 3561 |
<div id="ex_primary_block"> |
| 3562 |
<section id="appendix-A.1.1.1"> |
| 3563 |
<h5 id="name-primary-block"> |
| 3564 |
<a href="#appendix-A.1.1.1" class="section-number selfRef">A.1.1.1. </a><a href="#name-primary-block" class="section-name selfRef">Primary Block</a> |
| 3565 |
</h5> |
| 3566 |
<p id="appendix-A.1.1.1-1"> |
| 3567 |
The Bundle Protocol version 7 (BPv7) bundle has no special block |
| 3568 |
and bundle processing control flags, and no CRC is provided |
| 3569 |
because the primary block is expected to be protected by an |
| 3570 |
integrity service BIB using the BIB-HMAC-SHA2 security context.<a href="#appendix-A.1.1.1-1" class="pilcrow">¶</a></p> |
| 3571 |
<p id="appendix-A.1.1.1-2"> |
| 3572 |
The bundle is sourced at the source node ipn:2.1 and destined for |
| 3573 |
the destination node ipn:1.2. |
| 3574 |
The bundle creation time is set to 0, indicating lack of an accurate clock, |
| 3575 |
with a |
| 3576 |
sequence number of 40. The lifetime of the bundle is given as |
| 3577 |
1,000,000 milliseconds since the bundle creation time.<a href="#appendix-A.1.1.1-2" class="pilcrow">¶</a></p> |
| 3578 |
<p id="appendix-A.1.1.1-3"> |
| 3579 |
The primary block is provided as follows.<a href="#appendix-A.1.1.1-3" class="pilcrow">¶</a></p> |
| 3580 |
<span id="name-primary-block-cbor-diagnost"></span><div id="ex_bdl_prim"> |
| 3581 |
<figure id="figure-2"> |
| 3582 |
<div id="appendix-A.1.1.1-4.1"> |
| 3583 |
<pre class="lang-cbor-diag sourcecode"> |
| 3584 |
[ |
| 3585 |
7, / BP version / |
| 3586 |
0, / flags / |
| 3587 |
0, / CRC type / |
| 3588 |
[2, [1,2]], / destination (ipn:1.2) / |
| 3589 |
[2, [2,1]], / source (ipn:2.1) / |
| 3590 |
[2, [2,1]], / report-to (ipn:2.1) / |
| 3591 |
[0, 40], / timestamp / |
| 3592 |
1000000 / lifetime / |
| 3593 |
] |
| 3594 |
</pre> |
| 3595 |
</div> |
| 3596 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 3597 |
<a href="#name-primary-block-cbor-diagnost" class="selfRef">Primary Block (CBOR Diagnostic Notation)</a> |
| 3598 |
</figcaption></figure> |
| 3599 |
</div> |
| 3600 |
<p id="appendix-A.1.1.1-5"> |
| 3601 |
The CBOR encoding of the primary block is:<a href="#appendix-A.1.1.1-5" class="pilcrow">¶</a></p> |
| 3602 |
<div id="appendix-A.1.1.1-6"> |
| 3603 |
<pre class="sourcecode"> |
| 3604 |
0x88070000820282010282028202018202820201820018281a000f4240 |
| 3605 |
</pre><a href="#appendix-A.1.1.1-6" class="pilcrow">¶</a> |
| 3606 |
</div> |
| 3607 |
</section> |
| 3608 |
</div> |
| 3609 |
<div id="ex_payload_block"> |
| 3610 |
<section id="appendix-A.1.1.2"> |
| 3611 |
<h5 id="name-payload-block"> |
| 3612 |
<a href="#appendix-A.1.1.2" class="section-number selfRef">A.1.1.2. </a><a href="#name-payload-block" class="section-name selfRef">Payload Block</a> |
| 3613 |
</h5> |
| 3614 |
<p id="appendix-A.1.1.2-1"> |
| 3615 |
Other than its use as a source of plaintext for security blocks, |
| 3616 |
the payload has no required distinguishing characteristic for the |
| 3617 |
purpose of this example. The sample payload is a 35-byte string.<a href="#appendix-A.1.1.2-1" class="pilcrow">¶</a></p> |
| 3618 |
<p id="appendix-A.1.1.2-2"> |
| 3619 |
The payload is represented in the payload block as a byte string |
| 3620 |
of the raw payload string. It is NOT represented as a CBOR text |
| 3621 |
string wrapped within a CBOR binary string. The hex value of the |
| 3622 |
payload is:<a href="#appendix-A.1.1.2-2" class="pilcrow">¶</a></p> |
| 3623 |
<div id="appendix-A.1.1.2-3"> |
| 3624 |
<pre class="sourcecode"> |
| 3625 |
0x526561647920746f2067656e657261746520612033322d62797465207061796c6f |
| 3626 |
6164 |
| 3627 |
</pre><a href="#appendix-A.1.1.2-3" class="pilcrow">¶</a> |
| 3628 |
</div> |
| 3629 |
<p id="appendix-A.1.1.2-4"> |
| 3630 |
The payload block is provided as follows.<a href="#appendix-A.1.1.2-4" class="pilcrow">¶</a></p> |
| 3631 |
<span id="name-payload-block-cbor-diagnost"></span><figure id="figure-3"> |
| 3632 |
<div id="appendix-A.1.1.2-5.1"> |
| 3633 |
<pre class="lang-cbor-diag sourcecode"> |
| 3634 |
[ |
| 3635 |
1, / type code: Payload block / |
| 3636 |
1, / block number / |
| 3637 |
0, / block processing control flags / |
| 3638 |
0, / CRC type / |
| 3639 |
h'526561647920746f206765 / type-specific-data: payload / |
| 3640 |
6e657261746520612033322d |
| 3641 |
62797465207061796c6f6164' |
| 3642 |
] |
| 3643 |
</pre> |
| 3644 |
</div> |
| 3645 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 3646 |
<a href="#name-payload-block-cbor-diagnost" class="selfRef">Payload Block (CBOR Diagnostic Notation)</a> |
| 3647 |
</figcaption></figure> |
| 3648 |
<p id="appendix-A.1.1.2-6"> |
| 3649 |
The CBOR encoding of the payload block is:<a href="#appendix-A.1.1.2-6" class="pilcrow">¶</a></p> |
| 3650 |
<div id="appendix-A.1.1.2-7"> |
| 3651 |
<pre class="sourcecode"> |
| 3652 |
0x85010100005823526561647920746f2067656e657261746520612033322d627974 |
| 3653 |
65207061796c6f6164 |
| 3654 |
</pre><a href="#appendix-A.1.1.2-7" class="pilcrow">¶</a> |
| 3655 |
</div> |
| 3656 |
</section> |
| 3657 |
</div> |
| 3658 |
<section id="appendix-A.1.1.3"> |
| 3659 |
<h5 id="name-bundle-cbor-representation"> |
| 3660 |
<a href="#appendix-A.1.1.3" class="section-number selfRef">A.1.1.3. </a><a href="#name-bundle-cbor-representation" class="section-name selfRef">Bundle CBOR Representation</a> |
| 3661 |
</h5> |
| 3662 |
<p id="appendix-A.1.1.3-1"> |
| 3663 |
A BPv7 bundle is represented as an indefinite-length array consisting |
| 3664 |
of the blocks comprising the bundle, with a terminator character at |
| 3665 |
the end.<a href="#appendix-A.1.1.3-1" class="pilcrow">¶</a></p> |
| 3666 |
<p id="appendix-A.1.1.3-2"> |
| 3667 |
The CBOR encoding of the original bundle is:<a href="#appendix-A.1.1.3-2" class="pilcrow">¶</a></p> |
| 3668 |
<div id="appendix-A.1.1.3-3"> |
| 3669 |
<pre class="sourcecode"> |
| 3670 |
0x9f88070000820282010282028202018202820201820018281a000f424085010100 |
| 3671 |
005823526561647920746f2067656e657261746520612033322d6279746520706179 |
| 3672 |
6c6f6164ff |
| 3673 |
</pre><a href="#appendix-A.1.1.3-3" class="pilcrow">¶</a> |
| 3674 |
</div> |
| 3675 |
</section> |
| 3676 |
</section> |
| 3677 |
<section id="appendix-A.1.2"> |
| 3678 |
<h4 id="name-security-operation-overview"> |
| 3679 |
<a href="#appendix-A.1.2" class="section-number selfRef">A.1.2. </a><a href="#name-security-operation-overview" class="section-name selfRef">Security Operation Overview</a> |
| 3680 |
</h4> |
| 3681 |
<p id="appendix-A.1.2-1"> |
| 3682 |
This example adds a BIB to the bundle using the BIB-HMAC-SHA2 security |
| 3683 |
context to provide an integrity mechanism over the payload block.<a href="#appendix-A.1.2-1" class="pilcrow">¶</a></p> |
| 3684 |
<p id="appendix-A.1.2-2"> |
| 3685 |
The following diagram shows the resulting bundle after the |
| 3686 |
BIB is added.<a href="#appendix-A.1.2-2" class="pilcrow">¶</a></p> |
| 3687 |
<span id="name-example-1-resulting-bundle"></span><figure id="figure-4"> |
| 3688 |
<div class="alignCenter art-text artwork" id="appendix-A.1.2-3.1"> |
| 3689 |
<pre> |
| 3690 |
Block Block Block |
| 3691 |
in Bundle Type Number |
| 3692 |
+========================================+=======+========+ |
| 3693 |
| Primary Block | N/A | 0 | |
| 3694 |
+----------------------------------------+-------+--------+ |
| 3695 |
| Block Integrity Block | 11 | 2 | |
| 3696 |
| OP(bib-integrity, target=1) | | | |
| 3697 |
+----------------------------------------+-------+--------+ |
| 3698 |
| Payload Block | 1 | 1 | |
| 3699 |
+----------------------------------------+-------+--------+ |
| 3700 |
</pre> |
| 3701 |
</div> |
| 3702 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 3703 |
<a href="#name-example-1-resulting-bundle" class="selfRef">Example 1 - Resulting Bundle</a> |
| 3704 |
</figcaption></figure> |
| 3705 |
</section> |
| 3706 |
<section id="appendix-A.1.3"> |
| 3707 |
<h4 id="name-block-integrity-block"> |
| 3708 |
<a href="#appendix-A.1.3" class="section-number selfRef">A.1.3. </a><a href="#name-block-integrity-block" class="section-name selfRef">Block Integrity Block</a> |
| 3709 |
</h4> |
| 3710 |
<p id="appendix-A.1.3-1"> |
| 3711 |
In this example, a BIB is used to carry an integrity signature over |
| 3712 |
the payload block.<a href="#appendix-A.1.3-1" class="pilcrow">¶</a></p> |
| 3713 |
<section id="appendix-A.1.3.1"> |
| 3714 |
<h5 id="name-configuration-parameters-an"> |
| 3715 |
<a href="#appendix-A.1.3.1" class="section-number selfRef">A.1.3.1. </a><a href="#name-configuration-parameters-an" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 3716 |
</h5> |
| 3717 |
<p id="appendix-A.1.3.1-1"> |
| 3718 |
For this example, the following configuration and security context |
| 3719 |
parameters are used to generate the security results |
| 3720 |
indicated.<a href="#appendix-A.1.3.1-1" class="pilcrow">¶</a></p> |
| 3721 |
<p id="appendix-A.1.3.1-2"> |
| 3722 |
This BIB has a single target and includes a single security |
| 3723 |
result: the calculated signature over the payload block.<a href="#appendix-A.1.3.1-2" class="pilcrow">¶</a></p> |
| 3724 |
<span id="name-example-1-configuration-par"></span><div id="ex1_cpr"> |
| 3725 |
<figure id="figure-5"> |
| 3726 |
<div class="alignCenter art-text artwork" id="appendix-A.1.3.1-3.1"> |
| 3727 |
<pre> |
| 3728 |
Key : h'1a2b1a2b1a2b1a2b1a2b1a2b1a2b1a2b' |
| 3729 |
SHA Variant : HMAC 512/512 |
| 3730 |
Scope Flags : 0x00 |
| 3731 |
Payload Data: h'526561647920746f2067656e65726174 |
| 3732 |
6520612033322d62797465207061796c |
| 3733 |
6f6164' |
| 3734 |
IPPT : h'005823526561647920746f2067656e65 |
| 3735 |
7261746520612033322d627974652070 |
| 3736 |
61796c6f6164' |
| 3737 |
Signature : h'3bdc69b3a34a2b5d3a8554368bd1e808 |
| 3738 |
f606219d2a10a846eae3886ae4ecc83c |
| 3739 |
4ee550fdfb1cc636b904e2f1a73e303d |
| 3740 |
cd4b6ccece003e95e8164dcc89a156e1' |
| 3741 |
</pre> |
| 3742 |
</div> |
| 3743 |
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>: |
| 3744 |
<a href="#name-example-1-configuration-par" class="selfRef">Example 1 - Configuration, Parameters, and Results</a> |
| 3745 |
</figcaption></figure> |
| 3746 |
</div> |
| 3747 |
</section> |
| 3748 |
<section id="appendix-A.1.3.2"> |
| 3749 |
<h5 id="name-abstract-security-block"> |
| 3750 |
<a href="#appendix-A.1.3.2" class="section-number selfRef">A.1.3.2. </a><a href="#name-abstract-security-block" class="section-name selfRef">Abstract Security Block</a> |
| 3751 |
</h5> |
| 3752 |
<p id="appendix-A.1.3.2-1"> |
| 3753 |
The abstract security block structure of the BIB's |
| 3754 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.1.3.2-1" class="pilcrow">¶</a></p> |
| 3755 |
<span id="name-example-1-bib-abstract-secu"></span><div id="ex1_bib_asb"> |
| 3756 |
<figure id="figure-6"> |
| 3757 |
<div id="appendix-A.1.3.2-2.1"> |
| 3758 |
<pre class="lang-cbor-diag sourcecode"> |
| 3759 |
[1], / Security Target - Payload block / |
| 3760 |
1, / Security Context ID - BIB-HMAC-SHA2 / |
| 3761 |
1, / Security Context Flags - Parameters Present / |
| 3762 |
[2,[2, 1]], / Security Source - ipn:2.1 / |
| 3763 |
[ / Security Parameters - 2 Parameters / |
| 3764 |
[1, 7], / SHA Variant - HMAC 512/512 / |
| 3765 |
[3, 0x00] / Scope Flags - No Additional Scope / |
| 3766 |
], |
| 3767 |
[ / Security Results: 1 Result / |
| 3768 |
[ / Target 1 Results / |
| 3769 |
[1, h'3bdc69b3a34a2b5d3a8554368bd1e808 / MAC / |
| 3770 |
f606219d2a10a846eae3886ae4ecc83c |
| 3771 |
4ee550fdfb1cc636b904e2f1a73e303d |
| 3772 |
cd4b6ccece003e95e8164dcc89a156e1'] |
| 3773 |
] |
| 3774 |
] |
| 3775 |
</pre> |
| 3776 |
</div> |
| 3777 |
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a>: |
| 3778 |
<a href="#name-example-1-bib-abstract-secu" class="selfRef">Example 1 - BIB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 3779 |
</figcaption></figure> |
| 3780 |
</div> |
| 3781 |
<p id="appendix-A.1.3.2-3"> |
| 3782 |
The CBOR encoding of the BIB block-type-specific data field (the abstract security block) is:<a href="#appendix-A.1.3.2-3" class="pilcrow">¶</a></p> |
| 3783 |
<div id="appendix-A.1.3.2-4"> |
| 3784 |
<pre class="sourcecode"> |
| 3785 |
0x810101018202820201828201078203008181820158403bdc69b3a34a2b5d3a8554 |
| 3786 |
368bd1e808f606219d2a10a846eae3886ae4ecc83c4ee550fdfb1cc636b904e2f1a7 |
| 3787 |
3e303dcd4b6ccece003e95e8164dcc89a156e1 |
| 3788 |
</pre><a href="#appendix-A.1.3.2-4" class="pilcrow">¶</a> |
| 3789 |
</div> |
| 3790 |
</section> |
| 3791 |
<section id="appendix-A.1.3.3"> |
| 3792 |
<h5 id="name-representations"> |
| 3793 |
<a href="#appendix-A.1.3.3" class="section-number selfRef">A.1.3.3. </a><a href="#name-representations" class="section-name selfRef">Representations</a> |
| 3794 |
</h5> |
| 3795 |
<p id="appendix-A.1.3.3-1"> |
| 3796 |
The complete BIB is as follows.<a href="#appendix-A.1.3.3-1" class="pilcrow">¶</a></p> |
| 3797 |
<span id="name-example-1-bib-cbor-diagnost"></span><div id="ex1_bib"> |
| 3798 |
<figure id="figure-7"> |
| 3799 |
<div id="appendix-A.1.3.3-2.1"> |
| 3800 |
<pre class="lang-cbor-diag sourcecode"> |
| 3801 |
[ |
| 3802 |
11, / type code / |
| 3803 |
2, / block number / |
| 3804 |
0, / flags / |
| 3805 |
0, / CRC type / |
| 3806 |
h'810101018202820201828201078203008181820158403bdc69b3a34a |
| 3807 |
2b5d3a8554368bd1e808f606219d2a10a846eae3886ae4ecc83c4ee550 |
| 3808 |
fdfb1cc636b904e2f1a73e303dcd4b6ccece003e95e8164dcc89a156e1' |
| 3809 |
] |
| 3810 |
</pre> |
| 3811 |
</div> |
| 3812 |
<figcaption><a href="#figure-7" class="selfRef">Figure 7</a>: |
| 3813 |
<a href="#name-example-1-bib-cbor-diagnost" class="selfRef">Example 1 - BIB (CBOR Diagnostic Notation)</a> |
| 3814 |
</figcaption></figure> |
| 3815 |
</div> |
| 3816 |
<p id="appendix-A.1.3.3-3"> |
| 3817 |
The CBOR encoding of the BIB block is:<a href="#appendix-A.1.3.3-3" class="pilcrow">¶</a></p> |
| 3818 |
<div id="appendix-A.1.3.3-4"> |
| 3819 |
<pre class="sourcecode"> |
| 3820 |
0x850b0200005856810101018202820201828201078203008181820158403bdc69b3 |
| 3821 |
a34a2b5d3a8554368bd1e808f606219d2a10a846eae3886ae4ecc83c4ee550fdfb1c |
| 3822 |
c636b904e2f1a73e303dcd4b6ccece003e95e8164dcc89a156e1 |
| 3823 |
</pre><a href="#appendix-A.1.3.3-4" class="pilcrow">¶</a> |
| 3824 |
</div> |
| 3825 |
</section> |
| 3826 |
</section> |
| 3827 |
<section id="appendix-A.1.4"> |
| 3828 |
<h4 id="name-final-bundle"> |
| 3829 |
<a href="#appendix-A.1.4" class="section-number selfRef">A.1.4. </a><a href="#name-final-bundle" class="section-name selfRef">Final Bundle</a> |
| 3830 |
</h4> |
| 3831 |
<p id="appendix-A.1.4-1"> |
| 3832 |
The CBOR encoding of the full output bundle, with the BIB:<a href="#appendix-A.1.4-1" class="pilcrow">¶</a></p> |
| 3833 |
<div id="appendix-A.1.4-2"> |
| 3834 |
<pre class="sourcecode"> |
| 3835 |
0x9f88070000820282010282028202018202820201820018281a000f4240850b0200 |
| 3836 |
005856810101018202820201828201078203008181820158403bdc69b3a34a2b5d3a |
| 3837 |
8554368bd1e808f606219d2a10a846eae3886ae4ecc83c4ee550fdfb1cc636b904e2 |
| 3838 |
f1a73e303dcd4b6ccece003e95e8164dcc89a156e185010100005823526561647920 |
| 3839 |
746f2067656e657261746520612033322d62797465207061796c6f6164ff |
| 3840 |
</pre><a href="#appendix-A.1.4-2" class="pilcrow">¶</a> |
| 3841 |
</div> |
| 3842 |
</section> |
| 3843 |
</section> |
| 3844 |
<section id="appendix-A.2"> |
| 3845 |
<h3 id="name-example-2-simple-confidenti"> |
| 3846 |
<a href="#appendix-A.2" class="section-number selfRef">A.2. </a><a href="#name-example-2-simple-confidenti" class="section-name selfRef">Example 2 - Simple Confidentiality with Key Wrap</a> |
| 3847 |
</h3> |
| 3848 |
<p id="appendix-A.2-1"> |
| 3849 |
This example shows the addition of a BCB to a sample bundle |
| 3850 |
to provide confidentiality for the payload block. AES key wrap |
| 3851 |
is used to transmit the symmetric key used to generate the |
| 3852 |
security results for this service.<a href="#appendix-A.2-1" class="pilcrow">¶</a></p> |
| 3853 |
<section id="appendix-A.2.1"> |
| 3854 |
<h4 id="name-original-bundle-2"> |
| 3855 |
<a href="#appendix-A.2.1" class="section-number selfRef">A.2.1. </a><a href="#name-original-bundle-2" class="section-name selfRef">Original Bundle</a> |
| 3856 |
</h4> |
| 3857 |
<p id="appendix-A.2.1-1"> |
| 3858 |
The following diagram shows the original bundle before the |
| 3859 |
BCB has been added.<a href="#appendix-A.2.1-1" class="pilcrow">¶</a></p> |
| 3860 |
<span id="name-example-2-original-bundle"></span><figure id="figure-8"> |
| 3861 |
<div class="alignCenter art-text artwork" id="appendix-A.2.1-2.1"> |
| 3862 |
<pre> |
| 3863 |
Block Block Block |
| 3864 |
in Bundle Type Number |
| 3865 |
+========================================+=======+========+ |
| 3866 |
| Primary Block | N/A | 0 | |
| 3867 |
+----------------------------------------+-------+--------+ |
| 3868 |
| Payload Block | 1 | 1 | |
| 3869 |
+----------------------------------------+-------+--------+ |
| 3870 |
</pre> |
| 3871 |
</div> |
| 3872 |
<figcaption><a href="#figure-8" class="selfRef">Figure 8</a>: |
| 3873 |
<a href="#name-example-2-original-bundle" class="selfRef">Example 2 - Original Bundle</a> |
| 3874 |
</figcaption></figure> |
| 3875 |
<section id="appendix-A.2.1.1"> |
| 3876 |
<h5 id="name-primary-block-2"> |
| 3877 |
<a href="#appendix-A.2.1.1" class="section-number selfRef">A.2.1.1. </a><a href="#name-primary-block-2" class="section-name selfRef">Primary Block</a> |
| 3878 |
</h5> |
| 3879 |
<p id="appendix-A.2.1.1-1"> |
| 3880 |
The primary block used in this example is identical to the primary block |
| 3881 |
presented for Example 1 in <a href="#ex_primary_block" class="xref">Appendix A.1.1.1</a>.<a href="#appendix-A.2.1.1-1" class="pilcrow">¶</a></p> |
| 3882 |
<p id="appendix-A.2.1.1-2"> |
| 3883 |
In summary, the CBOR encoding of the primary block is:<a href="#appendix-A.2.1.1-2" class="pilcrow">¶</a></p> |
| 3884 |
<div id="appendix-A.2.1.1-3"> |
| 3885 |
<pre class="sourcecode"> |
| 3886 |
0x88070000820282010282028202018202820201820018281a000f4240 |
| 3887 |
</pre><a href="#appendix-A.2.1.1-3" class="pilcrow">¶</a> |
| 3888 |
</div> |
| 3889 |
</section> |
| 3890 |
<section id="appendix-A.2.1.2"> |
| 3891 |
<h5 id="name-payload-block-2"> |
| 3892 |
<a href="#appendix-A.2.1.2" class="section-number selfRef">A.2.1.2. </a><a href="#name-payload-block-2" class="section-name selfRef">Payload Block</a> |
| 3893 |
</h5> |
| 3894 |
<p id="appendix-A.2.1.2-1"> |
| 3895 |
The payload block used in this example is identical to the payload block |
| 3896 |
presented for Example 1 in <a href="#ex_payload_block" class="xref">Appendix A.1.1.2</a>.<a href="#appendix-A.2.1.2-1" class="pilcrow">¶</a></p> |
| 3897 |
<p id="appendix-A.2.1.2-2"> |
| 3898 |
In summary, the CBOR encoding of the payload block is:<a href="#appendix-A.2.1.2-2" class="pilcrow">¶</a></p> |
| 3899 |
<div id="appendix-A.2.1.2-3"> |
| 3900 |
<pre class="sourcecode"> |
| 3901 |
0x85010100005823526561647920746f2067656e657261746520612033322d627974 |
| 3902 |
65207061796c6f6164 |
| 3903 |
</pre><a href="#appendix-A.2.1.2-3" class="pilcrow">¶</a> |
| 3904 |
</div> |
| 3905 |
</section> |
| 3906 |
<section id="appendix-A.2.1.3"> |
| 3907 |
<h5 id="name-bundle-cbor-representation-2"> |
| 3908 |
<a href="#appendix-A.2.1.3" class="section-number selfRef">A.2.1.3. </a><a href="#name-bundle-cbor-representation-2" class="section-name selfRef">Bundle CBOR Representation</a> |
| 3909 |
</h5> |
| 3910 |
<p id="appendix-A.2.1.3-1"> |
| 3911 |
A BPv7 bundle is represented as an indefinite-length array consisting |
| 3912 |
of the blocks comprising the bundle, with a terminator character at |
| 3913 |
the end.<a href="#appendix-A.2.1.3-1" class="pilcrow">¶</a></p> |
| 3914 |
<p id="appendix-A.2.1.3-2"> |
| 3915 |
The CBOR encoding of the original bundle is:<a href="#appendix-A.2.1.3-2" class="pilcrow">¶</a></p> |
| 3916 |
<div id="appendix-A.2.1.3-3"> |
| 3917 |
<pre class="sourcecode"> |
| 3918 |
0x9f88070000820282010282028202018202820201820018281a000f424085010100 |
| 3919 |
005823526561647920746f2067656e657261746520612033322d6279746520706179 |
| 3920 |
6c6f6164ff |
| 3921 |
</pre><a href="#appendix-A.2.1.3-3" class="pilcrow">¶</a> |
| 3922 |
</div> |
| 3923 |
</section> |
| 3924 |
</section> |
| 3925 |
<section id="appendix-A.2.2"> |
| 3926 |
<h4 id="name-security-operation-overview-2"> |
| 3927 |
<a href="#appendix-A.2.2" class="section-number selfRef">A.2.2. </a><a href="#name-security-operation-overview-2" class="section-name selfRef">Security Operation Overview</a> |
| 3928 |
</h4> |
| 3929 |
<p id="appendix-A.2.2-1"> |
| 3930 |
This example adds a BCB using the BCB-AES-GCM security context |
| 3931 |
using AES key wrap to provide a confidentiality mechanism over |
| 3932 |
the payload block and transmit the symmetric key.<a href="#appendix-A.2.2-1" class="pilcrow">¶</a></p> |
| 3933 |
<p id="appendix-A.2.2-2"> |
| 3934 |
The following diagram shows the resulting bundle after the |
| 3935 |
BCB is added.<a href="#appendix-A.2.2-2" class="pilcrow">¶</a></p> |
| 3936 |
<span id="name-example-2-resulting-bundle"></span><figure id="figure-9"> |
| 3937 |
<div class="alignCenter art-text artwork" id="appendix-A.2.2-3.1"> |
| 3938 |
<pre> |
| 3939 |
Block Block Block |
| 3940 |
in Bundle Type Number |
| 3941 |
+========================================+=======+========+ |
| 3942 |
| Primary Block | N/A | 0 | |
| 3943 |
+----------------------------------------+-------+--------+ |
| 3944 |
| Block Confidentiality Block | 12 | 2 | |
| 3945 |
| OP(bcb-confidentiality, target=1) | | | |
| 3946 |
+----------------------------------------+-------+--------+ |
| 3947 |
| Payload Block (Encrypted) | 1 | 1 | |
| 3948 |
+----------------------------------------+-------+--------+ |
| 3949 |
</pre> |
| 3950 |
</div> |
| 3951 |
<figcaption><a href="#figure-9" class="selfRef">Figure 9</a>: |
| 3952 |
<a href="#name-example-2-resulting-bundle" class="selfRef">Example 2 - Resulting Bundle</a> |
| 3953 |
</figcaption></figure> |
| 3954 |
</section> |
| 3955 |
<section id="appendix-A.2.3"> |
| 3956 |
<h4 id="name-block-confidentiality-block"> |
| 3957 |
<a href="#appendix-A.2.3" class="section-number selfRef">A.2.3. </a><a href="#name-block-confidentiality-block" class="section-name selfRef">Block Confidentiality Block</a> |
| 3958 |
</h4> |
| 3959 |
<p id="appendix-A.2.3-1"> |
| 3960 |
In this example, a BCB is used to encrypt the payload block, and AES key |
| 3961 |
wrap is used to encode the symmetric key prior to its inclusion in the BCB.<a href="#appendix-A.2.3-1" class="pilcrow">¶</a></p> |
| 3962 |
<section id="appendix-A.2.3.1"> |
| 3963 |
<h5 id="name-configuration-parameters-and"> |
| 3964 |
<a href="#appendix-A.2.3.1" class="section-number selfRef">A.2.3.1. </a><a href="#name-configuration-parameters-and" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 3965 |
</h5> |
| 3966 |
<p id="appendix-A.2.3.1-1"> |
| 3967 |
For this example, the following configuration and security context |
| 3968 |
parameters are used to generate the security results |
| 3969 |
indicated.<a href="#appendix-A.2.3.1-1" class="pilcrow">¶</a></p> |
| 3970 |
<p id="appendix-A.2.3.1-2"> |
| 3971 |
This BCB has a single target -- the payload block. Three |
| 3972 |
security results are generated: ciphertext that |
| 3973 |
replaces the plaintext block-type-specific data to |
| 3974 |
encrypt the payload block, an authentication tag, and |
| 3975 |
the AES wrapped key.<a href="#appendix-A.2.3.1-2" class="pilcrow">¶</a></p> |
| 3976 |
<span id="name-example-2-configuration-par"></span><div id="ex2_cpr"> |
| 3977 |
<figure id="figure-10"> |
| 3978 |
<div class="alignCenter art-text artwork" id="appendix-A.2.3.1-3.1"> |
| 3979 |
<pre> |
| 3980 |
Content Encryption |
| 3981 |
Key: h'71776572747975696f70617364666768' |
| 3982 |
Key Encryption Key: h'6162636465666768696a6b6c6d6e6f70' |
| 3983 |
IV: h'5477656c7665313231323132' |
| 3984 |
AES Variant: A128GCM |
| 3985 |
AES Wrapped Key: h'69c411276fecddc4780df42c8a2af892 |
| 3986 |
96fabf34d7fae700' |
| 3987 |
Scope Flags: 0x00 |
| 3988 |
Payload Data: h'526561647920746f2067656e65726174 |
| 3989 |
6520612033322d62797465207061796c |
| 3990 |
6f6164' |
| 3991 |
AAD: h'00' |
| 3992 |
Authentication Tag: h'efa4b5ac0108e3816c5606479801bc04' |
| 3993 |
Payload Ciphertext: h'3a09c1e63fe23a7f66a59c7303837241 |
| 3994 |
e070b02619fc59c5214a22f08cd70795 |
| 3995 |
e73e9a' |
| 3996 |
</pre> |
| 3997 |
</div> |
| 3998 |
<figcaption><a href="#figure-10" class="selfRef">Figure 10</a>: |
| 3999 |
<a href="#name-example-2-configuration-par" class="selfRef">Example 2 - Configuration, Parameters, and Results</a> |
| 4000 |
</figcaption></figure> |
| 4001 |
</div> |
| 4002 |
</section> |
| 4003 |
<section id="appendix-A.2.3.2"> |
| 4004 |
<h5 id="name-abstract-security-block-2"> |
| 4005 |
<a href="#appendix-A.2.3.2" class="section-number selfRef">A.2.3.2. </a><a href="#name-abstract-security-block-2" class="section-name selfRef">Abstract Security Block</a> |
| 4006 |
</h5> |
| 4007 |
<p id="appendix-A.2.3.2-1"> |
| 4008 |
The abstract security block structure of the BCB's |
| 4009 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.2.3.2-1" class="pilcrow">¶</a></p> |
| 4010 |
<span id="name-example-2-bcb-abstract-secu"></span><div id="ex2_bcb_asb"> |
| 4011 |
<figure id="figure-11"> |
| 4012 |
<div id="appendix-A.2.3.2-2.1"> |
| 4013 |
<pre class="lang-cbor-diag sourcecode"> |
| 4014 |
[1], / Security Target - Payload block / |
| 4015 |
2, / Security Context ID - BCB-AES-GCM / |
| 4016 |
1, / Security Context Flags - Parameters Present / |
| 4017 |
[2,[2, 1]], / Security Source - ipn:2.1 / |
| 4018 |
[ / Security Parameters - 4 Parameters / |
| 4019 |
[1, h'5477656c7665313231323132'], / Initialization Vector / |
| 4020 |
[2, 1], / AES Variant - A128GCM / |
| 4021 |
[3, h'69c411276fecddc4780df42c8a / AES wrapped key / |
| 4022 |
2af89296fabf34d7fae700'], |
| 4023 |
[4, 0x00] / Scope Flags - No extra scope/ |
| 4024 |
], |
| 4025 |
[ / Security Results: 1 Result / |
| 4026 |
[ / Target 1 Results / |
| 4027 |
[1, h'efa4b5ac0108e3816c5606479801bc04'] / Payload Auth. Tag / |
| 4028 |
] |
| 4029 |
] |
| 4030 |
</pre> |
| 4031 |
</div> |
| 4032 |
<figcaption><a href="#figure-11" class="selfRef">Figure 11</a>: |
| 4033 |
<a href="#name-example-2-bcb-abstract-secu" class="selfRef">Example 2 - BCB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 4034 |
</figcaption></figure> |
| 4035 |
</div> |
| 4036 |
<p id="appendix-A.2.3.2-3"> |
| 4037 |
The CBOR encoding of the BCB block-type-specific data field |
| 4038 |
(the abstract security block) is:<a href="#appendix-A.2.3.2-3" class="pilcrow">¶</a></p> |
| 4039 |
<div id="appendix-A.2.3.2-4"> |
| 4040 |
<pre class="sourcecode"> |
| 4041 |
0x8101020182028202018482014c5477656c76653132313231328202018203581869 |
| 4042 |
c411276fecddc4780df42c8a2af89296fabf34d7fae7008204008181820150efa4b5 |
| 4043 |
ac0108e3816c5606479801bc04 |
| 4044 |
</pre><a href="#appendix-A.2.3.2-4" class="pilcrow">¶</a> |
| 4045 |
</div> |
| 4046 |
</section> |
| 4047 |
<section id="appendix-A.2.3.3"> |
| 4048 |
<h5 id="name-representations-2"> |
| 4049 |
<a href="#appendix-A.2.3.3" class="section-number selfRef">A.2.3.3. </a><a href="#name-representations-2" class="section-name selfRef">Representations</a> |
| 4050 |
</h5> |
| 4051 |
<p id="appendix-A.2.3.3-1"> |
| 4052 |
The complete BCB is as follows.<a href="#appendix-A.2.3.3-1" class="pilcrow">¶</a></p> |
| 4053 |
<span id="name-example-2-bcb-cbor-diagnost"></span><div id="ex2_bcb"> |
| 4054 |
<figure id="figure-12"> |
| 4055 |
<div id="appendix-A.2.3.3-2.1"> |
| 4056 |
<pre class="lang-cbor-diag sourcecode"> |
| 4057 |
[ |
| 4058 |
12, / type code / |
| 4059 |
2, / block number / |
| 4060 |
1, / flags - block must be replicated in every fragment / |
| 4061 |
0, / CRC type / |
| 4062 |
h'8101020182028202018482014c5477656c766531323132313282020182035818 |
| 4063 |
69c411276fecddc4780df42c8a2af89296fabf34d7fae7008204008181820150 |
| 4064 |
efa4b5ac0108e3816c5606479801bc04' |
| 4065 |
] |
| 4066 |
</pre> |
| 4067 |
</div> |
| 4068 |
<figcaption><a href="#figure-12" class="selfRef">Figure 12</a>: |
| 4069 |
<a href="#name-example-2-bcb-cbor-diagnost" class="selfRef">Example 2 - BCB (CBOR Diagnostic Notation)</a> |
| 4070 |
</figcaption></figure> |
| 4071 |
</div> |
| 4072 |
<p id="appendix-A.2.3.3-3"> |
| 4073 |
The CBOR encoding of the BCB block is:<a href="#appendix-A.2.3.3-3" class="pilcrow">¶</a></p> |
| 4074 |
<div id="appendix-A.2.3.3-4"> |
| 4075 |
<pre class="sourcecode"> |
| 4076 |
0x850c02010058508101020182028202018482014c5477656c766531323132313282 |
| 4077 |
02018203581869c411276fecddc4780df42c8a2af89296fabf34d7fae70082040081 |
| 4078 |
81820150efa4b5ac0108e3816c5606479801bc04 |
| 4079 |
</pre><a href="#appendix-A.2.3.3-4" class="pilcrow">¶</a> |
| 4080 |
</div> |
| 4081 |
</section> |
| 4082 |
</section> |
| 4083 |
<section id="appendix-A.2.4"> |
| 4084 |
<h4 id="name-final-bundle-2"> |
| 4085 |
<a href="#appendix-A.2.4" class="section-number selfRef">A.2.4. </a><a href="#name-final-bundle-2" class="section-name selfRef">Final Bundle</a> |
| 4086 |
</h4> |
| 4087 |
<p id="appendix-A.2.4-1"> |
| 4088 |
The CBOR encoding of the full output bundle, with the BCB:<a href="#appendix-A.2.4-1" class="pilcrow">¶</a></p> |
| 4089 |
<div id="appendix-A.2.4-2"> |
| 4090 |
<pre class="sourcecode"> |
| 4091 |
0x9f88070000820282010282028202018202820201820018281a000f4240850c0201 |
| 4092 |
0058508101020182028202018482014c5477656c7665313231323132820201820358 |
| 4093 |
1869c411276fecddc4780df42c8a2af89296fabf34d7fae7008204008181820150ef |
| 4094 |
a4b5ac0108e3816c5606479801bc04850101000058233a09c1e63fe23a7f66a59c73 |
| 4095 |
03837241e070b02619fc59c5214a22f08cd70795e73e9aff |
| 4096 |
</pre><a href="#appendix-A.2.4-2" class="pilcrow">¶</a> |
| 4097 |
</div> |
| 4098 |
</section> |
| 4099 |
</section> |
| 4100 |
<section id="appendix-A.3"> |
| 4101 |
<h3 id="name-example-3-security-blocks-f"> |
| 4102 |
<a href="#appendix-A.3" class="section-number selfRef">A.3. </a><a href="#name-example-3-security-blocks-f" class="section-name selfRef">Example 3 - Security Blocks from Multiple Sources</a> |
| 4103 |
</h3> |
| 4104 |
<p id="appendix-A.3-1"> |
| 4105 |
This example shows the addition of a BIB and BCB to |
| 4106 |
a sample bundle. These two security blocks are added |
| 4107 |
by two different nodes. The BCB is added by the source |
| 4108 |
endpoint, and the BIB is added by a forwarding node.<a href="#appendix-A.3-1" class="pilcrow">¶</a></p> |
| 4109 |
<p id="appendix-A.3-2"> |
| 4110 |
The resulting bundle contains a BCB to encrypt the |
| 4111 |
Payload Block and a BIB to provide integrity to the |
| 4112 |
primary block and Bundle Age Block.<a href="#appendix-A.3-2" class="pilcrow">¶</a></p> |
| 4113 |
<section id="appendix-A.3.1"> |
| 4114 |
<h4 id="name-original-bundle-3"> |
| 4115 |
<a href="#appendix-A.3.1" class="section-number selfRef">A.3.1. </a><a href="#name-original-bundle-3" class="section-name selfRef">Original Bundle</a> |
| 4116 |
</h4> |
| 4117 |
<p id="appendix-A.3.1-1"> |
| 4118 |
The following diagram shows the original bundle before the |
| 4119 |
security blocks have been added.<a href="#appendix-A.3.1-1" class="pilcrow">¶</a></p> |
| 4120 |
<span id="name-example-3-original-bundle"></span><figure id="figure-13"> |
| 4121 |
<div class="alignCenter art-text artwork" id="appendix-A.3.1-2.1"> |
| 4122 |
<pre> |
| 4123 |
Block Block Block |
| 4124 |
in Bundle Type Number |
| 4125 |
+========================================+=======+========+ |
| 4126 |
| Primary Block | N/A | 0 | |
| 4127 |
+----------------------------------------+-------+--------+ |
| 4128 |
| Extension Block: Bundle Age Block | 7 | 2 | |
| 4129 |
+----------------------------------------+-------+--------+ |
| 4130 |
| Payload Block | 1 | 1 | |
| 4131 |
+----------------------------------------+-------+--------+ |
| 4132 |
</pre> |
| 4133 |
</div> |
| 4134 |
<figcaption><a href="#figure-13" class="selfRef">Figure 13</a>: |
| 4135 |
<a href="#name-example-3-original-bundle" class="selfRef">Example 3 - Original Bundle</a> |
| 4136 |
</figcaption></figure> |
| 4137 |
<section id="appendix-A.3.1.1"> |
| 4138 |
<h5 id="name-primary-block-3"> |
| 4139 |
<a href="#appendix-A.3.1.1" class="section-number selfRef">A.3.1.1. </a><a href="#name-primary-block-3" class="section-name selfRef">Primary Block</a> |
| 4140 |
</h5> |
| 4141 |
<p id="appendix-A.3.1.1-1"> |
| 4142 |
The primary block used in this example is identical to the primary block |
| 4143 |
presented for Example 1 in <a href="#ex_primary_block" class="xref">Appendix A.1.1.1</a>.<a href="#appendix-A.3.1.1-1" class="pilcrow">¶</a></p> |
| 4144 |
<p id="appendix-A.3.1.1-2"> |
| 4145 |
In summary, the CBOR encoding of the primary block is:<a href="#appendix-A.3.1.1-2" class="pilcrow">¶</a></p> |
| 4146 |
<div id="appendix-A.3.1.1-3"> |
| 4147 |
<pre class="sourcecode"> |
| 4148 |
0x88070000820282010282028202018202820201820018281a000f4240 |
| 4149 |
</pre><a href="#appendix-A.3.1.1-3" class="pilcrow">¶</a> |
| 4150 |
</div> |
| 4151 |
</section> |
| 4152 |
<section id="appendix-A.3.1.2"> |
| 4153 |
<h5 id="name-bundle-age-block"> |
| 4154 |
<a href="#appendix-A.3.1.2" class="section-number selfRef">A.3.1.2. </a><a href="#name-bundle-age-block" class="section-name selfRef">Bundle Age Block</a> |
| 4155 |
</h5> |
| 4156 |
<p id="appendix-A.3.1.2-1"> |
| 4157 |
A Bundle Age Block is added to the bundle to help other nodes in the |
| 4158 |
network determine the age of the bundle. The use of this block is |
| 4159 |
recommended because the bundle source does not have an accurate |
| 4160 |
clock (as indicated by the DTN time of 0).<a href="#appendix-A.3.1.2-1" class="pilcrow">¶</a></p> |
| 4161 |
<p id="appendix-A.3.1.2-2"> |
| 4162 |
Because this block is specified at the time the bundle is being |
| 4163 |
forwarded, the bundle age represents the time that has elapsed |
| 4164 |
from the time the bundle was created to the time it is being prepared |
| 4165 |
for forwarding. In this case, the value is given as 300 milliseconds.<a href="#appendix-A.3.1.2-2" class="pilcrow">¶</a></p> |
| 4166 |
<p id="appendix-A.3.1.2-3"> |
| 4167 |
The Bundle Age extension block is provided as follows.<a href="#appendix-A.3.1.2-3" class="pilcrow">¶</a></p> |
| 4168 |
<span id="name-bundle-age-block-cbor-diagn"></span><div id="ex_bdl_age"> |
| 4169 |
<figure id="figure-14"> |
| 4170 |
<div id="appendix-A.3.1.2-4.1"> |
| 4171 |
<pre class="lang-cbor-diag sourcecode"> |
| 4172 |
[ |
| 4173 |
7, / type code: Bundle Age Block / |
| 4174 |
2, / block number / |
| 4175 |
0, / block processing control flags / |
| 4176 |
0, / CRC type / |
| 4177 |
<<300>> / type-specific-data: age / |
| 4178 |
] |
| 4179 |
</pre> |
| 4180 |
</div> |
| 4181 |
<figcaption><a href="#figure-14" class="selfRef">Figure 14</a>: |
| 4182 |
<a href="#name-bundle-age-block-cbor-diagn" class="selfRef">Bundle Age Block (CBOR Diagnostic Notation)</a> |
| 4183 |
</figcaption></figure> |
| 4184 |
</div> |
| 4185 |
<p id="appendix-A.3.1.2-5"> |
| 4186 |
The CBOR encoding of the Bundle Age Block is:<a href="#appendix-A.3.1.2-5" class="pilcrow">¶</a></p> |
| 4187 |
<div id="appendix-A.3.1.2-6"> |
| 4188 |
<pre class="sourcecode"> |
| 4189 |
0x85070200004319012c |
| 4190 |
</pre><a href="#appendix-A.3.1.2-6" class="pilcrow">¶</a> |
| 4191 |
</div> |
| 4192 |
</section> |
| 4193 |
<section id="appendix-A.3.1.3"> |
| 4194 |
<h5 id="name-payload-block-3"> |
| 4195 |
<a href="#appendix-A.3.1.3" class="section-number selfRef">A.3.1.3. </a><a href="#name-payload-block-3" class="section-name selfRef">Payload Block</a> |
| 4196 |
</h5> |
| 4197 |
<p id="appendix-A.3.1.3-1"> |
| 4198 |
The payload block used in this example is identical to the payload block |
| 4199 |
presented for Example 1 in <a href="#ex_payload_block" class="xref">Appendix A.1.1.2</a>.<a href="#appendix-A.3.1.3-1" class="pilcrow">¶</a></p> |
| 4200 |
<p id="appendix-A.3.1.3-2"> |
| 4201 |
In summary, the CBOR encoding of the payload block is:<a href="#appendix-A.3.1.3-2" class="pilcrow">¶</a></p> |
| 4202 |
<div id="appendix-A.3.1.3-3"> |
| 4203 |
<pre class="sourcecode"> |
| 4204 |
0x85010100005823526561647920746f2067656e657261746520612033322d627974 |
| 4205 |
65207061796c6f6164 |
| 4206 |
</pre><a href="#appendix-A.3.1.3-3" class="pilcrow">¶</a> |
| 4207 |
</div> |
| 4208 |
</section> |
| 4209 |
<section id="appendix-A.3.1.4"> |
| 4210 |
<h5 id="name-bundle-cbor-representation-3"> |
| 4211 |
<a href="#appendix-A.3.1.4" class="section-number selfRef">A.3.1.4. </a><a href="#name-bundle-cbor-representation-3" class="section-name selfRef">Bundle CBOR Representation</a> |
| 4212 |
</h5> |
| 4213 |
<p id="appendix-A.3.1.4-1"> |
| 4214 |
A BPv7 bundle is represented as an indefinite-length array consisting |
| 4215 |
of the blocks comprising the bundle, with a terminator character at |
| 4216 |
the end.<a href="#appendix-A.3.1.4-1" class="pilcrow">¶</a></p> |
| 4217 |
<p id="appendix-A.3.1.4-2"> |
| 4218 |
The CBOR encoding of the original bundle is:<a href="#appendix-A.3.1.4-2" class="pilcrow">¶</a></p> |
| 4219 |
<div id="appendix-A.3.1.4-3"> |
| 4220 |
<pre class="sourcecode"> |
| 4221 |
0x9f88070000820282010282028202018202820201820018281a000f424085070200 |
| 4222 |
004319012c85010100005823526561647920746f2067656e65726174652061203332 |
| 4223 |
2d62797465207061796c6f6164ff |
| 4224 |
</pre><a href="#appendix-A.3.1.4-3" class="pilcrow">¶</a> |
| 4225 |
</div> |
| 4226 |
</section> |
| 4227 |
</section> |
| 4228 |
<section id="appendix-A.3.2"> |
| 4229 |
<h4 id="name-security-operation-overview-3"> |
| 4230 |
<a href="#appendix-A.3.2" class="section-number selfRef">A.3.2. </a><a href="#name-security-operation-overview-3" class="section-name selfRef">Security Operation Overview</a> |
| 4231 |
</h4> |
| 4232 |
<p id="appendix-A.3.2-1"> |
| 4233 |
This example provides:<a href="#appendix-A.3.2-1" class="pilcrow">¶</a></p> |
| 4234 |
<ul class="normal"> |
| 4235 |
<li class="normal" id="appendix-A.3.2-2.1"> |
| 4236 |
a BIB with the BIB-HMAC-SHA2 security context to provide an |
| 4237 |
integrity mechanism over the primary block and Bundle Age |
| 4238 |
Block.<a href="#appendix-A.3.2-2.1" class="pilcrow">¶</a> |
| 4239 |
</li> |
| 4240 |
<li class="normal" id="appendix-A.3.2-2.2"> |
| 4241 |
a BCB with the BCB-AES-GCM security context to provide a |
| 4242 |
confidentiality mechanism over the payload block.<a href="#appendix-A.3.2-2.2" class="pilcrow">¶</a> |
| 4243 |
</li> |
| 4244 |
</ul> |
| 4245 |
<p id="appendix-A.3.2-3"> |
| 4246 |
The following diagram shows the resulting bundle after the |
| 4247 |
security blocks are added.<a href="#appendix-A.3.2-3" class="pilcrow">¶</a></p> |
| 4248 |
<span id="name-example-3-resulting-bundle"></span><figure id="figure-15"> |
| 4249 |
<div class="alignCenter art-text artwork" id="appendix-A.3.2-4.1"> |
| 4250 |
<pre> |
| 4251 |
Block Block Block |
| 4252 |
in Bundle Type Number |
| 4253 |
+========================================+=======+========+ |
| 4254 |
| Primary Block | N/A | 0 | |
| 4255 |
+----------------------------------------+-------+--------+ |
| 4256 |
| Block Integrity Block | 11 | 3 | |
| 4257 |
| OP(bib-integrity, targets=0, 2) | | | |
| 4258 |
+----------------------------------------+-------+--------+ |
| 4259 |
| Block Confidentiality Block | 12 | 4 | |
| 4260 |
| OP(bcb-confidentiality, target=1) | | | |
| 4261 |
+----------------------------------------+-------+--------+ |
| 4262 |
| Extension Block: Bundle Age Block | 7 | 2 | |
| 4263 |
+----------------------------------------+-------+--------+ |
| 4264 |
| Payload Block (Encrypted) | 1 | 1 | |
| 4265 |
+----------------------------------------+-------+--------+ |
| 4266 |
</pre> |
| 4267 |
</div> |
| 4268 |
<figcaption><a href="#figure-15" class="selfRef">Figure 15</a>: |
| 4269 |
<a href="#name-example-3-resulting-bundle" class="selfRef">Example 3 - Resulting Bundle</a> |
| 4270 |
</figcaption></figure> |
| 4271 |
</section> |
| 4272 |
<section id="appendix-A.3.3"> |
| 4273 |
<h4 id="name-block-integrity-block-2"> |
| 4274 |
<a href="#appendix-A.3.3" class="section-number selfRef">A.3.3. </a><a href="#name-block-integrity-block-2" class="section-name selfRef">Block Integrity Block</a> |
| 4275 |
</h4> |
| 4276 |
<p id="appendix-A.3.3-1"> |
| 4277 |
In this example, a BIB is used to carry an integrity signature over |
| 4278 |
the Bundle Age Block and an additional signature over the |
| 4279 |
payload block. The BIB is added by a waypoint node -- ipn:3.0.<a href="#appendix-A.3.3-1" class="pilcrow">¶</a></p> |
| 4280 |
<section id="appendix-A.3.3.1"> |
| 4281 |
<h5 id="name-configuration-parameters-and-"> |
| 4282 |
<a href="#appendix-A.3.3.1" class="section-number selfRef">A.3.3.1. </a><a href="#name-configuration-parameters-and-" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 4283 |
</h5> |
| 4284 |
<p id="appendix-A.3.3.1-1"> |
| 4285 |
For this example, the following configuration and security context |
| 4286 |
parameters are used to generate the security results |
| 4287 |
indicated.<a href="#appendix-A.3.3.1-1" class="pilcrow">¶</a></p> |
| 4288 |
<p id="appendix-A.3.3.1-2"> |
| 4289 |
This BIB has two security targets and includes two |
| 4290 |
security results, holding the calculated signatures over |
| 4291 |
the Bundle Age Block and primary block.<a href="#appendix-A.3.3.1-2" class="pilcrow">¶</a></p> |
| 4292 |
<span id="name-example-3-configuration-par"></span><div id="ex3_bib_cpr"> |
| 4293 |
<figure id="figure-16"> |
| 4294 |
<div class="alignCenter art-text artwork" id="appendix-A.3.3.1-3.1"> |
| 4295 |
<pre> |
| 4296 |
Key: h'1a2b1a2b1a2b1a2b1a2b1a2b1a2b1a2b' |
| 4297 |
SHA Variant: HMAC 256/256 |
| 4298 |
Scope Flags: 0x00 |
| 4299 |
Primary Block Data: h'88070000820282010282028202018202 |
| 4300 |
820201820018281a000f4240' |
| 4301 |
Bundle Age Block |
| 4302 |
Data: h'4319012c' |
| 4303 |
Primary Block IPPT: h'00581c88070000820282010282028202 |
| 4304 |
018202820201820018281a000f4240' |
| 4305 |
Bundle Age Block |
| 4306 |
IPPT: h'004319012c' |
| 4307 |
Primary Block |
| 4308 |
Signature: h'cac6ce8e4c5dae57988b757e49a6dd14 |
| 4309 |
31dc04763541b2845098265bc817241b' |
| 4310 |
Bundle Age Block |
| 4311 |
Signature: h'3ed614c0d97f49b3633627779aa18a33 |
| 4312 |
8d212bf3c92b97759d9739cd50725596' |
| 4313 |
</pre> |
| 4314 |
</div> |
| 4315 |
<figcaption><a href="#figure-16" class="selfRef">Figure 16</a>: |
| 4316 |
<a href="#name-example-3-configuration-par" class="selfRef">Example 3 - Configuration, Parameters, and Results for the BIB</a> |
| 4317 |
</figcaption></figure> |
| 4318 |
</div> |
| 4319 |
</section> |
| 4320 |
<section id="appendix-A.3.3.2"> |
| 4321 |
<h5 id="name-abstract-security-block-3"> |
| 4322 |
<a href="#appendix-A.3.3.2" class="section-number selfRef">A.3.3.2. </a><a href="#name-abstract-security-block-3" class="section-name selfRef">Abstract Security Block</a> |
| 4323 |
</h5> |
| 4324 |
<p id="appendix-A.3.3.2-1"> |
| 4325 |
The abstract security block structure of the BIB's |
| 4326 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.3.3.2-1" class="pilcrow">¶</a></p> |
| 4327 |
<span id="name-example-3-bib-abstract-secu"></span><div id="ex3_bib_asb"> |
| 4328 |
<figure id="figure-17"> |
| 4329 |
<div id="appendix-A.3.3.2-2.1"> |
| 4330 |
<pre class="lang-cbor-diag sourcecode"> |
| 4331 |
[0, 2], / Security Targets / |
| 4332 |
1, / Security Context ID - BIB-HMAC-SHA2 / |
| 4333 |
1, / Security Context Flags - Parameters Present / |
| 4334 |
[2,[3, 0]], / Security Source - ipn:3.0 / |
| 4335 |
[ / Security Parameters - 2 Parameters / |
| 4336 |
[1, 5], / SHA Variant - HMAC 256 / |
| 4337 |
[3, 0] / Scope Flags - No Additional Scope / |
| 4338 |
], |
| 4339 |
[ / Security Results: 2 Results / |
| 4340 |
[ / Primary Block Results / |
| 4341 |
[1, h'cac6ce8e4c5dae57988b757e49a6dd14 |
| 4342 |
31dc04763541b2845098265bc817241b'] / MAC / |
| 4343 |
], |
| 4344 |
[ / Bundle Age Block Results / |
| 4345 |
[1, h'3ed614c0d97f49b3633627779aa18a33 |
| 4346 |
8d212bf3c92b97759d9739cd50725596'] / MAC / |
| 4347 |
] |
| 4348 |
] |
| 4349 |
</pre> |
| 4350 |
</div> |
| 4351 |
<figcaption><a href="#figure-17" class="selfRef">Figure 17</a>: |
| 4352 |
<a href="#name-example-3-bib-abstract-secu" class="selfRef">Example 3 - BIB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 4353 |
</figcaption></figure> |
| 4354 |
</div> |
| 4355 |
<p id="appendix-A.3.3.2-3"> |
| 4356 |
The CBOR encoding of the BIB block-type-specific data field (the abstract security block) is:<a href="#appendix-A.3.3.2-3" class="pilcrow">¶</a></p> |
| 4357 |
<div id="appendix-A.3.3.2-4"> |
| 4358 |
<pre class="sourcecode"> |
| 4359 |
0x8200020101820282030082820105820300828182015820cac6ce8e4c5dae57988b |
| 4360 |
757e49a6dd1431dc04763541b2845098265bc817241b81820158203ed614c0d97f49 |
| 4361 |
b3633627779aa18a338d212bf3c92b97759d9739cd50725596 |
| 4362 |
</pre><a href="#appendix-A.3.3.2-4" class="pilcrow">¶</a> |
| 4363 |
</div> |
| 4364 |
</section> |
| 4365 |
<section id="appendix-A.3.3.3"> |
| 4366 |
<h5 id="name-representations-3"> |
| 4367 |
<a href="#appendix-A.3.3.3" class="section-number selfRef">A.3.3.3. </a><a href="#name-representations-3" class="section-name selfRef">Representations</a> |
| 4368 |
</h5> |
| 4369 |
<p id="appendix-A.3.3.3-1"> |
| 4370 |
The complete BIB is as follows.<a href="#appendix-A.3.3.3-1" class="pilcrow">¶</a></p> |
| 4371 |
<span id="name-example-3-bib-cbor-diagnost"></span><div id="ex3_bib"> |
| 4372 |
<figure id="figure-18"> |
| 4373 |
<div id="appendix-A.3.3.3-2.1"> |
| 4374 |
<pre class="lang-cbor-diag sourcecode"> |
| 4375 |
[ |
| 4376 |
11, / type code / |
| 4377 |
3, / block number / |
| 4378 |
0, / flags / |
| 4379 |
0, / CRC type / |
| 4380 |
h'8200020101820282030082820105820300828182015820cac6ce8e4c5dae5798 |
| 4381 |
8b757e49a6dd1431dc04763541b2845098265bc817241b81820158203ed614c0d9 |
| 4382 |
7f49b3633627779aa18a338d212bf3c92b97759d9739cd50725596' |
| 4383 |
] |
| 4384 |
</pre> |
| 4385 |
</div> |
| 4386 |
<figcaption><a href="#figure-18" class="selfRef">Figure 18</a>: |
| 4387 |
<a href="#name-example-3-bib-cbor-diagnost" class="selfRef">Example 3 - BIB (CBOR Diagnostic Notation)</a> |
| 4388 |
</figcaption></figure> |
| 4389 |
</div> |
| 4390 |
<p id="appendix-A.3.3.3-3"> |
| 4391 |
The CBOR encoding of the BIB block is:<a href="#appendix-A.3.3.3-3" class="pilcrow">¶</a></p> |
| 4392 |
<div id="appendix-A.3.3.3-4"> |
| 4393 |
<pre class="sourcecode"> |
| 4394 |
0x850b030000585c8200020101820282030082820105820300828182015820cac6ce |
| 4395 |
8e4c5dae57988b757e49a6dd1431dc04763541b2845098265bc817241b8182015820 |
| 4396 |
3ed614c0d97f49b3633627779aa18a338d212bf3c92b97759d9739cd50725596 |
| 4397 |
</pre><a href="#appendix-A.3.3.3-4" class="pilcrow">¶</a> |
| 4398 |
</div> |
| 4399 |
</section> |
| 4400 |
</section> |
| 4401 |
<section id="appendix-A.3.4"> |
| 4402 |
<h4 id="name-block-confidentiality-block-2"> |
| 4403 |
<a href="#appendix-A.3.4" class="section-number selfRef">A.3.4. </a><a href="#name-block-confidentiality-block-2" class="section-name selfRef">Block Confidentiality Block</a> |
| 4404 |
</h4> |
| 4405 |
<p id="appendix-A.3.4-1"> |
| 4406 |
In this example, a BCB is used encrypt the payload |
| 4407 |
block. The BCB is added by the bundle source node, ipn:2.1.<a href="#appendix-A.3.4-1" class="pilcrow">¶</a></p> |
| 4408 |
<section id="appendix-A.3.4.1"> |
| 4409 |
<h5 id="name-configuration-parameters-and-r"> |
| 4410 |
<a href="#appendix-A.3.4.1" class="section-number selfRef">A.3.4.1. </a><a href="#name-configuration-parameters-and-r" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 4411 |
</h5> |
| 4412 |
<p id="appendix-A.3.4.1-1"> |
| 4413 |
For this example, the following configuration and security context |
| 4414 |
parameters are used to generate the security results |
| 4415 |
indicated.<a href="#appendix-A.3.4.1-1" class="pilcrow">¶</a></p> |
| 4416 |
<p id="appendix-A.3.4.1-2"> |
| 4417 |
This BCB has a single target, the payload block. |
| 4418 |
Two security results are generated: ciphertext that |
| 4419 |
replaces the plaintext block-type-specific data to |
| 4420 |
encrypt the payload block and an authentication tag.<a href="#appendix-A.3.4.1-2" class="pilcrow">¶</a></p> |
| 4421 |
<span id="name-example-3-configuration-para"></span><div id="ex3_bcb_cpr"> |
| 4422 |
<figure id="figure-19"> |
| 4423 |
<div class="alignCenter art-text artwork" id="appendix-A.3.4.1-3.1"> |
| 4424 |
<pre> |
| 4425 |
Content Encryption |
| 4426 |
Key: h'71776572747975696f70617364666768' |
| 4427 |
IV: h'5477656c7665313231323132' |
| 4428 |
AES Variant: A128GCM |
| 4429 |
Scope Flags: 0x00 |
| 4430 |
Payload Data: h'526561647920746f2067656e65726174 |
| 4431 |
6520612033322d62797465207061796c |
| 4432 |
6f6164' |
| 4433 |
AAD: h'00' |
| 4434 |
Authentication Tag: h'efa4b5ac0108e3816c5606479801bc04' |
| 4435 |
Payload Ciphertext: h'3a09c1e63fe23a7f66a59c7303837241 |
| 4436 |
e070b02619fc59c5214a22f08cd70795 |
| 4437 |
e73e9a' |
| 4438 |
</pre> |
| 4439 |
</div> |
| 4440 |
<figcaption><a href="#figure-19" class="selfRef">Figure 19</a>: |
| 4441 |
<a href="#name-example-3-configuration-para" class="selfRef">Example 3 - Configuration, Parameters, and Results for the BCB</a> |
| 4442 |
</figcaption></figure> |
| 4443 |
</div> |
| 4444 |
</section> |
| 4445 |
<section id="appendix-A.3.4.2"> |
| 4446 |
<h5 id="name-abstract-security-block-4"> |
| 4447 |
<a href="#appendix-A.3.4.2" class="section-number selfRef">A.3.4.2. </a><a href="#name-abstract-security-block-4" class="section-name selfRef">Abstract Security Block</a> |
| 4448 |
</h5> |
| 4449 |
<p id="appendix-A.3.4.2-1"> |
| 4450 |
The abstract security block structure of the BCB's |
| 4451 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.3.4.2-1" class="pilcrow">¶</a></p> |
| 4452 |
<span id="name-example-3-bcb-abstract-secu"></span><div id="ex3_bcb_asb"> |
| 4453 |
<figure id="figure-20"> |
| 4454 |
<div id="appendix-A.3.4.2-2.1"> |
| 4455 |
<pre class="lang-cbor-diag sourcecode"> |
| 4456 |
[1], / Security Target - Payload block / |
| 4457 |
2, / Security Context ID - BCB-AES-GCM / |
| 4458 |
1, / Security Context Flags - Parameters Present / |
| 4459 |
[2,[2, 1]], / Security Source - ipn:2.1 / |
| 4460 |
[ / Security Parameters - 3 Parameters / |
| 4461 |
[1, h'5477656c7665313231323132'], / Initialization Vector / |
| 4462 |
[2, 1], / AES Variant - AES 128 / |
| 4463 |
[4, 0] / Scope Flags - No Additional Scope / |
| 4464 |
], |
| 4465 |
[ / Security Results: 1 Result / |
| 4466 |
[ |
| 4467 |
[1, h'efa4b5ac0108e3816c5606479801bc04'] / Payload Auth. Tag / |
| 4468 |
] |
| 4469 |
] |
| 4470 |
</pre> |
| 4471 |
</div> |
| 4472 |
<figcaption><a href="#figure-20" class="selfRef">Figure 20</a>: |
| 4473 |
<a href="#name-example-3-bcb-abstract-secu" class="selfRef">Example 3 - BCB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 4474 |
</figcaption></figure> |
| 4475 |
</div> |
| 4476 |
<p id="appendix-A.3.4.2-3"> |
| 4477 |
The CBOR encoding of the BCB block-type-specific data field |
| 4478 |
(the abstract security block) is:<a href="#appendix-A.3.4.2-3" class="pilcrow">¶</a></p> |
| 4479 |
<div id="appendix-A.3.4.2-4"> |
| 4480 |
<pre class="sourcecode"> |
| 4481 |
0x8101020182028202018382014c5477656c76653132313231328202018204008181 |
| 4482 |
820150efa4b5ac0108e3816c5606479801bc04 |
| 4483 |
</pre><a href="#appendix-A.3.4.2-4" class="pilcrow">¶</a> |
| 4484 |
</div> |
| 4485 |
</section> |
| 4486 |
<section id="appendix-A.3.4.3"> |
| 4487 |
<h5 id="name-representations-4"> |
| 4488 |
<a href="#appendix-A.3.4.3" class="section-number selfRef">A.3.4.3. </a><a href="#name-representations-4" class="section-name selfRef">Representations</a> |
| 4489 |
</h5> |
| 4490 |
<p id="appendix-A.3.4.3-1"> |
| 4491 |
The complete BCB is as follows.<a href="#appendix-A.3.4.3-1" class="pilcrow">¶</a></p> |
| 4492 |
<span id="name-example-3-bcb-cbor-diagnost"></span><div id="ex3_bcb"> |
| 4493 |
<figure id="figure-21"> |
| 4494 |
<div id="appendix-A.3.4.3-2.1"> |
| 4495 |
<pre class="lang-cbor-diag sourcecode"> |
| 4496 |
[ |
| 4497 |
12, / type code / |
| 4498 |
4, / block number / |
| 4499 |
1, / flags - block must be replicated in every fragment / |
| 4500 |
0, / CRC type / |
| 4501 |
h'8101020182028202018382014c5477656c766531323132313282020182040081 |
| 4502 |
81820150efa4b5ac0108e3816c5606479801bc04' |
| 4503 |
] |
| 4504 |
</pre> |
| 4505 |
</div> |
| 4506 |
<figcaption><a href="#figure-21" class="selfRef">Figure 21</a>: |
| 4507 |
<a href="#name-example-3-bcb-cbor-diagnost" class="selfRef">Example 3 - BCB (CBOR Diagnostic Notation)</a> |
| 4508 |
</figcaption></figure> |
| 4509 |
</div> |
| 4510 |
<p id="appendix-A.3.4.3-3"> |
| 4511 |
The CBOR encoding of the BCB block is:<a href="#appendix-A.3.4.3-3" class="pilcrow">¶</a></p> |
| 4512 |
<div id="appendix-A.3.4.3-4"> |
| 4513 |
<pre class="sourcecode"> |
| 4514 |
0x850c04010058348101020182028202018382014c5477656c766531323132313282 |
| 4515 |
02018204008181820150efa4b5ac0108e3816c5606479801bc04 |
| 4516 |
</pre><a href="#appendix-A.3.4.3-4" class="pilcrow">¶</a> |
| 4517 |
</div> |
| 4518 |
</section> |
| 4519 |
</section> |
| 4520 |
<section id="appendix-A.3.5"> |
| 4521 |
<h4 id="name-final-bundle-3"> |
| 4522 |
<a href="#appendix-A.3.5" class="section-number selfRef">A.3.5. </a><a href="#name-final-bundle-3" class="section-name selfRef">Final Bundle</a> |
| 4523 |
</h4> |
| 4524 |
<p id="appendix-A.3.5-1"> |
| 4525 |
The CBOR encoding of the full output bundle, with the BIB and BCB added is:<a href="#appendix-A.3.5-1" class="pilcrow">¶</a></p> |
| 4526 |
<div id="appendix-A.3.5-2"> |
| 4527 |
<pre class="sourcecode"> |
| 4528 |
0x9f88070000820282010282028202018202820201820018281a000f4240850b0300 |
| 4529 |
00585c8200020101820282030082820105820300828182015820cac6ce8e4c5dae57 |
| 4530 |
988b757e49a6dd1431dc04763541b2845098265bc817241b81820158203ed614c0d9 |
| 4531 |
7f49b3633627779aa18a338d212bf3c92b97759d9739cd50725596850c0401005834 |
| 4532 |
8101020182028202018382014c5477656c7665313231323132820201820400818182 |
| 4533 |
0150efa4b5ac0108e3816c5606479801bc0485070200004319012c85010100005823 |
| 4534 |
3a09c1e63fe23a7f66a59c7303837241e070b02619fc59c5214a22f08cd70795e73e |
| 4535 |
9aff |
| 4536 |
</pre><a href="#appendix-A.3.5-2" class="pilcrow">¶</a> |
| 4537 |
</div> |
| 4538 |
</section> |
| 4539 |
</section> |
| 4540 |
<section id="appendix-A.4"> |
| 4541 |
<h3 id="name-example-4-security-blocks-w"> |
| 4542 |
<a href="#appendix-A.4" class="section-number selfRef">A.4. </a><a href="#name-example-4-security-blocks-w" class="section-name selfRef">Example 4 - Security Blocks with Full Scope</a> |
| 4543 |
</h3> |
| 4544 |
<p id="appendix-A.4-1"> |
| 4545 |
This example shows the addition of a BIB and BCB to |
| 4546 |
a sample bundle. A BIB is added to provide integrity |
| 4547 |
over the payload block, and a BCB is added for |
| 4548 |
confidentiality over the payload and BIB.<a href="#appendix-A.4-1" class="pilcrow">¶</a></p> |
| 4549 |
<p id="appendix-A.4-2"> |
| 4550 |
The integrity scope and additional authentication data |
| 4551 |
will bind the primary block, target header, and the |
| 4552 |
security header.<a href="#appendix-A.4-2" class="pilcrow">¶</a></p> |
| 4553 |
<section id="appendix-A.4.1"> |
| 4554 |
<h4 id="name-original-bundle-4"> |
| 4555 |
<a href="#appendix-A.4.1" class="section-number selfRef">A.4.1. </a><a href="#name-original-bundle-4" class="section-name selfRef">Original Bundle</a> |
| 4556 |
</h4> |
| 4557 |
<p id="appendix-A.4.1-1"> |
| 4558 |
The following diagram shows the original bundle before the |
| 4559 |
security blocks have been added.<a href="#appendix-A.4.1-1" class="pilcrow">¶</a></p> |
| 4560 |
<span id="name-example-4-original-bundle"></span><figure id="figure-22"> |
| 4561 |
<div class="alignCenter art-text artwork" id="appendix-A.4.1-2.1"> |
| 4562 |
<pre> |
| 4563 |
Block Block Block |
| 4564 |
in Bundle Type Number |
| 4565 |
+========================================+=======+========+ |
| 4566 |
| Primary Block | N/A | 0 | |
| 4567 |
+----------------------------------------+-------+--------+ |
| 4568 |
| Payload Block | 1 | 1 | |
| 4569 |
+----------------------------------------+-------+--------+ |
| 4570 |
</pre> |
| 4571 |
</div> |
| 4572 |
<figcaption><a href="#figure-22" class="selfRef">Figure 22</a>: |
| 4573 |
<a href="#name-example-4-original-bundle" class="selfRef">Example 4 - Original Bundle</a> |
| 4574 |
</figcaption></figure> |
| 4575 |
<section id="appendix-A.4.1.1"> |
| 4576 |
<h5 id="name-primary-block-4"> |
| 4577 |
<a href="#appendix-A.4.1.1" class="section-number selfRef">A.4.1.1. </a><a href="#name-primary-block-4" class="section-name selfRef">Primary Block</a> |
| 4578 |
</h5> |
| 4579 |
<p id="appendix-A.4.1.1-1"> |
| 4580 |
The primary block used in this example is identical to the primary block |
| 4581 |
presented for Example 1 in <a href="#ex_primary_block" class="xref">Appendix A.1.1.1</a>.<a href="#appendix-A.4.1.1-1" class="pilcrow">¶</a></p> |
| 4582 |
<p id="appendix-A.4.1.1-2"> |
| 4583 |
In summary, the CBOR encoding of the primary block is:<a href="#appendix-A.4.1.1-2" class="pilcrow">¶</a></p> |
| 4584 |
<div id="appendix-A.4.1.1-3"> |
| 4585 |
<pre class="sourcecode"> |
| 4586 |
0x88070000820282010282028202018202820201820018281a000f4240 |
| 4587 |
</pre><a href="#appendix-A.4.1.1-3" class="pilcrow">¶</a> |
| 4588 |
</div> |
| 4589 |
</section> |
| 4590 |
<section id="appendix-A.4.1.2"> |
| 4591 |
<h5 id="name-payload-block-4"> |
| 4592 |
<a href="#appendix-A.4.1.2" class="section-number selfRef">A.4.1.2. </a><a href="#name-payload-block-4" class="section-name selfRef">Payload Block</a> |
| 4593 |
</h5> |
| 4594 |
<p id="appendix-A.4.1.2-1"> |
| 4595 |
The payload block used in this example is identical to the payload block |
| 4596 |
presented for Example 1 in <a href="#ex_payload_block" class="xref">Appendix A.1.1.2</a>.<a href="#appendix-A.4.1.2-1" class="pilcrow">¶</a></p> |
| 4597 |
<p id="appendix-A.4.1.2-2"> |
| 4598 |
In summary, the CBOR encoding of the payload block is:<a href="#appendix-A.4.1.2-2" class="pilcrow">¶</a></p> |
| 4599 |
<div id="appendix-A.4.1.2-3"> |
| 4600 |
<pre class="sourcecode"> |
| 4601 |
0x85010100005823526561647920746f2067656e657261746520612033322d627974 |
| 4602 |
65207061796c6f6164 |
| 4603 |
</pre><a href="#appendix-A.4.1.2-3" class="pilcrow">¶</a> |
| 4604 |
</div> |
| 4605 |
</section> |
| 4606 |
<section id="appendix-A.4.1.3"> |
| 4607 |
<h5 id="name-bundle-cbor-representation-4"> |
| 4608 |
<a href="#appendix-A.4.1.3" class="section-number selfRef">A.4.1.3. </a><a href="#name-bundle-cbor-representation-4" class="section-name selfRef">Bundle CBOR Representation</a> |
| 4609 |
</h5> |
| 4610 |
<p id="appendix-A.4.1.3-1"> |
| 4611 |
A BPv7 bundle is represented as an indefinite-length array consisting |
| 4612 |
of the blocks comprising the bundle, with a terminator character at |
| 4613 |
the end.<a href="#appendix-A.4.1.3-1" class="pilcrow">¶</a></p> |
| 4614 |
<p id="appendix-A.4.1.3-2"> |
| 4615 |
The CBOR encoding of the original bundle is:<a href="#appendix-A.4.1.3-2" class="pilcrow">¶</a></p> |
| 4616 |
<div id="appendix-A.4.1.3-3"> |
| 4617 |
<pre class="sourcecode"> |
| 4618 |
0x9f88070000820282010282028202018202820201820018281a000f424085010100 |
| 4619 |
005823526561647920746f2067656e657261746520612033322d6279746520706179 |
| 4620 |
6c6f6164ff |
| 4621 |
</pre><a href="#appendix-A.4.1.3-3" class="pilcrow">¶</a> |
| 4622 |
</div> |
| 4623 |
</section> |
| 4624 |
</section> |
| 4625 |
<section id="appendix-A.4.2"> |
| 4626 |
<h4 id="name-security-operation-overview-4"> |
| 4627 |
<a href="#appendix-A.4.2" class="section-number selfRef">A.4.2. </a><a href="#name-security-operation-overview-4" class="section-name selfRef">Security Operation Overview</a> |
| 4628 |
</h4> |
| 4629 |
<p id="appendix-A.4.2-1"> |
| 4630 |
This example provides:<a href="#appendix-A.4.2-1" class="pilcrow">¶</a></p> |
| 4631 |
<ul class="normal"> |
| 4632 |
<li class="normal" id="appendix-A.4.2-2.1"> |
| 4633 |
a BIB with the BIB-HMAC-SHA2 security context to provide an |
| 4634 |
integrity mechanism over the payload block.<a href="#appendix-A.4.2-2.1" class="pilcrow">¶</a> |
| 4635 |
</li> |
| 4636 |
<li class="normal" id="appendix-A.4.2-2.2"> |
| 4637 |
a BCB with the BCB-AES-GCM security context to provide a |
| 4638 |
confidentiality mechanism over the payload block and BIB.<a href="#appendix-A.4.2-2.2" class="pilcrow">¶</a> |
| 4639 |
</li> |
| 4640 |
</ul> |
| 4641 |
<p id="appendix-A.4.2-3"> |
| 4642 |
The following diagram shows the resulting bundle after the |
| 4643 |
security blocks are added.<a href="#appendix-A.4.2-3" class="pilcrow">¶</a></p> |
| 4644 |
<span id="name-example-4-resulting-bundle"></span><figure id="figure-23"> |
| 4645 |
<div class="alignCenter art-text artwork" id="appendix-A.4.2-4.1"> |
| 4646 |
<pre> |
| 4647 |
Block Block Block |
| 4648 |
in Bundle Type Number |
| 4649 |
+========================================+=======+========+ |
| 4650 |
| Primary Block | N/A | 0 | |
| 4651 |
+----------------------------------------+-------+--------+ |
| 4652 |
| Block Integrity Block (Encrypted) | 11 | 3 | |
| 4653 |
| OP(bib-integrity, target=1) | | | |
| 4654 |
+----------------------------------------+-------+--------+ |
| 4655 |
| Block Confidentiality Block | 12 | 2 | |
| 4656 |
| OP(bcb-confidentiality, targets=1, 3) | | | |
| 4657 |
+----------------------------------------+-------+--------+ |
| 4658 |
| Payload Block (Encrypted) | 1 | 1 | |
| 4659 |
+----------------------------------------+-------+--------+ |
| 4660 |
</pre> |
| 4661 |
</div> |
| 4662 |
<figcaption><a href="#figure-23" class="selfRef">Figure 23</a>: |
| 4663 |
<a href="#name-example-4-resulting-bundle" class="selfRef">Example 4 - Resulting Bundle</a> |
| 4664 |
</figcaption></figure> |
| 4665 |
</section> |
| 4666 |
<section id="appendix-A.4.3"> |
| 4667 |
<h4 id="name-block-integrity-block-3"> |
| 4668 |
<a href="#appendix-A.4.3" class="section-number selfRef">A.4.3. </a><a href="#name-block-integrity-block-3" class="section-name selfRef">Block Integrity Block</a> |
| 4669 |
</h4> |
| 4670 |
<p id="appendix-A.4.3-1"> |
| 4671 |
In this example, a BIB is used to carry an integrity signature over |
| 4672 |
the payload block. The IPPT contains the block-type-specific data |
| 4673 |
of the payload block, the primary block data, the payload block |
| 4674 |
header, and the BIB header. That is, all additional headers are |
| 4675 |
included in the IPPT.<a href="#appendix-A.4.3-1" class="pilcrow">¶</a></p> |
| 4676 |
<section id="appendix-A.4.3.1"> |
| 4677 |
<h5 id="name-configuration-parameters-and-re"> |
| 4678 |
<a href="#appendix-A.4.3.1" class="section-number selfRef">A.4.3.1. </a><a href="#name-configuration-parameters-and-re" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 4679 |
</h5> |
| 4680 |
<p id="appendix-A.4.3.1-1"> |
| 4681 |
For this example, the following configuration and security context |
| 4682 |
parameters are used to generate the security results |
| 4683 |
indicated.<a href="#appendix-A.4.3.1-1" class="pilcrow">¶</a></p> |
| 4684 |
<p id="appendix-A.4.3.1-2"> |
| 4685 |
This BIB has a single target and includes a single security |
| 4686 |
result: the calculated signature over the Payload block.<a href="#appendix-A.4.3.1-2" class="pilcrow">¶</a></p> |
| 4687 |
<span id="name-example-4-configuration-par"></span><div id="ex4_bib_cpr"> |
| 4688 |
<figure id="figure-24"> |
| 4689 |
<div class="alignCenter art-text artwork" id="appendix-A.4.3.1-3.1"> |
| 4690 |
<pre> |
| 4691 |
Key: h'1a2b1a2b1a2b1a2b1a2b1a2b1a2b1a2b' |
| 4692 |
SHA Variant: HMAC 384/384 |
| 4693 |
Scope Flags: 0x07 (all additional headers) |
| 4694 |
Primary Block Data: h'88070000820282010282028202018202 |
| 4695 |
820201820018281a000f4240' |
| 4696 |
Payload Data: h'526561647920746f2067656e65726174 |
| 4697 |
6520612033322d62797465207061796c |
| 4698 |
6f6164' |
| 4699 |
Payload Header: h'010100' |
| 4700 |
BIB Header: h'0b0300' |
| 4701 |
IPPT: h'07880700008202820102820282020182 |
| 4702 |
02820201820018281a000f4240010100 |
| 4703 |
0b03005823526561647920746f206765 |
| 4704 |
6e657261746520612033322d62797465 |
| 4705 |
207061796c6f6164' |
| 4706 |
Payload Signature: h'f75fe4c37f76f046165855bd5ff72fbf |
| 4707 |
d4e3a64b4695c40e2b787da005ae819f |
| 4708 |
0a2e30a2e8b325527de8aefb52e73d71, |
| 4709 |
</pre> |
| 4710 |
</div> |
| 4711 |
<figcaption><a href="#figure-24" class="selfRef">Figure 24</a>: |
| 4712 |
<a href="#name-example-4-configuration-par" class="selfRef">Example 4 - Configuration, Parameters, and Results for the BIB</a> |
| 4713 |
</figcaption></figure> |
| 4714 |
</div> |
| 4715 |
</section> |
| 4716 |
<section id="appendix-A.4.3.2"> |
| 4717 |
<h5 id="name-abstract-security-block-5"> |
| 4718 |
<a href="#appendix-A.4.3.2" class="section-number selfRef">A.4.3.2. </a><a href="#name-abstract-security-block-5" class="section-name selfRef">Abstract Security Block</a> |
| 4719 |
</h5> |
| 4720 |
<p id="appendix-A.4.3.2-1"> |
| 4721 |
The abstract security block structure of the BIB's |
| 4722 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.4.3.2-1" class="pilcrow">¶</a></p> |
| 4723 |
<span id="name-example-4-bib-abstract-secu"></span><div id="ex4_bib_asb"> |
| 4724 |
<figure id="figure-25"> |
| 4725 |
<div id="appendix-A.4.3.2-2.1"> |
| 4726 |
<pre class="lang-cbor-diag sourcecode"> |
| 4727 |
[1], / Security Target - Payload block / |
| 4728 |
1, / Security Context ID - BIB-HMAC-SHA2 / |
| 4729 |
1, / Security Context Flags - Parameters Present / |
| 4730 |
[2,[2, 1]], / Security Source - ipn:2.1 / |
| 4731 |
[ / Security Parameters - 2 Parameters / |
| 4732 |
[1, 6], / SHA Variant - HMAC 384/384 / |
| 4733 |
[3, 0x07] / Scope Flags - All additional headers / |
| 4734 |
], |
| 4735 |
[ / Security Results: 1 Result / |
| 4736 |
[ / Target 1 Results / |
| 4737 |
[1, h'f75fe4c37f76f046165855bd5ff72fbf / MAC / |
| 4738 |
d4e3a64b4695c40e2b787da005ae819f |
| 4739 |
0a2e30a2e8b325527de8aefb52e73d71'] |
| 4740 |
] |
| 4741 |
] |
| 4742 |
</pre> |
| 4743 |
</div> |
| 4744 |
<figcaption><a href="#figure-25" class="selfRef">Figure 25</a>: |
| 4745 |
<a href="#name-example-4-bib-abstract-secu" class="selfRef">Example 4 - BIB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 4746 |
</figcaption></figure> |
| 4747 |
</div> |
| 4748 |
<p id="appendix-A.4.3.2-3"> |
| 4749 |
|
| 4750 |
The CBOR encoding of the BIB block-type-specific data field (the abstract security block) is:<a href="#appendix-A.4.3.2-3" class="pilcrow">¶</a></p> |
| 4751 |
<div id="appendix-A.4.3.2-4"> |
| 4752 |
<pre class="sourcecode"> |
| 4753 |
0x81010101820282020182820106820307818182015830f75fe4c37f76f046165855 |
| 4754 |
bd5ff72fbfd4e3a64b4695c40e2b787da005ae819f0a2e30a2e8b325527de8aefb52 |
| 4755 |
e73d71 |
| 4756 |
</pre><a href="#appendix-A.4.3.2-4" class="pilcrow">¶</a> |
| 4757 |
</div> |
| 4758 |
</section> |
| 4759 |
<section id="appendix-A.4.3.3"> |
| 4760 |
<h5 id="name-representations-5"> |
| 4761 |
<a href="#appendix-A.4.3.3" class="section-number selfRef">A.4.3.3. </a><a href="#name-representations-5" class="section-name selfRef">Representations</a> |
| 4762 |
</h5> |
| 4763 |
<p id="appendix-A.4.3.3-1"> |
| 4764 |
The complete BIB is as follows.<a href="#appendix-A.4.3.3-1" class="pilcrow">¶</a></p> |
| 4765 |
<span id="name-example-4-bib-cbor-diagnost"></span><div id="ex4_bib"> |
| 4766 |
<figure id="figure-26"> |
| 4767 |
<div id="appendix-A.4.3.3-2.1"> |
| 4768 |
<pre class="lang-cbor-diag sourcecode"> |
| 4769 |
[ |
| 4770 |
11, / type code / |
| 4771 |
3, / block number / |
| 4772 |
0, / flags / |
| 4773 |
0, / CRC type / |
| 4774 |
h'81010101820282020182820106820307818182015830f75fe4c37f76f0461658 |
| 4775 |
55bd5ff72fbfd4e3a64b4695c40e2b787da005ae819f0a2e30a2e8b325527de8 |
| 4776 |
aefb52e73d71' |
| 4777 |
] |
| 4778 |
</pre> |
| 4779 |
</div> |
| 4780 |
<figcaption><a href="#figure-26" class="selfRef">Figure 26</a>: |
| 4781 |
<a href="#name-example-4-bib-cbor-diagnost" class="selfRef">Example 4 - BIB (CBOR Diagnostic Notation)</a> |
| 4782 |
</figcaption></figure> |
| 4783 |
</div> |
| 4784 |
<p id="appendix-A.4.3.3-3"> |
| 4785 |
The CBOR encoding of the BIB block is:<a href="#appendix-A.4.3.3-3" class="pilcrow">¶</a></p> |
| 4786 |
<div id="appendix-A.4.3.3-4"> |
| 4787 |
<pre class="sourcecode"> |
| 4788 |
0x850b030000584681010101820282020182820106820307818182015830f75fe4c3 |
| 4789 |
7f76f046165855bd5ff72fbfd4e3a64b4695c40e2b787da005ae819f0a2e30a2e8b3 |
| 4790 |
25527de8aefb52e73d71 |
| 4791 |
</pre><a href="#appendix-A.4.3.3-4" class="pilcrow">¶</a> |
| 4792 |
</div> |
| 4793 |
</section> |
| 4794 |
</section> |
| 4795 |
<section id="appendix-A.4.4"> |
| 4796 |
<h4 id="name-block-confidentiality-block-3"> |
| 4797 |
<a href="#appendix-A.4.4" class="section-number selfRef">A.4.4. </a><a href="#name-block-confidentiality-block-3" class="section-name selfRef">Block Confidentiality Block</a> |
| 4798 |
</h4> |
| 4799 |
<p id="appendix-A.4.4-1"> |
| 4800 |
In this example, a BCB is used encrypt the payload |
| 4801 |
block and the BIB that provides integrity over |
| 4802 |
the payload.<a href="#appendix-A.4.4-1" class="pilcrow">¶</a></p> |
| 4803 |
<section id="appendix-A.4.4.1"> |
| 4804 |
<h5 id="name-configuration-parameters-and-res"> |
| 4805 |
<a href="#appendix-A.4.4.1" class="section-number selfRef">A.4.4.1. </a><a href="#name-configuration-parameters-and-res" class="section-name selfRef">Configuration, Parameters, and Results</a> |
| 4806 |
</h5> |
| 4807 |
<p id="appendix-A.4.4.1-1"> |
| 4808 |
For this example, the following configuration and security context |
| 4809 |
parameters are used to generate the security results |
| 4810 |
indicated.<a href="#appendix-A.4.4.1-1" class="pilcrow">¶</a></p> |
| 4811 |
<p id="appendix-A.4.4.1-2"> |
| 4812 |
This BCB has two targets: the payload block and BIB. Four |
| 4813 |
security results are generated: ciphertext that |
| 4814 |
replaces the plaintext block-type-specific data of the |
| 4815 |
payload block, ciphertext to encrypt the BIB, and authentication |
| 4816 |
tags for both the payload block and BIB.<a href="#appendix-A.4.4.1-2" class="pilcrow">¶</a></p> |
| 4817 |
<span id="name-example-4-configuration-para"></span><div id="ex4_bcb_cpr"> |
| 4818 |
<figure id="figure-27"> |
| 4819 |
<div class="alignCenter art-ascii-art art-text artwork" id="appendix-A.4.4.1-3.1"> |
| 4820 |
<pre> |
| 4821 |
Key: h'71776572747975696f70617364666768 |
| 4822 |
71776572747975696f70617364666768' |
| 4823 |
IV: h'5477656c7665313231323132' |
| 4824 |
AES Variant: A256GCM |
| 4825 |
Scope Flags: 0x07 (All additional headers) |
| 4826 |
Payload Data: h'526561647920746f2067656e65726174 |
| 4827 |
6520612033322d62797465207061796c |
| 4828 |
6f6164' |
| 4829 |
BIB Data: h'81010101820282020182820106820307 |
| 4830 |
818182015830f75fe4c37f76f0461658 |
| 4831 |
55bd5ff72fbfd4e3a64b4695c40e2b78 |
| 4832 |
7da005ae819f0a2e30a2e8b325527de8 |
| 4833 |
aefb52e73d71' |
| 4834 |
Primary Block Data: h'88070000820282010282028202018202 |
| 4835 |
820201820018281a000f4240' |
| 4836 |
Payload Header: h'010100' |
| 4837 |
BIB Header: h'0b0300' |
| 4838 |
BCB Header: h'0c0201' |
| 4839 |
Payload AAD: h'07880700008202820102820282020182 |
| 4840 |
02820201820018281a000f4240010100 |
| 4841 |
0c0201' |
| 4842 |
BIB AAD: h'07880700008202820102820282020182 |
| 4843 |
02820201820018281a000f42400b0300 |
| 4844 |
0c0201' |
| 4845 |
Payload Block |
| 4846 |
Authentication Tag: h'd2c51cb2481792dae8b21d848cede99b' |
| 4847 |
BIB |
| 4848 |
Authentication Tag: h'220ffc45c8a901999ecc60991dd78b29' |
| 4849 |
Payload Ciphertext: h'90eab6457593379298a8724e16e61f83 |
| 4850 |
7488e127212b59ac91f8a86287b7d076 |
| 4851 |
30a122' |
| 4852 |
BIB Ciphertext: h'438ed6208eb1c1ffb94d952175167df0 |
| 4853 |
902902064a2983910c4fb2340790bf42 |
| 4854 |
0a7d1921d5bf7c4721e02ab87a93ab1e |
| 4855 |
0b75cf62e4948727c8b5dae46ed2af05 |
| 4856 |
439b88029191' |
| 4857 |
</pre> |
| 4858 |
</div> |
| 4859 |
<figcaption><a href="#figure-27" class="selfRef">Figure 27</a>: |
| 4860 |
<a href="#name-example-4-configuration-para" class="selfRef">Example 4 - Configuration, Parameters, and Results for the BCB</a> |
| 4861 |
</figcaption></figure> |
| 4862 |
</div> |
| 4863 |
</section> |
| 4864 |
<section id="appendix-A.4.4.2"> |
| 4865 |
<h5 id="name-abstract-security-block-6"> |
| 4866 |
<a href="#appendix-A.4.4.2" class="section-number selfRef">A.4.4.2. </a><a href="#name-abstract-security-block-6" class="section-name selfRef">Abstract Security Block</a> |
| 4867 |
</h5> |
| 4868 |
<p id="appendix-A.4.4.2-1"> |
| 4869 |
The abstract security block structure of the BCB's |
| 4870 |
block-type-specific data field for this application is as follows.<a href="#appendix-A.4.4.2-1" class="pilcrow">¶</a></p> |
| 4871 |
<span id="name-example-4-bcb-abstract-secu"></span><div id="ex4_bcb_asb"> |
| 4872 |
<figure id="figure-28"> |
| 4873 |
<div id="appendix-A.4.4.2-2.1"> |
| 4874 |
<pre class="lang-cbor-diag sourcecode"> |
| 4875 |
[3, 1], / Security Targets / |
| 4876 |
2, / Security Context ID - BCB-AES-GCM / |
| 4877 |
1, / Security Context Flags - Parameters Present / |
| 4878 |
[2,[2, 1]], / Security Source - ipn:2.1 / |
| 4879 |
[ / Security Parameters - 3 Parameters / |
| 4880 |
[1, h'5477656c7665313231323132'], / Initialization Vector / |
| 4881 |
[2, 3], / AES Variant - AES 256 / |
| 4882 |
[4, 0x07] / Scope Flags - All headers in SHA hash / |
| 4883 |
], |
| 4884 |
[ / Security Results: 2 Results / |
| 4885 |
[ |
| 4886 |
[1, h'220ffc45c8a901999ecc60991dd78b29'] / BIB Auth. Tag / |
| 4887 |
], |
| 4888 |
[ |
| 4889 |
[1, h'd2c51cb2481792dae8b21d848cede99b'] / Payload Auth. Tag / |
| 4890 |
] |
| 4891 |
] |
| 4892 |
</pre> |
| 4893 |
</div> |
| 4894 |
<figcaption><a href="#figure-28" class="selfRef">Figure 28</a>: |
| 4895 |
<a href="#name-example-4-bcb-abstract-secu" class="selfRef">Example 4 - BCB Abstract Security Block (CBOR Diagnostic Notation)</a> |
| 4896 |
</figcaption></figure> |
| 4897 |
</div> |
| 4898 |
<p id="appendix-A.4.4.2-3"> |
| 4899 |
|
| 4900 |
The CBOR encoding of the BCB block-type-specific data field |
| 4901 |
(the abstract security block) is:<a href="#appendix-A.4.4.2-3" class="pilcrow">¶</a></p> |
| 4902 |
<div id="appendix-A.4.4.2-4"> |
| 4903 |
<pre class="sourcecode"> |
| 4904 |
0x820301020182028202018382014c5477656c766531323132313282020382040782 |
| 4905 |
81820150220ffc45c8a901999ecc60991dd78b2981820150d2c51cb2481792dae8b2 |
| 4906 |
1d848cede99b |
| 4907 |
</pre><a href="#appendix-A.4.4.2-4" class="pilcrow">¶</a> |
| 4908 |
</div> |
| 4909 |
</section> |
| 4910 |
<section id="appendix-A.4.4.3"> |
| 4911 |
<h5 id="name-representations-6"> |
| 4912 |
<a href="#appendix-A.4.4.3" class="section-number selfRef">A.4.4.3. </a><a href="#name-representations-6" class="section-name selfRef">Representations</a> |
| 4913 |
</h5> |
| 4914 |
<p id="appendix-A.4.4.3-1"> |
| 4915 |
The complete BCB is as follows.<a href="#appendix-A.4.4.3-1" class="pilcrow">¶</a></p> |
| 4916 |
<span id="name-example-4-bcb-cbor-diagnost"></span><div id="ex4_bcb"> |
| 4917 |
<figure id="figure-29"> |
| 4918 |
<div id="appendix-A.4.4.3-2.1"> |
| 4919 |
<pre class="lang-cbor-diag sourcecode"> |
| 4920 |
[ |
| 4921 |
12, / type code / |
| 4922 |
2, / block number / |
| 4923 |
1, / flags - block must be replicated in every fragment / |
| 4924 |
0, / CRC type / |
| 4925 |
h'820301020182028202018382014c5477656c7665313231323132820203820407 |
| 4926 |
8281820150220ffc45c8a901999ecc60991dd78b2981820150d2c51cb2481792 |
| 4927 |
dae8b21d848cede99b' |
| 4928 |
] |
| 4929 |
</pre> |
| 4930 |
</div> |
| 4931 |
<figcaption><a href="#figure-29" class="selfRef">Figure 29</a>: |
| 4932 |
<a href="#name-example-4-bcb-cbor-diagnost" class="selfRef">Example 4 - BCB (CBOR Diagnostic Notation)</a> |
| 4933 |
</figcaption></figure> |
| 4934 |
</div> |
| 4935 |
<p id="appendix-A.4.4.3-3"> |
| 4936 |
The CBOR encoding of the BCB block is:<a href="#appendix-A.4.4.3-3" class="pilcrow">¶</a></p> |
| 4937 |
<div id="appendix-A.4.4.3-4"> |
| 4938 |
<pre class="sourcecode"> |
| 4939 |
0x850c0201005849820301020182028202018382014c5477656c7665313231323132 |
| 4940 |
8202038204078281820150220ffc45c8a901999ecc60991dd78b2981820150d2c51c |
| 4941 |
b2481792dae8b21d848cede99b |
| 4942 |
</pre><a href="#appendix-A.4.4.3-4" class="pilcrow">¶</a> |
| 4943 |
</div> |
| 4944 |
</section> |
| 4945 |
</section> |
| 4946 |
<section id="appendix-A.4.5"> |
| 4947 |
<h4 id="name-final-bundle-4"> |
| 4948 |
<a href="#appendix-A.4.5" class="section-number selfRef">A.4.5. </a><a href="#name-final-bundle-4" class="section-name selfRef">Final Bundle</a> |
| 4949 |
</h4> |
| 4950 |
<p id="appendix-A.4.5-1"> |
| 4951 |
The CBOR encoding of the full output bundle, with the security blocks added and payload block and BIB encrypted is:<a href="#appendix-A.4.5-1" class="pilcrow">¶</a></p> |
| 4952 |
<div id="appendix-A.4.5-2"> |
| 4953 |
<pre class="sourcecode"> |
| 4954 |
0x9f88070000820282010282028202018202820201820018281a000f4240850b0300 |
| 4955 |
005846438ed6208eb1c1ffb94d952175167df0902902064a2983910c4fb2340790bf |
| 4956 |
420a7d1921d5bf7c4721e02ab87a93ab1e0b75cf62e4948727c8b5dae46ed2af0543 |
| 4957 |
9b88029191850c0201005849820301020182028202018382014c5477656c76653132 |
| 4958 |
313231328202038204078281820150220ffc45c8a901999ecc60991dd78b29818201 |
| 4959 |
50d2c51cb2481792dae8b21d848cede99b8501010000582390eab6457593379298a8 |
| 4960 |
724e16e61f837488e127212b59ac91f8a86287b7d07630a122ff |
| 4961 |
</pre><a href="#appendix-A.4.5-2" class="pilcrow">¶</a> |
| 4962 |
</div> |
| 4963 |
</section> |
| 4964 |
</section> |
| 4965 |
</section> |
| 4966 |
</div> |
| 4967 |
<div id="cddl"> |
| 4968 |
<section id="appendix-B"> |
| 4969 |
<h2 id="name-cddl-expression"> |
| 4970 |
<a href="#appendix-B" class="section-number selfRef">Appendix B. </a><a href="#name-cddl-expression" class="section-name selfRef">CDDL Expression</a> |
| 4971 |
</h2> |
| 4972 |
<p id="appendix-B-1"> |
| 4973 |
For informational purposes, this section contains an |
| 4974 |
expression of the IPPT and AAD structures using the Concise Data |
| 4975 |
Definition Language (CDDL).<a href="#appendix-B-1" class="pilcrow">¶</a></p> |
| 4976 |
<p id="appendix-B-2">NOTES:<a href="#appendix-B-2" class="pilcrow">¶</a></p> |
| 4977 |
<ul class="normal"> |
| 4978 |
<li class="normal" id="appendix-B-3.1">Wherever the CDDL expression is in disagreement with the textual representation of |
| 4979 |
the security block specification presented in earlier sections of this document, |
| 4980 |
the textual representation rules.<a href="#appendix-B-3.1" class="pilcrow">¶</a> |
| 4981 |
</li> |
| 4982 |
<li class="normal" id="appendix-B-3.2"> |
| 4983 |
The structure of BP bundles and BPSec security blocks are provided by other |
| 4984 |
specifications; this appendix only provides the CDDL expression for structures uniquely |
| 4985 |
defined in this specification. Items related to elements of a bundle, such as "primary-block", |
| 4986 |
are defined in <span><a href="https://www.rfc-editor.org/rfc/rfc9171#appendix-B" class="relref">Appendix B</a> of the Bundle Protocol version 7 [<a href="#RFC9171" class="xref">RFC9171</a>]</span>.<a href="#appendix-B-3.2" class="pilcrow">¶</a> |
| 4987 |
</li> |
| 4988 |
<li class="normal" id="appendix-B-3.3"> |
| 4989 |
The CDDL itself does not have the concept of unadorned CBOR sequences as |
| 4990 |
a top-level subject of a specification. The current best practice, as documented in |
| 4991 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8742#section-4.1" class="relref">Section 4.1</a> of [<a href="#RFC8742" class="xref">RFC8742</a>]</span>, requires representing the sequence as an |
| 4992 |
array with a comment in the CDDL noting that the array represents a CBOR sequence.<a href="#appendix-B-3.3" class="pilcrow">¶</a> |
| 4993 |
</li> |
| 4994 |
</ul> |
| 4995 |
<span id="name-ippt-and-aad-expressions"></span><div id="appendix_b"> |
| 4996 |
<figure id="figure-30"> |
| 4997 |
<div id="appendix-B-4.1"> |
| 4998 |
<pre class="lang-cddl sourcecode"> |
| 4999 |
start = scope / AAD-list / IPPT-list ; satisfy CDDL decoders |
| 5000 |
|
| 5001 |
scope = uint .bits scope-flags |
| 5002 |
scope-flags = &( |
| 5003 |
has-primary-ctx: 0, |
| 5004 |
has-target-ctx: 1, |
| 5005 |
has-security-ctx: 2, |
| 5006 |
) |
| 5007 |
|
| 5008 |
; Encoded as a CBOR sequence |
| 5009 |
AAD-list = [ |
| 5010 |
AAD-structure |
| 5011 |
] |
| 5012 |
|
| 5013 |
; Encoded as a CBOR sequence |
| 5014 |
IPPT-list = [ |
| 5015 |
AAD-structure, |
| 5016 |
target-btsd: bstr ; block-type-specific data of the target block. |
| 5017 |
] |
| 5018 |
|
| 5019 |
AAD-structure = ( |
| 5020 |
scope, |
| 5021 |
? primary-block, ; present if has-primary-ctx flag set |
| 5022 |
? block-metadata, ; present if has-target-ctx flag set |
| 5023 |
? block-metadata, ; present if has-security-ctx flag set |
| 5024 |
) |
| 5025 |
|
| 5026 |
; Selected fields of a canonical block |
| 5027 |
block-metadata = ( |
| 5028 |
block-type-code: uint, |
| 5029 |
block-number: uint, |
| 5030 |
block-control-flags, |
| 5031 |
) |
| 5032 |
</pre> |
| 5033 |
</div> |
| 5034 |
<figcaption><a href="#figure-30" class="selfRef">Figure 30</a>: |
| 5035 |
<a href="#name-ippt-and-aad-expressions" class="selfRef">IPPT and AAD Expressions</a> |
| 5036 |
</figcaption></figure> |
| 5037 |
</div> |
| 5038 |
</section> |
| 5039 |
</div> |
| 5040 |
<div id="contr"> |
| 5041 |
<section id="appendix-C"> |
| 5042 |
<h2 id="name-acknowledgments"> |
| 5043 |
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a> |
| 5044 |
</h2> |
| 5045 |
<p id="appendix-C-1"> |
| 5046 |
<span class="contact-name">Amy Alford</span> of the Johns Hopkins University Applied Physics |
| 5047 |
Laboratory contributed useful review and analysis of these |
| 5048 |
security contexts.<a href="#appendix-C-1" class="pilcrow">¶</a></p> |
| 5049 |
<p id="appendix-C-2"><span class="contact-name">Brian Sipos</span> kindly provided the CDDL expression in <a href="#cddl" class="xref">Appendix B</a>.<a href="#appendix-C-2" class="pilcrow">¶</a></p> |
| 5050 |
</section> |
| 5051 |
</div> |
| 5052 |
<div id="authors-addresses"> |
| 5053 |
<section id="appendix-D"> |
| 5054 |
<h2 id="name-authors-addresses"> |
| 5055 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 5056 |
</h2> |
| 5057 |
<address class="vcard"> |
| 5058 |
<div dir="auto" class="left"><span class="fn nameRole">Edward J. Birrane, III</span></div> |
| 5059 |
<div dir="auto" class="left"><span class="org">The Johns Hopkins University Applied Physics Laboratory</span></div> |
| 5060 |
<div dir="auto" class="left"><span class="street-address">11100 Johns Hopkins Rd.</span></div> |
| 5061 |
<div dir="auto" class="left"> |
| 5062 |
<span class="locality">Laurel</span>, <span class="region">MD</span> <span class="postal-code">20723</span> |
| 5063 |
</div> |
| 5064 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 5065 |
<div class="tel"> |
| 5066 |
<span>Phone:</span> |
| 5067 |
<a href="tel:+1%20443%20778%207423" class="tel">+1 443 778 7423</a> |
| 5068 |
</div> |
| 5069 |
<div class="email"> |
| 5070 |
<span>Email:</span> |
| 5071 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 5072 |
</div> |
| 5073 |
</address> |
| 5074 |
<address class="vcard"> |
| 5075 |
<div dir="auto" class="left"><span class="fn nameRole">Alex White</span></div> |
| 5076 |
<div dir="auto" class="left"><span class="org">The Johns Hopkins University Applied Physics Laboratory</span></div> |
| 5077 |
<div dir="auto" class="left"><span class="street-address">11100 Johns Hopkins Rd.</span></div> |
| 5078 |
<div dir="auto" class="left"> |
| 5079 |
<span class="locality">Laurel</span>, <span class="region">MD</span> <span class="postal-code">20723</span> |
| 5080 |
</div> |
| 5081 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 5082 |
<div class="tel"> |
| 5083 |
<span>Phone:</span> |
| 5084 |
<a href="tel:+1%20443%20778%200845" class="tel">+1 443 778 0845</a> |
| 5085 |
</div> |
| 5086 |
<div class="email"> |
| 5087 |
<span>Email:</span> |
| 5088 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 5089 |
</div> |
| 5090 |
</address> |
| 5091 |
<address class="vcard"> |
| 5092 |
<div dir="auto" class="left"><span class="fn nameRole">Sarah Heiner</span></div> |
| 5093 |
<div dir="auto" class="left"><span class="org">The Johns Hopkins University Applied Physics Laboratory</span></div> |
| 5094 |
<div dir="auto" class="left"><span class="street-address">11100 Johns Hopkins Rd.</span></div> |
| 5095 |
<div dir="auto" class="left"> |
| 5096 |
<span class="locality">Laurel</span>, <span class="region">MD</span> <span class="postal-code">20723</span> |
| 5097 |
</div> |
| 5098 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 5099 |
<div class="tel"> |
| 5100 |
<span>Phone:</span> |
| 5101 |
<a href="tel:+1%20240%20592%203704" class="tel">+1 240 592 3704</a> |
| 5102 |
</div> |
| 5103 |
<div class="email"> |
| 5104 |
<span>Email:</span> |
| 5105 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 5106 |
</div> |
| 5107 |
</address> |
| 5108 |
</section> |
| 5109 |
</div> |
| 5110 |
<script>const toc = document.getElementById("toc"); |
| 5111 |
toc.querySelector("h2").addEventListener("click", e => { |
| 5112 |
toc.classList.toggle("active"); |
| 5113 |
}); |
| 5114 |
toc.querySelector("nav").addEventListener("click", e => { |
| 5115 |
toc.classList.remove("active"); |
| 5116 |
}); |
| 5117 |
</script> |
| 5118 |
</body> |
| 5119 |
</html> |