IETF Logo Mail Archive

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

Jim Schaad <ietf@augustcellars.com> Tue, 06 November 2018 04:24 UTC

Return-Path: <ietf@augustcellars.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 E6B31130DD2 for <spasm@ietfa.amsl.com>; Mon, 5 Nov 2018 20:24:17 -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, 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 dMCUkbeZf-jg for <spasm@ietfa.amsl.com>; Mon, 5 Nov 2018 20:24:16 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C8A6130DD1 for <spasm@ietf.org>; Mon, 5 Nov 2018 20:24:16 -0800 (PST)
Received: from Jude (31.133.136.100) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 5 Nov 2018 20:19:21 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Russ Housley' <housley@vigilsec.com>, 'SPASM' <spasm@ietf.org>
References: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com>
In-Reply-To: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com>
Date: Tue, 06 Nov 2018 11:24:05 +0700
Message-ID: <015601d47588$903966b0$b0ac3410$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIG07FQiq73R77ZJFLx7HGiPw5gtaTdaaCQ
Content-Language: en-us
X-Originating-IP: [31.133.136.100]
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/i1EETcQAd2qhB1AFqTDwTo-xJfA>
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: Tue, 06 Nov 2018 04:24:18 -0000


> -----Original Message-----
> From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
> Sent: Tuesday, November 6, 2018 10:35 AM
> To: SPASM <spasm@ietf.org>
> Subject: [lamps] Proposed addition of header protection to the LAMPS
> charter
> 
> 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.
> 
> Three questions:
> 
> 1) Do you support the addition of this work to the LAMPS charter?

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

Yes

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

No

Jim

> 
> Russ & Tim
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email