IETF Logo Mail Archive

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

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Mon, 12 November 2018 16:01 UTC

Return-Path: <dkg@fifthhorseman.net>
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 9083B130E7D for <spasm@ietfa.amsl.com>; Mon, 12 Nov 2018 08:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01] 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 D7kJR6loyRIe for <spasm@ietfa.amsl.com>; Mon, 12 Nov 2018 08:01:49 -0800 (PST)
Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AF2C12F1AC for <spasm@ietf.org>; Mon, 12 Nov 2018 08:01:49 -0800 (PST)
Received: from fifthhorseman.net (unknown [IPv6:2001:470:1f07:60d:5c39:20ff:fe78:805b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id D7C83F99B; Mon, 12 Nov 2018 11:01:47 -0500 (EST)
Received: by fifthhorseman.net (Postfix, from userid 1000) id D677E201FF; Mon, 12 Nov 2018 10:55:33 -0500 (EST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Russ Housley <housley@vigilsec.com>, SPASM <spasm@ietf.org>
In-Reply-To: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com>
References: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com>
Date: Mon, 12 Nov 2018 10:55:30 -0500
Message-ID: <87a7mewarx.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/tTwoXHEpDwPtNSNdpI4e4ZnKblc>
Subject: Re: [lamps] Proposed 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: Mon, 12 Nov 2018 16:02:00 -0000

On Mon 2018-11-05 22:34:33 -0500, Russ Housley wrote:
> In the session earlier today, there was interest in adding a header
> protection work item to the agenda.  Alexey talked about this in
> Montreal, and he posted a draft a few weeks ago:
> draft-melnikov-lamps-header-protection.  Several people said that they
> would implement a solution if the WG produced an RFC on this topic.
>
> 1) Do you support the addition of this work to the LAMPS charter?

I support this change to the charter.

> 2) If it is added, would you review the document?

i will not only review, but have offered to co-author the doc with Alexey.

> 3) If it results in an RFC, would you implement?

yes, i already have a implementation that consumes both variants
described, and will implement a producer for one of them as well.

           --dkg

v2.23.0 | Report a Bug | By Email