[EMAIL PROTECTED] wrote:
>
> I am a "novice" in ASN.1 and I am currently working on the topic of GSM, the
> nearly world-wide standard for wireless telephony. In this scope I am dealing
> with the billing format of GSM, called TAP (Transfer Account Procedure).
> There are two existing versions of TAP: one (TAP2+) using fixed length records
> in basic ASCII files, the other one (TAP3) using ASN. 1 as the encoding
> mechanism for the physical file layer.
> My question regards the complexity of the implementation of ASN.1 in this
> context. Is it really complex to implement ASN.1 in comparison to a basic ASCII
> encoding mechanism ?
Not complex, particularly if you use one of the compilers that are referenced
at:
http://asn1.elibel.tm.fr/links/#tools
> Which are the real advantages ?
Concerning the advantages of using tools, look e.g. at Chapter 22 of my book
that you can download from: http://www.oss.com/asn1/dubuisson.html
--
Olivier DUBUISSON
france telecom R&D
_ DTL/MSV - 22307 Lannion Cedex - France
( ) tel: +33 2 96 05 38 50 - fax: +33 2 96 05 39 45
/.\/ --------------------------------------
\_/\ Site ASN.1 : http://asn1.elibel.tm.fr/
