<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 14 (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;}
@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:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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";
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;}
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";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Let’s let Sharon and Sam help us word this as planned on the call yesterday.<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";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> matthew shears [mailto:mshears@cdt.org]
<br>
<b>Sent:</b> Wednesday, July 20, 2016 1:07 PM<br>
<b>To:</b> Seun Ojedeji<br>
<b>Cc:</b> Lise Fuhr; Andrew Sullivan; cwg-stewardship@icann.org; jrobinson@afilias.info; Flanagan, Sharon; Gomes, Chuck<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>Not sure I see the need or value of that additional clause. Unless there is a very good legal reason for doing so we should avoid layering this with unnecessary qualifiers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 20/07/2016 17:51, Seun Ojedeji wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>That could work as well(even though I prefer Andrew's modification), but not without including "...exclusively for the benefit of,.." in the text which will then result to the following:
<o:p></o:p></p>
<p>"The specific purpose of the corporation is to perform the IANA functions on behalf of, and exclusively for the benefit of, the Internet Corporation for Assigned Names and Numbers (“*ICANN*”)."<o:p></o:p></p>
<p>That ensures that PTI remains member(i.e ICANN) driven.<o:p></o:p></p>
<p>Regards<br>
Sent from my LG G4<br>
Kindly excuse brevity and typos<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 20 Jul 2016 5:41 p.m., "matthew shears" <<a href="mailto:mshears@cdt.org">mshears@cdt.org</a>> wrote:<o:p></o:p></p>
<div>
<p>I'm wondering if we even need to go to that next level. In the Services Agreement draft it says: "WHEREAS, following the IANA Stewardship Transition, PTI will perform the IANA<br>
functions on behalf of ICANN;"<o:p></o:p></p>
<p>So rather than making it more vague/complicated than necessary, why wouldn't the PTI bylaws state the following:
<o:p></o:p></p>
<pre>"The specific purpose of the corporation is to perform the IANA functions on behalf of the Internet Corporation for Assigned Names and Numbers (“*ICANN*”)."<o:p></o:p></pre>
<p>That is its purpose. Thanks.<o:p></o:p></p>
<p>Matthew<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 20/07/2016 17:18, Jonathan Robinson wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Copying in Sharon from Sidley as suggested by Greg on yesterday's CWG call.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Jonathan<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: Gomes, Chuck [<a href="mailto:cgomes@verisign.com" target="_blank">mailto:cgomes@verisign.com</a>] <o:p></o:p></pre>
<pre>Sent: 19 July 2016 14:31<o:p></o:p></pre>
<pre>To: 'Andrew Sullivan' <a href="mailto:ajs@anvilwalrusden.com" target="_blank"><ajs@anvilwalrusden.com></a>; <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><o:p></o:p></pre>
<pre>Subject: Re: [CWG-Stewardship] Purpose of PTI<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Andrew's suggestion works for me.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Chuck<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">mailto:cwg-stewardship-bounces@icann.org</a>] On Behalf Of Andrew Sullivan<o:p></o:p></pre>
<pre>Sent: Tuesday, July 19, 2016 9:26 AM<o:p></o:p></pre>
<pre>To: <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><o:p></o:p></pre>
<pre>Subject: Re: [CWG-Stewardship] Purpose of PTI<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I think you are rapidly walking in to angry terminological disputes that will delay the incorporation of PTI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What about saying something like "relating to certain Internet registries and certain Internet Domain Name System zones, consistent with ICANN's Mission," or something like that?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>A<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Tue, Jul 19, 2016 at 09:22:53AM -0400, Greg Shatan wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>I suggest considering something more specific than "relating to IANA <o:p></o:p></pre>
<pre>services" (especially since the second word in the paragraph is<o:p></o:p></pre>
<pre>"specific") in stating the purpose of PTI, since "IANA services" is <o:p></o:p></pre>
<pre>not a defined term nor is it self-explanatory. Rather it is a "term <o:p></o:p></pre>
<pre>of art," and undefined terms of art are generally to be avoided <o:p></o:p></pre>
<pre>wherever possible in drafting legal documents.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>We could use the current statement of purpose in the ICANN Articles as <o:p></o:p></pre>
<pre>a jumping off point, i.e.:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The specific purpose of the Corporation is to operate exclusively for <o:p></o:p></pre>
<pre>the benefit of, to perform the functions of and to carry out the <o:p></o:p></pre>
<pre>purposes of the Internet Corporation for Assigned Names and Numbers <o:p></o:p></pre>
<pre>(“*ICANN*”), namely (i) coordinating the assignment of Internet <o:p></o:p></pre>
<pre>technical parameters as needed to maintain universal connectivity on <o:p></o:p></pre>
<pre>the Internet; (ii) performing and overseeing functions related to the coordination of the Internet Protocol ("<o:p></o:p></pre>
<pre>*IP*") address space; (iii) performing and overseeing functions <o:p></o:p></pre>
<pre>related to the coordination of the Internet domain name system <o:p></o:p></pre>
<pre>("*DNS*"); and (iv) overseeing operation of the authoritative Internet DNS root server system.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I recognize that we'll probably want to change some of the verbs here <o:p></o:p></pre>
<pre>to more accurately reflect ICANN/IANA's role vs. that of the IETF and <o:p></o:p></pre>
<pre>RIRs, but I think this provides a good starting place for an <o:p></o:p></pre>
<pre>appropriately specific statement of purpose.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Greg<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Fri, Jul 15, 2016 at 11:35 AM, Sivasubramanian M <o:p></o:p></pre>
<pre><a href="mailto:isolatedn@gmail.com" target="_blank"><isolatedn@gmail.com></a><o:p></o:p></pre>
<pre>wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Dear Chuck,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Fri, Jul 15, 2016 at 8:06 PM, Gomes, Chuck <a href="mailto:cgomes@verisign.com" target="_blank"><cgomes@verisign.com></a> wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Would it work to make the following change:? “The specific purpose <o:p></o:p></pre>
<pre>of the Corporation is to operate exclusively for the benefit of, to <o:p></o:p></pre>
<pre>perform the functions of and to carry out the purposes of the <o:p></o:p></pre>
<pre>Internet Corporation for Assigned Names and Numbers (“*ICANN*”) related to the IANA services.”<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
<pre><span style="font-family:"Cambria Math","serif""></span>Even without <span style="font-family:"Cambria Math","serif""></span>the change, 'related to IANA services' is implied, <o:p></o:p></pre>
<pre>but there is no harm in saying it explicitly. When PTI operates for <o:p></o:p></pre>
<pre>the benefit of ICANN, and ICANN is built up on the foundation of a <o:p></o:p></pre>
<pre>fair accountability framework it, it necessarily follows that PTI <o:p></o:p></pre>
<pre>would act in global public interest.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Sivasubramanian M<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p> </o:p></pre>
<pre>I agree with Matthew that it is not PTI’s purpose to perform all of <o:p></o:p></pre>
<pre>ICANN’s functions and purposes.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Chuck<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>*From:* <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [mailto:<o:p></o:p></pre>
<pre><a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>] *On Behalf Of *matthew shears<o:p></o:p></pre>
<pre>*Sent:* Friday, July 15, 2016 5:28 AM<o:p></o:p></pre>
<pre>*To:* Yuko Green; <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><o:p></o:p></pre>
<pre>*Subject:* Re: [CWG-Stewardship] Purpose of PTI<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hi Yuko - thanks.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>As I noted in the CWG chat yesterday I am uncomfortable with this <o:p></o:p></pre>
<pre>definition of the purpose of PTI: "The specific purpose of the <o:p></o:p></pre>
<pre>Corporation is to operate exclusively for the benefit of, to <o:p></o:p></pre>
<pre>perform the functions of and to carry out the purposes of the <o:p></o:p></pre>
<pre>Internet Corporation for Assigned Names and Numbers (“*ICANN*”)."<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This is very broad and very vague. My understanding was that the<o:p></o:p></pre>
<pre>purpose of the PTI subsidiary was to perform the IANA functions <o:p></o:p></pre>
<pre>pursuant to an inter-company contract established between ICANN and <o:p></o:p></pre>
<pre>PTI. This is very different from the proposed language. Of course <o:p></o:p></pre>
<pre>we also need to see the inter company agreement to ensure that the <o:p></o:p></pre>
<pre>purpose of PTI is similarly parametered.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Matthew<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On 14/07/2016 19:00, Yuko Green wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Dear members of the CWG,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>From today’s CWG call #82, we stated that we will provide the <o:p></o:p></pre>
<pre>transcript from the IOTF call where we discussed about the purpose <o:p></o:p></pre>
<pre>stated within the PTI Bylaws and Articles. Extracted below is the <o:p></o:p></pre>
<pre>transcript and chat history specifically around this topic. The <o:p></o:p></pre>
<pre>whole transcript is available at<o:p></o:p></pre>
<pre><a href="https://www.icann.org/uploads/iana_work_session_asset/attachment/37" target="_blank">https://www.icann.org/uploads/iana_work_session_asset/attachment/37</a><o:p></o:p></pre>
<pre>3/1467913551526IOTF_Call__14_transcript_06JUL16.pdf<o:p></o:p></pre>
<pre>and the AC room recording at <a href="https://icann.adobeconnect.com/p3qeid579y7/" target="_blank">https://icann.adobeconnect.com/p3qeid579y7/</a>.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>****Transcript****<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Paul Kane: In the articles of association, it says the sole <o:p></o:p></pre>
<pre>function – apparently I haven’t read it, again I apologize – <o:p></o:p></pre>
<pre>function of PTI is to serve ICANN. Historically the function of <o:p></o:p></pre>
<pre>IANA has been to serve the community, ICANN just happens to be the <o:p></o:p></pre>
<pre>contract to doing it. And I don’t know if that is correct, if that’s what’s in the articles of incorporation.<o:p></o:p></pre>
<pre>But if that is, it sort of has lost the raison d’etre of PTI. It is <o:p></o:p></pre>
<pre>not a service sector of ICANN because that makes it feel like a <o:p></o:p></pre>
<pre>department. It’s actually trying to serve a broader community such <o:p></o:p></pre>
<pre>as the naming community, the protocols and the numbers. But I <o:p></o:p></pre>
<pre>haven’t read it so I will try and read it so I might be wrong.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Trang Nguyen: Thanks, Paul. Let me – so Section 3 of the articles <o:p></o:p></pre>
<pre>says this – it does say that the specific purpose of PTI is to <o:p></o:p></pre>
<pre>operate exclusively for the benefit of and to perform the functions <o:p></o:p></pre>
<pre>of and carry out the purposes of ICANN. And I want to go back and <o:p></o:p></pre>
<pre>double check that again the language that is in the ICANN bylaws <o:p></o:p></pre>
<pre>that has been adopted because I think some of this is the <o:p></o:p></pre>
<pre>reflection of what’s included in the ICANN bylaws. So we want to do <o:p></o:p></pre>
<pre>that cross check and come back to this group and see how it aligns <o:p></o:p></pre>
<pre>with – what’s in the ICANN bylaws. But that is currently what is <o:p></o:p></pre>
<pre>reflected in the PTI articles of incorporation. There are some <o:p></o:p></pre>
<pre>comments in the chat from James. Things that affect the agreement <o:p></o:p></pre>
<pre>are done by contract with ICANN for protocol and numbers means that <o:p></o:p></pre>
<pre>there needs to be language to that effect in the PTI articles…<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>James Gannon: So, yes, Paul, I had a similar comment from somebody <o:p></o:p></pre>
<pre>else as well from the IETF area. And I think in I suppose <o:p></o:p></pre>
<pre>philosophical principle, yes, it is a slight change but I think in <o:p></o:p></pre>
<pre>the reality the fact that both the numbers and protocol communities <o:p></o:p></pre>
<pre>will still contract with ICANN it needs to be very clear in PTI’s <o:p></o:p></pre>
<pre>documents then that, yes, it is for the purposes of fulfilling the <o:p></o:p></pre>
<pre>IANA functions it needs to be able to serve the owners of those <o:p></o:p></pre>
<pre>contracts, which is ICANN still. So I think philosophically, yes, <o:p></o:p></pre>
<pre>it doesn’t really sound very right, but I think for the realities <o:p></o:p></pre>
<pre>of running PTI and for PTI to be accountable through the mechanisms <o:p></o:p></pre>
<pre>that we’ve built up that there does need to be language like that <o:p></o:p></pre>
<pre>inside the articles to make sure that it’s clear that the – those <o:p></o:p></pre>
<pre>two communities have the right of PTI serving their needs but also <o:p></o:p></pre>
<pre>then the accountability mechanism that we’ve put into ICANN are <o:p></o:p></pre>
<pre>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></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Trang Nguyen: Thank you, James. And I see Russ has similar comments <o:p></o:p></pre>
<pre>in the chat as well that the contract for the protocol parameters <o:p></o:p></pre>
<pre>function as well as with the numbers are with ICANN and not PTI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>****Chat****<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Trang Nguyen: The specific purpose of the Corporation is to <o:p></o:p></pre>
<pre>operate exclusively for the benefit of, to perform the functions <o:p></o:p></pre>
<pre>of, and to carry out the purposes of the Internet Corporation for <o:p></o:p></pre>
<pre>Assigned Names and Numbers, a California nonprofit public benefit corporation(“ICANN”).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>James Gannon: I think this was Stephens comment yes? I think that <o:p></o:p></pre>
<pre>the fact that the agreements are done via contact to ICANN for <o:p></o:p></pre>
<pre>protocol and numbers means that there needs to be language to that <o:p></o:p></pre>
<pre>effect in the PTI articles<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>James Gannon: (Sorry no mic)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Paul Kane: A cross check is welcome but I hope you see my point it <o:p></o:p></pre>
<pre>is off target<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Russ Housley: @Paul, the Numbers and Protocol Parameter communities <o:p></o:p></pre>
<pre>have their agreements with ICANN, not PTI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Paul Kane: Good Point Russ<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Russ Housley: @Paul, ICANN is choosing to put that work in PTI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Russ Housley: @Paul, so PTI is an affiliate of ICANN to perform all <o:p></o:p></pre>
<pre>of that work<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Paul Kane: ok -thanks<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>*Yuko Green*<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Strategic Programs Manager<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Global Domains Division<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Internet Corporation for Assigned Names and Numbers (ICANN)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Direct Line: <a href="tel:%2B1%20310%20578%208693" target="_blank">+1 310 578 8693</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mobile: <a href="tel:%2B1%20310%20745%201517" target="_blank">+1 310 745 1517</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>E-mail: <a href="mailto:yuko.green@icann.org" target="_blank">yuko.green@icann.org</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="http://www.icann.org" target="_blank">www.icann.org</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<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><o:p> </o:p></pre>
<pre>Global Internet Policy and Human Rights<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Center for Democracy & Technology (CDT)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="tel:%2B%2044%20771%202472987" target="_blank">+ 44 771 2472987</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>[image: Avast logo] <a href="https://www.avast.com/antivirus" target="_blank"><https://www.avast.com/antivirus></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This email has been checked for viruses by Avast antivirus software.<o:p></o:p></pre>
<pre><a href="http://www.avast.com" target="_blank">www.avast.com</a> <a href="https://www.avast.com/antivirus" target="_blank"><https://www.avast.com/antivirus></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Sivasubramanian M<o:p></o:p></pre>
<pre><a href="https://www.facebook.com/sivasubramanian.muthusamy" target="_blank"><https://www.facebook.com/sivasubramanian.muthusamy></a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Andrew Sullivan<o:p></o:p></pre>
<pre><a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CWG-Stewardship mailing list<o:p></o:p></pre>
<pre><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></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><a href="tel:%2B%2044%20771%202472987" target="_blank">+ 44 771 2472987</a><o:p></o:p></pre>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></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>
</div>
</body>
</html>