On 28 Jul 2017, at 14:17, Ted Lemon wrote:
If you encounter bustage, you can switch to the legacy network.
The legacy network will have a different SSID. All laptops remember which SSIDs you have connected to successfully in the past. Thus, it is likely that if you encounter problems and have to switch to the example-ssid-legacy SSID, and you close your laptop to move to a new room and open it again, you'll be put back onto the ietf SSID.
The only way around this repeated problem is to *remove* the ietf SSID from the list of your trusted SSIDs. This is not only an additional step, but it is one that has effects on future IETF meetings.
Further, section 4.1 of the draft has no instructions for end users of various versions of various operating systems. The draft assumes that everyone attending an IETF meeting understands SLAAC and RA options and how they are set on their laptops: that assumption is demonstrably false, quite possibly for the majority of IETF attendees.
If we want to have a real dogfood test, the first step is documentation, not forced breakage for a significant portion of the attendees.
--Paul Hoffman