Slashdot Mirror


How Things Will Change Under IPv6

Da Massive writes "IPv6 Forum leader Latif Ladid provides an insight into the workings of IPv6. He also talks about how peer-to-peer file serving as we know it today will be redundant with the newer protocol." From the article: "Q: What is the most significant benefit that IPv6 offers the world? A: Global connectivity. Currently we have less than 50 percent world-wide Internet penetration, and we have used most of the address space. If you look at the Western world, we have more than 50 percent penetration. In total we have close to a billion people connected to the Internet. So it is a false perception that we have full Internet penetration. We have six billion people on the planet. When the Internet protocol was designed back in 1980 there were 4.3 billion address spaces; it was already insufficient for the population. By 2050 we will be nearly 10 billion people. But there are not only people. There are things. Billions and billions of devices that will service these people."

450 comments

  1. Haha... by NIN1385 · · Score: 0, Offtopic

    You said penetration.

    --

    If carrots got you drunk, rabbits would be fucked up. - Comedian Mitch Hedberg R.I.P. 03/30/68-2/24/05
    1. Re:Haha... by NIN1385 · · Score: 5, Informative

      Awww... c'mon, that's classic family guy comedy!

      --

      If carrots got you drunk, rabbits would be fucked up. - Comedian Mitch Hedberg R.I.P. 03/30/68-2/24/05
    2. Re:Haha... by utnow · · Score: 0, Redundant

      "Billions and billions of devices that will service these people."

      I should go get one...

  2. Billions and billions of devices... by zenmojodaddy · · Score: 1, Funny

    I call it The Thingternet!

    1. Re:Billions and billions of devices... by Anonymous Coward · · Score: 2, Funny

      Oh come on, that's just thtupid.

    2. Re:Billions and billions of devices... by RichardX · · Score: 1

      Billions and billions? Shouldn't it be the Sagannet?

      --
      Curiosity was framed. Ignorance killed the cat.
    3. Re:Billions and billions of devices... by necro81 · · Score: 2, Insightful

      Billions and billions of devices...

      Ah, if only Carl Sagan were alive to hear that comment!

    4. Re:Billions and billions of devices... by hunterx11 · · Score: 1

      For legal reasons, it will be called the BHAnet instead.

      --
      English is easier said than done.
  3. Why not give PEOPLE addresses? by KinkoBlast · · Score: 1, Interesting

    Like Jabber. if my IP was 1:2:3 then my fancy Intenet Coffee Pot would be 1:2:3:coffeepot1

    1. Re:Why not give PEOPLE addresses? by bhirsch · · Score: 3, Interesting

      How about if your domain name is blahblah.com, then your web server could be www.blahblah.com? It gets better: Your mail server could be mail.blahblah.com. And yes, your coffe pot could be coffeepot1.blahblah.com.

    2. Re:Why not give PEOPLE addresses? by MosesJones · · Score: 2, Interesting

      Errr you did read the bit that said that IPv4 can't support the number of people on the planet already? Also you do know that all you are talking about is a secondary addressing approach (network 1 : 1.2.1.2, sub-network : 2.3.3.3) which is already possible on IPv4, but requires an agreed standard for the secondary networking approach.

      Oddly secondary networks have been considered during all of this, but it was easier to update the primary network addresses rather than formalising NATs which had other issues.

      --
      An Eye for an Eye will make the whole world blind - Gandhi
    3. Re:Why not give PEOPLE addresses? by dslauson · · Score: 4, Interesting

      Not a terrible idea, but it assumes that end users are going to be able to figure out how to configure static IP addresses for all their devices, which is a pretty big assumption.

      Plus, who would be in charge of assigning them? Would that mean that I have to register for an IP like I do for a domain name? Who's handing them out, the DMV? The Social Security office? The UN?

      Also, it seems like it would be easy for hackers to mimic other people's IP address. Seems like maintenence nightmare.

    4. Re:Why not give PEOPLE addresses? by CosmeticLobotamy · · Score: 1

      He used the colon notation (1:2:3) not the dot (1.2.3.4), so it's very likely he was talking about v6.

    5. Re:Why not give PEOPLE addresses? by rekoil · · Score: 2, Informative

      No need - your IPv6-enabled DSL/cable modem will contain a Router Advertisement Daemon that takes care off all that for you.

    6. Re:Why not give PEOPLE addresses? by Mercano · · Score: 3, Informative

      It wouldn't really be routable. There would be no way figure out which way to send the packets for a given "address." For istance, under IP4, any router that sees a packet going to any machine with an address starting with 129.22 (one of the few blocks I know off the top of my head) knows that the packet should be pushed out a pipe that heads in the general direction of Cleveland. In fact, most routers probably work off even broder rules, with (just making this up, now), all address starting with 129.17-129.32 should be pushed out towards OAR net, then OARnet would do more focused routing in house.

      With "people address", there are three problems. First, no way to generalize routing rules. Secondly, there is the fact that all your stuff might not be in the same place. Most of it is at your house, but some of it is at the vacation home. Finally, there is the problem that people, unlike IP4 address, tend to move arround alot, geographically speaking. Usually, if you move from New York to LA, you get a different IP, even if you use the same national ISP. Under your scheme, the whole internet would have to be told to redirect your trafic. Yick.

      --
      #include <signature.h>
    7. Re:Why not give PEOPLE addresses? by mediocubano · · Score: 2, Funny

      but when some kiddie wants your IP to hack into your system you'll have to give him something other than "127.x.y.z". You'll have to make up a much longer number.

    8. Re:Why not give PEOPLE addresses? by onwardknave · · Score: 3, Funny

      As noted by the recent spate of cellphone-targeting malware....if you don't have the latest coffeepot firewall, someone could make you wake up to decaf! The horrrrror!

    9. Re:Why not give PEOPLE addresses? by xRizen · · Score: 1

      You mean like fe00::0?

    10. Re:Why not give PEOPLE addresses? by Cramer · · Score: 1

      And you are missing an important point: Every human in existance doesn't need an IP address.

      I'm one person with dozens of machines, yet I get along just fine with one IPv4 address. My office, with 2 dozen people and many more machines, gets along just fine with ONE IPv4 address.

      So, STOP with the BS that every grain of sand in the universe needs an address! Eventually, yes, we will exhaust available IPv4 addresses, but that's not going to happen tomorrow -- more like decades from now. People are not going to throw away a perfectly workable, deployed, solution until there's a real need -- i.e. until there are real problems, not theoretical problems decades away.

    11. Re:Why not give PEOPLE addresses? by JayJay.br · · Score: 1

      How about ::1?

    12. Re:Why not give PEOPLE addresses? by KinkoBlast · · Score: 1

      All those still need IPs. And here is something that you might find interesting:

      Not everyone has a domain name.

      Well, technicaly I beleve they do, but in many peoples case its the million-char-long one your ISP assigns so you have one for RDNS lookups.

    13. Re:Why not give PEOPLE addresses? by drakaan · · Score: 4, Insightful
      Quick test: if you have a web server running on each of your dozens of machines (all on port 80...no bucking the standard), can I connect to each of them using http?

      No? Why not? Why can't you just get more IPv4 addresses so that I can connect to each of them?

      The advent of NAT has solved the main problems that ISPs have had with giving their customers addresses to use for connecting to "content providers", but it has pretty much eliminated the original "every node is a peer" architecture of the internet.

      Sure, if you're an ISP that works for you, but if you're some random guy that wants it to be easy to connect two (currently natted) devices together without involving a third device as a go-between, it's not such a good solution.

      It's easy not to get it, just because we're all so used to having to do things the way we have been forced to. The epiphany comes when you realize how much more flexible the system is when NAT is not involved.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    14. Re:Why not give PEOPLE addresses? by indifferent+children · · Score: 2, Funny

      Which thanks to recent health studies, can now be prosecuted as Attempted Murder.

      --
      Censorship is telling a man he can't have a steak just because a baby can't chew it. --Mark Twain
    15. Re:Why not give PEOPLE addresses? by bhirsch · · Score: 1

      I was being facetious. Your idea mitigates a problem unrelated to IP address space and would cause more difficulties in implementation than IPv6.

    16. Re:Why not give PEOPLE addresses? by kwalker · · Score: 1

      No, the "end user" will just have an extra step when setting up their D-Link wireless router. Instead of it handing out 192.168.*.*, it'll hand out 0:1:2:3:4:5:: and instead of a NAT firewall rule, it'll have a FORWARD firewall rule.

      As for who assigns them, it'll probably be the same people who hand out IPV4 addresses now, and you have to register with the same people if you want a portable IP address now.

      And like it isn't difficult for "hackers" to "mimic" IP addresses now...

      --
      ... And so it comes to this.
    17. Re:Why not give PEOPLE addresses? by grahamlee · · Score: 1
      Quick test: if you have a web server running on each of your dozens of machines (all on port 80...no bucking the standard), can I connect to each of them using http? No? Why not? Why can't you just get more IPv4 addresses so that I can connect to each of them?

      If you have that many web servers in one institution and need external visitors to be able to connect directly to each I would suggest you don't have an effective sysadmin.

    18. Re:Why not give PEOPLE addresses? by kabocox · · Score: 2, Funny


      With "people address", there are three problems. First, no way to generalize routing rules. Secondly, there is the fact that all your stuff might not be in the same place. Most of it is at your house, but some of it is at the vacation home. Finally, there is the problem that people, unlike IP4 address, tend to move arround alot, geographically speaking. Usually, if you move from New York to LA, you get a different IP, even if you use the same national ISP. Under your scheme, the whole internet would have to be told to redirect your trafic. Yick.


      You've missed the tin foil hat consipary theory. Assigning an IP address to all newly minted currency along with some RFID and GPS. Instantly, the MAN and your neighbor could ping all your money! The IRS would know exactly how much cash that you have stuffed under your bed!

    19. Re:Why not give PEOPLE addresses? by Sharkeys-Day · · Score: 1
      Quick test: if you have a web server running on each of your dozens of machines (all on port 80...no bucking the standard), can I connect to each of them using http?
      Yes, it is quite easy with named virtual hosts and reverse proxies, and the usual NAT firewall.
      NameVirtualHost 1.2.3.4 # my only IPv4 address

      <VirtualHost machine1.my.domain>
      ProxyPass / http://10.3.2.1/
      ProxyPassReverse / http://10.3.2.1/
      </VirtualHost>

      # etc.
      I say again: removing NAT does not remove firewalls. You will still have the same problems getting your traffic through the firewall (especially corporate ones), even if the address no longer has to be munged.
    20. Re:Why not give PEOPLE addresses? by Luyseyal · · Score: 1

      Of course, the FORWARD rule will be followed with DENY ALL BUT INTERNALLY-INITIATED CONNECTIONS without explicit user override.

      Cheers,
      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
    21. Re:Why not give PEOPLE addresses? by drakaan · · Score: 2, Insightful
      I'm confused about your example. You say

      Yes, it is quite easy with named virtual hosts and reverse proxies, and the usual NAT firewall.

      ...and then you give an example of something that demonstrates specifically that I cannot connect to those web servers...I have to connect to a proxy.

      So, your answer is "no, you can't do that without a third machine as a go-between".

      I'm not talking about removing firewalls...access control is a necessity in any network that's open to the public (I think I even mentioned having a firewall in what you responded to). What I'm talking about is the perversions that NAT forces us through.

      Suppose we were talking about a different protocol...should we have no choice but to use proxies for any given protocol just because we want to connect to it on more than one machine in a given network?

      Again...NAT solves the problems that ISP's have. It ensures that they can continue on without making significant changes, and lets their customers make outbound connections pretty easily, most of the time. It does so by removing the ability of any machine on a given network to be a peer simultaneously with other wanna-be peers if they're behind a NAT device.

      NAT is an artful hack, and it has spawned many other artful hacks (virtualhosts, name-based and otherwise, being examples), but why would you want to make things complicated and restrictive when they can be simpler and open?

      There comes a time when you're just arguing to argue. I know, believe me (been there, done that). Drop me a note when you've had your own moment of clarity.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    22. Re:Why not give PEOPLE addresses? by NatasRevol · · Score: 1

      So every user would have to do that for every 'coffeepot'?

      Doesn't seem a workable solution, even if it is a technical solution.

      --
      There are two types of people in the world: Those who crave closure
    23. Re:Why not give PEOPLE addresses? by Anonymous Coward · · Score: 0

      That's awesome. At birth we could give everyone a nine digit code that would be their personal id number. They could carry it around their whole life and...wait a minute. Don't I already have one of those?

      --SSN

    24. Re:Why not give PEOPLE addresses? by Sharkeys-Day · · Score: 1
      ...and then you give an example of something that demonstrates specifically that I cannot connect to those web servers...I have to connect to a proxy. So, your answer is "no, you can't do that without a third machine as a go-between".
      I figured you knew about gateways and routers already. It's not as if you are on the same ethernet wire as I am.

      The end user doesn't know or care about the proxy any more than he knows or cares about all the other routers between us, at least for the http example you asked for.

      For other protocols, how are you going to convince the security manager in XYZ corporation to let your traffic through?

      arguing to argue
      There comes a time when you resort to personal attacks because your argument doesn't hold up, but I would prefer we don't do that, so let me make my position clear:

      The end of NAT will not convince me of IPv6's superiority.

      A very few enlighted people in this discussion have mentioned advantages in routing and other things, but they are being drowned out by the people yelling "NAT IS DEAD". People have been talking about the increased address space for years and years. There must be a reason why that hasn't convinced others to switch yet.

      If you want to convince me that IPv6 is better, please find another advantage to talk about.

    25. Re:Why not give PEOPLE addresses? by Sharkeys-Day · · Score: 1

      So every user would want to do that for every 'coffeepot'?

      Doesn't seem a realistic problem, even if it is a technical problem.

    26. Re:Why not give PEOPLE addresses? by Phisbut · · Score: 1
      Of course, the FORWARD rule will be followed with DENY ALL BUT INTERNALLY-INITIATED CONNECTIONS without explicit user override.

      Just like wireless routers have "don't broadcast until the user explicitely configures you to broadcast"...

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
    27. Re:Why not give PEOPLE addresses? by omegaloki · · Score: 1

      IIS and host headers... What's the problem?

    28. Re:Why not give PEOPLE addresses? by netkid91 · · Score: 0

      Problem: IIS(Information is shit)

      --
      NO~, I read Slashdot because I think it's stupid.....
    29. Re:Why not give PEOPLE addresses? by Luyseyal · · Score: 1

      Indeed, the point here is that "everything having a routable address" != "everything is insecure". By default, IPv6 DSL/Cable routers won't let traffic inbound unless the user specifies, but you gain the benefits of having a routable address, such as VPN being plug-n-play instead of plug-n-configure-a-bunch-of-annoying-crap.

      People tend to confuse the firewalling features of routers with NAT.
      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
    30. Re:Why not give PEOPLE addresses? by drakaan · · Score: 1
      I figured you knew about gateways and routers already. It's not as if you are on the same ethernet wire as I am.

      You're absolutely right. How about this. We can just replace all of the routers currently in use with proxies. If you're arguing that they're equivalent, or something like that.

      For other protocols, how are you going to convince the security manager in XYZ corporation to let your traffic through?

      I'm not. Why would I? Most corporations don't suffer from the dearth of IP addresses that the rest of us do, and my goal is not to get around security that's in place on purpose. On other protocols, how am I going to let more than one machine inside my NATed network be a peer for an arbitrary protocol or port?

      Anytime I'm at home and I want to set up anything, I'm limited to masq rules in my router/firewall or virtualhost directives on my web server (or using non-standard ports). Notice that all of those are work-arounds for dealing with not having enough addresses? We consider them necessary because we don't want to change something.

      I'm not sure what you read that you felt was a personal attack, but I suppose I might have said something to justify that comment. If so, I apologize.

      I'm not yelling "NAT IS DEAD"...it's not. I use it (I have no choice, really). What I'm trying to say is that there would be advantages to regular people if we transitioned to IPv6 (as well as confusion, heartache, overhauling, etc). Non-NATed IP addresses mean direct communication is possible, and that opens up a lot of possibilities in node-to-node communication that are not possible via NAT.

      You keep bringing up the work-arounds that are already in place, and while I agree that they work all right for the way we use the net right now, making them go away could open the door to new ideas, new functionality, and a whole new experience for everyone.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    31. Re:Why not give PEOPLE addresses? by Anonymous Coward · · Score: 0

      ipv6 will auto-delegate from you /48 based on your mac address. At least learn the protocol before you try and bash it.

    32. Re:Why not give PEOPLE addresses? by Sharkeys-Day · · Score: 2, Interesting
      If you're arguing that they're equivalent, or something like that.
      I am, actually. You should have quoted my next sentence, which explains that they are all the same (i.e. invisible) to the end user, who doesn't even want to know about IPv4 or IPv6 addresses. "google.com" gets him where he wants to go, and everything else is implementation details.

      And as a home user, it may be a bit annoying to me too, but it is still just implementation details. Set it up once, and I'm done. Now I actually have to build that website...

      Most corporations don't suffer from the dearth of IP addresses that the rest of us do, and my goal is not to get around security that's in place on purpose.
      Actually, 99.99% of of corporations do suffer from the same lack of IP addresses. But NAT and firewalls have solved that problem for them, and most are actually happy for the extra guarantee that their internal traffic cannot be accidently routed over the network at large.

      You keep bringing up the work-arounds that are already in place, and while I agree that they work all right for the way we use the net right now, making them go away could open the door to new ideas, new functionality, and a whole new experience for everyone.
      That may be true. But vague hopes are not going to convince anyone to switch to IPv6.

      You cannot ignore the needs of large corporations, because IPv6 will not be widely adopted until they get on board. The bigger address space is not convincing them, because they are going to keep their firewalls whether they NAT or not, so the proxy is not going away. They need another, better benefit before they will adopt IPv6.

      I'm not arguing that more addresses are bad, or that we should NOT adopt IPv6. I'm simply asking for another reason, any other reason, why we SHOULD adopt IPv6.

    33. Re:Why not give PEOPLE addresses? by ToasterofDOOM · · Score: 1

      not efficient. When it can be denoted in pure binary, then you have efficiency. It's not like jabber doesn't in the end rely on IP anyways.

      --
      I am Spartacus
    34. Re:Why not give PEOPLE addresses? by kosmicki · · Score: 1

      Stockpile currency now! Any US note is good for its face value no matter how old it is.

      Or have a tinfoil lined mattress. :)

    35. Re:Why not give PEOPLE addresses? by Jearil · · Score: 1
      I'm simply asking for another reason, any other reason, why we SHOULD adopt IPv6.


      VoIP

      At my company I was in charge of setting up the new phone system (VoIP running the asterisk PBX software). One of the biggest pains in the entire setup has had to do with NAT, specifially with the SIP protocol. There is another protocol that works with this type of system through a NAT (the IAX2 protocol), but there's some limited use. You see, most hard VoIP phones sold use the SIP protocol. The SIP protocol doesn't work very well through NATs. If no NAT is involved, it works fine. Our internal phones on the internal LAN work perfectly due to no NAT. We also have several minor offices all over the world that are using these VoIP phones.. some from their own home broadband connections. Most of those home connections use some form of NAT through their home router. These SIP phones do not work most of the time through the NAT (Sometimes they do.. it's about 50/50).

      There are IAX2 phones, but those are very new, low on features, and don't fit the standard setup we have already.

      Now if both sides (Server and phone over the net) are behind a NAT, it's impossible to connect. That's to be expected.. there needs to be at least one end-point in any situation like that. That also means that if I wanted multiple PBXs (I'm sure there's a use for that), I'd need multiple addresses. And man, it would sure make my job easier if I could get my users to have their own unique IP address just for their phone.. but no ISP will give you a second IPv4 address just for your phone -- well at least without charging you an arm and a leg.

      So I could easily see a very quickly growing market (VoIP phones) gaining quite a bit from an IPv6 transition.
    36. Re:Why not give PEOPLE addresses? by Sharkeys-Day · · Score: 1

      NAT. Same reason. Any other reason?

      I agree asterisk is way cool, but shouldn't the remote office have their own asterisk server, so inter-office calls can be routed over IAX2?

      The home broadband users are screwed, but most users in that situation are required to use a VPN to access the internal company network. It's hard enough to keep laptops from bringing viruses from one network to another, without some home user innocently routing around the corporate firewall. That brings in another host of routing problems. Many VPN packages will prevent any traffic from outside the connected host from being routed for security, including the VoIP phone. If you get rid of the NAT, you still have the same problem, this time for security reasons.

      I grant that you have more experience with asterisk than I do (I just do IVR apps with it), so I will accept any rebuttal to that silently, but I would still like a reason other than NAT to migrate to IPv6. It apparently hasn't convinced your company to switch.

    37. Re:Why not give PEOPLE addresses? by mrmud · · Score: 1

      In fact, most routers probably work off even broder rules, with (just making this up, now), all address starting with 129.17-129.32 should be pushed out towards OAR net, then OARnet would do more focused routing in house.

      Absolutely correct. But it's still possible. You assign a whole ipv6 subnet that goes to /people/. Then that particular network deals with the joy of routing to people -- much like a cell phone network. (patent pending;)

      --
      -- MrMud
    38. Re:Why not give PEOPLE addresses? by nzkbuk · · Score: 1

      The people giving them out are the same lot as giving ipv4 addreses namely arin, ripe, apnic, lanic (put www before and .net after each).

      Part of the advantage of ipv6 is you can get your own portable network assignment. where current networks are aaa.bbb.ccc.ddd ipv6 addresses are aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh currently globally routable / assigned ones start 2001:: ....
      The cool part is you can get an assignment like gggg:hhhh (which is the size of 10.0.0.0/8 (about 16.5 million addresses) ) which is portable aka you can take it to different isp's. They just handle the routing for the bits before.

      As for having to remember / hand them out. Well the ipv6 ip's are typically based on MAC address (hardware address) that is built into your computer. I'd expect every home router would have radvd (router advertising demon) on it, just like all of them have dhcp on them these days.

    39. Re:Why not give PEOPLE addresses? by Anonymous Coward · · Score: 0

      Here's a reason:

      Better download speed. IPv6 have shown to be quite a bit faster than IPv4 in regards to transfer rates.

      I don't know about you, but I sure as hell would appreciate a way to get all those porn vid^H^H^H^H^H^H^H^H free software ISOs down faster and if it could save me the cost of upgrading my company's line out into the real world, all the better.

    40. Re:Why not give PEOPLE addresses? by GrievousMistake · · Score: 1
      they are all the same (i.e. invisible) to the end user, who doesn't even want to know about IPv4 or IPv6 addresses. "google.com" gets him where he wants to go, and everything else is implementation details.


      Untrue. When, to take a random example, Blizzard has to walk end-users through setting up portforwarding on their routers for the WoW updater, the hack that is NAT is being inconvenient and very visible.
      I don't know about corporate networks, I suppose it might be okay to have your network cut off from targetted inbound connections, but NAT in a home network is a bother for all kinds of p2p traffic. Torrents, skype, messaging all require quite a bit more set-up than "google.com"
      --
      In a fair world, refrigerators would make electricity.
    41. Re:Why not give PEOPLE addresses? by drakaan · · Score: 1
      I didn't quote your sentence about everything being the same/invisible to end users, that's true. I didn't quote it mainly because I don't agree with it. There are plenty of protocols that don't automatically work behind a NAT (especially when both ends of a wanna-be connection are behind a NAT). That makes things not invisible.

      The average user is not smart about why certain things don't seem to work well (slow bittorrent downloads, gnutella not working well, etc, etc). Theere's a real problem in the ways that applications have to be developed now vs. the way they would be able to be developed in an internet without NAT. Firewalls would still work as intended and stop undesired connections, but basic node-to-node connectivity wouldn't suffer as it does with NAT.

      My comment about corporations was meant to illustrate the point that they don't *suffer* from the same problem, not that they don't face it. They have resources and people and know about site-to-site VPNs that get them past the problems that NAT causes otherwise. Firewalls solve the same problem as ever, but NAT causes problems with inter-site connectivity that have to be engineered around.

      Your question sounds like a good "ask Slashdot", actually...I'd love to see that conversation played out.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  4. But when? by Anonymous Coward · · Score: 4, Insightful

    How long will a complete transition to IPV6 take? Many many years IMO, if it ever happens at all. None of the firms I know of or work with have even started looking into migrating yet. Hell they are'nt even talking about it.

    1. Re:But when? by jimbolauski · · Score: 2, Insightful

      I'm personaly hoping that we run out I can't wait see the time share IP address and IP addresses on ebay.

      --
      Knowledge = Power
      P= W/t
      t=Money
      Money = Work/Knowledge so the less you know the more you make
    2. Re:But when? by aonaran · · Score: 4, Insightful

      "How long will a complete transition to IPV6 take? Many many years IMO, if it ever happens at all. None of the firms I know of or work with have even started looking into migrating yet. Hell they are'nt even talking about it."

      This is the thing that bothers me, it looks like y2k all over again. No body thinks it's a problem until there's a last minute scramble to get the issue resolved.

      The only difference is this time around there's no clearly defined cutoff date and when the transition happens it'll probably be spread out over months or years as people start to clue in that they are missing half the internet.

      Most of the technological hurdles in connectivity have been overcome, even home users can upgrade their linksys routers in 5 minutes or so to take advantage of IPv6 but for some reason ISPs are holding back and because of that businesses are holding back. Everyone is waiting for somone else to make the first move.

    3. Re:But when? by jacksonj04 · · Score: 2, Insightful

      Start with yourself. Install an IPv6 stack and start using IPv6 servers (Such as for IRC) wherever possible. The 6-to-4 routing can be dealt with on your end (Usually without you needing to change anything awkward) and through one of many open 4-to-6 bridges on the other end. Eventually your IP will notice more and more IPv6 traffic traversing their network using 6-to-4.

      Start turning businesses on internal networks and when it is realised that IPv6 is in fact far nicer, because you're not playing hell trying to set DNS servers and allocate IPs, they will demand more from their ISP.

      Longhorn has an IPv6 stack built in, find your favourite Linux distro and demand an IPv6 stack in that.

      --
      How many people can read hex if only you and dead people can read hex?
    4. Re:But when? by Undertaker43017 · · Score: 4, Insightful

      The problem is mostly social. You now have millions of people on the Internet that barely understand what it is, and while from a technical persons point of view IPv6 is "no big deal", from this groups point of view this is a "big scary", and something they wouldn't think of doing on their own. So I suspect the majority of ISP's have realized this and are not ready for the customer service nightmare that changing would cause. Sure you can upgrade your Linksys to handle IPv6, but how many people even know the device CAN be upgraded at all, let alone know how to do it...

    5. Re:But when? by puke76 · · Score: 1, Informative

      The IPv6 mess (according to D J Bernstein).

    6. Re:But when? by Scott+Wunsch · · Score: 4, Informative
      Longhorn has an IPv6 stack built in, find your favourite Linux distro and demand an IPv6 stack in that.

      What Linux distribution doesn't have an IPv6 stack built in these days?

      And for that matter, Windows users don't have to wait for Longhorn either. Windows XP has an IPv6 stack built in too: How to install IPv6

      --
      \\'
    7. Re:But when? by ysachlandil · · Score: 2, Informative

      > Most of the technological hurdles in connectivity have been overcome

      Multihoming is not fixed yet, and basically cannot be fixed within IPv6 (hierarchical address space and multihoming don't like each other). The current hack to fix this is give out addresses from all ISPs you want to connect to and have the _endpoints_ negotiate which address to use (proposal is called SHIM6, google for it). So basically, the network engineer needs root/administrator access to all endpoints in the network to do his/her work.

      Now, should I drop one of my peers (and lose my redundancy) just to use IPv6, or just keep my IPv4 addresses until the end of time?

      --Blerik

    8. Re:But when? by jrockway · · Score: 3, Interesting

      Doesn't qmail need a non-DJB patch to use IPv6? I enjoy Bernstein's writing, but in this case, he is doing a whole lot of talking and not a whole lot of acting.

      Personally, my entire home network is IPv6. If people don't want to use IPv6, that's fine with me. My ISP charges me $10/month for static IPs, but with IPv6, I got 2^64 of them for free. 2^64!!! That's 2^32 more than all the IPv4 addresses in existence.

      I think it's easy to see why people don't want IPv6. Without artificial scarcity, they can't gouge you for IP addresses.

      --
      My other car is first.
    9. Re:But when? by puke76 · · Score: 2

      I think you miss his point. You run IPv6 on your internal network. Great. But every time you talk to someone outside that network, you'll be using IPv4. Who is going to be the first one to switch to the IPv6 internet? No-one. Everyone needs to change at once. And I think that's why many say it's just not going to happen. Why don't you start using an external IPv6 address and get back to me.

    10. Re:But when? by megarich · · Score: 2, Interesting
      but for some reason ISPs are holding back and because of that businesses are holding back. Everyone is waiting for somone else to make the first move.

      I feel the ISP's have to be the ones who make the first move. A not so great example but gives an idea of how I'm viewing this is an official language of a country. Since I'm from the states I'm going to use English as my example. Most people here naturally speak english. Sure you have others here or there who knows other languages but they can't communicate by in large with the rest of the country without knowing english(thus its a GREAT benefit to know english). Now if there was a movement by a good portion of the poplulaton to move to spanish, what benefit would other people have moving to spanish if the key people(in this case the gov) still back english and will not change?

      That's how I look at the whole situation, until the key players, namely the ISP's, are willing to change to ipv6 there is no advantages of small/medium size businesses to switch over because everyone else is still talking in terms of ipv4.

    11. Re:But when? by drinkypoo · · Score: 1

      Yeah, but since there are numerous gateways 'twixt IPv6 and IPv4, it's pretty much irrelevant. The two protocols can cooperate. Granted, web servers and the like can't go to IPv6 until the clients do...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:But when? by jrockway · · Score: 2, Insightful

      My internal machines don't need to talk to anyone that uses IPv4.

      Admittedly, I do use a web proxy that fetches IPv4 websites for these machines, but I did that anyway. Having IPv6 lets me ssh to my machines without having to ssh to my firewall first. Convenient. And ready for the future.

      People can sit here and whine about how nobody's moving to IPv6, but the fact of the matter is that it's super simple to do, and once you have, you're done. If everyone does this, there will be no "great transition". It will just be done. And that's it.

      Not nearly as exciting as everyone wants it to be, is it...

      --
      My other car is first.
    13. Re:But when? by Marc2k · · Score: 1

      Better yet..how many people will be able to access their Linksys routers, given the knowledge and motivation to do so? At my friends' swank apartment, you can access at least half a dozen WLANs, all with the ID "linksys"; subsequently, all of them now have new passwords.

      --
      --- What
    14. Re:But when? by nite_warrior · · Score: 1

      Who said they can't run both protocols? you can set your servers to IPv6 and then clients running IPv6 can access the server withouth IPv6-to-IPv4 routing, and you will still be able to serve IPv4 clients, as clients keep switching to IPv6 it will be transparent to those users.

    15. Re:But when? by FireFury03 · · Score: 3, Insightful

      But every time you talk to someone outside that network, you'll be using IPv4. Who is going to be the first one to switch to the IPv6 internet? No-one. Everyone needs to change at once. And I think that's why many say it's just not going to happen. Why don't you start using an external IPv6 address and get back to me.

      I'm afraid you're talking crap - I use IPv6 on my internal network *and* over the Internet, it coexists quite happilly with IPv4. Enabling IPv6 support on a system does _not_ require leaving the IPv4 network. If you have both protocols enabled then IPv6 will be preferred when it is available on both ends (since the DNS lookup you make to find the remote server's address will return both A and AAAA records) but if one end doesn't do IPv6 then the IPv4 address will be used.

      The problem here is an economic one, not a technological one:
      1. Why should the content provider invest in rolling out IPv6 addresses to their servers (there is an administration cost in running an additional protocol) when 100% of their clients have IPv4 addresses (the number with IPv6 addresses is not important here if it is significantly less than 100%)
      2. Why should the ISPs invest in rolling out IPv6 networks if 100% of the content on the internet is accessible over IPv4?
      3. Why should the consumer grade DSL router manufacturers bother to include native IPv6 support in their hardware if the ISPs aren't going to support it?

      Most of the end-users neither know nor care about IPv6, but if the ISPs provided native IPv6 connectivity, the customers' DSL routers provided IPv6 support and their OSes shipped with IPv6 enabled by default (Fedora Core does this, as does OSX... sadly XP doesn't) then the customer wouldn't need to care about it because it would just automagically work - IPv6 does autoconfiguration our of the box.

      So whilest there are economic reasons why businesses won't be inclined to change without everyone else changing, there is no technical reason why anyone can't support IPv6 without everyone else changing.

    16. Re:But when? by hopeless+case · · Score: 2

      Thanks for posting DJB's piece, it was an interesting read.

      I don't see why everyone needs to change (if by that you mean 'get connected to the IPv6 network without losing your connection to the IPv4 network') at once, however. As long as useful services are provided over the IPv6 network that can't be provided over the IPv4 network, people will start changing over. As long as connecting to the IPv6 network doesn't mean you loose the ability to talk over the IPv4 network, and it doesn't, there is no penalty for connecting to IPv6 (except for the initial hassle of upgrading).

      Seeing as how Windows XP and Linux both currently ship with mature IPv6 implementations, connecting to the IPv6 network is largely a matter of setting up a 6 on 4 tunnel to a tunnel broker. In other words, a configuration exercise, not an upgrade exercise.

      Why should anyone do that, you ask? To access a new service that requires it. Plenty of people who are not computer savvy and who wanted to get VOIP service from Vonage stuck a VOIP router in their home network and the router configured itself.

      All that is needed to get us closer to the magic moment are compelling applications. Suppose, for example, that people start doing home security monitoring by using IPv6 addressed window and door sensors. To subscribe to such a service they send you a router that you stick in your home LAN, right next to your vonage VOIP router if you have one, and the router automatically connects to a tunnel broker and sets up a 6 on 4 tunnel to connect your sensors to the IPv6 network.

      As more and more people start using such services, the traffic traversing the IPv6 network starts growing. Initially this traffic will mostly tunnel through the IPv4 network but as it grows, ISPs will have a reason to offer direct IPv6 service (to lower the bandwidth required to carry all the 6 on 4 headers to just that required to carry the 6 headers by themselves).

      I think the IPv6 community did a great job in thinking through the of transition scenarios and providing all sorts of tunneling mechanisms to allow IPv4 and IPv6 to exist side by side.

      I am not sure why DJB thinks those transition mechanisms are not enough.

    17. Re:But when? by paranode · · Score: 1

      I think the push is going to come from Asia mostly because they got the short end of the stick on IPv4 allocation. The US has a history of leading (or at least being one of the leaders) of this type of infrastructure planning and change, and as long as US companies/orgs have most of the IPs and things are running smoothly, there is little motivation for them to change at all.

    18. Re:But when? by Bob_Robertson · · Score: 1

      I agree, my ISP refused to even talk about it. All they said was, "Maybe you should look into a business account." Luckly, http://tunnelbroker.net/ from Hurricane Electric is available for you to turn up IPv6 yourself today.

      The last time I was working on peerings at the MAEs, IPv6 was not being handled natively, has that changed?

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    19. Re:But when? by Cramer · · Score: 1

      Y2K was a real problem with a real deadline. IPv4 isn't either of these. We still have quite a bit of IPv4 space available and aren't going to "run out" for decades. (people have been screaming "10-20 years" for decades now.) When the last block(s) have been sent to RIRs for assignment, then it will be a problem.

      Honestly, it's not very difficult to switch to IPv6 on devices that currently support it. When it comes to it, IPv6 could be pushed across the internet over a few years with most transitioning in the first few months. The only real problem is the devices that don't currently support IPv6 because either there's no (official) software updates to bring them IPv6, or there's no one left to bring them IPv6 support -- how many IPv4 devices do companies use today that no longer have support from the manufacturer or no longer have a manufacturer? (IPv6 is not a sufficient reason to throw away millions in hardware.)

      Yes, you can load unsupported/hacked firmware on some Linksys gear if you know where to find it. The point is, it didn't come from linksys. And the hardware isn't coming IPv6 capable from factory.

    20. Re:But when? by Cramer · · Score: 1

      Not really... they just came late to the party and now there's no bean dip.

      It's easier for emerging markets to be IPv6 since they're starting out, day-one, with IPv6 capable hardware. When you go to buy a computer today, do you get a 486 running win95 or a P4 running XP? The 486 will certainly be cheaper, but the P4 has longer usable lifetime.

    21. Re:But when? by Omnifarious · · Score: 2, Informative

      I already do that, but my ISP still won't switch. :-(

    22. Re:But when? by marcosdumay · · Score: 1

      And how do I get a IPv6 subnet to deal with if my ISP is not cooperating?

    23. Re:But when? by Sithgunner · · Score: 1

      Let alone know or bother what we are talking about in here...

    24. Re:But when? by jacksonj04 · · Score: 1

      Thanks for the link, I was going to put a bit saying exactly the same in mine then forgot about it entirely.

      There is also a beta IPv6 deployment pack for the Windows 2000 platform, but Microsoft seem to have removed it from the obvious places. If I find it, I'll let you know.

      --
      How many people can read hex if only you and dead people can read hex?
    25. Re:But when? by msmercenary · · Score: 1

      The difference between Vista and XP is that Vista defaults to IPv6-enabled. In an out-of-box installation of Vista, all IPv4 traffic goes through the tunneling protocol, as the grandparent suggests.

    26. Re:But when? by Anonymous Coward · · Score: 1, Insightful

      People can sit here and whine about how nobody's moving to IPv6, but the fact of the matter is that it's super simple to do, and once you have, you're done. If everyone does this, there will be no "great transition". It will just be done. And that's it.

      It's funny how people completely miss DJB's point.. great, you've set up some random network protocol inside your house or whatever. Congratulations, you had a little extra free time one day, and you had a little fun.

      What you run at home just doesn't matter. The fact is, you are still using IPv4 (otherwise, how could you post on slashdot?). Using IPv6 alongside IPv4 doesn't mean anything. You can use fidonet tunneled over IPv4, who cares?

      I've said it before, and I'll say it again: IPv6 doesn't "happen" until a majority of *users* and a majority of *sites* are using IPv6 *ONLY*. In other words, the majority of their traffic is IPv6 from end to end without any IPv4 in between. Until then, IPv4 still works, and people will use what already works. What company is going to cut themselves off from IPv4? What internet user is going to cut themselves off from IPv4? You yourself haven't done it!

      What DJB is saying is, what will change this situation? What will make people disconnect from the IPv4 internet? I can't really think of anything. Maybe, government mandate combined with blocking IPv4 at every device? Why would the government do that?

      Just remember this simple concept: to consider yourself "on IPv6" you must be completely disconnected from IPv4. If you analyze the situation from that point of view, you'll come to agree with Dr. Bernstein and the rest of us who tell our clients "IPv6 will never happen, don't worry about it".

    27. Re:But when? by nzkbuk · · Score: 1

      Most of the probelm is that core routers cost quite a bit of money. It's not the sort of things that many ISP's want to throw away too quickly and not all routers can have firmware upgrades even when there is a support contract.

      Well all know that businesses will only spend money when they are forced to. So which do you think is more likely, The CEO of a small ISP will get a new sports car or they will get a new Cisco 7K maybe 10K series router. The sports car is probably the cheaper option

    28. Re:But when? by NutscrapeSucks · · Score: 1

      To reiterate the AC, you sound a lot like a Novell network admin in the mid 90s. "You can encapsulate IPv4 inside of IPX", "You can use a webproxy to fetch IPv4 sites to IPX machines.", "I can access resources directly with IPX without routing" etc etc.

      OK, so IPX wasn't the Way Forward(tm), but the point is that almost everyone wants to run a single protocol on both the inside and the outside -- and right now that protocol is IPv4. DJB's point is that that protocol is never going to be something other than IPv4 until the new thing is totally universal.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    29. Re:But when? by joeljkp · · Score: 1

      How do I do that? Is there a simple HOWTO?

      --
      WeRelate.org - wiki-based genealogy
    30. Re:But when? by joeljkp · · Score: 1

      Well, mine's called 'linksys', but it's got WPA turned on. I just couldn't think of a better name.

      --
      WeRelate.org - wiki-based genealogy
    31. Re:But when? by joeljkp · · Score: 1

      Well, how much space is left, and what's the current growth rate? Is it asymptotic (never reaching the limit because people keep implementing local workaraounds)?

      --
      WeRelate.org - wiki-based genealogy
    32. Re:But when? by jrockway · · Score: 1

      > to consider yourself "on IPv6" you must be completely disconnected from IPv4

      Wrong. To be "on IPv6", you just need to ... be on IPv6. Eventually everyone will have converted to IPv6 because they need more addresses than they can afford with IPv4. As a result, at some point IPv4 will become irrelevant.

      --
      My other car is first.
    33. Re:But when? by jacksonj04 · · Score: 1

      http://www.microsoft.com/ipv6 for any Windows based network. No idea for Linux, you may have to check with your individual distro.

      --
      How many people can read hex if only you and dead people can read hex?
    34. Re:But when? by Anonymous Coward · · Score: 0

      That's easy....

      People often don't understand that switching is a _big_ investment for ISPs (much more that the average "expert that has done it allready" can imagine, it's much broader than the technical effort, which is allready much bigger than the average slashdotter will understand).

      It'll take a while for ISPs to convert, they need to be able to make money out of that investment while their current investments are still paying off.....

  5. Welcome Overlords by j_kenpo · · Score: 4, Funny

    "There are things. Billions and billions of devices that will service these people"

    I for one welcome our new.... thingy overlords...

    1. Re:Welcome Overlords by Doctor+Memory · · Score: 2, Funny

      Not sure I want to be "serviced" by a device....

      --
      Just junk food for thought...
    2. Re:Welcome Overlords by Anonymous Coward · · Score: 1, Funny

      Seems to satisfy millions of women...

  6. untrue by Anonymous Coward · · Score: 5, Funny

    So it is a false perception that we have full Internet penetration.

    This is completely untrue! There is lots of full penetration on the internet.

  7. "Billions and billions" by FirienFirien · · Score: 4, Insightful

    On the comment "Billions and billions of devices that will serve these people", it seems to be unmentioned that (random estimate, not researched in any way) half of them will not be directly hooked into the interweb. Many of those are intended to be that way, since you want your layers of security, and that's why we have however many thousands of addresses in the range 10.0.0.[0-256]; technically they're using the same IP, but it doesn't matter because that IP is kept internally, and not in contact with the web.

    IPv4 does not have enough numbers to give every single device its own unique IP. On the flip side... if we were locked into the system, it would still be workable.

    --
    Browsing with +2 to insightful posts and a higher threshold makes the average post seen seem a lot more ingenious
    1. Re:"Billions and billions" by OakDragon · · Score: 2, Funny
      It always amuses me that people use the total population of the earth to explain why we need X number of whatever. Do the billion or so babies need an IP address? What about the billion+ sustenance farmers?

      OTH, there is a fair point that it's not about people, it's about devices..

    2. Re:"Billions and billions" by mindstrm · · Score: 2, Interesting

      Private addresses + NAT is not a security measure, although it looks like one.
      The same issues can be addressed without the need for NAT and private addressing.

      The main reason private addressing is used is because getting public address space is a hassle... whether people realize it or not.
      Just imagine.. if you could just have a million public IP addresses that worked, why wouldn't you use them?

    3. Re:"Billions and billions" by Anonymous Coward · · Score: 1, Insightful

      and that's why we have however many thousands of addresses in the range 10.0.0.[0-256]

      For a home network thats fine, but in the business world, it's got serious limitations. Sure, we could number all of our office computers in the 10.x.y.z network, but what do we do when we merge with another company, start over from scratch and renumber everything (sure, its easy with DHCP, a script to update all 2000 machines' addresses in the DHCP server, another script to update all the firewalls with the appropriate machines ip addresses, another script to update the network backup configuration, another script to....)? What if we just need to establish a VPN connection with another company? These are excessively complex things to deal with, when everyone could have had unique addresses and a decent firewall from the start.

    4. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      'Interweb' is only funny when you actually know the difference between the Internet and WWW ("that IP is kept internally, and not in contact with the web").

    5. Re:"Billions and billions" by TCM · · Score: 2, Informative

      half of them will not be directly hooked into the interweb. Many of those are intended to be that way, since you want your layers of security, and that's why we have however many thousands of addresses in the range 10.0.0.[0-256];

      Repeat after me for the 34253456345324th time: NAT is not a security measure. NAT is not a security measure. NAT is not..

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    6. Re:"Billions and billions" by Anonymous Coward · · Score: 3, Informative

      however many thousands of addresses in the range 10.0.0.[0-256]

      Sorry, but I have to completely discount technical analysis and discussion from anyone who writes 2^24 as "however many thousands" when discussing a technical subject in a technical forum. Nothing personal, mind you, but it demonstrates either (a) a lack of basic math skills which are essential, even reflexive, to anyone really knowledgeable in this space or (b) a lack of attention to detail. In either case, your analysis is of much less value given that there are people around who actually do understand the topic.

    7. Re:"Billions and billions" by Thomas+Charron · · Score: 2, Insightful

      NAT is a *layer* of security, but not security itself.

      Ok, NAT itself isn't. HOWEVER. MOST people relate NAT with a firewall performing NAT. Which is a level of security.

      Nitpicking that a NAT machine is not a security measure fails to take into consideration that most people, NAT assumes some sort of firewalling taking place between the networks.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    8. Re:"Billions and billions" by Anonymous Coward · · Score: 1, Insightful

      Just imagine.. if you could just have a million public IP addresses that worked, why wouldn't you use them?

      * You want all your workstations to go through a proxy to get outside the network for filtering/monitoring reasons.

      * You don't want your staff to have direct external access and don't want to have to limit this with firewall rules (i.e. you want it done by the nature of the network not by the configuration of the network devices).

      * You don't want any incoming connections.

      * You don't want the possibility of some junior tech bodging the firewall and opening your network wide open by removing filtering.

      * You don't want some senior tech bodging the firewall on a Friday afternoon after pub lunch and accidently opening your network up.

      There are quite a few reasons and quite a few situations where you wouldn't want this. Most corporate networks for a start.

    9. Re:"Billions and billions" by Anakron · · Score: 1

      There was nothing wrong with his use of the phrase "however many thousands". And where the hell did you get 2^24 from? 10.0.0.[0-255] is 256 addresses, 2^8. Count them.
      "However many thousands" is a reference to the "thousands" of private nets that use those addresses. Before criticizing someone else, you might want to actually pay attention to what was said. Get off your high horse.

      --
      There are 11 types of people. Those who understand binary, those who don't and those who are sick of this lame joke.
    10. Re:"Billions and billions" by TCM · · Score: 1

      NAT is a *layer* of security, but not security itself.

      It's not even a layer. It is nothing security-related. Security comes from the packet filter and the packet filter alone.

      Without a filter, your NAT box happily routes traffic destined for the inner network - think rogue ISP or spoofed packets claiming to come from the inside. All that NAT does is rewrite addresses in packets. It doesn't block anything.

      Of course, actually getting a packet destined for your inner network to your NAT box is not something any random user on the Internet could do. But "in 99% of cases it's not applicable anyway so it's secure" isn't security actually.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    11. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      10.0.0.0/8 is 16,777,216 addresses;
      172.16.0.0/12 is 1,048,576 addresses;
      192.168.0.0/16 is 65,536 addresses;

      Even a medium sized business can use 192.168.0.0/16, only a large organization needs to use one of the larger blocks of private addresses.

      Office workstations shouldn't be running servers, only clients; and they really don't need a routable address. Their IP addresses should be assigned dynamically anyway. Only servers and routers need to have static addresses (and the server addresses can still be configured with DHCP), this reduces the workload a lot.

      Backups? For office machines this should be a document management issue (i.e., save a copy on a server, via a document management system), for servers it doesn't make a difference if their static address is routable or private. The big trick, which you want to do anyway, is to have tools to integrate (name,address) and (name,address,MAC) sets in DHCP and DNS.

      Only servers and routers facing the Internet really need routable addresses, and VPNs are proxy bridges between them.

      And if two companys merge, isn't most of the work integrating the mail systems? Why would they need to consolidate physically disjoint networks?

    12. Re:"Billions and billions" by Cramer · · Score: 1

      ...NAT is not a security measure...

      Incorrect. NAT is a security measure. It is not the security measure. NAT will help protect a network, but it offers no protection for exported service(s) or outbound traffic. ("Packets show up; I rewrite the headers and send them on." -- NAT)

      if you could just have a million public IP addresses that worked, why wouldn't you use them?

      This is the exact mentality that has several dozen /8's hoarded away. In the early days of the internet, address space was abundant and thus large swaths were given away, rapidly consuming the landscape. Now we're poised to create a new landscape and we're doing the same damned stupid thing.

    13. Re:"Billions and billions" by zootm · · Score: 1

      You appear to have restated the point of the post you were replying to?

    14. Re:"Billions and billions" by DickBreath · · Score: 1
      Just because you can give every single device its own external IPv6 does not mean that you must give up any of the things you mentioned.
      • You still have complete control of your traffic at the border.
      • You can still require all web surfing to go through a proxy.
      • You can still prevent incomming connections.


      As to your second point about "the nature of the network", I take your point. Just because you can give every device its own public IPv6 does not mean that you must. There could still be a new v6 style of NAT that works much like we are familiar with.

      The new "translation" in NAT (as an implementation detail) could simply "rewrite" all addresses to the same address between the internal and external nets. Or not -- by using private non-routable addresses.

      Someone else already addressed that human error will always exist.
      --

      I'll see your senator, and I'll raise you two judges.
    15. Re:"Billions and billions" by jrockway · · Score: 1

      > Now we're poised to create a new landscape and we're doing the same damned stupid thing.

      For every IPv4 address, there are 2^96 IPv6 addresses. So if, right now, everyone has enough addresses, they will suddenly have 2^96 more. 2^96 is 79228162514264337593543950336! (I got 2^64 for free recently... but considering I have 3 static IPv4 addresses, I should have gotten around 2^97 IPv6 addresses. I'll survive, somehow, with 2^64 of 'em.)

      2^128 (340282366920938463463374607431768211456) IPs really ought to be enough for everybody.

      --
      My other car is first.
    16. Re:"Billions and billions" by Jerrry · · Score: 1

      Agreed. This is yet another case of something (NAT) that people have gotten so used to that they no longer see it as the monumental hack it really is.

      I, for one, will leave NAT for dead as soon as IPv6 becomes viable. Good riddance.

    17. Re:"Billions and billions" by Jerrry · · Score: 1
      OTH, there is a fair point that it's not about people, it's about devices..

      That's the point. In my house there are three people and 14 devices that have IP addresses. That's almost a 5:1 ratio.

    18. Re:"Billions and billions" by alva_edison · · Score: 1

      Yes, but there is the flip side that 10.x.y.z is the reserved class A network and actually does have 2^24 addresses for internal use. The fact that he only mentioned 10.0.0.[0-256] does make your point valid, but he should have been talking about 10.[0-256].[0-256].[0-256].

      --
      He effected a bored affect.
    19. Re:"Billions and billions" by drinkypoo · · Score: 1

      It doesn't matter if NAT is not a security measure; if you use NAT, your IP address is not routable and many attacks will not work. Given that in nearly all NAT implementations ports are not forwarded unless requested, it makes the system unreachable except for those ports. How could that not enhance security? Unless you're already doing filtering on the host? Personally, I do both, but it's probably overkill unless someone owns my border device.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:"Billions and billions" by alva_edison · · Score: 1

      That should have been [0-255] all of those times, missed that the first time I looked through the post

      --
      He effected a bored affect.
    21. Re:"Billions and billions" by TCM · · Score: 1

      Someone cracks a router at your ISP (not too improbable considering certain Cisco fiascos, right?) and sets up a route to your network. Now what? You NAT box suddenly makes your internal network "public" to the attacker.

      NAT is not security. At the very least you're trusting your ISP to never get owned or be malicious. If you can live with that, fine. Just don't tout it as security please.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    22. Re:"Billions and billions" by Anonymous Coward · · Score: 0
      You know as well as I do that, for example, a 10.* network connected to the internet through a NAT box (without any firewall) is more secure than the same network with public IP addresses connected directly to the internet through a regular router.

      Please stop your tiresome trolling.

    23. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      Sure it is...security through obscurity

    24. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      But 10.0.0.[0-256] is not necessarily a "Class A" network. (That would be 10.0.0.0/8.) His use of [0-256] would suggest otherwise, in fact, and it really should be [0-255], anyway.

      You're making an assumption. He could easily have been referring to 10.0.0.0/24. (A "Class C" in the really, really out-of-date terminology.)

    25. Re:"Billions and billions" by drinkypoo · · Score: 2, Interesting
      WTF? My ISP is not doing NAT. I have a different routable address dynamically assigned every time I connect. I am doing NAT, thus I am trusting that I will not be owned. My border gateway (linux box) does not accept packets for non-routable networks on the external interface; nor does it accept packets for services I am not running.

      You may well have an argument, but I can't tell from the above comment.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    26. Re:"Billions and billions" by Anonymous Coward · · Score: 1

      So let me get this strait. Because a someone can crack a router and make my IP routable it's not a security measure? Because someone can crack a computer and take down a firewall, it's not a security measure either?

      Everything that can block a malicous attack is a layer of security, no matter if it was intended that way, or even good at it. Unplugging the ethernet cable is a layer of security. Turning the computer off is a layer of security.

    27. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      There was nothing wrong with his use of the phrase "however many thousands".

      I beg to differ.

      And where the hell did you get 2^24 from? 10.0.0.[0-255] is 256 addresses, 2^8. Count them.

      If he was really intending to refer to a class C, then why did he say "thousands" of addresses? As you say, 2^8 is not thousands. The IPv4 private address space actually includes the whole 10.x.x.x class A range, which would make "thousands" slightly more sensible -- though "millions" would be a far better approximation.

      "However many thousands" is a reference to the "thousands" of private nets that use those addresses.

      Was it, now? Let's look at the quote:

      and that's why we have however many thousands of addresses in the range 10.0.0.[0-256]

      So you're saying that he meant to say "networks", not "addresses". Okay, not sure how you make that leap, but if you rewrite any sentence enough you can eventually construct something that makes sense.

      Before criticizing someone else, you might want to actually pay attention to what was said.

      That statement doesn't make sense in the current context. Here, I shall take a page from your book and rewrite it. What you meant to say was: "Before criticizing someone else, you might want to actually pay attention to what might have been said if the poster had a clue."

      Is that better?

    28. Re:"Billions and billions" by TCM · · Score: 1

      I didn't say your ISP does NAT. I really meant the common-almost-everywhere scenario:

      ISP ---- [public address] your router with NAT [RFC1918 net]

      You said "My border gateway (linux box) does not accept packets for non-routable networks on the external interface". That's a property of the packet filter, not the NAT mechanism. If you had only NAT and no filter, someone at the ISP could setup a route for [RFC1918 net] via [public address] as a gateway and your router would route it. That's what I was saying, NAT without a filter isn't security.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    29. Re:"Billions and billions" by just_another_sean · · Score: 2, Funny

      Please tell me for the 34253456345324th time... Why? (link is fine, I like to read.)

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    30. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      Nitpicking that watching football doesn't get you drunk fails to take into consideration that most people drink beer when they watch football.

      That fact that many appliances do both NAT and packet filtering doesn't weaken the original argument at all. NAT isn't and doesn't even resemble a security measure.

    31. Re:"Billions and billions" by fnj · · Score: 2, Insightful

      Repeat after me for the 34253456345324th time: NAT is not a security measure. NAT is not a security measure. NAT is not..

      You can repeat some mindless drivel endlessly, but that does not make it so. All the small users like me who have Netgear or Linksys NAT routers have thereby a very significant measure of security. With the default setup with no port forwarding, no WAN packet containing ANY destination address in the header is going to get routed to the LAN side except as part of a connection established FROM THE LAN SIDE, except by stumbling into an established translation state sequence, which is exceedingly unlikely.

      Cool it with the misdirection. It is POSSIBLE to use NAT and still permit inbound routing, but only a statistically insignificant proportion of NAT users would do so.

    32. Re:"Billions and billions" by drinkypoo · · Score: 1

      Security is not the purpose of NAT but it does provide an added layer. That's all anybody is saying here. Not filtering, of course, would be stupid.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    33. Re:"Billions and billions" by TCM · · Score: 1

      Quick google for "nat is not security" came up with: http://safecomputing.umich.edu/tools/download/nat_ security.pdf

      "Conclusion:

      The well-known security adage "security through obscurity is no security at all" is certainly applicable to NAT. IPv6, whose biggest initial win is a significant increase of address space, has no concept of NAT since no additional security is gained."

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    34. Re:"Billions and billions" by Thomas+Charron · · Score: 1

      Corrent, it ISN'T secure. But it adds a layer. Layers are good. Think smoke screen. Sure, you can walk around in it. But it's not crystal clear untill you bump into things. It won't stop aimed bullets, but it helps with making it harder to aim.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    35. Re:"Billions and billions" by smithmc · · Score: 1

        Someone cracks a router at your ISP (not too improbable considering certain Cisco fiascos, right?) and sets up a route to your network. Now what? You NAT box suddenly makes your internal network "public" to the attacker.

      How does a compromised router at my ISP make the NATed IP addresses on my home network available to the attacker? My machines' addresses are still 192.168.0.x; only my NAT/router has an address on my ISP's subnet. How does that attacker get to me without also cracking my router?

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    36. Re:"Billions and billions" by TCM · · Score: 1

      Read my post further down from the one you replied to.

      someone at the ISP could setup a route for [RFC1918 net] via [public address] as a gateway and your router would route it.

      There. To prevent that, you need a filter. NAT alone provides no security. Must have been the 45634576745764576th time now I said that.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    37. Re:"Billions and billions" by Ryan+Amos · · Score: 1

      Nitpick much? NAT is a process involving a packet filter (you've gotta check those connection states to see who to send the packet to, incoming connections must be checked against a port forwarding list.) Saying "NAT is not a security measure, the packet filter is" is like saying "An alarm system is not a security measure, but the door sensor is." Packet filtering is one of the things that makes effective NAT possible.

      Yes, you can do NAT without packet filtering, but not the kind of NAT that allows you to map one IP -> many devices, which is what we're talking about here. The simple fact that the machines behind NAT are not addressable to the large part of the internet provides some level of security.

    38. Re:"Billions and billions" by keithmoore · · Score: 2, Insightful

      All the small users like me who have Netgear or Linksys NAT routers have thereby a very significant measure of security.

      Not clear. There are so many ways to compromise a Windows box that NAT is pretty much irrelevant. If you're not running Windows then the potential threats are greatly reduced anyway. And there are ongoing efforts to define ways by which apps can ask the NAT to forward traffic to them without explicit configuration.

      Marketers love to promote the delusion that they can sell you a magic box that will provide security without harming your ability to run apps. Whether or not the box implements NAT, it's a delusion just the same.

    39. Re:"Billions and billions" by Ryan+Amos · · Score: 1

      It's also slashdot. Nobody puts more than half a second worth of thought into anything posted here, so why pick on this guy?

    40. Re:"Billions and billions" by volkris · · Score: 2, Informative

      It's clearly NOT the NAT that's providing you security here, but simple matters of routing.

      So as the parent post said, NAT is not security. Routing and firewalling can provide some security, but not the NAT itself.

    41. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      I think you guys are all idiots. Way to argue a point to death...

    42. Re:"Billions and billions" by Omnifarious · · Score: 1

      NAT is a stupid security mesasure, and IPv6 is just as good because IPv6 addresses are practically unguessable. Anybody who tries will be noticed by practically any ISP because it will take them an average of 2**32 packets to do it.

      Yes, it's possible for someone to get an IPv6 address from a P2P system or something similar. But that can be solved by having the address change randomly from day to day. Also, IPv6 installations are going to require a router to work right anyway, so just make the router not pass inbound connection requests unless specifically configured to do so. Poof, security as good as a NAT, but still possible for someone who wants to to bypass without much effort.

      Bypassing NAT requires oodles of effort in comparison.

    43. Re:"Billions and billions" by Cramer · · Score: 1

      ...what do we do when we merge with another company...

      This comes up everytime IPv6 is mentioned. And it's wrong. NAT is not the center of the difficulty in merge/connecting two large networks. The size of the network(s) and the breadth of interconnectedness are the real problems. And there's a lot more to merging networks than making sure there aren't address overlaps. Building a NAT-NAT map to address overlaps can be headache generating, but it's certainly not "excessively complex". [I've done it dozens of times.]

      Granted, not having to build any NAT maps at all is a lot simpler. *grin*

    44. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      right, well, since when can you NAT withount routing?

      you said it yourself, routing provides security. NAT must use routing, thus NAT provides some security.

      It's a locked door. Granted most internet crime is done by con men, but NAT provides security from B&E, which is scarier. You can outsmart a conman, you can do nothing about the burglar that opens your unlocked door when you aren't home.

    45. Re:"Billions and billions" by Thomas+Charron · · Score: 1

      ...

      That was an idiotic comparison. It is NOT true that 99% of the time, people watching football get shitfaced.

      It *IS* true that 99% of NAT machines are filtering packets and serving as a firewall, rejecting nearly all incoming connections unless perviously configured otherwise.

      Guess what? Stop signs don't stop a car either. Oh, and brake pedals? Worthless, they don't stop the car either.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    46. Re:"Billions and billions" by umeboshi · · Score: 1

      I agree, people seem to have forgotten that IP is supposed to be logically peer to peer, and how this has been constrained by NAT. I still believe in the average host on the internet running a http server containing at least a simple whoami page.

    47. Re:"Billions and billions" by Sharkeys-Day · · Score: 1

      Oh, and brake pedals? Worthless, they don't stop the car either.

      Heh, heh. I would like to see you stop the car without the brake pedals.

      "Where's a brick wall when you need one?!"

    48. Re:"Billions and billions" by Thomas+Charron · · Score: 1

      And I'd love to see a pure NAT device that NAT's absoutely ever single incoming and outgoing packet. ;-)

      That's not a NAT, that's called a router.. *snickers*

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    49. Re:"Billions and billions" by skaeight · · Score: 1

      Nobody will ever need more than 640k.

    50. Re:"Billions and billions" by andy_t_roo · · Score: 1

      encasing the computer in concrete and dropping it in the ocean is a layer of security, and even with all of the above, it might still be vulnerable if it has windows on it . . .

    51. Re:"Billions and billions" by misleb · · Score: 1
      It's clearly NOT the NAT that's providing you security here, but simple matters of routing.

      Simple matters such as... NAT and its consequences?

      So as the parent post said, NAT is not security. Routing and firewalling can provide some security, but not the NAT itself.

      Hogwash. NAT implies routing. There are two ways in which one can implement security on a router. Translate (NAT) packets such that no external hosts can initiate connections to hosts behind the router. Or actively block access to hosts using access control lists (firewall). Obviously these two methods can be combined, but suffice it to say that NAT can very well provide security itself. You can quibble over how GOOD the security is, but you can't argue that it isn't security.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    52. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      He meant 10.0.0.0/8 (10.0.0.0-10.255.255.255) or 10^(32-8) = 10^24 addresses.

    53. Re:"Billions and billions" by jrockway · · Score: 1

      When talking about numbers like 640, it's easy for it to be too small.

      When talking about numbers like 340282366920938463463374607431768211456, it's a little easier to be sure that there's enough.

      --
      My other car is first.
    54. Re:"Billions and billions" by ZenShadow · · Score: 1

      I can show you such a device.

      There's no rule that says you can't 1:1 NAT everything on your network so that it's accessible from IP's on a different netblock...

      Sadly, there are probably networks out there that are configured that way, too :-)

      --S

      --
      -- sigs cause cancer.
    55. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      "With the default setup with no port forwarding, no WAN packet containing ANY destination address in the header is going to get routed to the LAN side except as part of a connection established FROM THE LAN SIDE, except by stumbling into an established translation state sequence, which is exceedingly unlikely."

      And you can't do this with a firewall that only allows connections initiated by computers on your home network why? Seriously, it's easier to write a piece of software the doesn't allow inbound connection attempts (you *DO* know how TCP handshaking works don't you?) than it is to write software the correctly translates addresses and ports.

    56. Re:"Billions and billions" by Korgan · · Score: 1

      Depends on what pressure the glass in the windows has been tested to and which ocean you drop it in ;-)

    57. Re:"Billions and billions" by Anonymous Coward · · Score: 0

      Although I agree with you, I must say that the numbers to compare are actually 5242880 bits (not 640 KB) and 340282366920938463463374607431768211456 addresses (not 128 bits).

    58. Re:"Billions and billions" by jrockway · · Score: 1

      Although I agree with you, I must say that the numbers to compare are actually 5242880 bits (not 640 KB) and 340282366920938463463374607431768211456 addresses (not 128 bits).


      It's kind of hard to compare here... it's apples to oranges. A single IP address is more useful than a single bit of memory. 2^128-1 is the largest number you can store in 16 bytes of memory. Obviously 640K of memory could store a whole lot more IP addresses... but that's not what it's for. It's there to store data, and 640K is maybe one or two programs worth. Not enough.

      So really, the usefulness of "640,000 bytes of memory" is somewhere near "640" on my scale, whereas being able to address 2^128 unique computers on the Internet is somewhere near "340282366920938463463374607431768211456" on my usefulness scale. Obviously I could be full of it, though ;)

      All pedantry aside, my point is 640K isn't enough for everyone, but 340282366920938463463374607431768211456 IPs probably is.

      Who knows -- maybe the next generation's running joke will be "Haha, jrockway said that 340282366920938463463374607431768211456 is enough for everyone. lol." I doubt it though.
      --
      My other car is first.
    59. Re:"Billions and billions" by Thomas+Charron · · Score: 1

      Any network that required such a device..

      Is one crack asses configured network.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
  8. Re:service? by madaxe42 · · Score: 2, Funny

    Like this : here

  9. What About Private Address Space? by Anonymous Coward · · Score: 2, Insightful

    It seems that when discussing "the sky is falling" ipv4 schemes, no one ever takes into account private networks. In most cases, especially in the Western world, all devices are not directly connected to the internet. Private address space, when used according to specification, will eliminate the need for costly conversions to a new standard.

    IPv6, in some ways, is not a good thing, and my vote is to continue using the current addressing system, albeit in a more conservative manner.

    1. Re:What About Private Address Space? by WindBourne · · Score: 3, Insightful

      With IPv6, you still have private address space, if you want, so your reasoning for staying is faulty. The problem is that there is no ip space as more ppl want ip's than are available. Quite honestly, we need to move to IPv6.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    2. Re:What About Private Address Space? by kotj.mf · · Score: 5, Insightful
      Private address space, when used according to specification, will eliminate the need for costly conversions to a new standard.

      Actually, it'll eliminate the need for costly conversions to a new standard for a period of time, after which we'll all need to upgrade anyway, when it'll be even more costly.

      Ladid's main point seems to be that NAT-proponents take this kind of short-term, client/server-centric view. There's nothing wrong with client/server, but it's a significant hinderance for independent development of things like VoIP, where peer-to-peer makes far more sense.

      Basically, it's not just that we're running out of address space; it's also that treating NAT like anything other than a (relatively) short-term fix ultimately hinders the development of new uses for the internets.

      --
      hang brain.
    3. Re:What About Private Address Space? by bigtrike · · Score: 2, Insightful

      Connecting those devices indirectly to the internet requires NAT or some other kludge. While it works to a degree, it has a lot of shortcomings and is not a viable long term solution.

    4. Re:What About Private Address Space? by MindStalker · · Score: 1

      Its funny how preception changes with risk. A few years ago everyone was screaming that we needed IPv6 even though NAT had been invented. Now we are finally realizing the security advantages of NAT and are starting to accept that we don't all NEED a publically addressable space.

      At one time we wanted to be able to connect directly to our fridge from work, now we are happy and prefer to connect directly to our home server which will route request to our fridge based upon security clearances.. Because seriously do you expect GE to build an internet connected fridge that takes all security precautions and never gets hacked into. Much like the multi-layers of an OS local networks need layers of access starting with a secure router that can handle security instead of expecting each device to be secure on its own.

    5. Re:What About Private Address Space? by TheRaven64 · · Score: 3, Informative
      Rubbish. NAT is not a security measure. If you have port {whatever this week's virus uses} forwarded, you are just as vulnerable as if you don't use NAT. Similarly, if you have a public IP and a firewall between you and the Internet which doesn't allow anything through on that port, you are secure.

      A public IP with everything other the VoIP and (for example) BitTorrent blocked is much more useful, and no less secure than NAT.

      --
      I am TheRaven on Soylent News
    6. Re:What About Private Address Space? by Thomas+Charron · · Score: 1

      Generally, a NAT/Firewall box is must more specific to it's task, and tends to have less security issues then a more generalized operating system.

      Locking down a network box, from a code perspective, is easier then locking down, say, Windows XP, or, yes, even a Linux desktop.

      Adding a layer does indeed add more security. That little box in the corner doesn't have my personal data to it. To get to that, you need to break into 2 machines.

      That's assuming that port blocking is in place, however, which, in most cases, it is.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    7. Re:What About Private Address Space? by mrogers · · Score: 2, Insightful
      IPv6 won't solve the address scarcity problem, because nobody wants a public IPv6 address that isn't reachable from the IPv4 network (who wants to turn away customers?). This won't start to change until almost everyone has switched to IPv6. Therefore the non-IPv4-compatible parts of the IPv6 address space are only useful for private networks and point-to-point links, where address scarcity is not a problem.

      NAT, on the other hand, is already solving the address scarcity problem. It isn't necessary for every IP-enabled toaster to have a globally unique address - it isn't even necessary for every home computer to have a globally unique address! People who only use the internet for web and email can happily sit behind symmetric NAT without even noticing (many of them already are). People who use P2P need full-cone NAT, but assuming an average of 128 connections per user at peak times, you can fit about 500 users behind a single address even with full-cone NAT.

      IPv6 has some good features, but solving address scarcity isn't one of them.

    8. Re:What About Private Address Space? by TheRaven64 · · Score: 1

      You are missing the point. With IPv6, you would still need a router. This router would still have firewall capabilities. By default, it would still deny incoming connections on all ports. The only difference is that you wouldn't have to decide which machine on your network could use each well-known port.

      --
      I am TheRaven on Soylent News
    9. Re:What About Private Address Space? by IpalindromeI · · Score: 1
      Okay, here's your current setup:
      1. Internet traffic comes in through the ISP to your router (be it your DSL/cable modem, or a separate box behind that or whatever).
      2. The firewall rules running on your router filter out unwanted traffic.
      3. The NAT rules translate traffic to your local network.
      4. The traffic is then forwarded to the target machine.


      Here's the setup under IPv6:
      1. Internet traffic comes in through the ISP to your router (be it your DSL/cable modem, or a separate box behind that or whatever).
      2. The firewall rules running on your router filter out unwanted traffic.
      3. The traffic is then forwarded to the target machine.


      See the difference? In particular, notice that you did not all of the sudden lose your mind and stop using a firewall.

      So what is the benefit? Well, simpler router configuration for one. The other major benefit is that if you have multiple servers behind your router that want to serve similar stuff, you don't have to choose awkward ports to forward that traffic through for the different machines. And that can still be very useful for home networks that have more than one of a given internet-enabled device.
      --

      --
      Promoting critical thinking since 1994.
    10. Re:What About Private Address Space? by Luyseyal · · Score: 1
      People who use P2P need full-cone NAT, but assuming an average of 128 connections per user at peak times, you can fit about 500 users behind a single address even with full-cone NAT.

      Just don't try to set them up on 500 different VPN clients! :) That's where admins will be happier with IPv6.
      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
    11. Re:What About Private Address Space? by vertinox · · Score: 1

      Well the sky isn't falling but think of it like this...

      You are building a house. Its a very big big house and you are building a very big basement to hold your wife's shoes. Its so big that it is taking years to build the house. Before you started your wife only had 1 million shoes and you thought to yourself, "Damn women won't buy any more than 10 million shoes in 10 years!" so you have the contractor design the specs so the basement will hold 10 million shoes.

      However, after you complete the basement and start to build the frame of the house it occurs to you that you wife already has 8 million shoes and your only 1 year into building the house and she isn't slowing down.

      So you have to choices at this point... Either:

      1. Assume that she is going to have more shoes than your original basement can hold and build a bigger basement now and then build the house.
      2. Assume your original assumption was correct and complete construction on the house itself and if you are wrong then you will have to lift the entire house up and rebuild a bigger basement.

      The first option is more expensive and a pain in the immediate terms, but if you are wrong and you do run out of space then it is going to be really expensive and a big pain in the arse to lift the entire house up and redo the infrastructure underneath it. The more time that passes and the more you build on top of the basement foundation, the more problematic it will be to lift the entire house.

      So in a sense... The sooner we start rolling out IPv6 the less of a pain it will be in the future if we turn out to really need it.

      Now if will excuse me... I just broke my own rule on analogies and the internet.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    12. Re:What About Private Address Space? by TheSkyIsPurple · · Score: 1

      Following your logic, turning off auto-play for CDs on Windows wouldn't be a security measure then either, because if you manually run the autorun, then you are just as vulnerable. You work for Sony, right?

      A door isn't a security measure on my house because when I unlock it, someone can get in?

      Having a stateful firewall is not a security measure? Well, it can't be... because if you open ports on that, or setup a DMZ, then you're just as vulnerable.

      Oh, yeah... packet filters, that's right. That's the security answer. Unless, of course, you misconfigure an incoming rule for a port you want to make available to the outside world... then you're just as vulnerable.

      You say NAT isn't a security measure because if you open up a port you are just as vulnerable. That is rubbish =-)

      Repeat after me: "NAT can be a very good security measure"
      NAT by itself is not always the security solution, but NAT, as commonly implemented, is a very good measure.

    13. Re:What About Private Address Space? by Daytona955i · · Score: 1

      IPv6 has some good features, but solving address scarcity isn't one of them.

      Sure it is, you make the comment that no one wants to exclude the ipv4 community so no one will goto ipv6... Why not run both with the eventual goal of pulling the plug on ipv4 when it's outdated?

      I think we need to address the problem before it gets to be a really bad problem. NAT is nice and usefull and will continue to be useful in the ipv6 world, but ignoring the problem won't make it go away.

    14. Re:What About Private Address Space? by Breakfast+Pants · · Score: 1

      Ah but you are looking at it from a server's point of view and not the user's. You're forgetting that many people on IPv4 can't accept incoming connections today anyway because they are NATed. So they don't have the problem of "not being accessible to customers" when they are on IPv6 anyway. Their problem is they can't talk to other NATed people and if they go to IPv6 they can't talk to unNATed IPv4 people. For them they can go IPv6 and gain connectivity with everyone who is also on IPv6 and then go through a NATed pipe to IPv4. This allows them to still have their limited IPv4 connection abilities and begin freeing themselves of it with IPv6.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    15. Re:What About Private Address Space? by Thomas+Charron · · Score: 1

      Joe shmoe user at home has no idea what your talking about.

      And you know damned right well ISP's arent going to give each house 144 distinct IPs to use. How are you going to handle addressing of this? DNS? I'd love too see every machine have a distinct DNS name as well as IP. Managing it would be hell on earth for ISPs.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    16. Re:What About Private Address Space? by prockcore · · Score: 1

      If you have port {whatever this week's virus uses} forwarded, you are just as vulnerable as if you don't use NAT.

      That's a pretty big if there. I'd say the majority of NAT users don't have *any* ports forwarded.

    17. Re:What About Private Address Space? by volkris · · Score: 1

      The strawmen are out tonight!

      Joe shmoe user at home has no idea what YOU'RE talking about either. NAT? What? Routers? Well, that must be this little blue box.

      Joe there doesn't care if his stuff is working because it's using NAT or if it's working because of the IP6 address space. He WILL care, though, that his VOIP is working better when he's gotten rid of the NAT.

      And actually IP6 has many features that make it EASIER for ISPs to manage the address spaces. Fixing up routing is one of the main goals of the standard.

    18. Re:What About Private Address Space? by Bob_Robertson · · Score: 1

      As far as "need", my agreement is restricted. Had the entirety of the specification for IPv6 been the simplification of the header, including those massive address fields, I would be ecstatic. Everything else just adds complexity to the one layer which benefits the most from simplicity. Didn't ATM teach us anything?

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    19. Re:What About Private Address Space? by Bob_Robertson · · Score: 1

      Had the increased address space (and simplification of the header) been all that IPv6 did, I would embrace it whole heartedly. Oh well, second system syndrome and all that.

      I'm using IPv6 right now, happily connecting to v4 and v6 sites. It's a simple matter of intelligent use of private v4 space and "try v6 first" DNS.

      Go to http://tunnelbroker.net/ and get yourself one too. Oh, BTW, the tunnel doesn't work through NAT.

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    20. Re:What About Private Address Space? by Bob_Robertson · · Score: 1

      By Cromm, I hate VPN crap. A tool of very limited usefulness infected by buzz-word sales drones. I've seen otherwise nice servers so laden with VPNs that they could not function to 1/5 of their capacity.

      The number of people who think that VPN is some kind of tunnel is a perfect example of how hype-ridden the entire VPN concept has always been.

      Ignore VPNs, use a tunnel where a tunnel is useful, life will be easier for everyone.

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    21. Re:What About Private Address Space? by umeboshi · · Score: 1

      Ha! I got a better one. Try to setup irc clients capable of dcc transfers between two NAT's. You have to port forward a specific range of ports for each client on the lan, and have those ports configured on each irc client. Adding and removing hosts to the network can be a pain, and you can just about forget about dynamic address allocation, due to having to configure the irc clients anyway. I admit that the problem is mostly in the weak spec for dcc transfers, but ipv6 would make that much easier to handle (and firewall).

    22. Re:What About Private Address Space? by Luyseyal · · Score: 1

      Well sure, but once you've got enough tunnels poked for everything you need in a moderately sized organization, you may as well have installed a VPN in the first place. I agree with you that most small orgs don't really need VPNs, especially if they just need one service. However, as the number of internal services you need to access remotely increases, a VPN begins to make more and more sense.

      It makes less sense if you replicate browse traffic over the VPN from 1000 workstations. hehehehe
      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
    23. Re:What About Private Address Space? by Deltaanime · · Score: 1

      You can sign up with freenet6, which works over NAT just fine :) For the europe based people, there is sixxs, but they require quite a bit of work to sign up with.

    24. Re:What About Private Address Space? by bkoehler · · Score: 1

      While constructing a building with doors that only open from the inside may not provide the equivalent safety as hiring security to watch your building it does provide a level of defense due to the nature of the building.

      NAT routers are a poor man's firewall; not as secure as a real SPF firewall but usually far better than exposing internal resources to the harsh realities of the net.

      It's great that you only use VoIP and BitTorrent on your public IP. For the rest of the world that uses SSH, SMB/Samba, HTTP, FTP, or other network resources your suggestion isn't practical.

    25. Re:What About Private Address Space? by Bob_Robertson · · Score: 1

      For some reason, when I was investigating, freenet6 just wasn't striking the right chords with me. Can't say why now at all.

      I really like H.E.'s Tunnelbroker.net, very automated. If I had known about their tunnels not working through NAT, I would have been able to do it all without bothering their tech support people at all. I like that.

      Bob-

      --
      The Ludwig von Mises Institute. The reasoning individuals economics
    26. Re:What About Private Address Space? by HawkingMattress · · Score: 1
      Rubbish. A firewall is not a security measure. If you have port {whatever this week's virus uses} opened, you are just as vulnerable as if you don't use a firewall. Similarly, if you have NAT with a public IP between you and the Internet which doesn't forward anything to that port, you are secure.

      Your example is totally bogus, and just proves that in most cases NAT is as efficient as firewalls when it comes to protecting computers behind it. Yes it's not the purpose of the thing, it's just a coincidence that it enhance security, but who cares ? Now i agree that NAT is a kludge, causes a lot of headaches and i just like the static routable ip for everything because it's the internet as it should always have been, but that's another story.
      Security wise, NAT is MUCH better than nothing, and i'd go as far as saying that it is better than a firewall for most users, because real firewalls are really, really difficult to configure, and 99% of the population will misconfigure them.

  10. Oh, penetration by jfengel · · Score: 4, Insightful

    Q: Besides the obvious thing about address space, what other advantages does it have?

    A: Penetration! Because we don't have everybody connected yet!

    Q: And how does IPv6 increase penetration? Does it build wires to people's houses or make provide satellite dishes to third-world countries?

    A: No, but it does make sure we have enough addresses once they have some money to buy the actual hardware stuff!

    Look, I know that eventually we're going to have to transition off IPv4 because of the address space issues, and that we might as well start now, but articles like this make it more like a marketing stunt to sell new hardware RIGHT NOW.

    1. Re:Oh, penetration by Jeff+DeMaagd · · Score: 1

      I agree, I think the reasoning in the story description is flimsy at best. Besides, people don't need IP addresses, computers and other electronic devices do. Even then, most devices don't need publicly accessible IP addresses.

      I need a better argument than "NAT is a hack" and such to convince me. I suspect many others aren't accepting that argument for face value either. In short, not enough people are pushing for IPv6 because the proponents of IPv6 aren't convincing enough people to demand a switch, especially in light of the cost of replacing IPv4 devices.

      I don't want my refrigerator, lighting, A/C & furnace controls (hypothetically) on a public IP. I also don't need my printer, TiVo, Myth box to have a dedicated public IP because those too are private devices and I'd rather keep layer of abstraction for them with port forwarding and some form of authentication to restrict unwanted accesses. Still, those devices are the biggest arguments made for IPv6.

    2. Re:Oh, penetration by leonbev · · Score: 2, Insightful

      Exactly... No one in their right mind would want to give the appliances of their home network a public IP address. The last thing I want to worry about is having my microwave or refrigerator being hacked and wrecking my food because I haven't installed the latest security patch to whatever embedded OS they're running.

    3. Re:Oh, penetration by YaRness · · Score: 1

      Furthermore, most of those people that aren't hooked up yet don't need internet. They need food.

      Whatever idiot was being interviewed sounds more like a marketing exec than a techie. It's so brimming over with bravado and best-thing-since-sliced-bread it's hard to stomach. It's an interview for and by executives; nothing for nerds to see here, move along.

    4. Re:Oh, penetration by warpSpeed · · Score: 1
      This pretty much sums it up...

    5. Re:Oh, penetration by phaggood · · Score: 1

      Q: And how does IPv6 increase penetration? Does it build wires to people's houses or make provide satellite dishes to third-world countries?

      A: No, but it does make sure we have enough addresses once they have some money to buy the actual hardware stuff!


      And when a billion $100 laptops come online in 2009, what are their poor MAC's supposed to eat? It'll be anarchy, I tells ya; dogs sleeping with cats, fire and brimstone...

    6. Re:Oh, penetration by jfengel · · Score: 1

      Actually, I think that "security via NAT" is kind of a scary hack. Yeah, I too am comforted by the fact that my computers are nicely hidden from port scanners by a blue box from Linksys.

      But my TiVo and printer shouldn't need to be protected by that. If they only need to listen on a single port, then they should only open that one and not need the NAT box to protect them. If they're vulernable to buffer overflows on that port, then NAT won't protect them anyway. And if for some reason I had two TiVos, it would be a hassle to set up port forwarding separately for each of them, and maintaining that.

      (I speak hypothetically; I don't even own a single TiVo.)

      So I think that when IPv6 does come there will be a few new opportunities that come from the wide-open address space. It'll also impose more stringent security requirements, but those should be mandatory anyway. NAT for security is as much a hack as NAT for addressing. Yeah, I depend on it, but it's still a hack.

      But that doesn't mean that the guy in the article isn't an idiot. He's clearly just trying to get you to replace your router.

    7. Re:Oh, penetration by Anonymous Coward · · Score: 0

      That's the amazing thing, last night I used the internet to order Pizza! The internet provides food. I've also ordered clothes, electronics, music movies. And all I had to give them in return was a bunch of numbers. The internet is the cure for world hunger and poverty, it's true.

    8. Re:Oh, penetration by Mercano · · Score: 1

      The prefered way to keep private connected devices private is to use a firewall, not NAT. The fact that NAT provides some firewall-like features is a side effect, not it's intended use.

      --
      #include <signature.h>
    9. Re:Oh, penetration by drinkypoo · · Score: 1

      It can have a routable IP address and still not be public. That's what a bridging firewall is for, ala linux.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:Oh, penetration by Jerrry · · Score: 1
      I don't want my refrigerator, lighting, A/C & furnace controls (hypothetically) on a public IP. I also don't need my printer, TiVo, Myth box to have a dedicated public IP because those too are private devices and I'd rather keep layer of abstraction for them with port forwarding and some form of authentication to restrict unwanted accesses.

      Fine. There's nothing in the IPv6 spec that says you can't still use NAT if you want to. It's just that eliminating the need to NAT because of an address space shortage will make things better for people who want to have devices with globally reachable addresses but can't do it now because of the shortage.

    11. Re:Oh, penetration by sgt+scrub · · Score: 1
      100% agreed. When I hear someone regard a current technology as if it is dead only because it stands in the way of someone's sales I know its 100% BS.
      I think NAT worked well
      --
      Having to work for a living is the root of all evil.
    12. Re:Oh, penetration by nzkbuk · · Score: 1

      Yes and no. There's nothing in the spec saying you can't NAT IPV6, but most of the people writing ipv6 implementations have flatout refused to write NAT for it.

    13. Re:Oh, penetration by mikefe · · Score: 1

      It can have a routable IP address and still not be public. That's what a bridging firewall is for, ala linux.

      Uhh, you want a routing firewall. Just turn off the NAT.

      Bridging would only work if you were using the same hardware network protocol, ATM or Ethernet for instance.

      --
      There: Something at a specific location.
      Their: Owned by someone.
      Please make sure your english compiles.
    14. Re:Oh, penetration by mikefe · · Score: 1

      There's nothing in the IPv6 spec that says you can't still use NAT if you want

      When will people stop thinking NAT == Firewall? They are two seperate features. You can have an entirely insecure NAT if you just forward ports to the internal network blindly.

      With IPv4 you will typically have NAT+Firewall internet gateways between network boundaries.

      With IPv6 you will have Firewall internet gateways between network boundaries.

      --
      There: Something at a specific location.
      Their: Owned by someone.
      Please make sure your english compiles.
    15. Re:Oh, penetration by drinkypoo · · Score: 1

      The bridging firewall is nice because you can install it anywhere, without having to worry about intermediate networks for routing traffic. For example, if you have a cable modem that provides you n IP addresses, you can put a bridging firewall between it and your network and still use all n addresses behind the firewall without doing any IP aliasing and forwarding or any crap like that. It's not a necessity for this kind of network but it is likely the way it will be done for home users (unless the gateway device itself does the firewalling - but do you trust your ISP's equipment?)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  11. IPv6 Changes by mrtroy · · Score: 5, Interesting

    What people dont seem to realize is that IPv6 is not only about adding more addresses.

    They also improve the packet structure (by doing things like removing the fragmentation flag)

    And we should be looking at making wireless roaming easier (consider forwarding mechanisms when changing WAP's)

    But more addresses is a key benefit. And there is no real harm, just the cost of transition which can be minimized due to the backwards compatibility provided through tunneling, etc. So if everyone just starts installing IPv6 hardware, everything is happy. Why is this issue being rehashed?

    --
    [I can picture a world without war, without hate. I can picture us attacking that world, because they'd never expect it]
    1. Re:IPv6 Changes by LordEd · · Score: 1

      What i'd like to know if exactly why the author thinks web services won't require a central server. From TFA: "I want to send a piece of music directly to a friend. I don't want to pay someone else to do it for me." and "I need an ISP, I just don't need someone else like Skype to offer me additional services over my connection as I will be able to do it all myself. "

      So the IPv6 protocol includes a chat client and direct P2P application in the stack?

      Sure you can write apps that go directly point to point, but where is the list of those with the service going to be kept?

    2. Re:IPv6 Changes by Crazy+Man+on+Fire · · Score: 2, Informative

      The point is that P2P is harder in IPv4 than in IPv6 since you have to deal with NAT. In IPv6, you could communicate directly with somebody without going through NAT and therefore that part of the communication would be trivial. No fancy stuff would be required to account for NAT between the two peers. You'd still need an application to do the communication, but it would be pretty trivial.

    3. Re:IPv6 Changes by TheRaven64 · · Score: 1

      How about DNS? Most geeks own at least one domain name, and they're not that hard for other people to get. With IPv6, you will get your own IP address for each machine, simply set up which one you're going to use for VoIP, which for file transfers, etc.

      --
      I am TheRaven on Soylent News
    4. Re:IPv6 Changes by Sharkeys-Day · · Score: 1

      The thing with NAT is that it happens in firewalls.

      Those firewalls are not going away. You are still going to have to deal with the poor schmucks behind corporate firewalls which don't support your protocol.

      So NAT may go away, but the problem will stay.

    5. Re:IPv6 Changes by constantnormal · · Score: 1
      "So if everyone just starts installing IPv6 hardware, everything is happy."

      "Scuse me, but I can't think of a personal computer being sold today that does *NOT* support IPv6.

      XP does, Linux does, Macs do too. I'm pretty sure that Cisco's equipment supports IPv6, and all the wireless routers that I am familiar with support it.

      So why isn't IPv6 being rolled out for general consumption? What's the problem here?

      JUST DO IT.

    6. Re:IPv6 Changes by DickBreath · · Score: 1

      You could not only get an address for each machine, you could get an address for each domain name. You could even get a different address for each sub-domain name.

      www.example.com --> address1
      ftp.example.com --> address2
      ssh.example.com --> address3
      pop3.example.com --> address4
      etc.

      You can move these addresses around among machines according to your convenience or workloads. A single computer might simply have all of the above addresses, with a different sub-domain pointed at each different address.

      Want to do an experiment with, say ftp, on a different box? Simply change some ip addresses. No dns changes necessary.

      --

      I'll see your senator, and I'll raise you two judges.
    7. Re:IPv6 Changes by bigpat · · Score: 1

      Why is this issue being rehashed?

      Because we need to convince all the people that should know better, that we really should be asking our providers and all the major ISPs and carriers when they are going to be switching to an IPv6 infrastructure. And telling them that we are ready to press the right buttons on our end to make it happend.

      Sure it will be expensive for some companies to switch to all IPv6 equipment, but in that case NATs really could be part of the solution as they could translate between IPv6 and IPv4 of the local network until local networks are ready to upgrade. And even then large companies could upgrade from the edge inward as budgets and time permit.

      This has to start at the core (I thought there had been a lot of conversion already) and move outwards. It doesn't have to happen in a day. It can be phased, so that at some point a few years down the road the only people running IPv4 are small networks on the edge, and they can still route to the rest of the internet with just a layer of IPv4 to IPv6 NAT.

    8. Re:IPv6 Changes by silas_moeckel · · Score: 3, Informative

      And the ISP's are asking where the profit in doing it is? There are a lot of downfalls to providers Multicast being the big one along with a whole lot of training. I do love all the people that think all of a sudden there toasters can have real IP's and NAT will go away, nothing in IPv6 says they have to give you more than one IP without paying more for it just like today.

      --
      No sir I dont like it.
    9. Re:IPv6 Changes by ngg · · Score: 1

      "I do love all the people that think all of a sudden there toasters can have real IP's and NAT will go away, nothing in IPv6 says they have to give you more than one IP without paying more for it just like today."

      I love being one of them. Why? Because they *have* to give you a /64 subnet for things like globally routable addresses to work. Many people see to not know that a routable IP6 address is made of 64 bits that your upstream provider gives you, plus (in the case of ethernet) 16 bits of padding plus your 48 bit MAC address. The 16 bits of padding is needed because some other link-level protocals have 64 bit address.

      Unless maybe you mean that the ISP will somehow use a link-local address and all of the ISP's customers will be under one great big NAT?

      The reason 64 bits of the address are "thrown away" is that it makes automatic configuration of IP addresses trivial while still precluding the possibility of address collisions. DHCP is not needed with IP6. Each device will actually have multiple addresses because a link-local address is required. The local address is not routable. A /64 subnet is to be given to an *administrative* division (a household, a branch office of a company, etc) because that administrative division will have control over the media addresses of the devices it owns.

    10. Re:IPv6 Changes by silas_moeckel · · Score: 1

      Actualy your incorrect, the /64 can be the public IP's on your cable modem etc (remember it's a L2 bridge) same goes for your cell phones etc. Your descibing one possible addressing scheme that is not required. Per http://www.ietf.org/rfc/rfc2462.txt providers are free to use a statefull addressing scheme. A statefull scheme could be seen by the provider to provide accounting. Nowhere in the IPv6 spec does it require that ISP's assume a router at the customer end rather they are free to assume a single end station and have there gear enforce that assumption.

      --
      No sir I dont like it.
  12. IPv6 will finally allow the connectivity... by Anonymous Coward · · Score: 0

    ...needed to support a network of flying cars.

  13. Why don't we start today? Tunnels! by Nichotin · · Score: 3, Informative

    If you just want a broker that is quick to get started with, go to btexact and sign up. For those "permanent" set ups, go to (you will get a tunnel initially, but have to save uptime enough to get a subnet and such).

    So, what can it be used for? Well, at the moment I do not really use it to browse the web, but I use it for reverse dns on irc (efnet, freenode and most other ircnets have ipv6 enabled servers). In other words, I can have a range of customized hosts (very handy since many friends have shell accounts here) on irc, like @doomtech.net or cust-523452.nix.net.ru. The first one is my own domain, but the second is from afraid freedns. Afraid has a huge range of public domains, which you can add AAAA and PTR records for.
    After thinking up a host, please go to spamcalc, if you don't have the brains yourself to see if your host is dns spam or not. A host like doomtech.net is not dns spam, but something like i.am.god.and.i.live.in.the.cave.with.osama.bin.lad en.info is.

    Sixxs and btexact have pretty exact instructions on how to set this up on a range of operating systems. With the aiccu client from sixxs, the tunnel should work behind most NAT setups as well.

  14. I call it... by Anonymous Coward · · Score: 0

    I call it the Hawkingnet

    1. Re:I call it... by Anonymous Coward · · Score: 0

      ITYM Sagan.

      Even though I think it was Johnny Carson who said "billions and billions" doing a Sagan parody.

    2. Re:I call it... by spauldo · · Score: 1

      That's a futurama reference, actually.

      It's in the episode "Anthology of Interest I".

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
  15. But not everyone will need IP addresses by WebHostingGuy · · Score: 2, Informative

    While it is nice to say we don't have enough IP address to cover everyone now, be realistic. Not everyone will need one. There are a lot of people like me who will have lots and lots of them with all the toys I accumulate. However, there is also going to be a lot of people who won't.

    While we will need more in the future saying we have to have more IPs because we have more people is not necessarily correct. Whereas NAT is being used a lot in corporate networks it is also being used in the home as well. I know, this doesn't solve everything. However, I can say right now there is a generation of people (my parents) who do not know what an IP is, nor do they care. Including them in the big list saying we need IPs for them is a fallacy--they will never use it or want it. And how about babies? Unless you are tagging them with remote tracking chips when they are born chances are they don't need one. Moreover, right now there are entire places in the third world which do not have systematic running water or electricity. Including them in this count is ridiculous as well. They need a lot more basic needs before they all need individual cell phones running IPv6.

    --
    Quality Hosting e3 Servers
    1. Re:But not everyone will need IP addresses by Nichotin · · Score: 1

      Why is the "most regular people don't care" argument used each and every time? I mean, it is not like every person is interested in doing , but we still do it anyway. By the way, there are a lot of people in third world countries who have food and water, just not any tech.

    2. Re:But not everyone will need IP addresses by jcdick1 · · Score: 1

      Most people don't want to or care to vote. Lets not transition to democracy.

      I am only being a little fecetious here. Its about the technological innovation and its about the philosophy of the Net. The internet was designed and intended to be with the philosophy that all devices on the Net are equal in its end-to-end architecture. Your desktop PC is no less or more a valid member of the Net than the big web servers at IBM. Just because the majority of people on the Net don't know about or don't care about having an IP doesn't make this philosophy any less valid or important to maintain.

      And the technological advantage is that it allows the kind of innovation people are looking for. Potentially the greatest communication revolution since the development of the Internet itself - VoIP - would be dramatically easier without the short-term patch of NAT.

      --
      What?
    3. Re:But not everyone will need IP addresses by WebHostingGuy · · Score: 1

      "Just because the majority of people on the Net don't know about or don't care about having an IP doesn't make this philosophy any less valid or important to maintain."

      True to a point. But my statement was that the argument that we are going to run out because we have more people in the world is false. There will always be a significant portion of the people in the world who will not need an individual IP address. Basically, quit saying we are going to run out because we have more people. The real reason for moving from IPv4 to IPv6 should be the technical aspect and when people commit to moving over completely to this it will be because of the technological gains, not because we run out of IPs because someone had a baby.

      --
      Quality Hosting e3 Servers
    4. Re:But not everyone will need IP addresses by Anonymous Coward · · Score: 0

      NAT is being used a lot in corporate networks it is also being used in the home as well. I know, this doesn't solve everything. However, I can say right now there is a generation of people (my parents) who do not know what an IP is, nor do they care.

      This is exactly why we need IPv6.

      Let's say you want to call them on their computer with videoconferencing. Are you going to help them change their NAT configuration so your call can get to their private NAT-hidden IPv4 address? I sure as hell don't want to ever try to step *my* parents through that.

      IPv6 makes a lot of things -- especially P2P-type apps, but not only these -- a lot simpler for everybody involved. Wanting things your parents can use is a great reason in *favor* of widespread IPv6 adoption.

    5. Re:But not everyone will need IP addresses by jcdick1 · · Score: 1

      "The real reason for moving from IPv4 to IPv6 should be the technical aspect and when people commit to moving over completely to this it will be because of the technological gains, not because we run out of IPs because someone had a baby."

      Oh, well, when you put it that way, you are probably right.

      --
      What?
    6. Re:But not everyone will need IP addresses by smithmc · · Score: 1

        While it is nice to say we don't have enough IP address to cover everyone now, be realistic. Not everyone will need one. There are a lot of people like me who will have lots and lots of them with all the toys I accumulate. However, there is also going to be a lot of people who won't.

      Right. And in other news, 640K oughta be enough for anybody.

      Get serious. In the future, everyone will use multiple IP addresses. Someday, they'll be assigning everyone an IP range at birth.

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
  16. Why is NAT so bad? by mightypenguin · · Score: 3, Interesting

    I understand that NAT is considered a hack, but isn't the fact that a device's real address is hidden a security feature for the user? Wouldn't it be that much harder for malicious users to track my internet usage? This would be especially true if I had a mobile device, since moving from one NAT system to another would make following my movements remotely more difficult. So I'd think NAT would be considered a privacy boon. The article doesn't really address this effectively. Also, since most mobile devices have limited bandwidth, I'd think that having a constantly changing IP address, or hiding behind a NAT would mean that DOS attacks against them would be more difficult. If most big mobile device ISPs like the blackberry and sidekick folks offered NAT based access in the future, I'd think that we'd be relatively safe from IPv4 address exhaustion. So stating the main reason for IPv6 being address exhaustion I think is crap. It IS very useful for other reasons though, and I think those reasons warrant it being switched to.

    1. Re:Why is NAT so bad? by smbarbour · · Score: 3, Interesting

      NAT is the one of the best "hack" that has ever been made for networks. I don't want to have every computer publicly accessible. Is there NAT on IPv6? How many addresses are available for v6? Using NAT, the maximum number of connected devices (sorry for not having the figures in front of me) on IPv4 = Total # of public addresses x Total # of addresses in a class A private network (10.x.x.x).
       
      According to my calculations, using Class A private NAT with each address in a Class A public network comes to: 281,474,943,156,225 available nodes. That's over 281 trillion for the utilization of 1 class A IPv4 network. There are plenty of addresses if we use them properly.

    2. Re:Why is NAT so bad? by fractaloon · · Score: 1

      In fact, hiding behind NAT gives you about 17 million potential addresses. Anybody trying to get info on your computer or network has to first find the needle in the hay stack.

      IPv6 offers each business client a block that's 300 million times larger than that. Suddenly the haystack is much much bigger. Home users will probably have just as much obscurity because the ISP will potentially have a block that big for it's clients.

      Proponents of not switching to IPv6 because of NAT's "security" are doing themselves a diservice (sp).

    3. Re:Why is NAT so bad? by Anonymous Coward · · Score: 2, Interesting

      I understand that NAT is considered a hack, but isn't the fact that a device's real address is hidden a security feature for the user?

      Nope. Your real (read public) address is visible. Your fake (read private) address is hidden. NAT is not a security mechanism, and in fact causes security issues because of a false sense of security. Next.

      Wouldn't it be that much harder for malicious users to track my internet usage?

      Nope. It's just as difficult for malicious users. It's more difficult for "valid" users (sys admins, etc.). Next.

      So stating the main reason for IPv6 being address exhaustion I think is crap. It IS very useful for other reasons though, and I think those reasons warrant it being switched to.

      Agreed. The root problem isn't really the address exhaustion, it is address allocation. It wasn't handled very well, and now we're running out. (NAT does buy us some time.) Unfortunately we can't go back and reallocate everything nicely now...

      Oh wait, we can. IPv6 fixes the issue with a brute force approach, increasing the number of available addresses by a large factor. This will work for now, but isn't elegant. If the IPv6 addresses aren't allocated well, we'll have the exact same issue crop up again. And much sooner than anyone currently believes, of course.

      I'm going to simply things dramatically, but assuming a flat 128-bit addressing scheme, we could have up to 3.4028236692093846346337460743177e+38 addresses, or about 56.7 octillion addresses for each person on the planet. A bit much, I should think.

      Now, IPv6 isn't flat, it's true, but 80-bit (anyone remember IPX?) would be more than sufficient, even when considering allocation losses. IPv6 does have some useful features, but its addressing scheme is not one of them.

    4. Re:Why is NAT so bad? by Quill_28 · · Score: 1

      What are you talking about?

      It doesn't matter if you know the internal ip address of someone behind a NAT router you still can't get there from the outside.

    5. Re:Why is NAT so bad? by Anonymous Coward · · Score: 0

      Wouldn't it be that much harder for malicious users to track my internet usage? This would be especially true if I had a mobile device, since moving from one NAT system to another would make following my movements remotely more difficult. So I'd think NAT would be considered a privacy boon.

      Exactly! This is why Business and Governments will push for this technology. It is in their long term best interests to track you and reduce personal privicy. And it will be packaged in a box that reads "Designed save the Children"
    6. Re:Why is NAT so bad? by TCM · · Score: 1

      And with IPv6 and my /48 net, I already have 1,208,925,819,614,629,174,706,176 real addresses, publicly reachable.

      What everyone seems to disregard is that you can't just take all possible IPv4 addresses and squeeze them unto different needs as you want. With each splitting of address space comes the problem of increasing routing tables in routers. IPv6 is not only about increasing the address space but keeping its fragmentation low so that routing tables are more efficient. That's why the smallest subnet in IPv6 is /64 and single customers get a /48.

      Remember, there are 2^16 times as many /48 networks in IPv6 than there are single addresses in IPv4.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    7. Re:Why is NAT so bad? by drinkypoo · · Score: 1

      I don't want to have every computer publicly accessible.

      So uh, use filtering. Deny all from external interface to ip address of host. You're done! Merry christmas. Of course, if something on your internal network gets owned, they can now get to all your devices; probably the answer is to have a DMZ for internet-accessing systems, and a reserved net for everything else. You know, like we commonly do today, using IPv4, even when using NAT?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:Why is NAT so bad? by aj50 · · Score: 1

      Unless you compromise one of the machines on the local network, then you can access whatever that machine has access to.

      --
      I wish to remain anomalous
    9. Re:Why is NAT so bad? by Jerrry · · Score: 1
      In fact, hiding behind NAT gives you about 17 million potential addresses. Anybody trying to get info on your computer or network has to first find the needle in the hay stack.

      That's true, but I'd be willing to bet that more than 90% of all NAT addresses currently in use fall in the range 192.168.1.1 through 192.168.1.10.

    10. Re:Why is NAT so bad? by cciechad · · Score: 1

      NAT is not a security feature it was never meant to be! I don't know how many times this needs to be said. If you want security use a Firewall. If you want many to one mappings use NAT.

      --
      https://www.fsf.org/associate/support_freedom
    11. Re:Why is NAT so bad? by caseih · · Score: 1

      No there is no NAT in IPv6. You simply don't need it. If you want security, you need to do proper firewalling. For example in my organization, outbound traffic will flow on IPv6 directly (which is the same effect that NAT has) but the firewall will prevent any direct connections back in. Even ping can be rejected, minimizing exposure. Honestly this is the more correct way to do it anyway. NAT is broken, plain and simple. And the sooner we can get rid of it the better.

    12. Re:Why is NAT so bad? by vertinox · · Score: 1

      It doesn't matter if you know the internal ip address of someone behind a NAT router you still can't get there from the outside.

      If they compromise the NAT device (aka someone setup the router and thought remote access to the routers setup page would be a good idea, but for some unknown reason didn't change the default password *coughs*) then they could setup up blanket port fowarding to the internal IP address in question and proceed to attack that machine like they would if it were directly on the net.

      But luckily most NAT devices are not setup for that and most people don't know how to turn that option on in the first place.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    13. Re:Why is NAT so bad? by vertinox · · Score: 1

      In fact, hiding behind NAT gives you about 17 million potential addresses. Anybody trying to get info on your computer or network has to first find the needle in the hay stack.

      If i'm not mistaken, if you are using IE and you connect to an IIS webserver server it can log your internal IP by asking IE to ask your OS.

      I remember this because I wrote an ASP page once that had a log of all people who visited the site and I had incorrectly wrote the code to pull that address and we ended up with a list of many 192.168.*.* rather than the true external IP address which we wanted... This was maybe 4 years ago and I can't remember exactly what I did to fix it, but unless MS corrected it with later versions of IE then I would assume that it is not too hard to get someones internal address if they visit a website.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    14. Re:Why is NAT so bad? by Quill_28 · · Score: 1

      I agree but if someone has comprised one of your machines inside your NAT then it still doesn't matter if they know your IP address.

    15. Re:Why is NAT so bad? by forkazoo · · Score: 1

      If a packet gets to the NAT box, and it won't accept a connection from the external interface and forward it to an internal address, then it is filtering. The filtering saves you, not the NAT. We associate NAT with filtering because they are usually done together, but there is no inherent security in NAT by itself. Even if you have a routable IP, you can set up the exact same filter without NAT, and get the exact same security because no external packets will be routed to the local network.

    16. Re:Why is NAT so bad? by dodobh · · Score: 1

      Unless there are two organisations behind NATs wanting to connect with each other. VPNs with AH enabled. True end to end connectivity.

      Use a stateful packet filter, and NAT becomes irrelevant.

      --
      I can throw myself at the ground, and miss.
    17. Re:Why is NAT so bad? by smbarbour · · Score: 1

      So what is the gain of switching to IPv6? Having even more addresses than we currently need? Ensuring that Cisco, et al. continue to generate a profit?

      From the way it sounds, it is currently just to line the pockets of the networking companies for a problem that won't exist for some time.

      It would be like building the ships today for the exodus that may occur in the distant future when our sun "burns out" and the Earth is no longer inhabitable. Of course, civilization could be wiped out by the time that happens, but we need to be ready for it anyway.

    18. Re:Why is NAT so bad? by drinkypoo · · Score: 1

      NAT is a PITA. It creates huge problems with many legacy protocols, many of which cannot be supported without packet inspection and rewriting to determine and/or change port numbers and IPs. Even worse, many legacy protocols are tied to specific port numbers, which means you can only support one system using a specific protocol per routable IP. Having all-routable IPs would eliminate this problem entirely.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    19. Re:Why is NAT so bad? by smbarbour · · Score: 1

      Do these legacy protocols you refer to support IPv6? If not, then they will have to be re-written anyway. True, NAT is not the best possible solution for every circumstance, but it is more compatible with the current set of protocols than IPv6 is at the moment. The legacy systems don't support IPv6. Microsoft doesn't even have a viable IPv6 client available to the public yet. For most purposes, NAT is completely transparent.

  17. When we actually run out of numbers .... by bizitch · · Score: 3, Funny

    The closer we actually get to REALLY running out of IPV4 numbers - the more IPV6 will become adopted

    This is known as "Market Forces" - this is a foreign concept to many but it is the reality of this situation.

    When NAT becomes insuffiecient to handle the demand - IPV6 will be ready to roll. Then every man, woman, child, insect and grain of sand will have its own PUBLIC address which we can then begin to exploit - YAY!

    --
    ---- "Logoff! That cookie shit makes me nervous!" - A. Soprano
    1. Re:When we actually run out of numbers .... by TubeSteak · · Score: 1

      That's kinda like saying Microsoft will code a new OS once the patch level of their current system gets overloaded.

      MS has done amazing things with their OS, but 2k and XP are essentially built off of NT4. Win NT4 --> Win NT5 --> Win NT5.1

      My understanding is that Vista is based off Windows Server 2003 but we've seen that as Vista gets closer to release, features are dropping like flies.

      Its much easier to keep adding hacks than to announce "i'm making a big change. deal with it" Plus, this is the internet, no one person can say "that's it, i'm done with IPv4" and make it affect everyone else.

      --
      [Fuck Beta]
      o0t!
    2. Re:When we actually run out of numbers .... by Procyon101 · · Score: 1

      Nah. It's more fun to cry about how we're all going to die from lack of IP addresses and peak oil.

    3. Re:When we actually run out of numbers .... by kickdown · · Score: 0

      Actually, there is a growing market when IPv4 address get short. ISPs can make a whole lot of money by making special offers that give you a static IP, or even a (ridiculously small) subnet like /30. The shorter IP addresses get, the more money can be made out of the shortage.
      So, I am very sure that there are ISPs that are quite happy with the situation as it is now.
      The problem is: ISPs are the ones that need to set things up for IPv6, and if they have no incentive, it won't happen.

      --
      Continuous positive slashdot karma since... uh, maybe next year.
    4. Re:When we actually run out of numbers .... by zerogravity54 · · Score: 1

      Bizitch said: >"This is known as "Market Forces" - this is a foreign concept to > many but it is the reality of this situation." That may be true but who's to say that waiting for people's collective procrastination, laziness and selfishness to force situations to the breaking point and change is the SMARTEST way for things to be done? Do any of us who are arguably mentally healthy ENJOY being pushed, crammed, squeezed, mangled, etc. by competition and market forces? Wouldn't we appreciate it and have a much higher standard of healthy, satisfying living if change was approached and taken on thoughtfully and proactively?

  18. Good ideas always make slow progress by Billosaur · · Score: 2, Informative

    Just think of the number of systems that rely on IPv4 right now: networks, routers, cell phones, etc. There really isn't a lot of room left at the current rate of expansion. But let's face, that's how we get: complacent. The current system is working -- why bother with a new one? I believe the Romans got that way toward the end...

    I read the article and it was insightful, but I didn't have a lot of background on IPv6, so I searched for some background and found this on the details and this on implementing it in Linux.

    From the article: The Internet was not designed like this. It was designed to enable peer-to-peer and VoIP. In the meantime, through NAT, telecomms companies are offering VoIP but they want to bill you for it, but the Internet was not designed with any billing mechanism. When you connect to the Internet you pay anyway, so why should you pay for more services? This is the big debate. The Internet was not designed for telecomms companies, it was designed for everyone to share expensive CPU power. When you share expensive resources you can do anything.

    I agree. Paying for sevrices is basically just icing on the cake for telecoms.

    --
    GetOuttaMySpace - The Anti-Social Network
    1. Re:Good ideas always make slow progress by csgames · · Score: 1

      ahem, have a look at the newest gen of cell phones in Asia, 100% of them support ipv6. I think these huge corporations have a goal in mind. New killer apps are on the verge of becoming "public" and telcom infrastructure has to be ready. Want it or not, ipv6 is going to happen. Speculation about "When" or "Why" is useless. Just wait and you'll see.

  19. Not a convincing argument by Anonymous Coward · · Score: 0

    Sure, sure... Not everyone wants a single IP address to uniquely identifies them. What's the point of using this metric? That's the lamest argument possible. Not everyone uses the Internet 24/7/365, in fact, many users share addresses from a pool. As far as I know, the "shortage" of IP address space doesn't actually result in higher prices for me, however, a switch to IPv6 will. There has to be a more convincing argument for switching, one that involves people benefitting economically, but that isn't it.

  20. Yes, yes yes... by Colin+Smith · · Score: 1

    But what does it give me... Now... That I don't have already?

    --
    Deleted
  21. Mmmm, things... by Anonymous Coward · · Score: 0

    There are things. Billions and billions of devices that will service these people.

    I like the sound of that! :O

  22. big changes by BushCheney08 · · Score: 1

    I'll finally have access to the extended and color version of ASCII Star Wars via telnet at towel.blinkenlights.nl.

    --
    Be a real patriot: Question authority. Think for yourself. Formulate your own conclusions.
    1. Re:big changes by Anonymous Coward · · Score: 0
      are you sure?! ;)
      Well, the IPv6 version is exactly the same as the IPv4 one.

      The difference is in the visitors...

      Je bent een Stoere Bikkel, aka You Rock.

      Except when your name is mendel.
      Sorry dude, life's a bitch.
  23. P2P file serving redundant in IPv6? by Anonymous Coward · · Score: 0

    I'm not really familiar with IPv6. Can some explain how P2P will make file serving redundant?

  24. Mismanagement of the IPv4 address space by Caspian · · Score: 1, Informative

    This is freaking ridiculous. And there is a simple solution.

    The ONLY machines that need actual IP addresses are servers and gateways.

    PERIOD.

    Everyone else can be NATted.

    The simple solution is to NAT everyone and everything that isn't a server or a gateway to other machines. Instead of a typical University gobbling up class-Cs or even class-Bs like candy, they'd require a single class-C at most. Every other machine on campus would be NATted. AOL could have a single class-C, since its users aren't technologically literate enough to want actual "real" IPs. ISPs with a mix of non-technical and technical users (such as Earthlink) would need more, so they could sell "real" IPs to those who'd use them. ISPs which cater to geeks (such as Speakeasy) would need still more.

    In such a world, we'd see a complete reversal of current trends; huge national ISPs whose user populations are mostly non-geeks would need only a scant few IP addresses, and smaller "boutique" ISPs whose users are mostly geeks would need more than AOL or MSN.

    And we WOULDN'T run out of IPs this way.

    I've heard the hype about every coffee percolator, Coke machine and pencil sharpener having its own IP address. That's nice. But not necessary. This whole "crisis" with us running out of IPs can easily be averted with a change in IP distribution policies.

    --
    With spending like this, exactly what are "conservatives" conserving?
    1. Re:Mismanagement of the IPv4 address space by pdawson · · Score: 1
      This is freaking ridiculous. And there is a simple solution.

      The ONLY machines that need actual IP addresses are servers and gateways.

      PERIOD.

      Everyone else can be NATted.


      And now you've totaly given into the producer/consumer model, where we're supposed to be good little consumers that just suck down whatever the large corps choose to publish. Gods forbid we should want to host anything or act as a server.
    2. Re:Mismanagement of the IPv4 address space by Caspian · · Score: 1

      If you want to host something, your choices are legion:

      1) Pay for hosting services.
      2) Pay for a shell account somewhere, SSH-tunnel in, and have people connect to your machine's server through the tunnel.
      3) Pay for a "real" IP.
      4) Move to a boutique ISP that provides "real" IPs to all users.

      --
      With spending like this, exactly what are "conservatives" conserving?
    3. Re:Mismanagement of the IPv4 address space by kotj.mf · · Score: 2, Insightful

      What if the "average" user wants to host their own content, without worrying about some external entity having control over it?

      That was the original point of the Internet - not to differentiate between content/service "providers" and "consumers," but to enable redundant p2p information sharing.

      --
      hang brain.
    4. Re:Mismanagement of the IPv4 address space by Wishful · · Score: 1, Interesting

      Except you're assuming that you force every network programmer to design their client/server programs the right way. I've lost count of the number of times my company has had a turf war over a vendor trying to force a badly designed client/server setup on us where for example , the vendors wants to directly connect to 3000 devices on our network. (oh but of course we both use the same RFC1918 space...ie all of it). So what happens......they ask me to setup 3000 static NATs. This is the kind of work that makes me pull my hair out, and its all caused by crappy choice by software designers who have no grasp of the issues faced by network/firewall people at the IP layer.

    5. Re:Mismanagement of the IPv4 address space by Anonymous Coward · · Score: 1, Insightful

      You work for DMCA, right?

      This won't only kill almost all P2P schemes, but every direct file transfer between any two Internet users.

    6. Re:Mismanagement of the IPv4 address space by markov_chain · · Score: 2, Insightful

      In the original vision of the Internet everything is supposed to be a server, so we're back at square one.

      Creating a system where one has to opt in to have a routable IP is treading on a slippery slope. Soon after, you might need a special permit to have a server, and before you know it we're back to gatekeepers and the telephone network.

      Why shouldn't non-geeks have routable IPs? How many future Shawn Fannings, DVD Jons, or Linus Torvalds' would we lose through such restriction? The Internet should stay as connected as possible, so that the innovation and creativity at the ends stays unencumbered and free. Just think about how long it took telephone companies to implement call-waiting, *69, etc. Also check out the End-to-end Arguments in System Design, it's a classic.

      --
      Tsunami -- You can't bring a good wave down!
    7. Re:Mismanagement of the IPv4 address space by kotj.mf · · Score: 2, Insightful

      Oh, and before you try to convince me that "average" users don't want to host their own content, please consider the popularity of Kazaa, Blogger, Flickr, del.icio.us, Podcasting, Myspace, and the world ending when mp3.com went tits up. There are plenty of non-geeks who want to create and share information on the net, and they're currently mostly limited to using a somebody else's machine to do it for them, because the barrier to being a "server" is so high.

      --
      hang brain.
    8. Re:Mismanagement of the IPv4 address space by mark-t · · Score: 3, Insightful
      "Period"?

      Uh... no.

      How about anyone that is running software that requires a peer to peer connection (and I'm not just talking about filesharing software)? And it's further worth pointing out that the only people that require such connectivity are not just the techie geekoid people. Running VoIP through NAT, for example, is a bitch and a half, and often not even possible if the end user does not have administrative rights on the NAT.

      Your argument does touch on a very good reason why NAT would not be entirely obsolete even upon the move to IPv6, however.

      (Also, by playing around with IPv6 extension headers and a gateway that adds or strips headers to a packet, it's theoretically possible to do routing right _THROUGH_ a NAT on IPv6).

      So really, it seems that the only argument against IPv6 migration is just that people are lazy and cheap and don't want to do it right now because it'd actually require some effort.

    9. Re:Mismanagement of the IPv4 address space by mrbcs · · Score: 1
      This is freaking ridiculous. And there is a simple solution. The ONLY machines that need actual IP addresses are servers and gateways. EXACTLY! Sorry I don't have mod points. This is the best post in the thread.

      This whole issue sounds like the y2k scam all over again. (yes I know it was real but not the way it was adver-terrorized) In 6 years I saw 2 (TWO) home computers that weren't y2k compatible. Yet people were all told they needed new computers. That crap totally blew the crdibility of the computer industry. I doubt home users will be fooled again.

      --
      I'm not anti-social, I'm anti-idiot.
    10. Re:Mismanagement of the IPv4 address space by kotj.mf · · Score: 1

      Can you see the irony in being required to pay money to be something other than a "good little consumer"?

      --
      hang brain.
    11. Re:Mismanagement of the IPv4 address space by CodyEbberson · · Score: 1

      That might be sufficient for the internet as we know it today, but it's a short sighted view. As applications, and especially devices, move more to a p2p architecture, each online agent will need to be uniquely and globally identified. The paradigm of "open a browser and type in the url" is just one use case. I want my refrigerator to be able to talk to my car, and my watch to be able to talk to my tv. Those scenarios will require more addresses.

    12. Re:Mismanagement of the IPv4 address space by LordKazan · · Score: 1

      You would also be castrating the internet and preventing tons of functions it was intended to be capable of performing from being performed. You can kiss any type of peer to peer activity goodbye; and contrary to the RIAA and MPAA's assertions there are millions of legal uses for p2p communication.

      --
      If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    13. Re:Mismanagement of the IPv4 address space by Anonymous Coward · · Score: 0

      Alright grandpa, forgot to take your meds again? Pay, pay, pay. I already pay for a line with ~600kbps upstream. Why shouldn't I use it? And your point 3 slighty contradicts your rejection of IPv6.

      I hereby sentence you to setting up VoIP services behind NAT for eternity.

    14. Re:Mismanagement of the IPv4 address space by Alioth · · Score: 1

      So, basically - you'd effectively ban games from the Internet. Tens of thousands of gamers on a large ISP behind one small piece of address space doesn't really fly that well with NAT and UDP connections (which are stateless - it's a big hack and a lot of guesswork to try and keep state on more than a handful of users using UDP). And you'd be banning VOIP.

    15. Re:Mismanagement of the IPv4 address space by Anonymous Coward · · Score: 0

      The ONLY machines that need actual IP addresses are servers and gateways. PERIOD. Everyone else can be NATted.

      You obviously work for a router manufacturer. :-)

      I agree with your sentiments, but it would seem to me that wireless roaming and similar location-independent, network-hopping paradigms would be much more elegant and scalable if everything had it's own IP address and didn't have to be NATed.
       
      I can also think of a number of situations where I would like a device / appliance / car / etc to have its own address. I could think of a number of things just in my car alone having addresses. But of course we could NAT that too ;-)

      I think the biggest advantage of IPv6 would be getting a block of addresses for life, and not having to redo all your infrastructure if you change ISPs or need to expand your range.

    16. Re:Mismanagement of the IPv4 address space by Mercano · · Score: 1

      The problem is that your hypothetical online coffepot is probably going to need to accept incoming connections so you turn the thing on from the train on the way in to the office. NAT is causes an inordinate amount of pain when it comes to inbound connections. Things like UPnP help a little, but, unless you are the only one who wants to used the well known port for whichever service you are running, you need some way to inform your potential callers which port you are actually listening on. Works OK for Bittorent, when you can spread the word via the tracker, or something like XBox Live, where live can tell folks which port the server is listening on, but a pain if all you have to work with is a web browser.

      --
      #include <signature.h>
    17. Re:Mismanagement of the IPv4 address space by TCM · · Score: 1

      What you suggest as "choices" are nothing more than kludges which wouldn't be necessary if everyone had IPv6 and a publicly routable address space.

      Pay for a shell account and provide services over a SSH tunnel? That's brilliant! Why get IPv6 when the "solution" is so obvious. Duh.

      Pay for a real IP(v4)? Brilliant! We don't need plenty of IPv6 addresses for everyone when we.. uh.. can just buy IPv4 addresses.

      Move to a "boutique" ISP to get "real" IP adresses?

      Dude, what you list are problems that IPv6 will solve, not choices that make IPv6 unnecessary. I suggest you get a reality check.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    18. Re:Mismanagement of the IPv4 address space by Caspian · · Score: 1

      Uhh, "DMCA" is a law, not a corporation or government entity.

      How does one "work for" a law?

      --
      With spending like this, exactly what are "conservatives" conserving?
    19. Re:Mismanagement of the IPv4 address space by bn-7bc · · Score: 0

      well you will need yo change the first 48 bits of the addresses (iana recomends that isps give /48s to all costumers), but it will make renumbering easier. If uoe ever need more than 16bits for subneting (128 -64(interface id) -48(mask from isp)) you will probably just get an extra /48 mor info http://smakd.potaroo.net/ietf/idref/rfc3177/index. html

    20. Re:Mismanagement of the IPv4 address space by ArmpitMan · · Score: 1
      So really, it seems that the only argument against IPv6 migration is just that people are lazy and cheap and don't want to do it right now because it'd actually require some effort.
      Are you saying this is a bad argument?
  25. Global connectivity? by dumpsterdiver · · Score: 1

    Err - how is an expansion of IP space going to bring a net free of government speech controls (not to mention physical connections) to parts of the world that are resisting? We can't even pry those things out of the hands of the US Government, much less those of Robert Mugabe or Iraq.

  26. I don't get it by nmg196 · · Score: 4, Insightful

    Why does IPv6 make P2P any easier to implement?

    Why does it remove the need for servers?

    Why does it mean that we "won't need providers such as Skype anymore because we'll be able to do it all ourselves"?

    I don't see how IPv6 lets you do ANY of these things. You'll still be firewalled, you'll still need servers and software vendors like Skype. In fact the only thing about IPv6 that would seem to me to help P2P is that slighly more people might end up not being NATed but that won't affect anything much.

    Does this person actually know what they're talking about or are they from marketing?

    1. Re:I don't get it by Eriky · · Score: 1

      I think because multicasting with IPv6 will be better. You can multicast one stream to, for example, a single server on the other side of the world. From there 1000s of ip's can read your single stream.

    2. Re:I don't get it by k_187 · · Score: 1

      because instead of these aggrigation servises, each box on teh intarweb will be able to have its own address, and thus you'll be able to connect to them all individually. I think that P2P and skype and the like are more than just programs that say connect to that person over there, but it does allow for the removal of an extra layer of abstraction. Whether or not one would want that layer gone is another question.

      --
      11 was a racehorse
      12 was 12
      1111 Race
      12112
    3. Re:I don't get it by it0 · · Score: 3, Interesting

      I always understood that ipv6 has the ability to send 1 packet to mupltiple persons at once. So for example if you use bittorrent, and there are 7 people connected then you only have to send out 1 packet to reach to 6 people in stead of 6 packets with ipv4.

      The rest I don't know

    4. Re:I don't get it by Thomas+Charron · · Score: 1

      No need for NAT with ipv6. Makes it easier for clients to be servers.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    5. Re:I don't get it by vidarh · · Score: 1

      You miss the point. A large number of those machines will still be NAT'ed or firewalled and so will still need that extra layer because security or whatever hardware/software they're behind won't let them connect directly.

    6. Re:I don't get it by jrumney · · Score: 1

      IPv4 supports multicasting too, its just blocked by too many routers to be useful.

    7. Re:I don't get it by Anakron · · Score: 3, Informative
      Why does IPv6 make P2P any easier to implement?
      It allows you to make direct connections from any computer to any other computer connected to the Internet. The way it was supposed to be. I'm guessing most peer to peer applications contain a lot of code that is designed to work around NAT.
      Why does it remove the need for servers?
      It doesn't. Not servers in the sense we normally think of them
      Why does it mean that we "won't need providers such as Skype anymore because we'll be able to do it all ourselves"?
      I believe what he is referring to is the fact that Skype tries to set up a connection between two users who are both behind NAT boxes by using another computer that is not NATed. That part wouldn't be necessary. We'd still need the Skype software, though.
      you'll still need [...] software vendors like Skype
      Right. It's just that Skype wouldn't need to use the kinds of ugly kludges they do now to get around NATed users.
      In fact the only thing about IPv6 that would seem to me to help P2P is that slighly more people might end up not being NATed
      The hope is that nearly no one will have to be NATed. Please don't start that security story again. NAT is NOT about security. NAT boxes usually also perform firewall duty (and usually not very well). That's it
      but that won't affect anything much
      I disagree. I think it will help a great deal. Network administrators and creators of network-aware applications spend a great deal of time trying to make sure that NATed users won't see much of a difference (and it needs to be reinvented for every application). If they no longer need to spend time trying to work around such a broken concept, we can hope to see real innovation.
      --
      There are 11 types of people. Those who understand binary, those who don't and those who are sick of this lame joke.
    8. Re:I don't get it by cecom · · Score: 1

      No need for NAT with ipv6. Makes it easier for clients to be servers.

      That's what everybody says, but how exactly is it going to happen ? Is my ISP going to give me 16 static IPv6 addresses by default ? What if later I need to make them 32 ? Will they be able to give me 16 more while keeping the whole 32 contiguous ?

      Or if the ISPs give away, say, 65536 addresses by default, it may turn out that we run out of IPv6 too :-)

    9. Re:I don't get it by Anonymous Coward · · Score: 0

      I'm kind of a networking noob, but I'm curious if such
      feature would unfortunately make multiple denial
      of service attacks easier. Basically you can flood
      all ip's within a certain ip block without a tradeoff
      to your own bandwidth.

    10. Re:I don't get it by kwalker · · Score: 2, Informative

      Because two nodes on an IPV6 network wouldn't be stuck behind closed NAT firewalls and not able to communicate directly. Currently, if you're using Yahoo IM and want to send someone a picture, you have to relay it through Yahoo's servers, which causes a bottleneck because thousands of other people are doing the same and everything bottlenecks through Yahoo. With IPV6, both ends could have a public (possibly static) IP address, so person A could connect directly to person B and bypass the traffic jam at the server. It gets worse on something like eDonkey where if both ends are NAT'ed the transfer CANNOT happen.

      As for removing the need for Skype, it wouldn't, but it would change. A Skype server would just need to know IP addresses so if person A wants to talk to person B, the Skype server just tells A "B is at 0:1:2:3:4:5" and A can then connect to B directly, instead of relaying through god-only-knows how many intermediates who may or may not be compromised or malicious. However, if you were setting up your own PBX with a static IP (And IPv6 has enough addresses that you could), then you wouldn't need a central authority (Skype server) to do the matchmaking.

      Yes you'll still be firewalled, but the firewall will be at the end point, not in the middle somewhere that you have no control over (As in my case). The firewall rules would just change to a FORWARD rule instead of a "direct this port to this IP" rule.

      IPV6 is about decentralizing, while NAT is essentially centralized (At the NAT server). If something can't change ports (Some VPNs, old protocols, not smart enough, etc), then you can't have more than one person behind the NAT using said protocol. NAT also causes problems because to the machine on the public-side of the NAT, only sees the address of the NAT gateway, not the address of the machine actually making the request. The implications of that are left up to the reader.

      --
      ... And so it comes to this.
    11. Re:I don't get it by clenhart · · Score: 1

      Ahh bullsh**.

      Did you know that Skype routes other people's traffic through your connection, b/c they are behind a NAT? Two NAT'ed boxes makes it impossible for mere mortals to connect to each other.

      Granted, *some* people can setup port forwarding, but not my Grandmother.

    12. Re:I don't get it by WhiteWolf666 · · Score: 2, Informative

      You haven't grasped the number of addresses IPv6 will make avaliable.

      65535?

      Think bigger:
      IPv6 is intended to address the concern of IPv4 address exhaustion. There are too few IP addresses available for the future demand of device connectivity (especially cell phones and mobile devices). IPv4 supports 4.2 billion (2564 4.294 × 109) addresses, which is inadequate for giving even one address to every living person, much less support the burgeoning market for connective devices. IPv6 addresses this problem by supporting 340 undecillion (655368 3.4 × 1038) addresses. For scale, this would allow an average of about 430 quintillion (4.3 × 1020) unique addresses per square inch, or 670 quadrillion (6.7 × 1017) per square millimeter, of the Earth's surface. In other terms, assuming a population of about 6.5 billion humans, there are enough IPv6 addresses such that every atom of every person on Earth could be assigned 7 unique addresses with enough to spare (assuming 7 × 10^27 atoms per human).
      Source: http://en.wikipedia.org/wiki/IPv6

      So, think more like 4.9 x 10^28 address _per person_ (not per connection).

      That's a little more than 65536.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    13. Re:I don't get it by corblix · · Score: 1
      In other terms, assuming a population of about 6.5 billion humans, there are enough IPv6 addresses such that every atom of every person on Earth could be assigned 7 unique addresses with enough to spare (assuming 7 × 10^27 atoms per human).

      In other words, forget about subatomic-scale networked devices. Sorry, not enough address space. Geez, why don't these people ever think of the future?

    14. Re:I don't get it by Breakfast+Pants · · Score: 1

      IPv4 allows the same thing. Unless there are major improvements with IPv6 it will never see the light of day. Think about it, it means that a single user could be 6x more effective at DDoSing sites (and that's just your example, multicasting theoretically should scale a lot higher up than that).

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    15. Re:I don't get it by cecom · · Score: 1

      OK, but it still doesn't answer my question. How is it going to work in practice ? Obviously there isn't going to be a world database with IP addresses for all human beings and their toasters :-). Perhaps addresses could be distributed geographically (each square meter gets an address), but even that is impractical since it requires infrastructure that doesn't exist.

      I admit that I didn't think of the scale, though. Wow. Even if the ISP gave 65536 addresses per subscriber, which as it turns out is nothing for IPv6, that would be more than enough for all practical purposes and most businesses.

      I don't know how we are going to be able to remember 128-bit numbers ... They look nothing like 192.168.0.1 ...

    16. Re:I don't get it by just_another_sean · · Score: 1

      I think you are referring to multi-casting and that is available in IPv4. See RFC 2365 if you're curious.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    17. Re:I don't get it by Thomas+Charron · · Score: 1

      Hehe, I think other people who responded with exactly how many IPs would become available demostrated. 64k? Aww, hell no. Run your own internet under your existing ipv4 IP.. ;-)

      Now, how these can be addressed? Fark if I know. DNS IMHO, wildcard to your own personal DNS in a box servers.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    18. Re:I don't get it by man_ls · · Score: 1

      And of those 4.3x1020 addresses, your upstream United States ISP will give you exactly one. And charge for a "Home Networking" package to give you more addresses, or make you buy a NATv6 router.

    19. Re:I don't get it by xant · · Score: 1

      NAT provides users with a way to make themselves invisible to incoming connections, protecting them from bugs in the operating systems of computers on the LAN. We'll still need that, we just won't call it NAT, and it'll still have most of the same problems. (The step that will be eliminated? "Now go to whatsmyip.org.")

      --
      It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    20. Re:I don't get it by volkris · · Score: 1

      Multicasting is generally a subscriber-based system.

      That's part of the difference between muticast and broadcast.

    21. Re:I don't get it by volkris · · Score: 1

      It's not that it's blocked; it's that it's simply not supported.

    22. Re:I don't get it by chuckychesthair · · Score: 2, Informative

      Skype is popular because it can function even when both ends of the conversation are going through a NAT. NATs are inherently evil (no, they don't offer more protection than a simple ingress filter on any "real" router) and break the end-to-end principle. With IPv6, you will not get just 1 IP address like in IPv4, but a shitload (currently the thinking is a /48, which is over 65000 subnets, each subnet containing roughly 4 billion * 4 billion addresses, but thinking is changing towards /56's, only 256 subnets, still an impressive number of addresses).

      What this will do it 2 things:

      1- allow for more machines to do any particular service. (multiple VoIP devices, multiple webservers, no extra configuration to restore ICQ file transfers, easy webcamming)

      2- reduce worm problems (because most addresses are not used, simply scanning address ranges will not be successful, limiting worm propagation by several orders of magnitude)

      So, no, it doesn't remove the need for servers per se, but most applications that set up peer to peer connections these days need some other machine to bypass the NAT problem. With IPv6, NAT is no longer needed (although there will be idiots that think it makes things more secure and demand it for IPv6 as well. I'm praying it won't catch on)

      CC

    23. Re:I don't get it by WhiteWolf666 · · Score: 1

      Doesn't matter. There are many organizations which will give you a /64 prefix, no problem.

      Earthlink, for one: http://www.research.earthlink.net/ipv6/faq.html#4

      Or Hurricane Electric:
      http://ipv6tb.he.net/index.php?Example_Session=2f1 d74953d2143978bddd2e17b4e4c14

      There are many more.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    24. Re:I don't get it by WhiteWolf666 · · Score: 1

      Simple, like this:
      http://www.research.earthlink.net/ipv6/

      The current plan for most ISPs is to give each individual his own /64 prefix.

      That means:
      Q: What does that mean, "a /64 IPv6 network prefix"?
      A: An IPv6 address contains 128 bits. A "network prefix" is the first N bits of an IPv6 address. If we refer to a "/64" network, we mean a network in which the first 64 bits of the IPv6 address identify the network, while the last 64 bits define individual nodes on that network. A /64 network may contain up to 18,446,744,073,709,551,616 individual nodes. In contrast, the entire address space for IPv4 only supports a theoretical maximum of 4,294,967,296 individual nodes.

      Q: That seems like overkill. Why would you give out such big network blocks?
      A: Because "that's just the way it's done". A lot of the functionality of IPv6 depends on the network block being a /64 (or larger) prefix. If you have a network block smaller than a /64, certain things (like Stateless Autoconfiguration) will no longer work.

      Source: http://www.research.earthlink.net/ipv6/faq.html#4

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    25. Re:I don't get it by WhiteWolf666 · · Score: 1

      And another point, its not really question of how it'll work in the future.

      That's how it works, NOW. Want your own routable /64 IPv6 network?

      See here:
      http://www.6bone.net/

      and here:
      http://ipv6tb.he.net/

      You can tunnel IPv6 over IPv4, so you can do it right now, with your existing ISP service. Of course, there aren't a whole lot of destinations, yet. But that'll come with time.

      Also, you won't remember 128-bit numbers. That's what DNS is for. I feel its a small price to pay for all the improvements in IPv6.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    26. Re:I don't get it by IpalindromeI · · Score: 1

      Is my ISP going to give me 16 static IPv6 addresses by default?

      If you chose a good ISP they would. Probably more.

      Will they be able to give me 16 more while keeping the whole 32 contiguous?

      Why would the addresses need to be contiguous?

      it may turn out that we run out of IPv6 too :-)

      Possible, but pretty unlikely. According to Wikipedia, "For scale, this would allow an average of about 430 quintillion (4.3 × 10^20) unique addresses per square inch of the Earth's surface."

      --

      --
      Promoting critical thinking since 1994.
    27. Re:I don't get it by IpalindromeI · · Score: 1
      Does this person actually know what they're talking about or are they from marketing?

      He probably does know what he's talking about, but some of his answers sure looked like market-speak to me. Check out this excerpt:
      IPv6 will impact the IT industry from a value proposition viewpoint and from a scalability perspective. The new value-add that IPv6 will put on the table is a comprehensive reduction of complexity of networks to enable deployment of new end-to-end services and thereby create innovations to generate new revenues at much reduced costs.

      This stuff is so tiring to wade through. Just say it will make things simpler so that we can focus on more important things. Was that so hard?
      --

      --
      Promoting critical thinking since 1994.
    28. Re:I don't get it by Sithgunner · · Score: 1

      For one, VPN surely does become trivial. And I'd love to see it happen.

    29. Re:I don't get it by Wikipedia · · Score: 0
      IPv4 allows the same thing. Unless there are major improvements with IPv6 it will never see the light of day. Think about it, it means that a single user could be 6x more effective at DDoSing sites (and that's just your example, multicasting theoretically should scale a lot higher up than that).

      I'm no networking guru, so correct me if I'm wrong, but wouldn't they have to have acknowledged you already? As an example, six people say that they want such and such data, an mp3 file for example, they've acknowledged that they want that data via the p2p network, so they get that data.

      A website doesn't want your DoS, so they deny data from a potential DoS'er. They can't be DoS'ed because the network is smarter as a result of ipv6??

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
    30. Re:I don't get it by man_ls · · Score: 1

      The Earthlink link is amazing.

      Will it still work as a regular IPv4 NAT router as well? Or just an IPv6 router? Or does Earthlink provide a 6-to-4 bridge that isn't horribly high latency so we could still play games, etc. over it?

    31. Re:I don't get it by WhiteWolf666 · · Score: 1

      I think it runs IPv4 and IPv6 concurrently. That's usually the way you run IPv6. I'm not sure what you mean by 6-to-4 bridge.

      If you mean tunnel IPv6 over IPv4, then yes, most likely. You probably won't see a huge increase in latency, properly configured, its just another hop.

      If you mean support IPv4 apps on a pure IPv6 network, than no. AFAIK, no one has a good 4-to-6 bridge, which is what you would be talking about.

      Most apps don't have proper IPv6 support yet, however, there isn't any reason not to run IPv4 and IPv6 concurrently. The only limitation is IP addresses, but thats not a limitation that we'll be able to resolve. The only solution to that is native IPv6 support in apps; there's simply no way to map it correctly. The only possible solutions become hopelessly complex and kludgy; this means things like dynamically allocating IPv4 addresses in VPNs routed over IPv6 for legacy supported apps.

      Far better to just hobble along as we've been doing so, and properly switch to IPv6 for new equipment and apps. The main point of the 6-to-4 stuff is so you can run concurrently, so there isn't a break. Eventually, we'll be able to turn off the IPv4 stuff. Perhaps then, we'll have a functional IPv4 VPN over IPv6 tunnel that will allow us to setup private IPv4 networks for legacy apps.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    32. Re:I don't get it by WhiteWolf666 · · Score: 1

      As usual, I made an error.

      Someone's apparently solved the IPv4 over IPv6 problem.

      Solution here:http://www.ipv6.rennes.enst-bretagne.fr/dstm/

      I might try and make my household IPv6 ;-)

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    33. Re:I don't get it by Anonymous Coward · · Score: 0

      > I'm guessing most peer to peer applications contain a lot of code that is designed to work around NAT.

      Not really. Most P2P applications contain a lot of documentation explaining to NAT users how to configure their router's firewall to pass through the ports needed by the P2P application.

      If a P2P user doesn't open up any of his ports, then he can only participate on P2P as a "client-only", meaning that he can't directly trade files with other "client-only" users. No amout of coding can solve that problem.

    34. Re:I don't get it by FooBarWidget · · Score: 1

      IPv6 won't solve the NAT problem. Many people use NAT not because they don't have enough IP addresses, but because their ISPs don't allow them to connect more than one computer to the Internet.

    35. Re:I don't get it by jrumney · · Score: 1

      Are you saying that IGMP, the 224/4 IPv4 address range and RFCs 1112 and 2588 do not exist?

    36. Re:I don't get it by nzkbuk · · Score: 1

      NAT provides users with a way to make themselves invisible to incoming connections, protecting them from bugs in the operating systems of computers on the LAN.
      Nope, that's what a firewall does (almost all NAT boxes also have some degree of firewalling built in)

      NAT provides a way of multiple computers (and devices) to connect to the internet through 1 ip address.

      We'll still need that, we just won't call it NAT,
      We'll just have people calling it by it's correct name, Firewalling

    37. Re:I don't get it by nzkbuk · · Score: 1

      it's swings and roundabouts, ISP's don't provide additional addresses, or additional connections because they can charge for that, and they don't have enough address space to allow every user multiple public ip's. Read the specs for ipv6. Every isp is advised to route an ipv6 /64 to each customer. from apnic (asia pacific network information center (people responsible for assigning ip's in the asia pacific area) ) Note there are similar for arin, ripe, lanic 5.4.1. Assignment address space size Assignments are to be made in accordance with the existing guidelines [RFC3177,RIRs-on-48], which are summarized here as: * /48 in the general case, except for very large subscribers * /64 when it is known that one and only one subnet is needed by design * /128 when it is absolutely known that one and only one device is connecting. If an isp wanted to be tight then they would find it hard to justify giving less than a /96. even if they gave a /108 you'd have about 64K addresses note a /108 is global prefex:isp prefex:isp space:isp space:isp space:isp space:isp space:you. Most ISP's that are currently offering ipv6 will give a /48 on request (and they have over 64K of them to give out. That's global prefix:isp prefix:your prefix (and 64K other customers for that ISP) Following the numbers specified by the registry above (aka a /64) an isp can still have a little over 4 billion customers (1B = 1000M) (256^4 to be exact) If they go to the /96 then the number is 256^6 customers, if they give just a /108 to a customer then they can have 256^8 (that's about 18,446,744,073,709,551,616) 18 million million. and if they are wanting that many customers I'd be more worried about the state of the planet trying to feed us (not to mention I'm not sure if there is enough space on the planet surface)

    38. Re:I don't get it by nzkbuk · · Score: 1

      http://www.apnic.net/docs/policy/ipv6-address-poli cy.html

      they are looking / reccomending on giving /64's (it's on an address boundry ':')

    39. Re:I don't get it by Anonymous Coward · · Score: 0

      Did you know that Skype routes other people's traffic through your connection, b/c they are behind a NAT? Two NAT'ed boxes makes it impossible for mere mortals to connect to each other.

      Ever heard about udp hole punching? ... quoting skype technology wrong doesn't make you look smarter ;)

    40. Re:I don't get it by nmg196 · · Score: 1

      Err, 32? It's going to be more like millions per person (if you want them).

    41. Re:I don't get it by nmg196 · · Score: 1

      > It allows you to make direct connections from any computer to any other computer connected to
      > the Internet.

      No it doesn't. Firewalls prevent that - and IPv6 does not remove the need for firewalls. IPv6 does not provide a way to miraculously tunnel through firewalls.

      > It's just that Skype wouldn't need to use the kinds of ugly kludges they do now to get
      > around NATed users.

      Yes they would - for the reason stated above. I do not know of even one single ISP that uses NAT for broadband users. The main problem is firewalls - not NAT.

  27. Oops, I almost forgot! by Nichotin · · Score: 2, Informative

    With sixxs, you get a /48-subnet, which should be sufficient for your quadrillion machines. The address I have looks something like this: 2001:770:11e::1, which is a short for 2001:0770:011e:0000:0000:0000:0000:0001. Luckily those zeroes can be shorted to just ::, which makes these addresses pretty easy to remember, actually. You can also have a bit fun, if you wish, by having e.g. 2001:770:11e:FFFF:DEAD:BEEF:DEAD:BABE :)

    If you are bored some day, give the tunnel stuff a try, instead of sitting in your underwear drinking cola and multitasking irc and quake4.

    1. Re:Oops, I almost forgot! by Anonymous Coward · · Score: 0

      But....I would rather drink cola and play quake4 in my underwear.

  28. Re:service? by Soybean47 · · Score: 3, Funny

    Oh, you know what they're talking about. Billions and billions of devices to "service" you. Ever increasing "penetration." What, you think this guy is wrong aobut the future of the internet? ;)

  29. Routers and Local Network Addresses by trianglecat · · Score: 1

    I didnt RTFA but... I thought that this was pretty much a moot point with the widening use of routers and NAT. A single external IP to your router that dishes out local network IPs to your coffee pot and your fridge and whatever else...

    Can someone explain the value of IPv6 beyond that?

    1. Re:Routers and Local Network Addresses by Anonymous Coward · · Score: 0

      To you and the others that didn't read the article (but at least you admit it):

      Nat dose allow to join multiple machines, but to run peer 2 peer, (or to host anything from any device on that network) you need to tell your router to punch a hole to that device.

      Even in the coffee pot example, you might really want a cup of coffee when you get home, so before leaving the office you could connect by https login and tell it to brew, with ipv4 and a nat router you need to set up the nat to let the connection to the coffeepot. and if you have multiple coffee pots on the network remember what non standard port you need to connect to. While with ipv6 you can go directly to the coffeepot without additional configuration.

      Now granted instead of IPv6 I could make some new protocols for dns entries and nat routers so that I could automagicly make it so that coffeepot.mydomain:443 points to : .. but really the ipv6 solution is better defined.

      The other problem with IPv4 is there is quickly becoming more people/groups on the internet than ipv4 address space. (its one thing to say that my household needs to hide the coffee pot behind a nat router.. but to say I my household cant use any p2p technology as free VoIP because I'm behind the same nat as other households and can't make an incoming whole is problematic.

    2. Re:Routers and Local Network Addresses by queenb**ch · · Score: 1

      First off, this isn't about your coffe pot or your fridge. It's about entire countries. It's not really a problem in North America and Europe. We have plenty of IPV4 address space. There is no real pressure for us to convert. Why fix it if it ain't broke? The problem is that it is not broken here. It's broken every where else, and broken rather badly. There is a significant "black market" in IP addresses. Blocks of IP space, Class B's and Class C's, sell for significant amounts of money. I haven't seen a Class A up for grabs in ages. This adds greatly to the cost for other countries to bring their users on line so that they too, can play in the digital marketplace. IPV4 is about haves and have nots. The IPV4 standard has unintentionally created huge groups of "have nots" simply because they have come to table a bit later than the rest of us.

      Asia, Africa, Central & South America, as well as most of the Carribean and Pacific Islands are still not well represented on the Internet. Here in North America, the university that I work for holds more publically addressable IP space than the entire country of China. In answer your next question, no we are not willing to give it up, because we actually use it in ways that NAT, etc. would likely break. IPV6 is designed to address these issues and still leave us with plenty of room to grow.

      In answer to your question, NAT'ing entire countries simply isn't technically feasable. Many of you who are asking "Why bother with IPV6?" are the same people who bash China for controlling what their citizens are able to view on line. Why place yet another tool (i.e. NAT) which can be used to restrict the flow of information in the hands of such a goverment?

      2 cents,

      Queen B

      --
      HDGary secures my bank :/
    3. Re:Routers and Local Network Addresses by Big_Al_B · · Score: 1

      I thought that this was pretty much a moot point with the widening use of routers and NAT.

      No, for one thing, routers themselves don't do anything to limit IPv4 utilization. They just keep a table of known IP network destinations and forward traffic between interfaces based on that table. Not all routers have a "extenal" side and a "local" side. I have routers in my network that have thousands of interfaces and that switch many 100s of megabits every second of every day. On those routers, there is no concept of internal or external, and there is _no_ NAT.

      I believe you're thinking of one sort of router, that sits on the network edge between a service provider (probably broadband) and service customer with a single publicly routed address doing network and port translation for a local network. Many home network users have this sort of router , but most of the routers that comprise the internet itself don't operate that way at all.

      NAT is not a perfect solution to IP address utilization either. For one thing, it can break some very significant protocols and applications such as VoIP, video and IPSec. How?

      Some features in those protocols bury important IP address information in parts of an IP packet that NAT ignores. Thus, the translated address is used to route the packet across the internet, but the end application breaks when it tries to use the untranslated address found in the buried information.

      Secondly, NAT doesn't keep the internet routing table from growing, which is a problem for core internet providers. When I started in this field less than a decade ago, there were under 75,000 routes to other networks in the public internet, now there are almost 175,000. That's a 100,000 more paths to add, remove, or change as links go up & down from moment to moment around the world. That takes more memory and processor than most can currently afford.

      IPv6 by policy, keeps a hierarchy of IP address assignments, which drastically limits the number of routes seen globally. Currently, IIRC, there are less than 20,000 routes globally.

      IPv6 helps limit the need for NAT as we know it today, because with 2^64 addresses, we could practically give every molecule on this planet its own unique address.

  30. IPV6 by Zlib+pt · · Score: 3, Funny

    In other news, a door in germany refuses to open because some script kiddie got it's IP address and crashed the door. Officials are trying their best to open the door but they suspect the door has to be rebooted.

    Are this going to be the news from the future?

    1. Re:IPV6 by ichigo+2.0 · · Score: 1

      Officials are trying their best to open the door but they suspect the door has to be rebooted.

      Yeah, rebooting is a bitch in the future, ever since Microsoft started replacing the power buttons with retina scanners and started using fusion batteries as the power source. ;)

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

      That's a scene from Ubik by Mr Dick, a really funny bit where the door won't let him out of his own house because he owes it money and other doors say he has bad credit. In Dicks capitalist distopia not only are all things networked together they are AI's and form relationships with their users. In the future your IP6 coffeepot is going to sulk and not swich on because the RFID tags will grass you up and tell it you bought el cheapo beans instead of decent stuff.

  31. afraid of change by felto · · Score: 1

    It seems to me most of you are just afraid of change. I personally welcome it. Of course I don't see why we can't see different proposals, it is always nice to have choices. What is so bad about having more IP addresses? Yes, it's a little more complicated, but hey it could be fun. I am sure most of you where scared when a masked man in leather walked in with duct tape, pliers, and a watermelon, but you get used to it after awhile.

    --
    ...None because fish don't eat ice cream
    1. Re:afraid of change by Anonymous Coward · · Score: 0

      Of course I don't see why we can't see different proposals, it is always nice to have choices...

      Uh, because the proposals phase was in the mid-to-late 90's?

    2. Re:afraid of change by Anonymous Coward · · Score: 0

      so no better ideas have been made sense then?

  32. Re:Population by Carbonite · · Score: 2, Informative

    Even though we do have a lot of people on the planet; I seem to recall that the population on the planet actually declined in the last 10 years.

    Where the heck did you get that information? We've added 750 million people in the last 10 years.

    Take a look here http://www.census.gov/ipc/www/worldpop.html/

    1995 5,694,418,460
    2005 6,451,058,790

    --
    ich muß mehr Kuhglocke haben
  33. I'll believe in IPv6 "penetration"... by Urusai · · Score: 1

    ...when HDTV and digital broadcast become a reality. Right after the metric system is adopted.

  34. Why IPv6 Is Coming by Tony · · Score: 4, Insightful

    To all o' you people asking, "What does it give me?"

    It gives you nothing. You're already on the internet.

    IPv6 is going to give India and China and other high-populous countries connectivity. As it is, they don't have enough IPv4 addresses even to *nat* their country, let alone to provide real services with which NATing interferes.

    And that's why you and I have very little say about the adoption of IPv6. It's gonna happen, and it's gonna happen soon (say, the next 5 years, tops). Pretty soon, those of us who remember IPv4 are going to be like 3-digit /. users-- old, out-of-date, and constantly reminiscing about the old days.

    --
    Microsoft is to software what Budweiser is to beer.
  35. Maybe I'm just a Sick Twisted Freak by krgallagher · · Score: 3, Funny

    When I read "But there are not only people. There are things. Billions and billions of devices that will service these people." I immediately invisioned billions of internet enabled sex toys.

    --

    Insert Generic Sig Here:

    1. Re:Maybe I'm just a Sick Twisted Freak by grimJester · · Score: 1

      No more than the rest of Slashdot. The difference is, most of us are afraid of a future where billions of Sony Sexbots (tm) roam the streets searching for analog holes to plug.

    2. Re:Maybe I'm just a Sick Twisted Freak by DavidD_CA · · Score: 1

      You know, you may be on to something there. If the porn industry was behind IPv6, we'd have it up and running globally in under a year.

      --
      -David
    3. Re:Maybe I'm just a Sick Twisted Freak by Jerrry · · Score: 1
      most of us are afraid of a future where billions of Sony Sexbots (tm) roam the streets searching for analog holes to plug.
       


      So it can install its rootkit? ;-)

  36. Your easy solution is not so easy. by Nichotin · · Score: 1

    You will have a hard time making people give up their subnets, if your plan requires that. Another thing, actually paying for a public ip is what we want to avoid. I would certiantly love to have a huge subnet for free, instead of paying a two digit sum of money each month for one static ipv4 ip.

  37. Coming soon... by Anonymous Coward · · Score: 0
    "By 2050 we will be nearly 10 billion people. But there are not only people. There are things. Billions and billions of devices that will service these people..."
    ... then rise up -- crush them!
    Article has style of a good movie trailer.

    "Gee, I guess we better take up all IP addresses before the machines get 'em!"
    "What are you talking about? They're just machines!"

  38. Address space not the biggest feature by jgold03 · · Score: 3, Insightful

    Address space isn't why we should gloss over IPv6. Yeah, its nice that we can get rid of NAT, but the bigger deal is virtual circuits. IPv4 can't handle streaming data, keeping us from high-broadband technologies like TV-over-IP. IPv6 was designed to optimize routers for doing high-broadband transfers. That should be the biggest selling point of IPv6.

    1. Re:Address space not the biggest feature by Anonymous Coward · · Score: 0

      Address space isn't why we should gloss over IPv6. Yeah, its nice that we can get rid of NAT, but the bigger deal is virtual circuits. IPv4 can't handle streaming data, keeping us from high-broadband technologies like TV-over-IP. IPv6 was designed to optimize routers for doing high-broadband transfers. That should be the biggest selling point of IPv6.


      BS. The QoS mechanisms used in IPv6 are EXACTLY the same as those used in v4 (RTP at the transport layer, RSVP for per-flow reservation state, DiffServ, yadda yadda yadda). Who marked this Insightful??
  39. g0AT seX by Anonymous Coward · · Score: 0

    im more worried about g0at sex on the internet than this shit. fuck you

  40. Big Brother? by thealsir · · Score: 2, Interesting

    Implanting an RFID chip in everybody with a unique address makes it a very easy way of tracking people...and explains why IPv6 is being pushed so hard even though it is unnecessary. Sure, NAT will handle boatloads of expansion to come, but it offers a layer of anonymity to computers behind the NAT...security through obscurity...how many 192.168.x.x addresses are out there? This way, a unique IP can be given to each computer, more unique even than MAC addresses. And it can be reached around the world. If Those Above get their way through, I see computers eventually having hardcoded IP addresses. And RFID implants with a unique IP address for everybody.

    --
    Do not downmod posts "overrated" simply because you disagree with them.
    1. Re:Big Brother? by Anonymous Coward · · Score: 0

      The tracking comment has already been discussed. A personal IP would still have to be dynamic as you move, because the routers still need to know where to send the information.
      Beyond that, if your fear that the "Big Guys" really wanted it was valid, you'd be seeing legislation-and would have seen legislation years ago- enforcing a change to IPv6. As it stands, no such thing has happened and no progress has been made.
      Paranoia will destroy ya. Go put on your tin foil cap, and hope for the best in the mean time.

  41. Re:Population by MrNougat · · Score: 0

    I'd better get one of those life insurance policies with the robot clause, then. I need to protect my family from financial obligation when the robots come for me.

    --
    Web 2.0 == Giant Blogspam Circle Jerk
  42. Billions and billions by gasmonso · · Score: 3, Insightful
    "Billions and billions of devices that will service these people."

    Ah yes, in the immortal words of Carl Sagan

    gasmonso http://religiousfreaks.com/
    1. Re:Billions and billions by orospakr · · Score: 1

      Carl Sagan never said "Billions and billions".

  43. For you, nothing, for the connectivity of things, by crovira · · Score: 1

    a whole lot of things.

    Right now on the internet, "no one can tell you're a dog."

    With IPv6, we'll be able to tell that you are "Spot, a lab collie mix owned by Fred C Mugwump of 123 Fourth avenue, Anytown USA" and that you should not be trying to email anyone about viagra.

    Think of it as the death of Spam.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  44. The most important change by Thomas+Charron · · Score: 1

    The most important change will be the fact that, when we finally actually do start transitioning to IPv6...

        Hell will have frozen over.

        Widespread adoption has been 'any time now' for years now..

        Blah.. Just think, ipv6 gets adopted, and suddenly, all those girls who looked at the fat guys will regret saying, 'When hell freezes over'..

    --
    -- I'm the root of all that's evil, but you can call me cookie..
  45. I am surpised that Broadband ISP have jumped. by LWATCDR · · Score: 2, Interesting

    Think about it. Almost every broadband ISP offers a "home network" package where they charge you extra for extra computers on the connection. However everyone else on the planet is selling easy to use broadband routers to do it on the cheap. If every device gets an IPv6 address then you can bill them very easily for all those extra computers on that DSL line.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:I am surpised that Broadband ISP have jumped. by ehrichweiss · · Score: 1
      Well, seeing as how I used to manage an ISP, I can tell you that IP addresses are like gold. They surely aren't free to us, why should they be free to the end user?

      Have you ever tried to use a VOIP connection over one of those "easy to use" broadband routers? I'm experienced and I still can't get a friends Belkin to work. Now, try setting up two of them on the same IP. I'll rent you the gun and sell you the bullet cause you'd sooner kill yourself than deal with it usually.

      IPv6 doesn't rule out the use of routers and private subnets, AFAIK, just widens the numberspace, so what's your point again?

      --
      0x09F911029D74E35BD84156C5635688C0
  46. i dont' think so! by jaimz22 · · Score: 1

    "Currently we have less than 50 percent world-wide Internet penetration"

    No sir, alot more of the internet is penetration, well i guess he could be right if he's not including softcore...

  47. Why NAT is so bad by TallMatthew · · Score: 4, Interesting

    If you've ever tried to implement an IPSEC VPN with numerous endusers that have DSL/CableModem gateways that default to 192.168.1.x, you'll know why NAT is so bad, particularly if you're using that address space internally already. Granted, there are workarounds to this.

    That's dicey, but what's even more dicey is trying to interconnect corporate networks that use the same private address space. Companies that run virtual trading floors, for example, offer private line connections. You end up with multiple IP subnet conflicts and it's an incredible headache. That having been said, there are workarounds to that, too.

    When NAT became popular way back when, I was part of a few really painful reIPing projects. The reason we went to NAT was because there was no way to get portable IP space and our ISP was being a complete dick, jacking their prices and refusing to run BGP with us. Moving to NAT meant portability and portability meant our ISP couldn't dick us. If I was to move away from NAT and put v6 addresses in my corp network, that's what I'd worry about more than anything.

    1. Re:Why NAT is so bad by Anonymous Coward · · Score: 0

      the whole point of ipv6 is that it's easy to get an address space, and not have to dick around with your ISP at all. Hell, if I can own a /48 being a nobody end-user, your corporation should have no troubles at all.

    2. Re:Why NAT is so bad by Anonymous Coward · · Score: 0

      You don't need to run BGP with your ISP to have portable public address block. I know I work for a telco and I did just that.

      Client XYZ had a public IP block registered with ARIN. We just need to add that block to our RADB record so that other BGP peer on the Internet accept our route. (ISPs are not dumb, they just don't believe whatever the BGP peer sends them).

      Then it is just a matter of routing/bridging that block on some access/aggregation router. There you go, the client moved his private block to us without running BGP. You only really need BGP if you have redondant internet connection to separate BGP AS.

      On the downside, I have no idea how hard it is to get a block from ARIN. You have to explain why you *NEED* it.

    3. Re:Why NAT is so bad by nzkbuk · · Score: 1

      If you really wanted ipv6 there are places like 6bone who will route globally accessable blocks to your gateway

  48. Why the jump in version number by peterpi · · Score: 1

    Why have we gone from version 4 straight to 6? Is there such a thing as IPv5, and if so, how does it differ from versions 4 & 6?

    1. Re:Why the jump in version number by joecr · · Score: 1

      I beleive it is because IPv4 has four octets & IPv6 will have 6 groupings. I've heard different stories as to what the groupings are going to be for IPv6.

      Besides they have done it before, for example when Netscape went from version 4.* to 6.*. So this has actually happened before.

    2. Re:Why the jump in version number by Sir+Pallas · · Score: 1

      IPv5 was an experimental stream protocol.

    3. Re:Why the jump in version number by ichigo+2.0 · · Score: 1

      IPv5 was just IPv4 with 64-bit addresses. Wikipedia is a useful thing indeed.

  49. bs by Anonymous Coward · · Score: 0

    ipv6 will never happen. ive heard this same bullshit story for YEARS AND YEARS AND NOTHING HAS EVER COME OF IT. NO MAJOR ISP'S, CONTENT PROVIDERS AND END USERS EVEN HAVE PLANS TO IMPLEMENT IPV6. IF YOU SAY OTHERWISE YOU ARE A LIAR.

    no one cares what they do in foreign countries. the real internet is in the united states.

  50. In fact, I would think of the metric issue by WindBourne · · Score: 4, Interesting

    Back in the 70's, President Carter was going to move us to the Metric system. Road signs were being converted to mph/metric, goods were dual marked, etc. The idea was to make the conversion in 1981. Then reagan came in and stopped it. America was nearly ready, but it was stopped. Now, we are just about the only nation that does not do metric. That means that special labeling is done just for us. That also means, our goods are more expensive. Sadly, at this point, we have raised several whole generations without as much metric as we had in the 60's, and 70's. When we decide to finally change, it will be expensive and hard. reagan's choice was very short-sighted.

    Right now, is the time to switch. In the future, it will only be more expensive esp. as small devices get IPs. They will also have to be switched. Finally, a new wave of software development could take place with IPv6, that is more difficult to do with IPv4. Not siwtching is very short-sighted.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:In fact, I would think of the metric issue by kotj.mf · · Score: 2, Insightful

      Bingo. This isn't like some company deciding to forgo upgrading MS Office every two years. This is like deciding to run Cat3 in your house, instead of 5e or 6, because you've currently only got a 100Mbit hub.

      --
      hang brain.
    2. Re:In fact, I would think of the metric issue by rcamera · · Score: 1

      isn't it more like deciding to keep your cat3 wiring which is already in place instead of rewiring with cat[56]? if you have a 100Mb hub and wiring capable of up to 100Mb transmission and nics capable of up to 100Mb transmission, why would rewire for 10Gb? seems like a waste of time|money.

      --
      Wave upon wave of demented avengers March cheerfully out of obscurity into the dream
    3. Re:In fact, I would think of the metric issue by Anonymous Coward · · Score: 0
      That means that special labeling is done just for us. That also means, our goods are more expensive.

      My guess would be that *everyone* pays part of the cost for our special labeling (the cost is spread to all of a company's customers).

      Just like how customers who pay cash subsidize those who use a credit card. (They both pay the same price at the register, but the credit card company gets a slice of those sales.)

      Yeah, this is tangential to your primary argument about how being different from everybody else is Bad(TM).
    4. Re:In fact, I would think of the metric issue by Trailer+Trash · · Score: 1

      That means that special labeling is done just for us. That also means, our goods are more expensive.

      LOL! What a loon. Our goods are dirt cheap. Look, my wife is from the Philippines. I know people like you never get out of your parents' basement, so let me explain this to you in simple terms. A worker at Jollibee gets PHP20/hour (PHP is PHilippine Peso), and a regular value meal is around PHP90. So, if the worker wants to eat there, they work 4.5 hours just to pay for the meal. Compare that to here where McDonald's pays US$7/hour and the meal is US$4.50, about, oh 35 or 40 minutes of work. It's not a fair comparison since the meal at Jollibee is about 2/3 - 3/4 as much food as what you'd get here in a meal.

      Minimum wage there is PHP220/day, I think. That's about US$4.

      I have no idea what you think is expensive, but, buddy, you have no fucking clue.

      Sadly, at this point, we have raised several whole generations without as much metric as we had in the 60's, and 70's. When we decide to finally change, it will be expensive and hard. reagan's choice was very short-sighted.

      Bullshit. We wouldn't save any money by changing all of our signs to metric. Instead, we would waste a bunch of money to "upgrade" a lot of signs that don't need it.

      Look, what the metric system does is give us units that are easily converted. So, a meter is 100 centimeters, etc. Our English system uses powers of 2 and 3 instead of 10. But there's a major difference. The units of measure in the English system were chosen for convenience, not because they happen to be a multiple of 10 larger or smaller than something else. I've always said that if you want to get people to use the metric system, make a metric "foot".

    5. Re:In fact, I would think of the metric issue by cpeterso · · Score: 3, Funny


      Does your wife still work at Jollibee?

    6. Re:In fact, I would think of the metric issue by nzkbuk · · Score: 1

      The units of the imerial system were never "chosen for convenience", they were created out of royal decrees and later fudged to fit other measurements that were bigger eg inches to feet to yards to miles.
      Miles were 'invented' by the romans it came from the word milli (meaning one thousand) and was used to measure 1000 standard paces. The legions even had special solders trained to walk in standard paces.
      Inch: At first an inch was the width of a man's thumb. In the 14th century, King Edward II of England ruled that 1 inch equal 3 grains of barley placed end to end lengthwise.

      Yard: A yard was originally the length of a man's belt or girdle, as it was called. In the 12th century, King Henry I of England fixed the yard as the distance from his nose to the thumb of his out-stretched arm. Today it is 36 inches, about the distance from nose to out-stretched arm of a man.

      As you can see none of it was chosen for convenience (at least as far as conversion of units is concerned).
      The chineese based their system of measurement on sound, more specifically the sound of a bell ringing. Then all their measurements came from that (the volume in the bell, the length of the string to the ringer part at the bottom, the weight when made from a spcific material (bronze I think) )

      The whole point is that the imperial system of measurements isn't even standardized over the globe today. US and UK gallons are an example, the pint is another. Metric is not only standard, but the units of conversion are all quite easy even when converting from things like lengths to area, to volume, or from one form of energy to another (eg kenetic to thermal)

    7. Re:In fact, I would think of the metric issue by mikefe · · Score: 1

      This is like deciding to run Cat3 in your house, instead of 5e or 6, because you've currently only got a 100Mbit hub.

      Unless you are using all 4 pair, you are stuck at 10Mbps.

      --
      There: Something at a specific location.
      Their: Owned by someone.
      Please make sure your english compiles.
    8. Re:In fact, I would think of the metric issue by Trailer+Trash · · Score: 1

      As you can see none of it was chosen for convenience (at least as far as conversion of units is concerned).

      You just proved me right. I never said the conversions were created for convenience, just the units. The metric system has convenient conversions at the expense of inconvenient units.

      For scientific measurements, the convenient conversions of the metric system win every time, and in fact that's what we use (note, for instance, that the "volt" is a metric unit). But if I need to measure something around the house, which for most of us constitutes 99.99999999% of all measuring that we'll do in our lives, English units win every single time due to the convenience of the units.

      Thanks for playing.

    9. Re:In fact, I would think of the metric issue by Trailer+Trash · · Score: 1

      Does your wife still work at Jollibee?

      She worked as an RN making PHP5000/month, about US$120 at the time. It would take an entire year's salary just to afford a plane ticket to the US.

      But, have no fear, she lived like a queen because the Philippines uses the metric system so everything there is just dirt cheap. The rent is comparable to your parents' basement...

  51. Billions and billions of devices that will service by Abuzar · · Score: 1

    Yes, yes, we already have these. They're known as 3rd world labor to some and child labor to others. I suppose they will be needing their own IPs to report productivity? Perhaps direct links to Hyperion backends of multinationals?

  52. UN: 50% of the world has never used a phone by sanferrera · · Score: 1

    and you want to hype that IP6 will achieve global connectivity??

    1. Re:UN: 50% of the world has never used a phone by ichigo+2.0 · · Score: 1

      IPv6 would be useful for using phones in a p2p mesh network, thus getting rid of money leeching operators, and making phones more affordable. No point in building oldschool landlines in developing countries, when there are better technologies available.

  53. Most important change by Phronesis · · Score: 2, Funny

    Under IPv6 the internet will surf you.

  54. Consumer Driven by el_womble · · Score: 4, Insightful

    Of course companies and academics don't want IPv6 they already have the only real advantage it provides - per machine addressing. Why would they invest money to get something they already have?

    IPv6 benefits individuals. It benefits P2P, VoIP, photo sharing, blogging and email (yes email - you don't need a third party server if you have a permanent web presence). Yes you can have all of that with IPv4, but its held together with hacks like NAT, port forwarding and man-in-the-middle servers. That's fine, if like me, you hold a degree in computer science and arn't put off by the nuances of network security, berkley ports and subnet masks but if you're a noob who just wants to share their Christmas pictures with friends and family its a pretty steep learning curve.

    I'm a pretty typical nerd. My home network has 4 computers that regularly connect to the internet. Of those, 2 offer services such as SSH, bittorent, email and my testing web server. After christmas that will probably extend to a new XBox360 and a PSP (admittedly passive net users). Next Christmas it might be my mobile. The Christmas after that my espresso machine will probably be consulting a distributed database to see what is the best way of brewing Co-op's Fairtrade Java.

    You can buy a computer the size of a pack of gum with a complete Linux operating system and enough horse power to run a web server for ~$200. That's too expensive to be ubiquitous but in 2-3 years time that figure will be in the region of $20 and it will be a WiFi network. It's going to happen.

    IPv4 forces our devices to be passive because configuring a NAT Router and Firewall is hard for Joe Public. IPv4 means that we have to poll to get system updates. IPv4 means that I can't just ask my fridge what its contents are without configuring a seperate box. IPv4 means that I'm happy when a third party agrees to handle my communications - I actually ask them to listen in and they 'promise' not to read my mail or listen to my conversations. IPv4 means that when I get an email from my girlfriend at 195.95.195.94 I have no method of authenticating that.

    IPv6 means that I buy bandwidth and nothing else. I don't get 100MB of web hosting, or a whopping 5 emails addresses, I get to use my over powered desktop machine with 200GB of 'web space' and as many email addresses as I please. IPv6 means that I can start to build a web of trust, so that I can start to authenticate the messages I receive against a web of my peers - not a single verisign certificate. IPv6 means that consumer electoronics can be connected to my data pipe and that the manufacturer can be responible for its up keep - including firewalls and virus protection.

    In short IPv6 allows people to own a bit of the internet and say it's theirs rather than renting an inch and getting kicked off that inch every 4 hours.

    --
    Scared of flying, pointy things snce 1979!
  55. I want to Move by Nevynxxx · · Score: 1

    Ok, so I run a network. Lets say I want to move my internal network to IPv6. Where do I start? What do I do? How do I check that my switches/routers are capable of it? So I only have 100 pcs on my network, I don't care! This is not a rehtorical question, I have googled.

  56. You don't understant the Internet by swillden · · Score: 4, Informative

    The ONLY machines that need actual IP addresses are servers and gateways. PERIOD. Everyone else can be NATted.

    Sigh.

    The problem with this statement is that it presumes all content comes from central servers. But that's not what the Internet was designed to be, and forcing it into that model will severly retard, and in many cases simply destroy, all future innovation.

    The Internet was designed as an endpoint-to-endpoint communications medium. The intelligence is at the edges, every device on the network has equal access to every other device, none are "special". In practice, of course, 72.14.207.99 (one of Google's servers) *is* special, recieving many more connections than most other addresses, but that's an emergent phenomenon, not one that's designed in. It's only special because lots of other devices *choose* to talk to it. One day they could all choose to begin sending their search requests to some sort of massive, distributed, peer-to-peer search engine (I don't think so, I think it makes sense to centralize search, but perhaps there's a really powerful distributed indexing and search algorithm that no one has yet discovered).

    There's huge power, flexibility and opportunity in that model. We do a lot of things using the Internet now, in 2005, but it's still in its infancy. We have no idea what other kinds of communications technologies will arise or what sorts of things people might come up with to do with this medium ten, twenty, fifty years from now. That means it is critically important for the future of technology and innovation that we preserve the ultra-flexible model that the really bright guys at DARPA came up with.

    End-to-end delivery. Intelligent endpoints. Dynamic, multi-path routing. No central control. Those are the characteristics that turned the Internet from a lab-based curiosity to such a worldwide phenomenon that we seriously talk about how it will one day touch every human being on the planet. Think about it. The Internet looks poised to become the *single* communications medium used for all electronic communications, be it text, audio, video. What is it that made this such a powerful medium? End-to-end. PERIOD.

    Let's not throw it away before we even find out what we can really do with it.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    1. Re:You don't understant the Internet by Anonymous Coward · · Score: 0

      Not to mention, you MORON... i want to see you even try to download content you may or may not find if this is done. *snorts disdainfully* imagine 1 million aol users all on a NAT connecting through ONE gateway... YAY-my download is going at 0.0000045 B/s

  57. I disagree with all of your points. by Anonymous Coward · · Score: 0

    I disagree with all of your points.

    * You don't want your staff to have direct external access and don't want to have to limit this with firewall rules (i.e. you want it done by the nature of the network not by the configuration of the network devices).
    yeah, ip4 is good if you want to play China and control every step of your worker bees.

    * You don't want any incoming connections.
    Why would you want that? The phones of the workers allow incoming connections, why not the computer? How do you want to implement a real voice-over-ip system when people can't be reached from outside?

    * You don't want the possibility of some junior tech bodging the firewall and opening your network wide open by removing filtering.
    Human error exist no matter which implementation you chose. No argument.

  58. Cost Who Pays? by u16084 · · Score: 0

    Take into consideration how meny routers,switches,servers exist on the net. The ENTIRE infrastructure has to be wiped. (very expensive)
    Its not a "Flip the Switch" scenrio here,
    Even my crappy linksys router will need a firmware upgrade (which is already available) I just cant see a hardcore Aol user flashing firmware, untill he looses his connection because hes still using v4 in 2010 (even tho aol will no longer exist then :) )
    So whos gonna pay for all these upgrades?

    --
    -- I Dont Deserve A Sig I Have Bad Karma
  59. Not worth the trouble by sterno · · Score: 1

    Keep in mind that the reason they can make money is by minimizing the support costs. If they have to deal with people trying to run IPV6, they have an entirely new way they have to do things. As for charging per device, why do that? You just charge a rate based on an average usage. If you charge per device people get cranky with you about adding new devices and then they go find a provider that doesn't do that.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Not worth the trouble by zCyl · · Score: 1

      If you charge per device people get cranky with you about adding new devices and then they go find a provider that doesn't do that.

      Yeah, well for that to happen, you also need there to be genuine broadband competition. In much of the U.S., broadband competition is either minimal or nonexistent.

  60. "Things?" by tesseract5d · · Score: 1

    Where do I sign up to be 'serviced' by one of these devices??

  61. He just doesn't get it by Salamander · · Score: 1

    He seems to have a pretty "exotic" view of NAT and P2P, that's for sure. Point by point...

    While waiting for IPv6 to mature, some people decided to design a time-stalling tactic that would ensure IP address space did not run out. This is where NAT comes in. I think NAT worked well to keep the Internet going and it also attracted the telecomms world to adopt the Internet as it gave them "walled gardens" and they were able to sell their IP address space on to customers who had to connect through them. So it has attracted a bigger Internet community.

    Most people didn't adopt NAT for that reason, and in fact wouldn't even know what you meant if you told them about an IP-address shortage. Many consumers use NAT because their ISP would only give them one IP address. That's not going to change going from IPv4 to IPv6 without other structural changes at the ISPs. They're just not set up to track multiple addresses for one customer, no matter what kind of addresses those are. Their databases only have one field for that, and that one field gets used to seed their MAC filter etc. Where's the incentive for them to accomodate this guy's wishes?

    Another reason many people use NAT is for security. Never mind whether they actually achieve greater security; they believe that they do and that reason is distinct from concern over an address shortage.

    When you look at the traffic on the Internet, 72 percent is peer-to-peer, so that is what people want. People think 'I want to send a piece of music directly to a friend. I don't want to pay someone else to do it for me.' At the moment peer-to-peer is facilitated by a server. We need to use that server in order to talk to each other. With IPv6 we won't need that server anymore. We will each have our own IPv6 address open all the time and can decide who to publish it to. We will in effect each become little ISPs and we decide who will connect to us and who won't.

    What part of "peer to peer" doesn't he understand? Why does he think it's called that, instead of "client to server"? The whole point of P2P is that there's no such thing as a server. Also, again, he doesn't seem to understand why people use P2P systems. It's not just about getting content, which we've all been able to do via FTP for ages. It's also about storing multiple copies in multiple locations so that it will still be there despite a failure of a single node, and about finding it in one or more of those multiple locations, and about downloading pieces of it from multiple locations to maximize speed, and about keeping it all anonymous, etc. None of these are addressed by a switch from IPv4 to IPv6. Yes, NAT traversal is an issue that people have to deal with when they adopt P2P, but it's not the reason they did so in the first place.

    It's wonderful that this guy is beating the IPv6 drum, because there are legitimate reasons why we should switch to IPv6. However, he should not let partisanship lead him into misrepresenting the facts.

    --
    Slashdot - News for Herds. Stuff that Splatters.
    1. Re:He just doesn't get it by zrq · · Score: 1

      Many consumers use NAT because their ISP would only give them one IP address. That's not going to change going from IPv4 to IPv6 without other structural changes at the ISPs. They're just not set up to track multiple addresses for one customer, no matter what kind of addresses those are. Their databases only have one field for that, and that one field gets used to seed their MAC filter etc. Where's the incentive for them to accomodate this guy's wishes?

      Black Cat Networks
      http://www.blackcatnetworks.co.uk/services/adsl

      From their web site :
      Our ADSL service is IPv6 enabled; all customers will get a single static IPv6 address allocated to them by default if their equipment can support it. We can also allocate a /48 of IPv6 address space if a customer wishes to deploy it on their internal network.

  62. IPv6 is unlikely to be widely deployed by Great_Geek · · Score: 1

    Prof. D. J. Bernstein has an excellent summary of why he is
    not changing his programs to use IPv6.

          http://cr.yp.to/djbdns/ipv6mess.html

    Basically, IPv6 is *not* compatible with IPv4, it requires a
    whole new parallel system *everywhere* so it will never happen.

    1. Re:IPv6 is unlikely to be widely deployed by Sir+Pallas · · Score: 1

      They are compatible in that you can run them both on the same machine at once. Incompatible would be if you couldn't. If you have an approprite gateway (which exist) you can even talk to the IPv6 address space from IPv4 or to the IPv4 address space from IPv6, so I don't see the problem. As I understand it, some Comcast cable modems take IPv6 addresses for the Comcast internal network and tunnel IPv4 through them. I have a Linode out there that is on IPv4 but that tunnels IPv6 through Hurricane Electric. And the server is accessible to both address spaces. (It also has both A and AAAA DNS records.) I've read that article by DJB before, but it seems out of character for him: he is the one with the brilliant idea to thrash the current email system (which I agree with) but he wants to preserve the old address space? Sure, it takes longer to transition from IPv4 to IPv6 this way, but it's a much cleaner transition when it's done because IPv6 doesn't have to support some of the stupid ideas (that seemed good at the time and only experimentation toppled) that went into IPv4; for instance, the way routing and flow control are handled. Those could not be properly done on an IPv4 hybrid network. And in the end, no one will be tempted to no upgrade just because the networks directly interoperate. (Which, I believe, is what you meant when you said compatible.)

    2. Re:IPv6 is unlikely to be widely deployed by Great_Geek · · Score: 1

      I thought Prof. DJB explained it very clearly in his article, so I didn't go into the details. Since you say you read the article, but still don't understand the problem, I will try to expand on the details.

      The context of all this is the Networking Effect. For example, if I get a phone, I want to be able to call as many phones as possible; which mean if there are competing disjoint phone networks, I will likely choose the biggest one. Things will quickly evolve to a single network that includes everyone. The history of computing and networking is filled with examples of a single (possibly inferior) technology or product taking over the whole market. Some people don't like this, or object to it for philosophical reasons; but that does not change reality.

      In the IPv6 discussion, it is very difficult to upgrade from IPv4 to IPv6. DJB calls it an "Interoperability failure". Since the Internet is the prime example of networking effect, new entrants must be able to talk to the net. Think about it, the point of the internet is to talk to the other systems on the net; why would I do somthing to lessen my reach?

      IPv6 is defined a way that an IPv6 client cannot access an IPv4 web server, this means there is strong motivation for client to stay on IPv4 and not move to IPv6. Similarly, there is strong motivation for servers to stay on IPv4. End result is what is happening now - no adoption. Sure, it is possible to run IPv4 and IPv6 side by side; but why should I?

      There will be no transition until the definition is changed.

      Note that this has nothing to do with the underlying technology. You can say that pure IPv6 is easier/cheaper/faster for the wire/router/switch/stack, that may be true but still irrelevant. You may say upwards compatible mixed IPv4/6 systems are not possible, that still does not change the adoption problem - IPv6 will not be adopted as is. The two facets are independent and any winning solution *must* solve both problems.

      The only way these legacy systems (and IPv4 is nothing but legacy) change is by small evolutionary steps.

    3. Re:IPv6 is unlikely to be widely deployed by cthulhubob · · Score: 1

      DJB may write some decent software, but I'm pretty sure he's off on this.

      I've heard many reports of ISPs offering IPv6->IPv4 gateways for their clients. It's pretty easy to set one up yourself even.

      --

      In post-9/11 America, the CIA interrogates YOU!
    4. Re:IPv6 is unlikely to be widely deployed by Sir+Pallas · · Score: 1

      I understood the problem before DJB and I will understand the problem long after DJB. (As an aside, I do run djbdns and my mail server uses his .maildir format, though it isn't qmail.) The first thing to note is that, as I said, the systems are not directly interoperable. What DJB is talking about is exactly that. What we should note is that you said compatible, which is not the case. I used the correct terminology, the terminology that DJB also happens to use. One thing is left out in his discussion, however: the systems are indirectly interoperable via gateway software; this software (1) exists, (2) swings both ways, and (3) is running on my own IPv4 server, giving it IPv6 address space. The nice thing about the IPv6 address space is that with the same prefix I've been able to give the domains I serve http for different addresses, which means they can all run https without certificate problems ... as long as you access them from IPv6 space. (I believe that this is actually going to be one of the driving forces behind IPv6 adoption.) Another thing to note is when that article was written. Since then, sites like Google and Slashdot, etc, have entered the IPv6 arena. Different IPv6 backbones can now communicate with each other, and it's growing. Many of the problems DJB is describing have since begun to attract solutions.

    5. Re:IPv6 is unlikely to be widely deployed by Anonymous Coward · · Score: 0

      You don't understand him at all. With IPv4 there is no design problems, IPv6 id uding the existing design and adding to it, he is saying its braindead to make something based on an existing design incompatible when its possible to make it compatible without any loss. With email there is design problems, and his plan is not based on the prevous design so he was no choice besides for making it imcompatible.

      He is saying IPv6 is going the way of Plan9, killed by Unix's design being able to do the job as good but surely give it enough time it will happen but this is not the way to handle translations.

  63. The myth about IPv6 by deviate_this · · Score: 1, Interesting

    My biggest problem with IPv^6 is the deliberate hobbling of newer protocols to try and force the move to IPv6 on people. Take SIP for example, which has no built in support for NAT because either 1) they were too lazy to tackle it or 2) they were too arrogant and assumed everyone would just jump on the IPv6 bandwagon just because they were told to do so. The reason there's no rush to v6 is because the internet works just fine right now. What is it about v6 that's going to change the internet experience for my parents? Nothing.

    People have been predicting the depletion of v4 addresses for 5 years now but NAT has changed that. My question is, why aren't new protocols deliberately taking NAT into account so that we don't have to create hacks to get around this limitation later?

    History is full of companies trying to start over from scratch because it wasn't done exactly right the first time, but then end up bankrupt because they didn't stop to consider the most important part: the enduser. How many people are going to want to buy new routers or new dsl or cable modems because they don't support v6? And before anyone says that manufacturers could just offer a firmware upgrade, how many of them are going to do that when they could just as easily use it as an excuse to sell new equipment?

    There might be advantages but all I hear on slashdot are the sheep. How about we talk about the disadvantages?

    1. Re:The myth about IPv6 by Wizarth · · Score: 1

      Excuse me, but you are not correct. I don't know specifically about SIP, but I've been doing some H323 hacking lately, and I can talk about that.

      How is some-one else, without an existing connection to my machine, supposed to connect specifically to one of my home computers? They can connect to my IP address, but thats my modem/router.

      The only way to do it is sit a H323 gatekeeper/proxy on my DMZ. The H323 client thats out there then asks the Gatekeeper to forward the data to the machine named (for example) Larry*. This means I have to have a machine sitting there just to make H323 work right. If this doesn't seem like a work around to you...

      I'm pretty sure SIP supports a gatekeeper function (they do have uses as well, mostly as a directory service). But its a work around, a way to bring seperate IP spaces.

      If we were running IPv6, then the outside machine would be able to make a direct connection to Larry.

      OK, sure, in cases you wouldn't want this to happen, but you can still firewall and such things. But for people who just brought this internet phone thingie because they can make free/cheap calls where ever they can get online over wireless, IPv6 is the only way to go.

      So.. the original point. SIP is probably not, and H323 I can definately say isn't hobbled to not work with NAT. It's because NAT is a bugger of a hack, and the workarounds are an even bigger hack. It'd be kind of like saying why are car engines hobbled not to work on fuel thats 90% water?

      As for the disadvantages of IPv6 ... default lame firewalls allowing too much access to LAN machines, giving internet worms more targets (although the targets are now hiding in a much larger haystack).

      * I do not have a machine named Larry.

  64. Tunnel brokers by dindi · · Score: 1

    Back then there were a few test tunnels, however a quick search revealed, that there are so called "tunnel brokers" online allowing to play around....

    And Voila you have an ipv6 address (most sites will "approve" your endpoint and you need a public IP with ICMP enabled (from the tunnel site)....

    offtopic: i remember ping times being better between 2 macines using ipv6 addresses, interestingly now my laptop pings with bigger latency over ipv6 ...... strange ....

    hmm at the end I will make use of the ipv6 in my kernel that I religiously compile in for the last 5+ years for who knows what misterious reason...

    at least kill time instead of working on that "must finish today" project .... crap

  65. Re:For you, nothing, for the connectivity of thing by Sharkeys-Day · · Score: 1
    With IPv6, we'll be able to tell that you are "Spot, a lab collie mix owned by Fred C Mugwump of 123 Fourth avenue, Anytown USA" and that you should not be trying to email anyone about viagra.
    How long do you think the privacy advocates will allow that to continue?
    Think of it as the death of Spam.
    Spam will continue with 0wn3d machines and forged SMTP headers. IPv6 won't even take a nibble out of spam.
  66. Do you really know what this is? by Cinual · · Score: 1

    IPv6, Exactly how does this work? is it automatically burnt into your NIC like a MAC address? or does it gets it "permanent" address from the DNS? IPv6 isnt all about telling your toaster to start making toaster strudles or changing the temprature in your Freezer. You can do all of this with IPv4. It's called and internal network. and im sure they have the technology to be giving Coffepots and stoves Ip address and MAC address's. I mean they have Stoves now that dont have any hot coils or flames. They are just not putting technology to its full potential. IPv6 is going to be for those who dont yet have internet. making it MORE widley available. but then this problem exists, How are we getting computers and link connectivity to these minor outlaying countries? Is there going to be even people to help them there if they do have problems? I see how we could have Authentication not being a big problem but once again we would have to change Our Os's to be more compatible with Server technolgies.

  67. Nonsense by dpilot · · Score: 4, Insightful

    IPV6 could well be DOA, because it solves the wrong problem.

    IPV6 solves the problems of the Internet, as originally conceived - egalitarian and end-to-end.

    Nobody in power wants that any more. I'm sure that those in power would mostly prefer that the Internet would just go back and hide under the rock it came from, but they DO like the benefits it gives to THEM. If IPV6 goes forward, it'll only be because it has enough momentum as the "logical successor," and because TPTB can't propose what they'd really like.

    If IPV6 were being designed TODAY:
    It would have DRM built-in for the ??AA, as well as router-based monitors and controls for peer-to-peer networking.
    It would have built-in provisions for wiretapping, even at the opportunistic VPN level, for government TLAs.
    It would have content and traffic filtering provisions, for China and the Religious Right.

    Of course IPV6 really runs counter to all of these "design criteria."

    --
    The living have better things to do than to continue hating the dead.
    1. Re:Nonsense by burns210 · · Score: 1
      "IPV6 solves the problems of the Internet, as originally conceived - egalitarian and end-to-end."

      All the more reason for informed geeks to push its adoption and not wait for the big corproations to do it.

  68. It doesn't matter by keithmoore · · Score: 2, Interesting

    The notion of a complete transition is fairly meaningless. We're going to be using IPv4 for the web, email, and dedicated appliances like printers that are hard to upgrade, almost indefinitely. However for those applications the limitations of IPv4 addressing aren't such a big deal as there are fairly acceptable workarounds. IPv6 enables many more hosts to participate in peer-to-peer interactions than before, and this opens up potential for many new kinds of protocols and networked applications.

    As for deployment - Some large ISPs are already selling IPv6 access to commercial customers. Consumer ISPs will be the last to see IPv6 because consumers will be the last to understand why it is useful. But this isn't such a big problem either, as anyone with a static IPv4 address can use IPv6 right now using 6to4 or an IPv6 tunnel broker. Bottom line - if you want to use IPv6 with an application today, there's a way to do it using existing networks and services. What we're waiting for is new applications that make use of IPv6 to do things that they couldn't do with IPv4 (maybe because they couldn't access enough devices that way). I think we'll see IPv6 used to control traffic lights, monitor security cameras, etc. before we see it widely used to transport web and email.

    I use IPv6 every day between home and work. It's what lets me have multiple individually addressible machines at home with a residential DSL connection. My work network now supports IPv6, but my home ISP doesn't. 6to4 solves the problem handily.

  69. What happened to IPV8 (Jim Flemming) ?? by RouterSlayer · · Score: 1

    Whatever happened to IPV8 stuff?

    It would have solved all these issues. totally.

    where is it now?

  70. Re:Population by drinkypoo · · Score: 1

    A number of [reputable] science fiction authors have written about mass suicide due to changes in culture. Sometimes the scifi authors are dead on, I hope this isn't one of those times, no pun intended. Then again, the world could do with a couple billion less people...

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  71. Re:For you, nothing, for the connectivity of thing by deviate_this · · Score: 0

    And you don't see the problem with this? Are you going to sacrifice your privacy for freedom from spam? Let me guess, you're one of the those people who argue "If you have nothing to hide then why do you need privacy?"

    Think of it as the death of privacy.

  72. Re:YHBT YHL HAND..... by ozydingo · · Score: 1

    Your mommy buy you a 'puter for Christmas?

  73. Red Herring by Sir+Pallas · · Score: 1

    All of what you mention can be taken care of at the router in IPv6. Just like in IPv4. (Router is Firewall's oft-forgotten last name.)

  74. mark of the beast by Anonymous Coward · · Score: 0

    The reason China is so hot to trot for IPv6 is that they can track every individual and your little dog too. No more hiding behind dynamic IPs. We know what you did last summer.

  75. JUST DO IT by AviLazar · · Score: 1

    Jesus christ. Every other day some other yahoo (no pun intended) with how IPv6 will change our world - be it good or bad. Will they shut these zero originality, boring ass clowns up? This is not being a troll, this is for real. It's about as bad as my freshman year in college, where 40% of orientation comprised of required day classes about political correctness.

    God, just get IPv6 implemented...if you want to talk about it, stop trying to be- well you know - sounding like you came up with a new idea and actually come up with a new idea.

    --

    I mod down so you can mod up. Your welcome.
  76. I'm confused by penguin-collective · · Score: 1

    "world-wide Internet penetration"

    "Billions and billions of devices that will service these people."

    Which is it--penetration or service? I mean, it's kind of difficult to get both at the same time.

  77. No, not for the coffeepot by TheLink · · Score: 1

    For that, use the .here domain.

    A coffeepot somewhere physically near you would then be coffeepot.here or something like that.

    Given we still live in the physical world it makes sense that we should have a reserved domain to address things that are within a location.

    So whichever place you go to, http://jukebox.here/ should always get you to a jukebox in the general vicinity (if there's one). and http://here/ will give you info about who is providing the network etc, and perhaps point you to other stuff in that area.

    I tried to get ICANN to reserve such a TLD (emailled a few of them), but I'm not rich and don't have USD50K to apply.

    Don't forget the whole idea is to then give the TLD to the world so people can use the TLD in a similar way they get to use the 192.168.x.x and 10.x.x.x and the 172.x.x.x addresses.

    So far ICANN is just interested in creating TLDs that are mostly practically "Yet Another .Com".

    Look up tldhere for more info.

    --
    1. Re:No, not for the coffeepot by bhirsch · · Score: 1

      But that is why we have a default DNS suffix. You don't even need jukebox.here -- just jukebox.

    2. Re:No, not for the coffeepot by spauldo · · Score: 1

      That needs a convention, not a reserved name.

      You'd just need to talk all ISP's and service providers (your coffee shop, bar, restaurant, college, etc.) into adding it to their DNS servers. If every dns server claims that it's authoritative for .here, your idea will work.

      Of course, that requires that they run DNS servers or at least have update access to the DNS server they use. Most of the small firewalls those places use don't have that capability. Still, having .here be a registered name wouldn't help it any.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    3. Re:No, not for the coffeepot by TheLink · · Score: 1

      Yes that can work, but not everyone accepts dns searchpaths from externals.

      If we formally reserve .here, it can still work even if a site doesn't divert dns packets, and the client fetches the address from an upstream server. Because we can reserve an IP for *.here so that if no one else upstream answers for .here you will get that IP, and then devices upstream could answer - whether you get "OEM ROUTER default config" or "Welcome to Blah ISP" is a different matter.

      The company I work for provides an internet access system that even works most of the time if users have arbitrary static IPs and default gateways. So users don't even have to turn on DHCP to get internet access.

      I tried to get interest within my company about this TLD thing, but there's no short-term revenue in this.

      --
    4. Re:No, not for the coffeepot by TheLink · · Score: 1

      Once you have the TLD reserved properly then you can do this:

      At the global level the top level name servers if asked, resolve .here to a reserved IP say 128.0.0.1 (for example ok?).

      Anyone upstream from a client can choose to configure their routers to route 128.0.0.1 to their server.

      So if some place does not configure their access point, maybe you'd see their ISP's page when you visit .here, or maybe you'll see a Linksys ad ;).

      Whereas if a site is intentionally giving unrestricted (no redirection) free and open WiFi, you might see a page telling you about the terms and conditions etc.

      So instead of localhost you have a "localarea" domain and IP. Of course the .here domains don't necessarily need to point to the reserved IP. And for various reasons you might wish to redirect web browsers who visit http://here./ to a FQDN.

      --
  78. What can I do? by Anonymous Coward · · Score: 0

    As a regular nobody, What can I do to help speed the transition?

  79. Lots of IPv4 addresses left by trevorcor · · Score: 1

    Currently we have less than 50 percent world-wide Internet penetration, and we have used most of the address space.

    Um, no.

    Take a look at the IPv4 address space. Over a third of the addresses are still unused.

    Now, I understand that this is a result of the stingyness in handing out IPv4 addresses due to the address crunch -- I'm ready for IPv6 to go mainstream, so the /48 I get from freenet6 will be usable -- goodbye silly NAT hacks! -- but the statement that we're nearly out of addresses is untrue.

    --
    "That's all I have to say about that" --Forrest Gump
  80. Why do all our devices need an IP address? by Daytona955i · · Score: 1

    Ok, I'm not suggesting there's no need to upgrade to ipv6 but why do all devices need their own static ip address? If my toaster or fridge or tv or whatever is network capable, I don't want it accessible to anyone! I'm perfectly happy to have my mythtv box behind my firewall/router and just port forward using ssh when I'm at work.

    The main disadvantage would be if my phone was web enabled because as far as I know I can't get an ssh client for my phone. However, I think a better solution would be to integrate ssh into your programs to access these devices. ie. have a special mobile phone program where you insert your ipaddress (that would be the NAT) and of course the username/password and then say port 80 on local device 192.168.x.x so when I open up my phone mythtv program it automatically uses ssh to connect to it. Nice and secure and my mythtv box isn't exposed. This way I don't have to worry about the latest exploit for apache or upgrading my toaster every month. This way all I have to worry about are ssh exploits.

    This works fairly well for me now, I have two webservers behind my firewall, a general testing webserver where I can test stuff before I upload it to my main webserver and then the webserver on my mythtv box so I can schedule shows while at work. Neiter one are opened up to the internet except the one box is connectable via SSH (port 22)

    To get to the one:
    ssh -L80:localhost:80 username@ipaddress
    to get to the other:
    ssh -L80:192.168.x.x:80 username@ipaddress

    While the total population of the earth may not need an ipaddress right now, it's silly to rule it out completely. If history is any indicator, the population will continue to grow. As more and more people get on the internet, we will find there is a problem.

  81. How is this gonna improve p2p and VoIP? by Anonymous Coward · · Score: 0

    I don't really see how IPv6 will improve peer2peer and VoIP that much like claimed in TFA. I mean I have a static IP address now, and I've had one for many years, same goes for a lot of other people I know. Although these are all 1 IP per house and NATs for the internal network, it's still simple to forward different ports to different computers. I really don't see how IPv6 is gonna make a difference here. I'd appreciate if anyone could give me an example of where IPv6 can do something for me that I can't do now.

  82. I don't want IPV6 by zlogic · · Score: 1

    ...because my D-Link router doesn't support it, its firmware source is closed (no hacks) and D-link will probably force me to upgrade.

  83. Re:Population by Luyseyal · · Score: 1

    Well... it hasn't decreased, though there was a cool study published in Nature a couple years ago that concluded that the world population will probably top out at about 10 billion depending on various factors. This is due to the "adverse" effects of affluence on population growth. Africa is an enormous factor. How Earth's population grows depends a great deal on how African war, poverty, and AIDS turn out.

    -l

    --
    Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
  84. sure... by Anonymous Coward · · Score: 0

    which will come first, IPV6 or harnassing Fusion for power.

  85. Killer app. needed by Anonymous Coward · · Score: 0

    /The problem is mostly social./

    Its mostly an issue of justification: What killer app. makes the change worth any effort? Real* QOS for VOIP, for example, would do it but where is the movement on that?

    *Not QoS over IPv4, but the kind that all ISP's and backbones agree to and offer some level of guarantee about.

  86. A radical approach by Anonymous Coward · · Score: 0

    It a lot of people seem to think that the main advantage of IPv6 is the larger address space. IMHO, that's not much of an improvement, and could be handled without resorting to IPv6.

    President Bush, ironically enough, provided an alternate proposal when he referred to "the internets". There's no really compelling reason why there should be just one of them. He's right.

    Running out of address space? Fine, build another overlapping IPv4 internet (using identical public address space) and interconnect the two. It could be done with a little creativity involving NAT and/or part of the "reserved" or "experimental" IPv4 space to solve ambiguities.

    Yes, we would have to change a few things in IPv4 to make it go. But we'd have to change a lot less than implementing IPv6.

    * There are many good reasons to implement IPv6. Address space is not one of them. And I'm not a Bush fan, by any means. But he makes a good point occasionally.

  87. Shortage creates a market by kickdown · · Score: 0

    Actually, there is a growing market when IPv4 address get short. ISPs can make a whole lot of money by making special offers that give you a static IP, or even a (ridiculously small) subnet like /30. The shorter IP addresses get, the more money can be made out of the shortage. So, I am very sure that there are ISPs that are quite happy with the situation as it is now. The problem is: ISPs are the ones that need to set things up for IPv6, and if they have no incentive, it won't happen.

    --
    Continuous positive slashdot karma since... uh, maybe next year.
  88. What about by Anonymous Coward · · Score: 0

    our system that runs Windows NT 3.51 on Alpha? How do I get that to use IPV6?

  89. IPXv6 is what I'm waiting for... by Anonymous Coward · · Score: 0

    Who cares about IPv6?!? I waiting for IPXv6 to be released! :)

  90. A story by MightyMartian · · Score: 4, Interesting

    "Tell me, Grandpa, what was it like in the days of IPv4?" young Suzy asked as she played with the IP wireless transmitters in her golden locks of hair.

    "Well Suzy," Grandpa said, his mind on the distant past, "back then we only had 32 bit addressing, and much of it was provisioned out to various regional entities, with large corporate interests sitting on whole chunks of the space. We had these things called NAT routers."

    "Sounds scary, Grandpa." Suzy shivered.

    "It was." Grandpa replied. "The first NAT routers could only support FTP and IRC, and folks using some chat programs could barely get their software to work at all. Still NAT did okay, for a while."

    "Then what happened Grandpa?" Suzy asked, enthralled.

    "Well, as I recall, the first problems came when handheld wireless devices became more common. They had to sit behind various other networks, without direct connectivity. Proprietary solutions abounded, and connectivity was in the hands of large corporate communications giants. Everyone knew that IPv4 had been in trouble for many years, but some folks said 'NAT's all we need' while others didn't think there was a crisis at all, and even if there was one coming, it was nothing to worry about."

    "But there was, wasn't there Grandpa?" Suzy knew the best part of the story was coming.

    "Very much so." Grandpa said after a moment. "You see, even with NAT and various other networks between the IPv4 network and the average person's devices, the Internet was growing too fast. The limited supply of IP addresses as beginning to slow the expansion of the Internet. Finally, with the great IP Famine of '18, we had no choice. IPv6 was rolled out. Some folks were mad, because they had put their heads in the sand and refused to recognize the problem had been coming for a while. It costs those people lots of money, and some either had to put up with being stuck behind NAT routers and losing out on new functionality or simply going out of business."

    Suzy laughed. "They were very silly people, Grandpa!"

    Grandpa nodded. "Yes, they were, but most of us survived. Now it's time to go. Don't forget your data glasses and your book tablet. The last flight to Tokyo leaves in an hour, and I promised I'd get you home before dinner."

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
    1. Re:A story by Anonymous Coward · · Score: 0

      Why would the last flight for Tokyo leave so early?

    2. Re:A story by spauldo · · Score: 1

      Tokyo is GMT+9.

      You leave the U.S. today and get there tomorrow.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    3. Re:A story by Anonymous Coward · · Score: 0

      I fear this won't be the last story about Ipv6 on Slashdot. So why do I still read them, will "the need and soon coming uprise of IPv6" become an urban legend?

  91. More things that will change... by aapold · · Score: 1

    We will be able to get GPS callback service for celphones to find out where that person who called you is... Duplicate articles will become a thing of the past on /.... The Houston Texans will win a playoff game...

    --
    "Waste not one watt!" - CZ
  92. Because of DHCP by 955301 · · Score: 1

    We're multiplexing addresses with NAT and DHCP. If everyone's address is permanent, DNS already maps names to addresses. Your IM client would not use a central server, your buddy list entries would map to IPs.

    The list of those with the service is in your adress book. We don't ring the switchboard and ask for LordEd any more, we patch the call ourselves with LordEd's phone number.

    --
    You are checking your backups, aren't you?
  93. Plenty of IPv4 Space Left! by slashfun · · Score: 1


    ....Currently we have less than 50 percent world-wide Internet penetration, and we have used most of the address space....

    We keep hearing this, but what isn't emphasized is that there are over 75(!) class A-equivalent (/8) networks available that IANA is holding in reserve.

    In fact, organizations are returning /8 networks to IANA control and they are not being reallocated.

    Does IANA have an unpublished agenda to force IPV6 upon us?

    --

    Slashmail.org "The Open Source Email Company"

  94. Re:One thing that doesn't work by Mahou · · Score: 1

    you misspelled ginger. but man, yeh, those freaks with their red hair and light skin with freckles. sickening
    uauagh *shivers*

    --
    if i'm not immortal, what's the point of living?
    ...te?
  95. Does it also mean? by jbeaupre · · Score: 1

    Does it also mean that there are so many addresses that unless someone knows your address, they'll never find you? Security by obscurity, if you'll stomach the term. If addresses numbers are scattered enough (random?) then won't it make finding open ports, unsecured services, etc much more difficult for viruses, worms, miscreants, etc by just incrementing IP #s?

    --
    The world is made by those who show up for the job.
  96. economic reasons by hopeless+case · · Score: 1

    Nicely put.

    If I might elaborate on the economic reasons ...

    The economic reasons to change (or enable) will present themselves as consumer services that require IPv6 to run, or that work better over IPv6. Just as with VOIP, these may appear as cheap routers you stick on your home network to enable the service.

    Like, say, home security monitoring services with each sensor having its own IPv6 address.

    As these services become more widely deployed, and as the volume of IPv6 traffic tunneled over IPv4 grows, it will at some point become cheaper for the ISPs involved to support straight IPv6, instead of 6 on 4. At which point, it will be easy to do so, seeing as how every OS will then have mature dual stacks and the IPv4-only hardware will continue to function through 4 on 6 tunnels without ever knowing the difference or having to be touched or configured.

    The IPv6 community has done an excellent job of thinking through these co-existance scenarios. I really don't see what DJB is complaining about.

  97. False metrics by blair1q · · Score: 1

    Address translation has multiplied the effective address space way beyond the 4 billion unique values. The limitation for active connections under IPv4 is 2^32 IP addresses * 2^16 port numbers * number of protocols. The limitation for clients connected and sharing an address and port and protocol is infinity.

    IPv6 will, therefore, vastly increase the number of active connections possible, but security will still demand address translation (really? maybe; anyone want to kibbitz on that?), so the number of unique IP addresses you'll need won't get too big too fast.

  98. IPv6, Dynamic IPs and Anonymity by Anonymous Coward · · Score: 0

    Some degree of anonymity is provided by the dynamic IP addresses handed out by ISPs. Does IPv6 seek to remove this useful aspect? Case in point: a flood-based attack to a given IP can be thrwarted simply by getting a new IP from the ISP (old version of yahoo chat, for instance, makes the user vulnerable to these flood attacks).

  99. Re:Population by Audacious · · Score: 1

    Sorry! You are right. It is an over all decline in the growth rate - not population. Population is still increasing but growth rate has decreased.

    See:Growth Rate for the United States and World Population

    My bad.

    (Although the second site is predicting an upturn in growth rate once the third world countries have become more moderized and then there is a sharp drop off in growth rate once 10 billion people are on the earth. I would think, given that people still only live to be around 80 or 90 that at some point there will be as many people dying as there are being born.

    --
    Someone put a black hole in my pocket and now I'm broke. :-)
  100. WWHFD? by lullabud · · Score: 1

    What Would Harrison Ford Do?

  101. It's about a transition plan by Nicolay77 · · Score: 1

    The protocol doesn't have one. IPv4 addresses should be embedded into the IPv6 address space, and the protocols should co-exist for a while.

    But the IPv6 was designed as a replacement instead of a improvement of IPv4. It's not technical, it's economic, it means that we MUST BUY IPv6 addresses alongside our IPv4 ones. More money for already greedy companies.

    If the address space of IPv4 is put inside the address space of IPv6, this problem is over. Everybody instantly has an IPv6 address, no $$$ needed. This is the real problem with IPv6. Fix it and people will start using it.

    --
    We are Turing O-Machines. The Oracle is out there.
  102. Hey, Fucknut! by Anonymous Coward · · Score: 0

    Rubbish. Firewall is not a security measure. If you have port {whatever this week's virus uses} open, you are just as vulnerable as if you don't use Firewall. Similarly, if you have a public IP and a NAT between you and the Internet which doesn't forward anything on that port, you are secure.

    A public IP with everything other the VoIP and (for example) BitTorrent closed is much more useful, and no less secure than Firewall.

  103. NAT is security. Cracking ISP won't work! by Anonymous Coward · · Score: 0

    The parent says that by cracking the victim ISP router, he could propagate a route to his private subnet. Basically, adding a static route 192.168.1.0 /24 to the public victim's address.

    1) The guy is still protected by NAT because incoming packets won't reach his LAN because the NAT entry won't be in his NAT box.

    2) Private IP (10.x 192.168.x 172.16.x) are not routed on the internet.

    3) Even if the victim happens to be using public address space on his router, the other BGP peer on the Internet will ignore the route advertisement from the cracked ISP router. All decent ISP rely on stuff routing info from RADB.com If the RADB record does not list a particular route a being advertisable by AS X, AS Y will ignore it. You would need to crack RADB and modify the ISP routing info there.

    Even then, NAT will still protect the user. So YES NAT ***does*** security. If no, explain to me what's the difference between filtering using a firewall and filtering with the dynamic NAT entries ?

  104. Funny. by /dev/trash · · Score: 1

    I just bought a 2 Litre bottle of Coke tonite.

  105. What is complete transition ? by Arioch_BDV · · Score: 1

    It would not be earlier that i call IPv6 same mature as current IPv4, than we found ourselves running out of IPv6 addressses and switching to IPv8 :)

    Now, seriously, NAT is not only limiting, it is protecting also. The problem is that we have no ZeroConf or UPnP port forwarding up to an outer gate. If at home my campus network operator allowed me to demand some port - then it would make me easy to send/receive files with jabber, etc.
    I pay per-megabyte, and i guess i i had direct IP, all those port scanning, virus attacks and crackers trying to zombie my PC, would at very least make me traffic i would have to pay 10 times more than now. And perhaps they will find a hole and infect my PC. So i am not that against the NAT. It is limitaition, but it is saving my money also ;)

  106. More than 50% penetration by Sigg3.net · · Score: 0

    If you look at the Western world, we have more than 50 percent penetration.

    Something must be done!
    I refuse to be penetrated!