Reaching out to ARIN members about their RPKI INVALID prefixes

Tue Sep 18 18:16:06 UTC 2018

(popping back to the top of the thread.. sorry)

On Tue, Sep 18, 2018 at 7:58 AM nusenu <nusenu-lists at riseup.net> wrote:

> Dear NANOG,
>
> when I approached ARIN about how they feel about reaching out to their
> members about
> prefixes that are unreachable in a route origin validation (ROV)
> environment,
> John Curran (CEO ARIN) referred me to you (see email bellow - quoted with
> permission).
>
>
Perhaps this was answered elsewhere, but:
  "Why is this something ARIN (the org) should take on?"

Why can't (or why isn't) this something that 'many' monitoring/alerting
companies/orgs are offering?
it's unclear, to me, why ARIN is in any better position than any other
party to perform this sort of activity?
I would expect that, at the base level, "I just got random/unexpected email
from ARIN?" will get dropped in the spam-can, while: "My monitoring company
to which I signed up/contracted emailed into my ticket-system for action..
better go do something!" is the path to incentivize.

The question I asked ARIN was specifically:
> > Would you be open to reach out to your affected members to inform them
> about
> > their affected IP prefixes?
>
>
'how?' (email to the tech-contact? etc? did they sign up for said
monitoring and point to the right destination email catcher?)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20180918/cc344419/attachment.html>