IETF Logo Mail Archive

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

Russ Housley <housley@vigilsec.com> Fri, 21 December 2018 14:45 UTC

Return-Path: <housley@vigilsec.com>
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 69F3612426E for <spasm@ietfa.amsl.com>; Fri, 21 Dec 2018 06:45:09 -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 nGUlhDAQxaNn for <spasm@ietfa.amsl.com>; Fri, 21 Dec 2018 06:45:06 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A93CC123FFD for <spasm@ietf.org>; Fri, 21 Dec 2018 06:45:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 9A10F3001B2 for <spasm@ietf.org>; Fri, 21 Dec 2018 09:45:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Z5RNABADlU_n for <spasm@ietf.org>; Fri, 21 Dec 2018 09:45:03 -0500 (EST)
Received: from [192.168.1.161] (pool-108-45-137-105.washdc.fios.verizon.net [108.45.137.105]) by mail.smeinc.net (Postfix) with ESMTPSA id 4BE96300080; Fri, 21 Dec 2018 09:45:03 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <alpine.DEB.2.20.1812211422000.882@softronics.hoeneisen.ch>
Date: Fri, 21 Dec 2018 09:45:03 -0500
Cc: LAMPS WG <spasm@ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD949886-DE26-4B88-B8BB-474025F07ABD@vigilsec.com>
References: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com> <87bm5hxdn0.fsf@fifthhorseman.net> <alpine.DEB.2.20.1812211039240.882@softronics.hoeneisen.ch> <6C7FBB0D-1146-4DE8-AA56-76B0586C8807@vigilsec.com> <alpine.DEB.2.20.1812211422000.882@softronics.hoeneisen.ch>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/9t0vjMJ00aTw0nalyTaRqyfiWvs>
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: Fri, 21 Dec 2018 14:45:09 -0000

Bernie:
> 
> I am aware of the charter update discussion regarding header protection.
> 
> However, I am not aware that a concrete text for the charter update has already been (officially) proposed. In DKG's recent email to this list it looks like that there is an existing proposal, and DKG suggests a amend to this (in form of a diff). This is where my confusion is routed.
> 
> So, do I understand you correctly, that officially no concrete text for charter update has been proposed yet (for discussion)?

No.  I am saying that DKG is offering this text for discussion as the next step.  Please review and comment.

> Are the chairs (or ADs) actually about to submit a proposal to the list to trigger the discussion or will it be the other way around?

Once the WG discussion is complete, the ADs will put it in the Datatracker and discuss it on a telechat.

Russ

v2.23.0 | Report a Bug | By Email