Debian Codegraph @

rfc8823.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 8823: Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates</title>
8 <meta content="Alexey Melnikov" name="author">
9 <meta content="
10
11 This document specifies identifiers and challenges required to enable
12 the Automated Certificate Management Environment (ACME) to issue
13 certificates for use by email users
14 that want to use S/⁠MIME.
15
16 " name="description">
17 <meta content="xml2rfc 3.7.0" name="generator">
18 <meta content="ACME" name="keyword">
19 <meta content="S/MIME" name="keyword">
20 <meta content="8823" name="rfc.number">
21 <!-- Generator version information:
22 xml2rfc 3.7.0
23 Python 3.6.10
24 appdirs 1.4.4
25 ConfigArgParse 1.2.3
26 google-i18n-address 2.3.5
27 html5lib 1.0.1
28 intervaltree 3.0.2
29 Jinja2 2.11.2
30 kitchen 1.2.6
31 lxml 4.4.2
32 pycairo 1.19.0
33 pycountry 19.8.18
34 pyflakes 2.1.1
35 PyYAML 5.3.1
36 requests 2.22.0
37 setuptools 40.6.2
38 six 1.14.0
39 WeasyPrint 51
40 -->
41 <link href="rfc8823.xml" rel="alternate" type="application/rfc+xml">
42 <link href="#copyright" rel="license">
43 <style type="text/css">/*
44
45 NOTE: Changes at the bottom of this file overrides some earlier settings.
46
47 Once the style has stabilized and has been adopted as an official RFC style,
48 this can be consolidated so that style settings occur only in one place, but
49 for now the contents of this file consists first of the initial CSS work as
50 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
51 commented changes found necssary during the development of the v3
52 formatters.
53
54 */
55
56 /* fonts */
57 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
58 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
59 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
60
61 @viewport {
62 zoom: 1.0;
63 width: extend-to-zoom;
64 }
65 @-ms-viewport {
66 width: extend-to-zoom;
67 zoom: 1.0;
68 }
69 /* general and mobile first */
70 html {
71 }
72 body {
73 max-width: 90%;
74 margin: 1.5em auto;
75 color: #222;
76 background-color: #fff;
77 font-size: 14px;
78 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
79 line-height: 1.6;
80 scroll-behavior: smooth;
81 }
82 .ears {
83 display: none;
84 }
85
86 /* headings */
87 #title, h1, h2, h3, h4, h5, h6 {
88 margin: 1em 0 0.5em;
89 font-weight: bold;
90 line-height: 1.3;
91 }
92 #title {
93 clear: both;
94 border-bottom: 1px solid #ddd;
95 margin: 0 0 0.5em 0;
96 padding: 1em 0 0.5em;
97 }
98 .author {
99 padding-bottom: 4px;
100 }
101 h1 {
102 font-size: 26px;
103 margin: 1em 0;
104 }
105 h2 {
106 font-size: 22px;
107 margin-top: -20px; /* provide offset for in-page anchors */
108 padding-top: 33px;
109 }
110 h3 {
111 font-size: 18px;
112 margin-top: -36px; /* provide offset for in-page anchors */
113 padding-top: 42px;
114 }
115 h4 {
116 font-size: 16px;
117 margin-top: -36px; /* provide offset for in-page anchors */
118 padding-top: 42px;
119 }
120 h5, h6 {
121 font-size: 14px;
122 }
123 #n-copyright-notice {
124 border-bottom: 1px solid #ddd;
125 padding-bottom: 1em;
126 margin-bottom: 1em;
127 }
128 /* general structure */
129 p {
130 padding: 0;
131 margin: 0 0 1em 0;
132 text-align: left;
133 }
134 div, span {
135 position: relative;
136 }
137 div {
138 margin: 0;
139 }
140 .alignRight.art-text {
141 background-color: #f9f9f9;
142 border: 1px solid #eee;
143 border-radius: 3px;
144 padding: 1em 1em 0;
145 margin-bottom: 1.5em;
146 }
147 .alignRight.art-text pre {
148 padding: 0;
149 }
150 .alignRight {
151 margin: 1em 0;
152 }
153 .alignRight > *:first-child {
154 border: none;
155 margin: 0;
156 float: right;
157 clear: both;
158 }
159 .alignRight > *:nth-child(2) {
160 clear: both;
161 display: block;
162 border: none;
163 }
164 svg {
165 display: block;
166 }
167 .alignCenter.art-text {
168 background-color: #f9f9f9;
169 border: 1px solid #eee;
170 border-radius: 3px;
171 padding: 1em 1em 0;
172 margin-bottom: 1.5em;
173 }
174 .alignCenter.art-text pre {
175 padding: 0;
176 }
177 .alignCenter {
178 margin: 1em 0;
179 }
180 .alignCenter > *:first-child {
181 border: none;
182 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
183 support flexbox yet.
184 */
185 display: table;
186 margin: 0 auto;
187 }
188
189 /* lists */
190 ol, ul {
191 padding: 0;
192 margin: 0 0 1em 2em;
193 }
194 ol ol, ul ul, ol ul, ul ol {
195 margin-left: 1em;
196 }
197 li {
198 margin: 0 0 0.25em 0;
199 }
200 .ulCompact li {
201 margin: 0;
202 }
203 ul.empty, .ulEmpty {
204 list-style-type: none;
205 }
206 ul.empty li, .ulEmpty li {
207 margin-top: 0.5em;
208 }
209 ul.compact, .ulCompact,
210 ol.compact, .olCompact {
211 line-height: 100%;
212 margin: 0 0 0 2em;
213 }
214
215 /* definition lists */
216 dl {
217 }
218 dl > dt {
219 float: left;
220 margin-right: 1em;
221 }
222 /*
223 dl.nohang > dt {
224 float: none;
225 }
226 */
227 dl > dd {
228 margin-bottom: .8em;
229 min-height: 1.3em;
230 }
231 dl.compact > dd, .dlCompact > dd {
232 margin-bottom: 0em;
233 }
234 dl > dd > dl {
235 margin-top: 0.5em;
236 margin-bottom: 0em;
237 }
238
239 /* links */
240 a {
241 text-decoration: none;
242 }
243 a[href] {
244 color: #22e; /* Arlen: WCAG 2019 */
245 }
246 a[href]:hover {
247 background-color: #f2f2f2;
248 }
249 figcaption a[href],
250 a[href].selfRef {
251 color: #222;
252 }
253 /* XXX probably not this:
254 a.selfRef:hover {
255 background-color: transparent;
256 cursor: default;
257 } */
258
259 /* Figures */
260 tt, code, pre, code {
261 background-color: #f9f9f9;
262 font-family: 'Roboto Mono', monospace;
263 }
264 pre {
265 border: 1px solid #eee;
266 margin: 0;
267 padding: 1em;
268 }
269 img {
270 max-width: 100%;
271 }
272 figure {
273 margin: 0;
274 }
275 figure blockquote {
276 margin: 0.8em 0.4em 0.4em;
277 }
278 figcaption {
279 font-style: italic;
280 margin: 0 0 1em 0;
281 }
282 @media screen {
283 pre {
284 overflow-x: auto;
285 max-width: 100%;
286 max-width: calc(100% - 22px);
287 }
288 }
289
290 /* aside, blockquote */
291 aside, blockquote {
292 margin-left: 0;
293 padding: 1.2em 2em;
294 }
295 blockquote {
296 background-color: #f9f9f9;
297 color: #111; /* Arlen: WCAG 2019 */
298 border: 1px solid #ddd;
299 border-radius: 3px;
300 margin: 1em 0;
301 }
302 cite {
303 display: block;
304 text-align: right;
305 font-style: italic;
306 }
307
308 /* tables */
309 table {
310 width: 100%;
311 margin: 0 0 1em;
312 border-collapse: collapse;
313 border: 1px solid #eee;
314 }
315 th, td {
316 text-align: left;
317 vertical-align: top;
318 padding: 0.5em 0.75em;
319 }
320 th {
321 text-align: left;
322 background-color: #e9e9e9;
323 }
324 tr:nth-child(2n+1) > td {
325 background-color: #f5f5f5;
326 }
327 table caption {
328 font-style: italic;
329 margin: 0;
330 padding: 0;
331 text-align: left;
332 }
333 table p {
334 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
335 be allowed within tables more generally, it would be far better to select on a class. */
336 margin: 0;
337 }
338
339 /* pilcrow */
340 a.pilcrow {
341 color: #666; /* Arlen: AHDJ 2019 */
342 text-decoration: none;
343 visibility: hidden;
344 user-select: none;
345 -ms-user-select: none;
346 -o-user-select:none;
347 -moz-user-select: none;
348 -khtml-user-select: none;
349 -webkit-user-select: none;
350 -webkit-touch-callout: none;
351 }
352 @media screen {
353 aside:hover > a.pilcrow,
354 p:hover > a.pilcrow,
355 blockquote:hover > a.pilcrow,
356 div:hover > a.pilcrow,
357 li:hover > a.pilcrow,
358 pre:hover > a.pilcrow {
359 visibility: visible;
360 }
361 a.pilcrow:hover {
362 background-color: transparent;
363 }
364 }
365
366 /* misc */
367 hr {
368 border: 0;
369 border-top: 1px solid #eee;
370 }
371 .bcp14 {
372 font-variant: small-caps;
373 }
374
375 .role {
376 font-variant: all-small-caps;
377 }
378
379 /* info block */
380 #identifiers {
381 margin: 0;
382 font-size: 0.9em;
383 }
384 #identifiers dt {
385 width: 3em;
386 clear: left;
387 }
388 #identifiers dd {
389 float: left;
390 margin-bottom: 0;
391 }
392 #identifiers .authors .author {
393 display: inline-block;
394 margin-right: 1.5em;
395 }
396 #identifiers .authors .org {
397 font-style: italic;
398 }
399
400 /* The prepared/rendered info at the very bottom of the page */
401 .docInfo {
402 color: #666; /* Arlen: WCAG 2019 */
403 font-size: 0.9em;
404 font-style: italic;
405 margin-top: 2em;
406 }
407 .docInfo .prepared {
408 float: left;
409 }
410 .docInfo .prepared {
411 float: right;
412 }
413
414 /* table of contents */
415 #toc {
416 padding: 0.75em 0 2em 0;
417 margin-bottom: 1em;
418 }
419 nav.toc ul {
420 margin: 0 0.5em 0 0;
421 padding: 0;
422 list-style: none;
423 }
424 nav.toc li {
425 line-height: 1.3em;
426 margin: 0.75em 0;
427 padding-left: 1.2em;
428 text-indent: -1.2em;
429 }
430 /* references */
431 .references dt {
432 text-align: right;
433 font-weight: bold;
434 min-width: 7em;
435 }
436 .references dd {
437 margin-left: 8em;
438 overflow: auto;
439 }
440
441 .refInstance {
442 margin-bottom: 1.25em;
443 }
444
445 .references .ascii {
446 margin-bottom: 0.25em;
447 }
448
449 /* index */
450 .index ul {
451 margin: 0 0 0 1em;
452 padding: 0;
453 list-style: none;
454 }
455 .index ul ul {
456 margin: 0;
457 }
458 .index li {
459 margin: 0;
460 text-indent: -2em;
461 padding-left: 2em;
462 padding-bottom: 5px;
463 }
464 .indexIndex {
465 margin: 0.5em 0 1em;
466 }
467 .index a {
468 font-weight: 700;
469 }
470 /* make the index two-column on all but the smallest screens */
471 @media (min-width: 600px) {
472 .index ul {
473 -moz-column-count: 2;
474 -moz-column-gap: 20px;
475 }
476 .index ul ul {
477 -moz-column-count: 1;
478 -moz-column-gap: 0;
479 }
480 }
481
482 /* authors */
483 address.vcard {
484 font-style: normal;
485 margin: 1em 0;
486 }
487
488 address.vcard .nameRole {
489 font-weight: 700;
490 margin-left: 0;
491 }
492 address.vcard .label {
493 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
494 margin: 0.5em 0;
495 }
496 address.vcard .type {
497 display: none;
498 }
499 .alternative-contact {
500 margin: 1.5em 0 1em;
501 }
502 hr.addr {
503 border-top: 1px dashed;
504 margin: 0;
505 color: #ddd;
506 max-width: calc(100% - 16px);
507 }
508
509 /* temporary notes */
510 .rfcEditorRemove::before {
511 position: absolute;
512 top: 0.2em;
513 right: 0.2em;
514 padding: 0.2em;
515 content: "The RFC Editor will remove this note";
516 color: #9e2a00; /* Arlen: WCAG 2019 */
517 background-color: #ffd; /* Arlen: WCAG 2019 */
518 }
519 .rfcEditorRemove {
520 position: relative;
521 padding-top: 1.8em;
522 background-color: #ffd; /* Arlen: WCAG 2019 */
523 border-radius: 3px;
524 }
525 .cref {
526 background-color: #ffd; /* Arlen: WCAG 2019 */
527 padding: 2px 4px;
528 }
529 .crefSource {
530 font-style: italic;
531 }
532 /* alternative layout for smaller screens */
533 @media screen and (max-width: 1023px) {
534 body {
535 padding-top: 2em;
536 }
537 #title {
538 padding: 1em 0;
539 }
540 h1 {
541 font-size: 24px;
542 }
543 h2 {
544 font-size: 20px;
545 margin-top: -18px; /* provide offset for in-page anchors */
546 padding-top: 38px;
547 }
548 #identifiers dd {
549 max-width: 60%;
550 }
551 #toc {
552 position: fixed;
553 z-index: 2;
554 top: 0;
555 right: 0;
556 padding: 0;
557 margin: 0;
558 background-color: inherit;
559 border-bottom: 1px solid #ccc;
560 }
561 #toc h2 {
562 margin: -1px 0 0 0;
563 padding: 4px 0 4px 6px;
564 padding-right: 1em;
565 min-width: 190px;
566 font-size: 1.1em;
567 text-align: right;
568 background-color: #444;
569 color: white;
570 cursor: pointer;
571 }
572 #toc h2::before { /* css hamburger */
573 float: right;
574 position: relative;
575 width: 1em;
576 height: 1px;
577 left: -164px;
578 margin: 6px 0 0 0;
579 background: white none repeat scroll 0 0;
580 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
581 content: "";
582 }
583 #toc nav {
584 display: none;
585 padding: 0.5em 1em 1em;
586 overflow: auto;
587 height: calc(100vh - 48px);
588 border-left: 1px solid #ddd;
589 }
590 }
591
592 /* alternative layout for wide screens */
593 @media screen and (min-width: 1024px) {
594 body {
595 max-width: 724px;
596 margin: 42px auto;
597 padding-left: 1.5em;
598 padding-right: 29em;
599 }
600 #toc {
601 position: fixed;
602 top: 42px;
603 right: 42px;
604 width: 25%;
605 margin: 0;
606 padding: 0 1em;
607 z-index: 1;
608 }
609 #toc h2 {
610 border-top: none;
611 border-bottom: 1px solid #ddd;
612 font-size: 1em;
613 font-weight: normal;
614 margin: 0;
615 padding: 0.25em 1em 1em 0;
616 }
617 #toc nav {
618 display: block;
619 height: calc(90vh - 84px);
620 bottom: 0;
621 padding: 0.5em 0 0;
622 overflow: auto;
623 }
624 img { /* future proofing */
625 max-width: 100%;
626 height: auto;
627 }
628 }
629
630 /* pagination */
631 @media print {
632 body {
633
634 width: 100%;
635 }
636 p {
637 orphans: 3;
638 widows: 3;
639 }
640 #n-copyright-notice {
641 border-bottom: none;
642 }
643 #toc, #n-introduction {
644 page-break-before: always;
645 }
646 #toc {
647 border-top: none;
648 padding-top: 0;
649 }
650 figure, pre {
651 page-break-inside: avoid;
652 }
653 figure {
654 overflow: scroll;
655 }
656 h1, h2, h3, h4, h5, h6 {
657 page-break-after: avoid;
658 }
659 h2+*, h3+*, h4+*, h5+*, h6+* {
660 page-break-before: avoid;
661 }
662 pre {
663 white-space: pre-wrap;
664 word-wrap: break-word;
665 font-size: 10pt;
666 }
667 table {
668 border: 1px solid #ddd;
669 }
670 td {
671 border-top: 1px solid #ddd;
672 }
673 }
674
675 /* This is commented out here, as the string-set: doesn't
676 pass W3C validation currently */
677 /*
678 .ears thead .left {
679 string-set: ears-top-left content();
680 }
681
682 .ears thead .center {
683 string-set: ears-top-center content();
684 }
685
686 .ears thead .right {
687 string-set: ears-top-right content();
688 }
689
690 .ears tfoot .left {
691 string-set: ears-bottom-left content();
692 }
693
694 .ears tfoot .center {
695 string-set: ears-bottom-center content();
696 }
697
698 .ears tfoot .right {
699 string-set: ears-bottom-right content();
700 }
701 */
702
703 @page :first {
704 padding-top: 0;
705 @top-left {
706 content: normal;
707 border: none;
708 }
709 @top-center {
710 content: normal;
711 border: none;
712 }
713 @top-right {
714 content: normal;
715 border: none;
716 }
717 }
718
719 @page {
720 size: A4;
721 margin-bottom: 45mm;
722 padding-top: 20px;
723 /* The follwing is commented out here, but set appropriately by in code, as
724 the content depends on the document */
725 /*
726 @top-left {
727 content: 'Internet-Draft';
728 vertical-align: bottom;
729 border-bottom: solid 1px #ccc;
730 }
731 @top-left {
732 content: string(ears-top-left);
733 vertical-align: bottom;
734 border-bottom: solid 1px #ccc;
735 }
736 @top-center {
737 content: string(ears-top-center);
738 vertical-align: bottom;
739 border-bottom: solid 1px #ccc;
740 }
741 @top-right {
742 content: string(ears-top-right);
743 vertical-align: bottom;
744 border-bottom: solid 1px #ccc;
745 }
746 @bottom-left {
747 content: string(ears-bottom-left);
748 vertical-align: top;
749 border-top: solid 1px #ccc;
750 }
751 @bottom-center {
752 content: string(ears-bottom-center);
753 vertical-align: top;
754 border-top: solid 1px #ccc;
755 }
756 @bottom-right {
757 content: '[Page ' counter(page) ']';
758 vertical-align: top;
759 border-top: solid 1px #ccc;
760 }
761 */
762
763 }
764
765 /* Changes introduced to fix issues found during implementation */
766 /* Make sure links are clickable even if overlapped by following H* */
767 a {
768 z-index: 2;
769 }
770 /* Separate body from document info even without intervening H1 */
771 section {
772 clear: both;
773 }
774
775
776 /* Top align author divs, to avoid names without organization dropping level with org names */
777 .author {
778 vertical-align: top;
779 }
780
781 /* Leave room in document info to show Internet-Draft on one line */
782 #identifiers dt {
783 width: 8em;
784 }
785
786 /* Don't waste quite as much whitespace between label and value in doc info */
787 #identifiers dd {
788 margin-left: 1em;
789 }
790
791 /* Give floating toc a background color (needed when it's a div inside section */
792 #toc {
793 background-color: white;
794 }
795
796 /* Make the collapsed ToC header render white on gray also when it's a link */
797 @media screen and (max-width: 1023px) {
798 #toc h2 a,
799 #toc h2 a:link,
800 #toc h2 a:focus,
801 #toc h2 a:hover,
802 #toc a.toplink,
803 #toc a.toplink:hover {
804 color: white;
805 background-color: #444;
806 text-decoration: none;
807 }
808 }
809
810 /* Give the bottom of the ToC some whitespace */
811 @media screen and (min-width: 1024px) {
812 #toc {
813 padding: 0 0 1em 1em;
814 }
815 }
816
817 /* Style section numbers with more space between number and title */
818 .section-number {
819 padding-right: 0.5em;
820 }
821
822 /* prevent monospace from becoming overly large */
823 tt, code, pre, code {
824 font-size: 95%;
825 }
826
827 /* Fix the height/width aspect for ascii art*/
828 pre.sourcecode,
829 .art-text pre {
830 line-height: 1.12;
831 }
832
833
834 /* Add styling for a link in the ToC that points to the top of the document */
835 a.toplink {
836 float: right;
837 margin-right: 0.5em;
838 }
839
840 /* Fix the dl styling to match the RFC 7992 attributes */
841 dl > dt,
842 dl.dlParallel > dt {
843 float: left;
844 margin-right: 1em;
845 }
846 dl.dlNewline > dt {
847 float: none;
848 }
849
850 /* Provide styling for table cell text alignment */
851 table td.text-left,
852 table th.text-left {
853 text-align: left;
854 }
855 table td.text-center,
856 table th.text-center {
857 text-align: center;
858 }
859 table td.text-right,
860 table th.text-right {
861 text-align: right;
862 }
863
864 /* Make the alternative author contact informatio look less like just another
865 author, and group it closer with the primary author contact information */
866 .alternative-contact {
867 margin: 0.5em 0 0.25em 0;
868 }
869 address .non-ascii {
870 margin: 0 0 0 2em;
871 }
872
873 /* With it being possible to set tables with alignment
874 left, center, and right, { width: 100%; } does not make sense */
875 table {
876 width: auto;
877 }
878
879 /* Avoid reference text that sits in a block with very wide left margin,
880 because of a long floating dt label.*/
881 .references dd {
882 overflow: visible;
883 }
884
885 /* Control caption placement */
886 caption {
887 caption-side: bottom;
888 }
889
890 /* Limit the width of the author address vcard, so names in right-to-left
891 script don't end up on the other side of the page. */
892
893 address.vcard {
894 max-width: 30em;
895 margin-right: auto;
896 }
897
898 /* For address alignment dependent on LTR or RTL scripts */
899 address div.left {
900 text-align: left;
901 }
902 address div.right {
903 text-align: right;
904 }
905
906 /* Provide table alignment support. We can't use the alignX classes above
907 since they do unwanted things with caption and other styling. */
908 table.right {
909 margin-left: auto;
910 margin-right: 0;
911 }
912 table.center {
913 margin-left: auto;
914 margin-right: auto;
915 }
916 table.left {
917 margin-left: 0;
918 margin-right: auto;
919 }
920
921 /* Give the table caption label the same styling as the figcaption */
922 caption a[href] {
923 color: #222;
924 }
925
926 @media print {
927 .toplink {
928 display: none;
929 }
930
931 /* avoid overwriting the top border line with the ToC header */
932 #toc {
933 padding-top: 1px;
934 }
935
936 /* Avoid page breaks inside dl and author address entries */
937 .vcard {
938 page-break-inside: avoid;
939 }
940
941 }
942 /* Tweak the bcp14 keyword presentation */
943 .bcp14 {
944 font-variant: small-caps;
945 font-weight: bold;
946 font-size: 0.9em;
947 }
948 /* Tweak the invisible space above H* in order not to overlay links in text above */
949 h2 {
950 margin-top: -18px; /* provide offset for in-page anchors */
951 padding-top: 31px;
952 }
953 h3 {
954 margin-top: -18px; /* provide offset for in-page anchors */
955 padding-top: 24px;
956 }
957 h4 {
958 margin-top: -18px; /* provide offset for in-page anchors */
959 padding-top: 24px;
960 }
961 /* Float artwork pilcrow to the right */
962 @media screen {
963 .artwork a.pilcrow {
964 display: block;
965 line-height: 0.7;
966 margin-top: 0.15em;
967 }
968 }
969 /* Make pilcrows on dd visible */
970 @media screen {
971 dd:hover > a.pilcrow {
972 visibility: visible;
973 }
974 }
975 /* Make the placement of figcaption match that of a table's caption
976 by removing the figure's added bottom margin */
977 .alignLeft.art-text,
978 .alignCenter.art-text,
979 .alignRight.art-text {
980 margin-bottom: 0;
981 }
982 .alignLeft,
983 .alignCenter,
984 .alignRight {
985 margin: 1em 0 0 0;
986 }
987 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
988 possibly even requiring a new line */
989 @media print {
990 a.pilcrow {
991 display: none;
992 }
993 }
994 /* Styling for the external metadata */
995 div#external-metadata {
996 background-color: #eee;
997 padding: 0.5em;
998 margin-bottom: 0.5em;
999 display: none;
1000 }
1001 div#internal-metadata {
1002 padding: 0.5em; /* to match the external-metadata padding */
1003 }
1004 /* Styling for title RFC Number */
1005 h1#rfcnum {
1006 clear: both;
1007 margin: 0 0 -1em;
1008 padding: 1em 0 0 0;
1009 }
1010 /* Make .olPercent look the same as <ol><li> */
1011 dl.olPercent > dd {
1012 margin-bottom: 0.25em;
1013 min-height: initial;
1014 }
1015 /* Give aside some styling to set it apart */
1016 aside {
1017 border-left: 1px solid #ddd;
1018 margin: 1em 0 1em 2em;
1019 padding: 0.2em 2em;
1020 }
1021 aside > dl,
1022 aside > ol,
1023 aside > ul,
1024 aside > table,
1025 aside > p {
1026 margin-bottom: 0.5em;
1027 }
1028 /* Additional page break settings */
1029 @media print {
1030 figcaption, table caption {
1031 page-break-before: avoid;
1032 }
1033 }
1034 /* Font size adjustments for print */
1035 @media print {
1036 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1037 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1038 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1039 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1040 h4 { font-size: 1em; padding-top: 1.5em; }
1041 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1042 }
1043 /* Sourcecode margin in print, when there's no pilcrow */
1044 @media print {
1045 .artwork,
1046 .sourcecode {
1047 margin-bottom: 1em;
1048 }
1049 }
1050 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1051 table {
1052 min-width: 20em;
1053 }
1054 /* ol type a */
1055 ol.type-a { list-style-type: lower-alpha; }
1056 ol.type-A { list-style-type: upper-alpha; }
1057 ol.type-i { list-style-type: lower-roman; }
1058 ol.type-I { list-style-type: lower-roman; }
1059 /* Apply the print table and row borders in general, on request from the RPC,
1060 and increase the contrast between border and odd row background sligthtly */
1061 table {
1062 border: 1px solid #ddd;
1063 }
1064 td {
1065 border-top: 1px solid #ddd;
1066 }
1067 tr:nth-child(2n+1) > td {
1068 background-color: #f8f8f8;
1069 }
1070 /* Use style rules to govern display of the TOC. */
1071 @media screen and (max-width: 1023px) {
1072 #toc nav { display: none; }
1073 #toc.active nav { display: block; }
1074 }
1075 /* Add support for keepWithNext */
1076 .keepWithNext {
1077 break-after: avoid-page;
1078 break-after: avoid-page;
1079 }
1080 /* Add support for keepWithPrevious */
1081 .keepWithPrevious {
1082 break-before: avoid-page;
1083 }
1084 /* Change the approach to avoiding breaks inside artwork etc. */
1085 figure, pre, table, .artwork, .sourcecode {
1086 break-before: avoid-page;
1087 break-after: auto;
1088 }
1089 /* Avoid breaks between <dt> and <dd> */
1090 dl {
1091 break-before: auto;
1092 break-inside: auto;
1093 }
1094 dt {
1095 break-before: auto;
1096 break-after: avoid-page;
1097 }
1098 dd {
1099 break-before: avoid-page;
1100 break-after: auto;
1101 orphans: 3;
1102 widows: 3
1103 }
1104 span.break, dd.break {
1105 margin-bottom: 0;
1106 min-height: 0;
1107 break-before: auto;
1108 break-inside: auto;
1109 break-after: auto;
1110 }
1111 /* Undo break-before ToC */
1112 @media print {
1113 #toc {
1114 break-before: auto;
1115 }
1116 }
1117 /* Text in compact lists should not get extra bottim margin space,
1118 since that would makes the list not compact */
1119 ul.compact p, .ulCompact p,
1120 ol.compact p, .olCompact p {
1121 margin: 0;
1122 }
1123 /* But the list as a whole needs the extra space at the end */
1124 section ul.compact,
1125 section .ulCompact,
1126 section ol.compact,
1127 section .olCompact {
1128 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1129 }
1130 /* The tt and code background above interferes with for instance table cell
1131 backgrounds. Changed to something a bit more selective. */
1132 tt, code {
1133 background-color: transparent;
1134 }
1135 p tt, p code, li tt, li code {
1136 background-color: #f8f8f8;
1137 }
1138 /* Tweak the pre margin -- 0px doesn't come out well */
1139 pre {
1140 margin-top: 0.5px;
1141 }
1142 /* Tweak the comact list text */
1143 ul.compact, .ulCompact,
1144 ol.compact, .olCompact,
1145 dl.compact, .dlCompact {
1146 line-height: normal;
1147 }
1148 /* Don't add top margin for nested lists */
1149 li > ul, li > ol, li > dl,
1150 dd > ul, dd > ol, dd > dl,
1151 dl > dd > dl {
1152 margin-top: initial;
1153 }
1154 /* Elements that should not be rendered on the same line as a <dt> */
1155 /* This should match the element list in writer.text.TextWriter.render_dl() */
1156 dd > div.artwork:first-child,
1157 dd > aside:first-child,
1158 dd > figure:first-child,
1159 dd > ol:first-child,
1160 dd > div:first-child > pre.sourcecode,
1161 dd > table:first-child,
1162 dd > ul:first-child {
1163 clear: left;
1164 }
1165 /* fix for weird browser behaviour when <dd/> is empty */
1166 dt+dd:empty::before{
1167 content: "\00a0";
1168 }
1169 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1170 li > p {
1171 margin-bottom: 0.5em
1172 }
1173 /* Don't let p margin spill out from inside list items */
1174 li > p:last-of-type {
1175 margin-bottom: 0;
1176 }
1177 </style>
1178 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1179 <link href="https://dx.doi.org/10.17487/rfc8823" rel="alternate">
1180 <link href="urn:issn:2070-1721" rel="alternate">
1181 <link href="https://datatracker.ietf.org/doc/draft-ietf-acme-email-smime-14" rel="prev">
1182 </head>
1183 <body>
1184 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1185 <table class="ears">
1186 <thead><tr>
1187 <td class="left">RFC 8823</td>
1188 <td class="center">ACME for S/MIME</td>
1189 <td class="right">April 2021</td>
1190 </tr></thead>
1191 <tfoot><tr>
1192 <td class="left">Melnikov</td>
1193 <td class="center">Informational</td>
1194 <td class="right">[Page]</td>
1195 </tr></tfoot>
1196 </table>
1197 <div id="external-metadata" class="document-information"></div>
1198 <div id="internal-metadata" class="document-information">
1199 <dl id="identifiers">
1200 <dt class="label-stream">Stream:</dt>
1201 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1202 <dt class="label-rfc">RFC:</dt>
1203 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8823" class="eref">8823</a></dd>
1204 <dt class="label-category">Category:</dt>
1205 <dd class="category">Informational</dd>
1206 <dt class="label-published">Published:</dt>
1207 <dd class="published">
1208 <time datetime="2021-04" class="published">April 2021</time>
1209 </dd>
1210 <dt class="label-issn">ISSN:</dt>
1211 <dd class="issn">2070-1721</dd>
1212 <dt class="label-authors">Author:</dt>
1213 <dd class="authors">
1214 <div class="author">
1215 <div class="author-name">A. Melnikov</div>
1216 <div class="org">Isode Ltd</div>
1217 </div>
1218 </dd>
1219 </dl>
1220 </div>
1221 <h1 id="rfcnum">RFC 8823</h1>
1222 <h1 id="title">Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates</h1>
1223 <section id="section-abstract">
1224 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1225 <p id="section-abstract-1">
1226 This document specifies identifiers and challenges required to enable
1227 the Automated Certificate Management Environment (ACME) to issue
1228 certificates for use by email users
1229 that want to use S/⁠MIME.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1230 </section>
1231 <div id="status-of-memo">
1232 <section id="section-boilerplate.1">
1233 <h2 id="name-status-of-this-memo">
1234 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1235 </h2>
1236 <p id="section-boilerplate.1-1">
1237 This document is not an Internet Standards Track specification; it is
1238 published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1239 <p id="section-boilerplate.1-2">
1240 This document is a product of the Internet Engineering Task Force
1241 (IETF). It represents the consensus of the IETF community. It has
1242 received public review and has been approved for publication by the
1243 Internet Engineering Steering Group (IESG). Not all documents
1244 approved by the IESG are candidates for any level of Internet
1245 Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1246 <p id="section-boilerplate.1-3">
1247 Information about the current status of this document, any
1248 errata, and how to provide feedback on it may be obtained at
1249 <span><a href="https://www.rfc-editor.org/info/rfc8823">https://www.rfc-editor.org/info/rfc8823</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1250 </section>
1251 </div>
1252 <div id="copyright">
1253 <section id="section-boilerplate.2">
1254 <h2 id="name-copyright-notice">
1255 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1256 </h2>
1257 <p id="section-boilerplate.2-1">
1258 Copyright (c) 2021 IETF Trust and the persons identified as the
1259 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1260 <p id="section-boilerplate.2-2">
1261 This document is subject to BCP 78 and the IETF Trust's Legal
1262 Provisions Relating to IETF Documents
1263 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1264 publication of this document. Please review these documents
1265 carefully, as they describe your rights and restrictions with
1266 respect to this document. Code Components extracted from this
1267 document must include Simplified BSD License text as described in
1268 Section 4.e of the Trust Legal Provisions and are provided without
1269 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1270 </section>
1271 </div>
1272 <div id="toc">
1273 <section id="section-toc.1">
1274 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1275 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1276 </h2>
1277 <nav class="toc"><ul class="toc ulEmpty compact">
1278 <li class="toc ulEmpty compact" id="section-toc.1-1.1">
1279 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1280 </li>
1281 <li class="toc ulEmpty compact" id="section-toc.1-1.2">
1282 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-conventions-used-in-this-do" class="xref">Conventions Used in This Document</a></p>
1283 </li>
1284 <li class="toc ulEmpty compact" id="section-toc.1-1.3">
1285 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-use-of-acme-for-issuing-end" class="xref">Use of ACME for Issuing End-User S/MIME Certificates</a></p>
1286 <ul class="toc ulEmpty compact">
1287 <li class="toc ulEmpty compact" id="section-toc.1-1.3.2.1">
1288 <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-acme-challenge-email" class="xref">ACME "Challenge" Email</a></p>
1289 </li>
1290 <li class="toc ulEmpty compact" id="section-toc.1-1.3.2.2">
1291 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-acme-response-email" class="xref">ACME "Response" Email</a></p>
1292 </li>
1293 <li class="toc ulEmpty compact" id="section-toc.1-1.3.2.3">
1294 <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-generating-encryption-only-" class="xref">Generating Encryption-Only or Signing-Only S/MIME Certificates</a></p>
1295 </li>
1296 </ul>
1297 </li>
1298 <li class="toc ulEmpty compact" id="section-toc.1-1.4">
1299 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-internationalization-consid" class="xref">Internationalization Considerations</a></p>
1300 </li>
1301 <li class="toc ulEmpty compact" id="section-toc.1-1.5">
1302 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1303 <ul class="toc ulEmpty compact">
1304 <li class="toc ulEmpty compact" id="section-toc.1-1.5.2.1">
1305 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-acme-identifier-type" class="xref">ACME Identifier Type</a></p>
1306 </li>
1307 <li class="toc ulEmpty compact" id="section-toc.1-1.5.2.2">
1308 <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-acme-challenge-type" class="xref">ACME Challenge Type</a></p>
1309 </li>
1310 </ul>
1311 </li>
1312 <li class="toc ulEmpty compact" id="section-toc.1-1.6">
1313 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1314 </li>
1315 <li class="toc ulEmpty compact" id="section-toc.1-1.7">
1316 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-references" class="xref">References</a></p>
1317 <ul class="toc ulEmpty compact">
1318 <li class="toc ulEmpty compact" id="section-toc.1-1.7.2.1">
1319 <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1320 </li>
1321 <li class="toc ulEmpty compact" id="section-toc.1-1.7.2.2">
1322 <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1323 </li>
1324 </ul>
1325 </li>
1326 <li class="toc ulEmpty compact" id="section-toc.1-1.8">
1327 <p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1328 </li>
1329 <li class="toc ulEmpty compact" id="section-toc.1-1.9">
1330 <p id="section-toc.1-1.9.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a></p>
1331 </li>
1332 </ul>
1333 </nav>
1334 </section>
1335 </div>
1336 <section id="section-1">
1337 <h2 id="name-introduction">
1338 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1339 </h2>
1340 <p id="section-1-1">
1341 ACME <span>[<a href="#RFC8555" class="xref">RFC8555</a>]</span> is a mechanism for automating certificate
1342 management on the Internet. It enables administrative entities to
1343 prove effective control over resources like domain names, and it
1344 automates the process of generating and issuing certificates.<a href="#section-1-1" class="pilcrow">¶</a></p>
1345 <p id="section-1-2">
1346 This document describes an extension to ACME for use by S/MIME.
1347 <a href="#smime" class="xref">Section 3</a> defines extensions for issuing end-user S/MIME <span>[<a href="#RFC8550" class="xref">RFC8550</a>]</span> certificates.<a href="#section-1-2" class="pilcrow">¶</a></p>
1348 <p id="section-1-3">
1349 This document aims to support both:<a href="#section-1-3" class="pilcrow">¶</a></p>
1350 <ol start="1" type="1" class="normal type-1" id="section-1-4">
1351 <li id="section-1-4.1">A Mail User Agent (MUA) that has a built-in ACME client that is aware
1352 of the extension described in this document. (We will call such MUAs "ACME-email-aware".)
1353 Such an MUA can present a nice user interface to the user and automate certificate issuance.<a href="#section-1-4.1" class="pilcrow">¶</a>
1354 </li>
1355 <li id="section-1-4.2">An MUA that is not ACME aware, with a separate ACME client implemented in a command-line tool or as a part of a website. While S/MIME certificate issuance is not going to
1356 be as painless as in the case of the ACME-email-aware MUA, the extra burden on a user is
1357 going to be minimal.<a href="#section-1-4.2" class="pilcrow">¶</a>
1358 </li>
1359 </ol>
1360 </section>
1361 <section id="section-2">
1362 <h2 id="name-conventions-used-in-this-do">
1363 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-conventions-used-in-this-do" class="section-name selfRef">Conventions Used in This Document</a>
1364 </h2>
1365 <p id="section-2-1">
1366 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>",
1367 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
1368 described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
1369 when, and only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1370 </section>
1371 <div id="smime">
1372 <section id="section-3">
1373 <h2 id="name-use-of-acme-for-issuing-end">
1374 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-use-of-acme-for-issuing-end" class="section-name selfRef">Use of ACME for Issuing End-User S/MIME Certificates</a>
1375 </h2>
1376 <p id="section-3-1">
1377 ACME <span>[<a href="#RFC8555" class="xref">RFC8555</a>]</span> defines a "dns" identifier type that is used to verify that a particular entity
1378 has control over a domain or specific service associated with the domain.
1379 In order to be able to issue end-user S/MIME certificates, ACME needs a new identifier type that
1380 proves ownership of an email address.<a href="#section-3-1" class="pilcrow">¶</a></p>
1381 <p id="section-3-2">
1382 This document defines a new identifier type, "email", which corresponds to an email address.
1383 The address can be all ASCII <span>[<a href="#RFC5321" class="xref">RFC5321</a>]</span> or internationalized <span>[<a href="#RFC6531" class="xref">RFC6531</a>]</span>;
1384 when an internationalized email address is used, the domain part can contain both U-labels and A-labels <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span>.
1385 This can be used with S/MIME or another similar service that requires possession of a certificate tied to an email address.<a href="#section-3-2" class="pilcrow">¶</a></p>
1386 <p id="section-3-3">
1387 Any identifier of type "email" in a newOrder request <span class="bcp14">MUST NOT</span> have a wildcard ("*") character in its value.<a href="#section-3-3" class="pilcrow">¶</a></p>
1388 <p id="section-3-4">
1389 A new challenge type, "email-reply-00", is used with the "email" identifier type,
1390 which provides proof that an ACME client has control over an email address.<a href="#section-3-4" class="pilcrow">¶</a></p>
1391 <p id="section-3-5">
1392 The process of issuing an S/MIME certificate works as follows. Note that the ACME client can be a standalone
1393 application (if the MUA is not ACME-email-aware) or can be a component of the MUA.<a href="#section-3-5" class="pilcrow">¶</a></p>
1394 <ol start="1" type="1" class="normal type-1" id="section-3-6">
1395 <li id="section-3-6.1">An end user initiates issuance of an S/MIME certificate for one of their email addresses.
1396 This might be done by using an email client UI, by running a command-line tool, by
1397 visiting a certificate authority web page, etc.
1398 This document doesn't prescribe a specific UI
1399 used to initiate S/MIME certificate issuance or where the ACME client is located.<a href="#section-3-6.1" class="pilcrow">¶</a>
1400 </li>
1401 <li id="section-3-6.2">
1402 The ACME-email-aware client component begins the certificate issuance process by sending a POST
1403 request to the server's newOrder resource, including the identifier of type "email".
1404 See <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.4" class="relref">Section 7.4</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> for more details.<a href="#section-3-6.2" class="pilcrow">¶</a>
1405 </li>
1406 <li id="section-3-6.3">
1407 <p id="section-3-6.3.1">
1408 The ACME server
1409 responds to the POST request, including an "authorizations" URL for the requested email address.
1410 The ACME client then retrieves information about the corresponding "email-reply-00" challenge,
1411 as specified in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.5" class="relref">Section 7.5</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>.
1412 The "token" field of the corresponding challenge object (from the "challenges" array)
1413 contains token-part2. token-part2 should contain at least 128 bits of entropy.
1414 The "type" field of the challenge object is "email-reply-00". The challenge object
1415 also contains the "from" field, with the email address that would be used in the From header field
1416 of the "challenge" email message (see the next step).<a href="#section-3-6.3.1" class="pilcrow">¶</a></p>
1417 <p id="section-3-6.3.2">An example challenge object might look like this:<a href="#section-3-6.3.2" class="pilcrow">¶</a></p>
1418 <div id="section-3-6.3.3">
1419 <pre class="sourcecode">
1420 {
1421 "type": "email-reply-00",
1422 "url": "https://example.com/acme/chall/ABprV_B7yEyA4f",
1423 "from": "[email protected]",
1424 "token": "DGyRejmCefe7v4NfDGDKfA"
1425 }
1426 </pre><a href="#section-3-6.3.3" class="pilcrow">¶</a>
1427 </div>
1428 </li>
1429 <li id="section-3-6.4">
1430 After responding to the authorization request, the ACME server
1431 generates another token and a "challenge" email message with the subject "ACME: &lt;token-part1&gt;",
1432 where &lt;token-part1&gt; is the base64url-encoded <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span> form of the token.
1433 The ACME server <span class="bcp14">MUST</span> generate a fresh token for each S/MIME issuance request (authorization request),
1434 and token-part1 <span class="bcp14">MUST</span> contain at least 128 bits of entropy.
1435 The "challenge" email message structure is described in more details in <a href="#acme-smime-challenge-email" class="xref">Section 3.1</a>.<a href="#section-3-6.4" class="pilcrow">¶</a>
1436 </li>
1437 <li id="section-3-6.5">
1438 The MUA retrieves and parses the "challenge" email message.
1439
1440 If the MUA is ACME-email-aware, it ignores any "challenge" email that is not expected,
1441 e.g., if there is no ACME certificate issuance pending.
1442 The ACME-email-aware MUA also ignores any "challenge" email that has the Subject header field
1443 that indicates that it is an email reply, e.g., a subject starting with the reply prefix "Re:".<a href="#section-3-6.5" class="pilcrow">¶</a>
1444 </li>
1445 <li id="section-3-6.6">
1446 The ACME client concatenates "token-part1" (received over email) and "token-part2"
1447 (received over HTTPS <span>[<a href="#RFC2818" class="xref">RFC2818</a>]</span>) to create the ACME "token" and calculates
1448 keyAuthorization (as per <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-8.1" class="relref">Section 8.1</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>).
1449 Then, it returns the base64url-encoded SHA-256 digest <span>[<a href="#RFC6234" class="xref">RFC6234</a>]</span> of the key authorization.
1450 The MUA returns the base64url-encoded SHA-256 digest obtained from the ACME client
1451 in the body of a "response" email message. The "response" email message structure
1452 is described in more details in <a href="#acme-smime-response-email" class="xref">Section 3.2</a>.
1453 If the MUA is ACME-email-aware, it <span class="bcp14">MUST NOT</span> respond to the same "challenge" email more than once.<a href="#section-3-6.6" class="pilcrow">¶</a>
1454 </li>
1455 <li id="section-3-6.7">
1456 Once the MUA sends the "response" email, the ACME client notifies the ACME server
1457 by POST to the challenge URL ("url" field).<a href="#section-3-6.7" class="pilcrow">¶</a>
1458 </li>
1459 <li id="section-3-6.8">
1460 The ACME client can start polling the authorization URL
1461 (using POST-as-GET requests) to see if the ACME server received and validated the "response" email message. (See <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.5.1" class="relref">Section 7.5.1</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> for more details.)
1462
1463 If the "status" field of the challenge switches to "valid",
1464 then the ACME client can proceed with request finalization.
1465 The Certificate Signing Request (CSR) <span class="bcp14">MUST</span> indicate the exact same
1466 set of requested identifiers as the initial newOrder request.
1467 For an identifier of type "email", the PKCS#10 <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span>
1468 CSR <span class="bcp14">MUST</span> contain the requested email address in an extensionRequest
1469 attribute <span>[<a href="#RFC2985" class="xref">RFC2985</a>]</span> requesting a subjectAltName extension.
1470 The email address <span class="bcp14">MUST</span> also match the From header field value of the "response" email message.<a href="#section-3-6.8" class="pilcrow">¶</a>
1471 </li>
1472 <li id="section-3-6.9">
1473 In order to request generation of signing-only or encryption-only S/MIME certificates
1474 (as opposed to requesting generation of S/MIME certificates suitable for both),
1475 the CSR needs to include the key usage extension (see <span><a href="https://www.rfc-editor.org/rfc/rfc8550#section-4.4.2" class="relref">Section 4.4.2</a> of [<a href="#RFC8550" class="xref">RFC8550</a>]</span>).
1476 This is described in more details in <a href="#acme-smime-sign-or-encrypt-only" class="xref">Section 3.3</a>.<a href="#section-3-6.9" class="pilcrow">¶</a>
1477 </li>
1478 <li id="section-3-6.10">
1479 If a request to finalize an order is successful, the ACME server will
1480 return a 200 (OK) with an updated order object.
1481 If the certificate is issued successfully, i.e., if the order "status"
1482 is "valid", then the ACME client can download the issued S/MIME certificate
1483 from the URL specified in the "certificate" field.<a href="#section-3-6.10" class="pilcrow">¶</a>
1484 </li>
1485 </ol>
1486 <div id="acme-smime-challenge-email">
1487 <section id="section-3.1">
1488 <h3 id="name-acme-challenge-email">
1489 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-acme-challenge-email" class="section-name selfRef">ACME "Challenge" Email</a>
1490 </h3>
1491 <p id="section-3.1-1">
1492 A "challenge" email message <span class="bcp14">MUST</span> have the following structure:<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1493 <ol start="1" type="1" class="normal type-1" id="section-3.1-2">
1494 <li id="section-3.1-2.1">
1495 The Subject header field has the following syntax: "ACME: &lt;token-part1&gt;",
1496 where the prefix "ACME:" is followed by folding white space (FWS; see <span>[<a href="#RFC5322" class="xref">RFC5322</a>]</span>)
1497 and then by &lt;token-part1&gt;, which is the base64url-encoded first part of the ACME token
1498 that <span class="bcp14">MUST</span> be at least 128 bits long after decoding.
1499 Due to the recommended 78-octet line-length limit
1500 in <span>[<a href="#RFC5322" class="xref">RFC5322</a>]</span>, the subject line can be folded, so white spaces (if any) within
1501 the &lt;token-part1&gt; <span class="bcp14">MUST</span> be ignored. <span>[<a href="#RFC2231" class="xref">RFC2231</a>]</span> encoding of the Subject header field <span class="bcp14">MUST</span> be supported,
1502 and, when used, only the "UTF-8" and "US-ASCII" charsets are allowed; other charsets <span class="bcp14">MUST NOT</span> be used. The US-ASCII charset <span class="bcp14">SHOULD</span> be used.<a href="#section-3.1-2.1" class="pilcrow">¶</a>
1503 </li>
1504 <li id="section-3.1-2.2">
1505 The From header field <span class="bcp14">MUST</span> be the same email address as specified in the "from" field of the challenge object.<a href="#section-3.1-2.2" class="pilcrow">¶</a>
1506 </li>
1507 <li id="section-3.1-2.3">
1508 The To header field <span class="bcp14">MUST</span> be the email address of the entity that requested the S/MIME certificate to be generated.<a href="#section-3.1-2.3" class="pilcrow">¶</a>
1509 </li>
1510 <li id="section-3.1-2.4">The message <span class="bcp14">MAY</span> contain a Reply-To and/or CC header field.<a href="#section-3.1-2.4" class="pilcrow">¶</a>
1511 </li>
1512 <li id="section-3.1-2.5">
1513 The message <span class="bcp14">MUST</span> include the Auto-Submitted header field with the value "auto-generated" <span>[<a href="#RFC3834" class="xref">RFC3834</a>]</span>.
1514 To aid in debugging (and, for some implementations, to make automated processing easier), the Auto-Submitted header field <span class="bcp14">SHOULD</span> include the "type=acme" parameter.
1515 It <span class="bcp14">MAY</span> include other optional parameters, as allowed by the syntax of the Auto-Submitted header field.<a href="#section-3.1-2.5" class="pilcrow">¶</a>
1516 </li>
1517 <li id="section-3.1-2.6">
1518 <p id="section-3.1-2.6.1">
1519 In order to prove authenticity of a challenge message, it <span class="bcp14">MUST</span> be signed using either DomainKeys Identified Mail (DKIM) <span>[<a href="#RFC6376" class="xref">RFC6376</a>]</span>
1520 or S/MIME <span>[<a href="#RFC8551" class="xref">RFC8551</a>]</span>.<a href="#section-3.1-2.6.1" class="pilcrow">¶</a></p>
1521 <ul class="normal">
1522 <li class="normal" id="section-3.1-2.6.2.1">
1523 If DKIM signing is used, the resulting DKIM-Signature header field <span class="bcp14">MUST</span> contain the "h=" tag that includes
1524 at least the From, Sender, Reply-To, To, CC, Subject, Date, In-Reply-To, References,
1525 Message-ID, Auto-Submitted, Content-Type, and Content-Transfer-Encoding header fields.
1526 The DKIM-Signature header field's "h=" tag <span class="bcp14">SHOULD</span> also include the
1527 Resent-Date, Resent-From, Resent-To, Resent-Cc, List-Id, List-Help, List-Unsubscribe,
1528 List-Subscribe, List-Post, List-Owner, List-Archive, and List-Unsubscribe-Post header fields.
1529 The domain from the "d=" tag of the DKIM-Signature header field <span class="bcp14">MUST</span> be the same as the domain from
1530 the From header field of the "challenge" email.<a href="#section-3.1-2.6.2.1" class="pilcrow">¶</a>
1531 </li>
1532 <li class="normal" id="section-3.1-2.6.2.2">
1533 If S/MIME signing is used, the certificate corresponding to the signer <span class="bcp14">MUST</span> have an rfc822Name subjectAltName extension
1534 with the value equal to the From header field email address of the "challenge" email.<a href="#section-3.1-2.6.2.2" class="pilcrow">¶</a>
1535 </li>
1536 </ul>
1537 </li>
1538 <li id="section-3.1-2.7">
1539 The body of the challenge message is not used for automated processing, so it can be any media type.
1540 (However, there are extra requirements on S/MIME signing, if used. See below.)
1541 Typically, it is text/plain or text/html containing a human-readable explanation of the purpose of the message.
1542 If S/MIME signing is used to prove authenticity of the challenge message,
1543 then the multipart/signed or "application/pkcs7-mime; smime-type=signed-data;" media type should be used.
1544 Either way, it <span class="bcp14">MUST</span> use S/MIME header protection.<a href="#section-3.1-2.7" class="pilcrow">¶</a>
1545 </li>
1546 </ol>
1547 <p id="section-3.1-3">
1548 An email client compliant with this specification that detects that a particular "challenge" email
1549 fails the validation described above <span class="bcp14">MUST</span> ignore the challenge and thus will not generate a "response" email.
1550 To aid in debugging, such failed validations <span class="bcp14">SHOULD</span> be logged.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
1551 <p id="section-3.1-4" class="keepWithNext">
1552 Here is an example of an ACME "challenge" email (note that, for simplicity, DKIM-related header fields are not included).<a href="#section-3.1-4" class="pilcrow">¶</a></p>
1553 <figure id="figure-1">
1554 <div class="artwork art-text alignLeft" id="section-3.1-5.1">
1555 <pre>
1556 Auto-Submitted: auto-generated; type=acme
1557 Date: Sat, 5 Dec 2020 10:08:55 +0100
1558 Message-ID: &lt;[email protected]&gt;
1559 From: [email protected]
1560 To: [email protected]
1561 Subject: ACME: LgYemJLy3F1LDkiJrdIGbEzyFJyOyf6vBdyZ1TG3sME=
1562 Content-Type: text/plain
1563 MIME-Version: 1.0
1564
1565 This is an automatically generated ACME challenge for email address
1566 "[email protected]". If you haven't requested an S/MIME
1567 certificate generation for this email address, be very afraid.
1568 If you did request it, your email client might be able to process
1569 this request automatically, or you might have to paste the first
1570 token part into an external program.
1571 </pre>
1572 </div>
1573 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a></figcaption></figure>
1574 <p id="section-3.1-6" class="keepWithPrevious"></p>
1575 </section>
1576 </div>
1577 <div id="acme-smime-response-email">
1578 <section id="section-3.2">
1579 <h3 id="name-acme-response-email">
1580 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-acme-response-email" class="section-name selfRef">ACME "Response" Email</a>
1581 </h3>
1582 <p id="section-3.2-1">
1583 A valid "response" email message <span class="bcp14">MUST</span> have the following structure:<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1584 <ol start="1" type="1" class="normal type-1" id="section-3.2-2">
1585 <li id="section-3.2-2.1">
1586 The Subject header field is formed as a reply to the ACME "challenge" email
1587 (see <a href="#acme-smime-challenge-email" class="xref">Section 3.1</a>).
1588 Its syntax is the same as that of the challenge message except that it may be prefixed
1589 by a US-ASCII reply prefix (typically "Re:") and FWS (see <span>[<a href="#RFC5322" class="xref">RFC5322</a>]</span>), as is normal in reply messages. When
1590 parsing the subject, ACME servers <span class="bcp14">MUST</span> decode <span>[<a href="#RFC2231" class="xref">RFC2231</a>]</span> encoding (if any), and
1591 then they can ignore any prefix before the "ACME:" label.<a href="#section-3.2-2.1" class="pilcrow">¶</a>
1592 </li>
1593 <li id="section-3.2-2.2">The From header field contains the email address of the user that is requesting S/MIME certificate issuance.<a href="#section-3.2-2.2" class="pilcrow">¶</a>
1594 </li>
1595 <li id="section-3.2-2.3">The To header field of the response contains the value from the Reply-To header field from the
1596 challenge message (if set). Otherwise, it contains the value from the From header field of the
1597 challenge message.<a href="#section-3.2-2.3" class="pilcrow">¶</a>
1598 </li>
1599 <li id="section-3.2-2.4">The Cc header field is ignored if present in the "response" email message.<a href="#section-3.2-2.4" class="pilcrow">¶</a>
1600 </li>
1601 <li id="section-3.2-2.5">The In-Reply-To header field <span class="bcp14">SHOULD</span> be set to the Message-ID header field of the challenge message
1602 according to rules in <span><a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.6.4" class="relref">Section 3.6.4</a> of [<a href="#RFC5322" class="xref">RFC5322</a>]</span>.<a href="#section-3.2-2.5" class="pilcrow">¶</a>
1603 </li>
1604 <li id="section-3.2-2.6">List-* header fields <span>[<a href="#RFC4021" class="xref">RFC4021</a>]</span><span>[<a href="#RFC8058" class="xref">RFC8058</a>]</span> <span class="bcp14">MUST</span> be absent (i.e., the reply can't come from a mailing list).<a href="#section-3.2-2.6" class="pilcrow">¶</a>
1605 </li>
1606 <li id="section-3.2-2.7">
1607 <p id="section-3.2-2.7.1">The media type of the "response" email message is either text/plain or multipart/alternative <span>[<a href="#RFC2046" class="xref">RFC2046</a>]</span>, containing
1608 text/plain as one of the alternatives. (Note that the requirement to support multipart/alternative is to allow use of ACME-unaware MUAs,
1609 which can't always generate pure text/plain, e.g., if they reply to a text/html).
1610 The text/plain body part (whether or not it is inside multipart/alternative)
1611 <span class="bcp14">MUST</span> contain a block of lines starting with the line "-----BEGIN ACME RESPONSE-----", followed by one
1612 or more lines containing the base64url-encoded SHA-256 digest <span>[<a href="#RFC6234" class="xref">RFC6234</a>]</span>
1613 of the key authorization, calculated from concatenated token-part1 (received over email)
1614 and token-part2 (received over HTTPS), as outlined in the 5th bullet in <a href="#smime" class="xref">Section 3</a>.
1615 (Note that each line of text/plain is terminated by CRLF. Bare LFs or bare CRs are not allowed.)
1616 Due to historical line-length limitations in email, line endings (CRLFs)
1617 can be freely inserted in the middle of the encoded digest,
1618 so they <span class="bcp14">MUST</span> be ignored when processing it. The final line of the encoded digest
1619 is followed by a line containing:<a href="#section-3.2-2.7.1" class="pilcrow">¶</a></p>
1620 <div class="artwork art-text alignLeft" id="section-3.2-2.7.2">
1621 <pre>
1622 -----END ACME RESPONSE-----
1623 </pre><a href="#section-3.2-2.7.2" class="pilcrow">¶</a>
1624 </div>
1625 <p id="section-3.2-2.7.3">Any text before and after this block is ignored. For example, such text might explain what
1626 to do with it for ACME-unaware clients.<a href="#section-3.2-2.7.3" class="pilcrow">¶</a></p>
1627 </li>
1628 <li id="section-3.2-2.8">There is no need to use any Content-Transfer-Encoding other than 7bit for the text/plain body part.
1629 Use of quoted-printable or base64 in a "response" email message is not necessary and should be avoided,
1630 though it is permitted.<a href="#section-3.2-2.8" class="pilcrow">¶</a>
1631 </li>
1632 <li id="section-3.2-2.9">
1633 In order to prove authenticity of a response message, it <span class="bcp14">MUST</span> be DKIM <span>[<a href="#RFC6376" class="xref">RFC6376</a>]</span>
1634 signed. The resulting DKIM-Signature header field <span class="bcp14">MUST</span> contain the "h=" tag that includes
1635 at least the From, Sender, Reply-To, To, CC, Subject, Date, In-Reply-To, References,
1636 Message-ID, Content-Type, and Content-Transfer-Encoding header fields.
1637 The DKIM-Signature header field's "h=" tag <span class="bcp14">SHOULD</span> also include the
1638 Resent-Date, Resent-From, Resent-To, Resent-Cc, List-Id, List-Help, List-Unsubscribe,
1639 List-Subscribe, List-Post, List-Owner, List-Archive, and List-Unsubscribe-Post header fields.
1640 The domain from the "d=" tag of DKIM-Signature header field <span class="bcp14">MUST</span> be the same as the domain from
1641 the From header field of the "response" email.<a href="#section-3.2-2.9" class="pilcrow">¶</a>
1642 </li>
1643 </ol>
1644 <p id="section-3.2-3" class="keepWithNext">
1645 Here is an example of an ACME "response" email (note that, for simplicity, DKIM-related header fields are not included).<a href="#section-3.2-3" class="pilcrow">¶</a></p>
1646 <figure id="figure-2">
1647 <div class="artwork art-text alignLeft" id="section-3.2-4.1">
1648 <pre>
1649 Date: Sat, 5 Dec 2020 12:01:45 +0100
1650 Message-ID: &lt;[email protected]&gt;
1651 In-Reply-To: &lt;[email protected]&gt;
1652 From: [email protected]
1653 To: [email protected]
1654 Subject: Re: ACME: LgYemJLy3F1LDkiJrdIGbEzyFJyOyf6vBdyZ1TG3sME=
1655 Content-Type: text/plain
1656 MIME-Version: 1.0
1657
1658 -----BEGIN ACME RESPONSE-----
1659 LoqXcYV8q5ONbJQxbmR7SCTNo3tiAXDfowy
1660 jxAjEuX0=
1661 -----END ACME RESPONSE-----
1662 </pre>
1663 </div>
1664 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a></figcaption></figure>
1665 <p id="section-3.2-5" class="keepWithPrevious"></p>
1666 </section>
1667 </div>
1668 <div id="acme-smime-sign-or-encrypt-only">
1669 <section id="section-3.3">
1670 <h3 id="name-generating-encryption-only-">
1671 <a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-generating-encryption-only-" class="section-name selfRef">Generating Encryption-Only or Signing-Only S/MIME Certificates</a>
1672 </h3>
1673 <p id="section-3.3-1">
1674 ACME extensions specified in this document can be used to request signing-only or
1675 encryption-only S/MIME certificates.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
1676 <p id="section-3.3-2">
1677 In order to request signing-only S/MIME certificates, the CSR <span class="bcp14">MUST</span> include the key usage
1678 extension with digitalSignature and/or nonRepudiation bits set and no other bits set.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
1679 <p id="section-3.3-3">
1680 In order to request encryption-only S/MIME certificates, the CSR <span class="bcp14">MUST</span> include the key usage
1681 extension with keyEncipherment or keyAgreement bits set and no other bits set.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
1682 <p id="section-3.3-4">
1683 Presence of both of the above sets of key usage bits in the CSR,
1684 as well as absence of the key usage extension in the CSR,
1685 signals to the ACME server to issue an S/MIME certificate suitable for both signing
1686 and encryption.<a href="#section-3.3-4" class="pilcrow">¶</a></p>
1687 </section>
1688 </div>
1689 </section>
1690 </div>
1691 <section id="section-4">
1692 <h2 id="name-internationalization-consid">
1693 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-internationalization-consid" class="section-name selfRef">Internationalization Considerations</a>
1694 </h2>
1695 <p id="section-4-1">
1696 <span>[<a href="#RFC8616" class="xref">RFC8616</a>]</span> updated/clarified use of DKIM with internationalized email addresses <span>[<a href="#RFC6531" class="xref">RFC6531</a>]</span>.
1697 Please consult <span>[<a href="#RFC8616" class="xref">RFC8616</a>]</span> in regards to any changes that need to be implemented.<a href="#section-4-1" class="pilcrow">¶</a></p>
1698 <p id="section-4-2">
1699 Use of non-ASCII characters in left-hand sides of internationalized email addresses requires putting
1700 internationalized email addresses in X.509 certificates <span>[<a href="#RFC8398" class="xref">RFC8398</a>]</span>.<a href="#section-4-2" class="pilcrow">¶</a></p>
1701 </section>
1702 <section id="section-5">
1703 <h2 id="name-iana-considerations">
1704 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1705 </h2>
1706 <section id="section-5.1">
1707 <h3 id="name-acme-identifier-type">
1708 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-acme-identifier-type" class="section-name selfRef">ACME Identifier Type</a>
1709 </h3>
1710 <p id="section-5.1-1">
1711 IANA has registered a new identifier type in the "ACME Identifier
1712 Types" registry defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-9.7.7" class="relref">Section 9.7.7</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> with Label "email" and a Reference to this document,
1713 <span>[<a href="#RFC5321" class="xref">RFC5321</a>]</span>, and <span>[<a href="#RFC6531" class="xref">RFC6531</a>]</span>. The new identifier type corresponds to an (all
1714 ASCII) email address <span>[<a href="#RFC5321" class="xref">RFC5321</a>]</span> or
1715 internationalized email addresses <span>[<a href="#RFC6531" class="xref">RFC6531</a>]</span>.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
1716 </section>
1717 <section id="section-5.2">
1718 <h3 id="name-acme-challenge-type">
1719 <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-acme-challenge-type" class="section-name selfRef">ACME Challenge Type</a>
1720 </h3>
1721 <p id="section-5.2-1">
1722 IANA has registered a new entry in the "ACME Validation Methods" registry
1723 defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-9.7.8" class="relref">Section 9.7.8</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>.
1724 This entry is as follows:<a href="#section-5.2-1" class="pilcrow">¶</a></p>
1725 <table class="center" id="table-1">
1726 <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
1727 <thead>
1728 <tr>
1729 <th class="text-center" rowspan="1" colspan="1">Label</th>
1730 <th class="text-center" rowspan="1" colspan="1">Identifier Type</th>
1731 <th class="text-center" rowspan="1" colspan="1">ACME</th>
1732 <th class="text-center" rowspan="1" colspan="1">Reference</th>
1733 </tr>
1734 </thead>
1735 <tbody>
1736 <tr>
1737 <td class="text-center" rowspan="1" colspan="1">email-reply-00</td>
1738 <td class="text-center" rowspan="1" colspan="1">email</td>
1739 <td class="text-center" rowspan="1" colspan="1">Y</td>
1740 <td class="text-center" rowspan="1" colspan="1">RFC 8823</td>
1741 </tr>
1742 </tbody>
1743 </table>
1744 </section>
1745 </section>
1746 <div id="seccons">
1747 <section id="section-6">
1748 <h2 id="name-security-considerations">
1749 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1750 </h2>
1751 <p id="section-6-1">
1752 Please see the Security Considerations section of <span>[<a href="#RFC8555" class="xref">RFC8555</a>]</span> for general security
1753 considerations related to the use of ACME. This challenge/response
1754 protocol demonstrates that an entity that controls the private key
1755 (corresponding to the public key in the certificate) also controls the
1756 named email account. The ACME server is confirming that the requested
1757 email address belongs to the entity that requested the certificate,
1758 but this makes no claim to address correctness or fitness for purpose.
1759 If such claims are needed, they must be obtained by some other
1760 mechanism.<a href="#section-6-1" class="pilcrow">¶</a></p>
1761 <p id="section-6-2">
1762 The security of the "email-reply-00" challenge type depends on the security of the email system.
1763 A third party that can read and reply to user's email messages (by possessing a user's password
1764 or a secret derived from it that can give read and reply access, such as "password equivalent" information,
1765 or by being given permissions to act on a user's behalf using email delegation features common
1766 in some email systems) can request S/MIME certificates using the protocol specified in this document
1767 and is indistinguishable from the email account owner.
1768 This has several possible implications:<a href="#section-6-2" class="pilcrow">¶</a></p>
1769 <ol start="1" type="1" class="normal type-1" id="section-6-3">
1770 <li id="section-6-3.1">An entity that compromised an email account would be able to request S/MIME certificates
1771 using the protocol specified in this document, and such entity couldn't be distinguished from
1772 the legitimate email account owner (unless some external sources of information are consulted).<a href="#section-6-3.1" class="pilcrow">¶</a>
1773 </li>
1774 <li id="section-6-3.2">For email addresses with legitimate shared access/control by
1775 multiple users, any such user would be able to request S/MIME
1776 certificates using the protocol specified in this document; such
1777 requests can't be attributed to a specific user without consulting
1778 external systems (such as IMAP/SMTP access logs).<a href="#section-6-3.2" class="pilcrow">¶</a>
1779 </li>
1780 <li id="section-6-3.3">The protocol specified in this document is not suitable for use with email addresses
1781 associated with mailing lists <span>[<a href="#RFC5321" class="xref">RFC5321</a>]</span>. While it is not always
1782 possible to guarantee that a particular S/MIME certificate request is not from a mailing list
1783 address, prohibition on inclusion of List-* header fields helps certificate issuers
1784 to handle most common cases.<a href="#section-6-3.3" class="pilcrow">¶</a>
1785 </li>
1786 </ol>
1787 <p id="section-6-4">
1788 An email system in its turn depends on DNS. A third party that can manipulate DNS MX records
1789 for a domain might be able to redirect an email and can get (at least temporary) read and reply access to it.
1790 Similar considerations apply to DKIM TXT records in DNS.
1791 Use of DNSSEC by email system administrators is recommended to avoid making it easy to spoof
1792 DNS records affecting an email system. However, use of DNSSEC is not ubiquitous at the time of
1793 publishing of this document, so it is not required here.
1794
1795 Also, many existing systems that rely on verification of ownership of an email address --
1796 for example, 2-factor authentication systems used by banks or traditional certificate issuance
1797 systems -- send email messages to email addresses, expecting the owner to click on the link supplied
1798 in them (or to reply to a message), without requiring use of DNSSEC. So the risk of not requiring
1799 DNSSEC is presumed acceptable in this document.<a href="#section-6-4" class="pilcrow">¶</a></p>
1800 <p id="section-6-5">
1801 An ACME email challenge message can be forged by an attacker.
1802
1803 As per requirements on an ACME-email-aware MUA specified in <a href="#smime" class="xref">Section 3</a>,
1804 the MUA will not respond to requests it is not expecting.
1805 Even if the attacker causes the erroneous "response" email to go to
1806 an attacker-controlled email address, very little information is leaked --
1807 the SHA-256 hash of the key authorization would be leaked, not the key
1808 authorization itself, so no parts of the token or the account key
1809 thumbprint are leaked.<a href="#section-6-5" class="pilcrow">¶</a></p>
1810 <p id="section-6-6">
1811 An attacker that can read the "response" email has only one chance to guess the
1812 token-part2. Even if the attacker can guess it right, it still needs to know
1813 the ACME account key to be able to make use of the intercepted SHA-256 hash of
1814 the key authorization.<a href="#section-6-6" class="pilcrow">¶</a></p>
1815 <p id="section-6-7">
1816 Also see the Security Considerations section of <span>[<a href="#RFC6376" class="xref">RFC6376</a>]</span> for details on how DKIM depends
1817 on the DNS and the respective vulnerabilities this dependence has.<a href="#section-6-7" class="pilcrow">¶</a></p>
1818 </section>
1819 </div>
1820 <section id="section-7">
1821 <h2 id="name-references">
1822 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
1823 </h2>
1824 <section id="section-7.1">
1825 <h3 id="name-normative-references">
1826 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
1827 </h3>
1828 <dl class="references">
1829 <dt id="RFC2046">[RFC2046]</dt>
1830 <dd>
1831 <span class="refAuthor">Freed, N.</span> and <span class="refAuthor">N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"</span>, <span class="seriesInfo">RFC 2046</span>, <span class="seriesInfo">DOI 10.17487/RFC2046</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2046">https://www.rfc-editor.org/info/rfc2046</a>&gt;</span>. </dd>
1832 <dd class="break"></dd>
1833 <dt id="RFC2119">[RFC2119]</dt>
1834 <dd>
1835 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
1836 <dd class="break"></dd>
1837 <dt id="RFC2231">[RFC2231]</dt>
1838 <dd>
1839 <span class="refAuthor">Freed, N.</span> and <span class="refAuthor">K. Moore</span>, <span class="refTitle">"MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"</span>, <span class="seriesInfo">RFC 2231</span>, <span class="seriesInfo">DOI 10.17487/RFC2231</span>, <time datetime="1997-11" class="refDate">November 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2231">https://www.rfc-editor.org/info/rfc2231</a>&gt;</span>. </dd>
1840 <dd class="break"></dd>
1841 <dt id="RFC2818">[RFC2818]</dt>
1842 <dd>
1843 <span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"HTTP Over TLS"</span>, <span class="seriesInfo">RFC 2818</span>, <span class="seriesInfo">DOI 10.17487/RFC2818</span>, <time datetime="2000-05" class="refDate">May 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2818">https://www.rfc-editor.org/info/rfc2818</a>&gt;</span>. </dd>
1844 <dd class="break"></dd>
1845 <dt id="RFC2985">[RFC2985]</dt>
1846 <dd>
1847 <span class="refAuthor">Nystrom, M.</span> and <span class="refAuthor">B. Kaliski</span>, <span class="refTitle">"PKCS #9: Selected Object Classes and Attribute Types Version 2.0"</span>, <span class="seriesInfo">RFC 2985</span>, <span class="seriesInfo">DOI 10.17487/RFC2985</span>, <time datetime="2000-11" class="refDate">November 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2985">https://www.rfc-editor.org/info/rfc2985</a>&gt;</span>. </dd>
1848 <dd class="break"></dd>
1849 <dt id="RFC2986">[RFC2986]</dt>
1850 <dd>
1851 <span class="refAuthor">Nystrom, M.</span> and <span class="refAuthor">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" class="refDate">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>
1852 <dd class="break"></dd>
1853 <dt id="RFC3834">[RFC3834]</dt>
1854 <dd>
1855 <span class="refAuthor">Moore, K.</span>, <span class="refTitle">"Recommendations for Automatic Responses to Electronic Mail"</span>, <span class="seriesInfo">RFC 3834</span>, <span class="seriesInfo">DOI 10.17487/RFC3834</span>, <time datetime="2004-08" class="refDate">August 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3834">https://www.rfc-editor.org/info/rfc3834</a>&gt;</span>. </dd>
1856 <dd class="break"></dd>
1857 <dt id="RFC4648">[RFC4648]</dt>
1858 <dd>
1859 <span class="refAuthor">Josefsson, S.</span>, <span class="refTitle">"The Base16, Base32, and Base64 Data Encodings"</span>, <span class="seriesInfo">RFC 4648</span>, <span class="seriesInfo">DOI 10.17487/RFC4648</span>, <time datetime="2006-10" class="refDate">October 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4648">https://www.rfc-editor.org/info/rfc4648</a>&gt;</span>. </dd>
1860 <dd class="break"></dd>
1861 <dt id="RFC5321">[RFC5321]</dt>
1862 <dd>
1863 <span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Simple Mail Transfer Protocol"</span>, <span class="seriesInfo">RFC 5321</span>, <span class="seriesInfo">DOI 10.17487/RFC5321</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5321">https://www.rfc-editor.org/info/rfc5321</a>&gt;</span>. </dd>
1864 <dd class="break"></dd>
1865 <dt id="RFC5322">[RFC5322]</dt>
1866 <dd>
1867 <span class="refAuthor">Resnick, P., Ed.</span>, <span class="refTitle">"Internet Message Format"</span>, <span class="seriesInfo">RFC 5322</span>, <span class="seriesInfo">DOI 10.17487/RFC5322</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5322">https://www.rfc-editor.org/info/rfc5322</a>&gt;</span>. </dd>
1868 <dd class="break"></dd>
1869 <dt id="RFC5890">[RFC5890]</dt>
1870 <dd>
1871 <span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"</span>, <span class="seriesInfo">RFC 5890</span>, <span class="seriesInfo">DOI 10.17487/RFC5890</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5890">https://www.rfc-editor.org/info/rfc5890</a>&gt;</span>. </dd>
1872 <dd class="break"></dd>
1873 <dt id="RFC6234">[RFC6234]</dt>
1874 <dd>
1875 <span class="refAuthor">Eastlake 3rd, D.</span> and <span class="refAuthor">T. Hansen</span>, <span class="refTitle">"US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)"</span>, <span class="seriesInfo">RFC 6234</span>, <span class="seriesInfo">DOI 10.17487/RFC6234</span>, <time datetime="2011-05" class="refDate">May 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6234">https://www.rfc-editor.org/info/rfc6234</a>&gt;</span>. </dd>
1876 <dd class="break"></dd>
1877 <dt id="RFC6376">[RFC6376]</dt>
1878 <dd>
1879 <span class="refAuthor">Crocker, D., Ed.</span>, <span class="refAuthor">Hansen, T., Ed.</span>, and <span class="refAuthor">M. Kucherawy, Ed.</span>, <span class="refTitle">"DomainKeys Identified Mail (DKIM) Signatures"</span>, <span class="seriesInfo">STD 76</span>, <span class="seriesInfo">RFC 6376</span>, <span class="seriesInfo">DOI 10.17487/RFC6376</span>, <time datetime="2011-09" class="refDate">September 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6376">https://www.rfc-editor.org/info/rfc6376</a>&gt;</span>. </dd>
1880 <dd class="break"></dd>
1881 <dt id="RFC6531">[RFC6531]</dt>
1882 <dd>
1883 <span class="refAuthor">Yao, J.</span> and <span class="refAuthor">W. Mao</span>, <span class="refTitle">"SMTP Extension for Internationalized Email"</span>, <span class="seriesInfo">RFC 6531</span>, <span class="seriesInfo">DOI 10.17487/RFC6531</span>, <time datetime="2012-02" class="refDate">February 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6531">https://www.rfc-editor.org/info/rfc6531</a>&gt;</span>. </dd>
1884 <dd class="break"></dd>
1885 <dt id="RFC8174">[RFC8174]</dt>
1886 <dd>
1887 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
1888 <dd class="break"></dd>
1889 <dt id="RFC8398">[RFC8398]</dt>
1890 <dd>
1891 <span class="refAuthor">Melnikov, A., Ed.</span> and <span class="refAuthor">W. Chuang, Ed.</span>, <span class="refTitle">"Internationalized Email Addresses in X.509 Certificates"</span>, <span class="seriesInfo">RFC 8398</span>, <span class="seriesInfo">DOI 10.17487/RFC8398</span>, <time datetime="2018-05" class="refDate">May 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8398">https://www.rfc-editor.org/info/rfc8398</a>&gt;</span>. </dd>
1892 <dd class="break"></dd>
1893 <dt id="RFC8550">[RFC8550]</dt>
1894 <dd>
1895 <span class="refAuthor">Schaad, J.</span>, <span class="refAuthor">Ramsdell, B.</span>, and <span class="refAuthor">S. Turner</span>, <span class="refTitle">"Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling"</span>, <span class="seriesInfo">RFC 8550</span>, <span class="seriesInfo">DOI 10.17487/RFC8550</span>, <time datetime="2019-04" class="refDate">April 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8550">https://www.rfc-editor.org/info/rfc8550</a>&gt;</span>. </dd>
1896 <dd class="break"></dd>
1897 <dt id="RFC8551">[RFC8551]</dt>
1898 <dd>
1899 <span class="refAuthor">Schaad, J.</span>, <span class="refAuthor">Ramsdell, B.</span>, and <span class="refAuthor">S. Turner</span>, <span class="refTitle">"Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification"</span>, <span class="seriesInfo">RFC 8551</span>, <span class="seriesInfo">DOI 10.17487/RFC8551</span>, <time datetime="2019-04" class="refDate">April 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8551">https://www.rfc-editor.org/info/rfc8551</a>&gt;</span>. </dd>
1900 <dd class="break"></dd>
1901 <dt id="RFC8555">[RFC8555]</dt>
1902 <dd>
1903 <span class="refAuthor">Barnes, R.</span>, <span class="refAuthor">Hoffman-Andrews, J.</span>, <span class="refAuthor">McCarney, D.</span>, and <span class="refAuthor">J. Kasten</span>, <span class="refTitle">"Automatic Certificate Management Environment (ACME)"</span>, <span class="seriesInfo">RFC 8555</span>, <span class="seriesInfo">DOI 10.17487/RFC8555</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8555">https://www.rfc-editor.org/info/rfc8555</a>&gt;</span>. </dd>
1904 <dd class="break"></dd>
1905 <dt id="RFC8616">[RFC8616]</dt>
1906 <dd>
1907 <span class="refAuthor">Levine, J.</span>, <span class="refTitle">"Email Authentication for Internationalized Mail"</span>, <span class="seriesInfo">RFC 8616</span>, <span class="seriesInfo">DOI 10.17487/RFC8616</span>, <time datetime="2019-06" class="refDate">June 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8616">https://www.rfc-editor.org/info/rfc8616</a>&gt;</span>. </dd>
1908 <dd class="break"></dd>
1909 </dl>
1910 </section>
1911 <section id="section-7.2">
1912 <h3 id="name-informative-references">
1913 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
1914 </h3>
1915 <dl class="references">
1916 <dt id="RFC4021">[RFC4021]</dt>
1917 <dd>
1918 <span class="refAuthor">Klyne, G.</span> and <span class="refAuthor">J. Palme</span>, <span class="refTitle">"Registration of Mail and MIME Header Fields"</span>, <span class="seriesInfo">RFC 4021</span>, <span class="seriesInfo">DOI 10.17487/RFC4021</span>, <time datetime="2005-03" class="refDate">March 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4021">https://www.rfc-editor.org/info/rfc4021</a>&gt;</span>. </dd>
1919 <dd class="break"></dd>
1920 <dt id="RFC8058">[RFC8058]</dt>
1921 <dd>
1922 <span class="refAuthor">Levine, J.</span> and <span class="refAuthor">T. Herkula</span>, <span class="refTitle">"Signaling One-Click Functionality for List Email Headers"</span>, <span class="seriesInfo">RFC 8058</span>, <span class="seriesInfo">DOI 10.17487/RFC8058</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8058">https://www.rfc-editor.org/info/rfc8058</a>&gt;</span>. </dd>
1923 <dd class="break"></dd>
1924 </dl>
1925 </section>
1926 </section>
1927 <section id="section-appendix.a">
1928 <h2 id="name-acknowledgements">
1929 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
1930 </h2>
1931 <p id="section-appendix.a-1">Thank you to <span class="contact-name">Andreas Schulze</span>, <span class="contact-name">Gerd v. Egidy</span>,
1932 <span class="contact-name">James A. Baker</span>, <span class="contact-name">Ben Schwartz</span>,
1933 <span class="contact-name">Peter Yee</span>, <span class="contact-name">Hilarie Orman</span>,
1934 <span class="contact-name">Michael Jenkins</span>, <span class="contact-name">Barry Leiba</span>,
1935 <span class="contact-name">Fraser Tweedale</span>, <span class="contact-name">Daniel Kahn Gillmor</span>, and
1936 <span class="contact-name">Benjamin Kaduk</span> for their suggestions, comments, and corrections of this document.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
1937 </section>
1938 <div id="authors-addresses">
1939 <section id="section-appendix.b">
1940 <h2 id="name-authors-address">
1941 <a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
1942 </h2>
1943 <address class="vcard">
1944 <div dir="auto" class="left"><span class="fn nameRole">Alexey Melnikov</span></div>
1945 <div dir="auto" class="left"><span class="org">Isode Ltd</span></div>
1946 <div dir="auto" class="left"><span class="street-address">14 Castle Mews</span></div>
1947 <div dir="auto" class="left"><span class="locality">Hampton, Middlesex</span></div>
1948 <div dir="auto" class="left"><span class="postal-code">TW12 2NP</span></div>
1949 <div dir="auto" class="left"><span class="country-name">United Kingdom</span></div>
1950 <div class="email">
1951 <span>Email:</span>
1952 <a href="mailto:[email protected]" class="email">[email protected]</a>
1953 </div>
1954 </address>
1955 </section>
1956 </div>
1957 <script>const toc = document.getElementById("toc");
1958 toc.querySelector("h2").addEventListener("click", e => {
1959 toc.classList.toggle("active");
1960 });
1961 toc.querySelector("nav").addEventListener("click", e => {
1962 toc.classList.remove("active");
1963 });
1964 </script>
1965 </body>
1966 </html>