September 2005 - council - lists.icann.org

Re: [council] GNSO Council meeting proposed dates
by Your Name Feb. 15, 2006

Feb. 15, 2006

OK with me Tony Harris > Dear Councillors, > > These are proposed dates for Council meetings till the Vancouver meetings. > > Thursday 28 July 12:00 UTC > Thursday 18 August 12:00 UTC > Thursday 21 September 12:00 UTC > Thursday 20 October 12:00 UTC > Wednesday 16 November 19:00 UTC > > Please let me know if you have any questions. > > 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 > > --

4 5

.auDA WHOIS Policy Review
by Liz Williams Dec. 14, 2005

Dec. 14, 2005

Colleagues Some of you may be interested in this work. au: auDA WHOIS Policy Review - Aug 2005 auDA is currently holding a public consultation and reviewing the WHOIS Policy (2003-08). http://auda.org.au/reviews/whois-2005/ Regards. Liz Liz Williams Senior Policy Counselor ICANN - Brussels Tel: +32 2 234 7874 Fax: +32 2 234 7848 Mob: +61 414 26 9000

2 6

Proposed Amendment to .NET Registry Agreement for Public Comment
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 23, 2005

Sept. 23, 2005

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] ICANN Posts Proposed Amendment to .NET Registry Agreement for Public Comment. http://www.icann.org/announcements/announcement-22sep05.htm ICANN and VeriSign, the .NET Registry Operator, in consultation with representatives from ICANN-Accredited Registrars, have negotiated a proposed amendment to the .NET Registry Agreement. The proposed amendment limits registration fee increases to no more than 10% per year and incorporates a new version of the .NET Registry-Registrar Agreement. A summary of the .NET consultations is available at: <http://www.icann.org/announcements/announcement-2-22sep05.htm>. The public comment forum will be open through 10 October 2005. 22 September 2005 Submit comments on the Proposed Amendment to .NET Registry Agreement to: <net-amendment-comments(a)icann.org> You may view the submitted comments at: <http://forum.icann.org/lists/net-amendment-comments>. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

ICANN Regoinal Liaison: Jacob Malthouse
by Liz Williams Sept. 22, 2005

Sept. 22, 2005

Colleagues I said on the Council call today that ICANN's first Regional Liaison has been appointed. Jacob Malthouse is responsible for Canada and the Caribbean. He is based in the MdR office reporting to Theresa Swinehart. MF and I had a conference call with Jacob yesterday to give him a brief overview of the GNSO and we also discussed how the RL function could support the work of the GNSO especially in terms of outreach and building participation. If you have specific ideas about how the GNSO can make good use of the regional liaison initiatives, could you please let Maria Farrell know? She will funnel great ideas to Jacob which we can expect to see in action over the next few months. Liz Liz Williams Senior Policy Counselor ICANN - Brussels Tel: +32 2 234 7874 Fax: +32 2 234 7848 Mob: +61 414 26 9000

2 2

GNSO Council MP3 recording 22 Sept. 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 22, 2005

Sept. 22, 2005

[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/ICANN Board teleconference, held on September 22, 2005 at: http://gnso-audio.icann.org/GNSO-Council-20050922.mp3 http://www.gnso.icann.org/calendar/#sep Happy listening! -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Vancouver report
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 22, 2005

Sept. 22, 2005

[To: council[at]gnso.icann.org] Dear Council members, Please find some notes from the Vancouver planning meeting on 20 September 2005. Principle theme of the meeting was to identify difficulties and challenges in the scheduling and make sure that the requirements of all groups were known. The biggest issue was that a day has been removed from the schedule. In the last two ICANN meetings a day was added between constituency day and the public forum. It is a real challenge for the Vancouver meeting, because there are even more meetings scheduled than in the past. Diane has confirmed that Monday will be a working day for the GNSO - GNSO Councillors should plan to arrive in time to start work on Monday morning. There will be another logistics planning meeting at the end of next week to flesh out the details of the GNSO program. For now, here is the current essential information. - Tuesday November 29 morning - the GAC /GNSO WHOIS workshop - Wednesday November 30 - (tentative) DNSSEC deployment workshop, GAC, ALAC, ccNSO meetings. Apart from those nothing specified as yet. - Thursday December 1 - GNSO Constituency day, Opening ceremony - Prime minister of the Province of British Columbia has expressed an interest in coming. - Friday December 2 morning - (TENTATIVE) IDN workshop which is a joint effort with the GAC - Friday December 2 afternoon - Public Forum - Saturday December 3 morning - Public Forum - Sunday December 4 morning - Board meeting Other points to note are: Steve Crocker has also asked for a public meeting of the SSAC Committee presenting a report of their work, a general discussion on security and stability issues and an examination of glitches in the update process for the root, which may be placed late one afternoon/early one evening. ASO is going to meet with joint schedules There will be no separate WSIS session; reporting on what happened at the Summit will be done during the public forum. No information yet about the strategic/operational planning sessions. ICANN meetings are expanding and at the time the venue is chosen, the specifications fit. However 18 months later when the reality occurs there are more groups more workshops and the requests change. The plan is to have ongoing meetings with the "program" group to get into a planning mode that meets the needs of local hosts as well as community needs. Diane will have more time to be involved on an earlier and more regular basis. To improve meeting planning for the future, a face to face meeting of the program group is planned in Canada. The goal is to hear from the different groups what is not being done that should be done at ICANN meetings. I.e. does the workshop-type program and schedule meet the needs of the people coming to the meeting, or should the focus be on the constituencies, the supporting organisations, their meetings and their interactions between each other? Kind regards, -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

Issues report
by Bruce Tonkin Sept. 22, 2005

Sept. 22, 2005

>From ICANN bylaws: 2. Creation of the Issue Report Within fifteen (15) calendar days after receiving either (i) an instruction from the Board; (ii) a properly supported motion from a Council member; or (iii) a properly supported motion from an Advisory Committee, the Staff Manager will create a report (an "Issue Report"). Each Issue Report shall contain at least the following: a. The proposed issue raised for consideration; b. The identity of the party submitting the issue; c. How that party is affected by the issue; d. Support for the issue to initiate the PDP; e. A recommendation from the Staff Manager as to whether the Council should initiate the PDP for this issue (the "Staff Recommendation"). Each Staff Recommendation shall include the opinion of the ICANN General Counsel regarding whether the issue proposed to initiate the PDP is properly within the scope of the ICANN policy process and within the scope of the GNSO. In determining whether the issue is properly within the scope of the ICANN policy process, the General Counsel shall examine whether such issue: 1. is within the scope of ICANN's mission statement; 2. is broadly applicable to multiple situations or organizations; 3. is likely to have lasting value or applicability, albeit with the need for occasional updates; 4. will establish a guide or framework for future decision-making; or 5. implicates or affects an existing ICANN policy. f. On or before the fifteen (15) day deadline, the Staff Manager shall distribute the Issue Report to the full Council for a vote on whether to initiate the PDP, as discussed below.

1 0

ICANN Strategic Planning Process
by Bruce Tonkin Sept. 22, 2005

Sept. 22, 2005

Hello All, See note from Paul Twomey below. I proposed we schedule a GNSO Council meeting for Thursday 6 October 2005 to discuss the issues paper which will be available next week. We can then respond back to Paul by 15 October 2005. Regards, Bruce Tonkin -----Original Message----- From: Paul Twomey [mailto:twomey@icann.org] Sent: Thursday, 22 September 2005 4:58 PM To: Bruce Tonkin Subject: ICANN Strategic Planning Process Dear Bruce We are now in the middle of the ICANN strategic planning process for the 2006-2009 plan. In Luxembourg, the process was outlined, and a copy of that outline is attached. At present we are waiting for the response from the final SO/AC and hope to have the issues paper available next week. This puts us a little behind schedule, but not hopelessly so. The next step is to have the SOs, ACs and other members of the community respond to the issues paper. We will be asking for two elements in those responses. The first element will be an indication of whether the issues that have been identified in the issues paper are the correct issues. The issues paper is based on the input that was received from the consultation process. There will undoubtedly be places where the perspectives of members of the GNSO differ from some of the views of other members of the community. What we are looking for is a validation that the major issues have been covered and that the views of the GNSO are represented, not that you agree with everything that everybody said. Based on those issues, we would like the GNSO to identify what it believes the strategic priorities for ICANN should be, and, if possible, how ICANN should go about addressing those priorities. If the priorities really are to be priorities, there should be no more than five of them. Although it is a tight deadline, we would like to have those responses by 15 October. As mentioned in Luxembourg, we would then like to convene a meeting of the Chairs of the SOs and ACs (or their representatives) to agree on a common set of priorities. The arrangements for this meeting are still being finalised and we will let you know the details as soon as possible. Once these key strategic priorities have been formulated, they will be circulated for comment. Based on the feedback received, a draft strategic plan will be prepared for distribution in November. Further consultation will take place at the Vancouver meeting, with a view to having the Board approve a final version of the plan in January. Thank you for your assistance in the planning process. Regards, Paul

2 1

Draft Revised IDN Guidelines: Public Comment Period
by Bruce Tonkin Sept. 20, 2005

Sept. 20, 2005

From: http://www.icann.org/announcements/announcement-20sep05.htm Draft Revised IDN Guidelines: Public Comment Period 20 September 2005 ICANN has opened a 30-day public comment period on a draft revised version of the Guidelines for the Implementation of Internationalized Domain Names ("IDN Guidelines"). This draft reflects the experiences of the IDN registries in the implementation of Version 1.0 of the guidelines. Particular attention has been paid to concerns that have arisen about the deceptive use of visually confusable characters from different scripts in individual IDN labels. Analysis concerning such usage has been ongoing for several months and culminated when the IDN registries met during the ICANN meeting in Luxembourg. Some of the results from this meeting and from the Luxembourg IDN workshop (http://www.icann.org/meetings/luxembourg/idn-workshop-13jul05.htm ) have been reflected in the draft revised IDN Guidelines. This includes: * The registries will follow established authoritative language tables when such exist. * The registries will not permit the co-mingling of scripts in a domain label when no language table exists. * The successor document to the current guidelines must maximize the ability of a registry to support IDN in all regards where it is reasonably needed, and must minimize the ability for the abuse of IDN for deceptive purposes. * Policies based on script are needed in addition to those based solely on language, and developing script-based policies should be an immediate focus of action. Following the Luxembourg ICANN meeting, a working group of registries with IDN experience was formed to work on a revision of the guidelines, to be put forth for public comment. The working group includes the following members: * gTLD Registry Constituency Representatives: Cary Karp, MuseDoma Pat Kane, VeriSign Ram Mohan, Afilias * ccNSO Representatives: Hiro Hotta, JPRS Mohammed EL Bashir, .sd Registry * ICANN Staff: Tina Dam The revised version is now posted for public comments, and will subsequently be modified in accordance with commentary received. A final draft of version 2.0 will then be submitted to the ICANN Board for endorsement. The IDN Guidelines v.1.0 can be found here. http://www.icann.org/general/idn-guidelines-20jun03.htm The draft IDN Guidelines v.2.0 can be found here. http://www.icann.org/general/idn-guidelines-20sep05.htm Comments must be submitted by 19 October 2005, 23:00 UTC.

1 0

GNSO Council draft minutes teleconf 1 September 2005
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 19, 2005

Sept. 19, 2005

[To: council[at]gnso.icann.org] Dear Council members, Please find attached the draft minutes of the GNSO Council teleconference held on 1 September 2005. Please let me know what changes you would like made. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0