Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
Simon Hobson <linux@thehobsons.co.uk> Fri, 09 June 2017 10:01 UTC
Return-Path: <linux@thehobsons.co.uk>
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 EAB3412956C for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 03:01:43 -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 B8hdm2vANOjg for <ipv6@ietfa.amsl.com>; Fri, 9 Jun 2017 03:01:42 -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 E5ACE126FDC for <ipv6@ietf.org>; Fri, 9 Jun 2017 03:01:41 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.137.117] (unknown [192.168.137.117]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 94F6F1BC37 for <ipv6@ietf.org>; Fri, 9 Jun 2017 10:01:33 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <20170609011106.22E967B64301@rock.dv.isc.org>
Date: Fri, 09 Jun 2017 11:01:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB84AB04-ABAC-4DEB-B69B-92EA5A904967@thehobsons.co.uk>
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>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Oomg0q79IKqLVrY5lwXWFldntM8>
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:01:44 -0000
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.
- Deprecating IPv6 (Re: draft-bourbaki-6man-classle… Mark Smith
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Chris Morrow
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… David Conrad
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Simon Hobson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Carsten Bormann
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Job Snijders
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Roger Jørgensen
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Brian E Carpenter
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Brian E Carpenter
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mark Smith
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Brian E Carpenter
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Matthew Petach
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mikael Abrahamsson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Randy Bush
- Re: Deprecating IPv6 Havard Eidnes
- Re: Deprecating IPv6 Randy Bush
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Erik Kline
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Alexandre Petrescu
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… otroan
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Leddy, John
- The waist diameter (was: Deprecating IPv6 (Re: dr… otroan
- Re: The waist diameter (was: Deprecating IPv6 (Re… Tom Herbert
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Fred Baker
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Ca By
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Don Sturek
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Brian E Carpenter
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Fred Baker
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Simon Hobson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mikael Abrahamsson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… james woodyatt
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mark Andrews
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Lorenzo Colitti
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Simon Hobson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Leddy, John
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mark Andrews
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Fernando Gont
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Simon Hobson
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Carsten Bormann
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Mark Andrews
- Re: Deprecating IPv6 (Re: draft-bourbaki-6man-cla… Simon Hobson