Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Second teleconference of IEEE 802 Future meeting ad hoc

I'm going to throw it out here, knowing that this may not be the most appropriate place, but unaware of a better place.

We've been discussing ways to make virtual meetings run better in the possibility that face to face sessions are impossible, either because the pandemic continues to prevent face to face sessions, or some future unspecified event also prevents face to face sessions.  One point that has been made is that our current solution really makes it difficult for attendees who want to participate in multiple WGs and find the attendant attendance schedule onerous and difficult to justify to supervisors.

So, let's think outside the box.  With face to face meetings everything had to happen in the same week because we all were at the same location at the same time, and thus had to have all WGs meet during that same week.  But, if we do the sessions virtually, is there any reason that all WGs have to meet simultaneously?  (Other than PAR work, that is?)

Setting aside PAR approvals at the EC level, why couldn't 802.1 meet for a week, then 802.3 meet for a week, then 802.11 meet for a week and a half, then 802.15 meet for a week and a half, and then 802.18 for half a week, 802.19 for half a week, etc?  The entire cycle could take 6 to 7 weeks; the EC meets at the end of the cycle, and then the cycle starts all over again...

Or am I missing something?

On Wed, Oct 27, 2021 at 11:13 PM Andrew Myles (amyles) <amyles@cisco.com> wrote:

Update :

 

G’day all

 

This is an invitation for the second teleconference of IEEE 802 Future meeting ad hoc. It is an hour later than the first meeting (notes attached) to better enable 802.18 WG participation

 

A detailed agenda will be sent later but the high level agenda is to hear submissions that focus on:

  • What aspects of remote operation have worked during COVID?
    • Highlight real examples
    • Identify why remote operation was successful in these cases
  • What aspects of remote operation have NOT worked during COVID?
    • Highlight real examples
    • Identify why remote operation was NOT successful in these cases
  • What could be done to turn any failures into successes?
    • Describe some real turnaround examples (if any)
    • … or hypothesise about how this could be done

 

Submissions so far:

  • George Zimmerman: ec-21-0237-00
    • Presented on 14 Oct 2021
    • George, do you want to do a follow up based on discussion?
  • Ben Rolfe ec-21-0238-00
    • Scheduled for 28 Oct 2021

 

Andrew Myles

 

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

-- Do not delete or change any of the following text. --

 

When it's time, join your Webex meeting here.

 

 

Meeting number (access code): 2578 270 1179

Meeting password: d7NyKAfWK55 (37695239 from phones)

 

 

Join meeting

 

Tap to join from a mobile device (attendees only)  
+1-408-525-6800,,25782701179#37695239# Call-in toll number (US/Canada)  
Some mobile devices may ask attendees to enter a numeric password. 

Join by phone  
+1-408-525-6800 Call-in toll number (US/Canada)  
Global call-in numbers

 

Join by video system, application or Skype for business
Dial 25782701179@webex.com 
You can also dial 173.243.2.68 and enter your meeting number.

 

 

If you are a host, click here to view host information.

 

 

Need help? Go to http://help.webex.com

 

 



--
Clint Chaplin
Senior Principal Standards Engineer
Samsung Research America

To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1