{"id":4591,"date":"2012-02-06T11:14:35","date_gmt":"2012-02-06T19:14:35","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=4591"},"modified":"2020-05-06T10:31:43","modified_gmt":"2020-05-06T17:31:43","slug":"ipv4-nat-is-the-killer-app-for-ipv6","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/","title":{"rendered":"IPv4 NAT is the Killer App for IPv6"},"content":{"rendered":"<p>Another guest posting from\u00a0<a href=\"http:\/\/www.hoggnet.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Scott Hogg<\/a>\u00a0of our Technical Advisory Board.<\/p>\n<p>cricket<\/p>\n<p>For years people have been looking for the \u201cKiller App\u201d that will make everyone want to deploy IP Version 6 (IPv6).\u00a0 The primary reasons to deploy IPv6 have been to gain a larger address space and to avoid technological obsolescence.\u00a0 There have been several applications that we thought would be the Killer App for IPv6.\u00a0 These include\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/Ipsec\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">IPSec<\/a>,\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/Mobile_ipv6\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Mobile IPv6<\/a>,\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/Threedegrees\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Microsoft Three Degrees<\/a>,\u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/network\/dd420463\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Microsoft Direct Access<\/a>, and sensor networks enabled with\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/SLAAC#Stateless_address_autoconfiguration_.28SLAAC.29\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Stateless Address Auto-Configuration (SLAAC)<\/a>.\u00a0 However, these technologies and products have not caught on or have not been rapidly deployed.\u00a0 The search goes on for the one thing that will drive rapid IPv6 adoption.<\/p>\n<p>The fact remains that IPv4 address exhaustion has occurred in Asia and is coming soon to Europe and North America.\u00a0 If you do not believe the \u201crumors\u201d about IPv4 address exhaustion, then just try to ask your local RIR for another \/18.\u00a0 You will likely be unsuccessful unless you have some pretty heavy-weight justification for needing more public IPv4 addresses.\u00a0 The reality is that many organizations are going to be running IPv4 in their environment for the next 20 years.\u00a0 Does your organization really have enough IPv4 addresses to last for 20 years?<\/p>\n<p>Many times I have heard people utter the words \u201cour organization has plenty of IPv4 addresses so we don\u2019t need IPv6.\u201d \u00a0It may be true that they have plenty of IPv4 address for their immediate needs, but they may not be anticipating changes coming in the next 20 years.\u00a0 And just because you may have plenty of IPv4 addresses does not mean that there won\u2019t be others on the Internet who want to do business with you but they may be trying to use IPv6 to reach you.\u00a0 20 years ago could any of us predicted the explosion of WiFi, 3G, and 4G mobile devices.\u00a0 We can daydream and wonder what life will be like in 20 years.\u00a0 Regardless, it is easy to predict that the number of IP-enabled devices will continue to increase and put an even greater strain on IPv4 addressing.<\/p>\n<p>Now that the industry has reached a late stage of IPv4 address depletion there are many\u00a0<a href=\"http:\/\/www.networkworld.com\/community\/blog\/techniques-prolonging-lifespan-ipv4\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">creative ways to extend the lifespan of IPv4<\/a>. \u00a0These techniques include continuing to increase the efficiency of IPv4 addressing by continuing to chop up the address space into smaller and smaller subnets.\u00a0 This puts a greater strain on your IPv4 addressing plan and requires an efficient IP Address Management (IPAM) system to maintain your sanity and the accuracy of the addressing.<\/p>\n<p>Network Address Translation (NAT) is the technique that virtually all organizations use to allow for an internal network that uses private IPv4 addresses and translate them to a very limited number of public IPv4 addresses.\u00a0 Most enterprise organizations use NAT at their Internet perimeter and virtually all residential broadband Internet links use NAT.\u00a0 In fact, NAT has to be used with IPv4 because there is not enough address space for all IP nodes.\u00a0 If it weren\u2019t for NAT, the Internet would have run out of public IPv4 addresses many years ago.<\/p>\n<p>NAT is not an optimal solution for Internet communications because NAT breaks the end-to-end model of communications between nodes using unique IP addresses.\u00a0 The use of NAT has slowed down or limited the growth of transparent applications.\u00a0 Troubleshooting with NATs adds complexity and there is no easy way to maintain states of NAT in case of node failures.\u00a0 NAT breaks several applications like IP security (IPSec), reputation filtering, geolocation, FTP (requiring PASV mode), SNMP, and any other application that embeds the IP address in the application protocol payload.\u00a0 NAT allows for anonymity on the Internet and thus creates an environment for hackers hiding behind NATs.\u00a0 NAT also complicates mergers\/acquisitions and \u201cdouble-NATing\u201d is often needed for devices at the two companies to communicate with each other.<\/p>\n<p>Service providers have been feeling the pinch when it comes to limited IPv4 addresses.\u00a0 Many service providers do not have sufficient IPv4 addresses to continue to connect their customers to the Internet and sustain their growth for years to come.\u00a0 The fact is that service providers will need to continue to allocate IPv4 addresses to customers regardless of their IPv6 deployment plans.\u00a0 This situation has caused service providers to\u00a0<a href=\"http:\/\/www.networkworld.com\/community\/blog\/can-large-scale-nat-save-ipv4\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">starting contemplating using NAT in their networks<\/a>.\u00a0 In fact, service providers are actively planning and deploying Large-Scale NAT (LSN)\/Carrier-Grade NAT (CGN) solutions.\u00a0 This means that their customers will not be given a public IPv4 address for their connection and instead will be allocated a private IPv4 address.\u00a0 The customer will have one level of NAT at their location translating their private IPv4 addresses into their private IPv4 address provided by the service provider.\u00a0 The service provider will use private IPv4 addresses in the core of their infrastructure and perform another level of NAT to translate the connections to the limited public IPv4 address space they have remaining.\u00a0 This would create multiple layers of NAT and is sometimes referred to at NAT444.\u00a0 For most organizations, one level of NAT is not that difficult to live with, but problems start to arise when multiple levels of NAT are used.<\/p>\n<p>Today, some international organizations cannot get public IPv4 addresses for their Internet links.\u00a0 These organizations use residential broadband Internet connections to link up their small remote sites to their corporate extranet.\u00a0 The service providers in other countries are no longer offering public IPv4 addresses on residential-grade service and are using a LSN\/CGN system in their core.\u00a0 If the organization\u2019s remote sites cannot get a public, static IPv4 address then they cannot build site-to-site IPsec VPN tunnels between their sites.<\/p>\n<p>There are many miseries resulting from using multiple layers of NAT.\u00a0 For example, the performance of the IPv4 connections may deteriorate if the CGN\/LSN system is not scaled appropriately for the number of customers the service provider is connecting through the system.\u00a0 If the pool of public IPv4 addresses is too small then customers will be fighting for connections based on the limited number of addresses and port numbers available.\u00a0 The subscribers will also experience increased Internet latency as all their Internet traffic follows its path to the Internet through the city where the carrier has positioned the CGN\/LSN system.\u00a0 Subscribers may also find many applications that have difficulties going through multiple layers of NAT.\u00a0 The service provider will likely field many technical support calls from their subscribers as a result of the problems the end users experience.<\/p>\n<p>Over time, service providers will fully deploy IPv6 in their networks and more and more subscribers will gain IPv6 Internet connectivity.\u00a0 Customers may start to notice that their IPv6 connections will use native connectivity and follow the most direct path to and from the Internet.\u00a0 This will be a contrast to their experience using IPv4 in a double-NAT environment.\u00a0 Over time, service provider customers will start to see the benefits of native IPv6 and this will drive consumers of Internet connectivity to further adopt IPv6.\u00a0 Over time IPv6 will become the preferred transport method.<\/p>\n<p>It turns out that the \u201cKiller App\u201d for IPv6 is the poor IPv4 performance people will experience through using multiple layers of IPv4 NAT.<\/p>\n<p>Scott<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board. cricket For years people have been looking for the \u201cKiller App\u201d that will make everyone want to deploy IP Version 6 (IPv6).\u00a0 The primary reasons to deploy IPv6 have been to gain a larger address space and to avoid technological obsolescence.\u00a0 There have been several applications [&hellip;]<\/p>\n","protected":false},"author":178,"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,56,38,15],"class_list":{"0":"post-4591","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-ipv4","10":"tag-ipv6","11":"tag-security","12":"entry"},"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>IPv4 NAT is the Killer App for IPv6<\/title>\n<meta name=\"description\" content=\"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.\" \/>\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-nat-is-the-killer-app-for-ipv6\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"IPv4 NAT is the Killer App for IPv6\" \/>\n<meta property=\"og:description\" content=\"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2012-02-06T19:14:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:31:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.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=\"Cricket Liu\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Cricket Liu\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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-nat-is-the-killer-app-for-ipv6\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/\"},\"author\":{\"name\":\"Cricket Liu\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/bb6b62b1b99a7cbcd7c528d5763778d5\"},\"headline\":\"IPv4 NAT is the Killer App for IPv6\",\"datePublished\":\"2012-02-06T19:14:35+00:00\",\"dateModified\":\"2020-05-06T17:31:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/\"},\"wordCount\":1207,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"keywords\":[\"Infoblox\",\"IPv4\",\"IPv6\",\"Security\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/\",\"name\":\"IPv4 NAT is the Killer App for IPv6\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"datePublished\":\"2012-02-06T19:14:35+00:00\",\"dateModified\":\"2020-05-06T17:31:43+00:00\",\"description\":\"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"width\":660,\"height\":454,\"caption\":\"The IPv6 Tipping Point Effect\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv4-nat-is-the-killer-app-for-ipv6\\\/#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 NAT is the Killer App for IPv6\"}]},{\"@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\\\/bb6b62b1b99a7cbcd7c528d5763778d5\",\"name\":\"Cricket Liu\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/cricket-new-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/cricket-new-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/cricket-new-96x96.jpg\",\"caption\":\"Cricket Liu\"},\"description\":\"Cricket is one of the world\u2019s leading experts on the Domain Name System (DNS) and serves as the liaison between Infoblox and the DNS community. Before joining Infoblox, he founded an internet consulting and training company, Acme Byte &amp; Wire, after running the hp.com domain at Hewlett-Packard. Cricket is a prolific speaker and author, having written a number of books including \u201cDNS and BIND,\u201d one of the most widely used references in the field, now in its fifth edition.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/cricket-liu\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"IPv4 NAT is the Killer App for IPv6","description":"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.","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-nat-is-the-killer-app-for-ipv6\/","og_locale":"en_US","og_type":"article","og_title":"IPv4 NAT is the Killer App for IPv6","og_description":"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/","og_site_name":"Infoblox Blog","article_published_time":"2012-02-06T19:14:35+00:00","article_modified_time":"2020-05-06T17:31:43+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","type":"image\/jpeg"}],"author":"Cricket Liu","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Cricket Liu","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/"},"author":{"name":"Cricket Liu","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/bb6b62b1b99a7cbcd7c528d5763778d5"},"headline":"IPv4 NAT is the Killer App for IPv6","datePublished":"2012-02-06T19:14:35+00:00","dateModified":"2020-05-06T17:31:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/"},"wordCount":1207,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","keywords":["Infoblox","IPv4","IPv6","Security"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/","name":"IPv4 NAT is the Killer App for IPv6","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","datePublished":"2012-02-06T19:14:35+00:00","dateModified":"2020-05-06T17:31:43+00:00","description":"Another guest posting from\u00a0Scott Hogg\u00a0of our Technical Advisory Board.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","width":660,"height":454,"caption":"The IPv6 Tipping Point Effect"},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv4-nat-is-the-killer-app-for-ipv6\/#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 NAT is the Killer App for IPv6"}]},{"@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\/bb6b62b1b99a7cbcd7c528d5763778d5","name":"Cricket Liu","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/cricket-new-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/cricket-new-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/cricket-new-96x96.jpg","caption":"Cricket Liu"},"description":"Cricket is one of the world\u2019s leading experts on the Domain Name System (DNS) and serves as the liaison between Infoblox and the DNS community. Before joining Infoblox, he founded an internet consulting and training company, Acme Byte &amp; Wire, after running the hp.com domain at Hewlett-Packard. Cricket is a prolific speaker and author, having written a number of books including \u201cDNS and BIND,\u201d one of the most widely used references in the field, now in its fifth edition.","url":"https:\/\/www.infoblox.com\/blog\/author\/cricket-liu\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/4591","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\/178"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=4591"}],"version-history":[{"count":1,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/4591\/revisions"}],"predecessor-version":[{"id":4592,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/4591\/revisions\/4592"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/3187"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=4591"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=4591"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=4591"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}