<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Yuko - thanks.</p>
<p>As I noted in the CWG chat yesterday I am uncomfortable with this
definition of the purpose of PTI: <span
style="font-size:12.0pt;font-family: "Times New
Roman","serif";mso-fareast-font-family:"Times
New Roman";mso-ansi-language:
EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA"
lang="EN-US">"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.</span></p>
<p><span style="font-size:12.0pt;font-family: "Times New
Roman","serif";mso-fareast-font-family:"Times
New Roman";mso-ansi-language:
EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA"
lang="EN-US">Matthew<br>
</span></p>
<br>
<div class="moz-cite-prefix">On 14/07/2016 19:00, Yuko Green wrote:<br>
</div>
<blockquote
cite="mid:d25e195f4c184fc4acf870ae60c42c4d@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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">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 moz-do-not-send="true"
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 moz-do-not-send="true"
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***<o:p></o:p></b></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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.5pt"><o:p> </o:p></span></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><u><span style="font-size:11.5pt"><o:p><span
style="text-decoration:none"> </span></o:p></span></u></b></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><o:p> </o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>***Chat***<o:p></o:p></b></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;color:black">Yuko
Green<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Strategic
Programs Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Global
Domains Division<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Internet
Corporation for Assigned Names and Numbers (ICANN)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Direct
Line: +1 310 578 8693<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Mobile:
+1 310 745 1517<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">E-mail:
<a moz-do-not-send="true" href="mailto:yuko.green@icann.org"><span
style="color:blue">yuko.green@icann.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><a
moz-do-not-send="true" href="http://www.icann.org/"><span
style="color:blue">www.icann.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CWG-Stewardship mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--------------
Matthew Shears
Global Internet Policy and Human Rights
Center for Democracy & Technology (CDT)
+ 44 771 2472987</pre>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/antivirus">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>