Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review of draft-ietf-mtgvenue-iaoc-venue-selection-process-12

Alissa Cooper <alissa@cooperw.in> Tue, 06 February 2018 01:54 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B194A1241F3; Mon, 5 Feb 2018 17:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=cr28485K; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=S8ZVqKUP
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 fbh9oT1sEAn0; Mon, 5 Feb 2018 17:54:40 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6504B1200F1; Mon, 5 Feb 2018 17:54:40 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C992620BB9; Mon, 5 Feb 2018 20:54:39 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Mon, 05 Feb 2018 20:54:39 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Wr5ZqQaxqT8eSzh+Q3waPNVm61W5x JUFykxY/vafCtw=; b=cr28485KN2wYnIImIYxVM4AqBOol7xOthONh++1rIo/dY WD6z2mX9D+JcCRjZ9uKttpIb8L8114wpvF8cOfJYqkvEk1pJX60AA9XmBhnA0QsO S6okFau3jwif0Erl8oxOL+QTBJ9v2BnA9vK/L8muF/vcVD1KIyFltf8mvqt9GFfK PuZbqwLlB2wixtwmyXBQMFobjMUDT56mg2ob3QP+QAs1yPSjhAOEb66sDrXVa5FV rU3YUmtK8t0LSPZllbkUa5uxhhUpYpTg7d+1GnR+s0fcncN+3icniEYyMFD/edlc vxjwyMR+zCVODeTc/uL0eIyJWRZu/AKg6unFTDtCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Wr5ZqQ axqT8eSzh+Q3waPNVm61W5xJUFykxY/vafCtw=; b=S8ZVqKUPQ6+nUKrNclZTKC HsGGxz5RRON+EbKOoIdPe5D30xrSwYEZTOhi9EMwbf5Mad/eP41WPVC/j458plnr zH8teYBMHoOnd09Wh+KijOAaO/v0Nb37373w8A9TbTBZgAIhvl3DiOk1rwzzhlfb FwibYf+P6S5U3D+cVMyFhPAemWbI/QcAJQ5zVDsCiO8HbbX74NuI4LrS4IihJC41 CWqIg3AzBDFqRqBJOvqz7uTZQVtvFMdmIk+G/rNSQoBu2ZwrWjeLAID0316aNgRt 4FrZjtn0+LSI5LIiUA60/wUnTz+8m/Mk2Q+vZJ+sK6H31GNAdbAs6DLAsoZAmEyw ==
X-ME-Sender: <xms:3wp5WoV0CwYV6LaqHoy79-0ttDzgpncGmJv49zTlx64RH8UCRsz0eg>
Received: from alcoop-m-mx19.fios-router.home (pool-108-48-166-97.washdc.fios.verizon.net [108.48.166.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 703137E13B; Mon, 5 Feb 2018 20:54:39 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <33e0b6d3-6bda-b8c2-e08a-8d4c935f630e@gmail.com>
Date: Mon, 05 Feb 2018 20:54:38 -0500
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Stewart Bryant <stewart@g3ysx.org.uk>, mtgvenue@ietf.org, rtg-dir@ietf.org, IETF <ietf@ietf.org>, draft-ietf-mtgvenue-iaoc-venue-selection-process.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <918BC1CF-2B6D-4118-9139-F426F5F97AA1@cooperw.in>
References: <151782868264.5731.15496399706573021777@ietfa.amsl.com> <15F0E669-0195-4315-AAA5-AED71CD6C5B3@qti.qualcomm.com> <33e0b6d3-6bda-b8c2-e08a-8d4c935f630e@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/8R41TOd6a1k2pphfUEUWqVW3Pzc>
Subject: Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review of draft-ietf-mtgvenue-iaoc-venue-selection-process-12
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 01:54:42 -0000

> On Feb 5, 2018, at 2:06 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 06/02/2018 04:40, Pete Resnick wrote:
>> Hi Stewart,
>> 
>> Thanks for the review. Just on the things that Eliot hasn't already 
>> covered
>> 
>> On 5 Feb 2018, at 5:04, Stewart Bryant wrote:
> ...>> Where we meet?
>>>      We meet in different locations globally, in order to spread the
>>>      difficulty and cost of travel among active participants, 
>>> balancing
>>>      travel time and expense across the regions in which IETF
>>>      participants are based.
>>> 
>>> SB> Given the support and encouragement of remote participants, there 
>>> ought to
>>> be a note about sharing unreasonable time zone difference pain across 
>>> the
>>> spectrum of remote participants.
>> 
>> I don't believe we currently do take that into account in location 
>> selection (perhaps others can chime in), so this would be a new 
>> requirement. We could bring this back to the WG to try and get consensus 
>> around it, but that doesn't excite me. :-) I'll leave it to my fearless 
>> AD to advise.
> 
> Having participated in the IETF while living in UTC+1, UTC, UTC-6
> and UTC+12 at various times, all with or with daylight savings, I feel almost
> uniquely qualified to comment on this.
> 
> Firstly, add jet lag for the in-person participants to the mix. Then
> try to work out the optimisation function across all participants,
> to simultaneously minimise jet lag effects and unsocial hours.
> 
> I think it's impossible. At the very least, it's a rat hole. So I
> highly recommend leaving this issue aside.

Fully agree.
Alissa

> 
>    Brian