|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I joined the 802.19.1 teleconference call late, but I heard the last of the presentation and I have reviewed the material. I have not been privy to all of your discussions, but I do have some questions after having reviewed the material.
1. From a practical perspective in the architecture, what is the incentive to implement a system that is within the 802.19.1 scope?
2. Who or what would implement the 802.19.1 scope architecture?
3. Do whitespace participants have a requirement to do any coexistence methodology outside of the Whitespace Database and some scanning?
It appeared to me that the primary incentive might be handover and thought that it might fit within the 802.21 handover scenario and use cases. I have reviewed some of the documents of 802.21 and the closest that comes to even describing 802.21 requirements is the Zuniga document on use cases and requirements that was a draft in 2009 (21-09-0041-03-bcst-broadcast-services-use-cases-and-requirements.doc). It appears that 802.21 activity has been primarily focused on security and physical handover. However, I did find an 802.21 document from May that is at (https://mentor.ieee.org/802.21/dcn/10/21-10-0107-01-0000-thoughts-on-ieee-802-19-1-relation-with-ieee-802-21.ppt ) that exactly makes this point. It has not been presented in 802.19.
I would suggest that you get the presenters of the 10/107r1 document [Antonio de la Oliva (UC3M), Johannes Lessmann (NEC), and Christian Niephaus (FhG)] to present to the 802.19.1 group and seriously consider if there is an audience and consumer of 802.19.1 services.
Success is getting what you want, happiness is liking what you get!