Slashdot Mirror


IPv6 Adoption Will Grow With Smart Grid Adoption, Hopes Cisco

darthcamaro writes "A lot of people in the US have not seen a use case for the use of IPv6 yet, since we've got plenty of IPv4 addresses. But what happens when the entire electrical grid gets smart? The so-called Smart Grid will need a networking transport mechanism that will connect potentially hundreds of millions of people and devices. Networking giant Cisco sees IP (internet protocol) as the right transport and IPv6 as the logical choice for addressing. 'Pv6 is an interesting discussion and one that occupies a lot of bandwidth at Cisco,' Marie Hattar, Cisco's vice president of network systems and security solutions marketing said. 'Some people say that for smaller deployments, we could get away with IPv4, but the smart grid has a number of parts. The point is that if you're looking to build this [smart grid] out, why not build it out on the scalable protocol from the get-go?'"

169 comments

  1. wait - what IS a smart grid? by Anonymous Coward · · Score: 0

    What's a smart grid?

    1. Re:wait - what IS a smart grid? by Anonymous Coward · · Score: 2, Informative
    2. Re:wait - what IS a smart grid? by ObsessiveMathsFreak · · Score: 1

      It's a system that can automate itself, enabling you to fire al lot your existing engineers.

      --
      May the Maths Be with you!
    3. Re:wait - what IS a smart grid? by Anonymous Coward · · Score: 0

      A football/Rugby/Soccer field with one guy having a minimum IQ of 110. That is as smart as the grid gets.

    4. Re:wait - what IS a smart grid? by mysidia · · Score: 1

      "Smart Grid" is a new fad. You can think of it as the 2009 equivalent to 1995's "Information Superhighway".

    5. Re:wait - what IS a smart grid? by Fred_A · · Score: 1

      What's a smart grid?

      It's when you give each electron it's own IP on the power grid. It's the new big thing !

      --

      May contain traces of nut.
      Made from the freshest electrons.
  2. I know my utility meters can be read remotely. by vertinox · · Score: 2, Interesting

    But I'm not sure what protocol they use to check my electricity and water meters remotely.

    I doubt its IPv6, but it would be a logical thing to do simply because of network addressing.

    I mean even with private IPv6 addresses, it would still provide an easier way to identify the devices.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
    1. Re:I know my utility meters can be read remotely. by Anonymous Coward · · Score: 1, Informative

      Its ipv4 on a private network. They can use 4billion in addresses if they want.

      There is nothing that says you can not tunnel ipv4 over ipv4 and still have a private network as big as the real internet. This is exactly what all the different guys going after this are doing.

      Also think about it. Do you realllllllllllllllllllly want your power grid to be tied to the real internet? IPV6 is a waste of time in the 'utility' market. Never mind the existing protocols that would all have to be chucked out or be routed over ip to get them to work. Not going to happen. These dudes move at glacial pace and for good reason. With say facebook going down there are a bunch of people who can not chat to their 'friends'. But say a sub station goes down. There is thousands of volts and amps jumping around, people with out power/heat, possible death.

      They use modbus or a simple ascii protocol usually hooked to a remote wireless device to check your stuff. It is not exactly rocket science.

      The real market will be porn somehow. It always is.

    2. Re:I know my utility meters can be read remotely. by oasisbob · · Score: 3, Insightful

      I doubt its IPv6, but it would be a logical thing to do simply because of network addressing.

      They might be using IPv6 soon enough, check out 6lopan, an IETF group working towards getting IPv6 working on low-power networking devices like Xbee modems, etc. IEEE 802.15 transceivers are low-power, will mesh easily, and are very common in power meters.

      Having global addressability saves a lot of hassle, and should not be confused with global reachability. Seems to make a lot of sense to me.

    3. Re:I know my utility meters can be read remotely. by FireFury03 · · Score: 4, Insightful

      Also think about it. Do you realllllllllllllllllllly want your power grid to be tied to the real internet?

      Well, maybe not, but there are still big advantages with using IPv6 even if it isn't on the public network. For example, you can use addresses that are guaranteed to be globally unique - this means no readdressing problems when you suddenly decide 2 completely independent networks need to talk to each other.

      This is what has stunned me about the telephone industry - they are spending billions on replacing their antiquated SS7 networks with IMS networks. The IMS protocols were _designed_ to be run over IPv6 (but of course, IPv4 and IPv6 are so similar that they have actually been made to work on both), but most of the telcos are rolling out IPv4 networks. Nothing like spending vast amounts of money to replace one obsolete network with another.

      IPv6 is an established and proven technology, there really aren't many good reasons not to use it in a new network.

      IPV6 is a waste of time in the 'utility' market.

      I'm not sure how it can be described as a "waste of time" since that would imply it would take longer to implement than an IPv4 network. If you're starting from scratch and not having to interoperate with the existing internet, an IPv6 network takes no more time to implement and is a bit of a no-brainer (getting a much more future-proofed network at almost the same cost). Unfortunately it seems that a lot of people in charge of such projects do indeed have no brains.

    4. Re:I know my utility meters can be read remotely. by Nefarious+Wheel · · Score: 1

      Smart meters are only part of the smart grid, although where they're being deployed it's considered essential to it. And the jury is still out as to how they're going to do the remote reading in many places - that will involve networking, and considering the millions of end points it may end up being a purpose-built protocol running across purpose-built hardware. IPV6 is all well and good and well thought out, but security is a big concern of the electricity companies and they're not entirely wedded to Internet protocols, which may not be considered sufficiently hardened to them. Get it wrong and the juice could be turned on at an inappropriate moment, killing somebody.

      And the new networking framework doesn't just apply to the meters, either - distributors are planning to improve their back haul networks from high voltage infrastructure on down to the substation level too. Part of the reason for smart metering (along with remote reading) is to get a better usage profile - that is, when, during the day, the peaks and troughs of usage occur in any part of the network. There are big bucks to be saved by coupling that knowledge to demand-side electricity management.

      In Australia we have a national electricity market, and both bulk electricity and retail customer transactions are traded across a common market settlements system called MSATS. It's already geared to handle the higher load of transactions that smart metering will impose, and has since 2001.

      --
      Do not mock my vision of impractical footwear
    5. Re:I know my utility meters can be read remotely. by commodore64_love · · Score: 1

      My meters use the phone line using either a 28k or 56k modem (not sure which). My DVR also uses the phone line. That makes sense since the phoneline is the most-widely available service.

      As for smartgrid, I'll be extremely annoyed if I come home to my hot house, turn-on the A/C and my thermostat tells me I have to wait an hour. Grrr.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    6. Re:I know my utility meters can be read remotely. by MountainLogic · · Score: 1

      The two main wireless protocols in contention for use at the home level are 6LoWPAN ( http://www.ietf.org/html.charters/6lowpan-charter.html ) and ZigBee Pro ( http://www.zigbee.org/ ). ZigBee is the much more interesting network for this application

    7. Re:I know my utility meters can be read remotely. by Darinbob · · Score: 1

      I'm working on smart grid stuff at the moment, and IPv6 is used. But these things are NOT connected to the network at large. These grids are all private networks, so it won't promote IPv6 stuff on the "public" internet, except perhaps to drive more sales of routers that have to understand IPv6.

      Cisco is pretty much a latecomer to this arena from what I can see, hoping to leverage their router sales to utilities rather than let them be able to pick and choose the network infrastructure.

    8. Re:I know my utility meters can be read remotely. by yoghurt · · Score: 1

      >> this means no readdressing problems when you suddenly decide 2 completely independent networks need to talk to each other.

      What if one of those independent networks is running IPv4? Fail.

      And that is why IPv6 continues to lose.

      --
      Yoghurt
    9. Re:I know my utility meters can be read remotely. by jeffstar · · Score: 1

      that won't fly.

      Your hot water might be a bit less hot or your pool not as clean though

    10. Re:I know my utility meters can be read remotely. by arminw · · Score: 1

      ....my thermostat tells me I have to wait an hour. Grrr....

      The thermostat won't tell you to wait an hour, but it might tell you that your electricity price for that hour would be double or triple what it would otherwise be. One thing you can be sure of though is that energy prices will not be any less, because somebody has to pay for that technology and guess who that will be -- -- you! It is very seldom that companies make big investments in order for you to save money.

      --
      All theory is gray
    11. Re:I know my utility meters can be read remotely. by Cyberax · · Score: 1

      "What if one of those independent networks is running IPv4? Fail."

      Use 6to4 or any other interoperability technology.

    12. Re:I know my utility meters can be read remotely. by Tony+Hoyle · · Score: 1

      Yeah like that's gonna work. If you're merging networks the last thing you want is to have hacks like 6to4 in the middle. That's as silly as saying that if two ipv4 networks clash just use NAT.

      In such a case the ipv6 network would be switched to ipv4.

    13. Re:I know my utility meters can be read remotely. by Cyberax · · Score: 1

      Or maybe IPv4 to IPv6?

      If you have a fucked up network configuration you can either workaround it or fix it.

    14. Re:I know my utility meters can be read remotely. by TheRaven64 · · Score: 1

      Contiki has an IPv6 stack now. The uIPv6 stack is not tied to Contiki, and can easily be run elsewhere, as long as you have 11KB of ROM and 2KB of RAM spare for it (35KB of ROM and 3KB of RAM for Contiki with uIPv6), and will run happily on something like a 6502. Of course, for serious use and some buffers for large-packet reassembly, and some space for your application code, you probably want 64KB of RAM.

      --
      I am TheRaven on Soylent News
  3. Re:oh the headache ... by Locke2005 · · Score: 3, Funny

    when can we stop talking about IPv6? Just as soon as the IPv7 standard is released?

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
  4. Translation by Locke2005 · · Score: 4, Insightful

    Companies will soon actually have a reason to throw out their old routers and buy new ones, hopes Cisco.

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
    1. Re:Translation by chrylis · · Score: 1

      The routers are fine, it's only layer-3 switches that have to be replaced.

      Although on that count, could Vyatta and friends *please* get up to speed with IPv6 support? The underlying engine's supported it for years...

    2. Re:Translation by TheGratefulNet · · Score: 2, Informative

      throw out routers? haven't ciscos been ipv6-capable for at least a decade now?

      ipv6 is really old stuff. all routers that are 'worth anything' should be v6 capable already. those that aren't probably don't NEED to be, anyway.

      not everything needs a world-wide public address. NAT 'security' is actually a Good Thing(tm).

      --

      --
      "It is now safe to switch off your computer."
    3. Re:Translation by bcmm · · Score: 2, Interesting

      Surely any decent router which miraculously doesn't support it yet could have support introduced in a firmware update? There is nothing about IPv6 that should require hardware updates.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    4. Re:Translation by Amouth · · Score: 1

      your talking about Cisco's lovely IOS - routers are cheap and as long as they have the interfaces and backplanes you need will do what you want. (unless you do some ungodly evil filtering/processing of every packet)

      It's the SmartNet and IOS that is the real cost - and no not all of the IOS releases from 5 years and older have ipv6 support

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    5. Re:Translation by DarkOx · · Score: 1

      I would not be so sure. Most hardware manufactured recently was built with IPv6 in mind, so is probably a firmwareware upgradeable. There are hardware features, like express forwarding are hardware specific and would need to have enough space allocated for specific address lengths.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    6. Re:Translation by FireFury03 · · Score: 5, Interesting

      throw out routers? haven't ciscos been ipv6-capable for at least a decade now?

      Pretty much (although you might have to buy a firmware upgrade... but then if you aren't running a recent firmware you're probably infested with security holes anyway).

      those that aren't probably don't NEED to be, anyway.

      That's rather untrue though. If you're going to deploy IPv6-only systems then *all* the routers on the network need to do IPv6. Yes, this even includes the home DSL routers, most of which currently on the market *still* have absolutely no IPv6 support, even though we only have about 2 years until IANA runs out of IPv4 addresses. Anything else is going to involve kludging things to work through IPv4 to IPv6 gateways, or tunnelling IPv6 over IPv4 to bypass the non-compliant devices.

      The whole IPv4 address exhaustion problem is a really good example of people sticking their heads in the sane and hoping the problem goes away - most ISPs seem to not be interested in preparing their networks for IPv6 at all (PlusNet told me that they had no plans to roll out *any* IPv6 support over the next few years and EntaNet seem to have halted their IPv6 trials). Some time towards the end of 2011 there will be a "sky falling" moment similar to what we saw at Y2K when ISPs realise they are basically screwed and are going to have to do an expensive rush-job of deploying IPv6 over their networks in just a few short months.

      not everything needs a world-wide public address. NAT 'security' is actually a Good Thing(tm).

      Argh! Please will people stop spreading this crap. There is practically *no* security provided by a NAT. You get security from stateful packet inspection. NAT requires stateful packet inspection to work, but there is no significant security advantage (and many really serious operational disadvantages) provided by running NAT instead of just a stateful firewall. Also, most home NAT routers provide no stateful firewalling, only the limited stateful tracking required to make NAT work, and can therefore easily be bypassed by anyone on the upstream segment (which may be a few hundred random members of the public in the case of some cable setups).

      Security is better served by doing proper stateful firewalling, and this is probably best achieved by removing NAT from the equation so that people don't have a false sense of security. Removing NAT also solves a lot of operational problems, as there are an increasing number of protocols that can't be made to work well through NAT (and whilst many people regard this as a flawed protocol design, there are sound reasons for designing these protocols in this way).

    7. Re:Translation by Nefarious+Wheel · · Score: 1

      Security is better served by doing proper stateful firewalling, and this is probably best achieved by removing NAT from the equation so that people don't have a false sense of security.

      Now that's just being silly. Most people aren't going to be influenced by such a lesson, because they fundamentally don't care about such issues. NAT is still a good thing, although I do agree with much else you say.

      I disagree with your contention that most routers don't offer stateful firewalls; check the age of your information, most of them do now.

      For my choice, I run a nice little NetGear wireless router at home. It's IPV4, uses NAT and includes a stateful firewall. (The router is quite good, but I've found the NetGear wireless Ethernet cards at the PC end rather suck on many levels. Get the router, ignore the cards). I regularly check our home systems (six of them) for malware, zero day exploits I read about, etc. and we're all pretty clean. Our ISP (Optus) offers a firewalled connection too, which helps. And the kids know better than to click links indiscriminately. You can teach 'em that.

      --
      Do not mock my vision of impractical footwear
    8. Re:Translation by drinkypoo · · Score: 2, Interesting

      That's rather untrue though. If you're going to deploy IPv6-only systems then *all* the routers on the network need to do IPv6. Yes, this even includes the home DSL routers, most of which currently on the market *still* have absolutely no IPv6 support

      Yeah, when ISPs actually do go IPv6 it will be a beautiful day for DD-WRT and OpenWRT. There will be whole businesses around reflashing those routers and reselling them, while most manufacturers will not release an update including IPv6.

      There is practically *no* security provided by a NAT.

      Unless your ISP is compromised, the combination of using non-routed addresses and dropping source routed frames (as everyone and their mom does by default) means that a NAT does provide some significant security. Attacks generally rely on packets reaching their destination.

      Security is better served by doing proper stateful firewalling,

      This part is true.

      Removing NAT also solves a lot of operational problems, as there are an increasing number of protocols that can't be made to work well through NAT (and whilst many people regard this as a flawed protocol design, there are sound reasons for designing these protocols in this way).

      In some cases yes, in some cases no. FTP is just stupid no matter how you slice it, sorry. Most newer protocols have some facility for NAT traversal, or at least work with a SOCKS proxy.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Translation by FireFury03 · · Score: 1

      Now that's just being silly. Most people aren't going to be influenced by such a lesson, because they fundamentally don't care about such issues.

      They start to care after they lose all their data and pay for their computer to be cleaned of malware for the tenth time.

      Car analogy alert: people don't care that putting diesel into their petrol car is bad. Oh wait, yes they do when they have to pay lots for it to be fixed.

      Also, router manufacturers do have to build _some_ security into their products. They will always do the bare minimum they can get away with, but once you take away NAT, the bare minimum happens to be a hell of a lot better than what we have now.

      I disagree with your contention that most routers don't offer stateful firewalls; check the age of your information, most of them do now.

      As recently as a year ago I was finding that a lot of the consumer routers did nothing to stop me accessing the LAN from the WAN port, so long as I had tweaked my routing appropriately (i.e. if you have 192.168.0.0/24 on the LAN and the router's WAN port is 1.2.3.4/24 then I can plug a machine into the WAN port as 1.2.3.5/24 set to route to 192.168.0.0/24 via 1.2.3.4 and get access to anything on the LAN. This is because the routers weren't *blocking* incoming traffic that didn't match any existing connections - i.e. they were just using the SPI functionality to drive the NAT engine rather than to drive a firewall as well).

    10. Re:Translation by FireFury03 · · Score: 2, Informative

      There is practically *no* security provided by a NAT.

      Unless your ISP is compromised

      Your ISP doesn't have to be compromised. Many cable systems are set up so that the cable segment is basically a bus and the cable modems are bridges. Anyone on that segment can adjust their routing appropriately.

      Also, even if you're not on such a network I don't think it's a particularly good idea to trust that another party's network is secure.

      the combination of using non-routed addresses and dropping source routed frames (as everyone and their mom does by default) means that a NAT does provide some significant security. Attacks generally rely on packets reaching their destination.

      No... No it doesn't. The ability to track the state of all the connections and drop packets that don't belong to any that were established by a local machine gets you the security. It just so happens that NAT requires that you implement this underlying framework, but keep this framework and remove the NAT and you still have about as much security. The only thing NAT gets you over and above this is to hide your internal network topography, which is of questionable value and turns out to be very harmful to a lot of legitimate stuff many people want to do.

      In some cases yes, in some cases no. FTP is just stupid no matter how you slice it, sorry.

      No, FTP isn't stupid - it was invented before firewalls were thought of and did the job it was designed to do very well. However, most people don't use the full functionality of the protocol and can therefore get away with something more simplistic that plays better with these newfangled firewall things.

      Most newer protocols have some facility for NAT traversal, or at least work with a SOCKS proxy.

      NAT traversal is flakey at best - even the STUN RFC admits that it is not, nor can it be, reliable. STUN (and other forms of NAT traversal) are a best effort way to make the best of a bad job and they work most of the time, but by no means should they be considered a good solution.

      As for SOCKS, I've not seen anything using especially recent protocols provide any kind of support for SOCKS proxies. Certainly when it comes to applications that need to use UDP, whilst SOCKS 5 does support UDP I've never actually seen anything try.

    11. Re:Translation by TheGratefulNet · · Score: 2, Insightful

      There is practically *no* security provided by a NAT.

      untrue.

      try to ping my home address. its 10.a.b.c (you know what I mean).

      go ahead.

      now ssh to me.

      now try to port scan me.

      want to finally admit that there IS *some* security to nat? its not as secure as a smart firewall but its WAY better than being 'directly on the net'. way way better (for most of us).

      --

      --
      "It is now safe to switch off your computer."
    12. Re:Translation by Bruha · · Score: 1

      Unfortunately there will be many public implementations of IPv4-IPv6 natting going on in 2010. This is an interim solution to eliminate the need for any IPv4 support on the client side. There are less than 9 /8's left to be handed out and those are being held tightly. Corporations are being told no more or they're being forced to send company officers to DC to argue their cases directly.

      2010 will see several nationwide rollouts of IPv6 native services on end user devices in the mobile market where there hardware is pretty user agnostic. I know of no major deployments of IPv6 in the consumer segment, namely because replacement of CPE devices would be extremely expensive. It could happen for greenfield deployments and other new buildouts of service.

      Another issue that's been brought up is that a /64 is the smallest point to point subnet and there's no equivalent to a /32 for IPv4. Not sure why a p2p connection needs a few billion ip's. Clearly there are still a few idiots on the IETF payrolls, perhaps the same ones who thought IPv4 had enough..

    13. Re:Translation by Arlet · · Score: 2

      Go ahead and post your public IP address, then.

    14. Re:Translation by Tony+Hoyle · · Score: 1

      Some time towards the end of 2011 there will be a "sky falling" moment similar to what we saw at Y2K when ISPs realise they are basically screwed and are going to have to do an expensive rush-job of deploying IPv6 over their networks in just a few short months.

      Not 2011.

      The problem with the 'exhaustion counters' is they're designed to push an agenda rather than present accurate results. They don't represent the real depletion rate at all.

      Looking at an old blog post about a year ago the counter was at 736 days. Today it's not at 371 days, or anything close... it's at 721 days. In a whole year we've lost 15 'days' of internet. Extrapolating that out (hey, if they can be hopelessly innacurate so can I) we'll run out sometime in 2057.

      Now the truth is somewhere in the middle, but there are no even halfway accurate estimates of that date.

    15. Re:Translation by Anonymous Coward · · Score: 0

      The whole IPv4 address exhaustion problem is a really good example of people sticking their heads in the sane and hoping the problem goes away

      I sure hope the sane don't mind being used in this way....

    16. Re:Translation by FireFury03 · · Score: 1

      I'm not sure which exhaustion counter you've been looking at. I've been keeping an eye on a number of exhaustion predictions for the past few years and they have been reasonably consistent (i.e. +/- 6 months). The allocation policies have been changed over the years and this has extended the amount of time we have, but not by much. Obviously exhaustion predictions can't take into account policy changes until they are at least visible on the horizon, so I do expect it'll be extended a bit more, but I'm honestly not expecting that extension to be more than a few months. New policies will also probably start making it much harder for people to get IPv4 addresses, so increasing the pressure to migrate onto IPv6 before the IPv4 addresses are exhausted.

      there are no even halfway accurate estimates of that date.

      And _that_ is why ISPs need to act now (actually, several years ago) to prepare themselves. This *is* going to happen, the longer they leave it, the more chance they will be caught with their pants down when it actually happens.

      There are certainly short-term gains to be had by sticking your head in the sand and pretending that there isn't a problem. Unfortunately the cost of having to drop everything and roll out a whole new network at crunch time is going to be very expensive, far outweighing those short term savings. Sadly, business these days seems to be all about short term gains at the expense of long term viability.

    17. Re:Translation by TheRaven64 · · Score: 1

      We got a year because a lot of big allocations were reclaimed. This is a (very) temporary solution; it gave enough for about a year more v4 allocations, but that kind of reclamation can not happen again because the addresses have already been reclaimed and assigned. There are some 'reserved' ranges that could be assigned, but I'd rather not be one of the people who gets them because a lot of software written over the last 30 years has had those ranges hard-coded as invalid and will drop packets from them.

      --
      I am TheRaven on Soylent News
    18. Re:Translation by vtavares · · Score: 1

      That would be true 10-20 years ago, and on small routers, because they were/are purely software driven. However, most interesting routing platforms today have IP stack primitives implemented in hardware (FPGA, ASIC) and they would lose their ability to process IPv6 in the so-called "fast path" forwarding plane if they were designed with IPv4 only.

    19. Re:Translation by Vancorps · · Score: 1

      You realize your argument is circular right? You want to say NAT doesn't help make you more secure but the reality is that the underlying framework when combined with dropping source routed packets results in a more secure network and just bridging can provide.

      Now I have a fancy firewall cluster costing many 10s of thousands of dollars, I can do proper DPI at work here but at home no one will shell out for advanced firewalls that could safely provide protection without NAT and it's associated framework. Without NAT the underlying framework would not have been established and people would be having many more problems. I don't trust Netgear or Dlink or any of the common consumer brand firewalling routers to protect me in an IPv6 world where there is no underlying framework forcing them to protect my internal network.

      Also, FTP is stupid, it's very old and wasn't designed with today concerns such as security and transport integrity. Many a corrupt file I've had to deal with in the FTP world. A good day it will be when that stack can finally die.

      As for STUN and SOCKS, you're right there. Most applications prefer to deal with NAT on their own so they don't bother with SOCKS.

      Oh, and one final thing, what the hell cable operator are you referring to? I've not seen an ISP in many years that didn't use VLSM which means that each node is on a different subnet which removes your ability to route directly to another customer. This makes much sense from a provider standpoint as all traffic can be monitored by them.

    20. Re:Translation by j+h+woodyatt · · Score: 1

      I'll do better than that. I'll give him my public IPv6 prefix at home. I'm at 2001:5a8:4:2290::/56 and the router is not even a firewall. Have fun port scanning me. Knock yourself out.

      --
      jhw
    21. Re:Translation by Watson+Ladd · · Score: 1

      Maybe you should run a secure system at your endpoints.

      --
      Inventions have long since reached their limit, and I see no hope for further development.-- Frontinus, 1st cent. AD
    22. Re:Translation by Anonymous Coward · · Score: 0

      Try to ping my lightbulb, its just as "secure" from the world in nearly the same way

  5. Re:oh the headache ... by TheRaven64 · · Score: 3, Insightful

    When everyone's deployed it and it's boring.

    --
    I am TheRaven on Soylent News
  6. Re:oh the headache ... by Pulse_Instance · · Score: 2, Insightful

    When IPv7 standard is release we will talk about how no one will fill up all the address in IPv6 and there is no reason to switch to IPv7. When the IPv8 standard is released then we will talk about how easy it actually was to switch to IPv6 in the first place so there is no reason to stick around on IPv7. Maybe after IPv9 we will hear the end of IPv6 but it is highly unlikely.

  7. Wishful thinking by Locke2005 · · Score: 4, Insightful

    NAT/IP Masquerade has worked well for scaling IPv4 in every conceivable application to date... what makes them think it won't work for the "smart grid"? Or to put it differently, do you really want every appliance in your house directly addressable from anywhere in the world? After all, what could possibly go wrong?

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
    1. Re:Wishful thinking by sxedog · · Score: 1

      As long as they leave my coffee maker alone, I'm fine

      --
      If it ain't broke, DON'T fix it.
    2. Re:Wishful thinking by solevita · · Score: 3, Informative

      NAT/IP Masquerade has worked well for scaling IPv4 in every conceivable application to date

      Except, of course, that isn't really true. I've had to try and run a VPN endpoint on a NAT'd host because our ISP wasn't giving us what they'd advertised. That wasn't fun and if more people are going to want to run VPNs in the future, we're going to need more IP addresses.

    3. Re:Wishful thinking by RiotingPacifist · · Score: 1

      IPv6 != addressable from anywhere in the world. If i have a lan that is not connect to the internet it still communicates using IPv4. There are many nice tricks in IPv6's hat that make it much better than IPv4+nat+... for any new network. Ignoring the additional space that would allow a much better layout, you have multicast which is nice for the smart grid

      --
      IranAir Flight 655 never forget!
    4. Re:Wishful thinking by oasisbob · · Score: 1

      After all, what could possibly go wrong?

      ... someone deploys this tech without sensible ACLs and firewalling? We face those same problems now.

    5. Re:Wishful thinking by hardburn · · Score: 5, Insightful

      NAT/IP Masquerade has worked well for scaling IPv4 in every conceivable application to date

      Much the same way that up to Aug 28, 2005, the New Orleans leeves were successful in holding back every conceivable rise in water level.

      NAT works as long as you have simple networking needs--nothing much more than web and email. As soon as you need to use VPN, or VoIP, or try to get two or more people to play the same game behind the same firewall, it becomes readily apparent what a pain NAT is. In some cases, the application is doing all sorts of trickery to try to keep the user from noticing the issue. In others, the user is left on their own to deal with it. That doesn't even count a bunch of potential applications where the developers realized that they wouldn't be able to get around NAT, and thus never built it at all or simply toiled in obscurity.

      Or to put it differently, do you really want every appliance in your house directly addressable from anywhere in the world?

      NAT != Firewall. The only thing NAT provides you with over a packet filter is hiding your network topology. There is some use in that, but it comes at the expense of everything mentioned above. On balance, NAT comes out wanting. If you still really want to hide your topology, you can still use NAT on IPv6, but this should be the exception, not the rule.

      --
      Not a typewriter
    6. Re:Wishful thinking by bertok · · Score: 1

      Addressable is not the same as accessible.

      Still, I don't see IPv6 adoption happening until you can actually have it provided by most ISPs for residential access, have it go through a cheap ADSL/cable routers, and deliver the web pages people want to access.

      From what I've heard, less than 1% of the web is IPv6 accessible, less than 5% of residential internet connections allow IPv6, and very few home routers support it.

      It's basically like NetBEUI or IPX - used on LANs, but not on the Internet.

    7. Re:Wishful thinking by growse · · Score: 1, Interesting

      You mean, every IPv4 application you can conceive of....?

      Don't lets limit the rest of the world because you're too stupid to realise that NAT and IPv4 causes huge problems on a day to day basis for a lot of people.

      --
      There is nothing interesting going on at my blog
    8. Re:Wishful thinking by chrylis · · Score: 1

      Every home router I've seen does IP in software, so they ought to be updatable with a firmware upgrade. All it will take is for one major ISP to roll out IPv6 to customers and start advertising "next generation Internet" support for the others to put it on their while-we're-replacing-old-equipment list. Sure, it'll take a while, but it'll happen sometime.

    9. Re:Wishful thinking by techno-vampire · · Score: 2
      NAT != Firewall. The only thing NAT provides you with over a packet filter is hiding your network topology.

      Personally, I'd say that it does a little more. As long as your router drops incoming requests on the floor instead of forwarding them, it protects your LAN from port scanners. That, of course, doesn't make it a firewall, but it is a step in the right direction. There's nothing NAT can do to protect you if you click on the wrong link because whatever comes back is a response, not a request, but still, for the average office, it's better than nothing.

      --
      Good, inexpensive web hosting
    10. Re:Wishful thinking by hardburn · · Score: 1

      Router's don't drop requests, at least not by default. Firewalls do. Best Buy has never sold a single router, no matter what it says on the box.

      Anyway, you can have your firewall drop all incoming traffic by default, opening up specific ports to specific machines as needed. It's still easier than NAT, since you don't also have to fool around with forwarding those ports.

      Some applications have hardcoded ports, which makes it almost impossible to have more than one of these running at once behind the same NAT. A simple packet filtering firewall can handle this fine. Admittedly, those applications are poorly-written, but you're still going to have to deal with them in the real world.

      Or don't bother with any sort of gateway. I'm personally a fan of perimeterless networking, where each machine is expected to handle its own firewall. Done right, it can make administration easier, give better security, and keeps laptops safe no matter where they're connected.

      --
      Not a typewriter
    11. Re:Wishful thinking by FireFury03 · · Score: 3, Interesting

      NAT/IP Masquerade has worked well for scaling IPv4 in every conceivable application to date...

      Except it hasn't, NAT is a kludge that happens to work with simplistic client/server protocols in common use (such as HTTP). It doesn't even work well with some old standard protocols, such as FTP, without protocol-specific packet mangling.

      NAT breaks pretty much all peer-to-peer protocols, which are rapidly becoming more common. Want to do VoIP, or start a direct file transfer between 2 IM clients? If you have NATs in the way then that gets unreliable. STUN makes things work a lot of the time, but even the STUN RFC admits that it is not, and cannot be, reliable. Systems like Skype try to hide these problems by abusing unfirewalled clients to route traffic between NATted clients (often without the unfirewalled user's knowledge), but the problems still exist and such "solutions" start to fall to pieces as the proportion of unfirewalled hosts dwindles.

      what makes them think it won't work for the "smart grid"?

      I'm guessing that the electricity supplier is going to want to be able to talk directly to your electricity meter, etc. Having a NAT in the way makes this less reliable since they won't be able to talk to it unless the meter has already initiated the connection through the NAT.

      Or to put it differently, do you really want every appliance in your house directly addressable from anywhere in the world?

      Do not confuse global addressability with global reachability. Assigning every device a globally unique address is valuable, even if it is on an isolated network. It makes it easier to connect 2 isolated networks together when you realise that you actually need them to not be so isolated from each other.

      That said, I can think of a number of appliances that I wouldn't mind being globally reachable: My MythTV system is already globally reachable - if someone mentions a TV programme that sounds interesting, I can use the web browser on my phone to tell it to record that programme. I wouldn't mind my oven to be internet addressable, so I could remotely ask it to turn on and cook my dinner in time for me getting home. Being able to turn my heating on when I'm at the airport after coming back from holiday would be useful. Taking things a bit further, if I could ask my fridge what I'm running out of when I'm in the supermarket, I could save some hassle.

      After all, what could possibly go wrong?

      There are obviously security concerns to be addressed. But at the same time, designing a network so it *can't* be extended in the future seems somewhat short sighted.

    12. Re:Wishful thinking by Nefarious+Wheel · · Score: 1

      do you really want every appliance in your house directly addressable from anywhere in the world? After all, what could possibly go wrong?

      Part of the appeal, according to the electricity execs we've surveyed recently (study to be released soon) is the idea that people might like to know better where their money is going on a per-household-circuit level. A better dashboard, if you will. (warning: car analogy follows) It's like the dashboard of your car - you have a speedometer, tachometer, various warning lights - yet your house has nothing of the sort to show you your energy use, and you're using a similar amount of energy (car energy use approximates household energy use, it turns out). There's a hope that overall energy use will be cut down if people have better knowledge of where they're using it, and giving people that sort of dashboard option may help. Electricity is a big part of a lot of people's spend, and if they save money and the electricity providers save money, everybody benefits.

      Take-up will be proportional to how helpful it can be made, how easy it is to access, and how secure it can be made, how compliant with privacy regs.

      An interesting side observation from our survey is that the C-level people we've spoken to are concerned about the same things we are - effect on climate, safety of the workforce, renewable energy sources, and they're quite passionate about wanting to make a positive difference. They're not quite the rapacious bastards I thought they were.

      --
      Do not mock my vision of impractical footwear
    13. Re:Wishful thinking by FireFury03 · · Score: 1

      less than 5% of residential internet connections allow IPv6

      Untrue. Very few residential internet connections will do *native* IPv6, but 6to4 works reasonably well. What this basically means is that you can still roll out IPv6 on your internal network and you can still reach IPv6 services on the internet, it's just that the traffic is tunnelled across your ISP inside IPv4 packets until it gets to your nearest 6to4 anycast gateway.

    14. Re:Wishful thinking by techno-vampire · · Score: 3, Interesting
      Router's don't drop requests, at least not by default. Firewalls do. Best Buy has never sold a single router, no matter what it says on the box.

      I have a home LAN, with a router. In order to get bittorrent working correctly, I had to set up this machine with a static IP on the LAN, and tell my router to forward all rquests on the appropriate ports to that IP. I have my own domain, and I've used dynamic DNS to let me use SSH to connect to my home machine when I'm away from home. Again, I had to tell the router where to send incoming requests on Port 22. Now, you may prefer to call that a "residential gateway" as Wikipedia does, but most people would look at you funny if you called it anything other than a router.

      --
      Good, inexpensive web hosting
    15. Re:Wishful thinking by arndawg · · Score: 1

      . I'm personally a fan of perimeterless networking, where each machine is expected to handle its own firewall. Done right, it can make administration easier, give better security, and keeps laptops safe no matter where they're connected.

      If you want to allow, say, VLAN 100 to access VLAN 105 on specified ports that would be difficult to do on a computer level since you could only filter on ip-range / ports. And that would be rather insecure unless you're using ipsec. Also you will have management overhead when there's a security bug in the firewall software. But I too like having firewalls on servers and computers. But rules for outgoing connections and between vlans is managed centrally. It's a good additional layer if you can manage it, but don't use it as the only layer.

    16. Re:Wishful thinking by asdfghjklqwertyuiop · · Score: 1

      Personally, I'd say that it does a little more. As long as your router drops incoming requests on the floor instead of forwarding them, it protects your LAN

      NAT does not drop anything.

    17. Re:Wishful thinking by techno-vampire · · Score: 1
      NAT does not drop anything.

      Agreed. I never said that it did. NAT and packet filtering are two separate functions that a home router can do. Combined, they make the beginnings of a firewall, but you still need more to be properly protected.

      --
      Good, inexpensive web hosting
    18. Re:Wishful thinking by anarche · · Score: 1

      Really? Port 22 huh? And hosted on 1and1.com, sooo whats the url/ip?

      --
      Wait! Whats a sig?
    19. Re:Wishful thinking by cheekyboy · · Score: 1

      Climate is a bogus reason dude, no matter what you try to do, the same amount of coal is dug up and burned.
      And even if you can reduce usage by N percent in usa, china will use double in a week.

      The secret powers at be have the real solution, outright extermination of 80% of the planets people, if you do it in one day, its genecide, if you do it over 30years by reducing fertility levels, well... its kinder.

      --
      Liberty freedom are no1, not dicks in suits.
    20. Re:Wishful thinking by Aqualung812 · · Score: 0

      Replace "router" with "NAT device" in your post. Not only does that still work, but it is more accurate.
      You are not routing to your home network, the routing stops at the outside of your NAT device. From there, you are port forwarding, NOT routing.
      Routing is a two-way street.

      --
      Grammer Nazis - I mod you "troll" unless you actually add something on-topic. Yes, I know I have mispellings in my sig.
    21. Re:Wishful thinking by QuantumRiff · · Score: 1

      Or to put it differently, do you really want every appliance in your house directly addressable from anywhere in the world?

      Smart grid requires two way communication between your devices in your house, and other houses or electric company. The "Smart Grid" is the ability to do things like get a lower rate for electricity, but they tell your AC to turn off if there is too much load on the grid. Or to have your car charge only at certain electric rates, etc. That does not work if the actual devices are not addressable from outside your home.

      --

      What are we going to do tonight Brain?
    22. Re:Wishful thinking by techno-vampire · · Score: 2, Insightful

      *Shrug!* At this point, you're just playing word games with the nomenclature. The common name for the device in question is "router," and wanking about the definition isn't going to change that.

      --
      Good, inexpensive web hosting
    23. Re:Wishful thinking by Vancorps · · Score: 1

      Use better VPN software. My Sonicwall Global VPN or SSL VPN clients go right through NAT just fine. Cisco Pix if setup incorrectly can have trouble but it works for the most part as well. Of course in my Sonicwall world for SIP through NAT I have enabled consistent NAT which has the byproduct of making every VPN client out there seem to work fine. NAT in and of itself isn't that problematic, it's quite mature and there is always a way of dealing with it and usually by following a best practice anyway whether you run IPv4 or 6.

    24. Re:Wishful thinking by megabunny · · Score: 1

      Funny, the current Cisco VPN has multiple ways of getting through NAT. NAT-T, udp encapsulation and others. You can even layer them. I find it funny to look in the connect log where it notes each time it had to tunnel through a NAT layer during setup. MB

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    25. Re:Wishful thinking by Aqualung812 · · Score: 1

      It isn't word games, routers and firewalls are not the same thing.
      You sound like the same person that calls your monitor a "computer" and your computer case a "hard drive" or "CPU". You also thought the year 2000 was the first year of the 21st century.
      Just because a majority or people are ignorant to facts doesn't mean that I'm going to start calling a firewall a router. The common name is only a router because common people don't know what the hell they are talking about.

      --
      Grammer Nazis - I mod you "troll" unless you actually add something on-topic. Yes, I know I have mispellings in my sig.
    26. Re:Wishful thinking by techno-vampire · · Score: 1
      It isn't word games, routers and firewalls are not the same thing.

      And I never said they were. Insisting on calling a home router a "NAT Device," however, is just playing word games, and that's what I was referring to. NAT makes your computers harder to find by port scanners, and packet filtering is one layer needed for a firewall, and making quibbling over the nomenclature isn't going to change that no matter how many brownie points it gets you in class. And no, before you accuse me of thinking that machines on a home LAN don't need a real firewall, that's not what I'm saying.

      --
      Good, inexpensive web hosting
    27. Re:Wishful thinking by sjames · · Score: 1

      That is easily done with simple stateless filtering on an IPv6 network. Further, since the firewall only has to look at the packets rather than rewriting every last one of them, performance improves. If you add simple connection tracking, you can catch the more creative scanning attempts as well and still don't have to rewrite the packets.

      Of course, port scanning will become a LOT less useful when every joe has an address space the size of all of IPv4 (or larger) and only a few hosts living within it. Imagine, after weeks of scanning all you found was the dish washer.

    28. Re:Wishful thinking by ckaminski · · Score: 1

      Simply because you have a finite number of ports via nat, and natting is just one more layer of configuration I have to fuck with to be able to share services. I can't push out 100 HTTP servers via a single NAT port, for example, without some complex proxying.

      NAT is a great solution for a particular shortcoming of IPv4, but it's a workaround, nothing more. The underlying problem needs to be addressed, making clients first-class network citizens again.

  8. when the entire electrical grid gets smart? by JeanBaptiste · · Score: 1

    We can just assign each electron it's own IPv6 address.

    I call I don't have to work on the routing tables...

    1. Re:when the entire electrical grid gets smart? by sexconker · · Score: 2, Informative

      IPv6 only allows about 3.4 * 10^38 addresses.
      Not nearly enough!

  9. Windows 7 and Server 2008 by Enderandrew · · Score: 1

    Microsoft is pushing IPv6. Many people will be switching to IPv6 and not even realize it.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Windows 7 and Server 2008 by Anonymous Coward · · Score: 0

      Maybe so, but most of them are behind v4 networking equipment.

    2. Re:Windows 7 and Server 2008 by Gerald · · Score: 1
  10. NEGATIVE! Seperate it from public! by Anonymous Coward · · Score: 2, Insightful

    No, the smart grid should be a completely seperate network, only backed by the Internet/public network as a fallback to primary grid network failure. And even then severe security measures should be met for such a bridge. My point still stands, the grid should be implemented on a seperate network (not completely publicly accessible), and in that case using IPv4 on both will be just fine.

  11. Get a Clue! by refactored · · Score: 4, Interesting
    I waded through the replies with a fist full of mod points hoping to mod the cluefull up... but there weren't any!

    The internet and especially all the Linux nodes on the internet are designed from the ground up to have a static IP addresses and IP names and be their own DNS and own Mail smarthost and web server and ....

    Between the control freaks, the clueless, and the bean counters in Microsoft and the ISP's we have an internet with...

    • an artificial scarcity of ip numbers and ip names that the ISP's can rort a fortune out of their users for a service that costs them less to provide than the cost of billing their customers for it.
    • the vast majority of machines being dumb emasculated drones begging for content from the big media industries.
    • an a tightly controlled web where peer to peer traffic is being squeezed out.

    IPv6 will _never_ be allowed into the current mix.

    1. Re:Get a Clue! by sexconker · · Score: 2, Interesting

      Protip: We were networking long before IP. If you were talking about MAC addresses, you'd have a point.

      Yes, ISPs suck.
      No, believe it or not, IPv6's ridiculously slow uptake is MS's fault.

      Yes, IPv6 will be here one day.

    2. Re:Get a Clue! by tsotha · · Score: 4, Informative
      • an artificial scarcity of ip numbers and ip names that the ISP's can rort a fortune out of their users for a service that costs them less to provide than the cost of billing their customers for it.
      • the vast majority of machines being dumb emasculated drones begging for content from the big media industries.
      • an a tightly controlled web where peer to peer traffic is being squeezed out.

      Only your first point has anything to do with IPv6. Switching to a new protocol isn't going to make your machine any less "emasculated", and P2P is being suppressed over bandwidth costs (though I'm not even sure how much that's true - I use bittorrent all the time). People who aren't running some kind of web service aren't going to see any benefit from IPv6.

    3. Re:Get a Clue! by FireFury03 · · Score: 1

      an artificial scarcity of ip numbers

      Artificial? Not really - the scarcity of IPv4 addresses is real. Yes, a lot of it is caused by the rather address-wasteful way that IP subnetting works, but that is hardly an "artificial" scarcity, it is just an artefact of how the protocol works.

      and ip names

      Presumably by "IP names" you mean domain names? There is no scarcity here the DNS system can cope with a practically unlimited number of domain names.

      that the ISP's can rort a fortune out of their users for a service that costs them less to provide than the cost of billing their customers for it.

      I'm not seeing any ISPs around here ripping off their users to provide IPv4 addresses. In fact, every ISP I've ever used has been happy to hand out small IPv4 networks to their users at no extra cost. I currently have a /29 global scope IPv4 network hanging off the end of my ADSL. Most ISPs worth a damn in the UK will give you a /29 for free with no questions asked, and usually anything up to a /27 if you can provide some justification for the need.

      Sure, some ISPs rip people off for the cost of domain names, but there is plenty of competition in the area - the ISPs pick up business from clueless people who know no better, everyone else goes to the cheap mainstream registrars. This has nothing to do with scarcity any more than you might claim that a high street PC shop like PC World can rip clueless customers off because computer hardware is "scarce", even though the clueful customers are buying their hardware from elsewhere at a fraction of the price.

      an a tightly controlled web where peer to peer traffic is being squeezed out.

      Except it isn't. In fact, quite the opposite is happening - peer to peer applications are rapidly gaining a significant share. Things like peer to peer filesharing, VoIP, games, etc. are the things that will drive IPv6 since they require an agnostic network that makes no distinction between client and server. Other drivers for IPv6 are the multicast support (a big factor for streaming TV services), mobile portability (increasingly important as people roam between networks with their mobile gadgets), etc.

      IPv6 will _never_ be allowed into the current mix.

      Its already _in_ the current mix. Sure, it hasn't made a significant impact yet, but there was a time when the web wasn't significant, peer to peer file sharing wasn't significant, and VoIP wasn't significant.

      I'm afraid I think you're wrong - in a couple of years time the IANA IPv4 pool will be exhausted and the choices will be simple: adopt IPv6 or get squeezed behind layers and layers of ISP-based NAT. With the current mix of peer to peer technologies, there is a large chunk of the user base for whome that is unacceptable (those of us who use VPNs, VoIP, remote management, etc. on a day to day basis), thus there will be a significant market for ISPs offering IPv6 connectivity. Sure, IPv6 connections may well be more expensive than the run of the mill NATted home IPv4 connection, but there are already a significant number of people who pay more for better connections so I don't see this as a big problem.

    4. Re:Get a Clue! by westlake · · Score: 1

      The internet and especially all the Linux nodes on the internet are designed from the ground up to have a static IP addresses and IP names and be their own DNS and own Mail smarthost and web server and ....

      Thirty years of experience ought to have taught the geek that almost no one wants to manage systems and services on that level.

      the vast majority of machines being dumb emasculated drones begging for content from the big media industries.

      Wilmington, Delaware had a music-by-wire service in 1909:

      The rate of charge for this service is very reasonable. It is three cents, for each ordinary piece, and seven cents for grand opera. The subscriber must guarantee $18 per year.
      In most cases the actual amount of music used makes that revenue greater than the regular telephone rent. In addition to this, pay stations are installed in restaurants, cafes, hotels and other public places, where selections can be obtained by depositing a coin in the box.
      The returns from residence stations run from fifteen to twenty cents per day, while pay stations have averaged as high as $10 in a week. On the whole, it has been estimated by its introducers that the service will pay local telephone companies from thirty to thirty-five per cent on their investment.
      Distributing Music Over Telephone Lines

      KDKA began broadcasting in 1920. RCA launched the first national radio network in 1926. The geek who complains that users want prime media content from the major providers was born 100 years too late.

      The only fundamental difference between the geek's pristine Linux machine and the "emasculated" HP running Vista or Win 7 is that the HP will likely ship with a Blu-Ray drive, a licensed Blu-Ray player and an HDMI output for multichannel theater sound and HD Video.

      Amazon. Blockbuster. iTunes. Pandora. Songbird. WinAmP. Rhapsody. YouTube.

      Protected content. Unprotected content. Free services. Subscription services. It all works just fine with the native Windows clients.

      an a tightly controlled web where peer to peer traffic is being squeezed out.

      The real threat to P2P is the instant download stream.

      The Netflix client built into the HT receiver, the 65" Vizio HDTV, the Samsung Blu-Ray drive.

       

    5. Re:Get a Clue! by TheRaven64 · · Score: 2, Informative

      I'm not sure how you can blame it on Microsoft. You've been able to download IPv6 support for XP from Microsoft for several years (one of my housemates was running v6 on his machine via a tunnel back around 2002/3) and Vista supports 6to4 out of the box.

      --
      I am TheRaven on Soylent News
    6. Re:Get a Clue! by JSBiff · · Score: 1

      "You've been able to download IPv6 support for XP from Microsoft for several years"

      Furthermore, isn't IPv6 included with XP SP2 and later? So you don't even need a seperate download anymore - if you are running a patched version of XP, you *have* IPv6, I think? That is, it's not active, but if you go to the Network Connection properties for your network adapter, I think you can just 'add protocol' and select IPv6, and a few seconds later, it's all setup?

    7. Re:Get a Clue! by sexconker · · Score: 1

      Ugh I failed.

      No, believe it or not, IPv6's ridiculously slow uptake is MS's fault.

      No, believe it or not, IPv6's ridiculously slow uptake is NOT MS's fault.

    8. Re:Get a Clue! by TheRaven64 · · Score: 1

      That makes more sense. A lot of the blame probably goes to companies like Netgear and Linksys. If consumer-grade routers (other than Apple's Airport) did 6to4 out of the box, then most users would have v6 already (OS X and Vista both set up v6 automatically if the network supports it) and could be using it for things like file transfers and VoIP, killing the 'there's no market for it' argument from ISPs.

      --
      I am TheRaven on Soylent News
    9. Re:Get a Clue! by sjames · · Score: 1

      Actually, ISPs are sufficiently clueless about v6 that they're unlikely to even recognize P2P traffic running on a 6to4 tunnel. To them it looks like an odd UDP like IP protocol.

      The second part is a combination effect. At least some of it comes from the sad state of affairs where only servers get real static IP addresses and everybody else gets a dynamic IP and a TOS that forbids running a server. If not for that, some small portion of people on DSL might actually serve their personal webpage from home.

  12. I don't know about you all...but as for me... by Em+Emalb · · Score: 2, Funny

    I'm waiting for IP version Kevin Bacon.

    It's the only way to ensure your packet is going to positively absolutely get from point A to point B in a timely, efficient, and stylish manner.

    Keep your stupid IP ver 6. Pffft. It's about as elegant as Lemur poop. IPvKB, on the other hand...now THAT'S a protocol.

    --
    Sent from your iPad.
  13. The last thing we need is for the power grid by antifoidulus · · Score: 3, Funny

    to become self-aware AND connected to the internet. It will spend the whole day looking at ionic porn instead of providing power.

    "ooh baby, I can see your net positive charge, come put it in my net negative charge..ooh, you like like bonding....yeah baby...ooh, you want to get kinky and go 3 atom covalent?"

    1. Re:The last thing we need is for the power grid by sexconker · · Score: 1

      Wouldn't you be putting your net negative charge in the net positive charge?

      Charge transfer being done through electrons, of course. Anyone doing it with positrons will be turned into a pillar of salt.

    2. Re:The last thing we need is for the power grid by Cheesetrap · · Score: 4, Funny

      Wouldn't you be putting your net negative charge in the net positive charge?

      Hey don't push your politics on me, man!

  14. Can't Wait by sexconker · · Score: 4, Funny

    I can't wait to DDoS your fridge, then call you up (over VoIP) and ask you if your fridge is running.

    1. Re:Can't Wait by geekoid · · Score: 1

      Why don't you just subscribe to his fridges twitter feed?

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Can't Wait by sexconker · · Score: 1

      Because it can't tweet when it's DDoSed, duh.

  15. Obligatory Joke by riffzifnab · · Score: 1

    So a priest, a rabbi and an atheist walk into a bar. IPv6

  16. Re:oh the headache ... by iamapizza · · Score: 2, Insightful

    Does this mean we'll have to modify the quote to "There's no place like ::1"?

    --
    Always proofread carefully to see if you any words out.
  17. as long as it isn't connected to the internet by Anonymous Coward · · Score: 0

    as long as it isn't connected to the Internet, who cares?

    they can use IPv4 and allocate the entire 4B IP addresses to devices. nobody will have any problem with this.

    it's only when they then want to connect to these systems over the Internet that there becomes a problem (and even then, it's only a problem if they insist on routing to/from them instead of proxying)

    if they decide to use IPv6 (and why not for a dedicated environment, they shouldn't be interacting with the outside world, and they may have more than 4B devices someday), it still shouldn't affect anyone connected to the Internet because those people should not be talking to this network in any way other than through the approved, authenticated gateways that can deal with any translation issues needed.

  18. the Linux desktop will drive ipv6 by Trepidity · · Score: 4, Funny

    IPv6 adoption, I predict, will increase markedly in The Year of the Linux Desktop.

    1. Re:the Linux desktop will drive ipv6 by Daimanta · · Score: 1

      So that means that the Year of Linux on the Desktop will be between 2011 and 2013?

      Sources:
      http://www.potaroo.net/tools/ipv4/index.html
      http://www.ipv6.sltnet.lk/know4-exhaust.html

      --
      Knowledge is power. Knowledge shared is power lost.
    2. Re:the Linux desktop will drive ipv6 by Anonymous Coward · · Score: 0

      Too bad IPv6 doesn't set up for a snappy acronym like "It Still Does Nothing" or "Never Twice the Same Color".

      *grumble* those guys couldn't even do that much.

    3. Re:the Linux desktop will drive ipv6 by david_thornley · · Score: 1

      I've got a Linux desktop. For me, 2007 was the Year of the Linux Desktop.

      I'm going to be able to use IPv6 as soon as we have the Year of the IPv6-capable DSL router.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  19. Re:NEGATIVE! Seperate it from public! by FooAtWFU · · Score: 3, Funny

    Don't worry! You see, by using IPv6 you can guarantee that no normal host on the Internet is ever going to be capable of reaching it! :)

    --
    The World Wide Web is dying. Soon, we shall have only the Internet.
  20. If it's so interesting... by Gerald · · Score: 5, Insightful

    "IPv6 is an interesting discussion and one that occupies a lot of bandwidth at Cisco."

    So why can't I get to www.cisco.com via IPv6?

    1. Re:If it's so interesting... by chrylis · · Score: 2, Interesting

      Especially ironic since just this afternoon I was looking at a Cisco Press book that gave a lookup for www.cisco.com as an example of IPv6 DNS.

    2. Re:If it's so interesting... by Roman+Mamedov · · Score: 1

      $ host www.cisco.com www.cisco.com is an alias for www.cisco.com.akadns.net. www.cisco.com.akadns.net is an alias for geoprod.cisco.com.akadns.net. geoprod.cisco.com.akadns.net is an alias for www.cisco.com.edgekey.net. www.cisco.com.edgekey.net is an alias for www.cisco.com.edgekey.net.globalredir.akadns.net. www.cisco.com.edgekey.net.globalredir.akadns.net is an alias for e144.cd.akamaiedge.net. e144.cd.akamaiedge.net has address 88.221.32.170 And Akamai has their head firmly in the sand, and doesn't do IPv6, afaik.

    3. Re:If it's so interesting... by chrylis · · Score: 1

      Getting Akamai on board would solve a huge chunk of that inaccessible-Web problem. Seems like it'd even be easier to handle content distribution for IPv6 than for IPv4.

  21. The smart grid doesn't need public IPs by Desert+Tripper · · Score: 4, Informative

    Most grid control systems are on private (192.168 style) networks not connected to the general Internet for obvious reasons, and "smart-grid" meter-reading systems that are currently implemented or planned use other methods of addressing (packet-radio protocols, etc.) So, the "smart grid" argument in the article is misguided at best.

    1. Re:The smart grid doesn't need public IPs by jroysdon · · Score: 1

      Not sure where you're getting your info from. Both my local utility power, MID, and the big California utility PG&E (who provides my natural gas) use IPv6 for all their smart meters.

      You've got to address those meters somehow so you can read/poll them.

    2. Re:The smart grid doesn't need public IPs by Anonymous Coward · · Score: 0

      Actually, the best "Smart Grid" deployments ARE using IPv6 *now* and have for years. There are millions of IPv6 devices at dozens of US utilities.

    3. Re:The smart grid doesn't need public IPs by synackpshfin · · Score: 1

      You can always use fc00::/7 (Unique Local IPv6 Unicast Addresses) addresses in your IPv6 network. From RFC 4193: ...defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site. These addresses are not expected to be routable on the global Internet.

    4. Re:The smart grid doesn't need public IPs by sjames · · Score: 1

      Actually, IPv6 makes a LOT of sense for the smart grid. The 10.0.0.0/8 address space only offers 16 million or so IP addresses, nowhere near enough for each smart grid node to have a globally unique address.

      A single IPv6 /48 prefix OTOH would provide enough unique addresses and routes without question and each device would be pre-assigned based on it's MAC address. That saves the administrative overhead of maintaining an independant GUID database.

      That does NOT mean putting the lot on the internet. I imagine the chosen prefix will be a black hole as far as the internet is concerned. To be sure, they COULD choose an 'unassigned' /8 in the v6 space so that most routers out there wouldn't even be configured to route a packet to their space even if it did somehow end up connected to the internet.

  22. Re:oh the headache ... by 0100010001010011 · · Score: 3, Insightful

    In perspective, IPv6 is 5Ã--10^28 addresses for every man womand and child alive. 70kg human has around 7*10^27 atoms in their body. Or about 7 IP addresses per atom.

    Each 1.020144 * 10^-14 sq meter of Earth could have an IP address.

    It's 252 addresses for every known sun in the observable sky.

    Not making any 640k statements, but damn that's a lot of addresses.

  23. Re:Huh? by growse · · Score: 1

    What's IPv6 got to do with information security?

    --
    There is nothing interesting going on at my blog
  24. Re:oh the headache ... by tagno25 · · Score: 1

    IPv7 will be like ALL the odd numbed IP schemes, expermental only. We will wait until IPv8 comes out in 50+ years.

  25. Let Corps pay for IPv6 by tjstork · · Score: 1

    What's going to happen is that the internet is going to be broken up by country, so that each country will have its own set of IP addresses for IPv4. So, the people that want genuinely global internet coverage will get IPv6, but those of us who just want to be in one country can use the smaller, simpler and more efficient IPv4

    --
    This is my sig.
    1. Re:Let Corps pay for IPv6 by FireFury03 · · Score: 1

      What's going to happen is that the internet is going to be broken up by country, so that each country will have its own set of IP addresses for IPv4. So, the people that want genuinely global internet coverage will get IPv6, but those of us who just want to be in one country can use the smaller, simpler and more efficient IPv4

      I think if that were to happen you'd very suddenly realise that a lot of the services you use aren't hosted in your own country and you'd be off to get yourself an IPv6 connection.... Frankly, I can't see that ever happening though.

    2. Re:Let Corps pay for IPv6 by tjstork · · Score: 1

      I think if that were to happen you'd very suddenly realise that a lot of the services you use aren't hosted in your own country and you'd be off to get yourself an IPv6 connection.... Frankly, I can't see that ever happening though.

      Either that or I'd google using the datacenter in my own country and find another service such that I wouldn't have to switch. There's millions of people that are stubbornly on IE6 and just shift their traffic about.

      --
      This is my sig.
  26. 100s of Millions of Addresses by chrismiceli · · Score: 1

    Hmm, we need "hundreds of millions of people and devices" connected. IPv4 has 2^32 addresses, so 2^32/10^8 = ~43, so IPv4 provides "hundreds of millions" of addresses, in fact, it provides 43 hundreds of millions of addresses. No need to worry about IPv6 at all.

  27. IPv6 is the protocol of the future... by Anonymous Coward · · Score: 0

    ...and always will be!

  28. Having recently setup IPv6 ... by Sonic+McTails · · Score: 1

    I recently redid the routing on my network to add support for IPv6 through a tunnel broker. In all actuality, if your hardware supports IPv6, its VERY trivial to setup with autoconfiguration as long as you don't have a network configuration that requires DHCPv6 (such if you want ipv6 DDNS to work).

    On the flip side though, getting it setup across a tunnel broker is extremely tedious, and difficult. That being said, being able to route into the machines on my network directly is an absolute blast. Makes me wish I had a real IPv6 from my ISP.

    --
    This signature was left intentionally blank.
  29. Direct Access by LibertineR · · Score: 1
    I think they will be very successful as well, as soon as people start comparing Direct Access to the hemorrhoid of IT, the VPN.

    Direct Access works, and it works very well after a somewhat tedious configuration. Tunneling IPv6 through IPv4 will extend the life of many an SMB router, too.

  30. But we may still need nat with ipv6 as ISP may sti by Joe+The+Dragon · · Score: 1

    But we may still need nat with ipv6 as ISP may still only give you 1 ip and make you pay more per ip.

    I can see comcast doing that like they do with tv pay $6-$20 per box for rent + outlet fee.

  31. Patricksomerdmnum by Anonymous Coward · · Score: 2, Funny

    You know the most hilarious part of all this? We're currently running a protocol that the designers had NO intent of scaling. So then some of the SAME designers have turned around and come up with a scalable address scheme and protocol and NO ONE wants to use it - except for the Chinese. You know they have over a billion people over there? All of em - even the dirt farmers - seem to have a freakin computer that wants to hack my bank account!

  32. Re:oh the headache ... by JesseMcDonald · · Score: 2, Interesting

    Sure, IPv6 allows for far more individual addresses than we'll probably ever use. The idea is that, unlike with IPv4, we won't be forced to use every single one of those addresses. Instead we'll have the freedom to group them in ways which make sense--like purely hierarchical assignments, which greatly simplify routing, and unique, locally auto-generated host addresses. It's sort of like the way the name "John Smith" (which is hardly unique) consists of around 47.5 bits, assuming 4.75 bits per letter (26 letters + space). That leaves far more addressing possibilities than we need (about 10^14, vs. less than 10^10 humans), but the extra bits are useful in that they lets us skip inconvenient identifiers like Efmq Duisx.

    --
    "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
  33. anonymous coward by Anonymous Coward · · Score: 0

    This assumes that 1) network over electric utility gains user share 2) network over utility bribes the hell outta regulators to overcome both entrenchment and lobbying

    luck with that

  34. IP as transport? by glitch23 · · Score: 1
    I believe TCP, UDP and others are the transport protocols. IP is not a transport protocol. Just as the summary says:

    Networking giant Cisco sees IP (internet protocol) as the right transport and IPv6 as the logical choice for addressing.

    IP is used for addressing, doesn't matter whether its v4 or v6. It, however, is *not* the right transport because it isn't a transport method in the first place.

    And as a response to someone who said that MS is pushing IPv6....Apple is as well by including it in OS X for a long time now. That doesn't mean you have to use it though. I did hear recently that Comcast will be providing IPv6 addresses to customers in the near future. That should be interesting.

    --
    this nation, under God, shall have a new birth of freedom. -- Lincoln, Gettysburg Address
  35. odd, I work in the soon to be "smart grid" by gearloos · · Score: 1

    And I've heard nothing of this great need for change to IPv6. Score another one for misguided, uninformed media and sensationalism used as an advertising tool. Yawn, move along, nothing to see here.

    --
    "Computers are a lot like Air Conditioners" "They both work great until you start opening Windows"
  36. Re:oh the headache ... by FrankieBaby1986 · · Score: 1

    If i'm not mistaken, isn't there some part of the IPv6 standard (perhaps private nets?) where addressing works by having hosts pick a completely random number and use that, since the chances of collision are so slim?

    --
    ERROR: SIG NOT FOUND (A)bort, (R)etry, (F)ail?:
  37. Re:oh the headache ... by Anonymous Coward · · Score: 0

    [...]but the extra bits are useful in that they lets us skip inconvenient identifiers like Efmq Duisx.

    What's my Uncle Efmq have to do with anything? You're not the Jesse from over on Peachtree, are you?

    Uncle Efmq's always telling us stories about what "Jesse, bless his heart" broke this week.

  38. Top 10 why IPv4 will be around for decades... by Adeptus_Luminati · · Score: 0

    10. Who the fcsk wants to ping 2001:0db8:85a3:0000:0000:8a2e:0370:7334 on a daily basis ?!?
    9. As *some* organizations migrate to IPv6, their IPv4 addresses will be released for use by other organizations!
    8. IPv6 is a waste of bandwidth with its huge headers. PPS (packets per second) router ratings go way down - so you shorten your network hardware life-cycle + pay much more bandwidth while payload throughput is the same is less - this is very wasteful.
    7. Re-training your entire IT staff on IPv6 is going to be a huge pain in the *** and will drive costs up, not only in training but the extra downtime caused in the first couple of years due to human error.
    6. Initially you'll likely have to increase your IT budget just to purchase IPv4 to IPv6 gateways, as few large organizations are going to attempt a big-bang flip.
    5. The probability of errors in troubleshooting & configuration increases 4 fold as the addresses are 4 times as long, nevermind they are Hex to boot.
    4. 95% of the features of IPv6 can and area already being done in IPv4 years ago.
    3. There's tonnes of free $$ to be made in renting out IPv4 space in Asia. Just ask the Telcos!
    2. Organizations running critical propriatary software (i.e. not off the shelf) (i.e. banks, hospitals, military, etc) are going to have to spend BILLIONS in software re-writes, QA & testing... for what visible gains. Where's the IPv6 ROI case ?!??
    1. And lastly, don;t forget KISS and If it ain't broke... DONT FIX IT!

    Wake me up when * I * run out of IPv4 addresses.
    Adeptus

    --
    No trees were killed in the making of this post; however, many trillions of electrons were horribly inconvenienced.
    1. Re:Top 10 why IPv4 will be around for decades... by 4D6963 · · Score: 0, Flamebait

      Hallelujah! If IPv4's resilience proves anything, it's that millions of people and the thousands of companies we run/work in will do the less we have to do no matter what. That's like some days I wake up and wonder how I'll do all the things I think I have to do. Then at the end of the day I've only done one thing cause all the rest didn't matter that much.

      That's how it works for IPv6. 99% of companies gain ABSOLUTELY NOTHING from being among the first 50% to move to IPv6. That's some basic game theory for you, I'll let you guess what that means for the adoption of IPv6 by companies. What do they have to lose? Few of them even need a single public IP address of their own, and everyone will still be able to reach them long after the majority have moved to IPv6. The main flaw of IPv6 (despite its technical flaws, I mean seriously, 16 bytes addresses? What's your average Internet packet like, barely a hundred bytes?) is that as explained above there's no reason it could possibly compel anyone to move to it. To do so it would have needed some killer feature, like broadcast or something like that.

      Here's what I think will happen. Everything NATed. Even servers. You know how a single IP can host many domains? Well there you go. Now I don't know how it would work for non-HTTP protocols (can the frontline router remember which domain was asked for and always route to the correct NATed server?), but if we can't change the IP protocol (after such wide adoption you can't be surprised that the task would be so arduous) then we can have a higher level solution. None one wants to use more numbers than in an IPv4 address anyway, and even that was a PITA. Domain names are the way to go, and if the current DNS isn't good enough for it, maybe a DNSv2 can have the answer to all our problems? If someone with a better clue than me about networks and protocol could tell me if that wouldn't work out or if it actually would I'd appreciate.

      Bottom line is, IPv4 isn't broken, it's our vision of it (one public IP for everyone!) that is.

      --
      You just got troll'd!
    2. Re:Top 10 why IPv4 will be around for decades... by spectrokid · · Score: 1

      10: you ping anything on a daily basis, you use a script
      9: and you think they will sell it to you cheap??
      8: header compression is soooo last year
      7: then why are you not running Word95 across your organisation?
      6: anybody with brains has put "IPV6 compatible" on the spec list for the last 10 years
      5: somebody should invent a way of shorthand writing those adresses... oh, wait...
      4: 95% of what I use my car for, I could do in a Ford T model
      3: yep, Unfortunately I am not a Telco, are you?
      2: or, they could just use some of the shelf IPv4/IPV6 conversion stuff
      1: Try to explain an intelligent, educated non-IT specialist what NAT is and why he needs it. Then tell me again it ain't broke.

      --

      10 ?"Hello World" life was simple then

    3. Re:Top 10 why IPv4 will be around for decades... by synackpshfin · · Score: 1

      10. Why the fsck would you want to ping 2001:0db8:85a3::8a2e:0370:7334 when you have that DNS thingie? 9. As *most* of organizations migrate to IPv6, IPv4 universe is gonna be a lonely place 8. Ok, let me get this... Simpler (no header chksum, no fragmentation on router), fixed length headers need more processing power on router? Try again. 7. As already said in previous post... you're gonna have a hard time re-training your entire IT staff when you migrate from Win95 6. What? Your network hardware is more than 10 years old? BTW many vendors started IPv6 support in late 90's (previous century) 5. Sure. Especially in case of monkeys with typewriters. 4. Even if that was true the remaining 5% is worth the move. 3. I'm sure telcos will find other sources of revenue, don't you? 2. Nothing prevents those organizations from using IPv4 or IPX or whatever in their internal networks. 1. It *is* broken. I've got one word for you - NAT. You've been obviously sleeping for quite some years now. I think you're gonna wake up in dessert. ;)

    4. Re:Top 10 why IPv4 will be around for decades... by synackpshfin · · Score: 1

      10. Why the fsck would you want to ping 2001:0db8:85a3::8a2e:0370:7334 when you have that DNS thingie? 9. As *most* of organizations migrate to IPv6, IPv4 universe is gonna be a lonely place 8. Ok, let me get this... Simpler (no header chksum, no fragmentation on router), fixed length headers need more processing power on router? Try again.
      7. As already said in previous post... you're gonna have a hard time re-training your entire IT staff when you migrate from Win95
      6. What? Your network hardware is more than 10 years old? BTW many vendors started IPv6 support in late 90's (previous century)
      5. Sure. Especially in case of monkeys with typewriters.
      4. Even if that was true the remaining 5% is worth the move.
      3. I'm sure telcos will find other sources of revenue, don't you?
      2. Nothing prevents those organizations from using IPv4 or IPX or whatever in their internal networks.
      1. It *is* broken. I've got one word for you - NAT.

      You've been obviously sleeping for quite some years now. I think you're gonna wake up in desert. ;)

    5. Re:Top 10 why IPv4 will be around for decades... by 4D6963 · · Score: 1

      10. So why ping IPv4 addresses now?
      9. Yeah, and when Megan Fox becomes my girlfriend all the other girls who rejected me will so regret it. Besides, what you mean lonely place? Everybody's gonna still be able to connect with IPv4 for decades, even if IPv6 was adopted by all tomorrow.
      8. He said bandwidth. 16 bytes just for the raw address. What's your average IP packet length?
      7. Yeah, because IPv6 so is as trivial as migrating to a new version of MS Word.
      4. What's in those 5%?
      3. Sure, who in their right mind would want to exploit an artificial scarcity for profit?
      2. lol, you're kidding, right? You're not really suggesting to use IPv6 for the Internet and everything-IPv4 for the LAN, are you?
      1. What's so broken about NAT? That everyone doesn't get their very own public IP? Well boo-fucking-hoo! Is that what the big deal is all about??

      Seriously, I know people around here like to shout "DOOOOMED!! WE'RE DOOOOOMED!!", but it looks like just another "OMG Y2K TEH COMPUTALYPSE IS COMING!!" to me. Lots of noise for not much. What if everybody's behind NAT? Give me your Doomsday scenario and why anyone with a company should care even a bit.

      --
      You just got troll'd!
  39. Re:oh the headache ... by Anonymous Coward · · Score: 0

    Hey! My name is Efmq Duisx you insensitive bastard!

  40. Re:oh the headache ... by Anonymous Coward · · Score: 0

    You are doing a A divide by B comparison. According to the specs, every point-to-point network connection will get a /64 assigned to it, something that currently needs just 2 IPs (and those IPs can repeat as they can be in the 10. or 192.168. address spaces). The smallest network is a /64, so you get a whole /64 for your house (assuming a simple network). Little companies are getting /48's for asking for them, ISP's /32's or larger.
    So, while the numbers are still impressive and big, the specifications mandate that a huge percentage of the addresses will be unusable.

  41. Re:oh the headache ... by mysidia · · Score: 1

    There will likely not ever be an IPv7 release, because the IPv7 protocol one of the proposals a long time ago as the protocol designed to replace IPv4.

    RFC1475, TP/IX: The Next Internet

    The version number has been spent.

    That is, unless the IETF continues the work on that protocol and implementations are made in such a way that it supercedes IPv6. Still... after upgrading to 128-bit addresses, people are unlikely to want to downgrade back to 64-bit IP addresses.

    It's funny though:

    2.1 Is 64 Bits Enough?
    Consider: (thought experiment) 32 bits presently numbers "all" of the computers in the world, and another 32 bits could be used to number all of the bytes of on-line storage on each computer. Most have a lot less than 4 gigabytes on-line, the ones that have more could be notionally assigned more than one address.)

    Of course ultimately they missed the point that IP addresses have structure to them. Address spaces get divided into networks.. Having enough addresses for all hosts doesn't necessarily prevent shortages, if the networks aren't divided along the right lines.

    Also, if the networks are divided at too small a level, you get fragmentation, and routing table explosion.

    But then all that's why IPng became IPv6.... as far as V7 was concerned, good riddance :)

  42. Re:oh the headache ... by paul248 · · Score: 1

    IPv7 was specified in 1993:
    http://tools.ietf.org/html/rfc1475

  43. Easier to get IPv6 than IPv4 in many places by Casandro · · Score: 1

    Well if you are with a cable or mobile ISP it might even be easier to get propper IPv6 than IPv4. Just set up a tunnel to a tunnel broker like Sixxs for example. It will even work through NAT and you'll get 2^80 IPv6 adresses.

    I mean even today there are ISPs which only give you NAT. ISPs which filter your IPv4 traffic or inject additional packets to keep you from using IPv4. Many ISPs also only give you one dynamic IP-address and charge more if you want more of them.

    I mean IPv4 is so hard to use by now that people actually prefer Google reading through their mail instead of setting up their own mailserver! With IPv6 that's trivial to do. You can also easily log into your computer at home without having to go through hoops like dynamic DNS.

    1. Re:Easier to get IPv6 than IPv4 in many places by Tony+Hoyle · · Score: 1

      How the hell did you get from 'ipv4 is hard to use' to everyone using gmail? That's quite a logical leap. And ipv6 won't change that one bit.

      I can log into my computer at home. Any of them, in fact, as I have 16 IPs.. but then I have a half decent ISP. If it matters that much to you get one of those don't complain that for $5 a month your ISP uses dynamic IPs and doesn't like you running servers. The situation will be *exactly* the same with ipv6, by the way, if cheap ISPs ever move to it (and if they do, they'll be the last).

      btw. sixxs *global* traffic averages less than 100Mbps. There's nothing travelling over ipv6... moving now makes no sense.

    2. Re:Easier to get IPv6 than IPv4 in many places by Casandro · · Score: 1

      Well actually moving now makes a lot of sense as you will be one of the first to be on IPv6. Nobody cares what you do on IPv6 so you can easily just run FTP-Servers and be sure that nobody except the people you tell that will ever find you. You can do Bittorrent without any problems, in fact Sixxs.net is having it's own IPv6-only tracker. IPv6 still is free.

      And not many people are as lucky as you actually having an ISP giving you 16 IPs. In Germany for example you'll have to get a commercial account and those are many times as expensive as domestic ones. In Africa and Asia you are lucky if you get a single public IP-address at all. There you often are behind several layers of NAT.

  44. Re:oh the headache ... by mysidia · · Score: 1

    However, nothing prevents wasteful allocation from spending all those addresses.

    A lot of "Critical infrastructure" are getting their own /32. Each root server. 4294967296 /64s (65536 /48s) allocated for each one. These are IPs that get permanently reserved, and can't be assigned to people on earth.

    And root servers are just one example. There are a lot of other cases where /32s are being assigned to non-ISPs (including the registries direct-assigning /32s to themselves for their own use) who will never need that many addresses.

    Major ISPs get a /32 or bigger. And are encouraged to give each customer a /48 for each physical location. That is, the smallest amount of space an end user gets is /48.

    So the real question is... how does 281474976710656 compare to the world population?

    Well, when the world population reaches 1 billion, each can have 200,000 /48s; if they're distributed fairly, that is, and not tied up in wasteful /32 reservations to defunct or legacy ISPs as happened with IpV4 space, sometimes.

    And 1208925819614629174706176 is a lot of ip addresses indeed... but individuals won't be numbering atoms or grains of sand.

  45. Re:oh the headache ... by Mhtsos · · Score: 1

    Can I start with the lain jokes yet?

  46. Re:oh the headache ... by TheLink · · Score: 2, Interesting

    Sounds like a problem waiting to happen.

    What are the odds that some popular software/code turns out to be not so good at picking completely random numbers.

    --
  47. Cisco = unaffordable by lanner · · Score: 1

    If Cisco manufactures those "smart grid" (corp bullshit word) devices, nobody will be able to afford them, thus eliminating any requirement for IPv6.

    I like how Cisco whines about IPv6, but let's face it; They charge a bunch of money for you to actually be able to use IPv6 in most of their products. Even the modern 3750-E series switches requires a multi-thousand dollar license to support IPv6, and the list of caveats is huge! Half the crap that you do with IPv4 won't even work with their IP Services images enabled.

    Be looking at Juniper and other manufactures for IPv6 support. Cisco won't help their customers until they are forced into it.

  48. Blah blah, cough bullshit! by LostMyBeaver · · Score: 1

    Yeh, cause I'm going to directly attach all my devices to the Internet. Some idiot in marketting doesn't get it.

    Using protocols like XMPP, SIP, etc... the devices will connect to servers for session initiation. Given low bandwidth situations where there are settings like "Turn oven on at 5:12pm", messages will be passed without the need for firewall traversal directly from the server which already have open connections to the devices.

    For higher bandwidth situations, like a camera in the fridge that lets you monitor whether the light is out or if your cheese is green, firewall traversal mechanisms will be used. STUN and derivatives are reliable now.

    Each house or community really only needs a single public IP address now. There's little or no benefit of IP addresses for the user anymore.

    1. Re:Blah blah, cough bullshit! by Tony+Hoyle · · Score: 1

      I'm with you on house (unless you're a geek you don't need more than one IP) but community? That would be messy. It'll happen - carrier grade NAT will happen long before ipv6 (and is happening already, on mobile networks).. but it'll still be messy.

  49. Re:oh the headache ... by Tony+Hoyle · · Score: 1

    Well.. it would except we're giving it out in huge blocks.

    ipv6 has 128 bits, but for RA to work your home router has to have a /64 even if you only have one machine.. so that's half of them gone.. ISPs are supposed to allocate you a /48 (mine does) again, if you only have one machine that's wasteful.

    The top couple of bits are used for address type, so you're down to 46 bits of actual information. Still a lot, but nowhere near the 'atoms in the universe' idea.

  50. I did make a comment in another article that says IPv6 will be redundant when it becomes standardised. IPv10 is the standard we should be aiming for. If you think IPv6 is the solution you are higly mistaken and not taken in to consideration the full picture of devices and stream carriers. Smart Grids are already in operation in power stations and nuclear facilities. France has a good one already which is where the UK gets some electricity from!

    --
    All cows eat grass!
  51. Re:oh the headache ... by Anonymous Coward · · Score: 0

    You'll have to talk to Masami Eiri about that one.

    Not sure we want to implement it...

  52. IPv6 by Anonymous Coward · · Score: 0

    Apple fanboys would drool over it, but the rest of us will just .. err. wait ..

  53. Re:oh the headache ... by Muad'Dave · · Score: 1

    I'd check your division there, Sparky. 2^127 / 2^ 128 = half. 2^128 / 2^64 = 2^64.

    --
    Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
  54. What IPv10? by JSBiff · · Score: 1

    I've never heard of anyone work being done on IPv10. What are you talking about? Why would IPv6 be insufficient? Are you worried it doesn't have sufficient address space? There should be enough addresses in IPv6 for every person on the planet to have millions of addresses: the addressing scheme allows for 2^128 which is large enough that we'd only ever need to increase the address space if we intended to deploy billions of swarms of billions of individually addressed nano-bots.

    Or is there some other technical deficiency of IPv6? Or are you just trolling?

    1. Re:What IPv10? by NSN+A392-99-964-5927 · · Score: 1

      I've never heard of anyone work being done on IPv10. What are you talking about? Why would IPv6 be insufficient? Are you worried it doesn't have sufficient address space? There should be enough addresses in IPv6 for every person on the planet to have millions of addresses: the addressing scheme allows for 2^128 which is large enough that we'd only ever need to increase the address space if we intended to deploy billions of swarms of billions of individually addressed nano-bots.

      Or is there some other technical deficiency of IPv6? Or are you just trolling?

      Firstly, I am not trolling and China has been experimenting with IPv9 for the past 3 years to get an edge. Maybe I failed to explain myself in a clear manner, mainly because the mind boggles and you can call me a troll all you like, but every device you can imagine in 20 years will have commands issued remotely from alarm clocks to smart embedded chips under your skin, biometrics, banking you name it. Therefore there has to be scope in order for these services to work. Yes some services will run on IPv6 as will some on IPv4. Now if you think I am bonkers or lost the plot. I was a close friend of Sir Arthur C Clarke and visited him many times in Sri Lanka when he was alive and we had huge discussions at his house in Columbo which was a huge eye opener on issues like this, so yes I am bonkers and if you like I am a troll too. It still does not change the fact that IPv10 is a standard to aim for.

      --
      All cows eat grass!
  55. Re:oh the headache ... by Ksevio · · Score: 1

    So you're saying we'll have less than a current /24 for each solar system with IPv6? This is really going to hamper us once we have an interplanetarynet.

  56. Re:But we may still need nat with ipv6 as ISP may by Anonymous Coward · · Score: 0

    Possibly, but owing to principles of supply and demand, they could not continue to cost as much as ISP's currently charge people for extra IPv4 addresses.

    Of course, owing to the same principles of supply and demand is the underlying reason why IPv6 hasn't really achieved mainstream adoption in the first place, which is kind of ironic, huh?

  57. Re:oh the headache ... by sjames · · Score: 1

    Yes, the privacy extension. But it's supposed to send a probe packet (Duplicate Address Detection) to make sure nobody selected the same random address.That takes the chances of collision from slim to none. Machines using the privacy extension are expected to periodically depricate their selected address and choose a new one. That prevents external servers from establishing a 1to1 map of IP address and machine.