[Mtgvenue] Visa problems to Thailand -- tourism vs ED
Michael Richardson <mcr+ietf@sandelman.ca> Sun, 09 September 2018 18:53 UTC
Return-Path: <mcr+ietf@sandelman.ca>
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 F1FFD130DDE for <mtgvenue@ietfa.amsl.com>; Sun, 9 Sep 2018 11:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YWPdwutEIuUP for <mtgvenue@ietfa.amsl.com>; Sun, 9 Sep 2018 11:52:59 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C396D130DCD for <mtgvenue@ietf.org>; Sun, 9 Sep 2018 11:52:59 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B014020090 for <mtgvenue@ietf.org>; Sun, 9 Sep 2018 15:11:45 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A82BE344B; Sun, 9 Sep 2018 14:52:57 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A4FCA3446 for <mtgvenue@ietf.org>; Sun, 9 Sep 2018 14:52:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mtgvenue <mtgvenue@ietf.org>
In-Reply-To: <6C126AA4-C07B-4E41-8169-D0E6C8B4535E@episteme.net>
References: <A8143A75C4D32848AB4E59FFC8B8FBA84BD19247@SINEML521-MBX.china.huawei.com> <alpine.OSX.2.01.1808291846180.5588@ole-pro-2.local> <163e477e-956b-c388-a062-115ad64629c2@gmail.com> <alpine.OSX.2.01.1808291954390.5588@ole-pro-2.local> <1762761125.28180.1535604751601@ichabod.co-bxl> <0DCD267A-8333-41D2-875B-F68051789BB8@gmail.com> <1725ef85-0763-85ca-7e31-bd251e4b4bac@ericsson.com> <CAMb9nTsY2rg=ScppYxsaaesxBuS4DdZJraqjm9Vk-zWcMV_uhw@mail.gmail.com> <51f80d90-4413-86c2-96d4-f950ed321cca@ericsson.com> <CALZ3u+bf6x1O=v+0YYwpf4UNZdH3kfEs+dMLYG4pnY8Au+g72Q@mail.gmail.com> <CAC6JZKSe89qQcz9AEefWe1G_qKkS3LVymAvKfxQc2b67+ZJmTQ@mail.gmail.com> <684305d8-d384-edc1-3723-95764cb06153@nthpermutation.com> <alpine.DEB.2.20.1809062003540.27924@whs-18.cs.helsinki.fi> <e3bb17d6611547a9a0a09aaa318bff38@tudelft.nl> <6C126AA4-C07B-4E41-8169-D0E6C8B4535E@episteme.net>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 09 Sep 2018 14:52:57 -0400
Message-ID: <11660.1536519177@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/hrNA3lqhi6vVd17dujXLb4GCnik>
Subject: [Mtgvenue] Visa problems to Thailand -- tourism vs ED
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 09 Sep 2018 18:53:02 -0000
0) Lots of references to IASA in both draft-ietf-mtgvenue-meeting-policy-07 and draft-ietf-mtgvenue-iaoc-venue-selection-process-16 reference IASA and IAOC. Is there an AUTH48 plan to change these to LLC? 1) I'm asking because maybe we need an additional AUTH48 change detailing what "visa requirements" means in section 3.2: Section 3.2 includes: Travel barriers to entry, including visa requirements, are likely to be such that an overwhelming majority of participants who wish to do so can attend. The term "travel barriers" is to be read broadly by the IASA in the context of whether a successful meeting can be had. And we have a long thread this month about whether a VISA is required, if a tourism VISA is acceptable, or whether one of the various business visa's might be appropriate. Along with opinions from a variety of consolulates in various countries who clearly do not know what kind of VISA to issue. At this point, I think that there is a great deal of FUD in the air. It's tangible uncertainty, not just marketing that is occuring here. It started with a request for the IAOC to please collect the list of official statements in one place so that we don't have to do all the leg work (and the uncertainty that we have the wrong info!) The response was that the IAOC can not provide specific advice for any specific travellers is of course reasonable, but completely missed the point. That the IAOC can't manage to point to a specific visa requirement is of great concern. That we do not seem to be on the list of conferences seems to cause a great deal if uncertainty. see: https://mailarchive.ietf.org/arch/msg/ietf/XWeYQJjsZRVNDHcaVAEdpUW4Ri8 I'd like to see a paragraph basically saying that a mtgvenue criteria is the ability to get a clear statement as to what the visa requirements *are* for a specific meeting place. {I'd like to say that a reference to a government web site would be a great thing, ideally hosted in a clear "gc.cctld" place, but it appears that Thai government web sites often use .com. (There is an entire rathole of web-site reputation standardization that we could avoid here... maybe we can make it a W3C problem)} Please note that I am not asking for the VISA process to be predictable, repeatable, or rational. While many of us would like the legal codes to be subject to standardized interpretation, this is clearly not within our ability to affect. That doesn't mean that we can't ask for a stable ISO9001-type reference. Even if the documented process involves rolling die or consultation of the pineal gland. I rather feel like this is micromanaging the IAOC mtgvenue cmte by the community. Maybe this need to do this is part of the frustration that some have with the IAOC. Two months ago, I would not have thought that we needed to write this down, that it would be obvious that a request to place collect the information in one place would be responded to with: "yes, of course, sorry that we didn't point to official-site-X in the announcement" -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Mtgvenue] Visa problems to Thailand -- tourism v… Michael Richardson
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Brian E Carpenter
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Michael Richardson
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Eliot Lear
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Fred Baker
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Fred Baker
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Eliot Lear
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Brian E Carpenter
- Re: [Mtgvenue] Visa problems to Thailand -- touri… Spencer Dawkins at IETF