IEEE P802.11 Wireless LANs Abstract This submission proposes resolutions for the following comments from the letter ballot on P802.11ax D2.0: 13869, 12999, 11311, 13914, 13912, 13913, 11098, 13829, 13915, 13917, 13951 NOTE Set the Track Changes Viewing Option in the MS Word to Markup” to clearly see the proposed text edits. – “All Revision History: R0: Initial version. R1: Updated during teleconference on 5/3/2018 CID Clause Page Comment Proposed Change 13869 9.4.2.27 120.40 "If operating in an operating class for which the Remove the followings: behavior limits set listed in Annex E does not "If operating in an operating include the DFS_50_100_Behavior then a STA class for which the behavior sets the OBSS Narrow Bandwidth RU in UL limits set listed in Annex E OFDMA Tolerance Support field to 0." includes the Even though an AP is not operating in a DFS DFS_50_100_Behavior then band, if the AP has a the following apply:" dot11OBSSNarrowBWRUinULOFDMATolerated "If operating in an operating equal to true, it is better that the AP sets the class for which the behavior OBSS Narrow Bandwidth RU in UL OFDMA limits set listed in Annex E Tolerance Support field to 1. does not include the Because a DFS band is regionally different. DFS_50_100_Behavior then Considering an AP's movement to different DFS a STA sets the OBSS regions, the default value should be set based Narrow Bandwidth RU in UL on only the support of the feature if there is no OFDMA Tolerance Support negative impact. field to 0." 9.4.2.27 120.39 When operating in a channel without DFS, why As in comment should the bit "OBSS Narrow Bandwidth RU in UL OFDMA Tolerance Support" be set to 0 and not to 1? Narrow bandwidth RU from an OBSS STA would not cause a false DFS alarm
IEEE P802.11 Wireless LANs Abstract This submission proposes resolutions for the following comments from the letter ballot on P802.11ax D2.0: 13869, 12999, 11311, 13914, 13912, 13913, 11098, 13829, 13915, 13917, 13951 NOTE – Set the Track Changes Viewing Option in the MS Word to “All Markup” to clearly see the proposed text edits. Revision History: R0: Initial version. R1: Updated during teleconference on 5/3/2018 CID Clause Page Comment Proposed Change 13869 9.4.2.27 120.40 "If operating in an operating class for which the behavior limits set listed in Annex E does not include the DFS_50_100_Behavior then a STA sets the OBSS Narrow Bandwidth RU in UL OFDMA Tolerance Support field to 0." Even though an AP is not operating in a DFS band, if the AP has a dot11OBSSNarrowBWRUinULOFDMATolerated equal to true, it is better that the AP sets the OBSS Narrow Bandwidth RU in UL OFDMA Tolerance Support field to 1. Because a DFS band is regionally different. Considering an AP's movement to different DFS regions, the default value should be set based on only the support of the feature if there is no negative impact. Remove the followings: "If operating in an operating class for which the behavior limits set listed in Annex E includes the DFS_50_100_Behavior then the following apply:" "If operating in an operating class for which the behavior limits set listed in Annex E does not include the DFS_50_100_Behavior then a STA sets the OBSS Narrow Bandwidth RU in UL OFDMA Tolerance Support field to 0." 9.4.2.27 120.39 When operating in a channel without DFS, why should the bit "OBSS Narrow Bandwidth RU in UL OFDMA Tolerance Support" be set to 0 and not to 1? Narrow bandwidth RU from an OBSS STA would not cause a false DFS alarm As in comment
11-18-0807-01-00ax-d2-0-dfs-comment-resolution.docx