Re: Problems with my last message about ASN.1 :(

[Dean Povey <povey@xxxxxxxxxxxxxxx>]

> 
> In reply to my own previous message about PolicyQualifierId:
> 
> I realised after I sent this message that you can't have an enumerated
> type with OIDs in it.  Either we have to define integer identifiers here or 
> change the definition of PolicyQualifierId to OBJECT IDENTIFIER.
> 
> Any thoughts???
> 
> Dean. 
> 

It appears my previous message actually bounced.  This mailing list seems a 
little flakey lately :(.

What I am concerned about is the discrepancy between the body of the Part I 
draft and the ASN.1 at the back with regard to PolicyQualifiers.  Both define 
OIDs for the CPS and User notice policy types, however the PolicyQualifierID 
is defined in the ASN.1 at the back as:

PolicyQualifierId ::= ENUMERATED {
   qualId1(1), qualId2(2), qualId3(3), qualId(4), qualId5(5) }

whereas in section 4.2.1.5 on page 21 it is defined as:

PolicyQualifierId ::= ENUMERATED {
   id-pkix-cps, id-pkix-unotice }

Which given that id-pkix-cps and id-pkix-unotice are defined as OIDs (allbeit 
with different names to the ones in the back), is not valid ASN.1.

The options are to define PolicyQualifierID as type OBJECT IDENTIFIER (is this 
in violation of the X.509 standard?), or to not define OIDs for these policy 
qualifiers but use integer codes to identify them.

Is that clear?


-- 
+----------------------------------------+-----------------------------------+
| Dean Povey,                            |  Email: povey@dstc.edu.au         |
| Research Scientist, Security Unit,     |  Phone: +61 7 3864 2799           | 
| CRC for Distributed Systems Technology |  Fax:   +61 7 3864 1282           |
+----------------------------------------+-----------------------------------+