[Trans] Meeting: go or no go

Paul Wouters <paul@nohats.ca> Wed, 14 July 2021 15:01 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239353A1D1B for <trans@ietfa.amsl.com>; Wed, 14 Jul 2021 08:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 S-RcHVpo08sQ for <trans@ietfa.amsl.com>; Wed, 14 Jul 2021 08:01:29 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 256163A1D19 for <trans@ietf.org>; Wed, 14 Jul 2021 08:01:28 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4GQ10y0YKMzCDs for <trans@ietf.org>; Wed, 14 Jul 2021 17:01:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1626274882; bh=7lXyk9NOWgWzF8EkcvFiTJ5ctemXXFZOqo1+g7NwA+s=; h=Date:From:To:Subject; b=NdKBZd0yIkvb1BmaMji2gmZARS1X+p58DrGePBBQjERDRb1ousdWlA2b3+ak//8yK fa3XPgfo/LY6tI0RRyJMjS4LxqxWZgSsP8K1ykpuvZtYziMj+RzBW0+SE2tGPvCoCN /8WrAmNMBBrIoXTrtMxCHw+Cf86CrER5dFt65D2w=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id XXAc8PbvLRna for <trans@ietf.org>; Wed, 14 Jul 2021 17:01:19 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <trans@ietf.org>; Wed, 14 Jul 2021 17:01:19 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id AA523C87F8; Wed, 14 Jul 2021 11:01:18 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id A70FEC87F7 for <trans@ietf.org>; Wed, 14 Jul 2021 11:01:18 -0400 (EDT)
Date: Wed, 14 Jul 2021 11:01:18 -0400
From: Paul Wouters <paul@nohats.ca>
To: Trans <trans@ietf.org>
Message-ID: <2377b74-9d69-d845-345e-db3d281299ca@nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/oN8s-TL0wVN4IpZACf0yphnT300>
Subject: [Trans] Meeting: go or no go
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2021 15:01:34 -0000

Hi,

The bis draft has now made it through the IESG and is just
waiting on the announcement:

https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/

Thanks a lot to Rich Salz for chasing the IESG members in the last
few months and getting us over the finish line. And thanks to Rob
for being available to merge in the last few changes.

The only very minor item left at this point can be resolved with the
RFC Editor.

https://github.com/google/certificate-transparency-rfcs/pull/338

The meeting was originally scheduled to try and resolve any remaining
IESG issues. Since this is now done, the only thing on our agenda is
whether we want to continue as a group and pick up any of the items
that got stalled before, or whether we will close down the WG.

If anyone wants to pick up their drafts or propose new ones, now is
the time to ask for speaking slot for our IETF 111 meeting. If we
don't get any items, then I think we can take that as a clear signal
that we should cancel the IETF 111 meeting, and close the WG.

Paul & Melinda