Browse Source

Typo correction in review version

master
Bernie Hoeneisen 2 years ago
parent
commit
d71f31cb83
2 changed files with 9 additions and 9 deletions
  1. +4
    -4
      ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200625.html
  2. +5
    -5
      ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200625.txt

+ 4
- 4
ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200625.html View File

@ -390,7 +390,7 @@
<link href="#rfc.section.4" rel="Chapter" title="4 Specification">
<link href="#rfc.section.4.1" rel="Chapter" title="4.1 Main Use Case">
<link href="#rfc.section.4.1.1" rel="Chapter" title="4.1.1 MIME Format">
<link href="#rfc.section.4.1.2" rel="Chapter" title="4.1.2 Inner Message Header Header Fields">
<link href="#rfc.section.4.1.2" rel="Chapter" title="4.1.2 Inner Message Header Fields">
<link href="#rfc.section.4.1.3" rel="Chapter" title="4.1.3 Outer Message Header Fields">
<link href="#rfc.section.4.1.4" rel="Chapter" title="4.1.4 Message Processing">
<link href="#rfc.section.4.2" rel="Chapter" title="4.2 Backward Compatibility Use Case">
@ -501,7 +501,7 @@
</li>
<ul><li>4.1.1. <a href="#rfc.section.4.1.1">MIME Format</a>
</li>
<li>4.1.2. <a href="#rfc.section.4.1.2">Inner Message Header Header Fields</a>
<li>4.1.2. <a href="#rfc.section.4.1.2">Inner Message Header Fields</a>
</li>
<li>4.1.3. <a href="#rfc.section.4.1.3">Outer Message Header Fields</a>
</li>
@ -567,7 +567,7 @@
<li>S&#8203;/&#8203;MIME: Secure/Multipurpose Internet Mail Extensions (cf. <a href="#RFC8551" class="xref">[RFC8551]</a>)</li>
<li>PGP/MIME: MIME Security with OpenPGP (cf. <a href="#RFC3156" class="xref">[RFC3156]</a>)</li>
<li>Message: An Email Message consisting of header fields (collectively called &#8220;the Header Section of the message&#8221;) followed, optionally, by a Body; cf. <a href="#RFC5322" class="xref">[RFC5322]</a>.</li>
<li>Transport: The entity taking care of the transport of a Message towards the receiver or from the sender. The Transport on the sending side typically determines the destination recipients by reading the To, Cc and Bcc Header Header Fields (of the Outer Message). The Transport is typically implemented by an MTA (Mail Transfer Agent).</li>
<li>Transport: The entity taking care of the transport of a Message towards the receiver or from the sender. The Transport on the sending side typically determines the destination recipients by reading the To, Cc and Bcc Header Fields (of the Outer Message). The Transport is typically implemented by an MTA (Mail Transfer Agent).</li>
<li>Header Field (HF): cf. <a href="#RFC5322" class="xref">[RFC5322]</a> Header Fields are lines beginning with a field name, followed by a colon (&#8220;:&#8221;), followed by a field body (value), and terminated by CRLF; cf. <a href="#RFC5322" class="xref">[RFC5322]</a>. <br><br> Note: To avoid ambiguity, this document does not use the terms &#8220;Header&#8221; or &#8220;Headers&#8221; in isolation, but instead always uses &#8220;Header Field&#8221; to refer to the individual field and &#8220;Header Section&#8221; to refer to the entire collection; cf. <a href="#RFC5322" class="xref">[RFC5322]</a>.</li>
<li>Header Section (HS): The Header Section is a sequence of lines of characters with special syntax as defined in <a href="#RFC5322" class="xref">[RFC5322]</a>. It is the (top) section of a message containing the Header Fields.</li>
<li>Body: The Body is simply a sequence of characters that follows the Header Section and is separated from the Header Section by an empty line (i.e., a line with nothing preceding the CRLF); cf <a href="#RFC5322" class="xref">[RFC5322]</a>. It is the (bottom) section of Message containing the payload of a Message. Typically, the Body consists of a (multipart) MIME <a href="#RFC2045" class="xref">[RFC2045]</a> construct.</li>
@ -735,7 +735,7 @@
<p id="rfc.section.4.1.1.1.p.7">The impact of using &#8220;text/plain&#8221;, while in fact containing a (subset of a) &#8220;message/RFC822&#8221; media type to be parsed, is for further study concerning MIME standards and real world deployments.</p>
<p id="rfc.section.4.1.1.1.p.8">For further information, the reader is encouraged to consult <a href="#I-D.autocrypt-lamps-protected-headers" class="xref">[I-D.autocrypt-lamps-protected-headers]</a>.</p>
<h1 id="rfc.section.4.1.2">
<a href="#rfc.section.4.1.2">4.1.2.</a> <a href="#inner-msg-hf" id="inner-msg-hf">Inner Message Header Header Fields</a>
<a href="#rfc.section.4.1.2">4.1.2.</a> <a href="#inner-msg-hf" id="inner-msg-hf">Inner Message Header Fields</a>
</h1>
<p id="rfc.section.4.1.2.p.1">It is RECOMMEND that the Inner Messages contains all the Header Fields of the Original Message with the exception of the following Header Field, which MUST NOT be included to the Inner Message nor to any other protected part of the message:</p>
<p></p>


+ 5
- 5
ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200625.txt View File

@ -81,7 +81,7 @@ Table of Contents
4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Main Use Case . . . . . . . . . . . . . . . . . . . . . . 8
4.1.1. MIME Format . . . . . . . . . . . . . . . . . . . . . 8
4.1.2. Inner Message Header Header Fields . . . . . . . . . 11
4.1.2. Inner Message Header Fields . . . . . . . . . . . . . 11
4.1.3. Outer Message Header Fields . . . . . . . . . . . . . 11
4.1.4. Message Processing . . . . . . . . . . . . . . . . . 13
4.2. Backward Compatibility Use Case . . . . . . . . . . . . . 15
@ -191,9 +191,9 @@ Internet-Draft Header Protection S/MIME June 2020
o Transport: The entity taking care of the transport of a Message
towards the receiver or from the sender. The Transport on the
sending side typically determines the destination recipients by
reading the To, Cc and Bcc Header Header Fields (of the Outer
Message). The Transport is typically implemented by an MTA (Mail
Transfer Agent).
reading the To, Cc and Bcc Header Fields (of the Outer Message).
The Transport is typically implemented by an MTA (Mail Transfer
Agent).
o Header Field (HF): cf. [RFC5322] Header Fields are lines beginning
with a field name, followed by a colon (":"), followed by a field
@ -562,7 +562,7 @@ Hoeneisen & Melnikov Expires December 27, 2020 [Page 10]
Internet-Draft Header Protection S/MIME June 2020
4.1.2. Inner Message Header Header Fields
4.1.2. Inner Message Header Fields
It is RECOMMEND that the Inner Messages contains all the Header
Fields of the Original Message with the exception of the following


Loading…
Cancel
Save