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] Selecting only anchors for UDM
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Selecting only anchors for UDM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Thu Jun 12 00:59:08 CEST 2014
On Jun 11, 2014, at 11:39 AM, Klaus Darilion <klaus.mailinglists at pernau.at> wrote: > Am 11.06.2014 15:44, schrieb Daniel Karrenberg: >> On 11.06.14 14:54 , Stephane Bortzmeyer wrote: >>> On Wed, Jun 11, 2014 at 01:16:21PM +0200, >>> Antoin Verschuren <ripe at antoin.nl> wrote >>> a message of 18 lines which said: >>> >>>> some tags like anchor or hasipv6 could be filled automagicaly. >>> For "hasipv6", it is more complicated than it seems >>> >> Hence IPV6WORKS. ;-) > Actually I never would want to make any IPv6 test from a probe which does not have the IPV6WORKS tag. Thus, probes which are known to knot work, should never be selected for measurements. I “generally” agree with this. “IPv6-works” is defined as can contact greater than 50% of atlas anchors. (I’m surprised at how little traffic my anchors see). - Jared
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Selecting only anchors for UDM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]