Debian Codegraph @

rfc9057.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 9057: Email Author Header Field</title>
8 <meta content="Dave Crocker" name="author">
9 <meta content="
10 Internet mail defines the From: header field to indicate the
11 author of the message's content and the Sender: field to
12 indicate who initially handled the message on the author's
13 behalf. The Sender: field is optional if it has the same
14 information as the From: field. This was not a problem until
15 development of stringent protections on use of the From: field.
16 It has prompted Mediators, such as mailing lists, to modify the
17 From: field to circumvent mail rejection caused by those
18 protections. In effect, the From: field has become dominated by
19 its role as a handling identifier.
20 The current specification augments the altered use of the From:
21 field by specifying the Author: field, which ensures
22 identification of the original author of the message and is not
23 subject to modification by Mediators. This document is published
24 as an Experimental RFC to assess community interest, functional
25 efficacy, and technical adequacy.
26 " name="description">
27 <meta content="xml2rfc 3.8.0" name="generator">
28 <meta content="domain" name="keyword">
29 <meta content="email" name="keyword">
30 <meta content="security" name="keyword">
31 <meta content="messaging" name="keyword">
32 <meta content="dkim" name="keyword">
33 <meta content="spf" name="keyword">
34 <meta content="authentication" name="keyword">
35 <meta content="reporting" name="keyword">
36 <meta content="conformance" name="keyword">
37 <meta content="author" name="keyword">
38 <meta content="origination" name="keyword">
39 <meta content="original" name="keyword">
40 <meta content="from" name="keyword">
41 <meta content="sender" name="keyword">
42 <meta content="9057" name="rfc.number">
43 <!-- Generator version information:
44 xml2rfc 3.8.0
45 Python 3.6.10
46 appdirs 1.4.4
47 ConfigArgParse 1.2.3
48 google-i18n-address 2.3.5
49 html5lib 1.0.1
50 intervaltree 3.0.2
51 Jinja2 2.11.2
52 kitchen 1.2.6
53 lxml 4.4.2
54 pycairo 1.19.0
55 pycountry 19.8.18
56 pyflakes 2.1.1
57 PyYAML 5.3.1
58 requests 2.22.0
59 setuptools 40.6.2
60 six 1.14.0
61 WeasyPrint 51
62 -->
63 <link href="rfc9057.xml" rel="alternate" type="application/rfc+xml">
64 <link href="#copyright" rel="license">
65 <style type="text/css">/*
66
67 NOTE: Changes at the bottom of this file overrides some earlier settings.
68
69 Once the style has stabilized and has been adopted as an official RFC style,
70 this can be consolidated so that style settings occur only in one place, but
71 for now the contents of this file consists first of the initial CSS work as
72 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
73 commented changes found necssary during the development of the v3
74 formatters.
75
76 */
77
78 /* fonts */
79 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
80 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
81 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
82
83 @viewport {
84 zoom: 1.0;
85 width: extend-to-zoom;
86 }
87 @-ms-viewport {
88 width: extend-to-zoom;
89 zoom: 1.0;
90 }
91 /* general and mobile first */
92 html {
93 }
94 body {
95 max-width: 90%;
96 margin: 1.5em auto;
97 color: #222;
98 background-color: #fff;
99 font-size: 14px;
100 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
101 line-height: 1.6;
102 scroll-behavior: smooth;
103 }
104 .ears {
105 display: none;
106 }
107
108 /* headings */
109 #title, h1, h2, h3, h4, h5, h6 {
110 margin: 1em 0 0.5em;
111 font-weight: bold;
112 line-height: 1.3;
113 }
114 #title {
115 clear: both;
116 border-bottom: 1px solid #ddd;
117 margin: 0 0 0.5em 0;
118 padding: 1em 0 0.5em;
119 }
120 .author {
121 padding-bottom: 4px;
122 }
123 h1 {
124 font-size: 26px;
125 margin: 1em 0;
126 }
127 h2 {
128 font-size: 22px;
129 margin-top: -20px; /* provide offset for in-page anchors */
130 padding-top: 33px;
131 }
132 h3 {
133 font-size: 18px;
134 margin-top: -36px; /* provide offset for in-page anchors */
135 padding-top: 42px;
136 }
137 h4 {
138 font-size: 16px;
139 margin-top: -36px; /* provide offset for in-page anchors */
140 padding-top: 42px;
141 }
142 h5, h6 {
143 font-size: 14px;
144 }
145 #n-copyright-notice {
146 border-bottom: 1px solid #ddd;
147 padding-bottom: 1em;
148 margin-bottom: 1em;
149 }
150 /* general structure */
151 p {
152 padding: 0;
153 margin: 0 0 1em 0;
154 text-align: left;
155 }
156 div, span {
157 position: relative;
158 }
159 div {
160 margin: 0;
161 }
162 .alignRight.art-text {
163 background-color: #f9f9f9;
164 border: 1px solid #eee;
165 border-radius: 3px;
166 padding: 1em 1em 0;
167 margin-bottom: 1.5em;
168 }
169 .alignRight.art-text pre {
170 padding: 0;
171 }
172 .alignRight {
173 margin: 1em 0;
174 }
175 .alignRight > *:first-child {
176 border: none;
177 margin: 0;
178 float: right;
179 clear: both;
180 }
181 .alignRight > *:nth-child(2) {
182 clear: both;
183 display: block;
184 border: none;
185 }
186 svg {
187 display: block;
188 }
189 .alignCenter.art-text {
190 background-color: #f9f9f9;
191 border: 1px solid #eee;
192 border-radius: 3px;
193 padding: 1em 1em 0;
194 margin-bottom: 1.5em;
195 }
196 .alignCenter.art-text pre {
197 padding: 0;
198 }
199 .alignCenter {
200 margin: 1em 0;
201 }
202 .alignCenter > *:first-child {
203 border: none;
204 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
205 support flexbox yet.
206 */
207 display: table;
208 margin: 0 auto;
209 }
210
211 /* lists */
212 ol, ul {
213 padding: 0;
214 margin: 0 0 1em 2em;
215 }
216 ol ol, ul ul, ol ul, ul ol {
217 margin-left: 1em;
218 }
219 li {
220 margin: 0 0 0.25em 0;
221 }
222 .ulCompact li {
223 margin: 0;
224 }
225 ul.empty, .ulEmpty {
226 list-style-type: none;
227 }
228 ul.empty li, .ulEmpty li {
229 margin-top: 0.5em;
230 }
231 ul.compact, .ulCompact,
232 ol.compact, .olCompact {
233 line-height: 100%;
234 margin: 0 0 0 2em;
235 }
236
237 /* definition lists */
238 dl {
239 }
240 dl > dt {
241 float: left;
242 margin-right: 1em;
243 }
244 /*
245 dl.nohang > dt {
246 float: none;
247 }
248 */
249 dl > dd {
250 margin-bottom: .8em;
251 min-height: 1.3em;
252 }
253 dl.compact > dd, .dlCompact > dd {
254 margin-bottom: 0em;
255 }
256 dl > dd > dl {
257 margin-top: 0.5em;
258 margin-bottom: 0em;
259 }
260
261 /* links */
262 a {
263 text-decoration: none;
264 }
265 a[href] {
266 color: #22e; /* Arlen: WCAG 2019 */
267 }
268 a[href]:hover {
269 background-color: #f2f2f2;
270 }
271 figcaption a[href],
272 a[href].selfRef {
273 color: #222;
274 }
275 /* XXX probably not this:
276 a.selfRef:hover {
277 background-color: transparent;
278 cursor: default;
279 } */
280
281 /* Figures */
282 tt, code, pre, code {
283 background-color: #f9f9f9;
284 font-family: 'Roboto Mono', monospace;
285 }
286 pre {
287 border: 1px solid #eee;
288 margin: 0;
289 padding: 1em;
290 }
291 img {
292 max-width: 100%;
293 }
294 figure {
295 margin: 0;
296 }
297 figure blockquote {
298 margin: 0.8em 0.4em 0.4em;
299 }
300 figcaption {
301 font-style: italic;
302 margin: 0 0 1em 0;
303 }
304 @media screen {
305 pre {
306 overflow-x: auto;
307 max-width: 100%;
308 max-width: calc(100% - 22px);
309 }
310 }
311
312 /* aside, blockquote */
313 aside, blockquote {
314 margin-left: 0;
315 padding: 1.2em 2em;
316 }
317 blockquote {
318 background-color: #f9f9f9;
319 color: #111; /* Arlen: WCAG 2019 */
320 border: 1px solid #ddd;
321 border-radius: 3px;
322 margin: 1em 0;
323 }
324 cite {
325 display: block;
326 text-align: right;
327 font-style: italic;
328 }
329
330 /* tables */
331 table {
332 width: 100%;
333 margin: 0 0 1em;
334 border-collapse: collapse;
335 border: 1px solid #eee;
336 }
337 th, td {
338 text-align: left;
339 vertical-align: top;
340 padding: 0.5em 0.75em;
341 }
342 th {
343 text-align: left;
344 background-color: #e9e9e9;
345 }
346 tr:nth-child(2n+1) > td {
347 background-color: #f5f5f5;
348 }
349 table caption {
350 font-style: italic;
351 margin: 0;
352 padding: 0;
353 text-align: left;
354 }
355 table p {
356 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
357 be allowed within tables more generally, it would be far better to select on a class. */
358 margin: 0;
359 }
360
361 /* pilcrow */
362 a.pilcrow {
363 color: #666; /* Arlen: AHDJ 2019 */
364 text-decoration: none;
365 visibility: hidden;
366 user-select: none;
367 -ms-user-select: none;
368 -o-user-select:none;
369 -moz-user-select: none;
370 -khtml-user-select: none;
371 -webkit-user-select: none;
372 -webkit-touch-callout: none;
373 }
374 @media screen {
375 aside:hover > a.pilcrow,
376 p:hover > a.pilcrow,
377 blockquote:hover > a.pilcrow,
378 div:hover > a.pilcrow,
379 li:hover > a.pilcrow,
380 pre:hover > a.pilcrow {
381 visibility: visible;
382 }
383 a.pilcrow:hover {
384 background-color: transparent;
385 }
386 }
387
388 /* misc */
389 hr {
390 border: 0;
391 border-top: 1px solid #eee;
392 }
393 .bcp14 {
394 font-variant: small-caps;
395 }
396
397 .role {
398 font-variant: all-small-caps;
399 }
400
401 /* info block */
402 #identifiers {
403 margin: 0;
404 font-size: 0.9em;
405 }
406 #identifiers dt {
407 width: 3em;
408 clear: left;
409 }
410 #identifiers dd {
411 float: left;
412 margin-bottom: 0;
413 }
414 #identifiers .authors .author {
415 display: inline-block;
416 margin-right: 1.5em;
417 }
418 #identifiers .authors .org {
419 font-style: italic;
420 }
421
422 /* The prepared/rendered info at the very bottom of the page */
423 .docInfo {
424 color: #666; /* Arlen: WCAG 2019 */
425 font-size: 0.9em;
426 font-style: italic;
427 margin-top: 2em;
428 }
429 .docInfo .prepared {
430 float: left;
431 }
432 .docInfo .prepared {
433 float: right;
434 }
435
436 /* table of contents */
437 #toc {
438 padding: 0.75em 0 2em 0;
439 margin-bottom: 1em;
440 }
441 nav.toc ul {
442 margin: 0 0.5em 0 0;
443 padding: 0;
444 list-style: none;
445 }
446 nav.toc li {
447 line-height: 1.3em;
448 margin: 0.75em 0;
449 padding-left: 1.2em;
450 text-indent: -1.2em;
451 }
452 /* references */
453 .references dt {
454 text-align: right;
455 font-weight: bold;
456 min-width: 7em;
457 }
458 .references dd {
459 margin-left: 8em;
460 overflow: auto;
461 }
462
463 .refInstance {
464 margin-bottom: 1.25em;
465 }
466
467 .references .ascii {
468 margin-bottom: 0.25em;
469 }
470
471 /* index */
472 .index ul {
473 margin: 0 0 0 1em;
474 padding: 0;
475 list-style: none;
476 }
477 .index ul ul {
478 margin: 0;
479 }
480 .index li {
481 margin: 0;
482 text-indent: -2em;
483 padding-left: 2em;
484 padding-bottom: 5px;
485 }
486 .indexIndex {
487 margin: 0.5em 0 1em;
488 }
489 .index a {
490 font-weight: 700;
491 }
492 /* make the index two-column on all but the smallest screens */
493 @media (min-width: 600px) {
494 .index ul {
495 -moz-column-count: 2;
496 -moz-column-gap: 20px;
497 }
498 .index ul ul {
499 -moz-column-count: 1;
500 -moz-column-gap: 0;
501 }
502 }
503
504 /* authors */
505 address.vcard {
506 font-style: normal;
507 margin: 1em 0;
508 }
509
510 address.vcard .nameRole {
511 font-weight: 700;
512 margin-left: 0;
513 }
514 address.vcard .label {
515 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
516 margin: 0.5em 0;
517 }
518 address.vcard .type {
519 display: none;
520 }
521 .alternative-contact {
522 margin: 1.5em 0 1em;
523 }
524 hr.addr {
525 border-top: 1px dashed;
526 margin: 0;
527 color: #ddd;
528 max-width: calc(100% - 16px);
529 }
530
531 /* temporary notes */
532 .rfcEditorRemove::before {
533 position: absolute;
534 top: 0.2em;
535 right: 0.2em;
536 padding: 0.2em;
537 content: "The RFC Editor will remove this note";
538 color: #9e2a00; /* Arlen: WCAG 2019 */
539 background-color: #ffd; /* Arlen: WCAG 2019 */
540 }
541 .rfcEditorRemove {
542 position: relative;
543 padding-top: 1.8em;
544 background-color: #ffd; /* Arlen: WCAG 2019 */
545 border-radius: 3px;
546 }
547 .cref {
548 background-color: #ffd; /* Arlen: WCAG 2019 */
549 padding: 2px 4px;
550 }
551 .crefSource {
552 font-style: italic;
553 }
554 /* alternative layout for smaller screens */
555 @media screen and (max-width: 1023px) {
556 body {
557 padding-top: 2em;
558 }
559 #title {
560 padding: 1em 0;
561 }
562 h1 {
563 font-size: 24px;
564 }
565 h2 {
566 font-size: 20px;
567 margin-top: -18px; /* provide offset for in-page anchors */
568 padding-top: 38px;
569 }
570 #identifiers dd {
571 max-width: 60%;
572 }
573 #toc {
574 position: fixed;
575 z-index: 2;
576 top: 0;
577 right: 0;
578 padding: 0;
579 margin: 0;
580 background-color: inherit;
581 border-bottom: 1px solid #ccc;
582 }
583 #toc h2 {
584 margin: -1px 0 0 0;
585 padding: 4px 0 4px 6px;
586 padding-right: 1em;
587 min-width: 190px;
588 font-size: 1.1em;
589 text-align: right;
590 background-color: #444;
591 color: white;
592 cursor: pointer;
593 }
594 #toc h2::before { /* css hamburger */
595 float: right;
596 position: relative;
597 width: 1em;
598 height: 1px;
599 left: -164px;
600 margin: 6px 0 0 0;
601 background: white none repeat scroll 0 0;
602 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
603 content: "";
604 }
605 #toc nav {
606 display: none;
607 padding: 0.5em 1em 1em;
608 overflow: auto;
609 height: calc(100vh - 48px);
610 border-left: 1px solid #ddd;
611 }
612 }
613
614 /* alternative layout for wide screens */
615 @media screen and (min-width: 1024px) {
616 body {
617 max-width: 724px;
618 margin: 42px auto;
619 padding-left: 1.5em;
620 padding-right: 29em;
621 }
622 #toc {
623 position: fixed;
624 top: 42px;
625 right: 42px;
626 width: 25%;
627 margin: 0;
628 padding: 0 1em;
629 z-index: 1;
630 }
631 #toc h2 {
632 border-top: none;
633 border-bottom: 1px solid #ddd;
634 font-size: 1em;
635 font-weight: normal;
636 margin: 0;
637 padding: 0.25em 1em 1em 0;
638 }
639 #toc nav {
640 display: block;
641 height: calc(90vh - 84px);
642 bottom: 0;
643 padding: 0.5em 0 0;
644 overflow: auto;
645 }
646 img { /* future proofing */
647 max-width: 100%;
648 height: auto;
649 }
650 }
651
652 /* pagination */
653 @media print {
654 body {
655
656 width: 100%;
657 }
658 p {
659 orphans: 3;
660 widows: 3;
661 }
662 #n-copyright-notice {
663 border-bottom: none;
664 }
665 #toc, #n-introduction {
666 page-break-before: always;
667 }
668 #toc {
669 border-top: none;
670 padding-top: 0;
671 }
672 figure, pre {
673 page-break-inside: avoid;
674 }
675 figure {
676 overflow: scroll;
677 }
678 h1, h2, h3, h4, h5, h6 {
679 page-break-after: avoid;
680 }
681 h2+*, h3+*, h4+*, h5+*, h6+* {
682 page-break-before: avoid;
683 }
684 pre {
685 white-space: pre-wrap;
686 word-wrap: break-word;
687 font-size: 10pt;
688 }
689 table {
690 border: 1px solid #ddd;
691 }
692 td {
693 border-top: 1px solid #ddd;
694 }
695 }
696
697 /* This is commented out here, as the string-set: doesn't
698 pass W3C validation currently */
699 /*
700 .ears thead .left {
701 string-set: ears-top-left content();
702 }
703
704 .ears thead .center {
705 string-set: ears-top-center content();
706 }
707
708 .ears thead .right {
709 string-set: ears-top-right content();
710 }
711
712 .ears tfoot .left {
713 string-set: ears-bottom-left content();
714 }
715
716 .ears tfoot .center {
717 string-set: ears-bottom-center content();
718 }
719
720 .ears tfoot .right {
721 string-set: ears-bottom-right content();
722 }
723 */
724
725 @page :first {
726 padding-top: 0;
727 @top-left {
728 content: normal;
729 border: none;
730 }
731 @top-center {
732 content: normal;
733 border: none;
734 }
735 @top-right {
736 content: normal;
737 border: none;
738 }
739 }
740
741 @page {
742 size: A4;
743 margin-bottom: 45mm;
744 padding-top: 20px;
745 /* The follwing is commented out here, but set appropriately by in code, as
746 the content depends on the document */
747 /*
748 @top-left {
749 content: 'Internet-Draft';
750 vertical-align: bottom;
751 border-bottom: solid 1px #ccc;
752 }
753 @top-left {
754 content: string(ears-top-left);
755 vertical-align: bottom;
756 border-bottom: solid 1px #ccc;
757 }
758 @top-center {
759 content: string(ears-top-center);
760 vertical-align: bottom;
761 border-bottom: solid 1px #ccc;
762 }
763 @top-right {
764 content: string(ears-top-right);
765 vertical-align: bottom;
766 border-bottom: solid 1px #ccc;
767 }
768 @bottom-left {
769 content: string(ears-bottom-left);
770 vertical-align: top;
771 border-top: solid 1px #ccc;
772 }
773 @bottom-center {
774 content: string(ears-bottom-center);
775 vertical-align: top;
776 border-top: solid 1px #ccc;
777 }
778 @bottom-right {
779 content: '[Page ' counter(page) ']';
780 vertical-align: top;
781 border-top: solid 1px #ccc;
782 }
783 */
784
785 }
786
787 /* Changes introduced to fix issues found during implementation */
788 /* Make sure links are clickable even if overlapped by following H* */
789 a {
790 z-index: 2;
791 }
792 /* Separate body from document info even without intervening H1 */
793 section {
794 clear: both;
795 }
796
797
798 /* Top align author divs, to avoid names without organization dropping level with org names */
799 .author {
800 vertical-align: top;
801 }
802
803 /* Leave room in document info to show Internet-Draft on one line */
804 #identifiers dt {
805 width: 8em;
806 }
807
808 /* Don't waste quite as much whitespace between label and value in doc info */
809 #identifiers dd {
810 margin-left: 1em;
811 }
812
813 /* Give floating toc a background color (needed when it's a div inside section */
814 #toc {
815 background-color: white;
816 }
817
818 /* Make the collapsed ToC header render white on gray also when it's a link */
819 @media screen and (max-width: 1023px) {
820 #toc h2 a,
821 #toc h2 a:link,
822 #toc h2 a:focus,
823 #toc h2 a:hover,
824 #toc a.toplink,
825 #toc a.toplink:hover {
826 color: white;
827 background-color: #444;
828 text-decoration: none;
829 }
830 }
831
832 /* Give the bottom of the ToC some whitespace */
833 @media screen and (min-width: 1024px) {
834 #toc {
835 padding: 0 0 1em 1em;
836 }
837 }
838
839 /* Style section numbers with more space between number and title */
840 .section-number {
841 padding-right: 0.5em;
842 }
843
844 /* prevent monospace from becoming overly large */
845 tt, code, pre, code {
846 font-size: 95%;
847 }
848
849 /* Fix the height/width aspect for ascii art*/
850 pre.sourcecode,
851 .art-text pre {
852 line-height: 1.12;
853 }
854
855
856 /* Add styling for a link in the ToC that points to the top of the document */
857 a.toplink {
858 float: right;
859 margin-right: 0.5em;
860 }
861
862 /* Fix the dl styling to match the RFC 7992 attributes */
863 dl > dt,
864 dl.dlParallel > dt {
865 float: left;
866 margin-right: 1em;
867 }
868 dl.dlNewline > dt {
869 float: none;
870 }
871
872 /* Provide styling for table cell text alignment */
873 table td.text-left,
874 table th.text-left {
875 text-align: left;
876 }
877 table td.text-center,
878 table th.text-center {
879 text-align: center;
880 }
881 table td.text-right,
882 table th.text-right {
883 text-align: right;
884 }
885
886 /* Make the alternative author contact informatio look less like just another
887 author, and group it closer with the primary author contact information */
888 .alternative-contact {
889 margin: 0.5em 0 0.25em 0;
890 }
891 address .non-ascii {
892 margin: 0 0 0 2em;
893 }
894
895 /* With it being possible to set tables with alignment
896 left, center, and right, { width: 100%; } does not make sense */
897 table {
898 width: auto;
899 }
900
901 /* Avoid reference text that sits in a block with very wide left margin,
902 because of a long floating dt label.*/
903 .references dd {
904 overflow: visible;
905 }
906
907 /* Control caption placement */
908 caption {
909 caption-side: bottom;
910 }
911
912 /* Limit the width of the author address vcard, so names in right-to-left
913 script don't end up on the other side of the page. */
914
915 address.vcard {
916 max-width: 30em;
917 margin-right: auto;
918 }
919
920 /* For address alignment dependent on LTR or RTL scripts */
921 address div.left {
922 text-align: left;
923 }
924 address div.right {
925 text-align: right;
926 }
927
928 /* Provide table alignment support. We can't use the alignX classes above
929 since they do unwanted things with caption and other styling. */
930 table.right {
931 margin-left: auto;
932 margin-right: 0;
933 }
934 table.center {
935 margin-left: auto;
936 margin-right: auto;
937 }
938 table.left {
939 margin-left: 0;
940 margin-right: auto;
941 }
942
943 /* Give the table caption label the same styling as the figcaption */
944 caption a[href] {
945 color: #222;
946 }
947
948 @media print {
949 .toplink {
950 display: none;
951 }
952
953 /* avoid overwriting the top border line with the ToC header */
954 #toc {
955 padding-top: 1px;
956 }
957
958 /* Avoid page breaks inside dl and author address entries */
959 .vcard {
960 page-break-inside: avoid;
961 }
962
963 }
964 /* Tweak the bcp14 keyword presentation */
965 .bcp14 {
966 font-variant: small-caps;
967 font-weight: bold;
968 font-size: 0.9em;
969 }
970 /* Tweak the invisible space above H* in order not to overlay links in text above */
971 h2 {
972 margin-top: -18px; /* provide offset for in-page anchors */
973 padding-top: 31px;
974 }
975 h3 {
976 margin-top: -18px; /* provide offset for in-page anchors */
977 padding-top: 24px;
978 }
979 h4 {
980 margin-top: -18px; /* provide offset for in-page anchors */
981 padding-top: 24px;
982 }
983 /* Float artwork pilcrow to the right */
984 @media screen {
985 .artwork a.pilcrow {
986 display: block;
987 line-height: 0.7;
988 margin-top: 0.15em;
989 }
990 }
991 /* Make pilcrows on dd visible */
992 @media screen {
993 dd:hover > a.pilcrow {
994 visibility: visible;
995 }
996 }
997 /* Make the placement of figcaption match that of a table's caption
998 by removing the figure's added bottom margin */
999 .alignLeft.art-text,
1000 .alignCenter.art-text,
1001 .alignRight.art-text {
1002 margin-bottom: 0;
1003 }
1004 .alignLeft,
1005 .alignCenter,
1006 .alignRight {
1007 margin: 1em 0 0 0;
1008 }
1009 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1010 possibly even requiring a new line */
1011 @media print {
1012 a.pilcrow {
1013 display: none;
1014 }
1015 }
1016 /* Styling for the external metadata */
1017 div#external-metadata {
1018 background-color: #eee;
1019 padding: 0.5em;
1020 margin-bottom: 0.5em;
1021 display: none;
1022 }
1023 div#internal-metadata {
1024 padding: 0.5em; /* to match the external-metadata padding */
1025 }
1026 /* Styling for title RFC Number */
1027 h1#rfcnum {
1028 clear: both;
1029 margin: 0 0 -1em;
1030 padding: 1em 0 0 0;
1031 }
1032 /* Make .olPercent look the same as <ol><li> */
1033 dl.olPercent > dd {
1034 margin-bottom: 0.25em;
1035 min-height: initial;
1036 }
1037 /* Give aside some styling to set it apart */
1038 aside {
1039 border-left: 1px solid #ddd;
1040 margin: 1em 0 1em 2em;
1041 padding: 0.2em 2em;
1042 }
1043 aside > dl,
1044 aside > ol,
1045 aside > ul,
1046 aside > table,
1047 aside > p {
1048 margin-bottom: 0.5em;
1049 }
1050 /* Additional page break settings */
1051 @media print {
1052 figcaption, table caption {
1053 page-break-before: avoid;
1054 }
1055 }
1056 /* Font size adjustments for print */
1057 @media print {
1058 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1059 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1060 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1061 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1062 h4 { font-size: 1em; padding-top: 1.5em; }
1063 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1064 }
1065 /* Sourcecode margin in print, when there's no pilcrow */
1066 @media print {
1067 .artwork,
1068 .sourcecode {
1069 margin-bottom: 1em;
1070 }
1071 }
1072 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1073 table {
1074 min-width: 20em;
1075 }
1076 /* ol type a */
1077 ol.type-a { list-style-type: lower-alpha; }
1078 ol.type-A { list-style-type: upper-alpha; }
1079 ol.type-i { list-style-type: lower-roman; }
1080 ol.type-I { list-style-type: lower-roman; }
1081 /* Apply the print table and row borders in general, on request from the RPC,
1082 and increase the contrast between border and odd row background sligthtly */
1083 table {
1084 border: 1px solid #ddd;
1085 }
1086 td {
1087 border-top: 1px solid #ddd;
1088 }
1089 tr:nth-child(2n+1) > td {
1090 background-color: #f8f8f8;
1091 }
1092 /* Use style rules to govern display of the TOC. */
1093 @media screen and (max-width: 1023px) {
1094 #toc nav { display: none; }
1095 #toc.active nav { display: block; }
1096 }
1097 /* Add support for keepWithNext */
1098 .keepWithNext {
1099 break-after: avoid-page;
1100 break-after: avoid-page;
1101 }
1102 /* Add support for keepWithPrevious */
1103 .keepWithPrevious {
1104 break-before: avoid-page;
1105 }
1106 /* Change the approach to avoiding breaks inside artwork etc. */
1107 figure, pre, table, .artwork, .sourcecode {
1108 break-before: avoid-page;
1109 break-after: auto;
1110 }
1111 /* Avoid breaks between <dt> and <dd> */
1112 dl {
1113 break-before: auto;
1114 break-inside: auto;
1115 }
1116 dt {
1117 break-before: auto;
1118 break-after: avoid-page;
1119 }
1120 dd {
1121 break-before: avoid-page;
1122 break-after: auto;
1123 orphans: 3;
1124 widows: 3
1125 }
1126 span.break, dd.break {
1127 margin-bottom: 0;
1128 min-height: 0;
1129 break-before: auto;
1130 break-inside: auto;
1131 break-after: auto;
1132 }
1133 /* Undo break-before ToC */
1134 @media print {
1135 #toc {
1136 break-before: auto;
1137 }
1138 }
1139 /* Text in compact lists should not get extra bottim margin space,
1140 since that would makes the list not compact */
1141 ul.compact p, .ulCompact p,
1142 ol.compact p, .olCompact p {
1143 margin: 0;
1144 }
1145 /* But the list as a whole needs the extra space at the end */
1146 section ul.compact,
1147 section .ulCompact,
1148 section ol.compact,
1149 section .olCompact {
1150 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1151 }
1152 /* The tt and code background above interferes with for instance table cell
1153 backgrounds. Changed to something a bit more selective. */
1154 tt, code {
1155 background-color: transparent;
1156 }
1157 p tt, p code, li tt, li code {
1158 background-color: #f8f8f8;
1159 }
1160 /* Tweak the pre margin -- 0px doesn't come out well */
1161 pre {
1162 margin-top: 0.5px;
1163 }
1164 /* Tweak the comact list text */
1165 ul.compact, .ulCompact,
1166 ol.compact, .olCompact,
1167 dl.compact, .dlCompact {
1168 line-height: normal;
1169 }
1170 /* Don't add top margin for nested lists */
1171 li > ul, li > ol, li > dl,
1172 dd > ul, dd > ol, dd > dl,
1173 dl > dd > dl {
1174 margin-top: initial;
1175 }
1176 /* Elements that should not be rendered on the same line as a <dt> */
1177 /* This should match the element list in writer.text.TextWriter.render_dl() */
1178 dd > div.artwork:first-child,
1179 dd > aside:first-child,
1180 dd > figure:first-child,
1181 dd > ol:first-child,
1182 dd > div:first-child > pre.sourcecode,
1183 dd > table:first-child,
1184 dd > ul:first-child {
1185 clear: left;
1186 }
1187 /* fix for weird browser behaviour when <dd/> is empty */
1188 dt+dd:empty::before{
1189 content: "\00a0";
1190 }
1191 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1192 li > p {
1193 margin-bottom: 0.5em
1194 }
1195 /* Don't let p margin spill out from inside list items */
1196 li > p:last-of-type {
1197 margin-bottom: 0;
1198 }
1199 </style>
1200 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1201 <link href="https://dx.doi.org/10.17487/rfc9057" rel="alternate">
1202 <link href="urn:issn:2070-1721" rel="alternate">
1203 <link href="https://datatracker.ietf.org/doc/draft-crocker-email-author-04" rel="prev">
1204 </head>
1205 <body>
1206 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1207 <table class="ears">
1208 <thead><tr>
1209 <td class="left">RFC 9057</td>
1210 <td class="center">Email Author Header Field</td>
1211 <td class="right">June 2021</td>
1212 </tr></thead>
1213 <tfoot><tr>
1214 <td class="left">Crocker</td>
1215 <td class="center">Experimental</td>
1216 <td class="right">[Page]</td>
1217 </tr></tfoot>
1218 </table>
1219 <div id="external-metadata" class="document-information"></div>
1220 <div id="internal-metadata" class="document-information">
1221 <dl id="identifiers">
1222 <dt class="label-stream">Stream:</dt>
1223 <dd class="stream">Independent Submission</dd>
1224 <dt class="label-rfc">RFC:</dt>
1225 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9057" class="eref">9057</a></dd>
1226 <dt class="label-category">Category:</dt>
1227 <dd class="category">Experimental</dd>
1228 <dt class="label-published">Published:</dt>
1229 <dd class="published">
1230 <time datetime="2021-06" class="published">June 2021</time>
1231 </dd>
1232 <dt class="label-issn">ISSN:</dt>
1233 <dd class="issn">2070-1721</dd>
1234 <dt class="label-authors">Author:</dt>
1235 <dd class="authors">
1236 <div class="author">
1237 <div class="author-name">D. Crocker</div>
1238 <div class="org">Brandenburg InternetWorking</div>
1239 </div>
1240 </dd>
1241 </dl>
1242 </div>
1243 <h1 id="rfcnum">RFC 9057</h1>
1244 <h1 id="title">Email Author Header Field</h1>
1245 <section id="section-abstract">
1246 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1247 <p id="section-abstract-1">Internet mail defines the From: header field to indicate the
1248 author of the message's content and the Sender: field to
1249 indicate who initially handled the message on the author's
1250 behalf. The Sender: field is optional if it has the same
1251 information as the From: field. This was not a problem until
1252 development of stringent protections on use of the From: field.
1253 It has prompted Mediators, such as mailing lists, to modify the
1254 From: field to circumvent mail rejection caused by those
1255 protections. In effect, the From: field has become dominated by
1256 its role as a handling identifier.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1257 <p id="section-abstract-2"> The current specification augments the altered use of the From:
1258 field by specifying the Author: field, which ensures
1259 identification of the original author of the message and is not
1260 subject to modification by Mediators. This document is published
1261 as an Experimental RFC to assess community interest, functional
1262 efficacy, and technical adequacy.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1263 </section>
1264 <div id="status-of-memo">
1265 <section id="section-boilerplate.1">
1266 <h2 id="name-status-of-this-memo">
1267 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1268 </h2>
1269 <p id="section-boilerplate.1-1">
1270 This document is not an Internet Standards Track specification; it is
1271 published for examination, experimental implementation, and
1272 evaluation.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1273 <p id="section-boilerplate.1-2">
1274 This document defines an Experimental Protocol for the Internet
1275 community. This is a contribution to the RFC Series,
1276 independently of any other RFC stream. The RFC Editor has chosen to publish this
1277 document at its discretion and makes no statement about its value
1278 for implementation or deployment. Documents approved for publication
1279 by the RFC Editor are not candidates for any level of Internet
1280 Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1281 <p id="section-boilerplate.1-3">
1282 Information about the current status of this document, any
1283 errata, and how to provide feedback on it may be obtained at
1284 <span><a href="https://www.rfc-editor.org/info/rfc9057">https://www.rfc-editor.org/info/rfc9057</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1285 </section>
1286 </div>
1287 <div id="copyright">
1288 <section id="section-boilerplate.2">
1289 <h2 id="name-copyright-notice">
1290 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1291 </h2>
1292 <p id="section-boilerplate.2-1">
1293 Copyright (c) 2021 IETF Trust and the persons identified as the
1294 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1295 <p id="section-boilerplate.2-2">
1296 This document is subject to BCP 78 and the IETF Trust's Legal
1297 Provisions Relating to IETF Documents
1298 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1299 publication of this document. Please review these documents
1300 carefully, as they describe your rights and restrictions with
1301 respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1302 </section>
1303 </div>
1304 <div id="toc">
1305 <section id="section-toc.1">
1306 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1307 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1308 </h2>
1309 <nav class="toc"><ul class="ulEmpty compact toc">
1310 <li class="ulEmpty compact toc" id="section-toc.1-1.1">
1311 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1312 </li>
1313 <li class="ulEmpty compact toc" id="section-toc.1-1.2">
1314 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
1315 </li>
1316 <li class="ulEmpty compact toc" id="section-toc.1-1.3">
1317 <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-author-header-field" class="xref">Author Header Field</a></p>
1318 </li>
1319 <li class="ulEmpty compact toc" id="section-toc.1-1.4">
1320 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-discussion" class="xref">Discussion</a></p>
1321 </li>
1322 <li class="ulEmpty compact toc" id="section-toc.1-1.5">
1323 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1324 </li>
1325 <li class="ulEmpty compact toc" id="section-toc.1-1.6">
1326 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1327 </li>
1328 <li class="ulEmpty compact toc" id="section-toc.1-1.7">
1329 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-experimental-goals" class="xref">Experimental Goals</a></p>
1330 </li>
1331 <li class="ulEmpty compact toc" id="section-toc.1-1.8">
1332 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-references" class="xref">References</a></p>
1333 <ul class="toc ulEmpty compact">
1334 <li class="toc ulEmpty compact" id="section-toc.1-1.8.2.1">
1335 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1336 </li>
1337 <li class="toc ulEmpty compact" id="section-toc.1-1.8.2.2">
1338 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1339 </li>
1340 </ul>
1341 </li>
1342 <li class="ulEmpty compact toc" id="section-toc.1-1.9">
1343 <p id="section-toc.1-1.9.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1344 </li>
1345 <li class="ulEmpty compact toc" id="section-toc.1-1.10">
1346 <p id="section-toc.1-1.10.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a></p>
1347 </li>
1348 </ul>
1349 </nav>
1350 </section>
1351 </div>
1352 <section id="section-1">
1353 <h2 id="name-introduction">
1354 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1355 </h2>
1356 <p id="section-1-1">Internet mail conducts asynchronous communication from an author
1357 to one or more recipients and is used for ongoing dialog
1358 amongst them. Email has a long history of serving a wide range
1359 of human uses and styles, within that simple framework, and the
1360 mechanisms for making email robust and safe serve that sole
1361 purpose.<a href="#section-1-1" class="pilcrow">¶</a></p>
1362 <p id="section-1-2"> Internet mail defines the content header's From: field to
1363 indicate the author of the message and the Sender: field to
1364 indicate who initially handled the message on the author's
1365 behalf <span>[<a href="#RFC5322" class="xref">Mail-Fmt</a>]</span>. The Sender: field is optional
1366 if it has the same information as the From: field. That is, when
1367 the Sender: field is absent, the From: field has conflated
1368 semantics as both a handling identifier and a content creator
1369 identifier. These fields were initially defined in <span>[<a href="#RFC0733" class="xref">RFC733</a>]</span>, and making the redundant Sender: field
1370 optional was a small, obvious optimization in the days of
1371 slower communications, expensive storage, and less powerful
1372 computers.<a href="#section-1-2" class="pilcrow">¶</a></p>
1373 <p id="section-1-3">The dual semantics were not a problem until development of
1374 stringent protections on use of the From: field. It has prompted
1375 Mediators, such as mailing lists, to modify the From: field to
1376 circumvent receiver mail rejection caused by those protections.
1377 This affects end-to-end usability of email between the author
1378 and the final recipients, because mail received from the same
1379 author is treated differently by the recipient's software,
1380 depending on what path the message followed.<a href="#section-1-3" class="pilcrow">¶</a></p>
1381 <p id="section-1-4">By way of example, mail originating with:<a href="#section-1-4" class="pilcrow">¶</a></p>
1382 <div class="artwork art-text alignLeft" id="section-1-5">
1383 <pre>
1384 From: Example User &lt;[email protected]&gt;
1385 </pre><a href="#section-1-5" class="pilcrow">¶</a>
1386 </div>
1387 <p id="section-1-6"> which is sent directly to a recipient, will show the
1388 author's display name correctly and can correctly analyze,
1389 filter, and aggregate mail from the author based on their email
1390 address. However, if the author sends through a mailing list and
1391 the mailing list conducts a common form of From: modification
1392 needed to bypass enforcement of stringent authentication
1393 policies, then the received message might instead have a From:
1394 field showing:<a href="#section-1-6" class="pilcrow">¶</a></p>
1395 <div class="artwork art-text alignLeft" id="section-1-7">
1396 <pre>
1397 From: Example User via Example List &lt;[email protected]&gt;
1398 </pre><a href="#section-1-7" class="pilcrow">¶</a>
1399 </div>
1400 <p id="section-1-8"> The change inserts an operational address, for the
1401 Mediator, into the From: field and distorts the field's
1402 display name as a means of recording the modification.<a href="#section-1-8" class="pilcrow">¶</a></p>
1403 <p id="section-1-9">In terms of email identification semantics, this is a profound
1404 change:<a href="#section-1-9" class="pilcrow">¶</a></p>
1405 <ul class="normal">
1406 <li class="normal" id="section-1-10.1">The result is that the recipient's software will see the
1407 message as being from an entirely different author and
1408 will handle it separately, such as for sorting or
1409 filtering.
1410 In effect, the recipient's software will see
1411 the same person's email as being from a different
1412 address; this includes the person's actual address and each of the
1413 mailing lists that person's mail transits.<a href="#section-1-10.1" class="pilcrow">¶</a>
1414 </li>
1415 <li class="normal" id="section-1-10.2">Mediators might create a Reply-To: field with the
1416 original From: field email address. This facilitates
1417 getting replies back to the original author, but it does
1418 nothing to aid other processing or presentation done by
1419 the recipient's Mail User Agent (MUA) based on what it
1420 believes is the author's address or original
1421 display name.
1422 This Reply-To action represents another
1423 knock-on effect (e.g., collateral damage) by
1424 distorting the meaning
1425 of that header field, as well as creating an issue if
1426 the field already exists.<a href="#section-1-10.2" class="pilcrow">¶</a>
1427 </li>
1428 </ul>
1429 <p id="section-1-11">In effect, the From: field has become dominated by its role as a
1430 handling identifier. The current specification augments this
1431 altered use of the From: field by specifying the Author: field,
1432 which identifies the original author of the message and is not
1433 subject to modification by Mediators.<a href="#section-1-11" class="pilcrow">¶</a></p>
1434 <p id="section-1-12">While it might be cleanest to move towards more reliable use of
1435 the Sender: field and then to target it as the focus of
1436 authentication concerns, enhancement of existing standards works
1437 best with incremental additions, rather than with efforts at
1438 replacement. To that end, this specification provides a means of
1439 supplying author information that is not subject to modification
1440 by processes seeking to enforce stringent authentication.<a href="#section-1-12" class="pilcrow">¶</a></p>
1441 <p id="section-1-13">This version is published as an Experimental RFC to assess community
1442 interest, functional efficacy, and technical adequacy. See <a href="#experiment" class="xref">Section 7</a>.<a href="#section-1-13" class="pilcrow">¶</a></p>
1443 </section>
1444 <section id="section-2">
1445 <h2 id="name-terminology">
1446 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1447 </h2>
1448 <p id="section-2-1">Terminology and architectural details in this document are
1449 incorporated from <span>[<a href="#RFC5598" class="xref">Mail-Arch</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p>
1450 <p id="section-2-2">
1451 Normative language, per <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>:<a href="#section-2-2" class="pilcrow">¶</a></p>
1452 <p id="section-2-3">
1453 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>",
1454 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
1455 described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
1456 when, and only when, they appear in all capitals, as shown here.<a href="#section-2-3" class="pilcrow">¶</a></p>
1457 </section>
1458 <section id="section-3">
1459 <h2 id="name-author-header-field">
1460 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-author-header-field" class="section-name selfRef">Author Header Field</a>
1461 </h2>
1462 <p id="section-3-1">Author: is a new message header field being defined. It has the same
1463 syntax as the From: header field <span>[<a href="#RFC5322" class="xref">Mail-Fmt</a>]</span>. As
1464 with the original and primary intent for the From: field, the
1465 Author: field is intended to contain the email address of the author of
1466 the message content. It also can contain the displayable human
1467 name of the author.<a href="#section-3-1" class="pilcrow">¶</a></p>
1468 <p id="section-3-2">The <span>[<a href="#RFC5234" class="xref">ABNF</a>]</span> for the field's syntax is:<a href="#section-3-2" class="pilcrow">¶</a></p>
1469 <div id="section-3-3">
1470 <pre class="sourcecode lang-abnf">
1471 author = "Author:" mailbox-list CRLF
1472 </pre><a href="#section-3-3" class="pilcrow">¶</a>
1473 </div>
1474 <p id="section-3-4">which echos the syntax for the From: header field.<a href="#section-3-4" class="pilcrow">¶</a></p>
1475 <p id="section-3-5"> This header field can be added as part of the original message
1476 creation process, or it can be added later, by a Mediator, to
1477 preserve the original author information from the From:
1478 field.<a href="#section-3-5" class="pilcrow">¶</a></p>
1479 <p id="section-3-6"> The goal of the Author: field is to reflect information about
1480 the original author. However, it is possible that the author's
1481 MUA or Mail Submission Agent (MSA) will not create it but that
1482 a Mediator might know it will be modifying the From: field and
1483 wish to preserve the author information. Hence, it needs to be
1484 allowed to create the Author: field for this if the field does
1485 not already exist.<a href="#section-3-6" class="pilcrow">¶</a></p>
1486 <p id="section-3-7">Processing of the Author: field follows these rules:<a href="#section-3-7" class="pilcrow">¶</a></p>
1487 <ul class="normal">
1488 <li class="normal" id="section-3-8.1">If an Author: field already exists, a new one <span class="bcp14">MUST NOT</span> be
1489 created, and the existing one <span class="bcp14">MUST NOT</span> be modified.<a href="#section-3-8.1" class="pilcrow">¶</a>
1490 </li>
1491 <li class="normal" id="section-3-8.2">An author's MUA or MSA <span class="bcp14">MAY</span> create an Author: field, and
1492 its value <span class="bcp14">MUST</span> be identical to the value in the From:
1493 field.<a href="#section-3-8.2" class="pilcrow">¶</a>
1494 </li>
1495 <li class="normal" id="section-3-8.3">A Mediator <span class="bcp14">MAY</span> create an Author: field if one does not
1496 already exist, and this new field's value <span class="bcp14">MUST</span> be
1497 identical to the value of the From: field at the time
1498 the Mediator received the message (and before the
1499 Mediator causes any changes to the From: field).<a href="#section-3-8.3" class="pilcrow">¶</a>
1500 </li>
1501 </ul>
1502 </section>
1503 <section id="section-4">
1504 <h2 id="name-discussion">
1505 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-discussion" class="section-name selfRef">Discussion</a>
1506 </h2>
1507 <p id="section-4-1">The Author: header field, here, is intended for creation during
1508 message generation or during mediation. It is intended for use
1509 by recipient MUAs, as they typically use the From: field. In
1510 that regard, it would be reasonable for an MUA that would
1511 normally organize, filter, or display information based on the
1512 From: field to give the Author: header field preference.<a href="#section-4-1" class="pilcrow">¶</a></p>
1513 <p id="section-4-2">Original-From: is a similar header field referenced in <span>[<a href="#RFC5703" class="xref">RFC5703</a>]</span>. It is registered with IANA, which cites
1514 <span>[<a href="#RFC5703" class="xref">RFC5703</a>]</span> as the controlling source for the entry. However, that
1515 document only has a minimal definition for the field. Also, the
1516 field is solely intended for use by Mediators to preserve
1517 information from a modified From: field. The current specification can
1518 be used during either origination or mediation.<a href="#section-4-2" class="pilcrow">¶</a></p>
1519 <p id="section-4-3">While the basic model of email header fields is highly
1520 extensible, there well might be implementation and usability
1521 considerations for carrying this field through to end users,
1522 such as via <span>[<a href="#RFC3501" class="xref">IMAP</a>]</span>.<a href="#section-4-3" class="pilcrow">¶</a></p>
1523 <p id="section-4-4">Obviously, any security-related processing of a message needs to
1524 distinguish the From: field from the Author: field and treat their information
1525 accordingly.<a href="#section-4-4" class="pilcrow">¶</a></p>
1526 </section>
1527 <section id="section-5">
1528 <h2 id="name-security-considerations">
1529 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1530 </h2>
1531 <p id="section-5-1">Any header field containing identification information is a
1532 source of security and privacy concerns, especially when the
1533 information pertains to content authorship. Generally, the
1534 handling of the Author: header field needs to receive scrutiny
1535 and care, comparable to that given to the From: header field,
1536 but preferably not in a way that defeats its utility.<a href="#section-5-1" class="pilcrow">¶</a></p>
1537 <p id="section-5-2">Given the semantics of the Author: header field, it is easy to believe that use
1538 of this field will create a new attack vector for tricking
1539 end users. However (and perhaps surprisingly), for all of the
1540 real and serious demonstrations of users being tricked by
1541 deceptive or false content in a message, there is no evidence
1542 that problematic content in a header field, which is providing
1543 information about message's author, directly contributes to
1544 differential and problematic behavior by the end user. (The
1545 presents an obvious exercise for the reader to find credible,
1546 documented evidence.)<a href="#section-5-2" class="pilcrow">¶</a></p>
1547 </section>
1548 <div id="iana_considerations">
1549 <section id="section-6">
1550 <h2 id="name-iana-considerations">
1551 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1552 </h2>
1553 <p id="section-6-1">IANA has registered the Author: header field, per
1554 <span>[<a href="#RFC3864" class="xref">RFC3864</a>]</span>, in the "Provisional Message
1555 Header Field Names" registry:<a href="#section-6-1" class="pilcrow">¶</a></p>
1556 <span class="break"></span><dl class="dlParallel dlCompact" id="section-6-2">
1557 <dt id="section-6-2.1">Header field name:</dt>
1558 <dd style="margin-left: 1.5em" id="section-6-2.2">Author<a href="#section-6-2.2" class="pilcrow">¶</a>
1559 </dd>
1560 <dd class="break"></dd>
1561 <dt id="section-6-2.3">Applicable protocol:</dt>
1562 <dd style="margin-left: 1.5em" id="section-6-2.4">mail<a href="#section-6-2.4" class="pilcrow">¶</a>
1563 </dd>
1564 <dd class="break"></dd>
1565 <dt id="section-6-2.5">Status:</dt>
1566 <dd style="margin-left: 1.5em" id="section-6-2.6">Provisional<a href="#section-6-2.6" class="pilcrow">¶</a>
1567 </dd>
1568 <dd class="break"></dd>
1569 <dt id="section-6-2.7">Author/Change controller:</dt>
1570 <dd style="margin-left: 1.5em" id="section-6-2.8">Dave Crocker
1571 &lt;[email protected]&gt;<a href="#section-6-2.8" class="pilcrow">¶</a>
1572 </dd>
1573 <dd class="break"></dd>
1574 <dt id="section-6-2.9">Specification document(s):</dt>
1575 <dd style="margin-left: 1.5em" id="section-6-2.10">RFC 9057<a href="#section-6-2.10" class="pilcrow">¶</a>
1576 </dd>
1577 <dd class="break"></dd>
1578 </dl>
1579 </section>
1580 </div>
1581 <div id="experiment">
1582 <section id="section-7">
1583 <h2 id="name-experimental-goals">
1584 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-experimental-goals" class="section-name selfRef">Experimental Goals</a>
1585 </h2>
1586 <p id="section-7-1">Given that the semantics of this field echo the long-standing
1587 From: header field, the basic mechanics of the field's creation
1588 and use are well understood. Points of concern, therefore, are
1589 with possible interactions with the existing From: field,
1590 anti-abuse systems, and MUA behavior, along with basic
1591 market acceptance. So the questions to answer while the header
1592 field has experimental status are:<a href="#section-7-1" class="pilcrow">¶</a></p>
1593 <ul class="normal">
1594 <li class="normal" id="section-7-2.1">Is there demonstrated interest by MUA developers?<a href="#section-7-2.1" class="pilcrow">¶</a>
1595 </li>
1596 <li class="normal" id="section-7-2.2">If MUA developers add this capability, is it used by
1597 authors?<a href="#section-7-2.2" class="pilcrow">¶</a>
1598 </li>
1599 <li class="normal" id="section-7-2.3">Does the presence of the Author: field, in combination
1600 with the From: field, create any operational problems,
1601 especially for recipients?<a href="#section-7-2.3" class="pilcrow">¶</a>
1602 </li>
1603 <li class="normal" id="section-7-2.4">Does the presence of the Author: field demonstrate
1604 additional security issues?<a href="#section-7-2.4" class="pilcrow">¶</a>
1605 </li>
1606 <li class="normal" id="section-7-2.5">Does the presence of the Author: field engender
1607 problematic behavior by anti-abuse software, such as
1608 defeating its utility?<a href="#section-7-2.5" class="pilcrow">¶</a>
1609 </li>
1610 </ul>
1611 </section>
1612 </div>
1613 <section id="section-8">
1614 <h2 id="name-references">
1615 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a>
1616 </h2>
1617 <section id="section-8.1">
1618 <h3 id="name-normative-references">
1619 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
1620 </h3>
1621 <dl class="references">
1622 <dt id="RFC5234">[ABNF]</dt>
1623 <dd>
1624 <span class="refAuthor">Crocker, D., Ed.</span> and <span class="refAuthor">P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>&gt;</span>. </dd>
1625 <dd class="break"></dd>
1626 <dt id="RFC5598">[Mail-Arch]</dt>
1627 <dd>
1628 <span class="refAuthor">Crocker, D.</span>, <span class="refTitle">"Internet Mail Architecture"</span>, <span class="seriesInfo">RFC 5598</span>, <span class="seriesInfo">DOI 10.17487/RFC5598</span>, <time datetime="2009-07" class="refDate">July 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5598">https://www.rfc-editor.org/info/rfc5598</a>&gt;</span>. </dd>
1629 <dd class="break"></dd>
1630 <dt id="RFC5322">[Mail-Fmt]</dt>
1631 <dd>
1632 <span class="refAuthor">Resnick, P., Ed.</span>, <span class="refTitle">"Internet Message Format"</span>, <span class="seriesInfo">RFC 5322</span>, <span class="seriesInfo">DOI 10.17487/RFC5322</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5322">https://www.rfc-editor.org/info/rfc5322</a>&gt;</span>. </dd>
1633 <dd class="break"></dd>
1634 <dt id="RFC2119">[RFC2119]</dt>
1635 <dd>
1636 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
1637 <dd class="break"></dd>
1638 <dt id="RFC3864">[RFC3864]</dt>
1639 <dd>
1640 <span class="refAuthor">Klyne, G.</span>, <span class="refAuthor">Nottingham, M.</span>, and <span class="refAuthor">J. Mogul</span>, <span class="refTitle">"Registration Procedures for Message Header Fields"</span>, <span class="seriesInfo">BCP 90</span>, <span class="seriesInfo">RFC 3864</span>, <span class="seriesInfo">DOI 10.17487/RFC3864</span>, <time datetime="2004-09" class="refDate">September 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3864">https://www.rfc-editor.org/info/rfc3864</a>&gt;</span>. </dd>
1641 <dd class="break"></dd>
1642 <dt id="RFC8174">[RFC8174]</dt>
1643 <dd>
1644 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
1645 <dd class="break"></dd>
1646 </dl>
1647 </section>
1648 <section id="section-8.2">
1649 <h3 id="name-informative-references">
1650 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
1651 </h3>
1652 <dl class="references">
1653 <dt id="RFC3501">[IMAP]</dt>
1654 <dd>
1655 <span class="refAuthor">Crispin, M.</span>, <span class="refTitle">"INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"</span>, <span class="seriesInfo">RFC 3501</span>, <span class="seriesInfo">DOI 10.17487/RFC3501</span>, <time datetime="2003-03" class="refDate">March 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3501">https://www.rfc-editor.org/info/rfc3501</a>&gt;</span>. </dd>
1656 <dd class="break"></dd>
1657 <dt id="RFC5703">[RFC5703]</dt>
1658 <dd>
1659 <span class="refAuthor">Hansen, T.</span> and <span class="refAuthor">C. Daboo</span>, <span class="refTitle">"Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure"</span>, <span class="seriesInfo">RFC 5703</span>, <span class="seriesInfo">DOI 10.17487/RFC5703</span>, <time datetime="2009-10" class="refDate">October 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5703">https://www.rfc-editor.org/info/rfc5703</a>&gt;</span>. </dd>
1660 <dd class="break"></dd>
1661 <dt id="RFC0733">[RFC733]</dt>
1662 <dd>
1663 <span class="refAuthor">Crocker, D.</span>, <span class="refAuthor">Vittal, J.</span>, <span class="refAuthor">Pogran, K.</span>, and <span class="refAuthor">D. Henderson</span>, <span class="refTitle">"Standard for the format of ARPA network text messages"</span>, <span class="seriesInfo">RFC 733</span>, <span class="seriesInfo">DOI 10.17487/RFC0733</span>, <time datetime="1977-11" class="refDate">November 1977</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc733">https://www.rfc-editor.org/info/rfc733</a>&gt;</span>. </dd>
1664 <dd class="break"></dd>
1665 </dl>
1666 </section>
1667 </section>
1668 <section id="section-appendix.a">
1669 <h2 id="name-acknowledgements">
1670 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
1671 </h2>
1672 <p id="section-appendix.a-1">The idea for this field was prompted by discussions in the IETF's
1673 DMARC Working Group, with participation from: <span class="contact-name">Benny Lyne Amorsen</span>, <span class="contact-name">Kurt Anderson</span>,
1674 <span class="contact-name">Laura Atkins</span>, <span class="contact-name">Adrian Farrel</span>,
1675 <span class="contact-name">Murray S. Kucherawy</span>, <span class="contact-name">Mike Hammer</span>,
1676 <span class="contact-name">John Levine</span>, <span class="contact-name">Alexey Melnikov</span>,
1677 <span class="contact-name">Jesse Thompson</span>, and <span class="contact-name">Alessandro Vesely</span>.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
1678 </section>
1679 <div id="authors-addresses">
1680 <section id="section-appendix.b">
1681 <h2 id="name-authors-address">
1682 <a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
1683 </h2>
1684 <address class="vcard">
1685 <div dir="auto" class="left"><span class="fn nameRole">Dave Crocker</span></div>
1686 <div dir="auto" class="left"><span class="org">Brandenburg InternetWorking</span></div>
1687 <div class="email">
1688 <span>Email:</span>
1689 <a href="mailto:[email protected]" class="email">[email protected]</a>
1690 </div>
1691 </address>
1692 </section>
1693 </div>
1694 <script>const toc = document.getElementById("toc");
1695 toc.querySelector("h2").addEventListener("click", e => {
1696 toc.classList.toggle("active");
1697 });
1698 toc.querySelector("nav").addEventListener("click", e => {
1699 toc.classList.remove("active");
1700 });
1701 </script>
1702 </body>
1703 </html>