| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi, All, Just talked with Phil and got another clarification
regarding the item as highlighted by yellow
in Phil’s email, i.e., where to put the identification codes in your
comments, the answer is that the identification code shall be the first line of
your comment. Regards, Lei From: Phillip Barber
[mailto:pbarber@BROADBANDMOBILETECH.COM] All TGm participants, Brian has asked me to remind the participants
about one or two things from the TGm
Call for Contributions and Comments. First, the due date for the CfC&C is
rapidly approaching: Sept 5, 2008 Second, all contributions MUST BE
ACCOMPANIED/REFERENCED BY AN APPROPRIATE COMMENT. As usual, use the Commentary Tool to create and export
your comments. Upload your exported comments to the TGm
upload directory at http://dot16.org/upload/ Use ballot id ‘tgmsdd’ in your
comments. The document under review is 802.16m-08/003r4. Use of the Commentary Tool to file
comments is also required for comments EVEN WITHOUT A CONTRIBUTION. Remember that contributions are intended
to supplement comments only when the Problem discussion and/or Proposed Remedy
are so substantial as to require the contribution format for appropriate
presentation. So, please do not file a contribution to propose minor editorial
or technical changes. The commentary tool is well suited to such purpose. To reiterate: comments are the preferred
medium for requesting changes to the SDD text. Only submit a contribution
against the SDD text if the commentary tool proves unsuitable to the complexity
of your presentation. Third, the CfC&C calls for specific identification
of the CfC topic addressed in a contribution: Contributions should
follow the guidelines below: . . . • Specify on the
cover page (in the “Re:” or “Venue:” box) which of the
above mentioned topics the contribution pertains to. . . . The valid entries for the Re: field on the
contribution cover page are: SDD Session 56
Cleanup [related to CfC&C item: Newly accepted text output from the
Rapporteur Groups in Session #56, primarily in Sections 4, 6, 8, 10 and 11] PHY: Text PHY: Link PHY: HARQ PHY: MIMO MAC: HO MAC: Idle Mode MAC: Sleep Mode MAC: Data Plane MAC: Network Entry MAC: Connection
Establishment & Maintenance PHY & MAC aspects of Location Services* PHY & MAC aspects of enhanced MBS* Multi - Carrier Operation* Security* Multi-Radio Coexistence* For these last five italicized* topics the author should
clearly segment and identify the work as PHY or MAC So, a valid entry for the Re: field would
look something like: Re: PHY: Link; in
response to the TGm Call for Contributions and Comments 802.16m-08/033 for
Session 57 Fourth, embed these
identification codes in your comment as well. Comments and contributions will be organized by the identified
topic and resolved during Session 57 in appropriate PHY or MAC session. It is
imperative that both comments and contributions proposed SDD text have PROPER
EDITORIAL INSTRUCTIONS indicating exactly how to add/remove/modify text,
exactly where in the SDD document. Fifth, the RG and Ad-hoc Chairs will be
filing consensus contributions on behalf of the following Rapporteur Groups, by
the deadline: PHY: Text PHY: Link PHY: HARQ PHY: MIMO MAC: HO MAC: Idle Mode MAC: Sleep Mode DO NOT BE ALARMED! Harmonization and
consensus development will continue all the way up to the Session 57 start. RG
participants will continue to have opportunity to refine the consensus
contribution text, and accomplish consensus on topics when not already
achieved. If your text is included in the consensus contributions then you may
choose not to file your own comments and contributions. In any event,
participants that seek a change to these consensus contributions should file Reply
Comments during the Reply Comment period, rather than filing competing
contributions. This goes for both small editorial changes as well as
participants seeking to include otherwise excluded text. Use of the Reply
Comment process will ensure a more orderly and consistent resolution on these
topics. Competing comments and contributions to the consensus document,
comments and contributions not submitted as Reply Comments may very well be
ruled out-of-scope of the Call for Contributions and Comments for all of the
topics remanded to RG and Ad-hocs for processing. A few of these RG and Ad-hoc groups will
almost certainly be renewed for post-Session 57 operation. For instance, the
MAC HO ad-hoc is unlikely to resolve all issues of legacy 16m/16e handover and
inter-technology handover prior to Session 57 finish. But expect that this is
the exception, not the rule. PHY topics especially require resolution during
this meeting Session in order to keep on the project plan, enable the issuance
of the planned call for Stage 3 contributions for Session 58. RG and Ad-hoc
Chairs will be making recommendations on renewal prior to the end of Session
57. So, participants should expect that comments and contributions related to
continued RGs and Ad-hocs will be deferred to those groups for post-Session 57
work. Regardless, be aware that there will be
extremely limited time to discuss ANY contribution at Session 57. There is a
HUGE number of topics that were out for RG and Ad-hoc work during this
inter-Session interim period and limited time and facilities will simply not
allow such debate on the agenda, in addition to our other critical agenda
items. Plan appropriately. Sixth, obviously the restrictions and
process for RG and Ad-hoc material does not apply to those items that were not
part of any RG or Ad-hoc harmonization efforts: SDD Session 56
Cleanup [related to CfC&C item: Newly accepted text output from the
Rapporteur Groups in Session #56, primarily in Sections 4, 6, 8, 10 and 11] MAC: Data Plane MAC: Network Entry MAC: Connection
Establishment & Maintenance PHY & MAC aspects of Location Services* PHY & MAC aspects of enhanced MBS* Multi - Carrier Operation* Security* Multi-Radio Coexistence* Comments and contributions related to
these topics will be reviewed, and for SDD Session 56 Cleanup items resolved
during the Session. Expect the creation of Rapporteur Groups to continue harmonization
and consensus development on the unresolved topics for the period after Session
57 till Session 58 in On behalf of the participants of the RGs
and Ad-hocs, I want to convey my sincere thanks to all of the RG and Ad-hoc
Chairs for their dedication and hard work during this interval. We had a
substantial number of concurrent projects underway--many of substantial
complexity and contestation--during this inter-Session interim period. Their
significant efforts have made this, what appears to be, a productive cycle. We
all deserve recognition for this accomplishment. But we are in the home stretch
now and we need to finish delivery of our joint efforts. It would be a shame to
have things fall apart in the endgame. So no time to rest. Let’s make this
last tenday count! Thanks, Rapporteur Group Chair Coordinator, IEEE 802.16 TGm From: Kiernan, Brian G
[mailto:Brian.Kiernan@INTERDIGITAL.COM] I realize many of you would
like as much time as possible to
develop your comments and contributions,
but I do think
80 years is a tad excessive. Submissions are due no later than 5 September 2008
AOE Brian -----Original Message----- Some of you may have noticed that that the latest version of the
802.16m SDD, <http://www.ieee802.org/16/tgm/docs/80216m-08_003r4.zip>
has been posted on the TGm web page. In conjunction with this, a Call for
Comments and Contributions, <http://www.ieee802.org/16/tgm/docs/80216-08_033.pdf>
for session #57 has also been posted. Submissions are due no later than 5 September 2088 AOE. Brian |