1. 1 Session #56 802.16 Relay TG –Rev.2 Alignment Adhoc Report IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE 802.16j-08/141 Date Submitted: 2008-07-17 Source: Gamini SenarathVoice:+61 3 763 5972 Rev. 2 Adhoc Chair (Relay TG), Nortel Networks, 3500, Carling Av.E-mail:gamini@nortel.neworks Ottawa, Canada Venue: IEEE 802.16 Session #56, Denver, Colorado, USA Base Contribution: None Purpose: Alignment of 16j Text with latest Rev.2 Draft (Rev2/D5) Notice: This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and. ２http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2. Rev2. Alignment Adhoc Report to Session #56 802.16 Relay TG Meeting held on 14-17 July, 2008, at Denver, Colorado, USA Gamini Senarath for Rev. 2 Alignment Adhoc Team

3. 3 The Tasks Assigned to the Adhoc Team 1) Putting a contribution that shows how P802.16j/D5 should be changed so that it provides an amendment to Rev2/D5 2) If Required, to continue to monitor changes to Rev2 (D6, D7, etc) and provide an update to show how to keep P802.16j lined up with Rev2 as we move forward Ad-hoc Team Members: Israfil Bahceci, Wei-peng Chen, Mike Hart, Ting Li, Hyunjeong Kang, Kanchei Loa, Mitsuo Nohara, Yousuf Saifullah, Gamini Senarath (chair), Jungje Son, Sheng Sun, Zhifeng (Jeff) Tao, Chenxi Zhu, Peiying Zhu

4. 4 Outcome as of 13/07/2008 (1)Submitted a contribution to #56 (08/129) outlining the changes required to be incorporated to align Rev2/D5 with the current 16j draft (D5) Further changes identified. Will submit a revision after reviewing 16j reply comments. (2)451 comments. Main types of changes: Reference corrections Original Rev. 2 text is captured wrong The section numbers does not follow Rev2 due to new insertions in Rev. 2. Out of scope changes (Original Rev.2 text changes) were identified and removed from current 16j draft. Will be submitted to maintenance group as a late comment. (e.g. MS  SS/MS changes in Rev2. is out of scope) TLV duplications or inappropriate TLV changes. In appropriate terminology (e.g. MR-BS/BS need to be BS) (3)No major technical issues.

5. 5 Activities/Approach Taken: The first stage of preparation of comments were done using email discussions Different sections of the document was assignment to different members. Each section is reviewed by another member. After the integration another overall review was done and some modifications were made. The contribution was uploaded for review by the general membership. 08/129 A f2f meeting of some of the adhoc team members held on July 13th at Denver and a second round of review was done. These changes will be submitted as a revision together with the reply comment resolutions from general members.

6. 6 Next Steps: Current status: - There are still some sections where the instructions to editor is not clear and some further review is required. These have been identified in the second review process. Currently, the document is under another round of review among team members for further refinement. Reply comments by the general members will be incorporated and a revision would be uploaded for TG approval by Wednesday or Thursday.

7. 7 Recommendations by the adhoc: Approve latest 08/129 contribution after the next round of revisions. Future changes to Rev2 (D6/D7) need to be tracked by assigning the associated responsibility to a group of members. Given the maturity of Rev2 not many changes are expected. Therefore, tracking the changes in Rev. 2 and making the associated changes in 16j may be the easiest way to handle them. To avoid further unnecessary comments created due to these Rev. 2 changes: – The members should be explained the out of scope changes such as editorial changes to Rev. 2 text in 16j. Those need to be forwarded to the maintenance TG. –The future Rev. 2 changes are encouraged to be submitted separately to the Rev. 2 alignment team.