home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_j_p
/
draft-ietf-mhsds-routdirectory-06.txt
< prev
next >
Wrap
Text File
|
1995-06-10
|
2KB
|
64 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1801:
Title: MHS use of the X.500 Directory to support MHS
Routing
Author: S. Kille
Date: June 1995
Mailbox: S.Kille@ISODE.COM
Pages: 73
Characters: 156,462
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1801.txt
MHS Routing is the problem of controlling the path of a message as it
traverses one or more MTAs to reach its destination recipients.
Routing starts with a recipient O/R Address, and parameters associated
with the message to be routed. 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. There are a number of things which need to be considered
to determine this. This memo describes MHS Routing using X.500
Directory.
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 announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute