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

Jari Arkko <jari.arkko@piuha.net> Mon, 30 January 2017 19:39 UTC

Return-Path: <jari.arkko@piuha.net>
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 9B263129AEB for <ietf@ietfa.amsl.com>; Mon, 30 Jan 2017 11:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] 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 ysasgE_PK2ZG for <ietf@ietfa.amsl.com>; Mon, 30 Jan 2017 11:39:40 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C7013129AF1 for <ietf@ietf.org>; Mon, 30 Jan 2017 11:39:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5583C2D298 for <ietf@ietf.org>; Mon, 30 Jan 2017 21:39:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oslkjnnz_-dy for <ietf@ietf.org>; Mon, 30 Jan 2017 21:39:28 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C0A6A2CC9B for <ietf@ietf.org>; Mon, 30 Jan 2017 21:39:28 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_ED9C24F2-6326-40E3-AF0D-BE4C1501ED94"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: If Muslims are blocked by the U.S., should the IETF respond?
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <AB7E9EDD-C313-4821-8BEC-D0AF57D80DA2@nohats.ca>
Date: Mon, 30 Jan 2017 21:39:31 +0200
Message-Id: <2D08A4C9-969C-4EFD-8782-84728C458EA3@piuha.net>
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <20170130183846.21994.qmail@server322.com> <AB7E9EDD-C313-4821-8BEC-D0AF57D80DA2@nohats.ca>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U_BvZuBztPBKJIEMvuro7UpDwfg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 30 Jan 2017 19:39:48 -0000

I wanted to update people a bit on effects and numbers.

Adam had given earlier in this thread a list of affected
people from past meetings. I run my own script on the
attendee data though, and (I think) took into account
who was actually on site. Out of the seven countries
on the list, we’ve not had a single attendee on site from
the beginning of the full records at IETF #80.

Obviously, that doesn’t make it right. Also,
the registration data is still based on the country or
region that people given when they register. And
you can only enter one value.

I’m aware of at least two people (Kaveh and Naeem)
who have dual citizenships for instance, and they are
sadly affected. There’s likely some more. If you are
affected and planning to attend future IETF meetings,
drop me an e-mail.

Jari