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/[email protected]/
[atlas] AS number in traceroute data
- Previous message (by thread): [atlas] AS number in traceroute data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iñigo Ortiz de Urbina
inigo at infornografia.net
Mon Apr 29 17:44:34 CEST 2013
On Mon, Apr 29, 2013 at 5:01 PM, Lex van Roon <r3boot at r3blog.nl> wrote: > Hi > Hi, > On 04/29, Robert Kisteleki wrote: >> On 2013.04.26. 12:14, Pavel Veselovskiy wrote: >> > Is it possible to perform RIPE Atlas measurements with a key "-A" that >> > shows the number of autonomous systems? >> > >> No, there's no support for this on the probes. It'd be pretty expensive for >> to do this on the fly, as it involves a lookup (into BGP or IRRs) for >> virtually every packet received. >> >> But it would be possible to annotate the results in some way, when storing >> them or when you access them. Is this something that would be interesting >> for others too? > > Annotations would make sense and it would be interesting to me. Otoh, > this is also something that can be easily implemented on a case-by-case > basis by atlas users in their own scripts when parsing the RIPE atlas probe > results. > I entirely agree. To me, the right place to implement this sort of smarts is on the client side's userland. The new github community repo is a good starting point in that direction. I, for one, would be comfortable using a client* that would perform all the transformations/operations locally after consuming vanilla data straight from the Atlas API. Regards, Iñigo Ortiz de Urbina Cazenave * Ideally, an extensible client, part of a bigger, collaborative framework :-) > gr, Lex > -- > LRO-RIPE | 570DE0BE | 9BF5 922E AF87 8584 E9CA C3AD C508 39A9 570D E0BE
- Previous message (by thread): [atlas] AS number in traceroute data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]