October 2007 - council - lists.icann.org

New gTLD Workshop Agenda & Slide Presentation for Review & Comment
by Gomes, Chuck 17 Oct '07

17 Oct '07

The agenda and presentation for the New gTLD Workshop scheduled for Monday, 29 October in Los Angeles are attached for Council review and comment. Comments and questions are needed NLT Tuesday, 23 October, 21:00 UTC (11 pm CEST, 5 pm EDT, 2 pm PDT, 7 am Melbourne - next day). The New gTLD Workshop planning committee plans to finalize the slides at that time. Note that there are only placeholders for staff slides regarding implementation details. The plan is to discuss those slides with Council in our preparation meeting in L.A. Also note that the agenda file contains an abbreviated agenda and a detail agenda, the latter including the full principles, recommendations and implementation guidelines from the final report. Glen - The abbreviated agenda should be posted as soon as possible to as many sites as applicable (e.g., GNSO Master Calendar, ICANN Meetings Calendar, etc.). Please include links to the detailed agenda, the summary report and the full report if possible. Chuck Gomes "This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission."

1 0

FW: [Fwd: Sharing good news...]
by Gomes, Chuck 16 Oct '07

16 Oct '07

Glen kindly shared the following news and I would like to pass it on to the full Council and personally congratulate Norbert and compliment him for his excellent work. Chuck Gomes "This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission." -----Original Message----- From: GNSO.SECRETARIAT(a)GNSO.ICANN.ORG [mailto:gnso.secretariat@gnso.icann.org] Sent: Sunday, October 14, 2007 5:25 PM To: Gomes, Chuck; avri doria; Tina Dam Subject: [Fwd: Sharing good news...] Perhaps you have not been included on the list, but you may also like to share Norbert's news. Best wishes, Glen -------- Message original -------- Sujet: Sharing good news... Date: Sun, 14 Oct 2007 19:29:18 +0700 De: Norbert Klein <nhklein(a)gmx.net> Pour :: undisclosed-recipients:; Dear Friends and Colleagues, with this mail I would like to share the news - which came as a surprise to me, and only last week - that I received a medal from the Cambodian government in recognition of my cooperation towards the creation of the UNICODE codification for the Khmer script. I share this as my expression of thanks for all the encouragement and support that I have received from you over the years for the work to help as many people as possible to participate in the modern Information Society, including in their own language and script. I attach some pictures and a translation of the text, which is rather flowery. With my best greetings, Norbert Klein -- If you want to know what is going on in Cambodia, please visit us regularly - you can find something new every day: http://cambodiamirror.wordpress.com -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

4 3

Answer from John Jeffrey concerning proxy voting.
by Avri Doria 16 Oct '07

16 Oct '07

Hi, I received the following from John Jeffrey with permission to forward it on to the list. a.

1 0

ICANN Establishes Forum on Allocation Methods for Single-letter and Single-digit Domain Names
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 16 Oct '07

16 Oct '07

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/announcements/announcement-16oct07.htm ICANN Establishes Forum on Allocation Methods for Single-letter and Single-digit Domain Names 16 October 2007 As recommended by the GNSO Council, ICANN is commencing a forum on potential allocation methods for single-letter and single-digit domain names at the second level in gTLD registries. Examples include a.com, i.info, 4.mobi, 8.org. Since revenue will result from this allocation, comments regarding the potential uses for this revenue are also requested. ICANN intends to synthesize responses to the forum and present proposed methods for allocation of single-letter and single-digit domain names at the second level for community consideration. To be considered by ICANN, ideas on potential allocation methods should be submitted no later than 23:59 UTC, 15 November 2007 to allocationmethods(a)icann.org. Comments may be viewed at http://forum.icann.org/lists/allocationmethods/. The GNSO Council asked ICANN to initiate a forum on this issue after considering a report of the Council's Reserved Names Working Group (RN-WG), which recommended that “single letters and digits be released at the second level in future gTLDs, and that those currently reserved in existing gTLDs should be released. This release should be contingent upon the use of appropriate allocation frameworks. More work may be needed. In future gTLDs we recommend that single letters and single digits be available at the second (and third level if applicable).” The GNSO is one of ICANN's primary stakeholder-populated policy making bodies. The recommendations of the RN-WG can be found at http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.pdf [PDF, 713K]. Background Currently, all 16 gTLD registry agreements (.AERO, .ASIA, .BIZ, .CAT, .COM, .COOP, .INFO, .JOBS, .MOBI, .MUSEUM, .NAME, .NET, .ORG, .PRO, .TEL, and .TRAVEL) provide for the reservation of single-letter and single-digit names at the second level. ICANN’s gTLD registry agreements contain the following provision on single-letter and single-digit names. See Appendix 6 of the .TEL Registry Agreement, http://www.icann.org/tlds/agreements/tel/appendix-6-07apr06.htm (“the following names shall be reserved at the second-level: All single-character labels.”). Letters, numbers and the hyphen symbol are allowed within second level names in both top level and country code TLDs. Single letters and numbers also are allowed as IDNs -- as single-character Unicode renderings of ASCII compatible (ACE) forms of IDNA valid strings. Before the current reserved name policy was imposed in 1993, Jon Postel (under the IANA function) took steps to reserve all available single character letters and numbers at the second level for future extensibility of the Internet (see 20 May 1994 email from Jon Postel, http://ops.ietf.org/lists/namedroppers/namedroppers.199x/msg01156.html). All but six (q.com, x.com, z.com, i.net, q.net, and x.org) of the possible 144 single letters or numbers at the second-level in .COM, .EDU, .NET and .ORG remain reserved by IANA. Those six registrations are an exception to the reservation practice. Under current practice, these names would be placed on reserve if the registrations were allowed to expire. The RN-WG carefully considered technical implications of releasing single-letter and single-digit domain names from reservation, and engaged in discussions with technical experts as the working group recommendations were being developed. There are currently 265 TLDs in the root zone (19 gTLDs and 246 ccTLDs). Although nearly all single-letter and single-digit domain names are reserved in gTLDs, 24% of ccTLDs (60) have at least one single-character name registration. According to IANA, out of 9540 possible combinations of single-character ASCII names (containing 26 letters, 10 numbers, but not symbols, across 265 TLDs), 1225 delegations of single-character ASCII names exist in the root zone (See http://forum.icann.org/lists/gnso-rn-wg/msg00039.html). ICANN has received many inquiries from third parties seeking to register single-letter and single-digit domain names, and has advised these parties that the names are reserved. Through the establishment of the public forum described above, ICANN is following its bottom-up, multi-stakeholder model to develop suitable allocation mechanisms for the release of single-letter and single-digit domain names as recommended by the GNSO working group. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Update on Single-letter, Second Level Domain Names
by Patrick Jones 16 Oct '07

16 Oct '07

As noted in the GNSO Council minutes of 20 September 2007 (http://gnso.icann.org/mailing-lists/archives/council/msg03919.html), this is an update to the GNSO Council on the Staff implementation of the GNSO Reserved Names Working Group recommendations. Tomorrow, ICANN will commence a forum on potential allocation methods for single-letter, single-digit domain names at the second level in gTLD registries. The forum will be open until 23:59 UTC, 15 November 2007. Further information will be included in tomorrow's announcement. Work remains on ICANN/IANA names at the second level in existing gTLD registries, and an update will be provided to the GNSO Council. Regards, Patrick Patrick L. Jones Registry Liaison Manager Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Tel: +1 310 301 3861 Fax: +1 310 823 8649 patrick.jones(a)icann.org

1 0

My Name, My Language, My Internet: IDN Test Goes Live
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 15 Oct '07

15 Oct '07

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] My Name, My Language, My Internet: IDN Test Goes Live ICANN launches global test of Internationalized Domain Names http://www.icann.org/announcements/announcement-15oct07.htm MARINA DEL REY, Calif.: Internet users around the globe can now experiment with their name in their language on their Internet with today’s launch of the Internet Corporation for Assigned Names and Numbers live testing of Internationalized Domain Names in 11 languages. “This is one of the most exciting times yet in the development of IDNs,” said Dr Paul Twomey, ICANN’s President and CEO. “Internet users who speak the 11 languages of the test can play a key role in testing how IDNs operate, and help us move toward full implementation for all the languages of the world.” Internet users around the globe can now to access wiki pages with the domain name example.test in the 11 test languages -- Arabic, Persian, Chinese (simplified and traditional), Russian, Hindi, Greek, Korean, Yiddish, Japanese and Tamil. The wikis will allow Internet users to establish their own subpages with their own names in their own language -- one suggestion is: example.test/yourname. ICANN has also put a video explaining the evaluation process on YouTube, and available on the ICANN website. The wiki pages can be accessed by typing example.test in the characters of one of the 11 languages, or by going to http://idn.icann.org. “These wikipages are key to the test. We want to know how the URL displays in the Internet browser, if it works when you cut and paste it into the body of an email to a friend, and how all of this impacts the root zone,” Dr Twomey added. The 11 evaluation wikis will remain online until IDNs are fully implemented and the first top-level domain is introduced in the evaluation language. The full introduction of IDNs will mean that people can write the whole of a domain name in the characters used to write their own language. Presently you can only use these characters before the dot, so .com, .net, .org and the like can only be written in characters from basic Latin. IDNs will change this so that literally tens of thousands of characters will be available to the world. The "example.test" labels with the associated scripts, the languages that were used for translation of the two terms "example" and "test", and the A-labels for second and top level that are inserted in the IDN TLD zones and DNS respectively. Enjoy the videos! -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Reminder: Comments invited on reports and recommendations summarized in the Staff Overview of Recent GNSO WHOIS Activity.
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 15 Oct '07

15 Oct '07

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] Please note that the following two documents have been posted on page: http://gnso.icann.org/drafts/ Staff Overview of recent WHOIS activities http://gnso.icann.org/drafts/icann-staff-overview-of-whois11oct07.pdf Staff Implementation notes WHOIS working group report http://gnso.icann.org/drafts/gnso-whoiswg-report-staff-implementation-notes… Public comments are open on the WHOIS process until 30 October 2007. http://www.icann.org/public_comment/ Please submit comments to: <whois-comments-2007(a)icann.org> Comments may be viewed at: http://forum.icann.org/lists/whois-comments-2007/ Explanation: A Whois taskforce convened in June 2005 completed its work and sent a final report to the GNSO Council in March 2007. In that report, a majority of members endorsed a proposal called the "Operational Point of Contact" (OPOC) where a domain name registrant would be able to choose a third-party to appear in the public Whois information for this domain and the registrant’s contact details would no longer be displayed. Expanding on that work, the GNSO Council in March created a Whois working group to examine three issues and make recommendations on them: 1. To examine the roles, responsibilities and requirements of the OPOC, and what happens if they are not fulfilled; 2. To examine how legitimate interests will access unpublished registration data; and 3. To examine whether publication of registration contact information should be based on the type of registered name holder (legal vs. natural persons) or the registrant's use of a domain name. The working group's report [pdf] was published on 20 August 2007. On 6 September 2007, the GNSO Council approved a resolution for further public comment on the report with the intention to lead to a vote on the issue on 31 October 2007 during the Los Angeles ICANN meeting. The resolution called for ICANN staff to prepare a "draft final report" covering the Whois reports referenced above and called Staff Overview of Recent GNSO WHOIS Activity [pdf]. Public comments are invited on both of the GNSO Council's Whois reports and recommendations referenced above and summarized in the Staff Overview of Recent GNSO WHOIS Activity. Comments will be taken until 00:00 UTC (17:00 PDT) on 30 October 2007. Please take time to submit comments. Thank you. Kind regards, Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

GNSO Council teleconference MP3 recording 11 October 2007
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 12 Oct '07

12 Oct '07

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference, held on October 11, 2007 at: http://audio.icann.org/gnso/gnso-council-20071011.mp3 http://gnso.icann.org/calendar/#oct Happy listening! -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

RE: [Fwd: [council] GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues]
by Gomes, Chuck 12 Oct '07

12 Oct '07

I think it would be helpful to keep the redlining because it clearly shows what was changed from the WG document. It would be good on the draft documents oage and with the agends for 27 and 31. Chuck Sent from my GoodLink Wireless Handheld (www.good.com) -----Original Message----- From: GNSO.SECRETARIAT(a)GNSO.ICANN.ORG [mailto:gnso.secretariat@gnso.icann.org] Sent: Friday, October 12, 2007 12:33 PM Eastern Standard Time To: 'Council GNSO' Subject: [Fwd: [council] GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues] Chuck, This is very clear, thank you. Should we publish it on the draft document page, and for that purpose would you like the red portions to stay red? Thanks so much, Glen -------- Message original -------- Sujet: [council] GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues Date: Fri, 12 Oct 2007 09:29:15 -0400 De: Gomes, Chuck <cgomes(a)verisign.com> Pour :: Council GNSO <council(a)gnso.icann.org> Attached is the latest version of the proposed *GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues*. Please note that this version was created from the GNSO WG final draft by making the following two non-material edits: 1. An executive summary was added: a) to do this the first three paragraphs were made into an 'Introduction' section, including moving some text in the 3rd paragraph into the new 'Executive Summary'; b) the 'Executive Summary' was written by listing what appeared to be 'the most important points from the GNSO responses that are contained in the main body of the document'; c) the section containing the main body of the report (Parts A and B) was titled 'Responses to Issues Paper Questions'. 2. In Part A, paragraph 1, links were inserted to information about the IDN technical requirements and tests. For ease of identifying the revisions, they are highlighted in the attached file. In reviewing the Executive Summary I suggest asking the following questions: i) are all of the bulleted items points that should be included in the Executive Summary? and ii) are there any points not included that should be added? Note that the changes made in this version were sent to WG members for their review and comment and the changes made were result of the feedback received. If you have any questions, please let me know. This version of the draft comments should be used for discussion by the Council in L.A. Chuck Gomes "This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission." -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

[Fwd: [council] GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues]
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 12 Oct '07

12 Oct '07

Chuck, This is very clear, thank you. Should we publish it on the draft document page, and for that purpose would you like the red portions to stay red? Thanks so much, Glen -------- Message original -------- Sujet: [council] GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues Date: Fri, 12 Oct 2007 09:29:15 -0400 De: Gomes, Chuck <cgomes(a)verisign.com> Pour :: Council GNSO <council(a)gnso.icann.org> Attached is the latest version of the proposed *GNSO Comments in Response to the ccNSO-GAC Issues Report on IDN Issues*. Please note that this version was created from the GNSO WG final draft by making the following two non-material edits: 1. An executive summary was added: a) to do this the first three paragraphs were made into an 'Introduction' section, including moving some text in the 3rd paragraph into the new 'Executive Summary'; b) the 'Executive Summary' was written by listing what appeared to be 'the most important points from the GNSO responses that are contained in the main body of the document'; c) the section containing the main body of the report (Parts A and B) was titled 'Responses to Issues Paper Questions'. 2. In Part A, paragraph 1, links were inserted to information about the IDN technical requirements and tests. For ease of identifying the revisions, they are highlighted in the attached file. In reviewing the Executive Summary I suggest asking the following questions: i) are all of the bulleted items points that should be included in the Executive Summary? and ii) are there any points not included that should be added? Note that the changes made in this version were sent to WG members for their review and comment and the changes made were result of the feedback received. If you have any questions, please let me know. This version of the draft comments should be used for discussion by the Council in L.A. Chuck Gomes "This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission." -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0