Re: IPv4 outage at next IETF in Chicago

John C Klensin <john-ietf@jck.com> Wed, 25 January 2017 14:05 UTC

Return-Path: <john-ietf@jck.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 23682129955 for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 06:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 SvPlfy5qtpMw for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 06:05:53 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6771129953 for <ietf@ietf.org>; Wed, 25 Jan 2017 06:05:53 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cWOCt-000Gfb-H9; Wed, 25 Jan 2017 09:05:51 -0500
Date: Wed, 25 Jan 2017 09:05:45 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Franck Martin <franck@peachymango.org>, IETF <ietf@ietf.org>
Subject: Re: IPv4 outage at next IETF in Chicago
Message-ID: <5ECECBD0342DFE1DA15CFE63@PSB>
In-Reply-To: <fc6770df-850b-a4b4-de00-f20cc69b4944@gmail.com>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <fc6770df-850b-a4b4-de00-f20cc69b4944@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yfkaSmSpl2fJ-vl4QYu0HKZWHx0>
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 14:05:55 -0000

+1
And add anyone who has been strongly advocating this, and other
"if you are not running IPv6 exclusively, we should punish you"
strategies, to that list.

    john


--On Wednesday, January 25, 2017 08:53 +0000 Stewart Bryant
<stewart.bryant@gmail.com> wrote:

>> 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?
> 
> How about those that designed IPv6 and their ADs subject
> themselves to this regime and report to the rest of us how
> they got on?