We have been thinking about what we originally called "IP Next Generation" and then called "IPv6" and the requirements for a transition for about 20 years. When we started, we thought about requirements, and over time we have described methodologies and experience with those methodologies. There is ongoing work, primarily in the IETF's IPv6 Operations Working Group (). The current "received wisdom" is probably summarized in RFCs 4213 (
On the subject of transition mechanisms the basic obstacels are that v4 and v6 don't interoperate, that translation from v4 to v6 is highly problematic, that legacy equipment isn't dual-stack capable, and that as a planet we're pretty much out of v4.
* some ISP's are dual-stacking aggressively, and large chunks of their customer base are already v6-enabled.
* lagging ISP's are toying with "carrier-grade-NAT" as an delaying tactic
* some providers are going v6-only, with border NAT64+DNS64 translation of some kind to get to the legacy v4 internet. This includes several chinese ISP's and in the USA Verizon WIreless's LTE4 network. Although legacy v4 experience is between bad and mediocre in this scenario, the providers don't care, because the top destinations such as google, youtube, netflix, facebook etc. are already dual-stacked and perform well over native v6.
Note that in analogy to the HDTV transition in the US, the home user generally has to replace gear (windows XP hosts, wifi routers, broadband modems) to actually get live v6 once the ISP offers it.
In the datacenter the primary transition obstacle is lagging 3rd party application vendors; most enterprise grade network hardware, OS software, and middleware has supported dual-stack operations for a while now.
"Note that in analogy to the HDTV transition in the US, the home user generally has to replace gear (windows XP hosts, wifi routers, broadband modems) to actually get live v6 once the ISP offers it."
Yes, but... If you have bought your PC/Mac/*nix device since 2007, you have already upgraded it. The devices that a residential user will find lagging are typically the game box, residential gateway, set-top box, IP-capable TV, or mobile telephone.
Xbox 1 is IPv6-capable, although the edition that just came out has issues; better, as with many things, to wait for a service pack. The issue on XBox 1 apart from its SLAAC implementation is that the applications don't support it.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...