Re: [Trans] IETF 90 scheduling
"Salz, Rich" <rsalz@akamai.com> Fri, 25 April 2014 13:25 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 15F5F1A04AE for <trans@ietfa.amsl.com>; Fri, 25 Apr 2014 06:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.272
X-Spam-Level:
X-Spam-Status: No, score=-0.272 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 TQS_N707YXou for <trans@ietfa.amsl.com>; Fri, 25 Apr 2014 06:25:23 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id 78CE91A01D4 for <trans@ietf.org>; Fri, 25 Apr 2014 06:25:23 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 02F34473DE; Fri, 25 Apr 2014 13:25:17 +0000 (GMT)
Received: from prod-mail-relay02.akamai.com (prod-mail-relay02.akamai.com [172.17.50.21]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id EA22647391; Fri, 25 Apr 2014 13:25:16 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub6.kendall.corp.akamai.com [172.27.105.22]) by prod-mail-relay02.akamai.com (Postfix) with ESMTP id E0A92FE054; Fri, 25 Apr 2014 13:25:16 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by USMA1EX-CASHUB6.kendall.corp.akamai.com ([172.27.105.22]) with mapi; Fri, 25 Apr 2014 09:25:16 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Ben Laurie <benl@google.com>
Date: Fri, 25 Apr 2014 09:25:10 -0400
Thread-Topic: [Trans] IETF 90 scheduling
Thread-Index: Ac9ghqj5EeYrYdJpTGao3KiZ2zdfhgAAsV2g
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C7120C35E90C@USMBX1.msg.corp.akamai.com>
References: <53559D3B.1090504@gmail.com> <CAA7e52oXiCW4FfYfz-hT2=QOOm4xXGtxPmVwtC0rbcstQAP9qQ@mail.gmail.com> <CABrd9SRA+TnYXPo0eoNMyMxvVRT8AV39QB2BGb1S1yJ8imx6xg@mail.gmail.com> <2A0EFB9C05D0164E98F19BB0AF3708C7120C35E5B1@USMBX1.msg.corp.akamai.com> <53592714.4080502@comodo.com> <2A0EFB9C05D0164E98F19BB0AF3708C7120C35E5B4@USMBX1.msg.corp.akamai.com> <CABrd9SQiREMmtTswKBOD=KodNeP=0ZVEZxWkkVfHD-RPHH+Eww@mail.gmail.com>
In-Reply-To: <CABrd9SQiREMmtTswKBOD=KodNeP=0ZVEZxWkkVfHD-RPHH+Eww@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_2A0EFB9C05D0164E98F19BB0AF3708C7120C35E90CUSMBX1msgcorp_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/InplLuZg5WhJEfgb1fuRUNNjk9A
Cc: "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: Fri, 25 Apr 2014 13:25:25 -0000
Ø Hmm. I don't really object to that. Huzzah! Time to recall heartbleed as an attempt to wear you down ☺ (Too soon?) Ø We need something that allows clients to gossip so they can verify that the parameters they see in the root are as expected. Something in URL syntax to identify the log, even if it’s not the actual URL? Like an XMLNS string? -- Principal Security Engineer Akamai Technologies, Cambridge, MA IM: rsalz@jabber.me<mailto:rsalz@jabber.me>; Twitter: RichSalz
- [Trans] IETF 90 scheduling Melinda Shore
- Re: [Trans] IETF 90 scheduling Jean-Michel Combes
- Re: [Trans] IETF 90 scheduling Ben Laurie
- Re: [Trans] IETF 90 scheduling Salz, Rich
- Re: [Trans] IETF 90 scheduling Rob Stradling
- Re: [Trans] IETF 90 scheduling Salz, Rich
- Re: [Trans] IETF 90 scheduling Ben Laurie
- Re: [Trans] IETF 90 scheduling Salz, Rich
- Re: [Trans] IETF 90 scheduling Ben Laurie
- Re: [Trans] IETF 90 scheduling Salz, Rich
- Re: [Trans] IETF 90 scheduling Ben Laurie