Heh... are you trying to say "TC
P/IP" and "I
PV6"?
Also, we won't be transitioning from TCP/IP to IPV6 -- IPV6 will still use TCP/IP. I think you mean the transition from IPV4 to IPV6, no?
I don't think this will cause too many problems for those that don't know how IPV4 works... I mean, it's just another addressing scheme, and they'll still be typing "google.com" into their browsers. IPV4 vs. IPV6 won't make much of a difference here -- it'll be pretty transparent to the end user.
As for sysadmins and the IT departments, yes, it will take some time and headaches transitioning over -- but it's a necessity. We'll soon run out of IP addresses with IPV4, and the transition and need for IPV6 will soon be evident.
Just like any lazy sysadmin can screw up an IPV4 network, so they'll also be capable of screwing up an IPV6 network. I would think that those sysadmins that are good at networking wouldn't have much trouble with the transition to IPV6 (since IPV4 and IPV6 can co-exist simultaneously) -- if they know "networking" in general and know how to set up a network correctly, then there shouldn't be too many problems.
The Y2K fiasco was blown out of proportion. VERY few home users actually had a computer that was affected by the Y2K "bug" -- it mainly affected large corporations with massive legacy hardware. If you were a sysadmin running modern flavors of Windows or UNIX at the time, then you were pretty much in the clear.