{"id":3400,"date":"2014-07-22T08:28:48","date_gmt":"2014-07-22T08:28:48","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=3400"},"modified":"2020-05-06T10:31:34","modified_gmt":"2020-05-06T17:31:34","slug":"making-a-new-product-make-it-dual-protocol","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/","title":{"rendered":"Making a New Product?  Make it Dual Protocol!"},"content":{"rendered":"<p>Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.\u00a0 However, they RTM their software with an already obsolete feature-set. But the cost to change these products later in the development cycle will be higher than simply introducing the product with IPv6 capabilities right from the start. Meanwhile, the rate of adoption of IPv6 continues to accelerate.<\/p>\n<p>For example, IPv6 is continuing to\u00a0<a href=\"https:\/\/community.infoblox.com\/blogs\/2014\/01\/07\/ipv6-was-year-was\" target=\"_blank\" rel=\"noopener noreferrer\">gain steam<\/a>\u00a0and the statistics on the amount of IPv6 packets traversing the Internet continues to rise.\u00a0 Just a couple of years ago Google was only observing a fraction of one percent of IPv6 traffic.\u00a0 In the last 18 months, their amount of IPv6 traffic has gone from 1% to 4% of their<a href=\"https:\/\/www.google.com\/intl\/en\/ipv6\/statistics.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\u00a0total traffic volume<\/a>.\u00a0 Cisco\u2019s\u00a0<a href=\"http:\/\/6lab.cisco.com\/stats\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">6Lab site<\/a>\u00a0shows more green and darker green areas than just a year ago.\u00a0 Many\u00a0<a href=\"http:\/\/www.pcworld.com\/article\/2375220\/ipv6-usage-is-climbing-in-europe-while-asian-countries-are-most-ready-for-4k-tv-says-study.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">European<\/a>\u00a0countries like Belgium are experiencing climbing IPv6 traffic volumes.\u00a0\u00a0<a href=\"http:\/\/www.comcast6.net\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Comcast\u2019s<\/a>\u00a0IPv6 deployment is now reaching well over 20% and\u00a0<a href=\"http:\/\/www.internetsociety.org\/deploy360\/blog\/2014\/02\/new-ipv6-measurements-comcast-nearing-25-verizon-wireless-46-dt-at-18\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Verizon Wireless<\/a>\u00a0is approximately 50%.<\/p>\n<p>It is important to realize that for every Facebook page that is served up over IPv6, it means that there is one less Facebook page that must be served up over IPv4.\u00a0 My personal prediction is that in just a couple of years we will reach the tipping point and the rate of rise in IPv6 traffic will be nearly vertical.\u00a0 The aggregate traffic volume will continue to rise; no one ever uses less bandwidth.\u00a0 It is only the relative percentage of mix of IPv4 and IPv6 that will vary over time.\u00a0 IPv4 traffic volumes will continue to rise until the tipping point, when more connections will prefer IPv6.\u00a0 Eventually, the use of IPv4 will taper off, though IPv4 systems will be with us for decades.\u00a0 Following is a very basic diagram illustrating this concept.<\/p>\n<p>As early as 2003 many U.S. Federal government agencies drafted\u00a0<a class=\" bf_ungated_init\" href=\"http:\/\/www.defense.gov\/news\/Jun2003\/d20030609nii.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">procurement guidelines<\/a>\u00a0mandating that they prefer products that supported IPv6.\u00a0 This policy was formally adopted in the\u00a0<a href=\"https:\/\/acquisition.gov\/far\/current\/html\/Subpart%2011_1.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Federal Acquisition Regulation<\/a>\u00a0(FAR) 11.002(g).\u00a0 This was a great idea at the time to help position IPv6 in federal organizations and help manufacturers prioritize IPv6 on their product roadmaps.\u00a0 If a federal organization had an 8-year information technology refresh cycle and they stopped buying IPv4-only products in 2004 and started buying dual-protocol capable products, then by 2012 all their networks, computers and software would support IPv6.\u00a0 The idea was that if you waited long enough, eventually all the IT products in their environments would support IPv6.\u00a0 The plan was not to try to enable IPv6 right way, but to wait until some point when the federal government organizations would be able to enable IPv6 on their own timetable.\u00a0 The reality is that many federal organizations and many commercial enterprises continue to unknowingly purchase IPv4-only products.<\/p>\n<p>Many manufacturers and cloud providers are releasing products (and APIs) that are only configurable with IPv4 addresses.\u00a0 In 2014, it is disappointing to be seeing some new products introduced that do not have dual-protocol capability.\u00a0 These new IPv4-only products are in a class of products in the highly competitive areas of cloud management, software defined networking, and IT automation and orchestration software.\u00a0 Because of the high level of competition in these markets, the vendors are trying to come out with new features rapidly that appeal to the majority of use cases.\u00a0 Since virtually all organizations use IPv4 today, that is the only protocol these companies are concerning themselves with at the moment.<\/p>\n<p>The types of products that seem to be launched without any IPv6 support include:<\/p>\n<ul>\n<li>IaaS Cloud Services Management Interfaces \u2013 Many cloud providers offer only virtual compute systems using IPv4 networking<\/li>\n<li>PaaS and SaaS managed services \u2013 Some of these platforms and applications are only reachable over the IPv4 Internet<\/li>\n<li>Cloud Automation and Orchestration Software \u2013 Many of these products offer no way to have these systems mange other IPv6-enabled cloud or data center infrastructure<\/li>\n<li>Software Defined Networking Controllers and APIs \u2013 Some of these products only allow configuration of IPv4 forwarding via their southbound protocols, and their northbound protocols are only concerned with IPv4<\/li>\n<\/ul>\n<p>There are products in these market segments that do support dual-protocol.\u00a0 Organizations who are preparing for a purchase are encouraged to ask the vendors what level of IPv6 capability they have in their products.\u00a0 It behooves the consumer to be informed and fully understand where the product may not have full IPv4 to IPv6 feature parity.<\/p>\n<p>Here is a list of some of the IPv6-capable products in the above-mentioned categories:<\/p>\n<ul>\n<li><a class=\" bf_ungated_init\" href=\"https:\/\/www.opennetworking.org\/images\/stories\/downloads\/sdn-resources\/onf-specifications\/openflow\/openflow-spec-v1.3.0.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">OpenFlow<\/a>\u00a0version 1.3<\/li>\n<li>OpenDaylight with\u00a0<a href=\"https:\/\/wiki.opendaylight.org\/view\/Editing_OpenDaylight_OpenFlow_Plugin:End_to_End_Flows:Example_Flows\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">OpenFlow Plugin<\/a><\/li>\n<li>OpenStack\u00a0<a class=\" bf_ungated_init\" href=\"http:\/\/www.nephos6.com\/pdf\/OpenStack-on-IPv6.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Grizzly<\/a>,\u00a0<a class=\" bf_ungated_init\" href=\"http:\/\/www.nephos6.com\/pdf\/OpenStack-Havana-on-IPv6.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Havana<\/a>,\u00a0<a href=\"http:\/\/www.slideshare.net\/shixiongshang1\/openstack-icehouse-on-ipv6\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Icehouse<\/a><\/li>\n<li>AWS with\u00a0<a href=\"http:\/\/docs.aws.amazon.com\/ElasticLoadBalancing\/latest\/DeveloperGuide\/using-elb-ipv6.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Elastic Load Balancing<\/a><\/li>\n<li>Rackspace\u00a0<a href=\"http:\/\/www.rackspace.com\/blog\/cloud-load-balancers-and-support-for-ipv6-now-available-globally\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Cloud Load Balancers<\/a><\/li>\n<li>VMware\u00a0<a href=\"http:\/\/blogs.vmware.com\/management\/2013\/05\/using-vcloud-automation-center-with-infoblox-ipam.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">vCloud Automation Center with Infoblox IPAM<\/a><\/li>\n<li>Infoblox\u00a0<a href=\"http:\/\/www.infoblox.com\/solutions\/service-providers\/cloud-service-providers?utm_source=blox-community&amp;utm_campaign=community-q2&amp;utm_medium=blox-community\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Network Automation for Hosting and Cloud<\/a>\u00a0and<a href=\"http:\/\/www.infoblox.com\/products\/ip-address-management\/vmware?utm_source=blox-community&amp;utm_campaign=community-q2&amp;utm_medium=blox-community\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\u00a0IPAM for VMware<\/a><\/li>\n<li><a class=\" bf_ungated_init\" href=\"http:\/\/www.bluelock.com\/wp-content\/uploads\/2011\/11\/Bluelock_Datasheet_EnterpriseDatacenterConnectivity_v2.1.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Bluelock<\/a><\/li>\n<li>Brightbox\u00a0<a href=\"http:\/\/brightbox.com\/blog\/2012\/01\/11\/ipv6-servers\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Cloud Servers<\/a><\/li>\n<li>Linode\u00a0<a href=\"https:\/\/blog.linode.com\/2012\/02\/28\/native-ipv6-now-available-in-all-locations\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">NodeBalancers<\/a><\/li>\n<li>CloudFlare\u00a0<a href=\"http:\/\/blog.cloudflare.com\/introducing-cloudflares-automatic-ipv6-gatewa\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Automatic IPv6 Gateway<\/a><\/li>\n<li>Cisco\u00a0<a href=\"https:\/\/communities.cisco.com\/community\/technology\/datacenter\/ucs_management\/blog\/2013\/12\/18\/ucs-manager-221-el-capitan-released\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">UCS Manager 2.2(1)<\/a><\/li>\n<li>Embrane\u00a0<a href=\"http:\/\/support.embrane.com\/index.php?\/News\/List\/Index\/0\/6\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">heleos 2.2.1<\/a><\/li>\n<li>MuleSoft<a href=\"http:\/\/forum.mulesoft.org\/mulesoft\/topics\/how_to_make_a_mule_http_component_listen_to_an_local_ipv6_configured_interface_on_linux_box\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\u00a0iPaaS software<\/a><\/li>\n<\/ul>\n<p>It seems strange that some enterprise-grade cloud management products do not come with IPv6 capabilities, yet\u00a0<a href=\"https:\/\/community.infoblox.com\/blogs\/2014\/04\/01\/coming-soon-ipv6-only-facebook\" target=\"_blank\" rel=\"noopener noreferrer\">Facebook<\/a>\u00a0is already contemplating a world where they would only use IPv6 and disable IPv4.\u00a0 There was discussion at\u00a0<a class=\" bf_ungated_init\" href=\"https:\/\/ripe64.ripe.net\/presentations\/67-20120417-RIPE64-The_Case_for_IPv6_Only_Data_Centres.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RIPE 64<\/a>\u00a0about the topic of IPv6 only data centers.\u00a0 The Internet Society (<a href=\"http:\/\/www.internetsociety.org\/deploy360\/blog\/2012\/02\/slides-the-case-for-ipv6-only-data-centers\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">ISOC<\/a>) has also covered this topic and it was mentioned at the\u00a0<a class=\" bf_ungated_init\" href=\"http:\/\/fud.no\/talks\/20120209-V6_World_Congress_2012-The_Case_for_IPv6_Only_Data_Centres.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">V6 World Congress 2012<\/a>.<\/p>\n<p>It is easier to design a piece of software to be dual-protocol as that software is being initially developed.\u00a0 The cost to change an IT product to be dual-protocol after the product is designed takes more effort than if IPv6 would have been built into the product right from the start.\u00a0 We are not talking about an insurmountable amount of effort, but the further down the road you get, it will likely add up to be more work to make your system work in a fully dual-protocol environment.<\/p>\n<p>There is a list of the \u201c<a href=\"http:\/\/www.networkworld.com\/article\/2228323\/cisco-subnet\/top-10-tasks-for-ipv6-application-developers.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Top 10 Tasks for IPv6 Application Developers<\/a>\u201d that goes over some of the ideas you must keep in mind when you are making a dual-protocol software system.\u00a0 It may actually be quite difficult to make an IPv4-only system because so many of the software development environments and modern programming languages really assist developers in writing dual-protocol code.\u00a0 If you have an IPv4-only piece of code, then you will need to go back through your code and determine which modules, functions, objects, methods, and data structures have IPv4-only syntax.\u00a0 You will need to check for applications that input, store, or output IP addresses and\/or DNS names, and check those applications that are making socket connections (<a href=\"http:\/\/tools.ietf.org\/html\/rfc3493\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 3493<\/a>).\u00a0 You need to handle dual-protocol DNS queries and take into account\u00a0<a href=\"http:\/\/tools.ietf.org\/html\/rfc6555\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 6555<\/a>\u00a0Happy Eyeballs.\u00a0 You must allocate the proper amount of memory to hold an IPv6 address.\u00a0 Your code should also properly handle Path MTU Discovery (PMTUD) (<a href=\"http:\/\/tools.ietf.org\/html\/rfc1981\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 1981<\/a>).<\/p>\n<p><strong>The Bottom Line:<\/strong><\/p>\n<p>If you are a company that makes an IT product then you should build it in such a way that it would support both IP address families: IPv4 and IPv6.\u00a0 You should make your product dual-protocol right from the start or you may pay the consequences later.<\/p>\n<p>If you are a company that has internally developed software, you should be building it so it works in both an IPv4-only, dual-protocol, and IPv6-only environment.\u00a0 Even if your environment is predominantly IPv4 today, you should make sure the application will soon support dual-protocol networks.<\/p>\n<p>If you are a consumer of IT products, then you should look for products with support for both protocols.\u00a0 That will put your organization in the most advantageous position to enable IPv6 when you want to, without having to do a major upgrade to gain IPv6 support.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.\u00a0 However, they RTM their software with an already obsolete feature-set. But the cost to change these products later [&hellip;]<\/p>\n","protected":false},"author":321,"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,15],"class_list":{"0":"post-3400","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-security","10":"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>Making a New Product? Make it Dual Protocol!<\/title>\n<meta name=\"description\" content=\"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.\" \/>\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\/making-a-new-product-make-it-dual-protocol\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Making a New Product? Make it Dual Protocol!\" \/>\n<meta property=\"og:description\" content=\"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2014-07-22T08:28:48+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:31:34+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=\"Scott Hogg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Scott Hogg\" \/>\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\\\/making-a-new-product-make-it-dual-protocol\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/\"},\"author\":{\"name\":\"Scott Hogg\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/ee71ac61fe2ea349f6e991e628d22f4c\"},\"headline\":\"Making a New Product? Make it Dual Protocol!\",\"datePublished\":\"2014-07-22T08:28:48+00:00\",\"dateModified\":\"2020-05-06T17:31:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/\"},\"wordCount\":1285,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"keywords\":[\"Infoblox\",\"Security\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/\",\"name\":\"Making a New Product? Make it Dual Protocol!\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"datePublished\":\"2014-07-22T08:28:48+00:00\",\"dateModified\":\"2020-05-06T17:31:34+00:00\",\"description\":\"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/making-a-new-product-make-it-dual-protocol\\\/#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\\\/making-a-new-product-make-it-dual-protocol\\\/#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\":\"Making a New Product? Make it Dual Protocol!\"}]},{\"@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\\\/ee71ac61fe2ea349f6e991e628d22f4c\",\"name\":\"Scott Hogg\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"caption\":\"Scott Hogg\"},\"description\":\"Scott Hogg has 30 years of network and security experience and is president of Hogg Networking with. Scott Hogg specializes in teaching Internet Protocol version 6 (IPv6) and providing implementation guidance. Scott is CCIE #5133 (Emeritus) and CISSP #4610. Scott is Chair Emeritus of the Rocky Mountain IPv6 Task Force (RMv6TF), a member of the IPv6 Center of Excellence (COE), and co-author of the Cisco Press book on IPv6 Security.\",\"sameAs\":[\"https:\\\/\\\/hexabuild.io\"],\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/scott-hogg\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Making a New Product? Make it Dual Protocol!","description":"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.","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\/making-a-new-product-make-it-dual-protocol\/","og_locale":"en_US","og_type":"article","og_title":"Making a New Product? Make it Dual Protocol!","og_description":"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/","og_site_name":"Infoblox Blog","article_published_time":"2014-07-22T08:28:48+00:00","article_modified_time":"2020-05-06T17:31:34+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","type":"image\/jpeg"}],"author":"Scott Hogg","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Scott Hogg","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/"},"author":{"name":"Scott Hogg","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/ee71ac61fe2ea349f6e991e628d22f4c"},"headline":"Making a New Product? Make it Dual Protocol!","datePublished":"2014-07-22T08:28:48+00:00","dateModified":"2020-05-06T17:31:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/"},"wordCount":1285,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","keywords":["Infoblox","Security"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/","name":"Making a New Product? Make it Dual Protocol!","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","datePublished":"2014-07-22T08:28:48+00:00","dateModified":"2020-05-06T17:31:34+00:00","description":"Lately the IPv6 community has been witnessing a disturbing trend.\u00a0 Brand new networked products are being introduced to the market without IPv6 capabilities.\u00a0 Undoubtedly, these companies intend for their products to remain relevant for the foreseeable future.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/making-a-new-product-make-it-dual-protocol\/#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\/making-a-new-product-make-it-dual-protocol\/#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":"Making a New Product? Make it Dual Protocol!"}]},{"@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\/ee71ac61fe2ea349f6e991e628d22f4c","name":"Scott Hogg","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","caption":"Scott Hogg"},"description":"Scott Hogg has 30 years of network and security experience and is president of Hogg Networking with. Scott Hogg specializes in teaching Internet Protocol version 6 (IPv6) and providing implementation guidance. Scott is CCIE #5133 (Emeritus) and CISSP #4610. Scott is Chair Emeritus of the Rocky Mountain IPv6 Task Force (RMv6TF), a member of the IPv6 Center of Excellence (COE), and co-author of the Cisco Press book on IPv6 Security.","sameAs":["https:\/\/hexabuild.io"],"url":"https:\/\/www.infoblox.com\/blog\/author\/scott-hogg\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3400","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\/321"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=3400"}],"version-history":[{"count":2,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3400\/revisions"}],"predecessor-version":[{"id":3402,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3400\/revisions\/3402"}],"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=3400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=3400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=3400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}