Bob,
The TAGs were created to provide a place for scarce experts to gather to provide advice to IEEE 802. Hence the name Technical Advisory Group. When we needed a forum for forming
cross 802 external positions for regulatory, we morphed a TAG to do that. However since then we have added Standing Committees for other external relationships. A standing committee that helps coordinate the discussion across IEEE 802 but leaves voting on
external communications to the Working Groups is more consistent with the way we handle our other external relationships.
The 802.19 TAG was more internally focused (like the other earlier TAGs) and the 802.24 TAG has a broader focus.
Regards,
Pat
From: Bob Heile [mailto:bheile@ieee.org]
Sent: Wednesday, October 21, 2015 5:47 PM
To: Pat (Patricia) Thaler; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Regulatory Standing Committee
Pat
I am missing something here. A TAG is a group that provides a forum for cross Working Group discussions. Witness 19 (in its early form) and 24 (in its current form for IoT and Smartgrid) in addition to 18. So the plan is to disband a group that provides
a forum for cross Working Group discussions and start a group that provides a forum for cross Working Group discussions. Likewise, establishing a regular schedule for the Standing Committee (SC) during plenaries provides a structure for interaction with WGs.
As an EC SC, the meetings would be open to all participants. That is exactly what we already have now with a published agenda from the current TAGs and whose meeting are open to all 802 attendees. Likewise I get a report out from 18 and 24 at my closing plenary.
I am confused as to why this needed and how it differs from what we have other than in name. And if this structure makes more sense then why are we not disbanding all the TAGs and replacing them with SCs.. Like I said at the outset, I feel like I missing something
to make sense of this.
Regards
Biob
At 09:18 PM 10/21/2015 +0000, Pat (Patricia) Thaler wrote:
Dear Colleagues,
I took the action item in July to continue the disbanding 802.18 TAG discussion on the reflector.
Having had time to think about this and discuss it with some of you, Id like to propose disbanding 802.18 and forming a Regulatory Standing Committee. This would provide a forum for cross Working Group discussions of regulatory matters to coordinate Working
Group interaction with regulatory organizations. It would be consistent with the way we handle other external relationships (e.g. standing committees for IETF and ISO).
Establishing a regular schedule for the Standing Committee (SC) during plenaries provides a structure for interaction with WGs. As an EC SC, the meetings would be open to all participants.
Monday: The Regulatory SC Chair would prepare a list of items to address for an opening report on Monday and be available to attend opening plenaries of WGs to raise any issues.
Tuesday: The Standing Committee would meet in the AM1 slot to discuss any issues and plan for the week. AM2 and PM1 could be used if further time is needed to focus on specific topics.
Wednesday: No formal meetings time to work on drafting documents based on the input from the Tuesday meeting(s)
Thursday morning: Meet in AM1 to complete editing.
Thursday PM and Friday AM: Regulatory SC Chair attends WG closing sessions to report on activity during the week and make motions on outgoing documents
Friday PM: Regulatory SC Chair reports at the closing EC meeting and EC votes on outgoing IEEE 802 regulatory communications.
Regards,
Pat
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
Bob Heile, Ph.D
Director of Standards, Wi-SUN Alliance
Chair, IEEE 802.15 Working Group on Wireless Specialty Networks
Chair IEEE 2030.5 Working Group for Smart Energy Profile 2
Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications
11 Robert Toner Blvd, Suite 5-301
North Attleboro, MA 02763 USA
Mobile: +1-781-929-4832
email: bheile@ieee.org
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.