| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
> -----Original Message-----
> From:
owner-stds-802-sec@listserv.ieee.org
> [mailto:owner-stds-802-sec@listserv.ieee.org]
On Behalf Of John Lemon
> Sent: Wednesday, December 01, 2004 6:56
PM
> To: STDS-802-SEC@listserv.ieee.org
> Subject: [802SEC]
Attendance Credit At LMSC WG Meetings
>
> More experienced
ones:
>
> I'm seeking some advice on how to handle a claim
of
> attendance at the most recent plenary meeting. One person
>
managed to sign-in for 75% of the half-day sign-in slots for
> 802.17.
However, said person was not actually in attendance
> for more than a few
minutes for some of those periods.
>
> What would you recommend we
do in such a situation?
>
> 1. Strike the sign-ins for the periods
when the person was in
> attendance for only a few minutes, and notify
them of the action?
> 2. Strike the sign-ins for the periods when the
person was in
> attendance for only a few minutes, without notifying them
of
> the action?
> 3. Count this as a learning experience and
institute tighter
> control on the sign-in booklet in the future?
>
4. Other?
>
> If you chose 3, how would you recommend preventing
this abuse
> in the future?
John,
I would recommend 1 and 3. I say 1 vs. 2
because I think the person(s) involved deserve notice. You will need the
concurrence and support of your WG Chair, of course.
The intent, as I
understand it, and have implemented it in 802.18 and intend to implement it in
802.22, is that "attendance at a meeting" means "was present for substantially
all of the meeting period" (yes, people occasionally need to leave the room
temporarily to field phone calls, do "bio-breaks," etc., but the practice of
showing up, signing the book, and then leaving to go elsewhere is, in my
opinion, an abuse).
As far as how to institute tighter control on the sign-in book is concerned, I'm not sure what to suggest. 802.18 has been a small enough group that everyone pretty much knew everyone else and abuse would have been noted fairly easily. In a larger group, it's obviously not so easy. (I will have to give more thought on how to make sure that such abuse does not occur in 802.22 as well, since, with 76 voters and 114 total attendees at the first session, it will be harder to keep track by the "eyeball" method there, too.)
Perhaps someone else on the EC will have some useful suggestions.
Regards,
Carl R. Stevenson
President and Chief Technology Officer
WK3C Wireless LLC
Where wireless is a passion, as well as a profession. SM
———————————————————————————————————
Wireless Standards, Regulatory & Design Consulting Services
4991 Shimerville Road
Emmaus, PA 18049-4955
phone: +1 610 965 8799
cellular: +1 610 841 6180
e-mail: wk3c@wk3c.com
web: http://www.wk3c.com
> Tony, I came in to the 802.1 meeting for our
joint
> 802.1/802.17 meeting just as you were finishing saying
>
something about this to the 802.1 participants. I missed most
> of what
you said. Could you repeat it here?
>
> Thanks,
> John
Lemon
>
> ----------
> This email is sent from the 802
Executive Committee email
> reflector. This list is maintained by
Listserv.
>
>