Re: [Trans] RFC6962 BIS Log file encodings.

Eran Messeri <eranm@google.com> Wed, 02 July 2014 11:08 UTC

Return-Path: <eranm@google.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 0FDB51B28FF for <trans@ietfa.amsl.com>; Wed, 2 Jul 2014 04:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_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 2jeQCq6ZLBmC for <trans@ietfa.amsl.com>; Wed, 2 Jul 2014 04:08:35 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F08A91B28FC for <trans@ietf.org>; Wed, 2 Jul 2014 04:08:34 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id va2so11903109obc.5 for <trans@ietf.org>; Wed, 02 Jul 2014 04:08:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QWqGIEfBrpQBUfq4KAlLm7gA+8zbc5NnEmbXqrgGt5Q=; b=li7iekfH1+vC+ty5uvA5huadQ3RbDisctl0b1mZV2X1jZtauW3/wYSBTvHXwUSXjSm jbcjPKAKzy6NJr4UyP8SE1O4bddkqzwErVtAzk/f4n5lz/9Cvy/6k0+MWNXisatOHlem KjSsRIe/DYOOKbDFtWAtxBkapywzTaaSf8XK/xJjUWoBLafkZsfuBqDzFx969uSNJqqT 3/wTukyR/ncWgV+IrHgTV2+h46/Xf7Zvod7N65Y9F2YwtlDG/U8VxpTlpaAyI9aQRuQQ JPjvfVympnySo6gg3cVsb2fd5lEVpAprKz8P24PyReNj7J20Bw5rV3841wVKN8ms975b ak6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QWqGIEfBrpQBUfq4KAlLm7gA+8zbc5NnEmbXqrgGt5Q=; b=Aaesiwik2bE/iY7oRvOUNQsy33chVHM6NyeGHt1CzNDilt94kWcHGkBQmgA16+MlyM lPlP37AyuVzAqkqEMJjF3IUqfgU1Rdgro2g7vk4Ahyg3j0eXZUTytjLUWQ40fW6O3R1L olSyYhCJerL5pNv97EMondyAghPPtymQXeBP27vGoZAYUjhvsfLRmPonHcHAqSgvXgl+ pFLBDKMyeVWRKyAv70YXZMxjCRlWH0sQD3pm3fZQ8PTfsFE8AJQXKxjgYP0P8CWHkktP 2y+Mz2h/tm9odJK/eWsBdpMo+xwd2dORHFif/lt3DG3FBtIjnv1Y5fs9V7P3ZJKXGuuh O+Fw==
X-Gm-Message-State: ALoCoQnO4zClqjTRSV1dRshDZsKhri/ZCVocq6F4YakA3hQHqbwTfc805++yVEXSyyzJ2VBl2jq6
MIME-Version: 1.0
X-Received: by 10.60.33.65 with SMTP id p1mr1543140oei.20.1404299314231; Wed, 02 Jul 2014 04:08:34 -0700 (PDT)
Received: by 10.182.33.200 with HTTP; Wed, 2 Jul 2014 04:08:34 -0700 (PDT)
In-Reply-To: <CABrd9SSVxvCzWsJbL+Lx_4MBFxUKyo=SMrvNxvkPCK64Cj47vw@mail.gmail.com>
References: <r422Ps-1075i-50EDDACBA0064390A2CED9708B9D3E07@Williams-MacBook-Pro.local> <533986E8.6040201@bbn.com> <533A7923.9040302@mozilla.org> <CABrd9SSVxvCzWsJbL+Lx_4MBFxUKyo=SMrvNxvkPCK64Cj47vw@mail.gmail.com>
Date: Wed, 2 Jul 2014 12:08:34 +0100
Message-ID: <CALzYgEfa3Fc2hfYKZyEhWi-M=VC_rC5NNVn=fi=MuW_wSdbsUQ@mail.gmail.com>
From: Eran Messeri <eranm@google.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary=089e01184610c893a904fd33e98c
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/7zNZxbXJYQB0XLqkIO19KOSUzfM
Cc: "trans@ietf.org" <trans@ietf.org>, Gervase Markham <gerv@mozilla.org>, Stephen Kent <kent@bbn.com>
Subject: Re: [Trans] RFC6962 BIS Log file encodings.
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: Wed, 02 Jul 2014 11:08:39 -0000

On Tue, Apr 1, 2014 at 10:33 AM, Ben Laurie <benl@google.com> wrote:

> On 1 April 2014 09:30, Gervase Markham <gerv@mozilla.org> wrote:
> > On 31/03/14 17:16, Stephen Kent wrote:
> >> know how to process ASN.1), and since the consumers of the data are
> >> browsers who already
> >> process certs, it seems reasonable to stick with ASN.1.
> >
> > AIUI, when a browser receives a cert, it will need to reconstruct the
> > pre-cert in order to check that the SCT (which is a signature over the
> > pre-cert) is valid. If that is the case, is it not true that browsers
> > will need to develop some way of _encoding_ ASN.1 which they did not
> > need to have before?
> >
> > (I may well be wrong about this; please correct me if so.)
>
> No, you are right.
>
This is for a very specific case, and encoding ASN.1 For this specific
purpose is much more manageable than a general-purpose ASN.1 encoder. For
those concerned, the code (and tests) for Chrome can be found here:
https://code.google.com/p/chromium/codesearch#chromium/src/net/cert/ct_serialization.cc&sq=package:chromium


>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>