ASN.1
Click on the red underlined text to get to the source
... The X.400 protocols are encoded in a structured manner according to
ASN.1, whereas RFC 822std11(-> 2822prop) is text encoded. To define a detailed
mapping, it is necessary to refer to detailed protocol elements ...
... ASN.1 ...
... There is a need to convert between ASCII text and some of the types
defined in ASN.1 [14]. For each case, an EBNF syntax definition is
...
... syntax definition is
given, for use in all of this specification, which leads to a mapping
between ASN.1, and an EBNF construct. All EBNF syntax definitions of
ASN.1 ...
... ASN.1, and an EBNF construct. All EBNF syntax definitions of
ASN.1 types are in lower case, whereas ASN.1 types are referred to
with the first letter in upper case. Except as noted, all mappings
...
... syntax definitions of
ASN.1 types are in lower case, whereas ASN.1 types are referred to
with the first letter in upper case. Except as noted, all mappings
are symmetrical.
...
... ASN.1 Integer will be mapped onto EBNF.numericstring. In
many cases ASN.1 will enumerate Integer values or use ENUMERATED. An
EBNF encoding ...
... encoding labelled-integer is provided. When mapping from EBNF to
ASN.1, only the integer value is mapped, and the associated text is
discarded. When mapping from ASN.1 ...
... ASN.1, only the integer value is mapped, and the associated text is
discarded. When mapping from ASN.1 to EBNF, a text label may be
added. It is recommended that this is done wherever possible and
that clear text labels are chosen.
...
... Object identifiers are represented in a form similar to that given in
ASN.1. The order is the same as for ASN.1 (big-endian). The numbers
...
... Object identifiers are represented in a form similar to that given in
ASN.1. The order is the same as for ASN.1 (big-endian). The numbers
are mandatory, and used when mapping from the ASCII ...
... big-endian). The numbers
are mandatory, and used when mapping from the ASCII to ASN.1. The
key-strings are optional. It is recommended that as many strings as
possible are generated when mapping from ASN.1 ...
... ASN.1. The
key-strings are optional. It is recommended that as many strings as
possible are generated when mapping from ASN.1 to ASCII, to
facilitate user recognition.
...
...
In most cases, the EBNF encoding maps directly to the ASN.1 encoding
of the attribute. There are a few exceptions. In cases where an
attribute can be encoded as either a PrintableString or NumericString
...
... attribute can be encoded as either a PrintableString or NumericString
(Country, ADMD, PRMD), either form is mapped into the EBNF. When
generating ASN.1, the NumericString encoding shall be used if the
string contains digits and only digits.
...
... original message is available, but is not a legal message format, a
dump of the ASN.1 may be included, encoded as application/octet-
string. This is recommended, but not required.
...
... Appendix L - ASN.1 Summary ...
... CCITT/ISO, "Specification of Abstract Syntax Notation One (ASN.1)," CCITT Recommendation X.208 / ISO/IEC 8824, Dec 1988. ...