Monday, February 15, 2021

Test software/hardware in both IPv6-only *and* dual-stack environments?

At $relatively_large_company, we are starting to plan how to deploy IPv6, and naturally want to make sure all proposed hardware and software is tested in IPv6-only environments, to make sure that all functionality is in fact available over IPv6.

However, it's likely that at least some, if not most, of the internal networks will have IPv6 deployed in dual-stack mode, possibly for quite a while (I know IPv6-only is less complex, but that is another discussion). I'm wondering if anyone has found issues with software/hardware that has been rated for IPv6-only environments, when it is used in dual-stack environments. Any experiences, strange interactions, security concerns, etc., that have made you either wish that you had tested with *both* IPv6-only and dual-stack, or glad that you did?

Stated another way, are there any strong reasons why IPv6 testing for hardware/software should happen in both IPv6-only and dual-stack environments?

(I've asked this in the IPv6 group, but would like to ask this here to hopefully engage with a wider audience, and with those having enterprise experience.)



No comments:

Post a Comment