[IRTF-Announce] Fwd: Compliance with Recent U.S. Export Regulations

Colin Perkins <csp@csperkins.org> Thu, 30 May 2019 20:36 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: irtf-announce@ietfa.amsl.com
Delivered-To: irtf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47FCE120137 for <irtf-announce@ietfa.amsl.com>; Thu, 30 May 2019 13:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 CLGhQ2UVtIiU for <irtf-announce@ietfa.amsl.com>; Thu, 30 May 2019 13:36:39 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A86CF1200E3 for <irtf-announce@irtf.org>; Thu, 30 May 2019 13:36:39 -0700 (PDT)
Received: from [82.132.217.125] (port=5752 helo=[172.20.10.5]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1hWRmu-0007rn-TD for irtf-announce@irtf.org; Thu, 30 May 2019 21:36:38 +0100
From: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E54523BD-A272-4EAA-94D4-5A4F2089E03B"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <6B8C5566-BED4-49AA-B534-F7FD2789F2DF@csperkins.org>
References: <155923377790.22145.17777792239713733657.idtracker@ietfa.amsl.com>
To: irtf-announce@irtf.org
Date: Thu, 30 May 2019 21:36:26 +0100
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-announce/Z6Nf5KyyHKfNl6hqG_GKhZeLfjA>
Subject: [IRTF-Announce] Fwd: Compliance with Recent U.S. Export Regulations
X-BeenThere: irtf-announce@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF-Announce <irtf-announce.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-announce/>
List-Post: <mailto:irtf-announce@irtf.org>
List-Help: <mailto:irtf-announce-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2019 20:36:42 -0000

FYI.

> Begin forwarded message:
> 
> From: IETF Administration LLC Board of Directors Chair <llc-board-chair@ietf.org>
> Subject: Compliance with Recent U.S. Export Regulations
> Date: 30 May 2019 at 17:29:37 BST
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Reply-To: ietf@ietf.org
> 
> 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/