{"id":7890,"date":"2022-07-12T13:56:04","date_gmt":"2022-07-12T20:56:04","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=7890"},"modified":"2022-07-12T13:56:04","modified_gmt":"2022-07-12T20:56:04","slug":"the-true-cost-of-ipv4","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/","title":{"rendered":"The True Cost of IPv4"},"content":{"rendered":"

Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers.\u00a0 The status quo is a strong force.\u00a0 If everything is seemingly running well in the network, what is the driver to deviate?\u00a0 If it ain\u2019t broke, don\u2019t fix it, right?\u00a0 (Even if the network team sees impending problems by putting off network evolution.)<\/p>\n

The reality is that making the business case for deploying IPv6 can be a challenge.\u00a0 There is seldom a \u201cyou can save $40M if you do this\u201d moment that can be used to get the attention of leaders that often look at the world through a financial lens rather than a technical one.<\/p>\n

Ed Horley makes numerous business and financial arguments in support of IPv6 deployment in his blog The Problem Isn\u2019t the Price of IPv4<\/a>, and Scott Hogg, Tom Coffeen, and Ed further bolster the business case on their IPv6 Buzz 97 podcast Selling An IPv6 Project To Your Organization<\/a>. \u00a0\u00a0At the same time, I would like to build off this theme, but from the opposite direction.\u00a0 There are the business benefits of deploying IPv6, and there are also significant financial negatives associated with clinging to IPv4.\u00a0 It pains me to focus on IPv4 in an IPv6 Center of Excellence blog, but the goal is to assist you, the Network Architect, in building your case to corporate decision makers, and ultimately further the advancement of IPv6.<\/p>\n

So, let\u2019s dive into the true costs of IPv4.<\/p>\n

The actual cost of IPv4<\/strong><\/h3>\n

The first obvious cost of IPv4\u2026 is the actual cost of IPv4.\u00a0 The RIR\u2019s have depleted their free pools<\/a>, so getting address space from ARIN (or any other RIR) is not an option.\u00a0 For large service providers, the lack of public IPv4 address space makes the business case fairly straightforward.\u00a0 And they have aggressively deployed IPv6 – with some turning to IPv6-only<\/a>.\u00a0 However, the general impression is that most small enterprises have sufficient public IPv4 addresses, and have not yet felt the squeeze of RFC 1918 limitations.\u00a0 But is that completely true?\u00a0 Times are changing.\u00a0 In planning for the future of address management, make sure to account for modern networking trends.\u00a0 Most enterprises have adopted or are adopting a hybrid cloud strategy.\u00a0 Ensure that the network team is in sync with the cloud team on addressing needs in AWS, Azure, GCP, or your CSP of choice.\u00a0 The address requirements may be significantly greater than originally thought.\u00a0 Also, does your enterprise utilize containers, or plan on large IoT deployments?\u00a0 These can also be large consumers of IP addresses.<\/p>\n

The point being, even some smaller enterprises, after looking at the big picture and future network evolution, may be squeezed for IPv4 addresses \u2013 both public and private.<\/p>\n

If addresses are procured<\/a> from the gray market, there is a hard cost to acquire and transfer these assets.\u00a0 And that cost is currently above $50<\/a> per IP and rising.<\/p>\n

Or another way to look at the price of IPv4 addresses – they are a benefit to those enterprises that have a wealth of addresses to spare.\u00a0 These IPv4 assets could be sold on the public transfer market to other organizations that can justify the need.\u00a0 This is an important opportunity to keep in mind in your business case.<\/p>\n

The hidden costs of managing NAT<\/strong><\/h3>\n

In addition to the actual cost of IPv4, there are significant hidden costs.\u00a0 The most obvious is the cost of Network Address Translation (NAT) and address overlaps.\u00a0 Personally, I\u2019ve spent thousands of hours in my career dealing with NAT-related issues.\u00a0 How much time do you spend on this activity each year?\u00a0 Consider the cost of renumbering after M&A activity while attempting to splice together two networks that both use 10.0.0.0\/8.\u00a0 Or the cost of troubleshooting application reachability across the WAN given multiple firewalls implementing NAT.\u00a0 Root cause analysis is complicated by sifting through logs where addresses may or may not be the same addresses you were told were the source and destination IP\u2019s having connectivity problems.\u00a0 All of this consumes valuable engineering resources, time, and corporate productivity for critical business functions. There may be additional hidden costs because we often do not consistently account for the effort a full-time employee is spending working on NAT or renumbering issues. \u00a0(Instead of, say, spending time working on network automation, or zero trust, or other productive new innovations.)<\/p>\n

The added complexity of NAT in security policy also increases the risk of misconfiguration.\u00a0 Security can be jeopardized when multiple network and security engineers work on the same firewall sorting through convoluted layers of policy and translation.\u00a0 Consider the risks of a forensics specialist trying to track down a malware infection incident log for a device using 10.3.6.8, and that address is used in multiple different networks simultaneously.\u00a0 Simplicity can be a virtue, while IPv4\/NAT\/RFC1918 typically is anything but simple.\u00a0 And today, security mistakes can have large material costs that may threaten the entire business.<\/p>\n

It can be difficult to articulate and quantify these soft costs to corporate leaders, but we can attempt to frame the argument in human resources costs.\u00a0 If you spend 200 hours per year troubleshooting, think of all the others engaged in the troubleshooting effort with you \u2013 project managers, other network engineers, application developers, firewall administrators, etc.\u00a0 Employee time is often not tracked to this level, but it certainly adds up.\u00a0 Not to mention lost productivity in the broader company for employees waiting for the network to \u201cjust work.\u201d<\/p>\n

Equipment CAPEX and OPEX<\/strong><\/h3>\n

One expense that can be more easily pinned down is the cost of network devices.\u00a0 Network Address Translation takes memory, CPU cycles, and silicon to work.\u00a0 Consider the cost of NAT and\/or dual stack on routers, ADCs, firewalls, and all other network devices in your environment.\u00a0 It is well known that TCAM<\/a> is expensive, and deploying larger and more expensive routers to deal with IPv4 and NAT adds cost \u2013 not just up front but over the lifetime of the devices given annual subscriptions and maintenance.\u00a0 Firewalls are also expensive bit-movers (or blockers). \u00a0When spec\u2019ing out the proper firewall model, there are tiers to consider with respect to NAT table and security policy size.\u00a0 IPv4, and the NAT that commonly accompanies it, can add significant expense to your firewall, as well as other network devices. This added expense can bolster a business case that may get the attention of corporate leaders.<\/p>\n

Other Hard-to-Quantify Costs<\/strong>\u00a0<\/strong><\/h3>\n

Then there are more subtle drivers of costs that are difficult to quantify.\u00a0 For example, how can you put a price on IPv4 being slower than IPv6 in many cases<\/a>.\u00a0 For companies that rely on e-commerce revenue or customer experience in their app, performance may be measurable<\/a> in dollars.\u00a0 For other organizations, performance differences are at least worth noting when pitching the IPv6 business case to your CIO.<\/p>\n

Finally, can a cost be assigned to procrastination?\u00a0 The transition to IPv6 is ultimately unavoidable.\u00a0 Early adopters are reaping the benefit of moving to IPv6. \u00a0Standing on the sidelines could eventually prove costly.\u00a0 There will ultimately be a driver for your organization\u2019s IPv6 transition, whether that is customer experience\/demand, extranets\/partners, IPv4 exhaustion, or possibly even a compliance mandate.\u00a0 For many applications, and in many areas of the Internet, IPv6 represents a majority of traffic<\/a>.\u00a0 Forward thinking and avoiding technology obsolescence, while often difficult to quantify, can have benefits \u2013 especially in wide-ranging projects such as IPv6 implementations that can\u2019t realistically be done with a single \u201call-hands-on-deck\u201d effort.\u00a0 Executing such a project in a constant, planned, and non-disruptive fashion can save hard and soft costs.\u00a0 Upgrade to IPv6 on your timetable, not someone else\u2019s!<\/p>\n

Conclusions<\/strong><\/h3>\n

For large service providers, the deployment of IPv6 is a no-brainer – and probably happened years ago.\u00a0 For greenfield network deployments the same could be said.\u00a0 (Why would they go out of their way to deploy only IPv4, or even dual stack?)\u00a0\u00a0 However, many enterprises still lag in IPv6 adoption.\u00a0 The goal of the forward-thinking Network Architect is to formulate a business case and get buy-in from corporate decision makers to advance IPv6.\u00a0 There are two sides of this coin that can be used to articulate this thesis:\u00a0 the benefits of IPv6, and the cost of IPv4.\u00a0 C-level executives may not know the difference between IPv4 and IPv6 (or AppleTalk for that matter!).\u00a0 Nor should they care.\u00a0 But they want the business to run efficiently and smoothly.\u00a0 And you can enlighten them to the tangible benefits of starting the journey through dual-stack toward the ultimate goal of IPv6-only.\u00a0 This effort can reduce risk and save money.\u00a0 And it can, and should, be done in a controlled and planned manner.<\/p>\n","protected":false},"excerpt":{"rendered":"

Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers.\u00a0 The status quo is a strong force.\u00a0 If everything is seemingly running well in the network, what is the driver to deviate?\u00a0 If it ain\u2019t broke, don\u2019t fix it, right?\u00a0 (Even […]<\/p>\n","protected":false},"author":351,"featured_media":1016,"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":[56,38,717,120,617,718,719,720],"class_list":{"0":"post-7890","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-ipv4","9":"tag-ipv6","10":"tag-ip-address","11":"tag-arin","12":"tag-nat","13":"tag-rfc1918","14":"tag-tcam","15":"tag-network-traffic","16":"entry"},"acf":[],"yoast_head":"\nThe True Cost of IPv4<\/title>\n<meta name=\"description\" content=\"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)\" \/>\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\/the-true-cost-of-ipv4\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The True Cost of IPv4\" \/>\n<meta property=\"og:description\" content=\"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-12T20:56:04+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.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=\"Cody Christman\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Cody Christman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 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\\\/the-true-cost-of-ipv4\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/\"},\"author\":{\"name\":\"Cody Christman\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/467b05606b1887c11ca4576261e71c8a\"},\"headline\":\"The True Cost of IPv4\",\"datePublished\":\"2022-07-12T20:56:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/\"},\"wordCount\":1461,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/community-banner-5.jpg\",\"keywords\":[\"IPv4\",\"IPv6\",\"IP address\",\"ARIN\",\"NAT\",\"RFC1918\",\"TCAM\",\"network traffic\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/\",\"name\":\"The True Cost of IPv4\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/community-banner-5.jpg\",\"datePublished\":\"2022-07-12T20:56:04+00:00\",\"description\":\"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/community-banner-5.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/community-banner-5.jpg\",\"width\":660,\"height\":454,\"caption\":\"woman connecting network cables to switches; Shutterstock ID 171079511\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-true-cost-of-ipv4\\\/#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\":\"The True Cost of IPv4\"}]},{\"@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\\\/467b05606b1887c11ca4576261e71c8a\",\"name\":\"Cody Christman\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_351_1611073779-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_351_1611073779-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_351_1611073779-96x96.jpg\",\"caption\":\"Cody Christman\"},\"description\":\"Cody (@notthefakecc) is a principal consultant at HexaBuild.io, an IPv6 consulting and training company. Cody is a cofounder of the Rocky Mountain IPv6 Task Force (RMv6TF) and a recognized IPv6 expert with decades of IPv6 experience. Follow HexaBuild on X (formerly Twitter) and LinkedIn to learn more about advancing cloud, IoT and security with IPv6.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/cody-christman\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The True Cost of IPv4","description":"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)","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\/the-true-cost-of-ipv4\/","og_locale":"en_US","og_type":"article","og_title":"The True Cost of IPv4","og_description":"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/","og_site_name":"Infoblox Blog","article_published_time":"2022-07-12T20:56:04+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.jpg","type":"image\/jpeg"}],"author":"Cody Christman","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Cody Christman","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/"},"author":{"name":"Cody Christman","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/467b05606b1887c11ca4576261e71c8a"},"headline":"The True Cost of IPv4","datePublished":"2022-07-12T20:56:04+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/"},"wordCount":1461,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.jpg","keywords":["IPv4","IPv6","IP address","ARIN","NAT","RFC1918","TCAM","network traffic"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/","name":"The True Cost of IPv4","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.jpg","datePublished":"2022-07-12T20:56:04+00:00","description":"The True Cost of IPv4. Working with enterprises, I am often confronted with the challenge of justifying the benefits of deploying IPv6 to C-levels and corporate IT decision makers. The status quo is a strong force. If everything is seemingly running well in the network, what is the driver to deviate? If it ain\u2019t broke, don\u2019t fix it, right? (Even if the network team sees impending problems by putting off network evolution.)","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/community-banner-5.jpg","width":660,"height":454,"caption":"woman connecting network cables to switches; Shutterstock ID 171079511"},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-true-cost-of-ipv4\/#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":"The True Cost of IPv4"}]},{"@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\/467b05606b1887c11ca4576261e71c8a","name":"Cody Christman","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_351_1611073779-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_351_1611073779-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_351_1611073779-96x96.jpg","caption":"Cody Christman"},"description":"Cody (@notthefakecc) is a principal consultant at HexaBuild.io, an IPv6 consulting and training company. Cody is a cofounder of the Rocky Mountain IPv6 Task Force (RMv6TF) and a recognized IPv6 expert with decades of IPv6 experience. Follow HexaBuild on X (formerly Twitter) and LinkedIn to learn more about advancing cloud, IoT and security with IPv6.","url":"https:\/\/www.infoblox.com\/blog\/author\/cody-christman\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/7890","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\/351"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=7890"}],"version-history":[{"count":1,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/7890\/revisions"}],"predecessor-version":[{"id":7891,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/7890\/revisions\/7891"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/1016"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=7890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=7890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=7890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}