September 2006 - council - lists.icann.org

LSE's GNSO Review
by Denise Michel Sept. 15, 2006

Sept. 15, 2006

I wanted to give you a heads-up that the London School of Economics will provide ICANN with a final copy of it GNSO review report today. This report will be used to inform ICANN's effort to develop detailed proposals for improving the GNSO's structures and processes. The independent advice presented in this report will NOT simply be accepted and implemented (to state the obvious). This report should be viewed as a starting point for community collaboration on revising the GNSO. When I receive the report, it will be sent simultaneously to the Board, the GNSO Council, and constituency leaders. It also will be posted on ICANN's website along with a statement on ICANN's next steps for GNSO improvements. Outlined below is the general approach recommended by staff and supported by Board leaders to engage the community in developing specific changes for the GNSO. I had hoped to discuss this with you on the Council conference call prior to the report's release. We will, however, have an opportunity to address this on the next Council call and then further details will be added. As always, your comments and questions are welcome. Thanks. Denise Denise Michel Vice President, Policy Development ICANN denise.michel(a)icann.org Report Release • Submission of GNSO Review Report to Board by LSE. • Immediate transmission to GNSO Council and constituency leaders. • Immediate posting on ICANN website and opening of public comment list. • Phone briefing by LSE of Board (preferably within a week of release). • Phone briefing by LSE of GNSO Council (preferably within a week of release). • Phone briefing by LSE of GNSO constituencies (preferably within a week of release). Appointment of Board/GNSO Working Groups • Staff recommends the appointment of joint Board/GNSO working groups to address improvements to GNSO policy activities, structure, operations, and communications. • The groups' mandate wouldl be to consider input (LSE report, previous Council review, public comments, GNSO Council and constituency input, and Board input), and recommend to the Board changes to the GNSO (all done with opportunities for public comment). • The groups would address issues such as changing: the PDP (policy development process in the bylaws); voting and representation on the Council and Board; the GNSO's constituencies/stakeholder participation structure; staffing and support of the Council and constituencies, and other operational issues; and the distribution of information and solicitation of comments (including website improvements).

1 1

Erratum: "Fw: LSE's GNSO Review"
by Mawaki Chango Sept. 15, 2006

Sept. 15, 2006

Apologies: You may receive again at any moment from now Denise's message as per the subject above, reforwarded to the Council list. This of course was a mistake, please discard. Mawaki

1 0

Fwd: [council] LSE's GNSO Review
by Mawaki Chango Sept. 15, 2006

Sept. 15, 2006

Get ready ;-) ... --- Denise Michel <denise.michel(a)icann.org> wrote: > Date: Fri, 15 Sep 2006 06:30:22 -0700 > From: Denise Michel <denise.michel(a)icann.org> > To: Council GNSO <council(a)gnso.icann.org> > Subject: [council] LSE's GNSO Review > > I wanted to give you a heads-up that the London School of Economics > will provide ICANN with a final copy of it GNSO review report > today. This report will be used to inform ICANN's effort to > develop detailed proposals for improving the GNSO's structures and > processes. The independent advice presented in this report will > NOT simply be accepted and implemented (to state the obvious). > This report should be viewed as a starting point for community > collaboration on revising the GNSO. When I receive the report, it > will be sent simultaneously to the Board, the GNSO Council, and > constituency leaders. It also will be posted on ICANN's website > along with a statement on ICANN's next steps for GNSO improvements. > Outlined below is the general approach recommended by staff and > supported by Board leaders to engage the community in developing > specific changes for the GNSO. I had hoped to discuss this with > you on the Council conference call prior to the report's release. > We will, howe! > ver, have an opportunity to address this on the next Council call > and then further details will be added. > > As always, your comments and questions are welcome. > > Thanks. > Denise > > Denise Michel > Vice President, Policy Development > ICANN > denise.michel(a)icann.org > > > Report Release > > Submission of GNSO Review Report to Board by LSE. > Immediate transmission to GNSO Council and constituency > leaders. > Immediate posting on ICANN website and opening of public > comment list. > Phone briefing by LSE of Board (preferably within a week of > release). > Phone briefing by LSE of GNSO Council (preferably within a > week of release). > Phone briefing by LSE of GNSO constituencies (preferably > within a week of release). > > Appointment of Board/GNSO Working Groups > > Staff recommends the appointment of joint Board/GNSO working > groups to address improvements to GNSO policy activities, > structure, operations, and communications. > The groups' mandate wouldl be to consider input (LSE report, > previous Council review, public comments, GNSO Council and > constituency input, and Board input), and recommend to the Board > changes to the GNSO (all done with opportunities for public > comment). > The groups would address issues such as changing: the PDP > (policy development process in the bylaws); voting and > representation on the Council and Board; the GNSO's > constituencies/stakeholder participation structure; staffing and > support of the Council and constituencies, and other operational > issues; and the distribution of information and solicitation of > comments (including website improvements). > > > > > >

1 0

Regarding communicating task force/committee work with the press and other outside groups
by Bruce Tonkin Sept. 14, 2006

Sept. 14, 2006

Hello All, At various times, members of task forces, committees and the Council are approached by the press to comment on the work of a task force, committee or Council. Some members also operate blogs to keep the community informed. I recommend we take the following approach: (1) An individual member should not speak on behalf of a task force, committee or Council with respect to current proposed recommendations. Normally people should be referred to the current official report or minutes of a meeting. The appropriate chair of a group would normally present the current proposed recommendations in an agreed document. (2) An individual member is free to provide their own opinions on a preferred or potential outcome of a particular group. Ie feel free to speak for yourself :-) (3) An individual should not quote another individual out of context. In general if you are asked what someone else (either individual, business, group etc) thinks - then direct people to either an audio recording, a transcript, minutes, or a posting on a public mailing list. Note that our work by its nature results in many discussions, drafts, and proposals for future policy. We need to be careful that we clearly communicate the current status of any recommendation. E.g "under discussion", "proposed by a task force member", "proposed by a task force in an Initial Report" etc. I am interested in feedback on the above, as I think it would be useful to include in future to brief new members of a group. Regards, Bruce Tonkin

3 2

ICANN meetings in Sao Paulo
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 14, 2006

Sept. 14, 2006

[council[at]gnso.icann.org] Dear Council Members, Please see: http://www.icann.org/meetings/saopaulo/ http://www.icannsaopaulo.br/ There will be one full Council working session on Sunday, 3 December 2006, before the ICANN meetings start. Please make plans to arrive in time. Please let me know as soon as possible whether you will attend the meetings in person, and whether you would like to be part of a group reservation at the venue hotel. Last minute cancellations for the group booking cause problems, so please try and avoid this. 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

Purpose of Whois - informational materials
by Maria Farrell Sept. 14, 2006

Sept. 14, 2006

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

3 3

Regarding Item 3: Correspondence - Clarification sought by PDP-Feb06 task force
by Bruce Tonkin Sept. 14, 2006

Sept. 14, 2006

Hello All, With respect to the agenda topic: > > Item 3: Correspondence > > - Clarification sought by PDP-Feb06 task force on whether the > outcomes of the PDP would affect gTLD contracts in existence > at the time the > Board approves the policy. See > http://www.gnso.icann.org/correspondence/cubberley-to-tonkin-2 > 5aug06.pdf > I had a phone conference with John Jeffrey and Dan Halloran of the General Counsel's office, along with Denise Michel regarding this agenda item. John agreed to provide a written response to this request for discussion at our next Council call. I think there are really two quite separate issues that underlie the question from the PDP-Feb06 task force. (1) Legally is a registry operator obligated to comply when the ICANN Board approves a recommendation resulting from the PDP-Feb06 work. Note that ICANN can only require businesses to comply with a policy recommendation through its contracts with those businesses. These contracts have limitations on what recommendations a business must comply with. (2) Will the ICANN Board wait until the GNSO completes its work in PDP-Feb 06 before approving anymore contracts. I think it is reasonable for the General Counsel's office to provide advice with respect to point (1). The current contracts may make it difficult to apply or implement some new ICANN policies. It is certainly a requirement under Annex A, clause 2 (e)(3) of the bylaws that the GNSO consider policies that have "applicability". With respect to point (2) this is probably a discussion that needs to happen with the ICANN Board. The GNSO did request that the Board wait until approving the proposed .com agreement until the GNSO had a chance to consider all the issues through a PDP, and the Board decided to approve the agreement. We are now in the same position again with respect to biz, info, and org agreements. Regards, Bruce Tonkin

1 0

Regarding Item 4: Proposed bylaws amendment to improve transparency with respect to contract approvals
by Bruce Tonkin Sept. 14, 2006

Sept. 14, 2006

Hello All, With respect to the agenda topic: > > > 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 I had a phone conference with John Jeffrey and Dan Halloran of the General Counsel's office, along with Denise Michel regarding this agenda item. John agreed to create some draft wording in response to the original suggestion from the GNSO Council, and will send to the Council for comment. John also noted that the Board had been complying with the spirit of the recommendation with respect to putting out gTLD contracts for public comment. Regards, Bruce Tonkin

1 0

Regarding attendance at the Council meeting on 14 Sept 2006
by Bruce Tonkin Sept. 14, 2006

Sept. 14, 2006

Hello All, Please advise the GNSO Secretariat in advance if you will not be attending the teleconference on 14 Sept 06. The attendance level at the last meeting was not good (3 Aug 2006). I would rather re-schedule the meeting than have a meeting with he minimum quorum. Ie I would prefer to know that we have at least 14 Council members attending, out of a possible 21 members attending. So if there are more than 7 apologies, the meeting should be re-scheduled. Bear in mind that many of us attend these meetings very late in the evening, or very early in the morning - so it is important that when we do attend, that the meetings are well attended to justify the inconvenience. Regards, Bruce Tonkin

5 4

Information Page on Requests for New Registry Services
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Sept. 14, 2006

Sept. 14, 2006

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] ICANN publishes new page for Submitted Applications for New Registry Services: http://www.icann.org/announcements/announcement-1-13sep06.htm Addition to Website and Announcement of Information Page on Requests for New Registry Services As part of ICANN's effort to support a timely, open and transparent process for the evaluation of new registry services, ICANN has today added a link in the Current Issues menu of the ICANN website to the Registry Services Evaluation Process. This page serves as the information area for the Registry Services Evaluation Policy and requests for new registry services. 13 September 2006 http://www.icann.org/registries/rsep/ Registry Services Evaluation Process -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0