Re: [Trans] Summary of DISCUSS items for draft-ietf-trans-rfc6962-bis

Paul Wouters <paul@nohats.ca> Wed, 03 June 2020 22:51 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 D9DC33A0895 for <trans@ietfa.amsl.com>; Wed, 3 Jun 2020 15:51:09 -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 Fn9iZ9hJTfvk for <trans@ietfa.amsl.com>; Wed, 3 Jun 2020 15:51:07 -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 103C93A0882 for <trans@ietf.org>; Wed, 3 Jun 2020 15:51:06 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49ckfJ4DQrzMC3; Thu, 4 Jun 2020 00:51:04 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1591224664; bh=rwhVzWwcs/GdMA2P6e3xHx56hjNpIme7J49DVfsxkdg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=m6nItERsGS3iqdNNH2NC5GycQw12yIhLKClZ35rryRKmLAzZDAvz3QjiCKlU6Jy5c i+WpUe3ZJRzq+G6ChoLMi47O/NhqevkuKPto0JcRfLIXq5l7hPjs3v0lsxZinZuQuU xFX5edvKtUKNcxrF5vGkVzw62YL5oO573iWPKiZk=
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 6f7-lBuF74cJ; Thu, 4 Jun 2020 00:51:03 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 4 Jun 2020 00:51:03 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 8535C6029BA2; Wed, 3 Jun 2020 18:51:02 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 816CB66B7C; Wed, 3 Jun 2020 18:51:02 -0400 (EDT)
Date: Wed, 03 Jun 2020 18:51:02 -0400
From: Paul Wouters <paul@nohats.ca>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
cc: "trans@ietf.org" <trans@ietf.org>
In-Reply-To: <53BD0D75-D08B-4EDC-A3DC-43627ABBDF34@akamai.com>
Message-ID: <alpine.LRH.2.22.394.2006031850030.31879@bofh.nohats.ca>
References: <0326AF38-C3C7-43D8-824F-31D0E9879564@akamai.com> <847f0ed9ec8c4dbe9233b386b1af3ef3@cert.org> <53BD0D75-D08B-4EDC-A3DC-43627ABBDF34@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/UiZin9fkpvEoKDnXO4RkShhKk10>
Subject: Re: [Trans] Summary of DISCUSS items for draft-ietf-trans-rfc6962-bis
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, 03 Jun 2020 22:51:10 -0000

On Wed, 3 Jun 2020, Salz, Rich wrote:

> By "compare the two timelines," I meant look at TLS 1.3 draft history and TRANS draft history.  If it doesn't mean anything to others, that's fine.
>
> I still maintain this is cruelty.  But then, I'm not an author, nor a WG member, nor an ex-chair.

I'm going to poke the right people to get those DISCUSS items cleared.

As a chair, I should have picked this up sooner. My apologies to everyone.

Paul