June 15
Time (Helsinki Time)
Speaker(s)
Talk Title
Building Resilient Public Safety Connectivity
In this session, Mark will draw on his leadership of the WBA’s Mission Critical & Emergency Services Program to explore how Wi-Fi 6/7 and OpenRoaming can extend resilient, standards-based emergency communications into indoor venues, dense public spaces, and other environments where cellular alone falls short. The talk will address emergency calling over Wi-Fi, National Security and Emergency Preparedness (NSEP) services, and the framework the WBA has developed to help network operators, first responders, and public safety agencies rely on Wi-Fi alongside cellular when it matters most.
Expand Your Awareness RADIUS
Using RADIUS to improve network situational awareness
Most network administrators view RADIUS primarily as a gatekeeper—the “Yes/No” checkpoint for network entry. However, beneath the surface of simple authentication lies a massive, often ignored stream of real-time telemetry. Every access request and accounting packet contains critical metadata about the “who, what, where, and when” of your environment.
tail -f radiusd.log: Let’s AI Do It
A look at using AI for RADIUS troubleshooting
- What is an Agentic AI?
- Some different applications of AI.
- AI and Agents specific to troubleshooting, using RADIUS as an example.
You don't know RADIUS
You think you know RADIUS? This talk explains why your mental model of RADIUS is likely wrong. It then explains the correct mental model, and how this deeper understanding of RADIUS lets you solve problems more quickly, and with less frustration.
RADIUS is dead, Long live RADIUS
What’s old is new again. RADIUS has been declared obsolete many times over the years, but it continues to be a widely used protocol in industry. The evolution of RADIUS has now moved to the cloud where RadSec is required to secure communications. New authentication use cases have evolved that are becoming widespread through the industry using RadSec. What does the industry look like in the future of the protocol facing new challenges with quantum computing, cloud computing, and its long history of use to dynamically secure networks around the world? Hear directly from a commercial product manager what is being driven by customer demands to use RADIUS in customer networks today and tomorrow.
Challenges of running a large eduroam infrastructure
Running the second-busiest eduroam infrastructure in Europe has its challenges – policy, structure, growth. How to design the future as relentless growth and changes in the protocol landscape force a rethink of the status quo.
Deploying RADIUS at Carrier Grade Scale
In today’s demanding world of Passpoint and high-density authentication requirements, just bringing up a RADIUS server is simply not enough. GlobalReach Technology uses RADIUS to authenticate millions of user sessions everyday across a wide range of verticals where reliability and scalability are key to ensuring the best user experience. We’ll take a look at the how our highly-available, globally distributed, auto-scaling infrastructure delivers that service.
When in eduroam: site data from Internet2’s perspective
As the US roaming operator, Internet2 has collected significant data on service operation. As a decentralized community project, eduroam provides value to sites and users but also requires investment. What does service data reveal about sites that operate successfully, what can eduroam administrators do to raise their sites’ profile, and why does it matter to everyone, even those who don’t use eduroam?
The Importance of RadSec post-BlastRADIUS
Today RADIUS is authenticating every device on your network over UDP, in cleartext, with a shared secret. BlastRADIUS exposes this though a series of exploits on RADIUS attributes. RadSec (RFC 6614) fixes this by using RADIUS over TLS with mutual certificate authentication, but it’s chronically under deployed. This talk covers what RadSec actually changes at the packet level, and why it’s critical to deploy in the face of vulnerabilities like BlastRADIUS.
RADIUS Service Responsiveness Advisory Mechanism
This proposal introduces a RADIUS Service Responsiveness Advisory mechanism that enables a RADIUS server to signal clients when expected response times are elevated or service responsiveness is degraded. The cause may be server overload, slow identity-store lookups, backend dependency latency, maintenance, or other processing delays. The mechanism uses advisory attributes piggybacked on normal RADIUS responses and, optionally, a server-initiated notification message. Suggested client actions include preferring an alternate RADIUS server, increasing request timeouts, reducing retry frequency, and lowering interim accounting update frequency for a bounded period. Each advisory includes scope, lifetime, and optional load, latency, or reason information, while the client retains local policy control over whether and how to apply the recommendations.