<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I think all policies (if we really intend to implement them) must
be clear and leave no room for variable interpretation as
ambiguity will put additional burdens of interpretation on staff.
<br>
</p>
<p>If the community's preference is for the 24-month window to
become invalid on allocation/assignment of new resources, then the
policy (proposal) should state it clearly; If on the other hand,
the intention is for the 24-month window to stay in place
come-what-may, it's better for the policy (proposal) to be
explicit about it.</p>
<p>Please see below, additional questions for the community to
consider. Hopefully, they can be discussed and the authors can (if
they so choose,) take the inputs from the community into their
modified proposal.<br>
</p>
<p>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</p>
<p style="margin-top: 5px; margin-bottom: 5px; color: rgb(51, 51,
51); font-family: Helvetica, Arial, FreeSans, sans-serif;
font-size: 12px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(238, 238, 238);">3.3.2 Selected:</p>
<p style="margin-top: 5px; margin-bottom: 5px; color: rgb(51, 51,
51); font-family: Helvetica, Arial, FreeSans, sans-serif;
font-size: 12px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(238, 238, 238);"><br>
A member is selected because of an internal report or due to a
lack of contact between the AFRINIC and the member.</p>
<p>Q1. Do we presently have an existing (effective) structure (apart
from billing) that measures degree of contact with members? <br>
If there is no agreed means of measuring the degree contact, we
need to define degrees of contact so that "lack of contact" (as
referred to in the proposal) can be measured objectively. <br>
<br>
<i>Perhaps as a first step for ensuring regular contact without
using up too many resources, this proposal might want to borrow
a leaf from RIPE's Assisted Registry Check (ARC). See
<a class="moz-txt-link-freetext" href="https://www.ripe.net/manage-ips-and-asns/resource-management/assisted-registry-check">https://www.ripe.net/manage-ips-and-asns/resource-management/assisted-registry-check</a></i></p>
<p><i>Basically, the RIR does a consistency check on members'</i><i>
Registry, Resource, and Route/rDNS information and then</i><i>
sends emails to the contacts on file showing their view. They
then schedule a telephone call to work with the member and fix
any identified issues. </i><i><br>
</i></p>
<p><i>My understanding from RIPE is that these non-invasive checks
sometimes reveal issues that may warrant more detailed
investigation. The primary model is by random checks but done in
a manner that checks every member at least once in 3 years </i><i>(given
the size of RIPE)</i><i>. They also have ARCs that are initiated
as a result of information received from the member or third
parties. </i><br>
</p>
Q2. Can reachability/cooperation of a member for such a consistency
check-and-fix activity as described above be used to measure the
degree of contact?<br>
<br>
Q3. Given the fact that time taken for consistency checks are more
predictable, can these be implemented as a preliminary step in
addressing the "lack of investigation" problem as well as the
concern about taking up much of members' and/or AFRINIC hostmasters'
time? <br>
<br>
Regards,<br>
Dewole.<br>
(with apologies for continuing the cross-posting between RPD and
Community-discuss)<br>
<br>
<div class="moz-cite-prefix">On 15/11/2016 20:18, sergekbk wrote:<br>
</div>
<blockquote
cite="mid:0esdvkqntn1xves0t66ldl10.1479237528858@email.android.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div>Hello Dewole,</div>
<div>
<div><br>
Thanks for this comment.<br>
The limit of 24 months applies to a member based on
ressources portfolio. If the portfolio changes with new
allocation, member can be audited anytime on the new
ressources if required.</div>
<div>Is this clear enough or shall we make it explicit ?<br>
<br>
Kind Regards.</div>
</div>
<div><br>
</div>
<div id="composer_signature">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<b><i>Serge Ilunga</i></b>
<div><b><i>Cell: +243814443160</i></b></div>
<div><b><i>Skype: sergekbk</i></b></div>
<div><b><i>R.D.Congo</i></b></div>
</div>
<div style="font-size:100%;color:#000000"><!-- originalMessage -->
<div>-------- Original message --------</div>
<div>From: Dewole Ajao <a class="moz-txt-link-rfc2396E" href="mailto:dewole@tinitop.com"><dewole@tinitop.com></a> </div>
<div>Date: 11/15/2016 11:38 (GMT+01:00) </div>
<div>To: Arnaud AMELINA <a class="moz-txt-link-rfc2396E" href="mailto:amelnaud@gmail.com"><amelnaud@gmail.com></a>, "rpd
>> AfriNIC Resource Policy" <a class="moz-txt-link-rfc2396E" href="mailto:rpd@afrinic.net"><rpd@afrinic.net></a>,
General Discussions of AFRINIC
<a class="moz-txt-link-rfc2396E" href="mailto:community-discuss@afrinic.net"><community-discuss@afrinic.net></a> </div>
<div>Subject: Re: [Community-Discuss] Update to Resources review
policy proposal </div>
<div><br>
</div>
</div>
<p>Thanks for working to apply the community's input to your
proposal, Arnaud. <br>
</p>
<p>To test the proposed re-wording, consider the following
sequence of events:<br>
</p>
<p>Member XYZ initiates self-requested review;<br>
Review is completed by AFRINIC in X weeks;<br>
After review, Member XYZ applies for "large chunk" of number
resources;<br>
Member XYZ receives "large chunk" of number resources in say 60
days;<br>
Member XYZ happens to make some unacceptable use of (previous or
new) number resources and it somehow becomes known to the
community;<br>
Regardless of convincing evidence, Member XYZ cannot be
subjected to a review until 24 months have elapsed since the
last review.<br>
</p>
<p>Is this a design feature or a bug?<br>
</p>
<p>Regards,</p>
<p>Dewole.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 15/11/2016 10:48, Arnaud AMELINA
wrote:<br>
</div>
<blockquote
cite="mid:CAGDMR_c=eQOZq0y3gG1MoaccHohWyojceY_XiM6xTP20agDMAA@mail.gmail.com"
type="cite">
<div dir="ltr">
<p dir="ltr">Hi community !<br>
Following, recent discussions and in accordance with text
proposal from Owen and others contributors, authors propose
this as replacement to the section 3.3.3</p>
<p dir="ltr">-'---old version---''</p>
<p dir="ltr">3.3.3 Reported: Here, members are reviewed either
because:</p>
<p dir="ltr">a. They have requested the review themselves or<br>
b. There has been a community complaint made against them
that warrants investigation. </p>
<p dir="ltr">----new version-----</p>
<p dir="ltr">3.3.3 Reported: Here, members are reviewed either
because:</p>
<p dir="ltr">a..They have requested the review themselves or<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 on which a full review has been
completed in the preceding 24 months.</p>
<p>Regards.</p>
<p>Arnaud. <br>
</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Community-Discuss mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Community-Discuss@afrinic.net">Community-Discuss@afrinic.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/community-discuss">https://lists.afrinic.net/mailman/listinfo/community-discuss</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>