stds-802-16: TG1 COMMENTS

[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
77
[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"]
T
[Detailed Description of Proposed Insertion, Deletion, Change]
Insert a field "# of map elements (= 0 for PHY type 5)" before the map
elements.
[Reason for Edit]
Potentially easier HW processing of map.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
77
[Starting Line #]
61
[(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"]
[Detailed Description of Proposed Insertion, Deletion, Change]
Insert "for PHY type = {0,1}" after "Frame Length types"
[Reason for Edit]
clarity
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
79
[Starting Line #]
10
[(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]
Show Map Elements as 20-bit values.
[Reason for Edit]
Saves bandwidth. Not really any more difficult to process.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
79
[Starting Line #]
21
[(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]
Insert final map element with "DIUC=15" and "end PS of DL frame"
[Reason for Edit]
Dangerous to expect SS to guess where frame ends.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
79
[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"]
T
[Detailed Description of Proposed Insertion, Deletion, Change]
Replace the entire paragraph with "SSs listen to all portions of the
downlink that they are capable of listening to. For full-duplex SSs this
means all portions (TDM and TDMA) that have a robustness (as defined by the
DIUC) greater than or equal to that negotiated with the BS. For half-duplex
SSs there is the additional requirement that they shall not attempt to
listen to portions of the downlink coincident with their allocated uplink
transmission, if any, adjusted by their Tx time advance."
[Reason for Edit]
Since CIDs were removed from the DL Map, the original description is out of
date.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
80
[Starting Line #]
28
[(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]
Insert space between "Request" and "Backoff"
[Reason for Edit]
typo
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
81
[Starting Line #]
4
[(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]
Insert space between "the" and "UCD"
[Reason for Edit]
typo
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
82
[Starting Line #]
24
[(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]
Delete the entire paragraph
[Reason for Edit]
This concept was already removed in response to previous comments, but this
instance escaped the editors.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
84
[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"]
T
[Detailed Description of Proposed Insertion, Deletion, Change]
Change "Registration CID" to "Basic CID" and remove "(previously assigned in
REG-RSP)"
[Reason for Edit]
By this time an SS has a Basic CID, which shouldn't change unless it also
changes downlink. Additionally, there is no Registration CID.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
86
[Starting Line #]
45
[(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 concept of "Temporary CID" should be dropped as it is not as useful here
as it was in DOCSIS. The RNG-RSP message should return the Basic CID and
the secondary management CID. Low level MAC control (power control,
additional ranging) should happen over the basic CID. Large, more delay
tolerant actions such as TFTP of the configuration file, authentication, and
privacy messages should happen on the secondary management connection.
[Reason for Edit]
It's just as easy to age out 2 CIDs as it is to age out 1, so the TID isn't
necessary. The concept of a basic CID and a secondary management CID
separate from the user data CIDs is in the system for a reason. It was
agreed that there are small, quick response messages (power adjustment, etc)
that must be handled quickly but are short enough to not threaten the QoS of
other connections (Basic CID). There are also higher level management
messages that tend to be larger and more delay tolerant such as
configuration file TFTP, SNMP, etc (secondary management CID). After
meeting 7.5(?) in Boulder, there was an action to divide up management
messages between these two categories, but it never happened.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
65
[Starting Line #]
50
[(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 REG-REQ, REG-RSP, REG-ACK, PKM-REQ, and PKM-RSP messages should all be
on the secondary management CID. Additionally, provisioning of connections,
whether at SS initial access or dynamic, should happen over the secondary
management CID, while actual connection state changes could happen over the
Basic CID.
[Reason for Edit]
The concept of a basic CID and a secondary management CID separate from the
user data CIDs is in the system for a reason. It was agreed that there are
small, quick response messages (power adjustment, etc) that must be handled
quickly but are short enough to not threaten the QoS of other connections
(Basic CID). There are also higher level management messages that tend to
be larger and more delay tolerant such as configuration file TFTP, SNMP, etc
(secondary management CID). After meeting 7.5(?) in Boulder, there was an
action to divide up management messages between these two categories, but it
never happened.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
87
[Starting Line #]
25
[(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]
I thought we agreed to eliminate this last meeting. Aslo applies to all of
page 88.
[Reason for Edit]
unimplemented comment
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
89
[Starting Line #]
3
[(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 "allowing the CID shall be encoded in a type/length/value form"
[Reason for Edit]
The CID is in the MAC header.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
89
[Starting Line #]
42
[(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]
References to where these paramaters are defined should be included.
[Reason for Edit]
clarity of definition
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
92
[Starting Line #]
22
[(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]
Move lines 22-34 to the RNG-RSP message.
[Reason for Edit]
The concept of a basic CID and a secondary management CID separate from the
user data CIDs is in the system for a reason. It was agreed that there are
small, quick response messages (power adjustment, etc) that must be handled
quickly but are short enough to not threaten the QoS of other connections
(Basic CID). There are also higher level management messages that tend to
be larger and more delay tolerant such as configuration file TFTP, SNMP, etc
(secondary management CID). After meeting 7.5(?) in Boulder, there was an
action to divide up management messages between these two categories, but it
never happened.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
92
[Starting Line #]
55
[(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]
Insert space between "SS" and "capability"
[Reason for Edit]
typo
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
95
[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"]
TBD
[Detailed Description of Proposed Insertion, Deletion, Change]
eliminate TBD
[Reason for Edit]
TBDs are evil
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
95
[Starting Line #]
42
[(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]
We need to fix the way we define and reference TLVs.
[Reason for Edit]
Most of the TLVs for the variants of this message are in section 2.16.
There is one TLV in 2.3 that appears appropriate, but defines nothing and
points to section 2.16.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
97
[Starting Line #]
21
[(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]
We need to fix the way we define and reference TLVs.
[Reason for Edit]
The set defined starting on page 43 appears insufficient.
[Submitter's Last Name]
Stanwood
[Submitter's First Name]
Ken
[Membership Status: (M)ember; (O)bserver; (N)either]
M
[Starting Page #]
104
[Starting Line #]
52
[(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 "QohS" to "QoS"
[Reason for Edit]
typo