January 2012 - vip - lists.icann.org

FW: ICANN News Alert -- IDN Variant Issues Project: Draft Integrated Issues Report
by Naela Sarras Jan. 11, 2012

Jan. 11, 2012

Dear Colleagues, The Draft Integrated Issues Report is currently available for public comment. The public comment period was opened on 23 December 2011 and will run until 30 January 2012. We apologize about any confusion you may have had by receiving an interim version of the report sent to this list on 6 December 2011. This was a preliminary version of the report that was shared both to inform the list of progress and to seek input into the report before it is published for public comment. We have incorporated as many of your comments as possible into the draft Integrated Issues Report and now request that any additional comments you may have to be posted in the public comment forum, which will be used in considering changes in the Final Integrated Issues Report. The announcement and public comment forum can be accessed at: http://www.icann.org/en/announcements/announcement-2-23dec11-en.htm Best regards, Naela Sarras ICANN From: ICANN News Alert <communications(a)icann.org<mailto:communications@icann.org>> Date: Mon, 26 Dec 2011 15:52:18 -0800 To: Naela Sarras <naela.sarras(a)icann.org<mailto:naela.sarras@icann.org>> Subject: ICANN News Alert -- IDN Variant Issues Project: Draft Integrated Issues Report [http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/announcements/announcement-2-23dec11-en.htm ________________________________ IDN Variant Issues Project: Draft Integrated Issues Report 23 December 2011 IDN Variant Issues Project: Draft Integrated Issues Report Comment Period Deadlines (*) Important Information Links Public Comment Box<http://www.icann.org/en/public-comment/idn-vip-integrated-issues-23dec11-en…> Open Date: 23 December 2011 To Submit Your Comments (Forum)<mailto:idn-vip-integrated-issues@icann.org> Close Date: 30 January 2012 Time (UTC): 23:59 View Comments Submitted<http://forum.icann.org/lists/idn-vip-integrated-issues/> Section I: Description, Explanation, and Purpose On 20 April 2011, ICANN announced the IDN Variant Issues Project<http://www.icann.org/en/announcements/announcement-20apr11-en.htm> to explore the benefits and risks associated with the potential inclusion of IDN variant TLDs in the DNS root zone. This project was initiated in response to a 2010 ICANN Board of Directors resolution<http://www.icann.org/en/minutes/resolutions-25sep10-en.htm#2.5>. ICANN is publishing today for public comment<http://www.icann.org/en/public-comment/idn-vip-integrated-issues-23dec11-en…> the draft Integrated Issues Report<http://www.icann.org/en/topics/new-gtlds/idn-vip-integrated-issues-23dec11-…>, a study of the issues that this project has identified in relation to the management of IDN variant TLDs. It represents the result of the completion of the second phase of the project. The first phase involved the formation of six case study teams for the Arabic, Chinese, Cyrillic, Devanagari, Greek and Latin scripts. These teams were comprised of community experts with support by ICANN and worked on identifying issues related to IDN variant TLDs for each particular script, resulting in the publication in October of six individual reports<http://www.icann.org/en/announcements/announcement-4-03oct11-en.htm> detailing their findings. The second phase focused on integrating those six case study reports into the Integrated Issues Report. To complete this phase, ICANN formed a coordination team<http://www.icann.org/en/announcements/announcement-4-03oct11-en.htm> comprised of experts from each of the case study teams. The coordination team advised ICANN in completing the Integrated Issues Report, which summarizes and categorizes the various issues related to the identification and management of IDN variant TLDs. ICANN is now seeking community input on the issues discussed in this draft report. The report will be updated to reflect community feedback and the final Integrated Issues Report will be presented to the ICANN Board of Directors during their meeting at the ICANN public meeting in Costa Rica in March 2012. Following publication of the final Integrated Issues Report, ICANN will facilitate work toward determining the conditions under which certain types of variant TLDs could be implemented. Future work may also involve developing tools, processes, and protocols to support specific solutions, in cooperation with the appropriate experts. For the purpose of arriving at a determination on whether variant TLDs can be delegated, it is expected that the required work can be completed in calendar year 2012. Section II: Background On 25 September 2010 the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) directed the CEO "to develop an issues report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of gTLDs containing variant characters IDNs as part of the new gTLD process in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs." (http://www.icann.org/en/minutes/resolutions-25sep10-en.htm#2.5) In response, ICANN conducted six case studies of individual scripts to investigate any issues associated with delegating and using IDN variant TLDs that need to be resolved to facilitate a good user experience. The next phase focused on integrating those six case study reports into the draft Integrated Issues Report, which is being posted here for public comment. Section III: Document and Resource Links Documents posted for comment * The IDN Variant Issues Project: A Study of Issues Related to the Management of IDN Variant TLDs<http://www.icann.org/en/topics/new-gtlds/idn-vip-integrated-issues-23dec11-…> Additional Resources * The original Variant Issues Project proposal<http://www.icann.org/en/topics/new-gtlds/idn-variant-tlds-delegation-20apr1…> 20 April 2011. Section IV: Additional Information None Staff Contact: Kurt Pritz Email: kurt.pritz(a)icann.org<mailto:kurt.pritz@icann.org?subject=More%20information%20on%20the%20IDN%20Variant%20Issues%20Project:%20Draft%20Integrated%20Issues%20Report%20public%20comment%20period> (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. This message was sent to naela.sarras(a)icann.org<mailto:naela.sarras@icann.org> from: ICANN | 4676 Admiralty Way Suite 330 | Marina del Rey, CA 90292-6601 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=9827450&l=6333&s=2E94&m=869…>

7 19

Integrated Issues Report draft
by Karen Lentz Jan. 11, 2012

Jan. 11, 2012

Dear colleagues, As discussed last week, we are circulating for your information the current draft of the Integrated Issues Report, compiling all of the material created to date. We will circulate the section on User Experience issues (section 5.3.2 of the report) under separate cover shortly, so that we can begin discussing this set of issues. This draft of the report is intended to inform the team's discussions at the face-to-face meetings next week. All team members are requested to review and become familiar with the document prior to the meeting. We expect that discussions on the mailing list will continue in the interim. On this Wednesday's team call we will also discuss the agenda for the face-to-face meeting, and any suggestions for the agenda from the team based on the current draft are also welcome. Best regards, Karen Lentz ICANN

6 9

Re: [vip] ICANN variant project update
by SM Jan. 8, 2012

Jan. 8, 2012

At 14:41 04-01-2012, Andrew Sullivan wrote: >ICANN is eagerly soliciting comments, and I hope that those of you >interested in this topic will take the time to read the report and >send your observations. Having been a participant in this particular I browsed through the report. I found it difficult to understand. "if an email is sent to localpart(a)dname.example.com and that name has a DNAME that resolves to realname.example.com, the mail transport agent is not going to rewrite the server-part of the address." I have some doubts about whether the above is correct. "It might, however, be one important type of variant-inspiring behavior, because most of the deployed code today supports IDNA2003 and not IDNA2008." I did not find any comment in the report about how to reverse the trend. "The users of the DNS are varied in respect of what they expect, what they want, and what they need." This section lumps users and technical usage together. There is not much of a difference between Law enforcement and other security investigators and end users. Instead of System administrators and Software developers, it would have been clearer to discuss technical usage and the issues that may occur. "Similarly, any site renumbering and so on will require twice the effort" I don't see what site renumbering has to do with (DNS) strings. "These issues are noted in recent reports from ICANN's Security and Stability Advisory Committee (such as SSAC 051)" That's a report on "Domain Name WHOIS Terminology and Structure". Which name to call WHOIS is not an issue. "Areas of application behavior, resolution and registration services, WHOIS service, and business logic all need to be examined in order to determine if these objectives are achievable." This is buried deep within the report. There are some examples to illustrate how the Internet, which has been reduced to web and email, may be affected. The web examples are simplistic. The two words which stand out in the report are Cost and DNAME. The report emphasizes that there will be higher costs in all areas; i.e. an increase in revenue for anyone with an interest in the work, from ICANN or the software developer. DNAME might be read as the off-the-self "solution" to technical problems. Regards, -sm

3 4