[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

stds-802-16: TG1 Comment




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
20

[Starting Line #]
51

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Add to the MAC-CREATE-CONNECTION.request primitive a field called
'ARQ parameters'. The ARQ parameters include detials on whether ARQ is used
or
not for the connection, maximum re-transmission limit and acknowledgment
window size.

[Reason for Edit]
This comment has been resolved as accepted (see IEEE 802.16.1-00/09 item 49
at
page 10), but is missing from the current version of the draft.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
20

[Starting Line #]
51

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add to the MAC-CREATE-CONNECTION.request primitive a field called
'fragmentation'. The values for this field can be ON or OFF, and indicate
the fragmentation is used in this connection

[Reason for Edit]
Compatibility with the definition in page 123, line 54 of the draft, that
says
'The authority to fragment a traffic on a connection is defined when the
connecion is created by a MSAP.'




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
33

[Starting Line #]
40

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
G  

[Detailed Description of Proposed Insertion, Deletion, Change]
Timing values are referenced to symbol duration. This is PHY dependant, and
may not suit an OFDM PHY for instance. 

[Reason for Edit]
Make MAC suitable for use with PHY other than QAM 




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
35

[Starting Line #]
62

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the downstream modulation configuration field from the configuration
file.

[Reason for Edit]
Specifing the downstream modulation alone is not compatible with the concept
of IUC. The information contined in this field should be obtained from
listenting to the DCD messages.                   




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
40

[Starting Line #]
15

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
The SS modulator and SS demodulator fields are not enough to describe the
capability of a station. Another pair of TLVs should be added to describe
ECC
capability. Alternatively, the existing TLVs can be expanded to describe
modulation and ECC combinations supported. The following encoding could be
used,
       Bit #0: QPSK
       Bit #1: 16-QAM
       Bit #2: 64-QAM
       Bit #3: RS
       Bit #4: RS + Parity
       Bit #5: RS + BCC
       Bit #6: BTC

[Reason for Edit]
Specifing the modulation alone is not compatible with the concept of IUC.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
40

[Starting Line #]
36

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
FDD (burst downstream) and Half-Duplex FDD are now one mode, and therefore
should have one value in the TLV value field.

[Reason for Edit]
Correct an inconsistency in the draft




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
65

[Starting Line #]
5

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change 'Generic header' in figure 18 to 'Generic MAC header'

[Reason for Edit]
Consistency with figure 17 in the previous page




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
67

[Starting Line #]
5

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
The contents of the 'MAC Management Header' in figure 19 is not explained
anywhere in the document. Probably slipped somewhere along the way.

[Reason for Edit]
A missing detail that should be explained.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
74

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change 'dB' to 'dBm'.

[Reason for Edit]
Fix typo.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
76

[Starting Line #]
47

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change 'more less' to 'less robust'.

[Reason for Edit]
Fix typo.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
82

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove the sentences 'Within each pair, the short and long grant usage is 
distinguished by the maximum burst size. This allows short PDU transmissions
for services that are tolerant of packet loss to use less FEC coding
(relative
to longer grants).'

[Reason for Edit]
These lines seem to refer to the concept of short and long data grants,
which
has been replaced with the concept of interval usage codes.





[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
83

[Starting Line #]
1 

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Table 8 and table 13 both refer to the uplink map information elements, and 
seem to be the same. One of them should be replaced by information on
downlink
map information elements.

[Reason for Edit]
Duplication and missing information.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
88

[Starting Line #]
1 

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove lines 1 to 65.

[Reason for Edit]
This comment has been resolved as accepted (see IEEE 802.16.1-00/09 item 92
at page 11), but is missing from the current version of the draft.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
109

[Starting Line #]
8 

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
TBD

[Detailed Description of Proposed Insertion, Deletion, Change]
Add a description of the ARQ ACK message containing the following fields,
MAC Management Header
One TLV encoded information element where
Type   = ARQ-ACK message
Length = N, is two times the number of ACK sequence number carried by the
TLV
Value  = A list of N sequence number that where successfully received

[Reason for Edit]
Define a TBD item




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
122

[Starting Line #]
26

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T  

[Detailed Description of Proposed Insertion, Deletion, Change]
The sentence 'The BS may allow collisions on either requests or maintenance
PDUs.' does not specify clearly enough which PDUs may be transmitted in
contention slots. Replace with 'The BS may allow collisions on the following
PDUs: RNG-REQ, REG-REQ, PKM-REQ, DSA-REQ, DSC-REQ, DSD-REQ, DCC-REQ,
MCA-REQ,
DMC-REQ, Bandwidth request header.'

[Reason for Edit]
Make the draft more clear.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
137

[Starting Line #]
18

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T  

[Detailed Description of Proposed Insertion, Deletion, Change]
Remove lines (d) and (e) from the SS synchronization list. Insert new items
d) Synchronization of TC sub-layer (if it exists)
e) Recognition of the DL-MAP message                                        

[Reason for Edit]
MPEG packetization no longer exists, and PCD MAC messages are not defined in
this draft. The two suggested items are their replacement.




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
144

[Starting Line #]
1 

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E  

[Detailed Description of Proposed Insertion, Deletion, Change]
Combine the figure in this page and in the next page to one figure.

[Reason for Edit]
It is not clear how the two existing figures connect to each other 




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
289

[Starting Line #]
19

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E 

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the first sentence of the paragrph to read, 'The PHY/MAC control
portion
of the downstream frame shall be encoded with a well known modulation and
coding combination designated as TDM Burst Type 1 with DIUC = 0. TDM Burst
type
1 uses a fixed set of parameters in order to ensure that all subscriber
stations can read the information.'

[Reason for Edit]
Define explicitly the MAC DIUC code 0 




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
282

[Starting Line #]
57

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E 

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the value for the protection requiered to for the RS code to
t=0 to t=16

[Reason for Edit]
Compatibility with table 9 (page 71), table 12 (page 76), table 90 (page
311),
table 80 (page 297)that define RS correction capability T=0-16




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
299

[Starting Line #]
27

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E 

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the value for the protection requiered to for the RS code to
t=0 to t=16

[Reason for Edit]
Compatibility with table 9 (page 71), table 12 (page 76), table 90 (page
311),
table 80 (page 297)that define RS correction capability T=0-16




[Submitter's Last Name] 
Leiba

[Submitter's First Name]
Yigal

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

[Starting Page #]
313

[Starting Line #]
32

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar,
etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T 

[Detailed Description of Proposed Insertion, Deletion, Change]
Delete the paragraph starting with 'In order to satisfy timing requirements
for telephony or other CBR applications (T1/E1)...' and ending with '... or
an
internal oscillator with time stamps coming from the MAC layer at the base
station.'
Another option is to make the requirements in this paragraph non mandatory
(i.e. replace 'should' by 'may')

[Reason for Edit]
Supplying the clock for entities outside the scope of the standard need not
be a mandatory part of the standard.