So, the IPv4 sky is not falling. Net risk to you for not jumping on IPv6 now (if you have enough IP addresses) nada. If you have additional questions for Jeff Doyle? Post them at his blog. Also, just for fun, might want to check out the IPv4 versus IPv6 argument story in the package Networking's 50 greatest arguments.
The Cisco Subnet blog is the official blog of the Network World Cisco Subnet community, managed by Editor Linda Leung. Cisco Subnet is the independent voice of Cisco customers and is your gateway to daily Cisco news, blogs, opinion, books, prize giveaways and more. Visit the Cisco Subnet home page daily and while you are there, subscribe to the Cisco Alert e-mail newsletter, which includes news and views generated by the Cisco Subnet community as well as Cisco-related stories on Network World and elsewhere on the Web.
(WAN community)
|
|
IPv6: Pay attention to your public DMZ servers now...
Jeff -
As discussed, it could be quite some time before
enterprises have to worry about IPv6 internally.
However, that's definitely not the case for their
publically-facing servers, and enterprises should
be looking into this situation now, not in 5 years -
Here's the problem: The ISP community really gets no
choice in deploying IPv6, and they'll need to connect new
customers via IPv6. There'll certainly be a pool of IPv4
addresses and some form of translation for backward
compatibility, but the reality is that those new IPv6-
connected customers will have a much better time
reaching sites which have dual-homed IPv4/IPv6
websites than trying to use advanced web services
via translation gateways to IPv4-only enterprise web
sites.
So, while I agree with you that enterprises really do
not have to concern themselves with moving their
internal infrastructure to IPv6, for the sake of the ISP
community it might be useful to tell your readers that
they should indeed think about making their public
facing servers (web, mail, etc) dual-stack as soon as
possible.
/John
Re: Fuggedaboutit
Dear Friends,
I did not say anything to the effect of "forgetting about" IPv6, and have a distinct problem with the way what I did say has been represented in the headers to this chat. I have worked diligently for years to promote IPv6 and encourage people that they need to be planning for it *now*, because IPv4 addresses have little time left. The editors have jumped on my position that IPv6 is not as immediate an issue for enterprises as it is for service providers, simply because enterprises do not burn through public IP addresses as fast as SPs, and distorted what I said. But enterprises *do* need to be thinkinig about IPv6 *now* and making preliminary plans. John Curran in his post below makes some very good points as to why you could find yourself trying to imlement IPv6 in "panic mode" if you don't plan properly now.
Network World yanked the rug out from under me with these headlines, and after a weekend of dealing with the blowback from this I certainly won't be doing any more live chats; I can't afford further damage to the things I've worked hard for over the years.
--Jeff Doyle
Editor steps up -- my public apologies to Jeff Doyle
Hi all,
I'm the one that wrote that headline. I apologize to Jeff and to anyone else who read the headline. I have changed the header of this chat, too.
As for the importance of IPv4 or IPv6 right now, five years from now or ever, anyone that would like to publish their viewpoints and jump into the debate can contact me. Network World will be happy to cover all apsects of this debate.
RE: IPv6 in the Enterprise
Jeff,
Great discussion here. Last time I saw you was out in Denver I think. Seem like you're staying busy...
Regarding the IPv6 discussion, I agree with what you're saying regarding the need for IPv6 in the enterprise. However, I'm wondering if we're going to see it there more quickly based on other factors.
I'm starting to see IPv6 deployed a lot within the government space (especially military). My experience leads me to believe that in a couple of years the guys & gals that are building IPv6 networks in the military today will have completed their tours and will be out working within the enterprise market.
Now, even though they won't need to deploy IPv6, since they have been educated on the technology I'm thinking they may start deploying it because, well, that's just what geeks like us do. Same reason we deploy beta software into production environments and we drive our IT guys crazy by running "non-standard" software like Firefox on our laptops - we like being on the edge...
Your thoughts?
Josh