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.

Q4 2023 Plans and Community Input

Plans
Item Activity Description
1 Modernisation of RIPE NCC Access

RIPE NCC Access (SSO) combines a third-party identity provider and an application we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.
 
In Q3 2022, our preferred candidate decided to stop providing access in some countries within our service region due to sanctions, and the risk of that happening to other providers increased. Therefore we decided to use Keycloak, an open-source solution. This brings new challenges, so we have been working on the architecture and the infrastructure needed for the new tool. To reduce the maintenance effort, in Q2 2023, we deployed the solution to EKS (Kubernetes in AWS) with a disaster recovery solution in place in case our access to AWS is cut off for any reason. 

The next phase of the implementation is introducing additional features such as SSO integration with other platforms, additional multi-factor authentication options, and improved security.

2 Improvements in the registry software

We plan to make some changes to our internal registry software in relation to End Users to make it more future-proof. We would like to make some modifications to the architecture of how we store some of the information, add some additional functionality and increase automation.

3 Automation of the Assisted Registry Check (ARC)

The ARCs are part of the auditing activity of the RIPE NCC. 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 as well as to increase the efficiency and accuracy of the activity.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

New feature requests for the LIR Portal are on hold pending the modernisation of the RIPE NCC access solution.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.  
BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.  
BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.  

Q3 2023 Plans and Community Input

Plans
Item Activity Description
1 Modernisation of RIPE NCC Access

RIPE NCC Access (SSO) combines a third-party identity provider and an application we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.
 
In Q3 2022, our preferred candidate decided to stop providing access in some countries within our service region due to sanctions, and the risk of that happening to other providers increased. Therefore we decided to use Keycloak, an open-source solution. This brings new challenges, so we have been working on the architecture and the infrastructure needed for the new tool. To reduce the maintenance effort, we plan to deploy the solution to EKS (Kubernetes in AWS) with a disaster recovery solution in place in case our access to AWS is cut off for any reason. 

The next phase of the implementation is introducing additional features such as SSO integration with other platforms, additional multi-factor authentication options, and improved security.

2 Improvements in the registry software

We plan to make some changes to our internal registry software in relation to End Users to make it more future-proof. We would like to make some modifications to the architecture of how we store some of the information, add some additional functionality and increase automation.

3 Automation of the Assisted Registry Check (ARC)

The ARCs are part of the auditing activity of the RIPE NCC. 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 as well as to increase the efficiency and accuracy of the activity.

4 Support for the upcoming RIPE Meeting and General Meeting

We are making 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.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

New feature requests for the LIR Portal are on hold pending the modernisation of the RIPE NCC access solution.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.  
BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.  
BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.  

Q2 2023 Plans and Community Input

Plans
Item Activity Description
1 Modernisation of RIPE NCC Access

RIPE NCC Access (SSO) combines a third-party identity provider and an application we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.
 
In Q3 2022, our preferred candidate decided to stop providing access in some countries within our service region due to sanctions, and the risk of that happening to other providers increased. Therefore we decided to use Keycloak, an open-source solution. This brings new challenges, so we have been working on the architecture and the infrastructure needed for the new tool. To reduce the maintenance effort, we plan to deploy the solution to EKS (Kubernetes in AWS) with a disaster recovery solution in place in case our access to AWS is cut off for any reason. 

We will continue this work in Q2 2023 and prepare the first migration phase.

2 Improvements in the registry software

We plan to make some changes to our internal registry software in relation to End Users to make it more future-proof. We would like to make some modifications to the architecture of how we store some of the information, add some additional functionality and increase automation.

3 Increase the availability of the registry software

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

4 Service criticality of RIPE NCC Access and LIR Portal

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

The framework has been complete, and the RIPE NCC Services WG was asked for feedback about the ratings of the above services. Despite extending the deadline for feedback, the input was minimal. Therefore, we are in the process of finalising the ratings and publicising them on our website.

5 Automation of the Assisted Registry Check (ARC)

The ARCs are part of the auditing activity of the RIPE NCC. 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 as well as to increase the efficiency and accuracy of the activity.

6 Support for the upcoming RIPE Meeting and General Meeting

We are making 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.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

New feature requests for the LIR Portal are on hold pending the modernisation of the RIPE NCC access solution.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.  
BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.  
BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.  

Q1 2023 Plans and Community Input

Plans
Item Activity Description
1 Monitoring registry accuracy

We are proactively monitoring changes in the business structure of our members by leveraging external data sources (i.e. Altares Dun & Bradstreet).

We are now monitoring changes in legal name, legal address, registration number and members' operating status.

2 Modernisation of RIPE NCC Access

RIPE NCC Access (SSO) is a combination of a third-party identity provider and an application that we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.
 
In Q3 2022, our preferred candidate decided to stop providing access in some countries within our service region due to sanctions, and the risk of that happening to other providers increased. Therefore we decided to use an open-source solution (Keycloak) and completed its assessment in Q4 2022. This brings new challenges, so we have been working on the architecture and the infrastructure needed for the new tool. We will continue in Q1 2023 and prepare the first phase of migration.

3 Improvements in the registry software

We plan to make some changes to our internal registry software in relation to End Users to make it more future-proof. We would like to make some modifications to the architecture of how we store some of the information, add some additional functionality and increase automation.

4 Increase the availability of the registry software

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

5 Service criticality of RIPE NCC Access and LIR Portal

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

The framework is complete, and a proposal for the LIR Portal and RIPE NCC Access was sent to the RIPE NCC Services WG for feedback.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.

We will investigate creating an additional user profile in the LIR Portal with more restricted rights. 

We first recorded this request in Q3 2022.

Q4 2022 Plans and Community Input

Plans
Item Activity Description
1 Monitoring registry accuracy

We are proactively monitoring changes in the business structure of our members by leveraging external data sources (i.e. Altares Dun & Bradstreet).

We are now able to monitor changes in legal name and members' operating status, and in Q4 2022, we plan on adding monitoring for other types of business structure changes.

2 Modernisation of RIPE NCC Access

RIPE NCC Access (SSO) is a combination of a third-party identity provider and an application that we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.

In Q3 2022, we completed the proof of concepts (POCs) we needed to get input on the future architecture. We are currently in the process of finalising vendor selection to replace our current Identity Management product (the core of SSO), and running the legal and information security checks.

We intend to follow up with a RIPE Labs article soon.

3 NWI-10 Phase 3

The work was completed in Q4 2022.

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.

4 Improvements in the registry software

We plan to make some changes to our internal registry software in relation to End Users to make it more future-proof. We would like to make some modifications to the architecture of how we store some of the information, add some additional functionality and increase automation.

5 Increase the availability of the registry software

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

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.

We will investigate creating an additional user profile in the LIR Portal with more restricted rights. 

We first recorded this request in Q3 2022.

Q3 2022 Plans and Community Input

Plans
Item Activity Description
1 Monitoring registry accuracy

Work started in Q4 2021.

We are proactively monitoring changes in the business structure of our members by leveraging external data sources (i.e. Altares Dun & Bradstreet).

We are now able to monitor changes in legal name and members' operating status, and in Q4 2022, we plan on adding monitoring for other types of business structure changes.

2 Modernisation of RIPE NCC Access

Work started in Q1 2022.

RIPE NCC Access (SSO) is a combination of a third-party identity provider and an application that we have developed in-house. We have several issues with the current solution, so we want to review the architecture and decide on what changes we can make in the future.

So far, we have identified that replacing core components of the SSO is a very complex project. We are busy with vendor selection to replace our current Identity Management product (the core of SSO), creating proofs of concept (POCs) to decide on future architecture and preparing our current system for the new solution.

In Q3, we will finalise on vendor and architecture and start with the implementation.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#04 Request to introduce a 'Read Only' account level in the LIR Portal.

We will investigate creating an additional user profile in the LIR Portal with more restricted rights. 

We first recorded this request in Q3 2022.

Q2 2022 Plans and Community Input

Plans
Item Activity Description
1 Monitoring registry accuracy

Work started in Q4 2021.

We are proactively monitoring changes in the business structure of our members by leveraging on external data sources (i.e. Altares Dun & Bradstreet).

2 Digital identification services

Work started in Q1 2022 and was put on hold in Q2 2022 due to shifting priorities.

After investigation we saw that the Dutch digital identity solution for individuals (DigiD) cannot be used for our purpose. There is another solution for companies (E-herkenning) which is pending investigation. We also started exploring the European digital identity project (eIDAS) which is in early stages, not implemented by many countries, but more investigation is pending.

3 Modernisation of RIPE NCC Access

Work started in Q1 2022.

RIPE NCC Access (SSO) is a combination of a third-party identity provider and an application that we have developed in-house. We have several issues with the current solution, therefore we want to review the architecture and decide on what changes we can make in the future.

4  Changes in invoicing for UA and RU members

This work item was not included in the initial planning. 

We made necessary system changes for postponing payment obligations for UA and RU members.

5 Payment provider interface changes

This work item was not included in the initial planning. 

We updated our payment system accordingly to match the changes (Pay by Link) introduced by our payment provider, Adyen.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.

BA-2022-#01 Request on the mailing list to automatically add the primary LIR contact as CC: in all tickets, or to provide the ability to add additional CC:’s via the LIR Portal after the ticket has been created.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#02 Request on the mailing list to have the ability to trim the CC: list of a given ticket (for example to remove ticketing systems), or the ability to add a custom tag to the email Subject: line to facilitate better ticket tracking.

We will investigate possibilities here and add a reaction when ready.

We first recorded this request in Q2 2022.

BA-2022-#03 A user raised at RIPE 84 that the mobile version of replying to tickets via the LIR portal could be improved.

Completed

We have made improvements to address the issues raised.

Q1 2022 Plans and Community Input

Plans
Item Activity Description
1 Ticketing system improvements

Work started in Q4 2021 and was completed in Q1 2022.

There were requests from the community to improve some areas of the ticketing system, and have since made improvements.

2 Monitoring registry accuracy

Work started in Q4 2021.

We are proactively monitoring changes in the business structure of our members by leveraging on external data sources (i.e. Altares Dun & Bradstreet).

3 Digital identification services

Work started in Q1 2022 and was put on hold in Q2 2022 due to shifting priorities.

Preliminary investigation of the use of digital identification services for the registry services workflows.

4 Modernisation of RIPE NCC Access

Work started in Q1 2022.

RIPE NCC Access (SSO) is a combination of a third-party identity provider and an application that we have developed in-house. We have several issues with the current solution, therefore we want to review the architecture and decide on what changes we can make in the future.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.

Q4 2021 Plans and Community Input

Plans
Item Activity Description
1

GDPR: ID verification

Work was completed in Q4 2021.

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

2 Ticketing system improvements

Work started in Q4 2021 and was completed in Q1 2022.

There were requests from the community to improve some areas of the ticketing system. We are analysing at the moment what is possible and have planned out improvements.

3 Monitoring registry accuracy

Work started in Q4 2021.

We are proactively monitoring changes in the business structure of our members by leveraging on external data sources (i.e. Altares Dun & Bradstreet).

4 Improve handling of sanctioned organisations

Work was completed in Q4 2021.

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.).

5 Support for the RIPE Meeting and General Meeting

Work was completed in Q4 2021.

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

6 Improve our internal systems

Work was completed in Q4 2021.

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.

Community Input
Reference Input RIPE NCC Reaction
BA-2021-#01 Request to add a "view only" user to the LIR Portal that would allow the defined user to see all resources of the specific LIR (including RPKI) but not be able to modify anything.

We'll investigate possibilities here and add a reaction when ready. As shared on the mailing list, please share your feedback with us on what you would like to see on the LIR Portal.

We first recorded this request in Q4 2021.