IETF Logo Mail Archive

Re: [Trans] RFC6962 BIS Log file encodings.

Ben Laurie <benl@google.com> Tue, 01 April 2014 09:33 UTC

Return-Path: <benl@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 121E71A86DD for <trans@ietfa.amsl.com>; Tue, 1 Apr 2014 02:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level:
X-Spam-Status: No, score=-1.389 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 LiJTAZDhtnOD for <trans@ietfa.amsl.com>; Tue, 1 Apr 2014 02:33:24 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1631A86FD for <trans@ietf.org>; Tue, 1 Apr 2014 02:33:23 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id lh14so9184869vcb.20 for <trans@ietf.org>; Tue, 01 Apr 2014 02:33:20 -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=ZkYHmqDyZahM2ASqAv0BKfErWMEookOlXSHkF5TOCVk=; b=cggd3MFf8JsKvh/GDGqm/myxCRfeMG0X06vJ5yfl5OqF5jn91sCtQGsZev6u4ordmM HkrEe4wVMIzIjY5OyS91GX2Q6A5HDjiCDDOs4WHvgCtXDyBl/pz6sMPwL+HIHXa+mmnj Hp3EMfEPSURmn1QpJiPLNxKazGytveBTqcI+qNLUbpji0HMOO5RGvMMx4VypylZZzI3W qpwy/F5sFZFrTcgZsQ3dhjhCg2yE2FU68soRlx/ENAjtdB+n4dfMfnvtLwfruVXvL+TW 0IPkRv7tvhp7K7kN4JAg4njw0/fEkyru9SdUHMIOemukkgVIVWfAMBweegbc0C4tf3w+ hLUA==
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=ZkYHmqDyZahM2ASqAv0BKfErWMEookOlXSHkF5TOCVk=; b=k3BEKTyFoy0TmSwkqerGl6yvQzPbh2ztFKV9C+Lsy8aOhLVtDYpF772SN6xCPWIaY0 4b+p39Tax7dumOG4tdv0qD6l+MB/JE//FKNNBjx5h6Jeh3cVG0D7VzDIbVaFeiSi2MAC uoiYsZ+cJh7K6zx9HgWfyGRNzXDHDqU3BBv1mMjVP5heyUczJOjuwduGUs6cZ2ateV56 Op1ZEArbZ32QUTQO2QEKkSwwlvGXC2Bl9wnHon39hHo8cXF0QmctTl1ux6DhtUE2R+vl nGQ8wvneQUO4sx1/M3DnQ+tYX698IinX8hvc8SNzSXlesONGx5uiYqrAgKFPGry2u8ad YnYg==
X-Gm-Message-State: ALoCoQkZcBshqMSOXCCcnZogQEppfq1q/Q/kRkk9godyG7OsinLGW9mtaU2O1Fs1BqY3wSmaXI5PjOjSWBkc8Z74GqPczQIInMjn3mMb9T0abj3jz8vxQHOTkHaXvMe69BId9kRQEZ0s1yyZ2QKAwL9Y6PIQ/hvw8EJUCHy2R3YABEWJqPohfmfqbjrRwIE0TwATvgNUpGEP
MIME-Version: 1.0
X-Received: by 10.220.167.2 with SMTP id o2mr27779273vcy.8.1396344800175; Tue, 01 Apr 2014 02:33:20 -0700 (PDT)
Received: by 10.52.119.179 with HTTP; Tue, 1 Apr 2014 02:33:20 -0700 (PDT)
In-Reply-To: <533A7923.9040302@mozilla.org>
References: <r422Ps-1075i-50EDDACBA0064390A2CED9708B9D3E07@Williams-MacBook-Pro.local> <533986E8.6040201@bbn.com> <533A7923.9040302@mozilla.org>
Date: Tue, 01 Apr 2014 10:33:20 +0100
Message-ID: <CABrd9SSVxvCzWsJbL+Lx_4MBFxUKyo=SMrvNxvkPCK64Cj47vw@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Gervase Markham <gerv@mozilla.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/eTQQEnk_O3oTIzztipVGKH_cEV8
Cc: "trans@ietf.org" <trans@ietf.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: Tue, 01 Apr 2014 09:33:25 -0000

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.

v2.23.0 | Report a Bug | By Email