In message <4231B9DB(_dot_)70003(_at_)zurich(_dot_)ibm(_dot_)com>, Brian E
Carpenter writes:
Jordi, I thought that Jim Martin's message under subject
"IETF62 Wireless Network Update" had already explained
what was happening (and IPv6 was a victim of those
circumstances). Of course this was very annoying and nobody
wants to see it happen again.
In my experience the IPv4 network was working *most* of the time
after Monday, but there were roaming glitches. And if you
unintentionally associated with the hotel network, life became
more complicated.
It's also not a new problem; we've had major wireless network meltdowns
at many recent IETFs. (I'm not at this IETF; I've been at every other
one for the last 10 years, and it's an ongoing problem: running a
large-scale wireless net with no time for stress-testing is *hard*.)
--Prof. Steven M. Bellovin, http://www.cs.columbia.edu/~smb
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf