[IOT] possible webinar to SOs/ACs for establishing standing panel

[McAuley, David]

Dear members of the IRP IOT,



I have tried to outline a possible webinar/presentation to SOs/ACs to help them get up to speed on selecting a Standing Panel. The time is upon us for thinking through how this will work and how the SOs/ACs can prepare to act.



My thoughts are below. This falls under agenda item #5 for our call tomorrow. I hope to ask Sam or Liz to comment on training as well - and is there an opportunity to use ICANN60 to further/finish this effort.



Best wishes to all,

David



David McAuley

Sr International Policy & Business Development Manager

Verisign Inc.

703-948-4154





Suggested outline of Webinar for SOs/ACs relative to establishing IRP Standing Panel



>From Bylaw (Section 4.3):



1.      ICANN shall "in consultation with the [SOs/ACs]" initiate four-step process to establish standing panel (Section 4.3(j)(ii)):



   a.   Initiate tender process for admin support to IRP, consult IRP IOT;



   b.   ICANN issue a call for Expressions of Interest (EoI) from potential panel members - and work with SOs/ACs and the Board to identify and solicit applications from well-qualified candidates and to conduct initial review/vetting of applications.



   c.   SOs/ACs shall nominate a slate of proposed panel members from well-qualified candidates so identified;



   d.   Final selection subject to Board confirmation (not to be unreasonably withheld) - appointments to five-year terms.



   e.   Reasonable efforts "shall be taken" to achieve cultural, linguistic, gender, and legal tradition diversity, and diversity by Geographic region (Section 4.3(j)(iv)).



2.      Qualifications of members of Standing Panel - Bylaw 4.3(j)(i):



   a.   Significant relevant legal expertise in one or more of these areas:



                                                                  i.      International law;

                                                                ii.      Corporate governance;

                                                              iii.      Judicial systems;

                                                              iv.      Alternative dispute resolution and/or arbitration.



   b.   Knowledge, developed over time, regarding the DNS and ICANN's Mission, work, policies, practices, and procedures.



   c.   Members to be provided (at a minimum) training provided by ICANN on the workings and management of the Internet's unique identifiers and other appropriate training as recommended by the IRP IOT.



   d.   From Section 4.3(q): Members must be independent of ICANN and its SOs/ACs, and thus:



                                                                  i.      Have initial and ongoing duty of conflicts-of-interest disclosure;



                                                                ii.      Additional independence requirements as developed by IRP IOT (may include term-limits and limits on post-term appointments to ICANN).



   Additional Matters:



1.      Review/comment draft process flow.



2.      For IRP IOT - Create a rule for designation of a Chief Panelist (for efficiency and to ensure adherence to purposes of IRP) See Section 4.3(n)?



3.      For SOs/ACs:



   a.   Define decision-making process among SOs/ACs and authorizing representatives to participate.



   b.   Review methods for vetting/assessing candidates:

                                                                              i.      Establish method;

                                                                            ii.      Ensure appropriate confidentiality - balancing candidate-confidentiailty with community transparency;

                                                                          iii.      Records handling;

                                                                          iv.      Communications to candidates.

   c.   Interviewing process



4.      For ICANN:



   a.   Manage process flow and notifications under process flow;



   b.   Post call for EoI;











-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/iot/attachments/20170816/ef39c343/attachment-0001.html>