ASCII
Click on the red underlined text to get to the source
... 822std11(-> 2822prop) message consists of a header, and content which is
uninterpreted ASCII text. The header is divided into fields, which
are the protocol elements ...
...
2. To describe the structure of IA5 or ASCII information not in
an RFC 822std11(-> 2822prop) message.
...
... (1988) may be used [13]. These will then be encoded in
ASCII. This is the approach mandated in RFC 1327(-> 2156prop).
...
...
2. This mapping may be used if the characters are not contained
within ASCII repertoire, but are all in an IANA-registered
character set ...
... 2157prop.
There is also a need to represent Teletex Strings in ASCII, for some
aspects of OR Address ...
... ASN.1 (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
...
... 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.
...
...
Some information in RFC 822std11(-> 2822prop) is represented in ASCII, and needs to be
mapped into X.400 elements ...
... X.400 elements encoded as printable string. For this
reason, a mechanism to represent ASCII encoded as PrintableString is
needed.
...
...
A structured subset of EBNF.printablestring is now defined. This
shall be used to encode ASCII in the PrintableString character set.
...
... The 822.3DIGIT in EBNF.ps-encoded-char shall have range 0-127, and is
interpreted in decimal as the corresponding ASCII character. Special
encodings are given for: at sign (@), percent (%), exclamation
...
...
A reversible mapping between PrintableString and ASCII can now be
defined. The reversibility means that some values of printable
string (containing round braces) cannot be generated from ASCII ...
... ASCII can now be
defined. The reversibility means that some values of printable
string (containing round braces) cannot be generated from ASCII.
Therefore, this mapping shall only be used in cases where the
printable strings have been derived from ASCII ...
... ASCII.
Therefore, this mapping shall only be used in cases where the
printable strings have been derived from ASCII (and will therefore
have a restricted domain). For example, in this specification, it is
...
...
To encode ASCII as PrintableString, the EBNF.ps-encoded syntax is
used, with all EBNF.ps-restricted-char mapped directly. All other
822.CHAR are encoded as EBNF.ps-encoded-char.
...
...
To encode PrintableString as ASCII, parse PrintableString as
EBNF.ps-encoded, and then reverse the previous mapping. If the
PrintableString cannot be parsed, then the mapping is being applied
...
...
PrintableString ASCII
'a demo.' <-> 'a demo.'
...
... set of attributes
(type/value pairs). It is clearly necessary to be able to encode
this in ASCII for gatewaying purposes. All components shall be
encoded, in order to guarantee return of error messages, and to
...
... The following keys identify different EBNF encodings, which are
associated with the ASCII representation of MTS.ORAddress.
...
... (Printable String) Domain defined type "RFC-822" is defined. The
associated attribute value is an ASCII string encoded according to
Section 3.3.3 of this specification. The interpretation of the ASCII
string follows RFC 822std11(-> 2822prop) ...
... associated attribute value is an ASCII string encoded according to
Section 3.3.3 of this specification. The interpretation of the ASCII
string follows RFC 822std11(-> 2822prop), and RFC 1123std3 [10,16]. Domains ...
...
1. Map the domain defined attribute value to ASCII, as defined
in Chapter 3, and drop all other attributes.
...
... 2a. If IPMS.ORDescriptor.free-form-name is present, convert it
to ASCII or T.61 (Section 3.5), and use this as the 822.phrase
component of 822.mailbox ...
... IPMS.ORDescriptor.formal-name is absent, IPMS.ORDescriptor.free-
form-name is converted to ASCII (see section 3.5), and used as
822.phrase within the RFC 822std11(-> 2822prop) 822.group ...
... IPMS.IPMIdentifier.user-
relative-identifier mapped to ASCII and angle braces added parses as
822.msg-id, then this is an RFC 822std11(-> 2822prop) generated ID.
...
... subject
Mapped to "Subject:". The contents are converted to ASCII or T.61
(as defined in Section 3.5). CRLF ...
... The format is structured as if it was a message coming from the
gateway, with three body parts. The first body part is ASCII text
structured as follows:
...
... integer support
- Make PrintableString <-> ASCII mapping reversible
- The printable string mapping is aligned to the NBS mapping
...