[xrblock] FW: 86th IETF - Working Group/BOF/IRTF Scheduling

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 11 December 2012 10:29 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5DE21F8622 for <xrblock@ietfa.amsl.com>; Tue, 11 Dec 2012 02:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.712
X-Spam-Level:
X-Spam-Status: No, score=-102.712 tagged_above=-999 required=5 tests=[AWL=-0.512, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0Y92H8Eo0qG for <xrblock@ietfa.amsl.com>; Tue, 11 Dec 2012 02:29:00 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id BCF3021F8625 for <xrblock@ietf.org>; Tue, 11 Dec 2012 02:28:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigLAIbQt1DGmAcF/2dsb2JhbABEgmyDP7hmdBZsB4IeAQEBAQMSERFRBgEIDQQEAQEDAgYLAQIPAwIEHxEUAQYBAQUFBBMIAQsOh1wDDwELnVWEJooqgj+GQg2BF4g9gSKKNWkbcwgGBoIMMmEDlCsBh2KFJ4UQgnKBbDU
X-IronPort-AV: E=Sophos;i="4.84,186,1355115600"; d="scan'208";a="380051646"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 11 Dec 2012 05:20:13 -0500
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Dec 2012 05:26:17 -0500
Received: from AZ-FFEXHC01.global.avaya.com (135.64.58.11) by DC-US1HCEX2.global.avaya.com (135.11.52.37) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 11 Dec 2012 05:28:58 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Tue, 11 Dec 2012 05:28:56 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: 86th IETF - Working Group/BOF/IRTF Scheduling
Thread-Index: AQHN1wHHmDRPAYtvNUKPOi71Made9pgTZawg
Date: Tue, 11 Dec 2012 10:28:56 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA03AB09@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [xrblock] FW: 86th IETF - Working Group/BOF/IRTF Scheduling
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 10:29:01 -0000

Hi,

It's scheduling request time again for IETF-86. 

The experience in Vancouver was that booking only a one hour slot was quite stretchy. My suggestion is to ask for a 1 hour and a half this time. Opinions? 

Also please send us (the chairs) your list of conflicts so that we can ask to be avoided (and as you all know not all requests will be granted). 

Thanks and Regards,

Dan




-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF Agenda
Sent: Monday, December 10, 2012 8:11 PM
To: Working Group Chairs
Cc: irsg@irtf.org
Subject: 86th IETF - Working Group/BOF/IRTF Scheduling

-----------------------------------------------------------------
86th IETF – Orlando, FL, USA
Meeting Dates: March 10-15, 2013
Host: Comcast and NBC Universal
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

We are accepting scheduling requests for all Working Groups, BOFs, and IRTFs starting today.  The milestones and deadlines for scheduling-related activities are as follows:

NOTE: cutoff dates are subject to change.

- 2012-12-10 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool.
- 2013-01-14 (Monday): Cutoff date for requests to schedule Working Group meetings at UTC 24:00. To request a Working Group session, use the IETF Meeting Session Request Tool.
- 2013-01-28 (Monday): Cutoff date for BOF proposal requests to Area Directors at UTC 24:00. To request a BOF, please see instructions on Requesting a BOF.
- 2013-01-31 (Thursday): Cutoff date for Area Directors to approve BOFs at UTC 24:00.
- 2013-02-07 (Thursday): Preliminary agenda published for comment.
- 2013-02-11 (Monday): Cutoff date for requests to reschedule Working Group and BOF meetings UTC 24:00.
- 2013-02-15 (Friday): Final agenda to be published.
- 2013-02-27 (Wednesday): Draft Working Group agendas due by UTC 24:00, upload using IETF Meeting Materials Management Tool.
- 2013-03-04 (Monday): Revised Working Group agendas due by UTC 24:00, upload using IETF Meeting Materials Management Tool.
- 2013-04-12 (Friday): Proceedings submission cutoff date by UTC 24:00, upload using IETF Meeting Materials Management Tool.
- 2013-05-01 (Wednesday): Proceedings submission corrections cutoff date by UTC 24:00, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

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.

The URL for the tool is:

https://pub.ietf.org/sreq/

Please send requests to schedule your BOF sessions to agenda@ietf.org.  Please include the acronym of your BOF in the subject line of the message, and include all of the information specified in item (4) of "Requesting Meeting Sessions at IETF Meetings" in the body.  (This document is included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the agendas for your Working Group sessions as early as possible.  Draft Working Group agendas are due Wednesday, February 27, 2013 at UTC 24:00.  Revised Working Group agendas are due no later than Monday, March 4, 2013 at UTC 24:00.  The proposed agenda for a BOF session should be submitted along with your request for a session.  Please be sure to copy your Area Director on that message.

Please submit the agendas for your Working Group sessions using the "IETF Meeting Materials Management Tool," a Web-based tool for making your meeting agenda, minutes, and presentation slides available to the community before, during, and after an IETF meeting.  If you are a BOF chair, then you may use the tool to submit a revised agenda as well as other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://pub.ietf.org/proceedings/

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the "IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 86 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/86/materials.html

If you are a Working Group chair, then you already have accounts on the "IETF Meeting Session Request Tool" and the "IETF Meeting Materials Management Tool."  The same User ID and password will work for both tools.  If you are a BOF chair who is not also a Working Group chair, then you will be given an account on the "IETF Meeting Materials Management Tool" when your BOF has been approved.  If you require assistance in using either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting sessions at IETF 86 is presented below:

1. Requests to schedule Working Group sessions should be submitted using the "IETF Meeting Session Request Tool," a Web-based tool for submitting all of the information required by the Secretariat to schedule your sessions.  The URL for the tool is:

https://pub.ietf.org/sreq/

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then please send a message to ietf-action@ietf.org.  If you are unable to use the tool, then you may send your request via e-mail to agenda@ietf.org, with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved the BOF. The proponents behind a BOF need to contact a relevant Area Director, preferably well in advance of the BOF approval deadline date. The AD needs to have the full name of the BOF, its acronym, suggested names of chairs, an agenda, full description of the BOF and the information covered in item 4. Please read RFC 5434 for instructions on how to drive a successful BOF effort. The approval depends on, for instance, Internet-Drafts and list discussion on the suggested topic. BOF agenda requests, if approved, will be submitted to the IETF Secretariat by the ADs.

3. A Working Group may request either one or two sessions.  If your Working Group requires more than two sessions, then your request must be approved by an Area Director.  Additional sessions will be assigned, based on availability, after Monday, February 11, 2013, the cut-off date for requests to reschedule a session.

4. You MUST provide the following information before a Working Group or BOF session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets: 

    b. AREA under which Working Group or BOF appears:

    c. CONFLICTS you wish to avoid, please be as specific as possible:

    d. Expected Attendance:

    e. Special requests:

    f. Number of sessions:

    g. Length of session: 
       - 1 hour 
       - 1 1/2 hours
       - 2 hours 
       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors with their e-mail addresses:

IETF Chair
Russ Housley <housley@vigilsec.com> 

Applications Area (app)
Barry Leiba <barryleiba@computer.org>
Pete Resnick <presnick@qualcomm.com>

Internet Area (int)
Ralph Droms <rdroms.ietf@gmail.com>
Brian Haberman <brian@innovationslab.net> 

Operations & Management Area (ops)
Ronald Bonica <rbonica@juniper.net>
Benoit Claise <bclaise@cisco.com> 

Real-time Applications and Infrastructure Area (rai) Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> Robert Sparks <rjsparks@nostrum.com>  

Routing Area (rtg)
Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian@olddog.co.uk>  

Security Area (sec)
Stephen Farrell <stephen.farrell@cs.tcd.ie> Sean Turner <turners@ieca.com>  

Transport Area (tsv)
Wesley Eddy <wes@mti-systems.com>
Martin Stiemerling <martin.stiemerling@neclab.eu>  ===========================================================
85th IETF Meeting Attendance Number

6man - 153
6renum - 30
abfab	47
alto  - 59
apparea (AG) - 122
atoca - 20
avtcore (2nd session) - 60
avtext - 40
bmwg - 34
ccamp (2nd session) - 52
cdni - 54
cdni (2nd session) - 51
certrans - 99
clue - 55
clue (2nd session) - 53
core - 64
core (2nd session) - 50
dhc - 62
dime - 23
dispatch - 53
dtnrg (RG) - 39
ecrit - 36
eman - 44
emu - 25
forces - 44
geopriv - 41
httpauth - 103
httpbis - 85
iccrg (RG) - 81
idr - 62
intarea (AG) - 105
ippm - 56
iri - 26
irs - 291
IRTF Open Meeting - 82
isis - 34
karp - 46
l3vpn - 63
mdnsext - 164
mif - 68
mile - 39
mpls (2nd session) - 79
mptcp - 63
multimob - 21
netext - 46
netmod	 - 41
nvo3 (BoF) - 198
oauth - 65
opsawg - 66
opsec - 45
pce - 74
pcp - 27
pim - 24
pkix - 30
ppsp - 28
radext - 18
rmcat (BoF) - 64
rtcweb (2nd session) - 145
rtgarea (AG) - 72
rtgwg - 113
sacm - 63
sdnrg (RG) - 264
sidr - 65
siprec - 29
softwire - 89
softwire (2nd session) - 79
sunset4 - 142
tcpm - 32
tictoc - 23
tls - 80
trill - 38
tsvarea (AG) - 92
tsvwg - 38
tsvwg (2nd session) - 48
v6ops - 146
videocodec - 142
wpkops - 100