Re: [atlas] Updated RIPE Atlas Documentation
Hi, I’m out of office till 22 August. Any RIPE Labs related queries can be sent to l...@ripe.net and one of my colleagues will get back to you. Cheers, Alun On 4 Aug 2022, at 00:14, Simon Brandt via ripe-atlas wrote: > Hi, > > a lot of previously published URLs are not working anymore: "Document Not > Found". For example, links that have been posted in labs.ripe.net articles. > Those articles are now kind of... incomplete. Are there any plans to fix > this? Maybe mod_rewrite or something? > > Here's an example: > https://labs.ripe.net/author/alun_davies/announcing-ripe-atlas-vm-anchors/ > The URL "installation instructions for VM anchors" does not work anymore. > Also: i wasn't able to find that article by using the search bar in the new > documentation. > > BR, > Simon > > > On 15.07.22 16:44, camin wrote: > Dear colleagues, > > A new version of the RIPE Atlas documentation has been published. We have > consolidated the text in places and improved the structure to make it easier > to find content. > > The new version can be found at: > > https://atlas.ripe.net/docs/ > > Regards, > Chris Amin > > > -- > ripe-atlas mailing list > ripe-atlas@ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
Re: [atlas] Updated RIPE Atlas Documentation
Hi, I’m out of office till 22 August. Any RIPE Labs related queries can be sent to l...@ripe.net and one of my colleagues will get back to you. Cheers, Alun On 4 Aug 2022, at 00:24, Simon Brandt via ripe-atlas wrote: > Alright, i just found out that the old documentation is still available, it > has been renamed to "docs-old": > https://atlas.ripe.net/docs-old/anchor-installation-vm/ > > So maybe update all affected labs.ripe.net articles? I guess it's still > better to refer to docs-old pages than "Document Not Found". > > BR, > Simon > > > > On 04.08.22 00:14, Simon Brandt via ripe-atlas wrote: > Hi, > > a lot of previously published URLs are not working anymore: "Document Not > Found". For example, links that have been posted in labs.ripe.net articles. > Those articles are now kind of... incomplete. Are there any plans to fix > this? Maybe mod_rewrite or something? > > Here's an example: > https://labs.ripe.net/author/alun_davies/announcing-ripe-atlas-vm-anchors/ > The URL "installation instructions for VM anchors" does not work anymore. > Also: i wasn't able to find that article by using the search bar in the new > documentation. > > BR, > Simon > > > On 15.07.22 16:44, camin wrote: > Dear colleagues, > > A new version of the RIPE Atlas documentation has been published. We have > consolidated the text in places and improved the structure to make it easier > to find content. > > The new version can be found at: > > https://atlas.ripe.net/docs/ > > Regards, > Chris Amin > > > > > > -- > ripe-atlas mailing list > ripe-atlas@ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
Re: [atlas] Updated RIPE Atlas Documentation
Hi, I’m out of office till 22 August. Any RIPE Labs related queries can be sent to l...@ripe.net and one of my colleagues will get back to you. Cheers, Alun On 4 Aug 2022, at 00:24, Simon Brandt via ripe-atlas wrote: > Alright, i just found out that the old documentation is still available, it > has been renamed to "docs-old": > https://atlas.ripe.net/docs-old/anchor-installation-vm/ > > So maybe update all affected labs.ripe.net articles? I guess it's still > better to refer to docs-old pages than "Document Not Found". > > BR, > Simon > > > > On 04.08.22 00:14, Simon Brandt via ripe-atlas wrote: > Hi, > > a lot of previously published URLs are not working anymore: "Document Not > Found". For example, links that have been posted in labs.ripe.net articles. > Those articles are now kind of... incomplete. Are there any plans to fix > this? Maybe mod_rewrite or something? > > Here's an example: > https://labs.ripe.net/author/alun_davies/announcing-ripe-atlas-vm-anchors/ > The URL "installation instructions for VM anchors" does not work anymore. > Also: i wasn't able to find that article by using the search bar in the new > documentation. > > BR, > Simon > > > On 15.07.22 16:44, camin wrote: > Dear colleagues, > > A new version of the RIPE Atlas documentation has been published. We have > consolidated the text in places and improved the structure to make it easier > to find content. > > The new version can be found at: > > https://atlas.ripe.net/docs/ > > Regards, > Chris Amin > > > > > > -- > ripe-atlas mailing list > ripe-atlas@ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
Re: [atlas] Updated RIPE Atlas Documentation
Hi, I’m out of office till 22 August. Any RIPE Labs related queries can be sent to l...@ripe.net and one of my colleagues will get back to you. Cheers, Alun On 4 Aug 2022, at 00:14, Simon Brandt via ripe-atlas wrote: > Hi, > > a lot of previously published URLs are not working anymore: "Document Not > Found". For example, links that have been posted in labs.ripe.net articles. > Those articles are now kind of... incomplete. Are there any plans to fix > this? Maybe mod_rewrite or something? > > Here's an example: > https://labs.ripe.net/author/alun_davies/announcing-ripe-atlas-vm-anchors/ > The URL "installation instructions for VM anchors" does not work anymore. > Also: i wasn't able to find that article by using the search bar in the new > documentation. > > BR, > Simon > > > On 15.07.22 16:44, camin wrote: > Dear colleagues, > > A new version of the RIPE Atlas documentation has been published. We have > consolidated the text in places and improved the structure to make it easier > to find content. > > The new version can be found at: > > https://atlas.ripe.net/docs/ > > Regards, > Chris Amin > > > -- > ripe-atlas mailing list > ripe-atlas@ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
[atlas] New on RIPE Labs: Bias in Internet Measurement Infrastructure
Dear colleagues, In this new article on RIPE Labs, Pavlos Sermpezis talks about analysing bias in the Internet measurement infrastructures like RIPE Atlas and RIPE RIS. Are these infrastructures biased? How much of a problem is it if they are? What does bias even look like here? Find out more: https://labs.ripe.net/author/pavlos_sermpezis/bias-in-internet-measurement-infrastructure/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC -- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
[atlas] New on RIPE Labs: Latency Into Your Network - As Seen From RIPE Atlas
Dear colleagues, New prototype visualisations - put together by Emile Aben and Agustin Formoso using the ObservableHQ platform - allow you to visualise network deployment. Drawing on latency data available from RIPE Atlas, each visualisation aims at helping reveal insights about structural latency into given networks. Read more and try it out on RIPE Labs: https://labs.ripe.net/author/emileaben/latency-into-your-network-as-seen-from-ripe-atlas/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC
[atlas] New on RIPE Labs: Deploying a RIPE Atlas Probe Software via PPP
Dear colleagues, Want to install a RIPE Atlas software probe, but not sure how to keep it isolated from your private network? In this new guest post on RIPE Labs, Aris Tzermias demonstrates how to do this using a dedicated PPP connection with your Internet Service Provider. https://labs.ripe.net/author/aris-tzermias/deploying-a-ripe-atlas-probe-software-via-ppp/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC
[atlas] New on RIPE Labs: Surrounded by the Clouds - A Comprehensive Cloud Reachability Study
Dear colleagues, Lorenzo Corneo and colleagues recently conducted a comprehensive cloud reachability study to evaluate the suitability of modern cloud environments for latency-sensitive applications. Read about the results of the study now on RIPE Labs: https://labs.ripe.net/author/lorenzo-corneo/surrounded-by-the-clouds-a-comprehensive-cloud-reachability-study/ Kind regards, Alun Davies RIPE Labs Editor RIPE NCC
[atlas] New on RIPE Labs: RIPE Atlas Big Data is Back
Dear colleagues, At the beginning of the year, RIPE Atlas users started encountering delays in data retrieval and an overall drop in the responsiveness of the system. With service having gone back to normal earlier this month, we take a look at what caused the problem and what we're doing prevent it from happening again: https://labs.ripe.net/Members/paul_de_weerd/ripe-atlas-big-data-is-back Kind regards, Alun Davies RIPE Labs Editor RIPE NCC
[atlas] New on RIPE Labs: Join Us for a RIPE NCC Open House on 10 Years of RIPE Atlas
Dear colleagues, Tomorrow we’ll he holding a RIPE NCC Open House event to celebrate 10 years of RIPE Atlas. Join us for a mix of presentations, diverse use cases from external speakers, and open discussion between the people who are helping expand RIPE Atlas right now. In this new article on RIPE Labs, we tell you what we’ve got lined up and invite you to register: https://labs.ripe.net/Members/alun_davies/join-us-for-a-ripe-ncc-open-house-on-10-years-of-ripe-atlas Kind regards, Alun Davies RIPE NCC
[atlas] New on RIPE Labs: Rolling Out the RIPE Atlas Redesign
Dear colleagues, You might have noticed that RIPE Atlas is looking different. To explain what's changed and why, this article on RIPE Labs gives an update on our latest efforts to roll out a new design for all our services: https://labs.ripe.net/Members/michela_galante/rolling-out-the-ripe-atlas-redesign Kind regards, Alun Davies RIPE NCC
Re: [atlas] RIPE Atlas usage webinar (and software probe installation demo)
Hi Bjørn, At the time of writing that article, we were seeing different pros and cons for different platforms. For example, for at least one of the other platforms mentioned here, there were pretty strict limitations on the number of participants it would allow for back then. Zoom didn't have that kind of issue, and for this and other reasons, it really did stand out as the best option overall. It’s worth adding also that, for the most part, we have received good feedback for Zoom from attendees at our events. That said, as things move on, we're continuing to explore a whole variety of new options for future events. And we're also keeping a close eye on feedback we get from attendees and others. We appreciate the input and we are taking it into account. Kind regards, Alun Davies RIPE NCC > On 18 Aug 2020, at 16:11, Bjørn Mork wrote: > > Lia Hestina writes: >>> On 18 Aug 2020, at 10:41, Bjoern Franke wrote: >>> >>> Hi, >>> >>>> For this one, unfortunately not, but there will be more soon and depending >>>> how many people attend we have other option which is Adobe connect. >>>> As soon as a new date is known, we will share it in the mailing list. >>>> Please note that the recording of this webinar that will be made public. >>> >>> what about less proprietary applications like Big Blue Button or Jitsi? >> Do you face any issue with one of or both applications I mentioned? If yes, >> please let us know. >> >> We have to consider many things when choosing a new platform, and to >> give you a bit of insight of the choice we made, I should refer you to >> this article: >> https://labs.ripe.net/Members/kranjbar/the-ripe-nccs-use-of-zoom-for-meetings >> <https://labs.ripe.net/Members/kranjbar/the-ripe-nccs-use-of-zoom-for-meetings> > > Thanks for pointing to that, but I am afraid it left me with more > questions than before reading it. AFAICS, no other options are > discussed at all. The alternatives are simply rejected with > > "the absence of other viable options that provide the reliability, > scale, support and legal and contractual requirements we have, > > without further explanation of these requirements. I must admit that > this made me very curious... Exactly which > - reliability, > - scale, > - support and > - legal and contractual requirements > > cannot be fulfilled by for example the applications Bjoern mentioned? > > > Bjørn (another one :-) >
[atlas] RIPE Atlas Software Probes Survey
Dear colleagues, We are working on making the RIPE Atlas measurement software available as an installable package so you can run RIPE Atlas probes entirely in software without the need of a dedicated physical device. We are interested in your feedback regarding this feature, and we are also looking for volunteers willing to partner with us and help package the software for various operating systems and platforms. Please send your feedback and let us know if you can support RIPE Atlas software probes by filling in this short survey: https://www.ripe.net/participate/forms/apply/atlas-probes/ <https://www.ripe.net/participate/forms/apply/atlas-probes/> Kind regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New RIPE Atlas measurement details page
Dear colleagues, We have made the switch to the new and improved user interface for RIPE Atlas measurement details. To see the new interface right now, simply click on any measurement ID on the RIPE Atlas measurement listing page: https://atlas.ripe.net/measurements/ <https://atlas.ripe.net/measurements/> Please note that, for a limited time, you will still be able to revert back to the old interface via the yellow banner at the top of the measurement details page. For further details on exactly what changes have been made and why, please see the following article on RIPE Labs: https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionality-for-the-ripe-atlas-measurement-detail-page <https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionality-for-the-ripe-atlas-measurement-detail-page> Kind regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: RIPE Atlas Anchors 400+
Dear colleagues, We have published an article looking at how the quick uptake in RIPE Atlas VM anchors and other developments have helped us hit 400 connected anchors. https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchors-400 <https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchors-400> Kind regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: Redesigning the RIPE Atlas Measurement Details Page
Dear colleagues, Today we published an article on some of the changes we’ve made to the RIPE Atlas measurement details page. The redesign follows work we’ve been doing to move over to a new back-end storage solution for RIPE Atlas measurement metadata. Click the link to find out more: https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionality-for-the-ripe-atlas-measurement-detail-page <https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionality-for-the-ripe-atlas-measurement-detail-page> Kind regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors
Dear colleagues, We just this morning published an article announcing that, as of today, we are accepting applications for anyone interested in hosting RIPE Atlas VM anchors. The article points you to all the information you’ll need to apply for and install a virtual anchor: https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors <https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchor-vms> Kind regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: 2018 Campaign to Sponsor 10 RIPE Atlas Anchors
Dear colleagues, This morning we published an article looking at the RIPE NCC’s 2018 campaign to sponsor ten RIPE Atlas anchors. This is a repeat of the successful campaign we ran last year. The article contains all the details on criteria for applicants and how to apply: https://labs.ripe.net/Members/alun_davies/2018-campaign-to-sponsor-10-ripe-atlas-anchors <https://labs.ripe.net/Members/alun_davies/2018-campaign-to-sponsor-10-ripe-atlas-anchors> Best regards, Alun Davies smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: Update on the RIPE Atlas Anchor VM pilot
Dear colleagues, We recently published an update on our pilot programme to assess the feasibility of introducing virtual machines to the pool of RIPE Atlas anchors. Read all about it in this RIPE Labs article from Robert Kisteleki: https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pilot <https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pilot> Best regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: Last sponsored RIPE Atlas anchors for 2017
Dear colleagues, New on RIPE Labs, read all about the last phase of the RIPE NCC’s 2017 campaign to sponsor fifteen RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/last-sponsored-ripe-atlas-anchors-for-2017 Kind regards, Alun Davies RIPE NCC
[atlas] New vendor for RIPE Atlas v3 anchors
Dear all, Meconet, the latest addition to our list of vendors for RIPE Atlas v3 anchors, is offering the new anchor hardware fully assembled with 3 years warranty. The RIPE Atlas anchor from Meconet comes in a 19” chassis with integrated power supply: https://shop.meconet.de/a/117330?language=en <https://shop.meconet.de/a/117330?language=en> Whilst Meconet is currently the only one offering the device fully assembled, there are other vendors listed on the following page: https://atlas.ripe.net/get-involved/become-an-anchor-host/ <https://atlas.ripe.net/get-involved/become-an-anchor-host/> Updated information on the latest generation of RIPE Atlas anchors can be found in the following RIPE Labs article: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors <https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors> Best regards, Alun Davies RIPE NCC
[atlas] New RIPE Labs article on RIPE Atlas v3 Anchors
Dear colleagues, In this RIPE Labs article the RIPE NCC looks into hardware specifications and logistics for the next generation of RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors Best regards, Alun Davies RIPE NCC
[atlas] RIPE Atlas v3 Anchor Hardware
Dear all, The RIPE NCC has chosen a new model for the RIPE Atlas v3 Anchors. The hardware we finally opted for is the PC Engines APU2. As well as being cheaper than the previous generation of anchors, this model meets the majority of requirements we laid out for the next generation of anchors. To be clear, given that there are still a couple of minor logistical details to resolve, we are still keeping applications on hold for the time being. That said, we look set to meet our September deadline to resume shipping of RIPE Atlas anchors. For more information and future updates, please read our article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas-anchors <https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas-anchors> Kind regards, Alun Davies Comms RIPE NCC
[atlas] New on RIPE Labs: The Next Generation of RIPE Atlas Anchors
Dear Colleagues, The RIPE NCC is in the process of testing hardware for the next generation of RIPE Atlas anchors. Here’s a detailed overview of the process: https://labs.ripe.net/Members/alun_davies/the-next-generation-of-ripe-atlas-anchors Best regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New RIPE Atlas Measurement Options
Dear all, The RIPE Atlas team have added a number of new measurement options on RIPE Atlas. Here’s an overview of the changes: DNS measurements timeout: allows the user to specify a custom timeout in milliseconds after which probes will stop waiting for a response from the DNS server use_macros: allows the use of special macro strings in the "query_argument" field, to create unique or easily distinguishable queries. The allowed macros are: $p the (integer) ID of the probe carrying out the measurement $r a random 16-digit hexadecimal string $t a Unix timestamp of the time that the probe carries out the DNS query SSLcert measurements hostname: specifies a hostname to send as a Server Name Indication (SNI), which is necessary for web servers which host multiple TLS domains on the same IP address. Ping measurements include_probe_id: include the probe ID as an ASCII string within the payload of ping measurements. Note: this is included in addition to other payload data. The changes are all included in the RIPE Atlas API reference: https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_List_POST <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_List_POST> If you have any questions whatsoever about the new measurement options, do let us know. As always, we welcome suggestions for new features from RIPE Atlas users. Best regards, Alun Davies RIPE NCC Communications Department smime.p7s Description: S/MIME cryptographic signature
[atlas] Firmware Update for RIPE Atlas V1 and V2 Probes
Dear all, We’re currently in the process of deploying a new firmware update for RIPE Atlas V1 and V2 probes. The update provides a fix for a bug that caused around 15% of RIPE Atlas V1 probes to disconnect. As of the time of writing, the update is at approximately 60% deployment. If you’ve been unable to reconnect your RIPE Atlas V1 probe, you can return it to the following address to be fixed. If you’d like the probe to be returned to you afterwards, please let us know. Alternatively, we’d encourage you to apply for a V3 probe. RIPE NCC P.O. Box 10096 1001EB Amsterdam The Netherlands We’d like to take this opportunity to thank all probe hosts for your ongoing efforts in supporting RIPE Atlas. Cheers, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
Re: [atlas] RIPE Atlas V1 Probe Issue
A few points of clarification are warranted following the previous mail. The firmware alluded to in the previous email was released in February 2017. Since then, approximately 100 RIPE Atlas V1 probes have disconnected - about 15% of the total number of V1 probes on the network. The fix that is currently in the making is expected to be released in a month or so. If at that time you have still been unable to reconnect your V1 probe, you can then return your probe to be fixed. Alternatively, you may apply for a V3 probe by following the usual process as described here: https://atlas.ripe.net/get-involved/become-a-host/ <https://atlas.ripe.net/get-involved/become-a-host/> Cheers, Alun Davies RIPE NCC > On 16 May 2017, at 16:22, Alun Davies wrote: > > Hello all, > > Due to an unfortunate bug in a recently released probe firmware (version > 4760), a number of RIPE Atlas V1 probes are not currently able to connect to > the network. The bug leads to excessive memory fragmentation which impacts > that V1 probes because they have no MMU and only 8 MByte worth of memory. > > For reasons that are not yet clear, the issue has only affected well below > half of the V1 probes. We are working on a new firmware that will correct > this issue, but probes that will not connect will need to be returned to the > RIPE NCC in order for the fix to be carried out. Once the new firmware is > ready, users can either return their V1 probes to us to be fixed, or request > a V3 probe instead. > > Thank you to Wilfred Woeber for reporting this and requesting an update on > the current issue with the V1 probes. > > Cheers, > Alun Davies > RIPE NCC > > > smime.p7s Description: S/MIME cryptographic signature
[atlas] RIPE Atlas V1 Probe Issue
Hello all, Due to an unfortunate bug in a recently released probe firmware (version 4760), a number of RIPE Atlas V1 probes are not currently able to connect to the network. The bug leads to excessive memory fragmentation which impacts that V1 probes because they have no MMU and only 8 MByte worth of memory. For reasons that are not yet clear, the issue has only affected well below half of the V1 probes. We are working on a new firmware that will correct this issue, but probes that will not connect will need to be returned to the RIPE NCC in order for the fix to be carried out. Once the new firmware is ready, users can either return their V1 probes to us to be fixed, or request a V3 probe instead. Thank you to Wilfred Woeber for reporting this and requesting an update on the current issue with the V1 probes. Cheers, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] New on RIPE Labs: Update on First Five Sponsored RIPE Atlas Anchors
Hello all, We just released a RIPE Labs article giving an update on the RIPE NCC’s campaign to sponsor fifteen RIPE Atlas anchors: https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-atlas-anchors <https://labs.ripe.net/Members/alun_davies/update-first-five-sponsored-ripe-atlas-anchors> Best regards, Alun Davies RIPE NCC smime.p7s Description: S/MIME cryptographic signature
[atlas] Emails Regarding Probe Connection Issues
Dear members of the RIPE Atlas community, It was recently called to our attention that certain emails we send out to RIPE Atlas probe hosts, concerning probe connection issues, have been somewhat abrupt in their tone. We are working to address the issue. While we devote a great deal of effort to ensuring that any correspondence we send out is both informative in content and appropriate in tone, we greatly appreciate feedback whenever it is felt that such goals have not been met. We would like to take this opportunity to once again thank all RIPE Atlas probe hosts for their ongoing participation. Best regards, Alun Davies (RIPE NCC) smime.p7s Description: S/MIME cryptographic signature
