arstechnica.com— An unlikely combination of IPv6 and NAT experts from the IETF met in Montr?al last week to figure out better ways to allow IPv6-only and IPv4-only systems to communicate with each other.
Oct 6, 2008View in Crawl 4
We already have a standard. It's IPv6 tunneled through IPv4.However, the majority of network infrastructure cannot handle IPv6. All cable companies are using Docsis 2.0 or earlier, which did not call for IPv6 support. Just recently 3.0 was announced with IPv6 support and a new "2.0 + IPv6" standard was released as well. Cable companies have just announced they are going to start rolling out the 3.0 standard next year. Google for docsis 3.0 and your respective company to see when you'll have it.
That really would have made more sense, but when developing the IPv6 standard it was decided to go with a 32 character hexadecimal sequence: a 128-bit address. This was routing and other network information can be encoded into the address.Unfortunately, IPv6 requires an overhaul of lots of physical equipment, at a time when the telecomm networks are already whining about infrastructure costs.
They already are talking about sticking the 32 bit IPv4 address on the bottom of an IPv6 address. The problem is going the other way... properly routing a 128 bit IPv6 address while using only the 32 bits of an IPv4 address.
mooniniteOct 6, 2008
We already have a standard. It's IPv6 tunneled through IPv4.However, the majority of network infrastructure cannot handle IPv6. All cable companies are using Docsis 2.0 or earlier, which did not call for IPv6 support. Just recently 3.0 was announced with IPv6 support and a new "2.0 + IPv6" standard was released as well. Cable companies have just announced they are going to start rolling out the 3.0 standard next year. Google for docsis 3.0 and your respective company to see when you'll have it.
gabacho2Oct 6, 2008
I'm quite sure that you did not understand the word "working" from the title.
geekmansworldOct 6, 2008
That really would have made more sense, but when developing the IPv6 standard it was decided to go with a 32 character hexadecimal sequence: a 128-bit address. This was routing and other network information can be encoded into the address.Unfortunately, IPv6 requires an overhaul of lots of physical equipment, at a time when the telecomm networks are already whining about infrastructure costs.
swordedgeOct 7, 2008
network hardware cost is NOT an issue. IPv6 is software. Update the rom and BANG, you have an IPv6 router.
swordedgeOct 7, 2008
They already are talking about sticking the 32 bit IPv4 address on the bottom of an IPv6 address. The problem is going the other way... properly routing a 128 bit IPv6 address while using only the 32 bits of an IPv4 address.
ispshadowOct 7, 2008
I was stunned to see that China has been using IVI for two years now. Really?
esc27Oct 7, 2008
IPV6 is bloated, slow, compatible with existing technology, etc. We should just all wait for Win.. I mean IPV7.