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

Naeem Khademi <naeem.khademi@gmail.com> Tue, 31 January 2017 08:35 UTC

Return-Path: <naeem.khademi@gmail.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 CED33126FDC for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 00:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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 SPdhpNORX-jQ for <ietf@ietfa.amsl.com>; Tue, 31 Jan 2017 00:35:07 -0800 (PST)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 1A4E0120726 for <ietf@ietf.org>; Tue, 31 Jan 2017 00:35:07 -0800 (PST)
Received: by mail-it0-x231.google.com with SMTP id c7so211409178itd.1 for <ietf@ietf.org>; Tue, 31 Jan 2017 00:35:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7pfqajDF9iRHxIUcpK4In1ooPeBs5jAeofX8zqFZSzI=; b=Z9AvzUlCyH9ar2rxoxW8ynhdS5ti5SAXV3mtbfJw6Rtz+vQC5yS5E/5dv+8lOYqYYj enN2AeZc/l++ZZ3/lX0qy6/Z3WcgBckr9Mipuw3NSDKaBW54RbxKXEi1bXKK2C3nrU9W lJkUeOZ73IOtttwP/3gvdwi32NYQLGRN4mkVMBQMlWNJAyHFYb4xQJnSE0ZQuJG5SiXi +cL8Js6mxmjwP6RRtOoSYorIoMiKD+toLGxZPNPNr9KscT4IV+uBQh40GURLshAd1qlc XvBOf7D5duHzrMlbxiO+vpjSYwKfFh/vnIQBdSlGeOrcndEiXs56F0YGEPCQR5JK4QDt DN/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7pfqajDF9iRHxIUcpK4In1ooPeBs5jAeofX8zqFZSzI=; b=nNC4/gEFVadQ7BpmdpCaeg/AolLiyP8EpuRY0JyRKkEE8JYtL6rEtxXv1v5eJfdjDV VtEApwGwr1WO6dxYyZKNnnS3h2bfhSznneYZjSOHkKK/xqr91LIH9bYxZteL1BYV4kJV p/k8tGPoM6YUzlcqiYA4Y6Fpqk39dIzyjFyzc0uSGahw10Q94h1hGPukKKDwllmV8nrM KC98fW5tSYevO8KAfX1iffpdnDJ6DNQLUpRZYYaH5/d4+zKrH1XXiA2UrjaL8Zrm4WRO JxnczP5rCXt2CapaHEe9CIris26sPwy4maw1zlsWyK2d8epjrbDJQSALU5PIDMVNlUAY 9MBA==
X-Gm-Message-State: AIkVDXJw9Qt5RyWyfewnc8bUIklGUUeh8SXYpS/ijF4V04BuvYRtJWaR/cw9Cjj2Dof4o5PrqcZzDmuc92mfbQ==
X-Received: by 10.36.22.12 with SMTP id a12mr18603108ita.51.1485851706410; Tue, 31 Jan 2017 00:35:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.178.210 with HTTP; Tue, 31 Jan 2017 00:35:05 -0800 (PST)
In-Reply-To: <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> <2D08A4C9-969C-4EFD-8782-84728C458EA3@piuha.net>
From: Naeem Khademi <naeem.khademi@gmail.com>
Date: Tue, 31 Jan 2017 09:35:05 +0100
Message-ID: <CAEjQQ5XrbyxryZK8veNcY7+Y9qFXJyq4dc208gctOgxS3j2aDw@mail.gmail.com>
Subject: Re: If Muslims are blocked by the U.S., should the IETF respond?
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11451b2c26506305475fcf7d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cljhx84WZWabX2Ju85TPuYs25MQ>
Cc: IETF <ietf@ietf.org>
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: Tue, 31 Jan 2017 08:35:09 -0000

Hi Jari

inline:

On Mon, Jan 30, 2017 at 8:39 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> 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.
>

Just a clarification: some affected folks may not appear on such data as
is, since the IETF registration form asks for "country of residence" and
has only one field as "country of citizenship"; most people with dual
citizenship would have entered the country of citizenship that they thought
would have made it easier to get visa based on (since it's noted in the
IETF invitation letter for visa application) or even be exempted from visa.
The second nationality would have only appeared on the visa application
form used at the embassy and not in the IETF data.


>
> 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
>
>
Cheers,
Naeem