{"id":2140,"date":"2015-11-24T18:34:47","date_gmt":"2015-11-24T18:34:47","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=2140"},"modified":"2020-05-06T10:30:07","modified_gmt":"2020-05-06T17:30:07","slug":"ipv4-the-future-of-a-legacy-protocol","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/","title":{"rendered":"IPv4: The Future of a Legacy Protocol"},"content":{"rendered":"

\"\"<\/p>\n

When I talk about the\u00a0recent significant uptick<\/a>\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I’m always a bit surprised by the mild astonishment they express.<\/p>\n

When I have the chance to ask them, they often respond that \u2014 given all the previous warnings about the impending exhaustion of IPv4 and the coming of IPv6 they\u2019d heard \u2014 at some point they stopped paying attention.<\/p>\n

Even for someone like myself who\u2019s ostensibly much more focused on IPv6, adoption trends in different countries can change very quickly. Time and again we witness the effects of a single major provider\u2019s enablement of IPv6 on subsequent levels of IPv6 user traffic.<\/p>\n

Three recent examples from different global regions effectively demonstrate this trend.<\/p>\n

Switzerland: 10 Days in June<\/strong><\/p>\n

Back in June, Swisscom\u2019s Martin Gysi gave a\u00a0presentation<\/a>\u00a0at the\u00a0IPv6 Business Conference sponsored by the Swiss IPv6 Council<\/a>.<\/p>\n

In it, he highlighted Swisscom\u2019s success in enabling IPv6. According to the presentation 67% of their customers were dual-stacked with greater than 20% of Swisscom\u2019s total traffic over IPv6 (Figure 1).<\/p>\n

\"\"<\/p>\n

Figure 1: Swisscom IPv6 statistics<\/p>\n

And in looking at the overall\u00a0Swiss Internet traffic hitting Google over IPv6<\/a>\u00a0you can easily detect exactly when they \u201cflipped the switch.\u201d (Figure 2).<\/p>\n

\"\"<\/p>\n

Figure 2: IPv6 Traffic to Google in Switzerland<\/p>\n

Over the course of 10 days, traffic more than doubled. As the graph shows, Swiss IPv6 traffic continues to grow significantly, increasing an additional 4% in the months since.<\/p>\n

This is offers a perfect example of the kind of rapid increase of IPv6 traffic that has taken many IT decision makers by surprise. They\u2019re more surprised still when they learn that many of these providers are trying to figure out how to get IPv4 off of their networks. For instance, in his presentation Mr. Gysi talks about the added load when running dual-stack on broadband network gateways (BNGs) and explores some of the configuration and architecture options for getting to IPv6-only sooner than later.<\/p>\n

IPv6, hoser!<\/a><\/p>\n

In the North American region IPv6 adoption continues to accelerate. The US is home to several service providers that have been in the vanguard of deploying IPv6. As you can see from the graphs below (taken from the\u00a0World IPv6 Launch measurements page<\/a>), Verizon, T-Mobile, and Comcast are all several years into their IPv6 deployment initiatives (Figures 3-5).<\/p>\n

\"\"<\/p>\n

 <\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Figures 3-5: Verizon, T-Mobile, and Comcast IPv6 deployment<\/p>\n

But as with the example of Swisscom in Switzerland even service provider adopters that have taken more time to scale up their subscriber offerings can cause a huge spike in a short period of time.<\/p>\n

While Canada\u2019s Telus has been diligently planning IPv6 for several years, even participating in World IPv6 Day as far back as 2011, they only enabled a large number of subscribers within the last two months (Figure 6).<\/p>\n

\"\"<\/p>\n

Figure 6: Telus IPv6 deployment<\/p>\n

Given that Telus services\u00a0close to a third of Canada’s wireless subscribers<\/a>\u00a0and has around\u00a01.5 million broadband subscribers<\/a>, the impact on the total level of Canadian IPv6 traffic isn\u2019t surprising (Figure 7).<\/p>\n

\"\"<\/p>\n

Figure 7: IPv6 Traffic to Google in Canada<\/p>\n

Meanwhile in Britannia<\/strong><\/p>\n

The same effect is visible in the UK. British provider BSkyB and a little company called British Telecom both\u00a0announced IPv6 initiatives back in November of 2014<\/a>\u00a0(and\u00a0Virgin Media has announced plans as well<\/a>).\u00a0Just recently, levels of IPv6 in the UK have rapidly increased: September of 2015 saw a 16-fold increase (Figure 8).<\/p>\n

\"\"<\/p>\n

Figure 8: IPv6 Traffic to Google in the UK<\/p>\n

Is China next?<\/strong><\/p>\n

With these examples in mind,\u00a0a recent tweet<\/a>\u00a0(below) from Alain Fiocco the head of\u00a0Cisco\u2019s 6lab<\/a>\u00a0(providing many of the IPv6 measurement graphs in this post) suggests Great Wall broadband may be preparing to deploy IPv6. Its parent company, MVNO Dr. Peng,\u00a0reaches over 80 million broadband subscribers in China<\/a>.<\/p>\n

\"\"<\/p>\n

IPv4: The Legacy Protocol by 2018<\/strong><\/p>\n

The examples above demonstrate the power of service provider IPv6 adoption in driving global levels of IPv6 traffic. Using extrapolation tools available via\u00a0Cisco\u2019s excellent 6lab site<\/a>, the point at which IPv6 becomes more than 50% of the overall traffic on the Internet could arrive as soon as early 2018 \u2014 slightly more than two years from today (Figure 9).<\/p>\n

\"\"<\/p>\n

Figure 9: Estimated Global Growth in IPv6 Internet Traffic<\/p>\n

The question is no longer merely whether your organization prepared to deploy and operate IPv6. The question now also includes whether your organization is ready to operate IPv4 as a\u00a0legacy protocol<\/em>.<\/p>\n

Be sure to visit the\u00a0Infoblox IPv6 Center of Excellence website<\/a>\u00a0for resources to help with your IPv6 adoption initiative.<\/p>\n

Also, make sure to check out Infoblox’s\u00a0free, online IPv6 address planning tool, 6Map<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I’m always a bit surprised by the mild astonishment they express. When I have the chance to ask them, they often respond that \u2014 given all the previous warnings about the impending exhaustion […]<\/p>\n","protected":false},"author":319,"featured_media":2149,"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":[87,28,50,30,16,51,56,38,31],"class_list":{"0":"post-2140","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-6map","9":"tag-ddi","10":"tag-dhcp","11":"tag-dns","12":"tag-infoblox","13":"tag-ipam","14":"tag-ipv4","15":"tag-ipv6","16":"tag-networking","17":"entry"},"acf":[],"yoast_head":"\nIPv4: The Future of a Legacy Protocol<\/title>\n<meta name=\"description\" content=\"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"IPv4: The Future of a Legacy Protocol\" \/>\n<meta property=\"og:description\" content=\"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2015-11-24T18:34:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:30:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"660\" \/>\n\t<meta property=\"og:image:height\" content=\"454\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Tom Coffeen\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tom Coffeen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/\"},\"author\":{\"name\":\"Tom Coffeen\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\"},\"headline\":\"IPv4: The Future of a Legacy Protocol\",\"datePublished\":\"2015-11-24T18:34:47+00:00\",\"dateModified\":\"2020-05-06T17:30:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/\"},\"wordCount\":780,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/change-ahead.jpg\",\"keywords\":[\"6MAP\",\"DDI\",\"DHCP\",\"DNS\",\"Infoblox\",\"IPAM\",\"IPv4\",\"IPv6\",\"Networking\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/\",\"name\":\"IPv4: The Future of a Legacy Protocol\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/change-ahead.jpg\",\"datePublished\":\"2015-11-24T18:34:47+00:00\",\"dateModified\":\"2020-05-06T17:30:07+00:00\",\"description\":\"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/change-ahead.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/change-ahead.jpg\",\"width\":660,\"height\":454},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-the-future-of-a-legacy-protocol\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"IPv6 CoE\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/category\\\/ipv6-coe\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"IPv4: The Future of a Legacy Protocol\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"name\":\"infoblox.com\\\/blog\\\/\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\",\"name\":\"Infoblox\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"width\":137,\"height\":30,\"caption\":\"Infoblox\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\",\"name\":\"Tom Coffeen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"caption\":\"Tom Coffeen\"},\"description\":\"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/tom-coffeen\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"IPv4: The Future of a Legacy Protocol","description":"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/","og_locale":"en_US","og_type":"article","og_title":"IPv4: The Future of a Legacy Protocol","og_description":"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/","og_site_name":"Infoblox Blog","article_published_time":"2015-11-24T18:34:47+00:00","article_modified_time":"2020-05-06T17:30:07+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg","type":"image\/jpeg"}],"author":"Tom Coffeen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Coffeen","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/"},"author":{"name":"Tom Coffeen","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1"},"headline":"IPv4: The Future of a Legacy Protocol","datePublished":"2015-11-24T18:34:47+00:00","dateModified":"2020-05-06T17:30:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/"},"wordCount":780,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg","keywords":["6MAP","DDI","DHCP","DNS","Infoblox","IPAM","IPv4","IPv6","Networking"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/","name":"IPv4: The Future of a Legacy Protocol","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg","datePublished":"2015-11-24T18:34:47+00:00","dateModified":"2020-05-06T17:30:07+00:00","description":"When I talk about the\u00a0recent significant uptick\u00a0of IPv6 adoption to IT decision makers that aren\u2019t necessarily paying any special attention to IPv6, I'm always a bit surprised by the mild astonishment they express.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/change-ahead.jpg","width":660,"height":454},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-the-future-of-a-legacy-protocol\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.infoblox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"IPv6 CoE","item":"https:\/\/www.infoblox.com\/blog\/category\/ipv6-coe\/"},{"@type":"ListItem","position":3,"name":"IPv4: The Future of a Legacy Protocol"}]},{"@type":"WebSite","@id":"https:\/\/www.infoblox.com\/blog\/#website","url":"https:\/\/www.infoblox.com\/blog\/","name":"infoblox.com\/blog\/","description":"","publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.infoblox.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.infoblox.com\/blog\/#organization","name":"Infoblox","url":"https:\/\/www.infoblox.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","width":137,"height":30,"caption":"Infoblox"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1","name":"Tom Coffeen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","caption":"Tom Coffeen"},"description":"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.","url":"https:\/\/www.infoblox.com\/blog\/author\/tom-coffeen\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/2140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/users\/319"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=2140"}],"version-history":[{"count":3,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/2140\/revisions"}],"predecessor-version":[{"id":2160,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/2140\/revisions\/2160"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/2149"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=2140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=2140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=2140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}