<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div><span></span></div>
<div>
<div><span></span></div>
<div>
<div><span></span></div>
<div>
<div><span></span></div>
<div>
<div>Milton,</div>
<div><br>
</div>
<div>In "<span style="background-color: rgba(255, 255, 255, 0);">The plan was to _<i>transfer</i>_ staff from ICANN to PTI, not to second them. IANA staff would become part of PTI, not a department of ICANN," </span><br>
I accept that it is possible to assume this, but I can't see where we said this.</div>
<div><br>
</div>
<div>I've watched this discussion with some bewilderment. It seems to be way beyond the remit of the CWG to insist that the IANA staff must join PTI against their will or lose their job.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Having been a secondee from one government ministry to another and from my government to an IGO (the European Commission), in both cases it was recognised by my employer AND the host organisation that my loyalty was to the latter
for the period of the secondment. My annual review, for example, was by my line manager in my secondments and was on file as is with my employer.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">For separation, I don't see why secondees affect the situation. As the steward, it would not be in ICANN's interest to undermine the operator, whoever it is. Staff can still be seconded to the new operator (but cannot be forced
to go - but they can't be forced to stay with ICANN or PTO, either).<br>
<br>
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Martin Boyle<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><br>
</p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Sent from my iPhone</span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);"> </span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);"><img width="165" height="23" id="_x0030_6171EF1-7BF4-4B97-951F-DE331471A8A8" src="cid:image001.jpg@01D105C8.15DEB510" alt="cid:image001.jpg@01D0FCF7.DEE0F1F0"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);"> </span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"><a href="http://nominet.uk/"><b>nominet.uk</b></a><b> </b>DD: <a href="tel:+44%20(0)1865%20332251" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="2">+44
(0)1865 332251</a><o:p></o:p></span></font></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Minerva House, Edmund Halley Road, Oxford, OX4 4DQ, United Kingdom</span></p>
</div>
<div><br>
</div>
</div>
<div><br>
On 22 Jun 2016, at 20:29, Mueller, Milton L <<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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]-->
<div class="WordSection1">
<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"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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"> Guru Acharya [<a href="mailto:gurcharya@gmail.com">mailto:gurcharya@gmail.com</a>]
<br>
<br>
</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">While I wholeheartedly support strong separability, I personally don't see a problem with secondment of ICANN staff to PTI. From what I remember, PTI's staff does not have any role to play in the separation
<span style="color:#1F497D"><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">MM: It doesn’t matter what you have or do not have a problem with. The goal now is to implement the proposal, not to re-litigate the proposal. According to the
finalized proposal PTI is not a department of ICANN but an independent legal entity. The plan was to _<i>transfer</i>_ staff from ICANN to PTI, not to second them. IANA staff would become part of PTI, not a department of ICANN.
<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">I think we can all agree that we do not want to see people from ICANN walking into a door and becoming PTI for a few hours and then walking out the door and becoming
ICANN staff. That is not in line with either the spirit or the letter of the proposal. As others have noted, there are loyalty/mission issues with that. It was simply wrong of ICANN to propose it.
<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>
<p class="MsoNormal">That said, I also wish to note that the current separation process is undoubtedly skewed in favour of a very weak form of separability by giving the board the option to reject it twice. However, I don't think secondment of ICANN staff to
PTI has a role in making separability any weaker.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It does make it weaker by tying PTI staff to ICANN and increasing ICANN – and the staff-s resistance to any form of separation.
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>CWG-Stewardship mailing list</span><br>
<span><a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a></span><br>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>