Re: A common problem with SLAAC in "renumbering" scenarios

Simon Hobson <linux@thehobsons.co.uk> Fri, 15 February 2019 13:05 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 CDD2D130E74 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 05:05:54 -0800 (PST)
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] 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 n3YiJgKzOk4p for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 05:05:48 -0800 (PST)
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 7A4D3130F82 for <ipv6@ietf.org>; Fri, 15 Feb 2019 05:05:48 -0800 (PST)
X-Quarantine-ID: <V36FNzUo7Uo0>
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
X-Amavis-Alert: BAD HEADER SECTION, Header line longer than 998 characters: References: <60[...]
Received: from simons-macbookpro.thehobsons.co.uk (Simons-MacBookPro.thehobsons.co.uk [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id D36481BC37 for <ipv6@ietf.org>; Fri, 15 Feb 2019 13:05:40 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAO42Z2yAxcf1uz8B0LZ9JysfAB0Tr+Uzgkj7azaAT9vSgXWvjA@mail.gmail.com>
Date: Fri, 15 Feb 2019 13:05:39 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D25B255-26CB-4A0A-A57D-22EE73FEB36F@thehobsons.co.uk>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <1c7ebabb-d6f6-d877-d4aa-d6c0fc7d5c60@go6.si> <6278.1549471453@dooku.sandelman.ca> <CAO42Z2xdKtLJV11KXELBKca6CWn=B6Avz6bO_94kFFXaKiZ-pQ@mail.gmail.com> <4602.1549908472@localhost> <CAO42Z2w1swQNuwnrOyTCEMXt0NSyrBx7Ww3kUN-7dfEV=fvk3A@mail.gmail.com> <c16e0e1f-1ed2-ad88-80f1-070bdd8bccca@go6.si> <1F2C2AEE-1C7D-481C-BBA7-7E507312C53A@employees.org> <e56a6e5b-648d-200e-c35d-97f15a31fb2a@asgard.org> <CAO42Z2zh7fKAgQJq9aLCTiFoSSsTeGM=pK3gXitg+gcxH=9fhQ@mail.gmail.com> <d38857c2-6e92-91d6-bb5d-d3eeeb61276a@gmail.com> <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.com> <2612280f-195a-ae7a-b3b1-9022d9282fa7@foobar.org> <56F813F4-C512-40A9-8A68-1090C76A80F6@consulintel.es> <CAHL_VyCN8kU7qnLOphfGR25-xGBe_p6WeGTkKVXwU5uy5aJ8Dg@mail.gmail.com> <65DB4854-97D2-4C31-A691-2CD93812EF93@consulintel.es> <CAHL_VyCMpCcGkEQu+RV1GRf2QLB-HD0+AOOBV0YhfQ5sbydVzQ@mail.gmail.com> <1e31ec6a-a743-3034-51e4-19d88e379475@go6.si> <CAH L_VyAhbUVLwi2ViwrDNYi-Fy3j1TY2-Aq5SLCPtt5OdiFFdg@mail.gmail.com> <CAO42Z2yAxcf1uz8B0LZ9JysfAB0Tr+Uzgkj7azaAT9vSgXWvjA@mail.gmail.com>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/DrJijRgUnMWQWw0QuCqmSfuWLSo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Feb 2019 13:05:55 -0000

Mark Smith <markzzzsmith@gmail.com> wrote:

> I don't know about other markets, however dynamic IPv4 addresses on
> permanent, always up broadband links in Australia has usually been
> because ISPs wanted to charge a price premium for static address
> assignments..

That's the case in the UK as well. From my dealings with various of them over the years (with work hat on) I have come across a number of variations.
BT charges (or did last time I had any dealings) £5/mo for a single static IPv4 address - that may be a premium of as much as 15-20% but obviously less on a more expensive product. Since they run static and dynamic assignments on the same set of equipment/connections, and with permanent-on connections there's no IPv4 address saving with dynamic addressing, there's no technical reason to charge a monthly premium other than "because we can and it boosts profit margins".
TalkTalk does not allow static IPv4 on residential products, but does on business products. Naturally business products cost more, although they use the same set of infrastructure - so it's a purely marketing thing to stop a business that doesn't need a static IPv4 (or the slightly better service levels) paying less by using a "residential" product.

So yes, I think it's safe to assume that there's a strong profit driver towards doing anything that makes life "difficult" for any customer wanting a static address/prefix - eg for hosting services or running site-site VPNs. A lot of this is down to the competitive market we "enjoy" in the UK with a significant race to the bottom in terms of pricing among many of the ISPs - so anything that can lower the headline "from £xx" on adverts, while making it up on extras, is used. I don't expect IPv6 to be different if you want stable addressing.
So yes, I think the earlier reference to RFC 1925 (I'd forgotten about that one), section 2.3, is appropriate if pushing for stable addressing to be the norm.

Other ISPs are more reasonable. My own, Plusnet, charges a one-off setup when requesting a (single) static IPv4 and no premium thereafter.