Microsoft is betting big on devices, all the predictions is for devices to be network connected and volume to grow Sony announced every device will be network connected
Peer to Peer for applications is very compelling Microsoft is making a bet on real time communication Napster and Gaming example NAT break peer to peer. # of PSS calls where people can’t get video conferencing to work – because they are behind a NAT Net attached consumer electronics and gaming apps emerging - Want to record movies from outside the home, want to control the heating & alarm system from outside the home
Japan: Government incentives to move to IPv6 8 Billion Yen Subsidization already allocated Time-limited IPv4 addresses expire in 2005, when 100% IPv6 1000x /48 sites at 4/02 NTT commercial deployment of IPv6 e-Japan Priority Policy Program: “Internet users 80M by 2005. Essential to promote IPv6 to private enterprise, government bodies, organizations and personal users.” China: 2150 attendees, 5/02 summit ~9M Global IPv4 Addresses (137 /16’s + 27 /24’s), 1.3B people US: Lagging industrialized world, but has 74% of all IPv4 addresses Lag won’t last much longer as new scenarios are enabled c.f. lag in cell phones Europe: (following Japan) 2/02: Euro Commission: “Europe must work harder to shift the Internet to run on IPv6 to make room for the flood of wireless devices” “ Current reserve of addresses is expected to run out in 2005” Government sponsorship of pilot deployments Wants to be leading internet economic region by 2010 Skanova– IPv6 ISP Korea: (most broadband) ~28M Internet users, 60% population ~8M are broadband, 28% OECD: highest penetration Government incentives to move to IPv6 22% APNIC IPv6 pTLAs
Address Shortages is very real Not enough IPv4 addresses Everyone has seen in the news the focus in Europe and Asia with governement involvement around v6, people really focusing in on MIT and Stanford with their allocation of addresses Application writers don’t handle changing IP addresses well today. Protocols such as voice don’t work. New requirements for security. Two month effort on security to do code reviews and threat analyses to make sure the windows platform is secure.
Key thing I want you to walk away here with is the urgency of the IP address shortage. Seeing a shortage today as you are seeing NAT’s deployed
Address ability of each end point. The client – server model doesn’t work when you want to instant message or call someone from either end. NAT’s only allow communication that has been initiated from the inside out. Always chasing a new filter that needs to be added. We defined ways to automatically open the NAT but than people have double NAT’s.
Key to mobile ip success is fast handoff for two way communication When the ip address changes IPSEC has to renegotiation the keys causing a delay in connectivity. Mobile IPv4 We felt at Microsoft that it wasn’t deployable due to the foreign agent reliance. Thus we are saying No to NAT and IPv4
Similar to NAT’s firewalls break end to end connectivity Most firewalls operate on the basis of which port is open – can be limiting to It is not really necessary for me to setup a secure communication session with another company across the internet
Upper layer protocols unchanged!
End to End Connectivity is key for a world of web services. There is intelligence on each end of the cloud as well as within the cloud. Three types of applications Native Sockets Applications – these are applications who are written very close and aware of the network. Data Structure change to handle the larger addresses, deal with multiple ip addresses, focus of the platform is to provide the ip addresses in the correct order so applications should work down the list for connectivity. Higher Level applications such Enterprise Applications do not need to change as they are based on middle layer components for example Outlook is written on RPC, once RPC is enabled than Outlook doesn’t need to change. SOAP, XML are other examples where they don’t need to be updated. New application types that can take advantage of new v6 features, for example peer to peer. Microsoft has a big effort on providing a framework for peer to peer applications and the adhoc networking experience which is better in a v6 world. Added Managed Code. Remember the goal is protocol agnosticism.
6to4 used to connect IPv6 “islands” across IPv4 “ocean” IPv6 packets carried in protocol type 41 IPv4 packets 6to4 hosts get global IPv6 addresses V4 address embedded in /48 prefix (2002 is assigned Top Level Aggregator, or TLA) Example: 18.104.22.168 is 0x9D3B8F21, yields a prefix of 2002:9D3B:8F21::/48 6to4-enabled routers at IPv4 Internet boundary Router not always necessary in the single PC case Alternate scenario has both host A and host B with separate prefix when each of them get a unique IPv4 global address from the ISP. This is rare. DNS configuration is via IPv4 today moving to native in the near future 6to4-enabled relays facilitate reaching IPv6 destination
Teredo extends basic tunneling for IPv6 island-to-IPv6 island beyond NATs Uses UDP over IPv4 rather IPv6 over IPv4 Teredo hosts get global IPv6 addresses Teredo servers: Address discovery, Default “route”, Enable local “shortcut” Teredo relays: Send IPv6 packets directly Works for all NATs – widespread deployment; Any number of NATs
Cookbook for NEPs
IPv6 Stewart Tansley Program Manager Windows Core Networking http://www.microsoft.com/ipv6
IPv6 Roadmap 2002-04 2004-?? “ IPv4 Ocean, IPv6 islands” IPv6 in the home Pilot deployments in Asia Broadband ISPs in Asia Enterprise deployments Broadband ISPs in Asia/Europe ISPs in North America ? 3G WWAN 20xx “ IPv6 ocean, IPv4 islands” IPv6 is everywhere Hosts are still dual-stack for compatibility with older devices Windows XP SP1 Windows.NET Server Transparent connectivity via 6to4, Teredo, ISATAP Windows CE.NET Industry Trends Windows Roadmap Windows and MS application support IPv6 natively Top tier 3rd party apps