Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
All (802.11 TGbh reflector folks), Based on the quick feedback received so far (thanks for that!), I’d like to suggest, and request comments:
I did hear requests to avoid conflicts with TGbc, and to not impact EMEA timezones, but there really are no alternatives that work for everyone. This approach will impact only 2 TGbc calls (out of 6 calls, if I counted correctly), and has 1 call that is a bad option for EMEA. Thoughts? Mark From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx> All, On today’s TGbh call, it was pointed out that we have been holding teleconferences at times that are consistently bad for Asia (13:00 ET). So, I’d like to start a discussion about our options, and preferences. As I understand it, the options to be better for Asia are either 9:00 or 10:00 ET, or 19:00 ET. Any comments on those options? However, the challenge is that 9:00 or 10:00 ET is already taken by other TGs for their regular calls: CAC, REVme, AANI, TGbc, TGbd, TGbe, TGbf, and TGbi. I personally cannot meet in conflict with CAC, or REVme. I have gotten strong requests to avoid conflict with TGbe. I think TGbh meeting in conflict with TGbi is clearly inappropriate. So, the remaining options are to conflict with AANI, TGbc, TGbd, and/or TGbf.
The 19:00 ET slot is equally bad for EMEA, as our current time is for Asia.
One other choice is to have alternate times, sometimes meeting when it is bad for Asia and sometimes when it is bad for EMEA. (Since all of the leadership is in U.S. timezones, I’m not going to offer to have calls when it is bad for the U.S., sorry 😊 )
Thanks. Mark To unsubscribe from the STDS-802-11-TGBH list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBH&A=1 |