Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Mariana,
Then I suggest that on the next conference call we solicit feedback from the interested parties on how much time to schedule for such a meeting. The next call is May 31 so we can discuss it then.
Regards, Steve
From: Mariana
Goldhamer [mailto:marianna.goldhammer@alvarion.com]
Hi Steve,
I appreciate your initiative on organizing these slots.
Regarding the scheduled time, we should probably determine first the Agenda and who offers in providing contributions. Our group will have a busy meeting (I have asked for all the available slots during the July meeting), so I am a little concerned in allocating 4 hours, which may be more than needed for the 11y-16h-19 common meeting.
Regards,
Mariana
From: Shellhammer,
Steve [mailto:sshellha@qualcomm.com]
All,
The IEEE 802.19 TAG will schedule two two-hour time slots on Wednesday afternoon from 1:30 to 6:00 PM at the July IEEE Plenary in San Francisco. Those two time slots will be dedicated to presentations and discussions on coexistence of 11y and 16h.
I have already spoken to Peter Ecclesine and that time does not conflict with the planned 802.11y schedule.
Marianna, I would request that you schedule your 802.16h task group meetings in July so as to not conflict with these meetings, so that members of 802.16h who are interested in attending these meetings will be able to attend without missing an 802.16h meeting. Please confirm that this works for you.
I am assuming that four hours is sufficient for this topic. If however, others think we need more time please say so.
Regards, Steve
************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(190). ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42). ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(43). ************************************************************************************ |