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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 24 May 2016 22:44 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 30EF612DA05 for <ietf@ietfa.amsl.com>; Tue, 24 May 2016 15:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 ZXPXUgiKottt for <ietf@ietfa.amsl.com>; Tue, 24 May 2016 15:44:03 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DCAD12DA04 for <ietf@ietf.org>; Tue, 24 May 2016 15:44:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 02791BE58; Tue, 24 May 2016 23:43:59 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ds11lOn6QlIH; Tue, 24 May 2016 23:43:57 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3DCCCBE59; Tue, 24 May 2016 23:43:57 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1464129837; bh=g++4FFnK2/CHI0w4cuqT/J/kIgGK1FmdFb81sVB2VvY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=VhOHZkG9A86l5UmNiu8oZgpAnU4c5R6ecQ7x40hrsYcIW+dHAR+i1TIaTWKgL1A2g u8nlxVtLa4Lg6wQNJpErQ65KoW5UB7ILwrLwZBZPewDfcxB6/BIeMBi2BgQ7lq9n91 /ZT4tK5vkgPi57tybpH/4A3N7tBv3R1ZDyLc2iCU=
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
To: Alia Atlas <akatlas@gmail.com>, Jordi Palet Martinez <jordi.palet@consulintel.es>
References: <D3662363.190A96%jon.peterson@neustar.biz> <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>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5744D92D.7040208@cs.tcd.ie>
Date: Tue, 24 May 2016 23:43:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAG4d1rdC2SBC6F4-8MJGsJBt7kbJ+kRA5MKC5ZVUyhjCUJLkCg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080200040002050307030308"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HdLlaHoGQjsDAqgqV52YYgSQRG0>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
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: Tue, 24 May 2016 22:44:05 -0000


On 24/05/16 22:48, Alia Atlas wrote:
> 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.

That about sums it up for me too.

Purely related to IETF-100:

If there're indications that practical problems could occur
with a non-negligible probability, I'd be for moving the meeting.

If we find good evidence that even in cases folks are concerned
about (e.g. hospitalisation) there have been cases of male couples
not having issues with that, then I'd be fine with keeping IETF-100
in Singapore.

I'd be surprised if we could get good evidence for either of the
above. If we can, great, but I'd not count on it. At this point
I think anecdote or absence of evidence isn't likely to be very
useful in terms of convincing folks.

That leaves me figuring that I'm ok to trust the IAOC to make
the best call they can on this one. I hope they do so in as open
a manner as possible. If they choose to not move the meeting, and
on the basis of what I know so far, I'd likely go (assuming I have
funding at that point). The same is true if they do move it.

I do think that this discussion has shown convincingly that we
ought in future consider additional aspects of inclusiveness,
including family accompaniment, as good reasons have been offered
for that. (That's in addition to the other issues about general
transparency etc.)

S.