Hi,
3580 says Called-Station-Id SHOULD include the SSID. Most APs do
include the SSID.
s/Most/Some
There's a painful variety in what comes inside Calling-Station-Id, which
is *very* unfortunate. A set of RADIUS attributes to convey things like
the SSID in a proper place would be very handy (IEEE 802.11 attributes
draft in radext!).
And a FIXED syntax about MAC addresses in Calling-Station-Id, too. The
"SHOULD" canonical form that you both quoted isn't honoured by many.
Greetings,
Stefan Winter
However, SSIDs are *likely* to be unique within a roamin
consortium. This is because the parties talk to each other, and can
complain when the SSIDs are unknown, or re-used.
What parties? The BSSs? Why?
The parties in a roaming consortium talk to each other.
There are mitigating circumstances. AAA relationships leverage trust.
Continued trust depends on the parties continuing to meet expectations.
Lying about SSIDs violates trust.
But fraud doesn't?
Yes, fraud violates trust. My original post included an example of
fraud, stated why this was bad, and how channel bindings could help.
Alan DeKok.
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu
--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la
Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg
Tel: +352 424409 1
Fax: +352 422473
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu
