Re: [v6ops] 80th IETF - Working Group/BOF Scheduling
"Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com> Thu, 06 January 2011 11:09 UTC
Return-Path: <gvandeve@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA31C3A6DCD for <v6ops@core3.amsl.com>; Thu, 6 Jan 2011 03:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.08
X-Spam-Level:
X-Spam-Status: No, score=-9.08 tagged_above=-999 required=5 tests=[AWL=0.319, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8]
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 tgCF+iwYIopY for <v6ops@core3.amsl.com>; Thu, 6 Jan 2011 03:09:48 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 349353A6CE0 for <v6ops@ietf.org>; Thu, 6 Jan 2011 03:09:47 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4EAE4yJU2Q/khMgWdsb2JhbACDd59CXxUBARYiJKVYilONWIEhgWYIBQaBPnQEjiyCcA
X-IronPort-AV: E=Sophos;i="4.60,282,1291593600"; d="scan'208";a="72992506"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 06 Jan 2011 11:11:52 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p06BBpq3031619 for <v6ops@ietf.org>; Thu, 6 Jan 2011 11:11:52 GMT
Received: from xmb-ams-101.cisco.com ([144.254.74.76]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 6 Jan 2011 12:11:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Thu, 06 Jan 2011 12:11:44 +0100
Message-ID: <4269EA985EACD24987D82DAE2FEC62E502DF194F@XMB-AMS-101.cisco.com>
In-Reply-To: <BC62A7B4-F900-4FAB-A9A5-DEB897EBB8E0@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] 80th IETF - Working Group/BOF Scheduling
Thread-Index: AcusdtM/+Ro91j+6SoCytsSLWjFynwBG2/qw
References: <20110104162156.414BC3A6CCE@core3.amsl.com> <BC62A7B4-F900-4FAB-A9A5-DEB897EBB8E0@cisco.com>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>, v6ops v6ops <v6ops@ietf.org>
X-OriginalArrivalTime: 06 Jan 2011 11:11:45.0040 (UTC) FILETIME=[80F28900:01CBAD92]
Subject: Re: [v6ops] 80th IETF - Working Group/BOF Scheduling
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 11:09:49 -0000
Ole and me are working on a update based upon feedback of the WG comments on the harmful tunnels draft. So, as result a short slot for explaining those doc changes would be useful. G/ -----Original Message----- From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Fred Baker (fred) Sent: woensdag 5 januari 2011 2:21 To: v6ops v6ops Subject: Re: [v6ops] 80th IETF - Working Group/BOF Scheduling It looks like we are starting scheduling for Prague. I have signed us up for our usual 2.5 and 2 hour meetings. As usual, the ground rules for getting time on the agenda include - a speaker showing up at the meeting - relevance to the charter, and - a posted internet draft that is new since IETF 79. There is also a sense on the IESG, I'm told, that we should be able to get agendas together a lot earlier than we have in the past. One comment I heard asked for an agenda to be posted with the request for a meeting slot. At this point, I am expecting draft-ietf-v6ops-multihoming-without-nat66 draft-ietf-v6ops-v4v6tran-framework draft-ietf-v6ops-v6-aaaa-whitelisting-implications draft-v6ops-multihoming-without-nat66 draft-wbeebee-v6ops-ipv6-cpe-router-bis draft-wing-v6ops-happy-eyeballs-ipv6 draft-korhonen-v6ops-3gpp-eps draft-v6ops-multihoming-without-nat66, draft-wing-v6ops-happy-eyeballs-ipv6 should be reposted as draft-ietf-v6ops-*, please - working group draft. I expect that at this coming meeting we will find enough meat in cpe-router-bis to adopt it as well. We collectively need to decide what to do with draft-korhonen-v6ops-3gpp-eps; of the respondents in the survey, most felt it was something to work on, but we didn't have a clear consensus on whether or not to adopt it. I'll start that discussing in a separate thread in a few moments. At this point, we also have 15 other drafts posted. One will for sure die (mine); it has accomplished its purpose. Another is likely to be folded into cpe-router-bis. There was a sense at IETF 79 that there was value in draft-jankiewicz-v6ops-v4v6biblio, but no clear direction on where Ed should take it - some thought it should be a working group document and some thought it should be abandoned. I'll leave that to Ed for the moment. The comments made in the survey, which I emailed to the list on 20 November, were inconclusive with respect to the others; I'll leave it to the authors to tell v6ops-chairs@tools.ietf.org how they would like to proceed with their drafts. On Jan 4, 2011, at 8:21 AM, IETF Agenda wrote: > ----------------------------------------------------------------- > 80th IETF ˆ Prague, Czech Republic > Meeting Dates: March 27-April 1, 2011 > Host: CZ.NIC > ----------------------------------------------------------------- > IETF meetings start Monday morning and run through Friday mid-afternoon > (15:15). > > 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. > > 2010-12-27 (Monday): Working Group and BOF scheduling begins. To > request a Working Group session, use the IETF Meeting Session Request > Tool. > 2011- 01-31 (Monday): Cutoff date for BOF proposal requests to Area > Directors at 17:00 PT (01:00 Tuesday, February 1 UTC). To request a BOF, > please see instructions on Requesting a BOF. > 2011-02-14 (Monday): Cutoff date for requests to schedule Working Group > meetings at 17:00 PT (01:00 Tuesday, February 15 UTC). To request a > Working Group session, use the IETF Meeting Session Request Tool. > 2011-02-14 (Monday): Cutoff date for Area Directors to approve BOFs at > 17:00 PT (01:00 Tuesday, February 15 UTC). > 2011-02-24 (Thursday): Preliminary agenda published for comment. > 2011-02-28 (Monday): Cutoff date for requests to reschedule Working > Group and BOF meetings 17:00 PT (01:00 Tuesday, March 1 UTC). > 2011-02-28 (Monday): Working Group Chair approval for initial document > (Version -00) submissions appreciated by 17:00 PT (01:00 Tuesday, March 1 > UTC). > 2011-03-04 (Friday): Final agenda to be published. > 2011-03-16 (Wednesday): Draft Working Group agendas due by 17:00 PT > (01:00 Thursday, March 17 UTC), upload using IETF Meeting Materials > Management Tool. > 2011-03-21 (Monday): Revised Working Group agendas due by 17:00 PT > (01:00 Tuesday, March 22 UTC), 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 16, 2011 by 17:00 PT (01:00 > Thursday, March 17 UTC). Revised Working Group agendas are due no later > than Monday, March 21, 2011 at 17:00 PT (01:00 Tuesday, March 22 UTC). > 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 80 Meeting Materials" Web page is: > > https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=80 > > 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 80 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 Monday, February 28, 2011 at 17:00 PT (01:00 > Tuesday, March 1 UTC), 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) > Alexey Melnikov <alexey.melnikov@isode.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.farrel@huawei.com> > > Security Area (sec) > Tim Polk <tim.polk@nist.gov> > Sean Turner <turners@ieca.com> > > Transport Area (tsv) > Lars Eggert <lars.eggert@nokia.com> > David Harrington <ietfdbh@comcast.net> > =========================================================== > 79th IETF Meeting Attendance Number > > Working Group > > 6lowpan - 108 > 6man - 178 > abfab - 50 > alto - 110 > ancp - 26 > apparea (AG) - 74 > armd BOF - 70 > atoca - 37 > autoconf - 29 > avt - 82 > avt (2nd session) - 55 > behave - 103 > bmwg - 15 > ccamp - 100 > ccamp (2nd session) - 79 > codec - 59 > conex - 43 > core - 81 > core (2nd session) - 67 > cuss - 14 > decade - 59 > dhc - 28 > dime - 14 > dispatch - 61 > dnsext - 99 > dnsop - 96 > drinks - 37 > dtnrg (RG) - 22 > eai - 31 > ecrit - 37 > eman - 56 > emu - 21 > fecframe - 8 > forces - 23 > geopriv - 39 > grow - 44 > hiprg (RG) - 44 > hokey - 22 > iddtspec - 13 > idr - 80 > intarea (AG) - 111 > ipfix - 37 > ippm - 23 > ipsecme - 28 > iri - 18 > isis - 52 > isms - 14 > karp - 50 > kidns - 122 > kitten - 31 > krb-wg - 12 > l2vpn - 119 > l3vpn - 92 > lisp - 69 > lwip - 156 > manet - 35 > martini - 36 > mboned - 18 > mext - 69 > mext (second session) - 64 > mif - 114 > mip4 - 10 > mmusic - 50 > mpls - 150 > mpls (2nd session) - 158 > mptcp - 101 > mptcp (2nd session) - 64 > msec - 33 > multimob - 61 > nbs BPF - 101 > nea - 30 > netconf - 42 > netext - 52 > netmod - 28 > nfsv4 - 25 > nfsv4 (second session) - NO SHEETS > opsarea (AG) - 40 > opsawg - 51 > ospf - 53 > p2psip - 58 > pcp - 59 > pim - 47 > pkix - 30 > ppsp - 38 > precis - 31 > pwe3 - 140 > radext - 20 > roll - 72 > rtgarea (AG) - 135 > rtgwg - 56 > saag (AG) - 90 > samrg (RG) - 20 > savi - 67 > scap BOF - 44 > sidr - 68 > sipclf - 19 > sipcore - 57 > siprec - 44 > softwire - 110 > tcpm - 25 > tictoc - 17 > trill - 72 > tsvarea (AG) - 33 > tsvwg - 65 > v6ops - 203 > v6ops (second session) - 159 > vcarddav - 13 > vnrg (RG) - 48 > websec - 101 > _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Fred Baker
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Brian E Carpenter
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Fred Baker
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Gunter Van de Velde (gvandeve)
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Brian E Carpenter
- Re: [v6ops] 80th IETF - Working Group/BOF Schedul… Gunter Van de Velde (gvandeve)