Re: IPv4 outage at next IETF in Chicago

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 24 January 2017 23:43 UTC

Return-Path: <prvs=1197ee1ff8=jordi.palet@consulintel.es>
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 1C2071295A5 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 15:43:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 7H8-ar5hu5MJ for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 15:43:56 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFEFC12959C for <ietf@ietf.org>; Tue, 24 Jan 2017 15:43:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1485301431; x=1485906231; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=5DBLYob9s1NX5Rs3coTJ03pge OiMlOmREq2u/VSTbYs=; b=VhrBnw2jGp3ZprciBsj7K5m6K0UxronnnO/S6b4Sk 5rH5yokithesGsLl77HyD9yIAVpBweHuZKpGKxCYyfQBOfxaJR3uQk3d9jIjnSGS FBxDpRGJMJaxWs/4Df3tSwTBIYJlpCMj9nN2v+PoGoFQD/u0kDlDbo2u4Z9YgCNO CQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=IVcjSaia5RXioKtpUfsmfB67FgLuY2QCDMD9VJs4qnh3zt6w2Ci49ezFaVzL 97iVTmhw4LWs1mKlSpu5vFfPvbkecHOGtvfv93a94L4kD0YAjtCPiwlII z2lt6CbrBcGBWcF1MvQyNSrvN3mfYwheiZu4r5CEQYErUKYu7KC/V4=;
X-MDAV-Processed: mail.consulintel.es, Wed, 25 Jan 2017 00:43:51 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 25 Jan 2017 00:43:43 +0100
Received: from [172.20.62.10] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005351107.msg for <ietf@ietf.org>; Wed, 25 Jan 2017 00:43:43 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170124:md50005351107::CHUcp6mcojnLV/Zp:000094Kp
X-MDRemoteIP: 181.193.111.123
X-Return-Path: prvs=1197ee1ff8=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Tue, 24 Jan 2017 17:41:27 -0600
Subject: Re: IPv4 outage at next IETF in Chicago
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF <ietf@ietf.org>
Message-ID: <12DF90A8-164A-480F-9480-29C1D736C5F3@consulintel.es>
Thread-Topic: IPv4 outage at next IETF in Chicago
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <CAAiTEH_+ya3gdmC9Lhzgvrrk_--20MTvws0-oDaJ4EjJ7tEvng@mail.gmail.com>
In-Reply-To: <CAAiTEH_+ya3gdmC9Lhzgvrrk_--20MTvws0-oDaJ4EjJ7tEvng@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XiCOoRlooxZPHOGxumr-46RigM0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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:43:59 -0000

That’s why I already suggested a way that allow both, dual stack in the IETF LANs, and IPv6 only in the “access” (the link of the router to the LANs).

We can do this with 464XLAT, which has been tried massively in many cellular and residential customer networks.

This is a “more realistic” scenario about what each of us can find in their home networks in months/years from now. Many network and home networks will keep dual-stack, with private IPv4, but global IPv6, because many devices at home are and will be, IPv4 only for some time. You will not replace the IPv4-only devices immediately, right?

If anything fails, we need to know it.

Regards,
Jordi


-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Matthew Pounsett <matt@conundrum.com>
Responder a: <matt@conundrum.com>
Fecha: martes, 24 de enero de 2017, 17:23
Para: Franck Martin <franck@peachymango.org>
CC: IETF <ietf@ietf.org>
Asunto: Re: IPv4 outage at next IETF in Chicago

    
    
    On 24 January 2017 at 15:11, Franck Martin <franck@peachymango.org> wrote:
    
    
    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?
    
    
    
    
    
    If you wish to test that your networks are reachable from a v6-only environment, there is already a v6-only network you can use to test that.  Many of us require access to the entire Internet to do our jobs, however.
    
    
    
    
    
    





**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.