I use it 8 hours a day, five days a week. Works fine.
It has been supported in Cisco IOS since late 11.x. How long does something have to be around before it isn't "new" anymore? Calling someone who implements IPv6 *now* as cutting or leading edge is ridiculous. No it isn't. Get real, Adam. The support is not out there. Most providers are only just now beginning to dabble with it. What does provider support have to do with deploying IPv6 on your network? There is zero reason to wait for your provider - in fact, that is a bad idea. When your provider shows up with IPv6 support you won't be ready to exploit it. I think someone is living in cloud cuckoo land here.
I think you are confusing the issues of organizational [or disorganizational] behavior with arguments concerning the viability and benefits of a technology. Because your organization cannot or does not have a strategic approach to technology has nothing to do with IPv6.
You may be lucky in that someone is prepared to resource your requirements,
As I already explain: we added IPv6 readiness to our refresh cycle and over the course of 2 years deployed IPv6. Doing so didn't require 'resourcing' much of anything.
and maybe that infrastructure was built from scratch.
Hardly.
Older infrastructures may have all sorts of weird and wonderful kludges which support different things which may or may not be critical to business function, and which may or may not be properly and accurately documented.
WHICH HAS NOTHING TO DO WITH IPv6. Your argument against IPv6 is that your network is so full of kludges and hacks that it would be next to impossible. Hmmmm...
Many of those who run these have to struggle to get the resources to support the network infrastructure that they have already got,
Which has nothing to do with IPv6 or if beginning deployment is a good idea. Because your organization is resource starved doesn't count against it as a wise policy.
let alone create the network infrastructure they would like to have, and in the current economic environment this is not likely to get any better. IT departments are often very low in the organisational pecking order or frequently very unpopular in the organisation if they
"Very often", I don't know. Sometimes they are. Sometimes they aren't. That has nothing to do with sound policy about IPv6 deployment.
The comments are very idealistic,
That IPv6 is coming is not idealistic. That is is better to gradually phase in support rather than rushing when you need to is not idealistic. That IPv6 provides some real improvements over IPv4 is not idealistic. That lacking an IPv6 implementation creates potential security issues is not idealistic.
and not really based practicalities of the bigger picture.
Ah, "the bigger picture" - now I understand. Of course, how could I be so naive.
It would be nice to have a magic wand to make everything better, but these are in short supply.
Right - a gradual deployment over two years is a wave of a magic wand.
I think anyone designing a new (or a fundamental update of a) commercial network infrastructure around IPv4 is probably not entirely sane, but the growth of IPv6 is mainly going to be determined by the rate of update of physical infrastructure. This process is not going be fast.
With your approach and deep understanding of "the bigger picture" it will be worse than not fast. At least where you are. Weather is great over here.
On the other hand there are few (if any) benefits for IPv6 deployment on home networks, and it is surprising how much home kit is state of the Ark.
Home networks don't have any policy or deployment of anything at all. That is clearly NOT what we are discussing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org