You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
We use this library in our commercial product and therefore need to know the ECCN for it.
ECCN is an international Export control and compliance number that is necessary for EVERY Export.
So for export of a commercial Software using this library ( 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 or answer the following questions:
Country of origin ( where is this 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
Thanks and kind regards
Rachna Sharma
The text was updated successfully, but these errors were encountered:
Hello,
We use this library in our commercial product and therefore need to know the ECCN for it.
ECCN is an international Export control and compliance number that is necessary for EVERY Export.
So for export of a commercial Software using this library ( 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 or answer the following questions:
Country of origin ( where is this 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
Thanks and kind regards
Rachna Sharma
The text was updated successfully, but these errors were encountered: