[Agentx] Fw: 83rd IETF - Working Group/BOF Scheduling REMINDER

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 17 January 2012 20:44 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: agentx@ietfa.amsl.com
Delivered-To: agentx@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 457D221F873A; Tue, 17 Jan 2012 12:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGU2FhcCSeTK; Tue, 17 Jan 2012 12:44:01 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9ED21F85C0; Tue, 17 Jan 2012 12:44:00 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=lcIQyKFh3BF8nV2wlrH6OAcjCwSArKkP8Ia3s+2RnkW/GToyd35YsUx6tZEhSP5p; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.48.98] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1RnFss-0001Gx-20; Tue, 17 Jan 2012 15:43:58 -0500
Message-ID: <002101ccd559$3b347140$6b01a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Disman <disman@ietf.org>, agentx@ietf.org, LTRU Working Group <ltru@ietf.org>
Date: Tue, 17 Jan 2012 12:47:28 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88874e73e997ea5cd0f530ab163c12c615c6acd9e30df1a7299350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.48.98
Subject: [Agentx] Fw: 83rd IETF - Working Group/BOF Scheduling REMINDER
X-BeenThere: agentx@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SNMP Agent Extensibility <agentx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/agentx>, <mailto:agentx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/agentx>
List-Post: <mailto:agentx@ietf.org>
List-Help: <mailto:agentx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/agentx>, <mailto:agentx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 20:44:02 -0000

Hi -

Fwd. FYI.

Randy

----- Original Message ----- 
> From: "IETF Agenda" <agenda@ietf.org>
> To: "Working Group Chairs" <wgchairs@ietf.org>
> Cc: <irsg@irtf.org>
> Sent: Tuesday, January 17, 2012 8:54 AM
> Subject: 83rd IETF - Working Group/BOF Scheduling REMINDER
>
> 83rd IETF Paris, France
> Meeting Dates: March 25-30, 2012
> Host: TBD
> -----------------------------------------------------------------
> IETF meetings start Monday morning and run through Friday afternoon (13:30).
>
> We are accepting scheduling requests for all Working Groups and BOFs starting today.  The milestones and deadlines for
scheduling-related activities are as follows:
>
> NOTE: cutoff dates are subject to change.
>
> - 2012-01-30 (Monday): Cutoff date for requests to schedule Working Group meetings at 17:00 PT (UTC -8). To request a Working
Group session, use the IETF Meeting Session Request Tool.
> - 2012- 02-13 (Monday): Cutoff date for BOF proposal requests to Area Directors at 17:00 PT (UTC -8). To request a BOF, please see
instructions on Requesting a BOF.
> - 2012-02-16 (Thursday): Cutoff date for Area Directors to approve BOFs at 17:00 PT (UTC -8).
> - 2012-02-23 (Thursday): Preliminary agenda published for comment.
> - 2012-02-27 (Monday): Cutoff date for requests to reschedule Working Group and BOF meetings 17:00 PT (UTC -8).
> - 2012-03-02 (Friday): Final agenda to be published.
> - 2012-03-14 (Wednesday): Draft Working Group agendas due by 17:00 PT (UTC -7), upload using IETF Meeting Materials Management
Tool.
> - 2012-03-19 (Monday): Revised Working Group agendas due by 17:00 PT (UTC -7), upload using IETF Meeting Materials Management
Tool.
> - 2012-04-27 (Friday): Proceedings submission cutoff date by 17:00 PT (UTC -7), upload using IETF Meeting Materials Management
Tool.
> - 2012-05-16 (Wednesday): Proceedings submission corrections cutoff date by 17:00 PT (UTC -7), 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://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> Instructions for using the tool are available at:
>
> http://www.ietf.org/instructions/session_request_tool_instruction.html
>
> 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, March 14, 2012 by 17:00 PT.  Revised Working Group agendas are due no later than
Monday, March 19, 2012 at 17:00 PT.  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://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi
>
> 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 83 Meeting Materials" Web page is:
>
> https://datatracker.ietf.org/meeting/83/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 83 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://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> 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
27, 2012 at 17:00 PT, 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)
> Pete Resnick <presnick@qualcomm.com>
> Peter Saint-Andre <stpeter@stpeter.im>
>
> Internet Area (int)
> Jari Arkko <jari.arkko@piuha.net>
> Ralph Droms <rdroms.ietf@gmail.com>
>
> Operations & Management Area (ops)
> Ronald Bonica <rbonica@juniper.net>
> Dan Romascanu <dromasca@avaya.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>
> David Harrington <ietfdbh@comcast.net>
> ===========================================================
>
> Only 67 days until Paris!!
>