Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Pleas also address the comments on how the report is referenced in the motion. It needs to refer to exactly the report that we are going to send.
“with the sections with no consensus within 802.18 removed” doesn’t tell me which sections are going to be removed. Best would be to post a copy of the document as you intend
to send it and reference that version of the doc in the motion. A motion can be split if the two portions of the motion can each stand on their own. It doesn’t seem likely that we would send the report without a cover letter to provide
context for it so it probably shouldn’t be split. The way you have it now, each bullet says Move to approve which sounds like separate motions. If we are approving sending a cover letter and report in one motion, it would
be IEEE 802 LMSC Executive Committee approves sending to the FCC: ·
The cover letter in document <document number> and
·
The DSRC Tiger Team report in document <document number> Regards, Pat From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Michael Lynch Paul, From:
Paul Nikolich Dear EC Members, I updated the DSRC Tiger Team time-line to include reference to the 07FEB2014 letter 802 sent to the FCC Office of Engineering and Technology that provided background and status information
on the Tiger Team activity (https://mentor.ieee.org/802-ec/dcn/15/ec-15-0030-00-00EC-18-14-0007-02-dsrc-status-to-fcc.pdf). The pending FCC communication must be consistent with the 07FEB2014 letter, as it will be a follow up to that communication. I am not aware of any other formal written communication 802 has
had with the FCC on this topic--if there has been, please provide them to me and let the EC know immediately. Mike Lynch, what is the plan to address the Roger's, James' and Steve's comments? It's been almost a month since the closing EC, let's get this item closed. 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.
|