Hello Alfred
After the last TGax Call, I found we still do not have a change for CID 24554. First, there is no change for recipient. Regarding originator, we know WinSizeO is the number of buffers negotiated in the block ack agreement, I thought this should have the same rule as WinSizeR. However these buffers could be send by several transmissions as long as it is within this BA session. It is the same as complete MSDU. It will not cause any issue for the feedback as long as we have a limitation on the range of the Sequence Number subfield of the fragments in an A-MPDU. I am looking forward to your opinion.
24554
329.22
26.3.2.4
Rule that limits WinEndO-WinStartO to be within BL/4 is missing for fragmentation level 3. Please add here that a level 3 fragmentation BA session uses a WinSize that does not exceed BL/4 for the BA session that corresponds to that TID.
As in comment.
Best wishes,
Ming Gan
发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Ganming (Ming)
发送时间: 2020年7月2日 20:49
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGAX] 答复: [STDS-802-11-TGAX] 答复: TGax CRC Teleconference 2020-07-02
Thanks Mark for your feedback, please see my response inline.
发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Mark Rison
发送时间: 2020年7月2日 20:03
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGAX] 答复: TGax CRC Teleconference 2020-07-02
Thanks for these contributions, Ming.
I have the following comments:
11-20-0979-00-00ax-mac-cr-on-BSS-Load-for-draft 6.0
- "the percentage of time, linearly scaled with 255 representing 100%" -- if 100% is 255
then it's not a percentage. I suggest changing "percentage" to
"fraction" (3x)
[Ming]Agree, we should did the same change for BSS load and extended BSS load in REvmd
- "This percentage is computed" should similarly be "The field value is computed" (3x)
[Ming]Agree, same as before
- The resolutions refer to document xxxx (3x)
[Ming] Fixed
11-20-0980-00-00ax-mac-cr-on-MU-Cascading-for-draft 6.0
- "and also may enable the exchange of Control frames in both directions" is a bit weird,
because the Control frames might only go in one direction, right? Why
not delete "in both directions"? Or even this whole phrase?
[Ming] delete it
- "An MU cascading sequence shall not be exchanged between an AP and a non-AP STA (#CID 20732 and 20733) unless"
is a bit weird. Maybe "shall not occur" or "shall not be used"?
[Ming]Adopt
11-20-0981-00-00ax-mac-cr-on-Fragmentation-for-draft 6.0
I don't think CID 24364 has really been addressed.
Let's look at Level 1, which should be the easiest:
— Level 1: support for one dynamic fragment that is a non-A-MPDU [in a PSDU (#24364)], no support for dynamic fragments in an A-MPDU that is does not contain an S-MPDU.
So what does that mean?
It's clear I can only put my dynamic fragments in an S-MPDU, but beyond
that it's not clear.
Can I have multiple MSDUs fragmented at the same time (on different TIDs)?
[Ming] No if it is that A-MPDU
Can I have multiple MSDUs fragmented at the same time (to different STAs)?
[Ming] Maybe, one fragment in PSDU
If the receiver sees dynamic fragments for different MSDUs from the same STA,
does it need to assume that the earlier one was abandoned?
[Ming] abandon it in this case
Etc. Levels 2 and 3 are even more unclear.
It's possible that the intent is that all this "support for one" is intended
to be within the scope of a PSDU, i.e. just to prevent you, for level 1,
from having an A-MPDU with multiple dynamic fragments, but if so that's
not clear at all.
[Ming] your understanding is correct, do you have any suggestion if you think that is not clear
Also, it's not clear whether dynamic fragmentation is only for tx in an
HE TB PPDU. The original point was to make more efficient use of the
fixed HE TB PPDU durations, right? I can't immediately find such a restriction,
however.
[Ming] not only for TB PPDU, but also for HE MU PPDU, the initial stating point to reusing the wasted resource due to the ending time alignment in OFDMA PPDU.
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601
ROYAUME UNI WWW: http://www.samsung.com/uk
From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> On Behalf Of Osama Aboul-Magd
Sent: Wednesday, 1 July 2020 11:51
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] 答复: TGax CRC Teleconference 2020-07-02
Thanks Ming. I’ll add to the agenda.
Regards;
Osama.
On Wed, Jul 1, 2020 at 5:34 AM Ganming (Ming) <ming.gan@xxxxxxxxxx> wrote:
Hello Osama,
Could you help add the following contributions to the agenda
1. 11-20-0979-00-00ax-mac-cr-on-BSS-Load-for-draft 6.0
2. 11-20-0980-00-00ax-mac-cr-on-MU-Cascading-for-draft 6.0
3. 11-20-0981-00-00ax-mac-cr-on-Fragmentation-for-draft 6.0
Best wishes,
Ming Gan
发件人: *** 802.11 TGax - HEW - High Efficiency WLAN *** [mailto:STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx] 代表 Osama AboulMagd
发送时间: 2020年7月1日 17:22
收件人: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-02
Hello All,
TGax CRC has a conference call scheduled for Thursday July 2nd @ 10:00 ET; for 3 hours.
Please let me know if you have a submission. I’ll send an agenda later.
Webex info https://ieeesa.webex.com/ieeesa/j.php?MTID=md80a26eb27009f9eaa014f3fab6c4da2
Meeting number: 719 726 400
Meeting password: wireless (94735377 from phones and video systems)
Join by phone: Tap to call in from a mobile device (attendees only) +1-408-418-9388 USA Toll
Global call-in numbersAccess code: 719 726 400
Teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns you may have before proceeding with the teleconference
• IEEE Code of Ethics
– https://www.ieee.org/about/corporate/governance/p7-8.html
• IEEE Standards Association (IEEE-SA) Affiliation FAQ
– https://standards.ieee.org/faqs/affiliation.html
• Antitrust and Competition Policy
– https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/antitrust.pdf
• IEEE-SA Patent Policy
– http://standards.ieee.org/develop/policies/bylaws/sect6-7.html
– https://standards.ieee.org/about/sasb/patcom/
• IEEE 802 Working Group Policies &Procedures (29 Jul 2016)
– http://www.ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf
• IEEE 802 LMSC Chair's Guidelines (Approved 13 Jul 2018)
– https://mentor.ieee.org/802-ec/dcn/17/ec-17-0120-27-0PNP-ieee-802-lmsc-chairs-guidelines.pdf
• Participation in IEEE 802 Meetings
– https://mentor.ieee.org/802-ec/dcn/16/ec-16-0180-05-00EC-ieee-802-participation-slide.pptx
• IEEE 802.11 WG OM: (Approved 10 Nov 2017)
– https://mentor.ieee.org/802.11/dcn/14/11-14-0629-22-0000-802-11-operations-manual.docx
Regards;
Osama.
TGax CRC has a conference call scheduled for Thursday June 25 @ 20:00 ET; for 3 hours.
A draft agenda is available at: https://mentor.ieee.org/802.11/dcn/20/11-20-0538-35-00ax-tgax-crc-teleconference-march-july-2020-teleconference-agendas.pptx
Webex info: https://ieeesa.webex.com/ieeesa/j.php?MTID=mbda27a87f1a2aed6ebc8ff66bca58a6a
Meeting number: 715 674 299
Meeting password: wireless (94735377 from phones and video systems)
Join by phone: Tap to call in from a mobile device (attendees only) +1-408-418-9388 USA Toll
Global call-in numbersAccess code: 715 674 299
Teleconferences are bound by the conditions stipulated by the documentation below. Please review them and bring up any questions/concerns you may have before proceeding with the teleconference
• IEEE Code of Ethics
– https://www.ieee.org/about/corporate/governance/p7-8.html
• IEEE Standards Association (IEEE-SA) Affiliation FAQ
– https://standards.ieee.org/faqs/affiliation.html
• Antitrust and Competition Policy
– https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/antitrust.pdf
• IEEE-SA Patent Policy
– http://standards.ieee.org/develop/policies/bylaws/sect6-7.html
– https://standards.ieee.org/about/sasb/patcom/
• IEEE 802 Working Group Policies &Procedures (29 Jul 2016)
– http://www.ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf
• IEEE 802 LMSC Chair's Guidelines (Approved 13 Jul 2018)
– https://mentor.ieee.org/802-ec/dcn/17/ec-17-0120-27-0PNP-ieee-802-lmsc-chairs-guidelines.pdf
• Participation in IEEE 802 Meetings
– https://mentor.ieee.org/802-ec/dcn/16/ec-16-0180-05-00EC-ieee-802-participation-slide.pptx
• IEEE 802.11 WG OM: (Approved 10 Nov 2017)
– https://mentor.ieee.org/802.11/dcn/14/11-14-0629-22-0000-802-11-operations-manual.docx
Regards;
Osama.
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1
To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1