On Apr 1, 2013, at 12:17 PM, Sharon Goldberg <[email protected]> wrote:
<snip>
> > Nonetheless, all of the methods for whacking a ROA described in the paper
> > are detectable by anyone who monitors the RPKI. One might argue that each
> > resource holder should monitor his/her RPKI pub point to detect any action
> > that causes one's ROA to become unverifiable.
>
> We agree that monitoring is important and in fact we are working on such a
> monitor right now.
Yeah, actually, we've had RPKISpider up and running for several months:
http://rpkispider.verisignlabs.com/
and @RPKIUpdateBot tweeting all global repo changes for longer:
https://twitter.com/RPKIUpdateBot
Tweets show resource holders how they can view their own delegations and watch
in real time _today_. For example,
http://rpkispider.verisignlabs.com/rpki-rescert-chain.cgi?p=194.126.136.0/21-24&r=6254
Its metrics also serve as a pretty good detection mechanisms for outages. ;)
We're a little behind on a writeup, but we've been known to be active on email.
;)
Eric
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
