RIPE Chair Selection - Next Steps
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
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
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
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
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
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
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
Bringing high-quality independent measurements to your network!
Timeline of Reverse DNS Events
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
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.
As a community we know quite well what RIPE is about. People are here for a reason. I am not convinced that we need another meta discussion. Talking about principles we should remind ourselves of those we have had from the very beginning of RIPE: the "RIPE Terms of Reference" https://www.ripe.net/publications/docs/ripe-001. For a document written in 1989 this co-author believes that it holds up pretty well. Even the essence of "a globally interoperable, unfragmented Internet" is there, worded more than 30 years ago as: "RIPE promotes and coordinates interconnection of IP networks within Europe and to other continents." Personally I am happy with these principles even after more than 30 years. They guide us well. Maybe we just need to remind ourselves of these principles from time to time and interpret them in the current context. Should we agree that we need to work on revising our principles, we should start from ripe-001 and word them as much as possible in terms of what we actually *do* .
Deliberate change requires setting goals, working towards them and checking progress. So what diversity goals should we set ourselves. In gender diversity the popular/simplistic goal has been to reflect world population: classical 50/50 or contemporary with more categories. Shane also voices this in the podcast. But is this the right benchmark? Shouldn't we set goals based on the diversity of groups that are closer to our community? I have seen some organisations setting diversity goals based on current ratios: "We will double the percentage of female graduates in five years time." Others base their goals on statistics of a larger population they serve: "We will have double the percentage of female graduates compared with the average of similar programs in Europe." I strongly believe we should set ourselves realistic goals. I also believe that diversity has other parameters than gender and that our efforts on gender diversity should not lead to a loss of other diversity we have already achieved.
Thank you Alexander for the detailed information. Maybe it would be a good idea to develop some recommendations for ISPs outside Russia on how to deal with these developments. Do you think RIPE could and should help to do this?
It is good to hear that the RIRs as institutions organise support for AFRINIC as a fellow institution. My personal thoughts are first and foremost with the AFRINIC staff; they need to pay the bills and sustain their families. I understand that so far AFRINIC has been able to pay salaries. As a community we should stand ready to help the *people* of AFRINIC if that should become necessary. I am aware of a fundraising campaign (https://www.tespok.co.ke/?page_id=14001) and I have personally contributed a small amount. Some AFRICAN friends from the early days suggested that we visibly do something similar as a sister community *if it should become necessary*. Our African friends should know that we stand ready do so if necessary!
Very nice article considering that you have to say 'Do not call us!'. ;-) When using IP addresses to identify the source of abuse it is important to keep in mind the possibility of the source address being 'spoofed'. Especially in denial of service attacks what appears to be the address of the source may in fact be the address of the victim. Designers and implementers of automated processes that use IP addresses should take great care about the semantics of IP addresses too. As an author of RFC1918 I regularly get e-mails from automated tools asking me to stop hacking or attacking someone. The only positive development here is that I have not had a query from an LEA about private IP addresses in the past two years or so.
I cannot resist to point out that the privacy policy on the web site of this initiative says: 'Privacy Policy coming soon'.
“I think it’s a must-have to support presenters and chairs using open standards to stream their content. An open internet is not governed through propriety interfaces.”
Definitely! Any pointers to an open standard solution with similar or even acceptable performance? I am sure the RIPE NCC meeting team is all ears.
Great work. Thanks for sharing including what went wrong! It is really good to hear that we can deliver a stream with <10s delay. I am just curious how much AWS cost per viewer per day. A very rough estimate is fine.
Haris, I do not recall meeting you but that means very little. This was a period of many many things happening at the same time. I have helped many ccTLDs in the late 80s and early 90s. I'll get in touch privately and we will figure it out.
“Looks like I'm missing the requirements for attending enough ripe meetings lately. That rule does hampers the diversity requirements.”
Hoi Jaap, Yes that can be frustrating. However it is one of those rules that we should not change for pragmatic reasons while the process is running. Any eligibility criterum will reduce diversity somehow. I have had a couple of similar comments privately from people I would consider an asset to the NomCom. The ' three out of five meetings' criterium is based on research described in appendix M of ripe-728. It is a good idea to discuss this as part of the community evaluation of this first NomCom process. I plan to point this out in the NomCom report.
Showing 18 comment(s)