In the resource certification system you specify your routing policy via Route Origin Authorization (ROA) objects. One of the options you can set is the ‘Maximum Length’, which specifies the maximum length of an IP address prefix that the AS is authorised to advertise. In this article we will analyse if this feature is being used properly.
We have just released the RIPE NCC Resource Certification Web Validator. It will allow you to validate a Route Origin Authorisation (ROA) file against the RIPE NCC Trust Anchor through a web form, either online or locally.
Since we started providing the certification service on 1 January 2011, many LIRs made use of the service. In this article you can see some graphs showing the number of certificates in place today, as well as certified address space.
In the fall of 2010 SURFnet, the Dutch National Research and Education Network, held a workshop on IPv6. One of the issues that arose was making an IPv6 addressing plan. While this seems a simple subject at first, it turned out to be more complex. SURFnet decided to document best practices and make the results freely available.
Amidst the recent political unrest in the Middle East, researchers have observed significant changes in Internet traffic and connectivity. In this article we tap into a previously unused source of data: unsolicited Internet traffic arriving from Libya. The traffic data we captured shows distinct changes in unsolicited traffic patterns since 17 February 2011.
This article summarises the third RIPEstat demo session that took place today, 22 March 2011. At the end of the article you can find the date of the next demo, and options for providing feedback.
In a previous article we measured that a large percentage of 6to4 connections fail. In this article we show our attempts to find out why these connections fail.
We have redesigned and improved the way we mirror other databases. We now have a method of translating the operational data from other registries (for instance from other Regional Internet Registries or the RADb) into the RIPE Database structure.
In order to ensure accurate and up to date registration data, the RIPE NCC started the Registry Data Quality project in 2009. The article below describes this activity and the problems we found and how we fixed them.
This article, prompted by a panel discussion at the RIPE 61 Meeting, describes the most significant implications of network complexity and suggests ways to deal with it. This is a topic that requires more work and a lot of input from network operators. We hope you’ll work with us to advance this subject.