<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks Chuck made a point that I should have made clearer, I was specifically referring to an IANA staff member on the assumption that IANA staff were moving
over to the PTI, if that IANA staff member was still in ICANNS direct employ (Presumably some from GDD under the current org chart) then yes wouldn’t foresee any governance issues as there would then be no conflict of interest for said staff member.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-James<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Gomes, Chuck [mailto:cgomes@verisign.com]
<br>
<b>Sent:</b> Monday, May 25, 2015 5:47 PM<br>
<b>To:</b> James Gannon; Kieren McCarthy<br>
<b>Cc:</b> avri@acm.org; cwg-stewardship@icann.org<br>
<b>Subject:</b> RE: [CWG-Stewardship] PTI Board Composition<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Although I am not arguing one way or the other about whether staff members should be on the board. I think it is fairly common for organizations to put one
of their senior staff members on the Board of an affiliate.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> James Gannon [<a href="mailto:james@cyberinvasion.net">mailto:james@cyberinvasion.net</a>]
<br>
<b>Sent:</b> Monday, May 25, 2015 9:30 AM<br>
<b>To:</b> Kieren McCarthy; Gomes, Chuck<br>
<b>Cc:</b> <a href="mailto:avri@acm.org">avri@acm.org</a>; <a href="mailto:cwg-stewardship@icann.org">
cwg-stewardship@icann.org</a><br>
<b>Subject:</b> RE: [CWG-Stewardship] PTI Board Composition<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Without wading into this discussion just going to make the point with the exception of the CEO its extremely rare to have staff members on the board of their
employer and would usually be advised against as best practice in my knowledge. Have we received any legal advice on possible ‘restrictions’ as to the composition of the PTI board, even if as best practice rather than legal prohibitions?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-James<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Kieren McCarthy<br>
<b>Sent:</b> Monday, May 25, 2015 2:20 PM<br>
<b>To:</b> GomesChuck<br>
<b>Cc:</b> <a href="mailto:avri@acm.org">avri@acm.org</a>; <a href="mailto:cwg-stewardship@icann.org">
cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] PTI Board Composition<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">In this whole process, I had always assumed:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">* 1 Board member from names community<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* 1 Board member from numbers community<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* 1 Board member from protocols community<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* 1 IANA staff member<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">* 1 ICANN Board member<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Let each group decide on its representative.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Simple, balanced, effective. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think the most important thing would be to have as little politics and process as possible.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kieren<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
-<br>
[sent through phone]<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p>On Mon, May 25, 2015 at 5:23 AM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<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 [<a href="mailto:alan.greenberg@mcgill.ca">mailto:alan.greenberg@mcgill.ca</a>]
<br>
Sent: Sunday, May 24, 2015 11:57 AM <br>
To: Gomes, Chuck; <a href="mailto:avri@acm.org">avri@acm.org</a>; <a href="mailto:cwg-stewardship@icann.org">
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">cwg-stewardship-bounces@icann.org</a>
<br>
>[<a href="mailto:cwg-stewardship-bounces@icann.org">mailto: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">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">http://www.avast.com</a> <br>
> <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">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<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">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<br>
<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">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
<o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>