Reaching out to ARIN members about their RPKI INVALID prefixes

• Subject: Reaching out to ARIN members about their RPKI INVALID prefixes
• From: owen at delong.com (Owen DeLong)
• Date: Tue, 18 Sep 2018 14:35:44 -0700
• In-reply-to: <CA[email protected]>
• References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <CA[email protected]> <[email protected]> <CA[email protected]>

> 
> "rir says owen can originate route FOO"
> "ROA for 157.130.1.0/24 <http://157.130.1.0/24> says OWEN can originate"
> 

Nopeâ?¦ ROA says (e.g.) AS1734 (or anyone willing to impersonate AS1734)  can originate 192.159.10.0/24.

> those seem like valuable pieces of information. Especially since I can know this through some machine parseable fashion.

I would agree if you had some way to distinguish AS1734 originating FOO from AS174 originating FOO with a prepend of AS1734.

Owen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20180918/207b32a3/attachment.html>

• Follow-Ups:
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: job at ntt.net (Job Snijders)

• References:
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: nusenu-lists at riseup.net (nusenu)
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: owen at delong.com (Owen DeLong)
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: job at ntt.net (Job Snijders)
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: morrowc.lists at gmail.com (Christopher Morrow)
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: owen at delong.com (Owen DeLong)
  • Reaching out to ARIN members about their RPKI INVALID prefixes
    • From: morrowc.lists at gmail.com (Christopher Morrow)

• Prev by Date: Reaching out to ARIN members about their RPKI INVALID prefixes
• Next by Date: Brovade/Foundry VLAN translation
• Previous by thread: Reaching out to ARIN members about their RPKI INVALID prefixes
• Next by thread: Reaching out to ARIN members about their RPKI INVALID prefixes
• Index(es):
  • Date
  • Thread