Adrian,
Copying Hyunduk (SG Chair).
As you may recall from the San Antonio meeting I mentioned that the scope of this SG is to determine if a standard could lead to improved coexistence and if so to write a PAR and CSD. The scope
is listed in this document,
https://mentor.ieee.org/802.19/dcn/14/19-14-0084-01-0CUB-decision-on-sg-formation.ppt
Thanks to Ben for pointing out some key points.
The “study” part may not be completed by the March meeting, but should definitely be completed by the July meeting. If the decision is that a standard would be beneficial then a PAR and CSD will
be submitted before the July meeting. If the decision is that a standard would not be beneficial, then a PAR and CSD will not be submitted.
It is my understanding, that it is good that this is a Study Group since we want these types of activities to be duly approved activities. So I think formation of the study group was appropriate.
Regards,
Steve
From: outlook_2cb8745b51aa14eb@outlook.com [mailto:outlook_2cb8745b51aa14eb@outlook.com]
On Behalf Of Benjamin A. Rolfe
Sent: Monday, December 22, 2014 9:09 AM
To: adrian.p.stephens@intel.com; Shellhammer, Steve
Subject: Re: [802SEC] Draft Press Release for Editorial Review
Adrian,
Excellent point, but there is one additional detail that may help. The purpose of a study group includes determining if it is appropriate to initiate a new project, and what sort of project is appropriate. These are (in theory at least) determined and then
a PAR and CSD produced based on what the group determined during the "study". I agree that a SG should be able to come to a conclusion in 6 months.
Thus it seems a reasonable scope of the "study" part to determine if there is an 802 Guide, Recommended Practice or Standard that needs to be produced and if there is likely to be sufficient participation to produce it. I suppose if the answer is "no", but
some other course of action is uncovered that 802 should take, that would be a reasonable outcome also?
Makes sense to me...but I'm just an ordinary WG particpant who occasionally has to whinge at the wireless leadership about finances.
-B
On 12/22/2014 12:15 AM, Stephens, Adrian P wrote:
Hello Steve,
The issue I have with this is that the purpose of an 802 WG’s Study Group is to create a PAR (and CSD). This is not a study group for that purpose, but for a bunch of other admirable purposes.
It is reasonable for a WG’s Study Group to be able to write a PAR and CSD in 6 months, and the IEEE-SA rules mention that figure. I’m not sure it is reasonable for the group this proposes to be limited the
same way. The obvious rejoinder is that I was there and voted to approve the study group, so I should have said my piece then. Nevertheless, I believe we should discuss at the next EC meeting the purpose of this group and determine whether it fits within
the definition of a WG’s study group, or needs to be called (and follow the rules for) something else.
Best Regards,
Adrian P STEPHENS
Tel: +44 (1793) 404825 (office)
Tel: +44 (7920) 084 900 (mobile, UK)
Tel: +1 (408) 2397485 (mobile, USA)
----------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
EC,
At the November Plenary the EC approved formation of the 802.19 study group on Coexistence in Unlicensed Bands (CUB). At the time we had not prepared a press release. We have now done that.
Before running an electronic ballot on this I would like to give the EC a few days to look it over and see if there are any editorial comments on the draft.
Please take a few minutes to look this over and send me any comments you might have. This has already been reviewed and edited by the IEEE staff.
Thanks,
Steve
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.