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/db-wg@ripe.net/
[db-wg] NOC / Lookinglass Information in the RIPE DB
- Previous message (by thread): [db-wg] NOC / Lookinglass Information in the RIPE DB
- Next message (by thread): [db-wg] NOC / Lookinglass Information in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Wed Mar 28 17:47:04 CEST 2007
Jeroen, On Wed, Mar 28, 2007 at 02:44:43PM +0100, Jeroen Massar wrote: > > 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. I like the "reachable:" idea. It seems like a good debugging tool. But I think the looking glass idea is kind of backwards. Looking glasses know which routes they track, not the other way around, right? -- Shane
- Previous message (by thread): [db-wg] NOC / Lookinglass Information in the RIPE DB
- Next message (by thread): [db-wg] NOC / Lookinglass Information in the RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]