Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!decuac!avolio
From: avolio@decuac.UUCP (Frederick M. Avolio)
Newsgroups: net.mail.headers
Subject: Re: Non-domain host names in mail
Message-ID: <856@decuac.UUCP>
Date: Wed, 12-Mar-86 20:08:58 EST
Article-I.D.: decuac.856
Posted: Wed Mar 12 20:08:58 1986
Date-Received: Fri, 14-Mar-86 06:51:06 EST
References: <1355@brl-smoke.ARPA> <790@im4u.UUCP> <1611@brl-smoke.ARPA>
Organization: ULTRIX Applications Center, MD
Lines: 23
Summary: Non-Arpa domain names

In article <1611@brl-smoke.ARPA>, wmartin@brl-smoke.ARPA (Will Martin ) writes:
> In article <790@im4u.UUCP> jsq@im4u.UUCP (John Quarterman) writes:
> >Many people from IBM ... hand out business cards with USER@IBM.ARPA on them.
> For what it is worth, is not this business usage of the ARPANET in direct
> contradiction to the DDN guidelines for proper usage of the DDN network?

Okay.  What about domain-style addresses that look like ARPA addresses
but may never touch the Arpanet?  Is there a problem?  Because, for
example, user@decwrl.DEC.COM would go via the ARPANET from an ARPANET
host, but would go via DEC's internal network from decuac.  And even
though we are not an ARPANET host, avolio@decuac.DEC.COM will get to
me.  And it may go via UUCP or ARPA or any number of other ways.  And
user@host.ATT.COM won't touch the arpanet from here as neither will
user@host.UMD.EDU.  What I am getting at is, with the implementation
of domains across networks, including optional usage on the 'UUCP
network,' the transport mechanism will not be indicated, so those IBM
business cards could say "user@ibm.com" and, unless one knew the
communication channels, no one should object to the use.  Because,
user@host.SUB2.SUB1.TOPDOMAIN may or may not cross the DDN network.

-- 
Fred @ DEC Ultrix Applications Center
UUCP: {decvax,seismo,cbosgd}!decuac!avolio       INET: avolio@decuac.DEC.COM