TGah editor: modify the D0.2 text from P040L45, as follows Association Request frame format Changes based on 802.11REVmc D1.1 Modify Table 8-26 in Clause 8.3.3.5 by inserting the following rows :
TGah editor: No change 793 Shusaku Shimada 158 11 Non TIM STA may not be of Sector Report RAW but fast sector discovery may be needed by non TIM STAs. Other means than real sector discovery but to assign Group ID to non TIM STAs in locaton based may be desirable. REJECT. Refer to Doc. 13/1120r1. <Discussion> Sectorization operation element is included in the beacon, which is crucial for sector operation. So, it’s unlikely that an STA performes sectorization without decoding of RPS I.E in any beacon. If a non-TIM STA to operate in sectorization, it needs to check the RPS by short probe response or delayed check on short beacon by which it also can get to know about Sector Report RAW (and Sector Sounding RAW) scheduled. In addition, fast sector discovery is a useful feature whenever there are multiple (TIM) STAs which want to know its best sector fastly at the same time. TGah editor: No change 652 Ronald Murias 93 62 "else" needs to be clarified. In line 62 page 93, change "else" to the following text: if neither Type 0 Sectorization nor Type 1 Sectorization is supported. REJECT. Refer to Doc. 13/1120r1. As I mentioned in the the Sector Capabilites element is now merged into the S1G Capabilities element by resolution to CID 202. FYI, element ID and length sub-field of the S1G Capabilites element are already in the figure and table as well. (Please refer to 850 Timo Koskela Sector element 93 62 "else" as a fourth option should be "reserved" REJECT. 13/1120r1. As I mentioned in the the Sector Capabilites
element is now merged into the S1G Capabilities element by resolution to CID 202. FYI, element ID and length sub-field of the S1G Capabilites element are already in the figure and table as well. (Please refer to 653 Ronald Murias 93 48 The length of the Sector Capabilities element shall be specified. Make the following changes: 1). Add the following text in "Definition" column of the "Length" row in Table 8-191e: "indicates the number of octets in the Information fields after the Lenght field" 2). add the following text in "Encoding" column of the "Length" row in Table 8-191e: "set to 1." 3)Delete the last row in Table i.e., the Reserved row in line 13 page 94. REJECT. Refer to Doc. 13/1120r1. As I mentioned in the above, the Sector Capabilites element is now merged into the S1G Capabilities element by resolution to CID 202. FYI, element ID and length sub-field of the S1G Capabilites element are already in the figure and table as well. (Please refer to
654 Ronald Murias 93 41 The convention of 802.11 element specification is in the format of a figure, not in a table. In order to keep consistent, the Sector Capabilityies element should be also specified in Figure. Change Table into a figure format. REJECT. Refer to Doc. 13/1120r1. As I mentioned in the above, the Sector Capabilites element is now merged into the S1G Capabilities element by resolution to CID 202. FYI, element ID and length sub-field of the S1G Capabilites element are already in the figure and table as well. (Please refer to <Discussion> As I mentioned in the above, the Sector Capabilites element is now merged into the S1G Capabilities element by resolution to CID 202. FYI, element ID sub-field and length sub-field of the S1G Capabilites element are already well-defined in the figure and table as well. (Please refer to “11-13-1098-00-00ah-cc9-resolution-of-cid-201and-202”) TGah editor: resolution to CID 202 already covers resolution to these CIDs. 683 Ronald Murias 150 53 What's a Type 0 Sectorization Scheme element? What's a Type 1 Sectorization Scheme element? Searched entire 11ah/D0.1 doc, they only occur in the paragarph in line 52 page 150. Propose three options: Option-1: Define Type 0 Sectorization Scheme element and Type 1 Sectorization Scheme element. Option-2: Delete the paragraph in line 52 on page 150. Option-3: -- replace "Type 0 Sectorization Scheme element" REJECT. Refer to Doc. 13/1120r1. I agree with what the commenter pointed out. As I mentioned in the above, this also is resolved by resolution to CID 202 which describes the Sector Operation Element if sectorization type is group sectorzation and