Debian Codegraph @

rfc8756.html

raw
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 8756: Commercial National Security Algorithm (CNSA) Suite Profile of Certificate Management over CMS</title>
8 <meta content="Michael Jenkins" name="author">
9 <meta content="Lydia Zieglar" name="author">
10 <meta content="
11 This document specifies a profile of the Certificate Management over CMS (CMC) protocol for managing X.509 public key certificates in applications that use the Commercial National Security Algorithm (CNSA) Suite published by the United States Government.
12
13 The profile applies to the capabilities, configuration, and operation of all components of US National Security Systems that manage X.509 public key certificates over CMS. It is also appropriate for all other US Government systems that process high-value information.
14
15 The profile is made publicly available here for use by developers and operators of these and any other system deployments.
16
17 " name="description">
18 <meta content="xml2rfc 2.41.0" name="generator">
19 <meta content="NSA" name="keyword">
20 <meta content="CNSA" name="keyword">
21 <meta content="NSS" name="keyword">
22 <meta content="certificate" name="keyword">
23 <meta content="enrollment" name="keyword">
24 <meta content="8756" name="rfc.number">
25 <link href="rfc8756.xml" rel="alternate" type="application/rfc+xml">
26 <link href="#copyright" rel="license">
27 <style type="text/css">/*
28
29 NOTE: Changes at the bottom of this file overrides some earlier settings.
30
31 Once the style has stabilized and has been adopted as an official RFC style,
32 this can be consolidated so that style settings occur only in one place, but
33 for now the contents of this file consists first of the initial CSS work as
34 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
35 commented changes found necssary during the development of the v3
36 formatters.
37
38 */
39
40 /* fonts */
41 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
42 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
43 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
44
45 @viewport {
46 zoom: 1.0;
47 width: extend-to-zoom;
48 }
49 @-ms-viewport {
50 width: extend-to-zoom;
51 zoom: 1.0;
52 }
53 /* general and mobile first */
54 html {
55 }
56 body {
57 max-width: 90%;
58 margin: 1.5em auto;
59 color: #222;
60 background-color: #fff;
61 font-size: 14px;
62 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
63 line-height: 1.6;
64 scroll-behavior: smooth;
65 }
66 .ears {
67 display: none;
68 }
69
70 /* headings */
71 #title, h1, h2, h3, h4, h5, h6 {
72 margin: 1em 0 0.5em;
73 font-weight: bold;
74 line-height: 1.3;
75 }
76 #title {
77 clear: both;
78 border-bottom: 1px solid #ddd;
79 margin: 0 0 0.5em 0;
80 padding: 1em 0 0.5em;
81 }
82 .author {
83 padding-bottom: 4px;
84 }
85 h1 {
86 font-size: 26px;
87 margin: 1em 0;
88 }
89 h2 {
90 font-size: 22px;
91 margin-top: -20px; /* provide offset for in-page anchors */
92 padding-top: 33px;
93 }
94 h3 {
95 font-size: 18px;
96 margin-top: -36px; /* provide offset for in-page anchors */
97 padding-top: 42px;
98 }
99 h4 {
100 font-size: 16px;
101 margin-top: -36px; /* provide offset for in-page anchors */
102 padding-top: 42px;
103 }
104 h5, h6 {
105 font-size: 14px;
106 }
107 #n-copyright-notice {
108 border-bottom: 1px solid #ddd;
109 padding-bottom: 1em;
110 margin-bottom: 1em;
111 }
112 /* general structure */
113 p {
114 padding: 0;
115 margin: 0 0 1em 0;
116 text-align: left;
117 }
118 div, span {
119 position: relative;
120 }
121 div {
122 margin: 0;
123 }
124 .alignRight.art-text {
125 background-color: #f9f9f9;
126 border: 1px solid #eee;
127 border-radius: 3px;
128 padding: 1em 1em 0;
129 margin-bottom: 1.5em;
130 }
131 .alignRight.art-text pre {
132 padding: 0;
133 }
134 .alignRight {
135 margin: 1em 0;
136 }
137 .alignRight > *:first-child {
138 border: none;
139 margin: 0;
140 float: right;
141 clear: both;
142 }
143 .alignRight > *:nth-child(2) {
144 clear: both;
145 display: block;
146 border: none;
147 }
148 svg {
149 display: block;
150 }
151 .alignCenter.art-text {
152 background-color: #f9f9f9;
153 border: 1px solid #eee;
154 border-radius: 3px;
155 padding: 1em 1em 0;
156 margin-bottom: 1.5em;
157 }
158 .alignCenter.art-text pre {
159 padding: 0;
160 }
161 .alignCenter {
162 margin: 1em 0;
163 }
164 .alignCenter > *:first-child {
165 border: none;
166 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
167 support flexbox yet.
168 */
169 display: table;
170 margin: 0 auto;
171 }
172
173 /* lists */
174 ol, ul {
175 padding: 0;
176 margin: 0 0 1em 2em;
177 }
178 ol ol, ul ul, ol ul, ul ol {
179 margin-left: 1em;
180 }
181 li {
182 margin: 0 0 0.25em 0;
183 }
184 .ulCompact li {
185 margin: 0;
186 }
187 ul.empty, .ulEmpty {
188 list-style-type: none;
189 }
190 ul.empty li, .ulEmpty li {
191 margin-top: 0.5em;
192 }
193 ul.compact, .ulCompact,
194 ol.compact, .olCompact {
195 line-height: 100%;
196 margin: 0 0 0 2em;
197 }
198
199 /* definition lists */
200 dl {
201 }
202 dl > dt {
203 float: left;
204 margin-right: 1em;
205 }
206 /*
207 dl.nohang > dt {
208 float: none;
209 }
210 */
211 dl > dd {
212 margin-bottom: .8em;
213 min-height: 1.3em;
214 }
215 dl.compact > dd, .dlCompact > dd {
216 margin-bottom: 0em;
217 }
218 dl > dd > dl {
219 margin-top: 0.5em;
220 margin-bottom: 0em;
221 }
222
223 /* links */
224 a {
225 text-decoration: none;
226 }
227 a[href] {
228 color: #22e; /* Arlen: WCAG 2019 */
229 }
230 a[href]:hover {
231 background-color: #f2f2f2;
232 }
233 figcaption a[href],
234 a[href].selfRef {
235 color: #222;
236 }
237 /* XXX probably not this:
238 a.selfRef:hover {
239 background-color: transparent;
240 cursor: default;
241 } */
242
243 /* Figures */
244 tt, code, pre, code {
245 background-color: #f9f9f9;
246 font-family: 'Roboto Mono', monospace;
247 }
248 pre {
249 border: 1px solid #eee;
250 margin: 0;
251 padding: 1em;
252 }
253 img {
254 max-width: 100%;
255 }
256 figure {
257 margin: 0;
258 }
259 figure blockquote {
260 margin: 0.8em 0.4em 0.4em;
261 }
262 figcaption {
263 font-style: italic;
264 margin: 0 0 1em 0;
265 }
266 @media screen {
267 pre {
268 overflow-x: auto;
269 max-width: 100%;
270 max-width: calc(100% - 22px);
271 }
272 }
273
274 /* aside, blockquote */
275 aside, blockquote {
276 margin-left: 0;
277 padding: 1.2em 2em;
278 }
279 blockquote {
280 background-color: #f9f9f9;
281 color: #111; /* Arlen: WCAG 2019 */
282 border: 1px solid #ddd;
283 border-radius: 3px;
284 margin: 1em 0;
285 }
286 cite {
287 display: block;
288 text-align: right;
289 font-style: italic;
290 }
291
292 /* tables */
293 table {
294 width: 100%;
295 margin: 0 0 1em;
296 border-collapse: collapse;
297 border: 1px solid #eee;
298 }
299 th, td {
300 text-align: left;
301 vertical-align: top;
302 padding: 0.5em 0.75em;
303 }
304 th {
305 text-align: left;
306 background-color: #e9e9e9;
307 }
308 tr:nth-child(2n+1) > td {
309 background-color: #f5f5f5;
310 }
311 table caption {
312 font-style: italic;
313 margin: 0;
314 padding: 0;
315 text-align: left;
316 }
317 table p {
318 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
319 be allowed within tables more generally, it would be far better to select on a class. */
320 margin: 0;
321 }
322
323 /* pilcrow */
324 a.pilcrow {
325 color: #666; /* Arlen: AHDJ 2019 */
326 text-decoration: none;
327 visibility: hidden;
328 user-select: none;
329 -ms-user-select: none;
330 -o-user-select:none;
331 -moz-user-select: none;
332 -khtml-user-select: none;
333 -webkit-user-select: none;
334 -webkit-touch-callout: none;
335 }
336 @media screen {
337 aside:hover > a.pilcrow,
338 p:hover > a.pilcrow,
339 blockquote:hover > a.pilcrow,
340 div:hover > a.pilcrow,
341 li:hover > a.pilcrow,
342 pre:hover > a.pilcrow {
343 visibility: visible;
344 }
345 a.pilcrow:hover {
346 background-color: transparent;
347 }
348 }
349
350 /* misc */
351 hr {
352 border: 0;
353 border-top: 1px solid #eee;
354 }
355 .bcp14 {
356 font-variant: small-caps;
357 }
358
359 .role {
360 font-variant: all-small-caps;
361 }
362
363 /* info block */
364 #identifiers {
365 margin: 0;
366 font-size: 0.9em;
367 }
368 #identifiers dt {
369 width: 3em;
370 clear: left;
371 }
372 #identifiers dd {
373 float: left;
374 margin-bottom: 0;
375 }
376 #identifiers .authors .author {
377 display: inline-block;
378 margin-right: 1.5em;
379 }
380 #identifiers .authors .org {
381 font-style: italic;
382 }
383
384 /* The prepared/rendered info at the very bottom of the page */
385 .docInfo {
386 color: #666; /* Arlen: WCAG 2019 */
387 font-size: 0.9em;
388 font-style: italic;
389 margin-top: 2em;
390 }
391 .docInfo .prepared {
392 float: left;
393 }
394 .docInfo .prepared {
395 float: right;
396 }
397
398 /* table of contents */
399 #toc {
400 padding: 0.75em 0 2em 0;
401 margin-bottom: 1em;
402 }
403 nav.toc ul {
404 margin: 0 0.5em 0 0;
405 padding: 0;
406 list-style: none;
407 }
408 nav.toc li {
409 line-height: 1.3em;
410 margin: 0.75em 0;
411 padding-left: 1.2em;
412 text-indent: -1.2em;
413 }
414 /* references */
415 .references dt {
416 text-align: right;
417 font-weight: bold;
418 min-width: 7em;
419 }
420 .references dd {
421 margin-left: 8em;
422 overflow: auto;
423 }
424
425 .refInstance {
426 margin-bottom: 1.25em;
427 }
428
429 .references .ascii {
430 margin-bottom: 0.25em;
431 }
432
433 /* index */
434 .index ul {
435 margin: 0 0 0 1em;
436 padding: 0;
437 list-style: none;
438 }
439 .index ul ul {
440 margin: 0;
441 }
442 .index li {
443 margin: 0;
444 text-indent: -2em;
445 padding-left: 2em;
446 padding-bottom: 5px;
447 }
448 .indexIndex {
449 margin: 0.5em 0 1em;
450 }
451 .index a {
452 font-weight: 700;
453 }
454 /* make the index two-column on all but the smallest screens */
455 @media (min-width: 600px) {
456 .index ul {
457 -moz-column-count: 2;
458 -moz-column-gap: 20px;
459 }
460 .index ul ul {
461 -moz-column-count: 1;
462 -moz-column-gap: 0;
463 }
464 }
465
466 /* authors */
467 address.vcard {
468 font-style: normal;
469 margin: 1em 0;
470 }
471
472 address.vcard .nameRole {
473 font-weight: 700;
474 margin-left: 0;
475 }
476 address.vcard .label {
477 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
478 margin: 0.5em 0;
479 }
480 address.vcard .type {
481 display: none;
482 }
483 .alternative-contact {
484 margin: 1.5em 0 1em;
485 }
486 hr.addr {
487 border-top: 1px dashed;
488 margin: 0;
489 color: #ddd;
490 max-width: calc(100% - 16px);
491 }
492
493 /* temporary notes */
494 .rfcEditorRemove::before {
495 position: absolute;
496 top: 0.2em;
497 right: 0.2em;
498 padding: 0.2em;
499 content: "The RFC Editor will remove this note";
500 color: #9e2a00; /* Arlen: WCAG 2019 */
501 background-color: #ffd; /* Arlen: WCAG 2019 */
502 }
503 .rfcEditorRemove {
504 position: relative;
505 padding-top: 1.8em;
506 background-color: #ffd; /* Arlen: WCAG 2019 */
507 border-radius: 3px;
508 }
509 .cref {
510 background-color: #ffd; /* Arlen: WCAG 2019 */
511 padding: 2px 4px;
512 }
513 .crefSource {
514 font-style: italic;
515 }
516 /* alternative layout for smaller screens */
517 @media screen and (max-width: 1023px) {
518 body {
519 padding-top: 2em;
520 }
521 #title {
522 padding: 1em 0;
523 }
524 h1 {
525 font-size: 24px;
526 }
527 h2 {
528 font-size: 20px;
529 margin-top: -18px; /* provide offset for in-page anchors */
530 padding-top: 38px;
531 }
532 #identifiers dd {
533 max-width: 60%;
534 }
535 #toc {
536 position: fixed;
537 z-index: 2;
538 top: 0;
539 right: 0;
540 padding: 0;
541 margin: 0;
542 background-color: inherit;
543 border-bottom: 1px solid #ccc;
544 }
545 #toc h2 {
546 margin: -1px 0 0 0;
547 padding: 4px 0 4px 6px;
548 padding-right: 1em;
549 min-width: 190px;
550 font-size: 1.1em;
551 text-align: right;
552 background-color: #444;
553 color: white;
554 cursor: pointer;
555 }
556 #toc h2::before { /* css hamburger */
557 float: right;
558 position: relative;
559 width: 1em;
560 height: 1px;
561 left: -164px;
562 margin: 6px 0 0 0;
563 background: white none repeat scroll 0 0;
564 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
565 content: "";
566 }
567 #toc nav {
568 display: none;
569 padding: 0.5em 1em 1em;
570 overflow: auto;
571 height: calc(100vh - 48px);
572 border-left: 1px solid #ddd;
573 }
574 }
575
576 /* alternative layout for wide screens */
577 @media screen and (min-width: 1024px) {
578 body {
579 max-width: 724px;
580 margin: 42px auto;
581 padding-left: 1.5em;
582 padding-right: 29em;
583 }
584 #toc {
585 position: fixed;
586 top: 42px;
587 right: 42px;
588 width: 25%;
589 margin: 0;
590 padding: 0 1em;
591 z-index: 1;
592 }
593 #toc h2 {
594 border-top: none;
595 border-bottom: 1px solid #ddd;
596 font-size: 1em;
597 font-weight: normal;
598 margin: 0;
599 padding: 0.25em 1em 1em 0;
600 }
601 #toc nav {
602 display: block;
603 height: calc(90vh - 84px);
604 bottom: 0;
605 padding: 0.5em 0 0;
606 overflow: auto;
607 }
608 img { /* future proofing */
609 max-width: 100%;
610 height: auto;
611 }
612 }
613
614 /* pagination */
615 @media print {
616 body {
617
618 width: 100%;
619 }
620 p {
621 orphans: 3;
622 widows: 3;
623 }
624 #n-copyright-notice {
625 border-bottom: none;
626 }
627 #toc, #n-introduction {
628 page-break-before: always;
629 }
630 #toc {
631 border-top: none;
632 padding-top: 0;
633 }
634 figure, pre {
635 page-break-inside: avoid;
636 }
637 figure {
638 overflow: scroll;
639 }
640 h1, h2, h3, h4, h5, h6 {
641 page-break-after: avoid;
642 }
643 h2+*, h3+*, h4+*, h5+*, h6+* {
644 page-break-before: avoid;
645 }
646 pre {
647 white-space: pre-wrap;
648 word-wrap: break-word;
649 font-size: 10pt;
650 }
651 table {
652 border: 1px solid #ddd;
653 }
654 td {
655 border-top: 1px solid #ddd;
656 }
657 }
658
659 /* This is commented out here, as the string-set: doesn't
660 pass W3C validation currently */
661 /*
662 .ears thead .left {
663 string-set: ears-top-left content();
664 }
665
666 .ears thead .center {
667 string-set: ears-top-center content();
668 }
669
670 .ears thead .right {
671 string-set: ears-top-right content();
672 }
673
674 .ears tfoot .left {
675 string-set: ears-bottom-left content();
676 }
677
678 .ears tfoot .center {
679 string-set: ears-bottom-center content();
680 }
681
682 .ears tfoot .right {
683 string-set: ears-bottom-right content();
684 }
685 */
686
687 @page :first {
688 padding-top: 0;
689 @top-left {
690 content: normal;
691 border: none;
692 }
693 @top-center {
694 content: normal;
695 border: none;
696 }
697 @top-right {
698 content: normal;
699 border: none;
700 }
701 }
702
703 @page {
704 size: A4;
705 margin-bottom: 45mm;
706 padding-top: 20px;
707 /* The follwing is commented out here, but set appropriately by in code, as
708 the content depends on the document */
709 /*
710 @top-left {
711 content: 'Internet-Draft';
712 vertical-align: bottom;
713 border-bottom: solid 1px #ccc;
714 }
715 @top-left {
716 content: string(ears-top-left);
717 vertical-align: bottom;
718 border-bottom: solid 1px #ccc;
719 }
720 @top-center {
721 content: string(ears-top-center);
722 vertical-align: bottom;
723 border-bottom: solid 1px #ccc;
724 }
725 @top-right {
726 content: string(ears-top-right);
727 vertical-align: bottom;
728 border-bottom: solid 1px #ccc;
729 }
730 @bottom-left {
731 content: string(ears-bottom-left);
732 vertical-align: top;
733 border-top: solid 1px #ccc;
734 }
735 @bottom-center {
736 content: string(ears-bottom-center);
737 vertical-align: top;
738 border-top: solid 1px #ccc;
739 }
740 @bottom-right {
741 content: '[Page ' counter(page) ']';
742 vertical-align: top;
743 border-top: solid 1px #ccc;
744 }
745 */
746
747 }
748
749 /* Changes introduced to fix issues found during implementation */
750 /* Make sure links are clickable even if overlapped by following H* */
751 a {
752 z-index: 2;
753 }
754 /* Separate body from document info even without intervening H1 */
755 section {
756 clear: both;
757 }
758
759
760 /* Top align author divs, to avoid names without organization dropping level with org names */
761 .author {
762 vertical-align: top;
763 }
764
765 /* Leave room in document info to show Internet-Draft on one line */
766 #identifiers dt {
767 width: 8em;
768 }
769
770 /* Don't waste quite as much whitespace between label and value in doc info */
771 #identifiers dd {
772 margin-left: 1em;
773 }
774
775 /* Give floating toc a background color (needed when it's a div inside section */
776 #toc {
777 background-color: white;
778 }
779
780 /* Make the collapsed ToC header render white on gray also when it's a link */
781 @media screen and (max-width: 1023px) {
782 #toc h2 a,
783 #toc h2 a:link,
784 #toc h2 a:focus,
785 #toc h2 a:hover,
786 #toc a.toplink,
787 #toc a.toplink:hover {
788 color: white;
789 background-color: #444;
790 text-decoration: none;
791 }
792 }
793
794 /* Give the bottom of the ToC some whitespace */
795 @media screen and (min-width: 1024px) {
796 #toc {
797 padding: 0 0 1em 1em;
798 }
799 }
800
801 /* Style section numbers with more space between number and title */
802 .section-number {
803 padding-right: 0.5em;
804 }
805
806 /* prevent monospace from becoming overly large */
807 tt, code, pre, code {
808 font-size: 95%;
809 }
810
811 /* Fix the height/width aspect for ascii art*/
812 pre.sourcecode,
813 .art-text pre {
814 line-height: 1.12;
815 }
816
817
818 /* Add styling for a link in the ToC that points to the top of the document */
819 a.toplink {
820 float: right;
821 margin-right: 0.5em;
822 }
823
824 /* Fix the dl styling to match the RFC 7992 attributes */
825 dl > dt,
826 dl.dlParallel > dt {
827 float: left;
828 margin-right: 1em;
829 }
830 dl.dlNewline > dt {
831 float: none;
832 }
833
834 /* Provide styling for table cell text alignment */
835 table td.text-left,
836 table th.text-left {
837 text-align: left;
838 }
839 table td.text-center,
840 table th.text-center {
841 text-align: center;
842 }
843 table td.text-right,
844 table th.text-right {
845 text-align: right;
846 }
847
848 /* Make the alternative author contact informatio look less like just another
849 author, and group it closer with the primary author contact information */
850 .alternative-contact {
851 margin: 0.5em 0 0.25em 0;
852 }
853 address .non-ascii {
854 margin: 0 0 0 2em;
855 }
856
857 /* With it being possible to set tables with alignment
858 left, center, and right, { width: 100%; } does not make sense */
859 table {
860 width: auto;
861 }
862
863 /* Avoid reference text that sits in a block with very wide left margin,
864 because of a long floating dt label.*/
865 .references dd {
866 overflow: visible;
867 }
868
869 /* Control caption placement */
870 caption {
871 caption-side: bottom;
872 }
873
874 /* Limit the width of the author address vcard, so names in right-to-left
875 script don't end up on the other side of the page. */
876
877 address.vcard {
878 max-width: 30em;
879 margin-right: auto;
880 }
881
882 /* For address alignment dependent on LTR or RTL scripts */
883 address div.left {
884 text-align: left;
885 }
886 address div.right {
887 text-align: right;
888 }
889
890 /* Provide table alignment support. We can't use the alignX classes above
891 since they do unwanted things with caption and other styling. */
892 table.right {
893 margin-left: auto;
894 margin-right: 0;
895 }
896 table.center {
897 margin-left: auto;
898 margin-right: auto;
899 }
900 table.left {
901 margin-left: 0;
902 margin-right: auto;
903 }
904
905 /* Give the table caption label the same styling as the figcaption */
906 caption a[href] {
907 color: #222;
908 }
909
910 @media print {
911 .toplink {
912 display: none;
913 }
914
915 /* avoid overwriting the top border line with the ToC header */
916 #toc {
917 padding-top: 1px;
918 }
919
920 /* Avoid page breaks inside dl and author address entries */
921 .vcard {
922 page-break-inside: avoid;
923 }
924
925 }
926 /* Avoid wrapping of URLs in references */
927 @media screen {
928 .references a {
929 white-space: nowrap;
930 }
931 }
932 /* Tweak the bcp14 keyword presentation */
933 .bcp14 {
934 font-variant: small-caps;
935 font-weight: bold;
936 font-size: 0.9em;
937 }
938 /* Tweak the invisible space above H* in order not to overlay links in text above */
939 h2 {
940 margin-top: -18px; /* provide offset for in-page anchors */
941 padding-top: 31px;
942 }
943 h3 {
944 margin-top: -18px; /* provide offset for in-page anchors */
945 padding-top: 24px;
946 }
947 h4 {
948 margin-top: -18px; /* provide offset for in-page anchors */
949 padding-top: 24px;
950 }
951 /* Float artwork pilcrow to the right */
952 @media screen {
953 .artwork a.pilcrow {
954 display: block;
955 line-height: 0.7;
956 margin-top: 0.15em;
957 }
958 }
959 /* Make pilcrows on dd visible */
960 @media screen {
961 dd:hover > a.pilcrow {
962 visibility: visible;
963 }
964 }
965 /* Make the placement of figcaption match that of a table's caption
966 by removing the figure's added bottom margin */
967 .alignLeft.art-text,
968 .alignCenter.art-text,
969 .alignRight.art-text {
970 margin-bottom: 0;
971 }
972 .alignLeft,
973 .alignCenter,
974 .alignRight {
975 margin: 1em 0 0 0;
976 }
977 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
978 possibly even requiring a new line */
979 @media print {
980 a.pilcrow {
981 display: none;
982 }
983 }
984 /* Styling for the external metadata */
985 div#external-metadata {
986 background-color: #eee;
987 padding: 0.5em;
988 margin-bottom: 0.5em;
989 display: none;
990 }
991 div#internal-metadata {
992 padding: 0.5em; /* to match the external-metadata padding */
993 }
994 /* Styling for title RFC Number */
995 h1#rfcnum {
996 clear: both;
997 margin: 0 0 -1em;
998 padding: 1em 0 0 0;
999 }
1000 /* Make .olPercent look the same as <ol><li> */
1001 dl.olPercent > dd {
1002 margin-bottom: 0.25em;
1003 min-height: initial;
1004 }
1005 /* Give aside some styling to set it apart */
1006 aside {
1007 border-left: 1px solid #ddd;
1008 margin: 1em 0 1em 2em;
1009 padding: 0.2em 2em;
1010 }
1011 aside > dl,
1012 aside > ol,
1013 aside > ul,
1014 aside > table,
1015 aside > p {
1016 margin-bottom: 0.5em;
1017 }
1018 /* Additional page break settings */
1019 @media print {
1020 figcaption, table caption {
1021 page-break-before: avoid;
1022 }
1023 }
1024 /* Font size adjustments for print */
1025 @media print {
1026 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1027 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1028 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1029 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1030 h4 { font-size: 1em; padding-top: 1.5em; }
1031 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1032 }
1033 /* Sourcecode margin in print, when there's no pilcrow */
1034 @media print {
1035 .artwork,
1036 .sourcecode {
1037 margin-bottom: 1em;
1038 }
1039 }
1040 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1041 table {
1042 min-width: 20em;
1043 }
1044 /* ol type a */
1045 ol.type-a { list-style-type: lower-alpha; }
1046 ol.type-A { list-style-type: upper-alpha; }
1047 ol.type-i { list-style-type: lower-roman; }
1048 ol.type-I { list-style-type: lower-roman; }
1049 /* Apply the print table and row borders in general, on request from the RPC,
1050 and increase the contrast between border and odd row background sligthtly */
1051 table {
1052 border: 1px solid #ddd;
1053 }
1054 td {
1055 border-top: 1px solid #ddd;
1056 }
1057 tr:nth-child(2n+1) > td {
1058 background-color: #f8f8f8;
1059 }
1060 /* Use style rules to govern display of the TOC. */
1061 @media screen and (max-width: 1023px) {
1062 #toc nav { display: none; }
1063 #toc.active nav { display: block; }
1064 }
1065 </style>
1066 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1067 <link href="https://dx.doi.org/10.17487/rfc8756" rel="alternate">
1068 <link href="urn:issn:2070-1721" rel="alternate">
1069 <link href="https://datatracker.ietf.org/doc/draft-jenkins-cnsa-cmc-profile-05" rel="prev">
1070 </head>
1071 <body>
1072 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1073 <table class="ears">
1074 <thead><tr>
1075 <td class="left">RFC 8756</td>
1076 <td class="center">CNSA Suite CMC Profile</td>
1077 <td class="right">March 2020</td>
1078 </tr></thead>
1079 <tfoot><tr>
1080 <td class="left">Jenkins &amp; Zieglar</td>
1081 <td class="center">Informational</td>
1082 <td class="right">[Page]</td>
1083 </tr></tfoot>
1084 </table>
1085 <div id="external-metadata" class="document-information"></div>
1086 <div id="internal-metadata" class="document-information">
1087 <dl id="identifiers">
1088 <dt class="label-stream">Stream:</dt>
1089 <dd class="stream">Independent Submission</dd>
1090 <dt class="label-rfc">RFC:</dt>
1091 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8756" class="eref">8756</a></dd>
1092 <dt class="label-category">Category:</dt>
1093 <dd class="category">Informational</dd>
1094 <dt class="label-published">Published:</dt>
1095 <dd class="published">
1096 <time datetime="2020-03" class="published">March 2020</time>
1097 </dd>
1098 <dt class="label-issn">ISSN:</dt>
1099 <dd class="issn">2070-1721</dd>
1100 <dt class="label-authors">Authors:</dt>
1101 <dd class="authors">
1102 <div class="author">
1103 <div class="author-name">M. Jenkins</div>
1104 <div class="org">NSA</div>
1105 </div>
1106 <div class="author">
1107 <div class="author-name">L. Zieglar</div>
1108 <div class="org">NSA</div>
1109 </div>
1110 </dd>
1111 </dl>
1112 </div>
1113 <h1 id="rfcnum">RFC 8756</h1>
1114 <h1 id="title">Commercial National Security Algorithm (CNSA) Suite Profile of Certificate Management over CMS</h1>
1115 <section id="section-abstract">
1116 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1117 <p id="section-abstract-1">This document specifies a profile of the Certificate Management over CMS (CMC) protocol for managing X.509 public key certificates in applications that use the Commercial National Security Algorithm (CNSA) Suite published by the United States Government.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1118 <p id="section-abstract-2">The profile applies to the capabilities, configuration, and operation of all components of US National Security Systems that manage X.509 public key certificates over CMS. It is also appropriate for all other US Government systems that process high-value information.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1119 <p id="section-abstract-3">The profile is made publicly available here for use by developers and operators of these and any other system deployments.<a href="#section-abstract-3" class="pilcrow">¶</a></p>
1120 </section>
1121 <div id="status-of-memo">
1122 <section id="section-boilerplate.1">
1123 <h2 id="name-status-of-this-memo">
1124 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1125 </h2>
1126 <p id="section-boilerplate.1-1">
1127 This document is not an Internet Standards Track specification; it is
1128 published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1129 <p id="section-boilerplate.1-2">
1130 This is a contribution to the RFC Series, independently of any
1131 other RFC stream. The RFC Editor has chosen to publish this
1132 document at its discretion and makes no statement about its value
1133 for implementation or deployment. Documents approved for
1134 publication by the RFC Editor are not candidates for any level of
1135 Internet Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1136 <p id="section-boilerplate.1-3">
1137 Information about the current status of this document, any
1138 errata, and how to provide feedback on it may be obtained at
1139 <span><a href="https://www.rfc-editor.org/info/rfc8756">https://www.rfc-editor.org/info/rfc8756</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1140 </section>
1141 </div>
1142 <div id="copyright">
1143 <section id="section-boilerplate.2">
1144 <h2 id="name-copyright-notice">
1145 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1146 </h2>
1147 <p id="section-boilerplate.2-1">
1148 Copyright (c) 2020 IETF Trust and the persons identified as the
1149 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1150 <p id="section-boilerplate.2-2">
1151 This document is subject to BCP 78 and the IETF Trust's Legal
1152 Provisions Relating to IETF Documents
1153 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1154 publication of this document. Please review these documents
1155 carefully, as they describe your rights and restrictions with
1156 respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1157 </section>
1158 </div>
1159 <div id="toc">
1160 <section id="section-toc.1">
1161 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1162 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1163 </h2>
1164 <nav class="toc"><ul class="toc ulEmpty">
1165 <li class="toc ulEmpty" id="section-toc.1-1.1">
1166 <p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
1167 <ul class="toc ulEmpty">
1168 <li class="toc ulEmpty" id="section-toc.1-1.1.2.1">
1169 <p id="section-toc.1-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
1170 </li>
1171 </ul>
1172 </li>
1173 <li class="toc ulEmpty" id="section-toc.1-1.2">
1174 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-the-commercial-national-sec" class="xref">The Commercial National Security Algorithm Suite</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1175 </li>
1176 <li class="toc ulEmpty" id="section-toc.1-1.3">
1177 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-requirements-and-assumption" class="xref">Requirements and Assumptions</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1178 </li>
1179 <li class="toc ulEmpty" id="section-toc.1-1.4">
1180 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-client-requirements-generat" class="xref">Client Requirements: Generating PKI Requests</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1181 <ul class="toc ulEmpty">
1182 <li class="toc ulEmpty" id="section-toc.1-1.4.2.1">
1183 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-tagged-certification-reques" class="xref">Tagged Certification Request</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
1184 </li>
1185 <li class="toc ulEmpty" id="section-toc.1-1.4.2.2">
1186 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-certificate-request-message" class="xref">Certificate Request Message</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p>
1187 </li>
1188 </ul>
1189 </li>
1190 <li class="toc ulEmpty" id="section-toc.1-1.5">
1191 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-ra-requirements" class="xref">RA Requirements</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1192 <ul class="toc ulEmpty">
1193 <li class="toc ulEmpty" id="section-toc.1-1.5.2.1">
1194 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-ra-processing-of-requests" class="xref">RA Processing of Requests</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
1195 </li>
1196 <li class="toc ulEmpty" id="section-toc.1-1.5.2.2">
1197 <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-ra-generated-pki-requests" class="xref">RA-Generated PKI Requests</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
1198 </li>
1199 <li class="toc ulEmpty" id="section-toc.1-1.5.2.3">
1200 <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-ra-generated-pki-responses" class="xref">RA-Generated PKI Responses</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p>
1201 </li>
1202 </ul>
1203 </li>
1204 <li class="toc ulEmpty" id="section-toc.1-1.6">
1205 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-ca-requirements" class="xref">CA Requirements</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1206 <ul class="toc ulEmpty">
1207 <li class="toc ulEmpty" id="section-toc.1-1.6.2.1">
1208 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-ca-processing-of-pki-reques" class="xref">CA Processing of PKI Requests</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
1209 </li>
1210 <li class="toc ulEmpty" id="section-toc.1-1.6.2.2">
1211 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-ca-generated-pki-responses" class="xref">CA-Generated PKI Responses</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p>
1212 </li>
1213 </ul>
1214 </li>
1215 <li class="toc ulEmpty" id="section-toc.1-1.7">
1216 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-client-requirements-process" class="xref">Client Requirements: Processing PKI Responses</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1217 </li>
1218 <li class="toc ulEmpty" id="section-toc.1-1.8">
1219 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-shared-secrets" class="xref">Shared-Secrets</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1220 </li>
1221 <li class="toc ulEmpty" id="section-toc.1-1.9">
1222 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
1223 </li>
1224 <li class="toc ulEmpty" id="section-toc.1-1.10">
1225 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
1226 </li>
1227 <li class="toc ulEmpty" id="section-toc.1-1.11">
1228 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
1229 <ul class="toc ulEmpty">
1230 <li class="toc ulEmpty" id="section-toc.1-1.11.2.1">
1231 <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.11.2.1.1" class="pilcrow">¶</a></p>
1232 </li>
1233 <li class="toc ulEmpty" id="section-toc.1-1.11.2.2">
1234 <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.11.2.2.1" class="pilcrow">¶</a></p>
1235 </li>
1236 </ul>
1237 </li>
1238 <li class="toc ulEmpty" id="section-toc.1-1.12">
1239 <p id="section-toc.1-1.12.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-scenarios" class="xref">Scenarios</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
1240 <ul class="toc ulEmpty">
1241 <li class="toc ulEmpty" id="section-toc.1-1.12.2.1">
1242 <p id="section-toc.1-1.12.2.1.1"><a href="#section-a.1" class="xref">A.1</a>.  <a href="#name-initial-enrollment" class="xref">Initial Enrollment</a><a href="#section-toc.1-1.12.2.1.1" class="pilcrow">¶</a></p>
1243 </li>
1244 <li class="toc ulEmpty" id="section-toc.1-1.12.2.2">
1245 <p id="section-toc.1-1.12.2.2.1"><a href="#section-a.2" class="xref">A.2</a>.  <a href="#name-rekey" class="xref">Rekey</a><a href="#section-toc.1-1.12.2.2.1" class="pilcrow">¶</a></p>
1246 </li>
1247 </ul>
1248 </li>
1249 <li class="toc ulEmpty" id="section-toc.1-1.13">
1250 <p id="section-toc.1-1.13.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
1251 </li>
1252 </ul>
1253 </nav>
1254 </section>
1255 </div>
1256 <div id="intro">
1257 <section id="section-1">
1258 <h2 id="name-introduction">
1259 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1260 </h2>
1261 <p id="section-1-1">This document specifies a profile of the Certificate Management over CMS (CMC) protocol to comply with the United States National Security Agency's Commercial National Security Algorithm (CNSA) Suite <span>[<a href="#CNSA" class="xref">CNSA</a>]</span>. The profile applies to the capabilities, configuration, and operation of all components of US National Security Systems <span>[<a href="#SP80059" class="xref">SP80059</a>]</span>. It is also appropriate for all other US Government systems that process high-value information. It is made publicly available for use by developers and operators of these and any other system deployments.<a href="#section-1-1" class="pilcrow">¶</a></p>
1262 <p id="section-1-2">This document does not define any new cryptographic algorithm suites; instead, it defines a CNSA-compliant profile of CMC. CMC is defined in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>, <span>[<a href="#RFC5273" class="xref">RFC5273</a>]</span>, and <span>[<a href="#RFC5274" class="xref">RFC5274</a>]</span> and is updated by <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>. This document profiles CMC to manage X.509 public key certificates in compliance with the CNSA Suite Certificate and Certificate Revocation List (CRL) profile <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>. This document specifically focuses on defining CMC interactions for both the initial enrollment and rekey of CNSA Suite public key certificates between a client and a Certification Authority (CA). One or more Registration Authorities (RAs) may act as intermediaries between the client and the CA. This profile may be further tailored by specific communities to meet their needs. Specific communities will also define certificate policies that implementations need to comply with.<a href="#section-1-2" class="pilcrow">¶</a></p>
1263 <div id="terms">
1264 <section id="section-1.1">
1265 <h3 id="name-terminology">
1266 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1267 </h3>
1268 <p id="section-1.1-1">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>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1269 <p id="section-1.1-2">The terminology in <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-2.1" class="relref">Section 2.1</a></span> applies to this profile.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
1270 <p id="section-1.1-3">The term "certificate request" is used to refer to a single PKCS #10
1271 or Certificate Request Message Format (CRMF) structure. All PKI Requests are Full PKI Requests, and all PKI Responses are Full PKI Responses; the respective set of terms should be interpreted synonymously in this document.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
1272 </section>
1273 </div>
1274 </section>
1275 </div>
1276 <div id="cnsa">
1277 <section id="section-2">
1278 <h2 id="name-the-commercial-national-sec">
1279 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-the-commercial-national-sec" class="section-name selfRef">The Commercial National Security Algorithm Suite</a>
1280 </h2>
1281 <p id="section-2-1">The National Security Agency (NSA) profiles commercial cryptographic algorithms and protocols as part of its mission to support secure, interoperable communications for US Government National Security Systems. To this end, it publishes guidance both to assist with the US Government transition to new algorithms and to provide vendors -- and the Internet community in general -- with information concerning their proper use and configuration within the scope of US Government National Security Systems.<a href="#section-2-1" class="pilcrow">¶</a></p>
1282 <p id="section-2-2">Recently, cryptographic transition plans have become overshadowed by
1283 the prospect of the development of a cryptographically relevant quantum
1284 computer. The NSA has established the Commercial National Security
1285 Algorithm (CNSA) Suite to provide vendors and IT users near-term
1286 flexibility in meeting their cybersecurity interoperability
1287 requirements. The purpose behind this flexibility is to avoid having vendors and customers make two major transitions in a relatively short timeframe, as we anticipate a need to shift to quantum-resistant cryptography in the near future.<a href="#section-2-2" class="pilcrow">¶</a></p>
1288 <p id="section-2-3">The NSA is authoring a set of RFCs, including this one, to provide updated guidance concerning the use of certain commonly available commercial algorithms in IETF protocols. These RFCs can be used in conjunction with other RFCs and cryptographic guidance (e.g., NIST Special Publications) to properly protect Internet traffic and data-at-rest for US Government National Security Systems.<a href="#section-2-3" class="pilcrow">¶</a></p>
1289 </section>
1290 </div>
1291 <div id="reqts">
1292 <section id="section-3">
1293 <h2 id="name-requirements-and-assumption">
1294 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-requirements-and-assumption" class="section-name selfRef">Requirements and Assumptions</a>
1295 </h2>
1296 <p id="section-3-1">Elliptic Curve Digital Signature Algorithm (ECDSA) and Elliptic Curve
1297 Diffie-Hellman (ECDH) key pairs are on the P-384 curve. FIPS 186-4 <span>[<a href="#FIPS186" class="xref">FIPS186</a>]</span>, Appendix B.4 provides useful guidance for elliptic curve key pair generation that <span class="bcp14">SHOULD</span> be followed by systems that conform to this document.<a href="#section-3-1" class="pilcrow">¶</a></p>
1298 <p id="section-3-2">RSA key pairs (public, private) are identified by the modulus size expressed in bits; RSA-3072 and RSA-4096 are computed using moduli of 3072 bits and 4096 bits, respectively.<a href="#section-3-2" class="pilcrow">¶</a></p>
1299 <p id="section-3-3">RSA signature key pairs used in CNSA Suite-compliant implementations are either RSA-3072 or RSA-4096. The RSA exponent e <span class="bcp14">MUST</span> satisfy 2<sup>16</sup> &lt; e &lt; 2<sup>256</sup> and be odd per <span>[<a href="#FIPS186" class="xref">FIPS186</a>]</span>.<a href="#section-3-3" class="pilcrow">¶</a></p>
1300 <p id="section-3-4">It is recognized that, while the vast majority of RSA signatures are currently made using the RSASSA-PKCS1-v1_5 algorithm, the preferred RSA signature scheme for new applications is RSASSA-PSS. CNSA Suite-compliant X.509 certificates will be issued in accordance with <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>, and while those certificates must be signed and validated using RSASSA-PKCS1-v1_5, the subject's private key can be used to generate signatures of either signing scheme. Where use of RSASSA-PSS is indicated in this document, the following parameters apply:<a href="#section-3-4" class="pilcrow">¶</a></p>
1301 <ul>
1302 <li id="section-3-5.1">The hash algorithm <span class="bcp14">MUST</span> be id-sha384 as defined in <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span>;<a href="#section-3-5.1" class="pilcrow">¶</a>
1303 </li>
1304 <li id="section-3-5.2">The mask generation function <span class="bcp14">MUST</span> use the algorithm identifier mfg1SHA384Identifier as defined in <span>[<a href="#RFC4055" class="xref">RFC4055</a>]</span>;<a href="#section-3-5.2" class="pilcrow">¶</a>
1305 </li>
1306 <li id="section-3-5.3">The salt length <span class="bcp14">MUST</span> be 48 octets; and<a href="#section-3-5.3" class="pilcrow">¶</a>
1307 </li>
1308 <li id="section-3-5.4">The trailerField <span class="bcp14">MUST</span> have value 1.<a href="#section-3-5.4" class="pilcrow">¶</a>
1309 </li>
1310 </ul>
1311 <p id="section-3-6">
1312
1313 These parameters will not appear in a certificate and <span class="bcp14">MUST</span> be securely
1314 communicated with the signature, as required by <span><a href="https://www.rfc-editor.org/rfc/rfc4056#section-2.2" class="relref">Section 2.2</a> of [<a href="#RFC4056" class="xref">RFC4056</a>]</span>. Application developers are obliged to ensure that the chosen signature scheme is appropriate for the application and will be interoperable within the intended operating scope of the application.<a href="#section-3-6" class="pilcrow">¶</a></p>
1315 <p id="section-3-7">This document assumes that the required trust anchors have been securely provisioned to the client and, when applicable, to any RAs.<a href="#section-3-7" class="pilcrow">¶</a></p>
1316 <p id="section-3-8">All requirements in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>, <span>[<a href="#RFC5273" class="xref">RFC5273</a>]</span>, <span>[<a href="#RFC5274" class="xref">RFC5274</a>]</span>, and <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span> apply, except where overridden by this profile.<a href="#section-3-8" class="pilcrow">¶</a></p>
1317 <p id="section-3-9">This profile was developed with the scenarios described in <a href="#scenarios" class="xref">Appendix A</a> in mind. However, use of this profile is not limited to just those scenarios.<a href="#section-3-9" class="pilcrow">¶</a></p>
1318 <p id="section-3-10">The term "client" in this profile typically refers to an end-entity. However, it may instead refer to a third party acting on the end-entity's behalf. The client may or may not be the entity that actually generates the key pair, but it does perform the CMC protocol interactions with the RA and/or CA. For example, the client may be a token management system that communicates with a cryptographic token through an out-of-band secure protocol.<a href="#section-3-10" class="pilcrow">¶</a></p>
1319 <p id="section-3-11">This profile uses the term "rekey" in the same manner as CMC does (defined in <span><a href="https://www.rfc-editor.org/rfc/rfc5272#section-2" class="relref">Section 2</a> of [<a href="#RFC5272" class="xref">RFC5272</a>]</span>). The profile makes no specific statements about the ability to do "renewal" operations; however, the statements applicable to "rekey" should be applied to "renewal" as well.<a href="#section-3-11" class="pilcrow">¶</a></p>
1320 <p id="section-3-12">This profile may be used to manage RA and/or CA certificates. In that case, the RA and/or CA whose certificate is being managed is considered to be the end-entity.<a href="#section-3-12" class="pilcrow">¶</a></p>
1321 <p id="section-3-13">This profile does not discuss key establishment certification requests from cryptographic modules that cannot generate a one-time signature with a key establishment key for proof-of-possession purposes. In that case, a separate profile would be needed to define the use of another proof-of-possession technique.<a href="#section-3-13" class="pilcrow">¶</a></p>
1322 </section>
1323 </div>
1324 <div id="client-reqts-gen">
1325 <section id="section-4">
1326 <h2 id="name-client-requirements-generat">
1327 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-client-requirements-generat" class="section-name selfRef">Client Requirements: Generating PKI Requests</a>
1328 </h2>
1329 <p id="section-4-1">This section specifies the conventions employed when a client requests a certificate from a Public Key Infrastructure (PKI).<a href="#section-4-1" class="pilcrow">¶</a></p>
1330 <p id="section-4-2">The Full PKI Request <span class="bcp14">MUST</span> be used; it <span class="bcp14">MUST</span> be encapsulated in a SignedData; and the SignedData <span class="bcp14">MUST</span> be constructed in accordance with <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>. The PKIData content type defined in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span> is used with the following additional requirements:<a href="#section-4-2" class="pilcrow">¶</a></p>
1331 <ul>
1332 <li id="section-4-3.1">
1333 <p id="section-4-3.1.1">controlSequence <span class="bcp14">SHOULD</span> be present.<a href="#section-4-3.1.1" class="pilcrow">¶</a></p>
1334 <ul>
1335 <li id="section-4-3.1.2.1">TransactionId and SenderNonce <span class="bcp14">SHOULD</span> be included. Other CMC controls <span class="bcp14">MAY</span> be included.<a href="#section-4-3.1.2.1" class="pilcrow">¶</a>
1336 </li>
1337 <li id="section-4-3.1.2.2">
1338 <p id="section-4-3.1.2.2.1">If the request is being authenticated using a shared-secret, then Identity Proof Version 2 control <span class="bcp14">MUST</span> be included with the following constraints:<a href="#section-4-3.1.2.2.1" class="pilcrow">¶</a></p>
1339 <ul>
1340 <li id="section-4-3.1.2.2.2.1">hashAlgId <span class="bcp14">MUST</span> be id-sha384 for all certification requests (algorithm OIDs are defined in <span>[<a href="#RFC5754" class="xref">RFC5754</a>]</span>).<a href="#section-4-3.1.2.2.2.1" class="pilcrow">¶</a>
1341 </li>
1342 <li id="section-4-3.1.2.2.2.2">macAlgId <span class="bcp14">MUST</span> be HMAC-SHA384 (the Hashed
1343 Message Authentication Code (HMAC) algorithm is defined in <span>[<a href="#RFC4231" class="xref">RFC4231</a>]</span>).<a href="#section-4-3.1.2.2.2.2" class="pilcrow">¶</a>
1344 </li>
1345 </ul>
1346 </li>
1347 <li id="section-4-3.1.2.3">If the subject name included in the certification request is NULL
1348 or otherwise does not uniquely identify the end-entity, then the
1349 POP Link Random control <span class="bcp14">MUST</span> be included, and the
1350 POP Link Witness Version 2 control <span class="bcp14">MUST</span> be included
1351 in the inner PKCS #10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> or
1352 Certificate Request Message Format (CRMF) <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span> request as described in Sections <a href="#tgd-cert-reqst" class="xref">4.1</a> and <a href="#cert-reqst-msg" class="xref">4.2</a>.<a href="#section-4-3.1.2.3" class="pilcrow">¶</a>
1353 </li>
1354 </ul>
1355 </li>
1356 <li id="section-4-3.2">reqSequence <span class="bcp14">MUST</span> be present. It <span class="bcp14">MUST</span> include at least one tcr (see <a href="#tgd-cert-reqst" class="xref">Section 4.1</a>) or crm (see <a href="#cert-reqst-msg" class="xref">Section 4.2</a>) TaggedRequest. Support for the orm choice is <span class="bcp14">OPTIONAL</span>.<a href="#section-4-3.2" class="pilcrow">¶</a>
1357 </li>
1358 </ul>
1359 <p id="section-4-4">The private signing key used to generate the encapsulating SignedData <span class="bcp14">MUST</span> correspond to the public key of an existing signature certificate unless an appropriate signature certificate does not yet exist, such as during initial enrollment.<a href="#section-4-4" class="pilcrow">¶</a></p>
1360 <p id="section-4-5">The encapsulating SignedData <span class="bcp14">MUST</span> be generated using SHA-384 and either ECDSA on P-384 or RSA using either RSASSA-PKCS1-v1_5 or RSASSA-PSS with an RSA-3072 or RSA-4096 key.<a href="#section-4-5" class="pilcrow">¶</a></p>
1361 <p id="section-4-6">If an appropriate signature certificate does not yet exist and if a Full PKI Request includes one or more certification requests and is authenticated using a shared-secret (because no appropriate certificate exists yet to authenticate the request), the Full PKI Request <span class="bcp14">MUST</span> be signed using the private key corresponding to the public key of one of the requested certificates. When necessary (i.e., because there is no existing signature certificate and there is no signature certification request included), a Full PKI Request <span class="bcp14">MAY</span> be signed using a key pair intended for use in a key establishment certificate. However, servers are not required to allow this behavior.<a href="#section-4-6" class="pilcrow">¶</a></p>
1362 <div id="tgd-cert-reqst">
1363 <section id="section-4.1">
1364 <h3 id="name-tagged-certification-reques">
1365 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-tagged-certification-reques" class="section-name selfRef">Tagged Certification Request</a>
1366 </h3>
1367 <p id="section-4.1-1">The reqSequence tcr choice conveys PKCS #10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> syntax. The CertificateRequest <span class="bcp14">MUST</span>
1368 comply with <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-3.2.1.2.1" class="relref">Section 3.2.1.2.1</a></span>, with the following additional requirements:<a href="#section-4.1-1" class="pilcrow">¶</a></p>
1369 <ul>
1370 <li id="section-4.1-2.1">
1371 <p id="section-4.1-2.1.1">certificationRequestInfo:<a href="#section-4.1-2.1.1" class="pilcrow">¶</a></p>
1372 <ul>
1373 <li id="section-4.1-2.1.2.1">subjectPublicKeyInfo <span class="bcp14">MUST</span> be set as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8603#section-5.4" class="relref">Section 5.4</a> of [<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-4.1-2.1.2.1" class="pilcrow">¶</a>
1374 </li>
1375 <li id="section-4.1-2.1.2.2">
1376 <p id="section-4.1-2.1.2.2.1">Attributes:<a href="#section-4.1-2.1.2.2.1" class="pilcrow">¶</a></p>
1377 <ul>
1378 <li id="section-4.1-2.1.2.2.2.1">
1379 <p id="section-4.1-2.1.2.2.2.1.1">The ExtensionReq attribute <span class="bcp14">MUST</span> be included with its contents as follows:<a href="#section-4.1-2.1.2.2.2.1.1" class="pilcrow">¶</a></p>
1380 <ul>
1381 <li id="section-4.1-2.1.2.2.2.1.2.1">The keyUsage extension <span class="bcp14">MUST</span> be included, and it <span class="bcp14">MUST</span> be set as defined in <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-4.1-2.1.2.2.2.1.2.1" class="pilcrow">¶</a>
1382 </li>
1383 <li id="section-4.1-2.1.2.2.2.1.2.2">For rekey requests, the SubjectAltName extension <span class="bcp14">MUST</span> be included and set equal to the SubjectAltName of the certificate that is being used to sign the SignedData encapsulating the request (i.e., not the certificate being rekeyed) if the subject field of the certificate being used to generate the signature is NULL.<a href="#section-4.1-2.1.2.2.2.1.2.2" class="pilcrow">¶</a>
1384 </li>
1385 <li id="section-4.1-2.1.2.2.2.1.2.3">Other extension requests <span class="bcp14">MAY</span> be included as desired.<a href="#section-4.1-2.1.2.2.2.1.2.3" class="pilcrow">¶</a>
1386 </li>
1387 </ul>
1388 </li>
1389 <li id="section-4.1-2.1.2.2.2.2">The ChangeSubjectName attribute, as defined in <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>, <span class="bcp14">MUST</span> be included if the Full PKI Request encapsulating this Tagged Certification Request is being signed by a key for which a certificate currently exists and the existing certificate's subject field or SubjectAltName extension does not match the desired subject name or SubjectAltName extension of this certification request.<a href="#section-4.1-2.1.2.2.2.2" class="pilcrow">¶</a>
1390 </li>
1391 <li id="section-4.1-2.1.2.2.2.3">The POP Link Witness Version 2 attribute <span class="bcp14">MUST</span> be included if the request is being authenticated using a shared-secret and the subject name in the certification request is NULL or otherwise does not uniquely identify the end-entity. In the POP Link Witness Version 2 attribute, keyGenAlgorithm <span class="bcp14">MUST</span> be id-sha384 for certification requests, as defined in <span>[<a href="#RFC5754" class="xref">RFC5754</a>]</span>; macAlgorithm <span class="bcp14">MUST</span> be HMAC-SHA384, as defined in <span>[<a href="#RFC4231" class="xref">RFC4231</a>]</span>.<a href="#section-4.1-2.1.2.2.2.3" class="pilcrow">¶</a>
1392 </li>
1393 </ul>
1394 </li>
1395 <li id="section-4.1-2.1.2.3">signatureAlgorithm <span class="bcp14">MUST</span> be ecdsa-with-sha384 for P-384 certification requests and sha384WithRSAEncryption or id-RSASSA-PSS for RSA-3072 and RSA-4096 certification requests.<a href="#section-4.1-2.1.2.3" class="pilcrow">¶</a>
1396 </li>
1397 <li id="section-4.1-2.1.2.4">signature <span class="bcp14">MUST</span> be generated using the private key corresponding to the public key in the CertificationRequestInfo for both signature and key establishment certification requests. The signature provides proof-of-possession of the private key to the CA.<a href="#section-4.1-2.1.2.4" class="pilcrow">¶</a>
1398 </li>
1399 </ul>
1400 </li>
1401 </ul>
1402 </section>
1403 </div>
1404 <div id="cert-reqst-msg">
1405 <section id="section-4.2">
1406 <h3 id="name-certificate-request-message">
1407 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-certificate-request-message" class="section-name selfRef">Certificate Request Message</a>
1408 </h3>
1409 <p id="section-4.2-1">The reqSequence crm choice conveys Certificate Request Message
1410 Format (CRMF) <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span>
1411 syntax. The CertReqMsg <span class="bcp14">MUST</span> comply with <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-3.2.1.2.2" class="relref">Section 3.2.1.2.2</a></span>, with the following additional requirements:<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1412 <ul>
1413 <li id="section-4.2-2.1">popo <span class="bcp14">MUST</span> be included using the signature (POPOSigningKey)
1414 proof-of-possession choice and be set as defined in <span>[<a href="#RFC4211" class="xref">RFC4211</a>], <a href="https://www.rfc-editor.org/rfc/rfc4211#section-4.1" class="relref">Section 4.1</a></span> for both signature and key establishment certification requests. The POPOSigningKey poposkInput field <span class="bcp14">MUST</span> be omitted. The POPOSigningKey algorithmIdentifier <span class="bcp14">MUST</span> be ecdsa-with-sha384 for P-384 certification requests and sha384WithRSAEncryption or id-RSASSA-PSS for RSA-3072 and RSA-4096 certification requests. The signature <span class="bcp14">MUST</span> be generated using the private key corresponding to the public key in the CertTemplate.<a href="#section-4.2-2.1" class="pilcrow">¶</a>
1415 </li>
1416 </ul>
1417 <p id="section-4.2-3">The CertTemplate <span class="bcp14">MUST</span> comply with <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-3.2.1.2.2" class="relref">Section 3.2.1.2.2</a></span>, with the following additional requirements:<a href="#section-4.2-3" class="pilcrow">¶</a></p>
1418 <ul>
1419 <li id="section-4.2-4.1">If version is included, it <span class="bcp14">MUST</span> be set to 2 as defined in
1420 <span><a href="https://www.rfc-editor.org/rfc/rfc8603#section-5.3" class="relref">Section 5.3</a> of [<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-4.2-4.1" class="pilcrow">¶</a>
1421 </li>
1422 <li id="section-4.2-4.2">publicKey <span class="bcp14">MUST</span> be set as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8603#section-5.4" class="relref">Section 5.4</a> of [<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-4.2-4.2" class="pilcrow">¶</a>
1423 </li>
1424 <li id="section-4.2-4.3">
1425 <p id="section-4.2-4.3.1">Extensions:<a href="#section-4.2-4.3.1" class="pilcrow">¶</a></p>
1426 <ul>
1427 <li id="section-4.2-4.3.2.1">The keyUsage extension <span class="bcp14">MUST</span> be included, and it <span class="bcp14">MUST</span> be set as defined in <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-4.2-4.3.2.1" class="pilcrow">¶</a>
1428 </li>
1429 <li id="section-4.2-4.3.2.2">For rekey requests, the SubjectAltName extension <span class="bcp14">MUST</span> be included and set equal to the SubjectAltName of the certificate that is being used to sign the SignedData encapsulating the request (i.e., not the certificate being rekeyed) if the subject name of the certificate being used to generate the signature is NULL.<a href="#section-4.2-4.3.2.2" class="pilcrow">¶</a>
1430 </li>
1431 <li id="section-4.2-4.3.2.3">Other extension requests <span class="bcp14">MAY</span> be included as desired.<a href="#section-4.2-4.3.2.3" class="pilcrow">¶</a>
1432 </li>
1433 </ul>
1434 </li>
1435 <li id="section-4.2-4.4">
1436 <p id="section-4.2-4.4.1">Controls:<a href="#section-4.2-4.4.1" class="pilcrow">¶</a></p>
1437 <ul>
1438 <li id="section-4.2-4.4.2.1">The ChangeSubjectName attribute, as defined in <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>, <span class="bcp14">MUST</span> be included if the Full PKI Request encapsulating this Tagged Certification Request is being signed by a key for which a certificate currently exists and the existing certificate's subject name or SubjectAltName extension does not match the desired subject name or SubjectAltName extension of this certification request.<a href="#section-4.2-4.4.2.1" class="pilcrow">¶</a>
1439 </li>
1440 <li id="section-4.2-4.4.2.2">The POP Link Witness Version 2 attribute <span class="bcp14">MUST</span> be included if the request is being authenticated using a shared-secret and the subject name in the certification request is NULL or otherwise does not uniquely identify the end-entity. In the POP Link Witness Version 2 attribute, keyGenAlgorithm <span class="bcp14">MUST</span> be id-sha384 for certification requests; macAlgorithm <span class="bcp14">MUST</span> be HMAC-SHA384 when keyGenAlgorithm is id-sha384.<a href="#section-4.2-4.4.2.2" class="pilcrow">¶</a>
1441 </li>
1442 </ul>
1443 </li>
1444 </ul>
1445 </section>
1446 </div>
1447 </section>
1448 </div>
1449 <div id="ra_reqts">
1450 <section id="section-5">
1451 <h2 id="name-ra-requirements">
1452 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-ra-requirements" class="section-name selfRef">RA Requirements</a>
1453 </h2>
1454 <p id="section-5-1">This section addresses the optional case where one or more RAs act as
1455 intermediaries between clients and a CA as described in <span><a href="https://www.rfc-editor.org/rfc/rfc5272#section-7" class="relref">Section 7</a> of [<a href="#RFC5272" class="xref">RFC5272</a>]</span>. In this section, the term "client" refers to the entity from which the RA received the PKI Request. This section is only applicable to RAs.<a href="#section-5-1" class="pilcrow">¶</a></p>
1456 <div id="ra-proc-reqst">
1457 <section id="section-5.1">
1458 <h3 id="name-ra-processing-of-requests">
1459 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-ra-processing-of-requests" class="section-name selfRef">RA Processing of Requests</a>
1460 </h3>
1461 <p id="section-5.1-1">RAs conforming to this document <span class="bcp14">MUST</span> ensure that only the permitted signature, hash, and MAC algorithms described throughout this profile are used in requests; if they are not, the RA <span class="bcp14">MUST</span> reject those requests. The RA <span class="bcp14">SHOULD</span> return a CMCFailInfo with the value of badAlg <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
1462 <p id="section-5.1-2">When processing end-entity-generated SignedData objects, RAs <span class="bcp14">MUST NOT</span> perform Cryptographic Message Syntax (CMS) Content Constraints (CCC) certificate extension processing <span>[<a href="#RFC6010" class="xref">RFC6010</a>]</span>.<a href="#section-5.1-2" class="pilcrow">¶</a></p>
1463 <p id="section-5.1-3">Other RA processing is performed as described in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
1464 </section>
1465 </div>
1466 <div id="ra-gend-pki-reqst">
1467 <section id="section-5.2">
1468 <h3 id="name-ra-generated-pki-requests">
1469 <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-ra-generated-pki-requests" class="section-name selfRef">RA-Generated PKI Requests</a>
1470 </h3>
1471 <p id="section-5.2-1">RAs mediate the certificate request process by collecting client requests in batches. The RA <span class="bcp14">MUST</span> encapsulate client-generated PKI Requests in a new RA-signed PKI Request, it <span class="bcp14">MUST</span> create a Full PKI Request encapsulated in a SignedData, and the SignedData <span class="bcp14">MUST</span> be constructed in accordance with <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>. The PKIData content type complies with <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span> with the following additional requirements:<a href="#section-5.2-1" class="pilcrow">¶</a></p>
1472 <ul>
1473 <li id="section-5.2-2.1">controlSequence <span class="bcp14">MUST</span> be present. It
1474 <span class="bcp14">MUST</span> include the following CMC controls: Transaction
1475 ID, Sender Nonce, and Batch Requests. Other appropriate CMC controls
1476 <span class="bcp14">MAY</span> be included.<a href="#section-5.2-2.1" class="pilcrow">¶</a>
1477 </li>
1478 <li id="section-5.2-2.2">cmsSequence <span class="bcp14">MUST</span> be present. It contains the original, unmodified request(s) received from the client.<a href="#section-5.2-2.2" class="pilcrow">¶</a>
1479 </li>
1480 </ul>
1481 <div id="section-5.2-3">
1482 <pre class="sourcecode">
1483 SignedData (applied by the RA)
1484 PKIData
1485 controlSequence (Transaction ID, Sender Nonce,
1486 Batch Requests)
1487 cmsSequence
1488 SignedData (applied by client)
1489 PKIData
1490 controlSequence (Transaction ID, Sender Nonce)
1491 reqSequence
1492 TaggedRequest
1493 {TaggedRequest}
1494 {SignedData (second client request)
1495 PKIData...}
1496 </pre><a href="#section-5.2-3" class="pilcrow">¶</a>
1497 </div>
1498 <p id="section-5.2-4">Authorization to sign RA-generated Full PKI Requests
1499 <span class="bcp14">SHOULD</span> be indicated in the RA certificate by inclusion
1500 of the id-kp-cmcRA Extended Key Usage (EKU) from <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>. The RA certificate <span class="bcp14">MAY</span> also include
1501 the CCC certificate extension <span>[<a href="#RFC6010" class="xref">RFC6010</a>]</span>, or it <span class="bcp14">MAY</span> indicate authorization
1502 through inclusion of the CCC certificate extension alone. The RA
1503 certificate may also be authorized through the local configuration.<a href="#section-5.2-4" class="pilcrow">¶</a></p>
1504 <p id="section-5.2-5">If the RA is authorized via the CCC extension, then the CCC extension <span class="bcp14">MUST</span> include the object identifier for the PKIData content type. CCC <span class="bcp14">SHOULD</span> be included if constraints are to be placed on the content types generated.<a href="#section-5.2-5" class="pilcrow">¶</a></p>
1505 <p id="section-5.2-6">The outer SignedData <span class="bcp14">MUST</span> be generated using SHA-384 and either ECDSA on P-384 or RSA using RSASSA-PKCS1-v1_5 or RSASSA-PSS with an RSA-3072 or RSA-4096 key.<a href="#section-5.2-6" class="pilcrow">¶</a></p>
1506 <p id="section-5.2-7">If the Full PKI Response is a successful response to a PKI Request that only contained a Get Certificate or Get CRL control, then the algorithm used in the response <span class="bcp14">MUST</span> match the algorithm used in the request.<a href="#section-5.2-7" class="pilcrow">¶</a></p>
1507 </section>
1508 </div>
1509 <div id="ra-gend-resp">
1510 <section id="section-5.3">
1511 <h3 id="name-ra-generated-pki-responses">
1512 <a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-ra-generated-pki-responses" class="section-name selfRef">RA-Generated PKI Responses</a>
1513 </h3>
1514 <p id="section-5.3-1">In order for an RA certificate using the CCC certificate extension to be authorized to generate responses, the object identifier for the PKIResponse content type must be present in the CCC certificate extension.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
1515 </section>
1516 </div>
1517 </section>
1518 </div>
1519 <div id="ca-reqts">
1520 <section id="section-6">
1521 <h2 id="name-ca-requirements">
1522 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-ca-requirements" class="section-name selfRef">CA Requirements</a>
1523 </h2>
1524 <p id="section-6-1">This section specifies the requirements for CAs that receive PKI Requests and generate PKI Responses.<a href="#section-6-1" class="pilcrow">¶</a></p>
1525 <div id="ca-proc-reqst">
1526 <section id="section-6.1">
1527 <h3 id="name-ca-processing-of-pki-reques">
1528 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-ca-processing-of-pki-reques" class="section-name selfRef">CA Processing of PKI Requests</a>
1529 </h3>
1530 <p id="section-6.1-1">CAs conforming to this document <span class="bcp14">MUST</span> ensure that
1531 only the permitted signature, hash, and MAC algorithms described
1532 throughout this profile are used in requests; if they are not, the CA
1533 <span class="bcp14">MUST</span> reject those requests. The CA
1534 <span class="bcp14">SHOULD</span> return a CMCStatusInfoV2 control with a CMCStatus of failed and a CMCFailInfo with the value of badAlg <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
1535 <p id="section-6.1-2">For requests involving an RA (i.e., batched requests), the CA
1536 <span class="bcp14">MUST</span> verify the RA's authorization. The following
1537 certificate fields <span class="bcp14">MUST NOT</span> be modifiable using the
1538 Modify Certification Request control: publicKey and the keyUsage
1539 extension. The request <span class="bcp14">MUST</span> be rejected if an attempt
1540 to modify those certification request fields is present. The CA
1541 <span class="bcp14">SHOULD</span> return a CMCStatusInfoV2 control with a CMCStatus of failed and a CMCFailInfo with a value of badRequest.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
1542 <p id="section-6.1-3">When processing end-entity-generated SignedData objects, CAs <span class="bcp14">MUST NOT</span> perform CCC certificate extension processing <span>[<a href="#RFC6010" class="xref">RFC6010</a>]</span>.<a href="#section-6.1-3" class="pilcrow">¶</a></p>
1543 <p id="section-6.1-4">If a client-generated PKI Request includes the ChangeSubjectName
1544 attribute as described in <a href="#tgd-cert-reqst" class="xref">Section 4.1</a> or <a href="#cert-reqst-msg" class="xref">4.2</a>
1545 above, the CA <span class="bcp14">MUST</span> ensure that name change is
1546 authorized. The mechanism for ensuring that the name change is
1547 authorized is out of scope. A CA that performs this check and finds
1548 that the name change is not authorized <span class="bcp14">MUST</span> reject the
1549 PKI Request. The CA <span class="bcp14">SHOULD</span> return an Extended CMC
1550 Status Info control (CMCStatusInfoV2) with a CMCStatus of failed.<a href="#section-6.1-4" class="pilcrow">¶</a></p>
1551 <p id="section-6.1-5">Other processing of PKIRequests is performed as described in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>.<a href="#section-6.1-5" class="pilcrow">¶</a></p>
1552 </section>
1553 </div>
1554 <div id="ca-gend-resp">
1555 <section id="section-6.2">
1556 <h3 id="name-ca-generated-pki-responses">
1557 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-ca-generated-pki-responses" class="section-name selfRef">CA-Generated PKI Responses</a>
1558 </h3>
1559 <p id="section-6.2-1">CAs send PKI Responses to both client-generated requests and RA-generated requests. If a Full PKI Response is returned in direct response to a client-generated request, it <span class="bcp14">MUST</span> be encapsulated in a SignedData, and the SignedData <span class="bcp14">MUST</span> be constructed in accordance with <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
1560 <p id="section-6.2-2">If the PKI Response is in response to an RA-generated PKI Request, then the above PKI Response is encapsulated in another CA-generated PKI Response. That PKI Response <span class="bcp14">MUST</span> be encapsulated in a SignedData, and the SignedData <span class="bcp14">MUST</span> be constructed in accordance with <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>. The above PKI Response is placed in the encapsulating PKI Response cmsSequence field. The other fields are as above with the addition of the batch response control in controlSequence. The following illustrates a successful CA response to an RA-encapsulated PKI Request, both of which include Transaction IDs and Nonces:<a href="#section-6.2-2" class="pilcrow">¶</a></p>
1561 <div id="section-6.2-3">
1562 <pre class="sourcecode">
1563 SignedData (applied by the CA)
1564 PKIResponse
1565 controlSequence (Transaction ID, Sender Nonce, Recipient
1566 Nonce, Batch Response)
1567 cmsSequence
1568 SignedData (applied by CA and includes returned
1569 certificates)
1570 PKIResponse
1571 controlSequence (Transaction ID, Sender Nonce,
1572 Recipient Nonce)
1573 </pre><a href="#section-6.2-3" class="pilcrow">¶</a>
1574 </div>
1575 <p id="section-6.2-4">The same private key used to sign certificates <span class="bcp14">MUST NOT</span> be used to sign Full PKI Response messages. Instead, a separate certificate indicating authorization to sign CMC responses <span class="bcp14">MUST</span> be used.<a href="#section-6.2-4" class="pilcrow">¶</a></p>
1576 <p id="section-6.2-5">Authorization to sign Full PKI Responses <span class="bcp14">SHOULD</span> be indicated in the CA certificate by inclusion of the id-kp-cmcCA EKU from <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>. The CA certificate <span class="bcp14">MAY</span> also include the CCC certificate extension <span>[<a href="#RFC6010" class="xref">RFC6010</a>]</span>, or it <span class="bcp14">MAY</span> indicate authorization through inclusion of the CCC certificate extension alone. The CA certificate may also be authorized through local configuration.<a href="#section-6.2-5" class="pilcrow">¶</a></p>
1577 <p id="section-6.2-6">In order for a CA certificate using the CCC certificate extension to be authorized to generate responses, the object identifier for the PKIResponse content type must be present in the CCC certificate extension. CCC <span class="bcp14">SHOULD</span> be included if constraints are to be placed on the content types generated.<a href="#section-6.2-6" class="pilcrow">¶</a></p>
1578 <p id="section-6.2-7">Signatures applied to individual certificates are as required in <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-6.2-7" class="pilcrow">¶</a></p>
1579 <p id="section-6.2-8">The signature on the SignedData of a successful response to a
1580 client-generated request, or each individual inner SignedData on the
1581 successful response to an RA-generated request, <span class="bcp14">MUST</span> be
1582 generated using SHA-384 and either ECDSA on P-384 or RSA using
1583 RSASSA-PKCS1-v1_5 or RSASSA-PSS with an RSA-3072 or RSA-4096 key. An
1584 unsuccessful response <span class="bcp14">MUST</span> be signed using the same key
1585 type and algorithm that signed the request.<a href="#section-6.2-8" class="pilcrow">¶</a></p>
1586 <p id="section-6.2-9">The outer SignedData on the Full PKI Response to any RA-generated
1587 PKI Request <span class="bcp14">MUST</span> be signed with the same key type and algorithm that signed the request.<a href="#section-6.2-9" class="pilcrow">¶</a></p>
1588 <p id="section-6.2-10">The SignedData on a successful Full PKI Response to a PKI Request
1589 that only contained a Get Certificate or Get CRL control
1590 <span class="bcp14">MUST</span> be signed with the same key type and algorithm that signed the request.<a href="#section-6.2-10" class="pilcrow">¶</a></p>
1591 </section>
1592 </div>
1593 </section>
1594 </div>
1595 <div id="client-reqts-proc">
1596 <section id="section-7">
1597 <h2 id="name-client-requirements-process">
1598 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-client-requirements-process" class="section-name selfRef">Client Requirements: Processing PKI Responses</a>
1599 </h2>
1600 <p id="section-7-1">Clients conforming to this document <span class="bcp14">MUST</span> ensure that only the permitted signature, hash, and MAC algorithms described throughout this profile are used in responses; if they are not, the client <span class="bcp14">MUST</span> reject those responses.<a href="#section-7-1" class="pilcrow">¶</a></p>
1601 <p id="section-7-2">Clients <span class="bcp14">MUST</span> authenticate all Full PKI Responses. This includes verifying that the PKI Response is signed by an authorized CA or RA whose certificate validates back to a trust anchor. The authorized CA certificate <span class="bcp14">MUST</span> include the id-kp-cmcCA EKU and/or a CCC extension that includes the object identifier for the PKIResponse content type. Otherwise, the CA is determined to be authorized to sign responses through an implementation-specific mechanism. The PKI Response can be signed by an RA if it is an error message, if it is a response to a Get Certificate or Get CRL request, or if the PKI Response contains an inner PKI Response signed by a CA. In the last case, each layer of PKI Response <span class="bcp14">MUST</span> still contain an authorized, valid signature signed by an entity with a valid certificate that verifies back to an acceptable trust anchor. The authorized RA certificate <span class="bcp14">MUST</span> include the id-kp-cmcRA EKU and/or include a CCC extension that includes the object identifier for the PKIResponse content type. Otherwise, the RA is determined to be authorized to sign responses through local configuration.<a href="#section-7-2" class="pilcrow">¶</a></p>
1602 <p id="section-7-3">When a newly issued certificate is included in the PKI Response, the client <span class="bcp14">MUST</span> verify that the newly issued certificate's public key matches the public key that the client requested. The client <span class="bcp14">MUST</span> also ensure that the certificate's signature is valid and that the signature validates back to an acceptable trust anchor.<a href="#section-7-3" class="pilcrow">¶</a></p>
1603 <p id="section-7-4">Clients <span class="bcp14">MUST</span> reject PKI Responses that do not pass
1604 these tests. Local policy will determine whether the client returns a
1605 Full PKI Response with an Extended CMC Status Info control
1606 (CMCStatusInfoV2) with the CMCStatus set to failed to a user console, error log, or the server.<a href="#section-7-4" class="pilcrow">¶</a></p>
1607 <p id="section-7-5">If the Full PKI Response contains an Extended CMC Status Info control with a CMCStatus set to failed, then local policy will determine whether the client resends a duplicate certification request back to the server or an error state is returned to a console or error log.<a href="#section-7-5" class="pilcrow">¶</a></p>
1608 </section>
1609 </div>
1610 <div id="shared-secrets">
1611 <section id="section-8">
1612 <h2 id="name-shared-secrets">
1613 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-shared-secrets" class="section-name selfRef">Shared-Secrets</a>
1614 </h2>
1615 <p id="section-8-1">When the Identity Proof V2 and POP Link Witness V2 controls are used, the shared-secret <span class="bcp14">MUST</span> be randomly generated and securely distributed. The shared-secret <span class="bcp14">MUST</span> provide at least 192 bits of strength.<a href="#section-8-1" class="pilcrow">¶</a></p>
1616 </section>
1617 </div>
1618 <div id="sec-considerations">
1619 <section id="section-9">
1620 <h2 id="name-security-considerations">
1621 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1622 </h2>
1623 <p id="section-9-1">Protocol security considerations are found in <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span>, <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span>, <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>, <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>, <span>[<a href="#RFC5273" class="xref">RFC5273</a>]</span>, <span>[<a href="#RFC5274" class="xref">RFC5274</a>]</span>, <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>, and <span>[<a href="#RFC6402" class="xref">RFC6402</a>]</span>. When CCC is used to authorize RA and CA certificates, then the security considerations in <span>[<a href="#RFC6010" class="xref">RFC6010</a>]</span> also apply. Algorithm security considerations are found in <span>[<a href="#RFC8755" class="xref">RFC8755</a>]</span>.<a href="#section-9-1" class="pilcrow">¶</a></p>
1624 <p id="section-9-2">Compliant with NIST Special Publication 800-57 <span>[<a href="#SP80057" class="xref">SP80057</a>]</span>, this profile defines proof-of-possession of a key establishment private key by performing a digital signature. Except for one-time proof-of-possession, a single key pair <span class="bcp14">MUST NOT</span> be used for both signature and key establishment.<a href="#section-9-2" class="pilcrow">¶</a></p>
1625 <p id="section-9-3">This specification requires implementations to generate key pairs and other random values. The use of inadequate pseudorandom number generators (PRNGs) can result in little or no security. The generation of quality random numbers is difficult. NIST Special Publication 800-90A <span>[<a href="#SP80090A" class="xref">SP80090A</a>]</span>, FIPS 186-3 <span>[<a href="#FIPS186" class="xref">FIPS186</a>]</span>, and <span>[<a href="#RFC4086" class="xref">RFC4086</a>]</span> offer random number generation guidance.<a href="#section-9-3" class="pilcrow">¶</a></p>
1626 <p id="section-9-4">When RAs are used, the list of authorized RAs <span class="bcp14">MUST</span> be
1627 securely distributed out of band to CAs.<a href="#section-9-4" class="pilcrow">¶</a></p>
1628 <p id="section-9-5">Presence of the POP Link Witness Version 2 and POP Link Random attributes protects against substitution attacks.<a href="#section-9-5" class="pilcrow">¶</a></p>
1629 <p id="section-9-6">The certificate policy for a particular environment will specify whether expired certificates can be used to sign certification requests.<a href="#section-9-6" class="pilcrow">¶</a></p>
1630 </section>
1631 </div>
1632 <div id="iana-considerations">
1633 <section id="section-10">
1634 <h2 id="name-iana-considerations">
1635 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1636 </h2>
1637 <p id="section-10-1">This document has no IANA actions.<a href="#section-10-1" class="pilcrow">¶</a></p>
1638 </section>
1639 </div>
1640 <section id="section-11">
1641 <h2 id="name-references">
1642 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a>
1643 </h2>
1644 <section id="section-11.1">
1645 <h3 id="name-normative-references">
1646 <a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
1647 </h3>
1648 <dl class="references">
1649 <dt id="CNSA">[CNSA]</dt>
1650 <dd>
1651 <span class="refAuthor">Committee on National Security Systems</span>, <span class="refTitle">"Use of Public Standards for Secure Information Sharing"</span>, <span class="seriesInfo">CNSS Policy 15</span>, <time datetime="2016-10">October 2016</time>, <span>&lt;<a href="https://www.cnss.gov/CNSS/issuances/Policies.cfm">https://www.cnss.gov/CNSS/issuances/Policies.cfm</a>&gt;</span>. </dd>
1652 <dt id="FIPS186">[FIPS186]</dt>
1653 <dd>
1654 <span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Digital Signature Standard (DSS)"</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.186-4</span>, <span class="seriesInfo">FIPS PUB 186-4</span>, <time datetime="2013-07">July 2013</time>, <span>&lt;<a href="http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf">http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf</a>&gt;</span>. </dd>
1655 <dt id="RFC2119">[RFC2119]</dt>
1656 <dd>
1657 <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">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
1658 <dt id="RFC2986">[RFC2986]</dt>
1659 <dd>
1660 <span class="refAuthor">Nystrom, M.</span><span class="refAuthor"> and B. Kaliski</span>, <span class="refTitle">"PKCS #10: Certification Request Syntax Specification Version 1.7"</span>, <span class="seriesInfo">RFC 2986</span>, <span class="seriesInfo">DOI 10.17487/RFC2986</span>, <time datetime="2000-11">November 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2986">https://www.rfc-editor.org/info/rfc2986</a>&gt;</span>. </dd>
1661 <dt id="RFC4055">[RFC4055]</dt>
1662 <dd>
1663 <span class="refAuthor">Schaad, J.</span><span class="refAuthor">, Kaliski, B.</span><span class="refAuthor">, and R. Housley</span>, <span class="refTitle">"Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"</span>, <span class="seriesInfo">RFC 4055</span>, <span class="seriesInfo">DOI 10.17487/RFC4055</span>, <time datetime="2005-06">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4055">https://www.rfc-editor.org/info/rfc4055</a>&gt;</span>. </dd>
1664 <dt id="RFC4056">[RFC4056]</dt>
1665 <dd>
1666 <span class="refAuthor">Schaad, J.</span>, <span class="refTitle">"Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)"</span>, <span class="seriesInfo">RFC 4056</span>, <span class="seriesInfo">DOI 10.17487/RFC4056</span>, <time datetime="2005-06">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4056">https://www.rfc-editor.org/info/rfc4056</a>&gt;</span>. </dd>
1667 <dt id="RFC4086">[RFC4086]</dt>
1668 <dd>
1669 <span class="refAuthor">Eastlake 3rd, D.</span><span class="refAuthor">, Schiller, J.</span><span class="refAuthor">, and S. Crocker</span>, <span class="refTitle">"Randomness Requirements for Security"</span>, <span class="seriesInfo">BCP 106</span>, <span class="seriesInfo">RFC 4086</span>, <span class="seriesInfo">DOI 10.17487/RFC4086</span>, <time datetime="2005-06">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4086">https://www.rfc-editor.org/info/rfc4086</a>&gt;</span>. </dd>
1670 <dt id="RFC4211">[RFC4211]</dt>
1671 <dd>
1672 <span class="refAuthor">Schaad, J.</span>, <span class="refTitle">"Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"</span>, <span class="seriesInfo">RFC 4211</span>, <span class="seriesInfo">DOI 10.17487/RFC4211</span>, <time datetime="2005-09">September 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4211">https://www.rfc-editor.org/info/rfc4211</a>&gt;</span>. </dd>
1673 <dt id="RFC4231">[RFC4231]</dt>
1674 <dd>
1675 <span class="refAuthor">Nystrom, M.</span>, <span class="refTitle">"Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512"</span>, <span class="seriesInfo">RFC 4231</span>, <span class="seriesInfo">DOI 10.17487/RFC4231</span>, <time datetime="2005-12">December 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4231">https://www.rfc-editor.org/info/rfc4231</a>&gt;</span>. </dd>
1676 <dt id="RFC5272">[RFC5272]</dt>
1677 <dd>
1678 <span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and M. Myers</span>, <span class="refTitle">"Certificate Management over CMS (CMC)"</span>, <span class="seriesInfo">RFC 5272</span>, <span class="seriesInfo">DOI 10.17487/RFC5272</span>, <time datetime="2008-06">June 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5272">https://www.rfc-editor.org/info/rfc5272</a>&gt;</span>. </dd>
1679 <dt id="RFC5273">[RFC5273]</dt>
1680 <dd>
1681 <span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and M. Myers</span>, <span class="refTitle">"Certificate Management over CMS (CMC): Transport Protocols"</span>, <span class="seriesInfo">RFC 5273</span>, <span class="seriesInfo">DOI 10.17487/RFC5273</span>, <time datetime="2008-06">June 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5273">https://www.rfc-editor.org/info/rfc5273</a>&gt;</span>. </dd>
1682 <dt id="RFC5274">[RFC5274]</dt>
1683 <dd>
1684 <span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and M. Myers</span>, <span class="refTitle">"Certificate Management Messages over CMS (CMC): Compliance Requirements"</span>, <span class="seriesInfo">RFC 5274</span>, <span class="seriesInfo">DOI 10.17487/RFC5274</span>, <time datetime="2008-06">June 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5274">https://www.rfc-editor.org/info/rfc5274</a>&gt;</span>. </dd>
1685 <dt id="RFC5754">[RFC5754]</dt>
1686 <dd>
1687 <span class="refAuthor">Turner, S.</span>, <span class="refTitle">"Using SHA2 Algorithms with Cryptographic Message Syntax"</span>, <span class="seriesInfo">RFC 5754</span>, <span class="seriesInfo">DOI 10.17487/RFC5754</span>, <time datetime="2010-01">January 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5754">https://www.rfc-editor.org/info/rfc5754</a>&gt;</span>. </dd>
1688 <dt id="RFC6010">[RFC6010]</dt>
1689 <dd>
1690 <span class="refAuthor">Housley, R.</span><span class="refAuthor">, Ashmore, S.</span><span class="refAuthor">, and C. Wallace</span>, <span class="refTitle">"Cryptographic Message Syntax (CMS) Content Constraints Extension"</span>, <span class="seriesInfo">RFC 6010</span>, <span class="seriesInfo">DOI 10.17487/RFC6010</span>, <time datetime="2010-09">September 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6010">https://www.rfc-editor.org/info/rfc6010</a>&gt;</span>. </dd>
1691 <dt id="RFC6402">[RFC6402]</dt>
1692 <dd>
1693 <span class="refAuthor">Schaad, J.</span>, <span class="refTitle">"Certificate Management over CMS (CMC) Updates"</span>, <span class="seriesInfo">RFC 6402</span>, <span class="seriesInfo">DOI 10.17487/RFC6402</span>, <time datetime="2011-11">November 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6402">https://www.rfc-editor.org/info/rfc6402</a>&gt;</span>. </dd>
1694 <dt id="RFC8017">[RFC8017]</dt>
1695 <dd>
1696 <span class="refAuthor">Moriarty, K., Ed.</span><span class="refAuthor">, Kaliski, B.</span><span class="refAuthor">, Jonsson, J.</span><span class="refAuthor">, and A. Rusch</span>, <span class="refTitle">"PKCS #1: RSA Cryptography Specifications Version 2.2"</span>, <span class="seriesInfo">RFC 8017</span>, <span class="seriesInfo">DOI 10.17487/RFC8017</span>, <time datetime="2016-11">November 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8017">https://www.rfc-editor.org/info/rfc8017</a>&gt;</span>. </dd>
1697 <dt id="RFC8174">[RFC8174]</dt>
1698 <dd>
1699 <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">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
1700 <dt id="RFC8603">[RFC8603]</dt>
1701 <dd>
1702 <span class="refAuthor">Jenkins, M.</span><span class="refAuthor"> and L. Zieglar</span>, <span class="refTitle">"Commercial National Security Algorithm (CNSA) Suite Certificate and Certificate Revocation List (CRL) Profile"</span>, <span class="seriesInfo">RFC 8603</span>, <span class="seriesInfo">DOI 10.17487/RFC8603</span>, <time datetime="2019-05">May 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8603">https://www.rfc-editor.org/info/rfc8603</a>&gt;</span>. </dd>
1703 <dt id="RFC8755">[RFC8755]</dt>
1704 <dd>
1705 <span class="refAuthor">Jenkins, M.</span>, <span class="refTitle">"Using Commercial National Security Algorithm Suite Algorithms in Secure/Multipurpose Internet Mail Extensions"</span>, <span class="seriesInfo">RFC 8755</span>, <span class="seriesInfo">DOI 10.17487/RFC8755</span>, <time datetime="2020-03">March 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8755">https://www.rfc-editor.org/info/rfc8755</a>&gt;</span>. </dd>
1706 </dl>
1707 </section>
1708 <section id="section-11.2">
1709 <h3 id="name-informative-references">
1710 <a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
1711 </h3>
1712 <dl class="references">
1713 <dt id="SP80057">[SP80057]</dt>
1714 <dd>
1715 <span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Recommendation for Key Management, Part 1: General"</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-57pt1r4</span>, <span class="seriesInfo">Special Publication 800-57, Part 1, Revision 4</span>, <time datetime="2016-01">January 2016</time>, <span>&lt;<a href="http://doi.org/10.6028/NIST.SP.800-57pt1r4">http://doi.org/10.6028/NIST.SP.800-57pt1r4</a>&gt;</span>. </dd>
1716 <dt id="SP80059">[SP80059]</dt>
1717 <dd>
1718 <span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Guideline for Identifying an Information System as a National Security System"</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-59</span>, <span class="seriesInfo">Special Publication 800-59</span>, <time datetime="2003-08">August 2003</time>, <span>&lt;<a href="https://csrc.nist.gov/publications/detail/sp/800-59/final">https://csrc.nist.gov/publications/detail/sp/800-59/final</a>&gt;</span>. </dd>
1719 <dt id="SP80090A">[SP80090A]</dt>
1720 <dd>
1721 <span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Recommendation for Random Number Generation Using Deterministic Random Bit Generators"</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-90Ar1</span>, <span class="seriesInfo">Special Publication 800-90A Revision 1</span>, <time datetime="2015-06">June 2015</time>, <span>&lt;<a href="http://doi.org/10.6028/NIST.SP.800-90Ar1">http://doi.org/10.6028/NIST.SP.800-90Ar1</a>&gt;</span>. </dd>
1722 </dl>
1723 </section>
1724 </section>
1725 <div id="scenarios">
1726 <section id="section-appendix.a">
1727 <h2 id="name-scenarios">
1728 <a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-scenarios" class="section-name selfRef">Scenarios</a>
1729 </h2>
1730 <p id="section-appendix.a-1">This section illustrates several potential certificate enrollment and rekey scenarios supported by this profile. This section does not intend to place any limits or restrictions on the use of CMC.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
1731 <div id="init_enroll">
1732 <section id="section-a.1">
1733 <h2 id="name-initial-enrollment">
1734 <a href="#section-a.1" class="section-number selfRef">A.1. </a><a href="#name-initial-enrollment" class="section-name selfRef">Initial Enrollment</a>
1735 </h2>
1736 <p id="section-a.1-1">This section describes three scenarios for authenticating initial enrollment requests:<a href="#section-a.1-1" class="pilcrow">¶</a></p>
1737 <ol start="1" type="1" class="normal type-1" id="section-a.1-2">
1738 <li id="section-a.1-2.1">Previously certified signature key-pair (e.g., Manufacturer Installed Certificate).<a href="#section-a.1-2.1" class="pilcrow">¶</a>
1739 </li>
1740 <li id="section-a.1-2.2">Shared-secret distributed securely out of band.<a href="#section-a.1-2.2" class="pilcrow">¶</a>
1741 </li>
1742 <li id="section-a.1-2.3">RA authentication.<a href="#section-a.1-2.3" class="pilcrow">¶</a>
1743 </li>
1744 </ol>
1745 <div id="prev_inst">
1746 <section id="section-a.1.1">
1747 <h3 id="name-previously-certified-signat">
1748 <a href="#section-a.1.1" class="section-number selfRef">A.1.1. </a><a href="#name-previously-certified-signat" class="section-name selfRef">Previously Certified Signature Key-Pair</a>
1749 </h3>
1750 <p id="section-a.1.1-1">In this scenario, the end-entity has a private signing key and a corresponding public key certificate obtained from a cryptographic module manufacturer recognized by the CA. The end-entity signs a Full PKI Request with the private key that corresponds to the subject public key of the previously installed signature certificate. The CA will verify the authorization of the previously installed certificate and issue an appropriate new certificate to the end-entity.<a href="#section-a.1.1-1" class="pilcrow">¶</a></p>
1751 </section>
1752 </div>
1753 <div id="ss_oob">
1754 <section id="section-a.1.2">
1755 <h3 id="name-shared-secret-distributed-s">
1756 <a href="#section-a.1.2" class="section-number selfRef">A.1.2. </a><a href="#name-shared-secret-distributed-s" class="section-name selfRef">Shared-Secret Distributed Securely Out of Band</a>
1757 </h3>
1758 <p id="section-a.1.2-1">In this scenario, the CA distributes a shared-secret out of band
1759 to the end-entity that the end-entity uses to authenticate its
1760 certification request. The end-entity signs the Full PKI Request
1761 with the private key for which the certification is being
1762 requested. The end-entity includes the Identity Proof Version 2
1763 control to authenticate the request using the shared-secret. The CA
1764 uses either the Identification control or the subject name in the
1765 end-entity's enclosed PKCS #10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> or CRMF <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span>
1766 certification request message to identify the request. The
1767 end-entity performs either the POP Link Witness Version 2 mechanism
1768 as described in <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-6.3.1.1" class="relref">Section 6.3.1.1</a></span> or the shared-secret/subject distinguished
1769 name linking mechanism as described in <span>[<a href="#RFC5272" class="xref">RFC5272</a>], <a href="https://www.rfc-editor.org/rfc/rfc5272#section-6.3.2" class="relref">Section 6.3.2</a></span>. The subject name in the
1770 enclosed PKCS #10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> or CRMF <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span> certification
1771 request does not necessarily match the issued certificate, as it may
1772 be used just to help identify the request (and the corresponding shared-secret) to the CA.<a href="#section-a.1.2-1" class="pilcrow">¶</a></p>
1773 </section>
1774 </div>
1775 <div id="ra_auth">
1776 <section id="section-a.1.3">
1777 <h3 id="name-ra-authentication">
1778 <a href="#section-a.1.3" class="section-number selfRef">A.1.3. </a><a href="#name-ra-authentication" class="section-name selfRef">RA Authentication</a>
1779 </h3>
1780 <p id="section-a.1.3-1">In this scenario, the end-entity does not automatically
1781 authenticate its enrollment request to the CA, either because the
1782 end-entity has nothing to authenticate the request with or because
1783 the organizational policy requires an RA's involvement. The end-entity
1784 creates a Full PKI Request and sends it to an RA. The RA verifies
1785 the authenticity of the request. If the request is approved, the RA encapsulates and
1786 signs the request as described in <a href="#cert-reqst-msg" class="xref">Section 4.2</a>,
1787 forwarding the new request on to the CA. The subject name in the PKCS
1788 #10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> or CRMF <span>[<a href="#RFC4211" class="xref">RFC4211</a>]</span> certification request is not required to match the issued certificate; it may be used just to help identify the request to the RA and/or CA.<a href="#section-a.1.3-1" class="pilcrow">¶</a></p>
1789 </section>
1790 </div>
1791 </section>
1792 </div>
1793 <div id="rekey">
1794 <section id="section-a.2">
1795 <h2 id="name-rekey">
1796 <a href="#section-a.2" class="section-number selfRef">A.2. </a><a href="#name-rekey" class="section-name selfRef">Rekey</a>
1797 </h2>
1798 <p id="section-a.2-1">There are two scenarios to support the rekey of certificates that
1799 are already enrolled. One addresses the rekey of signature
1800 certificates, and the other addresses the rekey of key establishment
1801 certificates. Typically, organizational policy will require certificates to be currently valid to be rekeyed, and it may require initial enrollment to be repeated when rekey is not possible. However, some organizational policies might allow a grace period during which an expired certificate could be used to rekey.<a href="#section-a.2-1" class="pilcrow">¶</a></p>
1802 <div id="rk_sig">
1803 <section id="section-a.2.1">
1804 <h3 id="name-rekey-of-signature-certific">
1805 <a href="#section-a.2.1" class="section-number selfRef">A.2.1. </a><a href="#name-rekey-of-signature-certific" class="section-name selfRef">Rekey of Signature Certificates</a>
1806 </h3>
1807 <p id="section-a.2.1-1">When a signature certificate is rekeyed, the <span><a href="#RFC2986" class="xref">PKCS #10</a> [<a href="#RFC2986" class="xref">RFC2986</a>]</span> or <span><a href="#RFC4211" class="xref">CRMF</a> [<a href="#RFC4211" class="xref">RFC4211</a>]</span> certification request message enclosed in the Full PKI Request will include the same subject name as the current signature certificate. The Full PKI Request will be signed by the current private key corresponding to the current signature certificate.<a href="#section-a.2.1-1" class="pilcrow">¶</a></p>
1808 </section>
1809 </div>
1810 <div id="rk_kes">
1811 <section id="section-a.2.2">
1812 <h3 id="name-rekey-of-key-establishment-">
1813 <a href="#section-a.2.2" class="section-number selfRef">A.2.2. </a><a href="#name-rekey-of-key-establishment-" class="section-name selfRef">Rekey of Key Establishment Certificates</a>
1814 </h3>
1815 <p id="section-a.2.2-1">When a key establishment certificate is rekeyed, the Full PKI Request will generally be signed by the current private key corresponding to the current signature certificate. If there is no current signature certificate, one of the initial enrollment options in <a href="#init_enroll" class="xref">Appendix A.1</a> may be used.<a href="#section-a.2.2-1" class="pilcrow">¶</a></p>
1816 </section>
1817 </div>
1818 </section>
1819 </div>
1820 </section>
1821 </div>
1822 <div id="authors-addresses">
1823 <section id="section-appendix.b">
1824 <h2 id="name-authors-addresses">
1825 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
1826 </h2>
1827 <address class="vcard">
1828 <div dir="auto" class="left"><span class="fn nameRole">Michael Jenkins</span></div>
1829 <div dir="auto" class="left"><span class="org">National Security Agency</span></div>
1830 <div class="email">
1831 <span>Email:</span>
1832 <a href="mailto:[email protected]" class="email">[email protected]</a>
1833 </div>
1834 </address>
1835 <address class="vcard">
1836 <div dir="auto" class="left"><span class="fn nameRole">Lydia Zieglar</span></div>
1837 <div dir="auto" class="left"><span class="org">National Security Agency</span></div>
1838 <div class="email">
1839 <span>Email:</span>
1840 <a href="mailto:[email protected]" class="email">[email protected]</a>
1841 </div>
1842 </address>
1843 </section>
1844 </div>
1845 <script>const toc = document.getElementById("toc");
1846 toc.querySelector("h2").addEventListener("click", e => {
1847 toc.classList.toggle("active");
1848 });
1849 toc.querySelector("nav").addEventListener("click", e => {
1850 toc.classList.remove("active");
1851 });
1852 </script>
1853 </body>
1854 </html>