RFC 1465 (rfc1465) - Page 2 of 31
Routing Coordination for X
Alternative Format: Original Text Document
RFC 1465 Routing Coordination for X.400 Services May 1993
but may also be used at a national level or even within an
organisation.
Many experts from IETF X.400-Operations Group and RARE Working Group
1 on Message Handling Systems have read drafts of this document and
contributed ideas and solutions. I would especially like to thank
Harald Alvestrand, Erik Huizer, Marko Kaittola, Allan Cargille and
Paul-Andre Pays.
This is the third version of a table format. The first one was in
use within COSINE-MHS for about two years. A second version with
major enhancements was then proposed which has been in use for the
past year. The third version will probably be the last one before it
will be possible to switch to dynamic, directory service based
routing.
2. Terminology
MHS community
One or more MHS domains form an MHS community. Mail exchange
between these MHS domains is defined by the coordination
procedures within this document. Examples of such communities are
the Global Open MHS service GO-MHS and the COSINE-MHS service.
MHS domain
One or more MHS subtrees form an MHS domain. This is a purely
administrative grouping of MHS subtrees. It is helpful, if
someone is responsible for several MHS subtrees, to refer to an
MHS domain instead of listing all the subtrees.
MHS subtree
An MHS subtree consists of the total of the mailboxes addressable
within a subtree of the X.400 OR address space.
Example: O=SWITCH; P=SWITCH; A=ARCOM; C=CH;
MHS domain of SWITCH in Switzerland, consisting of all
mailboxes with O=SWITCH; P=SWITCH; A=ARCOM; C=CH; in the OR
address.
RELAY-MTA
An X.400 MTA serving one or several MHS domains. Note that the
term WEP -Well Known Entry Point- has been used since the early
X.400ies (1987/88) until now, giving the wrong impression of a
Eppenberger