CID i-13 CID Page Line Comment Proposed Change Resolution Status clause # i-13 25 6.2.10 64 The Number of Also can the Rejected subframes fields is 9-bit number of field, but this clams that subframes be 0? I TG3e group has up to 256 subframes can think the 256 decided that 256 be aggregated into a subframes limitation subframes are single frame. Is this was from the enough for meaning that the values previous format of aggregation, and from 0-0x100 are valid the secure the decision is for the Number of aggregated data regardless of the Subframes field, but frame payload, secure subframe values 0x101-0x1ff are where there was counter. Since not. separate 8-bit there is a frame secure subframe with 0 subframe counter. I think this (such as got removed in 9 bit is current version, so allocated to now we can have indicate subframe full 511 subframes number 0~256. in both non-secured and secured aggregated frames. Also as SFC is incremented for each subframe, the secure subframe counter is no longer used to generate nonce, this also does not set this requirement. CID i-217 and i-218 CID Page Line Comment Proposed Change Resolution Status clause # 24 6.2.7.1 43 "6.2.7.1 Frame Payload Change "in the Revised field" in the baseline piconet" to "in the should be amended to piconet or pairnet". See the proposed include pairnet. Add reference to text change in the secure MAC frame body format for HRCP.
CID i-13 CID Page Line # Comment Proposed Change Resolution Status i-13 25 6.2.10 64 The Number of subframes fields is 9-bit field, but this clams that up to 256 subframes can be aggregated into a single frame. Is this meaning that the values from 0-0x100 are valid for the Number of Subframes field, but values 0x101-0x1ff are not. Also can the number of subframes be 0? I think the 256 subframes limitation was from the previous format of the secure aggregated data frame payload, where there was separate 8-bit secure subframe counter. I think this got removed in current version, so now we can have full 511 subframes in both non-secured and secured aggregated frames. Also as SFC is incremented for each subframe, the secure subframe counter is no longer used to generate nonce, this also does not set this requirement. Rejected TG3e group has decided that 256 subframes are enough for aggregation, and the decision is regardless of the secure subframe counter. Since there is a frame with 0 subframe (such as 9 bit is allocated to indicate subframe number 0~256. CID i-217 and i-218 CID Page Line # Comment Proposed Change Resolution Status 24 6.2.7.1 43 "6.2.7.1 Frame Payload field" in the baseline should be amended to include pairnet. Change "in the piconet" to "in the piconet or pairnet". Add reference to the secure MAC frame body format for HRCP. Revised See the proposed text change in clause clause
15-16-0687-01-003e-sb-comment-resolution-on-security-cids.docx