<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
It may interest those without a long history in ICANN and At-Large to know that the ALAC initiated (and I Chaired) the only modern-era PDP that related to registrant rights - the Post-expiration domain name recovery PDP which led to the Expired Registration
Recovery Policy (ERRP). This Policy helps ensure that registrants do not inadvertently let their domains expire, and if they do, ensures that they are alerted to the fact and have an opportunity to recover them.
<br>
<br>
There is a (mild) user connection in that Internet users do appreciate that the web sites that they use do not suddenly disappear overnight! During the course of the PDP, we were well supported by the GNSO Business Constituency. There was one relalatively passive
NCUC participant in the PDP, but there was virtually no real support from the NCUC.<br>
<br>
So we do have a good track record of supporting registrants, and particularly those who do not have corporate departments looking after their portfolios.<br>
<br>
The difference between that PDP and more recent situations is that there was a individual user benefit and more importantly no individual user negative impact.<br>
<br>
Where there IS a conflict between the needs of registrants (who happen to be individual users) and the non-registrant individual users, we have a long history of supporting the non-registrant individual users - a position I support and hope that At-Large continues
to support. If we do not, we are not being true to our ICANN Bylaw mandate.<br>
<br>
Alan<br>
<br>
<br>
<br>
<br>
<br>
At 28/06/2019 12:08 AM, Seun Ojedeji wrote:<br>
<blockquote type="cite" class="cite" cite="">Sent from my mobile<br>
Kindly excuse brevity and typos<br>
<br>
On Thu, 27 Jun 2019, 16:06 Evan Leibovitch, <<a href="mailto:evan@telly.org">evan@telly.org</a>> wrote:<br>
<dl><dd>On Thu, 27 Jun 2019 at 04:40, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a> > wrote:<br>
</dd><dd> <br>
</dd><dd> <br>
<dl>
<dl><dd>We do not need to defend registrants, half of GNSO already does that. We are uniquely tasked with speaking for those who are completely outside the ICANN food chain. If we are incapable of finding a distinct voice, that's on us.<br>
<br>
</dd></dl>
<br>
<dd>SO: Well your statement above does not seem be inline with the bylaws<br>
<br>
</dd></dl>
<br>
</dd><dd>Exactly how?<br>
<br>
</dd><dd>The reference to ALAC is in Section 12.2(b). Please indicate the discrepancies,<br>
<br>
</dd><dd>This will be interesting.<br>
<br>
</dd></dl>
<br>
SO: It's actually section 12.2(d) and the point is that the section didn't say registrants were excluded from "individual internet end users". However I reiterate that I do agree (and definitely appreciate the well thought out illustration by Robert) that registrant's
interest should not be our only focus as ALAC and I really don't think it's been the only focus in practice.<br>
<br>
Regards<br>
<dl><br>
<br>
<dd>-- <br>
</dd><dd>Evan Leibovitch, Toronto Canada<br>
</dd><dd>@evanleibovitch or @el56<br>
<br>
</dd></dl>
_______________________________________________<br>
At-Large mailing list<br>
At-Large@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" eudora="autourl">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org/" eudora="autourl">http://atlarge.icann.org</a><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" eudora="autourl"> https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" eudora="autourl"> 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>
</body>
</html>