<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</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>
<div>Unless there are details as to </div>
<div><br>
</div>
<div>A.) How this will be accomplished</div>
<div>B.) What level of information / access AfriNIC can ask for to to do this</div>
<div>C.) How the additional cost of the resources required to implement this policy are to be covered</div>
<div>D.) What sort of complaints are covered by 3.3(c) </div>
<div><br>
</div>
<div>I will strongly oppose this policy – it is impractical, unenforceable and hugely open to abuse. Organisation X doesn’t like Organisation Y, Organisation X goes to AfriNIC and goes “omg I think someone is not using their space properly”, Organisation Y
is now under audit and wasting valuable time and effort when its entirely possible their space usage is entirely legitimate. Not to mention wasting AfriNIC time and resources.</div>
<div><br>
</div>
<div>As regards to point (B), what are you going to ask for? An addressing plan? Proof of infrastructure? Some vague log files? If they could have lied on their application, what is stopping them lying on this stuff? Or are you proposing AfriNIC actually
log into their equipment and check their usage? If the latter – the answer is flatly no, not until AfriNIC signs water tight NDA’s and water tight liability contracts that says if they screw anything up, expose anything etc, they accept the liability for
all of it – and since AfriNIC doesn’t have CLOSE to the resources to cover such liability hat ain’t going to happen.</div>
<div><br>
</div>
<div>Seriously – lets get real for a second – let go of the absolute paranoia that’s floating around and realise IPv4 is dead, move on, get some v6, and stop stressing ourselves out about v4 (and wasting precious time and resources trying to micro manage something
that should be 6 foot under the ground already)</div>
<div><br>
</div>
<div>(Hence, I retract my “Unless there are details as to…” and replace it with “I oppose this policy, in entirety, for all the reasons stated above”</div>
<div><br>
</div>
<div>Andrew</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; 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>Saturday, 21 May 2016 at 9:53 AM<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 - "Internet Number Resources Audit by AFRINIC (AFPUB-2016-GEN-001-DRAFT01)"<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>Dear Members,<br>
<br>
We have received a new policy Proposal - "Internet Number Resources Audit by AFRINIC (AFPUB-2016-GEN-001-DRAFT01)"<br>
<br>
Draft Policy name: <span>Internet Number Resources Audit by AFRINIC</span><br>
Unique identifier: AFPUB-2016-GEN-001-DRAFT01<br>
Status: Under Discussion<br>
Submission Date: 18 May 2016<br>
Amends: None<br>
Authors: Amelina Arnaud, Ilunga Kabwika Serge, Jean-Baptiste Millongo<br>
Wafa Dahmani <br>
<br>
Url: <a href="http://afrinic.net/en/library/policies/1741-internet-number-resources-audit-by-afrinic">
http://afrinic.net/en/library/policies/1741-internet-number-resources-audit-by-afrinic</a><br>
<br>
</div>
Text Below:<br>
<br>
<a href="http://www.afrinic.net/en/community/policy-development/policy-proposals/1157-out-of-region-use-of-afrinic-internet-number-resources" target="_blank"><span></span></a><b>1) Introduction</b><br>
<br>
As Internet Number resources are finite, their allocation is based on the operational needs of end-users and Internet Services Providers while avoiding stockpiling in accordance with RFC7020, IPv4 Allocation Policy (AFPUB-2005-V4- 001), IPv6 Allocation and
assignment policy (AFPUB-2013-v6-001) and Policy for Autonomous System Numbers (ASN) Management in the AFRINIC region (AFPUB-2004-ASN-001).<br>
<br>
Section 4 of the Registration Service Agreement (RSA) provides the framework for investigations of the usage of allocated Internet Number resources, defines members’ obligation to cooperate and the measures to be taken by AFRINIC in case of failure to comply.<br>
<br>
The lack of such investigation or regular control can lead to inefficient usage of the Internet Number resources, to stockpiling and other types of abuse.<br>
<br>
<br>
<b>2) Summary of How this Proposal Addresses the Problem</b><br>
<br>
In order to ensure efficient and appropriate use of resources, AFRINIC shall conduct regular audits of resource utilisation held by its members. This would allow recovery of any type of resource, where usage is not in compliance with the RSA. Those resources
can be reallocated for better usage.<br>
<br>
<br>
<b>3) Proposal</b><br>
3.1) The audits shall be based on compliance with the terms outlined in the RSA and Allocation/Assignment Policies.<br>
3.2) The audits cover all allocated or Assigned resources, but priority goes to IPv4 and ASN mappable to two-octet ASN.<br>
3.3) Classes of audit:<br>
<br>
Members to be audited shall be selected according to the following classes:<br>
<br>
<br>
a) Random:<br>
<br>
The member is chosen by AFRINIC at random between members of the following categories:<br>
<br>
Medium and above<br>
IPv6-only Large<br>
EU-AS<br>
<br>
<br>
b) Selected:<br>
A member is selected because of an internal report or due to a lack of contact between the AFRINIC and the member.<br>
<br>
<br>
c) Reported:<br>
The members have requested the audit themselves or there has been a community complaint made against them that requires investigation.<br>
<br>
<br>
3.4 In case of non-compliance and if evidence has been established in accordance with the non-exhaustive list below:<br>
<br>
a) Unjustified lack of visibility of the resource on the global routing table.<br>
b) Breach of AFRINIC policies.<br>
c) Breach of the provisions of the registration service agreement or other legal agreements between the organisation holding the resource and AFRINIC.<br>
d) Evidence that an organisation is no more operating and its blocks have not been transferred.<br>
e) Unauthorised transfers under the provisions of the policies.<br>
<br>
<br>
AFRNIC shall initiate the resource recovery process.<br>
<br>
AFRINIC shall attempt to contact the organisation and correct any discrepancy towards the RSA. If the situation cannot be rectified, AFRINIC shall publish the resources to be recovered for a period of three (3) months; during which the organisation may at any
time, seek compliance. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from AFRINIC databases.<br>
<br>
Any Internet Number Resources recovered under this policy may be assigned/allocated under existing Allocation and Assignment Policies.<br>
<br>
<br>
3.5 Appeal procedure<br>
The audit shall be conducted in full transparency and neutrality. But if the result of the audit does not appear to be fair, the audited members has the right to appeal against the result. Appeals shall follow an arbitration process as defined by AFRINIC, which
shall publish the process and the pool of arbitrators who shall be knowledgeable volunteers from the community.<br>
<br>
<br>
<br>
Outcome of the arbitration process are unequivocal and without appeal.<br>
<br>
3.6 Compliance Report<br>
AFRNIC shall publish an annual report describing the members which have been audited and their level of compliance.<br>
<br>
<br>
<b>4.0 Revision History</b><br>
18 May 2016: First Draft AFPUB-2016-GEN-001-DRAFT01 Posted on RPD list<br>
<br>
<br>
<b>5.0 References</b><br>
<br>
<a href="https://tools.ietf.org/html/rfc7020">https://tools.ietf.org/html/rfc7020</a><br>
<a href="http://afrinic.net/en/services/rs/rsa">http://afrinic.net/en/services/rs/rsa</a><br>
<a href="http://www.afrinic.net/library/policies/126-policy-ipv4-address-allocation-policies">http://www.afrinic.net/library/policies/126-policy-ipv4-address-allocation-policies</a><br>
<a href="http://www.afrinic.net/en/library/policies/122-afpub-2013-v6-001">http://www.afrinic.net/en/library/policies/122-afpub-2013-v6-001</a><br>
<a href="http://www.afrinic.net/en/library/policies/124-afpub-2004-asn-001">http://www.afrinic.net/en/library/policies/124-afpub-2004-asn-001</a><br>
<br>
Best Regards<br>
Relevant Url:<br clear="all">
1. Policy Development process: <a href="http://afrinic.net/en/community/policy-development" target="_blank">
http://afrinic.net/en/community/policy-development</a><br>
<div><br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">------------------------------------------------------------------------<br>
<font color="#888888">
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<span class=""><font color="#888888"><font color="#888888">
<div dir="ltr"><font color="#888888">
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<span><font color="#888888"><font color="#888888">
<div><span style="font-size:12.8px">Sami Salih & </span>Seun Ojedeji</div>
<div dir="ltr">PDWG Co-Chairs</div>
</font></font></span></blockquote>
</font></div>
</font></font></span><br>
</blockquote>
</font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>