|
|
|
@ -163,8 +163,8 @@ determined by the IETF LAMPS WG.
|
|
|
|
|
{{RFC2045}} construct.
|
|
|
|
|
|
|
|
|
|
* MIME Header Fields: Header Fields describing content of a MIME entity
|
|
|
|
|
{{RFC2045}}, in particular the MIME structure. Each MIME header field
|
|
|
|
|
name start with "Content-" prefix.
|
|
|
|
|
{{RFC2045}}, in particular the MIME structure. Each MIME Header Field
|
|
|
|
|
name starts with "Content-" prefix.
|
|
|
|
|
|
|
|
|
|
* MIME Header Section (part): The collection of MIME Header Fields.
|
|
|
|
|
"MIME Header Section" refers to a Header Sections that contains only
|
|
|
|
@ -338,11 +338,6 @@ c) Encryption only
|
|
|
|
|
This section contains the specification for Header Protection in
|
|
|
|
|
S/MIME to update and clarifies Section 3.1 of {{RFC8551}} (S/MIME
|
|
|
|
|
4.0).
|
|
|
|
|
<!--
|
|
|
|
|
Alexey: true, but this will not age well:
|
|
|
|
|
This specification is likely to be integrated into S/MIME at
|
|
|
|
|
some later stage.
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
Furthermore, it is likely that PGP/MIME {{RFC3156}} will also incorprorate
|
|
|
|
|
this specification or parts of it.
|
|
|
|
@ -768,17 +763,17 @@ Legend:
|
|
|
|
|
* MIME-HSp: MIME Header Section part to describe the encryption or
|
|
|
|
|
signature as per {{RFC8551}}
|
|
|
|
|
|
|
|
|
|
* Trans-HF: Header Fields added in Transit (between sending and
|
|
|
|
|
receiving side). RFC 5322 calls them "Trace Header Fields".
|
|
|
|
|
* Trace-HF: Header Fields added in Transit (between sending and
|
|
|
|
|
receiving side) as per {{RFC5322}}
|
|
|
|
|
|
|
|
|
|
* \>: taken over / copied from last column
|
|
|
|
|
|
|
|
|
|
* \=: propagates unchanged, unless something unusual (e.g. attack)
|
|
|
|
|
happens
|
|
|
|
|
|
|
|
|
|
* \*: HF that is often not present (also further HF may not be
|
|
|
|
|
present). If a HF is not present, naturally it can neither be taken
|
|
|
|
|
over nor propagated.
|
|
|
|
|
* \*: HF that is often not present (also further HFs, e.g. To, may not
|
|
|
|
|
be present). If a HF is not present, naturally it can neither be
|
|
|
|
|
taken over nor propagated.
|
|
|
|
|
|
|
|
|
|
* (new) / (OrigM): HF or MIME-HSp is generated depending on the
|
|
|
|
|
decision in {{sending-side-step-1}}, while '(new)' / '(OrigM)'
|
|
|
|
|