Re: [lamps] Proposed charter update regarding clarifications

Ryan Sleevi <ryan-ietf@sleevi.com> Sat, 27 July 2019 16:20 UTC

Return-Path: <ryan.sleevi@gmail.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 75929120024 for <spasm@ietfa.amsl.com>; Sat, 27 Jul 2019 09:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.558
X-Spam-Level:
X-Spam-Status: No, score=-1.558 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.091, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 7SrzonzkA_l2 for <spasm@ietfa.amsl.com>; Sat, 27 Jul 2019 09:20:08 -0700 (PDT)
Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FC5D12001A for <spasm@ietf.org>; Sat, 27 Jul 2019 09:20:08 -0700 (PDT)
Received: by mail-ed1-f43.google.com with SMTP id k8so55731305edr.11 for <spasm@ietf.org>; Sat, 27 Jul 2019 09:20:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b/9nYU+ag+c2dkMVUiiOZepDXf0UQrLEfbPRkHXoEWQ=; b=SRuwRwdTJ+jJBAaYq+jsnXK3mnPGbCoSD7OerP5LrafZnhucGyK3ere8fuNnJ7NUHl MS1GdIMqaACXdKIySI7FoDlO5EEhPPJ9KbVomaoVxarMclcF2PNOdkZvvWCNKCtwASjq 2L3RszYVByAtZU8u0ZTdCImVN9ntVIr7MdZZxw4QgIDc73it+uLulV5YOzsVUvluxURB vvttX3W+9GodGRZ1UgLtEBL1k6jf4S3IGE38/rjfT0r7P8O74/9/nXDnp8cyfmIejX5P /r+N3qk2PG9bdh0mggl2EmUreeaguMMUQQ+Uu/ex+j/YZPX2q7/WnKQHEM6oonAj7hmL KuhQ==
X-Gm-Message-State: APjAAAXijRXpP9dDJALSpB0Xr49SarQQmdyrs6LWPfrMUZ4stzFQyFE4 A2gx5wYWTrVhS4pm3ak27jvjMoXKZ/k=
X-Google-Smtp-Source: APXvYqwJreZ9LvUyLHGpuu8tMI45Jcy7/MxPD3WWH6nByvJDyvhrWMZomv1NWp8LICHpKlFLSRHrWg==
X-Received: by 2002:aa7:c393:: with SMTP id k19mr87703466edq.76.1564244406821; Sat, 27 Jul 2019 09:20:06 -0700 (PDT)
Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com. [209.85.128.44]) by smtp.gmail.com with ESMTPSA id i8sm14847507edg.12.2019.07.27.09.20.06 for <spasm@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Sat, 27 Jul 2019 09:20:06 -0700 (PDT)
Received: by mail-wm1-f44.google.com with SMTP id u25so39651321wmc.4 for <spasm@ietf.org>; Sat, 27 Jul 2019 09:20:06 -0700 (PDT)
X-Received: by 2002:a1c:cb01:: with SMTP id b1mr21639716wmg.69.1564244406381; Sat, 27 Jul 2019 09:20:06 -0700 (PDT)
MIME-Version: 1.0
References: <3DB1B550-26FA-4F93-8CFA-434C1F8811D1@vigilsec.com> <46773340-6bba-6c54-7049-c6ec30488174@cs.tcd.ie>
In-Reply-To: <46773340-6bba-6c54-7049-c6ec30488174@cs.tcd.ie>
From: Ryan Sleevi <ryan-ietf@sleevi.com>
Date: Sat, 27 Jul 2019 12:19:54 -0400
X-Gmail-Original-Message-ID: <CAErg=HHJinZzoUuAJ76Js6YPFegr0jtwjpr2KTvU+1-JQASQPw@mail.gmail.com>
Message-ID: <CAErg=HHJinZzoUuAJ76Js6YPFegr0jtwjpr2KTvU+1-JQASQPw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: LAMPS WG <spasm@ietf.org>, Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="0000000000002f329c058eac08c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/QJZa-7x7XFH1s-SDpHbYLqQXoX4>
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 16:20:11 -0000

On Sat, Jul 27, 2019 at 12:03 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> On 27/07/2019 12:40, Russ Housley wrote:
> > 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?
>
> Seems like another step on the road to re-creating PKIX
> which at the end produced pointless paper. IMO nothing
> should be done in this WG unless there's evidence the
> work will be implemented and deployed.
>
> S.


While I share the general sentiment, there is at least one clarification
which has clear signs of deployment if there is IETF consensus on the text
-
https://tools.ietf.org/id/draft-turner-5480-ku-clarifications-00.html

For example,
https://github.com/zmap/zlint/pull/293 is used by the majority of the
publicly trusted CAs, directly or indirectly, and would actively enforce
such text.

I too appreciate a narrowed scope, and wouldn’t be too miffed if any/every
clarification was a matter for rechartering, and the WG only looked at
chartering with this in scope.