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

Re: [802SEC] Item for potential rules change



Pat,

Please note the language (under both attaining and retaining) that says "one of which was an 802.16 LMSC Plenary Session."

Roger


Roger B. Marks <roger@consensii.com>
Consensii LLC <http://consensii.com>

On 2013/03/22, at 01:01 PM, Pat Thaler wrote:

Rogers wording would be a significant change in our current requirements. By our current requirements, one of the two qualifying meetings has to be a plenary session. The 802.16 text allows both meetings to be interims. I’d be against making that change.
 
Pat
 
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Tony Jeffree
Sent: Tuesday, February 05, 2013 11:49 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Item for potential rules change
 
Roger -
 
Your wording looks pretty watertight.

Regards,
Tony

 

On 5 February 2013 19:43, Roger Marks <r.b.marks@ieee.org> wrote:
Yes, I agree with Tony.
 
802.16 specifies this by splitting the concept into separate sentences. In summary:
 
Membership is granted at each 802.16 LMSC Plenary Session to the Potential Members who are registered and in attendance. 
 
A Potential Member is a nonmember who has participated in at least two recent 802.16 Sessions, one of which was an 802.16 LMSC Plenary Session.
 
Following each 802.16 LMSC Plenary Session, membership is retained only by those who have participated in at least two recent 802.16 Sessions, one of which was an 802.16 LMSC Plenary Session.
 
recent 802.16 Session is one of the four most recent 802.16 LMSC Plenary Sessions or another 802.16 Session that took place since the first of those.
 
I think that language like this could be used in the IEEE 802 WG P&P.
 
Roger
 
 
On 2013/02/05, at 12:27 PM, Tony Jeffree wrote:


James -
 
The rule I have applied in .1 is that you can only substitute an interim that falls within the span of the last 4 Plenaries.
 
As currently worded, it would seem that any interim in the history of 802 would apply; note that the current wording doesn't even insist that it be a WG or TG session of the WG that you are attempting to gain membership of either.

Regards,
Tony

 

On 5 February 2013 18:48, James P. K. Gilb <gilb@ieee.org> wrote:
All

In an 802.11 meeting, a question came up regarding the following text in the IEEE 802 WG P&P:

"7.2.2.Retention

Membership is retained by participating in at least two of the last four plenary sessions. One duly constituted interim WG or task group session may be substituted for one of the two plenary sessions."

So it is clear that there is a time of 2 of the last 4 plenary sessions.  However, a "duly constituted interim WG or task group session" does not have a specified time.  (BTW: same text is in the wording for gaining voting rights).

So, for example:

03/13 - Plenary
01/13 - Interim
11/12 - Plenary
09/12 - Interim
07/12 - Plenary
05/12 - Interim
03/12 - Plenary
01/12 - Interim
...
09/10 - Interim

So, at the end of 03/13, a Chair looks at the voters attendance.
Last 4 plenary sessions: 03/13, 11/12, 07/12, 03/12.

Now, what are the interim sessions that could count?  For sure, we would say that the following count: 01/13, 09/12, 05/12.

But, according to the rules, could 01/12 count?  What about 09/10?  The wording in the rules does not say when the "duly constituted interim WG or task group session" is required to occur.

My intention is to craft text 30 days in advance to change the IEEE 802 WG P&P rules in two places, 7.2.1 Establishment and 7.2.2 Retention to clarify which "duly constituted interim WG or task group session" may be substituted.

James Gilb

PS: The relevant wording in 7.2.1 Establishment is:

"... membership in a WG is established by achieving participation credit at the sessions of the WG for two out of the last four plenary sessions; one duly constituted interim WG or Task Group session may be substituted for one of the two plenary sessions required to establish membership."

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

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