ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Fwd: [Soac-infoalert] Community Input and Advice Process Session in Toronto

  • To: GNSO Council <council@xxxxxxxxxxxxxx>
  • Subject: [council] Fwd: [Soac-infoalert] Community Input and Advice Process Session in Toronto
  • From: Stéphane Van Gelder <stephane.vangelder@xxxxxxxxx>
  • Date: Thu, 4 Oct 2012 17:00:28 +0200
  • List-id: council@xxxxxxxxxxxxxx
  • References: <CC9354A3.33CA9%marika.konings@icann.org>
  • Sender: owner-council@xxxxxxxxxxxxxx

Councillors, FYI.

Stéphane



Début du message réexpédié :

> De : Marika Konings <marika.konings@xxxxxxxxx>
> Objet : [Soac-infoalert] Community Input and Advice Process Session in Toronto
> Date : 4 octobre 2012 15:02:56 HAEC
> À : "soac-infoalert@xxxxxxxxx" <soac-infoalert@xxxxxxxxx>
> 
> Dear SO/AC Leaders,
> 
> As you may have seen, ICANN Staff posted a document on Community Input and 
> Advice Process for public comment on 24 September (see 
> http://www.icann.org/en/news/public-comment/input-advice-function-24sep12-en.htm).
>  In addition, a session has been scheduled in Toronto to discuss this subject 
> (see http://toronto45.icann.org/node/34195). The objective of this public 
> comment forum and the discussion in Toronto is to obtain community input on 
> the process by which the ICANN Board seeks advice from the community on 
> topics that are not subject to formal policy development processes. It is 
> hoped that these discussions could lead to a consistent and predictable 
> process to be adopted by the ICANN Board for such inquiries. 
> 
> For the meeting in Toronto we are putting together an informal panel 
> discussion during which we would like to hear from the different SO/ACs how 
> they currently deal which such requests from the Board and provide their 
> views on the questions that were also outlined in the discussion paper (see 
> http://www.icann.org/en/news/in-focus/accountability/input-advice-function-24sep12-en.pdf):
> Should standardized processes be created for the Board's receipt of community 
> input and advice?
> If so, should such a procedure be standardized across ICANN SOs/ACs, aligned 
> with the current existing procedures, or should there be some flexibility 
> among the SOs/ACs (certain parts are required for all, while other parts may 
> be developed by the respective SO/Acs)
> How should the Board request this input and advice?
> What is the most effective and efficient method to deal with the issue topic 
> identified? Should it be a working group, could current procedures be used? 
> Who determines which method will be used?
> Should working groups be chartered for each initiative?
> How are different parts of the ICANN community expected to work together in 
> these efforts?
> What minimum public consultation requirements, if any, should be required 
> within this function?
> Who within ICANN lead this effort?
> We would like to encourage you and/or members of your SO/AC to attend this 
> session to share your views. If you have any suggestions for panel members, 
> please feel free to share those off-list with me. The session takes place on 
> Monday 15 October from 13.30 – 14.45 local time in room Metro Centre. 
> 
> With best regards,
> 
> Marika
> 
> Marika Konings
> Sr. Policy Director
> ICANN
> 
> 
> _______________________________________________
> soac-infoalert mailing list
> soac-infoalert@xxxxxxxxx
> https://mm.icann.org/mailman/listinfo/soac-infoalert



<<< Chronological Index >>>    <<< Thread Index >>>