Piotr Stefanski wrote:
My name is Piotr and I am completely new here. I would like to say hello to all members of this forum.
Welcome aboard ;)
Please forgive me if my question is too easy for someone.
There aren't silly questions, only silly answers (at least by my opinion) :)
But I don't understand how decoder should now what ANS.1 type is mentioned in (***) ? It is not possible to guess IA5String tag type from 0x80 0x03 0x053 0x69 0x72 binaries ....
Only by prior knowledge of the ASN.1 definition. If you 'generate' a decoder for a specific protocol (i.e. by compiling the ASN.1 definition into C-Sourcecode), the decoder will 'know' that at this specific position the tag '80h' will/should be an IA5String. A more general decoder (without this knowledge) would just decode it as 'binary data' (i.e. similiar to OCTET STRING), but wouldn't be able to recognize it as a string (least of all as an IA5String). So it's up to the programmer (and his tools) to write the decoder this way, that it will (try to) decode an IA5String there.
Best regards, Bj�rn Schneider
--
Bj�rn Schneider, B.Sc. Fraunhofer-Institute Secure Telecooperation Research Area Security and Smartcard Technology (SICA) Rheinstr. 75
D-64295 Darmstadt, Germany
Tel.: +49-6151-869-280 Fax: +49-6151-869-224
EMail: [EMAIL PROTECTED] URL: http://www.sit.fraunhofer.de
