Hi Katrina, David I agree with most of your responses, particularly with regard to “It looks that the group lacks a full picture of the needs of various SO/ACs”. We certainly do lack the full picture and I believe that if we understood the needs of the respective SO/ACs, and more generally what each SO/AC considers the purpose of ICANN meetings, we will better understand some of the problems we continually experience related to scheduling. I would add one qualifier and that is that the GNSO is not a homogenous group and as such we will need to drill down to Stakeholder Groups and Consiturencies. Similarly, we should take this into account in determing the size of this planning group. I’m not convinced we need a Charter as I believe this could be an unnecessary distraction. We run into two repeat problems – what is worthy of a High Interest Topic or Cross-Community Discussion subject and how do we reduce the number of conflicting sesions. If we can spend some time trying to solve these problems we should have a clearer path to developing a schedule people are more comfortable with. I would also note that the MSWG had a number of guiding principles that I believe could be helpful in these discussions. Thanks Donna Vice Chair, GNSO Council Donna Austin: Neustar, Inc. Policy and Industry Affairs Manager Cell: +1.310.890.9655 Email: donna.austin@neustar.biz<mailto:donna.austin@neustar.biz> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify me immediately and delete the original message. Follow Neustar: [cid:image001.png@01CC3CD3.5F595DC0] Facebook<http://www.facebook.com/neustarinc> [cid:image002.png@01CC3CD3.5F595DC0] LinkedIn<http://www.linkedin.com/company/5349> [cid:image003.png@01CC3CD3.5F595DC0] Twitter<http://www.twitter.com/neustar> P Please consider the environment before printing this e-mail. From: soac-leaders-icann59-bounces@icann.org [mailto:soac-leaders-icann59-bounces@icann.org] On Behalf Of Katrina Sataki Sent: Thursday, March 30, 2017 2:11 AM To: 'David Olive' <david.olive@icann.org>; soac-leaders-icann59@icann.org Subject: Re: [Soac-leaders-icann59] SOAC ICANN59 Planning Group - Organizational Issues Dear David, Thank you very much for initiating the discussion on the efficiency and effectiveness of agenda planning. Hereby I try to summarise the views of myself and my colleague Alejandra Reynoso, the Chair of the ccNSO Meeting Programme Working Group. We also note that Eberhard has already responded, and we believe our responses are very much aligned with his.
First, please confirm, if you have not already, your participation in this group by replying to me directly with your confirmation or to note who might be interested in taking that role on behalf of your community. I have heard from many of you and just need others to confirm. (See list below).
The two of us confirm, however we remain hopeful that a more efficient solution will be found.
We now have 34 SOAC representative on this planning/coordination group for ICANN59.
a) Is this the right size to for the group to do its work?
No.
b) Should we limit the group to this number? Expand it? Narrow it?
Narrow it. Significantly! Each SO/AC should designate one person to: a) Aggregate information from their respective SO/ACs b) Present the views of their SO/ACs c) Decide on behalf of their SO/ACs
c) Other suggestions?
It looks that the group lacks a full picture of the needs of various SO/ACs. We strongly suggest that each SO/AC documents its requirements/expectations per type of meeting and shares them with others. To date every time, after huge planning efforts, we have heard “but our SO/AC needs 2,3,4,5 full days of meetings” or “but we need to have a meeting with X-men”. It means that something is wrong in the process. We do not know and do not understand each other’s needs. If someone has the FULL picture, could you share it with the rest of us? It would allow us to identify problems and propose solutions.
a) What escalation process might work best in this situation to arrive at a decision to resolve session conflicts?
In our view conflicting sessions are inevitable. One can not expect people to spend resources (time, money) to attend a meeting and then go to a session that is of no interest to them. This surely outweighs the issue for those who are not able to choose between several interesting sessions. One just needs to set priorities. In addition, just proposing an interesting session is not enough, it should be organised properly!
a) How should we formalize this group?
Each SO/AC designate a person to represent their interests.
b) Does it need a charter in the short or long term?
Yes. Not sure we can make it before ICANN 59, but we definitely need a charter to which we all commit, including ICANN the organization and the Board.
c) Who would be willing to help contribute to that effort over the longer term?
We are definitely willing to help in shaping the process. Kindest regards, Katrina Sataki, Chair of the ccNSO Alejandra Reynoso, Chair of the ccNSO Meeting Programme Working Group SOAC ICANN59 e-mail list [cid:image001.png@01D2A926.0F8261A0] alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca> alejandra.reynoso@cctld.gt<mailto:alejandra.reynoso@cctld.gt> andrei@rol.ru<mailto:andrei@rol.ru> aso-chairs@aso.icann.org<mailto:aso-chairs@aso.icann.org> bverd@verisign.com<mailto:bverd@verisign.com> cwilson@21cf.com<mailto:cwilson@21cf.com> donna.austin@neustar.biz<mailto:donna.austin@neustar.biz> el@lisse.na<mailto:el@lisse.na> farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com> gbunton@tucows.com<mailto:gbunton@tucows.com> german@nro.net<mailto:german@nro.net> gregshatanipc@gmail.com<mailto:gregshatanipc@gmail.com> h.raiche@internode.on.net<mailto:h.raiche@internode.on.net> haforrestesq@gmail.com<mailto:haforrestesq@gmail.com> hcarrascob@gmail.com<mailto:hcarrascob@gmail.com> hilaliaziz@yahoo.fr<mailto:hilaliaziz@yahoo.fr> jbladel@godaddy.com<mailto:jbladel@godaddy.com> katrina@nic.lv<mailto:katrina@nic.lv> kdrstoll@gmail.com<mailto:kdrstoll@gmail.com> leonfelipe@sanchez.mx<mailto:leonfelipe@sanchez.mx> mcknight.glenn@gmail.com<mailto:mcknight.glenn@gmail.com> ncsg@tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info> ocl@gih.com<mailto:ocl@gih.com> patrik@frobbit.se<mailto:patrik@frobbit.se> pdiaz@pir.org<mailto:pdiaz@pir.org> rafik.dammak@gmail.com<mailto:rafik.dammak@gmail.com> rysgsecretariat@gmail.com<mailto:rysgsecretariat@gmail.com> sb.inapp@gmail.com<mailto:sb.inapp@gmail.com> secretariat@icannregistrars.org<mailto:secretariat@icannregistrars.org> thomas.schneider@bakom.admin.ch<mailto:thomas.schneider@bakom.admin.ch> tom@acig.com.au<mailto:tom@acig.com.au> tonyarholmes@btinternet.com<mailto:tonyarholmes@btinternet.com> wolf-ulrich.knoben@t-online.de<mailto:wolf-ulrich.knoben@t-online.de> David A. Olive Senior Vice President Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212<tel:+90.212.999.6212> Mobile: + 1. 202.341.3611<tel:+%201.%20202.341.3611> Mobile: +90.533.341.6550<tel:+90.533.341.6550>
