Re: [rgchairs] Re: 63rd IETF Agenda - DRAFT

Jari Arkko <jari.arkko@piuha.net> Thu, 14 July 2005 13:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt3yw-00072V-Jl; Thu, 14 Jul 2005 09:42:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dsycy-0001eH-6q for rgchairs@megatron.ietf.org; Thu, 14 Jul 2005 03:59:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15026 for <rgchairs@irtf.org>; Thu, 14 Jul 2005 03:59:25 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dsz5U-0005LH-RG for rgchairs@irtf.org; Thu, 14 Jul 2005 04:28:59 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id D795889879; Thu, 14 Jul 2005 10:59:10 +0300 (EEST)
Message-ID: <42D61B5C.4020603@piuha.net>
Date: Thu, 14 Jul 2005 10:59:24 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andrew Newton <andy@hxr.us>
Subject: Re: [rgchairs] Re: 63rd IETF Agenda - DRAFT
References: <1AA39B75171A7144A73216AED1D7478D6CE8FE@esebe100.NOE.Nokia.com> <E4A1E5F3-EDB0-4CD2-B752-54C92B582E9E@hxr.us> <20050713181140.GA889@boskop.local> <F1EF19D3-211C-4A1B-8DC0-1308FF36F84C@hxr.us>
In-Reply-To: <F1EF19D3-211C-4A1B-8DC0-1308FF36F84C@hxr.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 14 Jul 2005 09:42:28 -0400
Cc: wgchairs@ietf.org, rgchairs@irtf.org, bofchairs@ietf.org
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IRTF research group chairs list <rgchairs.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rgchairs>
List-Post: <mailto:rgchairs@lists.ietf.org>
List-Help: <mailto:rgchairs-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=subscribe>
Sender: rgchairs-bounces@lists.ietf.org
Errors-To: rgchairs-bounces@lists.ietf.org

>>> And when meetings are held in places like Paris, some people are
>>> under considerable pressure not to give the appearance of a
>>> boondoggle.
>>
The selection of a proper meeting site is a delicate decision.
Some of the main requirements for organizing a meeting
include:

 o  Conveniently located site, within a short drive from both US west
     and east coasts, Europe, and most of Asia, with reserved
     parking near the registration desk for everyone.

 o  Proper balance between services for work related
     purposes and recreational possibilities.  The key problem
     here is getting your manager to approve a trip to the IETF.
     For this to happen, the manager needs to have a vision of
     everyone working very hard and not even peeking outside.
     This is not likely if the destination is, say, Hawaiji.  On the
     other hand, the participants are not immune to enjoying
     good weather, food, or scenery.

     In order to solve this, the secretariat is negotiating with the
     city of Paris, France about changing the name of one of their
     suburbs to "Minneapolis" and holding our meetings there
     on a regular basis.  This would be a win-win change for
     everyone: travel gets approved, the participants concentrate
     only on work in any case, but they get to do it in a warm
     place and eat well.

 o  No meetings will be held during any religious holiday or during
     national holidays, all religions and nations considered.  (As a
     result, the next seven meetings all need to be held on January
     6th, 2006, as no other dates are available.)

 o  The meeting fees can raise the bar for participants without the
     backing of a major corporation.  On the other hand, the fees
     generate income necessary for the IETF to operate.  One option
     that has been considered for this problem is to create a new
     meeting fee category for Tourists.  The fee would be the same as
     for other participants, but it would not entitle for actual
     entrance to the meeting, reducing congestion in the meeting rooms.
     Initial marketing research among Tourists indicates that this new
     category would be attractive, as long as their managers would
     still approve their trip to "Minneapolis".

     Another experiment that has been planned is the creation of an
     "accommodation included" meeting fee option.  This would allow
     low-budget travel for our academic participants, with the
     accommodation arranged in the meeting rooms.  The only remaining
     problem is determining how to wake these participants up before
     the meeting starts, so that they go from their "night" sleep to
     "not an interesting draft" nap.


_______________________________________________
Rgchairs mailing list
Rgchairs@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/rgchairs