<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Bernard,<br />
<br />
I have been thinking about some of this, so a few things come to mind initially:<br /></div>
<blockquote style="border: none; margin: 0px 0px 0px 25px; padding: 0px;">
<div style="indent-level: 1">The mechanism will be available to the “affected” ccTLD Manager, and in cases of (new) delegations also to the unsuccessful applicants. </div>
<div style="indent-level: 1"><br /></div>
</blockquote>
<div dir="auto">That would weed out some of the frivolous appeals. And avoids the situation of a renaming which is a retirement and delegation, that if the ccTLD Manager were not a ccNSO member, it could not appeal, whereas unsuccessful applicants could.<br />
<br />
Then we should figure out language to achieve something like<br /></div>
<blockquote style="border: none; margin: 0px 0px 0px 25px; padding: 0px;">
<div style="indent-level: 1">Any review (application) must be as “wide” as reasonably possible, and all supporting documents that are reasonably available or could have been reasonably available must be submitted with the application or as soon as reasonable after they become available.</div>
<div style="indent-level: 1"><br /></div>
</blockquote>
<div dir="auto">That should weed out more chaff, and avoids multiple appeals, while protecting smaller Managers which do not have lawyers on tap.<br />
<br />
And to weed out further frivolous appeals but on the other hand making this mechanism available also to the smallest/poorest Managers, <br /></div>
<blockquote style="border: none; margin: 0px 0px 0px 25px; padding: 0px;">
<div style="indent-level: 1">we need a fair and reasonable fee mechanism, for example taking the size brackets of the ccNSO contribution as the base.</div>
</blockquote>
<div dir="auto"><br />
from which flows<br /></div>
<blockquote style="border: none; margin: 0px 0px 0px 25px; padding: 0px;">
<div style="indent-level: 1">we either make the non-binding mechanism fully mandatory (and free) before availing oneself of the binding one, or we make appropriate fee/cost requirements.</div>
<div style="indent-level: 1"><br /></div>
</blockquote>
<div dir="auto">I prefer the former.<br />
<br />
And finally should put in something<br /></div>
<blockquote style="border: none; margin: 0px 0px 0px 25px; padding: 0px;">
<div style="indent-level: 1">All reviews of the same decision (by different parties) must be heard as one “case”</div>
<div style="indent-level: 1"><br /></div>
</blockquote>
<div dir="auto">so as to speed things up and contain the cost.<br />
<br />
All,<br />
<br />
please review and comment.<br />
<br />
greetings, el</div>
</div>
<div name="messageSignatureSection"><br />
<div dir="auto">—
<div dir="auto">Sent from Dr Lisse’s iPhone</div>
</div>
</div>
<div name="messageReplySection">On 10. Oct 2021, 23:44 +0200, Patricio Poblete via Ccpdp-rm <ccpdp-rm@icann.org>, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">
<div dir="ltr">Thanks, Bernard,
<div><br /></div>
<div>I don't know if we had an estimate of how often this review mechanism could be used. As I see it, the two main sources of disputes would be retirements and revocations, which we don't see many each year. This might have an impact in the rationale for having a permanent Office of the Administrator, staffed and funded.</div>
<div><br /></div>
<div>Patricio</div>
<div> </div>
</div>
<br />
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Oct 7, 2021 at 11:14 AM Bernard Turcotte via Ccpdp-rm <<a href="mailto:ccpdp-rm@icann.org">ccpdp-rm@icann.org</a>> wrote:<br /></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">All,</div>
<div class="gmail_default" style="font-size:small"><br /></div>
<div class="gmail_default" style="font-size:small">As discussed at our last meeting please find attached an early draft of a non-binding mechanism which we will discuss at our next meeting.</div>
<div class="gmail_default" style="font-size:small"><br /></div>
<div class="gmail_default" style="font-size:small">Bernard Turcotte</div>
<div class="gmail_default" style="font-size:small">ICANN Support to the CCPDP-RM</div>
</div>
_______________________________________________<br />
Ccpdp-rm mailing list<br />
<a href="mailto:Ccpdp-rm@icann.org" target="_blank">Ccpdp-rm@icann.org</a><br />
<a href="https://mm.icann.org/mailman/listinfo/ccpdp-rm" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ccpdp-rm</a><br />
<br />
_______________________________________________<br />
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote>
</div>
_______________________________________________<br />
Ccpdp-rm mailing list<br />
Ccpdp-rm@icann.org<br />
https://mm.icann.org/mailman/listinfo/ccpdp-rm<br />
<br />
_______________________________________________<br />
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<br /></blockquote>
</div>
</body>
</html>