However, applying it successfully to IPv4 is severy compromised because, due to rampant address space fragmentation during the last years, increasingly longer prefixes (i.e., smaller address blocks) have had to be assigned. IPv6's much larger address space makes it unlikely that the routing table will ever become that fragmented in the foreseeable future.
http://www.iana.org/assignments/ipv6-unicast-address-assignm...
8 years of stability is hardly a "poorly planned mess".
To the point that the linux documentation project still recommends the following as an ipv6 default route example: /sbin/ip -6 route add 2000::/3 via 2001:0db8:0:f101::1
Yea.. it's /workable/, but a lot of decisions with respect to IPv6 feel like wasted opportunities that have only slowed adoption and promoted general confusion.
Some gotchas emerge when you start thinking about actually implementing this. How can you aggregate a city under a single prefix if it has multiple ISPs?