<?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; IDNs</title>
	<atom:link href="http://blog.icann.org/tag/idns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Mon, 09 Jan 2012 15:53:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>أسماء النطاقات الدولية الأولى</title>
		<link>http://blog.icann.org/2010/05/%d8%a3%d8%b3%d9%85%d8%a7%d8%a1-%d8%a7%d9%84%d9%86%d8%b7%d8%a7%d9%82%d8%a7%d8%aa-%d8%a7%d9%84%d8%af%d9%88%d9%84%d9%8a%d8%a9-%d8%a7%d9%84%d8%a3%d9%88%d9%84%d9%89/</link>
		<comments>http://blog.icann.org/2010/05/%d8%a3%d8%b3%d9%85%d8%a7%d8%a1-%d8%a7%d9%84%d9%86%d8%b7%d8%a7%d9%82%d8%a7%d8%aa-%d8%a7%d9%84%d8%af%d9%88%d9%84%d9%8a%d8%a9-%d8%a7%d9%84%d8%a3%d9%88%d9%84%d9%89/#comments</comments>
		<pubDate>Thu, 13 May 2010 11:31:04 +0000</pubDate>
		<dc:creator>Baher Esmat</dc:creator>
				<category><![CDATA[Global Partnerships]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Languages]]></category>
		<category><![CDATA[العربية]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=1639</guid>
		<description><![CDATA[شهد يوم الأربعاء 5 مايو 2010 إدراج أول ثلاثة أسماء نطاقات عليا دولية لرموز الدول في منطقة الجذر الخاصة بنظام أسماء النطاقات مما يعني أن تلك الأسماء يمكن استخدامها على الإنترنت.‏ الدول الثلاث التي تم إضافة رموزها الدولية في نفس اللحظة إلى منطقة الجذر هي: • المملكة العربية السعودية • جمهورية مصر العربية • دولة [...]]]></description>
			<content:encoded><![CDATA[<div style="text-align: right">
شهد يوم الأربعاء 5 مايو 2010 إدراج أول ثلاثة أسماء نطاقات عليا دولية لرموز الدول في منطقة الجذر الخاصة بنظام أسماء النطاقات مما يعني أن تلك الأسماء يمكن استخدامها على الإنترنت.‏ الدول الثلاث التي تم إضافة رموزها الدولية في نفس اللحظة إلى منطقة الجذر هي:<br />
•	المملكة العربية السعودية<br />
•	جمهورية مصر العربية<br />
•	دولة الإمارات العربية المتحدة<br />
وبالتالي لا يوجد هناك أول اسم نطاق عربي على الإنترنت بل إن أسماء النطاقات بدأت تظهرعلى الإنترنت بالأحرف العربية مسجلة تحت النطاقات العليا (.السعودية)، (.امارات)، (.مصر) متزامنة مع إدراج هذه النطاقات العليا في منطقة الجذر الخاصة بنظام أسماء النطاقات، فبمجرد أن انتهت عملية الإدراج أصبح هناك وبشكل آلي عناوين عربية تحت النطاقات العليا الثلاثة مفعلة وقابلة للاستخدام من أي مكان في العالم.<br />
ويعد هذا أحد الإنجازات المهمة في تاريخ الإنترنت، وتتويج لعمل شاق تم إنجازه من قبل مجموعات مختلفة في جميع أنحاء العالم، بما في ذلك العمل التقني الذي قام به فريق عمل هندسة الإنترنت لتطوير بروتوكولات أسماء النطاقات الدولية، وكذلك الهيئات التي عملت على وضع وتطوير السياسات. وتود الآيكان أن تشكر جميع من شارك في تحقيق هذا الإنجاز، وتتطلع إلى رؤية المجموعة التالية من أسماء النطاقات الدولية لرموز الدول وقد تم إضافتها إلى منطقة الجذر واستخدامها من قبل مستخدمي الإنترنت في العالم. ‏  </p>
<p>لكن الأهم من ذلك تقديم التهاني إلى كل من شارك في هذا الإنجاز من الدول الثلاث وساهم في ظهور هذه الأسماء على الإنترنت:	(.السعودية) و(.امارات) و(.مصر). ‏
</p></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2010/05/%d8%a3%d8%b3%d9%85%d8%a7%d8%a1-%d8%a7%d9%84%d9%86%d8%b7%d8%a7%d9%82%d8%a7%d8%aa-%d8%a7%d9%84%d8%af%d9%88%d9%84%d9%8a%d8%a9-%d8%a7%d9%84%d8%a3%d9%88%d9%84%d9%89/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Next Generation Internet Users?</title>
		<link>http://blog.icann.org/2009/11/next-generation-internet-users/</link>
		<comments>http://blog.icann.org/2009/11/next-generation-internet-users/#comments</comments>
		<pubDate>Sat, 14 Nov 2009 18:16:03 +0000</pubDate>
		<dc:creator>Tina Dam</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Fast Track]]></category>
		<category><![CDATA[Global Partnerships]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=1191</guid>
		<description><![CDATA[As we (at ICANN staff) have been preparing for the Fast Track launch, for tomorrow, it was suggested to me that I write a blog post about it. I could have written about all the hard work, the long hours, the aggressive testing of the online system, keeping it simple and yet flexible for all [...]]]></description>
			<content:encoded><![CDATA[<p>As we (at ICANN staff) have been preparing for the Fast Track launch, for tomorrow, it was suggested to me that I write a blog post about it. I could have written about all the hard work, the long hours, the aggressive testing of the online system, keeping it simple and yet flexible for all expected participants to find it useful for exactly their purpose. Not to mention the work ahead of us and the already  tireless hours put in by so many around the world that if I start listing you I’d run out of space – and how amazing it has been to be a part of this new development <img src='http://blog.icann.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Instead I have decided to post the letter below. Samira is a real person She is a little girl from a village in a developing country. She has one thing in common with many others &#8211; she has no access to the Internet (they do have radio). But while her Internet problems start at a different place than IDNs, I am confident that IDNs at some point soon will make it easier for her to learn about the Internet and also make it easier for her to use it. Samira will have to wait for the postal delivery of this letter – but then there is nothing like getting that kind of mail too <img src='http://blog.icann.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Other than that I just like to say that I hope the Fast Track launch goes smoothly, and that it will work favorable for all participants. But most of all I hope that we with this launch will treat IDNs carefully and with the respect it deserves, and that we will continue to work together across time-zones and cultures, because afterall, what is the Internet if it does not work well for many years and users to come.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
Dear Samira,<br />
Tomorrow is  BIG BIG day for many people around the world and I decided to share it with you.</p>
<p>I know you have not seen the Internet yet, but as you grow up and you do, maybe you will recall this letter and an exciting time. What is the Internet? Well, it’s like this big box of information, pictures, games – you can read and also write about anything you like. it could be about peasants, your favorite food, toy, and you know what? You can even listen to the radio on the Internet.  Only your imagination sets a limit for the Internet. Have you ever looked under water? It&#8217;s  like an entire new world down there, so different than on land. The Internet is kind of like that – a different world &#8211; only bigger and it has information about under-water and land in it….anything you can imagine <img src='http://blog.icann.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>And every page on this Internet has an address. You know, just like you know how to explain where you live. It is made that way so that I can tell you an address and you can then go to that address and read my letter to you, or look at a picture I placed there for you to see. All these addresses have only been able to be written in the Roman alphabet….yes sounds a little weird, but that is just all those letters you see me write here.</p>
<p>Guess what happens tomorrow? Countries around the world – your country too &#8211; will be able to get a new address on the Internet. The most exciting thing is that this new address can be in almost any letters you like. So you can use your own language for an address for you. Then your friends and family can use that address and see what you are putting on the Internet. So it will be easier for you and everyone you know to remember that address. I think you will be excited when you see how it works.</p>
<p>I know that even though you already know more than one language, you are soon going to begin learning English. English is the language I used to write this letter to you. Languages are so exciting and they change all the time. Sometimes it can be hard to keep up with, but I will tell you more about it in my next letter. Learning another  language is amazing and it will help you communicate with people around the world. I have made so many friends around the world who all have helped make the Internet change the way I tried to describe to you. They have all taught me something important about life that I will never forget. But it would not have worked if we did not speak a little bit of the same language. So I really hope that you will be enjoying learning a new language.</p>
<p>You know how you can write your language both by using the Roman alphabet, and also the Arabic one? Well, this Internet change is almost the same thing &#8211; now these addresses can be in either alphabet too! And the coolest thing about it is that there is only one to decide which alphabet to use, and that it YOU! It is your choice for you and you alone!</p>
<p>But please keep that in mind when you start using the Internet. Let me know when that is and I will help you get your own address to a place on the Internet, in your language. But remember that I am not able to read or write your language (although I wish) so it may be a little bit difficult for me in the beginning <img src='http://blog.icann.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  and I will need your help.</p>
<p>With the very best wishes to you and many many others in the next generation of Internet users. I know I am together with many people around the world when I say that I can’t wait to see what you will use it for and how you will change it over time too….</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2009/11/next-generation-internet-users/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Managing variants at the top-level</title>
		<link>http://blog.icann.org/2009/08/variations-on-a-theme-when-ae-becomes-%c3%a6/</link>
		<comments>http://blog.icann.org/2009/08/variations-on-a-theme-when-ae-becomes-%c3%a6/#comments</comments>
		<pubDate>Sat, 22 Aug 2009 00:58:15 +0000</pubDate>
		<dc:creator>Tina Dam</dc:creator>
				<category><![CDATA[ccTLDs]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Fast Track]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[gTLDs]]></category>
		<category><![CDATA[IDN]]></category>
		<category><![CDATA[native names]]></category>
		<category><![CDATA[tlds]]></category>
		<category><![CDATA[variant]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=1007</guid>
		<description><![CDATA[Variant top-level domains (TLDs) and how they are managed is one of the most hotly discussed topics we are facing at the moment. What are variant TLDs, you ask? Well, that&#8217;s where the discussion begins&#8230; ICANN&#8217;s staff is currently producing implementation plans for both the IDN ccTLD Fast Track Process and the New gTLD Process. [...]]]></description>
			<content:encoded><![CDATA[<p>Variant top-level domains (TLDs) and how they are managed is one of the most hotly discussed topics we are facing at the moment. What are variant TLDs, you ask? Well, that&#8217;s where the discussion begins&#8230;</p>
<p>ICANN&#8217;s staff is currently producing implementation plans for both the IDN ccTLD Fast Track Process and the New gTLD Process. What guides that process for the topic of variants, is three things:</p>
<ol>
<li>Following the direction of policy advice already provided</li>
<li>Taking broader community needs into consideration, and</li>
<li>Ensuring the continued stability of the DNS and the namespace in general</li>
</ol>
<p>In the course of doing this for the issue of variant TLDs there were two different proposals.</p>
<p><span id="more-1007"></span>
<ol>
<li>Reserve desired variants &amp; block all other variants; and</li>
<li>Delegate desired variants &amp; block all other variants</li>
</ol>
<p>Following public comment periods on both proposed implementation methods (none were agreeable across the community), it was decided during the Sydney meeting this June that ICANN staff would seek implementation assistance from the community. This is usually the case on policies that have technical implications and hence are difficult to implement. </p>
<p>As a result a small team has been asked to volunteer their time (you can read more about that team and another issue the team is looking at in the post <a href="http://blog.icann.org/2009/08/solving-the-remaining-idn-issues/">Solving the remaining IDN issues</a>).</p>
<p>Community discussion on this topic is very important as we strive to reach a conclusion that works for all involved. Variant TLD management is especially important to make the introduction of IDNs work well for the end-users. The IDN Tables that hold and define the character variants are the most important piece of the management of variants, as these tables are developed to reduce the potential for confusion to end users by the introduction of IDNs.</p>
<p>In the <a href="http://www.icann.org/en/topics/idn/fast-track/proposed-implementation-details-idn-tables-revision-1-clean-29may09-en.pdf">most recent paper</a> [pdf] published on this topic, a variant is defined as follows:</p>
<blockquote><p>&#8220;Variant characters are two or more characters that are similar in appearance and result in two domain names to be visually confusing. </p>
<p>As such the resulting &#8220;variant strings&#8221; that are obtained by replacing the original characters with the variant characters, are visually indistinctible and, if used for separate purposes, could create user confusion. In some cases this could result in visually similar strings having the same meaning. </p>
<p>As such, the term &#8220;variant&#8221; designates orthographic equivalence on the character level, such as that between &#8220;æ&#8221; and &#8220;ae&#8221; in &#8220;encyclopædia&#8221; and &#8220;encyclopaedia&#8221;, but not in the broader sense that pertains to the variant spelling of words, as &#8220;encyclopaedia&#8221; vs. &#8220;encyclopedia&#8221; or &#8220;color&#8221; vs. &#8220;colour&#8221;. The IDN Tables that define variant characters are useful because they enable TLD registries to develop registration policies that will reduce the potential for confusion that could result from typographic similarities in domain names.</p></blockquote>
<p>Recent discussions have suggested that the definition might be better if more technical stringent (for example by following the <a href="//www.ietf.org/rfc/rfc3743.txt" target="_blank">definition</a> in the JET Guidelines: <em>&#8220;One conceptual character can be identified with several different Code Points in character sets for computer use&#8221;</em>) and then add various examples of variants, where some are confusingly similar visually and others are not.</p>
<p>The same paper proposed the following way of managing IDN TLD variants:</p>
<blockquote><p>&#8220;ICANN understands the need expressed in the community for enabling allocation of variant strings, in particular for locations where some users will key in one string and other users will key in the variant string when accessing for example a website. ICANN urges the community to continue to discuss and develop a technical solution that will enable the allocation of variant strings in the root zone in a stable manner. Until then IDN ccTLD Fast Track requesters will need to select one string per script or language only or alternatively wait until a technical solution has been found.</p>
<p>&#8220;In order to reserve the possibility of allocating variant strings to the appropriate entities, ICANN will ensure that all variant strings are reserved or blocked for allocation for now. Blocked strings will be considered as “existing strings” when incoming requests are checked for conflicts with existing TLDs. Therefore, any later request for the same string will be denied.&#8221;</p></blockquote>
<p>The reservation of desired variants was thought to be the safest way of securing adequate variant management until a solution has been found on how to manage them at the top level. The community response to the temporary solution was mixed. There is a concern in certain regions that a blocking of variants will disfranchise certain user communities. However, at the same time the response received stated that solving this problem should not in any way slow down the Fast Track introduction.</p>
<p>While we continue work on the subject with the industry experts, one thing seem to be clear: variant TLDs will be identified using of the IDN Tables that are required in either a Fast Track request or an IDN gTLD application. </p>
<p>This means that for the sake of the end-users, the usability of IDNs globally, and therefore the adoption of IDNs across applications on the Internet, we better get these tables right! </p>
<p>I have previously blogged about what could be the <a href="http://blog.icann.org/2008/11/compliance-with-idn-technical-requirements/">worst case scenario</a>. We really want to avoid this. We are in the last step of making IDN TLDs a reality for users globally which will be an amazing step for all involved.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2009/08/variations-on-a-theme-when-ae-becomes-%c3%a6/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>A quick guide to Sydney material</title>
		<link>http://blog.icann.org/2009/06/a-quick-guide-to-sydney-material/</link>
		<comments>http://blog.icann.org/2009/06/a-quick-guide-to-sydney-material/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 00:37:15 +0000</pubDate>
		<dc:creator>Kurt Pritz</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[gTLDs]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[Meeting]]></category>
		<category><![CDATA[Participation]]></category>
		<category><![CDATA[IRT]]></category>
		<category><![CDATA[new gTLDs]]></category>
		<category><![CDATA[Sydney]]></category>
		<category><![CDATA[trademark]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=822</guid>
		<description><![CDATA[Over the weekend, we published quite a bit of material. It was published now to meet a request by the Board and the community that we post three business weeks prior to the start of a meeting; these series of postings ensure that the bulk of materials being considered during Sydney will meet this goal.

With Sydney opening on Monday 22 June, we strived to have this information up before this morning, Monday 1 June.

As such, it is probably as comprehensive a set of documents as ICANN has published for any meeting - addressing hard issues on IDNs, an important report on intellectual property issues as related to domain names, another huge piece of comment and analysis related to new TLDs, new financial analysis, more on community travel (which is coming), and other areas. I’m also pretty confident that this is the earliest (relative to an ICANN meeting) that this kind of material has been available.]]></description>
			<content:encoded><![CDATA[<p>Over the weekend, we published quite a bit of material. It was published now to meet a request by the Board and the community that we post three business weeks prior to the start of a meeting; these series of postings ensure that the bulk of materials being considered during Sydney will meet this goal.</p>
<p>With Sydney opening on Monday 22 June, we strived to have this information up before this morning, Monday 1 June.</p>
<p>As such, it is probably as comprehensive a set of documents as ICANN has published for any meeting &#8211; addressing hard issues on IDNs, an important report on intellectual property issues as related to domain names, another huge piece of comment and analysis related to new TLDs, new financial analysis, more on community travel (which is coming), and other areas. I’m also pretty confident that this is the earliest (relative to an ICANN meeting) that this kind of material has been available.</p>
<p><span id="more-822"></span><strong>So what was included?</strong></p>
<p><em>IDNs:</em> We posted the <a href="http://www.icann.org/en/topics/idn/fast-track/draft-implementation-plan-cctld-clean-29may09-en.pdf">third revision</a> to the Fast Track Implementation Plan. This was accompanied by <a href="http://www.icann.org/en/announcements/announcement-31may09-en.htm#memoranda">explanatory memos</a> that discuss: the form of agreement we will have with IDN TLD operators, financial contributions to ICANN, and the use of variant tables. The bottom line – we plan to launch this process right after the meeting in Seoul.</p>
<p><em>New gTLDs:</em> We posted the <a href="http://www.icann.org/en/topics/new-gtlds/agv2-analysis-public-comments-31may09-en.pdf">Analysis of public comment</a>, as we did before the Mexico City meeting. This document is intended to demonstrate ICANN’s careful consideration of all the comment. We decided to not publish a new version of the Guidebook since the overarching issues are not yet resolved.</p>
<p>Instead, we have identified several areas where the Guidebook can be amended and published excerpts – just those sections that are changing. We also published explanatory memos: discussing whether Chinese, Japanese, and Korean TLDs should be allowed to <a href="http://www.icann.org/en/topics/new-gtlds/three-character-30may09-en.pdf">register one or two-character names</a> since complete words in those languages are generally that short; describing all the <a href="http://www.icann.org/en/topics/new-gtlds/morality-public-order-30may09-en.pdf">research</a> that has been done regarding morality &#038; public order issues; describing a process for <a href="http://www.icann.org/en/topics/new-gtlds/rrdrp-30may09-en.pdf">contractual compliance</a> in community-based TLDs; and advocating a <a href="http://www.icann.org/en/topics/new-gtlds/thick-thin-whois-30may09-en.pdf">requirement</a> that registries maintain thick Whois databases.</p>
<p><em>IRT and Trademark Protection:</em> The Implementation Recommendation Team was created by a resolution of the Board to develop solutions to trademark protection issues. The IRT made its <a href="http://www.icann.org/en/topics/new-gtlds/irt-final-report-trademark-protection-29may09-en.pdf">final report</a>, it was posted yesterday. The report represents a ton of work by the 18 members of the team for which we are very grateful.</p>
<p>As an ICANN staff member closely associated with this important and huge amount of work, I would like to thank everyone from staff and the community that worked so hard in making it possible to publish this in time for review and discussion in Sydney.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2009/06/a-quick-guide-to-sydney-material/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tell us what you think &#8211; public comment rundown</title>
		<link>http://blog.icann.org/2009/02/tell-us-what-you-think-public-comment-rundown/</link>
		<comments>http://blog.icann.org/2009/02/tell-us-what-you-think-public-comment-rundown/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 01:34:55 +0000</pubDate>
		<dc:creator>Kieren McCarthy</dc:creator>
				<category><![CDATA[ALAC]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[gTLDs]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[IDNs]]></category>
		<category><![CDATA[Participation]]></category>
		<category><![CDATA[.biz]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[domains]]></category>
		<category><![CDATA[Fast Track]]></category>
		<category><![CDATA[GNSO]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[Operating Plan]]></category>
		<category><![CDATA[public comment]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[single-character]]></category>

		<guid isPermaLink="false">http://blog.icann.org/?p=698</guid>
		<description><![CDATA[In the build up to every ICANN meeting, there is always a glut of public comment periods as reports are finished in time for the community to review them before discussing them in person.

Mexico City is no exception. Although this time, it is very much easier to get a quick overview of what is out from public comment from the front page of the ICANN website (the third box down on the right). Just to present you with another avenue to finding out about these public comment periods however, there are all listed below with quick explanations of what they are and the dates when they close.]]></description>
			<content:encoded><![CDATA[<p>In the build up to every ICANN meeting, there is always a glut of public comment periods as reports are finished in time for the community to review them before discussing them in person.</p>
<p>Mexico City is no exception. Although this time, it is very much easier to get a quick overview of what is out for public comment by looking at the front page of the ICANN website (the third box down on the right). </p>
<p>Just to present you with another avenue to finding out about these public comment periods, there are all listed below with quick explanations of what they are and the dates when they close.</p>
<p><span id="more-698"></span><strong>Open comment periods</strong></p>
<p>1. <strong>GNSO Constituency Renewals</strong>. Closes 25 FEB<br />
As part of the ongoing changes to ICANN&#8217;s main policy-making body, the GNSO, all the existing constituencies have put in submissions stating that they have followed the bylaws and so should be reconfirmed as valid constituencies. You are <a href="http://www.icann.org/en/public-comment/#gnso-constituency-renewals" target="_blank">free to comment on these submissions</a>.</p>
<p>2. <strong>IPv4 Global Policy</strong>. Closes 26 FEB<br />
We are running out of IPv4 address space and so ICANN has been working with the Regional Internet Registries (RIRs) to decide what system we follow as the addresses get more and more scarce. The policy here proposes that each RIR be allocated one &#8220;slash-8&#8243; &#8211; equating to roughly 16.7 million IP addresses &#8211; as soon as they are only five blocks left. If you have a comment on this <a href="http://www.icann.org/en/public-comment/#ipv4-policy" target="_blank">you can make it between now and 26 February</a>.</p>
<p>3. <strong>Single and Two-Character .BIZ Domains.</strong> Closes 15 MAR<br />
The company that runs the .biz registry, NeuStar, wants to make single and two-character domains available. Until recently, no registries were allowed to do this because of technical concerns. But those rules have relaxed over the past year or so. To be allowed to create, for example, i.biz, NeuStar has to change its contract with ICANN, and ICANN puts all contract changes out for public comment and review. So if you have an opinion about this, <a href="http://www.icann.org/en/public-comment/#biz-alloc-amendment" target="_blank">you can make it online</a>.</p>
<p>4. <strong>Geographic Regions Working Group Charter</strong>. Closes 24 MAR<br />
As an organization hoping to represent global stakeholders, ICANN has followed the common approach of splitting the world up into different regions in order to make things manageable. The problems is: where do you draw the lines? It may seem simple but the closer the issue is looked at, the more complex it becomes. So, in order to review what these regions are and who they include, ICANN has created a Working Group to go through all the issues and make recommendations at the end of it. The first step in that process is to create a charter for the group &#8211; outlining the scope and methodology that will be followed. This public comment period <a href="http://www.icann.org/en/public-comment/#regions-charter" target="_blank">opens that charter up to public review</a>. </p>
<p>5. <strong>Fast Track Proposed Solutions</strong>. Closes 6 APR<br />
The Fast Track is the process by which governments and the managers of different countries&#8217; registries will be able to apply for and receive versions of their country name in different languages scripts at the top-level of the Internet i.e. the part after the dot in a domain name. An example would be &#8220;China&#8221; in Chinese characters. These &#8220;internationalized domain names&#8221; or IDNs are being put out on the Internet for the first time as the technical issues that make it possible have only recently been resolved. </p>
<p>It is not a simple process by any means, so ICANN has been producing drafts of an &#8220;implementation plan&#8221; to make this process a reality. In this iteration, as well as the latest version of the Fast Track Implementation Plan, there will be three papers identifying specific issues that still need to be resolved. You can see all the papers in question and <a href="http://www.icann.org/en/public-comment/#update-idn-cctlds" target="_blank">make comments about them now and until 6 April</a>.</p>
<p>6. <strong>ALAC Review Final Report</strong>. Closes 17 APR<br />
ICANN regularly reviews of its main supporting organizations and advisory committees to make sure they remain relevant and in the correct format. The At Large Advisory Committee or ALAC exists to represent ordinary Internet users and it has been under review for roughly a year and the process is drawing to a close. A final report of the working group created to carry out much of the review has been released for its final piece of public comment before being formally submitted to a Board Committee that then puts it forward to a vote by the whole Board. So <a href="http://www.icann.org/en/public-comment/#alac-review" target="_blank">if you want your say on how ordinary Internet users should be represented</a> within the ICANN model, this is your last chance. Until the ALAC is reviewed again in a few years.</p>
<p>7. <strong>Operating Plan and Budget FY2010</strong>. Closes 30 APR<br />
People are constantly asking how much money ICANN has and how it decides where to spend it. What few people recognise however is that those decisions are heavily influenced by the community itself. Every year, ICANN runs through a public strategic planning process that outlines what the organization needs to do in the next year. It then turns that into an Operating Plan and from that devises its budget. The community is invited every year to provide their feedback on the process of where ICANN spends it money. This is a <a href="http://www.icann.org/en/public-comment/#op-budget-fy2010" target="_blank">comment period on the first version of the Operating Plan and Budget for ICANN&#8217;s 2010 financial year</a>. The comments from this will be used to revise the plan and budget and it will then be put out a second time before being approved by the Board in June.</p>
<p>And that&#8217;s it for now. Much of the community will be focussed on the revised Applicant Guidebook for new generic top-level domains that will come out in the next day or so, but please do not forget these other public comment periods. </p>
<p>You can view all open and recently closed public comment periods on one page, as well as an archive of older comment periods: <a href="http://www.icann.org/en/public-comment/" target="_blank">http://www.icann.org/en/public-comment/</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.icann.org/2009/02/tell-us-what-you-think-public-comment-rundown/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

