IETF Logo Mail Archive

Re: [lamps] Proposed charter update regarding clarifications

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 27 July 2019 21:42 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 E7A0312008C for <spasm@ietfa.amsl.com>; Sat, 27 Jul 2019 14:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 111gaz-_UhsJ for <spasm@ietfa.amsl.com>; Sat, 27 Jul 2019 14:42:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFFC4120052 for <spasm@ietf.org>; Sat, 27 Jul 2019 14:42:27 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id B64DA3818C; Sat, 27 Jul 2019 17:42:05 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A8C595D3; Sat, 27 Jul 2019 17:42:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>
cc: LAMPS WG <spasm@ietf.org>
In-Reply-To: <3DB1B550-26FA-4F93-8CFA-434C1F8811D1@vigilsec.com>
References: <3DB1B550-26FA-4F93-8CFA-434C1F8811D1@vigilsec.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sat, 27 Jul 2019 17:42:25 -0400
Message-ID: <24985.1564263745@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/rpg4kqCuwpdE6Ye8F1fhIWoHMRM>
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: Sat, 27 Jul 2019 21:42:30 -0000

Russ Housley <housley@vigilsec.com> wrote:
    > At the meeting in Montreal, we suggested a charter update to allow
    > clarifications.  I suggest:

This change would seem to work for my document and subsequent equivalent
ones.

    > 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://www.ietf.org/mailman/listinfo/spasm

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email