[lamps] [dispatch] Improve UX in Encrypted Email (distinguish between forwarded and otherwise wrapped messages) (fwd)
Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Fri, 02 October 2020 16:06 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 886F83A10E0 for <spasm@ietfa.amsl.com>; Fri, 2 Oct 2020 09:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 CQ1hpw0XvgPt for <spasm@ietfa.amsl.com>; Fri, 2 Oct 2020 09:06:00 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [IPv6:2a01:4f8:c0c:15fc::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1443A0BA6 for <spasm@ietf.org>; Fri, 2 Oct 2020 09:06:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1kONZG-000I3h-RN; Fri, 02 Oct 2020 18:05:58 +0200
Date: Fri, 02 Oct 2020 18:05:58 +0200
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF LAMPS WG <spasm@ietf.org>
cc: Jim Schaad <ietf@augustcellars.com>
Message-ID: <alpine.DEB.2.22.394.2010021757520.55994@softronics.hoeneisen.ch>
User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
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/IreWZsUWuK_B9KmUj4NRgNHj-SQ>
Subject: [lamps] [dispatch] Improve UX in Encrypted Email (distinguish between forwarded and otherwise wrapped messages) (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: Fri, 02 Oct 2020 16:06:03 -0000
Dear LAMPS list Please be informed that I just sent the follwing Email to the IETF DISPATCH list to address a wider Email community with a matter that is also relevant to the Header Protection discussion in LAMPS. https://mailarchive.ietf.org/arch/msg/dispatch/GeaPjbvCllw5Gg1MhRlpqAfHwuU/ This discussion is expected to happen on the DISPATCH Mailing list and you are invited to share your experience there. cheers, Bernie PS: I am almost certain Jim Schaad has some relevant experience on this to share with us. ---------- Forwarded message ---------- Date: Fri, 2 Oct 2020 17:56:35 From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> To: IETF DISPATCH list <dispatch@ietf.org> Subject: [dispatch] Improve UX in Encrypted Email (distinguish between forwarded and otherwise wrapped messages) Hi, We are seeking advise from the Email community regarding the following: In the LAMPS WG we are working on so called "Header Protection" for Emails to achieve better privacy. This concerns in particular (but not only) the Subject Header Field that is often left unencrypted in otherwise encrypted email. The mechnism used for Protection of Header Fields is to wrap a whole email (including the Header Section) into another email and apply protection to the former. At the receiving side certain Email clients do not render such signed/encrypted emails correctly to the user, leading to "weired artefacts" and thus bad User Experience (UX). Such clients do not distinguish between forwarded mail and signed/encrypted emails (wrapped in a similar way as forwarded messages). Alexey came up with a proposal to help such email clients to make this distinction (with the intention to improve UX). Together with Alexey I wrote up this proposal to an early draft version: https://tools.ietf.org/html/draft-melnikov-iana-reg-forwarded-00 This I-D suggests a new Content-Type Header Field Parameter "forwarded": If set to "yes", the contained message was forwarded; if set to "no", the message was "wrapped" for signature/encryption with Header Protection. However, I am concerned that the (binary) scope of the Content-Type Header Field Parameter may be too narrow, as there a potentially more cases an email message is transported in the Body part of another email message and such a Parameter may be helpful, such as: - Rejected (non deliveries / bounces) - ML-hold (message to be assessed by a mailing list admin) - ML-discard-action (mailing list admin reply to this will discard) - ML-digest-item (mailing list digest item; digest is a collection of multiple emails) - even more? I am seeking advice (mainly from implemeters of MUAs) on: 1) Is it helpful/useful/needed to enhance such a Parameter for these additional cases? 2) Have there been problems in the past to distingish such cases from "forwarded" messages? We'd appeciate your feedback (preferably within the next 10 days)! cheers, Bernie -- http://ucom.ch/ Modern Telephony Solutions and Tech Consulting for Internet Technology _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch
- [lamps] [dispatch] Improve UX in Encrypted Email … Bernie Hoeneisen