stds-802-16: TG1 Comments

["Rakesh Gupta" <rakesh.gupta@alcatel.com>]

[Submitter's Last Name]
Gupta

[Submitter's First Name]
Rakesh

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

[Starting Page #]
29

[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"]
T
[Detailed Description of Proposed Insertion, Deletion, Change]
There are separate bit transmission procedures defined for the upstream
and downstream.  There is no technical reason that they should not be
the same. It is proposed that the text in the first three paragraphs of
this section be replaced by the following text:

"Within the MAC layer, when numeric quantities are represented by more
than one byte (i.e., 16 bit and 32 bit values), the byte containing the
most significant bits is the first transmitted.  This is sometimes
called byte-big-endian order.

Since all the parameters consist of integral number of bytes, the MAC
messages can be considered as a stack of  bytes.  The first byte
transmitted is the one at the top of the stack and the last one at the
bottom.  Within each byte the bits are transmitted with the most
significant bit first."

[Reason for Edit]
To have a consistent message transmission procedures in both the
upstream  and downstream.

[Submitter's Last Name]
Gupta

[Submitter's First Name]
Rakesh

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

[Starting Page #]


[Starting Line #]


[(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]
A minimal subset of the PHY and MAC layer protocols for both the base
station and the subscriber station should be identified and agreed upon
for ease of interoperability.  It would be quite useful to identify in a
single place which are the mandatory and optional parameters, messages
and procedures.

[Reason for Edit]
To facilitate interoperability.

[Submitter's Last Name]
Gupta

[Submitter's First Name]
Rakesh

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

[Starting Page #]


[Starting Line #]


[(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]
The TLVs for various parameters should be defined in a single place.
This will enhance the readability of the document and will make it
easier to reference.

[Reason for Edit]
To improve readability.

[Submitter's Last Name]
Gupta

[Submitter's First Name]
Rakesh

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

[Starting Page #]


[Starting Line #]


[(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]
Some of the type values used are unique within a message and not across
the entire MAC Message set while others are unique across the MAC
message set.  This may cause problems in the future if some of the
parameters which are not unique across the MAC message set are to be
used by a new message.  All type values should be unique across the MAC
message set.

[Reason for Edit]
To provide for future evolution of the standard.