Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses (RFC1838)
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 .
Network Working Group S. Kille
Request for Comments: 1838 ISODE Consortium
Category: Experimental August 1995
Use of the X.500 Directory to support mapping between X.400
and RFC 822 Addresses
Status of this Memo
This memo defines an Experimental Protocol for the Internet
community. This memo does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This document defines how to use directory to support the mapping
between X.400 O/R Addresses and mailboxes defined in RFC 1327 .
1. X.400/RFC 822 Mappings
RFC 1327 defines an algorithm for maintaining a global mapping
between X.400 and RFC 822 addresses directory . RFC 1327 also
defines a table based mechanism for maintaining this mapping. There
is substantial benefit to maintaining this mapping within the
directory. In particular, this will lead to an approach for managing
the mapping which is both distributed and scalable.
Mechanisms for representing O/R Address and Domain hierarchies within
the DIT are defined in [1, 5]. These techniques are used to define
two independent subtrees in the DIT, which contain the mapping
information. The benefits of this approach are:
1. The mapping information is kept in a clearly defined area which
can be widely replicated in an efficient manner. The tree is
constrained to hold only information needed to support the
mapping. This is important as gateways need good access to the
2. It facilitates migration from the currently deployed table-based
3. It handles the issues of "missing components" in a natural
An alternative approach which is not taken is to locate the
information in the routing subtrees. The benefits of this
o It is the "natural" location, and will also help to
ensure correct administrative authority for a mapping
o The tree will usually be accessed for routing, and so it
will be efficient for addresses which are being routed.
This is not done, as the benefits of the approach proposed
There are three mappings, which are represented by two subtrees
OU=X.400/RFC 822 Mapping, O=Internet
These subtree roots are of object class subtree, and use the
mechanism for representing subtrees defined i...