IETF Logo Mail Archive

Re: Distinguished names and X509v3 extension OIDs (fwd)

"Charles W. Gardiner" <gardiner@bbn.com> Wed, 02 April 1997 15:18 UTC

Received: by suntan.tandem.com (8.6.12/suntan5.970212) for ietf-pkix-relay id HAA25038; Wed, 2 Apr 1997 07:18:20 -0800
Received: from manchester.bbn.com by suntan.tandem.com (8.6.12/suntan5.970212) for <ietf-pkix@tandem.com> id HAA25035; Wed, 2 Apr 1997 07:18:18 -0800
Received: (gardiner@localhost) by manchester.bbn.com (8.6.9/8.6.5) id KAA06431; Wed, 2 Apr 1997 10:18:54 -0500
Message-Id: <199704021518.KAA06431@manchester.bbn.com>
To: dpkemp@missi.ncsc.mil
cc: ietf-pkix@tandem.com, ssl-users@mincom.oz.au
Subject: Re: Distinguished names and X509v3 extension OIDs (fwd)
In-reply-to: Your message of "Tue, 01 Apr 1997 09:12:42 EST." <199704011412.JAA05691@argon.ncsc.mil>
Date: Wed, 02 Apr 1997 10:18:53 -0500
From: "Charles W. Gardiner" <gardiner@bbn.com>

    Since tagging is implicit in extensions, wouldn't it be possible to have a
BIT STRING with named bits that has a context-specific tag which hides the BIT
STRING tag?  If one didn't know the ASN.1, one wouldn't be able to tell which
bits were named.  This affects the encoding, I believe.  Or a context=specific-
tagged BOOLEAN would also be concealed.

Charlie Gardiner

v2.23.0 | Report a Bug | By Email