February 2017 - council - lists.icann.org

Fwd: Thick WHOIS Legal Review Memorandum
by Erika Mann March 2, 2017

March 2, 2017

Dear James, dear GNSO colleagues - below is a draft approach to request a legal update from ICANN concerning the existing legal review memorandum which was submitted to the Thick WHOIS IRT on 8 June 2015. We discussed this at our last call. I hope you may find the draft request below helpful. First part (1) covers the reasoning. And, second part (2) highlights the relevant parts for this debate from the original 2015 legal memo. Thanks, Erika * 1) Draft text for request * GNSO request from ICANN legal an updated review of the existing legal review memorandum which was submitted to the Thick WHOIS IRT on 8 June 2015. We recommend to coordinate with appropriate subject matter experts and outside counsel to ensure the GNSO Council receives updated fact-based and independent advice, like this was done with the existing legal review memorandum from 2015. We like to see a full review of applicable law(s) and a list of recommendations as to what extent existing policies the GNSO should consider changing. FOR EXAMPLE: Since June 2015 the legal data privacy/protection/retention landscape changed drastically in many countries but in In particular in the European Union. It is therefore key to understand how these changes might impact ICANN registries, registrars, users and contractual arrangements in general. Certain national laws have additional extraterritorial implications. These impacts were not captured in the 2015 legal review memorandum. Why is such a review needed? A good example are the changes that were introduced in the European Union and between the EU and the US since June 2015. EXPLANATION: The 'General Data Protection Regulation' in the European Union came into force May 2016 and will apply across Europe in May 2018. The core element of the data protection reform is a general data protection regulation that will replace and equal existing data protection laws across the European Union countries. This new regulation updates and modernises the principles of the 1995 Data Protection Directive that the existing ICANN legal review memorandum from 2015 covers. It sets out the rights of the individual and establishes the obligations of those processing and those responsible for the processing of the data. It also establishes the methods for ensuring compliance as well as the scope of sanctions for those in breach of the rules. In addition, certain aspects of this law, will be interpreted by the European Data Protection Board (EDPB) in the near future. Law enforcement related aspects of this law are regulated in a separate legal framework. The GDRP is insofar unique as it's a law with far reaching extraterritorial implications, this aspect is not captured in ICANNs 2015 legal memo neither. Since 2015 the transfer of personal data requirements from EU to the US changed as well. In 2015 the Safe Harbor Agreement (SHA) was in place, in 2016 a new Privacy Shield Agreement came into force, replacing the SHA, implementing new adequacy requirements for the transfer of date between EU and US. ICANNs legal memo from 2015 does not cover these developments. In addition, we may see new legal challenges arising that might question the SHA because of President Donald Trump’s Executive Order on domestic safety, released on January 26th, 2017. "Agencies shall, to the extent consistent with applicable law, ensure that their privacy policies exclude persons who are not United States citizens or lawful permanent residents from the protections of the Privacy Act regarding personally identifiable information." * 2) Key exert from the existing legal review memorandum which was submitted to the Thick WHOIS IRT on 8 June 2015* To the extent that a contracted party finds that it is unable to comply with the Thick Whois policy requirements due to a conflict with its obligations under local privacy laws, such conflicts may be dealt with by exception through use of the Whois Conflicts Procedure, or requests to ICANN for an amendment to or waiver of certain provisions in the Registry Agreement or Registrar Accreditation Agreement. (page 1) As further detailed below, to address the concerns previously highlighted in the EWG Memo, this memorandum provides practical recommendations about the move to Thick Whois and also notes that ICANN’s Procedure for Handling WHOIS Conflicts with Privacy Law is available to contracted parties to address specific cases where Thick Whois requirements may be inconsistent with the parties’ obligations under local privacy laws. (page 2) Additionally, contracted parties may consider requesting amendments to or waivers from specific Thick Whois requirements in agreements with ICANN that may be inconsistent with contracted parties' obligations under local privacy laws. (page 2) The present analysis is neither a detailed nor complete analysis of data protection laws within any particular jurisdiction. Instead, ICANN performed a general survey of EU data protection laws as the Data Protection Directive 95/46/EC embodies international principles which serve as a basis for many data protection laws around the world. (page 3) As an example of the latter, see Russia’s Federal Law 242-FZ (“Localization Law”) which requires compliance by 1 September 2015, but is still the subject of significant uncertainty as to its scope, applicability and requirements.(page 4) It is true that in some countries there are some important and legitimate questions relating to data protection obligations under local law that must be addressed as implementation of Thick Whois across all gTLDs is considered. (page 5) ICANN recognizes that two of those principles trigger particular attention in relation to the transition to Thick Whois: the need for registrars in some countries to establish a 'lawful basis' (i) for the disclosure of registrants' personal data to the relevant registry and (ii) for the transfer of such data to another country (in this case, the U.S., where all three relevant registries are located). “Transfer” generally covers any sharing, transmission or disclosure of, providing access to, or otherwise making available, personal information to third parties. The EU Data Protection Directive (95/46/EC) (“EU Directive”), for example, requires that personal information may only be transferred to third countries outside the European Economic Area (EEA) if the receiving countries provide an “adequate” level of protection, as determined by the European Commission or the transfer satisfies one of the exceptions permitted by the EU Directive. One of the two most viable “exceptions” to permit lawful transfer is the consent of the data subjects. However, utilizing this “exception” does entail some challenge that the registrar and registry must ensure are addressed. (page 6/7) Consent in some form and degree is of significant importance across most jurisdictions as it relates to implementation of thick Whois. For example, consent is one way in which organisations can meet one of the ‘conditions’ for processing of personal data throughout the EEA. It also serves to justify transfers outside the EEA - the EU Directive clearly specifies consent9 as a lawful ground for these purposes. In Russia, transfer is permitted provided that (1) consent of the data subject is properly obtained and (2) the transfer is as legally prescribed.10 If proper consent is obtained, such data may be collected, stored, published and/or transferred in the manner consistent with the specific consent provided. Other data protection requirements will still need to be met– for example, proportionality, data quality and security considerations still apply even where consent has been obtained. (page 7) However, in certain jurisdictions there exists the right to revoke consent. In such instance, the registry or registrar must determine the effect on the registration and the corresponding registration data. The EU Directive does not contain any procedural guidance around withdrawal of consent (e.g. time periods for acting on this). The Article 29 Working Party11 requires that consent should be possible to be withdrawn at any time with effect for the future. It regards consent to be deficient if no effective withdrawal is provided.12 The Article 29 Working Party itself has made clear that withdrawal of consent is not retroactive13. Accordingly, if a registrant withdrew consent, this would not affect the lawfulness of data which had already been transferred from an EU registrar to a relevant registry. (page 8) Apart from the possibility to revoke consent, there may also be doubts as to whether the consent of registrants granted as a condition for the transfer of the registrant data to the registry under the thick Whois should be regarded as “freely given,” in particular if all registrars "require" registrants to grant consent in a similar form. However, ICANN notes that this concern can actually be addressed via the provision of privacy/proxy services by the relevant registrars, as these do provide effective choice to the registrant. (page 8) In any case and especially for the application of the thick Whois in the EU, ICANN considers it is important that the data processing under thick Whois and the transition thereto can also be based upon the legitimate interests of a party (including ICANN, registries, and registrants). Legitimate interests can be an alternative basis for EU registrars to justify processing of personal data, as long as the processing is not unwarranted because of the (privacy) interests of the individuals whose data is processed. Acknowledged legitimate interests include increased security, stability and resiliency in the Internet. However, from an EU perspective, if the data processing under thick Whois is based upon legitimate interests, instruments to provide for an adequate level of data protection on part of the data recipient located outside of the EEA will also become relevant (e.g., Standard Contract Clauses, Safe Harbor, approval from the relevant data protection authorities, etc.14). This is because while sharing of data within the EEA may be justified on this basis, there are additional restrictions on transfers of data outside the EEA. Those instruments contain restrictions on onward transfers (to be imposed on third parties wishing to look up EU Whois data) and contracted parties will need to assess whether and in which form it is practically feasible to implement those restrictions; these restrictions are likely to mean that consent is the most suitable approach, notwithstanding the difficulties outlined above. Furthermore, in addition to consent, (i) privacy/proxy services, and perhaps (ii) thick Whois services where the data stays in the region subject to restrictions to avoid data transfer limitations remain as options available to address transfer of the data. (page 9) The Whois Conflicts Procedure is the implementation of GNSO consensus policy adopted “in order to facilitate reconciliation of any conflicts between local/national mandatory privacy laws or regulations and applicable provisions of the ICANN contract regarding the collection, display and distribution of personal data via the gTLD Whois service.” The Whois Conflicts Procedure is designed to ensure regulatory obstacles on the collection, processing, transfer and display of gTLD registration data can be dealt with by exception in instances where a registry or registrar can demonstrate that it is legally prevented by local/national data protection laws or regulations from fully complying with applicable provisions of its contract. ICANN has commenced a review of the Whois Conflicts Procedure to determine whether modifications to that procedure might be considered. (page 10) The most common complaint of ICANN contracted parties is that the Whois Conflicts Procedure requires 15 http://www.icann.org/en/resources/registrars/whois-privacy-c onflictsprocedure-17jan08- en.htm <http://www.icann.org/en/resources/registrars/whois-privacy-conflictsprocedu…> 11 “notification of an investigation, litigation, regulatory proceeding or other government or civil action . . .” as its trigger. To the extent any proposed changes to implementation of the Whois Conflicts Procedure are recommended, they would be presented to the GNSO Council, which would determine next steps. (page 10/11) In other cases, ICANN has granted limited waivers from compliance with specific terms and conditions in the 2013 Registrar Accreditation Agreement regarding data retention requirements in cases where registrars requests such change because they believe the requirements violate their countries’ data retention laws. (page 12) Additionally, contracted parties may wish to consider requesting amendments to or waivers from specific contractual requirements in connection with the transition from a thin to a thick Whois model to the extent the contracted parties’ obligations conflict with its local laws. Historically, ICANN has granted amendments to specific Whois provisions in the Registry Agreement when requested by registry operators with support of relevant Data Protection Authorities to comply local privacy laws. (page 11) Where a conflict is proven to exist by a registrar or registry by way of the Whois Conflicts Procedure, or an amendment or waiver from certain Whois requirements is granted by ICANN, the Registration Data Access Protocol, or RDAP, could be a means to mitigating such conflict without eliminating entirely the benefits of thick WHOIS (e.g. an end-user looking up Whois data would see “thick” data, even though the underlying data is not be stored with the registry). Because RDAP would only permit registry-level access to thick Whois output by redirect to the registrar’s own portal, meaning such data would not be “thick” in the sense of existing also at the registry level, there are questions as to whether its implementation would be consistent with policy recommendation #1 and the identified benefits of the thick Whois model outlined in the Thick Whois Final Report. (page 12) (To assist with the legal analysis reflected in this Section, ICANN engaged Bird & Bird, a leading international law firm with over 1100 lawyers in 27 offices across Europe, the Middle East and Asia with a highly regarded International Privacy & Data Protection Group that advises clients throughout the world. (page 6) On Fri, Jan 20, 2017 at 12:22 AM, Marika Konings <marika.konings(a)icann.org> wrote: > > Dear All, > > > > As requested during the call today, please find attached the legal review memorandum which was submitted to the Thick WHOIS IRT on 8 June 2015. > > > > Best regards, > > > > Marika > > > > Marika Konings > > Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) > > Email: marika.konings(a)icann.org > > > > Follow the GNSO via Twitter @ICANN_GNSO > > Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. > > > > > _______________________________________________ > council mailing list > council(a)gnso.icann.org > https://mm.icann.org/mailman/listinfo/council >

3 2

FOR INFORMATION & DISTRIBUTION: Public comment period extended for the IGO-INGO Curative Rights PDP Initial Report
by Mary Wong Feb. 28, 2017

Feb. 28, 2017

Dear Councilors, Please note that the public comment period for the Initial Report of the IGO-INGO Access to Curative Rights PDP Working Group has been extended, on request, to 30 March 2017 (see below for further information). We hope this will allow your respective communities sufficient time to consider submitting comments to the report. For your information, a 30-minute slot has been allocated for the Working Group co-chairs – as has been done for the other ongoing PDP Working Groups – to discuss progress with the Council and GNSO community as part of the GNSO Working Sessions on Sunday 12 March. To maximize the discussion time, you may wish to consider sending in any questions you or your communities may have for each PDP Working Group ahead of time – staff will be pleased to collate and circulate the questions on your behalf. Thanks and cheers Mary From: <gnso-igo-ingo-crp-bounces(a)icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Tuesday, February 28, 2017 at 09:34 To: "gnso-igo-ingo-crp(a)icann.org" <gnso-igo-ingo-crp(a)icann.org> Subject: [Gnso-igo-ingo-crp] Comment period extended for the Initial Report Dear all, In view of community requests received for an extension of the public comment period for our Initial Report, the Working Group co-chairs have agreed to an extension of 2 weeks following the close of the upcoming ICANN58 Public Meeting. The comment period will now close on 30 March 2017: https://www.icann.org/public-comments/igo-ingo-crp-access-initial-2017-01-2…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>. We do not anticipate this extension affecting the current plan to discuss our preliminary recommendations, and feedback received so far, with the community at ICANN58. There have been several comments received to date, as some members will have noted: https://forum.icann.org/lists/comments-igo-ingo-crp-access-initial-20jan17/…<https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.icann.org_lists_…>. Staff will of course continue to encourage interested community groups and members to submit their comments as soon as they can. Thanks and cheers Mary

1 0

Celebrate a Storybook Evening in Copenhagen with Verisign
by Drazek, Keith Feb. 28, 2017

Feb. 28, 2017

Hello GNSO Council colleagues and ICANN GNSO Team. You are all invited to Verisign’s reception in Copenhagen, which is scheduled for Sunday the 12th. Details are below. I hope you can make it! Best regards, Keith If your email program has trouble displaying this email, view it as a web page<http://now.eloqua.com/es.asp?s=425&e=250593&elqTrackId=2245ca904e4b4268ac39…> Join Verisign to celebrate a Story Book Evening Join Verisign to celebrate a Story Book Evening<http://img.en25.com/EloquaImages/clients/Verisign/%7bfe8a03b0-5fa4-45fe-8d4…> <http://s3.amazonaws.com/verisign-email-2017/VRSN_Copenhagen_ICANN_Email_022…> Join Verisign to celebrate a Story Book Evening at the H.C. Andersen Castle in Tivoli Garden. The H.C. Andersen Castle is named after the world famous Danish fairytale writer Hans Christian Andersen – whose famous works include The Ugly Duckling, The Little Mermaid, The Nightingale and many more timeless classics. Tivoli Garden is a top attraction in Copenhagen and we hope you can join us for drinks, appetizers and great company. EVENT DETAILS: Date: Sunday, March 12 Time: 19:00 – 22:00 hours Venue: H.C. Andersen Castle H.C. Andersen Blvd. 22, 1553 København V, Denmark Phone +45 33 15 10 01 Dress Code: Business Attire or Cocktail Getting There: The castle is located a short drive from AC Bella Sky. Buses will be available from the AC Bella Sky departing at 18:30 until 19:30 hours. Please have your RSVP confirmation page and ICANN Name Badge with you prior to loading the bus. Entrance: Your ICANN Name Badge and a RSVP Confirmation is required to enter the event. This exclusive event is by INVITATION ONLY. <https://www.eventbrite.com/e/a-story-book-evening-with-verisign-tickets-323…> <http://s3.amazonaws.com/verisign-email-2017/VRSN_Copenhagen_ICANN_Email_022…> <https://twitter.com/verisign?elqTrackId=5c98875f5d2e402f9e571766b59c263e&el…> <https://www.facebook.com/Verisign?elqTrackId=87a7dd04226a4937904e8c9f33bd18…> <http://www.linkedin.com/company/verisign?elqTrackId=177d733ac979442b8e05e72…> <http://blogs.verisigninc.com?elqTrackId=6cb9d63530234fe189481c8b9523ae26&el…> Connect with Verisign on Social Media to stay on top of current internet security news, trends, and information. <http://img.en25.com/EloquaImages/clients/Verisign/%7b9ba0327d-eaaf-439d-b14…> Verisign.com<http://www.Verisign.com?elqTrackId=e0a605df77aa47078061359eea607c45&elq=f28…> ©2017 Verisign, Inc. All rights reserved. VERISIGN, the VERISIGN logo, and other trademarks, service marks, and designs are registered or unregistered trademarks of Verisign, Inc. and its subsidiaries in the United States and in foreign countries. All other trademarks are property of their respective owners. To remove your name from future Verisign promotional mailings or to update your communication preferences and user profile, please visit us at: http://www.verisign.com/en_US/compref/index.xhtml<http://www.verisign.com/en_US/compref/index.xhtml?elqTrackId=9d887eff595242…> or write to Verisign, Inc., Attention: Subscriber Services, 12061 Bluemont Way, Reston, VA 20190. To remove yourself from receiving future Verisign promotional emails or non-service emails, please visit us at http://www.verisign.com/compref/<HTTP://www.verisigninc.com/compref?elq=f2874edd00b0404fada8719284d6701e&elq…>and update your communication preferences and user profile. <http://s425.t.en25.com/e/FooterImages/FooterImage1?elq=f2874edd00b0404fada8…>

1 0

GNSO Policy Briefings published
by Marika Konings Feb. 28, 2017

Feb. 28, 2017

Dear All, To assist you and your respective communities in the preparation for ICANN58, the GNSO Team has just published the GNSO Policy Briefings which can be found here: https://gnso.icann.org/en/issues/policy-briefing-icann58-27feb17-en.pdf. Please distribute these to your respective communities and/or anyone else that may be interested. Best regards, 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

GNSO Council Abstention Notification Form [#238]
by ICANN Feb. 28, 2017

Feb. 28, 2017

1 0

Reminder: Document and Motion deadline Sunday, 5 March 2017 at 23:59 UTC for the GNSO Council Meeting 15 March 2017 at 10:00 UTC/ 11:00 local time
by Nathalie Peregrine Feb. 27, 2017

Feb. 27, 2017

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. SUNDAY, 5 March 2017 at 23:59 UTC) of the GNSO Council Meeting on 15 March 2017 at 10:00 UTC, 11:00 local time. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/lJvRAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> 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

Announcement: Pre-ICANN58 Policy Open House Registration
by Nathalie Peregrine Feb. 27, 2017

Feb. 27, 2017

https://www.icann.org/news/announcement-2017-02-27-en Pre-ICANN58 Policy Open House Monday, 6 March 2017 10:00 UTC and 19:00 UTC Please register via this form<https://goo.gl/vZw8kM> by 3 March 2017! 27 February 2017 The Policy Development Support Team is pleased to announce two sessions for the Pre-ICANN58 Policy Open House on Monday, 6 March 2017 at 10:00 UTC and 19:00 UTC. The Policy Open House builds on the previous Policy Update Webinar and incorporates more interaction. The focus of each open house session is an active question and answer session with the Policy Development Support Team. The new format will feature: · Decreased Duration | Two 60-minute sessions, rather than two 90-minute briefings · Interactive Format | A question and answer exchange with the Policy Team · Preparatory Materials | The Pre-ICANN58 Policy Report<https://www.icann.org/resources/pages/presentations-2012-08-27-en> and Generic Names Supporting Organization Policy Briefing ICANN58 Edition<https://gnso.icann.org/en/issues/background-briefings> This improved structure will allow the ICANN community to ask questions about policy and advice development work taking place at ICANN58. The Policy Team also welcomes questions through the registration form<https://goo.gl/forms/dVbmhQOT8sakSsmg2> and via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. The Policy Team will provide brief overviews and answer questions regarding current work within each Supporting Organization and Advisory Committee: · Address Supporting Organization (ASO) · Address Supporting Organization Address Council Annual Meeting · Internet Assigned Numbers Authority (IANA) Numbering Services Review Committee Meeting · Country Code Names Supporting Organization (ccNSO) · Implementation of the Processes and Mechanisms Related to The Empowered Community · Interim Report Cross-Community Working Group: Framework for Use of Country and Territory Names as Top Level Domains open for Public Comment · Policy Development Process regarding the retirement of country code Top Level Domains and the development of a review mechanism for the decisions on delegation, revocation and retirement of country code Top Level Domains · Generic Names Supporting Organization (GNSO) · Generic Names Supporting Organization Policy Development Processes (including new generic Top Level Domain Subsequent Procedures, the Review of All Rights Protection Mechanisms (RPMs) in All generic Top Level Domains, the Next-Generation Registration Directory Service (RDS) to Replace WHOIS, the International Governmental Organization (IGO)-International Non-Governmental Organization (INGO) Access to Curative Rights Protection Mechanisms) · Non-Policy Issues (such as Generic Names Supporting Organization Review Implementation, Bylaws updates and Generic Name Supporting Organization Standing Selection Committee) · Cross-Community Working Groups (including new generic Top Level Domain Auction Proceeds and Use of Country & Territory names as Top Level Domains) · At-Large Advisory Committee (ALAC) and At-Large Community · The At-Large Review · The work of the At-Large Structures Criteria and Expectations Taskforce · At-Large and Work Stream 2 Issues · Governmental Advisory Committee (GAC) · Protection of Red Cross/Red Crescent national names & Protection of International Governmental Organization acronyms · Accountability Work Stream 2 Issues · Input to Generic Names Supporting Organization Policy Development Process on Subsequent Procedures for new generic Top Level Domains and Registration Directory Services · Root Server System Advisory Committee (RSSAC) · [RSSAC023]: History of the Root Server System · [RSSAC024]: Key Technical Elements of Potential Root Operators · [RSSAC025]: Root Server System Advisory Committee October 2016 Workshop Report · Security and Stability Advisory Committee (SSAC) Update · [SAC091]: Security and Stability Advisory Committee Comment on Identifier Technology Health Indicators (20 January 2017) · [SAC090]: Security and Stability Advisory Committee Advisory on the Stability of the Domain Namespace (22 December 2016) · [SAC089]: Security and Stability Advisory Committee Response to ccNSO Comments on SAC084 (12 December 2016) The open house will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here<https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Team looks forward to assisting the ICANN community prepare for ICANN58! Please register via this form<https://goo.gl/vZw8kM> by 3 March 2017!

1 0

UPCOMING Public Comment Period - FY18 Operating Plan and Budget
by Nathalie Peregrine Feb. 27, 2017

Feb. 27, 2017

FYI Dear ICANN Community Members, As planned, the publication of the draft FY18 Operating Plan and Budget is upcoming, and intended for 7 Mar 2017, in line with our objective of having the document posted before ICANN 58. The public comment period will run for 51 days and end 28 April 2017. We will email an announcement once the document has been posted. We look forward to your participation and comments. Additionally, we would like to bring to your attention the upcoming Budget Working Group and Financial Accountability sessions at ICANN 58 in Copenhagen. Please see the session details below along with links to sign up online and/or participate remotely. If you know of additional community members who may be interested in attending, please feel free to forward this information to them. Attached are iCal appointments for easy addition to your calendars. Thank you and we hope to see you in Copenhagen. Budget Working Group 14 March 2017 5pm-8pm (16:00 UTC) Location: MR 5 (Limited Space) http://sched.co/9nmS[sched.co]<https://urldefense.proofpoint.com/v2/url?u=http-3A__sched.co_9nmS&d=DwMFAg&…> Financial Accountability: Operating Plan and Budget 16 March 2017 9am-1030am (08:00 UTC) Location: Hall A3 http://sched.co/9noC[sched.co]<https://urldefense.proofpoint.com/v2/url?u=http-3A__sched.co_9noC&d=DwMFAg&…> For the FY18 Planning Team (Becky Nash, Taryn Presley, Kirsten Wattson, Leo Vegoda, Anand Mishra) Jessica Castillo Operations & Project Coordinator ICANN | Human Resources & Finance Departments P: (310) 301-3897 (Direct) | M: (424) 316-9545 E: jessica.castillo(a)icann.org<mailto:jessica.castillo@icann.org> | www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFAg…> 12025 Waterfront Drive, Ste 300, Los Angeles, CA 90094

1 0

Draft Minutes Meeting of the GNSO Council 16 February 2017 to review
by Nathalie Peregrine Feb. 27, 2017

Feb. 27, 2017

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 16 February 2017 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 8th March 2017. Thank you very much. Kind regards,

1 0

RDS Scope Guidance
by James M. Bladel Feb. 25, 2017

Feb. 25, 2017

Councilors – Attached, please find a draft RDS Scope Guidance document, which consolidates the feedback received from all SOs and ACs on guidance/recommendations to limit the scope of the upcoming RDS (WHOIS) review. Time is tight, so if you have any comments or edits, please respond by 2000 UTC this Friday 24 FEB. Once completed, the RDS Scope Guidance document will be distributed to RDS Review Team applicants, to confirm that they are still interested in serving on this review team. There is also a proposal to extend the call for applications until 7 MAR. Thank you, J.

2 2