<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-IE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Alissa’s points make good sense to me.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Jonathan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Alissa Cooper [mailto:alissa@cooperw.in] <br><b>Sent:</b> 31 May 2016 17:58<br><b>To:</b> Alan Greenberg <alan.greenberg@mcgill.ca><br><b>Cc:</b> Alissa Cooper via Iotf <iotf@icann.org><br><b>Subject:</b> Re: [IOTF] Question on PTI implementation approach<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On May 29, 2016, at 5:49 PM, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>I am obviously missing something here.<br><br>In that case of "separation" ICANN would still be the steward of the IANA names functions. It would be the entity contracting with the successor of PTI. So it could well make arrangements for the employees to continue with the successor organization. Or not if the employees were in fact part of the problem.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Exactly. If the employees are part of the problem and the performance of the functions has gotten so bad that the community wants to use the separation process, that process should not be hamstrung by the fact that ICANN committed to offering the employees the option of being employed by the successor. <o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><br>Regardless of the details, as the steward of the names function, is not likely to be inclined to take action to sabotage things.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I wasn’t referencing the sabotage of anything. I think what needs to be clear is that, as Avri says, the employees always have their choice of employ. ICANN’s role is to make sure the choices within ICANN’s control are available to those employees, but not to control what other choices they may have with successors whose hiring decisions are not within ICANN’s purview.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Alissa<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><br>Alan<br><br>At 29/05/2016 07:48 PM, Greg Shatan wrote:<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>I think it does mean that ICANN will allow its seconded employees to leave the employ of ICANN and go to PTI or to a successor (if that's the way the separation is occurring). I can't see any other interpretation. As Chuck points out, it also seems to assure these ICANN employees that, if they do not want to join PTI/successor or are not offered a job there, that they will have the option of continuing as ICANN employees.<br><br>The secondment scenario does create some concern that ICANN could encourage these employees to stay with ICANN in the event of a separation (or to put it another way, discourage these employees from moving from secondee to employee within the IANA provider (PTI or successor)). This could have negative security and stability impacts. We may want an assurance from ICANN that it will not solicit or otherwise encourage the seconded employees to remain ICANN employees rather than continue to be part of the IANA provider. I could see some awkward moments otherwise.<br><br>Greg <br><br><br>On Sat, May 28, 2016 at 10:44 AM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>Good questions Alissa.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>It seems to me that with or without the sentence you quote, the affected employees would have the three options assuming that the applicable organizations gave them the employment option. Like you say, ICANN may not have any control over what the successor might do, but it is at least committing to offer employment to the seconded employees if they want it so this clause may be of some assurance to those employees.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'><span style='color:#888888'>Chuck</span><o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>-----Original Message-----<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>From: <a href="mailto:iotf-bounces@icann.org">iotf-bounces@icann.org</a> [<a href="mailto:iotf-bounces@icann.org"> mailto:iotf-bounces@icann.org</a>] On Behalf Of Alissa Cooper<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Sent: Saturday, May 28, 2016 2:12 AM<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>To: Alissa Cooper via Iotf<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>Subject: [IOTF] Question on PTI implementation approach<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>Hi all,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>Apologies that I have not been able to make the last few calls.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>I was reviewing the PTI implementation approach document and I noticed that Section 2.3 says:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>"In the event of separation, ICANN commits to an effectuating an orderly transition, including providing the seconded employees the option of employment with the affiliate, the successor, or ICANN. This commitment will be reflected in the naming function contract between ICANN and PTI.â<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>What does it mean for ICANN to provide the option of employment with the successor? I assume by "successor" what is meant is the new operator to replace PTI, for one or more IANA functions. In that case, ICANN wouldn't likely have the option of offering employment by the successor -- the successor would be a separate organization altogether, which is the point of separation. Does this mean ICANN won't prevent PTI employees from being employed by the successor (e.g., it wonât impose some sort of non-compete agreement)? If that is not what it means, what does it mean?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>Also, given that the second sentence says that this commitment will be reflected specifically in the naming function contract, does that mean it will not also apply to the seconded employees performing the other two functions (to the extent that employees are assigned wholly to either or both of the other two functions)?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'>I read through the transcript for call #10 but did not see these questions raised on the call.<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Thanks,<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Alissa<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>_______________________________________________<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>IOTF mailing list<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><a href="mailto:IOTF@icann.org">IOTF@icann.org</a><o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><a href="https://mm.icann.org/mailman/listinfo/iotf">https://mm.icann.org/mailman/listinfo/iotf</a><o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>_______________________________________________<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>IOTF mailing list<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><a href="mailto:IOTF@icann.org">IOTF@icann.org</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'><a href="https://mm.icann.org/mailman/listinfo/iotf">https://mm.icann.org/mailman/listinfo/iotf</a><o:p></o:p></p><p class=MsoNormal><br>Content-Type: text/plain; charset="us-ascii"<br>Content-Transfer-Encoding: 7bit<br>Content-Disposition: inline<br>X-Microsoft-Exchange-Diagnostics:<br> 1;SN1PR0301MB2030;9:0+ZiF373MgecgwhfjdnXDj9HBCxQlxBfcYlS6xEgVnnZsuI8gFRsXN/m+rAP6oPjL+vN+5XlPhm/+EVYFquY8LJBrCmI4P+SUs/O8moMS3LX/znyb34B3xoIJbiSSwuTdOrLmtt24VsigyO6F5MHw0/nQ6D5Za/ieTviw6oJQbAmSIAzS38lY4IxJeAnFWMw<br><br>_______________________________________________<br>IOTF mailing list<br><a href="mailto:IOTF@icann.org">IOTF@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/iotf">https://mm.icann.org/mailman/listinfo/iotf</a><o:p></o:p></p></blockquote></div><p class=MsoNormal>_______________________________________________<br>IOTF mailing list<br><a href="mailto:IOTF@icann.org">IOTF@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/iotf">https://mm.icann.org/mailman/listinfo/iotf</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>