1203 Adrian 9.4.2.250.1 "non-AP or non-PCP Replace all such use with Stephens EDMG STA" the expanded term AP EDMG STA or non-PCP EDMG STA". This is inherently ambiguous as it combines (or) and (and) operations and is no clear operator precedence. In this case, is the non-AP STA also an EDMG STA? I suspect it is also incorrect, because AP and PCP EDMG STAs also transmit this element. Resolution: Revise Discussion: Text is ambiguous and should be changed throughout 802.11ay. It is true that EDMG STAs and PCP EDMG STAs transmit this element, however these STAs also declare they are EDMG STAs through the DMG Parameters field that is transmitted in Beacons. "non-AP or non-PCP EDMG STA" Instruct the Editor to make a global change in the 802.11ay draft from "non-AP EDMG STA or non-PCP EDMG STA" to 1204 Adrian 9.4.2.250.1 "Each Extended Replace these fields with Stephens Capabilities field is "subelements" following structured as defined in the model of the Figure 28." baseline, e.g. in 9.4.2.22.14. Congratulations on the subelement. However, if you do use the sub-element, you avoid creating a novel concept, you re-use the existing concepts about extensibility, and what happens if you encounter an unknown subelement. 1207 Adrian 9.4.2.250.4 "PHY Capability field" - Insert "EDMG" in the Stephens this is an over-general name of the field. Ditto field name, as it is for all the subfields of the specific to EDMG STAs EDMG capabilities element.
1203 Adrian Stephens 9.4.2.250.1 "non-AP or non-PCP EDMG STA" This is inherently ambiguous as it combines (or) and (and) operations and is no clear operator precedence. In this case, is the non-AP STA also an EDMG STA? I suspect it is also incorrect, because AP and PCP EDMG STAs also transmit this element. Replace all such use with the expanded term EDMG STA or non-PCP EDMG STA". Resolution: Revise Discussion: Text is ambiguous and should be changed throughout 802.11ay. It is true that AP EDMG STAs and PCP EDMG STAs transmit this element, however these STAs also declare they are EDMG STAs through the DMG Parameters field that is transmitted in Beacons. Instruct the Editor to make a global change in the 802.11ay draft from "non-AP or non-PCP EDMG STA" to "non-AP EDMG STA or non-PCP EDMG STA" 1204 Adrian Stephens 9.4.2.250.1 "Each Extended Capabilities field is structured as defined in Figure 28." Congratulations on the subelement. However, if you do use the sub-element, you avoid creating a novel concept, you re-use the existing concepts about extensibility, and what happens if you encounter an unknown subelement. Replace these fields with "subelements" following the model of the baseline, e.g. in 9.4.2.22.14. 1207 Adrian Stephens 9.4.2.250.4 "PHY Capability field" - this is an over-general field name, as it is specific to EDMG STAs Insert "EDMG" in the name of the field. Ditto for all the subfields of the EDMG capabilities element.
11-18-0679-00-00ay-lb231-cid-resolutions.docx