January 2014 - Ccnso-council

Call for presentations Singapore meeting
by Gabriella Schittek Jan. 31, 2014

Jan. 31, 2014

Dear all, As always, we will host our popular "ccTLD News Session" during the Singapore meeting (currently scheduled for Wednesday, 26 March). If your registry recently has undergone any interesting changes, is kicking off some new initiatives or is facing challenges, which you wish to inform the ccTLD community about please let me know! I need following information from you: Name of presentation: Name of presenter: Short summary (2-3 sentences will do!): Estimated time needed: As we only have a limited time slot, we can't, unfortunately, guarantee a slot for every volunteer. Filling in the requested information will help our Programme Working Group in making a selection of presentations. Please, let me know if you wish to present by Friday, 14 February at the latest. Kind regards, Gabi

1 0

ccNSO Initiative - Your Area of Expertise!
by Gabriella Schittek Jan. 31, 2014

Jan. 31, 2014

Dear all, Last year, the ccNSO Council initiated a Study Group, which looked into ways of building capacity in the ccNSO Community and how to enhance its work. The final report is available at http://ccnso.icann.org/workinggroups/capacity-final-27feb13-en.pdf. One of the Study Group recommendations was to "Find out the skill set of the community members, target this more efficiently and enhance the skills that exist". In other words the ccNSO Secretariat is tasked to ask members (non-members are also welcome to respond) to indicate the expertise they can contribute with (if interested). The secretariat will then maintain a list of the "pools of expertise" that exists in our community - in order to be able to target the relevant people, when needed. Situations where such "pools of expertise" could be needed are, for instance, when the ccNSO receives a request for input from ICANN (or other relevant institutions) and quickly needs to react, or when a Working Group is set up to look into a certain topic. To meet this recommendation, we are now reaching out to you and ask if you are interested in participating, to indicate the expertise you could contribute with. Areas of expertise could be: Legal Financial Technical Administrative Strategy Internet Governance but you are welcome to define/add any other area. Participating in this initiative is entirely voluntary, however, the more people that participate, the better we get! Therefore, I would like to encourage as many as possible to step up and let us know your areas of expertise. Non-ccNSO members are also most welcome to participate. If you are interested, please send me an email and the ccNSO Secretariat will keep the data. You can, at any time, withdraw from this initiative as well. Kind regards, Gabi

1 0

Re: [ccnso-council] Council Minutes 23 January
by Lesley Cowley Jan. 30, 2014

Jan. 30, 2014

Hi Kristina, In section 3, I think that I expressed concern that it was not yet clear whether all ccTLDs who wished to participate would be able to do so. This concern was noted and it was hoped that Demi and others would bear it in mind and update colleagues when information was available. In section 6, I think that we agreed that the need to make ccNSO bylaw changes would have to be very carefully considered, given the process for making such changes and that any PDP process might open the possibility of other by law changes. Kind regards, Lesley Lesley Cowley, OBE CEO Nominet Minerva House Edmund Halley Road Oxford Science Park Oxford, OX4 4DQ UK Tel: +44-(0)-1865-332211 http://www.nominet.org.uk/ Twitter: @lesleycowley From: Kristina Nordstrom <kristina.nordstrom(a)icann.org<mailto:kristina.nordstrom@icann.org>> Date: Thursday, 30 January 2014 14:39 To: ccNSO Council <ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>> Subject: [ccnso-council] Council Minutes 23 January Dear all, Please find attached the Council minutes from 23 January 2014 and let me know before 5 February if you wish to make any amendments. Kind regards, Kristina

2 4

Council Minutes 23 January
by Kristina Nordstrom Jan. 30, 2014

Jan. 30, 2014

Dear all, Please find attached the Council minutes from 23 January 2014 and let me know before 5 February if you wish to make any amendments. Kind regards, Kristina

1 0

Triage Recommendation on Request 4-2014: GNSO Privacy & Proxy Services Accreditation Issues PDP Working Group
by Gabriella Schittek Jan. 29, 2014

Jan. 29, 2014

Dear Councillors, Below is a request for input, which was sent directly to Byron last week from the GNSO Privacy & Proxy Services Accreditation Issues PDP Working Group. The entire email is pasted in below the summary. The triage group recommendation is two-fold: : 1) A staff member should be requested to reply, on behalf of the ccNSO Council, that the ccNSO as a group does not have a point of view on this matter; 2) In the reply, it should also be noted, that whilst the questions can be forwarded to the ccTLD Community for individual input, chances are quite small that any input actually will be received. Suggest that the Working Group puts up the questions into a survey tool to increase chances of obtaining replies. Let me know if you have any objections to the recommendations by Friday, 31 January 2014. Thanks! Gabi == Topic: Privacy & Proxy Services Accreditation Issues Originator: GNSO Privacy & Proxy Services Accreditation Issues PDP Working Group Summary of request: The GNSO Privacy & Proxy Services Accreditation Issues PDP Working Group is asking other SO/ACs for help to define which topics they should look into during their work. See below for full explanation. Date received: 23 January 2014 Last day for Comments/input/response, if any: 28 February 2014 Recommended action, if any: 1) A staff member should be requested to reply, on behalf of the ccNSO Council, that the ccNSO as a group does not have a point of view on this matter; 2) In the reply, it should also be noted, that whilst the questions can be forwarded to the ccTLD Community for individual input, chances are quite small that any input actually will be received. Suggest that the Working Group puts up the questions into a survey tool to increase chances of obtaining replies. Expertise needed, if any: Legal, managerial Impact on ccNSO/ccTLDs: Low === Dear SO/AC Chair - Dear Byron, As you may be aware, the GNSO Council recently initiated a Policy Development Process (PDP) on Privacy & Proxy Services Accreditation Issues. As part of its efforts to obtain input from the broader ICANN Community at an early stage of its deliberations, the Working Group that has begun to explore questions related to these issues is looking for any input or information that may help inform our deliberations. Below you will find an overview of the issues that the WG has been assigned to address in its charter. We would appreciate it very much if you would examine the items and provide any input that your group may have to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org <mailto:gnso.secretariat@gnso.icann.org> ) by Friday 28 February 2014. If you cannot submit your input by that date, but your group would like to contribute, please let us know when we can expect to receive your contribution so that we can plan accordingly. While we would like your thoughts on all items, responses to a subset still will be helpful. Please feel free also to suggest modifications to or additional questions that your group believes useful for the WG to address. Your input will be valuable for informing the WG as we begin our work. We have included a list of relevant definitions at the end of this document in the hope that they will be of assistance to your group in providing input. For further background information on our WG¹s activities to date and to follow our work as we move forward, see https://community.icann.org/x/9iCfAg <https://community.icann.org/x/9iCfAg> . With best regards, Don Blumenthal, Chair of the Privacy & Proxy Services Accreditation Issues PDP Working Group QUESTIONS FOR WHICH THE WG WAS CHARTERED AND IS SEEKING INPUT This RAA PDP Working Group (WG) was created to provide the GNSO Council with policy recommendations regarding the issues identified during the 2013 RAA negotiations, including recommendations made by law enforcement and GNSO working groups,that were not addressed during the 2013 RAA negotiations but are otherwise suited for a PDP. These issues focus on theaccreditation of Privacy & Proxy Services. As part of its deliberations on the matter, the RAA PDP WG was asked to, at a minimum, consider those issues detailed in the StaffBriefing Paper <http://gnso.icann.org/en/issues/raa/negotiations-conclusion-16sep13-en.pdf> published on 16 September 2013 and included in the WG Charter (seehttps://community.icann.org/display/gnsopnpsrvaccrdtwg/WG+Charter <https://community.icann.org/display/gnsopnpsrvaccrdtwg/WG+Charter> ). The WG has organized the questions in the hope that it adds clarity. I. MAIN ISSUES 1. What, if any, are the types of Standard Service Practices that should be adopted and published by ICANN-accredited privacy/proxy service providers? 2. Should ICANN distinguish between privacy and proxy services for the purpose of the accreditation process? 3. What are the contractual obligations, if any, that if unfulfilled would justify termination of customer access by ICANN-accredited privacy/proxy service providers? 4. What types of services should be covered, and would be the forms of non-compliance that would trigger cancellation or suspension of registrations? 5. What are the effects of the privacy and proxy service specification contained in the 2013 RAA? Have these new requirements improved WHOIS quality, registrant contactability and service usability? 6. What should be the contractual obligations of ICANN accredited registrars with regard to accredited privacy/proxy service providers? Should registrars be permitted to knowingly accept registrations where the registrant is using unaccredited service providers that are however bound to the same standards as accredited service providers? II. MAINTENANCE 1. Should ICANN-accredited privacy/proxy service providers be required to label WHOIS entries to clearly show when a registration is made through a privacy/proxy service? 2. Should ICANN-accredited privacy/proxy service providers be required to conduct periodic checks to ensure accuracy of customer contact information; and if so, how? 3. What rights and responsibilities should customers of privacy/proxy services have? What obligations should ICANN-accredited privacy/proxy service providers have in managing these rights and responsibilities? Clarify how transfers, renewals, and PEDNR policies should apply. 4. Should ICANN-accredited privacy/proxy service providers distinguish between domain names used for commercial vs. personal purposes? Specifically, is the use of privacy/proxy services appropriate when a domain name is registered for commercial purposes? 5. Should there be a difference in the data fields to be displayed if the domain name is registered or used for a commercial purpose, or by a commercial entity instead of a natural person? 6. Should the use of privacy/proxy services be restricted only to registrants who are private individuals using the domain name for non-commercial purposes? III. CONTACT 1. What measures should be taken to ensure contactability and responsiveness of the providers? 2. Should ICANN-accredited privacy/proxy service providers be required to maintain dedicated points of contact for reporting abuse? If so, should the terms be consistent with the requirements applicable to registrars under Section 3.18 of the RAA? 3. Should full WHOIS contact details for ICANN-accredited privacy/proxy service providers be required? 4. What are the forms of alleged malicious conduct, if any, that would be covered by a designated published point of contact at an ICANN-accredited privacy/proxy service provider? IV. RELAY 1. What, if any, are the baseline minimum standardized relay processes that should be adopted by ICANN-accredited privacy/proxy service providers? 2. Should ICANN-accredited privacy/proxy service providers be required to forward to the customer all allegations of illegal activities they receive relating to specific domain names of the customer? V. REVEAL 1. What, if any, are the baseline minimum standardized reveal processes that should be adopted by ICANN-accredited privacy/proxy service providers? 2. Should ICANN-accredited privacy/proxy service providers be required to reveal customer identities for the specific purpose of ensuring timely service of cease and desist letters? 3. What forms of alleged malicious conduct, if any, and what evidentiary standard would be sufficient to trigger such disclosure? What specific alleged violations, if any, would be sufficient to trigger such publication? 4. What safeguards must be put in place to ensure adequate protections for privacy and freedom of expression? 5. What safeguards or remedies should be available in cases where publication is found to have been unwarranted? 6. What circumstances, if any, would warrant access to registrant data by law enforcement agencies? 7. What clear, workable, enforceable and standardized processes should be adopted by ICANN-accredited privacy/proxy services in order to regulate such access (if such access is warranted)? LIST OF RELEVANT DEFINITIONS (1) Privacy & Proxy Services The following definitions are those used by the GNSO in the various WHOIS studies it commissioned between 2010-2012 (http://gnso.icann.org/issues/whois/whois-working-definitions-study-terms-18 feb09.pdf <http://gnso.icann.org/issues/whois/whois-working-definitions-study-terms-18 feb09.pdf> ): · Privacy services hide customer details from going into WHOIS. Privacy service providers, which may include registrars and resellers, may offer alternate contact information and mail forwarding services while not actually shielding the domain name registrant¹s identity. By shielding the user in these ways, these services are promoted as a means of protecting personal privacy, free speech and human rights and avoiding personal data misuse. · Proxy services protect users¹ privacy by having a third-party register the name. The third-party is most often the proxy service itself. The third-party allows the user to access and use the domain name through a separate agreement or some other arrangement directly with the user. Proxy service providers may include web design, law, and marketing firms; web hosts, registrar subsidiaries, resellers and individuals. NOTE: The 2013 Registrar Accreditation Agreement contains a temporary specification relating to Privacy & Proxy Services, which refers to these services as follows (http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun1 3-en.pdf <http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun1 3-en.pdf> ): 1.1 "P/P Customer" means, regardless of the terminology used by the P/P Provider, the licensee, customer, beneficial user, beneficiary, or other recipient of Privacy Services and Proxy Services. 1.2 "Privacy Service" is a service by which a Registered Name is registered to its beneficial user as the Registered Name Holder, but for which alternative, reliable contact information is provided by the P/P Provider for display of the Registered Name Holder's contact information in the Registration Data Service (Whois) or equivalent services. 1.3 "Proxy Service" is a service through which a Registered Name Holder licenses use of a Registered Name to the P/P Customer in order to provide the P/P Customer use of the domain name, and the Registered Name Holder's contact information is displayed in the Registration Data Service (Whois) or equivalent services rather than the P/P Customer's contact information. 1.4 "P/P Provider" or "Service Provider" is the provider of Privacy/Proxy Services, including Registrar and its Affiliates, as applicable. (2) Relay & Reveal Requests The following descriptions are taken from the GNSO¹s Terms of Reference for a proposed Proxy & Privacy Relay & Reveal Study in 2010 (http://gnso.icann.org/issues/whois/whois-proxy-privacy-relay-reveal-studies -tor-29sep10-en.pdf <http://gnso.icann.org/issues/whois/whois-proxy-privacy-relay-reveal-studies -tor-29sep10-en.pdf> ): * For many domains, Registered Name Holders can be reached directly at addresses obtained from WHOIS. However, for Privacy/Proxy-registered domains, Registered Name Holders or third party licensees cannot be reached directly via WHOIS- published addresses. Instead, communication relay requests may be sent to the Privacy/Proxy service provider published in WHOIS, or attempted using addresses obtained from other sources, websites or communications associated with the domain. For many domains (including those registered via Privacy services), the Registered Name Holder's identity is published directly in WHOIS. However, for domains registered via Proxy services, the name of the licensee is not published in WHOIS; third party licensees can typically only be identified by asking the Proxy to reveal the licensee's identity, given reasonable evidence of actionable harm. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org <http://gnso.icann.org/>

2 1

Blog post on ICANN's Strategic Initiatives
by Gabriella Schittek Jan. 29, 2014

Jan. 29, 2014

Dear all, Thresesa Swinehart, ICANN's Senior Advisor to the President on Strategy, has published a blog post on ICANN's Strategic Initiatives: http://blog.icann.org/2014/01/update-icanns-strategic-initiatives/ Kind regards, Gabi

1 0

[Triage] Request 3-2014 Review of Trusted Community Representation in Root Zone DNSSEC Key Signing Ceremonies
by Gabriella Schittek Jan. 24, 2014

Jan. 24, 2014

Dear Councillors, See the Triage committee's recommendation below on the request for input to the Review of Trusted Community Representation in Root Zone DNSSEC Key Signing Ceremonies. If you do not agree on the recommendation, please send your suggestion for action to the Council email list by Tuesday, 28 January 2014. Kind regards, Gabi == Topic: Review of Trusted Community Representation in Root Zone DNSSEC Key Signing Ceremonies Originator: ICANN Summary of request: ICANN is reviewing what changes, if any, should be made to the current model of Trusted Community Representative participation in Root Zone DNSSEC Key Signing Ceremonies: http://www.icann.org/en/news/public-comment/tcr-dnssec-key-signing-21jan14-e n.htm Date received: 22 February 2014 Last day for Comments/input/response, if any: 11 February 2014 Recommended action, if any: Post to email lists for information (done) Expertise needed, if any: Variuos Date of submission to Council: 24 January 2014 Last date of Council decision: 28 January 2014 Impact on ccNSO/ccTLDs: Low

1 0

Webinar on Strategy Panel on ICANN Multistakeholder Innovation
by Gabriella Schittek Jan. 24, 2014

Jan. 24, 2014

Dear all, On Friday, 31 January, ICANN is hosting a webinar on the Strategy Panel on ICANN Multistakeholder Innovation. If you are interested in joining, see http://www.icann.org/en/news/announcements/announcement-23jan14-en.htm for further details. Kind regards, Gabi

1 0

Council Recording 23 January
by Kristina Nordstrom Jan. 23, 2014

Jan. 23, 2014

Dear all, The recording from the Council call today on 23 January can now be found here: http://audio.icann.org/ccnso/ccnso-council-20140123-en.mp3 Kind regards, Kristina

1 0

Reminder: Dial in details Council Call today 23 January 12:00 UTC
by Kristina Nordstrom Jan. 23, 2014

Jan. 23, 2014

Dear all, The next Council Call will take place today 23 January at 12:00 UTC. Please find the dial in details below. Dial in numbers: http://www.adigo.com/icann/ Conference ID: 5258 Adobe Room: http://icann.adobeconnect.com/ccnsocouncil/ Two-way audio will be available in the Adobe Room. Kind regards, Kristina

5 4