Re: [Trans] Parsing existing logs entries.
Kurt Roeckx <kurt@roeckx.be> Thu, 29 May 2014 20:34 UTC
Return-Path: <kurt@roeckx.be>
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 50DD61A0684 for <trans@ietfa.amsl.com>; Thu, 29 May 2014 13:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] 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 wHpT4YCOmqI0 for <trans@ietfa.amsl.com>; Thu, 29 May 2014 13:34:09 -0700 (PDT)
Received: from defiant.e-webshops.eu (defiant.e-webshops.eu [82.146.122.140]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86AB91A066D for <trans@ietf.org>; Thu, 29 May 2014 13:34:09 -0700 (PDT)
Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by defiant.e-webshops.eu (Postfix) with ESMTP id 791851C20D6; Thu, 29 May 2014 22:34:04 +0200 (CEST)
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 50DA81FE00F3; Thu, 29 May 2014 22:34:04 +0200 (CEST)
Date: Thu, 29 May 2014 22:34:04 +0200
From: Kurt Roeckx <kurt@roeckx.be>
To: Rob Stradling <rob.stradling@comodo.com>
Message-ID: <20140529203404.GA20394@roeckx.be>
References: <20140529175912.GB15165@roeckx.be> <5387961D.1010503@comodo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5387961D.1010503@comodo.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/GvgljLM29fKc3YOIODfjVS6c0lk
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: Thu, 29 May 2014 20:34:11 -0000
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? Kurt
- [Trans] Parsing existing logs entries. Kurt Roeckx
- Re: [Trans] Parsing existing logs entries. Rob Stradling
- Re: [Trans] Parsing existing logs entries. Kurt Roeckx
- Re: [Trans] Parsing existing logs entries. Rob Stradling
- Re: [Trans] Parsing existing logs entries. Ben Laurie