Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!NIC.DDN.MIL!TCP-IP-RELAY
From: TCP-IP-RELAY@NIC.DDN.MIL
Newsgroups: comp.protocols.tcp-ip
Subject: (none)
Message-ID: <8911140038.AA08539@ucbvax.Berkeley.EDU>
Date: 14 Nov 89 00:38:13 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 140

tcp-ip-relay
F4.N494.Z5.FIDONET.ORG
TCP-IP-RES.RURES
.WSU.EDU
tcp-ip-user@CS
DUPHY4.DREXEL.EDU
tcp-ip-users
LBL.GOV
tcp-ip-users
BNLUX0.BNL.GOV
TCP-IP
CARLETON.BITNET
tcp-ip
CS.MCGILL.CA
TCP-IP
MSSTATE.EDU
TCP-IP
NET.NRL.NAVY.MIL
tcp-ip
NETLABS.COM
tcp-ip
RIACS.EDU
TCP-IP
SPAM.ISTC.SRI.COM
tcp-ip
SCCGATE.SCC.COM
tcp-ip
TWG.COM
tcp-ip
USAFA.AF.MIL
tcp-ip
USNA.USNA.NAVY.MIL
tcp-ip
UTDALVM1.UTDALLAS.EDU
tcp-ip
UV4.EGLIN.AF.MIL
TCP-IP
VAX01.AMS.COM
TCP-IP
VENERA.ISI.EDU
TCP-IP
XX.DREA.DND.CA
TCP-IP
mbunix.mitre.org
tcp-ips
PURDUE.EDU
tcp-ip-local
MDC.COM
tcp-ip-relay
XEROX.COM
tcp-ip^.x
INTERLAN.COM
tcp-sig
TRWIND.TRW.COM
tcp
saturn.acc.com
tcpip-col
OMNIGATE.CLARKSON.EDU
tcpip-local
ALDNCF.ALCOA.COM
tcpip
CAM.UNISYS.COM
tcpip
SED.CEEE.NIST.GOV
tcpip
SIMPACT.COM
tcpip
CIM-VAX.HONEYWELL.COM
tcpip
isdres.isd.usgs.gov
tcpip
LOGICON.ARPA
tcpip
muvms1.bitnet
tcpip
anes.ucla.edu
tcp-ipg
ncs.dnd.ca
tcpipinfo
MSR.EPM.ORNL.GOV
tcpnews
WLV.IMSD.CONTEL.COM
teecp-ip
HAC2ARPA.HAC.COM
thomson%aries
DTRC.ARPA
tinker
CTS.SRI.COM
tony
FORALIE.ICS.HAWAII.EDU
torben
USC-SCE.USC.EDU
tsudik
CSAM.LBL.GOV
van
GARGOYLE.UCHICAGO.EDU
vijit!tcplist
DUCVAX.AUBURN.EDU
warlick
CSLI.STANFORD.EDU
whp4
NARDACVA.ARPA
yx0quinn

Received: from CORNELLC.cit.cornell.edu by NIC.DDN.MIL with TCP; Mon, 13 Nov 89 10:14:45 PST
Received: from CORNELLC.BITNET by CORNELLC.cit.cornell.edu (IBM VM SMTP R1.2.1MX) with BSMTP id 6258; Mon, 13 Nov 89 13:07:44 EST
Received: by CORNELLC (Mailer R2.04) id 7315; Mon, 13 Nov 89 13:07:43 EST
Date:         Mon, 13 Nov 89 12:21:38 EST
From:         Mark Bodenstein <MAB@CORNELLC.cit.cornell.edu>
Subject:      Re:  MXing the world (was RE:  New Host-Requirement RFCs)
To:           cs.utexas.edu!usc!csun!mx!cbcscmrs@tut.cis.ohio-state.edu
cc:           TCP-IP@NIC.DDN.MIL
In-Reply-To:  Your message of 7 Nov 89 22:51:55 GMT

> ...
On 7 Nov 89 22:51:55 GMT you said:
>I have one simple question, why don't we (The Internet side) put an MX record
>into the root servers for the top-level domains .bitnet and maybe even .uucp?
> ...
>We can point them to cunyvm.cuny.edu or ucbvax.berkeley.edu or new.foo.bar.net
>or whatever the lastest host is.  ...

This doesn't work because there isn't a single gateway between the internet
and Bitnet - there are many - probably in the dozens at this time.  (This must
have been said earlier in this conversation?)

I think we're heading towards having a DNS-style-name and an MX record per
Bitnet site (more or less), with the MX record specifying (for the internet)
which gateway is the best to use - i.e. which is the "closest" on the Bitnet
side.

This optimizes things if we assume we want to maximize the amount of its
journey a mailfile takes on the Internet, and minimize the journey through
Bitnet.  This is at this time, in general, a Good Thing, since Internet
links tend to be faster/higher throughput than Bitnet links (which are,
generally speaking, 9600 baud bisync lines).  When/as/if this changes (and
it is changing) it becomes much more complicated to try to optimize things.

Mark Bodenstein   (mab@cornellc.cit.cornell.edu; 607-255-3747)
Cornell University