You are on page 1of 15

IPv6

Were going to need a bigger address space

Phillip Dykstra Chief Scientist WareOnEarth Communications, Inc. phil@wareonearth.com

Why IPv6?
Huge Address Space Address Renumbering/Hierarchy/Mobility Multicast/Anycast Security (IPsec, Source Route) Flow Labels High Performance Design Jumbograms (packets > 64 KB)

Why not IPv6?


Network Address Translation (NAT) Application Level Gateways (ALG) Classless InterDomain Routing (CIDR) DHCP for IPv4 IPsec for IPv4 Mobility for IPv4 Multiprotocol Label Switching (MPLS) Jumbograms? (Try > 1500 Bytes!)

Why not IPv6?


http://2002:09fe:fdfc:2a41: fe2108c9e133fe01/index.html

Whats So Bad About NAT?


Address Rewriting

Local Intranet 10.xx, 192.168.xx

NAT

Globally Routed Internet

Loss of Transparency No Inbound Services Some Apps Wont Work (e.g. IPsec, WINS)

Performance Limitations Redundancy is Hard Nesting is Hard Merger is Hard

IPv4 and IPv6


Vers 4

IHL

Type of Service

Total Length Flags Frag Offset

Vers 6

Traffic Class

Flow Label Next Hdr Hop Limit

Identification
Time to Live

Payload Length

Protocol

Header Checksum Source Address

Source Address Destination Address

IP Options

v4 Header = 20 Bytes + Options v6 Header = 40 Bytes

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

Special ATM Consideration


ATM multicast support for ND ATM doesnt have 64 bit (or less) MACs IETF is working on MARS extensions for ND and CLIPv6 Most ATMers are going LANE/MPOA

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

vBNS IPv6 Logical Network Map


Viagenie/CA*Net II
Fibertel TCI Moscow State Univ APAN/WIDE PSU Abilene Texas AP

ESnet WIDE UUNET-UK

PSC
SUNY - Buffalo

Chicago
6TAP

Trumpet

San Francisco

Perryman

VA Tech

ODU UVA

San Diego
CAIRN SDSC Sprint

MIT

vBNS POP

Leaf Site Native Tunnel

UCSD

pTLA or other network


Transit Site Exchange Point

Selected IPv6 Code


Cisco routers, IOS 12.x
but performance is still rumored to be low

Juniper routers Naval Research Lab stack (merged with OpenBSD) KAME stack for Unix (in FreeBSD 4.0)
http://www.kame.net/

Microsoft Research stack


http://www.research.microsoft.com/msripv6/

For More Information


The 6Bone
http://www.6bone.net/

The Case for IPv6


http://www.6bone.net/misc/case-for-ipv6.html

You might also like