As far as I know, export control is to be required by the company
exporting the software. Your legal team should look at it, including
the fact that the software is open source, if you also publish all the
modifications made to it, it can simplify the process a lot, but YMMV.
Right now being based in China, I have no problem exporting it to
the USA, again check for your specific situation ;-P
Daniel
> _______________________________________________
On Tue, Nov 26, 2013 at 11:25:45AM +0530, Sunil P John wrote:
> Hi,
> I am using libxml2 library version 2.9.0.1 for xml parsing in our component
> and redistributing lixml2 binary along with our product. Now the legal team
> of our company asked me the following question
> 1. Is ECCN (Export control classification number) applicable to libxml2?
> 2. If yes, what is the ECCN for libxml2?
> 3. Also whats the classification source for libxml2?
>
> I tried searching in the archives and other forums, but couldn't get any
> pointers. Hope anyone can help me here.
>
> Regards
> Zunil
> xml mailing list, project page http://xmlsoft.org/
> xml gnome org
> https://mail.gnome.org/mailman/listinfo/xml
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard redhat com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/