3 ms·
Wouldn't it be nice to allocate a small part of the IPv6 space to geographically encoded IP addresses? In other words, the address itself can be used to physica
by phkahler 12y ago
Wouldn't it be nice to allocate a small part of the IPv6 space to geographically encoded IP addresses? In other words, the address itself can be used to physically locate the destination and a route could be chosen partially according to geography. It seems like this should be less arbitrary than the routes you need to chose now. Or is it?
- agwa 12y agoIPv6 addressing does sort of work that way: each RIR (regional Internet registry) has just a single prefix allocated out of the global unicast address space, instead of a whole bunch of prefixes all over the place as with IPv4. And the IPv6 address space is large enough that ISPs can be given a single huge prefix that they can grow into. Consequentially, the global IPv6 routing table should be a lot smaller than the IPv4 routing table is today.
- akira2501 12y agoNot 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.
- wmf 12y agoVoila: http://tools.ietf.org/html/draft-hain-ipv6-geo-addr-02 http://tools.ietf.org/html/draft-hain-ipv6-geo-addr-02 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?
- phkahler 12y agoYes, at its core, this is the "overlapping hierarchy" problem. I believe in the case of the internet, this is almost a regulatory issue. Not to be dismissed, but failure to build a simple network structure is largely due to the number of players involved. Perhaps we could encode an ISP ID in the address as well, but that has its own issues.
- tjgq 12y agoApart from the fact that "geographically close" does not always coincide with "network-wise close", that's essentially the principle behind route aggregation as used by routers today. 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.