William Allen Simpson wrote:
> What I meant is, I'd like to contribute code to FreeSWAN, or OpenSSL,
> or whatever, but the inclusion of a single line of my code will make
> the entire thing subject to EAR regulation. Worse, a single line of
> code that "looks" like a line I published will subject the whole thing
> to regulation. Means we cannot publish _anything_ for fear of damaging
> the efforts of our freinds. Not good.
I guess much will still be said (and, changed) on this now and in the
foreseeable future. There is more context at www.bxa.doc.gov in
its encryption page, with information on current policy and practice,
as well as a separate page for viewing the Export Administration
Regulations (EAR).
But, besides William's comments, I believe that the main market
value being reduced by the regulation is interoperation (a
non-exportable product reduces interoperation and thus increases
production costs, reduces market, increases the number of versions
and thereby the occurrence of bugs, increases time to market, etc.).
So, how could we boost interoperation in the face of (possible)
regulation? I am working on a technical approach to this. Of
course, the political track may be pursued in different countries,
administrations and over time, but is essentially local and will
have different results for different countries. A technical track
could be globally effective and even help defuse the political
questions by denying the cause. Can we devise such
solutions?
Cheers,
Ed Gerck
