3 ms·
Not quite. The current IPv6 global unicast table is a bit of a poorly planned mess. http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unic
by akira2501 12y ago
Not quite. The current IPv6 global unicast table is a bit of a poorly planned mess.
http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml http://www.iana.org/assignments/ipv6-unicast-address-assignm...
- agwa 12y agoThanks for the correction. How did things get so screwed up? At least it's still miles better than IPv4 I suppose.
- p1mrx 12y agoThere were some smaller chunks in the experimental days, but note that in 2006, each RIR was given a /12, and since then there have been zero allocations at the top level. 8 years of stability is hardly a "poorly planned mess".
- akira2501 12y agoIn 2006 they also gave ARIN a /23 and APNIC a /20. Then, one month later they expanded some previous RIR allocations into /12's; separate from the previous two allocations I mentioned. They are also allocated in a seemingly random order throughout 2000::/3, which they've decided to constrain their allocations to for some reason. 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.