<div dir="ltr">Agreed upon a comment section, maybe with a historical view such as wikipedia and also add the source probe location (city/country) to the tracelist, so it's faster to see if the second hop is realistic (waiting for the max distance radius based on latency).<div> <br></div><div>I did a few entries in the OpenIPmap, which resulted in some wonderfull screenshots. I think there is a decent start now as most of the routes I now see are 80% completely resolved. Baring in mind that the atlas probes are limited in some parts of the world.</div> <div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 18, 2014 at 1:33 PM, Daniel Karrenberg <span dir="ltr"><<a href="mailto:daniel.karrenberg@ripe.net" target="_blank">daniel.karrenberg@ripe.net</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 18.06.14 12:07 , Robert Kisteleki wrote:<br> ><br> ><br> > In this particular case, it'd be really good if you could tag this "name" as<br> > being wherever it really is. It may be even better to have a means of adding<br> > a comment (like "DNS name looks like X but it's wrong, it's really Y"). I<br> > consider that optional.<br> ><br> <br> </div>I agree. Rather than a separate list we could record this as a special<br> tag. I propose to add 'name error' and 'comment' to the OpenIPMap schema<br> in addition to what we have now.<br> <span class="HOEnZb"><font color="#888888"><br> Daniel<br> </font></span><div class="HOEnZb"><div class="h5"><br> <br> _______________________________________________<br> OpenIPMap mailing list<br> <a href="mailto:OpenIPMap@ripe.net">OpenIPMap@ripe.net</a><br> <a href="https://www.ripe.net/mailman/listinfo/openipmap" target="_blank">https://www.ripe.net/mailman/listinfo/openipmap</a><br> </div></div></blockquote></div><br></div>