{"text_format":"1","workbook":"xlsx","n_sheets":8,"sheets":["Comments","Progress-Status","Categories","Detailed Status","To-Do","Historical Status","CAD","Sheet1"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":3,"comments":1,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Comments","index":0,"n_rows":1472,"n_cols":22,"rows_kept":1472,"cut":false,"hidden":false,"merged":[]}
["Comment ID","Comment #","Name","Style","Index #","Vote","Affiliation","Category","Page","Sub-clause","Line #","Comment","File","Proposed Change","Must Be Satisfied?","Disposition Status (Accepted, Rejected, Revised)","Disposition Detail","Category","Notes","Editor Status DONE, Ready, N/A)","Editor Notes","Assignee"]
[null,null,"Billy Verso",null,1016,"No","Qorvo","Editorial",9,"Introduction",9,"IEEE Std 802.15.4-2020 will need to change when the 4me revision is completed, might be good to highlight this also to make it stand out as something subject to change.",null,"Highlight/change the 2020 like is done on line 5","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1017,"No","Qorvo","Editorial",9,"Introduction",26,"empty numbered line",null,"delete it","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1018,"No","Qorvo","Editorial",9,"Introduction",29,"for next revision of the draft the 4me draft reference here will need to change",null,"change it appropriately.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,280,"No","Self","Editorial",9,null,8,"The ranging capabilities in the -2020 version were quite limited, most of the ranging capabilities were added in 802.15.4z-2020. ",null,"Change to refere to 802.15.4z amendment?","No",null,null,"TE",null,"ASSIGNED","This whole intro was copied from 802.15.4z…. When I copied in in I meant to revise but forgot, will need a larger review.","Editor"]
[null,null,"Tero Kivinen",null,281,"No","Self","Technical",13,2,18,"The RFC 1951 Deflate compression is only used by one optional feature, there is no need for normative reference, as not everybody who reads 802.15.4 needs to understand what deflate does. ",null,"Move IETF RFC 1951 to bibliography.","Yes","Rejected","In clause 10.39.4.6.3, it states that \"If compression is enabled (as indicated by the Compression field  CIR Taps field of each receive report shall be compressed individually using the DEFLATE compressed data format described in IETF RFC 1951. \" which is a normative requirement","MISC",null,"N/A"]
[null,null,"Billy Verso",null,1019,"No","Qorvo","Technical",13,"3,1",23,"the term \"hash\" is used in the text, a definition should be added.",null,"include a definition for the term \"hash\"","Yes",null,null,"MISC",null,"ASSIGNED",null,"Tero"]
[null,null,"Lei HUANG",null,1429,"Yes","Huawei","Editorial",14,"3.2",16,"RPA should stand for \"resolvable private address\" instead of \"resolvable private addresses\"",null,"as in comment","Yes","Accepted",null,"MISC",null,"DONE"]
[null,null,"Lei HUANG",null,1430,"Yes","Huawei","Technical",14,"3.2",20,"HRP-SDEV and SDEV actually refer to the same type of 4ab devices. HRP-SDEV seems a better name. ",null,"delete SDEV","Yes",null,null,"TE",null,"ASSIGNED",null,"Billy"]
[null,null,"Tero Kivinen",null,282,"No","Self","Editorial",15,6.3,1,"There is extra PDF index subsection entries 6.3.1. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,285,"No","Self","Editorial",15,"5.2.5",5,"This is first use of the RSS outside the headers, expand here. ",null,"Expand RSS here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1020,"No","Qorvo","Editorial",15,"5.2.5",5,"Other than in the heading, \"The RSS defined …\" is first use of the RSS acronym in the text so the full definition should appear too.",null,"Change to: \"The Ranging support service (RSS) defined …\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1021,"No","Qorvo","Technical",15,"6.6.1",15,"This clause in the base standard describes transmission  steps.  It needs to be amended to also cover compact frame transmission.",null,"Review and amend appropriately.  At the very least it need to refer to the appropriate security clause, but it may need other actions also.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1022,"No","Qorvo","Technical",15,"6.6.2",15,"This clause in the base standard describes reception steps.  It needs to be amended to also cover compact frame reception.",null,"Review and amend appropriately.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1023,"No","Qorvo","Technical",15,"6.6.2",15,"This clause in the base standard describes reception steps and tells us to discard frames with bad CRC.  Rather than having to amend and maintain this for every compact frame encoding that has MIC instead of CRC, (and complicating the MAC receive processing implementation in the process), suggest to add CRC as part of the compact frame definition in clause 7.3.7 and remove CRC from the Compact Frame Content field definitions of clause 10.38.10.",null,"To simplify the low level MAC processing in everyone's implementation, make the CRC a common mandatory part of all Compact Frames. i.e. Add CRC are the end of the frame in Figure 1, and description text sub-clause in 7.3.7","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Kangjin Yoon",null,1413,"No","Spark Microsystems","Editorial",15,"6.6.3.3",17,"Typo",null,"Change \"Acknowledgment\" to \"Acknowledgement\"","Yes","Rejected","Acknowledgment is the spelling used throughout the base standard.","TE",null,"N/A"]
[null,null,"Tero Kivinen",null,284,"No","Self","Editorial",15,"6.6.3.3",24,"This is first use of HRP-EMDEV acronym, expand here. ",null,"Expand HRP-EMDEV here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,283,"No","Self","Technical",15,"6.6.3.3",25,"Why there is need for specific macEmdevImmAckAifsPeriod? The HRP-EMDEV will always use this different values regardless of mode (i.e., the high-rate pulse repetition frequency UWB PHY based enhanced modulations device will always use this) so it can be just be configured in the macSifsPeriod. ",null,"Or is it trying to say that high-rate pulse repetition frequency UWB PHY based enhanced modulations devices sometimes use this macEmdevImmAckAifsPeriod and sometimes uses macSifsPeriod? The HRP-EMDEV is device property, not a mode inside the device. Is the HRP-EMDEV supposed to be mode for devices not a device type itself?","Yes",null,null,"ACK",null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,1401,"No","Apple","Technical",15,"6.6.3.3","24-26","Fixing AIFS, but leaving SIFS, LIFS unchanged as 12 and 40 preamble symbols seems to be conflicting with the base standard requiring AIFS<SIFS<LIFS.",null,"Add definitions for SIFS and LIFS for HRP-EMDEV with adequate values.","Yes",null,null,"ACK",null,"ASSIGNED",null,"Ben"]
[null,null,"B. Rolfe",null,1322,"Yes","BCA","Editorial",16,"6.6.3.34",1,"The heading for clause 6.6.3.4 went missing. It would be nice to have it back. ",null,"If it can be found, insert it before the editing instruction",null,"Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,286,"No","Self","Editorial",16,"6.6.3.4",1,"Section 6.6.3.4 is missing header. ",null,"Add \"6.6.3.4 Retransmissions\" before editing instructions.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,287,"No","Self","Technical",16,"6.6.3.4",2,"This paragraph does not describe any mandatory to implement feature, move it to relevant clause in 10.44. ",null,"Move to 10.44.2, or most likely the text in 10.44.2 already covers this case, so this can be removed.","Yes","Rejected","This is a step in the mandatory retransmission feature when the optional SSBD is being used.  There needs to be this coupling between the two procedures.","SSBD",null,"N/A"]
[null,null,"Larry Zakaib",null,1427,"Yes","Spark Microsystems","Technical",16,"6.6.3.4","2,3","The wording can be more clear. \"When the SSBD channel access method, described in 10.44, is used for retransmission, isRetransmissionAttempt shall be set to TRUE when invoking SSBD\"",null,"Change to: \"When the SSBD channel access method, described in 10.44, is used, and when persistence is TRUE, when the packet is a retransmission, isRetransmissionAttempt shall be set to TRUE when invoking SSBD\"",null,"Revised","Change to: \"When the SSBD channel access method, described in 10.44, is used, and when macSsbdPersistence is enabled, when the packet is a retransmission, isRetransmissionAttempt shall be set to TRUE when invoking SSBD\"","SSBD",null,"DONE"]
[null,null,"Tero Kivinen",null,288,"No","Self","Technical",16,"7.2.2",9,"The format proposed for the frame type 100 is not very compact, and does not intended to be compact. ",null,"Rename to something that actually describes what the new format is trying to do (legacyblecopiedstuff?).","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,289,"No","Self","Technical",17,"7.3.7",1,"Is this new compact frame format really meant to be implemented by every single 802.15.4 device? It is now in part of clause 7 which is mandatory to implement parts. ",null,"Move to 10.xx and clearly mark that this is optional. In that case add similar footnote to table 7-1 than what there already exists for Fragment and frag frame types describing where the format can be found.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,290,"No","Self","Editorial",17,"7.3.7.1",3,"Figure number is wrong. ",null,"Figure numbers should indicate where the figure is to be added in the standard, thus it should be 7-20a, as this figure 1 are between figures 7-20 and 7-21 of the base standard.","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,291,"No","Self","Technical",17,"7.3.7.1",3,"Adding a new frame format that does not allow security or privacy in 2024 is really bad. We must not do such thing. Security and privacy is required for the modern 802.15.4 operating environments, especially on the phones etc. Privacy cannot be provided without security, and the currently defined security and privacy features in compact frames are not suitable for the use these frames are intended for. ",null,"Define compact frame format so that it can use the 802.15.4 security and reuse the privacy to be defined in TG4ac. It is known that IEEE has long standing tradition of making insecure and broken standards, but lets try to get away from that tradition.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1024,"No","Qorvo","Technical",17,"7.3.7.1",4,"Other than the extended frame type which is assigned to TIA to define, Compact frames are the first frame type without a MFR specifying a CRC, (and I expect TIA actually specify a CRC are the end of their frames also). Not having a CRC complicates the first level of frame filtering since the individual  specific decoding of Compact Frame ID and the Message Control internals of the frame have to be decoded before knowing whether there is a CRC or a MIC.",null,"Add a FCS/CRC as is done for all other frame types, in the standard. Even secured frames with a MIC have CRC as first level of filtering. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1344,"No","Qualcomm","Editorial",17,"7.3.7.1",4,"Change Figure number based on baseline 15.4 draft.",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1345,"No","Qualcomm","Editorial",18,"7.3.7.2",1,"Change Table number based on baseline 15.4 draft.",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,101,"No","Huawei","Technical",18,"7.3.7.4",1,"Compact Frame ID 30 is reserved for vendor specific use but the format is not defined. A lack of common format will lead to interoperability issues between different vendors.",null,"Define the Compact Frame Content field for the vendor specific compact frame. The vendor specific Header IE Content field can be used as a reference. The first 3 octets carry the Vendor OUI field while the rest of the Content field is left to the vendors to design.","Yes","Revised","Doc 15-24-0379-00-04ab-proposed-resolution-for-vendor-specific-compact-frame.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,292,"No","Self","Editorial",18,"7.3.7.4",1,"Table number is wrong. ",null,"The table numbers should indicate where in the table should be placed in the base standard, in this case it should be Table 7-5a, as this table will be between tables 7-5 and 7-6 of the base standard.","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,293,"No","Self","Technical",18,"7.3.7.4",1,"If there is vendor specific use reserved then there should be format specified for it (having vendor ID in the beginning etc). If this is just reservation then there is no need to explicitly reserve specific number for it, as if there is number reserved but no format, then vendors might start using it using their own formats causing interoperability issues in the future. ",null,"Remove \"Reserved for vendor specific use\" and change 21-29 to 21-30 on the previous line. Defining new vendor specific format for this frame seems unneeded as we already have several other frame types which can be used for vendor specific content.","Yes","Revised","Doc 15-24-0379-00-04ab-proposed-resolution-for-vendor-specific-compact-frame.docx","NEWFR",null,"DONE"]
[null,null,"B. Rolfe",null,1323,"Yes","BCA","Editorial",18,"7.3.7.4",1,"Table and figure numbers need to be updated to align with the base standard (RevE). This should be possible at this point in time.",null,"Update figure and table numbers",null,null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1025,"No","Qorvo","Technical",18,"7.3.7.4",2,"\"Reserved for vendor specific use\".  Elsewhere in 802.15.4 vendor specific use is allowed and understood through the use of the Vendor OUI, but compact frames do not include such a field, so the is no way to allow vendor specific functionality without potential conflicts.",null,"Define how this can be used / interpreted by individual vendors without conflict, or, change to a simple \"Reserved\".","Yes","Revised","Doc 15-24-0379-00-04ab-proposed-resolution-for-vendor-specific-compact-frame.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,295,"No","Self","Editorial",19,"7.4.2",1,"There is extra PDF index entries in subsection 7.4.2. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,294,"No","Self","Editorial",19,"7.4.4",4,"We are not incrementing reserved ID range, we are making it smaller. ",null,"Change to say \"adjusting the reserved ID range accordingly\". Also remove empty line before the \"Reserved\" on the table 7-9, and do not use underlined \"0x68\" for reserved line, but use something like <ANA> instead, as the actual value will depend on the ANA allocations.","No","Revised","Change the editing instructions to say \"adjusting the reserved ID range accordingly\", and in the table (Table 7-9) remove boththe final line giving the \"Reserved\" ID range and the empty line before it.","TE",null,"DONE"]
[null,null,"Billy Verso",null,1026,"No","Qorvo","Technical",19,"7.4.4",6,"In Table 7-9 the \"Use Description\" reference for these new IEs  is not present.  If they don't have a described use then they should be removed. ",null,"Determine the most relevant clause reference for each of these IEs and insert it into the table.","Yes",null,null,"MAC",null,"ASSIGNED",null,"Ben"]
[null,null,"Billy Verso",null,1027,"No","Qorvo","Editorial",19,"7.4.4",6,"In Table 7-9 there is a blank row",null,"delete it","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,296,"No","Self","Editorial",20,"7.5.1",3,"We are not incrementing reserved ID range, we are making it smaller. ",null,"Change to say \"adjusting the reserved ID range accordingly\". Also do not use underlined \"0x2d\" for reserved line, but use something like <ANA> instead, as the actual value will depend on the ANA allocations.","No","Revised","Change to say \"adjusting the reserved ID range accordingly\", and in the table (Table 7-11) remove the final line giving the \"Reserved\" ID range.","TE",null,"DONE"]
[null,null,"Billy Verso",null,1028,"No","Qorvo","Technical",20,"7.5.1",5,"HRP UWB Association seems badly named, before this was added networks could be formed using the HRP UWB PHY using the normal 15.4 coordinator association request, perhaps after doing an active or passive scan, and presumably that association mechanism is still open for HRP UWB PHY to use.  Similarly why can't this new command mechanism be used by other UWB PHY or any other PHY using the AC IE in a slotted protocol to advertise its willingness accept such association. Suggest to call this \"Controller Association\"",null,"Search for \"HRP UWB Association\" and replace with \"Controller Association\". ","Yes","Accepted",null,"MAC",null,"DONE"]
[null,null,"Tero Kivinen",null,299,"No","Self","Editorial",21,"8.2.4",1,"There is extra PDF index entries for subsections 8.2.4, 8.2.7 and 8.2.10. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,297,"No","Self","Editorial",21,"8.3.2.2",4,"The editing instructions does not indicate where in the table 8-27 those elements are supposed to be added. Also editing instructions talks about parameters, but they are elements of teh structure. ",null,"Remove the \"...\" lines from the 8-27 table, and change editing instructions to say \"Insert new elements at the end of the DataRequestRangingDescription structure, as shown:\".","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,300,"No","Self","Technical",21,"8.3.2.2",5,"The MmsRxClockTrackInterval description does not define the units of the value. Is it in ranging counter time units or what? ",null,"Define the units of the MmsRxClockTrackInterval.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,301,"No","Self","Technical",21,"8.3.2.2",5,"The MmsRxClockTrackOffset description does not define the units of the value. Is it in ranging counter time units or what? ",null,"Define the units of the MmsRxClockTrackOffset.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1029,"No","Qorvo","Technical",21,"8.3.2.2",5.7,"Need to add a little more to the description of MmsRxClockTrackInterval to say what it is.",null,"Add: \"The MmsRxClockTrackInterval gives a count of the time units over which the clock offset was measured during the\nreception of the packet that was used to estimate the remote device's clock offset\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1030,"No","Qorvo","Technical",21,"8.3.2.2",5.9,"Need to add a little more to the description of MmsRxClockTrackOffset to say what it is.",null,"Add: \"The MmsRxClockTrackOffset gives a count of the time units slipped or advanced by the radio tracking system over the course of the MmsRxClockTrackInterval used to estimate the remote device's clock offset\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,17,"Yes","STMicroelectronics","Technical",21,"8.3.2.2",6,"In Table 8-27 the description of MmsRxClockTrackInterval and MmsRxClockTrackOffset are the same. More detail is needed for the clock offset for the fragment receptions",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,18,"Yes","STMicroelectronics","Technical",21,"8.3.2.2",6,"We propose to add a note about RangingTxTime used in MMS. It shall be in RCTU",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,139,"No","Huawei","Technical",21,"8.3.2.2",6,"The definition and unit of MmsRxClockTrackInterval and MmsRxClockTrackOffset are not clear",null,"Specify the definition and unit of MmsRxClockTrackInterval and MmsRxClockTrackOffset","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pablo Corbalán Pelegrín",null,1293,"No","NXP Semiconductors","Editorial",21,"8.3.2.2",8,"\"The while the …\"",null,"Remove initial \"The\" and set to \"While the MmsRangingRxOnTime …\"","No","Accepted",null,"TE",null,"DONE"]
[null,null,"B. Rolfe",null,1324,"Yes","BCA","Technical",21,"8.3.2.2",8,"\"may\" is the wrong word in an informative note (see 1.3).  Avoiding misuse of \"may\" is hard sometimes, but it states an optional requirement so not allowed in an informative note.",null,"Change \"may\" to \"might\"",null,"Accepted",null,"MAC",null,"DONE"]
[null,null,"Lei HUANG",null,1431,"Yes","Huawei","Editorial",21,"8.3.2.2",8,"There is a grammar error in the sentence that \"The while the MmsRangingRxOnTime parameter is in ranging counter time units\".",null,"change \"The while\" to \"While\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Henk de Ruijter",null,1466,"Yes","Silicon Labs","Editorial",21,"8.3.2.2",8,"Typo, \"The\" should be deleted",null,"Change \"The while the…\" to \"While the…\"",null,"Accepted",null,"TE",null,"DONE"]
[null,null,"Stephan Sand",null,1470,"Yes",null,"Editorial",21,"8.3.2.2",8,"Sentence starts with \"The while\"",null,"Please replace the sentence with the following one: \nWhile the MmsRangingRxOnTime parameter is in ranging counter time units, the O-QPSK receiver may be unable to provide the arrival time of the poll or response Compact frames with this accuracy.",null,"Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,298,"No","Self","Technical",21,"8.3.3",12,"In table 8-29 DataRate there is text \", see note\" added, but the DataRate element of the TxOption cannot be described in the informational note. ",null,"Remove \", see note\" change.","Yes","Accepted",null,"MAC",null,"DONE"]
[null,null,"Mickael Maman",null,19,"Yes","STMicroelectronics","Technical",22,"8.3.3",1,"The MmsReceive parameters is confusing. When MmsReceive is FALSE, the interleaved MMS reception is not enabled and the MmsRangingRxOnTime, MmsRxClockTrackInterval, and MmsRxClockTrackOffset parameters are ignored. Nothing is said to ignore the TX.",null,"MmsReceive becomes MmsActive and change the description accordingly","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,20,"Yes","STMicroelectronics","Technical",22,"8.3.3",1,"Missing option to configure from which part of the packet the sensing is made",null,null,"Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Mickael Maman",null,21,"Yes","STMicroelectronics","Technical",22,"8.3.3",1,"Missing a field asking for the generation of the SYNC+SFD in the UWB driven MMS",null,"add in table 8-29 MmsUwbDriven | Boolean | TRUE, FALSE | For UWB MMS Ranging, this parameter is set TRUE if the SYNC+SFD fragment is present. FALSE, otherwise.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Huan-Bang Li",null,1435,"Yes","NICT","Editorial",22,"8.3.3",1,"The description on 'MmsReceive' in Table 8-28 includes an incompleted bracket.",null,"complete it or delete it.","Yes","Revised","Complete the bracketed phrase as: \", (where the transmitter is sending fragments),\"","TE",null,"DONE"]
[null,null,"Tero Kivinen",null,302,"No","Self","Technical",22,"8.3.3",3,"The DataRate description cannot be note, as that would make it informal, thus we would not have any normative description for DataRate. ",null,"Remove \"NOTE--\". Note, that the rest of the changes on the line are already changed in base standard, thus D06 draft of base standard already says \"For the DataRate element of the TxOptions structure, the following values are used:\", thus lines 2-3 can be removed.","Yes","Accepted",null,"MAC",null,"DONE"]
[null,null,"Mickael Maman",null,22,"Yes","STMicroelectronics","Technical",22,"8.3.3",6,"missing data rate element of txOptions structure for OQPSK PHY",null,"Add \"For OQPSK PHY, value 1-8 are valid and are defined in Table 58\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Youngwan So",null,927,"Yes","SAMSUNG Elec.","Editorial",23,"8.3.4",9,"The description column of DstAddrMode looks wrong. It should be \n\"The source addressing mode for this MPDU\" rather than \n\"The destination addressing mode for this MPDU\"",null,"Change from\n\"The source addressing mode for this MPDU\"\nto\n\"The destination addressing mode for this MPDU\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,304,"No","Self","Technical",23,"8.3.4",16,"There is no point of using MCPS-DATA.request primitive to send compact frames, as almost none of the parameters given to the MCPS-DATA.request are valid when sending compact frames. ",null,"Create new MCPS-COMPACT.request primitive and add it to the 10.38.x MAC Services section.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1031,"No","Qorvo","Editorial",23,"8.3.4",16,"Two \"defined\" in the line, I think the first one should be a \"specified\"",null,"Change \"with its contents defined using the\" to \"with its contents specified using the\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Rojan Chitrakar",null,102,"No","Huawei","Technical",23,"8.3.4",17,"SrcAddr is not present in the data.request primitive",null,"Delete SrcAddr here and clarify how the source address is set in the compact frame.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1032,"No","Qorvo","Technical",23,"8.3.4",17,"\"For Compact frames, if the SrcAddrMode and DstAddrMode is COMPACT….\" is in a paragraph only for compact frames, (where SendFrameType == COMPACT_FRAME\").  I think here the addressing mode can only be NONE or COMPACT",null,"Specify that NONE/COMPACT are only valid values for compact frames.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1033,"No","Qorvo","Technical",23,"8.3.4",18,"\"SrcAddr or DstAddr contain the Compact frame address information\"… needs more detail.",null,"Specify how SrcAddr and DstAddr parameters of this primitive map into the RPA Hash and RPA Prand fields of the transmitted compact frame, (assuming that is what is meant by this line, or otherwise clarify what is meant).  Use separate sentences, i.e., \"When SrcAddrMode is COMPACT, the SrcAddr parameter ....\" and \"When DstAddrMode is COMPACT, the DstAddr parameter ...\" ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,303,"No","Self","Technical",23,"8.3.4",19,"The note says that IE list parameters are not applicable, but there are also lots of other parameters which are not applicable for compact frames. For example DstPanID, SecurityParas, most of the TxOptions. The end of the table 8-30 already has NOTE saying that some values may be unsupported etc, so do we need another note here? ",null,"Remove \"Note, that the IE list parameters ...\" text.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,309,"No","Self","Editorial",23,"8.3.4",22,"This is first time of using MMS acronym, expand here. ",null,"Expand MMS here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1034,"No","Qorvo","Editorial",23,"8.3.4",22,"Sentence is a bit wordy.  Could be simplified as two sentences.",null,"Change to: \"The MmsReceive parameter of TxOptions applies to UWB MMS packet transmissions.  When MmsReceive is TRUE it enables the reception of UWB MMS fragments interlaced between the transmitted UWB MMS fragments.\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Shang-Te Yang",null,923,"Yes","Apple","Editorial",23,"8.3.4",23,"Interlaced is only used here once throughout the document. ",null,"Change interlaced to interleaved ","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,308,"No","Self","Technical",23,"8.3.4",25,"The actual description of the interleaved transmission should be in somewhere else, and it should have figure explaining different cases (MmsRangingRxOnTime > RangingTxTime vs RangingTxTime > MmsRangingRxOnTime etc). ",null,"Move this paragraph to 10.x and just add reference to it. Include figures explaining the interleaved transmission (or if this is already described somewhere move text there, and just add reference).","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,306,"No","Self","Technical",23,"8.3.4",26,"The RangingTxTime can be either in RCTUs or RSTUs. Does the TxTimeSpecified also affect the MmsRanginRxOnTime units? ",null,"Specify the MmsRangingRxOnTime in relation to the different values of the TxTimeSpecified enumeration which affects units of the RangingTxTime.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,305,"No","Self","Technical",23,"8.3.4",27,"This does not specify the time reference for the MmsRangingRxOnTime related to the other timing. Is it same as RangingTxTime (i.e., reference to the running ranging counter units as defined in 10.29.1.4) or something else. ",null,"Define the reference time for the MmsRangingRxOnTime.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,307,"No","Self","Technical",23,"8.3.4",28,"The text says that MmsRxClockTrackInterval and MmsRxClockTrackOffset specify the clock offset, but it does not exactly specify how they specify it. ",null,"Add description how MmsRxClockTrackInterval and MmsRxClockTrackOffset affect the timing of the MmsRanginRxOnTime. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Lei HUANG",null,1432,"Yes","Huawei","Technical",23,"8.3.4",28,"It is unclear how MmsRxClockTrackInterval together with MmsRxClockTrackOffset can be used to specify the clock offset for the fragment receptions.",null,"It should be clarified in the draft standard how MmsRxClockTrackInterval together with MmsRxClockTrackOffset can be used to specify the clock offset for the fragment receptions.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,312,"No","Self","Technical",24,"8.3.4",6,"What is this text \"nominally separated by 600 RSTU\" trying to say? ",null,"If there is requirement that RangingRxTime and MmsRangingRxOnTime are separated by certain time, add text specifying that relation, if there is not what is the point of giving some nominal value?","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1035,"No","Qorvo","Editorial",24,"8.3.4",6,"\"When MmsReceive is FALSE, the interleaved MMS reception...\" would be better to mention UWB and fragments, and the initial \"the\" would be better removed to improve readability.",null,"Change to: \"When MmsReceive is FALSE, interleaved UWB MMS fragment reception...\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,311,"No","Self","Editorial",24,"8.3.4",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,313,"No","Self","Technical",24,"8.3.4",11,"There is only very few valid values for CompactMessageControl so there is no point of sending it as 8-bit integer. It is possible to combine CompactFrameId and CompactMessageControl to 6-bit value while allowing all currently possible CompactFrameId and CompactMessageControl combinations. Combining those two to one value would also allow using of the existing frame formats with one extra octet but include support for extensibility, security, privacy etc which are not provided by the compact frame format (for example use MAC Command Frame format with 2 octet MHR (no addressing in header) and allocate those bit less than 60 different CompactFrameID and CompactMessageControl combinations as separate MAC Commands. ",null,"Combine CompactFrameID and CompactMessageControl to one integer, and transmit that one byte instead of current Message Control field. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1036,"No","Qorvo","Technical",24,"8.3.4",13,"The CompactMessageContent parameter is very loose in defining as set of octets what the content that clause 10.38.9 is defining in great detail. What is the role of the MAC here? Does it just send these octets blindly?",null,"Separate CompactMessageContent into a set of parameters needed to allow the MAC to construct the appropriate message (from 10.38.9), and add a detailed description of what the MAC does with each of the parameters supplied in this primitive.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,310,"No","Self","Editorial",24,"8.3.5",10,"Table reference number is wrong. ",null,"Fix the number to point to real table number.","No","Rejected","Seems correct already, so nothing to fix.","TE",null,"N/A"]
[null,null,"Tero Kivinen",null,314,"No","Self","Technical",24,"8.3.5",17,"Ranging counters are enabled in the transmission if the DataRequestRangingDescriptor has Ranging set to true. If Ranging is not true, then ranging counters are disabled, thus there is no counter to report. ",null,"Most likely there needs to be separate setting in the DataRequestRangingDescriptior to enable ranging counters even when ranging is not used, and when those frames are transmitted the next higher layer needs to set that setting on. Technical\\nThe current text does not work as the ranging counters are not enabled unless the Ranging is set true. Instead of adding this text to MCPS-DATA.confirm add new element to the DataRequestRangingDescriptor where you enable ranging counters even when you are not doing ranging, and add text to those compact frames saying that they need to set that element to true.","Yes",null,null,"MAC",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1037,"No","Qorvo","Technical",25,"8.3.4",26,"This MCPS-DATA.indication primitive seems to be missing parameters to deliver the compact frame content which is presumably required. (I note here also that having to interact with a layer above is a reason to rationalise the compact messages to have much fewer types and options, with more logical presence bits rather than an amorphous format controlled by arbitrary Message Control values.)",null,"Add parameters to MCPS-DATA.indication to allow the MAC to deliver whatever compact frame content is needed to the upper layer. Otherwise if the MAC is autonomously doing things in response to compact frame reception, we probably need some new indication and response primitives to allow the upper layer to be informed and control/authorise those actions, and/or, PIB attributes to configure those items of autonomous behaviour where there are optional or variable behaviours needed.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,103,"No","Huawei","Technical",25,"8.3.6",19,"MCPS-DATA.indication should include the Compact frame contents that are supposed to be passed up to higher layers, e.g.: passthrough data, Reply Time, Round-Trip Time etc. In fact, the entire Message Content field could be passed as done in the data.request.",null,"Add the Compact frame contents that are supposed to be passed up to higher layers in the MCPS-DATA.indication","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,315,"No","Self","Technical",25,"8.3.6",22,"Unless there is ranging enabled for the received packet the ranging counters are not running, thus there is no counters to report. If those frames are ranging frames then the counters are automatically already filled in. ",null,"Why are those few frames special cases? Why they can't use the default ranging frame processing. Remove this text and just make those frames to be processed just like other ranging frames.","Yes",null,null,"MAC",null,"ASSIGNED",null,"Billy"]
[null,null,"Mickael Maman",null,23,"Yes","STMicroelectronics","Technical",25,"8.3.6 ",13,"In the rangingReportDescriptor introduced in the 802.15.4me, clarify the fields description when MMS fragment report",null,"When RSF:\n- TxCounter: RMarker at the end of the fragment\n- RxCounter: RMarker at the end of the fragment\n\nWhen RIF:\n- TxS0RangingCounter: \n- TxS1RangingCounter:\n- RxS0RangingCounter:\n- RxS1RangingCounter: ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,24,"Yes","STMicroelectronics","Technical",25,"8.3.6 ",13,"In the rangingReportDescriptor introduced in the 802.15.4me, add the fields for MMS fragment report",null,"Field proposal:\n- isMmsFrag\n- MmsFragId\n- MmsFragType (RIF / RSF)","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1038,"No","Qorvo","Technical",26,"9.3.4",6,"In the secure frames any passthrough data should be encrypted. Securing the MAC payload, i.e. data from the upper layer, is a specified functionality of the 15.4 MAC.  Data confidentiality and authenticity should apply to the passthrough data.",null,"Alter text so that the passthrough data is in the encrypted/private part of the frame, for all secured frame types with passthrough data.  Also make sure that there is a secured version available of any compact frame with passthrough data.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,316,"No","Self","Editorial",27,"9.2.12",1,"There is Table 3 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,317,"No","Self","Technical",27,"9.2.12",3,"There must be a way to secure all compact frames, not only certain specific frame types. If those frames are used to transmit any data over the air, there must be a way to secure them. ",null,"Add format for adding security for all compact frames.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1039,"No","Qorvo","Technical",27,"9.2.12",8,"\"This procedure does not apply to Compact frames that are not listed above.\", should perhaps state more clearly that other compact frames cannot be secured, since neither procedures of 9.2.12 nor 9.2.2 apply.",null,"Add at the end of the line, \", i.e., other Compact frames can not be secured.\"","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1040,"No","Qorvo","Technical",27,"9.2.12",13,"The \"extended address\" here (as described in 10.38.9.2.3) may be the address of the destination, what information in the MCPS-DATA.request does the MAC use to know which extended address to use.",null,"Clarify how this is determined, either here or in 10.38.9.2.3, with reference to the appropriate MCPS-DATA.request parameter.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1041,"No","Qorvo","Technical",27,"9.2.12",18,"If security level is zero here, there will be no MIC and the defined secured frame will not even have a CRC.",null,"Add a CRC to these frame types.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Rojan Chitrakar",null,104,"No","Huawei","Technical",27,"9.2.12",29,"relative ranging block should be relative block as per 10.32.3.5 Hyper block mode.",null,"replace relative ranging block with relative block","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Rojan Chitrakar",null,105,"No","Huawei","Technical",28,"9.2.12",4,"Passthrough field should also be included in the fields to be secured.",null,"Add Passthrough field in the Private Payload field column for all applicable rows and make all necessary changes in the draft to enable the Passthrough field to be secured.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,318,"No","Self","Editorial",28,"9.2.12",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,319,"No","Self","Technical",28,"9.2.12",5,"Why are the passthrough fields open payload fields? I would assume that we would like to encrypt communication between upper layers. I can see that Message Control field and Key ID fields must be open payload field, but why do every other field be open? ",null,"Change Open Payload field to be specified as list of fields, i.e. \"Message Control field and Key ID field\", and move the \"all other fields\" to private payload fields, i.e., make it encrypted by default, not encrypted as an exception. ","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1042,"No","Qorvo","Technical",28,"9.2.13",13,"\"This procedure does not apply to Compact frames that are not listed above.\", should perhaps state more clearly that other compact frames cannot be secured, since neither procedures of 9.2.12 nor 9.2.2 apply.",null,"Add at the end of the line, \", i.e., other Compact frames can not be secured.\"","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1043,"No","Qorvo","Technical",28,"9.2.13",13,"Arguably to have secure ranging it may be necessary to secure many or all of the other packets involved in controlling the ranging exchange. In this case it would be better to have a generic way to apply security. One way to do this is to sacrifice a bit of  the HASH address say to signal a secured frame. This then could signal the inclusion of an appropriate security header in a similar way to the base standard MAC.  Then we would not need to have separate security procedures or separate secured versions of each frame.",null,"Make it possible to secure all frames, as described in the comment, and revise the procedures accordingly.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,320,"No","Self","Technical",28,"9.2.13",17,"This system assumes there is exactly one security level possible for the device at one time, this makes it impossible to implement devices who want to talk to multiple devices if those devices happen to use different security levels. ",null,"Perhaps the security level should be tied to the key, i.e., when we know the sender and the key used, we could use security level tied to that specific key instead of global security level. Either add support for multiple security levels, or add description of that limitation.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,321,"No","Self","Technical",29,"9.2.13",11,"How does the recipient of the frame know the originator of the compact frame? The compact frames in question only have either initiator or the responder RPA hash, so it needs to somehow map that to the extended address of the originator. ",null,"Describe how the initiator RPA hash and responder RPA hash are mapped to the extended address of the originator.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1044,"No","Qorvo","Technical",29,"9.2.13",11,"It is not immediately apparent to me where to get the \"extended address of the originator\".  Also, does this work for group addressing?",null,"Add to the line some additional text to indicate where/how this is address is retrieved .","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,322,"No","Self","Technical",29,"9.2.13",15,"The output fields of KeySource and KeyIndex are not yet initialized here, so they can't be used when searching for the key. The step c could in theory fill in the KeySource provided it has a way of mapping the RPA hashes extracted from the frame to extended address, but KeyID has not yet been parsed. ",null,"Add step between b and c that will parse the frame and fill in the KeyID and KeySource fields that can be used in c and d steps.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,323,"No","Self","Technical",29,"9.2.13",18,"How does both of these modes (hyper block mode and non-hyper block mode) make sure that there can be only one transmission during the slot? ",null,"Add reference to the point where there is a restriction that any device can only send one frame per slot. This restriction is requirement for the security, thus it needs to be mandated by the specification.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Rojan Chitrakar",null,106,"No","Huawei","Technical",29,"9.2.13",19,"relative ranging block should be relative block as per 10.32.3.5 Hyper block mode.",null,"replace relative ranging block with relative block","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1045,"No","Qorvo","Technical",30,"9.2.13",7,"Given this note and the one on line 14, it is worth also mentioning what frames/formats are necessary to use to ensure block, round and slot indices are aligned.",null,"Specify the Compact Frame formats used to signal these indices.  Maybe also mandate their use?","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1046,"No","Qorvo","Technical",30,"9.2.13",7,"If security / reply attack protection is relying on block, round and slot indices, the frames used to signal these also need to be secured.",null,"Include security for those frames also.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,324,"No","Self","Editorial",30,"9.3.2.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,234,"No","MediaTek","Technical",30,"9.3.2.4",6,"A compact frame could occupy multiple slots and multiple slot indices.  ",null,"Add a clarification that the slot index in Fig 3,4 refers to the slot at the start of a compact frame ","No",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,325,"No","Self","Editorial",30,"9.3.2.4",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,328,"No","Self","Editorial",30,"9.3.2.4",6,"The range for 0x00 is wrong. ",null,"Change 24-39 to 32-39.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Alex Krebs",null,1383,"No","Apple","Technical",30,"9.3.2.4",6,"Typo in Bits",null,"Change 24 to 32","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,327,"No","Self","Technical",30,"9.3.2.4",7,"This requirement is needed for the security of the system, so it can't be in the informal note. ",null,"Add text saying that different key shall be used for each block structure setups.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Rojan Chitrakar",null,107,"No","Huawei","Technical",30,"9.3.2.4",11,"relative ranging block should be relative block as per 10.32.3.5 Hyper block mode.",null,"replace relative ranging block with relative block","Yes","Accepted","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,326,"No","Self","Editorial",30,"9.3.2.4",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,329,"No","Self","Editorial",31,"9.3.4.3",6,"This is first use of RPA. Expand here. ",null,"Expand RPA here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,331,"No","Self","Technical",32,"9.5.1",1,"How is the secCompactFrameSecurityLevel negotiated? It is global to device, so it can't be negotiated per device or per network. ",null,"Add reference where the security level for compact frames are negotiated.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1047,"No","Qorvo","Technical",32,"9.5.1",1.2,"secCompactFrameSecurityEnabled seems superfluous since there are specific \"secure\" compact frames.  On RX side when these form of frames are received they should be validated and discarded. Or maybe we need to add text to make the non-secure ones be discarded if security is enabled?  On TX side, I assume that the next higher layer is involved in the decision to send the report so again it can choose whether to send secure/unsecure ones?",null,"In it is not needed delete it or describe some the uses cases where it has a role. Suggest to do this in a new high-integrity  (not called secure) MMS section of 10.39.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1048,"No","Qorvo","Technical",32,"9.5.1",1.5,"The secCompactFrameSecurityLevel range references table 9-6 which includes bits to be sent in the security header so that receiver knows the security level to be used for decoding the frame. Is such a field needed for secured Compact frames?  The Key ID octet could be reduced to 5 bits to carry this in the other 3 bits.",null,"If it is not needed then the description should say \"to be used both in securing outgoing compact frames and processing incoming secured compact frames,\"  Or perhaps we need separate TX and RX values if this can be asymmetric with different capability in TX and RX devices.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1049,"No","Qorvo","Technical",32,"9.5.1",1.6,"Are all 8 levels here applicable? Do we need this flexibility, if not perhaps a single level could be specified, which would reduce the testing needed for validation of products and for interworking tests.",null,"Consider whether all 8 levels are applicable/needed and if not specify only those that are.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1050,"No","Qorvo","Technical",32,"9.5.1",1.7,"The secCompactFrameSecurityLevel description says the value is \"negotiated for Compact frames\".  ",null,"If a negotiation mechanism is part of the standard, add a reference to the clause where it is described. Otherwise say that this is decided via out of band means.  ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,330,"No","Self","Editorial",32,"9.5.11",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,332,"No","Self","Technical",32,"9.5.11",6,"To be consistent with other tables (for example 9-12)  the Type of the secCompactFrameKeySource should be IEEE address. ",null,"Change 8 Octets to IEEE address.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,333,"No","Self","Technical",32,"9.5.11",6,"The key should also be associated with the Aead Algorithm as specified in the Table 9-9 to provide crypto agility. ",null,"Add Aead Algorithm to be associated with the key.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1051,"No","Qorvo","Technical",32,"9.5.11",7,"secCompactFrameKeyID says range is as described in\n10.38.9.3.21, but that clause does not give any range or size.  I think it is a single Octet so the range here is 0 to 255.  Good to clarify if same key ID might be used for a different link and decided based on RPA resolution also, or is unique.",null,"Change to say range is 0 to 255, and add text to indicate if appropriate that it shall be a unique number in the list, or if this is not the case that it needs to be qualified by some address resolution also.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Li Ma",null,204,"No","MediaTek","General",33,10,1,"There are numerous simulations in 802.15 and 802.11 sessions shown NB impact to wifi coex.  Suggest to adopt a mandatory LBT for NB transmission if aggregated NB duty cycle is more than a threshold",null,"as in comment","Yes",null,null,"CHA",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,275,"No","MediaTek","General",33,10,1,"There are numerous simulations in 802.15 and 802.11 in prior meetings shown NB impact to wifi coex.  Suggest to adopt a mandatory LBT for NB transmission if aggregated NB duty cycle is more than a threshold",null,"as in comment","Yes",null,null,"CHA",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,276,"No","MediaTek","General",33,10,1,"For applications using NB transmissions (e.g. data offload) with on-off cycles and if not performing LBT or power control, the duration of the off state should either be large enough to allow other technologies’ nominal channel occupancy time, or small enough to prevent other technology following LBT procedure from acquiring the channel and later being interfered",null,"as in comment","Yes",null,null,"CHA",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,334,"No","Self","Editorial",33,10.3,1,"There is extra PDF index subsection entry 10.3.1. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,338,"No","Self","Editorial",33,"10.21.6.1.2",6,"The editing instructions claims to change only first paragraph, but actually changes first two paragraphs. ",null,"Change \"initial paragraph\" to \"first three paragraphs\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1052,"No","Qorvo","Technical",33,"10.21.6.1.2",8,"Is the word \"UWB\" needed here, controller should be enough since the base standard defines a controller: as \"An ERDEV that controls the ranging and defines the ranging parameters by sending an RCM.\" ",null,"if the base standard definition is compatible with the type of device being associated with here, then delete \"UWB\", otherwise some new definition is needed for this to replace \"UWB controller\". Also review/rename the new parameter UwbControleeAssociation to ControlerAssociation (same page line 21 and in Table 10-104)","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,337,"No","Self","Technical",33,"10.21.6.1.2",20,"Adding new Uwb* parameters in the middle of DSME parameter is not good. ",null,"Move Uwb* after DSME parameters i.e. at the end of parameter list.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,335,"No","Self","Technical",33,"10.21.6.1.2",26,"The editing instructions should tell where new row needs to be added. ",null,"I.e., change editing instructions to say \"Insert new row after xxx into\" or \"Insert new row at the end into\". Also remove \"...\" rows from the table. ","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,336,"No","Self","Technical",33,"10.21.6.1.2",28,"After the table 10-104 the base specification has paragraph that tells which request command is to be sent. This text requires updating. ",null,"Add instructions to add text like \"If UwBControleeAssociation is TRUE, then MLME generates a HRP UWB Association Request command as specified in 10.40.4.1.\"","Yes",null,null,"DISC",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1053,"No","Qorvo","Technical",33,"10.21.6.1.2",28,"I think this is missing description after the parameter table to say that the (UWB) controller association command frame is sent  when the new parameter is true.",null,"Add appropriate description of the activity of the MAC in response to this primitive when the parameter is true, i.e. sending the new association command frame, and in particular indicate which of the other parameters are used / not used in doing this.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Huan-Bang Li",null,1436,"Yes","NICT","Technical",33,"10.21.6.1.2",28,"The description on 'UwbControleeAssociation' in Table 10-104 is not completed. Description for 'FALSE' need to be added.",null,"add description.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1054,"No","Qorvo","Technical",33,"10.21.6.1.3",28,"I think this is missing description after the parameter table to say what parameters of the indication primitive are valid in the case for this (UWB) controller association command frame being received",null,"Add appropriate description .","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,341,"No","Self","Editorial",34,"10.21.6.1.3",2,"The editing instructions claims to change only first paragraph, but actually changes first two paragraphs. ",null,"Change \"initial paragraph\" to \"first three paragraphs\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,340,"No","Self","Technical",34,"10.21.6.1.3",14,"Adding new Uwb* parameters in the middle of DSME parameter is not good. ",null,"Move Uwb* after DSME parameters i.e. at the end of parameter list.","Yes","Accepted",null,"DISC",null,"DONE"]
[null,null,"Tero Kivinen",null,339,"No","Self","Technical",34,"10.21.6.1.3",20,"The editing instructions should tell where new row needs to be added. ",null,"I.e., change editing instructions to say \"Insert new row after xxx into\" or \"Insert new row at the end into\". Also remove \"...\" rows from the table. ","Yes","Accepted",null,"DISC",null,"DONE"]
[null,null,"Huan-Bang Li",null,1437,"Yes","NICT","Technical",34,"10.21.6.1.3",22,"The description on 'UwbControleeAssociation' in Table 10-105 is not completed. Description for 'FALSE' need to be added.",null,"add description.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,342,"No","Self","Editorial",34,"10.21.6.1.4",24,"The editing instructions is not correct. There are three paragraph it is listing, and modifying second one of them. ",null,"It should either say \"Change second paragraph\" and remove 1st and 3rd paragraph, or say \"Change first three paragraphs\". ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,344,"No","Self","Technical",35,"10.21.6.1.4",4,"Adding new Uwb* parameters in the middle of DSME parameter is not good. ",null,"Move Uwb* after DSME parameters i.e. after ChannelIndex but before AssociationStatus.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1055,"No","Qorvo","Technical",35,"10.21.6.1.4",16,"Some description is probably needed here as a result of the new the parameter in the table",null,"Add appropriate description .","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Huan-Bang Li",null,1438,"Yes","NICT","Technical",35,"10.21.6.1.4",16,"The description on 'UwbControleeAssociation' in Table 10-106 is not completed. Description for 'FALSE' need to be added.",null,"add description.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,343,"No","Self","Editorial",35,"10.21.6.1.4",24,"The editing instructions should tell where new row needs to be added. ",null,"I.e., change editing instructions to say \"Insert new row after xxx into\" or \"Insert new row at the end into\". Also remove \"...\" rows from the table. ","Yes",null,null,"DISC",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,346,"No","Self","Editorial",35,"10.21.6.1.5",18,"The editing instructions is not correct. There are three paragraph it is listing, and modifying second one of them. ",null,"It should either say \"Change second paragraph\" and remove 1st and 3rd paragraph, or say \"Change first three paragraphs\". ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,345,"No","Self","Technical",35,"10.21.6.1.5",29,"Adding new Uwb* parameters in the middle of DSME parameter is not good. ",null,"Move Uwb* after DSME parameters, i.e. after ChannelIndex but before Status.","Yes","Accepted",null,"DISC",null,"DONE"]
[null,null,"Tero Kivinen",null,348,"No","Self","Technical",36,"10.21.6.1.5",6,"The editing instructions should tell where new row needs to be added. ",null,"I.e., change editing instructions to say \"Insert new row after xxx into\" or \"Insert new row at the end into\". Also remove \"...\" rows from the table. ","Yes","Accepted",null,"DISC",null,"DONE"]
[null,null,"Billy Verso",null,1056,"No","Qorvo","Technical",36,"10.21.6.1.5",8,"Some description is probably needed here as a result of the new the parameter in the table.  Also what happens next, this is not giving any slot assignment etc to the newly associated device, is this described already or is in needed here?",null,"Add appropriate description, of what parameters are valid in this case.  And describe/ reference what happens next, slot assignment etc.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Huan-Bang Li",null,1439,"Yes","NICT","Technical",36,"10.21.6.1.5",8,"The description on 'UwbControleeAssociation' in Table 10-107 is not completed. Description for 'FALSE' need to be added.",null,"add description.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,349,"No","Self","Technical",36,"10.21.6.1.5",9,"There is text here that does not have editing instructions, and it is not complete. ",null,"Add editing instructions, and change text to only cover case where the UwbControleeAssociation is TRUE.","Yes","Accepted",null,"DISC",null,"DONE"]
[null,null,"Tero Kivinen",null,347,"No","Self","Editorial",36,"10.21.8",12,"This is not correct place for the HRP-EMDEV association, the MAC commands, MAC Management primitives, MAC constants etc are supposed to be last sections in each subsection. ",null,"move 10.21.8 to 10.21.4a.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1057,"No","Qorvo","Technical",36,"10.21.8",13,"Maybe controlee is enough here",null,"change: \"HRP-EMDEV controlee\" to \"controlee\"","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1058,"No","Qorvo","Technical",36,"10.21.8",13,"Should the first step be scanning for AC IE with Association Availability field indicating the controller accepting such association attempts. Could either update the Passive Scan to allow for this, or have the next higher layer just turn on its receiver and examine received frames for one carrying the appropriate AC IE.",null,"If seeing Association Availability indication from the controller should be the first step, then describe that step in the text.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1059,"No","Qorvo","Technical",36,"10.21.8",16,"This new association is not to a PAN coordinator, (the pre-existing association doe that).",null,"Change \"coordinator of an existing PAN.\" to \"controller\"","Yes",null,null,"DISC",null,"ASSIGNED",null,"Carlos"]
[null,null,"Pablo Corbalán Pelegrín",null,1294,"No","NXP Semiconductors","Editorial",36,"10.21.8",19,"Missing word \"layer\" -- \"… to its next higher layer\"",null,"… to its next higher layer","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,351,"No","Self","Editorial",37,10.29,1,"There is extra subsection entries in the PDF index for 10.29.1, 10.29.4, 10.29.6, 10.29.7 and 10.29.8. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1060,"No","Qorvo","Technical",37,"10.21.8",1,"The controller has a slotted protocol, is a particular slot defined for the Association Response command frame to be sent in.  The would be good so that the joining controlee does not have to listen in lots of slots for a possible response.",null,"Consider including in the protocol a specification of the slot for the association response command frame to be sent and expected","Yes",null,null,"TE",null,"ASSIGNED",null,"Carlos"]
[null,null,"Tero Kivinen",null,352,"No","Self","Technical",37,"10.21.8",12,"Do not duplicate values here. ",null,"Remove last two sentences, they are not needed, as whether the association was successful or not can be seen frm the association status. Also small numbers would need to be spelled out if you keep duplicating this information.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1061,"No","Qorvo","Editorial",37,"10.21.8",15,"This is a repeat of line 1, which does not seem necessary",null," Delete it","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Alex Krebs",null,1402,"No","Apple","Technical",37,"10.21.8",17,"Device roles missing in Figure 5.",null,"Add controller/controlee device roles to figure.","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,350,"No","Self","Editorial",37,"10.21.8",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Wenzheng Li",null,179,"Non-Voter","Calterah Semiconductor ","Editorial",37,"10.29.9.2.2",26,"\"The MLME-SOUNDING.request primitive is used by the next higher layer to request channel sounding information, (i.e., the CIR data)\"\nthe description of sensing measurement may be added here for further clarification",null,"The MLME-SOUNDING.request primitive is used by the next higher layer to request channel sounding information for sensing measurement, (i.e., the CIR data)","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,353,"No","Self","Editorial",37,"10.29.9.2.2",26,"This is first use of CIR, expand it here. ",null,"Expand CIR here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,354,"No","Self","Editorial",38,"10.29.9.2.2",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,355,"No","Self","Editorial",38,"10.29.9.2.2",7,"Empty line in table 5. ",null,"Remove empty line.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,356,"No","Self","Editorial",38,"10.29.9.2.2",8,"The base standard has changed since this text was copied here. ",null,"Update to match latest base standard.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1062,"No","Qorvo","Editorial",38,"10.29.9.2.2",8,"This line has changed in 4me draft (D06, latest at time of writing tis comment), so its deletion and replacement with line 9 needs to be changed.  The D06 line says \"If the feature is supported, the MLME will respond with the MLME-SOUNDING.confirm to deliver the sounding information.\"",null,"Update the line editing accordingly. ","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Wenzheng Li",null,180,"Non-Voter","Calterah Semiconductor ","Editorial",38,"10.29.9.2.3",13,"\"The MLME-SOUNDING.confirm primitive reports the result of a request to the PHY to provide channel sounding information, (i.e., the CIR data)\"\nthe PHY here should be deleted due to not only PHY, but PHY/MAC are to provide channel sounding information, which may keep consistency with the description of The MLME-SOUNDING.request",null,"The MLME-SOUNDING.confirm primitive reports the result of a request to provide channel sounding information, (i.e., the CIR data)","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,25,"Yes","STMicroelectronics","Technical",38,"10.29.9.2.3 ",23,"In table 10-155 add parameter to recall the requested data list type",null,"FormatSpecifier: as defined in the MLME-SOUNDING.request","Yes","Accepted",null,"MAC",null,"DONE"]
[null,null,"Mickael Maman",null,26,"Yes","STMicroelectronics","Technical",39,"10.29.9.2.3",1,"the type of SoundingListSet is a set of SoundingList ",null,"as in comment","Yes","Rejected","Group disagees with the comment.  The type description is technically correct.","MAC",null,"N/A"]
[null,null,"Mickael Maman",null,27,"Yes","STMicroelectronics","Technical",39,"10.29.9.2.3",6,"replace AMPLITUDE_FORMAT by IQ_FORMAT",null,"as in comment","Yes","Accepted",null,"MAC",null,"DONE"]
[null,null,"Wenzheng Li",null,181,"Non-Voter","Calterah Semiconductor ","Editorial",39,"10.29.9.2.3",6,"Wording mistake for “FormatSpecifier of AMPLITUDE_FORMAT”",null,"modified to FormatSpecifier of IQ_FORMAT","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,357,"No","Self","Editorial",39,"10.29.9.2.3",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,108,"No","Huawei","Technical",40,"10.29.9.5.1",20,"FormatSpecificParameters Type should not be Enuration, also the details of the parameters seem to be missing.",null,"Correct the FormatSpecificParameters Type and add details of the packet parameters.","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission to address this","Billy"]
[null,null,"Wenzheng Li",null,182,"Non-Voter","Calterah Semiconductor ","Technical",40,"10.29.9.5.1",20,"For the Table 7, FormatSpecificParameters shall be defined",null,"FormatSpecificParameters shall include:\nactive segment lengths\npreamble code(91 or 127)\nsupport active segments number(1,2,3,4)","No",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission to address this","Billy"]
[null,null,"Tero Kivinen",null,358,"No","Self","Editorial",40,"10.29.9.5.1",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1346,"No","Qualcomm","Technical",40,"10.29.9.5.1",20,"Does \"PacketFormat\" parameter only specify SENS packets, or ranging packets too? If so, why is it called UWB-PACKET?",null,"Use a more descriptive name, or generalize to STS packets as well as other 4ab packets.","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Billy Verso",null,1063,"No","Qorvo","Technical",40,"10.29.9.5.1 ",10,"MLME-UWB-PACKET.request seems like a good way to configure not just sensing packets but all the UWB packet formats: Normal, STS, SENS, MMS, etc. ",null,"Unify HRP UWB PHY packet mode configuration into one place… I will prepare a submission to cover this.","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Mickael Maman",null,28,"Yes","STMicroelectronics","Technical",40,"10.29.9.5.1 ",20,"PacketFormat is missing for default STS_PACKET",null,"add STS_PACKET in valid range and add phyHrpUwbPacketFormat: SENS_PACKET_0, SENS_PACKET_1, SENS_PACKET_2, STS_PACKET (default) in Table 12-8","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Mickael Maman",null,29,"Yes","STMicroelectronics","Technical",40,"10.29.9.5.1 ",20,"FormatSpecificParameters for SENS_PACKET",null,"TxSensPacketStructure: 0-2\nTxSensSegmentLength: 16/32/64/128/256/512\nTxSensNumberSegments: 0-4\nRxSensPacketStructure: 0-2\nRxSensSegmentLength: 16/32/64/128/256/512\nRxSensNumberSegments: 0-4","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Billy Verso",null,1064,"No","Qorvo","Technical",40,"10.29.9.5.1 ",21,"If the FormatSpecificParameters parameter is not use, it should be removed.  I am thinking that simple PIB values should be used for configuring such items.",null,"Delete the FormatSpecificParameters parameter. And the INVALID_PARAMETER return value in MLME-UWB-PACKET.confirm if there are no other parameters to be invalid.","Yes",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"B. Rolfe",null,1325,"Yes","BCA","Technical",40,"10.29.9.5.1 M",21,"\"This may provide specific parameters associated with the selected packet format.\" can be more clear and avoid misuse of \"may\". ",null,"Provides lparameters specific to the selected packet format.",null,null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Wenzheng Li",null,183,"Non-Voter","Calterah Semiconductor ","Technical",41,"10.29.9.5.2",10,"For the Table 8, specific indication for not supported parameter may be introduced with respective to FormatSpecificParameters in Table 7",null,"NOT_SUPPORTED_SENS_LENGTH\nNOT_SUPPORTED_PREAMBLE_CODE\nNOT_SUPPORTED_SEGMENTS_NUMBER","No",null,null,"MAC",null,"ASSIGNED","working on a \"uwb-packet-format\" submission which will address this","Billy"]
[null,null,"Tero Kivinen",null,359,"No","Self","Editorial",41,"10.29.9.5.2",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,360,"No","Self","Editorial",41,"10.29.9.5.2",11,"Empty line in table 8. ",null,"Remove empty line.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Zhenzhen Ye",null,1,"No","Redpoint Positioning","Editorial",41,"10.32.1",22,"wrong section number on the reference of ARC IE?",null,null,"Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Wenzheng Li",null,184,"Non-Voter","Calterah Semiconductor ","Technical",41,"10.32.1",23,"To be more accurate, an RCM can also contains HBS IE, ERR IE ",null,"An RCM is a data frame conveying either an Advanced Ranging Control IE (ARC IE) described in 10.31.9.1 or an Application Control IE (AC IE) carrying a Ranging Control field (as described 10.39.6.1) or an Hyper Block Structure IE (HBS IE) as described in 10.32.9.12 or Enhanced Ranging Round IE (ERR IE) as described in 10.32.9.11 or any combination of them.","No",null,null,"TE",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1065,"No","Qorvo","Editorial",41,"10.32.1",26,"The sentence \"If both of ARC IE and AC IE are conveyed at the same time, the parameter values in both IE jointly configure the HRP-EMDEV while those of the ARC IE are for ERDEV.\" is being inserted so it should be underlined.",null,"Make it underlined","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1066,"No","Qorvo","Technical",41,"10.32.1",26,"\"If both of ARC IE and AC IE are conveyed at the same time, the parameter values in both IE jointly configure the HRP-EMDEV while those of the ARC IE are for ERDEV.\"  Is suggesting mixed networks of legacy ERDEV and the newer EMDEV being defined by 4ab. If this is the case then the parameters need to be aligned, and text needs to say this, perhaps we need a special sub-clause to describe these mixed networks and how to set up the parameters so that they can operate properly.",null,"Add clause to explain such a mixed network and specify which parameters in AC IE \"SHALL be\" set the same as the parameters in the ARC IE.  At the very least, the slot, round, block parameters need to be the same, but there may be others to consider also.","Yes",null,null,"MAC",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Zhenzhen Ye",null,2,"No","Redpoint Positioning","Technical",41,"10.32.1",28,"what is \"multi-mode ranging\"? Is it a typo of \"multi-node ranging\"?",null,null,"Yes","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","TE",null,"Ready"]
[null,null,"Billy Verso",null,1067,"No","Qorvo","Technical",41,"10.32.1",29,"The last two sentences on this paragraph (running into first two lines of p42) is suggesting networks with multiple nodes acting as controller and giving different conflicting information that the receiving node has to choose between based on some random criteria. I guess this is all higher layer behaviour so perhaps we should not concern ourselves with it, but why even add these lines if it is some higher layer protocol that is really making sense of this. ",null,"Consider what modifications are really necessary here, versus things that can be left to higher layer spec and modify accordingly. Maybe some text for an explanatory annex could be used to discuss the application scenarios where this occurs.","No","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","MAC",null,"Ready"]
[null,null,"Pablo Corbalán Pelegrín",null,1295,"No","NXP Semiconductors","Technical",41,"10.32.1",29,"A device listening to multiple RCMs with different ARC IEs in a ranging round may receiver various conflicting configurations. The text is currently a bit vague in how to deal with these conflicting RCMs.",null,"Ellaborate a bit more how to deal with multiple RCMs in a single ranging round. Perhaps reference other sections where usage of this feature (multiple RCMs in a ranging round) is described.","No","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","HB",null,"Ready"]
[null,null,"B. Rolfe",null,1326,"Yes","BCA","Technical",41,"10.32.1 In",28,"\" a device may\" stating a possibility not an optional requirement. ",null,"Change \"a device may\" to \"it is possible for a device to\"",null,"Accepted",null,"MAC",null,"DONE"]
[null,null,"B. Rolfe",null,1327,"Yes","BCA","Technical",42,"10.32.1 In",2,"\"It may be based on a majority decision\" is stating a possibility outside the scope of this standard.",null,"Change \"may\" to \"might\"",null,"Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","MAC",null,"Ready"]
[null,null,"Billy Verso",null,1068,"No","Qorvo","Technical",42,"10.32.2",9,"The definition of Ranging Slot based on RFRAME needs to be updated to include a note that MMS packet (which is also an RFRAME ?) may span multiple such ranging slots.  And given that ranging slots are also used for non-RFRAME frames, like ranging control frames, reporting frames etc, should include their needs in the slot sizing.",null,"A better definition might be that the ranging slot size is generally chosen to be big enough to cater for the messages used in the ranging protocol, and allowing for processing between transmissions and receptions. Add something about the UWB MMS packet typically taking multiple slots, (rather than defining a slot big enough for the 16 ms UWB MMS RFRAME).  Could suggest that a slot size of 1 ms is a good choice for UWB given that regulatory power limits are typically expressed as the mean power in a 1 ms interval.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Youngwan So",null,928,"Yes","SAMSUNG Elec.","Editorial",42,"10.32.2",11,"The reference is wrong. Figure10-220 is an example of interval-based mode time diagram. Block structure mentioned should be Figure10-214.",null,"Change from\n\"Figure 10-220 shows the ranging block structure. In this figure, the ranging block is divided into N ranging rounds, each consisting of M ranging slots.\"\nTo\n\"Figure 10-214 shows the ranging block structure. In this figure, the ranging block is divided into N ranging rounds, each consisting of M ranging slots.\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,361,"No","Self","Editorial",42,"10.32.2",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1069,"No","Qorvo","Technical",42,"10.32.2",22,"Here and line 26, are those \"other devices\" controllers? YES, I believe so since by definition a controller is a device that sends an RCM (base standard definition). So call them that.",null,"Change \"other devices\" to \"other controllers\", line 22 and line 27. ","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1070,"No","Qorvo","Technical",42,"10.32.2",23,"\"other ranging slots\" worries me now, since the sending of an RCM is defining slot zero, how can the receiving node know these are not resetting to slot 0. or perhaps each controller sending RCM is defining its local slot 0... This is worrying me... Unless it is very well described and consistent with the base standard, I fear this new stuff is breaking the pre-existing stuff in the 15.4 standard.  ",null,"Suggest to back-out this feature entirely and leave it to be defined in some higher layer protocol where can be done in a way that actually makes sense.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Alex Krebs",null,1384,"No","Apple","Technical",42,"10.32.2 ","22,23","Do we need a more clear definition of RCMs? It seems here as if anybody, not only the initiator/controller, are allowed to send RCMs not only for sync, but also with ranging config params. This may be in conflict with the initiator=controller paradigm.",null,"Change lines 21-23 to:\n\n- Ranging Control Message (RCM): A message transmitted during ranging control phase, to configure or to synchronize an upcoming ranging phase.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Alex Krebs",null,1385,"No","Apple","Technical",42,"10.32.2 ","26-30","RCP and RRP definitions are valid for O2O ranging only, O2M ranging does generally not follow these conventions.",null,"Change page 56, line 8-9 to:\n\nFor one-to-one ranging with one initiator and one responder a UWB MMS ranging exchange consists of consecutive control phase, ranging phase, and a report phase, as illustrated in Figure 25.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,362,"No","Self","Editorial",43,"10.32.3.5",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Zhenzhen Ye",null,3,"No","Redpoint Positioning","Technical",43,"10.32.3.5",8,"Is it mandtory to require successive hyper blocks to have the same configuration? With HBS IE, the configuration can be changed.",null,"change to \"while successive hyper blocks may employ the same configuration\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1071,"No","Qorvo","Technical",43,"10.32.3.5",10,"I don't think anything would be \"repeatedly transmitted in every RCM\", as it only makes sense to send something once in each RCM, so the language needs to be corrected.",null,"Change to \"Each RCM may include an HBS IE, to (continually) provide/confirm the hyper block structure configuration.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pablo Corbalán Pelegrín",null,1296,"No","NXP Semiconductors","Technical",43,"10.32.3.5",10,"In block-based mode, there is a controller per block or session with a repeatable block. Is the Hyper block controller also the controller of each block within the hyper block? This should be clarified. If various devices could act as controllers of the different blocks within the hyper block, then we would need to align these controllers and forward the HBS IE in the RCM of each individual block. Currently the text suggests the HBS IE may be only included in the RCM of the first slot in every hyper block. However, if some devices do not participate in block 1 of the hyper block but do in block 2, then they will not hear that RCM and therefore lose sight of the hyper block structure. ",null,"Add text to clarify whether the Hyper Block Controller is also the controller of each block within the Hyper Block or if instead there could be a different controller per block. Additionally, we may consider sending the HBS IE in the first slot of each block of the hyper block. Otherwise it should be clearly stated that all controlees need to listen to the very first slot to receive the RCM with the HBS IE.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1072,"No","Qorvo","Technical",43,"10.32.3.5",12,"It is difficult to interpret \"may be\" in terms of what is required or not for hyper block mode. Alternatives that could be permitted is sending RCM in first slot without the HBS IE, not sending RCM at all, or sending it in other slots, or ff the first slot is defined by the presence of the HBS IE ",null,"Rewrite paragraph/clause be more definite in specifying what constitutes a hyper block. For instance, if it is the RCM with HBS IE, in slot 0 then say that.  ","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1073,"No","Qorvo","Technical",43,"10.32.3.5",15,"Not really sure what the purpose of this sentence \"On reception of an HBS IE with the RCM, a controlee may assume that hyper block structure is followed.\", it does not read well, and is hard to understand. Is the \"with the RCM\" needed, I think HSB IE is included in the RCM so this \"with\" is strange.  \"May assume\" is also strange. Is it defining receiver behaviour.  Better to specify the transmitter controller behaviour using \"SHALL\" and not have the receiver assuming something ",null,"Rewrite the sentence to address the points of the comment or if it is not necessary then delete it.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1074,"No","Qorvo","Technical",43,"10.32.3.5",16,"\"The HBS IE takes effects from the corresponding hyper block where HBS IE exists.\" is strange language. \"Effects\" should be singular, but I  think the intent could be conveyed more clearly, something like the proposed change.",null,"Change to: \"The RCM with the HBS IE is sent at the start of the hyper block, and this immediately conveys the hyper block structure configuration for current hyper block, i.e., the hyper block beginning with the slot carrying the RCM.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1075,"No","Qorvo","Technical",43,"10.32.3.5",20,"\"and where there are common parameters in both ARC IE and HBS IE\" seems a bit vague, someone should do the work and give a list of all the common parameters that, either \"SHALL\" have the same value in both IE, or define which has precedence otherwise, and I would suggest this should be the ARC IE.  Or, you could if HBS IE is present in the RCM then the ARC IE shall be omitted.",null,"Explicitly list the common parameters and shall have the same values in both ARC IE and HBS IE,","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1076,"No","Qorvo","Technical",43,"10.32.3.5",21,"\"these corresponding overlapping parameter values should be the same. \" this  \"should\" should be a \"shall\". Otherwise operation is undefined.",null,"Change \"should\" to \"shall\", or define the operation as to what is the correct operation when they are not the same.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,939,"Yes","SAMSUNG Elec.","Technical",43,"10.32.3.5",22,"The overlapping parameters from different IEs within the same frame must have the same value so to avoid the ambiguity",null,"Change \n\nFrom\n\"these corresponding overlapping parameter values should be the same\" \nTo \n\"these corresponding overlapping parameter values shall be the same\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1077,"No","Qorvo","Technical",43,"10.32.3.5",23,"This paragraph suggests that HBS IE is sent in every hyper block (so the \"may\" in the first line of precious paragraph should be a shall.",null,"If I am right make it a \"Shall\", i.e., \"In hyper block mode the RCM with HSB IE shall be sent ….\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1078,"No","Qorvo","Technical",43,"10.32.3.5",26,"Now as I read this it seems there could be an HBS IE in each sub-block of the hyper-block, which perhaps modifies some of my earlier comments. I guess the \"block index\" referred to on this line what is referenced by the \"Relative Block Index\" in the Ranging Block Description List.\nThis is complex, maybe a worked example would make it clearer.",null,"Add an annex (referred to from this clause) with a detailed worked example showing where RCM and HBS IE may be sent and the content of the various fields of the HBS IE that are relevant to defining the hyper block scheduling operation","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,217,"No","NXP Semiconductors","Technical",43,"10.32.3.5","16, 17","inconsistent implementation can happen with the statement - The HBS IE takes effects from the corresponding hyper block where HBS IE exists",null,"The specification can keep it simple if the statement is - The Controlee shall follow the hyperblock structure when HBS IE is transmitted","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,218,"No","NXP Semiconductors","Technical",43,"10.32.3.5","18, 19","Conflicting slot duration in HBS IE and RCM needs to be handled ",null,"clarification on when HBS IE transmitted along with RCM, there needs to be a override of same configuration value","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Zhenzhen Ye",null,4,"No","Redpoint Positioning","Technical",43,"10.32.3.5","27-30","The formulation of the (absolute) ranging block index doesn't work if there is a hyper block configuration change",null,null,"Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1079,"No","Qorvo","Technical",44,"10.32.3.5",3,"Sentence \"Different blocks within a hyper block may be allocated for different applications such as ranging or sensing or data communications.\"  seems to be saying it is block level allocation, is there a real allocation mechanism defined that only requests/grants blocks to different devices, a reference to this scheme would be good to include here.  However, if it is a more informal method and not block level, then more informal language would be appropriate, and indeed perhaps mentioning that the allocation methods are not defined.",null,"Change to: \"Different parts of the hyper block may be used for different applications such as ranging or sensing or data communications.  The mechanisms for assigning these are not defined within this standard.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Zhenzhen Ye",null,5,"No","Redpoint Positioning","Technical",44,"10.32.3.5",5,"hyper block doesn't have to keep the same structure in every hyper block if HBS IE specify a new hyper block configuration.",null,"change to \"The hyper block may keep the same structure repeated in every hyper block.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1080,"No","Qorvo","Editorial",44,"10.32.3.5",6,"\"in one of the following methods\" should maybe be \"using one of the following methods\"",null," change \"in\" to \"using\" ","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1081,"No","Qorvo","Technical",44,"10.32.3.5",8,"The methods defined here are a little confusing saying the controlee \"may\" do something. A \"shall\" would be more appropriate, except it is probably actually the next higher layer that is taking the decision and we should not be mandating its behaviour.  Perhaps the text be reduced a lot or made clearer if it was defined from the transmitter's perspective.  ",null,"Rewrite the behaviours to describe transmitter operation not receivers.  The controller may set field xxx to value yyy to request that the controller hops into …..\"\n","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1082,"No","Qorvo","Technical",44,"10.32.3.5",8,"If hyper block is really something to be used and understood by the layers above the MAC, then perhaps the body of the text here could be much shorter, and just say something like the HBS IE is defined to allow next-higher layers coordinate the used of the medium.... it has fields that allow request of xxxx, and yyyy, etc. Could give specific examples in an informative annex, rather than a normative clause with non-normative \"may\" which are hard to understand the behaviour.",null,"Consider much simpler specification, with examples of use referenced and placed in an annex or an separate mentor document.. \n","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1083,"No","Qorvo","Technical",44,"10.32.3.5",13,"Again use of \"may\"…. Should it be \"should\"?  I think this is really next higher layer behaviour being specified in the wrong place. Another one on line 16 ",null,"Consider much simpler specification, with examples of use referenced and placed in an annex or an separate mentor document.. \n","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Huan-Bang Li",null,1440,"Yes","NICT","Technical",44,"10.32.3.5",22,"replace 'm not equal to p' by  'm does not equal to p'.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,363,"No","Self","Editorial",44,"10.32.3.5",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"B. Rolfe",null,1328,"Yes","BCA","Technical",44,null,3,"\"Different blocks within a hyper block may be allocated for different applications \" this may is stating a possibility outside the scope of this standard.  This is a (rare) instance of when \"can\" is the correct word.",null,"change \"may\" to \"can\"",null,"Accepted",null,"HB",null,"DONE"]
[null,null,"Youngwan So",null,940,"Yes","SAMSUNG Elec.","Technical",45,"10.32.3.5",1,"The Hyper Block Advertisement (HBA) round is optional feature. However \"at least once\" looks to give an impression that HBA is mandatory.",null,"Remove \"at least once\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,364,"No","Self","Editorial",45,"10.32.3.5",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1084,"No","Qorvo","Technical",45,"10.32.3.5",13,"\"to inform the next ranging block that is assigned to a controlee,\" reads badly which makes it hard to understand, if I understand it correctly then it could be clarified by the proposed change..",null,"\"to inform a controlee about its next ranging block assignment, and ….\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1085,"No","Qorvo","Technical",45,"10.32.3.5",13,"I suppose if there is an assignment like this it is superseding any previous assignment rather than adding to it.  Worth specifying what is the case. ",null,"Specify that the slot assignment in ERR are superseding previous assignment or additional.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1086,"No","Qorvo","Technical",45,"10.32.3.5",14,"ERR IE doesn't include controlee address field so I assume this is picked up from the MAC  address of the frame.  Worth saying the too",null,"state \"the ERR IE applies to the device addressed by the MHR of the frame carrying the ERR IE\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"B. Rolfe",null,1329,"Yes","BCA","Technical",45,"10.32.3.5",21,"\"the controlee may infer the number of rounds in the block based on the Number of Rounds field in 22 the ERR IE \" is not stating an optional requirement but a possible inference (we don't have a normative description of how to infer). ",null,"Change to:\" the controlee is able to determine the number of rounds in the block based on the Number of Rounds field in the ERR IE and will be able to calculate its allocated round in the block\"",null,null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"B. Rolfe",null,1330,"Yes","BCA","Technical",45,"10.32.3.5",24,"\" the controlee may listen to the channel at the next known hyper 25 block advertisement round\" This is stating an option, but I think it should be strongly recommended (\"should\") behavior. ",null,"Change \"may\" to \"should\"",null,null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1093,"No","Qorvo","Technical",46,"10.32.9.10",22,"\"schedule blocks or slots to be used by intended device\"  I am assuming an assignment is for the purpose of transmission only , but worth saying if this IE is also scheduling reception if that is the case add \"and receptions\" to my proposed change.",null,"\"assign ranging blocks or ranging slots to selected devices for scheduled transmissions\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,365,"No","Self","Editorial",46,"10.32.9.10",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,366,"No","Self","Technical",46,"10.32.9.3",2,"The section 10.38.9.3.20 defines round index as 8-bit field and the security restricts it to 8-bit field. Here the round index is 14 bit field. ",null,"Change Round Index to 8-bit field.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1087,"No","Qorvo","Editorial",46,"10.32.9.3",6,"\"Bitmap-based block scheduling\" should have lower case \"b\"",null,"Change \"Bitmap-based\" to say \"bitmap-based\".","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1088,"No","Qorvo","Technical",46,"10.32.9.3",7,"The sentence beginning \"In hyper block mode …\"  says defines a particular case where, \"Ranging Block Index field is assumed to specify Hyper Block Index\" which is strange, can we not specify the behaviour.",null,"Change to say \"the Ranging Block Index field shall specify the hyper block index\"\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1089,"No","Qorvo","Technical",46,"10.32.9.3",7,"\"Hyper Block Index\" (if it is not a field name) should be lower case.",null,"If it is a field add \"field\" otherwise make it lower case.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1090,"No","Qorvo","Technical",46,"10.32.9.3",7,"\"the Ranging Block Index field is assumed to specify Hyper Block Index\", (I assume by the receiver), maybe could be more definite and specify it from the transmitter perspective",null,"Change to the \"Ranging Block Index field specifies the Hyper Block Index\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Wenzheng Li",null,185,"Non-Voter","Calterah Semiconductor ","Technical",46,"10.32.9.3",8,"\"the Ranging Block Index field is assumed to specify Hyper Block Index for the \nranging hyper block and controlee may assume the block index will be the same with previous hyper block\" \nthe last block index in this sentence should be relative block index",null,"the Ranging Block Index field is assumed to specify Hyper Block Index for the \nranging hyper block and controlee may assume the relative block index will be the same with previous hyper block","No",null,null,"TE",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1091,"No","Qorvo","Technical",46,"10.32.9.3",8,"\"controlee may assume\" is strange…can we turn int into controller/transmitter perspective, or otherwise make a more definitive statement..",null,"Unless explicitly rescheduled the controlee block index assignments are the same in each hyper block\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"B. Rolfe",null,1331,"Yes","BCA","Technical",46,"10.32.9.3",8,"\" may assume\" might be read wrong.  DO we mean unless the information is updated for the current hyperblock,use the values from the prior hyperblock?",null,"In hyper block mode when neither block assignment scheduling nor Bitmap-based block scheduling is used, the Ranging Block Index field is specifies the Hyper Block Index for the ranging hyper block. Unless updated for the current Hyper Block, the controlee shall use the block index from the previous hyper block",null,null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1092,"No","Qorvo","Technical",46,"10.32.9.3",9,"Should define how hyper block index is conveyed in those other two hyper block modes, where either block assignment scheduling or bitmap-based block scheduling is used, (or reference where the details are specified).",null,"Add description as per comment, or reference where it is.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,367,"No","Self","Editorial",47,"10.32.9.10",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,368,"No","Self","Editorial",47,"10.32.9.10",17,"This is first use of RSF outside tables, expand here. ",null,"Expand RSF here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1094,"No","Qorvo","Technical",47,"10.32.9.10",18,"Not sure the \"shall\" is right here, the IE is conveying the assignment, but it is the next higher layer that is initiating the MMS ranging using the MCPS-DATA.request with interleaved TX and RX by two devices coordinated by something.  NBA poll and response Compact frames, or UWB versions of it, or by this IE ? ",null,"As this is description of IE format, the normative SHALL should perhaps be in the clause describing the procedure that uses this IE, and perhaps a message sequence chart might help show how this works.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,941,"Yes","SAMSUNG Elec.","Technical",47,"10.32.9.10",21,"This chapter (10.32.9.10) is specifying about Scheduling IE. Threrfore, \"One-to-many Poll Compact frame\" doesn't need to be mentioned here.",null,"Remove \"the One-to-many Poll Compact frame or\".\nThen the change will be as follows;\n\nFrom\n\"In this scheduling type, control phase is conducted in the UWB channel and starts with transmission of a Data frame that carries the One-to-many Poll Compact frame or the Scheduling IE (10.32.9.10) with scheduling list type field as four from Initiator.\"\nTo\n\"In this scheduling type, control phase is conducted in the UWB channel and starts with transmission of a data frame that carries the Scheduling IE (10.32.9.10) with scheduling list type field as four from Initiator.\"","Yes","Accepted",null,"HB",null,"DONE"]
[null,null,"Youngwan So",null,942,"Yes","SAMSUNG Elec.","Technical",47,"10.32.9.10",23,"Considering general Request/Response handshake, it's more natural for \"One-to-Many Response Compact Frame\" to be paired with \"One-to-Many Poll Compact Frame\" and for \"Scheduling IE\" to be paired with something suitable such as \"MMRC IE (Multiple Message Receipt Confirmation) \". However, in this sentence, UWB frame seems to be answered by compact frame, which is unnatural",null,"Change \n\nFrom\n\"After receiving the UWB frame, the responders reply with One-to-many Response Compact frame to the initiator\" \nTo \n\"After receiving the UWB frame which carries Scheduling IE, the responders reply with the UWB frame which carries the MMRC IE to the initiator\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Hong Won Lee",null,1407,"No","LG Electronics","Technical",47,"10.32.9.10",27,"There is no description of bitmap-based block scheduling for block-based mode, which can be used. Bitmap-based block scheduling should be described for both hyper block mode and block-based mode, respectively",null,"Change from \"element represents the pattern of scheduled blocks to a single device\" to \"element represents the pattern of scheduled blocks in hyper block mode defined in 10.x.x.x.x or represents the current scheduled block in block-based mode to a single device\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1095,"No","Qorvo","Technical",48,"10.32.9.10",2,"Sentence \"The Block Scheduling Bitmap field represents one or multiple ranging blocks assigned to a device for transmission using a single Scheduling List field element in a hyper block.\", is unclear in meaning especially the part from \"using...\" onward. ",null,"Change to \"The elements of this scheduling list type include a Block Scheduling Bitmap field to specify for each listed responder which ranging blocks of the hyper block it is assigned for its transmissions.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Huan-Bang Li",null,1441,"Yes","NICT","Editorial",48,"10.32.9.10",5,"replace 'more device' by 'more devices'.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1096,"No","Qorvo","Technical",48,"10.32.9.10",11,"\"hopping\" should possibly be called \"ranging round hopping\" to differentiate it from the channel hopping in other PHY/MAC.  Also not sure if there are differences in hopping when hyper blocks are used / not used… and whether we need a modified term to refer to it.",null,"Review occurrences of hopping and change appropriate ones to \"ranging round hopping\" to make the usage clearer. Also used different term for hopping in hyper block if this is needed.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1097,"No","Qorvo","Technical",48,"10.32.9.10",14,"Final Sentence in paragraph is not clear in meaning: \"When block assignment scheduling is used and the Block Assignment List field carries address of networks, the Address Size field indicates short address.\"…. Specifically I don't know what \"carries address of networks\" means.",null,"I am not sure what the sentence should say, but I am prepared to work with its author to come up with something that is more clear in meaning. ","Yes",null,null,"HB",null,"ASSIGNED","15-23-0215-02-04ab is the source of this phrase, Rojan is first listed co-author of that submission. Suggest to please assign this to him.","Rojan"]
[null,null,"Tero Kivinen",null,369,"No","Self","Editorial",48,"10.32.9.10",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,370,"No","Self","Editorial",48,"10.32.9.10",26,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,372,"No","Self","Editorial",49,"10.32.9.10",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1098,"No","Qorvo","Technical",49,"10.32.9.10",2,"Here there is a \"Scheduling Bitmap field\" but earlier there was mention of a \"Block Scheduling Bitmap field\", (which I do find specified later in this clause, however what does this \"Scheduling Bitmap\" schedule?  If it is also for blocks then same name should be used.",null,"Name this \"Scheduling Bitmap\" field appropriately for its use.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,371,"No","Self","Editorial",49,"10.32.9.10",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1099,"No","Qorvo","Technical",49,"10.32.9.10",8,"\"contains a binary bitmap string\", I think best to just say it is a bitmap… by definition a bit is binary so I think binary bitmap is a tautology.  Also bitmaps are not called bitmap strings elsewhere, so this one should be no different.",null,"merge into the second sentence and say it \"is a bitmap defining …..\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1100,"No","Qorvo","Technical",49,"10.32.9.10",17,"\"The Receiver Address field, if present, indicates the destination for the frames in the scheduled slots.\" Does  this mean the specified address need to be used as the destination address in the frames transmitted in the slots.  Or is the telling the intended recipient device to turn on its Receiver in the specified slots?",null,"Clarify which is the case or if both then say that too.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,373,"No","Self","Editorial",49,"10.32.9.10",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,374,"No","Self","Editorial",50,"10.32.9.10",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1101,"No","Qorvo","Technical",50,"10.32.9.10",9,"Figure 15 and field description seems to relate to MMS sequence, but there is no field to say number of RSF fragments.  Also no fields to specify RIF. Should these not be added? ",null,"Add missing fields to specify number of RSF fragments, and RIF parameters.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1102,"No","Qorvo","Technical",50,"10.32.9.10",10,"Seems likely this IE is used over UWB, so this would be \"UWB driven MMS\", in this case the first slot of the MMS packet is mandated to be the SHR (SYNC+SFD) fragment. Its only mention is in 10.38.8.4.3 which is somewhat broken text.  Seems we have multiple ways to do the same thing... pity people did not converge on sensible subset of operation to support for interworking.",null,"Maybe this first slot should be for SYNC+SFD?  ","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1103,"No","Qorvo","Technical",50,"10.32.9.10",11,"This is talking about a Gap between scheduled slots.  I don't think this is mentioned anywhere else. This clause should be defining the IE content and fields, but in another clause the usage should be described.  Do we really need six different scheduling list formats?",null,"Add clauses that use all the flavours of Scheduling IE. If a uses cannot be described then delete the unused format, and leave them OOB negotiation (to be defined elsewhere).  ","Yes",null,null,"HB",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1104,"No","Qorvo","Technical",50,"10.32.9.10",18,"The Number of Gaps field seems misnamed, since it is specifying a gap length rather than the number of gaps.",null,"Change field name to \"Gap Length\" in text on this line, and in Figure 15.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1105,"No","Qorvo","Technical",50,"10.32.9.10",21,"Fields with similar function to this \"Sequence Repetition\" field, are defined elsewhere with different names: \"N_MSR\" in the Ranging PHY Configuration field for use in Compact frames and \"MSR For MMRS\" in the MMS Ranging Configuration field of the AC IE.",null,"Change all three to use the same name \"MSR\" for consistency, updating all three figures and field descriptions accordingly.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1106,"No","Qorvo","Technical",50,"10.32.9.10",22,"An octet cannot represent a value of 256, ",null,"Change all three to use the same name \"MMRS MSR\" for consistency, updating all three figures and field descriptions accordingly.","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,375,"No","Self","Editorial",50,"10.32.9.10",25,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,976,"No","Meta Platforms","Technical",50,"10.32.9.10",25,"Table 11 lists only 2 values for Scaling Factor, yet Figure 16 allocates 2 bits.  This is not consistent.",null,"Please fix.","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Rojan Chitrakar",null,109,"No","Huawei","Technical",51,"10.32.9.10",4,"Since the Relative Block Index in the HBS IE is only 1 octet, there can only be maximum 255 blocks in a hyper block, multipler value of 4 is sufficient.",null,"Change the multiplier value for Scaling factor 1 to 4 to allow finer granularity control of the bitmap.","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,376,"No","Self","Editorial",51,"10.32.9.10",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Hong Won Lee",null,1409,"No","LG Electronics","Technical",51,"10.32.9.10",10,"There is no description of bitmap-based block scheduling for block-based mode, which can be used. Bitmap-based block scheduling should be described for both hyper block mode and block-based mode, respectively",null,"Add \"In block-based mode, the Block Scheduling Bitmap Length and the the Scaling Factor field should be set to 0 because only the first bit in the Block Scheduling Bitmap shall be used\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1107,"No","Qorvo","Technical",51,"10.32.9.10",11,"Another \"binary bitmap string\".  Elsewhere bitmaps are just bitmaps, a bit is binary by definition.",null,"merge into the second sentence and say it \"is a bitmap defining …..\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Hong Won Lee",null,1408,"No","LG Electronics","Technical",51,"10.32.9.10",12,"There is no description of bitmap-based block scheduling for block-based mode, which can be used. Bitmap-based block scheduling should be described for both hyper block mode and block-based mode, respectively",null,"Change from \"and including the block in which the Scheduling IE is transmitted.\" to \"and including the block in which the Scheduling IE is transmitted in hyper block mode.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,378,"No","Self","Editorial",51,"10.32.9.10",14,"Small numbers needs to be spelled out. ",null,"Change \"1\" to \"one\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Hong Won Lee",null,1410,"No","LG Electronics","Technical",51,"10.32.9.10",17,"There is no description of bitmap-based block scheduling for block-based mode, which can be used. Bitmap-based block scheduling should be described for both hyper block mode and block-based mode, respectively",null,"Add \"In block-based mode, the first bit maps to the current block in which the Scheduling IE is transmitted. The first bit in the bitmap is set to 1 to indicate that the current block is scheduled or set to 0 to indicate that the current block is not scheduled. The rest of bits except for the first bit shall be ignored in block-based mode.\" after the last sentence of the third paragraph in P51L17","Yes",null,null,"HB",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,377,"No","Self","Editorial",51,"10.32.9.10",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1109,"No","Qorvo","Editorial",51,"10.32.9.10",27,"empty numbered line",null,"delete it","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1108,"No","Qorvo","Editorial",52,"10.32.9.11",16,"End of line 15 \"to device\" is not needed.",null,"Delete it ","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,379,"No","Self","Editorial",52,"10.32.9.10",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,382,"No","Self","Technical",52,"10.32.9.10",1,"The section 10.38.9.3.20 defines round index as 8-bit field and the security restricts it to 8-bit field. Here the round index is 14 bit field. ",null,"Change Round Index to 8-bit field.","Yes","Rejected","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","HB",null,"N/A"]
[null,null,"Billy Verso",null,1110,"No","Qorvo","Editorial",52,"10.32.9.11",14,"\"inform\" bad choice of word",null,"change to \"specify\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,380,"No","Self","Editorial",52,"10.32.9.11",17,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,381,"No","Self","Technical",52,"10.32.9.11",17,"The section 10.38.9.3.20 defines round index as 8-bit field and the security restricts it to 8-bit field. Here the round index is 14 bit field. ",null,"Change Round Index to 8-bit field.","Yes","Rejected","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","HB",null,"N/A"]
[null,null,"Tero Kivinen",null,386,"No","Self","Editorial",53,"10.32.9.12",1,"There is Table 12 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,384,"No","Self","Editorial",53,"10.32.9.12",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,385,"No","Self","Editorial",53,"10.32.9.12",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1111,"No","Qorvo","Technical",53,"10.32.9.12",10,"\"It is recommended that the three values giving block, round and slot duration are all included in the HBS IE at the same time.\" Rather than recommending, could just define the format so that they all have to be included.",null,"Specify a single presence bit to cover the inclusion/exclusion of all three fields. ","No",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"B. Rolfe",null,1332,"Yes","BCA","Technical",53,"10.32.9.12",10,"Note sure what \"The controller may choose the units to suit its needs.\" means in the context of an optional behavior (without specifying conditions for \"needs\"). Are we saying this is determined by some process outside the scope of this standard? (seems likely).  ",null,"The controller  chooses the units as needed based on criteria outside the scope of this standard.",null,null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pablo Corbalán Pelegrín",null,1297,"No","NXP Semiconductors","Editorial",53,"10.32.9.12",14,"Typo \"froward\"",null,"Replace \"froward\" with \"forward\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,383,"No","Self","Editorial",53,"10.32.9.12",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Huan-Bang Li",null,1442,"Yes","NICT","Editorial",53,"10.32.9.12",16,"add 'are' before 'in numbers of ranging slots' in the second column of Table 12.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,389,"No","Self","Editorial",54,10.33,1,"The PDF index has extra subsection entries for subsection 10.33 and 10.36. ",null,"Remove extra PDF index entries.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Bin Qian",null,140,"No","Huawei","Editorial",54,"10.32.9.12",16,"\"format\" should be \"Format\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,387,"No","Self","Editorial",54,"10.32.9.12",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1112,"No","Qorvo","Technical",54,"10.32.9.12",18,"The end of this sentence \"so it starts from zero when every hyper block having a new hyper block index begins\" is confusing me.  Can we have hyper blocks beginning without new hyper block index, I think not, so the qualification makes the meaning confusing.",null,"Change sentence to \"It starts from zero at the start of each hyper block.\"","Yes",null,null,"HB",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Frank Leong",null,95,"No","NXP Semiconductors","Editorial",54,"10.38",28,"MMS is a variant of UWB, not the other way round.",null,"Change all instances of \"UWB MMS\" to \"MMS UWB\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,388,"No","Self","Editorial",54,"10.38.1",1,"There is Figure 23-24 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,391,"No","Self","Editorial",54,"10.38.1",31,"This is not first use of MMS, do not expand here. ",null,"Do not expand here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,390,"No","Self","Editorial",54,"10.38.1",32,"This is not first use of CIR, do not expand here. ",null,"Do not expand CIR here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,396,"No","Self","Editorial",55,"10.38.1",13,"This is first use of OOB, expand here. ",null,"Expand OOB here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,397,"No","Self","Editorial",55,"10.38.1",16,"This is not first use of RSF, do not expand here. ",null,"Do not expand here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,30,"Yes","STMicroelectronics","Technical",55,"10.38.1",19,"\"For the NBA UWB MMS case, of Figure 23, values of 1.5 ms and 2 ms shall be supported for this time interval.\" it could be interesting that the responder starts to send the first fragment. Then the values of A can be 1 ms and 2.5 ms",null,"\"For the NBA UWB MMS case, of Figure 23, values of 1.5 ms and 2 ms shall be supported for this time interval. Values 1 ms and 2.5 ms may also be supported for this time interval\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,31,"Yes","STMicroelectronics","Technical",55,"10.38.1",21,"In UWB driven UWB MMS, a value of 1 ms shall be supported for time interval A. Does it means that UWB packet for Initiator and responder are interleaved in 1ms?",null,"two options: clarify interleaved UWB SP0 packet or define two values for A as done in NBA UWB MMS. In the first case, new values for macMmsRcpPollNSlots, macMmsRcpRespNSlots and optionnaly macMms1stReportNSlots in Table 20 should be defined.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,395,"No","Self","Technical",55,"10.38.1",22,"What is the X in the figure 23? What is the Y in figure 23? I assume the X is supposed to be number of fragments, and Y is how many times each full thing is repeated or something like that. ",null,"Add description of X and Y to the Figure 23 (and Figure 24).","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Tero Kivinen",null,392,"No","Self","Editorial",55,"10.38.1",23,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,32,"Yes","STMicroelectronics","Technical",55,"10.38.1",25,"Clarify that NB packet and UWB Packet are compact frame packet",null,"Change the figure with NB compact frame and UWB compact frame","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,393,"No","Self","Editorial",55,"10.38.1",25,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Alex Krebs",null,1386,"No","Apple","Technical",55,"10.38.1 ",19,"Unnecessary for intiators to support 1.5ms and responders to support 2ms.",null,"Change\n\nvalues of 1.5 ms and 2 ms shall be supported for this time interval.\n\nto\n\nvalues of 1.5 ms and 2 ms shall be supported for this time interval by responder devices and initiator devices, respectively.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,394,"No","Self","Editorial",55,"10.38.2",1,"There is Figure 25 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1113,"No","Qorvo","Technical",55,"10.38.2",26,"Somewhere in this overview, we should state that NB and UWB PHYs are not transmitting or receiving at exactly the same time which I assume is the case. This would help designers better understand the requirements. (The only case for TX and RX at exactly the same time is monostatic sensing, which separate to MMS).  ",null,"Add a paragraph to make a statement along the lines of: For MMS ranging, the UWB radio does not transmit and receive at the same time, nor does the O-QPSK radio, and UWB and O-QPSK radios do not operate at the same time. Or stating this differently, In NBA UWB MMS ranging, NB transmission, NB reception, UWB transmission, and UWB reception are mutually exclusive operations that do not overlap with each other in time.","Yes",null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Billy Verso",null,1114,"No","Qorvo","Technical",56,"10.38.2",1,"I think some of the parameters talked about here are potentially in the realms of the next higher layer protocol and perhaps not configured directly into the MAC. Maybe for this introductory statement a rewording could help make this more generic.",null,"Change \"is configured for UWB MMS ranging by specifying\" to \"is reused for UWB MMS ranging including the specification of\"","Yes",null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Billy Verso",null,1115,"No","Qorvo","Technical",56,"10.38.2",5,"This phrase \"carrier coherence\" is not clear to me in meaning or how transmission offset might influence it..  I have no problem with the specifying that offset shall be zero, but I think we should note why.",null,"Add a definition of this term and a NOTE giving some explanation of this requirement.","Yes",null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Billy Verso",null,1116,"No","Qorvo","Technical",56,"10.38.2",15,"A ranging round is typically the time from the start of ranging exchange between two devices to the start of their next exchange. In figure 25, \"Ranging Round\" should be changed to \"UWB MMS ranging exchange\" to match the text, although later in the text this may be called a \"ranging sub-round\", but I think that term is never actually defined. This would be a good place to define it, if we want to use it to cover what is in Figure 25.",null,"Define \"MMS ranging sub-round\" here, and add the definition to clause 3.1.  Review all usages of sub-round to ensure that they are consistent (use \"MMS ranging sub-round\") everywhere.  Change figure 25 \"Ranging Round\" to \"MMS Ranging Sub-round\".   ","Yes",null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Tero Kivinen",null,398,"No","Self","Editorial",56,"10.38.2",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1117,"No","Qorvo","Editorial",56,"10.38.2",18,"\"albeit using different PHY layers\" should be in parenthesis ",null,"change to \"(albeit using different PHY layers),\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"B. Rolfe",null,1333,"Yes","BCA","Technical",56,"10.38.2 ",4,"\"may be optionally\" is redundant.  \"May\" means optional (within the scope of the standard).",null,"Remove \"be optionally\"",null,"Accepted",null,"MMSUWB",null,"DONE"]
[null,null,"B. Rolfe",null,1334,"Yes","BCA","Technical",56,"10.38.2 ",14,"Marginally incorrect use of \"may\" suggesting something outside of this standard (if only just). ",null,"alternatively, another OOB mechanism will be used.",null,null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Mickael Maman",null,33,"Yes","STMicroelectronics","Technical",56,"10.38.3",22,"Clarify that MMS initialization and setup is using only NB OQPSK",null,"update title","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1118,"No","Qorvo","Technical",56,"10.38.3",22,"We are missing a subclause about the control of MMS from the next higher layer perspective and how it all hangs together.  I think the interactions should be based on the thoughts captured in 15-23-0306, and new control and configuration parameters of the MCPS primitives added in clause 8.3, and it should employ a message sequence chart to illustrate the interactions. ",null,"I will prepare a submission to cover this, that we can insert in a suitable place in 10.38","Yes",null,null,"MMS",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1119,"No","Qorvo","Technical",56,"10.38.3.1",28,"\"a pair of initiator and responder devices\" perhaps a little unclear.",null,"Change to: \"a pair devices, i.e., an initiator and a responder,\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1120,"No","Qorvo","Technical",56,"10.38.3.1",31,"Given that the messages being sent for the initialisation and ranging phases are sent using MCPS-DATA.request and not autonomously by the MAC. The MAC is not really aware of the MMS ranging phase.  Perhaps therefore we could just have generic attributes which are set by next higher layer according to the phase it is in, e.g. for channel selection just use the phyCurrentChannelInfo attribute.",null,"Consider removing the attributes, or, perhaps (a bit contrived) there could be a Set-MMS-Ranging-Phase primitive that copies the phase specific configurations to the generic configurations. Developing message sequence charts showing next higher layer interactions through the MMS ranging phases may help in clarifying what is actually needed by way of MAC & PHY configurations, and what is really in the domain of the next higher layer.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"B. Rolfe",null,1335,"Yes","BCA","Technical",56,"10.38.3.1",31," \" may be changed by the higher layer \" indicates a that his is a statement of possibility,not  a permissible action defined in this standard.",null,"Change \"may be changed\" to \"are set by\"",null,null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,399,"No","Self","Editorial",57,"10.38.3.2",1,"There is Figure 26-27 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,205,"No","NXP Semiconductors","Editorial",57,"10.38.3.2",3,"Reference to time synchronization of the first poll packet is required",null,"Either refer to Figure 26 or have a new diagram to show the synchronization of the first poll packet","No",null,"Add \"(as shown in Figure 26 for example)\"","TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pooria Pakrooh",null,1347,"No","Qualcomm","Technical",57,"10.38.3.2",5,"Two sentences contradicting. Change to: \"Unless renegotiated by OOB or during initialization phase, the default ranging configuration parnmeters\"",null,"As in the comment","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Billy Verso",null,1121,"No","Qorvo","Technical",57,"10.38.3.2",8,"\"establishing initialisation\" seems like a contradiction, when typically initialisation is something done to establish a connection for interaction, ",null,"Would it be better to say \"To begin NB O-QPSK initialization,\"","Yes","Accepted",null,"MMS",null,"DONE"]
[null,null,"Billy Verso",null,1122,"No","Qorvo","Technical",57,"10.38.3.2",8,"I don't understand opportunistically receiving or listening as mentioned in this paragraph, I think higher layer decisions and protocols should really be defined to control the MAC/PHY activity here. I think the actual protocol is only loosely defined here, and is perhaps really for upper layer protocol to define.",null,"The protocol is only loosely defined here, and really an upper layer protocol should be specified.  I am not sure what change is best/necessary.  Perhaps a way forward, rather than a vague descriptions would be to actually say that these details are left to the upper layer, but that an example is given in annex X.  Then add annex X with a very specific example laid out from upper layer perspectives with specific example numbers, initiator device sending AP at interval n, and responder devices turning on for period p every interval m, so that .... etc.","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Mickael Maman",null,34,"Yes","STMicroelectronics","Technical",57,"10.38.3.2",11,"define the role of advertiser and advertising devices. Currently only the initiation can be the advertiser and send an Advertising Poll compact frame.",null,"The advertiser (initiator or responder) may send Advertising Poll Compact frames opportunistically at times and intervals at its discretion as deemed suitable for the higher layer functionality to be supported. Similarly, the advertising (responder or initiator) may opportunistically listen for incoming Advertising Poll Compact frames. For the sake of simplicity, we will consider the initiator as the advertiser and the responder as the advertising. The reverse is also possible.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carl Murray",null,866,"No","Qorvo","Editorial",57,"10.38.3.2",15,"Probably a typo \"a monotonous grid\"",null,"Fix typo - not sure what word was meant to be here, possibly monotonic?","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1123,"No","Qorvo","Technical",57,"10.38.3.2",17,"If there is only one response why is it listening in multiple slots? Also \"shall\" is perhaps specifying something in a protocol layer that is really above the MAC.",null,"Change line to: \"The initiator can then listen for incoming advertising responses in these subsequent initialization slots.\"","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Tero Kivinen",null,400,"No","Self","Technical",57,"10.38.3.2",18,"How does the responder indicate it wants to receive Advertising Poll Compact Frame? The Advertising Poll Compact frame does not contain destination address, that would allow responder to recognize that it wants to receive that specific frame. It contains RPA prand and hash which means the for every single frame received the responder need to loop through every single IRK it has and check the hash to see whether it recognizes the sender of the frame, and even if it recognizes the frame, that does not mean it comes from the original sender, as it can also be replay frame. ",null,"There is no interface to specify that responder wants to listen Advertising Poll Compact Frames. There is no way of using hardware filtering to filter incoming frames. There is no replay protection to protect against replayed frames. Remove the compact frames and use the normal frames which do offer security, privacy, replay protection etc all features required by modern systems.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Srivathsa Masthi Parthasarathi",null,206,"No","NXP Semiconductors","Editorial",57,"10.38.3.2",20,"Use acronyms wherever applicable to reduce the verbatim ",null,"Start of Ranging (SOR) \nFurther in the document replace Start of Ranging with the acronym SOR","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carlos Aldana",null,990,"No","Meta Platforms","Technical",57,"10.38.3.2",20,"What frequency is used to transmit SOR frame? Please clarify.",null,"As in comment","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Srivathsa Masthi Parthasarathi",null,207,"No","NXP Semiconductors","Editorial",57,"10.38.3.2",21,"Reference to table to be added when value is mentioned, for better readability",null,null,"No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1124,"No","Qorvo","Technical",57,"10.38.3.2",21,"The phrasing here \"the status field set as SUCCESS\" using upper case is I think out-of-line with style used elsewhere in 802.15.4, and It improve clarity to give a reference to where the values are defined.",null,"Probably should be something like \"with the status field value set to indicate success as defined in Table 16\".  There a good few of these to change, and not just for the SUCCESS case. (i.e. each of the dash bullets on p 57 is similar, and line 34/36 of p58, and dash bullets top of p 59, etc.)","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,208,"No","NXP Semiconductors","Editorial",57,"10.38.3.2",34,"Missing reference value for REQUESTED_PARAMETERS_NOT_ACCEPTED",null,"Add reference value in brackets, applicable for line 37, 39,43","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,401,"No","Self","Editorial",57,"10.38.3.2",37,"Error code has spaces in it. ",null,"Remove spaces.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1298,"No","NXP Semiconductors","Editorial",57,"10.38.3.2",37,"Missing underscore \"_\" ",null,"REQUIRED_CAPABILITY_NOT_SUPPORTED_BY_RESPONDER","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pooria Pakrooh",null,1348,"No","Qualcomm","Technical",57,"10.38.3.3",17,"Which slots specifically? Initiator wants to go back to Tx mode. Specify how long it has  to be in Rx.",null,"Specify the range of slots where initiator shall listen for adv-resp.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1349,"No","Qualcomm","Technical",57,"10.38.3.3",22,"If the initiator likes to use paramteres suggested in the ADV_RESP message, what is the point of repeating the content? Change to: \"If initiator wants to use any of the suggested params in the adv-resp, it does not need to include them in the SOR message.",null," Change to: \"If initiator wants to use any of the suggested params in the adv-resp, it does not need to include them in the SOR message.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Rojan Chitrakar",null,110,"No","Huawei","Technical",58,"10.38.3",4,"SORs with Message Control field set to 0x10 (with value of the status field set as SUCCESS) is also applicable here.",null,"Add SORs with Message Control field set to 0x10 (with value of the status field set as SUCCESS).","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Mickael Maman",null,35,"Yes","STMicroelectronics","Editorial",58,"10.38.3.1",5,"typo \"pubic\" instead of \"public\"",null,"as in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,36,"Yes","STMicroelectronics","Editorial",58,"10.38.3.1",6,"typo capital letters for Start of Ranging",null,"as in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,37,"Yes","STMicroelectronics","Technical",58,"10.38.3.1",16,"when coordination active, the initiation may scan default init channel and default UWB channel. It could be only one of them.",null,"change \"and\" by \"and/or\" ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Li-Hsiang Sun",null,235,"No","MediaTek","Technical",58,"10.38.3.2",4,"\"After transmitting the Start of Ranging Compact frame with the Message Control field equal to 0x00 ?\" \nSOR with msg ctrl=0x10 can also indicate success",null,"change to \"After transmitting the Start of Ranging Compact frame with the Message Control field equal to 0x00, or the Start of Ranging Compact frame with the Message Control field equal to 0x10 and the value of the Status field set to SUCCESS\"","No",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,404,"No","Self","Technical",58,"10.38.3.2",4,"It seems that each different message control field values are different messages when the text is full of \"Start o Ranging Compact frame with the Message Control field equal to 0x00\" texts. ",null,"Combine Compact Frame id and message control field values to one message id and use that.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,403,"No","Self","Editorial",58,"10.38.3.2",5,"Typo Pubic. ",null,"Change Pubic to Public","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1299,"No","NXP Semiconductors","Editorial",58,"10.38.3.2",5,"Typo \"Pubic\" --> \"Public\"",null,"Replace \"pubic\" with \"public\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1125,"No","Qorvo","Editorial",58,"10.38.3.2",6,"The comma in this sentence is not necessary and makes it read incorrectly.",null,"Delete the ','.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Pooria Pakrooh",null,1350,"No","Qualcomm","Technical",58,"10.38.3.2",7,"Control phase seems to refer to \"initialization phase\"",null,"Replace \"control phase\" with initialization phase","Yes","Rejected","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"N/A"]
[null,null,"Tero Kivinen",null,405,"No","Self","Technical",58,"10.38.3.2",10,"The initialization process figure is nice, but the message sequence chart would also be needed, i.e., the figure that shows what higher layers and MLMEs do to initiate sending those messages. ",null,"Add message sequence chart for initialization showing which MLME calls are needed to initialize things in initiator and responder, and what MLME calls are used to transmit and receive those frames. My understanding is that at least some of the MLME calls are not defined yet, so making this chart would find out the gaps in the specification. Also as there are tight timing requirements between SOR and POLL frames that means all this should be done in the MAC, thus MLME call is needed to do the whole transaction.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,236,"No","MediaTek","Technical",58,"10.38.3.2",11,"The sequence of REPORTs in FIG 26~31,33 seems inconsistent with what is defined in 10.38.6",null,"fix the figures to be consistent with Fig 37","No",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,408,"No","Self","Technical",58,"10.38.3.2",11,"The SOR is not defined as acronym. Either spell it out or add it to acronyms. ",null,"The figures use short versions of the actual frame names, so perhaps just add legend to the figure that expands the names of frames from the shorthand version (\"ADV POLL\") to full name (\"Advetrising Poll Compact Frame\"). I do not know what the POLL and REPORT frames are supposed to be as there are multiple possible frames they could match.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1126,"No","Qorvo","Editorial",58,"10.38.3.2",11,"In Figure 26 (and 27) Lower grey lines from initiator and responder are drawn on top of and through the ranging phase messages.",null,"Fill poll and response packet boxes white, and push these grey lines to the back so they are not drawn on top of the packet boxes, in both Figures 26 and 27.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,402,"No","Self","Editorial",58,"10.38.3.2",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,406,"No","Self","Technical",58,"10.38.3.2",13,"What does \"coordination is active\" mean. Is this some kind of mode or what. How does device know whether coordination is active or not? ",null,"Add text that explains how devices know whether coordination is active or not.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1127,"No","Qorvo","Editorial",58,"10.38.3.2",13,"\"If the coordination is active\" unnecessary \"the\"",null,"change to \"If coordination is active\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1128,"No","Qorvo","Technical",58,"10.38.3.2",15,"This sentence says \"may\" scan on the \"default value\" of a channel configuration attribute which seems strange.  The \"default value\" piece is meaningless, since \"may\" is not mandating any particular behaviour or channel use. ",null,"If NB channel 2 is required.  Make it a constant \"2\" in the text or make a separate constant aNbApScanCannnel defined.  Also use \"should\" instead of \"may\" to at least give a more definite guideline of the behaviour implementation expected. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,210,"No","NXP Semiconductors","Editorial",58,"10.38.3.2",19,"use acronym for Advertising Confirmation Compact (ACC)",null,"Further in the document refer to Acronym","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1129,"No","Qorvo","Technical",58,"10.38.3.2",19,"\"subsequent slot after receiving\" reads poorly",null,"change to: \"slot subsequent to receiving\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,407,"No","Self","Technical",58,"10.38.3.2",23,"This text P58L23-P59L11 looks very similar to the P57L20-L44. There are minimal editorial differences, plus that the P57L35 requires the parameters to be different before reattempting and the typo on P59L4. ",null,"Remove lines P58L23-P59L11 and say that processing is identical than in when coordination is not active.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Shang-Te Yang",null,924,"Yes","Apple","Editorial",58,"10.38.3.2",23,"The text from line 23 P58 to line 12 P59 seems duplicated from previous section, with the only change of advertisement confirmation. Duplicated text is confusing to the reader. ",null,"Merge the two flows together and make \"acquisition confirmation\" optional. ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Wenzheng Li",null,186,"Non-Voter","Calterah Semiconductor ","Editorial",58,"10.38.3.2",24,"\"If the initiator intends to proceed to the control phase, the Message Control field of the Start of Ranging Compact frame shall be set to 0x00 or 0x10 (with value of the status field set as SUCCESS)\"\n0x20 is missing here.",null,"If the initiator intends to proceed to the control phase, the Message Control field of the Start of Ranging \n21 Compact frame shall be set to 0x00 or 0x20 or0x10 (with value of the status field set as SUCCESS)","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1130,"No","Qorvo","Technical",58,"10.38.3.2",24,"\"(with value of the status field set as SUCCESS).\" style/meaning needs updating",null,"removing parentheses, change to: \", with the status field set to indicate success as defined in Table 16.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1131,"No","Qorvo","Technical",58,"10.38.3.2",31,"it does not matter what is communicated via OOB, it is the values configured into appropriate PIB configurations that \"shall\" be used, e.g. phyCurrentChannelInfo, etc",null,"Need to figure out the architecture of layering and what does what, and ensure that PHY, MAC, and upper layer roles are understood and specified properly.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1132,"No","Qorvo","Technical",58,"10.38.3.2",31,"fields don't have default values, it should be the values configured into appropriate PIB configurations that \"shall\" be used, e.g. phyCurrentChannelInfo, etc",null,"See my other comments on same line number.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1133,"No","Qorvo","Technical",58,"10.38.3.2",31,"Logically, (to me at least), the compact frames exchanged are asking for particular configurations to be used, but it is the receiving control layer (above the MAC) that is deciding the validity of this and configuring the parameters in the PIB and commanding subsequent UWB MMS ranging packet transmission and reception, using MCPS-DATA.request.",null,"Rework the text accordingly.  Essentially to say that these SOR frames may specify PHY and MAC parameter, as may the ADV frames, and that the higher layer is responsible for configuring the phyCurrentChannelInfo and other attributes appropriately for the ranging phase. (Suggest to look at the parameters in these messages to see which primitive parameter or PIB attribute is set as a result, and figure out are we missing any controls.)","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,991,"No","Meta Platforms","Editorial",58,"10.38.3.2",32,"Remove the word \"Otherwise\" as it's unnecessary",null,"As in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pooria Pakrooh",null,1351,"No","Qualcomm","Technical",58,"10.38.3.2",32,"Why is this explanation for Status field repeated? Anything specific for the case where there is AP packet? If not, please remove this for better readability",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,209,"No","NXP Semiconductors","Technical",58,"10.38.3.2","1,2","strong assumption on Advertising Response has successfully received by the Initiator, which may not be true in all the scenarios",null,"responder shall listen to SOR and if the SOR is not received then it may listen to the next Adv Poll\nthe initiator may continue transmission of Adv Poll of Adv Response is not received ","Yes","Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Carlos Aldana",null,992,"No","Meta Platforms","Technical",58,"10.38.3.3",17,"Can you clarify whether all transmissions use the same init channel or only some of them?  It would be good to explictly enumerate which packets are part of the initialization phase.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,141,"No","Huawei","Editorial",59,"10.38.3.2",4,"\"REJECT_WITH_SUGGESTED_CONFIG_CHANGE\" should be \"REQUIRED_CAPABILITY_NOT SUPPORTED_BY_RESPONDER\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,237,"No","MediaTek","Technical",59,"10.38.3.2",4,"The value of the Status field should be \"REQUIRED_CAPABILITY_NOT_\nSUPPORTED_BY RESPONDER\" to be consistent with p57, L37 ",null,"as in comment","No",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,410,"No","Self","Technical",59,"10.38.3.2",4,"Why the REJECT_WITH_SUGGESTED_CONFIG_CHANGE is listed twice, and first time it says should not reattempt session initialization. ",null,"I think this error message should be REQUIRED_CAPABILITY_NOT_SUPPORTED_BY_RESPONDER instead, replace with that.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Pablo Corbalán Pelegrín",null,1300,"No","NXP Semiconductors","Editorial",59,"10.38.3.2",4,"Missing underscore \"_\" ",null,"REJECT_WITH_SUGGESTED_CONFIG_CHANGE","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1301,"No","NXP Semiconductors","Editorial",59,"10.38.3.2",6,"Missing underscore \"_\" ",null,"REJECT_WITH_SUGGESTED_CONFIG_CHANGE","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,213,"No","NXP Semiconductors","Technical",59,"10.38.3.2",10,"When Status field is FAILURE the responder is asked to reattempt session initialization at a later time",null,"\"later time\" needs to be a MLME parameter","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,411,"No","Self","Technical",59,"10.38.3.2",12,"Message sequence chart is missing. ",null,"Add message sequence chart for initialization when coordination is active.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pablo Corbalán Pelegrín",null,1302,"No","NXP Semiconductors","Editorial",59,"10.38.3.2",12,"Missing word \"is\"",null,"… when coordination is active is illustrated …","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,409,"No","Self","Editorial",59,"10.38.3.2",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,211,"No","NXP Semiconductors","Editorial",59,"10.38.3.2","4 to 9","using word should does not make the requirement mandatory and can potentially cause interop issues\n",null,"use shall instead of should","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,212,"No","NXP Semiconductors","Technical",59,"10.38.3.2","4 to 9","using the words should and may for the same error code REJECT_WITH SUGGESTED_CONFIG_CHANGE leads to contradiction\n",null,"In the following error conditions the responder may reattempt for session initiatization with the following Advertising poll if there is an error in session initializiation with the current Advertising poll.\n-- If the value of the Status field is REQUESTED_PARAMETERS_NOT_ACCEPTED\n-- If the value of the Status field is REJECT_WITH SUGGESTED_CONFIG_CHANGE\nIn the followig error conditions the responder shall not reattemp for Session initialization","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"B. Rolfe",null,1336,"Yes","BCA","Technical",59,"10.38.3.3",18,"\"may change\" really means \"might be changed by the higher layer\" I think. SO it's a possibility of which the MAC has no control.",null,"Change \"may\" to \"might\"",null,"Revised","doc 15-24-0440-01-04ab-lb207-d01-comment-resolution-mms-operation-initialization-cids-209-395-990-1122-1123-1336-1347-1350.docx","MMS",null,"Ready"]
[null,null,"Billy Verso",null,1134,"No","Qorvo","Technical",59,"10.38.3.3",19,"I am wondering about these slot configurations, 4z did not add any such parameters. It has the notion of slots but it left the mechanics to the next higher layer to command transmissions or receiver enable at the appropriate time for the slot use case. This meant that the MAC behaviour was simple and the protocol behaviours did not have to be specified in detail as would otherwise have been the case.",null,"Change the initialisation slots into a concept for the control layer rather than a hard MAC configuration…. The MAC is not really in control of sending the ADV POLL or RESP since it is relying to the next higher layer to provide the message content and command its transmission at the appropriate time via the MCPS-DATA.request, which is actually defining the slot boundary.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,142,"No","Huawei","Editorial",59,"10.38.3.3",20,"\"next higher\" should be \"next higher layer\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"B. Rolfe",null,1337,"Yes","BCA","Technical",59,"10.38.3.3",20,"\" may be changed by the next higher\" is a hint this is improper use of \"may\".  ",null,"change \"may\" to \"might\"",null,null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,111,"No","Huawei","Technical",59,"10.38.3.4",18,"\"The initiator may set the value of the field Time_Offset …\"\nThe sentence assumes that the SOR carries the optional Starting Block Index field; this should be made explicit. Also \"may\" should be \"shall\" here.",null,"Change to:\n\"If the Starting Block Index field is  present in the Start of Ranging Compact frame, initiator shall set the value of the field Time_Offset...\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,995,"No","Meta Platforms","Editorial",59,"10.38.3.4",20,"add the word \"layer\" after \"higher\"",null,"As in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,214,"No","NXP Semiconductors","Editorial",60,"10.38.3.4",2,"the initiator should choose…, this needs to be mandatory",null,"\"the initiator shall choose…\"","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1135,"No","Qorvo","Technical",60,"10.38.3.4",2,"\"choose the values\"  is not very clear to me in what it means.",null,"Not sure what is intended so I am not sure what change is needed, but I would be happy to work with the originating author to come up with a better description of the process.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1136,"No","Qorvo","Technical",60,"10.38.3.4",8,"\"If the initiator changes the value of the NB Channel Map field received from the Advertising Response Compact frame, it shall change the value...\", i think should be reworded since it is not really changing the received field.",null,"Change the sentence to \"If the initiator wishes, it may choose an alternate channel map to that specified in the NB Channel Map field of the received Advertising Response Compact frame, in which case it shall choose a channel map that is a subset of the channels requested by the responder.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,993,"No","Meta Platforms","Technical",60,"10.38.3.4",9,"What if there is no subset? Can you write expected behavior?",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1137,"No","Qorvo","Technical",60,"10.38.3.4",11,"The text is talking about \"field values\" when it means choosing / negotiating configuration parameters values other than those being specified by the by the messages.  This makes it harder to understand.",null,"The paragraph (and more) needs a rewrite with clear language referring to what is a field value and what is a configuration parameter, although I appreciate this is a somewhat abstract description when in detail the messages being discussed have different forms with many fields and sub-fields, which would need to be considered/handled for any real implementation of this negotiation.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,143,"No","Huawei","Editorial",60,"10.38.3.4",22,"\"Time_Offset\" should be \"Time Offset\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Bin Qian",null,144,"No","Huawei","Editorial",60,"10.38.3.4",24,"\"NB_Channel_Seed\" should be \"NB Channel Seed\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"B. Rolfe",null,1338,"Yes","BCA","Technical",60,"10.38.3.4 ",15,"\"device may be provided by higher layer functionality\" is stating a possibility, not an option.",null,"change \"may\" to \"might\"",null,null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,412,"No","Self","Editorial",60,"10.38.3.5",1,"There is Figure 28-31 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,38,"Yes","STMicroelectronics","Editorial",60,"10.38.3.5",29,"typo capital letters for Cap and move contention access period from line 31",null,"as in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Srivathsa Masthi Parthasarathi",null,215,"No","NXP Semiconductors","Editorial",60,"10.38.3.5",29,"Inconsistent capitalization of acronym",null,"Cap should be changed to CAP","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,413,"No","Self","Technical",60,"10.38.3.5",29,"The text says that initiator sends Advertising Poll Compact frame to one or more intended responders, but the Advertising Poll Compact frame does not include destination address, thus it is not possible to send it to only one or some intended responders. Everybody who is on the channel will hear it and assume it is meant for them. ",null,"Add destination field to the Advertising Poll Compact frame so it can be sent to only some intended responder.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Koorosh Akhavan",null,968,"No","Qualcomm","Editorial",60,"10.38.3.5",29,"Change \"Cap\" to \"CAP\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1138,"No","Qorvo","Editorial",60,"10.38.3.5",29,"Cap Duration field, should be \"CAP Duration\".",null,"Change to \"CAP Duration\" here, and in Figures 63, 64, 111, 112, 113","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1139,"No","Qorvo","Technical",60,"10.38.3.5",32,"\"starting from the end\", I think should instead be a start-to-start relationship, as is used elsewhere in the text.  It cannot start immediately since it (and the slot size) needs to allow for the processing of the message and the radio turn around times, etc.",null,"Change: \"starting from the end of the Advertising Poll Compact frame.\", to \"starting in the next slot referenced from the start of the Advertising Poll Compact frame and the Initialization Slot Duration field value it carries.\"; and, add a \"NOTE: The initialization slot duration needs to be long enough to encompass the longest packet expected, its processing time in the received, and any radio turn-on or turn-around times.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,414,"No","Self","Technical",60,"10.38.3.5",41,"How long does the responder listen for advertising confirmation or start of ranging compact frames? ",null,"Specify how long will the responder wait for confirmation.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1140,"No","Qorvo","Technical",60,"10.38.3.5",41,"\"shall listen\", for how long? Just in the next slot? This should be defined.",null,"State whether this listening is just in the first initialization slot after the CAP or when and for how long it should listen","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Carl Murray",null,867,"No","Qorvo","Editorial",61,"10.38.3.5",3,"typo in \"… and the coordination is inactive\"",null,"Remove 'the'","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,416,"No","Self","Technical",61,"10.38.3.5",4,"For one to one ranging the Start of Ranging Compact frame RPA hash is calculated using initiators IRK. ",null,"Add text about the IRK to be used here.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,417,"No","Self","Technical",61,"10.38.3.5",7,"The figure 28 is good, but message sequence chart is also needed. ",null,"Add MSC for the one-to-one ranging exchange showing the MLME-calls done, i.e., how does the initiator higher layer indicate to which device it want to start the exchange with, and how do the initiator receive those ADV RESP packets.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1141,"No","Qorvo","Technical",61,"10.38.3.5",7,"Since this is talking about contention and a CAP, it would probably be good for the Figure(s) to show where the CAP is.  ",null,"Show the CAP in Figure 28, and other figures.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1142,"No","Qorvo","Technical",61,"10.38.3.5",8,"I suppose a responder seeing the ADV poll, and knowing were the initialisation slots / CAP ends, knows it can (a) turn off until it is time to transmit its response in its chosen/assigned slot, and (b) then turn off again until it is time to turn on its receiver again to receive SOR or ADV CONF.  Perhaps this is worth pointing out.",null,"Add a statement to guide the implementors on this point.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1143,"No","Qorvo","Technical",61,"10.38.3.5",8,"As this is the one-to-one case, do the other responders see the SOR and somehow know they were not selected so can stop listening? (And return to periodic scan?)",null,"Add a statement to guide the implementors on this point.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Srivathsa Masthi Parthasarathi",null,216,"No","NXP Semiconductors","Technical",61,"10.38.3.5",9,"Figure 28, suggested method of initialization in CAP is also applicale for one-to-one and one-to-many schemes, would it be possible to have one kind of initialization scheme and make it applicable for other contention free session initialization scheme ?",null,"potentially one scheme can be repurposed for other session init scheme","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Pablo Corbalán Pelegrín",null,1303,"No","NXP Semiconductors","Editorial",61,"10.38.3.5",9,"As only two responders are shown in Figure 28, shall we replace \"Responder n\" with \"Responder 2\"? Otherwise, we may wan to use \"…\" to show that additional responders could be replying. The same comment applies to subsequent figures in the section.",null,"Replace \"Responder n\" with \"Responder 2\" or add \"…\" in between the two responders.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,415,"No","Self","Editorial",61,"10.38.3.5",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,418,"No","Self","Editorial",62,"10.38.3.5",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,420,"No","Self","Technical",62,"10.38.3.5",2,"Message sequence chart is missing. ",null,"Add message sequence chart.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,422,"No","Self","Technical",62,"10.38.3.5",11,"For multiple one to one ranging I assume the Start of Ranging Compact frame RPA hash is calculated using initiators IRK. ",null,"Add text about the IRK to be used here.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Carl Murray",null,868,"No","Qorvo","Editorial",62,"10.38.3.5",11,"typo in \"… and the coordination is inactive\"",null,"Remove 'the'","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1144,"No","Qorvo","Technical",62,"10.38.3.5",13,"In the figures 28 to 31, there are slots and messages, initialisation slots, ranging slots, and It looks like the messages are same size as the slots. In reality the messages will be smaller than the slots size, and it will have to be that way to give time for processing and preparing for respond.  The figures don't really show that and the text doesn't explain that either.",null,"Consider whether any update to the figure is needed to show slots and messages withing slots, and/or note that in the text.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,421,"No","Self","Technical",62,"10.38.3.5",14,"Message sequence chart is missing. ",null,"Add message sequence chart.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1145,"No","Qorvo","Technical",62,"10.38.3.5",15,"The size of MMS initialisation slots and ranging slots is in units of 300 RTSU (0.25 ms), while the offset to SOR is in UWB chips, so can be arbitrarily aligned to the initialisation slot grid.\n",null,"Maybe it is obvious, but perhaps it would help designers reading the standard if this was noted as part of the figure description.  Also, consider whether such precise offset control is needed and if not the offset field could be in coarser units and smaller in size, saving energy.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,419,"No","Self","Editorial",62,"10.38.3.5",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,423,"No","Self","Technical",62,"10.38.3.5",18,"For one to many ranging which IRK is used for the Start of Ranging Compact frame RPA hash. ",null,"Add text about the IRK to be used here.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,424,"No","Self","Technical",62,"10.38.3.5",22,"Message sequence chart is missing. ",null,"Add message sequence chart.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1146,"No","Qorvo","Technical",63,"10.38.3.5",1,"In Figure 31 the \"SOR n\" line designated \"time offset to corresponding poll\" is not pointing to the poll for responder n (it was in pre-ballot draft C) so the designated/description is wrong.",null,"Make it clear in the descriptions if this is the time offset to the start of the ranging round that each responder is timing its own ranging sub-round from that.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1147,"No","Qorvo","Technical",63,"10.38.3.5",1,"In Figure 31 it seems to be showing the O2M POLL for responder 'n' starting exactly at the end of the O2M R RPRT from Responder 1.  This would only be the case if n=2.  (In this figure in the previous draft they were not shown like this.)   If they are supposed to be back to back like this, than make n=2, or draw figure with spacing to (n) responder n relative to the first something line (n-1)*macRangingSubRoundDuration.",null,"Fix the figure and explain in the text the key points being conveyed. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Pooria Pakrooh",null,1352,"No","Qualcomm","Technical",63,"10.38.3.5",1,"In Figure 31, \"Time offset\" should be drawn from SOR to the \"one to many first common Poll\", not corresponding poll.",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,425,"No","Self","Editorial",63,"10.38.3.5",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1148,"No","Qorvo","Technical",63,"10.38.3.5",6,"\"shall enter the control phase\" is here and on line 10, but I guess strictly speaking this does not happen until the time offset specified by the SOR has elapsed, (which could be seconds away given the unit and the size of the field)",null,"Change to \"enters the control phase at the time specified by the Time Offset field in the Start of Ranging Compact frame\", (NB: removing the \"shall\" here since these phases are really conceptual and defined by what the next higher later does.) \nChange on line 10 also.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,426,"No","Self","Editorial",63,"10.38.3.6.1",1,"There is Figure 32-33 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,427,"No","Self","Technical",63,"10.38.3.6.1",16,"All the addresses in the compact frames are public, as the privacy properties of the supposed \"private addresses\" are so weak that they are public too. ",null,"Remove distinction of ranging using private or public addresses, as they both are public, or change to use proper private addresses defined in 802.15.4ac.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,145,"No","Huawei","Editorial",63,"10.38.3.6.1",24,"\"RPA_hash\" should be \"RPA Hash\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1149,"No","Qorvo","Editorial",63,"10.38.3.6.1",24,"\"except for generating IRKs for the RPA_hash specified in 10.38.3.6.2.\" does not read well.",null,"Change to \"except that generating IRKs for the RPA_hash is done as specified in 10.38.3.6.2.\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1150,"No","Qorvo","Technical",63,"10.38.3.6.1",25,"\"may send\", is not right I think because if it doesn't send them there will be no initialisation.",null,"change to \"sends\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1151,"No","Qorvo","Technical",63,"10.38.3.6.1",25,"There are lots of \"may\" in the text which are possibly also questionable for the same reason, and perhaps could be similarly removed.",null,"Review uses of \"may\" everywhere, and consider removing/rewording to be more definite in language.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1152,"No","Qorvo","Technical",63,"10.38.3.6.1",29,"\"Once a responder has received Public Advertising Poll Compact frame\", missing \"a\", but also perhaps there is some qualification needed here, i.e., some validation by the application that it wants to start talking to this particular initiator.",null,"\"If a responder receives a Public Advertising Poll Compact frame from an initiator that it wants to perform ranging with, ….\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Hong Won Lee",null,1411,"No","LG Electronics","Editorial",64,"10.38.3.6",8,"\"RespAddr\" name should be aligned with address field in public compact frames",null,"Change from \"RespAddr\" to \"Responder Address\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1153,"No","Qorvo","Editorial",64,"10.38.3.6.1",1,"missing article",null,"Insert \"a\" before \"Public Advertising Response Compact frame\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,430,"No","Self","Technical",64,"10.38.3.6.1",7,"The figure 32 should be expanded to proper message sequence chart, and include the MLME calls made by each side to send those messages. ",null,"Expand Figure 32 to proper MSC.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Pablo Corbalán Pelegrín",null,1304,"No","NXP Semiconductors","Editorial",64,"10.38.3.6.1",7,"Remove \"the\": This procedure is shown in the Figure 32.",null,"This procedure is shown in Figure 32.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,428,"No","Self","Editorial",64,"10.38.3.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,431,"No","Self","Technical",64,"10.38.3.6.1",9,"The figure 32 is missing the POLL and RESP and ranging phases and REPORT frames shown on figure 33. ",null,"Add second half to the figure 32 to show what frames are sent / received and what MLME calls are done during the actual ranging phase on the ranging channel (you could use different arrow to indicate which messages are sent in initialization channel and which are sent on ranging channel).","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1154,"No","Qorvo","Technical",64,"10.38.3.6.1",9,"Figure is wrong, the frame names should match compact frame names, and not be in upper case hyphenated typically only used for primitives.  Also RespAddr should be \"Responder Address\".",null,"Change \"RespAddr\" to \"Responder Address\", and change \"PUBLIC-ADV-POLL\", to \"Public Advertising Response Compact frame\" etc.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,429,"No","Self","Editorial",64,"10.38.3.6.1",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Lei HUANG",null,1433,"Yes","Huawei","Technical",64,"10.38.3.6.1",13,"It is better to clarify what are coordination packets.",null,"Change \"coordination packets\" to \"Acquisition Compact frames\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1155,"No","Qorvo","Technical",64,"10.38.3.6.1",14,"\"with a public address\" is not needed here I think since the frame by definition has a public address, and the \"with a public address\" right before \"to defer…\" seems to suggest that is it the public address doing the deferral when in fact it is the confirmation message itself that is doing it.",null,"delete \"with a public address\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,432,"No","Self","Technical",64,"10.38.3.6.1",15,"The figure 27 does not show the use of public start of ranging compact frames. ",null,"Change text to say \"transmission of the Public Start of Ranging Compact frame similarly as is done in Figure 27\", as we are just doing things similarly than in figure 27, but using different frames.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,433,"No","Self","Technical",64,"10.38.3.6.1",19,"Why switch from more private addresses to less private? Completely randomly generated 24-bit source and destination addresses are more private then addresses generated using 24-bit hashing. ",null,"Just use the public addresses throughout the whole ranging process. During the initialization phase both ends learns the random 24-bit addresses to be used, and they can easily be used during ranging phase. My understanding is that the ranging phase is not going to be taking more than few minutes at max, so keeping same address during the whole ranging phase is not an issue, as the \"private\" addresses also uses the same prand during the ranging phase, i.e., addresses do not change even there during ranging phase.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Mickael Maman",null,39,"Yes","STMicroelectronics","Technical",64,"10.38.3.6.1",22,"is it possible to start an initialization process with public addresses for the variantes defined in 10.38.3.5 (e.g. multiple one-to-one, one to many) ",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Bin Qian",null,146,"No","Huawei","Editorial",64,"10.38.3.6.1","20, 22","\"RPA_hash\" should be \"RPA Hash\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,435,"No","Self","Editorial",65,"10.38.3.6.2",1,"There is Figure 34 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,437,"No","Self","Technical",65,"10.38.3.6.2",1,"All this RPA_hash generation is just extra work for the both devices without any gain. It does not offer any technical benefits, but will cause extra cost. ",null,"Remove this RPA_hash generation and use public addresses directly during the ranging phase. If the broken addressing structure in the ranging phase cannot be fixed, you could also define that prand must be generated so that it is never all zeros, and reserve that value to mean that no hashing is done and hash will then directly be the public address. This would allow keeping the RPA_prand and hash frame format in ranging frames without changing them. Poll frame would use responder address as hash and prand of zero, the Response would use initiators address as hash, etc. I.e., the hash field would be used as the destination address field.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1156,"No","Qorvo","Technical",65,"10.38.3.6.2",1,"\"RPA_hash\" with underscore is a format not typically used in the base standard to describe something ",null,"If technically acceptable, change \"RPA_hash\" (everywhere it appears) to \"RPA hash\" without the underscore, otherwise pick another technically acceptable term not using underscore.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,436,"No","Self","Technical",65,"10.38.3.6.2",2,"There is no need to list the frames used for initialization setup, as this will just be duplicating information and if someone adds or modifies the setup phase all these locations needs to be changed. ",null,"Simply say \"after the initialization setup handshake usng public addresses the IRK\".","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,434,"No","Self","Editorial",65,"10.38.3.6.2",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,148,"No","Huawei","Editorial",65,"10.38.3.6.2",17,"\"POLL\" should be \"Poll\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,438,"No","Self","Technical",65,"10.38.3.6.2",18,"If the public addresses are used directly then the address list inside the one-to-many poll could simply be the public address of the responder, no need to generate GroupID or special message control field value 0x21 poll format at all. ",null,"Remove GroupID concept as it is not needed if public addresses are used directly. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1157,"No","Qorvo","Technical",65,"10.38.3.6.2",24,"Strange negatives here \"The GroupID is NOT shared if a Public Advertising Poll Compact frame with the Message Control field value is NOT set to 0x21 on the initialization channel.\" Also I don't fully understand the sentence, it seems to be badly formed.",null,"Rewrite to use positive definition of something that is done instead of defining something that isn't done.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1158,"No","Qorvo","Technical",65,"10.38.3.6.2",27,"Strange to talk about the frame with Message Control not set to 0x00.  This should identify the frame with the particular the control field value wanted, rather than with one not wanted. Like this, maintenance of the text is harder, i.e., if a new ID value is defined would this line apply or not, could be hard to know to review/revise this line.",null,"Change to positive specification of the desired frame and behaviour.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Carl Murray",null,869,"No","Qorvo","Editorial",65,"10.38.3.6.2",36,"typo in \"The example in the below specifies ..\"",null,"Remove \"in the\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Bin Qian",null,147,"No","Huawei","Editorial",65,"10.38.3.6.2","1, 5","\"RPA_hash\" should be \"RPA Hash\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1305,"No","NXP Semiconductors","Editorial",66,"10.38.3.4",7,"I suggest replacing \"setup\" with \"initialization\".",null,"Unless set up during ranging initialization (10.383.4)","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,439,"No","Self","Technical",66,"10.38.3.7",6,"How is this ranging block structure set up? ",null,"Add message sequence chart showing what MLME calls are needed to set up the ranging block structure.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1159,"No","Qorvo","Technical",66,"10.38.3.7",7,"\"configured\", maybe \"agreed\" is better, if we accept that this is really in the realms of next higher layer since it is NHL that is initiating the interactions in each slot.",null,"Change accordingly.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1160,"No","Qorvo","Technical",66,"10.38.3.7",8,"\"shall be applied\" is something strange to do with defaults.  Maybe the upper layer should reset the MAC before starting,  but perhaps that goes without saying.  There is already a primitive to do that in the base standard.",null,"delete the sentence.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"B. Rolfe",null,1339,"Yes","BCA","Technical",66,"10.38.3.7",9,"\" round may be updated by the next higher layer. \" s/b \"might\"",null,"change \"may\" to \"might\"",null,null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1353,"No","Qualcomm","Technical",66,"10.38.3.7",10,"This sentence is Mandating a behaviour to upper layer. Change shall to should.",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1161,"No","Qorvo","Technical",66,"10.38.3.7",13,"The MAC (by definition, without stating it) uses the parameters set by the NHL.  These can be negotiated in any way, like OOB methods or using the compact frames defined in the text, which I believe the MAC does not (and should not) act on without NHL oversight.  I think short term parameter changes are the same, i.e. the NHL gets the parameter change request and decides whether/how to re-configure the MAC. (Line 23 clearly indicates there is a decision involved beyond the scope of the MAC specification).",null,"Rewrite this and the next paragraph to reflect this architecture (assuming I am right) or possibly considerer to delete them if they not really saying anything that needs to be said.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Koorosh Akhavan",null,966,"No","Qualcomm","Technical",66,"10.38.3.7",19,"Why do the short-term parameters only effective in the exisitng round? Once a paramter change is required, it does not seem to be efficient to change the parameters at every round. The parameters should take effect, until changed.",null,"As in the comment","Yes","Rejected","Because there is no acknowledgement mechanism with compact frames.","MMS",null,"N/A"]
[null,null,"Pooria Pakrooh",null,1354,"No","Qualcomm","Technical",66,"10.38.3.7",19,"This design for the behaviour of the short term parameters has several issues:\n1. If the devices need to switch the parameters for the remainder of the ranging session, they need to keep sending the short term parameters.\n\n2. What is the jusfification for changing the parameters other than NB channel map (such as ...). for one single round? \n\n3. The way short term parameters behaviour is defined, it can lead to extensive airtime without proper justification.",null,"1. Limit the short term change parameters to NB channel map. \n2. Explain the need for changing the other parameters in the middle of the session.\n3. Specify that the parameters changed will take effect until changed back again, and not only in the susequent round.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,997,"No","Meta Platforms","Technical",66,"10.38.3.7",66,"I see value in changing channel map in the short-term parameters.  Please limit changing the short-term parameters to include *only* channel map.  May want to create a Message content field with just NB Channel Map.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,440,"No","Self","Technical",66,"10.38.3.8",27,"How is this done inside the MAC, i.e., how does the upper layer configure this information. ",null,"Provide message sequence chart that shows how this indication procedure is done.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"B. Rolfe",null,1340,"Yes","BCA","Technical",66,"10.38.3.8",27,"\" may indicate \" seems strange here. Is this an option or a statement of fact?  If the prior it's fine. If the later it should be \"indicates\" ",null,"see comment, pick one.",null,null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,441,"No","Self","Technical",66,"10.38.3.9",36,"This section is way too late. There were already lots of descriptions about how to set up things when using coordination or when not using coordination. ",null,"Move this subsection much earlier, something like after 10.38.2 before 10.38.3 which uses it.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pooria Pakrooh",null,1355,"No","Qualcomm","Editorial",66,"10.38.3.9",37,"Change \"This\" to \"The\"",null,"Change \"This\" to \"The\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Wenzheng Li",null,197,"Non-Voter","Calterah Semiconductor ","Technical",67,"10.28.4.1",36,"poll Compact and Response Compact frame can be used for short-term operating parameters negotiation. But for NBA MMS, LBT may be mandatory before transmitting poll compact or response compact frame for initiator and responder. In this case, a short Compact frame length should be preferred. In the current poll Compact frame and response compact frame, the management PHY/MAC, Ranging PHY/MAC parameters and other parameters should be included for short-term operating parameters negotiation, which may lead to a very long frame.",null,"An index related to a set of management PHY/MAC, ranging PHY/MAC or other parameters may be introduced in the MMS control phase for  short-term operating parameters negotiation, in order to shorten the compact frame. ","No",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,443,"No","Self","Technical",67,"10.38.3",13,"Provide message sequence chart of how to start new session while using coordination, i.e., scanning channel, listening for acquisition compact frames (how are those frames sent from the MAC to next higher layer, i.e., what MLME call is used for them etc). ",null,"Add message sequence chart.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Carl Murray",null,870,"No","Qorvo","Editorial",67,"10.38.3.9",1,"typo in \"higher layer determines whether the coordination is active or not\"",null,"Remove 'the'","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1162,"No","Qorvo","Technical",67,"10.38.3.9",7,"The phrase \"the default value of the macMmsNbInitChannel attribute\" is used here, which is strange, if a single constant channel number is required at all times for this coordination then let's make that clear with a separate constant value for this.",null,"For this use change macMmsNbInitChannel to say using O-QPSK 5800 MHz band channel 2, or better still use the resolution for my comment on line 8.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1163,"No","Qorvo","Technical",67,"10.38.3.9",8,"The phrase \"the default value of the macMmsUwbChannel attribute\" is used here, which is strange.  If a single constant UWB channel number is required for this, it is probably better to define this as a constant, but note that this is not sufficient for proper UWB interworking. For that, it is also needed to specify the UWB packet format, and the preamble code, and the data rate etc, which are all needed for UWB reception to interwork. Since coordination and scanning is largely an upper layer procedure, perhaps it should be left to the upper layer to set the already defined PHY parameters to select the UWB channel, preamble code, data rate before sending the Acquisition Compact frame, or listening for them, i.e., leave it for the next higher layer specification body to decide what configuration to use, along with the duration and time intervals of the scanning, etc.).",null,"Delete these attributes and change the sentence to say \"The initiator transmits the NB Acquisition Compact frame using the O-QPSK PHY and transmits the UWB Acquisition\nCompact frame using the HRP UWB PHY.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1164,"No","Qorvo","Technical",67,"10.38.3.9",14,"The phrase \"the default value of the macMmsNbInitChannel attribute\" is used here…   see my comments on lines 7 and 8, and their proposed resolutions.",null,"See the resolution for my comments on lines 7 & 8.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1165,"No","Qorvo","Technical",67,"10.38.3.9",15,"The phrase \"the default value of the macMmsUwbChannel attribute\" is used here... see my comments on lines 7 and 8, and proposed resolutions.",null,"See the resolution for my comment on line 8.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Mickael Maman",null,40,"Yes","STMicroelectronics","Technical",67,"10.38.4",21,"Clarify if the UWB MMS control phase is defined for both PHYs (UWB and OQPSK) and if they are using the same packet format (POLL and RESP compact frame)",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1166,"No","Qorvo","Technical",67,"10.38.4",21,"Clause 10.38.8 is covering Procedures for one-to-many MMS ranging, and I am wondering the content from 10.38.4 to 10.38.7 shou be combined under a single umbrella of \"Procedures for one-to-one MMS ranging\"",null,"Consider whether this makes sense to help the read/user better understand the standard, and if so provide instructions to the editor to guide which parts would be appropriate to a common general section, and which parts should be made one-to-one case specific.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,442,"No","Self","Editorial",67,"10.38.4.1",1,"There is Figure 35 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1167,"No","Qorvo","Technical",67,"10.38.4.1",26,"This says \"may extend transmission of the poll\nCompact frame\", but the transmission time itself is dependant only on the content of poll frame.  This is really talking about the dimensioning of the slot.  Which should take account of any LBT pause before the TX, the expected packet length itself, local device turnaround time, and the reception processing, response generation, turn-around time of the remote system since the next packet (i.e., a response) is expected to be begin directly at the end of this period.  To keep packet boundaries on the 300 RSTU grid would suggest to leave 300 RSTU free after the end od the TX frame for all RX processing.",null,"Reword the sentence as per comment, i.e., say the  slot size should be set based on the factors as pet the comment.  And I think it should always incorporate allowance for LBT up front, even if LBT is not on, so that enabling or disabling LBT does not need to change the slot size.  Also potentially, one end might opt to do LBT when the other might not.  ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,41,"Yes","STMicroelectronics","Technical",67,"10.38.4.1",29,"The responder that receives the poll Compact frame\nsuccessfully should transmit a response Compact frame back to the initiator beginning in the ranging slot following the poll period",null,"shall transmit back response if poll correctly received","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,149,"No","Huawei","Technical",67,"10.38.4.1",35,"The poll Compact frame refers not only to one-to-one ranging case, but also to one-to-many ranging case",null,"Change the first sentence to \"The Poll Compact frame (10.38.9.7 and 10.38.9.12) serves to enable carrier coherent transmissions from the initiator to the responder device.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,444,"No","Self","Technical",67,"10.38.4.1",35,"How is this short term operating parameter update done inside the device? ",null,"Provide message sequence chart that shows what MLME calls are needed to set things up.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1168,"No","Qorvo","Technical",67,"10.38.4.1",35,"The phrase \"carrier coherent transmissions\" appears six times, in the text.  This should be defined. Actually the phrasing is the same in all six cases \"serves to\nenable carrier coherent transmissions\" the meaning of this phrase should be explained. ",null,"Add an appropriate definition for \"carrier coherent transmissions\" into clause 3.1 and since I expect this is one of the key feature requirements of NBA UWB MMS add some paragraph(s) into the introduction 10.38.1 to explain what it is. Also, consider whether \"serves to enable carrier coherent transmissions\" is a correct phrase and either explain its meaning or revise if necessary and explain the revised phrasing.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,445,"No","Self","Editorial",68,"10.38.4.1",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1169,"No","Qorvo","Technical",68,"10.38.4.1",13,"\"if either of following conditions is met\" is a bit wordy, a simple \"when\" would suffice.",null,"change to \"when\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Koorosh Akhavan",null,967,"No","Qualcomm","Technical",68,"10.38.4.2",10,"The draft needs to define a mechanism for NB channel access, to provide good coexistence of NB functionality with other devices and technologies operating in the UNII3/5 bands. \n\n",null,"Define a mandatory coexistence mechanism for NB OQPSK in UNII-3/5 with clear implementation details.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pooria Pakrooh",null,1356,"No","Qualcomm","Technical",68,"10.38.4.2",10,"The draft needs to define a mandatory mechanism to ensure good coexistence of NB functionality with other 4ab NB decives, as well as other technologies in UNII-3 and UNII-5 bands. \nSpecifying that LBT \"may be used\" is not a good coexistence practice as it causes confusion for the implementers, due to lack of details. The \"NBA channel access\" subclause needs to specify a detailed mandatory mechanism for the implementers of the 15.4ab, to ensure good coexistence with other NB devices as well as other technologies such as 802.11 devices. ",null,"Adopt a mandatory coexistence mechanism for NB operation in UNII-3 and UNII-5 bands. A good proposal has been presented and evaluated in DCN 15-24-212/r5, which does not impact low duty cycle ranging operations. Further details such as ED threshold need to be discussed and specified as well.\n\nChange FROM:\n\"For the NBA, channel access may use the listen-before-talk (LBT) functionality defined in 10.38.7.3.\"\n\nTO:\n\n\"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle.\nFor a NB capable device, if its NB transmission duty cycle is more than 2.5% (exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carlos Aldana",null,996,"No","Meta Platforms","Technical",68,"10.38.4.2",68,"given there is no baseline coexistence mechanism for NB, we should use LBT as the baseline.  change \"may\" to \"shall\"",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,446,"No","Self","Editorial",68,"10.38.5",1,"There is Figure 36 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Mickael Maman",null,42,"Yes","STMicroelectronics","Technical",68,"10.38.5",23,"RSF fragments are not mandatory in case of RIF only. Then change \"shall\" to \"may\"",null,"In the ranging phase, the initiator may transmit phyUwbMmsRsfNumberFrags RSF fragments","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Wenzheng Li",null,187,"Non-Voter","Calterah Semiconductor ","Technical",68,"10.38.5",23,"In this sub-clause, the ranging phase only for NBA UWB MMS is stated. For the UWB driven UWB MMS, the initial exchanged MMS fragment shall be SYNC+SFD. ",null,"The UWB driven UWB MMS with initial SYNC+SFD fragments exchange shall be added to be described in this sub-clause ","Yes",null,"Doc 15-24-0403-01-04ab-proposed-resolution-for-uwb-driven-mms-and-oob-assisted-mms.docx","MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1170,"No","Qorvo","Technical",68,"10.38.5",23,"Lines 23 through to Line 6 of the next page, are trying to explain the PHY packet in words, this should be clear from clause 16 and should not be repeated here.",null,"Delete as much as possible from this clause, since it is already specified in clause 16 (which is where this PHY level stuff it should be specified). Clause 16 should reference/use the PIB phyUwbMmsRsfNumberFrags and phyUwbMmsRifNumberFrags configurations, so they don’t need to be mentioned here again.  All it that is needed to say is that, responder fragments are offset by 600 RSTU, as shown in the figure.","Yes",null,"doc 15-24-0435-00-04ab-draft-1-comment-resolutions.docx","MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Mickael Maman",null,43,"Yes","STMicroelectronics","Technical",68,"10.38.5",27,"duration between RSF and RIF could be defined at least 2ms",null,"The initiator may start transmitting a first RIF fragment at the start of the ranging phase if no RSF fragments are present, or at least two milliseconds (2400 RSTU) after the start of its last RSF fragment\ntransmission otherwise. This parameter is RpRifOffsetInitiator.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,44,"Yes","STMicroelectronics","Technical",69,"10.38.5",3,"duration between RSF and RIF could be defined at least 2ms",null,"The responder may start transmitting a first RIF fragment at 600 RSTU into the ranging phase if no RSF fragments were transmitted, or at least two milliseconds (2400 RSTU) after the start of its last RSF fragment transmission otherwise.This parameter is RpRifOffsetIResponder.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Frank Leong",null,96,"No","NXP Semiconductors","Technical",69,"10.38.5",3,"The example only represents interleaved MMS operation. A non-interleaved example should be added.",null,"Add a paragraph stating \"The responder may start transmitting a first RIF or RSF fragment at 1200 RSTU after the start of the last initiator RSF or RIF fragment.\" Add another similar paragraph for the DS-TWR case.","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Frank"]
[null,null,"Tero Kivinen",null,449,"No","Self","Editorial",69,"10.38.5",7,"X and Y should be italics as they are variables. ",null,"Change X and Y to italics.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Riku Pirhonen",null,952,"No","NXP Semiconductors","Technical",69,"10.38.5",7,"In order to support traditional SS-TWR and DS-TWR, non-interleaved mode is proposed. It would delay sending responder MMS packet by RpDuration and, for DS-TWR, initiator can send another MMS packet after two RpDurations.",null,"In non-interleaved mode responder shall start transmission of MMS packet after one RpDuration from the start of the ranging phase, and when DS-TWR is desired, initiator may transmit a second MMS packet after two RpDurations from the start of the ranging phase.","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Riku Pirhonen",null,953,"No","NXP Semiconductors","Technical",69,"10.38.5",12,"Add behavior in case of the proposed non-interleaved mode.",null,"After macMmsRpDuration, or in case of non-interleaved mode after double or triple macMmsRpDuration as defined by the ExtendedRpDuration, and transmission and reception of all the fragments…","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Frank Leong",null,97,"No","NXP Semiconductors","Technical",69,"10.38.5",15,"The example only represents interleaved MMS operation. A non-interleaved example should be added.",null,"Add two similar figures, one showing non-interleaved SS-TWR MMS operation (2*RpDuration), and another showing non-interleaved DS-TWR MMS operation (3*RpDuration).","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Frank"]
[null,null,"Mickael Maman",null,45,"Yes","STMicroelectronics","Technical",69,"10.38.5",16,"in a particular case, the responder could send the first fragment",null,"In the ranging phase, the responder may also transmit phyUwbMmsRsfNumberFrags RSF fragments starting its first fragment at the start of the ranging phase and the initiator may start transmitting a first RSF fragment at 600 RSTU into the ranging phase. For the sake of simplicity, in this standard the initiator always start to send the first fragment but the switch is also possible.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,447,"No","Self","Editorial",69,"10.38.5",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Riku Pirhonen",null,954,"No","NXP Semiconductors","Technical",69,"10.38.5",16,"Add picture of the proposed non-interleaved mode",null,"Add picture that shows non-interleaved mode with double and triple RpDuration.","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Tero Kivinen",null,448,"No","Self","Editorial",69,"10.38.6",1,"There is Figure 37 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1171,"No","Qorvo","Technical",69,"10.38.6",20,"macMmsReportSender is unnecessary I think since I believe that the MAC does not act autonomously to send the report. There are lots of flavours of report, with/without security, with passthrough data, changes to short term operating parameters, etc. and I think that it is really the upper layer that is managing this. Perhaps we want the MAC to remember this piece of upper layer control data. But it should be described as such and not as enabling something in the MAC, unless we are prepared to specify and describe how all the various options are controlled in an autonomous reporting mode.",null,"For autonomous MAC operation, we should hugely reduce the number of MAC options supported by the standard, (messages, methods etc) to make that MAC operation simple to specify and implement, otherwise we will be spending a long time getting the text right,….","Yes",null,null,"MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Tero Kivinen",null,450,"No","Self","Technical",69,"10.38.6",22,"Provide message sequence charts for the report phase, preferably for all different cases. ",null,"Provide message sequence charts.","Yes",null,null,"MMSUWB",null,"ASSIGNED",null,"Carl"]
[null,null,"Pooria Pakrooh",null,1357,"No","Qualcomm","Technical",69,"10.38.6",27,"\"Reporting period\"  not \"slot\", as the report duration could span multiple slots.",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1172,"No","Qorvo","Technical",70,"10.38.?.?",15,"Not sure where it should go, but noting that we have secure format of some messages, maybe we need a clause on the \"high integrity\" use case.",null,"Add appropriate clause, to cover the \"high integrity\" use case and consider what compart frames are used for it and make sure all if these frames can be properly protected from attack by rogues.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1173,"No","Qorvo","Technical",70,"10.38.?.?",15,"Given secured compact frames only covers one aspect of the ranging (the reply times) which may be insufficient to be sure of secured ranging, lets remove all mention of compact frame security. ",null,"Remove the secured compact frames and all changes to clause 9.  And used base line frame format (adding IE if necessary) to have all necessary frames properly covered with security.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,451,"No","Self","Editorial",70,"10.38.6",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1306,"No","NXP Semiconductors","Technical",70,"10.38.6",5,"Shouldn't it be the \"responder's report in the first period\"?",null,"Change \"initiator's report\" to \"responder's report\"","No",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tushar Patel",null,1425,"Yes","LitePoint","Editorial",70,"10.38.6",5,"I don’t fully understand here but reading the line as is I would think  Line #4 to 5 should say \"  \"the initiator shall transmit its report in the second period, regardless of whether it received the responder’s report in the first period.\"",null,"Change Line #5 to \"second period, regardless of whether it received the responder’s report in the first period.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,452,"No","Self","Editorial",70,"10.38.7.2",1,"There is Figure 38 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,453,"No","Self","Editorial",71,"10.38.7.2",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,455,"No","Self","Editorial",71,"10.38.7.3",1,"There is Figure 39 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Bin Tian",null,12,"No","Qualcomm","Technical",71,"10.38.7.3",5,"The details of CCA need to be specified like ED threshold",null,"as in the comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1174,"No","Qorvo","Technical",71,"10.38.7.3",9,"\"as needed during the UWB MMS control phase.\" is wrong on two fronts. It is only appropriate for the NBA case, and, it is only needed (mandated) is certain regulatory domains.",null,"Change to \"as applicable to the control phase of NBA UWB MMS\".","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,454,"No","Self","Editorial",71,"10.38.7.3",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,982,"No","Meta Platforms","Technical",71,"10.38.7.3",12,"How long is the CCA duration? Figure 35 suggests at least 9us, but there is no text that says that.  Please add text that specifies the minimum CCA duration.",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,983,"No","Meta Platforms","Technical",71,"10.38.7.3",12,"In Figure 35, there is at least 100us of idle time between successive transmissions.  There is no normative text that describes this idle time.  Please add corresponding text that accomodates required idle time.",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,984,"No","Meta Platforms","Technical",71,"10.38.7.3",12,"In Figure 35, there is at least 100us of idle time between successive transmissions.  If the ranging slot duration is 300 RSTU (250us), will there be enough time to accommodate this idle time? If there is not enough time, what is expected behavior?",null,"Please clarify behavior","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,985,"No","Meta Platforms","Technical",71,"10.38.7.3",12,"In Figure 35, there is an upper bound of 95% of the ranging slot on the transmission duration.  There is no text associated with this.  Please add such text. ",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Tian",null,13,"No","Qualcomm","Technical",71,"10.38.7.3",13,"Even for channel number below 50, LBT shall be applied for NB OQPSK transmission unless its operation duty cycle is very low. ",null,"as in the comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Stephen Shellhammer",null,94,"No","Qualcomm","Technical",71,"10.38.7.3",13,"NB coexistence with other technologies in UNII-3 and UNII-5 bands needs to be addressed by defining a mandatory channel access mechanism for NB operation in UNII-3/5, with clear guidance for the implementers.\nA good option is the LBT mechanism proposed and evaluated in DCN 15-24-212/r5.",null,"Adopt a mandatory coexistence mechanism for NB operation in UNII-3 and UNII-5 bands. A good proposal is presented and evaluated in DCN 15-24-212/r5. \n\nAdd the following text from DCN 15-24-212/r5 following:\n\"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle.\nFor a NB capable device, if its NB transmission duty cycle is more than 2.5% (exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Bin Qian",null,150,"No","Huawei","Technical",71,"10.38.7.3",13,"NB coexistence in UNII-3 band needs to be addressed",null,"LBT shall be applied to channels 0-49 if NB duty cycle per ranging block >=TBD%","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carlos Aldana",null,977,"No","Meta Platforms","Technical",71,"10.38.7.3",13,"The statement \"LBT shall be applied to channel numbers 50 to 249 according to regulatory constraints.\" should be clarified as the word \"according\" is ambiguous.  After reading the subsequent sentence, I think the author meant \"in the presence of regulatory constraints\".  If that's the case, then regulatory constraints are already mandating LBT and the aforementioned statement does not provides additional information. Replace with \"LBT shall be applied to channel numbers 0 to 249 to improve coexistence with other spectrum users.\" and remove subsequent sentence.",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carlos Aldana",null,978,"No","Meta Platforms","Technical",71,"10.38.7.3",13,"LBT is proven to be a great coexistence technique.  Given that there is no baseline coexistence technique for narrowband, LBT should be made the baseline  Replace the sentence \"LBT may be applied to all channels in the absence of regulatory constraints, for example, to improve coexistence with other spectrum users.\" with \"LBT shall be applied to channel numbers 0 to 249 to improve coexistence with other spectrum users\".",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carlos Aldana",null,979,"No","Meta Platforms","Technical",71,"10.38.7.3",13,"replace \"may\" with \"shall\" and also add the following sentence: \"phyCcaEdThreshold should be set to a value that is inversely proportional to the transmit power, in dB.    For UNII-3, the phyCcaEdThreshold is set to -67 dBm/MHz - Pmax_dBm and for UNII-5 it is set to -74 dBm/MHz - Pmax_dBm.",null,"As in comment","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carlos Aldana",null,988,"No","Meta Platforms","Technical",71,"10.38.7.3",13,"SSBD can be used to specify LBT behavior.  Please add the following text: \"Channel access using listen before talk shall be used for improved coexistence performance.   When used for narrowband assist, SSBD shall use the following control attribute values:\nphyCcaDuration should be set as required by local regulations;\n\nmacSsbdMinBf and macSsbdMaxBf shall be set to 0;\nmacSsbdMaxBackoffs shall be set to 0;\nmacSsbdTxOnEnd shall be set to FALSE;\nmacSsbdPersistence shall be set to FALSE;\nphyCcaMode shall be set to 1 (energy above threshold)\nphyCcaEdThreshold shall be set to -67 dBm/MHz - Ptx for channels 0 to 49 and to -74 dBm/MHz - Ptx for channels 50 to 249, where Ptx is the equipment’s instantaneous transmit power in dBm.\"",null,"As in comment","Yes",null,"doc 15-24-0407-00-04ab-proposed-resolution-for-cid-988.docx","NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1358,"No","Qualcomm","Technical",71,"10.38.7.3",13,"NB coexistence with other technologies in UNII-3 and UNII-5 bands needs to be addressed by defining a mandatory channel access mechanism for NB operation in UNII-3/5, with clear guidance for the implementers.\nA good option is the LBT mechanism proposed and evaluated in DCN 15-24-212/r5.",null,"1. Adopt a mandatory coexistence mechanism for NB operation in UNII-3 and UNII-5 bands. \n\n2. Define specific parameters for NB (such as LBT with ED threshold value, CCA duration, etc.)such that they are clear to the implementers.\n\nA good proposal is presented and evaluated in DCN 15-24-212/r5. \n\nAdd the following text from DCN 15-24-212/r5 following:\n\"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle.\nFor a NB capable device, if its NB transmission duty cycle is more than 2.5% (exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pooria Pakrooh",null,1359,"No","Qualcomm","Technical",71,"10.38.7.3",13,"Sentence is unclear. What does \"according to regulatory constraints\" mean? ",null,"Clarify what is the mandatory requirement here? Specify that mandatory LBT needs to be applied to all channels 0-249.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Pooria"]
[null,null,"Alex Krebs",null,1387,"No","Apple","Technical",71,"10.38.7.3","5 to 15","The specifics of this LBT implementation are taken from ETSI BRAN, and are not valid for other regions outside the EU.",null,"Replace\n\nAfter...users.\n\nby\n\nLBT may be applied to improve coexistence with other spectrum users.\n\nand remove reference B1 on p.223.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"B. Rolfe",null,1321,"Yes","BCA","Technical",71,"10.38.7.3 ",4," The behavior defined in this clause already exists in the standard, though it might not be clear to the reader this is so. Clarify that either of the methods defined in the standard as Random access methods (6.3.2), CSMA-CA and SSBD, can be used to achieve the described behavior.",null,"Change \"then the device shall perform CCA before\" to \"then one of the channel access methods defined in 6.4.3 shall be used, with CCA mode 1 or 3 used, configured to meet the following constraints:\"  ",null,null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1175,"No","Qorvo","Technical",71,"10.38.7.4.1",19,"First sentence seems unnecessary here.",null,"Delete it","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1176,"No","Qorvo","Technical",71,"10.38.7.4.1",22,"The changing of channel is complex and perhaps dependant on the use case, one-to-one, one-many, number of reports being sent/received in the various rounds before the switch, does the MAC (at all nodes) always know when it the start of a new ranging block and time to do the channel switch, or, do we need a primitive for the application to say to MAC that it is starting a new ranging block and to \"do the channel switch now\"",null,"Add a description of how the MAC knows it is time to (autonomously) do the channel switch or add a primitive for the upper layer to tell it to do it.  If a primitive is not needed, then we still should add a MAC PIB attribute to control the enable/disable the (autonomous) MAC channel switch function.  I would recommend for the higher layer to set the allowed channel list and the seed for the switching, and then invoke a primitive to give next channel switch.  To be considered whether the primitive writes this to the phycurrentchannelinfo, or the higher layer does it at the appropriate time.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1177,"No","Qorvo","Technical",71,"10.38.7.4.1",22,"It is not clear whether channel switching is a mandatory part of NBA, i.e., do all NBA devices have to support this, is it enabled/disabled by default, etc.",null,"Add in to this overview text to specify whether channel switch support is mandatory requirement for NBA UWB MMS, (which can be enabled/disabled","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1178,"No","Qorvo","Technical",71,"10.38.7.4.1",25,"This sentence says the channel switching occurs per ranging block. Is this the case that irrespective of how many active ranging rounds, or sub-rounds there are (e.g., there might be quite a few transmissions from initiator in the one-to many cases), that the swich only occurs before the next ranging block,  ",null,"Consider one-to-many and hyper-block cases and clearly specify what switching is appropriate, and especially for any regulatory domains where such hopping is required.  (another reason for higher layer to be in control of this).","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,458,"No","Self","Technical",72,"10.38.7.4.1",16,"Using AES-128 as an PRNG here is overkill. It would be better to use for example the algorithm already defined in the base standard section 10.16.1. ",null,"Reuse the existing channel hopping channel shuffling algorithm, as it has the properties of using each channel exactly once before starting to repeat, and as it is repeating patter it does not require synchronized network as devices can find the network by knowing seed and listening channels. ","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,987,"No","Meta Platforms","Technical",72,"10.38.7.4.2",2,"How does the initiator determine whether a channel is unavailable, unusable, or inefficient?  Is it via passive scanning?  If so, how long is the passive scanning duration? How accurate should this result be?   What energy detect threshold should be used?  All this should be specified to have predictable behavior.",null,"Please clarify all the questions here.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Wenzheng Li",null,188,"Non-Voter","Calterah Semiconductor ","Technical",72,"10.38.7.4.2",4,"\" When all 250 O-QPSK channels are marked as blocked, devices should not \nengage in an MMS ranging session\"\nIf all NB channels are blocked, only NBA UWB MMS session should not be engaged",null,"When all 250 O-QPSK channels are marked as blocked, devices should not engage in an NBA MMS ranging session","No",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1403,"No","Apple","Technical",72,"10.38.7.4.2",4,"The sentence \"When all 250 O-QPSK channels are marked as blocked, devices should not\n5 engage in an MMS ranging session.\" is not a good recommendation, as UWB-only MMS mode could still be used.",null,"Remove the sentence, and add the following sentence instead in line 7 between \"conflicting channels.\" and \"The list\":\n\nWhen all 250 O-QPSK channels are marked as blocked, devices may use the UWB-driven MMS mode to engage in a ranging session.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1404,"No","Apple","Technical",72,"10.38.7.4.2",7,"Updating the allowed channel list for just one ranging round as described in 10.38.9.3.7 is not efficient, since only one channel is used during one ranging round anyways. It's also contradicting lines 25-26 of the channel switching protocol on the same page.",null,"Remove the sentence \"The list...\" in line 7-8, and propose a change to the short-term parameter update protocol (e.g. sending the channel number (one byte) explicitly instead of sending a 2, 5, or 6-byte channel map.)","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Carl Murray",null,871,"No","Qorvo","Technical",72,"10.38.7.4.3",11,"This section purports to describe the channel switching protocol but it does not describe how a change in the macMmsNbChannelAllowList via short term parameters is meant to work as indicated on line 7 \"The list of allowed channels may be updated during an ongoing ranging session using short-term signaling, as described in 10.38.3.7.\" Section 10.38.3.7 doesn't describe this either.",null,"Describe how the channel switching protocol works when there is a change in macMmsNbChannelAllowList via short term parameters","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,457,"No","Self","Technical",72,"10.38.7.4.3",19,"PRNG usually generates sequence of integers, in case of using AES-128 this is not really a case. It generates sequence of blocks which consists of sequence of bits and/or octets. Using term least significant will cause confusing as it would assume that the AES function wound return integer, which it does not. ",null,"Change to leftmost 32 bits, which matches how section 4.4 defines the strings.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Ben"]
[null,null,"Tero Kivinen",null,456,"No","Self","Technical",72,"10.38.7.4.3",21,"The base standard has been using % for modulo, and added text saying \"where a%b indicates a modulo b.\". ",null,"To use MOD here we would need to define it, and it would be best to use same format that is already done in the base standard in sections 10.3.2.3.3 or 10.16.1.","Yes","Revised","use \"mod\", which is extensively used in the base standard","NBF",null,"DONE"]
[null,null,"Tero Kivinen",null,459,"No","Self","Technical",72,"10.38.7.4.3",21,"If the receiving device looses synchronization and does not know the ranging block index, how can it recover from that? ",null,"Explain how to regain synchronization after it is lost.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1179,"No","Qorvo","Editorial",72,"10.38.7.4.3",27,"Three numbered Blank lines",null,"Remove them","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Alex Krebs",null,1388,"No","Apple","Technical",72,"10.38.7.4.3 ",21,"As pointed out similarly for RPA_hash calculation before, modulo operation is not defined for AES-128 block output. We can use similar language here to fix.",null,"\nReplace lines 19-21 by:\n\nThe PrngValue is then\ngiven by bits 0 to 31 of NbaPrng(macMmsPrngSeed, RangingBlockIndex)\n\nAlso change line 24 to:\n\nwhere MOD is the integer modulus operator, and n is the length of macMmsNbChannelAllowList, and input/outputs of NbaPrng are MSB zero-padded unsigned integers.","Yes",null,null,"NBF",null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,1405,"No","Apple","Technical",73,"10.38.8.1",4,"The introduction of \"sub-rounds\" is superfluous.",null,"Use the established definitions of block-based MAC ranging with \"ranging rounds\" instead of \"sub-rounds\", and \"ranging block\" instead of \"ranging round\" for all O2M definitions in this and all following subsections (basic O2M, time-efficient O2M, multiple RSF)","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Alex Krebs",null,1406,"No","Apple","Technical",73,"10.38.8.1",4,"The definition of O2M basic operation is explicit in what Poll what is to be used in round1, but ambigious in what Response and Report frames are to be used. ",null,"Change Figure 40 and the section to explicitly name the compact frames to be used for Reponse and Report frames (I assume the one-to-many frames in 10.38.9.13, 10.38.9.14, and 10.38.9.15 are meant?)","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Wenzheng Li",null,190,"Non-Voter","Calterah Semiconductor ","Technical",73,"10.38.8.1",6,"For the basic one to many ranging One-to-many Poll Compact frame within the first sub-round, is there only one One-to-many Poll Compact frame and one One-to-many Response Compact frame can be exchanged according to the description? ",null,"It is better to follow the same mechanism as which in one to one ranging control phase for all sub-rounds in basic one to many ranging control phase. The number of One-to-many Poll Compact frames and the number of One-to-many Response Compact frames can be configured in the Management MAC Configuration field.","No",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,461,"No","Self","Technical",73,"10.38.8.1",11,"The initiator first sends One-to-many poll, but what is the second POLL it sends? Is that also one-to-many? ",null,"Specify which poll message is used for 2nd responder.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,460,"No","Self","Editorial",73,"10.38.8.1",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,46,"Yes","STMicroelectronics","Technical",73,"10.38.8.1",15,"RpDuration shall be fixed for one-to-many MMS in order to avoid a shift of the subround",null,"add, In One-to-Many MMS Ranging, the RpDuration field shall be keept for the whole ranging round and the number of UWB MMS fragment transmissions of the ranging subrounds shall be adjusted.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,462,"No","Self","Technical",73,"10.38.8.1",15,"Unknown acronym CFO, and SFO. ",null,"Those acronyms are used in few places but are not expanded and are not added to acronyms. Either expand them here or add them to acronyms.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Huan-Bang Li",null,1443,"Yes","NICT","Editorial",73,"10.38.8.1",18,"There are grammar error in the first sentence.",null,"Figure 40 shows an example …","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1180,"No","Qorvo","Technical",73,"10.38.8.1",20,"\"These variations are accomplished using the configuration parameters.\" Is not a technical/true statement.. ",null,"change to \"Initialisation phase and control phase messages allow for these variations to be signalled and coordinated.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Alex Krebs",null,1389,"No","Apple","Technical",73,"10.38.8.1 ",15,"CFO/SFO undefined",null,"Add CFO = carrier frequency, SFO = symbol frequency offset to list of abbreviations.","Yes","Revised","doc 15-24-0446-00-04ab-d01-comment-index-469-and-1389-too.docx","MMS",null,"Ready"]
[null,null,"Alex Krebs",null,1391,"No","Apple","Technical",73,"10.38.8.1 ",20,"One to many ranging does use MessageControl to indicate report directions instead of configuration parameters.",null,"Replace \"These variations...\" with\n\n\"These variations are accomplished via message control signaling as described in 10.38.9.12\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Alex Krebs",null,1390,"No","Apple","Technical",73,"10.38.8.1 ","16,17","Clarify what the meaning of \"reserve\" is. Also this language turns the previously optional report phase into a conditionally mandatory report phase at the end of the ranging round.",null,"Replace lines 16-17 with:\n\nRanging slots for measurement report phases may be allocated at the end of each sub-round for each responder individually, and/or cumulatively grouped for multiple responders at the end of the ranging round.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Wenzheng Li",null,189,"Non-Voter","Calterah Semiconductor ","Technical",73,"10.38.8.2",26,"For the One-to-many Poll Compact frame with a Message Control field value of 0x50, if the two or more responders select the same sub-round and receiving the same one-to-many compact frame in the selected sub-round, how the responder knows it has been chosen by the initiator to proceed to the following ranging phase? There is no field in the One-to-many Poll Compact frame with a Message Control field value of 0x50 to inform the selected responder.",null,"need to clarify the use case of the One-to-many Poll Compact frame with a Message Control field value of 0x50, or this kind of poll compact frame should be deleted.","No",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Bin Qian",null,151,"No","Huawei","Editorial",74,"10.38.8.2",2,"\"skips\" should be \"skip\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1181,"No","Qorvo","Editorial",74,"10.38.8.2",5,"frames should be packets (the UWB fragments are not frames)",null,"change \"frames\" to \"packets/fragments\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Carl Murray",null,872,"No","Qorvo","Technical",74,"10.38.8.2",6,"In the contention base one-to-many the POLL and Response order is reversed in some instances. However many messages require the POLL, RESPONSE order, eg. when exchanging short term parameters.",null,"Describe the behaviour of messaging when the POLL, RESPONSE order is reversed. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,463,"No","Self","Editorial",74,"10.38.8.2",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,464,"No","Self","Editorial",74,"10.38.8.3",1,"There is Figure 43 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Zhongxing Yu",null,198,"Non-Voter","Calterah Semiconductor ","Technical",74,"10.38.8.3",8,"In Chapter 10.38.8.3 Time Efficient one-to-many ranging, it says about time efficient MMS for SS-TWR ranging. But in most scenario ,DS-TWR is more popular than SS-TWR. Time efficient MMS for one-to-many DS-TWR ranging is recommended to be introduced. ",null,"\nhttps://mentor.ieee.org/802.15/dcn/24/15-24-0313-01-04ab-time-efficient-mms-for-one-to-many-ds-twr-ranging.docx","Yes",null,null,"MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Mickael Maman",null,47,"Yes","STMicroelectronics","Technical",74,"10.38.8.3",9,"recall that time efficient one to many ranging is optional ",null,"Support of time efficient one to many ranging is optional.","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,465,"No","Self","Technical",74,"10.38.8.3",9,"Unknown or wrong acronyms. VR is not defined as acronym, and AR is acknowledgment request. ",null,"Expand VR/AR or remove them.","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Wenzheng Li",null,192,"Non-Voter","Calterah Semiconductor ","Technical",74,"10.38.8.3",12,"Since the initial SYNC+SFD fragment shall be exchanged in UWB driven UWB MMS, the type of SYNC+SFD should be introduced in the MMS fragment exchange in the time efficient one to many ranging",null,"The supported number of UWB \nMMS fragments (i.e., RSF and/or RIF or SYNC+SFD) per ranging sub-round is limited to two fragments","Yes",null,"Doc 15-24-0403-01-04ab-proposed-resolution-for-uwb-driven-mms-and-oob-assisted-mms.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Pablo Corbalán Pelegrín",null,1307,"No","NXP Semiconductors","Editorial",74,"10.38.8.3",18,"Missing \"be\" --- shall be set to zero and one",null,"shall be set to zero and one","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1308,"No","NXP Semiconductors","Editorial",74,"10.38.8.3",21,"Missing \"be\" --- shall be set to zero",null,"shall be set to zero","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Wenzheng Li",null,191,"Non-Voter","Calterah Semiconductor ","Technical",74,"10.38.8.3",23,"For the time efficient one to many ranging, according to Figure 42 and description, only one One-to-many Poll Compact frame and one respective One-to-many Response Compact frame from each responders are exchanged in the control phase of each ranging sub-round. Two issues need to be clarified: 1. Is the One-to-many Poll Compact frame exchanged in the sub-round other than the first sub-round; 2. Can One-to-many Poll Compact frame and One-to-many Response Compact frame be exchanged multiple times as configured by Management MAC Configuration field in each sub-round.",null,"It is better to follow the same mechanism as which in one to one ranging control phase for all sub-rounds in basic one to many ranging control phase. The number of One-to-many Poll Compact frames and the number of One-to-many Response Compact frames can be configured in the Management MAC Configuration field.","No",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1182,"No","Qorvo","Technical",74,"10.38.8.3",30,"Lines 30 through to 14 on next page, are reiterating the PHY packet format in words, this should be clear from clause 16 and should not be repeated here, really it is just saying that the initiator sends at offset 0, and first and second responders send interleaved at offsets 400 and 800 RSTU.",null,"Simplify the wording: Replace lines 30 through to 14 on next page with: \"The UWB MMS packet format shall be as specified in clause 16.2.11 with fragments from responder one and responder two offset from the initiator's fragments by 400 and 800 RSTU respectively.\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1183,"No","Qorvo","Technical",74,"10.38.8.3",30.1,"There are three separate sentences here trying to define the activity of the initiator for  three different cases of RSF/RIF packet formats.  Might be clearer to start with the \"if packet format is XXX, the initiator…\" also may is too weak. A \"shall\" would be better, and a complete rewrite would be even better.\n[THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, if that change is done this change is unnecessary]",null,"[THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, if that change is done this change is unnecessary]. Replace the paragraph with: \"If phyUwbMmsRsfNumberFrags is zero, the initiator shall, send its first RIF fragment at the start of the ranging phase and each subsequent RIF at regular intervals of 1200 RSTUs. Otherwise, the initiator shall, send its first RSF fragment at the start of the ranging phase and each subsequent RSF at regular intervals of 1200 RSTUs; and thereafter, if phyUwbMmsRifNumberFrags is non-zero, the initiator shall send its first RIF fragment 2400 RSTUs after the start of the last RSF fragment, and subsequent RIF fragments at intervals of 1200 RSTUs.\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Bin Qian",null,152,"No","Huawei","Technical",74,"10.38.8.3",31,"Since the supported number of UWB MMS fragment per ranging sub-round is limited to two, the subsequent RSF fragments only include one fragment",null,"Change \"subsequent RSF fragments\" to \"the second RSF fragment\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1184,"No","Qorvo","Technical",74,"10.38.8.3",33,"\"and continue to send the second RIF fragment at a regular interval\"",null,"[THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, if that change is done this change is unnecessary]. change to \"and continue to send the subsequent RIF fragments at a regular intervals\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1185,"No","Qorvo","Technical",74,"10.38.8.3",33,"\"and continue to send the second RIF fragment at a regular interval of 1200 RSTU\" doesn't make sense.",null,"[THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, if that change is done this change is unnecessary]. Change to \"and continue to send subsequent RIF fragments at a regular intervals of 1200 RSTU\", unless the change proposed from my comment on line 30 is accepted in which case no additional change is needed.","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1186,"No","Qorvo","Technical",74,"10.38.8.3",35,"This case of mixed RSF/RIF packets is poorly constructed and does not mention subsequent RIF.  It should be rewritten but,",null,"[THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, if that change is done this change is unnecessary]. Rewrite the sentence to properly describe this case.","No",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1187,"No","Qorvo","Technical",75,"10.38.8.3",1,"This paragraph is a copy of that on p74 lines 30-36, and my same comments apply, would recommend similar rewrite as per my comment on p74 L#30, but maybe a simpler approach could be taken.  [THIS COMMENT IS SUPERCEDED BY MY COMMENT ON P74 L30, However the idea to use a table for the offsets as per the proposed change here is worth incorporating .",null,"Replace paragraph and subsequent one with: \"The responders  transmit their fragments in the same manner as the initiator except they are offset from the start of the ranging phase by the time specified in Table X, based on the Time Shift Indication field value from the One-to-many Poll Compact frame with (Message Control = 0x90).\"; and, add Table X in clause 10.38.9.12 with the offsets for the Time Shift Indication field values, instead of the paragraph style text that defines the offsets.","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Pablo Corbalán Pelegrín",null,1309,"No","NXP Semiconductors","Technical",75,"10.38.8.3",2,"Is 400 RSTU the only allowed time offset value to schedule the RSF fragments from the two responder? Can this be also configurable? If the slot timing is > 1200 RSTUs, e.g., 2400 RSTU, then we may set this to 800 RSTU, is that correct?",null,"Clarify whether 400 us is an example and whether this value can be configured.","No",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Carl Murray",null,873,"No","Qorvo","Technical",75,"10.38.8.3",8,"The text \"The responder with Time Shift Indication field set to zero may start transmitting the first RSF fragment ...\" is a repeat of line 1 suggesting that one of them is wrong",null,"Change \"zero\" to \"one\"","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1188,"No","Qorvo","Technical",75,"10.38.8.3",8,"This paragraph is a copy of that on p74 lines 30-36, and my same comments apply, would recommend similar rewrite as per my comment on p74 L#30, but my proposed change for  p75 L#1 is a good fix for those issues.",null,"Apply the change I proposed for p75 line 1 ","Yes",null,"Doc 15-24-0445-00-04ab-draft-1-0-time-efficient-o2m-ranging-related-comments-resolution.docx","MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,466,"No","Self","Editorial",75,"10.38.8.3",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1189,"No","Qorvo","Technical",75,"10.38.8.3",22,"This is the first mention of the Secure Report Compact frame!  Does it not apply in the other cases of basic one-to-many, or even the one-to-one cases.  I think we need a separate section to cover the secure case(s)",null,"Remove security mention from here and have a separate section where the \"high integrity\" use case are added on top of all the other use cases, by using secured versions of the appropriate frames","Yes",null,null,"MMS",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,467,"No","Self","Editorial",76,"10.38.8.3",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1190,"No","Qorvo","Technical",76,"10.38.8.4",5,"This whole section is a bit problematic, and Ì believe it is not a useful mode, would prefer to delete it than try to fix it.",null,"Delete this clause.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1191,"No","Qorvo","Technical",76,"10.38.8.4",5,"If we want to keep this, I note initiators need multiple receivers operating in parallel while the responders are normal devices with one RX and one TX. I think this best way to incorporate this is to consider it achievable by having two radio receivers independent PHY and MAC in one unit that are controlled by the next higher layer to do the double overlapping reception of the overlapping transmissions.  As such we should move this to an annex and describe hope it can be achieved in a two radio device/",null,"Move this clause to an annex written to explain how a device with two (or more) radio receivers may be operated to receive such overlapping transmissions. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Mickael Maman",null,48,"Yes","STMicroelectronics","Technical",76,"10.38.8.4.2",9,"One-to-many ranging with multiple RSF transmissions per slot looks limited to only one RSF fragment per responder. Clarification is needed ",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,469,"No","Self","Technical",76,"10.38.8.4.2",12,"Unknown acronym CFO. ",null,"Either expand CFO or add it to acronyms.","Yes","Revised","doc 15-24-0446-00-04ab-d01-comment-index-469-and-1389-too.docx","MMS",null,"Ready"]
[null,null,"Carl Murray",null,874,"No","Qorvo","Editorial",76,"10.38.8.4.2",12,"typo",null,"change \"low enough cross correlations each other,\" to \"low enough cross correlations with each other,\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,468,"No","Self","Editorial",76,"10.38.8.4.2",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,875,"No","Qorvo","Technical",76,"10.38.8.4.2",18,"It is not clear what is meant by this text \"In the ranging phase, RSF transmissions are scheduled to have the RSF transmission timing of each responder.\"",null,"Make the intent of the text clearer.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,153,"No","Huawei","Technical",76,"10.38.8.4.2",19,"It is not clear which Poll compact frame is sent by the initiator in the control phase",null,"Specify the Poll compact frame and the Message Control field value used in the control phase","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,943,"Yes","SAMSUNG Elec.","Technical",76,"10.38.8.4.2",19,"There's no \"Poll Compact frame\" defined in current specification. The term should be exact.",null,"Change\n\nFrom\n\"In the control phase, the initiator sends a poll Compact frame to trigger RSF transmission in the ranging phase.\" \nTo \n\"In the control phase, the initiator sends either a One-to-Many poll Compact frame to schedule RSF transmission in the ranging phase or a data frame carrying Scheduling IE\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,154,"No","Huawei","Technical",76,"10.38.8.4.2",22,"It is not clear how to set the Message Control field value of the Ranging Report Compact frame",null,"Specify the Message Control field value used in the Ranging Report Compact frame","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,944,"Yes","SAMSUNG Elec.","Technical",76,"10.38.8.4.2",22,"Ranging report can be delivered both way \n\"from initiator to responder\" as well as\n\"from responder to initiator\". \nBut current texts just mentions about one way only.",null,"Change \nFrom\n\"The measurement report phase delivers ranging results from the responders to the initiator.\" \nTo \n\"The measurement report phase delivers ranging results from the responders to the initiator and/or from the initiator to the responders.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,945,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.3",1,"Figure 45 is just one of example operation rather than a soley mandated flow. So it should be distinguished as just an example.\n",null,"Change\n\nFrom \n\"The operation of multiple RSF transmissions in a slot without NB assis t is presented in Figure 45.\" \nTo \n\"The example operation of multiple RSF transmissions in a slot without NB assist is presented in Figure 45.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1192,"No","Qorvo","Technical",77,"10.38.8.4.3",1,"There is nothing to be gained by this technique, with two overlapping responders TX compared with the sequential responders of Figure 42, and it is potentially compromising the performance by having responses on top of each other.",null,"This is not necessary.  Deleting this it would my preferred approach, but otherwise move it into an annex as a description how a device with two (or more) radio receivers may be operated to receive such overlapping transmissions. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Wenzheng Li",null,193,"Non-Voter","Calterah Semiconductor ","Technical",77,"10.38.8.4.3",3,"For the Multiple RSF transmissions in a slot without NB assist, according to Figure 45 and description, only one One-to-many Poll Compact frame or a frame that carries the Scheduling IE from initiator and one respective One-to-many Response Compact frame  or a frame that carries the MMRC IE from each responder are exchanged in the control phase. Can multiple One-to-many Poll Compact frame  or a frame that carries the Scheduling IE and One-to-many Response Compact frame or a frame that carries the MMRC IE be exchanged as configured by Management MAC Configuration field in control phase?",null,"It is better to follow the same mechanism as which in control phase. The number of One-to-many Poll Compact frame or frame that carries the Scheduling IE from initiator and the number of One-to-many Response Compact frame or a frame that carries the MMRC IE from each responder can be configured in the Management MAC Configuration field.","No",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,948,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.3",4,"Only Initiator operation is described. There's no responder operation description. Need to specify responder operation.",null,"Change \n\nFrom\n\"The control phase uses the UWB channel and starts with the transmission by the initiator of either a One-to many Poll Compact Frame or a frame that carries the Scheduling IE (10.32.9.10).\" \nTo \n\"The control phase uses the UWB channel and starts with the transmission by the initiator of either a One-to many Poll Compact Frame or a frame that carries the Scheduling IE (10.32.9.10) to the responders. Based on the control phase, the transmissions of responders may be scheduled.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Mickael Maman",null,49,"Yes","STMicroelectronics","Technical",77,"10.38.8.4.3",12,"the initiator sends a SYNC+SFD in slot 3. Where are the SYNC+SFD of responders according to UWB driven MMS?",null,"need clarification","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,155,"No","Huawei","Technical",77,"10.38.8.4.3",12,"In UWB driven case, SYNC+SFD is the first fragment. It is not consist with the UWB driven MMS packet format if the responders reply with RSF aftering receiving SYNC+SFD",null,"The responders could reply SYNC + SFD after receiving SYNC + SFD from the initiator","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,156,"No","Huawei","Technical",77,"10.38.8.4.3",12,"The time interval between the reception and transmission of the responder is set to be AIFS, which is too limited",null,"Delete the AIFS constrain","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Wenzheng Li",null,194,"Non-Voter","Calterah Semiconductor ","Technical",77,"10.38.8.4.3",12,"\"If responder receives the SYNC+SFD fragment of the initiator, after AIFS the responders reply with RSF as allocated by the scheduling IE in the control phase. \" Since the initial SYNC+SFD fragment shall be exchanged in UWB driven UWB MMS, the type of SYNC+SFD should be introduced in the MMS fragment exchange in the time efficient one to many ranging",null,"If responder receives the SYNC+SFD fragment of the initiator, after AIFS the responders reply with MMS fragments (i.e., RSF and/or RIF or SYNC+SFD) as allocated by the scheduling IE in the control phase.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1193,"No","Qorvo","Technical",77,"10.38.8.4.3",12,"It is not good to use AIFS here since this is not an ACK.  Such reuse makes the standard maintenance harder. Suggest to define a special constant for this or insert the constant number value into the text as is done elsewhere for MMS responder timing, indeed better to specify the timing in the same way as for the other cases.",null,"Align with other MMS text and use appropriate offset for this case, (Do not use AIFS for this time).","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1194,"No","Qorvo","Technical",77,"10.38.8.4.3",12,"Figure 45 does not match the text and the text is not aligned with the PHY specified format of UWB driven MMS packet. Each device needs to send the SYNC-SFD fragment in first millisecond, and RSF fragments in the next millisecond. Really the default mode here should match the mandatory mode as per Table 24, so it should be RIF in the next millisecond.  ",null,"Since this text is broken, the easiest fix is to delete the clause.  Failing that in needs to support the default UWB driven format, and include SYNC+SFD from each responder, for the receivers to synchronise on.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,946,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.3",13,"Generally, the procedure comprise of three phases ; control, ranging and report phase. However, explanation corresponding to the Measurement Report Phase is missing here. So the report phase briefly is described.",null,"Add below texts at the end of the paragraph ; \n\n\"In the measurement report phase, the initiator and/or the responders send measurement report by One-to-Many initiator report and/or One-to-Many responder report compact frame or Ranging Measurement Information IE (RMI IE) in the UWB channel.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,949,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.3",13,"Not enough responder operation description..",null,"Change \n\nFrom\n\"If responder receives the SYNC+SFD fragment of the initiator, after AIFS the responders reply with RSF as allocated by the scheduling IE in the control phase.\" \nTo \n\"If responder receives the SYNC+SFD fragment of the initiator, after AIFS the responders reply with RSF as allocated by the scheduling IE in the control phase, when SYNC+SFD fragment is sent at the allocated slot which was scheduled in Control Phase.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,470,"No","Self","Editorial",77,"10.38.8.4.3",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Wenzheng Li",null,195,"Non-Voter","Calterah Semiconductor ","Technical",77,"10.38.8.4.3",18,"For the Multiple RSF transmissions in a slot with NB assist, according to Figure 46 and description, only one One-to-many Poll Compact frame and one respective One-to-many Response Compact frame from each responder are exchanged in the control phase. Can multiple One-to-many Poll Compact frame and One-to-many Response Compact frame be exchanged as configured by Management MAC Configuration field in control phase?",null,"It is better to follow the same mechanism as which in control phase. The number of One-to-many Poll Compact frame from initiator and the number of One-to-many Response Compact frame  from each responder can be configured in the Management MAC Configuration field.","No",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,950,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.4",18,"Lack of responder operation. \nClarify the operation of responders",null,"Change \n\nFrom\n\"The control phase is conducted by sending a One-to-many Poll Compact frame in the NB channel.\"  \nTo \n\"The control phase is conducted by sending a One-to-many Poll Compact frame in the NB channel to responders. Based on the control phase, the transmissions of responders may be scheduled.\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Mickael Maman",null,50,"Yes","STMicroelectronics","Technical",77,"10.38.8.4.4",19,"why in multiple RSF transmissions in a slot with NB assist, the initiator sends a SYNC+SFD? The initiator can directly send its RSF",null,"remove reference to SYNC+SFD in lines 19 to 23","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,157,"No","Huawei","Technical",77,"10.38.8.4.4",19,"If there exists NB, the MMS packet format does not include SYNC + SFD",null,"The RSF is transmitted directly instead of transmitting SYNC + SFD fragment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Carl Murray",null,876,"No","Qorvo","Technical",77,"10.38.8.4.4",21,"Starting on this line the description for NB assist includes transmitting a fragment with SYNC+SFD. NB assist does not support fragments with SYNC+SFD.",null,"Update text to remove references to SYNC+SFD fragments","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,951,"Yes","SAMSUNG Elec.","Technical",77,"10.38.8.4.4",21,"Clarify the control phase in example operation",null,"Change ;\nFrom\n\"Example operation of the multiple RSF transmissions per slot with NB assist is shown in Figure 46.\"\nTo\n\"Example operation of the multiple RSF transmissions per slot with NB assist is shown in Figure 46. The control phase uses the NB channel and starts with the transmission by the initiator of a One-to many Poll Compact Frame. This frame may include slot scheduling information and RSF allocation for the responders, (i.e., ranging slot 0 in Figure 46).\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Youngwan So",null,947,"Yes","SAMSUNG Elec.","Technical",77,"10.83.8.4.4",19,"To trigger the multiple RSF transmissions, SYNC+SFD fragment is used rather than MMS packet. So it should be corrected.",null,"Change \n\nFrom\n\"After control phase, the UWB MMS packet including the initial SYNC+SFD fragment, as per Figure 198, is transmitted to trigger multiple RSF transmissions.\" \nTo\n\"After control phase, the UWB packet including the initial SYNC+SFD fragment, as per Figure 198, is transmitted to trigger multiple RSF transmissions.\"\n","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1195,"No","Qorvo","Technical",78,"10.38.8",3,"I have an earlier comment (against clause 10.38.2) saying that 4ab should state UWB/NB/TX/RX are mutually exclusive.  Generally each PHY has a turnaround time specification, TX-to-RX and RX-to-TX. Now in MMS we have to switch from UWB to NB and NB to UWB in various combinations of TX to TX, TX to RX, RX to RX, and RX to TX.  The standard should specify minimum times for these as a worse case target for implementers. The times need to take into account the MAC operations necessary to decode any received frame, and configure / enable the device for next TX/RX operation.",null,"Insert a new subclause (possibly between 10.38.7 and 10.38.8) to define these times and specify these inter-radio-interframe spacing and TX/RX turnaround times that apply between NB and UWB activity. And we should be including allowance for these turnaround times in the appropriate slot time specifications. ","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Mickael Maman",null,51,"Yes","STMicroelectronics","Technical",78,"10.38.8.4.4",1,"What is Poll frame form initiator in uwb rangng slot 3?",null,"change to SYNC+SFD or rsf?","Yes",null,null,"MMS",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,471,"No","Self","Editorial",78,"10.38.8.4.4",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,472,"No","Self","Technical",78,"10.38.9.1",8,"The compact frame id field is not enough to describe the content, as the message control field changes the most of the fields inside the message content field. ",null,"Combine Compact Frame Id and Message Control fields, move that new 8-bit field as 2nd octet, and use the 5-bits in the first octet to include version number, and security support, so every frame can be secured.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,473,"No","Self","Technical",78,"10.38.9.1",10,"Having frames which have either FCS or MIC makes it impossible to easily reject frames with bit errors on the hardware. ",null,"Include FCS on all frames including those frames which have MIC.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1392,"No","Apple","Technical",78,"10.38.9.2.1",17,"This scheme does not protect the responder devices against active polling privacy attacks. ",null,"Add an optional extension that assures non-replayable addresses when required by the responders.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,474,"No","Self","Technical",78,"10.38.9.2.1",18,"The current defined address generation method allows easy passive monitoring and tracking of all users, and trivial active tests that will allow attackers to keep track of specific users. ",null,"Remove the currently defined completely broken private addressing scheme, and use the private addressing scheme defined in the 802.15.4ac.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,475,"No","Self","Technical",78,"10.38.9.2.1",20,"When the output of the prand is only 24-bits it is complete overkill to use CSPRNG for generating that. The security level of the CSPRNG is 128-bits but the security of the addressing scheme is 24 bits, so any kind of random number generator is acceptable for such low security levels. ",null,"Remove requirement for the CSPRNG as that is not needed when the security level of the addresses are so low. Using CSPRNG will just generate false sense of security.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1197,"No","Qorvo","Technical",78,"10.38.9.2.1 ",21,"\"RPA_prand\" with underscore is a format not typically used in the base standard to describe something.  Also this particular sentence (being first mention of the term) is a good place to introduce it, but it should be defined in clause 3.1 too. ",null,"Change: \"The initiator shall communicate a 3-octet output RPA_prand of the CSPRNG in the...\"  to  \"The initiator shall use the CSPRNG to generate a 3-octet random bit sequence, herein termed the 'RPA prand', which it shall communicate in the…\" ; and, change all occurrences of \"RPA_prand\" to \"RPA prand\" ; and, add a definition of \"RPA prand\" into clause 2.1: \"a random number used in the resolvable private address scheme (for Compact frames)\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1196,"No","Qorvo","Technical",78,"10.38.91",10,"For ease of MAC layering implementation it would make sense for lower layer MAC to always of an FCS check and discard frames with bad FCS, i.e. require a good FCS before parsing the frame to do security processing if the frame needs is.  ",null,"Change Compact frame format to always have the CRC field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,476,"No","Self","Technical",79,"10.38.9.2.1",18,"If devices carry multiple IRKs that will make address resolution even more expensive. The devices are already required to loop through all IRKs they have trying to find a match, and if there are multiple IRKs per device this will multiply this effect. ",null,"Add note, that multiplying number of IRKs will also exponentially multiply number of time required for resolving every single incoming frame.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1198,"No","Qorvo","Technical",79,"10.38.9.2.1 ",11,"This is talking about resolving RPA, and discarding frames.  This needs to be part of the general receive frame processing. ",null,"Add text about compact frame address filtering / receive frame processing into a revised (reviewed) subclause 6.2.2 Reception and rejection, including editorial marks to apply the necessary changes so that MAC can work with Compact Frames and other frames pre-existing and newly added by 4ab.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1199,"No","Qorvo","Technical",79,"10.38.9.2.1 ",12,"This is talking about using multiple IRK to resolve the hash (using AES) which implies a certain computational load.  This load will increase depending on the number of IRK searched. This might be done in software and take an appreciable amount of time.  The standard should specify the number of IRK that a compliant device needs to support, and specify the response time that a device needs to comply with, (which must assume the RPA resolution is on the final IRK in the list to be tested).",null,"Specify minimum number of IRK, and specify response time (RX to TX) to take account of processing involved to validate a hash, and well and any other processing needs.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1200,"No","Qorvo","Technical",79,"10.38.9.2.1 ",15,"This talking about the RPA being marked as unresolved (and discarding the packet), but maybe it is the frame's hash that is not resolved, and the frame that is marked? Clause 10.38.9.2.3 is talking about the frame being marked as resolved, which is probably the same thing but not clearly so.  It would be better for the receive processing steps to be laid out in clause 6.6.2 (which has to be updated anyway) since clause 6.6.2 is where it talks about what is checked, and discarding the frame etc.  When the text is in clause 6, it should not be repeated here (since double specification can be a source of error) so some of the text here should be removed.  ",null,"Merge the step by step flow of compact frame receive processing into clause 6.6.2, showing the changes to that clause that allow both normal and compact frame reception to operate correctly together as they should.  When that is done the processing steps should not be repeated here and can largely be deleted. The split I envisage for example would be to have Clause 6 describe how the hash is checked against various IRK as specified in 10.38.9.x.x to yield an RPA match or if this fails that the frame discarded. And, have the clause 10 text detail what are the IRKs and give the process steps for of finding a match for the hash).","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,479,"No","Self","Technical",79,"10.38.9.2.2",21,"This public address scheme is much more private than the private address scheme described earlier. This method of addressing provides quite good privacy properties, provided that devices change their public addresses often enough. Only downside is that even the devices participating with the ranging cannot keep track of the devices they are doing ranging with. ",null,"Rename this to private address method, and remove currently defined broken private addresses method. Define method here to do what 802.15.4ac plans to do i.e. to add method of initiator and responder to send secure token that will tell other end who has the key who the other end is. Or simply shorten the 3-octet addresses to 2-octets, use them as short addresses, and reuse what 802.15.4ac defines.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,477,"No","Self","Technical",79,"10.38.9.2.2",27,"The text on lines 27-32 is mostly redundant. Those frames already tell what addresses they are using, so repeating it here is not needed. ",null,"Remove lines 27-32 and replace it will text saying that Public Advertising Poll Compact frame (10.38.9.16), Public Advertising Response Compact frame (10.38.9.17), Public Start of Ranging Compact frame (10.38.9.18), and Public Advertising Confirmation Compact (10.38.9.19) frames use public addresses.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,478,"No","Self","Technical",79,"10.38.9.2.2",33,"There is no need to repeat the which frames keep the same address, this text should say that same public address shall be used during the duration of the ranging session. ",null,"Replace lines 33-35 with text that says that \"During the ranging session devices shall use the same public address\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Billy Verso",null,1201,"No","Qorvo","Technical",80,"10.38.9.2.3",5,"Are all outgoing secure compact frames going to responders, maybe sometimes they are sent to \"initiators\" or just to other devices with different roles.  Better to  use the term \"destination\" than responder.",null,"Make this paragraph more generic, use the terms \"source\" and \"destination\" rather than \"initiator\" and \"responder\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1202,"No","Qorvo","Technical",80,"10.38.9.2.3",9,"The term \"marked as resolved\" is not explained and does not appear in the referenced clause 10.38.9.2.1, although this clause is talking about RPA being resolved, and it does talk about the RPA being marked as unresolved.",null,"Use the same terms for the same thing, better still if clause 6 is filtering and discarding, then instead of \"marked as resolved\" instead say \"passes the first level frame filtering of 6.6.2\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1203,"No","Qorvo","Technical",80,"10.38.9.2.3",12,"This says that the mapping of the extended address to the IRK is not defined in this standard, but I think it has to be, or at least the PIB should include a structure with IRK and associated RPA and extended addresses, (it can be left to the upper layer to populate this but it needs to exist).  Can these be added to the secCompactFrameKeyDescriptor or is a separate structure needed?",null,"Add to secCompactFrameKeyDescriptor or create an appropriate descriptor to link IRK, RPA, extended address, and whatever security key information the MAC needs populated in order secure Compact frames in TX and process them appropriately in RX.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Shang-Te Yang",null,925,"Yes","Apple","Editorial",80,"10.38.9.3",15,"It's not clear if these common message fields are meant for all MAC formats or only compact frame.",null,"Change the title to \"Common message fields for compact frame\"","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1204,"No","Qorvo","Technical",80,"10.38.9.3",15,"I am not a big fan of defining fields separately to the messages, but I can see how it is used/useful in some cases here.  Some suggestions for improvement. (Really editorial but marking technical so the TG has oversight before technical editor just does it.)",null,"(A) If individual field clause is not explicitly referenced then rather than a separate numbered clause it could be defined by a paragraph in the overview.\n(B) if the description is short 1 to 2 lines, then include it in the message format definitions rather than the clause reference.\n(C) if the field is only used in one message or one message type the move its description to the message definition clause to avoid jumping to a cross referenced field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,480,"No","Self","Technical",80,"10.38.9.3.2",21,"The message control field and compact frame id fields should be combined, there is only less than 60 of valid combinations, so having one octet combining both would still leave few bits in that octet for other uses, and then the bits in the first octet of the compact frames could include other bits, for example security enabled, and version bits. ",null,"Combine message control field and compact frame id fields to one octet.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Bin Qian",null,158,"No","Huawei","Editorial",80,"10.38.9.3.2",22,"An \"of\" is missing after \"interpretation\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,481,"No","Self","Technical",80,"10.38.9.3.5",30,"If the compact frame id and message control fields are combined, then this structure comes much simplier, simply list of supported values. ",null,"Change to be list of supported combined compact id + message control field values.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,482,"No","Self","Editorial",81,"10.38.9.3.5",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1310,"No","NXP Semiconductors","Editorial",81,"10.38.9.3.5",2,"Remove \"from\"",null,"vaues in Table 1. ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,483,"No","Self","Editorial",81,"10.38.9.3.6",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1205,"No","Qorvo","Technical",81,"10.38.9.3.6",11,"For consistency with the way the Msdu parameter is described, change \"string of octets\" to \"set of octets\".",null,"Change \"string of octets\" to \"set of octets\".","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Bin Qian",null,159,"No","Huawei","Technical",81,"10.38.9.3.6",13,"The last sentence is not completed. The field information is missing",null,"It seems that the length of the octet string is indicated by the PT Data Length field value. If so, it is duplicated with Line 10 and it is suggested to remove the last sentence","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,485,"No","Self","Editorial",81,"10.38.9.3.7",14,"Extra period at the end of header. ",null,"Remove period at the end of header.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,490,"No","Self","Editorial",81,"10.38.9.3.7",15,"Spell out small numbers. ",null,"Change \"6-octet\" to \"six octet'.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,484,"No","Self","Editorial",81,"10.38.9.3.7",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,998,"No","Meta Platforms","Technical",81,"10.38.9.3.7",18,"To simplify design, there should be a way to signal the end of the NB channel map.   Please add a field to Figure 49 to signal NB channel end.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,489,"No","Self","Technical",81,"10.38.9.3.7",20,"The intersection operator is not defined anywhere in this standard of base standard. ",null,"Add text describing what the intersection operation does.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,486,"No","Self","Editorial",81,"10.38.9.3.7",21,"Variables should be in italics even when they are not in equations. ",null,"Change NbChannelBitmaskSet and NbChannelAffineSet to italics through the document.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,487,"No","Self","Technical",81,"10.38.9.3.7",21,"The NbChannelAffineSet is not obtained from the bits 42 to 46, it is constructed from those bits. ",null,"Change \"NbChannelAffineSet is obtained\" to \"NbChannelAffineSet is constructed\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,488,"No","Self","Technical",81,"10.38.9.3.7",21,"The nbChannelBitmaskSet is not obtained from the bits 0 to 41, it is constructed from there by returning list of integers in such way that for each bit from 0 to 41 it returns the bit number which are set. ",null,"Properly define the generation of the NbChannelBitMaskSet.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,492,"No","Self","Editorial",82,"10.38.9.3.7",1,"Small numbers needs to be spelled out. ",null,"Change \"set to 1\" to \"set to one\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1206,"No","Qorvo","Technical",82,"10.38.9.3.7",1,"Using bit numbers to talk about the sub fields e.g. \"Bits 0 to bit 3 set to 1....\" is not matching the normal style for fields in the rest of the standard.  The bit numbers should be just specified in the figure and then field names should be used to describe what the sub-fields signify.",null,"Rework the text accordingly.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Huan-Bang Li",null,1444,"Yes","NICT","Editorial",82,"10.38.9.3.7",1,"insert 'when' before 'set to 1 ...'",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,493,"No","Self","Editorial",82,"10.38.9.3.7",6,"Small numbers needs to be spelled out. ",null,"Change \"set to 1\" to \"set to one\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,494,"No","Self","Editorial",82,"10.38.9.3.7",6,"Small numbers needs to be spelled out. ",null,"Change \"6 NB channels\" to \"six NB channels\". This section includes quite a lot of other small numbers that needs to be spelled out.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,495,"No","Self","Editorial",82,"10.38.9.3.7",13,"The NB_channel_start is not using consistent style. Variables should be named without underscores and they should use italics. ",null,"Change NB_channel_start to NbChannelStart with italics throughout the document","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,496,"No","Self","Editorial",82,"10.38.9.3.7",14,"The NB_channel_step is not using consistent style. Variables should be named without underscores and they should use italics. ",null,"Change NB_channel_step to NbChannelStep with italics throughout the document","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,491,"No","Self","Editorial",82,"10.38.9.3.8",22,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,497,"No","Self","Technical",82,"10.38.9.3.8",25,"The nbChannelBitmaskSet is not obtained from the bits 0 to 9, it is constructed from there by returning list of integers in such way that for each bit from 0 to 9 it returns a channel number. ",null,"Properly define the generation of the NbChannelBitMaskSet.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,498,"No","Self","Technical",82,"10.38.9.3.8",25,"The NbChannelAffineSet is not obtained from the bits 10 to 14, it is constructed from those bits. ",null,"Change \"NbChannelAffineSet is obtained\" to \"NbChannelAffineSet is constructed\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,160,"No","Huawei","Editorial",82,"10.38.9.3.8",27,"There is an extra comma",null,"Remove one comma","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,499,"No","Self","Technical",82,"10.38.9.3.8",27,"This repeats same procedure which was already described in the 10.38.9.3.7. If the pieces of the NB Channel Map would be split in different parts ((macMmsNbChannelsLow, macMmsNbChannelsUnii3, macMmsNbChanneslHigh, macMmsNbChannelsUnii5) then the mapping from those mac variables to list of channels could be defined once, and NB Channel Map field, NB Lower Channel Map and NB Higher Channel Map structures could be defined by just concatenation of those mac fields. The constructions of the allow list from those separate mac PIB entries could be done once in 10.38.7.4.2. ",null,"Split macMmsNbChannelMap to separate PIB entries, describe construction of allow list once, and define these NB {,Lower,Higher} Channel Map structures to be just concatenation of those pib entries.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Huan-Bang Li",null,1445,"Yes","NICT","Editorial",82,"10.38.9.3.8",27,"redundent comma",null,"delete one comma","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1207,"No","Qorvo","Technical",82,"10.38.9.3.9",22,"Using bit numbers to talk about the sub fields e.g. \"Bits 32 to 34 encode....\" is not matching the normal style for fields in the rest of the standard.  The bit numbers should be just specified in the figure and then field names should be used to describe what the sub-fields signify.",null,"Rework the text accordingly.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1208,"No","Qorvo","Technical",83,"10.38.9.3.8",3,"Using bit numbers to talk about the sub fields e.g. \"Bits 10 to 12 encode....\" is not matching the normal style for fields in the rest of the standard.  The bit numbers should be just specified in the figure and then field names should be used to describe what the sub-fields signify.",null,"Rework the text accordingly.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,52,"Yes","STMicroelectronics","Technical",83,"10.38.9.3.8",6,"the upper limit of y is 49 for NB lower channel map",null,"change 0<=y<=49","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Li-Hsiang Sun",null,238,"No","MediaTek","Technical",83,"10.38.9.3.8",6,"0<=y<=249, should be 0<=y<=49 ",null,"as in comment","No","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,500,"No","Self","Editorial",83,"10.38.9.3.9",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,501,"No","Self","Technical",83,"10.38.9.3.9",15,"The nbChannelBitmaskSet is not obtained from the bits 0 to 31, it is constructed from there by returning list of integers in such way that for each bit from 0 to 31 it returns the bit number which are set. ",null,"Properly define the generation of the NbChannelBitMaskSet.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,502,"No","Self","Technical",83,"10.38.9.3.9",15,"The NbChannelAffineSet is not obtained from the bits 32 to 36, it is constructed from those bits. ",null,"Change \"NbChannelAffineSet is obtained\" to \"NbChannelAffineSet is constructed\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,239,"No","MediaTek","Technical",83,"10.38.9.3.9",25,"0<=y<=249, should be 50<=y<=249 ",null,"as in comment","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,240,"No","MediaTek","Technical",83,"10.38.9.3.9",25,"y = x × NB_channel_step + NB_channel_start, but the NB_channel_start=0~7",null,"change to \"y = x × NB_channel_step + NB_channel_start +50\"","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,504,"No","Self","Editorial",84,"10.38.9.3.10",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,505,"No","Self","Technical",84,"10.38.9.3.10",4,"Text description of how to map different values to different tables is hard to parse, especially if new values are added in the future. ",null,"Change the text to table, where first column is Sequence Code Index and second is description, i.e., first row will say \"9-24\" and description will say \"Length-127 ternary codes from Table 16-8\" etc. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,506,"No","Self","Technical",84,"10.38.9.3.10",10,"The text here is again hard to parse, make it table. ",null,"Add this information to the previous table for Sequence Code Index values, i.e., instead of description to 2nd column would be sequence code index reference, and there would be third field preamble code index which would then explain what preamble code index shall be used when using specific sequence code index value.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,507,"No","Self","Technical",84,"10.38.9.3.10",17,"I assume the numbers in {} are supposed to match the values, but the text does not say so. ",null,"Make the mapping from N_MSR field value to number of repetitions explicit by adding table that maps 0->32, 1->40 etc. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Carl Murray",null,877,"No","Qorvo","Technical",84,"10.38.9.3.10",17,"For clarity of the mapping, the values of this 3 bit field should be a table, and since there was some interest in smaller MSR values for future applications, the values reserved for future use should be 0 and 1.",null,"Create/reference a table where values 0 and 1 are reserved and values 2 to 7 map to MSR values 32 to 256 respectively.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1209,"No","Qorvo","Technical",84,"10.38.9.3.10",17,"The N_MSR field specification lists values of symbols reptation in text. For consistency should make this reference common table where other similar values are listed elsewhere. (Somewhat editorial, but technical to make TG aware).",null,"Change: \"specifies the number of repetitions or the MMRS symbol in each RSF, value range {32, 40, 48, 64, 128, 256}\" to \"specifies the number of MMRS symbol repetitions in each RSF as per Table 27.\"\n(Field name with underscore is a bit ugly, editor to consider common naming of same parameter in other messages or IEs)","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Alex Krebs",null,1393,"No","Apple","Technical",84,"10.38.9.3.10",17,"This is an enumeration, not a value range.",null,"Say its an enumeration of values, say other values are reserved.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Tero Kivinen",null,508,"No","Self","Technical",84,"10.38.9.3.10",19,"I assume the numbers in {} are supposed to match the values, but the text does not say so. ",null,"Make the mapping from STS Segment Length field value to number of repetitions explicit by adding table that maps 0->32, 1->64 etc. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Carl Murray",null,878,"No","Qorvo","Technical",84,"10.38.9.3.10",19,"To allow for potential future use cases the STS Segment\nLength field, should be a 3-bit field. Taking one of the spare bits in the Reserved field. Also the values and meaning should be presented as a table to make the mapping clearer.",null,"In Figure 52, make the STS Segment Length field ocupy bits 16 to 18, renumbering next fields as appropriate, and reducing reserved field by one bit). And, make a table to define the field value meanings, with 0 and 1 reserved, values 2 to 5 mapping to fragment lengths 32, 64, 128, 256, and vaues 6 and 7 reserved.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1210,"No","Qorvo","Technical",84,"10.38.9.3.10",19,"The STS Segment Length field, (a subfield of the Ranging PHY Configuration field), gives a text list of value meanings, but for clarity and consistency this should reference a table where the values and units etc defined. A similar field is specified in the MMS Ranging Configuration field of the AC IE already has a table. This should be used as part of a single common definition.",null,"Change: \"specifies length of RIF in units of 512 chips (~1 μs), with value range {32, 64, 128, 256}\" to \"specifies the fragment length of the RIF fragments as per Table 28\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Billy Verso",null,1211,"No","Qorvo","Technical",84,"10.38.9.3.10",19,"The STS Segment Length field, is misnamed, since there are no \"STS segments\" in the MMS ranging, i.e., this should be called RIF Fragment Length.",null,"Change the field name from \"STS Segment Length\" to \"RIF Fragment Length\", on this line and in Figure 52. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Alex Krebs",null,1394,"No","Apple","Technical",84,"10.38.9.3.10",19,"This is an enumeration, not a value range.",null,"Say its an enumeration of values, say other values are reserved.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Billy"]
[null,null,"Tero Kivinen",null,503,"No","Self","Editorial",84,"10.38.9.3.10",27,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,53,"Yes","STMicroelectronics","Technical",84,"10.38.9.3.9",6,"the lower limit of y is 50 for NB higher channel map",null,"change 50<=y<=249","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,511,"No","Self","Editorial",85,"10.38.9.3.11",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1360,"No","Qualcomm","Technical",85,"10.38.9.3.11",3,"Why number of RSF/RIF MAC param? it is part of the MMS PHY packet. Clarify whether these are Phy or MAC parameters.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,512,"No","Self","Technical",85,"10.38.9.3.11",4,"The table 14 defines more than just the valid range. ",null,"Change text to say that Number of RSF values are defined in table 14.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,509,"No","Self","Editorial",85,"10.38.9.3.11",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,879,"No","Qorvo","Technical",85,"10.38.9.3.11",7,"Make it more clear that the reserved entries of Table 14 might be used in the future.  ",null,"Change \"Reserved\" to \"Reserved for future use\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,513,"No","Self","Technical",85,"10.38.9.3.11",8,"The table 15 defines more than just the valid range. ",null,"Change text to say that table defines the values, not range.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,510,"No","Self","Editorial",85,"10.38.9.3.11",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,880,"No","Qorvo","Technical",85,"10.38.9.3.11",11,"Make it more clear that the reserved entries of Table 15 might be used in the future.  ",null,"Change \"Reserved\" to \"Reserved for future use\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,514,"No","Self","Technical",85,"10.38.9.3.12",13,"The Management MAC Configuration field is eight octets long, not seven. ",null,"Change seven to eight.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Youngwan So",null,929,"Yes","SAMSUNG Elec.","Technical",85,"10.38.9.3.12",13,"The management MAC Configuration Field seems to be 8 octets long, not 7 octets.\nAnd reference is wrong.",null,"Change from\n\"This seven-octet field is formatted as shown in Figure 53.\"\nTo\n\"This eight-octet field is formatted as shown in Figure 54.\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1395,"No","Apple","Technical",85,"10.38.9.3.12",13,"This says its a seven octet field, but Figure 54 shows a 8 octet field, newly carrying a one-to-many configuration field. This field can never be used for one-to-one ranging hence unnecessarily prolonging OTA configuration, and the 400 RSTU slots required for time efficient O2M cannot be configured using the O2O definitions hence depicted configuration does not work for O2M anyways. So this change from DraftC is a lose/lose situation. If the proponents of time-efficient O2M desire OTA configuration, a separate O2M MAC management config field should be specified (e.g. via a different message id and/or message control).",null,"Revert this change to preballot-C state by removing bits 56-63 again, and delete p87 lines 3-5.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Bin Qian",null,161,"No","Huawei","Editorial",86,"10.38.9.3.11",34,"“REPORT\" should be \"Report\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,515,"No","Self","Editorial",86,"10.38.9.3.12",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Riku Pirhonen",null,955,"No","NXP Semiconductors","Technical",86,"10.38.9.3.12",1,"Add ExtendedRpDuration field to the Managemetn MAC Configuration field figure",null,"Add ExtendedRpDuration field between RpDuration and Reserved, and use bits 44 and 45 for this","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","NEWFR",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Carlos Aldana",null,999,"No","Meta Platforms","Technical",86,"10.38.9.3.12",1,"Allocating 3 bits to Ranging Slot Duration is overkill.  Limit it to 2 bits so that upper bound is 1ms.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,54,"Yes","STMicroelectronics","Technical",86,"10.38.9.3.12",3,"what are the range of ranging slot duration?",null,"from 300/600 RSTU to 2400 RSTU?","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1212,"No","Qorvo","Technical",86,"10.38.9.3.12",10,"\"lowermost\" is an odd word…  perhaps should be more explicit.",null,"change to \"lowest value channel number enabled by the macMmsNbChannelAllowList…\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,55,"Yes","STMicroelectronics","Technical",86,"10.38.9.3.12",24,"RcpPollSlots field can be used by the initiator form transmission of the One-To-May Poll compact Frame ",null,"add \"or One-to-many\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,56,"Yes","STMicroelectronics","Technical",86,"10.38.9.3.12",26,"RcpResponseSlots field can be used by the initiator form transmission of the One-To-May Response compact Frame ",null,"add \"or One-to-many\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,57,"Yes","STMicroelectronics","Technical",86,"10.38.9.3.12",27,"RpDuration shall be fixed for one-to-many MMS in order to avoid a shift of the subround",null,"add, In One-to-Many MMS Ranging, the RpDuration field shall be keept and the number of UWB MMS fragment transmissions of the ranging round shall be adjusted.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1213,"No","Qorvo","Technical",86,"10.38.9.3.12",27,"Seems to be an extraneous \"RpDuration\" in the middle of the line.",null,"Delete it, or should it be something different like macMmsRpDuration","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Riku Pirhonen",null,956,"No","NXP Semiconductors","Technical",86,"10.38.9.3.12",33,"Add description for ExtendedRpDuration field",null,"The ExtendedRpDuration field enables non-interleaved MMS packets by extending the ranging phase to double or triple of the RpDuration. By default, bits are 00, which means interleaved initiator and responder transmissions. Bit values 01 meand double RpDuration and non-interleaved transmission by initiator and responder as shown in Figure XX [in chapter 10.38.5], and bits set to 10 mean triple RpDuration and non-interleaved transmissions by initiator – responder – initiator, as shown in figure XX [in chapter 10.38.5]. Bit combination 11 is reserved.","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","NEWFR",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Carlos Aldana",null,1000,"No","Meta Platforms","Technical",87,"10.38.9.3.12",5,"The concept of MrpThirdSlots seems to work for 2 responders.  What happens where there are more than 2 responders?  Do we need to define MrpFourthSlots, MrpFifthSlots,etc?   We probably need a more scalable solution.",null,"Please clarify","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,516,"No","Self","Editorial",87,"10.38.9.3.13",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1361,"No","Qualcomm","Technical",87,"10.38.9.3.13",11,"The requested channel map could be Lower/Upper or both.",null,"Dedicate 2 bits for \"NB Channel Map requested\" and explain the mapping.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Pooria"]
[null,null,"Riku Pirhonen",null,957,"No","NXP Semiconductors","Technical",87,"10.38.9.3.14",25,"To keep NB and UWB clock synchronization simple, and avoid issues with the 100 ppm tolerance requirement, the Time Offset value should take chip rate clock into account. For NB it is 2 MHz (0.5 µs) and for UWB 1/499.2 MHz (~2ns). The smallest common step size is 2.5 µs. Add the same comment to the corresponding PIB attribute if such is defined.",null,"… and the value shall be mulitple of 2.5 µs. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Alex Krebs",null,1400,"No","Apple","Technical",87,"10.38.9.3.14 ",25,"We discussed/agreed limiting time offset to 1s before to improve responder energy consumption. I wonder if it is too strict to mandate this, since 1. SOR time offset is a one-time process hence impact on overall energy consumption is scanning once per ranging session 2. energy consumption wrt to SOR time offset is determined by the responder's crystal accuracy which is an implementation choice. My suggestion is to not prohibit use, but rather make a more practical recommendation in the standard, allowing higher accurcy devices to take advantage of the full value range.",null,"Replace \"The maximum...second.\" by\n\nA value of 0-300ms is recommended for this field to limit packet arrival time uncertainty for the responder device.","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,58,"Yes","STMicroelectronics","Technical",87,"10.38.9.3.15",28,"SOR Time offset is between ADV conf and not ADV Poll",null,"This is a four-octet, 32-bit field that specifies the time offset in 1/499.2 MHz resolution between the start of the Advertising Confirmation Compact frame, or the Public Advertising Confirmation Compact frame, and the start of the Start of Ranging Compact frame.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Lei HUANG",null,1434,"Yes","Huawei","Technical",87,"10.38.9.3.15",28,"The SOR Time Offset field indicates the time offset between the start of the Advertising Confirmation Compact frame and the start of the Start of Ranging Compact frame.",null,"Change \"the start of the Advertising Poll Compact frame, or the Public Advertising Poll Compact frame\" to \"the start of the Advertising Confirmation Compact frame\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Riku Pirhonen",null,958,"No","NXP Semiconductors","Technical",87,"10.38.9.3.15",29,"Offset value betwee two NB packets should be multiple of chip rate of 2 MHz (0.5 µs). The smallest common step size is thus 0.5 µs.",null,"… and the value shall be mulitple of 0.5 µs. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Tero Kivinen",null,518,"No","Self","Editorial",88,"10.38.9.3.16",2,"The single octet is not a key, it is seed. ",null,"Change \"the key\" to \"a seed\".","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Rojan Chitrakar",null,112,"No","Huawei","Editorial",88,"10.38.9.3.16",3,"\"This field that carries the value of the macMmsPrngSeed attribute.\"\nunneccessary \"that\"",null,"Change as:\n\"This field carries the value of the macMmsPrngSeed attribute.\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,517,"No","Self","Editorial",88,"10.38.9.3.17",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,519,"No","Self","Technical",88,"10.38.9.3.17",8,"This information from mapping 1-8 and 14, and 15 is now in at least 4 different locations. Repeating same information in multiple locations is bad. ",null,"Create a table that provides mapping from the values to references where the modulation modes can be found, i.e. for values 1-8 the description would say modulation modes 1-8 from table 58. etc. Then change Control Phase Config field, Report Phase Config fiield, macMmsControlPhaseMode, and macMmsReportPhaseMode descriptions to use that same table.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,241,"No","MediaTek","Technical",88,"10.38.9.3.17",15,"To be consistent with  p56 L10~13\nthere should normative requirements that when value 1~8 is selected for Control Phase Config, values other than 1~8 cannot be selected for Report phase Config.\nSimilarly, if value 14~15 is selected for Control Phase Config, then values other than 14~15 cannot be selected for Report Phase Config.",null,"as in comment","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1362,"No","Qualcomm","Technical",88,"10.38.9.3.17",16,"This sequence mapping can be applied to control sequence since it is HPRF, but SYNC/SFD sequence for the MMRS packet is better to be 127 for RSF=127 to keep PRF consistent..",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,520,"No","Self","Technical",88,"10.38.9.3.17",18,"This mapping from sequence control index field is already defined in the 10.38.9.3.10. ",null,"After the table of mapping from sequence code index values to preamble code index is added there, this text can directly refer to that table, without copying the text here.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,242,"No","MediaTek","Technical",88,"10.38.9.3.17",19,"The case of Sequence code index 9~24 should also be mention here to use the conversion formula, to be consistent with p84 L11",null,"as in comment","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1214,"No","Qorvo","Technical",88,"10.38.9.3.19",25,"10.38.9.3.19 The Block Index field, is simply \"16-bit index of the current ranging block.\" a good candidate to insert in the text where it is used and not reference this tiny clause.",null,"Make editorial and let the editor take care of it.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1215,"No","Qorvo","Technical",88,"10.38.9.3.20",27,"10.38.9.3.20 The Round Index field, is simply \"8-bit index of the current ranging round.\" another good candidate to insert in the text where it is used and not reference this tiny clause.",null,"Make editorial and let the editor take care of it.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,523,"No","Self","Technical",89,"10.38.9.3.21",2,"It was helpful that block index, and round index fields defined the length of the field in the definition, so it is clear how long the field is supposed to be. This helps noticing places where the field length in the actual frame description does not match the field length of the data in that field. ",null,"Add text that this key id field is 8-bit long.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Pooria Pakrooh",null,1363,"No","Qualcomm","Technical",89,"10.38.9.3.22",3,"This newly added field can cause unnecessary overhead, how long can this be?",null,"Limit the maximum duration.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,522,"No","Self","Editorial",89,"10.38.9.3.22",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,521,"No","Self","Editorial",89,"10.38.9.3.23",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,524,"No","Self","Technical",89,"10.38.9.3.23",15,"The error names are quite long. Shorter ones might be better, especially as there is description that describes when it is used. ",null,"Change REQUESTED_PARAMETERS_NOT_ACCEPTED to INVALID_PARAMETERS, REQUIRED_CAPABILITY_NOT_SUPPORTED_BY_RESPONDER to to NOT_SUPPORTED, REJECTED_WITH_SUGGESTED_CONFIG_CHANGE to CONFIG_REJECTED.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1216,"No","Qorvo","Editorial",89,"10.38.9.3.23",16,"Name is long and not aesthetically pleasing, especially where used in the text.",null,"consider use and revising NAME to a \"short description\" for use in reference, and longer description in then in the meaning column.  Revising all referenced places accordingly","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,525,"No","Self","Editorial",90,"10.38.9.3.24",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,529,"No","Self","Technical",90,"10.38.9.3.24",3,"The NB Channel Map Present is bad name, as it does not only indicate whether NB Channel Map is present, it also indicates the type of it. ",null,"Change NB Channel Map Present field to NB Channel Map Type field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Pooria"]
[null,null,"Bin Qian",null,162,"No","Huawei","Technical",90,"10.38.9.3.24",4,"This paragraph contradicts the following paragraph",null,"Remove this paragraph","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,527,"No","Self","Technical",90,"10.38.9.3.24",4,"Lines 4-5 are wrong as text on lines 6-10 actually defines how 2 bit NB channel map present field is parsed. ",null,"Remove lines 4-5.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Pooria Pakrooh",null,1364,"No","Qualcomm","Technical",90,"10.38.9.3.24",4,"Remove Lines 4-5, it is explained in lines 6-7",null,"As in the comment","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,528,"No","Self","Technical",90,"10.38.9.3.24",7,"Make a new table that maps the NB Channel Map Present field to type of the NB Channel Map and use it. ",null,"Add new table that maps 0 = none, 1 = NB lower Channel Map, 2 = NB Higher Channel Map and 3 = NB Channel Map with references to suitable section. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Pooria"]
[null,null,"Bin Qian",null,163,"No","Huawei","Editorial",90,"10.38.9.3.24",23,"\"Block index field\" should be \"Block Index field\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,526,"No","Self","Editorial",90,"10.38.9.3.24",30,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Alex Krebs",null,1396,"No","Apple","Technical",90,"10.38.9.3.24","4,5","Deprecated by newly added lines 6-10",null,"Remove lines 4,5","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Kangjin Yoon",null,1414,"No","Spark Microsystems","Editorial",90,"10.38.9.3.24","7,9,10","Use octet instead of byte for consistency.",null,"Change \"byte\" to \"octet\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Mickael Maman",null,59,"Yes","STMicroelectronics","Technical",90,"10.39.9.3.24",4,"remove old description of NB channel Map ",null,"remove line 4 and 5","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Bin Qian",null,164,"No","Huawei","Editorial",91,"10.38.9.3.24",3,"\"Block index field\" should be \"Block Index field\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,532,"No","Self","Technical",91,"10.38.9.3.24",3,"The text does not make any sense. It starts talking about Start and End Slot Indexes Present fields but the text in the end says \"or are not included when Block and Rounde Index field value is zero\", but there is no block and round index present fields in the structure. ",null,"Most likely the block and round index present fields should be start and end slot indices present fields.","Yes","Revised","doc 15-24-0401-01-04ab-proposed-resolution-for-compact-frame-miscel-1.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,533,"No","Self","Editorial",91,"10.38.9.3.24",6,"Typo. ",null,"Change Staring to Starting.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,531,"No","Self","Editorial",91,"10.38.9.3.25",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,530,"No","Self","Editorial",91,"10.38.9.3.25",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Shang-Te Yang",null,926,"Yes","Apple","Editorial",91,"10.38.9.4",17,"The change from cmmon message field to the first comapct frame detail is abrumpt, and the 0x00 vs 0x10 options of message control field is very scattered and hard to track. ",null,"Duplicate the table-1 Compacrt Fame from 7.3.7 to 10.38.9.4 with more columns calling out if there are mulitple control field defined. ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,534,"No","Self","Editorial",92,"10.38.9.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,538,"No","Self","Technical",92,"10.38.9.4",5,"This means that RPA hash changes for every single advertising poll compact frames, thus quite often (for advertising poll compact frames to be useful, they needs to be transmitted at least several times per minute). If an passive attacker listens the advertising poll compact frames for few thousands of frames it can build database of known RPA hash and prand values that will allow it to keep track of sender. ",null,"The current privacy protection provided by the RPA hash and prand method is completely inadequate. Replace the broken privacy methods with the methods defined in 4ac, or more accurately use the existing 802.15.4 frames to which 4ac will provide privacy.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1217,"No","Qorvo","Technical",92,"10.38.9.4",6,"The numbering space of the Message Control field is sparce, and seems to be mostly increasing in units of 16, but not always.  After 4ab this numbering space will have to be managed by the 802.15 assigned numbers authority (ANA) and this will be easier to do via a simple sequential list.",null,"In preparation for ANA management of the numbering space, renumber all Message Control field values in ALL compact frames to be simple sequential values.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1218,"No","Qorvo","Technical",92,"10.38.9.4",7,"In general the message formats being totally dependant on Message Control field value while very flexible makes decoding the frames into a huge \"if … then…\" type structure where each value needs separate decoding routine which from a software point of view seems a bit clunky, and has given rise to multiple separate messages when different fields are needed.",null,"Please consider is this the best way to do it.  Pros/Cons… it’s not too late to improve the design choices here.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,539,"No","Self","Technical",92,"10.38.9.4",9,"Is there similar indication that if message control field value of 0x10 is used, then certain compact frame id field values are supported? If not, how does the received know which values are supported? ",null,"It seems only some subset of compact frame ids are supposed to be supported, but how does the transmitted know whether the other end supports specific frame ids. If there is some kind of set of frame ids (like 0x01-0x06) then there should be table that lists those requirements. Of course those will be present in the PICS when they are added, but having that also in the text would be good.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,113,"No","Huawei","Technical",92,"10.38.9.4",11,"With the new Presence Bitmap format, the 3 variants (0x10, 0x20 and 0x30) can be combined in a single variant by either making the Initialization Slot Duration and Cap Duration fields mandatory or adding relevant presence bits for Initialization Slot Duration and Cap Duration.",null,"Combine the 3 variants (0x10, 0x20 and 0x30) in a single variant by  either making the Initialization Slot Duration and Cap Duration fields mandatory in all 3 variant or adding relevant presence bits for Initialization Slot Duration and Cap Duration.","Yes","Revised","doc 15-24-0380-01-04ab-proposed-resolution-for-advertising-poll-compact-frame.docx","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,535,"No","Self","Editorial",92,"10.38.9.4",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,536,"No","Self","Editorial",92,"10.38.9.4",17,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,537,"No","Self","Editorial",92,"10.38.9.4",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,540,"No","Self","Editorial",93,"10.38.9.5",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,542,"No","Self","Technical",93,"10.38.9.5",14,"The Responder RPA Hash field description should be clear that the responder IRK that is used, is the IRK of the transmitter of this frame. ",null,"Add \"(i.e. the IRK of device transmitting this frame)\" to the end.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,114,"No","Huawei","Technical",93,"10.38.9.5",15,"0x20 and 0x30 doesn't exist",null,"Replace \"0x00, 0x10, 0x20 or 0x30\" with \"0x00 or 0x10\"","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Zhepeng Ma",null,199,"Non-Voter","Calterah Semiconductor ","Technical",93,"10.38.9.5",15,"For Advertising Response Compact frame, there are four values for Message Control field, but only Message Control field value of 0x00 and 0x10 are stated in this sub-clause.",null,"Need to clarify the usage of the Message Control field value of 0x20 and 0x30","No","Revised","Replace \"0x00, 0x10, 0x20 or 0x30\" with \"0x00 or 0x10\"","NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,541,"No","Self","Editorial",93,"10.38.9.5",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,243,"No","MediaTek","Technical",93,"10.38.9.5",21,"There should also be a similar language that if message control is 0x00 for ADV RESP, then compact frame ID 0~6 with message ctrl 0x00 are supported",null,"as in comment","No",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,60,"Yes","STMicroelectronics","Technical",93,"10.39.9.4",5,"missing the range of N",null,"add \"in the range 0 to 15.","Yes","Revised","doc 15-24-0380-01-04ab-proposed-resolution-for-advertising-poll-compact-frame.docx","NEWFR",null,"DONE"]
[null,null,"Rojan Chitrakar",null,115,"No","Huawei","Editorial",94,"10.38.9.5",1,"Presence Bitmap field can be 1 or 2 octets",null,"Change the size of the Presence Bitmap field to 1 or 2.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Rojan Chitrakar",null,116,"No","Huawei","Technical",94,"10.38.9.5",1,"NB channel Map field is 6 octets long, either the field here should be renamed to a different name or the 6-octet bitmap should be called something else (e.g., Full NB Channel Map).",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,543,"No","Self","Editorial",94,"10.38.9.5",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,546,"No","Self","Technical",94,"10.38.9.5",1,"The Management MAC Configuration field is 8 octets long. ",null,"Change 0/7 to 0/8.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,117,"No","Huawei","Technical",94,"10.38.9.5",3,"It is better to list the present fields that may be non-zero to avoid having to change the sentence if any new presence bit is added to the presence bitmap.",null,"change as:\n\"…, except that the fields other than the NB Channel Map Present field, the Management PHY Configuration Present field, the Management MAC Configuration Present field, the Ranging PHY Configuration Present field, the Ranging MAC Configuration Present field, the SMC TLVs Present field, the MMS Ranging Mode Configuration Present field and the Extended Presence Bitmap Present field shall all be set to zero.\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,118,"No","Huawei","Technical",94,"10.38.9.5",5,"Only the 6 octet version the NB channel Map field (10.38.9.3.7) is referenced.",null,"Add the other versions of the NB channel Map field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1365,"No","Qualcomm","Technical",94,"10.38.9.5",5,"This could be lower and upper NB channel maps as well",null,"Change to \"per 10.38.9.3.7, 10.38.9.3.8 and 10.38.9.3.9\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,119,"No","Huawei","Technical",94,"10.38.9.5",8,"\"field\" is missing",null,"add \"field\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,120,"No","Huawei","Technical",94,"10.38.9.5",10,"If the sentence in line 3 is modified as suggested in another comment, this sentence is not necessary and can be deleted.",null,"Delete the sentence since this can be covered by the sentence in line 3.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,121,"No","Huawei","Technical",94,"10.38.9.5",15,"\"field\" is missing",null,"add \"field\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,544,"No","Self","Editorial",94,"10.38.9.6",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,545,"No","Self","Technical",94,"10.38.9.6",23,"How does the responder know which IRK is used to calculate, or is it assumed to check both? ",null,"Specify how the responder of the start of ranging compact frame will know which IRK to use, or specify that initiator needs to calculate both RPA Hash with both IRKs and by comparing them to the RPA hash of the frame they know whether it was for single responder or for multiple. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,61,"Yes","STMicroelectronics","Technical",94,"10.39.9.5",1,"In figure 67, the presence bitmap is 1/2 because of extended presence bitmap for SMC TLVs and MMS Ranging mode configuration fields",null,"as in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,547,"No","Self","Editorial",95,"10.38.9.6",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,122,"No","Huawei","Editorial",95,"10.38.9.6",15,"Presence Bitmap field can be 0, 1 or 2 octets",null,"Change the size of the Presence Bitmap field t0 0 , 1 or 2 .","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,548,"No","Self","Editorial",95,"10.38.9.6",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,550,"No","Self","Technical",95,"10.38.9.6",15,"It might be better to split the figure 70 to 3 different figures, one for case where Status is success, one when the status is config change, and one for all other cases. ",null,"Split figure 70 to three.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,551,"No","Self","Technical",95,"10.38.9.6",15,"Presence bitmap can also be 2 octet long if the Starting Block Index or MMS Ranging Mode Configuration are included, as they are in the extended parts of the Presence bitmap. ",null,"Change 0/1 to 0/1/2 for Presence Bitmap.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1002,"No","Meta Platforms","Technical",95,"10.38.9.6",15,"Figure 70 is very flexible but there is no indication if the fields are present or not.  Need to add a presence indicator, similar to the one in 10.38.9.3.24, to allow for parsing of the field at the receiver.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1366,"No","Qualcomm","Technical",95,"10.38.9.6",15,"In Figure 70, change \"NB Channel Map\" field length to 0/2/5/6.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,549,"No","Self","Technical",95,"10.38.9.6",18,"The text says that if the status is success then we continue, but not all configuration values are transmitted, but I think they still can be transmitted even when some of them can also be omitted. ",null,"Remove \"but ...explictly\". ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1001,"No","Meta Platforms","Editorial",95,"10.38.9.6",20,"Should be more explicit and replace \"as one of the non-reserved values\" with \"to a value of 1,2, 3, or 4.\"",null,"As in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,62,"Yes","STMicroelectronics","Technical",95,"10.39.9.6",15,"In figure 70, the presence bitmap is 0/1/2 because of extended presence bitmap for MMS Ranging mode configuration fields and NB channel Map is 0/2/5/6",null,"as in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,123,"No","Huawei","Technical",96,"10.38.9.6",5,"the MMS Ranging Mode Configuration field and the Extended Presence Bitmap Present field needs to be added to the list.",null,"add the MMS Ranging Mode Configuration field and the Extended Presence Bitmap Present field to the end of the sentence","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,124,"No","Huawei","Technical",96,"10.38.9.6",8,"Sentence needs to be updated",null,"change as:\n\"The encoding and meaning of the NB Channel Map, the Management PHY Configuration field, Management MAC Configuration field, Ranging PHY Configuration field and the Ranging MAC Configuration field is identical to that of the fields of the same name in the Advertising Response\nCompact frame with Message Control field value equal to 0x00.\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,125,"No","Huawei","Technical",96,"10.38.9.6",14,"In the previous LB round, much effort was made to consolidate the different message variants; variant 0x20 can be easily combined into variant 0x10 by adding a presence bit: Block Description List Present.",null,"Combine variant 0x20 into variant 0x10 by adding the Block Description List Present in the Presence Bitmap field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carl Murray",null,881,"No","Qorvo","Editorial",96,"10.38.9.6",14,"The line \"When the Message Control field value is 0x20, the ranging executed in Hyper Block mode\" does not read well",null,"Replace text with \n\n\"When the Message Control field value is 0x20, the ranging operates in Hyper Block mode\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1219,"No","Qorvo","Technical",96,"10.38.9.6",15,"\"In this case, the responders assume\" is strange, not sure what it should be (or even if it should be in this clause). can assume, may assume, should assume ?",null,"Change to \"should assume\" ?","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,552,"No","Self","Editorial",96,"10.38.9.6",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,553,"No","Self","Editorial",96,"10.38.9.6",27,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,554,"No","Self","Technical",96,"10.38.9.6",27,"As this is talking about the hyper blocks, I assume the 8-bit field called Block Index is really a Relative Block Index, not Block Index. ",null,"Change Block Index to Relative Block Index.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1220,"No","Qorvo","Technical",97,"10.38.9.6",5,"This be talking about \"ranging slots\", \"ranging blocks\" etc.\nAlso somewhere in the text MMS slots were constrained to 300 RSTU multiples, so maybe we want to make that constraint in the slot duration field here (and elsewhere)",null,"Add in \"ranging\" before block, round, slot as appropriate.\nConsider if appropriate to constrain slot durations to 300 RSTU multiples and update accordingly. Here and everywhere.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1003,"No","Meta Platforms","Technical",97,"10.38.9.7",7,"This frame keeps getting longer after every draft.  Let's limit the duration to 1ms.  Add text that says so.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,555,"No","Self","Editorial",97,"10.38.9.7",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1311,"No","NXP Semiconductors","Editorial",97,"10.38.9.7",13,"Missing \"be\" : shall be calculated",null,"shall be calculated","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,557,"No","Self","Technical",97,"10.38.9.7",14,"When is the one to one poll compact frame sent to multiple recipient? ",null,"Remove text about one to one poll compact frame to sent to multiple recipients.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,558,"No","Self","Technical",97,"10.38.9.7",22,"What is the point of including two extra octets of zero when the frames are supposed to be compact. ",null,"Remove extra unneeded data.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,556,"No","Self","Editorial",97,"10.38.9.7",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,63,"Yes","STMicroelectronics","Editorial",97,"10.39.9.7",24,"update figure 74 with 0x00, 0x00 as other padding",null,"as in comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Rojan Chitrakar",null,126,"No","Huawei","Editorial",98,"10.38.9.7",1,"Presence Bitmap field can be 0 or 1 octets",null,"Change the size of the Presence Bitmap field t0 0 or 1.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Rojan Chitrakar",null,127,"No","Huawei","Technical",98,"10.38.9.7",1,"NB channel Map field is 6 octets long, either the field here should be renamed to a different name or the 6-octet bitmap should be called something else (e.g., Full NB Channel Map).",null,"As ini comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,559,"No","Self","Editorial",98,"10.38.9.7",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,128,"No","Huawei","Technical",98,"10.38.9.7",6,"Only the 6 octet version the NB channel Map field (10.38.9.3.7) is referenced.",null,"Add the other versions of the NB channel Map field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1004,"No","Meta Platforms","Technical",98,"10.38.9.8",14,"This frame keeps getting longer after every draft.  Let's limit the duration to 1ms.  Add text that says so.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,560,"No","Self","Editorial",98,"10.38.9.8",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,561,"No","Self","Technical",98,"10.38.9.8",22,"What is the point of including extra octets of zero when the frames are supposed to be compact. ",null,"Remove extra unneeded data.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,64,"Yes","STMicroelectronics","Technical",98,"10.39.9.7",7,"Management PHY Configuration and Management MAC Configuration shall not be short term parameters. There is a consensus to not switch from UWB driven MMS to NBA MMS. Another case is for one-to-may MMS ranging, we shall not modify them in one-to-one POLL compact frame when used in one-to-many subround.",null,"list of change: In figure 75 remove Management PHY Configuration and Management MAC Configuration. Line 3, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\" and remove line 7 and 8.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,562,"No","Self","Editorial",99,"10.38.9.8",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,565,"No","Self","Technical",99,"10.38.9.8",1,"What is the point of including padding when the frames are supposed to be compact. ",null,"Remove extra padding or add text explaining why the padding is required.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,563,"No","Self","Editorial",99,"10.38.9.8",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1221,"No","Qorvo","Technical",99,"10.38.9.9",20,"The four (non-secure) Report messages have similar generic format. Each begins with an RPA Hash and a Message Control Octet, the latter of which is a sparse set of values.  Seems we have an opportunity to use a common Compact Frame ID field value for all of these saving on Compact Frame ID space over half of which are used up already.",null,"Change to single \"Report\" ID in Table 1, and use the Message Control field (octet) to identify the meaning and encoding for the different flavours of secure report: One-to-one Initiator, One-to-one Responder, One-to-many Initiator and One-to-many Responder.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,564,"No","Self","Editorial",99,"10.38.9.9",22,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,566,"No","Self","Technical",99,"10.38.9.9",23,"If there is no different message control fields, the whole field can be omitted. This is supposed to be compact frames, make them compact. ",null,"Remove Message Control field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,65,"Yes","STMicroelectronics","Technical",99,"10.39.9.8",7,"Management PHY Configuration and Management MAC Configuration shall not be short term parameters. There is a consensus to not switch from UWB driven MMS to NBA MMS. Another case is for one-to-may MMS ranging, we shall not modify them in one-to-one RESP compact frame when used in one-to-many subround.",null,"list of change: In figure 78 remove Management PHY Configuration and Management MAC Configuration. Line 7, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\" and in line 16 remove\"Management PHY Configuration, Management MAC Configuration\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,568,"No","Self","Editorial",100,"10.38.9.10",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,569,"No","Self","Editorial",100,"10.38.9.10",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,567,"No","Self","Editorial",100,"10.38.9.9",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1222,"No","Qorvo","Technical",100,"10.38.9.9",1,"Passthrough size in figure 80 says 0/variable, but from 10.38.9.3.6 it looks like it should be 1/variable. ",null,"Chane to 1/variable in this figure and any other figures with passthrough data.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Libra Xiao",null,918,"No","NewRadio Technologies Co., Ltd.","Technical",100,"10.38.9.9","#3,#4,#5","Original text is :\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments \"\n\nIt should be clarified how to obtain the value of the Round-trip Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Round-trip Time parameter can be the cumulative or mean value of multiple RSFs and/or RIFs.",null,"\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Round-trip Time  should be the mean value of several Round-trip Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,570,"No","Self","Editorial",101,"10.38.9.10",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Libra Xiao",null,912,"No","NewRadio Technologies Co., Ltd.","Technical",101,"10.38.9.10","#3,#4,#5","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase, the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,571,"No","Self","Editorial",101,"10.38.9.11",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,572,"No","Self","Editorial",101,"10.38.9.11",15,"My understanding is that the logical way of sending frames is advertising poll, advertising response, advertising confirmation, start of ranging and so on. It would be logical to make description of the frames follow this same order. ",null,"move 10.38.9.11 between 10.38.9.5 and 10.38.9.6.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,66,"Yes","STMicroelectronics","Technical",101,"10.39.9.8",6,"Management PHY Configuration and Management MAC Configuration shall not be short term parameters. There is a consensus to not switch from UWB driven MMS to NBA MMS. Another case is for one-to-many MMS ranging, we shall not modify them in one-to-one REPORT compact frame when used in one-to-many subround.",null,"list of change: In figure 83 remove Management PHY Configuration and Management MAC Configuration. Line 7, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\" and in line 11 remove \"Management PHY Configuration, Management MAC Configuration\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,67,"Yes","STMicroelectronics","Technical",102,"10.38.9.11",1,"In advertising confirmation compact frame, the responder address is missing.",null,"add 1 octet for responder address in Figure 85 and the following text \"The Responder Address field identifies the address of a responder selected by the initiator to be involved in the following ranging session.\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,573,"No","Self","Editorial",102,"10.38.9.11",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,574,"No","Self","Editorial",102,"10.38.9.11",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,575,"No","Self","Editorial",102,"10.38.9.11",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,1014,"No","Meta Platforms","Technical",102,"10.38.9.12",16,"This frame keeps getting longer after every draft.  Let's limit the duration to 1ms.  Add text that says so.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,576,"No","Self","Editorial",102,"10.38.9.12",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,580,"No","Self","Technical",103,"10.38.9.12",8,"What is the point of including extra octets of zero when the frames are supposed to be compact. ",null,"Remove extra unneeded data.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Billy Verso",null,1223,"No","Qorvo","Technical",103,"10.38.9.12",9,"\"not the first one\" is ambiguous.",null,"Change to say \"for second and subsequent ranging sub-rounds in each ranging round\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,577,"No","Self","Editorial",103,"10.38.9.12",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,578,"No","Self","Editorial",103,"10.38.9.12",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1224,"No","Qorvo","Technical",103,"10.38.9.12",14,"In One-to-many Poll Compact frame, with its different formats, I see multiple different ways of doing the same thing, e.g. number of responders and slots per responder, is same/similar to number of responders with individual start and end index specifications. I understand this gives lots of flexibility, but it also add complexity in implementations having to code and test all the variations, or choose which to implement which leads to incompatibilities where different choices are made by different vendors.  Can TG4ab not converge as a group on a single message format that gives the most sensible set of controls and delete the rest.",null,"Rationalize the options here to have a single message format.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Billy Verso",null,1225,"No","Qorvo","Technical",103,"10.38.9.12",16,"The Number of Responders field should be the  number of responders, not the number of responders minus 1.  This is an octet, so it can cover up to 255 responders, which is more than enough without subtracting 1.  Most parameters give the exact number (of slots etc).  Doing this saves having to remember to add 1 to get the number in the field, when using it in calculations etc.  Otherwise please change the field name to \"One Less Than The Number of Responders\".",null,"Delete \"minus one\" from the end of the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1226,"No","Qorvo","Technical",103,"10.38.9.12",18,"The Slots Per Responder field should be the number of slots, not the number minus 1.  This is an octet, so it can cover up to 255 slots, which is more than enough without subtracting 1.  Remove this \"minus one\", otherwise please change the field name to \"One Less Than The Slots Per Responder\".",null,"Delete \"minus one\" from the end of the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,581,"No","Self","Technical",103,"10.38.9.12",21,"I assume the addresses are calculated using responders IRK and the initiators prand. ",null,"Add text who the addresses are generated.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,579,"No","Self","Editorial",103,"10.38.9.12",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Youngwan So",null,930,"Yes","SAMSUNG Elec.","Editorial",103,"10.38.9.12","P103L10, \nP103L14, \nP103L24","Figure title formality could be more consistent with those of other chapters.",null,"The title of some Figures should be updated as follows;\n\nFrom\n\"Figure 89—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x00\"\nTo\n\"Figure 89—One-to-many Poll Compact frame format (Message Control field value = 0x00\"\n\nFrom\n\"Figure 90—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x10\"\nTo\n\"Figure 90—One-to-many Poll Compact frame format (Message Control field value = 0x10\"\n\nFrom\n\"Figure 91—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x20\"\nTo\n\"Figure 91—One-to-many Poll Compact frame format (Message Control field value = 0x20\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1227,"No","Qorvo","Technical",104,"10.38.9.12",2,"Again unnecessary to use number of responders minus one.  Remove this \"minus one\", or change the field name to \"One Less Than The Number of Responders\".",null,"Delete \"minus one\" from the end of the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,582,"No","Self","Editorial",104,"10.38.9.12",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,584,"No","Self","Technical",104,"10.38.9.12",7,"The slot index fields are limited to 8-bits because of the security, but here they are sent as 16-bit fields. ",null,"Change Start and End Slot Index fields to be one octet long.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,583,"No","Self","Editorial",104,"10.38.9.12",29,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1228,"No","Qorvo","Technical",104,"10.38.9.12",31,"Another octet size field \"Number of Sub-Rounds field\" that does not need the \"minus one\".  Remove this \"minus one\", otherwise please change the field name to \"One Less Than The Number of Sub-Rounds\".",null,"Delete \"minus one\" from the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Youngwan So",null,933,"Yes","SAMSUNG Elec.","Editorial",104,"10.38.9.12","P104L27, \nP105L17,\nP106L12,\nP107L14","Message Control field values in sentence introducing each Message Content fields should be also updated as it is changed in different CID CRs above.",null,"\nUpdate is needed as follows;\n\nFrom\n\"When the Message Control field value is 0x50 the Message Content field shall be formatted as shown in Figure 93\"\nTo\n\"When the Message Control field value is 0x30 the Message Content field shall be formatted as shown in Figure 93\"\n\nFrom\n\"When the Message Control field value is 0x70 the Message Content field shall be formatted as shown in Figure 94.\"\nTo\n\"When the Message Control field value is 0x40 the Message Content field shall be formatted as shown in Figure 94.\"\n\nFrom\n\"When the Message Control field value is 0x80 the Message Content field shall be formatted as shown in Figure 96.\"\nTo\n\"When the Message Control field value is 0x50 the Message Content field shall be formatted as shown n Figure 96.\"\n\nFrom\n\"When the Message Control field value is 0x90 the Message Content field shall be formatted as shown in Figure 98.\"\nTo\n\"When the Message Control field value is 0x60 the Message Content field shall be formatted as shown in Figure 98.\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Youngwan So",null,931,"Yes","SAMSUNG Elec.","Editorial",104,"10.38.9.12","P104L29\nP105L19,\nP106L1","Figure title could be more consistent with those of other chapters.\nIn addition to that, some Message Control field value in Figure title is NOT continuous.",null,"\nThe title of some Figures and Message Control value should be updated as follows;\n\nFrom\n\"Figure 93—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x50\"\nTo\n\"Figure 93—One-to-many Poll Compact frame format (Message Control field value = 0x30\"\n\nFrom\n\"Figure 94—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x70\"\nTo\n\"Figure 94—One-to-many Poll Compact frame format (Message Control field value = 0x40\"\n\nFrom\n\"Figure 95—Responder Detail element format (Message Control = 0x70\"\nTo\n\"Figure 95—Responder Detail element format (Message Control = 0x40\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Youngwan So",null,932,"Yes","SAMSUNG Elec.","Editorial",104,"10.38.9.12","P106L15,\nP107L1,\nP107L16,\nP108L1","Figure title formality could be more consistent with those of other chapters.\nIn addition to that, some Message Control field value in Figure title is missing..",null,"\nThe title of some Figures and Message Control value should be updated as follows;\n\nFrom\n\"Figure 96—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x80\"\nTo\n\"Figure 96—One-to-many Poll Compact frame format (Message Control field value = 0x50\"\n\nFrom\n\"Figure 97—Responder Detail element format (Message Control = 0x80\"\nTo\n\"Figure 97—Responder Detail element format (Message Control = 0x50\"\n\nFrom\n\"Figure 98—Format of the Message Content field in the One-to-many Poll Compact frame when the Message Control field value is 0x90\"\nTo\n\"Figure 98—One-to-many Poll Compact frame format (Message Control field value = 0x60\"\n\nFrom\n\"Figure 99—Responder Detail element format (Message Control = 0x90\"\nTo\n\"Figure 99—Responder Detail element format (Message Control = 0x60\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1229,"No","Qorvo","Technical",105,"10.38.9.12",1,"Another unnecessary \"minus one\", on a byte field that is more than large enough to specify number (of slots?) in the (MMS ranging) sub-round.  Probably 3  or 4 slots is the minimum size could make it \"minus two\" or more, but let's just remove the \"minus one\" and make the field name right,",null,"Delete \"minus one\" from the end of the line.  ","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1230,"No","Qorvo","Technical",105,"10.38.9.12",1,"The Size of Sub-Rounds field does not indicate the units, also would be better renamed to \"Sub-round Size\".",null,"Change to say \"The Sub-round Size field indicates the size of the ranging sub-round in units of ranging slots.\", and rename the field in Figure 93 to \"Sub-round Size\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Billy Verso",null,1231,"No","Qorvo","Technical",105,"10.38.9.12",1,"units are not specified here. Is it in \"ranging slots\"?",null,"Add the unit into the line, change \"size\" to \"size in  ranging slot units\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,585,"No","Self","Editorial",105,"10.38.9.12",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1232,"No","Qorvo","Technical",105,"10.38.9.12",22,"Another number of responders minus one.",null,"Delete \"minus one\" from the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Billy Verso",null,1233,"No","Qorvo","Technical",105,"10.38.9.12",23,"Another unnecessary minus one.",null,"Delete \"minus one\" from the line.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Mickael Maman",null,68,"Yes","STMicroelectronics","Technical",105,"10.39.9.12",26,"is it interesting to modify Management PHY Configuration and Management MAC Configuration (i.e.  Management short term parameters) for each responder for O2M MMS ranging? We should not modify them in One-to-many Poll compact frame.",null,"list of change: Line 7 page 105, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\", in figure 95 remove Management PHY Configuration and Management MAC Configuration, remove line 6 and 7 page 106, add page 106 line 21 \" The Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\", in figure 97 remove Management PHY Configuration and Management MAC Configuration and remove line 6 and 7 page 107","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Rojan Chitrakar",null,129,"No","Huawei","Technical",106,"10.38.9.12",1,"NB channel Map field is 6 octets long, either the field here should be renamed to a different name or the 6-octet bitmap should be called something else (e.g., Full NB Channel Map).",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,586,"No","Self","Editorial",106,"10.38.9.12",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,130,"No","Huawei","Technical",106,"10.38.9.12",5,"Only the 6 octet version the NB channel Map field (10.38.9.3.7) is referenced.",null,"Add the other versions of the NB channel Map field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Pooria Pakrooh",null,1367,"No","Qualcomm","Technical",106,"10.38.9.12",5,"This could be lower and upper NB channel maps as well",null,"Change to \"per 10.38.9.3.7, 10.38.9.3.8 and 10.38.9.3.9\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,587,"No","Self","Editorial",106,"10.38.9.12",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,131,"No","Huawei","Technical",106,"10.38.9.12",19,"It is better to list the present fields that may be non-zero to avoid having to change the sentence if any new presence bit is added to the presence bitmap.",null,"change as:\n\"…, except that the fields other than the NB Channel Map Present field, the Management PHY Configuration Present field, the Management MAC Configuration Present field, the Ranging PHY Configuration Present field, the Ranging MAC Configuration Present field, the Start and End Slot\nIndices Present field, Block and Round Index Present field, and the Extended Presence Bitmap Present field shall all be set to zero.\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Mickael Maman",null,69,"Yes","STMicroelectronics","Technical",107,"10.38.9.12",1,"in Figure 97, how to define the presence of start slot index and end slot index fields?",null,"remove \"0/\" for the two fields or modify the size of presence bitmap to 1/2 in figure 94 ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,588,"No","Self","Editorial",107,"10.38.9.12",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,590,"No","Self","Technical",107,"10.38.9.12",1,"The slot index fields are limited to 8-bits because of the security, but here they are sent as 16-bit fields. ",null,"Change Start and End Slot Index fields to be one octet long.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Pooria Pakrooh",null,1368,"No","Qualcomm","Technical",107,"10.38.9.12",5,"This could be lower and upper NB channel maps as well",null,"Change to \"per 10.38.9.3.7, 10.38.9.3.8 and 10.38.9.3.9\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,589,"No","Self","Editorial",107,"10.38.9.12",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,591,"No","Self","Editorial",108,"10.38.9.12",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,593,"No","Self","Technical",108,"10.38.9.12",1,"The slot index fields are limited to 8-bits because of the security, but here they are sent as 16-bit fields. ",null,"Change Start Slot Index field to be one octet long.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,594,"No","Self","Technical",108,"10.38.9.12",5,"The slot index fields are limited to 8-bits because of the security, but here they are described as 16-bit fields. ",null,"Change Start Slot Index field to be one octet long.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Carlos Aldana",null,1015,"No","Meta Platforms","Technical",108,"10.38.9.13",17,"This frame keeps getting longer after every draft.  Let's limit the duration to 1ms.  Add text that says so.",null,"As in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,592,"No","Self","Editorial",108,"10.38.9.13",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,595,"No","Self","Technical",108,"10.38.9.13",25,"What is the point of including extra octets of zero when the frames are supposed to be compact. ",null,"Remove extra unneeded data.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,596,"No","Self","Editorial",109,"10.38.9.13",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,165,"No","Huawei","Editorial",109,"10.38.9.13",3,"There is an extra dot at the end of this line",null,"Remove this dot","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Bin Qian",null,166,"No","Huawei","Technical",109,"10.38.9.13",4,"The number of Octets occupied by Zero Padding should be 0/1/2/3 instead of 0/1/2/3/4",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Mickael Maman",null,71,"Yes","STMicroelectronics","Technical",109,"10.38.9.13",5,"in Figure 102,  the size of NB channel map is 0/2/5/6",null,"as in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Rojan Chitrakar",null,132,"No","Huawei","Technical",109,"10.38.9.13",5,"Is the NB channel Map field limited to 6 octets here?",null,"Add the other versions of the NB channel Map field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,597,"No","Self","Editorial",109,"10.38.9.13",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,598,"No","Self","Technical",109,"10.38.9.13",5,"The NB Channel Map has only lengths of 0 and 6, but there is no restriction for lengths of 2 or 5. ",null,"Either change 0/6 to 0/2/5/6 or explain why 2 and 5 octet versions are not allowed.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Pooria Pakrooh",null,1369,"No","Qualcomm","Technical",109,"10.38.9.13",5,"In Figure 102, change \"NB Channel Map\" field length to 0/2/5/6.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Pooria Pakrooh",null,1370,"No","Qualcomm","Technical",109,"10.38.9.13",11,"This could be lower and upper NB channel maps as well",null,"Change to \"per 10.38.9.3.7, 10.38.9.3.8 and 10.38.9.3.9\"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,599,"No","Self","Technical",109,"10.38.9.13",16,"What is the point of including padding when the frames are supposed to be compact. ",null,"Remove extra padding or add text explaining why the padding is required.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Mickael Maman",null,70,"Yes","STMicroelectronics","Technical",109,"10.39.9.13",7,"Management PHY Configuration and Management MAC Configuration shall not be short term parameters. Then we shall not modify them in One-to-many poll compact frame",null,"list of change: Line 7, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\", in figure 102 remove Management PHY Configuration and Management MAC Configuration, remove line 12 and 13","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,600,"No","Self","Editorial",110,"10.38.9.14",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,601,"No","Self","Editorial",110,"10.38.9.14",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1371,"No","Qualcomm","Technical",110,"10.38.9.14",10,"In Figure 105, change \"NB Channel Map\" field length to 0/2/5/6.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Mickael Maman",null,72,"Yes","STMicroelectronics","Technical",110,"10.38.9.14",11,"in Figure 105,  the size of NB channel map is 0/2/5/6",null,"as in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,602,"No","Self","Editorial",110,"10.38.9.14",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,603,"No","Self","Technical",110,"10.38.9.14",11,"The NB Channel Map has only lengths of 0 and 6, but there is no restriction for lengths of 2 or 5. ",null,"Either change 0/6 to 0/2/5/6 or explain why 2 and 5 octet versions are not allowed.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Rojan Chitrakar",null,133,"No","Huawei","Editorial",110,"10.38.9.14",16,"Align the sentence with other simillar sentences for consistency.",null,"The Presence Bitmap field is set as specified in 10.38.9.3.24, except that the Block and Round Index Present field and the Extended Presence Bitmap Present field shall both be set to zero. The encoding and meaning of the subsequent fields in the message content is identical to that of the Advertising Response Compact frame with Message Control field value of 0x10.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Libra Xiao",null,913,"No","NewRadio Technologies Co., Ltd.","Technical",110,"10.38.9.14","#13,#14,#15","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Mickael Maman",null,73,"Yes","STMicroelectronics","Technical",110,"10.39.9.14",16,"Management PHY Configuration and Management MAC Configuration shall not be short term parameters. Then we shall not modify them in One-to-many Resp compact frame",null,"list of change: Line 16, add\" except that the Management PHY Configuration present field and Management MAC Configuration present field shall be set to 0\", in figure 105 remove Management PHY Configuration and Management MAC Configuration.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,604,"No","Self","Editorial",111,"10.38.9.15",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,277,"No","MediaTek","Technical",111,"10.38.9.15",6,"In the last comment resolution process, there was a discussion of a corner case that if multiple responders choose to transmit O2M response in the same ranging sub-round in a contention-based O2M ranging, and the initiator receives one of them, and because the responding O2M poll frame’s IRK  only identifies the initiator, there could be multiple responders sending RSF fragments at the same time. It was concluded that the ranging procedure still works because the near responder’s first path and control/report message can be still be recognized by the initiator. \n\nHowever, in the above corner case, the O2M initiator report compact frame still uses initiator’s IRK and the far responder who has transmitted RSF and failed ctrl/report messages, could think the initiator report is for itself and get wrong ranging result.",null,"For one-to-many initiator report in a contention-based O2M ranging sub-round, the RPA hash should be calculated using the IRK of the responder winning the contention.","No",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Huan-Bang Li",null,1446,"Yes","NICT","Technical",111,"10.38.9.15",8,"replace 'Message Control field' by 'Message Content field'.",null,"make change.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,605,"No","Self","Editorial",111,"10.38.9.15",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,606,"No","Self","Editorial",111,"10.38.9.15",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,167,"No","Huawei","Technical",111,"10.38.9.15",21,"The description of the Round-trip Time One field and Round-trip Time Two field is not consist with that of the Round-trip time field in Line 13 ",null,"Adjust the description of the Round-trip Time One field and Round-trip Time Two field as the Round-trip Time field","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Libra Xiao",null,919,"No","NewRadio Technologies Co., Ltd.","Technical",111,"10.38.9.15","#13,#14,#15","Original text is :\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments \"\n\nIt should be clarified how to obtain the value of the Round-trip Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Round-trip Time parameter can be the cumulative or mean value of multiple RSFs and/or RIFs.",null,"\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Round-trip Time  should be the mean value of several Round-trip Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Jinjing"]
[null,null,"Tero Kivinen",null,607,"No","Self","Editorial",112,"10.38.9.16",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,134,"No","Huawei","Technical",112,"10.38.9.16",10,"Similar to the ADV-Poll, with the new Presence Bitmap format, the 4 variants can likely be combined in a single variant by either making the Initialization Slot Duration and Cap Duration fields mandatory or adding relevant presence bits for Initialization Slot Duration and Cap Duration.",null,"Consider combine the 4 variants in a single variant by  either making the Initialization Slot Duration and Cap Duration fields mandatory in all variant or adding relevant presence bits for Initialization Slot Duration and Cap Duration.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,610,"No","Self","Technical",112,"10.38.9.16",10,"As most of the Message Content formats are same as in Advertising Poll Compact Frame defined in 10.38.9.4, it would be better to just say that for message content fields of 0x00, 0x10, and 0x20 are described in the 10.38.9.4, and only cover differences here, i.e., message content field valus 0x21 and 0x30. ",null,"Remove duplicated text and add reference to 10.38.9.4.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,608,"No","Self","Editorial",112,"10.38.9.16",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Huan-Bang Li",null,1447,"Yes","NICT","Editorial",112,"10.38.9.16",18,"replace 'Figure 63' by 'Figure 111'.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,609,"No","Self","Editorial",112,"10.38.9.16",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Huan-Bang Li",null,1448,"Yes","NICT","Editorial",112,"10.38.9.16",22,"replace 'Figure 63' by 'Figure 112'.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,611,"No","Self","Editorial",113,"10.38.9.16",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Huan-Bang Li",null,1449,"Yes","NICT","Editorial",113,"10.38.9.16",4,"replace 'Figure 63' by 'Figure 113'.",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,612,"No","Self","Editorial",113,"10.38.9.16",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,168,"No","Huawei","Editorial",113,"10.38.9.16",7,"\"CAP\" should be \"Cap\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,613,"No","Self","Editorial",113,"10.38.9.17",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,614,"No","Self","Technical",113,"10.38.9.17",23,"If there is only one possible value for Message control field, it can be also omitted to make message more compact. ",null,"Remove message control field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Huan-Bang Li",null,1450,"Yes","NICT","Technical",113,"10.38.9.17",23," 'one of 0x00' is strange. Is there another value? Add another value if yes. Delete 'one of' if no.",null,"make change.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Li-Hsiang Sun",null,278,"No","MediaTek","Technical",113,"10.398.9.16",1,"With SMC TLVs before advertising data, the receiver would not be able to parse the length of either field",null,"reverse the order of advertising data and SMC TLVs","No",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,615,"No","Self","Editorial",114,"10.38.9.18",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Hong Won Lee",null,1412,"No","LG Electronics","Technical",114,"10.38.9.18",15,"It is beneficial to add more values to the Status field in the Public Start of Ranging Compact frame to indicate whether the public address of a responder is duplicated or not. This scenario can be one of the error cases for public initialization and session setup",null,"Add new status values such as \"Public Address Duplication\", \"Public Address Duplication with New Address\", and so on in Table 16. The behavior of the added status values should be described in sub-clause 10.38.9.18","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Hongwon"]
[null,null,"Tero Kivinen",null,616,"No","Self","Editorial",114,"10.38.9.19",22,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,621,"No","Self","Editorial",115,"10.38.9.20.1",1,"There is Table 18 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,618,"No","Self","Editorial",115,"10.38.9.20.1",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,617,"No","Self","Editorial",115,"10.38.9.20.1",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,620,"No","Self","Editorial",115,"10.38.9.20.2",1,"There is Table 19 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Huan-Bang Li",null,1451,"Yes","NICT","Editorial",115,"10.38.9.20.2",19,"replace 'has a Message Control field value is 0x00' by 'has a Message Control field value of 0x00'",null,"make change.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,619,"No","Self","Editorial",115,"10.38.9.20.2",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,622,"No","Self","Technical",115,"10.38.9.20.2",21,"The Common Info field has length of 2/4, but I think it is always 4 octets long. ",null,"Change 2/4 to 4.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Bin Qian",null,169,"No","Huawei","Editorial",116,"10.38.9.20.2",2,"“Number of UWB Per Session Info\" field should \"Number of UWB Per-Session Info\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,624,"No","Self","Editorial",116,"10.38.9.20.2",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,626,"No","Self","Technical",116,"10.38.9.20.2",4,"There is no point of saying that for one bit field other values than zero and one are reserved. ",null,"Remove \"Other values are reserved\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,623,"No","Self","Editorial",116,"10.38.9.20.2",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,170,"No","Huawei","Technical",116,"10.38.9.20.2",19,"According to the extended channels in 16.4.1.2, 4 bits Channel Number field is not enough",null,"Extend all Channel Number field to 7 bits in this sub-clause","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,625,"No","Self","Editorial",116,"10.38.9.20.2",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"B. Rolfe",null,1341,"Yes","BCA","Technical",116,"10.38.9.20.2 ",15,"\"may not\" is never correct in an IEEE standard. Here we're trying to say not all fields are included in all frames.",null," change to: not all  fields are included in all  frames",null,null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,627,"No","Self","Editorial",117,"10.38.9.20.2",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,628,"No","Self","Editorial",117,"10.38.9.20.2",25,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,629,"No","Self","Editorial",118,"10.38.9.20.2",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,630,"No","Self","Editorial",118,"10.38.9.20.3",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,631,"No","Self","Editorial",118,"10.38.9.20.3",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Zhepeng Ma",null,201,"Non-Voter","Calterah Semiconductor ","Editorial",118,"10.38.9.20.3 ",24,"Wording adjustment for \"Number of UWB Per Session Info\" in Figure 125",null,"Number of UWB Per-Session Info","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1234,"No","Qorvo","Technical",119,"10.38.9.20.3",1,"Seems like only 1 bit is needed for \"the UWB AP Type field\"",null,"Consider changing to a single bit. And maybe saving a whole octet since that would leave 8 bits reserved.","Yes","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Tero Kivinen",null,634,"No","Self","Technical",119,"10.38.9.20.3",7,"Next UWB AP field is present only when UWB AP Type field is zero or one, but all other values on the UWB AP Type field are reserved, so the Next UWB AP field is present always for all currently defined frames. ",null,"Mark Next UWB AP field to be there always, i.e., mark its length to 2 and mark Common info field length to 4. Remove text about it being present only when non reserved values are used.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1235,"No","Qorvo","Technical",119,"10.38.9.20.3",7,"\"The Next UWB AP field, should state this as a start to start relationship, as is done for the Next NB AP field in the NB Acquisition Compact frame.",null,"Chane definition to say it is the time \"from the start of current UWB Acquisition Compact Frame to the start of the next UWB Acquisition Compact frame\".","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Billy Verso",null,1236,"No","Qorvo","Technical",119,"10.38.9.20.3",7,"This says \"which is present when the UWB AP Type field value is either zero or one\", but looking at the definition of \"UWB AP Type field\" those are the only allowed values, which means this field always present.",null,"Delete \"which is present when the UWB AP Type field value is either zero or one\". And change \"Octets: 0/2\" in Figure 125 to \"Octets: 2\" since the field is always present,","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Zhepeng Ma",null,202,"Non-Voter","Calterah Semiconductor ","Technical",119,"10.38.9.20.3 ",2,"For UWB AP type, one bit should be enough, if no other clear potential type, the UWB AP type is recommended to be one bit, which is same as NB AP type in Figure 119",null,"one bit for UWB AP Type","No","Accepted",null,"NEWFR",null,"DONE"]
[null,null,"Alex Krebs",null,1399,"No","Apple","Technical",119,"10.38.9.21",19,"This is an encrypted report, that is not secure e.g. against the attacks previously presented & discussed to/with the group.",null,"Rename this and all following relevant chapters and messages from \"secure\" to \"encrypted\" and change the design such that it adds protection against the attacks presented in 22/410r1 and 23/274r0.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1237,"No","Qorvo","Technical",119,"10.38.9.21",22,"The four Secure Report messages have similar generic format. Each begins with an RPA Hash and a Message Control Octet, the latter of which is a sparse set of values.  Seems we have an opportunity to use a common Compact Frame ID field value for all of these saving on Compact Frame ID space over half of which are used up already.",null,"Change to single \"Secure Report\" ID in Table 1, and use the Message Control field (octet) to identify the meaning and encoding for the different flavours of secure report: One-to-one Initiator, One-to-one Responder, One-to-many Initiator and One-to-many Responder.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,632,"No","Self","Editorial",119,"10.38.9.21",23,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1238,"No","Qorvo","Technical",119,"10.38.9.21",23,"How does the MAC receiving this frame know what size the MIC is, i.e. can it tell the difference between a longer MIC or a Shorter mic with passthrough data which it says \"presence can be inferred from the frame length\".",null,"Consider if we need something in MHR to indicate MIC length","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,635,"No","Self","Technical",119,"10.38.9.21",25,"If there is only one possible value for Message control field, it can be also omitted to make message more compact. ",null,"Remove message control field.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,633,"No","Self","Editorial",119,"10.38.9.21",28,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,638,"No","Self","Technical",120,"10.38.9.21",2,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Billy Verso",null,1239,"No","Qorvo","Technical",120,"10.38.9.21",2,"In the secure frames any passthrough data should be encrypted. Securing the MAC payload, i.e. data from the upper layer, is a specified functionality of the 15.4 MAC.  Data confidentiality and authenticity should apply to the passthrough data.",null,"Make it so secure reports encrypt the passthrough data, (but probably not the length though).","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Libra Xiao",null,914,"No","NewRadio Technologies Co., Ltd.","Technical",120,"10.38.9.21","#22,#23,#24","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Libra Xiao",null,920,"No","NewRadio Technologies Co., Ltd.","Technical",120,"10.38.9.21","#3,#4,#5","Original text is :\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments \"\n\nIt should be clarified how to obtain the value of the Round-trip Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Round-trip Time parameter can be the cumulative or mean value of multiple RSFs and/or RIFs.",null,"\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Round-trip Time  should be the mean value of several Round-trip Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,636,"No","Self","Editorial",120,"10.38.9.22",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,637,"No","Self","Editorial",120,"10.38.9.22",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,639,"No","Self","Technical",120,"10.38.9.22",21,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,640,"No","Self","Editorial",121,"10.38.9.22",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1372,"No","Qualcomm","Technical",121,"10.38.9.22",1,"In Figure 130, change \"NB Channel Map\" field length to 0/2/5/6.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Rojan Chitrakar",null,135,"No","Huawei","Editorial",121,"10.38.9.22",4,"Align the sentence with other simillar sentences for consistency.",null,"The Presence Bitmap field is set as specified in 10.38.9.3.24, except that the Block and Round Index Present field and the Extended Presence Bitmap Present field shall both be set to zero. The encoding and meaning of the subsequent fields in the message content is identical to that of the Advertising Response Compact frame with Message Control field value of 0x10.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,643,"No","Self","Technical",121,"10.38.9.22",4,"Is there a reason why presence bitmap, NB Channel Map etc are not private payloads, i.e., not encrypted. ",null,"Move those other fields to be private or add warning here that they are not encrypted.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,642,"No","Self","Technical",121,"10.38.9.22",7,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Bin Qian",null,171,"No","Huawei","Editorial",121,"10.38.9.22",12,"\"one-to-one Secure REPORT (Responder) Compact frame\" should be \"One-to-one Responder Secure Report Compact frame\"",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Libra Xiao",null,915,"No","NewRadio Technologies Co., Ltd.","Technical",121,"10.38.9.22","#8,#9,#10","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,641,"No","Self","Editorial",121,"10.38.9.23",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,644,"No","Self","Editorial",122,"10.38.9.23",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,646,"No","Self","Technical",122,"10.38.9.23",4,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,645,"No","Self","Editorial",122,"10.38.9.23",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,647,"No","Self","Technical",122,"10.38.9.23",13,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Bin Qian",null,172,"No","Huawei","Technical",122,"10.38.9.23",14,"The description of the Round-trip Time One field and Round-trip Time Two field is not consist with that of the Round-trip time field in Line 5",null,"Adjust the description of the Round-trip Time One field and Round-trip Time Two field as the Round-trip Time field","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Libra Xiao",null,921,"No","NewRadio Technologies Co., Ltd.","Technical",122,"10.38.9.23","#5,#6,#7","Original text is :\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments \"\n\nIt should be clarified how to obtain the value of the Round-trip Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Round-trip Time parameter can be the cumulative or mean value of multiple RSFs and/or RIFs.",null,"\"The Round-trip Time field value is an unsigned integer that reports the time difference, measured at the initiator, between the RMARKERs of the initiator's MMS fragments and the responder's MMS fragments For the multiple RSFs and RIFs of the UWB MMS ranging phase,the value of  the Round-trip Time  should be the mean value of several Round-trip Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,648,"No","Self","Editorial",123,"10.38.9.24",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,649,"No","Self","Editorial",123,"10.38.9.24",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,651,"No","Self","Technical",123,"10.38.9.24",11,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,650,"No","Self","Editorial",123,"10.38.9.24",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1373,"No","Qualcomm","Technical",123,"10.38.9.24",18,"In Figure 136, change \"NB Channel Map\" field length to 0/2/5/6.",null,"As in the comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Libra Xiao",null,916,"No","NewRadio Technologies Co., Ltd.","Technical",123,"10.38.9.24","#12,#13,#14","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Carlos Aldana",null,986,"No","Meta Platforms","Technical",124,"10.38.10.1",10,"The following 802.11 20 MHz channel center frequencies are likely to have a lot of traffic (probe request, beacons from 6GHz only APs, and probe responses) and should be removed from the initial macMmsNbChannelAllowList to prevent ranging outages: 5975, 6055, 6135, 6215, 6295, and 6375 MHz ",null," Change text in column “Default” for macMmsNbChannelAllowList to “1-65, 74-97, 106-129, 138-161, 170-193, 202-225, 234-249”","Yes",null,null,"MMS",null,"ASSIGNED",null,"Rojan"]
[null,null,"Bin Qian",null,173,"No","Huawei","Technical",124,"10.38.10.1",16,"The range of macMmsConotrolPhaseMode and macMmsReportPhaseMode is 1-8, 14, 15",null,"Change the range to 1-8, 14, 15","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,652,"No","Self","Editorial",124,"10.38.10.1",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,653,"No","Self","Technical",124,"10.38.10.1",16,"The macMmsNbChannelMap description has wrong reference. That reference is for macMmsNbChannelAllowList. ",null,"Fix the reference to 10.38.9.3.7. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,654,"No","Self","Technical",124,"10.38.10.1",16,"The macMmsNbChannelAllowList is directly constructed from the macMmsNbChannelMap, so why store it in the pib separately? ",null,"Remove macMmsNbChannelAllowList as it is not possible to construct macMmsNbChannelMap from the macMmsNbChannelAllowList without loosing information, but it is possible to do the reverse, and the section 10.38.9.3.7 describes how to do that.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,655,"No","Self","Technical",124,"10.38.10.1",16,"Why is the macMmsNbChannelMap describes in this kind of encoded format. It would be much easier if the PIB entries would actually have the separate fields (macMmsNbChannelsLow, macMmsNbChannelsUnii3, macMmsNbChanneslHigh, macMmsNbChannelsUnii5) and the macMmsNbChannelMap would be constructed from them when needed.",null,"As specified in comment","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,656,"No","Self","Technical",124,"10.38.10.1",16,"There is no point of using Prng with Seed if the seed is going to be only one octet long. The problem with Prng is that it can generate non-optimal distribution of channels, and as there is no security reasons for using Prng using some kind of permutation function that picks channel numbers intelligently would be better. ",null,"What is the point of using Prgn here? Wouldn't some kind of permutation function be better. ","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1005,"No","Meta Platforms","Technical",124,"10.38.10.1",16,"There is no normative text associated with macMmsNbChannelMap variable",null,"Please add","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Billy Verso",null,1240,"No","Qorvo","Technical",124,"10.38.10.1",16,"Not sure everything in this table is actually configuring MAC behaviour.  Next higher layer and MAC roles are a bit blurred I think, some of these parameters while a necessary part of the protocol definition are perhaps not actually affecting MAC behaviour and should more properly be in NHL domain.",null,"Consider which are MAC and which not and revised table accordingly, and used of these elsewhere,","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1397,"No","Apple","Technical",124,"10.38.10.1 ",16,"ChannelAllowList 0-249 is not a good default configuration, as it interferes with the initialization channel and possibly licensed spectrum.",null,"Change default value to 4-49, 58-249.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Rojan Chitrakar",null,136,"No","Huawei","Editorial",124,"10.38.9.24",1,"Align the sentence with other simillar sentences for consistency.",null,"The Presence Bitmap field is set as specified in 10.38.9.3.24, except that the Block and Round Index Present field and the Extended Presence Bitmap Present field shall both be set to zero. The encoding and meaning of the subsequent fields in the message content is identical to that of the Advertising Response Compact frame with Message Control field value of 0x10.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,658,"No","Self","Technical",124,"10.38.9.24",1,"Is there a reason why presence bitmap, NB Channel Map etc are not private payloads, i.e., not encrypted. ",null,"Move those other fields to be private or add warning here that they are not encrypted.","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Tero Kivinen",null,657,"No","Self","Technical",124,"10.38.9.24",8,"I would assume that the passthrough data is exactly something that would need to be encrypted, but currently it is not. ",null,"Either mark passthrough field as being private payload field, or add warning here that its content is not encrypted.","Yes",null,"Doc 15-24-0381-00-04ab-proposed-resolution-for-security-pt-data.docx","NEWFR",null,"ASSIGNED",null,"Rojan"]
[null,null,"Libra Xiao",null,917,"No","NewRadio Technologies Co., Ltd.","Technical",124,"10.38.9.24","#9,#10,#11","Original text is :\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  \"\n\nIt should be clarified how to obtain the value of the Reply Time parameter in the UWB MMS ranging phase with multiple RSFs and/or RIFs (as shown in the example in Figure 36), as the value of  the Reply Time parameter can be the cumulative or  mean value of multiple RSFs and/or RIFs.",null,"\"The Reply Time field value is an unsigned integer reporting the time difference, measured at the responder, between the RMARKERs of the MMS fragments received from the initiator and the MMS fragments transmitted by the responder.  For the multiple RSFs and/or RIFs of the UWB MMS ranging phase,the value of  the Reply Time  should be the mean value of several Reply Time parameters measured at the responder. \"","Yes",null,null,"NEWFR",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,659,"No","Self","Technical",125,"10.38.10",1,"In the macMmsReportPhaseMode the description says that Value 14 selects xxx, but range does not allow value 14. ",null,"Remove description of value 14 or add 14 to range.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,660,"No","Self","Editorial",125,"10.38.10",1,"There is empty line at the end of table. ",null,"Remove empty line.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,661,"No","Self","Technical",125,"10.38.10",1,"The macMmsRangingSlotDuration is missing a range. ",null,"Add range to the macMmsRangingSlotDuration.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,662,"No","Self","Technical",125,"10.38.10",1,"The macMmsRangingRoundDuration is missing a range. ",null,"Add range to the macMmsRangingRoundDuration. Also I assume there is relation between slot duration and round duration, describe that relation in description.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,663,"No","Self","Technical",125,"10.38.10",1,"The macMmsRangingBlockDuration is missing a range. ",null,"Add range to the macMmsRangingBlockDuration. Also I assume there is relation between round duration and round duration, describe that relation in description.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,74,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"Value 14 is missing in the range of macmmsReportPhaseMode",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,75,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"Poll and Resp slot are mandatory. Then the range of macMmsRcpPollNslots and macMmsRcpRespNslots shall start at 1",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,76,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"according to management MAC configuration (line 2 page 86), macMmsRangingSlotDuration is 300*(N+1) 0<=N<=7 RSTU.",null,"add \"300*(N+1) 1<=N<=7\" in range","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,77,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"range of ranging round duration is missing",null,"add \"1-255\" in range and change RSTU to ranging slot","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,78,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"range of ranging block duration is missing",null,"add \"1-255\" in range and change RSTU to ranging round","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Mickael Maman",null,79,"Yes","STMicroelectronics","Technical",125,"10.38.10.1",1,"Rp duration is between 0 and 4095 according to section 10.38.9.3.12",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Li-Hsiang Sun",null,244,"No","MediaTek","Technical",125,"10.38.10.1",1,"The default value for macMmsRangingBlockDuration seems much longer than the 100ms typicaly assumed in 4ab discussions\n ",null,"Revise the default value if necessary","No",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,664,"No","Self","Technical",125,"10.38.10.1",1,"The macMmsRpDuration max value is wrong. ",null,"It is 12 bit field thus max value is 4095, not 4096. Change 4096 to 4095.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Riku Pirhonen",null,959,"No","NXP Semiconductors","Technical",125,"10.38.10.1",1,"Add MAC PIB attribute macMmsExtendedRpDuration to Table 20 on the row after MacMmsRpDuration",null,"macMmsExtendedRpDuration, Integer, 0 - 3, 0 = Interleaved ranging phase, 1 = Non-interleaved ranging phase of double RpDuration, 2 = Non-interleaved ranging phase of triple RpDuration, 3 = reserved, Default 0","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Carlos Aldana",null,994,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"macMmsNbInitChannel should be carefully selected and not have a wide range from 0-249 to prevent it from being interfered with.  Change it so that it covers the union of the following 2 sets : 1) from 5725 to 5732.5 (0 to 2) MHz 2) from 5835 to 5850 MHz (44 to 49)",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1006,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"In description of macMmsResportPhaseMode, values 1-9 are referred to, but Table 58 only has values 1-8.  Please fix.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1007,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"In description of macMmsResportPhaseMode, values 14 is referred to, but is not listed in Range.    Please fix.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1008,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"The range of both macMmsRcpPollNSlots and macMmsRcpRespNSlots is quite large (up to 7.5ms when slot duration is set to 0.5ms and 15 ms when slot duration is set to 1ms).  Consider limiting duration to 1ms.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1009,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"In decription of macMmsNbInitMode, the Range is 1-9, but Table 58 only has 8 values.  Please fix.",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1010,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"There is no normative text associated with macMmsRangingSlotDuration, macMmsRangingRoundDuartion, and macMmsRangingBlockDuration variables",null,"Please fix.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carlos Aldana",null,1011,"No","Meta Platforms","Technical",125,"10.38.10.1",1,"in Description of macMmsXReportNslots, there is text that says \"2 slots =1ms\".  That is not necessarily the case, as it depends on the value of macMmsRangingSlotDuration.  Please fix",null,"As in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1374,"No","Qualcomm","Technical",125,"10.38.10.1",1,"In Table 20, specify ranges of value for \"Ranging round duration\" and \"ranging block duration\"",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Pooria Pakrooh",null,1375,"No","Qualcomm","Technical",125,"10.38.10.1",1,"In Table 20, specify Round and block duration in units of slot and round duration respectively, nor RSTU.",null,"As in the comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Alex Krebs",null,1398,"No","Apple","Technical",125,"10.38.10.1 ",1,"UwbChannel range 1-16",null,"Change range to include extended channels 1-113 as defined in 16.4.1.2","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Tero Kivinen",null,665,"No","Self","Technical",125,"10.38.11",2,"This whole clause looks more like a clause that should be inside the clause 16, not in 10.38. ",null,"Move to clause 16.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Alex"]
[null,null,"Carl Murray",null,882,"No","Qorvo","Editorial",126,"10.38.11.2",4,"typo",null,"Replace\n\n\"are given in given in\"\n\nby\n\n\"are given in\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Huan-Bang Li",null,1452,"Yes","NICT","Editorial",126,"10.38.11.2",4,"redundant 'given in'",null,"delete one.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tushar Patel",null,1424,"Yes","LitePoint","Editorial",126,"10.38.11.2",5,"Line #5 - 6 reads \"For each separate network, a subset may be chosen limit\n6 interference, e.g., keeping the greatest common divisor among the MMRS symbol periods small\"",null,"Proposing to change line #6 as \"For each separate network, a subset may be chosen to limit\n6 interference, e.g., keeping the greatest common divisor among the MMRS symbol periods small.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,666,"No","Self","Editorial",126,"10.38.11.2",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,174,"No","Huawei","Technical",126,"10.38.11.2",15,"What does it mean of the last sentence  ",null,"As in the comment","Yes",null,null,"MMSNB",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Carl Murray",null,883,"No","Qorvo","Editorial",126,"10.38.11.2",15,"typo",null,"Replace\n\n\"in Table 23 and Table 22.\"\n\nby\n\n\"in Table 22 and Table 23.\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Zhepeng Ma",null,200,"Non-Voter","Calterah Semiconductor ","Editorial",126,"10.38.11.2 ",4,"Wording mistake for “This set of combinations is recommended for HRP-ARDEV. The sequences selected by each code index are given in given in Table 63.”",null,"This set of combinations is recommended for HRP-ARDEV. The sequences selected by each code index are given in Table 63.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carl Murray",null,884,"No","Qorvo","Technical",127,"10.38.11.3",2,"Ambiguous statement \"These combine a larger gap size with a smaller MSR.\"\n\nLarger than what, smaller than what?\nNote that for some of the specified configurations the MSR is larger than the gap size. ",null,"Remove statement","Yes",null,null,"MMSNB",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Tero Kivinen",null,667,"No","Self","Editorial",127,"10.38.11.3",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pooria Pakrooh",null,1376,"No","Qualcomm","Technical",127,"10.38.11.4",8,"Change \"mandatory set of configs for UWB MMS\" to \"mandatory set of configs for NBA UWB MMS\"",null,"Change \"mandatory set of configs for UWB MMS\" to \"mandatory set of configs for NBA UWB MMS\"","Yes",null,null,"MMSNB",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Jarek Niewczas",null,279,"No","Qorvo","Technical",127,"10.38.11.4",12,"the purpose of variable gap length was to reduce interference. Using the same gap length for all mandatory configs contradicts that purpose.  remove column \"MMRS config\"",null,"Remove \"MMRS Config\" columns from Table 23, and add below the\n statement: \"For the Mixed MMS configurations of Table 23, the device\n shall support MMRS Config Set numbers 21 to 49 as given in\n Table 16-9. \"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Tero Kivinen",null,668,"No","Self","Editorial",127,"10.38.11.4",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,885,"No","Qorvo","Technical",127,"10.38.11.4",12,"The mandatory configurations given in Table 23 are very limited. For example they only use one MMRS Config Set #. Historically mandatory parameters are the only parameters that multiple vendors can rely on to interoperate.  For example the mandatory set all use the same gap size but variable gap size is what gives interference protection.",null,"Expand the number of mixed MMS configuration sets to include a  broader range of configurations sets from Table 21. ","Yes",null,null,"MMSNB",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Tero Kivinen",null,671,"No","Self","Technical",128,"10.38.12",3,"This whole clause looks more like a clause that should be inside the clause 16, not in 10.38. ",null,"Move to clause 16.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Tero Kivinen",null,669,"No","Self","Editorial",128,"10.38.12",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,670,"No","Self","Editorial",128,"10.39.1",11,"This is not first use of CIR, do not expand here. ",null,"Do not expand CIR here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Aniruddh Rao Kabbinale",null,219,"Yes","Samsung Electronics","Technical",128,"10.39.1",14,"The nomenclature is not in accordance with nomenclature used for ERDEV in 15.4z. Controller, controlee, initator and responder should be the nomenclature",null,"Define controller, define controlee, remove transmitter and receiver nomenclatures","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,220,"Yes","Samsung Electronics","General",128,"10.39.1",15,"The definition of sensing initiator is not clear. It is not clear what does \"initiating RF session\" means. Clarify what it means.",null,"Modify definition of sensing initiator as follows:an SDEV that initiates an RF sensing session with one or more other SDEVs by sending/transmitting PPDUs to enable channel estimation for sensing.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,221,"Yes","Samsung Electronics","General",128,"10.39.1",16,"The definition of sensing responder is not clear. It is not clear what \"responds\" means. Clarify what it means",null,"Modify defitinion of sensing responder as follows: Ans SDEV that responds to a sensing initator by receiving PPDU from sensing initiator, performs channel estimation and may report CIR to initiator.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,222,"Yes","Samsung Electronics","Technical",128,"10.39.1",24,"Sensing initiator is the one who transmits always.",null,"Remove the part of the line \"For the cases that the sensing initiator is the sensing transmitter\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,223,"Yes","Samsung Electronics","Technical",129,"10.39.1",1,"It is not clear by what is meant by \"Initator is a sensing receiver\". Since it is initiator who sends the sensing PPDUs and may receive CIR report from responder. However, controller can take up roles of sensing initiator or responder",null,"Change as follows\" Bistatic sensing - where controller is the sensing responder.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,224,"Yes","Samsung Electronics","Technical",129,"10.39.1",2,"It is not clear by what is meant by \"Initator is a sensing transmitter\". Since it is the case always. However, controller can take up roles of sensing initiator or responder",null,"Change as follows\" Bistatic sensing - where controller is the sensing initiator.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,225,"Yes","Samsung Electronics","Technical",129,"10.39.1",3,"It is not clear by what is meant by \"Initator is a sensing receiver\". Since it is initiator who sends the sensing PPDUs and may receive CIR report from responder. However, controller can take up roles of sensing initiator or responder",null,"Change as follows \" Multi static sensing, where controller is the responder\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,226,"Yes","Samsung Electronics","Technical",129,"10.39.1",4,"It is not clear by what is meant by \"Initator is a sensing transmitter\". Since it is the case always. However, controller can take up roles of sensing initiator or responder",null,"Change as follows: \" Multistatic sensing, where controller is the initiator, supporting scheduling of CIR reports from multiple responders\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pablo Corbalán Pelegrín",null,1312,"No","NXP Semiconductors","Editorial",129,"10.39.2",6,"To be consistent with the other modes, shall we briefly explain what sensing by proxy means? Additionally we may add a reference to the section explaining Sensing by Proxy.",null,"Explain sensing by proxy: Sensing by proxy (10.39.5), where an SDEV requests another SDEV to do sensing on its behalf.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1241,"No","Qorvo","Technical",129,"10.39.4",23,"We are missing a subclause about the control of sensing  from the next higher layer perspective and how it all hangs together.  I think the interactions should be based on the thoughts captured in 15-23-0208. It should employ a message sequence chart to illustrate the interactions. ",null,"I will prepare a submission to cover this, for consideration to be inserted in a suitable place in 10.39","Yes",null,null,"SENS",null,"ASSIGNED",null,"Billy"]
[null,null,"Aniruddh Rao Kabbinale",null,227,"Yes","Samsung Electronics","Technical",129,"10.39.4.2",28,"Capabilities are not exchanged between initiator and responder but between controller and controlee",null,"Change initiator to controller and responder to controlee","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carl Murray",null,886,"No","Qorvo","Editorial",129,"10.39.4.2",29,"May be better to rephrase the following text to emphasize that multiple channels may be used \n\n\"including some or all the following: sensing mode (10.39.2), packet format (16.2.1), CIR report parameters (10.39.6.2), operating channel, and the use of frequency stitching.\"",null,"Change to \"including some or all the following: sensing mode (10.39.2), packet format (16.2.1), CIR report parameters (10.39.6.2), the use of frequency stitching and operating channel(s).\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,672,"No","Self","Editorial",129,"10.39.4.3",1,"There is Figure 137 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Mickael Maman",null,80,"Yes","STMicroelectronics","Technical",129,"10.39.4.3",37,"move \"The first sensing slot…as defined in 10.29.1.5)\" in section 10.34.4.4",null,"as in comment","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Wenzheng Li",null,196,"Non-Voter","Calterah Semiconductor ","Editorial",130,"10.39.4.3",9,"Wording mistake for “withing the same ranging block”",null,"within the same ranging block","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,673,"No","Self","Editorial",130,"10.39.4.3",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,675,"No","Self","Editorial",130,"10.39.4.4",1,"There is Figure 138 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,674,"No","Self","Editorial",130,"10.39.4.4",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Aniruddh Rao Kabbinale",null,228,"Yes","Samsung Electronics","Technical",130,"10.39.4.4",19,"Sensing packets are sent by sensing initiator only. Responders only process CIR and may report to initiator",null,"Remove the part \" and/or sensing responders\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carl Murray",null,887,"No","Qorvo","Editorial",131,"10.39.4.5",6,"Typo",null,"Replace \"SDEV\" with \"An SDEV\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1313,"No","NXP Semiconductors","Editorial",131,"10.39.4.5",7,"These values are not always included in the Processed Target Feature Report Ies (only those set as present). Therefore, we may want to change \"…, which include\" to \"…, which may include\".",null,"which may include","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,81,"Yes","STMicroelectronics","Technical",131,"10.39.4.6",12,"section 10.39.4.6 should be 10.39.4.5.1",null,"as in comment","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,677,"No","Self","Editorial",131,"10.39.4.6.1",1,"There is Figure 139 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Aniruddh Rao Kabbinale",null,229,"Yes","Samsung Electronics","Editorial",131,"10.39.4.6.1",17,"\"The HRP-SDEV shall support the\nearliest detect CIR tap as the reference tap\" This should be applicable in general to SDEV and not particularly to HRP-SDEV",null,"change HRP-SDEV to SDEV","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,678,"No","Self","Editorial",131,"10.39.4.6.1",17,"This is first use of the HRP-SDEV, expand here. ",null,"Expand HRP-SDEV here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carl Murray",null,888,"No","Qorvo","Technical",131,"10.39.4.6.1",19,"Figure 139 does not unambiguously indicate what the BMoffset and BMlength are. \n\nFor example it could be interpreted that the BMoffset =2 and BMlength =3. However in this case a BMlength of 3 has 4 taps\n\n",null,"Specify the values of BMoffset and BMlength in figure 139","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,676,"No","Self","Editorial",131,"10.39.4.6.1",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1242,"No","Qorvo","Technical",132,"10.39.4.6.2",11,"Line 11 ends in \":\" so I expect a dash list following it but it is just plain paragraphs, although the blank line #20 suggests that the list should be just the two paragraphs before.",null,"Make two paragraphs into two dash-bullets and delete the blank line?","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carl Murray",null,889,"No","Qorvo","Technical",132,"10.39.4.6.2",16,"The following text is ambiguous as it refers to the signal bandwidth - better to refer to the channel bandwidth\n\n\"The oversampling ratio is defined as the ratio of the CIR tap sampling rate to the signal bandwidth. For the frequency stitching feature, when the CIR of an effective larger bandwidth is obtained by an SDEV, the oversampling ratio is defined with respect to the aggregated bandwidth.\"",null,"Change to\n\n\"The oversampling ratio is defined as the ratio of the CIR tap\nsampling rate to the channel bandwidth. For the frequency stitching feature, when the CIR of an effective larger bandwidth is obtained by an SDEV, the oversampling ratio is defined with respect to the aggregated channel bandwidth.\"","Yes","Accepted","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Carl Murray",null,890,"No","Qorvo","Technical",132,"10.39.4.6.2",21,"There are no in-phase or quadrature taps. Both in-phase and quadrature are components of a tap.",null,"Replace the text starting in line 21 and ending on line 24 as follows or similar\n\n\n\"For each receive chain, the CIR measurement report shall be represented using a 16-bit signed value for the in-phase component of each CIR tap, and a 16-bit signed value for the quadrature component of each CIR tap. An SDEV may optionally represent the CIR measurement report using 10-bit, 12-bit, or 14-bit signed values separately for the in-phase component and quadrature component of each CIR tap value.\"","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Li-Hsiang Sun",null,245,"No","MediaTek","Technical",132,"10.39.4.6.2",31,"whether the alpha is the same as the Normalization Factor in CIR report?",null,"If they are the same, whether the description here can explicitly indicate that","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,679,"No","Self","Editorial",133,"10.39.4.6.3",1,"There is Figure 140-142 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Li-Hsiang Sun",null,247,"No","MediaTek","Technical",133,"10.39.4.6.3",10,"Where the measurement ID is assigned?",null,"Add in 10.39.4.2 that measurement ID is assigned in session setup phase","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pablo Corbalán Pelegrín",null,1314,"No","NXP Semiconductors","Editorial",133,"10.39.4.6.3",16,"Remove one \"in\": … as described in in ",null,"as described in ","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li Ma",null,203,"No","MediaTek","Technical",133,"10.39.4.6.3",22,"If Receive Report (RR) is compressed, and the RRD field only be present in the first part of Receive Report and not the second part , how does a receiver which only receives the second part knows what it receives contains a whole RR or just a second part of a RR",null,"Add in Report Identity Ctrl, or Receive Report Ctrl an indication whether the RR is complete,a 1st part  or a 2nd part.\n\nAlternatively, move the reserved bits of Receive Report Description (RRD) can be moved to the front, and 1 bit can be used for the indication whether the RR is complete, a 1st part  or a 2nd part,  and RRD is included in each part of a receive report","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,248,"No","MediaTek","Technical",133,"10.39.4.6.3",22,"If Report is compressed, and the RRD field only is present in the first part of Receive Report and not the second part , how does a receiver who only receives the second part knows what it receives contains a whole RR or just a second part of a RR",null,"Add in Report Identity Ctrl, or Receive Report Ctrl an indication whether the RR is complete,a 1st part  or a 2nd part.\n\nAlternatively, move the reserved bits of Receive Report Description (RRD)  to the front, and 2 bits can be used for the indication whether the RR is complete, a 1st part  or a 2nd part,  and RRD is included in each part of a receive report","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1243,"No","Qorvo","Technical",133,"10.39.4.6.3",22,"\"shall only\" is not good, and second \"present\" is not needed either.",null,"Change to \"shall be present in the first part of the receive\nreport and not in the second part.\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,680,"No","Self","Editorial",134,"10.39.4.6.3",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,137,"No","Huawei","Technical",134,"10.39.4.6.3",6,"\"… frame, the v is fragmented as described above.\"\nv should be \"Receive Report Lists field\"",null,"replace \"v\" with \"Receive Report Lists field \"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Bin Qian",null,175,"No","Huawei","Technical",134,"10.39.4.6.3",6,"What is the meaning of v?",null,"Specify the meaning of v","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,249,"No","MediaTek","Editorial",134,"10.39.4.6.3",6,"not sure what is v",null,"clarify v","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carl Murray",null,891,"No","Qorvo","Editorial",134,"10.39.4.6.3",6,"It looks like the is a typo in this line \"the v is fragmented as described above\"",null,"Replace \"v\" with appropriate text","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,681,"No","Self","Editorial",134,"10.39.4.6.3",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,682,"No","Self","Editorial",135,"10.39.4.6.3",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1244,"No","Qorvo","Editorial",135,"10.39.4.6.3",3,"blank line",null,"delete it","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Aniruddh Rao Kabbinale",null,230,"Yes","Samsung Electronics","Editorial",135,"10.39.4.7",5,"Generic wording \"UWB devices\" used for SDEV",null,"change UWB devices to SDEV","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,250,"No","MediaTek","Technical",135,"10.39.5.1",10,"sensing requesting device is a controllee associating to a controller. The controller (sensing initiator) does not initiating SBP setup and does not need to know controllee’s SBP capability",null,"as in comment","No","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Li-Hsiang Sun",null,251,"No","MediaTek","Technical",136,"10.39.5.3",8,"If the sensing requesting device is a sensing receiver, from the spec text it is not clear whether the requesting device needs to send CIR report.  The initiator normally does not schedule the requesting device for CIR reporting in this case. However if the sensing requesting device cannot perform frequency stitching reporting it may report multiple  499.2 MHz CIRs and requesting the aggregated CIR from the sensing initiator\n",null,"If sensing requesting device does not support aggregated CIR report but requested in SBP request IE Sensing ctrl as a sensing receiver, and requested aggregated CIR report, the sensing initiator should schedule  499.2 MHz CIR reports from the sensing requesting device ","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,252,"No","MediaTek","Technical",136,"10.39.5.3",8,"“The CIR Report IE transmitted by the sensing initiator shall include the address of the sensing\nresponder that generated the sensing measurement report carried in the CIR Report IE.”\n\nIf the initiator is sensing receiver, then all the reports should still have responder’s address",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,685,"No","Self","Editorial",136,"10.39.6.1",1,"There is Table 29-34 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,683,"No","Self","Editorial",136,"10.39.6.1",21,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,684,"No","Self","Editorial",136,"10.39.6.1",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1245,"No","Qorvo","Technical",137,"10.39.6.1",16,"\"The CSIP field shall be set to zero when the contention-based mode is used.\" seems strange, more likely this info would be present in contention based mode, maybe there is a \"NOT\" missing in this statement.",null,"Change to: \"The CSIP field shall be set to zero when the contention-based mode is not being used.\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Mickael Maman",null,82,"Yes","STMicroelectronics","Technical",137,"10.39.6.1",23," the default duration of ranging block shall be aligned with MAC PIB in Table 20. (i.e. 1209600 RTSU/16800 RSTU = 72 rounds per block)",null,"When the Block Duration field is not present, the ranging block shall have a default duration of 72 ranging rounds.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Mickael Maman",null,83,"Yes","STMicroelectronics","Technical",137,"10.39.6.1",26," the default duration of ranging round shall be aligned with MAC PIB in Table 20. (i.e. 16800 RTSU/ 600 RSTU = 28 slots per round)",null,"When the Round Duration field is not present, the ranging round shall have a default duration of 28 ranging slots.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Mickael Maman",null,84,"Yes","STMicroelectronics","Technical",137,"10.39.6.1",28," the default duration ofranging slot shall be aligned with MAC PIB in Table 20. (i.e. 600 RTSU)",null,"When the Slot Duration field is not present, the default ranging slot duration shall be\n600 RSTU.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,686,"No","Self","Editorial",138,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1246,"No","Qorvo","Editorial",138,"10.39.6.1",7,"UWB-only MMS",null,"change to \"UWB driven UWB MMS\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,687,"No","Self","Editorial",138,"10.39.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,688,"No","Self","Editorial",138,"10.39.6.1",17,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,689,"No","Self","Editorial",139,"10.39.6.1",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1247,"No","Qorvo","Editorial",139,"10.39.6.1",33,"UWB-only MMS",null,"change to \"UWB driven UWB MMS\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,692,"No","Self","Editorial",140,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,892,"No","Qorvo","Technical",140,"10.39.6.1",1,"The field names 'Number of RSF' and 'Number of RIF' are misleading as they do not store the number of RSF and RIFs but rather are an index into a table.",null,"Rename the fields 'Number of RSF' and 'Number of RIF' to 'RSF Number Index' and 'RIF Number Index' respectively.\n\nAlso make the appropriate changes elsewhere to related text.","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Carl Murray",null,893,"No","Qorvo","Technical",140,"10.39.6.1",1,"The field name MSR For MMRS is wrong. The 'M' in MSR stands for MMRS! Also it doesn’t contain the number of repetitions, i.e. the 'R'. So it is an index.",null,"Change the field name to 'MSR Index'\n\nAlso make the appropriate changes elsewhere to related text.","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,690,"No","Self","Editorial",140,"10.39.6.1",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,894,"No","Qorvo","Technical",140,"10.39.6.1",6,"The units for the STS segment length are not defined.",null,"Define the units of the STS segment length.","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,691,"No","Self","Editorial",140,"10.39.6.1",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,895,"No","Qorvo","Technical",140,"10.39.6.1",10,"The maximum channel number is 113 but the UWB Channel field allows for values up to 127. What happens if values greater that 113 are used.",null,"Specify what happens if this field is 114 to 127","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,693,"No","Self","Editorial",141,"10.39.6.1",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,896,"No","Qorvo","Technical",141,"10.39.6.1",3,"Since there was some interest in smaller MSR values, and none in larger ones, the values reserved for future use should be 0 and 1, rather than 6 and 7, to make any future use of these more logical.",null,"In Table 27 make field values 2 to 7 cover the range 32 to 256, and field values 0 and 1 be the reserved ones.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1248,"No","Qorvo","Technical",141,"10.39.6.1",5,"The STS Segment Length field, is misnamed, since there are no \"STS segments\" in the MMS ranging, i.e., this should be called RIF Fragment Length.",null,"Change the field name from \"STS Segment Length\" to \"RIF Fragment Length\", in Figure 149, and lines 5,6,7 of p141, and in Table 28.","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,694,"No","Self","Editorial",141,"10.39.6.1",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,897,"No","Qorvo","Technical",141,"10.39.6.1",7,"To allow for potential future use cases the STS Segment\nLength field, should be a 3-bit field. Taking the Reserved bit shown in Figure 149.",null,"In Figure 149, make the STS Segment Length field ocupy bits 22 to 24, renumbering following next fields as appropriate, and removing the reserved bit). And, update Table 28 so valies with 0 and 1 reserved, values 2 to 5 mapping to fragment lengths 32, 64, 128, 256, and vaues 6 and 7 reserved.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1249,"No","Qorvo","Technical",141,"10.39.6.1",8,"In Table 28, the units of this RIF Fragment Length specifier (\"STS Segment Length field\") are not defined. Assume this as 512-chip units",null,"Add into table 28, in the meaning column, \"in units of 512 chips (~1 μs)\"","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,695,"No","Self","Editorial",141,"10.39.6.1",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Youngwan So",null,934,"Yes","SAMSUNG Elec.","Editorial",141,"10.39.6.1",19,"It seems there's no description what acronym MMRA stands for.",null,"Please put full name of MMRA somewhere lie in chapter3.2 \"Acronyms and Abbreviations\" etc.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"B. Rolfe",null,1342,"Yes","BCA","Technical",141,"10.39.6.1 ",11,"\"may not\" is never correct.  ",null,"change \"may not be present \" to \"may be omitted\"",null,"Accepted","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Mickael Maman",null,85,"Yes","STMicroelectronics","Technical",142,"10.39.6.1",8,"CIR Report Request for Non-sensing Packet is defined but the non sensing TX CIR report parameters are missing",null,"define which packet format (ranging, data, MMS) and from which part of the packet (SYNC, STS, payload) the CIR report is generated","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,696,"No","Self","Editorial",142,"10.39.6.1",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,254,"No","MediaTek","Technical",142,"10.39.6.1",11,"The Sensing Report Parameters Present  shall be set to 0 if Responder Role is sensing transmitter and the sensing ctrl is sent by initiator to the responder(s)",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,255,"No","MediaTek","Technical",142,"10.39.6.1",11,"The Sensing Report Parameters Present  shall be set to 1 if sensing mode is  Sensing by proxy",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Aniruddh Rao Kabbinale",null,231,"Yes","Samsung Electronics","Editorial",142,"10.39.6.1",20,"\"Responder role\"  actually indicates device role that controller sets.",null,"Change to Device role","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,697,"No","Self","Editorial",142,"10.39.6.1",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,698,"No","Self","Editorial",143,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,701,"No","Self","Editorial",143,"10.39.6.1",1,"PDF index has Table 29-34, which should not be there. ",null,"Remove Table 29-34 from the PDF index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Li-Hsiang Sun",null,256,"No","MediaTek","Technical",143,"10.39.6.1",2,"If sensing mode is mono-static, i.e. responder is both sensing transmitter and receiver. then responder role should be reserved",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,699,"No","Self","Editorial",143,"10.39.6.1",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1250,"No","Qorvo","Technical",143,"10.39.6.1",6,"This is a strange \"minus one\", the paragraph says a value of zero is valid, indicating no offset, and a non-zero value indicates the offset, with a minus 1.  So we cannot use this field to specify an offset of 1. Also, as this is a 10-bit field, it so can represent an offset up to 1023 without subtracting one, which is enough to specify where to start in a 1K sized array.  Adding 1 to the value, would yield a max offset of 1024, an offset to the position 1 after the end of a 1K sized array.  This does not seem useful.",null,"Delete the \"minus one\" from the line, or just re-write to say it is the offset (which can be 0).","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,700,"No","Self","Editorial",143,"10.39.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Youngwan So",null,935,"Yes","SAMSUNG Elec.","Editorial",143,"10.39.6.1","P143L5,\nP143L9","Sometimes, no consistency of formality at Figure and Table title. Here, some Figure title ends with 'field' while some are not.",null,"Make a change as follows;\n\nFrom\n\"Table 30—Values of Responder Role subfield of the Common Sensing Control\"\nTo\n\"Table 30—Values of Responder Role subfield of the Common Sensing Control field\"\n\nFrom\n\"Table 31—Values of Sensing Packet Format subfield of the Common Sensing Controll\"\nTo\n\"Table 31—Values of Sensing Packet Format subfield of the Common Sensing Control field\"\n","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Aniruddh Rao Kabbinale",null,232,"Yes","Samsung Electronics","Editorial",143,"10.39.61",5,"Responder Role is actually device role.",null,"0 Initiator; 1 Responder","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,259,"No","MediaTek","Technical",144,"10.39.6.1",1,"Can the CIR bitmap configuration, compression, … (e.g. Fig 154) be different for different responders in the same multi-static session (i.e. same session ID) ?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,704,"No","Self","Editorial",144,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,257,"No","MediaTek","Technical",144,"10.39.6.1",2,"Report type shall not set to 1 or 2 when sensing ctrl is included in SBP request/response IE because the procedure in 10.39.5.3 only supports CIR reports",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,702,"No","Self","Editorial",144,"10.39.6.1",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,703,"No","Self","Editorial",144,"10.39.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,86,"Yes","STMicroelectronics","Technical",144,"10.39.6.1",10,"add reserved for value 3",null,"as in comment","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Tero Kivinen",null,706,"No","Self","Editorial",145,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,707,"No","Self","Editorial",145,"10.39.6.1",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,708,"No","Self","Editorial",145,"10.39.6.1",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,898,"No","Qorvo","Technical",145,"10.39.6.1",6,"To be consistent with the definitions on pg132 it would be better for the CBW field to specify the format of the real and imaginary components, e.g.16-bit signed value  rather than 16 bits. Also it would be good to reference the normalization in pg 132",null,"Align the CBW description with the definitions on pg 132","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,705,"No","Self","Editorial",145,"10.39.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,709,"No","Self","Editorial",146,"10.39.6.1",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,710,"No","Self","Editorial",146,"10.39.6.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,899,"No","Qorvo","Technical",146,"10.39.6.1",12,"In this paragraph 'amplitide' is used incorrectly. An amplitude can be positive or negative.",null,"Replace 'amplitude' with 'magnitude'.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,711,"No","Self","Editorial",147,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,713,"No","Self","Editorial",147,"10.39.6.1",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,712,"No","Self","Editorial",147,"10.39.6.1",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,714,"No","Self","Editorial",147,"10.39.6.1",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1315,"No","NXP Semiconductors","Editorial",147,"10.39.6.1",13,"Typo: \"let T denote\" instead of \"denotes\" ",null,"let T denote","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,268,"No","MediaTek","Technical",147,"10.39.6.1",16,"“where Smax is the magnitude of the strongest detected CIR tap.” strongest among all (ANT, SEG) tuples or just the current (ANT,SEG)?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1251,"No","Qorvo","Technical",148,"10.39.6.1",10,"Should the term \"speed\" be used rather than velocity, just to avoid people thinking it is a vector with a direction? ",null,"Change velocity to speed.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,260,"No","MediaTek","Technical",148,"10.39.6.1",19,"what is the reference for receiver orientation?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,261,"No","MediaTek","Technical",148,"10.39.6.1",22,"Feedback control could be omitted/reserved if responder role is sensing transmitter and sensing ctrl not in SBR request/response IE",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,715,"No","Self","Editorial",148,"10.39.6.1",22,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,176,"No","Huawei","Editorial",148,"10.39.6.1",23,"Remove \"when one\" in this line",null,"As in the comment","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carl Murray",null,900,"No","Qorvo","Technical",148,"10.39.6.1",27,"The Base Channel field does not support the the new channel numbering in section 16.4.1.2 pg 209 even though the note on this page seems to suggest that they will be used for frequency stitching and there does not appear to be a reason that the base channel should only be CH 0 to CH 15",null,"Change the Base channel field so that it supports the channels in section 16.4.1.2 and 11.1.3.5","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,716,"No","Self","Editorial",149,"10.39.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,262,"No","MediaTek","Technical",150,"10.39.6.1",2,"Is intra-packet frequency stitching PPDU format specified in  16.2?",null,"Clarify intra-packet frequency stitching PPDU format","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,717,"No","Self","Editorial",150,"10.39.6.1",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,264,"No","MediaTek","Technical",150,"10.39.6.1",4,"The example does not match formula on p149 for OF=2, N=6",null,"fix the formula, the (OF+1) in formula for OF=1,2 should be replace by a value of (1+1), i.e. there is 1 overlapping channel in the grid to a base channel  for the case of OF=1 and 2 so for these 2 cases the order should be the same ","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1252,"No","Qorvo","Technical",150,"10.39.6.1",4,"No such thing as sensing fragments, the sensing packet has sensing segments.",null,"Change to sensing segments.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,718,"No","Self","Editorial",150,"10.39.6.1",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,901,"No","Qorvo","Technical",150,"10.39.6.1",11,"Figure 160 and the associated text is incomplete as it does not address the SHR of the sensing packet. What happens if the SHR overlaps an SF (of its owns SFs or another packets).\n",null,"Update the figure to include the SHR and describe the spacing when the SHR overlaps an SF.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Billy Verso",null,1253,"No","Qorvo","Technical",150,"10.39.6.1",11,"Figure 160 is misleading since it is not showing the sensing packet completely with SHR, and the 4 sensing segments.",null,"Update figure to show full sensing packet(s) with SHR ","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,719,"No","Self","Editorial",151,"10.39.6.1",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,721,"No","Self","Editorial",151,"10.39.6.1",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,720,"No","Self","Editorial",151,"10.39.6.1",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,722,"No","Self","Editorial",152,"10.39.6.1",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Qian",null,177,"No","Huawei","Editorial",152,"10.39.6.1",5,"This paragraph and the next paragraph are repeated",null,"Remove Line 5-6","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,265,"No","MediaTek","Technical",152,"10.39.6.1",7,"UWB Channel field should be set to base channel number if Frequency Stitching Parameters field is included",null,"as in comment","No","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Carl Murray",null,902,"No","Qorvo","Technical",152,"10.39.6.1",9,"The maximum channel number is 113 but the UWB Channel field allows for values up to 255. What happens if values greater that 113 are used.",null,"Specify what happens if this field is 114 to 255.\n\nAlternatively reduce the field to 7 bits and specify what happens if this field is 114 to 127","Yes","Revised","doc 15-24-0431-01-04ab-draft-1-0-sensing-related-comments-resolution-part-1.docx","SENS",null,"DONE"]
[null,null,"Billy Verso",null,1254,"No","Qorvo","Editorial",152,"10.39.6.1",10,"blank line",null,"delete it","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,723,"No","Self","Editorial",152,"10.39.6.2",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1255,"No","Qorvo","Editorial",153,"10.39.6.1",17,"\"For each Rx antenna there\"",null,"change to \"For each antenna there\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,725,"No","Self","Editorial",153,"10.39.6.2",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1316,"No","NXP Semiconductors","Editorial",153,"10.39.6.2",4,"Reference should be to Table 10-149 in 04me-D04",null,"Fix reference","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1256,"No","Qorvo","Editorial",153,"10.39.6.2",9,"I think text should not say \"DEFLATE compressed\" everywhere and instead just say compressed as per clause x.x.x., and in that one place say the compression is done as per the RFC definition (referencing the DEFLATE RFC).",null,"Edit as per comment.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Li-Hsiang Sun",null,266,"No","MediaTek","Technical",153,"10.39.6.2",13,"“The Responder Address field, when present, identifies the SDEV that generated the CIR report.”  does not cover the case that responder is sensing transmitter and this is a SBP CIR report",null,"add “or identifies the sensing transmitter when the initiator generated the CIR report”","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pablo Corbalán Pelegrín",null,1317,"No","NXP Semiconductors","Technical",153,"10.39.6.2",13,"The Responder address may also be included in the MAC Header of the message. If this report is sent to the application together with the sender of the message, is the responder address field then needed?",null,"Verify if the Responder Address field is indeed needed. If not, we may reconsider whether the addressing fields should be added or not. In any case, setting the Responder Address Mode to 00 means that no responder address is added. ","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,267,"No","MediaTek","Technical",153,"10.39.6.2",15,"when bitmap mode is 1, how does one bitmap covers all tx/rx CIRs?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,726,"No","Self","Editorial",153,"10.39.6.2",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,724,"No","Self","Editorial",153,"10.39.6.2",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Kangjin Yoon",null,1415,"No","Spark Microsystems","Editorial",154,"10.39.6.2",6,"Use octet instead of byte for consistency.",null,"Change \"byte-wise\" to \"octet-wise\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,727,"No","Self","Editorial",154,"10.39.6.2",24,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,728,"No","Self","Editorial",154,"10.39.6.2",26,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,270,"No","MediaTek","Technical",154,"10.39.6.2",28,"How RSSI value for an aggregated report is acquired/claculated? ",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,729,"No","Self","Editorial",154,"10.39.6.2",28,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,246,"No","MediaTek","Technical",155,"10.39.6.2",1,"Not very clear about the definition of Timing Offset field. In Fig 139, the earliest CIR tap defines the timing grid, should this filed always be 0?",null,"Clarify the definition or Fig 139","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carl Murray",null,903,"No","Qorvo","Editorial",155,"10.39.6.2",2,"Here it states \"The value is a 6-bit signed\n3 quantity, in two’s complement format, ...\"\n\nElsewhere (eg pg 132) we refer to 16-bit signed values but we do not state that it is two's complement. We should use consistent notation.",null,"Use consistent notation. Either a x-bit signed value is implicitly two's complement and therefore does not need the qualification of \"two's complement\" or every x-bit signed value needs to be explicitly described as two's complement or an alternative format. Make the notation consistent.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carl Murray",null,904,"No","Qorvo","Technical",155,"10.39.6.2",4,"The Normalisation factor is poorly described - \"The Normalization Factor field specifies a 4-bit power-of-two normalization factor\". ",null,"Replace the indicated test with \n\n\"The Normalization Factor field specifies  a 4-bit unsigned integer, which will be used as the exponent in the expression 2^exponent to determine the normalization factor\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Pablo Corbalán Pelegrín",null,1318,"No","NXP Semiconductors","Editorial",155,"10.39.6.2",9,"We may want to clarify that the RSSI report resolution is 1 dB.",null,"The RSSI is reported in steps of 1 dB with a minimum value of 0 (-174 dBm) and maximum value of 254 (80 dBm).","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,730,"No","Self","Editorial",155,"10.39.6.2",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,87,"Yes","STMicroelectronics","Technical",155,"10.39.6.2",16,"the channel ID of the receive report control field is currently limited to the 16 legacy channels. It should be extended to extended channels",null,"update size of channel ID to 1 octet in figure 168 and add \"The Channel ID field indicates the channel corresponding to the CIR taps when frequency stitching is enabled. Values in the range 0 to 15 refer to channels defined in Table 16-27 (HRP UWB PHY band allocation), while values 16 to 113 refer to the extended channel numbering as specified in 16.4.1.2\"","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Li-Hsiang Sun",null,269,"No","MediaTek","Technical",155,"10.39.6.2",16,"How does Receive Report Control identify an aggregated CIR report? i.e. feedback ctrl value 2",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Carl Murray",null,905,"No","Qorvo","Technical",155,"10.39.6.2",16,"The 'Channel ID' field only has 4 bits which is not sufficient to indicated the channel for frequency stitching as they can be aligned to 128.8 MHz offsets.",null,"Change the 'Channel ID' field so that it incorporated the channels in section 16.4.1.2 and 11.1.3.5.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,731,"No","Self","Editorial",156,"10.39.6.3",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,253,"No","MediaTek","Technical",157,"10.39.6.4",18,"Some fields after SBP status code should be omitted if the status is REJECT or REJECTED__WITH_SUGGESTED_CHANGES",null,"as in comment","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,733,"No","Self","Editorial",157,"10.39.6.4",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,732,"No","Self","Editorial",157,"10.39.6.4",23,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1257,"No","Qorvo","Editorial",157,"10.39.6.4",24,"Normal text can be used for these meanings in the table and in the descriptive text below.",null,"Edit as per comment.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,734,"No","Self","Editorial",158,"10.39.6.5",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Li-Hsiang Sun",null,271,"No","MediaTek","Editorial",159,"10.39.6.6",1,"Bits 17, 18 seems missing in Fig 172",null,"as in comment","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,735,"No","Self","Editorial",159,"10.39.6.6",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Rojan Chitrakar",null,138,"No","Huawei","Technical",159,"10.39.6.6",3,"When EOL field is zero, how is the target list continued in a subsequent frame, is the target list the only content of the next report, or are the preceding control fields also present? Details are missing. Also which target list, full or short?",null,"Add detail of the procedure used to continue the target list in the next report when the EOL field is zero. Details are missing. Also specify if the target list is full or short?","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Li-Hsiang Sun",null,272,"No","MediaTek","Technical",159,"10.39.6.6",10,"Not clear what is the relationship between Fig 172 and Fig 177 when compression is enabled",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Pooria Pakrooh",null,1377,"No","Qualcomm","Technical",159,"10.39.6.6",20,"Unclear what the definition of \"Rotation\" and \"Elevation\" fields are",null,"Clarify the defenition and range of values","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Tero Kivinen",null,736,"No","Self","Editorial",160,"10.39.6.6",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,737,"No","Self","Editorial",160,"10.39.6.6",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,738,"No","Self","Editorial",160,"10.39.6.6",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,739,"No","Self","Editorial",160,"10.39.6.6",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Pablo Corbalán Pelegrín",null,1319,"No","NXP Semiconductors","Technical",160,"10.39.6.6",17,"Shouldn't the Elevation angle range from -90º to 90º instead of -180º to 180º? If we do make this change, the resolution for Azimuth and Elevation angles will be different.",null,"Change \"-pi to +pi radians\" to \"-pi/2 to +pi/2 radians\".","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Li-Hsiang Sun",null,273,"No","MediaTek","Technical",161,"10.39.6.6",1,"what is the reference for Delay field? i.e. what 0 means? What is the unit?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Li-Hsiang Sun",null,274,"No","MediaTek","Technical",161,"10.39.6.6",3,"what is the unit of the velocity?",null,"Please clarify","No",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Billy Verso",null,1258,"No","Qorvo","Technical",161,"10.39.6.6",3,"\"Velocity field reports the velocity of the target (4 bits, signed integer, zero padded to an octet)\"…. Units are missing.  Also maybe could uses whole octet as a singed integer, and/or sign extend it rather than zero padding, for easier use.",null,"Specify units.  Make full octet signed value. (and change name to \"Speed\" instead of velocity as it is not a velocity vector. ","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Tero Kivinen",null,740,"No","Self","Editorial",161,"10.39.6.6",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1259,"No","Qorvo","Technical",161,"10.39.6.6",14,"Two figures Figure 172 and Figure 177 give a format of the \"Processed Target Feature Report IE Content field format\" second is with deflate compression, but first has a compression bit and second does not… this is confusing. How can these be distinguished/parsed? Or maybe this is a mistake? Makes more sense to make one figure with the compression bit and make sure that it contains all the fields necessary.",null,"Delete figure 177 and include any missing fields back into figure 172.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Billy Verso",null,1260,"No","Qorvo","Technical",161,"10.39.6.6",15,"\"constructed from the uncompressed Full Target Report List and Sparse Target Report List fields, appended to each other\" does not convey ordering, possibly should be more precise \" saying which comes first and which comes second (\"right concatenated\") perhaps with the aid of a figure to make it clear.",null,"Clarify the ordering of concatenation of these fields, with the aid of a figure.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Aniruddh"]
[null,null,"Tero Kivinen",null,741,"No","Self","Editorial",162,"10.40.3",1,"There is Figure 178 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Zhenzhen Ye",null,6,"No","Redpoint Positioning","Editorial",162,"10.40.3",7,"wrong section number on the reference of AC IE?",null,null,"Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1261,"No","Qorvo","Technical",162,"10.40.3",9,"In the sentence \"may be sent in any unscheduled slot in the round slot in the round\" would \"unoccupied\" be a better word than \"unscheduled\"",null,"Change \"unscheduled\" to \"unoccupied\".","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1262,"No","Qorvo","Technical",162,"10.40.3",9,"UWB reception is expensive, so the initiator device is unlikely to have its receiver on in any slot that it is not expecting a packet.  Better to develop a protocol, with a slot dedicated to association, and perhaps that association scheme would be better being defined in the higher layer protocol and not in 4ab.",null,"Consider modification / deletion of this mode of association, to address this issue or explain what the initiator should be doing for an energy efficient scheme.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,742,"No","Self","Editorial",163,"10.40.3",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1263,"No","Qorvo","Technical",163,"10.40.3",2,"This figure (Figure 178) is not referenced in the text, if it is not referenced then it is probably not needed?",null,"Either delete the figure, or write some text to refer to it and explain what it is showing, (and perhaps the figure caption could be shortened, if the descriptive text is carrying the same info)","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1264,"No","Qorvo","Technical",163,"10.40.4.1",5,"I think this is wrongly named HRP UWB association command  suggest a more application (rather than PHY) related name, like perhaps \"ranging controller association\". HRP can associate to a normal 15.4 PAN coordinator, and no reason why other phy may not use this scheme in a ranging/slotted network,",null,"Rename to \"ranging controller association\"","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,745,"No","Self","Technical",163,"10.40.4.1",9,"The text \"Addressing Mode field shall be set to same mode as indicated by the AC IE\" does not make sense. AC IE does not have modes indicating the address mode fields, and if it is trying to say that use same source and destination addressing modes than what was used to AC IE then that does not work, as the if the AC IE is using short address then the device transmitting association request can't use short address, as it has not yet been given short address. ",null,"Specify how the source and destination addressing fields are to be used in association request command.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,746,"No","Self","Technical",163,"10.40.4.1",17,"The macShortAddress cannot be used before device has been associated and given a short address, using this mac command. ",null,"Source address needs to be extended address always as device do not yet have short address.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,743,"No","Self","Editorial",163,"10.40.4.1",20,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,744,"No","Self","Technical",163,"10.40.4.1",21,"Where does the device wanting to send association request get this session id? ",null,"is this Session Id same as AC IE, if so add reference to there.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Li-Hsiang Sun",null,258,"No","MediaTek","Technical",164,"10.40.4.1",1,"compression/decompression of CIR report should be added in capability",null," as in comment","No",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,748,"No","Self","Editorial",164,"10.40.4.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,747,"No","Self","Editorial",164,"10.40.4.1",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1265,"No","Qorvo","Technical",164,"10.40.4.2",17,"I think this is wrongly stated since we cannot know what the remote controlee is trying to do. And the SHALL here is dependent on next higher layer activity.",null,"Change to: \"This command shall be sent as a result of the MLME-ASSOCIATE.response primitive being issued by the next higher layer.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1266,"No","Qorvo","Technical",164,"10.40.4.2",19,"Since the next higher layer is in the loop here with MLME-ASSOCIATE.indication and MLME-ASSOCIATE.response primitives, we have to make sure that the requisite information is included in both to allow for this, and then change this sentence to make the parameters here come from the MLME-ASSOCIATE.response. ",null,"Check/Change MLME-ASSOCIATE.indication and MLME-ASSOCIATE.response primitives as per comment, and change the paragraph to explain how the Source Addressing Mode and Destination Addressing Mode fields values are determined from the MLME-ASSOCIATE.response primitive.,","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Billy Verso",null,1267,"No","Qorvo","Technical",165,"10.40.4.2",4,"Since the next higher layer is in the loop here with MLME-ASSOCIATE.indication and MLME-ASSOCIATE.response primitives, we have to make sure that the requisite information is included in both to allow for this, and then change this sentence to make the parameters here come from the MLME-ASSOCIATE.response. ",null,"Check/Change MLME-ASSOCIATE.indication and MLME-ASSOCIATE.response primitives as per comment, and change the paragraph to explain how the Destination Address field value is determined from the MLME-ASSOCIATE.response primitive.,","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,750,"No","Self","Editorial",165,"10.40.4.2",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,754,"No","Self","Technical",165,"10.40.4.2",9,"The response command should include the short address the controller assigned to the controlee not just updated short address. ",null,"Change \"Updated Short Address\" to \"Short Address\".","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,749,"No","Self","Editorial",165,"10.40.4.2",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,752,"No","Self","Technical",165,"10.40.4.2",11,"Status value 2 does not make any sense, as this is association request, thus by definition device does not yet have short address, that could be updated. ",null,"Remove status value 2.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,753,"No","Self","Technical",165,"10.40.4.2",11,"Status value 3 does not make any sense, as this is association request, thus by definition device does not yet have short address, that could be duplicate as the request does not provide short address request. ",null,"Remove status value 3.","Yes",null,"doc 15-24-0411-01-04ab-proposed-resolution-for-discovery.docx","DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,751,"No","Self","Editorial",165,"10.40.4.2",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,755,"No","Self","Editorial",166,"10.40.4.2",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,756,"No","Self","Technical",166,"10.40.4.2",3,"There is no macHrpUwbAifsPeriod pib variable. ",null,"Fix it to macEmdevImmAckAifsPeriod,","Yes",null,null,"DISC",null,"ASSIGNED",null,"Kanjing"]
[null,null,"Tero Kivinen",null,758,"No","Self","Editorial",167,"10.41.2",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,757,"No","Self","Editorial",167,"10.41.3.1",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,759,"No","Self","Editorial",168,"10.41.3.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,760,"No","Self","Editorial",168,"10.41.3.1",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Youngwan So",null,936,"Yes","SAMSUNG Elec.","Editorial",168,"10.41.3.1",5,"Seems Typo",null,"Change\n\nFrom\n\"Figure 186—Encoding of TRCS subfields of the of the DDMN IE\"\nTo\n\"Figure 186—Encoding of TRCS subfields of the DDMN IE\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,761,"No","Self","Editorial",168,"10.41.3.1",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,762,"No","Self","Editorial",168,"10.41.3.1",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,763,"No","Self","Editorial",169,"10.41.3.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,764,"No","Self","Editorial",169,"10.41.3.1",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,765,"No","Self","Editorial",170,"10.42.2.1",9,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,766,"No","Self","Editorial",171,"10.42.2.2",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Mickael Maman",null,88,"Yes","STMicroelectronics","Technical",171,"10.42.2.2",6,"it is not MLME-STS.request but MLME-WU-RX.request",null,"as in comment","Yes","Accepted",null,"WUR",null,"DONE"]
[null,null,"Youngwan So",null,937,"Yes","SAMSUNG Elec.","Editorial",171,"10.42.2.2",6,"Seems Typo",null,"Change\n\nFrom\n\"If any parameter in the MLME-STS.request primitive is not supported\"\nTo\n\"If any parameter in the MLME-WU-RX.request primitive is not supported\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,767,"No","Self","Editorial",172,"10.42.2.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,768,"No","Self","Editorial",172,"10.42.2.5",17,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Youngwan So",null,938,"Yes","SAMSUNG Elec.","Editorial",172,"10.42.2.5",21,"Seems Typo",null,"Change\n\nFrom\n\"If the device is not capable as operating as a WU-TXDEV, a Status value of NOT_SUPPORTED is returned.\"\nTo\n\"If the device is not capable of operating as a WU-TXDEV, a Status value of NOT_SUPPORTED is returned.\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1268,"No","Qorvo","Technical",173,10.43,2,"10.43 UWB data offload to narrowband, did not review this fully (may have more comments later) but explaining a complex procedure this would benefit from a MSC showing the interactions with primitives of now the offload is achieved.",null,"Consider next higher layer / mac / phy interactions necessary and draw a MSC with description to explain it.","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pooria Pakrooh",null,1378,"No","Qualcomm","Technical",173,10.43,4,"Not clear why this NB data transmission protocol is needed, given the significantly lower data rate relative to UWB, and also higher fading. If many users start to use this protocol, the congestion can be problematic. This can cause interference to unnecessarily longer range. There is no duty cycle limit specified for this feature and the benefits are not clear.\n\nRemove this functionality, or add a proper mandatory channel access mechanism.",null,"\n\nRemove this functionality, or add a proper mandatory channel access mechanism.","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pooria Pakrooh",null,1379,"No","Qualcomm","Technical",173,10.43,4,"Benefits of NB usage for ranging has been justified. What is the benefit of using two links with significantly different link budget? what is the application? The data communication associated with this application are for close range cases, which does not need NB.",null,"\n\nRemove this functionality, or add a proper mandatory channel access mechanism.","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,769,"No","Self","Editorial",173,"10.42.3.1",23,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,773,"No","Self","Editorial",173,"10.43.1",4,"This is not first use of NBA, do not expand here. ",null,"Do not expand here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,772,"No","Self","Editorial",173,"10.43.2",1,"There is Figure 189 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Carlos Aldana",null,971,"No","Meta Platforms","Technical",173,"10.43.2",15,"The statement says \"for starting NB data communication during measurement phase\" and the figure shows a single NB packet.  If the figure is correct, does NB data communication contain a single packet?  If so, please state it explicitly.  If so, is there no Ack?  If there is an Ack, what is IFS spacing?  What is the expected packet flow for NB data communications?",null,"Please clarify all the questions here.","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Carlos Aldana",null,1013,"No","Meta Platforms","Technical",173,"10.43.2",15,"NB data communications should use LBT as a baseline channel access mechanism.  Please add the followign text at the end of the paragraph: \"Channel access using listen before talk shall be used for improved coexistence performance.   When used for narrowband assist, SSBD shall use the following control attribute values:\nphyCcaDuration should be set as required by local regulations;\n\nmacSsbdMinBf and macSsbdMaxBf shall be set to 0;\nmacSsbdMaxBackoffs shall be set to 0;\nmacSsbdTxOnEnd shall be set to FALSE;\nmacSsbdPersistence shall be set to FALSE;\nphyCcaMode shall be set to 1 (energy above threshold)\nphyCcaEdThreshold shall be set to -67 dBm/MHz - Ptx for channels 0 to 49 and to -74 dBm/MHz - Ptx for channels 50 to 249, where Ptx is the equipment’s instantaneous transmit power in dBm.\"",null,"As in comment","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Carlos Aldana",null,1012,"No","Meta Platforms","Technical",173,"10.43.2",17," When does the NB data packet(s) end?  That should be communicated to ensure it does not overlap with the next ranging round.",null,"please clarify","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,770,"No","Self","Editorial",173,"10.43.2",18,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,972,"No","Meta Platforms","Technical",173,"10.43.3",19,"There is text missing associated with this section.  Either remove section or add text.",null,"As in comment","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,771,"No","Self","Editorial",173,"10.43.3.1",1,"There is Table 55 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Carlos Aldana",null,969,"No","Meta Platforms","Technical",173,"10.43.3.1",23,"4 octets are assigned to the \"Transmission Offset\" field.  This results in ~1 hour time offset from the time the NB Allocation packet is sent.  This seems excessive.  Consider reducing the number of octets or increasing the units of the field to something much greater than a RSTU (e.g., 1 ms)",null,"As in comment","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Carlos Aldana",null,970,"No","Meta Platforms","Technical",173,"10.43.3.1",23,"1 octet allocation to \"NB PHY\" field can be reduced to 3 bits.  More importantly, what happens if the content of the field is 0?  Does the value \"0\" mean 250kbps or is the value undefined since Table 58 starts with Config value of 1.  Please clarify.",null,"As in comment","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Pooria Pakrooh",null,1380,"No","Qualcomm","Technical",173,"10.43.3.1",23,"If this is a unicast message, why does it inclue address in the IE?",null,"Clarify the question in the comment.","Yes",null,null,"UWBDO",null,"ASSIGNED",null,"Youngwan"]
[null,null,"Tero Kivinen",null,774,"No","Self","Editorial",174,"10.42.3.1",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,973,"No","Meta Platforms","Editorial",174,"10.43.3.1",7,"It will be good to reference the Channel numbering definition in Section 11.1.3.15.",null,"Add \"as defined in 11.1.3.15\" after \"the address field\".","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Kangjin Yoon",null,1416,"No","Spark Microsystems","Editorial",174,"10.44.1",26,"The maximum number of deferral iterations also be used for bounded deferral.",null,"Change \"linearly growing random backoff at each deferral.\" \n\nto \"linearly growing random backoff at each deferral and bounded deferral and the maximum number of deferral iterations.\" at the end of the line.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,89,"Yes","STMicroelectronics","Technical",175,"10.44.2",4,"Replace Packet Retransmission by IsretransmissionAttempt in Figure 191",null,"as in comment","Yes","Revised","isRetransmissionAttempt","SSBD",null,"DONE"]
[null,null,"Kangjin Yoon",null,1417,"No","Spark Microsystems","Editorial",175,"10.44.2",4,"For better readability, use the defined \"isRetransmissionAttempt\".",null,"Change \"Packet Retransmission?\" to \"isRetransmissionAttempt\" in Figure 191.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,775,"No","Self","Editorial",175,"10.44.2",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Larry Zakaib",null,1426,"Yes","Spark Microsystems","Editorial",175,"10.44.2","8,9,10","Clause \"Prior to each CCA attempt, the SSBD algorithm shall delay for a period determined by the macSsbdUnitBackoffPeriod attribute value multiplied by a random integer between zero and BF\" is redundant with the flow chart and may lead to confusion. ",null,"Delete clause \"Prior to each CCA attempt, the SSBD algorithm shall delay for a period determined by the macSsbdUnitBackoffPeriod attribute value multiplied by a random integer between zero and BF\" ",null,null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Carlos Aldana",null,975,"No","Meta Platforms","Technical",176,"10.44.2",10,"We should be explicit in how we set phyCcaEdThreshold and phyCcaDuration.  phyCcaDuration can be set to the value of 16 us.  For 2.5MHz transmissions, phyCcaEdThreshold can be set to a value that is inversely proportional to the transmit power, in dB.    For UNII-3, the ED threshold can be set to -67 dBm/MHz - Pmax_dBm and for UNII-5 it can be set to -74 dBm/MHz - Pmax_dBm.",null,"As in comment","Yes",null,null,"SSBD",null,"ASSIGNED",null,"Larry"]
[null,null,"Tero Kivinen",null,776,"No","Self","Editorial",176,"10.44.3",14,"Empty line in the beginning and end of Table 56. ",null,"Remove empty lines.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,777,"No","Self","Editorial",176,"10.44.3",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carlos Aldana",null,974,"No","Meta Platforms","Technical",176,"10.44.3",14,"Since it's likely not needed at the beginning of a session, the default value of macSsbdPersistence should be FALSE",null,"As in comment","Yes","Revised","\"TRUE\" -> \"FALSE\"","SSBD",null,"DONE"]
[null,null,"Billy Verso",null,1269,"No","Qorvo","Technical",177,"10.45.2",6,"\"to be supported with this RSS.\" is strange phrasing.",null,"Change: \"Time structures for communication are defined by the Ranging Service to be supported with this RSS\" to \"Time structures for communication are specified by the RSS\"","Yes","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","RSS",null,"Ready"]
[null,null,"Zhenzhen Ye",null,7,"No","Redpoint Positioning","Editorial",177,"10.45.2",14,"The approved sb-clause name of 10.45.2 is \"Channel access for RSS with O-QPSK\" in the resolution 15-24-0160.",null,null,"Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1270,"No","Qorvo","Editorial",177,"10.45.2",15,"The tense of \"are communicating\" which I believe is \"present continuous\" seems wrong.",null,"Change \"are communicating\" to \"communicate\".","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1271,"No","Qorvo","Technical",177,"10.45.2",15,"We should not limit RSS to the 2.4 GHz band, since 4ab is adding O-QPSK channels in 5.8 and 6 GHz bands, RSS should be able to use these bands so that a 4ab devices with these channels can also be deployed in the dense industrial environments described in 15-22-0077. ",null,"Change the sentence to: \"Devices operating in RSS mode utilise the O-QPSK PHY specified in Clause 13, communicate in the 2450 MHz band at 250 kb/s, or in the 5800 MHz and 6200 MHz bands at 250 kb/s or optionally at the higher data rates defined Table 45.\"","Yes","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","RSS",null,"Ready"]
[null,null,"Billy Verso",null,1272,"No","Qorvo","Editorial",177,"10.45.2",17,"Again \"present continuous\", which I suggest to revise the as per my proposed change.",null,"Change the sentence to: \"In RSS, devices either transmit in dedicated allocated slots or during the optional RSS CAP (described in 10.37.3.1).\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1273,"No","Qorvo","Technical",177,"10.45.2",19,"\"to be supported\" appears twice in the paragraph, (line 19 and 22).  \"The RSS slotframe starts at the beginning of the ranging round of the UWB ranging to be supported.\" seems clunky language to me, unless there is a technical reason for phrasing it this way, suggest a shorter phrase.",null,"Change to: \"The RSS slotframe is defined to start at the same time as the UWB ranging round\". ","Yes","Accepted","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","RSS",null,"Ready"]
[null,null,"Huan-Bang Li",null,1453,"Yes","NICT","Technical",177,"10.45.2",26,"this case' in the last sentence is not clear.",null,"describe 'this case' more clearly.","Yes","Revised","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","RSS",null,"Ready"]
[null,null,"B. Rolfe",null,1343,"Yes","BCA","Technical",178,"10.45.3.3",14,"\"may\" means \"may or may not\" and \"may not\" is not correct in this standard.",null,"delete \"or may not\". ",null,"Accepted","doc 15-24-0415-05-04ab-proposed-resolution-for-comments-on-multiple-rcms-and-rss.docx","RSS",null,"Ready"]
[null,null,"Carlos Aldana",null,980,"No","Meta Platforms","Technical",179,"11.1.3.15",10,"The following 20 MHz block of frequency is not used by 802.11 devices in UNII-1: 5150-5170 and could be added to the frequency list to increase the number of channels allocated for NB.",null,"As in comment","Yes",null,"doc 15-24-0441-00-04ab-draft-1-0-nb-phy-related-comments-resolution-cid-980-981-989.docx","PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Carlos Aldana",null,981,"No","Meta Platforms","Technical",179,"11.1.3.15",10,"The following 20 MHz block of frequency is not planned to be extensively used by 802.11 devices in UNII-5: 5925-5945.  Redefine the UNII-5 frequencies so that k=50,…249 is replaced with 50,…57.  In addition, UNII-4 frequencies can be added so as have more Narrowband channels. ",null,"As in comment","Yes",null,"doc 15-24-0441-00-04ab-draft-1-0-nb-phy-related-comments-resolution-cid-980-981-989.docx","PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Carlos Aldana",null,989,"No","Meta Platforms","Technical",179,"11.1.3.15",10,"Ths frequency channel plan only covers UNII-3.  UNII-4 is available in some regions and should be added.  Please add channels to cover 5725 up to 5875 MHz along with LBT-based mechanism.",null,"As in comment","Yes",null,"doc 15-24-0441-00-04ab-draft-1-0-nb-phy-related-comments-resolution-cid-980-981-989.docx","PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,778,"No","Self","Editorial",179,"12.3.2",17,"Remove ... from the table, they are not needed. ",null,"Remove ... rows from the table.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Kangjin Yoon",null,1418,"No","Spark Microsystems","Editorial",180,"12.3.2",1,"The original text was not based on 802.15.4me-D04.",null,"Change \n\"The duration for CCA, specified in μs. For the SUN PHYs other than SUN O-QPSK the default value is 8 symbol periods, as defined in 6.1. For the SUN O-QPSK PHY, default value is defined in Table 22-24. For all other PHYs, the default duration of 8 symbol periods\" \n\nto \"The duration for CCA, specified in microseconds. If a recommended phyCcaDuration is not specified by the PHY clause then a phyCcaDuration of 8 symbol periods is recommended,\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Larry Zakaib",null,1428,"Yes","Spark Microsystems","Technical",180,"12.3.2",1,"The table states \"except when SSBD is being used in which \ncase clause 10.44 specifies the CCA \ndetection time\". This is no longer consistent with the base standard which now includes equivalent text. This addition to Table 12.2 is no longer needed.",null,"Delete this change to Table 12.2",null,"Accepted",null,"SSBD",null,"DONE"]
[null,null,"Tero Kivinen",null,779,"No","Self","Editorial",180,"12.3.7",5,"Remove ... from the table, they are not needed. ",null,"Remove ... rows from the table.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,780,"No","Self","Editorial",180,"12.3.7",5,"For the phyHrpUsbPhrDataRate the DRHM_1p95 ... DRHM_124p8 should be underlined as they are added relative to base standard. ",null,"Change them to underlined.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,781,"No","Self","Editorial",180,"12.3.7",7,"Remove ... from the table, they are not needed. ",null,"Remove ... rows from the table.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,782,"No","Self","Editorial",180,"12.3.7",7,"In the editing instructions add instructions to sort the table alphabetically after adding entries. ",null,"Add editing instructions asking for sorting of final table.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Mickael Maman",null,90,"Yes","STMicroelectronics","Technical",180,"12.3.7 ",6," PIBs for SENS packet configuration is missing",null,"similarly to MLM-UWB-PACKET. Request, add PIB in Table 12-8 \nphyHrpUwbSensTxPacketConfig\nphyHrpUwbSensTxSegLen\nphyHrpUwbSensTxSegNum\nphyHrpUwbSensRxPacketConfig\nphyHrpUwbSensRxSegLen\nphyHrpUwbSensRxSegNum","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Mickael Maman",null,91,"Yes","STMicroelectronics","Technical",181,12.3,2,"The PHY O-QPSK configuration is currently not detailed using primitives",null,"We propose to add a table for \"O-QPSK related PIB attributes\" with the following attributes:\n- phyOqpskSyncLen\n- phyOqpskSfdSelector\n- phyOqpskFecPhr\n- phyOqpskFecPayload\n- phyOqpskSpreadingFactor\nPossible values based on table 57, 58, 59, 60 of the 802.15.4ab amendment and table 13-1, 13-2 22-14, 22-15 of the 802.15.4me standard","Yes","Revised","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Billy Verso",null,1274,"No","Qorvo","Technical",182,"13.1.2.3",7,"\", with out of band selection being the default behaviour\" is slightly strange phrasing, and \"default\" has connotations in standards context that we should probably avoid..",null,"Change to: \"with the selection of these being agreed via out-of-band means\"","Yes","Accepted","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Huan-Bang Li",null,1454,"Yes","NICT","Editorial",182,"13.1.2.3",7,"replace 'out of band' by 'out-of-band'.",null,"make change.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Bin Tian",null,14,"No","Qualcomm","Editorial",182,"13.1.2.3",9,"\"defined by Figure 13-3\". There is no Figure 13-3",null,"Fix the figure index cross reference","Yes","Rejected","Figure 13-3 is in the base standard 802.15.4","TE",null,"N/A"]
[null,null,"Billy Verso",null,1275,"No","Qorvo","Technical",182,"13.1.2.3",10,"I think \"default\" not the right term to refer to the 250kb/s modulation. PHY parameters don't really have defaults.",null,"Change \"default\" to \"mandatory\"","Yes","Accepted","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Huan-Bang Li",null,1455,"Yes","NICT","Technical",182,"13.1.2.3",10,"replace 'modulation rate' by 'modulation data rate'",null,"make change.","Yes","Rejected","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"N/A"]
[null,null,"Billy Verso",null,1276,"No","Qorvo","Technical",182,"13.1.2.3",12,"For clarity there should be a statement that says what the SFD is when the dynamic SFD signalling is not being used.",null,"Add sentence at end of paragraph: \"When the dynamic modulation signalling is not being employed, the SFD defined by Figure 13-3 shall be used for each of Config #1 to #7 in Table 58 [Modulation modes for the 5800 MHz and 6200 MHz bands]).\"","Yes","Accepted","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Mickael Maman",null,92,"Yes","STMicroelectronics","Technical",182,"13.1.2.3",13,"Missing SFD patterns for config #6, #7 and #8",null,"as in comment","Yes","Rejected","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"N/A"]
[null,null,"Tero Kivinen",null,783,"No","Self","Editorial",182,"13.1.2.3",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1277,"No","Qorvo","Technical",182,"13.1.2.3",14,"In Table 57 only config #1 is mandatory, so for mode #8 where this table applies, is the assumption that that support for all configs #2 to #5 is mandatory, or how are both sides expected to know what is appropriate to use?",null,"Say this is done/agreed OOB, or mandate support for all, or add a mechanism for both sides to signal what they support so the other end only uses supported modes.","Yes","Revised","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Billy Verso",null,1278,"No","Qorvo","Technical",182,"13.2.2",15,"In the base standard clause 13.2.2 \"Data rate\" talks about data rates and channel bands, so we need some additional paragraph(s) to cover the new bands and data rates being added by 4ab",null,"Add a clause \"13.2.2 Data rate\" to with appropriate text inserted to cover the new bands and data rates that 4ab is adding.","Yes",null,null,"PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Huan-Bang Li",null,1456,"Yes","NICT","Technical",182,"13.2.3",20,"in that order' is not clear.",null,"specify the order.","Yes",null,null,"PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,784,"No","Self","Editorial",182,"13.2.3",22,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1279,"No","Qorvo","Technical",183,"13.2.5",5,"There is no mechanism for next higher layer to select the Modulation modes for the 5800 MHz and 6200 MHz bands.",null,"Add at the end of this sentence: \"The modulation mode is selected using the phyOqpskModulationConfiguration attribute.\" Add new phyOqpskModulationConfiguration PIB attribute integer, with description: \"Selects the O-QPSK PHY modulation modes for the 5800 MHz and 6200 MHz bands, as listed in Table 58\", and value range: \"As defined by Config # in Table 58\".","Yes","Accepted","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Tero Kivinen",null,785,"No","Self","Editorial",183,"13.2.5",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1280,"No","Qorvo","Technical",183,"13.2.5",8,"For in Table 58 for config #8, how does the transmitter know what actual mode to use, maybe should separate config #8 into 5 separate configs #8 to #12, each one defining what the TX should do, (i.e. one of the 5 options in Table 57), but where for all 5 of these the receiver uses the SFD to decide how to demodulate the PHR and data, as per Table 57.",null,"Separate out the config#8 into the 5 options as suggested.","Yes","Revised","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Billy Verso",null,1281,"No","Qorvo","Technical",183,"13.2.5",8,"When dynamic SFD selection is being used does the next higher layer need to know the SFD/Modulation used for the received packet?",null,"Consider my question and add it if necessary as a pub status parameter or a parameter in the MCPS-DATA.indication.","Yes",null,null,"PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,786,"No","Self","Editorial",184,"13.2.5",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,787,"No","Self","Editorial",184,"13.2.5",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,789,"No","Self","Editorial",185,"13.2.5",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Bin Tian",null,15,"No","Qualcomm","Technical",185,"13.3.14",20,"\"it is recommended\". NB and UWB PHY shall be derived from the same clock source instead of \"recommended\"",null,"as in the comment","Yes",null,null,"PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Bin Tian",null,16,"No","Qualcomm","Technical",185,"13.3.14",22,"\"the tolerance as stipulated for the UWB PHY\". Please specify the UWB PHY clause in which the tolerance requirement is specified",null,"as in the comment","Yes","Revised","Add a reference to 16.4.6","PHYNB",null,"DONE"]
[null,null,"Huan-Bang Li",null,1457,"Yes","NICT","Technical",185,"13.3.14",22,"tolerance' should be more precise.",null,"replace by 'center frequency tolerance'","Yes","Accepted","doc 15-24-0438-02-04ab-draft-1-0-nb-phy-related-comments-resolution.docx","PHYNB",null,"Ready"]
[null,null,"Pablo Corbalán Pelegrín",null,1320,"No","NXP Semiconductors","Editorial",185,"13.3.2",12,"Typo: Q-QPSK should be O-QPSK",null,"Replace Q-QPSK with O-QPSK","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Huan-Bang Li",null,1458,"Yes","NICT","Editorial",185,"13.3.2",12,"replace 'Q-QPSK' by 'O-QPSK'.",null,"make change.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,788,"No","Self","Editorial",185,"13.3.2",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Jaegook Lee",null,1469,"Yes","Samsung","Technical",185,"13.3.2",18," IEEE 802.15.4 (sec. 12.3.5) Adjacent channel rejection was designed in consideration of 5 MHz channel spacing. In IEEE 802.15.4ab, O-QPSK channel spacing was changed from 5 MHz to 2.5 MHz. Since channel spacing has been halved, adjacent channel rejection may need to be designed considering this new channel spacing.",null,"as in the comment","No",null,null,"PHYNB",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Tero Kivinen",null,791,"No","Self","Editorial",186,16.100000000000001,7,"This is not first use of HRP-EMDEV, do not expand here. ",null,"Do not expand here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Huan-Bang Li",null,1459,"Yes","NICT","Editorial",186,16.100000000000001,7,"replace 'a HRP' by 'an HRP'",null,"make change.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,792,"No","Self","Editorial",186,16.100000000000001,11,"This is not first use of HRP-SDEV, do not expand here. ",null,"Do not expand here.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,793,"No","Self","Editorial",186,16.100000000000001,16,"This is not first use of MMS, do not expand here. ",null,"Do not expand here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,790,"No","Self","Editorial",186,16.100000000000001,26,"This is first use of the HRP-LLDDEV properly expand it. ",null,"Change \"an HRP low-latency data device, HRP-LLDDEV\" to \"an HRP low-latency data device (HRP-LLDDEV)\". ","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,794,"No","Self","Editorial",186,16.100000000000001,32,"This is not first use of WU-RXDEV, do not expand here. ",null,"Do not expand here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Riku Pirhonen",null,960,"No","NXP Semiconductors","Editorial",186,"16.1",8,"HRP-EMDEV shall support HRP-ERDEV mandatory features when operating as a HRP-ERDEV, but it doesn't mean that ERDEV features can be mixed with EMDEV features. ",null,"\"The HRP-EMDEV shall be able to operate as a HRP-ERDEV and support he HRP-ERDEV mandatory featurs for backward compatibility in that mode, and the mandatory features of the HRP-EMDEV specified in this clause, and elsewhere in this standard.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Aniruddh Rao Kabbinale",null,233,"Yes","Samsung Electronics","Editorial",186,"16.1",11,"In the line \"An\nHRP UWB PHY device supporting these sensing modes is termed an HRP sensing device (HRP-SDEV)\" what does sensing modes mean? The definition if means to support all functionalities of SDV in section 10.39, the definition needs to be updated",null,"Update the sentence as \" An\nHRP UWB PHY device supporting all functionalities of SDEV as described in 10.39 is termed an HRP sensing device (HRP-SDEV)\"","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,795,"No","Self","Editorial",187,"16.2.1",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Frank Leong",null,98,"No","NXP Semiconductors","Technical",187,"16.2.1",14,"Suggesting interleaving is typical represents bias.",null,"Change \"are typically\" to \"may be\".","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","SENS",null,"ASSIGNED",null,"Frank"]
[null,null,"Carl Murray",null,906,"No","Qorvo","Editorial",188,"16.2.7.3",3,"I find it confusing that the PHR of a HRP-SDEV and a HRP-EMDEV are specifed under a heading for a HRP-ERDEV",null,"Create a new heading for the PHR specification of the HRP-SDEV and HRP-ERDEV or rename the heading of this section to \"PHR field in HPRF mode\" ","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,797,"No","Self","Editorial",188,"16.2.7.4.1",1,"There is Figure 195 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Carl Murray",null,907,"No","Qorvo","Editorial",188,"16.2.7.4.1",18,"The figure references a \"Dynamic rate PHR\". It should be \"Dynamic data mode PHR\"",null,"Relaces \"Dynamic rate PHR\" by \"Dynamic data mode PHR\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,796,"No","Self","Editorial",188,"16.2.7.4.1",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,798,"No","Self","Editorial",189,"16.2.7.4.2",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Frank Leong",null,99,"No","NXP Semiconductors","Technical",190,"16.2.10",25,"Splitting frequency stitiching across multiple packets is cumbersome, and results in link budget penalty, especially when using large numbers of small frequency steps.",null,"Specify {8,16,32} as optional numbers of segments inside the sensing field.","Yes",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Tero Kivinen",null,799,"No","Self","Editorial",190,"16.2.7.4.3",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,800,"No","Self","Editorial",191,"16.2.10",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Jaegook Lee",null,1468,"Yes","Samsung","Technical",191,"16.2.10",4,"According to the draft, the extended gap is employed BETWEEN active segments for the intra-packet stitching packet. This can be interpreted that the gap before the first segment or the gap after the last segment is one symbol gap, and only the gap between segments uses an extended gap. It should be clarified whether only one type of gap (one symbol or 40 symbols) is used for one packet or two types of gaps (one symbol & 40 symbols) are used for one packet as mentioned above.",null,"as in the comment","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Li-Hsiang Sun",null,263,"No","MediaTek","Technical",191,"16.2.10",8,"Is Ipatov 127 SYNC/SFD/SENS used in SENS pkt config 1 or 2",null,"Ipatov 127 SYNC/SFD/SENS are only applicable to SENS pkt config 0","No",null,null,"SENS",null,"ASSIGNED",null,"Pooria"]
[null,null,"Riku Pirhonen",null,961,"No","NXP Semiconductors","Editorial",191,"16.2.10",11,"CIR report shall be generated for those antennas that are used, not for every antenna",null,"…CIR report is generated per active SENS segment per active receiver antenna…","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1282,"No","Qorvo","Technical",191,"16.2.10 ",4,"It is a little ambiguous whether the initial and final gaps are also 40 symbols in the case of frequency stitching since the wording says \"between active segments\"",null,"Change the sentence to say: \"The gap duration shall be one preamble symbol time, except in the case of optional intra-packet frequency stitching being employed where the gap shall be 40 preamble symbol times\"","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1283,"No","Qorvo","Technical",191,"16.2.10 ",5.0999999999999996,"Since the PHY has to change frequency between the segments the sequence should be described/defined here in the PHY clause.  Suggest to define four PIB parameters to hold the channel number for each of Frequency Stitch Segment, e.g. phyFSS1channel, and define a PIB attribute phyFSEnable to enable the frequency stitch mode (making the gaps 40 when TRUE, and 1 when FALSE)",null,"Add a PHY clause paragraph to specify frequency stitching and describe the sequence, with reference to phy PIB configuration parameters, as per comment suggestion.","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1284,"No","Qorvo","Technical",191,"16.2.10 ",5.2,"For frequency stitching it is likely that the first frequency change would be wanted between the SHR and the first segment of SENS. My previous comment would allow for that. [For normal use the phyCurrentChannelInfo specifies the operating channel, so this can/should still be used to give the channel for the non-SENS parts of the sensing packet, and the whole packet when phyFSEnable is FALSE.",null,"Add some text in 10.39 to note that frequency stitching first  frequency change may be before the first SENS segment, i.e., if the channel for the first segment as specified in phyFSS1channel, is different from the phyCurrentChannelInfo.  Refer forward to the phy clause 16.2.10 where (hopefully after my previous comment) the frequency stitching operation is specified.","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Billy Verso",null,1285,"No","Qorvo","Technical",191,"16.2.10 ",5.3,"Can we state that Frequency Stitching only applies to SENS packet configuration zero? Or is it envisioned to be relevant to the other SENS packet configurations? It would seem to be problematical for SENS packet configuration one.",null,"State that when Frequency Stitching is enabled the packet format shall be SENS packet configuration zero","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Carl Murray",null,908,"No","Qorvo","Editorial",191,"16.2.11.1",12,"typo \"first RSF or RIF transmitted\"\n\nAlthough the 'F' refers to fragment, in the rest of the text the RIFs and RSFs are referred to as RIF fragments and RSF fragments.  So change here for consistency.",null,"Replace\n\n\"first RSF or RIF transmitted\"\n\n\"first RSF or RIF transmitted fragment\"\n\nAlso search for other similar inconsistencies and do the same (eg there is another example in the same paragraph)","Yes","Revised","change to \"first RSF or RIF fragment transmitted£","TE",null,"DONE"]
[null,null,"Tero Kivinen",null,801,"No","Self","Editorial",192,"16.2.11.1",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,803,"No","Self","Editorial",192,"16.2.11.1",4,"This is not first use of RSF, do not expand here. ",null,"Do not expand here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Pooria Pakrooh",null,1381,"No","Qualcomm","Technical",192,"16.2.11.1",4,"Figure 198 and text below it are confusing. SYNC/SFD are part of UWB driven packet, not NBA packet.",null,"Specify that \" SYNC/SFD are part of UWB driven packet, not NBA packet.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Tero Kivinen",null,802,"No","Self","Editorial",192,"16.2.11.1",5,"This is not first use of RIF, do not expand here. ",null,"Do not expand here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Xiliang Luo",null,10,"Yes","Apple","Editorial",192,"16.2.11.1",6,"Typo: UWM",null,"Change UWM to UWB","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Pooria Pakrooh",null,1382,"No","Qualcomm","Editorial",192,"16.2.11.1",6,"Change \"UWM\" to \"UWB\"",null,"Change \"UWM\" to \"UWB\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Huan-Bang Li",null,1460,"Yes","NICT","Editorial",192,"16.2.11.1",6,"replace 'UWM MMS' by 'UWB MMS'.",null,"make change.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Xiliang Luo",null,11,"Yes","Apple","Technical",192,"16.2.11.1",8,"We should include the clarification texts we have approved in doc#: 15-24-0139-05-04ab for CID #878.",null,"Add the following paragraph between line 8 and line 9:\n\nIn the case of NBA UWB MMS, another narrowband PHY packet precedes the RSF/RIFs and assists the MMS to provide this initial synchronization.\n\nIn the case of UWB-driven UWB MMS, the RSFs or RIFs are preceded by a fragment consisting of SYNC and SFD that is used to obtain initial timing and frequency synchronization.","Yes",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Billy Verso",null,1286,"No","Qorvo","Technical",192,"16.2.11.1",11,"The text should probably say that the SYNC+SFD (SHR) when present is also on ms boundary,",null,"Add at the end of the paragraph: \"The SHR fragment (SYNC and SDF) where present shall begin on the same millisecond grid as the other fragments, i.e., one millisecond offsets before T0, as shown in Figure 198.\"","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Carl"]
[null,null,"Mickael Maman",null,93,"Yes","STMicroelectronics","Technical",192,"16.2.11.1",14,"Where the MMS packet consists of both RSF and RIF fragments, the time between the start of the last RSF and the start of first RIF shall be at least two milliseconds.",null,"as in comment","Yes",null,null,"MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Tero Kivinen",null,804,"No","Self","Editorial",192,"16.2.11.1",15,"X and Y are variables, change them to italics. ",null,"Change to italics through this section.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Frank Leong",null,100,"No","NXP Semiconductors","Technical",192,"16.2.11.1",32,"MMS operation should not be exclusively interleaved.",null,"Change \"are interleaved\" to \"may be interleaved\".","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Frank"]
[null,null,"Riku Pirhonen",null,962,"No","NXP Semiconductors","Technical",192,"16.2.11.1",32,"Add word typically to reflect that also non-interleaved packets could be used in case of proposed non-interleaved mode.",null,"… the fragment transmissions of the transmitted MMS packets are typically interleaved …","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx","MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Riku Pirhonen",null,964,"No","NXP Semiconductors","Technical",192,"16.2.11.2",23,"In UWB-driven operation RSF (X) length is given as 1 to 8. To align with the NBA mode, RSF could take values up to 16. ",null,"RSF only MMS packets, i.e., where Y=0 and X ∈ {1, 2, 4, 8, 16}.","Yes",null,null,"MMS",null,"ASSIGNED",null,"Xiliang"]
[null,null,"Bernhard Großwindhager",null,1420,"No","NXP","Technical",192,"16.2.11.2",23,"RSF length is given as 1 to 8. I propose to allow values up to 16.",null,"{1, 2, 4, 8, 16}","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Carl"]
[null,null,"Carl Murray",null,909,"No","Qorvo","Editorial",193,"16.2.11.2",3,"The text \"is formed using one of a possible sixteen length-128 sequences given in Table 63\" is not very clear",null,"Change to \"is formed using one of the sixteen length-128 sequences given in Table 63\"","Yes","Revised","change \"one of a possible sixteen\" to \"one of the\"","TE",null,"DONE"]
[null,null,"Huan-Bang Li",null,1461,"Yes","NICT","Editorial",193,"16.2.11.2",3,"replace ' a possible sixteen' by ' sixteen possible'.",null,"make change.","Yes","Revised","change \"one of a possible sixteen\" to \"one of the\"","TE",null,"DONE"]
[null,null,"Huan-Bang Li",null,1462,"Yes","NICT","Editorial",193,"16.2.11.2",7,"add 'in' before 'Table 16-8'.",null,"make change.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Riku Pirhonen",null,963,"No","NXP Semiconductors","Technical",193,"16.2.11.2",8,"When Ipatov codes are used as RSF, MMRS is identical to the preamble and similar length RSF identical to SYNC. By adding the same SFD as in SHR at end of each Ipatov-RSF, each RSF could act as a SHR in case the first SHR is lost e.g. due to interference. This improves the robustness of ranging as the sequence is not necessarily lost in case the first SHR is lost. ",null,"Continue on line 8: \"When these codes are used, a copy of the SFD sequence is added at the end of each RSF. RSF consists of MMRS repetitions and SFD, and can be identical to the initial SHR (SYNC+SFD) fragment\"","Yes",null,null,"MMS",null,"ASSIGNED",null,"Riku/Carl"]
[null,null,"Tero Kivinen",null,806,"No","Self","Editorial",193,"16.2.11.2",10,"This is not first use of MSR, do not expand here. ",null,"Do not expand here.","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,805,"No","Self","Editorial",193,"16.2.11.2",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,910,"No","Qorvo","Editorial",194,"16.2.11.3",3,"The text \"Scrambled timestamp sequence (STS) field\" has an odd style. Also it is not the norm to give the heading when giving a section reference.",null,"Either make the style consistent or delete the text altogether","Yes","Revised","Delete the italisised \", Scrambled timestamp sequence (STS) field\" leaving just the clause reference to \"16.2.9\".","TE",null,"DONE"]
[null,null,"Billy Verso",null,1287,"No","Qorvo","Technical",194,"16.2.11.3",7,"It would make most sense to have a single AES PRNG for STS, and have the same SEED (Key and IV) set up at both ends of the link. Then, since RIF transmissions from initiator and responder are interleaved, the PRNG output should be consumed sequentially at both ends of the link, alternatively generating the sequence for transmission, and the sequence for cross-correlation in the receiver.",null,"I will prepare a submission to cover this.","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Billy"]
[null,null,"Tero Kivinen",null,809,"No","Self","Editorial",195,"16.3.3.4",1,"The PDF index has Table 64, Figure 199, Table 65-68, Figure 200. ",null,"Remove Table and Figure entries from the PDF index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,807,"No","Self","Editorial",195,"16.3.3.4",5,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,808,"No","Self","Editorial",195,"16.3.3.4",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,810,"No","Self","Editorial",196,"16.3.3.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,811,"No","Self","Editorial",196,"16.3.3.4",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,812,"No","Self","Editorial",197,"16.3.3.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,813,"No","Self","Editorial",197,"16.3.3.4",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,814,"No","Self","Editorial",198,"16.3.3.4",17,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,815,"No","Self","Editorial",198,"16.3.4.1",1,"There is Table 16-22 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Shang-Te Yang",null,922,"Yes","Apple","Editorial",200,"16.3.4.2",1,"It's not obvious on the first read which PRF the title is referring to. ",null,"Add \"Mean PRF\" to the title. ","No","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,818,"No","Self","Editorial",200,"16.3.4.2.1",1,"There is Table 69 and Figure 201-202 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,816,"No","Self","Editorial",200,"16.3.4.2.1",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,817,"No","Self","Editorial",200,"16.3.4.2.1",15,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Carl Murray",null,911,"No","Qorvo","Technical",200,"16.3.4.2.1",19,"It is not clear what i0 is referring to in this text \"with the initial bit i0 considered to be even numbered\"",null,"Change to \"with the initial bit i0 of the LDPC codeword considered to be even numbered\"\n\nSimilarly on (pg 202, line 4) , (pg 203, line 13), (pg 204, line 13), (pg 207, line 8)\n","Yes","Accepted",null,"LDPC",null,"DONE"]
[null,null,"Tero Kivinen",null,819,"No","Self","Editorial",201,"16.3.3.4",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,820,"No","Self","Editorial",201,"16.3.4.2.2",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
["d",null,"Tero Kivinen",null,821,"No","Self","Editorial",201,"16.3.4.2.2",14,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,822,"No","Self","Editorial",201,"16.3.4.2.3",1,"There is Table 70 and Figure 203-204 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,823,"No","Self","Editorial",202,"16.3.4.2.2",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,825,"No","Self","Editorial",202,"16.3.4.2.3",1,"There is Table 71 and Figure 16-18 - 16-19 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,824,"No","Self","Editorial",202,"16.3.4.2.3",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,826,"No","Self","Editorial",204,"16.3.4.3.1",1,"There is Figure 16-20, 16-21 and Table 16-25, 16-26 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,827,"No","Self","Editorial",206,"16.3.4.3.2",1,"There is Figure 205-206 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,830,"No","Self","Editorial",207,"16.3.4.3.2",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,829,"No","Self","Editorial",207,"16.3.4.3.2",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,828,"No","Self","Editorial",207,"16.3.4.3.2",10,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,831,"No","Self","Editorial",207,"16.3.4.4",1,"There is Figure 207 and Table 73 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Huan-Bang Li",null,1463,"Yes","NICT","Editorial",208,"16.1.4.2",19,"use of 'mitigate against' is rare and nonstandard.",null,"delete 'against'.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,832,"No","Self","Editorial",208,"16.3.4.4",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,833,"No","Self","Editorial",208,"16.3.4.4",7,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,834,"No","Self","Editorial",209,"16.4.4",1,"There is Figure 208 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tushar Patel",null,1422,"Yes","LitePoint","Technical",209,"16.4.4",12,"Section 16.4.4 line #12 - 28 defines cross correlaion requirement for sensing pulse. Can we add sample plots that display reference cross correlation? Similar to base spec 802.15.4-2020",null,"Add Sample cross correlation plots similar to base specification 802.15.4-2020","No",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Riku Pirhonen",null,965,"No","NXP Semiconductors","Technical",209,"16.4.4",14,"Cross-correlation test and time domain mask are two overlapping requirements. Cross correlation test is superseded by time domain mask test, so it can be removed. ",null,"Remove lines 14 - 28, from the text starting with \"The transmitted pulse shape…\" until \"... as |ϕ(τi)| ≤ 0.1 for all τi.\" ","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Bernhard Großwindhager",null,1421,"No","NXP","Technical",209,"16.4.4",14,"It is sufficient to have time domain mask, hence, I propose to remove cross-correlation requirement.",null,"Respective lines should be removed.","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Bin Qian",null,178,"No","Huawei","Technical",209,"16.4.4",18,"According to the definition of L, this duration of the pulse corresponds to UWB channel with 500 MHz. Regarding some UWB channels with larger bandwidth, the definition of L should be updated accordingly",null,"Change the definition of L to be the duration of the pulse which is 3Tp. Tp is defined in Table 16-28","Yes",null,null,"PHYHRP",null,"ASSIGNED",null,"Bin Q"]
[null,null,"Huan-Bang Li",null,1464,"Yes","NICT","Editorial",210,16.7,12,"rates of' is redundant.",null,"delete it.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Henk de Ruijter",null,1467,"Yes","Silicon Labs","Editorial",210,"16.4.4",1,"Figure 208 does not show time defenition (of x-axis)",null,"Add time unit",null,"Revised","Move the time unit text, \"Time (Tp)\", down so it appears below the x-axis figures, rather thn below the zero relative amplitude axis.","TE",null,"DONE"]
[null,null,"Tero Kivinen",null,835,"No","Self","Editorial",210,"16.4.4",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tushar Patel",null,1423,"Yes","LitePoint","Editorial",210,"16.7",8,"Line # 8 reads \"operating modes of Table 16-31 and Table 16-32 and in addition shall support those of those Table 74.\" ",null,"Proposing  to change line#8 as \"operating modes of Table 16-31 and Table 16-32 and in addition shall support those of Table 74\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,836,"No","Self","Editorial",211,16.7,1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,837,"No","Self","Editorial",211,"16.8.1",1,"There is Figure 209 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1288,"No","Qorvo","Technical",211,"16.8.1",23,"Looking at the numbers here, 24µs is not an even multiple of UWB chip times (11980.8 chips), propose 25µs as a better number for implementation.",null,"Change inter-burst spacing to 25µs, making Tws = 1.025 ms, in text and figure, and data rate figure to \"approximately 976 b/s\".","Yes","Accepted",null,"PHYHRP",null,"DONE"]
[null,null,"Tero Kivinen",null,838,"No","Self","Editorial",212,"16.8.1",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,840,"No","Self","Editorial",212,"16.8.2",1,"There is Figure 210 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,839,"No","Self","Editorial",212,"16.8.2",16,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,841,"No","Self","Editorial",213,19,1,"PDF Index has subsections under clause 19. ",null,"Remove extra PDF index entries for 19.x.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Billy Verso",null,1289,"No","Qorvo","Technical",214,33.1,13.5,"It is not clear from the text what data rates are supported by this PHY.  This should be clarified with the aid of a table.  The end of the introduction clause is a good place to do this.",null,"Insert a paragraph beginning \"The data rates supported by the LE-PHY in its various modulation modes is given by Table X\", and insert new Table X that lists the modulation modes and resultant PSDU bit rates available to the MAC after the PHY level coding is taken into account.","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Billy Verso",null,1290,"No","Qorvo","Editorial",214,"33.2.1",17,"No \"period\"/\"full stop\" at the end of the line",null,"Insert \".\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Billy Verso",null,1291,"No","Qorvo","Technical",214,"33.2.1",18,"For clarity, since there are no gaps in the PPDU between SHR, PHR and PSDU, these should be drawn as abutting each other. ",null,"Draw SHR, PHR and PSDU, boxes in contact with each other, ","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Tero Kivinen",null,842,"No","Self","Editorial",214,"33.2.1",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,843,"No","Self","Editorial",214,"33.2.3",1,"There is Figure 211 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,846,"No","Self","Editorial",215,"33.2.3",1,"There is Figure 212 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,844,"No","Self","Editorial",215,"33.2.3",19,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,845,"No","Self","Editorial",215,"33.2.5.1",1,"There is Figure 213 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,848,"No","Self","Editorial",216,"33.2.5.1",2,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,849,"No","Self","Editorial",216,"33.2.5.3",1,"There is Table 75 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,847,"No","Self","Editorial",216,"33.2.5.3",12,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,852,"No","Self","Editorial",217,"33.2.6.1",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,854,"No","Self","Editorial",217,"33.2.6.1",1,"The figure does not follow normal structure of figures used for frames in working group, ",null,"Redraw figure 214 to match normal structure.","No",null,null,"TE",null,"ASSIGNED",null,"Editor"]
[null,null,"Tero Kivinen",null,853,"No","Self","Editorial",217,"33.2.6.2",1,"There is Table 76-79 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,855,"No","Self","Technical",217,"33.2.6.2",4,"XNOR is not commonly used operation, explain what it is. ",null,"Add text explaining what XNOR operator does.","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Tero Kivinen",null,850,"No","Self","Editorial",217,"33.2.6.2",6,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,851,"No","Self","Editorial",217,"33.2.6.2",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,856,"No","Self","Technical",217,"33.2.6.2",11,"I assume there should be more than one column in the tables 77, 78, and 79. They now just lists parameters, but I would have assumed there be some number or something that is needed also. ",null,"Actually it seems the table 77, 78, 79 are not really used anywhere, they just list some configuration parameters that can be configured, but no way of configuring them. Remove tables 77, 78, 79.","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Tero Kivinen",null,857,"No","Self","Editorial",218,"33.2.6.2",1,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,858,"No","Self","Editorial",218,"33.2.6.2",3,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Kangjin Yoon",null,1419,"No","Spark Microsystems","Editorial",218,"33.2.6.3.1",9,"Use octet instead of byte for consistency.",null,"Change \"bytes\" to \"octets\"","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Huan-Bang Li",null,1465,"Yes","NICT","Editorial",219,"33.2.7",3,"a period is missed for the first sentence.",null,"add a period at the end of sentence.","Yes","Accepted",null,"TE",null,"DONE"]
[null,null,"Tero Kivinen",null,859,"No","Self","Editorial",219,"33.2.7",8,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,861,"No","Self","Editorial",220,"33.3.3",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,860,"No","Self","Editorial",220,"33.3.3",13,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yyz, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, and z is next free number. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,862,"No","Self","Editorial",221,"33.3.4",4,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Tero Kivinen",null,864,"No","Self","Editorial",221,"33.3.5",1,"There is Figure 218 in the PDF index. ",null,"Remove Table/Figure entries from the PDF Index.","No",null,null,"TE",null,"ASSIGNED","PI","Editor"]
[null,null,"Tero Kivinen",null,863,"No","Self","Editorial",221,"33.3.5",11,"Table/figure number is wrong. ",null,"The table/figure numbers needs to have format xx-yy, where xx is the clause number and yy is the figure/table number after which the table/figure should be added, in this case 33-xx as this is new clause. Fix the table/figure number. ","No",null,null,"TE",null,"ASSIGNED","FTN","Editor"]
[null,null,"Billy Verso",null,1292,"No","Qorvo","Technical",221,"33.4.3",19,"Both Pulse shape and PSD mask specifications refer to PSD mask and clause 16.4.5 in the base standard. Is this correct or should the pulse shape text be referring to the pulse shape clause of 16.4.4 or defining a pulse shape here.",null,"Consider, see comment, to change to refer to clause 16.4.4.","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Tero Kivinen",null,865,"No","Self","Technical",223,"Annex E",1,"The modifications to the Annex E PICS are missing. ",null,"Add PICS entries for all the new features specified in this amendment.","Yes",null,null,"PHYLE",null,"ASSIGNED",null,"Larry"]
[null,null,"Stefan Lemsitzer",null,8,"No","NXP","Technical",null,"16.2.1",13,"PPDUs can also be transmitted sequentially, propose to make this a \"may\" statement",null,"“In this MMS mode, the transmission and reception of the PPDU fragments are typically may be interleaved.”","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx",null,null,"ASSIGNED",null,"Billy"]
[null,null,"Stefan Lemsitzer",null,9,"No","NXP","Technical",null,"16.2.11.1",31,"In some ranging protocols, it may be beneficial if no interleaving is used. Propose to make this a \"may\" statement",null,"“For two-way ranging (TWR) with MMS packets, the fragment transmissions of the transmitted MMS packet aremay be interleaved with fragment receptions of the received MMS response packet.”","Yes",null,"doc 15-24-0409-00-04ab-non-interleaved-mms.pptx",null,null,"ASSIGNED",null,"Billy"]
[null,null,"Harry Bims",null,1471,"Non-Voter",null,"General",13,null,23,"My feedback on P802.15.4ab relates to the lone new definition of the draft for the term “sensing” (see line 23 of page 13).\n\nThis term is already used in multiple places in P802.15.4/D06, and P802.15.4ab is an amendment to this base standard. Thus, eventually this definition will be incorporated into a future base standard.\n\nMy concern is that the new definition of the word “sensing” will result in a technical change to the base standard.  In particular the areas of concern are:\n\na) the definition begins with “receiving radio signals scattered from physical targets” does not make clear whether sensing is limited to the particular sensing modes described in this draft, or extends more universally across all sensing described in the base standard.\n\nb) I would imagine the intent is not to limit sensing to signals that are “scattered”, but to also include reflection off targets.\n\nc) P802.15.4/D06 uses the term sensing with respect to the channel, not physical targets\n\n         1. line 15, p. 324:  “the backoff timer shall be suspended until sensing the channel indicates that the channel is clear” ",null,null,"Yes","Revised","Change to “UWB sensing” in the 4ab draft (everywhere outside 10.39 and 15, bulk replace; in 10.39 and 16 add to intro):\nChange to “UWB sensing” in front matter, clause 3, clause 8, 10.29.9, 10.32.2, 10.32.3, change title of 10.39 to “UWB sensing” and add in 10.39.1 “As used in this clause, “sensing” refers to UWB Sensing;  Same note in 16\nChange “scattered” to “reflected” in definition",null,null,"Ready"]

{"sheet":"Progress-Status","index":1,"n_rows":497,"n_cols":26,"rows_kept":497,"cut":false,"hidden":false,"merged":[[1,10,1,18],[6,4,6,6],[10,10,10,16],[1,1,1,8],[18,1,18,23]]}
[]
[null,"Comments and Resolution Status",null,null,null,null,null,null,null,null,"Draft editing Status"]
[]
[null,"Total #  Comments","# with Blank resolution","# with non-blank resolution","# with \"Rejected\" resolution","# with \"Accepted\" resolution","# with \"Revised\" resolution","# Assigned","No Resolution, not Assigned",null,"DONE","N/A",null,"PART","Ready","ISSUE","ASSIGNED",null,"Blanks"]
[null,{"$f":"COUNTA(Comments!E:E)-1","v":1471},{"$f":"B5-D5","v":1278},{"$f":"COUNTA(Comments!P:P)-1","v":193},{"$f":"COUNTIF(Comments!P:P,\"Rejected\")","v":12},{"$f":"COUNTIF(Comments!P:P,\"Accepted\")","v":130},{"$f":"COUNTIF(Comments!P:P,\"Revised\")","v":51},{"$f":"COUNTA(Comments!V:V)-1","v":1278},{"$f":"B5-D5-H5","v":0},null,{"$f":"COUNTIF(Comments!T:T,K4)","v":154},{"$f":"COUNTIF(Comments!T:T,L4)","v":12},null,{"$f":"COUNTIF(Comments!T:T,N4)","v":0},{"$f":"COUNTIF(Comments!T:T,O4)","v":27},{"$f":"COUNTIF(Comments!T:T,P4)","v":0},{"$f":"COUNTIF(Comments!T:T,Q4)","v":1278},null,{"$f":"B5-(COUNTA(Comments!T:T)-1)","v":0}]
[]
[null,"Technical","Editorial",{"$f":"IF(D5=E7,\"Okay\",\"MIS-MATCHED\")","v":"Okay"},{"$f":"E5+F5+G5","v":193},null,null,null,null,null,{"$f":"SUM(K5:L5)","v":166},"Done + N/A"]
[null,{"$f":"COUNTIF(Comments!H:H,B7)","v":854},{"$f":"COUNTIF(Comments!H:H,C7)","v":611}]
[null,"General",{"$f":"IF(B5=C10,\"Okay\",\"MIS-MATCHED\")","v":"Okay"},{"$f":"D5/$B5","v":0.13120326308633581},8.1577158395649222E-3,8.8375254928619987E-2,3.4670292318150921E-2,0.86879673691366421,0,null,{"$f":"K7/$B$5","v":0.11284840244731476},"of total",null,{"$f":"N5/$B$5","v":0},{"$f":"O5/$B$5","v":1.8354860639021073E-2},{"$f":"P5/$B$5","v":0},{"$f":"Q5/$B$5","v":0.86879673691366421},null,{"$f":"S5/$B$5","v":0}]
[null,{"$f":"COUNTIF(Comments!H:H,B9)","v":6},{"$f":"C8+B8+B10","v":1471}]
[null,null,null,null,null,null,null,null,null,null,{"$f":"K9+SUM(N9:Q9)","v":1}]
[]
[]
[]
[]
[]
[]
[]
[null,"Assigned Comments"]
[]
[null,"Alex","Aniruddh","Ben","Billy","Bin Q","Carl","Carlos","Editor","Frank","Hongwon","Jinjing",null,"Kanjing","Larry","Mickael","Pooria",null,"Riku/Carl","Rojan","Tero","Vinod","Youngwan","Xiliang",null,"SUM"]
[null,{"$f":"COUNTIF(Comments!V:V,B21)","v":240},{"$f":"COUNTIF(Comments!V:V,C21)","v":9},{"$f":"COUNTIF(Comments!V:V,D21)","v":5},{"$f":"COUNTIF(Comments!V:V,E21)","v":27},{"$f":"COUNTIF(Comments!V:V,F21)","v":34},{"$f":"COUNTIF(Comments!V:V,G21)","v":10},{"$f":"COUNTIF(Comments!V:V,H21)","v":2},{"$f":"COUNTIF(Comments!V:V,I21)","v":528},{"$f":"COUNTIF(Comments!V:V,J21)","v":4},{"$f":"COUNTIF(Comments!V:V,K21)","v":32},{"$f":"COUNTIF(Comments!V:V,L21)","v":45},null,{"$f":"COUNTIF(Comments!V:V,N21)","v":28},{"$f":"COUNTIF(Comments!V:V,O21)","v":7},{"$f":"COUNTIF(Comments!V:V,P21)","v":0},{"$f":"COUNTIF(Comments!V:V,Q21)","v":80},null,{"$f":"COUNTIF(Comments!V:V,S21)","v":10},{"$f":"COUNTIF(Comments!V:V,T21)","v":92},{"$f":"COUNTIF(Comments!V:V,U21)","v":1},{"$f":"COUNTIF(Comments!V:V,V21)","v":0},{"$f":"COUNTIF(Comments!V:V,W21)","v":114},{"$f":"COUNTIF(Comments!V:V,X21)","v":10},null,{"$f":"SUM(B22:X22)","v":1278}]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Alex, if he agrees, since he has other comments on the same part of the doc already assigned to him."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #782 is already assigned to him"]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #783 is already assigned to him"]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #786 is already assigned to him"]

{"sheet":"Categories","index":2,"n_rows":497,"n_cols":23,"rows_kept":497,"cut":false,"hidden":false,"merged":[]}
["MMS w/NBA","MMS wo/NBA","New frame format","Ack changes","RSS","SSBD","Other channel access","Security","Multi-node ranging / Hyper Block","Narrow Band function","Device discovery Ranging","Device discovery Data","Parameter Negotiation","Wake-up Radio","UWB data offload","Narrow Band PHY","UWB PHY HRP","UWB PHY LE","Sensing","Dynamic Data Rate Mode","PICS","IEs","OTHER"]
["NBMSS","UWBMSS","NEWFR","ACK","RSS","SSBD","CHA","SEC","HB","NBF","DISC-R","DISC-D","PARNEG","WUR","UWBDO","PHYNB","PHYHRP","PHYLE","SENS","DDRN","PICS",null,"OTHER"]
["Alex","Carl","Alex","Billy","Sven","Larry","Ben","Rojan","Youngwan","Alex","Alex","[Carlos]","Billy","Billy","Youngwan","Bin Q","Vinod","Larry","Pooria & Bin Q","[Carlos]"]
[]
[]
[]
[null,null,null,null,null,"11.2.8"]
[null,null,null,null,null,"12.3.2"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Alex, if he agrees, since he has other comments on the same part of the doc already assigned to him."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #782 is already assigned to him"]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #783 is already assigned to him"]
[]
[]
[]
[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"Was Editorial now Technical, Needs Assignment. Perhaps to Jinjing since a similar comment #786 is already assigned to him"]

{"sheet":"Detailed Status","index":3,"n_rows":4,"n_cols":21,"rows_kept":4,"cut":false,"hidden":false,"merged":[[2,10,2,19],[3,10,3,19],[0,9,0,20],[1,9,1,20],[0,1,0,3],[1,1,1,3],[0,6,0,8],[1,6,1,8],[0,4,0,5],[1,4,1,5]]}
["Resolution","Accepted",null,null,"Rejected",null,"Revised",null,null,"Blank"]
[null,{"$f":"COUNTIF(Comments!P:P,\"Accepted\")","v":130},null,null,{"$f":"COUNTIF(Comments!P:P,\"Rejected\")","v":12},null,{"$f":"COUNTIF(Comments!P:P,\"Revised\")","v":51},null,null,0]
["Editor Status","ISSUE","Ready","DONE","Waiting","N/A","ISSUE","Ready","DONE","Ready","Assigned",null,null,null,null,null,null,null,null,null,"Unassigned"]
[null,0,0,0,0,0,0,0,0,0,0,null,null,null,null,null,null,null,null,null,0]

{"sheet":"To-Do","index":4,"n_rows":0,"n_cols":0,"rows_kept":0,"cut":false,"hidden":false,"merged":[]}

{"sheet":"Historical Status","index":5,"n_rows":26,"n_cols":34,"rows_kept":26,"cut":false,"hidden":false,"merged":[[7,0,13,0],[14,0,24,0]]}
["Version",null,"-00","-01","-02","-03","-04","-05","-06","-07","-08","-09",null,"-14","-15","-16","-17","-18","-19",null,"-21","-22",null,"-24","-25","-26","-27","-28","-29","-30","-31","-32","-33,-34","-35"]
["Date",null,"2024-07-14","2024-07-16","2024-07-18","2024-07-30","2024-07-30",null,"2024-08-08","2024-08-13",null,"2024-08-22"]
["Occasion",null,"Initial spreadsheet",null,"End of 2024-07 session","Before 2024-07-30 telecon","After 2024-07-30 telecon",null,"After 2024-08-08 telecon","Before 2024-08-13 telecon",null,"After 2024-08-22 telecon"]
[]
[]
[]
[]
["Editorial","Total",614,614,611,611,611,null,611,611,null,611]
[null,"Addressed",0,3,3,51,51,null,51,84,null,84]
[null,"Ready",0,2,2,2,2,null,0,0,null,0]
[null,"Done",0,0,0,47,47,null,49,81,null,81]
[null,"N/A",0,1,1,2,2,null,2,3,null,3]
[null,"ISSUE",0,0,0,0,0,null,0,0,null,0]
[null,"To Be Addressed",614,611,608,560,560,null,560,527,null,527]
["Technical/General","Total",856,856,859,859,860,null,860,860,null,860]
[null,"Addressed",0,29,65,65,66,null,80,80,null,109]
[null,"Ready",0,27,59,54,55,null,14,1,null,27]
[null,"Done",0,0,0,5,5,null,60,73,null,73]
[null,"N/A",0,2,6,6,6,null,6,6,null,9]
[null,"To Be Addressed",856,825,794,794,794,null,780,780,null,751]
[null,"Assigned",0,825,794,794,794,null,780,780,null,751]
[null,"Proposed Resolutions",0,10,47,47,47,null,53,53,75,61]
[null,"Need Proposals",0,815,747,747,747,null,727,727,705,690]
[null,"Not Assigned",856,0,0,0,0,null,0,0,null,0]
[null,"Issue",0,0,0,0,0,null,0,0,null,0]
["Blank","Total"]

{"sheet":"CAD","index":6,"n_rows":48,"n_cols":22,"rows_kept":48,"cut":false,"hidden":false,"merged":[]}
["Comment ID","Comment #","Name","Style","Index #","Vote","Affiliation","Category","Page","Sub-clause","Line #","Comment","File","Proposed Change","Must Be Satisfied?","Disposition Status (Accepted, Rejected, Revised)","Disposition Detail","Category","Notes","Editor Status DONE, Ready, N/A)","Editor Notes","Assignee"]
[null,null,null,null,"CAD015",null,null,"Editorial",3,1,2,"802.19 comment from Kazuto Yano on CA document: \"assesment\" must be \"assessment\".",null,"Please fix this typo.","No","Accepted"]
[null,null,null,null,"CAD012",null,null,"Technical",3,1,9,"802.19 comment from Kazuto Yano on CA document: In Clause 1, 802.15.6 is noted that it is to be considered. However, Clause 5 where coexistence between 802.15.6 and 802.15.4ab would be discussed is blank.",null,"Please discuss the coexistence between 802.15.6 and 802.15.4ab.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,"CAD044",null,"Apple","Editorial",3,"1.1","not sure","More acronyms are used in the document without declaration.",null,"Add OFDM, O-QPSK, PHY, WLAN, MAC, ACK, NACK to the list of abbreviations.","Yes"]
[null,null,null,null,"CAD001",null,null,"Editorial",5,2,6,"802.19 comment from Billy Verso on CA document: Repetition on 5th line of first paragraph \"the original UWB PHY was renamed the original UWB PHY was renamed\"",null,"Replace with a single \"the original UWB PHY was renamed\"","No","Accepted"]
[null,null,null,null,"CAD002",null,null,"Editorial",5,2,9,"802.19 comment from Billy Verso on CA document: Using HRP (or LRP) on its own is not correct, nor is \"HRP PHY\".  It should always be written as the HRP UWB PHY, and, the LRP UWB PHY.",null,"Change to \"The HRP channel plan\" to \"The HRP UWB PHY channel plan\", and review other occurrences of HRP and LRP to similarly correct them.","No","Accepted"]
[null,null,null,null,"CAD003",null,null,"Technical",5,2,11,"802.19 comment from Billy Verso on CA document: In third line of 2nd paragraph, \"optional wider channels (from 1.2 to 1.5 GHz).\", is slightly wrong.  The HRP UWB PHY Channel 7 is 1081.6 MHz bandwidth, which rounds to 1.1 GHz, while the widest channel #15 is 1354.97 MHz bandwidth.",null,"Change to \"optional wider channels (from 1.1 to 1.4 GHz).\"","No","Accepted"]
[null,null,null,null,"CAD038",null,null,"Editorial",5,2,null,"802.19 comment from Dorothy Stanley on CA document: Duplicate text \"the original UWB PHY was renamed\"",null,"Delete one of the repeated phrases","Yes","Accepted"]
[null,null,null,null,"CAD008",null,null,"General",5,"2.1.1",50,"802.19 comment from Stephan Sand on CA document: The document is incomplete.",null,"Add detail on channel plans,\nalso on P6L3 a reference is broken,\nheading 2.1.3 should read Summary of Amendment 802.15.4ab\nSection 5 is empty\nSection 6 is empty","No",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD037",null,null,"Technical",5,"2.1.1",null,"802.19 comment from Dorothy Stanley on CA document: \"[can provide details of the channel plans] - the text appears incomplete. Either provide the details or provide a reference to the details.",null,"As in comment.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD018",null,null,"Editorial",6,"2.1.2",2,"802.19 comment from Stephen Shellhammer on CA document: There is a reference error in the document",null,"Fix the reference error","No","Accepted"]
[null,null,null,null,"CAD013",null,null,"Editorial",6,"2.1.2",3,"802.19 comment from Kazuto Yano on CA document: There is a reference error denoted by \"Error! Reference source not found.\"",null,"Please fix the reference error.","Yes","Accepted"]
[null,null,"Alex Krebs",null,"CAD045",null,"Apple","Editorial",6,"2.1.2","Table 1","Different font sizes in partially unfilled table",null,"User greater of the font sizes for all cells, remove empty cells","Yes"]
[null,null,null,null,"CAD039",null,null,"Technical",6,"2.1.2",null,"802.19 comment from Dorothy Stanley on CA document: 5935 or 5945? https://mentor.ieee.org/802-ec/dcn/22/ec-22-0266-00-WCSG-ieee-802-s-wireless-standards-table-of-frequency-ranges.xlsx indicates 5945.",null,null,"Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,"CAD040",null,"Apple","Editorial",7,"2.2","3 from page bottom","Typo \"liner\"",null,"Change to \"linear\"","Yes"]
[null,null,null,null,"CAD004",null,null,"Technical",7,2.2000000000000002,23,"802.19 comment from Billy Verso on CA document: On the last line of the 1st paragraph of 2.2, the parenthssiesd \"(and under some rules required)\" is a little unclear in meaning.  Suggest to use the term \"regulatory domains\".",null,"Change to \"(and in some regulatorydomains required)\".","No","Accepted"]
[null,null,null,null,"CAD005",null,null,"Technical",7,2.2000000000000002,24,"802.19 comment from Billy Verso on CA document: Sentence, 1st line of 2nd paragraph of 2.2,  \"CCA modes support preamble detection, energy detect, and Aloha.\" is missing mention of \"Carrier Sense\" mode.",null,"Change ot \"The 802.15.4 standard includes several CCA modes including: energy detection, carrier detrection, preamble detection and aloha.\"","No",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD011",null,null,"Technical",7,2.2000000000000002,null,"802.19 comment from Menzo Wentink on CA document: \"CCA modes support preamble detection, energy detect, and Aloha. There are many (very) different PHYs defined in 802.15.4, with very different signal structures and preambles. Thus no single preamble detection mechanism can be effective in the typical shared spectrum environment where multiple PHYs may be in operation.\"\n\nThe use of the word \"support\" is questionable here because energy detect is not mandatory in 802.15.4. Energy detect may just as well not be supported by an 802.15.4ab device even when it is defined in the standard. Energy detect is the only way to protect ongoing transmissions from other technologies, so it should be mandatory on the narrowband (NB) transmissions.\n\nThe power spectral density (PSD) difference between NB and wideband makes that NB may not be inherently motivated to defer for Wi-Fi, since a collision between the two will have much less impact on the NB signal than on the Wi-Fi signal. The LBT requirement should therefore be enforced through the standard.",null,"802.15.4ab narrowband (NB) transmissions should use listen before talk (LBT). Offline scanning can be used to identify spectrum where the clear channel assessment (CCA) will have the highest probability of being idle.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,"CAD043",null,"Apple","Technical",8,"3","3rd in paragraph","IR-UWB is unknown/undefined",null,"Say what IR-UWB is, or reference.","Yes"]
[null,null,null,null,"CAD006",null,null,"Editorial",8,"3.1.1",15,"802.19 comment from Billy Verso on CA document: Typo, \"Thes\", 1st line 2nd paragraph of 3.1.1.",null,"Change \"Thes\" to \"These\".","No","Accepted"]
[null,null,null,null,"CAD017",null,null,"Editorial",8,"3.1.1",16,"802.19 comment from Kazuto Yano on CA document: \"Thes\" must be \"These\".",null,"Please fix this typo.","No","Accepted"]
[null,null,"Alex Krebs",null,"CAD046",null,"Apple","Editorial",9,"3.1.2.1",10,"Different font face used.",null,"Use same font for this paragraph as for all others.","Yes"]
[null,null,"Alex Krebs",null,"CAD041",null,"Apple","Editorial",9,"3.1.2.1","4th in section","801.11 WLAN does not exist",null,"Change to \"802.11 WLAN\"","Yes"]
[null,null,null,null,"CAD019",null,null,"Technical",10,"3.1.3",10,"802.19 comment from Stephen Shellhammer on CA document: There have been a number of presentations in both 802.15 and 802.11 demonstrating issues with coexistence between 802.15.4ab and 802.11.  Here are a few of the presentations: https://mentor.ieee.org/802.15/dcn/24/15-24-0212-05-04ab-response-to-coexsc-11-24-360r3.pptx; https://mentor.ieee.org/802.11/dcn/24/11-24-0148-00-coex-nb-simulation-results-comparison.pptx; https://mentor.ieee.org/802.11/dcn/23/11-23-1622-00-coex-nbfh-coexistence-with-wi-fi.pptx; https://mentor.ieee.org/802.11/dcn/23/11-23-1279-00-coex-nb-with-lbt.pptx",null,"Introduce a mandatory coexistence mechanism that can demonstrate effective coexistence between the Narrowband operation of 802.15.4ab and 802.11.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD020",null,null,"Technical",10,"3.1.3",10,"802.19 comment from Stephen Shellhammer on CA document: The CA document describes a number of optional features like: an improved channel switching mechanism and an improved spectrum sensing and interference avoidance technique. However, all these features are optional and hence may not be implemented in practice.  There is no mandatory coexistence mechanism for the Narrowband operating mode. The spectrum sensing, like Energy Detection (ED) Listen Before Talk (LBD) is a common coexistence mechanism in other standards and if mandatory would likely work well in 802.15.4ab.",null,"One possibility is to make ED LBT a mandatory requirement.  That would address the coexistence issue.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD021",null,null,"Technical",10,"3.1.3",10,"802.19 comment from Stephen Shellhammer on CA document: The CA document states that the typical duty cycle of the NB operation is 1.5 to 5% of the time.  It is not clear if that is averaged over the course of 24 hours or some other time period.  It may be possible for the short-term duty cycle to be much higher than that. In that case, the coexistence impact could be significant. Also, it is quite possible for multiple 802.15.4ab devices to be in the same area near an 802.11 device, in which case the aggregate duty cycle can be also much higher.",null,"One possibility is to mandate ED LBT if the short-term duty cycle is above a specified threshold.  Then an analysis could be performed demonstrating effective coexistence.  Since it is probably not possible for the 802.15.4ab to know how many other 802.15.4ab devices are in the same vicinity, so the analysis can consider a reasonable number of such devices nearby.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD007",null,null,"Editorial",10,"3.1.3",12,"802.19 comment from Billy Verso on CA document: Typo, extra \"]\" in 2nd line of 1st paragraph of 3.1.3",null,"Change \"[32]]\" to \"[32]\".","No","Accepted"]
[null,null,"Alex Krebs",null,"CAD042",null,"Apple","Technical",10,"3.1.3",12,"Use of words typical/typically is use twice in the first  sentence of the paragraph. Meaning of the sentence is confusing as a regulatory constraint is mentioned that requires not only typical conformance. Also references are incorrectly numbered.",null,"Change sentence to\n\n802.15.4-2020 UWB ranging is duty-cycle constraint to 5% when regulatory and public safety requirements apply [30] [31]. ","Yes"]
[null,null,null,null,"CAD025",null,null,"Technical",10,"3.1.3","All","802.19 comment from Pooria Pakrooh on CA document: The 4ab amendment defines transmission of NB packets in UNII-3 and UNII-5 bands. The EIRP could be very high (14-20dBm) depending on regional regulatory rules. As specified in the 4ab draft, NB PHY can be used for ranging, data communication and transmission of acquisition packets, without any limit on duty cycle, and any mandatory channel access mechanism to ensure proper coexistence of 15.4ab NB radios with each other, or with other 802 radios.\n\nMany parts of this CA document claim methods which improve the coexistence, including very low duty cycle, coordination between radios, eDAA functionality, etc. However, none of these methods are mandatory in the 15.4ab draft, with clear definition of the parameters, defined for the specific operation of NB in UNII-3/5 bands.\n\nSeveral simulation and real measurements in 802.15 and 802.11 groups show the detrimental effect of NB operation on 802.11 devices. The studies are not covered in this document. See for example: 15-24-212/r5, 11-24-360/r3, 11-23/1279/r0.\n\nSince a mandatory coexistence mechanism is not defined in the 4ab draft, there is no proper evaluation or guarantee that the methods mentioned in section 3.1.3 are implemented, or provide sufficient coexistence with existing 802 technologies in UNII-3 and UNII-5. See 15-24-212/r5, 11-24-360/r3 and 11-23/1279/r0, for detailed evaluation of the coexistence issues caused by NB radio for 802.11 devices.",null,"Define a mandatory channel mechanism for the channel access protocol for NB OQPSK in UNII-3 and UNII-5 bands.\n\nThere is no proper assessment presented in the CA document, demonstarting proper coexistence between the NB radio and other 802.15 and 802.11 radios. Multiple simulation and real measurements show the detrimental effect of NB operation on 802.11 devices, both on latency and throughput. The studies are not covered in this document. See for example: 15-24-212/r5, 11-24-360/r3, 11-23/1279/r0.\n\nOne possibility to address the coexistence concerns is adopt the proposal in DCN 15-24-0212-05, as below:\n\n\"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle.\nFor a NB capable device, if its NB transmission duty cycle is more than 2.5% (exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD009",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Menzo Wentink on CA document: \"802.15.4 ranging services that operate under regulatory and public safety requirement constraints use typical airtime duty cycles between 1.5 and 5% typically [31] [32]].\"\n\nA duty cycle limitation is not an effective coexistence mechanism because the number of devices can not be controlled. Several devices using a low duty cycle will add up to a high duty cycle. With wideband capturing many NB channels, this may add up quickly.\n\nIn addition, low duty cycle Wi-Fi transmissions such as beacons and broadcast will not be reliably detected by offline scans as typically used in detect and avoid (DAA) algorithms. But beacons and broadcast traffic are not retried and will therefore be impacted immediately by collisions with no-LBT transmissions. Offline scans are typically also slow in detecting sudden changes in activity on a channel.\n\nNB/Wi-Fi coexistence has been the topic of study in the 802.11 coex SG. A summary presentation is available at https://mentor.ieee.org/802.11/dcn/24/11-24-0148-00-coex-nb-simulation-results-comparison.pptx, which concludes that LBT should be used.",null,"802.15.4ab narrowband (NB) transmissions should use listen before talk (LBT). Offline scanning can be used to identify spectrum where the clear channel assessment (CCA) will have the highest probability of being idle.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD010",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Menzo Wentink on CA document: \"802.15.4 ranging services that operate under regulatory and public safety requirement constraints use typical airtime duty cycles between 1.5 and 5% typically [31] [32]].\"\n\n802.15.4ab NB may be used for one-to-many MMS ranging, to send data, or as channel access coordination signal. It seems that the duty cycle could easily be higher than 5%.",null,"Please provide a realistic estimate for the expected NB duty cycle.","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD022",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Vincent Knowles IV Jones on CA document: In Section 3.1.3 (NB impact on 802.11), there does not appear to be an established mandatory mechanism for spectrum sharing.\nPlease be specific and instruct the industry about what spectrum sharing mechanism will be employed by NB devices.",null,"State clear what spectrum sharing mechanism shall be implemented for NB devices.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD023",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Vincent Knowles IV Jones on CA document: Low Duty cycle appears to be the justification as the reason why there is no Spectrum Sharing mechanism for NB implementations.\nThe days are long gone where unlicensed spectrum is for only best-effort traffic.\nAny amount of transmissions by unlicensed devices causes an impact to QoS for other unlicensed devices.\nIt looks like the 802.15.4ab authors do not care about Spectrum Sharing.\n\nPlease define and specify a suitable Spectrum Sharing Mechanism which is required for implementations.\nPlease do not fall back on the lame excuse that \"we can't pick just one\".\nThat argument is simply a way of distracting the group from making a good standard.\nThe wireless industry needs a precisely defined spectrum sharing mechanism that the industry can build and test.",null,"Define a mandatory spectrum sharing mechanism that gives clear instructions to implementers of NB devices and victim unlicensed devices.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD024",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Eugene Baik on CA document: A device having a low average duty cycle alone may not ensure coexistence with other technologies and even other 802.15.ab devices.\n\nAn average duty cycle limitation of 1.5-5% would be for just one device, while the aggregate coexistence impact of multiple devices in the vicinity is dependent on the number of devices, which could be quite large.\n\nAdditionally, a specifc % value and the time scale of the averaging are parameters that needs to be defined. Short term spikes in DC could disproportionately affect network behavior in the absence of other coexistence mechanisms.",null,"Consider requiring Energy Detection based LBT for CCA when 802.15.4ab devices want to transmit on the medium when sharing with 802.11, as that would scale with increased number of devices in the network.","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD026",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Pooria Pakrooh on CA document: Many of arguments in this document in subclauses 3.1.1 and 3.1.2.2 are building on the fact that UWB power is potentially much lower than 802.11 devices.\n\nOn the other hand, NB EIRP could be up to 21dB stronger than 802.11. Therefore, the impact of NB on 802.11 devices needs to be addressed.",null,"Specify a mandatory coexistence mechanism, which guarantees coexistence of the NB operation with other 802.15.4ab and other 802.11 devices. To avoid causing extra burden for very low duty cycle ranging operation, a duty cycle threshold can be defined such that very low duty cycle operations do not have to follow the mandatory mechanism.\n\nThis document does not provide analysis on the impact of NB operation in UNII-3/5 on the 802.11 devices.\n\nEnsure there is sufficient analysis. There are many studies in 802.11 Coex SC, and 15.4ab group, which show detrimental impact of NB on 802.11 throughput and latency. Those need to be included to give proper insight to the reader.","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD027",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Pooria Pakrooh on CA document: There are several issues with the statements in subclause 3.1.3:\n\n1. There is no duty cycle limitation in the 4ab draft defined for NB operation in UNII-3 and UNII-5 bands .\n\n2. For ranging, in case of multiple peer-to-peer ranging devices, and one-to-many ranging, the aggregate duty cycle could be very high. There is no guarantee to support the claim about 5% duty cycle limit.\n\n3. Ranging is not the only functionality that uses NB operation in UNII-3/5. In fact, given all the new functionalities defined in 4ab, the duty cycle of NB operation could be well above 5%. For example, NB data offload feature defined in subclause 10.43, or acquisition packet transmissions in channels other than the default channel can have unlimited duty cycle.\n\n4. It is not specified what is the definition of duty cycle. Definition of duty cycle depends on the measurement time (1ms, 1s, 1minute, 1hr, etc), otherwise it does not provide any useful information.\nTherefore, the statement below is misleading.\n\nSentence copied from CA document: \"802.15.4 ranging services that operate under regulatory and public safety requirement constraints use\ntypical airtime duty cycles between 1.5 and 5% typically [31] [32]]. 95% or greater of the available\nairtime is typically available to other radio technologies operating in the same frequency bands.\"",null,"Specify a mandatory coexistence mechanism, which guarantees coexistence of the NB operation with other 802.15.4ab and other 802.11 devices. To avoid causing extra burden for very low duty cycle ranging operation, a duty cycle threshold can be defined such that very low duty cycle operations do not have to follow the mandatory mechanism.\n\nA possible solution is to use the proposal in DCN 15-24-0212-05, as below:\n\n\"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle.\nFor a NB capable device, if its NB transmission duty cycle is more than 2.5% (exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD028",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Pooria Pakrooh on CA document: The sentence below is not accurate. Even though the default advertising channel is defined outside of the spectrum used by 802.11 devices, nothing prevents devices to send these advertising packets in interfering channels with 802.11.\nAlso, as defined in 15.4ab, these advertising/acquisition packets can be transmitted at arbitrarily low interval, which can lead to serious coexistence consequences.\n\nSentence copied from the CA document: \"Periodic NB packet transmissions on fixed channels such as background advertising and control traffic are allocated in 4ab in newly allocated\nspectrum outside of the channel map used by 802.11 WLAN such that no interference is cast [29].\"",null,"Do the following changes to ensure proper coexistence:\n\n1. Add a mandatory coexistence mechanism, which guarantees coexistence of the NB OQPSK with other NB usage, as well as 802.11 technology. One possible solution is to use the proposal in DCN 15-24-0212-05, as below: \"A NB capable device operating in UNII-3 or UNII-5 band shall measure its NB transmission duty cycle. For a NB capable device, if its NB transmission duty cycle is more than 2.5% (the exact threshold value to be discussed further), it shall perform listen-before-talk (LBT) before any NB transmission. Otherwise, LBT is optional.\"\n\n2. Limit advertising/acquisition packets to channel(s) outside of 802.11 spectrum to make this statement accurate.","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD029",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Pooria Pakrooh on CA document: The sentence below is unclear and misleading. What is the value for the fixed upper bound? Does that depend on block/round structure? If so, this upper bound can be very large and provides no meaningful coexistence improvement.\n\nSentence copied from the CA document: \"Instead all packet transmissions are cancelled following a non-recoverable packet error, thereby guaranteeing a fixed upper bound on duty cycle that is set by the 4ab MAC ranging configuration.\"",null,"Clarify the upper bound value. If there is no clear upper bound, remove this sentence, instead define a meaningful coexistence mechanism that can be evaluated, and ensures efficient coexistence with other radios in UNII-3 and UNII-5.","Yes",null,null,null,null,"ASSIGNED",null,"Alex"]
[null,null,null,null,"CAD030",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Pooria Pakrooh on CA document: This functionality referred to below, does not help with 802.11 coexistence as it does not make decision based on 802.11 channel occupancy. It is defined for UWB devices to avoid interfering with each other. In fact, the impact is quite the opposite of what is claimed, as these coordination packets increase interference with 802.11 devices.\n\n\nSentence copied from CA document: \"Additionally, 4ab actively promotes coordination between radios by introducing periodic broadcast packet transmissions that can be used to reveal channel occupancy patterns and interference avoidance information to other radios without spectrum sensing abilities [34].\"",null,"1. Specify how these packets help coexistence with 802.11 devices. These packets do not help with coexistence with 802.11 devices, and they can increase the interference with 802.11 devices.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD031",null,null,"Technical",10,"3.1.3",null,"802.19 comment from James Petranovich on CA document: Listen before talk should be used to provide effective coexistence with 802.11 and other systems.  The duty cycle of the proposed system is high enough to cause some collisions.  Shortening packets alone is not enough.",null,"Add listen-before-talk or a similar mechanism to insure that other users of the channel will not be disrupted.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD032",null,null,"Technical",10,"3.1.3",null,"802.19 comment from James Petranovich on CA document: Unlicensed frequency bands should be shared using listen before talk.",null,"Use listen before talk or some simialr technique to avoid transmitting when a different system, such as 802.11, is using the same resources.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD033",null,null,"Technical",10,"3.1.3",null,"802.19 comment from Rolf de Vegt on CA document: Section 3.1.3 (NB impact on 802.11) does not specify a mandatory mechanism for spectrum sharing.",null,"Please add a mandatory reference to the spectrum sharing mechanism(s) to be imp","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD036",null,null,"Technical",11,"3.1.3",null,"802.19 comment from Dorothy Stanley on CA document: \"Introducing periodic broadcast transmissions that can be used to reveal channel occupancy patterns and interference avoidance information to other radios without spectrum sensing abilities\"\nDo the broadcast transmissions contain useful data that must be decoded, or is the medium simply made busy?\nAre the other radios without sensing abilities required to receive and decode the transmissions?",null,"Explain the mechanisms in more detail.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD035",null,null,"Technical",13,5,null,"802.19 comment from Dorothy Stanley on CA document: The content from section 5, 802.15.6 is empty.",null,"Add the text.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD016",null,null,"Editorial",5,6,2,"802.19 comment from Kazuto Yano on CA document: A phrase \"the original UWB PHY was renamed\" is duplicated.",null,"Remove the unnecessary phrase.","No","Accepted"]
[null,null,null,null,"CAD014",null,null,"General",13,6,2,"802.19 comment from Kazuto Yano on CA document: Clause 6 where conclusion would be given is blank.",null,"Please give the conclusion of this document.","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,null,null,"CAD034",null,null,"Technical",13,6,null,"802.19 comment from Dorothy Stanley on CA document: The Conclusion, section 6 is empty",null,"Include a conclusion section","Yes",null,null,null,null,"ASSIGNED",null,"Ben"]
[null,null,"Alex Krebs",null,"CAD047",null,"Apple","Editorial",13,"7","various","References 5, 7, 9, 12, 13, 14-18, 20-22, 25, 33 are not used in the document text.",null,"Add reference to text where desired, remove unused references otherwise.","Yes"]

{"sheet":"Sheet1","index":7,"n_rows":42,"n_cols":4,"rows_kept":42,"cut":false,"hidden":false,"merged":[]}
["Voter","# Comments",null,"Vote"]
["Tero Kivinen",586,{"$f":"B2/1471","v":0.39836845683208699},"No"]
["Billy Verso",277,0.18830727396329028,"No"]
["Mickael Maman",77,5.2345343303874914E-2,"Yes"]
["Carlos Aldana",47,3.1951053704962609E-2,"No"]
["Carl Murray",46,3.1271244051665537E-2,"No"]
["Li-Hsiang Sun",45,3.0591434398368457E-2,"No"]
["Bin Qian",40,2.7192386131883073E-2,"No"]
["Pooria Pakrooh",39,2.6512576478585997E-2,"No"]
["Rojan Chitrakar",38,2.5832766825288921E-2,"No"]
["Huan-Bang Li",31,2.1074099252209381E-2,"Yes"]
["Pablo Corbalán Pelegrín",28,1.9034670292318152E-2,"No"]
["Youngwan So",25,1.6995241332426921E-2,"Yes"]
["Alex Krebs",24,1.6315431679129844E-2,"No"]
["B. Rolfe",23,1.5635622025832768E-2,"Yes"]
["Wenzheng Li",19,1.291638341264446E-2,"Non-voter"]
["Aniruddh Rao Kabbinale",15,1.0197144799456152E-2,"Yes"]
["Riku Pirhonen",14,9.5173351461590762E-3,"No"]
["Srivathsa Masthi Parthasarathi",14,9.5173351461590762E-3,"No"]
["Libra Xiao",10,6.7980965329707682E-3,"No"]
["Kangjin Yoon",7,4.7586675730795381E-3,"No"]
["Zhenzhen Ye",7,4.7586675730795381E-3,"No"]
["Frank Leong",6,4.0788579197824611E-3,"No"]
["Hong Won Lee",6,4.0788579197824611E-3,"No"]
["Lei HUANG",6,4.0788579197824611E-3,"Yes"]
["Bin Tian",5,3.3990482664853841E-3,"No"]
["Shang-Te Yang",5,3.3990482664853841E-3,"Yes"]
["Tushar Patel",4,2.7192386131883071E-3,"Yes"]
["Zhepeng Ma",4,2.7192386131883071E-3,"Non-voter"]
["Koorosh Akhavan",3,2.0394289598912306E-3,"No"]
["Larry Zakaib",3,2.0394289598912306E-3,"Yes"]
["Bernhard Großwindhager",2,1.3596193065941536E-3,"No"]
["Henk de Ruijter",2,1.3596193065941536E-3,"Yes"]
["Jaegook Lee",2,1.3596193065941536E-3,"Yes"]
["Li Ma",2,1.3596193065941536E-3,"No"]
["Stefan Lemsitzer",2,1.3596193065941536E-3,"No"]
["Xiliang Luo",2,1.3596193065941536E-3,"No"]
["Harry Bims",1,6.7980965329707678E-4,"Non-voter"]
["Jarek Niewczas",1,6.7980965329707678E-4,"No"]
["Stephan Sand",1,6.7980965329707678E-4,"Yes"]
["Stephen Shellhammer",1,6.7980965329707678E-4,"No"]
["Zhongxing Yu",1,6.7980965329707678E-4,"Non-voter"]