{"id":1807,"date":"2017-01-23T22:11:14","date_gmt":"2017-01-23T22:11:14","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=1807"},"modified":"2020-05-06T10:28:01","modified_gmt":"2020-05-06T17:28:01","slug":"ipv6-predictions-for-2017","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/","title":{"rendered":"IPv6 Predictions for 2017"},"content":{"rendered":"

I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times. IPv6 has had a longer ramp-up than expected and us IPv6 advocates have often been frustrated by the pace of adoption.\u00a0 The good news for me was that 2016 was a really great year for IPv6. You can check out my end of year\u00a0prediction reviews<\/a>\u00a0and see just how much really did change for IPv6 overall.<\/p>\n

But we are in a new year and I wanted to share what I think will change for IPv6 in 2017. In a similar format to my\u00a0IPv6 predictions for 2016<\/a>\u00a0I am simply stating what I think will happen.<\/p>\n

    \n
  1. The majority of container solutions (Docker, Kubernetes, Mesos*) will have IPv6 support by the end of 2017<\/li>\n
  2. IPv6 growth worldwide will again outpace the US<\/li>\n
  3. Major private cloud solutions (OpenStack, AzureStack, VMware) will have production ready IPv6 support<\/li>\n
  4. Security will finally start figuring out IPv6<\/li>\n
  5. Early IPv6-only data center solutions will start happening<\/li>\n<\/ol>\n

    Let\u2019s walk through each of these in more detail and unpack what I mean.<\/p>\n

    I think 2017 will continue to see the mass adoption of\u00a0containers<\/a>\u00a0for both developers and operators. There will likely be a period of disillusionment during 2017 (especially by those looking to push function as a service solutions) but containers and those that have solutions around containers will see continued massive growth. The container solutions around management of workloads and managing the clusters will be super important. They are effectively the next generation of operator platforms replacing VMware vCenter or OpenStack Horizon (as an interface at least). These solutions, I believe, will provide the ability to run and operate with IPv4 and\/or IPv6. The reality is that Mesos already provides this capability (Mesos was written with IPv6 support from day one) but production level support for IPv6 in Docker and Kubernetes are some ways off (see Shannon McFarland’s IPv6 and Docker blogs):<\/p>\n

    BASIC CONFIGURATION OF DOCKER ENGINE WITH IPV6<\/a><\/p>\n

    DOCKER, IPV6 AND \u2013NET=\u201dHOST”<\/a><\/p>\n

    DOCKER SWARM AND ETCD WITH IPV6<\/a><\/p>\n

    It shouldn\u2019t come as a surprise to anyone that the rest of the world will start adopting IPv6 at a faster rate, and here\u2019s why: The US is above 33% of native IPv6 services (mainly due to mobile operators) and that rate will grow steadily over 2017. But because so many countries outside the US have not had\u00a0high adoption rates<\/a>\u00a0(with a few exceptions like Belgium) they have a much higher initial deployment growth curve to leverage. Often a single service provider enabling IPv6 for a country will cause a massive deployment of IPv6 almost overnight. I think several other countries are poised to do just that in 2017. Also, if China or Russia decide to do that it would instantly become the largest deployment increase of the year. So keep your eyes out for such announcements!<\/p>\n

    Private clouds will become more important in 2017 as more and more customers determine that an all-in public cloud strategy does not address all their business requirements or concerns. As a result, you will see an uptick in hybrid-cloud solutions that will require deployment of private clouds. These private clouds will want to be as tightly integrated with their public cloud counterparts as possible to allow for low friction utilization of both public and private cloud. AWS and Azure both have native IPv6 capabilities and I expect Google to have the same shortly. With that in mind, it just makes natural sense that the on-premises version will need to have IPv6 support too. It will take until the end of 2017 to see anything close to a production level quality deployment of IPv6 for on-premises but I do believe it will happen this year.<\/p>\n

    Because of IPv6 support from the major public cloud providers the security industry overall will be forced to more deeply embrace and start taking IPv6 more seriously. You will start seeing IPv6 specific capabilities within security product portfolio but also\u00a0event correlation and matching for dual-stack hosts<\/a>. Understanding the relationship between IPv4 and IPv6 and what events are happening on either protocol will become more important. Turning off IPv6 will no longer be the standard request from IT security and gaining skill and insight into what IPv6 is doing will become more common among IT stakeholders.<\/p>\n

    My crazier prediction is that we will start seeing some more cutting edge companies decide to start deploying IPv6-only data center solutions to meet the demand of the mobile market. I don\u2019t think there will be a huge amount of them but I do believe you will start seeing companies take a very serious look into the option of doing an IPv6-only solution to meet their primary customer needs. They may adopt protocol conversion or proxy functions for IPv4 so that an IPv6-only solution can still provide resources for an IPV4-only host. At some point, as IPv6 adoption grows, it will be far more cost-effective to deploy and operate a new data center with IPv6-only compared to a dual-stack solution. I think that tipping point will happen in late 2017.<\/p>\n

    So, in summary, cloud, containers and global adoption will be the big IPv6 stories and my fingers are crossed that security and IPv6-only data center will become an important part of the 2017 story too.<\/p>\n

    You can find me on twitter as\u00a0@ehorley<\/a>\u00a0and remember\u2026<\/p>\n

    IPv6 is the future and the future is now!<\/p>\n

    – Ed<\/p>\n","protected":false},"excerpt":{"rendered":"

    I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times. IPv6 has had a longer ramp-up than expected and us IPv6 advocates have often been frustrated by the pace of adoption.\u00a0 The good news for me was that 2016 was a really great […]<\/p>\n","protected":false},"author":323,"featured_media":1808,"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":[38],"class_list":{"0":"post-1807","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-ipv6","9":"entry"},"acf":[],"yoast_head":"\nIPv6 Predictions for 2017<\/title>\n<meta name=\"description\" content=\"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.\" \/>\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\/ipv6-predictions-for-2017\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"IPv6 Predictions for 2017\" \/>\n<meta property=\"og:description\" content=\"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-01-23T22:11:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:28:01+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.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=\"Ed Horley\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ed Horley\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 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\\\/ipv6-predictions-for-2017\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/\"},\"author\":{\"name\":\"Ed Horley\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b09ec2fd0a273ea1cb94ae2fd98232f9\"},\"headline\":\"IPv6 Predictions for 2017\",\"datePublished\":\"2017-01-23T22:11:14+00:00\",\"dateModified\":\"2020-05-06T17:28:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/\"},\"wordCount\":913,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/may-13-1.jpg\",\"keywords\":[\"IPv6\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/\",\"name\":\"IPv6 Predictions for 2017\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/may-13-1.jpg\",\"datePublished\":\"2017-01-23T22:11:14+00:00\",\"dateModified\":\"2020-05-06T17:28:01+00:00\",\"description\":\"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/may-13-1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/may-13-1.jpg\",\"width\":660,\"height\":454},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-predictions-for-2017\\\/#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\":\"IPv6 Predictions for 2017\"}]},{\"@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\\\/b09ec2fd0a273ea1cb94ae2fd98232f9\",\"name\":\"Ed Horley\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/blog-ed-horley-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/blog-ed-horley-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/blog-ed-horley-96x96.jpg\",\"caption\":\"Ed Horley\"},\"description\":\"Ed Horley (@ehorley) is a Co-founder and CEO of HexaBuild.io, an IPv6 consulting and training company. Ed is Co-chair of the California IPv6 Task Force (CAv6TF) and authored the Apress Press book Practical IPv6 for Windows Administrators and two IPv6 courses on Pluralsight. He is also the co-host of the IPv6 Buzz Podcast on the PacketPushers. Follow HexaBuild on Twitter and LinkedIn and let us help you advance cloud, IoT and security with IPv6!\",\"sameAs\":[\"https:\\\/\\\/hexabuild.io\"],\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/ed-horley\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"IPv6 Predictions for 2017","description":"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.","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\/ipv6-predictions-for-2017\/","og_locale":"en_US","og_type":"article","og_title":"IPv6 Predictions for 2017","og_description":"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/","og_site_name":"Infoblox Blog","article_published_time":"2017-01-23T22:11:14+00:00","article_modified_time":"2020-05-06T17:28:01+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.jpg","type":"image\/jpeg"}],"author":"Ed Horley","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ed Horley","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/"},"author":{"name":"Ed Horley","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b09ec2fd0a273ea1cb94ae2fd98232f9"},"headline":"IPv6 Predictions for 2017","datePublished":"2017-01-23T22:11:14+00:00","dateModified":"2020-05-06T17:28:01+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/"},"wordCount":913,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.jpg","keywords":["IPv6"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/","name":"IPv6 Predictions for 2017","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.jpg","datePublished":"2017-01-23T22:11:14+00:00","dateModified":"2020-05-06T17:28:01+00:00","description":"I admit that being an IPv6 advocate for as long as I have been can cause some self-doubt and loathing at times.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/may-13-1.jpg","width":660,"height":454},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-predictions-for-2017\/#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":"IPv6 Predictions for 2017"}]},{"@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\/b09ec2fd0a273ea1cb94ae2fd98232f9","name":"Ed Horley","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/blog-ed-horley-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/blog-ed-horley-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/blog-ed-horley-96x96.jpg","caption":"Ed Horley"},"description":"Ed Horley (@ehorley) is a Co-founder and CEO of HexaBuild.io, an IPv6 consulting and training company. Ed is Co-chair of the California IPv6 Task Force (CAv6TF) and authored the Apress Press book Practical IPv6 for Windows Administrators and two IPv6 courses on Pluralsight. He is also the co-host of the IPv6 Buzz Podcast on the PacketPushers. Follow HexaBuild on Twitter and LinkedIn and let us help you advance cloud, IoT and security with IPv6!","sameAs":["https:\/\/hexabuild.io"],"url":"https:\/\/www.infoblox.com\/blog\/author\/ed-horley\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1807","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\/323"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=1807"}],"version-history":[{"count":3,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1807\/revisions"}],"predecessor-version":[{"id":3686,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1807\/revisions\/3686"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/1808"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=1807"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=1807"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=1807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}