Re: [Mtgvenue] Open issue: legal discrimination based on status/identity

Dave Crocker <dhc@dcrocker.net> Sat, 28 January 2017 03:56 UTC

Return-Path: <dhc@dcrocker.net>
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 A1812129B8A for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 19:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 d0YIkOBd9BTj for <mtgvenue@ietfa.amsl.com>; Fri, 27 Jan 2017 19:56:32 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C13F129B88 for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 19:56:32 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0S3w5pF007993 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <mtgvenue@ietf.org>; Fri, 27 Jan 2017 19:58:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485575885; bh=W5wWYyJgZki9i4s968KrR/L5KBA7ag57iDke4Co0Pbs=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=PTTqYTM2yBw4CIU48ZIcj1d95rRvVDml6AmzdxPz0HFeqH2Zuexfq/iyGz1ZfIYXg CEAjnMqtfJ8YsjjAsba6o4hUuop5UfvFSnUUgHusmYMXnFKSkRXIqidBFwQjjeopbf yjJSaX/+gnxlHlkaJlyGLi19nXH0tXsc1qnf+UEE=
To: mtgvenue@ietf.org
References: <55b0639f-a084-9582-cf22-061c29001f77@nomountain.net> <6.2.5.6.2.20170127162623.0efe9cf0@elandnews.com> <0c8fb5c6-e3cd-1cf7-3168-57264e68bc78@nomountain.net>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <0ecb9acd-92e3-11f6-4927-8c14932f1d7b@dcrocker.net>
Date: Fri, 27 Jan 2017 19:56:20 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <0c8fb5c6-e3cd-1cf7-3168-57264e68bc78@nomountain.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/oTrOYd9V_7oZySpJtujhh5NCWBc>
Subject: Re: [Mtgvenue] Open issue: legal discrimination based on status/identity
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sat, 28 Jan 2017 03:56:33 -0000

On 1/27/2017 5:50 PM, Melinda Shore wrote:
> The problem we're
> trying to solve with respect to venue selection is to establish
> policies that define conditions that can or should be met
> that allow IETF participants to travel to meetings
> without consistently placing undue burdens on some subset.


The IAOC has, at least once, chosen to decline from exploring an 
otherwise-very appealing venue that had onerous visa policies, which 
targeted exactly one country's citizens, and which would have affect 
perhaps one IETF attendee at that time.

(A challenge with the constraint to focus on 'attendees' is the desire 
to encourage new attendees, from everywhere.)

I don't know where the IETF should draw the line on selecting venues 
with respect to this kind of concern.  I don't believe it is possible to 
write a clear, precise, adequate rule that covers all such cases.  And 
so, for example, I don't know whether the US's latest action should 
preclude going to US venues.[*]

That's why I'm so fond of merely having the IETF community use its 
aggregate voice during an early city review query.


d/

[*] 
https://www.nytimes.com/2017/01/27/world/middleeast/trump-visa-muslim-ban.html
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net