Transcript PPT template - Christian Huitema

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
1995-1999: IPv6 is developed.
Address shortage; NAT for
client/server.
2000: peer-to-peer, always-on..
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

Problem 1: Peer-to-peer
RTP audio example
P1
P2
Home LAN

NAT
Internet
NAT
Home LAN
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
Solution 1: Peer-to-peer
RTP audio example
P1
P2
Home LAN

Home
Gateway
Internet
With IPv6:

Just use IPv6 address
Home
Gateway
Home LAN
Problem 2: Multiparty
Conference Example
P1
P2
Home LAN
NAT
Internet
NAT
Home LAN
P3

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

Solution 2: Multiparty IPv6
Conference Example
P1
P2
Home LAN
P3

Home
Gateway
Internet
With IPv6:

Just use IPv6 addresses
Home
Gateway
Home LAN
Problem 3: Ad-hoc
networking

IPv4: media lock +
63 sec.
Try DHCP
 Wait for timeout
 Select AutoNet
address
 Conflict detect

Solution 3: Ad-hoc
networking

IPv6: media lock +
1 sec.
Configure using
MAC
 Conflict detect

Problem 4: Move
from “cell” to “cell”
P1

‘cell’ A
‘cell’ B
Relay


Internet
P2
IPv4:
Tell server,
Packets are
relayed through
the server
Solution 4: Move from
“cell” to “cell” with IPv6
P1

‘cell’ A
‘cell’ B
Relay


Internet
P2
IPv6:
Tell server + peer
Packets take
direct path
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
Transition, with 6to4:
No dependency on “core”
Pure “Version 6” Internet
Original “Version 4” Internet
6to4 Site
6to4 Site
6to4 addresses:
1 v4 address = 1 v6 network
FP (3bits)
TLA (13bits)
IPv4 Address (32bits)
SLA ID (16bits)
Interface ID (64bits)
001
0x0002
ISP assigned
Locally administered
Auto configured

Stateless tunnel over the IPv4 network
without configuration
The IPv6 address contains the IPv4 address
 Entire campus infrastructure fits behind single
IPv4 address

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:



Goal: IPv6 and IPv4 parity


Work on further IPv6 release
Test and port applications, test the transition
tools.
Customer chooses!
Eventually => IPv4 becomes legacy
For More Information

Microsoft IPv6 white paper



Microsoft IPv6 Tech Preview News


http://www.microsoft.com/technet/netw
ork/ipvers6.asp
http://www.microsoft.com/windows2000
/library/howitworks/communications/net
workbasics/IPv6.asp
http://www.microsoft.com/PressPass/pr
ess/2000/Mar00/IPv6PR.asp
Microsoft IPv6 Tech Preview Kit

http://msdn.microsoft.com/downloads/s
dks/platform/tpipv6.asp
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