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
25 Years of the RIPE NCC – The First Hours
• 10 min read
March 1992 - NIKHEF Amsterdam - Main Computer Room: "We have connectivity!" Marten called out. "Running the check script." Daniel responded. The two young engineers were intently looking at their screens, totally oblivious to anything around them: the noise of the air-conditioning fans, the bli…
There is Gold in this Stream - Sifting Through Used RIPE Atlas Traceroute Results
• 15 min read
This work demonstrates the value of the results collected by RIPE Atlas independent of the original purpose for collecting them. Using all traceroute results from a particular day as an example, we first show that near real-time analysis of the result stream is feasible. Then we show that this has …
RIPE Atlas Fun: Map a RIPE Atlas Anchor
• 14 min read
View maps based on RIPE Atlas traceroute measurements. Compare the maps to the ISP's description of their topology. See the potential of RIPE Atlas for mapping the packet layer topology. Learn about experimental tools you can use yourself to explore. Make suggestions for further work.
Conclusions Drawn from Reverse DNS Event
• 3 min read
On Wednesday 13 June 2012, an unknown error caused the removal of several zone files from the configuration of our reverse DNS provisioning system. Following up from the initial report published on RIPE Labs, we further analysed what caused the incident and implemented a number of procedures to dec…
Registration History for Members - A Demo
• 4 min read
RIPE NCC members can browse RIPE database objects with history in RIPEstat for a couple of weeks as a demonstration. Please check it out and let us know what you think.
Root Servers in Member Networks
• 4 min read
In addition to the existing global and local instances of K-root, we propose member instances of K-root. This article describes the benefits and how this will be implemented during the pilot phase.
Introducing RIPE Atlas Anchors - Pilot Phase
• 6 min read
Bringing high-quality independent measurements to your network!
Timeline of Reverse DNS Events
• 8 min read
Last week there were several problems with the RIPE NCC's reverse DNS (rDNS) service. This article is a first report about the events. It is not intended to analyse the causes or make detailed recommendations for action.
IPv4: Business As Usual
• 3 min read
In anticipation of reaching the last /8 of IPv4 addresses in the RIPE NCC service region, we have been looking at the number of IPv4 addresses the RIPE NCC handed out over the last four years. The curves look surprisingly uniform.
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)