Re: [Mtgvenue] editor's take on draft-ietf-mtgvenue-iaoc-venue-selection-process

Mark Nottingham <mnot@mnot.net> Tue, 01 May 2018 23:58 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83A71275F4; Tue, 1 May 2018 16:58:25 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=2Z982h1G; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IARrIZ4p
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 bYm-75w_5biB; Tue, 1 May 2018 16:58:23 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEAF21200A0; Tue, 1 May 2018 16:58:22 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 09D3C22087; Tue, 1 May 2018 19:58:22 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 01 May 2018 19:58:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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=cuPi22SaoQBbPDtguwnpwBewWM8fA eRXA3hUrfs/xlk=; b=2Z982h1GFZ+MKASHXgJok4R9Y/mNoAvLk0GxOGBbDt09r Qdlkw/rEf6J3yhJ1O9sdeqohcuQdtiaL3xg4vyR5rsddjmuDizVqXSpljM+znIs2 D/bTw9huMplWi6NX6+c0ovXEIl6I2wdAXhvZlJ2M178kCID5iityyYBHfiBzBmPO n01jBKsUkiE+JK4ahOuXK8mj+KLuXcFKzrf34FUr3E8xX/4OPeXBg4dHplRynclo ETABQcrV6izyAxVCERQPFEExcafFFCfHA0853vN2xJl/sw0dRX5m2HNinHzw/k3V yQWPYh0n2q7FXgBT9ClmNDLANeLLudgCv/RU8UWdg==
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=fm2; bh=cuPi22 SaoQBbPDtguwnpwBewWM8fAeRXA3hUrfs/xlk=; b=IARrIZ4pDfYbr2l3HLWrnz 5O8VlCB+qK1quYXqcwAvqa9596QwsvYdOp1ouT2+K/NxuXIS5rkQiQpxNIE2PjCM 5niOWzSYs0007C7Y7kktSoSH9yPKngf5p9C/fjJTu0/QWuS6dtwMJQ7wkhw3hZiz V0QxY0aA7trbjoN+0H2s287hHET5uEgs5e7Ag4DwHGazMDnhQShQTThKRevWK9// nyGHlh724++lsLUhQIz2hWR5mDX+Hffx/b9WaLAsC210HDGROYhMXYNlKKRiKYzM XYFO35pJsQTSPrzam1+nZRv8UHlReZQp0FPjbV0Lz00vyNRVoTXOnwjXJruGR6Lw ==
X-ME-Sender: <xms:Hf_oWnCIBW0SyM6EVau6eCi7C3HyEQZNlqgk2BkiwX1d4C7NSk3GmA>
Received: from [192.168.1.25] (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id AA8711025C; Tue, 1 May 2018 19:58:19 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <A000D4CB462D1CD5461A466A@PSB>
Date: Wed, 02 May 2018 09:58:17 +1000
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Alissa Cooper <alissa@cooperw.in>, mtgvenue@ietf.org, ietf <IETF@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <51FB4E00-CB2B-4D1A-982A-EED9F2F227A1@mnot.net>
References: <CA+0Hr7syW5Jy8eyQxBU_GCbL+Omj0uR-x6bBB_Y0PjcNQ8wM2g@mail.gmail.com> <A1A1BC2A-9DFE-42AB-B93F-B80C306C9C01@cooperw.in> <7A3D61FB-40B2-456B-A174-407AF42783A5@gmail.com> <97CC171E239852CA5145CA09@PSB> <3CAE6814-F809-4D94-8680-F00A8F715685@mnot.net> <A000D4CB462D1CD5461A466A@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/xHBELU4cUp03pAlRxfcyR_Wms3Q>
Subject: Re: [Mtgvenue] editor's take on draft-ietf-mtgvenue-iaoc-venue-selection-process
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 23:58:26 -0000


> On 2 May 2018, at 9:43 am, John C Klensin <john-ietf@jck.com> wrote:
> 
> 
> 
> --On Wednesday, May 2, 2018 08:35 +1000 Mark Nottingham
> <mnot@mnot.net> wrote:
> 
>> On 2 May 2018, at 7:14 am, John C Klensin <john-ietf@jck.com>
>> wrote:
> 
>>> Given the above (and implicitly incorporating at least some
>>> of > Alissa's comments), do you believe it is necessary and >
>>> appropriate that we change our procedures to give parents
>>> with > small children (and possibly other groups with special
>>> issues) > priority on bookings in the meeting hotel?
> 
>> It seems like we could borrow from common practice on public
>> transport; if you're pregnant / with small children /
>> mobility-challenged (permanently or temporarily), you get
>> access to a separate hotel booking block / preferred seating
>> in the meeting rooms.
> 
> Mark, 
> 
> Again, I was trying to ask whether people thought this was
> desirable and appropriate, not how to do it if that conclusion
> were reached.  Your suggestion is about the (or at least an)
> obvious way to do it if that conclusion were reached.  

Then please consider my answer as a "yes".

> That said, an observation to save others, especially IAOC
> members, time.   While I'm pleased that it has apparently not
> been a problem for Montreal, we seem to routinely have
> complain-fests about the main hotel room block selling out
> almost as soon as reservations open.  Now think about the effect
> of reserving a block of unknown but probably large size (because
> we don't have even a rough estimate of how many people would
> want to use it) on that sometimes already-tight situation and be
> careful what you wish for.

I find it difficult to respond to these potential effects without returning to a discussion of "how to do it." If I were to do so, my suggestion would be to start small and gather data.

Cheers,



--
Mark Nottingham   https://www.mnot.net/