April 2017 - council - lists.icann.org

Reminder: Document and Motion deadline Monday, 8 May 2017 at 23:59 UTC for the GNSO Council Meeting 18 May 2017 at 12:00 UTC
by Nathalie Peregrine 27 Apr '17

27 Apr '17

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 8 May 2017 at 23:59 UTC) of the GNSO Council Meeting on 18 May 2017 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/eQLfAw Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC 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<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Open Board Sessions 6 and 7 May
by Austin, Donna 26 Apr '17

26 Apr '17

Just passing this along for those interested: https://www.icann.org/news/announcement-2-2017-04-25-en The ICANN Board of Directors will hold two open sessions during its upcoming workshop in Geneva, Switzerland, which will take place from 5 to 7 May 2017. The Board invites all interested individuals to join. Note that times are shown in Coordinated Universal Time (UTC). Marketplace Dynamics Session I: Registries and Registrars Saturday, 6 May, 11:15 - 12:00 UTC Internet Governance Engagement Strategy with a Focus on the Internet Governance Forums (IGFs): Proposal to the Board Sunday, 7 May, 09:00 - 10:00 UTC The sessions will be in English only. The format will be listen-only sessions via Adobe Connect: Adobe Connect Link: https://participate.icann.org/opencommunity/ Participant Code: 5969429891 Additional access numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=5969429891&num=1-719-… For more information, visit: https://www.icann.org/resources/pages/2017-board-meetings.

1 0

Re: [council] FW: GNSO Council Draft Response of the Copenhagen GAC Communiqué
by Nathalie Peregrine 26 Apr '17

26 Apr '17

Dear all, Please note that this has been posted on the GNSO website Correspondence page here: https://gnso.icann.org/en/council/correspondence Kind regards Nathalie From: <council-bounces(a)gnso.icann.org> on behalf of James Bladel <jbladel(a)godaddy.com> Date: Wednesday, April 26, 2017 at 5:32 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FW: GNSO Council Draft Response of the Copenhagen GAC Communiqué Councilors – Please note that Marika transmitted this letter, along with the current draft of our GNSO Response to the Copenhagen Communique, to the Board yesterday. Thank you, J. From: Marika Konings <marika.konings(a)icann.org> Date: Tuesday, April 25, 2017 at 20:50 To: "board-ops-team(a)icann.org" <board-ops-team(a)icann.org> Cc: "Thomas.Schneider(a)bakom.admin.ch" <Thomas.Schneider(a)bakom.admin.ch>, "James M. Bladel" <jbladel(a)godaddy.com>, Heather Forrest <haforrestesq(a)gmail.com>, "Austin, Donna" <Donna.Austin(a)neustar.biz>, "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org>, Mary Wong <mary.wong(a)icann.org> Subject: GNSO Council Draft Response of the Copenhagen GAC Communiqué Dear Board Operations Colleagues, Please be so kind as to forward at your earliest convenience the attached letter from the GNSO Council leadership to Dr. Crocker as Chairman of the ICANN Board. The letter concerns the GNSO Review of the GAC Communique to the ICANN Board. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. Thank you. Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

FW: GNSO Council Draft Response of the Copenhagen GAC Communiqué
by James M. Bladel 26 Apr '17

26 Apr '17

Councilors – Please note that Marika transmitted this letter, along with the current draft of our GNSO Response to the Copenhagen Communique, to the Board yesterday. Thank you, J. From: Marika Konings <marika.konings(a)icann.org> Date: Tuesday, April 25, 2017 at 20:50 To: "board-ops-team(a)icann.org" <board-ops-team(a)icann.org> Cc: "Thomas.Schneider(a)bakom.admin.ch" <Thomas.Schneider(a)bakom.admin.ch>, "James M. Bladel" <jbladel(a)godaddy.com>, Heather Forrest <haforrestesq(a)gmail.com>, "Austin, Donna" <Donna.Austin(a)neustar.biz>, "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org>, Mary Wong <mary.wong(a)icann.org> Subject: GNSO Council Draft Response of the Copenhagen GAC Communiqué Dear Board Operations Colleagues, Please be so kind as to forward at your earliest convenience the attached letter from the GNSO Council leadership to Dr. Crocker as Chairman of the ICANN Board. The letter concerns the GNSO Review of the GAC Communique to the ICANN Board. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. Thank you. Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

CSC Update April 2017
by James Gannon 25 Apr '17

25 Apr '17

Dear Councilors, Please find attached an update from myself as the Non-RySG liaison to the CSC on our progress to date. Please reach out if you have any questions or queries and I look forward to seeing you all at ICANN 59. -James Gannon

3 2

Re: [council] LAST CALL: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique
by Mary Wong 25 Apr '17

25 Apr '17

Dear all, Since no additional comments were received on the document, the Council chairs will proceed to write to the Board today informing them of the Council response and including the notes from Donna and James (below). The hope is that sending the letter today will be helpful to the Board as they meet with the GAC later this week on the Copenhagen Communique. Thanks and cheers Mary From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Monday, April 24, 2017 at 15:00 To: "Austin, Donna" <Donna.Austin(a)neustar.biz>, Mary Wong <mary.wong(a)icann.org>, Carlos Raul Gutierrez <crg(a)isoc-cr.org> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: [Ext] Re: [council] LAST CALL: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique Donna and Team – I’m fine with this, and agree we could note your last concern in the transmission letter. Something along the lines of (borrowing from and expanding upon Donna’s note): “Additionally, a recurring theme of many of our recent comments are to identify areas in which the GAC’s Communique appears to stray beyond the role of the GAC, or indeed, the mission and remit of ICANN. While these issues may not have immediate and direct implications for policy development, as representatives of the diverse community of GNSO stakeholders and constituents, the GNSO Council feels compelled to include these concerns in our response to each Communique. In particular, we note our concern with any Advice which conflicts with existing gTLD Consensus Policy or previous Board decisions, expands the role of the GAC or the mission of ICANN, or creates new rights or obligations for GNSO stakeholders outside of the defined Policy Development Process (PDP). We would welcome a broader discussion with the Board and GAC on this topic in the future.” Thank you, J. From: "Austin, Donna" <Donna.Austin(a)neustar.biz> Date: Monday, April 24, 2017 at 13:05 To: Mary Wong <mary.wong(a)icann.org>, Carlos Raul Gutierrez <crg(a)isoc-cr.org>, "James M. Bladel" <jbladel(a)godaddy.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: RE: [council] LAST CALL: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique Mary, all Thank you to everyone for their input. I’ve suggested some changes to the language responding to IGOs and 2 Characters with the intent of making the responses a little more focused. I’ve copied my suggested language below for ease of reference. I’m conscious that in our recent responses we have moved away some from the original intent of providing a GNSO Council response to GAC advice to the Board and I accept this as part of the evolution of this exercise. However, I don’t think it is appropriate for the Council to be telling the Board whether they should accept or reject GAC advice and for that reason I have removed that language from the original text on 2 characters. I also felt that we should be explicit with regard to the 2 character advice that the Board should not be re-opening this discussion after they have passed a resolution and had staff implement accordingly. On the IGO language, I have re-worked this with Mary’s help, to try to address Heather’s suggestions. It may also be worth explaining to the Board, in our transmittal letter, that at a meta level the Council is concerned that GAC advice does seem to be straying beyond the new ICANN bylaws and as a result potentially undermining the multi-stakeholder model and disenfranchising the broader ICANN community. As representatives of the stakeholder groups and constituencies that comprise the GNSO, the GNSO Council feels compelled to raise these issues with the Board where they appear as GAC advice. Perhaps this is also a conversation we should have with the Board at some point. Thanks Donna IGO Language: The GNSO Council refers to its previous response to the Board on this topic, which notes the ongoing work of the IGO-INGO Access to Curative Rights Protection Mechanisms Policy Development Process (PDP) Working Group. The GNSO Council appreciates the opportunity to participate in the facilitated discussion with the GAC at ICANN58, and the good faith dialogue that took place. In relation to the GAC’s advice to the Board to pursue implementation of: (i) a permanent system of notification to IGOs regarding second-level registration of strings that match their acronyms in up to two languages; and (ii) a parallel system of notification to registrants for a more limited time period, in line with both previous GAC advice and GNSO recommendations. The GNSO Council understands that the agreed outcome of the facilitated dialogue session at ICANN 58 was that further input from ICANN on the feasibility of permanent notification to IGOs is required; and that a parallel system of notification to registrants for a more limited time period, is in line with both previous GAC advice and GNSO recommendations. In relation to the GAC’s advice to the Board to facilitate continued discussions in order to develop a resolution that will reflect (i) the fact that IGOs are in an objectively unique category of rights holders and (ii) a better understanding of relevant GAC Advice, particularly as it relates to IGO immunities recognized under international law as noted by IGO Legal Counsels. The GNSO Council looks forward to continuing, in good faith, the discussions with the GAC and the Board on appropriate next steps, but is concerned that the GAC advice in this instance seems to suggest a predetermined outcome, which the Council believes is premature. As previously communicated to the Board, the ongoing PDP on IGO-INGO Access to Curative Rights Protection Mechanisms will take into account the GAC’s comments on the Initial Report. The GNSO Council notes that the Working Group is actively reviewing all comments received on its Initial Report, including the comments submitted by the GAC and a number of IGOs. 2 character language: There should be no opportunity for this Advice to cause the Board to re-open their decision on two letter codes at the second level, as contained in the Board’s resolution of 8 November 2016 and subsequent implementation, which came at the end of a long process that included community consultation and input. The Council is also concerned that the Consensus Advice contained in Section VI. 4. of the Communique that essentially requires the ICANN Board to negotiate directly, and reach resolution, with individual governments on two letter domain names at the second level is, in our view, inconsistent with the Consensus Advice mechanism found in the ICANN bylaws and as such should not be considered “Consensus Advice”. The GNSO Council regards this as an unhelpful attempt to sidestep requirements contained in the Bylaws to delegate GAC-equivalent consensus advice to individual GAC members, rather than the GAC as a whole. We note that this was discussed extensively during the CCWG-ACCT Workstream 1 process and was ultimately rejected. Bilateralism between the Board and individual GAC members also has the potential to undermine the utility of the GAC itself and is also inconsistent with ICANN’s commitment to the United States Government and other parts of the ICANN Community that the GAC or individual governments would not end up with more power in a post-transition ICANN. From: council-bounces(a)gnso.icann.org [mailto:council-bounces@gnso.icann.org] On Behalf Of Mary Wong Sent: Monday, April 24, 2017 8:00 AM To: Carlos Raul Gutierrez <crg(a)isoc-cr.org>; James M. Bladel <jbladel(a)godaddy.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: [council] LAST CALL: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique Dear all, As the Board and GAC will be meeting this Thursday to discuss the GAC Copenhagen Communique, please provide any comments or suggestions on the current draft of the GNSO Council response as soon as possible and preferably no later than 1400 UTC tomorrow (Tuesday 25 April). We are suggesting this deadline as the Council leadership needs to finalize the letter to be sent to the Board the same day noting the gist of the Council’s response. For your convenience, the latest draft is attached. This contains the edits made by James and the suggestions from Paul (see thread below). Your comments on Issue 2 (IGO names and acronyms) and Issue 4 (two-letter codes) will be particularly welcome as those are the topics on which substantive language has either been provided or requires resolution. Thanks and cheers Mary From: Carlos Raul Gutierrez <crg(a)isoc-cr.org<mailto:crg@isoc-cr.org>> Date: Sunday, April 23, 2017 at 08:34 To: "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>>, GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [Ext] Re: [council] FOR REVIEW/COMMENTS: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique James, sorry for missing the call last Thursday. Here are my personal suggestions to the issues that a focused letter should raise to the board before their meeting with the GAC based on comments of the drafting team so far: 1. In the case of the Red Cross et. al., the Copenhagen mediation by a former Board member made a clear Board resolution possible! The GNSO council looks forward to a revision of the policy based on this resolution, as the international law basis for the Red Cross et.al[et.al]<https://urldefense.proofpoint.com/v2/url?u=http-3A__et.al&d=DwMFaQ&c=FmY1u3…>. can be considered rather homogeneous. 2. In the case to the IGOs, The GNSO’s IGO-INGO Curative Rights Policy Development Process Working Group is actively reviewing all comments received on its Initial Report, including the comment submitted by the GAC. It remains clear from the mediation efforts during the Copenhagen meeting, that there is still the expectation in the Council that the Boards owes the GNSO community a clear resolution to direct future efforts in an efficient way forward, as was the case with the Red Cross et.al[et.al]<https://urldefense.proofpoint.com/v2/url?u=http-3A__et.al&d=DwMFaQ&c=FmY1u3…>. 3. In the case of the delegation of 2-letter codes, some members of the Council will like to raise serious concerns to the Board, of the impact that bilateral case by case resolution with Governments could have on the principle of bottom-up policy development of ICANN. Instead of developing a consensus position that all GAC members have agreed with, the Consensus Advice mechanism found in the bylaws is being circumvented to order the ICANN Board to negotiate with, and presumably reach agreement on, each government’s individual demands. This should not be considered proper “Consensus Advice”, but could rather be considered an attempt to circumvent the very clear threshold for the GAC to issue “Consensus Advice”. 4. In the case of the Mitigation of the DNS abuse, the GNSO Council refers to its input to the Board regarding the GAC’s Hyderabad Communique on this topic, and reiterates the concerns it stated in that response: https://gnso.icann.org/en/drafts/review-gac-communique-15dec16-en.pdf[gnso.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>. I hope it helps. Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA On Fri, Apr 21, 2017 at 2:04 PM, James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> wrote: Councilors – Please see attached for a revised version of this comment document. Note that due to a configuration error, I appear as both “James Bladel” and “Microsoft User”. I’ve attempted to clarify existing comments, but I believe we still have some work to do in item #2 (IGO Protections). I’m good with the other elements of the comment. As we are attempting to hit a short deadline, please review and provide your comments as soon as possible. I will then work with Staff to (a) restructure this document in the form of a letter that can be sent to the Board and (b) prepare a new formal motion for consideration at or before our next meeting. Thank you, J. From: <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Date: Friday, April 21, 2017 at 10:18 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] FOR REVIEW/COMMENTS: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique Dear Councilors, As discussed on the Council call yesterday, please find attached the current draft of a possible GNSO Council response to the gTLD policy issues raised in the GAC’s Copenhagen Communique. Staff had taken the liberty, when assisting the group of Council volunteers on this effort, of inserting certain comments and suggestions that are also reflected in the document. Please review the document and send your comments and suggestions to this mailing list. As noted on the Council call, the Board’s call with the GAC on the Communique is scheduled for 27 April, so it will be ideal if the Council chairs are in a position to send a note generally highlighting the Council’s views before that date, with a view toward formal Council adoption of the final text at the Council’s next meeting in mid-May. Thanks and cheers Mary _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l…>

1 0

Re: [council] FW: CSC Update April 2017
by Nathalie Peregrine 24 Apr '17

24 Apr '17

Dear James, James has been added as authorized sender to the GNSO Council list. Thank you for bringing this to our attention, Kind regards Nathalie From: <council-bounces(a)gnso.icann.org> on behalf of James Bladel <jbladel(a)godaddy.com> Date: Monday, April 24, 2017 at 9:57 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FW: CSC Update April 2017 Councilors – Apologies, but I thought this message from James was posted to the main GNSO Council mailing list. Here it is again, for your review. Staff – please grant James the ability to post to this list for the duration of his term as CSC Liaison? Thank you, J. From: James Gannon <james(a)cyberinvasion.net> Date: Monday, April 17, 2017 at 2:26 To: GNSO Council List <council(a)gnso.icann.org> Cc: "James M. Bladel" <jbladel(a)godaddy.com> Subject: CSC Update April 2017 Dear Councilors, Please find attached an update from myself as the Non-RySG liaison to the CSC on our progress to date. Please reach out if you have any questions or queries and I look forward to seeing you all at ICANN 59. -James Gannon

1 0

LAST CALL: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique
by Mary Wong 24 Apr '17

24 Apr '17

Dear all, As the Board and GAC will be meeting this Thursday to discuss the GAC Copenhagen Communique, please provide any comments or suggestions on the current draft of the GNSO Council response as soon as possible and preferably no later than 1400 UTC tomorrow (Tuesday 25 April). We are suggesting this deadline as the Council leadership needs to finalize the letter to be sent to the Board the same day noting the gist of the Council’s response. For your convenience, the latest draft is attached. This contains the edits made by James and the suggestions from Paul (see thread below). Your comments on Issue 2 (IGO names and acronyms) and Issue 4 (two-letter codes) will be particularly welcome as those are the topics on which substantive language has either been provided or requires resolution. Thanks and cheers Mary From: Carlos Raul Gutierrez <crg(a)isoc-cr.org> Date: Sunday, April 23, 2017 at 08:34 To: "James M. Bladel" <jbladel(a)godaddy.com> Cc: Mary Wong <mary.wong(a)icann.org>, GNSO Council List <council(a)gnso.icann.org> Subject: [Ext] Re: [council] FOR REVIEW/COMMENTS: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique James, sorry for missing the call last Thursday. Here are my personal suggestions to the issues that a focused letter should raise to the board before their meeting with the GAC based on comments of the drafting team so far: 1. In the case of the Red Cross et. al., the Copenhagen mediation by a former Board member made a clear Board resolution possible! The GNSO council looks forward to a revision of the policy based on this resolution, as the international law basis for the Red Cross et.al[et.al]<https://urldefense.proofpoint.com/v2/url?u=http-3A__et.al&d=DwMFaQ&c=FmY1u3…>. can be considered rather homogeneous. 2. In the case to the IGOs, The GNSO’s IGO-INGO Curative Rights Policy Development Process Working Group is actively reviewing all comments received on its Initial Report, including the comment submitted by the GAC. It remains clear from the mediation efforts during the Copenhagen meeting, that there is still the expectation in the Council that the Boards owes the GNSO community a clear resolution to direct future efforts in an efficient way forward, as was the case with the Red Cross et.al[et.al]<https://urldefense.proofpoint.com/v2/url?u=http-3A__et.al&d=DwMFaQ&c=FmY1u3…>. 3. In the case of the delegation of 2-letter codes, some members of the Council will like to raise serious concerns to the Board, of the impact that bilateral case by case resolution with Governments could have on the principle of bottom-up policy development of ICANN. Instead of developing a consensus position that all GAC members have agreed with, the Consensus Advice mechanism found in the bylaws is being circumvented to order the ICANN Board to negotiate with, and presumably reach agreement on, each government’s individual demands. This should not be considered proper “Consensus Advice”, but could rather be considered an attempt to circumvent the very clear threshold for the GAC to issue “Consensus Advice”. 4. In the case of the Mitigation of the DNS abuse, the GNSO Council refers to its input to the Board regarding the GAC’s Hyderabad Communique on this topic, and reiterates the concerns it stated in that response: https://gnso.icann.org/en/drafts/review-gac-communique-15dec16-en.pdf[gnso.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>. I hope it helps. Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA On Fri, Apr 21, 2017 at 2:04 PM, James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> wrote: Councilors – Please see attached for a revised version of this comment document. Note that due to a configuration error, I appear as both “James Bladel” and “Microsoft User”. I’ve attempted to clarify existing comments, but I believe we still have some work to do in item #2 (IGO Protections). I’m good with the other elements of the comment. As we are attempting to hit a short deadline, please review and provide your comments as soon as possible. I will then work with Staff to (a) restructure this document in the form of a letter that can be sent to the Board and (b) prepare a new formal motion for consideration at or before our next meeting. Thank you, J. From: <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Date: Friday, April 21, 2017 at 10:18 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] FOR REVIEW/COMMENTS: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique Dear Councilors, As discussed on the Council call yesterday, please find attached the current draft of a possible GNSO Council response to the gTLD policy issues raised in the GAC’s Copenhagen Communique. Staff had taken the liberty, when assisting the group of Council volunteers on this effort, of inserting certain comments and suggestions that are also reflected in the document. Please review the document and send your comments and suggestions to this mailing list. As noted on the Council call, the Board’s call with the GAC on the Communique is scheduled for 27 April, so it will be ideal if the Council chairs are in a position to send a note generally highlighting the Council’s views before that date, with a view toward formal Council adoption of the final text at the Council’s next meeting in mid-May. Thanks and cheers Mary _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council

3 2

FW: [Soac-infoalert] CSC Report performance PTI March 2017
by Marika Konings 24 Apr '17

24 Apr '17

For your information. Best regards, Marika From: <soac-infoalert-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Friday, April 21, 2017 at 13:03 To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> Cc: "ICANN-CSC(a)icann.org" <ICANN-CSC(a)icann.org> Subject: [Soac-infoalert] CSC Report performance PTI March 2017 Dear all, On behalf of the chair of the CSC (Byron Holland), please find included his monthly message to the community and the latest CSC report on the PTI performance march 2017 Kind regards, Bart Boswinkel 21 April 2017 Dear Community Members, As chair of the Customer Standing Committee I am pleased to provide you with our monthly report on the performance of Public Technical Identifiers (PTI) over March 2017. You will see that the CSC has concluded that, overall, PTI’s performance in March 2017 was “Satisfactory”, in that they met the service level agreement. The CSC is aware of some minor issues. The single missed service level is subject to a CSC recommendation and PTI will be investigating the issue further and reporting back to the CSC. In addition, PTI reported that it discovered two change types (revocations and root server changes) that had been underreported in previous monthly reports. The CSC found the explanation to be satisfactory. The CSC notes that these change types are infrequent manual work items (category v in terms of the agreed SLE) and for which performance metrics have not been established. The CSC discussed how to deal with this on a going forward basis. In summary: on the evidence to date, the CSC has not identified a persistent problem and no further action is needed. The CSC was informed that PTI has received no complaints. The PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports/201702[iana.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_performan…>. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce . The CSC was formed effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found athttps://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Any comments on our reporting to you would be welcomed. Kind regards, Byron Holland Chair CSC

1 0

FOR REVIEW/COMMENTS: Draft GNSO Council response on gTLD policy issues in the GAC Copenhagen Communique
by Mary Wong 23 Apr '17

23 Apr '17

Dear Councilors, As discussed on the Council call yesterday, please find attached the current draft of a possible GNSO Council response to the gTLD policy issues raised in the GAC’s Copenhagen Communique. Staff had taken the liberty, when assisting the group of Council volunteers on this effort, of inserting certain comments and suggestions that are also reflected in the document. Please review the document and send your comments and suggestions to this mailing list. As noted on the Council call, the Board’s call with the GAC on the Communique is scheduled for 27 April, so it will be ideal if the Council chairs are in a position to send a note generally highlighting the Council’s views before that date, with a view toward formal Council adoption of the final text at the Council’s next meeting in mid-May. Thanks and cheers Mary

4 3