Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Simon Hobson <linux@thehobsons.co.uk> Mon, 17 July 2017 18:08 UTC

Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803B712ECC6 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 11:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 y2MfLq1u_A7X for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 11:08:38 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B9CB12EC1D for <v6ops@ietf.org>; Mon, 17 Jul 2017 11:08:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.137.111] (unknown [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id ABA201BC37 for <v6ops@ietf.org>; Mon, 17 Jul 2017 18:08:32 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <m1dXA9Y-0000ChC@stereo.hq.phicoh.net>
Date: Mon, 17 Jul 2017 19:08:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADC7A752-8025-4B71-8E65-080BAC59C02A@thehobsons.co.uk>
References: <CAFU7BARz_u92NweYkTizT2=q420sBRh11m9bqWO9+aexCi3ANA@mail.gmail.com> <2A639918-C6AC-44B8-8D66-5293EE13A7BD@consulintel.es> <CAFU7BASrxoroJVHwxFpwwBxCUC62_VZXsUGgfDOj6y+KVWk6tw@mail.gmail.com> <C510C095-B9AB-432F-A050-FD9CD640A6DE@consulintel.es> <CAFU7BAR413hwY_G2Cw-Ab+J158udPDLSFo==EN4LHjWb_YzD5Q@mail.gmail.com> <m1dX7DB-0000FzC@stereo.hq.phicoh.net> <CAFU7BAQ1ML2ARZKozJLFiEw43jmMObKwOpD4pGt9S3VKOwLE4w@mail.gmail.com> <m1dX7nO-0000GTC@stereo.hq.phicoh.net> <20170717152345.GV45648@Space.Net> <m1dX8Uf-0000FkC@stereo.hq.phicoh.net> <20170717172242.GW45648@Space.Net> <m1dXA9Y-0000ChC@stereo.hq.phicoh.net>
To: "v6ops@ietf.org Operations" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/cqseAoj5DhlgmrXTB278kKsjmZs>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 18:08:39 -0000

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> wrote:

>> But after 20 years of IPv6, it's really time to seriously work on killing
>> IPv4.  
> 
> In a world where most people have no access to IPv6. Where IPv6 deployment
> is just slightly more than a blip on the radar. 
> 
> Yeah, there it is very obvious that we should start killing IPv4 support.
> 
> Convincing people that IPv6 is a good idea is already hard enough. So now
> we tell them that they should really do 'IPv6-only' and break all unmodified
> IPv4 hosts. That should really help IPv6 adoption.

"Break all unmodified hosts ?"
I was under the impression that many unmodified hosts (and the software running on them) was capable of running on an IPv6 only network - but there are specific, notable exceptions (OpenVPN config specific, and MS Outlook an Mac are two that have been mentioned), and that the scale is not clearly known.
If there is an experiment that will allow some insight into the scale of the issue, and with a self selected group who are likely to be able to provide more meaningful feedback than "internet's broken") then it's useful to be done.

And when people talk of "kill IPv4", I don't get the impression that they mean to literally get rid of it any time soon. Before you can get rid of it, a lot has to happen - and already mentioned, if you don't start that process then it'll never happen.
You've raised a good point - many people don't have IPv6 - that's one area to be addressed, and a good way of addressing that is to show that it's here, it's working, and the ISPs responsible really need to extract digit from posterior and start providing it.

I see a parallel with the old walled gardens like AOL, back when they were dial up and not internet connected. Many thought this new fangled internet thing, with it's complicated "IP addresses", was something to be ignored. Remember what happened to them ? it didn't happen overnight - but bit by bit they "went internet". First it was with "gateways", and eventually native IP - right now we are still at the "gateways" stage with IPv6 adoption, with many still stuck in the IPv4 walled garden, while many of us have this new fangled IPv6.

But if we sit back and wait, then those IPv4 walled gardens will remain, and the argument will be "but you can't kill it off" forever. I doubt if IPv4 will ever truly disappear (just as I still have some old kit doing AppleTalk !) - but it will get to the point where end users having to have it will be few and far between, eventually.
But, as Laozi said, "a journey of a thousand miles begins with a single step". A lot of people seem afraid of taking a single step, let alone a journey.