IPv4 Unallocated Addresses Exhausted by 2010
An anonymous reader writes "Ars Technica is reporting on how the unallocated IPv4 address pool could run out as soon as 2010. The IPv4 Address Report gives details on just how fast the available pool of IPv4 addresses is diminishing. Will ISPs be moving towards IPv6 any time soon? Or will IPv4 exhaustion become the next Y2K?"
Despite the best efforts of organizations like ARIN, the simple fact is that, compared to IPv4, IPv6 gives you access to very little content and very few users. So far, nobody has been able to get past this chicken-and-egg issue, although a The Great IPv6 Experiment proposes to change this by giving away free access to "10 gigabytes of the most popular 'adult entertainment,'" but only over IPv6.
Is IPv6 so unappealing that they've gotta bribe people with pr0n to use it?
i've been hearing about how ip4 will run out in the next 5 years for the last TEN years.
If you mod me down, I will become more powerful than you can imagine....
I bet that people will be bored of the internet by then
Y2K was a bug which was easily solved. This is an infrastructure defect which has an available, but expensive, solution.
It will be expensive to make a major shift to IPv6, which is why it's taking so long.
Until the complete exhaustion of all IPv4 addresses is an immanent threat the change will not happen, much like Y2K.
They could delay the inevitable by reallocating existing IPv4 space more efficiently. Many old/historical allocations are inefficient. Apple Computer, for example, has all of the 17.x.x.x space, comprising 256^3 = more than 16 million addresses, which is just plain absurd in this day and age.
Well duh, why do you think people got on the Internet in the first place? Some military experiment? pffffffft. It's all about the pr0n!
Mr. Universe: "They can't stop the signal, Mal. They can never stop the signal."
Telecom companies are switching everything, including cell phones, to VoIP. Soon, damn near every cell phone will have an IP address associated with it. CDMA phones that EVDO rev-A already do. I know one carrier that has a pool of 2 million available addresses, and 20+ million customers with cellphones.
IPv4 addresses are going to be going away very quickly.
Learning HOW to think is more important than learning WHAT to think.
Do you not understand that IPv6 essentially increases the address space for IPv4 to virtually infinity?
True, but you'll have to pry it from their cold dead fingers!!!
Kind of reminds me of a Grandpa Simpson (skewed to be somewhat on topic): "I didn't earn it, I don't need it, but if they miss one [octal] I'll raise hell."
Mr. Universe: "They can't stop the signal, Mal. They can never stop the signal."
Is IPv6 so unappealing that they've gotta bribe people with pr0n to use it?
With one of the bigger 'features' of IPv6 being the possibility of assigning and tracking users individually with the huge number of addresses - I suspect it does not play into the current (sorta) anonymous surfing mindset folks have today. (Not that anyone is truly anonymous on the web) Once you have to slap down your address to access the content, I can see why people might not be interested.
+++ UGUCAUCGUAUUUCU
Man, am I glad I've got 192.168.0.100 through 192.168.0.105 setup on my network at home. Hmmm.....maybe I should lay claim to 106 through 110, just in case.....
-- Fugacity: Confusing chemists since 1908
That would require a change to all TCP/IP stacks, and replacement of core routers.
Why not just fix the problem outright if you are going to do that?
There are two issues:
- Switching protocols
- Getting IPv6 addresses
You can use the IPv4 subset of the IPv6 address space, and everyone can still talk to everyone while you convert. It's only the folks that have IPV6 addresses before the IPv4 users have migrated that become unreachable by anyone.So the online businesses are going to want to be the last ones to switch, so that their customers don't become unable to reach them.
But anyway, IPV6 gives you access to all the same content.
- "History shows again and again how nature points out the folly of men" -- Blue Oyster Cult, 'Godzilla'
Ease adoption how, exactly? You still need to update the protocol, then update all the software, and all the hardware, and all the documentation and training... you can't just tack that on to existing implementations of software.
If you're going to force all that change, then change to something that isn't a silly half-arsed hackjob.
Is IPv6 so unappealing that they've gotta bribe people with pr0n to use it?
It's not unappealing, it's totally irrelevant to end-users. There's no market out there asking for IPv6 network access. ISPs and their upstream providers thus have no increase in revenue if they deploy IPv6, but that deployment will cost them real money -- v6 capable routers need much more storage and processing, for instance -- and so there's real financial incentive to avoid IPv6. Offering free pr0n might be a way to make the difference relevant to end-users and thus provide demand and revenue, but I kind of doubt that it's enough.
When end-users are getting IPv6 or private address IPv4 to the door, and a NAT exchange at the ISP, and their VOIP/game/spyware breaks, there will be financial motive at all levels. Being able to offer a full and uncrippled Internet experience will be the value-add.
But expect a period of chaos as ISPs try to barter IPv4 addresses around, and failing that, try to steal them.
I think companies will start 'renting' addresses as IPv4 is approaching its limit, pretty much like the concept of carbon credits.
Companies may cut down unnecessary IP usage, or buy/rent addresses from other companies with plenty to spare.
This 'trade' could go on until such point it's either more costly to rent than move to IPv6, or when all available-and-necessary addresses have been fully utilized.
Virtual Betting on Facebook for non-geeks.
I doubt anyone will be making a concerted effort to switch until it actually becomes necessary. Once the IPv4 address space runs out, hacks will be done to extend it. Ranges will be "repo'd" from companies, or those companies will just start reselling those ranges. Not until there is no space left to squeeze out will people really start caring.
That's really just not true. With IPv6, you can get a lot more anonymity than you have now with IPv4. v6 has all sorts of special provisions for randomly assigning addresses, letting you reset them when you want, so that you can appear to be a new user in the middle of a browsing session. That's tough to do with IPv4; even if you try a DHCP release-and-renew from your ISP, generally they won't issue you a new address until the other one has expired.
IPv6 doesn't force you to give up any privacy, and there's no 'user serialization' unless you buy into it voluntarily.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
If we do run out of IPv4 addresses for real this time, I predict ISPs will switch to 100% private IP addressing space before even thinking on IPv6.
Heck, it's already happening in other countries. In Chile for example (a reasonably high-tech country) VTR http://www.vtr.cl/, the only cable ISP, will give you ONLY RFC-1918 addresses, period.
The masses won't care. They only care about their basic apps, and ISPs will use that as leverage to control more services, especially all P2P and VoIP-related ones.
Those are MINE, you THIEF!
Kidding - I'm KIDDING
boycott slashdot February 10th - 17th check out: altSlashdot.org
"Is IPv6 so unappealing that they've gotta bribe people with pr0n to use it?"
It worked with IPv4.
Although I shudder to think back to the days of downloading pr0n on a 14.4k modem!
There's also significant financial incentive to keep the limited address space of IPv4. Want a static IP address or additional IP addresses? Fork over the cash, baby!
Routers that have been capable of supporting IPv4/IPv6 dual stack have been available for a long time now so unless you're a tiny ISP that has no budget for life-cycle upgrades it's very likely your kit is already capable of running IPv6. Now, whether or not your engineering staff is trained in supporting IPv6 is another story. Within 5-10 years though ISPs will have very little excuse to NOT support IPv6 since they will have replaced any antiquated IPv4-only equipment as it is end-of-lifed. US Federal Government agencies have a mandate to support IPv6 by June 2008 so it has been spurring a lot of vendors to get their shit in order and either upgrade their products to support IPv6 or face not being able to sell to one of their largest customers.
NAT is a dreadful hack.
-b.
...and climb on board as an enterprise IPv6 migration consultant.
Hopefully it *is* the new Y2K.
I'm continually amazed at the number of people in the IT and Net industry who keep "wondering" when IPv6 will arrive. Its been here for a long time. I'm running a series of web servers for internal company use that have native IPv6 addresses. For public consumption, we have an IPv4 reverse proxy that allows us to run our entire web services behind one IPv4 address. Any customer who has an IPv6 address gets to talk to the individual servers.
/64 v6 address for a cheap price. You'll design your websites to be usable on v4, but for management tools, etc, you'll need to install a v6 tunnel.
The advantage comes when you consider management. In order to have 20 SSH/FTP/etc accessible Internet servers, I'd either need 20 separate IPv4 addresses (getting a decent segment of a class C here is expensive), or I'd have to play fun games with ports. All our technicians have IPv6 on their laptops, and use tunnel brokers for access to the v6 network.
Most of our clients have IPv6 connectivity, though they don't notice it. When we put in a firewall, IPv6 comes default setup with tunnel brokers.
People keep asking, when's there gonna be v6 content? There is no v6 content (ok, their is full colour ascii starwars). Any content provider would be nuts to say "you have to have v6 to see our content" at this point (with the exception of mobile phones). IT Techs brought v4 to the public, we'll bring v6 to the public. Its technicians like myself who appreciate having an Internet accessible toaster (ok, so its not yet accessible) that have already started the ball rolling.
Before long you'll see hosting providers saying, you can have one web gateway shared v4 address and a
I use to have a funny sig, but slash cut it off, and I forgot what the punchline was.
I wonder if the bogon list space is considered?
http://www.faqs.org/rfcs/rfc1918.html
If I'm reading it correctly your ISP treats you like you are part of their corporate intranet and then pipes your traffic out. I'd expect the ISP have a similar traffic footprint and pattern to a largeish college campus that doesn't assign every PC an outside IP.
There will be some guy in an ill fitting suit accosting you, "hey man, got extra IP4?" "I gotta plug in man, I'm jones'ng for some connectivity." "IP6? can't. My colon can't take the colons, 3 dots is all I can handle"
- a new mobile phone for each person
- a new computer
- a new [xbox|ps2|ps3|nintendo]
- a new modem
- a new ANYTHING that contains a network interface (ip4 address)
because its more economical viable to buy some new than to fix something we already have and all the old stuff (which is in perfect working order) ends up on a rubbish dump.... off course until we realize that the temperature graph is exponential, ouch!
to code or not to code, that is the question.
Just move slashdot to an IPv6 only address; voilla by monday every corporate will have a functioning IPv6 setup... ;-)
In fact, if IPv4 truly were a subspace of IPv6, then what sources address would an IPv4-only host be seeing when it receives such a packet from an IPv6-only host?
It is perfectly possible to use both an IPv4 and an IPv6 stack simultaneously, and there are some NAT-like technologies that run on a router to give IPv4 connectivity to IPv6-only hosts, but you'll still need an IPv4 stack somewhere on your network to access IPv4 content.
And now to ensure this gets modded as Flamebait: there just aren't enough free-market thinkers on Slashdot.
Apart from full colour ASCII star wars, there's a free binary news server with 40+ TB data!
List of stuff.
ARS must have rushed the fact checking to get this article out. Truth is that ARIN does not, and has never, made a best effort at anything except to charge ISPs for address space and let them reap a 500 to 1000% profit reselling it. ARIN has done nothing substantive to promote IPv6, and ARIN looks the other way at hundreds of existing, unused, large IPv4 network allocations.
I've worked at Silicon Valley companies with multiple class B allocations that could have easily put them behind NAT gateways and firewalls. The University of California campuses have many class Bs and will tell you they "can't do NAT to the dormitories because it's too difficult to track". That's 65K address per class B and there are dozens of these, and several class As, that are just waiting to be reclaimed.
What these class A and B-owning organizations are doing is holding on to vacant land as long as they can, until it becomes valuable, at which point they hope to sell it at a big profit.
ARIN is doing the same thing by failing to reclaim these allocations. They're just waiting for demand to climb like California real-estate to begin cashing-in. This is exactly what Network Solutions/Verisign did with domain names when they had a government-protected monopoly. Have we forgotten so soon, one year domain registration was free (via SRI), and the mext year it was $100 per year per domain (via Verisign), despite actual costs of $7/year. This scenario should also be familiar to those who have had to change telephone area codes, sometimes more than once, until enough people complained (of course that was when the FCC was in Democratic hands. With Republicans the Telcos have once-again been cleaning up).
So believe the hype, but remember, if you fail to look a little deeper we will soon be paying the price, in increased ISP fees, for this wholly artificial IPv4 address shortage.
Same thing that happened when popular domain names started running out. I'm sure IP addresses will go up for auction. Seems kind of silly though considering the space available in IPv6. But if you have people that need these addresses, someone will be willing to pay for them. I imagine some of the big names that got them free from the start will be making a lot of money, such as MIT.
The IPv4 addresses are a subset of the IPv6 space -- you can get to all of the IPv4 systems from an IPv6 network.
This is what IPv6 fanatics constantly FAIL TO UNDERSTAND. IPv4 addresses ARE NOT a subset of IPv6 addresses, because IPv4 and IPv6 are INCOMPATIBLE PROTOCOLS.
Let that sink in.
Just because there's some addresses within the IPv6 space that can map onto IPv4 addresses doesn't mean you've made the two protocols compatible.
I can't get to these embedded IPv4 addresses from my IPv4-only machine unless I go through extra hardware/software that tunnels or gateways the packets, basically converting them to IPv6.
And if there's an IPv4 address on the other end, I'll simply USE IPv4 TO REACH IT.
The *only* incentive for people to use IPv6 is if popular and useful web sites exist ONLY on IPv6. I.e., Google, Hotmail, whatever. Apparently, the IPv6 fanatics think that ISPs will happily upgrade their hardware and software just so that their IPv4 hosts can talk to IPv4 servers through some Rube Goldberg IPv6 network, waiting for the day that Google's IPv4 IP goes dark. No, that's not gonna happen.
If you can't comprehend what I've said, replace "IPv6" with "Fidonet" or some other protocol and think about it.
Yes, it would have the same prefix, but that's exactly the same level of anonymity that you have now with a single IPv4 address and NAT.
With v4, your router gets the address and then NATs it out to however-many devices you have. With v6, you'd get a block of addresses at the router, which it could then distribute via DHCP, or the machines could randomly assign themselves within. You're not losing anything there. Where you might gain something is in the ability to quickly switch IPs when traveling and connecting to an AP that's not yours (which is conceptually similar to performing a DHCP release-and-renew).
If you want plausible deniability, pretty much your only option is to leave your AP unsecured and hope that when the cops show up they buy it as a defense, or use some type of onion routing like Tor.
There seems to be a lot of fear and paranoia going around regarding IPv6, and I just don't get it. There's nothing you can do on IPv4 today that you can't do on IPv6, if you want to. Hell, if you're that attached to NAT, you can do it with IPv6 addresses just as readily -- it's just that it's stupid, because there's no longer any reason to since there's no address shortage, and there's really no privacy or security gained from it that you don't get by just rotating your IPv6 address.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Oil out of supply in 1999, Global warming killing everyone in 2005, P2P piracy ends with Napster, Limewire, Kazaa.
Seriously it's all just FUD, There's an expiration date, but 2010? What happens when we make a few Class As into Class Bs? oh that's right, more time. I think the key is to figure out how to make the best "IPv6" and a way to make it so my old commodore 64 is willing to work with it (whether that be ISP level conversion or a inexpensive hub, note INEXPENSIVE)
Do I have a commodore 64? Not any more but the point remains there's literally a million devices out there only able to communicate with IPv4. There's actually a million people out there not willing to go through the hassle of going to IPv6 (and probably about that many who are unwilling to change) and if the way they are pushing to get people to switch with FUD like this, I'm guessing it's more than a couple million who don't want IPv6, so it's time to ask ourselves, how can we make IPv6 more attractive than staying with IPv4, and implement these ideas. IPv6 will likely overtake v4 one day, but come on, let's find a way to make people switch rather then just wait for it to happen.
clearly the real answer here is 42. we should skip right over IPv6 and go to.... IPv42
anything else?
"Jazz isn't dead, it just smells funny" ~Frank Zappa
EdelFactor
What are you talking about? You have to "slap down" your address to receive content with IPv4, too - otherwise, how would a server know where to send its response? And if you're paranoid to the point that you want to break your Internet connection for the sake of not divulging internal IP addresses, then yes, you can masquerade behind a single IP address on IPv6 just as easily as you can on IPv4.
Or you could perform more complex 1:1 address masquerading, the likes of which aren't possible on consumer IPv4 connections due to said address space crisis. This could be performed at the router to obscure any autoconfigured internal addresses which might have been generated from machines' MAC addresses; or you could take Microsoft's approach, and implement such features at the operating system level.
IPv6 offers more features and a much greater address space, with no built-in cost to privacy. Fearmongering by those who are unfamiliar with the new protocol will only hurt its adoption rate, to the detriment of the entire Internet community.
They don't allocate IP addresses, they allocate routes entry and with route entries, you get way more addresses than most need. The solution for this is to start allocating non-contigious /24... Force everyone to fix their routing and treat the wold as a 2^24 /24 ranges and get over it. To do this right requires less than 8mb of cache tag ram in most routers that want full feeds and enough ram to process the bgp routing updates.
Going to IPv6 doesn't fix the fact that routers are running out of routes. This problem will get plenty of attention in about 2 months when the big Cisco routers start to dump routes because they are too big and adding IPv6 only makes the problem much worse.
One issue is all the home users inadvertantly using NAT as a "firewall".
If one were to build a proper ipv6 router, they would need to (pony up the cash to) include a proper firewall, or educate the users. Good luck with either one.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
Well, yeah. That's the "Strategic IP Address Reserve."
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
But if you talked to @Home's people as individuals rather than Corporate Employees, almost all of them would say "Well, Duh! Napster is the reason that people are *buying* broadband internet connections, of *course* we like it."
And, ok, the paranoia about servers on home cable modems was partly because their early trial equipment didn't work very well and they had no way to regulate individual upstream bandwidth usage, and PacBell's dishonest "Cable Modem Web Hog" ads made them really worried about perceptions of slow performance, but they were worried that somebody would run a pr0n webserver from home, become Cool Site of the Day because doing that on cable modem would be cool, and trash their neighborhood's network performance while causing a lot of publicity. And unfortunately most of the cable companies have not only not recovered from that attitude, they've been propagating it to the DSL providers, and they've been learning other cluelessly paranoid attitudes from the Australian ex-monopoly who thinks you should cap the total monthly download of their users (since that used to be expensive in Oz), and cap it to a ridiculously low level like 1GB/month, which is like 1.5 days of continuous 56kbps usage.
But when I had my corporate hat on, especially if I was talking to non-California customers, it was certainly much more proper to talk about the big internet usage being for music piracy than for pr0n
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
The stateful firewall you'd need on an IPv6 connection isn't inherently any more complicated than an IPv4 UPnP+NAT box. In order for NAT to work, the device performing the translation must keep track of all the individual connections; it's basically a stateful firewall already. If you can do that, then you can firewall IPv6 (provided you have the capacity for the longer addresses). You need a protocol, like UPnP, so that clients can request "holes" (so that things like FTP, Bittorrent, and VoIP work), but that's no worse than NAT right now.
Now, I think this is a completely crappy way to run a network, and I think we just need to get rid of the idea of firewalls completely (at least as a generic cureall, I'm all for retaining them for specific applications); security needs to be at the client level, not at the network-gateway level; as more and more devices become mobile, they cannot and should not ever assume that their local network is secure.
But unfortunately, people have gotten so used to the idea of firewalls that they're attached to them, particularly because it allows for a certain amount of laziness (running old, crummy operating systems on Internet-enabled systems, not patching, etc.) while giving the perception of safety. So I suspect that all IPv6 implementations will mimic the brokenness of NAT, at least initially.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
You're kinda nuts...a 2621 runs the same price (on e-bay) as a mid to low end users computer! At $500-$600 on ebay we're talking router tech that's 6-7x the price of the average home router. So as long as that's the kind of hardware the end user will need, i's not going to work.
Mobius Custom Computers
IPv6 has large address blocks - the smallest any organization (like your home DSL line) is likely to have is a
So unlike IPv4, where any machine you connect to on the net or anybody eavesdropping in between knows what IPv4 address you're using, and maybe they can find out from DNS or logfiles where that address is, with IPv6, they see your IPv6 address which tells them what machine you're connecting from. You can do things to change that (e.g. pick a different IPv6 address, or set the MAC address on your network card if it supports that), and if you control the network connection, you can set it any way you want. And these days you're probably still going to go through some firewall, there might be something NAT-like happening, or at least a proxy, or some 6to4 gateways.
But in theory, if everybody administered everything the way the IPv6 designers envisioned it, every time you plugged in your laptop to a different LAN, your MAC address would probably still be visible, which is really convenient for debugging and not so hot for privacy.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Often the router can do it, but not well. We have this at work (a major university) with our stuff. It's all Layer-3 switches, which means that IPv4 is done extremely quickly via ASICs, with minimal impact on the CPU even for fairly complex sets of rules. However IPv6 is not accelerated. Thus you can turn it on, and it'll work fine so long as not many people use it, but if everyone tried, the router falls over as the CPU gets slammed. There are, of course, new supervisor modules that'll do the v6 routing on ASICs, but we don't have those and they aren't cheap (a few million dollars to upgrade all the core and edge routers that'd need it). Being that we are having our budget cut, this isn't something that's high on the list.
That's a large part of the problem with v6 is that it isn't as simple as many people think. You don't just enable it on your routers and expect everything to work well. There's a lot of high end gear in place that doesn't have hardware support for v6 and thus it all has to be done on the CPU, which is usually much less powerful than you'd think. It isn't a trivial amount of money to just replace all those, nor can they afford to turn it on in software and hope that usage is light enough that they don't get slammed.
Now as new gear gets put in to place, which happens all the time, this problem is slowly going away, however it's still a major problem right now. The routers on our campus may be about 6 years old, but they are still powerful units that do what we need, and we've no inclination to replace them. I'm sure big ISPs feel the same way.
Given that the IP situation isn't the crisis that some people keep wanting to make it out to be (I've heard this shit many times before) I imagine that the process will probably be slow, and equipment will be replaced for other reasons. However once all the equipment is IPv6 capable, organizations will probably start turning it on since why not. It isn't likely to be a big, hurried rollout, just a gradual shift.
Claiming to be pedantic on Slashdot is asking for trouble
IPv6 doesn't force you to give up any privacy, and there's no 'user serialization' unless you buy into it voluntarily. Sorry, but that is just not true. There's some fuss in the air about IPv6 privacy extensions, which is basically bullshit. As an IPv6 customer, you'll typically get a
BUT: The whole
To illustrate my example, there's a IPv6 ISP in Germany that gives out even a
If we're not counting accountability, but just usage tracking on websites etc, easy: just don't treat every Ip address as unique (like in IPv4), but instead every
Continuous positive slashdot karma since... uh, maybe next year.
Using (P)NAT, it's possible to map each one of those (potentially) 65536 services on a single real IP address to a unique machine on a reserved IP address (in the 10.x.x.x, 172.16.x.x, 192.168.x.x ranges). Since the reserved addresses are not routable, they can be used an infinite number of times provided that they connect to the Internet via a single real IP address.
The point I'm trying to make is that only an Internet server needs to be identified by a unique port on a unique IP address, everyone else can get away with using NAT-ed reserved IP addresses. Therefore, the exhaustion of the IPv4 address space really isn't that critical in the short term.
Gentoo Linux - another day, another USE flag.
I take it you haven't been following IPv6 closely, since that hasn't been the case for about six years (see RFC3041). The MAC address part of the IPv6 address was never used as a substitute for ARP; doing so would have broken addresses assigned in different ways (e.g. stateful autoconfiguration, manual configuration), which were always allowed. The low bits are a hash of your MAC address, and so only a mapping from MAC to IP is possible, not the other way around. If privacy is a concern for you, then you can easily pick a different IP at pseudo-random.
I am TheRaven on Soylent News
I am when im on my laptop in a parking lot of some coffee house.
Hold on, someone is at my window, 'yes officer?' * click *
---- Booth was a patriot ----
Vista will only contact Active Directory DC over IPv6, and although Samba3 works over IPv6, it won't work as a DC [Dan Shearer]
David Holder has a more detailed presentation of this at http://www.ipv6consultancy.com/ipv6blog/wp-content /uploads/2007/05/samba-and-vista-with-ipv6v2.pdf
but to oversimplify, MS tried to prevent Samba from being an
AD Domain Controller by making IPV6 a prerequisite, with
strictly limited and temporary success (;-))
--dave
davecb@spamcop.net
So right now we have a flat address space of 32bits or so. Why not
create multiple internets, one per country lets say. Everyone
gets to keep their existing internet address. Its just encapsulated
within a country network.
In order to get to country A address B.B.B.B you have to use
a route. Each ISP would have a special router address that would
send packets to that country accross a "dedidcated" connection. Your
computer would know that when DNS assigns a "zip" for a particular
connection, it locks the routing for those packets to go out via
the local ISP dedicated router address.
Your computer knows what router to use because it got the "zip code"
for that route when it did the DNS lookup.
Yes, I realize there would be problems. But perhaps less problems then
with IPv6 adoption?
This is moving to a hierarchial model. And the extra address space
comes from the routing tables.
Its just an idea. Please be kind.