Re: [Idr] Current affiliation of IDR WG chair

"Susan Hares" <> Fri, 07 June 2019 17:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C531512025B for <>; Fri, 7 Jun 2019 10:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id m5SWE4_3WyiX for <>; Fri, 7 Jun 2019 10:44:08 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BB79B12022E for <>; Fri, 7 Jun 2019 10:44:07 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: "'idr@ietf. org'" <>
Date: Fri, 07 Jun 2019 13:43:58 -0400
Message-ID: <04c501d51d58$96865050$c392f0f0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04C6_01D51D37.0F7636F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUdVomVdQxooVjDQyisJB4xwcSprQ==
Content-Language: en-us
X-Antivirus: AVG (VPS 190607-2, 06/07/2019), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: <>
Subject: Re: [Idr] Current affiliation of IDR WG chair
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 07 Jun 2019 17:44:23 -0000

IDR folks: 


The post regarding the affiliation of your idr WG chair was to keep all of us focused on the IDR technical discussions. 


Due to the fine work by lots of IDR members and BGP implementers, we have a full plate of draft ready for adoption and WG LC. John and I are working hard to pass all the drafts which have past WG LC and have implementations to the IESG.


My post was only tactical to relieve any nagging legal concerns.  


For those wanting additional information, this is the email to read.  

If not, I hope your delete key works.  (smile).  


I think the lesson for everyone is that "this too shall pass".  


Input from several of the IDR members is that they hope if moves on very quickly. 



Sue Hares 


Short version.



Alvaro mentioned the IETF Admin LLC Board of Directors chair message.  I've included it below. 


IEEE lawyers first halted review of Huawei documents (in accordance with very conservative reading of the US Department).  IEEE upon receiving an official ruling, pulled back that restriction. 



IETF information (contributed by Sandy Murphy) 


-----Original Message-----
From: IETF-Announce [] On Behalf Of IETF Administration LLC Board of Directors Chair
Sent: Thursday, May 30, 2019 12:30 PM
To: IETF Announcement List
Subject: Compliance with Recent U.S. Export Regulations


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.  



Jason Livingood

Chair, IETF LLC Board 








[4] See 15 CFR § 734.7(a)(4) and (a)(5) at


++++++++++ How to Contact the IETF LLC ++++++++++

Executive Director:  




++++++++++ General IETF LLC Board Background ++++++++++

About the IETF LLC:


IEEE Article Text (contributed by Sandy Murphy) 


Dear Sandra Murphy,  


Last week the U.S. government issued export controls on Huawei Technologies Ltd and 68 of its affiliated companies. In response, IEEE issued guidance on actions required to comply with these controls. We acted promptly because we wanted to protect our volunteers and members from potential legal risk that could have involved significant penalties. As a non-political, not-for-profit organization registered in New York, IEEE must comply with its legal obligations under the laws of the United States and other jurisdictions. We also engaged the U.S. government to seek clarification on the extent to which these export control restrictions were applicable to IEEE activities. 


I am pleased to report that this engagement was successful and we have revised our guidance to remove any restriction on the participation of the employees of these companies as editors or peer reviewers in the IEEE publication process. To reemphasize, all IEEE members can continue to participate in the open and public activities of the IEEE, including our scientific and technical publications. 


Many members expressed apprehension with respect to IEEE’s initial guidance and its impact on editors and peer reviewers based on their employer affiliation. I understand the concern this raised for many of you and appreciate the feedback that IEEE leaders and I received. 


As an international organization operating in 160 countries, IEEE supports the free and open exchange of scholarly and academic work and the global advancement of science and technology. IEEE is committed to enabling an environment of international cooperation and the sharing of our members’ wealth of knowledge to drive innovation. 


We appreciate the patience of our members and volunteers as we worked through a legally complex situation. If you have any comments, questions, or concerns, please contact me at 


For more information, please visit 


Thank you for supporting IEEE in our mission to advance technology for humanity. 


José M. F. Moura 

2019 IEEE President and CEO