[ipv6-hackathon] Combining TraceMON & project proposal 5a at ipv6-hackathon?

I have found a bug:

sds at stkilda:~$ curl 
'http://[2001:648:2ffc:1225:a800:1ff:fe7d:b4c1]:8000/jedi/api/data/results/country/GR/date/2017-10-01/src_asn/3329/dest_asn/6867/ipv/4'
curl: (7) Failed to connect to 2001:648:2ffc:1225:a800:1ff:fe7d:b4c1 
port 8000: Connection refused



On 03/11/2017 15:46, Gigis Petros wrote:
> Hi all,
>
>> On Nov 3, 2017, at 10:19 AM, Emile Aben <emile.aben at ripe.net 
>> <mailto:emile.aben at ripe.net>> wrote:
>>
>> On 03/11/2017 08:54, Vesna Manojlovic wrote:
>>> Hi,
>>>
>>> while reviewing projects with Pedro, we thought that this might be
>>> possible to combine with some of the already existing features in 
>>> TraceMON:
>>>
>>>> 5a. Comparing IPv4 and IPv6 traceroute paths
>>>> by Petros Gigis
>>>>
>>>> Create a visualization to compare IPv4 and IPv6 traceroute paths, 
>>>> highlighting the differences between these paths. For example, it 
>>>> would be interesting to observe differences in IP-level/AS-level 
>>>> paths in terms of traffic locality; e.g., IPv4 paths from ASX to 
>>>> ASY staying inside a country while IPv6 paths are leaving it. 
>>>> Moreover, this visualization would help the network operators and 
>>>> the academic community understand the differences in IPv4 vs. IPv6 
>>>> routing, on the data plane. Furthermore, some kind of statistics 
>>>> could be created based on the visualization (similar to the Eyeball 
>>>> Jedi approach (sg-pub.ripe.net/petros/eyeball-jedi 
>>>> <http://sg-pub.ripe.net/petros/eyeball-jedi>) to compare country 
>>>> ecosystems at a larger scale. Finally, comparing the IPv4 ASN of 
>>>> the endpoint probes (as given by the RIPE Atlas platform) with 
>>>> their IPv6 ASNs, would potentially reveal native IPv6 support on 
>>>> the AS vs. support from IPv6 providers.
>>>
>>> Massimo & Emile, could you care to comment?
>>
>> we looked into integrating traceMon into ixp-country-jedi for an earlier
>> code-sprint, and didn't get it to work then.
>>
>> it would be great if stuff that gets developed would work for the use
>> case of a mesh of traceroutes (like ixp-country-jedi), and would be
>> integratable into an interface like ixp-country-jedi  (see
>> https://ripe.net/ixp-country-jedi )
>>
>> the great benefit would be that you'll get visibility for the viz that
>> was created (people seem to like the ixp-country-jedi, and we do monthly
>> traceroute meshes for countries with enough probes)
>>
>
> Regarding the IXP Country Jedi, I am working on a _prototype_ API that 
> provides
> a 'query-based system’ for all the IXP country Jedi measurement results.
> One of the supported queries is the one that Stephen mentioned earlier
> "give me all traceroute paths from ASX to ASY”.
>
> Moreover, you can define the protocol family (v4/v6), specify a date 
> range and use flags as
> "return only traceroute results that crossed an IXP" or "went out of 
> country”.
>
> example API call: 
> http://83.212.100.80:8000/jedi/api/data/results/country/GR/date/2017-10-01/src_asn/3329/dest_asn/6867/ipv/4
>
> please don’t make aggressive use of the API,
> I am still working on this  :))
>
> Petros
>
>>
>>>
>>> Petros, Steve, Jasper & Pedro,
>>> and aevryone else on site tomorrow, interested in this project - let's
>>> consider TraceMON...
>>>
>>> https://labs.ripe.net/Members/massimo_candela/tracemon-traceroute-visualisation-network-debugging-tool
>>>
>>> https://github.com/RIPE-NCC/tracemon
>>>
>>> Thanks,
>>> Vesna
>>>
>>
>>
>> _______________________________________________
>> ipv6-hackathon mailing list
>> ipv6-hackathon at ripe.net <mailto:ipv6-hackathon at ripe.net>
>> https://lists.ripe.net/mailman/listinfo/ipv6-hackathon
>
>
>
> _______________________________________________
> ipv6-hackathon mailing list
> ipv6-hackathon at ripe.net
> https://lists.ripe.net/mailman/listinfo/ipv6-hackathon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-hackathon/attachments/20171103/d81ab811/attachment.html>