So what the Erlang asn1ct does is: Decode the incoming EXTERNAL type,
convert it to the 1994 format and hand it to the user program.
The encoder is opposite: Take what the user supplies (in our case 1994)
and then transform it to 1990 before handing it to the actual encoder function.
The only problem is: The 1994 format does only support OCTET STRING as actual
embedded data type, whereas the 1990 format can also indicate
'singla-asn1-type', i.e. a constructed type.
So since that information is already lost before we ever get the record from
the Erlang asn1 decoder, it will be re-encoded as OCTET STRING :(
Until this is fixed in the asn1ct/asn1rt code, we have to use this workaround...
Harald Welte
21c6b94271