IPv6 experience from a large enterprise - Networkshop44
•Download as PPTX, PDF•
3 likes•2,484 views
This document summarizes Microsoft's experience transitioning to IPv6 over many years, including enabling IPv6 on their corporate network, data centers, and internet access. It discusses operational issues encountered and solutions implemented. It also outlines Microsoft's plans to further expand IPv6 usage and eventually transition away from IPv4, such as piloting IPv6-only networks and deploying NAT64/DNS64 to allow IPv6-only client access.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to IPv6 experience from a large enterprise - Networkshop44
Similar to IPv6 experience from a large enterprise - Networkshop44 (20)
More from Jisc
More from Jisc (20)
Recently uploaded
Recently uploaded (20)
IPv6 experience from a large enterprise - Networkshop44
- 1. IPv6: Experience from a Large Enterprise Marcus Keane
- 4. • 1999 Microsoft Research looking at IPv6 • Acquired ARIN IPv6 /32 prefix 2001:4898::/32 • 2005-2006 Microsoft IT started working with IPv6 • 2006-2012 IPv6 collaboration across groups • World IPv6 Day • World IPv6 Launch • Mostly grassroots work
- 5. • Operating systems IPv6 capable • Transition technologies • Security and monitoring • On-premise DCs IPv6 enabled • Internet Access • Peering with AS8075 and Level3 • Advertising /48s out of regional /32s • Enabling IPv6 internet to labs on request
- 6. • Corporate network • 63% of managed hosts are v6 enabled • Approximately 50% of corporate access network is native enabled • 6,800 internal v6 routes, 20,000 internal v4 routes • Example DNS AAAA to A record comparison • This includes teredo… Europe Redmond A – 70009 A – 913,700 AAAA – 69,302 AAAA - 654,734
- 7. • Increased LAN control plane traffic • Rogue RAs • FIB requirements on routers • Incongruent traffic for IPv6 and IPv4 • Fixed by IS-IS • Miscellaneous operational issues - MPLS, DAD, etc. • User training
- 8. • MSIT has no more public IPv4 space • We have no more RFC1918 space • Guest wireless network • Corporate network expansion • We have overlapping RFC1918 space • Azure and online properties • Acquisitions – Nokia • This is getting complicated. And expensive
- 9. • Pilot IPv6-only on corporate network • There is an existing small pilot in Redmond, USA • Works for most applications • Still working on some issues – DHCPv6 related • Pilot IPv6-only on wireless guest network • This works well for iOS/Windows Phone • Still have some issues to solve – Android • Both using: • DNS64 • NAT64
- 11. • Deploy IPv6 to remaining access edge networks • This is being automated • Convert DC apps • Most DC apps are still using an IPv4 VIP • Convert to IPv6 with evolution of application • Deploy Global NAT64/DNS64 • Start Removing IPv4 from access edge networks • Network-of-Things will have to remain Dual-Stack
- 12. • DHCPv6 stateful or SLAAC or both? • MPLS for IPv6 – segment routing? • IPv6 Multicast • Network Management
Editor's Notes
- 1999 Microsoft started using IPv6 within research and development labs and via tunneling across the IPv4-only corporate network Also advertised prefix from 3ffe::/16 network via University of Washington Pacific Northwest Gigapop to 6bone research network Developed global IPv6 addressing plan and migrated ISATAP from Windows servers to Cisco routers
- Native IPv6 Office 365 Xbox.com Microsoft.com Windows update (test) Skype for Business Applications via NAT64; no noticeable performance degradation SharePoint Yammer Bing search Windows RPC/SMB Windows RDP Xbox VOD, video playback
- DNS64/NAT64 placement and redundancy will be crucial