Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)

Mark Andrews <marka@isc.org> Fri, 09 June 2017 22:10 UTC

Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C725B126DCA for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 15:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 YcNcjdFhbpeh for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 15:10:37 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 918001252BA for <ipv6@ietf.org>; Fri, 9 Jun 2017 15:10:37 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 244A5349315; Fri, 9 Jun 2017 22:10:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 12082160044; Fri, 9 Jun 2017 22:10:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E671C16006D; Fri, 9 Jun 2017 22:10:33 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id aJmSCs_AQqyW; Fri, 9 Jun 2017 22:10:33 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 2B2D9160044; Fri, 9 Jun 2017 22:10:33 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id F3F247B70921; Sat, 10 Jun 2017 08:10:29 +1000 (AEST)
To: Simon Hobson <linux@thehobsons.co.uk>
Cc: 6man WG <ipv6@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <CAO42Z2wp72j-yOsR8C=iqS+dX14wLwthAtOTvD5ugj_NQ=NQag@mail.gmail.com> <8be34ef8-557f-652e-0d2f-f1a1e008bffd@gmail.com> <alpine.DEB.2.02.1706050827290.17963@uplift.swm.pp.se> <E2B77C58-B235-49D6-8130-0B41BE55899C@google.com> <CAAedzxrkbywKMmUaZ6-OCunXe1sw=q3+TNz278xZDmdsQm3xaw@mail.gmail.com> <93C6138E-A2EE-4005-8C16-05E2A2DEA661@google.com> <CAKD1Yr3+pHFhCwoL4vbQLDQ3PNGpijci8c7eZM=Gb0oTy9C0XA@mail.gmail.com> <8678F73D-2CCD-4781-9947-8C07182DFAF4@google.com> <EF9AC09C-5262-4DFB-AA4D-AE95EF81293C@gmail.com> <CB328974-E401-4B62-A408-1814183E0010@google.com> <8C792BA9-3FBA-46F3-9CBE-E82E4B93BEFC@google.com> <CAD6AjGSvaAGydOjZ-LYA8=DR2pOjmUrYAGN0kVdC2aKb3jvx_A@mail.gmail.com> <A3E25B71-9EC6-4E1B-91BC-FE36388676CB@google.com> <73A42828-9F55-4B01-9C00-608221B66EA3@gmail.com> <9B812DC3-E06A-4FB6-B071-BF66F96C8E19@thehobsons.co.uk> <20170609011106.22E967B64301@rock.dv.isc.org> <BB84AB04-ABAC-4DEB-B69B-92EA5A904967@thehobsons.co.uk> <20170609125852.29C107B6EB8F@rock.dv.isc.org> <6d1 acd5d-9d45-9e2a-4ac9-5e0cb9787b13@si6networks.com> <E2460C65-6237-424B-BDBC-29378C27F3A0@thehobsons.co.uk>
Subject: Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
In-reply-to: Your message of "Fri, 09 Jun 2017 21:55:49 +0100." <E2460C65-6237-424B-BDBC-29378C27F3A0@thehobsons.co.uk>
Date: Sat, 10 Jun 2017 08:10:29 +1000
Message-Id: <20170609221029.F3F247B70921@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Mra5OzVoV4k_x4BWOBtfEjX9Lc4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jun 2017 22:10:40 -0000

In message <E2460C65-6237-424B-BDBC-29378C27F3A0@thehobsons.co.uk>, Simon Hobso
n writes:
> Fernando Gont <fgont@si6networks.com> wrote:
> 
> > On 06/09/2017 03:58 PM, Mark Andrews wrote:
> >> Just because you are not used to home routers that configure multiple
> >> subnets doesn't mean they don't exist.
> 
> >> Because we will ship routers that do multiple subnets by default
> >> because that is what is needed to deal with situations like you
> >> describe above.
>
> And conversely, just because they exists doesn't mean that any ISP will
> ship them - or ship them configured to anything more than a basic single
> network.
>
> Besides, for this to work properly it's going to require VLANs and
> multiple wireless SSIDs unless you limit the network to the ports on the
> router. Good luck getting that to work with the average user.

People can handle multiple SSIDs quite easily.  We have had routers
shipping with 2 SSIDs for many years now. Usually the second one in
labeled "Something Guest".

> >> Uses will come up.  I use 3 subnets today for the home.  I would
> >> expect that I'll use more in the future.  Once more than one becomes
> >> common people will design stuff that can make use of additional
> >> subnets.
>
> I can see uses for about 3 or 4 segments - note, segments rather than
> subnets! You are not clear whether you are talking about multiple
> segments or a single network with multiple subnets. If it's the latter
> then it adds almost zero security, if the former than it's beyond the
> average user to deal with.

The home user is quite capable of doing multiple segments.  It
really isn't hard.

Have a couple of cars that each do PD requests for a couple of /64s
each when they arrive home as they connect over WiFi rather than
using LTE possibly using a distinct WiFi SSID in the garage (another
/64). The LTE border router in the car becomes a interior router
when it connects to the WiFi.  This is really no different to coming
home with your mobile phone except you are connecting multiple
subnets rather than individual addresses.

What other equipement will request /64s as it comes into range or
just request /64s when it connects?  I don't know yet but I do know
it will happen.  256 subnets is going to look very small when that
happens.

> > (you || me || we) != users
> > 
> > network_knowledge(users) == NULL
> 
> Thanks - you've expressed it better than I would have.

Actually we are all users.  Adding WEP passwords was once "too hard"
for the ordinary user.  There used to be a dozen parameters presented
to users of WiFi networks.  Now you choose from a simple list of
SSIDs.

Anything we do today will be common in a few years time.

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org