RIPE Chair Selection - Next Steps
• 8 min read
Please find below an update from the RIPE Nominating Committee. Three of the NomCom members answer some of the questions you might have about the next steps in the selection process.
Daniel Karrenberg
Based in Western Europe, NL&DE mostly
36
Articles
30
Likes on articles
Based in Western Europe, NL&DE mostly
>>>>>>>>>>>> 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
Registry Data Quality Assessment – Phase 2
• 7 min read
In order to ensure accurate and up-to-date registration data, the RIPE NCC started to evaluate Registry Data Quality (RDQ) in 2009. The second phase has now been finalised and the results are encouraging.
Analysis of Increased Query Load on Root Name Servers
• 8 min read
After we observed increased query load on the root name severs recently, we did some investigation and analysis which is described in the article below.
RIPEstat Live Demo #1
• 5 min read
This article summarises the first RIPEstat demo session that took place today, 25th January 2011. At the end of the article are the dates of the next demos, and options for providing feedback.
The RIPE NCC and the World IPv6 Day
• 4 min read
The RIPE NCC supports the World IPv6 Day scheduled for 8 June 2011. Read more about plans for the event and the role that the RIPE NCC will play.
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)