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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 21 May 2016 21:00 UTC

Return-Path: <brian.e.carpenter@gmail.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 4009312D189 for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 14:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xLKAc3fPL7T0 for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 14:00:10 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (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 8D35E12B007 for <ietf@ietf.org>; Sat, 21 May 2016 14:00:10 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id y69so51800270pfb.1 for <ietf@ietf.org>; Sat, 21 May 2016 14:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=RuFK+kI1wOnECerDb9Qt0Ca/5kxfXUEoe+rzm1Lt7Ls=; b=Rty8tk6bmYJBdJntCp/b09JxkaAzDMls6/dEtn1SA2SCQvg4mZhcqqQOTQbhEm1hra ur+HZAZ3SfHAFg59vbmse7gD7unay+IoKGEqrCEnRLZrPsneHnTEKbD9QV/TGLa2aVdN fofhJiw6mwf44jOyn9GNCt+1L3mfvwK2YIpXCmpL1HDmh3e5AzI6jV4ryelYXHbHDw+z wjB0dNP7qCe2ZIr//b7lkL9g0OOtoZUQJf+1pJkYEg/LRwcbH1E+TL8KHTpD9qHuOOQb 3TA0otmrSeZqH4/NRv8LNod1wRbHzV2I1h73TmyS7hF2XlbYjNVAD64rQB9b9C8QdNcj oxdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=RuFK+kI1wOnECerDb9Qt0Ca/5kxfXUEoe+rzm1Lt7Ls=; b=Et1iZuzh0ykmgmBKEsZFxPAl66iJvuTIpODu0h/o2rhY+PS97vKaEP/SQA35WiSDwJ jXSJgITlcy+ioDTChRBhlX/kBLk12OWQY3k5R0l2Z5lcT9WM8VAyNkX7g/HUPmWqXuES jfJFrlH/YlIoc2ETVQUtFC1FpPW8AX+bGkIeC77XoaDvJAVUvRTK0TbrPk3fUXFf/th2 5xDjdWyepOYrLlOqYE2YaQpOLWWYMgyJ2CoApCpESBR+lxVmGZ7WX3k7ith3+FF1JGzF V82VP1m5sxjQwmpwtRNPkxAz+2HSRrWz8ujodEMJAmXXiX+URtaLn+aI7uYWhEJU/rak U38A==
X-Gm-Message-State: AOPr4FUove50uCefMbNppJ3R84MBamSjciUFHR3zEwevL5W+2sXNnsh/6lgZ6gwETxZQBg==
X-Received: by 10.98.101.198 with SMTP id z189mr15617737pfb.76.1463864409931; Sat, 21 May 2016 14:00:09 -0700 (PDT)
Received: from ?IPv6:2406:e007:4c59:1:9d34:271f:9dfb:d601? ([2406:e007:4c59:1:9d34:271f:9dfb:d601]) by smtp.gmail.com with ESMTPSA id n66sm36040165pfb.17.2016.05.21.14.00.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2016 14:00:08 -0700 (PDT)
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
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.c om> <C5B9F952-FEFC-4B73-9AC6-E050F59A74CB@consulintel.es> <5740A90E.2030200@gmail.com> <34CC7DDE-3341-4BF8-8238-B32176EDC72A@consulintel.es> <55BAE36899C13FA1D0565FAF@JcK-HP8200.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2ceffd31-c78f-f6f7-116e-85498b4413f1@gmail.com>
Date: Sun, 22 May 2016 09:00:05 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <55BAE36899C13FA1D0565FAF@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/82celBh0LmXh911gJoNEi8UMsVI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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 21:00:12 -0000

On 22/05/2016 08:13, John C Klensin wrote:
> Jordi,
> 
> I am almost completely in agreement with Ted's comment and
> summary which are, I think, exceptionally reasonable and
> well-balanced.

I agree, but I also agree with Jordi. The main reason for having
a diversity policy is ethical and moral, but there's also a 'business'
reason - making use of everybody's talents to the maximum - and that
surely is the fundamental reason for the whole site selection policy
anyway. It certainly isn't providing tourist and vacation opportunities
for family members. So...

<snip>

...
> In particular, "nice place to bring family or companion(s)" is
> either a selection criterion or it isn't.  I'm not talking about
> where it is in the list of priorities and tradeoffs; I'm talking
> about whether or not it is on the list.

It could be on the list if we believe that it has a significant
impact on attendance and therefore on financial viability. But
that's surely secondary to 'getting the work done' and 'getting the
best range of people to the meeting'.

> If it is on the list,
> then I think there is an absolute responsibility on the Meetings
> Committee and IAOC to select only those locations where everyone
> in the community who is inclined to bring non-participants along
> can do so.   No one gets to say (I don't think you have, but a
> few others have come close) "It is ok if your particular family
> doesn't feel comfortable coming because our main priority is
> getting work done".  Either "nice for companions" is a criterion
> or it isn't and, if it is, then it needs to apply to _all_
> plausible companions.

Certainly, if we consider it, even as a secondary criterion, it needs
to have a non-discriminatory effect, for moral, ethical *and* business
reasons.

> As to Singapore, if the conclusion is that we should hold IETF
> 100 there (or that we can't plausibly extricate ourselves), I'm
> strongly drawn to the suggestion I think I heard Ted make at the
> plenary, that, out of respect for his situation and that of
> others, _no one_ should bring a family or other companions to
> Singapore.

I'm not sure how realistic that is, but I can no longer resist a comment
that may be politically incorrect but to my mind shows how complex this
discussion could easily get.

I love Chicago. But some stupidity in the US system means that citizens
there are now able to carry concealed guns pretty much anywhere anytime.
I will no longer feel comfortable there next time I visit. I'm not
sure I'd want to bring family members to such a dangerous environment
(and the same went for the last meeting in Dallas). So by your logic,
no_one should bring family or a companion to IETF 98.

Regards
     Brian


> Not only is that a way to show support, but the
> economic impact, even if not huge, is one of the few ways that
> an unambiguous "you need to reconsider the acceptability of your
> laws if you want to continue to be an international go-to site"
> message can be sent even if the meeting is not cancelled.  In
> particular, I believe that the community should send a strong
> message to members of the IAOC, IESG, IAB, Meetings Committee,
> Nomcom, and ISOC and Secretariat staffs that they are not
> allowed to bring _their_ families or companions to a meeting in
> Singapore.  In addition to the sign of respect, that seems to me
> one way to create some institutional memory on this subject --
> it should not have been treated as a new issue when Singapore
> was being selected, but "we" seem to forget these things until
> there are loud complaints, apologize and try to make
> adjustments, and then forget them again.
> 
> best, 
>    john
> 
> Disclaimer: I realized in checking Nomcom eligibility
> requirements that I haven't been f2f to any of the last five
> IETF meetings.  More important to this particular issue, the
> people I might be inclined to bring along discovered that the
> schedule and pace I keep up during IETF makes me no fun to be
> around at all, so the closest they get anymore involves showing
> up after the meeting ends or leaving before it starts (and we
> haven't done that in years).    So I am not significantly
> affected personally by any of this, but that does not prevent me
> from feeling quite strongly that the IETF needs to have its
> criteria straight and to evaluate sites against those criteria
> in ways that are equally fair to all participants.  We need to
> do that not only as a matter of equity and respect because doing
> otherwise does affect the quality and credibility of our work.
> 
> 
> 
>