There are four things that drove our decision to move to IPv6-only on our internal network.įirst, IPv4 address depletion, and I’m not talking about public IPv4 depletion. Why move to an IPv6-only internal network? It won’t happen immediately, but we are working on it, and we are further along than any comparable company I know. We are now focusing on having a single stack in the network.
Now, wireless and wired corporate networks are IPv6-enabled too.
They already had their backbone network enabled over IPv6, and they had done work for World IPv6 Day and the IPv6 World Launch and later, in summer 2016, enabled user segments. When I began at Microsoft CSEO in 2016, they had already been working on IPv6 in some shape or form for about ten years. We have a distributed network with lots of different types of user profiles on the network, including developers and a big salesforce. Our biggest user population has over 100,000 users in Puget Sound region in the state of Washington. We currently support over 220,000 users in around 800 offices globally. Of course, it won’t happen overnight because we have a huge environment. All our corporate and VPN networks are dual-stack, but our ultimate goal is to run a single stack in the network. My job at Microsoft CSEO (used to be called IT) is to have our end-users be IPv6-only. 3 April 2019 Microsoft Works Toward IPv6-only Single Stack Networkīy Veronika McKillop – Network Architect, Microsoft CSEO Microsoft CSEO IPv6 Case Study
0 kommentar(er)
