March 2018 - council - lists.icann.org

R.I.P. Stephane Van Gelder
by Austin, Donna 27 Mar '18

27 Mar '18

Dear Councilors On behalf of Paul Diaz from the RySG, I am forwarding his note below about Stephane Van Gelder. Stephane was a very active and dedicated member of the ICANN community having served as Chair of the GNSO Council, and Chair of the Nominating Committee. He was currently serving as Vice Chair, Policy of the RySG. Stephane will be missed by many. Kind regards Donna From: regycon(a)googlegroups.com [mailto:regycon@googlegroups.com] On Behalf Of Paul Diaz Sent: Monday, March 26, 2018 8:02 AM To: RySG Mailing List <regycon(a)googlegroups.com> Subject: [EXTERNAL] [REGYCON] R.I.P. Stephane Van Gelder Dear colleagues, It’s with great sadness that I must report the passing of Stephane Van Gelder. He was involved in a motorcycle crash on Friday, went into a coma and died last night. I will share details re memorial services, and will coordinate with our Registrar colleagues for some sort of rememberance ceremony at the GDD Summit. Best, P Paul Diaz Chairman, Registries Stakeholder Group Mobile:+1 703.973.1667 | Skype: pdiaz(a)pir.org<mailto:pdiaz@pir.org> -- You received this message because you are subscribed to the Google Groups "ICANN Registries Stakeholder Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to regycon+unsubscribe(a)googlegroups.com<mailto:regycon+unsubscribe@googlegroups.com>. To post to this group, send email to regycon(a)googlegroups.com<mailto:regycon@googlegroups.com>. Visit this group at https://groups.google.com/group/regycon<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_grou…>. To view this discussion on the web visit https://groups.google.com/d/msgid/regycon/CY4PR10MB20249EBE27936D9FAFD7138A…<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_ms…>. For more options, visit https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_op…>.

5 4

On the Fellowship program
by Arsène Tungali 26 Mar '18

26 Mar '18

Hi colleagues, I am taking this opportunity to contribute to this draft as submitted by our colleagues. I would like to thank the small group for coming up with these answers. Please see bellow my comments and suggested edits. As much as I see value for us, as a Council, to respond but I also think it would be difficult for us to agree on this as it would be difficult within the GNSO itself. But I will personally be okay with this draft after consideration has been taken of my bellow small comments. - I don’t support the HL comments. I would suggest we delete that section and keep our responses based on the questions as requested by the call. - On Q1: I think we are too demanding here. Though this looks good but I think we are going too far in terms of what we ask fellows to be able to do. I would like to suggest that the spirit of this paragraph be to mean that this is the ideal that we would like to see. I am sure many of us agree that “active and meaningful” participation in PDPs is not easy and it is a challenge, that even some of those who have been to ICANN for very long are failing to be “active and meaningful” participants? I don’t have the proper wording here but that’s what I would like to see reflected here. - On Q4, I have the following comment: Not having fellowship alumni active in GNSO doesn’t mean they are not active elsewhere within ICANN. I believe if we check other SO/ACs, we will find maybe many of them active there. If we don’t have them active in the GNSO, maybe it is because we are failing in terms of outreach? Or we should review available learning materials (ICANN Learn, etc) and see whether they provide enough information for someone to decide to join the GNSO. Just thinking outloud here. I would like to suggest an additional text: We have to note however that some members of the Council started as fellows and many other alumni are active in our different SG/Cs but more work needs to be done to have many more active in our core business. - On Q7, I don’t know what exactly we request on the last paragraph and would suggest we remove it: “It may also be advisable to interview candidates to ascertain their suitability for a fellowship”. - On Q10: I don’t agree with this but would suggest the way around. Keep the fellowship as it is and push for an evaluation (on KPI) that will provide metrics. And only after that assessment, we can make an informed decision. The budget issue should not be put forward here because as we know, the Fellowship program does not cost that much to the organization, as said in many public comments on FY19. - Q12: I don’t support this paragraph and would suggest the following: “Many first time fellows we interact with are not enough knowledgeable regarding ICANN-related issues and in particular GNSO topics. This is understandable because it is their first participation at an ICANN meeting. Many of them are interested in important Internet governance issues that fall outside of ICANN’s remit. “ I would suggest we emphasize on the fact that what we find abnormal is when the same applies to returning fellows not to first time fellows. - On Q13, I would like to suggest we add the text in bold: We are not aware of any Fellows actively attending in GNSO Council meetings *but we have seen some attending SG/C meetings and ask questions, which is encouraging.* - On Q14: Not sure on the basis of what we said YES. Are we able as the Council to meet with the fellows? I think we should be clear on what we mean here. Happy to provide clarification if needed. Regards, Arsene ------------------------ **Arsène Tungali* <http://about.me/ArseneTungali>* Co-Founder & Executive Director, *Rudi international <http://www.rudiinternational.org>*, CEO,* Smart Services Sarl <http://www.smart-serv.info>*, *Mabingwa Forum <http://www.mabingwa-forum.com>* Tel: +243 993810967 GPG: 523644A0 *Goma, Democratic Republic of Congo* 2015 Mandela Washington Felllow <http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.ht…> (YALI) - ISOC Ambassador (IGF Brazil <http://www.internetsociety.org/what-we-do/education-and-leadership-programm…> & Mexico <http://www.internetsociety.org/what-we-do/education-and-leadership-programm…>) - AFRISIG 2016 <http://afrisig.org/afrisig-2016/class-of-2016/> - Blogger <http://tungali.blogspot.com> - ICANN's GNSO Council <https://gnso.icann.org/en/about/gnso-council.htm> Member. AFRINIC Fellow ( Mauritius <http://www.afrinic.net/en/library/news/1907-afrinic-25-fellowship-winners>)* - *IGFSA Member <http://www.igfsa.org/> - Internet Governance - Internet Freedom. Check the *2016 State of Internet Freedom in DRC* report (English <http://cipesa.org/?wpfb_dl=234>) and (French <http://cipesa.org/?wpfb_dl=242>)

6 10

Draft minutes of the GNSO Council meeting Wednesday 14 March 2018
by Nathalie Peregrine 26 Mar '18

26 Mar '18

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on Wednesday 14 March 2018 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://gnso.icann.org/en/council/op-procedures-30jan18-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 5 April 2018. 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

Re: [council] [EXTERNAL] Fwd: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2
by PAMELA LITTLE 22 Mar '18

22 Mar '18

In addition to bandwidth issue and in light of the discussions around ICANN budget and GDPR at ICANN61, perhaps the community should consider a deferral/pause of this review. Also, see below excerpt of Goran's latest blog https://www.icann.org/news/blog/budget-discussions-at-icann61: "...and for the RDS Review, there is still significant work remaining to address the impacts of the General Data Protection Regulation (GDPR) on the WHOIS system. Delaying either of these reviews would save many hours of volunteer time. Additionally, and more broadly, addressing the timing of reviews, and approach, will contribute to discussing how to make future reviews more efficient and more relevant. Deferring a review that will be impacted by current Policy Development Processes or other outside factors, could have significant savings on productivity and cost." Kind regards, Pam ------------------------------------------------------------------Sender:Austin, Donna via council <council(a)gnso.icann.org>Sent at:2018 Mar 21 (Wed) 07:34To:Heather Forrest <haforrestesq(a)gmail.com>; GNSO Council List <council(a)gnso.icann.org>Subject:Re: [council] [EXTERNAL] Fwd: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2 Heather, Susan Where does this leave the RDS Review Team in terms of adequate membership? I know Susan has raised concerns previously that there isn’t enough people to do the work. Is it possible for the GNSO to recommend additional candidates to fill the vacancies left by the ccNSO’s decision not to appoint volunteers? Donna From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Heather Forrest Sent: Tuesday, March 13, 2018 10:51 AM To: GNSO Council List <council(a)gnso.icann.org> Subject: [EXTERNAL] [council] Fwd: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2 Dear Council colleagues, Please note the ccNSO's affirmed position on RDS/WHOIS2 RT. Best wishes, Heather---------- Forwarded message ---------- From: Katrina Sataki <katrina(a)nic.lv> Date: Wed, Mar 7, 2018 at 1:37 PM Subject: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2 To: Alan Greenberg <alan.greenberg(a)mcgill.ca> Cc: Goran Marby <goran.marby(a)icann.org>, Chris Disspain <chris.disspain(a)board.icann.org>, mike.silber(a)board.icann.org, SOAC Chairs <soac-chairs(a)icann.org> 7 March 2018 To: Alan Greenberg, RDS/WHOIS 2 Review Team, ChairCC: Chris Disspain, Mike Silber, Göran Marby, Chairs of ALAC, ASO, GAC, GNSO, SSAC, RSAC Dear Alan, In May 2017, we informed the ICANN Board of Directors that the ccNSO did not find itself in a position to nominate candidates for the RDS/ WHOIS2 Review Team, and deferred participation in this specific review. On 18 January 2018, the ccNSO Council again discussed its participation in the review. Following this discussion, by 16 February 2018, the ccNSO Council decided not to participate in the RDS/WHOIS2 specific review. The ccNSO Council thanks the volunteers who sought endorsement of the ccNSO. Kind regards, Katrina Sataki,Chair of the ccNSO _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

4 3

Action Items: GNSO Council meeting 14 March 2018 & Wrap Up 15 March 2018
by Nathalie Peregrine 22 Mar '18

22 Mar '18

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Wednesday 14 March 2018 and the Wrap Up session from Thursday 15 March 2018. Please take note of the action items coming out of the Council sessions and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. ACTION ITEMS FROM THE GNSO COUNCIL MEETING 14 MARCH 2018 Item 2: COUNCIL DISCUSSION – Discussion with ICANN Finance on the Draft FY19 ICANN Operating Plan and Budget Action Items: * Standing Committee on Budget and Operations (SCBO) to help facilitate the collection and channelling of any Council questions or comments for ICANN Finance related to the FY19 Budget and Operating Plan by inviting input on the Council email list. * SCBO to develop possible Council input concerning Reserve Fund replenishment strategy public comment forum if there are no objections to the SCBO undertaking this task. (Note, deadline for comments is 25 April 2018) * SCBO Chair to request support / objections from Council to the SCBO developing possible Council input concerning Reserve Fund replenishment strategy. Item 5: COUNCIL UPDATE – Updated Charter for the Cross Community Engagement Group on Internet Governance Outcomes: * Per resolution<https://gnso.icann.org/en/council/resolutions#201708>, the GNSO is no longer a Chartering Organization of the Cross Community Working Group on Internet Governance. Action Items: * GNSO Council to seek clarification about the level of resources expected to be allocated to the Cross Community Engagement Group on Internet Governance. * GNSO Council Liaison to the ccNSO to coordinate with the Country Codes Names Supporting Organization (ccNSO) as the Cross Community Engagement Group on Internet Governance seeks to resolve concerns identified by the ccNSO Council. * GNSO Council to determine if it will serve as a Chartering Organization, if the Cross Community Engagement Group mechanism supports Chartering Organizations. Item 6: COUNCIL DISCUSSION – Update on the GNSO Council’s input to the consultation on the Fellowship Program Action Item: * Small Group of Councilors to consider input received during the 14 March 2018 Council meeting, circulate the updated version for Council feedback, and, if no objections are received, submit comments by the 30 March 2018 deadline. Item 7: COUNCIL DISCUSSION – Review of the Inter-Registrar Transfer Policy (IRTP) Action Item: * GNSO Council to consider next steps, timing and provide guidance to ICANN Org on if, how, and when the review of the Inter-Registrar Transfer Policy (IRTP) should take place, factoring in ongoing discussion on the post-implementation policy review framework as well as the transfer issue that is being considered by the Privacy & Proxy Services Accreditation Issues Implementation Review Team. ACTION ITEMS FROM THE GNSO COUNCIL WRAP-UP 15 MARCH 2018 ICANN62 Meeting Planning Action item: * Council Leadership (Heather Forrest and Rafik Dammak) to attend ICANN62 planning meeting, communicate concerns raised by Council, and report back to the Council. * Council to develop plan for conducting outreach at ICANN meetings, especially for the Policy Forum. CSC and IFR Review Action item: * Donna Austin and Philippe Fouquart to lead small team to suggest ways to avoid overlap between reviews; coordinate with the ccNSO in doing so. Board request regarding Emojis (see https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e) Action item: * Council Leadership to send response to the Board to acknowledge receipt of request. * Staff to summarize Board resolution and SSAC Advice for small team of Councilors to consider. * Small team of Councilors (Michele Neylon, Martin Silva Valent, Tatiana Tropina and Philippe Fouquart as the GNSO liaison to the ccNSO) to liaise with the SSAC, as well as ccNSO, in responding to Board resolution. Council liaison to new gTLD SubPro Action items: * Staff to update project list to note that Keith Drazek and Donna Austin will serve jointly as the Council liaisons to the New gTLD Subsequent Procedures PDP WG. * Staff to communicate new liaisons to the New gTLD Subsequent Procedures PDP WG. SubPro/RPM Consolidated timeline Action item: * Council liaisons to the respective PDP WGs to review Sunday Working Session and extract notes and action items. * Council liaisons to the respective PDP WGs to work with PDP WG leadership to expand timeline to include potential implementation steps/scenarios. GNSO Review of GAC Communique Action items: * Staff to circulate template to volunteers following publication of GAC Communique * Council volunteers (Julf Helsingius, Rafik Dammak, Darcy Southwell, Michele Neylon, Tatiana Tropina, Ayden Férdeline, and Paul McGrady) to provide a draft response for Council consideration. PDP 3.0 Action item: * Staff to consolidate input and comments into a Google document. * Staff to propose next steps (e.g., identify goal for ICANN62 and plan backwards). * Council to consider whether to form a small team to help in addressing the action item directly above. Timing of ICANN bylaw mandated reviews: Action item: * Council to await paper from Goran Marby and team to then consider next steps. Board Process for GAC Advice Action item: * [Note: More of an ongoing advisory than an action item] Anyone who has edits can send these to staff for consideration by the staff members that have ownership of the relevant documentation. Thank you, 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] [Ext] Re: INPUT PLEASE: ICANN Fellowship Program Community Consultation
by Heather Forrest 21 Mar '18

21 Mar '18

Dear Council colleagues, I am pleased to advise of an extension (one week, I anticipate, based on Ergys's email - specifics to follow when the website is updated) in the input period on the Fellowship Program. Best wishes, Heather ---------- Forwarded message ---------- From: Ergys Ramaj <ergys.ramaj(a)icann.org> Date: Thu, Mar 22, 2018 at 10:00 AM Subject: Re: [So-ac-sg-cleaders] [Ext] Re: INPUT PLEASE: ICANN Fellowship Program Community Consultation To: Heather Forrest <haforrestesq(a)gmail.com> Cc: Rod Rasmussen <rod(a)rodrasmussen.com>, Sally Costerton < sally.costerton(a)icann.org>, SOAC-Leaders-ICANNMeeting-Planning < soac-leaders-icannmeeting-planning(a)icann.org>, "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Dear Heather, Absolutely. We will extend the deadline for everyone and update the webpage accordingly. Best, Ergys On Mar 21, 2018, at 6:54 PM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear Ergys, On behalf of the GNSO, may I please seize the opportunity of the one week extension you have offered? Many thanks, Heather Forrest On Thu, Mar 22, 2018 at 8:27 AM, Ergys Ramaj <ergys.ramaj(a)icann.org> wrote: > Dear Rod, > > Many thanks for the question. I suspect others on this thread will also > benefit from the clarification. > > The intent is to collect feedback from each SO/AC/SG/C rather than > individual members from those groups. This will ensure that any resulting > changes reflects the guidance provided by the community structures. > > Would a one week extension help? > > Best, > Ergys > > > On Mar 21, 2018, at 4:50 PM, Rod Rasmussen <rod(a)rodrasmussen.com> wrote: > > David, > > I want to be clear on what the intent is here since the ask is not > explicit that I can tell. Are you looking for each SO/AC to provide their > feedback as an SO/AC as a whole, or are you looking for us to disseminate > this to our respective members so they can contribute individually? > Reading between the lines, I’m concerned that it’s the former, and with > only 10 days notice, I don’t think any SO/AC could turn around a consensus > opinion on this - I know SSAC won’t be able to. I’m sure individuals who > have been tracking this situation will have plenty of good insight to > share, but of course, cannot speak for each group, just as individuals > associated with a group. > > Thank you in advance for your clarification to me on this, and apologies > for being dense - I just want to make sure I’ve got this right. > > Cheers, > > Rod Rasmussen > SSAC Chair > > On Mar 20, 2018, at 10:01 AM, David Olive <david.olive(a)icann.org> wrote: > > And with the attachment. > > My apologies. Regards David > > > David A. Olive > Senior Vice President > > Policy Development Support > Internet Corporation for Assigned Names and Numbers (ICANN) > > > *From: *David Olive <david.olive(a)icann.org> > *Date: *Tuesday, March 20, 2018 at 12:49 PM > *To: *SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-pla > nning(a)icann.org>, "so-ac-sg-cleaders(a)icann.org" < > so-ac-sg-cleaders(a)icann.org> > *Cc: *Ergys Ramaj <ergys.ramaj(a)icann.org>, Sally Costerton < > sally.costerton(a)icann.org> > *Subject: *INPUT PLEASE: ICANN Fellowship Program Community Consultation > > Dear Community Leaders: > > With the discussion at ICANN61, here is an opportunity for your inputs on > the Fellowship Program. > > Questions about the program and responses to the questionnaire should be > sent to fellowshipconsultation(a)icann.org by 30 March 2018. > > > ------------------------------------------------------------ > ---------------------------- > > > Dear Community Leaders: > > > > > We’re launching a community-wide consultation on the Fellowship Program to > help inform its future direction. > > The attached paper provides an overview of the program, including a > breakdown of the data available on the Fellows, a questionnaire, and other > details about the consultation process. > > We anticipate that there will be interest in further discussing this > process and our team will be available to speak with community groups about > the current Fellowship Program and the questionnaire at ICANN61 or > remotely. Questions about the program and responses to the questionnaire > should be sent to fellowshipconsultation(a)icann.org by 30 March 2018. > > Grateful if you could share this informationso that each community group > is aware of and has the opportunity to participate in the consultation. > > Best, > > Ergys Ramaj > Sr. Director, Public Responsibility Support, ICANN > > > > > > > <ICANN Fellowship Program Community Consultation .pdf> > > <ICANN Fellowship Program Community Consultation [1].pdf> > _______________________________________________ > So-ac-sg-cleaders mailing list > So-ac-sg-cleaders(a)icann.org > https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders > > > > _______________________________________________ > So-ac-sg-cleaders mailing list > So-ac-sg-cleaders(a)icann.org > https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders > >

1 0

Fwd: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2
by Heather Forrest 21 Mar '18

21 Mar '18

Dear Council colleagues, Please note the ccNSO's affirmed position on RDS/WHOIS2 RT. Best wishes, Heather ---------- Forwarded message ---------- From: Katrina Sataki <katrina(a)nic.lv> Date: Wed, Mar 7, 2018 at 1:37 PM Subject: [soac-chairs] ccNSO Council resolves not to participate in RDS/WHOIS2 To: Alan Greenberg <alan.greenberg(a)mcgill.ca> Cc: Goran Marby <goran.marby(a)icann.org>, Chris Disspain < chris.disspain(a)board.icann.org>, mike.silber(a)board.icann.org, SOAC Chairs < soac-chairs(a)icann.org> 7 March 2018 To: Alan Greenberg, RDS/WHOIS 2 Review Team, Chair CC: Chris Disspain, Mike Silber, Göran Marby, Chairs of ALAC, ASO, GAC, GNSO, SSAC, RSAC Dear Alan, In May 2017, we informed the ICANN Board of Directors that the ccNSO did not find itself in a position to nominate candidates for the RDS/ WHOIS2 Review Team, and deferred participation in this specific review. On 18 January 2018, the ccNSO Council again discussed its participation in the review. Following this discussion, by 16 February 2018, the ccNSO Council decided not to participate in the RDS/WHOIS2 specific review. The ccNSO Council thanks the volunteers who sought endorsement of the ccNSO. Kind regards, Katrina Sataki, Chair of the ccNSO _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

5 4

Should the SCBO prepare a comment on the proposed Reserve Fund replenishment strategy?
by Ayden Férdeline 21 Mar '18

21 Mar '18

Dear all, As Xavier mentioned during our Council meeting yesterday, a new consultation opportunity has opened for comments on the proposed Reserve Fund replenishment strategy. The Standing Committee on Budget and Operations (SCBO) has a group of Councillors and Subject Matter Experts from across the GNSO who have gotten into the rhythm of meeting regularly as a part of our review of the proposed FY19 Budget and Operating Plan. Given this momentum, I was wondering whether or not the Council would like the SCBO to prepare a draft comment in response to this consultation opportunity? Thank you. Kind regards, Ayden Férdeline Chair, SCBO

7 10

Please share: Multistakeholder Ethos Award Nomination Process Extended
by Nathalie Peregrine 20 Mar '18

20 Mar '18

https://www.icann.org/news/announcement-2018-03-20-en Nominations Close 28 March 2018 Submit Nominations Via the Ethos Award Nomination Form<https://goo.gl/forms/gtjY7wFw1zlkL0J62> ICANN is pleased to remind community members that the nomination period for ICANN's Multistakeholder Ethos Award has been extended until 28 March 2018. The ideal recipient(s) will have served in roles in multiple ICANN working groups or committees and collaborated with more than one Supporting Organization and/or Advisory Committee in a significant capacity. Candidates for the award will demonstrate at least five years of participation in the ICANN Community. Candidates will be evaluated by a panel of community members appointed by the Chairs of each Supporting Organizations and Advisory Committees using a merit-based point system evaluated against three criteria: 1. Demonstrated ability to work across community lines with both familiar and unfamiliar ICANNStakeholders with the aim of consensus building and collaboration that substantiate ICANN's multistakeholder model; 2. Facilitator of dialogue and open discussion in a fair and collegial manner, through the spirit of collaboration as shown through empathy and demonstrating a sincere desire to engage with people from other backgrounds, cultures, and interests; and 3. Demonstrated additional devotional factors exhibited by time spent supporting ICANN's multistakeholder model and its overall effectiveness through volunteer service via working groups or committees. Please submit your nominations via this Nomination Form<https://goo.gl/forms/gtjY7wFw1zlkL0J62> including detailed information outlining why the nominee meets the award criteria. Any additional information in support of nominations and/or questions about the award process may be submitted via email at ethosaward2018(a)icann.org<mailto:ethosaward2018@icann.org>. Award recipient(s) will be announced in June 2018 at ICANN62 Panama City. For more insights on the award program, please consult the ICANN Community Wiki.<https://community.icann.org/x/YyOAAw> Submit Nominations Via the Ethos Award Nomination Form<https://goo.gl/forms/gtjY7wFw1zlkL0J62>

1 0

Fwd: Thank you!
by Heather Forrest 20 Mar '18

20 Mar '18

Dear Council colleagues, Passing on the kind note from previous Council Chair James Bladel, below. Best wishes, Heather ---------- Forwarded message ---------- From: James M. Bladel <jbladel(a)godaddy.com> Date: Tue, Mar 20, 2018 at 2:22 AM Subject: Thank you! To: Heather Forrest <haforrestesq(a)gmail.com> Heather – Would you be so kind as to forward the note below to the Council list? Thanks— J. Friends and Colleagues – Thank you current & former GNSO Councilors for the Cycling Jacket. Although it took some time to be delivered, it is arriving just in time for the spring cycling season, and I expect it will see extensive use in the next few months, and beyond. It was great seeing you all in San Juan, and looking forward to Panama this summer. In the meanwhile, please don’t hesitate to ping me if I can be helpful in your work. Cheers – J. ------------- *James Bladel* Vice President, Global Policy @bladel *Typical Time Zone: US Central Daylight (UTC-5)* [image: cid:image001.png@01D3A3E8.81BA80A0]

1 0