IETF Logo Mail Archive

Re: [lamps] Proposed charter update regarding clarifications

Russ Housley <housley@vigilsec.com> Mon, 29 July 2019 14:22 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 92BB9120100 for <spasm@ietfa.amsl.com>; Mon, 29 Jul 2019 07:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 SdvLn3o6iCEh for <spasm@ietfa.amsl.com>; Mon, 29 Jul 2019 07:22:25 -0700 (PDT)
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 C236D1200C4 for <spasm@ietf.org>; Mon, 29 Jul 2019 07:22:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BBDC2300AA2 for <spasm@ietf.org>; Mon, 29 Jul 2019 10:03:07 -0400 (EDT)
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 Rm9d-HEgRtAi for <spasm@ietf.org>; Mon, 29 Jul 2019 10:03:06 -0400 (EDT)
Received: from [172.20.3.215] (unknown [50.235.191.99]) by mail.smeinc.net (Postfix) with ESMTPSA id 1D2B03004AF; Mon, 29 Jul 2019 10:03:06 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DB7PR10MB2411F2A8FE1776633516C1EEFEDD0@DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 29 Jul 2019 10:22:22 -0400
Cc: LAMPS WG <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D08454BE-8EA4-4221-AD6E-ECEF6A84958A@vigilsec.com>
References: <3DB1B550-26FA-4F93-8CFA-434C1F8811D1@vigilsec.com> <DB7PR10MB2411F2A8FE1776633516C1EEFEDD0@DB7PR10MB2411.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/3S2JogIRg89TPAOw8S-IOHmNTuU>
Subject: Re: [lamps] Proposed charter update regarding clarifications
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, 29 Jul 2019 14:22:28 -0000

How does the update to RFC 5480 about key usage fit here?

Russ

> On Jul 29, 2019, at 8:13 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote:
> 
> I would be happy with the current text. But I guess there will be the need for many updates at least with regard to support of upcoming crypto algorithms. Therefore the new text will ease the processes.
> Finally it will be a trade-off between administrative overhead vs. risk of 'pointless paper'. Finally I am with Stephen, that nothing should be done without people willing to implement it.
> 
> Hendrik
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Spasm <spasm-bounces@ietf.org> Im Auftrag von Russ Housley
>> Gesendet: Samstag, 27. Juli 2019 13:40
>> An: LAMPS WG <spasm@ietf.org>
>> Betreff: [lamps] Proposed charter update regarding clarifications
>> 
>> At the meeting in Montreal, we suggested a charter update to allow
>> clarifications.  I suggest:
>> 
>> OLD:
>> 
>> In addition, the LAMPS WG may investigate other updates to documents
>> produced by the PKIX and S/MIME WGs, but the LAMPS WG shall not adopt
>> any of these potential work items without rechartering.
>> 
>> NEW:
>> 
>> In addition, the LAMPS WG may investigate other updates to documents
>> produced by the PKIX and S/MIME WG. The LAMPS WG may produce
>> clarifications where needed, but the LAMPS WG shall not adopt anything
>> beyond clarifications without rechartering.
>> 
>> Thoughts?
>> 
>> Russ
>> _______________________________________________
>> Spasm mailing list
>> Spasm@ietf.org
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
>> .ietf.org%2Fmailman%2Flistinfo%2Fspasm&amp;data=02%7C01%7Chendrik.
>> brockhaus%40siemens.com%7C28e8b2e7640e486105ab08d712873521%7C38
>> ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C636998244239259100&am
>> p;sdata=5wTBzw09KsNOVU%2FOZAIi94fIzXu2UZ%2Bm%2B12sIf%2FRS4w%3
>> D&amp;reserved=0
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email