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

"Leddy, John" <John_Leddy@comcast.com> Fri, 09 June 2017 10:10 UTC

Return-Path: <John_Leddy@comcast.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 B77D6129455 for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 03:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7hDiKF1pK2lY for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 03:10:02 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (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 813961201F8 for <ipv6@ietf.org>; Fri, 9 Jun 2017 03:10:02 -0700 (PDT)
X-AuditID: 60721c4c-813ff7000000211d-79-593a73f78ebe
Received: from VAADCEX43.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id D7.33.08477.7F37A395; Fri, 9 Jun 2017 06:10:01 -0400 (EDT)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX43.cable.comcast.com (147.191.103.220) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 9 Jun 2017 06:09:58 -0400
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Fri, 9 Jun 2017 06:09:57 -0400
From: "Leddy, John" <John_Leddy@comcast.com>
To: Simon Hobson <linux@thehobsons.co.uk>, 6man WG <ipv6@ietf.org>
Subject: Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
Thread-Topic: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
Thread-Index: AQHS4Qdfh/nIwD5xZ0m2+eOfSnT1nKIcTwmA
Date: Fri, 09 Jun 2017 10:09:57 +0000
Message-ID: <CC6F3DE5-29B9-42D6-ACAD-8D4828AF79F3@cable.comcast.com>
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>
In-Reply-To: <BB84AB04-ABAC-4DEB-B69B-92EA5A904967@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [68.87.29.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <235513791818E0498B881C4002EA1555@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA12Uf2wTZRjHfa/X9Vb64suNti/nVuUQiboflShW4g80UwcB9Z8Fij/g1p1r XX9x15ZV/8HoDM4/wMU0rJGIsayMLVFnkAlqYplMluCiI6hMNHUzplNhEhOdiYvve9fbrv51 z32+7/N8n+d5L8dZ+FK1wIWiCVmJSmGxys7uVjf7GubVjX7viT94X+n8Vcb37+BQ1SamJZeb Z1r+Hrtqe4LZab+3XQ6HUrLSdP9ue7D4di8b/7Cha+CfjG0fOFLfA6o5jO7E3T8W2R5g53h0 ksH5nn6L/vIZwPn9Q1b95QuAvzo9ZqMpVageH8pctNJ4JXoIF78f0eIatBmfPXmF0fkWfLm/ h5znSLweLwxspZhFN+NzEx9pxyFqxoMHxspmkzZ8OPOqJlQToS+TZ2kMkAv/NT6k1bQgN740 8xajt41w7uMJix47cWl6Qct1okY8fPyV8pl6fP6bGaDHXnzi6KesHt+IRw8usLQ3C7oVv3uq SQ834fFf3LrTavzGa0Wb3uYKfK5vppzpxmdGR6wHgZA1NZRdKpRdKpQ1FcqaCh0B1uPAk5Kk 9kAkGEsmvOsbA1JbWG4MxCIBSU3Q5zCgV6zUbh0B1zItBYA4IDrg46GNft4qpdR0pAA6OUZ0 wkycoOVtsfZ0UFKDu5RkWFbFlbDZTjBcxG3JcKcowAsKoTWLNCrvVcNygnxTogeuzd7t592L mppU46FAKJZUdyWVcAFgzkLKVqm0bLuUfl5WYrpZAdzAsaIb4tQ9fh51SAm5U5bjsmKoezlO xDC1hySuUOQOuevZUDhhyCRPpgoyK1qzdTC6jRR0mQVTv6vh9F0kTzDL/2+Z4aoLoINzkL4f eJL2rcaliBrqKFvXQLePUIdBNdtVcJzuiDegybIOrqMrchlSpd04SAtu+ANNRvREMBldnFJw we8ue/389SaBugm18GvKnSa+ZCjcBItUXWVSKz2N38AsCJDPowb2UncH+UksDcnrd76sDLUZ MTys3UaZmUashbfQEZ1lpdJtluySIbvMXfHRXSakhHmXJUodBi3vcppC3oAVu5ylksuQKp2E feD24rLhQaddOjD4vrfQVJg83d3q2fMrjwc+v+/1rp+e2/HinH106OjPf068c2r/xTT/W6T7 2txZ5elj3uvezOfZl2wjvQsv71g+9/vOtR80r9ngaqybFFqntj/1wpmp2b7SvOeS7wL7bcP2 Q8+M5jxTaF3r/HuP2fo3WD7xc8EHH859+cijIqsGpTtusyiq9B8WGcuPfAUAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dLoGdquLUHelO56W0gqDaDGcZTc>
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 10:10:05 -0000

“    I disagree - at least for home users.
    Most home users simply unpack the ISP router, plug it in, and connect their devices to it.
    They plug in their webcams… “

This is what Homenet was supposed to solve – an easy, automatic way to segment networks at Layer 3.
Assign prefixes where at least there is a chance at Policy/Security between them and avoid very dissimilar Layer 2 subnets being bridged together – requiring ever growing sets of Application and Protocol proxies between them.

John

On 6/9/17, 6:01 AM, "ipv6 on behalf of Simon Hobson" <ipv6-bounces@ietf.org on behalf of linux@thehobsons.co.uk> wrote:

    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 devices 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/osram_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_protect_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 security 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 networking, they won't have any clue about setting up multiple networks - and the way 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.
    
    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 ?
    
    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 !
    
    > Note: the rule always has been "if you don't have enough prefixes
    > ask your ISP for more".
    
    At which point you come up against the technically illiterate beancounters running (some of) the ISPs who figure that if you want more IPs then you must be a customer worthy of paying them more. The same ones who, in the IPv4 world want a significant amount extra just to have a single fixed IP rather than a dynamic one, and even more if you want more than one address.
    
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------