Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGAI] Editorial Review of Resolution Text



Dear all:

Adrian was kind enough to cross check our wording in the comment resolution, also to make us aware of potential wording issues that could come up when we eventually reach for RevCom/NesCom Approval.

Please let me summarize the risen issues and the actions I have taken:

(1)  Approved Comments.

The comment resolution must only contain the word "Accepted".

We may not add any other wording.  That also prohibits us to include the hint for out Editor, Lee, that the changes resulting from the "accept" are included in a consolidated document.

As a result, I verified that for all "accepted" comments that are pending for a motion, the comment resolution only says "accept".  The following CIDs were effected:

 2084,  2137,  2145,  2268,  2270,  2280,  2293,  2298,  2303,  2334,  2414,  2436,  2449,  2484,  2585,  2586,  2587,  2601,  2659,  2691,  2708,  2790,  2817,  2818,  2840,  2841,  2847,  2859,  2869,  2870,  2886,  2890,  2899,  2904,  2905,  2923,  2937,  2981,  3020,  3021,  3022,  3023,  3024,  3025,  3028,  3035,  3037,  3047,  3054,  3059,  3060,  3062,  3075,  3103,  3112,  3117,  3160,  3179,  3231,  3266,  3269,  3290,  3345


(2) CID 2484

The comments reads:  "Correct line" ...used to request an IP address using an encapsulation of a higher layer ...""

Suggested resolution "accept"

Remedy:  The nature of the change is not apparent from the comment.

I agree and will take the CID out of the motion tab. The resolution will not be motioned.


(3) CID 2867

The comments reads:  Rejected. FILS Action frame is Robust action frame (see table 8-38). Hence it is protected. Recommend to reject

Remedy:  "Recommend to reject" is not part of the comment resolution.

--> I deleted "Recommend to reject" from the resolution text



(4) CID 2370

The comments reads:   Revised. There is no such clause.  Maybe the author wants to say 10.25.3.2.12. In this case the text will be changed. See doc: https://mentor.ieee.org/802.11/dcn/13/11-13-1374-00-00ai-proposed-normative-text-for-comment-resolutions-section-10-related-to-anqp-sequence-number.docx

Remedy:  Linguistic difficulty.   It is unclear whether any change is being proposed.

-->  I have taken out the CID from the motion pool.  The resolution will not be motioned



(5) CID 2309

The comments reads: revised as per https://mentor.ieee.org/802.11/dcn/13/11-13-1311-03-00ai-fils-indication-element-comment-resolution.docx

Remedy:  Forces the reader to go and read the submission.  A summary of the nature of the change should be included.

I have taken out the CID from the motion pool.  The resolution will not be motioned.  We will have to elaborate on the resolution text.



The above changes are reflected in Rev9 of the comment resolution spreadsheet.
https://mentor.ieee.org/802.11/dcn/13/11-13-1076-09-00ai-tgai-lb-198-comments-for-d1-0.xlsx

Best,

Marc


-----------------------------------------------------------------------------------------
Marc Emmelmann
e-mail:  emmelmann@xxxxxxxx  web:  http://www.emmelmann.org

IEEE 802.11 TGai Vice-Chair

Google Scholar: http://scholar.google.de/citations?user=_EfkmxcAAAAJ





_______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.

SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAI and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________