Re: [Openpgp-dt] Resurrecting the design team?

Daniel Huigens <d.huigens@protonmail.com> Thu, 15 September 2022 17:30 UTC

Return-Path: <d.huigens@protonmail.com>
X-Original-To: openpgp-dt@ietfa.amsl.com
Delivered-To: openpgp-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF18C1524A9 for <openpgp-dt@ietfa.amsl.com>; Thu, 15 Sep 2022 10:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgGGa0bzBNvR for <openpgp-dt@ietfa.amsl.com>; Thu, 15 Sep 2022 10:30:00 -0700 (PDT)
Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E4FFC1527A4 for <openpgp-dt@ietf.org>; Thu, 15 Sep 2022 10:30:00 -0700 (PDT)
Date: Thu, 15 Sep 2022 17:29:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1663262997; x=1663522197; bh=QrWiCXTF10hAUheTrvbxCn4sg+Jj2LpOIv01uFa2+xQ=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=XSRLVIE66MaZwV7zhN37dqKaTT1bOgsBKbNvQBTDGkBx0PY1W8vWtd7kC+nAwNxd0 o3DQC+l+eoP+78MhQwEyBOAfn1KnW2qnfmeyAfRdMrmKsf7nfPs8FcaRdsLL02gW81 z8usGK0zwo7haShrF4n6rIWyMldLTpX1pKOqsa7jHPPIJ+61Nt5IgfPh/PdaSWZnId SHQ+QMv9xtKd0Og4ZDfvISw8PV85ptFtGcIfvwITQinVuYgSLDnT9uV0OLeQL3t0om elVZL36EvkkNHK172pCXjJdPI19/27M9xxFvs7C+yjF5buCLMuV9JN4feos/1+ocr7 +pMl1R5Aday4g==
To: Paul Wouters <paul@nohats.ca>
From: Daniel Huigens <d.huigens@protonmail.com>
Cc: "openpgp-dt@ietf.org" <openpgp-dt@ietf.org>
Message-ID: <o9pTGDfxNuczFtpsnEScsaXcEf-19hIhlmNnmDag9V0FSnC2-KsMhwa_qzUWuvPIachBr0Wc-dUCovjzZXSfBF0v__6BKnpVIMofXPnpp2k=@protonmail.com>
In-Reply-To: <9d1c4b68-b332-386e-1c7-7fec668bc54@nohats.ca>
References: <kmG4ljo5UX7pxlqL3rLQJfi1-kY_usIv8FNPtC4Q6HJtPgng5P4VvLaVnOyPPd6WPdVKBQOKMdH2JX1wAIXlywZXK9KVFj5egVpSavorSnw=@protonmail.com> <9d1c4b68-b332-386e-1c7-7fec668bc54@nohats.ca>
Feedback-ID: 2934448:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp-dt/5D_gJnucXD0BrI5_ihvpnZgNc2k>
Subject: Re: [Openpgp-dt] Resurrecting the design team?
X-BeenThere: openpgp-dt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OpenPGP working group design team <openpgp-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp-dt>, <mailto:openpgp-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp-dt/>
List-Post: <mailto:openpgp-dt@ietf.org>
List-Help: <mailto:openpgp-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp-dt>, <mailto:openpgp-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2022 17:30:04 -0000

On Thursday, September 15th, 2022 at 09:37, Paul Wouters wrote:

> I am not aware of pending approved issues. I'm waiting on consensus
> calls for some items to be called by the WG chairs.

Sure. I mean, even if we don't have a consensus called yet, there were
some issues with a large majority (or even unanimity) in favor of one
direction. So I was thinking we could at least review the MRs that
address those cases in the design team, on the assumption that we
(will) have consensus on them?

One example of that is [!213], and to some extent the other MRs
referenced in [#143]. An example of unanimity was [#134], addressed by
[!206], but that one has already been approved (including by one chair;
do we need to wait for an explicit call of consensus before merging it?
Maybe the answer is yes, just checking. IMHO we can always revert stuff
if the consensus ends up going the other way.)

> I think we decided that we would talk on the main list on any issues, as
> to ensure we are not excluding the WG.

Right, but that was before IETF 114 - can we have some discussion in the
DT before bringing it back to the WG at IETF 115 again? (It's an honest
question, I don't know the answer. But the discussion on the WG list is
moving very slowly, if at all :') So I thought having a meeting might
rekindle some momentum.)

> If it is editorial, I can pick it up as Editor.

Alright, thanks. There are some MRs with the "non-substantive" label
that fit in this category, and I would add [!199], [!201], and [!205] to
that as well, though that last one has only had one review.

> Anything bigger should
> at least be called out as having concensus by the chairs (or become a
> call to the list for consensus)

Well - for the context separation topic, for example, I tried to get
some discussion going on the WG list, but seem to have failed to do so.
But, before we try (again) to discuss it in the WG, it may be valuable
to discuss it in the DT, I think, so that we can at least gain consensus
there, hopefully?

> I have also pinged the chairs last week to move things forward :)

Thanks :)

Best,
Daniel

[!213]: https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/213
[#143]: https://gitlab.com/openpgp-wg/rfc4880bis/-/issues/143
[#134]: https://gitlab.com/openpgp-wg/rfc4880bis/-/issues/134
[!206]: https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/206
[!199]: https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/199
[!201]: https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/201
[!205]: https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/205