RIPE Atlas data is now available as a live data stream, opening the door to a host of new applications and use cases. Learn more about how this powerful new functionality can benefit your network.
Last week we improved the security of our routing infrastructure by implementing RPKI (Resource Public Key Infrastructure), a technology that can be used to secure the Internet routing infrastructure. RPKI was the topic of my Master's thesis and in this article I am trying to convince you to use this important technology for a more secure Internet.
We used RIPE Atlas to measure latency times to K-root, and we believe we can improve those times by adding new nodes to K-root in strategic locations. Here, we propose the idea of developing an experiment that would let us measure this potential improvement.
We're very excited to announce an all-new user interface (UI) for RIPE Atlas measurements. Users can now schedule, monitor and manage their own customised measurements more efficiently than ever before, and can now make use of the tagging feature when selecting probes for use in those measurements. Learn more about the new features below, explore the new interface, and let us know what you think.
During its meeting in September, the RIPE NCC presented the RIPE NCC Executive Board with a value proposition document detailing the value that RIPE Atlas can bring to network operators, researchers and the Internet community as a whole. The board asked the RIPE NCC to publish this document, which we have done here. We also plan to incorporate much of its content into the RIPE Atlas website so that RIPE Atlas users can clearly understand the different ways this global Internet measurement network can be used and the many unique benefits it provides.
The Locator/ID Separation Protocol (LISP) decouples identity from location on the current IP addresses by creating two separate namespaces. The LISPmob project aims to bring a full-featured LISP open-source implementation to Linux-flavoured systems.
This is the second part of a research project investigating the possible replacement of the current Remote Route Collectors (RRC) used for the Routing Information Services (RIS). In the second phase we developed a prototype based on the requirements determined in the first phase. Both parts of this research project were done as part of my bachelor thesis at the Hogeschool van Amsterdam (HvA).
The ATLAS, CMS, ALICE and LHCb particle detectors are designed to study particle collisions at the Large Hadron Collider (LHC) at CERN. Those as well as other existing and emerging large-scale experiments produce increasingly high volumes of data. Their source can be a wide variety of instruments, including sensors, detectors, antennas or telescopes. Although characteristics and goals of these experiments vary, they share a common challenge for real-time filtering, storage and analysis of the acquired data. One of the key components of this chain is a network, called the data acquisition network (DAQ).
Under ARIN's Number Resource Policy Manual (NRPM) Section 4.10, the IPv4 address block 23.128/10 is reserved for allocations and assignments dedicated to facilitate IPv6 deployment. The maximum allocation size is a /24; the minimum allocation size is a /28. There has been much discussion on the NANOG mailing list about the usability/routability of prefixes longer than a /24. In order to try to provide some additional data on this topic, the RIPE NCC has requested a small block of address space from the reserved /10 to test these types of prefixes.
The ninth annual Internet Governance Forum (IGF) ran from 1-5 September in Istanbul, Turkey, attracting nearly 2,500 participants on-site and more than 1,000 online to participate in wide-ranging Internet governance discussions. As part of ongoing efforts to ensure a strong technical community voice in IGF discussions, the RIPE NCC funded the participation of several key community members from across the service region. This article brings together some of their impressions and feedback from the event.