Slashdot Mirror


ARIN Is Down To the Last /8 of IPv4 Addresses

An anonymous reader writes "On 3 February 2011, the Internet Assigned Numbers Authority (IANA) issued the remaining five /8 address blocks, each containing 16.7 million addresses, in the global free pool equally to the five RIRs, and as such ARIN is no longer able to receive additional IPv4 resources from the IANA. After yesterday's large allocation (104.64.0.0/10) to Akamai, the address pool remaining to be assigned by ARIN is now down to the last /8. This triggers stricter allocation rules and marks the end of general availability of new IPv4 addresses in North America. ARIN thus follows the RIRs of Asia, Europe and South America into the final phase of IPv4 depletion."

306 comments

  1. About time! by drew_92123 · · Score: 4, Funny

    They've been talking about this day for what seems like an eternity... Finally, we can start complaining about something else!

    1. Re:About time! by i+kan+reed · · Score: 0

      Yeah, now we can start complaining about how we can't run servers anymore for actual lack of IP addresses.

    2. Re:About time! by Anrego · · Score: 5, Informative

      Nah.

      ISPs will just use more carrier grade NAT to free up IPs, maybe charge a little extra if you want your own IP outside of NAT to run game servers or skype or whatever (a relatively small group). Should hold of IPv6 for another 10 years or so.

    3. Re:About time! by Anrego · · Score: 1

      * hold off

    4. Re:About time! by cold+fjord · · Score: 3, Insightful

      And hopefully more large companies and organizations that hold large blocks of public IP addresses will start moving to private IP addresses and release the public IP addresses for use by others. I know some places that have large numbers of systems with public IP addresses that are behind firewalls and really have no business having a public IP address on those systems anymore.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    5. Re:About time! by DigiShaman · · Score: 2

      Yes, there's profit in scarcity. CGN/CGNAT also has a nice effect in breaking P2P which frees up the bandwidth they've been long seeking anyways. For them, IPv4 is a win-win-win all around.

      With regards to IPv6, I expect mobile phones to adopt it this standard more rapidly than your standard PC/Server market for home and business use. With the exception of IPv6 facing web servers of course.

      --
      Life is not for the lazy.
    6. Re:About time! by Anonymous Coward · · Score: 0

      Yeah, like IBM using their 9.0.0.0/8 for desktops.

    7. Re:About time! by Gerald · · Score: 2

      Depends on the ISP. You could create a Homeric epic from the things that Comcast does wrong but they seem to be doing a great job with their v6 deployment. T-Mobile is doing a pretty good job too.

    8. Re:About time! by Hamsterdan · · Score: 1

      Servers can be run on virtualized IPs, like in the ten last years...

      --
      I've got better things to do tonight than die.
    9. Re:About time! by Karl+Cocknozzle · · Score: 1

      Should hold of IPv6 for another 10 years or so.

      The odds of us ever actually "transitioning" to IPv6 are somewhere between slim and none for the foreseeable future. The most likely way it will work out is mobile applications (where it doesn't matter what you're using because it's a mobile phone that mates only to the provider's network) will be mostly IPv6 before too long, if they aren't already. Some consumer ISPs may move customers to IPv6, but that will be somewhat delayed by the incredibly slow pace that content providers are switching to IPv6--that is to say, as Akamai has illustrated for us here by getting themselves a /10 (FUCK ME, that's a shitload of IPs for a company that already controls multiple other swaths of space this big) the content providers just aren't bothering to move to IPv6.

      And yeah, the ISPs can choose maintain a bridge between the universes, but the more traffic you pour through that bridge the more resources it requires to operate... Eventually, if the ISP can't force the issue it stops making sense to transition any more users to IPv6 until more content providers get on-board.

      I fully anticipate retiring in another 25 years or so and still having IPv4 be the vast majority of IP networks in operation because in the end, even if your ISP switches, what's the point of changing your internal network over? Any company of decent size will have a security team that says "No fucking way will outsiders directly connect to your IPv6 address" and block it with some kind of firewall/NAT arrangement which almost instantly negates the biggest "advantage" of IPv6. And once that "advantage" is off the table there is zero business reason to incur the expense involved in such a change-over.

      --
      Who did what now?
    10. Re:About time! by petermgreen · · Score: 1

      Comcast is in the unusual position that they are so damn big they have run out of space in net10 leaving them with two painful options, move to IPv6 or "federate" their network so they can reuse the same private IPs in different places.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    11. Re:About time! by SuricouRaven · · Score: 1

      Can't speak globally, but in the UK most mobile applications are carrier-level NATed v4.

      There's little reason for content providers to go to IPv6, because hardly any consumers can reach them there.

    12. Re:About time! by mikael_j · · Score: 5, Informative

      That would have about as much effect as pissing into the ocean would have on raising sea levels.

      We need to move to IPv6 and if you're not prepared then yes, it will cost you more than if you had a bit of foresight and didn't keep buying IPv4-only software and hardware right up till the very end.

      --
      Greylisting is to SMTP as NAT is to IPv4
    13. Re:About time! by Anonymous Coward · · Score: 0

      The other "benefit" is that for CGNAT to work you need to have a large pool of addresses to start with, so the lack of unassigned IPv4 blocks means there's no longer reason to worry about pesky new competitors appearing.

    14. Re:About time! by Anonymous Coward · · Score: 0

      Or when I worked at Ford they used 19.0.0.0/8 for their workstations and desktops.

      My computer at my desk had a public 19.x address and they used their firewalls and corporate blablabla to make it just like an RFC1918 address.

      I say yank the 19.0.0.0/8 back from Ford. They only need like 100 addresses tops.

    15. Re:About time! by Aaden42 · · Score: 1

      And best yet, ISP’s will have an excuse to charge you extra for not-upgrading their infrastructure so you can continue to do what you already do for additional cost and no material improvements to your service. Brilliant!

    16. Re:About time! by decsnake · · Score: 1

      no argument about the basic evilness of comcast, but their core network engineers are really, really good.

      I'm running V6 at home thru a tunnel and the only major sites that I see supporting V6 are facebook and google.

      What this says to me is that the really big players have already gone to V6 out of need, as you pointed out about comcast.

    17. Re:About time! by MightyMartian · · Score: 2

      I don't understand that at all. If you're going to just have public-facing IP addresses, why not go to IPv6?

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    18. Re:About time! by Anonymous Coward · · Score: 0

      Without looking, what is your static IPv6 address? ;)

    19. Re:About time! by jbolden · · Score: 2

      No they won't do that. Carriers have been pretty clear they aren't implementing carrier grade NAT and supporting it. ARIN has been hostile to them making use of carrier grade NAT. It isn't happening.

    20. Re:About time! by jbolden · · Score: 1

      Once home / small business switch over the content providers are going to be virtualized. Which means that service will stop working, geolocation being the first to go. They'll lose the ability to meaningfully regulate traffic (everything is coming from West Virginia). It is fairly east to switch most websites over. Most consumer content will switch with a few years of the carriers being ready.

    21. Re:About time! by wagnerrp · · Score: 1

      Servers can be run on virtualized IPs, like in the ten last years...

      IPs are just numbers. There's nothing physical about them. What the hell is a "virtualized IP"?

    22. Re:About time! by radarskiy · · Score: 2

      "Without looking"

      Clearly, if I do not know how to start a fire by rubbing two sticks together I should only eat raw meat.

    23. Re:About time! by Anonymous Coward · · Score: 0

      speaking of holding off for another 10 years, we need to purge every organisation on the planet of their /8s swapping them for /24s or less would be a far better and more efficient alternative.

      How many internet facing machines do they need and why can't they NAT those that don't need a public IP?

      Discuss.

    24. Re:About time! by Anonymous Coward · · Score: 0

      Mod parent comment up, while this is no panacea, it would definitely hold off the IPv4 apocalypse and needs to be considered as it is a quicker fix than switching to IPv6.

    25. Re:About time! by mwvdlee · · Score: 1

      I know from research papers that both the USA, Germany and Canada's mobile networks are NAT too (USA seems to be split in east/west NAT's for some providers).
      From personal tests, the Netherlands are NAT too.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    26. Re:About time! by HappyPsycho · · Score: 2

      Quicker than what? IPv6 is at least a decade old, we've had time to switch and refused to do so.

      If you believe the week to month we get from reclaiming these blocks will have any reasonable effect on the global pace of allocations you are more than a little delusional.

    27. Re:About time! by Anonymous Coward · · Score: 0

      My first thought is that "virtualised IP" is what you get when Intellectual Property is no longer abstract enough.

    28. Re:About time! by Anonymous Coward · · Score: 0

      ...and this is what DNS is for...

    29. Re:About time! by Anonymous Coward · · Score: 0

      If you believe the week to month we get from reclaiming these blocks will have any reasonable effect on the global pace of allocations you are more than a little delusional.

      Which is why Ford and others should have never been allocated /8s from the beginning.

    30. Re:About time! by cold+fjord · · Score: 1

      That would have about as much effect as pissing into the ocean would have on raising sea levels.

      That isn't completely true due to the high degree of leveraging that can occur with NAT. It only takes a relatively small number of public addresses to service millions of private IP client addresses. There are very large numbers of private IP addresses being wasted. One properly used Class A block could allow you to service many billions of client computers.

      I agree that we do need to move to IPv6.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    31. Re:About time! by Karl+Cocknozzle · · Score: 0

      Once home / small business switch over the content providers are going to be virtualized . Which means that service will stop working, geolocation being the first to go.

      "That word... I don't think it means what you think it means..."

      Most consumer content will switch with a few years of the carriers being ready.

      Carriers have been "ready" for years--nothing whatsoever is stopping Comcast, AT&T and everybody else from flipping 100% of their users to IPv6 tomorrow, in fact. ...But there's no content to access via IPv6... So what's the rush?

      --
      Who did what now?
    32. Re:About time! by Anonymous Coward · · Score: 0

      It also has the benefit of breaking many games and consoles platforms. Sounds like a great way to increase your call center load. CGNAT is fine for cell phones, but wait until the PlayStaytion and XBox players start flooding in complains that they can't play half of their games because they use uPNP to forward ports, then the huge number of gamers who use Skype. Ohh yeah, fun times.

    33. Re:About time! by QuantumRiff · · Score: 3, Interesting

      Without looking, what is the IP address of slashdot? Oh, you don't care because there is DNS?

      --

      What are we going to do tonight Brain?
    34. Re:About time! by stderr_dk · · Score: 3, Funny

      Without looking, what is your static IPv6 address? ;)

      ::1/128

      --
      alias sudo="echo make it yourself #" ; # https://pipedot.org/~stderr & http://soylentnews.org/~stderr
    35. Re:About time! by Anonymous Coward · · Score: 0

      Your statement doesn't make his point any less valid. I can rattle off no less than 35 specific IPs with no subnet correlation smaller than /12, 4 ranges and a multitude of ipv4 private addresses all of which are assigned to or managed by the company I work for. Of the IPv6s, I know about 10, and only because they end in ::XX.

      Sometimes things just go to shit and it's useful to have that kind of stuff floating around in your head. I didn't go out of my way to put it there, but that's how it ended up.

    36. Re:About time! by Anonymous Coward · · Score: 0

      A /10 seems like a lot until you realize they are a CDN and are probably going to do a lot of really small subnets. When you start carving up a block of IPs into manageable subnets that have enough room to grow, you'd be amazed how quickly the usable number of IPs drops.

      It's a memory vs efficiency trade off. If you want to keep your routing clean, you need to be wasteful with IP addresses. A few years back they were talking about the IP address space fragmentation and the issue it's causing with core routers. An 50% increase of in use IP addresses resulted in a 200% increase of routes. That is unsustainable for routers.

      With an increase in the number of devices but reaching the cap on IP addresses, we'll soon see a 0% increase in in-use ip addresses, but a large increase in the number of routes caused by massive subnetting.

    37. Re:About time! by WillAffleckUW · · Score: 0

      Our blade servers run perfectly fine under IPv6.

      You're not using Windows, are you?

      --
      -- Tigger warning: This post may contain tiggers! --
    38. Re:About time! by bytestorm · · Score: 1

      To hyperbolically extend your argument, pretend you looking for an embedded systems kernel developer. Applicant A has worked on projects with hundreds of thousands of lines of PHP, so you should hire A because she can google it. Having direct knowledge is sometimes helpful.

    39. Re:About time! by HappyPsycho · · Score: 2

      Because if you are "Public-facing" you need to be able to speak to the maximum number of users for your service to stand a chance of being successful. To do that if you have to you need to choose the more common "language", right now that is still IPv4. You can argue the technical merits of going full IPv6 all you want (I have more than I care to admit), but at the end of the day if your product doesn't make money you will be out of business long before IPv4 vs IPv6 becomes a serious problem.

      Sadly, Content providers pretty much have to be bi-lingual until IPv4 dies, so do the ISPs (at least at their core, where their IPv4 and IPv6 customers mix, unless they have the enviable state of a full IPv6 customer base or current state of a full IPv4 customer base). The only ones that get to just move and have few repuccusions are the end users.

      Until IPv4 runs out and IPv6 is forced on end users by ISPs (on whom it will be forced by having no more IPv4 to give) will this dynamic change and then the content providers will respond by speaking the language the majority of their users are speaking (requiring less translators).

    40. Re:About time! by mikael_j · · Score: 2, Insightful

      Urgh, carrier grade NAT is the last thing the Internet needs.

      What's the point of the Internet if there is no end-to-end connectivity?

      --
      Greylisting is to SMTP as NAT is to IPv4
    41. Re:About time! by suutar · · Score: 2, Interesting

      if anyone back then had seen this coming that clearly, they'd have just used 64 bits to start with and we'd be fine for the next thousand years.

    42. Re:About time! by sosume · · Score: 1

      These addresses were allocated in the age before The Great IP Shortage. There were no signs that the internet would be used privately by regular people and many sysadmins were clueless as to how IP networking worked. NAT routers were incredibly expensive and the right way to go was to just buy an IP block, distribute it globally across branches and use the router to block traffic from other IP blocks. All major companies in the eighties bought IP blocks, see http://en.wikipedia.org/wiki/L... . Ofcourse many more companies have settled with 'just' a bunch of class B networks as 64k hosts is not enough if you're aiming to dominate global business. I can actually understand companies like Ford or US Postal to register an A class. Others such as Eli Lily or the UK Gov Dept of Pensions really don't need so many adresses. But now the internet has changed and there are barely enough addresses for all existing devices. So these blocks should be revoked and private networks should be private.
      Perhaps a nice rule would be : if you want to have a single public IP adress you will need to be online with it for at least 1% of a month. Failure to do so will cause the address to be revoked after 3 months. And for B and A classes. If the networks do not route and cannot be accessed through their gateway, the block grant should be revoked and NAT or VPN should be used instead. This should give us a few more years until we come up with a radical replacement of the current internet. Not that IPv6 crap..

    43. Re:About time! by maccodemonkey · · Score: 1

      Nah.

      ISPs will just use more carrier grade NAT to free up IPs, maybe charge a little extra if you want your own IP outside of NAT to run game servers or skype or whatever (a relatively small group). Should hold of IPv6 for another 10 years or so.

      People I know who work in things like media transports and video chatting are already being driven nuts by the number of problems and inefficiencies introduced by carrier grade NAT. You might as well be suggesting "Well sure, the wheel has fallen off the car, but let's just get someone to carry the car the rest of the way."

      Can't wait for wide IPV6 deployment. Carrier grade NAT is NOT a good solution.

    44. Re:About time! by Anonymous Coward · · Score: 0

      That's quite interesting. Why ATT would force my uVerse router to use IPv6 when they are alredy using private IP on WAN interface?

    45. Re:About time! by i+kan+reed · · Score: 1

      Windows supports IPv6. You know full well it's ancient machines and switches that cause all the problems.

    46. Re:About time! by profplump · · Score: 1

      35 IPv4 address is the same amount of data as ~9 IPv6 addresses. So I feel like you have the capability to remember them if you so desired.

      Also your important services should be at well-known addresses -- like $PREFIX::1, just like people frequently use in IPv4 -- to make the addresses easier to remember.

    47. Re:About time! by Darinbob · · Score: 3, Interesting

      No one really imagined in the 70s that there would be a need for more IP addresses than people.

    48. Re:About time! by Darinbob · · Score: 1

      AT&T claims they're getting IPv6 ready. They're pretty close. In fact the only thing that stands between me and IPv6 at home is their uverse router.

    49. Re:About time! by WillerZ · · Score: 2

      +1, accurate.

      One of my peeves with IPv6 is that in v4 I had over 16 million legal loopback addresses out of only 4 billion addresses; now in v6 I have exactly one out of a much larger pool. It is not often useful, but it isn't always useless to use more than one of the loopback addresses on a host.

      I would have preferred loopback to be a /64 rather than a /128 in IPv6: it's not like the address-space is too small to afford it.

      --
      I guess today is a passable day to die.
    50. Re:About time! by fgodfrey · · Score: 1

      The "great job" depends on whether you have Business or Residential service. Apparently, they're doing well on the Residential side. On the Business side (which I have), I just called to see when I can get IPv6 and their answer was "when we run out of IPv4, all our new customers will get IPv6 and the old customers will be on IPv4". Um, gee, thanks.... I'm assuming this person was misinformed, but the fact remains that my neighbor with residential service can get IPv6 and I, with business service paying quite a bit more, can't..... I hope they get their act together soon!

      --
      Go Badgers! -- #include "std/disclaimer.h"
    51. Re:About time! by Cyberdyne · · Score: 2

      Others such as Eli Lily or the UK Gov Dept of Pensions really don't need so many addresses

      Someone in the UK government pointed that out recently - it turns out that "Dept of Pensions" allocation is actually used across most of the government as some sort of VPN extranet with various external contractors. Apparently, since they all use different RFC1918 blocks internally, they can't all be VPNed into any single RFC1918 block: they needed a globally-unique block for that purpose.

      British Telecom uses the 30.0.0.0/8 block for managing all their customer modems - that block is actually allocated to the US DoD, but they don't allow external access to it anyway, so there's nothing to stop you using that block internally yourself as long as you don't need to communicate with any other networks using the same trick. Better than wasting an entire /8 of global address space just for internal administrative systems - or a /9, like Comcast grabbed back in 2010.

      My inner geek - who cares about efficiency - would love to see all the legacy blocks revoked. I'm sure the DoD could use 10/8 instead of 30/8 quite easily for their non-routed block; the universities could easily fit in a /16 instead of a /8, or smaller with a bit of NAT. Still, we should be moving to IPv6 instead now: give each university and ISP a /48, or /32 for big complex networks needing multiple layers. I just have a nasty feeling we're in for a long time of CGNAT spreading instead - where we currently have ISPs that don't offer static IP addresses, in a few years they'll be refusing to issue anything other than a NATted 100.64/16 address.

    52. Re:About time! by WillAffleckUW · · Score: 1

      hey we dev new switches here at the uw of course I know ...

      --
      -- Tigger warning: This post may contain tiggers! --
    53. Re: About time! by vadim_t · · Score: 2

      Why would they release anything? The more time passes, the more they are worth. They have all the incentive to sit on them as long as possible, and only sell for $$$. If they can't resell, still no reason to release, where would they get more afterwards if they need them?

    54. Re:About time! by Anonymous Coward · · Score: 2, Funny

      That would have about as much effect as pissing into the ocean would have on raising sea levels.

      But then Portland would throw out the Pacific Ocean.

    55. Re:About time! by DigiShaman · · Score: 1

      If you can pay extra for DLC and subscriptions, you can pay extra a month for that dynamic private IP. So that will be the way they see it.

      --
      Life is not for the lazy.
    56. Re:About time! by Khashishi · · Score: 1

      Once we finally move on to IPv6, can we all have our own static IP?

      That's a good reason to push it.

    57. Re:About time! by jbolden · · Score: 1

      "That word... I don't think it means what you think it means..."

      Let me clarify. Their addresses are going to be virtualized relative to the IPv6 space. The are going to look to the IPv6 customers as if they were on Verizon / AT&T... local routable subnet while in reality they are passing through a gateway. I'm not saying the servers are virtualized but the route will be.

      Carriers have been "ready" for years--nothing whatsoever is stopping Comcast, AT&T and everybody else from flipping 100% of their users to IPv6 tomorrow,

      Not they aren't ready. I've attended conferences on this. Verizon is getting close to ready. Comcast is done and it was 6 years of agony. They still have lots of stuff in their consumer / small business setups that makes v4 assumptions.

      But there's no content to access via IPv6... So what's the rush?

      The rush is to be able to reclaim that valuable v4 address space to sell it at a premium to business.

       

    58. Re:About time! by Yaztromo · · Score: 1

      if anyone back then had seen this coming that clearly, they'd have just used 64 bits to start with and we'd be fine for the next thousand years.

      Exception that on a 8-bit computer running at only a handful of MHz, using a 64-bit address right off would have entailed a performance penalty. There would be more packet overhead, and more address processing required.

      This may not seem like a bad compromise for clients, but you have to consider what would have happened to routers in the 70's and 80's had 64-bit addresses been the norm. Won't anybody think of the routers?

      Yaz

    59. Re:About time! by Yaztromo · · Score: 1

      Once we finally move on to IPv6, can we all have our own static IP?

      That's a good reason to push it.

      Actually, you get a prefix -- either a /48 or a /64, from which you can assign your own addresses. A /64 is enough to give you more addresses than the entire public IPv4 Internet. How you use them internally is up to you.

      Yaz

    60. Re:About time! by mars-nl · · Score: 0

      Why don't we switch to country-wide NAT or world-wide NAT? We would only need *one* public address and every client would be 192.168.0.1. Life would be so simple. And we wouldn't need DNS anymore. Nice! Oh, wait...

      My point is: NAT kills the internet.

    61. Re:About time! by Midnight+Thunder · · Score: 1

      Network infrastructure. Despite the writing being on the wall, it has been considered as comedy. The comedy is now laughing at them. As usual it is going be a question of people panicking over something that could have been planned for.

      --
      Jumpstart the tartan drive.
    62. Re:About time! by mrbcs · · Score: 1
      You sir win the internets!!

      I agree wholeheartedly. There is not now, nor will there ever be, a reason to have all computers facing the internet without a router. IPv6 has been a collossal (sp?) waste of resources.

      I tried a dumb little experiment the other week. I'm not retarded, I've been playing with computers since 1994.

      I thought I'd be "smart" and use the second port on my isp supplied router for gaming. The port is there for x-box and the like. Thought I'd get a better ping. My wife likes watching videos while I play WoT.

      Guess what? Virus like RIGHT NOW!!! I have antivirus, firewall and hosts file. I don't download anything sketchy, yet I was owned in no time.

      I changed back to my router, which is behind their router, cleaned out my system and haven't had any issues since. I now use qos from my switch. (Yes I realize I should have done that first).

      So by going through two routers I have no need for an ipv6 address and I can do anything I need to do including online gaming. People hate change naturally and there's no way people will change for NO REAL REASON!!! I have been saying this for 8 years now.

      --
      I'm not anti-social, I'm anti-idiot.
    63. Re:About time! by skids · · Score: 1

      I fully anticipate retiring in another 25 years or so and still having IPv4 be the vast majority of IP networks in operation

      I wouldn't give it 25 years. The last technical obstacle is about to fall on the enterprise campus, in that the latest generation of switches and wifi conrollers that are being sold now have roadmapped upgrade paths to RIPE-554. Almost all our other gear has been IPv6 ready for year; once the old edge switches are phased out (5 year timeframe) those roadmaps will have become reality and then it's just a matter of finding the time, which won't take two decades.

    64. Re:About time! by cold+fjord · · Score: 2

      Client nodes reach the public internet just fine using NAT.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    65. Re:About time! by cold+fjord · · Score: 1

      Your point is wrong. Much of the internet is reached by client nodes using NAT now.

      Does your internet have any firewalls on it?

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    66. Re:About time! by am+2k · · Score: 1

      My (EU) ISP still ships cable modems that are not IPv6-compatible...

    67. Re: About time! by cold+fjord · · Score: 1

      Why don't you ask Interop why they basically returned a Class A network address block?

      Interop Returns 16 Million IPv4 Addresses

      Interop gives back a month’s worth of IPv4 addresses

      Apparently Interop, the holder of the 45.x.x.x block since 1995, no longer needs that much space. They're now returning 99 percent of it to ARIN, the American Registry for Internet Numbers, which handles IP address distribution in North America. Interop is holding on to a small fraction of the 45/8 block that's currently in active use.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    68. Re:About time! by mysidia · · Score: 2

      they'll be refusing to issue anything other than a NATted 100.64/16 address.

      "Super-Enhanced Xbox/PS3 Plan: For an extra $75 a month, you can get a unique dynamic public IP address. Play games online with your network connection!"

    69. Re:About time! by Anonymous Coward · · Score: 0

      if anyone back then had seen this coming that clearly, they'd have just used 64 bits to start with and we'd be fine for the next thousand years.

      1) No, they wouldn't as hardware costs to use and process 64 bit would have been astronomical.
      2) If you think 64-bit will last the next 1000 years, you aren't seeing the big picture. This is precisely why IPv6 chose 128-bit ... they are hoping it will last a long time.
      3) The largest challenge moving forward isn't no longer going to be the size, but the management of it all. We've had to become creative with managing it due to size limitations with IPv4. Those same limitations won't be nearly a concern with IPv6.

    70. Re:About time! by mysidia · · Score: 1

      IPs are just numbers. There's nothing physical about them. What the hell is a "virtualized IP"?

      An IP address assigned to a service instead of a computer system.

      You would use a stateless translation at your border to translate the virtual IP to the IPv6 address of a load balancer, for example.

    71. Re:About time! by Anonymous Coward · · Score: 0

      Right terminology, wrong usage. Virtual IP is just a fancy word for load balancing based on IP addresses (instead of using domain name based load balancing). Individual servers have private IP addresses, and you have the public IP address point at a load balancer, which then distributes the connections across the machines. Virutal IP would not solve the problem of making IP addresses available if no addresses are available. However, it would mean that in a case where you'd normally do load balancing using domain names (and assigning each server with a public IP address), you would reduce your demand for public IP addresses and get by with obtaining fewer total public IP addresses.

    72. Re:About time! by Anonymous Coward · · Score: 0

      One properly used Class A block could allow you to service many billions of client computers.

      Breaking news! Classful addressing was deprecated over 20 years ago (RFC 1518 & RFC 1519).

    73. Re:About time! by FuzzNugget · · Score: 1

      Yeah, just what we need: another excuse for carriers to rape our wallets.

    74. Re: About time! by cbiltcliffe · · Score: 1

      That's great. Now try convincing your ISP to forward port 32794 to you so you can run a game server for your buddy to connect to.

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
    75. Re:About time! by ButchDeLoria · · Score: 1

      NAT means huge amounts of fun for sites that do IP bans.

    76. Re:About time! by unixisc · · Score: 1

      Hopefully, ISPs will now stop distributing routable IPv4 addresses like they are birdseed.

      In the end, I'll bet that they'll be forced to surreptitiously convert everybody to IPv6 w/o even telling them. Thanks to years of procrastinating.

    77. Re:About time! by unixisc · · Score: 1

      Why hope for that? The transition to IPv6 will go via dual-stack configurations, and that will require that the private IP addresses be retained, even if an organization is going IPv6. For the IPv4 part of the dual stack support, they'll need NAT, and since the most widespread NAT is PAT, which prefers multiple routable IPv4 addresses, organizations are better off keeping the private IPv4 addresses that they have. The best thing for organizations just entering the internet to do is start w/ IPv6-only, and provide IPv4 via something like a DS-lite configuration.

    78. Re:About time! by unixisc · · Score: 1

      Without looking, what is your static IPv6 address? ;)

      Do I need to know? If yeah, I'd use DHCPv6 to have it manually assigned. And if I'm manually assigning it, the Interface ID, or the host address part of the address I can make as simple as possible, such as [Global Prefix]::b00b

      If not, I'd just let ND pick an address.

    79. Re:About time! by unixisc · · Score: 1

      But what would you have gained w/ the loopback being /64 rather than /128? Also, why was loopback a Class A block in IPv4?

    80. Re:About time! by unixisc · · Score: 1

      But ain't that what DS-lite is about? You set up things on a IPv6 network, and for clients that are IPv4 and need to access your service, you set up an LSNAT @ their end of the connection. Up to their router, the traffic is IPv6, and their router then NATs it to a local IPv4 address of theirs on the network. They are then good to go.

    81. Re:About time! by unixisc · · Score: 1

      But most networks don't use either static or dynamic NATs: they use something called Port Address Translation (PAT), and that one prefers a pool of public addresses so that a single public address doesn't have too much of a load. Once one uses that, the effect of NAT is diluted by a few orders of magnitude, depending on the #public addresses thrown @ it.

    82. Re:About time! by unixisc · · Score: 1

      Those addresses were allocated @ a time when the only use of the internet was supposed to be the Pentagon, and organizations it dealt with within & outside the US. That's why the initial blocks that were assigned were Class A blocks to organizations like IBM, DEC, HP, GE, Ford, MIP, Stanford, et al. Nobody imagined that Billy Joe Blow in Podunk, XX would be on it. Also, IPv4 was an experimental protocol: IPv6 is the protocol that the IETF had meant to go into production.

      Since even the slightest change to IP address lengths - even changing them from 32-bit to 33-bit would have meant having to change every network on the planet, the IETF decided that given the scope, every conceived improvement should be built into it. Some materialized, while some, such as fewer routes didn't, since the Internet ain't hierarchical. But all in all, IPv6 has solved a lot of things.

      The only 'disadvantage' of IPv6 is that most of the world has yet to convert to it.

    83. Re:About time! by unixisc · · Score: 1

      Windows Server 2008 and 2012 has IPv6 as their native IP, as does Vista onwards. It's XP which is IPv4 only

    84. Re:About time! by Anonymous Coward · · Score: 0

      Please quote for us where the phrase, "may not longer be used" or "is deprecated" is used in regard to classic addressing?

    85. Re: About time! by Anonymous Coward · · Score: 0

      They still use 19.0.0.0.

    86. Re:About time! by Bengie · · Score: 1

      My firewall has about 30k active states. Should be interesting to see how that would affect a PAT CGNAT.

    87. Re:About time! by Bengie · · Score: 1

      if anyone back then had seen this coming that clearly, they'd have just used 64 bits to start with and we'd be fine for the next thousand years.

      The creator of IPv4 actually said he wanted to do 128bit, but he figured it would be hard to push for a proof-of-concept. But as soon as he showed his network to his bosses, they said "go live", without giving him the opportunity to switch to 128bit. He said he wished he just bit the bullet and used 128bit from the start and he no longer skimps on proof-of-concept designs because he doesn't want this same issue to occur.

    88. Re:About time! by mark-t · · Score: 1

      Where do you figure you have only one loopback address?

      0xfe80::/64 is explicitly reserved for link-local addresses in ipv6. You can add as many as you want.

      Or is 18 quintillion addresses not enough for you?

    89. Re:About time! by Anonymous Coward · · Score: 0

      They can't say they're selling Internet access if the Internet is fundamentally broken unless you pay extra. Just wait for 10 million console players to create a class action lawsuit.

    90. Re:About time! by HappyPsycho · · Score: 1

      DS-Lite from what I've read is no better than CGN in the sense that something still has to translate the IPv6 ip of the customer to a IPv4 address from the pool of available addresses all the while keeping a tunnel open to the IPv6 endpoint (CPE). This may be a better solution than whatever else is available, due to the lack of movement on switching to IPv6 any ISP has the choice between llama-goat-crap and wow-holy-bovine-crap. DS-lite pretty much also assumes that the customer only wants to make connections out via IPv4, with no inbound connections allowed. There is almost no way to have a 1-to-1 mapping between IPv4 to IPv6 (any ISP with enough address space available to have a DS-lite IPv4 pool that big will just run dual-stack).

      Also based on http://www.networkworld.com/co...

      If a simple mapping between inside IPv4 source address / port to outside IPv4 source address / port was performed on outgoing packets, as is done with regular NAT44, the LSN would have no way to differentiate between overlapping RFC1918 IPv4 addresses in different customer networks.

      In other words the LSN has to somehow be able to differentiate between 192.168.1.5 on your network (which might be your PS4 but for the guy down the street its his wife's laptop). This is normally handled by VRF (separate routing / arp / NAT table) per customer, Thankfully they have dealt with this by just tacking on the customer's unique IPv6 address to the record it just makes what I expect to be huge NAT tables even larger. The diagrams from that article also show that the real benefits of DS-lite won't start showing up until the end user's devices are running IPv6 natively (only then can they take advantage of the direct paths, instead of the translated paths).

      So if I'm understanding you (and DS-Lite) correctly, how does this remove the need for at least some part of the service provider to understand both IPv6 and IPv4? To me it concentrates the load on the translator devices in exchange for removing the need for the entire network to understand IPv4. In the short term this will be an extremely high load for these devices to maintain, I guess the hope is only token effort has to be put into them so it forces users to switch to IPv6 when available. Given that only 3 of the top 10 sites on http://www.alexa.com/topsites lack IPv6 records (twitter, amazon and baidu) that may not be an unreasonable expectation (the heavy streaming sites like, youtube & netflix are IPv6 so load may actually be lower than expected).

    91. Re:About time! by Agripa · · Score: 1

      It would help if some ISPs, namely AT&T, had not started actively blocking IPv6 tunneling.

    92. Re:About time! by Agripa · · Score: 1

      I tunneled IPv6 for years on AT&T. It is only recently that they have started actively blocking it. Coincidentally, this occurred right about the time they started offering upgrades for money to support it.

    93. Re:About time! by unixisc · · Score: 1

      Since when is a link-local address the same as a loopback address?

    94. Re:About time! by unixisc · · Score: 1

      B'cos it doesn't make sense to mix protocols. Both private & public IPs may be needed, but that issue should be independent of whether IPv6 is preferred to IPv4

    95. Re:About time! by unixisc · · Score: 1

      The only reason for DS-lite, as I understand it, is to provide services for IPv4, which can't happen w/o NAT. That's the simple fact - the moment you try to support IPv4 @ all, NAT is involved. What DS-lite makes different is that the external connection is an IPv6 public address, eliminating the need for that network to have a public IPv4 address (which in a depleted world is just not there) and just using private addresses for nodes that absolutely must be IPv4

      If a customer wants inbound connections w/ IPv4, they are out of luck once IPv4 depletes - NAT can't achieve that w/o going higher than Layer 3. So such customers would do well to embrace IPv6 as well, and only use IPv4 for downstream IPv4 connections.

      Frankly speaking, since the ISPs would prefer an IPv6 switchover due to the ease of use & administration, what are the stopping points? Can't be the general customers - all the mainstream OSs - Windows 7/8.x/Phone 8, OS-X, Linux, BSDs, Android, iOS, et al support IPv6, and can be enabled automatically, if that happens to be the connection. It's either the ISPs outdated equipment, which may not support it, or it may be websites that are still IPv4 only. For the last, what are the favorite OSs of web servers? How many of those are not IPv6 capable? Again, a similar list - Windows Server 2008/12, Linux, BSDs are what are used: how many web servers are still on Tru64 or Irix or UNIXWARE? So web servers that are still on IPv4 are there b'cos their Admins either didn't bother making them dual stacked, or didn't know how. Yeah, it would be nice to have more people know how to deploy IPv6 on their networks, but I'd argue that except for some dated equipment, there is no reason that most gear can't be updated to support IPv6 (via routing tools like OpenWRT, pFsense, Tomato, et al)

    96. Re:About time! by mark-t · · Score: 1

      Since when is a link local ip in ipv6 *not* localhost? Note, link-local, not site-local, the latter of which would correspond to a subnet.

    97. Re:About time! by stoatwblr · · Score: 1

      Mainly becvause IPv4 was a kludge only intended to last 5-10 years.

    98. Re:About time! by stoatwblr · · Score: 1

      clawing back the various underused /8s would gain a few months at best. It's not worth the hassle.

    99. Re:About time! by stoatwblr · · Score: 1

      CGN is bloody expensive to implement and keep running - far more expensive than getting IPv6 allocations.

      At some point CGN operators would end up _paying_ large IPv4 holdouts to go to IPv6 because it's cheaper than letting the status quo continue.

    100. Re:About time! by stoatwblr · · Score: 1

      Yup. I've been beating my head against carrier NATing for 15 years (it's been common in SE asia for a long time as a cheapskate way of getting IP space). It breaks a lot of stuff.

      If "Internet" == http, then CGN works. For just about everything else it breaks.

    101. Re:About time! by jbolden · · Score: 1

      CGN is a fantasy the carriers are clear about that. It is popular on /. with the "can't do" crowd that's taken over IT but not with a single carrier I've ever met. Besides ARIN hates the idea and going to something without regulatory approval is dangerous.

      I don't follow your comment about paying though. Even if carriers offered CGN they could drop it at a later date when as the contracts expired and force the move that way and/or just keep raising fees for IPv4. I suspect the fees are what they are going to do.

    102. Re:About time! by unixisc · · Score: 1

      Site local is Site-Unique - fc00::/6. It was substituted by Unique-local - fd00::/6. Both of these are universally unique, but non-routable IPs. Link-local addresses, OTOH, is the equivalent of private addresses on IPv4, or what's available on a subnet. Loopback is just ::1/128

    103. Re:About time! by Bengie · · Score: 1

      Link local addresses are visible to the entire broadcast domain, unless you firewall it off. Loopback will not be seen by others.

    104. Re:About time! by Bengie · · Score: 1

      Much of the internet is reached by client nodes using NAT+UPNP now. CGNAT does not support UPNP, which allows transparent port forwarding. A lot of stuff will break with CGNAT.

    105. Re:About time! by Bengie · · Score: 1

      If you're remotely getting viruses, then you're getting hacked. Please use a patched modern OS and make sure you're not using weak passwords.

    106. Re:About time! by mark-t · · Score: 1

      fe80::/64 addresses are automatically assigned locally, by the stack... and no two machines on the same subnet will ever have the same one anyways. I suppose it's theoretically possible to have the same IP on two different machines that start out unconnected and then you connect them together while they are still active, creating an ip conflict, but in reality, I'm not too sure how serious a problem this is. We're talking about over 18 quintillion choices here.... the likelihood of them picking the same one is pretty small in the first place, even if they are unable to verify that they are unique because they are unconnected. (when they are connected on a subnet, it's my understand that such automatically generated addresses *are* guaranteed to be unique on the lan).

      Anyways, the number of use cases for actually needing separate loopback addresses is really quite small, since there are tens of thousands of port numbers available for any given IP anyways, and there are usually workarounds for managing multiple virtual servers even on a single IP and port through dependance on DNS for some of the most common protocols. Nonetheless, after doing some additional research, it appears that 1::/32 is also being presently considered as a range to offer additional loopback addresses. Look up "A Larger Loopback Prefix for IPv6". As far as I can tell, it is still in the draft stage, though and it may not have enough use cases to justify its inclusion.

    107. Re:About time! by mark-t · · Score: 1

      It's my understanding that fc80::/64 is assigned automatically by the stack, and is guaranteed to be unique on a subnet without requiring any external IP issuer.

    108. Re:About time! by mars-nl · · Score: 1

      It kills the internet as it once was and how it was intended, i.e. every host can directly contact any other host (only limited by firewalls when necessary). The fact that most people noways just just google.com, facebook.com and that was about it, is sad. That is not internet, that is google-net and facebook-net.

    109. Re:About time! by unixisc · · Score: 1

      Why would that be the case? When IPv4 took hold, 32-bit CPUs were common, and even 64-bit CPUs came reasonably early, the earliest being from MIPS in the 1990s. There were several lightweight 64-bit CPUs from companies like QED, IDT such as the R4600. So something like IPv6 could have been supported on that w/o much difficulty.

    110. Re:About time! by stoatwblr · · Score: 1

      The point about CGN is that it's a way of ipv6 users contacting ipv4 sites - OUTSIDE the network doing CGN.

      If there are only a few popular ipv4 sites left and the vast majoritty of users are on ipv6 then it may be cheaper for the companies running the CGN kit to pay those ipv4 sites to get up to ipv6 speed, than to keep running the CGN gear (this is unlikely to happen, mostly CGN operators will just switch off the nat units and the ipv4 sites will adapt or die)

      $orkplace (A large UK university) has gone from "we don't plan to deploy ipv6 this decade, ipv4 will be fine until then" to "we need to get ipv6 working in the next 12 months" - I think it finally sunk in that the reason for going to IPv6 when everyone else does is mainly because if you don't, you drop off the radar of those who are ipv6 only.

      Many many organisations (including large ISPs) have the attitude "we've got all the ipv4 we need, we're ok" and are going to face a world of hurt when they find that they can't talk to ipv6 networks. ISPs in particular will have to get themselves sorted - quickly - or face losing customers. (Several UK ISPs are _still_ providing ipv4-only DSL units to their endusers)

      CGN is already in heavy use for mobile phone networks. My logs show that most accesses to local resources coming from the big wireless carriers in the UK only come from a handful of IP addresses, but there are thousands of users behind them. It's causing a particular problem with ssh sessions as they're running very short idle timers before breaking the NAT.

      (Let's not even go into the FUD being spread about ipv6 firewalling being harder than ipv4...)

    111. Re:About time! by stoatwblr · · Score: 1

      Forgot to say: ARIN disapproval or not is not "regulatory". They can't legislate CGN out of existance, merely ask that carriers don't use it.

    112. Re:About time! by kasperd · · Score: 1

      You got the names and prefixes wrong. fc00::/6 and fd00::/6 is actually the same prefix since they only differ in the 8th bit, and /6 indicates only 6 bits are significant. Also that /6 is not allocated to one specific purpose. Half of it is allocated and the other half is reserved.

      Site local used to be FEC0::/10, but it has been deprecated because it was not well-defined, what the boundaries of a site is. It was replaced with unique local addresses, which are only routed locally, but should be globally unique. FC00::/7 has been allocated for this. FC00::/7 was split into two halves with different allocation policy. In FD00::/8 you can create your own /48 by simply generating 40 random bits and append those to the 8 bit prefix. The result could for example be fd1d:19b8:d39f::/48. This allows the scope of such prefixes to overlap, since there will only be a conflict if the two randomly chosen 40 bit strings by chance are identical. Due to the "birthday paradox" you can expect to be part of one million different overlapping scopes before you run into a conflict. If such conflicts should happen, some central management may be needed, which is what FC00::/8 is reserved for.

      --

      Do you care about the security of your wireless mouse?
    113. Re:About time! by kasperd · · Score: 1

      It's my understanding that fc80::/64 is assigned automatically by the stack

      An address from fe80::/64 is assigned automatically. But by default you'll only get one per network interface. Moreover any application using them must indicate which interface it want to communicate on, as it is intended for communication between two hosts not separated by a router, and addresses could be duplicated on multiple interfaces. That makes it overly complicated to use, if you really just want local communication i.e. between two processes on the same computer.

      --

      Do you care about the security of your wireless mouse?
    114. Re:About time! by unixisc · · Score: 1

      Two questions:

      1. Why did the address range FEC0::/10 have to be deprecated, rather than simply redefine it as Unique local?

      2. Why didn't IANA define an allocation mechanism whereby FC00::/6 would get assigned by the RIRs, and they would simply assign non-overlapping ranges to everyone, thereby guaranteeing unique prefixes? They wouldn't be routable, but would still be useful for things like VPNs

  2. And yet Akamai deserves a /10 by Anonymous Coward · · Score: 2, Insightful

    Pretty outrageous that the whole of North America has to go on a diet earlier because Akamai somehow needs a whole fucking /10.

    ARIN's behavior has made it clear: you can get all the IPs you want as long as you're a big guy paying big fees. But a small company asking for a /22? Go away, small businesses don't deserve to be able to do business.

    1. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 1

      Akamai actually uses all that shit for SSL. Until SNI is universal, deal with it. Xerox still has a /8 they don't even route so...

    2. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      SNI is universal, unless you're running Windows XP or Android 2.0.3. If you're running either, upgrade. I mean come on, SNI was standardized in 2003 and wasting IPs just for a few legacy clients that ought to have a broken Internet to force them into upgrading is absurd.

    3. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      But a small company asking for a /22? Go away, small businesses don't deserve to be able to do business.

      How would you decide which small companies get the blocks? There are only 4,194,304 of those blocks in IPv4. This would mean one company per 1700 people in the world, and that's not exactly small.

    4. Re:And yet Akamai deserves a /10 by rs79 · · Score: 1
      --
      Need Mercedes parts ?
    5. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 2, Insightful

      RIR's general policy is if you can prove you require it, you can have it. Akamai clearly have the documentation to prove that they will burn through an entire /10 within a reasonable time frame (It was 3 months at the end in the RIPE region. I'm unsure about ARIN).

      Akamai are huge. They claim to provide 15-30% of all web traffic (http://www.akamai.com/html/about/facts_figures.html). Stands to reason that they will likely utilise that all fairly quickly.

      As for a company being unable to get a /22? Again, I'm not in the ARIN region, but I'm fairly confident if you can prove you are multi-homed - no problem. You can read their allocation policies here: https://www.arin.net/policy/archive/ipv4.html#multihomed

    6. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 1

      LOL at upgrade Android.

    7. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      I browse the web with lynx. What the hell is Akamai and why is it getting such privilege?

    8. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      How badly does the typical small-business need a PROVIDER-INDEPENDENT /22? That is the only reason to go to ARIN for address space - otherwise request addresses from your upstream.

    9. Re:And yet Akamai deserves a /10 by PRMan · · Score: 3, Insightful

      Akamai is one of the few companies in the US that is actually using a large allocation they were given. They're the LAST ones you should be complaining about.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    10. Re:And yet Akamai deserves a /10 by IamTheRealMike · · Score: 2

      SNI is universal, unless you're running Windows XP

      That's a pretty huge unless!

    11. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      According to MS, if you still use Windows XP after last week, you should replace the cdkey sticker on the outer case with one that says "hack me" /sarcasm

    12. Re:And yet Akamai deserves a /10 by petermgreen · · Score: 1

      Or pay them a shitload of money to keep providing patches.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    13. Re:And yet Akamai deserves a /10 by QuantumRiff · · Score: 1

      Windows XP works fine with SNI, as long as your using firefox (not sure about chrome and other browsers) IE on XP has the problem.

      --

      What are we going to do tonight Brain?
    14. Re:And yet Akamai deserves a /10 by elfprince13 · · Score: 1

      They're a CDN that serves 30% of all Internet traffic. They get whatever they want, because if they don't, the internet starts sucking.

    15. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      Fuck Xerox. The annoying bitch in their commercials told me that they're ready for real business. She didn't drop to her knees and give me a blow job immediately, so I didn't believe it.

    16. Re:And yet Akamai deserves a /10 by Anonymous Coward · · Score: 0

      Experiencing the same issue and aggravation over that /10 assignment as well. We requested a /21 recently (justified) and we were granted only a /22. We went thru the /22 quickly (as we indicated) and now today we went to ask for another /22 - I bet all April 23rd 2014 requests aren't going to be taken seriously.

      I don't understand how Akamai can justify a need for a /10. Why aren't they getting things like /21's /20's etc as they need them. Why a giant /10?! It is outrageous and insulting to us little guys.

      All the big guys got to do is clean up their blocks to gain efficiency. Us little guys will be hard out of resources soon. We won't be able to take on customers. I 'love' how ARINs solution is 'go deploy IPv6'. They should be shoving IPv6 down the throats of the big guys (AKAMAIs) to promote the adoption of v6.

    17. Re:And yet Akamai deserves a /10 by kimvette · · Score: 1

      You use Akamai every day and don't even realize it.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    18. Re:And yet Akamai deserves a /10 by unixisc · · Score: 1

      Can't you get provider independent /32 or/24? /22 seems a lot even for an organization that uses several ISPs in several countries

  3. Phase Four!?!? Oh noes by Anonymous Coward · · Score: 1

    Now capitalism kicks in and people start buying and selling spare IP4 addresses.

    Kinda like that other thing they ain't making any more of....land.

    1. Re:Phase Four!?!? Oh noes by Anonymous Coward · · Score: 3, Funny

      I've got a whole block of IPv6 addresses available, cheap... act now, before the rush!

    2. Re:Phase Four!?!? Oh noes by fuzzyfuzzyfungus · · Score: 1

      Hey, now that Intel is trying to sell quarks NICs, we could be looking at a real crunch in the IPv6 space... (and, at a tray price of over $9/unit, large atoms and even most molecules becoming enormously expensive.)

    3. Re:Phase Four!?!? Oh noes by NatasRevol · · Score: 2

      Finally, Xerox will have a revenue increase?

      --
      There are two types of people in the world: Those who crave closure
    4. Re:Phase Four!?!? Oh noes by MrNemesis · · Score: 2

      Hmmm... sounds like there's a market for selling hardware to mine IPv6 addresses. Just need to set up some sort of exchange...

      --
      Moderation Total: -1 Troll, +3 Goat
    5. Re:Phase Four!?!? Oh noes by ultranova · · Score: 1

      (and, at a tray price of over $9/unit, large atoms and even most molecules becoming enormously expensive.)

      Why? Even U-238 would cost only $9/quark * 3 quarks/baryon * 238 baryons, for a grand total of $6426. Sure, it's a lot for home users, but for enterprise uranium with a guaranteed minimum half-life and ISO-certified electron orbitals that's a bargain.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  4. World IPv6 Day by Anonymous Coward · · Score: 1

    It's going to be interesting to see this year.

  5. Sigh by koan · · Score: 2, Funny

    There's no place like ::1

    --
    "If any question why we died, Tell them because our fathers lied."
    1. Re:Sigh by Anonymous Coward · · Score: 0

      So, how much for your ::1?

    2. Re:Sigh by Anonymous Coward · · Score: 0

      Is that your web site at ::1? I must say it looks great!

      In all fairness, it looks a lot like mine so I'm biased.

  6. Re:Don't worry, the internet only has months to li by Anonymous Coward · · Score: 0

    Thanks, Obama!

    Oh wait.... never mind.

  7. Wasn't allocation always the problem? by GodfatherofSoul · · Score: 4, Interesting

    Years back, my boss got a whole class C for a company with ~5 employees and network footprint nothing more than one website. Maybe they can get some of the corporations with class As to give some back? (yeah yeah I know)

    --
    I swear to God...I swear to God! That is NOT how you treat your human!
    1. Re:Wasn't allocation always the problem? by afidel · · Score: 5, Informative

      Nope, it takes longer for existing tenants to vacate space than it has been for ARIN to allocate new addresses (ie it would take MIT 5 years to re-engineer their network to free up say half of their allocation, but at the rate we've been using new addresses that space would last less than 10 days, so why should an organization put in 5 years of work to help with 10 days of usage?) so the solution is IPv6.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      I was going to post the same thing.

      If they raise the cost of blocks of addresses sufficiently, many orgs will relinquish their under-utilized addresses and get a smaller block.

    3. Re:Wasn't allocation always the problem? by drew_92123 · · Score: 1

      I used to work for an ISP, we had a few class Bs and a bunch of class Cs, I remember the first time we were running low and decided to check what our customer that had been assigned blocks of addresses were actually using... maybe 10% were actually in use.

      We started assigning smaller blocks to companies that couldn't justify keeping their existing blocks but soon gave up. People are greedy, even with something as seemingly simple as reclaiming unneeded addresses. It was like trying to pry a steak out of a starving dogs mouth... just not a good idea.

    4. Re:Wasn't allocation always the problem? by rs79 · · Score: 1

      Which will fragment blocks and increase the size of the routing table.

      --
      Need Mercedes parts ?
    5. Re:Wasn't allocation always the problem? by jareth-0205 · · Score: 4, Insightful

      I was going to post the same thing.

      If they raise the cost of blocks of addresses sufficiently, many orgs will relinquish their under-utilized addresses and get a smaller block.

      And what? We'll buy ourselves another couple of years, at the most? Just fix the problem now and we don't have to worry about this anymore.

    6. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      Which will fragment blocks and increase the size of the routing table.

      You would have to play around with the math but they should be able to handle this too.
      Basically give discounts for less fragmentation, pay people to defragment or even force
      defragmentation at certain spots if necessary.

      It should be simple enough to look at the tables and look where you can buy up useful
      blocks to defragment. If it's worth defragmenting then buying a block here or there for
      $1/ip or even $100/ip and giving them a different block should be very doable.

    7. Re:Wasn't allocation always the problem? by Wycliffe · · Score: 2

      People are greedy, even with something as seemingly simple as reclaiming unneeded addresses.

      So why not use the greed to your advantage? Charge $10/ip and see how quickly they give back the ones they aren't using.
      ARIN could do the same thing. If ARIN charged just $1/ip per month you would see a huge influx of returning ips.

    8. Re:Wasn't allocation always the problem? by MikeBabcock · · Score: 1

      The biggest problem has always been the global routing tables. Routing IPv6 is going to get ugly soon too, but we'll see how that turns out.

      --
      - Michael T. Babcock (Yes, I blog)
    9. Re:Wasn't allocation always the problem? by medv4380 · · Score: 3, Funny

      IPv6 is the re-engineer the network solution.

    10. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      Except you can't if you were a LIR. And RIPE wanted you to be a LIR if you had more than /19. If you charged money for IPs and not for the internet service, RIPE could revoke all your addresses.

    11. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      Can't they just assign big enough blocks for pretty much any ISP ever and still have tons of blocks left over for each zone to give to ISPs that may set up shop there later?

      Wouldn't it even reduce routing tables since you could eliminate neighboring blocks not being in neighboring locations? if everything :::5 and down goes through your first port and all the rest go through your second port, you have a very small routing table. By having all those IPv4 blocks being divided a lot more nowadays, your routing tables get a bunch bigger.

    12. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      Because all the tenants can vacate space _simultaneously_.

    13. Re:Wasn't allocation always the problem? by petermgreen · · Score: 1

      ie it would take MIT 5 years to re-engineer their network to free up say half of their allocation

      I call BS, it would only take that long if it was a low priority job. If they were told in no uncertain terms to sort it out or be kicked out of the internet I'm sure they could deal with it much quicker than that.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    14. Re:Wasn't allocation always the problem? by WaffleMonster · · Score: 1

      Years back, my boss got a whole class C for a company with ~5 employees and network footprint nothing more than one website. Maybe they can get some of the corporations with class As to give some back? (yeah yeah I know)

      This comes at cost of increased route disaggregation pressure for little benefit in return.

    15. Re:Wasn't allocation always the problem? by DarkOx · · Score: 1

      That is pretty common an usual pretty much the smallest direct allocation you can get. Nobody will route anything smaller than that. Lots of ISP will subnet C allocations and resell smaller ranges, but than they are not your allocation so if you change ISPs you WILL be changing ip address ( for all be a few edge cases if that is really a problem than you are doing it wrong), what sucks through is it usually becomes a pain to get pointer records in DNS updated etc; as you need to get whoever controls the zone to do it for you.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    16. Re:Wasn't allocation always the problem? by Unknown+Lamer · · Score: 2

      If MIT had to give up some of their IPv4 addresses, maybe we'd get IPv6 openafs this century ;)

      --

      HAL 7000, fewer features than the HAL 9000, but just as homicidal!
    17. Re:Wasn't allocation always the problem? by DarkOx · · Score: 2

      It might be possible for HP, Apple, or Xerox to move things around that quickly but I doubt a University could get that done at any priority.

      I know people who work on university networks. They face the most bizare requirements. At Michigan for instance essentially any two ports anywhere on the entire campus have to be able to be made layer 2 adjacent upon request.

      Big research universities like MIT have odd problems like academics doing "network research" collaborating with different colleges withing the university, large portions of the network managed by academic teams rather than the "Network Engineers" to many cooks in their kitchens.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    18. Re:Wasn't allocation always the problem? by petermgreen · · Score: 1

      With IPv6 they are trying to allocate blocks in such a way that they almost never have to give a network a second block that is not continguous with it's initial block. So it should hopefully convege much closer to one block per multihomed network than IPv4 has.

      Still the number of multihomed networks is only going to grow over time and whatever you do each such network is going to want at least one entry in the global routing table.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    19. Re:Wasn't allocation always the problem? by QuantumRiff · · Score: 1

      We are relatively small, and trying to get our own /24. You need a /24 to do multihoming, most BGP routers won't propogate anything smaller than a /24.

      --

      What are we going to do tonight Brain?
    20. Re:Wasn't allocation always the problem? by Wycliffe · · Score: 1

      Except you can't if you were a LIR. And RIPE wanted you to be a LIR if you had more than /19. If you charged money for IPs and not for the internet service, RIPE could revoke all your addresses.

      Most ISPs and even cloud providers seem to charge me for IPs. The price range anywhere from $1 per month per IP
      to as high as $20 per month per static IP sometimes even more as they will sometimes require you to upgrade to
      "business class" to have a static IP.

    21. Re:Wasn't allocation always the problem? by HappyPsycho · · Score: 1

      A bit curious as to how you intend to look at the BGP tables and tell that a block is not in use? I understand maybe do a swap ips to make up a larget block to "defrag" the ip space but that requires at least one of the parties has enough free space to perform the swap (something that is going to become even harder to get as time goes on).

      Also what concession do you give to an ISP having multiple internet links of which I want half my ips to use link A and the other half using link B? This problem gets even worse when you get out of the theoretical 2 uplinks (very few ISPs have such a small number of links) and start looking at say the Teir 1 providers (of which there are aprox 14) which all have to peer with each other, even if you assume they have a single link between each other there is a formidable task in balancing load between the various links available.

    22. Re:Wasn't allocation always the problem? by suutar · · Score: 1

      How about we give out 240/8 to 255/8 first? That range is reserved for "future addressing modes", presumably something like how 225-239/8 are reserved for multicast, but I haven't heard of any new addressing modes on the horizon.

      But ignoring that for the moment... there's 126 class As (1-126; 0 and 127 are special), but only 40 of them are "legacy"; the rest are already handled by ARIN, RIPE, etc. So at 10 days each, that would handle 13 months of demand, after which, back to hosed. Not really a big win.

    23. Re:Wasn't allocation always the problem? by profplump · · Score: 1

      PTR records can be delegated with a CNAME record. Not that anyone does this, but it's the recommended solution when delegating IPs.

    24. Re:Wasn't allocation always the problem? by Megane · · Score: 1

      Nope. Microsoft fucked that a long time ago.

      http://packetlife.net/blog/201...

      The class E space has 268 million addresses and would give us in the order of 18 months worth of IPv4 address use. However, many TCP/IP stacks, such as the one in Windows, do not accept addresses from class E space and will not even communicate with correspondents holding those addresses. It is probably too late now to change this behavior on the installed base before the address space would be needed.

      And you forgot to mention class D space, which is pretty sparsely defined. I seem to recall it uses about 5 out of 16 /8 size blocks, not to mention that IPv4 multicast is basically a failure anyhow, so really all 16 /8 blocks are wasted.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    25. Re:Wasn't allocation always the problem? by Megane · · Score: 1

      Except that when the really big blocks were assigned, it was a one-time fee.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    26. Re:Wasn't allocation always the problem? by sfcat · · Score: 1

      If MIT had to give up some of their IPv4 addresses, maybe we'd get IPv6 openafs this century ;)

      AFS (in OpenAFS) stands for Andrew File System. Andrew, as in Andrew Carnegie, as in Carnegie Mellon, not MIT.

      --
      "Those that start by burning books, will end by burning men."
    27. Re:Wasn't allocation always the problem? by suutar · · Score: 1

      Bleah. I skipped the class D space because it's officially assigned to a purpose, but you're right, it could probably be slimmed down... but I bet something has hardcoded the notion that D is multicast and should be handled weirdly, so it's probably really in the same boat as E. Oh well...

    28. Re:Wasn't allocation always the problem? by Yaztromo · · Score: 1

      I call BS, it would only take that long if it was a low priority job. If they were told in no uncertain terms to sort it out or be kicked out of the internet I'm sure they could deal with it much quicker than that.

      Perhaps, but it's still potentially going to be a very large, costly job, which probably won't gain enough addresses to make it worth anyones while. It would still take them at least a few months.

      The problem here is how many organizations with a large allocation (like a /8) have allocated these addresses within their organizations. Typically, they don't go around doling out the addresses in a completely contiguous manner -- they may have done something akin to setting up a /16 for each building (they would have received their address block before CIDR, and thus would have had to spit things along glassful lines), out of which different labs may have got a /24 to use however they wanted. Readdressing all of these and setting up new routes for all of these subnets is a big job for a large organization like MIT. You'd have to combine subnets together, which would change the routing topology, and compress everything down into a few /16's to make the returned address space contiguous.

      You could return non-contiguous space, however this has a serious negative impact on world-wide routing tables. You can't just add a few million /28's to the global routing table (that is, you can't just say "hey, here's a few hundred thousand non-contiguous groups of 16 addresses we aren't using, let's give them back!").

      And after putting all that effort into making their address space more contiguous (while still allowing room for future growth), they'd probably wind up with enough addresses to extend IPv4 for a month or two at best -- at which point, they might as well have put the effort into migrating to IPv6 instead.

      Giving unused address space only slightly delays the inevitable. It does't postpone it indefinitely. If you're going to do the work, you might as well do it right the first time and get everything running on IPv6.

      Yaz

    29. Re:Wasn't allocation always the problem? by Anonymous Coward · · Score: 0

      I bet if university internet suddenly went down, priority will suddenly go up and problem will get fixed.

      Taking stuff away is not going to work however.

    30. Re:Wasn't allocation always the problem? by dissy · · Score: 1

      Sadly a surprisingly large number of core routers out there won't even propagate a /24, despite being the official minimum. A lot still dropped /22's and smaller, some even dropping /20's.
      I can understand end point routers doing this, as Cisco RAM isn't exactly cheap and in the end that normally would only actually effect the users at that one end point. But I was surprised how many were actually backbone routers! (I'm looking at you cogent)

      Back in 1996 or so the ISP I worked for had to get a /20 just to avoid all that crap, which arguably was more than overkill (we did dialup, webhosting, and "low speed" colo aka T1 speeds)

      Ironically, a couple years after that ISP went out of business, ARIN still didn't revoke the IP block or ASN despite being a year behind on payment.
      The contacts were still in my name (apparently being the last sysadmin to bother updating them) so after checking with the founder I ended up making the payments and keeping the IP block myself for another few years.

      I relinquished the /20 back to ARIN in 2007 mainly due to the shortages, and they reallocated it to another company not 3 months later (their standard at the time was to not reallocate for at least one full year)

      There are still days when I wonder if I should have kept it... But at least I can say I did my part as a good netizen.

    31. Re:Wasn't allocation always the problem? by thegarbz · · Score: 1

      Why not kick the can down the road? It works well enough in the worlds biggest and most powerful government.

    32. Re:Wasn't allocation always the problem? by unixisc · · Score: 1

      ...once, and not have to worry about that aspect of it again for ~ the next 100 years

    33. Re:Wasn't allocation always the problem? by unixisc · · Score: 1

      Not just that, w/ IPv6 and say, a /48, or even a /56, a university can support all the colleges and academic teams and whatever other combination they have, put them all on adjacent networks and have them all on a common Internet2 node. Speaking of which, is Internet2 going IPv6 anytime soon?

    34. Re:Wasn't allocation always the problem? by FireFury03 · · Score: 1

      I call BS, it would only take that long if it was a low priority job. If they were told in no uncertain terms to sort it out or be kicked out of the internet I'm sure they could deal with it much quicker than that.

      How exactly are you going to kick them off the internet? If IANA withdrew MIT's IPv4 allocation, nothing would happen - MIT would still be making BGP announcements for those addresses, all the other ISPs would still be listening to the BGP announcements, MIT's network would continue running. The only way you're going to "kick" them off the internet is by everyone independently filtering MIT's announcements - that kind of coordination just isn't going to happen. And you can't allocate those addresses to anyone else, because who on earth is going to want a bunch of addresses that aren't going to work reliably because someone else is already announcing them?

      No, the only way you can reclaim an IPv4 allocation is with the cooperation of the organisation that is using them. And on the whole, this seems a bit pointless - even if you reclaimed *all* of these large pre-IANA allocations, it will buy a few weeks at best. That might be worthwhile if those few weeks were actually going to be used to help the transition onto IPv6, but that won't happen - we have had 16 years to migrate onto IPv6 and it hasn't happened; everyone's been putting off the whole thing for 16 years - buying a few extra weeks just means they will put it off for a few extra weeks. Its pretty clear now that significant migration isn't going to happen until it is forced through things simply not working any more with IPv4.

      Frankly, *no one* should have any networking equipment that can't do IPv6 these days - the normal replacement cycle dictates that networking gear will have been replaced several times already since it was clear that IPv6 was necessary - anyone who didn't have "IPv6 support" as mandatory requirements for any new equipment bought over the past 5 or more years is a complete idiot.

    35. Re:Wasn't allocation always the problem? by Bengie · · Score: 1

      IPv6 is being given out with reserved adjacent IP blocks to reduce fragmentation for future requests and almost all routing is hierarchical. IPv6 is doing away with the "flat model" that is causing core router's tables to balloon, and is instead going with a hierarchical design that makes it easy to route.

  8. 2 more phases left... by Anonymous Coward · · Score: 0

    Phase 1 Recieve last IPv4 /8 Adresses
    Phase 2 Giveaway down to last 3x IPv4 /8 Adresses
    Phase 3 Giveaway down to last 2x IPv4 /8 Adresses
    Phase 4 Giveaway down to last 1x IPv4 /8 Adresses
    Phase 5 ???
    Phase 6 Profit

    1. Re:2 more phases left... by unixisc · · Score: 1

      Phase 5: IPv6 or bust

  9. Hmm... by Anonymous Coward · · Score: 1

    What comes first, a widespread NATed internet or IPv6?

    1. Re:Hmm... by GrpA · · Score: 1

      Nat'ed IPv6... No one will use direct allocations. IANA says you can't own them anyway, so what's the point?

      FC00::/7 is all I ever see lately.

      GrpA

      --
      Enjoy science fiction? "Turing Evolved" - AI, Mecha, Androids and rail-gun battles. What more could you want?
    2. Re:Hmm... by Anonymous Coward · · Score: 1

      NAT is already here..

    3. Re:Hmm... by petermgreen · · Score: 1

      I suspect the former.

      ISPs NEED to provide their customers with the ability to access resources on the IPv4 internet from end devices that only support IPv4. For most ISPs (massive ones that have problems with running out of private v4 space excepted) who can't give all their customers public IPs the easiest way to achive that will be to deploy NAT44. Once they have deployed the NAT44 there is no real pressure to get arround to deploying IPv6 as well.

      Some ISPs may consider building a v6 only access network and using ds-lite instead of using traditional NAT44. There are certainly advantages to that approach but I suspect it will be the exception rather than the rule and mostly seen with ISPs who are building new networks from scratch.

      We may see some NAT64 (especially on mobile) but as well as philosophical objections (messing with dns) it has the big problem that it can't support v4 only client devices.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    4. Re:Hmm... by Bengie · · Score: 1

      Routers are cheap and fast, but stateful firewalls to handle NAT are expensive and slow. They will not scale to everyone having 1gb and soon enough, 10gb Internet.

  10. 1/8 and 240/8-255/8 by jcomeau_ictx · · Score: 1

    285 million addresses reserved for no compelling reason. sure, let's push onwards to ipv6, but saying "our hands are tied" when over 1/16th of the entire space is still available is a bit irritating.

    1. Re:1/8 and 240/8-255/8 by compro01 · · Score: 2

      Great. Wave your wand, fix every piece of internet infrastructure that regards those reserved addresses as unroutable, and we can put off exhaustion for about 9 months, at best.

      Anything you do to IPv4 is nothing but a short-term stop gap. The address space is simply too small for the modern internet.

      --
      upon the advice of my lawyer, i have no sig at this time
    2. Re:1/8 and 240/8-255/8 by fuzzyfuzzyfungus · · Score: 2

      285 million addresses reserved for no compelling reason. sure, let's push onwards to ipv6, but saying "our hands are tied" when over 1/16th of the entire space is still available is a bit irritating.

      Would you want to be the guy who pokes every existing and legacy system that makes stupid and/or dangerous assumptions about reserved blocks being reserved permanently? You'd hope that that wouldn't be an issue; but finding out could be exciting indeed.

    3. Re:1/8 and 240/8-255/8 by Anonymous Coward · · Score: 0

      240 has been marked as multicast for several *generations* of operating systems. You would need to patch the entire internet to change that. (and also convince all the people who are actually *doing* multicast to re-ip out of that range first...so patch the internet twice, really)

    4. Re:1/8 and 240/8-255/8 by jcomeau_ictx · · Score: 1

      224/4 is multicast. 240/4 could be made available. https://tools.ietf.org/html/dr...

    5. Re:1/8 and 240/8-255/8 by jcomeau_ictx · · Score: 1

      sure, I'm game. I once had a /16 flapping for hours after I made a routing change after a 3-pint lunch and couldn't figure out how to undo what I'd done. and of course my co-workers rightly hung me out to dry.

    6. Re:1/8 and 240/8-255/8 by TheRealMindChild · · Score: 1

      9 months? If we exhausted addresses that fast, we would have ran out in the 90's

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    7. Re:1/8 and 240/8-255/8 by compro01 · · Score: 3, Insightful

      Addresses were being allocated at a rate of about 2 /8s per month just before IANA's pool was depleted back in 2011.

      If a new range of addresses became available, then, barring a policy shift, I would expect them to go at a similar rate, if not faster.

      --
      upon the advice of my lawyer, i have no sig at this time
    8. Re:1/8 and 240/8-255/8 by Megane · · Score: 1

      As I posted in another sub-thread: http://packetlife.net/blog/201...

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  11. A useful case study because it's not catastrophic by Anonymous Coward · · Score: 5, Interesting

    The IPv4 address exhaustion is a useful case study in human behavior in response to resource exhaustion.

    http://www.albartlett.org/presentations/arithmetic_population_energy_transcript_english.html

    Relevant quote: "Remember our conclusion from the cartoon of one person per square meter; we concluded that zero population growth is going to happen. Let’s state that conclusion in other terms and say it’s obvious nature is going to choose from the right hand list and we don't have to do anything—except be prepared to live with whatever nature chooses from that right hand list. Or we can exercise the one option that’s open to us, and that option is to choose first from the right hand list. We gotta find something here we can go out and campaign for. Anyone here for promoting disease? (audience laughter)"

    In this case, fortunately, it's extremely unlikely that violence and death will occur as a result of this specific resource exhaustion, but the study of human behavior in response to the resource shortage is telling.

    We've been aware for years that zero IPv4 address availability is going to happen. It's absolutely certain. The only way to make it not happen, or not *care* that it happens, is to do something about the problem. But of course, even for such a technically manageable problem, humanity on the whole chooses to do nothing. The exact same thing will happen for fossil fuel exhaustion, arable land exhaustion, etc.

    And now nature will choose for us from the right-hand list of IPv4 exhaustion: here comes corporate greed, lawsuits, slow and inconvenient CGNs (one bad actor in your ISP's network causes you to be banned from the services you use), etc.

    Humans are hard-wired to be reactionary, not proactive -- and at that, only reactionary to immediate problems. "Oh, I can't get a new IPv4 address. What do I do?" or "Oh, I can get a new IPv4 address, but it's too expensive. What do I do?" -- These are the kinds of things we will start thinking about, and making people start to care. NOT "Oh, we better deal with this problem that is likely to happen in 5 years."

    As flawed as we are, it's probably a good thing that we won't survive long enough to leave our solar system and populate the cosmos. We don't deserve it. We're just too *dumb* as a species.

  12. It didn't matter whether it was last year or next by gjh · · Score: 3, Interesting

    It didn't matter whether it was last year or next...IP usage was accelerating into the wall anyway. The GOOD part about this is that now the US is out of addresses certain parts of the Internet industry are more likely to take IPv6 seriously.

    Sadly, ISPs in other parts of the world have proven adept at further avoiding the problem by downgrading consumer connections to carrier-grade NAT, so we have another 5 years of eking out of old order before people REALLY have to take notice.

  13. Oh well we can all just use NAT by Anonymous Coward · · Score: 1

    NAT works great, no issues here [Ducks!]

    Kidding guys :)

    1. Re:Oh well we can all just use NAT by Anonymous Coward · · Score: 0

      Says the Anonymous Coward. Looks like somebody already NATed your name.

  14. Re:It's the end of the world as we know it. by blahbooboo · · Score: 0

    "It's the end of the world as we know it, and I feel fine"
      --- REM
    http://www.youtube.com/watch?v...

  15. We are not anywhere near running out of addresses. by ErikTheRed · · Score: 4, Interesting

    We're running out of free ones. And like any freely available resource, they've been squandered. Once the free supply is exhausted, they'll simply no longer be free - meaning that actual incentive will exist to conserve them and organizations will have incentive to sell unneeded blocks. Economics 101, people.

    --

    Help save the critically endangered Blue Iguana
  16. Re:It didn't matter whether it was last year or ne by badfish99 · · Score: 5, Insightful

    Now that addresses have run out, they have become a valuable resource for the ISPs that own them. If those ISPs implement IPv6 then there will be no shortage of addresses, and they will lose all their value.

    So the monopolist ISPs will now do everything in their power to prevent IPv6 from being adopted.

  17. Re: A useful case study because it's not catastrop by Anonymous Coward · · Score: 0

    You assume wrongly that most of the world behaves like the british and people from english-speaking countries, who still haven't made the move to the universal measurement system, and neither have reformed their language to make grammar and pronounciation rules consistent.

  18. Re:We are not anywhere near running out of address by Anrego · · Score: 2

    I doubt the organizations with those large blocks will sell them unless they become very expensive (which I don't think will happen for a long time). The costs of restructuring the network for a lot of these companies would far outweigh the gains.

    What I see as far more likely is ISPs implementing carrier grade NAT as the default, and potentially charging a small fee for those who need a unique IP. The vast majority of users won't care, and as long as getting an IP if you run a game server or use skype or whatever is an easy process, it's actually not a bad solution. I figure we've got 10 years or so before we actually see IPv6 really take off.

  19. Re:We are not anywhere near running out of address by jareth-0205 · · Score: 1

    We're running out of free ones. And like any freely available resource, they've been squandered. Once the free supply is exhausted, they'll simply no longer be free - meaning that actual incentive will exist to conserve them and organizations will have incentive to sell unneeded blocks. Economics 101, people.

    Why would you choose that option when we have a way of bypassing it? Isn't progress generally about creating plenty? We have the ability to create plenty, and not have to deal with buying and selling IP addresses. Just because you can create a market doesn't mean you should.

  20. Re:We are not anywhere near running out of address by pr0nbot · · Score: 5, Funny

    Clearly we should have invested years ago in finding renewable sources of IP addresses...

  21. Re: A useful case study because it's not catastrop by Sique · · Score: 1

    There are no languages where grammar and pronounciation rules are completely consistent. Spanish and Indonesian come close with regards to grammar, and Dutch and Czech, when it comes to spelling vs. pronounciation, but there just is no language which is completely consistent. Even artificial languages like Esperanto have their inconsistencies.

    --
    .sig: Sique *sigh*
  22. Re:We are not anywhere near running out of address by Kurast · · Score: 2

    Because there is a very high one-time-only cost involved in switching to ipv6, compared to a small running continuous cost of continuing in ipv4, and for now, it is advantageous to become in ipv4. No one wants to be the one to switch first.

    Just think of all sort of problems large ISPs will have to deal in terms of support if they switch to ipv6, in terms of phone service, visits, substitution of cable modems, support for old machines running none/bogus ipv6 implementation.

    Just think of all the programs coded years ago, with ipv4 hardwired in (I know 4to6, but your client does not).

    Not easy as flick a switch.

  23. Re: A useful case study because it's not catastrop by ArcadeMan · · Score: 1

    still haven't made the move to the universal measurement system

    I'm glad to know I'm not the only one using the universal Klapagorg measurement system!

  24. Re:A useful case study because it's not catastroph by SteveFoerster · · Score: 1

    As flawed as we are, it's probably a good thing that we won't survive long enough to leave our solar system and populate the cosmos. We don't deserve it. We're just too *dumb* as a species.

    How is anyone supposed to take a person like this seriously?

    --
    Space game using normal deck of cards: http://BattleCards.org
  25. 3 February 2011 by Anonymous Coward · · Score: 0

    That was over three years ago, why is this news?

    1. Re:3 February 2011 by kasperd · · Score: 1

      That was over three years ago, why is this news?

      ARIN is not IANA.

      --

      Do you care about the security of your wireless mouse?
  26. So let's finally move on by dkman · · Score: 2

    So let's finally move on to IPv6. ISPs, I'm looking at you.

    --
    I refuse to sign
  27. Some people.. by Anonymous Coward · · Score: 0

    I run several Xen virtual servers rented from a VPS vendor.. They come with two ip addresses, one of which I don't need. I asked them about returning the extra address to them, as I didn't need it.. They said "no, we have plenty" ... ????? Hey! I thought the ipv4 address space was running out... hmmm.. guess not.. At least THIS vendor does ipv6.. each vps comes with 3 (count 'em THREE) ipv6 addresses.. WAAAY cool!!

    1. Re:Some people.. by petermgreen · · Score: 1

      Hey! I thought the ipv4 address space was running out... hmmm.. guess not.

      Or maybe the vendor in question are doing it to "justify" getting a larger allocation from the RIR, once IP space really runs out they can reconsider their policy.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  28. Re:It didn't matter whether it was last year or ne by MikeBabcock · · Score: 2

    Most of the ISPs I've dealt with here in Canada do not offer routable IPv6 allocations to users. They certainly don't readily offer static ones for business use like they do with IPv4.

    --
    - Michael T. Babcock (Yes, I blog)
  29. And yet... by Dahan · · Score: 2
    Obligatory comment on Slashdot articles about IPv4 exhaustion or IPv6:

    $ host -t aaaa slashdot.org
    slashdot.org has no AAAA record

  30. Re:We are not anywhere near running out of address by Anonymous Coward · · Score: 0

    If you go by http://ipv4auctions.bstocksolutions.com/ a /8 is worth roughly USD 100M. There are a few unused ones by companies out there...

  31. Thanks! by Marrow · · Score: 1

    You brightened my day.

  32. Re: A useful case study because it's not catastrop by Anonymous Coward · · Score: 0

    You are wrong. Bulgarian is a language with 100% persistent pronunciation.

  33. Re:We are not anywhere near running out of address by Dagger2 · · Score: 2

    Except this still won't fix the fact that v4 is simply too small.

  34. Re:It didn't matter whether it was last year or ne by petermgreen · · Score: 1

    so we have another 5 years of eking out of old order before people REALLY have to take notice.

    Possiblly much more than that.

    XP and andriod 2.x are dying. They aren't dead yet but in a few years time their relavence will likely have declined to the level where website operators think it reasonable to stop supporting their default browsers. Once that happens we will be able to use SNI (and tell the holdouts still on XP to "use firefox or chrome damnit")

    Once that happens it will be possible to put multiple SSL websites behind one IP reducing the IP demand on the hosting side. With end lusers put behind CGN, SSL web hosting running multiple sites per IP and basic VM hosting using front end load balancers to let them share IPv4 IPs it should be possible to keep IPv4 going for a long time.

    One interesting question is what price will IPv4 addresses reach, currently it seems to vary from about $7-$25 per address depending on block size (http://ipv4auctions.bstocksolutions.com/)

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  35. Re:We are not anywhere near running out of address by pushing-robot · · Score: 5, Funny

    Here at DHCP, we're committed to providing only renewable and conflict-free IPs.

    --
    How can I believe you when you tell me what I don't want to hear?
  36. Re:We are not anywhere near running out of address by petermgreen · · Score: 1

    Why would you choose that option when we have a way of bypassing it?

    Because people will do what is individally best for them, not what is best for the community as a whole.

    If I want to run a server for the general public to access over the internet it needs to have an IPv4 address until such time as the vast majority of clients can reliablly access IPv6 servers (I would not consider teredo to be "reliable", it's overcomplicated and fights against NAT rather than working with it).

    Similarly if I want my users to be able to access resources on the public internet I need IPv4 addresses for the intent side of my nat boxes until such time as the vast majority of servers are available on IPv6.

    If I deploy IPv6 it will not change whether those systems need IPv4 addresses. To do that requires OTHER PEOPLE to deploy IPv6 which they are often unintertested in doing.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  37. Re:It didn't matter whether it was last year or ne by Anonymous Coward · · Score: 0

    So now the exact same thing that happened with land will happen with "land".

  38. Re: A useful case study because it's not catastrop by Anonymous Coward · · Score: 0

    You clearly have absolutely no clue of how linguistics work.

    First of all, your Bulgarian claim is not true: https://upload.wikimedia.org/wikipedia/commons/1/12/Bulgarian_dialects_by_Todor_Bozhinov.png

    Secondly, if it were, you'd just have to wait for around 25 years to start noticing things changing.

    You know which languages *could* (but don't) have 100% persistent pronunciation? Dead ones.

  39. And in other news... by hpa · · Score: 1

    A large number of companies from all over the world set up shell companies in Africa.

  40. 4G mobile should have been IPv6 only by Animats · · Score: 4, Insightful

    Newer mobile phones should have been IPv6 from the beginning. China mandated that years ago. T-Mobile is IPv6. (You can supposedly open up an end to end IPv6 connection between two T-Mobile phones). It's suprising that the cellular phone companies didn't fix this, since they have control of both network and handset.

    1. Re:4G mobile should have been IPv6 only by Rising+Ape · · Score: 1

      The phone companies themselves don't always control the handsets. Yes, they supply phones as part of a contract package but there are also a lot of people (like me) who got a phone from elsewhere and brought it on to the network.

      That's no reason not to do IPv6 though.

    2. Re:4G mobile should have been IPv6 only by Anonymous Coward · · Score: 0

      T-Mobile is IPv6.

      I have T-mobile, I have all IPv6 internal network and IPv6 compatible newer generation phone and tablet, yet T-mobile serves me an IPv4 address. They won't route any IPv6 packets I try to send. So this is entirely false.

      This, FWIW, is the entire problem. There can be articles on slashdot, nerds everywhere can cry how stupid people are for not switching and how doomed we are (just scroll up for that), but the bottom line is, there is nothing more the 99.9999999999999999% of us can do. The ISPs aren't running IPv6, none of them. If they are, I have yet to see one that offers it anywhere I've lived in the US...and I LOOK FOR IT. Just like I look for >5mbps internet but it doesn't ever seem to be anywhere I live. For the record, I currently live in downtown LA. There's fiber everywhere, if you're a big business, or living in a luxury highrise...they might even be IPv6, I don't know. But for us regular pleebz...

    3. Re:4G mobile should have been IPv6 only by Anonymous Coward · · Score: 0

      T-Mobile is pure v6. No one else is. And we all know that everyone else (ATT, Verizon, etc.) are all in the ditch because they missed the v6 boat, right? So T-Mobile is proof positive that without v6, we are doomed. Or not? I'm so confused. Is ATT doomed because they are not on v6? Or is T-Mobile eating everyone's lunch because without v6 your phone is a joke? So confused... Especially since I don't have T-Mobile! haha

    4. Re:4G mobile should have been IPv6 only by rsmith-mac · · Score: 1

      My understanding is that all of the mobile carriers are running CGN these days, so whether or not they support IPv6, they're not consuming much in the way of IPv4 addresses.

    5. Re:4G mobile should have been IPv6 only by thegarbz · · Score: 1

      Irrelevant, the critical point here is that we have a new grade of devices being built from the ground up with new hardware both locally and at the exchanges / towers, and yet they were IPv4 + nasty workaround.

      The cost of doing things IPv6 to begin with would have been non-existent and the money saved on the carrier grade NAT could have been put to IPv6/4 gateways which the ISPs could have used for other purposes too.

      But no. We as a race shoot ourselves in the foot with the uttermost care and precision.

    6. Re:4G mobile should have been IPv6 only by unixisc · · Score: 1

      I thought that the LTE spec did call out for IPv6 ONLY

    7. Re:4G mobile should have been IPv6 only by Anonymous Coward · · Score: 0

      Except for the "free" markets in Japan and USA, operators doesn't have handset control.

  41. Re: A useful case study because it's not catastrop by Sique · · Score: 1

    Bulgarian doesn't even note emphasis in the writing, and also not the length of the vowels, thus it doesn't have a fully written pronounciation. It is still possible to follow the full set of pronounciation rules in Bulgarian and still read a text completely non-understandable for a native speaker.

    --
    .sig: Sique *sigh*
  42. Enjoy your CGNAT. by Anonymous Coward · · Score: 0

    Now:

    Static IP Address: Requires a business account, plus $20/month.

    Future:

    Public IP Address: Requires a business account, plus $20/month.
    Static Public IP Address: : Requires a business account, plus $100/month.

    (Note: Numbers are completely made up. But in my experience, that's is how most residential ISPs structure it.)

  43. Re: A useful case study because it's not catastrop by IcyWolfy · · Score: 1

    That is wrong, first thing we learnt in class was (and from my textbook):
    Slashdot doesn't support unicode, so, I'll be using romanization
    @ = er golyam
    j = i kratko

    "In both e- and i- verbs, there is a lack of correspondance between pronunciation and spelling in the "I" and "they" forms:

    cheta', cheta't are pronounced as if written chet@', chet@'t;
    pi'ya, pi'yat are pronounced as if written pi'jo, pi'jot
    "
    In addition to other irregularities: s@bota, nominally /subota/, is often pronounced /supta/ (u in these examples are IPA (ram-horn)

  44. great job, idiots by Anonymous Coward · · Score: 0

    the way to get people to respect scarcity is to give them price signals. I guess the concern was that your favorite actor would buy a /8 for no reason, but lots of idiots have blocks for no reason now.

  45. Re:We are not anywhere near running out of address by WaffleMonster · · Score: 1

    We're running out of free ones. And like any freely available resource, they've been squandered. Once the free supply is exhausted, they'll simply no longer be free - meaning that actual incentive will exist to conserve them and organizations will have incentive to sell unneeded blocks. Economics 101, people.

    There has been pressure for near two decades now in the form of allocation policy and documentation requirements where lack of plentiful IP resources has lead directly to proliferation of 1:Many NAT.

  46. Re:We are not anywhere near running out of address by petermgreen · · Score: 1

    If you go by http://ipv4auctions.bstocksolu... a /8 is worth roughly USD 100M.

    This assumes that either the seller is allowed to split the block or the price per IP for a /8 is comparable to the price per IP for a /8 block is comparable to the price per IP for the much smaller blocks you see sold on that site.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  47. /8 is quite a bit by allo · · Score: 1

    remember, there were only 256 /8 nets. So a /8 is a lot of adresspace.

    1. Re:/8 is quite a bit by ChrisSlicks · · Score: 1

      16777214, take away a few after subnetting.

      US DoD has 11 /8's, about 184 million addresses or about 5% of the total global assignable address space. I also suspect that 99.99% of that address space is not internet routed.

  48. Lesson here folks by Alomex · · Score: 0

    There is lesson to be learned here:

    Every fix length field should have a reserved value for an extension. .

    Back in the early days of the internet each header bit was precious, so it was important to have packet headers as small as possible. However even then we could easily have reserved say 255:255:255:8 as the extensible value of the IP address.

    By the time they are needed, namely in present day, it is a rather trivial mod to make network gear which reads another 32 bits past the end of the standard TCP/IP headers to collect the extended IP address, and presto IPv4 address shortage is gone.

    1. Re:Lesson here folks by Typical+Slashdotter · · Score: 1

      I don't think that is a good technical solution. First of all, after everyone decides how best to change to protocol to use extended addresses, you still have the same problem of having to upgrade existing equipment. You say that is is just a "trivial mod," but it's not like implementing IPv6 is particularly difficult---rolling out any modification whatsoever will be about as hard as switching to IPv6. However, with your suggestion, the situation is must less predicatable for users during the transition phase. As it stands, if two hosts have routed IPv6 addresses, they can talk to each other over IPv6, assuming someone hasn't made a serious error. With the "extended address" scheme you propose, if I have an extended address and I try to talk to another host, how do I know if I should be able to? Does the other host support extended addresses? Does every piece of routing equipment between me and them support extended addresses? How would I know these things, and what's to stop the routing table from changing and breaking a previously working path?

    2. Re:Lesson here folks by WaffleMonster · · Score: 1

      There is lesson to be learned here:

      Every fix length field should have a reserved value for an extension. .

      Without careful planning in advance of deployment reserved fields in protocols often go unused as subsequent modifications are not operationally viable.

      Variable length addressing would have absolutely solved the problem only if it was defined from the beginning addresses may be between x and y bits in length and all systems handling addresses are expected to support the full range of address lengths.

      The act of simply reserving a bit without defining what it does in advance solves NOTHING and does NOT result in a better solution than parallel deployment of IPv6.

      By the time they are needed, namely in present day, it is a rather trivial mod to make network gear which reads another 32 bits past the end of the standard TCP/IP headers to collect the extended IP address, and presto IPv4 address shortage is gone.

      Not on a production network it aint. You have no way of knowing what equipment along path supports what, which part of routing infrastructure does or does not support an extension, no way to understand a-priori which addressing system to use. You have no way of knowing whether that which touches an IP address supports the extended length. Without parallel deployment or flag day it is the same or worse than IPv6.

    3. Re:Lesson here folks by Alomex · · Score: 1

      I don't see any merit in your technical objections. Why would "everyone decide how best to change to protocol to use extended addresses"? What I'm suggesting is that the extension behavior should have been there from the get go,

      Similarly rolliing at an extension is in now ay "about as hard as switching to IPv6". IPv6 was designed to be a flag day protocol. How is this about as hard as "extending in a minor way the current protocol without need for interruption?"

      I can carry on, but all you are doing is pointing out minor technical issues which would have needed to be taken care of. Yup, so they would have. Still it would have been easier to use an existing protocol.

    4. Re:Lesson here folks by Alomex · · Score: 1

      Without careful planning in advance of deployment reserved fields in protocols often go unused as subsequent modifications are not operationally viable.

      Correct, which is why I did not propose an extension field, but rather a reserved value.

      Variable length addressing would have absolutely solved the problem only if it was defined from the beginning addresses may be between x and y bits in length and all systems handling addresses are expected to support the full range of address lengths.

      Sure, all you do is you define the behavior but do not require the devices to actually do anything about it. Only later do you require the behavior to take place.

      Not on a production network it ain't.... Without parallel deployment or flag day it is the same or worse than IPv6.

      Let me FTFY:

      Without parallel deployment or flag day it is at worse the same but likely much easier than IPv6.

      Seriously think about it. Every issue you have with extensible fields you would have with a new protocol, while by virtue of being fully backward compatible you would avoid some of the worst issues of "flag day" IPv6, which we haven't yet managed to roll out 16 years after first proposed.

    5. Re:Lesson here folks by FireFury03 · · Score: 1

      I don't see any merit in your technical objections. Why would "everyone decide how best to change to protocol to use extended addresses"? What I'm suggesting is that the extension behavior should have been there from the get go,

      Your "trivial mod" involves redesigning hardware, so not really trivial at all. High speed routers do routing in hardware - making them understand longer addresses involves building new hardware to handle it.

      How is this about as hard as "extending in a minor way the current protocol without need for interruption?"

      Because it isn't without need for interruption. Using IPv6 is only possible when all the network gear between the sender and recipient understands IPv6. In your scenario with an "extension", using the extended addresses would only be possible when all the network gear between the sender and recipient understands the extended address. So in short, you either have to specify the whole "extended address" system right at the start and ensure all the hardware supports it (which is basically the same as saying "we should've just used IPv6 from the start"), or you have to make everyone upgrade their hardware in exactly the same way as they do to support IPv6 anyway.

      I can carry on, but all you are doing is pointing out minor technical issues which would have needed to be taken care of.

      Sure, if you don't understand much about how networks work you can handwave all the problems away as "minor technical issues", but once you actually learn how networks work you realise that they aren't minor at all, especially when you consider that IPv4 was intended to run on the hardware that existed in the 70s, which would make most solutions way too expensive.

    6. Re:Lesson here folks by Alomex · · Score: 1

      Your "trivial mod" involves redesigning hardware,

      As does IPv6, but my mod is light years easier than those of IPv6 which is what you propose.

      In your scenario with an "extension", using the extended addresses would only be possible when all the network gear between the sender and recipient understands the extended address.

      Not at all. That is the only solution you could think of, but there are smarter, simpler solutions. E.g. route all 255:255:255:8 packets to an extended field aware router down-stream (not unlike 255:255:255:255 are "routed" to the DHCP local server).

      You couldn't come up with a solution in five seconds and declare the whole thing impossible, which goes back to my point, you are raising minor technical objections and treating them as major showstoppers.

      Sure, if you don't understand much about how networks work you can handwave all the problems away as "minor technical issues",

      He he, kiddo the software developed by my team routed more traffic in a second than all the torrents you've ever downloaded in your lifetime put together, which explains why what looks as an insurmountable problem to you is just another day at the office for me.

      That you do not see how to do something doesn't mean other people with more experience can do it either.

    7. Re:Lesson here folks by WaffleMonster · · Score: 1

      Seriously think about it. Every issue you have with extensible fields you would have with a new protocol, while by virtue of being fully backward compatible.

      The core problem is all about ADDRESSING. What protocol headers look like is largely irrelevant.

      Quibbling about approach x vs. y when both only result in different arrangements of fields appearing in a header very few actually touch is counterproductive.

      Asserting "fully backward compatible" naturally implies maintenance of two separate address spaces given untouched gear would not be able to "do anything about" new unimplemented bits.

      One might argue it would be better to deploy support for an extended address space and designate a flag day after which we would expect the new space to be globally open for business .. yet this isn't a serious option that can be deployed in the real world. It has to be done incrementally and at the end there has to be pressure on outliers to switch or be left in the dark.

      Sure, all you do is you define the behavior but do not require the devices to actually do anything about it. Only later do you require the behavior to take place.

      Don't know how one goes about asking the whole world to start "doing something about it" without incurring massive cost.

      Every issue you have with extensible fields you would have with a new protocol

      My assertion is playing games with protocol fields does not make deployment appreciably any different or better than IPv6.

      What you suggest could have been done in IPv4 you could have used options field to define extended addressing without having to burn separate L2 protocol number. Yet we still would have had to touch everything which sees an address.

      Most importantly to enable ADDRESSING of new space while maintaining a fully reachable network for all participants you still need to concurrently deploy parallel addresses in both current and extended address spaces for duration of transition period. This includes CGN to make up for lack of available address space.

      When I connect to www.google.com my system does an AAAA query because it knows I have IPv6 connectivity. If the AAAA query returns an IPv6 address it also knows the remote system can be reached via IPv6. If there is no AAAA then it knows to use IPv4 instead. The incremental and easily understood rules for use of one address space over the other is a critical part of a successful transition.

      Some of it is counter-intuitive requiring appreciation for operational requirements of content and eyeball networks. A number of smart and well-intentioned people invented all manner of transition technologies to help bridge communications between networks yet in the end they only got in the way hindering adoption.

      While by virtue of being fully backward compatible you would avoid some of the worst issues of "flag day" IPv6, which we haven't yet managed to roll out 16 years after first proposed.

      IPv6 is in production use by millions currently enjoying exponential growth. >40% of my Internet traffic by volume is IPv6.

    8. Re:Lesson here folks by Alomex · · Score: 1

      given untouched gear would not be able to "do anything about" new unimplemented bits.

      There in lies your key error. You can have those packets be routed to an extended-field capable router using existing BGP/IGP routing protocols. The switches do not need to know anything about the extended field behavior to do that.

      My assertion is playing games with protocol fields does not make deployment appreciably any different or better than IPv6.

      IPv6 was particularly badly designed in terms of ease of implementation. It has many other virtues but easiness of implementation ain't one of them. A Jackson-Pollock-design-style protocol is likely easier to implement than flag day IPv6.

      This is exactly why we are running out of IPv4 addresses and we still do not implement IPv6. If you want to carry on arguing that IPv6 is the superior choice you are welcome to it, but you have a mountain of facts and 16 years of trying against you.

      >40% of my Internet traffic by volume is IPv6.

      Oh wow. You win then. An IPv6 fanboi,erh,sorry,strong proponent routes ~40% of his traffic using IPv6. Color me impressed.

      Seriously dude, reread your statement. You are damning IPv6 with faint praise when even a proponent cannot get the count over ~40% the day before we run out of IPv4 addresses.

      Globally IPv6 makes for ~2% of traffic sixteen years after it was first proposed.

    9. Re:Lesson here folks by Anonymous Coward · · Score: 0

      That's not how it works. Hardware expects a VERY specific structure for the headers. Adding extra bits makes routing ambiguous. This is not feasible in 100gb ASIC based routers. We're running up against the laws of physics, no branching, need easy static lookups.

      "it is a rather trivial mod to make network gear" says the person who doesn't realize that you can't change the hardware and thinks designing a datacenter like Google is simple. "Just add an index on every web page, it's a trivial change".

    10. Re:Lesson here folks by Bengie · · Score: 1

      Your mod is only "easier" in your head because you don't understand the issues. The hardware designs and network stack designs would be dramatically more complex and slower and still not backwards compatible, and even worse, ambiguous in some cases!

    11. Re:Lesson here folks by Anonymous Coward · · Score: 0

      As I said, everything you say against my proposal applies squared to IPv6 which of course you refuse to address since you know that really tips the argument in my favor. I'm signing off this discussion.

    12. Re:Lesson here folks by kasperd · · Score: 1

      However even then we could easily have reserved say 255:255:255:8 as the extensible value of the IP address.

      It already is! Along with all the other IP addresses in the range from 240.0.0.0 through 255.255.255.254. That's 268435455 IPv4 addresses reserved for extensions. But nobody has been able to come up with a way to utilize those reserved addresses to solve the IPv4 shortage. But that's not the only range that people have tried using in order to solve the problem. The 192.88.99.0/24 range is reserved as well, for a well-defined purpose, which was intended to help getting IPv6 deployed. It did not help, it may even have slowed down IPv6 deployment by 1-2 years because it lead to broken IPv6 connectivity for some users.

      The list of header fields, where values have been reserved, in order to help in this upgrade is long.

      • The version field: 6 through 9 are all reserved for different candidates for the next protocol, but everybody have now settled on one of them.
      • The protocol field: The value 41 can be used to embed an IPv6 packet within an IPv4 packet. And several other values are reserved for IPv6 related protocols.
      • IP addresses: As mentioned lots of addresses were reserved from the start with very little success. A much smaller range was reserved later with a bit more success, that unfortunately backfired.
      • Options: Option type 145 is reserved for extending the addresses in a way that maintained full IPv4 compatibility (until IPv4 addresses are exhausted).

      The only gaining any traction was IPv6 and tunneling of IPv6 over IPv4. The lack of IPv6 adoption is not due to any technical issue with IPv6. And none of the other ideas have technical advantages over IPv6, which would have given them better traction. The lack of deployment is entirely caused by lack of incentive, which would be the same regardless of which technical solution was chosen.

      By upgrading you are faced with some technical challenges, and there is little benefit to upgrading until a significant fraction of the Internet has upgraded. By postponing the upgrade you are hurting the entire Internet, but as long as you are hurting your competitors at least as much as you are hurting yourself, it still makes sense from a business perspective.

      Rationing of IPv4 addresses should not have waited until 2011. Rationing of IPv4 addresses should have started way earlier, by 2004 it was already clear that lack of incentive to upgrade was the main blocker for IPv6 deployment. At that point rationing could have been introduced in such a way as to keep the installed base of IPv4-only hosts constant. The rule should have been, that you new networks could get the IPv4 addresses they needed for dual-stack deployment, and existing networks could get new IPv4 addresses only if they could document, that they had upgraded an equivalent number of IPv4 hosts to dual stack. Had that been done, there would have been 40% dual stack hosts by the time IPv4 addresses ran out.

      But pointing out what could have been done smarter in the past is not very productive. I am very interested in hearing any suggestions on what can be done today in order to accelerate IPv6 deployments. What is clear today is that IPv6 is the future. There is no other viable option. The IPv4 network is going to fall apart slowly as more and more NAT is being deployed. And any other protocol, which is not IPv4 or IPv6, is not going to be a real option. Even if a technically superior protocol showed up, IPv6 would still have a 20 year head-start.

      --

      Do you care about the security of your wireless mouse?
    13. Re:Lesson here folks by Alomex · · Score: 1

      And any other protocol, which is not IPv4 or IPv6, is not going to be a real option. Even if a technically superior protocol showed up, IPv6 would still have a 20 year head-start.

      The IPv6 head start is so minimal that Linksys shipping a new shimming protocol with its NAT routers would exceed IPv6 usage within six months.

      IMHO that is still the way to go, because IPv6 just isn't happening.

    14. Re:Lesson here folks by kasperd · · Score: 1

      The IPv6 head start is so minimal that Linksys shipping a new shimming protocol with its NAT routers would exceed IPv6 usage within six months.

      Wrong. Shipping routers with support for a new protocol doesn't make it happen. If that was all it took, we'd all have been running IPv6 years ago. Getting a new protocol deployed means deploying hardware and software, which can support it on the entire route from one end to the other. And it means network operators have to get addresses, setup peerings and turn it on for their customers. There is no way Linksys could achieve all of that within six months.

      IMHO that is still the way to go, because IPv6 just isn't happening.

      IPv6 is happening. It is happening 13 years later than it should have, but at least it appears it is not falling any further behind. At the current rate we'll reach 50% dual stack by 2018 (and by 2030 we'll probably be 50% dual stack again as IPv4 will be phased out). The question is how bad the network will get in the meantime. Users of any P2P service have already been experiencing problems due to NAT, and that will keep getting worse until those services move to IPv6.

      Will it get so bad, that end users realize something has gone horribly wrong, and start demanding somebody take action? Or will ISPs manage to deploy IPv6 with the majority of users being blissfully unaware what is happening?

      Suggesting another solution because "IPv6 isn't happening" makes no sense. By the time you'd have a working standard for any alternative to IPv6, you'd be up against IPv6 deployed to half the internet. And deploying it couldn't be significantly simpler than IPv6, which means ISPs would be waiting for a decade to see if anybody else was deploying it first. And why would any ISP want to deploy a competitor to IPv6 which was less tested than IPv6 and did not have nearly the same market share? It took more than a decade to get them moving on deploying one replacement to IPv4, they are not suddenly going to support two replacements.

      --

      Do you care about the security of your wireless mouse?
    15. Re:Lesson here folks by Anonymous Coward · · Score: 0

      Shipping routers with support for a new protocol doesn't make it happen.

      I agree, I was implicitly assuming that it took off.

      Getting a new protocol deployed means deploying hardware and software,

      Depends on the protocol. For the most part NATs did not require software changes though they break some applications if not done properly.

      IPv6 is happening.

      I ran IPv6 for a few months last year and kept an eye of how often I was able to establish a connection with it. Answer? Almost never. If you call that "happening" we have a different definition of the term.

    16. Re:Lesson here folks by kasperd · · Score: 1

      Getting a new protocol deployed means deploying hardware and software,

      Depends on the protocol. For the most part NATs did not require software changes though they break some applications if not done properly.

      NAT breaks some applications. You cannot implement a NAT in a way that is guaranteed to not break any applications. Does that mean NAT is never done properly?

      Some applications may work through a NAT automatically, while others may require lots of work. In certain situations it is just plain impossible to get an application working through a NAT at all. Application developers are not supposed to spend their time working around NAT. That time should be spend on building new features instead.

      If an application works flawlessly without NAT, but fails in the presence of a NAT, that just demonstrates that NAT is a problem.

      You can deploy a NAT and still have some applications work without changes. But lots of development time has been wasted the last two decades on working around NAT. NAT could be deployed without needing involvement from ISPs, which is why it is so widespread today. But that is also a significant reason why IPv6 deployment is going so slow. Had NAT never been invented, we could all have been running IPv6 today, and things would work much better than they do.

      IPv6 is happening.

      I ran IPv6 for a few months last year and kept an eye of how often I was able to establish a connection with it. Answer? Almost never. If you call that "happening" we have a different definition of the term.

      Are you asking for servers with IPv6 support? Google, YouTube, facebook, and Akamai are a few examples with IPv6 support. Were you never able to establish a connection with any of them?

      I use IPv6 on a daily basis. Whenever I am on a network without IPv6 support, I realize how much more difficult it makes my work, not to have IPv6 access. Luckily Teredo works from most networks (but only for connecting with sites, that care enough about reliability to deploy their own Teredo relays).

      --

      Do you care about the security of your wireless mouse?
  49. Re:A useful case study because it's not catastroph by Anonymous Coward · · Score: 0

    You're not supposed to. This is called pandering to your base, however, as most people on Slashdot are anti-human trendy-wannabe psuedoliberals who really, honestly believe that the human race is a cancer upon the planet. They are the cancer in the human race.

  50. Re:We are not anywhere near running out of address by WaffleMonster · · Score: 2

    Because there is a very high one-time-only cost involved in switching to ipv6, compared to a small running continuous cost of continuing in ipv4, and for now, it is advantageous to become in ipv4. No one wants to be the one to switch first.

    Nobody is switching to IPv6 they are *adding* IPv6. IPv4 is not being turned off by anyone well into the foreseeable future.

    Most large content providers are already offering service via IPv6 and millions already have IPv6 access via their ISPs.

    Just think of all sort of problems large ISPs will have to deal in terms of support if they switch to ipv6, in terms of phone service, visits, substitution of cable modems, support for old machines running none/bogus ipv6 implementation

    The migration to IPv6 takes a while and does not involve turning off IPv4 anytime soon. There is no need to rush to replace gear. It will eventually break or become obsolete in the next few years anyway.

    Not easy as flick a switch.

    For most consumers it will be easier than a flick of a switch. They get it without having to expend any effort at all or ever even knowing they have it. This happens either immediately or after their old router or CE has broken and gets replaced.

  51. Who needs Bitcoins? by mendax · · Score: 1

    Think of it. Here is this scare resource, IPv4 addresses, and no more are going to be allocated in North America. I see great potential in profit, online exchanges opening up allowing the trading of IP addresses, etc. etc. To quote the Ferengi, my lobes are tingling.

    --
    It's really quite a simple choice: Life, Death, or Los Angeles.
  52. What is this IPv4 you speak of? by WillAffleckUW · · Score: 1

    We've been using IPv6 for about a decade now.

    Didn't you get the memo?

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:What is this IPv4 you speak of? by unixisc · · Score: 1

      Where?

  53. Necessity is the mother of all invention by EmagGeek · · Score: 1

    Human beings are terrible at planning ahead. Just look at the financial condition of just about any modern nation. Knee deep in debt with only plans to spend more money without thinking about how to pay it off. It takes bankruptcy for them to change their ways.

    Same goes for renewable energy - yeah there is some token adoption as long as it is heavily subsidized. It will take actual depletion of the current resource to drive full-scale adoption.

    IPv4 is just another example of human-driven resource exhaustion with immense resistance to the future plan until the current resource is actually completely exhausted.

  54. Time to moveon by Anonymous Coward · · Score: 0

    The same could have been said about the buggy whip manufacturers. Everything eventually needs to move on and improve. That's just how it goes. If you're on XP and you're on the internet, you shouldn't be and we should make it hard on you, not the other way around.

  55. Re:A useful case study because it's not catastroph by Anonymous Coward · · Score: 0

    Well, he's thought about it a bit more than you have, obviously.

    Tell us: what precisely do you find in his statement hard to take seriously, and what are your thoughts that you can present as an alternative viewpoint?

  56. Time will tell by Anonymous Coward · · Score: 0

    I started to follow this on 2000. "The end is here sooon". Now it starts to feel like generation after generation of new forget their history. Almost like some great war in the past. Kids just don't learn.

  57. Re:So lets take the whole address space back by lister+king+of+smeg · · Score: 1

    Sure do that if you want to break the whole fucking internet overnight.

    --
    ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
  58. Re:We are not anywhere near running out of address by Anonymous Coward · · Score: 0

    I prefer the slightly cheaper black market blood IPs.

  59. Also older mobile devices can't deal with SNI by Anonymous Coward · · Score: 0

    Add to it millions of mobile devices that can't deal with TLS (forces you to use SSLv3), or SHA-2 (forces certificates to use SHA1), or large RSA (force certificates to a maximum of 2048 bits)... and cannot deal with SLI at all.

    Universal SLI support is still at least 5 years away.

    Not to mention NATed IPv4 is the bane of P2P...

  60. Re:We are not anywhere near running out of address by Camel+Pilot · · Score: 1

    What! No way... Drill Baby Drill should be the new manta.

  61. LACNIC (latin america) is NOT EXAUSTED by Anonymous Coward · · Score: 0

    Meh, I know it is asking too much of /. editors, but LACNIC (which covers latin america, which includes South America entirely) is still in phase 0.

    ARIN entered phase 4 with one /8 left. The other registries have different phasing. LACNIC has three more phases to go, it is still in "if you ask, we have it" mode (phase 0), and will remain in phase 0 until there is a /9 left (we're currently at 0,66 of the last /8, so we have a few weeks left in phase 0). It will enter phase 1 when there is one /9 left.

    I expect lots of shaddy business in the LACNIC region when phase 2 begins, which might well require that LACNIC deploy a rule that all resources received under phase 2 and 3 must never be sold or transferred.

    ARIN has always been weird (mostly because much of the pre-ASO allocations are in ARIN), I doubt they can do anything about people gaming their final phases to get IPs to sell. Other regions are a lot less tolerant of monetization of the IP address space and have increased control, so they can reclaim such IP and ASN resources easier than ARIN.

    1. Re:LACNIC (latin america) is NOT EXAUSTED by unixisc · · Score: 1

      How is AFRINIC?

    2. Re:LACNIC (latin america) is NOT EXAUSTED by Anonymous Coward · · Score: 0

      Well, sort of exhausted. I'll give you that LACNIC isn't officially in the last phase of IPv4 exhaustion, but that's like saying people don't die from the fall: It's the impact that kills them. Just because LACNIC has decided to use a ridiculously small buffer for IPv6 transitioning doesn't mean that LACNIC isn't practically out of addresses. LACNIC has fewer addresses left than all other RIRs, and LACNIC is, due to their policy decision, burning through the remaining addresses faster than the other RIRs. It's a matter of weeks before LACNIC hits IPv4 exhaustion head on, without any crumple zone to soften the crash.

  62. Was wondering when this would happen by Anonymous Coward · · Score: 0

    The future is now

  63. Re:We are not anywhere near running out of address by Darinbob · · Score: 1

    I think we can pipe some down from Canada.

  64. Re:It didn't matter whether it was last year or ne by Anonymous Coward · · Score: 0

    While technical innovations could theoretically make IPv4 last a while longer, the reality in Asia and Europe is that end users are seeing severely degraded service due to CGN, for example with VoIP services. New ISPs, on the hosting and the access side, can not get IPv4 addresses for all their needs. Making IPv6 work is basically their only option.

    IPv6 will be used, and when it can do the job, then there will be no point in sticking with IPv4 and all its complicated multiplexing methods.

  65. Re:A useful case study because it's not catastroph by Anonymous Coward · · Score: 0

    This is a false comparison. People are doing NAT to deal with IPv4 exhaustion. You can say NAT is bad, but so far it's worked out ok. People are not head in sands, they are simply postponing the cost until they are convinced it's needed.

  66. Re:We are not anywhere near running out of address by ultranova · · Score: 1

    Isn't progress generally about creating plenty?

    Progress is about creating plenty, yes. However, the granparent specifically cited economics, which is typically about creating an artificial shortage and then profiteering.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  67. Now is the time to create IPv5 by Anonymous Coward · · Score: 0

    IPV6 was built to solve a host of problems we don't have anymore, and introduces a bunch of new of problems we don't need.

    It's time to simply add an octet to IPv4. Balancing scalability with ease of use is important, and IPv6 failed at the second part.

    1. Re:Now is the time to create IPv5 by mars-nl · · Score: 1

      Not sure whether this is a serious response or whether it's meant to be funny.

      Finally we're ready to deploy IPv6 and you propose to invent a new protocol? I'm sure we can roll this IPv4 and IPv6-incompatible protocol in 10 years from now.

      So what are those problems that we don't have anymore? And what are exactly those problems that IPv6 creates?

    2. Re:Now is the time to create IPv5 by Zan+Lynx · · Score: 1

      I love it when people who don't know anything about networking invent solutions to problems. As if actual IETF engineers were all idiots.

  68. Re: A useful case study because it's not catastrop by Anonymous Coward · · Score: 0

    I don't know about grammar, but for pronunciation, reading Hiragana and Katakana (Japanese) seem to be 100% consistent. There is only one way in which I can read those individual characters. Also Korean seems to be 100% consistent.

    There are no languages where grammar and pronounciation rules are completely consistent.

    Have you really studied all 4000 or so written languages in the world to make that claim?

  69. What happens by Highland+Deck+Box · · Score: 1

    when we run out of IPv6 addresses? It's a serious and pressing concern, like what happens when Intel runs out of nanometres to cut off their processors. Fools, the lot of them!

    1. Re:What happens by Anonymous Coward · · Score: 0

      512bit, enough IPs for every atom in the multiverse.

  70. virtual network adapter by Anonymous Coward · · Score: 0

    I think he's talking about a virtual network adapter in the VM with a NAT subnet created specifically for those thse VMs. Just another way of natting a VM.

  71. Re:It didn't matter whether it was last year or ne by petermgreen · · Score: 1

    Making IPv6 work is basically their only option.

    Trouble is "Making IPv6 work" requires other people to deploy it. I dunno what things are like where you live but here in the UK the only access providers that offer IPv6 connectivity are the boutique ones.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  72. IPv6 by Anonymous Coward · · Score: 0

    without net neutrality will just be multiple pingable anal probes up you ass anyway. Who cares about IPv7 without decent standards, not me. I'd prefer the dark ages I think...

  73. Re:A useful case study because it's not catastroph by gonnagetya · · Score: 1

    We don't deserve it. We're just too *dumb* as a species.

    Fuck you. If you have or intend to have any children you'll change your tune very quickly. You MUST remain positive about the future of humanity or end up like one of those morons who thinks he knows better than everyone else but appears on the outside as a miserable cunt, someone no-one wants to spend any time with because they see the future as hopeless. Don't be one of those miserable cunts, please.

  74. Re:A useful case study because it's not catastroph by strikethree · · Score: 1

    As flawed as we are, it's probably a good thing that we won't survive long enough to leave our solar system and populate the cosmos. We don't deserve it. We're just too *dumb* as a species.

    As flawed as single celled organisms are, it's probably good that they will not survive long enough to leave our solar system and populate the cosmos...

    Evolution is still happening. The "we" that you are postulating will not exist in a thousand years. If we were to separate 2 groups of humans for a thousand years, it is possible that they would be totally separate species if there were sufficient evolutionary pressure.

    In other words, kill yourself* to improve the species if you think the current state of the human species is so terrible.

    *not saying that to be a dick, just pointing out that is how evolution happens: death of the organism, growth of the new slightly different organism.

    --
    "Someone needs to talk to the tree of liberty about its ghoulish drinking problem." by ohnocitizen
  75. Re:It didn't matter whether it was last year or ne by unixisc · · Score: 1

    Like I said elsewhere in this page, even if ISPs implement IPv6, they'll still need their IPv4 addresses for dual-stack connections, which will be needed as long as a majority of the customers are IPv4.

  76. Re:It didn't matter whether it was last year or ne by FireFury03 · · Score: 1

    Most of the ISPs I've dealt with here in Canada do not offer routable IPv6 allocations to users. They certainly don't readily offer static ones for business use like they do with IPv4.

    You can get IPv6 connections here in the UK so long as you pick your ISP carefully. Unfortunately, the last time one of my customers shopped for a new internet connection (i.e. expensive leased line), they directly asked the ISP if they did IPv6 and got a "yes" reply, and only after the connection was installed and paid for did it become apparent that the ISP lied. (unfortunately it wasn't important enough to the customer for them to kick up a proper fuss about the ISP mis-selling).

  77. Re:It didn't matter whether it was last year or ne by Anonymous Coward · · Score: 0

    If ipv4 address are rare, then other ISP's will offer ipv6 as a cheaper option.

    All we need is some ISP competition...

  78. Re:It didn't matter whether it was last year or ne by liamoohay · · Score: 1

    All we need is some ISP competition...

    And I want a pink unicorn.

  79. Types of 'private' addresses in IPv6 by unixisc · · Score: 1

    Since when is a link local ip in ipv6 *not* localhost? Note, link-local, not site-local, the latter of which would correspond to a subnet.

    What you are thinking about is 'Node-local', which is the loopback address - ::0 in IPv6. Note that this falls within the IPv4-compatible addresses, which is currently deprecated by the IETF. As Bengie pointed out, link-local is your subnet, where addresses are automatically assigned, and is fe80::/10. Unique-local addresses are fc00::/7, and a site-unique address fd00::/7 is also there: fc00::/7 is meant to be universally unique, but that would require the IANA or the RIRs assigning them, while fd00::/7 can be unique just to a site, or domain.

    In IPv4, all of the above tend to get conflated under 'private addresses'. Here, link-local and Site-Unique addresses are clearly delineated. The link-local addresses are what are randomly assigned by stack, and visible throughout the subnet.

  80. Worse than that by ryanov · · Score: 1

    There are plenty of other dependencies (OpenSSL versions, Apache versions, Java versions), so it's even worse than that.

    PS: I can't see what the hell you responded to -- it's not in the parent comment!