<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ICANN Blog &#187; ccTLDs</title>
	<atom:link href="http://blog.icann.org/category/cctlds/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Mon, 17 Jun 2013 22:40:20 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>CEO Roundtable III: ccTLDs and the DNS Sector</title>
		<link>http://blog.icann.org/2013/03/ceo-roundtable-iii-cctlds-and-the-dns-sector/</link>
		<comments>http://blog.icann.org/2013/03/ceo-roundtable-iii-cctlds-and-the-dns-sector/#comments</comments>
		<pubDate>Tue, 19 Mar 2013 01:03:17 +0000</pubDate>
		<dc:creator>Fadi Chehadé</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=5403</guid>
		<description><![CDATA[I was pleased to have the opportunity last week to meet with a group of ccTLDs in London, as part of a series of CEO Roundtables centered on strategic issues faced by the Domain Name System (DNS) sector. This roundtable served as a forum for the ccTLDs, from a diverse set of countries, to provide [...]]]></description>
				<content:encoded><![CDATA[<p>I was pleased to have the opportunity last week to meet with a group of ccTLDs in London, as part of a series of CEO Roundtables centered on strategic issues faced by the Domain Name System (DNS) sector.</p>
<p>This roundtable served as a forum for the ccTLDs, from a diverse set of countries, to provide insights about the unique and influential role they play in the DNS ecosystem. I was thankful for the rich dialogue that resulted and which explored the quality of the operational and security functions ccTLDs perform to serve their users and citizens, all within the framework of policies and requirements of their own countries. In addition, the roundtable allowed for valuable feedback and for us to explore ways to enhance our relationship.</p>
<p>Another objective was to consider DNS developments, such as the introduction of new gTLDs, and the rapid pace of innovation within the sector and how this will influence ccTLDs. We also addressed potential challenges to the multistakeholder model of Internet governance in the context of the needs of the next billion Internet users who are scheduled to come online.</p>
<p>I briefed them on a number of ICANN&#8217;s operational priorities, as well as the work being undertaken by the registry and the registrar CEOs who participated in last month&#8217;s roundtables. Other topics included: 1) the reputational risks and opportunities for ccTLDs and the domain name industry from a media perspective; 2) statistical trends and the interplay between gTLD market changes and ccTLDs over the years; and 3) options for using infographic tools to depict and explain the role of the ccTLDs in the DNS sector.</p>
<p>Something of tremendous importance, which I stressed in my conversations with the ccTLD CEOs, and that I would like to ensure is communicated more broadly: ICANN&#8217;s focus should not be on the amount of ccTLD financial contributions, rather emphasis needs to be placed on areas where we can collaborate, as true partners. Working together must take priority over financial considerations that have been stumbling blocks in the past. We share a common goal of bringing value to the Internet and its users &#8211; individuals, businesses, citizens and organizations &#8211; that is possible through cooperation, alignment of our technical and operational performance, and support of the multistakeholder model.</p>
<p>While the drivers of ccTLD performance cannot be entirely decoupled from the performance of gTLDs, and the DNS sector as a whole, they do have many areas of differentiation. Among the issues we explored is ccTLDs&#8217; focus on the public interest through their role as national entities and in relation to larger, more global economic and social trends.</p>
<p>I am grateful to the CEOs for their participation and look forward to continuing our efforts at a DNS Summit, which will take place next month and will serve as the culminating event for this roundtable series.</p>
<div style="margin-bottom: 1em;">
	<a href="/wp-content/uploads/2013/03/ceo-roundtable-cctlds-1000x562-18mar13.png"><img src="/wp-content/uploads/2013/03/ceo-roundtable-cctlds-1000x562-18mar13.png" alt="CEO Roundtable III: ccTLDs and the DNS Sector" style="width: 480px; height: 270px; border: 1px solid #d8d8d8;" /></a>
</div>
<p>Roundtable participants (as pictured) include:</p>
<p><em>Back Row (from left to right):</em></p>
<p><strong>David Olive</strong>, Vice President, Policy Development Support, ICANN<br />
<strong>Frederico Neves</strong>, CTO, NIC.br<br />
<strong>Roelof Meijer</strong>, CEO, SIDN<br />
<strong>Xiaodong Lee</strong>, CEO, CNNIC<br />
<strong>Mathieu Weill</strong>, CEO, AFNIC<br />
<strong>Chris Disspain</strong>, CEO, auDA<br />
<strong>Bart Boswinkel</strong>, Senior Director, ccNSO Policy Development Support, ICANN<br />
<strong>Byron Holland</strong>, CEO, CIRA<br />
<strong>Richard Wein</strong>, CEO, nic.at</p>
<p><em>Front Row (from left to right):</em></p>
<p><strong>Sally Costerton</strong>, Senior Advisor to the President, Global Stakeholder Engagement, ICANN<br />
<strong>Rosalía Morales A.</strong>, Executive Director, NIC Costa Rica<br />
<strong>Sabine Dolderer</strong>, CEO, DENIC eG<br />
<strong>Lesley Cowley</strong>, CEO, Nominet<br />
<strong>Lim Choon Sai</strong>, General Manager, SGNIC<br />
<strong>Marc Van Wesemael</strong>, CEO, EURid<br />
<strong>Fadi Chehadé</strong>, President and CEO, ICANN</p>
<p><strong>This event was part of an ongoing series of small roundtable gatherings with CEOs that will continue in the future. For this particular roundtable, participants represented members and nonmembers of the ccNSO, and were from both smaller and larger-sized ccTLDs. Unfortunately, not all of the invitees could attend. Yet, we were fortunate to be joined by leaders from Latin America, Asia-Pacific, Europe, North America, and the Caribbean.</strong></p>
<hr />
<div style="background: #efefef; border: 1px solid #d8d8d8; padding: 1.5em 1.5em 0 1.5em; margin: 1em 0;">
<p>Reaction from the meeting participants confirming ICANN&#8217;s commitment to the public interest include:</p>
<blockquote style="border-left: 0;">
<p>&#8220;The meeting was dense and fruitful thanks to the very professional preparation by ICANN and the sincere and open manner in which participants, starting with Fadi Chehadé, were engaged. This is a great illustration of how ccTLDs and ICANN can engage in constructive and attentive partnerships.&#8221;</p>
<p style="text-align: right;">- Mathieu Weill, CEO, AFNIC</p>
<p>&#8220;It was a pleasure to attend this meaningful session and I congratulate ICANN CEO Fadi Chahedé for his leadership and commitment in reaching out to the ccTLD Managers. I am heartened that he would like to learn and obtain our advice in our roles as ccTLD Managers in meeting the needs of local stakeholders and in serving public interest. The session also allowed us to hear from him his concern and priority in steering the ICANN and to explore how best ccTLDs and other ICANN communities can work together to bring value to Internet and its users.&#8221;</p>
<p style="text-align: right;">- Choon Sai, General Manager, SGNIC</p>
<p>&#8220;It was a pleasure to attend the ccTLD CEO roundtable and have the opportunity to discuss the main issues affecting our industry with senior members of the ICANN staff. I congratulate Fadi&#8217;s effort to include the community in the future work plans of ICANN&#8217;s strategy and to promote an open dialogue with the key players in the DNS industry. The discussions were fruitful, engaging and demonstrate ICANN&#8217;s global perspective.&#8221;</p>
<p style="text-align: right;">- Rosalía Morales A., Executive Director, NIC Costa Rica</p>
</blockquote>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2013/03/ceo-roundtable-iii-cctlds-and-the-dns-sector/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>IPv6 All the Way Down</title>
		<link>http://blog.icann.org/2012/06/ipv6-all-the-way-down/</link>
		<comments>http://blog.icann.org/2012/06/ipv6-all-the-way-down/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:32:49 +0000</pubDate>
		<dc:creator>Leo Vegoda</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4067</guid>
		<description><![CDATA[In the past we&#8217;ve talked about how the Internet&#8217;s key infrastructure has been getting ready for IPv6. In 2004, the first IPv6 glue was added to the root DNS zone for .JP and .KR but when you look at a part of the root zone today &#8211; the part related to ccTLDs derived from the [...]]]></description>
				<content:encoded><![CDATA[<p>In the past we&#8217;ve talked about how the Internet&#8217;s key infrastructure has been getting ready for IPv6. In 2004, the first IPv6 glue was added to the root DNS zone for .JP and .KR but when you look at a part of the root zone today &ndash; the part related to ccTLDs derived from the ISO-3166-1 list &ndash; you can see that a huge proportion of TLD operators are ready for IPv6.</p>
<div style="margin-bottom: 1em;"> <a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"> <img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>In 2008 another big step was taken, when IPv6 glue was added for six of the root DNS servers. Today, in 2012, nine have IPv6 glue and as the map below shows, IPv6 access to root DNS servers is widely spread around the world. While all L-root nodes are IPv6 capable, some are attached to networks that do not yet run IPv6, so only 68 of the 112 nodes deployed today are accessed over IPv6.</p>
<div style="margin-bottom: 1em;"> <a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"> <img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"></a></div>
<p>Beyond the DNS, major network backbones and IXPs have been IPv6 ready for years, too. Currently, 95% of Euro-IX&#8217;s 63 members have IPv6 peering LANs ate the exchanges they operate. This means that ISPs, the IXPs&#8217; customers have been keen to make sure their peering platforms are ready for IPv6.</p>
<p>These are all major deliverables on the critical path to smooth IPv6 deployment. Now they&#8217;re done it&#8217;s time for content and access providers to offer content and access over IPv6. As the measurements make very clear, <a href="http://www.worldipv6launch.org/measurements/">World IPv6 Launch</a> delivered lots of content over IPv6 and a lot of large ISPs have been enabling their subscribers, with millions more to follow before the year end.</p>
<p>But those subscribers need IPv6 capable routers and modems in their homes so that they can access the Internet over IPv6. <a href="http://www.worldipv6launch.org/participants/?q=3">Five manufacturers</a> are now offering home networking equipment that&#8217;s IPv6 enabled by default and available at low and medium price points. This is on top of the <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">17 IPv6 ready cable modem products</a> available today.</p>
<p>All the jigsaw pieces are now available for successful IPv6 deployment to consumer Internet users.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/ipv6-all-the-way-down/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPv6 一路向前</title>
		<link>http://blog.icann.org/2012/06/ipv6-%e4%b8%80%e8%b7%af%e5%90%91%e5%89%8d/</link>
		<comments>http://blog.icann.org/2012/06/ipv6-%e4%b8%80%e8%b7%af%e5%90%91%e5%89%8d/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:31:41 +0000</pubDate>
		<dc:creator>ICANN Blog</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[Languages]]></category>
		<category><![CDATA[中文]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4481</guid>
		<description><![CDATA[此前，我们谈到了互联网的关键基础架构已经做好了部署 IPv6 的准备。2004 年，.JP 和 .KR 域名的根 DNS 域添加了第一个 IPv6 粘附，而在当今的根区域中，从与 ISO-3166-1 名单衍生的 ccTLD 相关的部分看，我们可以发现，有极大部分的 TLD 运营商已经准备好迎接 IPv6。 2008 年，IPv6 进程又迈出了一大步，又有六台根 DNS 服务器添加了 IPv6 粘附。时至今日，已有九台根 DNS 服务器上有 IPv6 粘附，具体如下图所示。世界各地已经广泛分布了能访问根 DNS 服务器的 IPv6 接口。虽然所有的 L-根节点都支持 IPv6，某些节点仍然隶属于未部署 IPv6 的网络，因此，目前已部署的 112 个节点中仅有 68 个能够接入 IPv6 网络。 除了 DNS 以外，主要的骨干网络和 IXP 都已经在数年前做好了部署 IPv6 的准备。目前，Euro-IX 的 63 个成员中 95% 已经在自己运行的交换服务器上测试了 [...]]]></description>
				<content:encoded><![CDATA[<p>此前，我们谈到了互联网的关键基础架构已经做好了部署 IPv6 的准备。2004 年，.JP 和 .KR 域名的根 DNS 域添加了第一个 IPv6 粘附，而在当今的根区域中，从与 ISO-3166-1 名单衍生的 ccTLD 相关的部分看，我们可以发现，有极大部分的 TLD 运营商已经准备好迎接 IPv6。</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"><img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>2008 年，IPv6 进程又迈出了一大步，又有六台根 DNS 服务器添加了 IPv6 粘附。时至今日，已有九台根 DNS 服务器上有 IPv6 粘附，具体如下图所示。世界各地已经广泛分布了能访问根 DNS 服务器的 IPv6 接口。虽然所有的 L-根节点都支持 IPv6，某些节点仍然隶属于未部署 IPv6 的网络，因此，目前已部署的 112 个节点中仅有 68 个能够接入 IPv6 网络。</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"><img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"></a></div>
<p>除了 DNS 以外，主要的骨干网络和 IXP 都已经在数年前做好了部署 IPv6 的准备。目前，Euro-IX 的 63 个成员中 95% 已经在自己运行的交换服务器上测试了 IPv6 局域网。这表明各 ISP（IXP 的客户）都热衷于确保其试验平台能够部署 IPv6。</p>
<p>这些都是顺利部署 IPv6 的关键进程中取得的重大成果。鉴于这些已取得的成果，现在正是让内容和接入供应商在 IPv6 网络上提供内容和接入服务的时机。测量结果清楚地表明，<a href="http://www.worldipv6launch.org/measurements/">World IPv6 Launch</a>（世界 IPv6 启动）已成功在 IPv6 上发送了许多的内容，而许多大型 ISP 也已经为用户开放了 IPv6 服务，并且在今年结束之前将再有数百万用户接入 IPv6 网络。</p>
<p>但这些用户须在家中自备支持 IPv6 的路由器和调制解调器，才能通过 IPv6 访问互联网。目前有<a href="http://www.worldipv6launch.org/participants/?q=3">五家制造商</a>正在供应默认支持 IPv6 的家庭网络连接设备，并且价格适中。这些产品在目前在售的 <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">17 种支持 IPv6 的有线调制解调器产品</a>中位于前列。</p>
<p>目前所有已具备的条件表明，IPv6 可以成功部署，供商业型互联网用户使用。</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/ipv6-%e4%b8%80%e8%b7%af%e5%90%91%e5%89%8d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Полное развертывание IPv6</title>
		<link>http://blog.icann.org/2012/06/%d0%bf%d0%be%d0%bb%d0%bd%d0%be%d0%b5-%d1%80%d0%b0%d0%b7%d0%b2%d0%b5%d1%80%d1%82%d1%8b%d0%b2%d0%b0%d0%bd%d0%b8%d0%b5-ipv6/</link>
		<comments>http://blog.icann.org/2012/06/%d0%bf%d0%be%d0%bb%d0%bd%d0%be%d0%b5-%d1%80%d0%b0%d0%b7%d0%b2%d0%b5%d1%80%d1%82%d1%8b%d0%b2%d0%b0%d0%bd%d0%b8%d0%b5-ipv6/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:29:47 +0000</pubDate>
		<dc:creator>ICANN Blog</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[Languages]]></category>
		<category><![CDATA[Русский]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4487</guid>
		<description><![CDATA[В прошлом мы говорили о процессе подготовки критически важной инфраструктуры Интернета к использованию IPv6. В 2004 году первые связующие элементы IPv6 были добавлены в корневую зону DNS для доменов .JP и .KR, однако если в наши дни взглянуть на часть корневой зоны &#8211; ту часть, которая относится к нДВУ из списка ISO-3166-1, &#8211; можно увидеть, [...]]]></description>
				<content:encoded><![CDATA[<p>В прошлом мы говорили о процессе подготовки критически важной инфраструктуры Интернета к использованию IPv6. В 2004 году первые связующие элементы IPv6 были добавлены в корневую зону DNS для доменов .JP и .KR, однако если в наши дни взглянуть на часть корневой зоны &ndash; ту часть, которая относится к нДВУ из списка ISO-3166-1, &ndash; можно увидеть, что очень большая часть операторов ДВУ готова к использованию IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"><img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>В 2008 году был сделан еще один большой шаг, когда были добавлены связующие элементы IPv6 для шести корневых серверов DNS. На сегодняшний день, в 2012 году, девять из них имеют связующие элементы IPv6 и, как показано на карте ниже, доступ по протоколу IPv6 к корневым серверам DNS широко распространен по всему миру. Хотя все корневые узлы сервера &laquo;L&raquo; совместимы с IPv6, некоторые из них подключены к сетям, еще не использующим IPv6, поэтому доступ по протоколу IPv6 возможен только к 68 из 112 развернутых в настоящее время узлов.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"><img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg" /></a></div>
<p>Помимо DNS, главные сетевые магистрали и точки обмена трафиком (IXP) уже в течение многих лет готовы к переходу на IPv6. В настоящее время 95% из 63 членов Euro-IX имеют одноранговые локальные сети IPv6 для обмена трафиком, находящимся под их управлением. Это означает, что поставщики услуг Интернета, клиенты IXP стремятся обеспечить готовность своих одноранговых платформ к использованию IPv6.</p>
<p>Все это &mdash; крупные результаты на важном пути развертывания IPv6, позволяющие обеспечить плавность развертывания. Теперь, когда они достигнуты, для поставщиков контента и доступа настало время предлагать информационное содержание и доступ по протоколу IPv6. Как совершенно точно показывают результаты измерений, инициатива <a href="http://www.worldipv6launch.org/measurements/">World IPv6 Launch (Всемирный запуск IPv6)</a> привела к передаче большого объема контента по IPv6, и многие крупные поставщики услуг Интернета позволяют своим абонентам использовать этот протокол, ожидая появления миллионов новых пользователей данного протокола до конца этого года.</p>
<p>Однако для получения возможности доступа к Интернету по протоколу IPv6 этим абонентам необходимо установить у себя дома совместимые с IPv6 маршрутизаторы и модемы. <a href="http://www.worldipv6launch.org/participants/?q=3">Пять производителей</a> предлагают в настоящее время домашнее сетевое оборудование, совместимое с IPv6 по умолчанию и относящееся к низкой и средней ценовой категории. Эти продукты лидируют среди доступных сегодня <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">17 кабельных модемов, готовых к использованию IPv6</a>.</p>
<p>Теперь имеются все компоненты, позволяющие осуществить успешное развертывание IPv6 для потребителей, использующих Интернет.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/%d0%bf%d0%be%d0%bb%d0%bd%d0%be%d0%b5-%d1%80%d0%b0%d0%b7%d0%b2%d0%b5%d1%80%d1%82%d1%8b%d0%b2%d0%b0%d0%bd%d0%b8%d0%b5-ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPv6, le chemin parcouru</title>
		<link>http://blog.icann.org/2012/06/ipv6-le-chemin-parcouru/</link>
		<comments>http://blog.icann.org/2012/06/ipv6-le-chemin-parcouru/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:28:49 +0000</pubDate>
		<dc:creator>Leo Vegoda</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Français]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4495</guid>
		<description><![CDATA[Dans le passé, nous avons parlé sur la manière dont l&#8217;infrastructure clé d&#8217;Internet se préparait pour IPv6. En 2004, la première liaison IPv6 (IPv6 glue) a été ajoutée à la zone racine du DNS pour .JP et .KR ; mais si aujourd&#8217;hui vous regardez une partie de la zone racine &#8211; la zone liée aux [...]]]></description>
				<content:encoded><![CDATA[<p>Dans le passé, nous avons parlé sur la manière dont l&#8217;infrastructure clé d&#8217;Internet se préparait pour IPv6. En 2004, la première liaison IPv6 (<em>IPv6 glue</em>) a été ajoutée à la zone racine du DNS pour .JP et .KR ; mais si aujourd&#8217;hui vous regardez une partie de la zone racine &ndash; la zone liée aux ccTLD qui dérivent de la liste ISO-3166-1 &ndash; vous verrez que la plupart des opérateurs TLD sont prêts pour IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"><img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>Un grand progrès a été réalisé lorsqu&#8217;en 2008 la liaison IPv6 a été ajoutée dans six des serveurs racine du DNS. À ce jour, en 2012, il y en a neuf ayant la liaison IPv6. La carte ci-dessous montre que l&#8217;accès IPv6 aux serveurs racine du DNS est largement répandu dans le monde entier. Alors que les nœuds de la racine L sont capables de supporter IPv6, quelques-uns sont rattachés à des réseaux qui n&#8217;opèrent pas encore avec IPv6, de sorte qu&#8217;à ce jour, on ne peut accéder qu&#8217;à 68 des 112 nœuds déployés sur IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"><img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"></a></div>
<p>Au-delà du DNS, les plus grands réseaux fédérateurs et les IXP ont aussi été prêts pour IPv6 pendant des années. À ce jour, 95 % des 63 membres d&#8217;Euro-IX ont des réseaux locaux (LAN) d&#8217;appairage IPv6 pour leurs échanges. Cela signifie que les ISP, les clients d&#8217;IXP ont été motivés pour s&#8217;assurer que leurs plateformes d&#8217;appairage soient prêtes pour IPv6.</p>
<p>Voici les objectifs majeurs de l&#8217;étape critique pour assurer le déploiement d&#8217;IPv6. Maintenant que cela est fait, il est temps pour que les fournisseurs offrent l&#8217;accès et les contenus sur IPv6. Il est clair d&#8217;après les mesures, que le <a href="http://www.worldipv6launch.org/measurements/">World IPv6 Launch</a> a livré un bon nombre de contenus sur IPv6, qu&#8217;une grande partie des ISP ont rendu possible l&#8217;accès à leurs abonnés, et que des millions vont les suivre avant la fin de l&#8217;année.</p>
<p>Mais, pour pouvoir accéder à l&#8217;Internet sur IPv6, ces abonnées ont besoin d&#8217;avoir des routeurs et des modems adaptés dans leurs foyers. <a href="http://www.worldipv6launch.org/participants/?q=3">Five manufacturers</a> offrent à ce jour des équipements de réseau domestiques supportant IPv6 par défaut et qui sont disponibles sur le marché à des prix raisonnables. Ce sont les principaux <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">17 IPv6 ready cable modem products</a> disponibles aujourd&#8217;hui.</p>
<p>Toutes les pièces du puzzle sont maintenant disponibles pour le déploiement réussi d&#8217;IPv6 en faveur des utilisateurs d&#8217;Internet.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/ipv6-le-chemin-parcouru/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPv6 a montones</title>
		<link>http://blog.icann.org/2012/06/ipv6-a-montones/</link>
		<comments>http://blog.icann.org/2012/06/ipv6-a-montones/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:27:38 +0000</pubDate>
		<dc:creator>Leo Vegoda</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Español]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4503</guid>
		<description><![CDATA[En el pasado hemos hablado sobre cómo la infraestructura de claves de Internet se ha estado preparando para el IPv6. En el año 2004, el primer registro de interconexión (glue) del IPv6 fue agregado a la zona raíz del DNS para los dominios .JP y .KR, pero si en la actualidad se observa una parte [...]]]></description>
				<content:encoded><![CDATA[<p>En el pasado hemos hablado sobre cómo la infraestructura de claves de Internet se ha estado preparando para el IPv6. En el año 2004, el primer registro de interconexión (glue) del IPv6 fue agregado a la zona raíz del DNS para los dominios .JP y .KR, pero si en la actualidad se observa una parte de la zona raíz, aquella que se encuentra relacionada a ccTLDs derivados de la lista del ISO-3166-1, podrá ver que una enorme cantidad de los operadores de TLD ya están listos para el IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"><img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>En el año 2008 se dio otro importante paso cuando el registro de interconexión (glue) del IPv6 fue agregado a seis de los servidores raíz del DNS. Actualmente, en el año 2012, nueve servidores tienen registros de interconexión (glue) del IPv6 y, tal como lo muestra el mapa a continuación, el acceso IPv6 a servidores raíz del DNS se encuentra ampliamente difundido en todo el mundo. Si bien todos los nodos de los servidores de raíz &#8220;L&#8221; tienen la capacidad necesaria para el IPv6, algunos se encuentran adjuntados a redes que aún no funcionan con IPv6. Por lo tanto, sólo 68 de los 112 nodos que se encuentran desplegados en la actualidad son accedidos mediante el IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"><img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"></a></div>
<p>Además del DNS, los ejes de las redes más importantes y los Puntos de Intercambio de Internet (IXPs) también han estado preparados para el IPv6 hace varios años. Actualmente, el 95% de los 63 miembros de la Asociación de Intercambio de Internet Europeo (Euro-IX&#8217;s) tienen IPv6 interconectados con Redes de Área Local (LANs) en los intercambios que operan. Esto significa que los Proveedores de Servicios de Internet (ISPs), los clientes de los IXPs, han tenido el interés en asegurar que sus plataformas de interconexión estuviesen preparados para el IPv6.</p>
<p>Estos son los principales productos que se encuentran en el camino principal hacia un despliegue sin complicaciones del IPv6. Ahora que están listos, es hora de que los proveedores de contenido y acceso ofrezcan contenido y acceso mediante el IPv6. Tal como lo aclaran las mediciones, <a href="http://www.worldipv6launch.org/measurements/">el Lanzamiento Mundial del IPv6</a> brindó mucho contenido a través del IPv6 y varios importantes Proveedores de Servicios de Internet (ISPs) han estado habilitando a sus suscriptores con el uso de este protocolo. Se seguirán habilitando millones más antes del final del año.</p>
<p>Pero esos suscriptores necesitan enrutadores y módems en sus hogares que tengan la capacidad necesaria para el IPv6 para poder tener acceso a Internet a través de este protocolo. <a href="http://www.worldipv6launch.org/participants/?q=3">Cinco fabricantes</a> están ofreciendo equipos de red para el hogar que permiten el uso del IPv6 de forma predeterminada. Los mismos están disponibles a precios bajos y medianos. Estos ocupan un lugar importante entre los <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">17 productos de cable módem, listos para el uso del IPv6</a> que se encuentran disponibles en la actualidad.</p>
<p>Todas las piezas del rompecabezas están disponibles para un despliegue exitoso del IPv6 para los usuarios de Internet.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/ipv6-a-montones/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IPv6 معطل تمامًا</title>
		<link>http://blog.icann.org/2012/06/ipv6-%d9%85%d8%b9%d8%b7%d9%84-%d8%aa%d9%85%d8%a7%d9%85%d9%8b%d8%a7/</link>
		<comments>http://blog.icann.org/2012/06/ipv6-%d9%85%d8%b9%d8%b7%d9%84-%d8%aa%d9%85%d8%a7%d9%85%d9%8b%d8%a7/#comments</comments>
		<pubDate>Mon, 11 Jun 2012 22:26:39 +0000</pubDate>
		<dc:creator>Leo Vegoda</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[L-Root]]></category>
		<category><![CDATA[العربية]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=4509</guid>
		<description><![CDATA[تكلمنا في الماضي عن كيفية استعداد البنية التحتية الأساسية للإنترنت للعمل ببروتوكول IPv6. في عام 2004، تمت إضافة أول لصق لبروتوكول IPv6 إلى منطقة جزر DNS لكل من .JP و .KR ولكن عندما تنظر إلى جزء من منطقة الجزر اليوم &#8211; أي الجزء المرتبط بنطاقات ccTLD المشتقة من القائمة ISO-3166-1 &#8211; يمكنك أن ترى بأن [...]]]></description>
				<content:encoded><![CDATA[<div style="direction:rtl;">
<p>تكلمنا في الماضي عن كيفية استعداد البنية التحتية الأساسية للإنترنت للعمل ببروتوكول IPv6. في عام 2004، تمت إضافة أول لصق لبروتوكول IPv6 إلى منطقة جزر DNS لكل من <span dir="ltr">.JP</span> و <span dir="ltr">.KR</span> ولكن عندما تنظر إلى جزء من منطقة الجزر اليوم &ndash; أي الجزء المرتبط بنطاقات ccTLD المشتقة من القائمة ISO-3166-1 &ndash; يمكنك أن ترى بأن حصة كبيرة من مشغلي نطاقات TLD جاهزة للعمل باستخدام IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"><img style="width: 485px; height: 270px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-cctld-diversity-1000x557-11jun12.jpg"></a></div>
<p>وفي عام 2008، تم اتخاذ خطوة أخرى كبيرة، وذلك عندما تمت إضافة لصق بروتوكول IPv6 لخوادم DNS الجذر الستة. واليوم في عام 2012، تحتوي تسعة خوادم على لصق IPv6 كما توضح الخريطة أدناه، فقد انتشر الوصول إلى خوادم DNS الجذر بشكل واسع حول العالم. ففي حين أن كافة عقد جذر L قادرة على التشغيل بنظام IPv6، فإن البعض منها مرتبط بشبكات لا تعمل حتى الآن بنظام IPv6، لذا فإن 68 عقدة فقط من بين 112 عقدة مستخدمة اليوم يمكن الوصول إليها من خلال بروتوكول IPv6.</p>
<div style="margin-bottom: 1em;"><a href="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"><img style="width: 485px; height: 274px; border: 0;" src="/wp-content/uploads/2012/06/ipv6-root-dns-servers-1000x564-11jun12.jpg"></a></div>
<p>وبخلاف DNS، فإن الركائز الأساسية للشبكات بالإضافة إلى نقاط تبادل الإنترنت (IXP) كانت هي الأخرى جاهزة للعمل بنظام IPv6 لعدة أعوام. وفي الوقت الحالي، فإن نسبة 95 % من أعضاء نقاط تبادل الإنترنت الأوروبية البالغ عددهم 63 لديهم شبكات واسعة تعمل بنظام IPv6 قد استوعبت التبادلات التي تشغلها. وهذا يعني أن مشغلي خدمة الإنترنت، وعملاء نقاط تبادل الإنترنت كانت لديهم الرغبة في التأكد من أن المنصات الموازية التي تعمل لديهم جاهزة لاستخدام نظام IPv6.</p>
<p>وكانت هذه جميعها مواد التسليم الأساسية في الطريق الحرج للحصول على نشر واستخدام سلس لنظام IPv6. وبما أن ذلك قد تم الآن، فقد حان الوقت لموفي المحتوى والوصول لعرض المحتوى والوصول من خلال IPv6. وحيث أن عمليات القياس تؤدي إلى مزيد من التوضيح, فقد قدم <a href="http://www.worldipv6launch.org/measurements/">تشغيل IPv6 العالمي</a> العديد من المحتويات عن طريق IPv6 والعديد من كبار موفر خدمة إنترنت كانوا يقومون بتمكين المشتركين لديهم، بالإضافة إلى الملايين للمتابعة قبل نهاية العام.</p>
<p>إلا أن هؤلاء المشتركين بحاجة إلى أجهزة توجيه وأجهزة مودم قادرة على استخدام IPv6 في منازلهم بحيث يمكنك الوصول إلى الإنترنت عبر استخدام IPv6. <a href="http://www.worldipv6launch.org/participants/?q=3">هناك خمس شركات مصنعة</a> تعرض الآن أجهزة شبكات منزلية لها القدرة على استخدام IPv6 بشكل افتراضي وتتوافر بأسعار منخفضة ومتوسطة. ويأتي ذلك زائدًا عن <a href="http://mydeviceinfo.comcast.net/?s=i&#038;so=1&#038;e=0&#038;d3=0&#038;tier=-1&#038;sc=310">منتجات مودم الكابل القادرة على استخدام IPv6 وعددها 17</a> المتوفرة حاليًا.</p>
<p>وتتوافر الآن جميع الأجزاء اللازمة لنجاح استخدام IPv6 لدى مستخدمي إنترنت العملاء.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/06/ipv6-%d9%85%d8%b9%d8%b7%d9%84-%d8%aa%d9%85%d8%a7%d9%85%d9%8b%d8%a7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jeff Moss Goes to Moscow</title>
		<link>http://blog.icann.org/2012/05/jeff-moss-goes-to-moscow/</link>
		<comments>http://blog.icann.org/2012/05/jeff-moss-goes-to-moscow/#comments</comments>
		<pubDate>Sat, 19 May 2012 02:21:13 +0000</pubDate>
		<dc:creator>Veni Markovski</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[Cyber Security]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Global Partnerships]]></category>
		<category><![CDATA[Languages]]></category>
		<category><![CDATA[Russia and CIS]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=3945</guid>
		<description><![CDATA[ICANN&#8217;s vice president and CSO, Jeff Moss, visited Moscow for the 3rd Russian Internet Governance Forum. He was the keynote speaker at the Russian IGF, but the local organizers, the Russian Coordination Center for the .ru ccTLD decided to use him even more, and invited Jeff also to join a panel discussion on DDoS attacks, [...]]]></description>
				<content:encoded><![CDATA[<p>ICANN&#8217;s vice president and CSO, Jeff Moss, visited Moscow for the 3rd <a href="http://www.rigf.ru">Russian Internet Governance Forum</a>.</p>
<p>He was the keynote speaker at the Russian IGF, but the local organizers, the Russian Coordination Center for the .ru ccTLD decided to use him even more, and invited Jeff also to join a panel discussion on DDoS attacks, with <a href="http://rigf.ru/en/prog/bio.php?id=32">Natalia Kaspersky</a> and <a href="http://rigf.ru/en/prog/bio.php?id=31">Andrea Rigoni</a>.</p>
<p>At the panel, Jeff spoke after some other prominent panelist, who discussed the topic &#8220;Combat with cybercrime: cooperation and collective initiatives&#8221; – like Michel Moren, Acting Assistant Deputy Director, INTERPOL and Alexey Moshkov, Head of the Bureau for Special Technical Measures of Department &#8220;K&#8221; of the Ministry of Interior of Russian Federation, Police Major General. Full program of the event (in English) is at <a href="http://rigf.ru/en/prog/">their web site</a>.</p>
<p>After the panel was over, and without giving Jeff a break, the Minister of telecom and mass communications, I.O. Schegolev, invited Jeff to officially open the 23rd international exhibition SvyazExpoCom. Jeff was in a good company – besides the Russian minister, the other dignitaries, who spoke at the opening of the exhibition included Slovenian member of the cabinet <a href="http://www.zturk.com/">Ziga Turk</a>, ITU deputy Secretary-General <a href="http://www.itu.int/plenipotentiary/2006/newsroom/elections/bios/zhao/index.html">Houlin Zhao</a>, and the deputy-chairman of the Russian Chamber of Commerce <a href="http://ru.wikipedia.org/wiki/%D0%A1%D1%82%D1%80%D0%B0%D1%88%D0%BA%D0%BE,_%D0%92%D0%BB%D0%B0%D0%B4%D0%B8%D0%BC%D0%B8%D1%80_%D0%9F%D0%B5%D1%82%D1%80%D0%BE%D0%B2%D0%B8%D1%87">Vladimir Strashko</a>. Interesting moment, and hardly with equivalent, was that Jeff&#8217;s speech was translated by the deputy-minister of communications (sic!).</p>
<div style="float: left; margin: 0.5em 1em 1em 0;"><a href="/wp-content/uploads/2012/05/jeff-moss-RIGF-2012.jpg"><img src="/wp-content/uploads/2012/05/jeff-moss-RIGF-2012.jpg" style="width: 275px; border: 0;" alt="Jeff Moss" /></a></div>
<p>After the opening of the exhibition, Jeff was rushed back to the main plenary hall, where hundreds of people were patiently waiting to hear his keynote (video to be posted soon).</p>
<p>I won&#8217;t write here about the presentation, but will note that after it was over, we had a number of meetings, one after the other, until late at night, with people from across the Internet specter – from law-enforcement, through academia, through business and non-profit, and government representatives.</p>
<p>Here&#8217;s what the CEO of the Russian Coordination Center for the .ru ccTLD, Andrei Kolesnikov, wrote about Jeff&#8217;s presentation and interaction with the participants at the event:</p>
<p>&#8220;Having spoken with a number of our guests, including government representatives and professionals, I am pleased to let you know everyone cited your presentation as a candid and provocative account which helped raise awareness of critical challenges in the cybersecurity area and ways to address them.&#8221;</p>
<p>I can also confirm that this opinion was indeed shared by many.</p>
<p>The Russians now want Jeff to visit again, and not only for a one day stay, but to stay longer. Some are already asking if he could join, in 2013, the 16th <a href="http://www.rif.ru">Russian Internet Forum</a>, or the 20th Relarn Internet geeks boat cruise on the Volga river.</p>
<p>I am thinking, &#8220;Maybe I should recommend him to take part in both!&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2012/05/jeff-moss-goes-to-moscow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Status Report on the DNS in Egypt</title>
		<link>http://blog.icann.org/2011/01/status-report-on-the-dns-in-egypt/</link>
		<comments>http://blog.icann.org/2011/01/status-report-on-the-dns-in-egypt/#comments</comments>
		<pubDate>Mon, 31 Jan 2011 21:17:48 +0000</pubDate>
		<dc:creator>Rod Beckstrom</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=1977</guid>
		<description><![CDATA[Along with the entire global Internet community, ICANN is watching the events unfolding in Egypt with great concern for the safety of the people of Egypt and for their ability to use the Internet. On January 27, most Internet connectivity to Egypt was shut down, apparently on the instruction of the national government. This has [...]]]></description>
				<content:encoded><![CDATA[<p>Along with the entire global Internet community, ICANN is watching the events unfolding in Egypt with great concern for the safety of the people of Egypt and for their ability to use the Internet. On January 27, most Internet connectivity to Egypt was shut down, apparently on the instruction of the national government. This has led to the inaccessibility of the main domain name system (DNS) server of the Egyptian ccTLD (.eg).</p>
<p>Egypt&#8217;s top-level domain .eg is operated by the Egyptian Universities Network (EUN) (<a href="http://www.iana.org/domains/root/db/eg.html">http://www.iana.org/domains/root/db/eg.html</a>). The Arabic script top-level domain .masr (مصر, <a href="http://www.iana.org/domains/root/db/xn--wgbh1c.html"> http://www.iana.org/domains/root/db/xn--wgbh1c.html</a>) is operated by the National Telecommunication Regulatory Authority of Egypt (NTRA) (<a href="http://www.iana.org/domains/root/db/xn--wgbh1c.html">http://www.iana.org/domains/root/db/xn--wgbh1c.html</a>).</p>
<p>The primary servers they operate have been inaccessible to those outside of Egypt since January 27. Secondary DNS servers for .eg, located in Austria and the United States, have continued to function with data provided before the shutdown.</p>
<p>The .مصر DNS servers are exclusively in Egypt and there do not appear to be any secondary DNS servers outside the country. This means that service to sites served by this top-level domain are unreachable by the rest of the world.</p>
<p>Secondary servers copy their data from the primary server at regular intervals. Data in the secondary DNS servers, serving anyone in the world wishing to receive .eg DNS services, have an expiration date. Secondary servers require regular updating from the primary server at specified intervals &ndash; called &#8220;time to live&#8221; (TTL) &ndash; and that time is set to expire in 140 days.</p>
<p>Normally when primary servers fail &ndash; for example, following the earthquake in Haiti &ndash; the operator wants secondary servers to continue operating with the last zone file they had provided. This allows users around the world to connect to functioning servers in their zone.</p>
<p>ICANN&#8217;s Manager for Regional Relations for the Middle East has been communicating with both TLD operators, EUN and NTRA. The operators of .eg have communicated with ICANN and through ICANN are communicating with the secondary operators outside the country. They have requested that the secondary operators continue using the existing zone files past their time to live timeframes, if necessary.</p>
<p>This experience offers a number of lessons, among them that a policy to encourage the establishment of secondary servers to promote continuity of service as well as DNS stability could be useful and in the global public interest. ICANN will ask the ccNSO to consider proposing a policy to address this type of situation.</p>
<p>ICANN helps to ensure a secure and stable global Internet through its coordination of the domain name system, and is the global policy development body for the DNS and related matters. More than 100 ccTLD operators are voluntary members of the Country Code Names Supporting Organization (ccNSO), a formal ICANN policy and coordination body.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2011/01/status-report-on-the-dns-in-egypt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Russian IDN ccTLD .рф Opens for Registrations, Makes History</title>
		<link>http://blog.icann.org/2010/11/russian-idn-cctld-%d1%80%d1%84-opens-for-registrations-makes-history/</link>
		<comments>http://blog.icann.org/2010/11/russian-idn-cctld-%d1%80%d1%84-opens-for-registrations-makes-history/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 20:58:04 +0000</pubDate>
		<dc:creator>Veni Markovski</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Fast Track]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Languages]]></category>
		<category><![CDATA[Russia and CIS]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=1872</guid>
		<description><![CDATA[November 11, 2010, marked the day when the new IDN ccTLD .рф (Cyrillic for Российская Федерация, Russian Federation) was opened for general registration. Prior to that date the registration was open only for trademark owners and governmental institutions. Before the registration started, in an interview for the КоммерсантЪ (Commersant) daily, Andrey Kolesnikov, CEO of the [...]]]></description>
				<content:encoded><![CDATA[<p>November 11, 2010, marked the day when the new IDN ccTLD .рф (Cyrillic for <strong>Р</strong>оссийская <strong>Ф</strong>едерация, <strong>R</strong>ussian <strong>F</strong>ederation) was opened for general registration. Prior to that date the registration was open only for trademark owners and governmental institutions.<br />
Before the registration started, in an interview for the <a href="http://www.kommersant.ru/doc.aspx?fromsearch=2f46dc57-3df7-4ab4-b069-e5457c3e3104&#038;docsid=1536648">КоммерсантЪ</a> (Commersant) daily, Andrey Kolesnikov, CEO of the Coordination Center for .ru and .рф, said that they expect to have about 100,000 domain names registered by the end of the year. </p>
<p>It turned out they needed less than three hours to reach to the <strong>100,000 domain names</strong>! Such a gold rush was not expected, and numbers continued to grow &#8211; 200,000 within 6 hours from the beginning of the registration period. And more than 460,000 by today. </p>
<ol>
The registration process, which clearly exceeded (and continues to exceed) all expectation, includes some interesting details, for example there is a list of 4023 words, which are not allowed for registration. The so-called &#8220;black list&#8221; contains variations of all different vulgar words, known in the Russian language. However, users have already found ways to bypass it, with simply adding another word in front, or after the blacklisted words.</ol>
<p>We&#8217;ll be waiting to hear more on the history and the development of the Russian IDN ccTLD during the <a href="http://cartagena39.icann.org/">ICANN meeting in Cartagena</a>, where several of the Russian ccTLD top management people will be present.<br />
And we&#8217;ll prepare a posting on that topic, with more details for the general public. We hope that these details might be helpful in the launch of other new TLDs. </p>
<p>There are hundred of publications in the Russian central media, and even more all over the web, with people sharing opinions about who might be these registrants, why there are so many domains registered, and what does the fact of so many domains mean for the Russian Internet. It will be also interesting to see in exactly one year how many of these domains will be renewed. But certainly the Russian IDN ccTLD has made history. </p>
<p><strong>More on the Russian ccTLD Coordination Center <a href="http://cctld.ru/ru/">here</a> (in Russian). </p>
<p>Statistics from the Russian IDN ccTLD <a href="http://cctld.ru/ru/statistics/rfdomains.php">here</a> (in Russian).</p>
<p>More on the ICANN IDN program <a href="http://www.icann.org/en/topics/idn/">here</a>.</strong></p>
<blockquote><p><em><strong>Interesting background information </strong><br />
The Cyrillic IDN ccTLD started as an idea, discussed during the meeting of the Bulgarian President Georgi Parvanov with his Russian colleague President Vladimir Putin on January 18, 2008 in Sofia, Bulgaria. The Bulgarian President&#8217;s office <a href="http://www.president.bg/news.php?id=4088">published</a> last week the transcript from that meeting. Asked by President Putin, the Russian foreign minister responds, &#8220;As for the usage of Cyrillic in the Internet, our experts have already reviewed these issues, we have contacts with the international structures [ICANN], now we are solving the technical questions and the contacts between our specialists on that issue, of course, will confirm our commitment that Cyrillic should be used in the domain names. As for the consultations, as a whole, we are very happy from our cooperation [between Russia, Bulgaria, and ICANN].&#8221;</em></p></blockquote>
<p><strong>UPDATE FROM November 18, 2010:</strong><br />
As of today, November 18, the number of domains in .рф (.rf IDN ccTLD) passed half a million. As the Coordination Center <a href="http://cctld.ru/ru/press_center/news/news_detail.php?ID=1076">announced</a>, the 500000th domain registered was металлоконструкции74.рф (xn--74-6kctqamahahrlb5apjiu5d.xn--p1ai – in puny-code). This number brings .рф on 17th place among all European domains. Domains, which were delegated, or a working, account to more than 162,000. Most of them are already used in advertising, not only as single words, but as whole phrases, which are easy for the Russian speaker to understand.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2010/11/russian-idn-cctld-%d1%80%d1%84-opens-for-registrations-makes-history/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>
