IPv 6 Issues Challenges Hopefully 79 228 162

  • Slides: 23
Download presentation
IPv 6 Issues & Challenges Hopefully 79, 228, 162, 514, 264, 337, 593, 543,

IPv 6 Issues & Challenges Hopefully 79, 228, 162, 514, 264, 337, 593, 543, 950, 336 IP addresses will be enough for a while. Dale W. Carder Network Engineer UW-Madison & Wisc. Net 2009 -05 -07

Flexible Agenda • • • Defining the issues Identifying problem areas A Call to

Flexible Agenda • • • Defining the issues Identifying problem areas A Call to start strategic planning Technical Stuff Discussion

So, Why are we here? - IPv 4 address space, which is shared by

So, Why are we here? - IPv 4 address space, which is shared by the world as a whole, is running out. - When this runnout occurs, the IPv 4 address fairy won’t have any more addresses to put under our pillow - The need for the true, global, unencumbered, end-to-end connectivity we have today will continue to exist.

Why are we running out? • • Normal usage growth Global growth IPv 4

Why are we running out? • • Normal usage growth Global growth IPv 4 addressing inefficiencies New Services – Explosion of Wireless – Scientific Computing Clusters – Virtual Machines (vmware, etc)

What is this IPv 6 thing? • “Just another protocol” • (remember appletalk, decnet,

What is this IPv 6 thing? • “Just another protocol” • (remember appletalk, decnet, ipx, etc? ) • A Method to continue to give all internet endpoints a globally unique address in the future. • A way to avoid multiple layers of NAT • Not a drop-in replacement for IPv 4. In fact, it’s natively incompatible with IPv 4!

Why adoption of IPv 6 is important IPv 6 will be the only method

Why adoption of IPv 6 is important IPv 6 will be the only method left for true end-to-end connectivity • Collaboration with entities beyond North America • Unified Communications • To be competitive • • Business Continuity

What does IPv 6 look like? • IPv 4 address – – – •

What does IPv 6 look like? • IPv 4 address – – – • 32 bits “dotted quad” format 128. 104. 181. 26 IPv 6 address – 128 bits – hexadecimal format – 2607: f 388: e: 100: 217: f 2 ff: fe 0 a: bdf 6 No Native Compatibility between the two.

IPv 6 Timeline • Right now there a few people trying to reach us

IPv 6 Timeline • Right now there a few people trying to reach us via IPv 6. • At some point, there will be people who will only be able to reach us via IPv 6. • IPv 6 will probably be the only way to ensure global reachability. Modern OS’s (Vista, OS X) ready today • Wisc. Net Backbone equipment ready today •

IPv 6 Roadblocks - Comparable in scope to Y 2 k, but without a

IPv 6 Roadblocks - Comparable in scope to Y 2 k, but without a date • 3 rd Party Application Support Numerous Backend Systems Legacy Systems Staff Training Transition Issues • • • Need to make IPv 6 a Requirement on all new Software/System acquisitions.

Where are others? • • • Federal Govt requiring IPv 6 from vendors Large

Where are others? • • • Federal Govt requiring IPv 6 from vendors Large ISP’s working on deployment plans and interoperability Foreign markets may have no choice but IPv 6 US Businesses largely have heads in the sand By planning early, we have the opportunity to deploy in a sensible, organized, and costeffective manner

Need to start planning • • • Identify how long IPv 4 will last,

Need to start planning • • • Identify how long IPv 4 will last, cost of NAT Chicken / Egg Problem Recognizing the Issues Management Leadership Can we acquire IPv 6 capability cost effectively? • Think about product refresh cycles • Planning for deployment

IPv 6 @ UW-Madison n Started grass-roots effort to “figure this thing out” amoung

IPv 6 @ UW-Madison n Started grass-roots effort to “figure this thing out” amoung techies n Convinced n Created Management to prioritize two parallel efforts: – Campus-centric task force – Formal central-IT project looking at core services, some UW-System in scale

IPv 6 at UW-Madison Installed on several client networks for testing n Initially used

IPv 6 at UW-Madison Installed on several client networks for testing n Initially used IPv 6 assignment from Wisc. Net, recently got our own space n Assigned v 6 space to College of Engineering n – – all college workstations & labs are enabled Mail servers enabled Web servers this summer Using Linux as a network firewall

Let’s get Technical

Let’s get Technical

What does IPv 6 Look Like? • IPv 4 address – 32 bits –

What does IPv 6 Look Like? • IPv 4 address – 32 bits – “dotted quad” format – 128. 104. 181. 26 • IPv 6 address – 128 bits – hexadecimal format – 2607: f 388: e: 100: 217: f 2 ff: fe 0 a: bdf 6 No Native Compatibility between the two.

IPv 6 Subnet features n All Subnets are the same, fixed size, supporting a

IPv 6 Subnet features n All Subnets are the same, fixed size, supporting a nearly “unlimited” number of hosts. n Wisc. Net holds an ISP-size allocation, which could allow for 65, 000 customers with 65, 000 subnets. n Example: 2001: 4 e 0: 0143: 1001: 0217: 02 ff: fe 0 a: bdf 6 WN Cust ID Cust subnet ID Host ID

IPv 6 Host addressing • Automatic address, based on MAC address – MAC: 00:

IPv 6 Host addressing • Automatic address, based on MAC address – MAC: 00: 17: f 2: 0 a: bd: f 6 – IPv 6: 2607: f 388: e: 100: 217: f 2 ff: fe 0 a: bdf 6 • Static assigned addresses - 2607: f 388: ab: 2 ef: : 53 • “Privacy” addresses - clients change address every day • Shorthand notation 2607: f 388: ab: 2 ef: : 1 equals 2607: f 388: 00 ab: 02 ef: 0000: 0001

IPv 6 / IPv 4 coexistence • Did I mention they are incompatible? -

IPv 6 / IPv 4 coexistence • Did I mention they are incompatible? - However, you can run both at the same time. This is called “Dual Stack”. • An IPv 6 enabled host checks DNS and prefers using IPv 6 when it can > dig ricotta. doit. wisc. edu any ricotta. doit. wisc. edu. 14340 IN ricotta. doit. wisc. edu. 10341 IN AAAA 2607: f 388: e: 100: 217: f 2 ff: fe 0 a: bdf 6 A 144. 92. 67. 161

IPv 4 / IPv 6 Coexistance (cont) • The most reasonable deployment model for

IPv 4 / IPv 6 Coexistance (cont) • The most reasonable deployment model for WN customers would be to run dual stack. • Hosts will need to run v 6 to get around NAT, or talk to regions of the world without v 4. This will be critical for servers. • Hosts will need to run v 4 indefinitely to talk to “legacy” v 4 -only hosts, applications, lab equipment, etc.

DHCP & DNS in v 6 • Hosts don’t have to use DHCP, although

DHCP & DNS in v 6 • Hosts don’t have to use DHCP, although it’s still useful to get DNS server info via DHCP • DHCP can still be used for static host assignment. • Since host IPv 6 addresses are messy, DNS will become more important. • You may want to consider using dynamic dns from the dhcp server.

Discussion

Discussion

UW-Madison IPv 4 runout

UW-Madison IPv 4 runout

Problems w/ NAT long-term n The Internet’s killer-app feature is end-to-end connectivity, which NAT

Problems w/ NAT long-term n The Internet’s killer-app feature is end-to-end connectivity, which NAT breaks. n We’re heavily entrenched in connectivity, having been online “forever”. (private enterprise architecture tends to be less well connected) n No real enterprisy NAT device exists / mucho $$$ n Support headaches n Doesn’t Support Servers, Data Center