Re: Visas for IETF 103 in Thailand

Carsten Bormann <> Wed, 15 August 2018 08:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0938B130EFF; Wed, 15 Aug 2018 01:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PF5yXv_4YKla; Wed, 15 Aug 2018 01:04:06 -0700 (PDT)
Received: from ( [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4C988129619; Wed, 15 Aug 2018 01:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
Received: from ( [IPv6:2001:638:708:30c9::b]) by (8.14.5/8.14.5) with ESMTP id w7F83qNe010183; Wed, 15 Aug 2018 10:03:53 +0200 (CEST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 41r26J3kgBzDWys; Wed, 15 Aug 2018 10:03:52 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Visas for IETF 103 in Thailand
From: Carsten Bormann <>
In-Reply-To: <>
Date: Wed, 15 Aug 2018 10:03:51 +0200
Cc:, IETF Discussion <>
X-Mao-Original-Outgoing-Id: 556013030.127975-e56b89cfebd199a38b7ff4412b9a2e4e
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Andrew Sullivan <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Aug 2018 08:04:08 -0000

On Aug 14, 2018, at 21:47, Andrew Sullivan <> wrote:
> As near as I can tell, there is nothing we collectively can do about
> this: we each need to be aware of the immigration realities affecting
> us.  The IAD and Secretariat and all of IASA can do as much as it
> likes to try to get information it knows, but IASA cannot and should
> not offer legal advice to any of us.  We all must evaluate our
> respective situations and make the determination best in each case.

Hi Andrew,

while this probably faithfully mirrors what a lawyer would tell you, it is also terribly inefficient.

The organization behind the IETF can very well collect information about the situation for, say, citizens of the 10 leading regions that will originate participants.  I would expect my meeting fee dollars to already have paid for that, because the venue selection committee must already have looked at that.  So why withhold that information?

Yes, it would need to be qualified as “not legal advice”, “subject to change”, “void where prohibited”, etc.
It would help if it contains pointers to authoritative information I can look up myself.
And, ultimately, it is my decision (or that of my organization) how to handle this information, but the IETF could do most of the legwork here.  Regularly, as a routine component of venue selection and preparing for a meeting.

Grüße, Carsten