Since all major OS support ipv6 there's nothing to educate about other than perhaps new IP address form.
Software upgrades? Like what software, OS to support NAT64? Which every major OS supports? (Including Windows 7. The holdouts are ancient telephones and tiny embedded trash.)
Toolchain updates are important... if you use IP addresses directly, bypass the OS network stack and so not support names. This likely means that software is junk that should've been replaced years ago and likely some internal cookery.
This leaves tests and dynamic DNS.
Not so fast. With over 60.000 clients (yes with all known OSes and versions known to man), 10.000 servers (yes with all known OSes and versions known to man), 50 network firewalls, firewall on nearly all hosts (clients & servers), it might be just a little more then a sed call.
> IDS are dinosaurs and junk that are generally worthless.
They're part of the infrastructure, partly "just a compliancy thingy" but also part of the layered security model. Hell, there is even antivirus software for that exact same reason.
> [...] there's nothing to educate about other than perhaps new IP address form.
That is a joke right? I am sure you know a little bit more about v6 then "it's just a longer address"
> Like what software
Like software that touches IP addresses. DHCP (if that's your choice for v6), monitoring tools (yes there is loads of that which does not support v6 (mainly home made crapola) etc.
You might live in a greenfield environment, homogene and clean. Loads of older organisations run everything ever invented within the last 20 years.
Keeping (private) v4 working is hard enough.
Even drafting a project budget for v6 makes management go balistic. - firewall & IDS upgrades
- firewalls rules
- accountablity
- dynamic DNS
- employee education
- toolchain updates
- upgrades of software
- functionality tests
Not all companies employ NY or Google level engineers who "just roll out v6" on a Sunday afternoon.