In this article we explain why we will be using Zoom for the upcoming RIPE 80 and RIPE NCC General Meeting, and we outline the policies and settings we have in place to address concerns about privacy and security.
Based in Amsterdam
Likes on articles
About the author
Based in Amsterdam
As Chief Information Officer at the RIPE NCC, I am mainly involved with the planning, operation and development of the RIPE NCC's global information services as well as research and development. This includes the RIPE NCC's authoritative DNS services as well as K-root infrastructure, data collection and measurement networks such as RIPE Atlas and RIS, data provisioning systems such as RIPEstat, and the RIPE NCC's data analysis efforts. I have been with the RIPE NCC since 2008 working in different capacities. Before the RIPE NCC, I worked for more than 12 years in the Internet services and ISP sectors, mostly in senior technical management positions. I was the engineering founder of one of the largest Iranian ISPs and helped several IT startups with their software and business process implementations. I have a M.Sc. in Software Engineering from the University of Oxford, UK and Lean Engineering/Agile Management training at MIT.
Links & Social
Please find below the third part of our technical services update. This time we're focusing on our research activities and a number of tools we are developing.
This is the second part of the technical services update. In this article we're focusing on our DNS services: providing reverse DNS; providing secondary services for ccTLDs; and maintaining K-root.
In 2013 and 2015 we provided high-level reports on the status of our plans for our technical services and tools. It is time for an update. In this first article we will focus on RIPE Atlas.
As the new Chief Information Officer at the RIPE NCC, I’d like to take this opportunity to share with you some of my ideas about the future direction of the technical services we offer to the community. This includes focusing on RIPE Atlas as the RIPE NCC’s data collection system, RIPEstat as the R…
The RIPE NCC proposes improvements to the algorithm used for removing personal data from the bulk provisioning of RIPE Database data.
In addition to the actual data presented in a RIPE Database object, there is additional data, not directly related to the information contained within an object but still valuable from an operational point of view. The RIPE NCC is proposing a method to optionally display this metadata alongside the…
Objects are created in the RIPE Database and are updated regularly by their maintainers. However, at the moment there is no mechanism to see the history of changes to an object. There are many cases where RIPE Databases users want to investigate the history of changes to an object. We would like to…
We’ve been brainstorming on a process to determine the criticality level of our services, and we’d now like to ask the community for input on how we should approach this effort moving forward.
Our cloud strategy framework provides a starting point that we will use when developing cloud implementations in the future. It also forms a solid basis for discussions with the community on specific proposals relating to our services.
Our draft cloud strategy framework is an attempt to bring everything together in a way that sets out some boundaries, identifies critical elements, and indicates where we need to be strict vs where we can afford to be a little more relaxed. This should hopefully support more clarity regarding how w…
The community’s reaction to our cloud proposal at RIPE 82 was stronger than we expected. We think it’s worth re-starting this discussion, and the first step is to check that we’ve heard you correctly.
The good news: RIPE Atlas is growing both in terms of geographical diversity and ASN coverage. What's more, RIPE Atlas is evolving, with a new generation of probe hardware having already passed the test phase and a pilot programme underway to assess the viability of VM anchors. The not so good news…
Showing 7 article(s)