<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello</p>
<p>I have reviewed the policy proposal and I find that part of it is
already part of the resource assignment process reviewing a
member's resource when necessary but not at random, this proposal
is unnecessary and therefore I am oppose it as it is now.<br>
</p>
<p>At BCP 12 (<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/bcp12">https://tools.ietf.org/html/bcp12</a>) under Section 2.1
says that RIR may request information about resource utilization
at any time and if that is not available measures can be taken. I
don't see a problem with that as long there is a motivation.</p>
<p>What I believe is bad and contra-productive is to make it at a
random in a kind of 'inverted Lottery'.<br>
When resources are allocated by the RIR there is a fair amount of
checks that must be done to ensure its proper utilization, so by
default there is no need to make random checks on ASNs and take
that whole process in good faith for the time bein.<br>
In the other hand if a ASN has been purchased or merged with
another then it's the case to make another review. The same way it
makes sense to conduct this procedure when there is a clear
motivation as a complaint and elements to support a investigation.<br>
</p>
<p>Making random checks only serves to increase significantly the
RIR operational costs and also the ASN's as well as most will
probably be fine.</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 06/04/2019 12:12, Arnaud AMELINA
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGDMR_f1MAUvtmUMoRFhxToc2xaiHJNmmDwpWaxnn-ZaEGi+ZA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Hi Ernest and Co-chairs, <br>
</div>
<div><br>
</div>
<div>Please find below an update of our Policy proposal
"Internet Number Resources Review by AFRINIC", for
future discussions on the list. <br>
</div>
<div><br>
</div>
<div>Regards <br>
</div>
<div><br>
</div>
<div>-------------------------------------------------------------------------------
Begin
---------------------------------------------------------------------------------<br>
<br>
Name : Internet Number Resources Review by AFRINIC
(Draft 7)<br>
Ref. Name: AFPUB-2016-GEN-001-DRAFT07<br>
Status: Under Discussion<br>
Date: 6 April 2019<br>
<br>
Authors:<br>
(a) Amelina A. A. Arnaud | <<a
href="mailto:arnaud.amelina@togorer.tg"
moz-do-not-send="true">arnaud.amelina@togorer.tg</a>>
| AUF/TogoRER<br>
(b) Jean-Baptiste Millogo |<<a
href="mailto:jean.millogo@orange.com"
moz-do-not-send="true">jean.millogo@orange.com</a>>|
Orange Burkina <br>
(c) Marcus ADOMEY <<a
href="mailto:madomey@ug.edu.gh" moz-do-not-send="true">madomey@ug.edu.gh</a>>
| University of Ghana<br>
<br>
13.0 Summary of the Problem Being Addressed by this
Policy Proposal<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 CPM 5.5, IPv6 Allocation and
assignment policy CPM 6.5 and Policy for Autonomous
System Numbers (ASN) Management in the AFRINIC region
CPM 7.0.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. The lack
of such investigation or regular control can lead to
inefficient usage of the Internet Number resources, to
stockpiling and other type of abuses.<br>
<br>
13.0.1 Summary of How this Proposal Addresses the
Problem<br>
<br>
In order to ensure efficient and appropriate use of
resources, AFRINIC shall conduct regular reviews of
resource utilization 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>
13.0.2 Proposal<br>
<br>
The policy proposal will modify the CPM as follows:<br>
<br>
Insert a section 13 to the CPM as follows:<br>
<br>
13.0 Internet Number Resources Review<br>
<br>
Regular reviews of resource utilization are conducted by
AFRINIC to ensure efficient and appropriate usage of
resources. This allows for recovery of any type of
resource where usage is not in compliance with the RSA;
to allow such resources to be reallocated for better
usage.<br>
<br>
13.1 The reviews shall be based on compliance with the
terms outlined in the RSA and Allocation/Assignment
Policies.<br>
<br>
13.2 The reviews cover all allocated/Assigned resources,
but priority goes to IPv4 and ASN mappable to two-octet
ASN.<br>
<br>
13.3 Classes of review: Members to be reviewed shall be
selected according to the following classes:<br>
<br>
13.3.1 Random<br>
<br>
The member is chosen by AFRINIC at random between the
membership.<br>
<br>
<br>
13.3.2 Selected<br>
<br>
Member is selected because of an internal report or due
to a lack of contact between the AFRINIC and the member.<br>
<br>
13.3.3 Reported: Here, members are reviewed either
because:<br>
<br>
A) They have requested the review themselves or<br>
<br>
B) There has been a community complaint made against
them that warrants investigation. Complaints shall be
backed by evidence and AFRINIC staff shall evaluate the
facts as appropriate to conduct the review. However this
review is not applicable to a member with the same
resources portfolio on which a full review has been
completed in the preceding 24 months.<br>
<br>
AFRINIC staff may, at its sole discretion, after having
assessed the nature of the evidence found in the
community complaint, require that such evidence be (i)
submitted in the form of a sworn affidavit or (ii)
declared to be true before a Commissioner of Oath.<br>
<br>
13.4 In case of non-compliance and if evidence has been
established in accordance with:<br>
<br>
• Breach of AFRINIC policies<br>
• Breach of the provisions of the registration
service agreement or other legal agreements between the
organization holding the resource and AFRINIC.<br>
<br>
AFRNIC shall initiate the resource recovery process.<br>
<br>
A) AFRINIC shall attempt to contact the organization and
correct any discrepancy towards the RSA. Except in cases
of fraudulent resource acquisition or unlawful usage
and abuse, the organization shall be given a minimum of
six months to effect the return of the resources.<br>
<br>
If the organization is cooperative and working in good
faith to substantially restore compliance or has a valid
need for additional time to renumber out of the affected
blocks, AFRINIC shall negotiate a longer term.<br>
<br>
The acceptance level of compliance and duration of the
longer term are at AFRINIC staff discretion. <br>
<br>
B) If the situation cannot be rectified and the member
did not transfer the ressources to meet other
AFRINIC-approved needs as per adopted policies<br>
<br>
AFRINIC shall publish the resources to be recovered for
a period of three (3) months; during which the
organization may at any time, seek compliance or
transfer the ressources to other members <br>
<br>
After this period, the resource shall be recovered and
therefore the records of the previous holder of the
recovered resource shall be updated in AFRINIC’s
databases.<br>
<br>
C) Any Internet Number Resources recovered under this
policy may be assigned/allocated under existing
Allocation and Assignment Policies.<br>
<br>
13.5 Appeal procedure<br>
<br>
Reviewed members who are not satisfied have the right to
appeal against the result within the four weeks. Appeals
shall follow an arbitration process as provided for in
the<br>
Code de Procedure Civile (Code of Civil Procedure) of
the Republic of Mauritius. AFRINIC may, on request from
an aggrieved party, suggest a pool of arbitrators who
shall be knowledgeable volunteers from the community.<br>
<br>
13.6 Compliance Report<br>
<br>
AFRINIC shall publish an annual meaningful report
describing review activities, in accordance with all
applicable laws and regulations.<br>
<br>
13.7 Acknowledgements<br>
<br>
The authors thank Ms Wafa Dahmani Zaafouri (become
Afrinic GC Chair), Mr Serge ILUNGA (become Afrinic Board
member) and Mr Alain P. Aina for their contributions
in the development of this Policy proposal.<br>
<br>
The authors also thank the community for the discussions
and contributions.<br>
<br>
4.0 Revision History<br>
<br>
18 May 2016<br>
Version 1.0<br>
- First Draft AFPUB-2016-GEN-001-DRAFT01<br>
- Posted on RPD list<br>
<br>
05 Aug 2016<br>
Version 2.0<br>
- Second Draft AFPUB-2016-GEN-001-DRAFT02<br>
- Change on the policy’s name<br>
- Addition of the Acknowledgement section<br>
- Rephrasing of section 3.3.3<br>
<br>
18 Nov 2016<br>
Version 3.0<br>
- Third Draft AFPUB-2016-GEN-001-DRAFT03<br>
- Update of section 3.3.3 from discussions on mailing
list<br>
- Update of section 3.7 (Acknowledgements) to thank the
community for discussions and contributions<br>
<br>
11 Apr 2017<br>
Version 4.0 <br>
- Fourth Draft AFPUB-2016-GEN-001-DRAFT04<br>
- Update and Rephrasing of section 3.4<br>
- Update and Rephrasing of section 3.5<br>
- Update and Rephrasing of section 3.6<br>
<br>
21 Oct. 2107<br>
Version 5.0 <br>
- Fifth Draft AFPUB-2016-GEN-001-DRAFT05<br>
- Adding the paragraphe C to 13.3.3. according to the
legal counsel proposition<br>
- Rephrasing the paragraphe 13.5 to comply with staff
and legal assessment <br>
- Rephrasing the paragraphe 13.6 to comply with staff
assessment and avoid any ambiguity <br>
- Changing the co-authors list<br>
- Updating the Acknowledgement session<br>
- Amending 13.4 (B) to reflect the Transfer policies<br>
<br>
06 Apr. 2018<br>
Version 6.0 <br>
- Sixth Draft AFPUB-2016-GEN-001-DRAFT06<br>
- Removing categorization between membership in random
class section 13.3.1<br>
<br>
06 Apr. 2019<br>
Version 07<br>
- Seventh Draft AFPUB-2016-GEN-001-DRAFT07<br>
- Modifying section 13.4 Paragraph A) to clarify the
resources recovery process: set conditions under which
a member could be given longer term to effect the
return of the resources. <br>
<br>
-------------------------------------------------------------------------------
End
---------------------------------------------------------------------------------<br>
</div>
<div><br>
</div>
<div>AAAA./<br>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le mar. 3 avr. 2018 à 07:51,
Ernest Byaruhanga <<a href="mailto:ernest@afrinic.net"
moz-do-not-send="true">ernest@afrinic.net</a>> a écrit :<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 style="overflow-wrap: break-word;">Hi Arnaud,
<div>
<div><br>
<blockquote type="cite">
<div>On 31 Mar 2018, at 18:41, Arnaud AMELINA <<a
href="mailto:amelnaud@gmail.com" target="_blank"
moz-do-not-send="true">amelnaud@gmail.com</a>>
wrote:</div>
<br
class="gmail-m_-8108743837464194404Apple-interchange-newline">
<div>
<div dir="ltr">
<div>Dear PDWG,</div>
<div>As you can see through the Lagos PPM minutes
[1], all pending legal concerns have been
addressed. Last suggestion received abiut
removing categories in section 13.3.1( make the
random selection applies to all members) was
accepted by working group and will reflect in
the next version to come.</div>
<div><br>
</div>
<div>While awaiting the new version, please send
any new comments, suggestions you may have on
the proposal [2]</div>
<div><br>
</div>
<div>[1] <a
href="https://afrinic.net/fr/library/policies/archive/ppm-minutes/2261-afrinic-27-pdwg-meeting-minutes"
target="_blank" moz-do-not-send="true">https://afrinic.net/fr/library/policies/archive/ppm-minutes/2261-afrinic-27-pdwg-meeting-minutes</a></div>
<div>[2] <a
href="https://afrinic.net/fr/community/policy-development/policy-proposals/2231-internet-number-resources-review-by-afrinic"
target="_blank" moz-do-not-send="true">https://afrinic.net/fr/community/policy-development/policy-proposals/2231-internet-number-resources-review-by-afrinic</a></div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
Please send the new version well ahead of the recommended
CPM 3.4.2 deadline to allow reasonable time for staff's
assessment of the updated proposal.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Ernest.</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
RPD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RPD@afrinic.net">RPD@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a>
</pre>
</blockquote>
</body>
</html>