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

[STDS-802-11-CAC] Fwd: [STDS-802-11] Request for motion -- TGbc Telco March 2nd

--- This message came from the IEEE 802.11 Chairs' Advisory Committee Reflector --- Dear Dorothy,

in addition to the motion text / request for a motion, I would like to provide to you and the CAC additional
procedural information on these two motions.

Right now, we cannot approve discussed comment resolutions, which are marked as
“ready for motion” in the next week as — due to the 10-day notice — creating the
motion tab after the telco does not meet the 10-day announcement.

My understanding is that the goal of the 10 day advance notice is that members are not surprised, and
have time to review material. 

The announcement meets this goal as members are made aware of the intend to run a motion
on a well defined topic.

All resolutions subject to be motioned have been reviewed by the entire TGbc group
in a telcos at least one week before the motion is run. Only resolutions which the group indicated
as “ready for motion” are included.

The underlying submissions, which present proposed resolution material, are on mentor well before
being reviewed by the group.

This announcement follows the general procedure as outlined below:


Day X — the “Topic Tab would be empty”. — motion announced. Announcement would include the notice that the tab will be upddated
with resolutions indicated as ”ready for motion” per discussion during the telco on Day X+N

On Day X+N we would discuss submissions presenting comment resolutions in the phone call (joint review of resolution text in the call, mark resolutions as “ready for motion” if people agree

On Day X+N+1  — Updated “Topic Tab” on mentor (give me one day after the telco to import the discussed / agreed resolution text in the data base an populate the tab)
—> announcement on WG reflector, that “Topic Tab” has been updated with resolutions discussed on Day X+n, which the group indicated that are ready for motion.

On Day X+N+1+6 — we have the next telco — run motion to approve the “Topic tab”

So everything motioned would have been
a) reviewed by the group on Day X+N
and
b) people would have time to double check the updated / populated “Topic Tab” to verify
that it contains the resolution text that has been indicated as  “ready for motion”


Best,

Marc



Begin forwarded message:

Subject: [STDS-802-11] Request for motion -- TGbc Telco March 2nd
Date: 15 February 2021 at 12:28:44 CET
Reply-To: Marc Emmelmann <marc.emmelmann@xxxxxx>

--- This message came from the IEEE 802.11 Working Group Reflector ---
Dear Dorothy,

I would like to request approval for the following motions to be run during the March 2nd TGbc telco:

Motion 94:
Move to approve the comment resolution in the tab “2021-02-15 – ready for motion” as contained in 11-20/1985rXXX

Motion 95:
Move to approve the comment resolution in the tab “2021-02-23 – ready for motion” as contained in 11-20/1985rXXX



The corresponding motion tabs will be updated with proposed comment resolutions
a) that were discussed during the Feb 15 and Feb 23 TGbc telco
and
b) that were indicated by the members based on the review to be “ready for motion”
The revision number of 1985 will be amended accordingly.


This announcement gives the 10-day announcement that TGbc would like to run motions
for comments that have been discussed in previous telcos and that were indicated as “ready for motion”.

The corresponding “motion tabs” will be updated based on the discussion during the cited
telcos and will be available on mentor for review before the motion is run.  I will announce any updates
of the motion tabs on the reflector.


Related documents.




Best,

Marc


To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1


To unsubscribe from the STDS-802-11-CAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-CAC&A=1