October 2013 - ispcp - lists.icann.org

Re: REMINDER: Meeting Invitation/ ISPCP OUTREACH COMMITTEE CALL
by Mike O'Connor Oct. 10, 2013

Oct. 10, 2013

hm… i wonder if i goofed this up. we just had a call, where the Outreach committee met. i wonder if we should change this one to an ISPCP "general" call? i think i'll copy the whole list and see how this time works for other people. sorry about the confusion -- can you all check your calendars and see whether time time would work for you? thanks, mikey On Oct 10, 2013, at 7:56 AM, Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: > Dear All, > > The next ISPCP Outreach Committee call is scheduled on Monday 14 October 2013 at 1300 UTC. > > To check your local time: > http://tinyurl.com/psxypoh > > Adobe Connect room: https://icann.adobeconnect.com/_a819976787/ispcp/?launcher=false > > Please find the dial-in details below: > > Participant Passcode: Participant: 3429 # > > Dial-in numbers: http://www.adigo.com/icann/ > > Thank you. > Kind regards, > Nathalie > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 3

RE: [ispcp] Outreach call
by Tony Holmes Oct. 10, 2013

Oct. 10, 2013

Excellent thanks Alain Ive also just received my copies. Tony From: alain.bidron(a)orange.com [mailto:alain.bidron@orange.com] Sent: 10 October 2013 15:15 To: Tony Holmes; Ispcp mailing list Cc: 'Anthony Harris' (harris(a)cabase.org.ar) Subject: RE: [ispcp] Outreach call I have just received the ISPCP Brochures mailed to my office by the ICANN staff. Just on time to used them during the next RIPE meeting in Athens next week and the next IGF meeting in Bali the week after. De : owner-ispcp(a)gnso.icann.org [mailto:owner-ispcp@gnso.icann.org] De la part de Tony Holmes Envoyé : lundi 7 octobre 2013 09:59 À : Ispcp mailing list Objet : [ispcp] Outreach call ---------------------------------------------------------------------------- --------------------------------------------------------------------------- ------ Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son carnet d'adresses. Vous pouvez le faire en utilisant ce modele <http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Do cuments/nouvelle_adresse.msg> d'email. Merci Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? You can use this email template <http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Do cuments/nouvelle_adresse.msg> if you like. Thanks ---------------------------------------------------------------------------- --------------------------------------------------------------------------- ------ Just a reminder to those involved in the ISPCP outreach activities that there is a call scheduled for 13.00 UTC today. All those involved should have received call-in details via a separate email. If thats not the case please contact me for those details. Tony ____________________________________________________________________________ _____________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Fw: [council] Resolution on New gTLD Collision Occurrence Management from the new gTLD committee meeting 7 Oct 2013
by WUKnoben Oct. 9, 2013

Oct. 9, 2013

FYI Wolf-Ulrich -----Ursprüngliche Nachricht----- From: Bruce Tonkin Sent: Wednesday, October 09, 2013 11:58 AM To: council(a)gnso.icann.org Subject: [council] Resolution on New gTLD Collision Occurrence Management from the new gTLD committee meeting 7 Oct 2013 From: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-07oct13… 1. Main Agenda: a. New gTLD Collision Occurrence Management Whereas, on 15 March 2013, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 057: SSAC Advisory on Internal Name Certificates. Whereas, in response to the overall issues highlighted in SAC 057, the ICANN Board directed the President and CEO, in consultation with the SSAC, to commission a study on the use of TLDs that are not currently delegated at the root level of the public DNS (the "Name Collision Study"). Whereas, the Name Collision Study, together with a proposal to manage the risks identified in the Name Collision Study (the "Proposal") was published for public comment from 5 August to 17 September. The Proposal has been revised in response to public comments. Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.10.07.NG01), the NGPC directs the President, Generic Domains Division to implement the proposal to manage the occurrence of collisions between new gTLDs and existing private uses of the same strings as presented in the "New gTLD Collision Occurrence Management Plan" attached as Annex 1 (http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1… ) and in doing so to take into account further advice that may be offered by SSAC and other experts and stakeholders. Resolved (2013.10.07.NG02), the NGPC directs the ICANN President and CEO, and as appropriate through the President, Generic Domains Division, to appropriately target the planned outreach campaign. The NGPC also recommends to the Board that: (1) the ICANN Board Risk Committee expressly reviews this matter and reports back to the Board, and continues to review and report at regular intervals; (2) the Board directs the ICANN President and CEO to develop a long-term plan to manage name collision at the root; and (3) the Board directs the ICANN President and CEO to work with the community to develop a long-term plan to retain and measure root-server data.

1 0

Outreach call
by Tony Holmes Oct. 7, 2013

Oct. 7, 2013

Just a reminder to those involved in the ISPCP outreach activities that there is a call scheduled for 13.00 UTC today. All those involved should have received call-in details via a separate email. If that's not the case please contact me for those details. Tony

1 0

Fw: [council] Agenda for new gTLD Program Committee - 4 Oct 2013
by WUKnoben Oct. 4, 2013

Oct. 4, 2013

FYI Best regards Wolf-Ulrich -----Ursprüngliche Nachricht----- From: Bruce Tonkin Sent: Thursday, October 03, 2013 8:30 AM To: council(a)gnso.icann.org Subject: [council] Agenda for new gTLD Program Committee - 4 Oct 2013 Hello All, Note that the new gTLD Program Committee will be discussing Name Collision Risk Management at its meeting on Friday 4 October 2013. See: http://www.icann.org/en/groups/board/documents/agenda-new-gtld-04oct13-en.h… Regards, Bruce Tonkin

1 0

fake renewal notices
by Mike O'Connor Oct. 3, 2013

Oct. 3, 2013

hi Wolf-Ulrich and Osvaldo was there any discussion of the Fake Renewal Notices issue in the Council meeting? i noticed that it has been put on hold in the Consent Agenda. my recollection was that Mason Cole was going to run with that one and come back to the Council with a plan for what to do about those. did he ever do that? thanks, mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

2 2

Fw: [council] Resolutions from the ICANN Board meeting held in Los Angeles on 28 Sept 2013
by WUKnoben Oct. 2, 2013

Oct. 2, 2013

FYI. See in particular the decisions re GNSO review and GNSO Stakeholder Group and Constituency Charter Amendments Best regards Wolf-Ulrich -----Ursprüngliche Nachricht----- From: Bruce Tonkin Sent: Wednesday, October 02, 2013 11:37 AM To: council(a)gnso.icann.org Subject: [council] Resolutions from the ICANN Board meeting held in Los Angeles on 28 Sept 2013 Hello All, See below the resolutions from the ICANN Board meeting held on 28 Sept 2013. The key topics of interest to the GNSO were: - approval of the policy for Locking of a Domain Name subject to UDRP Proceedings - kicking off review of GNSO in 2014 - appointment of Cheryl Langdon-Orr as the 2014 Nominating Committee Chair and Stéphane Van Gelder as the 2014 Nominating Committee Chair-Elect. - a Proposed Process for GNSO Stakeholder Group and Constituency Charter Amendments - a Clarification Regarding the Competition, Consumer Trust and Choice Metrics for the New gTLD Program per the AoC Review Regards, Bruce Tonkin From: http://www.icann.org/en/groups/board/documents/resolutions-28sep13-en.htm Approved Board Resolutions | Regular Meeting of the ICANN Board 28 September 2013 1. Consent Agenda: a. Approval of Board Meeting Minutes Resolved (2013.09.28.01), the Board approves the minutes of the 17 July, 18 July and 22 August 2013 Meetings of the ICANN Board. b. Delegation of a ccTLD for Iran in Arabic script Resolved (2013.09.28.02), as part of the exercise of its responsibilities under the IANA Functions Contract, ICANN has reviewed and evaluated the request to delegate the ایران ("Iran") countrycode top-level domain to the Institute for Research in Fundamental Sciences. The documentation demonstrates that the proper procedures were followed in evaluating the request. Resolved (2013.09.28.03), the Board directs that pursuant to Article III, Section 5.2 of the ICANN Bylaws, that certain portions of the rationale not appropriate for public distribution within the resolutions, preliminary report or minutes at this time due to contractual obligations, shall be withheld until public release is allowed pursuant to those contractual obligations. c. GNSO Locking of a Domain Name Subject to UDRP Proceedings PDP Recommendations Whereas, on 15 December 2011, the GNSO Council launched a Policy Development Process (PDP) on the Locking of a Domain Name subject to UDRP Proceedings addressing five charter questions, set forth at https://community.icann.org/x/ma-bAQ. Whereas, the PDP followed the prescribed PDP steps as stated in the Bylaws resulting in a Final Report delivered on 5 July 2013. Whereas, the Locking of a Domain Name subject to UDRP Proceedings Working Group (WG) reached full consensus on the recommendations in relation to the issues outlined in the Charter. Whereas, the GNSO Council reviewed, and discussed the recommendations of the Locking of a Domain Name subject to UDRP Proceedings WG, and adopted the Recommendations on 1 August 2013 by a Supermajority and unanimous vote (see http://gnso.icann.org/en/council/resolutions#201308) Whereas, the GNSO Council vote met and exceeded the required voting threshold to impose new obligations on ICANN contracted parties. Whereas, after the GNSO Council vote, a public comment period was held on the approved recommendations, and the comment received has been summarized and considered (http://www.icann.org/en/news/public-comment/locking-domain-name-recommendat…) Resolved (2013.09.28.04), the Board adopts the GNSO Council Policy Recommendations on the Locking of a Domain Name subject to UDRP Proceedings as set forth in the Final Report (see http://gnso.icann.org/en/issues/locking/domain-name-final-05jul13-en.pdf [PDF, 1.01 MB]). Resolved (2013.09.28.05), the President and CEO is directed to develop and complete an implementation plan for these Recommendations and continue communication with the community on such work. d. Country Code Names Supporting Organization (ccNSO) Review Implementation Whereas, on 21 April 2011, the Board resolved to direct ICANN staff, in coordination with the Structural Improvements Committee (SIC), to develop a proposed implementation plan and timeline for the recommendations in the Final Report of the ccNSO Review Board Working Group [PDF, 294 KB] and to submit these to the Structural Improvements Committee for review and Board approval (Resolution 2011.04.21.06). Whereas, at its 18 June 2011 meeting, the SIC acknowledged receipt from staff of an implementation plan, titled "ccNSO Improvements Implementation Project Plan", dated 9 June 2011, and resolved to recommend it to the ICANN Board for approval. Whereas, at its 24 June 2011 meeting, the Board resolved to request that ICANN CEO direct staff to proceed with the implementation in accordance with the implementation plan document ccNSO Improvements Implementation Project Plan dated 9 June 2011 [PDF, 508 KB] (Resolution 2011.06.24.03). Whereas, on 27 September 2013, the SIC acknowledged receipt of a letter from the ccNSO Chair announcing completion of the ccNSO review implementation in complement of a final ccNSO implementation Project Plan update, dated September 2013. Whereas, on 27 September 2013, the SIC agreed to recommend that the ICANN Board receive the final ccNSO implementation Project Plan update [PDF, 170 KB], dated September 2013, note the implementation phase of the ccNSO review as complete, and commence the assessment phase inherent in the review cycle. Resolved (2013.09.28.06), the Board receives the final ccNSO implementation Project Plan update, dated September 2013, and notes the completion of the implementation of the ccNSO review recommendations. Resolved (2013.09.28.07), the Board directs the ICANN President and CEO to assess the improvements arising out of the ccNSO review in accordance with the assessment phase of the organizational review cycle. Resolved (2013.09.28.08), the Board thanks the ccNSO for its implementation work. e. GNSO Review Whereas, under ICANN's Bylaws the next review of the GNSO was due to commence in 2013. Whereas, the SIC solicited and considered public comments on whether the review should be postponed and a new schedule for the review be established within the next six months. Whereas, it is important that the review of the GNSO take into account the outcomes of ICANN's strategic planning efforts and the Accountability and Transparency Review Team 2's work, which can only be achieved through the initiation of a GNSO review in 2014. Resolved (2013.09.28.09), that the Board directs the SIC to schedule the review of the Generic Names Supporting Organization (GNSO), which is mandated by ICANN Bylaws Article IV, Section 4, to commence in 2014, and that preparations for this Review commence as soon as feasible. 2. Main Agenda: a. Appointment of 2014 Nominating Committee Chair and Chair-Elect Whereas, the BGC reviewed the Expressions of Interest from candidates for the 2014 Nominating Committee ("NomCom") Chair and Chair-Elect, interviewed those candidates and considered the results of a 360-degree evaluation of the 2013 NomCom leadership. Whereas, the BGC has recommended that Cheryl Langdon-Orr be appointed as the 2014 NomCom Chair and Stéphane Van Gelder be appointed as the 2014 NomCom Chair-Elect. Resolved (2013.09.28.10), the Board hereby appoints Cheryl Langdon-Orr as the 2014 Nominating Committee Chair and Stéphane Van Gelder as the 2014 Nominating Committee Chair-Elect. b. Treatment of New gTLD Historical Costs Whereas, ICANN incurred costs over several years to design and prepare the launch of the New gTLD Program. Whereas, the costs incurred from October 2007 (the date of the GNSO recommendation on the New gTLD Program) to the launch of the program ("Historical Development Costs") are to be repaid to ICANN from a portion of the New gTLD Program application fees. Whereas, the Historical Development Costs are charged to the Program progressively as the evaluation work advances and the fees become non-refundable, which began in July 2012. Whereas, the Board Finance Committee has recommended that the amount of Historical Development Costs repaid to ICANN's operating fund from the New gTLD Program be transferred to the Reserve Fund. Resolved (2013.09.28.11), the Board authorizes the President and CEO, or his designee(s), to take all actions necessary to transfer, when and as appropriate, from ICANN's operating fund to ICANN's Reserve Fund all amounts, whether already paid or to be repaid in the future, that constitute Historical Development Costs. c. Proposed Process for GNSO Stakeholder Group and Constituency Charter Amendments Whereas, The ICANN Bylaws (Article X, Section 5.3) state, "Each [GNSO] Stakeholder Group … and each of its associated Constituencies shall maintain recognition with the ICANN Board." Whereas, it is important that GNSO Stakeholder Groups and Constituencies have the flexibility to update, modify and evolve their organizational charters to reflect community changes while balancing the need for validation by the Board. Whereas, there is currently no procedure for a GNSO Stakeholder Group or Constituency to obtain approval by the ICANN Board of Directors for an amendment of its charter. Whereas, the Structural Improvements Committee of the ICANN Board has formulated and recommended a process by which GNSO Stakeholder Groups and Constituencies can amend their charters with the Board maintaining its appropriate validation responsibilities for recognition of those GNSO groups. Whereas, the community has had the opportunity to review and comment on the proposed process and changes have been made to the proposed process to address community suggestions. Resolved (2013.09.28.12), the Board approves the process formulated and recommended by the Structural Improvements Committee and directs ICANN Staff to notify the leadership of the various GNSO Stakeholder Groups and Constituencies of the process and post a copy of the approved process on the GNSO web site within seven calendar days. d. Clarification Regarding the Competition, Consumer Trust and Choice Metrics for the New gTLD Program per the AoC Review Whereas, on 18 July 2013, the ICANN Board directed the CEO to commence the process for convening the Competition, Consumer Trust and Consumer Choice (CCT) Review Team to facilitate preliminary work on the feasibility, utility and cost-effectiveness of adopting the recommendations of the GNSO Council and the ALAC, as well as analyzing other potential metrics to be made available for the CCT review. Whereas, the Board wishes to clarify its Resolutions 2013.07.18.06 and 2013.07.18.07 to identify that the actual CCT review is not being commenced at this time, rather that an Implementation Advisory Group for Competition, Consumer Trust and Consumer Choice is approved for empanelment. The work of this Advisory Group is intended to be an input to the CCT review at the point in the future when the CCT review is commenced according to the schedule set forth in the Affirmation of Commitments (AoC). Resolved (2013.09.28.13), the Board directs the CEO to convene a volunteer group (the Implementation Advisory Group for Competition, Consumer Trust and Consumer Choice) in advance of a future AoC Competition, Consumer Trust and Consumer Choice Review Team, for the purpose of: (i) evaluating and reporting to the Board on the feasibility, utility and cost-effectiveness of adopting the recommendations of the GNSO Council and the ALAC; (ii) evaluating other inputs, including historical data regarding metrics used to evaluate earlier rounds of new gTLDs (2000, 2004); (iii) engaging with the GNSO, ALAC and staff in an effort to reach agreement on the metrics; and (iv) proposing a set of metrics to be compiled by ICANN to be made available to a future AoC Review Team examining the New gTLD Program. Resolved (2013.09.28.14), the portions of Resolutions 2013.07.18.06 and 2013.07.18.07 suggesting that the CCT review was being commenced prior to the time called for within the AoC are retracted.

1 0

Fwd: [council] Regarding 2014 Nominating Committee leadership
by Wolf-Ulrich.Knoben＠t-online.de Oct. 2, 2013

Oct. 2, 2013

Sent from my personal phone Anfang der weitergeleiteten E‑Mail: > Von: Bruce Tonkin <Bruce.Tonkin(a)melbourneit.com.au> > Datum: 2. Oktober 2013 07:01:45 MESZ > An: "council(a)gnso.icann.org" <council(a)gnso.icann.org> > Betreff: [council] Regarding 2014 Nominating Committee leadership > > > > From: http://www.icann.org/en/news/announcements/announcement-01oct13-en.htm > > ICANN Appoints Chair and Chair-Elect for the 2014 Nominating Committee (NomCom) > > 1 October 2013 > > The ICANN Board is pleased to announce that it has appointed Cheryl Langdon-Orr as Chair and Stéphane Van Gelder as Chair-Elect for the 2014 Nominating Committee (NomCom) [http://www.icann.org/en/groups/board/documents/resolutions-28sep13-en.htm#2…] At Cheryl's request, Yrjö Länsipuro has agreed to serve as Associate Chair for the 2014 NomCom. These three members of the 2014 NomCom Leadership are well-known personalities in the ICANN community with in-depth knowledge of ICANN from many years of involvement and experience in ICANN. Cheryl Langdon-Orr serves as Chair-Elect of the 2013 NomCom, Stéphane Van Gelder is a member of the 2013 NomCom, and Yrjö Länsipuro serves as Chair of the 2013 NomCom and was a member of the 2011 and 2012 NomComs. > > Cheryl commented on her appointment as Chair of the 2014 NomCom, stating: > > "I am delighted to be working again in 2014 with Stéphane and Yrjö, having served with them in 2013 whilst Chair Elect, but this time as the 2014 NomCom Leadership Team. We can assure the ICANN Community and Stakeholders, that we will be continuing to build on the continued evolution in practices and changes to ICANN's Nominating Committee transparency that have been seen in 2013. We are looking forward and planning for the 2014 NomCom 'kick off' meeting and activities following the ICANN Public meeting in Buenos Aires in November 2013, which is when the work of the 2014 NomCom starts, and where we formally take our seats with the rest of the appointed Community representatives and voting delegates." > > After its initial meetings later this year, the 2014 NomCom will issue a public call for applicants to the open ICANN leadership positions and work to reach their final selections in 2014. The NomCom's activities can be followed on the NomCom website, at http://nomcom.icann.org , where all relevant documentation regarding NomCom can be found. > > > About the NomCom Leadership: > > The NomCom Chair is responsible for organizing the NomCom in its activities to select ICANN Board members and individuals who will serve in other key leadership positions within ICANN's Supporting Organizations (SO) and Advisory Committees (AC) in accordance with ICANN's Bylaws. The Chair-Elect serves alongside the Chair, with anticipated succession into the role of the Chair for the subsequent year's NomCom. The Associate Chair, selected by the Chair, assists with the duties of the Chair. The Chair, the Chair-Elect and Associate Chair are non-voting members of the NomCom. > >

1 0