Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Pat,
I think what Geoff is suggesting is a good idea. 802.18 cannot be expected to be aware of all regulatory matters that the WGs feel affect them. A two way exchange of information seems to be a more efficient way of staying up to date. While not every regulatory matter impacts every WG keeping all of the groups up to date seems to be a good idea. Best regards, Mike +1.972.814.4901 Sent from my Windows 8.1 Phone From: Pat (Patricia) Thaler Sent: 1/26/2016 14:34 To: STDS-802-SEC@LISTSERV.IEEE.ORG Subject: Re: [802SEC] Radio Regulatory Mission Statement Discussion Geoff,
My “f’ key was misbehaving. I caught most of them but missed one.
I’m not sure what you want me to add regarding your further suggestion. This is about the TAG Mission, not the WG’s obligations. Bullets c and d under 2 already cover its role coordinating between Working Groups to develop joint positions.
Regards, Pat
From: Geoff Thompson [mailto:thompson@ieee.org]
Pat-
RE: "Drat IEEE 802 Radio Regulatory Mission statement:
Change "Drat" to "Draft"
Further, it sounds as if the internal mission is all communication TO the Working groups. There should also be a mission element of using the group to communicate BETWEEN working groups. That is, part of the mission should be for a WG to notify all other concerned WGs upon which it is taking up work in the hope that work will be coordinated during creation.
Geoff
On Jan 25, 2016, at 12:17 PMPST, Pat (Patricia) Thaler <pthaler@BROADCOM.COM> wrote:
Dear Colleagues,
The draft Radio Regulatory TAG Mission statement is on Mentor in the IEEE 802 EC Docs
This email is to open a discussion of the proposed mission statement to prepare for conducting an email motion to approve the mission statement.
Please respond to this thread with your comments on the mission statement.
Regards, Pat
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
|