[rgchairs] Re: 63rd IETF Agenda - DRAFT

Brian E Carpenter <brc@zurich.ibm.com> Wed, 13 July 2005 09:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsdAC-0001JK-OK; Wed, 13 Jul 2005 05:04:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsdA8-0001Iu-Qc for rgchairs@megatron.ietf.org; Wed, 13 Jul 2005 05:04:18 -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 FAA16565 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 05:04:12 -0400 (EDT)
Received: from mtagate3.uk.ibm.com ([195.212.29.136]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsdcS-0006IK-OP for rgchairs@irtf.org; Wed, 13 Jul 2005 05:33:34 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j6D9435T345322 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 09:04:03 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j6D943uO276920 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 10:04:03 +0100
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j6D942AW031436 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 10:04:03 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j6D942NH031409; Wed, 13 Jul 2005 10:04:02 +0100
Received: from zurich.ibm.com (sig-9-145-249-78.de.ibm.com [9.145.249.78]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA44982; Wed, 13 Jul 2005 11:03:55 +0200
Message-ID: <42D4D8FE.9040905@zurich.ibm.com>
Date: Wed, 13 Jul 2005 11:03:58 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
References: <E1Ds6Ih-000461-Sk@newodin.ietf.org> <20050712185749.1f7f8b85.ernst@sfc.wide.ad.jp> <42D3BEF6.5060804@zurich.ibm.com> <20050713104953.2e5cc8d8.ernst@sfc.wide.ad.jp> <E4A45476A1A5F692EBA00019@sirius.fac.cs.cmu.edu>
In-Reply-To: <E4A45476A1A5F692EBA00019@sirius.fac.cs.cmu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, Thierry Ernst <ernst@sfc.wide.ad.jp>, rgchairs@irtf.org, bofchairs@ietf.org
Subject: [rgchairs] Re: 63rd IETF Agenda - DRAFT
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

I've made a mental note that for future meetings, both the web site
and the announcements need to be much more explicit that working sessions
extend through Friday lunchtime. We have to make sure that anyone who
takes a quick glance and books a ticket is not misled.

    Brian

Jeffrey Hutzelman wrote:
> 
> 
> On Wednesday, July 13, 2005 10:49:53 AM +0900 Thierry Ernst 
> <ernst@sfc.wide.ad.jp> wrote:
> 
>> It's notorious that people try to arrange their flight in advance in
>> order to get cheaper prices,
> 
> 
> There's nothing wrong with doing this.  The dates and locations of IETF 
> meetings (if not always the exact hotel) are announced well in advance. 
> The problem arises when people want to buy tickets far in advance to get 
> the cheaper price _and_ tailor their trip so they are there only for one 
> or two sessions.  The two just aren't compatible, and making them 
> compatible would probably require pushing the whole scheduling process 
> so far out that many WG's wouldn't know whether they need to meet or how 
> much time they need.
> 
> It seems we have this discussion about three times a year, usually on 
> the main IETF list, and the arguments rarely change.  You can consult 
> the archives to see how the discussion generally goes, or I can 
> summarize for you:
> 
> 
> A: Please don't schedule me in <time X>; I'll only be there on <day Y>
> B: We can't schedule meetings around people's flights; you should plan
>   on being there for the entire week of the meeting.
> A: But I only want to be there for my meeting, can't you schedule things
>   earlier so that I can just fly in for my timeslot?
> B: We don't want people to only show up for their one meeting; we want
>   them to stick around, attend other sessions, talk to people, etc.
>   One big strength of the IETF is bringing together people from a wide
>   variety of backgrounds and specialties, and we want to encourage that.
> A: But lots of people don't have the budget to stay for a week, or can't
>   afford the time away, or their employer won't send them.  Aren't we
>   excluding these people?
> B: Yes, but what else can we do without fragmenting the IETF into lots
>   of little isolated groups.  Besides, scheduling is complicated and
>   time-consuming already, making a final agenda early enough would be
>   too hard.
> A: But you should try, because it would be really useful to me.
> B: Lots of WG's won't know that far in advance whether they need to meet
>   or how much time they need.  And we don't care about helping people
>   who aren't going to contribute outside their one WG.
> A: You just want everyone to be forced to come the whole week, and don't
>   care that you're screwing the people who can't do that!
> B: You don't really care about the IETF, you just want to do whatever
>   the hell you feel like doing.
> A: You're a fascist!
> B: You're an anarchist!
> A: You're a Nazi! (*)
> X: OK, so much for that thread, time to move on.
> 
> At this point, the discussion turns to an equally stimulating topic such 
> as whether the IESG has too much power or why last week's major process 
> change hasn't yet resulting in either a dramatic improvement in the time 
> it takes to go form first-draft to full Standard or the complete 
> implosion of the IETF, the Internet, the Universe, or all three.
> 
> 
> Seriously folks, a couple of key points:
> - We are in the middle of an experiment related to changing the timeline
>  for meeting scheduling.  We only do this three times a year, so it is
>  far too soon to have enough data to draw conclusions.  Give it some time.
> 
> - The process of scheduling an IETF meeting is really hard -- much harder
>  than your average conference with several "tracks" of related talks.
>  There are a huge number of constraints, a limited number of rooms and
>  timeslots; there's not much time in which to get the job done, and
>  whatever the outcome, someone will be unhappy.  By all means, point out
>  any conflicts you see, and ask for changes you think might help.  But be
>  prepared to accept that some conflicts are unavoidable, and some changes
>  simply cause too many problems.
> 
> - Marcia and the other folks at the IETF Secretariat who work on this
>  generally do a fabulous job making it all work out.
>  Please cut them some slack.
> 
> -- Jeff
> 
> 
> 
> 
> * see <http://en.wikipedia.org/wiki/Godwin's_law>
> 


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