Hi again, I am sorry my problem is only with "ReportingMTACertificate" below. The "RECOMMENDED CRITICALITY" is defined in the CLASS. What is "ReportingMTACertificate"?
Thanks, - Eranga -----Original Message----- From: Eranga Udesh [mailto:[EMAIL PROTECTED] Sent: Friday, January 20, 2006 10:22 AM To: 'Lev Walkin' Cc: 'Kenzo'; '[email protected]' Subject: RE: [ASN1] ASN.1 Remove Value Check Contraints Hi, Thanks for your advice. I have another problem. In the spec I am using (X.519) there's a CLASS like below. -- Extension Fields EXTENSION ::= CLASS { &id ExtensionType UNIQUE, &Type OPTIONAL, &absent &Type OPTIONAL, &recommended Criticality OPTIONAL } WITH SYNTAX { [&Type [IF ABSENT &absent],] [RECOMMENDED CRITICALITY &recommended,] IDENTIFIED BY &id } And there's a definition like, reporting-MTA-certificate EXTENSION ::= { ReportingMTACertificate, RECOMMENDED CRITICALITY {for-delivery}, IDENTIFIED BY standard-extension:32 } If that definition correct? What're the attributes denoted by "ReportingMTACertificate" and "RECOMMENDED CRITICALITY {for-delivery}"? Also is having "," correct in the "reporting-MTA-certificate" definition above. I have attached the full spec for your information. Please advice, as soon as possible. Thanks, - Eranga -----Original Message----- From: Lev Walkin [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 5:23 PM To: Eranga Udesh Cc: 'Kenzo'; [email protected] Subject: Re: [ASN1] ASN.1 Remove Value Check Contraints Eranga Udesh wrote: > Hi, > > Thanks for the advice. Are you saying, I can use as below? > > dir2or3se ABSTRACT-SYNTAX ::= { > SESEapdus ANY > IDENTIFIED BY {id-as-2or3se} > } > > Or > > dir2or3se ABSTRACT-SYNTAX ::= { > SESEapdus {{ANY}, { ANY }} > IDENTIFIED BY {id-as-2or3se} > } > > Could there be any type conflicts if I do that? Something along the lines of the former. However, there's a chance your ABSTRACT-SYNTAX CLASS won't be compiled this way. If this happens, you'll have to model instance of this class as DirInstance ::= SEQUENCE { type-id OBJECT IDENTIFIER, value [0] ANY } > Thanks, > - Eranga > > > -----Original Message----- > From: Lev Walkin [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 19, 2006 4:49 PM > To: Eranga Udesh > Cc: 'Kenzo'; [email protected] > Subject: Re: [ASN1] ASN.1 Remove Value Check Contraints > > Eranga Udesh wrote: >> Hi, >> >> >> >> Thanks for the reply. My target compilation is for BER. Therefore the >> Constraints are not much relevant. If I can remove the constraints from > the >> below definition will do the trick. > > These are not your ordinary value constraints. Value set constraints > describe relationships between an identifier and a particular type to be > encoded. > > You'll have to use the ANY type and decode it manually according to > the specified OBJECT IDENTIFIER. > > >> Thanks, >> >> - Eranga >> >> >> >> _____ >> >> From: Kenzo [mailto:[EMAIL PROTECTED] >> Sent: Thursday, January 19, 2006 4:37 PM >> To: Eranga Udesh >> Subject: Re: [ASN1] ASN.1 Remove Value Check Contraints >> >> >> >> Hi, >> I'm not sure, but You can convert the code as you make. The problem still >> for the: >> >> {{dirAuthenticationTwoWay | dirAuthenticationThreeWay | >> spkmThreeWay} >> >> This is a constrain (maybe beacause I don't know what you have to do) that >> you can lost. You have to link almost 2 parameters to create a table of >> constraints. You have to look to the spec to see the right link between >> these parameters. >> >> Try because is only an idea. >> >> Bye >> Alessandro Lago >> >> 2006/1/19, Eranga Udesh <[EMAIL PROTECTED]>: >> >> Hi, >> >> I have aANS.1 spec as, >> dir2or3se ABSTRACT-SYNTAX ::= { >> SESEapdus >> {{dirAuthenticationTwoWay | dirAuthenticationThreeWay | >> spkmThreeWay}, >> {NoInvocationId}} >> IDENTIFIED BY {id-as-2or3se} >> } >> >> Unfortunately the ASN.1 compiler I use (Erlang) doesn't still support >> SingleValue Set Contraints. How can I convert the above spec to remove > Value >> Set constraint? >> >> Could it be like, >> dir2or3se ABSTRACT-SYNTAX ::= { >> SESEapdus >> IDENTIFIED BY {id-as-2or3se} >> } >> >> Thanks, >> - Eranga >> >> >> _______________________________________________ >> ASN1 mailing list >> [email protected] >> http://lists.asn1.org/mailman/listinfo/asn1 >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> ASN1 mailing list >> [email protected] >> http://lists.asn1.org/mailman/listinfo/asn1 > > > _______________________________________________ ASN1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
