Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umd5.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!cvl!umd5!zben
From: zben@umd5.UUCP
Newsgroups: net.mail
Subject: Re: name change
Message-ID: <353@umd5.UUCP>
Date: Sat, 2-Mar-85 00:24:53 EST
Article-I.D.: umd5.353
Posted: Sat Mar  2 00:24:53 1985
Date-Received: Mon, 4-Mar-85 07:55:40 EST
References: <484@digi-g.UUCP> <405@lsuc.UUCP> <597@plus5.UUCP> <603@plus5.UUCP> <604@plus5.UUCP> <890@cbosgd.UUCP> <2180@vax4.fluke.UUCP>
Reply-To: zben@umd5.UUCP (Ben Cranston)
Organization: U of Md, CSC, College Park, Md
Lines: 19
Summary: Break site names loose from transport mechanisms 

I decided to break site names loose entirely from transport mechanisms.
Perhaps engendered by the unfortunate fact I need to transfer mail between
UMD2.ARPA and UMDA.ARPA by BitNet/RSCS rather than InterNet/SMTP, but there
you are.  DON'T ask why...

In any case break address parsing loose from transfer channel selection.
You can consider UMDC!ZBEN and ZBEN@UMDC to be identical addresses, they
specify a host and a user.  Even with forwarding, the two addresses:

     MARYLAND!UMD2!UMDC!ZBEN
and
     @MARYLAND,@UMD2:ZBEN@UMDC

have the same SEMANTICS.  Now, make your transport channel a property of
UMDC rather than anything from the SYNTAX format.  In this case my channel
to UMDC is *neither* Internet *nor* UUCP - its BitNet.

-- 
Ben Cranston        ...seismo!umcp-cs!cvl!umd5!zben    zben@umd2.ARPA