Hello all,
Thanks all for all the POC/TTT volunteering so far.
I wanted to provide some clarifications on the tasks of POCs and TTTs, which should already be clear in the guidelines document (if they are not then will upload a revision that clarifies them).
1) The responsibilities of the POC are those mentioned in the TGbn guidelines (starting from page 5 of
11-24/1682r3) and does not have any particular authority in making technical decisions. The POC and TTT can discuss and incorporate technical concepts in the PDT, which are expected to be reflective of the agreements in the TGbn SFD. The PDT may contain additional details in support of the spec development for a particular topic, which are expected to be developed within the TTT first (benefiting from the TTT expertise to minimize controversial items), and then they need to be brought up to the attention of the task group following our usual procedures (presentation, and so on), and the same applies to the decision making process (documents need to be motioned by the TGbn group for these changes to take effect).
2) POC assignment should be completed for topics that have motions in the TGbn SFD. And for this purpose please rely on the motions that are in the SFD. This applies to the subtopic division as well (i.e., it is fine to divide a topic in subtopic provided that such a subdivision reflects the motions in the SFD). Dividing a topic into subtopic based on technical aspects might not help (especially if not aligned with approved motions in the TGbn SFD).
3) POC assignment for topics that do not have motions in the TGbn but are related to subclauses that are reasonably expected to appear in drafts (e.g., UHR BSS operation) may be done once the TGbn group agrees that the subclause needs to be added (e.g., during the conf call we can have both the discussion on the need of the subclause and assign the POC). Also here, the PDT document, once prepared by the POC/TTT will need to be presented to the TGbn group, and motioned following our usual procedures.
4) POC assignment for topics that do not have motions in the TGbn will be done once there is at least one motion in the TGbn SFD. Until then those entries in the Spec Text Volunteers and Status document (11-24/1698) need to be grayed out. Ross please do so in the next revision of this document. Once the topic has at least one entry then we go to the above bullet 2) for this entry.
Hopefully the above helps on this task and thanks again for your interest and coordination efforts.
Let me know if you have any additional questions.
Regards,
Alfred
-- Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1