Hi Gabor, I would like to point out that, after some reflection, I think that the reporting of the channels since the last query would be redundant if the WSD has to query the database every time it wants to change channel (which would be normal since the list of available channels may have changed in the meantime). In such case, the last channel used would always be a repeat of the ‘’anticipated’’ channel reported at the end of the last query. If the WSD can select a new operating channel at any time amongst the list of available channels without having to query again, then, the number of past channels to be reported may be sizeable since the device could jump between these available channels at a rather rapid rate. Before determining whether reporting this list of past channels is required or not, one would need to determine whether the WSD will always need to query the database every time it wants to change channel or not. If not, a reasonable guess at the maximum number of channels to be accommodated in this list would need to be made and implemented in the messaging protocol. Regards, Gerald
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, 11 May, 2012 14:01 To: [email protected] Subject: Re: [paws] Charter update progress A reporting capability will be included to paws. At minimum, the anticipated usage will be reported in the regulatory domains which require it. What Amer was asking for is have a capability to report (in addition to the above) also the channels used since the last query. As I mentioned, I believe this type of data can be sent to the db together with the anticipated usage, so I do not think this would add any new requirement to the protocol itself, but would need to be supported by the data model. So the question is really if people on this list feel paws should build a capability into the data model to report also usage since last query, in addition to anticipated usage, or not. - Gabor
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
