ProjectIEEE Working Group on Mobile Broadband Wireless Access TitleRepeater issues for MBWA Date Submitted Source(s)John Humbert 6220 Sprint Parkway, MS KSOPHD D276 Overland Park, KS Voice: (816) Fax: (913) Re:System Requirements Update AbstractThis contribution provides an update on the status of the System Requirements document. PurposeStatus Update / Process for SRD Notice This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) 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 Patent Policy The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development.Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3http://standards.ieee.org/board/pat/guide.html IEEE C /75

-2- C System Requirements update SRD Status Significant Changes made since the last Plenary Open sections Next Steps

-3- C SRD Status 2 conference calls since the January Meeting Version 11r of the System Requirements posted on the IEEE web site.

-4- C Concerns/ Next Steps Concerns –The CG process is not developing further consensus on the SRD language –The CG needs greater involvement from the WG to obtain an approved SRD –This requires news processes for WG meetings and the interval between meetings Next Steps –Motion for WG process in session #7

-5- C802.20

-6- C SRD Procedure Motion (pg 1 of 4) Whereas it is the desire of the working group to complete the System Requirements document by the end of the March meeting and the SRD has gone about as far as it can go with the current correspondence group process and most of the work remaining needs to be completed by the working group. Therefore the WG shall adopt the following process to review and approve the System Requirements Document during session #7 in Orlando. It is noted that adoption of this process will allow Immediate motions and voting on the system requirements document text. 1.Review the section as presented in latest version of the SRD. 2.Call for additional contributions for that particular section (section is defined as X.X.X) 3.Hold a brief discussion on each contribution. The idea is not to debate the contribution but rather provide an opportunity for the WG to consider the rational behind the proposed language. Presentations are limited to 5 minutes and then the floor is open for 5 minutes or the time required for one comment per person in the discussion queue for questions.

-7- C SRD Procedure Motion (pg 2 of 4) 1.Present a motion to the WG to vote on each option as potential baseline text, there are two cases for consideration 1.Only one option for the section 1. If there is only one option and it gets 75% approval then this becomes the baseline text 2.If this fails then there will be another motion to remand this section to an ad-hoc group for consideration. 3. If the motion to remand the section to an ad-hoc group fails then there will be another vote on whether or not this section should be dropped from consideration by the WG. This motion must have at least 75% of the members voting in favor to end consideration of this section by the working group.

-8- C SRD Procedure Motion (pg 3 of 4) If more than one option exists for a section 1.A vote will be taken on each option in the section 2.The option with the 75% of the vote will become the baseline text. 1.If more than one option has 75% approval, the baseline text becomes the one with the highest percentage of approval. 3.If none of the options considered has 75% approval then: 1.If there are 3 or more options then the WG will hold another vote on the two options with the highest percentage approval 2.If neither one of the two top options passes the 75% threshold then there will be a motion to remand the option with the highest percentage to an ad-hoc group for further development. Obviously the option with the highest percentage approval becomes the working text for the ad-hoc group and the other options will be dropped. 4.Here again if the motion to remand this to an ad-hoc group fails then there will be another vote on whether or not this section should be dropped from consideration by the WG. This motion must have at least 75% of the members voting in favor to end consideration of this section by the working group.

-9- C SRD Procedure Motion (pg 4 of 4) The Chair of shall establish ad-hoc groups as needed, progress reports from the working group leaders are due to be presented to the working group ON THURSDAY MARCH 18TH. The working group will again follow the procedure outlined above except that any sections that do not have baseline text will follow the process that the WG approves for handling issues between meetings.