<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Would it work to make the following change:? “</span>The specific purpose of the Corporation is to operate exclusively for the benefit of, to perform the functions of and to carry out the purposes of the Internet
Corporation for Assigned Names and Numbers (“<b>ICANN</b>”)<span style="color:#00B0F0"> related to the IANA services.</span><span style="color:#1F497D">”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I agree with Matthew that it is not PTI’s purpose to perform all of ICANN’s functions and purposes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>matthew shears<br>
<b>Sent:</b> Friday, July 15, 2016 5:28 AM<br>
<b>To:</b> Yuko Green; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Purpose of PTI<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Yuko - thanks.<o:p></o:p></p>
<p>As I noted in the CWG chat yesterday I am uncomfortable with this definition of the purpose of PTI: "The specific purpose of the Corporation is to operate exclusively for the benefit of, to perform the functions of and to carry out the purposes of the Internet
Corporation for Assigned Names and Numbers (“<b>ICANN</b>”)."<br>
<br>
This is very broad and very vague. My understanding was that the purpose of the PTI subsidiary was to perform the IANA functions pursuant to an inter-company contract established between ICANN and PTI. This is very different from the proposed language.
Of course we also need to see the inter company agreement to ensure that the purpose of PTI is similarly parametered.<o:p></o:p></p>
<p>Matthew<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 14/07/2016 19:00, Yuko Green wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear members of the CWG,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">From today’s CWG call #82, we stated that we will provide the transcript from the IOTF call where we discussed about the purpose stated within the PTI Bylaws and Articles. Extracted below is the transcript and chat history specifically
around this topic. The whole transcript is available at <a href="https://www.icann.org/uploads/iana_work_session_asset/attachment/373/1467913551526IOTF_Call__14_transcript_06JUL16.pdf">
https://www.icann.org/uploads/iana_work_session_asset/attachment/373/1467913551526IOTF_Call__14_transcript_06JUL16.pdf</a> and the AC room recording at
<a href="https://icann.adobeconnect.com/p3qeid579y7/">https://icann.adobeconnect.com/p3qeid579y7/</a>.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>***Transcript***</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Paul Kane: <span style="font-size:11.5pt">In the articles of association, it says the sole function – apparently I haven’t read it, again I apologize – function of PTI is to serve ICANN. Historically the function of IANA has been to serve
the community, ICANN just happens to be the contract to doing it. And I don’t know if that is correct, if that’s what’s in the articles of incorporation. But if that is, it sort of has lost the raison d’etre of PTI. It is not a service sector of ICANN because
that makes it feel like a department. It’s actually trying to serve a broader community such as the naming community, the protocols and the numbers. But I haven’t read it so I will try and read it so I might be wrong.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.5pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.5pt">Trang Nguyen: </span>Thanks, Paul. Let me – so Section 3 of the articles says this – it does say that the specific purpose of PTI is to operate exclusively for the benefit of and to perform the functions of
and carry out the purposes of ICANN. And I want to go back and double check that again the language that is in the ICANN bylaws that has been adopted because I think some of this is the reflection of what’s included in the ICANN bylaws. So we want to do that
cross check and come back to this group and see how it aligns with – what’s in the ICANN bylaws. But that is currently what is reflected in the PTI articles of incorporation. There are some comments in the chat from James. Things that affect the agreement
are done by contract with ICANN for protocol and numbers means that there needs to be language to that effect in the PTI articles…<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">James Gannon: So, yes, Paul, I had a similar comment from somebody else as well from the IETF area. And I think in I suppose philosophical principle, yes, it is a slight change but I think in the reality the fact that both the numbers and
protocol communities will still contract with ICANN it needs to be very clear in PTI’s documents then that, yes, it is for the purposes of fulfilling the IANA functions it needs to be able to serve the owners of those contracts, which is ICANN still. So I
think philosophically, yes, it doesn’t really sound very right, but I think for the realities of running PTI and for PTI to be accountable through the mechanisms that we’ve built up that there does need to be language like that inside the articles to make
sure that it’s clear that the – those two communities have the right of PTI serving their needs but also then the accountability mechanism that we’ve put into ICANN are also then bound to PTI by that language going backwards. And I think Trang is right that
it’s also reflected in the ICANN bylaws going downwards towards PTI.<o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.5pt"> </span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.5pt">Trang Nguyen: </span>Thank you, James. And I see Russ has similar comments in the chat as well that the contract for the protocol parameters function as well as with the numbers are with ICANN and not PTI.
<o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>***Chat***</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Trang Nguyen: The specific purpose of the Corporation is to operate exclusively for the benefit of, to perform the functions of, and to carry out the purposes of the Internet Corporation for Assigned Names and Numbers, a California nonprofit
public benefit corporation(“ICANN”). <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">James Gannon: I think this was Stephens comment yes? I think that the fact that the agreements are done via contact to ICANN for protocol and numbers means that there needs to be language to that effect in the PTI articles<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">James Gannon: (Sorry no mic)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Paul Kane: A cross check is welcome but I hope you see my point it is off target
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Russ Housley: @Paul, the Numbers and Protocol Parameter communities have their agreements with ICANN, not PTI.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Paul Kane: Good Point Russ<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Russ Housley: @Paul, ICANN is choosing to put that work in PTI.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Russ Housley: @Paul, so PTI is an affiliate of ICANN to perform all of that work<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Paul Kane: ok -thanks<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Yuko Green</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Strategic Programs Manager</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Global Domains Division</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Internet Corporation for Assigned Names and Numbers (ICANN)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Direct Line: +1 310 578 8693</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Mobile: +1 310 745 1517</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">E-mail:
<a href="mailto:yuko.green@icann.org"><span style="color:blue">yuko.green@icann.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><a href="http://www.icann.org/"><span style="color:blue">www.icann.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--------------<o:p></o:p></pre>
<pre>Matthew Shears<o:p></o:p></pre>
<pre>Global Internet Policy and Human Rights<o:p></o:p></pre>
<pre>Center for Democracy & Technology (CDT)<o:p></o:p></pre>
<pre>+ 44 771 2472987<o:p></o:p></pre>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">
<hr size="1" width="99%" noshade="" style="color:#909090" align="center">
</span></div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 11.25pt 0in 6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><a href="https://www.avast.com/antivirus"><span style="text-decoration:none"><img border="0" id="_x0000_i1026" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo"></span></a><o:p></o:p></span></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><span style="font-family:"Calibri","sans-serif";color:#3D4D5A">This email has been checked for viruses by Avast antivirus software.
<br>
<a href="https://www.avast.com/antivirus">www.avast.com</a> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
</body>
</html>