<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)"><!--[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:"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:Verdana;
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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
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:0cm;
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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{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 bgcolor=white 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'>On the point highlighted below by Becky and supported by Greg i.e. that both would be desirable, Lise & had the opportunity to discuss this briefly. <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'>To do both does seem to us to cover the bases well and so it appears optimal, assuming the CCWG can work with this i.e. it is a practical outcome for the CCWG.<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'>Agreed that the timing is good both in terms of the CCWG meeting later today and the current work on bylaws.<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'>Thanks,<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'><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><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;color:windowtext'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> Gomes, Chuck [mailto:cgomes@verisign.com] <br><b>Sent:</b> 26 January 2016 14:06<br><b>To:</b> Matthew Shears <mshears@cdt.org>; Greg Shatan <gregshatanipc@gmail.com>; Burr, Becky <Becky.Burr@neustar.biz><br><b>Cc:</b> avri@acm.org; cwg-stewardship@icann.org<br><b>Subject:</b> Re: [CWG-Stewardship] CCWG-ACCT Request for Guidance on PTI - IRP - Please respond by 23h59 UTC Monday 25 January 2016<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>It doesn’t seem to me that that should be hard to fix and the timing is perfect because we are currently working on the draft Bylaws changes.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Chuck<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US 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 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext'> <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>] <b>On Behalf Of </b>Matthew Shears<br><b>Sent:</b> Tuesday, January 26, 2016 6:51 AM<br><b>To:</b> Greg Shatan; Burr, Becky<br><b>Cc:</b> <a href="mailto:avri@acm.org">avri@acm.org</a>; <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br><b>Subject:</b> Re: [CWG-Stewardship] CCWG-ACCT Request for Guidance on PTI - IRP - Please respond by 23h59 UTC Monday 25 January 2016<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>This is an interesting question. Para 107 says: <i>This final proposal attempts to meet all of the above requirements by: ... Establishing a contract between PTI and ICANN that will grant PTI the rights to act as the IFO, and set out the rights and obligations of PTI and ICANN</i><b><br></b><br>Could/should the concerns raised by Becky and Greg be addressed in the "rights and obligations" part of the contract outlined above, and if so does the Draft Proposed Term Sheet in Annex S adequately account for the concerns raised in this thread? (My cursory read suggests that it does not.) <br><br>Matthew<o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-US>On 26/01/2016 04:17, Greg Shatan wrote:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span lang=EN-US style='font-family:"Verdana",sans-serif'>Becky,<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-family:"Verdana",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-family:"Verdana",sans-serif'>That is my impression as well.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-family:"Verdana",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-family:"Verdana",sans-serif'>Greg<o:p></o:p></span></p></div></div><div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US>On Mon, Jan 25, 2016 at 4:05 PM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:<o:p></o:p></span></p><div><div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'>My impression based on the various posts is that we need both a general provision regarding ICANN’s obligation to cause the PTI to fulfill its obligations (the failure to do so would give rise to a standard IRP) and we need something to address SLA failures, etc. with a operational (rather than constitutional) standard of review.<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto'><b><span lang=EN-US style='font-size:9.0pt'>J. Beckwith Burr</span></b><b><span lang=EN-US style='font-size:10.0pt;color:#262626'> </span></b><b><span lang=EN-US style='font-size:9.0pt;color:#3366FF'><br></span></b><b><span lang=EN-US style='font-size:9.0pt;color:#008656'>Neustar, Inc.</span></b><b><span lang=EN-US style='font-size:9.0pt;color:#068658'> </span></b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'>/</span><b><span lang=EN-US style='font-size:9.0pt;color:#068658'> </span></b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'>Deputy General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span lang=EN-US style='font-size:9.0pt;color:gray'><br></span><b><span lang=EN-US style='font-size:9.0pt;color:#008656'>Office:</span></b><b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'> </span></b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'><a href="tel:%2B1.202.533.2932" target="_blank">+1.202.533.2932</a> </span><b><span lang=EN-US style='font-size:9.0pt;color:#008656'>Mobile:</span></b><b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'> </span></b><span lang=EN-US style='font-size:9.0pt;color:#7D7D7D'><a href="tel:%2B1.202.352.6367" target="_blank">+1.202.352.6367</a> </span><strong><span lang=EN-US style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#7D7D7D'>/</span></strong><span lang=EN-US style='font-size:9.0pt;color:#068658'> </span><span lang=EN-US><a href="http://www.neustar.biz" target="_blank"><b><span style='font-size:9.0pt;color:#008656'>neustar.biz</span></b></a><o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 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'>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>><br><b>Date: </b>Monday, January 25, 2016 at 3:22 PM<br><b>To: </b>Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>><br><b>Cc: </b>"<a href="mailto:avri@acm.org">avri@acm.org</a>" <<a href="mailto:avri@acm.org">avri@acm.org</a>>, "<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>><br><b>Subject: </b>Re: [CWG-Stewardship] CCWG-ACCT Request for Guidance on PTI - IRP - Please respond by 23h59 UTC Monday 25 January 2016<o:p></o:p></span></p></div><div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p></div><div><div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'>Becky,<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'>have we specified that there should be such a provision in the Bylaws?<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'>I guess we have left to "implementation" the agreement between ICANN and PTI. I don't believe this has been picked up yet. Am I correct? If so, that should probably change soon.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Verdana",sans-serif'>Greg<o:p></o:p></span></p></div></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'>On Mon, Jan 25, 2016 at 10:45 AM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Presumably if ICANN has an obligation in its Bylaws to ensure that PTI<br>does the right thing, it will need to create the necessary enforcement<br>mechanisms in its relationship with PTI.<br><br><br>J. Beckwith Burr<br>Neustar, Inc. / Deputy<br>General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006<br>Office: <a href="tel:%2B1.202.533.2932" target="_blank">+1.202.533.2932</a> Mobile: <a href="tel:%2B1.202.352.6367" target="_blank">+1.202.352.6367</a> / <a href="http://neustar.biz" target="_blank">neustar.biz</a><br><<a href="http://www.neustar.biz" target="_blank">http://www.neustar.biz</a>><br><br><br><br><br>On 1/25/16, 10:30 AM, "Avri Doria" <<a href="mailto:avri@acm.org">avri@acm.org</a>> wrote:<br><br>>Hi,<br>><br>>Another nagging question I have, and one I think people tell me I am<br>>wrong about becase of MOUs and contracts.<br>><br>>In the PTI environment, given that ICANN remains the representative for<br>>2 of the operational communities, and they resolve their IANA issues<br>>with ICANN based on contracts and MOUs, how do we expect ICANN to get<br>>what it needs from IANA on their behalf?<br>><br>>Will, as today. they just tell IANA what to do and that will be the end<br>>of it.<br>><br>>The other OCs have indicated that any appeals mechanisms we create are<br>>irrelevant to their case - they have their own methods. But these<br>>methods involve ICANN and not PTI. Does ICANN need to appeal on their<br>>behalf? How does it do this?<br>><br>>avri<br>><br>>---<br>>This email has been checked for viruses by Avast antivirus software.<br>><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivir" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_antivir</a><br>>us&d=CwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8<br>>WDDkMr4k&m=sNRRTgQciMa9L6cxsRmapxpj1FEfitYPlAMn4NmB4Gk&s=VjHS6O9uycnwTVSFP<br>>XRCBB11R2TBkKIwjKy1wEj8MaU&e=<br>><br>>_______________________________________________<br>>CWG-Stewardship mailing list<br>><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_</a><br>>listinfo_cwg-2Dstewardship&d=CwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6<br>>X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=sNRRTgQciMa9L6cxsRmapxpj1FEfitYPlAMn4Nm<br>>B4Gk&s=0HwgSD_DtHwhuq9QOacLroSh0USPJ_sMNZMCTVHGh78&e=<o:p></o:p></span></p><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><br>_______________________________________________<br>CWG-Stewardship mailing list<br><a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=6HapdIJul6_Kghgkb89eqFTW7ZOOi_qFE_TfT-h15z0&s=uD5dLPU_fKJNDV-O0vSqyTVMbq1ZOrZJqcWw5QTB_jQ&e=" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></span></p></div></div></div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p></div></div></div></div></div></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><br><br><o:p></o:p></span></p><pre><span lang=EN-US>_______________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US>CWG-Stewardship mailing list<o:p></o:p></span></pre><pre><span lang=EN-US><a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><o:p></o:p></span></pre><pre><span lang=EN-US><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></span></pre></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><o:p> </o:p></span></p><pre><span lang=EN-US>-- <o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span lang=EN-US>Matthew Shears | Director, Global Internet Policy & Human Rights Project<o:p></o:p></span></pre><pre><span lang=EN-US>Center for Democracy & Technology | cdt.org<o:p></o:p></span></pre><pre><span lang=EN-US>E: <a href="mailto:mshears@cdt.org">mshears@cdt.org</a> | T: +44.771.247.2987<o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span lang=EN-US>CDT's Annual Dinner, Tech Prom, is April 6, 2016. Don't miss out - register at cdt.org/annual-dinner.<o:p></o:p></span></pre><table class=MsoNormalTable border=1 cellspacing=3 cellpadding=0 style='border:none;border-top:solid #AAABB6 1.0pt'><tr><td width=131 style='width:78.75pt;border:none;padding:11.25pt .75pt .75pt .75pt'><p class=MsoNormal style='margin-top:22.5pt'><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><span style='text-decoration:none'><img border=0 id="_x0000_i1025" src="https://ipmcdn.avast.com/images/logo-avast-v1.png"></span></a><o:p></o:p></p></td><td width=588 style='width:352.5pt;border:none;padding:15.0pt .75pt .75pt .75pt'><p class=MsoNormal style='margin-top:22.5pt;line-height:13.5pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E'>This email has been sent from a virus-free computer protected by Avast. <br><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><span style='color:#4453EA'>www.avast.com</span></a> <o:p></o:p></span></p></td></tr></table><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p></div></body></html>