Skip to main content

Archived Plans

You can find our plans from previous quarters, along with requests from the community, on this page. We are updating this page at the end of each quarter.

2024 Plans and Community Input

Item 1: Improvements in the registry software

We made some changes to our internal registry software about End Users to make it more future-proof. Our goal was to modify the architecture of how we store some of the information, add some additional functionality and increase automation.

Completed in Q1 2024.

Item 2: Strengthening the security of RIPE NCC Access by enforcing Two Factor Authentication

Our main plan for 2024 is to strengthen the security of RIPE NCC Access. Since 27 March, it has been mandatory with RIPE NCC Access to use Two Factor Authentication (2FA).

The interim measure to remind users to enable 2FA has been removed, and since 27 March, 2FA has been required to log in with RIPE NCC Access. We still show LIR admins which users have not enabled 2FA because they can see which users do not have access to their accounts. We achieved this by offloading the log-in and log-out flows from an in-house developed code to Keycloak, which is the engine behind SSO.

Status: Completed

Item 3: Automation of the Assisted Registry Check (ARC)

The ARCs are part of the RIPE NCC's auditing activity. The process has been email-based until now, with little automation. We plan to increase automation for this activity to make it easier for members to complete it and increase the activity's efficiency and accuracy.

Status: In progress

2023 Plans and Community Input

Item 1: Support for the upcoming RIPE Meeting and General Meeting

We made a number of changes to improve the process of getting the registrations for voting for the General Meeting to the new voting tool (Assembly Voting), which was introduced at RIPE 85.

Completed in Q3 2023.

Item 2: Increase the availability of the registry software

We increased the availability of our internal registry software in order to reduce downtime for planned and unplanned events.

Completed in Q2 2023.

Item 3: Service criticality of RIPE NCC Access and LIR Portal

We formulated a framework with the community to determine the level of criticality of RIPE NCC services, including the RIPE NCC Access and LIR Portal.

Read more about our service criticality rating.

Completed in Q2 2023.

2022 Plans and Community Input

Item 1: Ticketing system improvements

After receiving requests from the community, we have improved several areas of our ticketing system.

Completed in Q1 2022.

Item 2: Changes in invoicing for UA and RU members

We made the necessary system changes to postpone payment obligations for UA and RU members.

Completed in Q2 2022.

Item 3: NWI-10 Phase 3

We made improvements to our software to propagate and synchronise the legal country code of End Users to the organisation object in the RIPE Database as well as the RIPE NCC (extended) delegated stats as described in NWI-10.

More information on RIPE Labs.

Completed in Q4 2022.

Community Input BA-2022#03: Mobile version of the LIR Portal

A user raised at RIPE 84 that the mobile version of replying to tickets via the LIR portal could be improved. We have made improvements to address the issues raised.

Completed in Q2 2022.

2021 Plans and Community Input

Item 1: GDPR - ID verification

We have started using a third-party service to improve and standardise the verification of ID documents.

Completed in Q4 2021.

Item 2: Improve handling of sanctioned organisations

After temporary restrictions, we have re-opened the LIR Portal for sanctioned members with limited functionality. Certain actions are not permitted due to sanctions (resource requests, transfers, etc.).

Completed in Q4 2021.

Item 3: Support for the RIPE Meeting and General Meeting

We supported the RIPE Meeting administration team and helped the General Meeting team with verifying the meeting's voters.

Completed in Q4 2021.

Item 4: Improve our internal systems

We have worked on and will continue introducing technical and security improvements to our internal systems, particularly our registry and finance software. This included protecting our systems from the log4j zero-day vulnerability.

Completed in Q4 2021.