RE: tagged CHOICEs in CRMF ASN.1

[Carlisle Adams <carlisle.adams@xxxxxxxxxxx>]

Hi James,

While I'm as keen as anyone to remove sources of possible confusion, I
suspect that your request has come too late to be acted upon at this
time (CRMF has already been approved by the IESG and is simply awaiting
publication by the RFC editor, which should happen any day now).

On the bright side, however, it is quite possible that your request will
itself serve the purpose (at least for the current generation of
implementers) since it reminds everyone to be careful here.  Thank you!

Carlisle.


-----Original Message-----
From: James Nicolson [mailto:nicolson@netscape.com]
Sent: Tuesday, December 08, 1998 2:46 PM
To: ietf-pkix@imc.org
Cc: javi@netscape.com
Subject: tagged CHOICEs in CRMF ASN.1

Several  places in the CRMF ASN.1 have tagged CHOICEs: Names in
CertTemplate, Times in OptionalValidity, POPOPrivKey in
ProofOfPossession, GeneralName in POPOSigningKeyInput, EncryptedKey in
PKIArchiveOptions.  Although the CRMF definition indicates a default of
IMPLICIT tagging,  ASN.1 dictates that a CHOICE is always EXPLICITly
tagged regardless of the default.  In order to remove a source of
possible confusion, could these tags be labeled EXPLICIT, even though
technically it is redundant?