How to Migrate to Internet Protocol Version 6 (IPv6)?

IEC TC 57 just published a new draft document for a future Technical Report:

IEC 62357-200 TR (57/1563/DTR):
Power systems management and associated information exchange –
Part 200: Guidelines for migration to Internet Protocol version 6 (IPv6)

Application: Utility communications using utility-owned and leased networks, including, but not restricted to communication within substations, from substation to substation, from substation to control center / maintenance center, control center to control center, energy management systems, synchrophasors, distributed and bulk energy generation and storage resources and (including fossil fuel plants and renewables) wind-, and solar power generation, storage, demand side management, and demand response for distribution level consumers / producers.

This draft Technical Report addresses the issues encountered when migrating from Internet Protocol version 4 (IPv4) to the Internet Protocol version 6 (IPv6). It describes migration strategies, covering impact on applications, communication stack, network elements, configuration, address allocation, cyber security, and the related management.

The migration will add new need and require more skills of the engineers. It is highly recommended to have some people that start learning the changes that will come during the next 30+ years.

Maybe you start with a small group as we did in the standardization process 15+ years ago in Seattle (WA) in 1999:

Teamwork makes the dream work!

Be aware that the “network infrastructure” becomes one of the most crucial basics for all other infrastructures.

Would your company’s communications infrastructure survive a blackout like the one in The Netherlands today (2015-03-27)?

“Dutch electricity network administrator Tennet says that a large part of North Holland province, which is home to some 2.7 million people, was hit by the outage.

Tennet said on its Twitter feed that the outage was caused by a “technical fault” a high-voltage power station in the town of Diemen, just outside Amsterdam.”

Source: The Independent

I hope it was not caused by an “unknown” GOOSE Trip Message! … Which – at least – would mean it was not related to TCP/IP … IPv4 or IPv6. I am kidding! … a bit.