All TGm participants,
After discussion with several members, several RG Chairs, and
consultation with Brian, there will be a slight change to the RG work
plans to align better with the TGm project process flow. This
alignment is designed to ensure that participants have the best
opportunity to provide useful Reply Comments on the original comments
and consensus contributions filed by the RG and Ad-hoc Chairs.
RG/AHG Chairs shall submit a comment and associated/referenced
consensus contribution as the output of the RG. The Chairs shall
submit the comment and contribution by the Sept 5 AOE deadline
specified in the original TGm Call for Contributions and Comments
<http://grouper.ieee.org/groups/802/16/tgm/docs/80216m-08_033.pdf>.
The Reply Comment period then opens, due to close on Sept 16, 8am Kobe
time (the opening of the Kobe Session).
But the RG/AHGs keep conducting harmonization/consensus development.
The RG/AHG Chairs submit their final pre-Session revision of their
consensus contribution by Sept 12 AOE. Members then have from Sept 13
AM to Sept 16 AM to update/prepare any Reply Comments based on this
final pre-Session revision of the RG/AHG consensus comments and
contributions, and then file them by the Sept 16 8am Kobe deadline.
Members are encouraged to develop the comments early, but should
withhold submittal until after having an opportunity to review the
final pre-Session consensus contribution uploaded on Sept 12.
Reply Comments need not include the identification ‘tags’ (PHY: Text,
PHY: Link, MAC: HO, etc…) as the Reply Comments are automatically tied
to the original comment which will already have such tag. The Reply
Comments effectively inherit the tag, and there is no confusion in
PHY/MAC session assignment for resolution.
On Sept 16 during the day the RG/AHG Chairs will review the Reply
Comments and make reasonable update/revision to the consensus
contribution and re-post. We will arrange the TGm agenda so that the
RG/AHG Chairs have the time for their review and update.
During the PHY and MAC sessions, respectively, the agenda will include
a period to resolve the comments for the output of the RGs. Reply
Comments will be considered during this process.
To be clear, Reply Comments is the intended method of participant
comment on the consensus output of the RG and Ad-hoc activity.
Participants should use Reply Comments to both request minor editorial
changes to the proposed consensus text, as well as more substantial
add/remove/modification requests to that consensus text. Participants
should use the Reply Comment process to indicate alternate
view/modified proposals and contributions.
Should participants instead elect to submit competing original
comments and contributions (not Reply Comments due on Sept 16, but
original Comments due on Sept 5), it is very likely that the Chair of
the PHY or MAC session in Kobe will reject the competing comment as
‘out-of-scope’, as the output of the RG is not covered in the original
TGm Call for Contributions and Comments
<http://grouper.ieee.org/groups/802/16/tgm/docs/80216m-08_033.pdf>.
One note: the restriction that participants use the Reply Comments
instead of original comments to address the RG and Ad-hoc outputs only
applies to the matter of the RG and Ad-hoc output. Participants are
absolutely expected and required to file original comments (though
they may follow with Reply Comments later), with or without
contributions, on all of the matters in the TGm Call for Contributions
and Comments
<http://grouper.ieee.org/groups/802/16/tgm/docs/80216m-08_033.pdf> for
which they wish to make comment:
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.
Thanks,
Phillip Barber
Chief Scientist
Wireless Advanced Research and Standards
Huawei Technologies Co., LTD.
Rapporteur Group Chair Coordinator, IEEE 802.16 TGm
* From: * Phillip Barber [mailto:pbarber@BROADBANDMOBILETECH.COM]
*Sent:* Thursday, September 04, 2008 5:03 PM
*To:* STDS-802-16@LISTSERV.IEEE.ORG
*Subject:* [STDS-802-16] FW: [STDS-802-16] TGm Call for SDD Comments
and Contributions
All TGm participants,
Brian has asked me to remind the participants about one or two things
from the TGm Call for Contributions and Comments
<http://grouper.ieee.org/groups/802/16/tgm/docs/80216m-08_033.pdf>.
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
<http://dot16.org/Commentary/> to create and export your comments.
Upload your exported comments to the TGm
<http://dot16.org/ul/ul.cgi?command=viewupload&database=TGm_db> upload
directory at http://dot16.org/upload/
Use ballot id ‘tgmsdd’ in your comments. The document under review is
802.16m-08/003r4
<http://grouper.ieee.org/groups/802/16/tgm/docs/80216m-08_003r4.zip>.
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 Dallas .
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,
Phillip Barber
Chief Scientist
Wireless Advanced Research and Standards
Huawei Technologies Co., LTD.
Rapporteur Group Chair Coordinator, IEEE 802.16 TGm
* From: * Kiernan, Brian G [mailto:Brian.Kiernan@INTERDIGITAL.COM]
*Sent:* Sunday, August 10, 2008 9:09 PM
*To:* STDS-802-16@LISTSERV.IEEE.ORG
*Subject:* Re: [STDS-802-16] TGm Call for SDD Comments and Contributions
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-----
From: Kiernan, Brian G
Sent: Friday, August 08, 2008 5:57 PM
To: Roger B. Marks; STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] TGm Call for SDD Comments and Contributions
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