<div>Hi Renata,<br></div><div><br></div><div>I'm going to rehash a conversation I had with you privately, because it's now on the list: ICANN does not care that you cancelled your trip to San Juan because of a family emergency. So please do not worry about this. I know you are, but please don't. This is not an example of resources being mishandled, and ICANN org does not see it this way either.<br></div><div><br></div><div>Now that has been said... it might be a useful exercise for us to table what resources ICANN gives us. I did ask Finance for one, but they are extremely reluctant to prepare such a table. I think they worry we will use it compare ourselves to other SO/ACs (which we might - and we might be upset if we saw another part of the community receiving more support than we do). But the reason why I think it would be useful is because we do receive a lot of 'soft' resources from ICANN, not just Maryam. We get Adobe Connect, we get the dial-outs (which are surprisingly expensive), we get the communications support (i.e. when I ordered NCUC stickers and Comms reimbursed me), if we ask enough times, we get translation/interpretation on a call. There might be other support too that we don't appreciate today, but would feel if it is disappeared.. <br></div><div><br></div><div>So ICANN <i>does</i> give us a lot of support. The question is, is it the right support?<br></div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Ayden <br></div></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><div>-------- Original Message --------<br></div><div> On 16 February 2018 1:56 AM, Renata Aquino Ribeiro <raquino@gmail.com> wrote:<br></div><div> <br></div><blockquote class="protonmail_quote" type="cite"><div dir="ltr"><div>[observer]<br></div><div><br></div><div>Hi<br></div><div><br></div><div>(1st message here so hope I'm not pulverized in beam of lava coming from my computer as I speak up about this)<br></div><div><br></div><div>As a current Chair, thankfully with administrative support (1, yet there is), (limited) meeting attendance support for the group, I will just note that we do not take lightly our resources currently.<br></div><div>There are several criteria put in place for use of resources, previously, during and after the meetings. <br></div><div>It takes time for a member to do well on writing, contributing to WGs and many other activities. Participating in meetings accelerates that learning time and yes, CROP activities help immensely too.<br></div><div><br></div><div>So I do not see this [hindering volunteer participation] as saving cost measure from any volunteer organization. It is rather a very shortsighted move which can concentrate even further an organization in the hands of those who can buy their ticket. <br></div><div><br></div><div>The real reason I came to comment here as that, yes, I am one of those who could probably be singled out as an example of travel which was allocated and not completed as I won't be with you in ICANN61. That decision was also not taken lightly and the after effects of it just keep coming. <br></div><div><br></div><div>So I guess I would only hope that the tone that we debate travel allocation is not only about saving a few pennies but also seeing the organization from a broader perspective. Specific cases or not. CROP or meeting support. There is no other volunteer organization that I know of so narrow minded about discussing support more than ICANN currently<br></div><div><br></div><div>And not only the deletion of CROP but its silent assassination after being labelled a success w/out any hint of prior investigation or consultation to the community or announcement is only a prelude of even worse practices to come. <br></div><div><br></div><div>Discussing at least the arbitrary decision should be done, at least as preparedness for other arbitrary decisions to come. <br></div><div><br></div><div>Best,<br></div><div><br></div><div>Renata<br></div><div><br></div><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div>On Thu, Feb 15, 2018 at 9:22 PM, Rafik Dammak <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>></span> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class="gmail_quote"><div dir="ltr"><div class="gmail_extra">Hi Ayden,<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I just send my response to Stephanie at the same time. I am more cautious about this and won't really support bringing the topic for the reasons I explained.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I think there is a conflation of 2 separate issues here: expectations from elected officers and members in term of behavior and accountability and the impact of the budget on our activities as SG.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">the former can be discussed, while I would like to understand what are the specific concerns. I know there were some issues and I don't want to single out individuals. I am also worried if there are some general insinuations substantiated or not. there is enough misunderstanding and so we need to move here carefully. We raised previously the communication issues and we are trying to make an improvement here but still to be done. I am only speaking about the policy part and so PC and councilors, I cannot speak about other committees or constituencies activities.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">for the budget, I agree we can advise being more carefulness of how we are using the existing resources. as I explained to many of you in private, I think we get too complacent and dependent on ICANN support e.g. expanded travel support and seeing that we are linking travel support to be active on PDPs (e.g. using it as an incentive) while the work is mostly done in working groups and intersessionally . <br></div><div class="gmail_extra">For councilors support, I am not worried since, in fact, that is at GNSO council level and not SG. I think we can suggest being cautious for now and acknowledge that we have now may not be available in few years and think how we can do better (and also defining priorities). there was the time that admin work was done by the chair (I was the last chair to do that before we get admin support :)). Crisis can lead to more creative and original thinking.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><div>Rafik<br></div><div> <br></div><div class="gmail_quote"><div><div class="h5">2018-02-16 9:03 GMT+09:00 Ayden Férdeline <span dir="ltr"><<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>></span>:<br></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class="gmail_quote"><div><div class="h5"><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></div><div class="m_-2481389104279629553m_3915081762148852322HOEnZb"><div class="m_-2481389104279629553m_3915081762148852322h5"><div><div class="h5"><div>On 15 February 2018 5:53 PM, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoront<wbr>o.ca</a>> wrote:<br></div><div><br></div></div></div><blockquote type="cite" class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923protonmail_quote"><div><div class="h5"><p><br></p><div class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-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="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-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="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-forward-container">cheers SP<br></div></div></div><div class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-forward-container"><div><div class="h5"><div>-------- Forwarded Message
-------- <br></div><table class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-email-headers-table" cellspacing="0" cellpadding="0" border="0"><tbody><tr><th align="RIGHT" valign="BASELINE" nowrap="">Subject:<br></th><td>Re: [council] Reminder - topics for meeting with ICANN
Board at ICANN61<br></td></tr><tr><th align="RIGHT" valign="BASELINE" nowrap="">Date:<br></th><td>Thu, 15 Feb 2018 22:33:19 +1100<br></td></tr><tr><th align="RIGHT" valign="BASELINE" nowrap="">From:<br></th><td>Heather Forrest <a class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-txt-link-rfc2396E" href="mailto:haforrestesq@gmail.com"><haforrestesq@gmail.com></a><br></td></tr><tr><th align="RIGHT" valign="BASELINE" nowrap="">To:<br></th><td>Marika Konings <a class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-txt-link-rfc2396E" href="mailto:marika.konings@icann.org"><marika.konings@icann.org></a><br></td></tr><tr><th align="RIGHT" valign="BASELINE" nowrap="">CC:<br></th><td><a class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a> <a class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><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></div><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div><div class="h5"><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></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US"><div class="m_-2481389104279629553m_3915081762148852322m_-3447169733158720923m_-7776137299844508011WordSection1"><div><div class="h5"><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 class="MsoNormal" style="color:black"><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 class="MsoNormal" style="color:black"><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></div></div><p class="MsoNormal"><i><span class="size" style="font-size:11pt">Find
out more about the GNSO by taking our <span id="m_-2481389104279629553m_3915081762148852322TSRSpan_249" class="m_-2481389104279629553m_3915081762148852322TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553m_3915081762148852322TSRWebRatingIcon"></span><span id="m_-2481389104279629553TSRSpan_260" class="m_-2481389104279629553TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553TSRWebRatingIcon"></span><a style="background-color:rgb(184,234,184)" href="http://learn.icann.org/courses/gnso"><span class="colour" style="color:rgb(5, 99, 193)">interactive courses</span></a> and
visiting the <span id="m_-2481389104279629553m_3915081762148852322TSRSpan_250" class="m_-2481389104279629553m_3915081762148852322TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553m_3915081762148852322TSRWebRatingIcon"></span><span id="m_-2481389104279629553TSRSpan_261" class="m_-2481389104279629553TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553TSRWebRatingIcon"></span><a style="background-color:rgb(184,234,184)" 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><span class=""><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></span><div><span id="m_-2481389104279629553m_3915081762148852322TSRSpan_251" class="m_-2481389104279629553m_3915081762148852322TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553m_3915081762148852322TSRWebRatingIcon"></span><span id="m_-2481389104279629553TSRSpan_262" class="m_-2481389104279629553TSRSpan"><img style="width:16px;height:16px;border:0px" class="m_-2481389104279629553TSRWebRatingIcon"></span><a style="background-color:rgb(184,234,184)" href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer">https://mm.icann.org/mailman/l<wbr>istinfo/council</a><br></div><div><br></div></blockquote></div></div></div></blockquote><div><br></div></div></div><div><span class=""><br>______________________________<wbr>_________________<br> NCSG-PC mailing list<br> <a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br> <a rel="noreferrer" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br> </span></div></blockquote></div><div><br></div></div></div><div><br></div><div>______________________________<wbr>_________________<br></div><div> NCSG-PC mailing list<br></div><div> <a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br></div><div> <a rel="noreferrer" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br></div><div> <br></div></blockquote></div></div></div></blockquote><div><br></div>