On 26 Jul 2013, at 13:52, "Harasty, Daniel J" <[email protected]<mailto:[email protected]>> wrote:
Ray: I’m less familiar with the UK use cases. Is this the case you are contemplating?: 1. Device requests AVAIL_SPECTRUM_REQ 2. Database sends AVAIL_SPECTRUM_RESP with a list of available channels and max power values 3. Device picks one that is either not available, or picks a power that exceeds the limit on an available channel 4. Device reports its [non-conforming] selection via the [optional] SPECTRUM_USE_NOTIFY 5. Database “rejects” that notification 6. Device stops transmitting on the frequency it selected due to the “rejection” If the Device is willing to conform to the “rejection”, why did it pick – and report – a non-conforming value to start with? Well, quite :) In theory of course a device shouldn't do that, but this is in effect the OFCOM requirement. I'll suggest to the OFCOM folks that the SPECTRUM_USE_NOTIFY should become "informational only", and not require any positive action other than logging those values. kind regards, Ray
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
