You are here: Home > Publications > RIPE Labs > Daniel Karrenberg

Daniel Karrenberg

Location: Western Europe, NL&DE mostly

Daniel Karrenberg is chief scientist at the RIPE NCC, the regional Internet registry for Europe and surrounding areas. He advises on research, creation and piloting of new services as well as general strategy development. A computer scientist by training, Daniel likes to invent, design and implement Internet related systems, especially those collecting and processing data about the Internet itself. He also likes to occasionally inject physics, engineering and "networking style" into debates about Internet governance. ------------ Daniel maintains his public bio on linkedin. ------------ 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 / 2000s: dnsmon nsd ris internet+society rssac / 2010s: ripe+labs ripestat ripe+atlas

Pages created by Daniel Karrenberg

There is Gold in this Stream - Sifting Through Used RIPE Atlas Traceroute Results
There is Gold in this Stream - Sifting Through Used RIPE Atlas Traceroute Results
Daniel Karrenberg — 20 May 2016

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 great potential for studying the packet layer of the Internet in general and for providing tools to network operators in particular. All this suggests a large and diverse potential for further work.

Conclusions Drawn from Reverse DNS Event
Daniel Karrenberg — 21 Dec 2012

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 decrease the likelihood of this happening in the future.

1...5 of 35