Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-14

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

I have the following comments on 20/1022r2, which is proposed for

motion today:

- CID 24403: the D6.0 wording gives insufficient regard to QoS.

The principles described in the comment were extensively discussed

in TGm and should be given effect to. There are also editorial

issues with the D6.0 wording, as mentioned in the comment.

The wording from 19/1667 under CID 21203 should be adopted ([*]).

- CID 24565: the rejection claims that "Ack-enabled multi-TID A-MPDU is already included".

But it's only mentioned as a reference, not in the actual rule,

which only mentions ack-enabled single-TID A-MPDUs:

Table 9-532b (A-MPDU contents in the HE ack-enabled single-TID immediate response context) or

Table 9-532d (A-MPDU contents in the HE ack-enabled multi-TID immediate response context) if

the TID Aggregation Limit field of the User Info field addressed to the non-AP STA in the Trigger

frame is greater than 0 and the non-AP STA intends to carry an ack-enabled single-TID A-MPDU

(see 26.6.3.1 (General) and 26.6.3.4 (Ack-enabled multi-TID A-MPDU operation).

[Also, there's a missing closing parenthesis. And the parenthesis

is incompatible with the yellow highlight.]

- CID 24381: "then the HE STA" should be "then it" or "then the HE non-AP STA"

(I think the former is sufficient)

Thanks,

Mark

P.S. : Liberté, Égalité, Fraternité ! Bonne fête nationale ! 🇫🇷

[*] Here are the propoosed changes:

In 26.6.3.1 change:

If the AP specifies a value defined in Table 9-154 (ACI-to-AC encoding)(#20006) in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then an HE STA that transmits a multi-TID A-MPDU to the AP should aggregate QoS Data frames from any one of the TIDs from the same AC or higher priority AC as indicated in the Preferred AC subfield of the Trigger Dependent User Info field that is addressed to the STA in the Trigger frame, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

NOTE—While it is recommended that the STA transmit QoS Data from the AC that is same or higher than the preferred AC, the STA might still(#20227) to aggregate QoS Data from an AC that has lower priority than the preferred AC.

The STA may aggregate MPDUs from TIDs in other ACs within the remaining time to the HE TB PPDU duration value indicated in the UL Length subfield in the Common Info field of the received Trigger frame, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

NOTE—If the AP indicates AC_BK in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then an HE STA that transmits a multi-TID A-MPDU to the AP might aggregate MPDUs from any AC/TID or combination of TIDs, up to the limit indicated in the TID Aggregation Limit subfield in Trigger Dependent User Info field of the Trigger frame.

An HE STA that intends to send QoS Data frames from a single TID should select a TID from the same or higher priority AC indicated in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame. If the HE STA has no buffered MPDU for TIDs belonging to the same or higher priority AC indicated in the Preferred AC subfield in the Trigger Dependent User Info field of a Basic Trigger frame, then the HE STA may include MPDUs for a TID belonging to any other AC in that A-MPDU carried in the HE TB PPDU.

to:

An HE STA that transmits a multi-TID A-MPDU in an HE TB PPDU should aggregate MPDUs in the following order:

· first, any and all MPDUs that correspond to the Preferred AC subfield of the Trigger Dependent User Info field addressed to the STA in the Trigger frame

· then, any and all MPDUs that correspond to any AC that has a higher priority

· then, any MPDUs that correspond to any AC that has a lower priority

subject to:

· the limit indicated in the TID Aggregation Limit subfield in the Trigger Dependent User Info field addressed to the STA in the Trigger frame

· the duration indicated in the UL Length subfield in the Common Info field of the Trigger frame

NOTE—These rules permit a STA to not aggregate any MPDUs from the preferred AC or a higher priority AC.

In 26.4.1 change:

An HE STA that transmits a Multi-TID BlockAckReq frame in a PPDU that is not an HE TB PPDU shall set the TID subfields in the AID TID Info fields in the Per TID Info subfields of the BAR Information field of the Multi-TID BlockAckReq frame to TIDs that correspond to ACs that have the same or higher priority as the primary AC. An HE STA that transmits a Multi-TID BlockAckReq frame in an HE TB PPDU may set the TID subfields in the AID TID Info fields in the Per TID Info subfields of the BAR Information field of the Multi-TID BlockAckReq frame to a TID that corresponds to any AC.

to:

An HE STA that transmits a Multi-TID BlockAckReq frame in a PPDU that is not an HE TB PPDU shall set the TID Value subfields in the Per TID Info subfields of the BAR Information field of the Multi-TID BlockAckReq frame to TIDs that correspond to ACs that have the same or higher priority as the primary AC. An HE STA that transmits a Multi-TID BlockAckReq frame in an HE TB PPDU should set the TID Value subfields in the Per TID Info subfields of the BAR Information field of the Multi-TID BlockAckReq frame to TIDs that correspond to ACs that have the same or higher priority as the preferred AC.

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: Tuesday, 14 July 2020 12:15
To: STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-14

I’ve uploaded a new revision of the TG agenda. It is available at: https://mentor.ieee.org/802.11/dcn/20/11-20-0538-44-00ax-tgax-crc-teleconference-march-july-2020-teleconference-agendas.pptx

Regards;

Osama.

From: Osama Aboul-Magd <oamagd@xxxxxxxxx>
Date: Sunday, July 12, 2020 at 2:53 PM
To: Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>, <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-14

I’ve uploaded an agenda foe the teleconference. It is available at: https://mentor.ieee.org/802.11/dcn/20/11-20-0538-43-00ax-tgax-crc-teleconference-march-july-2020-teleconference-agendas.pptx

Regards;

Osama.

From: "*** 802.11 TGax - HEW - High Efficiency WLAN ***" <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx> on behalf of Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>
Reply-To: Osama AboulMagd <Osama.AboulMagd@xxxxxxxxxx>
Date: Friday, July 10, 2020 at 6:20 AM
To: <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGAX] TGax CRC Teleconference 2020-07-14

Hello All,

TGax CRC has a conference call scheduled for Tuesday July 14 @ 10:00 ET; for 2 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=m7eb8986b9ef9a24da4da272a794135bc

Meeting number: 129 761 3003

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 numbers

Access code: 129 761 3003

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)