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

Phillip Hallam-Baker <hallam@gmail.com> Thu, 12 December 2013 13:58 UTC

Return-Path: <hallam@gmail.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 C968D1AE2CF; Thu, 12 Dec 2013 05:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 J7HML06Udnjv; Thu, 12 Dec 2013 05:58:38 -0800 (PST)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD0E1AE2B5; Thu, 12 Dec 2013 05:58:38 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id z2so2512693wiv.6 for <multiple recipients>; Thu, 12 Dec 2013 05:58:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tBFcfDpAKp4bMDkp2SeS+kWP177NdjlQx41ferR2l20=; b=ssjFnXmxC2Qvd7OtPmSoGJHCNfmhGsS7aGi6SmRXrtymheL3zirqp7czehp4rKoxWW JgxnldM9OZKnh3hk4Qxy5HTJC8vUj+hUjy6M7Ct3wGfoVXWCE1Yx5I+L9uLLrt1TQATY 7c1uRKkkD7EmAK0K9wPZknDbU6ukmxWd65oqz5ut2DPgfP7eRmm2GfPjfiNGfuTkawrf h21YIj4htTGDWWPumCfFzEl3FnKzUvBhwfWk0mxAvJj7VbaU8vUTXlHsnZz1VrXo5Tvy VFM2sRrByQJtnVdBZ+L4LenrUjK7VnOAujEk1pMXhn45A9jfkUujYT/pAvAmm8THUdLi OHXQ==
MIME-Version: 1.0
X-Received: by 10.180.109.201 with SMTP id hu9mr7690708wib.59.1386856711905; Thu, 12 Dec 2013 05:58:31 -0800 (PST)
Received: by 10.194.243.136 with HTTP; Thu, 12 Dec 2013 05:58:31 -0800 (PST)
In-Reply-To: <CABrd9SRyOCSTjxJ5B-vaiaF_Quos3K7070dL+n8-Nky-8d4+fw@mail.gmail.com>
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> <C32FC8CD-7EA5-479B-89F4-88556301F14B@gmail.com> <CABrd9SRyOCSTjxJ5B-vaiaF_Quos3K7070dL+n8-Nky-8d4+fw@mail.gmail.com>
Date: Thu, 12 Dec 2013 08:58:31 -0500
Message-ID: <CAMm+LwgNrL1a18=chEk_rdbeenyA=+cKmnhAPQKLDFqD8fdoDA@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary="e89a8f2356bdaae8fc04ed56bdf3"
Cc: "saag@ietf.org" <saag@ietf.org>, perpass <perpass@ietf.org>, Douglas Otis <doug.mtview@gmail.com>, Dave Crocker <dcrocker@bbiw.net>
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 13:58:42 -0000

On Thu, Dec 12, 2013 at 6:06 AM, Ben Laurie <benl@google.com> wrote:

> On 11 December 2013 23:48, Douglas Otis <doug.mtview@gmail.com> wrote:
> >
> > On Dec 11, 2013, at 1:56 PM, Ben Laurie <benl@google.com> wrote:
> >
> > Agree, I just want to be able to refer to 6962 for what
> > "cryptographically verifiable log" means.
> >
> >
> > Dear Ben,
> >
> > There was an eXtensible Access Method, XAM, developed by SNIA.  This
> > permitted vendors a means to implement strategies for handling massive
> > amounts of data in a manner called Content Addressable Storage, such as
> > EMC^2's Centera product. The data blobs create multiple secure hashes
> that
> > act within a standardized label. The blobs are combined with timestamps
> and
> > XML MIME tags. This removes a need for difficult to manage file
> hierarchy.
> > One of the benefits of this scheme is data can not change without
> detection.
>
> A brief romp through the spec suggests that XUIDs could be hashes, but
> don't have to be. In particular, identical XSets do not have to have
> identical XUIDs.
>
> In the case where they are hashes (or are otherwise one-to-one linked
> to XSets), then a transparent log might well be usefully applied to
> them.
>

If we get into that area I have to point out that I am currently engaged by
a client who is defending a case in which a relevant patent is being
asserted.


-- 
Website: http://hallambaker.com/