On Sunday, October 5, 2014 3:58:00 AM UTC-4, Andy Buckingham wrote:
I know my local regulations allow for it - but they do not assign a Pi identification for such usage.
More importantly though, for me, is that I recently started work with iBeacons - low powered 2.4GHz bluetooth signals which carry extremely small amounts of information, a 128bit UUID along with 2 16bit subcode identifiers.
This end result is a process very similar to radiodns, where additional logic must be performed to trigger additional actions. Currently this means that each company must provide their own custom smartphone application to provide that extra logic - when frequently that extra logic is extremely small - displaying a slideshow, or some small amount of html content.
Rather then re-inventing a whole new wheel - it seems to me that RadioDNS already provides the basic level of functionality. If instead of performing a lookup for <frequency>.<pi>.(<gcc>|<country>).
fm.radiodns.org a single application to handle multiple manufacturers could perform a lookup for <minor>.<major>.<uuid>.
ble.radiodns.org and leverage the existing specifications and extend as needed.
But if there is a fixed requirement on having a program identifier in order to do anything, this then would be limited to licensed broadcasters only.
For my OWN application, I am simply running my own dns lookup servers and leveraging the existing radioDNS specification[including some of the upcoming new html content standards] - I can simply use my own domain name instead of relying on radioDNS. I also am adding the FM transmitter from adafruit for some of the beacons to provide specialized functionality for local events[loops of local musicians, as well as providing the ability to notify attendees of keynote events without installing a town wide loudspeaker system]