RIPE NCC Measurements for World IPv6 Day
As announced earlier, the RIPE NCC is going to measure World IPv6 Day. This article details the measurements we intend to do.
Based in Amsterdam, NL
Likes on articles
I'm a system architect/research coordinator at the RIPE NCC, where I work in the science group. I'm a chemist by training, but have been working since 1998 on Internet related things, as a sysadmin, security consultant, web developer and researcher. I am interested in technology changes (like IPv6 deployment), Internet measurement, data analysis, data visualisation, sustainability and security. I'd like to bring research and operations closer together, ie. do research that is operationally relevant. When I'm not working I like to make music (electric guitar, bass and drums), do sports (swimming, (inline) skating, bouldering, soccer), and try to be a good parent.
BGP routing table growth is one of the major Internet scaling issues, and prefix deaggregation is thought to be a major contributor to table growth. In this work we quantify the fragmentation of the routing table by the type of IP prefix. We observe that the proportion of deaggregated prefixes has …
Please find below the third part of our technical services update. This time we're focusing on our research activities and a number of tools we are developing.
This post provides an update on our IPv6 RIPEness project, including an analysis of IPv6 RIPEness for new Local Internet Registries (LIRs).
Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception!
In this article, we give one example of the possible communities that are now easier to build around RIPE Atlas probes. With the tagging of similar probes, existing communities can use additional tools for creating and analysing RIPE Atlas measurements, such as "IXP Country Jedi", to create their o…
We look into why dynamic addresses change and find ISPs that renumber periodically, most commonly every 24 hours or a multiple of 24 hours. We also find that outages influence address changes.
This article is intended to make RIPE Atlas users aware of ethical issues that could arise when using RIPE Atlas. We do not intend to propose any new formal processes or procedures to address the relevant ethical issues, but we do want to encourage members of the RIPE Atlas community to consider th…
We used a number of RIPE NCC tools and data sets to take a quick look at the recent DDoS attack on Dyn’s infrastructure. We wanted to see if this could be found in the data produced by the RIPE Atlas community.
The issue of the relative sizes of the IPv4 and IPv6 Internet in BGP came up during discussion at the APNIC/APRICOT meeting held in Auckland, New Zealand earlier this year.
Detecting network disruptions is a recurring problem. Clearly locating performance degradation is an important step in debugging and subsequently fixing connectivity issues.
“@emileaben Rather than standardizing human-readable output format, why not emitting a standard structured format, separating the network part (traceroute) and the visualisation part (a tool using the structured output format). Such a format already exists, in RFC 5388. I let you do the same in JSON :-)”
thanks for the interest in the topic Stephane. You hit the nail on the head, the main idea was to standardise a structured format for traceroute. I notice a lack of enthusiasm for RFC5388, probably due to it's verbosity. quick test shows that gzip compression of RFC5388-style results would need 3x more storage relative to plain-text traceroute results. But the RFC is likely very useful to see if we cover all bases in a slimmer structured output format.
One other activity that may be worth mentioning here: We organised a get-together for traceroute implementers. As many traceroute implementations do things slightly different, a bit more coordination can help in making things more consistent, for instance in output formats.
“I'm trying to work with the ixp-jedi tool. In this step: ## measure.py This script runs one-off measurements for the probes specified in _probeset.json_ and stores their results in _measurementset.json_ This uses the RIPE Atlas measurement API for measurement creation, And it needs a valid measurement creation API key in ~ / .atlas / auth When trying to execute the script ./measure.py I get the following and I do not know how to solve it. Authentication file /root/.atlas/auth not found Please, I need your help.”
hi, thanks for trying to use the tool. i hope the docs on github are clear enough: https://github.com/emileaben/ixp-country-jedi/#measurepy --- This script runs one-off measurements for the probes specified in probeset.json and stores their results in measurementset.json This uses the RIPE Atlas measurement API for measurement creation, and it needs a valid measurement creation API key in ~/.atlas/auth . For more information on RIPE Atlas API keys see https://atlas.ripe.net/docs/keys/ --- if not let me know how to improve that. if you are interested in country-level monthy runs. these are available at: http://sg-pub.ripe.net/emile/ixp-country-jedi/history/
“Hi, Is there a way to download multiple days dataset without having to do them individually? Also do you have any API's which will permit me to download the datasets using wget?”
Hi Meenakshi, I think you'll have to download the files individually. I think, if your RIPE Access account doesn't have 2 factor authentication, you can use wget to download the files with the --user and --password options.
While we were busy pushing this post out, it looks like the Gambian Internet was restored, roughly around 12h UTC on 2 December. RIPE Atlas probes came online again, and we see 6 out of 7 ASNs in RIS data again.
Showing 15 comment(s)