Hi Alain, Since our sw is Open Source with Apache License this is applied (source: http://www.apache.org/licenses/exports/):
The Apache Software Foundation (ASF) makes NO WARRANTY or representation that the information contained in the ASF Product Classification Matrix is accurate, current, or complete. It is your obligation as the exporter to comply with the current applicable requirements of United States export rules and regulations. Any use of such information by you is without recourse to the ASF and is at your own risk. The ASF is in no way responsible for any damages, whether direct, consequential, incidental, or otherwise, suffered by you as a result of using or relying upon such information for any purpose. Each ASF product is classified <http://www.bis.doc.gov/licensing/exportingbasics.htm> with an Export Control Classification Number (ECCN) if it is believed to correspond to an entry in the Commerce Control List (CCL) and subject to the EAR. All ASF software is published in a publicly available source code form. Since publicly available software is only subject to the EAR <http://www.access.gpo.gov/bis/ear/txt/734.txt> when it is classified as ECCN 5D002 or 5D992 <http://www.access.gpo.gov/bis/ear/txt/ccl5-pt2.txt> , all ASF software product versions that do not fit those two classifications are noted as ECCN "n/a" (not applicable) or not included in the matrix. Products classified as ECCN 5D002 <http://www.access.gpo.gov/bis/ear/txt/ccl5-pt2.txt> , are exported by the ASF under the TSU exception in EAR 740.13(e) <http://www.access.gpo.gov/bis/ear/txt/740.txt> , which applies to software containing or designed for use with encryption software that is publicly available as open source. Exception TSU further provides that " *Posting encryption source code and corresponding object code on the Internet (e.g., FTP or World Wide Web site) where it may be downloaded by anyone neither establishes "knowledge" of a prohibited export or reexport for purposes of this paragraph, nor triggers any "red flags" necessitating the affirmative duty to inquire[...]* " Note that exporters other than the ASF within the US may or may not be eligable for exception TSU, and it is each specific exporter's responsibility to understand and comply with all export regulations applicable within their jurisdiction. Lvc@ On 27 January 2015 at 12:51, Alain C <[email protected]> wrote: > Hello, > > In order to valid the deployment of the solution, I need the ECCN (Export > Control Classification Number). > Does somebody know it? > > Thanks > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
