Re: [openpgp] Éric Vyncke's No Objection on charter-ietf-openpgp-02-02: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Thu, 26 November 2020 02:44 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDA93A0C4F; Wed, 25 Nov 2020 18:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 gJ3_MXMgFH5O; Wed, 25 Nov 2020 18:44:55 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BA113A0C11; Wed, 25 Nov 2020 18:44:54 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AQ2iiD8019316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Nov 2020 21:44:49 -0500
Date: Wed, 25 Nov 2020 18:44:44 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael Richardson <mcr@sandelman.ca>
Cc: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>, openpgp@ietf.org, openpgp-chairs@ietf.org
Message-ID: <20201126024444.GT39170@kduck.mit.edu>
References: <160456975729.19433.13353452999589156795@ietfa.amsl.com> <14483.1604596676@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <14483.1604596676@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/VlklW8FYkb0t-uxgxXsOW5pP348>
Subject: Re: [openpgp] Éric Vyncke's No Objection on charter-ietf-openpgp-02-02: (with COMMENT)
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2020 02:45:03 -0000

On Thu, Nov 05, 2020 at 12:17:56PM -0500, Michael Richardson wrote:
> Éric Vyncke via Datatracker <noreply@ietf.org> wrote:
>     > 1) is it necessary to include the first four paragraphs about the
>     > history ?
> 
> I think so.
> 
>     > 2) the charter insists on 'no delay' but the previous version of the
>     > charter is dated 2015... ;-)
> 
> well, that refers to new work, right?

The only "delay" in this text is saying that "if you work on stuff other
than the core deliverable, it can't delay the core deliverable".  So yes,
it refers to the "new" (non-core) work, regardless of any absolute delay in
the core work.

>     > 3) is the word 'entertain' the right one in "OpenPGP may be entertained
>     > by the working group" ? For a non-English speaker, the word 'entertain'
>     > is about getting fun but there seems to be other meaning
> 
> yes, it's correct.

Agreed.
I thought about alternatives like "considered" or "adopted" but neither has
quite the same connotation.  So I left this unchaged, at least for now.

>     > 5) I do not know about the context, but the last paragraph looks to me
>     > like requesting a WGLC before adoption. Also, it requires two reviews
>     > but what will happen if those two reviews are negative ?
> 
> It is odd.
> I think though, that the intent is WG is not going to standardize things that don't
> have support of a few implementors.

Yes; we need to have people looking at it.  I also left this unchanged (for
now), since if the reviews are negative that will be used as input to any
determination of consensus to adopt.

Thanks for the review Éric, and the responses Michael,

Ben