Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ucbvax!nprdc.arpa!bierma
From: bierma@NPRDC.ARPA (Larry Bierma)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Re:  UUCP over a TAC?
Message-ID: <8511062134.AA15993@nprdc.arpa>
Date: Wed, 6-Nov-85 16:34:00 EST
Article-I.D.: nprdc.8511062134.AA15993
Posted: Wed Nov  6 16:34:00 1985
Date-Received: Thu, 7-Nov-85 06:19:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: tcp-ip@ucbvax.berkeley.edu

It looks like setting up a link with a uucp site in the DC area is the
best solution (Rick@seismo has already generously offered his site).
Thank you all for you responses. 

Ironically enough I'm putting the system in DC to eliminate some of
that "charater at a time" traffic.  The people there now currently
use a TAC to access the VAX(s) here.  But, the eliminated "character"
traffic is now replace by the need for "bulk data" traffic.  Which
it appears can't be done directly.

Is anybody working on a general solution to this problem?  I hope so,
since it's going to get worse.  For the Navy, OPNAVINST 2070.4 requires
use of the DDN as the primary data communications medium.  It seems
silly to permanantly attach a PC to an IMP just for mail and an
occaisonal file transfer.

Maybe something like a dialin UDP port.

--Larry		ARPA: bierma@nprdc.arpa
		UUCP: {decvax,ucbvax,ihnp4}!sdcsvax!sdcsla!nprdc!bierma
		PSTN: (619) 225-2161