[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
the prefixes that wont be able to reach Cloudflare by the end of the year (unless RPKI ROAs are fixed)
- Subject: the prefixes that wont be able to reach Cloudflare by the end of the year (unless RPKI ROAs are fixed)
- From: michel.py at tsisemi.com (Michel Py)
- Date: Wed, 19 Sep 2018 18:29:15 +0000
- In-reply-to: <[email protected]>
- References: <[email protected]>
> nusenu wrote :
> apparently Cloudflare will be enforcing RPKI route origin validation "by the end of the year" .
> If this is actually the case then some prefixes run at risk of loosing the ability to reach Cloudflare.
This is the way we are going to get people to clean up their invalid prefixes. When people start to actually discard or block them and something breaks.
I still think that ARIN should be contacting them, if they are willing to do it.
> Phil Lavin wrote :
> That said, having recently done this with ARIN... they've got a long way to go before it's a simple process (like RIPE). Submitting numerous tickets over a 3 day period doesn't strike me as particularly efficient.
I was wondering if this is the reason ARIN is so far behind RIPE in terms of RPKI adoption. I did not find it bad personally, but I could understand that it may discourage people with a large number of prefixes.
There must be something else than the process not being as simple as RIPE's, IMHO.
TSI Disclaimer: This message and any files or text attached to it are intended only for the recipients named above and contain information that may be confidential or privileged. If you are not the intended recipient, you must not forward, copy, use or otherwise disclose this communication or the information contained herein. In the event you have received this message in error, please notify the sender immediately by replying to this message, and then delete all copies of it from your system. Thank you!...