Re: [802SEC] Five day approval process
Carl,
I will consult with the voting members present here in Geneva.
What you are saying, and what your supporters are saying, make it
impossible for 802.18 to function as was proposed for this meeting -
unless it is simply as an observer group unable to do any real work.
That would seem to limit the TAG to complying with the wireless interim
schedule. When will that meeting ever be in Geneva?
There are those here that remember an enabling motion being used so that
a quorum wasn't needed in 802.18 interim meetings. The voting members
will meet to both review collective memory and discuss this tomorrow.
Frankly what you say here doesn't seem to fit the collective memory at
this time.
Regards,
Mike
+1 972 814 4901
-----Original Message-----
From: Carl R. Stevenson [mailto:wk3c@wk3c.com]
Sent: Wednesday, September 21, 2005 18:38
To: Lynch, Michael [RICH1:2H50:EXCH]; STDS-802-SEC@listserv.ieee.org
Subject: RE: [802SEC] Five day approval process
Mike,
We did not previously authorize "doing official business without a
quorum." There were times when we went ahead and drafted documents
during an interim without a quorum present, but they were followed up
with a conf call meeting to do the approval. There were also times when
we had a conf call meeting to deal with work that couldn't be completed
during an interim in order to meet filing deadlines.
There are provisions in the TAG P&P and the TAG section of the 802 P&P
that allow meetings between interims via conference call, with 5 day
minumum notice, but a quorum is still required for those meetings to
take official action.
Also, anything from .18 that's to "go outside" needs 75% approval, with
a quorum present, then must pass the 5 day EC review.
That is the proceedure that was followed during my tenure as Chair of
.18.
I don't believe that it's possible to bypass the quorum requirements of
the 802.18 P&P, let alone the quorum requirements of of the 802 P&P via
a TAG motion.
This is a question of process, not a question of content from my
perspective.
Regards,
Carl
> -----Original Message-----
> From: Michael Lynch [mailto:mjlynch@nortel.com]
> Sent: Wednesday, September 21, 2005 1:18 PM
> To: wk3c@wk3c.com; STDS-802-SEC@listserv.ieee.org
> Subject: RE: [802SEC] Five day approval process
> Importance: High
>
> Carl,
>
> We did as you previously did - we had an enabling motion at the July
> Plenary to allow work in this meeting. All those here felt that was
> sufficient. If that does not satisfy you please advise how this is
> different on how you conducted .18 business at an interim.
>
> The document was approved by all. Our two new participants,
> representing
> Qualcomm, contributed and did not seem to have any issues.
>
> Regards,
>
> Mike
>
>
> -----Original Message-----
> From: Carl R. Stevenson [mailto:wk3c@wk3c.com]
> Sent: Wednesday, September 21, 2005 09:42
> To: Lynch, Michael [RICH1:2H50:EXCH]; STDS-802-SEC@listserv.ieee.org
> Subject: RE: [802SEC] Five day approval process
>
>
> Mike,
>
> Do you have a quorum in Geneva?
>
> If so, was this document approved by 75% of the members, per the P&P?
>
>
> Regards,
> Carl
>
> > -----Original Message-----
> > From: Michael Lynch [mailto:mjlynch@NORTEL.COM]
> > Sent: Monday, September 19, 2005 11:03 AM
> > To: STDS-802-SEC@listserv.ieee.org
> > Subject: [802SEC] Five day approval process
> >
> > Please find enclosed 802.18's comments in response to the European
> > Commission 2.6 GHz consultation. The comment period closes 15
> > September but the membership believes it is beneficial to file a
> > response. This was approved by unanimous consent.
> > I would like to be able to forward this the European
> Commission on 25
> > September.
> >
> > Regards,
> >
> > Mike
> >
> > +1 972 814 4901
> >
> > <<18-05-0033-r0-0000-EC_2.6GHz_Band_Consultation Response.doc>>
> >
> > ----------
> > 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.