andrew michael baron wrote: > So Clint, are you saying that you are not interested in considering a > problem of this magnitude that will arrive in ten short years from now?
No, I said it would be 10 years before IPv6 will be in wide use. The military will drive it's adoption initially (following of course the academic implementations in place now), followed if not coinciding with wireless adoption. Wireless will be the first to widely adopt it, simply because it's a closed box, they can work with the manufacturers to support it, and they have more IP-enabled devices to support than any other ISP. Much much further down the road will be the adoption of IPv6 on PCs and for the wider Internet. The main problem with IPv6 adoption is the problem with maintaining two Internets, with tunnels running amuck tunneling IPv6 over IPv4 and later IPv4 over IPv6. It's a huge logistical problem. To explain where I'm at in the chain, I implement new networks, systems and software for a living. When the adoption rate has picked up to the point where all the devices I need to glue together a cohesive network, with computers, routers, switches, network devices (firewalls, load balancers, etc), have stable IPv6 implementations, then I'll start considering what I need to do to learn an entirely new set of protocols that will double the amount of knowledge I need to have to operate effectively. Throwing away codebases with 15+ years of work in developing an IPv4 stack is no simple undertaking, and even bigger than that is throwing away the experience of a workforce with 15+ years of experience working with IPv4. Addressing is only one of the reasons to consider switching to IPv6, and it's probably not even the best one. Among the better reasons include QoS built into the IP stack (most implementations don't contain QoS support right now), IPSec built into the protocol, better routing based on geographic regions (meaning aggregation is much simpler, requiring less memory to hold routing tables), better autoconfiguration (eliminating DHCP), multicast routing built into the protocol, etc. However, of all of these except addressing are easily done with IPv4 implementations, it's just that they're not available on the Internet in a standard fashion. Which only leaves addressing as the crunch to switch, and since that's not an immediate issue anymore (last I heard 2032 was the estimated date for running out of IPv4 addresses by the IANA), we're still waiting for a driving force to drive adoption. > > Yea, years away is not very far either Clint, you should be very, > very scared. I'm warning you Clint!!! This is dangerous. You should > be VERY VERY worried. I don't know if this was serious or sarcasm. I'm not worried, and I'll tell you why. I understand at a fundamental level how IP and the Internet works and how addresses are assigned. I can tell you, from memory, in intricate detail how data moves about on the Internet, from session establishment, to packet routing (and the protocols that build those routing tables). I can tell you detailed reasons why addressing is no longer an immediate issue, and thusly with that expert knowledge, I'm not concerned. There's not a lot of things I'm an expert in, this is one of them, so I'm thusly incredibly confident that there's absolutely nothing to be concerned about. > > Whew! you are hot tonight! > Yeah, I know, sorry. It's really not an incredibly topical conversation for this list, but still fun none-the-less. We should probably take it off-list if we want to continue past this point. Clint -- Clint Sharp New Media Guy & Technologist ClintSharp.com Contact Info: http://clintsharp.com/contact/ We are the media. ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/lBLqlB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/videoblogging/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
