[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
stds-802-16: SYSREQ: Draft 5 and Comment Instructions
We have posted draft 5 of the system requirements document, which includes:
-Output from the QoS ad-hoc group.
-Output from the Terminology ad-hoc group.
-Resolved comments from the comment and on-line resolution process (Sept. 17
through Oct. 6).
Draft 5 is at
We are also now open to receive comments on draft 5 which we will resolve at the
November 8-11 session. Please find detailed comment instructions below. The
instructions are the same as last time. Also note the comment deadline, 00:00
GMT November 4, 1999, which is the same as midnight GMT, November 3.
* 802.16 SYSTEM REQUIREMENTS GROUP SEEKS SPECIFIC COMMENTS
* Call for Comments on the System Requirements Working Draft
The 802.16 System Requirements Task Group is working on a document that
describes system requirements that directly affect the development of the
802.16 air interface standard for broadband wireless access systems, as
described in the Project Authorization Request
(http://grouper.ieee.org/groups/802/16/interop/par.html). It seeks input and
review by 802.16 members, participants and the industry to ensure that the
802.16 standards meet industry expectations.
The current working draft, with changes approved by the task group, is at
The current working draft is open for comment regarding only specific changes:
insertion, deletion or change of any part of the document. Below are detailed
instructions for submitting comments. The instructions MUST be followed or
comments will be respectfully rejected by the editor and will not be entered
into the comment database. For a rejected comment to be considered, the
commentor receiving a rejection MUST resubmit the comment(s) using the
instructions found below:
***Each comment to the document MUST use the comment submittal form found at:
http://grouper.ieee.org/groups/802/16/sysreq/commentform.txt. The form is
ASCII text-based (DOS text with CR/LF at the end of each line), and
accommodates one "edit request." It is filled-out with a short example.
***Commentors MUST replace the example text with their own information.
***Commentors MUST NOT delete the delimiters which are surrounded by square
brackets (), as we may need these to conveniently import the submitted forms
into a database.
***Commentors SHOULD wrap/fold each line at 80 columns or less (the only
exception is for a table or other format that can not be rendered in 80
***Commentors MUST fill out all of the fields, which are:
-Starting page number
-Starting line number
-"T" or "E": Technical (content-related) or Editorial (typos, grammar,
-A detailed description of the proposed edit
-A reason for the edit
***The commmentor MUST send the comments directly to the email reflector
(mailto:firstname.lastname@example.org). This allows other participants to see, and
prepare for, all of the comments and avoid overlapping comments.
***The prefix "SYSREQ COMMENT:" MUST appear on the subject line of the
message. This allows participants to easily recognize COMMENT in their
in-box, and non-participants to conveniently skip-over COMMENT messages.
***Each email message MUST NOT contain attachments (MS-Word files, text files,
Visio files, etc.).
***Each email message MUST contain at least one comment form in the body of
***An email message MAY contain more than one filled-out comment form in the
body of a message.
***Comments regarding graphics, figures, drawings and tables MUST be fully
described in text form. If such graphic-oriented comments can not be rendered
or described in text form, the commentor MAY contact the editor for "special"
***Commentors SHOULD send each comment message as a "reply" to the editor's
"request for comments" message so that people who browse the reflector archive
on our web page can more conveniently skip over the sysreq comments. Note
that you may have to override the subject line with the "SYSREQ COMMENT:"
prefix (see above).
The editor will gather all of the proposed comments and integrate them into
the document and published it as draft #6. Overlapping and conflicting
comments will be clearly recognizable in draft #6.
Submissions will be considered non-confidential and will be posted for public
access on the System Requirements Area of the 802.16 Web Site.
For consideration for incorporating changes in the next working draft of the
System Requirements Document, valid comments that follow these instructions
MUST be received no later than 00:00 GMT, November 4, 1999 (which is the same
as midnight, November 3, 1999.
Thank you, from the System Requirements Task Group leadership:
George Fishel (Chair)
Communications Consulting Services
Shermans Dale, PA
Brian Petry (Editor)
San Diego, CA