| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Juan Carlos, WGs are not supposed to be meeting during the tutorial sessions now. That is the whole point of this thread. If groups were meeting, they must have been running late. John From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Zuniga, Juan Carlos Dear all, FWIW, during and after the July Privacy Tutorial there were multiple complaints to me and the other presenters about having scheduled a Tutorial of broad interest during a time that conflicted with some WG agendas. Every time we explained that it was not in our control to handle such a collision, but I see it as a proof that it would be best to avoid overlaps as not all people shared the same views/priorities when the agendas were planned. Regarding the maximization of meeting time, I believe that adding extra time to the meetings would be just a slight improvement. However, making use of email reflectors would allow making a much better use of the very long inter-meeting times. For instance, people that have the intention to present should be encouraged to announce/introduce their presentations in advance, so that the group does not need to spend too much time at the meeting discussing the topic. This could dramatically reduce the presentation time at the F2F meeting and allow a much better use of the F2F time for critical things. A lot of the discussion can take place over email and in advance of the meeting. Regards, Juan Carlos From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Stephens, Adrian P Random musings on this topic… My personal opinion is that it’s OK to reserve Monday night for tutorials. I don’t think we should attempt to determine that a topic is not relevant to a particular WG and set up a competing meeting, because that topic may actually be of interest to members of the WG looking to understand what the ecosystem is doing. Such an attempt just reinforces silos/firewalls. 802.11’s timetable is crammed full. We use that time pretty effectively, with the exception of the closing plenary on Friday morning (which suffers from members leaving early). If we can make more time for WG meetings, we will effectively use that time. I am not opposed to holding the opening EC meeting on Sunday, because it creates pain for a small group of individuals and gain for a larger group. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) Tel: +1 (408) 2397485 (mobile, USA) ---------------------------------------------- From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Jon Rosdahl Hello All, I have an action item to start the discussion on the reflector for how can we maximize the time we have allocated for Tutorials. Sometimes we have tutorials that some believe are not for the whole of 802. Sometimes we have tutorials that everyone believes that they are for the whole of 802. Sometimes we have tutorials that some believe are for only one WG. This has caused a bit of angst. Historically, we have had rules that said that during the Plenaries no WG meetings were to be held on Monday or Tuesday to allow for the Tutorials to be held. Then we has a period where WGs could hold meeting regardless of the Tutorial schedule. Currently we have said that WGs should not hold meetings on Monday evenings, to clear the schedule for Tutorials, and that on Tuesday evenings if we have overflow Tutorials they can be held in parallel with WG meetings. We all recognize that our time is short and very full. Some WG utilize more time from Monday to Friday than others. Each WG utilizes the amount of time to match what they believe their Members want. How to squeeze more time has lead to this discussion on when a WG could try to gain more time? Comments and suggestions? I will look for your input and try to summarize both sides for discussion in San Antonio. Jon ----------------------------------------------------------------------------- ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. |