Browse Source

Implemented Alexey's latest feedback (deleting some misleading text)

master
Bernie Hoeneisen 2 years ago
parent
commit
b947a04edd
3 changed files with 2807 additions and 17 deletions
  1. +5
    -17
      ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd
  2. +1290
    -0
      ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200709.html
  3. +1512
    -0
      ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200709.txt

+ 5
- 17
ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd View File

@ -35,7 +35,7 @@ informative:
# RFC3501: # IMAP #
RFC4949: # Internet Security Glossary #
# RFC4880: # OpenPGP #
RFC5321: # SMTP #
# RFC5321: # SMTP #
# RFC5490:
RFC6376: # DKIM #
RFC6409:
@ -234,12 +234,10 @@ mechanism is to be determined by the IETF LAMPS WG.
Note: The Submission Entity varies among implementations, mainly
depending on the stage, where protection measures are applied to: It
could be e.g. a Message Submission Agent (MSA) {{RFC6409}} or a Mail
Transfer Agent (MTA) using Simple Mail Transfer Protocol (SMTP)
{{RFC5321}} or another (proprietary) solution. The latter is
particularly relevant, if protection is implemented as a plugin
solution or for mixnet networks, i.e. "onion routing" for email
(e.g. {{pEp.mixnet}}).
could be e.g. a Message Submission Agent (MSA) {{RFC6409}} or
another (proprietary) solution. The latter is particularly relevant,
if protection is implemented as a plugin solution or for mixnet
networks, i.e. "onion routing" for email (e.g. {{pEp.mixnet}}).
* Data Minimization: Data sparseness and hiding of all technically
concealable information whenever possible.
@ -593,16 +591,6 @@ interoperability issues result from it:
{{RFC2046}} on "Multipart Media Type). In the following an excerpt
of paragraphs that may be relevant in this context:
{::include ../shared/fence-line.mkd}
A body part is an entity and hence is NOT to be interpreted as
actually being an RFC 822 message. To begin with, NO header
fields are actually required in body parts. A body part that
starts with a blank line, therefore, is allowed and is a body
part for which all default values are to be assumed. In such a
case, the absence of a Content-Type header usually indicates
that the corresponding body has a content-type of "text/plain;
charset=US-ASCII".
{::include ../shared/fence-line.mkd}
{::include ../shared/fence-line.mkd}
The only header fields that have defined meaning for body parts
are those the names of which begin with "Content-". All other


+ 1290
- 0
ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200709.html
File diff suppressed because it is too large
View File


+ 1512
- 0
ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200709.txt
File diff suppressed because it is too large
View File


Loading…
Cancel
Save