February 2018 - Ccnso-council

FW: [soac-chairs] Input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT)
by Katrina Sataki Feb. 16, 2018

Feb. 16, 2018

From: Katrina Sataki [mailto:katrina@nic.lv] Sent: Tuesday, February 13, 2018 4:40 PM To: 'ccnso-council(a)icann.org' <ccnso-council(a)icann.org> Subject: FW: [soac-chairs] Input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT) FYI From: soac-chairs [mailto:soac-chairs-bounces@icann.org] On Behalf Of Nathalie Peregrine Sent: Tuesday, February 06, 2018 11:00 PM To: soac-chairs(a)icann.org <mailto:soac-chairs@icann.org> Cc: denisemichel(a)fb.com <mailto:denisemichel@fb.com> ; eosterweil(a)verisign.com <mailto:eosterweil@verisign.com> ; gnso-chairs(a)icann.org <mailto:gnso-chairs@icann.org> ; Board Ops Team <board-ops-team(a)icann.org <mailto:board-ops-team@icann.org> >; ssr2-review(a)icann.org <mailto:ssr2-review@icann.org> Subject: [soac-chairs] Input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT) Dear SO/AC Chairs, On behalf of the GNSO Council Leadership, please find attached the input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT). This will be posted shortly on the GNSO website Correspondence page. <https://gnso.icann.org/en/council/correspondence> Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org 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

I&J webcast
by Byron Holland Feb. 15, 2018

Feb. 15, 2018

Dear Colleagues, As per our discussion earlier today, the I & J conference will be livestreamed. It will be Livestreamed at https://www.youtube.com/channel/UCHA9d7SlPimYNZ-S5Ijvjqg More information can be found here: https://conference.internetjurisdiction.net/ Best regards, Byron

1 0

SAVE THE DATE: ccNSO Cocktail in San Juan, PR
by Kimberly Carlson Feb. 15, 2018

Feb. 15, 2018

[cid:image001.jpg@01D3A637.D0E9ED40]

1 0

REMINDER Re: Assessment duration/shape ccNSO Members Meetings: we seek your input
by Joke Braeken Feb. 15, 2018

Feb. 15, 2018

Dear all, This is a reminder that the ccNSO Meeting Strategy Review Working Group is seeking your input: The review is to assess the duration and shape of the ccNSO Members Meetings. It might lead to recommendations to change how ccNSO Members Meetings work, and your input is particularly valuable in shaping future ccNSO Members Meetings. How to provide your feedback? Via the online response form: https://www.surveymonkey.de/r/ccNSOmeetingstratreview[surveymonkey.de]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.de_r_…> (Estimated time for completion is 3 minutes) The survey will be open until Monday, 26 February 2018, noon UTC. Next Steps An initial report with proposed recommendations by the ccNSO Meeting Strategy Review Working Group will be made available prior to ICANN61. A further session to consult the ccTLD community will be held on Tuesday 13 March 2018 at the ccNSO Members Meeting[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> in San Juan (13:30-15:00). Where needed, the initial recommendations by the Working Group will be adjusted, and submitted for approval to the ccNSO Council, after ICANN61. Background * Background paper, about the ccNSO Meeting Strategy Review, the ICANN meeting strategy, and the ccNSO meeting distribution at ICANN meetings: https://community.icann.org/display/ccnsowkspc/ccNSO+Meeting+Strategy+Worki…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> * Wiki: https://community.icann.org/display/ccnsowkspc/ccNSO+Meeting+Strategy+Worki…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> On behalf of the ccNSO Meeting Strategy Review Working Group, thank you. 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[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=Dw…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso…> http://ccnso.icann.org[ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGa…>

1 0

NOTES ccNSO Council meeting Thu, 15 febr 2018
by Joke Braeken Feb. 15, 2018

Feb. 15, 2018

Dear all, Please find below the informal notes as taken during today’s ccNSO Council meeting (15 February 2018) Best regards, Joke Braeken 1) Welcome and Apologies we are not quorate yet. Meeting will start nonetheless. Remains to be seen if decisions need to be postponed. on audio only: Souleymane, Nigel, Barrack 2) Minutes and Actions minutes circulated on Friday. Deadline for review: end of this week. Not all action items completed yet. 3) Overview inter-meeting Council decisions - statement submitted on 02/02/18: draft Operating Standards - doc sent to NomCom with requirements for NomCom appointments - additional members appointed to PDP-ret and SOPC 4) Update & Discussion progress Work Track 5 Subsequent procedures (country and territory names Written update provided by Annebeth. Council sent its expectations to the WG. Response from the GNSO. Please review in prep for our meeting in San Juan. Hard to keep up with the pace. 5) ccNSO Travel Funding 5.1 Progress Guideline: ccNSO travel funding GRC decided the guideline is ready to be sent to the council. After council consultation, it will be sent to the community for review. 5.2 Number of ccNSO travel slots FY 19 Budget ccNSO submitted comments to the budget last year (17 slots for FY18). Draft budget FY19 mentions again 17 slots. is the number of slots adequate?As part of the general budget cuts, Tech Day participants will no longer be funded by GSE, was funding Eberhard to date. Expected is that the chair of the Tech WG is to be funded by the ccNSO in the future.Travel fund Commiitee members mentioned that there is a need for more slots. Nigel prefers to see funding for all ccNSO council members for all icann meetings. Suggestion to reduce the number of council members to 2 per region. Byron: we are covered as councillors. Who else do we think is important? We committed to a budget within ICANN (voluntary financial contributions), but do not manage to keep up to our committment. This reflects on this community. Travel funding is a direct expense. Are councillors denied funding? is this an actual issue, or a hypothetical one? yes, one instance where a council member requested funding but was not granted. 6) GDPR implications secretariat activities Implications of the GDPR on the calls for volunteers issued by the ccNSO Secretariat: we collect and process personal data. TLD-OPS: lots of personal data is collected there. New process: 1. secretariat to send out call for volunteers 2. volunteer approached: needs to provide consent. without explicit consent, the candidate cannot join/become a member. 7) Study Group Emoji: Adoption draft Terms of Reference ICANN61: Risks linked to the use of emoji in domain names will be addressed both at Tech Day and at the ccNSO Members Meeting (business/policy point of view) 8) Update SSR2 SO/AC leaders recently sent a letter to the review team. More communications are on the way (e.g. to Board, to the Board OEC) 9) Adoption revised Guideline: ccNSO Council Elections We are not quorate, so no decisions can be made. Guideline was put on hold. Discussions started with NomCom: placeholder, in case we need to remove a councillor appointed by NomCom. Decisions to be taken online, on the mailing list 10) Special Elections European Region Nigel will step down after the Panama meeting. 3 possible election scenarios. Assumption: we need to have a Q&A at one of the ICANN-meetings. - San Juan: not enough time to go through the whole process - Panama: voting in July. High holiday season in Europe - Barcelona: Q&A together with regular elections In August NomCom will appoint 2 council members To be discussed at a later occasion. 11) Approval updated membership application form References to ICANN bylaws and terminology adjusted. Please let us know quickly if there are any issues. Decision to be taken on the mailing list. 12) PDP Retirement next meeting postponed due to participation of members and staff at APTLD. One more meeting prior to San Juan. 13) CSC, RZERC and ECA related updates 13.1 CSC update (Byron) next meeting later today. Most recent PTI report received. Clean report, no issues from day to day operations point of view. Remedial action procedure process: CSC involved, PTI staff involved as well. ICANN legal had some comments, so the procedure is not nailed down yet. 13.2 RZERC update (placeholder) agreed on relevant procedural documents. Dormant at the moment. Concerns that some do not see this as a valuable addition to the general ICANN structure. Only structure not clearly described in the bylaws. 13.3 Empowered Community Administration update (placeholder) Rejection Action Guideline for review by council. SOPC is drafting feedback to the draft ICANN FY19 Operating Plan and Budget 13.4 CSC Charter review (Abdalla) CSC review Team will join the CSC call on initial discussion on initial draft, which will be published in time for ICANN61. Report includes amendments to the CSC charter. issue: 2 concurrent reviews: - CSC effectiveness review - IANA functions review 14) ICANN 61 14.1 ccNSO Council meetings Sunday: prep meeting with lunch, and council workshop (priorities, roles and responsabilities to be discussed) Council meeting on Wednesday afternoon. Alejandra presenting the ccNSO Block Schedule for ICANN61. 14.2 ICANN61 ccNSO Meetings Agenda 14.3 Topics meeting with ICANN Board 14.4 Topics meeting ccNSO- GAC 14.5 Topics meeting ccNSO-GNSO Councils 15) Council Updates 15.1 Chair Update 15.2 Vice-Chair Update 15.3 Councilors Update 15.4 Regional Organizations Update 15.5 Secretariat update - Margarita stepped down from ccNSO Meeting Strategy Review Team. no replacement needed 16) WG update 16.1 GRC update (Katrina) Guideline soon to be sent to the community for review. 2 webinars in 2 weeks to explain the Guideline Rejection Actions. Travel funding guideline, ccNSO internal review. Alejandra and Eduardo have stopped down from the GRC. currently 2 regions not represented on GRC: N-Am, AP 16.2 CCWG Auction Proceeds (Ching) update in written form 16.3 CCWG Internet Governance (Young Eum) update in written form 16.4 CCWG Accountability WS 2 update in written form 16.5 ccNSO Meeting Strategy review update in written form 17) Liaison Updates 17.1 GNSO Update 17.2 ALAC update 18) Next meeting 14 March - face to face, San Juan 19) AOB - Stephen raised the issue that we need to implement changes on the guideline for the board elections. informal taskforce on what would work better (e.g. candidates, election manager, few council members) what worked, where are changes needed? Report by Nomination Manager is a starting point for the changes needed. Katrina suggested to forward this to the GRC instead. Several options for due diligence background checks. internet and jurisdiction conference to be held in Ottawa in 2 weeks. spearheaded by Bertrand de la Chapelle. (topics: Domain names, trusted modifiers, trusted regime in the domain space with regards to notifications) Next year the 3rd and final conference will be held in Berlin next year. no binding activity, but topic of interest. By invite only. Output is publicly available. Remote Participation? Byron will inform council. 20) Closure Thank you all. Online decisions needed. 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

Fwd: Programme WG Update for the Council
by Alejandra Reynoso Feb. 15, 2018

Feb. 15, 2018

Dear All Please find attached the documents presented at the Council Call. Best regards, Alejandra *--* *Registro de Dominios .gt* 18 Ave. 11-42. Z.15. V.H.III. +502.23688302, +502.23688564 y +502.23688565

1 0

FY18 Q2 Stakeholder Update
by Joke Braeken Feb. 15, 2018

Feb. 15, 2018

Dear all, ICANN published its FY18 Q2 Stakeholder Update for the quarter ending 31 December 2017. Göran Marby, President and CEO, and Cherine Chalaby, Chairman of the Board have prepared an executive summary highlighting key updates from the report. Read the report and the executive summary here: https://www.icann.org/quarterlyreports . You are invited to attend a question and answer (Q&A) call on 22 February at 17:00 Coordinated Universal Time (UTC) to ask any questions about this report. To join the call, please register here: http://survey.clicktools.com/app/survey/response.jsp . If you are unable to access the form, please register by sending an email to icann.communications(a)icann.org<mailto:icann.communications@icann.org> with your full name and email address. The call will be recorded and open for all to attend, with simultaneous interpretation in Arabic, Chinese, English, French, Portuguese, Russian, and Spanish. Recordings in all languages will be posted on ICANN's Quarterly Reports page: https://www.icann.org/quarterlyreports 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 - Upcoming SLA Monitoring System API
by Joke Braeken Feb. 14, 2018

Feb. 14, 2018

Dear all, The ccNSO Secretariat was approached by ICANN’s Global Domains Division Technical Services and Registry Services Teams, with the request to share the message included below to the ccTLD community. = = = Dear Colleague, This is to notify you of a new ICANN Monitoring System API (MoSAPI) for generic and country code top-level domain (gTLD/ccTLD) registries planned for launch during the first half of 2018. You may consider using this service to monitor the health of your ccTLD DNS service in near real-time. The measurements are based on DNS service availability as defined in Specification 10 of the gTLD Base Registry Agreement<https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…> (for example, the DNS service is considered to be up when all the IP addresses of at least two of the name servers for a given TLD are considered to be up). We recognize the gTLD Base Registry Agreement does not apply to ccTLDs, but as a service to the community, the monitoring data of the ccTLD is available to the ccTLD operator. The MoSAPI will include the ability to: · Monitor the state of a TLD. · Monitor the alarm status of a service. · Monitor the availability of a service. · Monitor the state of a particular incident. · Monitor the false positive flag of an incident. · Query a list of incidents for a service. · Query the list of measurements for an incident. · Query the details of a particular measurement. · Retrieve the list of IP addresses used in the probe node network. Beta testing of the new MoSAPI platform began 13 January 2018 with pilot users. Participation in the beta program is open to all registries. The technical specification of the system is here<https://www.icann.org/en/system/files/files/mosapi-pilot-28nov17-en.pdf>. The beta program is intended for users to test the new interface. Feedback from the beta program will be used to address issues uncovered during testing prior to the production version launch. To request access for the MoSAPI beta program, please contact the ICANN Global Support Center using the contact details below. Please state the ccTLD for which you are requesting access. ICANN will contact the administrative and technical contacts of the ccTLD as listed in the IANA Root Database to validate the information and provide access. More information about MoSAPI is available by viewing this presentation and audio recording from the ICANN60 session here<https://schedule.icann.org/event/CbFm/icann-gdd-monitoring-system-api-mosap…>. If you have questions or would like to provide beta testing feedback, please contact ICANN’s Global Support Center by email<mailto:globalsupport@icann.org?subject=Probe%20Node%20IP%20Addresses> or at one of the phone numbers found here<https://www.icann.org/resources/pages/customer-support-2015-06-22-en>. Best regards, GDD Technical Services and Registry Services Teams Global Domains Division ICANN = = = 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 Fellowship Program Community Consultation: invitation to answer the survey
by Joke Braeken Feb. 14, 2018

Feb. 14, 2018

Dear council members, Based on recent triage recommendation 08-2018, you are kindly invited to participate in the ICANN Fellowship Program Community Consultation. The Public Responsibility Support department within ICANN approached all SO/AC leaders. ICANN staff has launched a community-wide consultation on the Fellowship Program to help inform its future direction. ICANN staff will be available to speak with community groups about the current Fellowship Program and the questionnaire at ICANN61 or remotely. How to participate? Please answer the survey questions included in the attached PDF (page 5&6). Please send questionnaire responses and any questions to fellowshipconsultation(a)icann.org Deadline: 30 March 2018 Thank you. 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

proposed triage recommendation [10 - 2018]: Call for Experts to Study the Application of Root Zone Label Generation Rules
by Joke Braeken Feb. 14, 2018

Feb. 14, 2018

Dear ccNSO council members, Please find below the proposed triage recommendation [10 - 2018]. Kindly provide me with your input by the end of Friday, 16 February 2018, 23:59 UTC, in case you do not agree with the proposed recommendations. Thank you. Topic: 10-2018: Call for Experts to Study the Application of Root Zone Label Generation Rules Summary of request: Following the letter from the Chair of ICANN Board to the SO/AC chairs on 29 January 2018, posted at https://www.icann.org/en/system/files/correspondence/chalaby-to-so-ac-chair…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, ICANN org recently released an announcement at https://www.icann.org/news/announcement-2018-02-08-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> for nominations of technical experts from GNSO (2), ccNSO (2), SSAC (2) and ALAC (2) to work on recommendations for application of Root Zone LGR Date received: 9 February 2018 Last day for comments/input/response, if any: 28 February 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media channels Expertise needed, if any: IDN, root zone label generation rules Date of submission to Triage Committee: 9 February 2018 Recommendation received by Triage Committee: 14 February 2018 Date of submission to Council: 14 February 2018 Deadline Council decision: 16 February 2018, 23:59 UTC Impact on ccNSO/ccTLDs: low 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