incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: 'Handling Crypto..' - River project
Date Wed, 24 Oct 2007 17:21:49 GMT
Keep in mind, "Sun" stuff wasn't necessarily handled under generally available
open source TSU (exception) classifications, but as commercial "product".  This
is, in part, why distributors may have issues using our exceptions and our
classifications (their export legal advisors know better).

For these questions, always kick them across to legal-discuss@a.o please :)


Jim Hurley wrote:
> We're (River incubator project) trying to comply with:
>     "Handling Cryptography within an ASF Release"
>     <>
> This process talks only about software that has been
> self classified as 5D002 (has strong crypto classification).
> Parts of the Sun Jini Technology Starter Kit (the base contribution
> for the River project) were classified as 5D992.b.1, which is
> a different classification.  From the ASF perspective, should
> we treat this (5D992) classification as effectively "no crypto"?
> Need some guidance and insight to help us understand
> what we need to do to comply.
> thanks -Jim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message