Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. IPv6 Update Windows ® Networking & Communications Microsoft Corporation
  2. 2. Agenda <ul><li>Enabling new engaging experiences </li></ul><ul><li>Today’s networking challenges </li></ul><ul><li>IPv6 and transitional technologies </li></ul><ul><li>Microsoft’s IPv6 status and roadmap </li></ul>
  3. 3. Deliver New Engaging Experiences <ul><li>Real-Time Communications (RTC) </li></ul><ul><ul><li>Instant messaging, voice, video </li></ul></ul><ul><ul><li>Real-time game play / collaboration </li></ul></ul><ul><li>Collaboration </li></ul><ul><ul><li>Project workspaces solving a need </li></ul></ul><ul><ul><li>Sharing your files with other people </li></ul></ul><ul><li>Shared experiences </li></ul><ul><ul><li>Concert, company meeting, class </li></ul></ul><ul><ul><li>Distribution of product updates </li></ul></ul><ul><li>Pervasive Collaborative Computing! </li></ul>
  4. 4. Today’s Networking Challenges <ul><li>Development and deployment of these new experiences is difficult </li></ul><ul><li>End-to-end connectivity is broken </li></ul><ul><ul><li>Network address translators (NATs) are widely deployed in networks </li></ul></ul><ul><ul><ul><li>Homes, WiFi hotspots, enterprises, branch offices </li></ul></ul></ul><ul><ul><li>Networks have a mix of private and public IP addresses </li></ul></ul><ul><ul><li>Firewalls prevent end-to-end connectivity </li></ul></ul><ul><ul><li>Users and applications becoming more mobile </li></ul></ul><ul><li>Developers implement custom solutions </li></ul><ul><ul><li>Application development is restricted and expensive </li></ul></ul><ul><ul><li>Use client/server model rather than peer connectivity </li></ul></ul><ul><ul><li>Complicated workarounds and manual configuration </li></ul></ul><ul><li>IT and network administrators engineer expensive point solutions </li></ul><ul><ul><li>Deploy specialized relays and gateways to enable communication between applications and/or computers </li></ul></ul>
  5. 5. IPv6 Addresses These Challenges <ul><li>Enables end-to-end connectivity </li></ul><ul><ul><li>More public addresses worldwide </li></ul></ul><ul><ul><li>Improved allocation for ISPs to provision many public addresses </li></ul></ul><ul><ul><li>Eliminates need for NATs and private addresses </li></ul></ul><ul><ul><li>Restores connectivity as appropriate </li></ul></ul><ul><li>Security for end-to-end trustworthy networking </li></ul><ul><ul><li>Temporary addresses provide privacy across multiple sessions </li></ul></ul><ul><ul><li>Authenticated, authorized, tamper proof, private Communication </li></ul></ul><ul><ul><li>IPSec enables host-based authentication and security at the IP layer to augment edge-based security or obscurity </li></ul></ul><ul><li>Mobile </li></ul><ul><ul><li>No need for additional infrastructure or server-side routing </li></ul></ul>
  6. 6. Misconceptions About IPv6 <ul><li>IPv6 security concepts are vastly different from current practices </li></ul><ul><li>Reasons for IPv6 have been eliminated by the development of NATs </li></ul><ul><li>Requires a wholesale network upgrade from the current network infrastructure </li></ul>Businesses Taking a “Wait-and-See” Attitude – Until Now…
  7. 7. IPv6: Where is the Market Today? <ul><li>“ In 2005, all Sony products will be IPv6-enabled.” </li></ul><ul><ul><li>– Mario Tokoro, Corp Exec VP, Sony Corp, March 2003 </li></ul></ul><ul><li>Customers </li></ul><ul><ul><li>Noticeable increased interest in IPv6 in over the past 3 months </li></ul></ul><ul><ul><li>Department of Defense </li></ul></ul><ul><ul><ul><li>Announced IPv6 migration starting in Oct 2003, completing in 2008 </li></ul></ul></ul><ul><li>Independent hardware vendors </li></ul><ul><ul><li>Hardware vendors have the most-complete solutions </li></ul></ul><ul><ul><li>Routers with v6 – Hitachi, NEC, Fujitsu, Juniper, Cisco, Foundry </li></ul></ul><ul><ul><li>Infrastructure </li></ul></ul><ul><ul><ul><li>Firewalls – CheckPoint, NetScreen </li></ul></ul></ul><ul><ul><li>Co-existence tunneling technologies available </li></ul></ul><ul><ul><ul><li>6to4, ISATAP, Teredo </li></ul></ul></ul><ul><ul><li>Devices – Nokia Communicator, Ericsson Bluetooth phone </li></ul></ul><ul><li>Independent software vendors </li></ul><ul><ul><li>OS support available – Microsoft, Apple, Novell, SCO, Sun, Linux, BSD, etc. </li></ul></ul><ul><ul><li>Applications – Emerging </li></ul></ul><ul><li>Network service providers </li></ul><ul><ul><li>Commercial services in Europe, Asia - NTT </li></ul></ul><ul><ul><li>Trails in Asia – Japan Telecom, KDDI, JENS, Chita, AboveNet Japan, KPN; Australia – Telstra; U.S. – Verio </li></ul></ul><ul><ul><li>R&D underway for mobile carriers worldwide </li></ul></ul>
  8. 8. Moving From v4 to v6 Connectivity is available in Asia & Europe, limited in U.S. HW support available HW & SW support available IPv6-enabled applications are limited Today’s Availability ~0 IPv6-enabled applications, hosted Teredo service Independently deploy IPv6-based consumer and knowledge worker applications Option A $$$$ IPv6 connectivity Native IPv6 Option D $$$ Infrastructure upgrade Dual-stack Option C $$ ISATAP, 6to4 Deploy transition technologies into existing v4 infrastructure Option B Relative Cost Deployment Requirement Deployment Method Description
  9. 9. IPV6 Transition Technology Overview <ul><li>6to4 tunneling </li></ul><ul><ul><li>Provides IPv6 connectivity over the public IPv4 Internet </li></ul></ul><ul><ul><li>IPv6 traffic tunneled within IPv4 </li></ul></ul><ul><ul><li>6to4 addresses can be provided by routers, home gateway devices, Windows ICS or by the host itself </li></ul></ul><ul><li>ISATAP </li></ul><ul><ul><li>Provides IPv6 connectivity over IPv4 intranets </li></ul></ul><ul><ul><li>IPv6 tunneled within IPv4 </li></ul></ul><ul><ul><li>Provides corporations with a central location to provision IPv6 addresses to IPv4 hosts </li></ul></ul><ul><ul><li>Can serve as a router between native IPv6 hosts and ISATAP tunneled IPv6 users </li></ul></ul><ul><li>Teredo </li></ul><ul><ul><li>Provides IPv6 connectivity when clients are behind a IPv4 NAT </li></ul></ul><ul><ul><li>IPv6 tunneled over UDP/IPv4 </li></ul></ul><ul><ul><li>Runs only in unmanaged networks today </li></ul></ul><ul><ul><li>Uses servers to facilitate the creation of global IPv6 addresses for Teredo clients </li></ul></ul>
  10. 10. v4/v6 Co-Existence Strategy 6to4 ISATAP Router 6to4 Router 6to4 Router 6to4 Relay ISATAP Teredo Relay 6to4 Relay 6to4 IDG v4 Internet NAT v6 v6 v4+ISATAP Enterprise 6to4 v6 Enterprise v6 v6 NAT Native v6 Enterprise v6 Teredo v4 Enterprise V4-v6 Dual Stack Enterprise v6 Internet
  11. 11. Deploying IPv6 With Windows <ul><li>Multiple techniques are required to cover all deployment scenarios </li></ul><ul><li>Microsoft is shipping automatic transition technologies today </li></ul><ul><ul><li>Windows 2003 Server with ISATAP </li></ul></ul><ul><ul><ul><li>Provides centralized deployment of IPv6 connectivity throughout corporate network </li></ul></ul></ul><ul><ul><li>Windows XP SP1 </li></ul></ul><ul><ul><ul><li>Native, ISATAP and 6to4 connectivity </li></ul></ul></ul><ul><ul><ul><li>6to4 and Teredo for unmanaged networks </li></ul></ul></ul><ul><li>Simple installation and configuration to enable basic deployment </li></ul><ul><li>Microsoft is working with network equipment providers to support these technologies in their hardware </li></ul>
  12. 12. Microsoft IPv6 Status <ul><li>Operating system support </li></ul><ul><ul><li>Windows ® XP SP1 and Windows Server 2003 </li></ul></ul><ul><ul><li>Windows CE .NET, Pocket PC (2003), Windows Embedded SP1 </li></ul></ul><ul><ul><li>Windows XP Advanced Networking Pack – IPv6 NAT traversal (Teredo), IPv6 host firewall </li></ul></ul><ul><li>Developer support </li></ul><ul><ul><li>Peer-to-peer SDK </li></ul></ul><ul><ul><li>Winsock, HTTP, RPC, DPlay </li></ul></ul><ul><ul><li>Visual Studio ® & .Net Framework, DCOM </li></ul></ul><ul><ul><li>IPv6 application porting tools and guidelines </li></ul></ul><ul><li>Applications support </li></ul><ul><ul><li>IIS 6.0, IE 6.0, Windows Media Server & Client, File Sharing (Windows 2003), DNS Server (client on Windows 2003) </li></ul></ul><ul><ul><li>MSN Messenger file sharing </li></ul></ul><ul><ul><li>3 Degrees www.threedegrees.com </li></ul></ul><ul><ul><ul><li>Built on P2P SDK and requires IPv6 connectivity </li></ul></ul></ul>
  13. 13. Microsoft IPv6 Deployment <ul><li>Native v6 indicated by circles </li></ul><ul><ul><li>Also in Cambridge, U.K. </li></ul></ul><ul><li>ISATAP available in all buildings and all locations </li></ul><ul><ul><li>Native and ISATAP can communicate via ISATAP routers </li></ul></ul><ul><li>Microsoft publicly hosts Teredo servers on the Internet </li></ul>
  14. 14. Microsoft IPv6 Roadmap Scenarios Deployment methods Scenarios Deployment methods Future Next Now <ul><li>Developers: </li></ul><ul><ul><li>Peer to peer and all core infrastructure </li></ul></ul><ul><li>Enterprise connectivity </li></ul><ul><ul><li>Anywhere access </li></ul></ul><ul><ul><li>Remote management </li></ul></ul><ul><ul><li>Mobility </li></ul></ul><ul><li>Developers: </li></ul><ul><ul><li>Peer to peer collaborative applications for knowledge workers </li></ul></ul><ul><li>Developers: </li></ul><ul><ul><li>Peer to peer applications for consumers </li></ul></ul><ul><li>Centralized transition : </li></ul><ul><ul><li>ISATAP/Teredo server </li></ul></ul><ul><li>Native adoption: </li></ul><ul><ul><li>Dual stack </li></ul></ul><ul><ul><li>6to4 </li></ul></ul><ul><li>IPv6 Home gateways </li></ul><ul><ul><li>6to4/Teredo/Native </li></ul></ul><ul><li>Centralized transition: </li></ul><ul><ul><li>ISATAP/Teredo server </li></ul></ul><ul><li>Client based transition, now +: </li></ul><ul><ul><li>Firewall Traversal </li></ul></ul><ul><ul><li>Full IPSec </li></ul></ul><ul><li>IPv6 Home gateways </li></ul><ul><ul><li>6to4/Teredo relay </li></ul></ul><ul><li>Client based transition: </li></ul><ul><ul><li>6to4, Teredo NAT Traversal </li></ul></ul><ul><li>Public Teredo service </li></ul>
  15. 15. IPv6 Partnerships <ul><li>Microsoft staff </li></ul><ul><ul><li>Communicate the IPv6 message </li></ul></ul><ul><ul><li>Identify qualified customers </li></ul></ul><ul><ul><li>Help IPv6 team to connect and engage dialogue with customers </li></ul></ul><ul><ul><li>Provide feedback to the IPv6 team </li></ul></ul><ul><ul><li>Become a Microsoft IPv6 expert </li></ul></ul><ul><li>Developers </li></ul><ul><ul><li>Investigate peer-to-peer and IPv6 as components for new development </li></ul></ul><ul><ul><li>Develop IP-agnostic applications using new APIs </li></ul></ul><ul><ul><li>Augment existing solutions with new capabilities </li></ul></ul><ul><li>Enterprises </li></ul><ul><ul><li>Deploy IPSec </li></ul></ul><ul><ul><li>Deploy transition technologies </li></ul></ul><ul><ul><li>Use IPv6-enabled equipment and applications for new deployments </li></ul></ul><ul><ul><li>Reduce/Remove NATs </li></ul></ul><ul><ul><li>Do not blindly block IPv6 traffic </li></ul></ul><ul><li>Service providers, carriers </li></ul><ul><ul><li>Deploy transition technologies </li></ul></ul><ul><ul><li>Reduce/Remove NATs </li></ul></ul><ul><ul><li>Use IPv6-enabled equipment for new deployments </li></ul></ul><ul><ul><li>Conduct native v6 trials and provide native v6 connectivity </li></ul></ul><ul><ul><li>Require IPv6 capability for new RFPs </li></ul></ul>
  16. 16. Key Message: Don’t Wait <ul><li>Native IPv6 environment is NOT a prerequisite for achieving v6 benefits </li></ul><ul><li>Application developers can use IPv6 NOW </li></ul><ul><li>IPv4 will exist for a long time </li></ul><ul><li>Tunneling technologies enable IPv4 and IPv6 to co-exist </li></ul>
  17. 17. IPv6 Developer Support <ul><li>“ IPv6 Guide for Windows Sockets Applications” </li></ul><ul><li>http:// msdn.microsoft.com/library/default.asp?url =/library/en-us/winsock/winsock/ipv6_guide_for_windows_sockets_applications_2.asp </li></ul><ul><ul><li>Topics covered </li></ul></ul><ul><ul><ul><li>Changing data structures </li></ul></ul></ul><ul><ul><ul><li>Function calls </li></ul></ul></ul><ul><ul><ul><li>Use of hard-coded IPv4 addresses </li></ul></ul></ul><ul><ul><ul><li>User interface issues </li></ul></ul></ul><ul><ul><ul><li>Underlying protocols </li></ul></ul></ul><ul><li>Utility for IPv6-compliance </li></ul><ul><ul><li>Checkv4 </li></ul></ul>
  18. 18. Tools and Resources <ul><li>Tools: </li></ul><ul><ul><li>All standard command-line utilities support IPv6 (Ping, TraceRT etc.) </li></ul></ul><ul><ul><li>NetSh – all IPv6, ISATAP configuration options </li></ul></ul><ul><ul><li>SMS Network Monitor </li></ul></ul><ul><li>Resources: </li></ul><ul><ul><li>“ Understanding IPv6” book by Joseph Davies </li></ul></ul><ul><ul><ul><li>MSPress; ISBN 0-7356-1245-5 </li></ul></ul></ul><ul><ul><li>Microsoft.com IPv6 site </li></ul></ul><ul><ul><ul><li>http://www.microsoft.com/ipv6 </li></ul></ul></ul><ul><ul><li>IPv6/IPv4 coexistence and migration whitepaper </li></ul></ul><ul><ul><ul><li>http://www.microsoft.com/windowsserver2003/technologies/ipv6/ipv6coexist.mspx </li></ul></ul></ul>
  19. 19. More Information on IPv6 <ul><li>Send feedback on Microsoft IPv6 implementations: </li></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><li>Key IETF standards information: </li></ul><ul><ul><li>Microsoft supports (by RFC) </li></ul></ul><ul><ul><ul><li>http://www.microsoft.com/windowsserver2003/technologies/ipv6/ip v6rfc.mspx </li></ul></ul></ul><ul><ul><li>IPv6 specification (ipngwg) </li></ul></ul><ul><ul><ul><li>RFC 2460, 2463. 2373 - IPv6 protocol ftp://ftp.isi.edu/in-notes/rfc2460.txt & 2463.txt & 2373.txt, </li></ul></ul></ul><ul><ul><li>IPv6 transition tools (ngtrans/v6ops) </li></ul></ul><ul><ul><ul><li>RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds (6to4) ftp://ftp.isi.edu/in-notes/rfc3056.txt </li></ul></ul></ul><ul><ul><ul><li>Internet Draft - Tunneling IPv6 over UDP through NATs (Teredo) http://www.ietf.org/internet-drafts/draft-huitema-v6ops-teredo-00.txt </li></ul></ul></ul><ul><ul><ul><li>Internet Draft - Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) ftp://ftp.isi.edu/internet-drafts/draft-ietf-ngtrans-isatap-05.txt </li></ul></ul></ul>