Re: [therightkey] Draft charter for a Transparency Working Group
"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Wed, 11 December 2013 17:45 UTC
Return-Path: <jason_livingood@cable.comcast.com>
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 745471AE0F9 for <therightkey@ietfa.amsl.com>; Wed, 11 Dec 2013 09:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level:
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 XoBLVpg-7YDR for <therightkey@ietfa.amsl.com>; Wed, 11 Dec 2013 09:45:28 -0800 (PST)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id D36481AE0E5 for <therightkey@ietf.org>; Wed, 11 Dec 2013 09:45:27 -0800 (PST)
Received: from ([24.40.56.115]) by pacdcavout01.cable.comcast.com with ESMTP id 97wm3m1.75849416; Wed, 11 Dec 2013 12:45:14 -0500
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.202]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Wed, 11 Dec 2013 12:45:14 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Ben Laurie <benl@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>
Thread-Topic: [therightkey] Draft charter for a Transparency Working Group
Thread-Index: AQHO9pHEKt3E69RZxEmGP9vf1l32hZpPkimA//+yKgA=
Date: Wed, 11 Dec 2013 17:44:26 +0000
Message-ID: <10229F86C86EB444898E629583FD4171EDEAB12A@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <52A89F9F.70604@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [24.40.56.164]
x-wiganss: 0100000001001EPACDCEXHUB02.cable.comcast.com ID0048<10229F86C86EB444898E629583FD4171EDEAB12A@PACDCEXMB06.cable.comcast.com>
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F45B35EE864161418741404FE91AF6DA@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 11 Dec 2013 17:45:29 -0000
I totally understand the problem statement. But what concrete things can you enumerate as goals/output of the WG? Jason On 12/11/13, 12:23 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote: > >Thanks Ben, > >So folks know what we're thinking and in case all the >process gibberish isn't clear to you all... > >Sean and I like the idea of doing this, and the more that >it seems to get broader support, the more we'll like it. > >Since there was already a BoF on this back at IETF-85 [1] >that concluded this was work that's relevant to do in >the IETF, we're thinking that if a crisp enough charter >can be crafted on this list then this wouldn't need another >BoF but would be ok to just be pushed into the IESG/IETF >approval process. > >What that means is that when Sean and I think we have a >good enough charter draft, then we'll put that into the >datatracker and the IESG will do an IESG-internal review >to decide if its ready to be sent out for IETF review. >If/when the IESG are ok with that going for IETF-wide >review then a mail will go to the IETF discuss list so's >anyone can comment on the proposed new WG. Then the IESG >get to look at it again, and any comments we've gotten, >and approve the new WG or not. Charter text tweaks can >be expected at each stage. > >All going well, that could result in a new WG for this >being formed early in the new year, before IETF-89 >with the WG having a first f2f meeting there presumably. > >So please comment on Ben's text and the above with that >in mind. I assume Ben will hold the pen on draft charter >text and update that as comments are received. > >And please use this list for now, since this is the >one we used for RFC 6962 so probably has the right >people. When/if we form a WG we can make a new list >or use this one if folks prefer that. > >Thanks, >S. > >[1] http://www.ietf.org/proceedings/85/certrans.html > >On 12/11/2013 04:55 PM, Ben Laurie wrote: >> Who's in? >> >> "Problem statement: many Internet protocols require a mapping between >> some kind of identifier and some kind of key, for example, HTTPS, >> SMTPS, IPSec, DNSSEC and OpenPGP. >> >> These protocols rely on either ad-hoc mappings, or on authorities >> which attest to the mappings. >> >> >> History shows that neither of these mechanisms is entirely >> satisfactory. Ad-hoc mappings are difficult to discover and maintain, >> and authorities make mistakes or are subverted. >> >> >> Cryptographically verifiable logs can help to ameliorate the problems >> by making it possible to discover and rectify errors before they can >> cause harm. >> >> >> These logs can also assist with other interesting problems, such as >> how to assure end users that software they are running is, indeed, the >> software they intend to run. >> >> >> Work items: Specify a standards-track mechanism to apply verifiable >> logs to HTTP/TLS (i.e. RFC 6962-bis). >> >> >> Discuss mechanisms and techniques that allow cryptographically >> verifiable logs to be deployed to improve the security of protocols >> and software distribution. Where such mechanisms appear sufficiently >> useful, the WG will re-charter to add relevant new work items." >> _______________________________________________ >> therightkey mailing list >> therightkey@ietf.org >> https://www.ietf.org/mailman/listinfo/therightkey >> >> >_______________________________________________ >therightkey mailing list >therightkey@ietf.org >https://www.ietf.org/mailman/listinfo/therightkey
- [therightkey] Draft charter for a Transparency Wo… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Rob Stradling
- Re: [therightkey] Draft charter for a Transparenc… Stephen Farrell
- Re: [therightkey] Draft charter for a Transparenc… Phillip Hallam-Baker
- Re: [therightkey] Draft charter for a Transparenc… Daniel Kahn Gillmor
- Re: [therightkey] Draft charter for a Transparenc… Livingood, Jason
- Re: [therightkey] Draft charter for a Transparenc… Paul Wouters
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Leif Johansson
- Re: [therightkey] Draft charter for a Transparenc… Leif Johansson
- Re: [therightkey] Draft charter for a Transparenc… Phillip Hallam-Baker
- Re: [therightkey] Draft charter for a Transparenc… Warren Kumari
- Re: [therightkey] Draft charter for a Transparenc… Lucy Lynch
- Re: [therightkey] Draft charter for a Transparenc… Lucy Lynch
- [therightkey] Fwd: [perpass] Draft charter for a … Phillip Hallam-Baker
- Re: [therightkey] Draft charter for a Transparenc… Paul Lambert
- Re: [therightkey] [perpass] Draft charter for a T… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Leif Johansson
- Re: [therightkey] Draft charter for a Transparenc… Stephen Farrell
- Re: [therightkey] Draft charter for a Transparenc… Paul Lambert
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Phillip Hallam-Baker
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Stephen Farrell
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Warren Kumari
- Re: [therightkey] Draft charter for a Transparenc… Ralph Holz
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie
- Re: [therightkey] Draft charter for a Transparenc… Tom Fitzhenry
- Re: [therightkey] Draft charter for a Transparenc… Stephen Farrell
- Re: [therightkey] Draft charter for a Transparenc… Stephen Farrell
- Re: [therightkey] Draft charter for a Transparenc… Ben Laurie