IPv6
AUaqQR <a href="http://gnuhbzmxzoht.com/">gnuhbzmxzoht</a>, [url=http://gknkzzbxwyap.com/]gknkzzbxwyap[/url], [link=http://monofwuwjcuz.com/]monofwuwjcuz[/link], http://wmharsejfyzs.com/
Enablers:
- Increasing internet usage: Severe shortage of IP addresses today
- Increasing mobile usage, pervasive computing: Network resources available worldwide 24/7
- Routing table explosion: IPv6 solves this
- Management Nightmare
- Most IPv4 addresses allocated to United States
- IPv6 has lots of extra features, and is more efficient:
- IPv4 has no support (build in) for new applications (QOS, Mobility etc.)
- IPv4 not scalable, efficient, extensible enough
- IPv4 only has 32-bit addressing
- IPv4 has no security (build in): IPv6 does
- IPv4 has lots of redundancy in protocol
Inhibitors:
- High transistion cost.
- Deployement Issues: Transistioning or direct replacement
- IPv6 is not backwards compatible:
- IPv4 applications cannot work with IPv6. Major patching effort.
- Lack of IPv6 applications in general.
- Transistion phase is needed: Either applications get rewritten, or we translate/tunnel different IP protocols through each other. [IPv4 over IPv6 or IPv4 over IPv6].
Paradigms:
- IPv4 era: Limited amount of online users thus a limited amount of IP-addresses, mostly allocated to US.
- IPv6 era: Enormous boom in online users, and new (mobile) networks demand for more and more IP-addresses. Backwards compatability should be solved by workarounds like tunneling or translation.
Experts:
Timing:
When the demand for new IP-addresses is high enough to force the industry to invest in IPv6 infrastructure. But before that happens IPv6 will be stimulated by many IPv6 networks that communicate over the web via IPv4 (tunneling/translation).
