John:
Interestingly enough, at the last moment, I believe it was after the straw polls were run, two FCC Commissioners, in a joint (Republican and Democratic!) blog, suggested that the DSRC community consider realigning their channels, which would allow the Yucek proposal all it needed to succeed. The DSRC community has since blasted the suggestion. So it is not only us they don’t agree with. Ultimately, this could lead to a new proceeding (or just a ruling) that would open the door to that proposal.
Rich Kennedy
Manager, New Technology Development
MediaTek Inc.
rich.kennedy@mediatek.com
(832) 298-1114
Wi-Fi Alliance Spectrum & Regulatory TG Chair
Wi-Fi Alliance White Spaces TTG Chair
Wi-Fi Alliance White Spaces MTG Vice-chair
IEEE802.11 TGaf (WLAN in White Spaces) Chair
IEEE802.11/15 Regulatory SC Chair
IEEE 802.11/18 Liaison
From: John_DAmbrosia@DELL.com [mailto:John_DAmbrosia@DELL.com]
Sent: Friday, April 3, 2015 8:19 AM
To: rkennedy1000@gmail.com; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: RE: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline
Rich,
Let’s take this in two steps
Step 1 - The IEEE 802.11 portion of the tiger team made two proposals – was there any consensus within the IEEE 802.11 portion of the tiger team on either of these proposals? I suspect not – since there were two proposals.
Step 2 - Neither proposal then garnered consensus within the tiger team, which included individuals from IEEE 802 and DSRC
Do I have this right?
John
John:
The IEEE 802.11 segment of the Tiger Team made two proposals for sharing mechanisms, but this group did not come to consensus on a solution, neither a selection of one of the proposal, nor a compromise proposal. The Tiger Team, with both sides weighing in on the proposals in a series of straw polls (in the removed section 11 of the Tiger Team final report) came to no consensus on anything.
Rich Kennedy
Manager, New Technology Development
MediaTek Inc.
rich.kennedy@mediatek.com
(832) 298-1114
Wi-Fi Alliance Spectrum & Regulatory TG Chair
Wi-Fi Alliance White Spaces TTG Chair
Wi-Fi Alliance White Spaces MTG Vice-chair
IEEE802.11 TGaf (WLAN in White Spaces) Chair
IEEE802.11/15 Regulatory SC Chair
IEEE 802.11/18 Liaison
All,
This wording is somewhat confusing to me.
In the first sentence it states that there is no consensus within IEEE 802. However, bullet 1 indicates individuals from 802 met with DSRC representatives, and this group was unable to reach consensus.
What is not clear to me was there a lack of consensus within 802 or in the tiger team, which consisted of 802 and DSRC representatives.
I am not sure if I am missing something or if this is a wording issue, but it is somewhat confusing.
John
Sent from my Windows Phone
All
From what I have been told, what the EC should approve is as follows:
----------------------------
The IEEE 802 EC would like to state that while IEEE 802 has no
consensus regarding an answer to the question, IEEE 802 would like to
state the following:
1) IEEE 802 participants met in a Tiger Team with DSRC representatives
to discuss the issue.
2) While there was a good exchange of ideas, the group was unable to
reach consensus.
3) IEEE 802 EC would like to report that participants discussed
various issues, as outlined in http://mentor.ieee.org/... but that we
can take no position on the issue before the FCC.
4) IEEE 802 encourages similar discussions and efforts for consensus
in the future regarding regulatory matters.
Thanks
Chair of IEEE 802
----------------------------
I can support sending that letter to the FCC. Anything else would
misrepresent the consensus of IEEE 802 (from what I have been told).
IMHO.
James Gilb
On 04/02/2015 12:34 PM, John Kenney wrote:
> Hi Paul and Adrian,
>
> Thanks for the opportunity to comment on the timeline.
>
> I suggest that for the period Dec. 2014 to March 2015 we add some
> detail concerning the process that produced the Tiger Team final report and
> the Tiger Team online poll.
>
> These documents demonstrate that both the report and the voting results
> were developed through an open and deliberative process. Poll questions
> were edited over several hours of Tiger Team teleconferences in December
> and January. Final report comments were resolved over several hours
> of Tiger Team teleconferences in February and March.
>
> *Date of posting of each revision of draft Tiger Team final report: DCN
> 11-14-1596 (doc)*
> revision 00 posted Dec. 12, 2014
> revision 01 posted Jan. 30, 2015
> revision 02 posted Feb. 20, 2015
> revision 03 posted Mar 06, 2015
> revision 04 posted Mar 09, 2015
>
> *Date of posting of clean Tiger Team final report: DCN 11-15-0347 (pdf)*
> March 09, 2015
>
> *Date of posting of each revision of consolidated comment spreadsheet: DCN
> 11-15-0175 (xls)*
> revision 00 posted Jan. 15, 2015
> revision 01 posted Jan. 29, 2015
> revision 02 posted Feb. 20, 2015
> revision 03 posted Feb. 27, 2015
> revision 04 posted Mar 06, 2015
> revision 05 posted Mar 09, 2015
>
> *Comment resolution teleconference dates (60 to 90 minutes each):*
> Feb. 6, Feb. 20, Feb. 27 and March 6, 2015.
>
> *Tiger Team voting:*
>
> - Straw Poll final questions: posted Jan 30, 2015
>
> https://mentor.ieee.org/802.11/dcn/15/11-15-0240-00-0reg-dsrc-coex-tt-final-report-straw-poll-questions.ppt
>
> - Eligible voter list and Tiger Team attendance: posted Jan. 30, 2015
>
> https://mentor.ieee.org/802.11/dcn/15/11-15-0183-02-0reg-dsrc-coexistence-tt-attendance.xls
>
> - Online Survey Period: Feb. 9 to Feb. 23, 2015
>
> - Overview of results: posted Feb. 27, 2015
>
> https://mentor.ieee.org/802.11/dcn/15/11-15-0288-00-0reg-overview-of-dsrc-coex-tt-straw-poll-results.ppt
>
> - Sorted comments: posted March 8, 2015
>
> https://mentor.ieee.org/802.11/dcn/15/11-15-0352-01-0reg-dsrc-tiger-team-straw-poll-comments-sorted.xlsx
>
> I hope the EC voters find this information useful.
>
> Best Regards,
> John Kenney
>
>
>
>
> On Wed, Apr 1, 2015 at 10:05 AM, Shellhammer, Steve <
> sshellha@qti.qualcomm.com> wrote:
>
>> Paul and Adrian,
>>
>>
>>
>> Here are a few corrections, based on my memory of events.
>>
>>
>>
>> *March 10. 802.11 Regulatory Standing Committee Meeting*
>>
>> The minutes are missing the statement from the chair that he is not going
>> to have the standing committee vote on approval of the Tiger Team Technical
>> Report.
>>
>>
>>
>> *March 11. 802.11 WG minutes*
>>
>> “28.2.20. Chair: This is a procedural motion (50%), as the motion states
>> that the document will go to IEEE 802.18.” is missing the final words of
>> the chair. His statement was actually,
>>
>>
>>
>> “28.2.20. Chair: This is a procedural motion (50%), as the motion states
>> that the document will go to IEEE 802.18, since this will be a technical
>> motion in 802.18 where 75% approval is required.”
>>
>>
>>
>> *March 12. 802.18 Meeting*
>>
>> The minutes are missing that statement from the chair that this is a
>> procedural motion, though several of us in the meeting stated that our
>> opinion that this was a technical motion.
>>
>>
>>
>> Regards,
>>
>> Steve
>>
>>
>>
>> *From:* ***** IEEE 802 Executive Committee List ***** [mailto:
>> STDS-802-SEC@ieee.org] *On Behalf Of *Paul Nikolich
>> *Sent:* Wednesday, April 01, 2015 8:28 AM
>> *To:* STDS-802-SEC@LISTSERV.IEEE.ORG
>> *Subject:* [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team
>> ad hoc timeline
>>
>>
>>
>> Dear EC members,
>>
>>
>>
>> Adrian and I have collaborated on creating a timeline (
>> https://mentor.ieee.org/802-ec/dcn/15/ec-15-0029-00-00EC-dsrc-tiger-team-timeline.docx).
>> The objective of this effort is capture the procedural steps taken by
>> 802 in an easy-to-follow document on how 802 arrived at the current state
>> regarding the completion of the 802.11 Regulatory Standing Committee DSRC
>> Tiger Team ad hoc activities.
>>
>>
>>
>> Please review, correct errors and suggest enhancements. It is important
>> that we have an accurate context in which to make a decision on this
>> pending matter.
>>
>>
>>
>> Regards,
>>
>>
>>
>> --Paul
>>
>> ---------- 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.
---------- 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.