stds-802-16: TG1 COMMENT: IEEE 802.16.1 Final Task Group Review [revision]

["Roger B. Marks" <marks@boulder.nist.gov>]

This is a reissue of the previous Call for Comments. The only change 
is the revision in document number to reflect the updated version 
released on 10 August 2000.

-------------------------------------------------------------------------
The 802.16.1 Task Group has produced a working version of its air 
interface standard, entitled "Air Interface for Fixed Broadband 
Wireless Access Systems," (Document 802.16.1-00/01r1 
<http://ieee802.org/16/tg1/docs/802161-00_01r1.pdf>).

In accordance with a Task Group decision at 802.16 Session #8, this 
process initiates a Final Task Group Review in preparation for 
initiation of an 802.16 Working Group Letter Ballot following Session 
#9. The Task Group invites comment on this document. Detailed 
instructions for submitting comments electronically follow. 
Commentors are encouraged to be thorough and concise in their 
comments so the next version will be ready for Working Group Letter 
Ballot.

The Session #8 motion specified that priority consideration be given 
to resolving all open technical issues "to be determined" that remain 
marked as "TBD" in the document. Therefore, commentors are also 
encouraged to provide detailed input on these sections of the 
document. At Session #9, resolution of comments on TBD sections will 
be the first order of business.

You may have participated in similar comment/resolution procedures 
that took place for 802.16.1 and 802.16.3 Functional Requirements. We 
will use a very similar process for this Task Group review. All 
comments will be incorporated into a database and the 802.16.1 
editors will produce two additional documents prior to Session #9: a 
database "dump" that is sorted by Page Number/Line Number (with 
comments on TBD sections listed first), and a new version of the 
document, with each comment edited-in and noted by change bars. Then, 
at Session #9, the 802.16.1 Task Group will proceed by considering 
each and every comment with discussion and vote. The Task Group may 
divide itself into parallel sessions to resolve MAC- and PHY-specific 
comments simultaneously.

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 and may require debate on 
the proposed change.
-TBD: The comment is technical in nature and covers one of the 
sections marked with a "TBD." These comments will be resolved before 
all others.

The editors and chairs reserve the right to change "E" categorizations to "T."

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 editors 
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/tg1/docs/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 cannot be rendered 
in 80 columns).
- Commentors MUST fill out all of the fields, which are:
    - Last Name
    - First Name
    - Membership Status (Member, Observer, Neither)
    - Starting page number
    - Starting line number
    - "T," "E" or "TBD": Technical (content-related), Editorial 
(typos, grammar, etc.), or TBD-related
    - 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 "TG1 COMMENT:" MUST appear at the start of the message's 
subject line. This allows participants to easily recognize the 
COMMENT in their in-box and non-participants to conveniently filter 
out the COMMENT.
- Each email message MUST NOT contain attachments of any kind. 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 cannot 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 1, 2000.

Thank you,

 From the 802.16.1 Editors:
   Jim Mollenauer
   Brian Petry

and the 802.16.1 Editorial Team:
   Carl Eklund
   Jeff Foerster
   Phil Guillemette
   Jay Klein
   John Liebetreu
   Roger Marks
   Glen Sater
   George Stamatelos
   Ken Stanwood
   Nico van Waes
   Juan Carlos Zuniga