From: Gary Thomas <gary@mlbassoc.com>
To: RayGold <raygold@bcr-dc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos
Date: Wed, 30 Aug 2006 16:47:00 -0000 [thread overview]
Message-ID: <44F5C0FC.7030009@mlbassoc.com> (raw)
In-Reply-To: <44F5B4C9.8030909@bcr-dc.com>
RayGold wrote:
> Dear Sir/Madam:
>
> My name is Ray Gold from Berliner, Corcoran & Rowe, LLP, in Washington, DC.
>
> Do you know the U.S. export control classification (ECCN) of eCos? Do
> you know if a License Exception is available?
I am not a lawyer and this response should not in any way be taken
as a legal opinion.
As far as we know, there are no parts of eCos which are considered
sensitive or require any export license. Any code which can be used
with eCos, e.g. cryptographic code, is not part of eCos per se and
must be obtained from outside the U.S.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-08-30 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 15:56 RayGold
2006-08-30 16:47 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 8:17 [ECOS]ecos Shu Higashiyama
2008-09-02 16:07 [ECOS] eCos ltbeque
2003-09-13 7:14 [ECOS] ecos piyali probodh de
2003-09-13 15:27 ` Andrew Lunn
2003-05-14 5:19 [ECOS] eCos Narasimha
2003-05-14 7:10 ` Andrew Lunn
2002-08-02 1:34 Mikael Bokell (MIC)
2001-05-25 19:50 sophists
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F5C0FC.7030009@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=raygold@bcr-dc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).