Re: [Trans] RFC6962 BIS Log file encodings.

Ben Laurie <benl@google.com> Mon, 31 March 2014 15:28 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 28B061A0807 for <trans@ietfa.amsl.com>; Mon, 31 Mar 2014 08:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.789
X-Spam-Level:
X-Spam-Status: No, score=-0.789 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, J_CHICKENPOX_45=0.6, 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 60ry_mNeviMZ for <trans@ietfa.amsl.com>; Mon, 31 Mar 2014 08:28:15 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id D63E51A0549 for <trans@ietf.org>; Mon, 31 Mar 2014 08:28:14 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id oy12so8135157veb.40 for <trans@ietf.org>; Mon, 31 Mar 2014 08:28:11 -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=8wXmTZ8BE/vhO4NspA7mgoyriSSSvkWlt3ChLY0Ny4s=; b=eij9DiDduVWzp5qRS4Gs3Vzae98VWWHTxg5xeUHpU4ST4RiZyNGX7fXammQvNLTX9L sRviClgIzttSDjK28d4QA1wDdlfLiPSaXvLOkZZgbtn9WAy4cMIv25tghu//MLr+dFII /iwJ4cAs/rijF45ZrNQH5ah9GHpe+zvd++dBD7p2z4yc+JMn5/z+c4GKz8d4OT5PNzdL ljQNwBKW40l66/HcnK48QkXK1gN45hU8dqhIRxCIn8LCk4saSfv9VvnP54DojyPuCH8o g7V9+QkCNmgppzaJUF7kD1wtnQS2knFsyx7JwFriJovGovg1mk2F9LWMsF4zlqbol8FM ymTA==
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=8wXmTZ8BE/vhO4NspA7mgoyriSSSvkWlt3ChLY0Ny4s=; b=c9fCcK3PuJHzjqZpOc7rvn/SvNMvbK5h4XBxjvHaRy3RJW8JG2CBczdZfB9QcMrIxb FeNl3ftaKI+laIx+dpxTCS5opHT3AxSocjXKQu/a4HZbclSXoQREQXC64uxQ2UolbJ2c F2TABVxUmE6820V2IcMYB002QPzThnUjj7KL6aBlT4zUSocxvSkT8qwfZgANE+9vB9Hj TttgJQA04DeB6qkRseFBHPQU1OcNdV6sPWZVe/3/4rlWNfOAzI48DDaPbNS4IO54eVWr 9PedG11ZsTT4iHNd6huufoRG04sQaeE1HVEoxLyoIvNOpgrbvcqqhU/WOS/6/4TFMrFy jDAw==
X-Gm-Message-State: ALoCoQlZfGO+Vkt1D6EJsSEISREE0fxrkCWd3LNhOgQhz2AN0Q8/e34lifQA8iSniBzDYPwinjeJ+o8S6gIHWx7x68Go/+6p+kFkFYpWWyylVpoCCZzQD+YKxP78+W4uiqE/jtrpfJ8aC+YOnCsRiPllZLZVrjBrdZbh57x6jhVWZjroNKBDrb9u79cfB3tS8p9LAW4s3E0p
MIME-Version: 1.0
X-Received: by 10.220.249.6 with SMTP id mi6mr473205vcb.33.1396279691445; Mon, 31 Mar 2014 08:28:11 -0700 (PDT)
Received: by 10.52.119.179 with HTTP; Mon, 31 Mar 2014 08:28:11 -0700 (PDT)
In-Reply-To: <2A0EFB9C05D0164E98F19BB0AF3708C711FD90F03D@USMBX1.msg.corp.akamai.com>
References: <r422Ps-1075i-50EDDACBA0064390A2CED9708B9D3E07@Williams-MacBook-Pro.local> <533986E8.6040201@bbn.com> <2A0EFB9C05D0164E98F19BB0AF3708C711FD90F03D@USMBX1.msg.corp.akamai.com>
Date: Mon, 31 Mar 2014 16:28:11 +0100
Message-ID: <CABrd9SS5d6De38tE-cxWBTopOh7vZhD3EHCW30rEzThj-g30-w@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: "Salz, Rich" <rsalz@akamai.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/9XoDseTXl6UYXZ85nnxQvhsGv7k
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: Mon, 31 Mar 2014 15:28:16 -0000

On 31 March 2014 16:19, Salz, Rich <rsalz@akamai.com> wrote:
>>  But since we're talking about data from a TBS cert,since the generators of the data are CAs (who should 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.
>
> Adding another encoding makes things more complex.  Therefore, the simplest thing to do is use ASN.1
>
> It's like when you're editing someone else's source code: the best thing to do is preserve the existing style.

As I just mention, its not actually another encoding - the data
structure can also (ideally should also) be sent as a TLS extension,
in which case ASN.1 is not the simplest thing to do.

>
>         /r$
>
> --
> Principal Security Engineer
> Akamai Technology
> Cambridge, MA
>
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans



-- 
Certificate Transparency is hiring! Let me know if you're interested.