November 2014 - council - lists.icann.org

RE: [council] FW: NomCom appointee skill sets
by Winterfeldt, Brian J. May 7, 2015

May 7, 2015

Dear all: Based on recommendations by others, and a shift from the ambiguous to the explicit, I note that intellectual property law is absent from the criteria. Accordingly I would ask for the following amendment.  International law  Competition law  Intellectual property law  Public interest issues  Consumer rights  Human rights  Economics, especially market analysis  Market mechanisms and dynamics  Business principles Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 575 Madison Avenue / New York, NY 10022-2585 p / (212) 940.6762 f / (212) 894.5585 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> ________________________________________ From: owner-council(a)gnso.icann.orgOn<mailto:owner-council@gnso.icann.orgOn> Behalf OfVolker Greimann Sent: Thursday, October 30, 2014 8:43:28 AM (UTC-05:00) Eastern Time (US & Canada) To: David Cake; jrobinson(a)afilias.info<mailto:jrobinson@afilias.info> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] FW: NomCom appointee skill sets I agree with David's suggested additions. instead of financial services businesses, general business experience may be more appropriate. Volker Am 30.10.2014 07:15, schrieb David Cake: > I would consider adding to the list of variable criteria: > - data protection and privacy law > - broader internet governance activities > > I'm also not sure why 'the special needs of financial services businesses' is on that list - not that I have a strong objection to anyone having this expertise, but I do not recall any item of council business having looked at this area in the last couple of years (though it is possible something is slipping my mind). > > David > > On 30 Oct 2014, at 10:02 am, Jonathan Robinson <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> wrote: > >> <NomCom - GNSO Candidate Criteria.docx> -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> Web: www.key-systems.net<http://www.key-systems.net> / www.RRPproxy.net<http://www.RRPproxy.net> www.domaindiscount24.com<http://www.domaindiscount24.com> / www.BrandShelter.com<http://www.BrandShelter.com> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems<http://www.facebook.com/KeySystems> www.twitter.com/key_systems<http://www.twitter.com/key_systems> Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu<http://www.keydrive.lu> Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> Web: www.key-systems.net<http://www.key-systems.net> / www.RRPproxy.net<http://www.RRPproxy.net> www.domaindiscount24.com<http://www.domaindiscount24.com> / www.BrandShelter.com<http://www.BrandShelter.com> Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems<http://www.facebook.com/KeySystems> www.twitter.com/key_systems<http://www.twitter.com/key_systems> CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu<http://www.keydrive.lu> This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone. =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). ===========================================================

14 28

Name Collision - staff expert participation required?
by Marika Konings Dec. 8, 2014

Dec. 8, 2014

Dear All, In relation to agenda item 6 name collision (see below), Fransisco Arias has indicated that he is available to join the Council meeting tomorrow should there be any further questions in relation to the staff paper or other technical questions relating to this issue. If you anticipate that his input may be required to help inform the Council deliberations on what further action, if any, should be taken on this topic, please let me know (off-list) by today 20.00 UTC at the latest so I can inform him accordingly. Of course, should any questions arise during the meeting that were not originally anticipated, we can always pass these on after the meeting for a response. Best regards, Marika Item 6: UPDATE Name Collision (15 mins) On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." ICANN Staff submitted this paper to the GNSO Council on 7 October 2014 (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oct 14-en.pdf) and it was presented to the Council during the ICANN meeting in Los Angeles. Council members agreed in Los Angeles to discuss with their respective group what further action, if any, should be taken on this topic and report back accordingly during this meeting. Furthermore, a letter <http://gnso.icann.org/en/correspondence/namazi-to-robinson-30oct14-en.pdf> was received from Cyrus Namazi offering any additional information or assistance that ICANN Staff can provide to further assist the Council in its deliberations. This is an opportunity for the Council to discuss which steps, if any, it would like to take in relation to this topic. 6.1 Discussion 6.2 Next steps

2 1

Draft minutes GNSO Council meeting 13 November 2014
by Glen de Saint Géry Nov. 27, 2014

Nov. 27, 2014

Dear Councillors, Attached, please find the draft minutes of the GNSO Council meeting on 13 November 2014 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 <http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 7 December 2014. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Draft minutes GNSO Council Public administrative meeting LA 15 October 2014
by Glen de Saint Géry Nov. 27, 2014

Nov. 27, 2014

Dear Councillors, Attached, please find the draft minutes of the GNSO Council Public administrative meeting of the new Council in Los Angeles on 15 October 2014 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 <http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 7 December 2014. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/> From: Glen de Saint Géry Sent: mercredi 26 novembre 2014 23:52 To: Jonathan Robinson; Volker Greimann (vgreimann(a)key-Systems.net) David Cake (dave(a)difference.com.au) (dave(a)difference.com.au) Cc: Glen de Saint Géry; gnso-secs(a)icann.org Subject: Draft minutes GNSO Council Public meeting LA & 13 November 2014 for review Dear Jonathan, Volker and David, Please be so kind as to review these minutes so that they can be published on the Council mailing list for approval after 10 days if there are no comments. Thank you so much. Kind regards, Glen From: Glen de Saint Géry Sent: mercredi 12 novembre 2014 20:52 To: David Cake (dave(a)difference.com.au<mailto:dave@difference.com.au>) (dave(a)difference.com.au<mailto:dave@difference.com.au>); Volker Greimann (vgreimann(a)key-Systems.net<mailto:vgreimann@key-Systems.net>) Cc: jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>; Glen de Saint Géry; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: FW: Draft minutes GNSO Council Public meeting LA for review Dear David and Volker, In Jonathan's absence, would you please be so kind as to go through these with a fine comb and let me know what changes you would like made. Jonathan always has heaps! Thank you so much. All the best Glen From: Glen de Saint Géry Sent: vendredi 7 novembre 2014 16:43 To: Jonathan Robinson; David Cake (dave(a)difference.com.au<mailto:dave@difference.com.au>) (dave(a)difference.com.au<mailto:dave@difference.com.au>); Volker Greimann (vgreimann(a)key-Systems.net<mailto:vgreimann@key-Systems.net>) Cc: Glen de Saint Géry; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Draft minutes GNSO Council Public meeting LA for review Dear Jonathan, David and Volker, Attached are the draft minutes from the LA Council meeting for your review. Please let me know if you would like any changes made. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Draft minutes GNSO Council Public meeting LA 15 October 2014
by Glen de Saint Géry Nov. 27, 2014

Nov. 27, 2014

Dear Councillors, Attached, please find the draft minutes of the GNSO Council Public meeting on 15 October 2014 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 <http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 7 December 2014. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Informal notes GNSO Council Development Session
by Marika Konings Nov. 27, 2014

Nov. 27, 2014

Dear All, As discussed during the last GNSO Council meeting, please find attached the informal notes of the GNSO Council Development session that was held in Los Angeles on 17 October 2014. Best regards, Marika

1 0

Document and Motion deadline Monday,1 December 2014 at 23:59 UTC for Council meeting 11 December 2014 at 15:00 UTC
by Glen de Saint Géry Nov. 26, 2014

Nov. 26, 2014

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 1 December 2014 at 23:59 UTC) of the GNSO Council meeting on 11 December 2014 at 15:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+11+December… Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Volunteers for Charter for a Cross Community Working Group on Enhancing ICANN Accountability
by Glen de Saint Géry Nov. 24, 2014

Nov. 24, 2014

Dear All, As per the Council resolution passed on the adoption of a Charter for a Cross Community Working Group on Enhancing ICANN Accountability, please be reminded that "Each GNSO Stakeholder Group should identify one member for the CWG by 20 November 2014 taking into account the charter requirement. Best efforts should be made to ensure that individual members: * Have sufficient expertise to participate in the applicable subject matter (see for example https://www.icann.org/resources/pages/enhancing-accountability-faqs-2014-08… for areas identified for expertise); * Commit to actively participate in the activities of the CCWG-Accountability on an ongoing and long-term basis; and * Where appropriate, solicit and communicate the views and concerns of individuals in the organization that appoints them. Please provide names by COB today. If you have already and this has been missed, apologies and please resend. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Annex A to the resolution on Planning for Future gTLD Application Rounds
by Bruce Tonkin Nov. 22, 2014

Nov. 22, 2014

From: https://www.icann.org/en/system/files/files/resolutions-annex-a-17nov14-en.… I have attached Annex A from the resolution on Planning for Future gTLD Application Rounds. Regards, Bruce Tonkin On Nov 21, 2014, at 5:47 AM, Bruce Tonkin wrote: > > From: https://www.icann.org/resources/board-material/resolutions-2014-11-17-en > > > > 1. Consent Agenda: > > a. Approval of Board Meeting Minutes > > Resolved (2014.11.17.01), the Board approves the minutes of its 16 and 28 October 2014 meetings. > > > b. Appointment of B-, C-, F-, and K- Root Server Operator Representatives to the RSSAC > > Whereas, the ICANN Bylaws call for the establishment of a Root Server System Advisory Committee (RSSAC) with the role to advise the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System. > > Whereas, the ICANN Bylaws call for Board appointment of RSSAC members based on recommendations from the RSSAC co-chairs. > > Whereas, the RSSAC co-chairs recommended for Board consideration appointments to the RSSAC to represent the B-root, C-root, F-root, and K-root server operators. > > Resolved (2014.11.17.02), the Board appoints the representatives for B-root, C-root, and K-root server operators, Bill Manning, Paul Vixie, Daniel Karrenberg, respectively, through 31 December 2017 and the representative for F-root server operator, Jim Martin, through 31 December 2015 to the Root Server System Advisory Committee. > > > > c. SSAC Advisory on DNS "Search List" Processing and DDos Attacks Leveraging DNS Infrastructure > > Whereas, in February 2014, the ICANN Security and Stability Advisory Committee (SSAC) published SAC064 [PDF, 931 KB]: SSAC Advisory on DNS "Search List" Processing and SAC065 [PDF, 423 KB]: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure. > > Whereas, in SAC 064, the advice highlights some of the DNS "search list" processing behavior presents security and privacy issues to end systems, lead to performance problems for the Internet, and might cause collision with names provisioned under the newly delegated top-level domains. > > Whereas, in SAC 065, the advice recommends ICANN and operators of Internet infrastructure and manufacturers to take action to address the unresolved critical design and deployment issues that have enabled increasingly large and severe Distributed Denial of Service (DDoS) attacks using the DNS. > > Whereas, while in some instances SAC 064 and SAC 065 call for actions not under ICANN's control and actors not necessarily within ICANN's usual community, they are meant to address the overall responsibilities of the multi-stakeholder community and encourage ICANN to take action where it is relevant to do so. > > Whereas, ensuring the stable and secure operation of the Internet's system of unique identifiers is part of ICANN's mission; preserving and enhancing the operational stability, reliability, security, and global interoperability of the Internet part of ICANN's core value; and ensuring the introduction of new gTLDs in a secure and stable manner is a strategic priority for ICANN. > > Resolved (2014.11.17.03), the Board acknowledges the receipt of SAC064: SSAC Advisory on Search List Processing, and SAC065: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure. > > Resolved (2014.11.17.04), the Board directs the President and CEO, or his designee(s), to evaluate the advice provided in SAC064 and SAC 065. > > Resolved (2014.11.17.05), in the instances where it is recommended that the advice be accepted, the Board directs the President and CEO, or his designee(s), to evaluate the feasibility and cost of implementing the advice, and provide an implementation plan with timelines and high-level milestones for review by the Board, no later than 120 days from the adoption of this resolution. > > > > d. Completion of the Address Supporting Organization (ASO) Organizational Review > > Whereas, ICANN Bylaws Article IV, Section 4 call for a "periodic review of the performance and operation of each Supporting Organization, each Supporting Organization Council, each Advisory Committee (other than the Governmental Advisory Committee), and the Nominating Committee by an entity or entities independent of the organization under review"; > > Whereas, the Number Resource Organization (NRO) "shall provide its own review mechanisms" in reference to periodic review of the ASO, based on the terms of the ICANN Address Supporting Organization (ASO) Memorandum of Understanding dated 21 October 2004; > > Whereas, the NRO completed the review of the ASO and the implementation work resulting from the recommendations offered by ITEMS International, the independent examiner engaged to conduct the ASO review. > > RESOLVED (2014.11.17.06) that the Board accepts the final report from the Number Resource Organization (NRO) issued in the form of a letter to the Chair of the Structural Improvements Committee in November 2013 regarding the completion of implementation work resulting from the ASO Review. The Board thanks the NRO for its work in conducting the review and acknowledges the completion of the implementation work resulting from the recommendations received by the NRO during the review. > > RESOLVED (2014.11.17.07) that the Board directs staff to provide support requested by the Chair of the NRO Executive Council, consisting of logistical staff support associated with ICANN meetings, allocation of time during ICANN meetings for ASO and NRO reports to the ICANN community, translation services and improved visibility on the ICANN web site. > > > > 2. Main Agenda: > > a. Meeting Strategy Working Group (MSWG) Recommendations Implementation Plan for 2016 > > Whereas, ICANN intends to hold meetings in 2016, 2017, 2018, 2019, and 2020. > > Whereas, the Meeting Strategy Working Group produced a Final Report of recommendations to improve the overall structure and format of ICANN Meetings and on 26 June 2014 received the Board's gratitude for conducting this review. > > Whereas, in furtherance of the Board's 26 June 2014, ICANN reviewed the MSWG Final Report and developed an implementation plan based on the recommendations within that Final Report, identifying implementation in the calendar year 2016. In addition, ICANN identifies a five (5) year schedule and regional rotation for ICANN Meetings through 2020. > > Whereas, the five year schedule reflects the MSWG recommendations for timing and duration of ICANN Public Meetings. > > Resolved (2014.11.17.08), the Board accepts all MSWG recommendations and directs the President and CEO, through his designee(s), to proceed with implementation. For recommendations on meeting support and engagement activities, focusing on technical support for remote participants and easing of future visa attainment for attendees, the Board directs the President and CEO to provide required support to obtain relevant metrics on recurring attendees. > > Resolved (2014.11.17.09), the Board accepts the dates of Meetings to be held in 2016, 2017, 2018, 2019, and 2020 as set forth in Annex 1 to this Resolution. > > > b. Planning for Future gTLD Application Rounds > > Whereas, the New gTLD Program was developed and implemented based on consensus policy recommendations from the GNSO; > > Whereas, ICANN undertook thorough consultation with the global stakeholder community in the development of the application and evaluation processes in the New gTLD Applicant Guidebook ("Applicant Guidebook"); > > Whereas, the GNSO policy recommendations provide that applications for new gTLDs should continue to be accepted in rounds; > > Whereas, the Board has reaffirmed its commitment to opening a subsequent application round in a timely manner; > > Whereas, the Board wishes to set the continuing direction for the New gTLD Program; > > Whereas, ICANN is committed to executing a number of reviews as part of moving forward with subsequent rounds of the New gTLD Program; > > Whereas, the Board wishes to ensure that the GNSO's deliberations on policy applicable to future rounds includes consideration of potential policy issues that were not addressed by the GNSO's 2007 policy recommendations, including issues that the NGPC was called on to address as implementation issues; > > Resolved (2014.11.17.10), the Board directs the staff to continue working with the community to refine the work plan for executing all required reviews of the New gTLD Program and to provide regular updates to the community on the status and timeframes of review activities. > > Resolved (2014.11.17.11), the Board notes the effort in progress within the GNSO to identify areas where the GNSO believes that policy advice can be clarified or where it wishes to provide additional policy advice applicable to future application rounds, and looks forward to the results of this work, to ensure that key policy areas are addressed for future rounds. > > Resolved (2014.11.17.xx), the Board notes that the GNSO has invited the NGPC to provide input to the GNSO Council to identify areas that may be appropriate for discussion for an evaluation of the current gTLD application round and for possible adjustments for subsequent application procedures. The Board appreciates the request and has identified, in addition to the GNSO analysis of the Applicant Guidebook and the current application round, a set of topics (included as Annex A) that may be appropriate for discussion by the GNSO. > > > c. ICANN 53 Meeting Location > > No resolution taken. > > > Mason Cole VP Communications & Industry Relations Donuts Inc. ................................................ mason(a)donuts.co Ofc +1 503 908 7623 Cell +1 503 407 2555

1 0

Preliminary Report from ICANN Board meeting 17 Nov 2014
by Bruce Tonkin Nov. 21, 2014

Nov. 21, 2014

From: https://www.icann.org/resources/board-material/resolutions-2014-11-17-en 1. Consent Agenda: a. Approval of Board Meeting Minutes Resolved (2014.11.17.01), the Board approves the minutes of its 16 and 28 October 2014 meetings. b. Appointment of B-, C-, F-, and K- Root Server Operator Representatives to the RSSAC Whereas, the ICANN Bylaws call for the establishment of a Root Server System Advisory Committee (RSSAC) with the role to advise the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System. Whereas, the ICANN Bylaws call for Board appointment of RSSAC members based on recommendations from the RSSAC co-chairs. Whereas, the RSSAC co-chairs recommended for Board consideration appointments to the RSSAC to represent the B-root, C-root, F-root, and K-root server operators. Resolved (2014.11.17.02), the Board appoints the representatives for B-root, C-root, and K-root server operators, Bill Manning, Paul Vixie, Daniel Karrenberg, respectively, through 31 December 2017 and the representative for F-root server operator, Jim Martin, through 31 December 2015 to the Root Server System Advisory Committee. c. SSAC Advisory on DNS "Search List" Processing and DDos Attacks Leveraging DNS Infrastructure Whereas, in February 2014, the ICANN Security and Stability Advisory Committee (SSAC) published SAC064 [PDF, 931 KB]: SSAC Advisory on DNS "Search List" Processing and SAC065 [PDF, 423 KB]: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure. Whereas, in SAC 064, the advice highlights some of the DNS "search list" processing behavior presents security and privacy issues to end systems, lead to performance problems for the Internet, and might cause collision with names provisioned under the newly delegated top-level domains. Whereas, in SAC 065, the advice recommends ICANN and operators of Internet infrastructure and manufacturers to take action to address the unresolved critical design and deployment issues that have enabled increasingly large and severe Distributed Denial of Service (DDoS) attacks using the DNS. Whereas, while in some instances SAC 064 and SAC 065 call for actions not under ICANN's control and actors not necessarily within ICANN's usual community, they are meant to address the overall responsibilities of the multi-stakeholder community and encourage ICANN to take action where it is relevant to do so. Whereas, ensuring the stable and secure operation of the Internet's system of unique identifiers is part of ICANN's mission; preserving and enhancing the operational stability, reliability, security, and global interoperability of the Internet part of ICANN's core value; and ensuring the introduction of new gTLDs in a secure and stable manner is a strategic priority for ICANN. Resolved (2014.11.17.03), the Board acknowledges the receipt of SAC064: SSAC Advisory on Search List Processing, and SAC065: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure. Resolved (2014.11.17.04), the Board directs the President and CEO, or his designee(s), to evaluate the advice provided in SAC064 and SAC 065. Resolved (2014.11.17.05), in the instances where it is recommended that the advice be accepted, the Board directs the President and CEO, or his designee(s), to evaluate the feasibility and cost of implementing the advice, and provide an implementation plan with timelines and high-level milestones for review by the Board, no later than 120 days from the adoption of this resolution. d. Completion of the Address Supporting Organization (ASO) Organizational Review Whereas, ICANN Bylaws Article IV, Section 4 call for a "periodic review of the performance and operation of each Supporting Organization, each Supporting Organization Council, each Advisory Committee (other than the Governmental Advisory Committee), and the Nominating Committee by an entity or entities independent of the organization under review"; Whereas, the Number Resource Organization (NRO) "shall provide its own review mechanisms" in reference to periodic review of the ASO, based on the terms of the ICANN Address Supporting Organization (ASO) Memorandum of Understanding dated 21 October 2004; Whereas, the NRO completed the review of the ASO and the implementation work resulting from the recommendations offered by ITEMS International, the independent examiner engaged to conduct the ASO review. RESOLVED (2014.11.17.06) that the Board accepts the final report from the Number Resource Organization (NRO) issued in the form of a letter to the Chair of the Structural Improvements Committee in November 2013 regarding the completion of implementation work resulting from the ASO Review. The Board thanks the NRO for its work in conducting the review and acknowledges the completion of the implementation work resulting from the recommendations received by the NRO during the review. RESOLVED (2014.11.17.07) that the Board directs staff to provide support requested by the Chair of the NRO Executive Council, consisting of logistical staff support associated with ICANN meetings, allocation of time during ICANN meetings for ASO and NRO reports to the ICANN community, translation services and improved visibility on the ICANN web site. 2. Main Agenda: a. Meeting Strategy Working Group (MSWG) Recommendations Implementation Plan for 2016 Whereas, ICANN intends to hold meetings in 2016, 2017, 2018, 2019, and 2020. Whereas, the Meeting Strategy Working Group produced a Final Report of recommendations to improve the overall structure and format of ICANN Meetings and on 26 June 2014 received the Board's gratitude for conducting this review. Whereas, in furtherance of the Board's 26 June 2014, ICANN reviewed the MSWG Final Report and developed an implementation plan based on the recommendations within that Final Report, identifying implementation in the calendar year 2016. In addition, ICANN identifies a five (5) year schedule and regional rotation for ICANN Meetings through 2020. Whereas, the five year schedule reflects the MSWG recommendations for timing and duration of ICANN Public Meetings. Resolved (2014.11.17.08), the Board accepts all MSWG recommendations and directs the President and CEO, through his designee(s), to proceed with implementation. For recommendations on meeting support and engagement activities, focusing on technical support for remote participants and easing of future visa attainment for attendees, the Board directs the President and CEO to provide required support to obtain relevant metrics on recurring attendees. Resolved (2014.11.17.09), the Board accepts the dates of Meetings to be held in 2016, 2017, 2018, 2019, and 2020 as set forth in Annex 1 to this Resolution. b. Planning for Future gTLD Application Rounds Whereas, the New gTLD Program was developed and implemented based on consensus policy recommendations from the GNSO; Whereas, ICANN undertook thorough consultation with the global stakeholder community in the development of the application and evaluation processes in the New gTLD Applicant Guidebook ("Applicant Guidebook"); Whereas, the GNSO policy recommendations provide that applications for new gTLDs should continue to be accepted in rounds; Whereas, the Board has reaffirmed its commitment to opening a subsequent application round in a timely manner; Whereas, the Board wishes to set the continuing direction for the New gTLD Program; Whereas, ICANN is committed to executing a number of reviews as part of moving forward with subsequent rounds of the New gTLD Program; Whereas, the Board wishes to ensure that the GNSO's deliberations on policy applicable to future rounds includes consideration of potential policy issues that were not addressed by the GNSO's 2007 policy recommendations, including issues that the NGPC was called on to address as implementation issues; Resolved (2014.11.17.10), the Board directs the staff to continue working with the community to refine the work plan for executing all required reviews of the New gTLD Program and to provide regular updates to the community on the status and timeframes of review activities. Resolved (2014.11.17.11), the Board notes the effort in progress within the GNSO to identify areas where the GNSO believes that policy advice can be clarified or where it wishes to provide additional policy advice applicable to future application rounds, and looks forward to the results of this work, to ensure that key policy areas are addressed for future rounds. Resolved (2014.11.17.xx), the Board notes that the GNSO has invited the NGPC to provide input to the GNSO Council to identify areas that may be appropriate for discussion for an evaluation of the current gTLD application round and for possible adjustments for subsequent application procedures. The Board appreciates the request and has identified, in addition to the GNSO analysis of the Applicant Guidebook and the current application round, a set of topics (included as Annex A) that may be appropriate for discussion by the GNSO. c. ICANN 53 Meeting Location No resolution taken.

3 3