Re: Debian Linux ECCN-Codes?
Hi Markus,
let me translate it from German as both lists are English ones.
(debian-www is maybe not the best list but if there exists such a number
it should be mentioned in the website where I didn't found it. You could
try debian-legal@... instead.)
<translation>
We use on one of our VoIP GSM gateways Debian/GNU Linux.
For export issues according to US law we require a so called ECCN code
for our project.
The ECCN determines by the ECCN codes of the used sub projects.
Is there a ECCN code for Debian/GNU Linux?
</translation>
PS: After some searching I found
http://www.mail-archive.com/debian-legal%40lists.debian.org/msg37336.html
which seems not to answer it (didn't read it carefully).
On Mon, Aug 27, 2007 at 02:47:15PM +0200, Diehl Markus wrote:
> wir verwenden auf einem unserer VoIP-GSM-Gateways ein Debian Linux System.
>
> Für die Export-Abwicklung nach US-Vorschriften benötigen wir jetzt einen sog.
> ECCN-Code für unser Produkt.
>
> Bei der Bestimmung der Nummer kommt es auf die evtl. vorhandenen ECCN-Codes
> der in unserem Produkt verwendeten Komponenten an.
>
> Gibt es für die Debian Linux Systeme einen ECCN-Code?
>
> Freundliche Grüße
> Markus Diehl
>
>
> > -------------------------------------------------------------------------------------------------------------------
> > VIERLING Holding GmbH & Co. KG
> Dr. Markus Diehl, Director Marketing
> > Pretzfelder Str. 21, D-91320 Ebermannstadt, Germany
> Phone: +49 (0)9194 / 97-284, Fax: +49 (0)9194 / 97-105
> > E-Mail: markus.diehl@vierling.de, URL: www.vierling-group.com
> -------------------------------------------------------------------------------------------------------------------
> > Headquarter: Ebermannstadt, Bamberg commercial registry: HRA 4769
> > Managing Directors: Dipl.-Ing. Manfred Vierling, Dipl.-Ing. Werner Vierling
> > Limited Partner: VIERLING Holding Verwaltungs-GmbH,
> > Bamberg commercial registry: HRB 4250
> -------------------------------------------------------------------------------------------------------------------
>
Reply to: