Hi Matt,
Thanks for your work on this. I have a few comments in the attached.
Thanks,
Gaurang
From: Matthew Fischer <matthew.fischer@xxxxxxxxx>
Sent: Thursday, December 19, 2024 9:49 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-NPCA
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable
macros.
New and Improved! r13:
Re MIB (Li Quan):
I agree that having a default value does not make sense.
An item for TGmf is that in at least 23.x and 27.x there are PHY MIB tables with many XxxxOptionImplemented variables with default values.
Re (Haorui):
In 37.x, within 1762r13, removed redundant phrase "and the channel occupied by the received PPDU(s)"
It makes no sense for a capability variable to have a default.
A STA is either capable or not capable.
Also, it should be "STA" not "station", I think.
[Also, I always forget about the current preference re
dot11FooImplemented v dot11FooEnabled.]
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
Hello Matthew and all,
Thank you for updating the PDT.
Recently, I have been revising the MIB and would like to
ask your opinion.
Below is the MIB I drafted for NPCA. Would you prefer to use this version or do you have any suggestions for modifications?
dot11NPCAOptionImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is a capability variable.
Its value is determined by device capabilities.
This attribute, when true, indicates that the station implementation is
capable of supporting NPCA operation."
DEFVAL { false }
::= { TBD }
BR,
Li Quan
Original
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-NPCA
r12 is now on the server:
Generally agree with both of your comments, r12 includes changes that generally follow the spirit of those comments.
1. - agree, changed to multiple BSS in r12
2. the commas in the cited item in r11 are in the correct locations
note that as long as conjunctions are used, no comma should appear as those conjunctions are adding/modifying the single, albeit long, qualifying phrase
i.e. the entire phrase beginning with "identified" and ending with "received PPDU(s)" is a single qualifying phrase referring to the subject "channel" that appears at the very beginning
the predicate for channel is "does not overlap", making everything in between is a single qualifying phrase, which must be set aside by commas
so the structure of the sentence is:
the channel, identified by some means, does not overlap something
"identified by some means" is then expanded into that big long multiply-qualifying phrase
the commas serve to separate the qualifier from the subject and the predicate
this is because the natural English order is:
adjectival phrase
subject predicate
object
In the cited sentence, when the order of adjectival phrase and subject is reversed, commas are used to separate the adjectival phrase
subject, adjectival phrase,
predicate object
NOTE - this email has been truncated by removing quoted text from previous emails.
If you want to view the previous emails, please refer to earlier emails in the thread.
Thanks for your efforts on updating the draft over and over.
I have the below comments further:
1. MBSS in baseline = mesh BSS so in this PDT the MBSS should be changed to multiple BSS set, or other better wording;
2. for b)-c, the highlighted comma seems in a wrong place. Maybe it should be after "CH_BANDWIDTH_IN_NON_HT of the received PPDU(s)";
"c.the 20/40/80/160 MHz channel occupied by the received PPDU(s), identified by the STA based on the channel allocations in the corresponding band and the PPDU bandwidth that is signaled
in the received PPDU(s) or obtained from the RXVECTOR parameter CH_BANDWIDTH_IN_NON_HT of the received PPDU(s) and the channel occupied by the received PPDU(s),
does not overlap with the NPCA primary channel"
3. based on Motion #164, only receiving the CTS without RTS cannot trigger NPCA switch, but in current bullet b) "and/or" means 3 possible cases including the case where only the
response frame is received, which seems against the Motion.
b)the STA received a PPDU containing a Control frame and/or a PPDU containing a initial response frame of a Control frame exchange on the BSS
primary channel and all of the following conditions apply:
--
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
--
Matthew Fischer
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|