Obsolete
Status Update
Comments
wi...@google.com <wi...@google.com> #2
The ECCN is 5D002, and it is generally eligible for license exception TSU.
fu...@gmail.com <fu...@gmail.com> #3
The ECCN for SDK w/source and publicly available should be 5D002, and it should be eligible for License Exception TSU. See §740.13(e).
SDK w/o source, compiled from the 5D002 (TSU) source code and/or library and also publicly available, would be classified under 5D002 if subject to the EAR, but is not subject to the EAR.
See §734.2 (b)(9)(ii):
"Publicly available encryption software in object code that corresponds to encryption source code made eligible for License Exception TSU under section 740.13(e) is not subject to the EAR."
Also see Note to paragraph (e),§740.13:
"Publicly available encryption object code software classified under ECCN 5D002 is not subject to the EAR when the corresponding source code meets the criteria specified in this paragraph (e), see § 734.3(b)(3) of the EAR."
SDK w/o source, compiled from the 5D002 (TSU) source code and/or library and also publicly available, would be classified under 5D002 if subject to the EAR, but is not subject to the EAR.
See §734.2 (b)(9)(ii):
"Publicly available encryption software in object code that corresponds to encryption source code made eligible for License Exception TSU under section 740.13(e) is not subject to the EAR."
Also see Note to paragraph (e),§740.13:
"Publicly available encryption object code software classified under ECCN 5D002 is not subject to the EAR when the corresponding source code meets the criteria specified in this paragraph (e), see § 734.3(b)(3) of the EAR."
jo...@google.com <jo...@google.com>
sa...@google.com <sa...@google.com> #4
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
But at nowhere I can find this issue in website.
Please someone kindly inform me.
Best regards,
H.Shino