<div dir="auto"><div dir="auto">+1 Anthony. </div><div dir="auto"><br></div><div dir="auto">I’d also like to add that this policy should go back to discussion for the simple reason that it completely misreads the main role of RIRs. More precisely, and as many individuals have commented on the PPM, RIRs have nothing to do with the resource routing process, it is safe to say that it is totally out of their mandate scope. Their one and only mission is to properly register and allocate number resources to end-users. </div><div dir="auto"><br></div><div dir="auto">Correspondingly, the implementation of this policy will increase the chances of committing routing errors, which can potentially hinder network functioning. In fact, AFRINIC staff has a history in committing such technical mistakes, jeopardizing networks. It is simply not in AFRINIC’s mandate to inject data into the routing database. Plus, the following concern that has been raised during the meeting still remains unaddressed : how does this policy prevents hijacking as it’s intended to do ?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jun 6, 2021, 16:48 Anthony Ubah <<a href="mailto:ubah.tonyiyke@gmail.com">ubah.tonyiyke@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear PDWG,<div><br></div><div>Regarding this policy, I didn't throw my weight on it for one reason. There is a gray area which requires clarity and may turn around to hunt service providers and resource owner in the long run. </div><div>I directed a question to the Legal team at the hearing of this policy, multiple times, and it was inexplicably ignored by Jordi, the Co-chairs and perhaps the legal team, and I still sought clarity on it. </div><div><br></div><div>My question remains; In a situation where, due to human or machine error AS0 is injected by AFRINIC on already assigned resources, and expectedly this result in service disconnection, thus DOS, causing an SLA breach with service end users. <b>Who bears the final brunt for the consequences (e.g.poor QoS, fines, revenue cut, and loss of customers), Afrinic or resource owner?</b></div><div><br></div><div>I still insist this policy isn't ripe, because;</div><div>1. The Legal team must include this on the impact assessment, clearly stating responsibility for liability.</div><div>2. The policy must include text stating these policies and mitigation plans.</div><div>3. Since it has become a trend to follow other RIRs, why do you think most have rejected this policy so far?</div><div>4. How did the RIRs who have adopted this policy tackled this scenario legally?</div><div><br></div><div><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="line-height:150%"><b style="line-height:150%;font-size:12.8px"><span style="line-height:150%"><font face="garamond, serif">Best Regards,</font></span></b></p><p style="line-height:150%"><font face="garamond, times new roman, serif"><b><span style="line-height:150%;font-size:12.8px"><span style="line-height:150%">Anthony </span></span>Ubah </b><br></font></p></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 4, 2021 at 11:00 AM PDWG Chair <<a href="mailto:dacostadarwin@gmail.com" target="_blank" rel="noreferrer">dacostadarwin@gmail.com</a>> wrote:<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><span id="m_-7067639406591852395gmail-m_-8819288778926012565docs-internal-guid-8340d0f9-7fff-afd6-ad0d-6332af72c039" style="color:rgb(0,0,0)"><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Dear PDWG, </span></div><br><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">This is to announce the official start of the last call period for the following policy proposal (in line with the provisions of the CPM):</span></div><br><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">RPKI ROAs for Unallocated and Unassigned AFRINIC Address Space AFPUB-2019-GEN-006-DRAFT03</span></div><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">URL: </span><a href="https://afrinic.net/policy/proposals/2019-gen-006-d3" style="text-decoration:none" target="_blank" rel="noreferrer"><span style="font-size:11pt;font-family:Arial;color:rgb(17,85,204);font-variant-ligatures:normal;font-variant-east-asian:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">https://afrinic.net/policy/proposals/2019-gen-006-d3</span></a></div><br><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The proposal reached rough consensus at the Public Policy Meeting held 2-3 June 2021 in online format. This last call period will run for a period of two weeks as a minimum. The closing date will be communicated to the mailing list depending on the feedback received. </span></div><br><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Regards,</span></div><div style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">PDWG Co-Chairs.</span></div></span><br style="color:rgb(0,0,0)"></div>_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div>