CIS suggests implementing an IPv6 adopting project soon to avoid the need IPv4 IPv6 translation mechanisms. CIS is IPv6 ready.
IPv6 - It will matter to you.
Check your readiness - http://test-ipv6.com
The worlds top 3 internet sites Google, YouTube and Facebook are all already IPv6 capable using the DualStack solution.
People have made some ingenious attempts to visualise the size difference between IPv4 and IPv6.
IPv6 addresses are made up of 128bits, vs 32bits for IPv4. The address below is a typical 128bit ipv6 address grouped in 8 chunks of 16bits each. The extent of the IPv4 internet is represented in just the last 2 16bit chunks:
Once you try to imagine that 4 billion IPv4 internets still only consume the lower 4 16bit chunks the futility of continuing the comparison becomes obvious.
The number is simply unpronounceable.
CIS's Data Centre in the UK (Custodian) is DualStack IPv4 and IPv6 capable.
We have also published an example of how we've configured a Small Office / Home Office (SOHO) environment for Dual Stack.
IPv4 address space exhaustion is the most compelling reason to consider a move to IPv6. IP addresses are assigned first globally and then geographically in ever smaller sub-allocations. From the quote below, the global pool ran out in 2011. A number of regions have also run out. See the IPv4 Exhausion Counter on the right.
When there are no more IPv4 addresses left to allocate new content will only be provided to the IPv6 internet. IPv4 only consumers will be reliant on gateways to access this content.
New internet users will be allocated only IPv6 addresses, they will be able to access IPv6 content without an issue, but they will need to use tunnels or gateways to access IPv4 content.
The use of gateways and tunnels for access between IPv4 and IPv6 carries risk of performance loss through latency and congestion - public gateways/tunnels have no SLAs where as private gateway/tunnels will incurr costs.
Since the work to move to IPv6 is inevitable CIS's advice is to plan and start work on enabling IPv6 now to avoid any reliance on gateways / tunnels.
IPv6 removes the need for Network Address Translation (NAT). NAT has a firewalling side effect, which some have come to rely on.
Organisational Border Control needs to actively protect internal services once IPv6 is enabled (to make up for the loss of NATs passive protection).
This will be a non issue for any good firewalling product/design/device, but it should be an item on the project checklist.
There are 3 recognised mechanisms for IPv6 adoption :-
Dual stack implementation is the only one that will not require another non-trivial change again in the future. It results in both IPv4 and IPv6 addresses being accessible from networked devices at the same time. Once set up this will likely remain in place for next 5-15 years, until all the content on the IPv4 internet is natively available on the IPv6 internet.
The entire channel must become IPv6 enabled: providers and consumers of content and the ISP/IAP channel must all be enabled.
Everyone is a consumer and if you have a website you are a provider of content. If you operate a network at home or at work you are part of the channel.
Talk to your network provider / PC support and ask them to ensure that when you follow the link http://test-ipv6.com you see a 10/10 for readiness.
Ensure that your content is reachable over the IPv6 internet. If it isn't you will be reliant on gateways to deliver your content to IPv6 consumers. If CIS is your hosting company contact us to begin a conversation. We have one fully routed Dual stack IPv6 office we can test access from.