Debian Codegraph @

rfc8739.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 8739: Support for Short-Term, Automatically Renewed (STAR) Certificates in the Automated Certificate Management Environment (ACME)</title>
8 <meta content="Yaron Sheffer" name="author">
9 <meta content="Diego Lopez" name="author">
10 <meta content="Oscar Gonzalez de Dios" name="author">
11 <meta content="Antonio Agustin Pastor Perales" name="author">
12 <meta content="Thomas Fossati" name="author">
13 <meta content="
14 Public key certificates need to be revoked when they are compromised,
15 that is, when the associated private key is exposed to an unauthorized
16 entity. However, the revocation process is often unreliable. An
17 alternative to revocation is issuing a sequence of certificates, each
18 with a short validity period, and terminating the sequence upon
19 compromise. This memo proposes an Automated Certificate Management
20 Environment (ACME) extension to enable the issuance of Short-Term,
21 Automatically Renewed (STAR) X.509 certificates.
22 " name="description">
23 <meta content="xml2rfc 2.40.1" name="generator">
24 <meta content="OCSP" name="keyword">
25 <meta content="CRL" name="keyword">
26 <meta content="revocation" name="keyword">
27 <meta content="8739" name="rfc.number">
28 <link href="rfc8739.xml" rel="alternate" type="application/rfc+xml">
29 <link href="#copyright" rel="license">
30 <style type="text/css">/*
31
32 NOTE: Changes at the bottom of this file overrides some earlier settings.
33
34 Once the style has stabilized and has been adopted as an official RFC style,
35 this can be consolidated so that style settings occur only in one place, but
36 for now the contents of this file consists first of the initial CSS work as
37 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
38 commented changes found necssary during the development of the v3
39 formatters.
40
41 */
42
43 /* fonts */
44 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
45 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
46 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
47
48 @viewport {
49 zoom: 1.0;
50 width: extend-to-zoom;
51 }
52 @-ms-viewport {
53 width: extend-to-zoom;
54 zoom: 1.0;
55 }
56 /* general and mobile first */
57 html {
58 }
59 body {
60 max-width: 90%;
61 margin: 1.5em auto;
62 color: #222;
63 background-color: #fff;
64 font-size: 14px;
65 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
66 line-height: 1.6;
67 scroll-behavior: smooth;
68 }
69 .ears {
70 display: none;
71 }
72
73 /* headings */
74 #title, h1, h2, h3, h4, h5, h6 {
75 margin: 1em 0 0.5em;
76 font-weight: bold;
77 line-height: 1.3;
78 }
79 #title {
80 clear: both;
81 border-bottom: 1px solid #ddd;
82 margin: 0 0 0.5em 0;
83 padding: 1em 0 0.5em;
84 }
85 .author {
86 padding-bottom: 4px;
87 }
88 h1 {
89 font-size: 26px;
90 margin: 1em 0;
91 }
92 h2 {
93 font-size: 22px;
94 margin-top: -20px; /* provide offset for in-page anchors */
95 padding-top: 33px;
96 }
97 h3 {
98 font-size: 18px;
99 margin-top: -36px; /* provide offset for in-page anchors */
100 padding-top: 42px;
101 }
102 h4 {
103 font-size: 16px;
104 margin-top: -36px; /* provide offset for in-page anchors */
105 padding-top: 42px;
106 }
107 h5, h6 {
108 font-size: 14px;
109 }
110 #n-copyright-notice {
111 border-bottom: 1px solid #ddd;
112 padding-bottom: 1em;
113 margin-bottom: 1em;
114 }
115 /* general structure */
116 p {
117 padding: 0;
118 margin: 0 0 1em 0;
119 text-align: left;
120 }
121 div, span {
122 position: relative;
123 }
124 div {
125 margin: 0;
126 }
127 .alignRight.art-text {
128 background-color: #f9f9f9;
129 border: 1px solid #eee;
130 border-radius: 3px;
131 padding: 1em 1em 0;
132 margin-bottom: 1.5em;
133 }
134 .alignRight.art-text pre {
135 padding: 0;
136 }
137 .alignRight {
138 margin: 1em 0;
139 }
140 .alignRight > *:first-child {
141 border: none;
142 margin: 0;
143 float: right;
144 clear: both;
145 }
146 .alignRight > *:nth-child(2) {
147 clear: both;
148 display: block;
149 border: none;
150 }
151 svg {
152 display: block;
153 }
154 .alignCenter.art-text {
155 background-color: #f9f9f9;
156 border: 1px solid #eee;
157 border-radius: 3px;
158 padding: 1em 1em 0;
159 margin-bottom: 1.5em;
160 }
161 .alignCenter.art-text pre {
162 padding: 0;
163 }
164 .alignCenter {
165 margin: 1em 0;
166 }
167 .alignCenter > *:first-child {
168 border: none;
169 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
170 support flexbox yet.
171 */
172 display: table;
173 margin: 0 auto;
174 }
175
176 /* lists */
177 ol, ul {
178 padding: 0;
179 margin: 0 0 1em 2em;
180 }
181 ol ol, ul ul, ol ul, ul ol {
182 margin-left: 1em;
183 }
184 li {
185 margin: 0 0 0.25em 0;
186 }
187 .ulCompact li {
188 margin: 0;
189 }
190 ul.empty, .ulEmpty {
191 list-style-type: none;
192 }
193 ul.empty li, .ulEmpty li {
194 margin-top: 0.5em;
195 }
196 ul.compact, .ulCompact,
197 ol.compact, .olCompact {
198 line-height: 100%;
199 margin: 0 0 0 2em;
200 }
201
202 /* definition lists */
203 dl {
204 }
205 dl > dt {
206 float: left;
207 margin-right: 1em;
208 }
209 /*
210 dl.nohang > dt {
211 float: none;
212 }
213 */
214 dl > dd {
215 margin-bottom: .8em;
216 min-height: 1.3em;
217 }
218 dl.compact > dd, .dlCompact > dd {
219 margin-bottom: 0em;
220 }
221 dl > dd > dl {
222 margin-top: 0.5em;
223 margin-bottom: 0em;
224 }
225
226 /* links */
227 a {
228 text-decoration: none;
229 }
230 a[href] {
231 color: #22e; /* Arlen: WCAG 2019 */
232 }
233 a[href]:hover {
234 background-color: #f2f2f2;
235 }
236 figcaption a[href],
237 a[href].selfRef {
238 color: #222;
239 }
240 /* XXX probably not this:
241 a.selfRef:hover {
242 background-color: transparent;
243 cursor: default;
244 } */
245
246 /* Figures */
247 tt, code, pre, code {
248 background-color: #f9f9f9;
249 font-family: 'Roboto Mono', monospace;
250 }
251 pre {
252 border: 1px solid #eee;
253 margin: 0;
254 padding: 1em;
255 }
256 img {
257 max-width: 100%;
258 }
259 figure {
260 margin: 0;
261 }
262 figure blockquote {
263 margin: 0.8em 0.4em 0.4em;
264 }
265 figcaption {
266 font-style: italic;
267 margin: 0 0 1em 0;
268 }
269 @media screen {
270 pre {
271 overflow-x: auto;
272 max-width: 100%;
273 max-width: calc(100% - 22px);
274 }
275 }
276
277 /* aside, blockquote */
278 aside, blockquote {
279 margin-left: 0;
280 padding: 1.2em 2em;
281 }
282 blockquote {
283 background-color: #f9f9f9;
284 color: #111; /* Arlen: WCAG 2019 */
285 border: 1px solid #ddd;
286 border-radius: 3px;
287 margin: 1em 0;
288 }
289 cite {
290 display: block;
291 text-align: right;
292 font-style: italic;
293 }
294
295 /* tables */
296 table {
297 width: 100%;
298 margin: 0 0 1em;
299 border-collapse: collapse;
300 border: 1px solid #eee;
301 }
302 th, td {
303 text-align: left;
304 vertical-align: top;
305 padding: 0.5em 0.75em;
306 }
307 th {
308 text-align: left;
309 background-color: #e9e9e9;
310 }
311 tr:nth-child(2n+1) > td {
312 background-color: #f5f5f5;
313 }
314 table caption {
315 font-style: italic;
316 margin: 0;
317 padding: 0;
318 text-align: left;
319 }
320 table p {
321 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
322 be allowed within tables more generally, it would be far better to select on a class. */
323 margin: 0;
324 }
325
326 /* pilcrow */
327 a.pilcrow {
328 color: #666; /* Arlen: AHDJ 2019 */
329 text-decoration: none;
330 visibility: hidden;
331 user-select: none;
332 -ms-user-select: none;
333 -o-user-select:none;
334 -moz-user-select: none;
335 -khtml-user-select: none;
336 -webkit-user-select: none;
337 -webkit-touch-callout: none;
338 }
339 @media screen {
340 aside:hover > a.pilcrow,
341 p:hover > a.pilcrow,
342 blockquote:hover > a.pilcrow,
343 div:hover > a.pilcrow,
344 li:hover > a.pilcrow,
345 pre:hover > a.pilcrow {
346 visibility: visible;
347 }
348 a.pilcrow:hover {
349 background-color: transparent;
350 }
351 }
352
353 /* misc */
354 hr {
355 border: 0;
356 border-top: 1px solid #eee;
357 }
358 .bcp14 {
359 font-variant: small-caps;
360 }
361
362 .role {
363 font-variant: all-small-caps;
364 }
365
366 /* info block */
367 #identifiers {
368 margin: 0;
369 font-size: 0.9em;
370 }
371 #identifiers dt {
372 width: 3em;
373 clear: left;
374 }
375 #identifiers dd {
376 float: left;
377 margin-bottom: 0;
378 }
379 #identifiers .authors .author {
380 display: inline-block;
381 margin-right: 1.5em;
382 }
383 #identifiers .authors .org {
384 font-style: italic;
385 }
386
387 /* The prepared/rendered info at the very bottom of the page */
388 .docInfo {
389 color: #666; /* Arlen: WCAG 2019 */
390 font-size: 0.9em;
391 font-style: italic;
392 margin-top: 2em;
393 }
394 .docInfo .prepared {
395 float: left;
396 }
397 .docInfo .prepared {
398 float: right;
399 }
400
401 /* table of contents */
402 #toc {
403 padding: 0.75em 0 2em 0;
404 margin-bottom: 1em;
405 }
406 nav.toc ul {
407 margin: 0 0.5em 0 0;
408 padding: 0;
409 list-style: none;
410 }
411 nav.toc li {
412 line-height: 1.3em;
413 margin: 0.75em 0;
414 padding-left: 1.2em;
415 text-indent: -1.2em;
416 }
417 /* references */
418 .references dt {
419 text-align: right;
420 font-weight: bold;
421 min-width: 7em;
422 }
423 .references dd {
424 margin-left: 8em;
425 overflow: auto;
426 }
427
428 .refInstance {
429 margin-bottom: 1.25em;
430 }
431
432 .references .ascii {
433 margin-bottom: 0.25em;
434 }
435
436 /* index */
437 .index ul {
438 margin: 0 0 0 1em;
439 padding: 0;
440 list-style: none;
441 }
442 .index ul ul {
443 margin: 0;
444 }
445 .index li {
446 margin: 0;
447 text-indent: -2em;
448 padding-left: 2em;
449 padding-bottom: 5px;
450 }
451 .indexIndex {
452 margin: 0.5em 0 1em;
453 }
454 .index a {
455 font-weight: 700;
456 }
457 /* make the index two-column on all but the smallest screens */
458 @media (min-width: 600px) {
459 .index ul {
460 -moz-column-count: 2;
461 -moz-column-gap: 20px;
462 }
463 .index ul ul {
464 -moz-column-count: 1;
465 -moz-column-gap: 0;
466 }
467 }
468
469 /* authors */
470 address.vcard {
471 font-style: normal;
472 margin: 1em 0;
473 }
474
475 address.vcard .nameRole {
476 font-weight: 700;
477 margin-left: 0;
478 }
479 address.vcard .label {
480 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
481 margin: 0.5em 0;
482 }
483 address.vcard .type {
484 display: none;
485 }
486 .alternative-contact {
487 margin: 1.5em 0 1em;
488 }
489 hr.addr {
490 border-top: 1px dashed;
491 margin: 0;
492 color: #ddd;
493 max-width: calc(100% - 16px);
494 }
495
496 /* temporary notes */
497 .rfcEditorRemove::before {
498 position: absolute;
499 top: 0.2em;
500 right: 0.2em;
501 padding: 0.2em;
502 content: "The RFC Editor will remove this note";
503 color: #9e2a00; /* Arlen: WCAG 2019 */
504 background-color: #ffd; /* Arlen: WCAG 2019 */
505 }
506 .rfcEditorRemove {
507 position: relative;
508 padding-top: 1.8em;
509 background-color: #ffd; /* Arlen: WCAG 2019 */
510 border-radius: 3px;
511 }
512 .cref {
513 background-color: #ffd; /* Arlen: WCAG 2019 */
514 padding: 2px 4px;
515 }
516 .crefSource {
517 font-style: italic;
518 }
519 /* alternative layout for smaller screens */
520 @media screen and (max-width: 1023px) {
521 body {
522 padding-top: 2em;
523 }
524 #title {
525 padding: 1em 0;
526 }
527 h1 {
528 font-size: 24px;
529 }
530 h2 {
531 font-size: 20px;
532 margin-top: -18px; /* provide offset for in-page anchors */
533 padding-top: 38px;
534 }
535 #identifiers dd {
536 max-width: 60%;
537 }
538 #toc {
539 position: fixed;
540 z-index: 2;
541 top: 0;
542 right: 0;
543 padding: 0;
544 margin: 0;
545 background-color: inherit;
546 border-bottom: 1px solid #ccc;
547 }
548 #toc h2 {
549 margin: -1px 0 0 0;
550 padding: 4px 0 4px 6px;
551 padding-right: 1em;
552 min-width: 190px;
553 font-size: 1.1em;
554 text-align: right;
555 background-color: #444;
556 color: white;
557 cursor: pointer;
558 }
559 #toc h2::before { /* css hamburger */
560 float: right;
561 position: relative;
562 width: 1em;
563 height: 1px;
564 left: -164px;
565 margin: 6px 0 0 0;
566 background: white none repeat scroll 0 0;
567 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
568 content: "";
569 }
570 #toc nav {
571 display: none;
572 padding: 0.5em 1em 1em;
573 overflow: auto;
574 height: calc(100vh - 48px);
575 border-left: 1px solid #ddd;
576 }
577 }
578
579 /* alternative layout for wide screens */
580 @media screen and (min-width: 1024px) {
581 body {
582 max-width: 724px;
583 margin: 42px auto;
584 padding-left: 1.5em;
585 padding-right: 29em;
586 }
587 #toc {
588 position: fixed;
589 top: 42px;
590 right: 42px;
591 width: 25%;
592 margin: 0;
593 padding: 0 1em;
594 z-index: 1;
595 }
596 #toc h2 {
597 border-top: none;
598 border-bottom: 1px solid #ddd;
599 font-size: 1em;
600 font-weight: normal;
601 margin: 0;
602 padding: 0.25em 1em 1em 0;
603 }
604 #toc nav {
605 display: block;
606 height: calc(90vh - 84px);
607 bottom: 0;
608 padding: 0.5em 0 0;
609 overflow: auto;
610 }
611 img { /* future proofing */
612 max-width: 100%;
613 height: auto;
614 }
615 }
616
617 /* pagination */
618 @media print {
619 body {
620
621 width: 100%;
622 }
623 p {
624 orphans: 3;
625 widows: 3;
626 }
627 #n-copyright-notice {
628 border-bottom: none;
629 }
630 #toc, #n-introduction {
631 page-break-before: always;
632 }
633 #toc {
634 border-top: none;
635 padding-top: 0;
636 }
637 figure, pre {
638 page-break-inside: avoid;
639 }
640 figure {
641 overflow: scroll;
642 }
643 h1, h2, h3, h4, h5, h6 {
644 page-break-after: avoid;
645 }
646 h2+*, h3+*, h4+*, h5+*, h6+* {
647 page-break-before: avoid;
648 }
649 pre {
650 white-space: pre-wrap;
651 word-wrap: break-word;
652 font-size: 10pt;
653 }
654 table {
655 border: 1px solid #ddd;
656 }
657 td {
658 border-top: 1px solid #ddd;
659 }
660 }
661
662 /* This is commented out here, as the string-set: doesn't
663 pass W3C validation currently */
664 /*
665 .ears thead .left {
666 string-set: ears-top-left content();
667 }
668
669 .ears thead .center {
670 string-set: ears-top-center content();
671 }
672
673 .ears thead .right {
674 string-set: ears-top-right content();
675 }
676
677 .ears tfoot .left {
678 string-set: ears-bottom-left content();
679 }
680
681 .ears tfoot .center {
682 string-set: ears-bottom-center content();
683 }
684
685 .ears tfoot .right {
686 string-set: ears-bottom-right content();
687 }
688 */
689
690 @page :first {
691 padding-top: 0;
692 @top-left {
693 content: normal;
694 border: none;
695 }
696 @top-center {
697 content: normal;
698 border: none;
699 }
700 @top-right {
701 content: normal;
702 border: none;
703 }
704 }
705
706 @page {
707 size: A4;
708 margin-bottom: 45mm;
709 padding-top: 20px;
710 /* The follwing is commented out here, but set appropriately by in code, as
711 the content depends on the document */
712 /*
713 @top-left {
714 content: 'Internet-Draft';
715 vertical-align: bottom;
716 border-bottom: solid 1px #ccc;
717 }
718 @top-left {
719 content: string(ears-top-left);
720 vertical-align: bottom;
721 border-bottom: solid 1px #ccc;
722 }
723 @top-center {
724 content: string(ears-top-center);
725 vertical-align: bottom;
726 border-bottom: solid 1px #ccc;
727 }
728 @top-right {
729 content: string(ears-top-right);
730 vertical-align: bottom;
731 border-bottom: solid 1px #ccc;
732 }
733 @bottom-left {
734 content: string(ears-bottom-left);
735 vertical-align: top;
736 border-top: solid 1px #ccc;
737 }
738 @bottom-center {
739 content: string(ears-bottom-center);
740 vertical-align: top;
741 border-top: solid 1px #ccc;
742 }
743 @bottom-right {
744 content: '[Page ' counter(page) ']';
745 vertical-align: top;
746 border-top: solid 1px #ccc;
747 }
748 */
749
750 }
751
752 /* Changes introduced to fix issues found during implementation */
753 /* Make sure links are clickable even if overlapped by following H* */
754 a {
755 z-index: 2;
756 }
757 /* Separate body from document info even without intervening H1 */
758 section {
759 clear: both;
760 }
761
762
763 /* Top align author divs, to avoid names without organization dropping level with org names */
764 .author {
765 vertical-align: top;
766 }
767
768 /* Leave room in document info to show Internet-Draft on one line */
769 #identifiers dt {
770 width: 8em;
771 }
772
773 /* Don't waste quite as much whitespace between label and value in doc info */
774 #identifiers dd {
775 margin-left: 1em;
776 }
777
778 /* Give floating toc a background color (needed when it's a div inside section */
779 #toc {
780 background-color: white;
781 }
782
783 /* Make the collapsed ToC header render white on gray also when it's a link */
784 @media screen and (max-width: 1023px) {
785 #toc h2 a,
786 #toc h2 a:link,
787 #toc h2 a:focus,
788 #toc h2 a:hover,
789 #toc a.toplink,
790 #toc a.toplink:hover {
791 color: white;
792 background-color: #444;
793 text-decoration: none;
794 }
795 }
796
797 /* Give the bottom of the ToC some whitespace */
798 @media screen and (min-width: 1024px) {
799 #toc {
800 padding: 0 0 1em 1em;
801 }
802 }
803
804 /* Style section numbers with more space between number and title */
805 .section-number {
806 padding-right: 0.5em;
807 }
808
809 /* prevent monospace from becoming overly large */
810 tt, code, pre, code {
811 font-size: 95%;
812 }
813
814 /* Fix the height/width aspect for ascii art*/
815 pre.sourcecode,
816 .art-text pre {
817 line-height: 1.12;
818 }
819
820
821 /* Add styling for a link in the ToC that points to the top of the document */
822 a.toplink {
823 float: right;
824 margin-right: 0.5em;
825 }
826
827 /* Fix the dl styling to match the RFC 7992 attributes */
828 dl > dt,
829 dl.dlParallel > dt {
830 float: left;
831 margin-right: 1em;
832 }
833 dl.dlNewline > dt {
834 float: none;
835 }
836
837 /* Provide styling for table cell text alignment */
838 table td.text-left,
839 table th.text-left {
840 text-align: left;
841 }
842 table td.text-center,
843 table th.text-center {
844 text-align: center;
845 }
846 table td.text-right,
847 table th.text-right {
848 text-align: right;
849 }
850
851 /* Make the alternative author contact informatio look less like just another
852 author, and group it closer with the primary author contact information */
853 .alternative-contact {
854 margin: 0.5em 0 0.25em 0;
855 }
856 address .non-ascii {
857 margin: 0 0 0 2em;
858 }
859
860 /* With it being possible to set tables with alignment
861 left, center, and right, { width: 100%; } does not make sense */
862 table {
863 width: auto;
864 }
865
866 /* Avoid reference text that sits in a block with very wide left margin,
867 because of a long floating dt label.*/
868 .references dd {
869 overflow: visible;
870 }
871
872 /* Control caption placement */
873 caption {
874 caption-side: bottom;
875 }
876
877 /* Limit the width of the author address vcard, so names in right-to-left
878 script don't end up on the other side of the page. */
879
880 address.vcard {
881 max-width: 30em;
882 margin-right: auto;
883 }
884
885 /* For address alignment dependent on LTR or RTL scripts */
886 address div.left {
887 text-align: left;
888 }
889 address div.right {
890 text-align: right;
891 }
892
893 /* Provide table alignment support. We can't use the alignX classes above
894 since they do unwanted things with caption and other styling. */
895 table.right {
896 margin-left: auto;
897 margin-right: 0;
898 }
899 table.center {
900 margin-left: auto;
901 margin-right: auto;
902 }
903 table.left {
904 margin-left: 0;
905 margin-right: auto;
906 }
907
908 /* Give the table caption label the same styling as the figcaption */
909 caption a[href] {
910 color: #222;
911 }
912
913 @media print {
914 .toplink {
915 display: none;
916 }
917
918 /* avoid overwriting the top border line with the ToC header */
919 #toc {
920 padding-top: 1px;
921 }
922
923 /* Avoid page breaks inside dl and author address entries */
924 .vcard {
925 page-break-inside: avoid;
926 }
927
928 }
929 /* Avoid wrapping of URLs in references */
930 @media screen {
931 .references a {
932 white-space: nowrap;
933 }
934 }
935 /* Tweak the bcp14 keyword presentation */
936 .bcp14 {
937 font-variant: small-caps;
938 font-weight: bold;
939 font-size: 0.9em;
940 }
941 /* Tweak the invisible space above H* in order not to overlay links in text above */
942 h2 {
943 margin-top: -18px; /* provide offset for in-page anchors */
944 padding-top: 31px;
945 }
946 h3 {
947 margin-top: -18px; /* provide offset for in-page anchors */
948 padding-top: 24px;
949 }
950 h4 {
951 margin-top: -18px; /* provide offset for in-page anchors */
952 padding-top: 24px;
953 }
954 /* Float artwork pilcrow to the right */
955 @media screen {
956 .artwork a.pilcrow {
957 display: block;
958 line-height: 0.7;
959 margin-top: 0.15em;
960 }
961 }
962 /* Make pilcrows on dd visible */
963 @media screen {
964 dd:hover > a.pilcrow {
965 visibility: visible;
966 }
967 }
968 /* Make the placement of figcaption match that of a table's caption
969 by removing the figure's added bottom margin */
970 .alignLeft.art-text,
971 .alignCenter.art-text,
972 .alignRight.art-text {
973 margin-bottom: 0;
974 }
975 .alignLeft,
976 .alignCenter,
977 .alignRight {
978 margin: 1em 0 0 0;
979 }
980 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
981 possibly even requiring a new line */
982 @media print {
983 a.pilcrow {
984 display: none;
985 }
986 }
987 /* Styling for the external metadata */
988 div#external-metadata {
989 background-color: #eee;
990 padding: 0.5em;
991 margin-bottom: 0.5em;
992 display: none;
993 }
994 div#internal-metadata {
995 padding: 0.5em; /* to match the external-metadata padding */
996 }
997 /* Styling for title RFC Number */
998 h1#rfcnum {
999 clear: both;
1000 margin: 0 0 -1em;
1001 padding: 1em 0 0 0;
1002 }
1003 /* Make .olPercent look the same as <ol><li> */
1004 dl.olPercent > dd {
1005 margin: 0 0 0.25em 0;
1006 min-height: initial;
1007 }
1008 /* Give aside some styling to set it apart */
1009 aside {
1010 border-left: 1px solid #ddd;
1011 margin: 1em 0 1em 2em;
1012 padding: 0.2em 2em;
1013 }
1014 aside > dl,
1015 aside > ol,
1016 aside > ul,
1017 aside > table,
1018 aside > p {
1019 margin-bottom: 0.5em;
1020 }
1021 /* Additional page break settings */
1022 @media print {
1023 figcaption, table caption {
1024 page-break-before: avoid;
1025 }
1026 }
1027 /* Font size adjustments for print */
1028 @media print {
1029 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1030 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1031 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1032 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1033 h4 { font-size: 1em; padding-top: 1.5em; }
1034 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1035 }
1036 /* Sourcecode margin in print, when there's no pilcrow */
1037 @media print {
1038 .artwork,
1039 .sourcecode {
1040 margin-bottom: 1em;
1041 }
1042 }
1043 /*
1044 The margin-left: 0 on <dd> removes all distinction
1045 between levels from nested <dl>s. Undo that.
1046 */
1047 dl.olPercent > dd,
1048 dd {
1049 margin-left: revert;
1050 }
1051 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1052 table {
1053 min-width: 20em;
1054 }
1055 /* ol type a */
1056 ol.type-a { list-style-type: lower-alpha; }
1057 ol.type-A { list-style-type: upper-alpha; }
1058 ol.type-i { list-style-type: lower-roman; }
1059 ol.type-I { list-style-type: lower-roman; }
1060 /* Apply the print table and row borders in general, on request from the RPC,
1061 and increase the contrast between border and odd row background sligthtly */
1062 table {
1063 border: 1px solid #ddd;
1064 }
1065 td {
1066 border-top: 1px solid #ddd;
1067 }
1068 tr:nth-child(2n+1) > td {
1069 background-color: #f8f8f8;
1070 }
1071 /* Use style rules to govern display of the TOC. */
1072 @media screen and (max-width: 1023px) {
1073 #toc nav { display: none; }
1074 #toc.active nav { display: block; }
1075 }
1076 </style>
1077 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1078 <link href="https://dx.doi.org/10.17487/rfc8739" rel="alternate">
1079 <link href="urn:issn:2070-1721" rel="alternate">
1080 <link href="https://datatracker.ietf.org/doc/draft-ietf-acme-star-11" rel="prev">
1081 </head>
1082 <body>
1083 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1084 <table class="ears">
1085 <thead><tr>
1086 <td class="left">RFC 8739</td>
1087 <td class="center">Support for ACME STAR</td>
1088 <td class="right">March 2020</td>
1089 </tr></thead>
1090 <tfoot><tr>
1091 <td class="left">Sheffer, et al.</td>
1092 <td class="center">Standards Track</td>
1093 <td class="right">[Page]</td>
1094 </tr></tfoot>
1095 </table>
1096 <div id="external-metadata" class="document-information"></div>
1097 <div id="internal-metadata" class="document-information">
1098 <dl id="identifiers">
1099 <dt class="label-stream">Stream:</dt>
1100 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1101 <dt class="label-rfc">RFC:</dt>
1102 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8739" class="eref">8739</a></dd>
1103 <dt class="label-category">Category:</dt>
1104 <dd class="category">Standards Track</dd>
1105 <dt class="label-published">Published:</dt>
1106 <dd class="published">
1107 <time datetime="2020-03" class="published">March 2020</time>
1108 </dd>
1109 <dt class="label-issn">ISSN:</dt>
1110 <dd class="issn">2070-1721</dd>
1111 <dt class="label-authors">Authors:</dt>
1112 <dd class="authors">
1113 <div class="author">
1114 <div class="author-name">Y. Sheffer</div>
1115 <div class="org">Intuit</div>
1116 </div>
1117 <div class="author">
1118 <div class="author-name">D. Lopez</div>
1119 <div class="org">Telefonica I+D</div>
1120 </div>
1121 <div class="author">
1122 <div class="author-name">O. Gonzalez de Dios</div>
1123 <div class="org">Telefonica I+D</div>
1124 </div>
1125 <div class="author">
1126 <div class="author-name">A. Pastor Perales</div>
1127 <div class="org">Telefonica I+D</div>
1128 </div>
1129 <div class="author">
1130 <div class="author-name">T. Fossati</div>
1131 <div class="org">ARM</div>
1132 </div>
1133 </dd>
1134 </dl>
1135 </div>
1136 <h1 id="rfcnum">RFC 8739</h1>
1137 <h1 id="title">Support for Short-Term, Automatically Renewed (STAR) Certificates in the Automated Certificate Management Environment (ACME)</h1>
1138 <section id="section-abstract">
1139 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1140 <p id="section-abstract-1">Public key certificates need to be revoked when they are compromised,
1141 that is, when the associated private key is exposed to an unauthorized
1142 entity. However, the revocation process is often unreliable. An
1143 alternative to revocation is issuing a sequence of certificates, each
1144 with a short validity period, and terminating the sequence upon
1145 compromise. This memo proposes an Automated Certificate Management
1146 Environment (ACME) extension to enable the issuance of Short-Term,
1147 Automatically Renewed (STAR) X.509 certificates.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1148 </section>
1149 <div id="status-of-memo">
1150 <section id="section-boilerplate.1">
1151 <h2 id="name-status-of-this-memo">
1152 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1153 </h2>
1154 <p id="section-boilerplate.1-1">
1155 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1156 <p id="section-boilerplate.1-2">
1157 This document is a product of the Internet Engineering Task Force
1158 (IETF). It represents the consensus of the IETF community. It has
1159 received public review and has been approved for publication by
1160 the Internet Engineering Steering Group (IESG). Further
1161 information on Internet Standards is available in Section 2 of
1162 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1163 <p id="section-boilerplate.1-3">
1164 Information about the current status of this document, any
1165 errata, and how to provide feedback on it may be obtained at
1166 <span><a href="https://www.rfc-editor.org/info/rfc8739">https://www.rfc-editor.org/info/rfc8739</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1167 </section>
1168 </div>
1169 <div id="copyright">
1170 <section id="section-boilerplate.2">
1171 <h2 id="name-copyright-notice">
1172 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1173 </h2>
1174 <p id="section-boilerplate.2-1">
1175 Copyright (c) 2020 IETF Trust and the persons identified as the
1176 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1177 <p id="section-boilerplate.2-2">
1178 This document is subject to BCP 78 and the IETF Trust's Legal
1179 Provisions Relating to IETF Documents
1180 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1181 publication of this document. Please review these documents
1182 carefully, as they describe your rights and restrictions with
1183 respect to this document. Code Components extracted from this
1184 document must include Simplified BSD License text as described in
1185 Section 4.e of the Trust Legal Provisions and are provided without
1186 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1187 </section>
1188 </div>
1189 <div id="toc">
1190 <section id="section-toc.1">
1191 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1192 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1193 </h2>
1194 <nav class="toc"><ul class="toc ulEmpty">
1195 <li class="toc ulEmpty" id="section-toc.1-1.1">
1196 <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>
1197 <ul class="toc ulEmpty">
1198 <li class="toc ulEmpty" id="section-toc.1-1.1.2.1">
1199 <p id="section-toc.1-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-name-delegation-use-case" class="xref">Name Delegation Use Case</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
1200 </li>
1201 <li class="toc ulEmpty" id="section-toc.1-1.1.2.2">
1202 <p id="section-toc.1-1.1.2.2.1"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.1.2.2.1" class="pilcrow">¶</a></p>
1203 </li>
1204 <li class="toc ulEmpty" id="section-toc.1-1.1.2.3">
1205 <p id="section-toc.1-1.1.2.3.1"><a href="#section-1.3" class="xref">1.3</a>.  <a href="#name-conventions-used-in-this-do" class="xref">Conventions Used in This Document</a><a href="#section-toc.1-1.1.2.3.1" class="pilcrow">¶</a></p>
1206 </li>
1207 </ul>
1208 </li>
1209 <li class="toc ulEmpty" id="section-toc.1-1.2">
1210 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-protocol-flow" class="xref">Protocol Flow</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1211 <ul class="toc ulEmpty">
1212 <li class="toc ulEmpty" id="section-toc.1-1.2.2.1">
1213 <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-bootstrap" class="xref">Bootstrap</a><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p>
1214 </li>
1215 <li class="toc ulEmpty" id="section-toc.1-1.2.2.2">
1216 <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-auto-renewal" class="xref">Auto Renewal</a><a href="#section-toc.1-1.2.2.2.1" class="pilcrow">¶</a></p>
1217 </li>
1218 <li class="toc ulEmpty" id="section-toc.1-1.2.2.3">
1219 <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-termination" class="xref">Termination</a><a href="#section-toc.1-1.2.2.3.1" class="pilcrow">¶</a></p>
1220 </li>
1221 </ul>
1222 </li>
1223 <li class="toc ulEmpty" id="section-toc.1-1.3">
1224 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-protocol-details" class="xref">Protocol Details</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1225 <ul class="toc ulEmpty">
1226 <li class="toc ulEmpty" id="section-toc.1-1.3.2.1">
1227 <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-acme-extensions" class="xref">ACME Extensions</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
1228 <ul class="toc ulEmpty">
1229 <li class="toc ulEmpty" id="section-toc.1-1.3.2.1.2.1">
1230 <p id="section-toc.1-1.3.2.1.2.1.1"><a href="#section-3.1.1" class="xref">3.1.1</a>.  <a href="#name-extending-the-order-resourc" class="xref">Extending the Order Resource</a><a href="#section-toc.1-1.3.2.1.2.1.1" class="pilcrow">¶</a></p>
1231 </li>
1232 <li class="toc ulEmpty" id="section-toc.1-1.3.2.1.2.2">
1233 <p id="section-toc.1-1.3.2.1.2.2.1"><a href="#section-3.1.2" class="xref">3.1.2</a>.  <a href="#name-canceling-an-auto-renewal-o" class="xref">Canceling an Auto-renewal Order</a><a href="#section-toc.1-1.3.2.1.2.2.1" class="pilcrow">¶</a></p>
1234 </li>
1235 </ul>
1236 </li>
1237 <li class="toc ulEmpty" id="section-toc.1-1.3.2.2">
1238 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-capability-discovery" class="xref">Capability Discovery</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
1239 </li>
1240 <li class="toc ulEmpty" id="section-toc.1-1.3.2.3">
1241 <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-fetching-the-certificates" class="xref">Fetching the Certificates</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
1242 </li>
1243 <li class="toc ulEmpty" id="section-toc.1-1.3.2.4">
1244 <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-negotiating-an-unauthentica" class="xref">Negotiating an Unauthenticated GET</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p>
1245 </li>
1246 <li class="toc ulEmpty" id="section-toc.1-1.3.2.5">
1247 <p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-computing-notbefore-and-not" class="xref">Computing notBefore and notAfter of STAR Certificates</a><a href="#section-toc.1-1.3.2.5.1" class="pilcrow">¶</a></p>
1248 <ul class="toc ulEmpty">
1249 <li class="toc ulEmpty" id="section-toc.1-1.3.2.5.2.1">
1250 <p id="section-toc.1-1.3.2.5.2.1.1"><a href="#section-3.5.1" class="xref">3.5.1</a>.  <a href="#name-example" class="xref">Example</a><a href="#section-toc.1-1.3.2.5.2.1.1" class="pilcrow">¶</a></p>
1251 </li>
1252 </ul>
1253 </li>
1254 </ul>
1255 </li>
1256 <li class="toc ulEmpty" id="section-toc.1-1.4">
1257 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-operational-considerations" class="xref">Operational Considerations</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1258 <ul class="toc ulEmpty">
1259 <li class="toc ulEmpty" id="section-toc.1-1.4.2.1">
1260 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-the-meaning-of-short-term-a" class="xref">The Meaning of "Short Term" and the Impact of Skewed Clocks</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
1261 </li>
1262 <li class="toc ulEmpty" id="section-toc.1-1.4.2.2">
1263 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-impact-on-certificate-trans" class="xref">Impact on Certificate Transparency (CT) Logs</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p>
1264 </li>
1265 <li class="toc ulEmpty" id="section-toc.1-1.4.2.3">
1266 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-http-caching-and-dependabil" class="xref">HTTP Caching and Dependability</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p>
1267 </li>
1268 </ul>
1269 </li>
1270 <li class="toc ulEmpty" id="section-toc.1-1.5">
1271 <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><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1272 <ul class="toc ulEmpty">
1273 <li class="toc ulEmpty" id="section-toc.1-1.5.2.1">
1274 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-new-registries" class="xref">New Registries</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
1275 </li>
1276 <li class="toc ulEmpty" id="section-toc.1-1.5.2.2">
1277 <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-new-error-types" class="xref">New Error Types</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
1278 </li>
1279 <li class="toc ulEmpty" id="section-toc.1-1.5.2.3">
1280 <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-new-fields-in-order-objects" class="xref">New Fields in Order Objects</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p>
1281 </li>
1282 <li class="toc ulEmpty" id="section-toc.1-1.5.2.4">
1283 <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-fields-in-the-auto-renewal-" class="xref">Fields in the "auto-renewal" Object within an Order Object</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p>
1284 </li>
1285 <li class="toc ulEmpty" id="section-toc.1-1.5.2.5">
1286 <p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>.  <a href="#name-new-fields-in-the-meta-obje" class="xref">New Fields in the "meta" Object within a Directory Object</a><a href="#section-toc.1-1.5.2.5.1" class="pilcrow">¶</a></p>
1287 </li>
1288 <li class="toc ulEmpty" id="section-toc.1-1.5.2.6">
1289 <p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>.  <a href="#name-fields-in-the-auto-renewal-o" class="xref">Fields in the "auto-renewal" Object within a Directory Metadata Object</a><a href="#section-toc.1-1.5.2.6.1" class="pilcrow">¶</a></p>
1290 </li>
1291 <li class="toc ulEmpty" id="section-toc.1-1.5.2.7">
1292 <p id="section-toc.1-1.5.2.7.1"><a href="#section-5.7" class="xref">5.7</a>.  <a href="#name-cert-not-before-and-cert-no" class="xref">Cert-Not-Before and Cert-Not-After HTTP Headers</a><a href="#section-toc.1-1.5.2.7.1" class="pilcrow">¶</a></p>
1293 </li>
1294 </ul>
1295 </li>
1296 <li class="toc ulEmpty" id="section-toc.1-1.6">
1297 <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><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1298 <ul class="toc ulEmpty">
1299 <li class="toc ulEmpty" id="section-toc.1-1.6.2.1">
1300 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-no-revocation" class="xref">No Revocation</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
1301 </li>
1302 <li class="toc ulEmpty" id="section-toc.1-1.6.2.2">
1303 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-denial-of-service-considera" class="xref">Denial-of-Service Considerations</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p>
1304 </li>
1305 <li class="toc ulEmpty" id="section-toc.1-1.6.2.3">
1306 <p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>.  <a href="#name-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.6.2.3.1" class="pilcrow">¶</a></p>
1307 </li>
1308 </ul>
1309 </li>
1310 <li class="toc ulEmpty" id="section-toc.1-1.7">
1311 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1312 <ul class="toc ulEmpty">
1313 <li class="toc ulEmpty" id="section-toc.1-1.7.2.1">
1314 <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><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
1315 </li>
1316 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2">
1317 <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><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
1318 </li>
1319 </ul>
1320 </li>
1321 <li class="toc ulEmpty" id="section-toc.1-1.8">
1322 <p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1323 </li>
1324 <li class="toc ulEmpty" id="section-toc.1-1.9">
1325 <p id="section-toc.1-1.9.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.9.1" class="pilcrow">¶</a></p>
1326 </li>
1327 </ul>
1328 </nav>
1329 </section>
1330 </div>
1331 <div id="introduction">
1332 <section id="section-1">
1333 <h2 id="name-introduction">
1334 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1335 </h2>
1336 <p id="section-1-1">The ACME protocol <span>[<a href="#RFC8555" class="xref">RFC8555</a>]</span> automates
1337 the process of issuing a certificate to a named entity (an Identifier
1338 Owner or IdO). Typically, but not always, the identifier is a domain
1339 name.<a href="#section-1-1" class="pilcrow">¶</a></p>
1340 <p id="section-1-2">If the IdO wishes to obtain a string of short-term certificates
1341 originating from the same private key (see <span>[<a href="#TOPALOVIC" class="xref">TOPALOVIC</a>]</span> about why using short-lived certificates might be
1342 preferable to explicit revocation), she must go through the whole ACME
1343 protocol each time a new short-term certificate is needed, e.g., every
1344 2-3 days. If done this way, the process would involve frequent
1345 interactions between the registration function of the ACME Certification
1346 Authority (CA) and the identity provider infrastructure (e.g., DNS, web
1347 servers), therefore making the issuance of short-term certificates
1348 exceedingly dependent on the reliability of both.<a href="#section-1-2" class="pilcrow">¶</a></p>
1349 <p id="section-1-3">This document presents an extension of the ACME protocol that
1350 optimizes this process by making short-term certificates first-class
1351 objects in the ACME ecosystem. Once the Order for a string of
1352 short-term certificates is accepted, the CA is responsible for
1353 publishing the next certificate at an agreed upon URL before the
1354 previous one expires. The IdO can terminate the automatic renewal
1355 before the negotiated deadline if needed, e.g., on key compromise.<a href="#section-1-3" class="pilcrow">¶</a></p>
1356 <p id="section-1-4">For a more generic treatment of STAR certificates, readers are referred to <span>[<a href="#I-D.nir-saag-star" class="xref">SHORT-TERM-CERTS</a>]</span>.<a href="#section-1-4" class="pilcrow">¶</a></p>
1357 <div id="name-delegation-use-case">
1358 <section id="section-1.1">
1359 <h3 id="name-name-delegation-use-case">
1360 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-name-delegation-use-case" class="section-name selfRef">Name Delegation Use Case</a>
1361 </h3>
1362 <p id="section-1.1-1">The proposed mechanism can be used as a building block of an
1363 efficient name-delegation protocol, for example, one that exists between a
1364 Content Distribution Network (CDN) or a cloud provider and its
1365 customers <span>[<a href="#I-D.ietf-acme-star-delegation" class="xref">STAR-DELEGATION</a>]</span>. At any time, the service customer (i.e., the IdO)
1366 can terminate the delegation by simply instructing the CA to stop the
1367 automatic renewal and letting the currently active certificate expire
1368 shortly thereafter.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1369 <p id="section-1.1-2">Note that in the name delegation use case, the delegated entity needs to access
1370 the auto-renewed certificate without being in possession of the ACME account
1371 key that was used for initiating the STAR issuance. This leads to the optional
1372 use of unauthenticated GET in this protocol (<a href="#certificate-get-nego" class="xref">Section 3.4</a>).<a href="#section-1.1-2" class="pilcrow">¶</a></p>
1373 </section>
1374 </div>
1375 <div id="terminology">
1376 <section id="section-1.2">
1377 <h3 id="name-terminology">
1378 <a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1379 </h3>
1380 <dl class="dlParallel dlCompact" id="section-1.2-1">
1381 <dt id="section-1.2-1.1">IdO</dt>
1382 <dd style="margin-left: 4.0em" id="section-1.2-1.2">
1383 Identifier Owner, the owner of an identifier, e.g., a domain name, a
1384 telephone number, etc.<a href="#section-1.2-1.2" class="pilcrow">¶</a>
1385 </dd>
1386 <dt id="section-1.2-1.3">STAR</dt>
1387 <dd style="margin-left: 4.0em" id="section-1.2-1.4">
1388 Short-Term, Automatically Renewed X.509 certificates.<a href="#section-1.2-1.4" class="pilcrow">¶</a>
1389 </dd>
1390 </dl>
1391 </section>
1392 </div>
1393 <div id="conventions-used-in-this-document">
1394 <section id="section-1.3">
1395 <h3 id="name-conventions-used-in-this-do">
1396 <a href="#section-1.3" class="section-number selfRef">1.3. </a><a href="#name-conventions-used-in-this-do" class="section-name selfRef">Conventions Used in This Document</a>
1397 </h3>
1398 <p id="section-1.3-1">
1399 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>",
1400 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
1401 described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
1402 when, and only when, they appear in all capitals, as shown here.<a href="#section-1.3-1" class="pilcrow">¶</a></p>
1403 </section>
1404 </div>
1405 </section>
1406 </div>
1407 <div id="protocol-flow">
1408 <section id="section-2">
1409 <h2 id="name-protocol-flow">
1410 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-protocol-flow" class="section-name selfRef">Protocol Flow</a>
1411 </h2>
1412 <p id="section-2-1">The following subsections describe the three main phases of the protocol:<a href="#section-2-1" class="pilcrow">¶</a></p>
1413 <ul>
1414 <li id="section-2-2.1">Bootstrap: the IdO asks an ACME CA to create a short-term,
1415 automatically renewed (STAR) certificate (<a href="#proto-bootstrap" class="xref">Section 2.1</a>);<a href="#section-2-2.1" class="pilcrow">¶</a>
1416 </li>
1417 <li id="section-2-2.2">Auto-renewal: the ACME CA periodically reissues the short-term
1418 certificate and posts it to the star-certificate URL (<a href="#proto-auto-renewal" class="xref">Section 2.2</a>);<a href="#section-2-2.2" class="pilcrow">¶</a>
1419 </li>
1420 <li id="section-2-2.3">Termination: the IdO requests the ACME CA to discontinue the
1421 automatic renewal of the certificate (<a href="#proto-termination" class="xref">Section 2.3</a>).<a href="#section-2-2.3" class="pilcrow">¶</a>
1422 </li>
1423 </ul>
1424 <div id="proto-bootstrap">
1425 <section id="section-2.1">
1426 <h3 id="name-bootstrap">
1427 <a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-bootstrap" class="section-name selfRef">Bootstrap</a>
1428 </h3>
1429 <p id="section-2.1-1">The IdO, in its role as an
1430 ACME client, requests the CA to issue a STAR certificate, i.e., one that:<a href="#section-2.1-1" class="pilcrow">¶</a></p>
1431 <ul>
1432 <li id="section-2.1-2.1">Has a short validity, e.g., 24 to 72 hours. Note that the exact definition of "short" depends on the use case;<a href="#section-2.1-2.1" class="pilcrow">¶</a>
1433 </li>
1434 <li id="section-2.1-2.2">Is automatically renewed by the CA for a certain period of time;<a href="#section-2.1-2.2" class="pilcrow">¶</a>
1435 </li>
1436 <li id="section-2.1-2.3">Is downloadable from a (highly available) location.<a href="#section-2.1-2.3" class="pilcrow">¶</a>
1437 </li>
1438 </ul>
1439 <p id="section-2.1-3">Other than that, the ACME protocol flows as usual between IdO and CA.
1440 In particular, IdO is responsible for satisfying the requested ACME challenges until the CA is willing to issue the requested certificate.
1441 Per normal ACME processing, the IdO is given back an Order resource associated with the STAR certificate to be used in subsequent interaction with the CA (e.g., if
1442 the certificate needs to be terminated.)<a href="#section-2.1-3" class="pilcrow">¶</a></p>
1443 <p id="section-2.1-4">The bootstrap phase ends when the ACME CA updates the Order resource to include the URL for the issued STAR certificate.<a href="#section-2.1-4" class="pilcrow">¶</a></p>
1444 </section>
1445 </div>
1446 <div id="proto-auto-renewal">
1447 <section id="section-2.2">
1448 <h3 id="name-auto-renewal">
1449 <a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-auto-renewal" class="section-name selfRef">Auto Renewal</a>
1450 </h3>
1451 <p id="section-2.2-1">The CA issues the initial certificate after the authorization
1452 completes successfully. It then automatically reissues the
1453 certificate using the same Certificate Signing Request (CSR) (and therefore the same identifier and
1454 public key) before the previous one expires and publishes it to the
1455 URL that was returned to the IdO at the end of the bootstrap phase.
1456 The certificate user, which could be either the IdO itself or a
1457 delegated third party as described in <span>[<a href="#I-D.ietf-acme-star-delegation" class="xref">STAR-DELEGATION</a>]</span>, obtains the
1458 certificate (<a href="#fetching-certificates" class="xref">Section 3.3</a>)
1459 and uses it.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
1460 <p id="section-2.2-2">The auto-renewal process (<a href="#figprotorefresh" class="xref">Figure 1</a>) goes on until either:<a href="#section-2.2-2" class="pilcrow">¶</a></p>
1461 <ul>
1462 <li id="section-2.2-3.1">IdO explicitly terminates the automatic renewal (<a href="#proto-termination" class="xref">Section 2.3</a>); or<a href="#section-2.2-3.1" class="pilcrow">¶</a>
1463 </li>
1464 <li id="section-2.2-3.2">Automatic renewal expires.<a href="#section-2.2-3.2" class="pilcrow">¶</a>
1465 </li>
1466 </ul>
1467 <span id="name-auto-renewal-2"></span><div id="figprotorefresh">
1468 <figure id="figure-1">
1469 <div class="artwork art-text alignLeft" id="section-2.2-4.1">
1470 <pre>
1471 Certificate ACME/STAR
1472 User Server
1473 | Retrieve cert | [...]
1474 |----------------------&gt;| |
1475 | +------. /
1476 | | | /
1477 | | Automatic renewal :
1478 | | | \
1479 | |&lt;-----' \
1480 | Retrieve cert | |
1481 |----------------------&gt;| short validity period
1482 | | |
1483 | +------. /
1484 | | | /
1485 | | Automatic renewal :
1486 | | | \
1487 | |&lt;-----' \
1488 | Retrieve cert | |
1489 |----------------------&gt;| short validity period
1490 | | |
1491 | +------. /
1492 | | | /
1493 | | Automatic renewal :
1494 | | | \
1495 | |&lt;-----' \
1496 | | |
1497 | [...] | [...]
1498 </pre>
1499 </div>
1500 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1501 <a href="#name-auto-renewal-2" class="selfRef">Auto-renewal</a>
1502 </figcaption></figure>
1503 </div>
1504 </section>
1505 </div>
1506 <div id="proto-termination">
1507 <section id="section-2.3">
1508 <h3 id="name-termination">
1509 <a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-termination" class="section-name selfRef">Termination</a>
1510 </h3>
1511 <p id="section-2.3-1">The IdO may request early termination of the STAR certificate by
1512 sending a cancellation request to the Order resource as described in
1513 <a href="#protocol-details-canceling" class="xref">Section 3.1.2</a>. After
1514 the CA receives and verifies the request, it shall:<a href="#section-2.3-1" class="pilcrow">¶</a></p>
1515 <ul>
1516 <li id="section-2.3-2.1">Cancel the automatic renewal process for the STAR certificate;<a href="#section-2.3-2.1" class="pilcrow">¶</a>
1517 </li>
1518 <li id="section-2.3-2.2">Change the certificate publication resource to return an error indicating the termination of the issuance;<a href="#section-2.3-2.2" class="pilcrow">¶</a>
1519 </li>
1520 <li id="section-2.3-2.3">Change the status of the Order to "canceled".<a href="#section-2.3-2.3" class="pilcrow">¶</a>
1521 </li>
1522 </ul>
1523 <p id="section-2.3-3">Note that it is not necessary to explicitly revoke the short-term certificate.<a href="#section-2.3-3" class="pilcrow">¶</a></p>
1524 <span id="name-termination-2"></span><div id="figprototerm">
1525 <figure id="figure-2">
1526 <div class="artwork art-text alignLeft" id="section-2.3-4.1">
1527 <pre>
1528 Certificate ACME/STAR
1529 User IdO Server
1530 | | |
1531 | | Cancel Order |
1532 | +----------------------&gt;|
1533 | | +-------.
1534 | | | |
1535 | | | End auto-renewal
1536 | | | Remove cert link
1537 | | | etc.
1538 | | | |
1539 | | Done |&lt;------'
1540 | |&lt;----------------------+
1541 | | |
1542 | |
1543 | Retrieve cert |
1544 +----------------------------------------------&gt;|
1545 | Error: autoRenewalCanceled |
1546 |&lt;----------------------------------------------+
1547 | |
1548 </pre>
1549 </div>
1550 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1551 <a href="#name-termination-2" class="selfRef">Termination</a>
1552 </figcaption></figure>
1553 </div>
1554 </section>
1555 </div>
1556 </section>
1557 </div>
1558 <div id="protocol-details">
1559 <section id="section-3">
1560 <h2 id="name-protocol-details">
1561 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-protocol-details" class="section-name selfRef">Protocol Details</a>
1562 </h2>
1563 <p id="section-3-1">This section describes the protocol details, namely the extensions
1564 to the ACME protocol required to issue STAR certificates.<a href="#section-3-1" class="pilcrow">¶</a></p>
1565 <div id="acme-extensions">
1566 <section id="section-3.1">
1567 <h3 id="name-acme-extensions">
1568 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-acme-extensions" class="section-name selfRef">ACME Extensions</a>
1569 </h3>
1570 <p id="section-3.1-1">This protocol extends the ACME protocol to allow for automatically renewed Orders.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1571 <div id="star-order-ext">
1572 <section id="section-3.1.1">
1573 <h4 id="name-extending-the-order-resourc">
1574 <a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-extending-the-order-resourc" class="section-name selfRef">Extending the Order Resource</a>
1575 </h4>
1576 <p id="section-3.1.1-1">The Order resource is extended with a new "auto-renewal" object
1577 that <span class="bcp14">MUST</span> be present for STAR certificates. The
1578 "auto-renewal" object has the following structure:<a href="#section-3.1.1-1" class="pilcrow">¶</a></p>
1579 <ul>
1580 <li id="section-3.1.1-2.1">start-date (optional, string): The earliest date of validity
1581 of the first certificate issued, in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span> format. When omitted, the start date is as
1582 soon as authorization is complete.<a href="#section-3.1.1-2.1" class="pilcrow">¶</a>
1583 </li>
1584 <li id="section-3.1.1-2.2">end-date (required, string): The latest date of validity of
1585 the last certificate issued, in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span> format.<a href="#section-3.1.1-2.2" class="pilcrow">¶</a>
1586 </li>
1587 <li id="section-3.1.1-2.3">lifetime (required, integer): The maximum validity period of
1588 each STAR certificate, an integer that denotes a number of
1589 seconds. This is a nominal value that does not include any extra
1590 validity time due to server or client adjustment (see below).<a href="#section-3.1.1-2.3" class="pilcrow">¶</a>
1591 </li>
1592 <li id="section-3.1.1-2.4">lifetime-adjust (optional, integer): The amount of "left pad"
1593 added to each STAR certificate, an integer that denotes a number
1594 of seconds. The default is 0. If present, the value of the
1595 notBefore field that would otherwise appear in the STAR
1596 certificates is pre-dated by the specified number of seconds. See
1597 <a href="#operational-cons-clocks" class="xref">Section 4.1</a> for
1598 why a client might want to use this control, and <a href="#computing-effective-cert-lifetime" class="xref">Section 3.5</a> for
1599 how the effective certificate lifetime is computed. The value
1600 reflected by the server, together with the value of the lifetime
1601 attribute, can be used by the client as a hint to configure its
1602 polling timer.<a href="#section-3.1.1-2.4" class="pilcrow">¶</a>
1603 </li>
1604 <li id="section-3.1.1-2.5">allow-certificate-get (optional, boolean): See <a href="#certificate-get-nego" class="xref">Section 3.4</a>.<a href="#section-3.1.1-2.5" class="pilcrow">¶</a>
1605 </li>
1606 </ul>
1607 <p id="section-3.1.1-3">These attributes are included in a POST message when creating the
1608 Order as part of the object encoded as "payload". They are returned
1609 when the Order has been created. The ACME server <span class="bcp14">MAY</span>
1610 adjust them at will according to its local policy (see also <a href="#capability-discovery" class="xref">Section 3.2</a>).<a href="#section-3.1.1-3" class="pilcrow">¶</a></p>
1611 <p id="section-3.1.1-4">The optional notBefore and notAfter fields defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.1.3" class="relref">Section 7.1.3</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> <span class="bcp14">MUST NOT</span> be present in a STAR Order. If they are included, the
1612 server <span class="bcp14">MUST</span> return an error with status code 400 (Bad
1613 Request) and type "malformedRequest".<a href="#section-3.1.1-4" class="pilcrow">¶</a></p>
1614 <p id="section-3.1.1-5"><span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.1.6" class="relref">Section 7.1.6</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>
1615 defines the following values for the Order resource's status:
1616 "pending", "ready", "processing", "valid", and "invalid". In the
1617 case of auto-renewal Orders, the status <span class="bcp14">MUST</span> be
1618 "valid" as long as STAR certificates are being issued. This
1619 document adds a new status value: "canceled" (see <a href="#protocol-details-canceling" class="xref">Section 3.1.2</a>).<a href="#section-3.1.1-5" class="pilcrow">¶</a></p>
1620 <p id="section-3.1.1-6">A STAR certificate is by definition a dynamic resource, i.e., it
1621 refers to an entity that varies over time. Instead of overloading
1622 the semantics of the "certificate" attribute, this document defines
1623 a new attribute, "star-certificate", to be used instead of
1624 "certificate".<a href="#section-3.1.1-6" class="pilcrow">¶</a></p>
1625 <ul>
1626 <li id="section-3.1.1-7.1">star-certificate (optional, string): A URL for the (rolling)
1627 STAR certificate that has been issued in response to this
1628 Order.<a href="#section-3.1.1-7.1" class="pilcrow">¶</a>
1629 </li>
1630 </ul>
1631 </section>
1632 </div>
1633 <div id="protocol-details-canceling">
1634 <section id="section-3.1.2">
1635 <h4 id="name-canceling-an-auto-renewal-o">
1636 <a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-canceling-an-auto-renewal-o" class="section-name selfRef">Canceling an Auto-renewal Order</a>
1637 </h4>
1638 <p id="section-3.1.2-1">An important property of the auto-renewal Order is that it can be
1639 canceled by the IdO with no need for certificate revocation. To
1640 cancel the Order, the ACME client sends a POST to the Order URL as
1641 shown in <a href="#figcancelingstarorder" class="xref">Figure 3</a>.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p>
1642 <span id="name-canceling-an-auto-renewal-or"></span><div id="figcancelingstarorder">
1643 <figure id="figure-3">
1644 <div id="section-3.1.2-2.1">
1645 <pre class="sourcecode">
1646 POST /acme/order/ogfr8EcolOT HTTP/1.1
1647 Host: example.com
1648 Content-Type: application/jose+json
1649
1650 {
1651 "protected": base64url({
1652 "alg": "ES256",
1653 "kid": "https://example.com/acme/acct/gw06UNhKfOve",
1654 "nonce": "Alc00Ap6Rt7GMkEl3L1JX5",
1655 "url": "https://example.com/acme/order/ogfr8EcolOT"
1656 }),
1657 "payload": base64url({
1658 "status": "canceled"
1659 }),
1660 "signature": "g454e3hdBlkT4AEw...nKePnUyZTjGtXZ6H"
1661 }
1662 </pre>
1663 </div>
1664 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1665 <a href="#name-canceling-an-auto-renewal-or" class="selfRef">Canceling an Auto-renewal Order</a>
1666 </figcaption></figure>
1667 </div>
1668 <p id="section-3.1.2-3">After a successful cancellation, the server <span class="bcp14">MUST NOT</span> issue any additional certificates for this Order.<a href="#section-3.1.2-3" class="pilcrow">¶</a></p>
1669 <p id="section-3.1.2-4">When the Order is canceled, the server:<a href="#section-3.1.2-4" class="pilcrow">¶</a></p>
1670 <ul>
1671 <li id="section-3.1.2-5.1">
1672 <span class="bcp14">MUST</span> update the status of the Order resource to "canceled" and <span class="bcp14">MUST</span> set an appropriate "expires" date;<a href="#section-3.1.2-5.1" class="pilcrow">¶</a>
1673 </li>
1674 <li id="section-3.1.2-5.2">
1675 <span class="bcp14">MUST</span> respond with 403 (Forbidden) to any
1676 requests to the star-certificate endpoint. The response
1677 <span class="bcp14">SHOULD</span> provide additional information using a
1678 problem document <span>[<a href="#RFC7807" class="xref">RFC7807</a>]</span> with
1679 type "urn:ietf:params:acme:error:autoRenewalCanceled".<a href="#section-3.1.2-5.2" class="pilcrow">¶</a>
1680 </li>
1681 </ul>
1682 <p id="section-3.1.2-6">Issuing a cancellation for an Order that is not in "valid" state
1683 is not allowed. A client <span class="bcp14">MUST NOT</span> send such a
1684 request, and a server <span class="bcp14">MUST</span> return an error response
1685 with status code 400 (Bad Request) and type
1686 "urn:ietf:params:acme:error:autoRenewalCancellationInvalid".<a href="#section-3.1.2-6" class="pilcrow">¶</a></p>
1687 <p id="section-3.1.2-7">The state machine described in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.1.6" class="relref">Section 7.1.6</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> is extended as illustrated in
1688 <a href="#fig-order-state-transitions-ext" class="xref">Figure 4</a>.<a href="#section-3.1.2-7" class="pilcrow">¶</a></p>
1689 <span id="name-state-transitions-for-star-"></span><div id="fig-order-state-transitions-ext">
1690 <figure id="figure-4">
1691 <div class="artwork art-text alignLeft" id="section-3.1.2-8.1">
1692 <pre>
1693 pending --------------+
1694 | |
1695 | All authz |
1696 | "valid" |
1697 V |
1698 ready ---------------+
1699 | |
1700 | Receive |
1701 | finalize |
1702 | request |
1703 V |
1704 processing ------------+
1705 | |
1706 | First |
1707 | certificate | Error or
1708 | issued | Authorization failure
1709 | |
1710 | V
1711 | invalid
1712 V
1713 valid----------------+
1714 | |
1715 | STAR |
1716 | Certificate | Natural
1717 | canceled | Expiration
1718 V |
1719 canceled ='=
1720 </pre>
1721 </div>
1722 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1723 <a href="#name-state-transitions-for-star-" class="selfRef">State Transitions for STAR Order Objects</a>
1724 </figcaption></figure>
1725 </div>
1726 <p id="section-3.1.2-9">Explicit certificate revocation using the revokeCert interface
1727 (<span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.6" class="relref">Section 7.6</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>) is not
1728 supported for STAR certificates. A server receiving a revocation
1729 request for a STAR certificate <span class="bcp14">MUST</span> return an error
1730 response with status code 403 (Forbidden) and type
1731 "urn:ietf:params:acme:error:autoRenewalRevocationNotSupported".<a href="#section-3.1.2-9" class="pilcrow">¶</a></p>
1732 </section>
1733 </div>
1734 </section>
1735 </div>
1736 <div id="capability-discovery">
1737 <section id="section-3.2">
1738 <h3 id="name-capability-discovery">
1739 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-capability-discovery" class="section-name selfRef">Capability Discovery</a>
1740 </h3>
1741 <p id="section-3.2-1">In order to support the discovery of STAR capabilities, the "meta"
1742 field inside the directory object defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-9.7.6" class="relref">Section 9.7.6</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> is extended with a new
1743 "auto-renewal" object. The "auto-renewal" object <span class="bcp14">MUST</span>
1744 be present if the server supports STAR. Its structure is as
1745 follows:<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1746 <ul>
1747 <li id="section-3.2-2.1">min-lifetime (required, integer): Minimum acceptable value for
1748 auto-renewal lifetime, in seconds.<a href="#section-3.2-2.1" class="pilcrow">¶</a>
1749 </li>
1750 <li id="section-3.2-2.2">max-duration (required, integer): Maximum allowed delta between
1751 the end-date and start-date attributes of the Order's auto-renewal
1752 object.<a href="#section-3.2-2.2" class="pilcrow">¶</a>
1753 </li>
1754 <li id="section-3.2-2.3">allow-certificate-get (optional, boolean): See <a href="#certificate-get-nego" class="xref">Section 3.4</a>.<a href="#section-3.2-2.3" class="pilcrow">¶</a>
1755 </li>
1756 </ul>
1757 <p id="section-3.2-3">An example directory object advertising STAR support with one-day
1758 min-lifetime and one-year max-duration and supporting certificate
1759 fetching with an HTTP GET is shown in <a href="#figstardir" class="xref">Figure 5</a>.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
1760 <span id="name-directory-object-with-star-"></span><div id="figstardir">
1761 <figure id="figure-5">
1762 <div id="section-3.2-4.1">
1763 <pre class="sourcecode lang-JSON">
1764 {
1765 "new-nonce": "https://example.com/acme/new-nonce",
1766 "new-account": "https://example.com/acme/new-account",
1767 "new-order": "https://example.com/acme/new-order",
1768 "new-authz": "https://example.com/acme/new-authz",
1769 "revoke-cert": "https://example.com/acme/revoke-cert",
1770 "key-change": "https://example.com/acme/key-change",
1771 "meta": {
1772 "terms-of-service": "https://example.com/acme/terms/2017-5-30",
1773 "website": "https://www.example.com/",
1774 "caa-identities": ["example.com"],
1775 "auto-renewal": {
1776 "min-lifetime": 86400,
1777 "max-duration": 31536000,
1778 "allow-certificate-get": true
1779 }
1780 }
1781 }
1782 </pre>
1783 </div>
1784 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1785 <a href="#name-directory-object-with-star-" class="selfRef">Directory Object with STAR Support</a>
1786 </figcaption></figure>
1787 </div>
1788 </section>
1789 </div>
1790 <div id="fetching-certificates">
1791 <section id="section-3.3">
1792 <h3 id="name-fetching-the-certificates">
1793 <a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-fetching-the-certificates" class="section-name selfRef">Fetching the Certificates</a>
1794 </h3>
1795 <p id="section-3.3-1">The certificate is fetched from the star-certificate endpoint with
1796 POST-as-GET as per <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-7.4.2" class="relref">Section 7.4.2</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> unless the client and server have successfully
1797 negotiated the "unauthenticated GET" option described in <a href="#certificate-get-nego" class="xref">Section 3.4</a>. In such case, the
1798 client can simply issue a GET to the star-certificate resource without
1799 authenticating itself to the server as illustrated in <a href="#figunauthgetstarcert" class="xref">Figure 6</a>.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
1800 <span id="name-fetching-a-star-certificate"></span><div id="figunauthgetstarcert">
1801 <figure id="figure-6">
1802 <div class="artwork art-text alignLeft" id="section-3.3-2.1">
1803 <pre>
1804 GET /acme/cert/g7m3ZQeTEqa HTTP/1.1
1805 Host: example.com
1806 Accept: application/pem-certificate-chain
1807
1808 HTTP/1.1 200 OK
1809 Content-Type: application/pem-certificate-chain
1810 Link: &lt;https://example.com/acme/some-directory&gt;;rel="index"
1811 Cert-Not-Before: Thu, 3 Oct 2019 00:00:00 GMT
1812 Cert-Not-After: Thu, 10 Oct 2019 00:00:00 GMT
1813
1814 -----BEGIN CERTIFICATE-----
1815 [End-entity certificate contents]
1816 -----END CERTIFICATE-----
1817 -----BEGIN CERTIFICATE-----
1818 [Issuer certificate contents]
1819 -----END CERTIFICATE-----
1820 -----BEGIN CERTIFICATE-----
1821 [Other certificate contents]
1822 -----END CERTIFICATE-----
1823 </pre>
1824 </div>
1825 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
1826 <a href="#name-fetching-a-star-certificate" class="selfRef">Fetching a STAR Certificate with Unauthenticated GET</a>
1827 </figcaption></figure>
1828 </div>
1829 <p id="section-3.3-3">The server <span class="bcp14">SHOULD</span> include the "Cert-Not-Before" and
1830 "Cert-Not-After" HTTP header fields in the response. When they exist,
1831 they <span class="bcp14">MUST</span> be equal to the respective fields inside the
1832 end-entity certificate. Their format is "HTTP-date" as defined in
1833 <span><a href="https://www.rfc-editor.org/rfc/rfc7231#section-7.1.1.2" class="relref">Section 7.1.1.2</a> of [<a href="#RFC7231" class="xref">RFC7231</a>]</span>. Their
1834 purpose is to enable client implementations that do not parse the
1835 certificate.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
1836 <p id="section-3.3-4">The following are further clarifications regarding usage of these
1837 header fields as per <span><a href="https://www.rfc-editor.org/rfc/rfc7231#section-8.3.1" class="relref">Section 8.3.1</a> of [<a href="#RFC7231" class="xref">RFC7231</a>]</span>. All apply to both headers.<a href="#section-3.3-4" class="pilcrow">¶</a></p>
1838 <ul>
1839 <li id="section-3.3-5.1">This header field is a single value, not a list.<a href="#section-3.3-5.1" class="pilcrow">¶</a>
1840 </li>
1841 <li id="section-3.3-5.2">The header field is used only in responses to GET, HEAD, and
1842 POST-as-GET requests, and only for MIME types that denote public key
1843 certificates.<a href="#section-3.3-5.2" class="pilcrow">¶</a>
1844 </li>
1845 <li id="section-3.3-5.3">Header field semantics are independent of context.<a href="#section-3.3-5.3" class="pilcrow">¶</a>
1846 </li>
1847 <li id="section-3.3-5.4">The header field is not hop-by-hop.<a href="#section-3.3-5.4" class="pilcrow">¶</a>
1848 </li>
1849 <li id="section-3.3-5.5">Intermediaries <span class="bcp14">MAY</span> insert or delete the value;<a href="#section-3.3-5.5" class="pilcrow">¶</a>
1850 </li>
1851 <li id="section-3.3-5.6">If an intermediary inserts the value, it <span class="bcp14">MUST</span>
1852 ensure that the newly added value matches the corresponding value in
1853 the certificate.<a href="#section-3.3-5.6" class="pilcrow">¶</a>
1854 </li>
1855 <li id="section-3.3-5.7">The header field is not appropriate for a Vary field.<a href="#section-3.3-5.7" class="pilcrow">¶</a>
1856 </li>
1857 <li id="section-3.3-5.8">The header field is allowed within message trailers.<a href="#section-3.3-5.8" class="pilcrow">¶</a>
1858 </li>
1859 <li id="section-3.3-5.9">The header field is not appropriate within redirects.<a href="#section-3.3-5.9" class="pilcrow">¶</a>
1860 </li>
1861 <li id="section-3.3-5.10">The header field does not introduce additional security
1862 considerations. It discloses in a simpler form information that is
1863 already available inside the certificate.<a href="#section-3.3-5.10" class="pilcrow">¶</a>
1864 </li>
1865 </ul>
1866 <p id="section-3.3-6">To improve robustness, the next certificate <span class="bcp14">MUST</span> be made
1867 available by the ACME CA at the URL indicated by "star-certificate" halfway
1868 through the lifetime of the currently active certificate at the latest. It is
1869 worth noting that this has an implication in case of cancellation; in fact,
1870 from the time the next certificate is made available, the cancellation is not
1871 completely effective until the "next" certificate also expires. To avoid the
1872 client accidentally entering a broken state, the notBefore of the "next"
1873 certificate <span class="bcp14">MUST</span> be set so that the certificate is already
1874 valid when it is published at the "star-certificate" URL. Note that the
1875 server might need to increase the auto-renewal lifetime-adjust value to
1876 satisfy the latter requirement. For a detailed description of the renewal
1877 scheduling logic, see <a href="#computing-effective-cert-lifetime" class="xref">Section 3.5</a>. For further rationale on the need for adjusting the
1878 certificate validity, see <a href="#operational-cons-clocks" class="xref">Section 4.1</a>.<a href="#section-3.3-6" class="pilcrow">¶</a></p>
1879 <p id="section-3.3-7">The server <span class="bcp14">MUST NOT</span> issue any certificates for this
1880 Order with notAfter after the auto-renewal end-date.<a href="#section-3.3-7" class="pilcrow">¶</a></p>
1881 <p id="section-3.3-8">For expired Orders, the server <span class="bcp14">MUST</span> respond with 403
1882 (Forbidden) to any requests to the star-certificate endpoint. The
1883 response <span class="bcp14">SHOULD</span> provide additional information using a
1884 problem document <span>[<a href="#RFC7807" class="xref">RFC7807</a>]</span> with type
1885 "urn:ietf:params:acme:error:autoRenewalExpired". Note that the Order
1886 resource's state remains "valid", as per the base protocol.<a href="#section-3.3-8" class="pilcrow">¶</a></p>
1887 </section>
1888 </div>
1889 <div id="certificate-get-nego">
1890 <section id="section-3.4">
1891 <h3 id="name-negotiating-an-unauthentica">
1892 <a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-negotiating-an-unauthentica" class="section-name selfRef">Negotiating an Unauthenticated GET</a>
1893 </h3>
1894 <p id="section-3.4-1">In order to enable the name delegation workflow defined in <span>[<a href="#I-D.ietf-acme-star-delegation" class="xref">STAR-DELEGATION</a>]</span> and to
1895 increase the reliability of the STAR ecosystem (see <a href="#dependability" class="xref">Section 4.3</a> for details), this document
1896 defines a mechanism that allows a server to advertise support for
1897 accessing star-certificate resources via unauthenticated GET (in
1898 addition to POST-as-GET), and a client to enable this service with
1899 per-Order granularity.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
1900 <p id="section-3.4-2">Specifically, a server states its availability to grant
1901 unauthenticated access to a client's Order star-certificate by setting
1902 the allow-certificate-get attribute to "true" in the auto-renewal object
1903 of the meta field inside the directory object:<a href="#section-3.4-2" class="pilcrow">¶</a></p>
1904 <ul>
1905 <li id="section-3.4-3.1">allow-certificate-get (optional, boolean): If this field is
1906 present and set to "true", the server allows GET (and HEAD) requests
1907 to star-certificate URLs.<a href="#section-3.4-3.1" class="pilcrow">¶</a>
1908 </li>
1909 </ul>
1910 <p id="section-3.4-4">A client states its desire to access the issued star-certificate
1911 via unauthenticated GET by adding an allow-certificate-get attribute
1912 to the auto-renewal object of the payload of its newOrder request and
1913 setting it to "true".<a href="#section-3.4-4" class="pilcrow">¶</a></p>
1914 <ul>
1915 <li id="section-3.4-5.1">allow-certificate-get (optional, boolean): If this field is
1916 present and set to "true", the client requests the server to allow
1917 unauthenticated GET (and HEAD) to the star-certificate associated
1918 with this Order.<a href="#section-3.4-5.1" class="pilcrow">¶</a>
1919 </li>
1920 </ul>
1921 <p id="section-3.4-6">If the server accepts the request, it <span class="bcp14">MUST</span> reflect
1922 the attribute setting in the resulting order object.<a href="#section-3.4-6" class="pilcrow">¶</a></p>
1923 <p id="section-3.4-7">Note that even when the use of unauthenticated GET has been agreed
1924 upon, the server <span class="bcp14">MUST</span> also allow POST-as-GET requests
1925 to the star-certificate resource.<a href="#section-3.4-7" class="pilcrow">¶</a></p>
1926 </section>
1927 </div>
1928 <div id="computing-effective-cert-lifetime">
1929 <section id="section-3.5">
1930 <h3 id="name-computing-notbefore-and-not">
1931 <a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-computing-notbefore-and-not" class="section-name selfRef">Computing notBefore and notAfter of STAR Certificates</a>
1932 </h3>
1933 <p id="section-3.5-1">We define "nominal renewal date" as the point in time when a new
1934 short-term certificate for a given STAR Order is due. Its cadence is
1935 a multiple of the Order's auto-renewal lifetime that starts with the
1936 issuance of the first short-term certificate and is upper-bounded by
1937 the Order's auto-renewal end-date (<a href="#fignrd" class="xref">Figure 7</a>).<a href="#section-3.5-1" class="pilcrow">¶</a></p>
1938 <span id="name-nominal-renewal-date"></span><div id="fignrd">
1939 <figure id="figure-7">
1940 <div class="artwork art-text alignLeft" id="section-3.5-2.1">
1941 <pre>
1942 T - STAR Order's auto-renewal lifetime
1943 end - STAR Order's auto-renewal end-date
1944 nrd[i] - nominal renewal date of the i-th STAR certificate
1945
1946
1947 .- T -. .- T -. .- T -. .__.
1948 / \ / \ / \ / end
1949 -----------o---------o---------o---------o----X-------&gt; t
1950 nrd[0] nrd[1] nrd[2] nrd[3]
1951 </pre>
1952 </div>
1953 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
1954 <a href="#name-nominal-renewal-date" class="selfRef">Nominal Renewal Date</a>
1955 </figcaption></figure>
1956 </div>
1957 <p id="section-3.5-3">The rules to determine the notBefore and notAfter values of the i-th STAR
1958 certificate are as follows:<a href="#section-3.5-3" class="pilcrow">¶</a></p>
1959 <div class="artwork art-text alignLeft" id="section-3.5-4">
1960 <pre>
1961 notAfter = min(nrd[i] + T, end)
1962 notBefore = nrd[i] - max(adjust_client, adjust_server)
1963 </pre><a href="#section-3.5-4" class="pilcrow">¶</a>
1964 </div>
1965 <p id="section-3.5-5">Where "adjust_client" is the minimum value between the auto-renewal
1966 lifetime-adjust value ("la"), optionally supplied by the client, and
1967 the auto-renewal lifetime of each short-term certificate ("T");
1968 "adjust_server" is the amount of padding added by the ACME server to
1969 make sure that all certificates being published are valid at the time
1970 of publication. The server padding is a fraction (f) of T (i.e., f
1971 * T with .5 &lt;= f &lt; 1; see <a href="#fetching-certificates" class="xref">Section 3.3</a>):<a href="#section-3.5-5" class="pilcrow">¶</a></p>
1972 <div class="artwork art-text alignLeft" id="section-3.5-6">
1973 <pre>
1974 adjust_client = min(T, la)
1975 adjust_server = f * T
1976 </pre><a href="#section-3.5-6" class="pilcrow">¶</a>
1977 </div>
1978 <p id="section-3.5-7">Note that the ACME server <span class="bcp14">MUST NOT</span> set the notBefore of the first STAR
1979 certificate to a date prior to the auto-renewal start-date.<a href="#section-3.5-7" class="pilcrow">¶</a></p>
1980 <div id="example">
1981 <section id="section-3.5.1">
1982 <h4 id="name-example">
1983 <a href="#section-3.5.1" class="section-number selfRef">3.5.1. </a><a href="#name-example" class="section-name selfRef">Example</a>
1984 </h4>
1985 <p id="section-3.5.1-1">Given a server that intends to publish the next STAR certificate halfway
1986 through the lifetime of the previous one, and a STAR Order with the following
1987 attributes:<a href="#section-3.5.1-1" class="pilcrow">¶</a></p>
1988 <div class="artwork art-text alignLeft" id="section-3.5.1-2">
1989 <pre>
1990 "auto-renewal": {
1991 "start-date": "2019-01-10T00:00:00Z",
1992 "end-date": "2019-01-20T00:00:00Z",
1993 "lifetime": 345600, // 4 days
1994 "lifetime-adjust": 259200 // 3 days
1995 }
1996 </pre><a href="#section-3.5.1-2" class="pilcrow">¶</a>
1997 </div>
1998 <p id="section-3.5.1-3">The amount of time that needs to be subtracted from each nominal renewal
1999 date is 3 days, i.e., max(min(345600, 259200), 345600 * .5).<a href="#section-3.5.1-3" class="pilcrow">¶</a></p>
2000 <p id="section-3.5.1-4">The notBefore and notAfter of each short-term certificate are:<a href="#section-3.5.1-4" class="pilcrow">¶</a></p>
2001 <table class="center" id="table-1">
2002 <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
2003 <thead>
2004 <tr>
2005 <th class="text-left" rowspan="1" colspan="1">notBefore</th>
2006 <th class="text-left" rowspan="1" colspan="1">notAfter</th>
2007 </tr>
2008 </thead>
2009 <tbody>
2010 <tr>
2011 <td class="text-left" rowspan="1" colspan="1">2019-01-10T00:00:00Z</td>
2012 <td class="text-left" rowspan="1" colspan="1">2019-01-14T00:00:00Z</td>
2013 </tr>
2014 <tr>
2015 <td class="text-left" rowspan="1" colspan="1">2019-01-11T00:00:00Z</td>
2016 <td class="text-left" rowspan="1" colspan="1">2019-01-18T00:00:00Z</td>
2017 </tr>
2018 <tr>
2019 <td class="text-left" rowspan="1" colspan="1">2019-01-15T00:00:00Z</td>
2020 <td class="text-left" rowspan="1" colspan="1">2019-01-20T00:00:00Z</td>
2021 </tr>
2022 </tbody>
2023 </table>
2024 <p id="section-3.5.1-6">The value of the notBefore is also the time at which the client should expect
2025 the new certificate to be available from the star-certificate endpoint.<a href="#section-3.5.1-6" class="pilcrow">¶</a></p>
2026 </section>
2027 </div>
2028 </section>
2029 </div>
2030 </section>
2031 </div>
2032 <div id="operational-considerations">
2033 <section id="section-4">
2034 <h2 id="name-operational-considerations">
2035 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-operational-considerations" class="section-name selfRef">Operational Considerations</a>
2036 </h2>
2037 <div id="operational-cons-clocks">
2038 <section id="section-4.1">
2039 <h3 id="name-the-meaning-of-short-term-a">
2040 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-the-meaning-of-short-term-a" class="section-name selfRef">The Meaning of "Short Term" and the Impact of Skewed Clocks</a>
2041 </h3>
2042 <p id="section-4.1-1">"Short Term" is a relative concept; therefore, trying to define a
2043 cutoff point that works in all cases would be a useless exercise. In
2044 practice, the expected lifetime of a STAR certificate will be counted
2045 in minutes, hours, or days, depending on different factors: the
2046 underlying requirements for revocation, how much clock synchronization
2047 is expected among relying parties and the issuing CA, etc.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
2048 <p id="section-4.1-2">Nevertheless, this section attempts to provide reasonable
2049 suggestions for the Web use case, informed by current operational and
2050 research experience.<a href="#section-4.1-2" class="pilcrow">¶</a></p>
2051 <p id="section-4.1-3">Acer et al. <span>[<a href="#ACER" class="xref">ACER</a>]</span> find that one of
2052 the main causes of "HTTPS error" warnings in browsers is misconfigured
2053 client clocks. In particular, they observe that roughly 95% of the
2054 "severe" clock skews -- the 6.7% of clock-related breakage reports
2055 that account for clients that are more than 24 hours behind -- happen
2056 to be within 6-7 days.<a href="#section-4.1-3" class="pilcrow">¶</a></p>
2057 <p id="section-4.1-4">In order to avoid these spurious warnings about a not yet valid
2058 server certificate, site owners could use the auto-renewal
2059 lifetime-adjust attribute to control the effective lifetime of their
2060 Web-facing certificates. The exact number depends on the percentage
2061 of the "clock-skewed" population that the site owner expects to
2062 protect -- 5 days cover 97.3%, 7 days cover 99.6% -- as well as the
2063 nominal auto-renewal lifetime of the STAR Order. Note that exact
2064 choice is also likely to depend on the kinds of client that are
2065 prevalent for a given site or app -- for example, Android and Mac OS
2066 clients are known to behave better than Windows clients. These
2067 considerations are clearly out of scope of this document.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
2068 <p id="section-4.1-5">In terms of security, STAR certificates and certificates with the
2069 Online Certificate Status Protocol (OCSP) "must-staple" flag asserted <span>[<a href="#RFC7633" class="xref">RFC7633</a>]</span> can be considered roughly
2070 equivalent if the STAR certificate's and the OCSP response's lifetimes
2071 are the same. (Here, "must-staple" refers to a certificate carrying a
2072 TLS feature extension with the "status_request" extension identifier
2073 <span>[<a href="#RFC6066" class="xref">RFC6066</a>]</span>.) Given OCSP responses can be cached, on average, for 4
2074 days <span>[<a href="#STARK" class="xref">STARK</a>]</span>, it is
2075 <span class="bcp14">RECOMMENDED</span> that a STAR certificate that is used on the
2076 Web has an "effective" lifetime (excluding any adjustment to account
2077 for clock skews) no longer than 4 days.<a href="#section-4.1-5" class="pilcrow">¶</a></p>
2078 </section>
2079 </div>
2080 <div id="impact-on-certificate-transparency-ct-logs">
2081 <section id="section-4.2">
2082 <h3 id="name-impact-on-certificate-trans">
2083 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-impact-on-certificate-trans" class="section-name selfRef">Impact on Certificate Transparency (CT) Logs</a>
2084 </h3>
2085 <p id="section-4.2-1">Even in the highly unlikely case STAR becomes the only certificate
2086 issuance model, discussion with the IETF TRANS Working Group and
2087 implementers of Certificate Transparency (CT) logs suggests that existing
2088 CT Log server implementations are capable of sustaining the resulting
2089 100-fold increase in ingestion rate. Additionally, such a future
2090 higher load could be managed with a variety of techniques (e.g.,
2091 sharding by modulo of certificate hash, using "smart" load-balancing
2092 CT proxies, etc.). With regards to the increase in the log size,
2093 current CT log growth is already being managed with schemes like
2094 Chrome's Log Policy <span>[<a href="#OBRIEN" class="xref">OBRIEN</a>]</span>, which
2095 allow Operators to define their log life cycle, as well as allowing the CAs,
2096 User Agents, Monitors, and any other interested entities to build in
2097 support for that life cycle ahead of time.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
2098 </section>
2099 </div>
2100 <div id="dependability">
2101 <section id="section-4.3">
2102 <h3 id="name-http-caching-and-dependabil">
2103 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-http-caching-and-dependabil" class="section-name selfRef">HTTP Caching and Dependability</a>
2104 </h3>
2105 <p id="section-4.3-1">When using authenticated POST-as-GET, the HTTPS endpoint from where
2106 the STAR certificate is fetched can't be easily replicated by an
2107 on-path HTTP cache. Reducing the caching properties of the protocol
2108 makes STAR clients increasingly dependent on the ACME server
2109 availability. This might be problematic given the relatively high
2110 rate of client-server interactions in a STAR ecosystem, especially
2111 when multiple endpoints (e.g., a high number of CDN edge nodes) end up
2112 requesting the same certificate. Clients and servers should consider
2113 using the mechanism described in <a href="#certificate-get-nego" class="xref">Section 3.4</a> to mitigate the risk.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
2114 <p id="section-4.3-2">When using unauthenticated GET to fetch the STAR certificate, the server <span class="bcp14">SHALL</span>
2115 use the appropriate cache directives to set the freshness lifetime of the
2116 response (<span><a href="https://www.rfc-editor.org/rfc/rfc7234#section-5.2" class="relref">Section 5.2</a> of [<a href="#RFC7234" class="xref">RFC7234</a>]</span>) such that on-path caches will consider
2117 it stale before or at the time its effective lifetime is due to expire.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
2118 </section>
2119 </div>
2120 </section>
2121 </div>
2122 <div id="iana-considerations">
2123 <section id="section-5">
2124 <h2 id="name-iana-considerations">
2125 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2126 </h2>
2127 <div id="new-registries">
2128 <section id="section-5.1">
2129 <h3 id="name-new-registries">
2130 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-new-registries" class="section-name selfRef">New Registries</a>
2131 </h3>
2132 <p id="section-5.1-1">Per this document, IANA has created the following new registries:<a href="#section-5.1-1" class="pilcrow">¶</a></p>
2133 <ul>
2134 <li id="section-5.1-2.1">ACME Order Auto-Renewal Fields (<a href="#iana-order-auto-renewal-registry" class="xref">Section 5.4</a>)<a href="#section-5.1-2.1" class="pilcrow">¶</a>
2135 </li>
2136 <li id="section-5.1-2.2">ACME Directory Metadata Auto-Renewal Fields (<a href="#iana-metadata-auto-renewal-registry" class="xref">Section 5.6</a>)<a href="#section-5.1-2.2" class="pilcrow">¶</a>
2137 </li>
2138 </ul>
2139 <p id="section-5.1-3">These registries are administered under a Specification Required policy
2140 <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
2141 </section>
2142 </div>
2143 <div id="new-error-types">
2144 <section id="section-5.2">
2145 <h3 id="name-new-error-types">
2146 <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-new-error-types" class="section-name selfRef">New Error Types</a>
2147 </h3>
2148 <p id="section-5.2-1">Per this document, IANA has added the following entries to the "ACME Error Types" registry:<a href="#section-5.2-1" class="pilcrow">¶</a></p>
2149 <table class="center" id="table-2">
2150 <caption><a href="#table-2" class="selfRef">Table 2</a></caption>
2151 <thead>
2152 <tr>
2153 <th class="text-left" rowspan="1" colspan="1">Type</th>
2154 <th class="text-left" rowspan="1" colspan="1">Description</th>
2155 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2156 </tr>
2157 </thead>
2158 <tbody>
2159 <tr>
2160 <td class="text-left" rowspan="1" colspan="1">autoRenewalCanceled</td>
2161 <td class="text-left" rowspan="1" colspan="1">The short-term certificate is no longer available because the auto-renewal Order has been explicitly canceled by the IdO</td>
2162 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2163 </tr>
2164 <tr>
2165 <td class="text-left" rowspan="1" colspan="1">autoRenewalExpired</td>
2166 <td class="text-left" rowspan="1" colspan="1">The short-term certificate is no longer available because the auto-renewal Order has expired</td>
2167 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2168 </tr>
2169 <tr>
2170 <td class="text-left" rowspan="1" colspan="1">autoRenewalCancellationInvalid</td>
2171 <td class="text-left" rowspan="1" colspan="1">A request to cancel an auto-renewal Order that is not in state "valid" has been received</td>
2172 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2173 </tr>
2174 <tr>
2175 <td class="text-left" rowspan="1" colspan="1">autoRenewalRevocationNotSupported</td>
2176 <td class="text-left" rowspan="1" colspan="1">A request to revoke an auto-renewal Order has been received</td>
2177 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2178 </tr>
2179 </tbody>
2180 </table>
2181 </section>
2182 </div>
2183 <div id="new-fields-in-order-objects">
2184 <section id="section-5.3">
2185 <h3 id="name-new-fields-in-order-objects">
2186 <a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-new-fields-in-order-objects" class="section-name selfRef">New Fields in Order Objects</a>
2187 </h3>
2188 <p id="section-5.3-1">Per this document, IANA has added the following entries to the
2189 "ACME Order Object Fields" registry:<a href="#section-5.3-1" class="pilcrow">¶</a></p>
2190 <table class="center" id="table-3">
2191 <caption><a href="#table-3" class="selfRef">Table 3</a></caption>
2192 <thead>
2193 <tr>
2194 <th class="text-left" rowspan="1" colspan="1">Field Name</th>
2195 <th class="text-left" rowspan="1" colspan="1">Field Type</th>
2196 <th class="text-left" rowspan="1" colspan="1">Configurable</th>
2197 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2198 </tr>
2199 </thead>
2200 <tbody>
2201 <tr>
2202 <td class="text-left" rowspan="1" colspan="1">auto-renewal</td>
2203 <td class="text-left" rowspan="1" colspan="1">object</td>
2204 <td class="text-left" rowspan="1" colspan="1">true</td>
2205 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2206 </tr>
2207 <tr>
2208 <td class="text-left" rowspan="1" colspan="1">star-certificate</td>
2209 <td class="text-left" rowspan="1" colspan="1">string</td>
2210 <td class="text-left" rowspan="1" colspan="1">false</td>
2211 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2212 </tr>
2213 </tbody>
2214 </table>
2215 </section>
2216 </div>
2217 <div id="iana-order-auto-renewal-registry">
2218 <section id="section-5.4">
2219 <h3 id="name-fields-in-the-auto-renewal-">
2220 <a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-fields-in-the-auto-renewal-" class="section-name selfRef">Fields in the "auto-renewal" Object within an Order Object</a>
2221 </h3>
2222 <p id="section-5.4-1">The "ACME Order Auto-Renewal Fields" registry lists field names that are
2223 defined for use in the JSON object included in the "auto-renewal" field of an
2224 ACME order object.<a href="#section-5.4-1" class="pilcrow">¶</a></p>
2225 <p id="section-5.4-2">Template:<a href="#section-5.4-2" class="pilcrow">¶</a></p>
2226 <ul>
2227 <li id="section-5.4-3.1">Field name: The string to be used as a field name in the JSON object<a href="#section-5.4-3.1" class="pilcrow">¶</a>
2228 </li>
2229 <li id="section-5.4-3.2">Field type: The type of value to be provided, e.g., string, boolean, array of
2230 string<a href="#section-5.4-3.2" class="pilcrow">¶</a>
2231 </li>
2232 <li id="section-5.4-3.3">Configurable: Boolean indicating whether the server should accept values
2233 provided by the client<a href="#section-5.4-3.3" class="pilcrow">¶</a>
2234 </li>
2235 <li id="section-5.4-3.4">Reference: Where this field is defined<a href="#section-5.4-3.4" class="pilcrow">¶</a>
2236 </li>
2237 </ul>
2238 <p id="section-5.4-4">Initial contents: The fields and descriptions defined in <a href="#star-order-ext" class="xref">Section 3.1.1</a>.<a href="#section-5.4-4" class="pilcrow">¶</a></p>
2239 <table class="center" id="table-4">
2240 <caption><a href="#table-4" class="selfRef">Table 4</a></caption>
2241 <thead>
2242 <tr>
2243 <th class="text-left" rowspan="1" colspan="1">Field Name</th>
2244 <th class="text-left" rowspan="1" colspan="1">Field Type</th>
2245 <th class="text-left" rowspan="1" colspan="1">Configurable</th>
2246 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2247 </tr>
2248 </thead>
2249 <tbody>
2250 <tr>
2251 <td class="text-left" rowspan="1" colspan="1">start-date</td>
2252 <td class="text-left" rowspan="1" colspan="1">string</td>
2253 <td class="text-left" rowspan="1" colspan="1">true</td>
2254 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2255 </tr>
2256 <tr>
2257 <td class="text-left" rowspan="1" colspan="1">end-date</td>
2258 <td class="text-left" rowspan="1" colspan="1">string</td>
2259 <td class="text-left" rowspan="1" colspan="1">true</td>
2260 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2261 </tr>
2262 <tr>
2263 <td class="text-left" rowspan="1" colspan="1">lifetime</td>
2264 <td class="text-left" rowspan="1" colspan="1">integer</td>
2265 <td class="text-left" rowspan="1" colspan="1">true</td>
2266 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2267 </tr>
2268 <tr>
2269 <td class="text-left" rowspan="1" colspan="1">lifetime-adjust</td>
2270 <td class="text-left" rowspan="1" colspan="1">integer</td>
2271 <td class="text-left" rowspan="1" colspan="1">true</td>
2272 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2273 </tr>
2274 <tr>
2275 <td class="text-left" rowspan="1" colspan="1">allow-certificate-get</td>
2276 <td class="text-left" rowspan="1" colspan="1">boolean</td>
2277 <td class="text-left" rowspan="1" colspan="1">true</td>
2278 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2279 </tr>
2280 </tbody>
2281 </table>
2282 </section>
2283 </div>
2284 <div id="new-fields-in-the-meta-object-within-a-directory-object">
2285 <section id="section-5.5">
2286 <h3 id="name-new-fields-in-the-meta-obje">
2287 <a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-new-fields-in-the-meta-obje" class="section-name selfRef">New Fields in the "meta" Object within a Directory Object</a>
2288 </h3>
2289 <p id="section-5.5-1">Per this document, IANA has added the following entry to the "ACME Directory Metadata Fields":<a href="#section-5.5-1" class="pilcrow">¶</a></p>
2290 <table class="center" id="table-5">
2291 <caption><a href="#table-5" class="selfRef">Table 5</a></caption>
2292 <thead>
2293 <tr>
2294 <th class="text-left" rowspan="1" colspan="1">Field Name</th>
2295 <th class="text-left" rowspan="1" colspan="1">Field Type</th>
2296 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2297 </tr>
2298 </thead>
2299 <tbody>
2300 <tr>
2301 <td class="text-left" rowspan="1" colspan="1">auto-renewal</td>
2302 <td class="text-left" rowspan="1" colspan="1">object</td>
2303 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2304 </tr>
2305 </tbody>
2306 </table>
2307 </section>
2308 </div>
2309 <div id="iana-metadata-auto-renewal-registry">
2310 <section id="section-5.6">
2311 <h3 id="name-fields-in-the-auto-renewal-o">
2312 <a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-fields-in-the-auto-renewal-o" class="section-name selfRef">Fields in the "auto-renewal" Object within a Directory Metadata Object</a>
2313 </h3>
2314 <p id="section-5.6-1">The "ACME Directory Metadata Auto-Renewal Fields" registry lists field names
2315 that are defined for use in the JSON object included in the "auto-renewal"
2316 field of an ACME directory "meta" object.<a href="#section-5.6-1" class="pilcrow">¶</a></p>
2317 <p id="section-5.6-2">Template:<a href="#section-5.6-2" class="pilcrow">¶</a></p>
2318 <ul>
2319 <li id="section-5.6-3.1">Field name: The string to be used as a field name in the JSON object<a href="#section-5.6-3.1" class="pilcrow">¶</a>
2320 </li>
2321 <li id="section-5.6-3.2">Field type: The type of value to be provided, e.g., string, boolean, array of
2322 string<a href="#section-5.6-3.2" class="pilcrow">¶</a>
2323 </li>
2324 <li id="section-5.6-3.3">Reference: Where this field is defined<a href="#section-5.6-3.3" class="pilcrow">¶</a>
2325 </li>
2326 </ul>
2327 <p id="section-5.6-4">Initial contents: The fields and descriptions defined in <a href="#capability-discovery" class="xref">Section 3.2</a>.<a href="#section-5.6-4" class="pilcrow">¶</a></p>
2328 <table class="center" id="table-6">
2329 <caption><a href="#table-6" class="selfRef">Table 6</a></caption>
2330 <thead>
2331 <tr>
2332 <th class="text-left" rowspan="1" colspan="1">Field Name</th>
2333 <th class="text-left" rowspan="1" colspan="1">Field Type</th>
2334 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2335 </tr>
2336 </thead>
2337 <tbody>
2338 <tr>
2339 <td class="text-left" rowspan="1" colspan="1">min-lifetime</td>
2340 <td class="text-left" rowspan="1" colspan="1">integer</td>
2341 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2342 </tr>
2343 <tr>
2344 <td class="text-left" rowspan="1" colspan="1">max-duration</td>
2345 <td class="text-left" rowspan="1" colspan="1">integer</td>
2346 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2347 </tr>
2348 <tr>
2349 <td class="text-left" rowspan="1" colspan="1">allow-certificate-get</td>
2350 <td class="text-left" rowspan="1" colspan="1">boolean</td>
2351 <td class="text-left" rowspan="1" colspan="1">RFC 8739</td>
2352 </tr>
2353 </tbody>
2354 </table>
2355 </section>
2356 </div>
2357 <div id="iana-http-headers">
2358 <section id="section-5.7">
2359 <h3 id="name-cert-not-before-and-cert-no">
2360 <a href="#section-5.7" class="section-number selfRef">5.7. </a><a href="#name-cert-not-before-and-cert-no" class="section-name selfRef">Cert-Not-Before and Cert-Not-After HTTP Headers</a>
2361 </h3>
2362 <p id="section-5.7-1">The "Message Headers" registry has been updated with the following additional values:<a href="#section-5.7-1" class="pilcrow">¶</a></p>
2363 <table class="center" id="table-7">
2364 <caption><a href="#table-7" class="selfRef">Table 7</a></caption>
2365 <thead>
2366 <tr>
2367 <th class="text-left" rowspan="1" colspan="1">Header Field Name</th>
2368 <th class="text-left" rowspan="1" colspan="1">Protocol</th>
2369 <th class="text-left" rowspan="1" colspan="1">Status</th>
2370 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2371 </tr>
2372 </thead>
2373 <tbody>
2374 <tr>
2375 <td class="text-left" rowspan="1" colspan="1">Cert-Not-Before</td>
2376 <td class="text-left" rowspan="1" colspan="1">http</td>
2377 <td class="text-left" rowspan="1" colspan="1">standard</td>
2378 <td class="text-left" rowspan="1" colspan="1">RFC 8739, <a href="#fetching-certificates" class="xref">Section 3.3</a>
2379 </td>
2380 </tr>
2381 <tr>
2382 <td class="text-left" rowspan="1" colspan="1">Cert-Not-After</td>
2383 <td class="text-left" rowspan="1" colspan="1">http</td>
2384 <td class="text-left" rowspan="1" colspan="1">standard</td>
2385 <td class="text-left" rowspan="1" colspan="1">RFC 8739, <a href="#fetching-certificates" class="xref">Section 3.3</a>
2386 </td>
2387 </tr>
2388 </tbody>
2389 </table>
2390 </section>
2391 </div>
2392 </section>
2393 </div>
2394 <div id="security-considerations">
2395 <section id="section-6">
2396 <h2 id="name-security-considerations">
2397 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2398 </h2>
2399 <div id="no-revocation">
2400 <section id="section-6.1">
2401 <h3 id="name-no-revocation">
2402 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-no-revocation" class="section-name selfRef">No Revocation</a>
2403 </h3>
2404 <p id="section-6.1-1">STAR certificates eliminate an important security feature of PKI,
2405 which is the ability to revoke certificates. Revocation allows the
2406 administrator to limit the damage done by a rogue node or an adversary
2407 who has control of the private key. With STAR certificates,
2408 expiration replaces revocation so there is potential for lack of
2409 timeliness in the revocation taking effect. To that end, see also the
2410 discussion on clock skew in <a href="#operational-cons-clocks" class="xref">Section 4.1</a>.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
2411 <p id="section-6.1-2">It should be noted that revocation also has timeliness issues
2412 because both Certificate Revocation Lists (CRLs) and OCSP responses
2413 have nextUpdate fields that tell relying parties (RPs) how long they
2414 should trust this revocation data. These fields are typically set to
2415 hours, days, or even weeks in the future. Any revocation that happens
2416 before the time in nextUpdate goes unnoticed by the RP.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
2417 <p id="section-6.1-3">One situation where the lack of explicit revocation could create a
2418 security risk to the IdO is when the Order is created with a
2419 start-date of some appreciable amount of time in the future. Recall
2420 that when authorizations have been fulfilled, the Order moves to the
2421 "valid" state and the star-certificate endpoint is populated with the
2422 first cert (<a href="#fig-order-state-transitions-ext" class="xref">Figure 4</a>). So, if an attacker manages to get hold of the
2423 private key as well as the first (post-dated) certificate, there is
2424 a time window in the future when they will be able to successfully
2425 impersonate the IdO. Note that cancellation is pointless in this
2426 case. In order to mitigate the described threat, it is
2427 <span class="bcp14">RECOMMENDED</span> that IdO place their Orders at a time that
2428 is close to the Order's start-date.<a href="#section-6.1-3" class="pilcrow">¶</a></p>
2429 <p id="section-6.1-4">More discussion of the security of STAR certificates is available in
2430 <span>[<a href="#TOPALOVIC" class="xref">TOPALOVIC</a>]</span>.<a href="#section-6.1-4" class="pilcrow">¶</a></p>
2431 </section>
2432 </div>
2433 <div id="denial-of-service-considerations">
2434 <section id="section-6.2">
2435 <h3 id="name-denial-of-service-considera">
2436 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-denial-of-service-considera" class="section-name selfRef">Denial-of-Service Considerations</a>
2437 </h3>
2438 <p id="section-6.2-1">STAR adds a new attack vector that increases the threat of
2439 denial-of-service attacks, caused by the change to the CA's
2440 behavior. Each STAR request amplifies the resource demands upon the
2441 CA, where one Order produces not one but potentially dozens or
2442 hundreds of certificates, depending on the auto-renewal "lifetime"
2443 parameter. An attacker can use this property to aggressively reduce
2444 the auto-renewal "lifetime" (e.g., 1 second) jointly with other ACME
2445 attack vectors identified in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-10" class="relref">Section 10</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span>. Other collateral impact is related to the
2446 certificate endpoint resource where the client can retrieve the
2447 certificates periodically. If this resource is external to the CA
2448 (e.g., a hosted web server), the previous attack will be reflected to
2449 that resource.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
2450 <p id="section-6.2-2">Mitigation recommendations from ACME still apply, but some of them
2451 need to be adjusted. For example, applying rate limiting to the
2452 initial request, due to the nature of the auto-renewal behavior,
2453 cannot solve the above problem. The CA server needs complementary
2454 mitigation, and specifically, it <span class="bcp14">SHOULD</span> enforce a
2455 minimum value on auto-renewal "lifetime". Alternatively, the CA can
2456 set a rate limit for internal certificate generation processes. Note
2457 that this limit has to take account of already scheduled renewal
2458 issuances as well as new incoming requests.<a href="#section-6.2-2" class="pilcrow">¶</a></p>
2459 </section>
2460 </div>
2461 <div id="privacy-considerations">
2462 <section id="section-6.3">
2463 <h3 id="name-privacy-considerations">
2464 <a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
2465 </h3>
2466 <p id="section-6.3-1">In order to avoid correlation of certificates by account, if
2467 unauthenticated GET is negotiated (<a href="#certificate-get-nego" class="xref">Section 3.4</a>), the recommendation in <span><a href="https://www.rfc-editor.org/rfc/rfc8555#section-10.5" class="relref">Section 10.5</a> of [<a href="#RFC8555" class="xref">RFC8555</a>]</span> regarding the choice of URL
2468 structure applies, i.e., servers <span class="bcp14">SHOULD</span> choose URLs of
2469 certificate resources in a non-guessable way, for example, using
2470 capability URLs <span>[<a href="#W3C.CAPABILITY-URLS" class="xref">W3C.CAPABILITY-URLS</a>]</span>.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
2471 </section>
2472 </div>
2473 </section>
2474 </div>
2475 <section id="section-7">
2476 <h2 id="name-references">
2477 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
2478 </h2>
2479 <section id="section-7.1">
2480 <h3 id="name-normative-references">
2481 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2482 </h3>
2483 <dl class="references">
2484 <dt id="RFC2119">[RFC2119]</dt>
2485 <dd>
2486 <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>
2487 <dt id="RFC3339">[RFC3339]</dt>
2488 <dd>
2489 <span class="refAuthor">Klyne, G.</span><span class="refAuthor"> and C. Newman</span>, <span class="refTitle">"Date and Time on the Internet: Timestamps"</span>, <span class="seriesInfo">RFC 3339</span>, <span class="seriesInfo">DOI 10.17487/RFC3339</span>, <time datetime="2002-07">July 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3339">https://www.rfc-editor.org/info/rfc3339</a>&gt;</span>. </dd>
2490 <dt id="RFC7231">[RFC7231]</dt>
2491 <dd>
2492 <span class="refAuthor">Fielding, R., Ed.</span><span class="refAuthor"> and J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</span>, <span class="seriesInfo">RFC 7231</span>, <span class="seriesInfo">DOI 10.17487/RFC7231</span>, <time datetime="2014-06">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7231">https://www.rfc-editor.org/info/rfc7231</a>&gt;</span>. </dd>
2493 <dt id="RFC7234">[RFC7234]</dt>
2494 <dd>
2495 <span class="refAuthor">Fielding, R., Ed.</span><span class="refAuthor">, Nottingham, M., Ed.</span><span class="refAuthor">, and J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Caching"</span>, <span class="seriesInfo">RFC 7234</span>, <span class="seriesInfo">DOI 10.17487/RFC7234</span>, <time datetime="2014-06">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7234">https://www.rfc-editor.org/info/rfc7234</a>&gt;</span>. </dd>
2496 <dt id="RFC7807">[RFC7807]</dt>
2497 <dd>
2498 <span class="refAuthor">Nottingham, M.</span><span class="refAuthor"> and E. Wilde</span>, <span class="refTitle">"Problem Details for HTTP APIs"</span>, <span class="seriesInfo">RFC 7807</span>, <span class="seriesInfo">DOI 10.17487/RFC7807</span>, <time datetime="2016-03">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7807">https://www.rfc-editor.org/info/rfc7807</a>&gt;</span>. </dd>
2499 <dt id="RFC8126">[RFC8126]</dt>
2500 <dd>
2501 <span class="refAuthor">Cotton, M.</span><span class="refAuthor">, Leiba, B.</span><span class="refAuthor">, and T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
2502 <dt id="RFC8174">[RFC8174]</dt>
2503 <dd>
2504 <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>
2505 <dt id="RFC8555">[RFC8555]</dt>
2506 <dd>
2507 <span class="refAuthor">Barnes, R.</span><span class="refAuthor">, Hoffman-Andrews, J.</span><span class="refAuthor">, McCarney, D.</span><span class="refAuthor">, and 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">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>
2508 </dl>
2509 </section>
2510 <section id="section-7.2">
2511 <h3 id="name-informative-references">
2512 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2513 </h3>
2514 <dl class="references">
2515 <dt id="ACER">[ACER]</dt>
2516 <dd>
2517 <span class="refAuthor">Acer, M.E.</span><span class="refAuthor">, Stark, E.</span><span class="refAuthor">, Felt, A.P.</span><span class="refAuthor">, Fahl, S.</span><span class="refAuthor">, Bhargava, R.</span><span class="refAuthor">, Dev, B.</span><span class="refAuthor">, Braithwaite, M.</span><span class="refAuthor">, Sleevi, R.</span><span class="refAuthor">, and P. Tabriz</span>, <span class="refTitle">"Where the Wild Warnings Are: Root Causes of Chrome HTTPS Certificate Errors"</span>, <span class="seriesInfo">DOI 10.1145/3133956.3134007</span>, <time datetime="2017-10">October 2017</time>, <span>&lt;<a href="https://acmccs.github.io/papers/p1407-acerA.pdf">https://acmccs.github.io/papers/p1407-acerA.pdf</a>&gt;</span>. </dd>
2518 <dt id="OBRIEN">[OBRIEN]</dt>
2519 <dd>
2520 <span class="refAuthor">O'Brien, D.</span><span class="refAuthor"> and R. Sleevi</span>, <span class="refTitle">"Chromium Certificate Transparency Policy"</span>, <time datetime="2017-04">April 2017</time>, <span>&lt;<a href="https://github.com/chromium/ct-policy">https://github.com/chromium/ct-policy</a>&gt;</span>. </dd>
2521 <dt id="RFC6066">[RFC6066]</dt>
2522 <dd>
2523 <span class="refAuthor">Eastlake 3rd, D.</span>, <span class="refTitle">"Transport Layer Security (TLS) Extensions: Extension Definitions"</span>, <span class="seriesInfo">RFC 6066</span>, <span class="seriesInfo">DOI 10.17487/RFC6066</span>, <time datetime="2011-01">January 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6066">https://www.rfc-editor.org/info/rfc6066</a>&gt;</span>. </dd>
2524 <dt id="RFC7633">[RFC7633]</dt>
2525 <dd>
2526 <span class="refAuthor">Hallam-Baker, P.</span>, <span class="refTitle">"X.509v3 Transport Layer Security (TLS) Feature Extension"</span>, <span class="seriesInfo">RFC 7633</span>, <span class="seriesInfo">DOI 10.17487/RFC7633</span>, <time datetime="2015-10">October 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7633">https://www.rfc-editor.org/info/rfc7633</a>&gt;</span>. </dd>
2527 <dt id="I-D.nir-saag-star">[SHORT-TERM-CERTS]</dt>
2528 <dd>
2529 <span class="refAuthor">Nir, Y.</span><span class="refAuthor">, Fossati, T.</span><span class="refAuthor">, Sheffer, Y.</span><span class="refAuthor">, and T. Eckert</span>, <span class="refTitle">"Considerations For Using Short Term Certificates"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-nir-saag-star-01</span>, <time datetime="2018-03-05">5 March 2018</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-nir-saag-star-01">https://tools.ietf.org/html/draft-nir-saag-star-01</a>&gt;</span>. </dd>
2530 <dt id="I-D.ietf-acme-star-delegation">[STAR-DELEGATION]</dt>
2531 <dd>
2532 <span class="refAuthor">Sheffer, Y.</span><span class="refAuthor">, Lopez, D.</span><span class="refAuthor">, Pastor, A.</span><span class="refAuthor">, and T. Fossati</span>, <span class="refTitle">"An ACME Profile for Generating Delegated STAR Certificates"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-acme-star-delegation-03</span>, <time datetime="2020-03-08">8 March 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-acme-star-delegation-03">https://tools.ietf.org/html/draft-ietf-acme-star-delegation-03</a>&gt;</span>. </dd>
2533 <dt id="STARK">[STARK]</dt>
2534 <dd>
2535 <span class="refAuthor">Stark, E.</span><span class="refAuthor">, Huang, L.S.</span><span class="refAuthor">, Israni, D.</span><span class="refAuthor">, Jackson, C.</span><span class="refAuthor">, and D. Boneh</span>, <span class="refTitle">"The case for prefetching and prevalidating TLS server certificates"</span>, <time datetime="2012-02">February 2012</time>, <span>&lt;<a href="https://crypto.stanford.edu/~dabo/pubs/abstracts/ssl-prefetch.html">https://crypto.stanford.edu/~dabo/pubs/abstracts/ssl-prefetch.html</a>&gt;</span>. </dd>
2536 <dt id="TOPALOVIC">[TOPALOVIC]</dt>
2537 <dd>
2538 <span class="refAuthor">Topalovic, E.</span><span class="refAuthor">, Saeta, B.</span><span class="refAuthor">, Huang, L.S.</span><span class="refAuthor">, Jackson, C.</span><span class="refAuthor">, and D. Boneh</span>, <span class="refTitle">"Towards Short-Lived Certificates"</span>, <time datetime="2012">2012</time>, <span>&lt;<a href="https://www.ieee-security.org/TC/W2SP/2012/papers/w2sp12-final9.pdf">https://www.ieee-security.org/TC/W2SP/2012/papers/w2sp12-final9.pdf</a>&gt;</span>. </dd>
2539 <dt id="W3C.CAPABILITY-URLS">[W3C.CAPABILITY-URLS]</dt>
2540 <dd>
2541 <span class="refAuthor">Tennison, J.</span>, <span class="refTitle">"Good Practices for Capability URLs"</span>, <span class="refContent">W3C First Public Working Draft</span>, <span class="refContent">Latest version available at &lt;https://www.w3.org/TR/capability-urls/&gt;
2542 </span>, <time datetime="2014-02">February 2014</time>, <span>&lt;<a href="https://www.w3.org/TR/2014/WD-capability-urls-20140218">https://www.w3.org/TR/2014/WD-capability-urls-20140218</a>&gt;</span>. </dd>
2543 </dl>
2544 </section>
2545 </section>
2546 <div id="acknowledgments">
2547 <section id="section-appendix.a">
2548 <h2 id="name-acknowledgments">
2549 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
2550 </h2>
2551 <p id="section-appendix.a-1">This work is partially supported by the European Commission under
2552 Horizon 2020 grant agreement no. 688421 Measurement and Architecture for
2553 a Middleboxed Internet (MAMI). This support does not imply
2554 endorsement.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
2555 <p id="section-appendix.a-2">Thanks to <span class="contact-name">Ben Kaduk</span>, <span class="contact-name">Richard Barnes</span>, <span class="contact-name">Roman Danyliw</span>, <span class="contact-name">Jon Peterson</span>, <span class="contact-name">Eric Rescorla</span>, <span class="contact-name">Ryan Sleevi</span>, <span class="contact-name">Sean Turner</span>, <span class="contact-name">Alexey Melnikov</span>, <span class="contact-name">Adam Roach</span>, <span class="contact-name">Martin Thomson</span>, and <span class="contact-name">Mehmet Ersue</span> for helpful comments and
2556 discussions that have shaped this document.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p>
2557 </section>
2558 </div>
2559 <div id="authors-addresses">
2560 <section id="section-appendix.b">
2561 <h2 id="name-authors-addresses">
2562 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2563 </h2>
2564 <address class="vcard">
2565 <div dir="auto" class="left"><span class="fn nameRole">Yaron Sheffer</span></div>
2566 <div dir="auto" class="left"><span class="org">Intuit</span></div>
2567 <div class="email">
2568 <span>Email:</span>
2569 <a href="mailto:[email protected]" class="email">[email protected]</a>
2570 </div>
2571 </address>
2572 <address class="vcard">
2573 <div dir="auto" class="left"><span class="fn nameRole">Diego Lopez</span></div>
2574 <div dir="auto" class="left"><span class="org">Telefonica I+D</span></div>
2575 <div class="email">
2576 <span>Email:</span>
2577 <a href="mailto:[email protected]" class="email">[email protected]</a>
2578 </div>
2579 </address>
2580 <address class="vcard">
2581 <div dir="auto" class="left"><span class="fn nameRole">Oscar Gonzalez de Dios</span></div>
2582 <div dir="auto" class="left"><span class="org">Telefonica I+D</span></div>
2583 <div class="email">
2584 <span>Email:</span>
2585 <a href="mailto:[email protected]" class="email">[email protected]</a>
2586 </div>
2587 </address>
2588 <address class="vcard">
2589 <div dir="auto" class="left"><span class="fn nameRole">Antonio Agustin Pastor Perales</span></div>
2590 <div dir="auto" class="left"><span class="org">Telefonica I+D</span></div>
2591 <div class="email">
2592 <span>Email:</span>
2593 <a href="mailto:[email protected]" class="email">[email protected]</a>
2594 </div>
2595 </address>
2596 <address class="vcard">
2597 <div dir="auto" class="left"><span class="fn nameRole">Thomas Fossati</span></div>
2598 <div dir="auto" class="left"><span class="org">ARM</span></div>
2599 <div class="email">
2600 <span>Email:</span>
2601 <a href="mailto:[email protected]" class="email">[email protected]</a>
2602 </div>
2603 </address>
2604 </section>
2605 </div>
2606 <script>const toc = document.getElementById("toc");
2607 toc.querySelector("h2").addEventListener("click", e => {
2608 toc.classList.toggle("active");
2609 });
2610 toc.querySelector("nav").addEventListener("click", e => {
2611 toc.classList.remove("active");
2612 });
2613 </script>
2614 </body>
2615 </html>