I would like to see this be described in a more generic way. I agree with Raj that this is all about providing information for more than a point on a map but there are several possible scenarios for which a query for a "polygon" could be requested. It could be a very long thin polygon if the request is related to a road or railroad or a fairly square polygon if the request is for a venue or even a field. While the use case may be a mobile master it could also be for a master that is supporting devices that either roam within the polygon or cannot accurately locate themselves within the polygon.
On TueJan/17/12 Tue Jan 17, 6:17 PM, "[email protected]" <[email protected]> wrote: > >Hi Gabor, > >On 1/12/12 8:26 PM, "ext [email protected]" <[email protected]> >wrote: > >>We did not have any discussion on P.9, so I'd like to get comments on the >>list about this: >> P.9: A master device MUST be able to query the whitespace >> database for channel availability information for a >> specific expected coverage area around its current >> location. > >This requirement addresses the need associated with a white space master >device which is mobile. >The master device may query channel availability for a specific contour or >a set of locations on a certain path for example. >Hence this requirement is primarily about allowing the query to contain >information that goes beyond just a specific lat/long co-ordinate. > >-Raj > >_______________________________________________ >paws mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/paws _______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
