<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-PL" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thanks Randy, Michael, Emile and Romain for your data. I will have to allocate some time to go through it.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I think it’s also useful to understand better my specific needs. I usually do anycast measurements per country and I use all probes from the country (yes, I’m even able to use 1000+ probes from DE). I don’t really care about geographical distribution because after all I use all probes in the country. My point is to see if my work goes in good direction and to catch all routing anomalies. That’s why my only concern is to filter out probes which are:<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <ol style="margin-top:0cm" start="1" type="a"> <li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span lang="EN-US" style="mso-fareast-language:EN-US">Definitely not from this country. I regularly report to RIPE team probes which for example are assigned to DE but in reality they are located in GB. I usually catch them when I see that they are routed to anycast node in another country and don’t see domestic hops in traceroutes. Such probes gets system-geoloc-disputed tag so other users can filter out these probes more easily.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span lang="EN-US" style="mso-fareast-language:EN-US">Definitely duplicates of already existing probes (in the same location, in the same AS like in case of Hostinger). They are example that more data is not always good because they skew cumulative results and lead to over representative of given location and ASN.<o:p></o:p></span></li></ol> <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I hope that data that you shared will help me to make this filtering easier.<o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div> <p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p> </div> <p class="MsoNormal"><span lang="EN-US">Grzegorz</span><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> <p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Romain Fontugne via ripe-atlas <ripe-atlas@ripe.net><br> <b>Reply to: </b>Romain Fontugne <romain@iij.ad.jp><br> <b>Date: </b>Thursday 2022-06-30 at 07:49<br> <b>To: </b>Michael Rabinovich <michael.rabinovich@case.edu>, Randy Bush <randy@psg.com><br> <b>Cc: </b>"Ponikierski, Grzegorz via ripe-atlas" <ripe-atlas@ripe.net>, Nicholas Kernan <nlk39@case.edu>, Emile Aben <emile.aben@ripe.net><br> <b>Subject: </b>Re: [atlas] Overuse of software probes<o:p></o:p></span></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">On 6/29/22 00:23, Michael Rabinovich wrote:<o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div> <p class="MsoNormal">Looking forward to reading Emile’s paper, but in the meantime: Nick <o:p></o:p></p> </div> <div> <p class="MsoNormal">Kernan, a graduate student of mine, wrote a python script for selecting <o:p></o:p></p> </div> <div> <p class="MsoNormal">a geographically diverse set of probes from a list of probes.<o:p></o:p></p> </div> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">The paper describes a similar approach, but using topological distances <o:p></o:p></p> </div> <div> <p class="MsoNormal">(e.g. AS path length, RTT). It is not perfect but more useful than <o:p></o:p></p> </div> <div> <p class="MsoNormal">Atlas' world-wide probe selection.<o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Results are weekly updated here:<o:p></o:p></p> </div> <div> <p class="MsoNormal"><a href="https://ihr.iijlab.net/ihr/en-us/metis/selection">https://ihr.iijlab.net/ihr/en-us/metis/selection</a><o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">We've also extended this approach to find places where deploying new <o:p></o:p></p> </div> <div> <p class="MsoNormal">Atlas probes would add more diversity to Atlas:<o:p></o:p></p> </div> <div> <p class="MsoNormal"><a href="https://ihr.iijlab.net/ihr/en-us/metis/deployment">https://ihr.iijlab.net/ihr/en-us/metis/deployment</a><o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">The paper is now available:<o:p></o:p></p> </div> <div> <p class="MsoNormal"><a href="https://tma.ifip.org/2022/wp-content/uploads/sites/11/2022/06/tma2022-paper18.pdf">https://tma.ifip.org/2022/wp-content/uploads/sites/11/2022/06/tma2022-paper18.pdf</a><o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Thanks,<o:p></o:p></p> </div> <div> <p class="MsoNormal">Romain<o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> </div> </body> </html>