Have you been scratching your head wondering what this IPv6 thing is all about and how it might impact you? Have you seen an IPv6 address and wondered “How in the world do I subnet that?” Have you been praying to a deity that you will get to retire before you ever have to deal with IPv6? Does your IT team have ANY experience with IPv6 at all? Face it, it’s 2013 and you and your company don't know squat about IPv6. IANA ran out of IPv4 in 2011, APNIC and RIPE effectively ran out in 2011 and 2012 respectively, and ARIN is due to run out in 2014. So, what is your IPv6 strategy?
This session starts with explaining the current status of IPv4 and IPv6. It covers the desperate measures that the industry is adopting to extend the life of IPv4 and how it will affect your business use of the Internet. Next, it provides best practices for how to deploy IPv6, the gotchas and common mistakes you and your team will make along the way, and how to fix them. Finally, it will wrap up with some resources and next steps to get your IPv6 adoption moving.
Key Takeaways:
Why you need to move to IPv6 for your Enterprise
The impact to your business of staying on IPv4 only
What to do next to get started with IPv6 in your Enterprise
Who Should Attend:
Enterprise Network Managers, Directors of IT and CTOs
Ed Horley is the author of Practical IPv6 for Windows Administrators http://tinyurl.com/Practical-IPv6 and is the co-chair of the California IPv6 Task Force.
This presentation was given on April 3, 2014 at the Las Vegas Interop show. You can download the PDF version if you were an attendee at: http://presentations.interop.com/events/las-vegas/2014/conference-presentations/download/1770
Good Stuff Happens in 1:1 Meetings: Why you need them and how to do them well
Getting Serious About IPv6: Go Big or Go Home
1. About this session
Infrastructure Track: IPv6
Title: "Getting Serious About IPv6 - Go Big or Go Home"
Audience: North America – Enterprise Network
Managers, Directors of IT and CTO's
You will learn:
1. Why you need to move to IPv6 for your Enterprise
2. Understand the impact to your business of staying on IPv4 only
3. What to do next to get started with IPv6 in your Enterprise
Don't break the Internet - get moving on IPv6.
2. Getting Serious About IPv6
By Ed Horley
Principal Solutions Architect, Groupware Technology &
Co-Chair of the California IPv6 Task Force
April 2014
3. About me
Ed Horley @ehorley (twitter)
Author of Practical IPv6 for Windows
Administrators from Apress
Co-chair of the California IPv6 Task Force
Annual MVP recipient since 2004
11. For the majority of current OS flavors
IPv6 is enabled and on by
default
IPv6 is preferred
There are IPv6 transition
technologies in Windows
There is zeroconf
capabilities in all the OS’s
using IPv6
There are mDNS or
LLMNR capabilities using
IPv6
IPv6 & IPv4 on the same
OS is called dual-stack
IPv6 configures link-local
address automatically
IPv6 will connect with link-
local
IPv6 will dynamically build
addresses
IPv6 has several address
mechanisms – does your
team know them?
12. For Windows…
IPv6 transition
technologies are on by
default
If you deployed Windows
Vista, 7, 8 or Server 2008,
2008R2, 2012 or 2012R2,
congratulations!...
…You deployed IPv6, you
just didn’t do any planning
Do you understand the
impact of turning IPv6 off?
Do you understand the
impact of turning off IPv6
transition technologies?
Is your staff educated
enough to know how to do
either?
13. Does your company have compliance
requirements?
So… how do you pass a
compliance audit when you
have a protocol running on
your network you don’t
understand?
How educated is your staff
on understanding IPv6?
Would they know it if they
saw it?
Even if you think you have
turned IPv6 off on your
equipment, how often do
you actually audit and
check to see if it is
running?
Do you perform network
captures to understand
what is or is not using
IPv6?
17. Because…
You will have purchased
the right equipment to
support IPv6 the first time
Your staff has the
knowledge to manage and
mitigate any issues with
IPv6 (avoiding downtime)
You have less concerns
around compliance
You understand how your
applications and services
work over IPv6
Deploying new OS’s with
IPv6 support are not as
difficult
19. The transition is going to be ugly, for everyone
For service providers, they
are starting to adopt and
deploy IPv6
But…
They need to extend the
life of IPv4 due to the slow
adoption of IPv6
They do this with Carrier
Grade NAT or CGN
But…
CGN breaks IPv4
uniqueness
CGN exasperates IPv4
port exhaustion issues
CGN compounds stateful
NAT issues
20. Your users will start experiencing things like:
http://isoc.org/wp/ietfjournal/?p=262
21. What problems will my company see?
First, it will be much harder
for your employees to get
public IPv4 addresses at
home (DSL or Cable)
This will cause problems
for VPN, VoIP, Video and
Collaboration depending
on how they are deployed
Second, as partners, 3rd
parties and employees
start getting IPv6 and you
stay on IPv4, their
connection will be proxied
to you
Because these sessions
are proxied, you lose the
ability to have end to end
connectivity (IPv6 ->
IPv6/v4 proxy -> IPv4)
22. This will financial impact your
business and how productive
your employees are
23. CGN is NOT a WIN, it is
expensive and kicks the can
down the road
30. “At the current rate of acceleration, we can
expect the majority of the Internet to be
IPv6-enabled around the end of 2015.”
- Own DeLong, ARIN Advisory Council
“No longer is IPv6 adoption "just around
the corner." It's here.”
- Erik Nygren, Chief Architect for Akamai
“At MCI, we have made a full commitment to
implement and deploy IPv6 during 2005.”
- Vinton Cerf, frm SVP MCI and current
Chief Internet Evangelist for Google
32. Education
You, your staff and your
partners need to
understand IPv6
This means getting
educated on IPv6
How to design, deploy,
operate and maintain a
network running IPv6…
You will also need to
understand impacts of a
dual-stack environment
You will need to have an
education plan and
resources in place for staff
This does not happen
overnight, start now!
33. Have a plan
Once your staff is
educated it is much easier
to build a plan
A plan that is tailored to
your business needs and
requirements
A plan that accounts for
what your business does
Without a plan you will fail,
especially if you deploy
IPv6 without one
Your plan should include
testing and validation of
both network and apps
You will need a lab – trust
me on this one
34. Build a core team
You will need people from
every team
Why?
Because while IPv6 at first
glance appears to be a
networking only function…
You will quickly figure out
that the application teams
need to understand it
The database team will
need to know it
The helpdesk will have to
troubleshoot it, etc.
35. Understand the business impacts
You many have critical line
of business applications
that do not work with IPv6
Or partners in parts of the
world might only have IPv6
as a protocol option
Understand what IPv6
impacts before it is a
surprise
You may have third party
software or solutions that
do not support IPv6
If the majority of your
business is on the Internet
then supporting IPv6 is
critical
Are all your teams ready?
36. I still don’t believe I will be
using IPv6 anytime soon
37. If you are FINALLY migrating
off Windows XP
What has taken you so long?!?!?