Mapping between X.400(1988) / ISO 10021 and RFC 822
Voir toute la rfc dans une seule page
Page : 75 / 92
Télécharger le PDF
Auteur(s) : S.E. Kille
RFC 1138 Mapping X.400(88) and 822 December 1989
For each element of MTS.ReportDeliveryEnvelope.per-recipient-fields,
a value of EBNF.dr-recipient, and an EBNF.drc-field (Recipient-Info)
should be generated. The components are mapped as follows.
Used to generate the first EBNF.mailbox and EBNF.std-or in
EBNF.recipient-info. Both RFC 822 and X.400 forms are
given, as there may be a problem in the mapping tables. It
also generates the EBNF.mailbox in EBNF.dr-recip-success or
If it is MTS.Report.delivery, then set EBNF.dr-recipient to
EBNF.dr-recip-success, and similarly set EBNF.report-type,
filling in EBNF.drc-success. If it is a failure, set
EBNF.dr-recipient to EBNF.dr-recip-failure, making a human
interpretation of the reason and diagnostic codes, and
including any supplementary information. EBNF.drc-failure
should be filled in systematically.
Set EBNF.drc-field ("converted eits")
Set the second ("originally intended recipient") mailbox
std-or in EBNF.drc-field.
Set EBNF.drc-field ("supplementary info"), and include this
information in EBNF.dr-recip-failure.
Set EBNF.drc-field ("redirection history")
Set ENBF.drc-field ("physical forwarding address")
Any unknown extensions should be discarded, irrespective of
Kille [Page 75]