Subject: [Medup] New Version Notification for draft-luck-lamps-pep-header-protection-01.txt (fwd)

From: Bernie Hoeneisen <[email-masked]>
Date: Thu, 14 Mar 2019 15:25:51 +0100 (CET)

FYI (I-D updated to -01, major rewrite)

---------- Forwarded message ----------
Date: Tue, 12 Mar 2019 00:58:12
From: [email-masked]
To: Claudio Luck <[email-masked]>,
     Bernie Hoeneisen <[email-masked]>
Subject: New Version Notification for
     draft-luck-lamps-pep-header-protection-01.txt

A new version of I-D, draft-luck-lamps-pep-header-protection-01.txt
has been successfully submitted by Bernie Hoeneisen and posted to the
IETF repository.

Name:		draft-luck-lamps-pep-header-protection
Revision:	01
Title:		pretty Easy privacy (pEp): Header Protection
Document date:	2019-03-12
Group:		Individual Submission
Pages:		22
URL:            https://www.ietf.org/internet-drafts/draft-luck-lamps-pep-header-protection-01.txt
Status:         https://datatracker.ietf.org/doc/draft-luck-lamps-pep-header-protection/
Htmlized:       https://tools.ietf.org/html/draft-luck-lamps-pep-header-protection-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-luck-lamps-pep-header-protection
Diff:           https://www.ietf.org/rfcdiff?url2=draft-luck-lamps-pep-header-protection-01

Abstract:
    Issues with email header protection in S/MIME have been recently
    raised in the IETF LAMPS Working Group.  The need for amendments to
    the existing specification regarding header protection was expressed.

    The pretty Easy privacy (pEp) implementations currently use a
    mechanism quite similar to the currently standardized message
    wrapping for S/MIME.  The main difference is that pEp is using PGP/
    MIME instead, and adds space for carrying public keys next to the
    protected message.

    In LAMPS voices have also been expressed, that whatever mechanism
    will be chosen, it should not be limited to S/MIME, but also
    applicable to PGP/MIME.

    This document aims to contribute to this discussion and share pEp
    implementation experience with email header protection.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat