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

Sean Turner <sean@sn3rd.com> Wed, 15 August 2018 18:13 UTC

Return-Path: <sean@sn3rd.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 C472F1277C8 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2018 11:13:05 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 PXMA-JrZRXh3 for <ietf@ietfa.amsl.com>; Wed, 15 Aug 2018 11:13:03 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 49843128CB7 for <ietf@ietf.org>; Wed, 15 Aug 2018 11:13:03 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id t5-v6so2186991qtn.3 for <ietf@ietf.org>; Wed, 15 Aug 2018 11:13:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wF/dhZ0GPJsrhqKcm9SUMu8zgppIoWiCqLxv9C+tEGE=; b=AskkRmcjj2pz2MxViLRf6Ra6FeR5v0Ak9qdH4ajE6OtWkbRUccCygylvPsDQLLb07Q jfaWP8U7nCEZGZOc/yY/KKYfPi6CPgcrwGNehRTJnKFUS6ECm/0sKi2rkv6MmtXsxduH C9JA+kT0VG8YZ+jY6yUCTAgofc4iJ/fOghcOI=
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=wF/dhZ0GPJsrhqKcm9SUMu8zgppIoWiCqLxv9C+tEGE=; b=LlOMMcR08IQ2dIqvu2wWY84deSZr4IzyUmIbePBQxMdajQSq65krypXupzUegdfaOt U94igunr/4DfQklTU5kXINNNRsZVzTr3KXDlxzyrptrSjsRd37o1Rg2kSxgD5xGO+H0v jEbnA6XjBb8ua0PVAdmF++XNe/81GjQR+Lk3F7nJOHMTcIFIJXsKJXvzy4ImltHrjapG uVHf55HjY/nCoyW9z3esaVnOGRXBc213bYZb8dpvi/9LtRR9D4I7EcSIcVsxPUSXIXWV qyjVQ/KrhVJlD8nByEM4vl/Naeed0qgUtPZyZHv7UODtSZlqG10gXPwUMUueELupvsNF 5z4Q==
X-Gm-Message-State: AOUpUlGQgeeqPk/I0/UIMFj1loeq/RgSr6jCas4A+vfU4OIo0q27gwi1 +zLEgazfiROBLFNRSMJSRXJAzKr1lIM=
X-Google-Smtp-Source: AA+uWPx8ToSuJWKGyGx6km6OtXG8nL1pTHqgN0vDmrd0z/czTCLnt7U2HkOzx5pMk9yCCw0q+L00kw==
X-Received: by 2002:ac8:6790:: with SMTP id b16-v6mr27232392qtp.66.1534356782370; Wed, 15 Aug 2018 11:13:02 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.225.148]) by smtp.gmail.com with ESMTPSA id b83-v6sm14178958qkc.20.2018.08.15.11.13.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Aug 2018 11:13:01 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [103all] Visas for IETF 103 in Thailand
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <41103334-DDAD-451F-AED4-9D268D907372@gmail.com>
Date: Wed, 15 Aug 2018 14:12:59 -0400
Cc: Carsten Bormann <cabo@tzi.org>, 103all@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B7371BC-FFA1-4FD3-9E13-1BED87A66F4A@sn3rd.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> <41103334-DDAD-451F-AED4-9D268D907372@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UUdkyJX-V3LUuYrKie3a0gaNieE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 15 Aug 2018 18:13:06 -0000

That is typically what I do too, but I also stumbled across this handy link at United:

https://www.united.com/web/en-US/apps/vendors/default.aspx?i=TIMATIC

spt

> On Aug 15, 2018, at 12:14, Fred Baker <fredbaker.ietf@gmail.com> wrote:
> 
> 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