stds-802-16: TG1 COMMENT

["Foerster, Jeffrey R" <jeffrey.r.foerster@intel.com>]

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
267

[Starting Line #]
20

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove Section 3.1.1 Reference Configuration.

[Reason for Edit]
This is already described by Figures 1, 3, and 5 in Sections 1. 

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
268

[Starting Line #]
25

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change Section 3.1.4 title to "Physical Layers Overview".

[Reason for Edit]
To alleviate confusion between the title of Section 3 and subsection 3.1.4.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
269

[Starting Line #]
32

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
The discussions in Sections 3.2 and 3.3 in the PHY overlap the discussions
in Section 2.6 of the MAC.  I would recommend combining the information into
a single section.  One approach would be to do the following:
	1.	Delete sections 3.2, 3.3, and 3.3.1.
	2.	Make further changes to Section 2.6 as suggested in the
following comment.

[Reason for Edit]
Contain all the framing discussion in a single section to alleviate any
confusion and allow for easier referencing.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
110

[Starting Line #]
39

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
The discussions in Sections 3.2 and 3.3 in the PHY overlap the discussions
in Section 2.6 of the MAC.  I would recommend combining the information into
a single section.  One approach would be to do the following:
	1.	Change the title of Section 2.6 to "Duplexing Techniques,
Framing, and Scheduling Intervals"
	2.	Insert Section 3.2 as the first subsection in Section 2.6.
	3.	Combine figures 119 and 50.
	4.	Remove sections 2.6.1.1 and 2.6.1.2.
	5.	Replace Section 2.6.3 with Section 3.3 (ending at subsection
heading 3.3.1).
	6.	Insert Section 3.3.1 after Section 2.6.3.
	7.	Rearrange Section 2.6 in the document to lie just before the
PHY layer discuss for easier referencing.


[Reason for Edit]
Contain all the framing discussion in a single section to alleviate any
confusion and allow for easier referencing.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
283

[Starting Line #]
55

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the table in Section 3.3.3.2.1.  Add the following sentence to the
end of the paragraph:
"The downstream channel and burst profiles are communicated to the CPEs via
the MAC messages described in Section 2.5.2.2."

[Reason for Edit]
This table duplicates the information that is contained in the MAC section
in Tables 9 and 10 of Section 2.5.2.2.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
284

[Starting Line #]
52

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the table in Section 3.3.3.2.2.  Add the following to the end of the
first sentence,
"(i.e., including the highest modulation order supported, the optional FEC
coding schemes supported, and the minimum shortened last codeword length
supported)."
Add the following to the end of the last sentence,
"using the Registration Request and Response MAC messages described in
Sections 2.5.7 and 2.5.8."

[Reason for Edit]
This information should be contained in the Registration Request message
defined in Sections 2.5.7 and 2.5.8 of the MAC.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
91

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "Modem Capabilities Encodings" to "Upstream and Downstream Modem
Capabilities Encodings".  Add the following after "Upstream and Downstream
Modem Capabilities Encodings":
"These include the highest modulation order supported by the CPE (QPSK,
16-QAM, or 64-QAM), the optional FEC types supported by the CPE(BTC1 based
on (32,26) Extended Hamming Code or BTC2 based on (64,57) Extended Hamming
Code), and the minimum shortened last codeword size supported by the CPE."

[Reason for Edit]
To ensure these items get included in the Modem capabilities set exchange
message for both the upstream and downstream channels.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
296

[Starting Line #]
58

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the subsection 3.4.1 title to "Upstream Channel and Burst
Descriptions".  Remove the table in Section 3.4.1.  Remove the paragraph in
this section, and replace it with the following:
"Since subscriber stations cannot transmit in the upstream channel until
they have received some minimal configuration information from the base
station, it's possible to support several different modem configurations
that can be adjusted on an upstream channel basis or on a burst-by-burst
basis.  These parameters, and their ranges, are supported through MAC layer
signaling, as described in Section 2.5.2.1."

[Reason for Edit]
The table of information is redundant with the information provided in the
MAC portion of the document.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
297

[Starting Line #]
37

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove Section 3.4.2.

[Reason for Edit]
This information is redundant with the information provided in the MAC
portion of the document (Sections 2.5.2.1 and 2.6).


[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
70

[Starting Line #]
15

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Add the following parameter to Table 7:
Spectrum Inversion    |    0=inverted, 1=non-inverted

[Reason for Edit]
To make the PHY and MAC consistent, since this parameter was included in the
PHY Upstream channel description.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
73

[Starting Line #]
23

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the Rows starting with "FEC Error Correction (T)" and "FEC Codeword
Information Bytes(k)" (Rows 4 and 5 in the table on page 73).  Insert Rows
3-11 from Table 10 into Table 8.

[Reason for Edit]
The complete list of FEC parameters was missing from Table 8.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
73

[Starting Line #]
2

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Make the following changes to Table 8:
	1.	Under "Value" for "Preamble Length", change the second
sentence to read, "The preamble must be an integer number of PSs."
	2.	Under "Value" for "Maximum Burst Size", change "bytes" in
the first sentence to "PSs".
	3.	Under "Value" for "Guard Time Size", change "symbol times"
to "PSs" in the first sentence.

[Reason for Edit]
The smallest unit of reference in the channel should be a physical slot (PS)
to be consistent with the rest of the specification.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
299

[Starting Line #]
55

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove Section 3.4.3.

[Reason for Edit]
This information is contained in Section 2.6 already, so there is no need to
repeat it.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
77

[Starting Line #]
58

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add the following sentences at end of the paragraph beginning on line 54,
"The time stamp represents the count state of the base station counter at
the instant that the first byte of the Downlink MAP Message is transferred
from the Downstream Transmission Convergence Sublayer to the Downstream
Physical Media Dependent Sublayer."

[Reason for Edit]
To clear up the ambiguity that appears in the current specification with
regard to the synchronization method.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
84

[Starting Line #]
49

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the second row ("IUCType") to the Name "Downstream IUC Type Change
Request" and the Value "=4-9, corresponding to Data Grants 1-6".

[Reason for Edit]
This request can be generalized to change the modulation/FEC pair rather
than just the modulation type.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
86

[Starting Line #]
27

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "IUC-1 through IUC-6 Thresholds" to "Data Grant 1-6 Thresholds".

[Reason for Edit]
The thresholds should be for the different data grants, not IUCs.  Note that
there should be a threshold for each data grant that is supported.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
86

[Starting Line #]
41

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Change "IUC Type" heading to "Maximum Modulation Type Supported".

[Reason for Edit]
The "IUC Type" heading is unclear what it refers to.  It appears that it was
used to identify the highest modulation level that is supported by the CPE
on the downlink.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
88

[Starting Line #]
25

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
	1.	Replace 16-QAM and 64-QAM Thresholds with Data Grant 1-6
Thresholds in Table 13.  
	2.	Also, change "IUC Type" Name to "Maximum Modulation Type
Supported".

[Reason for Edit]
	1.	The Data Grants have been generalized to support a
modulation/FEC pair rather than just a modulation.
	2.	To reflect the change from the previous comment.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
154

[Starting Line #]
48

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
	1.	Update this section to reflect that the thresholds are used
to change modulation/FEC pairs rather than just modulation levels.  For
example, the beginning of the first sentence could be changed to "The
downstream modulation/FEC format for data transmission (characterized by the
Data Grant types 1-6) is determined by the BS according ...".
	2.	Also, the first sentence starting at line 58 should read
something like the following, "The CPE applies an algorithm to determine its
best operating modulation/FEC region in accordance with the threshold
parameters established in the RNG-RSP message."
	3.	Update Figure 76 on page 155 to reflect modulation/FEC
groups (or Data Grant Types) rather than just modulation groups.


[Reason for Edit]
To be consistent with the PHY that allows for modulation and FEC changes on
a burst-by-burst basis rather than just the modulation level.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
110

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
	1.	Change the Section 2.5.22 subtitle to "Downlink Data Grant
Type Change Request (DGC-REG) Message".
	2.	Change the first paragraph by replacing "modulation" with
"data grant type" except for after the word "QPSK".  Also, replace "QPSK
modulation" with "the most robust data grant type".
	3.	Under "Parameters shall be as follows:", it should read
Data Grant Types
0x00 = Data Grant Type 1
0x01 = Data Grant Type 2
0x02 = Data Grant Type 3
0x03 = Data Grant Type 4
0x04 = Data Grant Type 5
0x05 = Data Grant Type 6

[Reason for Edit]
To reflect the PHY changes that allow for changes the modulation/FEC pair
(reflected in the different data grant definitions) rather than just the
modulation level.

[Submitter's Last Name]
Foerster

[Submitter's First Name]
Jeff

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
60

[Starting Line #]
44

[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc., (TBD) for a comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Under the Message formats, add a CRC checksum on each MAC message payload
for error detection?

[Reason for Edit]
It seems like all MAC messages should have an error detection capability
associated with them in order to prevent reading erroneous messages.
Currently, there is no error detection capability in the PHY Mode A
Transmission convergence sublayer, and the error detection capability in the
upstream is selectable.  It seems like an error detection capability should
be present in the PHY and/or the MAC layer.  If it is not present in the PHY
layer (as it currently is not in the PHY Mode A), then it either needs to be
added to the PHY Mode A, or needs to be added to the MAC payload.