IETF Logo Mail Archive

Re: [Trans] RFC6962 BIS Log file encodings.

"Salz, Rich" <rsalz@akamai.com> Fri, 28 March 2014 18:32 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 14EA81A095D for <trans@ietfa.amsl.com>; Fri, 28 Mar 2014 11:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 pEprQIGTV3Ys for <trans@ietfa.amsl.com>; Fri, 28 Mar 2014 11:32:25 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id DCAC41A0959 for <trans@ietf.org>; Fri, 28 Mar 2014 11:32:24 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 90518476BA; Fri, 28 Mar 2014 18:32:20 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (unknown [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id 5E800476A9; Fri, 28 Mar 2014 18:32:20 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub7.kendall.corp.akamai.com [172.27.105.23]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 481178003C; Fri, 28 Mar 2014 18:32:20 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by usma1ex-cashub7.kendall.corp.akamai.com ([172.27.105.23]) with mapi; Fri, 28 Mar 2014 14:32:19 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Rick Andrews <Rick_Andrews@symantec.com>, Phillip Hallam-Baker <hallam@gmail.com>
Date: Fri, 28 Mar 2014 14:32:18 -0400
Thread-Topic: [Trans] RFC6962 BIS Log file encodings.
Thread-Index: Ac9KsXj0MD4tIBGmRdufjav8x8zLiAAAU+fQAABLfHA=
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C711FD4AEA05@USMBX1.msg.corp.akamai.com>
References: <CAMm+Lwjy7gMphsfByROYP2WDTvP4nVkCQPj=oHkVFr=AQv=qjw@mail.gmail.com> <5322131A.2080507@comodo.com> <CAMm+Lwhz7KM44kMgn8mdFtR6Ow=aMik-5GD-Wge+JZUKz751mA@mail.gmail.com> <CALzYgEdSs0+SJrL9uzem1NnWv=jPAFr_dxrqvLkSqyd_nX+yGg@mail.gmail.com> <544B0DD62A64C1448B2DA253C011414607C85F39F4@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM> <CAMm+LwjriXwEYZZX03y=w-gC_O5uczuXKnAcJpUFnZ-m6JS4Pw@mail.gmail.com> <544B0DD62A64C1448B2DA253C011414607C85F3B2D@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM>
In-Reply-To: <544B0DD62A64C1448B2DA253C011414607C85F3B2D@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2A0EFB9C05D0164E98F19BB0AF3708C711FD4AEA05USMBX1msgcorp_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/U53BV5Uiqz4xd20xR-eP8I8wJ7M
Cc: Eran Messeri <eranm@google.com>, "trans@ietf.org" <trans@ietf.org>, Rob Stradling <rob.stradling@comodo.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: Fri, 28 Mar 2014 18:32:27 -0000

Ø  I understand that there are problems with ASN.1 and many people don't like it, but if we're talking about X.509 certificates we have to use ASN.1. All of our code for putting blobs into a cert work by defining the structure using ASN.1. Yes, we can add a blob that has some other encoding, but it's more difficult.


Ø  If the encoding were ASN.1, it might make adoption more straightforward.

+1


--
Principal Security Engineer
Akamai Technology
Cambridge, MA

v2.23.0 | Report a Bug | By Email