Mapping between X.400(1988) / ISO 10021 and RFC 822
Voir toute la rfc dans une seule page
Page : 49 / 92
Télécharger le PDF
Auteur(s) :
S.E. Kille
RFC 1138 Mapping X.400(88) and 822 December 1989
- The 822.phrase component if the 822.address is an
822.phrase 822.route-addr construct.
- Any 822.comments, in order, retaining the parentheses.
This string should then be encoded into T.61 us a human
oriented mapping (as described in Chapter 3). If the string
is not null, it should be assigned to
IPMS.ORDescriptor.free-form-name.
3. IPMS.ORDescriptor.telephone-number should be omitted.
If IPMS.ORDescriptor is being used in IPMS.RecipientSpecifier,
IPMS.RecipientSpecifier.reply-request and
IPMS.RecipientSpecifier.notification-requests should be set to
default values (none and false).
If the 822.group construct is present, any included 822.mailbox
should be encoded as above to generate a separate IPMS.ORDescriptor.
The 822.group should be mapped to T.61, and a IPMS.ORDescriptor with
only an free-form-name component built from it.
4.7.2. X.400 -> RFC 822
Mapping from IPMS.ORDescriptor to RFC 822 address. In the basic
case, where IPMS.ORDescriptor.formal-name is present, proceed as
follows.
1. Encode IPMS.ORDescriptor.formal-name (MTS.ORName) as
EBNF.822-address.
2a. If IPMS.ORDescriptor.free-form-name is present, convert it
to ASCII (Chapter 3), and use this as the 822.phrase
component of 822.mailbox using the 822.phrase 822.route-addr
construct.
2b. If IPMS.ORDescriptor.free-form-name is absent. If
EBNF.822-address is parsed as 822.addr-spec use this as the
encoding of 822.mailbox. If EBNF.822-address is parsed as
822.route 822.addr-spec, then a 822.phrase taken from
822.local-part should be added.
3. If IPMS.ORDescriptor.telephone-number is present, this
should be placed in an 822.comment, with the string "Tel ".
The normal international form of number should be used. For
example:
(Tel +44-1-387-7050)
Kille [Page 49]