stds-802-16: 802.16.3 Functional Requirements Draft #3 Available; Open for Comments

[Brian_Petry@3com.com]

*
* IEEE 802.16.3 Functional Requirements: Call for comments and instructions
*
* Comments due September 7, 2000
*

The 802.16.3 Task Group has produced a new version of the functional
requirements (rev. 3), based on comments resolved at session #8.  It is titled
"Functional Requirements for the 802.16.3 Interoperability Standard" and can
be found at http://ieee802.org/16/sub11/docs/802163-00_02r3.pdf.

The task group invites comment on the draft from 802.16 members, observers and
other interested persons.  Detailed instructions for submitting comments
electronically follow.  Commentors are encouraged to be thorough and concise
in their comments.  Our goal is for the 802.16.3 task group to approve the
requirements at session #9.

You may have participated previous rounds of comment/resolution that took
place for 802.16.3 functional requirements.  We will use the same process this
time as well.  All comments will be incorporated into a database and the
editor will produce two additional documements prior to session #9: a database
"dump" that is sorted by page #/line #, and a new version of the functional
requirements document, with each comment edited-in and noted by change bars.
Then, at session #9, the 802.16.3 task group will proceed by considering each
and every comment with discussion and vote.

To help resolve comments quickly at session #9, commentors are required to
categorize each comment into one of three categories:
   E: The comment is "editorial" in nature.  Acceptance of the requested
      change should not require debate.
   T: The comment is "technical" in nature.  It may require the committee to
      debate the proposed change.

The 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 on the document MUST use the comment submittal form found at:
 http://ieee802.org/16/sub11/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 or change the delimiters which are surrounded by
 square brackets ([]), as we need these to automatically import the
 submitted comment 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
 columns).

***Commentors MUST fill out all of the fields, which are:
    -Last Name
    -First Name
    -Starting page number
    -Starting line number
    -"T" or "E": Technical (content-related) or Editorial (typos,
     grammar, etc.)
    -A detailed description of the proposed edit
    -A reason for the edit

***The commentor MUST send the comments directly to the email reflector
 (mailto:stds-802-16@ieee.org).  This allows other participants to see, and
 prepare for, all of the comments and perhaps avoid overlapping comments.

***The prefix "SUB11 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 such as MS-Word files, text
 files, Visio files, etc.  Note that the IEEE reflector will automatically
 reject messages with any sort of attachment.

***Each email message MUST contain at least one comment form in the body of
 the message.

***An email message MAY contain more than one filled-out comment form in the
 body of a message.  Commentors are encouraged to use this option by building
 up all comments in one text file so they can be reviewed, submitted and
 processed in one batch.  It should be convenient for commentors to copy-and-
 paste comment forms (with their name already filled in) into one file while
 generating their comments.

***If multiple comment forms are sent in one message, each comment form
 MUST contain all of the fields filled out as required (see above), including
 the commentor's name.

***Comments regarding graphics, figures, drawings, equations 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 editors
 for "special" consideration.  We will accommodate these requests by
 associating a graphical figure with the database comment.

The editors will gather all of the proposed changes (comments) and integrate
them into the document and publish it as a new draft.  Overlapping and
conflicting comments will be clearly recognizable in the new draft.

Submissions will be considered non-confidential and will be posted for public
access on the 802.16 Web Site.

For consideration for incorporating changes in the next working draft of the
interoperability standard, valid comments that follow these instructions
MUST be received no later than close of business, September 7, 2000.

Thank you,

From the 802.16.3 Functional Requirements Team

George Fishel
Brian Petry