Supported, but as SEQUENCE
s and SEQUENCE OF
s respectively.
In other words, the handling of the unordered nature of SET fields is left to the
code generated by the ASN.1 compiler (which represents them in the generated code as normal,
``fixed'' C structs), while the SET OF is handled as a simple array of the contained type:
the extra knowledge that no two elements can be the same is enforced by the calling code,
not by the toolchain. Keep in mind, though, that...(Copying again from [17]):
It is recommended to use the SEQUENCE OF type as much as possible:
indeed, when using canonical encoding rules such as the CER or the
canonical PER (see Part III on page 391), the SET OF type requires
dynamically sorting the encoding of every value before transmitting it!