Archived Plans
You can find our plans from previous quarters along with requests from the community on this page. In Q1 2023, we separated the work items of Information Technology from the Information Security, Risk and Compliance and added them into a separate area. We are updating this page at the end of each quarter.
Q3 2023 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Email infrastructure |
We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. We have new Salt-managed MX servers and containerised Mailman 3 for mailing lists. We migrated internal mailing lists, and we are busy with the migration of external ones. |
| 2 | Network Attached Storage (NAS) |
We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. We are now in the process of provisioning our new infrastructure related to our storage and backup services. The work is expected to be finished in 2023-2024. |
| 3 | Containerisation and Kubernetes |
We are building a resilient Kubernetes setup in the cloud (EKS) and on-premise to host our production applications. At the same time, we are in the process of containerising our existing applications. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2023-#01 | - | - |
Q2 2023 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
We are in the process of engaging with four Working Groups (Database, DNS, NCC Services and Routing) on the criticality rating for a number of our services. This follows the process described in the Service Criticality Framework, which was presented and discussed with the community during RIPE 84. In Q1 2023, we will finalise the criticality rating for eight of our services in consultation with the community. |
| 2 | Email infrastructure |
We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. We have new Salt-managed MX servers and containerised Mailman 3 for mailing lists. We migrated internal mailing lists, and we are busy with the migration of external ones. |
| 3 | Network Attached Storage (NAS) |
We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. We are now in the process of provisioning our new infrastructure related to our storage and backup services. The work is expected to be finished in 2023-2024. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2023-#01 | - | - |
Q1 2023 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
We are in the process of engaging with four Working Groups (Database, DNS, NCC Services and Routing) on the criticality rating for a number of our services. This follows the process described in the Service Criticality Framework, which was presented and discussed with the community during RIPE 84. We will finalise the criticality rating for eight of our services in consultation with the community. |
| 2 | Email infrastructure |
We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. We have new Salt-managed MX servers and containerised Mailman 3 for mailing lists. We migrated internal mailing lists, and we are busy with the migration of external ones. |
| 3 | Network Attached Storage (NAS) |
We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. We are now in the process of provisioning our new infrastructure related to our storage and backup services. The work is expected to be finished in 2023-2024. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2023-#01 | - | - |
Q1 2023 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
We are in the process of engaging with four Working Groups (Database, DNS, NCC Services and Routing) on the criticality rating for a number of our services. This follows the process described in the Service Criticality Framework, which was presented and discussed with the community during RIPE 84. In Q1 2023, we will finalise the criticality rating for eight of our services in consultation with the community. |
| 2 | Email infrastructure |
We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. We have new Salt-managed MX servers and containerised Mailman 3 for mailing lists. We migrated internal mailing lists, and we are busy with the migration of external ones. |
| 3 | Network Attached Storage (NAS) |
We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. We are now in the process of provisioning our new infrastructure related to our storage and backup services. The work is expected to be finished in 2023-2024. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2023-#01 | - | - |
Q4 2022 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
Work started in Q1 2022. We are in the process of engaging with four Working Groups (Database, DNS, NCC Services and Routing) on the criticality rating for a number of our services. This follows the process described in the Service Criticality Framework, which was presented and discussed with the community during RIPE 84. |
| 2 | Email infrastructure |
Work started in Q1 2022. We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. |
| 3 | Network Attached Storage (NAS) |
Work started in Q2 2022. We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. |
| 4 | Compliance with ISO/IEC 27000 |
This work item has migrated to the Information Security, Risk and Compliance Quarterly Planning. Define our operations within the ISO/IEC 27000 framework and ensure that we are at the level of ISO 27001 certification, with the Plan/Do/Check/Act cycle fully in place. |
| 5 | Bug bounty programme |
This work item has migrated to the Information Security, Risk and Compliance Quarterly Planning. To supplement our existing responsible disclosure policy, we are planning to implement a public bug bounty programme for our external facing services. |
| 6 | Cooperation with security organisations |
This work item has migrated to the Information Security, Risk and Compliance Quarterly Planning. We are supporting the development of an independent TF-CSIRT and intend to join the Supervisory Board of the new Dutch foundation. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2022-#01 | - | - |
Q3 2022 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
Work started in Q1 2022 and continues in Q4 2022. We are in the process of engaging with four Working Groups (Database, DNS, NCC Services and Routing) on the criticality rating for a number of our services. This follows the process described in the Service Criticality Framework, which was presented and discussed with the community during RIPE 84. |
| 2 | Email infrastructure |
Work started in Q1 2022 and continues in Q4 2022. We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. |
| 3 | Network Attached Storage (NAS) |
Work started in Q2 2022 and continues in Q4 2022. We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. |
| 4 | Compliance with ISO/IEC 27000 |
Work started in Q1 2022 and continues in Q4 2022. Define our operations within the ISO/IEC 27000 framework and ensure that we are at the level of ISO 27001 certification, with the Plan/Do/Check/Act cycle fully in place. |
| 5 | Bug bounty programme |
Work started in Q3 2022 and continues in Q4 2022. To supplement our existing responsible disclosure policy, we are planning to implement a public bug bounty programme for our external facing services. |
| 6 | Cooperation with security organisations |
Work started in Q3 2022 and continues in Q4 2022. We are supporting the development of an independent TF-CSIRT and intend to join the Supervisory Board of the new Dutch foundation. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2022-#01 | - | - |
Q2 2022 Plans and Community Input
| Plans | ||
|---|---|---|
| Item | Activity | Description |
| 1 | Defining the criticality of RIPE NCC services, part of the cloud strategy framework |
Work started in Q1 2022 and continues in Q4 2022. We are incorporating the feedback received from the community and staff since we presented our first draft during RIPE 83. |
| 2 | Email infrastructure |
Work started in Q1 2022 and continues in Q4 2022. We are upgrading our mailing list software from Mailman 2 to Mailman 3, containerising it in the process. |
| 3 | Network Attached Storage (NAS) |
Work started in Q2 2022 and continues in Q4 2022. We are revisiting our NAS infrastructure configuration and consulting with our suppliers on the best way forward regarding our storage, backup infrastructure and setup. |
| 4 | Compliance with ISO/IEC 27000 |
Work started in Q1 2022 and continues in Q4 2022. Define our operations within the ISO/IEC 27000 framework and ensure that we are at the level of ISO 27001 certification, with the Plan/Do/Check/Act cycle fully in place. |
| Community Input | ||
| Reference | Input | RIPE NCC Reaction |
| IT-2022-#01 | - | - |