Re: IETF 62
Lars Eggert <lars.eggert@netlab.nec.de> Mon, 20 September 2004 11:53 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 HAA23529; Mon, 20 Sep 2004 07:53:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9Mpc-000410-6c; Mon, 20 Sep 2004 07:59:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9Maa-0006rQ-Ni; Mon, 20 Sep 2004 07:44:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9MXO-0006Mp-SS for ietf@megatron.ietf.org; Mon, 20 Sep 2004 07:40: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 HAA22902 for <ietf@ietf.org>; Mon, 20 Sep 2004 07:40:53 -0400 (EDT)
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9MdX-0003nb-LU for ietf@ietf.org; Mon, 20 Sep 2004 07:47:16 -0400
Received: from [10.1.1.112] (dummy.netlab.nec.de [195.37.70.40]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 5D0BB1BAC4D; Mon, 20 Sep 2004 13:40:22 +0200 (CEST)
Message-ID: <414EC19E.5070609@netlab.nec.de>
Date: Mon, 20 Sep 2004 13:40:14 +0200
From: Lars Eggert <lars.eggert@netlab.nec.de>
Organization: NEC Network Laboratories
User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <20040911210653.A62C48958A@newdev.harvard.edu> <012c01c49b03$ef7f21b0$0400a8c0@DFNJGL21> <3744.1095366813@marajade.sandelman.ottawa.on.ca> <20040917082340.GC11438@login.ecs.soton.ac.uk> <20040917085228.GA1019@danisch.de> <20040917121521.63fcf133@chardonnay> <16715.9211.456204.708279@saint.heaven.net> <414BE4F9.3020503@netlab.nec.de> <tslllf5bx7t.fsf@cz.mit.edu> <414E7EA0.1020409@netlab.nec.de> <086DEF6FF9C4B05CFC8D3455@scan.jck.com>
In-Reply-To: <086DEF6FF9C4B05CFC8D3455@scan.jck.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: Sam Hartman <hartmans@mit.edu>, 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>
Content-Type: multipart/mixed; boundary="===============1677247330=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
John, John C Klensin wrote: > > 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. good point, and a valid concern. One of the advantages of going to a touristy place - or the hub of a major airline - is inexpensive airfare and maybe decreased travel time due to the higher likelihood of direct fligths. But I agree, it's a tradeoff. Lars -- Lars Eggert NEC Network Laboratories
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- first steps (was The other parts of the report...) scott bradner
- Re: first steps (was The other parts of the repor… Harald Tveit Alvestrand
- Re: first steps (was The other parts of the repor… scott bradner
- Re: first steps (was The other parts of the repor… Margaret Wasserman
- Re: first steps (was The other parts of the repor… John C Klensin
- RE: first steps (was The other parts of the repor… Steve Crocker
- RE: first steps (was The other parts of the repor… Wijnen, Bert (Bert)
- Re: first steps (was The other parts of the repor… Carl Malamud
- What we need done (Re: first steps (was The other… Harald Tveit Alvestrand
- Re: first steps (was The other parts of the repor… John C Klensin
- Re: What we need done (Re: first steps (was The o… avri
- Re: first steps (was The other parts of the repor… Dave Crocker
- Re: first steps (was The other parts of the repor… Harald Tveit Alvestrand
- Re: first steps (was The other parts of the repor… Harald Tveit Alvestrand
- Re: first steps (was The other parts of the repor… Dave Crocker
- RE: first steps (was The other parts of the repor… graham.travers
- RE: first steps (was The other parts of the repor… graham.travers
- RE: first steps (was The other parts of the repor… Steve Crocker
- RE: first steps (was The other parts of the repor… Joel Jaeggli
- IETF 62 (was: Re: first steps) Spencer Dawkins
- Re: IETF 62 (was: Re: first steps) shogunx
- Re: IETF 62 (was: Re: first steps) Michael Richardson
- Re: IETF 62 (was: Re: first steps) Michael Richardson
- Re: IETF 62 (was: Re: first steps) Tim Chown
- Re: IETF 62 (was: Re: first steps) william(at)elan.net
- Re: IETF 62 (was: Re: first steps) Hadmut Danisch
- Re: IETF 62 (was: Re: first steps) Henrik Levkowetz
- Re: IETF 62 (was: Re: first steps) Dick St.Peters
- Re: IETF 62 Lars Eggert
- Re: IETF 62 Sam Hartman
- Re: IETF 62 Lars Eggert
- Re: IETF 62 John C Klensin
- Re: IETF 62 Lars Eggert
- Re: IETF 62 (was: Re: first steps) Mark Allman
- RE: Meeting locations (was IETF 62) Robin Uyeshiro
- Re: IETF 62 Scott Michel
- Re: IETF 62 Michael D Frisch
- Re: IETF 62 Ted Faber