Introduction 
The workshop gathered several NRENs to discuss common challenges and opportunities in monitoring, network operations, NAC, and IoT. There was strong interest in shared solutions and practical collaboration, especially around Argus, NAV, NOC practices, and iotroam. 

Key outcomes 

Monitoring (Argus / NAV) 
- Strong interest in Argus for log aggregation. 
- Requests for demos and better setup documentation. 
- Need for better support for “glue services”, especially event correlation across systems (e.g. Mist, NAV, Aruba UXI). 
- Surf noted that SNMP for stats polling does not scale for some use cases and recommended streaming telemetry. A number of open source telemetry collectors already exist, so it would likely make more sense to integrate an existing one with NAV, than to implement another collector from scratch. 

NOC 
- Large differences in NOC models across NRENs. 
- Key success factors: 
  - Good documentation 
  - Standardization 
  - Automation 
  - Effective monitoring 
  - Low alarm noise 
  - Linking procedures directly from alarms 
- Surf’s Network Dashboard (multi-source KPI view) raised strong interest. 

NAC 
- Clear need for NAC across several NRENs. 
- Large variation in the use of NAC at different NRENs.  
- Challenges: 
  - High cost of ClearPass and ISE 
  - Weak usability of FreeRADIUS 
  - Important with a way for users to register their devices themselves.  
- Interest in cooperation on RADIUS as a Service (RaaS) and best practices 

IoT / iotroam 
- Very strong interest. 
  - CSC is in process with Surf for a pilot 
  - Sikt has been contacted by several Norwegian customers to know more about iotroam. 
- Seen as a potential national service. 
- Business model not yet clear 
  - As a part of the cost for the CNaaS service? 
  - As a part of the cost for eduroam? 
  - As a standalone subscription? 
 
- Interest in pilots and VM-based deployment. 
- OpenSAML / federated login support coming soon. 
- Costs mainly for extended functionality. 

Overall 
- High engagement and constructive discussions. 
- Clear value in joint development and shared services (Argus, iotroam). 
- Collaboration requires prioritization and concrete commitments. 

Way forward 

Planned actions 
- Argus / NAV: joint demos and alignment between Sikt and Surf. Owner: Sikt 
- IoT / iotroam: demo and discussion of deployment model and pilots. Owner: Surf 
- NOC: session on organization, tools and best practices. Owner: Sunet 

Concrete objective 
The shared goal is to achieve tangible, practical collaboration results (e.g. pilots, shared tooling, or joint processes) that can be presented at the TNC BOF meeting in June. 

This requires clear ownership, allocation of time and resources, and a commitment to move from discussion to implementation. 

Action points / Next steps

1. Argus demo (log aggregation)

Description: Technical demo of Argus, including architecture, main use cases, and operational experience.
Owner: Sikt
Participants: Interested NRENs
Proposed timeframe: Week 9–10

1. NAV + telemetry demo

Description:

• Demo of current NAV setup
• Overview of possible streaming telemetry solutions and integration with NAV
• Discussion of “glue services” and cross-system event correlation

Owner: Sikt / Surf (joint)
Proposed timeframe: Week 11–12

1. iotroam demo and pilot discussion

Description:

• Functional demo of iotroam
• Walk-through of VM-based deployment model
• Discussion of pilot setup and possible operational and business models

Owner: Surf
Participants: Sikt, CSC, other interested NRENs
Proposed timeframe: Week 13–14

1. NOC session – organisation and best practices

Description: Experience sharing on:

• NOC organisation models
• Tools and platforms
• Alarm handling and noise reduction
• Procedures and documentation
• KPI and dashboard usage

Owner: Sunet
Proposed timeframe: Week 15–16

1. Consolidation towards TNC BOF

Description:

• Select concrete outcomes to present at TNC BOF
• Confirm ownership and delivery plans
• Agree on 2–3 tangible deliverables (pilots, tools, documentation, or processes)

Owner: SIG-CNaaS coordination / Sikt
Proposed timeframe: Week 18–19

If you want, I can also provide this as:

• a compact table version, or
• aligned to the exact TNC dates, or
• adapted to a more formal project-management style (e.g. with milestones).