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

Paul Lambert <paul@marvell.com> Thu, 12 December 2013 16:48 UTC

Return-Path: <paul@marvell.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 C4A471AE028; Thu, 12 Dec 2013 08:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.566
X-Spam-Level:
X-Spam-Status: No, score=-1.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, 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 Z_TCEVqsxf1X; Thu, 12 Dec 2013 08:48:42 -0800 (PST)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD0D1AD2EC; Thu, 12 Dec 2013 08:48:42 -0800 (PST)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id rBCGmSHd019528; Thu, 12 Dec 2013 08:48:28 -0800
Received: from sc-owa.marvell.com ([199.233.58.135]) by mx0b-0016f401.pphosted.com with ESMTP id 1gpgd4n56a-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 12 Dec 2013 08:48:28 -0800
Received: from SC-vEXCH2.marvell.com ([10.93.76.134]) by SC-OWA.marvell.com ([::1]) with mapi; Thu, 12 Dec 2013 08:48:27 -0800
From: Paul Lambert <paul@marvell.com>
To: Douglas Otis <doug.mtview@gmail.com>, Ben Laurie <benl@google.com>
Date: Thu, 12 Dec 2013 08:48:26 -0800
Thread-Topic: [saag] [perpass] Draft charter for a Transparency Working Group
Thread-Index: Ac73Wfrd+LJkHtEQRe2UEqFDYRYh6A==
Message-ID: <CECF2734.2A043%paul@marvell.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>
In-Reply-To: <C32FC8CD-7EA5-479B-89F4-88556301F14B@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CECF27342A043paulmarvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2013-12-12_04:2013-12-12, 2013-12-12, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1312120072
X-Mailman-Approved-At: Thu, 12 Dec 2013 08:50:06 -0800
Cc: perpass <perpass@ietf.org>, Phillip Hallam-Baker <hallam@gmail.com>, Dave Crocker <dcrocker@bbiw.net>, "saag@ietf.org" <saag@ietf.org>
Subject: Re: [perpass] [saag] 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 16:48:44 -0000


On Dec 11, 2013, at 1:56 PM, Ben Laurie <benl@google.com<mailto: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.

Interesting … in IEEE we’re  defining ‘services’ as a hash/UUID-like identifier https://mentor.ieee.org/802.11/dcn/12/11-12-0706-00-0isd-service-discovery-proposal.pptx ).  UPnP and Bonjour are both mapped to a hash.  We’re truncating them to 6 octets … but that’s a different discussion.

In looking at Transparency for “X”, I’d suggest that the X can be an arbitrary service identified as a hash.

Paul


SNIA now seems focused on identifying individuals.  Perhaps this is an outgrowth of their data-deduplication?
http://www.snia.org/tech_activities/standards/curr_standards/xam

Regards,
Douglas Otis