Re: [Mtgvenue] If Muslims are blocked by the U.S., should the IETF respond?

Fred Baker <fredbaker.ietf@gmail.com> Fri, 27 January 2017 22:50 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01CF3129A67 for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 14:50:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 khdCFYtDC-hr for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 14:50:00 -0800 (PST)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2941129A55 for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 14:50:00 -0800 (PST)
Received: by mail-pf0-x233.google.com with SMTP id f144so76211819pfa.2 for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 14:50:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=H5yp6LoRF8yRelEDzAECOOC1vohK+VYmQfrIr6sXKF0=; b=uwNFrGXGYxEyb5sj7+Vvpc7gsFDi+m98GMcOjPHs1xfb2nLQ4IysOSwJQ0tBNSIFxF nMdfH51NN+UmKnwR7+f9R9bCbT1NtkXTxE8b5zUbwMUypsuKWP5Q3T9iU5kU8DhS5Q24 pjMYLwB61QTW95q50zgkdvn/Izo3vvkTyCvhCd55BekS8m/R4cGJhFuAKciKTf1Q/TEP tEQ5qJPQLAbvPqJByY+TYItOiedLRGKymRZOWz4z5WAiP9KafPnMMCA2e/4iA/qx+fPl DsUG/J6X0zyF16PorQ9GMrS5Zom1SCrQ3vZgMgYDIu1VZDza2KJMYrChlwl88BEjxgk1 C1Uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=H5yp6LoRF8yRelEDzAECOOC1vohK+VYmQfrIr6sXKF0=; b=kqW0JN6nOKHgvNgGcJXYzR8NBXxeW/9jWGOVrdgTAjBCQpJWyG8iEILjC8HQcp09kA z42lP2T0WMc6RI+5Pa6PcC9W5BPKPaEA7VhmR+5jTraxu5W6deuZQIXSpLp/xzvUt3aE Vm5RPFo1i4T7IbPelQqM6byJvO6D2viwOXnqm+fcKjq6UvLVbAOjZqsIjegZbJNH+jcK XMXa2Y+dCNgmw5nF5nNcv+Na/7im4YyaSJ8PoUR/r9T+GdqXDR2k6xj4NEr4XS1NY9hw 9oqk46kpBJpEXhAPFppOzwgllQJAFKNE1KSYdrRR0zxfnSoeC/56uvqZY62Fn+EyKR3B LDaQ==
X-Gm-Message-State: AIkVDXKOrP+RT2weOhvNTEeGo1CvT7nPix5H9/V6RmiqmgZM6mG8uKJXkgQ501NX0Br4iw==
X-Received: by 10.84.241.203 with SMTP id t11mr15832464plm.18.1485557400196; Fri, 27 Jan 2017 14:50:00 -0800 (PST)
Received: from ?IPv6:2600:8801:d004:600:8404:25ac:ff89:3b7? ([2600:8801:d004:600:8404:25ac:ff89:3b7]) by smtp.gmail.com with ESMTPSA id u75sm13736060pgc.31.2017.01.27.14.49.58 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Jan 2017 14:49:59 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Fri, 27 Jan 2017 14:49:58 -0800
References: <20170127194324.GB38766@mx2.yitter.info> <c65c5fb0-2dba-4132-47eb-8239291c6f7a@dcrocker.net>
To: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
In-Reply-To: <c65c5fb0-2dba-4132-47eb-8239291c6f7a@dcrocker.net>
Message-Id: <950D4E21-B938-4B0F-AC1F-A4D5CA868349@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/fTmpdsvH4ZOARpeQ-AeU2LSMyKI>
Subject: Re: [Mtgvenue] If Muslims are blocked by the U.S., should the IETF respond?
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2017 22:50:02 -0000

On Fri, Jan 27, 2017 at 02:29:01PM -0500, Dave Burstein wrote:
> Some might also think that we should move the July 2018 meeting from San
> Francisco to a location accessible to more of our members, perhaps to
> Mexico or Canada.

We have literally done that in the past, primarily because our Chinese colleagues have had issues with the US Embassy, getting visas. 

While the IETF doesn't have "membership" per se, I think an important part of Dave's comment is the impact on "members". To my knowledge, our muslim colleagues are far more interested in making the Internet work in their countries than in attacking the US (or anyone else). Our reasoning on moving away from US venues a decade ago had to do with people that wanted to actively participate, and who were interested in more wholesome activities.

In the particular case, I might suggest we find out what the issues are and how we are impacted before making changes; the important thing in this document isn't specific venues, but the process by which they are chosen. Whatever the rhetoric has been, I suspect that a ban against a religion will not stand, as it directly violates the US first amendment ("Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof..."). What could stand (and is largely in place today) is a ban on travel of people associated with organizations known to have issues with the US government or its citizens.