IETF Logo Mail Archive

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

Denis <denis.ietf@free.fr> Wed, 18 March 2015 15:52 UTC

Return-Path: <denis.ietf@free.fr>
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 6CCBC1A1AAE for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 08:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35] 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 DGzKxDCwZocE for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 08:52:28 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [IPv6:2a01:e0c:1:1599::15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EA171A1A8F for <pkix@ietf.org>; Wed, 18 Mar 2015 08:52:28 -0700 (PDT)
Received: from [192.168.0.14] (unknown [88.182.125.39]) by smtp6-g21.free.fr (Postfix) with ESMTP id D54A7822C8 for <pkix@ietf.org>; Wed, 18 Mar 2015 16:51:26 +0100 (CET)
Message-ID: <55099F3D.4070705@free.fr>
Date: Wed, 18 Mar 2015 16:52:29 +0100
From: Denis <denis.ietf@free.fr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: pkix@ietf.org
References: <550881DE.8090304@bbn.com> <EF3BDB0E-F3FB-455F-88E7-7196ADCCE60B@vpnc.org>
In-Reply-To: <EF3BDB0E-F3FB-455F-88E7-7196ADCCE60B@vpnc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/wc2nWYV9PK-9uxBg-50KzGDhmus>
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:52:30 -0000

+1

Denis
> 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
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix

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