Re: [STDS-802-11-TGBH] Request for motions on upcoming TGbh telecon (Apr

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

Thanks, Jay,

I’ll get it added to the agenda.

In terms of the changes to the use case, I think it might be helpful to the group to understand the requirements that result from the other group/standard, with a little more detail.

(Note that I think it was mentioned that the “other group” is the WFA, and WFA Specifications are generally in the public domain and can be discussed/reviewed in IEEE – I/you would need to double-check for any specific document, but it is probably okay to reference.)

The last part is news to me, if I understood: “we already have the solutions standardized by other group.” So, are you saying that not only is the RCM problem an issue for the WFA spec, but the WFA have a solution already standardized as well? If that’s the case, then we are getting in a “grey area” in terms of how much the IEEE should try to capture any of that (a third party protocol has a problem, and has already found a solution) – but we can discuss at the task group. More information would be helpful, again, to those members who don’t know any details here (myself included).

Mark

From: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>
Sent: Monday, April 11, 2022 2:12 AM
To: mark.hamilton2152@xxxxxxxxx; STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBH] Request for motions on upcoming TGbh telecon (April 12)

Hi Mark,

Issue tracking document is updated to R35, please help add it to the agenda.

Hi All,

We propose to change use case 4.1 and 4.8 to “in scope” in R35 as we already have the solutions standardized by other group.

Please don’t hesitate to contact me if you have any concern on this.

Thanks

Best Regards

Jay Yang

From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Sent: 2022年4月8日 0:14
To: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>; STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBH] Request for motions on upcoming TGbh telecon (April 12)

Thanks, Jay. Added, in updated agenda: https://mentor.ieee.org/802.11/dcn/22/11-22-0568-01-00bh-agenda-tgbh-2022-april-7.pptx

Since members have little time to review this updated proposal, I suggest we tackle our planned motion preparation activity first, and then consider your updated proposal in the time remaining.

Mark

From: Yang, Zhijie (NSB - CN/Shanghai) <zhijie.yang@xxxxxxxxxxxxxxx>
Sent: Thursday, April 7, 2022 6:27 AM
To: mark.hamilton2152@xxxxxxxxx; STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBH] Request for motions on upcoming TGbh telecon (April 12)

Hi Mark,

Issue tracking document is updated to R34, please help add it to the agenda.

Thanks

Best Regards

Jay Yang

From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx>
Sent: 2022年4月1日 0:14
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBH] Request for motions on upcoming TGbh telecon (April 12)

Dorothy/all,

I request permission for the following motions, to be run during the TGbh telecon on April 12 (9:00am ET). Note that:

It is likely/possible the group will “down-select” from this set of motions, or quite possibly will combine one or more into a “set of documents” motion, as a combination of the subject documents of proposed single motions. That will be discussed in the TG, prior to starting the motions.
Documents may receive revisions, so the latest revision will be anticipated for motion.

Proposed motions: