Live data from Hacker News

Whatever happened to the IPv4 address crisis?

networkworld.com

71–80 of 149 posts

Re: Whatever happened to the IPv4 address crisis?

#71
post #38

Earlier quoted context omitted.

IPv6 makes the global routing table much smaller (because there's enough space for the subnets to be logical parts of the network, rather than squeezing as many addresses in as possible), so the core routers for the IPv6 internet ought to need less hardware than the IPv4 ones.

Ah thanks! Does this mean that the end routers can be simpler too, or do they still need significant processing power?

One big advantage of IPv6 is that routers will not have to deal with fragmentation. At higher debits, it should make a pretty important difference. http://en.wikipedia.org/wiki/IPv6_packet#Fragmentation

IPv6 also deals better with packet headers, so it's easier to calculate for routers. I suspect however this will make more of a difference for high end routers with lots of traffic.

As others have mentioned, the dual-stack transition does require more resources. Then again, you can implement NAT64 (or 464xlat), which seem to become more realistic/robust/more widespread solutions (running dual-stack also means managing two layers of routes, two layers of firewalls, etc).

(Disclaimer: this is not my day job, I just find it lots of fun to play with on my local network and the Montreal local city mesh.)

Re: Whatever happened to the IPv4 address crisis?

#72
post #33

http://cr.yp.to/djbdns/ipv6mess.html (circa 2003)

That was always a question I had in the back of my mind. We have this huge address space. Why not reserve a single prefix that means "look at the lower 32-bits of this address and use it as an IPv4 address"?

So sort of exactly like 64:ff9b::/96 in NAT64?

Re: Whatever happened to the IPv4 address crisis?

#73
post #38

Earlier quoted context omitted.

IPv6 makes the global routing table much smaller (because there's enough space for the subnets to be logical parts of the network, rather than squeezing as many addresses in as possible), so the core routers for the IPv6 internet ought to need less hardware than the IPv4 ones.

Ah thanks! Does this mean that the end routers can be simpler too, or do they still need significant processing power?

They won't have to do NAT. They can just route packets. Plus, the header format is much simpler, and all fragmentation should happen at the end node.

Re: Whatever happened to the IPv4 address crisis?

#74
post #70

Earlier quoted context omitted.

No. You provide the best service to your customers for the best price. For DO's case, default to IPv6 and charge extra for each IPv4 address used. Currently, they charge $5/month for their cheapest droplet. Change that to $4/month and charge an extra $1/month for an IPv4 address. This way if my setup is more complex than a single droplet running everything, I can save some money on VPS's that don't need public IPv4 a…

It won't help. If they charge $4+$1, it would not be seen as "they just changed the price structure". It would be seen as "they are charging for something that used to be free". Especially as marketing folks won't miss the chance of advertising "our package is now $4 " small print "( additional charges apply)". And most customers will be royally pissed at that, both by the fact that they got advertised $4 but have to…

OK so give a $1 DISCOUNT for IPv6 only.

Re: Whatever happened to the IPv4 address crisis?

#75
post #70

Earlier quoted context omitted.

No. You provide the best service to your customers for the best price. For DO's case, default to IPv6 and charge extra for each IPv4 address used. Currently, they charge $5/month for their cheapest droplet. Change that to $4/month and charge an extra $1/month for an IPv4 address. This way if my setup is more complex than a single droplet running everything, I can save some money on VPS's that don't need public IPv4 a…

It won't help. If they charge $4+$1, it would not be seen as "they just changed the price structure". It would be seen as "they are charging for something that used to be free". Especially as marketing folks won't miss the chance of advertising "our package is now $4 " small print "( additional charges apply)". And most customers will be royally pissed at that, both by the fact that they got advertised $4 but have to…

It's already happening. Most providers charge $1-2/month for every additional IPv4 address AND you have to justify why you need it. EC2's Elastic IP's also don't get added to EC2 instances automatically; you have to add them manually and newly opened accounts are limited to I believe 10 IPv4 addresses for all EC2 instances. That's what IPv4 exhaustion looks like today.

This has nothing to do with net neutrality. It's progress of technology. Your ISP doesn't give you IPX access do they? Instead this is a natural progression of technology. Want to use old tech? Pay a premium!

Re: Whatever happened to the IPv4 address crisis?

#76

Doesn't the US defence department hold a ridiculous amount of the address space? What would it take for them to give some of that up?

Entire /8s wouldn't last a single month at current demand (and demand is only going to continue to increase), while consolidating usage to free up the /8 would take many times that long.

It's simply not worth the time and cost for such a short-lived bandaid.

Re: Whatever happened to the IPv4 address crisis?

#77
The problem is the majority of the companies who are stalling the IPv6 upgrade are in the US; which as chimeracoder stated is not going to feel the crunch as bad as other countries. People are very short sighted for one; and for two are afraid of 'breaking' what works.

I have even setup organizations with native IPv6 addresses (no tunnel) to watch them fear and lament it.

There's a thousand excuses and people need to look upon this as an opportunity; to up their skill set and mentor a new generation.

Re: Whatever happened to the IPv4 address crisis?

#79

The main problem the 20 years ago with the take off of the internet as a mass networking standard it was blindingly obvious that ipv6 was deeply flawed - IPv6 should have been taken out behind the woodshed back then and ipv7 or 8 done properly. When I looked at it 19 or the 20 involved in the RFC for ipv6 where from academia plus one guy from bell labs. Migration and Interpenetration should have been the highest prio…

Maybe. Or maybe we will suffer tremendous amount of pain for some period of years after which we will have a much brighter future as opposed to an ipv7 that made too many concessions and left us with a mess that would be politically impossible to ever fix.
Post reply on HN