It sounds a lot like...
... "DNS for White Space."
It would be cool, though, if they would implement it in a way that was actually similar to (secured) DNS, so that the requesting/querying device didn't need to go directly to a top-tier "root server" to get a list of available White Space channels (frequency ranges).
The additional redundancy created by additional "White Space Spectrum Availability Protocol" (I just made that up) caching servers would go a long way toward ensuring that your node doesn't suddenly find itself lost in the woods without a map, so to speak, if one of the spectrum availability list providers falls over.
The caching servers would be made read-only (from a client perspective, since updates can ONLY be provided by one of the registered White Space database maintenance companies) and multi-homed (i.e., it gets data from a primary provider, then falls back to a list of secondaries if the primary isn't available).
A new record type would be created and implemented in the real DNS protocol that would provide information regarding the address of the nearest WSSAP caching server. A WSSAP-compliant access point would then query a local DNS server, and ask it for the DNS server's preferred WSSAP caching server. The info would be passed by the DNS server back to the device, which would then query the WSSAP server(s) listed in the DNS reply.