On Oct 15, 3:08 pm, europe72 <[EMAIL PROTECTED]> wrote: > On Oct 15, 1:45 pm, "Susan Heath" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Is Rhino classified with an ECCN (Export Control Classification Number) > > for export? If not, would it be designated as EAR99? > > > Thanks in advance, > > > Susan > > What an interesting question...and I am now curious as well. > > First step here would be to find out whether or not anyone at the > Rhino project has ever assigned a schedule B number to the Rhino > codebase. If no one has done that, then of course I wouldn't expect > that an ECCN would have been assigned. I don't believe there is any > serious encryption anywhere in the codebase, so I wouldn't expect to > see a tight control, but I also wouldn't expect to see EAR99 (a lack > of control), but perhaps since the product is "generally available" it > has no controls and thus no ECCN? > > If no one at the Rhino project has this level of expertise I would be > happy to lend a helping hand to help classify for export. Just send me > an e-mail.
No, we don't have an ECCN. We don't have any encryption as part of Rhino, FWIW. --N _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
