Re: [Trans] RFC6962 BIS Log file encodings.

"Salz, Rich" <rsalz@akamai.com> Mon, 31 March 2014 15:19 UTC

Return-Path: <rsalz@akamai.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 E56251A6F01 for <trans@ietfa.amsl.com>; Mon, 31 Mar 2014 08:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_45=0.6, 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 uWZRTJ-rwLQZ for <trans@ietfa.amsl.com>; Mon, 31 Mar 2014 08:19:08 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 90DA71A0862 for <trans@ietf.org>; Mon, 31 Mar 2014 08:19:08 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 1C3CA165576; Mon, 31 Mar 2014 15:19:05 +0000 (GMT)
Received: from prod-mail-relay04.akamai.com (prod-mail-relay04.akamai.com [172.27.8.27]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id 11215165567; Mon, 31 Mar 2014 15:19:05 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub4.kendall.corp.akamai.com [172.27.105.20]) by prod-mail-relay04.akamai.com (Postfix) with ESMTP id B61F847BD5; Mon, 31 Mar 2014 15:19:04 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by USMA1EX-CASHUB4.kendall.corp.akamai.com ([172.27.105.20]) with mapi; Mon, 31 Mar 2014 11:19:04 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Stephen Kent <kent@bbn.com>, "trans@ietf.org" <trans@ietf.org>
Date: Mon, 31 Mar 2014 11:19:03 -0400
Thread-Topic: [Trans] RFC6962 BIS Log file encodings.
Thread-Index: Ac9M9EZFxzx1MMW1RhmnpIjTc0lJQgAABVXA
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C711FD90F03D@USMBX1.msg.corp.akamai.com>
References: <r422Ps-1075i-50EDDACBA0064390A2CED9708B9D3E07@Williams-MacBook-Pro.local> <533986E8.6040201@bbn.com>
In-Reply-To: <533986E8.6040201@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/b_ShiWBLXu9542JCkMZ8AeVz7Ko
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:19:10 -0000

>  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.

	/r$

--  
Principal Security Engineer
Akamai Technology
Cambridge, MA