The IEEE 802.16 Mentor documentation system is at http://docs.wirelessman.org
(equivalent to http://mentor.ieee.org/802.16/documents). You may browse and download documents anonymously. However, to submit a document, you must be logged in using your IEEE Web Account. IEEE Web Accounts are free and do not require IEEE or IEEE-SA membership. If you have used the IMAT attendance system, then use the same IEEE Web Account for Mentor. You can create an IEEE Web Account here.
To submit a document to the IEEE 802.16 Working Group (WG) or a subgroup:
Prepare the document using one of the current (Rev. 0: 2012-01-01) revision of the IEEE 802.16 Mentor Document Template, available below:
IEEE 802.16 Mentor Document Template: odt or rtf or doc or docx
IEEE 802.16 Mentor Presentation Template: odp or ppt or pptx
Determine the appropriate four-character IEEE 802.16 Mentor "file code" using with reference to "Choosing a File Code" below.
Choose "New Document" in blue text in the upper right of the page.
Note: If you log in and still see "Join Group", then click the link to connect your account to 802.16. When you log in again, the "New Document" link should appear.
Use the "Group" drop-down menu to select the "file code" you determined previously. Enter the Document Title in the appropriate field. In the "Author (Affiliation)" field, enter the name(s) and affiliation(s), with affiliation in parentheses.
In the case of a Gdoc, the "affiliation" field should be the name of the relevant group.
Click the "New Document" button to reserve your document serial number.
Enter the correct the Document Number in the header of your document, based on the appropriate file code, the reserved document serial number, and the appropriate revision number.
Note: You need not be concerned with the file name, because the IEEE Mentor system will automatically rename your file based on the Document Control Number and the title you enter at upload time, retaining only the file extension of the uploaded file.
Note: You don't have to upload immediately after reserving the document number. If you come back later your document will be listed as "pending." Use the "Upload" link at the right.
Revisions are supported. Once the initial document has been uploaded, a link to upload a revised version will be available under Actions. Mentor automatically increments the revision number in the DCN.
Make sure to manually increment the revision number in your document header.
See also "If this is a revised contribution..." below.
The IEEE 802.16 Mentor upload directories are exclusively for the business of the Working Group and its subgroups, including contributions for consideration.
Comments for consideration in Working Group ballots and in response to a Call for Comments are NOT to be submitted to the Mentor system. Instead, submit them to the appropriate folder at upload.wirelessman.org.
Document Number format The Document Number takes the form "IEEE 802.16-YY-####-RR-FFFF", where:
Every IEEE 802.16 Document Number begins with "IEEE 802.16-".
Following "IEEE 802.", the remainder of the Document Number ("16-YY-####-RR-FFFF") is the Document Control Number (DCN), used by IEEE Mentor as the basis of the file name.
"YY" represents the final two digits of the calendar year of original submission, as assigned by the IEEE Mentor documentation system.
"####" represents the four-digit document serial number, as assigned by the IEEE Mentor documentation system. The serial number is uniquely assigned, for each calendar year, over all IEEE 802.16 documents (i.e., not per File Code). (Note: The Mentor listings refer to the document serial number as the "DCN", though the Mentor documentation specifies that the the "DCN" is the longer string of information as specified above.)
"RR" represents the revision number, as assigned by the IEEE Mentor documentation system. The initial version of the document uses the revision number "00".
"FFFF" represents the Mentor "file code," as described above. It is selected by the submitter as the most appropriate identifier among the list of IEEE 802.16 file codes in the IEEE Mentor documentation system.
Choosing a File Code
Group-Oriented File Codes: official group documents, and individual contributions related to general group activities but not to development of specific standardization projects
Document prepared by the WG or a subgroup; normally Group output documents or documents prepared by an officer acting on behalf of the group. Examples: WG and TG agendas, minutes, group reports, approved documents, etc. Note: The IEEE Mentor "affiliation" field should be the name of the relevant group.
Working Group Liaison Statement as either (a) received by the WG or otherwise provided for its use; or (b) approved by the WG for delivery to an external entity or for forwarding for approval prior to external delivery. Note: Proposed draft liaison statements use the file code "Gcon". Those developed by a Task Group or other WG subgroup use the file code "Gdoc". Note: The IEEE Mentor "affiliation" field should be the name of the relevant group.
Document representing the view of individual participants and submitted to the WG for consideration by the WG or a subgroup but not as a technical input under an existing standardization project.
File Codes for Project-Oriented and Study Group Contributions: to be used by all documents contributed by individual participants for consideration in the development of individual standardization projects or for consideration by Study Groups
Checklist of Contribution Requirements The document is submitted on the appropriate template and shows the current date.
The correct Document Number (see "Document Number format" above) has been inserted into the appropriate place in the template, in EXACTLY the proper format.
If this is a revised contribution, the contributor acknowledges that:
The revision makes earlier versions obsolete.
The authors of the earlier versions agree to the revision.
It is completely inappropriate to submit an unauthorized revision, intentionally or not, expects to be punished accordingly for doing so.
The revision reuses the original document serial number, rather than introduces a new one.
The Document Number shows the correct revision number.
The document cover sheet shows the date that the revision is submitted.
The contributor understands that the contribution may be rejected and deleted without notification if the requirements are not followed.
Document Status
The document template states the following status:
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in the "Source(s)" field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein.
For documents with a different status, the preparing official should modify the status field to correctly reflect the status. Examples include "Approved by IEEE 802.16 Working Group" and "Approved by IEEE 802.16 Task Group X".
Presentations
Presentations shall be prepared using the IEEE 802.16 Mentor Presentation Template (see above).
A presentation intended to accompany or explain a contribution shall reference it on the cover page as the "Base Contribution". The title of such a presentation file shall be "Presentation of Contribution IEEE 802.16-YY-####-RR-FFFF", where "16-YY-####-RR-FFFF" represents the DCN of the Base Contribution.
Use of IEEE-Copyrighted Conference and Journal Papers The IEEE 802.16 Working Group has obtained permission to post IEEE-copyrighted material from IEEE conferences and publications when received in an official contribution to the Working Group. IEEE requires two conditions:
This material is posted here with permission of the IEEE. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE (contact pubs-permissions@ieee.org).
By choosing to view this document, you agree to all provisions of the copyright laws protecting it.
2) If the author is not the submitter of the contribution, the author's written approval for the reuse of the material must be attached.
This process was developed and documented by Roger Marks. Please contact him with any suggestions or corrections.