IETF Logo Mail Archive

Re: [pkix] a question of cert (and OCSP) extension syntax

Sean Leonard <dev+ietf@seantek.com> Wed, 25 March 2015 14:23 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7F81A6FF9 for <pkix@ietfa.amsl.com>; Wed, 25 Mar 2015 07:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 JGhmyZ1KMxpv for <pkix@ietfa.amsl.com>; Wed, 25 Mar 2015 07:23:17 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64341A702A for <pkix@ietf.org>; Wed, 25 Mar 2015 07:23:13 -0700 (PDT)
Received: from [10.9.132.6] (unknown [23.105.140.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 61BB6509C1 for <pkix@ietf.org>; Wed, 25 Mar 2015 10:23:11 -0400 (EDT)
From: Sean Leonard <dev+ietf@seantek.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_FF10CC8D-527D-4AF0-BDEF-ED1486211509"; protocol="application/pkcs7-signature"; micalg="sha1"
Message-Id: <C961CE34-4F55-4B11-86D7-1566B701911D@seantek.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Date: Wed, 25 Mar 2015 09:20:47 -0500
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB6418@uxcn10-5.UoA.auckland.ac.nz>
To: IETF PKIX <pkix@ietf.org>
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C73AAFB6418@uxcn10-5.UoA.auckland.ac.nz>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/Xv0YPCIxcuEf3h561IDZwP4oBxc>
Subject: Re: [pkix] a question of cert (and OCSP) extension syntax
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2015 14:23:18 -0000

On Mar 18, 2015, at 2:10 AM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:

> Melinda Shore <melinda.shore@gmail.com> writes:
> 
>> it's what's in the document until someone can either point to some normative
>> specification that it violates or can point to something that actually would
>> break.
> 
> This isn't a case of standards rules-lawyering though (in any case the PKIX
> spec is flexible enough that you can stuff anything you want into a
> certificate if you interpret things just right, see the famous MPEG-of-cat
> quote), it's that this is creating a situation where an *X.509 standards-
> compliant certificate* contains data that can't be processed by an *X.509
> standards-compliant certificate application*.

I agree with Peter. Keep the encoding as ASN.1 for this extension. It is not particularly onerous, and it preserves compatibility for other applications.

+1

Sean

v2.27.8 | Report a Bug | By Email | System Status