Re: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)
John C Klensin <john@jck.com> Thu, 17 December 2015 19:27 UTC
Return-Path: <john@jck.com>
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 190AB1A8946 for <ietf@ietfa.amsl.com>; Thu, 17 Dec 2015 11:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gvGMVlmdd51Q for <ietf@ietfa.amsl.com>; Thu, 17 Dec 2015 11:27:12 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 563D51A88CB for <ietf@ietf.org>; Thu, 17 Dec 2015 11:27:12 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1a9eCj-0002Qz-PH; Thu, 17 Dec 2015 14:27:09 -0500
Date: Thu, 17 Dec 2015 14:27:04 -0500
From: John C Klensin <john@jck.com>
To: dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)
Message-ID: <FA905E0564B6E47B70076F92@JcK-HP8200.jck.com>
In-Reply-To: <5672E4BB.2050702@dcrocker.net>
References: <076c01d138e7$0a68dba0$1f3a92e0$@olddog.co.uk> <5672E4BB.2050702@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3DnBAdd9_O4p7Q-Mviom6b3oa8g>
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: Thu, 17 Dec 2015 19:27:16 -0000
--On Thursday, December 17, 2015 08:37 -0800 Dave Crocker <dhc@dcrocker.net> wrote: >> But it wold be useful thought experiment for them all to >> examine how their weeks would be different if they had a 20 >> minute walk each way each day. > > > Effort to get decision-makers to have better empathy for the > rank-and-file is certainly useful. The challenge is to make > the effort practical and sufficient. By 'sufficient' I mean it > has to cover enough of the core issues in ways that work. > > In this case, hotel choice is only part of the equation. > Travel time and travel cost are two other major factors. So > are additional costs, such as food in the main venue. (We had > one main venue with reasonable hotel room rate but US$ 25 > hamburgers...) Hi. Having proposed this particular experiment, I agree with Dave. It is only part of the issue, perhaps even the most important part. but has the advantage that pain-sharing is relatively easy to test and perhaps symbolically important. Because several of the responses have been from IESG members, let me be clear that, as a sometime IESG and IAB member, I found it a huge advantage, one that I think improved IETF efficiency, to be able to stagger into a 7AM meeting (especially the second or third of the week) by getting into an elevator rather than walking down the street, even more so if it followed an evening meeting or bar BOF than ran past midnight. My objection isn't really to making those "hold back" arrangements, it is to the combination of enough regular controversies about hotels and meeting locations with having the decisions made out of community view and with no apparent accountability. I think it would be entirely reasonable for the IESG to say to the community "we need to be on-site because... and believe that IETF efficiency would suffer if we weren't". Personally, I'd probably support that position. But these discussions have gone on long enough that it is probably time for the community to decide whether the value of that improved efficiently is worth lowering the chances of other participants who want to be in the conference hotel doing so by whatever part of 28% the IESG involves. I'd like to believe that, it the community said "it is more important for you folks to share the pain" that the IESG would respect that decision and that, if the community believed that having the IESG in the meeting hotel was important, some of the whining would stop. But there is no way to know without asking and the current system avoids asking. I'm not certain the same argument about the importance to the community of being in the main hotel can be made for all of the members of the IAOC. If they need that consideration, let them explain why to the community and then ask. Personally, I believe that a great deal of the source of these regular disconnects and complaints is a perception about lack of accountability and responsiveness of the IAOC and Meetings Committee. With "3 years" and "confidential business arrangements" figuring prominently in the situation (whether actually justified or not), this is not a good community to tell things that amount to "we have your best interests in mind and are not going to explain further". I note that some IAOC and Meetings Committee members have tried really hard to be good about this, but the overall record does not appear to me to be so good and I consider it a bad sign that we keep having the same discussions over and over again without discernable change or real community conclusions. Similarly, I have no doubt that having some secretariat staff in the main hotel is absolutely necessary. My impression is that AMS has been hyper-careful to not abuse that requirement and I trust them to continue to exercise good judgment about it. But a bit of explanation of who (by either role or name) needs to be in the conference hotel and why, would, OMO, do a lot to build general confidence. FWIW, 28% of only 400+ rooms feels like a rather big number. Had Ray said "5%", it wouldn't have occurred to ma to propose that particular exercise. best, john
- RE: IETF hotel selection mode and a proposal (was… Adrian Farrel
- Re: IETF hotel selection mode and a proposal (was… Stephen Farrell
- Re: IETF hotel selection mode and a proposal (was… Dave Crocker
- Re: IETF hotel selection mode and a proposal (was… Kathleen Moriarty
- Re: IETF hotel selection mode and a proposal (was… Alia Atlas
- RE: IETF hotel selection mode and a proposal (was… Christian Huitema
- Re: IETF hotel selection mode and a proposal (was… Alia Atlas
- Re: IETF hotel selection mode and a proposal (was… John C Klensin
- Re: IETF hotel selection mode and a proposal (was… Ole Jacobsen
- Re: IETF hotel selection mode and a proposal (was… Dave Crocker
- Re: IETF hotel selection mode and a proposal (was… John Levine
- Re: IETF hotel selection mode and a proposal (was… Christian Hopps
- RE: IETF hotel selection mode and a proposal (was… MAISONNEUVE, JULIEN (JULIEN)
- RE: IETF hotel selection mode and a proposal (was… Ole Jacobsen
- Re: IETF hotel selection mode and a proposal (was… Behcet Sarikaya
- Re: IETF hotel selection mode and a proposal (was… Lou Berger
- Re: IETF hotel selection mode and a proposal (was… Randall Gellens
- Re: IETF hotel selection mode and a proposal (was… John Levine
- Re: IETF hotel selection mode and a proposal (was… John C Klensin
- Re: IETF hotel selection mode and a proposal (was… Eliot Lear
- Re: IETF hotel selection mode and a proposal (was… Randall Gellens
- Re: IETF hotel selection mode and a proposal (was… John C Klensin
- Re: IETF hotel selection mode and a proposal (was… Randall Gellens