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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 24 May 2016 22:20 UTC

Return-Path: <prvs=195250426c=jordi.palet@consulintel.es>
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 C205912D586 for <ietf@ietfa.amsl.com>; Tue, 24 May 2016 15:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level:
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, USER_IN_WHITELIST=-100] 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 Vq48Z1f9Q7ND for <ietf@ietfa.amsl.com>; Tue, 24 May 2016 15:20:53 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0C612D5A4 for <ietf@ietf.org>; Tue, 24 May 2016 15:20:52 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Wed, 25 May 2016 00:20:51 +0200
Received: from [10.10.10.99] by mail.consulintel.com (MDaemon PRO v11.0.3) with ESMTP id md50000546782.msg for <ietf@ietf.org>; Wed, 25 May 2016 00:20:51 +0200
X-Spam-Processed: mail.consulintel.com, Wed, 25 May 2016 00:20:51 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=195250426c=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.16.0.160506
Date: Wed, 25 May 2016 00:20:48 +0200
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <201BB54E-ECEF-46F3-BE79-FBDF12CAAD40@consulintel.es>
Thread-Topic: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
References: <D3662363.190A96%jon.peterson@neustar.biz> <CAHkmkwtEtDk4sPv3GjkrSFqOdRV3HBA5i2_uZu3X2D4RxSF4wA@mail.gmail.com> <2e95fd51-23b8-39e7-d4ca-a9fc9d49559c@gmail.com> <CAHkmkwsf3YfFfR7jUHYnaw6dCrasMOazjbXPJRRhZS28k8HV0w@mail.gmail.com> <alpine.DEB.2.02.1605241405210.28372@uplift.swm.pp.se> <714DDDE2-562D-488A-AAAA-F8DE3C2CA97D@consulintel.es> <FE76F502-617E-4190-BFF5-649EC9CFECAC@consulintel.es> <CABcZeBMPAFdLwZTr7TCJC-tZ+X=CKGzQ7Jp0zqDO86PdPn6YvQ@mail.gmail.com> <8D82EA4F-1275-436C-8030-1E799F5D7F59@consulintel.es> <CABcZeBOCtk6JK_3w2_L87oyze+dfgy7fFyU7QrGmGgEtta1oZA@mail.gmail.com> <1CA535AB-CAC4-49CB-B094-AAA7FE3119FB@consulintel.es> <2b01eb8f-d319-7d20-0f84-9a774f9e0e44@nostrum.com> <C01AE269-3168-4B6A-B8D8-D97230288302@gmail.com> <8161273d-97c2-2757-5f0c-6146d0b297aa@nostrum.com> <E51DA1A2-AB3E-42F7-BC0A-308BE6B58580@gmail.com> <2270ea7c-cd6d-c3d5-e768-6d1f0ae15605@nostrum.com> <216D2B11-5E07-4DBE-BCC4-0A8ABCCB15B7@gmail.com> <cf9ad015-ef7d-6e11-44e8-6a0fb5a78b91@gmail.com> <EBBFC64A-C730-47D8-8F66-E4C7773A0344@gmail.com> <D5E06CF1-9C2D-41BE-8635-1F73321986EC@consulintel.es> <CAG4d1rfvYrW5TDCzdUoFeeQFnsDejWFn7jH+20xnJ4QHEsJ=2g@mail.gmail.com> <F2144741-4441-4F6E-B91E-6AEB52BCA7CF@consulintel.es> <CAG4d1rdC2SBC6F4-8MJGsJBt7kbJ+kRA5MKC5ZVUyhjCUJLkCg@mail.gmail.com>
In-Reply-To: <CAG4d1rdC2SBC6F4-8MJGsJBt7kbJ+kRA5MKC5ZVUyhjCUJLkCg@mail.gmail.com>
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/XMlKCrjywU0PWnf4se146XTwqXI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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: Tue, 24 May 2016 22:20:56 -0000

Be sure that at no means I want to discourage anyone to participate in the IETF meetings, or giving less priority to few than majorities, but in the scope of the work itself.

I guess the main problem is our disagreement regarding that a participant of the IETF has no other choice than
1) Go to a meeting and bring his family
vs
2) Not going to the meeting or not bringing his family.

I said this already a few messages ago. If instead of the IETF is a business meeting that your boss tell you need to go (at least in my country, and here comes what you said about different cultures), you will have no choice:
a) Go there
b) You’re fired, maybe unless a colleague can make it for you and your boss accept it
But definitively, you will not be able to argue in front of a court to defend your job that you can’t go there because your family need to go there with you and that country don’t allow it.

I know seems quite simplistic approach, but what I’m saying is that as much as we can we should support families to go to IETF meetings as much as possible, but not necessarily change our decisions (even less if already taken and engaged in contracts), If in some cases that’s not feasible/convenient, unless the situation affects a big enough group that will mean the work can’t be done.

Regards,
Jordi


-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Alia Atlas <akatlas@gmail.com>
Responder a: <akatlas@gmail.com>
Fecha: martes, 24 de mayo de 2016, 23:48
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Asunto: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

>Hi Jordi,
>You are completely right that I don't know your personal circumstances.  I do hear you implying that those with circumstances that might require bringing their families or other assistance should figure out ways to participate in the IETF that don't involve going to the problematic meetings.  I feel that discourages particular sets of people from participating in the physical meetings.
>
>As far as Singapore goes, I don't have a clear opinion.   It is one meeting - not a pattern.  All the information from folks on the ground indicates that the risk of this being an issue is extremely low - but also quite critical if it did become an issue.  Ted's original ask at the plenary was that others not bring their families.  Indeed - I don't intend to, but I have that luxury this time.
>
>I am concerned that we are pulling apart based on nuanced opinions of a rather complex situation with insufficient information.
>One of the strengths of the IETF is that we come from different cultures and backgrounds.  When we focus on how to make the Internet work better for everyone and many different circumstances, this diversity strengthens us.  When we pick apart each others' perspectives and feel the need to defend our viewpoints and culture as being open enough, I don't find it helpful.
>
>Regards,
>Alia
>
>
>
>On Tue, May 24, 2016 at 5:26 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>
>Hi Alia,
>
>The fact that we are getting up to this debate, means that the IAOC is taking in consideration the issue. Otherwise, the immediate response will have been “sorry, we sympathize with your family issue, but at no means can that situation be taken in consideration for even a simple study to move the meeting somewhere else”. I may be wrong, of course, but is what it looks like.
>
>Nothing personal, believe me, but I must say that you don’t know at all if this affects me or not, you don’t know my personal/familiar circumstances and if doing the meeting in Singapore or an alternative place is better for me and my circumstances. I just take it from another principle. I’m there to work and either I go to the meeting for work (and prioritize the work), or if I’ve a familiar problem and is in clash with my work, tell my employer and find an alternative solution instead of going there. What I can’t definitively do is to ask for a venue reconsideration, unless the problem affecting me is also affecting a big proportion of the rest of the attendees.
>
>I fully respect inclusion and minorities. I don’t like democracy in the sense that majority always win. Isn’t like that, but when we have a new fact in the table, we should consider it for the future, and balance it with the rest of the possible considerations from every other minority, and again, put on top the maximum priority of the reason for the meetings: Getting the work done for as much people as we can.
>
>Reading other emails from Ted, he already had a few examples, that reflect what I’ve in mind, so I’m not going to repeat them.
>
>Saludos,
>Jordi
>
>
>-----Mensaje original-----
>De: ietf <ietf-bounces@ietf.org> en nombre de Alia Atlas <akatlas@gmail.com>
>Responder a: <akatlas@gmail.com>
>Fecha: martes, 24 de mayo de 2016, 21:12
>Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
>CC: IETF Discussion Mailing List <ietf@ietf.org>
>Asunto: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
>
>>Jordi,
>>I've never heard any indication that the extremely minimal companion stuff (a mailing list and one gathering that the companions pay for) has factored into the IAOC venue-selection.
>>
>>It's always easy to give up - in the abstract - things that don't affect you.
>>
>>In this particular instance, the concern is about keeping legal guardianship & medical concerns in a
>>country whose laws may not recognize familial ties legal in other countries.   There can certainly be personal
>>reasons why bringing a child along is necessary - and they don't require others' judgement as to whether those
>>reasons are "deserving" enough.
>>
>>Regards,
>>Alia
>>
>>
>>On Tue, May 24, 2016 at 3:04 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>>
>>+1  to drop companion stuff IF it is increasing the IAOC venue-selection criteria difficulties, and I want to make it clear, even if it affects me personally at any time.
>>
>>Even if is only for simple curiosity (I don’t think our decisions must consider other organizations decisions, but is always good to know), it will be nice to know if venue-selection-criteria of other similar organizations take in consideration possible “difficulties” for companion/familties.
>>
>>Regards,
>>Jordi
>>
>>
>>-----Mensaje original-----
>>De: ietf <ietf-bounces@ietf.org> en nombre de Yoav Nir <ynir.ietf@gmail.com>
>>Responder a: <ynir.ietf@gmail.com>
>>Fecha: martes, 24 de mayo de 2016, 20:52
>>Para: Melinda Shore <melinda.shore@gmail.com>
>>CC: <ietf@ietf.org>
>>Asunto: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
>>
>>>
>>>> On 24 May 2016, at 9:28 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
>>>>
>>>> On 5/24/16 10:14 AM, Yoav Nir wrote:
>>>>> Then I guess where I disagree with both you and Melinda is that I don’t
>>>>> think the ability to bring families along should be an important
>>>>> consideration.
>>>>
>>>> I don't, either, but as long as the IETF does, and provides
>>>> a companion program, I feel quite strongly that IETF travel
>>>> should be equally accessible to all families.  I'd personally
>>>> be good with dropping the companion stuff UNLESS it was done
>>>> specifically to avoid problems with travel to places hostile
>>>> to same-sex partners.
>>>
>>>I would be happy with dropping the companion stuff for many reasons. The fact that it adds considerations and criteria to the IAOC’s decision process that already has way too many criteria is just another reason to drop it.
>>>
>>>Yoav
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>