| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear Phillip and
all,
Comment #600 should be in
the category of "Connection" rather than "Data plane". The comment is
targeted at Page 27, Line 2.
We are sorry for the
inconvenience.
Best Regards,
Chun-Yen Hsu
Institute for Information Industry From: Phillip
Barber [mailto:pbarber@broadbandmobiletech.com] All TGm
Participants, To provide a little
more detail on instances where different topic identifier tags were assigned
than that indicated by the commenter: Twenty-nine comments
were judged to actually be ‘SDD Cleanup – PHY’ but were labeled by their
commenter as ‘PHY: Text’, which was a tag reserved for the output of the PHY
Text Rapporteur Group output, as provided by the PHY Text RG Chair. All such
comments have been reassigned to ‘SDD Cleanup –
PHY’. Eighteen
comments submitted with the tag ‘PHY: MIMO’ were judged to instead be ‘SDD
Cleanup – PHY’ as they primarily seemed to deal with modification of existing
text in the MIMO section of the SDD, and did not appear to be topics under
current review in the MIMO Rapporteur Group. There were
some forty-four additional comments submitted inappropriately and against
instruction as ‘PHY: HARQ’, ‘PHY: MIMO’, or ‘MAC: Idle Mode’. These topic tags
were, again, reserved for the output of the respective Rapporteur Groups, as
provided by the RG Chair(s). Participants were instructed that they were to
instead submit Reply Comments, not original comments, against the RG outputs on
these topics. All of these comments have been tagged as
‘out-of-scope’. Two
additional comments were tagged ‘out-of-scope’ because they identified
themselves as dealing with material not in the
CfC&C. Participants are
encouraged to review the RG output comments and contributions and avail
themselves of the opportunity to file Reply Comments to recommend
add/remove/changes to RG text. This encouragement is extended to specifically
include those whose original comments on RG topics were tagged ‘out-of-scope’.
Note that final RG revision uploads are not due until Sept 12 AOE. Participants
may choose to prepare and withhold Reply Comments until after reviewing the
final pre-Session revision of the RG consensus output comments and
contributions. As Roger indicated in
his invitation for Reply Comment email announcement, participants—both the
owners of the comments as well as other participants—have the opportunity in the
Reply Comment process to recommend changes to the tag assignment for all
comments. Thanks,
From: Roger B.
Marks [mailto:r.b.marks@IEEE.ORG] The IEEE 802.16 TGm SDD Call for Contributions and
Comments (CfC&C) IEEE 802.16m-08/033 <http://ieee802.org/16/tgm/#08_033>
closed on 5 Sept. The 613 comments received have been compiled into a
Commentary database and posted as IEEE 802.16m-08/034r2 <http://ieee802.org/16/tgm/#08_034>. This note is a Call for Reply Comments, with a deadline
of Monday 15 Sept at 8 pm local time in Comments were requested to identify a specific topic in
the CfC&C. This identification is primarily intended as a tool for
process control, agenda planning, and resolution assignment. TGm leadership
has reviewed the comments and assigned topic identifiers for all comments, in
most cases in alignment with the recommendation of the commenter. The
assigned topic has been identified in the Commentary database tool by a new
‘Comment Tag:’ field that you will see just below the Suggested Remedy. The
following tags are assigned:
Reply comments may include a request (explained in
free-form text) to revise the Comment
Tag. The Commentary file will open to the view in which you
can begin entering reply comments. Use the "Submit Reply Comments" tab in the
upper right corner to export your replies to a file for uploading, per the
embedded instructions. Reply comments, in "cmtr" format, need to be uploaded to
the "TGm" folder at <http://upload.wirelessman.org>. Roger __________ NOD32 3433 (20080910) Information __________ This message was checked by NOD32 antivirus system. http://www.nod32.com.hk |