Based in Western Europe, NL&DE mostly
Articles
Likes on articles
>>>>>>>>>>>> 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
• 3 min read
After the DNS root zone was finally signed and a number of TLDs began signing their zones, we were curious to see how many clients actually request DNSSEC information. First we looked at our server that provides secondary service to several ccTLDs.
• 3 min read
Following the first announcement of the active measurement network we are planning to set up, you can find a short description below of the equipment we are planning to use for all vantage points.
• 3 min read
This is the first in a series of articles in which we will describe our plan to set up a new measurement network and how we plan to master the engineering, economic and community-building challenges.
• 2 min read
In the previous article we looked at membership growth over the years. In this article we will see how RIPE NCC Internet number resources are distributed among the membership, as of 1 January 2010.
• 4 min read
With the year 2009 behind us, here is a quick look at some RIPE NCC membership demographics.
• 9 min read
Here are the first results of our DNS transfer size measurements. We are interested to determine any possible problems for users of K-root once it starts giving DNSSEC responses to resolvers that request them. DNSSEC responses are significantly larger than current responses. We are interested to le…
• 3 min read
REX has been supporting queries on IPv6 addresses for a couple of weeks already. Some inquisitive users have already found out.
• 1 min read
There is a lot of interesting stuff here on Labs and there is more to come.
• 2 min read
These are the slides Daniel Karrenberg presented - well tried to present when the laptop broke down - at the Moscow Regional Meeting. The version on offer here includes a few extras that didn't make it to the screen in Moscow.
• 1 min read
Labs is being built. We're almost ready to go. Find out about the early days of RIPE Labs
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)