On Wed, May 13, 2015 at 7:00 AM, Beurer, Maria (Coriant - DE/Munich) <maria.beu...@coriant.com> wrote: > Hello, > We use openVSwitch in our commercial product and therefore need to know the > ECCN for it. > The ECCN is an international Export control and compliance number that is > necessary for EVERY Export. Most of the european countries specify their > goods according to the european commerce control list (EG dual-use list : > http://ec.europa.eu/trade/index_en.htm). > So for export of a commercial Software using openVSwitch ( or any other open > source or OEM Software), we need to document the libs, on one side to comply > with license obligations and on the other side the ECCNs for Export > restrictions. Please note, as the US regulations also care about re-export of > US items ( any stuff that contains US Content above a certain Limit), we need > to specify both; the EU-ECCN and the US-ECCN and hopefully the US license > exception that applies (e.g. TSU for open source). > > So please specify the ECCN for openVSwitch or answer the following questions: > - Country of origin ( where is openVSwitch Software mainly developed) > - is there US Content in there? ( e.g. other open source libs) > - Is the SW designed or modified to use cryptography performing any > cryptographic function other than authentication or digital signature? (y/n) > -if yes, > -- key length symetric > -- Bit length asymmetric
This is almost certainly something that you will need to do your own due diligence on rather than asking random people on a mailing list. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
