Re: IPv4 outage at next IETF in Chicago

joel jaeggli <joelja@bogus.com> Wed, 25 January 2017 19:59 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7574129B90 for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.099
X-Spam-Level:
X-Spam-Status: No, score=-10.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAvSIuj3anrQ for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:59:05 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBF54129B8C for <ietf@ietf.org>; Wed, 25 Jan 2017 11:59:05 -0800 (PST)
Received: from mbp-4.local ([IPv6:2601:647:4201:9e61:e47d:faae:b30b:13ab]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v0PJwtpo092146 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 25 Jan 2017 19:58:55 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4201:9e61:e47d:faae:b30b:13ab] claimed to be mbp-4.local
Subject: Re: IPv4 outage at next IETF in Chicago
To: Franck Martin <franck@peachymango.org>, Matthew Pounsett <matt@conundrum.com>, paul.hoffman@vpnc.org
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <20170124235626.042F960836B0@rock.dv.isc.org> <158901d276b3$387d6050$a97820f0$@huitema.net> <CAAiTEH_4WgdmMZQm5nbFbvweibkZ0DAo2feN91zftspD4EbWjg@mail.gmail.com> <WM!572ad9a6ae19416c99bd6357d98a5df59a81b46a887701f7fe5b0c3faf7d157d9ed99107720fab7bcb2711df4ea4ce8c!@mailstronghold-3.zmailcloud.com> <1350087674.115436952.1485371218219.JavaMail.zimbra@peachymango.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <c6e8af52-dd97-0e61-12cb-59f685065153@bogus.com>
Date: Wed, 25 Jan 2017 11:58:54 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <1350087674.115436952.1485371218219.JavaMail.zimbra@peachymango.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AmG738Wfu5RKLrLcxbQRONHfcOFxSveTD"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RXrqXaYiwoYix0ayhH3ZdWwDKY0>
Cc: Christian Huitema <huitema@huitema.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 19:59:17 -0000

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... ;)
>