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

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Thu, 14 March 2019 14:24 UTC

Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48840130EB5 for <spasm@ietfa.amsl.com>; Thu, 14 Mar 2019 07:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FgUaabgLC-T9 for <spasm@ietfa.amsl.com>; Thu, 14 Mar 2019 07:24:55 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0769129B88 for <spasm@ietf.org>; Thu, 14 Mar 2019 07:24:54 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1h4RHv-0002Ww-LL for spasm@ietf.org; Thu, 14 Mar 2019 15:24:51 +0100
Date: Thu, 14 Mar 2019 15:24:51 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF LAMPS WG <spasm@ietf.org>
Message-ID: <alpine.DEB.2.20.1903141524030.6514@softronics.hoeneisen.ch>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/uIik5WIwjWbK9eDkqciykFrs2yY>
Subject: [lamps] New Version Notification for draft-luck-lamps-pep-header-protection-01.txt (fwd)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2019 14:24:58 -0000

FYI (I-D updated to -01)

---------- Forwarded message ----------
Date: Tue, 12 Mar 2019 00:58:12
From: internet-drafts@ietf.org
To: Claudio Luck <claudio.luck@pep.foundation>,
     Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
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