IETF Logo Mail Archive

Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT

Russ Housley <housley@vigilsec.com> Sun, 22 March 2015 17:15 UTC

Return-Path: <housley@vigilsec.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 3809B1A0099 for <trans@ietfa.amsl.com>; Sun, 22 Mar 2015 10:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 pS5BwAOOZfVs for <trans@ietfa.amsl.com>; Sun, 22 Mar 2015 10:15:10 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id BE8091A0065 for <trans@ietf.org>; Sun, 22 Mar 2015 10:15:10 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 3D59B9A4042 for <trans@ietf.org>; Sun, 22 Mar 2015 13:15:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id RXfR2e06-Bl6 for <trans@ietf.org>; Sun, 22 Mar 2015 13:14:39 -0400 (EDT)
Received: from dhcp-8867.meeting.ietf.org (dhcp-8867.meeting.ietf.org [31.133.136.103]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 58D079A402D for <trans@ietf.org>; Sun, 22 Mar 2015 13:14:39 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1085)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <550C6B61.9000308@gmail.com>
Date: Sun, 22 Mar 2015 13:14:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D49C309-1AA0-48CD-AD46-944E7BDFC267@vigilsec.com>
References: <052.10eb26d4fde793d0a60756eb4c9dc8cc@tools.ietf.org> <067.3f6fd76ea878508f23fc24cdf754d7e0@tools.ietf.org> <54EF8403.90307@bbn.com> <54EFAAE7.3040707@comodo.com> <54EFB7B9.1010001@gmail.com> <537F8554-19B7-4C66-BA5E-A48D11FFCB51@vigilsec.com> <CABrd9SRn0ayrWzEstsZ5xCPY5seUGtoMgZsokhkzizjM=N2wJQ@mail.gmail.com> <55005FDD.8060009@bbn.com> <55007BB5.4040007@cs.tcd.ie> <5501A6B3.1090605@bbn.com> <5501A7B6.9090100@cs.tcd.ie> <550C62D1.2050002@bbn.com> <550C6B61.9000308@gmail.com>
To: trans@ietf.org
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/cXQ1et0T_tnT02gDpyxUUK78_WM>
Subject: Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT
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: Sun, 22 Mar 2015 17:15:12 -0000

Stephen Farrell and I discussed this today.  When this document reaches IETF Last Call, I will raise this question from two perspectives.  First, ask if others agree with my interpretation that the use of a structure other that ASN.1 is  prohibited by RFC 2459, RFC 3280, and RFC 5280.  Second, ask if this decision will break any certificate processing software.  

Russ


On Mar 20, 2015, at 2:48 PM, Melinda Shore wrote:

> As I've said several times, unless there's new information, we're
> done discussing this.
> 
> Melinda

v2.23.0 | Report a Bug | By Email