October 2018 - council - lists.icann.org

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong 03 Jul '19

03 Jul '19

Dear Ayden and all, We apologize if there were difficulties with accessing the feedback tool – there ought not to be any, so please do try it again if you wish to provide feedback. Please be assured that ICANN organization is committed to and interested in gathering the community’s feedback on each of the features that we will be rolling out with the objective of improving the findability, transparency, and accessibility of ICANN public content. The deadlines are, unfortunately, what they are in order to ensure that we are able to deliver on this major project on budget and on time. There will certainly be multiple and additional opportunities and forums for continuing community feedback, as noted in David’s blog that is referenced in the announcement below. Thank you. Best regards, Mary From: council <council-bounces(a)gnso.icann.org> on behalf of Ayden Férdeline <icann(a)ferdeline.com> Reply-To: Ayden Férdeline <icann(a)ferdeline.com> Date: Wednesday, April 25, 2018 at 09:17 To: Heather Forrest <haforrestesq(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] Fwd: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad Given comments are being sought for less than a week, this does not strike me as a genuine consultative activity but appears to be a token form of participation intended to manipulate public opinion. This new website implies a shift towards greater consultation and community participation in ICANN's content strategy, but we cannot actually wield any influence by commenting here. (And not just because if you press the 'provide feedback' button, you see "The feedback survey is temporarily unavailable.") From what I understand we are not even being asked to comment on anything important. The list of 250 definitions, which I would like to review for neutrality and accuracy, are not online and it sounds like they have already been approved internally and are not open to community review. Are we really being asked to comment on just the glossary tool itself, and did ICANN really produce a video mockup and slide deck of something so incredibly mundane when it is up for public comment for just a week? Please forgive the negative sentiment to my message here, but it really seems a poor allocation of resources to me. Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 25 April 2018 3:03 PM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear Council colleagues, I am pleased to pass on David Olive's update, below, on the Information Transparency Initiative. Best wishes, Heather ---------- Forwarded message ---------- From: "David Olive" <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: 24/04/2018 10:37 AM Subject: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad To: "so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>" <so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>> Cc: "David Conrad" <david.conrad(a)icann.org<mailto:david.conrad@icann.org>>, "Jana Juginovic" <jana.juginovic(a)icann.org<mailto:jana.juginovic@icann.org>> https://www.icann.org/news/blog/the-information-transparency-initiative-iti…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> The Information Transparency Initiative (ITI) Feedback Site is Now Live I'm pleased to announce that today, we launched the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> (feedback.icann.org[feedback.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__feedback.icann.org&d=Dw…>). As I have written about in previous blogs and discussed at ICANN60 and ICANN61 sessions, this site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is intended to provide you, the ICANN community, with the ability to share your input on the content and features the ITI team is working on to improve the findability, transparency, and accessibility of ICANN public content. The first item we are looking for your comments on is an updated Acronyms and Terms feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to replace the existing feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Our update doubles the number of terms available, provides up-to-date definitions for the terms, and improves search. Unlike most of the ITI project, we will launch this updated feature on the current https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…> before 31 May 2018. The deadline to provide your input on the proposed updates to Acronyms and Terms is 30 April 2018, 23:59 UTC. Please visit feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to experience the proposed changes and complete a short survey. How the ITI Feedback Site Works The ITI Team will regularly post documents, mockups, or video walkthroughs of new content and features. The proposed content or feature items are listed on the homepage under the heading "Feedback Needed." Each item lists a deadline by which you need to provide input. Simply click on the item you're interested in. This will take you to another page, which provides you with the option to either download a mockup or watch a video walkthrough. Once you have completed that task, click on the "Feedback" button to complete a short survey or email your feedback to informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Once the deadline has passed, the ITI Team will collect and publish all comments to feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…>. All published results of the survey will be anonymous, unless otherwise requested by the submitter. We will review all submissions and make our best efforts to implement the feedback, prioritizing input that serves the goals of improving search and accessibility, and increasing the transparency of our content. Feedback Deadlines We do have a tight deadline for community comments – one week for each new item. The reason for this timeline is we need to maintain a rigorous development schedule to ensure we are delivering the project on time and within budget. However, feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is not your only avenue to share input. ITI has many other opportunities to learn about ITI and provide comments including: * Regular sessions at ICANN Public Meetings. * Special sessions or webinars for Supporting Organizations and Advisory Committees (SO/ACs) on request or for special features and content like Public Comment. * Monthly blogs and newsletters. * Via email at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org> Feedback Translations As I outlined above, we are working at a brisk development pace. This does limit our ability to fully translate feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and its survey. But, if you want to share feedback in another language, email us at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. It is important to emphasize that one of the primary goals of ITI is a multilingual https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, and the sooner we complete this project, the sooner we can deliver on that goal. ITI Goals ITI's goal is not a revamp of https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>. While the ITI team is working on making improvements to your User Experience (UX) on https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, the vast majority of our efforts are focused on: * Creating content governance through new, enforced workflows and the creation of a consistent, multilingual taxonomy. * Building new technical infrastructures including a first-ever for ICANN document management system (DMS) and a new content management system (CMS). This new infrastructure will enforce this governance and enable improved content findability. Much of this foundational work won't be available on the feedback site for your input, but we will show the intended benefits of this work through the content and features we will share. ITI Update The ITI team has been hard at work completing that foundational work I mentioned above. We have completed the following tasks since the January 2018 launch of ITI: * The foundational build of the DMS and CMS, and the integration between the two platforms. * Sixty percent of the content audit and the taxonomy creation. * Interviews with SO/AC leaders, registrants, registrars, Fellows, and other ICANN stakeholders. We have also begun work on the following items: * Content modelling, workflow creation, and content governance enforcement in the DMS. * Accessibility guidelines and multilingual site implementation planning. ITI will launch in December 2019. ITI Backgrounders For those of you unfamiliar with ITI, you can read about what it is and how it will benefit the ICANN community in my kickoff blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. You can learn more about how the content audit and taxonomy will help your search experience in my January blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We also outlined the differences between ITI and the Open Data Initiative (ODI) in our pre-ICANN61 blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We Need Your Feedback Remember, we need your input to help us make the specific improvements to search, transparency, and accessibility that you need and want. Please visit the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and email us anytime at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Comments Log in to Comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> or Sign Up[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> Details * ICANN Blog * Author: David Conrad, Chief Technology Officer (CTO) and Senior Vice-President * 23 Apr 2018 David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org<mailto:So-ac-sg-cleaders@icann.org> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

4 7

Amendments to the Consensus Policy Implementation Framework (CPIF)
by Brian Aitchison 01 Nov '18

01 Nov '18

Dear GNSO Council members, Following conversations among ICANN org and the GNSO Council—in particular the IPC and the RrSG who provided written input—please find attached a redlined version of the CPIF that addresses the suggestions for amendments we received. Also attached is the original letter sent from ICANN org to the GNSO Council detailing the mandate and focus of the CPIF amendment process. We were not able to integrate all suggestions received into this round of CPIF amendments. You’ll see in the comment boxes the suggestions received, along with a rationale for why we did or did not update the document based on those suggestions. Generally speaking, we did not add amendments that merited more in-depth discussion between ICANN org and the Council. For example, the process for recruiting IRTs is based on a “call for volunteers”, so we could not add the IPC’s suggestion that IRT’s must “fairly represent all constituencies” until further discussion with the Council about how IRTs should be constituted. We also tried to minimize any redundant language that may overly simplify the process of soliciting GNSO Council input on an implementation via an IRT. In accordance with Point H of the CPIF, which directs “ICANN staff [to] continually review the implementation framework and related materials to encapsulate additional best-practices or to adjust the steps as a result of lessons learned with previous Consensus Policy projects,” ICANN org will continue to work with the GNSO Council to refine the CPIF. Currently we are working on defining a standard process for proposing amendments to it, which we will share with the Council when ready. ICANN org will continue to welcome input on how and where the CPIF should be amended. Any such input received will be tracked and evaluated for a future round of amendments, which we plan to begin in the next calendar year. To provide input, please email me at brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> (please cc the Council list). Our Policy Team colleagues also welcome your input; should you have any, please feel free to discuss it with them during one of your meetings or via email. We request that the GNSO Council review the attached redlined CPIF document. If no further input is received, we will post it to icann.org’s implementation page at https://www.icann.org/policy/implementation on 10 December 2018. On behalf of ICANN org, we thank the Council and its members for providing input on this important process. Sincerely, Brian -- Brian Aitchison, PhD Lead Researcher Global Domains Division, Operations and Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles, CA p. 310 578 8688 m. 424 353 9041 e. brian.aitchison(a)icann.org<mailto:brian.aitchison@icann.org> Sk. brian.aitchison.icann CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.

2 1

Board resolution and rationale on reserve fund replenishment
by Marika Konings 30 Oct '18

30 Oct '18

Dear All, As discussed during today’s wrap up session, please find below the Board resolution and rationale in relation to the reserve fund replenishment strategy. Best regards, Marika ================ https://www.icann.org/resources/board-material/resolutions-2018-10-25-en#2.f • Reserve Fund Replenishment Strategy Whereas, the Board confirmed by previous decision (resolutions 2018.02.04.09 – 2018.02.04.10) that the target level of the ICANN Reserve Fund should be at a minimum equivalent to 12 months of operating expenses. Whereas, the current level of the Reserve Fund is approximately of US$70 million as of 30 June 2018, reflecting a shortfall compared to the minimum target level of approximately US$68 million. Whereas, ICANN organization posted for public comment a proposed strategy to replenish the Reserve Fund and the Board took all comments submitted into account to determine the final Reserve Fund replenishment strategy. Whereas, the proposed replenishment strategy entails allocating to the Reserve Fund: (i) annual operational excess of funding over expenses for a total of US$32 million over an eight-year period; and (ii) US$36 million of new gTLD auction proceeds. Resolved (2018.10.25.22), the Board directs the President and CEO, or his designee(s), to take all actions necessary to increase the Reserve Fund through annual excesses from the operating fund of ICANN organization by a total amount of US$32 million over a period of seven to eight years, starting with FY19. Resolved (2018.10.25.23), the Board directs the President and CEO, or his designee(s), to take all actions necessary to allocate US$36 million of auction proceeds to the Reserve Fund, as soon as technically feasible. Rationale for Resolutions 2018.10.25.22 – 2018.10.25.23 Based on its fiduciary duties and considering the significant growth and risk profile that ICANN has seen since the creation of its Reserve Fund, the Board determined that the Reserve Fund required to be reviewed, especially in light of the significant drop in its level. The Board conducted an evaluation of the Rationale and Target level for the Reserve Fund, which was based on the public comments received on a first consultation paper. As a result, an updated ICANN Investment Policy was approved by the Board to include: (a) an updated Reserve Fund Rationale; and (b) a confirmation that the Reserve Fund Target Level will be set at a minimum of 12 months of Operating Expenses (See resolution https://features.icann.org/confirmation-reserve-fund-target-level). Once the Target Level was confirmed, the Board outlined a proposed strategy to replenish the Reserve Fund from its current level to its updated minimum Target Level, which was the subject of a second public comment process. The comments received provided for a wide range of views on the sources of funds and extent of use of such sources for the purpose of replenishment. Relative to the annual excess allocation, most comments received on this aspect suggested a higher allocation than the one proposed. On the allocation of auction proceeds, some comments suggested a lower allocation and others a higher allocation to the Reserve Fund. All comments but one indicated that no increase to ICANN fees should be considered. Also, the use of New gTLD Program funds for purpose of replenishment was not retained in the final proposed strategy due to the continued existence of risks associated with the program. Based on comments received, a final proposed replenishment strategy was drafted, which reflects a higher annual excess allocation than proposed, and is now submitted for Board approval and implementation. The remaining auction proceeds continue to be segregated and are not intended to be used for day-to-day operations. The Board will review the CCWG recommendations for a disbursement mechanism, as approved by the chartering organizations, and will then make a decision on the mechanism by which available proceeds should be disbursed, for implementation by ICANN org. At all times, the Board will continue to make all decisions in furtherance of ICANN's mission, under consideration of its duty of care and its fiduciary responsibility. This action is in the public interest and is consistent with ICANN's mission as it is important to ensure stability of ICANN organization in the way of an adequately funded Reserve Fund in case use of a Reserve Fund becomes necessary. This action will have a positive financial impact on ICANN and will enable ICANN to support its financial stability and sustainability. It will not have any impact on the security, stability or resiliency of the domain name system. This is an Organizational Administrative function that has already been subject to public comment as set forth above. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

3 2

Thank you and best wishes
by Heather Forrest 29 Oct '18

29 Oct '18

[image: 20171225_165055.jpg] Dear Council colleagues, I echo all of Donna's beautifully articulated sentiments. It has been a tremendous privilege working with you all and and achieving so much together. Puerto (left) and Rico (right) send their thanks. I'll send a photo of them in the fabulous blankets when I get home in a few weeks. I would love to see the Google searches that led up to that most perfect of gifts. :) With very best wishes, and sincerest thanks, Heather

3 2

It’s been a joy
by Austin, Donna 28 Oct '18

28 Oct '18

Dear Councilors Hopefully I still have posting rights for one last message. I can’t believe how quickly four years has flown by. Sincere thanks to you all for the collegial spirit In which we’ve undertaken our work during that time. The last 12 months has been a series of unforeseen and unprecedented challenges, but thanks to Heather’s leadership and everyone’s willingness to engage and find a path forward, I think we’ve done pretty well. I’ll see you around and I hope I have an opportunity to work with you all again in some capacity. Many thanks Donna Sent from my iPhone

4 3

Call for Volunteers - SCBO
by Berry Cobb 28 Oct '18

28 Oct '18

Hi All, As discussed at the GNSO Council wrap-up session in Barcelona, please find attached a call for volunteers to join the Standing Committee on ICANN's Budget and Operations. It will be helpful to have adequate representation from both houses. You can view the current membership here <https://community.icann.org/pages/viewpage.action?pageId=74580769> . The SCBO is formulating comments for the draft FY20 IANA/PTI budget, which is due 12 November 2018. The draft FY20 ICANN Org budget is expected to be posted on 17 December 2018. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Call for Volunteers - SCBO
by Berry Cobb 28 Oct '18

28 Oct '18

Hi All, As discussed at the GNSO Council wrap-up session in Barcelona, please find attached a call for volunteers to join the Standing Committee on ICANN's Budget and Operations. It will be helpful to have adequate representation from both houses. You can view the current membership here <https://community.icann.org/pages/viewpage.action?pageId=74580769> . The SCBO is formulating comments for the draft FY20 IANA/PTI budget, which is due 12 November 2018. The draft FY20 ICANN Org budget is expected to be posted on 17 December 2018. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Re: [council] Proposed GNSO Council meeting dates 2019
by Flip Petillion 26 Oct '18

26 Oct '18

Dear Nathalie, May I ask you to kindly confirm the dates for November and December? Thank you Kind regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_907712380]<http://www.petillion.law/> From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday, 25 October 2018 at 13:32 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed GNSO Council meeting dates 2019 Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th 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…>

2 1

Proposed GNSO Council meeting dates 2019
by Nathalie Peregrine 26 Oct '18

26 Oct '18

Dear all, Please have a quick look at the below list of proposed GNSO Council meeting dates for 2019. This is an agenda item for our Wrap-Up meeting later today (17:00 – 18:30 in GNSO room 115). Religious holidays and IG related events have been taken account as much as possible, but please point out conflicts if they have been left out. * January - 24th (Pacific time, during the GNSO Strategic Planning session) * February – 21st * March 13th (ICANN64 Kobe) * April 18th * May 16th * June 26th (ICANN65 Marrakech) * July 18th * August 22nd (August 15th is end of Eid al-Adha and French National Holiday) * September 19th * October 24th (17th is Sukkot - Jewish holiday) * November 6th (ICANN66 Montreal) * December 19th 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…>

5 4

FW: [gnso-secs] Rafik as NCPH vice chair
by Nathalie Peregrine 26 Oct '18

26 Oct '18

Dear councilors, Please see below notification from Farzaneh Badii that Rafik Dammak is the Non Contracted Party House representative GNSO Council Vice Chair. Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of farzaneh badii <farzaneh.badii(a)gmail.com> Date: Thursday, October 25, 2018 at 6:57 PM To: Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Rafik as NCPH vice chair Dear GNSO Secretariat We hereby confirm that Rafik has been re appointed to the gnso council vice chair position. Thank you -- Farzaneh

4 3