Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: SRD document review process



Title: SRD document review process
John,
 
The motion you propose mandates a series of subsequent motions based on various outcomes.  On its
face, I believe this motion is way to complicated to be acceptable.    More importantly, if a motion of this
nature passed it would hamstring the working group by making potentially useful motions out of order if they
conflicted with the series of embedded motions that this main motion contains.  I believe it could even interfere
with the chair's ability to make determinations of a procedural basis.   Finally, I don't think that it is appropriate to
impose such restrictions, a priori, on the normal exercise of parlimentary procedure within the working
group.    So, as opposed to trying to untangle the web of motions you're offered, I propose that we stick
to a much simpler process of limited debate and voting to determine whether there exist >75% support for
a specific requirement or for remanding the topic to an ad hoc group.
 
Best regards,
 
Joanne
 
 
 
 -----Original Message-----
From: owner-stds-802-mobility@LISTSERV.IEEE.ORG [mailto:owner-stds-802-mobility@LISTSERV.IEEE.ORG]On Behalf Of Humbert, John J [NTK]
Sent: Thursday, March 11, 2004 7:03 PM
To: STDS-802-MOBILITY@LISTSERV.IEEE.ORG
Subject: SRD document review process

  

   To follow up on Bob Loves earlier e-mail there will be a motion at the

   next meeting dealing with the process for resolving the remaining

   sections. Note that there are changes from Mr. Loves e-mail in the way

   that the WG will process sections that do not meet the 75% rule during

   the first review of the SRD.

  

   The text of the motion is shown below for your consideration.

  

  

   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.

  

   4) Present a motion to the WG  to vote on each option as potential

   baseline text, there are two cases for consideration

  

      a. Only one option for the section

          i. If there is only one option and it gets 75% approval

                then this becomes the baseline text

          ii. If this fails then there will be another motion to

                remand this section to an ad-hoc group for consideration.

         iii. 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.

      b. If more than one option exists for a section

          i. A vote will be taken on each option in the section

          ii. The option with the 75% of the vote will become the

                baseline text.

              a. If more than one option has 75% approval, the

                        baseline text becomes the one with the highest

                        percentage of approval.

         iii. If none of the options considered has 75% approval then:

              a. If there are 3 or more options then the WG

                        will hold another vote on the two options with the

                        highest percentage approval

  

  

         iv. 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.

  

  

         ii. Here again if the motion to remand this to an ad-hoc group fails

         then the process that outlined in a.ii.

  

   4) The Chair of 802.20 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.

  

   END OF MOTION...

  

   If by 3pm on Thursday the WG has not voted to approve the SRD, then there will be an additional motion to adopt the latest consensus version as the baseline document and to require further work on the document via a WG

   ballot circulation using the 802.16 software tool.

  

   Assuming that the 802.16 process is adopted then WG will take the

   output from commentary and make changes to the SRD at the May 2004

   meeting. Only comments submitted within Commentary or comments related

   to changes proposed by the WG will be considered at the next working

   group meeting.

  

Attached is flow chart version of what is described above.

  

   <<Plenary SRD review process1.pdf>>

  

John Humbert

Sprint Corporation

(816) 210-9611