MHS use of the X.500 Directory to support MHS Routing
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 73
- Abstract
- 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. This is done repeatedly until the message can be directly delivered to the recipient UA. This memo defines an Experimental Protocol for the Internet community.
- Publication Date
- 1995-06-01
- Status Note
- Experimental
- DOI
10.17487/RFC1801- Link
- https://doi.org/10.17487/RFC1801
- Author(s)
- Steve Kille
- Keyword(s)
- Routing, Mail, Email, Message, X.400
Latest version of IETF RFC 1801
Document Versions — IETF RFC 1801
-
▶ IETF RFC 1801 (1995-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- ISBN.0890065640 — 10 EXTERNAL
- Lauder, P., Kummerfeld, R., and A. Fekete. Hierarchical network routing. In Tricomm 91, 1991. EXTERNAL
- Kille, S., "Representing tables and subtrees in the X.500 directory", Work in Progress, September 1994. EXTERNAL
- Kille, S., "Representing the O/R Address hierarchy in the X.500 directory information tree", Work in Progress, September 1994. EXTERNAL
- S.E. Kille. MHS use of directory service for routing. In IFIP 6.5 Conference on Message Handling, Munich, pages 157--164. North Holland Publishing, April 1987. EXTERNAL
- A. Consael, M. Tschicholz, O. Wenzel, K. Bonacker, and M. Busch. DFN-Directory nutzung durch MHS, April 1990. GMD Report. EXTERNAL
- The Directory --- overview of concepts, models and services, 1993. CCITT X.500 Series Recommendations. EXTERNAL
- Kille, S., Mhs use of X.500 directory to support mhs content conversion, Work in Progress, July 1993. EXTERNAL
- Zen and the ART of navigating through the dark and murky regions of the message transfer system: Working document on MTS routing, September 1991. ISO SC 18 SWG Messaging. EXTERNAL
- K.E. Jordan. Using X.500 directory services in support of X.400 routing and address mapping, November 1991. Private Note. EXTERNAL
- J.N. Chiappa. A new IP routing and addressing architecture, 1991. EXTERNAL
- S.E. Kille. Topology and routing for MHS. COSINE Specification Phase 7.7, RARE, 1988. EXTERNAL
- P. Dick-Lauder, R.J. Kummerfeld, and K.R. Elz. ACSNet - the Australian alternative to UUCP. In EUUG Conference, Paris, pages 60--69, April 1985. EXTERNAL
- IETF RFC 822 [Superseded*]
- IETF RFC 1277 [Active*]
- IETF RFC 1465 [Active*]
- IETF RFC 1485 [Superseded*]
- T-REC-X.400.1988 — CCITT/ISO88a EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1801.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1801, MHS use of the X.500 Directory to support MHS Routing. Available at https://doi.org/10.17487/RFC1801
Snippet:
IETF RFC 1801, MHS use of the X.500 Directory to support MHS Routing. Available at https://doi.org/10.17487/RFC1801
HTML (ISO 690 compliant)
Preview:
IETF RFC 1801, MHS use of the X.500 Directory to support MHS Routing. Available at https://doi.org/10.17487/RFC1801
Snippet:
<span class="citation"><cite>IETF RFC 1801</cite>, MHS use of the X.500 Directory to support MHS Routing. Available at <a href="https://doi.org/10.17487/RFC1801" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1801</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1801, MHS use of the X.500 Directory to support MHS Routing
doi: 10.17487/RFC1801
url: https://doi.org/10.17487/RFC1801
doi: 10.17487/RFC1801
url: https://doi.org/10.17487/RFC1801
Snippet:
<li> <cite id="bib-rfc1801">IETF RFC 1801</cite>, MHS use of the X.500 Directory to support MHS Routing <span class="doi">10.17487/RFC1801</span> </li>
Referenced By
- IETF RFC 1836 [Superseded*]
- IETF RFC 1837 [Superseded*]
- IETF RFC 1838 [Superseded*]
- IETF RFC 2164 [Active*]