Residential assignments are often /56 (2^8 subnets) or even maybe /60 (2^4 subnets): this may or may not be enough for business needs, depending on the size of the organization.
ULA is absolutely routable. Are you confusing it with LLA?
> and has lower precedence (3) than ipv4 (35)
This already got changed in https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc672..., the document is fully done with the RFC editor queue and only waiting for the [SNACBIT] reference to get published.
New preference table:
Prefix Precedence Label
::1/128 50 0
$known_local/4x 45 14 (**)
::/0 40 1
fc00::/7 30 13 (*)
::ffff:0:0/96 20 4 (*)
2002::/16 5 2 (*)
2001::/32 5 5
::/96 1 3
fec0::/10 1 11
3ffe::/16 1 12Yes many keep track of that RFC. However you're aware that every client device, tv, phone, esp32, iot device, has to apply this change? That will take decades
I don't necessarily disagree with the assessment, but to a certain extent I like getting new addresses/prefixes to help with privacy: with my previous ISP I had my own Asus router (now have to use ISP-provided), and it had built-in functionality to schedule reboots.
To me it seems the main issue is that the old prefix immediately stops being valid. There's not exactly a shortage of IPv6 addresses, so the ISP shouldn't be in any hurry to reuse the old prefix. If they were to still route it to the customer for, say, 24 hours, then it would give equipment time to switch over to the new one.
Non-sticky, dynamic prefixes cause all sort of mayhem because suddenly your RAs, firewall rules, DNS recods, NAT64 pools etc. are all outdated and you have to somehow update them.
[1]: https://www.ripe.net/publications/docs/ripe-690/