May 2017 - Ccnso-council - lists.icann.org

ICANN59 ccNSO Members Meeting: updated agenda and session summaries now available
by Joke Braeken May 19, 2017

May 19, 2017

Dear all, Regarding the upcoming ICANN59 ccNSO Members Meeting, the ccNSO Meetings Programme WG is pleased to inform you that the following information is now available online: · an updated version of the ccNSO Members Meeting agenda: https://ccnso.icann.org/meetings/johannesburg59/agenda.htm · a summary with main highlights of the ccNSO Members Meeting sessions: https://ccnso.icann.org/meetings/johannesburg59/session-summaries.htm The presentation slides will be published during or shortly after the meeting on https://schedule.icann.org/, and on https://ccnso.icann.org/meetings/johannesburg59/presentations.htm LINKS: · Full ICANN59 schedule: https://schedule.icann.org/ available as of 5 June 2017 · ICANN59 meeting site: https://meetings.icann.org/en/johannesburg59 (including info regarding transportation, venue map etc.) · ICANN59 Mobile App: meetingapp.icann.org · Recent webinar on ICANN59 logistics (AC recording and presentation): https://www.icann.org/news/announcement-2-2017-05-11-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Notification of Board Seat 11 Nomination
by Bart Boswinkel May 18, 2017

May 18, 2017

Dear Empowered Community Administration, cc. ICANN Secretary and Decisional Participants On behalf of the ccNSO Chair, Katrina Sataki, please find included a notification concerning the nomination of Chris Disspain for Board Seat 11 per ICANN AGM 2017. Kind Regards, Bart Boswinkel

1 0

Draft Agenda for ICANN 59
by Alejandra Reynoso May 18, 2017

May 18, 2017

Dear All Attached are the updated documents shared today during our call. Please, take note that this is still in draft, so changes may occur. Best regards, Alejandra *Registro de Dominios .gt* -- Universidad del Valle de Guatemala. 18 Ave. 11-95. Z. 15. V.H. III. Edificio *J*. Oficina *204*. *Tels:* *+502.23688564 <+502%202368%208564>* y *+502.23688565 <+502%202368%208565>*

1 0

notes : ccNSO Council call Thursday 18 May (12 UTC)
by Joke Braeken May 18, 2017

May 18, 2017

Dear All, Please find below the notes taken during the council meeting from Thursday 18 May (12 UTC) Best regards, Joke Apologies: Peter Van Roste, Ben Fuller, Nigel Roberts (leaving early), Margarita Valdes, Abibu Ntahigiye NOTES 1. Welcome and apologies 2. Minutes and Actions Minutes from the previous meeting were published. Action items from the previous meeting: - draft to increase travel funding slots - CCWG IG questions - Letter to the Board - ALAC liaison: ALAC chair has no issues with the current situation. - table: items to be included in each council meeting - update wiki - GRC is working on an update of the council responsibilities guideline - issue report to be published for public comment. Will be done by next Wednesday 24 May 3. Overview inter-meeting council decisions - RDS/WHOIS review: letter sent to board - submission OPS Plan & Budget - Jordan appointed as co-chair CCWG Accountability - 2 calls for volunteers. to replace Mathieu Weill on CCWG-Accountability and the CCWG new gTLD Auction Proceeds - discussion next steps EPSRP - draft FAQ to GAC 4. ccNSO as decisional participant update 4.1. Approval Action process ICANN Board adopts an approval action, this kicks off the entire process. They publish it then for public comment (40 days). When we learn about this event, the secretariat will update website and wiki. The council informs the community. Once the 40-day period is over, ICANN staff analyses the public comments received. The Board then decides on the approval action, and submit it to the EC Administration. The ECA can then ask the board to organise a community telco (optional step), or they can direct ICANN to organise a community forum (as F2F at ICANN meeting, or telco). Anyone can ask questions during the community forum, and at the end of the ICANN-meeting a 21 day period starts. The ccNSO council then has to decide to either support this action, reject it, or abstain. Problem: the 21 day period is in the bylaws, we cannot change that. However, 21 days is too short, but according to the rules of the ccNSO, any decision of the council may be questioned by the community. If 10% of the members request so, there will be a member vote (currently 17 members). we then need to organise a voting, and at least 50% of the members need to vote. This takes at least 14 days. If we do not come up with a decision, we will neither support nor reject the action. Therefor the GRC proposes 2 alternatives to the voting (included in the draft guideline): 1) we listen closely to the community and then take a decision (preferred way forward) 2) we take a decision early in the process, and allow members to object, and then have time only for 1 round of voting. Likely we will not get 50% of the votes, so it means we will be neutral, and do not take a decision. Community Forum will be held at 8 am on Tuesday, in Johannesburg (ICANN59). Where the guidelines explicitly say the rules do not apply, there is a mandatory consultation. In the other case it is expected to have a consultaton, but not mandatory. Byron: Challenges regarding the authority to schedule the community forum. Will the EC have the voice that it needs? Stephen: meeting format is not adjusted to reality, now that the new bylaws are in place. Considerable further discussion needed with ICANN regarding the scheduling. Most likely we have community forums at 2 out of 3 meetings, and the meeting format is not adjusted to that. 4.2. ECA update Correspondence form ALAC and GNSO nominating their board members. Will be sent to John Jeffreys later today. Similar document expected regarding ccNSO Board seat 11. Will be sent out after this call. 5. Council response to SO/AC accountability public comment WS2 We have received a SO/AC accountability report. The GRC looked into this, and has not found any issues. The GRC suggest to support the direction of travel expressed in the document by the CCWG. Byron: recommendations to continue are 3-fold. They question the practical ability to continue. Accountability roundtable might be a significant challenge to put into operation. Concerned that they already mention now that they will be challenged. Even the CCWG has a sense that the conclusion is foregone already. We should flag it as a concern. 6. CSC charter review Small team needed: draft team that prepares the parameters for the review. . Max 2 or 3 from our side. We have reached out to Martin Boyle and Maarten Simon. Maarten cannot join unfortunately, and we are waiting feedback from Martin B. Byron: very important that we as a community get what we need from the CSC. Byron encourages people to participate in this review. Important work, but not a huge amount. Another call for volunteers will be sent out once the parameters for the review are in place. 7. EPSRP update Thank you to Hiro and Wafa to be on the working team. Strategy was discussed, on how to ensure we come up with a mutually acceptable solution with SSAC. They expect to have 2 people as well in the team. We almost finalised the draft description of work. 8. PDP Progress Call for volunteers for this WG was closed. List is being displayed in the AdobeConnect room. Draft resolution Move? Alejandra Seconder? Byron Against? none Abstentions? none All in favour 9. Extension CCWG Accountability mandate 10. The CCWG-Accountability WS2 Co-Chairs would welcome approval or support of the ccNSO to extend the mandate of the CCWG prior to the finalization of the ICANN FY18 budget and remain at the disposal of the ccNSO to provide any additional information or presentations. We have issued a call for volunteers to replace Mathieu on the CCWG. We have received no response to that call for volunteers. This will be one of the topics for discussion in Johannesburg. (Accountability session, ICANN59) Broader problem is the lack of qualified volunteers. ATRT3 review: we are asked to nominate 1 to 7 candidates. Currently there is only 1 person that receives endorsement from the ccNSO (Demi Getschko) We also need to replace Mathieu on the CCWG new gTLD auction proceeds. Ching is co-chair, and then we have Peter Vergote (.be). Ching his term ends at ICANN60. Ching: more comprehensive review will start now on the mechanism and the scope of the funds. how to govern the use of those funds? (200 plus million available to the benefit of the community) at ICANN59: decision to be taken on how to proceed regarding the CCWG accountability mandate, and how to deal with the issue of lack of volunteers. 11. ICANN59 meeting agenda ==> Block schedule with ccNSO relevant sessions. Overview of the current draft agenda. Main highlights: split of the WG updates into cross-community updates, and ccNSO WG updates No RO update. No legal session, no marketing session. The ccNSO as decisional participant is a main topic in this ccNSO members meeting Call for volunteers ccTLD news: 3 responses (.rs, .eu, .cn) ==> Cross-community sessions: 3 hosted by the ccNSO. interest from other SO/ACs New: the other SO/ACs want to be involved in the planning of the cross-community topics. Interest from the GNSO and GAC regarding GDPR, interest mainly from GAC regarding who sets ICANN’s priorities. Talks with Jordan, Peter and Giovanni are ongoing regarding the planning of these sessions. One of the ccNSO proposals for cross-community topics for ICANN59 was entitled “Rejection Action Petitions: Is the EC able to Exercise its Rights under the ICANN Bylaws?” Katrina informed the ICANN59 planning team that since there seemed to be little interest from other communities on this topic, the ccNSO preferred to withdraw this proposal. Nonetheless, the ccNSO believes this is the topic of the utmost importance. Therefor it has been decided to limit the scope to the ccNSO only, and run it as a ccNSO internal session during the ccNSO Members Meeting. Anyone interested to see how the ccNSO intends to deal with Rejection petitions and related issues is welcome to attend. Currently the session is tentatively scheduled for Wednesday, 28 June, block 2. ==> WG meetings scheduled for Monday. PDP WG will meet on Thursday. Joint session with GAC. Topics for discussion include: - update CWG-UCTN - update PDP 12. CSC and RZERC update 13. Council updates, RO, Secretariat None 14. WG update Thanks to Alejandra for executing a difficult task GRC: draft approval action guideline is currently work in progress. Needs to be adopted in Johannesburg latest. CCWG-AP The group looked into the initial response to the charter question. The actual working plan will be sent to different SO/ACs before the end of this week. Response to the Board letter has been submitted as well: thanking them for their guidance. Concerns regarding administration costs for running the funds. 15. Liaison updates 16. Next meetings - at ICANN59 (Thursday, block 1) - 20 July (12 UTC) - 21 September (12 UTC) 17. AOB Stephen expects to share a monthly written update with the council. Comments are welcome. 18. Closure Thank you. Please continue to provide feedback and input. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Agenda and Draft resolutions an additional background material
by Bart Boswinkel May 18, 2017

May 18, 2017

Dear all, Please find included the agenda and draft resolution(s) In addtion latest background material: · Wrtitten updates and · draft nomination letter to ECA to designate Chris Disspain as Board member taking seat nr 11. Kind regads, Bart

2 1

Call for Council volunteer(s) to participate in CSC review preparatory group.
by Bart Boswinkel May 17, 2017

May 17, 2017

Dear all, As you will recall the CSC charter will need to be reviewed by the RySG and ccNSO one year after the CSC has become operational, so starting at or around 1 October 2017. In Copenhagen, the ccNSO Council and RySg agreed to form a small light weight working party that would prepare the Charter review, the agreed timeline is: May- June 2017: draft terms/parameters review (ccNSO and RySG team). - mid – June 2017: Propose terms of reference review to RySG and ccNSO - June agreement/adoption terms of review at ICANN 59. - October 2017 kick-off review - Annual meeting (ICANN 60). Public consultation - Preparation final report, include proposed changes charter - Adoption Final report RySG and ccNSO January/February 2018 - Submit updated charter to GNSO and ccNSO Council for adoption by ICANN 61 The preparatory team is supposed to be very small, preferably 2-3 persons from the ccNSO and 2-3 from RySG. In to prepare the review properly one or two Councilors are invited to participate as well as one person who was involved in the discussions that led to the creation of the CSC. Could you be so kind to consider whether you would be available and willing to participate in the preparatory group? It is expected that it will take 1-2 hours per week for the upcoming weeks leading up to Johannesburg meeting. FYI: Maarten Simon and Martin Boyle have also been asked, as former members/ people close to the initial discussions on the CSC and development of its charter. Please note thatthis small group is about defining the terms of reference for the review it will NOT lead the actual review, which will be conducted by another group, following a call for volunteers to the community. Kind regards, Bart Agreed principles between ccNSO and RySG to date: - Small review team (3 members RySG, 3 members ccNSO) - Include appointed CSC members as advisors - Check with full CSC potential areas of improvement - Light weight approach

1 0

Release of Country and Territory Names within the .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS TLDs
by Joke Braeken May 17, 2017

May 17, 2017

Dear all, Five (5) Registry Services Evaluation Policy https://www.icann.org/resources/pages/registries/rsep/policy-en (RSEP) requests were submitted by the registry operators listed below to allow the release of country and territory names for the below TLDs. In total, the requests concern six (6) new gTLDs. .pioneer, .fujitsu, .obi, .sharp, .toyota, .lexus Currently, the .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS Registry Agreements require country and territory names contained in specific internationally recognized lists to be withheld from registration or allocated to the registry operator at all levels. As required by the RSEP, ICANN has undertaken a preliminary determination on whether these RSEP proposals might raise significant competition, security or stability issues. ICANN's preliminary review (based on the information provided) did not identify any such issues. Following ICANN's preliminary determination that the proposals do not raise significant competition, security or stability issues, it was further determined that the change would require a material change to the respective Registry Agreements and that an amendment is needed in order to effect the change. The proposed amendments, which are being posted for comment, would allow the registration of country and territory names at all levels in .PIONEER, .FUJITSU, .OBI, .SHARP, .TOYOTA, and .LEXUS. It should be noted that Specification 13 has been granted for .PIONEER on 16 July 2015, .FUJITSU on 30 July 2015, .OBI on 25 September 2014, .SHARP on 03 September 2015, and .TOYOTA and .LEXUS on 23 April 2015. Read the announcement here: https://www.icann.org/public-comments/ctn-release-tlds-2017-05-08-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

public comments sought on the draft Framework of Interpretation for Human Rights
by Joke Braeken May 17, 2017

May 17, 2017

Dear all, A Public Comment seeks community input on the Cross Community Working Group on Enhancing ICANN Accountability Work Stream 2 (CCWG-Accountability, WS2) draft Framework of Interpretation for Human Rights. This draft was developed by the CCWG-Accountability as required by Annex 12 of the final report of the CCWG-Accountability, Work Stream 1. Current Status: The CCWG-Accountability reviewed this draft at its 25 April 2017 plenary meeting and approved its publication to gather public comments. Next Steps: Following the public comment period the inputs will be analysed by the CCWG-Accountability WS2 who will consider amending the Framework in light of the comments received and will publish a report on the results of the public consultation. If significant changes are required as a result of the public consultation the CCWG-Accountability WS2 may opt to have a second public consultation on the amended Framework. If there are no significant changes required, the CCWG-Accountability WS2 will forward the final Framework of Interpretation for Human Rights to its Chartering Organizations for approval and then to the ICANN Board for consideration and adoption. Close Date: 16 Jun 2017 23:59 UTC Read the announcement here: https://www.icann.org/news/announcement-2017-05-05-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

The Latin Script Community Forms the Generation Panel for Developing the Root Zone Label Generation Rules (LGR)
by Joke Braeken May 16, 2017

May 16, 2017

Dear all, ICANN announces the formation of the Generation Panel to develop root zone Label Generation Rules (LGR) for the Latin script. Following the Call for Generation Panels to Develop Root Zone Label Generation Rules (https://www.icann.org/news/announcement-2013-07-11-en ) the Latin script community has submitted to ICANN the Proposal for Generation Panel for Latin Script Label Generation Ruleset for the Root Zone. ICANN organization has reviewed the proposal including panel composition and scope, to ensure that requirements set forth in the LGR Procedure[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 772 KB], and in particular the criteria set forth in the Call for Generation Panels to Develop Root Zone Label Generation Rules[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>, are fulfilled. With composition and work plan approved, the Latin script Generation Panel will start its work on the label generation rules. According to the LGR Procedure[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 772 KB], the starting point of any Generation Panel's work is the Maximal Starting Repertoire (MSR), with its second version (MSR-2[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>) released on 27 April 2015. The full specification of Generation Panel's tasks can be found in theLGR Procedure[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 772 KB] in particular, Section B.3 "Variant Rule Generation Procedure". "I'd like to take this opportunity to reiterate our appreciation for the efforts of many communities towards developing their root zone LGR proposals," said Sarmad Hussain. "We still have more work to do including organizing script panels for Hebrew, Myanmar, Sinhala and Tibetan. I encourage interested parties to lend their skills in support of this effort. There are currently LGR efforts underway by Chinese, Cyrillic, Greek, Japanese, Korean, Latin and Neo-Brahmi communities. In addition, the Arabic, Armenian, Ethiopic, Georgian, Khmer, Lao and Thai script communities have finalized their root zone LGR proposals[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, of which the Arabic script proposal has been integrated in the first edition of the Root Zone LGR[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Learn more about how you can speak up for your language by visiting the Call for Generation Panels to Develop Root Zone Label Generation Rules[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>. For further information on the IDN Program at ICANN, please visit www.icann.org/idn[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_idn&d=Dw…>. To start a new Generation Panel or to get involved in an existing one, please email at IDNProgram(a)icann.org<mailto:IDNProgram@icann.org>. Read more here: https://www.icann.org/news/announcement-2017-05-15-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

ICANN FY16 Form 990 Announcement
by Joke Braeken May 16, 2017

May 16, 2017

Dear all, ICANN continues to provide accountability and transparency on its financial results with the publication of its US tax return ("Form 990"), which is available on the https://www.icann.org/resources/pages/governance/financials-en page. The Form 990 is the United States tax return for organizations exempt from income taxes under section 501(c) of the Internal Revenue Code. The Form 990 contains information and disclosures as required by the IRS on financial statements, funding sources, compensation practices, and much more. It is a useful source of information, which we invite the ICANN community to review and offer comments or questions as desired (controller(a)icann.org)<mailto:controller@icann.org)>. ICANN filed its Form 990 (https://www.icann.org/en/system/files/files/fy-2016-form-990-15mar17-en.pdf) for the fiscal year ending 30 June 2016 with the Internal Revenue Service on 12 May 2017 in compliance with the extended due date of 15 May 2017. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0