RE: Meeting locations (was IETF 62)

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Mon, 20 September 2004 22:10 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 SAA27709; Mon, 20 Sep 2004 18:10:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9WSi-0003kj-Gw; Mon, 20 Sep 2004 18:16:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9WKU-0001vF-NJ; Mon, 20 Sep 2004 18:08:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9WFa-0007Og-9p for ietf@megatron.ietf.org; Mon, 20 Sep 2004 18:03:10 -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 SAA26788 for <ietf@ietf.org>; Mon, 20 Sep 2004 18:03:07 -0400 (EDT)
Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9WLp-0003d0-2A for ietf@ietf.org; Mon, 20 Sep 2004 18:09:37 -0400
Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i8KM1NZp022980 for <ietf@ietf.org>; Mon, 20 Sep 2004 18:01:23 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i8KM0aZp022136 for <ietf@ietf.org>; Mon, 20 Sep 2004 18:00:52 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Sep 2004 01:01:53 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E2FED8@is0004avexu1.global.avaya.com>
Thread-Topic: Meeting locations (was IETF 62)
Thread-Index: AcSfWvMSxCGflOO5QEGedfuYOnj7MQAARO3A
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Robin Uyeshiro" <uyeshiro@ifa.hawaii.edu>, "John C Klensin" <john-ietf@jck.com>, "Lars Eggert" <lars.eggert@netlab.nec.de>, "Sam Hartman" <hartmans@mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: Meeting locations (was IETF 62)
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: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable

You are correct if you refer to the participation numbers in last couple of meetings. Historically IEEE 802 Plenaries have been much smaller in size than the IETF meetings. I believe that by the time when the Hilton Head and Kauai meetings were hold (2001, 2002), the IEEE plenaries were gathering around 1000 attendees, while the IETF meetings were about the double size. It' s only at the last two meetings that IEEE continued to grow in size, while IETF participation decreased, so that the two organizations got to about the same size in participation. 

IEEE 802 Plenaries do not provide a terminals room, but they do wireless networking for the last three years or so. The schedule is roughly the same (Monday through Friday afternoon) and number of meeting rooms they use is higher - maybe double or more than the IETF needs.  

IEEE 802 use the services of an external events organizing company for a few years. 

Regards,

Dan



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On 
> Behalf Of Robin Uyeshiro
> Sent: 20 September, 2004 10:57 PM
> To: 'John C Klensin'; 'Lars Eggert'; 'Sam Hartman'
> Cc: ietf@ietf.org
> Subject: RE: Meeting locations (was IETF 62)
> 
> 
> Would the IEEE 802 Plenaries have comparable geographical/logistical
> requirements to IETF meetings?  Their next few plenaries are scheduled
> in San Antonio, Atlanta, San Francisco, Vancouver, New Orleans, San
> Diego, and Dallas.  All but one are in the US, and all are in North
> America.  
> 
> I attended one plenary at Hilton Head, and talked to people about
> another held on Maui, both resort areas.  This was before the crash,
> though, so perhaps money is tighter now.
> 
> I'm not advocating doing the same thing; just thought another 
> data point
> might be helpful.
> 
> http://grouper.ieee.org/groups/802/meeting/future_meetings.html
> 
> -- Robin Uyeshiro
> P.S. Honolulu has a new convention center.  
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of
> John C Klensin
> Sent: Monday, September 20, 2004 12:59 AM
> To: Lars Eggert; Sam Hartman
> Cc: ietf@ietf.org
> Subject: Re: IETF 62
> 
> 
> 
> --On Monday, 20 September, 2004 08:54 +0200 Lars Eggert
> <lars.eggert@netlab.nec.de> wrote:
> 
> >> Secondly, I'm concerned that people are proposing optimizing
> >> for pleasant climate and good vacation spots.  I come to the
> >> IETF to get work done; I'd rather be at meetings where the
> >> other participants have the same goal.  We should be somewhat
> >> careful of optimizing for enjoyable location.  I'd rather see
> >> us optimize for who can attend and cost.
> > 
> > If you have data that shows an inverse proportionality between
> > the enjoyability of past locations and the generated IETF
> > output, please post it.
> 
> Lars,
> 
> I have no idea about actual IETF experience, but, based on
> experience with other organizations and meetings of similar
> technical focus, the key issue is not whether those who go can
> get work done, or even whether some people decide to go it if is
> a nice place.  Rather, it is the tendency of people who have to
> review and approve travel to look at a destination, pronounce
> the words "probable boggle" and then say "no".    And I've seen
> enough situations in which that has occurred to make that a real
> concern.  
> 
> It probably isn't enough of a concern to say "we absolutely
> should, or should not, meet there", but it should be a
> significant consideration.
> 
> On other observation on the US situation.  In the few years, we
> have had a significant problem with participants from some
> countries getting to US meetings at all due to increasing
> scrutiny of visa applications and consequent difficulties in
> getting visas.  Sometimes, those delays have been equivalent to
> visa denial, even when no formal denial occurs.  Those
> restrictions are qualitatively different from, e.g., the
> fingerprint issue, since they prevent someone from even making
> the decision as to whether they are willing to put up with the
> marginal aggravation and intrusion to attend.  Classes of IETF
> participants are excluded entirely depending on their
> nationality or normal residency, and that has a direct on IETF
> openness and global participation.
> 
> That is, fwiw, I've been suggesting that we reduce the focus on
> meetings in the US for a few years now.  As others have pointed
> out, doing that isn't quite as easy as would appear to be the
> case at first glance but, IMO, we should keep trying.
> 
>    regards,
>      john
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

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