Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watrose.UUCP
Path: utzoo!watmath!watnot!watrose!mdapoz
From: mdapoz@watrose.UUCP (Mark Dapoz)
Newsgroups: sci.crypt,net.sources.d,misc.legal
Subject: Re: Re: There are basically no export controls on public domain information.
Message-ID: 
Date: Sat, 25-Oct-86 23:01:57 EST
Article-I.D.: watrose.8221
Posted: Sat Oct 25 23:01:57 1986
Date-Received: Sun, 26-Oct-86 04:10:28 EST
References:   
Reply-To: mdapoz@watrose.UUCP (Mark Dapoz)
Organization: U of Waterloo, Ontario
Lines: 23
Keywords: Import Control?????
Xref: watmath sci.crypt:23 net.sources.d:615 misc.legal:118
Summary: 

In article  klr@hadron.UUCP (Kurt L. Reisler) writes:
>
>	You can go one step further.  Why export what you can import?
>	I recently received a copy of a MS/PC-DOS Public Key Encryption
>	system that was written in Canada!  We can't export the technology.
>	Why should we?  If the outside world can't buy it from us, they 
>	can just reinvent it and sell/give it to us.

This brings up a question I've been wondering about ever since this discussion
started up.  Everyone keeps talking about export controls on software
distributed over the net.  If someone over there (the US) decides that
you shouldn't post a program to net.sources, does that mean I have to
live by that decision here in Canada?  As far as I know of (and I may be
wrong), but there is no control over distrbution of a DES encryption program
here in Canada.  So what is there from stopping me from posting the program
so that my fellow *Canadian* programers can use my work.  You have to remember
that this net also covers Canada, which is another county with many 
different laws than the USA.  Just because my posting would spill over into
the US shouldn't stop me from posting the program.  Are there any laws for
IMPORT control over the net?  I sure hope not.

	Mark Dapoz
	mdapoz@watrose.UUCP