those bit positions in (in Draft 1.3), Figure 9-589ck. no entry ahs this type syntax. Suggesting to have a comment to update the syntax of table 9-262z, it seems out of place if QTP is the only one 5069 96.22 9.4.2.223 QTP setup frame as in comment Rejected: only contains Vendor Since the Specific Service Peer-to-peer Identifier, in order to operation may distinguish different or may not types of STA2STA belong to the operation, such as same service, NAN, DLS, and etc. even there is In dense collision, the environment, if many interference is DLS links try to limited to the contend for channel STAs of the in QTP period, they peer-to-peer may collide or operation. interferece with each other. 5340 96.54 9.4.2.224 The granularity of Express Period Counter: Period Offset, Offset, Interval and with part of Interval and Duration Duration in 32 us, the comment. is too coarse (1TU or similarly to MCCA. Since the 1024 us) while the Such unit provide a offset frame format allows range for these values field is to have values up to 32 us to 2s which is a anchor by 65535 TUs, i.e. good trade-off TBTT, longer than 1 minute, between granularity the offset which is hardly and scalability field is needed. reduced to one byte in TU. The interval field remains two bytes
those bit positions in Figure 9-589ck. (in Draft 1.3), no entry ahs this type syntax. Suggesting to have a comment to update the syntax of table 9-262z, it seems out of place if QTP is the only one 5069 96.22 9.4.2.223 QTP setup frame only contains Vendor Specific Service Identifier, in order to distinguish different types of STA2STA operation, such as NAN, DLS, and etc. In dense environment, if many DLS links try to contend for channel in QTP period, they may collide or interferece with each other. as in comment Rejected: Since the Peer-to-peer operation may or may not belong to the same service, even there is collision, the interference is limited to the STAs of the peer-to-peer operation. 5340 96.54 9.4.2.224 The granularity of Period Offset, Interval and Duration is too coarse (1TU or 1024 us) while the frame format allows to have values up to 65535 TUs, i.e. longer than 1 minute, which is hardly needed. Express Period Offset, Interval and Duration in 32 us, similarly to MCCA. Such unit provide a range for these values 32 us to 2s which is a good trade-off between granularity and scalability Counter: with part of the comment. Since the offset field is anchor by TBTT, the offset field is reduced to one byte in TU. The interval field remains two bytes