Re: [Mtgvenue] Visa problems to Thailand -- tourism vs ED

Brian E Carpenter <> Sun, 09 September 2018 20:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ED64C130DFA for <>; Sun, 9 Sep 2018 13:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MBNwW_UsP6iY for <>; Sun, 9 Sep 2018 13:34:31 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 37D6F130DF9 for <>; Sun, 9 Sep 2018 13:34:31 -0700 (PDT)
Received: by with SMTP id d19-v6so9397849pgv.1 for <>; Sun, 09 Sep 2018 13:34:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=sjvt0sto1FK/sUKvYIyJWOGBhQQJkdvGscaB5ULgRrs=; b=vZ0is2+eJl9J7BpFw/f4vvqyB22/tSxQlq3QnDVK4uCbkBzyyrW43DIq0EIME8Jfmt iLxls//NlRlz0jAknlbHODo9XgRLQZAfiA4ggj4WBBuwvbATtFJwH5jkbqkuMLe0QdeH BGnwLCWaSoS6489f7I5Rj7YY/LdtS1PfAugML+nkHqzy0+9JZmByFOuDYT31WCiQbF3z LRRYkEKyHhdNZGFPx61fzsLZEJ2Fdxyrsmz04VpMyHuZ2zMIEh7gKgwX8oLgtHDuKZ1T risuvkqyY1Qdg5yTprj5IMRnA1IAvGsw7sDRQuYt/dMwjFs6ljU4zS469fGA5WplgGkc MjJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=sjvt0sto1FK/sUKvYIyJWOGBhQQJkdvGscaB5ULgRrs=; b=IPAWpAAXwfkCWE1ISe3um4I0h5kUgA5/MQd5JTRhOPtHSPkYmsJVm05DEB6Fxe1S3K LA572eDmYgXFD60pp8JYFBGxS11eDqjv82N07IxbdMzFc8B3EODga0fzhXAChtdlTeW9 gGSEgADclT/c5MWBgvgb8RM7KdevRHa714N45DMpN4z42uMjM9CvCL2GM6+mikzfqKel mD9msAT1DY9DwRJ7UOfyh2baVjhCbH63ByfCybK8aUEmXZ5K6LgNBlgPyeFptplalz4Q EfRN4iDczZOaIerFP8Jqpi6jJ3G5HUUU1BU/d/qLSV9nVubHu7A/GbOrXYPCjrginEHX XaKg==
X-Gm-Message-State: APzg51DplJE69v0WBsX/m6LFake9yJ1AQFW2clSUjhV+2lDO2C4KYmMz Wo6qgZiVWwWM+yX5FBFYXFqeA+v5
X-Google-Smtp-Source: ANB0VdbdDb0Zux+65ZFqSuIc7+Iz8tV1FPEACSfhqlZkSg4v8/IOriHNsijxFdYrSJoj6gZpEG3mnA==
X-Received: by 2002:a63:d44:: with SMTP id 4-v6mr19442638pgn.107.1536525270413; Sun, 09 Sep 2018 13:34:30 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id b126-v6sm18482943pga.49.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Sep 2018 13:34:29 -0700 (PDT)
To: Michael Richardson <>, mtgvenue <>
References: <> <alpine.OSX.2.01.1808291846180.5588@ole-pro-2.local> <> <alpine.OSX.2.01.1808291954390.5588@ole-pro-2.local> <> <> <> <> <> <> <> <> <> <> <> <11660.1536519177@localhost>
From: Brian E Carpenter <>
Message-ID: <>
Date: Mon, 10 Sep 2018 08:34:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <11660.1536519177@localhost>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Mtgvenue] Visa problems to Thailand -- tourism vs ED
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 09 Sep 2018 20:34:34 -0000

On 2018-09-10 06:52, Michael Richardson wrote:
> 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?

As far as I know, "IASA" will still be a valid acronym after the
transition to the LLC. But "IAOC" will need to be fixed. Personally
I'm happy to consider that to be an editorial fix.

> 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.

That "likely" already makes it clear that there's a judgment call involved.

> 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.

That seems reasonable. But why doesn't it apply to *all* "travel barriers"?
(We had some discussion pre-Singapore about whether it was OK to arrive
carrying prescribed medication.)