Re: [lamps] Draft addition of header protection to the LAMPS charter

bernie@ietf.hoeneisen.ch Sat, 05 January 2019 12:40 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 738611277CC for <spasm@ietfa.amsl.com>; Sat, 5 Jan 2019 04:40:07 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 bSt6G5_Bh3JK for <spasm@ietfa.amsl.com>; Sat, 5 Jan 2019 04:40:05 -0800 (PST)
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 44F3A124B0C for <spasm@ietf.org>; Sat, 5 Jan 2019 04:40:04 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1gflF8-0003Qa-It; Sat, 05 Jan 2019 13:39:58 +0100
Date: Sat, 05 Jan 2019 13:39:58 +0100
From: bernie@ietf.hoeneisen.ch
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: John R Levine <johnl@taugh.com>
cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, spasm@ietf.org
In-Reply-To: <alpine.OSX.2.21.1901041201150.93160@ary.qy>
Message-ID: <alpine.DEB.2.20.1901051314190.26171@softronics.hoeneisen.ch>
References: <20190104012415.AA6C3200C425F9@ary.qy> <87h8eonzxx.fsf@fifthhorseman.net> <alpine.OSX.2.21.1901041201150.93160@ary.qy>
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/teDcvVh_XMeeRLzR9uqfC9rMpzc>
Subject: Re: [lamps] Draft addition of header protection to the LAMPS charter
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: Sat, 05 Jan 2019 12:40:08 -0000

Hi John

Thanks for your feedback

On Fri, 4 Jan 2019, John R Levine wrote:

> My preference would be to leave out the prior history catalog completely.

This is not about prior history.

S/MIME Version 3.2 (RFC 5751) defines a mechanism to perform Header 
Protection, which has some implementations out there. The outcome of the 
new Charter Item on Header Protection is almost certainly going to have an 
impact on the currently standardized version and therefore to update RFC 
5751 (or rather its bis).

Although, I hope (and still believe) we can find a viable solution that 
remains backwards compatible to S/MIME Version 3.2 (i.e. minor updates and 
additions to the existing standards only), there are other proposals that 
suggest to change the way Header Protection is done in S/MIME rather 
fundamentally.

Therefore, I am of the opinion we ought to mention / reference what 
existing standards are directly going to be affected by the outcome of 
the new charter item.

cheers,
  Bernie