1. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 1 802-11 Editor’s Guideline Version 1.1 Terry Cole, AMD 802.11 WG Technical Editor & Simon Barber, Devicescape 802.11 WG Co-Technical Editor July 2006

2. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 2 July Updates Modified posting procedure Added explanation on normative figures Added editor roles in ballot resolution Added comment carryover process

3. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 3 Getting started… The IEEE SA website has a lot of info you will need, document templates, etc. Home Page: –http://standards.ieee.org/resources/developme nt/index.htmlhttp://standards.ieee.org/resources/developme nt/index.html Writing The Draft: –http://standards.ieee.org/resources/developme nt/writing/index.htmlhttp://standards.ieee.org/resources/developme nt/writing/index.html

4. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 4 Numbering the Draft Before first Ballot –0.xy, where x/y denotes major/minor revision level –Always monotonically increasing. –No standard meaning to x and y. Use as your TG likes. Ballot Drafts –B.0, where B is denotes the bth ballot or recirculation Drafts in between Ballots –B.xy, where symbols have same meaning as above Number every draft distributed or posted by you uniquely! Example: –TG created drafts 0.1, 0.2, 0.5, and 0.9 and 0.91 before putting forward draft 1.0 for WG ballot –TG creates drafts 1.1 and 1.2 before adopting draft 2.0 for recirculation. –TG creates draft 3.0 for sponsor ballot (including some editorial work from 2.0 to 3.0) –TG creates draft 4.0 for sponsor ballot recirculation. –TG submits draft 4.0 for REVCOM (ALWAYS same as last sponsor ballot) along with a list of editorial errata to be addressed during publication.

5. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 5 Interim Draft Checklist Labeled and named correctly –Labeled according to style guide on the top of each page –Draft number assigned according to 802.11 practice (see separate slide) –Examples: IEEE P802.11k/D3.4, March 2006 (Draft Amendment to IEEE Std 802.11(tm), 2006 Revision Draft 5.1) IEEE P802.11r/D2.0, March 2006 (Draft Amendment to IEEE Std 802.11(tm), 2006 Revision Draft 5.1, as amended by IEEE P802.11k/D3.4, xxx and yyy) IEEE P802.11s/D2.0, March 2006 (Draft Amendment to IEEE Std 802.11(tm), 2006 Revision, as amended by IEEE Std 802.11k(tm)-2007, xxx and yyy) Updated copyright notice per style guide and current year in copyright notice “This is an unapproved IEEE Standards Draft, subject to change” on the bottom of all pages Note that there is not a requirement for completeness. –I recommend explaining major work items still to be done with an editor note

6. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 6 Ballot Draft Checklist Must meet all requirements for posting as an interim draft, PLUS: Substantially Complete –NO Avoidable TBDs! –No Incomplete Text –No Outstanding Motions To Be Done –I recommend explaining EACH exception with an editor note and why it cannot be completed now! No publication flaws of these types: –“reference not found” errors –“figure not found” errors –TOC updated Pages numbered and lines numbered If WG ballot: –Available for review as a technical document by the appropriate deadline, but only if challenged (even if by only one person). Not out of order if unchallenged. –Change bar version (FROM LAST BALLOT) AND clean version If sponsor ballot: –MEC Section I comments completed before opening of first ballot –MEC Section II comments completed before last recirculation

7. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 7 Posting a Draft The Task Group editor should follow this procedure: 1.Make sure the draft satisfied proper numbering, interim draft requirements, and, if applicable, ballot draft requirements. 2.You may post.doc or.pdf or both formats, and you may need to post clean and red- line versions. Send these in a single email as attachments for posting with a clear subject: 802.11x Draft for Posting. If you zip the file(s) you must rename to.xzy and mention this in the email. Zip files are not deliverable in many email systems and in particular not to Harry’s ATT address. 3.Email to your task group chair, who is required to review it to double check that all motions have been included. You should call your task group chair. 4.Task group chair emails to Harry using primary and backup email addresses. He should also copy Stuart, myself and Simon, to hworstell@att.com and worstellhr@hotmail.com with cc to: stuart@ok-brit.com terry.cole@amd.com and simon@devicescape.com. 5.He should call Harry on his cell phone. 6.Harry or Stuart will post quickly, and the task group chair will get a confirmation email. 7.The Task Group chair should announce the draft availability over the appropriate email reflectors and in appropriate meeting sessions. Note: Posting of drafts to any other sites, including our own temporary file server space at meetings or on open company ftp sites, is not allowed.

8. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 8 Baselines & Revisions IEEE rules prevent amendments from being published while a revision is in progress All current amendments will have to be based on 802.11ma. Groups to decide on a group by group basis how they want to track 11ma.

9. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 9 How to handle simultaneous drafts... Best practices described in next 2 slides. Original presentation in doc 11/06/238r1 Note: –Approved means approved by REVCOM –None of this process affects the need for drafts to be based ONLY on previously approved documents when they are finally presented to REVCOM.

10. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 10 When a revision and another amendment are in progress… –Your amendment should be based on the latest draft of the revision text AND the latest draft of all amendments expected to be approved prior to yours –Your document must then be sent for sponsor balloting with all the below: the current, complete approved base text (prior to the revision) the latest draft of the revision the latest draft of all amendments expected to be approved before yours –These amendments are only included if they make technical changes that are relevant to your amendment. your amendment. –If a technical change happens in a part of the revision text or part of the amendment text expected to be approved prior to your amendment, and that change is technically relevant to your amendment then your amendment should be re-circulated. Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case)

11. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 11 When other amendments are in progress… –Your amendment should be based on the current, complete approved base text AND the latest draft of all amendments expected to be approved prior to yours –Your document must then be sent for sponsor balloting with all the below: the current, complete approved base text the latest draft of all amendments expected to be approved before yours –These amendments are only included if they make technical changes that are relevant to your amendment. your amendment. –If a technical change happens in a part of the revision text or part of the amendment text expected to be approved prior to your amendment, and that change is technically relevant to your amendment then your amendment should be re-circulated. Relevant technical change is decided by the ballot resolution group (the TG itself in 802.11’s case)

12. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 12 IEEE Review Insertion Numbering 2006 IEEE Style Guide changes now mean that all amendments will renumber inserted text, figures, and tables based on 802.11ma Add letter after current number To insert between 2 letter clauses, add second letter. Needed for insertions ONLY, not additions to end of current numbers.

13. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 13 IEEE MEC process Make sure your chairs are aware of this –Time constraints that this will put on sponsor ballot –Section I has to be addressed before you can start Sponsor Ballot –Section II comments have to be addressed before last SB recirculation –Section III comments are suggestions

14. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 14 Figures Figures are normative, unless included in an informative Annex.

15. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 15 Editor Roles in Ballot Resolution –The editor may be assigned to compile and track comments by the TG chair. Other leaders or members in the TG may instead keep this database, depending on the TG. Assigning this task to the editor has both advantages (e.g., efficiency, organization of comments) and disadvantages (e.g., lack of a check and balance, additional work for the editor). This is not an editor’s responsibility but may be done on a volunteer basis as additional duties. Excel spreadsheets are commonly used, although other methods also exist that connect more directly with the myBallot voting machine. In any case, the comment resolution list must be published to members. –The editor may be assigned any or all editorial comments for resolution by the TG. Editorial comments may be assigned to others or done by committee review, as well, depending on the TG. The editor should write and submit comment resolutions for each comment assigned, and the editor should publish a list of all proposed resolutions. It should be combined with the comment database. The TG may adopt editorial comment resolutions formally by motion, but this is not required as the editor is empowered to make changes and submit text back to the TG chair. The editor should bring back to the attention of the TG chair any comments which are wrongly classified as editorial and have technical impact on the document. –The editor at times may be directed by motion or comment resolution to make changes to the draft without detailed text changes being reviewed by the TG. The editor should keep an accurate record of each action taken from such direction. The editor should bring to the attention of the TG chair all concerns from non-specific directions, especially in the case a contentious issues is found, the issue “snowballs”, conflicting directions exists, critical timing, etc.

16. 802.11 Editor’s Guideline July 2006 Terry Cole, AMDSlide 16 Comment Carryover –In A WG ballot, each comment is accepted, rejected, or countered by the TG “Rejected” technical comments associated with negative votes are carried forward from WG ballot to ballot. “Countered” comments go away in a WG ballot only when the voter votes yes in future ballots or otherwise explicitly communicate to the TG chair in writing (email) that they accept the counter, withdraw their comment, or change their vote to yes. All comments associated with negative votes and not accepted must be available to voters during subsequent ballots as they may change their vote on the basis of new comments with which they agree, even if there are no other text changes. –In a sponsor ballot, each comment is accepted, rejected, or countered by the sponsor ballot resolution committee “Rejected” comments associated with negative votes are carried forward in a sponsor ballot regardless of type. “Countered” comments go away in a sponsor ballot only when the voter votes yes or otherwise explicitly communicate to the sponsor ballot resolution committee chair in writing (email) that they withdraw their comment. All comments associated with negative votes and not accepted must be available to voters during subsequent ballots as they may change their vote on the basis of new comments with which they agree, even if there are no other text changes. –Comment resolution process applies to ballots the pass. It may optionally be applied to ballots that fail.