Re: [Mtgvenue] visa situation... worsens?

Vinayak Hegde <vinayakh@gmail.com> Wed, 22 March 2017 21:50 UTC

Return-Path: <vinayakh@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 BF98B1294F6 for <mtgvenue@ietfa.amsl.com>; Wed, 22 Mar 2017 14:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, 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 EIWqIO4nklQG for <mtgvenue@ietfa.amsl.com>; Wed, 22 Mar 2017 14:50:20 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 954A012751F for <mtgvenue@ietf.org>; Wed, 22 Mar 2017 14:50:20 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id r45so161996143qte.3 for <mtgvenue@ietf.org>; Wed, 22 Mar 2017 14:50:20 -0700 (PDT)
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=hbxtsL9sMgpgjQUk2u1zLW814gGqAnPNJ+fxPnwcxfA=; b=GWPqsGbc0N0c1FUbOSLHoZLh8eNvbPVkTwIUQWNg7yTc5EcMoyurPnYd41S+VZGVJv QfNUN10f4YV5p5ximpGjlKVtD0VMqfnrvY2N7DKoWCArF+dRFdrFvvMUDFtKvwr4Rdrs 6GZeVNJvr/fq11LGcK0i0xqCqIDHtzqN65vESHw+WYDBXiSjz0Crkmzo+NP/tNRXxiae OCuCzSlR7aceNzNateIkLHi8noeDaKuxJSd3ayMuM/2mFDR1eJ0mixjNxNidvg9arrkQ nEUiLkFnCryYifLvRXvVCvohXWYfY4kq66sZnNHW5PN1npW28kRAfBKzKcHbOkYcbQM6 g+jw==
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=hbxtsL9sMgpgjQUk2u1zLW814gGqAnPNJ+fxPnwcxfA=; b=YXsd49a8cD32e1JmNZecu1m4DhkSlIMIDIcOzFhpC3027uZHITbXsxylwOJgrgFLjg FtRGwecudX83qyHH81zc+AhPCaC393xGADyJ+elFwMTrFj+RJeM4Ai65IkGkO1r5V80a s7KaoPEK1Z1E5yztGkgGK2dJk653vTYjy42qQogeWqHArbRfQF+lltmJZYniWM88iYod tQjdcO7vJPitPHEpjdVkd8MXZX2pFNIvZXjg6yDtC4WOEuOFVORWhscJg04iRiCIN+WU M+T7pGyMIX5QJYoP3yqLrociMt/FAK649wdhFCKiBDZPd4YU/UJm+Y3Fy2Yd7saMjFfP SwKQ==
X-Gm-Message-State: AFeK/H3EuiSTWLF4CH1xDSLWBxfc8AD9Ad/Q3eN7qaoWErzfL0/ay60xpIboB9TviRfU4hLSk7+Ig4HuKvQ8Ww==
X-Received: by 10.237.57.169 with SMTP id m38mr44403534qte.196.1490219419614; Wed, 22 Mar 2017 14:50:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.50.228 with HTTP; Wed, 22 Mar 2017 14:50:19 -0700 (PDT)
In-Reply-To: <2805.1490212930@obiwan.sandelman.ca>
References: <2805.1490212930@obiwan.sandelman.ca>
From: Vinayak Hegde <vinayakh@gmail.com>
Date: Thu, 23 Mar 2017 03:20:19 +0530
Message-ID: <CAKe6YvNXAucSABZrc84SQEmhevcV3O5Ft3hxKcgg94rvt7kdTg@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: mtgvenue <mtgvenue@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/7eTR2-aZ514L6ced6fbxXvJpxUw>
Subject: Re: [Mtgvenue] visa situation... worsens?
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 22 Mar 2017 21:50:23 -0000

Then there is the no small matter of laptop/tablet ban on certain ME
Asian airlines
http://www.telegraph.co.uk/news/2017/03/21/exclusive-britain-poised-follow-us-ban-laptops-ipads-flights/

This is extremely inconvenient and dangerous for anyone who has
travelled a bit knows.
1. Stuff in check-baggage gets banged around and thrown around (seen
it myself multiple times) so electronics can get damaged.
2. Stuff in check-in baggage gets robbed. (Happened multiple times to
my friends)
3. If there is a fire in check-in baggage in the hold due to a
lithium-ion battery it can have worse implications than in carry-on.
4. Finally customs can scan/clone your data without intervention (so
there are privacy concerns here as well).

Also it bears repeating that much of Africa and Asia connects through
the middle-east for flights to Europe and US. With the US
administration being what it is (this trend is likely to get worse),
how much more needs to happen before the US is disqualified as a
location for IETF meetings.

Also looks likely that UK and Canada will follow this trend.

-- Vinayak

On Thu, Mar 23, 2017 at 1:32 AM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> https://www.theguardian.com/us-news/2017/mar/20/no-african-citizens-visas-california-annual-trade-summit
>
> An annual African trade summit in California had no African attendees this
> year after at least 60 people were denied visas, according to event leaders.
>
> ====
>
> Is it too late to cancel IETF 102 in SFO?  {I'm guessing so}
> What about IETF 111?  Was it a multi-year deal?
>
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue
>