From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20242 invoked by alias); 9 Jan 2006 19:11:47 -0000 Received: (qmail 20232 invoked by uid 22791); 9 Jan 2006 19:11:46 -0000 X-Spam-Check-By: sourceware.org Received: from rt.gnu.org (HELO rt.gnu.org) (199.232.76.167) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 09 Jan 2006 19:11:44 +0000 Received: from www-data by rt.gnu.org with local (Exim 4.34) id 1Ew2UT-0003HE-FE; Mon, 09 Jan 2006 14:15:37 -0500 Subject: RE: [gnu.org #265428] Export Compliance and Schedule B numbers From: "Rutherford, Helene via RT" Reply-To: info@fsf.org In-Reply-To: Message-ID: X-RT-Loop-Prevention: gnu.org RT-Ticket: gnu.org #265428 Managed-by: RT 3.0.11 (http://www.bestpractical.com/rt/) RT-Originator: helene.rutherford@eds.com Cc: gnu@gnu.org,overseers@gcc.gnu.org,steve@smc.vnet.net MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Mon, 09 Jan 2006 19:11:00 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00035.txt.bz2 If the items on your website are direct product from Red Hat or CodeSourcery, it's your responsibility to make sure that the ECCN is available on these products you have on your website where it is being exported from. Your website is providing the code to be downloaded by anyone, anywhere(do you control who and to where the downloads are executed by?), It's your responsibility to make sure what's on your website is exportable and has an ECCN assigned and available. http://www.bis.doc.gov/licensing/ExporterResponsibility.htm That is why I'm asking you for the ECCN number because our company downloaded it from your site and for us to export it, the ECCN from the source is required. Helene >ITO Export Compliance Coordinator 248-754-7635 -----Original Message----- From: Per Bothner [mailto:per@bothner.com] Sent: Monday, January 09, 2006 1:33 PM To: Rutherford, Helene Cc: info@fsf.org; gnu@gnu.org; overseers@gcc.gnu.org; steve@smc.vnet.net Subject: Re: [gnu.org #265428] Export Compliance and Schedule B numbers Rutherford, Helene wrote: > > http://www.bis.doc.gov/licensing/exportingbasics.htm So somebody would need to go through the "Commerce Control List" (available on http://www.access.gpo.gov/bis/ear/ear_data.html) looking for a 5-character code that applies to Gcc. I'm sure someone at Red Hat or CodeSourcery (say) has done this, or is willing to do it, if nothing else as part of a support contract. Somebody at the FSF may also have looked into these issues. This site: http://dev.sleepycat.com/resources/faq_search.html?product_id=1&action=p rint says "As an open source product, DB does not fall under standard export controls." The same would apply to Gcc. (The page notes that DB does optionally include cryptographic support - that is not an issue with Gcc.) -- --Per Bothner per@bothner.com http://per.bothner.com/