Re: IETF LLC & IETF Participation from USA-sanctioned countries

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 04 March 2021 19:57 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 DE4673A1566 for <ietf@ietfa.amsl.com>; Thu, 4 Mar 2021 11:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=fppHE/QL; dkim=pass (1024-bit key) header.d=yitter.info header.b=TCcZww6p
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 hZUh9QcH9IBq for <ietf@ietfa.amsl.com>; Thu, 4 Mar 2021 11:57:48 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E86AF3A1564 for <ietf@ietf.org>; Thu, 4 Mar 2021 11:57:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 659BFBD530 for <ietf@ietf.org>; Thu, 4 Mar 2021 19:57:46 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1614887866; bh=+Rc6NmQ5+vB9YNPW8ixYYoSHIpHOZ0lQOQ+LBXm0IDE=; h=Date:From:To:Subject:References:In-Reply-To:From; b=fppHE/QLu52CvSLTEBo00BXOKdJpv5HIXacdAF0jINdg/XsC6uQWhhPY8Elx58mlm CkGiunP/19hodMYnDUn8V3kj9sjb6wCNL6jIwqNkUdOqrdnT28QAX4a3mltfrggG25 GI7ir4qK5x5urVdgUdcVHJ3nSKvNbSgadRFOtKyY=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkPNFzbwI-OO for <ietf@ietf.org>; Thu, 4 Mar 2021 19:57:45 +0000 (UTC)
Date: Thu, 4 Mar 2021 14:57:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1614887865; bh=+Rc6NmQ5+vB9YNPW8ixYYoSHIpHOZ0lQOQ+LBXm0IDE=; h=Date:From:To:Subject:References:In-Reply-To:From; b=TCcZww6pizeynoqDCuCFvKF2u19CELtrGt8UJD4vsxRSk3DQXi9j6V2njMlOgyAOH bmfqNMpVBanzY9PSJcb2IWoOjdtQtDrVHJRlpb2vRIMw+OJpnX15aMLUlfATlOUxUb u2XTl8cyPIrGzoQyktXrCzP2bdwP0NYrklq7ZELc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF LLC & IETF Participation from USA-sanctioned countries
Message-ID: <20210304195744.jbgzpjlegbogmxu4@crankycanuck.ca>
Mail-Followup-To: ietf@ietf.org
References: <4619acc8-1ed4-52e8-849b-bfda9de61bb0@gont.com.ar> <20210303221433.ufsitioimata4dtg@crankycanuck.ca> <4739AA0B-95BA-48C8-A17D-730EAF547F55@gmail.com> <20210304155203.n5cfd3kmu2fpgdrt@crankycanuck.ca> <4FCD1F07-6DE9-402F-AFD3-A3C42F3D0ACF@cisco.com> <5a221b8f-73d8-037d-9b4f-f51a9c54e3bd@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5a221b8f-73d8-037d-9b4f-f51a9c54e3bd@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0AUunhTgv7Cbwu3uMuegytsSqzE>
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: Thu, 04 Mar 2021 19:57:50 -0000

Disclaimer: still employed, still speaking for me

On Thu, Mar 04, 2021 at 01:40:52PM -0500, Keith Moore wrote:
>
>Especially when we're just trying to get a sense of the spectrum of 
>barriers to participation, I don't think it's "off track" to consider 
>anything that impairs individuals' ability to participate.

In that case, there are multiple issues here.  Off the top of my head:

	• People from sanctioned countries under the laws of wherever the IETF is incorporated may face legal barriers to interactions with the corporate body of the IETF.

	• People from sanctioned countries under any law may face legal barriers in arranging support for or travel to their IETF activities.

	• People from sanctioned countries may have their network connectivity impaired in various ways.

	• People from sanctioned countries under any law may face barriers to arranging payments for any paid IETF activities due to the rules imposed by payment processors.  These may be beyond the control of the IETF and may not be in place or foreseeable at the time of the IETF's contract with the processor, so they may not be possible to fix.

I do think that it is useful to lay out issues in a way such that the things that are actually addressable get priority.  Geopolitical harmony does not seem to be the barrier to inclusion and diversity that the IETF needs to prioritize compared to some other things that are perhaps closer to home.

Hope that helps,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com