Re: IPv4 outage at next IETF in Chicago

JORDI PALET MARTINEZ <> Wed, 25 January 2017 03:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B0698129666 for <>; Tue, 24 Jan 2017 19:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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: (amavisd-new); dkim=pass (1024-bit key); domainkeys=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bC9Zw_vhY31I for <>; Tue, 24 Jan 2017 19:31:38 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5DE9812964C for <>; Tue, 24 Jan 2017 19:31:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; s=MDaemon; t=1485315094; x=1485919894; 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=lxZhScJVTyBnlOeMZa0mivWXa /JVjICRDgmxmtniFYE=; b=OTaOkNk+2T5890HHz9zPIZXzhFufx0M5XYSjK9Agf tXXi51jCH+ttT9AEIcDivKWdcmt3nzI89t0Iygb63ce29liF7icXgTJ1gAPi8ma6 ey0FCQmv0PbDgz/yuRoF1qoz/M/8uzvJuynugKVqXKBhBc/aK0sXpiP14kCKVX5k uE=
DomainKey-Signature: a=rsa-sha1; s=MDaemon;; c=simple; q=dns; h=from:message-id; b=C0GFO1QzAN+INbTsk16f/awBsMZHNorGb1KCpA9qrqLW2NMApAqfAUUC1yx6 EO73LJf4Lt8ZTU6GyZjUkHQETwsYb9AUj+RnmDpdbM4jaaWVGGnCb50R7 hc57I7djYpPH0x6xBTWx1szSJdlfHIRvnpGmEBVW3dsxj4kiA9yl6U=;
X-MDAV-Processed:, Wed, 25 Jan 2017 04:31:34 +0100
X-Spam-Processed:, Wed, 25 Jan 2017 04:31:28 +0100
Received: from [] by (MDaemon PRO v11.0.3) with ESMTP id md50005351199.msg for <>; Wed, 25 Jan 2017 04:31:28 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-HashCash: 1:20:170125:md50005351199::Ci0dUAdS87vSwzf7:00000dXV
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Tue, 24 Jan 2017 21:31:20 -0600
Subject: Re: IPv4 outage at next IETF in Chicago
To: IETF <>
Message-ID: <>
Thread-Topic: IPv4 outage at next IETF in Chicago
References: <> <> <WM!9d8566ee4a667cbd16edab2df707ef7a0c8c696ee92bca1ab194c80d7f9f38afca46538cbe422dcfd43306b1345f3435!> <> <> <WM!d42d3ceb3d1cd674dd9f1ad2a99fbed5e41e8de6ce258b70db511984b58d1e426445eb716e9fa13ee84ef542e91f73ed!> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Jan 2017 03:31:41 -0000


What I’m proposing will not involve installing the “client” part in the devices connecting to the IETF network.

The idea is the following:

Upstream provider – IETF router – NAT64/DNS64 – CLAT (can be a virtual machine) – IETF default SSID
                                                 |------------------------------ other IETF SSIDs

So I’m saying the IETF default SSID will behave as a “residential” LAN of the CLAT enabled “CPE”.


-----Mensaje original-----
De: ietf <> en nombre de Franck Martin <>
Responder a: <>
Fecha: martes, 24 de enero de 2017, 21:24
Para: Brian E Carpenter <>
Asunto: Re: IPv4 outage at next IETF in Chicago

    This is hardly to prove a point.
    It is to have an operational experience so that stuff gets fixed and standards get written to fix stuff.
    An IPv4 outage is radical, granted, may be it should be done during hackday on the weekend before IETF. May be it should not be done at all and instead the default network SSID:IETF to be NAT64, with an SSID:IETF-IPv4-only.
    May be NAT64 is not the right one, may be it is XLAT464? (NAT64/DNS64 does not require much client participation, XLAT464 does).
    May be it is way too short to have it in Chicago? Likely.
    May be it should be better planned. Certainly.
    We need a transition to IPv6-only, this go via dual stack, sure, but do we have to wait for the whole world to be IPv6 before we can deprecate IPv4? No, we need something that allows to have IPv6-only networks (enterprise, guest, customers,...) capable of talking to the legacy Internet. We also realize that the bottom line is: "dual stack=dual costs" and "dual stack=dual security issues". As the world progress, the need for NAT64 will go away...
    So, this is a very interesting discussion, as long we move towards some solution(s).
    What do you propose?
    ----- Original Message -----
    From: "Brian E Carpenter" <>
    To: "Franck Martin" <>
    Cc: "IETF" <>
    Sent: Tuesday, January 24, 2017 5:21:23 PM
    Subject: Re: IPv4 outage at next IETF in Chicago
    Franck, I try not to be religious about NAT, and I use NAT44 every day
    like most people. Also like most people, I experience occasional
    unexplained failures of web-based transactions. Whether they are due
    to a NAT garbage-collect or a load-balancer failure, I don't know,
    of course. But actually I am not deeply concerned about NAT64, although
    any failures that it generates would be very hard to identify. I am
    more concerned about IETF participants whose devices are not set up
    as dual stack nodes at all. They would be completely blocked. Yes,
    I know, such people should not exist, should be deeply ashamed, etc.
    But I don't see why we would cut them off to prove a point.
    On 25/01/2017 14:05, Franck Martin wrote:
    > ----- Original Message -----
    >> From: "Brian E Carpenter" <>
    >> To: "Franck Martin" <>rg>, "IETF" <>
    >> Sent: Tuesday, January 24, 2017 4:33:22 PM
    >> Subject: Re: IPv4 outage at next IETF in Chicago
    >> On 25/01/2017 12:11, Franck Martin wrote:
    >>> 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?
    >> That would be a good way of damaging IETF productivity for a few hours.
    > Do you have evidence of applications not running in a NAT64 environment? I'm interested to know them.
    >> And for what? Moving away from the mainstream coexistence mechanism (dual
    >> stack),
    >> to a mechanism known to be intrinsically defective (NAT). I don't see the point.
    > I fail to see how NAT is intrinsically defective, since it is used successfully by everyone...
    > Nevertheless, the goal here is to get the Internet designers (IETF) to have operational experience on what needs to be fixed.
    > When the IPv4 outage happened a few years back, it gave a serious impetus in getting IPv6 totally mainstream on many platforms.
    > IAB encourages IPv6:
    > However going IPv6-only can only be done in walled gardens. There still will be many environments with IPv4 only. A solution here is to move networks to NAT64, so you only need to support IPv4 at the edges...
    > Yes creating an outage for the sake of an outage is pointless, experience on what works and not work needs to be recorded.
    > May be the first step instead of doing an outage is to have as default a NAT64 network at IETF meetings and a dual stack network for the people that experience issues.

IPv4 is over
Are you ready for the new Internet ?
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.