Though it lacked a high-profile event like 2012’s\u00a0World IPv6 Launch<\/u>, 2013 was still an eventful year for IPv6. As it stands, 2014 might prove the proverbial “calm before the storm” if IPv4 runs out in North America in 2015 as predicted. In any case,\u00a0we should expect to see more slow but steady progress in the worldwide deployment of IPv6.<\/p>\n
IPv4 Exhaustion<\/b><\/p>\n
IPv4 has already been formally exhausted in Asia and Europe. For much of 2011 and 2012, projections of IPv4 rundown suggested that 2013 would be the year that North America exhausted its supply IPv4. Due to a number of factors, including grey market transfers of address space as well as perhaps a more cautious application of policy by\u00a0ARIN (the Internet registry for the region), the\u00a0estimated date of North American run out of IPv4 is now in early\u00a02015<\/u>. Of course, as with any scarce resource approaching its imminent exhaustion\u00a0is subject to the phenomenon of rapid and unpredictable depletion, the date could always arrive sooner.<\/p>\n
In any case, once North American exhaustion of IPv4 happens, expect much sky-is-falling industry media coverage. Resulting reactions from\u00a0enterprise IT administrators will likely run the gamut from wary (or even smug) confidence in their IPv6 adoption planning and efforts to this point, to\u00a0the shrugging of shoulders (likely the majority reaction), to outright\u00a0weeping and gnashing of teeth as upper management decides and demands, in\u00a0Veruca Salt-like fashion<\/u>\u00a0that “don’t care how” the organization in question must have “IPv6 now” (with no serious preparation for adoption having\u00a0yet occurred).<\/p>\n
IPv6 Uptake<\/b><\/p>\n
Though in large part subsumed by arguably underwhelming\u00a0statistics showing IPv6 as ~2% of overall Internet traffic<\/u>,\u00a02013 saw remarkable data points that, taken individually, suggest a watershed uptake of IPv6:<\/p>\n As suggested above, uptake of IPv6 among enterprises is likely to be accelerated by the formal announcement of IPv4 exhaustion in North America.\u00a0In the meantime (and with notable, high-profile exceptions), enterprises will continue to adopt IPv6 more slowly, with emphasis on first making websites and Internet-facing resources available over IPv6 while continuing to rely on NAT and private addressing internally.<\/p>\n The IPv6 Protocol<\/b><\/p>\n Now that IPv6 is beginning to see more substantial adoption levels across the Internet and in production environments, some aspects of the protocol itself\u00a0are getting more scrutiny.<\/p>\n 2013 saw a\u00a0proposal to deprecate the IPv6 fragment header<\/u>\u00a0due to\u00a0its resource-intensive nature at the application layer as well as\u00a0its use as an attack vector (many firewalls are configured to drop IPv6 fragments). Of course, DNSSEC over UDP often relies on IPv6 fragmentation so deprecation before a workable alternative architecture is defined and deployed is unlikely. (And as we all know: as goes DNSSEC, so goes the Internet!).<\/p>\n In a boon for secure deployment of IPv6 in the enterprise, last year also saw the introduction of\u00a0expanded first-hop security features from Cisco<\/u>. These features complement Cisco IOS’s\u00a0existing support for\u00a0secure neighbor discovery (SeND)<\/u>\u00a0and attempt to make\u00a0the local IPv6 segment more secure, perhaps in the absence of wide deployment of SeND. Commonly\u00a0deployed host OS implementations of IPv6 continue to lack support for SeND and significant progress on this front seems unlikely in 2014 (though some external applications might make SeND feasible in the enterprise, if not scalable or manageable).<\/p>\n I<\/b>Pv6 and You<\/b><\/p>\n If you haven’t started your IPv6 adoption effort, the momentum suggested above might be cause for concern. But don’t panic! Check out our\u00a0abundant knowledge resources on the topic<\/u>\u00a0to help you get started. And if you have started, let us know in the comments how things are going for you and what your plans for IPv6 are in 2014.<\/p>\n Tom Coffeen<\/p>\n @ipv6tom<\/p>\n","protected":false},"excerpt":{"rendered":" Though it lacked a high-profile event like 2012’s\u00a0World IPv6 Launch, 2013 was still an eventful year for IPv6. As it stands, 2014 might prove the proverbial “calm before the storm” if IPv4 runs out in North America in 2015 as predicted. In any case,\u00a0we should expect to see more slow but steady progress in the […]<\/p>\n","protected":false},"author":319,"featured_media":3187,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[17],"tags":[16,38,15],"class_list":{"0":"post-3550","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-ipv6","10":"tag-security","11":"entry"},"acf":[],"yoast_head":"\n\n