stds-802-16: TG1 COMMENT:

["Hoon Choi" <hchoi@antd.nist.gov>]

[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
110

[Starting Line #]
51

[(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]
It is written as "transmission timings are linked via the Upstream TimeStamp
within the DS-MAP and the US-MAP messages." But no messages such as DS-MAP
or US-MAP message have been defined in the draft. 
Instead of adding DS-MAP and US-MAP messages, we can use already defined 
messages with similar function. Downstream and upstream information can be 
transmitted to CPEs periodically via Downstream Channel Descriptor message 
and Upstream Channel Descriptor message, respectively.  
Considering these messages don't have "Upstream TimeStamp" but have
other timeing information, new text can be 
"transmission timings are linked via the timing information
within the Downstream Channel Descriptor and the Upstream Channel Descriptor
messages."  

[Reason for Edit]
To correct use of undefined messages in draft #1



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
121

[Starting Line #]
26

[(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]
It is written as "The BS may allow collisions on either Requests or Data
PDUs". 
Based on the current media access control of the draft, 
the Data PDUs are always transmitted via data slot without collision
once they are granted a bandwidth for data. 
Therefore the new text should be 
"The BS may allow collisions on Requests PDUs only."   

[Reason for Edit]
To delete a misleading description in draft #1



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
81

[Starting Line #]
2

[(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]
Make "PCD Count" typesetted in bold face  

[Reason for Edit]
To fix a typo in draft #1



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
81

[Starting Line #]
7

[(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]
Insert "of" between "Number" and "Elements"   

[Reason for Edit]
To fix a typo in draft #1




[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
112

[Starting Line #]
46

[(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]
Insert a space in a word "processby" to make "process by"   

[Reason for Edit]
To fix a typo in draft #1



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
123

[Starting Line #]
31

[(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]
In the entry of the third row, fourth column of the Table 16,
it is written that Polling is not allowed for UGS-AD service flow type. 
But, periodic unicast polling is performed for the UGS-AD service type 
when the flow is inactive, as mentioned in section 2.9.3.
Therefore the entry should be written as 
"Unicast polling is allowed when the flow is inactive".    

[Reason for Edit]
To fix a typo in draft #1



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
123

[Starting Line #]
64

[(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]
"Piggy-back requests may be used to request additional bandwidth 
for a different connection using the Bandwidth Request Header." 
This is true only in the GPT mode because there is no way in the
GPC mode to specify the ID of the connection for which 
this additional bandwidth request is made. 
Therefore it may be better to write as 
"Piggy-back requests may be used in the GPT mode to request
additional bandwidth for a different connection using the 
Bandwidth Request Header." 

Another solution may be to add Piggyback CID (PCID) field(2 octets) 
right after Grant Management field and before HCS field 
in the generic MAC header(Figure 13). Then the
piggy-back requests may be used for both the GPT and GPC modes.
This gives a new capability to the GPC mode, and it also makes 
the GPT mode more flexible to select either piggybacking or bandwidth 
stealing for the same purpose. 

[Reason for Edit]
To add additional information for better understanding.



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
124

[Starting Line #]
9

[(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 Bandwidth Management fiels in the Generic MAC Header..."
must be read as 
"The Grant Management fields in the Generic MAC Header..." 
as defined in the generic MAC header(Figure 13). 

[Reason for Edit]
To fix a typo in draft #1.



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
126

[Starting Line #]
31

[(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 word "CPE" in "The number of bytes requested shall be the total 
number that are desired by the CPE at the time of the request..."
must be read as "connection" because the bandwidth is requested 
on a connection basis in either the GPT or GPC mode.


[Reason for Edit]
To fix a typo in draft #1.



[Submitter's Last Name] 
Choi

[Submitter's First Name]
Hoon

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

[Starting Page #]
134

[Starting Line #]
53

[(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]
Insert a section explaining the definition and usage of the
piggy-backing and bandwidth stealing.


[Reason for Edit]
For better understanding of draft #1.