[db-wg] NOC / Lookinglass Information in the RIPE DB

[Jeroen Massar <]

Hi,

I am probably approaching this from the wrong way, in that case point me
at the right way so that I can do it in the correct way. It needs
discussion first anyway, so here we go:


RIPE currently has a couple of projects going on which help in solving
network connectivity issues, amongst those of course the really nice RIS
tool (I love BGPPlay btw :) and the debogon projects.

The latter project can be used by a network admin to check if that, to
be debogonized network, is reachable.

This does not help with network problems that might occur at other places.

Now what if we could have an object in the RIPE registry that would
explain us where to find Looking Glasses that are applicable for a
prefix? I am thinking of something in the area of the following:

route:        192.0.2.0/24
descr:        Documentation Network
origin:       AS23456
lookingglass: http://noc.as23456.net/lg/
reachable:    icmp:192.0.2.1
reachable:    http://192.0.2.1
mnt-by:       RIR-MNT
source:       RIPE # Filtered

One could debate that maybe putting the proposed 'lookingglass' and
'reachable' addresses might be better suited in the ASN object.
Another option to store this data would be to create a new 'noc' object
and to have the details in there.

The above information, when available, could then easily allow operators
who have a problem with a certain prefix to find the lookingglass which
allows them to look at the problem from the remote angle, without having
to contact that NOC. This will give people with network problems a
better insight, which allows for better reporting of the issue, and thus
hopefully faster resolution of issues.

There are indeed resources (eg www.traceroute.org) which list these
items, but it is much more scalable and reliable to have it in the RIPE
registry.

What do folks think about this? Useless? Useful? Nonsense? ??? :)

Greets,
 Jeroen

Attachment: signature.asc
Description: OpenPGP digital signature