[OpenIPMap] A long-overdue update on the status of openipmap

• Previous message: [OpenIPMap] A long-overdue update on the status of openipmap
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sebastian,

Thanks for suggestions, some quick comments inline.

> I think the RTT features are at this point the most helpfull
> because they improve the output accuracy. Other features such as
> visual representation are things others could change for their
> purpose. The RTT features can also be gradually build-in in terms
> of complexity.
> 
> If you do not take the first and last hop into account, then you
> are basically left with 'public' router locations. These cities are
> saved into the system, doing a count on them gives them a value
> that could be taken into account with the suggestions: "well known
> router locations / internet exchanges". If the lookup for a hop is
> not for the first/last one of the traceroute then the min-latency
> and the lat/long of the previous hop should give a radius where the
> current hop should be in.

Doing this hop-to-hop is tricky (variability adds up, and packets to
hop N, are far from guaranteed to traverse hop N-1 you see in the
traceroute, nor is the return path guaranteed to have the same
latency), but we can certainly do this as RTT from the source as you
suggest below.

> 
> Then check the known routerlocations and "popularity" for
> suggestions. If none are found, do the PTR name based suggestion.
> 
> This could be improved, if the certainty of the next hop is high,
> that radius could be used to limit the currents hop possible
> locations, but that is for later I think.
> 
> Also taking into account that traces of RIPE atlas have a known
> starting point and traces to a RIPE probe have a known end-point
> aswell. Not usefull for 3rd parties that use OpenIPmap but for the
> RIPE sources it will help improving the data.
> 
> When this is a public service, this could be abused or mis-used and
> polute the data. This is more a security issue, anonymous lookups
> might not be allowed to change router locations and registered
> users are logged to the system making it traceable. Maybe some sort
> of reputation system could also prevent a low reputation from
> overiding a location set by a (very) high reputation, option left
> is then to send a suggestion.

Anonymous updates are already not allowed. The version of OpenIPMap
running on marmot.ripe.net does authenticate against RIPE Access, so
we do only have logged in users, every insertion in the database has a
userID associated with it, so doing reputation-things would certainly
be possible if the situation called for that.

OpenIPMap is going to be a bit more exposed soon as RIPE Atlas
traceroute results are going to have an 'openipmap' tab.

cheers,
Emile
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUTSeTAAoJEKxthF6wloMOcSEP/0gsHNMhi5ls+ACJMvL29M9e
XdE80ao4gzoArZgU+YXhNuPbt0cZ857V7Ljr49bmeDxwlGl/fKcnI7RnjZXlsjLe
08V/XNQEudZ/mTKBEGafM96G3zjfuUZZNZIrOU1skDqxEIzOOAtv3RAdzZuq2efT
nVBWMGfXakWKXmrR7CL/JA7fwnQqeIPRSJNGiDL4LFB3Bmf7eJyx7c23Pd8BJjie
mxodTrU5sG3Vq//EkrzV/W3rO9bg1ZI68/Qp1mvAxRLo4J62K+OOddonpEkM2wPu
xyzRLI/rxasJXsqignudebnviPImrwf692JCr/wdO/jFQlQIUlVN3MaegI5jwSVY
9Gj3J3uMqCkRJW3c8ZzHUqLS4Ue9obZDQJjV4zLqfa0JuXJj1ULrXGi0IUuQNEZC
W8QywXAVXwAETfB2+ALCwIlCUcyXw5dahGL373eb/P/AJbfIn7s4WjRqIcKLMVOi
5uRbzp3g3L/fZY89L/YcTJHZcIdcgrX5cen5eXnCPw8zDvwzSead+FMkSbuh+SoC
KsIgYsqXM/hbpLynEqSL7FdInYWpBs6fwPVksxxr+1QttAlL6/wz8pXW0pbF+FOA
JhNypMNvm5S0b0Ap8/y9CoyJSAo3sCnnTaFg9o90X07ZeHIl7Nq8L+HWLKUNH/yO
XOROdC1rHtQk9xqgL//b
=MqK/
-----END PGP SIGNATURE-----

• Previous message: [OpenIPMap] A long-overdue update on the status of openipmap
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]