Re: IPv4 outage at next IETF in Chicago

[joel jaeggli <[e-mail]>]

On 1/25/17 11:06 AM, Franck Martin wrote:
> Besides all the passive aggressiveness of some responses, I like what
> Paul Hoffman proposed and I would be game to help run this... However
> I don't have control on the IETF network. How would I go about
> requesting an SSID for IPv6-only with NAT64/DNS64 is setup?

from the ietf97 all network information and roughly the previous 20 or
so ietf meetings with variations since which ssids provide what and the
names of the primary networks have changed over time:

...

Here’s a quick summary of the network layout: || SSID || Description ||
Encrypted || Frequencies || IP Versions || || ietf || Our default
network || yes || 5Ghz only || v4 and v6 || || ietf-legacy || For legacy
and unencrypted use || no || 2.4 and 5Ghz || v4 and v6 || ||
ietf-2.4ONLY || An encrypted network for 2.4Ghz users || yes || 2.4Ghz
only || v4 and v6 || || ietf-v6ONLY || For users wanting pure IPv6 ||
yes || 5Ghz only || v6 only || || ietf-nat64 || IPv6 stack with NAT64 ||
yes || 5Ghz only || v6 with NAT64 & DNS64 || || eduroam || educational
users || yes || 2.4 and 5Ghz || v4 and v6 || All networks marked as
encrypted will offer layer 2 security. This is done using WPA2
enterprise with 802.1X (PEAP or TTLS) authentication and AES encryption.
As usual, we are all using the same credentials (user “ietf”, password
“ietf”), yet each user will get unique session encryption keys. Our
802.1x authentication servers use a certificate that you can install by
going to this page: [https://802.1x-config.org/?idp=137&profile=60] or
alternatively, check them yourself here:
[https://tickets.meeting.ietf.org/wiki/CertCheck] ...


> I would take care of running a jabber channel, encourage people to
> switch and test, create some forms to collect experience and report back.
>
> I would even be willing to offer a real vintage LinkedIn IPv6 polo
> shirt as prize... ;)
>