IPv6 - Introduction Michael Dirska Hasso-Plattner-Institut Potsdam

04/2004 -md-2 Why a new protocol version? Beginning of 1990s: –Help! - IPv4 address space is running out –There are too few Class-B-Networks left –Routing Tables are growing immensely

04/2004 -md-3 IPv4 address structure (old) 32 Bit Written as 4 Bytes, decimal, "." inbetween Netmasks: number of relevant bits 0Class A/812.x.x.x 10Class B/ x.x 110Class C/ x 1110Class DMulticast 1111Class E(nicht belegt)

04/2004 -md-4 IPv4 address structure (new) Classless Inter-Domain Routing (CIDR) RFC 1519 September 1993RFC 1519 ( 0Unicast-Adressen /8 bis /24-Netze 10" 110" 1110Multicast 1111(nicht belegt)

04/2004 -md-5 Internet-Routing Uni Potsdam /16 HU Berlin /16 DFN G-WiN AS680 WIDE Project /21 AS2500

04/2004 -md-6 IP: Next Generation (IPng) Dec. 1993: RFC 1550 Request for White PapersRFC 1550 lots of answers August 1994, examples: – RFC 1669 " Market Viability as a IPng Criteria "RFC 1669 – RFC 1671 " IPng White Paper on Transition "RFC 1671 – RFC 1687 " A Large Corporate User's View of IPng "RFC 1687

04/2004 -md-7 IPng renamed to IPv6 Jan. 1995: RFC 1752 "The Recommendation for the IP Next Generation Protocol"RFC 1752 Dec. 1995: RFC 1883 "Internet Protocol, Version 6 (IPv6) Specification"RFC 1883

04/2004 -md-8 Decision in favour of a new address space IPv6 has 128-Bit addresses (millions of addresses per square meter of the earths surface) the new version solves old problems (fragmentation) and keeps the IP-header small elegant solution – technically! but: how do you switch from IPv4 to IPv6? Do we switch at all? Can both protocols co-exist?

04/2004 -md-9 Advantages of a new address space We can learn from the mistakes: –better address allocation (smaller routing tables) –enough global routable addresses even for the smallest imaginable devices

04/2004 -md-10 Disadvantages of a new address space all connections between Autonomous Systems (AS) must be re-negotiated lots of work to setup a second infrastructure there is no killer application in sight – so why do we want it? see: D.Bernstein "IPv6-mess"IPv6-mess

04/2004 -md-11 currentcurrent IPv6 specifications RFC 2460 "Internet Protocol, Version 6 (IPv6) Specification"RFC 2460 RFC 2461 "Neighbor Discovery for IP Version 6 (IPv6)"RFC 2461 RFC 2462 "IPv6 Stateless Address Autoconfiguration"RFC 2462 RFC 2463 "Internet Control Message Protocol (ICMPv6)"RFC 2463

04/2004 -md-12 IPv4 header |Version| IHL |Type of Service| Total Length | | Identification |Flags| Fragment Offset | | Time to Live | Protocol | Header Checksum | | Source Address | | Destination Address | | Options | Padding | from RFC 791RFC 791

04/2004 -md-13 IPv6 header |Version| Traffic Class | Flow Label | | Payload Length | Next Header | Hop Limit | | | + + | | + Source Address + | | + + | | | | + + | | + Destination Address + | | + + | | from RFC 2460RFC 2460

04/2004 -md-14 IPv6 Adress-Struktur 128 Bit written as 8*16 Bit, hexadecimal : inbetween 2001:0DB8:0010:0000:0000:0000:0000: :0DB8:10::1 FF02::1 FE80:: = FE80::C0A8:6F :DB8::/32 ::1 ::FFFF:

04/2004 -md-15 IPv6 address structure Allocation Prefix Fraction of (binary) Address Space Unassigned (see Note 1 below) /256 Unassigned /256 Reserved for NSAP Allocation /128 [RFC1888] Unassigned /64 Unassigned /32 Unassigned /16 Global Unicast 001 1/8 [RFC2374] Unassigned 010 1/8 Unassigned 011 1/8 Unassigned 100 1/8 Unassigned 101 1/8 Unassigned 110 1/8 Unassigned /16 Unassigned /32 Unassigned /64 Unassigned /128 Unassigned /512 Link-Local Unicast Addresses /1024 Site-Local Unicast Addresses /1024 Multicast Addresses /256 aus RFC 3513RFC 3513

04/2004 -md-16 global IPv6 adresses IANARIRRIRLIRLIRCustomer Interface ID bit for local configuration (auto-configuration)

04/2004 -md-17 weitere IPv6-Adresstypen FE80::/64 0 Interface ID Link Local

04/2004 -md-18 Interface Identifier |0 1|1 3|3 4| |0 5|6 1|2 7| |cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm| aus RFC2373RFC2373 |0 1|1 3|3 4|4 6| |0 5|6 1|2 7|8 3| |cccccc1gcccccccc|cccccccc | mmmmmmmm|mmmmmmmmmmmmmmmm| FFFE XOR 0x0200 IEEEIEEE bit MAC

04/2004 -md-19 IPv6 network node link node host router Interface FE80::/64

04/2004 -md-20 Stateless Address Autoconfiguration (RFC2462)RFC2462 is always used for link-local addresses can be used to configure global adresses Duplicate Address Detection should be performed on the link

04/2004 -md-21 Neighbor Discovery (RFC2641)RFC2641 Duplicate Address Detection Router Discovery Address Autoconfiguration Next-hop Determination Address Resolution Neighbor Unreachability Detection Redirect

04/2004 -md-22 Neighbor Discovery five message types (in ICMPv6) –Router Discovery –Router Solicitation –Neighbor Discovery –Neighbor Solicitation –Redirect Why ICMPv6? You can use AH...

04/2004 -md-23 transition to IPv6 t199620?? IPv4 IPv ? 2030 ? Es wird lange Zeit gleichzeitige IPv4- und IPv6-Konnektivität geben müssen.

04/2004 -md-24 IPv4 Netzwerk node link node host router IPv4 Internet

04/2004 -md-25 dual stack node link node host IPv4 router IPv4 Internet node IPv6 router node host IPv6 Internet

04/2004 -md-26 configured tunnel node link node host IPv4 router IPv4 Internet node IPv6 router node host IPv6 Internet tunnel broker node IPv6-over-IPv4 tunnel

04/2004 -md-27 Ethernet adapter Local Area Connection: Connection-specific DNS Suffix. : IP Address : Subnet Mask : IP Address : fe80::208:2ff:fe5e:7afd%7 Default Gateway : Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix. : IP Address : fe80::5445:5245:444f%8 Default Gateway : Tunnel adapter 6to4 Tunneling Pseudo-Interface: Connection-specific DNS Suffix. : IP Address : 2002:8d59:e091::8d59:e091 Default Gateway : 2002:c058:6301::c058: :836b:213c::836b:213c Tunnel adapter Automatic Tunneling Pseudo-Interface: Connection-specific DNS Suffix. : IP Address : fe80::5efe: %2 Default Gateway : Windows XP