Subject: [Tsvwg] 70th IETF - Working Group/BOF Scheduling

From: Lars Eggert <[email-masked]>
Date: Wed, 5 Sep 2007 13:08:04 +0300

Hi,

please note the BOF deadline for Vancouver:

> -- Cut-off date for requests to schedule Working Group meetings and  
> for
> preliminary BOF proposals to ADs: Monday, October 1 at 17:00 ET (21:00
> UTC/GMT).

If you are planning a BOF targeted at TSV, you should already be  
talking to Magnus and me.

In any event, you will need a fully complete BOF proposal by October  
1. Please also read draft-narten-successful-bof.

Lars

Begin forwarded message:
> -----------------------------------------------------------------
> 70th IETF - Vancouver, BC, Canada
> Meeting Dates: December 2-7, 2007
> -----------------------------------------------------------------
> We will be accepting scheduling requests for all Working Groups and  
> BOFs
> starting today, Tuesday, September 4, 2007.  The milestones and  
> deadlines
> for scheduling-related activities are as follows:
>
> -- Cut-off date for requests to schedule Working Group meetings and  
> for
> preliminary BOF proposals to ADs: Monday, October 1 at 17:00 ET (21:00
> UTC/GMT).
> -- Cut-off date for requests to schedule BoFs: Monday, October 22  
> at 17:00
> ET (21:00 UTC/GMT).
> -- Preliminary agenda published for comment: Friday, October 26 by
> midnight ET.
> -- Cut-off date for requests to reschedule Working Group and BOF  
> meetings:
> Wednesday, November 7 at 09:00 ET (14:00 UTC/GMT).
> -- Final agenda published: Monday, November 12 before midnight ET.
> -- Draft Working Group agendas due: Wednesday, November 21 at 17:00 ET
> (22:00 UTC/GMT).
> -- Revised Working Group agendas due: Monday, November 26 at 12:00 ET
> (17:00 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 [email-masked].
> 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, November 21 by 17:00 ET  
> (22:00
> UTC/GMT).  Revised Working Group agendas are due no later than Monday,
> November 26 at 12:00 ET (17:00 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 70 Meeting Materials" Web page is:
>
> https://datatracker.ietf.org/public/meeting_materials.cgi? 
> meeting_num=70
>
> 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:
> [email-masked].
> ===============================================================
> For your convenience, comprehensive information on requesting meeting
> sessions at IETF 70 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 [email-masked].  If you are unable  
> to use
> the tool, then you may send your request via e-mail to  
> [email-masked],
> with a copy to the appropriate Area Director(s).
>
> Requests to schedule BOF sessions must be sent to [email-masked]  
> 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 Wednesday, November 7 at 09:00 ET (14: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 69th IETF meeting are
> included at the end of this message):
>
>     e. Special requests:
>
>     f. Number of sessions:
>
>     g. Length of session:
>        - 1 hour
>        - 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 <[email-masked]>
>
> Applications Area (app)
> Lisa Dusseault <[email-masked]>
> Chris Newman <[email-masked]>
>
> Internet Area (int)
> Jari Arkko <[email-masked]>
> Mark Townsley <[email-masked]>
>
> Operations & Management Area (ops)
> Ronald Bonica <[email-masked]>
> Dan Romascanu <[email-masked]>
>
> Real-time Applications and Infrastructure Area (rai)
> Cullen Jennings <[email-masked]>
> Jon Peterson <[email-masked]>
>
> Routing Area (rtg)
> Ross Callon <[email-masked]>
> David Ward <[email-masked]>
>
> Security Area (sec)
> Sam Hartman <[email-masked]>
> William Polk <[email-masked]>
>
> Transport Area (tsv)
> Lars Eggert <[email-masked]>
> Magnus Westerlund <[email-masked]>
> ===========================================================
> 69th IETF Meeting Attendance Number
>
> 16ng	66
> 6lowpan	No Blue Sheets
> ancp	No Blue Sheets
> apm (BoF)	93
> apparea (AG)	75
> autoconf	77
> autoconf (2nd session)	63
> avt	94
> avt (2nd session)	73
> behave	53
> biff (BoF)	30
> bliss	123
> bmwg	38
> btns	38
> calcify	14
> capwap	44
> ccamp	112
> ccamp (2nd session)	95
> dccp	33
> dhc	66
> dime	35
> dkim	58
> dnsop	104
> dtnrg	51
> eai	47
> ecrit	93
> emu	39
> enum	82
> forces	17
> geopriv	100
> grow	73
> hiprg/emerg	77
> hokey	87
> httpbis (BoF)	61
> iccrg	52
> idr	112
> intarea (AG)	120
> ipdvb	7
> ipfix	24
> ippm	No Blue Sheets
> ipr	23
> isis	58
> isms	25
> keyprov 	46
> kitten	17
> krb-wg	32
> krb-wg (2nd session)	21
> l1vpn	CANCELLED
> l2vpn	No Blue Sheets
> l3vpn	83
> lemonade	35
> lemonade (2nd session)	25
> ltans	16
> manet	77
> mboned	50
> mediactrl	42
> mip4	31
> mip6	101
> mipshop	100
> mmusic	42
> mmusic (2nd session)	77
> mobopts (RG)	85
> monami6	90
> mpls	152
> nea	62
> nee (BoF)	46
> nemo	92
> netconf	38
> netlmm	99
> nfsv4	20
> nsis	36
> ntp	37
> opsawg	66
> ospf	56
> p2psip (adhoc)	36
> p2psip	154
> pana	34
> pce	63
> pcn	79
> pim	32
> pkix	52
> pwe3	127
> radext	39
> rmt	32
> rpsec	50
> rrg	145
> rtgarea (AG)	136
> rtgwg	97
> saag (AG)	149
> samrg	41
> sasl	31
> sidr	89
> sieve	17
> simple	81
> sip 	162
> sip (2nd session)	128
> sipping	137
> sipping (2nd session)	135
> smime	17
> softwire	51
> speermint	125
> tam (BoF)	103
> tcpm	35
> tls	54
> trill	44
> trill (2nd session)	27
> tsvarea (AG)	67
> tsvwg	81
> v6ops	130
> vcarddav (BoF)	24
> xcon	45
> xsdmi (BoF)	29
>
>
>
>