<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I for one have no real objection to this policy, however I’d like to see it expanded more to provide more detail on the annual cleanup process. How is it proposed that this is done or is this entirely at the AfriNIC’s staff discretion?</div>
<div><br>
</div>
<div>I’d also like to see the policy expanded to put timelines on the cleanups that AfriNIC will conduct so that we aren’t in a constant state of cleanup. The reality is that at the moment, getting AfriNIC to update records can take a LONG LONG time. I point
to the fact that I am still waiting for AfriNIC to complete work related to resource transfers (which really is nothing more than database updates), and it has been exactly 2 months and 1 day since that request was filed.</div>
<div><br>
</div>
<div>If it takes this long to complete basic resource transfers for 5 organisations, how long is it going to take to complete an “annual cleanup” of over 750 members? </div>
<div><br>
</div>
<div>Hence, I feel that where work is required on AfriNIC’s side, I’d like to see them held to specific timelines by policy. If indeed point 3.1.1 is covered by the timelines in 3.2, then the over points are moot.</div>
<div><br>
</div>
<div>I’d also like to see a change in 3.2.4 from “may publish” to “will publish”. I think if we’re going to down the road of publishing things like this, it should not be haphazard, and making it optional will result in exactly that.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Andrew</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, May 18, 2014 at 1:54 PM<br>
<span style="font-weight:bold">To: </span>rpd <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>><br>
<span style="font-weight:bold">Subject: </span>[rpd] New proposal - "AfriNIC Whois Database Update Process" (AFPUB-2014-GEN-001-DRAFT-01)<br>
</div>
<div><br>
</div>
<div dir="ltr">
<p dir="ltr">Dear members,</p>
<p dir="ltr">We have received a new policy - "AfriNIC Whois Database Update Process" (AFPUB-2014-GEN-001-DRAFT-01)<br>
</p>
<p dir="ltr">While this may not be on the agenda of the next public policy meeting, we encourage the community to discuss this on the list and at the upcoming face to face meeting. Public url to the "draft" policy will soon be made available. However the content
is pasted below for comments and discussion from the PDWG/community.</p>
<p dir="ltr">____________________________________________________________________________________________________________________<br>
</p>
<p dir="ltr">Draft Policy name: AfriNIC Whois Database Update Process<br>
Unique identifier: AFPUB-2014-GEN-001-DRAFT-01<br>
Status: New<br>
Submission Date 15 MAY 2014<br>
Author:Jean Robert Hountomey <br>
</p>
<br>
<div>1.Summary of the Problem Being Addressed by this Policy Proposal<br>
<br>
The African network infrastructure is growing with changes and extensions. This growth has brought changes in telecommunication and Internet infrastructure. With the emergence of new operators, mergers and acquisitions, the dynamism brought by the penetration
of Internet technology has required organizational changes with job rotation. The need for accurate whois data has been in the news for years all over the world.<br>
<br>
Inaccurate data is still present in the AfriNIC whois database because changes have occurred in organizations (point of contact, contact information etc.) and object owners have not updated their records. The result is a “No response” from “whois” contacts
listed in the AfriNIC Database.<br>
<br>
The goal of the proposal is setting a process towards ensuring that AfriNIC whois database is updated. A previous policy (AFPUB-2012-GEN-001-DRAFT-02 : AfriNIC Whois Database Clean-up ) was withdrawn by the Author after AfriNIC advised that there was already
an internal process to handle the cleanup of whois data and do general contact update. However it has been noticed that objects in AfriNIC database are not accurate.<br>
<br>
2. Summary of How this Proposal Addresses the Problem<br>
<br>
This proposal asks AfriNIC to maintain accuracy through a periodical database clean up. Furthermore, at least
<br>
once a year or at the renewal of resources, AFRINIC staff should conduct a whois database information validation.<br>
<br>
3. The Proposal<br>
<br>
AfriNIC members are committed through the RSA to maintain their data and keep it accurate. AfriNIC will then
<br>
maintain accuracy of whois information through periodical database clean up or update. AfriNIC will periodically ask object
<br>
owners in the Whois Database to actively check and update the accuracy of data in AfriNIC whois database.<br>
<br>
3.1 Cleanup<br>
<br>
3.1.1 - General Database Cleanup: At the ratification of this policy, AfriNIC staff will conduct a first cleanup by asking all POC present except those who received their objects in less than a year to confirm their POC information. We leave to AfriNIC staff
the discretion to use any communication tool they find useful for this action.<br>
<br>
3.1.2 - Annual Clean up: After the first cleanup, AfriNIC will conduct a cleanup once a year. We leave to AfriNIC's staff to define the period.<br>
<br>
3.1.3 - At the request of additional resources or services, AfriNIC staff will ask the organization to update its records.<br>
<br>
3.2. If a change is requested by another policy.<br>
<br>
In case another AfriNIC policy made mandatory a change or introduce another object, the object owner is required to make this update.<br>
<br>
3.2 Steps<br>
<br>
3.2.1 - AfriNIC staff will ask members to confirm accuracy of their records in the Whois database in a month’s
<br>
timeframe when contacted by email.<br>
<br>
3.2.2 - After one month, AfriNIC Staff will use any communication tools at their discretion to contact
<br>
those who have not answered or those whose email has bounced back.<br>
<br>
3.2.3 - After another month of unresponsive response, the record will be marked invalid.<br>
<br>
3.2.4 - AfriNIC may publish publicly a report about number resources with invalid POC.<br>
<br>
3.2.5 - One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the call to resolve the data inconsistency, AfriNIC may claim the number resources back.<br>
<br>
4. Situation within other RIRs<br>
<br>
- ARIN conducts an annual POC (point of contact) validation process: <br>
<a href="https://www.arin.net/resources/services/poc_validation.html" target="_blank">https://www.arin.net/resources/services/poc_validation.html</a><br>
- At APNIC, there was a similar policy proposed that did not reach consensus and was withdrawn by the author.
<br>
<a href="http://www.apnic.net/__data/assets/file/0006/22857/prop-084-v002.txt" target="_blank">http://www.apnic.net/__data/assets/file/0006/22857/prop-084-v002.txt</a>
<br>
- RIPE NCC<br>
<a href="http://www.ripe.net/data-tools/support/clean-up-of-unreferenced-data" target="_blank">http://www.ripe.net/data-tools/support/clean-up-of-unreferenced-data</a><br>
- LACNIC obligates the resources holders contractually throught their RSA and reviews whois data when resources are requested and updates accordingly<br>
<br>
<p style="text-align:justify"><b>History</b></p>
</div>
<ul style="text-align:justify">
<li>02 Oct. 2012 - AFPUB-2012-GEN-001-DRAFT-02 was withdrawn by the Author.</li></ul>
<p style="text-align:justify"><b>Previous Versions </b></p>
None<br>
<br clear="all">
Kind Regards,<br>
<br>
Seun Ojedeji, Emile Milandou<br>
PDWG Co-Chairs<br>
</div>
</span><br>
<hr>
<font face="Arial" color="Black" size="2">DISCLAIMER: This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please
notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, copy, print, or rely on this email. We cannot accept liability for any statements made which are clearly the sender's own and not expressly made
on behalf of this company or one of its agents.<br>
<br>
</font>
</body>
</html>