IPv6 for UPnP Forum


Published on

1 Like
  • Be the first to comment

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

No notes for slide
  • 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: 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 for UPnP Forum

    1. 1. IPv6 Stewart Tansley Program Manager Windows Core Networking http://www.microsoft.com/ipv6
    2. 2. Agenda <ul><li>Trends – devices, apps, markets </li></ul><ul><li>Today’s Internet Problems </li></ul><ul><li>The Promise of IPv6 </li></ul><ul><li>Deploying IPv6 </li></ul><ul><li>Roadmap </li></ul><ul><li>Specific Guidelines </li></ul><ul><li>Call to Action </li></ul>
    3. 3. Trends – Computing devices <ul><li>Small form factor devices </li></ul><ul><ul><li>PDAs, Smart Phones, Web Pads </li></ul></ul><ul><li>Always On, Always connected </li></ul><ul><li>Enable new and interesting usage scenarios </li></ul>
    4. 4. Trends - Applications <ul><li>Peer-to-Peer enables compelling scenarios </li></ul><ul><ul><li>Require end to end connectivity </li></ul></ul><ul><ul><li>Blocked by Network Address Translators (NATs) </li></ul></ul><ul><li>Net attached Consumer Electronics and Gaming appliances emerging </li></ul><ul><li>Applications assuming always on connectivity, anywhere </li></ul><ul><ul><li>Voice, Video, Collaboration </li></ul></ul>4255551212
    5. 5. <ul><li>Japan : </li></ul><ul><ul><li>Government incentives to move to IPv6 </li></ul></ul><ul><ul><ul><li>8 Billion Yen Subsidization already allocated </li></ul></ul></ul><ul><ul><li>Time-limited IPv4 addresses expire in 2005, when 100% IPv6 </li></ul></ul><ul><ul><li>1000x /48 sites at 4/02 </li></ul></ul><ul><ul><li>NTT commercial deployment of IPv6 </li></ul></ul><ul><ul><li>e-Japan Priority Policy Program: “Internet users 80M by 2005. Essential to promote IPv6 to private enterprise, government bodies, organizations and personal users.” </li></ul></ul><ul><li>China : </li></ul><ul><ul><li>2150 attendees, 5/02 summit </li></ul></ul><ul><ul><li>~9M Global IPv4 Addresses (137 /16’s + 27 /24’s), 1.3B people </li></ul></ul><ul><li>US : </li></ul><ul><ul><li>Lagging industrialized world, but has 74% of all IPv4 addresses </li></ul></ul><ul><ul><li>Lag won’t last much longer as new scenarios are enabled c.f. lag in cell phones </li></ul></ul><ul><li>Europe : </li></ul><ul><ul><li>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” </li></ul></ul><ul><ul><li>“ Current reserve of addresses is expected to run out in 2005” </li></ul></ul><ul><ul><li>Government sponsorship of pilot deployments </li></ul></ul><ul><ul><li>Wants to be leading internet economic region by 2010 </li></ul></ul><ul><ul><li>Skanova– IPv6 ISP </li></ul></ul><ul><li>Korea : </li></ul><ul><ul><li>~28M Internet users, 60% population </li></ul></ul><ul><ul><li>~8M are broadband, 28% </li></ul></ul><ul><ul><li>OECD: highest penetration </li></ul></ul><ul><ul><li>Government incentives to move to IPv6 </li></ul></ul><ul><ul><li>22% APNIC IPv6 pTLAs </li></ul></ul>Regional Trends (highlights)
    6. 6. Key Problems <ul><li>Address Shortage </li></ul><ul><ul><li>Not enough IPv4 addresses available </li></ul></ul><ul><ul><li>Disproportionate allocation </li></ul></ul><ul><ul><li>Increasing number of devices and Always On experience exacerbate the problem </li></ul></ul><ul><li>Lack of Mobility </li></ul><ul><ul><li>Applications and network protocols break in mobile scenarios </li></ul></ul><ul><li>Network Security </li></ul><ul><ul><li>Always On == Always attacked! </li></ul></ul>
    7. 7. Key Problems Address Shortage Extrapolating the number of DNS registered addresses shows total exhaustion in 2009 . But the practical maximum is about 200 M addresses , in 2002-2003 .
    8. 8. Key Problems Address Shortage <ul><li>Peer to Peer applications require: </li></ul><ul><ul><li>Addressability of each end point </li></ul></ul><ul><ul><li>Unconstrained inbound and outbound traffic </li></ul></ul><ul><ul><li>Direct communication between end points using multiple concurrent protocols </li></ul></ul><ul><li>NATs are a band-aid to address shortage </li></ul><ul><ul><li>Block inbound traffic on listening ports </li></ul></ul><ul><ul><li>Constrain traffic to “understood” protocols </li></ul></ul><ul><ul><li>Create huge barrier to deployment of P2P applications </li></ul></ul>
    9. 9. Key Problems Lack of Mobility <ul><li>Existing applications and networking protocols do not work with changing IP addresses </li></ul><ul><ul><li>Applications do not “reconnect” when a new IP address appears </li></ul></ul><ul><ul><li>TCP drops session when IP address changes </li></ul></ul><ul><ul><li>IPSec hashes across IP addresses, changing address breaks the Security Association </li></ul></ul><ul><li>Mobile IPv4 solution is not deployable </li></ul><ul><ul><li>Reliance on “Foreign Agent” is not realistic </li></ul></ul><ul><ul><li>NATs and Mobile IPv4? Just say NO </li></ul></ul>
    10. 10. Key Problems Network Security <ul><li>Always On == Always attacked! </li></ul><ul><ul><li>Consumers deploying NATs and Personal Firewalls </li></ul></ul><ul><ul><li>Enterprises deploying Network Firewalls </li></ul></ul><ul><li>NATs and Network Firewalls break end-to-end semantics </li></ul><ul><ul><li>Barrier to deploying Peer to Peer applications </li></ul></ul><ul><ul><li>Barrier to deploying new protocols </li></ul></ul><ul><ul><li>Block end-to-end, authorized, tamper-proof, private communication </li></ul></ul><ul><li>No mechanisms for privacy at the network layer </li></ul><ul><ul><li>IP addresses expose information about the user </li></ul></ul><ul><li>No transparent way to restrict communication within network boundaries </li></ul>
    11. 11. The Promise of IPv6 <ul><li>Enough addresses </li></ul><ul><ul><li>128 bits, 64+64 format = 1.8E+19 networks, units </li></ul></ul><ul><ul><li>Assuming IPv4 efficiency: 1E+16 networks, or 1 million networks per human </li></ul></ul><ul><ul><li>20 networks per m 2 of Earth (2 per ft 2 ) </li></ul></ul><ul><ul><li>Removes need to stretch addresses with NATs </li></ul></ul><ul><li>True mobility </li></ul><ul><ul><li>No reliance on Foreign Agents </li></ul></ul><ul><li>Better network layer security </li></ul><ul><ul><li>IPSec delivers end-to-end security </li></ul></ul><ul><ul><li>Link/Site Local addresses allow partitioning </li></ul></ul><ul><ul><li>Anonymous addresses provide privacy </li></ul></ul>
    12. 12. IPv6 – Key advantages <ul><li>Global addressing: </li></ul><ul><ul><li>Scaling well beyond 4 trillion public endpoints </li></ul></ul><ul><ul><li>Stateless address auto-configuration </li></ul></ul><ul><li>Plug and play: </li></ul><ul><ul><li>Simple instant-on ad-hoc networking </li></ul></ul><ul><li>Efficient mobility: </li></ul><ul><ul><li>Mobile IPv6, unlike IPv4, does not need the Foreign Agent </li></ul></ul><ul><li>Secure </li></ul><ul><ul><li>IPSec is a requirement and integral part of the IP layer </li></ul></ul><ul><ul><li>Anonymous addresses ensure privacy </li></ul></ul>
    13. 13. IPv6 basics <ul><li>Address size: 128 bit </li></ul><ul><ul><li>Cf. 32 bit IPv4 – IPv6 has 10 38 addresses! </li></ul></ul><ul><li>Examples </li></ul><ul><ul><li>Look unfriendly, but auto configured! </li></ul></ul><ul><ul><li>fe80::54ff:fe55:4e01%4 (link-local) </li></ul></ul><ul><ul><li>fec0::1:2c0:4fff:fe27:e421 (site-local) </li></ul></ul><ul><ul><li>2002:ac1f:4798::ac1f:4798 (global) </li></ul></ul><ul><li>Convenient address scopes </li></ul><ul><ul><li>Link local : always present, instant-on </li></ul></ul><ul><ul><li>Site local : private site addressing </li></ul></ul><ul><ul><li>Global : true Internet addresses </li></ul></ul>
    14. 14. IPv6 Migration <ul><li>End to End Connectivity: </li></ul><ul><ul><li>6to4 : Automatic tunneling of IPv6 over IPv4 </li></ul></ul><ul><ul><ul><li>Derives IPv6 /48 network prefix from IPv4 global address </li></ul></ul></ul><ul><ul><li>Teredo : Automatic tunneling of IPv6 over UDP/IPv4 </li></ul></ul><ul><ul><ul><li>Works through NAT, may be blocked by firewalls </li></ul></ul></ul><ul><ul><li>ISATAP : Automatic tunneling of IPv6 over IPv4 </li></ul></ul><ul><ul><ul><li>For connecting IPv6 islands to IPv4 network in the enterprise </li></ul></ul></ul><ul><ul><ul><li>Enables gradual migration to IPv6 </li></ul></ul></ul><ul><li>Applications: </li></ul><ul><ul><li>Native sockets based applications need change </li></ul></ul><ul><ul><ul><li>Checkv4 tool helps identify changes </li></ul></ul></ul><ul><ul><li>Applications using high level programming paradigms are already IPv6 ready </li></ul></ul><ul><ul><ul><li>E.g. RPC, DPlay etc. </li></ul></ul></ul><ul><ul><li>.NET Framework is IPv6-ready </li></ul></ul>
    15. 15. Home – Enabling IPv6 – I <ul><li>6to4 (new NATs) </li></ul>6to4 relay router 6to4 router IPv6 host A 6to4 host C IPv6 host D IPv6 host B Home Site 1 Home Site 2 IPv4 Internet IPv6 Internet
    16. 16. Home – Enabling IPv6 – II <ul><li>Teredo (legacy NATs) </li></ul>Home A Home B Teredo relay IPv6 host D Teredo client Home IPv4-only NAT IPv6-only device ISP’s IPv4-only NAT Teredo server Teredo client + bridge Teredo client IPv6 Internet IPv4 Internet
    17. 17. Enterprise – Enabling IPv6 <ul><ul><li>6to4 gateway router for site </li></ul></ul>6to4 relay ISATAP router for site IPv4 subnets IPv6 ISATAP Nodes IPv4 Internet IPv6 Internet <ul><li>Use IPv6 ISP or 6to4 for connectivity to IPv6 internet </li></ul><ul><li>Use ISATAP while upgrading the network incrementally </li></ul>IPv6 subnets <ul><ul><li>Firewall </li></ul></ul>
    18. 18. What does it take to deploy IPv6 Applications Platform and Infrastructure Application Development Tool Support Network Infrastructure
    19. 19. What is Microsoft Doing ? <ul><li>Platform and Infrastructure </li></ul><ul><ul><li>Windows XP SP1, Windows.NET Server full deployment quality IPv6 </li></ul></ul><ul><ul><li>Windows CE.NET, Windows Embedded SP1 too </li></ul></ul><ul><li>Application Development Tools </li></ul><ul><ul><li>Support for native Winsock layer </li></ul></ul><ul><ul><li>RPC, Dplay, P2P SDK </li></ul></ul><ul><ul><li>.NET Framework and VS.NET </li></ul></ul><ul><li>Applications </li></ul><ul><ul><li>IE, IIS, File and Print, Media Server … </li></ul></ul><ul><ul><li>Working with 3 rd party ISVs </li></ul></ul><ul><li>Network Infrastructure </li></ul><ul><ul><li>IPv6 islands connected to/across IPv4 internet (6to4, Teredo) </li></ul></ul><ul><ul><li>Gradual Migration in the enterprise (ISATAP) </li></ul></ul><ul><ul><li>Working with NEPs to make the migration easier </li></ul></ul>
    20. 20. Deploying IPv6 Recommended Strategies <ul><li>Dual-stack, IPv6-only </li></ul><ul><li>In the home </li></ul><ul><ul><li>Use native IPv6 if available </li></ul></ul><ul><ul><li>Or use 6to4 if global IPv4 address </li></ul></ul><ul><ul><li>Or use IPv6 over UDP if private IPv4 address </li></ul></ul><ul><li>In the enterprise </li></ul><ul><ul><li>Use IPv6 ISP or 6to4 for external access </li></ul></ul><ul><ul><li>Use ISATAP while upgrading the network </li></ul></ul>
    21. 21. 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
    22. 22. IPv6 and Internet Gateway Devices <ul><li>One subnet per household </li></ul><ul><li>Single gateway </li></ul><ul><li>Dual-stack connectivity </li></ul><ul><li>Network security boundary at the IGD </li></ul>
    23. 23. ISP scenarios for an IPv6 IGD <ul><li>IPv4-only ISP </li></ul><ul><ul><li>ISP provides global IPv4 address through automatic (e.g. DHCP) or manual configuration </li></ul></ul><ul><ul><li>IGD uses 6to4 technology to offer a single Home LAN subnet in the 2002::/16 range </li></ul></ul><ul><li>IPv6 enabled ISP (may also offer IPv4) </li></ul><ul><ul><li>ISP supports automatic IPv6 address assignment with Router Advertisements (RA) </li></ul></ul><ul><ul><li>IGD relays RA to the Home LAN and serves as site boundary (serves as RA proxy) </li></ul></ul>
    24. 24. Device scenarios for a Home LAN <ul><li>IPv4-only device </li></ul><ul><ul><li>Does not benefit from IPv6 service, uses NAT </li></ul></ul><ul><li>IPv6/IPv4 device </li></ul><ul><ul><li>May use either protocol, depends on destination </li></ul></ul><ul><ul><li>Most network settings assigned with DHCPv4 </li></ul></ul><ul><li>IPv6-only device </li></ul><ul><ul><li>Cannot talk to IPv4-only destinations directly </li></ul></ul><ul><ul><li>Should implement mDNS and DDNS </li></ul></ul>
    25. 25. Features of an IPv6 IGD <ul><li>IPv6 Router with 6to4 and RA proxy </li></ul><ul><ul><li>6to4 for IPv4 ISPs, RA proxy for IPv6 ISPs </li></ul></ul><ul><li>DNS Proxy </li></ul><ul><ul><li>Allows name resolution for IPv6-only nodes attached to the Home LAN </li></ul></ul><ul><li>DNS name registration and enumeration </li></ul><ul><ul><li>Allows name discovery and name resolution within the home LAN </li></ul></ul>
    26. 26. Features known to be harmful <ul><li>IPv6-to-IPv4 NAT-PT </li></ul><ul><li>DNS record A<->AAAA translation in the DNS proxy </li></ul><ul><li>Reverse DNS name lookup </li></ul><ul><li>IGD implementers considering these features are encouraged to contact Microsoft IPv6 team </li></ul>
    27. 27. Call to Action <ul><li>IPv6 is here already !! </li></ul><ul><li>Enable applications to use IPv6 now ! </li></ul><ul><ul><li>Use IPv6 stack in Windows XP and programming tools in VS.NET and .NET Framework </li></ul></ul><ul><ul><li>Take advantage of IPv6 to enable new scenarios, enhanced user experience </li></ul></ul><ul><li>Start deploying IPv6 now ! </li></ul><ul><ul><li>ISP: 6to4 relays, Teredo relays & servers </li></ul></ul><ul><ul><li>Enterprises: 6to4, ISATAP </li></ul></ul><ul><li>NATs/Firewalls/Routers follow our guidelines </li></ul><ul><ul><li>Do not block IPv6, Support 6to4 </li></ul></ul><ul><li>Handheld devices – Build around IPv6 </li></ul><ul><ul><li>Secure, Mobile, Small footprint </li></ul></ul><ul><li>Join us to move the world to a simple ubiquitous network based on IPv6 </li></ul>
    28. 28. More Information on IPv6 <ul><li>Microsoft IPv6 information portal: </li></ul><ul><ul><ul><li>http://www.microsoft.com/ipv6/ </li></ul></ul></ul><ul><li>Send feedback on Microsoft IPv6 implementations: </li></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><li>Specific Guidelines for IGD implementers: </li></ul><ul><ul><ul><li>http://www.microsoft.com/hwdev/tech/network/ </li></ul></ul></ul><ul><ul><ul><li>“ IPv6 Support in Internet Gateway Devices” </li></ul></ul></ul><ul><li>Key IETF standards </li></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) ftp://ftp.isi.edu/internet-drafts/draft-ietf-ngtrans-shipworm-08.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>
    29. 29. For the interconnected lifestyle