After reading the books at http://www.oss.com/asn1/booksintro.html I am still confused about the impact of the "ANY DEFINED BY" as used in sec 4.1.2.4 of rfc 3280Name ::= CHOICE { RDNSequence } RDNSequence ::= SEQUENCE OF RelativeDistinguishedName RelativeDistinguishedName ::= SET OF AttributeTypeAndValue AttributeTypeAndValue ::= SEQUENCE { type AttributeType, value AttributeValue } AttributeType ::= OBJECT IDENTIFIER AttributeValue ::= ANY DEFINED BY AttributeType Does it just mean ANY, but scoped by the language of a given OID text?
It means that somewhere (possibly in a non-ASN.1 document) is a table that specifies the relationship between AttributeType and AttributeValue. It would, for instance, say that for an AttributeType (OID) of { 1 2 3 }, AttributeValue would be Message52.
Types like ANY and ANY DEFINED BY have been a sty in the eye for many years. They were such trouble that the ASN.1 standards committee declared their use illegal as of 1994, replacing them with information object classes and sets.
===================================================================== Conrad Sigona Voice Mail : 1-732-302-9669 x400 OSS Nokalva Fax : 1-614-388-4156 [EMAIL PROTECTED] My direct line : 1-315-845-1773 _______________________________________________ Asn1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
