I think I recall that since GeneralName is a CHOICE that using it with
IMPLICIT tags requires the implicit tag to be declared explicitly to avoid
ambiguity. I'm not an ASN.1 expert but I've come across this problem before
and had to work around it by reversing the implicit tag of GeneralName.
On Thu, May 29, 2003, Fernando Moya wrote:
Hi, I am having problems with GENERAL_NAMES in the following sequence: :
-
DEFINITIONS IMPLICIT TAGS
Seq1 ::= SEQUENCE
{
field1 INTEGER,
field2 Seq2
}
Seq2 ::=
On Fri, May 30, 2003, Steven Reddie wrote:
I think I recall that since GeneralName is a CHOICE that using it with
IMPLICIT tags requires the implicit tag to be declared explicitly to avoid
ambiguity. I'm not an ASN.1 expert but I've come across this problem before
and had to work around it
Thanks for the clarification.
Regards,
Steven
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dr. Stephen Henson
Sent: Friday, 30 May 2003 9:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Problems with GENERAL_NAMES on IMPLICIT mode
On Fri, May 30, 2003
So instead of doing:
ASN1_IMP_OPT(Seq2, Sub_field2, GENERAL_NAMES,1),
do:
ASN1_IMP_SEQUENCE_OF_OPT(Seq2, Sub_field2, GENERAL_NAME,1),
Steve
It works ok. Thanks a lot.
Fernando Moya Bernal.
University of Malaga.
