Browse Prior Art Database

Network mail path service (RFC0915)

IP.com Disclosure Number: IPCOM000004326D
Original Publication Date: 1984-Dec-01
Included in the Prior Art Database: 2000-Oct-05
Document File: 10 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M.A. Elvy: AUTHOR [+2]

Abstract

The network mail path service fills the current need of people to determine mailbox addresses for hosts that are not part of the ARPA-Internet but can be reached by one or more relay hosts that have Unix To Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, etc.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group Marc A. Elvy

Request for Comments: 915 Harvard University

Rudy Nedved

Carnegie-Mellon University

December 1984

NETWORK MAIL PATH SERVICE

STATUS OF THIS MEMO

This RFC proposes a new service for the ARPA-Internet community and

requests discussion and suggestions for improvements. Distribution

of this memo is unlimited.

INTRODUCTION

The network mail path service fills the current need of people to

determine mailbox addresses for hosts that are not part of the

ARPA-Internet but can be reached by one or more relay hosts that have

Unix To Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail,

etc.

Anyone can use the service if they have TCP/TELNET to one of the

hosts with a mail path server.

DISCUSSION

Currently many hosts that are not connected to the ARPA-Internet

network can send mail to and receive mail from the ARPA-Internet

community. The ARPA-Internet community sends mail using mailbox

addresses of the form "user@host" or "local-part@domain" [1, 5]. In

an effort to provide service to hosts not connected directly to the

ARPA-Internet, mail maintainers have used the feature that the

"local-part" of the mailbox address is locally interpreted to imbed

specially encoded mail routing or relaying information. These

encoded mailbox addresses have a variety of forms and have become

common practice. For example:

demco%ucb-ean.cdn%ubc.csnet@CSNET-RELAY.ARPA

"Rudy.Nedved%CMCCTE@CARNEGIE.MAILNET"@MIT-MULTICS.ARPA

ihnp4!cmucsg!ern@UT-SALLY.ARPA

mss.dartmouth@CSNET-RELAY.ARPA

nedved%CMCCTF.BITNET@WISCVM.ARPA

It is important that people be able to communicate, but it is clear

from the rampant confusion and frustration that something must be

RFC 915 Month Year

Network Mail Path Service

provided to make it easier for people to address mail to

non-ARPA-Internet hosts. The result, for a variety of reasons, has

been the work and development of the Domain Name system and

facilities [2, 3, 7, 9], and it is expected to make mailbox addresses

be as simple as the current ARPA-Internet mailbox format (e.g.,

"user@domain").

How do people discover the special encoded addresses for

non-ARPA-Internet host mailboxes until the domain name system is

working and covering the majority of hosts in the mail world? ...