ipv6 at 1&1

® 1&1 Internet AG 2011

IPv6

Next Generation Internet


IPv6NEXT GENERATION INTERNET

“I think there is a world market for maybe five computers.”-Thomas J. Watson, chairman of IBM, 1943

“640K ought to be enough for anybody.”-Bill Gates, Microsoft, 1981

“32 bits should be enough address space for Internet.”-Vint Cerf, Internet Pioneer, 1977



“As a result of our trip, on which we expected to get orders for five machines, we came home with orders for 18.”

-Thomas Watson Jr., chairman of IBM, 1953

“I've said some stupid things and some wrong things, but not that.”

-Bill Gates, Microsoft, 1995

“Who the hell knew how much address space we needed? I thought it was an experiment and I thought 4.3 billion [addresses] would be enough to do an experiment.”

-Vint Cerf, Internet Pioneer, 2011



The Internet is growing beyond imaginations and borders,but IPv4 limits today's Internet growth.

Every computer on the Internet needs a unique IP address.

32 bits of address space permit 232 = 4.3 billion IPv4 addresses

built to experimentally support a few dozen sites with a few hundred computers

Fixed size is good for network equipment, but limits growth.

The last 30 years of Internet Software and Protocols rely on IPv4.

This issue requires a plan.



IANA delegates IPv4 address space to regional registries.

IANA spent their last IPv4 addresses in February 2011

Regional registries assign IPv4 address space to ISPs.

Common Policy: 80% of ISP's current IPv4 has to be used.

Asia-Pacific's APNIC ran out of IPv4 in April 2011

Europe will be next in early 2012

ISPs do give IPv4 addresses to their customers.

Around 70% of assigned IPv4 is actually used on the Internet.



Internet growth needs options

Large Scale NAT, Carrier Grade NAT

expensive

limited scalability

“works” for Internet Client Access only, not for servers.

Internet services do degrade

IPv6

works for Internet Client Access and servers

tons of IP addresses, some new features, tons of possibilities

requires software changes

Is not backwards compatible with IPv4



What won't work

IPv4 ranges from 0.0.0.0 to 255.255.255.255. Use numbers larger than 255, e.g. 1234.567.891.5423

Enable IPv6 and IPv4 to talk to each other.

What probably won't work

Large Scale NAT/Carrier Grade NAT



IPv6 does have limits, too

ISPs initially receive the equivalent of 4.3 billion IPv6 /64-networks;this equals 16.7 million IPv6 /56-networks.

Every /64 networks permits 4.3 billion by 4.3 billion (=264) IPv6 addresses.A /56-network does contain 256 networks of size /64.

Once 15% of IPv6 have been spent, IANA will reconsider assignment policies.



IPv6 in 2 Minutes

Every user's network receives a minimum adress range (prefix)of 264 (=18.446.744.073.709.551.616) IPv6 addresses.

IPv6 automatically chooses a single address from that range of addresses, e.g.2001:8d8:1fe:1:21e:4fff:fef9:f540

To prevent privacy issues for client access, one may also configure and use random addresses from the given range, the ISP may change the prefix.

Changing IPv6 addresses this way does work automatically and is completely transparent to the user.

IPv6 privacy extensions are per Default enabled on any Microsoft Windows Desktop

Hiding or not permitting the user to use IPv6 privacy extensions is not an “IPv6 issue” but an issue with the internet device (iPhone, Android, Mac OS X).

Servers still do require “static” IPv6 addresses.



IPv4 and IPv6 can't talk to each other.

Users and servers need to use IPv4 and IPv6 in parallel, so they can access “old” and “new” internet without restrictions

Applications need to be changed to use IPv6

Applications (usually) do prefer IPv6 than IPv4

Some Internet Access Service Providers see IPv4-NAT as a “compatibility bridge” for accessing the IPv4-Internet.

The Internet grows about 5-15% per year.

At 10% growth using IPv6-only, an IPv4-only service will be accessible from only 91% of the “whole” internet.

IPv6-access is also important when IPv4-NAT exposes degraded quality.

So IPv6 is also required for availability



IPv6 at 1&1

1999: Lab experiments

2002: network management via IPv6

2003: (tunneled) IPv6 for dedicated servers

2005: IPv6 in office networks

2007: implementing IPv6 in our software

2009: first public services using native IPv6

2010: preparing our products for IPv6

End of 2011: first products using IPv6



Open issues with IPv6 deployment

Application Software

Personal Firewalls, “real” Firewalls

Intrusion Detection Systems

consumer-grade DSL routers/CPEs

actually using IPv6

software developers

Home and Enterprise users

transit providers

content providers

ipv6 at 1&1

Documents