Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Anirud, Since our draft is still not feature complete, yes, some effort will be made to add and/or complete features by using the comment resolution process. Keep in mind that all comments will be reviewed by TGbf and require 75% approval to be incorporated into the draft. In this sense, nothing has changed. Claudio From: Sahoo, Anirudha (Fed) <00001823ca88828f-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi all, Many of the comments seem like require *major* addition/change to the draft. For example, comment with CID 380 in R2R says “The details of R2R sensing operating are missing, e.g., how to schdule R2R sensing, How to trasmit NDP in terms of R2R sensing”. This probably requires a presentation (of proposal to address the issue) to the group with potentially multiple
iterations. So, when a volunteer takes up this CID, he/she has to come up with the presentation (containing the solution)? In such cases, the “Proposed Change” will be pretty involved (not simple) and hence, I guess, the commenters have simply put “as per
comment” or something similar. It looks like “comment resolution” phase is used to incorporate all the missing features (in addition to correcting things which are already there) in the draft. Is this correct understanding? thanks and regards -Anirud Anirudha (Anirud) Sahoo (He/Him) https://sites.google.com/view/a-sahoo National Institute of Standards and Technology Wireless Networks Division Communications Technology Lab 100 Bureau Drive, Stop 6730 Gaithersburg, MD 20899 Ph: 301-975-4439 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |