[Openpgp-dt] Resurrecting the design team?

Daniel Huigens <d.huigens@protonmail.com> Thu, 15 September 2022 16:11 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 F2DDCC1526E5 for <openpgp-dt@ietfa.amsl.com>; Thu, 15 Sep 2022 09:11:09 -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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=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 qNEo_BzYnRra for <openpgp-dt@ietfa.amsl.com>; Thu, 15 Sep 2022 09:11:05 -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 211EFC152566 for <openpgp-dt@ietf.org>; Thu, 15 Sep 2022 09:11:05 -0700 (PDT)
Date: Thu, 15 Sep 2022 16:10:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1663258263; x=1663517463; bh=wZoSgqEiZhewX10oXohVjydFkQoZQ40xTEZO4TIfkw8=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID; b=qnCt+5+PwY60SBPC0V6mojdTvj5cUJ+FTQfJLAajuXWcz7o5Qp8gHUHx4gpPsF0Hd fHfXv2za604HE0aUWK5YHFrSTN5cGyL0UtNO9Z96oUoffIetm1icA6VTREdKwaQrDI cPzaMswLdBdLsZ8YmkbKlAX0sTjL1lqOCYjSOua7c2uzCG0uQ7v2st7VT4ufWYP+C6 PBv3UkCYBDo40WJZEGZzlhDa/PvQcmQmMmmJ4LyszFgpQrCDYw5X35nRylb2SbSEmF zUl7dkPxU0oMe76IOdEW0nHDyXMRjWE+ymy4plbDMkm6Ng4mUCUPbDUWHgXS6geVRr 0/bJQwlcUdTGA==
To: "openpgp-dt@ietf.org" <openpgp-dt@ietf.org>
From: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <kmG4ljo5UX7pxlqL3rLQJfi1-kY_usIv8FNPtC4Q6HJtPgng5P4VvLaVnOyPPd6WPdVKBQOKMdH2JX1wAIXlywZXK9KVFj5egVpSavorSnw=@protonmail.com>
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/_WDz3nwl3-z5IdSv3VCmhBxHh30>
Subject: [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 16:11:10 -0000

Hi all,

Hope everyone is doing well.

Before IETF 114, we agreed not to meet, and have discussions in the WG
instead. At IETF 114, I think we came to some clear decisions based on
the polls that were held, but those decisions haven't been "executed"
yet, although there are some MRs for them.

There are also some editorial MRs that are already approved, and some
new items that came up on the WG list after IETF 114 (e.g. the context
binding / separation) that I think would be good to discuss in the
design team.

So - I would propose that we meet a couple of times before IETF 115, so
that we can make some progress on those items. And then, hopefully we
can report at IETF 115 that the changes discussed in IETF 114 have been
made, and potentially bring new points up for discussion, if necessary.

If you agree: on the practical side; I'm off next week, but I would be
available the week after at the old slot of 12:30 UTC on Tuesday
(September 27). But other times may work as well.

Let me know what you think!

Best,
Daniel