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

Two-Factor Authentication for RIPE NCC Access Using Passkeys
by Felipe Silveira 02 Nov '25

02 Nov '25

Dear colleagues, Two-factor authentication (2FA) was made mandatory for all RIPE NCC Access accounts in March earlier this year, and we received many requests to use security keys as an authentication method. You can now use passkeys as a two-factor authentication method for RIPE NCC Access accounts, in addition to authenticator apps. Passkeys can be stored on an hardware security key (FIDO2 compatible) or in a password manager, potentially synced across devices. They are supported on mobile devices (iOS, Android) and by most browsers on computers. If you have any feedback, please contact us at ncc(a)ripe.net Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

3 2

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