Arguably if your work network doesn't work with IPv6, that's a problem
with your work network, not a problem with the IETF network. You
should be submitting a support request to your company's IT
department, not to the IETF.
On Thu, Nov 17, 2016 at 1:52 PM, Benson Schliesser
<bensons(_at_)queuefull(_dot_)net> wrote:
On Thu, Nov 17, 2016 at 10:34 AM, David Conrad
<drc(_at_)virtualized(_dot_)org> wrote:
I sort of like the idea of making the default IETF SSID IPv6 only, with
other SSIDs that support v4/dual stack. It would probably be an eye opening
experience for some.
Perhaps it would be eye opening for some. For a subset of those, perhaps it
would even cause them to do something helpful: write drafts, debug software,
fix their networks, harass their service providers and IT depts, etc. But
for others, it will merely be an inconvenience.
E.g., I imagine somebody not paying close attention to announcements on the
mailing list, showing up to a Monday morning meeting, connecting to the IETF
network, wondering why their employer's VPN isn't working, not getting
email, ... This experience is certainly not the end of the world for
anybody. But it may cause extra work for chairs, the NOC, et al.
It's not clear to me how we weigh the costs vs benefits. I think it would be
valuable to consider data from the NOC such as proportions of v6 / v4
traffic. But for now I'm a skeptic of intentionally breaking network
connectivity for attendees.
-Benson