1141 114.01 8.4.2.170q "is one octet in Remove redundant Rejected- length" - size specifiers from the redundant text in this subclause. There are many instances such as ”1 octet in length” in baseline draft too. 1142 114.44 8.4.2.170q I don't see any Add behaviour in Revised- text on how the clause 9/10 that "DL Max Data indicates how the Add a behavior Rate field" is values in this field description in Relay used. affect AP and non-AP Discovery Procedure Is it a commitment STA behaviour. (subclause 9.48.5). by the AP, or a constraint on the Ditto for the other data TGah editor to make non-AP STA? rate fields of this changes shown in structure. 0576r1 under the heading for CID 1139 to 1435 1143 114.58 8.4.2.170q "with value "100" Change to: 'with value Accepted- indicating 100% 100 indicating 100% busy level and busy level and value 0 TGah editor to make value "0" indicating idle (values changes shown in indicating idle 101 to 255 are 0576r1 under the (value "101" to reserved).' heading for CID 1139 "255" are to 1435. reserved)." Typo. Also the double quotes are not needed when indicating values. 1435 113.39 8.4.2.170q There is not any Add a cumulative Revised- cumulative metric metric to the element defined for Relay Add a behavior Discovery description at STA Procedure, that side about how to can be used choose a Relay among directly at the multiples candidates STA side in Relay Discovery Procedure (subclause 9.48.5) TGah editor to make changes shown in 0576r1 under the heading for CIDs 1139 to 1435. CIDs 1139,1140,1141,1142,1143,1435 8.4.2.170q Relay Discovery element TGah editor: Change the figure 8-401dr ( page130 Line 32) by reducing the table cell margin to zero, and choosing a smaller font.
1141 114.01 8.4.2.170q "is one octet in length" - redundant Remove redundant size specifiers from the text in this subclause. Rejected- There are many instances such as ”1 octet in length” in baseline draft too. 1142 114.44 8.4.2.170q I don't see any text on how the "DL Max Data Rate field" is used. Is it a commitment by the AP, or a constraint on the non-AP STA? Add behaviour in clause 9/10 that indicates how the values in this field affect AP and non-AP STA behaviour. Ditto for the other data rate fields of this structure. Revised- Add a behavior description in Relay Discovery Procedure (subclause 9.48.5). TGah editor to make changes shown in 0576r1 under the heading for CID 1139 to 1435 1143 114.58 8.4.2.170q "with value "100" indicating 100% busy level and value "0" indicating idle (value "101" to "255" are reserved)." Typo. Also the double quotes are not needed when indicating values. Change to: 'with value 100 indicating 100% busy level and value 0 indicating idle (values 101 to 255 are reserved).' Accepted- TGah editor to make changes shown in 0576r1 under the heading for CID 1139 to 1435. 1435 113.39 8.4.2.170q There is not any cumulative metric defined for Relay Discovery Procedure, that can be used directly at the STA side Add a cumulative metric to the element Revised- Add a behavior description at STA side about how to choose a Relay among multiples candidates in Relay Discovery Procedure (subclause 9.48.5) TGah editor to make changes shown in 0576r1 under the heading for CIDs 1139 to 1435. CIDs 1139,1140,1141,1142,1143,1435 8.4.2.170q Relay Discovery element TGah editor: Change the figure 8-401dr ( page130 Line 32) by reducing the table cell margin to zero, and choosing a smaller font.
11-14-0576-01-00ah-lb200-mac-resolution-clause-9-48-5-8-4-2-170q.docx