This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Atlas F.ROOT ping
- Previous message (by thread): [atlas] Atlas F.ROOT ping
- Next message (by thread): [atlas] Atlas F.ROOT ping
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Gervai
grinapo+ripeatlas at gmail.com
Tue Nov 13 18:09:37 CET 2012
On Tue, Nov 13, 2012 at 4:34 PM, Leo Bicknell <bicknell at ufp.org> wrote: > In a message written on Tue, Nov 13, 2012 at 12:57:22PM +0100, Peter Gervai wrote: >> Atlas helped me today first to see a hard-to-detect bug: F-root >> anycast algo works fine for v4 but fails miserably for v6, as instead >> of AMSterdam it sends all traffic to some remote island in the >> pacific. ;-) > > The good folks at ISC would be quite happy if you opened a ticket > with them on this issue. Drop an e-mail to noc at isc.org to do so, > including traceroutes and such would help a lot. I did. > As you noticed with both F and M, there's always a routing > misconfiguration somewhere for someone. IPv6 is still a little > less mature than IPv4 in that sense. Lots of good people are working > on the problem. We have to watch ipv6 with much more attention since we really have to prevent people saying that it's "worse" than ipv4, especially now that ripe handled our last v4 block ever and no more. Later or possibly sooner the endusers get it, and I mean the END endusers, those gravediggers, spoon-binders and dishwashers. :-) And DNS is the first entry, so I'd prefer working and reachable roots. And Atlas is a great way to assure that. Peter
- Previous message (by thread): [atlas] Atlas F.ROOT ping
- Next message (by thread): [atlas] Atlas F.ROOT ping
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]