IEEE 802.11TM TGai Technical Letter Ballot 201 Instructions

Instructions

Motion: " Should P802.11ai D2.0 be forwarded to Sponsor Ballot? "

(Type of Motion: Technical)

Cast your vote here


This Letter Ballot opens on: Mon Apr 07, 2014 at 23:59 Eastern Time USA and closes 30 days later on Wed May 07, 2014 at 23:59 Eastern Time USA. (Add reminder to calendar).

Show detailed instructions
Show detailed description of how to provide comments

The draft and the supporting documentation: 
Document Hyperlink
Draft Draft P802.11ai_D2.0.pdf
Redlined Doc Draft P802.11ai_D2.0 Redline.pdf
Resolution Doc 11-13-1076-34-00ai-tgai-lb-198-comments-for-d1-0.xlsx
Comment Template .xls format or .csv format
NOTE - you must be already signed into Mentor for these links to work.
Pool LB201 Voters
CA Document n/a

Notes

Comments

Should you wish to submit comments, the following instructions indicate how to fill in the fields of the comment.
 
Comment Describe the problem here.
Category Select one of:  Technical,  Editorial or General.
If you are filling in a comment spreadsheet,  be sure to use the full word spelled out as above.  If you don't exactly match one of these three terms,  the system will not let you upload your spreadsheet.
Page Number If you choose to include a page / line number reference in your comments, please do so by entering a non-negative integer in these columns (or roman numeral page number). In recirculation ballots make sure you quote the numbering from the clean draft,  not the redline draft,  as they will be different.
Line Number
Subclause Include there the number of the heading that your comment applies to (e.g. 5, 2.1, 4.2.3., C, C.3, 8.2a.4b).  If you have a comment that applies to the entire document put "General" in the section field. Don't put "all", "many", "various" or any other word you may personally fancy. If the field contains anything other that a (sub)clause number or "General", the comment may be discarded and your vote possibly invalidated.  If your comment relates to a table/figure, place the clause in which the table/figure resides in this column and put a reference to the table/figure at the start of the comment.  Put only the clause number and not any words such as "clause" or "annex".
Proposed Change If you do not recommend a change the comment may be skipped as you have not asked the group to do anything.

Please keep the explanation of the comment separate from what you want done as a result of your reasoning. The voting group is too large for the task group to be interpreting what you are requesting.

Please remember that the operating rules state that all "No" votes MUST be accompanied by comments which include specific reasons and enough information for the group to understand what you desire in order to change your "no" to a "yes". Simply saying "not good enough" is insufficient as the task group cannot reasonably be expected to understand what would satisfy the commenter and so invalidation of the vote is justifiable.
Must Be Satisfied This field appears on the web user-interface only if you have voted "no".  Clearly it is present in the spreadsheet regardless of vote.

This field indicates whether the comment must be satisfied in order for you to change your vote to "yes".

Any voter that votes "no" must have at least one comment marked "must be satisfied=yes" as to support for their "no" vote.  This field must not be left blank for any comment accompanying a "no" vote, as the intent of the voter regarding this comment would be ambiguous.

If you are uploading a spreadsheet,  be sure to use either "Yes" or "No" in this column, as any other value might stop the system accepting your comments.  Any voter that votes "yes" should not have any comments marked "yes" in this column.
Other notes related to writing comments:
Redline drafts The redline draft (if present) is there to show differences between a version being balloted in the current ballot and a previous version.   Due to limitations of the tools used to produce the redline,  this version of the draft may contain artifacts arising from the comparison process.  Before reporting a comment against a problem found in a redline draft *always* check that it is also present in the clean draft.  Regardless of the above, always report any page and line numbers from the clean draft.