[rgchairs] Re: 63rd IETF Agenda - DRAFT

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dsf6q-0005UE-VH; Wed, 13 Jul 2005 07:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dsf6p-0005QD-Iy for rgchairs@megatron.ietf.org; Wed, 13 Jul 2005 07:08:59 -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 HAA26380 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 07:08:56 -0400 (EDT)
Received: from mtagate1.uk.ibm.com ([195.212.29.134]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsfZC-0003U4-N9 for rgchairs@irtf.org; Wed, 13 Jul 2005 07:38:20 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate1.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j6DB8dJP170172 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 11:08:40 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j6DB8duO280550 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 12:08:39 +0100
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j6DB8doL001285 for <rgchairs@irtf.org>; Wed, 13 Jul 2005 12:08:39 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j6DB8cOK001275; Wed, 13 Jul 2005 12:08:38 +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 NAA58420; Wed, 13 Jul 2005 13:08:37 +0200
Message-ID: <42D4F637.2040709@zurich.ibm.com>
Date: Wed, 13 Jul 2005 13:08:39 +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: Thierry Ernst <ernst@sfc.wide.ad.jp>
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> <732ADB16-A6DF-42F8-B194-943F7B89B06F@netlab.nec.de> <20050713164855.3b596465.ernst@sfc.wide.ad.jp>
In-Reply-To: <20050713164855.3b596465.ernst@sfc.wide.ad.jp>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Cc: Lars Eggert <lars.eggert@netlab.nec.de>, wgchairs@ietf.org, 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

Actually, not.

Firstly there's nothing "guinea pig" about the Friday morning
slots. They've been in regular use for years:

FRIDAY, August 4, 2000
	  	
0800-1000 IETF Registration - South Hall, The Center
0800-0900 Continental Breakfast - The Center
0900-1130 Morning Sessions  	  	  	  	  	  	
South Rm 11/12 APP beep Blocks Extensible Exchange Protocol WG
South Rm 7     APP wrec Web Replication and Caching WG
North Rm 7/12  INT ipoptr IP over Packet Transport Rings BOF *
South Rm 2     OPS snmpconf Configuration Management with SNMP WG
South Rm 10    RTG gsmp General Switch Management Protocol WG
South Rm 9     SEC idwg Intrusion Detection Exchange Format WG
North Rm 1/6   SEC ipsp IP Security Policy WG
South Rm 4     TSV rohc Robust Header Compression WG *

Secondly, it's important that BOFs are spread out over the week.
For the IESG and IAB, being sure that all BOFs are covered by both
IAB and IESG memebers is a key element of our IETF week: BOFs are
where the constituency for new work is evaluated, and IAB and IESG
members need to be there. That's not consistent with concentrating
BOFs on one half day.

     Brian

Thierry Ernst wrote:
> Actually, this is an excellent idea !
> Thierry
> 
> On Wed, 13 Jul 2005 09:00:47 +0200
> Lars Eggert <lars.eggert@netlab.nec.de> wrote:
> 
> 
>>Hi,
>>
>>On 2005-7-13, at 3:49 , Thierry Ernst wrote:
>>
>>>It's notorious that people try to arrange their flight in advance in
>>>order to get cheaper prices, so if we really want people to organize
>>>their trip in a way they consider staying on Friday, we:
>>>1. must issue a draft agenda earlier (I would say 1 month in  
>>>advance at
>>>the very least
>>>2. in case of agenda changes, no slot should be move to the  
>>>extremity of
>>>the week
>>>3. people should get used to stay on Friday
>>>
>>>The problem for 3 is that some WGs have to play the role of
>>>guinea-pig and this is not acceptable. So, 1 and 2 may be the 1st
>>>category's requirement. May be one eaay way is for some WGs to
>>>volunteer for a Friday BOF ahead of time, with the information
>>>spread on the relevant mailing lists.
>>>
>>>A side note, I think it's a bad idea to schedule a BOF on Friday  
>>>because
>>>many people are not aware of the content of a BOF before they
>>>attend; also BOF need to span a larger audience.
>>
>>If you want to achieve (3), which is the right thing to do IMO, then  
>>let's make Friday "BOF day" in Vancouver, announce it well before and 
>>schedule all BOFs then. (Or the IETF after Vancouver if that's too  
>>soon.)
>>
>>Lars
>>-- 
>>Lars Eggert                                     NEC Network
>>Laboratories
>>
>>
> 
> 


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