IETF Logo Mail Archive

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

Ben Laurie <benl@google.com> Thu, 12 December 2013 11:00 UTC

Return-Path: <benl@google.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92BB61AE216 for <perpass@ietfa.amsl.com>; Thu, 12 Dec 2013 03:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.38
X-Spam-Level:
X-Spam-Status: No, score=-1.38 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
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 wBZg1mmOpT38 for <perpass@ietfa.amsl.com>; Thu, 12 Dec 2013 03:00:02 -0800 (PST)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1A05C1AE020 for <perpass@ietf.org>; Thu, 12 Dec 2013 03:00:02 -0800 (PST)
Received: by mail-ve0-f170.google.com with SMTP id oy12so160770veb.29 for <perpass@ietf.org>; Thu, 12 Dec 2013 02:59:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eacEjswDijWna5jYWqt65RIk1B5Rh7IWLNcsQxUgtH8=; b=JTW4BMkZNYr1+ntUmmrHyPbzjInbfEBMu1/wzt+7r4IoMSlTsPoVFhOh+RjoANFFhs Hudlpb3zRZfG1ikhnEVruNUSsSSSsCIjgA9By8o1Y3PIZqWToNKoGDegUegcEPyP27dQ wJ+/h8WGnukZZLMtTltxgaw6Cgb6CwFEsxXp8Rx8WGK0CIj7duPZwLUB6M9farX11+aO lXGCXb3D4Yy8zhL0ACRozevkZaofDC4Wh7Vn+WMXIE8EPN3xhCnl+VhR/nM1D8uLM0TT 2nTGAY6G+KTDZaUoOXatfOAa/BsLM/IuhQbTmfzjOiTR/Vw1rEIWeiXifNi1Y4DxchUZ x8IQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eacEjswDijWna5jYWqt65RIk1B5Rh7IWLNcsQxUgtH8=; b=A7+MAiflfWum2j2VArJI5mmRD8OamUVW2Y20yb23NE6ml4Zk0wCO3blDYpNU8suI+o 0KSbUvkH1nYdUYKetkUFZvAe61udrcfpZF+xXeUmznQr/zyWuLMvnEZYTvoeEdc2qNW0 1YjpORgZ+FjnFvS6QeBTq0vmoRpaslo1G8UtdvgJLEpqYb9qFxicwYc5pwFg3QrJDjLX sWwGyPF0rZXXEn5Pqya+4/KFEDWbb72BwHk6iXRuanGefkBkGaeqLRlr69EyWHFtLQKh r87JNNP0N4TmxjfDqpyDarghYjLHY7zmDRAJ571l7alJsYkFAnc4QQI1XWg/frnlSeZe qNZQ==
X-Gm-Message-State: ALoCoQnuRWoVixFFDVQBfRGQiwJ5T9bgjaibynvGIfnjTNwd2YVv0b/xOy0y7iGiCX+SmpN1gkP1UZVTdwhghRdqqSYEh0D7vLlkHhT5md3VHGN7gLBU6Oedt7XvCoy0LdWlDfaZfwCWaCCmy4/W4lNpZiQDidwOmfXefq1bm8t/ZRtovSHQ96+qdjpxHJosYOuEuuUwotsl
MIME-Version: 1.0
X-Received: by 10.220.144.80 with SMTP id y16mr3265725vcu.4.1386845995978; Thu, 12 Dec 2013 02:59:55 -0800 (PST)
Received: by 10.52.183.65 with HTTP; Thu, 12 Dec 2013 02:59:55 -0800 (PST)
In-Reply-To: <52A8E0E9.5020409@dcrocker.net>
References: <CABrd9STYF166vXEXNneJfPyfo5VG3LPKmzyZpAhvYnDTsy_U9g@mail.gmail.com> <52A8B1D0.2080304@dcrocker.net> <CABrd9SS9FGsm-waznAHeMr33XzprhRF=DXVjknyL-7bOyArAxg@mail.gmail.com> <CAMm+LwjNXpszKMqXr231Vti=pfwYn98Fgmuv1T5M__nhGmZHQw@mail.gmail.com> <CABrd9SSYnBRtecDSwUZUjvKJPLB+XX6Kk_9NHtQ=X-5jo4jGxQ@mail.gmail.com> <52A8E0E9.5020409@dcrocker.net>
Date: Thu, 12 Dec 2013 10:59:55 +0000
Message-ID: <CABrd9ST+CKNNHZ-jLd1=boeWUh-sjZf1WF5fmayCF7+DjnD65w@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Dave Crocker <dcrocker@bbiw.net>, "therightkey@ietf.org" <therightkey@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: perpass <perpass@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Subject: Re: [perpass] Draft charter for a Transparency Working Group
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 11:00:03 -0000

[please include therightkey on replies]

On 11 December 2013 22:02, Dave Crocker <dhc@dcrocker.net> wrote:
> On 12/11/2013 1:56 PM, Ben Laurie wrote:
>>
>> Agree, I just want to be able to refer to 6962 for what
>> "cryptographically verifiable log" means.
>
>
>
> Being able to cite a doc that defines the term is always nice; so yes,
> please do cite freely.
>
> My own view is that charters need to have some pedagogy, since one goal of a
> charter is to explain the work to folk who might get involved (eventually).
> While a citation is formally sufficient, it's not the best pedagogy.  So I
> tend to prefer to have a charter be somewhat self-explanatory about its
> basic constructs, unless they are already very well established in industry.
>
> In this case, I think what you mean is /not/ obvious to a reader who is not
> already immersed in the topic.  So some sort of superficial explanation
> would help, with the citation pointing the reader to the deeper discussion.

How about this footnote?

"A cryptographically verifiable log is an append-only log of hashes of
more-or-less anything that can prove its own correctness
cryptographically. See RFC 6962,
http://www.links.org/files/CertificateTransparencyVersion2.1a.pdf and
http://www.links.org/files/RevocationTransparency.pdf for background."

v2.31.3 | Report a Bug | By Email | System Status