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

Justus Winter <justus@sequoia-pgp.org> Tue, 27 September 2022 13:29 UTC

Return-Path: <justus@sequoia-pgp.org>
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 88A60C1522BD for <openpgp-dt@ietfa.amsl.com>; Tue, 27 Sep 2022 06:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_FROM_MTA_HEADER=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
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 V6R6QZ6ms3JD for <openpgp-dt@ietfa.amsl.com>; Tue, 27 Sep 2022 06:29:17 -0700 (PDT)
Received: from harrington.uberspace.de (harrington.uberspace.de [185.26.156.85]) (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 3ED74C1522BE for <openpgp-dt@ietf.org>; Tue, 27 Sep 2022 06:29:16 -0700 (PDT)
Received: (qmail 633 invoked by uid 500); 27 Sep 2022 13:29:13 -0000
Authentication-Results: harrington.uberspace.de; auth=pass (plain)
From: Justus Winter <justus@sequoia-pgp.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>, Paul Wouters <paul@nohats.ca>
Cc: "openpgp-dt@ietf.org" <openpgp-dt@ietf.org>
In-Reply-To: <5d6a0b12-24da-9e94-83be-f1ee456a3da9@cs.tcd.ie>
References: <kmG4ljo5UX7pxlqL3rLQJfi1-kY_usIv8FNPtC4Q6HJtPgng5P4VvLaVnOyPPd6WPdVKBQOKMdH2JX1wAIXlywZXK9KVFj5egVpSavorSnw=@protonmail.com> <9d1c4b68-b332-386e-1c7-7fec668bc54@nohats.ca> <o9pTGDfxNuczFtpsnEScsaXcEf-19hIhlmNnmDag9V0FSnC2-KsMhwa_qzUWuvPIachBr0Wc-dUCovjzZXSfBF0v__6BKnpVIMofXPnpp2k=@protonmail.com> <87czbhm2d6.fsf@europ.lan> <5d6a0b12-24da-9e94-83be-f1ee456a3da9@cs.tcd.ie>
Date: Tue, 27 Sep 2022 15:29:03 +0200
Message-ID: <87a66llzds.fsf@europ.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Rspamd-Bar: /
X-Rspamd-Report: R_MISSING_CHARSET(0.5) MIME_GOOD(-0.2) SIGNED_PGP(-2) SUBJECT_ENDS_QUESTION(1) BAYES_HAM(-0.005747)
X-Rspamd-Score: -0.705747
Received: from unknown (HELO unkown) (::1) by harrington.uberspace.de (Haraka/2.8.28) with ESMTPSA; Tue, 27 Sep 2022 15:29:13 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp-dt/34OtJRIJICHlSX6x7gMQKizXpEw>
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: Tue, 27 Sep 2022 13:29:18 -0000

Hi Stephen,

Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:

> Hi Justus,
>
> (I'll skip over details of MRs etc to process in this mail.)
>
> On 27/09/2022 13:24, Justus Winter wrote:
>
>> The OpenPGP WG mailing list has proven again to be unsuitable to get any
>> work done. 
>
> I agree that the DT was productive and can be again in
> future, but don't think this is the time to reactivate
> it. (Mainly for the reasons Paul W. stated but also as
> we need to resolve the current thread on the WG list.)
>
> It can be hard to deal with IETF WG lists yes. But that's
> really a cost of being open, so has to be borne, even if
> it's a real pain from time to time.

I disagree with the idea that "being open" means tolerating that kind of
behavior.  Being open doesn't mean giving random people the chance to
derail the process.  Being open doesn't mean letting crackpots burn out
people who are actually doing some work and are actually having a horse
in the game.

>> This is an endless drain of energy.  We need to address that
>> at some point.  Maybe close the working group and open a new one with a
>> different name.  Maybe just kick everybody and see who rejoins.
>> 
>> Is there precedent in other working groups?  E.g., are the TLS people
>> having problems with people clinging to SHA1 and dismissing AEAD as
>> pointless?  Are there threads on the MLS WG list that have 150+ mails in
>> them from random strangers bringing the WG work to a grinding halt?
>
> There's no precedent for closing a list like that, for that
> reason. The have been times when TLS was significantly side-
> tracked, and those were worse believe it or not, but the WG
> did manage to get through that, albeit with some effort.
>
>> The DT was the most successful attempt of getting anywhere since I have
>> started working in this space.  I welcome and support the motion to
>> reinstate it.
>
> Ack. I think there will come a time when that's the right
> thing to do, but it'd not, IMO, be the correct approach
> right now.

If there is actual work to be done, I will engage again.  But until that
point, I'll stay away from that toxic dumpster fire.

Best,
Justus