Fundamentals of Ipv6 “A Webinar to Help You Prepare for the CBNE™ Certification”

2/20/2013

IP Networking Part 4‐ Fundamentals of IPv6 “A webinar to help you prepare for the CBNE™ Certification”

Wayne M. Pecena, CPBE, CBNE Texas A&M IIfnformat ion TThechno logy Educational Broadcast Services

IP Networking Part 4‐ Fundamentals of IPv6 “A webinar to help you prepare for the CBNE™ Certification” Advertised Presentation Scope:

This webinar builds upon the brief introduction to IPv6 terminology presented in the third webinar of the series held in January 2013. Just as IPv4 addressing can be challenggging when mana ggging limited IP address s pace, IPv6 brin gs new challen ges when working with enormous IP address space. A new mindset is required to effectively understand and implement IPv6 in your network. New IPv6 features and capabilities also bring challenges to the broadcast network engineer.

My Goals & Deliverables for This Afternoon:

‐ Provide an Awareness of IPv6 Terminology ‐ Provide an Understanding of IPv6 Technology Fundamentals & Implementation ‐ Provide a Foundation for SBE CBNT & CBNE Certification Exams ‐ Provide Reference Material & Resources to Obtain Further Knowledge

1 2/20/2013

Agenda

• Introduction – IP Address Status – Why IPv6? • IPv6 Fundamentals – IPv6 Address Space – Address Format & Notation – Understanding IP Address Types – IPv6 Address Allocation – IPv6 Enhancements • When to Implement IPv6 • How to Implement IPv6 • Takeaway Summary –Q&A • Reference Sources

A Poll ?:

My Interest in IPv6 is:

□ Just Want to Keep Up Wit h IP NNkietworking TThechno logy □ Want to Understand If I Need to Implement □ Plan to Implement IPv6 □ Have Already Implemented IPv6 and Looking for More Knowledge

2 2/20/2013

IPv4 Address Depletion Source: http://www.potaroo.net/tools/ipv4/plotvar.png

• As of February 2011 ALL ICANN IPv4 Address Space Assigned! • Regional Registries Now Have Their Last Allocation! • APNIC & RIPE NCC IPv4 Space Now Deplldeted

IPv6 Technology Fundamentals IETF –Internet Engineering Task Force

• Request for Comments –RFC’s – The “Standards Bible” of the Internet – Used to Explain All Aspects of IP Networking – Nomenclature “RFC xxxx” • Requirement Levels: – Required – Recommended – Elective – Limited Use – Not Recommended www.rfc‐editor.org/rfc.html

3 2/20/2013

Why IPv6? RFC 2460 • IPv6 Provides Expanded IP Address Space • But, IPv6 is More Than Expanddded Address Space: – An Opportunity to Re‐Engineer IPv4 • Host Auto‐Configuration Capability • Regain TCP End‐End Connectivity Model – Eliminates Need for Network Address Translation (NAT) • Eliminates the Broadcast Address • Improved Support: – Multicasting – Security Built In – Mobile Application Roaming Support

Decimal (10) Hexadecimal (16) Binary (2) Hexadecimal Review 0 0 0000 1 1 0001 RFC 5952 recommends use of 2 2 0010 lower case hexadecimal characters 3 3 0011 But, case insensitive! 4 4 0100 5 5 0101 6 6 0110 7 7 0111 8 8 1000 9 9 1001 10 a 1010 11 b 1011 12 c 1100 13 d 1101 14 e 1110 15 f 1111 8

4 2/20/2013

IPv6 Address Space IETF ‐ RFC 2460

IPv6 PPidrovides EEddxpanded IP Address Space

128 bit address 2128 =

340,282,366,920,938,463,463,374,607,431,768,211,456

(three hundred forty UNDECILLION addresses) 3.4 x 1038

How Big is the IPv6 Address Space? 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses

• 50 octillion addresses per person • 3.7 x 1021 addresses per square inch of earth

Owen DeLong – Hurricane Electric 10

5 2/20/2013

IPv6 Address – Similar to IPv4, But DIFFERENT

• 128 bit vs 32 bit Address Length • Hexadecimal vs Decimal Address Characters • Colon vs Period Address Section Separators • Hextet vs Octet Address Sections

192.168.100.255 vs 2001:0:0:0:db8:8000:200c:417a

IPv4 IPv6 Address Length (bits) 32 128 Address Characters Decimal Hexadecimal Address Section Separators . : (or maybe ::) Address Section Nomenclature Octet Hextet (chunk, Quartet, or quad)

The IPv6 Address

128‐Bit Address Binary Format: 001001100000011110111000000000001111101010100000000000110010000110010101100110001000011110111100010010000010100011110001 Subdivide Into Eight (8) 16‐bit Groups: 0010011000000111 1011100000000000 0000111110101010 0000000000000011 0010000110010101 1001100010000111 1011110001001000 0010100011110001

Convert Each 16‐bit Binary Group to Hexadecimal: (separate Hextet(s) with a colon) 2607:bfb800:0faa:0003:2195:9887: bc48:28f 1

6 2/20/2013

Representing an IPv6 Address RFC 4291

X : X : X : X : X : X : X : X Each IPv6 Address:

0000 128 bits in length ‐ Written as 32 to hexadecimal digits FFFF Expressed as (8) 16 bit sections separated by a colon

Each 16 bit section or “Hextet” 0000 0000 0000 0000 represented by 4 hexadecimal to to to to digits 1111 1111 1111 1111 (also called Chunks, Quads, Quartets)

Preferred Address Format

0000:0000:0000:0000: 0000:0000:0000:0000

0000:0000:0000:0000: 0000:0000:0000:0001

2001:0000:0000:0000: 0000:0000:0000:0001

2001:0ccc:bbbb:0001: 0000:0000:0000:1234

7 2/20/2013

IPv6 Address Summarization Rules 3 ‐ Rules of Address Notation Reduction

• Eliminate Leading Zero’s Eliminate Leading Zero’s in Any Hextet: 0001 becomes 1 00f0 becomes f0

• Eliminate Hextet’s With All Zero’s Double Colon Represents Continuous Hextet’s of All Zeros: 0000:0000:0000:0001 becomes ::0001 Apply Rule #1 yields ::1

• Only One (1) Double Colon Allowed in an Address

Compressed Address Format Address Summarization

Preferred Format: Compressed Format:

0000:0000:0000:0000: 0000:0000:0000:0000 ::

0000:0000:0000:0000: 0000:0000:0000:0001 ::1

2001:0000:0000:0000: 0000:0000:0000:0001 2001::1

2001:0ccc:bbbb:0001: 0000:0000:0000:0234 2001:0ccc:bbbb:1::234

8 2/20/2013

A Quiz ?:

Address f123:0000:0000:abcd:00fe:0000:0000:9876

Can Be Condensed To:

F123::abcd:fe::9876

□ TRUE □ FALSE

Address Mask

• An IPv6 Address is Divided Into Network Portion & Host Portion (just like IPv4) • Mask Specifies the Division Betwwen Network & Host Portion of Address –Determines the Block Size To‐Be‐Routed • CIDR Notation ALWAYS USED –No Explicit Mask

128 bits

Network Portion Host Portion

Provider Site

IANA Allocated Global Routing SLA 0x001 Interface ID Prefix (Subnet ID)

3 bits 45 bits 16 bits 64 bits

EXAMPLE: Global Unicast Address Format (Aggregatable & Routable)

9 2/20/2013

IPv6 Address Notation

Classless Inter‐Domain Routing “CIDR” Notation Always Utilized

CIDR Notation Represents An IP Address & Mask in a Shorthand Form:

IPv4: 165.95.240.136/n

IPv6: 2607:b800:faa::/n

Where n represents the number of bits in the subnet mask

IPv6 Address Types

• Unicast –One Destination Single Interface – Global – Link & Site Local – Loopback • Anycast – Allows Multiple Devices to Share the Same Address – Router Selects the Closest Host • Typically Used for Host Replication • Multicast –One Source to Many “Subscribers” – NOTE –No Broadcast Address in IPv6

10 2/20/2013

Layered Address Access

Site Global Link – Local Local 2xxx: or 3xxx: FE8x: FECx:

IPv6 Addresses:

Link – Local Address – Used on a Single Subnet or Link – Never Routed to Another Subnet – Every IPv6 Host Interface Has A Link-local Address That is Assigned or Auto-Configured

Site Local Address – Routed Within the Organization – Never Routed to the Public Internet

Global Address – Routed to the Public Internet 21

The Global Unicast IPv6 Address in Detail Applying the “3 –1 –4” Rule

Structure of an IPv6 Global Unicast Address

/48 /64

Global Routing Prefix Interface ID Subnet ID (assigned by IANA/provider) (unique interface ID) /128 48 bits 48 bits 64 16 bits 16

16 bits 16 bits16 bits 16 bits 16 bits 16 bits 16 bits 16 bits

3 4

1 The “3 – 1 - 4” Rule Makes the IPv6 Address Easier to Decypher

11 2/20/2013

IPv6 Representation in a URL

• IPv6 Address in a URL: In IPv4 : https://192 .168 .1 .1 :8080

In IPv6: Address 2001::0DB8:8:200C:417A Entered URL within [Brackets] as: https://[2001::0DB8:8:200C:417A]:8080

IPv6 Enhancements Re‐Engineering Beyond Increased Address Space

• IP Header Format Simplification

• Improved Support for Extensions and Options

• Improved Flow Labeling Capability

• Improved Authentication and Privacy Capabilities

• Host Auto‐Configuration

• Mobility Incorporated

12 2/20/2013

The IPv6 Header

The “Next Header” UDP TCP ICMP Or An Extension Header: Hop‐Hop Options Destination Options RtiRouting HdHeader Fragment Header Authentication Header ESP Header

Host Auto‐Configuration • Assigning the Link‐Local Interface ID: – Stateful generally configured via DHCPv6 – Crypto RFC 3972 Secure Unique Interface ID – Manual – Auto‐Configuration (RFC 4291) : • No Additional Network Services Support Required • Privacy Format Derived from RNG • Modified IEEE EUI‐64 MAC Address Derived

13 2/20/2013

Auto ‐ Configuration Interface ID Derived from MAC Address

Mobility Incorporated

• Provides Roaming Service Without Interrupting Connectivity – Ability to Move Between Networks – Maintains Home IP Address Regardless of Location – Establishes Care‐Of IP Address When In a “Foreign” Network • Similar in Concept to IPv4 Mobile IP

14 2/20/2013

IPv6 Implementation “Speed Bumps”?

– The “FUD” Principle – “Does Not Apply to Me” • I Have Adequate IP Address Space Now • I Do Not Anticipate Network Growth • I Only Care About My Internal Network – No IPv4 to IPv6 Interoperability – Another IT Industry “Crying Wolf” Event – No Demand for IPv6 from My Users – Low Priority –No “ROI” Seen

A Poll ?:

I Consider My Organization to Be an Internet Content Provider:

□ Yes □ No □ Not Sure □ Expect to Be In The Future

15 2/20/2013

Viewing the “Broadcasters”

Network IPV6 Only Audience Is Growing

“Content Consumer”

Your Network IPV6 As A Only “Content Provider”

I Am Ready to Implement IPv6 “What’s Next?” • You Gotta Have a Plan! • Evaluate Network – Core – DMZ – Internal – External Provider(s) • Inventory & Evaluate Applications • Inventory & Evaluate Server Op Systems – Focus on Outward Facing Services First – Then Address Internal Networks • Establish Organization Wide Address Plan • Training & Study • Implement a Pilot!

16 2/20/2013

IPv6 Implementation “Overcoming the IPv4 Mindset”

• Address Plan – “May Be the Most Difficult Aspect” – MtMust Overcome IPv4 Address CtiConservation RflReflex – No More “VLSM” – Address Assignment by Subnet Rather Than Host – IPv6 Addresses Are Assigned to Interfaces (Hosts are likely to have multiple IPv6 addresses) – Stick With /64 Subnet Size – Assign to Simplify Network Management and Configuration

ARIN IPv6 Address Allocation Policies

• End‐User / Enterprise Network – Qualify by Meeting IPv4 Qualifications – /48 Minimum Allocated • 65,536 /64 subbtnets • Qualify for Larger Blocks by Justification of Proposed Use – Allocation Guideline –Large Sites: /48 – Allocation Guideline –Small Sites: /56

• Home End‐User Network – /64 Minimum Allocated – 18,446 ,744,0 73 ,709 ,552 ,000 hosts

IP Address Conservation Is No Longer a Concern Abandon IPv4 Allocation Mindset

17 2/20/2013

ARIN IPv6 Address Allocation Policies

• Service Provider: /32 232 /64 subnets • Large End User: /48 65,536 /64 subnets • Small End User: /56 256 /64 subnets • SOHO: /64 1 /64 subnets CIDR Notation = Number of subnet bits

A /64 IPv6 subnet = 18,446,744,073,709,552,000 hosts

IPv6 Implementation Techniques

• Native – Separate IPv4 and IPv6 Networks • Dual ‐ Stack – Simultaneous IPv4 and IPv6 • Tunnel – IPv4 Network Used as Transport for IPv6 • Translation Based – MlilMultiple Layer NAT or LSN or CGN – NAT64 – NAT44 Preference

18 2/20/2013

Implementation Options

Migration Techniques “Dual‐Stack”

Hosts Run IPv4 and IPv6 Simultaneously, But Independently

Advantages: Gradual IPv6 Host Implementation No Translation Devices –No Added Latency

19 2/20/2013

IPv4 –IPv6 “Dual –Stack”

Migration Techniques “Tunnel”

20 2/20/2013

IPv6 –IPv4 Tunnel Approach

The Typical IPv4 Based ISP Today!

21 2/20/2013

Migration Techniques “Translation”

Migration Techniques “6 to 4” Translation

22 2/20/2013

Interoperability Between IPv4 and IPv6 Hosts

Translation Adds Latency –Detrimental for Real‐Time Media Breaks Some Applications

IPv6 Device Support Today

• Desktop & Server OS: – Microsoft XP & Server 2003 (manual enable) – Microsoft Vista, 7, 8, & Server 2008/10 – MAC OS X 10.4+ (no DHCPv6 support) Default Enabled – MAC LION DHCPv6 Supported – LINUX (2.6 kernal)

• Ethernet Switches: (NOTE ‐ Layer 2 devices are not generally concerned with a Layer 3 address) Don’t Forget the Management Interface!

• Enterprise Routers: – Cisco (manual enable) – Juniper (manual enable)

Source: • Consumer Routers: Stan Barber –Academ Consulting – D‐Link Jeff Carrell –Network Conversions – Cisco –Linksys May Need Firmware Upgrade – Netgear 46

23 2/20/2013

Routing Protocols for IPv6 “Just Need the Proper Version”

• Interior Gateway Protocols – “IGP” – RIPng (RFC 2080) – OSPFv3 (RFC 5340) – IS‐IS (RFC 5308) – EIGRP for IPv6 • Exterior Gateway Protocols – “EGP” – BGP‐4

Takeaway Summary

• The Industry is IPv4 Based Today • IPv4 Demand Continues • IPv4 Availability Pool Rapidly Decreasing or Depleted • IPv6 Provides the Future for Continued Growth • “IPv6 Only” End Users Rapidly Growing • IPv6 Implementation Does Not Happen Overnight –Plan Today! • Focus Implementation Upon External Users • IPv6 is NOT Backward Compatible With IPv4, Thus Expect IPv4 and IPv6 To Be Maintained for Many Years to Come • IPv6 Address Allocation Focuses Upon Subnet Allocation, NOT Address Allocation • Don’t Loose Sight of IPv6 Is Still IP. • IPv6 Is More Than Expanded IP Address Space.

48 48

24 2/20/2013

Familiar TCP/IP Tools (Win XP Shown)

An Ipv6 Address You Can Remember

The IPv6 Loopback Address ::1 Summarized from: 0:0:0:0:0:0:0:1

Equivalent of the IPv4 Loopback Address: 127.0.0.1

25 2/20/2013

Some Final Trivia What Happened to Version 5 or IPv5 of the Internet Protocol?

“IPv5 Simp ly Does NtNot Eit!Exist!

Version 5 was intentionally skipped to avoid confusion, or at least to rectify it. The problem with version 5 relates to an experimental TCP/IP protocol called the Internet Stream Protocol, Version 2, originally defined in RFC 1190. This protocol was originally seen by some as being a peer of IP at the Internet Layer in the TCP/IP architecture and these packets were assigned IP version 5 to differentiate them from “normal” IPv4 packets. This protocol never went anywhere, but to be absolutely sure that there would be no confusion, version 5 was skipped over in favor of version 6.”

Reference Sources:

• IPv6 Reference Texts: – IPv6 Fundamentals –Rick Graziani – Understanding IPv6 –Joseph Davies – IPv6 Essentials – Silvia Hagen – Deploying IPv6 Networks –Ciprian Popoviciu – IP Address Management Principals & Practice –Timothy Rooney – Migrating to IPv6 – Marc Blanchet

• IETF ‐ RFC Documents: www.rfc‐editor.org • IP Address Block Size Chart: https://www.arin.net/knowledge/cidr.pdf • IPv4 Address Rundown Models: http://www.potaroo.net/tools/ipv4/index.html

• IPv6 Reference Websites: – International IPv6 Forum: www.ipv6forum.com – North American IPv6 Task Force: www.nav6tf.org – IPv6 Portal: www.ipv6tf.org

26 2/20/2013

Recommended References

https://www.arin.net/knowledge/cidr.pdf

27 2/20/2013

Learn More: IPv6 Enable Your Network

But, My Provider is Not IPv6 Enabled!

Then “Tunnel” to an IPv6 Provider:

http://www.tunnelbroker.net/

IPv6 Test Web Sites

http://ipv6‐test.com/

http://v6.testmyipv6.com/

www.ARIN.net

28 2/20/2013

? Questions ?

Thank You for Attending!

Wayne M. Pecena Texas A&M University w‐[email protected] 979.845.5662