IPv6 Tutorial ICANN Sao Paulo December, 2006 Jordi Palet (jordi.palet@consulintel.es) - 1
Why a New IP? Only compelling reason: more addresses! – for billions of new devices, e.g., cell phones, PDAs, appliances, cars, etc. – for billions of new users, e.g., in China, India, etc. – for “always-on” access technologies, e.g., xDSL, cable, ethernet-to-the-home, etc. - 2
But Isn’t There Still Lots of IPv4 Address Space Left? • ~ Half the IPv4 space is unallocated – if size of Internet is doubling each year, does this mean only one year’s worth?! • No, because today we deny unique IPv4 addresses to most new hosts – we make them use methods like NAT, PPP, etc. to share addresses • But new types of applications and new types of access need unique addresses! - 3
Why Are NAT’s Not Adequate? • They won’t work for large numbers of “servers”, i.e., devices that are “called” by others (e.g., IP phones) • They inhibit deployment of new applications and services • They compromise the performance, robustness, security, and manageability of the Internet - 4
Incidental Benefits of Bigger Addresses • Easy address auto-configuration • Easier address management/delegation • Room for more levels of hierarchy, for route aggregation • Ability to do end-to-end IPsec (because NATs not needed) - 5
Incidental Benefits of New Deployment • Chance to eliminate some complexity, e.g., in IP header • Chance to upgrade functionality, e.g., multicast, QoS, mobility • Chance to include new enabling features, e.g., binding updates - 6
Summary of Main IPv6 Benefits • Expanded addressing capabilities • Server-less autoconfiguration (“plug-n-play”) and reconfiguration • More efficient and robust mobility mechanisms • Built-in, strong IP-layer encryption and authentication • Streamlined header format and flow identification • Improved support for options / extensions - 7
Why Was 128 Bits Chosen as the IPv6 Address Size? • Some wanted fixed-length, 64-bit addresses – easily good for 10 12 sites, 10 15 nodes, at .0001 allocation efficiency (3 orders of mag. more than IPng requirement) – minimizes growth of per-packet header overhead – efficient for software processing • Some wanted variable-length, up to 160 bits – compatible with OSI NSAP addressing plans – big enough for autoconfiguration using IEEE 802 addresses – could start with addresses shorter than 64 bits & grow later • Settled on fixed-length, 128-bit addresses – (340,282,366,920,938,463,463,374,607,431,768,211,456 in all!) - 8
What Ever Happened to IPv5? 0–3 unassigned 4 IPv4 (today’s widespread version of IP) 5 ST (Stream Protocol, not a new IP) 6 IPv6 (formerly SIP, SIPP) 7 CATNIP (formerly IPv7, TP/IX; deprecated) 8 PIP (deprecated) 9 TUBA (deprecated) 10-15 unassigned - 9
IPv6 Tutorial Header Formats - 10
RFC2460 • Internet Protocol, Version 6: Specification • Changes from IPv4 to IPv6: – Expanded Addressing Capabilities – Header Format Simplification – Improved Support for Extensions and Options – Flow Labeling Capability – Authentication and Privacy Capabilities - 11
IPv4 Header Format • 20 Bytes + Options bits: 4 8 16 20 32 Version H. Length TOS Total Length Fragment Offset Identification Flags Protocol Header Checksum Time To Live 32 bits Source Address 32 bits Destination Address Options Modified Field Deleted Field - 12
IPv6 Header Format • From 12 to 8 Fields (40 bytes) bits: 4 12 16 24 32 Version Class of Traffic Flow Label Payload Length Next Header Hop Limit 128 bits Source Address Dirección Destino 128 bits Destination Address De – Avoid checksum redundancy – Fragmentation end to end - 13
Summary of Header Changes • 40 bytes • Address increased from 32 to 128 bits • Fragmentation and options fields removed from base header • Header checksum removed • Header length is only payload (because fixed length header) • New Flow Label field • TOS -> Traffic Class • Protocol -> Next Header (extension headers) • Time To Live -> Hop Limit • Alignment changed to 64 bits - 14
Extension Headers • “Next Header” Field IPv6 Header Next Header = TCP Header DATA TCP IPv6 Header Routing Header Next Header = Next Header = TCP Header DATA Routing TCP IPv6 Header Security Header Fragmentation Next Header = Next Header = Header TCP Header DATA Security Fragmentation Next Header =TCP - 15
Extension Headers Goodies • Processed Only by Destination Node – Exception: Hop-by-Hop Options Header • No more “40 byte limit” on options (IPv4) • Extension Headers defined currently: – Hop-by-Hop Options – Routing – Fragment – Authentication (RFC 2402, next header = 51) – Encapsulating Security Payload (RFC 2406, next header = 50) – Destination Options - 16
Control Plane IPv4 vs. IPv6 ICMPv6 MLD ND ICMP IGMPv2 IPv6 IPv4 ARP Broadcast Multicast Multicast Ethernet Ethernet - 17
IPv6 Tutorial Addressing and Routing - 18
Text Representation of Addresses “Preferred” form: 1080:0:FF:0:8:800:200C:417A Compressed form: FF01:0:0:0:0:0:0:43 becomes FF01::43 IPv4-compatible: 0:0:0:0:0:0:13.1.68.3 or ::13.1.68.3 URL: http://[FF01::43]/index.html - 19
Address Types Unicast (one-to-one) – global – link-local – site-local (deprecated) – Unique Local (ULA) – IPv4-compatible Multicast (one-to-many) Anycast (one-to-nearest) Reserved - 20
Address Type Prefixes address type binary prefix IPv4-compatible 0000...0 (96 zero bits) Global unicast 001 Link-local unicast 1111 1110 10 Site-local unicast 1111 1110 11 (deprecated) ULA 1111 110x (1= Locally assigned) Multicast 1111 1111 • All other prefixes reserved (approx. 7/8ths of total) • Anycast addresses allocated from unicast prefixes - 21
Aggregatable Global Unicast Addresses (RFC2374) (Deprecated) 001 TLA NLA* SLA* Interface ID Public Site Interface Topology Topology Identifier (45 bits) (16 bits) (64 bits) • TLA = Top-Level Aggregator NLA* = Next-Level Aggregator(s) SLA* = Site-Level Aggregator(s) • TLAs may be assigned to ISPs and IX - 22
Global Unicast Addresses (RFC3587) Glob. Rout. prefix subnet ID Interface ID 001 Sub-network Interface ID Global Routing ID (64 bits) Prefix (45 bits) (16 bits) • The global routing prefix is a value assigned to a zone (site, a set of subnetworks/links) – It has been designed as an hierarchical structure from the Global Routing perspective • The subnetwork ID, identifies a subnetwork within a site – Has been designed to be an hierarchical structure from the site administrator perspective • The Interface ID is build following the EUI-64 format - 23
Global Unicast Addresses in Production Networks Glob. Rout. prefix subnet ID Interface ID 001 Sub-network Interface ID Global Routing ID (64 bits) Prefix (45 bits) (16 bits) • LIRs receive by default /32 – Production addresses today are from prefixes 2001, 2003, 2400, 2800, etc. – Can request for more if justified • /48 used only within the LIR network, with some exceptions for critical infrastructures • /48 to /128 is delegated to end users – Recommendations following RFC3177 and current policies • /48 general case, /47 if justified for bigger networks • /64 if only and only one network is required • /128 if it is sure that only and only one device is going to be connected - 24
Global Unicast Addresses for the 6Bone Until 06/06/06 ! 001 NLA* TLA pTLA SLA* interface ID 13 12 20 16 64 bits • 6Bone: experimental IPv6 network used for testing only • TLA 1FFE (hex) assigned to the 6Bone – thus, 6Bone addresses start with 3FFE: – (binary 001 + 1 1111 1111 1110) • Next 12 bits hold a “pseudo-TLA” (pTLA) – thus, each 6Bone pseudo-ISP gets a /28 prefix • Not to be used for production IPv6 service - 25
Link-Local & Site-Local Unicast Addresses Link-local addresses for use during auto- configuration and when no routers are present: 0 interface ID 1111111010 Site-local addresses for independence from changes of TLA / NLA* (deprecated !): 0 SLA* interface ID 1111111011 - 26
Unique Local IPv6 Unicast Addresses IPv6 ULA (RFC4193) • Globally unique prefix with high probability of uniqueness • Intended for local communications, usually inside a site • They are not expected to be routable on the Global Internet • They are routable inside of a more limited area such as a site • They may also be routed between a limited set of sites • Locally-Assigned Local addresses – vs Centrally-Assigned Local addresses - 27
IPv6 ULA Characteristics • Well-known prefix to allow for easy filtering at site boundaries • ISP independent and can be used for communications inside of a site without having any permanent or intermittent Internet connectivity • If accidentally leaked outside of a site via routing or DNS, there is no conflict with any other addresses • In practice, applications may treat these addresses like global scoped addresses - 28
Recommend
More recommend
