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

Re: [802SEC] Straw Poll on: LMSC Operations Manual



I also agree with Pat.

Carl
 

> -----Original Message-----
> From: ***** IEEE 802 Executive Committee List ***** 
> [mailto:STDS-802-SEC@ieee.org] On Behalf Of Jerry1upton@AOL.COM
> Sent: Wednesday, July 19, 2006 1:24 AM
> To: STDS-802-SEC@listserv.ieee.org
> Subject: Re: [802SEC] Straw Poll on: LMSC Operations Manual
> 
> I agree with Pat.
> Regards,
> Jerry Upton
> 
> In a message dated 7/18/2006 8:50:35 PM Central Standard 
> Time, pthaler@BROADCOM.COM writes:
> I feel our rules should be stable and we should be able to 
> work with changing rules once per year. If we do partition, 
> there is no way of ensuring that the places we decide we need 
> to change are in the operations manual. 
> 
> It is more difficult to use two documents. With the SB P&P 
> and Ops Manual, I find I have to go to both to check what the 
> rule is on a topic. 
> 
> It can also be more work to maintain. Even with one document 
> we find holes and contradictions in the rules. Two documents 
> won't make that better.
> 
> Regards,
> Pat 
> 
> -----Original Message-----
> From: ***** IEEE 802 Executive Committee List ***** 
> [mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of Sherman, 
> Matthew J.
> (US SSA)
> Sent: Monday, July 17, 2006 8:22 AM
> To: STDS-802-SEC@LISTSERV.IEEE.ORG
> Subject: Re: [802SEC] Straw Poll on: LMSC Operations Manual
> 
> I note that the SA SB finds it necessary to do this for their rules.  
> 
> Till now the current rules have not been tightly enforced.  
> They are starting to tighten up enforcement.  To my knowledge 
> I have never received formal approval of any P&P I have 
> submitted to AudCom and AudCom has never posted any version 
> of our P&P.  My understanding it that AudCom does not plan to 
> review our P&P more than once a year (imagine them trying to 
> review all P&P throughout IEEE more than that).
> I do not believe only being able to change our rules only 
> once per year is acceptable.
> 
> Mat
> 
> Matthew Sherman, Ph.D. 
> Senior Member Technical Staff
> BAE SYSTEMS, NES
> Office: +1 973.633.6344
> email: matthew.sherman@baesystems.com 
> 
> 
> -----Original Message-----
> From: Bob O'Hara (boohara) [mailto:boohara@cisco.com]
> Sent: Monday, July 17, 2006 10:44 AM
> To: Sherman, Matthew J. (US SSA); STDS-802-SEC@listserv.ieee.org
> Subject: RE: [802SEC] Straw Poll on: LMSC Operations Manual
> 
> Mat,
> 
> I fail to see from the material you supplied that changing 
> our P&P is any more difficult that before.  They have always 
> had to be approved by AudCom to be official.  The only new 
> requirement is that AudCom must post them in a common 
> location.  This places no new requirements or obligations on us.
> 
> I say there is no need to separate and maintain two different 
> documents.
> 
> 
> 
> -Bob
> 
> -----Original Message-----
> From: ***** IEEE 802 Executive Committee List ***** 
> [mailto:STDS-802-SEC@ieee.org] On Behalf Of Sherman, Matthew 
> J. (US SSA)
> Sent: Sunday, July 16, 2006 11:00 PM
> To: STDS-802-SEC@listserv.ieee.org
> Subject: [802SEC] Straw Poll on: LMSC Operations Manual
> 
> Folks,
> 
> Please respond to the following straw poll:
> 
> Should we partition our current P&P into a P&P and subsidiary 
> Operations Manual?
> 
> Background: 
> 
> The changes below were approved by the standards board.  It 
> has been suggested on several occasion that we should split 
> our rules into a more rigorous 'bylaws' type document that 
> would be our actual P&P, and a lesser subsidiary document 
> which still be binding governance, but be lower in the order 
> of precedence and easier to change.  Most of the material 
> based on the Model P&P would remain in the current P&P, and 
> sections that aren't required for the P&P would wind up in 
> the operations manual.
> 
> Given the current changes in SA I believe it is even more 
> imperative to more towards this format because changing the 
> P&P will be that much more difficult under the new rules.  
> One of the push backs I received at the P&P review tonight 
> was that it would be more cumbersome for our members to 
> utilize than if all the 'rules' are in a singe document.  
> Some people seemed to support creation of the new document 
> and some seemed to be against it.  There was only a small 
> cross section of the EC present, so accordingly I'm running 
> this straw poll to see how people feel.
> 
> Please respond at your first reasonable opportunity.
> 
> Thanks,
> 
> Mat 
> 
> Matthew Sherman, Ph.D. 
> Senior Member Technical Staff
> BAE SYSTEMS, NES
> Office: +1 973.633.6344
> email: matthew.sherman@baesystems.com 
> 
> 
> -----Original Message-----
> From: Grow, Bob [mailto:bob.grow@intel.com]
> Sent: Sunday, July 16, 2006 5:12 PM
> To: Sherman, Matthew J. (US SSA)
> Subject: P&P motions
> 
> Mat:
> 
> From AudCom minutes:
> 
>         AI - Bring this to the SASB as a motion to make this 
> a part of the rules Move that the IEEE-SA Standards Board 
> include in its procedures (IEEE-SA Standards Board Operations
> Manual) that any Sponsor policy and procedure document 
> accepted by AudCom shall reside in one approved location on 
> the IEEE Standards website.
> 
> From Stds Board minutes:
> 
>     A motion was made by Daleep Mohla and seconded by Gary 
> Robinson that was amended by Robby Robson and Bill Hopf as follows:
>         
>     Motion - Move that the IEEE-SA Standards Board include 
> the following in the IEEE-SA Standards Board Operations Manual: 
>     The IEEE Standards Sponsor policy and procedure document 
> accepted by AudCom shall be the official policies of that 
> Sponsor and shall reside online on the IEEE-SA Standards 
> Board AudCom website. No other copy shall be designated as 
> the official copy.  Links to the IEEE-SA Standards Board 
> AudCom website are encouraged.
>     Result - 22 approve
> 
> ----------
> This email is sent from the 802 Executive Committee email reflector.
> This list is maintained by Listserv.
> 
> ----------
> This email is sent from the 802 Executive Committee email reflector.
> This list is maintained by Listserv.
> 
> ----------
> This email is sent from the 802 Executive Committee email 
> reflector.  This list is maintained by Listserv.
> 
> ----------
> This email is sent from the 802 Executive Committee email 
> reflector.  This list is maintained by Listserv.
> 

----------
This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.