From Francis.Dupont@fdupont.fr Fri Mar 1 04:12:02 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 129B421F88A9; Fri, 1 Mar 2013 04:12:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.799 X-Spam-Level: X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cb+VBs0EA8rI; Fri, 1 Mar 2013 04:12:01 -0800 (PST) Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id EFBE121F87C5; Fri, 1 Mar 2013 04:12:00 -0800 (PST) Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r21CBxDO000557; Fri, 1 Mar 2013 13:11:59 +0100 (CET) (envelope-from dupont@givry.fdupont.fr) Message-Id: <201303011211.r21CBxDO000557@givry.fdupont.fr> From: Francis Dupont To: Ben Laurie In-reply-to: Your message of Fri, 22 Feb 2013 11:17:51 GMT. Date: Fri, 01 Mar 2013 13:11:59 +0100 Sender: Francis.Dupont@fdupont.fr X-Mailman-Approved-At: Fri, 01 Mar 2013 04:13:29 -0800 Cc: "therightkey@ietf.org" , gen-art@ietf.org, draft-laurie-pki-sunlight.all@tools.ietf.org Subject: Re: [therightkey] review of draft-laurie-pki-sunlight-07.txt X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 12:12:02 -0000 In your previous mail you wrote: > > Minor issues: => BTW I received a side comment stating the document is too long and should be split into 3 parts (maths, mechanisms, application). Of course you may answer it is too late... > > - section 2 is not enough accurate, for instance: > > * the critical [k1:k2] notation is introduced after its first use, IMHO > > it is the primary one, i.e., [n] is a short hand for [0:n] > > Notation is rather tricky here, but I don't think that saying D[n] is > shorthand for D[0:n] adds clarity. This is because D[k:n] becomes > D[n-k] on recursion. Saying D[k:n] is the same as D[0:n-k] is just > confusing (and, indeed, wrong). => I don't say D[k:n] is the same as D[0:n-k], just that D[0:n-k] is the same than D[n-k]. But this is a matter of taste and I have no good proposal to make this section very clear... > > * the largest power of two must be strictly smaller, not just smaller. > > There is no difference between "strictly smaller" and "smaller" (in > contrast to "decreasing" and "strictly decreasing"). => it is a language problem: I leave it to native English speaker. > > - 1 page 4: it is a general mechanism but what are its constraints at > > the exception of the intended usage. For instance is the mechanism > > applicable to any end entity public key certificate? or larger?? > > I don't know what this comment refers to. => you have a mechanism which can be applied to more than public TLS server certificates. IMHO it should be fine to put a few words about the technical (vs usage) scope of the mechanism. Note the term "general" before mechanism and the very limited scope are both at the end of the first paragraph of section 1. > > - 1 page 5: misbehaviours -> misbehaviors > > (and 3.3 page 16, and others too) > > I am not American. => nor I am: I just applied an american English spell checker and reported what it considered as spelling errors. Note that RFCs are supposed to be written in american English (even it is not a strict rule at all), and what I did is a good practice when they are many authors from different countries (i.e., in the general case). > > - 2.1.1 page 7 and 2.1.2 page 8: the wording "the length (k2 - k1) list" > > is IMHO a bit uncommon even I can understand it. > > It's maths. => I am clearly under the Bourbaki's influence (i.e., maths should be written in the best possible wording :-). > > - 2.1.4 page 10: using a key of at least 2048 bits. -> > > using a public key of at least 2048 bits. (or a modulus as it is for RSA > ?) > > The public and private keys are the same length in RSA (and the length > is the length of the modulus). => as keys in RSA are not integers but tuples of integers they have no length by themselves. Now I agree the common meaning is what you say so I remove my comment (i.e., to be more accurate will be pedantic without a clear benefit). > > - 3 pages 13, 14, etc: what is the language used for ASN.1? It is not > > ASN.1 itself, nor C? > > The format of certificates is defined elsewhere. The name ASN.1Cert > (which is what I assume you refer to) is taken from RFC 5246. => oops, I missed the 1.2 where this was stated. > > - 3.1 page 13: parenthesis around 65535 are not necessary (i.e, they > > are insipid and stupid :-) > > I love you, too. => I thought you know the LISP programming language acronym... (I was a LISP programmer so I know all jokes about LISP :-) > In fact, they are required, see section 4.5 of RFC 5246. => I see. But in this case there are spurious 255 (not (255) as the default is one byte?). RFC 5246 uses (255) so I suggest to change all 255 at the end of enums into (255) *if* you have the opportunity to do this. > > BTW if the document creates new OID perhaps they should be put > > in an annex? > > I am not aware of a requirement to do so. => nor I am (this is why I put a question mark) > > PS: I noted there are still some LC comments in the ML. > > I am not aware of any I have missed. => it was just a reminder to the LC comment statement at the beginning of the standard gen-art template, and an indication to other gen-art ML readers. Thanks Francis.Dupont@fdupont.fr From stephen.farrell@cs.tcd.ie Fri Mar 1 04:16:20 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7898521F8AAC; Fri, 1 Mar 2013 04:16:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.499 X-Spam-Level: X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mrzRx+tms4gE; Fri, 1 Mar 2013 04:16:20 -0800 (PST) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D8C3421F8899; Fri, 1 Mar 2013 04:16:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4531FBE58; Fri, 1 Mar 2013 12:15:58 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9Krolmr36dJ; Fri, 1 Mar 2013 12:15:58 +0000 (GMT) Received: from [IPv6:2001:770:10:203:8eb:c49b:fda5:dc39] (unknown [IPv6:2001:770:10:203:8eb:c49b:fda5:dc39]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1B50CBE53; Fri, 1 Mar 2013 12:15:58 +0000 (GMT) Message-ID: <51309BFE.9090401@cs.tcd.ie> Date: Fri, 01 Mar 2013 12:15:58 +0000 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Francis Dupont References: <201303011211.r21CBxDO000557@givry.fdupont.fr> In-Reply-To: <201303011211.r21CBxDO000557@givry.fdupont.fr> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "therightkey@ietf.org" , Ben Laurie , gen-art@ietf.org, draft-laurie-pki-sunlight.all@tools.ietf.org Subject: Re: [therightkey] review of draft-laurie-pki-sunlight-07.txt X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 12:16:20 -0000 On 03/01/2013 12:11 PM, Francis Dupont wrote: >> > > - 1 page 5: misbehaviours -> misbehaviors >> > > (and 3.3 page 16, and others too) >> > >> > I am not American. > => nor I am: I just applied an american English spell checker and > reported what it considered as spelling errors. Note that RFCs are > supposed to be written in american English (even it is not a strict > rule at all), and what I did is a good practice when they are many > authors from different countries (i.e., in the general case). > I believe the RFC editor allows either English or American spellings so long as the document is consistent. S. From benl@google.com Fri Mar 1 04:22:56 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C772F21F8ACE for ; Fri, 1 Mar 2013 04:22:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.978 X-Spam-Level: X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6h-0nSslBQd7 for ; Fri, 1 Mar 2013 04:22:56 -0800 (PST) Received: from mail-ia0-x22f.google.com (mail-ia0-x22f.google.com [IPv6:2607:f8b0:4001:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 135D821F8976 for ; Fri, 1 Mar 2013 04:22:55 -0800 (PST) Received: by mail-ia0-f175.google.com with SMTP id k38so391589iah.6 for ; Fri, 01 Mar 2013 04:22:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gTriIGOTCpUX3DcFFxUBxpT4eCv+aG4PJtWAWzomzYs=; b=Mu47I8h2hqc7msVRFj9vkE0qeaDorLJCWxheh9Pz0Xx902Yi+Likb8I8ablB0XlURo k4yfXMWEVCf6sYGJZWEZSQUCR6kkIOdMBmn4RyrJUOCdmYcxVH5qrF1C8zmYGsMX46C2 FQqXC2Htoqk1sGnw8e+/9qHNyJsBHsa0yrxCg2vXO3MjCaDZTi3PkgHp6pMXlOhqZrX/ TeUG/ANXx+aZ4wVQUchRs4LCtgQFSxUaoXXDTJxYLqEA/sFvSBNrHi6XrsoIpzk1pIl4 lIWCcxtJ0nIHPCVALzMV3EYqL0hTXu3RUz6GuYA1Nyu+A2b7N3rpi2Mn+uSgWWDAFcZQ mzng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=gTriIGOTCpUX3DcFFxUBxpT4eCv+aG4PJtWAWzomzYs=; b=jukfkCntjvRoNgM1lWhQHYltniQmdg4jPxOm1RamVWKKao6OJ9ELOWvuhyZSLBRJuq DxD850VulDC2zHOjWq9XdgGbwno6nUaKBmInJlQuqlaTSPMOEa9AoRhr9NAm8SFzbLCY 6+f2J7/rqiTziFrMCOLJuR/WsFKXyuiDJXzy3a5xUz8dMw3ireOKdL6Fe/lz0v0D+HEe zOO30HBlCDxbNw4ddwm4wx9+56BwKcQzkAzSiN/2TYIVzgoma1prH/IGa1aJCvsrpxf7 vbMsZaYqHYXD7AT1WuPAgJgxxhE4JCToki38OLKATCMrZvU6u5rTILHVTPED9fPzaoBh kbZA== MIME-Version: 1.0 X-Received: by 10.50.41.225 with SMTP id i1mr6275655igl.100.1362140575570; Fri, 01 Mar 2013 04:22:55 -0800 (PST) Received: by 10.64.65.228 with HTTP; Fri, 1 Mar 2013 04:22:55 -0800 (PST) In-Reply-To: <201303011211.r21CBxDO000557@givry.fdupont.fr> References: <201303011211.r21CBxDO000557@givry.fdupont.fr> Date: Fri, 1 Mar 2013 12:22:55 +0000 Message-ID: From: Ben Laurie To: Francis Dupont Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnVLF7Xf7c7gfQYGsmAUaN5QqZ6Z+v39p6rWQQyr6w9daVLMp2Lm8IIsWKsr+yvFO7evIMhdqqYrfWHYwdWcz1vBoulmyOXS8Wxj3YAS03J+obQYv5WX51CxEP0JnmoJoPyPV1a465i2t0eE+OTZo6oukWGAbV8tRvGl7/o6T2hKVNDP0DtCKKVWvaIpn+vI9ytI6S8 Cc: "therightkey@ietf.org" , gen-art@ietf.org, draft-laurie-pki-sunlight.all@tools.ietf.org Subject: Re: [therightkey] review of draft-laurie-pki-sunlight-07.txt X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 12:22:56 -0000 On 1 March 2013 12:11, Francis Dupont wrote: > In your previous mail you wrote: > >> > Minor issues: > > => BTW I received a side comment stating the document is too long > and should be split into 3 parts (maths, mechanisms, application). > Of course you may answer it is too late... I do. Way too late. :-) Also, I'd observe that increasing the number of documents will not decrease the amount of reading. >> > - section 2 is not enough accurate, for instance: >> > * the critical [k1:k2] notation is introduced after its first use, IMHO >> > it is the primary one, i.e., [n] is a short hand for [0:n] >> >> Notation is rather tricky here, but I don't think that saying D[n] is >> shorthand for D[0:n] adds clarity. This is because D[k:n] becomes >> D[n-k] on recursion. Saying D[k:n] is the same as D[0:n-k] is just >> confusing (and, indeed, wrong). > > => I don't say D[k:n] is the same as D[0:n-k], just that D[0:n-k] > is the same than D[n-k]. But this is a matter of taste and I have > no good proposal to make this section very clear... > >> > * the largest power of two must be strictly smaller, not just smaller. >> >> There is no difference between "strictly smaller" and "smaller" (in >> contrast to "decreasing" and "strictly decreasing"). > > => it is a language problem: I leave it to native English speaker. This was explained to me offlist. Certainly there is no problem in English, but I understand other languages don't work as well. So, I added mathematical notation for clarity. > >> > - 1 page 4: it is a general mechanism but what are its constraints at >> > the exception of the intended usage. For instance is the mechanism >> > applicable to any end entity public key certificate? or larger?? >> >> I don't know what this comment refers to. > > => you have a mechanism which can be applied to more than public TLS > server certificates. IMHO it should be fine to put a few words about > the technical (vs usage) scope of the mechanism. Note the term "general" > before mechanism and the very limited scope are both at the end of > the first paragraph of section 1. > >> > - 1 page 5: misbehaviours -> misbehaviors >> > (and 3.3 page 16, and others too) >> >> I am not American. > > => nor I am: I just applied an american English spell checker and > reported what it considered as spelling errors. Note that RFCs are > supposed to be written in american English (even it is not a strict > rule at all), and what I did is a good practice when they are many > authors from different countries (i.e., in the general case). The style guide (http://www.rfc-editor.org/rfc-style-guide/rfc-style) says English. >> > - 2.1.1 page 7 and 2.1.2 page 8: the wording "the length (k2 - k1) list" >> > is IMHO a bit uncommon even I can understand it. >> >> It's maths. > > => I am clearly under the Bourbaki's influence (i.e., maths should be > written in the best possible wording :-). I changed it anyway :-) >> > - 2.1.4 page 10: using a key of at least 2048 bits. -> >> > using a public key of at least 2048 bits. (or a modulus as it is for RSA >> ?) >> >> The public and private keys are the same length in RSA (and the length >> is the length of the modulus). > > => as keys in RSA are not integers but tuples of integers they have > no length by themselves. Now I agree the common meaning is what > you say so I remove my comment (i.e., to be more accurate will be > pedantic without a clear benefit). > >> > - 3 pages 13, 14, etc: what is the language used for ASN.1? It is not >> > ASN.1 itself, nor C? >> >> The format of certificates is defined elsewhere. The name ASN.1Cert >> (which is what I assume you refer to) is taken from RFC 5246. > > => oops, I missed the 1.2 where this was stated. > >> > - 3.1 page 13: parenthesis around 65535 are not necessary (i.e, they >> > are insipid and stupid :-) >> >> I love you, too. > > => I thought you know the LISP programming language acronym... > (I was a LISP programmer so I know all jokes about LISP :-) Heh. I always thought it was irritating, not insipid. >> In fact, they are required, see section 4.5 of RFC 5246. > > => I see. But in this case there are spurious 255 (not (255) > as the default is one byte?). RFC 5246 uses (255) so > I suggest to change all 255 at the end of enums into (255) > *if* you have the opportunity to do this. You are right, I will change them. >> > BTW if the document creates new OID perhaps they should be put >> > in an annex? >> >> I am not aware of a requirement to do so. > > => nor I am (this is why I put a question mark) > >> > PS: I noted there are still some LC comments in the ML. >> >> I am not aware of any I have missed. > > => it was just a reminder to the LC comment statement > at the beginning of the standard gen-art template, and > an indication to other gen-art ML readers. I see. Thanks! From hannes.tschofenig@gmx.net Tue Mar 5 06:21:27 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556D221F8742 for ; Tue, 5 Mar 2013 06:21:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.099 X-Spam-Level: X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYjpkRYWxhEr for ; Tue, 5 Mar 2013 06:21:26 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 7169A21F86E4 for ; Tue, 5 Mar 2013 06:21:26 -0800 (PST) Received: from mailout-de.gmx.net ([10.1.76.4]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MM1JK-1U9YIT1Kea-007jmR for ; Tue, 05 Mar 2013 15:21:25 +0100 Received: (qmail invoked by alias); 05 Mar 2013 14:21:24 -0000 Received: from dslb-188-107-233-245.pools.arcor-ip.net (EHLO [192.168.178.169]) [188.107.233.245] by mail.gmx.net (mp004) with SMTP; 05 Mar 2013 15:21:24 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+TrW8ykymTbYOjzC/qH6SyAWvjoShCtgPT2STw/g qvCx9mOXb6Hvt8 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) From: Hannes Tschofenig Date: Tue, 5 Mar 2013 16:21:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <12A7F462-1509-44D2-950E-167D77165E12@gmx.net> References: To: therightkey@ietf.org X-Mailer: Apple Mail (2.1085) X-Y-GMX-Trusted: 0 Cc: Hannes Tschofenig Subject: [therightkey] Fwd: Alternative PKI Models Side Meeting X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Mar 2013 14:21:27 -0000 FYI Begin forwarded message: > From: Hannes Tschofenig > Date: March 5, 2013 4:19:51 PM GMT+02:00 > To: 86attendees@ietf.org > Cc: Hannes Tschofenig > Subject: Alternative PKI Models Side Meeting >=20 > Hi all, >=20 > When our security ADs scheduled the BOF on Certificate Transparency = (CT) [0] in Atlanta (IETF-85), some expressed interest in continuing the = discussions regarding improvements to the Web PKI. In the IAB, we have = been brainstorming about holding a workshop to progress the topic, but = with the announcement of the NIST workshop on Improving Trust in the = Online Marketplace [1] we decided to postpone our workshop. >=20 > The upcoming IETF-86 meeting is, however, a good opportunity to = discuss whether there is a need for additional investigations. In = particular, we have been wondering whether the IETF community has the = same level of understanding regarding the requirements, goals, and the = design assumptions. The emerging evolutionary alterations to the Web PKI = model -- i.e., DANE, CT, TACK, etc. -- superficially fit the model, but = they alter it in subtle and interesting ways. >=20 > If you are interested in a discussion you are welcome to join our side = meeting on Thursday evening (at 8pm*) in room Boca 4 (the IAB Office). >=20 > Ciao > Hannes & JeffH >=20 > References:=20 > [0] https://www.ietf.org/mailman/listinfo/therightkey > [1] http://www.nist.gov/itl/csd/ct/ca_workshop.cfm >=20 > PS: We picked 8pm since some of you may want to stop by at the = Bits-N-Bites event. From benl@google.com Fri Mar 15 07:52:45 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4351221F8831 for ; Fri, 15 Mar 2013 07:52:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.977 X-Spam-Level: X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYD9CupyqneI for ; Fri, 15 Mar 2013 07:52:44 -0700 (PDT) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 080F421F8821 for ; Fri, 15 Mar 2013 07:52:40 -0700 (PDT) Received: by mail-ie0-f181.google.com with SMTP id 17so4490114iea.12 for ; Fri, 15 Mar 2013 07:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=mx4gKbKAiCPs0K4WsfiBJpfbTgmp/Js0x+c9SNvUn6g=; b=hZaSjJ5rutjgs5uyMbB7KSowoMsh6I3iDdlNc2N2BctfOU803wZCI3DR12ycY7BHEQ pi8yB18IjfdDigVCpup46zaj5stleSwWIc6yvEth4TD2hkY+/2SM30DPIyl1aI3z1IWq GBWpXmwY0PMr2kYs9V5QFBdQjfvcgRRTL6llyT4VBTJMic/q/U4iu2aH5ceaKvorjkVq qJqhtTaKja8eAQXmF3xDOWQX4HfNLc7G/5awvSUjFiyx+bItRepPMg7j27yqx3f8bSjw jjelkMKVguOW99+Y50H77SucxDIXlEtVWnz8FmWpPRGv++xWPsGC70bolHYNmjREZKd2 A+3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=mx4gKbKAiCPs0K4WsfiBJpfbTgmp/Js0x+c9SNvUn6g=; b=GtHy+5xzkaGueZ/B/eoGlduNdpd8ROIzXoFq+P7d2visZNv7KHCwzoLd2P+LN+bRWJ AqaHz9hCqY++iA/H0VGPOkIA/X/rjL+TeeUdV7J/yX4RH71hz0NUr817RCSRrZoAqqMB 59o2LHLdo6HSqpGw4zhZnx0ck3Zh38KITsljVGu3jziP+li/pVku6drrQnJ5yCmrCxcC whtKK+0P7XgXqrtjzxxspgukE4Wqch4Rgv7OzVjmRLUD3isiSTClYjB0BGxPObyTYwN3 nVKPxgI48+93hgTvzAuE4v5fXkCAM19zktf7tj2qj91GsMyCThRTYVVMDWtQ9UNj5Twt 5Ikg== MIME-Version: 1.0 X-Received: by 10.50.208.101 with SMTP id md5mr1450313igc.60.1363359160624; Fri, 15 Mar 2013 07:52:40 -0700 (PDT) Received: by 10.64.20.131 with HTTP; Fri, 15 Mar 2013 07:52:40 -0700 (PDT) Date: Fri, 15 Mar 2013 14:52:40 +0000 Message-ID: From: Ben Laurie To: "therightkey@ietf.org" Content-Type: multipart/alternative; boundary=14dae934063b78a00c04d7f7caf1 X-Gm-Message-State: ALoCoQmbh297bzTf6huPAHxBlgrC7eF2UP7jyXll4s0OVOhDdB2t/beQlfnuMPrngVQiU1RrFCSs3hKnHN2ke7g1p8jsp0SynOsiYmaLxCsIcYeLVB9WI4HY1jIIsKmEwhTja+ZxaThGSTxMHLK+ArsZ/eX/y+BEL4WIAKtgcRcv7BG8pvBg4VXBbabro9jGcEGu0NdXAY/h Subject: [therightkey] Acknowledgements in CT I-D X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:52:45 -0000 --14dae934063b78a00c04d7f7caf1 Content-Type: text/plain; charset=ISO-8859-1 I should've been tracking contributions from the start, but I didn't, I'm sorry. I submitted the new version yesterday with a placeholder section, but I am working on fleshing it out. Trawling back through over a year of discussions means I am sure I will have missed people out. So, if you think you should be acknowledged in the I-D, do please let me know. --14dae934063b78a00c04d7f7caf1 Content-Type: text/html; charset=ISO-8859-1
I should've been tracking contributions from the start, but I didn't, I'm sorry. I submitted the new version yesterday with a placeholder section, but I am working on fleshing it out.

Trawling back through over a year of discussions means I am sure I will have missed people out. So, if you think you should be acknowledged in the I-D, do please let me know.

--14dae934063b78a00c04d7f7caf1-- From stephen.farrell@cs.tcd.ie Fri Mar 15 08:01:24 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C6A21F86AD for ; Fri, 15 Mar 2013 08:01:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.506 X-Spam-Level: X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQfq-OqMdEDe for ; Fri, 15 Mar 2013 08:01:23 -0700 (PDT) Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C102A21F8691 for ; Fri, 15 Mar 2013 08:01:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 51A90BE5A; Fri, 15 Mar 2013 15:00:59 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0x1B7FmeWOYi; Fri, 15 Mar 2013 15:00:54 +0000 (GMT) Received: from [130.129.96.60] (dhcp-603c.meeting.ietf.org [130.129.96.60]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EDA4EBE63; Fri, 15 Mar 2013 15:00:53 +0000 (GMT) Message-ID: <514337A4.30905@cs.tcd.ie> Date: Fri, 15 Mar 2013 15:00:52 +0000 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ben Laurie References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "therightkey@ietf.org" Subject: Re: [therightkey] Acknowledgements in CT I-D X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 15:01:24 -0000 Thanks Ben. For those who like IETF process, I've put -08 on the March 28th IESG telechat agenda for approval. I've noted that the acks section might change in the next week or so (and that nothing else ought change:-) S On 03/15/2013 02:52 PM, Ben Laurie wrote: > I should've been tracking contributions from the start, but I didn't, I'm > sorry. I submitted the new version yesterday with a placeholder section, > but I am working on fleshing it out. > > Trawling back through over a year of discussions means I am sure I will > have missed people out. So, if you think you should be acknowledged in the > I-D, do please let me know. > > > > _______________________________________________ > therightkey mailing list > therightkey@ietf.org > https://www.ietf.org/mailman/listinfo/therightkey > From leifj@mnt.se Sun Mar 17 11:27:52 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC03821F8AD8 for ; Sun, 17 Mar 2013 11:27:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.733 X-Spam-Level: X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H41r0fcvC4F7 for ; Sun, 17 Mar 2013 11:27:52 -0700 (PDT) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DAA0421F8AD5 for ; Sun, 17 Mar 2013 11:27:51 -0700 (PDT) Received: by mail-la0-f44.google.com with SMTP id eb20so5350379lab.3 for ; Sun, 17 Mar 2013 11:27:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:x-gm-message-state; bh=Hgr3xyaAUfBCzREcj7CufNHX4AgejzhziyTrKZ7/Sk4=; b=odSumlgu72PqBLfUB8Es34RLImO4gqjq7c90X1jlWjDy3qkqCU3c3mdRwY/oKQ6pEX FA7lFuLDGRWWkABwrpeAj6l1ZvUaowCRh3eoC9avgN5SQMzO1nmyfIlqUGXQ9llB4AcD jDNdyOBLFdfIflnKuCbm1PAP0cP61KwHm7wu5nDJm7/kD8Hc/zoJaFImKndRQUb+4ifI QA4Seek87RT2daQKuHc2pLMW6fXSLHtQi9t20QU5YDgTBDzeVjwJbDloNjNWFpnX35L6 VhD493YCZJ+4Yv2L9B4FxZpQsVTmE+lxHVnfdNyrBzduGlip8dXVyoEvznkZtD2ONXph VAKg== X-Received: by 10.112.79.34 with SMTP id g2mr962016lbx.41.1363544870260; Sun, 17 Mar 2013 11:27:50 -0700 (PDT) Received: from [10.0.0.244] (tb62-102-145-131.cust.teknikbyran.com. [62.102.145.131]) by mx.google.com with ESMTPS id c10sm4505973lbu.11.2013.03.17.11.27.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Mar 2013 11:27:49 -0700 (PDT) Message-ID: <51460B23.2050200@mnt.se> Date: Sun, 17 Mar 2013 19:27:47 +0100 From: Leif Johansson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: therightkey@ietf.org Content-Type: multipart/alternative; boundary="------------080106070706060800050901" X-Gm-Message-State: ALoCoQllt8hU0YAryWw74TznuylbQIdLvZ6Fd22qtxMRJB3m7dDsQ+yGGc+Ccizkz9PAFxtcclUp Subject: [therightkey] CT implementation(s) X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 18:27:52 -0000 This is a multi-part message in MIME format. --------------080106070706060800050901 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On the plane back from Orlando I started playing with the CT implementation from google code: https://code.google.com/p/certificate-transparency/ Is it supposed to track the sunlight draft, because afikt the ct-server doesn't implement the REST interface specified in -08. Am I missing something? Cheers Leif --------------080106070706060800050901 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On the plane back from Orlando I started playing with the CT implementation
from google code: https://code.google.com/p/certificate-transparency/

Is it supposed to track the sunlight draft, because afikt the ct-server doesn't
implement the REST interface specified in -08. Am I missing something?

        Cheers Leif
--------------080106070706060800050901-- From benl@google.com Sun Mar 17 12:01:51 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F4B21F8B8A for ; Sun, 17 Mar 2013 12:01:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.977 X-Spam-Level: X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4XvzmopDX9R for ; Sun, 17 Mar 2013 12:01:50 -0700 (PDT) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 85B2E21F8B48 for ; Sun, 17 Mar 2013 12:01:50 -0700 (PDT) Received: by mail-ie0-f181.google.com with SMTP id 17so6237949iea.12 for ; Sun, 17 Mar 2013 12:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=4fhlVTKWKMahWnfGvI3kqeF7YWZ73EDXzloKQZp5sug=; b=PhjMd+UfB5cjAQIbvEz6e52rANbDJaRrrGg77S2XeXVCdAXfu9/ZGztResnkRLvFHr qYCRsA3JoZmGPLHYjkbFXfTHiXrQ4WQNt0Q2n6/PKh+HWoajZqQQJLm1SQLkWqwgaTqa tGVnhLTWqWv0nAZL/UsgRo3nNp/MzG9y/PZgB8YK6L+p1JIPMEUGst6eb/ZsSYJrB1jJ 66WCU5ecmnJlg1/IAzY98ZKz3ZWGr5+4KODVznMzb5CrsrPkA4F5993vu1cyjLCEibwO sfMUcSIQuHfOF+LgJmzpKnMJfYpG5QRdqhguwakTQ++ESeHuoG7TsKrwkAdlII5YWf/P fOrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=4fhlVTKWKMahWnfGvI3kqeF7YWZ73EDXzloKQZp5sug=; b=IIzi7DfMtW4tq685+LKkFWtKaAuLyzVkH/t0m6kBLwICn8MKf9Cn+8Ah3BTsn1QElL Pw1DP/YJykGUS2kJjsCrNp1Bl5gpSV9/pJZPXEHgTRA8em1P6bUiaX+FyOeyXM67YReU o6Kyd3geJdbUioIA8C0w784r9CCpxe94O3Ev8cYdJ6syfBrWHpiESfYSAk9CD08K9D/9 vF9rTqdtpHaBkfCCznBjyRqjD48S041hOCXJcHqNtfiPP2QEI/RIRpO7okuKstg9NNfe 6YCGbe7BowhZ9LGhGcqF1iIueGYRlymRtI/AKUs/p39+xnHzFh+p5G73BeRLS2GNQXgu RuRA== MIME-Version: 1.0 X-Received: by 10.50.208.68 with SMTP id mc4mr5008596igc.35.1363546909983; Sun, 17 Mar 2013 12:01:49 -0700 (PDT) Received: by 10.64.20.131 with HTTP; Sun, 17 Mar 2013 12:01:49 -0700 (PDT) In-Reply-To: <51460B23.2050200@mnt.se> References: <51460B23.2050200@mnt.se> Date: Sun, 17 Mar 2013 19:01:49 +0000 Message-ID: From: Ben Laurie To: Leif Johansson Content-Type: multipart/alternative; boundary=14dae93408e734709404d823814e X-Gm-Message-State: ALoCoQnPzj7fpPCWGVt/5CQwm190uOT03nQND6USudR1Sthud+KwQpRWQCddyE7ca1FFpVWlxIVCHtiOAWcL1gjPPoDx+iXDJl7cm2zetN/DZjuR9sQn77+/a7QXaq4zXwdO77WjoMuBKaEy3YRIx/MhNZlPF4X6m3bWKzBG2LCRvOJsl0Gl6OMlJ/jtoSpn4j4MokidQCun Cc: "therightkey@ietf.org" Subject: Re: [therightkey] CT implementation(s) X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 19:01:51 -0000 --14dae93408e734709404d823814e Content-Type: text/plain; charset=ISO-8859-1 On 17 March 2013 18:27, Leif Johansson wrote: > > On the plane back from Orlando I started playing with the CT implementation > from google code: https://code.google.com/p/certificate-transparency/ > > Is it supposed to track the sunlight draft, because afikt the ct-server > doesn't > implement the REST interface specified in -08. Am I missing something? > I'm working on it right now :-) > > Cheers Leif > > _______________________________________________ > therightkey mailing list > therightkey@ietf.org > https://www.ietf.org/mailman/listinfo/therightkey > > --14dae93408e734709404d823814e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 17 March 2013 18:27, Leif Johansson <leifj@mnt.se> wro= te:
=20 =20 =20

On the plane back from Orlando I started playing with the CT implementation
from google code: =20 https://code.google.com/p/certificate-transparency/

Is it supposed to track the sunlight draft, because afikt the ct-server doesn't
implement the REST interface specified in -08. Am I missing something?

I'm work= ing on it right now :-)
=A0

=A0=A0=A0 =A0=A0=A0 Cheers Leif

_______________________________________________
therightkey mailing list
therightkey@ietf.org
https://www.ietf.org/mailman/listinfo/therightkey


--14dae93408e734709404d823814e-- From leifj@mnt.se Sun Mar 17 12:23:28 2013 Return-Path: X-Original-To: therightkey@ietfa.amsl.com Delivered-To: therightkey@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76CAD21F8B35 for ; Sun, 17 Mar 2013 12:23:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.733 X-Spam-Level: X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2xJRTIFmF7Z for ; Sun, 17 Mar 2013 12:23:28 -0700 (PDT) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A2DF221F8AE3 for ; Sun, 17 Mar 2013 12:23:27 -0700 (PDT) Received: by mail-la0-f52.google.com with SMTP id fs12so5283148lab.39 for ; Sun, 17 Mar 2013 12:23:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type:x-gm-message-state; bh=UjCT/zcab3EZ0MPDTrbh3ArFgtQYB9ymiQ1+LfCbucQ=; b=kOdqpV1Z+XjlY+dw8yxEVQ0CnnJGb2LH+0THOsp9uvScto2UOLkkKGoEZ0i3G2QWp6 ICDO6jfY1Xv56QsB3QrOZ+1GqMTfs+BOiFmTGR1fq3Iwt7w0+UqX+jyUQVi5TB3q/z2T x0XXlmrRVlYZBTXrgI3bfTX93RLAMqs9X/XlVczyfnPIi9mS3gtkDbks0tyAt9GTsCyc GfxiDFV2qqsZuvUUFXsblRjBLApclC3fbHfWY1kCOFkMZsVndwZE7P8wHiAEKi74Sd2L 1LHFf5cz4TbQ5mid6WIReYqsRVyIWKufQ/2IQcncrUUvn0bvXMT0MQYtLE/AVHpw1sfa JHgg== X-Received: by 10.112.9.231 with SMTP id d7mr5411942lbb.8.1363548206564; Sun, 17 Mar 2013 12:23:26 -0700 (PDT) Received: from [10.0.0.244] (tb62-102-145-131.cust.teknikbyran.com. [62.102.145.131]) by mx.google.com with ESMTPS id e9sm4567207lbz.1.2013.03.17.12.23.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Mar 2013 12:23:25 -0700 (PDT) Message-ID: <5146182B.5010209@mnt.se> Date: Sun, 17 Mar 2013 20:23:23 +0100 From: Leif Johansson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Ben Laurie References: <51460B23.2050200@mnt.se> In-Reply-To: Content-Type: multipart/alternative; boundary="------------030303020007030204000208" X-Gm-Message-State: ALoCoQkr5JtXbI7g1o7J3GIwiBkt+CFuiGG6Sz53A4ZxwWvEKsIbUT0eFb5vSQund5CDdauKs2on Cc: "therightkey@ietf.org" Subject: Re: [therightkey] CT implementation(s) X-BeenThere: therightkey@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 19:23:28 -0000 This is a multi-part message in MIME format. --------------030303020007030204000208 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 03/17/2013 08:01 PM, Ben Laurie wrote: > > > > On 17 March 2013 18:27, Leif Johansson > wrote: > > > On the plane back from Orlando I started playing with the CT > implementation > from google code: https://code.google.com/p/certificate-transparency/ > > Is it supposed to track the sunlight draft, because afikt the > ct-server doesn't > implement the REST interface specified in -08. Am I missing something? > > > I'm working on it right now :-) > > Excellent ! Fingers poised over hg pull && hg update :-) --------------030303020007030204000208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 03/17/2013 08:01 PM, Ben Laurie wrote:



On 17 March 2013 18:27, Leif Johansson <leifj@mnt.se> wrote:

On the plane back from Orlando I started playing with the CT implementation
from google code: https://code.google.com/p/certificate-transparency/

Is it supposed to track the sunlight draft, because afikt the ct-server doesn't
implement the REST interface specified in -08. Am I missing something?

I'm working on it right now :-)
 

Excellent ! Fingers poised over hg pull && hg update :-)

--------------030303020007030204000208--