1 / 18

Once the was IPv4 Christian Huitema Architect, Windows ® Networking Microsoft ® Corporation

Once the was IPv4 Christian Huitema Architect, Windows ® Networking Microsoft ® Corporation. Internet: the exponentials and the brick wall?. 1991: something is going to break… 1992: CIDR is adopted, works starts on IPnG. 1994: IPv6 draft is selected

andrew
Télécharger la présentation

Once the was IPv4 Christian Huitema Architect, Windows ® Networking Microsoft ® Corporation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Once the was IPv4 Christian HuitemaArchitect, Windows ® NetworkingMicrosoft ® Corporation

  2. Internet: the exponentials and the brick wall? • 1991: something is going to break… • 1992: CIDR is adopted, works starts on IPnG. • 1994: IPv6 draft is selected • 1995-1999: IPv6 is developed. Address shortage; NAT for client/server. • 2000: peer-to-peer, always-on..

  3. How will IPv6 change the world? • Global addressing: • 64+64 format: 1.8E+19 networks, units • 1E+16 networks, assuming IPv4 efficiency • 1 million networks per human • 2 networks per sq.ft of Earth (20 per m2) • Plug and play: • IP networking easier than IPX • Efficient mobility: • Simple instant-on ad-hoc networking • Mobile IP, without servers, without dogleg

  4. Problem 1: Peer-to-peerRTP audio example P1 P2 Home LAN Home LAN Internet NAT NAT • With NAT: • Need to learn the address “outside the NAT” • Provide that address to peer • Need either NAT-aware application, or application-aware NAT • May need a third party registration server to facilitate finding peers

  5. Solution 1: Peer-to-peer RTP audio example P1 P2 Home LAN Home LAN Internet Home Gateway Home Gateway • With IPv6: • Just use IPv6 address

  6. Problem 2: MultipartyConference Example P1 P2 Home LAN Home LAN Internet NAT NAT • With NAT, complex and brittle software: • 2 Addresses, inside and outside • P1 provides “inside address” to P3, “outside address” to P2 • Need to recognize inside, outside • P1 does not know outside address of P3 to inform P2 P3

  7. Solution 2: Multiparty IPv6Conference Example P1 P2 Home LAN Home LAN Internet Home Gateway Home Gateway • With IPv6: • Just use IPv6 addresses P3

  8. Problem 3: Ad-hoc networking • IPv4: media lock + 63 sec. • Try DHCP • Wait for timeout • Select AutoNet address • Conflict detect

  9. Solution 3: Ad-hoc networking • IPv6: media lock + 1 sec. • Configure using MAC • Conflict detect

  10. Problem 4: Move from “cell” to “cell” • IPv4: • Tell server, • Packets are relayed through the server P1 ‘cell’ A ‘cell’ B Relay Internet P2

  11. Solution 4: Move from “cell” to “cell” with IPv6 • IPv6: • Tell server + peer • Packets take direct path P1 ‘cell’ A ‘cell’ B Relay Internet P2

  12. If IPv6 is so great, how come it is not there yet? • Applications • Need upfront investment, stacks, etc. • Similar to Y2K, 32 bit vs. “clean address type” • Network • Need to ramp-up investment • No “push-button” transition ?

  13. Transition, with 6to4:No dependency on “core” Pure “Version 6” Internet Original “Version 4” Internet 6to4 Site 6to4 Site

  14. FP  (3bits) TLA  (13bits) IPv4 Address  (32bits) SLA ID  (16bits) Interface ID (64bits) 001 0x0002 ISP assigned Locally administered Auto configured 6to4 addresses:1 v4 address = 1 v6 network • Stateless tunnel over the IPv4 network without configuration • The IPv6 address contains the IPv4 address • Entire campus infrastructure fits behind single IPv4 address

  15. Microsoft Roadmap • March 1998 => MSR prototype for NT4. • March 2000 => Early developer release for W2K on MSDN Web. • September 2000 => Full IPv6 Winsock SDK and key application support. • Next phase: • Work on further IPv6 release • Test and port applications, test the transition tools. • Goal: IPv6 and IPv4 parity • Customer chooses! • Eventually => IPv4 becomes legacy

  16. For More Information • Microsoft IPv6 white paper • http://www.microsoft.com/technet/network/ipvers6.asp • http://www.microsoft.com/windows2000/library/howitworks/communications/networkbasics/IPv6.asp • Microsoft IPv6 Tech Preview News • http://www.microsoft.com/PressPass/press/2000/Mar00/IPv6PR.asp • Microsoft IPv6 Tech Preview Kit • http://msdn.microsoft.com/downloads/sdks/platform/tpipv6.asp

  17. Key Messages • IPv6 direct addressing of all stations enables peer-to-peer, conferencing, auto-configuration, mobility. • Transition to IPv6 akin to Y2K (upgrade all SW to 128-bit addresses) • To help industry move along this path, MSFT released a stack and an SDK for Win2000; MS will continue to iterate this based on industry feedback

More Related