[Ltru] Fw: 76th IETF - Working Group/BOF Scheduling

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 31 August 2009 17:48 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800133A6E39 for <ltru@core3.amsl.com>; Mon, 31 Aug 2009 10:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.324
X-Spam-Level:
X-Spam-Status: No, score=-1.324 tagged_above=-999 required=5 tests=[AWL=0.675, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 eWEr6eyz4keY for <ltru@core3.amsl.com>; Mon, 31 Aug 2009 10:48:35 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 1242628C399 for <ltru@ietf.org>; Mon, 31 Aug 2009 10:48:35 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=MWtg+dpIOyHGL1OpyPUEh+jzdByOqPgV5dp3UqL0Dz8DELw6QoS3YPyUtSbgHzzs; 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 [99.41.49.166] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1MiAzm-0007jB-14 for ltru@ietf.org; Mon, 31 Aug 2009 13:48:46 -0400
Message-ID: <003001ca2a63$bea69ec0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "LTRU Working Group" <ltru@ietf.org>
Date: Mon, 31 Aug 2009 10:52:00 -0700
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8881afdcb5313ff34f9913ab8ced2ef8bc2539337a6ae1cc9cc350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.41.49.166
Subject: [Ltru] Fw: 76th IETF - Working Group/BOF Scheduling
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 17:48:36 -0000

Hi -

As co-chair...

Forwarded for your information.  Currently there are no plans for
the ltru WG to meet in Hiroshima.  Based on what we've seen so
far of the discussion of potential new work, I believe co-chair
Martin and I will recommend that the WG be shut down after our
two current work items are published.

Randy

----- Original Message ----- 
> From: "IETF Agenda" <agenda@ietf.org>
> To: "Working Group Chairs" <wgchairs@ietf.org>
> Cc: <irsg@isi.edu>du>; <bofchairs@ietf.org>
> Sent: Monday, August 31, 2009 7:05 AM
> Subject: 76th IETF - Working Group/BOF Scheduling 
>
> -----------------------------------------------------------------
> 76th IETF  Hiroshima, Japan
> Meeting Dates: November 8-13, 2009
> Host: WIDE
> -----------------------------------------------------------------
> IETF meetings start Monday morning and run through Friday mid-afternoon
> (15:15).
> 
> We are accepting scheduling requests for all Working Groups and BOFs. 
> The milestones and deadlines for scheduling-related activities are as
> follows:
> 
> NOTE: cutoff dates are subject to change.
> 
> 2009-09-07 (Monday): Cutoff date for BOF proposal requests to Area
> Directors at 17:00 PDT (24:00 UTC/GMT). To request a BOF, please see
> instructions on Requesting a BOF
> http://www.ietf.org/wg/bof-procedures.html.
> 2009-09-14 (Monday): Cutoff date for requests to schedule Working Group
> meetings at 17:00 PDT (24:00 UTC/GMT). To request a Working Group session,
> use the IETF Meeting Session Request Tool
> https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi. 
> **Please note - if you send in your request after this date your Working
> Group will not be scheduled until after the Preliminary agenda has been
> published (Friday, October 2, 2009) and will NOT receive priority
> scheduling.**
> 2009-09-14 (Monday): Cutoff date for Area Directors to approve BOFs at
> 17:00 PDT (24:00 UTC/GMT).
> 2009-10-02 (Friday): Preliminary agenda published for comment.
> 2009-10-09 (Friday): Cutoff date for requests to reschedule Working Group
> and BOF meetings 17:00 PDT (24:00 UTC/GMT).
> 2009-10-16 (Monday): Final agenda to be published.
> 2009-10-28 (Wednesday): Draft Working Group agendas due by 17:00 PDT
> (24:00 UTC/GMT), upload using IETF Meeting Materials Management Tool
> https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi.
> 2009-11-02 (Monday): Revised Working Group agendas due by 17:00 PST (01:00
> Tuesday, November 3 UTC/GMT), 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, October 28 by 17:00 PDT (24:00
> UTC/GMT).  Revised Working Group agendas are due no later than Monday,
> November 2 at 17:00 PDT (01:00 Tuesday, November 3 UTC/GMT).  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 76 Meeting Materials" Web page is:
> 
> https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=76
> 
> 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 76 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
> request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
> NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
> DESCRIPTION, and the information requested in (4) below. (Please read the
> BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
> requesting a session for a BOF.)
> 
> 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 Friday, October 9 at 17:00 PDT (24:00 UTC/GMT), 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 (figures from the 75th IETF meeting are
> included at the end of this message):
> 
>     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) 
> Lisa Dusseault <lisa.Dusseault@messagingarchitects.com>
> Alexey Melnikov <alexey.melnikov@isode.com>
> 
> Internet Area (int) 
> Jari Arkko <jari.arkko@piuha.net>
> Ralph Droms <rdroms@cisco.com>
> 
> Operations & Management Area (ops) 
> Ronald Bonica <rbonica@juniper.net>
> Dan Romascanu <dromasca@avaya.com>
> 
> Real-time Applications and Infrastructure Area (rai)
> Cullen Jennings <fluffy@cisco.com>
> Robert Sparks <rjsparks@nostrum.com>
> 
> Routing Area (rtg) 
> Ross Callon <rcallon@juniper.net>
> Adrian Farrel <adrian.farrel@huawei.com>
> 
> Security Area (sec) 
> Pasi Eronen <pasi.eronen@nokia.com>
> Tim Polk <tim.polk@nist.gov>
> 
> Transport Area (tsv) 
> Lars Eggert <lars.eggert@nokia.com>
> Magnus Westerlund <magnus.westerlund@ericsson.com>
> ===========================================================
> 75th IETF Meeting Attendance Number
> 
> 6lowpan  50
> 6man  80
> alto  86
> ancp  27
> apparea  72
> autoconf  48
> avt  73
> avt (2nd session)  34
> behave  141
> behave (2nd session)  126
> bliss  54
> bmwg  24
> capwap  7
> ccamp  89
> codec  152
> dhc  42
> dime  18
> dispatch  83
> dispatch (2nd session)  24
> dkim  25
> dnsext  113
> dnsop  171
> drinks  51
> dtnrg  50
> eai  35
> ecrit  61
> emu  32
> fecframe  16
> forces  25
> geopriv  62
> grow  88
> hip  66
> hiprg  33
> hokey  38
> hokey (2nd session)  27
> httpbis  25
> iccrg  54
> idnabis  81
> idr  92
> intarea  142
> ipdvb  5
> ipfix  28
> ippm  26
> ipsecme  43
> isis  25
> isms  21
> keyprov  25
> kitten  17
> krb-wg  13
> l2vpn  100
> l3vpn  101
> ledbat  58
> lisp  148
> manet  43
> mboned  39
> mediactrl  22
> mext  61
> mif  84
> mip4  29
> mmusic  58
> morg  14
> mpls  154
> mpls (2nd session)  133
> mptcp  126
> multimob  42
> nea  35
> netconf  27
> netext  56
> netext2  69
> netmod  32
> netmod (2nd session)  20
> nfsv4  15
> ogpx  54
> opsarea  72
> opsawg  33
> ospf  38
> p2prg  88
> p2psip  81
> pce  52
> pcn  31
> pim  41
> pkix  42
> pwe3  136
> radext  22
> rmt  11
> roll  80
> rrg  94
> rtgarea  131
> rtgwg  42
> saag  80
> sasl  22
> savi  NO SHEETS
> sidr  95
> sieve  11
> simple  69
> sipcore  72
> softwire  103
> speermint  NO SHEETS
> syslog  24
> tcpm  44
> tictoc  47
> tls  36
> tsvarea  98
> tsvwg  55
> v6ops  155
> vcarddav  19
> xcon  22
> xmpp  44
> yam  19