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

Re: [STDS-802-11-TGBE] Announcement: Motions for TGbe on Wednesday 14th of December 2022



Hi Alfred,

We can run a motion on doc 1381r5 for the following 15 CIDs, which includes the 3 CIDs:
"10386, 12158, 10572, 13735, 11121, 13734, 10206, 13960, 13620, 10426, 12484, 12643, 10876, 12380, 13856"

Guogang somehow took the 3 CIDs from doc 1381r5 and put them in his doc 1517 without any coordination with PoC so I'm not sure what's going on there.

Regards,
Minyoung

On Tue, Dec 13, 2022 at 12:07 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:
Hi Minyoung, 

The request is past the deadline but there is some inconsistencies in the comment resolution of these CIDs as they appear to be all related:
- There was a request in an individual e-mail (which cc-ed me as well) to run separate motions for 3 CIDs (request from you) that are covered in both 11-22/1381 and in 1517r2: 10386, 12158, 10572.
- There was a request in the reflector from Guogang to defer CID 10386 (which i already did) and for which i requested the DCN that will be covering (currently listed as TBD in the queue), but since there is 1517 as well then i am not certain if the TBD is actually going to be replaced by 1517 (waiting for Guogang to advise).

So I am leaning towards  removing these CIDs from the motion, and place the two documents (1381, and 1517) as pending SP/Motion (whichever preferred) under post-quarantine queues and by the time there is a bit of clarity of which docs will be covering which CIDs (and hopefully some convergence). In the meantime will wait for feedback from you and Guogang as to which are the docs that need to be queued and the list of CIDs that they will be covering.

Regards,

Alfred




On Tue, Dec 13, 2022 at 10:52 AM Minyoung Park <mpark.ieee@xxxxxxxxx> wrote:
Hi Alfred,

Could we run a separate motion for the following CIDs in doc 1381r5 (Beacon-A frame)?

10386, 12158, 10572, 13735, 11121, 13734, 10206, 13960, 1362010426, 12484, 12643, 10876, 12380, 13856


SP result was (32y, 29n, 16a)


Thanks,
Minyoung



On Fri, Dec 2, 2022 at 3:19 PM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all,

This is an advanced notification that TGbe will run motions during the Joint teleconference scheduled on 14th of December 2022.

Please refer to the document linked below for a preliminary list of all the motions (starting from slide 104) that will be run during the conference call:


Please review the documents included in Motions 480-484, and reply to this e-mail if you would like to identify any of these documents or any particular CID as items that need further discussion. The deadline for sending these e-mails is  December 13th 2022 @10:00am ET.

 

A list of these requested items will be queued for discussion and run as a separate motion (Motions >485) during the same Joint conference call.
Contributions that have not received a request for further discussions will be part of their respective cumulative motion and will be run at the same Joint conference call. 

 

In addition, POCs/Assignees are invited to review the CIDs that are listed in the 11-22/1773r11 and 11-22/1849r0 that are prepared for the CIDs that are in quarantine (these are CIDs that were discussed up to September 17th of 2022, and included in Motion 483, and those that were discussed up to October 31st of 2022, and included in Motion 484). 

POCs are invited to do the following by the end of next week (by December 11, EOB ET) :

- Identify any CIDs for which a request for SP was sent until Friday 02, 2022 or is pending for SP. These CIDs will be placed on hold (i.e., removed from Motion 452) until the SP is run.  

- Provide notes from the discussions for the other CIDs so that we can populate the proposed resolution column with the technical arguments that the group had on that particular CID. 

  • More specifically the following POCs are requested to provide technical notes for the CIDs listed in the docs below:
    • Kumail for CIDs discussed in 11-22/1463 that are listed in Motion 483, 
    • Jason for CIDs discussed in 11-22/1250 that are listed in Motion 483,
    • Vishnu for CIDs discussed in 11-22/1335  that are listed in Motion 484,
    • Abdel for CIDs discussed in 11-22/1373 that are listed in Motion 484,
    • Minyoung for CIDs discussed in 11-22/1381 that are listed in Motion 484,
    • Duncan for CIDs discussed in 11-22/1454, 11-22/1457 that are listed in Motion 484,
    • Gaurang for CIDs discussed in 11-22/1477 that are listed in Motion 484,
    • Liwen for CIDs discussed in 11-22/1500, 11-22/1501, 11-22/1503 that are listed in Motion 484,
    • Yongho for CIDs discussed in 11-22/1509 that are listed in Motion 484,
    • Subir for CIDs discussed in 11-22/1582 that are listed in Motion 484,
    • Abhi for CIDs discussed in 11-22/1586 and 11-22/1690 that are listed in Motion 484,
    • Ming for CIDs discussed in 11-22/1746 that are listed in Motion 484


If you have any comments and/or questions please let me know.

Best Regards,

Alfred


--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe Chair,
Qualcomm Technologies Inc.
Cell #:    +1 858 263 9445
Office #: +1 858 658 5302

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



--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe Chair,
Qualcomm Technologies Inc.
Cell #:    +1 858 263 9445
Office #: +1 858 658 5302

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