1 / 14

CID #46 rationale and discussion of proposed resolution

CID #46 rationale and discussion of proposed resolution. Date: 2010-03-14. Authors:. Problem Statement. The issue is simple: the current TGv draft contains a specific subclause which is vague, and results in implementation ambiguity and interoperability failures. Problem Details.

zinna
Download Presentation

CID #46 rationale and discussion of proposed resolution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CID #46 rationale and discussion of proposed resolution Date: 2010-03-14 Authors:

  2. Problem Statement • The issue is simple: the current TGv draft contains a specific subclause which is vague, and results in implementation ambiguity and interoperability failures

  3. Problem Details • Subclause 7.3.2.6 modified for mBSSIDs • TIM encoding needed to be updated to indicate buffered group addressed frames for multiple BSSIDs (mBSSIDs) • Two new encodings for TIM described: Method A and Method B • Each method is clear, no ambiguity • Vague language is in choice between Methods: • “… an AP uses Method B whenever it does not incur the misinterpretation of the received Partial Virtual Bitmap by non-AP STAs. Otherwise, an AP uses Method A.” (Full text is provided in backup slides.) • “No” vote and comment are focused on this vague language.

  4. A bit of history • This vote was first submitted during WG letter ballots • Requested the text specify the situations where Method B could “incur the misinterpretation of the received Partial Virtual Bitmap by non-AP STAs” • TGv and subject matter experts declined the comment, stating the Draft text was clear, and that specific change text was needed. • Subsequent e-mails and discussions on the issue, suggesting specific text listing the scenarios in which Method A must be used, ended with only “… there are [still] other scenarios” which still weren’t covered.

  5. Current status • The fact that many hours of study, and e-mail exchanges with the subject matter experts, still did not result in a clear understanding of when Method A must be used, seems to only prove that the text is not clear. • Latest ballot comments (on SB letter ballots) attempt to eliminate the need for two Methods, to eliminate the ambiguity, rather than try to clarify the vague language. (Full text is provided in backup slides.) • On 1st Sponsor Ballot, comment declined similarly to WG letter ballot. • Hence, the vague text remains. It seems unlikely that AP implementations will all get this right (unless they are more clever than I am – and why are we asking implementers to be clever to get interoperability right?). • Note that Annex L, even being only informative, does not help resolve this ambiguity, either.

  6. Requested Action • This commenter requests the CRC consider carefully the referenced text, and determine if it agrees it is vague enough to cause incorrect implementations to be likely. • If the CRC agrees the text should be clarified, this can be done by describing the scenarios where Method A must be used (suggestions in backup slides, below), or by replacing the text so that a single method is used (suggested text for this is also in backup slides).

  7. Thank you

  8. Backup slides

  9. Current Draft (D9.0) text When dot11MgmtOptionMultiBSSIDEnabled is false, the Partial Virtual Bitmap field consists of [traditional TIM description, unmodified …] When dot11MgmtOptionMultiBSSIDEnabled is true, the Partial Virtual Bitmap field of the TIM element is constructed as follows, where the maximum possible number of BSSIDs is an integer power of 2, n=log2 (maximum possible number of BSSIDs), k is the number of actually supported non-transmitted BSSIDs, and k<=(2n-1). • The bits 1 to k of the bitmap are used to indicate that one or more group addressed frames are buffered for each AP corresponding to a non-transmitted BSSID. The AIDs from 1 to k are not allocated to a STA. The AIDs from (k+1) to (2n-1) are reserved and set to 0. The remaining AIDs are shared by the BSSs corresponding to the transmitted BSSID and all non-transmitted BSSIDs. • Each of the bits from 1 to k is set to 1 when the DTIM Count field is 0 for the BSS corresponding to the non-transmitted BSSID and one or more group addressed frames are buffered at the AP for this BSS. • Each bit starting from bit 2n in the traffic-indication virtual bitmap corresponds to unicast traffic buffered for a specific STA within any BSS corresponding to a transmitted or non-transmitted BSSID at the time the Beacon frame is transmitted. The correspondence is based on the AID of the STA. • Based upon its knowledge of the capability of associated stations to support the multiple BSSID capability, as indicated by the corresponding field in the Extended Capabilities element and the content of the traffic indication virtual bitmap, an AP shall encode the Partial Virtual Bitmap and the Bitmap Control field of the TIM element using one of the two following methods. Specifically, an AP uses Method B whenever it does not incur the misinterpretation of the received Partial Virtual Bitmap by non-AP STAs. Otherwise, an AP uses Method A.

  10. Current Draft (D9.0) text – con’t Method A and Method B are described as follows: • Method A: The Partial Virtual Bitmap field consists of octets numbered 0 through N2 of the traffic indication virtual bitmap, where N2 is the smallest number such that bits numbered (N2 + 1) × 8 through 2007 in the bitmap are all 0. If such a value N2 does not exist, that is, when not all bits in the last octet of the traffic indication virtual bitmap are equal to 0, N2=250. When using this method, the Bitmap Offset subfield value always contains the number 0, and the Length field is set to N2 + 4. • Method B: The Partial Virtual Bitmap field consists of a concatenation of octets numbered 0 through N0-1 and octets numbered N1 through N2 of the traffic indication virtual bitmap, where N0 is the smallest positive integer such that N0×8-2n < 8. If N0 is an odd number, then N1 is the largest odd number such that N0< N1and each of the bits N0×8 to (N1×8-1) is equal to zero. When N0 is an even number, N1 is the largest even number such that N0< N1and each of the bits N0×8 to (N1×8-1) is equal to zero. If such a value N1> N0 does not exist, N1=N0. Additionally, N2 is the smallest integer value for which the values for bit (N2+1)×8 to 2007 in the bitmap are all 0. If such a value N2 does not exist, that is, when not all bits in the last octet of the traffic indication virtual bitmap are equal to 0, N2 = 250. When using this method, the Bitmap Offset subfield contains the value of (N1-N0)/2, and the Length field is set to N0+N2-N1+4. NOTE — when N1=N0, Method B reduces to Method A.

  11. Attempted clarification language(reportedly, not sufficient) • Based upon its knowledge of the capability of associated stations to support the multiple BSSID capability, as indicated by the corresponding field in the Extended Capabilities element and the content of the traffic indication virtual bitmap, an AP shall encode the Partial Virtual Bitmap and the Bitmap Control field of the TIM element using one of the two following methods. Specifically, an AP uses Method B whenever no BSSs have buffered group addressed frames, and all legacy STAs (non-AP STAs that do not support the multiple BSSID capability) have no buffered directed frames. Otherwise, an AP uses Method A.

  12. Proposed text to remove two Methods When dot11MgmtOptionMultiBSSIDEnabled is false, the Partial Virtual Bitmap field consists of [traditional TIM description, unmodified …] When dot11MgmtOptionMultiBSSIDEnabled is true, the Partial Virtual Bitmap field of the TIM element is constructed as follows, where the maximum possible number of BSSIDs is an integer power of 2, n=log2 (maximum possible number of BSSIDs), k is the number of actually supported non-transmitted BSSIDs, and k<=(2n-1). • The bits 1 to k of the bitmap are used to indicate that one or more group addressed frames are buffered for each AP corresponding to a non-transmitted BSSID. The AIDs from 1 to k are not allocated to a STA. The AIDs from (k+1) to (2n-1) are reserved and set to 0. The remaining AIDs are shared by the BSSs corresponding to the transmitted BSSID and all non-transmitted BSSIDs. • Each of the bits from 1 to k is set to 1 when the DTIM Count field is 0 for the BSS corresponding to the non-transmitted BSSID and one or more group addressed frames are buffered at the AP for this BSS. • Each bit starting from bit 2n in the traffic-indication virtual bitmap corresponds to unicast traffic buffered for a specific STA within any BSS corresponding to a transmitted or non-transmitted BSSID at the time the Beacon frame is transmitted. The correspondence is based on the AID of the STA. • Based upon its knowledge of the capability of associated stations to support the multiple BSSID capability, as indicated by the corresponding field in the Extended Capabilities element and the content of the traffic indication virtual bitmap, an AP shall encode the Partial Virtual Bitmap and the Bitmap Control field of the TIM element using one of the two following methods. Specifically, an AP uses Method B whenever it does not incur the misinterpretation of the received Partial Virtual Bitmap by non-AP STAs. Otherwise, an AP uses Method A.

  13. Proposed text to remove two Methods – con’t. Method A and Method B are described as follows: • Method A: The Partial Virtual Bitmap field consists of octets numbered 0 through N2 of the traffic indication virtual bitmap, where N2 is the smallest number such that bits numbered (N2 + 1) × 8 through 2007 in the bitmap are all 0. If such a value N2 does not exist, that is, when not all bits in the last octet of the traffic indication virtual bitmap are equal to 0, N2=250. When using this method, the Bitmap Offset subfield value always contains the number 0, and the Length field is set to N2 + 4. • Method B: The Partial Virtual Bitmap field consists of a concatenation of octets numbered 0 through N0-1 and octets numbered N1 through N2 of the traffic indication virtual bitmap, where N0 is the smallest positive integer such that N0×8-2n < 8. If N0 is an odd number, then N1 is the largest odd number such that N0< N1and each of the bits N0×8 to (N1×8-1) is equal to zero and corresponds to an AID for a STA that supports the multiple BSSID capability. When N0 is an even number, N1 is the largest even number such that N0< N1and each of the bits N0×8 to (N1×8-1) is equal to zero and corresponds to an AID for a STA that supports the multiple BSSID capability. If such a value N1> N0 does not exist, N1=N0. Additionally, N2 is the smallest integer value for which the values for bit (N2+1)×8 to 2007 in the bitmap are all 0. If such a value N2 does not exist, that is, when not all bits in the last octet of the traffic indication virtual bitmap are equal to 0, N2 = 250. When using this method, the Bitmap Offset subfield contains the value of (N1-N0)/2, and the Length field is set to N0+N2-N1+4. NOTE — when N1=N0, Method B reduces to Method A.

  14. Demonstration of proposed technique(only slight modification from Method B)

More Related