September 2017 - council - lists.icann.org

Follow up on proposed revisions to GNSO Operating Procedures and ICANN Bylaws
by Marika Konings Oct. 11, 2017

Oct. 11, 2017

Dear All, Following up on the update on the revised GNSO Operating Procedures and ICANN Bylaws that was provided during the last meeting (see https://gnso.icann.org/en/drafts/gop-bylaws-20sep17-en.pdf) I wanted to highlight that even though the staff report is long and addresses all the post-transition Bylaw changes and how these have been addressed as a result of the Bylaws DT recommendations, the actual changes to the GNSO Operating Procedures and the ICANN Bylaws are fairly limited. As such, I would recommend that you review the attached redline versions so that you get a better sense of the changes that are being proposed. To summarize, the redline includes: 1. Changes to section 11.3.i of the ICANN Bylaws to reflect new GNSO voting thresholds1<https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en#foot1>which are different from the current threshold of a simple majority vote of each House. 2. Changes to the GNSO Operating Procedures, section 4.9 (Consent Agenda) to reflect that certain decisions are to be confirmed "automatically" by the GNSO Council through its consent agenda. 3. Addition to the GNSO Operating Procedures to clarify that in specific circumstances, the GNSO Council may waive the timeframes currently referenced in the GNSO Operating Procedures in relation to submission of motions as well as scheduling of meetings to meet its obligations under the timelines outlined in the ICANN Bylaws as a Decisional Participant. 4. Addition to the GNSO Operating Procedures to clarify that certain petitions submitted by an individual must be submitted through a GNSO Stakeholder Group or Constituency to the GNSO Council for consideration. For this purpose, each GNSO Stakeholder Group and Constituency must develop clear rules for the submission of such petitions, including any requirements for the criteria to be included in a petition. These rules would be added to the GNSO Operating Procedures as an annex once available. 5. Addition to the GNSO Operating Procedures to clarify that all petitions concerning a director removal process submitted by an individual must be submitted directly to the GNSO Council. For this purpose, the GNSO Council will develop a clear process and rules for the submission of such petitions, including any requirements for the criteria to be included in a petition. These rules would be added to the GNSO Operating Procedures as an annex once available. In addition to these modifications, the redline version also includes the following updates: * Updated references to the ICANN Bylaws as many changed as a result of the post-transition Bylaws; * Updated the generalized schedule for board elections to align it with the timing as well as notification requirements outlined in the post-transition Bylaws; * Included references to the Governmental Advisory Committee (GAC) Quick Look Mechanism in the PDP Manual as a result of the GAC-GNSO Consultation Group recommendations, and; * Included references to the inclusion of a draft PDP WG Charter in the Preliminary Issue Report in the PDP Manual as a result of the GNSO Improvements recommendations. As noted during my presentation during the last Council meeting, in response to the public comments provided, staff would suggest making the following updates: * In relation to the waiver for petitions and the suggestion by the IPC that any recommendations in this regard are unanimously taken by the GNSO Chair and Council Vice-Chairs, staff notes that the proposed language reads ‘as recommended by the GNSO Chair and Council Vice-Chairs’ which implies that this is a unanimous recommendation. However, should there be a desire to explicitly state this assumption, the following wording could be considered ‘as recommended unanimously by the GNSO Chair and Council Vice-Chairs’. * Clarifying the voting results table in Appendix 1 with regards to approval of a petition and approval of a petition notice to remove a director holding seat 13 or 14 by changing >75% of one to >75% of the House that appointed the Director As pointed out during the meeting, until such time the GNSO Council adopts the revised GNSO Operating Procedures and ICANN Bylaws the existing rules apply to any actions and/or decisions related to the GNSO as a member of the Empowered Community. If it would be helpful, staff would be more than willing to schedule a separate call to go through the proposed changes as well as any questions you may have. Just let us know and we can schedule accordingly. 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-…>.

3 2

Fwd: Please find "What's New with Reviews" published by Theresa Swinehart
by James M. Bladel Sept. 29, 2017

Sept. 29, 2017

Councilors, for your review. Please distribute to your SG/C. Thank you, J. ————— James Bladel GNSO Chair ---------- Forwarded message ---------- From: Sherwood Moore <sherwood.moore(a)icann.org> Date: Sep 29, 2017, 02:06 +0200 Subject: Please find "What's New with Reviews" published by Theresa Swinehart Dear SO / AC Leadership, With so many reviews currently active, Theresa Swinehart has published the third iteration of “What’s New with Reviews”<https://www.icann.org/news/blog/what-s-new-with-reviews> to share areas where community participation is needed. Please read the blog and help us by sharing with your community. You can find the announcement here: https://www.icann.org/news/blog/what-s-new-with-reviews . Thank you ahead of time for your support! Sherwood Moore Senior Project Manager, Strategic Communication & Community Engagement

1 0

ICANN News Alert -- KSK Rollover Postponed
by Nathalie Peregrine Sept. 29, 2017

Sept. 29, 2017

[ANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2017-09-27-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ KSK Rollover Postponed 27 September 2017 The Internet Corporation for Assigned Names and Numbers ("ICANN") today announced that the plan to change the cryptographic key[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> that helps protect the Domain Name System (DNS) is being postponed. Changing the key involves generating a new cryptographic key pair and distributing the new public component to the Domain Name System Security Extensions (DNSSEC)-validating resolvers. Based on the estimated number of Internet users who use DNSSEC validating resolvers, an estimated one-in-four global Internet users, or 750 million people, could be affected by the KSK rollover. The changing or "rolling" of the KSK Key was originally scheduled to occur on 11 October, but it is being delayed because some recently obtained data shows that a significant number of resolvers used by Internet Service Providers (ISPs) and Network Operators are not yet ready for the Key Rollover. The availability of this new data is due to a very recent DNS protocol feature that adds the ability for a resolver to report back to the root servers which keys it has configured. There may be multiple reasons why operators do not have the new key installed in their systems: some may not have their resolver software properly configured and a recently discovered issue in one widely used resolver program appears to not be automatically updating the key as it should, for reasons that are still being explored. ICANN is reaching out to its community, including its Security and Stability Advisory Committee, the Regional Internet Registries, Network Operator Groups and others to help explore and resolve the issues. In the meantime, ICANN believes it prudent to follow its process and to delay the changing of the key rather than run the risk of a significant number of Internet users being adversely affected by the changing of the key. ICANN is committed to continuing its education, communication and engagement with the relevant technical organizations to ensure readiness for the key change. "The security, stability and resiliency of the domain name system is our core mission. We would rather proceed cautiously and reasonably, than continue with the roll on the announced date of 11 October," said Göran Marby. "It would be irresponsible to proceed with the roll after we have identified these new issues that could adversely affect its success and could adversely affect the ability of a significant number of end users." A new date for the Key Roll has not yet been determined. ICANN's Office of the Chief Technology Officer says it is tentatively hoping to reschedule the Key Roll for the first quarter of 2018, but that it will be dependent on more fully understanding the new information and mitigating as many potential failures as possible. ICANN will provide additional information as it becomes available and the new Key Roll date will be announced as appropriate. "It's our hope that network operators will use this additional time period to be certain that their systems are ready for the Key Roll," said Marby. "Our testing platform (http://go.icann.org/KSKtest[go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_KSKtest&d=…>) will help operators ensure that their resolvers are properly configured with the new key and we will continue our engagement and communications to these operators." About DNSSEC To easily identify resources on the Internet, the underlying numerical addresses for these resources are represented by human readable strings. The conversion of these strings to numbers is done by the distributed hierarchical Domain Name System (DNS). Increased sophistication in computing and networking since its design in 1983 have made this "phone book" vulnerable to attacks. In response to these threats, the international standards organization, IETF[ietf.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_&d=DwMFaQ&…>, developed DNSSEC to cryptographically ensure DNS content cannot be modified from its source without being detected. Once fully deployed, DNSSEC will stop the attacker's ability to redirect users using the DNS. ## To keep informed about KSK Rollover developments go here: https://www.icann.org/resources/pages/ksk-rollover[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> On social media use: #Keyroll

2 1

Fwd: [So-ac-sg-cleaders] KSK Rollover Postponed - ICANN
by James M. Bladel Sept. 29, 2017

Sept. 29, 2017

Councilors - You’ve probably already seen some tweets/industry news on the KSK rollover postponement, but here’s the official announcement. Thank you, J. ----------------- James Bladel GNSO Chair ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Sep 28, 2017, 19:48 +0200 To: so-ac-sg-cleaders(a)icann.org <so-ac-sg-cleaders(a)icann.org> Subject: [So-ac-sg-cleaders] KSK Rollover Postponed - ICANN https://www.icann.org/news/announcement-2017-09-27-en KSK Rollover Postponed This page is available in: * Português<http://www.icann.org/news/announcement-2017-09-27-pt> * Pусский<http://www.icann.org/news/announcement-2017-09-27-ru> * Español<http://www.icann.org/news/announcement-2017-09-27-es> * Français<http://www.icann.org/news/announcement-2017-09-27-fr> * 中文<http://www.icann.org/news/announcement-2017-09-27-zh> * العربية<http://www.icann.org/news/announcement-2017-09-27-ar> * English The Internet Corporation for Assigned Names and Numbers ("ICANN") today announced that the plan to change the cryptographic key<https://www.icann.org/resources/pages/ksk-rollover/#overview> that helps protect the Domain Name System (DNS) is being postponed. Changing the key involves generating a new cryptographic key pair and distributing the new public component to the Domain Name System Security Extensions (DNSSEC)-validating resolvers. Based on the estimated number of Internet users who use DNSSEC validating resolvers, an estimated one-in-four global Internet users, or 750 million people, could be affected by the KSK rollover. The changing or "rolling" of the KSK Key was originally scheduled to occur on 11 October, but it is being delayed because some recently obtained data shows that a significant number of resolvers used by Internet Service Providers (ISPs) and Network Operators are not yet ready for the Key Rollover. The availability of this new data is due to a very recent DNS protocol feature that adds the ability for a resolver to report back to the root servers which keys it has configured. There may be multiple reasons why operators do not have the new key installed in their systems: some may not have their resolver software properly configured and a recently discovered issue in one widely used resolver program appears to not be automatically updating the key as it should, for reasons that are still being explored. ICANN is reaching out to its community, including its Security and Stability Advisory Committee, the Regional Internet Registries, Network Operator Groups and others to help explore and resolve the issues. In the meantime, ICANN believes it prudent to follow its process and to delay the changing of the key rather than run the risk of a significant number of Internet users being adversely affected by the changing of the key. ICANN is committed to continuing its education, communication and engagement with the relevant technical organizations to ensure readiness for the key change. "The security, stability and resiliency of the domain name system is our core mission. We would rather proceed cautiously and reasonably, than continue with the roll on the announced date of 11 October," said Göran Marby. "It would be irresponsible to proceed with the roll after we have identified these new issues that could adversely affect its success and could adversely affect the ability of a significant number of end users." A new date for the Key Roll has not yet been determined. ICANN's Office of the Chief Technology Officer says it is tentatively hoping to reschedule the Key Roll for the first quarter of 2018, but that it will be dependent on more fully understanding the new information and mitigating as many potential failures as possible. ICANN will provide additional information as it becomes available and the new Key Roll date will be announced as appropriate. "It's our hope that network operators will use this additional time period to be certain that their systems are ready for the Key Roll," said Marby. "Our testing platform (http://go.icann.org/KSKtest) will help operators ensure that their resolvers are properly configured with the new key and we will continue our engagement and communications to these operators." About DNSSEC To easily identify resources on the Internet, the underlying numerical addresses for these resources are represented by human readable strings. The conversion of these strings to numbers is done by the distributed hierarchical Domain Name System (DNS). Increased sophistication in computing and networking since its design in 1983 have made this "phone book" vulnerable to attacks. In response to these threats, the international standards organization, IETF<http://www.ietf.org/>, developed DNSSEC to cryptographically ensure DNS content cannot be modified from its source without being detected. Once fully deployed, DNSSEC will stop the attacker's ability to redirect users using the DNS. ## To keep informed about KSK Rollover developments go here: https://www.icann.org/resources/pages/ksk-rollover David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Fwd: Appointment of Cheryl Langdon-Orr as Co-Chair of Subsequent Procedures PDP
by James M. Bladel Sept. 29, 2017

Sept. 29, 2017

Councilors, see message from Jeff Neuman, below. If there are no objections, I would like to propose that we add approval of Cheryl’s appointment, and a thank you message to Avri, to the Consent Agenda for our next meeting on 12 OCT. If you have concerns, would like to discuss, or would prefer this be considered as a formal motion, please respond to this note in the next day or so, and we’ll draw that up. Thank you, J. ----------------- James Bladel GNSO Chair ---------- Forwarded message ---------- From: Jeff Neuman <jeff.neuman(a)comlaude.com> Subject: Appointment of Cheryl Langdon-Orr as Co-Chair of Subsequent Procedures PDP Dear GNSO Council Leadership team, As you know, we will be losing Avri as a co-chair of the Subsequent Procedures PDP Working Group at the close of the annual meeting in Abu Dhabi. Avri will continue to participate in the Working Group which is fantastic, but understandably is stepping down as co-chair. We are happy to report that Cheryl Langdon-Orr has been nominated by the Working Group and overwhelmingly supported by the members as well as the current leadership of the PDP Working Group. According to either the bylaws or the GNSO Operating Procedures, Co-Leadership of the overall Working Groups need to be approved by the GNSO Council. So, I am formally requesting that this be placed on the agenda for the next council call (hopefully the consent agenda). Paul, as the GNSO Council Liaison, can I request that you formally make the motion? I know the deadline for motions is approaching fairly soon for your next meeting. We would love to have Cheryl in place and active as a co-chair in the Abu Dhabi meeting. Please let me know what if anything else I need to do. Thanks! Best regards, Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514<tel:+1.703.635.7514> M: +1.202.549.5079<tel:+1.202.549.5079> @Jintlaw

1 0

Deadline update: Draft minutes of the GNSO Council meeting on Wednesday 20 September 2017
by Nathalie Peregrine Sept. 28, 2017

Sept. 28, 2017

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 20 September 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 8 October 2017. Thank you very much. Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Draft minutes of the GNSO Council meeting on Wendesday 20 September 2017
by Nathalie Peregrine Sept. 28, 2017

Sept. 28, 2017

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 20 September 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 30 September 2017. Thank you very much. Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FYI - ICANN Webinar: Data Protection/Privacy Activities on 4 October at 14.00 UTC
by Marika Konings Sept. 28, 2017

Sept. 28, 2017

https://www.icann.org/news/announcement-2-2017-09-27-en ICANN Webinar: Data Protection/Privacy Activities LOS ANGELES – 27 Sept. 2017 – The Internet Corporation for Assigned Names and Numbers ("ICANN") invites you to join us in a webinar on 4 October 2017 from 1400 to 1500 UTC to discuss data protection/privacy activities related to the European Union's General Data Protection Regulation (GDPR)<http://ec.europa.eu/justice/data-protection/reform/index_en.htm>. We also welcome updates on the webinar from the community and community groups on their GDPR related activities. Topics of discussion will include: * ICANN's focus with respect to GDPR * Recap of recent activities * Personal data use matrix * Engagement activities * Update on legal analysis of matrix data * ICANN60 session in Abu Dhabi * Community updates on their GDPR activities In order to facilitate global participation, interpretation services will be available in Arabic, Chinese, French, Portuguese, Russian, and Spanish. Participants will have the opportunity to ask questions at the end of the session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. In advance of the webinar, questions may be submitted to gdpr-questions(a)icann.org<mailto:gdpr-questions@icann.org>. We will make every effort to answer the questions during the webinar or in an FAQ document to be circulated after the webinar. Please submit your requests no later than Monday, 2 October. A recording of the webinar will be made available for future reference. Webinar Details & How to Attend Date: 4 October 2017 Time: 1400 – 1500 UTC Join via Adobe Connect<https://participate.icann.org/webinar/> (please send dial-in requests to gdpr-questions(a)icann.org<mailto:gdpr-questions@icann.org>) View Dial-in Information<http://www.adigo.com/icann> Participant Codes: English – Participant Code: 9001 Français – Participant Code: 9002 Español – Participant Code: 9003 中文 – Participant Code: 9004 Pусский – Participant Code: 9005 العربية – Participant Code: 9006 Português – Participant Code: 9007 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

REMINDER Re: Call for Topics: GNSO & Board discussion ICANN60
by Marika Konings Sept. 28, 2017

Sept. 28, 2017

Reminder, please send in your proposed topics for the GNSO & Board discussion at ICANN60 as soon as possible. The deadline for submission has already passed. Thanks, Marika From: <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, September 15, 2017 at 09:23 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Call for Topics: GNSO & Board discussion ICANN60 **On behalf of James Bladel** Dear councilors, The Board sent their two topics for discussion on 1 September 2017 to the SG/Cs. The two topics are: (1) What are the key issues/topics you are currently working on? (2) What are the concerns of your Group regarding GDPR and how best to mitigate? We need to send the Board the GNSO topics of discussion for the joint GNSO/ ICANN Board meeting on Sunday 29 October 2017. Could you please let us know on the mailing list what you would like to discuss? Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Fwd: [So-ac-sg-cleaders] Adopted Board Resolutions | Regular Meeting of the ICANN Board - ICANN
by James M. Bladel Sept. 27, 2017

Sept. 27, 2017

Councilors, for your review. Thank you, J. ----------------- James Bladel GNSO Chair ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Sep 27, 2017, 00:52 +0200 Subject: [So-ac-sg-cleaders] Adopted Board Resolutions | Regular Meeting of the ICANN Board - ICANN https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.f Adopted Board Resolutions | Regular Meeting of the ICANNBoard 23 Sep 2017 1. Consent Agenda:<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1> * Approval of Minutes<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.a> * Appointment of Root Server Operator Organization Representatives to the RSSAC<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.b> * Rationale for Resolution 2017.09.23.02<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.…> * Transfer of the .CI (Cote d'Ivoire) top-level domain to Autorité de Régulation des Télécommunications/TIC de Côte d'Ivoire (ARTCI)<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.c> * Rationale for Resolution 2017.09.23.03<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.…> * Appointment of 2018 Nominating Committee Chair and Chair-Elect<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.d> * Rationale for Resolution 2017.09.23.04<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.…> * Deferral of the Second Review of the Country Code Name Supporting Organization (ccNSO)<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.e> * Rationale for Resolutions 2017.09.23.05 – 2017.09.23.06<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.…> * GAC Advice: Johannesburg Communiqué (June 2017)<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.f> * Rationale for Resolution 2017.09.23.07<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#1.…> 2. Main Agenda:<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2> * Consideration of Reconsideration Request 17-2<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.a> * Rationale for Resolution 2017.09.23.08<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.…> * Consideration of Reconsideration Request 17-3<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.b> * Rationale for Resolution 2017.09.23.09<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.…> * Information Transparency Initiative<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.c> * Rationale for Resolutions 2017.09.23.10 – 2017.09.23.11<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.…> * Board Governance Committee Charter Revisions and the Inaugural Charters of the Board Accountability Mechanisms Committee and the Board Technical Committee<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.d> * Rationale for Resolutions 2017.09.23.12 – 2017.09.23.14<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.…> * Consideration of the Amazon EU S.à.r.l. v. ICANN Independent Review Process Final Declaration<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.e> * Rationale for Resolutions 2017.09.23.15 – 2017.09.23.18<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.…> * Further Consideration of the Gulf Cooperation Council v. ICANNIndependent Review Process Final Declarations<https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.f> Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0