juga
/
internet-drafts
forked from pEp.foundation/internet-drafts
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

revert last commit (was for testing new script)

master
Bernie Hoeneisen 2019-11-04 23:24:47 +01:00
parent 9874186c81
commit de6778fca3
5 changed files with 2 additions and 1774 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
forwarded-no/Makefile
View File

@ -3,7 +3,7 @@
DATE := $(shell date +%Y%m%d)
NAME := draft-melnikov-iana-reg-forwarded
REV := 03
REV := 01
DRAFT := $(NAME)-$(REV)
OUTPUTS = $(DRAFT).xml $(DRAFT).txt $(DRAFT).html
@ -48,7 +48,4 @@ publish:
clean:
rm -f $(OUTPUTS)
distclean:
rm -f -r $(NAME)-* .refcache
.PHONY: clean all

771
forwarded-no/archive/draft-melnikov-iana-reg-forwarded-02.html
View File

@ -1,771 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>IANA Registration of Content-Type Header Field Parameter 'forwarded'</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents">
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction">
<link href="#rfc.section.1.1" rel="Chapter" title="1.1 Use Cases">
<link href="#rfc.section.1.2" rel="Chapter" title="1.2 Implementations">
<link href="#rfc.section.1.3" rel="Chapter" title="1.3 Requirements Language">
<link href="#rfc.section.1.4" rel="Chapter" title="1.4 Terms">
<link href="#rfc.section.2" rel="Chapter" title="2 Specification">
<link href="#rfc.section.3" rel="Chapter" title="3 Example">
<link href="#rfc.section.4" rel="Chapter" title="4 Security Considerations">
<link href="#rfc.section.5" rel="Chapter" title="5 Privacy Considerations">
<link href="#rfc.section.6" rel="Chapter" title="6 IANA Considerations">
<link href="#rfc.section.7" rel="Chapter" title="7 Acknowledgments">
<link href="#rfc.references" rel="Chapter" title="8 References">
<link href="#rfc.references.1" rel="Chapter" title="8.1 Normative References">
<link href="#rfc.references.2" rel="Chapter" title="8.2 Informative References">
<link href="#rfc.appendix.A" rel="Chapter" title="A Additional Example (pEp)">
<link href="#rfc.appendix.B" rel="Chapter" title="B Document Changelog">
<link href="#rfc.appendix.C" rel="Chapter" title="C Open Issues">
<link href="#rfc.authors" rel="Chapter">
<meta name="generator" content="xml2rfc version 2.9.6 - https://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Melnikov, A. and B. Hoeneisen" />
<meta name="dct.identifier" content="urn:ietf:id:draft-melnikov-iana-reg-forwarded-02" />
<meta name="dct.issued" scheme="ISO8601" content="2019-11-04" />
<meta name="dct.abstract" content="This document defines a new Content-Type header field parameter named &#8220;forwarded&#8221; for &#8220;message/rfc822&#8221; and &#8220;message/global&#8221; media types, and its registration with IANA." />
<meta name="description" content="This document defines a new Content-Type header field parameter named &#8220;forwarded&#8221; for &#8220;message/rfc822&#8221; and &#8220;message/global&#8221; media types, and its registration with IANA." />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left">Network Working Group</td>
<td class="right">A. Melnikov</td>
</tr>
<tr>
<td class="left">Internet-Draft</td>
<td class="right">Isode Ltd</td>
</tr>
<tr>
<td class="left">Intended status: Informational</td>
<td class="right">B. Hoeneisen</td>
</tr>
<tr>
<td class="left">Expires: May 7, 2020</td>
<td class="right">pEp Foundation</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">November 04, 2019</td>
</tr>
</tbody>
</table>
<p class="title">IANA Registration of Content-Type Header Field Parameter 'forwarded'<br />
<span class="filename">draft-melnikov-iana-reg-forwarded-02</span></p>
<h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
<p>This document defines a new Content-Type header field parameter named &#8220;forwarded&#8221; for &#8220;message/rfc822&#8221; and &#8220;message/global&#8221; media types, and its registration with IANA.</p>
<h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on May 7, 2020.</p>
<h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
<p>Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a>
</li>
<ul><li>1.1. <a href="#rfc.section.1.1">Use Cases</a>
</li>
<li>1.2. <a href="#rfc.section.1.2">Implementations</a>
</li>
<li>1.3. <a href="#rfc.section.1.3">Requirements Language</a>
</li>
<li>1.4. <a href="#rfc.section.1.4">Terms</a>
</li>
</ul><li>2. <a href="#rfc.section.2">Specification</a>
</li>
<li>3. <a href="#rfc.section.3">Example</a>
</li>
<li>4. <a href="#rfc.section.4">Security Considerations</a>
</li>
<li>5. <a href="#rfc.section.5">Privacy Considerations</a>
</li>
<li>6. <a href="#rfc.section.6">IANA Considerations</a>
</li>
<li>7. <a href="#rfc.section.7">Acknowledgments</a>
</li>
<li>8. <a href="#rfc.references">References</a>
</li>
<ul><li>8.1. <a href="#rfc.references.1">Normative References</a>
</li>
<li>8.2. <a href="#rfc.references.2">Informative References</a>
</li>
</ul><li>Appendix A. <a href="#rfc.appendix.A">Additional Example (pEp)</a>
</li>
<li>Appendix B. <a href="#rfc.appendix.B">Document Changelog</a>
</li>
<li>Appendix C. <a href="#rfc.appendix.C">Open Issues</a>
</li>
<li><a href="#rfc.authors">Authors' Addresses</a>
</li>
</ul>
<h1 id="rfc.section.1">
<a href="#rfc.section.1">1.</a> <a href="#introduction" id="introduction">Introduction</a>
</h1>
<p id="rfc.section.1.p.1">This document defines a new Content-Type header field parameter <a href="#RFC2045" class="xref">[RFC2045]</a> for &#8220;message/rfc822&#8221; and &#8220;message/global&#8221; <a href="#RFC6532" class="xref">[RFC6532]</a> media types with name &#8220;forwarded&#8221;. The parameter value is case- insensitive and can be either &#8220;yes&#8221; or &#8220;no&#8221;. Setting the value to &#8220;no&#8221; is meaningful when used within S&#8203;/&#8203;MIME or PGP/MIME signed or encrypted body parts (cf. <a href="#I-D.ietf-lamps-header-protection-requirements" class="xref">[I-D.ietf-lamps-header-protection-requirements]</a>. The value &#8220;yes&#8221; means that the message nested inside &#8220;message/rfc822&#8221; (or &#8220;message/global&#8221;) is a simple forwarded message. If the parameter is missing, the default assumption is the message has been forwarded.</p>
<h1 id="rfc.section.1.1">
<a href="#rfc.section.1.1">1.1.</a> <a href="#use-cases" id="use-cases">Use Cases</a>
</h1>
<p id="rfc.section.1.1.p.1">Two use cases have been discovered so far:</p>
<p></p>
<ol>
<li>This parameter indicates whether a nested message is signed and/or encrypted (S&#8203;/&#8203;MIME or PGP/MIME), which tells the receiving side how to display the message to the user. Currently, many email clients display &#8220;weird artefacts&#8221; to users due to this missing information.</li>
<li>This parameter indicates to mailing lists which email messages are forwarded, and which are signed and/or encrypted (S&#8203;/&#8203;MIME or PGP/MIME), and how to handle these respective messages.</li>
</ol>
<h1 id="rfc.section.1.2">
<a href="#rfc.section.1.2">1.2.</a> <a href="#implementations" id="implementations">Implementations</a>
</h1>
<p id="rfc.section.1.2.p.1">At this time, there are two known email systems which use this Content-Type header field parameter:</p>
<p></p>
<ol>
<li>Isode with S&#8203;/&#8203;MIME <a href="#RFC8551" class="xref">[RFC8551]</a>
</li>
<li>pEp with PGP/MIME <a href="#I-D.birk-pep" class="xref">[I-D.birk-pep]</a>
</li>
</ol>
<h1 id="rfc.section.1.3">
<a href="#rfc.section.1.3">1.3.</a> <a href="#requirements-language" id="requirements-language">Requirements Language</a>
</h1>
<p id="rfc.section.1.3.p.1">The key words &#8220;MUST&#8221;, &#8220;MUST NOT&#8221;, &#8220;REQUIRED&#8221;, &#8220;SHALL&#8221;, &#8220;SHALL NOT&#8221;, &#8220;SHOULD&#8221;, &#8220;SHOULD NOT&#8221;, &#8220;RECOMMENDED&#8221;, &#8220;MAY&#8221;, and &#8220;OPTIONAL&#8221; in this document are to be interpreted as described in <a href="#RFC2119" class="xref">[RFC2119]</a>.</p>
<h1 id="rfc.section.1.4">
<a href="#rfc.section.1.4">1.4.</a> <a href="#terms" id="terms">Terms</a>
</h1>
<p id="rfc.section.1.4.p.1">The following terms are defined for the scope of this document:</p>
<p></p>
<ul>
<li>Header Field (HF): cf. <a href="#RFC5322" class="xref">[RFC5322]</a>
</li>
<li>Header Section (HS): cf. <a href="#RFC5322" class="xref">[RFC5322]</a>
</li>
</ul>
<h1 id="rfc.section.2">
<a href="#rfc.section.2">2.</a> <a href="#specification" id="specification">Specification</a>
</h1>
<p id="rfc.section.2.p.1">This section defines the new &#8220;forwarded&#8221; Content-Type header field parameter.</p>
<p id="rfc.section.2.p.2">The Content-Type header field parameter &#8220;forwarded&#8221; may assume three values:</p>
<p></p>
<ul>
<li>&#8220;yes&#8221;: The email message contained in the MIME part is a forwarded message. A MUA (Mail User Agent) that is forwarding a message should add a Content-Type header field parameter &#8220;forwarded=yes&#8221;.</li>
<li>&#8220;no&#8221;: The email message contained in the MIME part is a encapsulated email message that has been signed and/or encrypted for header protection. MUAs SHOULD add a Content-Type header field parameter &#8220;forwarded=no&#8221; to indicate the message is not forwarded, but encapsulated for header protection (cf. <a href="#I-D.ietf-lamps-header-protection-requirements" class="xref">[I-D.ietf-lamps-header-protection-requirements]</a>).</li>
<li>absent: If the MUA has no information to determine whether an email message is forwarded or encapsulated, it omits the &#8220;forwarded&#8221; Content-Type header field parameter. A receiving MUAs default behavior is to assume the email message contained in the MIME part is a forwarded message.</li>
</ul>
<h1 id="rfc.section.3">
<a href="#rfc.section.3">3.</a> <a href="#example" id="example">Example</a>
</h1>
<p id="rfc.section.3.p.1">The following example shows the usage of the Content-Type header field parameter &#8220;forwarded&#8221; for an email message that is not forwarded, but encapsulated in another email message.</p>
<pre>
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
Message-ID: &lt;e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net&gt;
Subject: Meeting at my place
From: "Alexey Melnikov" &lt;alexey.melnikov@example.net&gt;
MIME-Version: 1.0
Content-Type: multipart/signed; charset=us-ascii; micalg=sha1;
protocol="application/pkcs7-signature";
boundary=.cbe16d2a-e1a3-4220-b821-38348fc97237
This is a multipart message in MIME format.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Type: message/rfc822; forwarded=no
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
From: "Alexey Melnikov" &lt;alexey.melnikov@example.net&gt;
Message-ID: &lt;e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net&gt;
MIME-Version: 1.0
MMHS-Primary-Precedence: 3
Subject: Meeting at my place
To: somebody@example.net
X-Mailer: Example Mailer
Content-Type: text/plain; charset=us-ascii
This is an important message that I don't want to be modified.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature
[[base-64 encoded signature]]
--.cbe16d2a-e1a3-4220-b821-38348fc97237--
</pre>
<p><a href="#additional-example" class="xref">Appendix A</a> contains an additional example on the usage of the Content-Type header field parameter &#8220;forwarded&#8221; as used by pEp <a href="#I-D.birk-pep" class="xref">[I-D.birk-pep]</a>.</p>
<h1 id="rfc.section.4">
<a href="#rfc.section.4">4.</a> <a href="#security-considerations" id="security-considerations">Security Considerations</a>
</h1>
<p id="rfc.section.4.p.1">This document does not define a new protocol, and thus does not create new security concerns in and of itself.</p>
<h1 id="rfc.section.5">
<a href="#rfc.section.5">5.</a> <a href="#privacy-considerations" id="privacy-considerations">Privacy Considerations</a>
</h1>
<p id="rfc.section.5.p.1">This document does not introduce any new issues regarding Privacy.</p>
<h1 id="rfc.section.6">
<a href="#rfc.section.6">6.</a> <a href="#iana-considerations" id="iana-considerations">IANA Considerations</a>
</h1>
<p id="rfc.section.6.p.1">This document requests IANA to register the Content-Type header field parameter <a href="#RFC2045" class="xref">[RFC2045]</a> with name &#8220;forwarded&#8221; for &#8220;message/rfc822&#8221; and &#8220;message/global&#8221; media types as specified in <a href="#specification" class="xref">Section 2</a> of this document.</p>
<h1 id="rfc.section.7">
<a href="#rfc.section.7">7.</a> <a href="#acknowledgments" id="acknowledgments">Acknowledgments</a>
</h1>
<p id="rfc.section.7.p.1">The authors would like to thank the following people who have provided helpful comments and suggestions for this document: David Wilson, Kelly Bristol, Krista Bennett, Robert Williams, Steve Kille, and Wei Chuang.</p>
<p id="rfc.section.7.p.2">David Wilson came up with the idea of defining a new Content-Type header field parameter to distinguish forwarded messages from inner header field protection constructs.</p>
<h1 id="rfc.references">
<a href="#rfc.references">8.</a> References</h1>
<h1 id="rfc.references.1">
<a href="#rfc.references.1">8.1.</a> Normative References</h1>
<table><tbody>
<tr>
<td class="reference"><b id="RFC2045">[RFC2045]</b></td>
<td class="top">
<a>Freed, N.</a> and <a>N. Borenstein</a>, "<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>", RFC 2045, DOI 10.17487/RFC2045, November 1996.</td>
</tr>
<tr>
<td class="reference"><b id="RFC2119">[RFC2119]</b></td>
<td class="top">
<a>Bradner, S.</a>, "<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.</td>
</tr>
<tr>
<td class="reference"><b id="RFC5322">[RFC5322]</b></td>
<td class="top">
<a>Resnick, P.</a>, "<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>", RFC 5322, DOI 10.17487/RFC5322, October 2008.</td>
</tr>
<tr>
<td class="reference"><b id="RFC8551">[RFC8551]</b></td>
<td class="top">
<a>Schaad, J.</a>, <a>Ramsdell, B.</a> and <a>S. Turner</a>, "<a href="https://tools.ietf.org/html/rfc8551">Secure/Multipurpose Internet Mail Extensions (S&#8203;/&#8203;MIME) Version 4.0 Message Specification</a>", RFC 8551, DOI 10.17487/RFC8551, April 2019.</td>
</tr>
</tbody></table>
<h1 id="rfc.references.2">
<a href="#rfc.references.2">8.2.</a> Informative References</h1>
<table><tbody>
<tr>
<td class="reference"><b id="I-D.birk-pep">[I-D.birk-pep]</b></td>
<td class="top">
<a>Marques, H.</a>, <a>Luck, C.</a> and <a>B. Hoeneisen</a>, "<a href="https://tools.ietf.org/html/draft-birk-pep-04">pretty Easy privacy (pEp): Privacy by Default</a>", Internet-Draft draft-birk-pep-04, July 2019.</td>
</tr>
<tr>
<td class="reference"><b id="I-D.ietf-lamps-header-protection-requirements">[I-D.ietf-lamps-header-protection-requirements]</b></td>
<td class="top">
<a>Melnikov, A.</a> and <a>B. Hoeneisen</a>, "<a href="https://tools.ietf.org/html/draft-ietf-lamps-header-protection-requirements-01">Problem Statement and Requirements for Header Protection</a>", Internet-Draft draft-ietf-lamps-header-protection-requirements-01, October 2019.</td>
</tr>
<tr>
<td class="reference"><b id="RFC6532">[RFC6532]</b></td>
<td class="top">
<a>Yang, A.</a>, <a>Steele, S.</a> and <a>N. Freed</a>, "<a href="https://tools.ietf.org/html/rfc6532">Internationalized Email Headers</a>", RFC 6532, DOI 10.17487/RFC6532, February 2012.</td>
</tr>
</tbody></table>
<h1 id="rfc.appendix.A">
<a href="#rfc.appendix.A">Appendix A.</a> <a href="#additional-example" id="additional-example">Additional Example (pEp)</a>
</h1>
<p id="rfc.section.A.p.1">The following example shows the usage of the Content-Type header field parameter &#8220;forwarded&#8221; as used by pEp <a href="#I-D.birk-pep" class="xref">[I-D.birk-pep]</a> in an email message (after decryption). The inner email message was not forwarded, but encapsulated in another email message.</p>
<pre>
Message-ID: &lt;pEp.PVUYXR.CEB1A-47AC-4B4D-AC1B-F8F02D49D@example.org&gt;
From: Alice Spivak Hyatt &lt;alice@example.org&gt;
To: Carol Burnett &lt;carol@example.net&gt;
Subject: pEp
[...]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="238e1f2946e87ccd3d1b58ba507ed7ab"
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline; filename="msg.txt"
[[ User-Information, e.g. "If you are seeing this message, your
client does not support raising message attachments. Please click
on the message attachment to view it!" ]]
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: message/rfc822; forwarded="no"
Message-ID: &lt;pEp.PVUYXR.CEB1A-47AC-4B4D-AC1B-F8F02D49D@example.org&gt;
From: Alice Spivak Hyatt &lt;alice@example.org&gt;
To: Carol Burnett &lt;carol@example.net&gt;
Subject: Boom shaka laka
[...]
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; filename="msg.txt"
Don't you get sick of these=3F
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: application/pgp-keys
Content-Disposition: attachment; filename="pEpkey.asc"
-----BEGIN PGP PUBLIC KEY BLOCK-----
xsBNBFV4PbEBCADTmjGDsoti/VPoZ3w2oCjLBNq1jWIGMkbiUgCGUQjVsNrSZ80U
[...]
q46bEcclS/gTGHtFweVOiqRnR4H5YEjurCd84h8zF8MAArhxBhAtbg1nYgeHjkKX
=t2WB
-----END PGP PUBLIC KEY BLOCK-----
--238e1f2946e87ccd3d1b58ba507ed7ab--
</pre>
<h1 id="rfc.appendix.B">
<a href="#rfc.appendix.B">Appendix B.</a> <a href="#document-changelog" id="document-changelog">Document Changelog</a>
</h1>
<p id="rfc.section.B.p.1">[[ RFC Editor: This section is to be removed before publication ]]</p>
<p></p>
<ul>
<li>draft-melnikov-iana-reg-forwarded-00</li>
<li>Initial version derived from draft-ietf-lamps-header-protection-requirements-01</li>
</ul>
<h1 id="rfc.appendix.C">
<a href="#rfc.appendix.C">Appendix C.</a> <a href="#open-issues" id="open-issues">Open Issues</a>
</h1>
<p></p>
<ul><li>Determine whether to add an option for &#8220;forwarded=unknown&#8221; to indicate support for this Content-Type header field parameter.</li></ul>
<p id="rfc.section.C.p.2">[[ RFC Editor: This section should be empty and is to be removed before publication. ]]</p>
<h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
<div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Alexey Melnikov</span>
<span class="n hidden">
<span class="family-name">Melnikov</span>
</span>
</span>
<span class="org vcardline">Isode Ltd</span>
<span class="adr">
<span class="vcardline">14 Castle Mews</span>
<span class="vcardline">
<span class="locality">Hampton, Middlesex</span>,
<span class="region"></span>
<span class="code">TW12 2NP</span>
</span>
<span class="country-name vcardline">UK</span>
</span>
<span class="vcardline">EMail: <a href="mailto:alexey.melnikov@isode.com">alexey.melnikov@isode.com</a></span>
</address>
</div><div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Bernie Hoeneisen</span>
<span class="n hidden">
<span class="family-name">Hoeneisen</span>
</span>
</span>
<span class="org vcardline">pEp Foundation</span>
<span class="adr">
<span class="vcardline">Oberer Graben 4</span>
<span class="vcardline">
<span class="locality">CH-8400 Winterthur</span>,
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline">Switzerland</span>
</span>
<span class="vcardline">EMail: <a href="mailto:bernie.hoeneisen@pep.foundation">bernie.hoeneisen@pep.foundation</a></span>
<span class="vcardline">URI: <a href="https://pep.foundation/">https://pep.foundation/</a></span>
</address>
</div>
</body>
</html>

448
forwarded-no/archive/draft-melnikov-iana-reg-forwarded-02.txt
View File

@ -1,448 +0,0 @@
Network Working Group A. Melnikov
Internet-Draft Isode Ltd
Intended status: Informational B. Hoeneisen
Expires: May 7, 2020 pEp Foundation
November 04, 2019
IANA Registration of Content-Type Header Field Parameter 'forwarded'
draft-melnikov-iana-reg-forwarded-02
Abstract
This document defines a new Content-Type header field parameter named
"forwarded" for "message/rfc822" and "message/global" media types,
and its registration with IANA.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 7, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Melnikov & Hoeneisen Expires May 7, 2020 [Page 1]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Implementations . . . . . . . . . . . . . . . . . . . . . 3
1.3. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.4. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. Additional Example (pEp) . . . . . . . . . . . . . . 6
Appendix B. Document Changelog . . . . . . . . . . . . . . . . . 8
Appendix C. Open Issues . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
This document defines a new Content-Type header field parameter
[RFC2045] for "message/rfc822" and "message/global" [RFC6532] media
types with name "forwarded". The parameter value is case-
insensitive and can be either "yes" or "no". Setting the value to
"no" is meaningful when used within S/MIME or PGP/MIME signed or
encrypted body parts (cf.
[I-D.ietf-lamps-header-protection-requirements]. The value "yes"
means that the message nested inside "message/rfc822" (or "message/
global") is a simple forwarded message. If the parameter is missing,
the default assumption is the message has been forwarded.
1.1. Use Cases
Two use cases have been discovered so far:
1. This parameter indicates whether a nested message is signed and/
or encrypted (S/MIME or PGP/MIME), which tells the receiving side
how to display the message to the user. Currently, many email
clients display "weird artefacts" to users due to this missing
information.
2. This parameter indicates to mailing lists which email messages
are forwarded, and which are signed and/or encrypted (S/MIME or
PGP/MIME), and how to handle these respective messages.
Melnikov & Hoeneisen Expires May 7, 2020 [Page 2]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
1.2. Implementations
At this time, there are two known email systems which use this
Content-Type header field parameter:
1. Isode with S/MIME [RFC8551]
2. pEp with PGP/MIME [I-D.birk-pep]
1.3. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
1.4. Terms
The following terms are defined for the scope of this document:
o Header Field (HF): cf. [RFC5322]
o Header Section (HS): cf. [RFC5322]
2. Specification
This section defines the new "forwarded" Content-Type header field
parameter.
The Content-Type header field parameter "forwarded" may assume three
values:
o "yes": The email message contained in the MIME part is a forwarded
message. A MUA (Mail User Agent) that is forwarding a message
should add a Content-Type header field parameter "forwarded=yes".
o "no": The email message contained in the MIME part is a
encapsulated email message that has been signed and/or encrypted
for header protection. MUAs SHOULD add a Content-Type header
field parameter "forwarded=no" to indicate the message is not
forwarded, but encapsulated for header protection (cf.
[I-D.ietf-lamps-header-protection-requirements]).
o absent: If the MUA has no information to determine whether an
email message is forwarded or encapsulated, it omits the
"forwarded" Content-Type header field parameter. A receiving MUAs
default behavior is to assume the email message contained in the
MIME part is a forwarded message.
Melnikov & Hoeneisen Expires May 7, 2020 [Page 3]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
3. Example
The following example shows the usage of the Content-Type header
field parameter "forwarded" for an email message that is not
forwarded, but encapsulated in another email message.
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
Message-ID: <e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net>
Subject: Meeting at my place
From: "Alexey Melnikov" <alexey.melnikov@example.net>
MIME-Version: 1.0
Content-Type: multipart/signed; charset=us-ascii; micalg=sha1;
protocol="application/pkcs7-signature";
boundary=.cbe16d2a-e1a3-4220-b821-38348fc97237
This is a multipart message in MIME format.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Type: message/rfc822; forwarded=no
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
From: "Alexey Melnikov" <alexey.melnikov@example.net>
Message-ID: <e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net>
MIME-Version: 1.0
MMHS-Primary-Precedence: 3
Subject: Meeting at my place
To: somebody@example.net
X-Mailer: Example Mailer
Content-Type: text/plain; charset=us-ascii
This is an important message that I don't want to be modified.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature
[[base-64 encoded signature]]
--.cbe16d2a-e1a3-4220-b821-38348fc97237--
Appendix A contains an additional example on the usage of the
Content-Type header field parameter "forwarded" as used by pEp
[I-D.birk-pep].
Melnikov & Hoeneisen Expires May 7, 2020 [Page 4]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
4. Security Considerations
This document does not define a new protocol, and thus does not
create new security concerns in and of itself.
5. Privacy Considerations
This document does not introduce any new issues regarding Privacy.
6. IANA Considerations
This document requests IANA to register the Content-Type header field
parameter [RFC2045] with name "forwarded" for "message/rfc822" and
"message/global" media types as specified in Section 2 of this
document.
7. Acknowledgments
The authors would like to thank the following people who have
provided helpful comments and suggestions for this document: David
Wilson, Kelly Bristol, Krista Bennett, Robert Williams, Steve Kille,
and Wei Chuang.
David Wilson came up with the idea of defining a new Content-Type
header field parameter to distinguish forwarded messages from inner
header field protection constructs.
8. References
8.1. Normative References
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996,
<https://www.rfc-editor.org/info/rfc2045>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008,
<https://www.rfc-editor.org/info/rfc5322>.
Melnikov & Hoeneisen Expires May 7, 2020 [Page 5]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
[RFC8551] Schaad, J., Ramsdell, B., and S. Turner, "Secure/
Multipurpose Internet Mail Extensions (S/MIME) Version 4.0
Message Specification", RFC 8551, DOI 10.17487/RFC8551,
April 2019, <https://www.rfc-editor.org/info/rfc8551>.
8.2. Informative References
[I-D.birk-pep]
Marques, H., Luck, C., and B. Hoeneisen, "pretty Easy
privacy (pEp): Privacy by Default", draft-birk-pep-04
(work in progress), July 2019.
[I-D.ietf-lamps-header-protection-requirements]
Melnikov, A. and B. Hoeneisen, "Problem Statement and
Requirements for Header Protection", draft-ietf-lamps-
header-protection-requirements-01 (work in progress),
October 2019.
[RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized
Email Headers", RFC 6532, DOI 10.17487/RFC6532, February
2012, <https://www.rfc-editor.org/info/rfc6532>.
Appendix A. Additional Example (pEp)
The following example shows the usage of the Content-Type header
field parameter "forwarded" as used by pEp [I-D.birk-pep] in an email
message (after decryption). The inner email message was not
forwarded, but encapsulated in another email message.
Melnikov & Hoeneisen Expires May 7, 2020 [Page 6]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
Message-ID: <pEp.PVUYXR.CEB1A-47AC-4B4D-AC1B-F8F02D49D@example.org>
From: Alice Spivak Hyatt <alice@example.org>
To: Carol Burnett <carol@example.net>
Subject: pEp
[...]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="238e1f2946e87ccd3d1b58ba507ed7ab"
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline; filename="msg.txt"
[[ User-Information, e.g. "If you are seeing this message, your
client does not support raising message attachments. Please click
on the message attachment to view it!" ]]
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: message/rfc822; forwarded="no"
Message-ID: <pEp.PVUYXR.CEB1A-47AC-4B4D-AC1B-F8F02D49D@example.org>
From: Alice Spivak Hyatt <alice@example.org>
To: Carol Burnett <carol@example.net>
Subject: Boom shaka laka
[...]
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; filename="msg.txt"
Don't you get sick of these=3F
--238e1f2946e87ccd3d1b58ba507ed7ab
Content-Type: application/pgp-keys
Content-Disposition: attachment; filename="pEpkey.asc"
-----BEGIN PGP PUBLIC KEY BLOCK-----
xsBNBFV4PbEBCADTmjGDsoti/VPoZ3w2oCjLBNq1jWIGMkbiUgCGUQjVsNrSZ80U
[...]
q46bEcclS/gTGHtFweVOiqRnR4H5YEjurCd84h8zF8MAArhxBhAtbg1nYgeHjkKX
=t2WB
-----END PGP PUBLIC KEY BLOCK-----
--238e1f2946e87ccd3d1b58ba507ed7ab--
Melnikov & Hoeneisen Expires May 7, 2020 [Page 7]
Internet-Draft Content-Type HF Parameter 'forwarded' November 2019
Appendix B. Document Changelog
[[ RFC Editor: This section is to be removed before publication ]]
o draft-melnikov-iana-reg-forwarded-00
o Initial version derived from draft-ietf-lamps-header-protection-
requirements-01
Appendix C. Open Issues
o Determine whether to add an option for "forwarded=unknown" to
indicate support for this Content-Type header field parameter.
[[ RFC Editor: This section should be empty and is to be removed
before publication. ]]
Authors' Addresses
Alexey Melnikov
Isode Ltd
14 Castle Mews
Hampton, Middlesex TW12 2NP
UK
Email: alexey.melnikov@isode.com
Bernie Hoeneisen
pEp Foundation
Oberer Graben 4
CH-8400 Winterthur
Switzerland
Email: bernie.hoeneisen@pep.foundation
URI: https://pep.foundation/
Melnikov & Hoeneisen Expires May 7, 2020 [Page 8]

550
forwarded-no/archive/draft-melnikov-iana-reg-forwarded-02.xml
View File

@ -1,550 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes"?>
<rfc docName="draft-melnikov-iana-reg-forwarded-02" category="info">
<front>
<title abbrev="Content-Type HF Parameter 'forwarded'">IANA Registration of Content-Type Header Field Parameter 'forwarded'</title>
<author initials="A." surname="Melnikov" fullname="Alexey Melnikov">
<organization>Isode Ltd</organization>
<address>
<postal>
<street>14 Castle Mews</street>
<city>Hampton, Middlesex</city>
<code>TW12 2NP</code>
<country>UK</country>
</postal>
<email>alexey.melnikov@isode.com</email>
</address>
</author>
<author initials="B." surname="Hoeneisen" fullname="Bernie Hoeneisen">
<organization>pEp Foundation</organization>
<address>
<postal>
<street>Oberer Graben 4</street>
<city>CH-8400 Winterthur</city>
<country>Switzerland</country>
</postal>
<email>bernie.hoeneisen@pep.foundation</email>
<uri>https://pep.foundation/</uri>
</address>
</author>
<date year="2019" month="November" day="04"/>
<abstract>
<t>This document defines a new Content-Type header field parameter named
“forwarded” for “message/rfc822” and “message/global” media types, and
its registration with IANA.</t>
</abstract>
</front>
<middle>
<section anchor="introduction" title="Introduction">
<t>This document defines a new Content-Type header field parameter
<xref target="RFC2045"/> for “message/rfc822” and “message/global” <xref target="RFC6532"/>
media types with name “forwarded”. The parameter value is case-
insensitive and can be either “yes” or “no”. Setting the value to “no”
is meaningful when used within S/MIME or PGP/MIME signed or encrypted
body parts (cf. <xref target="I-D.ietf-lamps-header-protection-requirements"/>.
The value “yes” means that the message nested inside “message/rfc822”
(or “message/global”) is a simple forwarded message. If the parameter
is missing, the default assumption is the message has been forwarded.</t>
<section anchor="use-cases" title="Use Cases">
<t>Two use cases have been discovered so far:</t>
<t><list style="numbers">
<t>This parameter indicates whether a nested message is signed and/or
encrypted (S/MIME or PGP/MIME), which tells the receiving side how
to display the message to the user. Currently, many email clients
display “weird artefacts” to users due to this missing information.</t>
<t>This parameter indicates to mailing lists which email messages are
forwarded, and which are signed and/or encrypted (S/MIME or
PGP/MIME), and how to handle these respective messages.</t>
</list></t>
</section>
<section anchor="implementations" title="Implementations">
<t>At this time, there are two known email systems which use this
Content-Type header field parameter:</t>
<t><list style="numbers">
<t>Isode with S/MIME <xref target="RFC8551"/></t>
<t>pEp with PGP/MIME <xref target="I-D.birk-pep"/></t>
</list></t>
</section>
<section anchor="requirements-language" title="Requirements Language">
<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this
document are to be interpreted as described in <xref target="RFC2119"/>.</t>
</section>
<section anchor="terms" title="Terms">
<t>The following terms are defined for the scope of this document:</t>
<t><list style="symbols">
<t>Header Field (HF): cf. <xref target="RFC5322"/></t>
<t>Header Section (HS): cf. <xref target="RFC5322"/></t>
</list></t>
</section>
</section>
<section anchor="specification" title="Specification">
<t>This section defines the new “forwarded” Content-Type header
field parameter.</t>
<t>The Content-Type header field parameter “forwarded” may assume three
values:</t>
<t><list style="symbols">
<t>“yes”: The email message contained in the MIME part is a forwarded
message. A MUA (Mail User Agent) that is forwarding a message should
add a Content-Type header field parameter “forwarded=yes”.</t>
<t>“no”: The email message contained in the MIME part is a encapsulated
email message that has been signed and/or encrypted for header
protection. MUAs SHOULD add a Content-Type header field parameter
“forwarded=no” to indicate the message is not forwarded, but
encapsulated for header protection
(cf. <xref target="I-D.ietf-lamps-header-protection-requirements"/>).</t>
<t>absent: If the MUA has no information to determine whether an email
message is forwarded or encapsulated, it omits the “forwarded”
Content-Type header field parameter. A receiving MUAs default
behavior is to assume the email message contained in the MIME part
is a forwarded message.</t>
</list></t>
<!-- krb: Add to the end of the absent bullet point: "For legacy
clients that do not recognize this parameter, email messages are
treated as though the parameter is missing."
-->
</section>
<section anchor="example" title="Example">
<t>The following example shows the usage of the Content-Type header field
parameter “forwarded” for an email message that is not forwarded, but
encapsulated in another email message.</t>
<figure><artwork><![CDATA[
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
Message-ID: <e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net>
Subject: Meeting at my place
From: "Alexey Melnikov" <alexey.melnikov@example.net>
MIME-Version: 1.0
Content-Type: multipart/signed; charset=us-ascii; micalg=sha1;
protocol="application/pkcs7-signature";
boundary=.cbe16d2a-e1a3-4220-b821-38348fc97237
This is a multipart message in MIME format.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Type: message/rfc822; forwarded=no
Date: Mon, 25 Sep 2017 17:31:42 +0100 (GMT Daylight Time)
From: "Alexey Melnikov" <alexey.melnikov@example.net>
Message-ID: <e4a483cb-1dfb-481d-903b-298c92c21f5e@matt.example.net>
MIME-Version: 1.0
MMHS-Primary-Precedence: 3
Subject: Meeting at my place
To: somebody@example.net
X-Mailer: Example Mailer
Content-Type: text/plain; charset=us-ascii
This is an important message that I don't want to be modified.
--.cbe16d2a-e1a3-4220-b821-38348fc97237
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature
[[base-64 encoded signature]]
--.cbe16d2a-e1a3-4220-b821-38348fc97237--
]]></artwork></figure>
<t><xref target="additional-example"/> contains an additional example on the usage of
the Content-Type header field parameter “forwarded” as used by pEp
<xref target="I-D.birk-pep"/>.</t>
</section>
<section anchor="security-considerations" title="Security Considerations">
<t>This document does not define a new protocol, and thus does not create
new security concerns in and of itself.</t>
</section>
<section anchor="privacy-considerations" title="Privacy Considerations">
<t>This document does not introduce any new issues regarding Privacy.</t>
</section>
<section anchor="iana-considerations" title="IANA Considerations">
<t>This document requests IANA to register the Content-Type header
field parameter <xref target="RFC2045"/> with name “forwarded” for “message/rfc822”
and “message/global” media types as specified in <xref target="specification"/>
of this document.</t>
</section>
<section anchor="acknowledgments" title="Acknowledgments">
<t>The authors would like to thank the following people who have provided
helpful comments and suggestions for this document: David Wilson,
Kelly Bristol, Krista Bennett, Robert Williams, Steve Kille, and Wei
Chuang.</t>
<t>David Wilson came up with the idea of defining a new Content-Type
header field parameter to distinguish forwarded messages from inner
header field protection constructs.</t>
</section>
</middle>
<back>
<references title='Normative References'>
<reference anchor="RFC2045" target='https://www.rfc-editor.org/info/rfc2045'>
<front>
<title>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
<author initials='N.' surname='Freed' fullname='N. Freed'><organization /></author>
<author initials='N.' surname='Borenstein' fullname='N. Borenstein'><organization /></author>
<date year='1996' month='November' />
<abstract><t>This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2045'/>
<seriesInfo name='DOI' value='10.17487/RFC2045'/>
</reference>
<reference anchor="RFC5322" target='https://www.rfc-editor.org/info/rfc5322'>
<front>
<title>Internet Message Format</title>
<author initials='P.' surname='Resnick' fullname='P. Resnick' role='editor'><organization /></author>
<date year='2008' month='October' />
<abstract><t>This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of &quot;electronic mail&quot; messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, &quot;Standard for the Format of ARPA Internet Text Messages&quot;, updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5322'/>
<seriesInfo name='DOI' value='10.17487/RFC5322'/>
</reference>
<reference anchor="RFC8551" target='https://www.rfc-editor.org/info/rfc8551'>
<front>
<title>Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification</title>
<author initials='J.' surname='Schaad' fullname='J. Schaad'><organization /></author>
<author initials='B.' surname='Ramsdell' fullname='B. Ramsdell'><organization /></author>
<author initials='S.' surname='Turner' fullname='S. Turner'><organization /></author>
<date year='2019' month='April' />
<abstract><t>This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 4.0. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 5751.</t></abstract>
</front>
<seriesInfo name='RFC' value='8551'/>
<seriesInfo name='DOI' value='10.17487/RFC8551'/>
</reference>
<reference anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<abstract><t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
</reference>
</references>
<references title='Informative References'>
<reference anchor="I-D.ietf-lamps-header-protection-requirements">
<front>
<title>Problem Statement and Requirements for Header Protection</title>
<author initials='A' surname='Melnikov' fullname='Alexey Melnikov'>
<organization />
</author>
<author initials='B' surname='Hoeneisen' fullname='Bernie Hoeneisen'>
<organization />
</author>
<date month='October' day='29' year='2019' />
<abstract><t>Privacy and security issues with email header protection in S/MIME have been identified for some time. However, the desire to fix these issues has only recently been expressed in the IETF LAMPS Working Group. The existing S/MIME specification is likely to be updated regarding header protection. This document describes the problem statement, generic use cases, and requirements of header protection.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-lamps-header-protection-requirements-01' />
<format type='TXT'
target='http://www.ietf.org/internet-drafts/draft-ietf-lamps-header-protection-requirements-01.txt' />
</reference>
<reference anchor="RFC6532" target='https://www.rfc-editor.org/info/rfc6532'>
<front>
<title>Internationalized Email Headers</title>
<author initials='A.' surname='Yang' fullname='A. Yang'><organization /></author>
<author initials='S.' surname='Steele' fullname='S. Steele'><organization /></author>
<author initials='N.' surname='Freed' fullname='N. Freed'><organization /></author>
<date year='2012' month='February' />
<abstract><t>Internet mail was originally limited to 7-bit ASCII. MIME added support for the use of 8-bit character sets in body parts, and also defined an encoded-word construct so other character sets could be used in certain header field values. However, full internationalization of electronic mail requires additional enhancements to allow the use of Unicode, including characters outside the ASCII repertoire, in mail addresses as well as direct use of Unicode in header fields like &quot;From:&quot;, &quot;To:&quot;, and &quot;Subject:&quot;, without requiring the use of complex encoded-word constructs. This document specifies an enhancement to the Internet Message Format and to MIME that allows use of Unicode in mail addresses and most header field content.</t><t>This specification updates Section 6.4 of RFC 2045 to eliminate the restriction prohibiting the use of non-identity content-transfer- encodings on subtypes of &quot;message/&quot;. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6532'/>
<seriesInfo name='DOI' value='10.17487/RFC6532'/>
</reference>
<reference anchor="I-D.birk-pep">
<front>
<title>pretty Easy privacy (pEp): Privacy by Default</title>
<author initials='H' surname='Marques' fullname='Hernani Marques'>
<organization />
</author>
<author initials='C' surname='Luck' fullname='Claudio Luck'>
<organization />
</author>
<author initials='B' surname='Hoeneisen' fullname='Bernie Hoeneisen'>
<organization />
</author>
<date month='July' day='8' year='2019' />
<abstract><t>The pretty Easy privacy (pEp) model and protocols describe a set of conventions for the automation of operations traditionally seen as barriers to the use and deployment of secure, privacy-preserving end- to-end interpersonal messaging. These include, but are not limited to, key management, key discovery, and private key handling (including peer-to-peer synchronization of private keys and other user data across devices). Human Rights-enabling principles like Data Minimization, End-to-End and Interoperability are explicit design goals. For the goal of usable privacy, pEp introduces means to verify communication between peers and proposes a trust-rating system to denote secure types of communications and signal the privacy level available on a per-user and per-message level. Significantly, the pEp protocols build on already available security formats and message transports (e.g., PGP/MIME with email), and are written with the intent to be interoperable with already widely- deployed systems in order to ease adoption and implementation. This document outlines the general design choices and principles of pEp.</t></abstract>
</front>
<seriesInfo name='Internet-Draft' value='draft-birk-pep-04' />
<format type='TXT'
target='http://www.ietf.org/internet-drafts/draft-birk-pep-04.txt' />
</reference>
</references>
<!-- =========================================================================== -->
<section anchor="additional-example" title="Additional Example (pEp)">
<t>The following example shows the usage of the Content-Type header field
parameter “forwarded” as used by pEp <xref target="I-D.birk-pep"/> in an email
message (after decryption). The inner email message was not forwarded,
but encapsulated in another email message.</t>