RFC 1801: MHS use of the X.500 Directory to support MHS Routing

The key problem in routing is to map from an O/R Address onto an MTA (next hop). This shall be an MTA which in some sense is "nearer" to the destination UA.…

Read RFC 1801 on the RFC Editor

Outgoing relationships (5 related RFCs)

Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 1006: ISO Transport Service on top of the TCP Version: 3
Informative reference — RFC 1277: Encoding Network Addresses to Support Operation over Non-OSI Lower Layers
Informative reference — RFC 1465: Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing
Informative reference — RFC 1485: A String Representation of Distinguished Names (OSI-DS 23 (v5))

Incoming relationships (5 related RFCs)

Informatively referenced by — RFC 1836: Representing the O/R Address hierarchy in the X.500 Directory Information Tree
Informatively referenced by — RFC 1837: Representing Tables and Subtrees in the X.500 Directory
Informatively referenced by — RFC 2293: Representing Tables and Subtrees in the X.500 Directory
Informatively referenced by — RFC 1802: Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing
Informatively referenced by — RFC 1838: Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses