On Thu, Oct 3, 2013 at 1:34 AM, Koos van den Hout <[email protected]> wrote:
> Quoting Ask Bjørn Hansen who wrote on Thu 2013-10-03 at 00:54: > > > You can reference this anecdote next time there's a discussion about why > IPv6 is (still) worse. > > > If this happened with IPv4 all sorts of network engineers would be > fixing it. I'd not be surprised it it's the same in X days. > > You have notified both ends about this anomaly? I did – and the transit provider that seemed to bring the traffic to the wrong end of the world. The only replies I got was variations of "out of our control" (true) and "it's just traversing our backbone" (dubious; looked like some not-smart announcements). Anyway -- my point was that this happens regularly (in my experience) with IPv6 whereas with IPv4 I routinely ignore things like that when it's "in the middle of the internet" and just see it fixed within a reasonable timeframe. Ask -- http://www.ntppool.org/ | http://askask.com/
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
