IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 18 March 2015 15:12 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 D90671A1A67 for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 08:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] 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 0eJ63LS8_wsk for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 08:12:37 -0700 (PDT)
Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F04381A1A17 for <pkix@ietf.org>; Wed, 18 Mar 2015 08:12:36 -0700 (PDT)
Received: from [10.20.30.101] (50-1-51-95.dsl.dynamic.fusionbroadband.com [50.1.51.95]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t2IFCZ35094656 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pkix@ietf.org>; Wed, 18 Mar 2015 08:12:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 50-1-51-95.dsl.dynamic.fusionbroadband.com [50.1.51.95] claimed to be [10.20.30.101]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <550881DE.8090304@bbn.com>
Date: Wed, 18 Mar 2015 08:12:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF3BDB0E-F3FB-455F-88E7-7196ADCCE60B@vpnc.org>
References: <550881DE.8090304@bbn.com>
To: pkix <pkix@ietf.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/cnwf0yPLDEIfqhjw9Lm6unyPjP0>
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, 18 Mar 2015 15:12:39 -0000

There is no problem with an extension being a blob of data that does not have an ASN.1 structure. Any PKIX-y application that *needs* to read the parts of the blob can do so in the same way that a TLS-y application does, using the same decoder. To be clear: most PKIX-y applications don't descend into ASN.1 structures for extensions they don't know about, so this isn't really any different.

--Paul Hoffman

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