| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
OK, well in that case you need to fix the Contains the 12 least significant bits of the AID of a STA expected to process the following VHT NDP and prepare the sounding feedback. at 616.27, and potentially also examine the other 60 or so "expected to"s I can see in D5.0. 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: Stephens, Adrian
P [mailto:Adrian.P.Stephens@xxxxxxxxx] Hello Mark, “Having said that, I'm OK with the direction of the proposed resolution below. I would suggest changing "that can provide feedback"
to "that is expected to provide feedback" (see 616.27), though.” In the past we have had comments about the use of passive voice, and anthropomorphic verbs (expect, hopes, desires etc…). The “that can provide feedback” is shorthand (like all other cans) for: “That is able to provide feedback, given the rules defined in this standard”, and the reference cites those rules. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) ---------------------------------------------- From: Mark Rison [mailto:m.rison@xxxxxxxxxxx]
> The commenter’s proposed resolution does not work because “STA
identified by the AID12 subfield in the STA Info field” does not work when the AID12 field is zero. The commenter's proposed resolution does work, because it is qualified by "directed to a non-AP STA in an infrastructure BSS",
and such a STA has an AID. Per 616.29, the AID12 field is (only) "Equal to 0 if the STA is
an AP, mesh STA, or STA that is a member of an IBSS." Having said that, I'm OK with the direction of the proposed resolution below. I would suggest changing "that can provide feedback"
to "that is expected to provide feedback" (see 616.27), though. 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: ***** IEEE stds-802-11-tgm
List ***** [mailto:STDS-802-11-TGM@xxxxxxxx]
On Behalf Of Stephens, Adrian P --- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Dear TGmc participants, I was tasked to generate and circulate a resolution for Comment 7770. This email does this. I propose to bring this resolution to TGmc for consideration asap.
Context: 615.36
Discussion; The change proposed in the comment addresses the specific issue raised. But it doesn’t address the more general comment that an IBSS or mesh STA cannot generate an AID12 value to go in the STA Info field, and probably
a non-AP infrastructure STA can’t either. So the question is whether it is ever meaningful for an IBSS, mess or non-AP STA to generate a VHT NDP announcement frame. If so, then we might
want to fix this. If not, we might want to make this constraint explicit. I was tasked with stimulating discussion on the reflector. I received only one reply which stated:
As the response indicates, in the case when the intended recipient is an AP, mesh STA or an IBSS STA, Table 9-25 (616.29) clearly indicates that
the AID12 field contains a zero. The normative behaviour is specified in 1461.61:
So the only issue is with the cited text. The commenter’s proposed resolution does not work because “STA
identified by the AID12 subfield in the STA Info field” does not work when the AID12 field is zero. The email correspondent’s resolution is better, but contains the problematical “expected”, which generally causes comments of the form “expected
by whom”? The proposed change is as follows: 615.36
Proposed resolution: Revised. At 615.38 change “identified by the AID in the STA Info field” to “that can provide feedback (see 10.34.5.2)”. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) ---------------------------------------------- _______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to -
http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at:
http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________
IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ |