IPv4 outage at next IETF in Chicago

Franck Martin <franck@peachymango.org> Tue, 24 January 2017 23:11 UTC

Return-Path: <franck@peachymango.org>
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 A6BDA129529 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 15:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 (1024-bit key) header.d=peachymango.org
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 dW20npzZcQc0 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 15:11:27 -0800 (PST)
Received: from zmcc-5-mx.zmailcloud.com (zmcc-5-mx.zmailcloud.com [192.198.93.228]) (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 461FF129517 for <ietf@ietf.org>; Tue, 24 Jan 2017 15:11:27 -0800 (PST)
Received: from zmcc-5-mta-1.zmailcloud.com (127.37.197.104.bc.googleusercontent.com [104.197.37.127]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zmcc-5-mx.zmailcloud.com (Postfix) with ESMTPS id 4B88F52027E for <ietf@ietf.org>; Tue, 24 Jan 2017 18:11:26 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 00E53C18E5 for <ietf@ietf.org>; Tue, 24 Jan 2017 17:11:26 -0600 (CST)
Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 98YfVkxVLhE9 for <ietf@ietf.org>; Tue, 24 Jan 2017 17:11:25 -0600 (CST)
Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 7C67AC18C9 for <ietf@ietf.org>; Tue, 24 Jan 2017 17:11:25 -0600 (CST)
DKIM-Filter: OpenDKIM Filter v2.9.2 zmcc-5-mta-1.zmailcloud.com 7C67AC18C9
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peachymango.org; s=61F775A4-4A7F-11E4-A6BB-61E3068E35F6; t=1485299485; bh=LNIjaNxYuhuLaXpq8YYdgMTeWDCDsPnnhWptoAVsSc8=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; b=bp7y1298fSWRzBqREHSBPxqRA4qKTVCf0ZI2BZtmigDAhCmfPxoYkV3NNvNc5Ljmx GhHoLlv8v0CH7kSxSXgP8Jdiv7pFn8KDikRAiZ8uUld/IQPdS72DN+QANbRhM0spzz Yjb3xuZsvPtVqDjzV3WSrKhVf+/lEm4QA2fQEOW0=
X-Virus-Scanned: amavisd-new at zmcc-5-mta-1.zmailcloud.com
Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id B8_UuwKPC3Hu for <ietf@ietf.org>; Tue, 24 Jan 2017 17:11:25 -0600 (CST)
Received: from zmcc-5-mailbox-1.zmailcloud.com (zmcc-5-mailbox-1.zmailcloud.com [10.240.0.12]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 6627DC18AE for <ietf@ietf.org>; Tue, 24 Jan 2017 17:11:25 -0600 (CST)
Date: Tue, 24 Jan 2017 17:11:25 -0600 (CST)
From: Franck Martin <franck@peachymango.org>
To: IETF <ietf@ietf.org>
Message-ID: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org>
Subject: IPv4 outage at next IETF in Chicago
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_114000857_1256834273.1485299485194"
X-Mailer: Zimbra 8.6.0_GA_1194 (ZimbraWebClient - FF50 (Mac)/8.6.0_GA_1194)
Thread-Topic: IPv4 outage at next IETF in Chicago
Thread-Index: tFn7rui8srlCpWmJGy0H65AnI0Vevg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3EB47Cf4w76URHFqT_6FWw2eq2Y>
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: Tue, 24 Jan 2017 23:11:28 -0000

I think it is time to move to the next level of IPv6 deployment. 

Ideally the IETF WiFi network should now only provide the following 2 networks: 
1)IPv6-only 
2)IPv6-only with NAT64 

The later should be the default network. 

However you would say, well some stuff will break, some non technical people will use the IETF network and may have a bad experience, etc... 

So to be conservative but at the same time futurist and like it was done a few years back, why not create again an IPv4 outage of a few hours where the above 2 networks would be the only networks available? 

Depending on results, this outage could be expanded to a full day at the following meeting, until the IPv4 network is totally removed from the WiFi?