need to values for standardize consecutive how to TWT choose the requests. value for Dialog Token field at the TWT requesting STA, it is neccesary to specify that a dffierent value shalld be chosen between any consecutive TWT requests. Proposed Clause Comment Resolution Change 758 TXOP Clarify. One Rejected- sharing of the A Relay operation possible decides has to ways to whether work with is to reuse the TXOP beacon maximally sharing is collision MBCA, while used or avoidance RAW not. If the capability. protection Relay may work thinks that inconsistently the TXOP to generate sharing too much makes a ovarlapped beacon restricted collision, it windows. Or may not otherwise use the discard entire TXOP "Relay" sharing. concept. Proposed Clause Comment Resolution Change 759 "Sectorization" Change Rejected- is wrong "secttorization" Sectorization terminology to "areal is more here, for areal zoning", for general than or instance. terminologies.
need to standardize how to choose the value for Dialog Token field at the TWT requesting STA, it is neccesary to specify that a dffierent value shalld be chosen between any consecutive TWT requests. values for consecutive TWT requests. Clause Comment Proposed Change Resolution 758 TXOP sharing operation has to work with beacon collision avoidance capability. Clarify. One of the possible ways to is to reuse maximally MBCA, while RAW protection may work inconsistently to generate too much ovarlapped restricted windows. Or otherwise discard entire "Relay" concept. Rejected- A Relay decides whether the TXOP sharing is used or not. If the Relay thinks that the TXOP sharing makes a beacon collision, it may not use the TXOP sharing. Clause Comment Proposed Change Resolution 759 "Sectorization" is wrong terminology here, for areal or Change "secttorization" to "areal zoning", for instance. Rejected- Sectorization is more general than terminologies.