[OPS-AREA] (no subject)

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 07 September 2010 14:29 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D23F43A6918; Tue, 7 Sep 2010 07:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.612
X-Spam-Level:
X-Spam-Status: No, score=-101.612 tagged_above=-999 required=5 tests=[AWL=-0.775, BAYES_00=-2.599, MISSING_SUBJECT=1.762, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTbkeZiyG5kj; Tue, 7 Sep 2010 07:29:16 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 970B63A6903; Tue, 7 Sep 2010 07:29:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,328,1280721600"; d="scan'208";a="33435532"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Sep 2010 10:29:43 -0400
X-IronPort-AV: E=Sophos;i="4.56,328,1280721600"; d="scan'208";a="508062233"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Sep 2010 10:29:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 07 Sep 2010 16:28:51 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040251DCD5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Index: ActOmP4xp7nnphw3TWO1o4ScP7FV9w==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: ops-chairs@ietf.org, ops-area@ietf.org, ops-dir@ietf.org
Subject: [OPS-AREA] (no subject)
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 14:29:17 -0000

Important dates for the Beijing IETF: 

2010-09-13 (Monday): Cutoff date for BOF proposal requests to Area
Directors at 17:00 PT (24:00 UTC). To request a BOF, please see
instructions on Requesting a BOF. 
2010-09-27 (Monday): Cutoff date for requests to schedule Working Group
meetings at 17:00 PT (24:00 UTC). To request a Working Group session,
use the IETF Meeting Session Request Tool. 
2010-09-27 (Monday): Cutoff date for Area Directors to approve BOFs at
17:00 PT (24:00 UTC). 
2010-10-06 (Wednesday): Preliminary agenda published for comment. 
2010-10-11 (Monday): Cutoff date for requests to reschedule Working
Group and BOF meetings 17:00 PT (24:00 UTC). 
2010-10-11 (Monday): Working Group Chair approval for initial document
(Version -00) submissions appreciated by 17:00 PT (24:00 UTC). 
2010-10-15 (Friday): Final agenda to be published. 
2010-10-18 (Monday): Internet Draft Cut-off for initial document (-00)
submission by 17:00 PT (24:00 UTC), upload using IETF ID Submission
Tool. 
2010-10-25 (Monday): Internet Draft final submission cut-off by 17:00 PT
(24:00 UTC), upload using IETF ID Submission Tool. 
2010-10-27 (Wednesday): Draft Working Group agendas due by 17:00 PT
(24:00 UTC), upload using IETF Meeting Materials Management Tool. 
2010-11-01 (Monday): Revised Working Group agendas due by 17:00 PT
(01:00 Tuesday, November 02 UTC), upload using IETF Meeting Materials
Management Tool. 

Note that the first two cutoff dates (BOF requests, WG meetings
scheduling) are very close. 

Also, although the draft WG agendas are required later in the process we
strongly prefer that all OPS WGs submit draft agendas together with the
request to schedule meetings.

Regards,

Ron and Dan