Re: Hotel situation

John C Klensin <john-ietf@jck.com> Tue, 05 January 2016 13:28 UTC

Return-Path: <john-ietf@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 41ED51A6FFA for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2016 05:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 w1hx7r2ZeFmD for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2016 05:28:31 -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 C3A9D1A6FA3 for <ietf@ietf.org>; Tue, 5 Jan 2016 05:28:31 -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-ietf@jck.com>) id 1aGRf0-000NrG-K2; Tue, 05 Jan 2016 08:28:26 -0500
Date: Tue, 05 Jan 2016 08:28:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Mary Barnes <mary.h.barnes@gmail.com>, Eric Gray <eric.gray@ericsson.com>
Subject: Re: Hotel situation
Message-ID: <7E1588330F38B7D9A45B189E@JcK-HP8200.jck.com>
In-Reply-To: <568B89BD.1040008@gmail.com>
References: <567192F3.9090506@gmail.com> <8D23D4052ABE7A4490E77B1A012B630797A09BC1@mbx-03.WIN.NOMINUM.COM> <48E1A67CB9CA044EADFEAB87D814BFF6449900E0@eusaamb107.ericsson.se> <CABmDk8n2TFvmoMVa8t3FOGXtKF9GUii=wrEyMpJucAoLzCix1Q@mail.gmail.com> <D38CB535C27A8E9D7B77BC2F@JcK-HP8200.jck.com> <568B89BD.1040008@gmail.com>
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-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/skNEjAVX1m0GjPK_TeTMuNwqir0>
Cc: IETF Discussion <ietf@ietf.org>
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, 05 Jan 2016 13:28:33 -0000


--On Tuesday, January 05, 2016 09:15 +0000 Stewart Bryant
<stewart.bryant@gmail.com> wrote:

> On 04/01/2016 21:33, John C Klensin wrote:
>> (1) While it is clear that people who favor going back to
>> Minneapolis are in the minority of the Meetings Committee (at
>> least as they and the IAOC count votes), it is much less clear
>> that such people are in the minority of active participants in
>> the IETF.

> Minneapolis is really a metaphor for functional, works well
> for most people, easy to get flights and hotels, flight times
> not too bad, not regarded as a holiday trip at work, everyone
> is there to work.

> It does not have to be Minneapolis, but the utilitarian
> properties above, are in my view far more relevant than the
> IETF World Tour model we seem to have in place.

Agreed.  But Minneapolis is, in one way, not just a metaphor.
Especially as we start discussing "go back to the same places
every year" again, Minneapolis was a place we went to multiple
times and found successful (for the reasons you give).  Then we
stopped.  There has never been an explanation to the community
as to why we stopped, but there have been rumors that someone
had a bad experience (whether with the weather, the hotel, or
something else), vowed that we would never go back there, and
apparently was in a position to implement that vow.  Rumors like
that are unfortunate, but can be seen as symptoms of the
failures of the Meeting Committee and IAOC to communicate
clearly and openly with the community about these issues and
decisions.

     john