in 1994 and replaced with the "open type" which allows ASN.1 compilers to explicitly link the contents of the "open type" field with the object identifier.
In other LTANS specifications the following approach is used: One module is specified in 'CURRENT' ASN.1 syntax.An alternative module is done for 'old' compilers with is an almost 88 syntax
Which one is normative is still a debate (as in another group). In some specs also an XSD schema is defined. For LTAP at least the XSD is automatically generated from the ASN.1 and produces the same encodings and an XER encoding of the ASN.1 Besides that and in response to Sean. Although a module can reuse a name that is defined in another module, I agree that this may be confusing. Peter --To verify the signature, see http://edelpki.edelweb.fr/ Cela vous permet de charger le certificat de l'autorite'; die Liste mit zuru"ckgerufenen Zertifikaten finden Sie da auch.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature