Re: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)

Randall Gellens <rg+ietf@randy.pensive.org> Tue, 12 January 2016 18:17 UTC

Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 701791A03E3 for <ietf@ietfa.amsl.com>; Tue, 12 Jan 2016 10:17:06 -0800 (PST)
X-Quarantine-ID: <AatyXpWdBuQb>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 AatyXpWdBuQb for <ietf@ietfa.amsl.com>; Tue, 12 Jan 2016 10:17:04 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id BAE581A03A6 for <ietf@ietf.org>; Tue, 12 Jan 2016 10:17:04 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 12 Jan 2016 10:17:04 -0800
Mime-Version: 1.0
Message-Id: <p06240602d2baf1b32bc7@[99.111.97.136]>
In-Reply-To: <04902D3FAB4E2A56D0D2F985@JcK-HP8200.jck.com>
References: <076c01d138e7$0a68dba0$1f3a92e0$@olddog.co.uk> <5672E4BB.2050702@dcrocker.net> <FA905E0564B6E47B70076F92@JcK-HP8200.jck.com> <p06240602d2ba0deec939@[99.111.97.136]> <04902D3FAB4E2A56D0D2F985@JcK-HP8200.jck.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 12 Jan 2016 10:16:09 -0800
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9WjyD-1_AK3M738rw3U2DedM9zg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Jan 2016 18:17:06 -0000

At 9:24 AM -0500 1/12/16, John C Klensin wrote:

>  But that gets back to an example of the same old set of
>  tradeoffs --and my desire that those involved in the process be
>  a lot more transparent about it.  Your comment above is
>  reasonable and even obvious.  But there are cities (apparently
>  including Buenos Aires) where there are approximately zero
>  hotels that have enough rooms to give us an 800 or 900 room
>  block.
>
>  So, would you propose a hard rule of "stop considering any city
>  unless we could got a room block of at least N rooms", with N
>  somewhere in the range of 800 or 900?   Unlike the variety of
>  more subjective rules, it would be very clear and easy to
>  interpret.    My assumption about IETF 95 is that, despite
>  understanding and considering the disadvantages of smaller
>  hotels, the decision-makers believed they had a sufficient "go
>  to Buenos Aires" mandate to override hotel or room block size
>  considerations.  I presume that, for the future, we could change
>  that if we had consensus that, e.g., minimum room block size was
>  a firm requirement.

I'm not fond of hard rules, and would be fine if we had some clear 
information as to why this city was chosen despite the room block 
issue.  Which of course is an example of your calls for transparency. 
Maybe a semi-rigid rule that can be overridden with good cause (sort 
of a SHOULD rather than a MUST)?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Secrecy is as essential to Intelligence as vestments and
incense to a Mass, or darkness to a Spiritualist seance, and
must at all costs be maintained, quite irrespective of whether
or not it serves any purpose.             --Malcolm Muggeridge