Slashdot Mirror


IPv4 vs IPv6: The Road Ahead

jeffy124 writes "With the world moving towards having every device under the sun being Internet-connected, is the Internet going to be too large? This article off CNN.com examines this potential situation. They look into the problems of switching networks from IPv4 to IPv6, and the inclusion of inter-operability between the two. Benefits of moving to IPv6 are looked at, but so are the critics of it who point out that if we don't have a problem now, why fix it? While low of technical details, the story points out that not many systems out there currently support IPv6. "

334 comments

  1. Not many systems support it? by JeremyYoung · · Score: 1

    How about the enormous chunk of Linux webservers? Last I read, Linux has supported IPv6 for some time now.

    --

    Go Lakers!

    1. Re:Not many systems support it? by Cymbaline · · Score: 1

      Most all *IX distributions do.

      (sarcasm) But remember! Microsoft rules the world, and won't implement IPV6 in Win XP V2.1/e1 unless it somehow supports MS SNA Server!
      (/sarcasm)

      Waiting 'til its too late sounds akin to Senator Conlin deciding to have his face wiped on public TV by Connie Chung. Smart move.

    2. Re:Not many systems support it? by Anonymous Coward · · Score: 0

      Um. Actually Winxp has IPV6 and so does Win2k (as an addon patch from MS)

      Nice FUD though... Probably tricked a lot of people.

    3. Re:Not many systems support it? by Cymbaline · · Score: 1

      Wasn't ment as FUD - hence the "(sarcasm)" tags. Figured somebody would say it sooner or later; might as well head it off at the pass.

    4. Re:Not many systems support it? by CmdrTaco+on · · Score: 0

      Not to mention MacOS X...

      --

      saru mo ki kara ochiru

    5. Re:Not many systems support it? by Frederic54 · · Score: 2, Informative

      every win32 system can have IPv6 for months using Trumpet TCP/IP stack, even win98, not "only" nt/2k that have ipv6 support from M$ also.

      --
      "Science will win because it works." - Stephen Hawking
    6. Re:Not many systems support it? by ergo98 · · Score: 1

      Wow Trumpet is still around? Is that the same Trumpet Winsock people?

    7. Re:Not many systems support it? by Anonymous Coward · · Score: 0

      But you need applications too!

    8. Re:Not many systems support it? by Koos · · Score: 1
      How about the enormous chunk of Linux webservers? Last I read, Linux has supported IPv6 for some time now.

      Yes, but does your cable or DSL provider route IPv6 ? Do they help you get your own /48 routed to your home if you want it ? I wish my cable provider supported IPv6 and/or multicast.

      And your Linux webserver might have a bit of a problem serving IPv6 clients out of the tarball. Apache 1.3.x still needs a set of patches (available from the kame ftp server). Apache 2.0, still in beta supports it now.

    9. Re:Not many systems support it? by Wouter+Van+Hemel · · Score: 1


      It's true, I see less and less mentioned about ipv6 then -let's say- two years ago. And it IS needed, do you know how hard it is these days to get a few ip-addresses assigned, even for big ISP's? It's 'later' already, and yet I don't see an increasing amount of people using it, even less and less actually. True, most unix systems support it (more or less) now, but are any of them using it? Are there applications that understand ipv6? Not many, as far as I know.

      I seriously start wondering if ipv6 'the next generation' will ever become a reality...

    10. Re:Not many systems support it? by Frederic54 · · Score: 1

      Yes, the same!!! remember Trumpet Winsock 2.0f or 3.0d, now they have IPv? since version 5 I think, not bad, seems a fast stack etc

      --
      "Science will win because it works." - Stephen Hawking
    11. Re:Not many systems support it? by c_g_hills · · Score: 1

      All isps support ipv6*. All you need is to find a 6-to-4 relay router to get your packets on and off the ipv6 backbone. www.freenet6.net for a free /48.

      *not natively

    12. Re:Not many systems support it? by fyonn · · Score: 1

      when you say "supports", you did of course mean "requires" didn't you :)

      dave

  2. Re:fp by robvasquez · · Score: 1

    Might as well just go ahead to IPv8

  3. Not many systems? by mr100percent · · Score: 1

    Come on, Apple, Dell, Cisco, and Linksys have had the capability of IPV6 for years now.

    1. Re:Not many systems? by Anonymous Coward · · Score: 0
      How many more posts do you plan to make in the next hour? So far I've seen tree of yours, all replying to this article!

      Now, if you had something interesting to say...

    2. Re:Not many systems? by Anonymous Coward · · Score: 0

      Oh, I call my posts in this article CONSTRUCTIVE to the conversation. Oh, except this one.

  4. I don't get it... by buzban · · Score: 1

    Most of the office-administered winboxen don't even have their own IP...why would my clothes dryer need one?
    This to me is somewhat like the continuing problem of new area codes...why not go with a main number and extensions for each individual device?
    while the phone infrastructure can't seem to handle this concept right now, Internet devices certainly can....router for the house, and a port for each device (stupid worms...send as many port 80s as you like...they all go to the commode!) ;)

    1. Re:I don't get it... by 4mn0t1337 · · Score: 1
      stupid worms...send as many port 80s as you like...they all go to the commode!

      And you are kept up all night by the sound of flushing water. And then there is the sudden spike in your waterbill...


      You know the Urban Legend about how the water levels drop during half-time at the Super Bowl as everyone uses the bathroom? Well, enter the DDoS atack of the '20s (2020 that is): script kiddies h4X0ring all the toilets in NYC and having them all flush at once.

      --

      ______
      Once: you're a philosopher. Twice: a pervert.

    2. Re:I don't get it... by Sir+Mix+A+Lot · · Score: 1

      This is more or less what NAT does. Instead of assinging a port for each device it assigns one for each connection to the external network. It maintains a table to map the incoming/outgoing messages to the corresponding internal IP/port for each connection. The main number on the public side of the network is assigned by someone, i.e. the IP address that your ISP gives you. Using this method you could map port 80 to nothing and the NAT would dump it. The problem is that if an external person wants to contact a webserver on your side of the network legally they have no means of doing so without you telling them more information than your IP address, specifically they also need to know to use a port other than 80. Combine that with ports for telnet, ssh, etc and you have a lot of annoying mappings to setup and share with people legally connecting to your box. It does fix the IP problem though, assuming that there are fewer than 65536 connections to the private side of the network.

      --

      % rm * .o
      rm: .o: No such file or directory
      % ls
      %
      damn
    3. Re:I don't get it... by CyberKnet · · Score: 2

      "An online electronic device only needs one port!"
      slashdot://buzban

      --
      Video meliora proboque deteriora sequor - Ovidius
    4. Re:I don't get it... by Anonymous Coward · · Score: 0

      What you describe is actually Port Address Translation. Network Address Translation on the other hand substitutes one address (usually all ports) for another. The most common application is connecting private address space to the Internet when you have too few public addresses, or you do not a 1 to 1 mapping of private to public addresses. If you only have 1 public address and many private what you are doing is PAT.

    5. Re:I don't get it... by Anonymous Coward · · Score: 0

      Hey, within the last 18 months, the Colorado Springs Gazette ran a story about how the "tide comes in" during ads in the Broncos games. Really.

      So, maybe the *water level* doesn't drop, but the sewage level RISES!

      Seriously. Dig around gazette.com's archives if you don't believe me.

    6. Re:I don't get it... by Beast+Of+Bodmin · · Score: 1

      Don't forget that it's a strong possibility that
      the telephone systems may move from SONET to IP
      based routing.

      That would be voice over IP, wouldn't it?

  5. The plane is gonna crash by jamirocake · · Score: 1

    I've heard that chanaging the protocol for the internet to IPv6 is similar to changing the motor of an airplane in mid air. Is it really plausible to do that, or is the Internet destined to become a useless dinosaur? (hopefully another kind of mamal-like network will emerge! )

    --

    --Manuel
    "I hate quotations, tell me what you think"
    1. Re:The plane is gonna crash by jhoffoss · · Score: 1

      Read the article much?

      --
      Linux: The world's best text-adventure game.
    2. Re:The plane is gonna crash by buzban · · Score: 1

      In my opinion the issue is a lot more like having 40 planes that currently handle the schedule, and needing to keep 39 of them in the air at all times...truly, the Internet was built as a distributed network, so the idea that it stands alone and needs to be repaired while all parts are in use is a little bit of a stretch, to me...

    3. Re:The plane is gonna crash by Anonymous Coward · · Score: 0

      I've heard that chanaging the protocol for the internet to IPv6 is similar to changing the motor of an airplane in mid air. Is it really plausible to do that?

      Ask Aaliyah.

      a.c.

  6. More IP address !=more ease by mr100percent · · Score: 2

    Will IPV6 fix DNS?
    Will it give back that huge class A domain that MIT still has?

    Will my cable modem ISP with IPV6 give me more than 1 IP address so I can turn off NAT and DHCP? probably not.

    1. Re:More IP address !=more ease by jd · · Score: 2
      If IPv6 is properly administered, DNS (per se) will cease to exist. IP addresses will be dynamically assigned, be transitory, and be mobile.


      In consequence, there will be no real point in a DNS system, as it exists today. There would be no way a centralized system could keep up with the changes.


      With IPv6, I suspect you'll find that DNS is replaced with self-identifying systems, using the Anycast protocol. Each machine would then be responsible for knowing what it was called, at that time. (Which sounds reasonable to me!)


      We haven't seen that, so far, because Anycasting is still too new and few existing IPv6 stacks support it. However, when IPv6 starts getting seriously used, it could become the most important protocol of all.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    2. Re:More IP address !=more ease by Golias · · Score: 1
      Damn, I am sick of all this hand-wringing over IPv6, like it's going to change our lives or something.

      (This is not addressed directly at your comment mr100percent, so please don't take this too personally...)

      It's so much not the big deal some people are trying to make it out to be. Here is one example of a simple solution:

      Write IP drivers that treat all devices which return an old IP addres as being the old address followed by 96 zeroes. Treat all IP calls from legacy software the same way. Then when people update their drivers (or replace their NIC cards, whichever is less hassle for them), they just keep all IP settings exactly the same. After a few months of transition goes by (to give everybody a chance to make the update), you start assigning 128-bit IP's for all new requests. Done. Wasn't that easy?

      --

      Information wants to be anthropomorphized.

    3. Re:More IP address !=more ease by RoweM · · Score: 1
      Huh?

      If anything, the vast address space of IPv6 will mean that every device can have its own, permanent, hard coded address, just in case it ever wants to get on the net.

      Name resolution will still be a problem.

      --

      --
      "Small minds discuss people, average minds discuss events, great minds discuss ideas"

    4. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      No need for all that. Gateways already exist that easily handle this for you. There no nee to make changes to end systems until you are ready.

      Furthermore, core systems can easily translate back and forth between IP4 and IP6 numerous times in a single path. So, it's no big deal if one provide uses IP4 and the next uses IP6.

      The big deal is that there is nothing, today, that will force anyone to make the jump. That said, there will be some expense incurred for anyone that makes the transition. Everyone is watching everyone else saying, "I'm not going to all that trouble and expense if I don't have to. So, IP6 stays on the shelf for several years to come.

    5. Re:More IP address !=more ease by RollingThunder · · Score: 2

      I'd suspect it would depend on how much IP addresses cost, under IPv6. As it stands, if you want your own range (not a range delegated from your ISP), it's Not Cheap, and I recall you had to get 3 class C's (which struck me as really odd).

      If the cost of an IPv6 block dwindles to about ten bucks a year per thousand (pulling numbers out of the air) then I suspect each ISP account would come with 16 or so addresses.

      And man, would I like that. Ever try playing a DirectPlay game behind a NAT firewall? It's fine with one client and a bunch of blind portforwards, but you're on your own if you have two systems behind it that want to play. (admittedly, that's not IPv4's fault, it's that nobody knows how to read the stream to make an ip_masq_directplay as far as I know)

    6. Re:More IP address !=more ease by 3247 · · Score: 1
      "If IPv6 is properly administered, DNS (per se) will cease to exist. IP addresses will be dynamically assigned, be transitory, and be mobile.

      In consequence, there will be no real point in a DNS system, as it exists today. There would be no way a centralized system could keep up with the changes."
      On the contrary! It makes DNS more important than ever. However, we will certainly see more dynamically updated DNS records. On the other hand, real servers will still use constant IPv6 addresses.
      --
      Claus
    7. Re:More IP address !=more ease by kurowski · · Score: 1

      Um, how do you intend to do routing then, when you have things like mobile devices that move from one network to another?

    8. Re:More IP address !=more ease by ASyndicate · · Score: 1

      Also,

      How do you propose to eliminate name conflicts?
      " NO! My Computer is named yyy.isp.net!!"

      "NO! Mine is!"

      If everyone could assign their own names. It would be a disaster.

      -syndicate

      --
      This page left intentionally blank.
    9. Re:More IP address !=more ease by mike260 · · Score: 3, Insightful

      Will it give back that huge class A domain that MIT still has?

      A class A is 1/20,282,409,603,651,670,423,947,251,286,016th of the total IP6 namespace. Why not let them keep it?

    10. Re:More IP address !=more ease by jd · · Score: 5, Informative
      Doesn't work that way with IPv6. IPv6 uses a system whereby the provider announces a prefix to the device, and the device then attaches whatever number it likes to that prefix. If another device attaches to that first device, then that first device announces the prefix it got, PLUS the first 1-2 bytes of whatever it added, as the new prefix.


      The theory behind all this is that you can then move a device from one network to another, without ever having to worry about routing problems, IP numbers colliding, or other such mundane trivia.


      "Permanent" addresses, in this system, don't exist. They're all calculated.


      How does this work, in practice?


      Well, let's say that Joe Bloggs is connected to AOL. AOL decides that the backbone provider it uses can get stuffed, and switches. This changes all of AOL's addresses, and therefore Joe Bloggs' address.


      However, because addresses have a lifetime attached to them, the old address remains active (although forwarded) for a finite length of time, although new connections to the old address are prohibited.


      Because of this, it makes no sense for some central registry to store AOL's IP number. It can change once every 60 seconds, along with the IP address of everyone/everything connected via it.


      The only person who can meaningfully store AOL's IP address becomes AOL, itself. Nobody else can possibly know it, with any reliability.


      Normally, ISPs and large corporations aren't going to flip around like that. But they -can-. The protocol permits it. Because of that, and because uptime is increasingly important, they will then be able to shop for a secondary provider for a backup link, in case the first one dies.


      In IPv4, a backup link via an alternative provider would be lethal. There would be no way to handle the changes in addressing, unless the entire ISP or company was behind a NAT system with High Availability at the IP level, which causes its own problems.


      With IPv6, the change-over would take under 5 seconds for the whole of AOL. Nobody would notice the delay, nobody would get disconnected, and the whole setup is much simpler.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    11. Re:More IP address !=more ease by jd · · Score: 2

      One problem: IPv6 doesn't know about constant addresses. :) Well, other than the local-link ones. :)

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    12. Re:More IP address !=more ease by SVDave · · Score: 1
      IP addresses will be dynamically assigned, be transitory, and be mobile.

      Dynamically assigned? Transitory? Why? IPV6 has 2^128 possible addresses. According to the IPV6 FAQ, that's 3.4*10^27 addresses per person (assuming a worldwide population of 10 billion). You could give every person 256, or 4096, or 65536 IPV6 addresses and barely scratch the surface of the address space. Why make address assignments anything other than permanent?
    13. Re:More IP address !=more ease by Jherico · · Score: 2, Interesting
      Write IP drivers that treat all devices which return an old IP addres as being the old address followed by 96 zeroes. Treat all IP calls from legacy software the same way. Then when people update their drivers (or replace their NIC cards, whichever is less hassle for them), they just keep all IP settings exactly the same.

      Actually, there is a standard in IPv6 for how to encode an IPv4 address as IPv6 (prepended zeros, not appended). Also, no one needs to replace a NIC. NICs talk Ethernet (typically), not IPv4 or IPv6, and the appropriate protocol is wrapped up in layers before it gets to the NIC.

      And there is no such thing as a NIC card, or for that matter a PIN number. Sigh. Sorry, its just irritating.

      --

      Jherico

      What can the average user can do to ensure his security? "Nothing, you're screwed"

    14. Re:More IP address !=more ease by aozilla · · Score: 1

      If the cost of an IPv6 block dwindles to about ten bucks a year per thousand (pulling numbers out of the air) then I suspect each ISP account would come with 16 or so addresses.

      you can get a tunnel to the 6bone with a billion IP addresses for free...

      --
      ok then your [sic] infringing on my copyright! Could you as [sic] me next time before STEALING my comments for your own?
    15. Re:More IP address !=more ease by jd · · Score: 2, Informative
      The people who designed IPv6 opted, right from the start, to make it as automatic as possible. Administrators should not be burdened with assigning IP addresses, making sure there's no conflict, or running DHCP and similar carp.


      Further, they anticipated an increasing use of portable devices, such as laptops and hand-helds, which made it important to have Mobile IP a part of the protocol.


      The result was the complete absence of any notion of static IP addresses. Addresses are assigned at connection time, and last until either they're revoked by the owner, or they time out. Once they reach that point, they are marked as expiring. A new address is then generated. The host machine is required to then notify ALL machines connected to it or that it connects to that the address is changing, and what that new address is. The remote machines then have a certain length of time (it's not long) to change over. During the change-over, if the host has moved, the old IP addresses are forwarded by intermediate routers to the new location.


      In theory, this means that IPv6 has not just 2^128 addresses, but also a TOTALLY dynamic topology. (Mapping the Internet'll suddenly become a whole lot more interesting! :)


      In turn, this means that you can have wireless IP and multiple providers, move from one zone to another, and be guaranteed you'll remain connected.


      Further, because addressing follows an enforced heirarchy, router tables will NEVER need more than enough addresses to go one layer up or one layer down. For 99.999% of providers, this will mean an entire 512 entries, tops. Compare this with the millions of entries a typical router handles. Forwarding lag will be carved, sliced, diced and roasted.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    16. Re:More IP address !=more ease by Jeremiah+Cornelius · · Score: 1
      I've said it once, I've said it a thousand times:

      IPv6 is the future, and it always will be!

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    17. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      In IPv4, a backup link via an alternative provider would be lethal. There would be no way to handle the changes in addressing, unless the entire ISP or company was behind a NAT system with High Availability at the IP level, which causes its own problems. Umm, BGP?

    18. Re:More IP address !=more ease by NonSequor · · Score: 2

      I say that we won't have a networking protocol that provides more addresses than their are particles in the universe. I'm thinking that the number of addresses should be roughly the size of Graham's number. Then we will NEVER run out of addresses.

      --
      My only political goal is to see to it that no political party achieves its goals.
    19. Re:More IP address !=more ease by NonSequor · · Score: 2

      I misinterpreted your comment at first. I was thinking that you were saying that IPv6 would provide enough addresses for our needs forever. So forget my other comment.

      --
      My only political goal is to see to it that no political party achieves its goals.
    20. Re:More IP address !=more ease by Jeremiah+Cornelius · · Score: 1
      Eternal optimist, I thought it would be modded up "FUNNY".


      Jeremiah

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    21. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      IPv6 is the future, and it always will be!

      It will only be the future until it is implemented. Then it will be the present, and past.

    22. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      Or you can use FreeBSD's address mapper, which lets you map one set of IPs to another, and freebsd will rewrite the packets in both directions.

    23. Re:More IP address !=more ease by SVDave · · Score: 1

      If the cost of an IPv6 block dwindles to about ten bucks a year per thousand (pulling numbers out of the air) then I suspect each ISP account would come with 16 or so addresses.


      At 2^128 addresses, $10 per trillion would be too expensive. At that price, the entire address space would be worth $3 billion billion billion, which would probably make the IPV6 address space worth more than all the real estate on the planet :-). Does anyone think that the IPV6 address space is worth that much? If so, then we should all switch from IPV4 to IPV6 for no other reason than to cause the single greatest creation of wealth in the history of the human race.

    24. Re:More IP address !=more ease by Ben+Hutchings · · Score: 2

      One of the big problems with IPv4 is the difficulty of routing. Given that there's a shortage of IP addresses, we can't let ISPs allocate large blocks, so they have to get several smaller blocks which results in several entries in routing tables. Worse, if an ISP's customer wants its own address allocation that it can take to another ISP or make accessible through multiple ISPs for redundancy, that makes another entry in the routing table. The result is that routing tables are huge and not always well optimised.

      By making address allocation dynamic, IPv6 makes it possible to optimise address allocations for simplicity of routing. That should result in better routing decisions even as the number of addresses in use increases.

    25. Re:More IP address !=more ease by Golias · · Score: 2
      Thanks for the information. Your point serves to strenghten my resolve that the switch to IPv6 is nothing to get our titties in a twist over.

      Now try not to be such an acronym nazi.

      (j/k) :)

      --

      Information wants to be anthropomorphized.

    26. Re:More IP address !=more ease by Gordonjcp · · Score: 1

      Yeah, well I'm STILL user 137...

      ... even though you're Moonglum now.

    27. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      Who need IP6 now that all the IP space is cleared up by the .COM melt down. We got another couple of years before that's a problem. ;)

    28. Re:More IP address !=more ease by mr100percent · · Score: 1

      I can't believe I forgot. What's Graham's Number?

    29. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      Very constructive.

    30. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      *hits you with a clue stick* Way to miss the point completely!

    31. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      what about the security consederations? If your refridgerator gets RBL'd you would have to change the nic card to get it back on the net. WHY? because part of the address scheme includes the MAC ADDRESS! Can anybody say "Big Brother?"

    32. Re:More IP address !=more ease by Anonymous Coward · · Score: 0

      IPv6 doesn't have class As. With IPv6, most people will get a /48, which has 2^80 addresses; that's even more than an old class A.

    33. Re:More IP address !=more ease by Wesley+Felter · · Score: 2

      I looked up how much IPv6 addresses cost (at least in North America), and it's $2,500/year for a /35. Since each customer is supposed to get a /48, that's enough room for 8192 customers. That works out to about 30 cents per customer per year.

    34. Re:More IP address !=more ease by uchian · · Score: 1

      Surely dynamic address allocation will, even if it speeds up routers, mean that DNS servers will be hopelessly out of date, permanantely?

      Since I dial up on a modem at the moment, where I get a dynamically allocated IP address, I cannot set myself up as a web server, simply because my address changes every time I reconnect to the internet (OK, I'm not serious about making a web server over a 56k modem but you get my point).

      I thought that every time your IP changed, you had to broadcast this inforrmation to the DNS servers, which take a while to propogate and tell each other who is who? If everyone is doing this constantly, the DNS servers would become hopelessly confused... or am I missing something obvious?

    35. Re:More IP address !=more ease by rtaylor · · Score: 1

      Actually, that would be the very reason they got a class A in the first place... You know, when there were only 200 people on the internet (in total), so they all got Class A's.

      --
      Rod Taylor
    36. Re:More IP address !=more ease by RollingThunder · · Score: 2

      Yeesh, and here I thought I was picking something arbitrarily low enough to basically make the cost of them meaningless! :)

    37. Re:More IP address !=more ease by mino · · Score: 1

      I say that we won't have a networking protocol that provides more addresses than their are particles in the universe.

      Hey... that's not NEARLY enough. We don't just need to be able to address the particles... we need to address items MADE of those particles. So not only should we be able to ping a carbon molecule somewhere near Sirius, we need enough addresses to ping any given chain of them. So I guess we need number-of-particles-in-the-universe-factorial addresses, to make sure we've got all the combos covered.

    38. Re:More IP address !=more ease by Cato · · Score: 2

      Let's see - DNS lets you type in slashdot.org and get an IPv4 or IPv6 address. Anycast lets you type in a long hexadecimal IPv6 address in your browser bar. Why do you think Anycast could ever replace DNS? It may well be used in some niches, e.g. to talk to a server farm, but it's not going to be relevant and will never replace DNS.

    39. Re:More IP address !=more ease by Cato · · Score: 2

      There are several kinds of dynamic allocation here:

      - dynamic IPv4 addresses, often used for dialup as you say, and hard to use for web serving

      - IPv6 allocation of the bottom half of the IPv6 address (last 64 bits I think) - this is basically the MAC address of your Ethernet card (with some provisions to change this for privacy reasons). Not really dynamic unless you want it to change.

      - IPv6 allocation of the top half of the address - this is derived from your ISP, and it is *very* easy to renumber your whole network (even thousands of machines) when you switch to a different ISP. This is crucial to make sure that the route to your machines doesn't need to be stored in core routing tables in the Internet, avoiding them growing too fast. Also not dynamic unless you want to change providers.

      The first kind of dynamic allocation goes away completely. The MAC address type allocation is only dynamic if you want to preserve privacy, typically on a client. And the provider part allocation is slowly changing, over a number of days after you switch providers, with plenty of time for DNS servers to react.

      The upshot of this is that static addresses are very common in IPv6 - you only have to change your address if you switch providers. A couple of points though:

      - you might want to use a dynamic MAC address for outbound client requests, for privacy reasons, and a static IPv6 address (plus DNS name) for your web server (even on the same host, it's easy to have multiple addresses per interface)

      - networks with two Internet connections, termed multi-homed, are still a big problem for core routing tables, since they incur one 'exception' route in the core routers. There's some work going on under the term PTOMAINE (a very tortured acronym) that should solve this in the next 5 years or so, 'ietf ptomaine' should find it.

  7. Good summary of the problem by Masem · · Score: 2
    I think the best part of this article is the summary of the problem: it's chicken & egg in that IPv6 won't be implemented by the backbone people until customers want it, while customers don't want it until the services are there. It reminds me very much of the current problem with HDTV, in that viewers don't want to buy HDTV systems since there's little programming that takes advantage of it, while the stations don't want to go to HDTV since no audience people have HDTVs. Of course, in this case, (We hope) government regulation will make the transition required. The switch to IPv6 is yet still only an informal agreement via the standards body and has no force of law yet to make it occur.

    --
    "Pinky, you've left the lens cap of your mind on again." - P&TB
    "I can see my house from here!" - ST:
    1. Re:Good summary of the problem by RacerX69 · · Score: 1

      Or another analogy:

      Mainstream consumers are reluctant to switch from Windows to Linux or other OS because of the lack of a port of [insert your favorite app here].

      Mainstream developers are reluctant to program/port their apps to Linux because there isn't (in their eyes) enough consumers to support porting their apps.

    2. Re:Good summary of the problem by bnenning · · Score: 2
      Of course, in this case, (We hope) government regulation will make the transition required.


      I certainly don't hope that. I was all for HDTV at first, but since the vendors seem far more concerned with trying to destroy time and space-shifting than actually making a quality product at a reasonable price, I wouldn't mind at all if they went down in flames.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    3. Re:Good summary of the problem by Eil · · Score: 2

      Hmm. So let me get this straight. You *want* HDTV to succeed? Even though they're currently busy making it so that you can never make copies of anything broadcast over it, even well within your fair use rights?

      And you then want this backed up by law?

      I'm sorry, but if anything is going to be succeeded by anything, making the government do it is not the right way. It's not even their job! Hopefully, what's going to happen is that the backbone providers will see IPv6 as a great technical or strategical boon and they will more or less (through hopefully non-bullying means) convince their customers to switch over.

      *That* is how progess happens. Remember that "law" and "progress" are seldom used in the same sentence on purpose.

    4. Re:Good summary of the problem by Anonymous Coward · · Score: 0
      I certainly don't hope that. I was all for HDTV at first, but since the vendors seem far more concerned with trying to destroy time and space

      AAAHHH!! Oh, wait. Word wrap...

  8. ain't broke, don't fix it doesn't always apply by coloneyb · · Score: 1

    I like this one:
    "but so are the critics of it who point out that if we don't have a problem now, why fix it"
    Now, I understand this to an extent.
    But, at the same time people are seeing the limitations of IPv4 and how we are starting to exhaust the space.
    Now, just to equate the statment to something else. Y2K.
    Nothin was broken and didn't pertain to many people earlier and so they didn't try to fix it earlier and it caused that hoopla of "what will happen".
    Yeah - not exactly the same thing. Ok, here is another one then.
    High Schools (in the US)
    Have you noticed how most counties get all the reports and build a school and they haven't been allowed to forecast. Forbid we forecast and build a slightly larger school because we foresee the need for a larger school in the near future.
    So, it works great for a little while with plenty of room and then one day it is overcrowded and so we hinge things like trailers onto them or try to rework schedules and create a nightmare until we can build a new highschool, but that will take a few years. It's cyclical.

    1. Re: ain't broke, don't fix it doesn't always apply by 3247 · · Score: 1

      But IPv4 is broken already. It's only that HTTP/1.1 and NAT cover the worst cracks. But it certainly is not a long-term solution.

      --
      Claus
    2. Re: ain't broke, don't fix it doesn't always apply by coloneyb · · Score: 1

      didn't say we didn't need to fix it.
      Was sayin that we DO need to fix it.

  9. OS support exists by Proud+Geek · · Score: 2

    From what I understand, Linux and Windows NT have had IPv6 support for quite some time now. The bigger barrier to adoption is that router technology for IPv6 is not quite ready for primetime. When Cisco and Nortel get their act in gear, IPv6 should be up and running in the wild in no time.

    --

    Even Slashdot wants to hide some things

    1. Re:OS support exists by DeathBunny · · Score: 2

      Cisco has support for IPv6 in the newer versions of IOS (12.1T and above I believe). Check the Cisco Web Site for more information.

    2. Re:OS support exists by jd · · Score: 2

      CISCO has had an implementation for some time. So has 3COM, Bay, Telebit, and many others. It's ready for prime-time, alright.... Well, it would be, if they could agree on what protocol to use. The 6bone was a MESS, the last time I looked, with the only good protocol (a heirarchical version of RIP, from the looks of it) coming in last.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:OS support exists by eggnet · · Score: 1

      It's actually 12.2T and above, so it probably won't reach General Deployment for a long time. 12.2T will be merged into 12.3, but GD won't happen until 12.4 (or 13.0).

      What does that mean? That means that if you want to use IPv6, you have to run what amounts to an experimental code base until 12.4 or 13.0.

  10. IPv6 was also designed to support interplanetary by orionpi · · Score: 1

    ... connections, by allowing longer ping times. So much for multiplayer gaming. But it is a more sound idea than every ISP having only one IP address and running NAT.

  11. IPv6 is well supported by dgp · · Score: 1

    linux has had ipv6 for a long time. Microsoft has an add-on for windows 2000 here and it comes standard with Windows XP.

    having support from linux and win2k/xp means its pretty well supported.

    1. Re:IPv6 is well supported by RKloti · · Score: 1

      Actually the problem is less the clients (once OS X, Windows 9X/ME/XP/2k, Linux, Solaris, and *BSD support it, you could more or less consider it universal. And most of the aforementioned OSes already support it or will support it soon) than it is the ISPs. It is very unlikely that your ISP is going to take the time and money to upgrade to IPv6, since it would make a potential source income - IP addresses - largely worthless. (there would be 256^16 of them, if my memory serves me correctly) Likewise, your ISP's backbone provider is also unlikely to make the leap.

  12. Why fix it? by Zeekamotay · · Score: 1

    ...critics of it who point out that if we don't have a problem now, why fix it...

    To anyone who ever said, "If it ain't broke, don't fix it," I offer, "Improvement is impossible without change."

    1. Re:Why fix it? by Anonymous Coward · · Score: 0

      and reliability is impossible with stability

  13. Yickers...no more food security? by xcomputer_man · · Score: 1

    "For instance, do people really want a unique address for a refrigerator -- allowing hackers to spy on individual eating habits -- or order you a truckload of milk?"

    Oh my God - what if my fridge got DoS attacked? Or Code Red? We would all go hungry for days on end!

    1. Re:Yickers...no more food security? by Anonymous Coward · · Score: 0
      Oh my God - what if my fridge got DoS attacked? Or Code Red? We would all go hungry for days on end!

      Don't sweat so much lunchbox. You could stand to lose a few pounds anyway you fat fuck.

      - jay

    2. Re:Yickers...no more food security? by fishebulb · · Score: 1

      hackers dont care what food you buy
      companies do

      another "hackers, wont somebody think of the children response" considering hackers have no motivation to care what brand ketchup someone buys, companies do

    3. Re:Yickers...no more food security? by Anonymous Coward · · Score: 1, Funny

      Screw that. I'll create my own in house lan, and hook my beer fridge up to 192.168.1.24

  14. Who would start the change? by mr100percent · · Score: 2

    Who would start the change, since nobody is "in charge" of IP out there. If DNS root server A upgraded, would everyone else follow? So far, everybody is watching everyone else, nobody is making the first move.

    How about if AOL made a systemwide change, or ATT, Excite, and MCI all together?

    1. Re:Who would start the change? by JesseL · · Score: 2

      Actually, I believe ARIN (American Registry for Internet Numbers) is in charge of IP (for the USA).
      I imagine they would be the ones to initiate the change to IPv6.

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    2. Re:Who would start the change? by DeathBunny · · Score: 2

      Bind has supported IPv6 records since version 4.9.4 (which is pretty damn old). DNS isn't the problem with IPv6. It's really getting the IPS's and backbone providers to bother implimenting IPv6.

    3. Re:Who would start the change? by jd · · Score: 2
      ALL it would take is for one of those to change, and then to have IPv4IPv6 gateways at the borders. The customers would then be using an IPv6 stack, and gaining all the benefits, REGARDLESS of whether the rest of the Internet ever switched over.


      FURTHER, because they were using IPv6 stacks, companies would have an incentive to write IPv6 apps, which would pressure other ISPs into changing over, too.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    4. Re:Who would start the change? by jilles · · Score: 3, Insightful

      How about a killer app? The problem is that right now if you start using ipv6 you are pretty much alone. Actually you might as well unplug your network cable, since you won't be able to do much useful stuff with it.

      What is needed is ipv6 only services (e.g. mp3 peer2peer filesharing) AND an easy way to get an ipv6 number for your clients/servers that can coexist with your current ipv4 number (i.e. your computer has both an ipv4 and ipv6 number). The easy part is essential because that prevents that people start creating ipv4 gateways to such services (thus removing the need for getting an ipv6 number). There are plenty of ipv6 numbers available so getting and registering one should be made as easy as possible (something like a distributed, global dhcp server that would automatically get you one based on your mac address would come in handy). Come to think of it, why not just automatically convert those mac addresses into ipv6 numbers (mac addresses are supposed to be unique anyway but I'm not entirely sure this is a great idea)

      As I understand it, ipv6 can be tunneled over existing ipv4 networks, so it shouldn't be a problem if some routers inbetween ipv6 hosts are ipv4 only.

      This would cause the amount of client pc's with ipv6 numbers to gradually grow. Also since lots of PCs don't have static ipv4 numbers, the amount of servers on ipv6 would also grow. Eventually, there will be a critical mass of ipv6 servers and clients and the switch can be made.

      Currently there are a lot of p2p applications in development. I imagine, implementing such stuff would be a lot easier using ipv6 with its improved features. Another killerapp could be streaming multimedia (you want to see this great movie, get yourself an ipv6 number now!!).

      --

      Jilles
    5. Re:Who would start the change? by jhines · · Score: 1

      It would happen in the far east, they are the ones experiencing the worst effects of the IPv4 number shortage.

      The Chinese would be another likely guess, since sending all their traffic through a single (or multiple) gateways would help in both their efforts to limit the net to their population, and in the transition.

    6. Re:Who would start the change? by gorilla · · Score: 2

      And the OS's and devices. If IPv4 is on the bootup screen, but IPv6 is hidden down deep so that you have to be an expert, then people are going to choose IPv4 only.

    7. Re:Who would start the change? by b1t+r0t · · Score: 3, Interesting
      The problem isn't getting an IPv6 node number. There's already a pre-defined IPv6 number range for IPv4 addresses. The problem is that there need to be IPv6 routing protocols for routers, and backbones that use them.

      You're thinking about this completely wrong. What was it that made TCP/IP the 800 pound gorilla standard in the first place? The US Government, especially the military, standardized on it. What we need is to get the US Government to start requiring IPv6 in contracts.

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    8. Re:Who would start the change? by Rumble · · Score: 1

      Of course back then the only people who used the Internet, DARPA and such, were from the government, military, or educational institutions. It is a different situation now. I doubt uu.net or @home would give a rats ass if the government started using IPv6.

  15. IP6 by foo+fighter · · Score: 1

    As the (one and only) sysadmin for a medium sized business, I'm interested in what an all IP6 network would do for our systems. Does it make things faster, make address management easier, make my network more secure, do I need a new ISP? Could someone reply with a link to an IP6 FAQ of some sort?

    Searching google for IP6 brought up a lot of links to herbal cancer cures (!?), but nothing that looked very useful.

    --
    obviously no deficiencies vs. no obvious deficiencies
    1. Re:IP6 by ethereal · · Score: 1

      Maybe you should try searching for the name of the thing you're trying to find out about: "ipv6". I guarantee you'll find more than you want to know :)

      --

      Your right to not believe: Americans United for Separation of Church and

  16. famous prophecies by Telek · · Score: 5, Insightful

    if we don't have a problem now, why fix it?

    (ahem)

    "640 kB should be enough for everybody"

    "I see a worldwide market for 5, maybe 6 computers"

    and one that I can only assume:

    "yeah, use 2 digits for the year. Bah, the year 2000 is 20 years away, nobody will be using this stuff then anyways"

    And besides, if you wait until the problem is upon us, it'll be too late to fix it.

    --

    If God gave us curiosity
    1. Re:famous prophecies by TomK32 · · Score: 1

      you forgot US Ex-Vice-President Gore:
      "I invented the internet"

      --
      -- just a geek - trying to change the world
    2. Re: famous prophecies by Anonymous Coward · · Score: 0
      If we don't have a problem *now*, why fix it?

      Oh great, who gave George W. Bush control of the internet?

    3. Re:famous prophecies by j7953 · · Score: 2

      "I see a worldwide market for 5, maybe 6 computers"

      "We now know he overestimated by four."
      -- Clay Shirkey, in a talk on Napster

      --
      Sig (appended to the end of comments I post, 54 chars)
    4. Re:famous prophecies by Velex · · Score: 1

      > "640 kB should be enough for everybody"

      Oh, great, I can see it all now. Well have andextra byte for High Address Area, then there will be Extended Addresses, which will require special drivers. These Extended Addresses will, of course, be mutually exclusive with Enhanced Addresses. Then, a wizard will write software which will unify all address bytes, and this will require a special address server. Then, when we finally get around to implementing continuous addresses, people will have to backwards support applications which are expecting a four byte barrier. (smacks forehead)

      --
      Join the Slashcott! Stay away entirely Feb 10 thru Feb 17! Close all tabs to prevent autorefresh!
    5. Re:famous prophecies by tswinzig · · Score: 2

      640 kB should be enough for everybody

      Bill Gates never said this. Its an urban legend.

      --

      "And like that ... he's gone."
    6. Re:famous prophecies by Anonymous Coward · · Score: 0
      640 kB should be enough for everybody

      Bill Gates never said this. Its an urban legend.

      He didn't, but Intel did in their original specification for an 8088-based PC, which IBM followed. Even if you don't believe that, IBM at least implied it in their design of the PC.

    7. Re:famous prophecies by Telek · · Score: 2

      Doesn't matter. Somebody said it enough to get noticed, so it's still funny =)

      --

      If God gave us curiosity
    8. Re:famous prophecies by Fjord · · Score: 2

      No, you are thinking of the 64K barrier, not the 640K one. The 640K one was a DOS restriction. 64K was because of the 8088's 16-bit addressing. 640K was for no real good reason other than "it should be enough". While Bill G may have never said those exect words, his company okayed the philosophy behind them.

      --
      -no broken link
    9. Re:famous prophecies by WWWWolf · · Score: 1

      "I invented the internet"

      No. "I took the initiative in creating the Internet."

      There is some truth in this - remember that DARPA, a military entity, funded the ARPAnet research. While Gore wasn't around when the ARPAnet project began, I think I read somewhere that he referred to time when ARPAnet became Internet.

      As usual, the bright ones all around do the sweaty work and the Management (be it bosses or politicians) try to take the credit for it. =)

    10. Re:famous prophecies by PD · · Score: 2

      Dammit, that's completely wrong.

      Bill Gates never said that, and the 640K limit was not because of DOS.

      IBM build the hardware with the various devices occupying memory locations above 640K. The whole machine could only have 1 megabyte of memory, and the devices needed to go somewhere.

      The 640K limitation is because of the design of the hardware, not anything Microsoft did.

  17. When it's time for IPv6, by The_Messenger · · Score: 2, Funny
    Windows NT will be ready. Windows NT was the first network operating system to support IPv6, and also includes support for the next-generation MSIPv8, also known as Microsoft IP 2004. MSIPv8 enhances the usability and managabilty of the Internet Protocal through versitile .NET servives and intuitive Web-enabled application diversification.

    We're living in a wired world, and Windows NT provides the computing tools that we need to do ebusiness, as well as iPlay. Remember, Microsoft Windows NT: it doesn't get any better than this!

    --

    --
    I like to watch.

    1. Re:When it's time for IPv6, by Aexia · · Score: 1

      That more scary that funny, really.

    2. Re:When it's time for IPv6, by zhevek · · Score: 1

      This is moderated up to 2, funny....

      but is this trying to being funny? Or is this
      person serious? *shiver*

  18. 203.178.141.220 by blackeye · · Score: 1

    Just looking at the link to the side, I wonder how many people lookup'ed that ip, and also the v6 ip of the microwave :)

    1. Re:203.178.141.220 by Tek+Neek · · Score: 1

      $ nslookup 203.178.141.220
      Server: ns2.ast.lmco.com
      Address: 160.205.13.3

      Name: kame220.kame.net
      Address: 203.178.141.220

      It's a japanese project to build an IPv6 stack for BSD.

  19. A problem that was circumvented long ago. by Matey-O · · Score: 2, Insightful

    A group migration to IPv6 may never be necessary. With NAT now being pervasive, There only needs to be one or very few IP addresses per company.

    The original quote (around 1989) was: "My god! At this rate, we'll be out of addresses by [1992]"

    That obviously hasn't happened now, has it?

    When ALL of an ISP's web clients can function on a single IP address at port 80 using header redirection, I don't thenk we're going to need the additional address space for a long time.

    (IP addressing by latitude and longitude, while a cool idea, always seemed to be a solution looking for a problem.)

    --
    "Draco dormiens nunquam titillandus."
    1. Re:A problem that was circumvented long ago. by mr100percent · · Score: 1

      NAT isn't THE solution to this, otherwise I wouldn't have to spend hours troubleshooting a Linksys and explain to my mother why the second computer can't run napster on the same connection as the first due to port-forwarding problems.

    2. Re:A problem that was circumvented long ago. by Matey-O · · Score: 1

      Sounds like a limitation in napster. After all, there are 65535 ways (ports) to talk to any given IP address.

      Yeah, it's a band-aid to a problem, but it IS a solution.

      --
      "Draco dormiens nunquam titillandus."
    3. Re:A problem that was circumvented long ago. by swright · · Score: 1

      What I'd like to see is some sort of protocol for communication between applications and the NAT device - whereby the app could dynamically request inbound tunnels on certain ports.

      I realise this wouldn't always help (contention betw. multiple instances of the same app on different boxes within the LAN) - but it would certainly help - particularly with messaging apps, or indeed anything where there is a prior outbound connection to either the remote host concerned or some central server.

      By way of example... app says to NAT 'please assign me an external port and forward all connections on it to me at port x' - that should work fine for things like IRC (DCC), ICQ, NetMeeting (yuk) and things like that...

      For the security conscious, this could be filtered by internal IP address, external port ranges, external hosts ('I'm expecting a connection from x.x.x.x within y seconds'), or by app (perhaps some manual insertion of a key from the NAT into the app on installation).

      Maybe I've missed something but this sounds to me like a useful kind of protocol

    4. Re:A problem that was circumvented long ago. by The+Larch · · Score: 1
      It exists and it's called socks. The trouble is, it usually requires application level support as many braindead protocols make unwarranted assumptions.

      Durr there is a network interface on this machine with an ip address of 192.168.1.7, that must be my ip address, HELLO SERVER i am a client, please send the file BRITNEYSPEARS.MP3 to 192.168.1.7 port 5432 i have opened it for you!

      And don't get me started on peer-to-peer voice-over-ip ..

      (apologies to drew)

    5. Re:A problem that was circumvented long ago. by Anonymous Coward · · Score: 0

      That sounds like cool idea!!!
      Oh, wait, you mean like a socks firewall?

      I guess somebody already did it.

    6. Re:A problem that was circumvented long ago. by iritant · · Score: 1

      Please check out the MIDCOM working group of the IETF on this very topic. See http://www.ietf.org (under "working groups") for more information.

    7. Re:A problem that was circumvented long ago. by szomb · · Score: 1

      After all, there are 65535 ways (ports) to talk to any given IP address.

      That's 65535 TCP ports, and 65535 UDP ports. :)

      --
      Just because a few of us can read write and do a little math, doesn't mean we deserve to conquer the universe
    8. Re:A problem that was circumvented long ago. by Wesley+Felter · · Score: 2

      This is called Universal Plug-n-Play; it's already supported by Windows XP and the spec will come out in a few months. Makers of cheap NAT boxes have already pledged their support.

    9. Re:A problem that was circumvented long ago. by PMan88 · · Score: 1

      I'd sure as hell be PO'd if my ISP gave me a NAT address with outgoing connections only.

    10. Re:A problem that was circumvented long ago. by swright · · Score: 1

      ok this is true. Somehow the word SOCKS kinda echoed in my head but not enough twigged for me to realise it was pretty much the same thing.

      Good job I didnt try and patent it eh ;)

      Nevertheless though, it is the kind of thing that more widespread support for would help alleviate the IP address space shortage.

  20. 6-BONE? by ethereal · · Score: 4, Interesting

    Why not run the conversion like the 6bone has? That is, start off with virtual IPv6 between IPv6 supporting sites over IPv4 links, and gradually shift to native IPv6 where possible as more and more of the intermediate "link" sites convert to IPv6? At some point, you switch over core routers one by one so that they're running virtual IPv4 over IPv6 transport, and switch out the last of the IPv4 hardware as it becomes obsolete.

    Not that this necessarily provides an incentive for IPv4 users to switch, but IMHO, as a person that's not too knowledgeable about IPv6, I don't see why technically a migration has to be too difficult. Maybe you could make the incentive something like rewarding you with more IPv6 addresses as you move out of IPv4 space - that would definitely move big network operators along, at least.

    I'm still not sure how to force a more equal global assignment of the dwindling IPv4 address space. It seems like if the IPv4 afficianados aren't careful, China will just switch to IPv6 immediately, and the rest of the world will get dragged along just so we can continue to communicate with that huge percentage of the human race.

    --

    Your right to not believe: Americans United for Separation of Church and

    1. Re:6-BONE? by farmhick · · Score: 2, Insightful

      A reward that would definitely make a big impact would be to offer Microsoft the first publicly available Class A block in IPv6. they would switch in about 3 seconds, and drag everyone else kicking and screaming along with. The whole of MSN would be on it, including Hotmail, and the .Net side of MS.

      But the Chinese government might not really care about this, since they don't want their people to access the Net anyway, with all the political stuff and all.

      --
      I have to stop wasting so much time reading Slashdot. It's interfering with my crystal meth addiction.
    2. Re:6-BONE? by aozilla · · Score: 2

      Not that this necessarily provides an incentive for IPv4 users to switch, but IMHO, as a person that's not too
      knowledgeable about IPv6, I don't see why technically a migration has to be too difficult.


      The problem with the 6bone is that it pretty much requires a static IP address to connect to, and more importantly, that there are no free service providers (that I know of) which allow you to run it through a firewall.


      If you want to deploy ipv6 really fast just create a PPTP tunnel and a freenet. With the ability to get a static block of ipv6 addresses which work through a dynamic IPv4 (via PPTP), and IPSec (which is standard on ipv6), you can easily create a freenet-like system. The idea is that each of your fowarded connections go through a separate IPv6 tunnel.


      Implement something like napster, provide an easy to use installer, and provide the 6bone tunnel, and IPv6 will be deployed in a matter of months. Plus you can probably escape a lawsuit since the only service you're providing is an IPv6 tunnel. Release the napster client part anonymously.

      --
      ok then your [sic] infringing on my copyright! Could you as [sic] me next time before STEALING my comments for your own?
    3. Re:6-BONE? by LiteForce · · Score: 2, Interesting
      It's a nice idea but I have been trying to join the 6bone for absolutely ages now.

      My upstream ISP (Demon Internet) is a participant in the 6bone network; so I e-mailed their 6bone contact and requested a small allocation of IPv6 addresses with which I could use on my internal network (all Linux; therefore all capable of IPv4).

      I received no response from them whatsoever after three seperate e-mails. I *want* to switch away from IPv4, but my upstream ISP won't let me, while they are making out to the outside world that they are 'spearheading' the IPv6 revolution by announcing that they are a member of the 6bone.

      Yes, I have considered applying to other 6bone networks, such as JANET and other UK ISPs, but my upstream ISP would have been ideal for my IPv4IPv6 tunnel (zero routing overheads). Besides, it is a matter of principle.

      Anybody running a 6bone site reading this care to comment ? - before you say it, yes, I fulfil the criteria for joining the 6bone (according to http://www.6bone.net/ anyway).

      --
      "Be vewy vewy quiet, I'm hunting wuntime ewwors!" - Elmer Fudd
    4. Re:6-BONE? by Wesley+Felter · · Score: 2

      I'm guessing MS can buy all the IPv4 addresses they need. Why should they move to IPv6?

    5. Re:6-BONE? by Cato · · Score: 2

      IPv6 doesn't have 'Class A' blocks - everyone can get a large amount of address space with IPv6, not just the mega corporations. The main drivers for IPv6 are going to be:

      - 3G mobile phones - IPv6 is mandated by UMTS R5, the 3G technology for GSM network operators

      - Asian markets - Asia was late to the party in IP, and only got a tiny amount of IPv4 address space. This is why NTT is already running a commercial IPv6 service in the US and Japan.

    6. Re:6-BONE? by Cato · · Score: 2

      Does PPTP even work with IPv6? I doubt it, since it's not an IETF standard. An easier way to create tunnels is to use 6to4 - this allows any two IPv6 networks to dynamically create a tunnel over the IPv4 backbone, making it very easy to do this sort of thing. You could probably use IPsec in transport mode to secure the tunnel as well, but in practice IPsec is not too good for freenet etc, as it demands either pre-arranged keys (symmetric or RSA certificates) or a centralised certificate authority. Check google for 'opportunistic ipsec', though.

  21. It's time to stop and think. by perdida · · Score: 2

    Do we want everything connected to the Internet?

    Who has pushed for universal connectivity of most things to the Internet and why do they want it that way?

    Is the Net reaching a growth limit because of the IP numbers being used for the benefit of the Net and efficiency in the transfer of information, or so New Yuckers can trade stocks on their cellphones?

    Consider the NASDAQ, which has sold its soul to technological change. It expands its trading capacity every year. The sellers of trading tools anticipate this expansion, and the traders overload the system again every year, driving a further expansion.

    We can get to longer and longer fingerprints for our digital devices, or we can decide to better allocate IPs. This decision is directly related to our decisions about what we eventually want the Internet to be for.

    Do we want the Internet to be a marketplace, a teacher, a trainer? I would rather have limited resources allocated to training, skills enrichment, and exposure to art and culture, than to a thousand million Doom-playing boxes and gabby cellphones.

    Think about it. Which places in a given city get services such as DSL first? Is that the best social choice, for both the city and the Internet?

    1. Re:It's time to stop and think. by GiorgioG · · Score: 1

      See, unfortunately - it's not about what we want. It's about what business wants. If business wants joe schmoe to want all of his stuff on the net, they'll throw some marketing genius behind it, add some "convenience value" to joe's life and he's happy....

    2. Re:It's time to stop and think. by dpilot · · Score: 2

      And whether we get IPV6 or not, and whether Sears wants my next refrigerator to be on the Internet, or not...

      I'll have a firewall at the boundary of my house. *Maybe* I'll poke a point-to-point hole so Sears and my fridge can exchange sob stories. Maybe not.

      --
      The living have better things to do than to continue hating the dead.
    3. Re:It's time to stop and think. by Gilanthis · · Score: 1

      What people want(Yes this includes buisnesses which are after all just a collection of people) is what happens. If people didn't want to use the internet to play Doom as you put it then would there be thousands of boxs doing it..Again as you put it. Why should you or anyone else decide what the internet is or isn't for? Even more so why should the Goverment(God help us) decide this? IP addresses should be as easy to come by as possible. The fewer addresses and the more hacks(NAT and so on) that are required to use the internet the more expensive the internet will become. This will result in few home users being able to use the internet and the rise of big buisnesses using it. Eventually the internet will recess back to somthing that only large orginaztions can afford to use. Then it will undobutably come back to the home user so that companies can sell all their stuff to the masses via it...But it will never again be the place it is today or was 10 years ago. The internet is best when self regulated.

      --
      Duct tape is like the force. It has a light side, a dark side, and it holds the universe together.... Carl Zwanzig
    4. Re:It's time to stop and think. by CrazyBrett · · Score: 2, Insightful
      "Do we want everything connected to the Internet?"

      Whenever I've thought about IPv6 and its "suggested applications", this is the first thought that's come to mind. The answer is clearly "no, I don't want the entire world to be able to connect to my fridge." But don't you imply that level of connectivity when you assign your fridge an IP address? Not necessarily. What we should see with the switch to IPv6 is a shift of focus from "addresses" to "routes". Let me explain:

      Right now, particularly in the ISP world, packet destinations are very address-centric; each customer has one or two IP addresses, and if a packet arrives at those addresses, it is delivered to the customer, either directly or through a hub.

      With the number of IP addresses available in IPv6, it would be silly for an ISP to only give you a few addresses, or even a few hundred addresses. Instead, they will give out entire class B networks, and (here's the key), simply route any packet addressed to that network over the customer's connection. Since you can't just stick several thousand devices on a lan, having a full-featured router in your home will be a requirement to sort out all the incoming packets.

      Once there's a router in everyone's home, it's trivial to set them up as firewalls so that someone can't hack your fridge from the outside. Sure, your fridge can still initiate a connection to the supermarket and order more milk, and everything works with no NAT hackery, since the fridge has its own IP address within your subnet. Or, you could require authentication when connecting to the fridge from outside, but still be able to address it by its unique IP from anywhere.

      So, the bottom line is: more IP addresses leads to required home routers, which are trivially set up as firewalls.

      -- Brett

    5. Re:It's time to stop and think. by gorilla · · Score: 2

      But you could do this right now with NAT and a single address. Why do you need IPv6 to do it?

    6. Re:It's time to stop and think. by MajroMax · · Score: 1
      But you could do this right now with NAT and a single address. Why do you need IPv6 to do it?

      No, you cannot. If my fridge were connected to the Internet via NAT, I would not be able to get to it from the outside. A demonstration for you and everyone else who thinks that NAT is a cure-all:

      My house's IP is 185.12.16.192 [not my real IP. Don't try it. I don't know who's it is, if anyone's]. That IP is directly connected to a Linux NAT box [or Linksys router, if you prefer.] By definition of NAT, it takes outgoing requests from local bits [192.168.x.x], munges with the TCP/IP headers, and routes them to the outside world. It then keeps watch for reply contacts and does the reverse header-munging.

      My fridge is connected to my local network. From its point of view, its only IP is 192.168.1.17.

      Now, I'm at the supermarket and want to check how much milk I have left. I can get to the house no problem [see above IP], but there's no way I can get to the fridge. I cannot simply direct a request to the fridge because there is no way for me to reach the fridge -- it has no address from my point of view. The NAT box won't help, either, because my connection is not in reply to a fridge outgoing request, so the NAT box doesn't know to do its header munging/routing. It is possible to get around this through port forwarding or a seperate protocol, but the former is an ugly hack and the latter is an ugly hack that requires a special forwarding deamon to be running on the NAT box.

      With IPv6, the only bits of the system that still remain are the local router, the fridge, and the supermarket. This time around, the fridge has an outside-addressable IP. The local router doesn't need to do any header-munging, and in fact is transparent to the entire process.

      Implementations of NAT to hide extensive local networks function to approximately the same degree as trying to place a phone call to the Andromeda galaxy -- you don't exactly know where your recipiant is, so you can't get the message to it.

      --
      "Evil company X is threatening to restrict our rights! Let's all get together to stop--OOOH! SHINEY!!!" -- AC
    7. Re:It's time to stop and think. by gorilla · · Score: 2

      Yes you can. You're thinking of the IP Masq type of NATing, where the system dynamically looks for outgoing connections, and NAT's them. Many systems allow static NATs to be defined, so that incoming connections are NATed as appropraite. If you connect to one port, you're NAT'd to one IP address/port. If you connect to another port, you're NAT'd to a different address/port. This is not theoretical, I do it right now every day, where we have about a dozen services distributed to different machines.

    8. Re:It's time to stop and think. by KjetilK · · Score: 2

      Do we want everything connected to the Internet?

      I don't know about you, but I certainly want it. I want a single PDA that can do everything, and that's always connected. I want a big desktop computer that is the frontend for all the real work I'm going to do. I want my fridge connected so I can check what's in there from my PDA when I'm standing in a shop, I want my washing machine connected so I don't need to go home before I would know it's finished, and I want my car connected so I can lookup in maps, and download ogg vorbis files to the stereo.

      And I'd be happy to pay for it.

      What I'm worried about are the privacy issues. With all this being logged, things can go wrong. We need laws that says you're not allowed to record a lot of information. Strong privacy laws. And that you own whatever information is recorded about you.

      Do we want the Internet to be a marketplace, a teacher, a trainer? I would rather have limited resources allocated to training, skills enrichment, and exposure to art and culture, than to a thousand million Doom-playing boxes and gabby cellphones.

      As I see it, one of the fundamental pillars of the web is that it is universal. It has to be all. It has to be a marketplace too, but we need to make sure it isn't only a marketplace, because if it becomes, it dies. Now, the web is part of the internet, so the internet must be universal too.

      --
      Employee of Inrupt, Project Release Manager and Community Manager for Solid
  22. The Road Ahead by BierGuzzl · · Score: 2

    I can't wait for the book! It'll be filled with commentary equally lacking in technical details, written by a mildly deluded harvard graduate.

  23. NEVER FEAR CONSUMER UNITS! by sllort · · Score: 2, Funny

    "For instance, do people really want a unique address for a refrigerator -- allowing hackers to spy on individual eating habits -- or order you a truckload of milk?"

    Do not fear, Consumer/Citizen #238o47234-9. We have taken care of the threat of the evil hackers. We have applied Purchase::Courts in order to prosecute, convict & incarcerate Evil Hacker Units for crimes we think they'll commit in the future, preventing them from ever happening. We call this "time-shifted law enforcement".

    Do not fear, Consumer Units. We will prevent Technology::IPV6 from being used to order too much Commodity::Milk.

    Everything has been rendered extraordinarily safe.

    1. Re:NEVER FEAR CONSUMER UNITS! by psych031337 · · Score: 1

      I think my public key is fishy... [slashdot.org]


      I'd like to point out that (slashdot.org == goatse.cx) by now...

      --
      +++ath0
    2. Re:NEVER FEAR CONSUMER UNITS! by Anonymous Coward · · Score: 0

      If you had been using a Real Browser, that link would have given a broken page =)

  24. good, fix DNS too while we are at it by abde · · Score: 2

    quoth the article:

    To ease the transition, engineers are developing ways for networks on v6 to talk with those still on v4. It'll be like running two separate Internets, with boxes in the middle to connect and translate seamlessly between the two.

    great! if we are gonna effectively have two internets anyway, lets have the IPv6-based Net do away with the current DNS monopoly and let anyone register a TLD. .web, .sex, .JoeSchmoe, whatever. Open DNS is the way to go.

    all someone would have to do is, write a plugin for a browser that lets it seamlessly navigate IPv6 networks. But at the same time, also allow the user to choose from a open list of DNS servers at the same time. YOU choose your root ! as it was intended to be.

    my apologies to JoeSchmoe for any offense. thpbt :P

    --
    Don't blame me - I voted for Howard Dean. http://dean2004.blogspot.com
    1. Re:good, fix DNS too while we are at it by Anonymous Coward · · Score: 0

      "The only thing IPV4 is used for is surfing the web... just write a browser plugin and its all fixed!"
      - slashdot://abde

  25. Re:IP6 MLP by DaSyonic · · Score: 2
    Here's a good FAQ

    Or checkout the IPv6 project page

    --

    Linux: Because a PC is a terrible thing to waste.
    James Brents
  26. Quit complaining about it already! by Rackemup · · Score: 2
    "Stanford University and Massachusetts Institute of Technology each got a block of 16 million IP addresses -- more than what's available to latecomers, including the entire country of China"

    someone was being greedy eh? Comeon folks, time to share..

    Seriously though, the article does a good job at least trying to cover all the bases even if some of the arguements are weak. We all know that it's a big change and that it's going to take years to make the transistion from 32 bit addressing to 128 bit addressing, but the people saying "why fix it if we dont have a problem?" had better get their heads out of their asses. It's just like standing in the street and saying "why should I buy a car when my horse and wagon works fine?".

    I agree that some ideas are way over the top (tell me again why my toaster should be networked??) but with computers getting smaller and cheaper the number of networked devices will continue to grow. We need a new system that can handle assigning addresses to them all. It's going to take time, effort and money to switch everything over so get started and quit complaining.

    1. Re:Quit complaining about it already! by p_trinli · · Score: 1

      It's just like standing in the street and saying "why should I buy a car when my horse and wagon works fine?"

      No, it's like saying, "Why should we use 4-digit years in our software, when 2-digit years work fine?"

      ...but with computers getting smaller and cheaper the number of networked devices will continue to grow.

      There is a perfect analogy in my state of Oregon--recently, we had to add another area code, because cell phones and other devices were taking up so many seven-digit numbers.

  27. Good summary, Bad Solution by jazmataz23 · · Score: 1
    Government Regulation is *NOT* the answer! Where would we be if government regulated Token Ring networking?
    Government regulation is inherantly out of date. Didn't you read that article on Be the other day? The fellow prosecuting the Microsoft case didn't even have an email address!
    Government regulation hasn't helped HDTV either; that's been in place for years in Japan, and a while in the US, and few if anyone bothers with it, because they don't see much of it. I'm a widescreen buff, and I love it, and a lot of my friends who've seen a DVD on a real widescreen are very impressed. Once the pricepoint comes down a little further you'll see a lot more adoption.
    On the networking side, I'd like to see IPv6 take off, but not by a government mandate! Saints preserve us.

    jaz

    --
    Death to Argument by Slogan!! (This post twice-encrypted with ROT-13. Replies not using same will be ignored)
    1. Re:Good summary, Bad Solution by Anonymous Coward · · Score: 0
      Government Regulation is *NOT* the answer!

      So, you'd like the markets to decide? Markets are fair and always lead to the most profitable and ethical solution?

      Grow up. Government regulation can be a good thing too.

    2. Re:Good summary, Bad Solution by jazmataz23 · · Score: 1
      Man, Black/White with everyone on slashdot.

      Let's talk shades of grey; just because a government mandate isn't the answer doesn't mean the "free market" is. Government regulation rarely has anything to do with what "the people" want. Sometimes that's a good thing; people want to be able to buy guns and shoot their neighbor because "his dog keeps pooping in my yard". I think gun control is an excellent example of government regulation. The government should stick to issues it's good at though, and government is *not* good at technology.

      Tech moves too fast, and yes, adoption is market-driven. The market doesn't always come up with the best solution (*cough* Betamax *cough* BeOS) but it muddles through. The people that know & understand the issue are aware of the problem, and are working on a way to fix it. NAT buys us some time until IPv6 or whatever comes along. But the Government saying all broadcasts must be in HDTV hasn't helped; I doubt mandating 20% of all internet traffic being on IPv6 would help either.

      Telling others to grow up is not exactly intellectual discourse. You don't know who the hell I am. Did you even bother to read my bio? That'll give you a small clue.

      jaz

      --
      Death to Argument by Slogan!! (This post twice-encrypted with ROT-13. Replies not using same will be ignored)
    3. Re:Good summary, Bad Solution by Anonymous Coward · · Score: 0

      A) Betamax wasn't a superior standard http://www.urbanmyths.com/brands_beta.html

      You may not like the outcome of what happens in a free market, BeOS may tank even though you think everyone would be much better off by using it. If the product is really better and cheaper it will prosper. Switching to BeOS from windows incurs a cost (purchase, training). Even if BeOS were free, it would still incurs intsallation & training costs. The extra oooh-aaahs of BeOS weren't enough for most people to justify all the costs, hence it is dying. Simply being 1% technically superior isn't much of an advantage when 99.999% of the population has never heard of your product.
      Government regulation is only good at preserving the status quo. All regulation rewards someone, people will fight to get it and then fight to keep & expand it once it is in place.

      It is too easy to turn to government as a lever to get something you want implemented. Restrain yourself, do it the right way (get other real people to work with you).

    4. Re:Good summary, Bad Solution by jazmataz23 · · Score: 1

      It is too easy to turn to government as a lever to get something you want implemented. Restrain yourself, do it the right way (get other real people to work with you).

      Which is really exactly my point.

      [RANT]
      I'm starting to think it's insanity trying to make a nuanced point on /.; no matter what you say, someone's going to pidgeonhole you one way or another. First I say that government mandating IPv6 is the wrong direction and AC yells at me for being a Dittohead, against any government regulation. I explain my point, that I'm not against all gov't regulation, just where it's going to cause more harm than good. Then AC tells me not to rely on the government for everything.
      [/RANT]


      Actually, I think you make an excellent point, and I didn't know that in the beginning Beta was not technically superior (I was six when the video wars were at their peak). I'm only familiar with the current incarnation, which is pretty damn good. No touching a DVD, but excellent for a tape.

      Anyway, we've gotten way off topic, but thanks for at least something to do on a slow Tuesday.

      jaz

      --
      Death to Argument by Slogan!! (This post twice-encrypted with ROT-13. Replies not using same will be ignored)
  28. More than just address space by Jason+Cwik · · Score: 1
    IPv6 has more features than just an expanded address space. I've heard that address spoofing should be impossible with v6. It also has some routing enhancements to make the large address space more routable...

    ARIN(the people that assign IPs in North America has more info)

    1. Re:More than just address space by Anonymous Coward · · Score: 0

      IPv6 has more features than just an expanded address space.


      I was wondering why nobody seemed to be aware of that. With the push for streaming media, IPV6 seems almost mandaory.

  29. Offtopic Search by sharkey · · Score: 2

    Try searching for IPv6, which is the topic at hand.

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  30. Re:IP6 MLP by foo+fighter · · Score: 1

    Thanks for the useful links.

    I also found my problem; You need to search for "ipv6" instead of "ip6". Duh.

    --
    obviously no deficiencies vs. no obvious deficiencies
  31. Don't forget this famous prophesy by Tony+Shepps · · Score: 2

    "If we don't switch to ipv6 by late 1997, the net will run out of addresses."
    -- many many pundits

    1. Re:Don't forget this famous prophesy by MagikSlinger · · Score: 2
      "If we don't switch to ipv6 by late 1997, the net will run out of addresses."


      We did. Ever heard of NAP? :-)


      --
      The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
    2. Re:Don't forget this famous prophesy by Anonymous Coward · · Score: 0
      Ever heard of NAP?

      No. What the hell are you talking about?

    3. Re:Don't forget this famous prophesy by alcmena · · Score: 1

      Nope, never heard of NAP. Though, NAT did keep us going for a while longer.

    4. Re:Don't forget this famous prophesy by Anonymous Coward · · Score: 0

      Uhh - you mean Network Address T ranslation?

    5. Re:Don't forget this famous prophesy by Anonymous Coward · · Score: 0

      He was saying you seem rather cranky, and thus need a NAP. I have to say I agree based on your message.

    6. Re:Don't forget this famous prophesy by b1t+r0t · · Score: 2
      We did. Ever heard of NAP?

      We didn't. Ever hear of CIDR?

      So what's this NAP you're babbling about?

      --

      --
      "Open source is good." - Steve Jobs
      "Open source is evil." - Microsoft
    7. Re:Don't forget this famous prophesy by laeraun2 · · Score: 1

      One of the great things about IPv6 is that we won't need NAT's. We will run out of addresses, its just a matter of time. Think about the future where we will have our fridges and light switches hooked up to the net via thier own ip addresses. IPv6 allows for 1000+ adresses per square metre on earth.

      --
      Error: Erection reset by beer.
  32. Vital IPv6 links by DaSyonic · · Score: 3, Informative
    --

    Linux: Because a PC is a terrible thing to waste.
    James Brents
    1. Re:Vital IPv6 links by Anonymous Coward · · Score: 0

      http://www.kame.net/

  33. NO IPs FOR DEVICES!!! by scott1853 · · Score: 2

    If you want to have access to 20+ devices in your house while you're away, then giving each one an IP is ridiculous. You get a server for the house, and communicate with each of the devices through the server. The server has an IP address, the devices have names (or the standard internal network addresses, 192.168.0.x). You access the devices by name, using the server as a proxy. I'm sure somebody will come up with some XML based protocol for this if they haven't already.

    Also, right now the worlds population is about 6 billion, and 4 billion address are possible with IPv4. Based on everybodies estimates on the adoption rate of internet access, we still have a decade before we're screwed. So, take the time to get it right instead of screwing up everything at once.

    1. Re:NO IPs FOR DEVICES!!! by Anonymous Coward · · Score: 0

      "Each person on the internet only NEEDS one IP address. And companies have NO NEED for one!"
      slashdot://scott1853

    2. Re:NO IPs FOR DEVICES!!! by AKAImBatman · · Score: 1

      right now the worlds population is about 6 billion, and 4 billion address are possible with IPv4.

      Actually, you have to cut that number in half (IIRC), A large portion of IPV4 was reserved for private networks, routing, and other such BS. As a result, the address space is FAR smaller than one would expect.

    3. Re:NO IPs FOR DEVICES!!! by scott1853 · · Score: 2

      Maybe it's not too late to include an extra byte in the IPv6 header to indicate the senders IQ. It would make filtering idiots much easier.

      Besides, since all the dot-com companies have, or are about to go out of business, the IP addresses will just be recycled.

    4. Re:NO IPs FOR DEVICES!!! by farmhick · · Score: 1

      There are not 4 billion address available, even if they are possible. As the article pointed out, MIT and Stanford each have a block of 16 million. Plus as you go to Class B and Class C networks, and subnet them, you lose large chunks of addresses. Plus many of the ranges are not available at all right now, such as 10.0.0.0, 192.0.0.0, and I think all of 225.0.0.0-255.0.0.0.

      So how do developing countries in Africa get IP addresses when most of the available ones are owned and assigned in the US? While I agree that gving the oven an IP address is stupid, I would like to have all the computers in my house connected directly, not thru the Linksys router.

      --
      I have to stop wasting so much time reading Slashdot. It's interfering with my crystal meth addiction.
    5. Re:NO IPs FOR DEVICES!!! by nairnr · · Score: 1

      4 billion addresses may be available, but there is a lot of wasted address space. If you consider MIT and Standford as an example, the each have a class A giving them 16 million addresses each. Do you think every one of those is spoken for? Not very likely at all. It is not an issue of the addresses available, but how it can be effectively allocated.

    6. Re:NO IPs FOR DEVICES!!! by CyberKnet · · Score: 2

      No, seriously... your assumption that each person on the internet only needs one IP address is wrong. There are legitimate reasons why a person might need two IP addresses.

      do you an internet connected PC at work?
      Do you use only one OS, or two OS on one computer? Some people have two computers for that.
      Do you use any applications that will not work under NAT without a server in the middle.

      In my opinion, proposing that only individuals need IP addresses, and that they only need one is preposterous. There are more cases than I can think of or list here where a person might require more than one IP address.

      There is a world outside your box.

      CyberKnet (the original poster)

      --
      Video meliora proboque deteriora sequor - Ovidius
    7. Re:NO IPs FOR DEVICES!!! by cfulmer · · Score: 1

      So, assuming that the device has a NIC with a unique MAC address, the IP address does not need to be assigned to the NIC -- it ought to be determinable by the network number on which the machine sits -- the right 48 bits of the 128-bit IPv6 address are intended for the MAC address.

      IPv6 does a lot more than quadruple the address space -- it makes things like mobility and redundant routers much easier. In doing so, it actually wastes a large percentage of the address space.

      Also, while it's true that IPv4 theoretically has 2^32 addresses, we need to remember that there's a lot of deliberate underuse there as well -- for example, the multi-cast range, the numbers reserved for private subnets & so on.

      In addition, just the way in which addresses have been doled out (class A addresses, for example) has yielded a lot of waste. But, I don't think that the right solution is to "undo" those things -- "Ok, MIT, we need a bunch of those addresses back, and we don't care how much you have to spend to do it." Not only does this cost money, but it means that your central routing tables get really messed up -- now you can't just say "55.something..." Ok, gotta route that to Boeing. Instead, you replace that one entry with 65,000 entries. (Assuming class C addressing.) Ick.

      NAT works reasonably well if you're operating in client/server mode -- ie your client is behind a firewall and the only time the NAT host receives something for the client, it's in response to a different client message. If you're peer-to-peer or running servers, NAT really gets in the way. Ever try running two web servers at port 80 behind a NAT server? Doesn't work.

    8. Re:NO IPs FOR DEVICES!!! by Anonymous Coward · · Score: 0
      do you an internet connected PC at work?

      Que?

      Do you use only one OS, or two OS on one computer? Some people have two computers for that.

      And both of them can be NATted.

      Do you use any applications that will not work under NAT without a server in the middle.

      Such as? I mean, there are some peer-to-peer problems with NAT, but does a toaster need direct connectivity to the web? NAT the house and VPN to the home network. Done.

    9. Re:NO IPs FOR DEVICES!!! by Anonymous Coward · · Score: 0

      Yes, but you're forgetting: NAT is shite.

    10. Re:NO IPs FOR DEVICES!!! by certsoft · · Score: 1
      Since there are tens of thousands of TCP and UDP ports available for every IP address it might be possible to give each device the same IP address but a different port number to respond to. The only catch I can see is ARP handling for Ethernet.

      Then of course, I could be wrong.

    11. Re:NO IPs FOR DEVICES!!! by CyberKnet · · Score: 2

      You said nothing of anything except people using computers, and that there was enough for one ip address per connected internet user. I am arguing that even at that basic level you were (and are) wrong.

      FTR, P2P is used (And always has been used) for more than Napster/Clones and IM. Anything that works without going via a server to find the end place is P2P.

      Some mail clients still deliver mail this way by delivering directly to a domains MX instead of to their local sendmail daemon. Its not some new thing.

      --
      Video meliora proboque deteriora sequor - Ovidius
    12. Re:NO IPs FOR DEVICES!!! by Anonymous Coward · · Score: 0

      >Do you use only one OS, or two OS on one computer? Some people have two computers for that.

      And both of them can be NATted

      and neither of them will function properly.

    13. Re:NO IPs FOR DEVICES!!! by Anonymous Coward · · Score: 0

      Hehehe. you make it sounds like this is not already going on... when I 1st got into the Internet business, I was AMAZED to see 26,000 routes in the forwarding table of our big ass cisco... When I finally got out of the operations oriented side a couple of years ago, leakage, poor admin, and general growth occasionaly saw the tables pushing close to 100k routes...

      IPv6 will only make this worse, not better. So, unless you want to pony up the bucks to intall uber super computers to replace all the public IP routers that have full tables, don't expect to see IPv6 coming to you anytime soon. If you are THAT hot to try it, there are a couple of tunneling services that will let you setup an IPv6 connection to them. (mine was up for about a year, then I got tired of playing with it, so I pulled it down, got to love BSD!)

      As for running out of public address space... please. These are the same marketing droids that cause you to have to buy a new PC every other minute because they persuaded programers to increase the size of your word processor by another 20Megs of drive space, the processor requirements 25%, and the MEMORY requirments 100% over the previous version...

      Now that the Internet growth 'hockey stick' has finally peaked, I think growth rates for more ip devices are going to stabilize at a fairly low rate, and we will see more growth in raw bandwidth wasted.. er used... ;)

      What SO many people tend to forget is that there are a finite number of 'power users' that need all the functionality of a 'real' IP address. the vast majority of people are pleased as punch if they can pull up thier favorite web site, and check thier email.

    14. Re:NO IPs FOR DEVICES!!! by DavidTC · · Score: 1
      Um, no. IPv6 makes routing easier, not harder.


      IPv6 addresses follow a heirarchy. You never need to know more than the addresses of the people above and below you. And the addresses of the people below you will all be subsets of your addresses, and you will be a subset of the people above you. No exceptions allowed.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  34. Not So Famous... by JeremyYoung · · Score: 1

    If noone can prove that it's unsafe to fly, we fly - - Pre-Challenger NASA mindset.

    Jet fighters won't help us win the war, let's move those R&D funds elsewhere - Adolf Hitler, 1942

    Mp3? What's that? - RIAA, 1996

    --

    Go Lakers!

    1. Re:Not So Famous... by ethereal · · Score: 0, Offtopic

      "They can't hit anything at that dist-" -- unknown (deceased) American Civil War Confederate General.

      --

      Your right to not believe: Americans United for Separation of Church and

    2. Re:Not So Famous... by jandrese · · Score: 2

      If noone can prove that it's unsafe to fly, we fly - - Pre-Challenger NASA mindset.
      Doesn't seem to strange when you consider how unbelievably complicated and dangerous something like going into space is. If somone has proof (and a fix) to some deadly problem I can see them stopping, otherwise it's all just theoretical mumbo jumbo and we'd still debating launching our first rocket. Even now space shuttle launches are risky, it's only a matter of time before someone else dies in them.

      Jet fighters won't help us win the war, let's move those R&D funds elsewhere - Adolf Hitler, 1942
      Almost certainly true. One of Hitler's problems was his belief in superweapons. Germany spent countless R&D dollars on wasted projects during the war that would have (in the end) been better spent on making Panthers more reliable and simply producing more of them. Jet fighters wouldn't be viable for several years after 1942, even if Hitler decided to spend massive R&D dollars on them. By the way, Germany DID build jet powered planes near the end of the war, but their affect was minimal (the war was already pretty much lost by that point).

      Mp3? What's that? - RIAA, 1996
      Shouldn't that be: MP3? Our existing copyright laws should cover that nicely, but just to be sure, let's go and buy some Congressmen.

      --

      I read the internet for the articles.
    3. Re:Not So Famous... by MindStalker · · Score: 1

      The statement was about the O ring defect, which was known about before the challenger mission, and many people in NASA said that there was a high chance of failure in. NASA management basically said, before the challenger launch, which many were trying to delay to fix the problem, that unless it can be proven that its going to blow up, they are going to fly it anyways.

  35. The Road Ahead by Amazing+Quantum+Man · · Score: 1

    Greetings. We represent Mr. William H. Gates III. Mr. Gates owns the copyright on the phrase "The Road Ahead", as it was the title of his book. You are in violation of the DMCA. Please remain where you are, until we can get federal marshalls to come and arrest you.

    Thank you,

    Dewey, Cheatham, and Howe, Attorneys at Law.

    --
    Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  36. Why? So that peer-to-peer and servers will work by fmaxwell · · Score: 2
    If we stick with IPv4, the argument will be made that we are running out of IP address space. Residential Internet connections will switch over to NAT or PPPOE "to conserve valuable IP address space." When that occurs, it will break just about everything from peer-to-peer networking to home FTP and web servers.


    So who would be in favor of that? Just the RIAA, MPAA, SPA (Software Publishers' Association), BSA (Business Software Alliance), and every other organization that believes that elimination of peer-to-peer and residential FTP and web servers would reduce piracy. ISPs would love it because servers on residential connections sometimes use an inordinate amount of bandwidth. Law enforcement would be happy because ISPs would have to process the packets, meaning that they had an easy way to monitor which user connected to which IP addresses. And ISPs could more easily perform content filtering if, say, Adobe's lawyers wrote a letter and said "IP address xxx.xxx.xxx.xxx has a downloadable program that decrypts our e-books. Please assure that your users cannot access that IP address."

  37. NAT considered harmful. by 3247 · · Score: 1
    NAT is only a hack but not a real solution.
    • What happens if two large companies merge and decide to hook their NATed networks together?
    • What happens if broadband Internet access becomes more widespread with a need of additional IP addresses?
    • What happens if you want to play online games from two computers in your home network (which share a NATed address)?
    • ...

    NAT is harmful because it delays the use of IPv6. NAT sort of works most of the time and where it does not work IPv6 is not yet a real alternative.
    --
    Claus
    1. Re:NAT considered harmful. by Jubedgy · · Score: 1

      Well, I don't know about you, but with a few exceptions I can play games simultaneously from any comp on my lan...halflife (mods), q3, UT, SS, etc...I can even play on the same server!

      --Jubedgy

      --
      Si hoc legere scis nimium eruditionis hebes
    2. Re:NAT considered harmful. by Anonymous Coward · · Score: 0

      I can play games simultaneously from any comp on my lan

      Wow, you must be good!

    3. Re:NAT considered harmful. by Yokaze · · Score: 1

      Jay, thats what's the net needs, playing from any device on the net some games.

      Ever tried to provide some services, preferably simultaneously?

      Granted, checking the status of my vcr from the net is not really necessary, either :)

      --
      "Between strong and weak, between rich and poor [...], it is freedom which oppresses and the law which sets free"
  38. It isn't the OSen, It is the hardware! by Marvin_Runyon · · Score: 1

    From what I understand, Linux and Windows NT have had IPv6 support for quite some time now. The bigger barrier to adoption is that router technology for IPv6 is not quite ready for primetime. When Cisco and Nortel get their act in gear, IPv6 should be up and running in the wild in no time.

    -Marvin

    1. Re:It isn't the OSen, It is the hardware! by Anonymous Coward · · Score: 0

      Nortel (Bay Networks) have been shipping IPv6 code for a while. Never tried it, but I can't imagine how it's possible for their IPv6 code to be all that much worse than their IPv4.

    2. Re:It isn't the OSen, It is the hardware! by Anonymous Coward · · Score: 0

      Its not the hardware, its the software. The IPv6-stacks are already being tested by machines connected to the ipng-tunnels. But when the user-space applications become ipv6-aware then we hit the jackpot.

  39. Re:IPv6 was also designed to support interplanetar by RKloti · · Score: 1

    I seriously doubt that. Radio signals to Mars would take ~20 minutes either way, which, unless a method of FTL communications develops, means the physical difficulties of real-time interplanetary communications are much more significant than the tech ones. Not to mention solar flares and what you're going to do when Mars is on the other side of the Sun. (you could use a relay, of course, but the times would be even longer) We can, however, technically use IPv4 to communicate with a theoretical moon base or a free floating colony ala 2001.

  40. Embeded Devices Will Be The Hardest To Change... by Black+Art · · Score: 2

    The hardest part to change will be all of these new embeded devices that use IPv4 at some level. Not to mention all the cable modem and DSL routers and other misc equiptment that does not update easily.

    Try explaining to the average AOL user why his new net radio gizmo no longer works. Or why he has to replace his cable modem firewall when it works just fine.

    And I am not going to even try and think about what IPv6 will look like once Microsoft gets their hands on it...

    --
    "Trademarks are the heraldry of the new feudalism."
  41. Seamless Intergration by El_Nofx · · Score: 1

    That is a good article with a lot of points the ctitics miss, It will be an almost seamless intergration for the average user. Most won't know anything has changed. Almost every computer, router and switch will be replaced within the next 10 years anyway and Windows 2000, Xp and beyond provide support for it, with routers and such a small firmware upgrade will only be neccessary. That is routinely done anyway. So what is the problem here?

    Also i would like to address the statement
    "The US hogged all of the IP addresses"
    SO WHAT, we invented the internet. Too bad if we didn't think about who would need addressess in the future. Noone knew if it would even work.
    It wasn't designed for what it is doing now.
    It was desinged for text messages across modems, not video confrencing and counter strike. IP need to be updated.

    --
    It's not the OS it's the user that sucks. If it's user friendly, you get stupider people. - clinko
    1. Re:Seamless Intergration by Anonymous Coward · · Score: 0

      Todays fastest routers and layer 3 switches implement IPv4 in hardware. They cannot be upgraded. IPv6 over IPv4 tunnels or local network NAT style hacks will be the only option to get good use out of those without replacing them.

  42. Not broke!?! What!?! by genericid · · Score: 1

    Who says it's not broke? Large ISP/busineses? These institutions find it easy to get a large address block of IP's, but when I call my ISP to get just a few, they chage me an additional $20 a month (for 5 usable IP's)!!!! Maybe if there were more available, the smaller ISP would be willing to dole them out without charging extra, wich would then force the larger ISP's to do the same. More IP's would make them much less like a commodity and make them easier to get a hold of. I would really like to not have to NAT at home.....

  43. Those damn engineers! by Mtgman · · Score: 1

    The communications system that glues the Internet together was designed for no more than 4.3 billion computers and devices -- thought to be plenty 20 years ago. Half the connection points have already been assigned, and the life span for the remainder is estimated at five years. At that point, a "No Vacancy" sign may have to go up.

    First the Y2K bug, now the IPv4 debacle. You're making technology look bad! How will you ever get widespread acceptance if people think you don't think far enough ahead to have your infrastructure scale?

    Seriously, I think this is going to grow into something like the Y2K thing. Sure people won't be stockpiling on water and food like a few people I know did, but the reporting of this limitation could cause the public to think "Well, if I get involved in this thing, it'll just max out and then I'll be stuck with a useless 3G phone, or whatever."

    Hell, my company is already taking IP addresses away from our servers and workstations and putting us on NAT because they need those IP address spaces for customers. This is a serious problem for the growth and mainstream acceptance of a wired world.

    Steven

    --
    -- I have marked myself unwilling to moderate-- I don't have other accounts to artificially inflate the karma of
  44. NAT doesn't solve the whole problem. by David+McBride · · Score: 3, Informative

    Network Address Translation only provides one-way connectivity. It allows a system behind a NAT to establish connections from external sites and retrieve data.

    What it *doesn't* allow is anyone out on the internet to go and connect to the machine behind the NAT, which is kinda essential for anything beyond web-browsing.

    The internet is not just port 80. Many people treat it as such, and I hope they have fun. But don't delude yourself that you have a full internet connection, because you don't. You've just got a fancy TV with a few more channels.

    NAT is a stop-gap measure at best. IPv6 is essential for allowing the internet to scale the way you want it to.

    Think about it: it's not outrageous that MIT and similar institutions have class-A networks - it's outrageous that *you* don't. IPv6 can fix that.

    Ask your ISP about their plans to upgrade to IPv6 - and what their IP allocation policy will be. If the ISP doesn't intend to give you lots of IPv6 addresses, start looking somewhere else.

    Dynamic IP allocation sucks in the same way that NAT does. Many of the peer to peer projects nowadays, in order to keep functioning, have to build their own namespace and addressing structures just to work around it.

    1. Re:NAT doesn't solve the whole problem. by Matey-O · · Score: 1

      Hmm, what about instant messaging? A technology that:

      1. works behind NAT
      2. allows two-way communication
      3. conveniently solves all those hairy location and p2p issues.

      I believe the APPLICATIONS will become smarter, bypassing the limitations of the network they're running on. In exactly the same way that games programmers overcame inherent limitations in the hardware by clever programming.

      "it's not outrageous that MIT and similar institutions have class-A networks - it's outrageous that *you* don't. IPv6 can fix that. "

      I don't NEED a Class A address. I don't WANT a Class A address. I want a single way of reaching me. That doesn't have to be the IP address!

      That's where something like Mono/Passport is a good solution. Who you are is resolvable and reachable from ANYWHERE.

      --
      "Draco dormiens nunquam titillandus."
    2. Re:NAT doesn't solve the whole problem. by ivan256 · · Score: 2

      Two points:

      ---
      Every time a new car is built do they reinvent the wheel?

      Why should application developers have to do something similar?

      ---

      You don't WANT a class A because you can't imagine what kinds of technologies you could use if you and everyone else did have one.

      Also, Instant messaging doesn't work as well as you say. When people are behind NAT, an intermediary who isn't behind NAT is required. It solves the p2p issue by not being p2p. If you can figure out how to make two machines that are using NAT find each other without an intermediary, and with no advance knowledge held by the NAT devices can you please let the rest of us know how to do it.

    3. Re:NAT doesn't solve the whole problem. by alienmole · · Score: 2
      I believe the APPLICATIONS will become smarter, bypassing the limitations of the network they're running on. In exactly the same way that games programmers overcame inherent limitations in the hardware by clever programming.

      Certainly the applications become smarter, because they have to. But at the same time, the hardware must become smarter. In the game world, video cards have all become much more powerful and support a more consistent set of services than they used to, and game developers benefit from this. By the same token, right now developers have to write their way around NAT and proxies etc., but it can't and won't stay that way: the current Internet architecture is seriously limiting and doesn't even provide particularly good security.

      That's where something like Mono/Passport is a good solution. Who you are is resolvable and reachable from ANYWHERE.

      You're talking about a higher level of operation - directory services, essentially - that still requires an addressing and routing solution at a lower level. The point is that the current addressing and routing mechanism is already obsolete, most people just don't realize it yet because they don't understand what's under the hood.

    4. Re:NAT doesn't solve the whole problem. by CrazyBrett · · Score: 1
      I don't NEED a Class A address. I don't WANT a Class A address. I want a single way of reaching me.

      That's fine, you can use 00.11.22.33.44.55.66.77.88.99.AA.BB.CC.DD.00.00 as your sole internet connection (and drop all other packets). But go ahead, keep those other 65535 addresses in case you decide you want them later. Meanwhile, the businesses that WANT that many addresses can be allocated the same sized chunk as you, and can use all the addresses.

      It's all about flexibility and uniformity. It reduces the address crunch (which does exist, despite the fact that some people only want one address), and it dramatically simplifies routing.

      -- Brett

    5. Re:NAT doesn't solve the whole problem. by Matey-O · · Score: 1

      "Every time a new car is built do they reinvent the wheel? "

      Nope, but they change the way the chassis is built, and they reduce the wires used (serial line comminucation protocol), and they move to a fly-by-wire throttle to reduce mechanical complexity. And, well, Yes. They DO reinvent the wheel (runflats, forged vs. stamped wheels) But that's not the point.

      "You don't WANT a class A because you can't imagine what kinds of technologies you could use if you and everyone else did have one. "

      You're right. I can't! I also don't think much of the population can either. To what end do you need an outside device initiating a conversation with your fridge? Not ALL network applications require two-way communication. The example cited (that of a networked house) would work _just_fine_ in a NAT environment. The MP3 streamer can talk to the AC3 decoder, the Microwave can talk to the fridge, the fridge can initiate an order for milk [shudder]

      Why I'd WANT them to is anybody's guess.

      Between my cellphone, pda, digital camera, watch, and X10 home controller, I'm a) suffering from featureitis, and b)have about 10,000 features in these doo-dads I'll never use....and I'm a certifyable geek!

      Just because you CAN network something, doesn't mean you should, or that the feature will be used.

      --
      "Draco dormiens nunquam titillandus."
    6. Re:NAT doesn't solve the whole problem. by ivan256 · · Score: 2

      To what end do you need an outside device initiating a conversation with your fridge?

      I wonder if I should stop and pick up some milk on the way home. I'll just telnet to my fridge to... Oh wait, the fridge is behind my firewall, and I can't get that information...

      Having a fridge initiate an order is probably a bad idea, but of course one that someone trying to make some money off of the idea is going to try to get you to like. There are way more bad ideas out there then there are good ones. Being able to find out what's in your fridge while you're, say, at the grocery store seems like a good idea though. So, the ideas that we've thought of that can work with NAT aren't too appealing, but the ideas that don't work with NAT are the ones that are truely interesting. Score 1 for having non translated addresses.

      It doesn't matter if most of the population can imagine new devices that would use these address. Only the people who invent them need this ability. They will not have this creative freedom without the addresses being there.

      Not ALL network applications require two-way communication.

      So by your logic no devices should be able to have communications initiated from either end?

    7. Re:NAT doesn't solve the whole problem. by aozilla · · Score: 2

      If you can figure out how to make two machines that are using NAT find each other without an intermediary, and with no advance knowledge held by the NAT devices can you please let the rest of us know how to do it.


      This has nothing to do with NAT. Say you move from the east coast US to the west coast. Would you rather update the routing tables for the entire country or update a single entry in a dns record? A single IP address with a fancy NAT setup could theoretically handle 32,000 computers each listening on a single port.


      IPv6 makes things a lot easier, but it is by no means necessary. If I were creating an IP scheme I'd probably just use GPS coordinates. If you need to move the computer, use DNS or some other app level feature, possibly with a tunnel in the mean time. Routing tables become partitions in physical space. For better privacy, the GPS coordinates could be those of your upstream provider, and then some static/dynamic number tacked on to the end. You can already be tracked to your upstream provider, if you want more privacy than that you need to start tunnelling.

      --
      ok then your [sic] infringing on my copyright! Could you as [sic] me next time before STEALING my comments for your own?
    8. Re:NAT doesn't solve the whole problem. by ivan256 · · Score: 2

      Say you move from the east coast US to the west coast. Would you rather update the routing tables for the entire country or update a single entry in a dns record?

      That's a whole different (unrelated) problem. Of course it makes more sence to change a DNS record, that's how it works now. However, I thought we were talking about devices sharing an address...

      A single IP address with a fancy NAT setup could theoretically handle 32,000 computers each listening on a single port.

      A single IP address with each device that's behind it listening on a different port is possible, but unrealistic. First off, you broke one of the rules: with no advance knowledge held by the NAT devices. If the NAT device needs to be programmed with each new device added to the network then the device is screwed in the mass market. Most people aren't going to reprogram their router. Worse, NAT is being implemented by ISPs these days. People's ISPs definatly aren't going go reprogram their router to open a port every time you get a new device. Hell, you'd be lucky if you could get them on the phone in the first place. Then you have the problem of which device get's which port. For most applications, if they don't have a well known port then they're almost useless since you won't be able to find them. The problem could be solved by inventing some kind of automatic port allocation, and linking it to dynamically assigned DNS entrys, but if every router would need to be changed to support that then you might as well just switch to IPv6 which is already implemented and solves more then one problem.

    9. Re:NAT doesn't solve the whole problem. by aozilla · · Score: 1

      Also, Instant messaging doesn't work as well as you say. When people are behind NAT, an intermediary who isn't behind NAT is required. It solves the p2p issue by not being p2p. If you can figure out how to make two machines that are using NAT find each other without an intermediary, and with no advance knowledge held by the NAT devices can you please let the rest of us know how to do it.


      Say you move from the east coast US to the west coast. Would you rather update the routing tables for the entire country or update a single entry in a dns record?


      That's a whole different (unrelated) problem. Of course it makes more sence to change a DNS record, that's how it works now. However, I thought we were talking about devices sharing an address...


      You were talking about peer to peer applications needing an intermediary. My point was that the entire internet is based upon using intermediaries. When I try to reach http://www.yahoo.com/, it is completely reliant on an intermediary to tell me where yahoo.com is located. I don't think your restriction on using intermediaries is a valid one.


      A single IP address with a fancy NAT setup could theoretically handle 32,000 computers each listening on single port.


      A single IP address with each device that's behind it listening on a different port is possible, but unrealistic. First off, you broke one of the rules: with no advance knowledge held by the NAT devices.


      I get into why it's realistic later. But as for breaking one of the rules, once again, that is not a valid restriction. When telnet to 216.115.108.243 (yahoo.com), it relies on advance knowledge held by the routers between myself and yahoo.com.


      If the NAT device needs to be programmed with each new device added to the network then the device is screwed in the mass market.


      Are you familiar with SOCKS? The client requests a port to be listened on, and incoming connections to that port are tunnelled through to the client.


      For most applications, if they don't have a well known port then they're almost useless since you won't be able to find them.


      Which applications? Once again, if you have a lookup server (similar to a DNS server) acting as an intermediary, this isn't a problem. If the user on DSL wants to run a webserver, the user can get a static port forwarded. Even without a static port there are services which will forward static URLS to dynamic ones. They use redirects, so only the URL goes through the intermediary, the data goes through the regular connection. If the user wants to look professional, they're going to need a static IP address, but if they're doing this for professional purposes it makes little sense for them to be using a home DSL connection. That's where the 1% I was talking about above fall in.


      The problem could be solved by inventing some kind of automatic port allocation, and linking it to dynamically assigned DNS entrys, but if every router would need to be changed to support that then you might as well just switch to IPv6 which is already implemented and solves more then one problem.


      Not every router would need to be changed, only the router the DSL user is using. But yeah, that's my point, IPv6 makes things a lot easier, but it is by no means necessary. On the other hand, I thought about the GPS thing after submitting it, and it wouldn't be an efficient solution because two computers could be right next to each other but using different ISPs, and for efficiency they should therefore only have similar IP addresses to the point where their ISPs peer. In theory that is fairly close, but perhaps the GPS coordinates of your peering point with your ISP combined with a code for your ISP and a secondary part given by your ISP would be better. But hey, now that's sounding a hell of a lot like NAT, except you're making the end computers hold the state rather than the NAT box.

      --
      ok then your [sic] infringing on my copyright! Could you as [sic] me next time before STEALING my comments for your own?
    10. Re:NAT doesn't solve the whole problem. by ivan256 · · Score: 2

      You were talking about peer to peer applications needing an intermediary. My point was that the entire internet is based upon using intermediaries

      That's not an intermediary in the same sense. Once you look up the piece of information you need from DNS you're done with that connection. When you have two IM clients that are behind firewalls, they relay ALL the data through the intermediary. It is impossible for them to connect to each other directly ever. That's a lot different.

      Are you familiar with SOCKS? The client requests a port to be listened on, and incoming connections to that port are tunnelled through to the client.

      I'm sure you're aware of what happens when two machines behind the proxy request the same port. If it has to pick a different one, then how are the devices on the outside to know? What if it's this new DNS like server that conflicts? It'll have to be well known by the router or even implemented IN the router then. Now you're changing the router and you might as well go IPv6.

      Which applications? Once again, if you have a lookup server (similar to a DNS server) acting as an intermediary, this isn't a problem

      Like I said above, the DNS server isn't an intermediary in the sense that I meant. As for which applications, cat /etc/services next time you're on a *NIX box. If you don't have a *NIX box then just think about all the URL prefixes you've seen before the ':'. Those are well known ports. Those are the ones that exist now. As for the ones that exist in the future, if I knew what they were going to be I'd go create them and become very wealthy.

      If the user on DSL wants to run a webserver, the user can get a static port forwarded.

      You still haven't told me who is going to set up these forwards, and who is going to arbitrate them.

      Not every router would need to be changed, only the router the DSL user is using.

      Really? So how many DSL routers out there do you think are this intellegent. It's less then 10%. Most ISP's who do NAT do it on the other side of the DSL link. It's way cheaper to buy a nice NAT capable Cisco switch and a bunch of dumb DSL bridges then to give everyone a router. THese ISPs are the same ones who are the roadblock to switching to IPv6, so do you think it's going to be any easier to get them to change to your new NATlike scheme?

      If the user on DSL wants to run a webserver, the user can get a static port forwarded.

      Say you do come up with the perfect 'hack' over IPv4 to make IPv6 unessicary. Why would you use the hack when there's this nice elegant new technology that is ready to be dropped into place? Whatever hack is used has to become universal if it is to be built into consumer devices, and that deployment would end up being just as expensive as deploying any other solution...

  45. Re:IPv6 was also designed to support interplanetar by cluthu · · Score: 1

    And IPv7 was designed so that a lab tech at Tachibana Labs can rule over both the wired and real worlds.

  46. JoeSchmoe by Anonymous Coward · · Score: 0

    There are no Schmoes, Joe or otherwise, in the United Kingdom. Nor are there any Sixpacks. There are however 3 Joe Bloggs, 82 John Does, 12 Jane Does, 44 Tony Blairs, 59 George Bushes (including 10 Ws) and 11896 John Smiths (not including children).

    Unfortunately I don't have definitive US data, so I cannot tell you if there are any American Schmoes to be offended, though there is at least one listed in the telephone white pages (517 area code). There are 36 Steve Wozniak phone numbers though (how is that such a common name?)

  47. Don't forget... by AKAImBatman · · Score: 1

    ...that Connie Chung disappeared from CBS shortly after she did an interview with Bill Gates. The story goes (See: Barbarians Led by Bill Gates) that she tried pretty hard to lean into him. So hard that he stormed off the set and Connie Chung's career ended. Coincidence? Probably not.

    1. Re:Don't forget... by ethereal · · Score: 0, Offtopic

      Is that the same way that the "Checkers" speech was widely believed to be the end of Richard Nixon's career? Last time I checked, Connie Chung was still working...

      --

      Your right to not believe: Americans United for Separation of Church and

    2. Re:Don't forget... by Aexia · · Score: 1

      And where has Connie Chung's career gone? Nowhere.

      Though, judging from her interview with Condit, the reason probably has more to do with Connie than Bill.

  48. The solution. by pclinger · · Score: 1

    The solution to all our problems... someone write a virus (eg Mellissa) that changes Windoze systems to support IPv6. That'll take care of over 50% of the computers just from morons opening attachments.

    --
    /. editors made it impossible to link to file:///c:/con/con in my sig. Please just type it in
    1. Re:The solution. by fat_mike · · Score: 1

      Pay attention. Windows already supports it.

  49. the problem by Anonymous Coward · · Score: 0

    it's not the OS that's the issue.... it's the apps and even more the routers and other hardware that are switching the packets around

  50. Simple Solution by The+Ape+With+No+Name · · Score: 1

    Carve up MIT's, IBM's, and Stanford's Class A networks.

    --
    Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
    1. Re:Simple Solution by Anonymous Coward · · Score: 0

      Simple just ain't the word for a large-scale network renumber...

  51. As a class C IPv4 holder that can't get routed. . by ahfoo · · Score: 2, Interesting

    I say this article sucked.
    Clueless hype is all that's out there these hot summer days. It's ridiculous. They did concede that IPv6 is inevitable, but they sure spent some time wringing hands over totally irrelevant crap at the same time. I saw that link on CNN earlier in the evening and didn't read it because I knew it would suck and only went back and read it only because I saw the link here on /. and knew I could vent.
    For those of us old enough to go ahead and got busy organizing networks here and there back when ICANN was getting started and you could just ask for net numbers --as I and many others did-- the problem is all too clear. The beauracratic, financial and legal powers that became involved over the years totally twisted the original premise. If you want a frickin' number you get one. If you want a thousand, you get a thousand. They're just numbers. Deal with it.
    But that's not what it turned into at all. Vast portions of those billions of IPv4 numbers don't go anywhere because network routing is a financial issue closely intertwined with a technical issue that few people outside of open source are familiar with.
    It's irrelevant though because IPv6 is inevitable and this has already been covered in so many other ways.
    And, to top it off, dynamic domain names makes it all meta anyway. Yeah, I'm not crying about the way things are by any means but more numbers is such a rational idea. And why stop at IPv6, next step is get rid of this restricive domain naming stuff. They've already started using Chinese characters at some domain registrars. So let's just name domains like long file names so we can use popular phrases! Shit, you don't think there will be a gold rush on that shit? There's a limited set of English phrases. You take that from an English major.

  52. Airplane simile by Tek+Neek · · Score: 1

    From the article:

    "Replacing all hardware and software at once is akin to rebuilding an airplane while flying."

    Seems to me like changing to v6 is more like refueling than rebuilding. Just changing the software (on most machines, granted some hardware would have to be changed) shouldn't be as difficult as everyone who uses the internet having to go out and buy new hardware.

  53. Not only that, but-- by Anonymous Coward · · Score: 0

    What about the millions and millions of IPv4 addresses that are 'reserved', like that monsterous block that goes from like 69.0.0.0/8 to 7x.* something? that's several hundred million IPs right there. Who needs this IPv6 junk, I want to be able to remember IP addresses dammit! :)

  54. Hindsight is 20-20 by Pandaemonium · · Score: 1

    Wow. I just love this quote from the article:

    "It solves problems people don't have and it doesn't solve the hard problems we do have," said Mike O'Dell, an early v6 advocate who now believes the Internet has far greater problems -- like how to more efficiently route data traffic. "

    That makes no sense. Y2K was a problem we didn't have yet. It was inevitible, and we fixed it. This is the same thing. If we don't get to this issue soon, the Internet will be crowded, and our problems will be even harder to fix than they are now.

    What I don't understand is why noone has come up with an intelligent way to get IPv6 implemented. I'd have every router company have IPv4 and v6 on every router they sell. Have ISO or IEEE come up with a standard for a 'magic packet to switch to IPv6'. Have all PC's have IPv6 ready to go. All routers have to be upgraded in the next five years. Offer discounts for doing it. Then, at a designated date and time, send that magic packet that everyone conforms to, and instantly, the whole freaking internet is running IPv6 instead of v4. Then start working on addresses and getting things back in order, since it's so easy to switch addresses with v6. Sounds good to me.

  55. Re:Not broke!?! What!?! by Blowit · · Score: 1

    IP Addresses cost an annual fee to have. Therefore, this is the reason why they charge for IP Addresses. Most dynamic Dialup IPs are priced within their pricing and therefore you don't see an IP Address charge. If you want static IPs, you have to pay for it. period.

    --
    *Headline News* censorship shuts down the Internet! More at 6PM!
  56. Apple IPV6 Support by rpk · · Score: 1

    Yes, Apple did demo Mentat's IPV6 support in Open Transport for MacOS Classic a while ago, but never shipped it.

    From what I understand, Darwin includes (or can include) the KAME networking code that it inherits from FreeBSD, but it is not turned on. Maybe for OS X.1 though...

  57. Last Change of this magnitude was Color TV. by BigBlockMopar · · Score: 5, Interesting

    From what I understand, Linux and Windows NT have had IPv6 support for quite some time now.

    The problem appears to be more subtle than that. The routers are mostly compliant, I wouldn't worry about it.

    The smooth transition is going to require that everyone on the 'Net start to switch over. Even half-wit Windows-95 AOL-point-and-drool users.

    Surely, we can release patches to the operating systems. And users can upgrade to new applications programs which aren't crashing when they request a DNS lookup and get something longer than they expect.

    But you know they won't.

    As evidence, I submit to you the Code Red worm. You'd have to be living under a rock for the past two months to not know about it. Yet, I still get hit by infected machines. Follow the link on my .sig.

    I haven't studied or attempted to deploy IPv6, but it will have to be backwards compatible with IPv4.

    In the 1950s, Europe upgraded their TV system to color. The new PAL and SECAM color standards weren't compatible with their old 405/441-line black and white standards, leaving consumers with far too many confusing choices. Arguably, European TV never recovered.

    By contrast, RCA came up with an ingenious way of making a color signal ride on top of the existing North American black and white system. Old black and white TV sets were eventually replaced with color, but there was no great format change. You bought a color TV or a black and white set, and you weren't at the mercy of finding out whether or not there was still a black and white station in your area. People transitioned more gently and weren't put off by having their two-year-old oak-cabinet investment turned into a paperweight by moving out of a 405 line service area.

    IPv6 will have to be deployed in the same way or adoption rates will wane.

    --
    Fire and Meat. Yummy.
    1. Re:Last Change of this magnitude was Color TV. by pantherace · · Score: 1
      Why not follow that? Set IPv4 addresses to all be a class c ipv6 address. Forexample current (random) 182.34.5.13 would go to say 1.1.182.34.5.13. Allowing IPv4 to stay around on systems that don't support IPv6 (majority of clients-win mac).

      The problem with the 'adoption rate' comment is that if we do switch over, there is going to be a huge problem with ipv4 holdouts, because suddenly everyone will be on ipv6, essentially no bw tv stations at all. Either they can handle it or will not work, unless something like the above is implemented.

    2. Re:Last Change of this magnitude was Color TV. by MarkLR · · Score: 1

      I doubt the AOL users will be the problem. Most of them likely have no idea what an IP address is and wouldn't notice if AOL switched to IPv6. The trickey part is convincing AOL itself to switch.

    3. Re:Last Change of this magnitude was Color TV. by eram · · Score: 1

      This is slightly off-topic, but there seems to be a few things that have to be clarified.

      In the 1950s, Europe upgraded their TV system to color. The new PAL and SECAM color standards weren't compatible with their old 405/441-line black and white standards [ausys.se], leaving consumers with far too many confusing choices.

      According to the link you provided (very interesting actually) the 405 and 441 line standards that you are talking about were only used in the UK and France. The reason to discontinue these standards was not the introduction of color. The PAL and SECAM color standards are compatible with the black and white standard introduced in most countries when TV broadcasts started in the 1940s and 50s. Black and white 625 line television sets bought then can still be used.

      Color television was introduced in most places in the 1960s. OK, you have probably had both TV and color TV for a longer time in the US, but the price that you've to pay for that is a slightly lower quality picture with fewer lines and a color signal that is not always perfect.

      Arguably, European TV never recovered.

      I don't know what you mean by that. Most Western European households have at least one television set and there are lots of channels available through cable or satellite receivers.

    4. Re:Last Change of this magnitude was Color TV. by gorilla · · Score: 2
      You have to remember that the 405 line service started earlier than the US 525 line service.

      405 line was first introduced in 1936, and temporarily shutdown in 1939. During the war, the european countries were too busy to do anything, but by 1940 the US decided to standardize on 525 lines, not a huge amount above the British 405 lines systems, but enough that in the mid sixties when colour was coming along, NTSC could be built on top of 525 lines, but no acceptable colouring system could be built on top of 405 lines.

      However, with new TV stations broadcasting only in 625 lines, as soon as PAL came out, you could get monocrome PAL sets. Indeed, monocrome PAL was all that was available for many years. At that time, the tube & the colour decoding was the most expensive part, and by ommitting those, you could make a cheaper set.

      I doubt if anyone lost any investment in 405 line sets. 405 line was offically obsolete in 1964, when the first 625 line channel (BBC2) was introduced. There was never a 405 line BBC2 signal. Colour was introduced to BBC2 in 1967, but 405 line service continued on until 1985, 49 years of broadcasting.

    5. Re:Last Change of this magnitude was Color TV. by BigBlockMopar · · Score: 2

      OK, you have probably had both TV and color TV for a longer time in the US, but the price that you've to pay for that is a slightly lower quality picture with fewer lines and a color signal that is not always perfect.

      Yes. Admittedly, PAL has more scanning lines.

      But there's no magic to that. Nearly the same horizontal frequency, with a 50Hz vertical. The bandwidth of the video and RF circuits is nearly the same, so there's really no dramatic improvement in picture quality.

      On the other hand, NTSC has 525 interlaced scanning lines, 60Hz vertical, a higher frame rate, and almost no perceivable flicker as a result.

      --
      Fire and Meat. Yummy.
    6. Re:Last Change of this magnitude was Color TV. by Gordonjcp · · Score: 1

      but no acceptable colouring system could be built on top of 405 lines.


      Not so much the number of lines, but the low bandwidth provided for in the VHF channel spacing. The lowest VHF TV channels were around 45MHz, well below UHF/625's 470MHZ-upwards channels. Channel spacing was (iirc) 3.5MHz or so...

    7. Re:Last Change of this magnitude was Color TV. by Anonymous Coward · · Score: 0

      Hey my dick is bigger than yours because I shaved off all my pubic hairs :)

      even 60Hz isn't acceptable, so now we have tv-sets that digitally enhance the image and give 100Hz

      IMHO American TV suck, and it suck hard, to many comercials and verry bad picture quality, but mind you that was in 1992

      and when is the us going to switch to hdtv ?

      :)

    8. Re:Last Change of this magnitude was Color TV. by terrymr · · Score: 1

      NTSC = Never Twice the Same Color

    9. Re:Last Change of this magnitude was Color TV. by Afty0r · · Score: 1

      In the 1950s, Europe upgraded their TV system to color. The new PAL and SECAM color standards weren't compatible with their old 405/441-line black and white standards [ausys.se], leaving consumers with far too many confusing choices. Arguably, European TV never recovered.

      And this is bad... how?

    10. Re:Last Change of this magnitude was Color TV. by Cato · · Score: 2

      The majority of ISPs run Cisco routers. Cisco's IOS software only supported IPv6 in 12.2T, which is the latest bleeding edge release, and even then it has 2 more phases to support full hardware acceleration and various routing protocols.

      So... Most routers in the world don't support IPv6. Most hosts don't either - Windows XP is the first MS OS that supports IPv6, although Linux 2.2 and Solaris 8 and many other Unixes already do.

      IPv6 adoption is NOT a big bang affair, although it is a lot of work - you can deploy IPv4+IPv6 routers and hosts and then gradually convert them so that IPv6 is enabled, and then much later turn off IPv4 is enabled. It's a huge job to get all the apps and hosts converted, but once converted, you can drive the choice of IPv6 vs. IPv4 for a given session using DNS - just return an IPv6 entry and the v6-capable apps will use IPv6.

      Within a few years, all host OSs and most apps should be IPv6-capable without any extra work, enabling this to happen quite smoothly (though with a lot of work from network administrators and some from sys admins).

  58. Yes it will by Srin+Tuar · · Score: 3, Insightful

    According to the RFC's, even a lowly dialup users will be given more routable addresses than the
    entire internet contains at the moment.

  59. Too much milk? by room101 · · Score: 2

    For instance, do people really want a unique address for a refrigerator -- allowing hackers to spy on individual eating habits -- or order you a truckload of milk?

    Wow, that kinda puts a new spin on the old too much milk problem from my Operating Systems class in school. Brings back bad memories.

    (For those of you who don't know/remember this problem, it is an example of resource locking, needed in OS design. I would say all Computer Science/Engineering students take that class, at least the did at my university).

    --
    room101 -- how much can you stand before they break you?
    (they always break you eventually)
  60. Why implement V6 ? by rpk · · Score: 1
    If you can run a V4 tunnel to the outside of your LAN before your ISP supports it, there might some advantages:
    • New, so hackerz don't understand it. V6-only hosts might be more secure for a while.
    • Most workstations don't need DNS names anyway.
    • If your DHCP server does goes down, peer-to-peer inside the V6 LAN still works.
  61. Before we start arguing about IPv6... by fm6 · · Score: 2
  62. Addressing isn't the biggest problem now... by nologin · · Score: 1

    While I agree that IPv6 will fix some problems with addressing devices on the net, there are bigger problems to deal with first.

    Routing network traffic effectively is a far greater concern, especially with the major backbone providers. In the last few years, Internet traffic has grown around 300% per year. It is very difficult to get a cost-effective solution to the routing problem. The industry is already looking at terabit routers in order to keep up with today's demand for bandwidth.

    And considering that over 50% of the routable network traffic (300000+ routes in total) are class C networks (24 significant bits), the biggest problem is not necessarily the bandwidth; the key problem is being able to process the routing of that data.

    Considering that IPv6 will put a lot more networks up with more significant bits to indicate the routing of that data, routers will have to become a lot more powerful before they can even begin to handle the load of IPv6. If the major backbones decided to implement IPv6 today, the routers on these backbones would slow to a crawl, the net being virtually useless.

    So, until router technology matures to meet the potential demands, IPv6 will look good on paper, and nothing more.

    1. Re:Addressing isn't the biggest problem now... by Asgard · · Score: 1

      One of the main points of ipv6 is that routing will be simplified greatly. The header has been fixed in size (less work for the router to parse) and the addresses can be distributed in a hierarchical fashion. See the IPv6 Routing FAQ for more details.

    2. Re:Addressing isn't the biggest problem now... by CrazyBrett · · Score: 1
      routers will have to become a lot more powerful before they can even begin to handle the load of IPv6

      I disagree. Routing has become overly complicated due to CIDR and other "hacks" that compensate for the lack of addresses. Routers practically need to look at the entire address to figure out where to send it. The advantage of IPv6 is that it allows us to reorganize the address space in a way that is easier (more heirarchical) to route. Each server can simply handle one or two octets of the address, and delegate all further processing to the "next router down".

      Also, changing addressing schemes doesn't mean we'll instantly have millions of new machines using the new addresses. In the beginning, we'll have the same number of addresses and a simpler routing strategy, which will put less strain on individual routers. In the future, when people do start using all the new addresses, it will be trivial to scale the routing strategy up by adding new layers of routers to the heirarchy.

      -- Brett

  63. Cisco has good intentions, but... by huge · · Score: 1
    As the Cisco is deploying (in future) new IOS with IPv6 support, it's good for gradual change but doesn't give real reason for anyone to start using v6 addresses. From my point-of-view (it's always easy to say) deployment of IPv6 capable IOS version could be started at last year, as the standard has been complete for a while.

    Presence of the IPv6 support is no reason to start using it. It's same thing as with DoRK, the next generation p2p system. I have support for that also, but why should I use it? If it would be compatible with Napster, gnutella, etc... I would love to use it.
    The point is, at the moment registars (RIPE atleast, only one that I have experience about) are allocating too large IP blocks for customers without any plans about how to reduce the usage of IPv4 addresses. What would happen if they would stop assigning more that 1 to 16 addresses for single company (depending one the size of the company), but they would give you (more) supplementary IPv4 addresses when allocate block of v6 addresses. They could also require that client must have plan about how to deploy and start using v6 capable hw/sw.

    If you postpone the start of assigning new v6 addresses until there are no more v4 addresses left, you are making a big mistake. It's almost the same that uyou would start fixing Y2k problems at 2001.

    Better later than never, though.

    --
    -- Reality checks don't bounce.
    1. Re:Cisco has good intentions, but... by DavidTC · · Score: 1

      Dude, they already 'assign' IPv6 addresses. You just use the ones that are a subset of yur providers. And you can get free providers.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  64. Excellent news, Shopper sllort by FreeUser · · Score: 2

    We the Consumers of This Great Nation(tm) are delighted at the news you bring us, Shopper sllort. Indeed, it is gratifying that Crime(tm) was prevented by Our FBI(tm) in such an effecient manner, such that Shopper Bell can be Reformed(tm). While regrettable that Shopper Bell's Consumer Credit(tm) will be limited for a period of ten years due to his incarceration for Unapproved Speech(tm), it is important to the serenety of our Shopper's Paradise(tm) that such potentially dangerous Shoppers be detained and Reformed(tm) early in order to insure their quick return and continued contribution to Our Consumer Economy(tm).

    Yours in Consumption,

    Shopper FreeUser.

    --
    The Future of Human Evolution: Autonomy
    1. Re:Excellent news, Shopper sllort by Anonymous Coward · · Score: 0
      Nice photo album Jean; now I know what you look like.

      *Consumer Database Updated*

  65. NAT isn't the only patch to address shortage by rpk · · Score: 1

    There's also one that's less obvious: CIDR. It works very well but has the already-discussed problem that it's hard to your subnet number(s) if you change ISPs.

  66. the "looming doom" is based on assumptions by Lumpy · · Score: 2

    First off, my toaster,TV,shower,alarm clock, and bed do not need to have an IP address on the internet. 99.995% of all internet users do not need an actual IP address on the internet. Yes, we are getting close to using up all the Class C network numbers. but if many of the messed up ISP's and co-lo farms actually managed IP's better it would, quite possibly, become a self controlling problem. when I Had my server on the internet I was given 8 IP addresses by my ISP. What the heck for? I asked for one, they said, "here! take 8!" so there's 7 Ip addresses that are now unuseable by others.
    Now you might have the reason that you need to run dns,smtp,www,pop3,ftp,etc... on different machines... ok, you still dont need more than 1 Internet IP address. that's what your routing equipment is for, to manage IP addresses. They magically route that request from 127.0.0.1:80 to 10.12.1.2:80 and that 127.0.0.1:21 to 10.12.1.3:21

    any shortage is because of slipshod management of the IP space.

    --
    Do not look at laser with remaining good eye.
    1. Re:the "looming doom" is based on assumptions by Raven667 · · Score: 2

      That's obnoxious. Packet mangling (and DHCP) is an ugly hack and breaks many network protocols (IP Telephone, Incoming services, PtP filesharing, etc.) With IPv6 neither technologies are necessary.

      Do you really think that NAT is the solution for the future?? I believe that the right answer is for every electronic device to have routable addresses and apply packet filtering as appropriate. Then everyone can have their own /48 address space.

      --
      -- Remember: Wherever you go, there you are!
  67. After Y2K ... by MALKAV(PAT) · · Score: 1

    The next big problem will be IP address shortage,
    we will have to migrate all our internet connect device to IPV6 compliant before the wave hits us. And again after its over and everything went well because of good programmers everybody is going to say it was all an Hoax...

  68. One HUGE Benefit of IPv6 by terrymr · · Score: 1

    Is the way addresses are constructed - because the route to a particular subnet can be determined by its address (aggregatable addressing) routing tables become much easier to manage - something that can't be said for the current state of IPv4 - as subnets become smaller routing table size increases - it is more likely that routing tables will become unmanagable before the number of ipv4 addresses runs out.

    1. Re:One HUGE Benefit of IPv6 by Anonymous Coward · · Score: 0

      Interesting statement. saying a route to a particular subnet can be determined by it's address is akin to saying 'that tree has green leaves'. What I _believe_ you are refering to is the proposed hierarchical addressing structure that v6 MAY be able to impose on the network as it goes into place. However, what you may want to consider is that if v6 goes in, we are going to drasticly increase the number of available networks, and we ARE going to DRAMATICLY increase the size of routing tables with IPv6.

      Just because we think we have a great addressing scheme doesn't mean it will survive contact with the real world. (history has proven otherwise, much to the embaresment of routing engineers all over the world) The real size of the routing table depends just as much (if not more) on the number of individual networks that can NOT aggregate themselves behind someone else (for fault tolerance, political purposes, what have you), as if does on the number of IP address those networks need. So with that in mind, the size of the routing table will probably remain amazingly close to what it is now, no matter which version of IP you use. The 'smaller subnet' routes that are popping up with v4 will be there for v6, because of the nature of the way people use the network. If a small company wants a web site, run in house, they are going to want some fault tolerance. which means they have to announce the route for thier web site to at LEAST 2 providers... Do you really think someone like that needs more than 32 IP address? (esp if they are being charged for them, and security folks are telling them horror stories about the big bad public network?) Of course, since the physical size of the address is much larger in v6, even if you are only keeping track of the aggregates, I would imagine the size of the routing table would be close to haveing a list of host routes for every v4 address in a router. So, not unlike your favorite m$ wordprocessor, you end up building a super computer to support upteen million features that 99.95% of the people are NEVER going to use... And you go out of business...

      And you wonder why no one is rushing to implement this thing?

  69. I wouldn't mind... by sulli · · Score: 1

    if my fridge suddenly got taken over by (filled with) Code Red!

    --

    sulli
    RTFJ.
  70. Re:Seamless Intergration - far from it by Lumpy · · Score: 2

    For the longest time all devices will require dual addresses (Ip4 and ip6) DHCP is not capable of that feat. so now we either have a techie-guy(tm) deal with the customer or just silently piss-off everyone at once. I.E. switch over from ip4 to ip6 at midnight on XX/xx/xx. Let all your users know this and send them links to the patches/files/wizards. after the switch those that have incompatable hardware are to be told to jump in a lake. those with incompatalbe software are scolded for not upgrading when they were warned.

    the switch will piss-off a huge block of users. and that's the price of progress..

    --
    Do not look at laser with remaining good eye.
  71. How do I get an IPV6 address? by Omnifarious · · Score: 2

    I want an IPV6 address. I'm going to run my internal home network on IPV6 and run a translator to make my IPV4 addresses translate to internal IPV6 ones. Where do I get a number space? I know the lower 8 bytes are suppose to be a MAC address, but what about the upper 8?

    1. Re:How do I get an IPV6 address? by Anonymous Coward · · Score: 0

      You can get one here, of course :-)

    2. Re:How do I get an IPV6 address? by Omnifarious · · Score: 1

      Thanks! I discovered my ISP is on the 6bone though. :-) They'll give me a /64, which I really don't need, but hey! :-)

    3. Re:How do I get an IPV6 address? by Wesley+Felter · · Score: 2

      Use 6to4; it's more efficient than tunnel-based systems like 6bone and freenet6.

      Instructions: BSD, Debian, Windows.

    4. Re:How do I get an IPV6 address? by Omnifarious · · Score: 1

      I'll have to look into that. It seems like I'd have to get a tunnelled address anyway if I wanted to both be on the 6bone and use 6to4. If I wanted the best IPV6 connectivity I could get, that sounds like the way to go.

      Interestingly enough, I can use that same SLA and interface addresses in both the 6bone, and the 6to4 address space. That's kinda neat. :-)

      Since I'm going to be doing lots of NAT anyway to make this all work, maybe I'll just use site addressing inside my network, and translate the 48 bit prefix address to make it look like I'm on whatever network I happen to be talking to.

      That'll get confusing in DNS though. :-(

  72. Re:As a class C IPv4 holder that can't get routed. by Col.+Panic · · Score: 2
    I saw that link on CNN earlier in the evening and didn't read it because I knew it would suck and only went back and read it only because I saw the link here on /. and knew I could vent.

    ditto

    more numbers is such a rational idea

    agreed

    next step is get rid of this restricive domain naming stuff

    Well, I think we have been selecting our own domains on the premise that shorter is better. You can't even get a three letter .com domain anymore because they are all taken. Longer is not necessarily better when your customers have to type this.is.my.cool.domain.name.everyone.will.remember .com

  73. Won't cost much by msheppard · · Score: 1

    could cost billions of dollars worldwide

    So that adds about 2 bucks to the next computer you buy... or the next internet enabled fridge.

    These kinds of monetary esimates tend to misconstrue the actual cost per person. Getting a flat tire in the city during rush hour on a buzy road can cost the world "Millions" in man hours.

    --
    Krispy Cream is people
  74. IPv6? Forget it. by thejake316 · · Score: 1

    I can't remember my IP address as a goddamned dotted quad, and you want me to remember 8 colon-separated 16-bit values in HEX with the leading zeros suppressed! Bite me.

    --
    AC's cheerfully ignored
  75. Re:Paved with dead jews by John+F.+Ketamine · · Score: 0, Offtopic

    BAN HIM NOW.

    --
    "Upgrade your grey matter, 'cause one day it may matter." --Deltron Zero
  76. The question that seems more important to me... by Kasreyn · · Score: 2

    ...is not how IPv6 will deal with the increased addressing range, but how it will handle issues of security, and more importantly, WHO will control that security and will the specifications be OPEN?

    The internet as it stands suffers because it is trust-based and there are all too many willing to abuse that trust. Many untrusting-internet ideas have been flown, and most of them involve more identity checking and awareness of the originators of packets. Would this "new" internet (I hate to use such an overused term but it seems appropriate) - would this "new" internet retain any opportunities for anonymity (and thus more secure freedom of speech), or will it be a case of "let's crack down on anonymity online because anyone who doesn't want the totally benign government to know who he is must be a terrorist or a child molestor! Why do you want to be anonymous, do you have something to HIDE?"

    A lot can be done towards preventing the latter if the specs for any new internet communications protocols being open or hopefully even GPL'd. Is this likely?

    -Kasreyn

    --
    Kasreyn: Cheerfully playing the part of Devil's Advocate to hairtrigger /. flamers since 1999.
  77. On the lighter side... by johnnie · · Score: 1

    And with mobile devices, Nokia's Robert Hinden said, the inability to give each an IP number would be like having cell phones that could only make calls, not receive them.

    ... if i could get one like that, i might still have one...

    --
    Don't ask. Go see.
  78. Re:Not broke!?! What!?! by Anonymous Coward · · Score: 0

    You are correct that Ip addresses cost an annual fee, but your reasoning that you should have to pay more for more globally unique ip addresses is crap. For the paltry sum of $5000/year any ISP can obtain a /16(with justification). In laymans terms that is 65,536 IP addresses, or about $0.08 per ip per year. Poor genericid is paying $48.00 per ip per year to his ISP. Profit Margins like that make the RIAA look like a saint. Not to mention the fact that IP addresses are not supposed to be thought of as a commodity or asset, and therefor cannot be bought or sold. Don't let your ISP bully you into these outragous payments! Their costs of maintaining those IP's is negligable.

  79. Re:IPv6? Forget it. by Anonymous Coward · · Score: 0

    You're not supposed to remember it, that is why we have directories. (Good job too, otherwise phone numbers will get to be a bit of a problem - that's why we can't use NAT, btw, unless you don't actually want any incoming phone calls - hey might not be such a bad thing actually :-)

  80. Fairly extensive IPv4 vs IPv6 comparison by crimsen · · Score: 1

    I wrote a research paper covering the differences between the protocols a few months ago. Although some of the information already might be out of date with ever changing RFCs, some might find it interesting.

    http://webpub.allegheny.edu/student/d/dotyr/x/ri ch doty_ipv6ipv4_with_allegheny.pdf

  81. MIT's A-Class by alexhmit01 · · Score: 2

    MIT's IP scheme has allowed them to build a by-the-books network. They use their IP scheme to make it really easy to figure out where a machine is by IP. For added fun, they don't use firewalls. In fact, MIT discourages firewalling. They recommend using real security, and recommend that you use Kerberos for everything... while not supporting Kerberos (in a useful manner) except on their UNIX machines.

    For added fun, MIT gave an entire B-class (well, 1/256th of their A-class, not technically a B, but you understand) to each dormitory and each fraternity. MIT groups aren't starving for IPs, which is nice, but the rest of the Internet is.

  82. Not exactly correct by Srin+Tuar · · Score: 2

    You seem to be confused:

    The point of having a static address is so that one machine can be found by others. You have to have some fixed address in order to describe who it is your connecting to.

    Imagine the havoc that would pass if area codes in telephone numbers could change on moments notice. Take away the phone book too, since you think dns is uneeded. (Works fine for calling out- since in that case you dont care what your number is. but who are you going to call, exactly?)

    If there is no way for anyone else to determine what a given servers address is, then there no way anyone else can connect to it.

    In reality each "entity" be it a megacorp or a measly dialup user, will be given 80 bits worth of routable address. 16 bits of that they can use for subnets. Only the 48 starting bits are really "fixed". The 128 bit addressing scheme is really an attempt to get everyone tons of "static" routable addresses.


    And There will of course be a name-to address mapping similiar to what DNS does now. The simple reason is that noone is going to type in a huge monster address when they want to hit a web page.

    1. Re:Not exactly correct by jd · · Score: 2
      The only "workable" solution is to do an "Anycast". You send out the name of the machine you are looking for, and it would be the job of the recipient to send back the current valid IP address.


      (Of course, this would be extremely easy to spoof, if you weren't also using IPSEC and machine authentication to validate the connection.)


      This negates any need for a fixed destination. It =does= result in far more peer-to-peer traffic, removes ALL centralized control, and requires Anycasting to be implemented fully on all stacks, but it DOES kill off ICANN, and that can't be a bad thing.


      Anycasting works by multicasting to all receiving hosts, and then having the first match transmit back. At least, that's the theory. It removes any need for centralized data stores, by using a peer-to-peer search and reply system.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    2. Re:Not exactly correct by rtaylor · · Score: 1

      Considering the amount of traffic our DNS server recieves for a few thousand domains, I don't think I'd want to receive 'lookup' requests for everyone on the internet all the time.

      The 100MBit connection wouldn't be able to handle it. Don't know how anyone on a DSL or modem would manage...

      --
      Rod Taylor
    3. Re:Not exactly correct by kilgore_47 · · Score: 1

      Sure. Every Host will receive every name lookup for the entire network.

      I think you need to reread whatever you read that gave you these crazy ideas, because you're making a bunch of good intentioned nerds say wtf and then try to explain the concept to you. Its not a pretty situation.

      --
      ___
      The way to see by faith is to shut the eye of reason. --Ben Franklin
    4. Re:Not exactly correct by Cato · · Score: 2

      Anycast isn't even supported by many IPv6 implementations, since it's hard to actually implement it. DNS is *more* important in IPv6 than IPv4, because the addresses are more of a pain to type. DNS is not going to go away...

  83. Others have said it, but... by KC7GR · · Score: 1

    ...I feel compelled to point out something that EVERYone seems to have missed.

    Let me say first that I see no reason whatsoever to wire every imaginable device to the 'net outside of government and the bureausplats wanting to be able to monitor anything they can think of on demand.

    Think about it: Fridges, washers, dryers, toasters... they were all built to serve specific purposes, and those purposes are not in any way, shape or form assisted by connecting the device in question to some global network. So why connect them unless you want to know when they're on, what they're doing, etc.?

    Now, with that said... If the marketdroids and polly-tishuns are going to insist that everything be "connected," there needs to be an "off" switch or similar way to 'pull the plug' as it were for ANY such interconnected device. Furthermore, the basic function of the device in question must NOT be impaired by doing so. Consumers will never buy into such crap otherwise (heck, they may not buy into it now).

    I still want to know which bonehead(s) thought it would be a good idea to connect appliances to the 'net in any case...

    --

    Bruce Lane, KC7GR,

    Blue Feather Technologies

    1. Re:Others have said it, but... by Brandon+Hume · · Score: 1

      I believe the "bonehead(s)" in question presented the idea of hooking appliances to the net as an example of what COULD be done, not as any endorsement of DOING it. Too bad so many armchair net admins have taken it up as a flag to wave for the "uselessness of IPv6".

      Ignoring the fact that address space IS NOT the only reason for the implementation of IPv6, it IS a major part. As much as some people would like to bury us behind NAT after NAT after NAT, there are all kinds of reasonable applications that "solution" would hinder or destroy.

      Sure, the dork at home is perfectly willing to buy a NAT box, and exclaim that he doesn't need an IP-enabled fridge, but what about the vending machine maker, or the cellphone manufacturer?

      Sure, they can both hide their devices behind NATs. But that makes the benefits of management disappear in the mess of trying to build and maintain the network. (Such a thing would NOT be static, like the home-dork's network.)

      And THEN, what happens when those two companies want to make their devices talk to each other? Waving your cellphone at a Coke machine to order a drink is a perfectly reasonable thing to expect people to want to do. Or how about pushing the takeoff schedule into your cellphone when you walk into the airport?

      These things CAN be done without IPv6 - but the implementation in that case turns into a BIG FRIGGIN' MESS.

      The cries of "I can use NAT! My toaster doesn't need an IP!" from the three-device home-users in no way counter the REAL reasons IPv6 is a good idea.

      --
      Brandon Hume
      hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/
  84. It's called Virtual hosts, and it works. by slashkitty · · Score: 2

    You can run thousands of webservers on a single server, single ip address. You use the names. Similarly, this can be extended to other services. (Do a search on /., it was mentioned earlier).

    --
    -- these are only opinions and they might not be mine.
    1. Re:It's called Virtual hosts, and it works. by funky+womble · · Score: 1

      Host-header based virtual servers doesn't work with https.

  85. Save space! by nr · · Score: 1

    The IPv4 loopback address "127.0.0.1" is represented in IPv6 as "::1".

    1. Re:Save space! by thejake316 · · Score: 1

      I can represent it as "no way in hell." You can have ipv4 as soon as you pry it from my cold, dead fingers. "Ooh ooh!" they say, "we can't possibly run out of address space now!" Last I checked, we're running out of address space now because whoever was allocating it in the first place basically said, "oh, you have a computer? Here, have 65,000 or so addresses, keep the change" for the first billion or so IP addresses.

      --
      AC's cheerfully ignored
    2. Re:Save space! by frogstomper · · Score: 1
      The IPv4 loopback address "127.0.0.1" is represented in IPv6 as "::1".
      Actually, the IPv4 loopback address "127.0.0.1" is represeneted in IPv6 as "::127.0.0.1" (or "::FFFF:127.0.0.1"). The IPv6 loopback address, on the other hand, is "::1".

      HTH, HAND

  86. Its not that much about addess shortage by nr · · Score: 1

    Well, the real problem is not adress shortage its that NAT breaks end-to-end communication. That means that things like video-conferencing, ip-telephony, peer-to-peer, IPsec, instant messaging, etc, dont work becouse they require that both ends can connect to each-other. Thats why NAT is a bad longterm solution and we will need IPv6 sooner or later. Another nice thing is the autoconfiguration in IPv6. That means you dont need any special DHCP servers on the network. The same time you plug the cable into the wall or turn on your computer it will autoconfigure the interface IP address from the router.

  87. Re:Seamless Intergration - far from it by gorilla · · Score: 2

    I think the approved way to do this is for the client to try to DHCP to a IPv6 server. If it gets an answer from this, then it will get either just an IPv6 address, or both an IPv6 and an IPv4 address. If it does not get an answer, then it should try to DHCP to an IPv4 server, in which case it would get only an IPv4 address. The DHCP server would listen on only IPv4 (If it was an IPv4 version) or both IPv4 and IPv6 (If it was an IPv6 version). This way you get backwards compatability for both old clients, and old servers.

  88. It's M$ Time by PetriBORG · · Score: 1

    ::nervous laugh::
    That's all we really need, a proprietary internet controlled by M$. Then they can charge us whatever they want on a per machine basis to login and while their at it, see everything we do so that information can be sold to the highest bidder. Not to mention spying on inovations by competitors.

    Pete

    --
    Pete/Petri "damn, my chainsaw is clogged with 1's and 0's again." --clyde
  89. off topic by Nightpaw · · Score: 1

    And there is no such thing as a NIC card, or for that matter a PIN number. Sigh. Sorry, its just irritating.

    I agree. It's irritating to me, but I feel like a pedantic ass to be irritated. I wish people would just leave the base noun out when they invent acronyms and we could have things like AT machines, NI cards, and GN Unix (ha ha).

  90. Bzzt! Wrong! by mortonda · · Score: 1
    Network Address Translation only provides one-way connectivity.

    One form of NAT behaves this way, but other forms do not. You are thinking of what Linux calls IP MASQ. However, NAT also includes the ability to statically map real IP addresses to private IP addresses inside the firewall. It would be possible, with a good NAT router, to instantly change the IP address in the entire network. DNS propagation, OTOH, would be a nightmare. I'm guessing that's where IPv6 is better.

    1. Re:Bzzt! Wrong! by Obadusni · · Score: 1

      However, NAT also includes the ability to statically map real IP addresses to private IP addresses inside the firewall.

      In which case, you need another real IP address, meaning NAT doesn't help with the problem of limited addresses for true two-way connectivity.

  91. chicken-or-egg problem? by MavEtJu · · Score: 1

    It's a chicken-or-egg problem. Service providers and developers are waiting for demand from customers. Customers won't see benefits until products and services become available.

    I agree that providers are waiting, but developers? It's soo easy to add basic IPv6 support to applications, it's not funny.

    Last week I was trying a new MUD-client and it had IPv6 support. I congratulated the author with it and he said "When looking at it it seemed trivial to add so why not?"

    Edwin

    --
    bash$ :(){ :|:&};:
  92. What do you mean we don't have a problem? by redcliffe · · Score: 1

    The problem is having to use NAT or Masquerading to access the net. I want all my machine to have real world outside IP addresses. To do that we need IPv6.

  93. Wowee, B-Movies are here today! by TACD · · Score: 1
    I can already see the benefits of IPv6. With every household appliance connected to the 'net, finally we can live out some of those classic (er, or not so classic) B-movies. You know, with a hacker or something making all the drawers fly open and shut and the fridge try to eat people.

    Okay, so maybe then it was a poltergeist, but in tomorrow's B-movies it will be hackers.


    But anyway. Is IPv6 truly somehow the end of the road? Is it formatted so that it can be extended indefinitely? Or are our descendants doomed to upgrade their computers to accept an extra 4 numbers in their IPs every few decades?


    And also, the point that someone made about everyone and his agony aunt not having a clue how to upgrade to IPv6... is this a bad thing? Would we miss our precious AOLers? (And remember, future generations will be far more tech-wise than current middle-aged slackers.)

    If what many people say about most platforms and routers being compatible with IPv6 (commendations for the people with enough foresight to set that one up), and the problem is emerging into a middle-distance instead of a long-distance problem, I say go for it! Chances are there will be hitches along the way and everyone can always do with more time...


    As an aside, are there yet any reports of accidental IP banning? As in, Joe Bloggs signs on to some chat room and gets his IP permanently banned, and a few weeks later Fred Bliggs signs on to the same chat room to find he has been already banned? This happened to anyone?

    --
    Security through promiscuity is no better than security through obscurity.
  94. Re:Seamless Intergration - far from it by Brandon+Hume · · Score: 1

    This is almost the way things work now (except DHCP
    for IPv6 is a nebulous concept).

    Most OSes which implement IPv6 treat IPv4 and IPv6
    as if they were completely seperate interfaces. Getting
    an address for each is handled individually, the
    success (or failure) of getting an address on one does
    not affect the other.

    --
    Brandon Hume
    hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/
  95. AVES DNS by Dark+Coder · · Score: 1
    The solution to mapping IPv6 to IPv4's various server application is AVES DNS.

    This is by far the best solution possible without any router or BGP infrastructure upgrade. Works for me.

  96. Can I ask you a ? by Anonymous Coward · · Score: 0

    whether the prosecutor has an email address or not, or just isn't publishing it, why does that make him unable to or less capable of prosecuting MS?

    I have been in the industry ~10yrs (julian calendar :) and besides never listing anything other than a hotmail address, I have even disconnected my cable modem for 6 month stretches at a time (gotta dial in sometimes to work..luv dialup)....anyway...I am trying to say that not being on the net hasn't hampered my ability to stay abreast of current tech or events, I even got outside, lost 40 lbs, and became tan to boot....so stop holding everyone else to your (low?) standards of living

  97. you don't get it, do you? by Anonymous Coward · · Score: 0

    your simple analogy just implies a simple mind behind the thought.....free as in beer, eh?

    man, first of all, TV is FREE to watch because of advertising. So stop being such a whiner and just enjoy it. Second, if you want to stop, play, rewind, or just plain view a movie at your leisure, then they have facilities for this (RENT a movie, fool). As far as, well....let's say...taping the evening news...sure...go ahead..but you're not ENTITLED to it! i.e. driving is a privilege, not a RIGHT, sheesh. If you're upset because you won't be able to STEAL programming and use it for your own nefarious (yet strangely personal) reasons later, then tough. Oh yeah....if you're so "entitled to tape and blah blah wtf" your broadcasts now, just try calling your local tv station/corporate affilitate and ask them to REBROADCAST what you missed...cause you had to work late or whatever..see how far it gets you.

    fucking kids.

    1. Re:you don't get it, do you? by Eil · · Score: 2


      Well, I'll take this mainly as a troll. Nevertheless...

      It appears that you are the one who has not fully grasped the entirety of the situation. I suppose it's not only 100% a matter of rights, but also a matter of ethics. Ever since the advent of VCRs, people have been able to time-shift their viewing in the name of convenience. It's commonplace. As such, most people consider it a fair-use right. Since the government is *supposed* to follow in the interests of the people, it *should* be a right by law. (De facto, I think they call it.)

      For broadcasters to take that away from us while masquerading the action as an anti-piracy measure is not right, not ethical, and should be (in many people's minds, not just my own) considered illegal.

      man, first of all, TV is FREE to watch because of advertising

      As long as we are *forced* to watch the advertisements, TV is not free. The price does not always have to involve money. That aside, I would probably agree to having to watch advertisements if I could time-shift the program. But not if I had a choice.

      As well, mandatory advertisement-watching disallowal of time-shifting would not be in the best interests of the industry either. (Take Napster for example. Is it any coincedence that CD sales have skyrockted in the last few years? Maybe. But I doubt it.) I currently record Star Trek episodes during the week on my VCR for viewing on the weekend because I'm typically a rather busy person. So, if the government came along and mandated this new HDTV technology that prohibits time-shifting and skipping over advertisements, I am one of many types of TV viewers who would be severely impacted. I would probably not watch Star Trek any more. That means I would not even have the *chance* to view the very commercials that pay them to run the show.

      And I might note that I do not consider time-shifting as "stealing." By your own admission, you apparently do. Who's the "fucking kid" again?

  98. No IPv6 multicast routing for one thing by Anonymous Coward · · Score: 0

    We in our university have set up an IPv6 Testnetwork - initially with a bunch of Win2k servers (yes, they do support IPv6, but only experimentally), but we made the discovery that IPv6 multicasting is not supported and Microsoft also seem to have more important things to do than work on their IPv6 stacks.

    We then switched to Linux servers. But development IPv6 stacks in the linux kernel (we had 2.4.9) was also pretty much halted for a long time. And multicast routing? forget it.

    There is a kernel patch that adds a lot of IPv6 functionality, but not IPv6 routing.

    The major IPv6 project www.kame.org has got functional IPv6 multicasting for some other unix variants - but not Linux.

  99. Point the Big Yagi at Buffalo! by BigBlockMopar · · Score: 2

    Hey my dick is bigger than yours because I shaved off all my pubic hairs :)

    Heh. And your girlfriend is a pedophile. ;)

    even 60Hz isn't acceptable, so now we have tv-sets that digitally enhance the image and give 100Hz

    True. You don't see features like that in NTSC sets, though - the 60Hz vertical rate of NTSC means that set mfrs concentrate on other things - like 53" projection sets where the scan lines are 1/4" apart. Ugh.

    IMHO American TV suck, and it suck hard, to many comercials and verry bad picture quality, but mind you that was in 1992

    Too many commercials, I agree. But that's not a technical issue. As for the picture quality, were you watching TV on NYC's cablesystem? [grin]

    A good, clean NTSC signal is very nice. It's nothing compared to a VGA monitor, of course, but neither is PAL. I'm a videophile, I've worked as a broadcast technician, and NTSC's picture quality can be amazingly good.

    and when is the us going to switch to hdtv ?

    When Linux conquers the desktop, IIS users keep their webservers patched, and our home 'net connections are fiber optic with IPv6 addresses.

    Maybe sooner. [sigh] It's the same chicken or egg issue which slows the IPv6 adoption.

    Here in Canada, we're waiting for the US to take the lead. ER is now simulcast in HDTV, but until I point a big UHF Yagi at Buffalo NY and smuggle a receiver across the border, it does me no good.

    --
    Fire and Meat. Yummy.
  100. All USA VCRs will die in 2006 by yerricde · · Score: 1

    The reason to discontinue [405- and 441-line] standards was not the introduction of color. The PAL and SECAM color standards are compatible with the black and white standard introduced in most countries when TV broadcasts started in the 1940s and 50s. Black and white 625 line television sets bought then can still be used.

    But neither black and white nor color, 525 line nor 625 line, 60 Hz nor 50 Hz, will work with digital ATSC signals without a converter box. On January 1, 2006, the FCC will pull all licenses for analog TV broadcast spectrum in favor of encrypted digital television that includes DMCA-protected flags such as "you may not record this program; decoder must insert Macrovision garbage into all analog outputs" and "you may not watch this program on sets larger than X centimeters diagonal measure because any larger sets are assumed to be used in a public performance setting."

    --
    Will I retire or break 10K?
    1. Re:All USA VCRs will die in 2006 by Cro+Magnon · · Score: 1

      On Janurary 2, 2006 the FCC will restore licences for analog TV broadcast spectrum after 250 million angry Americans show up on their doorstep with shotguns and rotten tomatoes!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  101. IP addresses per person by einhverfr · · Score: 2

    The article said that everybody on the planet could plug in millions of devices. This is somewhat untrue. With 128 bit addressing space, 10 BILLION people could plug in 34028236692093846346337460743.177 IPv6 devices each!

    --

    LedgerSMB: Open source Accounting/ERP
  102. Re:Seamless Intergration - far from it by El_Nofx · · Score: 1

    I disagree, from what i have read from cisco and other network vendors, it appears that first the backbone and other major lines will be upgraded followed by local trunks say to a CO and then finally to the home user. All that would have to be done is make sure the user is using a dhcp client that will take either an ipv6 address or a ipv4, once an ipv6 address is leased the machine switches the stack to ipv6, just asks the user to reboot. Windows users are used to that . There is no reason why a router can't have entries in it's table for ipv6 and ipv4 and be able to route both at the same time, they can router both ip and ipx now right. All you would have to do is setup a DHCP that will give out ipv6 addresses and one day turn it on and turn the old one off. You say that no DHCP exists to lease ipv6 addresses, you are right, but you are arrogent to think noone will make one. The burden will be placed on the isp's not the end user. Speaaking from 3 years of tech support experience for Gateway, 99% of users don't know what an ip address is. Leaving any amount of responsibility to the user is a disaster waiting to happen. We had our ISP Gateway.net dropped by our provider UUNet, every single person on Gateway.net had to call in and get a link to dialer upgrade. This took MONTHS and we had people calling in after 8 months wondering why they couldn't get on the net. Paying for it the whole time.
    It must be a seamless integration or it will be a disaster

    --
    It's not the OS it's the user that sucks. If it's user friendly, you get stupider people. - clinko
  103. If you are looking to carve up a Class A by Anonymous Coward · · Score: 0

    Look no further than Compaq, which inherited 16.0.0.0 from Digital Equipment when they bought DEC. Since then, Compaq seem to have sold everything else of value that they got in the acquisition (or just destroyed some bits), so maybe the 16.0.0.0 Class A address is the last remaining asset of that takeover.

    There don't seem to be many of the old DEC systems left in the DNS, but DEC used to use 16. addresses internally, because there was no need to use 10. with their own Class A.

    Maybe Compaq are interested in selling 16.0.0.0. They seem to be burning the furniture anyway.

  104. You are missing the point, think Mobile by jfanning · · Score: 1

    You are all missing the point with thinking about refridgerators, etc.

    You should be thinking mobile devices such as cellphones and PDAs. Soon all of these will be capable of wireless IP and there will be literally hundreds of millions of these devices.

    Even China will soon have more cellphones than the whole US and they have only just started.

    Also, IPV6 is mandatory in UMTS (European 3G cellular networks) so it is more or less inevitable that it will happen.

  105. A nice list of IPv6 links by fuzzel · · Score: 1

    The following list will keep you occupied about IPv6 for some time... oh just for the record ams-ix is doing NATIVE IPv6 since 1998 now... alongside NSPIXP6 and PAIX and some others to be found at v6nap.net.

    First two nice repositories where you can find almost anything IPv6 related:
    IPv6 News and Links (hs247)
    Open Directory Project Computers/Internet/Protocols/IP/IPng/

    And some others important ones which can also be found there:
    6bone
    Belnet
    Bieringer's Linux IPv6 FAQ
    Euronet Belgium
    IPng
    KAME
    Kitame's Debian IPv6 Packages
    Microsoft IPv6
    PuTTY IPv6
    SiXXS
    Sun Solaris IPv6
    Surfnet IPv6
    Trumpet IPv6

    IPv6 for the future (or something advocating like that :)

  106. Re:Graham's Number by vector_infinity · · Score: 1

    The smallest dimension of a hypercube such that if the lines joining all pairs of corners are two-colored, a planar complete graph K_4 of one color will be forced. The actual number is believed to be 6, but the best bound proved is so large that if all the material in the universe was turned into pen and ink it would not be enough to write the number down.

    Now, if we build an Internet which has Graham's Number possible addresses, we had better hope that Graham's number isn't actually six, or there's going to be some problems...