Comcast seems like one of the largest deployments of IPv6 for normal consumers outside of the cell companies.
A /60 is pathetically small, with SLAAC you have 16 (!!) subnets for your whole network. With people having multiple computers and multiple phones, this is not enough even for a normal household of 3 people. If you are a IT person, with multiple computers and VMs, forget it.
The recommended size of block that every ISP should give is /48 (RFC 6177). Good ISPs will give you a /48, some lesser ISPs will give you a /56. Comcast and crappy ISPs will give you a /60.
I agree a /60 is stingy, but "not enough even for a normal household of 3 people" sounds like massive hyperbole. Even as a tech enthusiast filling that would be some work, unless you insist I use a /64 for point-to-point links.
Have you ever used VMs on a laptop? How many virtual networks do you need? Only one? With only one you only need one extra bit bit for routing, so you could give a /63 instead of a /64 to your laptop, except that IPv6 allocation is supposed to be done in nibbles (and you need to overprovison anyway, what if tomorrow you need two networks?), so the next logical step is a /60, which means your ISP should give you at least a /56. Personally, I use much more than one virtual network on my laptops, so I would need a /60 anyway (if I want to keep all the nice properties of IPv6, that is).
As long as you want to keep everything nice with IPv6, the block you need is /64-(4*n), where n is the level of routing you plan to do.
> unless you insist I use a /64 for point-to-point links.
Each p2p link on IPv6 uses a /64 (even though it's only assigned an /127).
> How does a household with 3 people need 14 subnets?
In the IoT era (where S stands for security), if you don't put each IoT device in its own VLAN, you are in for a surprise.
Very few, to the point of "if it's more than one, the other ones aren't intended be reachable and thus don't need public space".
> Each p2p link on IPv6 uses a /64 (even though it's only assigned an /127).
No, it doesn't, since my routers don't need to do SLAAC between each other, but can happily live with static IPs.
> In the IoT era (where S stands for security), if you don't put each IoT device in its own VLAN, you are in for a surprise.
Never felt the need to put each device in it's own subnet, sensible firewalling seems enough. I tend to avoid devices that really want to talk to the internet though, so most of the time it's "you don't get to talk to the internet"-subnet. But ok, if you love connected stuff and want to split it in very fine ways, that'd be a bunch of subnets.
So yes, as I said /56 would be nice and should be the default but /60 is likely to be enough for the vast majority of users.
I've got a larger then normal home router with 6 ports. I can have a /64 for each, and still have a bunch left over if I want to split up wireless into more secure, medium secure, less secure, and least secure networks.
I'm all for more address space, but I'm at a loss as to why a normal even a sophisticated home user needs more than a /60.
I wouldn't turn down a /48, but realistically I've got 30 or so IPs in use. Sure recently I added an IP for a wristwatch, TV, and a stereo. Clearly cheaper devices are getting Wifi. It's becoming more common in appliances, thermostats, door locks, electrical outlets, light bulbs etc. But 2^64 pennies is quite a bit, and I doubt anything will be consuming more than one IP per $0.01 of cost anytime soon.
A /64 can't be subnetted any more (one host, NO VMs!).
A /60 can support one level of extra routing.
A /56 can support two levels of extra routing.
If you plan to run VMs on your laptop, you need a /60 on your laptop, which means you need a /56 from your ISP. If you want to keep everything nice and future proof, that is, if you want to fuck up with special configurations, you can use your /60 from your ISP, and give a /62 to your laptop, then each laptop can have 4 networks for VMs. But that is limiting and a PITA to set-up.
Why not directly bind all VMs to laptop's NIC? This way, they can get IP from the same /64 subnet. On firewall, only enable public access to those VMs that are needed.
I do have a home lab, but every VM is directly bridged to NIC and gets its IP from home router. So a single /64 is sufficient for me.