{"id":143,"date":"2011-02-03T00:09:10","date_gmt":"2011-02-03T00:09:10","guid":{"rendered":"http:\/\/prensa.lacnic.net\/news\/2011-01\/ipv6-telecoms-experience"},"modified":"2011-02-15T18:28:17","modified_gmt":"2011-02-15T18:28:17","slug":"ipv6-telecoms-experience","status":"publish","type":"post","link":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/","title":{"rendered":"IPv6: Telecom\u2019s experience"},"content":{"rendered":"<h3><strong>Introduction<\/strong><\/h3>\n<p><em>When we were invited to share with the community how Telecom Argentina is experiencing the transition from IPv4 to IPv6, memories came back of how we had to explain to the &#8220;greater Company&#8221; that IPv4 \u2013\u00a0that precious resource\u00a0\u2013 would be soon exhausted.<\/em><\/p>\n<p><em>Managing the early stages of IPv6 has shown us that IP communications do not only involve technical issues. IPv6 is a change that we cannot choose to avoid and from which there is no turning back. It involves not only network administrators but also the company as a whole.<\/em><\/p>\n<p><em>In the beginning, every time the subject of IPv6 came up we heard comments such as the following:<\/em><\/p>\n<p><em>&#8211; There\u2019s still a lot of time&#8230; let&#8217;s talk about this later.<\/em><\/p>\n<p><em>&#8211; What do you mean IP addresses will run out? <\/em><\/p>\n<p><em>&#8211; Are you sure? When?<\/em><\/p>\n<p><em>Now that day has come and, thanks to all the work that has been done and the plans that have been implemented, Telecom Argentina is prepared to begin the transition to IPv6.<\/em><\/p>\n<h3>Telecom Argentina<\/h3>\n<p>Telecom Argentina S.A. is a company that provides communications services in Argentina and Paraguay. As at September 9, 2010, its consolidated results showed <strong>17,843,000<\/strong> mobile clients; 1,330,000 broadband accesses; 4,087,000 landlines; and a growth of 18% in net sales of voice, data, Internet and mobile telephone services within the past year.<\/p>\n<p>Based on current growth estimates for (mobile and fixed) data and Internet services, in 2011 the company will need to assign 1,000,000 new IP addresses to satisfy its clients\u2019 needs.<\/p>\n<h3>Transition to IPv6<\/h3>\n<h4><strong>Background at  Telecom:<\/strong><\/h4>\n<p>Because the company has always been involved in  technological innovation activities, we began preparing projections on the  exhaustion of the stock of IPv4 addresses back in 2005. At that time, a goal  requiring that all future purchases of new equipment relating to Internet  access services, from the backbone to corporate CPE, should comply with the  various standards that make up IPv6 was adopted. This decision allowed us to  begin acquiring the formal tools required for the new protocol\u2019s future  deployment.<\/p>\n<p>The process of developing the necessary network  engineering began in late 2007, focusing on the backbone. This phase included a  detailed analysis of the IPv6 support status of existing infrastructure and  identifying which hardware and software would have to be replaced due to their  obsolescence. Consequently, a replacement plan was prepared that would be  executed along with the annual process of expanding required infrastructure  during the upcoming periods. Thus, the required investment was gradually  absorbed within the normal growth process.<\/p>\n<p>During 2008 and 2009, capacity plans were  executed that provided the network with the hardware and software needed to  support IPv6, among other drivers. In parallel, during 2008 and 2009, laboratory  testing was conducted and the configuration parameters that would be applied to  the network through ad-hoc engineering processes were prepared. During this  stage the company worked jointly with the provider, as many of the required  functionalities were part of their internal development roadmap but had not yet  been released for use.<\/p>\n<p>During the last quarter of 2009, we began to  implement the previously approved logical configurations in the production  network, beginning with RFC 4798, 6PE (IPv6 packets  transported from PE to PE inside MPLS network) .<\/p>\n<p>During the second quarter of 2010, the levels of  field deployment and reliability that had been achieved were enough to consider  backbone IPv6 to be of production quality. For this, the joint work carried out  with one of our clients, RIU (<a href=\"http:\/\/www.riu.edu.ar\/topologia.html\">Redes de Interconexi\u00f3n Universitaria<\/a>) and our upstream  provider, TIS was essential (Seabone is the international backbone of Telecom  Italy, property of and operated by <a href=\"http:\/\/www.tisparkle.net\/\">Telecom Italia  Sparkle<\/a>).<\/p>\n<p>Towards the end of 2010, laboratory testing for  compliance with RFC 4659, 6VPE (IPv6 packets transported from PE to PE inside  VPN-MPLS network), was concluded. Field testing and production network  deployment are planned for the first quarter of 2011.<\/p>\n<h3>IPv4 Address Management<\/h3>\n<p>Although Telecom Argentina has always kept its  assignment processes in line with LACNIC policies, during 2008 and 2009 the company  worked on reorganizing the assignment of all products requiring IPv4 in order  to prepare for IPv4 address stock exhaustion. In addition, in order to increase  the efficiency in the use of IPv4 address space, an adaptation plan was  defined:<\/p>\n<ul>\n<li>Reviewing assignments for  all products that use public IPv4 addresses<\/li>\n<li>IP address recovery plan<\/li>\n<li>Creating awareness on IPv4  exhaustion and a plan for introducing IPv6<\/li>\n<li>Analysis of the impact on  the company&#8217;s systems<\/li>\n<\/ul>\n<h4><span style=\"text-decoration: underline;\">Reviewing assignments  for all products that use public IPv4 addresses<\/span><\/h4>\n<p>Executing the first item of  the plan required modifying the assignment of all company products requiring  IPv4. For this, we worked together with the Marketing and Product Development  departments for the various customer segments, redefining the number of IPv4  addresses that would be assigned to each service and aligning them with the  latest policy approved by LACNIC. Section 2.3.2.8. of the current policy,  Webhosting, which affects datacenter clients was the one that had the greatest  impact.<\/p>\n<p>These modifications were  coordinated by the Corporate Process department, which documented and published  the agreed processes on our internal portal.<\/p>\n<h4><span style=\"text-decoration: underline;\">IP  address recovery plan<\/span><span style=\"text-decoration: underline;\"> <\/span><\/h4>\n<p>The  Company set up a task force to implement a plan for recovering underutilized  IPv4 addresses, which resulted in the recovery of a large amount of IPv4  address space.<\/p>\n<h4><span style=\"text-decoration: underline;\">Creating awareness on IPv4  exhaustion and a plan for introducing IPv6<\/span><span style=\"text-decoration: underline;\"> <\/span><\/h4>\n<p>Meetings with various Company departments to  communicate &#8220;the news&#8221;, answering questions, clearing doubts and  dispelling existing myths:<\/p>\n<ul>\n<li>The Internet will not  come to a halt.<\/li>\n<li>There will be IPv4  addresses in production networks for many years to come (in various ways).<\/li>\n<li>IPv6 does not replace  IPv4.<\/li>\n<li>IPv6 is the evolution  of IPv4.<\/li>\n<li>It&#8217;s not about disabling IPv4 in order to enable  IPv6. THIS IS NOT A MIGRATION.<\/li>\n<\/ul>\n<p><strong>Implementing  IPv6 involves the coexistence of IPv4 and IPv6; applications are responsible  for deciding which protocol they will use.<\/strong><strong> <\/strong><\/p>\n<h4><span style=\"text-decoration: underline;\">Analysis of the impact on  the company&#8217;s systems<\/span><span style=\"text-decoration: underline;\"> <\/span><\/h4>\n<p>In order to prepare an adaptation plan, an  analysis was conducted to determine which systems would be affected and when.<\/p>\n<h3>Our Experience in Enabling  IPv6 Services<\/h3>\n<p>A field testing period was  required to stabilize the service.<\/p>\n<p>The dual-stack solution  involves higher costs (building and maintaining two networks, including  security).<\/p>\n<h4>DNS Resolution for IPv6  Addresses<\/h4>\n<p>Dual-stack DNS resolver software must be available \u2013 a software that  supports all the elements required both for IPv4 and IPv6 address resolution (A  records, AAAA records, PTR records, etc.) and that is within the IPv6 domain  (0.d.3.1.1.0.0.2.ip6.arpa). Reverse resolution of the assigned \/32 prefix is  also required, as are the reverse and direct resolution of each IPv6 host.  Authoritative resolution also requires dual-stack software.<\/p>\n<p>As part of our experience in enabling IPv6 services, in October 2010 we  conducted field tests to verify the support status of dual-stack resolution in  some content servers using our dual-stack DNS resolver.<\/p>\n<p>The operation was verified on some websites which can be reached using  both IPv4 and IPv6: <a href=\"http:\/\/www.isoc.org\/\">www.isoc.org<\/a>, <a href=\"http:\/\/www.ietf.org\/\">www.ietf.org<\/a>, <a href=\"http:\/\/www.iana.org\/\">www.iana.org<\/a>, <a href=\"http:\/\/www.arin.net\/\">www.arin.net<\/a> and <a href=\"http:\/\/www.lacnic.net\/\">www.lacnic.net<\/a>.<\/p>\n<p>However, it is still not possible to reach websites such as <a href=\"http:\/\/www.yahoo.com.ar\/\">www.yahoo.com.ar<\/a>, <a href=\"http:\/\/www.ebay.com\/\">www.ebay.com<\/a>, <a href=\"http:\/\/www.flickr.com\/\">www.flickr.com<\/a>, <a href=\"http:\/\/www.linkedin.com\/\">www.linkedin.com<\/a> and <a href=\"http:\/\/www.facebook.com\/\">www.facebook.com<\/a> using IPv6 as they are not providing DNS resolution for IPv6 but only for  IPv4.<\/p>\n<p>In the case of <a href=\"http:\/\/www.youtube.com\/\">www.youtube.com<\/a> and <a href=\"http:\/\/www.google.com\/\">www.google.com<\/a><em>, <\/em>an  AAAA DNS Whitelisting IPv6 policy is used (to qualify, Google requires  separate DNS servers for IPv6 users, not servers shared with IPv4-only users).<\/p>\n<h4>Interconnection Challenges<\/h4>\n<p>Assumption:<\/p>\n<p>\u201c<em>When a <\/em><em>certain number of clients are able to access IPv6, part of their  communications will fail&#8230;\u201d <\/em><\/p>\n<p>There are several factors  that determine the quality of Internet interconnections. In particular, due to  the fact that IPv6 deployment is in its early stages, it is important to  consider the existence of low-latency paths, symmetry in IPv4 and IPv6 paths  for the same website, operational status reliability (industrial process  support), and DNS connectivity.<\/p>\n<p>Based on this assumption,  as part of the experience we verified route and path quality at certain points,  comparing both IPv4 and IPv6 performance.<\/p>\n<p>As a general conclusion, we  observed that <span style=\"text-decoration: underline;\">IPv6 paths have a latency of the same order of magnitude as  IPv4 paths<\/span>. In addition, <span style=\"text-decoration: underline;\">path asymmetries were observed<\/span> for the same  site for IPv4 and IPv6. This is an aspect that should be improved for improving  future reliability.<\/p>\n<h3>Final Considerations<\/h3>\n<p>To conclude, we would like to highlight some relevant points that should  be taken into consideration for transitioning to IPv6 (recommendations taken  from IETF RFC 6036, October 2010 &#8211; Emerging  Service Provider Scenarios for IPv6 Deployment, informational survey of  a number of ISPs carried out in early 2010).<\/p>\n<p><em>&#8220;Without customers  wanting IPv6, getting business backing is very hard, and IPv6 security and  scale was not a focus for vendors until very recently. Operators lack real  experience with customer usage of IPv6, and the resulting lack of confidence  causes delay. <\/em>&#8230;\u201d.<\/p>\n<p><strong><em>\u201c<\/em><\/strong><em>Customer support needs to be aware that IPv6 is  being started in your network, or servers. We experienced many IPv6 blocking  applications, applications that do not fall back to IPv4, etc\u2026\u201d.<\/em><\/p>\n<p><em>\u201cEvangelization remains a  must, as it seems that many ISP and IT managers are still unaware of the need  for an IPv6 plan, and are inclined to dismiss IPv4 depletion as a false alarm,  and also seem unaware that NATs create expensive support requirements\u201d.<\/em><\/p>\n<h4>Finally:<\/h4>\n<ul>\n<li><a title=\"Permanent Link to Why bother moving to IPv6?\" href=\"http:\/\/www.ipv6actnow.org\/2010\/09\/why-bother-moving-to-ipv6\/\">Why bother moving  to IPv6?<\/a><\/li>\n<li><a href=\"http:\/\/www.ipv6actnow.org\/2010\/10\/ready-or-not-heres-ipv6\">Ready or not, here is IPv6<\/a><\/li>\n<li><a title=\"Permanent Link to Don\u2019t panic! The web isn\u2019t full to capacity \u2013 yet\" href=\"http:\/\/www.ipv6actnow.org\/2011\/01\/dont-panic-the-web-isnt-full-to-capacity-%e2%80%93-yet\/\">Don\u2019t panic! The web isn\u2019t full to capacity \u2013 yet<\/a><\/li>\n<\/ul>\n<h3>Acknowledgements:<\/h3>\n<p>To  our managers and directors who provide their unconditional support to this  project, and to the working team that makes it possible.<\/p>\n<p><strong>Gabriel Castro<br \/>\n<\/strong><strong><\/strong>Transportation Engineering Department &#8211; Engineering  Department &#8211; Technology Division &#8211; Network Division &#8211; TELECOM ARGENTINA<\/p>\n<p><strong>Marta Astaco<br \/>\n<\/strong><strong> <\/strong>Network and Services Assurance Department &#8211; Network  and Services Provision and Assurance Department &#8211; Network Division &#8211; TELECOM  ARGENTINA<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u201cWhen we were invited to share with the community how Telecom Argentina is experiencing the transition from IPv4 to IPv6, memories came back of how we had to explain to the &#8220;greater Company&#8221; that IPv4 \u2013 that precious resource \u2013 would be soon exhausted,\u201d say the authors of this article.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[650],"tags":[],"archivo":[1345,547],"taxonomy-authors":[],"tipo_autor":[],"class_list":["post-143","post","type-post","status-publish","format-standard","hentry","category-sin-categoria-en","archivo-editions","archivo-february-2011-edition"],"acf":{"author":"","related_notes":null},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>LACNIC Blog | IPv6: Telecom\u2019s experience<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"LACNIC Blog | IPv6: Telecom\u2019s experience\" \/>\n<meta property=\"og:description\" content=\"\u201cWhen we were invited to share with the community how Telecom Argentina is experiencing the transition from IPv4 to IPv6, memories came back of how we had to explain to the &quot;greater Company&quot; that IPv4 \u2013 that precious resource \u2013 would be soon exhausted,\u201d say the authors of this article.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\" \/>\n<meta property=\"og:site_name\" content=\"LACNIC Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/lacnic\" \/>\n<meta property=\"article:published_time\" content=\"2011-02-03T00:09:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2011-02-15T18:28:17+00:00\" \/>\n<meta name=\"author\" content=\"Mart\u00edn\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@lacnic\" \/>\n<meta name=\"twitter:site\" content=\"@lacnic\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\"},\"author\":{\"name\":\"Mart\u00edn\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/person\/3f3117e292d71f4166f765368b0760dc\"},\"headline\":\"IPv6: Telecom\u2019s experience\",\"datePublished\":\"2011-02-03T00:09:10+00:00\",\"dateModified\":\"2011-02-15T18:28:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\"},\"wordCount\":1619,\"commentCount\":8,\"publisher\":{\"@id\":\"https:\/\/blog.lacnic.net\/#organization\"},\"articleSection\":[\"sin categoria\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\",\"url\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\",\"name\":\"LACNIC Blog | IPv6: Telecom\u2019s experience\",\"isPartOf\":{\"@id\":\"https:\/\/blog.lacnic.net\/#website\"},\"datePublished\":\"2011-02-03T00:09:10+00:00\",\"dateModified\":\"2011-02-15T18:28:17+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Portada\",\"item\":\"https:\/\/blog.lacnic.net\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"IPv6: Telecom\u2019s experience\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.lacnic.net\/#website\",\"url\":\"https:\/\/blog.lacnic.net\/\",\"name\":\"LACNIC Blog\",\"description\":\"En el Blog de LACNIC encontrar\u00e1s art\u00edculos t\u00e9cnicos vinculados al desarrollo de Internet en la regi\u00f3n de Am\u00e9rica Latina y el Caribe.\",\"publisher\":{\"@id\":\"https:\/\/blog.lacnic.net\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.lacnic.net\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.lacnic.net\/#organization\",\"name\":\"LACNIC Blog\",\"url\":\"https:\/\/blog.lacnic.net\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg\",\"contentUrl\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg\",\"caption\":\"LACNIC Blog\"},\"image\":{\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/facebook.com\/lacnic\",\"https:\/\/x.com\/lacnic\",\"https:\/\/www.instagram.com\/lacnic\/?hl=es-la\",\"https:\/\/uy.linkedin.com\/company\/lacnic\",\"https:\/\/www.youtube.com\/user\/lacnicstaff\",\"https:\/\/www.lacnic.net\/podcast\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/person\/3f3117e292d71f4166f765368b0760dc\",\"name\":\"Mart\u00edn\",\"description\":\"Especialista en imagen institucional\",\"url\":\"https:\/\/blog.lacnic.net\/en\/author\/sysmartin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"LACNIC Blog | IPv6: Telecom\u2019s experience","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:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/","og_locale":"en_US","og_type":"article","og_title":"LACNIC Blog | IPv6: Telecom\u2019s experience","og_description":"\u201cWhen we were invited to share with the community how Telecom Argentina is experiencing the transition from IPv4 to IPv6, memories came back of how we had to explain to the \"greater Company\" that IPv4 \u2013 that precious resource \u2013 would be soon exhausted,\u201d say the authors of this article.","og_url":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/","og_site_name":"LACNIC Blog","article_publisher":"https:\/\/facebook.com\/lacnic","article_published_time":"2011-02-03T00:09:10+00:00","article_modified_time":"2011-02-15T18:28:17+00:00","author":"Mart\u00edn","twitter_card":"summary_large_image","twitter_creator":"@lacnic","twitter_site":"@lacnic","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#article","isPartOf":{"@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/"},"author":{"name":"Mart\u00edn","@id":"https:\/\/blog.lacnic.net\/#\/schema\/person\/3f3117e292d71f4166f765368b0760dc"},"headline":"IPv6: Telecom\u2019s experience","datePublished":"2011-02-03T00:09:10+00:00","dateModified":"2011-02-15T18:28:17+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/"},"wordCount":1619,"commentCount":8,"publisher":{"@id":"https:\/\/blog.lacnic.net\/#organization"},"articleSection":["sin categoria"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/","url":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/","name":"LACNIC Blog | IPv6: Telecom\u2019s experience","isPartOf":{"@id":"https:\/\/blog.lacnic.net\/#website"},"datePublished":"2011-02-03T00:09:10+00:00","dateModified":"2011-02-15T18:28:17+00:00","breadcrumb":{"@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.lacnic.net\/en\/ipv6-telecoms-experience\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Portada","item":"https:\/\/blog.lacnic.net\/en\/"},{"@type":"ListItem","position":2,"name":"IPv6: Telecom\u2019s experience"}]},{"@type":"WebSite","@id":"https:\/\/blog.lacnic.net\/#website","url":"https:\/\/blog.lacnic.net\/","name":"LACNIC Blog","description":"En el Blog de LACNIC encontrar\u00e1s art\u00edculos t\u00e9cnicos vinculados al desarrollo de Internet en la regi\u00f3n de Am\u00e9rica Latina y el Caribe.","publisher":{"@id":"https:\/\/blog.lacnic.net\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.lacnic.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/blog.lacnic.net\/#organization","name":"LACNIC Blog","url":"https:\/\/blog.lacnic.net\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/","url":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg","contentUrl":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg","caption":"LACNIC Blog"},"image":{"@id":"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/lacnic","https:\/\/x.com\/lacnic","https:\/\/www.instagram.com\/lacnic\/?hl=es-la","https:\/\/uy.linkedin.com\/company\/lacnic","https:\/\/www.youtube.com\/user\/lacnicstaff","https:\/\/www.lacnic.net\/podcast"]},{"@type":"Person","@id":"https:\/\/blog.lacnic.net\/#\/schema\/person\/3f3117e292d71f4166f765368b0760dc","name":"Mart\u00edn","description":"Especialista en imagen institucional","url":"https:\/\/blog.lacnic.net\/en\/author\/sysmartin\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"wpml_current_locale":"en_US","wpml_translations":[{"locale":"es_ES","id":79,"post_title":"IPv6: La experiencia de Telecom","slug":"ipv6-la-experiencia-de-telecom","href":"https:\/\/blog.lacnic.net\/ipv6-la-experiencia-de-telecom\/"},{"locale":"pt_BR","id":144,"post_title":"IPv6: A experi\u00eancia de Telecom","slug":"ipv6-a-experiencia-de-telecom","href":"https:\/\/blog.lacnic.net\/pt-br\/ipv6-a-experiencia-de-telecom\/"}],"_links":{"self":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/comments?post=143"}],"version-history":[{"count":7,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/143\/revisions"}],"predecessor-version":[{"id":313,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/143\/revisions\/313"}],"wp:attachment":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/media?parent=143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/categories?post=143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/tags?post=143"},{"taxonomy":"archivo","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/archivo?post=143"},{"taxonomy":"taxonomy-authors","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/taxonomy-authors?post=143"},{"taxonomy":"tipo_autor","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/tipo_autor?post=143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}