Ist IPv6 bei Microsoft schon angekommen? Gerne möchten wir Ihnen aufzeigen wie Microsoft das Thema IPv6 für Ihre interne Netzwerkinfrastuktur einsetzt. IPv6 ist jedoch auch wichtiger Bestandteil unsere Public Cloud Offerings und bereits stark vertreten. Abschliessend soll ein Blick auf unsere Software Entwicklung und dessen Nutzung von IPv6 das Bild abrunden.

1. A View from our Datacenters, Internal IT up to our Software
Stack.
Technical Solution Professional – Datacenter
Microsoft Switzerland

4. Source: http://mnlab-ipv6.seas.upenn.edu/monitor/index.html

6. Site Participating? Site Participating?
Google Yes MSN.com No
Facebook Yes Go.com No
Yahoo Yes Bing Yes
YouTube Yes CNN No
Amazon No AOL.com Yes
Wikipedia No PayPal No
Blogger Yes WordPress No
Twitter No ESPN No
eBay No NetFlix No
Craigslist No Flickr No
LinkedIn No Weather Channel No
Live.com No Huffington Post No

8. great
% Market Share
Windows 7 Windows Vista Windows XP
Linux Mac Mobile
5% 8% 1%
36%
42%
Source: http://www.w3schools.com/browsers/browsers_os.asp
8%

11. Special News:

14. 59 markets and
36 languages
76 markets and
48 languages
200+ CLOUD SERVICES

15. Microsoft has more than 10 and less than 100 DCs worldwide
Amsterdam
Dublin
Quincy Chicago
Japan
Hong Kong
Boydton
Des Moines
San Antonio
Singapore
Multiple global CDN locations
Quincy, Washington 27MW 100% Hydro power
San Antonio, Texas 27MW Recycled water for cooling
Chicago, Illinois Up to 60MW Water side economization, Containers "Datacenters have become as vital to the
Dublin, Ireland Up to 50MW Outside air cooling, PODs
functioning of society as power stations."
The Economist

17. 1989-2005 2007 2008 2010+
Scalability and Sustainability
Capacity Density and Deployment 1.2-1.5 PUE Reduced Carbon, Rightsized
~2 PUE 1.4 – 1.6 PUE Air & Water Economization 1.05-1.20 PUE
20 year Technology Minimized Resource Impact Differentiated SLAs Faster Time to Market

19.  No mechanical cooling
 Ultra-efficient water utilization
 Relentless focus on renewable materials
 Near-JIT deployment
 Low initial capital investment
 Scale with business demand
 Deploy 1 to 10,000+ servers at a time

20. www.globalfoundationservices.com
http://blogs.technet.com/msdatacenters

23. •Dual Stack and limited native network deployments support v6 needs
•Reliant on transition technologies
V4 predominance •Gaps in Tools, Network, and Products block aggressive adoption
FY06-FY10
•Achieve Parity between v4/v6 wherever possible
•Migration to v6 naturally happens during network and server upgrade cycle
Managed •Requires commitment by Infrastructure, App, Ops, Security, and Product teams to proper planning in place.
Coexistence •Reduce/Eliminate Transition Technologies.
FY10-FY14
•V6 displaces v4
•Management control plan becomes v6 capable
V6 predominance •Legacy systems may still require v4 (printers, environmental)
FY14-FY??

24. 2001 First Deployments supporting research and Dev
• Limited support from vendors
• Deployed using experimental 6bone address space.
• Deployed on dedicated devices due to poor performance on routing platforms
2002-2004 limited expansion
• A single ISATAP instance deployed in each region (Redmond, SVC, Dublin, Singapore)
• Pockets of native v6 deployed across enterprise
•Limited to Dev and Research groups with a documented business need.
•“stitched” together across the enterprise network on a link by link basis.
2005-2006 Enable enterprise backbone
• Obtained new v6 address space from ARIN and RIPE. Entire network readdressed into new address blocks.
• Requests for native v6 enabled networks grow
•Operational issues in connecting disparate v6 clouds become commonplace
• Network hardware capable of routing at performance parity with V6 is introduced during hardware refresh cycle.
• Native v6 enabled across all backbone and tail site WAN links to resolve issue
• End user networks still require justification for v6 due lack of security and performance visibility.
2007-2010 Dealing with growth
• Client and Server OS platforms become v6 capable
•ISATAP usage grows concurrently, causing scaling/performance issues
• Redesigned ISATAP infrastructure to distribute service across the backbone
• IDS infrastructure becomes v6 aware

25. IPv6 has been enabled across the majority of the network backbone for the past 4 years.
• Host connectivity is enabled on an as needed basis
•Limited to Dev, Test, Research segments due to lack of features and management visibility
• Build process supports v6
Leveraging dual stack hosts and network transition technologies
• Dual Stack Hosts
•V6 is the primary choice for dual stack host (ISATAP or Native)
• Transition Technologies
•ISATAP : Provides connectivity between dual-stack hosts across a v4 network.
• Dealing with scaling and support issues
•NAT-PT : Provides a 6 to 4 NAT translation and is used extensively for Direct Access to provide access to systems that are not v6 capable.
• depreciated as an IETF RFC, limited industry adoption.
Current Stats
• Infrastructure
•30% of access networks are native enabled
• 2703 Corp v6 routes (Internet has 2824)
•Client/Server
•80% of clients are dual stack
•40% of servers are v6 capable
• Traffic
•We currently don’t have the ability to monitor or measure native v6 traffic.