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

Fernando Gont <fgont@si6networks.com> Fri, 09 June 2017 17:27 UTC

Return-Path: <fgont@si6networks.com>
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 7FB99129411 for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 10:27:16 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 v1Y54evjOtvl for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 10:27:13 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28B241293F4 for <ipv6@ietf.org>; Fri, 9 Jun 2017 10:27:12 -0700 (PDT)
Received: from [192.168.0.185] (unknown [105.50.131.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 1EE7583123; Fri, 9 Jun 2017 19:27:27 +0200 (CEST)
Subject: Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
To: Mark Andrews <marka@isc.org>, Simon Hobson <linux@thehobsons.co.uk>
Cc: 6man WG <ipv6@ietf.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>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <6d1acd5d-9d45-9e2a-4ac9-5e0cb9787b13@si6networks.com>
Date: Fri, 09 Jun 2017 20:26:41 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20170609125852.29C107B6EB8F@rock.dv.isc.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cIWlKsUaGZjdOCLcTZflvd6sMNE>
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 17:27:16 -0000

On 06/09/2017 03:58 PM, Mark Andrews wrote:
> 
> In message <BB84AB04-ABAC-4DEB-B69B-92EA5A904967@thehobsons.co.uk>, Simon Hobso
> n writes:
>> Mark Andrews <marka@isc.org> wrote:
>>
>>>> My very limited experience with ISP provided IPv6 is that so far, what
>>>> I've seen is sensible allocations (eg a /56 for a home user). If the
>>>> majority do the right thing, then the exceptions can stand out and get a
>>>> reputation for "broken". I know in the real world there will be cases
>>>> where there's an effective monopoly (for some group of users) allowing
>>>> the ISP to do what they want, but that's not an excuse to just throw in
>>>> the towel and give the rest carte blanch.
>>>
>>> And 256 prefixes very quickly become too few as we develop new
>>> technologies to take advantage that you can get prefixes easily.
>>> ISP's have been short sighted here.  The IETF started out saying
>>> /48 to give every site enough prefixes that they shouldn't have to
>>> go back and get more except in exceptional circumstances.
>>
>> I disagree - at least for home users.
>> Most home users simply unpack the ISP router, plug it in, and connect their d
>> evices to it.
>> They plug in their webcams https://www.theregister.co.uk/2017/06/08/whitebox_
>> webcam_scatters_vulnerabilities_through_multiple_oems/
>> plug in their "smart" lightbulbs https://www.theregister.co.uk/2016/07/27/osr
>> am_smart_lightbulbs/
>> plug in their "smart" doorbell & locks https://www.theregister.co.uk/2016/01/
>> 12/ring_doorbell_reveals_wifi_credentials/
>> http://www.theregister.co.uk/2016/08/08/using_a_smart_bluetooth_lock_to_prote
>> ct_your_valuables_youre_an_idiot/
>> connect their kids toys http://www.theregister.co.uk/2015/02/19/hello_barbie/
>>  and their own "toys" http://www.theregister.co.uk/2016/08/07/your_sec_toy_is
>> _spying_on_you_hackers_crack_our_plastic_pals/
>>
>> I could go on (kettles, fridges, bathroom scales, ... all with reported secur
>> ity flaws), but I think you get the idea !
>> All of this will be on one network, one subnet/prefix. The majority of users 
>> (some small rounding error below 100%) will have no idea at all about network
>> ing, they won't have any clue about setting up multiple networks - and the wa
>> y much of the kit works, it won't work anyway if the device isn't on the same
>>  network/subnet/prefix and the users phone/tablet.
> 
> Just because you are not used to home routers that configure multiple
> subnets doesn't mean they don't exist.
> 
>> I recall a few years ago visiting my alma mater and found that ethernet
>> ports  had appeared in the rooms. When I plugged into one, I could see
>> all the security cameras etc were on the same segment and even the same
>> subnet ! If a university college can't get simple things like this right,
>> what makes you think  home users will do any better ?
> 
> 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.
> 
>> As I sit here (as part of that rounding error of users), to be frank, I
>> am struggling to think what I could (practically) use 10 separate networks
>> for, let alone 100 or 200 or 256 !
> 
> 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.

(you || me || we) != users


network_knowledge(users) == NULL

(and that's the way it should be)


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492