>>>>>>>>>>>> https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg <<<<<<<<<<<<
Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE; 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net; 2000s: dnsmon nsd ris internet+society rssac; 2010s: ripe+labs ripestat ripe+atlas
RIPE Atlas can now test packet flows from more than 1000 vantage points on the Internet. We took a quick look at anycast traffic to DNS root name servers. There is a lot of interesting signal in this data.
RIPE Atlas has made steady progress in its first year. But we have more ambitious plans. Please read below how we are suggesting to achieve them and why we need your support.
According to address policy, the experimental address allocations for RIPE RIS beacons have to be returned soon. This would mean we have to either discontinue the RIS beacons or request permanent allocations for them according to address policy. We are asking for community support to continue opera…
As part of our effort to make an evolution plan for the RIPE Test Traffic Measurement service, we conducted a survey among TTM hosts. Find below the results and suggested next steps.
The RIPE NCC is working on a toolbox, called RIPEstat, that will make it easier to access the various datasets maintained by the RIPE NCC. This toolbox will be developed in close cooperation with the community. There will be public demo sessions as described in this article.
RIPE Atlas probes are now active on five continents. After the big run on the measurement probes during the recent RIPE Meeting, the deployment is a little slower than expected; but there is a steady stream of probes coming online. We expect to make our initial goal of 300 active probes well before…
This is the next in a series of articles about the new active measurements network, which now has a name: "RIPE Atlas". In this article I will describe the current planning for the pilot. This is also a call for sponsors which will be needed to make the measurement network really big.
After a short service outage, I was interested to find out what happened. Please find below a case study for using public RIPE NCC Tools for this purpose.
In this episode of the RIPE Labs podcast, three Internet pioneers talk about how they helped grow the Internet out of its early infancy, back when its purpose - and much of the excitement around its development - lay in the promise of connecting researchers from around the world.
Our cloud strategy framework provides a starting point that we will use when developing cloud implementations in the future. It also forms a solid basis for discussions with the community on specific proposals relating to our services.
Following the Facebook outage that took place on 4 October, we saw people looking to BGPlay to get a better view of what went on. Here's a look at what the RIPEstat visualisation has to show us about the event in question.
Our draft cloud strategy framework is an attempt to bring everything together in a way that sets out some boundaries, identifies critical elements, and indicates where we need to be strict vs where we can afford to be a little more relaxed. This should hopefully support more clarity regarding how w…
The community’s reaction to our cloud proposal at RIPE 82 was stronger than we expected. We think it’s worth re-starting this discussion, and the first step is to check that we’ve heard you correctly.
At the Internet Governance Forum this week, we signed an MoU with CENTR, the European association of country-code Top Level Domains (ccTLDs). This seemed like a good opportunity to revisit some of the shared history between our two organisations.
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…
During the RIPE 70 Meeting in Amsterdam this week (on 13 May around 10:00 UTC), we experienced a network outage at AMS-IX. Let's see how this was monitored by various tools.
Similar to an experiment done for IPv4 address space, Merit is now performing a darknet experiment with the IPv6 ranges that have been allocated to the RIRs. This also includes prefixes allocated to the RIPE NCC.
They are suggestions, so do not take them as instructions! Especially the defaults I suggested should be subject to discussion and community feedback.
As to keeping the probes visible: I do not think that this is what the typical user wants when they are interested in the topology close to the *target*. In any case what I was interested in when I used traceroutes like that was a simple representation of the topology close to the target, never mind how the packets got close.
Daniel
Suggestions:
a) add an option to limit to h hops from the target and then show paths from all probes providing data during the interval
b) use 'network names' as a label option
c) use AS 'names' as a label option
d) use a colour scale (better visual resolution than greyscale) for the number of paths along an edge
e) add an option to only show endgs used by at least p % of all probes providing data during the interval
f) make h=4 and p=25 the default view
For examples of all that see https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor
Daniel
They are suggestions, so do not take them as instructions! Especially the defaults I suggested should be subject to discussion and community feedback. As to keeping the probes visible: I do not think that this is what the typical user wants when they are interested in the topology close to the *target*. In any case what I was interested in when I used traceroutes like that was a simple representation of the topology close to the target, never mind how the packets got close. Daniel
Suggestions: a) add an option to limit to h hops from the target and then show paths from all probes providing data during the interval b) use 'network names' as a label option c) use AS 'names' as a label option d) use a colour scale (better visual resolution than greyscale) for the number of paths along an edge e) add an option to only show endgs used by at least p % of all probes providing data during the interval f) make h=4 and p=25 the default view For examples of all that see https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor Daniel
Showing 22 comment(s)