<p dir="ltr">Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<p dir="ltr">On 23 Nov 2016 09:04, "ALAIN AINA" <<a href="javascript:_e(%7B%7D,'cvml','aalain@trstech.net');" target="_blank">aalain@trstech.net</a>> wrote:<br>
><br>
> hello,<br>
><br>
> inline...<br>
>><br>
>> On Nov 22, 2016, at 6:16 PM, Seun Ojedeji <<a href="javascript:_e(%7B%7D,'cvml','seun.ojedeji@gmail.com');" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<br>
>><br>
><br>
>> SO: Well this would have been fine but in a unique environment that we find ourselves<br>
><br>
> which unique environment ? what makes our environment so unique ?<br>
></p>
<p dir="ltr">SO: Actually I don't often use that phrase but I note that it's been used many times on this list to indicate that how we approach things doesn't have to be "based on normal circumstances". My point was that some level of effort should be expected from the complainant to reduce rate of false/invalid complains and maximises staff time.</p>
<p dir="ltr">>> I think it's important to set minimum level of proof that is expected from the complainant. This ensures that significant level of homework has been done by whoever is raising a complain and maximises staff resources.<br>
><br>
> hmmmm. Define all sort of use cases, abuses, frauds and incident reportable and the level of proof to qualify them? <br>
></p><p dir="ltr">
SO: My point was more on incision inclusion of trends and consistency in complains; Wouldn't you agree that it would be more helpful if someone presents proof that indicates consistent fraudulent act. </p>
<p dir="ltr">> This seems like a good topic for an informational RFC<br>
></p><p dir="ltr">
SO: Oga Alain I hope you will agree with me that the statement above isn't necessary, especially if we are supposed to be discussing with one another.</p>
<p dir="ltr">>> Perhaps I should add that it may be good that such complain is limited and open to members alone (since those are the category with "direct stake" in this)<br>
><br>
> The Internet Number Ressources(INR) are public ressources and the community at large is responsible for the management and good utilisation. Furthermore the INRs being used impact everyone and not only AFRINIC members. Report may come from AFRINIC members, but also from end-users, operators, CERTS/CSIRTs, Law enforcement, community member, etc...<br>
></p><p dir="ltr">SO: Would this not then be an abuse related issue and I wonder whether the abuse policy does not already address this? </p><p dir="ltr"><a href="http://www.afrinic.net/library/policies/698-abuse-contact-information-in-the-afrinic-service-region">http://www.afrinic.net/library/policies/698-abuse-contact-information-in-the-afrinic-service-region</a></p><p dir="ltr"><br></p><p dir="ltr">
>> and has a more reliable mean to verify source of the complainant.<br>
><br>
> Why is the source so important if the facts and evidences are good enough for the RIR ? <br>
> In all cases AFRINIC will know and can verify the source.<br>
></p><p dir="ltr">SO: My point here is that just because one have an email address should not be the only thing that identifies the complainant; Further details that clearly identify the person with his/her affiliation is important and I was hoping that this policy doesn't restrict the level of information that staff can request to ascertain source of the complainant. From your response I think we are on the same page with this one.</p><p dir="ltr"><br></p><p dir="ltr">
>> > - for 3.6 as long as the policy is in force, there must be a report as there's Random class review.<br>
>> ><br>
>> > Also, 3.6 does not prescribe naming members. It allows Afrinic staff to decide how to describe the members, thus reviewed resources and level of compliance. <br>
>> ><br>
>> SO: Maybe I am the one not interpreting the current text well. Below is what it currently reads:<br>
>><br>
>> "AFRINIC shall publish an annual report describing the *members* which have been reviewed and their level of compliance."<br>
>><br>
>><br>
> It sound like the term “members” in the section 3.6 is the problem… The text shall then be amended to satisfy all.<br>
></p><p dir="ltr">SO: If the point implies that this proposal does not envisage/require staff to publish the specifics of the members audited then we are both in order. </p><p dir="ltr">Secondly, my suggested edits about the flexibility in timing has not been addressed. i.e Staff may indeed not see any need to run an audit throughout the year hence the point about "annual" report would be misplaced. Will be good to clarify that wording as well.</p><p dir="ltr">Regards</p><p dir="ltr"><br></p><p dir="ltr"><br>
> "Describe the members” in AFRINIC context may at some point looks like:<br>
><br>
> A- How many members have been reviewed :<br>
><br>
> - By type:<br>
> LIR, End-users, etc…<br>
><br>
> - By Category:<br>
> Xlarge, Large, Medium, small, etc…<br>
><br>
> B- Type of ressources invloved:<br>
> ASN, IPv4 ,IPv6<br>
><br>
> C- Level of compliance<br>
>><br>
>> If indeed your intent is similar to mine then I see no reason why it should not be clearly stated in the proposal as I suggested(or in the line with that). I believe a proposal should be as unambiguous as much as possible.<br>
>><br>
>><br>
><br>
> We share the same vision here, but unambiguous does not mean make it meaningless and non evolutive. <br>
><br>
> —Alain<br>
><br>
><br>
>> Regards<br>
>><br>
>> > Kind Regards.<br>
>> ><br>
>> ><br>
>> > Serge Ilunga<br>
>> > Cell:<a href="tel:%2B243814443160" target="_blank"> +243814443160</a><br>
>> > Skype: sergekbk<br>
>> > R.D.Congo<br>
>> > -------- Original message --------<br>
>> > From: Seun Ojedeji <<a href="javascript:_e(%7B%7D,'cvml','seun.ojedeji@gmail.com');" target="_blank">seun.ojedeji@gmail.com</a>><br>
>> > Date: 11/20/2016 09:33 (GMT+01:00)<br>
>> > To: Dewole Ajao <<a href="javascript:_e(%7B%7D,'cvml','dewole@forum.org.ng');" target="_blank">dewole@forum.org.ng</a>><br>
>> > Cc: rpd <<a href="javascript:_e(%7B%7D,'cvml','rpd@afrinic.net');" target="_blank">rpd@afrinic.net</a>><br>
>> > Subject: Re: [rpd] Proposal Update received: Internet Number Resources Review by AFRINIC<br>
>> ><br>
>> > Hello,<br>
>> ><br>
>> > May I suggest rewording of section 3.3.3b and 3.6 to the following:<br>
>> ><br>
>> > 3.3.3b:<br>
>> ><br>
>> > ....Complaints shall be backed by evidence, such evidence must have a consistency duration of at least 3months and AFRINIC staff...."<br>
>> ><br>
>> > 3.6 Compliance Report<br>
>> ><br>
>> > As applicable, AFRINIC shall publish a summary of total number of unit address (or an approximate prefix) reviewed and their level of compliance.<br>
>> ><br>
>> > Sent from my LG G4<br>
>> > Kindly excuse brevity and typos<br>
>> ><br>
>> ><br>
>> > On 19 Nov 2016 22:09, "Dewole Ajao" <<a href="javascript:_e(%7B%7D,'cvml','dewole@forum.org.ng');" target="_blank">dewole@forum.org.ng</a>> wrote:<br>
>> >><br>
>> >> Dear PDWG members,<br>
>> >><br>
>> >> This is to inform you that authors of the policy proposal named "Internet Number Resources Review by AFRINIC" have submitted an updated version as displayed below. PDWG section of AFRINIC website will be updated in due course. <br>
>> >><br>
>> >> Thank you.<br>
>> >> PDWG Co-Chairs<br>
>> >><br>
>> >><br>
>> >> ------------------------[<wbr>Proposal Header]-----------------------<br>
>> >><br>
>> >> Unique identifier: AFPUB-2016-GEN-001-DRAFT03<br>
>> >><br>
>> >><br>
>> >> Draft Policy Name: Internet Number Resources Review by AFRINIC<br>
>> >> Author(s)<br>
>> >> (a) Arnaud A. A. AMELINA |<a href="javascript:_e(%7B%7D,'cvml','arnaud.amelina@auf.org');" target="_blank"> arnaud.amelina@auf.org</a> | AUT.TogoRER<br>
>> >> (b) Serge ILUNGA KABWIKA |<a href="javascript:_e(%7B%7D,'cvml','sergekbk@gmail.com');" target="_blank"> sergekbk@gmail.com</a> | Vodacom Congo SA<br>
>> >> (c) Jean-Baptiste MILLOGO |<a href="javascript:_e(%7B%7D,'cvml','jbmillogo@gmail.com');" target="_blank"> jbmillogo@gmail.com</a> | Airtel Burkina<br>
>> >> (d) DAHMANI ZAAFOURI Wafa |<a href="javascript:_e(%7B%7D,'cvml','wafa@ati.tn');" target="_blank"> wafa@ati.tn</a> | ATI <br>
>> >><br>
>> >> Draft Policy <br>
>> >><br>
>> >> Submission Date : 19 Nov. 2016<br>
>> >><br>
>> >> Related Policies (where applicable)<br>
>> >> Obsoletes : None<br>
>> >> Amends : None<br>
>> >><br>
>> >> ------------------------[<wbr>Proposal Header]-----------------------<br>
>> >><br>
>> >><br>
>> >> 1. 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.<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 type of abuses.<br>
>> >><br>
>> >> <br>
>> >> 2.0 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>
>> >> <br>
>> >> 3.0 Proposal<br>
>> >><br>
>> >> 3.1 The reviews shall be based on compliance with the terms outlined in the RSA and Allocation/Assignment Policies.<br>
>> >> <br>
>> >><br>
>> >> 3.2 The reviews cover all allocated/Assigned resources, but priority goes to IPv4 and ASN mappable to two-octet ASN.<br>
>> >> <br>
>> >><br>
>> >> 3.3 Classes of review: Members to be reviewed shall be selected according to the following classes: <br>
>> >><br>
>> >> 3.3.1 Random: 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>
>> >> 3.3.2 Selected:<br>
>> >><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>
>> >> 3.3.3 Reported: Here, members are reviewed either because:<br>
>> >><br>
>> >> 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 with the same resources portfolio on which a full review has been completed in the preceding 24 months.<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>
>> >> - Unjustified lack of visibility of the resource on the global routing table.<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>
>> >> - Evidence that an organisation is no more operating and its blocks have not been transferred.<br>
>> >> - Unauthorized transfers of resources.<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’s 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>
>> >><br>
>> >> The review shall be conducted in full transparency and neutrality. But if the result of the review does not appear to be fair, the reviewed 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>
>> >> Outcome of the arbitration process are unequivocal<br>
>> >> <br>
>> >><br>
>> >> 3.6 Compliance Report<br>
>> >><br>
>> >> AFRINIC shall publish an annual report describing the members which have been reviewed and their level of compliance.<br>
>> >> <br>
>> >><br>
>> >> 3.7 Acknowledgement<br>
>> >><br>
>> >> - The authors thank Mr. Alain AINA for his contribution in the development of this Policy proposal.<br>
>> >> - The authors also thank the community for the discussions and contributions.<br>
>> >><br>
>> >> 4.0 Revision History<br>
>> >><br>
>> >> 18 May 2016 Version 1.0 <br>
>> >><br>
>> >> First Draft AFPUB-2016-GEN-001-DRAFT01 Posted on RPD list<br>
>> >><br>
>> >> 05 Aug 2016 Version 2.0 <br>
>> >><br>
>> >> - Change on the policy’s name<br>
>> >> - Addition of the Acknowledgement section<br>
>> >> - Rephrasing of section 3.3.3<br>
>> >><br>
>> >> 19 Nov 2016 Version 3.0 <br>
>> >> - Update of section 3.3.3 from discussions on mailing list<br>
>> >> - Update of section 3.7 (Aknowledgement) to thank the</p>
<br><br>-- <br><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">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">alt email:<a href="http://goog_1872880453" target="_blank"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bringing another down does not take you up - think about your action!<br></blockquote></blockquote></font><br></div></div></div></div></div><br>