A suggested ISUP written in ASN.1/ECN project. My comments:
1. The ISUP comes in many different flavours. We would need to know which Info Elements (IE) were needed -and also a list of required options. There are a few options in the ISUP. 2. The amount of time that would be needed to invest in order to obtain an ASN.1/ECN version of the ISUP would be considerable. I guess that's why so few say they have actually done the task. 3. It would be interesting to find out how many firms have actually had a go with this task ? And who have actually accomplished it ? 4. The best solution from my point of view would be to let several firms pool their efforts - once the ASN.1 source file is there it could be reused and indefinite number of times by various vendors/manufacturers/testing companies/Universities/.... 5. I do appreciate the support you offer from OSS. It would most likely be neccesary underway to have alterations in any vendors' ASN.1/ECN parser and code generator, so given the ISUP development team got stuck it could get neccesary to obtain more than just the kind of support you offer. 6. Actually I think we should think about the community approach here - Why not split the Info Elements among say 10 to 50 individuals / development groups and then publish the outcome. After all the competition situation would not be altered after the publishing of the common ISUP. OSS would benefit from this. The participants would obtain insight in their generated code and the integration of the code in their development paths. The generated code side does not neccesary need to be open. Only the ASN.1 /ECN code would need to be shared. Steen Oluf Karlsen S�holtvej 6 Vester Vandet DK-7700 Thisted Danmark Tel +45 97 97 72 72 email [EMAIL PROTECTED] _______________________________________________ ASN1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
