IETF Logo Mail Archive

Re: [Trans] IETF 90 scheduling

"Salz, Rich" <rsalz@akamai.com> Thu, 24 April 2014 14:56 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2EF1A02A6 for <trans@ietfa.amsl.com>; Thu, 24 Apr 2014 07:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level:
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272] 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 lCDtRx8x5TqM for <trans@ietfa.amsl.com>; Thu, 24 Apr 2014 07:56:49 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 596801A0298 for <trans@ietf.org>; Thu, 24 Apr 2014 07:56:49 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 16E9E165634; Thu, 24 Apr 2014 14:56:43 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (prod-mail-relay03.akamai.com [172.27.8.26]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id 0BB74165633; Thu, 24 Apr 2014 14:56:43 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub7.kendall.corp.akamai.com [172.27.105.23]) by prod-mail-relay03.akamai.com (Postfix) with ESMTP id CE0AB2FD65; Thu, 24 Apr 2014 14:56:42 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by usma1ex-cashub7.kendall.corp.akamai.com ([172.27.105.23]) with mapi; Thu, 24 Apr 2014 10:56:42 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Ben Laurie <benl@google.com>, Jean-Michel Combes <jeanmichel.combes@gmail.com>
Date: Thu, 24 Apr 2014 10:56:41 -0400
Thread-Topic: [Trans] IETF 90 scheduling
Thread-Index: Ac9fzMSg206CPWNBT02IveFFJ5GuwgAAFDFA
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C7120C35E5B1@USMBX1.msg.corp.akamai.com>
References: <53559D3B.1090504@gmail.com> <CAA7e52oXiCW4FfYfz-hT2=QOOm4xXGtxPmVwtC0rbcstQAP9qQ@mail.gmail.com> <CABrd9SRA+TnYXPo0eoNMyMxvVRT8AV39QB2BGb1S1yJ8imx6xg@mail.gmail.com>
In-Reply-To: <CABrd9SRA+TnYXPo0eoNMyMxvVRT8AV39QB2BGb1S1yJ8imx6xg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2A0EFB9C05D0164E98F19BB0AF3708C7120C35E5B1USMBX1msgcorp_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/SZc8Tsml-dHuSTXFp9Djmczbh48
Cc: Melinda Shore <melinda.shore@gmail.com>, "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] IETF 90 scheduling
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 14:56:51 -0000

Ø  There's already been a fairly extensive discussion on this, perhaps still not resolved. But my position continues to be that the TLS client needs to know various things about the log - public key, URL, MMD. I don't see the problem in those things being communicated in a data structure (e.g. in JSON).

.. and crypto mechanisms being used. At IMHO, this is not resolved.


Ø  Indeed we will shortly be defining such a structure for Chrome's valid logs. Whether this should form part of the RFC is up to the WG.

Yes, at least there.  I think the structure should be embedded in the log’s root, for simplicity of deployment evolution, and aiding after-the-fact auditing.

                /r$

--
Principal Security Engineer
Akamai Technologies, Cambridge, MA
IM: rsalz@jabber.me<mailto:rsalz@jabber.me>; Twitter: RichSalz

v2.23.0 | Report a Bug | By Email