Re: [therightkey] Draft charter for a Transparency Working Group

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 12 December 2013 15:33 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF96B1AE329 for <therightkey@ietfa.amsl.com>; Thu, 12 Dec 2013 07:33:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 TbWjclee_KNj for <therightkey@ietfa.amsl.com>; Thu, 12 Dec 2013 07:33:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD7A1AE30C for <therightkey@ietf.org>; Thu, 12 Dec 2013 07:33:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D2D2EBE9C; Thu, 12 Dec 2013 15:33:39 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wd0yOBJQ+A0I; Thu, 12 Dec 2013 15:33:38 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.42.29.42]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 316C4BE79; Thu, 12 Dec 2013 15:33:38 +0000 (GMT)
Message-ID: <52A9D752.2060303@cs.tcd.ie>
Date: Thu, 12 Dec 2013 15:33:38 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ben Laurie <benl@google.com>
References: <CABrd9SSzGJy18tf_iR5jFNk-sJyX66OPhmM4H23K5X2ZpWniyQ@mail.gmail.com> <52A9AB84.6090609@cs.tcd.ie> <CABrd9STXJ-_hbfKV3NraQHvAFzcqZ9aCi4v=Pur82yLtCZk-MQ@mail.gmail.com>
In-Reply-To: <CABrd9STXJ-_hbfKV3NraQHvAFzcqZ9aCi4v=Pur82yLtCZk-MQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "therightkey@ietf.org" <therightkey@ietf.org>
Subject: Re: [therightkey] Draft charter for a Transparency Working Group
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 15:33:48 -0000

On 12/12/2013 03:23 PM, Ben Laurie wrote:
> I want to generate standards-track RFC(s) for 6962-bis, but other
> stuff could proceed in parallel. I don't want to hold up 6962-bis for
> that other stuff, though.

What requirements are there to be able to also
use a 6962bis log instance or piece of s/w for
another transparency-for-X thing?

If there are none or its ok as a best-effort
thing then working in parallel seems ok, but if
there's a strong desire to be able to use the
same log instance or s/w for more than one
thing, aren't there dangers there?

I've no particular opinion as to what's right
here btw, but its a fairly typical way in which
a WG might trip up and can lead to the WG
convincing themselves to step back to start
from use-cases, blah, requirements, blah,
architecture, blah etc. after a big and non-fun
argument.

Better to figure it out and have some sort of
consensus on that kind of thing up front if
possible.

S.