We're Going To Need A Bigger Address Space
We're Going To Need A Bigger Address Space
We're Going To Need A Bigger Address Space
Why IPv6?
Huge Address Space Address Renumbering/Hierarchy/Mobility Multicast/Anycast Security (IPsec, Source Route) Flow Labels High Performance Design Jumbograms (packets > 64 KB)
NAT
Loss of Transparency No Inbound Services Some Apps Wont Work (e.g. IPsec, WINS)
IHL
Type of Service
Vers 6
Traffic Class
Identification
Time to Live
Payload Length
Protocol
IP Options
Destination Address
IPv6 Addressing
3 F 13 TLA 8 resv 24 NLA 16 SLA 64 Interface ID
Public Topology
Site Topology
Top Level and Next Level Aggregators Interface ID typically from MAC address Special site-local and link-local addresses Special multicast and anycast addresses Special IPv4 compatible addresses
Address Autoconfigure
Start with link-local address Neighbor Discovery (ND) multicast to find prefix or DHCP server Stateful assignment via DHCPv6 Stateless assignment via a routing prefix Entire sites can renumber with new prefix Mobility via dynamic care-of address
Why so Long?
Everything has to change (end-to-end) Apps and APIs have to change Domain Name System (DNS) changes Border Gateway Protocol (BGP) changes Routing protocol changes IPv4 over xxx now needs IPv6 over xxx
IPv6 Evolution
The 6Bone, 1996
explicit tunnels (6over4 RFC2529)
IPv6 RFC2460, Dec 1998 (update to Dec 1995) Native IPv6 backbones, 1999 6to4 draft, Oct 1999 Bump In the Stack (BIS), Feb 2000
The 6Bone
PSC
SUNY - Buffalo
Chicago
6TAP
Trumpet
San Francisco
Perryman
VA Tech
ODU UVA
San Diego
CAIRN SDSC Sprint
MIT
vBNS POP
UCSD
Juniper routers Naval Research Lab stack (merged with OpenBSD) KAME stack for Unix (in FreeBSD 4.0)
http://www.kame.net/