TKJunkMail
Enjoy the sun
Premium
join:2002-03-03
Avalon, NJ
 ·Sprint Mobile Broa..
 ·Comcast
|  Look for this to be a very slow process
One of those who replied to Cringley's column made a good point. This may take 10 to 15 yrs to complete thru 4 major phases.
1) the core infrastructure of the Internet will need to be upgraded to support a IPv4-IPv6 hybrid system.
2) ISPs and Data Centers will need to upgrade their systems, also supporting a hybrid system.
3) Then, everybody, everywhere will need to start installing new home networking devices that support IPv6. A lot of them already do, but most don't yet.
4) Then, there will be a period where backward compatibility will be allowed, like for older cell phones, etc.
In my math, that is going to take between 10-15 years to complete all 4 steps.
Marcelo Calbucci External Link | Nov 04, 2006 | 6:20PM IPV6 was being discussed at my company back in 1998. And very little has occurred in the intervening years. Look for this to be a very slow process.
--
--
My BLOG
My Web Page |
|
SteveLV702
Premium
join:2004-04-22
Henderson, NV | 3) is kinda false as most routers would just require a new firmware build.... You can already get one for a Linksys WRT54G |
|
TKJunkMail
Enjoy the sun
Premium
join:2002-03-03
Avalon, NJ
·Sprint Mobile Broa..
·Comcast
| said by SteveLV702  :3) is kinda false as most routers would just require a new firmware build.... You can already get one for a Linksys WRT54G Isn't that 3rd party firmware, and not from Cisco/Linksys.
--
--
My BLOG
My Web Page |
|
SteveLV702
Premium
join:2004-04-22
Henderson, NV | reply to TKJunkMail
Yes.... But pretty sure when IPv6 becomes standard.. Linksys, DLink and everything would release an official firmware update..
Aint gonna have to buy all new equipment. |
|
dslpartner
join:2005-02-18
| said by SteveLV702 :Yes.... But pretty sure when IPv6 becomes standard.. Linksys, DLink and everything would release an official firmware update.. Aint gonna have to buy all new equipment. No, most of the vendors will say that the products you are using today are at EOL and no new features will be added.
Or that it is unable to support IPv6 due to memory restrictions or it uses integrated chips that got the routing engine on silicon which can no be update.
End of story is, vendors expect you to buy new equipment.
--
"Perl is executable line noise, Python is executable pseudo-code." |
|
SteveLV702
Premium
join:2004-04-22
Henderson, NV | reply to TKJunkMail
well I know better and will either make my own or use 3rd party firmware........ |
|
Kearnstd
Elf Wizard
Premium
join:2002-01-22
Mullica Hill, NJ | reply to TKJunkMail
if IPv6 doesnt have a route to enhance the bottom line US ISPs wont do it.
--
[65 Arcanist]Filan(High Elf) Zone: Broadband Reports |
|
Ulmo
join:2005-09-22
San Jose, CA
·Comcast
 ·SONIC.NET
2 edits | said by Kearnstd :if IPv6 doesnt have a route to enhance the bottom line US ISPs wont do it. Interesting point. Probably a phase out situation will occur: at some point, if IPv6 goes forward (all the techno stuff is basically at a point that it could), then the system will hybridize. After that, IPv4 won't look that bad, since it will still work as a backward compatible situation. Eventually, all equipment would be made to work well with IPv6, since so many would require it at some point. Then, IPv4 will still be OK. But then it will just slowly fade away in that scenario. Then, at some point, the administration of "old outdated IPv4" stuff will become a sort of burden, and it will be phased out at that point. MIT-MC and MIT-AI would need reprogramming to work right. (They were already decommissioned.) I don't know how long all of those steps would take. Very few people are rushing it.
Small P.S.: Sonic.net ISP internal backbone is IPv6-IPv4 hybrid native, from what I understand, although I'm sure some clarification could be made about those points. |
|
BF69
join:2004-07-28
Camden, TN
| reply to Kearnstd
said by Kearnstd :if IPv6 doesnt have a route to enhance the bottom line US ISPs wont do it. Well very soon we will run out of web addresses so it's in the interest of the ISPs to get moving on this. And 15 years will be many years to late to be doing something about this. |
|
