<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-ZA link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi Mark, <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>thanks<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>On further investigation, it appears that the old ROA engine is/was “off the air” (I say was, at the time of writing this email, it appears back – I have been in contact with Afrinic, so…but waiting to hear anything)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The challenge that I am finding is that there seems to be no way to verify real time.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Using http://validator.afrinic.net:8080/trust-anchors, I have revoked an offending prefix 154.72.108.0/22 yet despite the update timer saying it was updated 5 minutes ago (10:50) and I revoked the certificate at 10:16, it still shows at axtive.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The prefix has one originating AS in the old engine and another in the new engine (I am migrating networks)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Another prefix 41.77.156.0/23 which had a ROA in the old engine, when querying at bgmon, show no ROA – same for all my other prefixes in the old engine.<o:p></o:p></span></p><p class=MsoNormal>[saul@linux1 ~]$ whois -h whois.bgpmon.net " --roa 32653 41.77.156.0/23"<o:p></o:p></p><p class=MsoNormal>[Querying whois.bgpmon.net]<o:p></o:p></p><p class=MsoNormal>[whois.bgpmon.net]<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>That said, a few hours later and I am now, correctly getting:<o:p></o:p></span></p><p class=MsoNormal>[saul@linux1 ~]$ whois -h whois.bgpmon.net " --roa 32653 41.77.156.0/23"<o:p></o:p></p><p class=MsoNormal>[Querying whois.bgpmon.net]<o:p></o:p></p><p class=MsoNormal>[whois.bgpmon.net]<o:p></o:p></p><p class=MsoNormal>0 - Valid<o:p></o:p></p><p class=MsoNormal>------------------------<o:p></o:p></p><p class=MsoNormal>ROA Details<o:p></o:p></p><p class=MsoNormal>------------------------<o:p></o:p></p><p class=MsoNormal>Origin ASN: AS32653<o:p></o:p></p><p class=MsoNormal>Not valid Before: 2014-02-06 13:27:59<o:p></o:p></p><p class=MsoNormal>Not valid After: 2018-02-01 13:27:59 Expires in 2y188d16h52m24.2000000029802s<o:p></o:p></p><p class=MsoNormal>Trust Anchor: rpki.afrinic.net<o:p></o:p></p><p class=MsoNormal>Prefixes: 41.77.156.0/23 (max length /23)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Maybe BGMon had an issue…. (with us and others)<o:p></o:p></p><p class=MsoNormal>So my question is more how to get accurate realtime verification of what is in the DB and what others are seeing. <a href="http://validator.afrinic.net:8080/trust-anchors">http://validator.afrinic.net:8080/trust-anchors</a> isn’t current (or even vaguely, despite their timers)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks<o:p></o:p></p><p class=MsoNormal>Saul<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='color:windowtext;mso-fareast-language:EN-ZA'>From:</span></b><span lang=EN-US style='color:windowtext;mso-fareast-language:EN-ZA'> Mark Tinka [mailto:mark.tinka@seacom.mu] <br><b>Sent:</b> 28 July 2015 09:55 AM<br><b>To:</b> Saul <saul@enetworks.co.za>; afnog@afnog.org<br><b>Subject:</b> Re: [afnog] RPKI<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;mso-fareast-language:EN-ZA'><o:p> </o:p></span></p><div><p class=MsoNormal>On 28/Jul/15 09:34, Saul wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Hi<o:p></o:p></p><p class=MsoNormal>Sorry for not giving to much info here, but I still trying to pinpoint what the issue is. <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I am suddenly getting alerts from BGPmon about RPKI validation failing on some of my prefixes and I have made no changes.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I am seeing different data on <a href="http://www.rpki.co.za/roas">http://www.rpki.co.za/roas</a> verses what I am seeing at HE.net – both what is valid and what I have ROAs for.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I know of at least one other entity having issues as well and was wondering if it is not perhaps a bigger issue?<o:p></o:p></p></blockquote><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-ZA'><br>Can you send your prefixes through so we can check what the actual validation state is vs. what HE are reporting?<br><br>There was a time when HE had an issue obtaining RPKI data from AFRINIC. This was some kind of issue AFRINIC were having, I suppose when changing over to the new PKI engine. That was fixed, but that was a couple of months ago. <br><br>For my network (AS37100), both HE and <a href="http://www.rpki.co.za">www.rpki.co.za</a> are showing the correct data.<br><br>Also, note that AFRINIC have been encouraging operators to upgrade to the new engine (which now supports max-length). I'm not sure whether this could be affecting the old engine.<br><br>Mark.<o:p></o:p></span></p></div></body></html>