Ivan Pepelnjak <[email protected]> writes:
> The problem is often internal networking. Every large cloud provider
> probably wrote their own overlay networking implementation, and would
> have to reimplement it for IPv6
I can't hear it anymore.
Sometimes IT is a world full of surprises and magic. Puff and it
1999. Oh year 2000 is coming[1]. Puff and the support for Windows XP[2]
ends. Puff and there are only few IPv4 addresses left. Puff and many
access providers are doing some form of large scale NAT and maybe
IPv6. Puff and the solution we bought last year doesn't support
IPv6. But we need IPv6 now.
About two years ago there was a large German VoIP provider complaining
that all these evil German cable providers had started using IPv6. They
wrote about it in an their BLOG. There were about 70 comments in the
form of "Why don't you just provide IPv6?"
There was a lot of time to see that IPv6 is coming. There are still
networking projects today that are not build with IPv6 in mind[3].
Just my 2 cents.
Jens
[1] I attended an IT training in 1999 and the trainer ask "Anybody of
you know COBOL? I told a customer about 20 years about y2k. He called
last week."
[2] Just mentioning this because I was hired by an Insurance company to
do IPv6 consulting while some people behind my were managing the
transition from XP to Windows 7.
[3] "We never will need IPv6" or "We can add this later" are the most
common answers I guess.
--
----------------------------------------------------------------------------
| Foelderichstr. 40 | 13595 Berlin, Germany | +49-151-18721264 |
| http://blog.quux.de | jabber: [email protected] | --------------- |
----------------------------------------------------------------------------
