Re: [103all] Visas for IETF 103 in Thailand

Fred Baker <fredbaker.ietf@gmail.com> Wed, 15 August 2018 16:14 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: 103all@ietfa.amsl.com
Delivered-To: 103all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470BC130FFF; Wed, 15 Aug 2018 09:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6CBkPm_Yoo_g; Wed, 15 Aug 2018 09:14:52 -0700 (PDT)
Received: from mail-pl0-x235.google.com (mail-pl0-x235.google.com [IPv6:2607:f8b0:400e:c01::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 EB60B131004; Wed, 15 Aug 2018 09:14:51 -0700 (PDT)
Received: by mail-pl0-x235.google.com with SMTP id g1-v6so667382plo.2; Wed, 15 Aug 2018 09:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FrDgktNsh+DLNni0w+4/cBSwDPfJ2VKOs9qF7S7Y8rY=; b=HGMEtGn4fBE+C869n4wEw9/pPf5PUzavTvtn/70wy4uBZGWf5w4Fp0r+JRIEFwCD0i rS+AvJMwm4paUtPhiquNt8enXcnK26MuzrX5T+kcYrj6IG+JQgshZKHOsPVm8Qnm8oq0 wx+gPQWWGedIeh5A9ZfrkzD571UyKbzmlWc5HDB0vhm9B9o2AYDEwg4RIAMRE0MSLc3t drHI9iFleXMXAthnQHh82OtTseZZA13uYW0yhMphKOmqb0xSNd5O83GbdMaVSmvFbBlv u4mdjM19WMHTDvroFjjbpbSt+iCROaVVNVRh5bRxO5l8KUFfq4uEDVxMlXPqi/9/WTrK unfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FrDgktNsh+DLNni0w+4/cBSwDPfJ2VKOs9qF7S7Y8rY=; b=Y/qtEoaFdP2HwMy54GMxWXCO3X6YKsKf01kE4qKqyEWobiHrCjry9NbXzWirE/9zz3 4isVXNVTMmRxnzrW6fdQVsLiUl28SBdeBWUtbSYxClGYr9lfayxBpXLAPO+UHzGV2jjd qOUK/0/MOemDrftZKbONeBs1DtmGrsDcOom9ZQVifAXb0qMBOD29lB8n++d92aVcwOu6 RpWch8EXhb6NCg8PRvgZQqPrYIUICgLgeDDV1fHOVlxfRcUJK80FUjGWW1Miuh3bxHbc T/CT0seSBnNMGu9fhvBNpOaHE5A2u3/Z/B+8zRgJrx+Co3Gm+hjDybzVFFTjuhh4tH4G qUKg==
X-Gm-Message-State: AOUpUlGHWzqReKQOsG7YF+o2shaNzmhH3KyafcTYzE6O306DYk/n/4BH 9eaLGhFmahP3NRMemplI4v0=
X-Google-Smtp-Source: AA+uWPwYREy2cu2d2r/gXRZBMwSiau+yc/1l75wbmxXcM8PUBy+5yj04uahofx/OSC8dOV8TD3b27w==
X-Received: by 2002:a17:902:7b87:: with SMTP id w7-v6mr25343348pll.142.1534349691482; Wed, 15 Aug 2018 09:14:51 -0700 (PDT)
Received: from ?IPv6:2607:fb90:56b5:b8e7:6c5b:8809:a3d7:e4a2? ([2607:fb90:56b5:b8e7:6c5b:8809:a3d7:e4a2]) by smtp.gmail.com with ESMTPSA id 143-v6sm38361139pfy.156.2018.08.15.09.14.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Aug 2018 09:14:50 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-8E7B6536-1D3C-441D-9757-F515784A557E
Mime-Version: 1.0 (1.0)
From: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: iPhone Mail (16A5345f)
In-Reply-To: <C0533504-4EE0-44CB-AD42-7C5F1051AC2A@tzi.org>
Date: Wed, 15 Aug 2018 09:14:49 -0700
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, 103all@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <41103334-DDAD-451F-AED4-9D268D907372@gmail.com>
References: <153426794535.27168.17582506604424633822.idtracker@ietfa.amsl.com> <CAA=duU0ijWy8hxRdDE0arC1MhBZwSt=YQSkC-bfZX8ySH5BqSw@mail.gmail.com> <20180814194722.GA16126@mx4.yitter.info> <C0533504-4EE0-44CB-AD42-7C5F1051AC2A@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/103all/ASJuckWx6vphaY0YCrfUchgAEdQ>
Subject: Re: [103all] Visas for IETF 103 in Thailand
X-BeenThere: 103all@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Mailing list of all 102 attendees for official communication <103all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/103all>, <mailto:103all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/103all/>
List-Post: <mailto:103all@ietf.org>
List-Help: <mailto:103all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/103all>, <mailto:103all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2018 16:14:55 -0000

For myself, the information seems pretty readily obtained. I asked my favorite search engine “do I need a visa to go to Thailand”, and up popped https://th.usembassy.gov/u-s-citizen-services/thai-visas-americans/. You might make a similar inquiry.

Sent using a machine that autocorrects in interesting ways...

> On Aug 15, 2018, at 1:03 AM, Carsten Bormann <cabo@tzi.org>; wrote:
> 
>> On Aug 14, 2018, at 21:47, Andrew Sullivan <ajs@anvilwalrusden.com>; 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
> 
> -- 
> 103all mailing list
> 103all@ietf.org
> https://www.ietf.org/mailman/listinfo/103all