Well, since you had a reply-to to this unmoderated list :-)...
This is what I get (Windows 7):
Radius Server: services.meeting.ietf.org
Root CA: Starfield Class 2 Certification Authority
The server "services.meeting.ietf.org" presented a valid certificate issued by
"Starfield Class 2 Certification Authority", but
"Starfield Class 2 Certification Authority" is not configured as a valid trust
anchor for this profile. Further, the server
"services.meeting.ietf.org" is not configured as a valid NPS server to connect
to for this profile.
Regards
Brian
On 25/07/2014 08:38, IETF Chair wrote:
While many of us have been working on improved transport and other security
mechanisms, I’d like to observe that the default wireless network we are
using here in Toronto is unencrypted over the air. I am not sure how good
practice that is. And it is probably not a good example either.
Could we consider making 802.1X the default, for instance, starting in
Honolulu meeting? At least in the sense of the ietf SSID providing security
and perhaps ietf-nosec providing the current behaviour?
It would also be helpful if you try it now. The two SSIDs, ietf.1x and
ietf-a.1x are available now, we recommend you use them and we would
appreciate your reporting any problems. The user ID and password are both
'ietf' (sans quotes).
Jari Arkko
IETF Chair
(with input from some NOC people)