September 2006 - council - lists.icann.org

ICANN Releases Issues Paper for the July 2007 - June 2010 Strategic Plan
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 13, 2006

Sept. 13, 2006

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] ICANN Releases Issues Paper for the July 2007 - June 2010 Strategic Plan http://www.icann.org/announcements/issues-paper-08sep06.htm Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

CANCELLED: GNSO Council meeting 14 September 2006
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 13, 2006

Sept. 13, 2006

[council[at]gnso.icann.org] Dear Council Members, The GNSO Council Chair, Bruce Tonkin, who is currently off line, has asked me to inform the Council that he proposes cancelling the GNSO Council teleconference scheduled tomorrow, 14 September 2006, and rescheduling the meeting for Thursday 28 September 2006. The response from councillors indicates that there will be no quorum for the meeting tomorrow. Would you please inform me of your availability for the rescheduled date, 28 September 2006 at the usual time for Council teleconferences: 12:00 UTC, 5:00 LA, 8:00 Washington DC, 14:00 Brussels, 22:00 Melbourne. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

Re: [gtld-council] Outcome of discussion on string checks on Wed 30 Aug in Amsterdam
by Mawaki Chango Sept. 9, 2006

Sept. 9, 2006

I am not sure if the definition of "confusingly similar" provided here is clear enough to avoid contentious interpretations, and if it totally reflects the discussions in Amsterdam. To my recollection, at the end of the discussions there was a widely shared opinion that we should restrain the confusion criterion to typo-confusion (i.e., in what the user can see and what s/he can imply from it). As explained in the meeting, everything in the root servers, including IDN, is just ASCII-based codes (coding character strings), and I'm assuming that there is no risk for a root server to make confusion even if the coding strings differ only by one slight character. Thus, having no reason to assume probable massive confusions based on the possibility of a few user's mistakes (always possible in user behavior for whatever reasons), the security and the stability of the Internet wouldn't be at risk here. Mawaki --- Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> wrote: > Process for string checks: > > (1) Staff will make a determination and can engage appropriate > expert advice. > > (2) Public comment (which may include input from Governments or the > GAC) that is specific to the criteria for a new string. > > (3) If staff think there may be an issue, then it is put to a panel > of experts with appropriate background. > > > String criteria: > > (a) That the TLD string should not be confusingly similar to an > existing TLD string. Confusingly similar means there is a > likelihood of > confusion on the part of the relevant public. > > (b) The string must not infringe the legal rights of any third > party. > (consistent with current requirements of Registered Name Holder - > see > clause 3.7.7.9 of the gTLD registrar accreditation agreement) > > (c) The string should not cause technical issues (e.g not > .localhost, .exe etc) > > (d) The string should not be <controversial, political, cultural, > religious terms> (develop text related to public policy issues with > GAC) > > (e) The string should not be a reserved word. > > > Dispute resolution: > > (a) A dispute resolution process using independent arbitrators > where > existing registry operators could challenge a decision made by > ICANN > staff regarding whether or not a new gTLD string is confusingly > similar > to an existing gTLD string. If a string is successfully challenged > as > being misleadingly similar, then no operator may subsequently > register > it. > > (b) A dispute resolution process using independent arbitrators > where > existing trademark holders could challenge the string, based on > UDRP. > >

2 1

Re: [council] Purpose of Whois - informational materials
by Suzanne Sene Sept. 8, 2006

Sept. 8, 2006

apologies, maria, for failing to attach the australian statement to my earlier message. here it is, suz. >>> "Maria Farrell" <maria.farrell(a)icann.org> 9/8/2006 7:44 AM >>> Dear all, Attached are several Word documents that provide information requested by the GNSO Council on 26 July in the following resolutions: "(2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and governments." This information is provided in the document: SUMMARY OF INTERPRETATIONS OF THE DEFINITION OF WHOIS.doc .." (1) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers." This information is provided in the document: ccTLD registrant agreements.doc "The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers." This information is provided in the document: gTLD registrant agreementst purpose of Whois collection.doc "(3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service." This information is provided in the document: Uses of Whois data2006.doc All of this information will also be presented in html form and posted to the GNSO website to make it more easily accessible in the future. Best regards, Maria Farrell

1 0

Re: [council] Purpose of Whois - informational materials
by Suzanne Sene Sept. 8, 2006

Sept. 8, 2006

maria, thanks for the information/documentation. re the summary of comments and interpretations of formulation one, there are two small omissions that can be easily corrected. the first is to include the australian statement, shared with the gnso in April (copy attached). and the second refers to the opta presentation; as i noted in an earlier email, the "further comments" box should include the following: "opta is worried about the definition as recently preferred in the gnso and would suggest opening it up for debate to solutions to the following: more complex administrative processes; loss of time and efficiency; increased burden and costs on registrars; increase in international information requests; opta cannot enforce abroad. i cannot stress sufficiently the importance of the whois databases for opta and comparable institutions; it is the starting point of all our investigations". thanks, suz. Suzanne R. Sene Senior Policy Advisor NTIA/OIA 202-482-3167 (ph) 202-482-1865 (fax) >>> "Maria Farrell" <maria.farrell(a)icann.org> 9/8/2006 7:44 AM >>> Dear all, Attached are several Word documents that provide information requested by the GNSO Council on 26 July in the following resolutions: "(2) The ICANN staff will provide a summary of the other interpretations of the definition that have been expressed during the public comment period, and subsequently in correspondence from the public and governments." This information is provided in the document: SUMMARY OF INTERPRETATIONS OF THE DEFINITION OF WHOIS.doc .." (1) The ICANN staff will review a representative sample of cctld registry or cctld registrar agreements with registrants, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers." This information is provided in the document: ccTLD registrant agreements.doc "The ICANN staff will review a representative sample of registrar agreements with Registered Name Holders, taking into account the issues of geographical diversity and rule of law variances, to identify some of the purposes for which registrars collect Personal Data in the course of registering a domain name for their customers." This information is provided in the document: gTLD registrant agreementst purpose of Whois collection.doc "(3) The ICANN staff will summarise the current material that has resulted from WHOIS discussions since 2002 that document the current uses and abuses of the Personal Data that is currently made public through the WHOIS service." This information is provided in the document: Uses of Whois data2006.doc All of this information will also be presented in html form and posted to the GNSO website to make it more easily accessible in the future. Best regards, Maria Farrell

1 0

Revised wording to Council agenda item 7
by Philip Sheppard Sept. 8, 2006

Sept. 8, 2006

Council, please find enclosed a revised wording to the proposed resolution under item 7 of the next meeting. The only change is a copy and paste from the existing bylaws of the section on what the Board does after it gets a Council PDP report. It is of course necessary to keep this part (of bylaws annex A) within the bylaws. Philip

1 0

Schedule of Council meetings
by Bruce Tonkin Sept. 8, 2006

Sept. 8, 2006

Hello All, Please note that the schedule of Council meetings is available at: http://www.gnso.icann.org/calendar/ I assume that Council members will make an effort to note these dates in their diaries. I aim to issue agendas for meetings 7 days in advance, but the actual meeting date and time is announced well in advance. The upcoming dates are: 14 Sept 2006 19 Oct 2006 16 Nov 2006 2-8 Dec 2006 Regards, Bruce Tonkin

1 0

Draft GNSO Council Agenda for Thursday 14 September 2006
by Bruce Tonkin Sept. 7, 2006

Sept. 7, 2006

Draft Agenda for Council meeting - Thursday 14 September 2006 Coordinated Universal Time UTC 12:00 (5:00am Los Angeles, 8:00am Washington DC, 9:00am Buenos Aires, 13:00 London, 14:00 Brussels, 19:00 Phnom Penh, 22:00 Melbourne, 00:00 Auckland) Item 1: Update any statements of interest Item 2: Approval of Minutes - 20 July 2006 - 3 Aug 2006 Item 3: Correspondence - Clarification sought by PDP-Feb06 task force on whether the outcomes of the PDP would affect gTLD contracts in existance at the time the Board approves the policy. See http://www.gnso.icann.org/correspondence/cubberley-to-tonkin-25aug06.pdf Item 4: Proposed bylaws amendment to improve transparency with respect to contract approvals - update from General Counsel on action with respect to the GNSO request of 18 August 05 regarding proposed changes to ICANN bylaws to improve transparency with respect to contract approvals Item 5: Next steps with respect to IDNs - the proposed terms of reference on an IDN PDP was reviewed in the context of the draft recommendations for new gTLD arising from the Amsterdam meeting Item 6: Next steps for improving the GNSO structure and processes Taking into account the 2004 review of the GNSO Council, the about to be released review of the GNSO by the London School of Economics, and the experience of the Council, consider the next steps to identify changes to be made, and identify any changes required in the bylaws to allow these changes. Item 7: Motion proposed by Philip Sheppard Proposed GNSO resolution on revised PDP procedures - change to ICANN by-laws Whereas: Article X section 3.4 of the ICANN bylaws states: "The GNSO Council is responsible for managing the policy development process of the GNSO. It shall adopt such procedures as it sees fit to carry out that responsibility, provided that such procedures are approved by the Board, and further provided that, until any modifications are recommended by the GNSO Council and approved by the Board, the applicable procedures shall be as set forth in Section 6 of this Article". Article X section 6 of the bylaws states: "Initially, the policy-development procedures to be followed by the GNSO shall be as stated in Annex A to these Bylaws". Annex A of the bylaws contains procedures for the GNSO policy development process; Experience has shown that the procedures of Annex A are inappropriate for the work of the GNSO; Recommendation 5 of the 2004 GNSO Council review recommended changing the procedures; The ICANN by-laws are not the place for such procedures which may need to be re-visited frequently. The GNSO Council resolves: a) To request ICANN staff to draft a new set of procedures within 30 days reflecting the experience of previous PDPs and the recommendations of the Council review 2004; b) To request ICANN staff to submit those new procedures to Council for approval; c) To request ICANN staff to then inform the Board that the Council has adopted new procedures; d) and that therefore the Council requests the Board: - to approve its new procedures; - resolves to delete Article X section 6 and Annex A of the by-laws; - resolves to change section 3.4 to read: "The GNSO Council is responsible for managing the policy development process of the GNSO. It shall adopt such procedures as it sees fit to carry out that responsibility, provided that such procedures are approved by the Board." Item 8: Update on planning for Sao Paulo Item 9: Any other business Regards, Bruce Tonkin

1 0

MP3 recordings of new gTLD committee Amsterdam meeting 29-31 August 2006
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 6, 2006

Sept. 6, 2006

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] [To: gtld-council[at]gnso.icann.org] The MP3 recordings of the new gTLD committee (PDPDec05) meeting held in Amsterdam are online at: http://gnso.icann.org/calendar/#aug 29,30,31 August Face to face policy working group - PDPDec05, IDNs (Sheraton Airport Hotel, Amsterdam) * Mp3 (29 August) o Part 1 o Part 2 * Mp3 (30 August) o Part 1 o Part 2 o Part 3 * Mp3 (31 August) o Part 1 o Part 2 o Part 3 o Part 4 Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Council resolution new PDP procedures
by Philip Sheppard Sept. 6, 2006

Sept. 6, 2006

Fellow Council members, we have wittered on for years about the fact the PDP procedures are unsuited to the work of Council. I propose we do something about it. Nothing coming out of the LSE review of the GNSO (sic) will change the fact we need to change them. Bruce please see a proposed Council resolution for consideration at a forthcoming meeting. Philip

2 2