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!info-law
From: monty@UAB.CSNET (Montgomery Bob)
Newsgroups: mod.legal
Subject: Boris
Message-ID: <8603041721.AA21534@ucbvax.berkeley.edu>
Date: Fri, 28-Feb-86 11:47:01 EST
Article-I.D.: ucbvax.8603041721.AA21534
Posted: Fri Feb 28 11:47:01 1986
Date-Received: Wed, 5-Mar-86 05:19:42 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: info-law@brl.arpa


   Possibly the people responsible for spawning MInet and MILnet from ARPAnet
would not turn a deaf ear to the issue of legal Soviet/Warsaw-pact use of 
technology covered by the Export-Technology Act. Although their focus in the
past has been widely publicized by movies like "War Games", their unawareness
or unresponsiveness to the current issue is only magnified by the lack of
legislation to deal with controlling the use of commercial computer systems
in the context of todays long-haul telecommunications capabilities.
   The authors of the Export Technology Act apparently did not forsee Russians 
utilizing the DNN and public domain software, or commercially available
US supercomputers or CAD facilities from remote sites within their country.
As of yet we have discovered that the Commerce Department cannot prevent this,
and we are waiting for a reply from the Director of the Office of Export 
Technology qualifying his departments capability to handle such a situation.
   If the FBI, Commerce Department, Export Technology Office, and NSA all 
indicate that they are unprepared to handle such a situation, then I think
that the appropriate thing to do is to forward discussion of this issue to the 
Congressmen or Senators responsible for introducing  the Export Technology
Act, notifying them of the impotence of their bill in a telecommunications
environment.