Re: [lamps] Magnus Westerlund's Block on charter-ietf-lamps-04-02: (with BLOCK)

Russ Housley <housley@vigilsec.com> Thu, 05 December 2019 14:56 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 39B50120013 for <spasm@ietfa.amsl.com>; Thu, 5 Dec 2019 06:56:35 -0800 (PST)
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=unavailable 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 H3Oscduq9b1j for <spasm@ietfa.amsl.com>; Thu, 5 Dec 2019 06:56:33 -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 100D112002E for <spasm@ietf.org>; Thu, 5 Dec 2019 06:56:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6730A300B31 for <spasm@ietf.org>; Thu, 5 Dec 2019 09:56:31 -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 aryDIBZCTrhZ for <spasm@ietf.org>; Thu, 5 Dec 2019 09:56:29 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id EA5DE300A3B; Thu, 5 Dec 2019 09:56:28 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <157555728863.16390.3630034252134851529.idtracker@ietfa.amsl.com>
Date: Thu, 05 Dec 2019 09:56:29 -0500
Cc: IESG <iesg@ietf.org>, LAMPS WG <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <437ABB37-76FB-4BA1-A619-3B4DB04C82DB@vigilsec.com>
References: <157555728863.16390.3630034252134851529.idtracker@ietfa.amsl.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/dYXiaNtAxKTduTxO7G_ZDFosAa4>
Subject: Re: [lamps] Magnus Westerlund's Block on charter-ietf-lamps-04-02: (with BLOCK)
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: Thu, 05 Dec 2019 14:56:35 -0000


> On Dec 5, 2019, at 9:48 AM, Magnus Westerlund via Datatracker <noreply@ietf.org> wrote:
> 
> Magnus Westerlund has entered the following ballot position for
> charter-ietf-lamps-04-02: Block
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-lamps/
> 
> 
> 
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
> 
> Regarding:
> 
> The LAMPS WG may produce
> clarifications where needed, but the LAMPS WG shall not adopt
> anything beyond clarifications without rechartering.
> 
> ... may produce clarifications ...
> 
> I would argue that this allows for updates specifications that doesn't change
> the scope of the specification. Some clarifications may result in a actual
> change of a prior WG consensus decision. If that is what is intended, then
> fine. But I would appreciate some clarification on what type of work is
> actually expected here.

There is not intent to change previous consensus.  In Singapore, these were discussed as likely work:

  - draft-richardson-lamps-rfc7030est-clarify
  - draft-turner-5480-ku-clarifications
  - draft-housley-lamps-cms-update-alg-id-protect

I'm not sure how you want to constrain the charter beyond clarifications.

Russ