<div>This is an excellent suggestion, Stephanie. I would like to hear what suggestions the Board has here for us, too. This is something we really need to tackle. And it's something I hope we might be able to table for discussion in San Juan as well. We need to talk about the expected standard of behaviour for our officers and members, along with the trajectory ICANN is moving in and what that could mean for us... We predicted ICANN was broke last year, insinuated as much in our Reserve Fund comment, and called for cuts to spending, but we haven't insulated ourselves sufficiently from these cuts... We are very, very vulnerable at the moment and if we are not prudent with our allocation of resources I worry we [non-commercial voices] could pay a heavy price. I think Sam made a very insightful comment on this topic yesterday on Skype; I'm cc'ing him into this discussion in case he'd like to paste his message here for other list subscribers to see, and/or expand upon his prediction... I'd certainly like to hear more about the 'red flags' we should be looking out for over the coming 12 months...<br></div><div><br></div><div>Ayden <br></div><div><br></div><div><br></div><div>-------- Original Message --------<br></div><div> On 15 February 2018 5:53 PM, Stephanie Perrin <stephanie.perrin@mail.utoronto.ca> wrote:<br></div><div> <br></div><blockquote class="protonmail_quote" type="cite"><p><br></p><div class="moz-forward-container">these are not bad questions. I
think we should ask the Board if they have suggestions for greater
accountability in our stakeholder group. Since they are proposing
to cut CROP funding, how do they propose we inform our members of
the complexity of ICANN policy issues, and ensure they are
contributing effectively to the MS model on which ICANN depends? <br></div><div class="moz-forward-container">I think our goals for next year
should include greater accountability for our actions and
expenditures. $$$ may be going out the window with falling
registrar revenues, and we may be coming back to a world where
ICANN did not support us for travel and admin. And nobody would
wave goodbye.....<br></div><div class="moz-forward-container">cheers SP<br></div><div class="moz-forward-container"><div>-------- Forwarded Message
-------- <br></div><table border="0" cellpadding="0" cellspacing="0" class="moz-email-headers-table"><tbody><tr><th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:<br></th><td>Re: [council] Reminder - topics for meeting with ICANN
Board at ICANN61<br></td></tr><tr><th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date:<br></th><td>Thu, 15 Feb 2018 22:33:19 +1100<br></td></tr><tr><th nowrap="nowrap" valign="BASELINE" align="RIGHT">From:<br></th><td>Heather Forrest <a href="mailto:haforrestesq@gmail.com" class="moz-txt-link-rfc2396E"><haforrestesq@gmail.com></a><br></td></tr><tr><th nowrap="nowrap" valign="BASELINE" align="RIGHT">To:<br></th><td>Marika Konings <a href="mailto:marika.konings@icann.org" class="moz-txt-link-rfc2396E"><marika.konings@icann.org></a><br></td></tr><tr><th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC:<br></th><td><a href="mailto:council@gnso.icann.org" class="moz-txt-link-abbreviated">council@gnso.icann.org</a> <a href="mailto:council@gnso.icann.org" class="moz-txt-link-rfc2396E"><council@gnso.icann.org></a><br></td></tr></tbody></table><div><br></div><div><br></div><div dir="ltr"><div>Hello everyone, <br></div><div><div><br></div><div>I hope you've returned home happy and healthy after our time
in LA.<br></div></div><div><br></div><div>We're behind in communicating our questions/topics to the
Board for discussion in San Juan. As yet we've had no
suggestions. Here are three possibilities to seed the
discussion: <br></div><div><ul><li>SSR2 - the Board has stated on various recent occasions
that it has 'learned lessons' from its handling of the
SSR2-RT pause. What specific lessons have been learned and
how will these affect future Board action?<br></li><li>Goals - The Board has asked the various community groups
to identify their most relevant longer-term goals. What
are the Board's longer-term goals, in view of budgetary
and market trends?<br></li><li>The GNSO Council devoted time in January to strategic
planning for the year ahead. Taking into account a
continuously high volume of work and the FY19 budgetary
pressures, we see the need for and benefit of
prioritisation. Considering the many activities currently
underway in ICANN, which do the Board consider to be top
priority? What milestones or achievements is the Board
hoping to reach by the end of 2018?<br></li></ul><div>Best wishes,<br></div></div><div><br></div><div>Heather<br></div></div><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div>On Wed, Feb 7, 2018 at 7:56 AM, Marika
Konings <span dir="ltr"><<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>></span> wrote:<br></div><div> <br></div><blockquote style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex" class="gmail_quote"><div lang="EN-US"><div class="m_-7776137299844508011WordSection1"><p class="MsoNormal"><span class="size" style="font-size:11pt">Reminder
– the GNSO Council leadership team is expected to
submit to the ICANN Board proposed topics for the
joint meeting at ICANN61. If you have any proposed
topics, please share these with the list as soon as
possible. Topics are expected to be submitted by 12
February at the latest. The Board has suggested the
following two topics for its meeting with the GNSO
Council:</span><br></p><ul type="disc"><li style="color:black" class="MsoNormal"><b><span class="size" style="font-size:11pt">What are your key
goals in 2018? </span></b><span class="size" style="font-size:11pt"> The Board is interested
in this question to make sure that its own
priorities are aligned with the community’s
priorities.</span><br></li><li style="color:black" class="MsoNormal"><b><span class="size" style="font-size:11pt">What are your most
relevant longer-term goals?</span></b><span class="size" style="font-size:11pt"> The Board is interested
in this question because discussions about
longer-term goals and strategic planning will
commence soon between the community, the Board and
ICANN org.</span><br></li></ul><p class="MsoNormal"><span class="colour" style="color:black"><span class="size" style="font-size:11pt">Best regards,</span></span><br></p><p class="MsoNormal"><span class="colour" style="color:black"><span class="size" style="font-size:11pt">Marika</span></span><br></p><p class="MsoNormal"><b><i><span class="size" style="font-size:11pt">Marika Konings</span></i></b><br></p><p class="MsoNormal"><i><span class="size" style="font-size:11pt">Vice
President, Policy Development Support – GNSO,
Internet Corporation for Assigned Names and
Numbers (ICANN) </span></i><br></p><p class="MsoNormal"><i><span class="size" style="font-size:11pt">Email: <a href="mailto:marika.konings@icann.org"> <span class="colour" style="color:rgb(5, 99, 193)">marika.konings@icann.org</span></a> </span></i><br></p><p class="MsoNormal"><i><span class="size" style="font-size:11pt"> </span></i><br></p><p class="MsoNormal"><i><span class="size" style="font-size:11pt">Follow
the GNSO via Twitter @ICANN_GNSO</span></i><br></p><p class="MsoNormal"><i><span class="size" style="font-size:11pt">Find
out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso"><span class="colour" style="color:rgb(5, 99, 193)">interactive courses</span></a> and
visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span class="colour" style="color:rgb(5, 99, 193)">GNSO Newcomer pages</span></a>. </span></i><br></p><p class="MsoNormal"> <br></p></div></div><div><br></div><div>______________________________<wbr>_________________<br></div><div> council mailing list<br></div><div> <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br></div><div> <a rel="noreferrer" href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/<wbr>listinfo/council</a><br></div><div> <br></div></blockquote></div></div></div></blockquote><div><br></div>