Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline

I would like to point out that on Page 9 of the Time line document (just below Motion 12), the comment states that I objected to be being named as a 2nd to the .18 motion. Please note that .18 Motion above on page 8 does not have my name, and the reason is that .18 Motion slides has since been modified/corrected. The .18 Motion slide presented during the Thursday EC meeting in Berlin showed me as a 2nd.

 

Above is simply a clarification for those who might wonder what was I objecting to?

 

Regards,
Vijay

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Michael Lynch
Sent: Tuesday, April 07, 2015 9:51 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline

 

Paul,

 

Yes, I’ve been following this. I’ll go through the timeline and create a draft motion.

 

EC, I am canceling the 802.18 conference call that was planned for tomorrow. I don’t see a need for it now.

 

Best regards,

 

Mike

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Paul Nikolich
Sent: 7 April, 2015 11:47
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline

 

Mike,

 

Please consider the updated time line document I just posted and all the EC discussion on this matter to date and prepare a draft motion you believe will gain EC approval. Then send the draft motion to EC reflector for review and comment before crafting final motion text and obtain a second.

 

Regards,

 

--Paul

 

------ Original Message ------

From: "Michael Lynch" <MJLynch@mjlallc.com>

Sent: 4/1/2015 12:07:36 PM

Subject: Re: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline

Paul,

During the last portion of the EC closing Apurva and I  did develop a revised motion which was never presented. Do you want that motion to be presented for an EC email ballot? Do you want to review it prior to starting an EC email ballot? In any case I'll need to get back to the laptop that I used in Berlin later today.

BR,

Mike

Sent from my Windows 8.1 Phone

From: Rich Kennedy
Sent: ‎4/‎1/‎2015 10:39
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] 802.11 Regulatory Standing Committee DSRC Tiger Team ad hoc timeline

Paul:

 

One needed clarification. During the 802.18 meeting where the document was edited and then approved, the edited version of 11-15/0347r0 was saved as 18-15/16r0. This is the document 802.18 approved.

 

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: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Paul Nikolich
Sent: Wednesday, April 1, 2015 10: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.

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.