December 2017 - council - lists.icann.org

Fwd: Resignation from SSR2 Review Team
by Heather Forrest Dec. 10, 2017

Dec. 10, 2017

Dear Council colleagues, I regretfully forward the email below from James Gannon re his decision to resign from SSR2 Review Team. Prior to receiving this message the GNSO Secretariat was in the process of scheduling a call between Council leadership and our GNSO reps to help determine how best to kick off a broader conversation within the GNSO. As you can see from my email below I have expressed to James Gannon that we're hopeful he might be willing to attend that call. Council leadership will put together an action plan for next steps and circulate this as soon as possible. In the meantime, any and all suggestions, inputs, ideas and comments, keenly encouraged via the list. Best wishes, Heather ---------- Forwarded message ---------- From: Heather Forrest <haforrestesq(a)gmail.com> Date: Sat, Dec 9, 2017 at 11:13 AM Subject: Re: Resignation from SSR2 Review Team To: James Gannon <james(a)cyberinvasion.net> Dear James, I am very sorry to receive your email, not least because I feel that "the community" is not unified in this matter and the impression exists that all SOs and ACs feel that the Board acted appropriately. Certainly neither James nor I have received instructions to that effect, and the GNSO has been caught off guard, scrambling to discern what has led us to this bizarre point. The GNSO Secretariat is in the process of reaching out to you and your fellow GNSO members of SSR2 for a call to help us better understand where we are. I very much hope that you would be willing to participate, as without your perspective, it's very hard to know what we should be doing to support you (GNSO reps) and how/when to do that. On behalf of the GNSO I thank you most heartily for your service, and I appreciate any feedback you can give to help us improve as a Council and community. Best wishes, Heather Forrest On 09/12/2017 2:20 AM, "James Gannon" <james(a)cyberinvasion.net> wrote: > > Hi All, > > After much consideration and evaluation I have decided to resign from the SSR2 review team. This is due in part to the changes in my personal life, my employment in a new role and also partly due to the situation that the SSR2 review currently finds itself in. I feel that its very unfortunate that there has seemingly been a loss in trust from the community in the review team and I feel that the work and dedication from the review team members should be recognised. > > When the review (hopefully) restarts I hope that the community leaders choose to make a strong declaration of support of their appointed members and empower them to run the independent review in the same fashion that the reviews were executed in previous years and iterations. > > I hope to continue my involvement in the ICANN community including representing the non RYSG GNSO community on the CSC. > I wish to wish the review team the very best of luck in executing against the plan and will likely sign up as an observer to the review team in the new year. > > Regards, > James Gannon

1 0

Fwd: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review
by Heather Forrest Dec. 8, 2017

Dec. 8, 2017

Dear colleagues, Following up on our discussion just now on SSR2 RT, please find here the skills matrix and scoping document developed by the Review Team. The formal scope approved by the SSR-RT can be found on https://community.icann.org/display/SSR/Terms+of+Reference. Scope is on pages 4-5. Staff - could you please help us to coordinate volunteers for a small team to review these documents? I'll follow up by separate post on logistics of meeting with our SSR2 members. Many thanks to all for an effective Council meeting! Best wishes, Heather ---------- Forwarded message ---------- From: Denise Michel <denisemichel(a)fb.com> Date: Sat, Nov 11, 2017 at 3:11 PM Subject: Re: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org> Dear SO & AC Chairs: Please find attached a description of the SSR2 Review Team’s perspective of the scope of this review, and a skill matrix developed and completed by a majority of the Team. As requested, the SSR2 is completing these requested items to “[resolve] the issues identified and discussed before and during ICANN60 related to scope and skills.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review and relevant, useful skills. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here <https://community.icann.org/display/SSR/Terms+of+Reference?preview=/6407612…>. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki <https://community.icann.org/display/SSR/SSR2+Review>. Please let us know if you require anything further. We’d appreciate confirmation of receipt of this email and of the 4 Nov. email (copy included below), as well as a response to our previous request for information regarding the Team’s “un-pausing” (see below). Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) *From: *<ssr2-review-bounces(a)icann.org> on behalf of Denise Michel < denisemichel(a)fb.com> *Date: *Saturday, November 4, 2017 at 12:16 AM *To: *SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> *Cc: *SSR2 <ssr2-review(a)icann.org> *Subject: *[Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review Dear SO/AC Chairs: As one of the co-chairs of the SSR2, I’ve been asked to share an informal update on the Review Team’s work, and a query. The SSR2 met Friday 3 Nov., addressed scope and skills as directed, and then adjourned, since our work is “paused.” Specifically, the Review Team developed a skills matrix and a document clarifying SSR2’s scope/terms of reference. These drafts have been shared with all Review Team members for edits (not all participated in the 3 Nov. meeting), and we plan to finalize and deliver them to you next week. (Note that SSR2 operates by consensus and input from all Team members may necessitate a slight extension of this schedule, or not). The SSR2 would appreciate receiving information from the chairs on how and when you will decide on “un-pausing” this review. As you can appreciate, the Review Team’s volunteers would like more certainty as to their schedules. SSR2 previously planned a January face-to-face drafting session for which time has been blocked on our calendars and travel arrangements have been made. Please advise if we should cancel these. Please let us know if you need anything else from the Review Team (cc’d). Best, Denise Denise Michel *denisemichel(a)fb.com <denisemichel(a)fb.com>* *From: *Patrik Fältström <paf(a)frobbit.se> *Date: *Thursday, November 2, 2017 at 7:29 PM *To: *Denise Michel <denisemichel(a)fb.com> *Cc: *SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Eric Osterweil <eosterweil(a)verisign.com> *Subject: *Re: Statement from SO/AC Chairs on the suspension of the Security and Stability Review Your interpretation is correct. The goal now is to unpause SSR2. Please not that I do not have posting rights to the SSR2 list, so the moderated message must be released or forwarded by someone with posting rights. Best, Patrik On 2 Nov 2017, at 21:06, Denise Michel <denisemichel(a)fb.com> wrote: Thanks for forwarding, Patrick. Could the SO/AC Chairs please clarify the SSR2’s status tonight as the SSR2 is meeting tomorrow morning. My quick read of this indicates that SSR2 is still “paused” except that the Team is to address “resolving the issues identified and discussed before and during ICANN60 related to scope and skills.” That takes the work plan and other items off the table. Thanks for clarifying. Best Denise Denise Michel Sent via phone _____________________________ From: Patrik Fältström <paf(a)frobbit.se> Sent: Thursday, November 2, 2017 7:42 PM Subject: Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Osterweil, Eric <eosterweil(a)verisign.com>, Denise Michel <denisemichel(a)fb.com> STATEMENT FROM SO/AC CHAIRS ON THE SUSPENSION OF THE SECURITY AND STABILITY REVIEW The Chairs of ICANN’s Supporting Organizations (SOs) and Advisory Committees (ACs) acknowledge the 28 October 2017 announcement from the Board of Directors, pausing the work of the Security, Stability and Resiliency Review Team (SSR2-RT), and the Board's having tasked the SOs and ACs in sessions this week with addressing concerns raised by the Board, Organizational Effectiveness Committee (OEC), and the Security and Stability Advisory Committee (SSAC). Collectively, we accept responsibility for getting SSR2-RT restarted as expeditiously as possible. During various sessions throughout ICANN60, our groups have met with the Board and/or members of SSR2-RT to hear their concerns. We intend to continue to consult with our respective communities, and each other, to assess and address issues relating to the scope, composition and participation, resource utilization, and overall work plan of the Review. Additionally, the Board’s unilateral decision to suspend the work of a key accountability mechanism has raised questions that go to the independence of SSR2-RT, and specific reviews going forward. As a follow-on effort, we intend to examine the selection and scoping process for review teams, and develop a clear and predictable process for raising and addressing concerns about review teams. We also intend to carefully consider the Board's action, with a view to preventing similar instances in the future. We look forward to working collaboratively with the Board, SSR2-RT and the broader community on this task. The SO/AC Chairs support the SSR2 RT meeting on Friday, 3 November 2017, and followup telephone conferences when needed. These are necessary so that the team can work on resolving the issues identified and discussed before and during ICANN60 related to scope and skills. Finally, we wish to acknowledge the efforts of our colleagues on the SSR2-RT to date, and thank them for their continued commitment towards security, stability and resiliency. Alan Greenberg (Chair ALAC) Patrik Fältström (Outgoing Chair SSAC) Rod Rasmussen (Incoming Chair SSAC) Katrina Sataki (Chair ccNSO) Thomas Schneider (Outgoing Chair GAC) Manal Ismail (Incoming Chair GAC) James Bladel (Outgoing Chair GNSO Council) Heather Forrest (Incoming Chair GNSO Council) Tripti Sinha(Co-Chair RSSAC) Brad Verd (Co-Chair RSSAC) _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

4 5

ECO GDPR Public Consultation Event
by Michele Neylon - Blacknight Dec. 8, 2017

Dec. 8, 2017

All GDPR was one of the hot topics at the recent ICANN meeting and is definitely having impact on many facets of our work on Council. With the clock ticking towards May 2018 many of us want to find a workable and legal path forward. With that in mind ECO are holding a GDPR Industry Playbook consultation next Monday in Brussels. Remote participation will be available. Full details here: https://web.eco.de/event/gdpr-domain-industry-playbook-public-consultation/ There is a draft document, but as it's nearly 5 MB I won't fill your inboxes with it - if you'd like a copy please let myself or Thomas know Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845

1 0

Fwd: [Ext] Re: Request For Community Selection Panel Participants – 2018 Multistakeholder Ethos Award Program
by Heather Forrest Dec. 8, 2017

Dec. 8, 2017

Dear Council colleagues, Sincere thanks in advance to Rafik Dammak and Keith Drazek for serving as this year's Council representatives on the Multistakeholder Ethos Award selection panel. Traditionally, the Council has been represented by the two vice chairs. This is the third year of this initiative, and the organizers expressed an interest in limiting representatives to 2 consecutive terms on the selection panel, rendering Donna ineligible (she and I served in our roles as Council Vice Chair in 2016/17 and 2015/16). In Donna's stead, Keith has agreed to serve. Below please find David Olive's confirmation of our representatives. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Wed, Dec 6, 2017 at 1:04 AM Subject: Re: [Ext] Re: Request For Community Selection Panel Participants – 2018 Multistakeholder Ethos Award Program To: Heather Forrest <haforrestesq(a)gmail.com> Thanks Heather. We welcome Rafik and Keith. Regards. David Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) On Dec 5, 2017, at 7:43 AM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear David, I am pleased to notify you that Rafik Dammak and Keith Drazek will represent the GNSO in this year's Ethos selection panel. It was an honour to serve on the panel in the previous two years. With best wishes, Heather Forrest On 21/11/2017 12:48 PM, "David Olive" <david.olive(a)icann.org> wrote: > Dear Heather, Filiz, Katrina, Manal, Tripti, Alan, Patrik, Rod, and Brad: > > > > The process for the 2018 Multistakeholder Ethos Award is opening shortly, > and I would like to give you some more details about the Award, our goal of > presenting the fourth annual award at the ICANN62 Policy Forum and the > desire to have up to two members from each of your communities made > available to help choose the recipient(s) of the award. > > > > Following a successful collaboration between staff and panelists who > served on last year’s selection committee, the award program has been > maintained intact for this year. Notable changes were rolled out last year, > as you may be aware, which included updated award criteria language and a > more detailed and streamlined nomination process via a nomination form. > Panelists also shared positive feedback regarding the introduction of calls > with nominators which were decisive in the selection process last year. > Please find attached an overview document outlining the program details. > > > > In order to achieve the goal of presenting the award at ICANN62, we will > announce the opening of the recipient nomination period in a couple of > weeks – we are targeting the second week of December. That nomination > period will run through the 19th of March 2018 for nominations to be > submitted from the full ICANN community. > > > > *In the meantime, between now and 15 January 2018 we’d like to identify > interested community members from your communities to help select the > recipient(s) of the award. Following the framework used for the previous > awards, we would like to offer you the opportunity to name up to two people > from your community (including yourself if you would like) to comprise the > panel that will select the award recipient(s). * > > > > I’d like to take this opportunity to thank panelists who served on > previous panels and helped shape the award process for the future. *Moving > forward it would be ideal for panelists to serve a maximum of two > consecutive terms on the selection panel to ensure diversity and variety of > input and equal opportunity among community members to take part in this > valuable effort of fellow recognition*. Alternatively, it would be great > if one of the two slots could be rotated, for the reasons listed above. > > > > With appropriate staff support, we envision the workload of the selection > panelists will be limited. Some time will be necessarily devoted to > reviewing nominations, but we expect weekly one-hour calls from the end of > March to June to discuss the process, review the nominations and select the > award recipient. > > > > *We’d like to have panelist names from you by 15 January 2018* so that an > initial panelist call can be scheduled before the nomination period ends, a > second call can take place shortly after the nomination period closes and > then additional calls can be scheduled to make award recipient decisions. > > > > Following the successful efforts carried out in London, Buenos Aires, > Helsinki and Johannesburg and the positive feedback received from the > selection panels, we are happy to reaffirm that this award will be an > annual award to be presented during the welcome reception of the Policy > Forums. Please note that volunteers who previously served on the selection > panel are welcome to serve again, if they wish to do so, bearing in mind > some diversity of input and a two consecutive term cap. > > > > Please share any thoughts, comments or ideas with me on this list. I look > forward to working with you on this effort. > > > > Best regards, > > > > David > > > > > > > > > > David A. Olive > Senior Vice President > > Policy Development Support > Internet Corporation for Assigned Names and Numbers (ICANN) > > >

1 0

Reminder: Document and Motion deadline Monday 11 December 2017 at 23:59 UTC for the GNSO Council Meeting 21 December 2017 at 12:00 UTC
by Nathalie Peregrine Dec. 7, 2017

Dec. 7, 2017

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 11 December 2017 at 23:59 UTC) of the GNSO Council Meeting on 21 December 2017 at 12:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/6RJyB Thank you very much. With kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 1

New gTLD Subsequent Procedures PDP WG newsletter - December 2017
by Emily Barabas Dec. 6, 2017

Dec. 6, 2017

Dear all, On behalf of the leadership team of the New gTLD Subsequent Procedures PDP Working Group, I am writing to share the latest edition of the Working Group newsletter: https://gnso.icann.org/en/news/working-group-newsletters/newsletter-new-gtl…. Please feel free to share this newsletter with individuals and groups who may be interested in the Working Group’s activities. An archive of previous editions of the newsletter is available on the WG wiki<https://community.icann.org/pages/viewpage.action?pageId=58001970> and on the GNSO website<https://gnso.icann.org/en/news/working-group-newsletters>. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

January strategic session agenda as posted during Council meeting
by Heather Forrest Dec. 6, 2017

Dec. 6, 2017

Dear colleagues, Following up on the action items from our Council meeting last week, please find attached the most current version of the January strategic session agenda, as posted in the AC at the meeting. Best wishes, Heather

1 0

Action Items: GNSO Council meeting 30 November 2017
by Nathalie Peregrine Dec. 5, 2017

Dec. 5, 2017

Dear Councilors, Please find the action items, as stated during the meeting, below and as attachment arising from the GNSO Council meeting held on Thursday 30 November 2017. Please take note of the action items coming out of the Council sessions and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here<https://community.icann.org/x/RgZlAg>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. ACTION ITEMS FROM THE GNSO COUNCIL MEETING 30 NOVEMBER 2017 Item 4: COUNCIL VOTE – Adoption of the GNSO Council response to the GAC Communique for submission to the ICANN Board Voting Results: * Motion passed unanimously. Action Items: * Heather Forrest, as GNSO Chair, to communicate the GNSO Review of the Abu Dhabi GAC Communiqué to the ICANN Board, with copy to the GAC Chair. Item 5. COUNCIL VOTE – Referral of the privacy and proxy services issue, related to IRTP-C, to the PPSAI IRT Voting Results: * Motion passed unanimously. Action Items: * Council liaison to the PPSAI IRT to communicate Council decision to refer IRTP C Privacy / Proxy implementation issues to the PPSAI IRT. The Council liaison should direct the PPSAI IRT to the additional directives contained in the Resolved clauses here: https://gnso.icann.org/en/council/resolutions#201711 Item 6: COUNCIL VOTE – Confirmation of GNSO Representative to the Empowered Community Administration Voting Results: * Motion passed unanimously Action Items: * GNSO Secretariat to communicate decision by GNSO Council, confirming Heather Forrest will represent the GNSO as the Decisional Participant on the Empowered Community Administration until the end of the ICANN Annual General Meeting (ICANN63), to the ICANN Secretary. This communication will serve as the required written certification from the GNSO Chair, designating the individual who shall represent the Decisional Participant on the EC Administration. Item 7: COUNCIL VOTE – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation Decisions: * Motion withdrawn by Keith Drazek Action Items: * ICANN Staff to circulate call for volunteers to establish group of Councilors to develop draft guidelines and parameters around scope, deliverables, membership, operating procedures, etc. for subsequent group that will seek to determine Council’s next steps for addressing the feedback received in relation to the public comment forum on the new and possible alternative triggers for the ICANN Procedure For Handling Whois Conflicts with Privacy Law. Target date is 11 December, the Motions and Documents deadline for the 21 December meeting.. * Following approval by the GNSO Council of charter for this subsequent group, Subsequent Group to determine Council’s next steps for addressing the limitations of the ICANN Procedure For Handling Whois Conflicts with Privacy Law. Item 9: COUNCIL DISCUSSION – Update on the GNSO Council Standing Committee on ICANN budget Action Items: * Heather Forrest and ICANN Staff to attempt to re-draft possible public comment response regarding the Reserve Fund, to show Council’s awareness of the issue and to highlight comments from specific Stakeholder Groups and Constituencies. * Council members to consider re-draft and indicate possible objections within the timeframe provided (less than 24 hours to meet the deadline) Item 10: ANY OTHER BUSINESS 10. 2 – Update on the status of the Second Security, Stability, and Resiliency Review Team (SSR2-RT) Action Items: * ICANN Staff to circulate call for volunteers to establish group of Councilors to review SSR2-RT scoping information and skills matrix and prepare a draft response for Council consideration. Susan Kawaguchi and Carlos Raúl Gutiérrez have volunteered to date. * Council leadership to explore options for discussing challenges within the SSR2-RT with the GNSO appointed members of that review team (i.e., Denise Michel, James Gannon, and Norm Ritchie). Thank you, Kind regards, Nathalie -- Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Fwd: [Gdd-gnso-ppsai-impl] Referral of IRT Part C Privacy/Proxy Registration Implementation Issues to PPSAI IRT
by Darcy Southwell Dec. 5, 2017

Dec. 5, 2017

Fellow Councilors - below is my communication to the PPSAI IRT and ICANN staff's acknowledgement. Best, Darcy __________ *Darcy Southwell *| Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart ---------- Forwarded message ---------- From: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Mon, Dec 4, 2017 at 8:03 PM Subject: Re: [Gdd-gnso-ppsai-impl] Referral of IRT Part C Privacy/Proxy Registration Implementation Issues to PPSAI IRT To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Dear Darcy, Thank you very much for the update. Kind regards, Caitlin *From: *Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Darcy Southwell <darcy.southwell(a)endurance.com> *Reply-To: *"gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> *Date: *Monday, December 4, 2017 at 5:39 PM *To: *"gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> *Subject: *[Gdd-gnso-ppsai-impl] Referral of IRT Part C Privacy/Proxy Registration Implementation Issues to PPSAI IRT All, The GNSO Council passed the below resolution during the 30 November 2017 meeting. As GNSO Council Liaison to the PPSAI IRT, I'm communicating this to the entire IRT. Please not that this work is expected to be undertaken only after the upcoming PPSAI IRT comment period. *Motion to Refer IRTP Part C Privacy / Proxy Registrations Implementation Issues to PPSAI IRT* Submitted by Darcy Southwell Seconded by Donna Austin 1. The Generic Names Supporting Organization (GNSO) Council sent a letter (see https://gnso.icann.org/en/correspondence/bladel-to- crocker-01dec16-en.pdf) to the ICANN Board on 1 December 2016 regarding implementation concerns with the Inter-Registrar Transfer Policy ("Transfer Policy") – Part C for privacy/proxy registrations. Specifically, the concerns relate to whether the addition/removal of a privacy/proxy service potentially triggers the 60-day inter-registrar transfer lock described in the updated Transfer Policy. The policy recommendations were silent with respect to the addition/removal of privacy/proxy services, and at the time the policy was implemented, the current issue and potential harms described by the GNSO Council were not brought to ICANN org's attention. 2. In this letter, the GNSO Council requested the Board to instruct ICANN Org to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C. 3. On 16 March 2017, the Board instructed the ICANN President and CEO, or his designee(s), to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C and to report back to the GNSO Council with the results of the discussion.” During this time, enforcement of the policy related to this specific issue has been deferred. 4. The Registrar Stakeholder Group discussed this issue and reached out to other interested parties to evaluate alternatives for the implementation concerns related to IRTP Part C and recommended that this issue is further evaluated by the Privacy & Proxy Services Accreditation Issues Implementation Review Team (PPSAI IRT) as this group is best placed to determine if/how implementation of IRTP Part C for privacy / proxy registrations can be carried out. Resolved, 1. The GNSO Council directs the PPSAI IRT to consider the issue of privacy/proxy registrations and IRTP Part C as outlined in the annex to the GNSO Council letter (see https://gnso.icann.org/en/correspondence/bladel-to- crocker-01dec16-en.pdf) and to put forward recommendations for implementation that are consistent with the IRTP Part C policy recommendations as well as the PPSAI policy recommendations. 2. The GNSO Council requests that this work be undertaken only after the upcoming PPSAI IRT comment period, and that if it appears as though it will cause any significant or unreasonable delay in implementation of privacy/proxy service accreditation implementation, that the GNSO Council Liaison must alert the Council. 3. The GNSO Council encourages registrars and other impacted parties to join the PPSAI IRT to collaborate in these discussions. 4. The GNSO Council requests the GNSO Council Liaison to the PPSAI IRT (in consultation with ICANN org and the IRT) provides regular updates on the timeline for incorporating the issue of privacy/proxy registrations and the Transfer Policy into the work of the PPSAI implementation plan. Where issues emerge during implementation that may require possible policy discussion, the Council requests GNSO Council Liaison to the PPSAI IRT to escalate these issues using the designated procedure outlined in the Final Recommendations Report on Policy & Implementation. 5. The GNSO Council requests the GNSO Council Liaison to the PPSAI IRT to communicate this decision to the PPSAI IRT as soon as possible. Vote Results[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Best, Darcy __________ *Darcy Southwell *| Compliance Officer M: +1 503-453-7305 <(503)%20453-7305> │ Skype: darcy.enyeart _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

1 0

FW: [Ext] CCWG-Accountability-WS2 - Extension of closing dates for public consultations
by Marika Konings Dec. 5, 2017

Dec. 5, 2017

For your information. Best regards, Marika From: Bernard Turcotte <turcotte.bernard(a)gmail.com> Date: Tuesday, December 5, 2017 at 07:25 To: "soac-chairs(a)icann.org" <soac-chairs(a)icann.org>, Accountability Cross Community <accountability-cross-community(a)icann.org> Cc: Heidi Ullrich <Heidi.Ullrich(a)icann.org>, Steve Sheng <steve.sheng(a)icann.org>, Bart Boswinkel <bart.boswinkel(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Robert Hoggarth <robert.hoggarth(a)icann.org>, David Olive <david.olive(a)icann.org> Subject: [Ext] CCWG-Accountability-WS2 - Extension of closing dates for public consultations All, Given the low number of responses to the Diversity and Ombudsman public consultations the CCWG-Accountability WS2 is extending the closing date of these public consultations to align with its two other public consultations on Jurisdiction and Staff Accountability so that all of these will now close on Friday January 5th 2018. These four public consultations can be found at: • Enhancing Accountability - Recommendations for Diversity – Closes 5 January 2018 * https://www.icann.org/public-comments/accountability-diversity-2017-10-26-e…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> • Recommendations to Improve ICANN's Office of Ombudsman (IOO) – Closes 5 January 2018 * https://www.icann.org/public-comments/ioo-recs-2017-11-10-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> • Enhancing Accountability – Recommendations for Jurisdiction – Closes 5 January 2018 * https://www.icann.org/public-comments/accountability-recs-2017-11-13-en[ica…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> • Enhancing Accountability – Recommendations and Guidelines for Staff Accountability – Closes 5 January 2018 * https://www.icann.org/public-comments/recommendations-on-icann-jurisdiction…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> As explained and documented since ICANN 58 the CCWG-Accountability-WS2 will be publishing a final integrated report of all recommendations for public comment but will only be seeking comments on the resolution of any inconsistencies between the various individual report recommendations. As such, the community, including all SOs and ACs, are encouraged to provide any substantial comments they may have on the recommendations in the individual reports during the public consultations on these individual reports. The CCWG-Accountability-WS2 would like to take this occasion to remind the community that these recommendations will affect all parts of the ICANN community directly and as such the community is strongly encouraged to take the time to consider these and comment during the public comment period. It is also important to note that although all comments are considered equally that it is just as important for the community to show support for those recommendations they agree with. The CCWG-Accountability-WS2 Co-Chairs Thomas Rickert, Jordan Carter and Tijani Ben Jemaa

1 0