New contributions
comments
Introducing ENISA: Securing European Networks
ENISA, the European Union Agency for Network & Information Security, is an independent body of expertise, set up by the European Union, to secure Europe’s information society. It was founded in 2004 to facilitate the exchange of information between EU institutions, the public and the private sector. The goal is to work together with operational communities to identify pragmatic solutions to current security issues. In this first article, we have asked ENISA to introduce themselves and highlight some of their activities that could be of interest to the RIPE community.
comment
Today's Mobile Internet
It has been observed that the most profound technologies are those that disappear. They weave themselves into the fabric of everyday life until they are indistinguishable from it, and are notable only by their absence.
comments
Tracebox, a Tool to Detect Middleboxes
The increasing number of middleboxes (such as firewalls, NATs, proxies, or Deep Packet Inspection) has raised concerns over the impact of such middleboxes on the network and the possibility to innovate. As a result, operators and researchers are studying the distribution and behaviour of middleboxes in large networks. In this article, we will describe a tool called Tracebox that helps in detecting middleboxes. Tracebox was developed at the Université Catholique de Louvain (UCL) and at university of Liège (ULg) in 2013 and funded by Change (INFSO-ICT-257422), mPlane (ICT-318627), and Bestcom IAP. We believe that adding tracebox-like capabilities to RIPE Atlas could give network operators a deeper insight into their systems and help debugging network problems.
comments
Stopping Support for Internet Explorer 8 on Windows XP in RIPE Atlas and RIPEstat
Microsoft ended support for Windows XP as of April 2014. We're about to change RIPE Atlas and RIPEstat to stop support for Internet Explorer 8 running on these systems.
comments
RIPE NCC Membership - Developments After Reaching the Last /8
On 14 September 2012, the RIPE NCC started allocating IPv4 addresses based on the last /8 policy. With more than two years passed, we look at the effects this had on membership numbers and demographics. We also look at what the last /8 policy meant for IPv6 uptake.
comments
NTP Measurements with RIPE Atlas
This article describes how RIPE Atlas probes and anchors maintain their clocks, and how accurate these clocks are. We also plan to make the NTP measurements we describe here available as an additional measurement type for RIPE Atlas users.
comments
Redesigning the RIPE NCC Website: Search Improvements
This article is one in a series that explains the main changes we're making to the RIPE NCC website as part of the website redesign project. Here, we take a look at the ways in which we've already improved the search functionality on www.ripe.net, as well as additional improvements that will come into effect when the redesigned site launches in a few weeks' time.
comments
Internet Interconnection: Networking in Uncertain Terrain
The Internet today consists of more than 49,000 networks. Network interconnection is the Internet’s central feature. Yet, there is little qualitative research on the junctions between networks – about why networks interconnect where they do, or about how network engineers create, maintain or shut down relationships with other networks. Given our current dependence on the Internet, this lack of exploration comes as a surprise.
comments
Visualising Network Outages With RIPE Atlas
This article shows some prototypes of visualising network outages with RIPE Atlas using CartoDB.
comments
Deprecating the "changed:" Attribute in the RIPE Database
The RIPE Database Working Group requested the RIPE NCC to replace the “changed:” attribute in the RIPE Database with “created:” and “last-modified:”. Following discussions at RIPE 69, the RIPE NCC has met with the working group chairs and finalised an implementation plan consisting of three phases: 1) introduce the new attributes “created:” and “last-modified:”, 2) make the "changed:" attribute optional, 3) deprecate the "changed:" attribute. Please find the details in this article.
