On Tue, May 02, 2017 at 03:03:15PM -0400, Lee Howard wrote: > >Do you have a reference for the following statement > >Serving ads: "This host is probably in town.province." An ISP that does > >not > >provide PTR records might affect somebody else's geolocation. > > No. Given the privacy considerations, I¹ve changed the example from > ³x.town.province² to ³string.region² and added privacy considerations. So > I need to fix this text anyway. > > > > > >Extracting geo information from reverse DNS is very hard. As far as I > >know, > >geo location services for IPv4 mostly rely on other sources. > > That¹s probably true. Given that I need to update it to match what it says > in the Privacy Considerations section and the examples, should I just > remove mention of geolocation? Or should I tweak it to match the rest, and > add text saying, ³But reverse DNS is not a great source for geolocation > information²?
For whatever it's worth, I know of one geolocation effort that uses the names in the reverse as clues about geolocation improvement. I am not able to state who it is or how they use this, but I can testify that it is in fact used that way. A -- Andrew Sullivan a...@anvilwalrusden.com _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
