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

REMINDER - Call for nominations: Special ccNSO Council Elections | European region
by Joke Braeken June 8, 2018

June 8, 2018

Dear all, This is a reminder to the ccNSO Members from the European region: the ccNSO has recently opened a call for nominations, which closes Tuesday, 12 June 2018 (23.59 UTC). Further instructions can be found below. Nigel Roberts has indicated he will step down from the ccNSO Council after the ccNSO Council meeting in Panama City (ICANN62). In accordance with section 10.4(g) of the ICANN Bylaws, the ccNSO members in the European Region will need to select a candidate for the remainder of Nigel’s term (until March 2020). The person selected for the special council election will take the seat on the Council immediately after the selection. Read the announcement here: https://ccnso.icann.org/en/announcements/announcement-21may18-en Bylaw Article 10 – Section 10.4 (g) [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> states: “The ccNSO Council members selected by the ccNSO members from each Geographic Region (see Section 10.3(a)(i)) shall be selected through nomination, and if necessary election, by the ccNSO members within that Geographic Region. At least 90 days before the end of the regular term of any ccNSO-member-selected member of the ccNSO Council, or upon the occurrence of a vacancy in the seat of such a ccNSO Council member, the ccNSO Council shall establish a nomination and election schedule, which shall be sent to all ccNSO members within the Geographic Region and posted on the Website.” Eligibility requirements to be elected to the ccNSO Council A Councillor can be any individual nominated, seconded and selected as described in the ccNSO Council Election Guideline [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>. Individuals are selected in their personal capacity and serve the ccTLD community. Councillors do not represent the views and interests of their employers. Candidates need to be neither resident in the region nor a citizen of a country within the region in which they stand for election. How to nominate and second a candidate Timeline START nominations/secondments: Tuesday, 22 May 2018 (00.01 UTC) END nominations/secondments: Tuesday, 12 June 2018 (23.59 UTC) Who can nominate/second? According to section 10.4 (h) of the ICANN Bylaws, each ccNSO member from ICANN’s European region may nominate a person to serve on the ccNSO Council for the European region. The nominated person must need to be seconded by another ccNSO member from the European region. Candidates do not need to reside or be a citizen of a country in the region for which they stand. ccNSO members may self-nominate themselves but are not allowed to second their nomination. Self-nominations must be seconded by two ccNSO members from the region. Accepting nominations After closure of the nomination period, the Election Manager will ask the candidates that are nominated to accept their nomination. Self-nominations are understood to have accepted their nomination. The Election Manager will provide a list with the name(s) of the candidate(s) who have accepted their nomination. A record of who has nominated and seconded the candidate(s) is publicly available [forum.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__forum.icann.org_lists_c…> . Instructions Nominations and secondments should be sent by e-mail to the Election Manager at the following e-mail address: ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org> . Templates for nominating and seconding nominations are provided below. You are kindly invited to follow these instructions closely, and not to use alternative templates. Template for nominations: NOMINATION TO THE CCNSO COUNCIL 1. Your full name: 2. Your e-mail address: 3. Your ccTLD: 4. Your geographic region: 5. Full name of the person you nominate to the ccNSO council: 6. e-mail address of the person you nominate: Template for seconding nominations: SECONDING A NOMINATION TO THE CCNSO COUNCIL 1. Your full name: 2. Your e-mail address: 3. Your ccTLD: 4. Your geographic region: 5. Full name of the nominee you would like to second: Consult here [forum.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__forum.icann.org_lists_c…> the archive for nominations and secondments. Next steps If at the close of nominations period only one candidate has been nominated, seconded and accepted nomination the the nominated person shall be selected to serve on the ccNSO Council. Otherwise, an election shall to select the ccNSO Councillor from among the valid candidates. Only ccNSO members from the European Region may vote. Voting will be by secret ballot. Links * Archive for nominations and secondments [forum.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__forum.icann.org_lists_c…> * Relevant ccNSO guideline [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>: ccNSO Council Election Procedure * Timeline: https://ccnso.icann.org/workinggroups/timeline-special-council-elections-21… 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 3

call for volunteers: Rejection Action Petition Review Committee
by Joke Braeken June 1, 2018

June 1, 2018

Dear all, Following a discussion during the 24 May ccNSO Council call, I am hereby sending you a call for volunteers. We seek 2 councillors as members of the Rejection Action Petition Review Committee. If you are interested in this position, kindly send an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, latest on Tue, 5 June 2018 COB. Background During its 24 May meeting, the ccNSO council adopted the Guideline on Rejection Action Procedures. (https://community.icann.org/download/attachments/84219624/Item%204.1%2024%2… [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> ) The Rejection Action Petition Review Committee will evaluate any Rejection Action Petition received by the Rejection Action Petition Manager to ensure that it meets the requirements for a Rejection Action Petition as set forth in Annex D of the Bylaws[1] and advise the ccNSO Council accordingly. The Rejection Action Petition Manager and its alternate are ex-officio members of the Rejection Action Petition Review Committee. Thank you. 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] ICANN Bylaws, Annex D Section 2.2(c)(i)(A-B)

1 1

call for volunteers: Rejection Action Petition Manager + back-up
by Joke Braeken June 1, 2018

June 1, 2018

Dear all, Following a discussion during the 24 May ccNSO Council call, I am hereby sending you a call for volunteers for 2 councillors, one to serve as Rejection Action Petition Manager and one as Rejection Action Petition Manager back-up. If you are interested in this position, kindly send an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, latest on Tue, 5 June 2018 COB. Background During its 24 May meeting, the ccNSO council adopted the Guideline on Rejection Action Procedures. (https://community.icann.org/download/attachments/84219624/Item%204.1%2024%2… ) The timelines for rejection actions are very tight. To deal with this issue as best as possible, the GRC proposed that a limited number of Councillors (2) manage the Rejection Action process, in light of the critical role of the ccNSO Council in the process. A core role has been designed for the Rejection Action Petition Manager. To make sure that we do not create a single point of failure, a Rejection Action Petition Manager back-up is needed as well. According to the ICANN Bylaws<https://www.icann.org/resources/pages/bylaws-2016-02-16-en>, the ccNSO is one of the Decisional Participants of the Empowered Community (EC). The ccNSO, as decisional participant, shall act through its chair or another person as may be designated by the ccNSO. Stephen Deerhake (.as) as ccNSO appointed member of the EC Administration, and ccNSO Council chair Katrina Sataki cannot apply for the position of Rejection Action Petition Manager and back-up. 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

3 4

FW: [Ccnsosecretariat] RZERC report for the ccNSO Council
by Bart Boswinkel May 31, 2018

May 31, 2018

Dear all, Please find included an update from Peter Koch on latest RZERC On 24/05/18 00:31, "Ccnsosecretariat on behalf of Peter Koch" Dear ccNSO Council, please find attached my most recent report on RZERC and an addendum. Best regards, Peter ----------------------------------------------------------------------------- 2018-05-23, Peter Koch, DENIC (DE) ccNSO appointee to the Root Zone Evolution Review Committee (RZERC) <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rzerc&d=…> ----------------------------------------------------------------------------- The work of RZERC is made transparent by means of the website above and the publicly accessible mailing list archive at <http://mm.icann.org/pipermail/rzerc/>. ----------------------------------------------------------------------------- This is the first written report regarding RZERC in 2018. The committee had ended its initialization phase on 11 December 2017 and went dormant afterwards. On 22 May 2018, the committee held a teleconference with two main action items: o Discussion and comments of the Root Zone Management Evolution Study Following a recommendation in the ICG IANA Stewardship Proposal the ICANN OCTO (Office of the CTO) team has drafted a study (Details to be found in the PDF attached to <https://mm.icann.org/pipermail/rzerc/2018-April/000290.html>) "Root Zone Management Evolution Study" that is believed to be conducted by an outside contractor. RZERC was asked for comments, most likely because part of the genesis of RZERC's was the discontinuation of NTIA oversight. RZERC members preliminary assessed the request as informal, given that the current draft envisions any study results to be addressed by RZERC. RZERC will seek clarification with OCTO. Relevance for the ccNSO/ccTLDs: Given that the study is an open issue from the IANA Stewardship Transition, policy level attention is advised. The current scope of the study as well as requirements for recommendations need to be evaluated against both the letter and the spirit of the recommendation made by the ICG. A risk analysis and the prevention of unintended and/or unauthorized changes to content of the root zone and/or the root zone database are vital issues for all TLDs. o Board Resolution on KSK Rollover After the postponed initial rollover of the DNSSEC root zone key signing key (KSK), the current schedule aims at 11 October 2018 for the KSK roll. (Details at <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>) The revised schedule has been subject to outreach events and a public comment perios, a summary of the latter to be found at <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>. The ICANN Board noted that neither RSSAC, nor SSAC, nor RZERC had submitted contributions during the comment period and so, per Board Resolution on 13 May 2018 <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> asked all three committees to provide advices (mind the plural) per 10 August 2018. RZERC will deliberate on a response. Relevance for the ccNSO/ccTLDs: Any DNSSEC enabled DNS resolver failing to accept the new root KSK by the rollover date would cease to properly resolve any domain underneath the root, signed or unsigned. While this would be local to the user population behind those resolvers, TLD managers and anybody else running DNS services might be affected by confusion on the side of end users or other customers. Detailed discussion has been part of the planning process. It should be noted that most of the limited number of comments received during the public consultation were submitted by well known individuals from the tech/ops community. This gives no clear signal regarding the effectiveness of the outreach efforts. ----------------------------------------------------------------------------- Addendum outside the report: The RZM study might need a bit more attention by teh ccTLD community, so if the schedule allows for an RZERC report, I'd elaborate a bit on this, or maybe even consult with the community via email beforehand. For the KSK roll, it appears the Board is seeking utmost coverage of any potential impact, but it is not yet clear (at least to me) what exactly is asked of RZERC in addition to SSAC and RSSAC. There are some meta issues around the decision making and the more genaral question of change and innovation within the Internet's technical infrastructure and whether 'failure thresholds' are an appropriate instrument for decision making, both technically and policy wise. -- Peter Koch DENIC eG |

1 0

CC's as second level of .XXX
by Demi Getschko May 30, 2018

May 30, 2018

Dear colleagues, any comments/thougths on this issue? === Heads up notice: Please note that ICANN intends to authorize the release of 2 char-code domain names under the legacy top level domain name .XXX, of course subject to the registry operators implementing the previously announced measures to avoid confusion with corresponding Country Codes === best demi

2 2

SAVE THE DATE: ccNSO Community Organized Networking Event - Panama City
by Kimberly Carlson May 30, 2018

May 30, 2018

Dear all, On behalf of our sponsors, you are invited to join our ccNSO Community Organized Networking event in Panama City, Panama. Date: Tuesday, 26 June 2018 Time: 7:30-9:30 pm Location: Hard Rock Hotel 62nd floor terrace Wristbands will be required for this event, to be distributed during Tuesdays Members meeting. [cid:image004.jpg@01D3F7FE.B17DC580] _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Email Kimberly.Carlson(a)icann.org<mailto:Kimberly.Carlson@icann.org> Skype kimberly.carlson.icann [cid:image001.png@01D243BB.E5949130]

1 0

Call for co-organisers session on increasing number of active WG members
by Bart Boswinkel May 29, 2018

May 29, 2018

Dear all, Following the discussion on the last call (24 May) Councillors are (again) invited to participate and help shape the session on workload balancing and volunteer burnout with the cctLD community present in Panama. The session is tentatively scheduled for day 1 of the upcoming ccNSO Members Meeting. As discussed during the last and the ccNSO Council call in April 2018, there will be an interactive session in Panama on how to increase the number of active volunteers in working groups. This is a follow-up and part of the overarching discussion on balancing the workload i.e. setting priorities that Council initiated at its work shop in San Juan. Please find again a link to the background material distributed prior to the April 2018 council meeting:https://community.icann.org/display/ccNSOCWS/26+April+2018 [community.icann.org] If you are interested, kindly let me know by 5 June 2018. Thank you and kind regards, Bart

2 1

ICANN Files Legal Action in Germany to Preserve WHOIS Data
by Joke Braeken May 29, 2018

May 29, 2018

Dear all, ICANN on 25 May 2018 filed injunction proceedings against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. ICANN has taken this step to ask the court for assistance in interpreting the European Union's General Data Protection Regulation (GDPR) in order to protect the data collected in WHOIS. ICANN's "one-sided filing" in Bonn, Germany, seeks a court ruling to ensure the continued collection of all WHOIS data, so that such data remains available to parties demonstrating legitimate purpose to access it, consistent with the GDPR. EPAG recently informed ICANN that when it sells new domain name registrations it would no longer collect administrative and technical contact information, as it believes collection of that data would violate the GDPR rules. ICANN requires that information to be collected, via its contract with EPAG which authorizes it to sell generic top-level domain name registrations. ICANN recently adopted [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> a new Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> regarding how WHOIS data should be collected and which parts may be published, which ICANN believes is consistent with the GDPR. "We are filing an action in Germany to protect the collection of WHOIS data and to seek further clarification that ICANN may continue to require its collection. It is ICANN's public interest role to coordinate a decentralized global WHOIS for the generic top-level domain system. ICANN contractually requires the collection of data by over 2,500 registrars and registries who help ICANN maintain that global information resource," said John Jeffrey, ICANN's General Counsel and Secretary. "We appreciate that EPAG shared their plans with us when they did, so that we could move quickly to ask the German court for clarity on this important issue. We also appreciate that EPAG has agreed that it will not permanently delete WHOIS data collected, except as consistent with ICANN policy." If EPAG's actions stand, those with legitimate purposes, including security-related purposes, law enforcement, intellectual property rights holders, and other legitimate users of that information may no longer be able to access full WHOIS records. ICANN does not seek to require its contracted parties to violate the law. EPAG's position has identified a disagreement with ICANN and others as to how the GDPR should be interpreted. This lawsuit seeks to clarify that difference in interpretation. In its 17 May 2018 adoption of the Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>, the ICANN Board noted that the global public interest is served by the implementation of a unified policy governing aspects of gTLD registration data when the GDPR goes into effect. "The ICANN org is committed to enforcing our contracts to the fullest extent the law allows and preserving the integrity of the WHOIS system," said ICANN President and CEO Göran Marby. The Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, effective today, still requires gTLD registry operators and registrars to collect all registration data. If you submit a WHOIS query for a registration subject to the GDPR, you will only receive "thin" data in return, which includes technical data sufficient to identify the sponsoring registrar, status of the registration, and creation and expiration dates for each registration, but not personal data. Additionally, you will have access to an anonymized email address or a web form to facilitate email communication with the relevant contact for that registration. If you are a third party with legitimate interests in gaining access to the non-public data held by the gTLD registry operator or registrar, there are still ways for you to access that data. You can look up the sponsoring registrar and contact them, and they are obligated to respond to you in a reasonable time. If you do not get a response, ICANN's complaint mechanisms [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_complian…> will be available for you to use. If you find individual parties who you believe are not complying with their obligations under this Temporary Specification or their agreements with ICANN, you may contact ICANN's Contractual Compliance Department to file a complaint. ICANN appreciates the ongoing discussions with the European Commission, and WP29, together with all of the ICANN stakeholders. However, ICANN has seen steps taken by some of our contracted parties that violate their contractual agreements with ICANN. Thus, ICANN must file this action now to both prevent permanent harm to the public interest and seek clarification of the laws, as they relate to the integrity of the WHOIS services. Read the news alert here: https://www.icann.org/news/announcement-2018-05-25-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

call for presenters Tech Day & ccNSO Members Meeting : Natural disasters, disaster recovery and business continuity planning
by Joke Braeken May 29, 2018

May 29, 2018

Dear all, This e-mail contains a call for presenters for ICANN62 (Panama City), on the topic of Natural disasters, disaster recovery and business continuity planning. The topic will be addressed both at Tech Day, and at the ccNSO Members Meeting. TECH DAY At ICANN62, Tech Day (Monday, 25 June) will have a technical oriented discussion on Natural Disasters, and/or Disaster Recovery and Business Continuity Planning (DR/BCP), focusing on the technical recovery plans for the DNS, for the Registry and for the corporate. If you are interested in presenting on the topic of Natural disasters, disaster recovery and business continuity planning at Tech Day, please email ccNSO-techday(a)icann.org<mailto:ccNSO-techday@icann.org> Deadline: Friday, 1 June 2018. COB ccNSO MEMBERS MEETING During a session at the ccNSO Members Meeting on the other hand (Wednesday, 27 June | 09:00-09:45), the same topic will be approached from a business side, focusing among others on testimonials, plans, initiation, testing, critical even, communications, simulation, policy aspects or a tabletop exercise. Consult the draft ccNSO Members Meeting agenda here https://buff.ly/2IFrZEu If you are interested in presenting on this topic during the ccNSO Members Meeting, please email joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Deadline: Friday, 1 June 2018. COB 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

Deadline Extension: Request for Proposal for ccNSO Review
by Joke Braeken May 25, 2018

May 25, 2018

Dear all, ICANN has extended its deadline for applicants to respond to its request for proposal for (RFP) for a provider to conduct an independent assessment of the Country Code Names Supporting Organization (ccNSO). The new deadline is Monday 4 June 2018, 16:00 UTC. The objective of this RFP is to identify an independent examiner that can conduct a comprehensive assessment of the ccNSO. This includes, but is not limited to assessments of: * Whether the ccNSO has a continuing purpose within the ICANN structure; * How effectively the ccNSO fulfils its purpose and whether any change in its structure or operations is desirable to improve the ccNSO's effectiveness; and * The extent to which the ccNSO as a whole is accountable to its organizations, committees, constituencies, and stakeholder groups. The review is scheduled to take place from August 2018 through July 2019. For a complete overview and timeline for the RFP, please see here [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 107 KB]. Indications of interest must be emailed to: ccNSOReview-RFP(a)icann.org<mailto:ccNSOReview-RFP@icann.org>. Proposals should be electronically submitted by 4 June 2018, 16:00 UTC using ICANN's sourcing tool. Access to the sourcing tool may be requested via the same email address as above. 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 From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Friday, 27 April 2018 at 14:19 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-members] Request for Proposal for ccNSO Review Dear all, ICANN is seeking a provider to conduct an independent assessment of the Country Code Names Supporting Organization (ccNSO). The objective of this RFP is to identify an independent examiner that can conduct a comprehensive assessment of the ccNSO. This includes, but is not limited to assessments of: * Whether the ccNSO has a continuing purpose within the ICANN structure; * How effectively the ccNSO fulfils its purpose and whether any change in its structure or operations is desirable to improve the ccNSO's effectiveness; and * The extent to which the ccNSO as a whole is accountable to its organizations, committees, constituencies, and stakeholder groups. The review is scheduled to take place from August 2018 through July 2019. For a complete overview and timeline for the RFP, please see here: https://www.icann.org/en/system/files/files/rfp-ccnso-review-26apr18-en.pdf…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> Indications of interest must be emailed to: ccNSOReview-RFP(a)icann.org<mailto:ccNSOReview-RFP@icann.org>. Proposals should be electronically submitted by 23:59 UTC on 24 May 2018 using ICANN's sourcing tool. Access to the sourcing tool may be requested via the same email address as above. Background According to the ICANN Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_resources…>, the ccNSO is responsible for: * Developing and recommending to the Board global policies relating to country-code top-level domains; * Nurturing consensus across the ccNSO's community, including the name-related activities of ccTLDs; * Coordinating with other ICANN Supporting Organizations, committees, and constituencies under ICANN; * Nominating individuals to fill Seats 11 and 12 on the Board; and * Other responsibilities of the ccNSO as set forth in the Bylaws. 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