(Look at the ID ;-) )

I think this guy summarised it well -

http://www.ietf.org/mail-archive/web/v6ops/current/msg06483.html

Here in Australia, at both private enterprise and government, nobody has even begun to think about IPv6 at any level.

Are you sure about that? I suggest you check the dates in the PDF linked to at the following URL - http://www.finance.gov.au/e-government/infrastructure/internet-protocol-version-6.html

"If you're an experienced network expert it may not be surprising, ..."

and they're the people at ISPs who're running it (I used to be one of them). Running the Internet backbone is self regulating, because everybody who does it also has a vested interest in policing it. This article is FUD. The clueless tech people can continue to remain clueless.

None of those have happened to me. I in fact left a job last year where I'd done what I said should be done. and they've said I'd be welcome back if I was looking to.

And I should say, the approach to take is to be constantly eliminating the weakest link until the point where eliminating it is not feasible. You'll end up with the weakest link being very strong - availability is a weakest link type problem.

Build redundant systems on work time, such that only common faults are those that are unpredictable and unpreventable e.g. building catching on fire. When your systems are resilient to common faults, you don't have any anxiety about leaving them to look after them selves, and you know that if a common failure occurs, recovering is easy because you're prepared for it.

"There's no excuse for predictable and preventable downtime (except laziness and incompetence)."