Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

<nalini.elkins@insidethestack.com> Sat, 21 May 2016 20:21 UTC

Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D26812D189 for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 13:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 nPe47SUhYTtx for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 13:21:43 -0700 (PDT)
Received: from nm29-vm3.bullet.mail.ne1.yahoo.com (nm29-vm3.bullet.mail.ne1.yahoo.com [98.138.91.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0CBA12B007 for <ietf@ietf.org>; Sat, 21 May 2016 13:21:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1463862103; bh=wfR2orHowPKjkhR3PpQZu6U7lH+F8L365tECHjHM8LY=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=XomtvQeyCYcGjjviQAO6RRrLFbBUOw1+xPmW8c18LkvjlE0lyBZgjwN6fLJY+fVe/9ch/mJOj1YzlT4TnfH9YyK1ogr/GII47DDIQ6FzVxmc5h4uiQnKAaA8yfziAkv9F6xViqLWeZKn4hB6pwwqDOxNO318gr1AkUuiAYoywBxYaJ52yWjOPwWXub19pSZgM/nwpuedoi9SgyV2HIrsiU6+EyyTRyAW5Vt+IP5EKfABsuSTsTjsYfWFmVG+2kTHe8HEbfEHyuo3g8MAHOQWCak0Li1Mc4dzqjUnDnvbF9zDvzZBlmTy0yVEUFhhHAAOSPkz/oyE5UflfYt2hiebng==
Received: from [98.138.226.178] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 21 May 2016 20:21:43 -0000
Received: from [98.138.88.232] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 21 May 2016 20:21:43 -0000
Received: from [127.0.0.1] by omp1032.mail.ne1.yahoo.com with NNFMP; 21 May 2016 20:21:43 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 247089.55939.bm@omp1032.mail.ne1.yahoo.com
X-YMail-OSG: RnU6jHoVM1nTB8sZN1emBws9gboGxaijwQuXX3GILRzZpilTqWs1OkcnarkYbPV ekzyZxCNiFip8zGJmtynKnXgl6FxZRV2Gitt6hpRDpqSuvuZjjID82ROnnWFBlWvg8qSVrWlZovv ZyzgO.BZx3NvtUT3ZTrVm7PtgDUZr7DtMdq3P6w5Wfx9tJFkyHpuOuAdmhjxy2wMXgaL3Wv3UrXR p31UWBsBrLEE2BdKvT_EhWdsP1khYi5YWfVM6i_U9hYXSo.FTuzjBP4qml5kySSTZcsP4wcwARVM Y5ZILMGjfR1OBi0GnCE.A7fWP.l1FhoyES3Y6RDnmScUqZvXxlq2JtXYtWeCIB2pbGgFolGirBPA VzWvuwp.M.I3c80Ju4BTJmAGpDK17PhfCWKiFveK3pBTCYyksTXIM60M3.t3RBoT5r_7aLRu.Dxb m8mbjDA._EMdLfC5HFHSkfvdl5IlkfGyCeXZ8Uij1YqfLIqlF4xrJSOurYJDvfEF3fqbZPMeHUOL xB1fIRbqAi5vlxnHruY5wxcEU5NNE3ZodgV96EK7CBSj..oXXpGYtKIGk2w9_dN5uRUvAXDakLuvb
Received: from jws10074.mail.ne1.yahoo.com by sendmailws163.mail.ne1.yahoo.com; Sat, 21 May 2016 20:21:42 +0000; 1463862102.710
Date: Sat, 21 May 2016 20:21:31 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <193234674.293864.1463862091242.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <34CC7DDE-3341-4BF8-8238-B32176EDC72A@consulintel.es>
References: <20160517181436.24852.58610.idtracker@ietfa.amsl.com> <3945cc1f-3e99-0fcb-e983-ed2e46fa871c@nostrum.com> <CA+9kkMAWFQDrT6WqTGz=6LcDiBkg+iuLEuSzeSqfZA4-J-tvZg@mail.gmail.com> <CABcZeBMGpKFiA78iQDFa5xaM0r0q_3LfLO_JKxaWJ9CBUTeaLg@mail.gmail.com> <C5B9F952-FEFC-4B73-9AC6-E050F59A74CB@consulintel.es> <5740A90E.2030200@gmail.com> <34CC7DDE-3341-4BF8-8238-B32176EDC72A@consulintel.es>
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3-MOczhK3nyxZ4m1C7pLm4hjHug>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 20:21:45 -0000

+1
 
Nalini


----- Original Message -----
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ietf@ietf.org
Sent: Saturday, May 21, 2016 12:12 PM
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

Absolutely not, all is about the same discussion. Is about how we select the venues.

It has been said many times, is not about GLBT, is about which country respect all the rights. Is about US or Spain, or country “x”, respecting everything, each country has their own rules, we like it or not. There are many many many possible reasons not to go to US for subset of participants.

I’m not saying I agree with those rules, neither any kind of unequal treatment, not at all. 

What I’m saying is that if we start taking in consideration EVERY possible unequal treatment, politial issues, safety, health, terrorist risks, crime level, etc., etc., etc., then we will NEVER find a good venue.

We can’t find a trade off if we start considering all those issues, so we need to have on top of our priority list the principal reason for the meetings.

I will agree that if being married with a same sex person don’t allow you to go into a specific country, then the country should be banned, but if is a matter of traveling or not with that family, then we shouldn’t take that into consideration for cancelling that venue, because you have the choice to not travel with the family.

IETF is part of our work (some got paid by their companies for it, others not). Let’s take it as if we are “IETF” contractors. We work for IETF, same as we work for our employeer.

If our employeer send us to Singapore, and our famility can’t travel there, we have to choices: 1) Go there without family and do the work 2) Tell our boss, sorry, will not go there.

In many countries, if you tell your boss, sorry I will not go there because I can’t bring my family, this means you’re breaking your contract and you will be fired.

Again, I’m not saying I agree, what I’m saying is that we must put all the apple in the decision basket, but we must have a prioritization for all them and if we can do the work safely, with no famiily, then  we must not exclude that venue.

Otherwise, ALWAYS we may find a smal group of IETF participants that have issues with a specific venue, and if we don’t repect EQUALLY all the cases, then is the venue selections criteria and in consequence all of us, who are doing an unequal treatment to different groups of participants.

Regardss,
Jordi



-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Melinda Shore <melinda.shore@gmail.com>
Responder a: <melinda.shore@gmail.com>
Fecha: sábado, 21 de mayo de 2016, 20:29
Para: <ietf@ietf.org>
Asunto: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

>On 5/21/16 10:14 AM, JORDI PALET MARTINEZ wrote:
>> What about announcing venues and cancelling because whatever
>> circumstances?
>
>Please don't do the slippery slope thing.  Seriously.
>This is about a specific circumstance.
>
>Also, understand that you're asking that GLBT people accept
>different conditions for participating in an IETF meeting.  I
>strongly agree that our top priority is, and has to remain,
>getting work done.  But, for better or for worse, a lot of
>participants bring their family members, and there are some
>basic questions here about equal and unequal treatment, aside
>from the potential safety issues.
>
>Melinda
>
>