On Tue, Oct 7, 2008 at 11:52 AM, John Pettitt <[EMAIL PROTECTED]> wrote: > Ryan Malayter wrote: >> Given the errors in all IP geolocation services, wouldn't it make >> sense to allow pool server operators to identify their country (and >> maybe LAT/LONG) alongside their bandwidth? This could be of course >> optional, falling back on the MaxMind/whatever geolocation data if >> operator-supplied location data is not present. >> >> > > I suspect that geographical location is less important than network > location - as somebody pointed out if the delay is symmetrical the > distance doesn't matter that much. It would be interesting to build a > system that just looked looked at routing, specifically AS number to > determine how many different networks a packet has to cross and picked > the lowest (on the theory that it's crossing from one net to another > that introduces asymmetric latencies). > I think that there was already a trial using routing data that didn't work out well. You would often get servers on another continent simply because they were in the same AS as your ISP for example. A combination of routing data and geolocation was mentioned at some point.
A synthetic coordinate system such as that used by OASIS would be a better option. It essentially gives and estimate of RTT between two hosts based on their IP addresses. http://oasis.coralcdn.org/ Of course OASIS is largely experimental, and even after years of operation has not proven stable or scalable (OASIS and the Coral CDN go down very frequently). Akamai has a similar solution that is proprietary. -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
