[STDS-802-11-TGAY] Additional session and Call for contributions in January interim
Hi all,
As a follow-up of my previous email on January 5, TGay will now have 2
sessions in Irvine:
[1] Tuesday AM1
[2] Thursday AM2
The main agenda items are to start comment assignment and resolve the
comments resulting from our initial SA ballot
Please let Sang and me know if you have any contribution preferably by
the end of Sunday (January 12).
Regards,
Edward
On Sun, Jan 5, 2020 at 3:11 AM Edward Au <edward.ks.au@xxxxxxxxx> wrote:
>
> Hi,
>
> Happy New Year to all! Thanks again for all of your dedicated effort
> and contribution to the task group in the past year.
>
> There are a few reminders as follows:
>
> [1] If you are a voter of the initial SA ballot on P802.11ay Draft
> 5.0, please do remember to cast your vote and submit your comment, if
> any, by 11:59pm ET on January 9 (Friday).
>
> [2] For the January interim in Irvine, CA, in the week of January 15,
> our plan is to start the comment assignment and comment resolution.
>
> [3] As you may refer to the Working Group agenda, there is only one
> session, Tuesday AM2, allocated for our task group. Since the initial
> SA ballot is now scheduled to be closed prior to the interim, I am
> requesting one/two additional sessions on Wednesday and Thursday
> subject to the room availability.
>
> [4] If you plan to present any contribution to the task group in the
> interim, please let Sang and me know as per your earliest convenience.
> Similar to the past few face-to-face sessions, comment resolution
> submission is of the highest priority.
>
> [5] If you plan to finalize your comment resolution document in
> Irvine and ask the task group to consider approval by a motion, please
> do remember the 4-hour rule as per section 3.8 of the IEEE 802.11
> operations manual (14-0629/22). I copy the text of the section below
> for your convenience. If your proposed resolution contains complex
> technical changes to Draft 5.0, I would appreciate if you would upload
> your contribution at least 4 hours prior to your presentation so that
> our members would have sufficient time to review and provide you
> comments if necessary.
>
> "Motions modifying drafts may be made at appropriate times during meetings.
>
> Complex technical changes to a draft shall be in a submission that has
> been accepted by document control according to document formats
> specified in section 3.7 of this document and has been made available
> electronically for a period of not less than four active 802.11 WG
> session hours. The TG chair determines if a technical change is
> sufficiently complex to require a submission.
>
> When a CRC is following the “Accelerated process” for completion of a
> WG letter ballot, and is not meeting during an 802.11 WG session, any
> submission containing changes to the draft shall be on the server and
> announced to the appropriate TG reflector no less than 72 hours before
> any motion is made related to that submission.
>
> NOTE – when a CRC is meeting coincident with an 802.11 session, it is
> subject to the four hour rule described in the previous paragraph."
>
> [6] As per our Working Group Chair's email on December 11
> (http://www.ieee802.org/11/email/stds-802-11/msg04005.html), the
> "accelerated process" as defined in the 802.11 Operations Manual
> applies for our task group. Please read her email in details and let
> us know if you have any question. We would consider technical motions
> approving comment resolution during the teleconference calls,
> providing the authors have uploaded their contributions no less than
> 72 hours to the IEEE mentor (please do refer to the text I copy
> above).
>
> Regards,
> Edward
_______________________________________________________________________________
If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.
Instead, go to http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAY and then press the LEAVE button.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html
_______________________________________________________________________________