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] Reverse traceroute
- Previous message (by thread): [atlas] Reverse traceroute
- Next message (by thread): [atlas] Reverse traceroute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Tue Apr 16 22:18:43 CEST 2024
Hank, On 16/04/2024 19.44, Hank Nussbacher wrote: > https://pulse.internetsociety.org/blog/reverse-traceroutes-help-troubleshoot-improve-visibility-of-internets-health > > "Measure at least one reverse path from 39,544 Autonomous System (AS) > destinations, which host 92.6% of Internet users. As a comparison, RIPE > Atlas vantage points can measure from 4,344 AS destinations, > representing 67.1% of the Internet user base." This particular metric feels highly-contrived... as if to highlight one specific property that their system excels at. Number of ASN doesn't mean that much really... a single vantage point at Comcast would account for 30 million customers and probably twice that many users, but not actually tell you much about the network for the vast majority of those users. It seems like the effort is targeted at operators and not end users, with the selling point is to provide a win-win situation, where operators gain useful metrics and the researchers learn about the network. This would encourage operators to run their code, and the researchers could more easily coax them to run their tool, getting these impressive numbers. (I haven't read the paper of course, because apparently the ACM is not open access and honestly I don't feel like spending $15 for access.) My understanding is that RIPE Atlas is mostly targeted at end users, not operators, so probably a bit harder to get probes placed, as it has no direct benefit for operators... and in fact could reveal details about their network and the quality of their service that they would not care to share. This is not *completely* true, as there are the RIPE Atlas Anchors, which I think are intended to run as infrastructure nodes, but mostly. > Has anyone tried this and indeed found better visibility via their system? I have not. It looks less flexible than Atlas, but also nice and simple! Thanks for pointing it out. Cheers, -- Shane -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3732979CF967B306.asc Type: application/pgp-keys Size: 11519 bytes Desc: OpenPGP public key URL: </ripe/mail/archives/ripe-atlas/attachments/20240416/61ac0d8a/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ripe-atlas/attachments/20240416/61ac0d8a/attachment.sig>
- Previous message (by thread): [atlas] Reverse traceroute
- Next message (by thread): [atlas] Reverse traceroute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]