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

So, Fred, are you going to tell immigration you're there as a tourist or to
work?   That's the whole crux of it.  There is the referenced website in
this thread about conferences, expos, etc. that suggests you don't need a
VISA for those, but that's not an official website.

On Wed, Aug 15, 2018 at 11:14 AM, 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
>
>