It'd be nice if they gave out a proper prefix delegation. Instead the best I can get allocated is a /60. Pretty sure the RFC recommends /48's to be allocated to customers.
Out of curiosity, what's your use case for more than 16 subnets? I agree on principle they should give you a /48 if you ask for it, but the truth is that I'm extremely grateful they rethought their original stance, which was that a measly /64 was enough for anyone! That would have been extremely harmful and short-sighted; I feel pretty comfortable with a /60.
On that note, does anyone know what Time Warner's maximum prefix delegation size is?
(Unless there is an aspect of the privacy extensions I'm not familiar with, but this is what people usually mean when they say "privacy extensions.")
I'll fine with 16 subnets today, but I don't know what'll change in the future. I'm sure I'll have use cases for more.
By what method are you noticing that? I made this extension for Chrome that displays a "4" or "6" in the address bar:
https://ipvfoo.googlecode.com/
Here's a similar extension for Firefox:
https://addons.mozilla.org/en-us/firefox/addon/sixornot/
Sadly, Hacker News is still stuck on "4".
So right from the start, consumer/small business IPv6 gear won't be able to build on having more than a /64 for themselves (to subdelegate for things like home automation networks, virtualization, etc). Oh well, I guess those things will need to support IPv6 NAT!
Not very ironic at all. IPv6's autoconfiguration (through link-local addresses, the Neighbor-Discovery Protocol, etc.) comes from engineers with decades of experience (and frustration) in managing ISP-sized netblocks.