8 Jul
2019
8 Jul
'19
7:29 a.m.
Hi Brian,
On Sun, Jul 07, 2019 at 04:42:55PM -0700, Brian Kantor wrote:
Unfortunately, the subject line of this message might
have led to
some misunderstanding.
ok.
About a month ago, several of us received notification
from Vultr that
our BGP RPKI entries were lacking. After some inquiry, it turned out
that these notifications were a false alarm caused by overly-sensitive
audit software, and were to be disregarded. There was no BGP RPKI
problem.
I see. I am happy to observe that this provider is working to improve
their process around whether to accept or reject prefixes learned from
BGP customers. I share your observation that for the context of
44.0.0.0/8 marking prefixes tagged with RPKI state "Unknown" somewhat
over-sensitive.
The current reported problem is almost certainly a
separate issue,
and it would have been helpful had the message had a different
subject line. I doubt if RPKI is involved at all.
OK. Perhaps an IRR route object related issue? We need more debugging
information! https://honestnetworker.net/2016/04/12/network-debugging/
Kind regards,
Job