Hi Xinpeng,
On Sun, Jun 16, 2013 at 7:13 PM, Weixinpeng <[email protected]> wrote: > Hi Vince, **** > > The following statement seems ok to me. And I think a separate > discovery document is needed.**** > > There is a question, when the Database returns an > OUTSIDE_COVERAGE error and includes a list of alternate Databases, how does > database know the alternate databases? > Good question. Presumably, it would depend on business relationships between the databases and trust that the returned database(s) are certified by the application regulator. In a domain that requires the use of a Listing Server, the device must still check the alternate database(s) with the Listing Server. A flow might be: 1. Device is in regulatory domain X (but does not know it), but contacts a Database A in Y 2. Database Y returns OUTSIDE_COVERAGE error, suggesting the use of Database B 3. Device contacts Database B, returning available spectrum and a ruleset that indicates the device is in domain X 4. Device uses its (preconfigured) Listing Server for X to determine whether Database B is valid 5. If so, Device can use the available spectrum returned by B (The device may do any sort of caching it desires to try to start with the "right" database for the next query). -vince
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
