<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(0, 0,
0); font-family: Tahoma; font-size: 16px;" text="#000000"
bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 8/Aug/18 10:04, Andy Davidson wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:20180808080458.GA15135@chilli.default.andyd.uk0.bigv.io"
style="border-left: 2px solid #009900 !important; border-right:
2px solid #009900 !important; padding: 0px 15px 0px 15px; margin:
8px 2px; color: rgb(0, 0, 0) !important; color: rgb(0, 0, 0)
!important; color: rgb(0, 0, 0) !important; background-color: null
!important; color: null !important;">
<pre wrap="">
I still do not like that we have imported non RIR originated databases to
our queries as I want there to be a link through from prefix assignment, to
prefix holder, to announcement that I can verify. Hence whilst I ask
operators to please register their announced prefixes in Afrinic's database,
please also create RPKI ROAs for your prefixes. We are testing methodology
to accept/reject prefixes based on ROAs when RPKI hints exist in addition to
generating prefix-lists from IRR. I hope to have some conversations about
how this is going at AfPIF next week.</pre>
</blockquote>
<br>
+1 on encouraging everyone to create ROA's for your allocations (in
all regions, not just AFRINIC).<br>
<br>
Please remember to click the "up to /24" + "up to /48" button so
that the ROA automatically applies to all more-specifics that you
may originate. We've found that the majority of "Invalids" are due
to more-specifics that have not been ROA'd, even though the parent
allocation has.<br>
<br>
Mark.<br>
</body>
</html>