January 2011 - ispcp - lists.icann.org

Meeting Invitation / ISPCP Call / Monday 23 August at 1400 UTC
by Gisella Gruber-White Aug. 3, 2012

Aug. 3, 2012

Dear All, Please note that the next ISPCP call is scheduled for on Monday 23 August 2010 at 1400 UTC. Please find the dial-in details below. Thank you Kind regards Gisella ------------------------------------------------------------- Passcodes: Participant: 1385274 Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0489 AUSTRALIA ADELAIDE: 61-8-8121-4854 1-800-009-646 AUSTRALIA BRISBANE: 61-7-3102-0956 1-800-009-646 AUSTRALIA CANBERRA: 61-2-6100-1956 1-800-009-646 AUSTRALIA MELBOURNE: 61-3-9010-7725 1-800-009-646 AUSTRALIA PERTH: 61-8-9467-5235 1-800-009-646 AUSTRALIA SYDNEY: 61-2-8211-1378 1-800-009-646 AUSTRIA 43-1-92-80-004 0800-677-079 BELGIUM 32-2-401-7012 0800-4-9773 BRAZIL 0800-7610709 CHILE 1230-020-2471 CHINA* 86-400-810-4743 10800-712-1185 10800-120-1185 COLOMBIA 01800-9-156479 CZECH REPUBLIC 420-2-25-98-56-06 800-700-159 DENMARK 45-7014-0229 8088-5346 ESTONIA 800-011-1092 FINLAND Land Line: 106-33-156 0-800-1-12318 FINLAND Mobile: 09-106-33-156 0-800-1-12318 FRANCE LYON: 33-4-26-69-12-67 080-563-9648 FRANCE MARSEILLE: 33-4-86-06-00-67 080-563-9648 FRANCE PARIS: 33-1-70-75-25-91 080-563-9648 GERMANY 49-69-2222-20599 0800-101-2179 GREECE 30-80-1-100-0630 00800-12-5998 HONG KONG 852-2286-5624 800-968-767 HUNGARY 06-800-15230 INDIA 000-800-852-1209 INDONESIA 001-803-011-3492 IRELAND 353-1-431-9674 1800-992-641 ISRAEL 1-80-9214131 ITALY 39-02-3600-0507 800-985-846 JAPAN OSAKA: 81-6-7739-4755 00531-12-1423 JAPAN TOKYO: 81-3-5539-5146 00531-12-1423 LATVIA 8000-2933 LUXEMBOURG 352-27-000-1305 MALAYSIA 1-800-80-8114 MEXICO 001-866-761-6529 NETHERLANDS 31-20-713-3466 0800-020-3473 NEW ZEALAND 64-9-970-4633 0800-445-270 NORWAY 47-21-59-00-05 800-11825 PANAMA 011-001-800-5072096 PERU 0800-53765 PHILIPPINES 63-2-858-3702 POLAND 00-800-1210066 PORTUGAL 8008-12795 RUSSIA 8-10-8002-9763011 SINGAPORE 65-6883-9189 800-120-4141 SLOVAK REPUBLIC 421-2-322-422-07 SOUTH AFRICA 080-09-93386 SOUTH KOREA 82-2-6744-1044 00798-14800-6315 SPAIN 34-91-414-08-12 800-099-807 SWEDEN 46-8-506-92-118 0200-897-066 SWITZERLAND 41-44-580-4209 0800-000-663 TAIWAN 886-2-2795-7338 00801-137-557 THAILAND 001-800-1206-65077 UNITED KINGDOM BIRMINGHAM: 44-121-210-9007 0800-279-9198 UNITED KINGDOM GLASGOW: 44-141-202-3207 0800-279-9198 UNITED KINGDOM LEEDS: 44-113-301-2107 0800-279-9198 UNITED KINGDOM LONDON: 44-20-7098-0710 0800-279-9198 UNITED KINGDOM MANCHESTER: 44-161-601-1407 0800-279-9198 URUGUAY 000-413-598-3427 USA 1-210-795-0464 866-617-1530 VENEZUELA 0800-1-00-3717 Certain dialing restrictions can apply from specific countries. To ensure that your participants have the correct dialing procedures, please include this link in your invitation: https://e-meetings.verizonbusiness.com/audioconferencing/global_access.php

6 30

Main points from ISPCP conference call Wenesday 26th Jan
by Tonyarholmes＠btinternet.com Feb. 2, 2011

Feb. 2, 2011

The following note record the main issues discussed during the call. Changes to ISPCP Charter An updated copy of the ISPCP Charter had been circulated which attempted to align the document with relevant requirements set out within the CSG Charter. Comments should be submitted to the Secretariat within the next 7 days. If no comments are received this version (v4) will be considered the final approved version of the ISPCP Constituency Charter. Arrangements for the March San Francisco meeting - Proposed meeting between SO reps and ICANN ICANN have proposed an additional meeting between the chairs of the SOs and ACs and ICANNs CEO. Originally the proposal was for a 2-day meeting but has since been reduced to a half-day session followed by dinner. No agenda for the meeting has been posted. ISPCP councillors will offer support for attendance by the GNSO Chair and in addition will call for an agenda to be posted in good time, and for the outcome to be publicly posted to ensure full transparency. - GNSO arrangements No information is currently available on the agenda for the GNSO sessions that will be held on the Saturday and Sunday prior to the meeting. This issue will be discussed once that happens. - Constituency and SG arrangements It has yet to be confirmed whether the CSG breakfast with the Board will take place in San Francisco. Concern exist within the ISPCP that the ability to have adequate dialogue with ICANN Board members will be reduced. If this meeting does not go ahead the ISPCP will discuss with other CSG representatives how best to increase the level dialogue with Board members, the GAC and other key stakeholders - Early agenda items for the ISPCP Constituency meetings No final decisions were taken with regard to the ISPCP Constituency meeting, but members were asked to flag important issues for the agenda, particularly after the GAC, Board meeting in Brussels. - Travel support ICANN travel support, allocated via the ISPCP Constituency for the San Francisco meeting will be assigned to Wolf-Ulrich Knoben (GNSO Councillor) and Tony Harris (ISPCP CSG executive). The Secretariat will advise the GNSO secretary. GNSO Council issues Attention was drawn to the status of the report on CWG Rec 6. The GNSO council have been requested to endorse the report which was sent to the Board via ALAC. Concern exist that the CWG did not refer back to the SO's prior to submitting their report to the Board. ISPCP members are invited to send comments on the report to the list within the next 7-days in order to ensure ISPCP council members can represent their views when this is discussed at the next GNSO Council meeting. ATRT report Olivier Muron gave a short overview of the status of the ATRT report which is now open for public comment. It was noted that the ISPCP have already raised issues over the ASO, which whilst raised within the report, were not covered by the recommendations. This remains a major issue for the ISPCP but no further action was proposed. GNSO Working Group Guidelines Public comments on the WG Guidelines are now invited. ISPCP members who wish to express any views were invited to contact Wolf-Ulrich Knoben who has led on this issue for the Constituency. ISPCP website Noting the ISPCP website urgently requires updating and that currently this cannot be achieved through the GNSO toolkit, it was agreed that minimum changes must be made to reflect the current organisation of the ISPCP, its charter and position statement. Once this can be handled as part of the GNSO toolkit the Constituency will appoint a contact person for the website. The Secretariat was requested to pursue this in conjunction with the GNSO Secretariat. Date of next conference call To be advised.

3 4

Issue for todays ISPCP call
by Tonyarholmes＠btinternet.com Jan. 26, 2011

Jan. 26, 2011

Attached is an updated version of the ISPCP Charter which includes additional references to the CSG now that the CSG Charter has been agreed by all stakeholder groups. We can discuss the changes during today's conference call (16.00GMT). Draft agenda for the call is as follows. 1. Changes to ISPCP Charter 2. Arrangements for the March San Francisco meeting - Proposed meeting between SO reps and ICANN - GNSO arrangements - Constituency and SG arrangements - Early agenda items for the ISPCP Constituency meetings - Travel support 3. GNSO Council issues 4. ATRT report 5. GNSO Working Group Guidelines 6. ISPCP website 7. AoB Please add additional issues Tony

1 0

WG: [council] Fwd: [gnso-chairs] GNSO meeting with new SSAC chair in March meeting?
by KnobenW＠telekom.de Jan. 25, 2011

Jan. 25, 2011

This could be an opportunity for the ISPCP meeting in SF, too. Wolf-Ulrich ________________________________ Von: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Im Auftrag von Stéphane Van Gelder Gesendet: Dienstag, 25. Januar 2011 19:08 An: council(a)gnso.icann.org Council Betreff: [council] Fwd: [gnso-chairs] GNSO meeting with new SSAC chair in March meeting? Thanks Liz, Am replying to the full Council list so that everyone is aware of the change at SSAC. I think meeting with Patrik is an excellent idea. Glen, Olga, can this be worked into our SF agenda? Thanks, Stéphane Début du message réexpédié : De : Liz Gasster <liz.gasster(a)icann.org> Date : 25 janvier 2011 17:46:40 HNEC À : Objet : [gnso-chairs] GNSO meeting with new SSAC chair in March meeting? All, As you may be aware, Steve Crocker is stepping down as SSAC Chair, and Patrik Faltstrom will be assuming this role. The Council may be interested in meeting Patrick and learning about what changes the community might expect as the committee moves forward. Patrik has graciously agreed to visit with each SO/AC during the upcoming SV meeting, schedules permitting. He would also be glad to attend any Stakeholder Group or Constituency meetings if that would be of interest. Please let me know if the GNSO Council is interested, and, if so, perhaps Olga and Glen might propose a workable time. Also Patrik did ask what style of meeting (discussion, presentation, intro & Q&A) you'd prefer, to which I might suggest introductory comments followed by short Q and A? Thanks, Liz

1 0

WG: [council] Form for 2012 budget requests
by KnobenW＠telekom.de Jan. 21, 2011

Jan. 21, 2011

Tony, deadline for budget requests is EOJanuary. We should discuss potential request next Wednesday. But any idea prior to our call is welcome. Wolf-Ulrich ________________________________ Von: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Im Auftrag von Glen de Saint Géry Gesendet: Freitag, 7. Januar 2011 17:47 An: council(a)gnso.icann.org Betreff: [council] Form for 2012 budget requests Dear Council members, Please find attached the form that should be used for budget requests for Fiscal Year 2012 (a "pdf" version was embedded in the presentation that was circulated in December). Forms should be completed by the SO/AC leadership (the Chairs of the SGs and Cs as well as the Council itself if there are budget items that the Council chooses to request) and sent to: controller(a)icann.org <mailto:controller@icann.org> . The deadline is the end of January 2011. Thank you. Kind regards, Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org <http://gnso.icann.org>

1 0

WG: ICANN News Alert -- Public Comment: GNSO Council Requests Your Input on Proposed GNSO Working Group Guidelines
by KnobenW＠telekom.de Jan. 19, 2011

Jan. 19, 2011

FYI Wolf-Ulrich ICANN <http://www.icann.org/> News Alert http://www.icann.org/en/announcements/announcement-18jan11-en.htm ________________________________ Public Comment: GNSO Council Requests Your Input on Proposed GNSO Working Group Guidelines 18 January 2011 As part of the GNSO Improvements Process, which has as its objective to improve the structure and operations of the Generic Names Supporting Organization (GNSO), the Policy Process Steering Committee (PPSC) has now submitted to the GNSO Council the proposed GNSO Working Group Guidelines (see http://gnso.icann.org/improvements/gnso-working-group-guidelines-final-1 0dec10-en.pdf [PDF, 626 KB]). Prior to considering the proposed GNSO Working Group Guidelines, the GNSO Council is seeking your input. Comments on the proposed GNSO Working Group Guidelines <http://gnso.icann.org/improvements/gnso-working-group-guidelines-final- 10dec10-en.pdf> [PDF, 626 KB] can be submitted until 8 February 2011 (see details below). Following the public comment period, the GNSO Council will review the comments received and determine whether additional modifications need to be made to the document or whether the document is ready for adoption following which it will be incorporated in the GNSO's Operating Procedures and become applicable to all new GNSO Working Groups. Background In the past, the GNSO decided policy mainly through small legislative bodies called "Task Forces." Intentionally, it is moving towards a more inclusive, representative model where key parties tackle an issue together as a "Working Group". This Working Group Model should become the focal point for policy development and enhance the policy development process by making it more inclusive and representative, and - ultimately - more effective and efficient. The PPSC tasked a Working Group Work Team (WG WT) to define this new Working Group model. The WG WT prepared a first draft that was put out for public comment <http://www.icann.org/en/announcements/announcement-3-31may10-en.htm> , following which it reviewed the comments and modified <https://st.icann.org/data/workspaces/icann-ppsc/attachments/working_gro up_team:20100928090126-0-24693/original/GNSO%20Working%20Group%20Guideli nes%20-%20Including%20Comments%20-%20updated%2024%20August%202010.doc> [DOC, 188 KB] the document accordingly. In addition, the PPSC identified a number of issues that were subsequently addressed <https://st.icann.org/data/workspaces/icann-ppsc/attachments/policy_proc ess_steering_committee_ppsc:20101101171932-0-13671/original/PPSC%20Comme nts%20%252B%20WG%20WT%20Response%20-%2014%20October%202010.doc> [DOC, 48 KB] by the WG WT. The proposed GNSO Working Group Guidelines, as approved by the PPSC, bring together all the different elements of the Working Group process; it addresses what should be considered in creating, chartering, staffing, and instructing/guiding a WG to accomplish the desired outcome, and; secondly, what guidance should be provided to a WG on elements such as structure, decision-making, tasking, reporting, and delivering the outcome(s) as chartered. Background documents / links * GNSO Working Group Guidelines, as approved by the PPSC <http://gnso.icann.org/improvements/gnso-working-group-guidelines-final- 10dec10-en.pdf> [PDF, 626 KB] * The GNSO Improvements Web Site <http://gnso.icann.org/en/improvements/> * PPSC Workspace <https://st.icann.org/icann-ppsc/index.cgi?policy_process_steering_commi ttee_ppsc> * WG WT Workspace <https://st.icann.org/icann-ppsc/index.cgi?working_group_team> Staff responsible: Marika Konings Deadline and how to submit comments Comments are welcome via e-mail to gnso-wg-guidelines(a)icann.org until 8 February 2011. Access to the public comment forum from which comments can be posted can be found at http://www.icann.org/en/public-comment/public-comment-201102-en.htm#gnso -wg-guidelines. An archive of all comments received will be publicly posted at http://forum.icann.org/lists/gnso-wg-guidelines/. This message was sent from ICANN News Alert to knobenw(a)telekom.de. It was sent from: ICANN, 4676 Admiralty Way Suite 330 , Marina del Rey, CA 90292-6601. You can modify/update your subscription via the link below. Email Marketing by <http://www.icontact.com/a.pl/144186> iContact - Try It Free! <http://www.icontact.com/a.pl/144186> <http://app.icontact.com/icp/static/images/icons/email_manage_subscripti on.png> Manage your subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=11118977&l=6333&s=WW8E& m=341190&c=165637> <http://click.icptrack.com/icp/track.php?msgid=341190&act=WW8E&r=1111897 7&c=165637>

1 0

ENC: [council] GNSO Council resolutions 13 January
by Jaime Wagner - PowerSelf Jan. 16, 2011

Jan. 16, 2011

fyi Jaime Wagner jaime(a)powerself.com.br Direto (51) 3219-5955 Cel (51) 8126-0916 Geral (51) 3233-3551 DDG: 0800-703-6366 <http://www.powerself.com.br/> www.powerself.com.br De: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Em nome de Glen de Saint Géry Enviada em: sexta-feira, 14 de janeiro de 2011 13:40 Para: GNSO Council Assunto: [council] GNSO Council resolutions 13 January Dear All, Before the official minutes, the following motions were passed by the GNSO Council at its meeting on Thursday, 13 January 2011. Thank you very much. Kind regards, Glen Joint SO/AC Working group on support for new gTLD applicants (JAS) Motion Whereas: The GNSO Council and ALAC established the Joint SO/AC Working group on support for new gTLD applicants in April of 2010; and The Working Group has completed the work as defined in its initial charter and published a Milestone report on 10 November 2010 covering those chartered items and including a list of further work items that it recommended further work on; and In recognition of the ICANN Board's resolution 2010.12.10 which reiterated its 2010.10.28.21 in response to an Interim report from the JAS WG, which states: the Board encourages the JAS WG and other stakeholders to continue their work on the matter, and in particular, provide specific guidelines on the implementation of their recommendations such as determining the criteria for eligibility for support. Resolved: 1. The charter of the Joint SO/AC New gTLD Applicant Support Working Group is extended to include the following limited objectives: a) Propose criteria for financial need and a method of demonstrating that need. Financial need has been established as the primary criterion for support. The group should seek out expert advice in this area, especially given the comparative economic conditions and the cross-cultural aspects of this requirement. b) Propose mechanisms for determining whether an application for special consideration should be granted and what sort of help should be offered; c) Propose methods for applicants to seek out assistance from registry service providers. d) Propose methods for applicants to seek out assistance from other top-level domain consultants, translators, and technicians, in the application for, and administration of, a new top-level domain e) Design mechanisms to encourage the build out of Internationalized Domain Names (IDNs) in small or underserved languages. 2. The Working group is asked to present a schedule for the work that allows for completion in time for the opening of the application round, currently scheduled for Q2 2011, in any event no delays for the new gTLD program should result from the working groups work. 3. The Working group shall report its results and present a final report directly to the GNSO Council and the ALAC for discussion and adoption, as appropriate, according to their own rules and procedures. 4. All communication to the ICANN Board regarding the work of this Working Group shall be through the respective SO/AC unless expressly approved by the respective SO/AC. Motion to Approve the Recommendations in the Final Report on Proposals for Improvements to the Registrar Accreditation Agreement. "WHEREAS, a motion to approve the recommendations in the final report on proposals for improvement to the Registrar Accreditation Agreement has been submitted and seconded; (8 December motions https://st.icann.org/gnso-council/index.cgi?8_december_motions) WHEREAS, that motion called for the GNSO Council to accept the final report to approve the form of the Registrant Rights andResponsibilities Charter as described in Annex D of the final report, to recommend that staff commence the consultation process withRegistrars to finalize the Registrant Rights and Responsibilities Charter for posting on the Web sites of Registrars as specified in Section 3.15 of the RAA, and to recommend that staff adopt the process specified as Process A in the final report, to develop a new form of RAA with respect to the high and medium priority topics described in the final report; WHEREAS, some GNSO Councillors have expressed the view that further work is necessary on the portion of that motion relating to the process specified as Process A in the final report to develop a new form of RAA; WHEREAS, the GNSO Council does not wish for such work to delay progress on the Registrant Rights and Responsibilities Charter referenced above; NOW, THEREFORE, BE IT RESOLVED that the motion to approve the recommendations in the final report on proposals for improvements to the Registrar Accreditation Agreement be amended as set out below: WHEREAS, on 4 March, 2009, the GNSO Council approved the form of the 2009 registrar accreditation agreement (RAA) developed as a result of a consultative process initiated by ICANN; WHEREAS, in addition to approving the 2009 RAA, on 4 March 2009 the GNSO Council convened a joint drafting team with members of theAt-Large community to conduct further work related to improvements to the RAA. Specifically, to draft a charter identifying Registrant Rights and Responsibilities; WHEREAS, on 18 October 2010 the joint GNSO/ALAC RAA drafting team published its final report describing specific recommendations and proposals for improvements to the RAA; (http://gnso.icann.org/issues/raa/raa-improvements-proposal-final-report-18o ct10-en.pdf) WHEREAS, the GNSO Council has reviewed the final report and desires to approve some of the recommendations and proposals contained therein; NOW, THEREFORE, BE IT RESOLVED that the GNSO Council appreciates the effort of the joint GNSO/ALAC RAA drafting team in developing the recommendations and proposals delineated in the final report for improvements to the RAA; (http://gnso.icann.org/issues/raa/raa-improvements-proposal-final-report-18o ct10-en.pdf) RESOLVED FURTHER, that the GNSO Council hereby accepts the final responsibilities charters as described in Annex D of the final report; RESOLVED FURTHER, that the GNSO Council recommends that the staff commence the consultation process with registrars in the RAA to finalize the registrant rights and responsibilities charter for posting on the Web sites on specified in Section 3.15 of the RAA. Motion on the implementation of the Fast Flux recommendations that were adopted by the GNSO Council on 3 September 2009 Whereas the Fast Flux PDP Working Group submitted its Final Report to the GNSO Council on 13 August 2009; Whereas the Fast Flux PDP Working Group did not make recommendations for new consensus policy, or changes to existing policy, but did develop several other recommendations that were adopted by the Council on 3 September 2009 (seehttp://gnso.icann.org/meetings/minutes-03sep09.htm) Whereas the GNSO Council intended to create a drafting team to develop a plan with a set of priorities and schedule to address the adopted recommendations for review and consideration by the GNSO Council; Whereas due to workload and other priorities such a drafting team was never created; Whereas the Council tasked the Council leadership at the wrap up meeting at the ICANN meeting in Cartagena to put forward proposals to suggest which projects should be continued and discontinued; Whereas the Council leadership has reviewed the Fast Flux Recommendations that were adopted by the GNSO Council, also in light of the recent recommendations made by the Registration Abuse Policies Working Group; Whereas the Council leadership has recommended the approach outlined below to the GNSO Council for consideration as an acceptable way of implementing the adopted recommendations and therewith closing the project; RESOLVED, The Council accepts the approach identified below for the adopted recommendations (see http://gnso.icann.org/meetings/minutes-03sep09.htm) and instructs the ICANN Staff to implement these recommendations as set forth below: a) Adopted recommendation Fast-Flux Working Group (FFWG) #1: To encourage ongoing discussions within the community regarding the development of best practices and / or Internet industry solutions to identify and mitigate the illicit uses of Fast Flux Proposed implementation: This recommendation is encompassed by the Registration Abuse Policies WG (RAPWG) Malicious Use of Domain Names Recommendation #1 which recommends the creation of non-binding best practices to help registrars and registries address the illicit use of domain names. b) Adopted FFWG recommendation #2: The Registration Abuse Policy Working Group (RAPWG) should examine whether existing policy may empower Registries and Registrars, including consideration for adequate indemnification, to mitigate illicit uses of Fast Flux; Implementation completed as it was addressed by the RAP WG in its final report (see http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf) c) Adopted FFWG recommendation #3: To encourage interested stakeholders and subject matter experts to analyze the feasibility of a Fast Flux Data Reporting System to collect data on the prevalence of illicit use, as a tool to inform future discussions; · The RAPWG Final Report and the Fast-Flux Working Group Final Report indicated that fast-flux is generally a domain use issue and not a domain registration issue, and as such falls outside the purview of the GNSO and ICANN. Therefore no further action is recommended*. d) Adopted recommendation #4: To encourage staff to examine the role that ICANN can play as a best practices facilitator" within the community; Proposed Implementation: Integrate this recommendation into the RAP WG Recommendation on Meta Issue: Collection and Dissemination of Best Practices which recommends that the GNSO, and the larger ICANN community in general, create and support structured, funded mechanisms for the collection and maintenance of best practices. e) Adopted FFWG recommendation 5: To consider the inclusion of other stakeholders from both within and outside the ICANN community for any future Fast Flux policy development efforts; Proposed Implementation: It is assumed that if the Registration Abuse Policies WGs (RAPWG) Malicious Use of Domain Names Recommendation #1 is adopted by the Council, that the subsequent effort will be open to participation by stakeholders from both within and outside the ICANN community. f) Adopted FFWG recommendation #6: To ensure that successor PDPs on this subject, if any, address the charter definition issues identified in the Fast Flux Final Report. Proposed Implementation: No action needed at this point, but should be included if any future PDPs are initiated on this subject. g) Adopted FFWG recommendation #6: To form a Drafting Team to work with support staff on developing a plan with set of priorities and schedule that can be reviewed and considered by the new Council as part of its work in developing the Council Policy Plan and Priorities for 2010. Proposed Implementation: The Council deems this work to be completed in conjunction with the above-proposed implementation proposals. RESOLVED FURTHER The Council now considers the work of the Fast Flux WG complete. As such, the "Fast Flux Council Follow-up" action item is deemed closed and will be deleted from the Pending Project List. Motion to Acknowledge the Receipt of the GNSO Working Group Guidelines and Initiate a Public Comment Period WHEREAS, in October 2008, the GNSO Council established a framework (see GNSO Council Improvement Implementation Plan; (http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-implemen tation-plan-16oct08.pdf) for implementing the various GNSO Improvements identified and approved by the ICANN Board of Directors on 26 June 2008 (http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113182) (http://www.icann.org/en/minutes/resolutions-26jun08.htm) WHEREAS, that framework included the formation, in January 2009, of two Steering Committees, the Operations Steering Committee (OSC) and the Policy Process Steering Committee (PPSC), to charter and coordinate the efforts of five community work teams in developing specific recommendations to implement the improvements; WHEREAS, the PPSC established two work teams, including the Working Group Work Team (WG WT), which was chartered to develop a new GNSO Working Group Model that improves inclusiveness, improves effectiveness, and improves efficiency; WHEREAS, the WG WT completed its deliberations and forwarded the GNSO Working Group Guidelines to the PPSC on 1 November 2010; WHEREAS, the PPSC reviewed and approved the GNSO Working Group Guidelines on 20 December 2010 http://gnso.icann.org/improvements/gnso-working-group-guidelines-final-10dec 10-en.pdf and forwarded the report to the GNSO Council on 1 January 2011 ; NOW THEREFORE, BE IT: RESOLVED that the GNSO Council acknowledges receipt of the GNSO Working Group Guidelines as delivered by the PPSC and directs ICANN Staff to commence a twenty-one (21) day public comment period on the GNSO Working Group Guidelines. RESOLVED FURTHER that the GNSO Council shall take action on the GNSO Working Group Guidelines as soon as possible after the end of the public comment period. RESOLVED FURTHER that the GNSO Council recommends that a concise summary of the WG Guidelines be drafted by ICANN Staff, following approval of the GNSO Working Guidelines by the GNSO Council, in order to serve as a primer to the full document for potential WG members. The summary should be approved by the PPSC before being submitted to the GNSO Council. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Brief notes of ISPCP call held 13 Jan 2011
by Tonyarholmes＠btinternet.com Jan. 14, 2011

Jan. 14, 2011

Brief notes from the ISPCP conference call held on 13th January 2011 The call was held as preparation for the GNSO council meeting scheduled for the same day. 1. Joint Applicant support WG An original motion carried forward from the last meeting, proposed by Rafik Danmak was still on the table, proposing a charter extension in response to the ICANN Board resolution supporting applicants and calling for completion of a list of further work items. A counter motion opposing this extension had been tabled by Jeff Neuman, following which Wolf- Ulrich Knoben has attempted to find a compromise. However Wolf's proposal for a 'friendly amendment' has not been accepted by Geoff, therefore this will be voted on during the meeting. The ISPCP line will be to support Wolf-Ulrich's proposal, but if this fails the ISPs will offer support for Jeff Neumans proposal. 2. Registrar Accreditation Agreement A motion has been tabled to accept the report, but the Registrar's are unable to accept the proposal that requires the involvement of a third party in signing any agreement between ICANN and Registrars. The ISPs support this approach in principle but have issues over who the third party would be and how such an arrangement would be implemented. A final approach remains dependent upon the resolution of those concerns. 3. Status of Stakeholder Group and Constituency statements on Recommendation 6 The main issue concerns the ability of the Board to initiate further dialogue directly with the WG as this has the potential to short circuit the discussion and responsibility for this work with relevant Support Organizations. Working Group reports will all be submitted to relevant Support Organizations for ratification. The ISPCP view is that any WG report must not be filtered by the GNSO or any other S.O, although they are all entitled to either endorse or reject the outcome. Such a position must not inhibit any required further dialogue between the Board and any Constituency/part of the community. 4. Board Resolution on Consumer Choice, Competition and Innovation A briefing on this issue will be provided by Bruce Tonkin during the meeting. No voting is anticipated on this issue. Pending the outcome of this session ISPCP councilors will be seeking representative to engage in this work going forward. 5. Board Response to reconsideration requests This item is for discussion only, with no additional action required from ISP Councilors at this stage. 6. Operations Steering Committee (OSC) and Policy Process Steering Committee (PPSC) and new Standing Committee. This item will consider actions required to take this work forward. The ISPCP will support the proposal to establish a new standing committee to oversee the implementation of the recommendations. The next ISPCP call will take place on Wednesday 26th January from 16.00 to 17.00 UTC with the following items included on the agenda; - Issue for the next GNSO meeting - ISPCP Charter - Arrangements for San Francisco - ISPCP website

1 0

Is anyone trying to join the ISPCP call now?
by Tonyarholmes＠btinternet.com Jan. 13, 2011

Jan. 13, 2011

Tony

2 1

Call details & Adobe Connect for GNSO Council meeting Thursday 13 January 2011 at 20:00 UTC
by KnobenW＠telekom.de Jan. 11, 2011

Jan. 11, 2011

FYI Dear Councillors, Please find the dial-in numbers for the GNSO Council call on Thursday, 13 January 2011 at 20:00 UTC. Please notify your constituency and stakeholder group members that the meeting will be audio cast GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u <http://stream.icann.org:8000/gnso.m3u> Meeting Time 20:00 UTC 12:00 PST; 14:00 CST; 15:00 EST; 17:00 Buenos Aires; 17:00 Brazil; 21:00 CET; 23:00 Moscow Friday,14 January 2011 01:00 Pakistan; 04:00 Beijing; 05:00 Tokyo, 07:00 Melbourne Other times may be found at: http://www.timeanddate.com/worldclock/fixedform.html Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0