<div dir="ltr"><div>Well in that setup, item 1 will obviously be the issue (assuming 2 and 3 accepts). That said, considering that PTI is expected to be accountable to the community and considering that each community would already have their respective review teams (like for names we have the CSC), i wonder why it will be important again for the communities to sit on the board. <br><br>Either using ICANN board or ICANN staff that are not operational staff of IANA seem like a workable option<br><br></div>Cheers!<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 25, 2015 at 2:19 PM, Kieren McCarthy <span dir="ltr"><<a href="mailto:kierenmccarthy@gmail.com" target="_blank">kierenmccarthy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>In this whole process, I had always assumed:</div>
<div><br></div>
<div>* 1 Board member from names community</div>
<div>* 1 Board member from numbers community</div>
<div>* 1 Board member from protocols community</div>
<div>* 1 IANA staff member</div>
<div>* 1 ICANN Board member</div>
<div><br></div>
<div>Let each group decide on its representative.</div>
<div><br></div>
<div>Simple, balanced, effective. </div>
<div><br></div>
<div>
<span>I think the most important thing would be to have as little politics and process as possible.</span><br></div>
<div><br></div>
<div><br></div>
<div>Kieren</div>
<div>
<br>-<br>[sent through phone]</div><div class="HOEnZb"><div class="h5">
<br><br><div class="gmail_quote"><p>On Mon, May 25, 2015 at 5:23 AM, Gomes, Chuck <span dir="ltr"><<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>Alan,
<br><br>Assuming a PTI Board of 5 or larger, two registry related Directors would not be in a preferential position in terms of majority. In my opinion, having a couple Directors who understand the functioning of the IFO in meeting TLD registry needs would increase the chances that the Board would " have the requisite skills and knowledge to do that quickly and effectively".
<br><br>Chuck
<br><br>-----Original Message-----
<br>From: Alan Greenberg [mailto:<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>]
<br>Sent: Sunday, May 24, 2015 11:57 AM
<br>To: Gomes, Chuck; <a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>; <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>
<br>Subject: Re: [CWG-Stewardship] PTI Board Composition
<br><br>Chuck, the ALAC has not reach consensus as to whether the PTI Board should be MS or not, but we have definitely reach closure on the PTI Board NOT having registries in a preferential position to other stakeholders (if indeed we end up with a MS PTI Board).
<br><br>In my personal opinion, the PTI Board will have relatively little to do in a steady-state situation where everything is working well.
<br>However, if things are NOT going well, it is the PTI Board that would need to be the first line of recourse in fixing it, and it must have the requisite skills and knowledge to do that quickly and effectively.
<br><br>Alan
<br><br>At 24/05/2015 10:25 AM, Gomes, Chuck wrote:
<br>>Avri,
<br>>
<br>>It is not clear to me that the NomCom's mission and makeup is the right
<br>>fit to appoint PTI Directors, and particularly a majority of them.
<br>>
<br>>I haven't tested this idea with others yet, but I kind of like the idea
<br>>of having one each of the ICANN Directors elected by the ccNSO and GNSO
<br>>serve on the PTI Board. In an ICANN membership structure, the ccNSO or
<br>>GNSO could remove their appointed directors if they were not
<br>>accountability.
<br>>
<br>>Chuck
<br>>
<br>>-----Original Message-----
<br>>From: <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>
<br>>[mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>] On Behalf Of Avri Doria
<br>>Sent: Sunday, May 24, 2015 8:49 AM
<br>>To: <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>
<br>>Subject: [CWG-Stewardship] PTI Board Composition
<br>>
<br>>Hi,
<br>>
<br>>I would like to put a proposal on the table on the composition of the
<br>>PTI Board.
<br>>
<br>>Specifically
<br>>
<br>>On 22-May-15 18:32, Avri Doria wrote:
<br>> > * On the PTI Board, I believe it should be minimal, so instead of
<br>> > having a balanced multstakeholder set of individuals, it should
<br>> have a majority
<br>> > of representatives (s)elected by a multistakeholder modality. e.g 1
<br>> > ICANN Staff, 1 PTI Staff, 3 selected by ICANN Nomcom.
<br>>
<br>>Personally, I propose:
<br>>
<br>>1 ICANN Staff as selected by ICANN President and endorsed by ICANN
<br>>Board
<br>>1 PTI Staff, typically the Sr. Officer of the PTI, i.e its President or
<br>>Executive Director or their designee
<br>>3 Nomcom Selections
<br>>various liaisons as agreed after cross operational community
<br>>discussions
<br>>
<br>>This PTI Board would have fewer people in it than the PTI staff has,
<br>>but would be large enough for some degree of diversity.
<br>>
<br>>While in a formal sense, this would seem to be an outside Board, given
<br>>that the majority is picked by the ICANN community instead of the ICANN
<br>>staff, it is an insider board when considered from the perspective of
<br>>ICANN as a multistakeholder run organization.
<br>>
<br>>It avoids the problem of deciding that one stakeholder type is more
<br>>appropriate that another, but allows the community on an annual basis
<br>>to decide which skills and knowledge are most important using a well
<br>>established ICANN method. The skills and knowledge may vary over time,
<br>>including considerations such as operational experience, financial
<br>>skill, international legal knowledge, security capability, root zone
<br>>operator perspective, community policy perspective, DNS protocol or
<br>>system design expertise. Those selected by the ICANN Nomcom could be
<br>>community insiders or outside experts, as decided by each Nomcom
<br>>according to the perceived needs at that time. The set of
<br>>considerations and needs would be decided on by the ICANN Nomcom in
<br>>consultation with ICANN Board & Staff, the multistakeholder community
<br>>and PTI staff, according to Nomcom's normal current and future
<br>>practices.
<br>>
<br>>In terms of the current discussions, it allows us to defer certain
<br>>decisions, such as which skill and knowledge categories are most
<br>>appropriate until they can address future understandings. It avoid
<br>>having the CWG micromanage the future of the PTI Board, yet leaves it
<br>>under the community's control.
<br>>
<br>>
<br>>thanks
<br>>avri
<br>>
<br>>---
<br>>This email has been checked for viruses by Avast antivirus software.
<br>><a href="http://www.avast.com" target="_blank">http://www.avast.com</a>
<br>>
<br>>_______________________________________________
<br>>CWG-Stewardship mailing list
<br>><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a>
<br>><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<br>>_______________________________________________
<br>>CWG-Stewardship mailing list
<br>><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a>
<br>><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<br><br>_______________________________________________
<br>CWG-Stewardship mailing list
<br><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a>
<br><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<br></p></blockquote></div><br></div></div><br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">alt email:<a href="http://goog_1872880453" target="_blank"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The key to understanding is humility - my view !<br></blockquote></blockquote></font><br></div></div>
</div>