Hello all,
I’ve tried to simplify the “dog’s dinner” comment. Please see below. Comments to fido please.
|
6483
|
|
|
The term "supported rate set" is undefined
|
Change throughout to "operational rate set", except at 1277.47, 1383.45, 1384.1 (change to "basic rate set") and maybe 892.52, 1383.50, 1384.5 (not sure what is intended there)
|
MAC
|
|
Status: From
last meeting: Pages 1544 1606 change “operational rate set” to format shown above.
I have added changes for these two locations since the last review.
Discussion:
The AP broadcasts its supported rates in the “Supported Rates and BSS Membership Selectors” element combined with the “Extended Supported Rates and
BSS Membership Selectors”. It indicates which rates are “basic” by setting the top bit of a rate.
The MLME-START.request supplies these values in a combination of the BSSBasicRateSet, OperationalRateSet and BSSMembershipSelectorSet parameters.
A non-AP uses the same elements to indicate its supported rates.
The MLME-JOIN.request specifies an OperationalRateSet parameter, but not a BSS Membership Selector. The MLME-ASSOCIATE.request contains no rate information.
There is no definition of “operational rate set”, but it presumably relates to one or more of the parameters cited above. Neither is there a formal
definition of “basic rate set”, even though that term is frequently used. I shall assume it’s OK to use “basic rate set”.
Basically we have two choices: which of “operational” or “basic” was intended, and how to convey the definition of “operational” (as the latter is
less firmly entrenched).
Proposed Changes:
Insert in 3.2, ordered appropriately, a new definition:
“supported rates set: The set of rates that a STA might use for transmission, and that the STA is capable
of receiving. The supported rates set is determined locally by the OperationalRateSet parameter of the MLME-START.request or MLM-JOIN.request primitive. The supported rate set of a peer contains the data rates from the peer’s Supported Rates and BSS Membership
Selectors element and, if present, the Extended Supported Rates and BSS Membership Selectors element.”
At 648.11: delete NOTE in its entirety.
At 1544.44:
Discussion. “Select the operational rate set” is something done by the SME, in generating the parameters of the JOIN.request. We could use language
like “adopt as its operational rates those indicated in the OpeartionalRateSet parameter”, but then that begs the question of a whole bunch of other equally important parameters affecting MLME internal state that are not mentioned here.
|
10.1.4.4.1 General
Upon receipt of an MLME-START.request primitive, a STA shall determine the BSS’s BSSID (as described in 10.1.4 (Acquiring synchronization, scanning)), select channel
synchronization information, select a beacon period, select the operational rate set, initialize and start its TSF timer, and begin transmitting Beacon frames if the STA is a non-DMG STA or DMG Beacon frames if the STA
is a DMG STA. See 8.3.3.2 (Beacon frame format) for the description of a Beacon frame, and see 8.3.4.2 (DMG Beacon) for the description of a DMG Beacon frame.
|
At 1606.38:
(no change proposed)
|
The value of the Minimum PHY Rate in a TSPEC shall satisfy the following constraints:
a) for an uplink TS, it
— is included in dot11SupportedDataRatesTxTable and in the
AP's operational rate set, or
— corresponds to an HT MCS included in dot11HTSupportedMCSTxTable, if present, and in the
AP's operational HT MCS set, if defined, at a bandwidth and guard interval supported by the
non-AP STA on transmission and permitted in the BSS, or
— corresponds to a VHT-MCS and NSS for which support is indicated in the Tx VHT-MCS Map
subfield in the VHT Operation parameter ofthe MLME-(RE)ASSOCIATE.request primitive,
if present, and in the AP's operational VHT-MCS and NSS set, if defined, at a bandwidth and
guard interval supported by the non-AP STA on transmission and permitted in the BSS
|
At 892.47:
|
NOTE 2—Examples of when this bit may be set to 1 include, but are not limited to, the following situations:
— One or more non-HT STAs are associated
— A non-HT BSS is overlapping (a non-HT BSS may be detected by the reception of a Beacon or Probe Response frame
where the supported rates contain only Clause 16 (DSSS PHY specification for the 2.4 GHz band designated for ISM applications), Clause 18 (Orthogonal frequency division multiplexing (OFDM) PHY specification), Clause 17 (High rate
direct sequence spread spectrum (HR/DSSS) PHY specification), or Clause 19(Extended Rate PHY (ERP) specification) rates)
that does not include an HT Capabilities element).
— A Management frame (excluding a Probe Request) is received where the supported rate set includes only Clause 16 (DSSS PHY specification for the
2.4 GHz band designated for ISM applications), Clause 18 (Orthogonal frequency division multiplexing (OFDM) PHY specification), Clause 17 (High rate direct sequence spread spectrum (HR/DSSS) PHY specification), and Clause 19 (Extended Rate PHY (ERP) specification)
rates
|
At 1277.47:
|
The characteristic rate set is equal to the IBSS’s
basicsupported rate set when the STA is operating as a member of an IBSS. It is equal to the AP’s
supported operational
rate set when the STA is associated with an AP.
|
At 1291.21:
+ same change at 1293.05 and 1294.32
|
When the
operationalsupported rate set of the receiving STA or STAs is not known, the transmitting STA shall transmit using a rate in the BSSBasicRateSet parameter, or anMCS in the Basic MCS
Set field of the HT Operation parameter of the MLME-START.request primitive or Basic MCS Set field of the HT Operation parameter of the SelectedBSS parameter of the MLME-JOIN.request primitive, or a <VHT-MCS, NSS> tuple in the BSS basic VHT-MCS and NSS set,
or a rate from the mandatory rate set of the attached PHY if the BSSBasicRateSet, the Basic MCS Set field of the HT Operation parameter of the MLME-START.request primitive or Basic MCS Set field ofthe HT Operation parameter of the SelectedBSS parameter of
the MLME-JOIN.request primitive, and the BSS basic VHT-MCS and NSS set are empty.
|
At 1383.45:
|
b) In an IBSS if a Beacon frame isreceived from one of the IBSS participants where the
supported operational
rate set contains only Clause 16 (DSSS PHY specification for the 2.4GHz band designated for ISM applications) or Clause 17 (High rate direct sequence spread spectrum (HR/DSSS) PHY specification) rates.
contains no Clause 19 (ERP) rates and no BSS membership selectors.
c) A Management frame (excluding a Probe Request) is received where the
operationalsupported rate set
contains no Clause 19 (ERP) rates and no BSS membership selectors.includes only Clause 16 (DSSS PHY specification for the 2.4 GHz band designated for ISM applications) or Clause 17 (High rate
direct sequence spreadspectrum (HR/DSSS) PHY specification) rates.
|
At 1384.01:
|
— A Beacon frame is received from a neighbor STA where the
supported operational
rate set contains only Clause 16 (DSSS PHY specification for the 2.4 GHzband designated for ISM applications) or Clause 17 (High rate direct sequence spread spectrum (HR/DSSS) PHY specification) rates, or
— A Management frame (excluding Probe Request) isreceived where the
supported operational
rate set includes only Clause 16 (DSSS PHY specification for the 2.4 GHz band designated for ISM applications) or Clause 17 (High rate direct sequence spreadspectrum (HR/DSSS) PHY specification) rates
|
Proposed resolution:
Revised. Make changes under CID 6483 in <this-document>. These changes essentially replace instances of “supported rate set” with either basic or
operational rate set.
Best Regards,
Adrian P STEPHENS
Tel: +44 (1793) 404825 (office)
Tel: +1 (971) 330 6025 (mobile) ç please note new number
----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
_______________________________________________________________________________
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.