<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 10:45:46 Wednesday, 20 January 2016 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
LI.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
DIV.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
TABLE.90ee7c49-625a-40f7-a446-19f7d81ef5deTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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";}
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-family:"Calibri","sans-serif";}
@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 lang="EN-US" link="blue" vlink="purple">
<p class="90ee7c49-625a-40f7-a446-19f7d81ef5de"></p>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree and would add that DIDP appeals, although they potentially could involve a bylaws violation I suppose, would most often involve an independent review
via IRP of the original decision to ensure that it was correct. <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">It seems that the IRP is being stretched in the borrowing. At the very least, there needs to be clarification that on how the IRP should handle these matters
if it is the proper vehicle and, if it is not, what exactly should be created to handle these matters. <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"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Greg Shatan<br>
<b>Sent:</b> Wednesday, January 20, 2016 12:36 AM<br>
<b>To:</b> Avri Doria<br>
<b>Cc:</b> Accountability Cross Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] PTI and the IRP<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Avri,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I agree with your analysis and share your concern. The PTI IRP is fundamentally not a Bylaws issue (or more accurately -- fundamentally not a "violation of the Bylaws" issue).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Having "borrowed" the IRP in an attempt to fill the requirements of the CWG, we can't then pretend that the requirements of the CWG are coterminous with the general design of the IRP. The
CWG's requirements will require a specific statement of the basis on which a claim may be brought -- and it is a different basis than for other IRP claims. This doesn't have to be long, but it does have to be right.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Conversely, if we are truly wedded to the idea that the IRP is a "bylaws court" and nothing more, then it can't be used to satisfy the CWG's requirement and we will need to do something else.
Personally, I don't endorse this position (though it does raise some concern about the ability of the panel to deal with PTI failures, if it is designed to be a bylaws court. That said, I have sufficient faith in the skill of experienced arbitrators to be
able to resolve a variety of disputes.)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Since this a requirement for the transition, we need to resolve this crisply, explicitly and appropriately.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jan 20, 2016 at 12:25 AM, Avri Doria <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
I am uncomfortable with closing the discussion of the new principles for<br>
the IRP. Since we decided not to create a new entity to serve the<br>
requirements of the CWG but rather to make it a function of the IRP, we<br>
need to make sure that the basis for the IRP is fit for purpose before<br>
starting on its implementation.<br>
<br>
The CWG calls for:<br>
<br>
> 1. *Appeal mechanism*. An appeal mechanism, for example in<br>
> the form of an Independent Review Panel, for issues relating to the<br>
> IANA functions. For example, direct customers with non-remediated<br>
> issues or matters referred by ccNSO or GNSO after escalation by the<br>
> CSC will have access to an Independent Review Panel. The appeal<br>
> mechanism will not cover issues relating to ccTLD delegation and<br>
> re-delegation, which mechanism is to be developed by the ccTLD<br>
> community post-transition.<br>
><br>
<br>
I do not see how to define this function in terms of By Laws alone as By<br>
Laws have little to say about negotiated SLAs and the customers' or CSC<br>
complaints. Perhaps it can be done by changes to some of the By Laws,<br>
but I do not see us as having scoped out what those changes need to be.<br>
<br>
So until such time as we have dealt the the policy issues of filling the<br>
CWG's requirements, I would like to register a personal caution, and<br>
thus an objection, to closing the discussion of the basis and standing<br>
for IRP appeals. I do not believe this is merely an implementation<br>
issue. At least not yet.<br>
<br>
avri<br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" target="_blank">https://www.avast.com/antivirus</a><br>
<br>
</p>
</div>
</div>
</div>
<p></p>
<p class="90ee7c49-625a-40f7-a446-19f7d81ef5de"></p>
<hr align="left" color="#58595b" width="200">
<span style="font-size:x-small; color: #004B8D; font-weight: bold; ">Brett</span><span style="font-size:x-small; color: #004B8D; font-weight: bold; "></span>
<span style="font-size:x-small; color: #004B8D; font-weight: bold; ">Schaefer</span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "><br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs</span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "></span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "><br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy</span><br>
<font color="#58595b" size="2">The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002</font><span style="font-size:x-small; color: #58595B; "><br>
202-608-6097</span><br>
<font color="#004b8d" size="2"><a style="COLOR: #004b8d; TEXT-DECORATION: none" href="http://heritage.org/">heritage.org</a><br>
<span style="font-size:x-small; "></span><span style="font-size:x-small; "></span>
<p></p>
</font>
<p></p>
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p></p>
</body>
</html>