On Tuesday, 17 August 2021 14:55:13 PDT Tait wrote:
>
> I take the silence to mean nobody else knows or has looked into
> this either. A bunch of volunteers writing open-source software
> would have little reason to deal with export control
> regulations, so perhaps that not surprising. Please do not
> consider this any sort of remotely authoritative answer! I'm
> just an uninformed nobody eyeballing things. If you need an ECCN
> for whatever you're doing, then I believe you'll need to
> self-certify that gnuplot is EAR99.
My first take is doubt that any "exported item" is involved.
Who is exporting what from where to where?
If someone out there is shipping/exporting a product that
falls under the jurisdiction of the US Dept of Commerce and
incorporates gnuplot, then maybe they need an export code
for their product. But that's on them, not on us.
And it would be an export code for their product, not a
code for gnuplot, although the inclusion of gnuplot might
indicate that the export code would include a letter "D".
with the usual disclaimer that I am not a lawyer
and this is not legal advice,
Ethan
> "Balick, Rebekah C [US] (ES)" <Reb...@ng...> said (on 2021/08/02):
> > Hello,
> >
> > I would like to request the ECCN (Export Control Classification Number) for GNUplot 5.0. It should be a 5 or 6 digit code of numbers and letters such as EAR99 or 5D002. I need this in order to maintain the software downloaded. Thank you!
|
