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

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



BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:AUS Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+1100
TZOFFSETTO:+1000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=4
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:+1000
TZOFFSETTO:+1100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=10
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Andrew Myles (amyles):mailto:amyles@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=tbaykas@gm
 ail.com:mailto:tbaykas@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=phil@beech
 er.co.uk:mailto:phil@beecher.co.uk
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=clint.chap
 lin@gmail.com:mailto:clint.chaplin@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=tim.godfre
 y@ieee.org:mailto:tim.godfrey@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=j.haasz@ie
 ee.org:mailto:j.haasz@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=daniel.har
 kins@hpe.com:mailto:daniel.harkins@hpe.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jay.holcom
 b@itron.com:mailto:jay.holcomb@itron.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chad Jones
  (cmjones):mailto:cmjones@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=stephan.ke
 hrer.committees@gmail.com:mailto:stephan.kehrer.committees@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=stuart@ok-
 brit.com:mailto:stuart@ok-brit.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Beth Kochu
 parambil (edonnay):mailto:edonnay@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=r.b.marks@
 ieee.org:mailto:r.b.marks@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=p.nikolich
 @ieee.org:mailto:p.nikolich@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=glenn.pars
 ons@ericsson.com:mailto:glenn.parsons@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=apetrick@i
 eee.org:mailto:apetrick@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ieee@max-r
 iegel.de:mailto:ieee@max-riegel.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jrosdahl@i
 eee.org:mailto:jrosdahl@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jessy.rouy
 er@nokia.com:mailto:jessy.rouyer@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=shellhamme
 r@ieee.org:mailto:shellhammer@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rjstacey@g
 mail.com:mailto:rjstacey@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rui.yang.1
 987@ieee.org:mailto:rui.yang.1987@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=George Zim
 merman:mailto:george@cmephyconsulting.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=cpowell@ie
 ee.org:mailto:cpowell@ieee.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ben@blindc
 reek.com:mailto:Ben@blindcreek.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Myl
 es (amyles):mailto:amyles@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=STDS-802-S
 EC@LISTSERV.IEEE.ORG:mailto:STDS-802-SEC@LISTSERV.IEEE.ORG
ATTACH:CID:7B1D6F65F7793140B3EAD9352FE5DDFA@namprd11.prod.outlook.com
DESCRIPTION;LANGUAGE=en-US:G’day all\n\nThis is an invitation for the sec
 ond 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 partici
 pation\n\nA detailed agenda will be sent later but the high level agenda i
 s to hear submissions that focus on:\n\n  *   What aspects of remote opera
 tion have worked during COVID?\n     *   Highlight real examples\n     *  
  Identify why remote operation was successful in these cases\n  *   What a
 spects of remote operation have NOT worked during COVID?\n     *   Highlig
 ht real examples\n     *   Identify why remote operation was NOT successfu
 l in these cases\n  *   What could be done to turn any failures into succe
 sses?\n     *   Describe some real turnaround examples (if any)\n     *   
 … or hypothesise about how this could be done\n\nSubmissions so far:\n\n
   *   George Zimmerman: ec-21-0237-00<https://mentor.ieee.org/802-ec/dcn/2
 1/ec-21-0237-00-00EC-future-meetings-observations.pdf>\n     *   Presented
  on 14 Oct 2021\n     *   George\, do you want to do a follow up based on 
 discussion?\n  *   Ben Rolfe ec-21-0238-00<https://mentor.ieee.org/802-ec/
 dcn/21/ec-21-0238-00-00EC-a-counter-point-of-the-remote-meeting-experience
 .pptx>\n     *   Scheduled for 28 Oct 2021\n\nAndrew Myles\n\n-~-~-~-~-~-~
 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\n-- Do not delete or change any of the f
 ollowing text. --\n\nWhen it's time\, join your Webex meeting here.\n\n\nM
 eeting number (access code): 2578 270 1179\nMeeting password: d7NyKAfWK55 
 (37695239 from phones)\n\n\nJoin meeting<https://cisco.webex.com/cisco/j.p
 hp?MTID=m484e15452978650d5fa9833b3b9777a9>\n\nTap to join from a mobile de
 vice (attendees only)\n+1-408-525-6800\,\,25782701179#37695239#<tel:%2B1-4
 08-525-6800\,\,*01*25782701179%2337695239%23*01*> Call-in toll number (US/
 Canada)\nSome mobile devices may ask attendees to enter a numeric password
 .\n\nJoin by phone\n+1-408-525-6800 Call-in toll number (US/Canada)\nGloba
 l call-in numbers<https://cisco.webex.com/cisco/globalcallin.php?MTID=m31d
 729f96a87b5ce57effcf892f6e362>\n\nJoin by video system\, application or Sk
 ype for business\nDial 25782701179@webex.com<sip:25782701179@webex.com>\nY
 ou can also dial 173.243.2.68 and enter your meeting number.\n\n\nIf you a
 re a host\, click here<https://cisco.webex.com/cisco/j.php?MTID=mb6d7e2487
 fd9cea2ac1a1bb82f9fc009> to view host information.\n\n\nNeed help? Go to h
 ttp://help.webex.com\n\n\n
UID:040000008200E00074C5B7101A82E00800000000409587DAE1C1D701000000000000000
 0100000005FF8CCE60EF43C409C41472130D56829
SUMMARY;LANGUAGE=en-US:Second teleconference of IEEE 802 Future meeting ad 
 hoc
DTSTART;TZID=AUS Eastern Standard Time:20211029T070000
DTEND;TZID=AUS Eastern Standard Time:20211029T080000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20211015T053244Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://cisco.webex.com/cisco/j.php?MTID=m484e15452
 978650d5fa9833b3b9777a9
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:269461477
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[ { "DisplayName" : "https://cisco.webex.com/cisco/j.
 php?MTID=m484e15452978650d5fa9833b3b9777a9"\, "LocationAnnotation" : ""\, 
 "LocationSource" : 0\, "Unresolved" : false\, "LocationUri" : "" } ]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
--- Begin Message ---

G’day all

 

Thank you for those (all bcc’ed) who attended today’s IEEE 802 Future meeting vision ad hoc. The agenda a notes from today’s meeting are in ec-21-0227-04.

 

Given we have at least one more submission in the hopper (from Ben Rolfe), I propose we have another one hour session in  two weeks’ time, but one hour later to avoid clashing again with 802.18 WG. I will send the invitation shortly.

 

The short term goal of these discussions is to 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 these failures into successes?
    • Describe some real turnaround examples (if any)
    • … or hypothesise about how this could be done

 

Submissions are requested. It is easy to criticise, and so if you highlight remote-only has not worked for some activity, please put some real effort into proposing a way to fix the identified issue(s). Also please focus on actual examples rather than strawmen. So far we have had submissions from:

  • 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

 

Would anyone else like to volunteer to present their experiences?

 

I would like to undertake more discussion off line, and to this end I will consult with the IEEE 802 EC leadership on how they would like to do this, in a manner that is open and yet does not fill the IEEE 802 EC reflector.

 

Andrew Myles

Manager, Cisco Standards

http://www.cisco.com/web/europe/images/email/signature/logo05.jpg

Andrew Myles
Manager, Enterprise Standards
amyles@cisco.com
Phone: +61 2 8446 1010
Mobile: +61 418 656587

Cisco Systems Limited
The Forum 201 Pacific Highway
St Leonards 2065
AUSTRALIA
Cisco.com

 

 


--- End Message ---