The intention of this mapping is to identify both existing competence and future interests across NRENs. Based on the input, we aim to highlight areas where collaboration would create added value. The results will be reviewed in the next SIG meeting, where potential topics can be further specified and shaped into concrete collaboration projects.
Collaboration Area | Description | Current Experience/Competence (what you do today) | Future Plans/Interests (what you want to achieve) 2026 | Future plans (2027+) | Where do you want to collaborate on? | NREN | Names of NRENs interested in collaboration |
|---|---|---|---|---|---|---|---|
Knowledge sharing / competence mapping | Use of BookStack as internal documentation system |
|
| Experiences in use of different documentation systems (Wikis) | Sikt |
| |
|
|
|
|
|
|
|
|
Standardisation of architecture and interoperability |
| wireless-as-a-service architecture and implementation plans |
|
|
| SURF |
|
|
| Preferred design based on Juniper FW, switches and WiFi. | Less implementations that deviate from preferred design |
| Find designs that can be used to the majority of customers | Sikt |
|
|
| WiFi design and planning |
|
| WiFi7 | Sikt |
|
|
| EVPN/VxLAN with Juniper |
|
|
| Sikt |
|
|
|
|
|
|
|
| |
Tools and automation |
| Argus - Alarm Aggregation and Correlation Tool https://network.geant.org/argus/ | Further development of glue services and adaptable views for different use cases. |
| Sikt | SURF , RENU | |
|
| NAV - Network Administration Visualized https://nav.uninett.no/ |
|
| Sikt |
| |
|
| Scripts for configuration of Juniper equipment | Investigate the possibility of multi vendor support | Making it more usable for customers to configure themselves. | Sikt |
| |
|
| Network sensors acting as clients for alerting and troubleshooting. Today with Aruba UXI sensors. | Investigating a glue service for Argus | Investigating other vendors or solutions for a more cost effective solution | Sikt |
| |
|
| Firewall-rules and ACL administration with Juniper Security Director and FWBuilder |
| Investigate the possibilty of tools like Capirca to be more vendor agnostic. | Sikt |
| |
|
| Radius as a Service throught freeRadius and RadSecProxy | Today this service is not something we offer officially, but we would like to do that,. |
|
| Sikt |
|
|
| Hamina as Wireless planning tool and survey |
|
|
| Sikt |
|
|
|
|
|
|
|
|
|
Business models and financial frameworks |
| Business Models of different parts of campus services |
|
|
| SURF |
|
|
| Business models with different "packages" for different needs with leasing of equipment | Lower the amount of different packages that we offer |
|
| Sikt |
|
|
|
|
|
|
|
|
|
Product management |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Security and compliance |
| Some experience with seeing the security not only by implementation in firewalls, but looking at security at the client and server levels |
|
|
| Sikt |
|
|
| Network sensors (IDS) from Sikt eduCSC where traffic north/south gets mirrored to the sensor. This to lessen the need for IDS functionality in the firewalls. | Closer collaboration with our security teams to get these two services closer together (Sikt eduCSC and Sikt CNaaS) |
|
| Sikt |
|
|
|
| Use of custom feeds from Sikt eduCSC to block known malware sources (MISP) |
|
| Sikt |
|
|
|
|
|
| Security/ZeroTrust | Sikt |
|
|
|
|
|
|
|
|
|
IoT and new applications |
| iotroam: authentication of IoT stuff on Wi-Fi | Service growth, identifiy user requirements | Stable service | International adoption of iotroam by providing the service or the software to other NRENs | SURF |
|
|
| iotnet: service development of a campus-wide covering IoT low powered (LoRaWAN) network | Working towards an operational service national wide | Operational service | Share knowledge, research advantages of international collaboration/standardization/roaming possibilities | SURF |
|
|
|
|
| Audio/Video (AV) and Multicast | Sikt |
| |
|
|
|
| IOT solutions like iotroam and iotnet | Sikt |
| |
|
|
|
|
|
|
|
|
Hybrid event and network support |
| NOC internal in place (24x7), field services by the institutes themselves, training by the NREN to the engineer at the institute |
|
| Sharing en enhancing NOC documentation and training stuff; training engineers | SUNET | SURF, SIKT, RENU |
|
| NOC is at the specialists internal | NOC internal |
| Sikt |
| |
|
| NOC is outsourced, 3rd line internal | Evaluate NOC |
|
| SURF |
|
|
|
|
|
|
|
| |
Training and competence development |
| Used Juniper All Access Pass for education of CNaaS engineers on Juniper products |
|
|
| Sikt |
|
|
|
|
|
|
|
|
|
We kindly ask each Steering Group member to fill in the survey for their respective NREN. During the September meeting, we will discuss which areas are most relevant to take forward. It is clear that some topics will be interesting but may require more resources to realise.
Our initial focus should be on identifying low-hanging fruits for collaboration, while at the same time using this mapping as a way to outline a roadmap for both short-term initiatives and longer-term potential collaborations.