Re: IETF 62
Melinda Shore <mshore@cisco.com> Mon, 20 September 2004 13:34 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 JAA02008; Mon, 20 Sep 2004 09:34:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9OPl-00064M-Dx; Mon, 20 Sep 2004 09:41:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9OGF-0006Xu-Cw; Mon, 20 Sep 2004 09:31:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9OAz-0005m5-RM for ietf@megatron.ietf.org; Mon, 20 Sep 2004 09:25:54 -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 JAA01436 for <ietf@ietf.org>; Mon, 20 Sep 2004 09:25:52 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9OHA-0005ug-44 for ietf@ietf.org; Mon, 20 Sep 2004 09:32:16 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 20 Sep 2004 06:27:12 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8KDPH7Y004875; Mon, 20 Sep 2004 06:25:18 -0700 (PDT)
Received: from cisco.com ([10.25.65.179]) by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with SMTP id AZE19578; Mon, 20 Sep 2004 06:25:18 -0700 (PDT)
Date: Mon, 20 Sep 2004 09:24:52 -0400
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v553)
To: hadi@cyberus.ca
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <1095682615.1048.221.camel@jzny.localdomain>
Message-Id: <74224EC5-0B08-11D9-99F9-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: 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: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
On Monday, September 20, 2004, at 08:16 AM, jamal wrote: > So Mineapolis (the mother of all IETF venues) is less bloodier to get > to? I am shocked. I would claim Ottawa is more accessible, colder, > cheaper and doesnt have wimpy tunnels - which makes it a perfect > choice. I think Minneapolis is a terrific venue - the facilities are great, meals are easy, etc. I've hosted a meeting in Ottawa, and while it's also a terrific venue it's not that easy to find facilities that can accommodate a meeting the size of the IETF. Toronto or Montreal would be a better bet in terms of meeting space. I've been denied travel funds to a location that looked too much like a holiday spot, so I'm not much of an advocate for basing location decisions on whether or not I'd enjoy the locale - that can backfire. We've all heard jokes about the European Travel and Sightseeing Institute, right? I used to be heavily involved with Usenix, which has a full-time meeting coordinator whose job is specifically to find and arrange meeting venues. I checked their events page recently and they've got locations for the annual conference pinned down through 2008. Melinda _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: IETF 62 Ben Crosby
- Re: IETF 62 Greg Daley
- Re: IETF 62 Martin Stiemerling
- Re: IETF 62 Ben Crosby
- Re: IETF 62 jamal
- Re: IETF 62 Melinda Shore
- Re: IETF 62 shogunx
- Re: IETF 62 jamal
- Re: IETF 62 Ben Crosby
- Re: IETF 62 Tim Chown
- Re: IETF 62 Ben Crosby
- Re: IETF 62 jamal
- Re: IETF 62 Ben Crosby
- Re: IETF 62 Michael Richardson