🚀 go-pugleaf

While looking at a set of requirements for generalised binding between ASN.1 and "C" could prove to be usefull, my suggestion is to learn from what experience (if any) has been gained from current ASN.1 to "C" bindings.

Having been through this process, and also reviewing the proposed X/Open XOM and XMP API specifications (these seem to be gaining support) I am concerned that there has not been any significant practical use of these API (at least for OSI product parts), a clear example is the way the "user managed  associations" has been specified (or what is missing from the specification), in addition the way (mandatory) synchronous operations have been specified also is a concern for implementors and their application 

users.


Having stated the above, I would be interested in exchanging views on the X/Open API's with developers of OSI related products. 




----
Regards, Charles Moore.

 _____________________________________________________________________________
| 	Australian Overseas Telecommunications Corporation  	  |           |
|_________________________________________________________________|   /-_|\   |
| Email:cmoore@nmpd.oz.au| Snailmail: AOTC       	  	  |  /     *  |
| Phone: +61 7 837 3403  | Network Management Protocol Development|  \_,-._/  |
| Fax:   +61 7 837 5253  | 14/151 Roma St, Brisbane Q. 4003 	  |       v   |
|________________________|_AUSTRALIA____________A.C.N 051 775 556_|___________|
|X.400:/C=AU/ADMD=TELEMEMO/PRMD=TELECOM011/O=TELECOM/OU=NMPD/PN=CHARLES.MOORE/|
|_____________________________________________________________________________|