<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p><strong>COMMENTS ON THE PROPOSED POLICY FOR THE RETIREMENT OF CCTLDS.</strong></p>
<p><strong>10<sup>th</sup> July, 2020</strong></p>
<p><br /></p>
<p>I am happy at this opportunity to provide Comments on the draft Policy developed for the Retirement of ccTLDs</p>
<p>I commend the synergy in the draft developed by the working group and the traditional role played by the ICANN Board of Directors in serving as the final authority on the removal of a ccTLD from the Root Zone, while this is done after the ICANN Board has reviewed systems deployed by the IFO (staff) and affirmed that all due procedures were properly followed, the report did not state if changes to the ICANN by-laws were envisaged considering the role of the IFO and the ICANN Board of Directors, nor if mechanisms within ICANN need to be restructured to help make this process effective.</p>
<p>Brands that have made massive investments in securing various domain names across the retiring ccTLD should be provided ample time and notice to migrate their data and contents asides switching urls in the public domain. Entities that may have made advanced payments for their domain names would also be desirous of holding on to their domain names until the expiry of their domains validity, hence a 5-year notice of removal in the retirement plan may be subject to the ccTLD, especially where a number of ccTLD allow for domain payments of up to 10 years at a stretch.</p>
<p>Going by the proposal that the IFO must remove a retiring ccTLD from the Root Zone no later than 10 years after having sent a Notice of Removal to the ccTLD Manager, this condition on one hand makes it impossible for ccTLDs to allow advance payments beyond 10 years cumulatively at every given point. On the second hand such contracts may provide users reasons and means to seek legal redress to stop or delay the process until their domain validity expires.</p>
<p>It may be outside the mandate of this working group to determine a price charter for ccTLDs that does not extend beyond 10 years at any given point in time, but ccTLD allowing payments for 10years more creates a binding contract assuring the Registrant that they would be in business for that duration of time and even where good reasons prevail, may truncate the process of retiring a ccTLD until such issues are dealt with..</p>
<p>I would like to recommend that taking into cognizance the concerns of working group members that some Retirement Managers could game the system leading to the numbers of active domains increasing rather than deteriorating, a provision for mandatory system audit at least twice in five years to be conducted by the IFO to determine if the ccTLD being retired is truly winding down its operations or not should be a standard.</p>
<p>I am of the opinion that even If the Functional Manager of the retiring ccTLD does not wish an extension to the Default Retirement Date stated in the Notice of Removal, it should still be mandatory that the Manager produce a Retirement Plan for the ccTLD which would typically include:</p>
<ul>
<li>A copy of the Notice of Removal;</li>
<li>The date when the ccTLD is expected to stop taking registrations, renewals and transfers that exceed the date of removal from the Root Zone. It is important to note that there is a reasonable expectation that the date provided is the earliest practical date for implementing the retirement; and</li>
<li>Details of a Communication Plan to advise the registrants of the Retirement of the ccTLD.</li>
</ul>
<p><br /></p>
<p><br /></p>
<p>I align with the proposal that while a Retirement Plan requesting an extension beyond five (5) years from receipt of the Notice of Removal from the IFO is submitted, in addition to the previously listed items, the following should accompany the plan:</p>
<ul>
<li>The length of the extension requested (a maximum 5 additional years) including the proposed date of the removal of the ccTLD from the Root Zone;</li>
<li>The reasons for requesting an extension; and</li>
<li>An impact analysis which supports the reasons for making the extension request.</li>
</ul>
<p><br /></p>
<p>I wish to however note that the stress tests conducted did not measure how Registrants data and key National values resident on the retiring ccTLDs domain/servers would affect the retirement process especially in the light of multiple data privacy laws.</p>
<p><br /></p>
<p><strong>Lawrence O. Olawale-Roberts.</strong></p>
<p>MD, MicroBoss</p>
<p>Board Member, Nigeria Internet Registration Association (NIRA) and</p>
<p>Member, Business Constituency, ICANN.</p>
<div id="signature">-- <br />
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="top"><img id="preview-image-url" src="https://pbs.twimg.com/profile_images/582224125877477376/iAS-50-Z_400x400.jpg" width="203" height="203" /></td>
<td>
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td colspan="2"><span style="color: #000080;"><strong>Lawrence Olawale-Roberts</strong></span></td>
</tr>
<tr>
<td colspan="2"><span style="color: #ff6600;"><em>Managing Director/CEO</em></span></td>
</tr>
<tr>
<td colspan="2">
<p><strong><img src="http://microboss.org/wp-content/uploads/2017/11/MicroBossLogo.png" /></strong></p>
</td>
</tr>
<tr>
<td valign="top" width="20">p:</td>
<td valign="top"><span style="color: #ff6600;">+2348056 3333 18 / 9</span> <span>m: </span><span style="color: #ff6600;">+2348070892705</span></td>
</tr>
<tr>
<td valign="top" width="20">a:</td>
<td valign="top"><span style="color: #000000;">Suite 7, 1st floor, Right Wing, Z.M.Plaza, Plot 1469, Ahmadu Bello Way, Area 11, Garki 2, Abuja, Nigeria.</span></td>
</tr>
<tr>
<td valign="top" width="20">w:</td>
<td valign="top"><a href="http://www.microboss.org/">www.microboss.org</a> <span>e: </span><a href="mailto:lawrence@microboss.org">lawrence@microboss.org</a></td>
</tr>
<tr>
<td colspan="2"><a href="https://www.facebook.com/Olawale.Roberts"><img src="http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/facebook_sig.png" width="25" height="25" /></a> <a href="https://twitter.com/lawrenceraves"><img src="http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/twitter_sig.png" width="25" height="25" /></a> <a href="https://ng.linkedin.com/in/lawrenceor"><img src="http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/linkedin_sig.png" width="25" height="25" /></a> <a href="https://www.instagram.com/pstlawrence/"><img src="http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/instagram_sig.png" width="25" height="25" /></a></td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td style="text-align: left;" colspan="2"><span style="color: #339966;">This e-mail and any attachments are confidential and may be protected </span><span style="color: #339966;">by legal, professional or other privilege. If you are not the intended </span><span style="color: #339966;">recipient you should not store it, copy it, re-transmit it, use it or </span><span style="color: #339966;">disclose its contents, but should return it to the sender immediately </span><span style="color: #339966;">and delete your copy from your system. The views expressed are those of </span><span style="color: #339966;">the sender and his company MicroBoss. Please </span><span style="color: #339966;">note that whilst we scan all e-mails for viruses we cannot guarantee </span><span style="color: #339966;">that any e-mail is virus-free.</span></td>
</tr>
</tbody>
</table>
</div>
</body></html>