IETF Logo Mail Archive

Re: IPv4 outage at next IETF in Chicago

Michal Krsek <michal@krsek.cz> Wed, 25 January 2017 19:14 UTC

Return-Path: <michal@krsek.cz>
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 53113129B0D for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=krsek-cz.20150623.gappssmtp.com
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 7SUVbtyF6jtK for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:14:06 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AB0C129AF1 for <ietf@ietf.org>; Wed, 25 Jan 2017 11:14:06 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id r126so40953888wmr.0 for <ietf@ietf.org>; Wed, 25 Jan 2017 11:14:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krsek-cz.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=wyw27raSVGrIcnqKBGfJzBbzjpmPvDUPnrWyM65Jejc=; b=bNxWEKQ6Sms5dD3bQBoUsexF9+/sGtzUMz+RRVFEH1eD1ZoAPCplL59srT0F9t/WD8 xIrdKF/JwfQgtGx96WOr1jPoH5CEQjTFUE1/c39PJ2EpPQfBIknGYl7uwJwhjP6ZMPrv B0tqEkew+b9J/2MakYepE3W76k/HU5eUNMbyVpF8+zeV2HAg0B+cS9WSoc+YUQdxRIRA SIPH9wVVuonwa9NTxrfHRVIQYtw8HQf1rY/OVU8T8wNq3rE4AIuebxNXyvEDQoMEUgNo iTA8kfKXQ5rYL8N5C+r6NAomsYKQBneWcjvomvgTiBu7lkmlsUeoxuGwkrbpl4g5SzPx GKiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=wyw27raSVGrIcnqKBGfJzBbzjpmPvDUPnrWyM65Jejc=; b=G1Ux6LKPJJ9XsZ7EKUE2UePiG5qrJ8Uh7kuRMTNmSUcd3pHLs7yzVSnELF2xjT6/5o s0iH0Qprr7z+EQnw5yEwq8l9hDi1egcpnVyBsPuKw+OPBFw+vEC5gypSSbUqiG2kILjW i4CWpCSz6MZbDi4rNJtK2z/+01d9FKUlaVoQlEbXidXmiZ2jV5f9D4yrjI4m1ghACrpz g9sygFw1C10jnzgSl73fu0ZAv98/fxLT3tJVmd0SZybfIY91kdsAAQzOTZx462ruRj0x 8xwFKxiM6J8bnpHsLvuGCY3Bqs09yEWfLCW5BMFOAk6lyPggVENJSRdjogpc1RmAe0EV dcGQ==
X-Gm-Message-State: AIkVDXK6Rpzuq296q9fg68wNrVIS/vgc7NJvNNtRHE8Q5he98XY6bovwFT0L3WwDCRC4tQ==
X-Received: by 10.28.227.133 with SMTP id a127mr22481849wmh.104.1485371644382; Wed, 25 Jan 2017 11:14:04 -0800 (PST)
Received: from [192.168.100.132] (ip-89-103-97-76.net.upcbroadband.cz. [89.103.97.76]) by smtp.googlemail.com with ESMTPSA id e72sm10504183wma.16.2017.01.25.11.14.03 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Jan 2017 11:14:03 -0800 (PST)
Subject: Re: IPv4 outage at next IETF in Chicago
To: ietf@ietf.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: Michal Krsek <michal@krsek.cz>
Message-ID: <b30cb454-f35a-f5d4-01ec-9d4a3d3b494f@krsek.cz>
Date: Wed, 25 Jan 2017 20:14:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; 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/alternative; boundary="------------1B55A79514E08932005CA263"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WZnDb9egx3dHVs0guGA7xfvRNvI>
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:14:08 -0000

Hi Franck,


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

as Randy wrote already, various SSIDs with various v6 setups are 
deployed regularly for years.

                 Michal

v2.3.2 | Report a Bug | By Email