- ncc-services-wg - mailman.ripe.net

Exit Strategy for Cloud Services
by Felipe Silveira 31 May '24

31 May '24

Dear colleagues, First of all, I would like to thank you all for the engaged discussions and feedback received during RIPE 88 last week. Following up on some of the questions raised during my presentation last week, I would like to clarify a couple of points, mostly around RIPE NCC’s exit strategy for our cloud providers. First point raised was concerning the exit cost for AWS S3 should we decide to move to a different provider, potentially at very short notice. As part of the AWS S3 pricing model, a certain amount is charged for egress costs. Due to the large amount of data we have stored in AWS (in the order of petabytes of uncompressed data), this could potentially lead to a large bill. However, following the direction set by the European Data Act, AWS decided to waive all egress fees for customers migrating their data to a competitor (or to on-premise): https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-mo… However, even in a partial exit scenario, where we decide to stay with AWS but move only one service out, and thus egress costs waiving would not apply, the S3 exit cost for the Atlas historical data would be in the order of a few thousand euros. The other point raised was about our exit strategy in general, not only referring to egress costs. Our strategy is to use industry standards (e.g. Kubernetes) as a way to mitigate switching costs, as many providers offer alternative solutions. That is true for both AWS S3 and Kubernetes, having similar solutions offered by other companies. We also pay very close attention to our backup strategy (e.g. having the data stored elsewhere) and diversifying our suppliers. If you have any questions, please do not hesitate to contact me. Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

1 0

RIPE Labs: Reflections on Six Months as Chief Registry Officer
by James Kennedy 17 May '24

17 May '24

Dear colleagues, I have published a new RIPE Labs article reflecting on my first six months as Chief Registry Officer: https://labs.ripe.net/author/james-kennedy/reflections-on-six-months-as-chi… In the article, I explore the changing environment and how some of the associated pressures are affecting our Registry Department. I also look at the impact of the increased volume of End User ASN requests and provide some numbers on our overall workload. Any feedback or questions are welcome. However, please note that ASN related discussions are probably best held on the Address Policy WG mailing list, where I have also shared this article. Kind regards, James Kennedy Chief Registry Officer RIPE NCC

1 0

RIPE NCC Registry Investigation Report Published
by James Kennedy 16 May '24

16 May '24

Dear colleagues, We have published a report detailing the findings of an investigation into an attempt to defraud the registry. The report is available at: https://www.ripe.net/support/documentation/disclosures-and-reports/ripe-ncc… In recent months, we have uncovered an unusual pattern of incidents concerning unauthorised access to certain LIR accounts. Attempts were made to gain access to resources through fraud and to transfer resources without authorisation from the legitimate holders. Following an investigation, the unauthorised transfers were reverted and the membership of the party submitting fraudulent documents has been terminated. We, therefore, encourage our members to work with us to ensure the security of your resources and to report any suspicious activity concerning your accounts. We recommend the following measures: - Be vigilant about the validity of your email domains and email security. - Ensure that all contacts in your LIR account are valid and kept up to date. - Report any suspicious activity to us immediately. - Store account credentials in a secure manner, and stop using shared accounts. Kind regards, James Kennedy Chief Registry Officer RIPE NCC

1 0

Agenda for the NCC Services WG meeting at RIPE 88
by Rob Evans 13 May '24

13 May '24

Hi, This is the agenda for our meeting during RIPE 88 in three weeks’ time. Cheers, Rob (on behalf of the WG co-chairs) RIPE NCC Services Working Group May 22, 2024, 14:00 - 15:30 CEST. Krakow, PL, and virtually. A. Welcome, admin. [5 minutes] B. Update from the RIPE NCC, Hans Petter Holen [30 minutes] C. Technology Update, Felipe Victolla Silveira [25 minutes] D. Registry Update, James Kennedy [20 minutes] Z. Open Mic [10 minutes]

1 1

Retiring ns.ripe.net
by Paul de Weerd 02 May '24

02 May '24

Dear colleagues, We have published a RIPE Labs article on how we believe it is now time to retire the secondary DNS service for member’s reverse DNS delegations, ns.ripe.net: https://labs.ripe.net/author/anandb/retiring-nsripenet/ We are proposing to retire the secondary DNS service by the end of 2024 and we're asking for your input and feedback on this proposal. Please share any feedback on the DNS Working Group mailing list by 16 May 2024. Once we’ve collected your feedback, we will discuss this topic in the DNS Working Group session at RIPE 88 on Wednesday, 22 May 2024. Paul de Weerd Manager Global Information Infrastructure team RIPE NCC

1 0

RIPE NCC Access Security Investigation Report Published
by Hans Petter Holen 24 Apr '24

24 Apr '24

Dear colleagues, We have published a report on our findings and actions taken following an investigation into a security breach concerning RIPE NCC Access, our Single Sign-On system. This report follows the last update that we shared with you in January this year [1]. Since the launch of the investigation, we have made two-factor authentication mandatory for all RIPE NCC Access accounts, strengthened password requirements, improved monitoring for leaked credentials and automated the process of resetting passwords for any credentials found in data breaches. Read the full report at: https://www.ripe.net/support/documentation/disclosures-and-reports/ripe-ncc… We further recommend that members follow our security recommendations: - Please restrict account access to necessary personnel only - Follow password security best practices - Actively monitor data breaches for your own credentials If you have any concerns about the security of your RIPE NCC Access account, please contact us at ncc(a)ripe.net. Regards, Hans Petter Holen, CEO and Managing Director RIPE NCC [1] https://www.ripe.net/ripe/mail/archives/ncc-announce/2024-January/001695.ht…

1 0

New RIPE Labs Article - Building a stable future for the RIPE NCC
by Remco van Mook 18 Apr '24

18 Apr '24

Dear colleagues, I’d like to draw your attention to an article that was just published on RIPE Labs, about building a stable future for the RIPE NCC. As it touches on some very foundational aspects all across the various working groups and NCC membership, I thought it important to share, and I would very much like to ask everyone for their input and ideas. In order to not spread the discussion too much across the various mailing lists, I suggest that we use the general RIPE list (which I’ve put into the reply-to field of this email. I’m currently in the process of organising a BOF during RIPE 88 on this topic as well and am looking forward to a constructive discussion! Kind regards, Remco van Mook RIPE NCC Executive Board

1 1

Enhancing the Security of RIPE NCC Access
by Felipe Victolla Silveira 10 Apr '24

10 Apr '24

Dear colleagues, Over the past few months, the RIPE NCC has been working on enhancing the security of RIPE NCC Access. In a new article on RIPE Labs, I explain the recent enhancements we've implemented and provide an overview of forthcoming developments you can anticipate from us: https://labs.ripe.net/author/felipe_victolla_silveira/enhancing-the-securit… Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

2 1

Using Google for RIPE NCC Email
by Felipe Victolla Silveira 04 Apr '24

04 Apr '24

Dear colleagues, We want to inform you that from today we will be using Google for some of our email infrastructure at the RIPE NCC - we use Gmail to host our mailboxes, filter mail for spam and malware, and send some of our outgoing mail through their mail servers. On some emails we send, the headers will show they passed through the Google servers, but it’s still the same RIPE NCC you’re talking with. We have been using Google Workspace for some time internally for other purposes, so this change allows us to reduce operational overhead at no extra cost. All of the external cloud providers that we use are published here for transparency: https://www.ripe.net/support/documentation/cloud-technology-status/ Regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

1 0

RIPE NCC Quarterly Planning Q2 2024
by Adonis Stergiopoulos 02 Apr '24

02 Apr '24

Dear colleagues, We have now published the Q2 2024 quarterly plans for our development teams: https://www.ripe.net/support/documentation/quarterly-planning Our plans include the work that will be carried out in the next few months and give you the opportunity to comment on those plans and suggest items that the RIPE NCC should be working on going forward. The plans cover the following areas: - Learning & Development - RIPE Database - Business Applications, including the LIR Portal, Registry Services and other applications. - DNS and K-root - RIPE Atlas - RIPEstat - Resource Public Key Infrastructure (RPKI) - Routing Information Service (RIS) - Information Security, Risk, and Compliance We have also made some changes to our reporting process. First, following our website refresh, we made it easier to identify the completed work items of previous quarters. You can check this by clicking on the ‘Archived Plans’ sub-page for each area. Second, we have decided to discontinue reporting on our ‘Information Technology (IT)’ area as we could only provide limited details, and the information was mostly relevant to internal teams. The previous IT plans will remain active on our website until they expire as part of our archiving process. If you have any questions or any input on these plans, please reach out to us. Kind regards, Adonis Stergiopoulos Senior Marketing & Communications Officer RIPE NCC

1 0