Subject: Re: IPsec exportability
To: Jonathan Stone <jonathan@dsg.stanford.edu>
From: Michael C. Richardson <mcr@sandelman.ottawa.on.ca>
List: current-users
Date: 09/22/1998 15:22:09
>>>>> "Jonathan" == Jonathan Stone <jonathan@DSG.Stanford.EDU> writes:

    Jonathan> Perry,

    Jonathan> If we integrate IPsec into the NetBSD kernel in a US
    Jonathan> repository, doesn't that mean we won't be able to export the
    Jonathan> integrated kernel?

  Correct.

    Jonathan> That'd probably mean maintaining a non-IPsec kernel tree,
    Jonathan> either with IPsec add-ins in domestic/sys or two separate IP
    Jonathan> stacks (ugh).

  No. Just maintain all the crypto parts outside the of the US. Import only.
You can still edit all the policy code, since that is needed for AH, which
is exportable.

  I have disk space and bandwidth here in Canada, and there is supposed
to an immenent announcement from the other side of the pond soon.

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |         Firewalls, TCP/IP and Unix administration
 Personal: http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html
 Corporate: http://www.sandelman.ottawa.on.ca/SSW/
	ON HUMILITY: To err is human, to moo bovine.