On Tue, 20 Dec 2011 11:07:45 -0800, D. Stussy <
spam+ne...@bde-arc.ampr.org> wrote:
> Is there a significant reason for news servers not supporting IPv6?
>
> Only 16% of my U.S. peers and about half of my non-U.S. peers even have
> IPv6 addresses. It really doesn't take very much to enable the protocol,
> even if it's just for a 6to4 (2002::/16) address.
6to4 has it's own set of problems (from anycast routing relating, to
firewalls blocking unknown tunneling protocols, MTU issues due to broken
PMTU discovery and similar etc).
So in order for it to have IPv6 news servers :
a) you need to have working IPv6 at your organisation (and networking guys
have their own set of problems, from hardware performance issues to
software incompatibilities -- and big players like Cisco also are not
without sins here)
b) your backbone provider needs to have working IPv6 too (don't know how
well it's in the US, in Croatia still 80% of commercial ISPs are not
offering IPv6 in production). Or you need to go with the tunnels (which
have their own set of problems, and have the networking guys hate you for
holing through their carefully setup firewalls :)
c) sysadmins need to invest time to setup, configure, verify and
troubleshoot the IPv6 problems with the system. And software might have
problems too in so little tested IPv6 environments.
And all that for no immediate gain and on service which is in most cases
(there are exceptions of course) not a leading bussiness thing. So, yeah,
things are going somewhat slow -- can't say I'm surprised.
I forsee at least 5-10 years until IPv6 traffic becomes somewhat on the par
with IPv4...
(Still;
newsfeed.carnet.hr works over IPv6 and welcomes IPv6 peers)
--
Opinions above are GNU-copylefted.