<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span style="font-size: 13px;">[Apologies for duplicate emails]</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">Dear colleagues,</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">When reviewing the results of our pilot phase, we came to the conclusion that it would be better to build RIPE Atlas anchors as a single-service system than to host multiple services on the same box. Therefore, we will use more modest hardware for the anchors in the next phases of the project. We will publish the full findings from the RIPE Atlas anchors project on RIPE Labs in the coming weeks.</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">The reasons for the decision to use a single-service system are:</span></div><div><span style="font-size: 13px;">- The lower price of the smaller box will allow more hosts to participate, especially from developing countries</span></div><div><span style="font-size: 13px;">- Currently, we do not have an additional service to install in the boxes because no expansion is planned for K-root in the coming year</span></div><div><span style="font-size: 13px;">- Based on the survey from September 2012, people expressing a need for multiple services on the same box did not form a clear majority; most people were interested in the anchor service and �maybe� other services</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">Using the single-service system will enable us to meet our original goals, which were to:</span></div><div><span style="font-size: 13px;">- Provide powerful hardware that can perform more measurements</span></div><div><span style="font-size: 13px;">- Provide stable targets for measurements, with more bandwidth to withstand more measurements from a larger probe</span></div><div><span style="font-size: 13px;">- Achieve greater coverage for the RIPE Atlas network and expand globally</span></div><div><span style="font-size: 13px;">- Keep related logistics and operations as simple as possible</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">The change in hardware will not immediately affect support to anchor functionality on the current Dell servers. We will continue to provide support for the anchors currently in use for the duration of the pilot hosts� service contracts. After that time, RIPE Atlas anchors will require the new hardware.</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">With this new plan, all other features and benefits of hosting the anchor remain:</span></div><div><span style="font-size: 13px;">- The anchor still performs as both the target and as a larger probe </span></div><div><span style="font-size: 13px;">- Anchors earn extra credits for their hosts, allowing hosts to perform more of the user-defined measurements about their own network(s)</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">Planned additional features include:</span></div><div><span style="font-size: 13px;">- Anchor hosts benefiting from regional anchoring measurements </span></div><div><span style="font-size: 13px;">- Packet-capturing software, which is currently being investigated</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">Our goal is to bring RIPE Atlas anchors to production by the RIPE 67 Meeting in October.</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">If you have any queries or feedback, please contact <<a href="mailto:mcb@ripe.net">mcb@ripe.net</a>>.</span></div><div><span style="font-size: 13px;"><br></span></div><div><span style="font-size: 13px;">Regards,</span></div><div><span style="font-size: 13px;">Vesna</span></div></body></html>