{"id":5977,"date":"2021-02-03T10:45:28","date_gmt":"2021-02-03T18:45:28","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=5977"},"modified":"2021-02-03T10:45:28","modified_gmt":"2021-02-03T18:45:28","slug":"lessons-learned-recommendations-from-ipv6-only-deployments-part-two","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/","title":{"rendered":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two"},"content":{"rendered":"

In part one<\/a> we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.<\/p>\n

In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.<\/p>\n

LinkedIn\u2019s Goal to Remove IPv4<\/strong><\/h3>\n

Most readers are familiar with the professional networking company LinkedIn.\u00a0 They currently have over 700 million registered members from 150 countries.\u00a0 Serving their user base takes a significant amount of compute capacity, and LinkedIn operates its own datacenters in multiple U.S. locations (as well as one overseas).\u00a0 At the 2017 North American IPv6 Task Force Summit (coincidentally hosted by LinkedIn), Franck Martin, Chairman of LinkedIn\u2019s IPv6 in the Datacenter Working Group, made a splash by announcing their intention to build an IPv6-only datacenter. \u00a0I recently caught up with Franck to get an update on LinkedIn\u2019s IPv6 activities.<\/p>\n

First, some background on LinkedIn\u2019s network.\u00a0 They were a relatively early adopter of IPv6.\u00a0 Back in 2013, they enabled IPv6 on their email platform, and in 2014 they activated the protocol on their web servers. \u00a0The primary driver behind their dual-stack deployment was the forecasted depletion of their RFC 1918 address space.\u00a0 Another driver, however, was the added benefit that IPv6 was, in many cases, faster than IPv4.\u00a0 Since dual-stacking their website seven years ago, the amount of IPv6 traffic handled by LinkedIn has steadily increased to the point where it is currently the majority<\/a>.<\/p>\n

In 2017, Franck noted that LinkedIn\u2019s platform was dual stack on the front end but some of the back-end communication was still using IPv4.\u00a0 In the years since, their infrastructure has been fully upgraded to support IPv6.\u00a0 This work has created a solid platform for LinkedIn, as well as third-party applications used by partners, which now must support both IPv4 and IPv6.\u00a0 The ultimate goal of turning IPv4 off has not yet been achieved, but there has been significant progress adopting IPv6 nonetheless.<\/p>\n

It is also important to note that LinkedIn\u2019s network and compute priorities have evolved over the past few years.\u00a0 In 2016, they were acquired by Microsoft.\u00a0 Until recently, LinkedIn\u2019s network remained independent.\u00a0 In 2019, however, LinkedIn and Microsoft publicly announced a multi-year project to migrate their compute workloads to Azure.\u00a0 Franck\u2019s recent focus has been working with LinkedIn\u2019s parent company, Microsoft, to ensure that Azure provides a suitable dual-stack environment that can seamlessly communicate with the current LinkedIn datacenters.<\/p>\n

Even if some goals take longer than anticipated to achieve (turning IPv4 off for example), vision and leadership are still invaluable.\u00a0 Franck notes that because of their IPv6 implementation efforts, LinkedIn\u2019s network is in a much better position today than even a few years ago and is able to rapidly adapt and accommodate future requirements.\u00a0 He touts that being an early adopter has already paid dividends.\u00a0 When Apple announced in 2015 that IPv6 support will be required for all iOS 9 apps, LinkedIn was already in compliance:\u00a0 They required zero effort to meet the mandate.\u00a0 Vision and planning do have their benefits.<\/p>\n

Franck is always open to provide recommendations for other organizations deploying IPv6.\u00a0 He stresses that workforce training is key. \u00a0(See Ed Horley\u2019s post on Why an Investment in IPv6 Training Will Pay Off<\/a>.)\u00a0 And not just the network group.\u00a0 Franck refers to three towers: hardware, software, and network, all of which need to be included in training and implementation efforts.\u00a0 Involvement is also needed from the security team to account for IPv6 in their practices and testing.<\/p>\n

He recommends working with vendors early in the IPv6 planning process.\u00a0 LinkedIn is a large company with significant influence, but this point is still valid for smaller organizations.\u00a0 Also, a suitable lab or test environment is indispensable in ensuring proper functionality in your environment, regardless of vendor feature claims.\u00a0 In other words, do not blindly trust vendors: test, assess, and verify.<\/p>\n

Finally, be ready to adapt if priorities change.\u00a0 This was the case when LinkedIn announced plans to migrate from operating their own datacenters to using Microsoft Azure.<\/p>\n

Turning IPv4 off is still a goal of LinkedIn, and the current dual-stack environment is a step in that direction.\u00a0 Below is a summary of IPv6 benefits and lessons learned with recommendations from LinkedIn.<\/p>\n\n\n\n\n\n\n\n\n\n
IPv6 Lessons Learned and Recommendations<\/strong><\/td>\nIPv6 Benefits<\/strong><\/td>\n<\/tr>\n
Training is key\u2013including non-network silos that need to be involved in IPv6 deployment<\/td>\nIncreased performance<\/td>\n<\/tr>\n
Ensure the security team plans for and manages IPv6<\/td>\nElimination of layers of NAT (performance and simplicity)<\/td>\n<\/tr>\n
Do not blindly trust vendor claims of compliance: test, assess, and verify<\/td>\nPositions network to comply with external requirements \u2013 for example Apple\u2019s iOS 9 IPv6-only mandate<\/td>\n<\/tr>\n
Work with partners and\/or any parent companies on IPv6 readiness and integration<\/td>\nGlobally unique addresses do make integration much easier<\/td>\n<\/tr>\n
Be ready to adapt to changing priorities<\/td>\nFaster to market, less technical debt and effort<\/td>\n<\/tr>\n
Early adoption has its benefit \u2013 for example, after Apple\u2019s IPv6 mandate LinkedIn did not have to perform any work to comply with it<\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

T-Mobile\u2019s IPv6-only Wireless Network<\/strong><\/p>\n

During the 2017 North American IPv6 Task Force Summit, T-Mobile\u2019s Stephan Lagerholm gave an excellent presentation and demonstration of their IPv6-only subscriber network.\u00a0 This stood out from the other presentations at the event in that T-Mobile was not just talking about eliminating IPv4, they had already done it.\u00a0 It was a testament to the fact that mobile communications providers like T-Mobile, and their peers, have been leaders in IPv6 deployment.<\/p>\n

These companies realized years ago that limited public IPv4 and RFC 1918 addressing does not provide enough space to operate and grow their business.\u00a0 For this reason, cellular carriers are consistently at the top of the list for IPv6 adoption.\u00a0 A good resource to view the completeness of IPv6 deployment is https:\/\/www.worldipv6launch.org\/measurements\/<\/a>.\u00a0 This tool displays the percentage of traffic to major dual-stack sites from various BGP Autonomous Systems.\u00a0 Out of the 350 organizations tracked, T-Mobile tops the list (at the time of this writing \u2013 the values are fluid) with 94% IPv6 deployment.\u00a0 (The value was 84% back in 2017.)<\/p>\n

To get an update on T-Mobile\u2019s experience operating an IPv6-only network I caught up with Senior Engineer Ben Bittfield.\u00a0 Ben arrived at T-Mobile via Sprint after their merger last year, and he notes that both networks had a similar architecture.\u00a0 T-Mobile may have led the way in large-scale IPv6 deployments, but customers still needed access to the legacy Internet. \u00a0To support cases where applications are still relying on IPv4, T-Mobile utilizes a combination of NAT64 and 464XLAT<\/a>.\u00a0 Ben notes that it was a huge boon for the protocol when Apple mandated IPv6-only support for apps in iOS 9 and beyond.\u00a0 This move by the one of the primary smart device producers has helped cellular providers in leading IPv6 deployments in an environment where operating IPv4 at large scale has significant challenges.\u00a0 There are still legacy apps and devices in use requiring the workarounds outlined above, but over time their need will diminish thanks to IPv6\u2019s momentum in this industry.<\/p>\n

Mergers and acquisitions often force companies to struggle with addressing conflicts as networks get integrated after the dust settles.\u00a0 Ben notes, however, that it was a tremendous benefit for both Sprint and T-Mobile to have IPv6-only subscriber networks after their $26 billion merger.\u00a0 \u201cIt made integration 100 times easier.\u201d\u00a0 After such a major M&A<\/a> event, it is difficult to put an exact value on simply plugging together the revenue generating networks of two major carriers with little to no pain.\u00a0 From an operational perspective there is no renumbering, no NAT, no complications–just routing\u2026\u00a0 Priceless!<\/p>\n

From his vantage point operating in an IPv6-only environment, Ben offers the following advice for others in their IPv6 deployments.\u00a0 First, fix the root cause of problems.\u00a0 At this point NAT64 and 464XLAT are relatively solid and mature, but there are still instances when mobile applications get hung up.\u00a0 This often involves apps that carry IP information at higher layers in the OSI stack.\u00a0 Though it may be quicker to implement a workaround, Ben recommends taking the extra time to remedy the core of the issue.\u00a0 This often requires reaching out to the app developer and working through the obstacle.<\/p>\n

Like LinkedIn, he advocates working with key infrastructure vendors early in the planning process and to be sure to test their products.\u00a0 Deployment boundary cases can expose IPv6 bugs, and T-Mobile also noted that stress-testing equipment uncovered performance limitations.\u00a0 Eventually they were able to work with their partners to resolve these issues.\u00a0 But it was critical that these limitations were caught pre-production.<\/p>\n

Ben also recommends preparing for flexibility on IPv6 address planning.\u00a0 He cautions that the first draft of an address plan is not always perfect, and it may be necessary to adapt or get assistance in this effort.\u00a0 Finally, do not be afraid to make mistakes.\u00a0 Like any IT endeavor, mistakes will happen.\u00a0 Learn from them and move forward.<\/p>\n

Below is a summary of benefits and lessons learned with recommendations from a true leader in IPv6-only deployments.<\/p>\n\n\n\n\n\n\n\n
IPv6-Only Lessons Learned and Recommendations<\/strong><\/td>\nIPv6-only Benefits<\/strong><\/td>\n<\/tr>\n
Take the time to solve the root cause of problems\u2013resist the urge to implement workarounds<\/td>\nSimplicity of merger and acquisition network integration<\/td>\n<\/tr>\n
Work with key infrastructure vendors and test their platforms, including performance testing<\/td>\nScalability \u2013 the ability to operate a large, global network<\/td>\n<\/tr>\n
Be prepared to adapt<\/td>\nEarly adoption–better prepared for partner mandates (like Apple\u2019s IPv6-only requirement)<\/td>\n<\/tr>\n
Like in any IT initiative, mistakes will happen\u2013but don\u2019t be afraid to make them as long as progress is being made<\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/h3>\n

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

There has been a clear shift in industry thinking with respect to IPv6 implementation models from dual-stack to IPv6-only.\u00a0 Though many enterprises lag in IPv6 adoption, many other organizations have decided to forgo IPv4 altogether.\u00a0 For those willing to take this step, the recommendations and lessons learned from three pioneers in IPv6-only planning and deployment will assist in the journey.<\/p>\n

It is no surprise that Ungleich Glarus, LinkedIn and T-Mobile trumpet overlapping benefits and lessons learned.\u00a0 It is often easy to find roadblocks that discourage a network architecture transformation–such as migrating to an IPv6-only network.\u00a0 But these companies have found a path that overcomes hurdles and progresses toward their objectives.\u00a0 It is important to keep in mind that all major IT projects present challenges.\u00a0 But with the proper vision, guidance, and mindset, aided by the knowledge from those that have come before, your goal can be obtained.<\/p>\n

Though it may seem far-fetched today, most enterprises will eventually run into business drivers to adopt IPv6 and turn off IPv4.\u00a0 These may be noticeable immediately or they may take years or even decades to appear. \u00a0The process of moving to IPv6-only will most likely occur as a gradual evolution rather than a forklift upgrade and flag day.\u00a0 For example, datacenters and IoT environments may require IPv6-only long before it makes sense for corporate desktops and laptops.\u00a0 Regardless, it is good to start thinking about and planning for this future now.<\/p>\n

The table below summarizes the recommendations above.<\/p>\n\n\n\n\n\n\n\n\n\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>\nReduced network complexity<\/td>\n<\/tr>\n
Find workarounds to accommodate IPv4 if necessary<\/td>\nCan enable service providers to offer a less expensive service<\/td>\n<\/tr>\n
Do not get bogged down in legacy software and tools\u2013if 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
Work with vendors and persuade them to support IPv6 if there are gaps<\/td>\nIncreased performance<\/td>\n<\/tr>\n
Do not be afraid to tinker with open source code and fix bugs<\/td>\nPositions network to comply with external requirements<\/td>\n<\/tr>\n
Training is key\u2013including non-network silos that need to be involved in IPv6 deployment<\/td>\nGlobally unique addresses do make integration much easier<\/td>\n<\/tr>\n
Ensure the security team plans for and manages IPv6<\/td>\nFaster to market, less technical debt and effort<\/td>\n<\/tr>\n
Do not blindly trust vendor compliance:\u00a0 test, assess, and verify (functionality and performance)<\/td>\nMerger and acquisition network integration simplicity<\/td>\n<\/tr>\n
Be prepared to adapt<\/td>\n <\/td>\n<\/tr>\n
Work with partners and and\/or parent company on IPv6 readiness and integration<\/td>\n <\/td>\n<\/tr>\n
Be ready to adapt to changing priorities<\/td>\n <\/td>\n<\/tr>\n
Take the time to solve the root cause of the problem<\/td>\n <\/td>\n<\/tr>\n
Like any IT initiative mistakes will happen\u2013but don\u2019t be afraid to make them as long as progress is being made<\/td>\n <\/td>\n<\/tr>\n
IPv6 brings the fun back to networking<\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Learning from others who have come before will assist you in your IPv6-only implementation effort.\u00a0 Won\u2019t it be nice to one day disable IPv4 and operate in a much simpler, secure and more scalable IPv6-only world?<\/p>\n","protected":false},"excerpt":{"rendered":"

In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey. In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and […]<\/p>\n","protected":false},"author":351,"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":[38,410],"class_list":{"0":"post-5977","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-only","10":"entry"},"acf":[],"yoast_head":"\nLessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two<\/title>\n<meta name=\"description\" content=\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.\" \/>\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-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 Two\" \/>\n<meta property=\"og:description\" content=\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-02-03T18:45:28+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=\"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=\"11 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-two\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/\"},\"author\":{\"name\":\"Cody Christman\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/467b05606b1887c11ca4576261e71c8a\"},\"headline\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two\",\"datePublished\":\"2021-02-03T18:45:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/\"},\"wordCount\":2182,\"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-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"keywords\":[\"IPv6\",\"IPv6-only\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/\",\"name\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part 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-two\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"datePublished\":\"2021-02-03T18:45:28+00:00\",\"description\":\"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\\\/#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\\\/lessons-learned-recommendations-from-ipv6-only-deployments-part-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 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 Two","description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.","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-two\/","og_locale":"en_US","og_type":"article","og_title":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two","og_description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/","og_site_name":"Infoblox Blog","article_published_time":"2021-02-03T18:45:28+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","type":"image\/jpeg"}],"author":"Cody Christman","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Cody Christman","Est. reading time":"11 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-two\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/"},"author":{"name":"Cody Christman","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/467b05606b1887c11ca4576261e71c8a"},"headline":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two","datePublished":"2021-02-03T18:45:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/"},"wordCount":2182,"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-two\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","keywords":["IPv6","IPv6-only"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/","name":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part 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-two\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","datePublished":"2021-02-03T18:45:28+00:00","description":"Lessons Learned & Recommendations from IPv6-only Deployments \u2013 Part Two. In part one we discussed the background related to the industry momentum around going IPv6-only.\u00a0 We also received some sage advice from Ungleich Glarus CEO, Nico Schottelius, and covered his lessons learned in their IPv6-only journey.\u00a0In part two, we will continue the dialogue with two other leaders in the industry, LinkedIn and T-Mobile, and summarize what all of this can do for you in your IPv6 transition.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/lessons-learned-recommendations-from-ipv6-only-deployments-part-two\/#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\/lessons-learned-recommendations-from-ipv6-only-deployments-part-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 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\/5977","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=5977"}],"version-history":[{"count":2,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5977\/revisions"}],"predecessor-version":[{"id":5979,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5977\/revisions\/5979"}],"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=5977"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=5977"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=5977"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}