Re: [Trans] Parsing existing logs entries.

Rob Stradling <rob.stradling@comodo.com> Fri, 30 May 2014 10:17 UTC

Return-Path: <rob.stradling@comodo.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 E055F1A0893 for <trans@ietfa.amsl.com>; Fri, 30 May 2014 03:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.29
X-Spam-Level:
X-Spam-Status: No, score=-1.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, 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 qMhhi-f-8bpY for <trans@ietfa.amsl.com>; Fri, 30 May 2014 03:17:28 -0700 (PDT)
Received: from ian.brad.office.comodo.net (eth5.brad-fw.brad.office.ccanet.co.uk [178.255.87.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B483D1A03E3 for <trans@ietf.org>; Fri, 30 May 2014 03:17:26 -0700 (PDT)
Received: (qmail 11261 invoked by uid 1000); 30 May 2014 10:17:20 -0000
Received: from nigel.brad.office.comodo.net (HELO [192.168.0.58]) (192.168.0.58) (smtp-auth username rob, mechanism plain) by ian.brad.office.comodo.net (qpsmtpd/0.40) with (AES128-SHA encrypted) ESMTPSA; Fri, 30 May 2014 11:17:20 +0100
Message-ID: <53885AB0.6060107@comodo.com>
Date: Fri, 30 May 2014 11:17:20 +0100
From: Rob Stradling <rob.stradling@comodo.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Kurt Roeckx <kurt@roeckx.be>
References: <20140529175912.GB15165@roeckx.be> <5387961D.1010503@comodo.com> <20140529203404.GA20394@roeckx.be>
In-Reply-To: <20140529203404.GA20394@roeckx.be>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/xpqfeQM2K36bHQOqyPxXugldDWY
Cc: trans@ietf.org
Subject: Re: [Trans] Parsing existing logs entries.
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, 30 May 2014 10:17:30 -0000

On 29/05/14 21:34, Kurt Roeckx wrote:
> On Thu, May 29, 2014 at 09:18:37PM +0100, Rob Stradling wrote:
>> Kurt, RFC6962 says...
>>
>> "1.2.  Data Structures
>>
>>     Data structures are defined according to the conventions laid out in
>>     Section 4 of [RFC5246]."
>>
>> So you shouldn't have to guess.  Just read RFC5246 Section 4.
>
> Thanks, I seems to have overlooked that section.
>
> Anyway, I really don't understand why this is such a mixture of
> josn and base64 encoded things.  Why isn't this all just json with
> just the certificate in base64?

Personal preference of the authors of RFC6962?

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online