{"id":5869,"date":"2021-01-19T08:52:07","date_gmt":"2021-01-19T16:52:07","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=5869"},"modified":"2021-01-19T08:52:07","modified_gmt":"2021-01-19T16:52:07","slug":"lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/","title":{"rendered":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)"},"content":{"rendered":"

Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you<\/em> ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?<\/p>\n

In 2017 I published a whitepaper that focused on the rather new trend (at the time) of deploying IPv6-only networks (https:\/\/www.linkedin.com\/pulse\/ipv6-deployment-evolution-ipv6-only-networks-cody-christman\/<\/a>). \u00a0I will look back to that article in this blog and follow up with pioneers in this space to uncover how their efforts have progressed over the past few years–especially now that they have greater operational experience in their undertaking. \u00a0I recently met with T-Mobile, LinkedIn, and Ungleich Glarus AG to discuss lessons learned and best practices from their deployments, which will ultimately assist you in your efforts if (and when) you choose to follow in their footsteps.<\/p>\n

Background<\/strong><\/h3>\n

In April of 2017, the North American IPv6 Task Force held a summit hosted by LinkedIn at their Sunnyvale, California campus.\u00a0 It featured two days of renowned speakers and panelists and an eager crowd of network enthusiasts.\u00a0 As the conference progressed, a clear pattern in the content started to emerge.\u00a0 Numerous presenters were discussing how their companies were rolling out, or had already deployed, IPv6-only networks.\u00a0 This included Cisco, LinkedIn, Microsoft, and T-Mobile.\u00a0 It was clear there was a shift in industry thinking with respect to IPv6 implementation models from dual-stack to IPv6-only.\u00a0 This prompted me to author the 2017 whitepaper, which summarized this topic for those who weren\u2019t able to attend the conference in person.<\/p>\n

The whitepaper pointed out that certain industry segments had been driving IPv6 adoption, which includes mobile\/cellular carriers, broadband service providers, large multinationals, and social media companies.\u00a0 The business drivers varied, but typically revolved around performance, scalability, simplicity, and address scarcity.<\/p>\n

This proliferation of IPv6 adoption led to the evolution of transition and deployment models.\u00a0 In the late 1990s, IPv6 existed in pockets and tunneling was widely deployed to interconnect network islands.\u00a0 In the early 2000s, service providers started to support IPv6 for transport, which enabled new IPv6 deployment scenarios.\u00a0 Thereafter, industry experts recommended the following approach, \u201cdual stack where you can, tunnel where you must<\/a>.\u201d\u00a0 Given the present state of adoption and lessons learned, expert opinion has morphed.\u00a0 The current consensus, which came up several times during the Sunnyvale conference, is \u201cIPv6-only where you can, dual stack where you must.\u201d<\/p>\n

At that time, the percentage of IPv6 traffic on the US Internet, as measured by Google, was just over 33%.\u00a0 (It currently exceeds 44%.)\u00a0 Though this value is significant, the percentage of IPv6 traffic transmitted and received by dual-stack hosts is significantly greater.\u00a0 Mobile carriers and broadband providers consistently report that in excess of 70% of their traffic to dual stack endpoints flows over IPv6.\u00a0 (In this case, \u201cdual-stack\u201d may also include IPv6-only endpoints that can reach IPv4 content via DNS64-NAT64<\/a>.)\u00a0 There are multiple reasons for the preponderance of IPv6 traffic.\u00a0 First, dual-stack endpoints by default prefer IPv6 content over IPv4.\u00a0 Second, from the content side, the majority of top U.S. and global web sites support IPv6.\u00a0 Another way to interpret Google and carrier metrics is that legacy IPv4-only endpoints are still holding down global IPv6 traffic averages.<\/p>\n

This shift represented a turning point in network architecture thinking.\u00a0 The whitepaper made a case for IPv6-only networks and concluded with a list of tradeoffs as well as practical recommendations for organizations deploying them.<\/p>\n

Fast Forward to Today\u2026<\/strong><\/h3>\n

So, what can be learned from these early IPv6-only deployments? \u00a0Let\u2019s discuss best practices and lessons learned from the industry leaders that were some of the first to make the evolutionary step.<\/p>\n

Ungleich Glarus and their IPv6-only Datacenter Service<\/strong><\/h3>\n

The Swiss company Ungleich Glarus AG (Ungleich is German for \u201cunequaled\u201d and Glarus is the canton\/region where they are located) is a Platform as a Service (PaaS) provider that has been a trailblazer in IPv6 deployments.\u00a0 They offer dual-stack and IPv6-only services out of their alpine datacenter, but their flagship is their native IPv6 product<\/a>. \u00a0In general, Ungleich provides a platform, for example NodeJS, Django or Ruby on Rails, and their customers develop and manage applications leveraging these tools.\u00a0\u00a0 As noted, they offer dual-stack and IPv6-only services.\u00a0 However, the cost for their dual-stack platform is higher, reflecting the added expense needed to include IPv4 on those servers.<\/p>\n

I recently met with CEO Nico Schottelius, who was kind enough to provide some background on their offering and supply recommendations for others deploying IPv6.<\/p>\n

Originally, Ungleich Glarus was a Linux consulting company that was agnostic to the hosting platform used by their customers. \u00a0Nico noted that in 2016, however, they decided to broaden their portfolio and build their own datacenter.\u00a0 As with any major undertaking, architectural decisions were required based on tradeoffs, including their IP framework.\u00a0 Ungleich ultimately decided to focus on IPv6 rather than IPv4.\u00a0 The two primary drivers for deploying IPv6 were address scarcity and sustainability.\u00a0 RIPE had already depleted their free pool and Nico\u2019s company only had 4,000 public IPv4 addresses at their disposal – not enough for any significant future growth.\u00a0 When asked about purchasing IPv4 addresses on the gray market, Nico noted such a practice would increase their cost of doing business, and ultimately not be sustainable.<\/p>\n

Sustainability is an important principle not only for Nico and his company, but also for their client base, which tends to be environmentally conscious.\u00a0 In this case, IP address sustainability coexists with other environmentally friendly practices.\u00a0 Their datacenter is fully powered by renewable energy.\u00a0 And to minimize power consumption, servers are sparsely deployed at four square meters (43 square feet) per device. \u00a0This low density is made possible because Ungleich reused a large, defunct textile factory for their datacenter, leaving plenty of room to spread servers out.\u00a0 From a green perspective, this design eliminates the need for energy consuming cooling facilities.\u00a0 Thus, a sustainably powered datacenter along with a sustainable Internet protocol.<\/p>\n

As with any network design there can be challenges and building an IPv6-only datacenter is no exception.\u00a0 Per Nico, their product attracts an innovative client base and early adopters.\u00a0 Though IPv6 is suitable for most needs, some customers have requested access to their IPv6-only hosts from the legacy Internet.\u00a0 To accommodate these use cases, HAproxy, an open source, high-availability server load balancer, and NAT64 were implemented to allow IPv4 communication with IPv6-only hosts.<\/p>\n

Other hurdles needed to be overcome around tooling.\u00a0 For example, it is known that FTP does not work well through NAT64.\u00a0 Instead of trying to implement an ALG to coax FTP to function, Nico simply recommends SFTP, which is a superior tool that works seamlessly in this environment.\u00a0 A simple workaround that includes a security upgrade!<\/p>\n

Some tools like the web hosting management portal Ungleich was using supported IPv6, but not natively.\u00a0\u00a0 (It still required IPv4 in some areas.)\u00a0 So Ungleich looked into another platform that performed the same function but did not require IPv4 to operate.\u00a0 Nico states, \u201cDon\u2019t get bogged down in legacy software and tools–if a required application does not support native IPv6, find a modern replacement.\u201d\u00a0 This is an example of yet another way to circumvent an IPv6 support problem.<\/p>\n

Nico notes that time has mended some of their problems.\u00a0 For example, NodeJS and Kubernetes–originally deficient in IPv6–now have better IPv6 support.\u00a0 And if other open source projects lack compatibility, he and his team are not afraid to dig into their code and hack around to make them work.\u00a0 He pointed out that the Germans and Swiss have a penchant for tinkering.\u00a0 It is obvious talking to Nico that he is passionate about IPv6 despite periodic challenges.\u00a0 He states, \u201cRunning an IPv6-only business brings the fun back to networking.\u201d<\/p>\n

Below is a summary of IPv6-only benefits and lessons learned with recommendations from Ungleich Glarus.<\/p>\n\n\n\n\n\n\n\n\n\n
IPv6-Only Lessons Learned and Recommendations<\/strong><\/td>\nIPv6-Only Benefits<\/strong><\/td>\n<\/tr>\n
Focus on IPv6 because IPv4 deployments are neither scalable nor sustainable<\/td>\nNetwork complexity significantly reduced<\/td>\n<\/tr>\n
Find a work around when needed–for example, if FTP does not work across NAT64, use SFTP<\/td>\nAllows Ungleich Glarus to offer a less expensive service<\/td>\n<\/tr>\n
Do not get bogged down in legacy software and tools–if a required application does not support native IPv6, find a modern replacement<\/td>\nScalability and sustainability<\/td>\n<\/tr>\n
Time mends problems\u2013IPv6-only in 2021 is easier than 2016 and 2025 will be better than 2021<\/td>\nThis is where the Internet is going; you are ready for the future today<\/td>\n<\/tr>\n
Do not be afraid to tinker with open source code and fix bugs<\/td>\n<\/td>\n<\/tr>\n
IPv6 brings the fun back to networking<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

That\u2019s it for part one.\u00a0 Next time we will get additional insight from LinkedIn and T-Mobile, and tie all of this information together.\u00a0 Thanks for reading and stay tuned!<\/p>\n","protected":false},"excerpt":{"rendered":"

Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been […]<\/p>\n","protected":false},"author":351,"featured_media":3730,"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,170,56,410,411],"class_list":{"0":"post-5869","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-ipv6","9":"tag-ipv6-address-planning","10":"tag-ipv4","11":"tag-ipv6-only","12":"tag-dual-stack","13":"entry"},"acf":[],"yoast_head":"\nLessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)<\/title>\n<meta name=\"description\" content=\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0\" \/>\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\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)\" \/>\n<meta property=\"og:description\" content=\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-19T16:52:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"302\" \/>\n\t<meta property=\"og:image:height\" content=\"227\" \/>\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=\"8 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\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/\"},\"author\":{\"name\":\"Cody Christman\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/467b05606b1887c11ca4576261e71c8a\"},\"headline\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)\",\"datePublished\":\"2021-01-19T16:52:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/\"},\"wordCount\":1523,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/1409954267002-Volleyball-ipv6.jpg\",\"keywords\":[\"IPv6\",\"IPv6 address planning\",\"IPv4\",\"IPv6-only\",\"Dual Stack\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/\",\"name\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/1409954267002-Volleyball-ipv6.jpg\",\"datePublished\":\"2021-01-19T16:52:07+00:00\",\"description\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/1409954267002-Volleyball-ipv6.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/1409954267002-Volleyball-ipv6.jpg\",\"width\":302,\"height\":227,\"caption\":\"IPv4 with nothing but a volleyball for a friend\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\\\/#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\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)\"}]},{\"@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":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)","description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0","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\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/","og_locale":"en_US","og_type":"article","og_title":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)","og_description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/","og_site_name":"Infoblox Blog","article_published_time":"2021-01-19T16:52:07+00:00","og_image":[{"width":302,"height":227,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg","type":"image\/jpeg"}],"author":"Cody Christman","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Cody Christman","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/"},"author":{"name":"Cody Christman","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/467b05606b1887c11ca4576261e71c8a"},"headline":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)","datePublished":"2021-01-19T16:52:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/"},"wordCount":1523,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg","keywords":["IPv6","IPv6 address planning","IPv4","IPv6-only","Dual Stack"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/","name":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg","datePublished":"2021-01-19T16:52:07+00:00","description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two). Wouldn\u2019t it be nice to only have one Internet Protocol in your campus or datacenter to operate?\u00a0 Eschewing IPv4 for an IPv6-only network achieves this goal and brings the promise of simplicity, scalability, and a greatly reduced security surface\u2014not to mention possible performance benefits.\u00a0\u00a0 This is exactly what many leaders in the industry have been doing.\u00a0 They are deploying IPv6-only networks.\u00a0 But are you ready to take this step?\u00a0 And if so, what are the recommendations from early adopters?\u00a0\u00a0","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/1409954267002-Volleyball-ipv6.jpg","width":302,"height":227,"caption":"IPv4 with nothing but a volleyball for a friend"},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-one-of-two\/#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":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part One (of Two)"}]},{"@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\/5869","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=5869"}],"version-history":[{"count":2,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5869\/revisions"}],"predecessor-version":[{"id":5872,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5869\/revisions\/5872"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/3730"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=5869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=5869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=5869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}