[Gnso-ssc] For your review - draft process to designate GNSO Rep to EC Admin

Tue Jun 13 16:56:37 UTC 2017

Personally I would prefer that the GNSO representative to the EC Admin was not from the leadership team, I accepted it since it seemed to be the position of the majority of the SSC.
I think that it is better if the representative has what I think in English is call it an “arm length” separation from the Council.  This way we can ensure that the representative has to consult the GNSO in every occasion and we diminish the possibility that the representative gives what he thinks is the position of the GNSO Council without consulting previously.  This does not mean that I distrust the actual Council leadership team, it is just that it is a good way to prevent any misunderstanding.
Best regards,
Osvaldo

De: gnso-ssc-bounces at icann.org [mailto:gnso-ssc-bounces at icann.org] En nombre de Susan Kawaguchi
Enviado el: martes, 13 de junio de 2017 01:42 p.m.
Para: Marika Konings
CC: gnso-ssc at icann.org
Asunto: Re: [Gnso-ssc] For your review - draft process to designate GNSO Rep to EC Admin

Thank you Marika for clarifying the process required for the EC admin.  I agree we can still recommend that the EC Admin role be filled by Council leadership team.

Anyone else have thoughts on this additional information?

Susan

On Thu, Jun 8, 2017 at 5:30 PM, Marika Konings <marika.konings at icann.org<mailto:marika.konings at icann.org>> wrote:
Dear All,

Per the SSC discussion, I reached out to our legal colleagues to obtain some further information in relation to whether it would be possible to have the collective of the GNSO Leadership team (GNSO Chair and Council Vice-Chairs) designated as the GNSO representative to the Empowered Community Administration. They pointed out that the Bylaw language states that “Each Decisional Participant shall deliver annually a written certification from its chair or co-chairs to the Secretary designating the individual who shall represent the Decisional Participant on the EC Administration”. As such, under the scenario that the SSC is currently considering, it would be a requirement for the GNSO Leadership team to make a determination who would serve in the role of representative to EC Administration so that this person subsequently can be designated by the GNSO Council. This, however, does not preclude those on the leadership team that have not been designated to step in if/when needed but it would be recommendable to include this possibility as part of the designation so there is clarity around this possibility of an alternate. Based on this information, the process, based on the scenario of having the leadership team make a determination of who from the leadership team would serve in the role as representative to the EC Admin could look as follows:

  1.  GNSO Chair election takes place at ICANN Annual Meeting
  2.  Noting that the Vice-Chair cannot be from the same Stakeholder Group as the Chair, Vice-Chairs may be confirmed prior to the Chair Election only if there is a single Chair candidate or all Chair candidates are from the SG. Otherwise, confirmation of Vice-Chairs may happen after the Chair election.
  3.  GNSO Chair is confirmed upon election as the interim representative to the EC Admin, until such time as the leadership team has had an opportunity to meet and decide who is taking on this role. In case the GNSO Council fails to select a Chair, the existing representative to the EC Admin will remain in that role until such time as a Chair has been elected.
  4.  As soon as possible upon confirmation of the leadership team, the leadership team will meet to decide who is to be designated as GNSO Representative to the EC Admin. Following this determination, this decision is to be confirmed by the GNSO Council as part of the consent agenda. The decision on the designation of the permanent representative to the EC Admin is then communicated to the ICANN Secretary and EC Admin.
  5.  Should at any point during term of the Chair and/or Vice-Chairs there be a change (for example, a resignation or a change in circumstances which may mean the representative is no longer able to perform in this role), the leadership team will communicate this to the GNSO Council as soon as possible together with the name of the individual on the leadership team who will take on this role so that a new designation can be made.
  6.  As part of the designation, it will be made clear that in case of absence or conflict, another member of the leadership team may step in to replace the representative on the EC Admin.

As noted, this is a possible way in which the scenario of having a member of the GNSO leadership team (GNSO Chair and Council Vice-Chairs) serve as the designated representative to the EC Admin, but as always, please feel free to share any comments, edits or alternative scenarios you may have. Following your feedback, the proposed process could be written up in the form of a motion which can then be shared with the GNSO Council for its consideration ahead of ICANN59.

Best regards,

Marika

Marika Konings
Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN)
Email: marika.konings at icann.org<mailto:marika.konings at icann.org>

Follow the GNSO via Twitter @ICANN_GNSO
Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>.

_______________________________________________
Gnso-ssc mailing list
Gnso-ssc at icann.org<mailto:Gnso-ssc at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-ssc

________________________________

El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información

This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-ssc/attachments/20170613/4bdf3550/attachment-0001.html>