[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exporting an IPSec implementation

To: sommerfeld@apollo.hp.com
Subject: Re: Exporting an IPSec implementation
From: Phil Karn <karn@qualcomm.com>
Date: Thu, 25 Jul 1996 14:38:33 -0700 (PDT)
Cc: baldwin@rsa.com, ipsec@TIS.COM
In-Reply-To: <199607251653.MAA03817@thunk.orchard.medford.ma.us> (message from Bill Sommerfeld on Thu, 25 Jul 1996 12:53:00 -0400)
Sender: ipsec-approval@neptune.tis.com

>My experience with the export control people is that they don't like
>source exports at all (and they have difficulty understanding the
>concept of free software); they consider code which *calls* a
>cryptographic API (because it would necessarily have a (possibly
>trivial) key management component) to be the "ancillary equipment" (in
>the "cryptographic hardware and ancillary equipment") of the ITAR.

Exactly what I expected to hear. Which means the 40-bit rule isn't much
use to us, given the IETF tradition of releasing free reference source
implementations, is it?

Phil

References:

Re: Exporting an IPSec implementation

From: Bill Sommerfeld <sommerfeld@apollo.hp.com>

Prev by Date: Re: Exporting an IPSec implementation
Next by Date: Any key mgmt proto comparison info available?
Prev by thread: Re: Exporting an IPSec implementation
Next by thread: Re: Exporting an IPSec implementation
Index(es):
- Main
- Thread