Re: Venue selection (Re: Options for IETF administrative restructuring)

Iljitsch van Beijnum <iljitsch@muada.com> Mon, 30 August 2004 09:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03361; Mon, 30 Aug 2004 05:04:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1i6p-0006PX-IW; Mon, 30 Aug 2004 05:05:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1i0z-0003rk-Iq; Mon, 30 Aug 2004 04:59:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C1hzh-0003c5-8s for ietf@megatron.ietf.org; Mon, 30 Aug 2004 04:58:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02994 for <ietf@ietf.org>; Mon, 30 Aug 2004 04:58:26 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1i1Q-0006FR-SP for ietf@ietf.org; Mon, 30 Aug 2004 05:00:17 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1]) by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i7U90OJZ009882; Mon, 30 Aug 2004 11:00:24 +0200 (CEST) (envelope-from iljitsch@muada.com)
In-Reply-To: <0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
References: <412D268D.3020402@thinkingcat.com> <00a301c48e04$dcac4fb0$3220dfa9@consulintel.es> <0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <BA6FFF85-FA62-11D8-9464-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 30 Aug 2004 10:58:14 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Venue selection (Re: Options for IETF administrative restructuring)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit

On 30-aug-04, at 9:29, Harald Tveit Alvestrand wrote:

> The subject of continent selection is, BTW, one of the real touchy 
> ones; my statistics show that in the North American contingent, the 
> attendance is cut in half when we meet outside North America; in the 
> Asian contingent, the attendance from the host country quadruples or 
> more when we meet in their country, while Europeans show more steady 
> attendance statistics.

Are you sure about this? The number of attendees in Vienna was a bit 
higher than in Minneapolis last year. I also ran into a much larger 
contingent of fellow countrymen in Vienna. (Don't look too far in the 
past as you can't compare the 2000+ attendees of a few years ago with 
the 1500- ones now, I'd assume the people who still come are more 
loyal.)

Also, it's not just about the continent. I find the US somewhat 
visitor-unfriendly in places like Minneapolis, and very much so on the 
international airports of larger cities. I would very much like to see 
a meeting in North America but outside the US.

> I think the organizer needs to be able to make these tradeoffs in real 
> time, and without going back to the IETF for a consensus process on 
> individual meetings - but we do need to have our criteria right out in 
> the open.

> I would prefer to split the process into two rather independent parts: 
> One (open) that sets the criteria, and one (subcontracted) that 
> attempts to find sites that fulfil the criteria. Then we can evaluate 
> the result - for economics, for venue performance, for sponsor 
> satisfaction (that too matters!), and for "fairness".

> As to how to achieve all that.... I'm not at all sure.

Speaking as someone who has to pay for going to IETF meetings out of 
his own pocket and as someone who has been trying to muster up some 
enthusiasm to host a meeting, I'm not all that happy about the way 
things are going now. I'll concentrate on the second role for now.

First of all, I'm not surprised it has been getting harder to find 
sponsors. There are two main reasons for that: the duties of the 
sponsor are solely defined by what's convenient for the people who 
organize the meetings on behalf of the IETF (I'm assuming Foretec and 
the secretariat but I can't be sure). This means the prospective host 
is left with a plethora of duties, some of which are easily solved with 
money (which some sponsors have), others with manpower (which some 
sponsors have) and others with some very specific knowledge (which some 
sponsors have). However, few sponsors are going to have all three.

Also, the process is completely un-transparent both from the view of 
the attendee and from the view of the would-be host.

Last but not least, the people who handle this on the IETF side really 
don't seem to care. For instance, for the past year I've been trying to 
get an answer to the following questions:

> Can you provide me with the current numbers that are relevant to 
> hosting the terminal room (and the social event) for an IETF meeting? 
> And which are the upcoming meetings for which there is no location 
> determined yet?

(Ok, I've only sent four or so messages, but still.) All of this makes 
it hard to create enthusiasm within prospective host organizations.

I think it's essential to start publishing the following information on 
a regular basis:

- meeting status: decided, under consideration, open
- date specific constraints, such as the continent that has been 
selected
- up to date numbers for hotel rooms, meeting rooms, terminal room and 
so on


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf