[rgchairs] RE: 65th IETF - WG/RG/BOF Scheduling

Black_David@emc.com Sat, 28 January 2006 18:57 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2vGO-0003rj-Kv; Sat, 28 Jan 2006 13:57:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eys8v-0001nc-GM; Tue, 17 Jan 2006 09:49:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20974; Tue, 17 Jan 2006 09:47:39 -0500 (EST)
From: Black_David@emc.com
Received: from mexforward.lss.emc.com ([168.159.213.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EysH3-0003Ay-Gi; Tue, 17 Jan 2006 09:57:30 -0500
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0HEmjXs012417; Tue, 17 Jan 2006 09:48:45 -0500 (EST)
Received: from MAHO3MSX2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32]) by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id k0HEmf65027296; Tue, 17 Jan 2006 09:48:43 -0500 (EST)
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id <CKRHWS7X>; Tue, 17 Jan 2006 09:48:40 -0500
Message-ID: <F222151D3323874393F83102D614E055013E9066@CORPUSMX20A.corp.emc.com>
To: agenda@ietf.org
Date: Tue, 17 Jan 2006 09:48:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.1.0.0, Antispam-Data: 2006.01.17.055104
X-PerlMx-Spam: Gauge=, SPAM=1%, Reasons='EMC_FROM_00+ -3, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-Mailman-Approved-At: Sat, 28 Jan 2006 13:57:28 -0500
Cc: wgchairs@ietf.org, rgchairs@irtf.org, bofchairs@ietf.org
Subject: [rgchairs] RE: 65th IETF - WG/RG/BOF Scheduling
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

Ditto - as chair of 3 WGs, 2 conflict slots are taken immediately
to avoid trying to run two meetings at once, and 1 remaining conflict
slot is nowhere near enough.  My past meeting requests have run 6-10
conflicts that MUST be avoided plus about that many that SHOULD be
avoided (can be tolerated, but are rather undesirable).

Thanks,
--David

> -----Original Message-----
> From: wgchairs-bounces@ietf.org 
> [mailto:wgchairs-bounces@ietf.org] On Behalf Of Lars Eggert
> Sent: Tuesday, January 17, 2006 8:34 AM
> To: IETF Agenda
> Cc: Working Group Chairs; rgchairs@irtf.org; bofchairs@ietf.org
> Subject: Re: 65th IETF - WG/RG/BOF Scheduling 
> 
> On Jan 17, 2006, at 1:13, IETF Agenda wrote:
> > Please submit requests to schedule your Working Group sessions  
> > using the "IETF Meeting Session Request Tool," a Web-based 
> tool for  
> > submitting all of the information that the Secretariat requires to  
> > schedule your sessions.
> 
> Is there a reason why we can enter only 3 WG conflicts? DCCP had  
> listed a lot more than that in the past.
> 
> Lars
> --
> Lars Eggert                                     NEC Network 
> Laboratories
> 
> 

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