December 2004 - council - lists.icann.org

GNSO Council Representatives from the Registries constituency
by Bruce Tonkin 03 Dec '04

03 Dec '04

-----Original Message----- From: Marie.Zitkova(a)sita.aero [mailto:Marie.Zitkova@sita.aero] Sent: Friday, 3 December 2004 9:14 AM To: Bruce Tonkin Cc: Glen Saint Gery Subject: GNSO Council Representatives Bruce I am pleased to report that the gTLD Registries constituency elected the following representatives to the GNSO Council seats vacated after the 2004 annual meeting: Ken Stubbs Philip Colebrook (for the third seat allocated to gTLD Registries Constituency providing the constituency retains 3 representatives in the Council) Best regards, Marie Zitkova Chair, gTLD Registries Constituency

1 0

GNSO Council Weblog
by Ross Wm. Rader 03 Dec '04

03 Dec '04

In response to suggestions made at our meeting earlier this week, I have taken the initiative to create a weblog for use by the Council (donation, freebie, no-strings attached, etc.). As suggested, I'd like to move forward with an experiment with Glenn's cooperation to post the notes from our minutes to the weblog on a regular basis. I will be sitting down with Glenn sometime this week to discuss the finer points and provide her with some training - if there is interest, I'd be happy to include others in this walkthrough as well. More details to follow as we figure out next steps, etc. -- -rwr Contact info: http://www.blogware.com/profiles/ross Skydasher: A great way to start your day My weblog: http://www.byte.org

4 4

Robin Gross - New appointee from the Non-commercial constituency to the GNSO Council
by Bruce Tonkin 03 Dec '04

03 Dec '04

-----Original Message----- From: Milton Mueller [mailto:mueller@syr.edu] Sent: Friday, 3 December 2004 9:18 AM To: gnso.secretariat(a)gnso.icann.org; jeffrey(a)icann.org; Bruce Tonkin Cc: ca(a)rits.org.br; marc(a)schneiders.org Subject: GNSO Council elections This is to inform you that Robin Gross has been elected to replace Jisuk Woo on the GNSO Council. --Milton Mueller, Chair NCUC

1 0

ANYONE WITH IM? (for alick)
by Amadeu Abril i Abril 03 Dec '04

03 Dec '04

folks for some reason my AIM-compatible chat software and Alick's refuse to talk. Is anyoen there taht could try to connect with him? Amadeu

1 1

Glen, do you or anybody else have an instant messenger up so Philip or I can send messages in lieu of phone? Thanks, Alick
by Alick Wilson 03 Dec '04

03 Dec '04

2 1

WIPO-II
by Paul Verhoef 03 Dec '04

03 Dec '04

All, Please find enclosed the letter and its annex from WIPO that we received last week. I understand there were some technical issues with getting it on the web-site but as soon as these are arranged it will go up, hopefully already today. I would like to offer my excuses for that. regards Paul ____________________________________ Paul Verhoef Vice President Policy Development Support ICANN 6 Rond Point Schuman, Bt.5 B-1040 Brussels, Belgium Tel.: +32.2.234 7872 Fax: +32.2.234 7848 www.icann.org

5 4

Dial in problem
by Alick Wilson 03 Dec '04

03 Dec '04

Hi everyone, I'm also on line. Glen, proxy to Amadeu if I get lost. Alick

1 0

RE: We are on dial in but can't hear anybody or see Real Player, please advise
by Alick Wilson 03 Dec '04

03 Dec '04

Hi everybody, Philip Colebrook and I are on dial in but aren't connected. Real Player is not working either. John Crain is on dial in line and trying to fix. Alick -----Original Message----- From: Steve Conte [mailto:conte@icann.org] Sent: Friday, 3 December 2004 9:48 p.m. To: alick.wilson(a)xendra.co.nz Cc: John Crain Subject: Re: We are on dial in but can't hear anybody or see Real Player, please advise Hi Alick, We're having some serious phone and connectivity issues in the auditorium. John Crain is in there (I'm doing the ccNSO meeting today) and hopefully things will stabilze. Steve At 12:40 AM 12/3/2004, you wrote: > --------------- Steve Conte - Technical Systems Administrator - ICANN conte(a)icann.org - www.icann.org +1 (310) 823 - 9358 x5829 PGP KeyID: E72D5F30

1 0

Proposed motion for Council meeting on Friday 3 Dec 2004
by Bruce Tonkin 02 Dec '04

02 Dec '04

Hello All, Here is a proposed motion for the Council meeting tomorrow. "Whereas at the ICANN meeting in Tunisia (October 2003) the Board resolved to change the transition article (Article XX) to allow three representatives per constituency on the GNSO Council until the end of the ICANN annual meeting 2004; and resolved to perform a review of the GNSO Council in or around July 2004 which should include among other aspects of the review criteria, an analysis of the efficacy of having three representatives from each constituency on the GNSO Council. Taking into account the draft of the external review report on the GNSO Council, and the Council's self-review, the GNSO Council requests that the ICANN Board extend the current arrangement of 3 representatives per constituency until the ICANN meeting in Mar del Plata, Argentina (April 2005). This will allow time for the external review to be completed following a public comment period, allow time for ICANN to announce a proposed change to the ICANN bylaws to allow three representatives per constituency on an ongoing basis, and allow an appropriate period for public discussion before changing the bylaws." Regards, Bruce

1 0

Updated self-review doc - version 2.2
by Bruce Tonkin 02 Dec '04

02 Dec '04

Hello All Attached is the latest version of the self-review document with the addition suggested by Niklas. Below is a plain text summary of the recommendations. Regards, Bruce Tonkin 10.1. Required changes to ICANN bylaws ======================================= 10.1.1. Maintain the present 3 representatives per constituency 10.1.2. Adjust the bylaws to specify that the timelines in the policy development process are guidelines, and allow the GNSO Council to set and revise timelines according to the level of consensus on a particular issue and the amount of volunteer and staff resources available for the specific issue. 10.2. Additional ICANN staff resources required =============================================== 10.2.1. Prior to the commencement of policy development on a particular issue, ensure that ICANN staff provide an analysis and Issues Paper that provides sufficient background and information to support the development of the Terms of Reference and statement of work for a Task Force. . The issue report should indicate how the issue is currently handled within the existing contractual and policy framework. In some instances, it may be necessary for Council to agree to commission an independent expert to analyse an issue (which may include interviewing affected parties within the GNSO) and propose options for policy recommendations that may address the issue. . 10.2.2. During the pubic comment process on a proposed policy recommendation, an independent expert may need to be commissioned to produce a report on the views of the GNSO community in relation to a proposed policy recommendation. 10.2.3. Provide staff support to the task forces and GNSO Council sub-committees that are skilled in creating reports that reflect the input provided by members of Council, and clearly identify where the areas of disagreement exist. 10.2.4. Provide staff support to the Task Forces and to the GNSO Council subcommittees that familiarize themselves with the bylaws and the policy development processes, as well as the relevant previous work of the Council. 10.2.5. Ensure that legal counsel is available for all GNSO Council calls, and ensure that legal counsel is available to task forces and subcommittees as required. With respect to policy development activity, ensure that the legal counsel is fully briefed on the existing contractual arrangements with registries and registrars that relate to the particular issue under discussion. 10.2.6. Prior to the development of a final policy recommendation for the GNSO Council, ICANN should ensure that the recommendation has been reviewed by legal counsel to ensure that the recommendation can be implemented and enforced via the relevant contracts. 10.2.7. Establish a project management process within ICANN that defines a plan and expected dates for implementation of a policy once it is approved by the ICANN Board. 10.2.8. Ensure that the mechanisms are established for monitoring and enforcing compliance with a new policy. This is particularly important in the first 6 months of a new policy, when registry and registrars systems are being modified to support a new policy. 10.2.9. ICANN staff develop a complaints handling process that is capable of logging complaints regarding gtld domain name registration practices, and capable of producing data on a trend basis. This data reporting would be useful on a monthly basis. 10.3. Actions required by the GNSO Council ========================================== 10.3.1. During the early public comment process, encourage members of the ICANN community to submit proposals for solutions to a particular issue. 10.3.2. Given that legal contracts between ICANN and registries and registrars may be open to different interpretation by the contracted parties. Ensure that legal advice from ICANN legal counsel (or external counsel to ICANN) is in writing, and allow affected parties (such as registrars and registries) to submit their own written legal advice for consideration by the GNSO community. 10.3.3. Ensure that the policy is ready for implementation after approval by the GNSO Council and ICANN Board. 10.3.4. As part of the Council report at the end of the policy development process, establish key metrics for measuring the success of the policy, and ensure that appropriate measurement and reporting systems are put in place. 10.3.5. To the extent that the lack of intermediate sanctions for non-compliance with contractual obligations presents a significant impediment to compliance activities, the GNSO should, without prejudice to efforts to enforce existing contractual obligations, develop recommendations for a system of graduated or intermediate sanctions for incorporation in revised contracts. As an initial step, ICANN legal counsel should brief GNSO Council (or a relevant subgroup/task force) on ICANN's current plans to correct ongoing harm and provide greater flexibility and legitimacy for the compliance function.

1 0