Hi Max and list,
Maximilian Wilhelm <[email protected]> writes:
>> "We have enough IPv4 addresses for ourselves, so this isn't a problem to
>> us."
>
> That's the dumbest and sadly most oftenly heared sentence in this context.
that's why I like to quote it...
> I had hoped that there were some IPv6 only/broken IPv4 services around
> today that would show people that's not the way to go, but I don't
> know any. Does anyone have a good example here?
That's going to be difficult. If you run a service for money, making it
v6only will cost you a lot of market share, so everybody still needs to
support IPv4 in that kind of business. You can only expect that on
sites run without regard for money by some hyperenthusiastic hobbyists.
And frequently enough, enthusiasm is a bad substitute for competence.
Things change drastically however if you talk about internal networks.
There you can at least sometimes only make the servers dual stacked but
connect the bulk mass of clients to either v4 or v6 only.
> Even in the educational sector where I work, where we have enough[tm]
> money for hardware and tutorials there's no interest in a useful deployment.
> Activating v6 in the 5k+ users wifi is delayed (again) for next year, because
> it's neither important or urgent. That's the point where I gave up
No, don't give up. Try to be nice so they don't hold a grudge against
you when the time comes, and then renegotiate your terms.
Just make sure they don't blame you for not telling them. Sounds crazy,
but that's how people sometimes tick: You tell them to watch out, they
ignore you, things blow up in their face, so you should've warned---and
protected---them, because after all you already knew beforehand.
> What I absolutely fail to grasp is why people don't want to deploy
> this v6 stuff while they have a chance to do it without user/customer/
> peer pressure but want to wait until the pressure gets too high.
When do people go to the dentist? When they can't stand the pain
anymore. Or put differently: "As far as I can tell, everything works
for me. So why should I allocate some of my limited resources to this?"
>From a technically challenged business perspective it makes perfect
sense.
In some cases you might reason that fixing your WiFi takes at least
three months (or whatever), will be necessary without prior warning,
will incur significant extra cost and most importantly, also a
loss/reduction of service lasting three months.
Or put another way: If you wait until you notice that you're losing
money, then you'll lose money.
However: In most organizations management has got so used to being lied
to with similar claims that they'll simply trust their own "experience".
In other words: "As far as I can tell, everything works for me." Makes
it rather hard to be heard.
Cheers,
Benedikt
--
Benedikt Stockebrand, Stepladder IT Training+Consulting
Dipl.-Inform. http://www.stepladder-it.com/
Business Grade IPv6 --- Consulting, Training, Projects
BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/
