> That's interesting, and clever work to solve the problem of making APs into > reliable location references. > > They are doing a more involved/automated version of what I suggested - using > GPS (in their case built-in GPS, plus AP-AP communication) for APs to locate > themselves. Once the AP knows where it is, the clients can find out where > they are in physical (WGS84 coordinate) space using the APs as references. > Note that it's an enterprise solution - definitely not for most homes - since > it requires at least 4, and probably many more suitable APs. > > But LOC records don't have any role in what's described. They *could* be an > output (e.g. an AP could use DNS UPDATE to install LOC records). But there's > still no obviously useful consumer for the LOCs...so why bother? > > If you're in WiFi range of the AP, a client is better off getting precise > information from its broadcast. If not, it's useless. And as previously > noted, LOC for servers suffers from AnyCast, cache, and CDN uncertainty. > > LOC was proposed in simpler times.
Actually, if the AP doesn't have GPS but does offer WiFi Certified Location Service, then it could use its own LOC record to provision itself... -Philip -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
