Re: Compliance with Recent U.S. Export Regulations

Toerless Eckert <tte@cs.fau.de> Wed, 19 June 2019 18:46 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD1812096B; Wed, 19 Jun 2019 11:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYVzWg6hiFzc; Wed, 19 Jun 2019 11:46:48 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F3461209A4; Wed, 19 Jun 2019 11:46:46 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2819354890B; Wed, 19 Jun 2019 20:46:40 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 1818E440041; Wed, 19 Jun 2019 20:46:40 +0200 (CEST)
Date: Wed, 19 Jun 2019 20:46:40 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: ietf@ietf.org, iesg@ietf.org, LLC-Board-Chair@ietf.org
Subject: Re: Compliance with Recent U.S. Export Regulations
Message-ID: <20190619184639.2emoyea32dn7ijaz@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="q2xunskjx62uva33"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3JGKPFtyuCBvPF5UkPiD-UcEBd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2019 18:47:00 -0000

Jason, *:

Attached an IMHO interesting data point from other SDOs.

Can i assume that the IETF is happy with the current BIS
regulations and is not planning to voice any public opinion or
suggestions about the regulation given how the IETF lawyers have 
come to the conclusion that there is no impediment to IETF operations
(due to the open nature of our processes and work result) ?

Cheers
    Toerless

In-Reply-To: <155923377790.22145.17777792239713733657.idtracker@ietfa.amsl.com>

On Thu, May 30, 2019 at 09:29:37AM -0700, IETF Administration LLC Board of Directors Chair wrote:
> The IETF LLC is based in the United States and as such must comply with U.S. law, as well as the laws of other countries as applicable. The U.S. Department of Commerce???s Bureau of Industry and Security (BIS) recently announced a rule that placed Huawei and certain Huawei affiliates on the ???Entity List??? -- a list of companies that are subject to special licensing requirements under the U.S. Export Administration Regulations (EAR).[1] Subsequently, on May 20, 2019, the BIS issued a ???Temporary General License,??? adjusting some of these requirements for a period of 90 days.[2] The rules issued on May 20th specifically cite 5G-related standardization work in the IETF as an area subject to the new temporary license.[3]
> 
> The EAR generally do not apply to information that is published or that is submitted in connection with a process that is intended to result in open publications or presentations.[4] Given the public nature of IETF, IRTF, and IAB activities and the fact that our output is freely published online, the EAR are thus largely inapplicable to our materials and activities. So, the addition of Huawei and Huawei affiliates to the Entity List -- an action which affects only materials that would otherwise be governed by the EAR -- has little impact on the IETF.  
> 
> After consultation with legal counsel, we have concluded that, given current circumstances, we see no need to change our existing practices. We will continue to monitor the situation carefully, and will work with counsel and the IETF leadership teams to address any ???corner cases??? that may emerge and raise unique concerns. For IETF contributors that believe they may be affected, we recommend you consult your own legal counsel.  
> 
> Regards, 
> Jason Livingood
> Chair, IETF LLC Board
> LLC-Board-Chair@ietf.org 
> 
> [1] https://www.federalregister.gov/documents/2019/05/21/2019-10616/addition-of-entities-to-the-entity-list
> 
> [2] https://www.commerce.gov/news/press-releases/2019/05/department-commerce-issues-limited-exemptions-huawei-products
> 
> [3] https://www.bis.doc.gov/index.php/documents/regulations-docs/2396-temporary-general-license-rule/file
> 
> [4] See 15 CFR ยง 734.7(a)(4) and (a)(5) at https://www.law.cornell.edu/cfr/text/15/734.7
> 
> ++++++++++ How to Contact the IETF LLC ++++++++++
> Executive Director: Exec-Director@ietf.org  
> Sponsorship: sponsorship@ietf.org 
> Board: LLC-Board@ietf.org 
> 
> ++++++++++ General IETF LLC Board Background ++++++++++
> About the IETF LLC: https://www.ietf.org/about/administration/