IETF Logo Mail Archive

Re: [Mtgvenue] visa situation... worsens?

"Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com> Fri, 24 March 2017 14:36 UTC

Return-Path: <Glenn.Deen@nbcuni.com>
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 7F2DA13150A for <mtgvenue@ietfa.amsl.com>; Fri, 24 Mar 2017 07:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 RypFTnif_OrQ for <mtgvenue@ietfa.amsl.com>; Fri, 24 Mar 2017 07:36:07 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0a-00176a04.pphosted.com [67.231.149.53]) (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 82280131509 for <mtgvenue@ietf.org>; Fri, 24 Mar 2017 07:36:07 -0700 (PDT)
Received: from pps.filterd (m0048276.ppops.net [127.0.0.1]) by m0048276.ppops.net-00176a04. (8.16.0.20/8.16.0.20) with SMTP id v2OERwJa005256 for <mtgvenue@ietf.org>; Fri, 24 Mar 2017 10:36:05 -0400
Received: from usaoamgip002.mail.tfayd.com ([173.213.212.136]) by m0048276.ppops.net-00176a04. with ESMTP id 29ba187pj8-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT) for <mtgvenue@ietf.org>; Fri, 24 Mar 2017 10:36:05 -0400
Received: from unknown (HELO USUSHECWP004.mail.tfayd.com) ([10.40.78.204]) by usaoamgip002.mail.tfayd.com with ESMTP; 24 Mar 2017 10:36:03 -0400
Received: from USUSHEMWP012.mail.tfayd.com ([169.254.4.151]) by usushecwp004.mail.tfayd.com ([3.156.41.22]) with mapi id 14.03.0266.001; Fri, 24 Mar 2017 07:36:03 -0700
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
CC: mtgvenue <mtgvenue@ietf.org>
Thread-Topic: [Mtgvenue] visa situation... worsens?
Thread-Index: AQHSo0c1JEsJE39nhkaJSv8k0j3WcqGh22KAgAAByQCAAqL5gP//kTqO
Date: Fri, 24 Mar 2017 14:36:02 +0000
Message-ID: <EBE7909B-64D0-4898-8D18-201CC6A97B6C@nbcuni.com>
References: <2805.1490212930@obiwan.sandelman.ca> <CAKe6YvNXAucSABZrc84SQEmhevcV3O5Ft3hxKcgg94rvt7kdTg@mail.gmail.com> <97F88D1C-6940-40AA-BACC-10F568E61BB1@consulintel.es>, <86357066-b5c3-7d4b-3012-92ae63a3f22d@dcrocker.net>
In-Reply-To: <86357066-b5c3-7d4b-3012-92ae63a3f22d@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-24_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703240126
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/SSe5f8Irlx7wTjCyhgGh2UcxW9c>
Subject: Re: [Mtgvenue] visa situation... worsens?
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 24 Mar 2017 14:36:09 -0000

I would suggest that instead of rushing to make any major decisions that we first must get hard data on the visa problems visitors are facing and not rely on news reports, social media reports, or individual experiences reported via blogs. 

The IETF has a significant number of attendees and sponsors from the US and completely stopping scheduling meetings in the US may also have some unintended consequences that we will not discover if we rush to act without thought and critical analysis.  

For example we may have attendees who for their own visa issues cannot leave the US and our periodic US meetings are their only opportunity to attend in person.  

Clearly there are very legitimate concerns here but we need to seek out facts perhaps from talking to other organizations that host internationally attended events in the US and from professionals that deal with obtaining visas for visitors to those meetings. 

Glenn 

Sent from my iPhone

> On Mar 24, 2017, at 2:12 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> 
> 
>> Agree, we should definitively STOP completely doing meetings in US while this situation keeps going on.
> 
> 
> If there are folk who believe that the IETF should continue to hold meetings in the US, it might be helpful for them to post comments here, supporting that view.
> 
> d/
> 
> -- 
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue

v2.23.0 | Report a Bug | By Email